Siemens TC65 Terminal. Manual (Version: 02.000)

14. SIM related Commands

14.

SIM related Commands

The AT commands described in this chapter are related to the Subscriber Identity Module (SIM) connected to

TC65.

Note:

If using data from the SIM please bear in mind that the content of all Elementary Files is subject to change at any

moment!

This is true because the network can change the SIM's data in the background via the SIM Application Toolkit

(SAT) procedure "Data download to SIM". For a detailed description please refer to GSM 11.14, [26].

To get informed that changing Elementary Files has taken place the TA needs to hook to the SAT Proactive Com-

mand "REFRESH". To achieve this, the AT command interface of SAT, i.e. Remote-SAT, needs to be activated.

An overview is given at Chapter 16., SIM Application Toolkit (SAT) Commands, additional information is available

with the document "Remote-SAT User Guide" [6].

14.1

AT+CRSM Restricted SIM Access

AT+CRSM offers easy access of the Elementary Files on the SIM. Access to the SIM database is restricted to the

commands which are listed at <command>. However, additional SIM commands are available via AT^SXSM.

All parameters of AT+CRSM are used as specified by GSM 11.11 [25]. TC65 handles internally all required SIM

interface locking and file selection routines.

As response to the command, the TC65 sends the actual SIM information parameters and response data. Error

result code "+CME ERROR" may be returned if the command cannot be passed to the SIM, e.g. if the SIM is not

inserted. However, failure in the execution of the command in the SIM is reported in <sw1> and <sw2> param-

eters.

AT+CRSM requires PIN authentication. However, using <command> "READ BINARY" and <command> "READ

RECORD" is possible before PIN authentication and if the SIM is blocked (state after three failed PIN authenti-

cation attempts) to access the contents of the following Elementary Files:

EF Symbol

EF Name

EF ID (hex.)

EF ID (dec.)

EF_ICCID

ICC identification

2FE2

12258

EF_ELP

Extended language pref-

2F05

12037

erence

EF_LP

Language preference

6F05

28421

EF_SPN

Service provider name

6F46

28486

EF_AD

Administrative data

6FAD

28589

EF_Phase

Phase identification

6FAE

28590

EF_ECC

Emergency call codes

6FB7

28599

Please beware of possible changes to Elementary Files by the network at any time, refer Chapter 14., SIM

related Commands.

Syntax

Test Command

AT+CRSM=?

Response(s)

Page 400 of 567

14.1 AT+CRSM

Write Command

AT+CRSM=<command>[, <fileID>[, <P1>, <P2>, <P3>[, <data>]]]

Response(s)

+CRSM: <sw1>,<sw2>[,<response>]

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07

Parameter Description

<command>^(num)

SIM command number.

176

READ BINARY

178

READ RECORD

192

GET RESPONSE

214

UPDATE BINARY

220

UPDATE RECORD

242

STATUS

<fileID>^(num)

Identifier for an elementary data file on SIM, if used by <command>.

<P1>^(num)

Parameter to be passed on by the TC65 to the SIM.

0...255

<P2>^(num)

Parameter to be passed on by the TC65 to the SIM.

0...255

<P3>^(num)

Parameter to be passed on by the TC65 to the SIM.

0...255

<data>^(str)

Information which shall be written to the SIM (hexadecimal character format).

<sw1>^(num)

Status information from the SIM about the execution of the actual command. It is returned in both cases, on suc-

cessful or failed execution of the command.

0...255

Page 401 of 567

14.2 AT^SXSM

14.2

AT^SXSM Extended SIM Access

AT^SXSM extends AT+CRSM with additional SIM commands.

All parameters of AT^SXSM are used as specified by GSM 11.11 [25]. TC65 handles internally all required SIM

interface locking and file selection routines.

TC65 may return error result code "+CME ERROR" if the command cannot be passed to the SIM, e.g. if no SIM

is inserted. However, errors related to SIM action are reported in <sw1> and <sw2> parameters as defined in

GSM 11.11 [25].

Syntax

Test Command

AT^SXSM=?

Response(s)

Write Command

AT^SXSM=<command>[, <fileID>[, <P1>, <P2>, <P3>[, <data>]]]

Response(s)

^SXSM: <sw1>, <sw2>[,<response>]

ERROR

+CME ERROR: <err>

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

Parameter Description

<command>^(num)

136

RUN GSM ALGORITHM

Start the authentication mechanism and cipher key generation on the SIM. It

runs the algorithms A3 and A8 using a 16 byte random number and the sub-

scriber authentication key Ki, which is stored in the SIM.

<fileID>^(num)

Identifier for an elementary data file on SIM, if used by <command>.

<P1>^(num)

Parameter to be passed on by the TC65 to the SIM.

<P2>^(num)

Parameter to be passed on by the TC65 to the SIM.

<P3>^(num)

Parameter to be passed on by the TC65 to the SIM.

<data>^(str)

If <command>=136 (RUN GSM ALGORITHM):

16 byte random number.

Page 403 of 567

14.2 AT^SXSM

<sw1>^(num)

Status information from the SIM about the execution of the actual command. It is returned in both cases, on suc-

cessful or failed execution of the command.

0...255

<sw2>^(num)

Status information from the SIM about the execution of the actual command. It is returned in both cases, on suc-

cessful or failed execution of the command.

0...255

<response>^(str)

Response in case of a successful completion of the previously issued SIM command.

If <command>=136 (RUN GSM ALGORITHM):

TC65 returns SRES and cipher key Kc as calculated by the SIM.

Byte(s)

Description

Length

1 - 4

SRES - Signed RESponse

5 - 12

- Cipher Key

Example

Use <command>=136 (RUN GSM ALGORITHM) to obtain SRES and cipher key Kc values as calculated by the

SIM.

at^sxsm=136,,0,0,16,"0011223

Start SIM command "RUN GSM ALGORITHM" with 16 byte random

3445566778899AABBCCDDEEFF"

number.

^SXSM:

SRES (bytes 1-4) and Cypher Key Kc (bytes 5-12) values as returned

144,0,00112233445566778899AA

by the SIM.

Page 404 of 567

14.3 AT^SCKS

14.3

AT^SCKS Query SIM and Chip Card Holder Status

This command controls the SIM connection presentation mode and queries the connection status of the SIM and

the card holder tray of the TC65.

The query can be used for the locally attached and remote SIM's as well. For details regarding Remote SIM

Access refer to AT^SRSA.

Syntax

Test Command

AT^SCKS=?

Response(s)

^SCKS:(list of supported <mode>s)

Read Command

AT^SCKS?

Response(s)

^SCKS: <mode>, <SimStatus>

ERROR

+CME ERROR: <err>

Write Command

AT^SCKS=<mode>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Unsolicited Result Code

^SCKS: <SimStatus>

During startup, and if the TC65's SIM connection status has changed an unsolicited result code (URC) is issued.

Command Description

The read command returns the URC presentation mode and the status of the SIM card connection.

The write command enables or disables the presentation of URCs to report whether or not the SIM card is con-

nected.

If the ME is powered down or reset (AT+CFUN or AT^SMSO) the current presentation mode setting <mode> will

not be retained. Therefore the setting <mode>=1 needs to be restored after power on the TC65 or may be saved

in the user profile (AT&W).

Parameter Description

<mode>^{(num)(&W)(&V)}

0^(&F)

Suppress unsolicited result codes

Output unsolicited result codes

Page 405 of 567

14.3 AT^SCKS

<SimStatus>^(num)(&V)

Card holder tray removed or SIM connection error

SIM inserted(refer to note)

The SIM interface HW has been deactivated to prevent possible damage (e.g.

if a SIM with invalid or unsupported electrical specifications has been

detected).

The SIM interface can be reactivated only with a restart of the module, e.g. with

"AT+CFUN= n,1".

If the Remote SIM Access feature is activated (refer to AT^SRSA) and a SIM

card error occurs while accessing the remote SIM, the TC65 switches to its

local SIM, if any. If the SIM card error occurs while local SIM access, use of the

remote SIM is still possible.

Note

•

<SimStatus> reflects the status of the SIM and the card holder tray. Therefore if an empty SIM card tray is

inserted, two URCs will be presented, indicating the status 1 followed by 0, i.e. a SIM is inserted into the card

holder tray but no SIM connection could be established.

If Remote SIM Access switches back from remote to local SIM, SCKS indicates the status 1 regardless of the

real SIM status. If no SIM is inserted this is followed by a second SCKS URC indicating 0.

Example

AT^SCKS=1

Activates the presentation of unsolicited result codes

Now, after inserting an empty card tray the following URCs appear:

^SCKS: 1

Tray connected

^SCKS: 0

No SIM card found

Page 406 of 567

14.4 AT^SSET

14.4

AT^SSET Indicate SIM data ready

After power-up and personalization (PIN entry if required) the ME starts reading data from SIM. The AT^SSET

command controls the presentation of the "^SSIM READY" URC which indicates, on the corresponding serial

channel, when the ME has finished reading SIM data. See Section 23.1, Restricted access to SIM data after SIM

PIN authentication for further detail.

Syntax

Test Command

AT^SSET=?

Response(s)

^SSET:(list of supported <n>s)

Read Command

AT^SSET?

Response(s)

^SSET: <n>

ERROR

+CME ERROR: <err>

Write Command

AT^SSET=[<n>]

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Unsolicited Result Code

^SSIM READY

The URC acknowledges to the user that SIM data is accessible.

Parameter Description

<n>^{(num)(&W)(&V)}

URC presentation mode

0^(&F)

Disable URC "^SSIM READY" indication.

Enable URC "^SSIM READY" indication.

Page 407 of 567

15. Remote SIM Access (RSA) Commands

15.

Remote SIM Access (RSA) Commands

This chapter contains AT commands and responses related to the Remote SIM Access (RSA) feature of TC65.

RSA allows TC65 to access and use a remote SIM card via its serial interface in addition to resp. instead of the

SIM that is locally attached via the dedicated lines on the interface connector.

The necessary protocols and procedures are implemented following the «SIM Access Profile (SAP) Interopera-

bility Specification» [15]. As stated there it is possible for a SAP client to use a SIM card in an external device

connected via a wireless link. The external device can either be a mobile phone, a PDA or any other mobile

equipment that may be used as SIM card holder. The SIM Access Profile builds on the interface between mobile

equipment and the SIM card (refer to the «Specification of the Subscriber Identity Module (GSM 11.11)» [25]).

For further details contact the Wireless Modules Application Engineering Department at Siemens AG.

Figure 15.1, Basic Remote SIM Access Usage Scenario via Bluetooth illustrates an access scenario via Blue-

tooth:

Figure 15.1: Basic Remote SIM Access Usage Scenario via Bluetooth

Since the TC65 itself - acting as SAP client - does not control the Bluetooth wireless link, the communication with

the remote SIM needs to be routed via an external customer application. The external application establishes

and controls the Bluetooth connection. It maps data received over a serial interface channel to data transferred

over a Bluetooth interface and vice versa.

Figure 15.2, Basic Remote SIM Access Usage Scenario via RS232 illustrates an alternative access scenario via

a serial RS232 interface. Instead of Bluetooth it is possible for an external customer application to use a serial

RS232 interface in mapping data for the remote SIM in an external device. In this case an ASCII coded string

format (Siemens' XSAP) is used instead of the binary SAP data format employed for Bluetooth.

Figure 15.2: Basic Remote SIM Access Usage Scenario via RS232

Page 410 of 567

In general, the ME can operate either as SAP server or as SAP client. A brief description of the configuration is

given below.

• SAP server

The SIM Access Server has direct (galvanic) access to a SIM. It acts as a SIM card reader, which assists the

client in accessing and controlling this SIM via the serial link. Typical examples of a server are SIM card

reader or mobile phones.

After SAP client activation (see (1) in Figure 15.3, SIM usage states of SAP server) the ME starts sending the

SAP message CONNECTION_REQ. However, the client will still use its local SIM card until a server

responds and the parameter negotiation with subsequent ATR access has been accomplished successfully.

Figure 15.3: SIM usage states of SAP server

Page 411 of 567

• SAP client

The SIM Access Client is connected via a serial link to the SIM Access Server. The client accesses and con-

trols the SIM inside the Server via the serial link. Typical examples of a server are a simple SIM card holder

or a mobile phone. A typical example of a client is an ME that uses a remote SIM card in the server for a

connection to the cellular network. With the additional AT Commands it is possible to switch the TC65 to use

an external SIM instead of the physically attached (local) SIM during runtime.

After SAP server activation (see (1) in Figure 15.4, SIM usage states of SAP client) the ME waits for the SAP

message CONNECTION_REQ. The server will use its local SIM until the parameter negotiation has been

accomplished successfully.

Figure 15.4: SIM usage states of SAP client

Page 412 of 567

15.1 AT^SRSA

15.1

AT^SRSA Remote SIM Access Activation

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)

