> 15.1 | AT^SRSA Remote SIM Access Activation

> The AT^SRSA write command enables and disables RSA connections and allows to control the TC65's SIM usage scheme.
> The AT^SRSA read command requests the current RSA status. Every line indicates an RSA connection, if any.
> Syntax

> Test Command AT^SRSA=?
> Response(s)
> ^SRSA:(list of supported <devId>s) , (list of supported <sapRole>s) , (list of supported <muxChan>s) , (list of supported <dataForm>s) , (list of supported <beaconPer>s) , (list of supported <discType>s)
> OK

> Read Command AT^SRSA?
> Response(s)
> [^SRSA:<devId>, <sapRole>, <connState>, <muxChan>, <dataForm>, <beaconPer>]
> OK

> Write Command AT^SRSA=<devId>, <sapRole>[, <muxChan>[, <dataForm>[, <beaconPer>[, <discType>]]]]
> Response(s)
> ^SRSA:<actResult>
> OK

> Reference(s) |  | PIN |  | ASC0 | ASC1 | USB | MUX1 | MUX2 | MUX3 |  |  | Charge | Q | Last
> SIEMENS |  | - |  | + | + | + | + | + | + |  |  | - | - | -

> Unsolicited Result Code
> ^SRSA: <devId>, <sapRole>, <connState>
> This URC is generated if either the SIM usage scheme or the SAP connection status has changed due to SAP message communication or AT command control.
> Parameter Description

> <actResult>(num)

> Activation result
> 0
> No Error
> Parameters valid, SAP mode change initiated. However, actual mode change is signaled via URC "^SRSA".
> Other values indicate invalid activation requests, no SAP mode change is initiated in the following cases:
> 1
> Error unspecified.
> 2
> Error activation command is busy.
> 3
> Error activation started with serial multiplex mode is off.
> 4
> Error activation started on invalid serial multiplex channel.
> 5
> Error device Id is already known.
> 6
> Error SAP mode is already active.
> 7
> Error invalid parameter.

> <devId>(num)

> Device identification
> Arbitrary number assigned on RSA activation by the host. Used for all subsequent RSA communication (AT commands and URCs) during the activated session. Different numbers shall be used for SAP server and client.
> 1...100

> <sapRole>(num)

> SIM usage scheme of the TC65
> Direct switch from SAP server to SAP client mode and vice versa is not supported.
> 0(P)
> Local SIM
> If this parameter value is used with write command meaning depends on parameter <discType>.
> 1
> SAP server
> Enables Remote SIM Access and configures the TC65 as SAP server.
> The SAP server waits for CONNECT_REQ messages sent from the SAP client until the right <MaxMsgSize> is negotiated. Once the SAP client sends a CONNECT_REQ message with <MaxMsgSize> 276, the SAP server deregisters from the network and then acts as SIM card reader.
> However, under the following conditions the SAP server will not react to CONNECT_REQ messages:

> • | during any calls (voice or data),

> • | if a GPRS context is activated,

> • | if Remote-SAT interface is activated (AT^SSTA) and a proactive command is ongoing.

> 2
> SAP client
> Enables Remote SIM Access and configures the TC65 as SAP client.
> The SAP client starts sending CONNECT_REQ messages periodically, until the right <MaxMsgSize> is negotiated. The intervals between sending CONNECT_REQ messages are set with <beaconPer>. The SAP client deregisters from the network if a local SIM was used before and switches to the remote SIM after receiving all of the following messages from the SAP server:

> • | the SAP message CONNECT_RESP,

> • | the SAP message STATUS_IND

> • | and, finally, the SAP message ATR_RESP received after the appropriate request was issued by the client.

> However, under the same conditions listed above for <sapRole>=1, the SAP client will not send CONNECT_REQ messages, nor will it switch to the remote SIM.

> <muxChan>(num)

