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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

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

4.2ISU- ISU Messages<br />

Messages from ISU #1 are to a second ISU (ISU #2) without leaving the <strong>Iridium</strong> network. [See Figure 4-1.]<br />

This option requires provisioning by the Value Added Reseller through SPNet. ISU #1 can be provisioned to<br />

send the same MO-SBD message to up to five ISUs. Note that only one delivery method is permitted: Either<br />

email or ISU-ISU, it is not possible to mix destination types.<br />

ISU-ISU SBD messages are billed twice. Once as a MO-SBD message to the initiating ISU IMEI and once<br />

as a MT-SBD message to the terminating ISU IMEI.<br />

The MO-SBD message from ISU #1 is placed into the MT-SBD qu<strong>eu</strong>e of ISU #2 when it has been received<br />

by the GSS. The MO-SBD message is never delivered to the Vendor Application as no email address can<br />

be programmed for the Vendor Application. No SBD session descriptors are delivered to either the<br />

originating or terminating ISU. However if ISU #2 is provided to send MO-SBD messages to a VA, then the<br />

mailbox check or sending of a MO-SBD message will cause an email message indicating the mailbox check<br />

or the transmission of the MO-SBD message to the Vendor Application. There are five error conditions that<br />

can occur in ISU-ISU SBD messaging as shown in Table 4-1 below.<br />

Table 4-1: Mobile Originated Message Email Message Field Description<br />

Error Condition Action<br />

Message size = 0 bytes MT-SBD message will not be qu<strong>eu</strong>ed and will be deleted<br />

Message Size >270 bytes when ISU #2 is<br />

MT-SBD message will not be qu<strong>eu</strong>ed and will be deleted<br />

a 9601 SBD Transceiver<br />

Message size >1890 bytes when ISU #2 is<br />

a 9522 or 9522A LBT<br />

Destination ISU MT qu<strong>eu</strong>e > 50 messages<br />

Destination ISU is not provisioned<br />

ISU #1<br />

MT-SBD message will not be qu<strong>eu</strong>ed and will be deleted<br />

If the destination ISU MT qu<strong>eu</strong>e is full the MT-SBD<br />

message will not be qu<strong>eu</strong>ed<br />

If the destination ISU is not provisioned the MT-SBD<br />

message will not be qu<strong>eu</strong>ed<br />

<strong>Iridium</strong> Gateway<br />

31<br />

ETC Subsystem<br />

ETS SEP ECS<br />

SPP<br />

SBD<br />

Subsystem<br />

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

ISU #2<br />

Telephony<br />

Switch<br />

Figure 4-1 SBD Call Routing for ISU-ISU SBD Messages<br />

PSTN<br />

Internet<br />

Email

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

Saved successfully!

Ooh no, something went wrong!