Read Command

AT^SRSA?

Response(s)

[^SRSA:<devId>, <sapRole>, <connState>, <muxChan>, <dataForm>, <beaconPer>]

Write Command

AT^SRSA=<devId>, <sapRole>[, <muxChan>[, <dataForm>[, <beaconPer>[, <discType>]]]]

Response(s)

^SRSA:<actResult>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

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.

Command Description

The read command can be used to request the current RSA settings. Every line outputs an RSA connection, if

any.

The write command allows to control the TC65's SIM usage scheme along with the related configuration param-

eters.

Parameter Description

<actResult>^(num)

Activation result

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 initi-

ated in the following cases:

Error unspecified.

Error activation command is busy.

Error activation started with serial multiplex mode is off.

Error activation started on invalid serial multiplex channel.

Error device Id is already known.

Page 413 of 567

15.1 AT^SRSA

Error SAP mode is already active.

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>.

SAP server

Enable Remote SIM Access usage whereas the TC65 acts as SIM Access

server. It waits for a SAP message CONNECT_REQ to deregister from the net-

work and then acts as a SIM card reader. However, under the following condi-

tions the TC65 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.

SAP client

Enable Remote SIM Access usage whereas the TC65 acts as SIM Access cli-

ent. It starts sending CONNECT_REQ messages periodically, refer to param-

eter <beaconPer>. Under the same conditions listed above the TC65 will

neither send CONNECT_REQ messages nor a SIM switch will take place.

The client deregisters from the network if a local SIM was used before and

switches to a remote SIM when

• SAP message CONNECT_RESP is received,

• SAP message STATUS_IND is received,

• SAP message ATR_RESP is received after the appropriate request was

issued by the client.

<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 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 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 supplied channel on which command is issued is

used.

Page 414 of 567

15.1 AT^SRSA

<dataForm>^(num)

SAP message data format

[0]

XSAP ATC/URC format

SAP messages are translated into ASCII coded strings and transmitted as

parameters of AT command AT^SRSM and URC "^SRSM". If 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 chan-

nel.

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 conver-

sation. As a result less data will be transferred and the SIM communication will

be faster.

<beaconPer>^(num)

Beacon period

Determines the period in seconds between sending the CONNECT_REQ messages. A 0 value leads to a one-

time connection request. This parameter is applicable for SAP client activation only.

0...[6]...100

<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 rec-

ommended to query call states before RSA deactivation.

Hold SAP role

SAP connection is going to be disabled. The TC65 remains in SAP mode and

is ready to (re)establish a SAP connection. If a SAP connection was ongoing

an URC "^SRSA:

<devId>,

<sapRole>,

<connState>" with

<connState>= 0 is issued.

• A server exclusively sends a SAP message DISCONNECT_IND (type

"Graceful") to the client.

• A client saves SIM data which is temporarily held in TC65's memory to the

remote SIM and sends SAP message DISCONNECT_REQ 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. An URC

"^SRSA: <devId>, <sapRole>, <connState>" with <sapRole>= 0 and

<connState>= 0 is issued.

• A server sends a SAP message DISCONNECT_IND (type "Immediate") to

the client and returns to local SIM mode immediately. SIM data which is

temporarily held in client's memory would be lost.

• A client exclusively sends SAP message DISCONNECT_REQ to the

server. Without saving temporary held data to a remote SIM or waiting for

DISCONNECT_RESP the client returns to local SIM mode immediately.

Page 415 of 567

15.1 AT^SRSA

<connState>^(num)

SAP connection state

No SAP connection established.

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 recom-

mended 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. There-

fore 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.

Page 416 of 567

15.2 AT^SRSM

15.2

AT^SRSM Remote SIM Access Message

This command is used to transfer SAP messages between devices acting as SAP server and client. It is appli-

cable for XSAP data format only, for details please refer to parameter <dataForm> of command AT^SRSA.

The write command transports SAP messages into an ME acting as SAP server or client.

Syntax

Test Command

AT^SRSM=?

Response(s)

Write Command

AT^SRSM=<RsaDevId>, <RsaMsgId>[, <RsaMsgData>[, <RsaMsgLen>[, <RsaMsgRc>]]]

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Unsolicited Result Code

^SRSM: <RsaDevId>, <RsaMsgId>[, <RsaMsgData>[, <RsaMsgLen>[, <RsaMsgRc>]]]

This URC is issued by an ME acting as SAP server or client to transfer SAP message data.

Parameter Description

<RsaDevId>^(num)

RSA device identification

Number assigned by the host on RSA activation via AT^SRSA, parameter <devId>.

<RsaMsgId>^(num)

RSA message identification

For details refer to Section 15.2.1, SAP Request Message Parameter and Section 15.2.2, SAP Response Mes-

sage Parameter.

<RsaMsgData>^(str)

RSA message data

For details refer to Section 15.2.1, SAP Request Message Parameter and Section 15.2.2, SAP Response Mes-

sage Parameter.

<RsaMsgLen>^(num)

RSA message data length

For details refer to Section 15.2.1, SAP Request Message Parameter and Section 15.2.2, SAP Response Mes-

sage Parameter.

<RsaMsgRc>^(num)

RSA message result code

For details refer to Section 15.2.1, SAP Request Message Parameter and Section 15.2.2, SAP Response Mes-

sage Parameter.

Page 417 of 567

15.2 AT^SRSM

<MaxMsgSize>^(num)

SAP parameter MaxMsgSize

Handling of this parameter is as follows:

• If the TC65 is acting as SAP client the requested value of <MaxMsgSize> is 300. While SAP connection

setup this value may be negotiated with the server to the minimal value 274, which is calculated by 256 data

bytes as part of a TRANSFER_APDU_RESP message plus a 16 byte SAP header and two status bytes. If

the server does not accept this value range no SAP connection will be established.

• If the TC65 is acting as SAP server it requires that a <MaxMsgSize> value of 276 will be accepted by a

connected client.

<ConnStatus>^(num)

SAP parameter Connection Status

<DiscType>^(num)

SAP parameter Disconnection Type

<CmdApdu>^(str)

SAP parameter Command APDU or Command APDU7816

<CmdApduLen>^(num)

SAP parameter Command APDU length

<RspApdu>^(str)

SAP parameter Response APDU

<RspApduLen>^(num)

SAP parameter Response APDU length

<ATR>^(str)

SAP parameter ATR

<AtrLen>^(num)

SAP parameter ATR length

<ResCode>^(num)

SAP parameter Result Code

<CardRdStatus>^(num)

SAP parameter Card Reader Status

<StatusChange>^(num)

SAP parameter Status Change

<TransportProtocol>^(num)

SAP parameter Transport Protocol

Page 418 of 567

15.2 AT^SRSM

Example

The following example shows how to establish a RSA connection.

AT+CMEE=2

Switch on verbose error messages

(use

AT+CMEE=1 with production code)

AT+CREG=1

Switch on network registration URC

AT^SSET=1

Switch on SIM data ready URC

AT^SCKS=1

Switch on SIM status URC

AT^SM20=0

Switch on immediate return after call attempt via

ATD.

AT^SRSA?

Does the ME support RSA and is a SAP connection

established?

AT^SRSA=2,2,3,0

^SRSA:0

Initialization of RSA mode using XSAP data format.

^SRSA:2,2,0

URC indicating SAP client start without ongoing con-

nection.

ME now starts sending SAP message

CONNECTION_REQ on dedicated RSA channel.

If a SAP server has responded and offers its SIM:

^SRSA:2,2,1

URC indicating a connection with SAP server

^SCKS:0

URC indicating the loss of (local) SIM

+CREG:0

URC indicating the deregistration from network

because of loss of SIM.

^SCKS:1

URC indicating the activation of remote SIM

ME now starts reading data from the SIM

Does the new SIM require a PIN?

AT+CPIN?

Request PIN status

+CPIN: SIM PIN

PIN needs to be entered

+CME ERROR: SIM blocked

+CME ERROR: SIM busy

Retry if the ME returns these messages

AT+CPIN=1234

+CREG:2

+CREG:1

URC indicating network registration.

^SSIM READY

URC indicating that SIM data is read out.

ATD491777777777777

Make a call.

15.2.1

SAP Request Message Parameter

The following table shows all SAP request message parameter that are used in two cases:

• An URC "^SRSM" is issued by an ME acting as SAP client, then

• an AT^SRSM write command transfers its data into an ME acting as SAP server.

SAP Request Message Parameter Mapping:

Page 419 of 567

15.2 AT^SRSM

SAP Message Name

SAP parameter mapping to AT^SRSA parame-

ters

<RsaMsgId> [,<RsaMsgData> [,<RsaMs-

gLen> [,<RsaMsgRc>]]]

CONNECT_REQ

0,,<MaxMsgSize>

DISCONNECT_REQ

TRANSFER_APDU_REQ

5,<CmdApdu>,<CmdApduLen>

TRANSFER_ATR_REQ

POWER_SIM_OFF_REQ

POWER_SIM_ON_REQ

RESET_SIM_REQ

TRANSFER_CARD_READER _STATUS_REQ

SET_TRANSPORT_PROTOCOL_REQ

19,<TransportProtocol>

15.2.2

SAP Response Message Parameter

The following table shows all SAP response and indication message parameters that are used in two cases:

• An URC "^SRSM" is issued by an ME acting as SAP server, then

• an AT^SRSM write command transfers its data into an ME acting as SAP client.

SAP Response Message Parameter Mapping:

SAP Message Name

SAP parameter mapping to AT^SRSA parame-

ters

<RsaMsgId> [,<RsaMsgData> [,<RsaMs-

gLen> [,<RsaMsgRc>]]]

CONNECT_RESP

1,,<MaxMsgSize>,<ConnStatus>

DISCONNECT_RESP

DISCONNECT_IND

4,,,<DiscType>

TRANSFER_APDU_RESP

6,<RspApdu>,<RspApduLen>,<ResCode>

TRANSFER_ATR_RESP

8,<ATR>,<AtrLen>,<ResCode>

POWER_SIM_OFF_RESP

10,,,<ResCode>

POWER_SIM_ON_RESP

12,,,<ResCode>

RESET_SIM_RESP

14,,,<ResCode>

TRANSFER_CARD_READER

16,,<CardRdStatus>,<ResCode>

_STATUS_RESP

STATUS_IND

17,,,<StatusChange>

ERROR_RESP

SET_TRANSPORT_PROTOCOL_RESP

20,,,<ResCode>

Page 420 of 567

15.3 Related AT Commands

15.3

Related AT Commands

The following commands might be of interest while using the RSA feature. For a detailed description of all com-

mands given below refer to:

• AT^SCKS

This AT command is used to check the current status of the SIM (local or remote).

• AT^SSET

After power on and personalization (PIN entry if required), the ME starts reading data from the SIM. Please

keep in mind that after entering the PIN, even after the TE sends "OK", subsequent commands need access

to data stored on the SIM may be blocked for up to 30 seconds. It may take even longer to access the remote

SIM depending on the establishment of the RSA communication link. Therefore, it is recommended that the

AT^SSET command, which controlls the "^SSIM READY" URC indicating that the SIM data reading process

has been completed, be used. Afterwards all commands regarding to SIM data files can be used, e.g. the

SMS and phonebook commands.

• AT+CLCC

This command is recommended for querying the state of current calls. A list of all active calls will be returned.

This is especially important if the SAP connection should be terminated using

AT^SRSA=<devId>,<sapRole>,,,,<discType>; where <sapRole> is set to 0 and <discType> set to 1.

All calls or active GPRS contexts established via remote SIM will be terminated and the ME will use the locally

attached SIM card.

• SIM data storage

It is recommended that all user relevant data are stored on the SIM only. For example, added phonebook and

SMS entries in the client's storage are not accessible after a RSA connection.

15.3.1

Establishing an RSA connection in a PC environment

To set up an RSA connection in a PC environment an appropriate PC application is needed. For test and eval-

uation purposes and as exemplary implementation guidance Siemens offers a PC application called "Com-

Bridge" as MS Windows executable and source code. For ordering details contact your local Siemens dealer or

visit the Siemens website. "ComBridge" provides basic features to generate a car application environment, e.g.

mapping of the SAP communication between a SAP server and client. To support the different RSA coding

modes (SAP and XSAP) and to transfer data between the two COM ports, the PC application uses two variable

modules (filters):

• XSAP filter Translating the "^SRSM" URCs into AT command "AT^SRSM"

• SAP filter Transparently transfer binary SAP messages. The generic "1:1" filter ("software null modem") can

also be used for this purpose, but communication might be slower since it performs bytewise data transfer.

15.3.2

Bluetooth scenario (SAP)

A connection between a cellular engine operating as a SAP client and an ME that supports Bluetooth and SIM

Access profile requires:

a) System requirements

• Windows 2000, Windows XP (or later) installed

