17.10.2012 Views

Iridium Short Burst Data Service Developers ... - Discoverytelecom.eu

Iridium Short Burst Data Service Developers ... - Discoverytelecom.eu

Iridium Short Burst Data Service Developers ... - Discoverytelecom.eu

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Iridium</strong> Satellite LLC<br />

<strong>Short</strong> <strong>Burst</strong> <strong>Data</strong> <strong>Developers</strong> Guide V2.01<br />

5.4.5 MT DirectIP Header<br />

The information in this header is required as part of every DirectIP MT message delivery.<br />

5.4.5.1 MT Header Length<br />

This field specifies the number of bytes in the IE following this byte. Even though the length is fixed, the field<br />

is included as a standard across all IEs and to allow for maximum flexibility for future enhancements.<br />

Field Name <strong>Data</strong> Type<br />

Table 5-13 MT Header IE<br />

Length<br />

(bytes)<br />

43<br />

<strong>Iridium</strong> Satellite LLC Proprietary & Confidential<br />

Range of Values<br />

MT Header IEI char 1 See Table 5-7<br />

MT Header Length unsigned short 2 21<br />

Unique Client Message ID char 4 From client (not MTMSN)<br />

IMEI (User ID) char 15 ASCII Numeric Characters<br />

MT Disposition Flags unsigned short 2<br />

5.4.5.2 Unique Client Message ID<br />

Bit Map: See Table 5-14 MT Disposition<br />

Flags<br />

The vendor client will include a 4-byte message ID unique within its own application. This value is not used<br />

in any way by the GSS server except to include it in the confirmation message sent back to the client. This is<br />

intended to serve as a form of validation and reference for the client application. The data type is specified<br />

to be characters. However, from the client’s perspective, the four bytes may be a character string, an<br />

integer, etc.<br />

5.4.5.3 IMEI<br />

The IMEI is the equipment identifier, unique to each <strong>Iridium</strong> field device, of the MT message destination<br />

IMEI. It is a 15-digit number represented here in ASCII format.<br />

5.4.5.4 MT Disposition Flags<br />

These flags are set by the vendor client to trigger particular actions by the GSS. Combinations of flags are<br />

allowed. The field is a 2-byte bit map with 16 available flags. Those defined are shown in Table 5-14.<br />

Table 5-14 MT Disposition Flags<br />

Disposition Flag Value Description<br />

Flush MT Qu<strong>eu</strong>e 0x0001 Delete al MT payloads in the IMEI’s MT qu<strong>eu</strong>e<br />

Send Ring Alert –Mo MTM 0x0002<br />

Send ring alert with no associated MT payload<br />

(normal ring alert rules apply)<br />

5.4.6 MT Payload<br />

This information element includes the actual MT payload to be qu<strong>eu</strong>ed and delivered over the air to the<br />

destination IMEI. This inclusion of this IE in the MT delivery is optional based on the disposition flags<br />

included in the header.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!