> Serial multiplexer channel number
> Logical channels 2 and 3 can be reserved for RSA traffic on serial interface multiplexer. Multiplex mode shall be enabled before RSA activation via AT+CMUX.
> Note:
> Number of multiplex channels is implementation specific, please refer to AT+CMUX and the multiplex documentation supplied with the TC65. If for instance three logical channels are implemented these are referenced as numbers 1 - 3. The selected multiplexer channel is dedicated to the RSA communication. However, it is not possible to reserve logical channel number 1 for RSA traffic because only on this channel the TC65 can perform circuit switched data transfer, e.g. FAX or data calls. If no channel is specified the ME uses the channel on which the command was issued.

> <dataForm>(num)

> SAP message data format
> [0]
> XSAP ATC/URC format
> SAP messages are translated into ASCII coded strings and transmitted as parameters of the AT^SRSM command and the "^SRSM" URC. When using a Bluetooth modem with AT command interface for transmitting data, it is recommended to choose the XSAP data format. Note that AT commands not related to RSA shall not be used after RSA activation on the dedicated serial multiplexer channel.
> 1
> SAP transparent binary format
> SAP messages are transmitted as coded in the SAP specification. This data format should be selected for transmitting SIM data to a Bluetooth stack which is part of the application. The binary data will be exchanged transparently with the ME. However, the SAP data format does not need ASCII character conversion. As a result less data will be transferred and the SIM communication will be faster.

> <beaconPer>(num)

> Beacon period
> 0...[6]...100
> Specifies the number of seconds the SAP client waits before sending the next CONNECT_REQ message. A 0 value leads to a one-time connection request. This parameter is applicable for SAP client activation only.

> <discType>(num)

> SAP disconnection type
> This parameter is only applicable if <sapRole> equals 0.
> Calls or active GPRS contexts via a remote SIM will be lost due to missing SIM access. Use of AT+CLCC is recommended to query call states before RSA deactivation.
> 0
> Hold SAP role
> SAP connection is going to be disabled. The TC65 remains in SAP mode and is ready to (re)establish an SAP connection. If an SAP connection was ongoing a URC "^SRSA: <devId>, <sapRole>, <connState>" with <connState>= 0 is issued.

> • | A server exclusively sends an SAP message DISCONNECT_IND (type "Graceful") to the client.

> • | A client saves the SIM data temporarily held in the TC65's memory to the remote SIM and sends the DISCONNECT_REQ message to the server. If requested the client restarts sending CONNECTION_REQ messages. If a local SIM is attached the TC65 will use it to register to the network until a server offers its SIM again.

> [1]
> Stop SAP operation
> SAP connection is disabled and TC65 is forced to local SIM mode. A URC "^SRSA: <devId>, <sapRole>, <connState>" with <sapRole>= 0 and <connState>= 0 is issued.

> • | A server sends a DISCONNECT_IND message (type "Immediate") to the client and returns to local SIM mode immediately. SIM data temporarily held in the client's memory would be lost.

> • | A client exclusively sends the DISCONNECT_REQ message to the server. Without saving temporarily held data to a remote SIM or waiting for DISCONNECT_RESP the client immediately returns to local SIM mode.

> <connState>(num)

> SAP connection state
> 0
> No SAP connection established.
> 1
> SAP connection ongoing, i.e. peers exchange messages.
> Notes

> • | If AT^SRSA with <dataForm> set to 1 (SAP) is given on the same serial multiplex channel as specified with parameter <muxChan> the SAP data transfer mode is entered immediately. Therefore no command response is issued by the TC65 in this case.

> • | If a TC65 acting as SAP client switches to a remote SIM card, it needs to load data from the SIM card first. The duration of the initial data load varies depending on the SIM card. Users should be aware that during this time SIM related AT commands (e.g. Phonebook or SMS commands) cannot be used. Therefore, it is recommended to activate the "^SSIM READY" which indicates when the SIM card is accessible. See AT^SSET for detail.

> • | If the TC65 is acting as SAP server and has released its SIM to a client it considers it as not accessible. Therefore AT commands which require SIM access will be rejected with "+CME ERROR: SIM not inserted".

> • | Parameters <muxChan>, <dataForm> and <beaconPer> are applicable for RSA activation only.