• USB Bluetooth dongle. It is recommended to use the Fujitsu-Siemens product with the "PlugFree" Bluetooth

driver. This driver allows connections to Bluetooth profiles which are not yet specified by the SIG, e.g. SAP.

b) Installation procedure

• After installing the USB Bluetooth dongle and the "PlugFree" driver software, the Bluetooth profiles are acces-

sible via their own virtual COM port.

• If the WinMux driver has been installed another three virtual channels (mapped to additional COM ports) are

available. The physical Multiplexer COM port is connected to the cellular engine.

Page 421 of 567

15.3 Related AT Commands

• Start the Bluetooth connection using the driver provided by the USB Bluetooth dongle.

• Through "ComBridge", one virtual COM port supplied by "WinMux" is connected to the SAP COM port of

"PlugFree". This establishes an direct communication link between the cellular engine and the cellular phone.

However, AT commands can still be entered to the cellular engine via the remaining multiplexer channels.

• Select the "ComBridge" SAP filter.

• Press the "ComBridge-Start" button to connect both MEs.

• Start the SAP client using the AT command "AT^SRSA=2,2,3,1", if multiplexer channel 3 is used.

15.3.3

Serial Interface Scenario (XSAP)

This example describes the connection of two cellular engines. It is recommended that the instructions be fol-

lowed in the order that they are presented:

• Install two WinMux drivers on the PC and connect each ME to the physical port of a Multiplexer.

• Connect the PC application "ComBridge" to one virtual COM port of each Multiplexer. This establishes an

communication link between the two cellular engines. Bear in mind that AT commands can still be issued on

both cellular engines using the remaining serial channels.

• Select the "ComBridge" XSAP filter.

• Open the XSAP "Config Filter" menu and deactivate the "Startup - Send Initialization" and the "Shutdown -

Switch back to local SIM" tags. However, the appropriate device IDs need to be entered in the "Startup"

frame.

• Press the "ComBridge - start" button to connect both MEs.

• Start the SAP client via AT command "AT^SRSA=2,2,3,0", if multiplexer channel 3 is used.

• Start the SAP server via AT command "AT^SRSA=1,1,3,0", if multiplexer channel 3 is used.

Page 422 of 567

16. SIM Application Toolkit (SAT) Commands

16.

SIM Application Toolkit (SAT) Commands

This chapter offers a brief reference of commands and responses related to the TC65's SIM Application Toolkit

(SAT) implementation. Detailed information is available with the document "Remote-SAT User Guide" [6]. Please

contact the Wireless Modules Application Engineering Department at Siemens AG for details.

ETSI specification GSM 11.14 [26] defines SAT in detail.

SAT allows for the execution of applications provided by a Subsciber Identity Module (SIM). Usually SIM cards

are used for storing GSM network provider and user specific data, e.g. phonebook entries and Short Messages

(SMS). However, a SIM card may also hold a SIM Application.

Since the TC65 has SAT functionality it is able to execute the commands issued by applications implemented

on a network provider specific SIM card.

Two groups of commands are used between the ME and the SIM Application:

• Proactive Commands are issued to the TC65's SAT from the SIM Application, such as "DISPLAY TEXT".

• Envelope Commands are responded to the SIM Application from the TC65, such as "MENU SELECTION".

16.1

AT^SSTA SAT Interface Activation

Syntax

Test Command

AT^SSTA=?

Response(s)

^SSTA:(list of supported <state>s), (list of supported <Alphabet>s)

Read Command

AT^SSTA?

Response(s)

^SSTA: <state>, <Alphabet>, <allowedInstance>, <SatProfile>

Write Command

AT^SSTA=<mode>[, <Alphabet>]

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Command Description

The read command can be used to request the current operating status and the used alphabet of the Remote-

SAT interface.

The write command is used to activate the AT command interface of the SIM Application Toolkit in the TC65 and

needs to be issued after every power on. However, removing and inserting the SIM does not affect the activation

status.

SAT commands which are not using the AT interface (non MMI related SAT commands , e.g. PROVIDE LOCAL

INFORMATION) could be executed without activating Remote-SAT.

Page 423 of 567

16.1 AT^SSTA

Parameter Description

<state>^(num)

TC65 Remote-SAT interface states

RESET

OFF

IDLE

PAC

WAIT

<Alphabet>^(num)

GSM character set

Input of a character requests one byte, e.g. "Y".

UCS2

To display the 16 bit value of characters represented in UCS2 alphabet a 4 byte

string is required, e.g. "0059" is coding the character "Y". For details please

refer to ISO/IEC 10646.

<allowedInstance>^(num)

SAT is already used on another instance (logical channel in case of the multi-

plex protocol). Only test and read commands can be used.

SAT may be started on this instance via the write version of this command.

<SatProfile>^(str)

SAT profile according to GSM 11.14 [26].

The profile tells the SIM Application which features (e.g. proactive commands) are supported by the SIM Appli-

cation Toolkit implementation of the TC65.

<mode>^(num)

Activate Remote-SAT

Note

• To limit the time Remote-SAT is kept in states PAC or WAIT any ongoing (but unanswered) Proactive Com-

mand is automatically aborted after 10 minutes with Terminal Response "ME currently unable to process com-

mand" or "No response from user" if applicable. An URC "Terminate Proactive Command" will be send to the

external application in this case, too.

Page 424 of 567

16.2 ^SSTN

16.2

^SSTN SAT Notification

Unsolicited Result Codes

URC 1

Proactive Command notification

^SSTN: <cmdType>

Every time the SIM Application issues a Proactive Command, via the ME, the TA will receive a notification.

This indicates the type of Proactive Command issued.

AT^SSTGI must then be used by the TA to request the parameters of the Proactive Command from the ME.

Upon receiving the ^SSTGI response from the ME, the TA must send AT^SSTR to confirm the execution of

the Proactive Command and provide any required user response, e.g. a selected menu item.

URC 2

Terminate Proactive Command notification

^SSTN: <cmdTerminateValue>

When the SIM application has issued a Proactive Command to the ME, it is possible that this command will

be terminated later. URC "^SSTN" is sent with a different Proactive Command type number (added terminate

offset 100) to indicate the termination of the specified command.

The state changes to idle. Therefore the TA should avoid sending any further commands related to the ter-

minated Proactive Command, e.g. AT^SSTGI or AT^SSTR.

URC 3

Notification that SIM Application has returned to main menu

^SSTN: 254

Notification to the TA when the SIM Application has finished a command cycle and again enters its main

menue, which was transferred with an URC "^SSTN: 37" (SET UP MENU) at start up.

This URC should be used to open this menue on the sreen.

The TA does not need to respond directly, i.e. AT^SSTR is not required.

URC 4

SIM reset notification

^SSTN: 255

Notification to the TA if a Proactive Command "REFRESH - SIM Reset" has been issued by the SIM Applica-

tion, please refer to AT^SSTGI.

This URC should be used to set the TAs application to its initial state since the SIM Application will start from

the beginning, too.

The TA does not need to respond directly, i.e. related AT^SSTGI and AT^SSTR are neither required nor

allowed.

Since the ME is still busy on SIM access the ME may respond with "+CME ERROR: SIM blocked" or "+CME

ERROR: SIM busy" on following PIN required AT Commands for a while. Then TA shall retry until the ME

responds with "OK". The time needed for this process depends on the SIM and may take more than 10 sec-

onds.

Parameter Description

<cmdType>^(num)

Proactive Command number

<cmdTerminateValue>^(num)

Defined as <cmdType> + terminate offset. The terminate offset equals 100.

Page 425 of 567

16.3 AT^SSTGI

16.3

AT^SSTGI SAT Get Information

Regularly this command is used upon receipt of an URC "^SSTN" to request the parameters of the Proactive

Command.

Then the TA is expected to acknowledge the AT^SSTGI response with AT^SSTR to confirm that the Proactive

Command has been executed. AT^SSTR will also provide any user information, e.g. a selected menu item.

The Proactive Command type value specifies to which "^SSTN" the command is related.

Syntax

Test Command

AT^SSTGI=?

Response(s)

^SSTGI:(list of supported <state>s), (list of supported <cmdType>s)

Read Command

AT^SSTGI?

Response(s)

^SSTGI: <state>, <cmdType>

Write Command

AT^SSTGI=<cmdType>

Response(s)

ERROR

+CME ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<state>^(num)

TC65 Remote-SAT interface states

RESET

OFF

IDLE

PAC

WAIT

<cmdType>^(num)

Related Proactive Command

Page 426 of 567

16.4 AT^SSTR

16.4

AT^SSTR SAT Response

The TA is expected to acknowledge the AT^SSTGI response with AT^SSTR to confirm that the Proactive Com-

mand has been executed. AT^SSTR will also provide any user information, e.g. a selected menu item.

Syntax

Test Command

AT^SSTR=?

Response(s)

^SSTR:(list of supported <state>s), (list of supported <cmdType>s)

Read Command

AT^SSTR?

Response(s)

^SSTR: <state>, <cmdType>

Write Command

AT^SSTR=<cmdType>, <status>[, <inputNumber>][, <inputString>]

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<state>^(num)

TC65 Remote-SAT interface states

RESET

OFF

IDLE

PAC

WAIT

<cmdType>^(num)

Number related to Proactive Command or event type according to GSM 11.14 [26].

<status>^(num)

Command status return regarding the type of action that has taken place, e.g. action performed by the user.

Values are in accordance with GSM 11.14 [26].

<inputNumber>^(num)

Response number entered by user

<inputString>^(str)

Response string entered by user

Page 427 of 567

17. Phonebook Commands

17.

Phonebook Commands

The AT commands described in this chapter allow the external application to access the phonebooks located in

the TC65's memory or on the attached Subscriber Identity Module (SIM).

17.1

Sort Order for Phonebooks

Due to the support of UCS2 for the <text> part of phonebook entries, the sort order for phonebook records fol-

lows the algorithm published as Unicode Technical Standard #10, "Unicode Collation Algorithm".

A memory-optimized version of the proposed collation tables "[AllKeys]" from Unicode Technical Standard #10

is used in order to determine collation weights for Code points between 0000 and 06FF, and composed keys are

used for Code points from ranges 0700 to 33FF, A000 to D7FF and E000 to FFFD. Code Points not referenced

in these tables will be assigned a default collation weight with their unicode value as level 1 weight. Decomposi-

tion is not supported.

Phonebook entries whose names contain only characters from the GSM07.07 default alphabet are converted

internally into their UCS2 equivalents in order to achieve consistent sorting results.

For the user, this means that:

• Punctuation marks and other non-alphabetical characters from the common latin-based character sets, and

from the standard GSM character set, will be sorted before any alphabetical characters. The ordering in which

these marks appear as compared to other non-alphabetical characters from the same group is determined

by their collation weights and does not reflect their code values in the UCS2 or GSM alphabet tables above.

Please refer to www.unicode.org for detail.

• Alphabetical characters from the common latin-based character sets, and from the standard GSM character

set, will be sorted according to their underlying base characters, plus the collation weights of their accent

signs.

• Only collation levels 1 and 2 are regarded, so sorting is not case-sensitive.

Example: the european letters "Å" (GSM 0EH, UCS2 00C5h), "æ" (GSM 1DH, UCS2 00E6h), "ç" (GSM09h,

UCS2 00E7h), "a" (GSM 61H, UCS2 0061h ) and "b" (GSM 62H, UCS2 0062h) will be sorted in order "a", "Å",

"æ" "b","ç" although their numerical values in GSM and UCS2 suggest a different ordering.

Reference(s)

Unicode Technical Standard #10,"Unicode

Collation Algorithm"

Page 428 of 567

17.2 AT+CNUM

17.2

AT+CNUM Read own numbers

AT+CNUM returns the subscribers own number(s) from the SIM.

Syntax

Test Command

AT+CNUM=?

Response(s)

Exec Command

AT+CNUM

Response(s)

[+CNUM: [<alpha>], <number>, <type>]

[+CNUM: ... ]

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.07

Parameter Description

<alpha>^(str)

Optional alphanumeric string associated with <number>.

<number>^(str)

Phone number in format specified by <type>.

<type>^(str)

Type of address octet, see also: AT+CPBR <type>.

Note

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Page 429 of 567

17.3 AT+CPBR

17.3

AT+CPBR Read from Phonebook

AT+CPBR serves to read one or more entries from the phonebook selected with AT command AT+CPBS.

The AT+CPBR test command returns the location range supported by the current phonebook storage, the maxi-

mum length of <number> field and the maximum length of <text> field.

Note: Length information may not be available while SIM storage is selected. If storage does not offer format

information, the format list contains empty parenthesizes.

The AT+CPBR write command determines the phonebook entry to be displayed with <location1> or a location

range from

<location1> to <location2>. Hence, if no <location2>

is given only the entry at

<location1> will be displayed.

If no entries are found at the selected location "OK" will be returned.

