Difference between revisions of "IoTGateway/CoAP-like"
From ESS-WIKI
(Created page with "=Advantech CoAP-like Packet Structure= <br /> '''<big><big>CoAP-like Packet Format</big></big>'''<br /> 600x100px '''<big><big>CoAP-like...") |
|||
| Line 7: | Line 7: | ||
'''<big><big>CoAP-like Header</big></big>'''<br /> | '''<big><big>CoAP-like Header</big></big>'''<br /> | ||
[[File:CoAP-like-Header.jpg|780x160px]] | [[File:CoAP-like-Header.jpg|780x160px]] | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |- | ||
| + | ! Name !! Size ( bits ) | ||
| + | |- | ||
| + | | Ver || 2 | ||
| + | |- | ||
| + | | Type (T) || 2 | ||
| + | |- | ||
| + | | TKL: Token Length || 4 | ||
| + | |- | ||
| + | | Code || 8 | ||
| + | |- | ||
| + | | Message ID || 16 | ||
| + | |- | ||
| + | | Length || 32 | ||
| + | |} | ||
| + | |||
| + | '''Type (T) :''' 2-bit unsigned integer Transaction Type field. Indicates if this message is | ||
| + | *'''Confirmable (0)''': Some messages require an acknowledgment | ||
| + | *'''Non-Confirmable (1)''': Some other messages do not require an acknowledgment | ||
| + | *'''Acknowledgment (2)''': An Acknowledgment message acknowledges that a specific Confirmable message (identified by its Transaction ID) arrived | ||
| + | *'''Reset (3)''': A Reset message indicates that a specific Confirmable message was received, but some context is missing to properly process it. This condition is usually caused when | ||
| + | ::::the receiving node has rebooted and has forgotten some state that would be required to interpret the message | ||
| + | |||
| + | '''Code :''' : 8-bit unsigned integer <br /> | ||
| + | '''Request''' | ||
| + | *'''GET(0.01): 1''' | ||
| + | *'''PUT(0.03): 3''' | ||
| + | |||
| + | '''Response''' | ||
| + | *'''Change(2.04): 68''' | ||
| + | *'''Content(2.05): 69''' | ||
| + | *'''Bad Request(4.00): 128''' | ||
| + | *'''Unauthorized(4.01): 129''' | ||
| + | *'''Not Found(4.04): 132''' | ||
| + | *'''Method Not Allowed(4.05): 133''' | ||
| + | *'''Not Implemented(5.01): 161''' | ||
Revision as of 04:34, 8 March 2016
Advantech CoAP-like Packet Structure
CoAP-like Packet Format
CoAP-like Header
| Name | Size ( bits ) |
|---|---|
| Ver | 2 |
| Type (T) | 2 |
| TKL: Token Length | 4 |
| Code | 8 |
| Message ID | 16 |
| Length | 32 |
Type (T) : 2-bit unsigned integer Transaction Type field. Indicates if this message is
- Confirmable (0): Some messages require an acknowledgment
- Non-Confirmable (1): Some other messages do not require an acknowledgment
- Acknowledgment (2): An Acknowledgment message acknowledges that a specific Confirmable message (identified by its Transaction ID) arrived
- Reset (3): A Reset message indicates that a specific Confirmable message was received, but some context is missing to properly process it. This condition is usually caused when
- the receiving node has rebooted and has forgotten some state that would be required to interpret the message
Code : : 8-bit unsigned integer
Request
- GET(0.01): 1
- PUT(0.03): 3
Response
- Change(2.04): 68
- Content(2.05): 69
- Bad Request(4.00): 128
- Unauthorized(4.01): 129
- Not Found(4.04): 132
- Method Not Allowed(4.05): 133
- Not Implemented(5.01): 161