1.1.3 Usage of Remote-SAT
If no customer application is involved there is no need to communicate through the AT interface, and
Both scenarios – whether or not
As a cellular module does not have an MMI, RSAT differs from a phone implementation of SAT. It uses a special set of AT Commands to pass data, e.g. a list of menu items, to the TA and to receive responses, e.g. a selected menu item.
The TA, being the customer application, is required to implement a state machine that controls the module's SAT. It monitors the states of SAT and sends appropriate AT commands when required, depending upon user input. As an example of a proven implementation approach, the SIEMENS PC- MMI tool is available on request.
If the TA does not offer the SIM Application Toolkit to the end user, e.g. online banking, information services, then the module does not place any requirements on the TA for additional support. Therefore the state machine and the use of RSAT AT commands do not need to be implemented in the TA.
1.1.4 Command Type Values
The Command Type value (<cmdType>) identifies the type of command or associated response passed between the TA (customer application) and the ME.
<cmdType>) is the parameter that comes first in AT commands, in response to AT^SSTGI (see Chapter 1.4) and AT^SSTR (see Chapter 1.5), and in the ^SSTN unsolicited result code (see Chapter 1.3).
The SAT implementation supports SAT class 3 (GSM 11.14 Release 98, no support of letter classes). Therefore, Table 1 summarizes only those command types and parameters which may appear on the user interface (UI) and thus, allow the user to take an action. Command types that are transparent to the user are not listed in the table, although they are supported by
MC35_SAT_01_v02.00 | Page 8 of 65 | 11.01.2002 |