Syntax

Test Command

AT+CPBR=?

Response(s)

+CPBR: (1-<maxloc>), <nlength>, <tlength>

+CME ERROR

Write Command

AT+CPBR=<location1>[, <location2>]

Response(s)

[+CPBR: <location1>, <number>, <type>, <text>]

[+CPBR: <location2>, <number>, <type>, <text>]

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1

MUX2 MUX3 Charge

Last

GSM 07.07, GSM 11.11

Parameter Description

<location1>^(num)

The first (lowest) location number within phonebook memory where to start reading. The maximum range sup-

ported by the current phonebook is given in the test command response.

<location1> exceeds the upper bound <maxloc> (as indicated by the test command), command will

respond with "+CME ERROR: invalid index".

<location2>^(num)

The last (highest) location number within phonebook memory where to stop reading. The maximum range sup-

ported by the current phonebook is given in the test command response.

If both <location1> and <location2> are in the range indicated by the test command parameter <max-

loc>, the list of entries will be output and terminated with "OK".

If <location2> exceeds the range indicated by the test command parameter <maxloc>, the list of entries will

be output but terminated with "+CME ERROR: invalid index".

Note: The maximum value of <location2> is 255, regardless of the phonebook type and its range indicated

by <maxloc>. If a value greater than 255 is used the query returns no phonebook records, and only "+CME

ERROR: invalid index" is shown.

<number>^(str)

Phone number in format specified by <type>, it may be an empty string.

Page 430 of 567

17.3 AT+CPBR

<type>^(num)

Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi).

Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending

on the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> of

AT+CPBW.

Possible values are:

145

Dialing string <number> includes international access code character '+'

161

National number. Network support of this type is optional.

209

Dialing string <number> has been saved as ASCII string and includes non-

digit characters other than "*", "#" or "+". Note that phonebook entries saved

with this type cannot be dialed.

255

Dialing string <number> is a command to control a Supplementary Service,

i.e. "*", "#" codes are contained. Network support of this type is optional.

129

Otherwise

<text>^(str)(+CSCS)

Text assigned to a phone number. The maximum length for this parameter is given with test command response

parameter <tlength>.

If using an ASCII terminal characters which are coded differently in ASCII and GSM have to be entered via

escape sequences as described in Section 1.5, Supported character sets.

<maxloc>^(num)

Maximum location number for the currently selected storage. For phonebooks located on the SIM this value

depends on the SIM card type.

<nlength>^(num)

Maximum length of phone number for "normal" locations. Depending on the storage a limited number of loca-

tions with extended memory is available per phonebook. These locations allow storing numbers with twice the

standard length, which is 2*<nlength> digits for normal numbers, but only <nlength> digits for numbers

saved with <type>=209.

<tlength>^(num)

Maximum length of <text> assigned to the telephone number. The value indicated by the test command is

given in octets. If <text> is given as GSM characters each character corresponds to one octet. If the <text>

string is given in UCS2, the maximum number of characters depends on the coding scheme used for the alpha

field of the SIM according to GSM 11.11, Annex B [25]. In the worst case the number of UCS2 characters is at

least one less than half the number of GSM characters.

Note

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Page 431 of 567

17.4 AT+CPBS

17.4

AT+CPBS Select phonebook memory storage

AT+CPBS selects the active phonebook storage, i.e. the phonebook storage that all subsequent phonebook com-

mands will be operating on.

The read command returns the currently selected <storage>, the number of <used> entries and the <total>

number of entries available for this storage. The test command returns all supported <storage>s as compound

value.

Syntax

Test Command

AT+CPBS=?

Response(s)

+CPBS: (list of supported <storage>s)

+CME ERROR

Read Command

AT+CPBS?

Response(s)

+CPBS: <storage>, <used>, <total>

+CME ERROR

Write Command

AT+CPBS=<storage>

Response(s)

+CME ERROR:

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM07.07

Parameter Description

<storage>^(str)

"FD"

Fixed dialing phonebook

Capacity: depending on SIM card

Location: SIM

"SM"^(&F)

SIM phonebook

Capacity: depending on SIM card

Location: SIM

"ON"

MSISDN list

Capacity: depending on SIM card

Location: SIM

"ME"

Mobile Equipment Phonebook

Capacity: max. 250 entries

Location: ME

"LD"

Last number dialed phonebook. Stores all voice call numbers dialed with ATD,

but no data call numbers.

Capacity: max. 10 entries

Location: depending on SIM this phonebook may reside partly or completely in

AT+CPBW command is not applicable to this storage. The LD list can be deleted

with AT^SDLD or with AT^SPBD.

Page 433 of 567

17.4 AT+CPBS

"MC"

Missed (unanswered received) calls list

Capacity: max. 10 entries

Location: ME

AT+CPBW command is not applicable to this storage. The MC list can be

deleted with AT^SPBD.

"RC"

Received calls list

Capacity: max. 10 entries

Location: ME

AT+CPBW command is not applicable to this storage. The RC list can be

deleted with AT^SPBD.

<used>^(num)

Value indicating the number of used locations in selected memory storage.

<total>^(num)

Value indicating the maximum number of locations allowed in the selected memory storage.

Notes

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

• If the SIM card is changed, all records of the "MC", "RC" and "LD" phonebooks stored on the ME will be

deleted automatically. If the same SIM is removed and reinserted, no automatic deletion is performed. Calls

made after last switch-on will be lost from "MC", "RC" and "LD" phonebook, if the SIM is removed and rein-

serted during normal operation.

Page 434 of 567

17.5 AT+CPBW

17.5

AT+CPBW Write into Phonebook

The AT+CPBW write command can be used to create, edit and delete a phonebook entry at a <location> of

the active storage selected with AT+CPBS.

If <storage>="FD" (SIM fixed dialing numbers) is selected, PIN2 authentication has to be performed prior to

any write access.

The AT+CPBW test command returns the location range supported by the current storage, the maximum length

of the <number> field, the range of supported <type> values and the maximum length of the <text> field.

Note: The length may not be available while SIM storage is selected. If storage does not offer format information,

the format list contains empty parenthesizes.

Syntax

Test Command

AT+CPBW=?

Response(s)

+CPBW: (1-<maxloc>), <nlength>, (list of supported <type>s), <tlength>

ERROR

+CME ERROR

Write Command

AT+CPBW=[<location>][, <number>[[, <type>][, <text>]]]

Response(s)

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

GSM 07.07, GSM 04.08

Parameter Description

<location>^(num)

Location number within phonebook memory. The maximum range supported by each storage type is indicated

in the test command response. If <location> is not given, the first free entry will be used.

If <location> is given as the only parameter, the phonebook entry specified by <location> is deleted.

<number>^(str)

Phone number in format specified by <type>. Parameter must be present, although it may be an empty string.

Alphabetic characters are not permitted. <number> may contain dialstring modifiers "*", "#" or "+".

If other printable non-alphabetic characters are used the entry needs to be saved with <type>=209. Otherwise,

if <type>=209 is not used any non-digit characters other than "*", "#" or "+" will be removed from the string and

only accepted modifiers from the GSM alphabet will be saved.

A <number> saved with <type>=209 requires double memory. In order to fit into a standard location, the num-

ber needs to be reduced to a maximum length of <nlength>/2, including all digits and dial string modifiers.

Extended locations may be used as stated below for <nlength>.

Page 435 of 567

17.5 AT+CPBW

<type>^(num)

Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi).

Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending

on the network, not always possible (refer GSM 04.08 subclause 10.5.4.7 for details).

If <type> is not specified the unknown <type>=129 is used. If <number> contains a leading "+" <type>=145

(international) is used.

Supported values are:

145

Dialing string <number> includes international access code character "+"

161

National number. The network support for this type is optional.

209

Dialing string <number> will be saved as ASCII string.

This is the default value, if <type> is not specified explicitly and characters

other than "*", "#" or "+" are included in <number>.

Note that phonebook entries saved with this type cannot be dialed.

255

Dialing string <number> is a command to control a Supplementary Service,

i.e. "*", "#" codes are contained. Network support of this type is optional.

129

Unknown number. If <type> is unknown and the <number> contains a lead-

ing "+", <type>=145 (international) is used.

<text>^(str)(+CSCS)

Text assigned to the phone number. The maximum length of this parameter is given in the test command

response <tlength>. When using an ASCII terminal, characters which are coded differently in ASCII and GSM

have to be entered via escape sequences as described in Section 1.5, Supported character sets.

<maxloc>^(num)

Maximum number of locations supported by the currently selected storage. For phonebooks located on SIM,

this value varies depending on the SIM card. See AT+CPBS for typical values.

<nlength>^(num)

Maximum length of phone number for "normal" locations. Depending on the storage, a limited number of loca-

tions with extended memory is available per phonebook. These locations allow storing numbers with twice the

standard length, which is 2*<nlength> digits for normal numbers, but only <nlength> digits for numbers

saved with parameter <type>= 209. If all extended locations of the selected phonebook are used up, then any

attempt to write a number which requires extended memory will be denied with CME ERROR 260: INVALID

DIAL STRING.

<tlength>^(num)

Maximum length of <text> assigned to the telephone number. The value indicated by the test command is

given in octets. If the <text> string is given in GSM characters, each character corresponds to one octet. If the

<text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for

the alpha field of the SIM. In the worst case the number of UCS2 characters is at least one less than half the

number of GSM characters.

For a detailed description please refer to GSM 11.11, Annex B [25].

Note

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Page 436 of 567

17.5 AT+CPBW

Examples

EXAMPLE 1

Make a new phonebook entry at the first free location

AT+CPBW=,"+431234567",145,"international"

EXAMPLE 2

Delete entry at location 1

AT+CPBW=1

EXAMPLE 3

The following examples are provided to illustrate the effect of writing phonebook entries with different types

of dial string modifiers in <number>

AT+CPBW=5,"12345678",,"Arthur"

AT+CPBW=6,"432!+-765()&54*654#",,"John"

AT+CPBW=7,"432!+-765()&54*654#",129,"Eve"

AT+CPBW=8,"432!+-765()&54*654#",145,"Tom"

AT+CPBW=9,"432!+-765()&54*654#",209,"Richard"

EXAMPLE 4

Read phonebook entries from locations 5 - 9 via AT+CPBR

+CPBR:5,"12345678",129,"Arthur"

+CPBR:6,"432!+-765()&54*654#",209,"John"

+CPBR:7,"432+76554*654#",129,"Eve"

+CPBR:8,"+432+76554*654#",145,"Tom"

+CPBR:9,"432!+-765()&54*654#",209,"Richard"

Page 437 of 567

17.7 AT^SPBC

17.7

AT^SPBC Find first matching entry in sorted phonebook

The AT^SPBC write command searches the current phonebook for the index number of the first (lowest) entry

that matches the character specified with <schar>. The AT^SPBC test command returns the list of phonebooks

which can be searched through with AT^SPBC.

CAUTION: Please note that AT^SPBC is assigned the same index as AT^SPBG or AT^SPBS which is not identical

with the physical location numbers used in the various phonebooks. Therefore, do not use the index numbers

retrieved with AT^SPBC to dial out or modify phonebook entries.

Syntax

Test Command

AT^SPBC=?

Response(s)

^SPBC: "FD","SM","ME"

ERROR

+CME ERROR

Write Command

AT^SPBC=<schar>

Response(s)

^spbc: <index>

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<schar>^(str)

First character of the entry to be searched in the sorted list of phonebook entries.

<index>^(num)

In the active phonebook, the first (lowest) index number of an entry beginning with <schar>. As stated above,

the retrieved index number shall not be used to dial out or edit phonebook entries. If no matching phonebook

entry is found, <index>=0 will be returned.

Note

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Page 439 of 567

17.8 AT^SPBD

17.8

AT^SPBD Purge phonebook memory storage

AT^SPBD can be used to purge the selected phonebook <storage> manually, i.e. all entries stored in the

selected phonebook storage will be deleted. CAUTION! The operation cannot be stopped nor reversed!

The AT^SPBD test command returns the list of phonebooks which can be deleted with AT^SPBD.

An automatic purge of the phonebooks is performed when the SIM card is removed and replaced with a different

SIM card. This affects the ME based part of the "LD" storage, and storages "MC" and "RC". Storage "ME" is not

affected.

Syntax

Test Command

AT^SPBD=?

Response(s)

^SPBD: list of supported <storage>s

+CME ERROR

Write Command

AT^SPBD=<storage>

Response(s)

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<storage>^(str)

If test command: List of phonebooks which can be deleted by AT^SPBD.

If write command: Phonebook to be deleted.

For a detailed description of storages see AT+CPBS.

"LD"

Last number dialed phonebook

"MC"

Missed (unanswered received) calls list

"RC"

Received calls list

Note

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Page 440 of 567

17.9 AT^SPBG

17.9

AT^SPBG Display phonebook entries in alphabetical order

