Chapter 5 - Carrier Specific Information; Notice For Devices That Use Aeris Radios; Multi-Tech Sprint Approved Device Requirements; Telit Oma Dm Notifications - Multitech SocketModem Cell Device Manual

Chapter 5 – Carrier Specific Information

Notice for Devices that Use Aeris Radios

One component of your device is a radio. A radio algorithm prevents your device from repeatedly attempting to
connect to the network when the radio:
cannot establish a packet data connection or

fails to access the application server.

When writing applications for your devices, ensure that your applications do not interfere with the radio's
connection retry algorithm. If you fail to do so, Aeris might block network access for your devices.
After your devices reach the end of their commercial lifespan, you must remove them from the Aeris network. To
do so, remove power from the devices and remove their antennas. If your devices continue to attempt to register
with the network after you cancel device subscriptions, Aeris can bill you for any traffic generated by those
devices.

Multi-Tech Sprint Approved Device Requirements

Any changes to a Sprint approved Multi-Tech device circuit board or antenna system requires you to contact
Sprint certifications. Sprint will determine if additional testing is required due to modification of the approved
device circuit board or antenna system.
All applications interacting with Sprint approved Multi-Tech devices must be written in a manner where they do
not interfere/ interrupt the Sprint HFA process or OMA-DM processes outlined in section labeled Telit OMA DM
Notifications.
If the Multi-Tech device will be co-located with any other transmitters you will be required to submit your device
to an FCC approved lab for additional FCC testing.
If the Sprint approved Multi-Tech device/circuit board is embedded into another device/circuit board be aware
you will be required to perform EMC and safety testing on your end device.

Telit OMA DM Notifications

Applications should look for the following unsolicited OMA indications at all times:
#904 HFA Started
#905 PRL - Session started
#906 DC - Session started
#907 FUMO -Session started
If application sees one of these indications it should not attempt to issue commands, attempt data connection, or
reset device until the OMA process is complete as indicated by additional #9XX OMA success or failure indications
below.
If the device is in a data connection when a Network Initiated PRL, DC, or FUMO update alert message is received
from Sprint the radio will wait for a point where data is not being transmitted, then "gracefully" close the data
connection, and then start OMA-DM process with #9xx indication. When this occurs the application should not
SocketModem CDMA MTSMC-C2 Device Guide
CHAPTER 6 –APPLICATION NOTES
14