35: Device IDs
Used to GET the various IDs of the device.
Message fields
Fields specific to Device IDs. Operation sections below explain when each field is used.
| Field | Type | Description | Example |
|---|---|---|---|
| IDField 1 | uint | Unique ID for the device which is used in the cloud API. uint32 or uint64 only | 10579203Example |
| IMEIField 2 | ascii | IMEI - 15 characters | 864950060212587Example |
| ICCIDField 3 | ascii | ICCID - 19 to 22 characters | 89457300000022214806Example |
| SerialField 4 | uint32 | Device serial number. Currently only available on some device types. | |
| Cached SIM2 ICCIDField 8 | ascii | SIM2 ICCID cached from a previous read. This value may be stale. |
Examples are observed values from the linked captures, not defaults.
Read device IDs
Request the available device and SIM identifiers.
Request
No payload fields are required. Include Method GET to request the device identifiers.
Request headers
- MethodHeader 5
uint8requiredValue
2· GETRequest a service to be perform an action
- Message IDHeader 1
uint32optionalInclude a nonzero Message ID to correlate the reply.
Expected response (MT35)
Device IDs
The GET response contains the available device identifiers. Not all fields are available on every device type. Cached SIM2 ICCID is a previously read value and may be stale.
Correlation, status and acknowledgment rules
Response data fields
- IDField 1
uintoptionalUnique ID for the device which is used in the cloud API. uint32 or uint64 only
- IMEIField 2
asciioptionalIMEI - 15 characters
- ICCIDField 3
asciioptionalICCID - 19 to 22 characters
- SerialField 4
uint32optionalDevice serial number. Currently only available on some device types.
- Cached SIM2 ICCIDField 8
asciioptionalSIM2 ICCID cached from a previous read. This value may be stale.
Message and field constants
Identifiers for this message type and its fields. See the operation sections above for rules and limits.