AT^SPBG sorts the entries of the current phonebook in alphabetical order by name (the first six characters mat-

ter). The sort order is described in Section 17.1, Sort Order for Phonebooks.

There are two ways to use AT^SPBG:

• If the optional parameter <RealLocReq> equals 0 or is omitted the sorted entries will be sequentially num-

bered. As these numbers are not identical with the location numbers stored in the various phonebooks

AT^SPBG can be used for reading only. For example, it helps you find entries starting with matching charac-

ters. Do not use the serial numbers to dial out or modify entries.

• If parameter <RealLocReq>=1 is given by the write command, the response parameter <location> addi-

tionally appended to each entry indicates the actual location number. This number can be used for editing

with AT+CPBW or dialing with ATD><mem><n>. The first index number of each entry is only the serial number

of the sorted list.

Before using the AT^SPBG write command it is recommended to query the number of records currently stored in

the active phonebook (refer to test command parameter <used>). The test command also includes the param-

eters <nlength> and <tlength>. Note that if SIM storage is selected the length may not be available. If stor-

age does not offer format information, the format list should be empty parenthesises.

Syntax

Test Command

AT^SPBG=?

Response(s)

^SPBG: (1-<used>), <nlength>, <tlength>

ERROR

+CME ERROR

Write Command

AT^SPBG=<index1>[, <index2>][, <RealLocReq>]

Response(s)

[^SPBG: <index1>, <number>, <type>, <text>[, <location>]]

[^SPBG: <index2>, <number>, <type>, <text>[, <location>]]

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<index1>^(num)

First index number in the sorted list where to start reading. The supported range is given in the test command

response.

If <index 1> exceeds the upper bound <used>, "+CME ERROR: "invalid index" will be returned.

<index2>^(num)

Last index number in the sorted list where to stop reading. The supported range is given in the test command

response.

If <index2> is not given via write command, only the entry located at <index1> will be displayed.

If both <index1> and <index2> are in the range indicated by the test command parameter <used>, the list

of entries will be output and terminated with OK.

<index2> exceeds the range indicated by the test command parameter <used>, the list of entries will be

Page 441 of 567

17.9 AT^SPBG

output but terminated with a "+CME ERROR: "invalid index".

Note: The maximum value of <index2> is 255, regardless of the phonebook type and its range indicated by

the parameter <used>. If a value greater than 255 is used the query returns no phonebook records, and only

"+CME ERROR: invalid index" is shown.

<RealLocReq>^(num)

Is a display of the "real" <location> of the entry required?

[0]

Do not show an entry's "real" location number. Parameter <location> will not

be displayed.

Show the "real" location number as parameter <location> at the end of each

entry.

<number>^(str)

String type phone number in format specified by <type>.

The number parameter may be an empty string.

<type>^(num)

Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi).

Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending

on the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> of

AT+CPBW.

Possible values are:

145

Dialing string <number> includes international access code character '+'

161

National number. Network support of this type is optional.

209

Dialing string <number> has been saved as ASCII string and includes non-

digit characters other than "*", "#" or "+". Note that phonebook entries saved

with this type cannot be dialed.

255

Dialing string <number> is a command to control a Supplementary Service,

i.e. "*", "#" codes are contained. Network support of this type is optional.

129

Otherwise

<text>^(str)(+CSCS)

Text assigned to the phone number. The maximum length for this parameter is given in test command response

<tlength>.

<used>^(num)

Value indicating the number of used locations in selected memory storage.

<location>^(num)

The location within phonebook memory at which the corresponding entry is located.

This location may be used for other commands (e.g. AT+CPBR or ATD><mem><n>)

<nlength>^(num)

Maximum length of phone number for "normal" locations. Depending on the storage, a limited number of loca-

tions with extended memory is available per phonebook. Please refer to AT command AT+CPBW for detail.

Page 442 of 567

17.9 AT^SPBG

<tlength>^(num)

Maximum length of <text> assigned to the telephone number. The value indicated by the test command is

given in octets. If the <text> string is given in GSM characters, each character corresponds to one octet. If the

<text> string is given in UCS2, the maximum number of characters depends on the coding scheme used for

the alpha field of the SIM according to GSM 11.11, Annex B [25]. In the worst case the number of UCS2 char-

acters is at least one less than half the number of GSM characters.

Notes

• The command can be used for the phonebooks "SM", "FD", "ME" (cf. AT+CPBS).

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Examples

EXAMPLE 1

Using AT^SPBG without <RealLocReq>:

AT^SPBG=?

First run the AT^SPBG test command to find out the

range of entries stored in the current phonebook.

^SPBG: (1-33),20,17

TA returns the range, where 33 is the number of

entries stored in the current phonebook.

AT^SPBG=1,33

Now, enter the write command. To obtain best

^SPBG:1,"+999999",145,"Arthur"

results it is recommended to query the full range of

^SPBG:2,"+777777",145,"Bill"

entries. TA returns phonebook entries in alphabetical

order.

^SPBG:3,"+888888",145,"Charlie"

The numbers at the beginning of each line are not the memory locations in the phonebook, but only serial

numbers assigned to the entries' positions in the alphabetical list.

EXAMPLE 2

Using AT^SPBG with <RealLocReq>:

AT^SPBG=?

First run the AT^SPBG test command to find out the

range of entries stored in the current phonebook.

^SPBG: (1-33),20,17

TA returns the range, where 33 is the number of

entries stored in the current phonebook.

AT^SPBG=1,33,1

Now, enter the write command including parameter

^SPBG:1,"+999999",145,"Arthur",27

<RealLocReq>=1 to get the actual location num-

^SPBG:2,"+777777",145,"Bill",6

bers.

^SPBG:3,"+888888",145,"Charlie",15

The numbers at the end of each line are the memory locations in the phonebook and can be used for dialing

or editing phonebook entries:

AT+CPBR=27

Read out phonebook location 27.

+CPBR: 27,"+999999",145,"Arthur"

This entry can be edited with AT+CPBW or used for

dialing with ATD><mem><n>.

Page 443 of 567

17.10 AT^SPBS

17.10

AT^SPBS Step through the selected phonebook alphabetically

AT^SPBS can be used to scroll sequentially through the active phonebook records in alphabetical order by name.

Three entries will be displayed at a time.

Every time the write command is executed, 3 rows of phonebook records are returned. Each triplet overlaps with

the next one. The actual index depends on parameter <value>. This parameter determines whether the index

will be increased or decreased.

If the index in one output line reaches the last index in the alphabetical list, the next output line will display the

first list entry.

After the last record of the phonebook has been reached (see parameter <used> for AT^SPBG), the <inter-

nal-counter> switches over to the first.

There are two ways to use AT^SPBS:

• If the optional parameter <RealLocReq> is omitted or (0) the sorted entries will be sequentially numbered.

As these numbers are not identical with the location numbers stored in the various phonebooks AT^SPBS can

be used for reading only. For example, it helps you find entries starting with matching characters. Do not use

the serial numbers to dial out or modify entries.

• If parameter <RealLocReq>=1 is given by the write command, the response parameter <location> addi-

tionally appended to each entry indicates the actual location number. This number can be used for editing

with AT+CPBW or dialing with ATD><mem><n>. The first index number of each entry is only the serial number

of the sorted list.

See examples below.

Syntax

Test Command

AT^SPBS=?

Response(s)

^SPBS: (list of supported <value>)

Write Command

AT^SPBS=<value>[, <RealLocReq>]

Response(s)

^SPBS: <index-a>, <number>, <type>, <text>[, <location>]

^SPBS: <index-b>, <number>, <type>, <text>[, <location>]

^SPBS: <index-c>, <number>, <type>, <text>[, <location>]

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Parameter Description

<value>^(num)

To make a step forward in the alphabetically sorted phonebook.

To make a step backward in the alphabetically sorted phonebook.

<index-a>^(num)

1...maxindex

The index in the sorted list of phonebook entries that identifies the first entry

displayed.

The value of <index-a> is determined by the value of the <internal-

counter> and by parameter <value>.

Page 444 of 567

17.10 AT^SPBS

After a write command has terminated successfully with "OK", the value from

parameter <index-a> is saved and retained as the new <internal-

counter> value.

Mind after the last record of phonebook, the first entry follows.

<index-b>^(num)

1...maxindex

The index in the sorted list of phonebook entries that identifies the second entry

displayed.

<index-b>= (<index-a>+1).

Mind after the last record of phonebook, the first entry follows.

<index-c>^(num)

1...maxindex

The index in the sorted list of phonebook entries that identifies the third entry

displayed.

<index-c>= (<index-b>+1).

Mind after the last record of phonebook, the first entry follows.

<number>^(str)

String type phone number in format specified by <type>.

the number parameter may be an empty string.

<type>^(num)

Type of address octet, which defines the used type of number (ton) and the numbering plan identification (npi).

Please consider that for types other than 129 or 145 dialing from phonebook with ATD><mem><n> is, depending

on the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> of

AT+CPBW.

Possible values are:

145

Dialing string <number> includes international access code character '+'

161

National number. Network support of this type is optional.

209

Dialing string <number> has been saved as ASCII string and includes non-

digit characters other than "*", "#" or "+". Note that phonebook entries saved

with this type cannot be dialed.

255

Dialing string <number> is a command to control a Supplementary Service,

i.e. "*", "#" codes are contained. Network support of this type is optional.

129

Otherwise

<text>^(str)(+CSCS)

Text assigned to the phone number.

<RealLocReq>^(num)

Is a display of the "real" <location> of the entry required?

[0]

Do not show an entry's "real" location number. Parameter <location> will not

be displayed

Show the "real" location number as parameter <location> at the end of the

entry

<location>^(num)

The location within phonebook memory at which the corresponding entry is located.

This location may be used for other phonebook commands (e.g. AT+CPBR, AT+CPBW, ATD><mem><n>).

Page 445 of 567

17.10 AT^SPBS

<internal-counter>^(num)

0^(&F)...maxindex

This parameter is only an internal parameter and cannot modified directly.

The internal counter will be reset to index 0 after a call to ATZ or AT&F.

Notes

• The complete list of sorted entries can be retrieved using AT command AT^SPBG.

• The command can be used for the phonebooks "SM", "FD", "ME" (cf. AT+CPBS).

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM data

may not yet be accessible, resulting in a short delay before the requested AT command response is returned.

See Section 23.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Examples

EXAMPLE 1

This example illustrates how to search down and up again using AT^SPBS=1 and 2:

at&f

First, AT&F is issued to make sure that AT^SPBS=1

starts from the first character in alphabetical order.

at^spbs=1

^SPBS:1,"+999999",145,"Arthur"

^SPBS:2,"+777777",145,"Bill"

^SPBS:3,"+888888",145,"Charlie"

at^spbs=1

^SPBS:2,"+777777",145,"Bill"

^SPBS:3,"+888888",145,"Charlie"

^SPBS:4,"0304444444",129,"Esther"

at^spbs=1

^SPBS:3,"+888888",145,"Charlie"

^SPBS:4,"0304444444",129,"Esther"

^SPBS:5,"03033333333",129,"Harry"

at^spbs=2

^SPBS:2,"+777777",145,"Bill"

^SPBS:3,"+888888",145,"Charlie"

^SPBS:4,"0304444444",129,"Esther"

EXAMPLE 2

This example shows that when the last index in the sorted list has been reached, the internal counter over-

flows to the first index.

at&f

Reset internal counter to 0.

at^spbs=2

Step down one entry starting from

(internal

^SPBS:33,"+49301234567",145,"TomTailor"

counter)=0 - overflow occurs.

^SPBS:1,"+999999",145,"Arthur"

^SPBS:2,"+777777",145,"Bill"

Page 446 of 567

18.2 ATL

18.2

ATL Set monitor speaker loudness

ATL is implemented for V.250ter compatibility reasons only, and has no effect. In multiplex mode (refer

AT+CMUX) the command is supported on logical channel 1 only.

Syntax

Exec Command

ATL[<val>]

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

V.250

Parameter Description

<val>^(num)

18.3

ATM Set monitor speaker mode

ATM is implemented for V.250ter compatibility reasons only, and has no effect. In multiplex mode (refer

AT+CMUX) the command is supported on logical channel 1 only.

Syntax

Exec Command

ATM[<val>]

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

V.250

Parameter Description

<val>^(num)

Page 450 of 567

18.4 AT+CLVL

18.4

AT+CLVL Loudspeaker volume level

Syntax

Test Command

AT+CLVL=?

Response(s)

+CLVL: (list of supported<level>s)

Read Command

AT+CLVL?

Response(s)

+CLVL: <level>

ERROR

+CME ERROR: <err>

Write Command

AT+CLVL=<level>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.07

Parameter Description

<level>^(num)

Loudspeaker Volume Level

0...4^(D)

Notes

• The write command can only be used in audio mode 2 - 6.

