User's Manual

Iridium Satellite LLC
9601 Transceiver –AT Command Reference
Iridium Satellite LLC Proprietary & Confidential Information Page 25 of 51
Information contained herein is preliminary and subject to change without further notice
that auto-registration runs only while the Transceiver is attached to the gateway,
i.e. the registration status is “Not registered” or “Registered”.
Auto-registration may only be used with system-provided location. If the FA is
providing its own location (e.g. GPS), the FA should use the manual registration
command, +SBDREG.
Upon triggering in mode 1, “Automatic”, the Transceiver autonomously initiates an
SBD session in order to perform a registration with the updated location of the
Transceiver, with the session type set to 3 –auto-registration. This session does
not transfer any MO or MT messages.
Upon triggering in mode 2, “Ask”, the Transceiver reports to the FA that it should
register with the system because the Transceiver location has changed (see
<event> below); it is then the responsibility of the FA to register via +SBDREG or
+SBDIX. +SBDIX allows the FA to register while including an MO message and/or
retrieving an MT message that is pending at the Gateway.
When auto-registration is enabled, mode 1 or 2, the Transceiver reports relevant
events to the FA by issuing an unsolicited result code +AREG:<event>,<reg error>.
<event>:
0 Suggest FA makes a registration attempt (mode 2 only)
1 Auto-registration has been performed successfully (mode 1 only)
2 Auto-registration has failed and will be retried after a delay (mode 1
only)
<reg error>:
Gateway-reported values
0 No error.
2 Session completed but the requested Location Update was not
accepted.
3..14 Reserved, but indicate Location Update failure if used.
15 Access is denied.
Transceiver-reported values
16 Transceiver has been locked and may not make SBD calls (see
+CULK command).
17 Gateway not responding (local session timeout).
18 Connection lost (RF drop).
19..31 Reserved, but indicate failure if used.