• The values of the volume steps are specified with the parameters <outCalibrate>[0],...<outCali-

brate>[4] of the AT^SNFO command.

• As an alternative to AT+CLVL, you can use AT^SNFO and AT^SNFV. The parameter <level> is identical with

<outStep> used by both commands.

• Any change to <level> (or <outStep>) takes effect in audio modes 2 to 6. That is, when you change

<level> (or <outStep>) and then select another mode with AT^SNFS, the same step will be applied.

The only exception is audio mode 1 which is fixed to <level>=4 (or accordingly <outStep>=4).

•

<level> (or <outStep>) is stored non-volatile when the ME is powered down with AT^SMSO or reset with

AT+CFUN=1,1.

Page 451 of 567

18.5 AT+CMUT

18.5

AT+CMUT Mute control

The AT+CMUT command mutes the microphone input. The command can be used in all audio modes (1 to 6) and

during a voice call only. See AT^SNFS for more details on the various audio modes. As alternative, you can use

the AT^SNFM command.

During an active call, users should be aware that when they switch back and forth between different audio modes

(for example handsfree on/off) the value of <mute> does not change, i.e. the microphone mode is retained until

explicitly changed.

Syntax

Test Command

AT+CMUT=?

Response(s)

+CMUT: (list of supported<mute>s)

Read Command

AT+CMUT?

Response(s)

+CMUT: <mute>

ERROR

+CME ERROR: <err>

Write Command

AT+CMUT=<mute>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.07

Parameter Description

<mute>^(num)

0^(P)

Mute off

Mute on

Page 452 of 567

18.7 AT+VTS

18.7

AT+VTS DTMF and tone generation

AT+VTS is intended to send ASCII characters or strings which cause the Mobile Switching Center (MSC) to trans-

mit DTMF tones to a remote subscriber. The command can only be used during active voice calls and offers the

following variants:

• AT+VTS=<dtmfString> allows to send a sequence of DTMF tones with a duration defined with AT+VTD.

• AT+VTS=<dtmf>[,<duration>] allows to send a single DTMF tone. In this case, the duration can be ind-

vidually determined during the call.

Syntax

Test Command

AT+VTS=?

Response(s)

+VTS: (list of supported<dtmf>s), (list of supported<duration>s)

Write Command

AT+VTS=<dtmfString>

Response(s)

Write Command

AT+VTS=<dtmf>[, <duration>]

Response(s)

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.07

Parameter Description

<dtmfString>^(str)

String of ASCII characters in the set 0-9,#,*,A, B, C, D. Maximal length of the string is 29. The string must be

enclosed in quotation marks ("...").

<dtmf>^(str)

ASCII character in the set 0...9,#,*, A, B, C, D.

<duration>^(num)

Tone duration in 1/10 seconds with tolerance. If not specified current setting of AT+VTD is used.

The minimum duration of DTMF signals is 300ms.

1...255

Page 454 of 567

18.8 AT^SAIC

18.8

AT^SAIC Audio Interface Configuration

AT^SAIC configures the interface connections of the active audio mode. Please keep in mind that the TC65 Ter-

minal has only one analog audio interface.

The write command is usable in audio modes 2 to 6 only.

If AT^SNFS=1, any attempt to use AT^SAIC write command is rejected with error response. This is because all

default parameters in audio mode 1 are determined for type approval and are not adjustable.

To allocate a specific audio mode to one of the audio interfaces, first select the audio mode with AT^SNFS and

then choose the interface using AT^SAIC.

Syntax

Test Command

AT^SAIC=?

Response(s)

^SAIC:(list of supported <io>s), (list of supported<mic>s), (list of supported<ep>s)

Read Command

AT^SAIC?

Response(s)

^SAIC: <io>, <mic>, <ep>

Write Command

AT^SAIC=<io>[, <mic>[, <ep>]]

Response(s)

ERROR

+CME ERROR: operation not allowed

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<io>^{(num)(^SNFW)}

Input and output selection

Digital input and output (DAI) of the TC65 Module, not applicable to TC65 Ter-

minal

Analog input and output

<mic>^{(num)(^SNFW)}

Microphone selection

Microphone 1

Microphone 2

Not applicable to TC65 Terminal

<ep>^{(num)(^SNFW)}

Select differential earpiece amplifier

Selects the earpiece amplifier 1

Page 455 of 567

18.8 AT^SAIC

Selects the earpiece amplifier 2

Not applicable to the TC65 Terminal

Selects both amplifiers. Note that both amplifiers are connected in parallel and

therefore, get the same output power if <ep>=3.

Not applicable to the TC65 Terminal

Notes

• The factory defaults of AT^SAIC vary with the selected audio mode.

If AT^SNFS=1 or 4 or 5, then AT^SAIC=2,1,1.

If AT^SNFS=2 or 3 or 6, then AT^SAIC=2,2,2. (Although given by default, this setting applies to the TC65

module only, it cannot be used with the TC65 Terminal where the second audio interface is not connected.

Nevertheless, you can configure TC65 Terminal for operation with audio modes 2, 3 or 6 by setting

AT^SAIC=2,1,1 instead. See examples provided with AT^SNFS.)

AT^SNFD can be used to reset the factory defaults.

• For use after restart of the ME, you are advised to store the settings of AT^SAIC and AT^SNFS to the audio

profile saved with AT^SNFW. Otherwise, audio mode 1 (AT^SNFS=1) and audio interface 2 (AT^SAIC=2,1,1)

will be active each time the ME is powered up.

Page 456 of 567

18.9 AT^SNFA

18.9

AT^SNFA Set or query of microphone attenuation

AT^SNFA specifies the large-scale attenuation on the microphone path of the audio device currently selected

with AT^SNFS. The write command is only available in audio modes 2 to 6.

Syntax

Test Command

AT^SNFA=?

Response(s)

^SNFA: (list of supported <atten>s)

Read Command

AT^SNFA?

Response(s)

^SNFA: <atten>

Write Command

AT^SNFA=<atten>

Response(s)

ERROR

CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<atten>^{(num)(^SNFW)}

Multiplication factor for input samples. Parameter <atten> is identical with <inCalibrate> of AT^SNFI.

Formula used to calculate microphone attenuation (negative gain):

Gain in dB = 20 * log(<atten>/32768)

0...32767^(P)...65535

Microphone is muted.

Please note that AT^SNFA cannot be used to mute the microphone. Therefore,

any attempt to enter 0 will be rejected with error response. Value 0 is returned

only by the read command AT^SNFA? after the microphone was muted with

AT^SNFM=0 during an active call.

32767

No attenuation on the microphone path

Values greater than 32767 will be suppressed to 32767.

Notes

• This command is provided for compatibility with former products (e.g. M20) and is a subset of AT^SNFI. The

parameter <inCalibrate> of AT^SNFI is identical with <atten> of AT^SNFA.

• To make the changes persistent use AT^SNFW.

Page 457 of 567

18.10 AT^SNFD

18.10

AT^SNFD Set audio parameters to manufacturer default values

AT^SNFD sets the active audio parameters to manufacturer defined default values.

The restored values are:

AT^SNFA: <atten>

AT^SNFI: <inBbcGain>, <inCalibrate>

AT^SNFO: <outBbcGain>, <outCalibrate>[0 to 4], <sideTone>

AT^SAIC: <io>, <mic>, <ep>

AT^SNFS: <audMode>

Syntax

Test Command

AT^SNFD=?

Response(s)

Exec Command

AT^SNFD

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Note

• Remember that the factory set audio mode 1 is fixed to <outStep>=4. Consequently, AT^SNFD restores

<audMode> together with <outStep>=4, but does not affect the values of <outStep> currently selected in

audio modes 2 - 6. This means, if <audMode>=1, the read commands AT^SNFO, AT^SNFV and AT+CLVL will

always deliver <outStep>=4. In all other modes the <outStep> value is retained until explicitly changed.

Page 459 of 567

18.11 AT^SNFI

18.11

AT^SNFI Set microphone path parameters

AT^SNFI controls the microphone path amplification. Read and write options of this command refer to the active

audio mode. The write command works only in audio modes 2 to 6.

Syntax

Test Command

AT^SNFI=?

Response(s)

^SNFI: (list of supported <inBbcGain>s) , (list of supported <inCalibrate>s)

Read Command

AT^SNFI?

Response(s)

^SNFI: <inBbcGain>, <inCalibrate>

Write Command

AT^SNFI=<inBbcGain>, <inCalibrate>

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<inBbcGain>^{(num)(^SNFW)}

ADC gain adjustable in eight 6 dB steps from 0 dB to 42 dB (0=0dB, 7=42dB, 8 steps of 6 dB).

0...7

<inCalibrate>^{(num)(^SNFW)}

Multiplication factor for input samples. Formula to calculate the negative gain (attenuation) of the input signal:

Gain in dB = 20 * log (inCalibrate / 32768)

0...32767

Notes

• The range of <inCalibrate> is up to 65535 but will be suppressed to 32767. Values above <inCali-

brate>= 65535 will cause a failure.

• The parameter <inCalibrate> of AT^SNFI is identical with <atten> of AT^SNFA.

• For use after restart, changed values can be stored with AT^SNFW.

• Attention! When you adjust audio parameters avoid exceeding the maximum allowed level. Bear in mind that

exposure to excessive levels of noise can cause physical damage to users!

Page 460 of 567

18.12 AT^SNFM

18.12

AT^SNFM Set microphone audio path and power supply

The AT^SNFM read command returns the microphone mute and supply voltage status.

The AT^SNFM write command can be used to switch the microphone's audio path (muted / not muted) or to con-

trol the power supply of the VMIC line for the two microphone inputs of the TC65 Module. Please keep in mind

that the TC65 Terminal has no programmable microphone power supply, therefore only the mute switch applies.

The microphone can be muted or activated by changing <MicSwitch> in all audio modes (1 to 6) and during a

voice call only. As an alternative, you can use the AT+CMUT command to mute the microphone.

Syntax

Test Command

AT^SNFM=?

Response(s)

^SNFM: (list of supported <MicSwitch>s) , (list of supported <MicVccCtl>s)

Read Command

AT^SNFM?

Response(s)

^SNFM: <MicSwitch>, <MicVccState>

Write Command

AT^SNFM=[<MicSwitch>][, <MicVccCtl>]

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<MicSwitch>^(num)

Microphone mute control parameter.

Evaluated only during voice calls and if <MicVccCtl> is omitted, e.g. AT^SNFM=1.

Command does not depend on audio mode.

Mutes the microphone.

1^(P)

Activates the microphone.

<MicVccCtl>^(num)

Microphone supply voltage control parameter. Controls the power supply VMIC of the two microphone inputs of

the TC65 Module. Parameter is not applicable to the TC65 Terminal.

CME error is given if <MicSwitch> is not omitted. Enter for example AT^SNFM=,1 or AT^SNFM=,2.

Supply voltage is always switched off.

Supply voltage is always switched on.

2^(P)

Supply voltage state during voice calls is controlled by the ME. Actual value is

determined by parameter data set of the selected audio mode.

Page 461 of 567

18.12 AT^SNFM

<MicVccState>^(num)

Microphone supply voltage control status.

Parameter is not applicable to the TC65 Terminal.

Supply voltage was set to a constant value.

Supply voltage state is controlled by the ME and depends on parameter data

set of the selected audio mode.

Notes

• The programmable power supply of the VMIC line gives you greater flexibility in connecting audio accessories

or using the two analog audio interfaces for a variety of functions other than audio. A detailed description of

the extended usage of the analog audio interfaces can be found in [10].

• During an active call, users should be aware that when they switch back and forth between different audio

modes (for example handsfree on/off) the value of <MicSwitch> does not change, i.e. the microphone mode

is retained until explicitly changed.

Page 462 of 567

18.13 AT^SNFO

18.13

AT^SNFO Set audio output (= loudspeaker path) parameter

AT^SNFO controls the earpiece path amplification. The read and write commands refer to the active audio mode.

The write command works only in audio modes 2 to 6.

Syntax

Test Command

AT^SNFO=?

Response(s)

^SNFO: (list of supported <outBbcGain>s), (list of supported <outCalibrate>s), (list of supported

<outStep>s), (list of supported <sideTone>s)

Read Command

AT^SNFO?

Response(s)

^SNFO: <outBbcGain>, <outCalibrate>[0] , <outCalibrate>[1] , <outCalibrate>[2] ,

Write Command

AT^SNFO=<outBbcGain>, <outCalibrate>[0] , <outCalibrate>[1] , <outCalibrate>[2] ,

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Parameter Description

<outBbcGain>^{(num)(^SNFW)}

Negative DAC gain (attenuation) adjustable in four 6 dB steps from 0 dB to -18 dB (0=0 dB, 3=-18 dB)

0...3

<outCalibrate>^{(num)(^SNFW)}

Formula to calculate the value of the 5 volume steps selectable with parameter <outStep>:

Attenuation = 20 * log (2 * outCalibrate[n] / 32768)

0...32767

<outStep>^(num)

Volume steps 0 - 4, each defined with outCalibrate[n]

0...[4]

<sideTone>^{(num)(^SNFW)}

Multiplication factor for the sidetone gain.

Formula to calculate how much of the original microphone signal is added to the earpiece signal:

Sidetone gain in dB = 20 * log (sideTone / 32768).

0...32767

Page 463 of 567

18.13 AT^SNFO

Notes

•

<outCalibrate> specifies the amount of volume of each <outStep>. The range of each <outCali-

brate> is up to 65535, but will be suppressed to 32767. A value above <outCalibrate>= 65535 will cause

an error.

• The range of <sideTone> is up to 65535, but will be suppressed to 32767. A value above <sideTone>=

65535 will cause an error.

• Any change to <outStep> takes effect in audio modes 2 to 6. That is, when you change <outStep> and

then select another mode with AT^SNFS, the same step will be applied. Nevertheless, the sound quality and

the amount of volume are not necessarily the same, since all remaining audio parameters can use different

values in either mode.

• Audio mode 1 is fixed to <outStep>=4. In this mode, any attempt to change <outStep> or other parameters

returns an error.

• The value of <outStep> is stored non-volatile when the ME is powered down with AT^SMSO or reset with

AT+CFUN=x,1. Any other parameters changed with AT^SNFO need to be saved with AT^SNFW for use after

restart. See also AT^SNFD for details on restoring factory defaults.

• The values of <outStep> can also be changed with AT^SNFV and AT+CLVL.

• CAUTION! When you adjust audio parameters avoid exceeding the maximum allowed level. Bear in mind that

exposure to excessive levels of noise can cause physical damage to users!

Page 464 of 567

18.14 AT^SNFPT

18.14

AT^SNFPT Set progress tones

AT^SNFPT controls the Call Progress Tones generated at the beginning of a mobile originated call setup.

Please note that the setting is stored volatile, i.e. after restart or reset, the default value 1 will be restored.

Syntax

Test Command

AT^SNFPT=?

Response(s)

^SNFPT: (list of supported <pt>s)

Read Command

AT^SNFPT?

Response(s)

^SNFPT: <pt>

Write Command

AT^SNFPT=<pt>

Response(s)

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3 Charge

Last

SIEMENS

Parameter Description

<pt>^(num)

Disables Call Progress Tones

1^(P)

Enables Call Progress Tones (audible tones shortly heard on the phone when

ME starts to set up a call.)

Page 465 of 567

18.15 AT^SNFS

18.15

AT^SNFS Select audio hardware set

The AT^SNFS write command serves to set the audio mode required for the connected equipment.

AT^SNFS can also be used in conjunction with AT^SAIC. This is useful, for example, if the audio interfaces are

operated alternatively to benefit from different devices. Each audio mode can be assigned a specific interface.

To do so, first select the audio mode with AT^SNFS, then activate the audio interface with AT^SAIC and finally

enter AT^SNFW to store the settings to your audio profile. To switch back and forth it is sufficient to use AT^SNFS.

Syntax

Test Command

AT^SNFS=?

Response(s)

^SNFS: (list of supported <audMode>s)

Read Command

AT^SNFS?

Response(s)

^SNFS: <audMode>

Write Command

AT^SNFS=<audMode>

Response(s)

ERROR

CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<audMode>^{(num)(^SNFW)}

[1]

Audio mode 1: Standard mode optimized for the reference handset, that can

be connected to the analog interface

1 (see "TC65 Hardware Interface

Description" for information on this handset.) To adjust the volume use the

knob of the reference handset. In audio mode 4, this handset can be used with

user defined parameters.

Note: The default parameters are determined for type approval and are not

adjustable with AT commands.

AT^SNFD restores <audMode> 1.

Audio mode 2: Customer specific mode for a basic handsfree (speakerphone)

device (Siemens Car Kit Portable).

Analog interface 2 is assumed as default.

Audio mode 3: Customer specific mode for a mono-headset.

Analog interface 2 is assumed as default.

Audio mode 4: Customer specific mode for a user handset.

Analog interface 1 is assumed as default.

Audio mode 5: Customer specific mode.

Analog interface 1 is assumed as default.

Audio mode 6: Customer specific mode.

Analog interface 2 is assumed as default.

Page 466 of 567

18.15 AT^SNFS

Notes

• The write command can be used during a voice call to switch back and forth between different modes. This

allows the user, for example, to switch handsfree operation (speakerphone) on and off.

• Users should be aware that <outStep> is a global setting. This means, when another audio mode is selected

during a call, the value of <outStep> does not change. This is also true for mute operation which can be set

with AT^SNFM or AT+CMUT: If the microphone is muted and the user selects another audio mode during the

call, then the microphone remains muted until explicitly changed. Exception: In audio mode 1 <outStep>=4

is fix.

• For use after restart of the module, you are advised to store the selected mode to the audio profile saved with

AT^SNFW. Otherwise, audio mode 1 will be active each time the module is powered up.

Examples

EXAMPLE 1

Suppose a user wishes to use alternatively a handsfree device (speakerphone) and a handset. The handset

can be connected to the first analog interface and adjusted to audio mode 4. The handsfree device can be

attached to the second analog interface and adjusted to audio mode 2. The factory defaults of AT^SAIC need

not be changed.

Settings for the handset:

AT^SNFS=4

AT^SAIC?

Factory default of AT^SAIC assigned to audio mode 4.

^SAIC: 2,1,1

Settings for the handsfree device:

AT^SNFS=2

AT^SAIC?

Factory default of AT^SAIC assigned to audio mode 2.

^SAIC: 2,2,2

To store the configuration to the user defined audio profile:

AT^SNFW

Stores the audio mode and the interface.

To switch back and forth:

AT^SNFS=4

Switches to the handset connected to analog interface 1.

AT^SNFS=2

Switches to the handsfree device at analog interface 2.

EXAMPLE 2

The following example illustrates a combination of a handset and a handsfree device connected to other inter-

faces than those assumed as factory default.

Settings for a handset connected to the second analog interface and adjusted to audio mode 4:

AT^SNFS=4

AT^SAIC=2,2,2

Settings for a handsfree device connected to the first analog interface and adjusted to audio mode 2:

AT^SNFS=2

AT^SAIC=2,1,1

To store the configuration to the user defined audio profile:

Page 467 of 567

18.16 AT^SNFTTY

18.16

AT^SNFTTY Signal TTY/CTM audio mode capability

TC65 offers basic support for equipment using the CTM standard (Cellular Text Telephone Modems). The benefit

of CTM is that text characters typed on a TTY device (Text Telephone Type-writer) can be transformed into spe-

cial audio burst signals for reliable transmission via the existing speech channels of a cellular phone system.

If CTM mode is activated, the ME will set the necessary bearer capability bit on outgoing (mobile originated) calls

and incoming calls with this bearer capability bit set are accepted. The TE needs to decode the special audio

burst signals.

If CTM mode is disabled, the ME will clear the bearer capability bit on mobile originated calls and incoming calls

with the bearer capability bit set are rejected because the TC65 expects that CTM coded speech data cannot be

decoded by the TE.

Designed to set the module's speech system into CTM mode, the AT^SNFTTY command allows a CTM device

to be connected to one of the three audio interfaces of TC65. Traditional TTY devices that do not incorporate

CTM functionality can be connected through an external TTY-to-CTM adapter.

Related documents: Refer to the relevant standards, such as 3GPP TS 26.226 (ETSI TS 126 226) and 3GPP

TS 23.228 (ETSI TS 123 226). 3GPP documentation can be retrieved, for example, from http://www.3gpp.org/

specs/specs.htm. Application Note 22 "Using TTY/CTM equipment" supplies information needed to connect

TTY/CTM equipment to the TC65.

Requirements for using TTY/CTM features:

• TTY/CTM functionality requires audio mode 5 or 6 with all audio parameters set to their factory default.

To do so, first enter the AT^SNFS command to select audio mode 5, then use AT^SNFI and AT^SNFO to

restore the default values. Alternatively, factory defaults of all audio parameters in audio modes 2 - 6 can eas-

ily be set with AT^SNFD.

• Depending on which audio interface the CTM device is connected to select the according settings via

AT^SAIC.

Syntax

Test Command

AT^SNFTTY=?

Response(s)

^SNFTTY: (list of supported <audioState>s)

Read Command

AT^SNFTTY?

Response(s)

^SNFTTY: <audioState>

Write Command

AT^SNFTTY=<audioState>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<audioState>^(num)

Audio path is in normal speech mode.

Audio path is in TTY/CTM mode.

Page 469 of 567

18.17 AT^SNFV

18.17

AT^SNFV Set loudspeaker volume

AT^SNFV can be used to set the volume of the loudspeaker to the value <outCalibrate> addressed by <out-

Step>. The read and write commands refer to the active audio mode. The write command works only in audio

modes 2 to 6.

Syntax

Test Command

AT^SNFV=?

Response(s)

^SNFV: (list of supported <outStep>s)

Read Command

AT^SNFV?

Response(s)

^SNFV: <outStep>

Write Command

AT^SNFV=<outStep>

Response(s)

ERROR

+CME ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Parameter Description

<outStep>^(num)

The actual volume of each step is defined by the parameter <outCalibrate>, which can be set with AT^SNFO.

0...4^(P)

Notes

• Any change to <outStep> takes effect in audio modes 2 to 6. That is, when you change <outStep> and

then select another mode with AT^SNFS, the same step will be applied. Nevertheless, the actual volume can

be quite different, depending on the values of <outCalibrate> set in each mode. The only exception is

audio mode 1 which is fixed to <outStep>=4.

•

<outStep> is stored non-volatile when the ME is powered down with AT^SMSO or reset with AT+CFUN=1,1.

<outStep> is not stored by AT^SNFW.

•

<outStep> can also be changed by AT^SNFO (Section 18.13) and AT+CLVL (Section 18.4).

Page 470 of 567

18.19 AT^SRTC

18.19

AT^SRTC Ring tone configuration

The AT^SRTC read command returns the current <type> and current <volume>. The read command can be

used while test playback is off or on. In the latter case, see execute command for details.

The AT^SRTC execute command is intended for testing. It starts to play a melody from the audio output currently

selected with AT^SNFS. To deactivate test playback use AT^SRTC again.

During test playback, you can enter the write command to select another melody and adjust the volume. Also,

you can enter the read command to check the type and volume of the current ring tone, and to view the status

of playback (on / off). The test ringing signal cannot be activated when an MTC is ringing (ERROR).

Selecting <volume>=0 during the test, immediately stops playback. After this, ring tones will be muted until you

change <volume> using the write command.

The AT^SRTC write command chooses the type and volume of ring tones. The settings can be changed no matter

whether or not the ME is ringing. The selected type and volume are saved in the non-volatile Flash memory and,

thus, are retained after Power Down. An exception is <type>=0, that can be entered to quickly mute the tone or

melody currently played to indicate an event. <type>=0 only stops immediately the audible ring tone, but does

not terminate the URC that indicates the event (for example RING). No permanent settings are changed or

saved.

Syntax

Test Command

AT^SRTC=?

Response(s)

^SRTC:(list of supported) <type>s, (list of supported) <volume>s

Read Command

AT^SRTC?

Response(s)

^SRTC: <type>, <volume>, <status>

Exec Command

AT^SRTC

Response(s)

Write Command

AT^SRTC=[<type>][, <volume>]

Response(s)

^SRTC: <type>, <volume>

ERROR

Reference(s)

PIN ASC0 ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

SIEMENS

Page 472 of 567

18.19 AT^SRTC

Parameter Description

<type>^(num)

Type of ring tone. You have a choice of 7 different ring tones and melodies. All will be played from the audio

output selected with the AT^SNFS command. <type>=0 is only intended for muting.

Mutes the currently played tone immediately.

Sequence 1

Sequence 2

3^(D)

Sequence 3

Sequence 4

Sequence 5

Sequence 6

Sequence 7

<volume>^(num)

Volume of ring tone, varies from low to high

0^(D)

Mute

Very low

Identical with 1

Low

Identical with 3

Middle

Identical with 5

High

<status>^(num)

Status of test ringing. Indicates whether or not a melody is currently being played back for testing

Switched off

Switched on

Notes

• Before first using ring tones note that the following settings apply:

We have chosen to let you decide your own preferences when you start using ring tones. Therefore, factory

setting is AT^SRTC=3,0,0 (ring tones are muted). To activate ring tones for the very first time, first enter the

write command and simply change the volume. After applying a firmware update the volume and type

selected before the firmware update will be preserved.

• The test ringing signal cannot be activated while an MTC is ringing (ERROR).

• If an MTC arrives during test playback, test ringing will be deactivated and "normal" ringing reactivated

(RING). Likewise, an MOC will also stop test ringing.

• If no optional parameter is entered, the old value will be kept.

Page 473 of 567

19. Hardware related Commands

19.

Hardware related Commands

The AT Commands described in this chapter are related to the TC65's hardware interface. More information

regarding this interface is available with the "TC65 Hardware Interface Description"[2].

19.1

AT+CCLK

Real Time Clock

Syntax

Test Command

AT+CCLK=?

Response(s)

Read Command

AT+CCLK?

Response(s)

+CCLK: <time>

Write Command

AT+CCLK=<time>

Response(s)

+CME ERROR: <err>

ERROR

Reference(s)

ASC0

ASC1

USB

MUX1

MUX2

MUX3

Charge

Last

GSM 07.07

Parameter Description

<time>^(str)

Format is "yy/mm/dd,hh:mm:ss", where the characters indicate the two last digits of the year, followed by month,

day, hour, minutes, seconds; for example 6th of July 2005, 22:10:00 hours equals to "05/07/06,22:10:00"

Factory default is "02/01/01,00:00:00"

Notes

•

<time> is retained if the device enters the Power Down mode via AT^SMSO.

•

<time> will be reset to its factory default if power is totally disconnected. In this case, the clock starts with

<time>= "02/01/01,00:00:00" upon next power-up.

• Each time TC65 is restarted it takes 2s to re-initialize the RTC and to update the current time. Therefore, it is

recommended to wait 2s before using the commands AT+CCLK and AT+CALA (for example 2s after

^SYSSTART has been output).

Page 474 of 567

19.2 AT+CALA

19.2

AT+CALA Set alarm time

The AT+CALA write command can be used to set an alarm time in the ME or to clear a programmed alarm. When

the alarm time is reached and the alarm is executed the ME returns an Unsolicited Result Code (URC) and the

alarm time is reset to "00/01/01,00:00:00".

The alarm can adopt two functions, depending on whether or not you switch the GSM engine off after setting the

alarm:

• Reminder message: You can use the alarm function to generate reminder messages. For this purpose, set

the alarm as described below and do not switch off or power down the ME. When executed the message

comes as an Unsolicited Result Code which reads "+CALA".

• Airplane mode: The alarm function can be used to wake up the ME at a scheduled time. For this purpose, set

the alarm as described below. Then power down the ME by entering the AT^SMSO command. When the alarm

time is reached the ME enters the Airplane mode, notified to the user by the URC "^SYSSTART AIRPLANE

MODE" and, if available, by a user defined text message (specified with <text>). In Airplane mode, the RF

interface of the ME is shut down to prevent it from unintentionally logging into the GSM network. All AT com-

mands whose execution requires a radio connection are disabled. A list of AT commands supported during

Airplane mode can be found in Section 23.4, Availability of AT Commands Depending on Oper-

ating Mode of ME. To return from Airplane mode to Normal mode use the AT^SCFG command and set

the parameter <map> to "off". This immediately activates the RF interface and restores access to all AT com-

mands. The URC "^SYSSTART" notifies the user that the ME has returned to Normal mode. Please note that

setting an alarm with AT+CALA is one method to wake up into Airplane mode. The second approach is using

the AT^SCFG command, parameter <mapos>. For further detail on Airplane mode refer to Section 2.14,

AT^SCFG.

The AT+CALA test command returns the supported array index values <n>, the supported alarm types <type>

and the maximum length of the text <tlength> to be output.

The AT+CALA read command returns the current alarm settings in the ME.

Syntax

Test Command

AT+CALA=?

Response(s)

+CALA: (list of supported<n>s), (list of supported<type>s), (list of supported<tlength>s)

ERROR

+CME ERROR: <err>

Read Command

AT+CALA?

Response(s)

+CALA: <time>[, <n>[, <type>[, <text>]]]

ERROR

+CME ERROR: <err>

Write Command

AT+CALA=<time>[, <n>[, <type>[, <text>]]]

Response(s)

ERROR

+CME ERROR

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3

Charge

Last

GSM 07.07

Page 475 of 567

19.2 AT+CALA

Unsolicited Result Code

+CALA: [<text>]

Indicates reminder message.

After power-down and wake-up at the scheduled time, the following URC indicates that the ME has entered the

Airplane mode:

"^SYSSTART AIRPLANE MODE"

+CALA: [<text>]

Parameter Description

<time>^(str)

Format is "yy/MM/dd,hh:mm:ss". For example, 6th of July 2005, 22:10:00 equals to "05/07/06,22:10:00" (see

also AT+CCLK).

Note: If <time> equals current date and time or is set to an earlier date, TA returns +CME ERROR: 21.

To clear a given alarm before its scheduled time simply enter an empty string for parameter <time>. See exam-

ples below.

<n>^(num)

Integer type value indicating the array index of the alarm.

The ME allows to set only one alarm at a time. Therefore, the list of supported alarm events indicated by the test

command AT+CALA=? is <n>=0. If a second alarm time is set, the previous alarm will be deleted. Therefore, the

read command AT+CALA? will always return <n>=0. This is also true if individual settings are made on ASC0

and ASC1 or the various Multiplexer channels, for details see notes below.

<type>^(num)

Integer type value indicating the type of the alarm.

Alarm indication: text message via serial interface

<text>^(str)

String type value indicating the text to be displayed when alarm time is reached; maximum length is <tlength>.

By factory default, <text> is undefined.

Note: <text> will be stored to the non-volatile flash memory when the device enters the Power Down mode via

AT^SMSO. Once saved, it will be available upon next power-up, until you overwrite it by typing another text. This

eliminates the need to enter the full string when setting a fresh alarm.

<text> should not contain characters which are coded differently in ASCII and GSM (e.g. umlauts), see also

"Supported character sets" and "GSM alphabet tables".

<tlength>^(num)

Integer type value indicating the maximum length of <text>. The maximum length is 16.

Notes

• After the alarm was executed the parameter <time> of AT+CALA will be reset to "00/01/01,00:00:00", but

<text> will be preserved as described above.

• If TC65 is totally disconnected from power supply the most recently saved configuration of +CALA:

<time>[,<n>[,<type>[,<text>]]] will be presented when TC65 is powered up.

• Each time TC65 is restarted with ignition it takes 2s to re-initialize the RTC and to update the current time.

Therefore, it is recommended to wait 2s before using the commands AT+CCLK and AT+CALA (for example

2s after ^SYSSTART has been output).

Page 476 of 567

19.2 AT+CALA

• Alarm settings on ASC0 / ASC1 and different Multiplexer channels (see AT+CMUX):

- On each interface an individual <text> message can be stored, but only one time setting applies. This

means an alarm <time> set on one of the interfaces overwrites the time setting on all remaining inter-

faces. Therefore, the total number of alarm events returned by the read command AT+CALA? will always

be <n>=0, no matter whether different text messages are stored.

- When the scheduled alarm occurs, the ME sends the URC only on the interface where the most recent

alarm setting was made. The alarm time will be reset to "00/01/01,00:00:00" on all interfaces.

Examples

EXAMPLE 1

You may want to configure a reminder message for July 31, 2005, at 9.30h, including the message "Good

Morning".

AT+CALA="05/07/31,09:30:00",0,0,"Good Morning"

Do not switch off the GSM engine.When the alarm occurs the ME returns the following URC:

+CALA: Good Morning

EXAMPLE 2

To set a fresh alarm using the same message as in Example 1, simply enter date and time. <n>, <type>,

<text>, <tlength> can be omitted:

AT+CALA="05/07/31,08:50:00"

When the alarm is executed the URC comes with the same message:

+CALA: Good Morning

EXAMPLE 3

To enable the ME to wake up into Airplane mode, e.g. on July 20, 2005, at 8.30h, enter

AT+CALA="05/07/20,08:30:00"

Next, power down the ME:

AT^SMSO

^SMSO: MS OFF

^SHUTDOWN

When the alarm is executed the ME wakes up to Airplane mode and displays a URC. If available, this line is

followed by the individual <text> most recently saved. If no individual message was saved only the first line

appears.

"^SYSSTART AIRPLANE MODE"

+CALA: Good Morning

EXAMPLE 4

To delete an alarm before its scheduled time is reached enter an empty string for parameter <time>. This

will restore the default time and clear any individual message defined with <text>.

AT+CALA=""

AT+CALA?

+CALA: "00/01/01,00:00:00",0,0,""

Page 477 of 567

19.3 AT^SBC

19.3

AT^SBC Battery Charge Control

The functions of the AT^SBC differ depending on whether or not a battery is present.

• General functions:

The AT^SBC provides URCs used to alert the user of undervoltage and overvoltage conditions before the

module switches off. The automatic shutdown caused by undervoltage or overvoltage is equivalent to the

power-down initiated with the AT^SMSO command, i.e. ME logs off from the network and the software enters

a secure state avoiding loss of data. When the module is in IDLE mode it takes typically one minute to dereg-

ister from the network and to switch off. For further details regarding automatic shutdown and voltage ratings

please refer to the Hardware Interface Description [2].

The URCs do not need to activated by the TE. They will be output automatically when fault conditions occur.

• Functions available with battery connected:

The AT^SBC read command can be used to query the status of the battery and the charger.

The AT^SBC write command is important for entering the current consumption of the external application via

<current>. It should be noted that the charge control supported by TC65 works only if the requirements

described in the Hardware Interface Description [2] are met (battery type Lithium-Ion or Lithium Polymer,

presence of an NTC and protection circuit etc.) and if <current> is correctly specified. If the battery does

not incorporate an NTC, or the battery and the NTC are not compliant with the specified requirements the

battery cannot be detected by TC65.

Syntax

Test Command

AT^SBC=?

Response(s)

^SBC:(list of supported <bcs>s), (list of supported <bcl>s), (list of supported <mpc>s)

Read Command

AT^SBC?

Response(s)

^SBC: <bcs>, <bcl>, <mpc>

ERROR

+CME ERROR: <err>

Write Command

AT^SBC=<current>

Response(s)

ERROR

+CME ERROR: <err>

Reference(s)

PIN ASC0 ASC1

USB MUX1 MUX2 MUX3

Charge

Last

SIEMENS

Unsolicited Result Codes

URC 1

^SBC: Undervoltage

The message will be reported, for example, when the user attempts to set up a call while the voltage is close

to the critical limit and further power loss is caused during the transmit burst. When the external charging cir-

cuit includes an NTC connected to the BATT_TEMP pin, the URC appears several times before the module

switches off.

In applications which are not battery operated, i.e. where no NTC is connected to the BATT_TEMP pin, TC65

will present the undervoltage URC only once and will then switch off without sending any further messages.

Page 478 of 567

19.3 AT^SBC

URC 2

^SBC: Overvoltage warning

This URC is an alarm indicator displayed when the supply voltage approaches its maximum level. The URC

appears only once.

URC 3

^SBC: Overvoltage shutdown

This URC will be reported when the voltage exceeds the maximum level specified in the Hardware Interface

Description [2]. It appears only once before the module starts to perform an orderly shutdown.

In applications powered from Lithium batteries the incorporated protection circuit typically prevents over-

charging, thus eliminating the risk of overvoltage conditions. Yet, in case of charging errors, for example

caused by a bad battery or due to the absence of a battery protection circuit, the module's overvoltage shut-

down function will take effect to avoid overcharging.

Parameter Description

<bcs>^(num)

Connection status of battery pack

No charging adapter is connected

Charging adapter is connected

Charging adapter is connected, charging in progress

Charging adapter is connected, charging has finished

Charging error, charging is interrupted

False charging temperature, charging is interrupted while temperature is

beyond allowed range

<bcl>^(num)

Battery capacity

0, 20, 40, 60, 80, 100 percent of remaining capacity (6 steps).

0 indicates that either the battery is exhausted or the capacity value is not available.

While charging is in progress (charging adapter connected) the battery capacity is not available. Consequently,

parameter <bcl>=0. To query the battery capacity disconnect the charger.

<mpc>^(num)

Current consumption of the host application as specified with parameter <current>.

<current>^(num)

0^(P)...5000

Enter the current consumption of your host application in mA. This information

enables TC65 to correctly determine the end of charging and terminate charg-

ing automatically when the battery is fully charged. Note that if <current> is

inaccurate, and the application draws a current higher than the final charge

current, either charging will not be terminated or the battery fails to reach its

maximum voltage. Therefore, the termination condition is defined as: current

consumption dependent on operating mode of the ME plus current consump-

tion of the external application. If used, the current flowing over the VEXT pin

of the application interface must be added, too.

The specified value will also be displayed as parameter <mpc> of the AT^SBC

read command.

When the TC65 is powered down or reset, the value of <current> is restored

to its default. This affects the charging control. Therefore, the parameter should

be set every time when needed after rebooting the TC65.

Page 479 of 567

Siemens TC65 Terminal. Manual (Version: 02.000) - part 6