bgs3_atc_v01000a

BGS3

Version: 01.000aDocId: BGS3_ATC_V01.000a

AT

Com

man

d S

et

BGS3 AT Command Set

BGS3_ATC_V01.000a of 574 1/21/10Confidential / Released

GENERAL NOTE THE USE OF THE PRODUCT INCLUDING THE SOFTWARE AND DOCUMENTATION (THE "PRODUCT") ISSUBJECT TO THE RELEASE NOTE PROVIDED TOGETHER WITH PRODUCT. IN ANY EVENT THE PROVI-SIONS OF THE RELEASE NOTE SHALL PREVAIL. THIS DOCUMENT CONTAINS INFORMATION ON CIN-TERION PRODUCTS. THE SPECIFICATIONS IN THIS DOCUMENT ARE SUBJECT TO CHANGE ATCINTERION'S DISCRETION. CINTERION WIRELESS MODULES GMBH GRANTS A NON-EXCLUSIVERIGHT TO USE THE PRODUCT. THE RECIPIENT SHALL NOT TRANSFER, COPY, MODIFY, TRANSLATE,REVERSE ENGINEER, CREATE DERIVATIVE WORKS; DISASSEMBLE OR DECOMPILE THE PRODUCTOR OTHERWISE USE THE PRODUCT EXCEPT AS SPECIFICALLY AUTHORIZED. THE PRODUCT ANDTHIS DOCUMENT ARE PROVIDED ON AN "AS IS" BASIS ONLY AND MAY CONTAIN DEFICIENCIES ORINADEQUACIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, CINTERION WIRELESSMODULES GMBH DISCLAIMS ALL WARRANTIES AND LIABILITIES. THE RECIPIENT UNDERTAKES FORAN UNLIMITED PERIOD OF TIME TO OBSERVE SECRECY REGARDING ANY INFORMATION AND DATAPROVIDED TO HIM IN THE CONTEXT OF THE DELIVERY OF THE PRODUCT. THIS GENERAL NOTESHALL BE GOVERNED AND CONSTRUED ACCORDING TO GERMAN LAW.

CopyrightTransmittal, reproduction, dissemination and/or editing of this document as well as utilization of its contents andcommunication thereof to others without express authorization are prohibited. Offenders will be held liable forpayment of damages. All rights created by patent grant or registration of a utility model or design patent arereserved.

Copyright © 2010, Cinterion Wireless Modules GmbH

Trademark NoticeMicrosoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the UnitedStates and/or other countries. All other registered trademarks or trademarks mentioned in this document areproperty of their respective owners.

Document Name: BGS3 AT Command Set Version: 01.000a

Date: January 21, 2010

DocId: BGS3_ATC_V01.000a

Status Confidential / Released

BGS3 AT Command Set Contents


1. Introduction............................................................................................................................................ 141.1 Scope of the document ................................................................................................................. 141.2 Related documents ....................................................................................................................... 151.3 Document conventions.................................................................................................................. 16

1.3.1 Quick reference table..................................................................................................... 161.3.2 Superscript notation for parameters and values ............................................................ 17

1.4 AT Command Syntax .................................................................................................................... 181.4.1 Using Parameters .......................................................................................................... 181.4.2 Concatenating AT Commands....................................................................................... 19

1.5 Communication between Customer Application and BGS3.......................................................... 201.6 Supported character sets .............................................................................................................. 21

1.6.1 GSM alphabet tables and UCS2 character values ........................................................ 221.6.2 UCS2 and GSM data coding and conversion for SMS text mode and Remote SAT..... 241.6.2.1 Implementing output of SIM data to Terminal (direction TA to TE) ................................ 241.6.2.2 Implementing input of Terminal data to SIM (direction TE to TA)................................... 25

1.7 Unsolicited Result Code Presentation........................................................................................... 261.8 Errors and Messages .................................................................................................................... 271.9 Auxiliary Serial Interface................................................................................................................ 281.10 Serial Interface Flow Control ......................................................................................................... 29

1.10.1 Software Flow Control (XON/OFF Handshake)............................................................. 291.10.2 Hardware Flow Control (RTS/CTS Handshake) ............................................................ 29

1.11 Common PCN Handset Specification (CPHS) .............................................................................. 31

2. Configuration Commands..................................................................................................................... 322.1 AT&F Set all current parameters to manufacturer defaults ......................................................... 322.2 AT&V Display current configuration ............................................................................................ 33

2.2.1 AT&V responses............................................................................................................ 342.3 AT&W Stores current configuration to user defined profile ......................................................... 362.4 ATQ Result code presentation mode .......................................................................................... 372.5 ATV Result code format mode .................................................................................................... 38

2.5.1 Verbose and numeric result codes ................................................................................ 382.6 ATX Set CONNECT result code format and call monitoring ....................................................... 392.7 AT\V Set CONNECT result code format ..................................................................................... 402.8 ATZ Set all current parameters to user defined profile................................................................ 412.9 AT+CFUN Set phone functionality .............................................................................................. 42

2.9.1 Wake up the ME from SLEEP mode ............................................................................. 452.10 AT^SMSO Switch off mobile station............................................................................................ 462.11 AT+GCAP Request complete TA capabilities list........................................................................ 472.12 AT+CMEE Mobile Equipment Error Message Format ................................................................ 48

2.12.1 CME/CMS Error Code Overview ................................................................................... 492.13 AT+CSCS Select TE character set ............................................................................................. 562.14 AT^SCFG Extended Configuration Settings ............................................................................... 572.15 AT^SM20 Set M20 compatibility mode ....................................................................................... 74

3. Status Control Commands ................................................................................................................... 753.1 AT+CMER Mobile Equipment Event Reporting .......................................................................... 75

Contents



3.2 AT+CIND Indicator control .......................................................................................................... 773.3 AT^SIND Extended Indicator Control .......................................................................................... 803.4 AT+CEER Extended Error Report............................................................................................... 88

3.4.1 Cause Location ID for the extended error report ........................................................... 893.4.2 Proprietary L2 cause...................................................................................................... 903.4.3 GSM release cause for L3 Radio Resource (RR).......................................................... 903.4.4 Proprietary release cause for L3 Radio Resource (RR) ................................................ 913.4.5 GSM release cause for Mobility Management (MM) or Session Management (SM)..... 913.4.6 Proprietary release cause for L3 Mobility Management (MM) ....................................... 923.4.7 GSM release cause for L3 Call Control (CC)................................................................. 933.4.8 Proprietary release cause for L3 Call Control (CC) ....................................................... 943.4.9 GSM Release cause for Supplementary Service Call ................................................... 943.4.10 GSM release cause for Session Management (SM) ..................................................... 963.4.11 GSM cause for L3 Protocol module or other local cause ............................................. 963.4.12 Proprietary release cause for GPRS API....................................................................... 963.4.13 Proprietary release cause for PPP/IP-Stack.................................................................. 96

3.5 ATS18 Extended call release report............................................................................................ 973.6 AT+CPAS Mobile equipment activity status................................................................................ 993.7 AT+WS46 Select wireless network ........................................................................................... 100

4. Serial Interface Control Commands................................................................................................... 1014.1 ATE Enable command echo...................................................................................................... 1014.2 AT&C Set Data Carrier Detect (DCD) Line mode ..................................................................... 1024.3 AT&D Set Data Terminal Ready (DTR) line mode .................................................................... 1034.4 AT&S Set Data Set Ready (DSR) line mode............................................................................. 1044.5 AT\Q Flow control...................................................................................................................... 1054.6 AT+IFC Flow Control................................................................................................................. 1064.7 AT+ILRR Set TE-TA local rate reporting................................................................................... 1084.8 AT+IPR Bit Rate........................................................................................................................ 110

4.8.1 Autobauding................................................................................................................. 1114.9 AT+CMUX Multiplex Mode........................................................................................................ 113

4.9.1 Restrictions on Multiplex mode.................................................................................... 114

5. Security Commands............................................................................................................................ 1165.1 AT+CPIN PIN Authentication .................................................................................................... 116

5.1.1 What to do if PIN or password authentication fails? .................................................... 1185.2 AT+CPIN2 PIN2 Authentication ................................................................................................ 1205.3 AT^SPIC Display PIN counter ................................................................................................... 1225.4 AT+CLCK Facility lock .............................................................................................................. 1265.5 AT^SLCK Facility lock ............................................................................................................... 1315.6 AT+CPWD Change Password .................................................................................................. 1325.7 AT^SPWD Change Password................................................................................................... 1365.8 AT^SCSL Customer SIM Lock .................................................................................................. 138

6. Identification Commands.................................................................................................................... 1426.1 ATI Display product identification information ........................................................................... 1426.2 AT+CGMI Request manufacturer identification......................................................................... 1436.3 AT+GMI Request manufacturer identification ........................................................................... 1436.4 AT+CGMM Request model identification .................................................................................. 1446.5 AT+GMM Request model identification..................................................................................... 144



6.6 AT+CGMR Request revision identification of software status................................................... 1456.7 AT+GMR Request revision identification of software status ..................................................... 1456.8 AT+CGSN Request International Mobile Equipment Identity (IMEI) ......................................... 1466.9 AT+GSN Request International Mobile Equipment Identity (IMEI) ........................................... 1466.10 AT+CIMI Request International Mobile Subscriber Identity (IMSI)............................................ 147

7. Call related Commands....................................................................................................................... 1487.1 Call Status Information ................................................................................................................ 1487.2 ATA Answer a call ..................................................................................................................... 1497.3 ATD Mobile originated call to specified number ........................................................................ 1507.4 ATD><mem><n> Mobile originated call using specific memory and index number ................. 1527.5 ATD><n> Mobile originated call from active memory using index number ............................... 1547.6 ATD><str> Mobile originated call from active memory using corresponding field .................... 1557.7 ATDI Mobile originated call to ISDN number............................................................................. 1567.8 ATDL Redial last number used ................................................................................................. 1577.9 ATH Disconnect existing connection......................................................................................... 1587.10 AT+CHUP Hang up call ............................................................................................................ 1597.11 AT^SHUP Hang up call(s) indicating a specific GSM04.08 release cause ............................... 1607.12 ATS0 Set number of rings before automatically answering a call ............................................. 1617.13 ATS2 Set escape sequence character...................................................................................... 1627.14 ATS6 Set pause before blind dialing ......................................................................................... 1637.15 ATS7 Set number of seconds to wait for connection completion .............................................. 1647.16 ATS8 Set number of seconds to wait for comma dialing modifier............................................. 1657.17 ATS10 Set disconnect delay after indicating the absence of data carrier ................................. 1667.18 ATO Switch from command mode to data mode / PPP online mode........................................ 1677.19 +++ Switch from data mode or PPP online mode to command mode ...................................... 1687.20 AT+CBST Select bearer service type ....................................................................................... 1697.21 AT+CRLP Select radio link protocol parameters for originated non-transparent data calls ...... 1717.22 AT+CLCC List of current calls ................................................................................................... 1727.23 AT^SLCC Extended list of current calls .................................................................................... 1747.24 AT+CR Service reporting control .............................................................................................. 1797.25 AT+CRC Set Cellular Result Codes for incoming call indication .............................................. 1807.26 AT+CSNS Single Numbering Scheme...................................................................................... 1817.27 AT^SCNI List Call Number Information..................................................................................... 1827.28 AT^SLCD Display Last Call Duration ........................................................................................ 1837.29 AT^STCD Display Total Call Duration....................................................................................... 1847.30 ATP Select pulse dialing ........................................................................................................... 1857.31 ATT Select tone dialing ............................................................................................................. 185

8. Network Service Commands .............................................................................................................. 1868.1 AT+COPN Read operator names ............................................................................................. 1868.2 AT+COPS Operator Selection .................................................................................................. 1878.3 AT^SOPS Extended Operator Selection................................................................................... 1908.4 AT+CREG Network registration ................................................................................................ 1928.5 AT+CSQ Signal quality ............................................................................................................. 1958.6 AT^SMONC Cell Monitoring...................................................................................................... 1968.7 AT^SMOND Cell Monitoring...................................................................................................... 1988.8 AT^SFNUR Select the fixed network user rate ......................................................................... 2018.9 AT^MONI Monitor idle mode and dedicated mode ................................................................... 202

8.9.1 AT^MONI responses.................................................................................................... 203



8.9.2 Service states .............................................................................................................. 2048.10 AT^MONP Monitor neighbor cells ............................................................................................. 205

8.10.1 AT^MONP responses .................................................................................................. 2058.11 AT^SMONG Packet Data Monitor ............................................................................................. 207

8.11.1 AT^SMONG Cell Info Table......................................................................................... 2088.12 AT^SALS Alternate Line Service............................................................................................... 2098.13 AT^SHOM Display Homezone .................................................................................................. 2118.14 AT^SPLM Read the PLMN list .................................................................................................. 2128.15 AT+CPOL Preferred Operator List ............................................................................................ 213

9. Supplementary Service Commands .................................................................................................. 2149.1 AT+CACM Accumulated call meter (ACM) reset or query ........................................................ 2149.2 AT^SACM Advice of charge and query of ACM and ACMmax ................................................. 2159.3 AT+CAMM Accumulated call meter maximum (ACMmax) set or query.................................... 2179.4 AT+CAOC Advice of Charge information.................................................................................. 2189.5 AT+CCUG Closed User Group ................................................................................................. 2199.6 AT+CCFC Call forwarding number and conditions control ....................................................... 2219.7 AT+CCWA Call Waiting ............................................................................................................ 2259.8 AT+CHLD Call Hold and Multiparty........................................................................................... 2299.9 AT+CLIP Calling Line Identification Presentation ..................................................................... 2319.10 AT+CLIR Calling Line Identification Restriction ........................................................................ 2339.11 AT+COLP Connected Line Identification Presentation ............................................................. 2349.12 AT+CPUC Price per unit and currency table............................................................................. 2369.13 AT+CSSN Supplementary service notifications ........................................................................ 2389.14 AT+CUSD Unstructured supplementary service data............................................................... 240

10. Internet Service Commands ............................................................................................................... 24210.1 AT^SICS Internet Connection Setup Profile.............................................................................. 245

10.1.1 Example: Default values of a CSD connection profile ................................................. 24810.1.2 Example: GPRS connection profile ............................................................................. 249

10.2 AT^SICI Internet Connection Information.................................................................................. 25010.2.1 Checking Connection Profile Status ............................................................................ 251

10.3 AT^SISS Internet Service Setup Profile .................................................................................... 25310.4 AT^SISI Internet Service Information ........................................................................................ 26310.5 AT^SISO Internet Service Open ............................................................................................... 265

10.5.1 Example: Accepting / Rejecting Socket Connection Request from Remote Client ..... 26910.6 AT^SISC Internet Service Close ............................................................................................... 27110.7 AT^SISR Internet Service Read Data ....................................................................................... 272

10.7.1 Example: Socket Host Reads Small Amounts of UDP Data Packets (URC Mode)..... 27410.8 AT^SISW Internet Service Write Data....................................................................................... 275

10.8.1 Usage of parameter <eodFlag>................................................................................... 27710.9 AT^SIST Enter Transparent Access Mode ............................................................................... 27910.10 AT^SICO Internet Connection Open ......................................................................................... 28110.11 AT^SICC Internet Connection Close......................................................................................... 28310.12 AT^SISX Internet Service Execution......................................................................................... 284

10.12.1 Example: Ping.............................................................................................................. 28610.13 AT^SISE Internet Service Error Report ..................................................................................... 28710.14 Internet Service URC "^SIS" ....................................................................................................... 288

10.14.1 Information Elements Related to the Service Application............................................ 28910.14.2 Information Elements Related to FTP Service............................................................. 290



10.14.3 Information Elements Related to HTTP Service .......................................................... 29110.14.4 Information Elements Related to POP3 Service.......................................................... 29110.14.5 Information Elements Related to SMTP Service ......................................................... 291

10.15 Examples of how to Configure and Use Internet Service Profiles............................................... 29210.15.1 Selecting URC Mode or Polling Mode ......................................................................... 29210.15.2 Configuring Socket Listener......................................................................................... 29210.15.3 Configuring Socket Client for Calling a Socket Listener on Another Host ................... 29310.15.4 Socket Client Sends Data via TCP Connection (Polling Mode)................................... 29310.15.5 Socket client sends data via TCP connection with URCs............................................ 29410.15.6 Socket Scenario with UDP Endpoint ........................................................................... 29410.15.7 Configuring and Using FTP Download (URC Mode) ................................................... 29610.15.8 Configuring and Using FTP Upload (URC Mode)........................................................ 29610.15.9 Configuring SMTP Service Profile ............................................................................... 29710.15.10 Sending Email (URC Mode) ........................................................................................ 29810.15.11 Sending Email (Polling Mode) ..................................................................................... 29810.15.12 Configuring POP3 Service Profile................................................................................ 29910.15.13 Retrieving Email (URC Mode) ..................................................................................... 30110.15.14 Retrieving Email (Polling Mode) .................................................................................. 30110.15.15 HTTP POST (Polling Mode) ........................................................................................ 30210.15.16 HTTP GET (Polling Mode)........................................................................................... 30310.15.17 Creating Transparent TCP Socket Client .................................................................... 30410.15.18 Opening and Closing Transparent TCP Service.......................................................... 30410.15.19 Transparent TCP Client Receives Data While in AT Command Mode........................ 30510.15.20 Server Disconnects While Transparent TCP Service is in Transparent Access Mode 30610.15.21 Server Disconnects While Transparent TCP Service is in AT Command Mode and Data

is Pending .................................................................................................................... 307

11. GPRS Commands................................................................................................................................ 30911.1 AT+CGACT PDP context activate or deactivate ....................................................................... 30911.2 AT+CGANS Manual response to a network request for PDP context activation ...................... 31111.3 AT+CGATT GPRS attach or detach ......................................................................................... 31311.4 AT+CGAUTO Automatic response to a network request for PDP context activation ............... 31411.5 AT+CGDATA Enter data state .................................................................................................. 316

11.5.1 Automatic deactivation of PDP context during dial-up PPP......................................... 31711.6 AT+CGDCONT Define PDP Context ........................................................................................ 31811.7 AT+CGEQMIN Rel. 99 Quality of Service Profile (Minimum acceptable) ................................. 32011.8 AT+CGEQREQ Rel. 99 Quality of Service Profile (Requested)................................................ 32411.9 AT+CGPADDR Show PDP address ......................................................................................... 32811.10 AT+CGQMIN Quality of Service Profile (Minimum acceptable) ................................................ 32911.11 AT+CGQREQ Quality of Service Profile (Requested) .............................................................. 33311.12 AT+CGREG GPRS Network Registration Status...................................................................... 33711.13 AT+CGSMS Select service for MO SMS messages................................................................. 33911.14 AT^SGACT Query all PDP context activations ......................................................................... 34011.15 AT^SGAUTH Set type of authentication for PPP connection.................................................... 34211.16 AT^SGCONF Configuration of GPRS related Parameters ...................................................... 34311.17 ATA Manual response to a network request for PDP context activation................................... 34411.18 ATD*99# Request GPRS service.............................................................................................. 34511.19 ATD*98# Request GPRS IP service ......................................................................................... 34611.20 ATH Manual rejection of a network request for PDP context activation.................................... 34711.21 ATS0 Automatic response to a network request for PDP context activation............................. 348



11.22 Using GPRS AT commands (Examples)..................................................................................... 34911.23 Using the GPRS dial command ATD .......................................................................................... 351

12. FAX Commands................................................................................................................................... 35212.1 FAX parameters .......................................................................................................................... 352

12.1.1 Fax Result Codes ........................................................................................................ 35212.2 AT+FCLASS Fax: Select, read or test service class................................................................. 35312.3 AT+FRH Receive Data Using HDLC Framing .......................................................................... 35412.4 AT+FRM Receive Data ............................................................................................................. 35512.5 AT+FRS Receive Silence.......................................................................................................... 35612.6 AT+FTH Transmit Data Using HDLC Framing.......................................................................... 35712.7 AT+FTM Transmit Data............................................................................................................. 35812.8 AT+FTS Stop Transmission and Wait ....................................................................................... 359

13. Short Message Service (SMS) Commands........................................................................................ 36013.1 SMS parameters ......................................................................................................................... 36013.2 AT+CMGC Send an SMS command......................................................................................... 36513.3 AT+CMGD Delete short message............................................................................................. 36613.4 AT+CMGF Select SMS message format .................................................................................. 36713.5 AT+CMGL List SMS messages from preferred store................................................................ 36813.6 AT+CMGR Read SMS messages............................................................................................. 37013.7 AT+CMGS Send Short Message .............................................................................................. 37213.8 AT+CMGW Write Short Messages to Memory ......................................................................... 37413.9 AT+CMSS Send short messages from storage ........................................................................ 37613.10 AT+CNMA New Message Acknowledgement to ME/TE, only phase 2+ .................................. 37713.11 AT+CNMI New short Message Indication ................................................................................. 37813.12 AT+CPMS Preferred SMS message storage............................................................................ 38113.13 AT+CSCA SMS Service Center Address.................................................................................. 38313.14 AT+CSCB Select Cell Broadcast Message Indication .............................................................. 38413.15 AT+CSDH Show SMS text mode parameters........................................................................... 38513.16 AT+CSMP Set SMS text Mode Parameters.............................................................................. 38613.17 AT+CSMS Select Message Service.......................................................................................... 38813.18 AT^SCML List Concatenated Short Messages from preferred store ........................................ 39013.19 AT^SCMR Read Concatenated Short Messages ..................................................................... 39113.20 AT^SCMS Send Concatenated Short Messages...................................................................... 39213.21 AT^SCMW Write Concatenated Short Messages to Memory................................................... 39313.22 AT^SLMS List SMS Memory Storage ....................................................................................... 39413.23 AT^SMGL List Short Messages from preferred store without setting status to REC READ ..... 39513.24 AT^SMGO Set or query SMS overflow presentation mode or query SMS overflow ................. 39613.25 AT^SMGR Read short message without setting status to REC READ..................................... 39813.26 AT^SSCONF SMS Command Configuration ........................................................................... 39913.27 AT^SSDA Set SMS Display Availability .................................................................................... 40013.28 AT^SSMSS Set Short Message Storage Sequence ................................................................. 401

14. SIM related Commands....................................................................................................................... 40214.1 AT+CRSM Restricted SIM Access............................................................................................ 40214.2 AT^SATR Query SIM's Answer to Reset Data.......................................................................... 40514.3 AT^SXSM Extended SIM Access.............................................................................................. 40614.4 AT^SCKS Query SIM and Chip Card Holder Status ................................................................. 40814.5 AT^SCID Display SIM card identification number ..................................................................... 410



14.6 AT+CXXCID Display card ID..................................................................................................... 411

15. SIM Application Toolkit (SAT) Commands........................................................................................ 41215.1 Usage of Remote-SAT ................................................................................................................ 414

15.1.1 Automatic Response Mode (AR Mode) ....................................................................... 41415.1.2 Explicit Response Mode (ER Mode)............................................................................ 41415.1.3 Character Sets............................................................................................................. 41415.1.4 SIM Update Initiated by the Network ........................................................................... 41415.1.5 Icon Handling............................................................................................................... 41415.1.6 Using SMS Related AT Commands ............................................................................ 415

15.2 Remote-SAT States .................................................................................................................... 41615.2.1 Remote-SAT State Transition Diagram ....................................................................... 41715.2.2 Remote-SAT State Transition Table............................................................................ 418

15.3 Remote-SAT Command Types ................................................................................................... 42015.4 AT^SSTA Remote-SAT Interface Activation ............................................................................. 42215.5 ^SSTN SAT Notification ............................................................................................................ 42415.6 AT^SSTGI SAT Get Information ............................................................................................... 42615.7 AT^SSTGI SAT Get Information - Refresh (1) .......................................................................... 42715.8 AT^SSTGI SAT Get Information - Set Up Event List (5) ........................................................... 42915.9 AT^SSTGI SAT Get Information - Set Up Call (16)................................................................... 43015.10 AT^SSTGI SAT Get Information - Send SS (17)....................................................................... 43215.11 AT^SSTGI SAT Get Information - Send USSD (18) ................................................................. 43315.12 AT^SSTGI SAT Get Information - Send Short Message (19) ................................................... 43415.13 AT^SSTGI SAT Get Information - Send DTMF (20) ................................................................. 43515.14 AT^SSTGI SAT Get Information - Launch Browser (21) ........................................................... 43615.15 AT^SSTGI SAT Get Information - Play Tone (32)..................................................................... 43815.16 AT^SSTGI SAT Get Information - Display Text (33) ................................................................. 44015.17 AT^SSTGI SAT Get Information - Get Inkey (34) ..................................................................... 44215.18 AT^SSTGI SAT Get Information - Get Input (35) ...................................................................... 44415.19 AT^SSTGI SAT Get Information - Select Item (36) ................................................................... 44615.20 AT^SSTGI SAT Get Information - Set up Menu (37) ................................................................ 44815.21 AT^SSTGI SAT Get Information - Set up Idle Mode Text (40).................................................. 45015.22 AT^SSTGI SAT Get Information - Language Notification (53) .................................................. 45115.23 AT^SSTR SAT Response ......................................................................................................... 45215.24 AT^SSTR SAT Response - Refresh (1) .................................................................................... 45415.25 AT^SSTR SAT Response - Set Up Event List (5) ..................................................................... 45515.26 AT^SSTR SAT Response - Set Up Call (16) ............................................................................ 45615.27 AT^SSTR SAT Response - Send SS (17) ................................................................................ 45715.28 AT^SSTR SAT Response - Send USSD (18) ........................................................................... 45815.29 AT^SSTR SAT Response - Send Short Message (19) ............................................................. 45915.30 AT^SSTR SAT Response - Send DTMF (20) ........................................................................... 46015.31 AT^SSTR SAT Response - Launch Browser (21)..................................................................... 46115.32 AT^SSTR SAT Response - Play Tone (32) .............................................................................. 46215.33 AT^SSTR SAT Response - Display Text (33) ........................................................................... 46315.34 AT^SSTR SAT Response - Get Inkey (34) ............................................................................... 46415.35 AT^SSTR SAT Response - Get Input (35)................................................................................ 46515.36 AT^SSTR SAT Response - Select Item (36)............................................................................. 46615.37 AT^SSTR SAT Response - Setup Menu (37) ........................................................................... 46815.38 AT^SSTR SAT Response - Set Up Idle Mode Text (40) ........................................................... 469



15.39 AT^SSTR SAT Response - Language Notification (53) ............................................................ 47015.40 AT^SSTR SAT Event - Menu Selection (211) ........................................................................... 47115.41 AT^SSTR SAT Event - User Activity (232)................................................................................ 47215.42 AT^SSTR SAT Event - Idle Screen Available (233) .................................................................. 47315.43 AT^SSTR SAT Event - Language Selection (235) .................................................................... 47415.44 AT^SSTR SAT Event - Browser Termination (236) .................................................................. 47515.45 AT^SSTR SAT Event - Terminate Command (254) .................................................................. 47615.46 Examples for Using Remote-SAT ............................................................................................... 477

16. Phonebook Commands....................................................................................................................... 48016.1 Sort Order for Phonebooks ......................................................................................................... 48016.2 AT+CNUM Read own numbers................................................................................................. 48116.3 AT+CPBR Read from Phonebook............................................................................................. 48216.4 AT+CPBS Select phonebook memory storage ......................................................................... 48516.5 AT+CPBW Write into Phonebook ............................................................................................. 48716.6 AT^SPBW Write into Phonebook with location report ............................................................... 49016.7 AT^SDLD Delete the 'last number redial' memory .................................................................... 49316.8 AT^SPBC Find first matching entry in sorted phonebook ......................................................... 49416.9 AT^SPBD Purge phonebook memory storage.......................................................................... 49516.10 AT^SPBG Display phonebook entries in alphabetical order ..................................................... 49616.11 AT^SPBS Step through the selected phonebook alphabetically ............................................... 499

17. Audio Commands................................................................................................................................ 50317.1 Audio programming model .......................................................................................................... 50317.2 ATL Set monitor speaker loudness ........................................................................................... 50417.3 ATM Set monitor speaker mode................................................................................................ 50417.4 AT+CLVL Loudspeaker volume level ........................................................................................ 50517.5 AT+CMUT Mute control ............................................................................................................ 50617.6 AT+VTD Tone duration ............................................................................................................. 50717.7 AT+VTS DTMF and tone generation......................................................................................... 50817.8 AT^SAIC Audio Interface Configuration .................................................................................... 50917.9 AT^SNFA Set or query of microphone attenuation .................................................................. 51117.10 AT^SNFD Set audio parameters to manufacturer default values ............................................. 51317.11 AT^SNFG Generate Tone......................................................................................................... 51417.12 AT^SNFI Set microphone path parameters .............................................................................. 51617.13 AT^SNFM Set microphone audio path and power supply......................................................... 51717.14 AT^SNFO Set audio output (= loudspeaker path) parameter ................................................... 51917.15 AT^SNFPT Set progress tones ................................................................................................. 52117.16 AT^SNFS Select audio hardware set ........................................................................................ 52217.17 AT^SNFTTY Signal TTY/CTM audio mode capability............................................................... 52517.18 AT^SNFV Set loudspeaker volume........................................................................................... 52717.19 AT^SNFW Write audio setting in non-volatile store .................................................................. 52817.20 AT^SRTC Ring tone configuration ............................................................................................ 529

18. Hardware related Commands............................................................................................................. 53118.1 AT+CCLK Real Time Clock....................................................................................................... 53118.2 AT^SBC Battery Charge Control ............................................................................................... 532

18.2.1 Responses returned by read command....................................................................... 53418.3 AT^SBV Battery/Supply Voltage ............................................................................................... 53518.4 AT^SCTM Critical Operating Temperature Monitoring.............................................................. 536



18.4.1 Deferred shutdown ...................................................................................................... 53818.5 AT^SSYNC Configure SYNC Pin.............................................................................................. 539

18.5.1 ME status indicated by status LED patterns ................................................................ 540

19. Miscellaneous Commands.................................................................................................................. 54219.1 A/ Repeat previous command line ............................................................................................ 54219.2 ATS3 Set command line termination character......................................................................... 54319.3 ATS4 Set response formatting character .................................................................................. 54419.4 ATS5 Write command line editing character ............................................................................. 54519.5 AT^SFDL Enter Firmware Download Mode .............................................................................. 546

20. Appendix .............................................................................................................................................. 54720.1 Restricted access to SIM data after SIM PIN authentication....................................................... 54720.2 Star-Hash (*#) Network Commands............................................................................................ 54920.3 Available AT Commands and Dependency on SIM PIN ............................................................. 55220.4 AT Command Settings storable with AT&W................................................................................ 56020.5 Factory Default Settings Restorable with AT&F.......................................................................... 56320.6 Summary of Unsolicited Result Codes (URC)............................................................................. 56620.7 Alphabetical List of AT Commands ............................................................................................. 568

BGS3 AT Command Set List of Tables


Table 1.1: Symbols used to mark the type of parameters ........................................................................... 17Table 1.2: Symbols used to indicate the correlations with other commands ............................................... 17Table 1.3: Symbols used to mark different types of default values of parameters ..................................... 17Table 1.4: Types of AT commands and responses .................................................................................... 18Table 1.5: Examples for character definitions depending on alphabet ........................................................ 21Table 2.1: Current configuration on ASC0 / MUX channel 1 (example) ...................................................... 34Table 2.2: Current configuration on ASC1 and MUX channels 2 and 3 (example) .................................... 35Table 2.3: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes ................................................. 45Table 2.4: General "CME ERROR" Codes (GSM 07.07) .......................................................................... 49Table 2.5: General "CME ERROR" Codes (proprietary) ........................................................................... 50Table 2.6: GPRS related "CME ERROR" Codes (GSM 07.07) ................................................................. 51Table 2.7: GPRS related "CME ERROR" Codes (proprietary) .................................................................. 51Table 2.8: SMS related "CMS ERROR" Codes (GSM 07.05) ................................................................... 53Table 4.1: Availability of AT Commands on Virtual Channels .................................................................. 114Table 4.2: Summary of AT commands with Different Behavior in Multiplex Mode ................................... 114Table 10.1: Applicability of AT^SICS <conParmTag> values ................................................................... 245Table 10.2: Applicability of AT^SISS <srvParmTag> values ................................................................... 253Table 12.1: Fax Result Codes ..................................................................................................................... 352Table 15.1: State: RESET description ......................................................................................................... 418Table 15.2: State: OFF description.............................................................................................................. 418Table 15.3: State: IDLE description ............................................................................................................. 418Table 15.4: State: PAC description.............................................................................................................. 419Table 15.5: State: WAIT description ............................................................................................................ 419Table 15.6: Command Type Table .............................................................................................................. 420Table 18.1: Modes of the LED and indicated ME functions......................................................................... 540Table 20.1: Star-Hash (*#) Command Overview ........................................................................................ 549Table 20.2: Abbreviations of Codes and Parameters used in Table 20.1 .................................................. 550Table 20.3: Star-Hash Command Response Parameters .......................................................................... 551Table 20.4: Star-Hash Commands for Supplementary Services ................................................................ 551Table 20.5: Available AT Commands and Dependency on SIM PIN........................................................... 552Table 20.6: Settings Stored to User Profile on ASC0 / MUX Channel 1...................................................... 560Table 20.7: Settings Stored to User Profile on ASC1 / MUX Channels 2 and 3.......................................... 561Table 20.8: Factory Default Settings Restorable with AT&F ....................................................................... 563Table 20.9: Summary of Unsolicited Result Codes (URC) .......................................................................... 566Table 20.10: Alphabetical List of AT Commands........................................................................................... 568

List of Tables

BGS3 AT Command Set List of Figures


Figure 1.1: Main character table of GSM 03.38 alphabet ............................................................................. 22Figure 1.2: Extension character table of GSM 03.38 alphabet ..................................................................... 23Figure 15.1: Remote-SAT Context diagram.................................................................................................. 413Figure 15.2: Remote-SAT State Transition Diagram .................................................................................... 417Figure 17.1: Audio programming model for BGS3 Module ........................................................................... 503

List of Figures

BGS3 AT Command Set 1. Introduction


1. Introduction

1.1 Scope of the document

This document presents the AT Command Set for BGS3 Release 01.000a.

Before using the product or upgrading to a new firmware version please read the latest product information pro-vided in the Release Notes [1].

More information is available at http://www.cinterion.com.

http://www.cinterion.com

BGS3 AT Command Set 1.2 Related documents


1.2 Related documents

[1] BGS3 Release Notes, Version 01.000a[2] BGS3 Hardware Interface Description, Version 01.000a[3] GPRS Startup User's Guide[4] Multiplexer User's Guide [5] 3GPP TS 27.010 (GSM 07.10): Terminal Equipment to User Equipment (TE-UE) multiplexer protocol [6] Multiplex Driver Developer's Guide [7] Multiplex Driver Installation Guide [8] Application Note 02: Audio Interface Design[9] Application Note 16: Updating BGS3 Firmware

[10] Application Note 22: Using TTY / CTM equipment with BGS3[11] Application Note 24: Application Developer's Guide[12] ISO/IEC10646: "Universal Multiple-Octet Coded Character Set (UCS)"; UCS2, 16 bit coding [13] ITU-T Recommendation V.24: List of definitions for interchange circuits between data terminal equipment

(DTE) and data circuit-terminating equipment (DCE) [14] ITU-T Recommendation V.250: Serial asynchronous automatic dialling and control [15] 3GPP TS 100 918/EN 300 918 (GSM 02.04): General on supplementary services [16] 3GPP TS 100 907 (GSM 02.30): Man-Machine Interface (MMI) of the Mobile Station (MS) [17] 3GPP TS 23.038 (GSM 03.38): Alphabets and language specific information [18] 3GPP TS 27.005 (GSM 07.05): Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE

- DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) [19] 3GPP TS 27.007 (GSM 07.07): AT command set for User Equipment (UE) [20] 3GPP TS 27.060 (GSM 07.60): Mobile Station (MS) supporting Packet Switched Services [21] 3GPP TS 51.011 (GSM 11.11): Specification of the Subscriber Identity Module - Mobile Equipment (SIM -

ME) interface [22] 3GPP TS 11.14 (GSM 11.14): Specification of the SIM Application Toolkit for the Subscriber Identity Module

- Mobile Equipment (SIM - ME) interface [23] 3GPP TS 22.101 (GSM 22.101): Service principles [24] Common PCN Handset Specification (CPHS) v4.2

BGS3 AT Command Set 1.3 Document conventions


1.3 Document conventions

Throughout the document, the GSM engines are referred to as ME (Mobile Equipment), MS (Mobile Station), TA(Terminal Adapter), DCE (Data Communication Equipment) or facsimile DCE (FAX modem, FAX board). To control your GSM engine you can simply send AT Commands via its serial interface. The controlling deviceat the other end of the serial line is referred to as TE (Terminal Equipment), DTE (Data Terminal Equipment) orplainly 'the application' (probably running on an embedded system). All abbreviations and acronyms used throughout this document are based on the GSM specifications. For defi-nitions please refer to TR 100 350 V7.0.0 (1999-08), (GSM 01.04, version 7.0.0 release 1998).

1.3.1 Quick reference table

Each AT command description includes a table similar to the example shown below. The table is intended as aquick reference to indicate the following functions:

Example:

PIN: Is the AT command PIN protected? + Yes - No ± Usage is dependent on conditions specified for the command, or not all command types are PIN

protected (for example write command PIN protected, read command not). Note: The table provided in Section 20.3, Available AT Commands and Dependency on SIM

PIN uses the same symbols.ASC0: Is the AT command supported on the first physical serial interface ASC0? + Yes - NoASC1: Is the AT command supported on the second physical serial interface ASC1? + Yes - NoMUXn: Is the AT command usable on the Multiplexer channels MUX1, MUX2, MUX3? + Yes

- No ± AT command is usable, but under the restrictions specified in the section related to the command. Note: The columns MUX1, MUX2 and MUX3 are relevant only when the GSM engine operates in Mul-

tiplexer mode, that is, when the first physical serial interface is partitioned into 3 virtual channels by using the Multiplexer protocol. Usage is the same on ASC0 and MUX1.

Charge: Is the AT command supported in CHARGE ONLY mode? + Yes - No ± AT command is usable, but under the restrictions specified in the section related to the command. Last: If commands are concatenated, this AT command must be the last one. + Yes - No Note: See also Section 1.4, AT Command Syntax for details on concatenated AT commands.

PIN ASC0 ASC1 MUX1 MUX2 MUX3 Charge Last

- + + ± ± ± + -

BGS3 AT Command Set 1.3 Document conventions


1.3.2 Superscript notation for parameters and valuesTable 1.1: Symbols used to mark the type of parameters

Table 1.2: Symbols used to indicate the correlations with other commands

Table 1.3: Symbols used to mark different types of default values of parameters

Parameter type Meaning<param>(num) Parameter value must be numeric type<param>(str) Parameter value must be string type

Parameter option Meaning<param>(&W) Parameter value will be stored with AT&W<param>(&V) Parameter value will be displayed with AT&V<param>(ˆSNFW) Parameter value will be stored with AT^SNFW<param>(+CSCS) Parameter value has to be (is) coded according to current setting of <chset> (see

AT+CSCS for details)

Value option Meaning[x] Default value: if the parameter is omitted, the value 'x' will be assumedx(&F) Factory default value, will be restored to 'x' with AT&Fx(P) Powerup default value of a parameter which is not stored at power downx(D) Delivery default value of a parameter which cannot be restored automatically

BGS3 AT Command Set 1.4 AT Command Syntax


1.4 AT Command Syntax

The "AT" or "at" prefix must be set at the beginning of each command line. To terminate a command line enter<CR>. Commands are usually followed by a response that includes "<CR><LF><response><CR><LF>". Through-out this document, only the responses are presented, <CR><LF> are omitted intentionally.

Table 1.4: Types of AT commands and responses

1.4.1 Using Parameters

• Optional parameters are enclosed in square brackets. If optional parameters are omitted, the current settingsare used until you change them.

• Optional parameters or subparameters can be omitted unless they are followed by other parameters. If youwant to omit a parameter in the middle of a string it must be replaced by a comma. See also example 1.

• A parameter value enclosed in square brackets represents the value that will be used if an optional parameteris omitted. See also example 2.

• When the parameter is a character string, e.g. <text> or <number>, the string must be enclosed in quotationmarks, e.g. "Charlie Brown" or "+49030xxxx". Symbols in quotation marks will be recognized as strings.

• All spaces will be ignored when using strings without quotation marks.• It is possible to omit the leading zeros of strings which represent numbers.• If an optional parameter of a V.250 command is omitted, its value is assumed to be 0.Example 1: Omitting parameters in the middle of a string

Example 2: Using default parameter values for optional parameters

AT command type Syntax FunctionTest command AT+CXXX=? The mobile equipment returns the list of parameters and value

ranges set with the corresponding Write command or by internal processes.

Read command AT+CXXX? This command returns the currently set value of the parameter or parameters.

Write command AT+CXXX=<...> This command sets user-definable parameter values.Exec(ution) command AT+CXXX The execution command reads non-variable parameters deter-

mined by internal processes in the GSM engine.

AT+CCUG? Query current setting+CCUG: 1,10,1OKAT+CCUG=,9 Set only the middle parameterOKAT+CCUG? Query new setting+CCUG: 1,9,1OK

AT+CFUN=7,0 Activate CYCLIC SLEEP mode, don't reset MEOKAT+CFUN? Query ME mode+CFUN: 7 OKAT+CFUN= Set ME back to normal (default parameters: 1,0)OK+CFUN: 1OK

BGS3 AT Command Set 1.4 AT Command Syntax


1.4.2 Concatenating AT Commands

Concatenating AT commands on the same line is possible, though not recommended because of restrictionslisted below (for more details see [14]).When concatenating AT commands you need to enter the "AT" or "at" prefix only once at the beginning of a com-mand line. Basic commands (i.e., V.250 commands) are concatenated without delimiter. Extended commands(i.e., commands starting with AT+ or AT^) use a semicolon as delimiter.

Disadvantages and restrictions: • There is no way to control the minimum time to wait between finishing an AT command and sending the next

one. Please refer to Section 1.5, Communication between Customer Application and BGS3 for details abouttiming.

• The sequence of processing the AT commands may be different from the sequential order of command input.• Many AT commands cannot be concatenated (see list below). Concatenating these commands might end up

with an error result code, or leads to an unexpected order of responses.

AT command type CommentV.250 commands Cannot be concatenated with FAX commands (prefix

AT+F)GSM 7.07 commands Cannot be concatenated with extended commands

(prefix AT^S)GSM 7.05 commands (SMS) To be used standaloneCommands starting with AT& To be used standaloneAT+IPR To be used standalone

BGS3 AT Command Set 1.5 Communication between Customer Application and BGS3


1.5 Communication between Customer Application and BGS3

Leaving hardware flow control unconsidered the Customer Application (TE) is coupled with the BGS3 (ME) viaa receive and a transmit line. Since both lines are driven by independent devices collisions may (and will) happen. For example, if the TEissues an AT command the BGS3 starts sending a URC. This will probably cause the TE to misinterpret the URCbeing part of the AT command's response. To avoid this conflict the following measures must be taken: • If an AT command is finished (with "OK" or "ERROR") the TE shall always wait at least 100 ms before sending

the next one. This applies to bit rates of 9600 bps or higher (see AT+IPR). At bit rates below 9600 bps thedelay must be longer: 300 ms at 1200 bps, and 500 ms at 300 bps. The pause between two AT commands gives the BGS3 the opportunity to the transmission of pending URCsand get necessary service. Note that some AT commands may require more delay after "OK" or "ERROR" response, refer to the followingcommand specifications for details.

• The TE shall communicate with the BGS3 using activated echo (ATE1), i.e. the BGS3 echoes charactersreceived from the TE. Hence, when the TE receives the echo of the first character "A" of the AT command just sent by itself it hascontrol both over the receive and the transmit paths.

Using Backspace at command line: • As the standard GSM alphabet does not provide a backspace functionality the BGS3 is designed to use the

character "08" (hex 0x08) as backspace for command line input. This allows the user to easily erase the lastcharacter when writing an AT command. On the other hand, this solution requires entering the escapesequence \08 for writing the "ò" character in GSM character string parameters.

Software flow control: • Regardless of the selected alphabet, keep in mind that, when software flow control is activated, decimal 17

and 19 are interpreted as XON/XOFF control characters.

BGS3 AT Command Set 1.6 Supported character sets


1.6 Supported character sets

The ME supports two character sets: GSM 03.38 (7 bit, also referred to as GSM alphabet or SMS alphabet) andUCS2 (16 bit, refer to ISO/IEC 10646). See AT+CSCS for information about selecting the character set. Charactertables can be found below.

Explanation of terms • International Reference Alphabet (IRA)

IRA means that one byte is displayed as two characters in hexadecimal format. For example, the byte 0x36(decimal 54) is displayed as "36" (two characters). IRA is used here for input 8-bit or 16-bit data via terminaldevices using text mode. This means only characters 'A'..'F','a'..'f' and '0'..'9' are valid.

• Escape sequencesThe escape sequence used within a text coded in the GSM default alphabet (0x1B) must be correctly inter-preted by the TE, both for character input and output. To the module, an escape sequence appears like anyother byte received or sent.

• Terminal Adapter (TA)TA is an equivalent term for Mobile Equipment (ME) which stands for the BGS3 module.

• Terminal Equipment (TE)TE is the device connected to the TA via serial interface.

• TE Character SetThe character set currently used by Terminal Equipment is selected with AT+CSCS.

• Data Coding Scheme (dcs)DCS is part of a short message and is saved on the SIM. When writing a short message to the SIM in textmode, the dcs stored with AT+CSMP is used and determines the coded character set.

When you enter characters that are not valid characters of the supported alphabets the behavior is undefined. If the GSM alphabet is selected, all characters sent over the serial line (between TE and TA) must be in the rangefrom 0 to 127 (7 bit range). Note: If the ME (TA) is configured for GSM alphabet, but the application (TE) uses ASCII, bear in mind that somecharacters have different code values, such as the following: • "@" character with GSM alphabet value 0 is not printable by an ASCII terminal program (e.g. Microsoft©

Hyperterminal®).• "@" character with GSM alphabet value 0 will terminate any C string! This is because value 0 is defined as C

string end tag. Therefore, the GSM Null character may cause problems on application level when using a 'C'-function as "strlen()". Using an escape sequence as shown in the table below solves the problem. By the way,this may be the reason why even network providers often replace "@"with "@=*" in their SIM application.

• Some other characters of the GSM alphabet may be misinterpreted by an ASCII terminal program. For exam-ple, GSM "ö" (as in "Börse") is assumed to be "|" in ASCII, thus resulting in "B|rse". This is because in bothalphabets there are different characters assigned to hex values 7C or 00.

When you write characters differently coded in ASCII and GSM (e.g. Ä, Ö, Ü), you need to enter escapesequences. The escape sequence will be translated into the corresponding GSM character value that can becorrectly represented by any program using the GSM alphabet. However, trying to read the same string with anASCII terminal delivers a wrong character.

Table 1.5: Examples for character definitions depending on alphabet

Some terminal programs do not recognize escape sequences, and thus, handle escape sequences as normalcharacters. Ways of writing escape sequences depend on the used terminal program. To prevent misinterpretation of control characters or special characters it is recommended to prefer the USC2alphabet and/or PDU mode in any external application.

GSM 03.38character

GSM characterhex. value

CorrespondingASCII character

ASCIIEsc sequence

Hex Escsequence

Ö 5C \ \5C 5C 35 43" 22 " \22 5C 32 32@ 00 NULL \00 5C 30 30



1.6.1 GSM alphabet tables and UCS2 character values

This section provides tables for the GSM 03.38 alphabet supported by the ME. Below any GSM character findthe corresponding two byte character value of the UCS2 alphabet. (For related mapping definition see: http://www.unicode.org/Public/MAPPINGS/ETSI/GSM0338.TXT)

1) This code is an escape to the following extension of the 7 bit default alphabet table.2) This code is not a printable character and therefore not defined for the UCS2 alphabet. It shall be treated as the accom-

panying control character.3) See Section 1.5, Communication between Customer Application and BGS3 for further details on using backspace and

"ò" character.

Figure 1.1: Main character table of GSM 03.38 alphabet



1) This code value is reserved for the extension to another extension table. On receipt of this code, a receiving entity shalldisplay a space until another extension table is defined.

2) This code represents the EURO currency symbol. The code value is the one used for the character 'e'. Therefore a receiv-ing entity which is incapable of displaying the EURO currency symbol will display the character 'e' instead.

3) This code is defined as a Page Break character and may be used for example in compressed CBS messages. Any mobilewhich does not understand the 7 bit default alphabet table extension mechanism will treat this character as Line Feed.

Figure 1.2: Extension character table of GSM 03.38 alphabet



In the event that an MS receives a code where a symbol is not represented in Figure 1.2, Extension charactertable of GSM 03.38 alphabet the MS shall display the character shown in the main default 7 bit alphabet table(see Figure 1.1, Main character table of GSM 03.38 alphabet).

1.6.2 UCS2 and GSM data coding and conversion for SMS text mode and Remote SAT

This section provides basic information on how to handle input and output character conversion for SMS textmode and Remote SAT if internal (TA) and external (TE) character representation differ, i.e. if the Data CodingScheme and the TE character use different coding.

1.6.2.1 Implementing output of SIM data to Terminal (direction TA to TE)

Note: The ratio of SIM bytes to output bytes is given in parentheses.

Case 1Every GSM character is sent to the TE as it is (8-bit value with highest bit set to zero).Example: 47'H, 53'H, 4D'H → 47'H, 53'H, 4D'H, displayed as "GSM"

Case 2Every data byte is sent to the TE as 2 IRA characters each representing a halfbyte.Example: B8'H (184 decimal) → 42'H, 38'H, displayed as "B8"

Case 3Every 16-bit UCS2 value is sent to the TE as 4 IRA characters.Example: C4xA7'H (50343 decimal) → 43'H, 34'H, 41'H, 37'H, displayed as "C4A7"Problem: An odd number of bytes leads to an error because there are always two bytes needed for each USC2character

Case 4Every GSM character is sent to the TE as 4 IRA characters to show UCS2 in text mode.Example: 41'H ("A") → 30'H, 30'H, 34'H, 31'H, displayed as "0041"

Case 5Every data byte is sent to the TE as IRA representation of UCS2 (similar to case 4).Example: B2'H → 30'H, 30'H, 42'H, 32'H, displayed as "00B2"

Case 6Every 16-bit value is sent to the TE as IRA representation of it. It is assumed that number of bytes is even.Example: C3x46'H → 43'H, 33'H, 34'H, 36'H, displayed as "C346"

Used character set DCS = 7 bitGSM

DCS = 8 bitData

DCS = 16 bitUCS2

GSM Case 1GSM (1:1)

Case 28 bit to IRA (1:2)

Case 3UCS2 to IRA (2:4)

UCS2 Case 4GSM to IRA (1:4)

Case 58 bit to IRA (1:4)

Case 6UCS2 to IRA (2:4)



1.6.2.2 Implementing input of Terminal data to SIM (direction TE to TA)

Note: The ratio between the number of input characters and bytes stored on the SIM is given in parentheses.

Case 1Every character is sent from TE to TA as GSM character (or ASCII with standard terminal emulation, e.g. Hyper-terminal).Character value must be in range from 0 to 127 because of 7-bit GSM alphabet.To reach maximum SMS text length of 160 characters in 140 bytes space characters will be compressed on SIM.This must be set using the parameter <dcs> of AT+CSMP (add 64).Example: "ABCDEFGH" typed is sent and stored uncompressed as → 4142434445464748'H (stored com-pressed as 41E19058341E91'H)

Case 2Every data byte is sent as 2 IRA characters.Maximum text length is 280 IRA characters which will be converted into 140 bytes SMS binary user dataExample: "C8" typed is sent as 43'H, 38'H → stored as C8'H

Case 3Every 16-bit value is sent as 4 IRA characters.Maximum text length is 280 IRA characters which will be converted into 70 UCS2 characters (16-bit each)Number of IRA characters must be a multiple of four because always 4 half bytes are needed for a 16-bit valueExample: "D2C8" typed is sent as 44'H, 32'H, 43'H, 38'H → stored as D2C8'H

Case 4Every GSM character is sent as 4 IRA characters representing one UCS2 character.Example: To store text "ABC" using UCS2 character set you have to type "004100420043".This is sent as 30'H,30'H,34'H,31'H, 30'H,30'H,34'H,32'H, 30'H,30'H,34'H,33'H → detected as IRA representa-tion of 3 UCS2 characters, converted to GSM character set and stored as 41'H, 42'H, 43'H.Maximum input is 640 IRA characters repesenting 160 UCS2 characters when compression is active. These areconverted to 160 GSM 7-bit characters.Without compression only 140 GSM characters can be stored which are put in as 560 IRA characters.Values of UCS2 characters must be smaller than 80'H (128 decimal) to be valid GSM characters.Number of IRA characters must be a multiple of four. Problems:• "41" → Error, there are four IRA characters (two bytes) needed• "0000" → Error, not an UCS2 character• "4142" → Error, value of UCS2 character > 7F'H• "008B" → Error, value of UCS2 character > 7F'H This affects the maximum input length of a string)

Case 5Every UCS2 character is sent as 4 IRA characters and is converted into two 8-bit values. This means that thefirst two characters have to be '00'.Example: UCS2 character 009F'H typed as "009F" is sent as 30'H,30'H,39'H,46'H → converted into 8-bit value9F'H.Maximum number of UCS2 characters is 140 which are represented by 560 IRA characters. Number of IRA char-acters must be a multiple of four.

Case 6Every UCS2 character is sent as 4 IRA characters each and is converted into a 16-bit value again.Example: UCS2 character 9F3A'H typed as "9F3A" is sent as 39'H,46'H,33'H,41'H → converted into 9F3A'H.Maximum number of UCS2 characters is 70 which are represented by 280 IRA characters. Number of IRA char-acters must be a multiple of four.Invalid UCS2 values must be prevented.

Used character set DCS = 7 bitGSM

DCS = 8 bitData

DCS = 16 bitUCS2

GSM Case 1GSM (1:1)

Case 2IRA to 8 bit (2:1)

Case 3IRA to 16 bit (4:2)

UCS2 Case 4UCS2 to GSM (4:1)

Case 5UCS2 to 8 bit (4:1)

Case 6UCS2 to 16 bit (4:2)

BGS3 AT Command Set 1.7 Unsolicited Result Code Presentation


1.7 Unsolicited Result Code Presentation

URC stands for Unsolicited Result Code and is a report message issued by the ME without being requested bythe TE, i.e. a URC is issued automatically when a certain event occurs. Hence, a URC is not issued as part ofthe response related to an executed AT command. Typical events leading to URCs are incoming calls ("RING"), waiting calls, received short messages, changes intemperature, network registration etc. A list of all URCs can be found in Section 20.6, Summary of Unsolicited Result Codes (URC).

To announce a pending URC transmission the ME will do the following: • The ME activates its RING line (logic "1") for 1 second, i.e. the RING line changes to the physical "Low" level.

This allows the TE to stay in power saving mode until an ME related event requests service. If several URCs occur coincidently or in quick succession each URC triggers the RING line independently,although the line will not be deactivated between each URC. As a result, the RING line may stay low for morethan 1 second. If an incoming call is answered within less than 1 second (with ATA or if autoanswering is set to ATS0=1) thanthe RING line will be deactivated earlier.The "^SHUTDOWN" URC will not activate the RING line.

• If the AT command interface is busy a "BREAK" will be sent immediately but the URC will not be issued untilthe line is free. This may happen if the URC is pending in the following cases: - During the processing of an AT command (i.e. the time after the TE echoes back the first character "A" of

an AT command just sent by itself until the ME responds with "OK" or "ERROR"). - During a data call. Please note that AT command settings may be necessary to enable in-band signaling, e.g. refer to AT+CMERor AT+CNMI.

It is strongly recommended to use the multiplex mode to map logical communication channels onto the serial lineof the BGS3, for details refer to [4] and AT command AT+CMUX. Doing so it is possible to use one channel to stillprocess URCs while having a data call active on another.For most of these messages, the ME needs to be configured whether or not to send a URC. Depending on theAT command, the URC presentation mode can be saved to the user defined profile (see AT&W), or needs to beactivated every time you reboot the ME. Several URCs are not user definable, such as "^SYSSTART","^SYSSTART <text>", "^SHUTDOWN". If autobauding is enabled ( AT+IPR=0), URCs generated after restart will be output with 115200 bps until the MEhas detected the current bit rate. The URCs "^SYSSTART", "^SYSSTART <text>", however, are not presentedat all. For details please refer to Section 4.8.1, Autobauding. To avoid problems we recommend to configure afixed bit rate rather than using autobauding.

BGS3 AT Command Set 1.8 Errors and Messages


1.8 Errors and Messages

The command result codes "+CME ERROR: <err>" and "+CMS ERROR: <err>" indicate errors related to mobileequipment or network functionality.

The format of <err> can be either numeric or verbose and is selectable via AT+CMEE.

A result error code terminates the execution of the command and prevents the execution of all remaining com-mands that may follow on the same command line. If so, neither "ERROR" nor "OK" result codes are returnedfor these commands. A 30 seconds timeout will deliver "ERROR" when the input of a command is not complete.

Using the wrong command syntax may result in errors: For example, using the execute command syntaxalthough the command has no execute format, causes "ERROR" to be returned. Likewise, using the write com-mand syntax although the command has no write format causes "+CME ERROR: <err>" to be returned.

See also: • Section 2.12.1, CME/CMS Error Code Overview• Section 2.5.1, Verbose and numeric result codes• Section 3.4, AT+CEER

BGS3 AT Command Set 1.9 Auxiliary Serial Interface


1.9 Auxiliary Serial Interface

The second serial interface (ASC1) is designed as an additional interface for applications which need multipleparallel access to the BGS3, e.g. to query status information while a data connection is in progress on ASC0.However, the auxiliary interface provides only limited functionality: • Multiplex mode via AT+CMUX is not supported. • DTR, DSR, DCD, RING hardware lines do not exist. AT commands for controlling the behavior of these lines

(AT&D, AT&C, AT&S) can be used but will have no effect.• CSD calls are not supported.• Fax calls are not supported.• When you set up packet switched connections take care that your application uses only AT commands,

parameters and signal lines supported on the ASC1 interface. For example, keep in mind that Microsoft Dial-up connections are typically trying to request the DCD line status and that common modem drivers use tosend commands such as AT+CBST or ATS7, which may not be supported.

• No Autobauding. The hardware is not capable of automatically detecting the baudrate on this interface, sothe AT command which selects autobauding (AT+IPR=0) is not allowed and returns ERROR.

ASC1 is disabled when the multiplexer is enabled on the first serial interface ASC0. Yet, both ASC1 and the mul-tiplexer channel 2 are using the same parameters, and thus, the same user defined profile (if any). As a result,a user profile stored on multiplexer channel 2 takes effect on ASC1 after closing the multiplexer and starting upASC1. Likewise, a user profile stored on ASC1 will be loaded on multiplexer channel 2.This may be a problem when ASC1 is not connected, but flow control (for example AT\Q1 or AT\Q3) is stored tothe user profile on the multiplexer channel 2. In this case, flow control takes effect on ASC1, when the multiplexeris switched off. If then for example a large amount of URCs is generated, their transmission might be stoppeddue to the flow control. To avoid this problem we recommend that you do not activate flow control on multiplexerchannel 2 when you set up a user profile with AT&W.

BGS3 AT Command Set 1.10 Serial Interface Flow Control


1.10 Serial Interface Flow Control

Flow control is essential to prevent loss of data or avoid errors when, in a data or fax call, the sending device istransferring data faster than the receiving side is ready to accept. When the receiving buffer reaches its capacity,the receiving device should be capable to cause the sending device to pause until it catches up. There are basically two approaches to regulate data flow: Software flow control and hardware flow control. TheHigh Watermark (HWM) of the input/output buffer should be set to approximately 60% of the total buffer size, theLow Watermark (LWM) is recommended to be about 30%. The data flow should be stopped when the buffercapacity rises close to the High Watermark and resumed when it drops below the Low Watermark. The timerequired to cause stop and go results in a hysteresis between the High and Low Watermarks.

1.10.1 Software Flow Control (XON/OFF Handshake)

Software flow control can be used to control the data flow in both directions from DTE to BGS3 and from BGS3to DTE. Software flow control uses different characters to stop (XOFF, decimal 19) and resume (XON, decimal17) data flow. Hence, all data that represent XON or XOFF characters will be interpreted as control characters.This applies also to characters included within the data stream to be transmitted (usually plain ASCII text files donot inlude such characters). The only advantage of software flow control is that three wires would be sufficienton the serial interface.

1.10.2 Hardware Flow Control (RTS/CTS Handshake)

Hardware flow control sets or resets the RTS/CTS wires. This approach is faster and more reliable, and there-fore, the better choice. When the HWM is reached, CTS is set inactive. When the LWM is passed, CTS goesactive again. To achieve smooth data flow, ensure that the RTS/CTS lines are present on your application plat-form.

Configuring hardware flow control • Hardware flow control must be set on both sides: with AT\Q3 or AT+IFC in the ME and an equivalent RTS/

CTS handshake option in the host application. • The default setting of the ME is AT\Q0 (no flow control) which must be altered to AT\Q3 (RTS/CTS hardware

handshake on). The setting is stored volatile and must be restored each time after rebooting the ME. • AT\Q has no read command. To verify the current setting of AT\Q, simply check the settings of the active

profile with AT&V. • Often, fax programs run an intialization procedure when started up. The intialization commonly includes

enabling RTS/CTS hardware handshake, eliminating the need to set AT\Q3 once again. However, before set-ting up a CSD call, you are advised to check that RTS/CTS handshake is set.

Buffer design considerations • Each serial interface (ASC0 and ASC1) of the BGS3 uses two buffers, one for the uplink and one for the

downlink. Each buffer has a capacity of minimum 1024 bytes. • Uplink direction (where ME is receiving data from host application):

CTS control is based on the filling level of the ME's receive buffer. When the application detects that CTS isbeing deactivated it must instantly stop sending data to the ME's receive buffer. But still, after deactivation ofCTS, the receive buffer of the ME can accept another 512 bytes.

• Downlink direction (where ME is sending data to host application): The transmit buffer of the ME can hold at least 1024 bytes. After deactivation of RTS the ME sends max. 2more bytes and then stops transferring data to the application. The maximum time RTS can be kept inactive without losing data is determined by the buffer size and the max-imum possible over-the-air data rate. In any case, the local data rate between DCE and DTE (AT+IPR) shouldbe set to a value higher than the maximum possible over-the-air data rate.

• Buffer size recommended for the host application: Just like the ME, the host application should include send and receive buffers for each serial interface. To

BGS3 AT Command Set 1.10 Serial Interface Flow Control


handle large amounts of data at high speed a buffer capacity of 1024 bytes is recommended. If the host appli-cation is designed mainly for one direction (uplink or downlink) a lower buffer size will do for the directionwhere less data is transferred. In fact, the optimal size of the host application buffers is a matter of finding the balance between the amountof data, data throughput, reaction time of the application when handling the buffer, processor performanceand available memory. To give an example, a small buffer size (such as 256 bytes) increases the frequencyof deactivating RTS/CTS and the frequency of flushing the buffer, thus diminishing the efficiency of the appli-cation. Also, please consider that RTS/CTS flow control cannot stop the data stream coming from the network, e.g.in a GPRS or fax connection. So the lack of appropriate hardware flow control increases the risk of losing datapackets if, like in the case of UDP, the connection protocol has no or only minimum error handling functions.Other network protocols are using high level flow control mechanisms. For example, to prevent loss of datathe TCP protocol uses retransmission algorithms, fax applications usually repeat the transfer of faulty pages.

BGS3 AT Command Set 1.11 Common PCN Handset Specification (CPHS)


1.11 Common PCN Handset Specification (CPHS)

The ME provides features to implement a device following the prerequisites of the Common PCN Handset Spec-ification (CPHS) Phase 2.

CPHS Feature Description/Remarks AT commandAlternate Line Service Using two phone numbers with one SIM card. AT^SALS

Voice Message Waiting Indication

Indicate the receipt of a short message coded as Voice Mes-sage Waiting Indicator as defined by the CPHS Phase 2 standard.

AT^SIND, AT+CMER, indicators "vmwait1" and "vmwait2"

Operator (Service pro-vider) name from SIM

Read specific Elementary Files (6F14h, 6F18h) from SIM. AT+CRSM

Network and Service Pro-vider Lock

Lock/Unlock an ME to specific HPLMN and service provider. AT+CLCK, (AT+CPIN)

Call Forwarding Get and set diverted call status. Access specific Elementary File (6F13h) from SIM.

AT+CCFC, AT+CRSM

Customer Service Profile (CSP)

Setting services and their menu entries depending on cus-tomer profiles.

AT+CRSM

Information numbers Hierarchically structured service numbers phonebook on SIM according to CPHS 4.2 (mandatory).

AT+CRSM

BGS3 AT Command Set 2. Configuration Commands


2. Configuration Commands

The AT Commands described in this chapter allow the external application to determine the BGS3's behaviourunder various conditions.

2.1 AT&F Set all current parameters to manufacturer defaults

AT&F sets all current parameters to the manufacturer defined profile. All defined GPRS contexts which are notactivated or not online will be undefined if the non volatile storage of CGDCONT settings is not activated by theAT^SCFG parameter "GPRS/PersistentContexts" (see AT+CGDCONT).

Syntax

Parameter Description

[0] Set all TA parameters to manufacturer defaults

Notes• List of parameters reset to manufacturer default can be found in Section 20.5, Factory Default Set-

tings Restorable with AT&F.• In addition to the default profile, you can store an individual one with AT&W. To alternate between the two pro-

files enter either ATZ (loads user profile) or AT&F (restores factory profile).• Every ongoing or incoming call will be terminated.

Exec Command

AT&F[<value>]Response(s)

OK

PIN ASC0 ASC1 MUX1 MUX2 MUX3 Charge Last Reference(s)

- + + + + + - - V.250

<value>(num)

BGS3 AT Command Set 2.2 AT&V


2.2 AT&V Display current configuration

AT&V returns the current parameter setting. The configuration varies depending on whether or not PIN authen-tication has been done.

Syntax


[0] Profile number

Notes• The value of \Q (flow control) is also determined by the AT+IFC command. In case the value set by AT+IFC

cannot be represented by a \Q equivalent, \Q255 will be displayed. • The parameters of AT^SMGO can only be displayed after the SMS data from the SIM have been read success-

fully for the first time. Reading starts after successful SIM authentication has been performed, and may takeup to 30 seconds depending on the SIM used. While the read process is in progress, an attempt to read theparameter will result in empty values.

• The parameter of AT+CSDH will only be displayed in SMS PDU mode, see AT+CMGF.

Exec Command

AT&V[<value>]Response(s)

ACTIVE PROFILE:... (see Section 2.2.1, AT&V responses)OK


- + ± + ± ± - - V.250

<value>(num)



2.2.1 AT&V responses

The following tables show four different kinds of responses depending on whether or not the PIN is entered andwhether or not the Multiplex mode is enabled (see AT+CMUX).

Table 2.1: Current configuration on ASC0 / MUX channel 1 (example)

PIN authentication done No PIN authenticationACTIVE PROFILE:E1 Q0 V1 X4 &C1 &D2 &S0 \Q0 \V1 S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000+CBST: 7,0,1+CRLP: 61,61,78,6+CR: 0+FCLASS: 0+CRC: 0+CMGF: 1+CSDH: 0+CNMI: 0,0,0,0,1+IFC: 0,0+ILRR: 0+IPR: 115200+CMEE: 2^SMGO: 0,0+CSMS: 0,1,1,1^SACM: 0,"000000","000000"^SLCC: 0^SCKS: 0,1+CREG: 0,1+CLIP: 0,2+CAOC: 0+COPS: 0,0,"operator"+CGSMS: 3OK

ACTIVE PROFILE:E1 Q0 V1 X4 &C1 &D2 &S0 \Q0 \V1 S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002 S18:000+CBST: 7,0,1+CRLP: 61,61,78,6+CR: 0+FCLASS: 0+IFC: 0,0+ILRR: 0+IPR: 115200+CMEE: 2^SCKS: 0,1OK



Table 2.2: Current configuration on ASC1 and MUX channels 2 and 3 (example)

PIN authentication done No PIN authenticationACTIVE PROFILE:E1 Q0 V1 X4 &C1 &D0 &S0 \Q0 \V1 S0:000 S3:013 S4:010 S5:008+CR: 0+CRC: 0+CMGF: 1+CSDH: 0+CNMI: 0,0,0,0,1+IFC: 0,0+ILRR: 0+IPR: 115200+CMEE: 2^SMGO: 0,0+CSMS: 0,1,1,1^SACM: 0,"000000","000000"^SLCC: 0^SCKS: 0,1+CREG: 0,1+CLIP: 0,2+CAOC: 0+COPS: 0,0,"operator"+CGSMS: 3OK

ACTIVE PROFILE:E1 Q0 V1 X4 &C1 &D0 &S0 \Q0 \V1 S0:000 S3:013 S4:010 S5:008+CR: 0+IFC: 0,0+ILRR: 0+IPR: 115200+CMEE: 2^SCKS: 0,1+CGSMS: 3OK

BGS3 AT Command Set 2.3 AT&W


2.3 AT&W Stores current configuration to user defined profile

AT&W stores the currently set parameters to a user defined profile in the non-volatile memory.

Syntax


[0] Number of profile

Notes• The user defined profile will be restored automatically after power-up. Use ATZ to restore user profile and

AT&F to restore factory settings. Until the first use of AT&W, ATZ works as AT&F.• AT&W stores all global settings and the current local settings of the interface, on which the command is exe-

cuted.• A list of parameters stored to the user profile can be found in Section 20.4, AT Command Settings stor-

able with AT&W.

Exec Command

AT&W[<value>]Response(s)

OKERROR+CME ERROR: <err>


- + + + + + - - V.250

<value>(num)

BGS3 AT Command Set 2.4 ATQ


2.4 ATQ Result code presentation mode

This command determines whether or not the TA transmits any result code to the TE. Other information texttransmitted as response is not affected.

Syntax


[0](&F) DCE transmits result code 1 Result codes are suppressed and not transmitted

Exec Command

ATQ[<n>]Response(s)

If <n>=0:OKIf <n>=1:(none)


- + + + + + - - V.250

<n>(num)(&W)(&V)

BGS3 AT Command Set 2.5 ATV


2.5 ATV Result code format mode

This command determines the contents of header and trailer transmitted with AT command result codes andinformation responses. Possible responses are described in Section 2.5.1, Verbose and numeric result codes.

Syntax


[0] Information response: <text><CR><LF>Short result code format: <numeric code><CR>

1(&F) Information response: <CR><LF><text><CR><LF>Long result code format: <CR><LF><verbose code><CR>

2.5.1 Verbose and numeric result codes

Exec Command

ATV[<value>]Response(s)

OKERROR


- + + + + + - - V.250

<value>(num)(&W)(&V)

Verbose format Numeric format MeaningOK 0 command executed, no errors CONNECT 1 link establishedRING 2 ring detectedNO CARRIER 3 link not established or disconnectedERROR 4 invalid command or command line too longNO DIALTONE 6 no dial tone, dialling impossible, wrong modeBUSY 7 remote station busyNO ANSWER 8 no answerCONNECT 2400/RLP 47 link with 2400 bps and Radio Link ProtocolCONNECT 4800/RLP 48 link with 4800 bps and Radio Link ProtocolCONNECT 9600/RLP 49 link with 9600 bps and Radio Link ProtocolCONNECT 14400/RLP 50 link with 14400 bps and Radio Link ProtocolALERTING alerting at called phoneDIALING mobile phone is dialing

BGS3 AT Command Set 2.6 ATX


2.6 ATX Set CONNECT result code format and call monitoring

ATX determines whether or not the TA detects the presence of dial tone and busy signal and whether or not TAtransmits particular result codes.

Syntax


[0] CONNECT result code only returned, dial tone and busy detection are both dis-abled.

1 CONNECT <text> result code only returned, dial tone and busy detection areboth disabled.

2 CONNECT <text> result code returned, dial tone detection is enabled, busydetection is disabled.

3 CONNECT <text> result code returned, dial tone detection is disabled, busydetection is enabled.

4(&F) CONNECT <text> result code returned, dial tone and busy detection are bothenabled.

Exec Command

ATX[<value>]Response(s)

OKERROR


- + + + + + - - V.250


BGS3 AT Command Set 2.7 AT\V


2.7 AT\V Set CONNECT result code format

Syntax


[0] CONNECT <text> result code returned without RLP trailer1(&F) CONNECT <text> result code returned with RLP trailer

Notes• For circuit switched data calls only.• Output only if ATX parameter is set with value > 0.

Exec Command

AT\V[<value>]Response(s)

OKERROR


- + - + - - - - V.250


BGS3 AT Command Set 2.8 ATZ


2.8 ATZ Set all current parameters to user defined profile

ATZ sets all current parameters to the user profile stored with AT&W. If a connection is in progress, it will be ter-minated.All defined GPRS contexts which are not activated or not online will be undefined if the non volatile storage ofCGDCONT settings is not activated by the AT^SCFG parameter "GPRS/PersistentContexts" (see AT+CGDCONT).The user defined profile is stored to the non-volatile memory.

Syntax


[0] Reset to user profile

Notes• First the profile will be set to factory default (see AT&F). If there is a valid user profile (stored with AT&W), this

profile will be loaded afterwards. • Any additional commands on the same command line may be ignored. A delay of 300 ms is required before

next command is sent, otherwise "OK" response may be corrupted.

Exec Command

ATZ[<value>]Response(s)

OK


- + + + + + - - V.250

<value>(num)

BGS3 AT Command Set 2.9 AT+CFUN


2.9 AT+CFUN Set phone functionality

The AT+CFUN command serves to control the functionality level of the ME. It can be used to reset the ME, tochoose one of the SLEEP modes or to return to full functionality.Intended for power saving, SLEEP mode reduces the functionality of the ME to a minimum and thus minimizesthe current consumption. Further information, particularly power supply ratings during the various operatingmodes and the timing of hardware signals in SLEEP mode can be found in the "BGS3 Hardware InterfaceDescription, Version 01.000a". SLEEP mode falls in two categories: • NON-CYCLIC SLEEP mode <fun>=0 • and CYCLIC SLEEP modes, selectable as <fun>= 7 or 9.

NON-CYCLIC SLEEP mode permanently blocks the serial interface. The benefit of the CYCLIC SLEEP mode isthat the serial interface remains accessible and that, in intermittent wake-up periods, characters can be sent orreceived without terminating the selected mode. This allows the ME to wake up for the duration of an event and,afterwards, to resume power saving. Please refer to Section 2.9.1, Wake up the ME from SLEEP mode for asummary of all SLEEP modes and the different ways of waking up the module.For CYCLIC SLEEP mode both the ME and the application must be configured to use hardware flow control.This is necessary since the CTS signal is set/reset every 0.9-2.7 seconds in order to indicate to the applicationwhen the UART is active. The default setting of hardware flow control is AT\Q0 which must be altered to AT\Q3.For use after restart you are advised to add it to the user profile saved with AT&W. If both interfaces ASC0 and ASC1 are connected, hardware flow control must be set in either application. Seenotes below for further detail.

The AT+CFUN test command returns the values of the supported parameters. The AT+CFUN read command returns the current functionality value. The AT+CFUN write command can be used to reset the ME, to choose one of the SLEEP modes or to return tofull functionality.

SyntaxTest Command

AT+CFUN=?Response(s)

+CFUN: (list of supported <fun>s) , (list of supported <rst>s)OK

Read Command

AT+CFUN?Response(s)

+CFUN: <fun>OK

Write Command

AT+CFUN=[<fun>[, <rst>]]Response(s)



- + + ± ± ± - - GSM 07.07



Unsolicited Result Codes

URC 1

^SYSSTART

Indicates that the ME has been started and is ready to operate. If autobauding is active (AT+IPR=0) the URCis not generated.

URC 2

^SYSSTART CHARGE ONLY MODE

Indicates that the ME has entered the CHARGE ONLY mode. This occurs if the charger is connected whilethe ME is in POWER DOWN mode. If autobauding is active (AT+IPR=0) the URC is not generated. InCHARGE ONLY mode the ME is neither registered to the GSM network nor are the serial interfaces fullyaccessible. For further details on charging refer to the Hardware Interface Description [2].


0 NON-CYCLIC SLEEP mode: In this mode, the AT interface is not accessible. Consequently, after setting<fun>=0, do not send further characters. Otherwise these characters remainin the input buffer and may delay the output of an unsolicited result code. The first wake-up event stops power saving and takes the ME back to full func-tionality level <fun>=1.

[1](&F)(P) Full functionality (no power saving). If the ME is in one of the CYCLIC SLEEP modes you can issue AT+CFUN=1to stop power saving and return to full functionality. Keep in mind that, unlike the reset command described below, this action doesnot restart the ME but only changes the level of functionality. See parameter<rst> for details on the reset.

7 CYCLIC SLEEP mode: In this mode, the serial interface is shortly enabled while CTS is active. If char-acters are recognized on the serial interface, the ME stays active for 2 secondsafter the last character was sent or received. The ME exits SLEEP mode only, if AT+CFUN=1 is entered.

9 CYCLIC SLEEP mode: In this mode, the serial interface is shortly enabled while CTS is active. If char-acters are recognized on the serial interface, the ME stays active after the lastcharacter was sent or received for at least the time, which can be configuredby AT^SCFG="PowerSaver/Mode9/Timeout",<psm9to> (temporary wakeup). In contrast to SLEEP mode 7 assertion of RTS can also be used to temporarilywake up the ME. In this case too, activity time is at least the time set withAT^SCFG="PowerSaver/Mode9/Timeout",<psm9to>. RTS can be activatedeither from ASC0 or ASC1.The ME exits SLEEP mode only, if AT+CFUN=1 is entered.

The parameter can only be used if the serial interface is enabled. Due to the command syntax, you need to enter parameter <fun>, followed by <rst>, where <fun> is only aplaceholder and has no effect. See examples below. [0] Placeholder for <fun> as stated above. 1 ME resets and restarts to full functionality. After reset and restart, PIN 1

authentication is necessary (AT+CPIN). If autobauding is enabled, it is recom-mended to wait 3 to 5 seconds before entering the first AT command. Fordetails on autobauding refer to Section 4.8.1, Autobauding.

<fun>(num)

<rst>(num)



Notes• The settings made with AT+CFUN apply to both serial interfaces ASC0 and ASC1. • CYCLIC SLEEP mode cannot be activated or resumed as long as data are buffered in one of the output buff-

ers of the ME (ASC0 or ASC1). This should be taken into account, because RTS may be unintentionallyasserted if, for example, one of the following scenarios occurs: a) Hardware flow control is set in the ME (AT\Q3), but not in the host application (RTS/CTS handshake).b) The two serial interfaces ASC0 and ASC1 are connected, but one of them is released, e.g. after closing ordeactivating the application connected to this interface. In cases a) and b) data sent by the ME, such as URCs or outstanding AT command responses, will be buff-ered in the output buffer of this interface, signalized by the active RTS line until the buffer is emptied. Therefore, for CYCLIC SLEEP mode to work properly take care that the following requirements be met: Besure that data sent by the ME are collected on both interfaces. Activate hardware flow control on ME (TA) andapplication side (TE). Avoid releasing one of the interfaces if any URCs are likely to occur on this interface.

• CYCLIC SLEEP mode cannot be activated or resumed as long as data is buffered in one of the output buffersof the ME (ASC0 or ASC1). Therefore, ensure that the following requirements be met: a) If hardware flow control is set in the ME (AT\Q3), the host must also use hardware flow control.b) Remember that AT\Q3 takes effect only on the interface where the command was set. Therefore, if bothinterfaces ASC0 and ASC1 are connected ensure to set AT\Q3 on each interface. However, if only one inter-face shall be operated ensure that, on the unused interface, AT\Q3 is neither enabled and nor stored to theAT&W user profile. This is necessary to avoid that URCs, outstanding AT command responses or, after restarteven the "^SYSSTART" URC might be buffered on the unused interface without being collected by the hostapplication.

• In Multiplex mode, the CFUN profile is shared by all multiplexer channels. • If the ME is in Multiplexer mode, it is not recommended to activate SLEEP mode with AT+CFUN=<fun>. The

best approach to properly control SLEEP mode in this case is to issue the PSC messages described in [4],Section "Power saving control".

• When a circuit-switched call is in progress, <fun>=7 or 9 can be activated without terminating the call. How-ever, setting <fun>=0 during a circuit-switched call immediately disconnects this call.

• To check whether power saving is on, you can query the status with the read command AT+CFUN? only ifthe module is in full functionality mode or in CYCLIC SLEEP mode. If available, you can also take advantageof the status LED controlled by the SYNC pin (see AT^SSYNC and [2]). With AT^SSYNC you can select differ-ent modes of LED signalization during SLEEP modes (see Section 18.5.1, ME status indicated by status LEDpatterns for details). However, the module can wake up temporarily from power saving without leaving itsCYCLIC SLEEP mode (without changing +CFUN "<fun>"), e.g. for a network scan after a loss of radio cov-erage, or after receipt of serial data during CYCLIC SLEEP mode. During this "temporary wakeup state" theLED will operate as if the ME was in full functionality mode.



2.9.1 Wake up the ME from SLEEP mode

A wake-up event is any event that causes the ME to draw more current. Depending on the selected mode, thewake-up event either switches the SLEEP mode off and takes the ME back to full functionality AT+CFUN=1, oractivates the ME temporarily without terminating the selected SLEEP mode.

Definitions of the state transitions described in Table 2.3: • Quit: ME exits SLEEP mode.• Temporary: ME becomes active temporarily for the duration of the event and the mode-specific follow-up time

after the last character was sent or received on the serial interface.• No effect: Event is not relevant in the selected SLEEP mode. The ME does not wake up.

Table 2.3: Wake-up events in NON-CYCLIC and CYCLIC SLEEP modes

Event Selected mode:<fun>=0

Selected mode:<fun>=7 or 9

Ignition line No effect No effect RTS0 or RTS1 activation Quit Mode 7: No effect (RTS is only

used for flow control)Mode 9: Temporary

Unsolicited Result Code (URC) Quit Temporary Incoming voice or data call Quit Temporary Any AT command (incl. outgoing SMS, voice or data call)

Not possible (UART disabled) Temporary

Incoming SMS (AT+CNMI is set to 0,0 (this is the default setting)

No effect No effect

Incoming SMS (AT+CNMI is set to 1,1)

Quit Temporary

GPRS data transfer Not possible (UART disabled) Temporary AT+CFUN=1 Not possible (UART disabled) Quit

BGS3 AT Command Set 2.10 AT^SMSO


2.10 AT^SMSO Switch off mobile station

AT^SMSO initiates the power-off procedure. High level of the module's PWR_IND pin and the URC "^SHUTDOWN"notify that the procedure has completed and the module has entered the POWER DOWN mode. Therefore, besure not to disconnect the operating voltage until PWR_IND is high or until the URC "^SHUTDOWN" is displayed.Otherwise, you run the risk of losing data. For further details on how to turn off the module see the [2].

Syntax

Unsolicited Result Code^SHUTDOWN

Indicates that the power-off procedure is finished and the module will be switched off in less than 1 second.

Notes• Do not send any other AT command after AT^SMSO. • If AT^SMSO is entered on one of the Multiplexer channels the ME closes the Multiplexer channels, terminates

the Multiplexer and deactivates all other functions. Then, the URC "^SHUTDOWN" will be issued on the phys-ical serial interface (ASC0). The URC will be transmitted at the bit rate last activated on ASC0 for use withthe Multiplex driver.

• If both interfaces ASC0 and ASC1 are connected the URC appears on both of them. • If the module is in NORMAL mode and the charger is connected to the VCHARGE line, the AT^SMSO com-

mand causes the module to shut down shortly and then start into the CHARGE ONLY mode. If the module isin CHARGE ONLY mode the AT^SMSO command is not supported at all. In both cases, the module can onlybe switched off by disconnecting the charger. See also [2].

Test Command

AT^SMSO=?Response(s)

OK

Exec Command

AT^SMSOResponse(s)

^SMSO: MS OFFOKERROR


- + + + + + - +

BGS3 AT Command Set 2.11 AT+GCAP


2.11 AT+GCAP Request complete TA capabilities list

AT+GCAP returns a list of additional capabilities.

Syntax


e.g.: +CGSM,+FCLASS

Note• +CGSM: The response text shows which GSM commands of the ETSI standard are supported.

Test Command

AT+GCAP=?Response(s)

OK

Exec Command

AT+GCAPResponse(s)

+GCAP: <name>OK


- + + + + + - - V.250

<name>(str)

BGS3 AT Command Set 2.12 AT+CMEE


2.12 AT+CMEE Mobile Equipment Error Message Format

AT+CMEE controls the format of the error result codes that indicates errors related to BGS3 functionality. Formatcan be selected between plain "ERROR" output, error numbers or verbose "+CME ERROR: <err>" and "+CMSERROR: <err>" messages. Possible error result codes are listed in Table 2.4, General "CME ERROR" Codes (GSM 07.07), Table 2.5, Gen-eral "CME ERROR" Codes (proprietary), Table 2.6, GPRS related "CME ERROR" Codes (GSM 07.07) andTable 2.8, SMS related "CMS ERROR" Codes (GSM 07.05). In multiplex mode (refer AT+CMUX) the setting applies only to the logical channel where selected. The setting onthe other channels may differ.

Syntax


0(&F)(D) Disable result code, i.e. only "ERROR" will be displayed. 1 Enable error result code with numeric values. 2 Enable error result code with verbose (string) values.

Example

To obtain enhanced error messages it is recommended to choose <errMode>=2.

Test Command

AT+CMEE=?Response(s)

+CMEE: (list of supported<errMode>s)OK

Read Command

AT+CMEE?Response(s)

+CMEE: <errMode>OK

Write Command

AT+CMEE=<errMode>Response(s)

OK ERROR +CME ERROR: <err>


- + + + + + - - GSM 07.07

<errMode>(num)(&W)(&V)

AT+CMEE=2OK



2.12.1 CME/CMS Error Code OverviewTable 2.4: General "CME ERROR" Codes (GSM 07.07)

<err> Code Text (if AT+CMEE=2) 0 phone failure 1 no connection to phone 2 phone adapter link reserved 3 operation not allowed 4 operation not supported 5 PH-SIM PIN required 6 PH-FSIM PIN required 7 PH-FSIM PUK required 10 SIM not inserted 11 SIM PIN required 12 SIM PUK required 13 SIM failure 14 SIM busy 15 SIM wrong 16 incorrect password 17 SIM PIN2 required 18 SIM PUK2 required 20 memory full 21 invalid index 22 not found 23 memory failure 24 text string too long 25 invalid characters in text string 26 dial string too long 27 invalid characters in dial string 30 no network service 31 network timeout 32 network not allowed - emergency calls only 40 network personalization PIN required 41 network personalization PUK required 42 network subset personalization PIN required 43 network subset personalization PUK required 44 service provider personalization PIN required 45 service provider personalization PUK required 46 corporate personalization PIN required 47 corporate personalization PUK required 48 PH-SIM PUK (master phone code) required 100 unknown 132 service option not supported



Table 2.5: General "CME ERROR" Codes (proprietary)

133 requested service option not subscribed 134 service option temporary out of order 256 operation temporary not allowed 257 call barred 258 phone busy 259 user abort 260 invalid dial string 261 SS not executed 262 SIM blocked 263 invalid block

<err> Code Text (if AT+CMEE=2) 673 audio manager not ready 674 audio format cannot be configured 705 SIM toolkit menu has not been configured 706 SIM toolkit already in use 707 SIM toolkit not enabled 737 +CSCS type not supported 738 +CSCS type not found 741 must include <format> with <oper> 742 incorrect <oper> format 743 <oper> length too long 744 SIM full 745 unable to change PLMN list 746 network operator not recognised 749 invalid command length 750 invalid input string 753 missing required cmd parameter 754 invalid SIM command 755 invalid file Id 756 missing required P1/2/3 parameter 757 invalid P1/2/3 parameter 758 missing required command data 759 invalid characters in command data 761 CTM call is not setup 764 missing input value 765 invalid input value 766 unsupported value or mode 767 operation failed 768 multiplexer already active 769 unable to get control of required module

<err> Code Text (if AT+CMEE=2)



Table 2.6: GPRS related "CME ERROR" Codes (GSM 07.07)

Table 2.7: GPRS related "CME ERROR" Codes (proprietary)

770 SIM invalid - network reject 771 call setup in progress 772 SIM powered down 773 SIM file not present

<err> Code Text (if AT+CMEE=2) 103 illegal MS 106 illegal ME 107 GPRS services not allowed 111 PLMN not allowed 112 location area not allowed 113 roaming not allowed in this location area 148 unspecified GPRS error 149 PDP authentication failure 150 invalid mobile class

<err> Code Text (if AT+CMEE=2) 577 GPRS - activation rejected by GGSN 578 GPRS - unspecified activation rejection 579 GPRS - bad code or protocol rejection 580 GPRS - can't modify address 581 GPRS - no echo replyGPRS - CHAP close 582 GPRS - profile (CID) currently unavailable 583 GPRS - a profile (CID) is currently active 584 GPRS - combined services not allowed 585 GPRS - conditional IE error 586 GPRS - context activation rejected 587 GPRS - duplicate TI received 588 GPRS - feature not supported 589 GPRS - service not available 590 GPRS - unknown IE from network 591 GPRS - implicitly detached 592 GPRS - insufficient resources 593 GPRS - invalid activation state (0-1) 594 GPRS - invalid address length 595 GPRS - invalid character in address string 596 GPRS - invalid CID value 597 GPRS - invalid dialstring length 598 GPRS - mode value not in range 599 GPRS - invalid MAND information




600 GPRS - SMS service preference out of range 601 GPRS - invalid TI value 602 GPRS - IPCP negotiation timeout 603 GPRS - LCP negotiation timeout 604 GPRS - LLC error 605 GPRS - LLC or SNDCP failure 606 GPRS - lower layer failure 607 GPRS - missing or unknown APN 608 GPRS - mobile not ready 609 GPRS - MS identity not in network 610 GPRS - MSC temporary not reachable 611 GPRS - message incompatible with state 612 GPRS - message type incompatible with state 613 GPRS - unknown message from network 614 GPRS - NCP close 615 network failure 616 network is down 617 GPRS - no free NSAPIs 618 GPRS - processing of multiple CIDs not supported 619 GPRS - no PDP context activated 620 GPRS - normal termination 621 GPRS - NSAPI already used 622 GPRS - address element out of range 623 GPRS - PAP close 624 GPRS - PDP context w/o TFT already activated 625 GPRS - PDP type not supported 626 GPRS - peer refuses our ACCM 627 GPRS - peer refuses our IP address 628 GPRS - peer refuses our MRU 629 GPRS - peer rerequested CHAP 630 GPRS - profile (CID) not defined 631 GPRS - unspecified protocol error 632 GPRS - QOS not accepted 633 GPRS - QOS validation fail 634 GPRS - reactivation required 635 GPRS - regular deactivation 636 GPRS - semantic error in TFT operation 637 GPRS - semantic errors in packet filter 638 GPRS - semantically incorrect message 639 service type not yet available 640 operation of service temporary not allowed 641 GPRS - syntactical errors in packet filter




Table 2.8: SMS related "CMS ERROR" Codes (GSM 07.05)

642 GPRS - too many RXJs 643 GPRS - unknown PDP address or type 644 GPRS - unknown PDP context 645 GPRS - user authorisation failed 646 GPRS - QOS invalid parameter 647 GPRS - FDN failure 648 GPRS - bad default PDP context parameters 649 GPRS - bad PDP context parameters 650 GPRS - PDP context already active 660 GPRS - no echo reply 661 GPRS - syntactical error in TFT operation

<err> Code Text (if AT+CMEE=2) 1 unassigned (unallocated) number 8 operator determined barring 10 call barred 21 short message transfer rejected 27 destination out of service 28 unidentified subscriber 29 facility rejected 30 unknown subscriber 38 network out of order 41 temporary failure 42 congestion 47 resources unavailable, unspecified 50 requested facility not subscribed 69 requested facility not implemented 81 invalid short message transfer reference value 95 invalid message, unspecified 96 invalid mandatory information 97 message type non-existent or not implemented 98 message not compatible with short message protocol state 99 information element non-existent or not implemented 111 protocol error, unspecified 127 interworking, unspecified 128 telematic interworking not supported 129 short message type 0 not supported 130 cannot replace short message 143 unspecified TP-PID error 144 data coding scheme (alphabet) not supported 145 message class not supported




159 unspecified TP-DCS error 160 command cannot be actioned 161 command unsupported 175 unspecified TP-command error 176 TPDU not supported 192 SC busy 193 no SC subscription 194 SC system failure 195 invalid SME address 196 destination SME barred 197 SM rejected-duplicate SM 198 TP-VPF not supported 199 TP-VP not supported 208 do SIM SMS storage full 209 no SMS storage capability in SIM 210 error in MS 211 memory capacity exceeded 212 SIM application toolkit busy 213 SIM data download error 255 unspecified error cause 300 ME failure 301 SMS service of ME reserved 302 operation not allowed 303 operation not supported 304 invalid PDU mode parameter 305 invalid text mode parameter 310 SIM not inserted 311 SIM PIN required 312 PH-SIM PIN required 313 SIM failure 314 SIM busy 315 SIM wrong 316 SIM PUK required 317 SIM PIN2 required 318 SIM PUK2 required 320 memory failure 321 invalid memory index 322 memory full 330 SMSC address unknown 331 no network service 332 network timeout 340 no +CNMA acknowledgement expected




500 unknown error 516 invalid length 519 invalid length or character 520 invalid character in text 532 SIM not ready 533 unread records on SIM 534 CB error unknown 535 PS busy 536 couldn't read SMS parameters from SIM 537 SM BL not ready 538 invalid parameter 539 ME temporary not available 548 invalid (non-hex) chars in PDU 549 incorrect PDU length 550 invalid MTI (message type indication) 551 invalid (non-hex) chars in address 552 invalid address (no digits read) 553 incorrect PDU length (UDL) 554 incorrect SCA length 556 invalid first octet (should be 2 or 34) 557 invalid command type 558 SRR bit not set 559 SRR bit set 560 invalid user data header IE


BGS3 AT Command Set 2.13 AT+CSCS


2.13 AT+CSCS Select TE character set

The AT+CSCS write command informs the TA which character set <chset> is used by the TE. This enables theTA to convert character strings correctly between TE and ME character sets. See also Section 1.6, Supportedcharacter sets.Note that when the TA-TE interface is set to 8-bit operation and the used TE alphabet is 7-bit, the highest bit willbe set to zero.

Syntax


“GSM“(&F)(P) GSM default alphabet (GSM 03.38 subclause 6.2.1);Note: This setting may cause software flow control problems since the codesused to stop and resume data flow (XOFF = decimal 19, XON = decimal 17)are interpreted as normal characters.

“UCS2“ 16-bit universal multiple-octet coded character set (ISO/IEC10646 [32]); UCS2character strings are converted to hexadecimal numbers from 0000 to FFFF;e.g. "004100620063" equals three 16-bit characters with decimal values 65, 98and 99.

Test Command

AT+CSCS=?Response(s)

+CSCS: (list of supported<chset>s)OK

Read Command

AT+CSCS?Response(s)

+CSCS: <chset>OK

Write Command

AT+CSCS=[<chset>]Response(s)



- + + + + + - - GSM 07.07, GSM 11.11

<chset>(str)

BGS3 AT Command Set 2.14 AT^SCFG


2.14 AT^SCFG Extended Configuration Settings

AT^SCFG can be used to query and configure various settings of the BGS3. AT^SCFG read command returns a list of all supported parameters and their current values. AT^SCFG write command queries a configuration parameter (if no value is entered) or sets its value(s). Input of parameter names is always coded in GSM character set, parameter values are expected to be given asspecified via AT+CSCS.

SyntaxTest Command

AT^SCFG=?Response(s)

^SCFG: "AutoExec" , (list of supported <AutoExecCmd>), (list of supported <AutoExecType>), (list of supported <AutoExecIndex>), (list of supported <AutoExecMode>), (max. string length of <AutoExecATC>), (time range of <AutoExecPeriod>)^SCFG: "Call/ECC", (list of supported <ecc>s)^SCFG: "GPRS/ATS0/withAttach", (list of supported <gs0aa>s)^SCFG: "GPRS/AutoAttach", (list of supported <gaa>s)^SCFG: "GPRS/PersistentContexts", (list of supported <gpc>s)^SCFG: "GPRS/RingOnIncomingData", (list of supported <groid>s)^SCFG: "MEShutdown/OnIgnition", (list of supported <msi>s)^SCFG: "PowerSaver/Mode9/Timeout", (list of supported <psm9to>s)^SCFG: "Radio/Band", (list of supported <rbp>s), (list of supported <rba>s)^SCFG: "Radio/CNS", (list of supported <cns>s)^SCFG: "Radio/OutputPowerReduction", (list of supported <ropr>s)^SCFG: "Tcp/BufSize", (list of supported <tcpBufSize>)^SCFG: "Tcp/IRT", (list of supported <tcpIrt>)^SCFG: "Tcp/MR", (list of supported <tcpMr>)^SCFG: "Tcp/OT", (list of supported <tcpOt>)^SCFG: "Tcp/SAck", (list of supported <tcpSack>)^SCFG: "Tcp/TTcp", (list of supported <tcpTtcp>)^SCFG: "Tcp/WithURCs", (list of supported <tcpWithUrc>)^SCFG: "URC/CallStatus/CIEV", (list of supported <succ>s)^SCFG: "URC/CallStatus/SLCC", (list of supported <sucs>s)^SCFG: "URC/Datamode/Ringline", (list of supported <udri>s) ^SCFG: "URC/Ringline", (list of supported <uri>s)^SCFG: "URC/Ringline/ActiveTime", (list of supported <urat>s)OK

Read Command

AT^SCFG?Response(s)

^SCFG: "AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>, <AutoExecATC>[, <AutoExecPeriod>, <AutoExecPeriodTimeLeft>]^SCFG: "Call/ECC", <ecc>^SCFG: "GPRS/ATS0/withAttach", <gs0aa>^SCFG: "GPRS/AutoAttach", <gaa>^SCFG: "GPRS/PersistentContexts", <gpc>^SCFG: "GPRS/RingOnIncomingData", <groid>^SCFG: "MEShutdown/OnIgnition", <msi>^SCFG: "PowerSaver/Mode9/Timeout", <psm9to>^SCFG: "Radio/Band", <rbc>, <rba>^SCFG: "Radio/CNS", <cns>^SCFG: "Radio/OutputPowerReduction", <ropr>^SCFG: "Tcp/BufSize", <tcpBufSize>



^SCFG: "Tcp/IRT", <tcpIrt>^SCFG: "Tcp/MR", <tcpMr>^SCFG: "Tcp/OT", <tcpOt>^SCFG: "Tcp/SAck", <tcpSack>^SCFG: "Tcp/TTcp", <tcpTtcp>^SCFG: "Tcp/WithURCs", <tcpWithUrc>^SCFG: "URC/CallStatus/CIEV", <succ>^SCFG: "URC/CallStatus/SLCC", <sucs>^SCFG: "URC/Datamode/Ringline", <udri>^SCFG: "URC/Ringline", <uri>^SCFG: "URC/Ringline/ActiveTime", <urat>OK

Write Command

Configure Audio Loop:AT^SCFG="Audio/Loop"[, <al>]Response(s)

^SCFG: "Audio/Loop", <al>OKERROR+CME ERROR: <err>

Write Command

Automatic AT command execution AT^SCFG="AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>[, <AutoExecMode>, <AutoExecATC>[, <AutoExecPeriod>]]Response(s)

^SCFG: "AutoExec" , <AutoExecCmd>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>, <AutoExecATC>[, <AutoExecPeriod>, <AutoExecPeriodTimeLeft>]OKERROR+CME ERROR: <err>

Write Command

Query/Configure Emergency numbers for SIM without ECC fieldAT^SCFG="Call/ECC"[, <ecc>]Response(s)

^SCFG: "Call/ECC", <ecc>OKERROR+CME ERROR: <err>

Write Command

GPRS ATS0 with automatic attachAT^SCFG="GPRS/ATS0/withAttach"[, <gs0aa>]Response(s)

^SCFG: "GPRS/ATS0/withAttach", <gs0aa>OKERROR+CME ERROR: <err>

Read Command (Continued)

AT^SCFG?Response(s)



Write Command

Automatic GPRS attachAT^SCFG="GPRS/AutoAttach"[, <gaa>]Response(s)

^SCFG: "GPRS/AutoAttach", <gaa>OKERROR+CME ERROR: <err>

Write Command

Persistent GPRS contextsAT^SCFG="GPRS/PersistentContexts"[, <gpc>]Response(s)

^SCFG: "GPRS/PersistentContexts", <gpc>OKERROR+CME ERROR: <err>

Write Command

Ring on incoming GPRS IP data packetsAT^SCFG="GPRS/RingOnIncomingData"[, <groid>]Response(s)

^SCFG: "GPRS/RingOnIncomingData", <groid>OKERROR+CME ERROR: <err>

Write Command

Enable/disable shutdown by ignition lineAT^SCFG="MEShutdown/OnIgnition"[, <msi>]Response(s)

^SCFG: "MEShutdown/OnIgnition", <msi>OKERROR+CME ERROR: <err>

Write Command

Query/Set timeout value for power saving mode 9AT^SCFG="PowerSaver/Mode9/Timeout"[, <psm9to>]Response(s)

^SCFG: "PowerSaver/Mode9/Timeout", <psm9to>OKERROR+CME ERROR: <err>

Write Command

Radio band selectionAT^SCFG="Radio/Band"[, <rbp>][, <rba>]Response(s)

^SCFG: "Radio/Band", <rbp>, <rba>OKERROR+CME ERROR: <err>



Write Command

Query/Enable/Disable Continuous Network SearchAT^SCFG="Radio/CNS"[, <cns>]Response(s)

^SCFG: "Radio/CNS", <cns>OKERROR+CME ERROR: <err>

Write Command

Radio output power reductionAT^SCFG="Radio/OutputPowerReduction"[, <ropr>]Response(s)

^SCFG: "Radio/OutputPowerReduction", <ropr>OKERROR+CME ERROR: <err>

Write Command

Configuration of TCP parameter 'BufSize':AT^SCFG="Tcp/BufSize"[, <tcpBufSize>]Response(s)

^SCFG: "Tcp/BufSize", <tcpBufSize>OKERROR+CME ERROR: <err>

Write Command

Configuration of TCP parameter 'InitialRetransmissionTimeout':AT^SCFG="Tcp/IRT"[, <tcpIrt>]Response(s)

^SCFG: "Tcp/IRT", <tcpIrt>OKERROR+CME ERROR: <err>

Write Command

Configuration of TCP parameter 'MaxRetransmissions':AT^SCFG="Tcp/MR"[, <tcpMr>]Response(s)

^SCFG: "Tcp/MR", <tcpMr>OKERROR+CME ERROR: <err>

Write Command

Configuration of TCP parameter 'OverallTimeout':AT^SCFG="Tcp/OT"[, <tcpOt>]Response(s)

^SCFG: "Tcp/OT", <tcpOt>OKERROR+CME ERROR: <err>



Write Command

Configuration of TCP parameter 'Selective Acknowledge':AT^SCFG="Tcp/SAck"[, <tcpSack>]Response(s)

^SCFG: "Tcp/SAck", <tcpSack>OKERROR+CME ERROR: <err>

Write Command

Configuration of Internet Service URCs:AT^SCFG="Tcp/WithURCs"[, <tcpWithUrc>]Response(s)

^SCFG: "Tcp/WithURCs", <tcpWithUrc>OKERROR+CME ERROR: <err>

Write Command

Configuration of URC "+CIEV: call" Call Status IndicationAT^SCFG="URC/CallStatus/CIEV"[, <succ>]Response(s)

^SCFG: "URC/CallStatus/CIEV", <succ>OKERROR+CME ERROR: <err>

Write Command

Configuration of URC "^SLCC" Call Status IndicationAT^SCFG="URC/CallStatus/SLCC"[, <sucs>]Response(s)

^SCFG: "URC/CallStatus/SLCC", <sucs>OKERROR+CME ERROR: <err>

Write Command

URC indication in datamode via Ring line:AT^SCFG="URC/Datamode/Ringline"[, <udri>]Response(s)

^SCFG: "URC/Datamode/Ringline", <udri>OKERROR+CME ERROR: <err>

Write Command

URC indication via Ring line:AT^SCFG="URC/Ringline"[, <uri>]Response(s)

^SCFG: "URC/Ringline", <uri>OKERROR+CME ERROR: <err>



Unsolicited Result Code^SCFG: "AutoExec", <AutoExecState>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>, <AutoExecATC>

If the event specified with <AutoExecType> occurs and the related AT command line is executed this URC isissued.


Audio Loop SettingThis parameter can be used to configure an audio loop. The feature is intended for testing only. When an audio loop is closed DSP audio processing is excluded from the audio path. Only ADC gain and DACgain remain in the audio path (see AT commands AT^SNFI respectively AT^SNFO). But mostly audio parame-terization capabilities remain nearly unrestricted and will be valid when the audio loop is open. To use the audio loop for test purposes please select at first the audio mode with AT^SNFS and the audio inter-face configuration with AT^SAIC. Then check the gain and attenuation values of the audio path with AT^SNFIand AT^SNFO and configure the power supply VMIC with AT^SNFM. After that close the audio loop withAT^SCFG. The following AT write commands are blocked while the audio loop is closed: AT^SNFS, AT^SAIC, AT^SNFWand AT^SNFTTY. Please close the audio loop only in idle mode. Don't change audio parameters outside of the audio path whenthe audio loop is closed. “0“(P) No audio loop active“1“ Audio loop active

AutoExec CommandThis parameter serves to switch the Autoexec function on or off. If it is switched off (<AutoExecCmd>=0), parameters following <AutoExecIndex> are ignored and all settingsat the given index are restored to their default values. Parameter is global for all interfaces, non-volatile and will not be reset by AT&F. “0“ Disable automatic execution of the AT command(s) specified with <AutoEx-

ecATC> at a given <AutoExecIndex>. “1“ Enable automatic execution of the AT command(s) specified with <AutoExe-

cATC> at a given <AutoExecIndex>. Not allowed for <AutoExecType>=0(DTR line activation) while multiplex mode is active, refer to AT+CMUX.

Write Command

Duration of active RING line for URC indications:AT^SCFG="URC/Ringline/ActiveTime"[, <urat>]Response(s)

^SCFG: "URC/Ringline/ActiveTime", <urat>OKERROR+CME ERROR: <err>


- + + + + + ± -

<al>(str)

<AutoExecCmd>(str)(+CSCS)



AutoExec Event TypeThis parameter selects the kind of event used to automatically launch the AT command(s) specified with<AutoExecATC>. Parameter is global for all interfaces, non-volatile and will not be reset by AT&F. “0“ Autoexec activity is driven by ASC0 DTR line activation (OFF-ON transition). “1“ Autoexec activity is timer driven. To specify the time span use <AutoExecPe-

riod>.

AutoExec Command IndexThis parameter specifies the command storage index. The following table shows the index ranges supported foreach variant of <AutoExecType>. Parameter is global for all interfaces, non-volatile and will not be reset by AT&F.

AutoExec Command Mode0...255This parameter specifies details regarding the behavior of the BGS3 when the AT command starts to be exe-cuted. Value is interpreted as a bit field, unused bits are reserved for future use (RFU) and shall be set to 0.When a call is released by an Autoexec activity, no release indication may be issued on the first logical channel.Parameter is global for all interfaces, non-volatile and will not be reset by AT&F.

AutoExec AT command StringThis parameter specifies the AT command(s) to be launched automatically. Each AT command is executed inthe same way as if it were entered online, this means that command concatenation is possible if supported bythe given commands. If serial multiplex mode is activated (AT+CMUX) the first logical channel is used, i.e. CSDcalls (data or fax) could be set up. If the BGS3 is busy on the serial channel command execution will be delayed

<AutoExecType>(str)(+CSCS)

<AutoExecIndex>(str)(+CSCS)

<AutoExecType> value <AutoExecType> event Valid Indices 0 Autoexec activity is driven by ASC0 DTR

line activation 0

1 Autoexec activity is timer driven. 0-2

<AutoExecMode>(str)(+CSCS)

Bit Maskhex Maskdec Control D0 D1

0x00 0x01 0x02 0x03

0 1 2 3

00: Ignore ongoing calls 01: Wait until all calls have ended 10: Dismiss any ongoing call 11: RFU

D2 0x04 4 0: One shot action 1: Periodic action (for "AutoExec/Period" only)

D3 0x08 8 RFUD4 0x10 16 RFUD5 0x20 32 RFUD6 0x40 64 RFUD7 0x80 128 RFU

<AutoExecATC>(str)(+CSCS)



until ongoing action is finished. The first two characters of the automatically launched AT command shall be "at". Please refer to examples below.Parameter is global for all interfaces, non-volatile and will not be reset by AT&F.

AutoExec Command PeriodParameter specifies the period after which <AutoExecATC> will be executed. Format is "hhh:mm:ss", wherecharacters indicate hours, minutes and seconds. This parameter applies to <AutoExecType>=1 only.Parameter is global for all interfaces, non-volatile and will not be reset by AT&F. 000:00:05...240:00:00

AutoExec Command Period LeftThis parameter shows the amount of time left until <AutoExecATC> will be executed. Format is "hhh:mm:ss",where characters indicate hours, minutes and seconds. This parameter applies to <AutoExecType>=1 only.Due to the internal activity and network signaling an execution delay of several seconds may occur for the overallprocedure.000:00:00...240:00:00

AutoExec Command StatusThis parameter is part of the Autoexec URC which is presented when a scheduled Autoexec activity is beingperformed.“1“ The value 1 indicates that the Autoexec activity specified with <AutoExec-

ATC> is currently executed.

Emergency call numbers on non-ECC SIMThis parameter specifies emergency call numbers on SIM cards without ECC field. The parameter has no influ-ence on the commonly used emergency numbers 112 and 911 which are always supported. Please refer also to Section 7.3, ATD where you can find a list of emergency call numbers supported if no SIMis inserted. The value range of <ecc> is "0"..."255". To select or deselect an emergency number calculate the sum of thevalues of all desired numbers and use the resulting value. For example, for "08" (2) and "118" (8) please enterthe value (10). Parameter is global for the ME, non-volatile and will not be reset by AT&F. “ 0“ No additional emergency numbers“ 1“ 000“ 2“ 08“ 4“ 110“ 8“ 118“16“ 119“32“ 999“64“ Reserved“128“ Reserved“255“(D) All additional emergency call numbers are supported.

<AutoExecPeriod>(str)(+CSCS)

<AutoExecPeriodTimeLeft>(str)(+CSCS)

<AutoExecState>(str)(+CSCS)

<ecc>(str)(+CSCS)



GPRS ATS0 with AttachThis parameter can be used to control the behaviour of ATS0.Parameter is global for all interfaces, volatile and will not be reset by AT&F. “on“(P) When the ATS0=<n> (<n>>0) command is received, the MT will attempt to per-

form a GPRS attach. “off“ When the ATS0=<n> (<n>>0) command is received, the MT will not attempt to

perform a GPRS attach.

GPRS with AutoAttachThis parameter can be used to control whether the ME will perform a GPRS attach immediately after power-upand registering to the network or not. If the setting is changed to "enabled" and the ME is not attached yet, it willnot initiate an attach immediately but after the next power-up and registration to the network.Parameter is global for all interfaces, non-volatile and will not be reset by AT&F. “disabled“(D) GPRS auto attach is disabled“enabled“ GPRS auto attach is enabled

GPRS with persistent contextsThis parameter can be used to control whether the ME will store the GPRS context information defined by theAT+CGDCONT volatile or non-volatile.Parameter is global for all interfaces, non-volatile and will not be reset by AT&F. “0“(D) GPRS context definitions are volatile.“1“ GPRS context definitions are non-volatile and will not be reset by AT&F.

Ring on incoming GPRS IP data packetsThis parameter can be used to control the behaviour of the RING line for incoming IP packets in GPRS onlinemode.Parameter is local for the interface, volatile and will not be reset by AT&F. “on“ If the ME is in power saving mode 7 or 9 (see AT+CFUN) and hardware flow

control is in use (AT\Q3) and the RTS line is inactive and there are incomingIP packets for a GPRS context which is online, then the RING line will be acti-vated once, for a time which is configured by the parameter "URC/Ringline/ActiveTime" (<urat>). The RING line to be used can be configured with theparameter "URC/Ringline" (<uri>).

“off“(P) RING line is not activated for incoming IP packets.

MEShutdown/OnIgnition: Enable/disable shutdown by IGT lineThe parameter specifies two different switching modes of the ignition line IGT: The line may either be used onlyto switch on the ME, or to switch it on and off. By factory default the module's IGT line is configured only for switching on the ME. We recommend that greatcare be taken before changing the switch mode of IGT. It is of vital importance that the following conditions aremet to ensure that IGT works properly as ON/OFF switch: Switch-on condition: If the ME is off the IGT line must be asserted for at least 400 ms and then released. Switch-off condition: If the ME is on the IGT line must be asserted for at least 1 s and then released. The switch-off routine is identical with the shutdown procedure initiated by the AT^SMSO command, i.e. the ME performs an

<gs0aa>(str)(+CSCS)

<gaa>(str)(+CSCS)

<gpc>(str)(+CSCS)

<groid>(str)(+CSCS)

<msi>(str)(+CSCS)



orderly shutdown and issues the "^SHUTDOWN" URC. Before switching off the ME wait at least 2 seconds after startup.For further details please refer to [2]. Parameter <msi> is global for all interfaces, non-volatile and will not be reset by AT&F. “on“ Ignition line (IGT) can be used to switch on and off the ME. “off“(D) Ignition line (IGT) can be used to switch on the ME.

Power saving mode 9 timeoutThis parameter can be used to query or configure the wake up time for power saving mode 9 (see AT+CFUN withparameter <fun>=9). Parameter is global for the ME, volatile and will not be reset by AT&F. 5...20(P)...36000 The granularity of the timeout value is 100ms (i.e. a value of 10 equal 1 sec-

ond). The minimum timeout value that can be applied is 5, but accuracy is onlyguaranteed for timeout values greater than 20.

Allowed radio band(s)The feature "Radio/Band" with its parameters <rba>, <rbp> and <rbc> can be used to set and query prefer-ences for selecting frequency bands. The BGS3 normally uses an automode algorithm designed to recognize automatically the radio bands of thecurrent country, typically a combination of two bands. Commonly used dual-band combinations are, for exam-ple, 900/1800 MHz in European countries or 850/1900 MHz in North America. The standard radio band combi-nation of a country depends on the ARFCNs (Absolute Frequency Channel Number) and the MCCs (MobileCountry Code) visible at the air interface. This enables the ME to easily find the standard band or band combi-nation of a country every time after power-up and, thus, usually eliminates the need for the subscriber to makeany changes. So, if automode is used and the allowed bands are not restricted with <rba> the response param-eter <rbc> shows the standard band(s) of the current area. As an alternative, if any bands other than those automatically selected by the ME are needed, the automodecan be influenced using the AT^SCFG command. This may be necessary, for example, when running tests ofGSM applications, when access to specific radio bands shall be restricted or when the final product is notintended for operation in certain countries. Before changing the parameters <rba> or <rbp> ensure that no network activity occurs. The write commandcannot be executed when making a call, or sending / receiving short messages. Execution of the write command causes the ME to deregister from and re-register to the network, no matterwhether the selected <rbp> or <rba> setting really changes. Therefore, it is useful to have the URC "+CREG"enabled. The status of the SIM PIN authentication remains unchanged, eliminating the need to enter the SIMPIN again after the change.

The parameter <rba> is intended to restrict the allowed bands to less than four bands. By default, all four bandsare allowed. Each band not contained in <rba> is generally disabled. All bands of <rbp> must be contained in the range set with <rba>. The response parameter <rbc> will nevershow a value outside the <rba> range. <rba> has precedence over <rbp> and <rbc>. The <rba> value to select resp. deselect radio bands can be either a single band value or a multiple band valueas listed below. Parameter <rba> is global for the ME, non-volatile and will not be reset by AT&F. “1“ GSM 900 MHz“2“ GSM 1800 MHz“4“ GSM 1900 MHz“8“ GSM 850 MHz“3“ GSM 900 MHz + GSM 1800 MHz“5“ GSM 900 MHz + GSM 1900 MHz“10“ GSM 850 MHz + GSM 1800 MHz

<psm9to>(str)(+CSCS)

<rba>(str)(+CSCS)



“12“ GSM 850 MHz + GSM 1900 MHz“15“ GSM 900 MHz + GSM 1800 MHz + GSM 850 MHz + GSM 1900 MHz

Preferred radio band(s)The write command will trigger the band selection, starting with the user preference specified by <rbp>. Thismeans bands contained in <rbp> will be searched first, regardless of the standard band combination of the cur-rent country. The final result of the band selection can be read from <rbc>.If <rbp> was a band or band combination which differs from the standard band(s) and the requested band(s)are not visible at the air interface the ME reverts to the standard band(s) of this country. Please note that theband selection procedure is independent of the registration procedure, i.e. the ME selects a band no matterwhether or not there is a PLMN (Public Land Mobile Network) the ME can register to. So, if the <rbp> was aband or band combination supported by the country, but currently no PLMN can be found, the ME will select the"preferred" band (indicated by <rbc>) without registering to the network. To avoid registration problems, forexample when the settings are configured for testing the GSM application it is recommended that the tester firstactivates the desired band(s) on the test equipment and then executes the AT^SCFG write command. Besidesremember that the network registration also depends on the settings made with AT+COPS. The <rbp> is volatile and cannot be read back with the AT^SCFG read command. This is because the value isused only for triggering one single search operation. The parameter <rbp> may be one of the single bands or band combinations listed below. All preferred bandsmust be contained in the range of allowed bands set with <rba>, invalid combinations are not accepted. To givepriority to a certain single band or band combination and suppress all others simply select the same value bothfor <rbp> and <rba>. “1“ GSM 900 MHz“2“ GSM 1800 MHz“4“ GSM 1900 MHz“8“ GSM 850 MHz“3“ GSM 900 MHz + GSM 1800 MHz“5“ GSM 900 MHz + GSM 1900 MHz“10“ GSM 850 MHz + GSM 1800 MHz“12“ GSM 850 MHz + GSM 1900 MHz“15“ GSM 900 MHz + GSM 1800 MHz + GSM 850 MHz + GSM 1900 MHz

Currently selected radio band(s)<rbc> is the single band or band combination currently used by the ME, found either by the automode algorithmor after the network search was triggered with <rbp>. The <rbc> value is saved on power down. Whenrestarted next time the ME tries to select the same band(s) if these are visible. If the band(s) stored with <rbc>are not visible the ME uses the standard band(s) of the current country and consequently updates the <rbc>value. <rbc> is only a response parameter returned either after sending the read command AT^SCFG? or writingAT^SCFG="Radio/Band". In addition to <rbc> and to allow the subscriber to be notified whenever the selected band changes it is recom-mended to activate the "+CIEV: band" (see Section 3.3, AT^SIND). “1“ GSM 900 MHz“2“ GSM 1800 MHz“4“ GSM 1900 MHz“8“ GSM 850 MHz“3“ GSM 900 MHz + GSM 1800 MHz“5“ GSM 900 MHz + GSM 1900 MHz“10“ GSM 850 MHz + GSM 1800 MHz

<rbp>(str)(+CSCS)

<rbc>(str)(+CSCS)



“12“ GSM 850 MHz + GSM 1900 MHz“15“ GSM 900 MHz + GSM 1800 MHz + GSM 850 MHz + GSM 1900 MHz

Continuous Network Search ModeThis parameter can be used to influence the time the ME takes to register to the network. Parameter is global for the ME, volatile and will not be reset by AT&F. “0“(P) Normal

When trying to register to a network the ME sleeps longer than in "Fast mode"before restarting a network scan.

“1“ Fast"Fast mode" reduces the time the ME sleeps before restarting a network scanwhen trying to register.Advantage: If the ME is out of network service it may take less time to find anetwork.Disadvantage: Higher current consumption while the ME is out of network ser-vice.

Note: To monitor the search process it may be useful to have the "+CREG" URC enabled. Each time the networksearch starts, the URC "+CREG" equals "2" (searching). When the network search stops, the URC is issuedagain, indicating either "0" (not registered), or "1" (registered) or "5" (registered, roaming). As long as no networkcan be found, the URC will be toggling between "2" and "0".

Radio Output Power ReductionAccording to 3GPP Rel99, output power reduction for multiple TX slots is a mandatory feature. The amount ofpower reduction is configurable up to 3.0dB for 2TX. To optimize heat dissipation, power consumption and SARvalues it is recommended to use full power reduction (value "3"). Parameter is global for all interfaces, volatile and will not be reset by AT&F. “3“(P) Maximal Reduction at GMSK (0dB reduction for 1TX, 3dB for 2TX)

BufferSizeThis value defines the default size of the TCP receive queue in bytes. Higher values allow higher throughput butless number of parallel connections. The total throughput is limited by the GPRS/EDGE network resources andcannot exceed the theoretical maximum gross throughput of 230Kbit. Parameter is global for the ME and non-volatile. Use of default value is recommended. If changed the new valuetakes effect the next time you start an Internet service with AT^SISO. 3000...5200(&F)(D)...20000 Size of TCP receive buffer in bytes.

Possible number of parallel socket connections depending on buffer size:- 5200 bytes (default): max. 8 connections- 10000 bytes (medium): max. 4 connections- 20000 bytes (high): max. 2 connections

Initial Retransmission Timeout (IRT)1...3(&F)(D)...60 This parameter determines the time (in seconds) the TCP/IP stack will wait

before starting the first retransmission of packets during the initial connectionestablishment phase. The TCP protocol ensures the retransmission of packets several times atincreasing intervals until some upper limit is reached. This mechanism prevents packet loss and serious congestion problems. Parameter is global for the ME and non-volatile. Use of default value is recom-mended. If changed the new value takes effect the next time you start an Inter-net service with AT^SISO.

<cns>(str)(+CSCS)

<ropr>(str)(+CSCS)

<tcpBufSize>(str)(+CSCS)

<tcpIrt>(str)(+CSCS)



Maximum Number of Retransmissions (MR)1...10(&F)(D)...30 This parameter determines the maximum number of times to retransmit TCP

packets while the service is in connected state. If the service is still connecting(connection setup) another algorithm applies. The value set with <tcpMr> will be assumed as default for the <srv-ParmTag> "tcpMR" when a new service profile is created with AT^SISS. Ineach service profile, you can set another "tcpMR" value which has precedenceover the global value set with AT^SCFG. Existing service profiles are notaffected when you change the global value via AT^SCFG. Parameter is global for the ME and non-volatile. Use of default value is recom-mended.

Overall TCP Timer for outstanding connections (tcpOT)1...6000(&F)(D) This parameter specifies the number of seconds to wait before closing a con-

nection if TCP/IP packets are not acknowledged. Setting the maximum value is practically equivalent to deactivating the tcpOTmechanism because the maximum time would never be reached by the TCP/IP stack. The value set with <tcpOt> will be assumed as default for the <srv-ParmTag> "tcpOT" when a new service profile is created with AT^SISS. How-ever, in each service profile, you can set another "tcpOT" value which hasprecedence over the global value set with AT^SCFG. Existing service profilesare not affected when you change the global value via AT^SCFG. Parameter is non-volatile. Use of default value is recommended.

Selective Acknowledge (SAck)This parameter concerns a set of TCP extensions to improve performance and to provide reliable operation. Itdefines new TCP options for scaled windows and timestamps, which are designed to provide compatible inter-working with TCPs that do not implement the extensions. The set of TCP extensions to improve performance is described in RFC 1323. The value set with <tcpSack>enables or disables the set of TCP extensions. Parameter is global for the ME. Use of powerup value is recommended. “0“ Disable set of TCP extensions.“1“(P) Enable set of TCP extensions.

Transaction/TCP (T/TCP)This parameter concerns T/TCP, an extension of TCP to provide a transaction-oriented service. T/TCP is described in RFC 1644. The value set with <tcpTtcp> enables or disables T/TCP. Parameter is global for the ME. Use of powerup value is recommended. “0“(P) Disable T/TCP extension.“1“ Enable T/TCP extension.

<tcpMr>(str)(+CSCS)

<tcpOt>(str)(+CSCS)

<tcpSack>(str)(+CSCS)

<tcpTtcp>(str)(+CSCS)



URC mode or polling mode for Internet service commandsThis parameter enables or disables the presentation of the following URCs related to Internet service com-mands: "^SISR" URC, "^SISW" URC and "^SIS" URC for parameter <urcCause>=0 (Internet service events)."^SIS" URCs with <urcCause>=1 or 2 used to indicate incoming Socket connections are always enabled. Parameter is global for the ME and non-volatile. “on“(&F)(D) Enable URCs related to Internet service commands.

Throughout the Chapter "Internet Service AT Commands" the mode is alsoreferred to as URC mode.

“off“ Disable URCs related to Internet service commands. This requires the host application to employ polling techniques when using theInternet service AT commands: The host application is responsible to retrieveall status information needed to control an Internet session. The method isreferred to as polling mode.

CIEV Call Status IndicationThis parameter can be used to control the behaviour of URC "+CIEV: call". See also AT+CIND, AT+CMER andSection 7.1, Call Status Information.Parameter is global for all interfaces and will not be reset by AT&F. “restricted“(P) URC "+CIEV: call" will be issued only when a Call Status transition ends in

state "active" or "unknown" (see Section 7.1, Call Status Information) for a callin the list of active calls.

“verbose“ URC "+CIEV: call" will be issued when any state transition (including transi-tions beginning or ending in state "unknown") occurs in the list of active calls,or when a traffic channel is established.

SLCC Call Status IndicationThis parameter can be used to control the behaviour of URC "^SLCC". See also AT^SLCC and Section 7.1, CallStatus Information.Parameter is global for all interfaces and will not be reset by AT&F. “restricted“ URC "^SLCC" will be issued only when a Call Status transition ends in state

"active" or "unknown" (see Section 7.1, Call Status Information) for a call in thelist of active calls

“verbose“(P) URC "^SLCC" will be issued when any state transition (including transitionsbeginning or ending in state "unknown") occurs in the list of active calls, orwhen a traffic channel is established.

URC RING lineThis parameter can be used to control the behaviour of the RING line to indicate URCs (both for idle interfacesand, if configured by the parameter "URC/Datamode/Ringline", if link is reserved) and, if configured, the indicatorfor incoming IP packets (see parameter "GPRS/RingOnIncomingData" (<groid>).Parameter is local for the interface, volatile and will not be reset by AT&F. “off“ URC is not indicated by RING.“local“(P) URC will be indicated by an activated RING line of the interface on which the

URC appears “asc0“ URC is indicated by an activated RING0 line.

<tcpWithUrc>(str)(+CSCS)

<succ>(str)(+CSCS)

<sucs>(str)(+CSCS)

<uri>(str)(+CSCS)



URC Datamode RING lineThis parameter specifies whether RING or BREAK is used for the signaling of URCs when the TA-TE link isreserved (e.g. during circuit-switched data calls, fax connections, in GPRS data mode, in transparent TCPaccess mode opened with AT^SIST or during the execution of an AT command).Parameter is global for all interfaces, volatile and will not be reset by AT&F. “off“(P) URC will be indicated by BREAK“on“ URC is indicated by an active RING line for a time which is configured by the

parameter "URC/Ringline/ActiveTime" (<urat>). The RING line which will beused, can be configured by the parameter "URC/Ringline" (<uri>).

URC RING line Active TimeThis parameter can be used to control how long the RING line is activated to indicate URCs (both for idle inter-faces and, if configured by the parameter "URC/Datamode/Ringline" (<udri>), if link is reserved) and, if con-figured by the parameter "GPRS/RingOnIncomingData", to indicate incoming GPRS IP data packets(<groid>).Parameter is global for all interfaces, volatile and will not be reset by AT&F. “0“ RING line will be activated for a time between 4.6 and 9.2 ms.“1“ RING line will be activated for about 100ms.“2“(P) RING line will be activated for about 1s.

Notes• Any changes to parameters of the Autoexec function will be saved and restored on next power-up only when

the ME is switched off via AT commands (e.g. AT+CFUN or AT^SMSO). • Please keep in mind, that each time the ME is restarted the timers of all autoexec actions configured with

<AutoExecType>=1 and <AutoExecPeriod> will be reinitialized and restarted. As a result, an autoexecaction configured at a time later then a scheduled automatic restart would never be executed.

• Be careful using <AutoExecType>=1 with small period values and shutdown or reset AT commands, sinceonly little time remains to change these settings again after BGS3 restart.

• If <AutoExecATC> uses AT commands containing secret data, this information may be retrieved withAT^SCFG?. For instance, this applies if using AT+CPIN.

• Parameters "GPRS/ATS0/withAttach" (<gs0aa>) and "GPRS/RingOnIncomingData" (<groid>) are avail-able only for modules supporting GPRS.

ExamplesEXAMPLE 1

Usage of "AutoExec":Enable sending of a short message (SMS) on next DTR activation (OFF-ON transition). Sent SMS isassumed to be stored at first location of storage selected with AT+CPMS and AT^SSMSS, i.e. SMS may besent either from SIM or ME storage. Also refer to AT+CMSS and AT+CMGW. Since SMS transmission and ongoing calls are possible at the sametime there is no need to wait until all calls have ended (<AutoExecMode>=0).

<udri>(str)(+CSCS)

<urat>(str)(+CSCS)

AT+CMGF=1 Enable SMS text mode.OKAT+CNMI=1,1 Enable "+CMTI:" URC to be indicated when a short

message is received.OKAT+CMGD=1 Delete first SMS location.OKAT+CMGW="01522400045",145 Start writing a short message.



If a DTR activation has occurred the ME issues the "Autoexec" URC followed by the response of the executedcommand; the message reference in this case:

EXAMPLE 2

Usage of "AutoExec":Configure BGS3 to perform a reset every 10 hours. The execution of the reset command shall be deferreduntil after any calls have ended.For details regarding software controlled power down refer to AT+CFUN and AT^SMSO.

After ten hours:

EXAMPLE 3

Usage of "AutoExec":Switch off the ME after three minutes without restarting it.For details regarding software controlled power down refer to AT+CFUN and AT^SMSO.Please keep in mind that if the GSM alphabet is enabled special characters within the executed AT commandshall be issued as escape sequences. A list of typical escape sequences can be found in Section 1.6.1, GSMalphabet tables and UCS2 character values. For example, the caret character "^" included in all proprietaryAT commands shall be given as "\1B\14".

After three minutes:

EXAMPLE 4

Usage of "AutoExec":Deactivate a timer-driven Autoexec function configured at <AutoExecIndex> 0 (such as the periodic auto-matic reset or the automatic switch-off functions configured in the preceding examples):

>Test-SMS to be sent from storage! Enter the text of the message. Finish with CTRL-Z.+CMGW: 1 Confirms that message is stored to first location.OKAT^SCFG="AutoExec",1,0,0,0,"AT+CMSS=1" Enable execution on next DTR activation.^SCFG: "AutoExec","1","0","0","0","at+cmss=1"^SCFG: "AutoExec","0","1","0","0","","000:00:00","000:00:00"^SCFG: "AutoExec","0","1","1","0","","000:00:00","000:00:00"^SCFG: "AutoExec","0","1","2","0","","000:00:00","000:00:00"OK

^SCFG: "AutoExec",0,0,1,0,"AT+CMSS=1"OK Confirms that AT+CMSS=1 has been issued.+CMSS: 16

AT^SCFG="AutoExec",1,1,2,5,"AT+CFUN=0,1","010:00:00"...OK

^SCFG:"AutoExec",1,1,2,5,"AT+CFUN=0,1"OK Confirms that AT+CFUN=0,1 has been issued.SYSSTART BGS3 has restarted. Remember that the

"^SYSSTART" URC will not appear if autobauding isenabled.

AT^SCFG="AutoExec",1,1,0,0,"AT\1B\14SMSO","000:03:00"^SCFG: "AutoExec","0","0","0","0",""^SCFG: "AutoExec","1","1","0","0","ATSMSO","000:03:00","000:02:59"

Please note that the indication of the escapesequence in the write command response dependson the used program.

^SCFG: "AutoExec","0","1","1","0","","000:00:00","000:00:00"^SCFG: "AutoExec","0","1","2","0","","000:00:00","000:00:00"OK

^SCFG:"AutoExec",0,1,1,0,"AT^SMSO" ^SMSO: MS OFF OK^SHUTDOWN Indicates that AT^SMSO was successfully executed.

The ME enters the POWER DOWN mode.



EXAMPLE 5

Usage of "URC/Ringline" and "URC/Datamode/Ringline":

AT^SCFG="AutoExec",0,1,0...OK

AT+CSCS="GSM" Switch to GSM character set.OKAT^SCFG? Query all parameters....^SCFG:"URC/Datamode/Ringline","off" While the TA-TE link is reserved URCs will be indi-

cated by BREAK.^SCFG:"URC/Ringline","local" URCs on this interface will be indicated by Ring line

associated to the interface (e.g. RING0 for ASC0)....OKAT^SCFG="URC/Datamode/Ringline","on"^SCFG:"URC/Datamode/Ringline","on" While the TA-TE link is reserved URCs will be indi-

cated by an activated "local" Ring line.OKAT^SCFG="URC/Ringline","asc0"^SCFG:"URC/Ringline","asc0" URCs on this interface will be indicated by an acti-

vated RING0 no matter whether or not the TA-TE linkis reserved.

OKAT^SCFG="URC/Datamode/Ringline","off"^SCFG:"URC/Datamode/Ringline","off" URCs on this interface will be indicated by an acti-

vated RING0 if the TA-TE link is not reserved and byBREAK if the TA-TE link is reserved.

OKAT^SCFG="URC/Ringline" Disable any Ring line indication for URCs on this

interface.^SCFG:"URC/Ringline","off"OK

BGS3 AT Command Set 2.15 AT^SM20


2.15 AT^SM20 Set M20 compatibility mode

M20 is an earlier, widely used GSM engine. The AT^SM20 command selects different modes of responsesreturned upon execution of the commands ATD and sms commands like e.g. AT+CMGW. Please note that theAT^SM20 command has no effect on any other features and is not intended to adjust other differences betweenM20 and BGS3.

Syntax


Call setup response modeApplies only to voice calls.0 Set compatibility to Cinterion Wireless Modules.

ME will return "OK" immediately after attempting a call with the ATD command.In case of failure, additional call release indications, such as "NO DIALTONE,"NO CARRIER", "BUSY" will follow.

1(&F) Default call setup mode, compatible to M20.ME will return "OK" in case of a successful connection, otherwise one of thecall release indications "NO DIALTONE, "NO CARRIER", "BUSY" are indi-cated.

Response mode for sending and writing short messagesApplies to the sms commands like e.g. AT+CMGS and AT+CMGW command.0 Set compatibility to Cinterion Wireless Modules.

ME will return +CMS ERROR: <err> when writing or sending of short mes-sages fails.

1(&F) Default mode for sending and writing short messages, compatible to M20.ME will return "OK", no matter whether or not sms command was successfullyexecuted.

Test Command

AT^SM20=?Response(s)

OK

Read Command

AT^SM20?Response(s)

^SM20:<CallMode>, <CmgwMode>OK

Write Command

AT^SM20=<CallMode>[, <CmgwMode>]Response(s)

OK


- + + + + + - -

<CallMode>(num)

<CmgwMode>(num)

BGS3 AT Command Set 3. Status Control Commands


3. Status Control Commands

The AT Commands described in this chapter allow the external application to obtain various status informationfrom the BGS3.

3.1 AT+CMER Mobile Equipment Event Reporting

This command controls details of the "+CIEV" URC presentation related to AT^SIND and AT+CIND. If registeredvia these commands the URCs are sent whenever a value of the related indicator changes. In addition, AT+CMER controls "^SLCC" URCs related to AT^SLCC. For details refer to Call Status Infor-mation, AT^SLCC and AT^SCFG, parameter <sucs>.The read command returns the URC presentation mode <mode> and among others, the indicator event reportingstatus <ind>.The write command enables and disables the presentation of "+CIEV: <indDescr>, <indValue>1[, <ind-Value>2]" URCs. <indDescr> refers to the name of a "+CIEV" indicator and <indValue> is the new value ofthis indicator. After AT+CMER has been switched on, URCs for all registered indicators will be issued. See exam-ples provided in Section 3.2, AT+CIND and Section 3.3, AT^SIND.

Syntax

Unsolicited Result Code+CIEV: <indDescr>, <indValue>1[, <indValue>2]

A value of an indicator has changed.

Test Command

AT+CMER=?Response(s)

+CMER: (list of supported<mode>s), (list of supported <keyp>s), (list of supported <disp>s), (list of supported <ind>s), (list of supported <bfr>s)OK

Read Command

AT+CMER?Response(s)

+CMER: <mode>, <keyp>, <disp>, <ind>, <bfr>OK

Write Command

AT+CMER=[<mode>[, <keyp>[, <disp>[, <ind>[, <bfr>]]]]]Response(s)



- + + + + + - - GSM 07.07

BGS3 AT Command Set 3.1 AT+CMER



0(&F) Discard "+CIEV" and "^SLCC" URCs. 1 Discard "+CIEV" and "^SLCC" URCs when TA-TE link is reserved, e.g. in

online data mode. Otherwise they are forwarded directly to the TE. 2 Buffer "+CIEV" and "^SLCC" URCs in the TA while TA-TE link is reserved, e.g.

in online data mode, and flush them to the TE afterwards. Otherwise they areforwarded directly to the TE.

3 Forward "+CIEV" and "^SLCC" URCs directly to the TE. If BGS3 is in onlinedata mode, URCs are signaled via sending BREAK and stored in a buffer.Once it is back in command mode e.g. after +++ was entered, all URCs storedin the buffer will be output.

0(&F) Keypad event reporting is not supported by BGS3.

0(&F) Display event reporting is not supported by BGS3.

0(&F) Disable indicator event reporting. 2 Enable indicator event reporting.

0(&F) TA buffer of URCs defined within this command is cleared when <mode> 1..3is entered.

Name of indicator; for a list of all supported indicators please refer to AT+CIND and AT^SIND.

Value of indicator; for a list of all values for the supported indicators please refer to AT+CIND and AT^SIND.

Notes• If the ME operates on different instances (MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings for

routing and indicating SMS. For example, if messages shall be routed directly to one instance of the TE (setwith AT+CNMI, AT^SSDA), it is not possible to activate the presentation of URCs with AT+CMER or AT+CNMIon another instance. Any attempt to activate settings that conflict with existing settings on another interface,will result in "+CME ERROR", or accordingly "+CMS ERROR".

• It is recommended that priority be given to AT+CMER=<mode> 2 or 3. Otherwise, if <mode> equals 1, URCswill be discarded in case of long running AT commands or an active data connection.

• If <mode> equals 3, URCs are signaled via sending BREAK only on ASC0 or ASC1.

<mode>(num)

<keyp>(num)

<disp>(num)

<ind>(num)

<bfr>(num)

<indDescr>(str)

<indValue>(num)

BGS3 AT Command Set 3.2 AT+CIND


3.2 AT+CIND Indicator control

The AT+CIND command controls the presentation of Indicator Event Reports related to various functions suchas battery charge level, signal quality, service availability, sound generation, indication of unread short mes-sages, full SMS storage, call in progress or roaming activities. Use of AT+CIND has become outdated. Rather we recommend the more powerful AT^SIND command which iseasier to use and provides additional indicators. All indicators provided by AT+CIND can be handled withAT^SIND as well.

AT+CIND supports two ways to get the values related to indicators: • One approach is to query the current status of each indicator by using the read command AT+CIND?. It

returns the status no matter whether the indicator has been registered with the write commandAT+CIND=[<mode>[,<mode>[,...]]].

• The other way is an event-driven notification based on the "+CIEV" URCs. In this case, the ME will automat-ically send a message to the application, whenever the value of an indicator changes. The application shouldbe designed to react adequately when receiving a URC. The presentation of these URCs depends on two settings: - The indicators must be registered with the write command AT+CIND=[<mode>[,<mode>[,...]]]. When the

ME is switched on all of them are in registered mode. Any indicator can be excluded if deregistered with<mode>=0. To register or deregister an indicator the AT+CIND write command requires to type the value<mode>=1 or 0 exactly at the position where the indicator is located in the list. This is not necessary withAT^SIND which allows to specify indicators by name. See examples below.

- The presentation of the registered indicators must be enabled with AT+CMER.

Syntax


Integer type value, which shall be in range of corresponding <indDescr>

Test Command

AT+CIND=?Response(s)

+CIND: (<indDescr>, list of supported <indValue>s)[, (<indDescr>, list of supported <indValue>s)[, ...]]OK

Read Command

AT+CIND?Response(s)

+CIND: <indValue>[, <indValue>[, ...]]OKERROR+CME ERROR: <err>

Write Command

AT+CIND=<mode>[, <mode>[, ...]]Response(s)



- + + + + + - - GSM 07.07

<indValue>(num)



String values and their <indValue> ranges.More indications are available via AT^SIND. Therefore use of AT^SIND for control of all indications is recom-mended.The following indications are accessible via AT+CIND: “battchg“ Battery charge level 0..4 or 5 if no measuring is performed, e.g because no bat-

tery is connected. Also refer to AT^SBC. “signal“ Signal quality (0..7) or (99) if not measurable

The indicated value is the bit error rate of the signal received. Bit errors are esti-mated values. See also AT+CSQ.

“service“ Service availability (0-1)0: Not registered to any network1: Registered to home network or, if "roam"=1 then registered to another net-work

“sounder“ Sounder activity (0-1)Reports every event that causes the ME to generate a tone.Value 1 means for example:Incoming call - ME is ringing. Note that the URC "+CIEV: sounder" will be out-put only if ringing tones are activated with AT^SRTC.Waiting call - ME generates waiting call tone (if call waiting is enabled).Outgoing call - ME generates Call Progress tone.Outgoing call - ME generates BUSY tone.The value changes to 0 when the tone stops.

“message“ Unread received short message (0-1) “call“ Call in progress (0-1). Indicator value is "1" if at least one call is in state "active"

or "held".Depending on the parameter <succ> selected with AT^SCFG the indicator"call" will be issued • when a state transition ends in state "active" or state "unknown", if

<succ>="restricted", • when any state transition (including transitions beginning or ending in state

"unknown") occurs in the list of active calls or when a traffic channel isestablished, if <succ>="verbose".

Also refer to Section 7.1, Call Status Information. “roam“ Roaming indicator (0-1)

0: Registered to home network or not registered1: Registered to other network

“smsfull“ A short message memory storage in the MT has become full (1) or memorylocations are available (0), i.e. range is (0-1)

“rssi“ Received signal (field) strength (0..5) 0: signal strength ≤ -112 dBm1-4: signal strength in 15 dB steps5: signal strength ≥ -51 dBm99: not known or not detectableReceived signal (field) strength can also be obtained with AT+CSQ. However,the signal strength is scaled to value range 0..31 by this command.

0 Indicator is deregistered. The indicator will not be presented as "+CIEV" URC,but can be queried with AT+CIND?.

[1](&F)(P) Indicator is registered, indicator event report allowed.

<indDescr>(str)

<mode>(num)



Notes• Due to its restrictive value range, indicator "call" does not clearly reflect specific call states (such as alerting,

active, held etc.), but rather serves to trigger the application to retrieve the new call status from the list of cur-rent calls with the AT commands AT^SLCC, AT+CLCC or AT^SCNI.

• If AT^SCFG setting <succ>="verbose", indicator "call" will be issued also when a traffic channel is estab-lished, or when a call enters states "terminating" or "dropped" (see Call Status Information).In these cases, the relevant information about the cause of the display is available only from AT commandAT^SLCC.

ExamplesEXAMPLE 1

EXAMPLE 2

Deactivation of indicator "sounder" via AT+CIND

EXAMPLE 3

Deactivation of indicator "sounder" via AT^SIND

^SYSSTARTAT+CPIN=9999OKAT+CIND?+CIND: 5,0,1,0,0,0,0,0 The battery is either full or no battery is connected to the ME. The bit

error rate of the signal quality is not available (since there is no call inprogress). The ME is registered to its home network.

OKAT+CMER=2,0,0,2 Now activate the Indicator Event Report with AT+CMER.OK+CIEV: battchg,5+CIEV: signal,99+CIEV: service,1+CIEV: sounder,0+CIEV: message,0+CIEV: call,0+CIEV: roam,0+CIEV: smsfull,0+CIEV: rssi,5 Full receive signal strength.ATD0123456; Make a call.OK+CIEV: sounder,1 A set of "+CIEV" URCs is received.+CIEV: call,1+CIEV: sounder,0+CIEV: call,0 Called party hangs up.NO CARRIERAT+CIND=,,,0,,0 Deregister the indicators "sounder" and "call".OKATD0123456; Dial the same call.OK This time, no URCs are displayed.NO CARRIER Called party hangs up.

AT+CIND? Query the current status of indicators.+CIND: 5,0,1,0,1,0,0,0,4OKAT+CIND=,,,0 To deactivate indicator "sounder" (= fourth item in list of indicators).OK

AT^SIND="sounder",0 To deactivate indicator "sounder".^SIND: sounder,0,0OK

BGS3 AT Command Set 3.3 AT^SIND


3.3 AT^SIND Extended Indicator Control

Designed for extended event indicator control AT^SIND • offers greater flexibility than the standard command AT+CIND, • offers several extra indicators, • can show the current status of all indicators supported by AT+CIND and AT^SIND, • can be used to register or deregister the indicators of both commands, • displays all indicator event reports via "+CIEV" URCs. Presentation mode of the generated URCs is controlled via AT+CMER.

The AT^SIND read command provides a list of all indicators supported by AT+CIND and AT^SIND. Each indica-tor is represented with its registration mode and current value. The AT^SIND write command can be used to select a single indicator in order to modify its registration and toview the current value.

SyntaxTest Command

AT^SIND=?Response(s)

^SIND: (<indDescr>, list of supported <indValue>s)[, (<indDescr>, list of supported <indValue>s)[, ...]], (list of supported <mode>s)OK

Read Command

AT^SIND?Response(s)

^SIND: <indDescr>, <mode>, <indValue>[^SIND: <indDescr>, <mode>, <indValue>]...

In case of <indDescr>="eons"^SIND: "eons", <mode>, <eonsOperator>, <servProvider>

In case of <indDescr>="nitz"^SIND: "nitz", <mode>, <nitzUT>, <nitzTZ>, <nitzDST>

In case of <indDescr>="lsta"^SIND: "lsta", <mode>, <lstaLevel>OKERROR+CME ERROR: <err>

Write Command

AT^SIND=<indDescr>, <mode>Response(s)

^SIND: <indDescr>, <mode>, <indValue>

In case of: <indDescr>="eons" and <mode>=2^SIND: "eons", <mode>, <indValue>, <eonsOperator>, <servProvider>

In case of: <indDescr>="nitz" and <mode>=2^SIND: "nitz", <mode>, <nitzUT>, <nitzTZ>, <nitzDST>OK




URC 1

Format of the standard indicator:+CIEV: <indDescr>, <indValue>

Value related to an indicator has changed.

URC 2

Format of the Voice Message indicator, if the number of waiting messages is delivered by the network: +CIEV: <indDescr>, <indValue>, <vmCounter>

If the number of waiting messages is not delivered the standard indicator applies.

URC 3

Format of the "eons" indicator: +CIEV: <indDescr>, <indValue>, <eonsOperator>, <servProvider>

One URC is issued for each new LAI (Location Area Information) broadcast by the network.

URC 4

Format of the "nitz" indicator: +CIEV: <indDescr>, <nitzUT>, <nitzTZ>, <nitzDST>

URC 5

Format of the "lsta" indicator:In case <indValue> equals "0". +CIEV: <indDescr>, <indValue>, <lstaEdv>, <lstaRssi>

The URC is issued for every radio link error. It provides the error downcounter value corresponding to numberof consecutive errors on downlink and the RSSI of the serving cell.Error downcounter value of 10 corresponds to first error occurred on downlink, 0 corresponds to last beforecell loss.

URC 6

In case <indValue> equals "1". +CIEV: <indDescr>, <indValue>, <lstaNo>, <lstaMin>, <lstaMax>, <lstaMean>, <lstaVar>

After the error downcounter reaches the value 0 the URC provides some statistic parameters of signalstrength distribution across the band.

ERROR+CME ERROR: <err>

Write Command

AT^SIND="lsta", <mode>[, <lstaLevel>]Response(s)

^SIND: "lsta", <mode>[, <lstaLevel>]OKERROR+CME ERROR: <err>


- + + + + + - -

Write Command (Continued)

AT^SIND=<indDescr>, <mode>Response(s)




String values and their <indValue> ranges.All indicators supported by AT+CIND are accessible with this command, too. A detailed description of these indi-cators can be found there.The following indicators are accessible via AT^SIND only: “audio“ Activity of the built-in audio unit.

“vmwait1“ Voice Message Waiting Indication for line 1

"vmwait1" and "vmwait2" indicate the receipt of a special short message witha Voice Message Waiting Indicator. The service must be provisioned by theoperator. The numbers 1 or 2 in "vmwait1" and "vmwait2" are related to the two lines ofthe Alternate Line Service (ALS), also defined in CPHS Phase 2 standard. Forfurther details refer to the AT^SALS command. The presentation mode of the indicator varies with the operator: If more thanone message are waiting, some operators only indicate the first one, othersdeliver the indicator each time a new voice message is put into the mailbox.After the subscriber has retrieved all voice messages the service center auto-matically sends another message indication which provides the value 0. Some operators may also send the number of waiting voice messages alongwith the indication. In this case, the number will be displayed by the BGS3 aspart of the URC. For example, "+CIEV: vmwait1,1,5" notifies that five new voicemessages are waiting. However, it should be noted that neither the read com-mand AT^SIND? nor the write command AT^SIND=<mode>,2 display thenumber of waiting messages. The "vmwait" indicators do not apply if a network provider signals new voicemail(s) via standard SMS. In this case the indicator "message" will be displayed(see AT+CIND).

“vmwait2“ Voice Message Waiting Indication for line 2

“ciphcall“ Ciphering Status Change Indication

As stated in GSM specifications 02.07 and 02.09 the ciphering indicator featureallows the BGS3 to detect that ciphering is not switched on and to indicate thisto the user. The ciphering indicator feature may be disabled by the home network operatorsetting data in the "administrative data" field (EFAD) in the SIM, as defined inGSM 11.11. If this feature is not disabled by the SIM, then whenever a connection is inplace, which is, or becomes unenciphered, an indication shall be given to theuser. This enables the user's decision how to proceed. Read command returns valid ciphering status only if a call is in progress oractive. If EFAD setting disables the ciphering indicator feature read command alwaysindicates a ciphered link and no URC presentaion will take place. The following restrictions apply if the same serial channel is used for AT^SIND

<indDescr>(str)

0 Audio unit not active.1 Audio unit is active, for example:

MO voice call: Indicator is output with value 1 when dialing starts.MT voice call: Indicator is output with value 1 when call is ringing.

0 The value 0 notifies that no new voice message is available, and is pro-vided by the service center to clear the voice message indication after the subscriber has retrieved all voice messages.

1 The value 1 notifies the subscriber that the mailbox contains one or several messages.

0 See description of "vmwait1". 1 See description of "vmwait1".

0 Current call or SMS is not ciphered.1 Current call or SMS is ciphered.



"ciphcall" indication and for the action triggering this URC. In general, the rec-ommended solution is to use a dedicated channel for all status signalling viaURCs. • If an unciphered mobile originated SMS is performed, AT^SIND "ciphcall"

URCs on the same serial channel will be issued after the related "OK" andindicate the ciphering state at this time.

• If an unciphered mobile originated data call is performed, AT^SIND "ciph-call" URCs on the same serial channel will be issued after the interface isnot longer blocked by the call (call is released or temporarily stopped) andindicate the ciphering state at this time.

“eons“ Enhanced Operator Name String (EONS) Indication The Enhanced Operator Name String indicator feature allows the BGS3 to out-put various operator names for different PLMN identities via URC. It also allowsthe output of a different operator name based on a subset of the registered net-work by using a range of Location Area Codes (LACs) or a single LAC.The presentation of the "eons" indicator is determined by network activity. Forexample, the indicator appears every time a location update occurs or a NITZinformation is sent, no matter whether or not the status of the EONS informa-tion has changed. This means that the same EONS information may bereported several times.The EONS tables are stored in the SIM card and will be read at power-up. Following are the SIM Elementary Files that are affected by the introduction ofEONS feature in the SIM card:EFSST (SIM Service Table) - describes which features are active. EFOPL (Operator PLMN List) - contains the PLMN identification and location IDtogether with the index of the corresponding PNN record EFPNN (PLMN Network Name) - contains the full and short form version of thenetwork name for the registered PLMN If the Operator Name Source is CPHS Operator Name String long and shortform, refer to <indValue>, the following two SIM Elementary Files will beused: EFONString (Operator Name String) - contains the name of the PLMN operatorwho issued the SIM. EFOPShort (Operator Name Short form) - contains a short form of the name ofthe PLMN operator who issued the SIM.

“nitz“ Network Identity and Time Zone indicationThis indicator shows the time relevant information elements of an MM Informa-tion (MMI) or GMM Information (GMMI) message received from the network(see GSM 24.008, ch. 9.2.15a and 9.4.19). The network usually sends a NITZindicator when the mobile attaches to the network, when it enters a locationarea with different time zone or when a daylight change occurs.A NITZ indicator may consist of the following parameters: Universal Time (UT),local Time Zone (TZ), Daylight Saving Time (DST). All information elements ofMMI/GMMI are optional and therefore, the presentation of the parameters<nitzUT>, <nitzTZ>, <nitzDST> varies with the network. For example, thenetwork may send all three parameters UT, TZ, DST, or only UT and TZ or onlyTZ.

UT is indicated in usual date/time format and represents the current world time(GMT) at the moment when sent.TZ is given as a positive (east) or negative (west) offset from UT in units of 15minutes.DST shows the number of hours added to the local TZ because of daylight sav-ing time (summertime) adjustment. Usually DST is 1 hour but it can be also 2hours in certain locations.

Example for time and time zone with DST:+CIEV: nitz,"04/07/23,13:39:20",-28,1In this example TZ is -28, showing a time offset of -7 hours (west) to Universal



Time/GMT (which never changes for DST). DST is 1 which indicates that onehour was added to TZ because of Daylight Saving Time. If a network does notsend the DST parameter the TZ value would be -32 (8 hours west) as wouldbe done in winter:+CIEV: nitz,"04/11/23,13:39:20",-32

Please be aware that despite the last NITZ value can be looked up again via"AT^SIND=nitz,2" the returned values may be out of date. Especially the UTvalue is obsolete because there is no internal NITZ clock and therefore no con-tinuation of UT.NITZ values are lost when the module detaches from network. Also when amanual network selection fails and the module automatically falls back to theprevious network the NITZ values cannot be recalled. Nevertheless an indi-cated time zone is valid until a new MMI/GMMI will trigger another NITZ indi-cation.

“simlocal“ SIM availability "+CIEV" URC indicates if the SIM is available.

“simstatus“ SIM Status IndicationThe SIM Status Indicator allows to query the status of the SIM (SubscriberIdentity Module).

“band“ Currently selected frequency band or band combination.

“lsta“ Link Stability IndicationThe Link Stability indicator feature allows the BGS3 to output radio link errorsand statistic parameters of signal strength distribution across the band viaURC.

The presentation of the "lsta" indicator is determined by the radio link spectrumshape. For example, each time a radio link error appears the URC indicates anError Downcounter value and the RSSI of the serving cell to provide some kindof warning. Every consecutive error decrements the Error Downcounter valueand successful downlink signal reception resets it to start value of 10. The fac-tor on which Error Downcounter is decremented depends on network settings.Error Downcounter value 0 means that the ME has lost the cell and will startthe cell reselection process. In this case the URC is enhanced and includes thefollowing statistic parameters of signal strength distribution across the band.These are:

0 SIM removed. 1 SIM inserted.

0 SIM card removed.Note: Another way to verify the SIM card connection is the "^SCKS" URC enabled with AT^SCKS. For use after restart, its presentation mode can be stored to the user profile with AT&W.

1 SIM card inserted. 2 SIM PIN1 not required - SIM card unlocked. BGS3 automatically regis-

ters to the GSM network without requesting SIM PIN1. 3 SIM PIN1 required - SIM card locked. SIM PIN1 must be entered to

enable BGS3 to register to the GSM network. 4 Personalization info ready - CHV (Card Holder Verification) data have

been verified (if required). 5 SIM initialization completed - ME has finished reading SIM data.

1...15 Identical with <rbc> of AT^SCFG. The value indicates the band(s) cur-rently available for network selection, depending on the network config-uration either a single band or a dualband combination. The URC appears whenever the status of the currently available band(s) changes, for example after using the AT^SCFG command to change the "Radio/Band" parameters <rba> or <rbp>. Please see AT^SCFG for further detail about the feature "Radio/Band" selection.

0 Radio link error.1 Radio link signal strength distribution.



- Number of reported channels,- Maximal signal strength value,- Minimal signal strength value,- Mean value of signal strength across frequency band and - Variance of signal strength across frequency band.To avoid that radio link error URCs are output too often, when radio conditionsare bad, you can select a lower warning level with <lstaLevel>.

Integer type value in the range stated above for the corresponding <indDescr>.

Notes specific to the EONS feature: If the indicator is "eons", the <indValue> is a type associated to the operator name according to GSM 22.101[23]. This type depends on the source of the operator name. Priority of types associated to the operator names is defined as follows (the type listed first has the highest pri-ority). If a type cannot be indicated the next one will be used.

The name information received by the NITZ service (type 3) is stored non-volatile. It replaces the operator nameof the registered PLMN (type 4) or its numeric form (type 5) stored in the ME. But if the ME, after restart, registersto another PLMN that is not equal to the saved NITZ name information, the NITZ name information must beinvalidated. If the type is 2, 4 or 5, AT+COPS with the appropriate <mode> displays the same operator name.

0 Indicator is deregistered, i.e. no such indicator event report (URC) will beissued. <mode>=0 is power-up and factory default of indicators defined byAT^SIND only.

1 Indicator is registered. • Indicator event reports are controlled via AT+CMER. • All indicators can be registered or deregistered via AT^SIND, but different

default settings apply: Power-up and factory default of the indicators sup-ported by AT+CIND is <mode>=1, while, as stated above, indicators definedby AT^SIND only are set to <mode>=0.

2 Query the registration status and the current value of a single indicator type.

If delivered by the network: Number of new voice messages sent as part of the Voice Message Waiting Indicator.Refer to <indDescr>.

Operator in format which depends on the type associated to the operator name. Refer to <indValue>.

<indValue>(num)

0 Not registered.1 EF-OPL and EF-PNN (alphanumeric format, can contain up to 24 characters.)2 Operator Name String in long and short format according to Common PCN

Handset Specification (CPHS) [24] (alphanumeric format, can contain up to 16 characters).

3 Name information received by the NITZ service long and short form (alphanu-meric format, can contain up to 16 characters). The short form will be displayed only if EFOPShort from CPHS is available.

4 Any operator name stored internal to the ME (alphanumeric format, can con-tain up to 16 characters).

5 Broadcast MCC-MNC (numeric format which consists of a 3-digit country code plus a 2- or 3-digit network code).

<mode>(num)

<vmCounter>

<eonsOperator>



Service Provider Name according to the status settings (SIM Service No. 17) in the SIM Service Table (SST) ofthe SIM.

Universal Time delivered as part of the "nitz" Indicator. Refer to <indDescr>.

Time Zone delivered as part of the "nitz" Indicator. Refer to <indDescr>.

Adjustment for Daylight Saving Time as part of the "nitz" Indicator. Refer to <indDescr>.

Warning Level (0-10)User value to limit the indication of radio link errors. Refer to <indDescr>.

EDV (0-10)Error Downcounter value. Refer to <indDescr>.

(value-110) dBm Received signal strength indication value. Refer to <indDescr>.

Number of reported channels. Refer to <indDescr>.

(value-110) dBm Minimal received signal strength value. Refer to <indDescr>.

(value-110) dBm Maximal received signal strength value. Refer to <indDescr>.

(value-110) dBm Mean value of received signal strength across frequency. Refer to <indDescr>.

Variance of signal strength across frequency. Refer to <indDescr>.

Example

Activation and use of indicator "audio":

<servProvider>(str)

<nitzUT>

<nitzTZ>

<nitzDST>

<lstaLevel>(num)

<lstaEdv>(num)

<lstaRssi>(num)

<lstaNo>(num)

<lstaMin>(num)

<lstaMax>(num)

<lstaMean>(num)

<lstaVar>(num)



AT^SIND="audio",1 You register the indicator "audio".^SIND: audio,1,0OKAT+CMER=2,,,2 You activate the Indicator Event Report with AT+CMER.OK A set of all registered URCs is presented. (Please note that the example

includes the indicators registered due to the power-up default settingsof AT+CIND.)

+CIEV: battchg,5+CIEV: signal,99+CIEV: service,1+CIEV: sounder,0+CIEV: message,1+CIEV: call,0+CIEV: roam,0+CIEV: smsfull,0+CIEV: rssi,4+CIEV: audio,0ATD030123456; You make a call.OK+CIEV: audio,1+CIEV: sounder,1+CIEV: call,1+CIEV: signal,0+CIEV: sounder,0ATH You hang up.OK+CIEV: call,0+CIEV: rssi,3+CIEV: audio,0+CIEV: signal,99+CIEV: rssi,4

BGS3 AT Command Set 3.4 AT+CEER


3.4 AT+CEER Extended Error Report

AT+CEER returns an extended error report regarding the reason of the last • call release• failure to set up a call (both mobile originated or terminated)• failure to modify a call by using Supplementary Services • failed attempt to activate, register, query, deactivate or deregister a Supplementary Service • unsuccessful GPRS attach or unsuccessful PDP context activation • GPRS detach or PDP context deactivation The release cause report is presented in numeric format. Default output in case of a none-error-situation is+CEER: 0,0,0. A description associated with each number can be found in the tables given in the following sub-clauses and the relevant GSM specifications. The first parameter <locationID> serves to locate the other two parameters. Depending on the failure orrelease cause either <reason> or <ssRelease> are applicable, i.e. if <reason> ≠ 0, then <ssRelease> = 0.Vice versa, if <reason> = 0, then <ssRelease> may be ≠ 0. In addition to AT+CEER, the command ATS18 can be used to check especially the status of fax and data calls.

Syntax


Location ID as number code. Location IDs are listed in Section 3.4.1, Cause Location ID for the extended errorreport. Each ID is related with another table that contains a list of <reason>s or <ssRelease>s.

Reason for last call release as number code. The number codes are listed in several tables, sorted by differentcategories in the following subclauses. The tables can be found proceeding from the Location ID given in Sec-tion 3.4.1, Cause Location ID for the extended error report.

Release cause for last Supplementary Service call (listed in Section 3.4.9, GSM Release cause for Supplemen-tary Service Call)

Test Command

AT+CEER=?Response(s)


Exec Command

AT+CEERResponse(s)

+CEER: <locationID>, <reason>, <ssRelease>OKERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07

<locationID>(num)

<reason>(num)

<ssRelease>(num)



ExamplesEXAMPLE 1

EXAMPLE 2

The user attempts to activate call barring, but uses a wrong password.

3.4.1 Cause Location ID for the extended error report

ATD"01751223344"; A mobile originated call is rejected by the remote party. NO CARRIER Call setup is terminated with NO CARRIER. AT+CEER To check the cause, the caller enters AT+CEER. +CEER: 8,21,0 The Location ID 8 in Section 3.4.1 points to Section 3.4.7, where 21 =

"call rejected". 0 = "no error" refers to parameter <ssRelease> that isnot applicable.

OK

AT+clck=oi,1,"0000",3+CME ERROR: incorrect passwordAT+CEER+CEER: 35,0,38 The Location ID 35 in Section 3.4.1 points to Section 3.4.9, where 38 =

"negative PW check" may mean that a wrong password was tried for thefirst time. 0 = "no error" refers to parameter <reason> that is not appli-cable.

OK

ID Description0 no error (default)1 Proprietary L2 cause2 GSM cause for L3 radio resource sublayer (GSM 04.08 annex F)3 Proprietary cause for L3 radio resource sublayer4 GSM cause for L3 mobility management (GSM 04.08 annex G)5 Proprietary cause for L3 mobility management 6 GSM cause for L3 mobility management via MMR-SAP (GSM 04.08 annex G)8 GSM cause for L3 call control (GSM 04.08 10.5.4.11 and annex H)9 Proprietary cause for L3 call control 12 GSM cause for L3 SMS CP entity13 Proprietary cause for L3 SMS CP entity14 GSM cause for L3 SMS RL entity16 GSM cause for L3 SMS TL entity17 Proprietary cause for L3 SMS TL entity21 GSM cause for L3 call-related supplementary services 22 Proprietary cause for L3 call-related supplementary services33 Proprietary cause for supplementary services manager34 network cause for supplementary services (GSM 04.08 10.5.4.11 and annex H)35 supplementary services network error (GSM 04.80 3.6.6)48 GSM cause for GPRS mobility management (GSM 04.08 annex G.6)49 Proprietary cause for GPRS mobility management 50 GSM cause for session management (GSM 04.08 annex I)127 Proprietary cause for protocol module or other local cause128 supplementary services general problem (GSM 04.80 3.6.7)



3.4.2 Proprietary L2 cause

3.4.3 GSM release cause for L3 Radio Resource (RR)

129 supplementary services invoke problem (GSM 04.80 3.6.7)130 supplementary services result problem (GSM 04.80 3.6.7)131 supplementary services error problem (GSM 04.80 3.6.7)241 Proprietary cause for GPRS API 243 Proprietary cause for PPP/IP-stack

Number Description242 L2 decoding error243 L2 decoding error244 L2 decoding error245 L2 decoding error246 L2 decoding error247 L2 decoding error248 L2 decoding error249 no network response received, e.g. due to low signal quality250 L2 decoding error251 L2 decoding error252 L2 decoding error253 L2 decoding error

Number Description0 normal event1 abnormal release, unspecified2 abnormal release, channel unacceptable3 abnormal release, timer expired4 abnormal release, no activity on the radio path5 pre-emptive release8 handover impossible, timing advance out of range9 channel mode unacceptable10 frequency not implemented65 call already cleared95 semantically incorrect message96 invalid mandatory information97 message type non-existent or not implemented98 message type not compatible with protocol state100 conditional information element error

ID Description



3.4.4 Proprietary release cause for L3 Radio Resource (RR)

3.4.5 GSM release cause for Mobility Management (MM) or Session Management (SM)

101 no cell allocation available111 protocol error unspecified

Number Description1 RACCHs not answered2 RACCHs rejected3 access class of the SIM is barred by the network provider4 SABM failure5 radio link counter expiry or perform abnormal release6 confirm ABORT of the MM7 respond to DEACT REQ8 loss of coverage9 reestablishment not possible10 T3122 still running11 cell selection in progress12 responding to paging13 location area code has changed14 circuit switched not available

Number Descriptioncauses related to MS identification2 IMSI unknown in HLR3 illegal MS4 IMSI unknown in VLR5 IMEI not accepted6 illegal MEcause related to subscription options11 PLMN not allowed12 location area not allowed13 roaming not allowed in this location areacauses related to PLMN specific network failures and congestion17 network failure22 congestioncauses related to nature of request25 PDP context is deactivated because of a LLC or SNDCP failure

Number Description



3.4.6 Proprietary release cause for L3 Mobility Management (MM)

32 service option not supported33 requested service option not subscribed34 service option temporary out of order38 call cannot be identifiedcauses related to invalid messages95 semantically incorrect message96 invalid mandatory information97 message type non-existent or not implemented98 message not compatible with protocol state99 information element non-existent or not implemented100 conditional information element error101 messages not compatible with protocol state111 protocol error, unspecifiedcauses related to GPRS7 GPRS services not allowed8 GPRS services not allowed in combination with non-GPRS services9 MS identity cannot be identified by the network10 implicitly detached14 GPRS services not allowed in current PLMN16 MSC temporary unreachable

Number Description1 no SIM available8 no MM connection9 authentification failure11 MM performs detach17 registration failed and will be re-attempted in a short term18 CM connection establishment failed19 registration failed and will be re-attempted in a long term20 RR connection is released21 MS tries to register22 SPLMN is not available23 an MTC is in progress24 a PLMN scan is in progress25 the MM is detached, the MS is in MS class C GPRS only26 the maximum numbers of CM connections is exceeded27 the MM is not registered28 the MM state is incompatible

Number Description



3.4.7 GSM release cause for L3 Call Control (CC)

Number Descriptionnormal class1 unassigned (unallocated) number3 no route to destination6 channel unacceptable8 operator determined barring16 normal call clearing17 user busy18 no user responding19 user alerting, no answer21 call rejected22 number changed25 pre-emption26 non-selected user clearing27 destination out of order28 invalid number format (incomplete number)29 facility rejected30 response to STATUS ENQUIRY31 normal, unspecifiedresource unavailable class34 no circuit/channel available38 network out of order41 temporary failure42 switching equipment congestion43 access information discarded44 requested circuit/channel not available47 resource unavailable, unspecifiedservice or option not available class49 quality of service unavailable50 requested facility not subscribed55 incoming calls barred within the CUG57 bearer capability not authorized58 bearer capability not presently available63 service or option not available, unspecifiedservice or option not implemented65 bearer service not implemented68 ACM equal or greater than ACM max69 requested facility not implemented70 only restricted digital information bearer capability is available79 service or option not implemented, unspecifiedinvalid message (e.g. parameter out of range) class



3.4.8 Proprietary release cause for L3 Call Control (CC)

3.4.9 GSM Release cause for Supplementary Service Call

81 invalid transaction identifier value87 user not member of CUG88 incompatible destination91 invalid transit network selection95 semantically incorrect messageprotocol error (e.g. unknown message) class96 invalid mandatory information97 message type non-existant or not implemented98 message type not comaptible with protocol state99 information element non-existent or not implemented100 conditional information element error101 message not compatible with protocol102 recovery on timer expiry111 protocol error, unspecifiedinterworking class127 interworking, unspecified

Number Description2 service not available3 hold procedure not available4 temporary no service, previous procedure not yet finished7 mobile received a release (complete) message during a modify procedure (modify reject)10 number not included in FDN listnotifications300 called party barred incoming call

Number Description0 no error (default)1 unknown subscriber9 illegal subscriber10 bearer service not provisioned11 teleservice not provisioned12 illegal equipment13 call barred15 CUG reject16 illegal SS operation

Number Description



17 SS error status18 SS not available19 SS subscription violation20 SS incompatibility21 facility not supported27 absent subscriber29 short term denial30 long term denial34 system failure35 data missing36 unexpected data value37 PW registration failure38 negative PW check43 number of PW attempts violation71 unknown alphabet72 USSD busy126 max nums of MPTY calls exceeded127 resources not availablegeneral problem codes300 unrecognized component301 mistyped component302 badly structured componentinvoke problem codes303 duplicate invoke ID304 unrecognized operation305 mistyped parameter306 resource limitation307 initiating release308 unrecognized linked ID309 linked response unexpected310 unexpected linked operationreturn result problem codes311 unrecognize invoke ID312 return result unexpected313 mistyped parameterreturn error problem codes314 unrecognized invoke ID315 return error unexpected316 unrecognized error317 unexpected error318 mistyped parameter

Number Description



3.4.10 GSM release cause for Session Management (SM)

3.4.11 GSM cause for L3 Protocol module or other local cause

3.4.12 Proprietary release cause for GPRS API

3.4.13 Proprietary release cause for PPP/IP-Stack

Number Description102 recovery on timer expiry

Number Description10 unspecified RLP error14 unreliable data link or if the peer instance is not RLP15 SREJ timed out16 REMAP procedure timed out

Number Description0 regular deactivation of the call1 action temporary not allowed2 wrong connection type3 specified data service profile invalid4 PDP type or address is unknown5 FDN check was not successful; GPRS attach and PDP context activation blocked9 GPRS service not available255 undefined

Number Description0 regular call deactivation1 LCP stopped255 undefined

BGS3 AT Command Set 3.5 ATS18


3.5 ATS18 Extended call release report

ATS18 controls the presentation of extended call release reports for circuit switched fax and data calls. Extendedcall release reports related to voice calls are controlled via AT+CEER.

The call release report is presented in numeric format and shows as follows:

If enabled the message will be reported every time a fax or data call is released or fails to be established.

Syntax


An odd number enables the presentation of the extended call release report. Any even number disables thisfeature. 0(&F)...255

Location ID as number code, see also <locationID> of AT+CEER. Location IDs are listed in Section 3.4.1, Cause Location ID for the extended error report. Each ID is related toanother table that contains a list of <reason>s.

Reason for last call release as number code (see also <reason> of AT+CEER).<reason> numbers and the associated descriptions are listed in several tables, sorted by different categoriesat AT+CEER. The tables can be found proceeding from the Location IDs listed in Section 3.4.1, Cause LocationID for the extended error report.

+CAUSE: <locationID>:<reason>

Read Command

ATS18?Response(s)

<n>OK

Write Command

ATS18=<n>Response(s)

OKERROR


- + - + - - - - V.250

<n>(num)(&W)(&V)

<locationID>(num)

<reason>(num)



ExamplesEXAMPLE 1

EXAMPLE 2

ATS18=1 Enables the presentation of extended call release reports.OKATD03012345678 Now, a mobile originated data call fails.+CAUSE: 8:17 An extended error report is output, followed by the result code BUSY.BUSY The Location ID 8 stated in Section 3.4.1 points to Section 3.4.7, with 17

= "User busy".

ATS18=1 Enables the presentation of extended call release reports.OKATD03012345678 Now, a mobile originated data call is set up.CONNECT 9600/RLPHello,....+++ Call ends after remote party hung up.+CAUSE: 8:16 Normal call release is reported, followed by the result code NO CAR-

RIER.NO CARRIER The Location ID 8 stated in Section 3.4.1 points to Section 3.4.7, with 16

= "Normal call clearing".

BGS3 AT Command Set 3.6 AT+CPAS


3.6 AT+CPAS Mobile equipment activity status

The AT+CPAS execute command indicates the activity status of the ME.

Syntax


0 Ready3 Incoming call (ringing)4 Call in progress or call hold

Test Command

AT+CPAS=?Response(s)

+CPAS: (list of supported<pas>s)OK

Exec Command

AT+CPASResponse(s)

+CPAS: <pas>OK


- + + + + + - - GSM 07.07

<pas>(num)

BGS3 AT Command Set 3.7 AT+WS46


3.7 AT+WS46 Select wireless network

Syntax


12 GSM digital cellular

Test Command

AT+WS46=?Response(s)

+WS46: (list of supported<n>s)OK

Read Command

AT+WS46?Response(s)

<n>OK

Write Command

AT+WS46=[<n>]Response(s)



- + + + + + - - GSM 07.07

<n>(num)

BGS3 AT Command Set 4. Serial Interface Control Commands


4. Serial Interface Control Commands

The AT Commands described in this chapter allow the external application to determine various settings relatedto the BGS3's serial interface.

4.1 ATE Enable command echo

The ATE command determines whether or not the TA echoes characters received from TE during commandstate.

Syntax


[0] Echo mode off1(&F) Echo mode on

Note• In case of using the command without parameter, <value> is set to 0.

Exec Command

ATE[<value>]Response(s)

OK


- + + + + + - - V.250


BGS3 AT Command Set 4.2 AT&C


4.2 AT&C Set Data Carrier Detect (DCD) Line mode

The AT&C command determines how the state of the DCD line (circuit 109) reflects the BGS3's internal activity.

Syntax


[0] DCD line shall always be on. 1(&F) DCD line shall be on only when data carrier signal is present. 2 DCD line shall be on when one or more Internet services defined on the related

serial channel are in state "Connecting" or "Up" as described below. For detailson the various service states refer to AT^SISI, parameter <srvState> orAT^SISO, parameter <srvState>.• SOCKET, transparent TCP, HTTP,SMTP, POP3: DCD shall be on when

<srvState>="Connnecting" or "Up"• FTP: DCD shall be on when data channel is connected, i.e.

<srvState>="Up"

Exec Command

AT&C[<value>]Response(s)

OK


- + - + + + - - V.250


BGS3 AT Command Set 4.3 AT&D


4.3 AT&D Set Data Terminal Ready (DTR) line mode

AT&D determines how the ME responds if the DTR line is changed from ON to OFF state during data connection(CSD or PPP or active Internet service opened with AT^SIST).

Syntax


[0] ME ignores status of the DTR line.1 ON->OFF on DTR: Change to command mode while retaining the data con-

nection.2(&F) ON->OFF on DTR: Disconnect the data connection (only for CSD and PPP)

and change to command mode. For internet service the behaviour is likeAT&D1. During OFF state of the DTR line auto-answer is disabled.

Exec Command

AT&D[<value>]Response(s)

OK


- + ± + + + - - V.250


BGS3 AT Command Set 4.4 AT&S


4.4 AT&S Set Data Set Ready (DSR) line mode

AT&S determines how the ME sets the DSR line depending on its communication state.

Syntax


[0](&F) DSR line is always ON1 ME in command mode: DSR is OFF.

ME in data mode: DSR is ON.

Exec Command

AT&S[<value>]Response(s)

OK


- + - + + + - - V.250


BGS3 AT Command Set 4.5 AT\Q


4.5 AT\Q Flow control

Syntax


[0](&F) Disable flow control1 XON/XOFF software flow control2 Only CTS by DCE (TA)3 RTS/CTS hardware flow control

Recommended for the following procedures: incoming or outgoing data calls,fax calls, MUX mode.Often, the initialization routine of Fax programs includes enabling RTS/CTShandshake, eliminating the need to issue AT\Q3 once again.

Notes• When using XON/XOFF flow control (AT\Q1) in online mode, +++ should not be used while the data trans-

mission is paused with XOFF. Before entering the command mode with +++ the paused transmission shouldbe resumed using the XON character.

• For compatibility reasons, the AT\Q command can be used in Multiplex mode, though the settings will nottake effect. However, be aware that whenever you use the AT\Q write command in Multiplex mode and thensave the current configuration to the user profile with AT&W, the changed AT\Q setting will become active afterrestart.

• AT+IFC configures flow control separately for each data direction, while AT\Q applies to both directions. Both commands influence each other, i.e. settings made with AT\Q apply to AT+IFC and, vice versa, AT+IFCchanges the AT\Q setting.

Exec Command

AT\Q[<n>]Response(s)

OKIf RTS/CTS flow control is not supported by interface and <n> is 2 or 3:ERROR


- + + ± ± ± - -

<n>(num)(&W)(&V)

BGS3 AT Command Set 4.6 AT+IFC


4.6 AT+IFC Flow Control

AT+IFC controls the flow control mode used by the BGS3 separately for each data direction (send and receive).In contrast to this, flow control settings made with AT\Q are identical for both directions.

AT+IFC and AT\Q are designed to configure the TA (i.e. BGS3). The TE must, of course, also be configured.When programming the TE bear in mind that the flow control mode set on the TA must be compliant with the flowcontrol method set on the TE. Please refer notes below.

Syntax


Specifies the method used by the TA when sending data to the TE. [0](&F) none1 XON/XOFF

Local setting on the TA. Terminates flow control in the TA and thus, causes theTA to stop sending data to the remote TA.

2 RTS lineLocal setting on the TA.

3 XON/XOFFUsed to evaluate flow control in the TA. If the data flow from the TA requiresthat the transmission be stopped, the TE inserts the XON/OFF control charac-ters into the data stream to be sent, over the air, to the opposite TE. It is theresponsibility of the receiving TE to recognize and filter out from the datastream the XON/OFF control characters. So, both TEs must have XON/OFFflow control enabled.Also, the receiving TA must be configured to use software flow control. Thismeans, that if the sending TA is configured for AT+IFC=3,x the receiving TAmust be set to AT+IFC=y,1. In addition, XON/OFF flow control must be

Test Command

AT+IFC=?Response(s)

+IFC: (list of supported <TEflowcontrol>s), (list of supported <TAflowcontrol>s)OK

Read Command

AT+IFC?Response(s)

+IFC: <TEflowcontrol>, <TAflowcontrol>OK

Write Command

AT+IFC=<TEflowcontrol>, <TAflowcontrol>Response(s)



- + + ± ± ± - - V.250

<TEflowcontrol>(num)(&W)

BGS3 AT Command Set 4.6 AT+IFC


enabled on either TE.If the TAs and TEs on both sides are properly configured, the transmission ofthe XON/OFF control characters will instantly stop the data flow. So, value "3"has an immediate effect on the over-the-air connection between both TEs.

Specifies the method used by the TA when receiving data from the TE.[0](&F) none1 XON/XOFF2 CTS line

Notes• If using XON/XOFF flow control (AT+IFC=1,x or AT+IFC=3,x) in data mode, +++ should not be used while

the data transmission is paused with XOFF. Before entering the command mode with +++ the paused trans-mission should be resumed using the XON character.

• For compatibility reasons, the AT+IFC command can be used in Multiplex mode, though the settings will nottake effect. However, be aware that whenever you use the AT+IFC write command in Multiplex mode andthen save the current configuration to the user profile with AT&W, the changed AT+IFC setting will becomeactive after restart if autobaud mode is disabled (for details refer AT+IPR).

• AT+IFC and AT\Q usage influence each other, i.e. settings made with AT\Q apply to AT+IFC and, vice versa,AT+IFC changes the AT\Q setting.

• Bear in mind that when you set a flow control method for one direction on the TA (with AT+IFC) the TE mustalso be configured accordingly.

• The values "1" and "2" have only local effect for the connection between TA and TE. Value "3" has an imme-diate effect on the over-the-air connection.

• XON/OFF flow control is not recommended for transferring binary files or using the GSM character set (referAT+CSCS). In this case the data stream might contain characters equal to the values typically used as XON/OFF control characters, i.e. values 11 (hex) resp. 17 (dec) and 13 (hex) resp. 19 (dec).

<TAflowcontrol>(num)(&W)

BGS3 AT Command Set 4.7 AT+ILRR


4.7 AT+ILRR Set TE-TA local rate reporting

The command AT+ILRR controls whether or not the intermediate result code "+ILRR" is transmitted from the TAto the TE while a connection is being set up. The result code indicates the local rate. It is issued before the finalresult code of the connection, e.g. CONNECT, is transmitted to the TE.

Syntax

Intermediate Result Code+ILRR: <rate>

Indicates local port rate setting upon connection setup.


0(&F) Disables reporting of local port rate 1 Enables reporting of local port rate

Port rate setting upon connection setup (bps)0 Autobauding (see Section 4.8.1, Autobauding). Not supported on ASC1. 300600120024004800960014400

Test Command

AT+ILRR=?Response(s)

+ILRR: (list of supported <value>s) OK

Read Command

AT+ILRR?Response(s)

+ILRR: <value>OK

Write Command

AT+ILRR=<value>Response(s)



+ + - + - - - - V.250


<rate>(num)

BGS3 AT Command Set 4.7 AT+ILRR


19200288003840057600115200230400460800

BGS3 AT Command Set 4.8 AT+IPR


4.8 AT+IPR Bit Rate

AT+IPR allows to query and set the bit rate of the BGS3's asynchronous serial interfaces (UART). The test command returns the values of supported automatically detectable bit rates and the values of the sup-ported fixed bit rates. The read command returns the the currently set <rate> value. The write command specifies the bit rate to be used for the interface. Delivery bit rate value (<rate>) is115200bps on ASC0 and 115200bps on ASC1. This setting will not be restored with AT&F.

If using a fixed bit rate, make sure that both BGS3 and TA are configured to the same rate. A selected fixed bitrate takes effect after the write command returns OK and is stored in non-volatile memory. It is not recommendedto set bit rates lower than 9600 bps in order to avoid timing problems (see Section 1.5, Communication betweenCustomer Application and BGS3 for details about timing). In case of autobauding mode (AT+IPR=0) the detected TA bit rate will not be saved and, therefore, needs to beresynchronized after any restart of the ME (for details refer Section 4.8.1, Autobauding). If autobauding is acti-vated, the TA will automatically recognize bit rate currently used by the TE. In Multiplex mode the write command will not change the bit rate currently used, but the new bit rate will be storedand becomes active, when the module is restarted. The current setting of AT+IPR will be preserved when you download firmware (i.e. a firmware update does notrestore the factory setting) or in the event of power failure.

Syntax


bit rate per second (bps)0 Activates autobauding. Not supported on ASC1. See Section 4.8.1, Autobaud-

ing for further details. 3006001200

Test Command

AT+IPR=?Response(s)

+IPR: (list of supported auto-detectable <rate>s) , (list of supported fixed-only <rate>s)OK

Read Command

AT+IPR?Response(s)

+IPR: <rate>OK

Write Command

AT+IPR=<rate>Response(s)



- + ± ± ± ± - - V.250

<rate>(num)(&V)



2400480096001440019200288003840057600115200230400460800921600

Note• Generally, AT+IPR should be used as a standalone command as specified in Section 1.4.2, Concatenating

AT Commands. If nevertheless combinations with other commands on the same command line cannot beavoided, there are several constraints to be considered: - Avoid combinations with the AT commands listed in Section 1.4.2, Concatenating AT Commands.- Keep in mind that there shall be a minimum pause between two AT commands as specified in Section 1.5,

Communication between Customer Application and BGS3. - If local echo is active (ATE1) and AT+IPR=x is entered with other commands you may encounter the fol-

lowing problem: If switching to the new bit rate takes effect while a response is being transmitted, the lastbytes may be sent with the new bit rate and thus, not properly transmitted. The following commands willbe correctly sent at the new bit rate.

4.8.1 Autobauding

To take advantage of autobaud mode specific attention must be paid to the following requirements: • Synchronization between TE and TA:

Ensure that TE and TA are correctly synchronized and the bit rate used by the TE is detected by the TA. Toallow the bit rate to be synchronized simply use an "AT" or "at" string. This is necessary when you start upthe ME while autobauding is enabled. It is recommended to wait 3 to 5 seconds before sending the first ATcharacter. Otherwise undefined characters might be returned.

• Restrictions on autobauding operation:- If autobaud mode is enabled, then autobauding does not take effect immediately after the write command

AT+IPR=0 ends. Instead the old bit rate remains active. The autobaud mode is activated with the nextrestart of the TA. This is indicated by any following AT+IPR read command which still returns the old bitrate until the next restart. Before you activate autobauding switch on the local echo with ATE1. To verify if autobauding has becomeeffective after restart first send only the characters "AT" or "at" and check that they are echoed within100ms. In some cases you may need to repeat this several times, until both characters are properly ech-oed within 100ms. Please note that after the successful synchronization between TE and TA the autobauding mechanism ofthe TA is deactivated until next restart. So, while autobauding is enabled you will need to restart the TAeach time after changing the bit rate of the TE.

- The TA cannot distinguish between 1 and 2 stop bits. Therefore, 1 stop bit will be used by the TA. - The command A/ cannot be used.- Only the first "AT" or "at" after restart of the module can be detected (neither "At" nor "aT"). This means

that all the AT commands have to use the same bit rate and frame type. - The second serial interface ASC1 does not support autobauding.



- URCs that may be issued before the ME detects a new bit rate (by receiving the first AT character) will besent at the previously detected bit rate or, after ME restart, at 115200 bps.

• Autobauding and bit rate after restart:Unless the bit rate is determined, the following constraints apply: - An incoming CSD call or a network initiated GPRS request cannot be accepted. This must be taken into

account when autobauding and autoanswer mode (ATS0 ≠ 0) are enabled at the same time, escpeciallyif SIM PIN 1 authentication is done automatically and the setting ATS0 ≠ 0 is stored to the user profile withAT&W.

- Until the bit rate is found, URCs generated after restart will be output at 115200 bps. This applies only touser defined URCs, such as "+CREG", "CCWA", "^SCKS" etc. The URCs "^SYSSTART", "^SYSSTARTCHARGE-ONLY MODE" will not be indicated when autobauding is enabled.

Note: To avoid any problems caused by undetermined bit rates in the direction from TA to TE we stronglyrecommend to configure a fixed bit rate rather than autobauding.

• Autobauding and multiplex mode:If autobauding is active you cannot switch to multiplex mode (see AT+CMUX).

BGS3 AT Command Set 4.9 AT+CMUX


4.9 AT+CMUX Multiplex Mode

Multiplex mode according to GSM 07.10 and 3G TS 27.010 ([5]) enables the use of virtual channels set up overone single serial interface. Every channel is used as an independent serial link. This way, up to three simulta-neous AT command sessions can be handled at a time. For example, the first channel can be used to send orreceive data, while two channels are available to control the module with AT commands or to establish a dedi-cated channel to receive Unsolicited Result Codes (URC), e.g. "+CIEV:" or "RING".

BGS3 incorporates an internal multiplexer and thus integrates all the functions needed to implement full-featuredmultiplex solutions. For the application on top, customers have the flexibility to create their own multiplex pro-grams conforming to the multiplexer protocol. To help system integrators save the time and expense of designingmultiplexer applications, Cinterion Wireless Modules GmbH offers WinMUX, a ready-to-use multiplex driver forWindows XP and Windows Vista. Another approach is to develop customized solutions based on the sources ofthe WinMUX driver.Refer to [4] which provides a detailed description of the multiplex architecture and step-by-step instructions ofhow to install and configure the multiplex mode. The WinMUX driver and its source files can be supplied onrequest. Please contact your local distributor to obtain the latest installation software and user's guide.

All information provided in this section applies only to the ASC0 interface. The second interface ASC1 does notsupport Multiplex mode and is not accessible when the multiplexer is started on ASC0. See also Section 1.9,Auxiliary Serial Interface for details on ASC1. AT+CMUX write command is used to enter Multiplex mode. Setup of the logical channels is initiated by the TE,i.e. the TE acts as initiator. This means that the TE shall ensure that logical channels are established before anyfurther actions on the channels can be started. There is a timeout of five seconds, if the multiplexer protocol isenabled but no multiplexer control channel is established. Afterwards BGS3 returns to AT command mode. The parameter maximum frame size (N1) according to GSM 07.10 is implemented as 98 bytes by default. Allother parameters are not available. Refer to [4] for further details regarding frame size.

SyntaxTest Command

AT+CMUX=?Response(s)

+CMUX: (list of supported<mode>s)OK

Read Command

AT+CMUX?Response(s)

+CMUX: <mode>OKERROR+CME ERROR: <err>

Write Command

AT+CMUX=<mode>Response(s)



- + - - - - - + GSM 07.07, GSM 07.10, 3GPP TS 27.010




Enable Multiplex mode.0 Basic option

4.9.1 Restrictions on Multiplex mode

In multiplex mode, data and fax calls can only be set up on logical channel 1. Due to this restriction, AT com-mands have a different behavior on channels 2+3 compared to channel 1. Several commands are not available,others return different responses. This section summarizes the concerned commands. For general rules andrestrictions to be considered in Multiplex mode please refer to [4].

Table 4.1: Availability of AT Commands on Virtual Channels

1) The ME supports the registers S0 - S29. You can change S0,S3,S4,S5,S6,S7,S8,S10 and S18 using the related ATSncommands (see starting from ATS0). The other registers are read-only and for internal use only!

2) The applicability of the +++escape sequence depends on the customer's external application based on the MulitplexerProtocol. Recommendations for implementing an appropriate modem status command (MSC) are provided in [4], Section"Escape Sequence".

3) PDP contexts can be defined on any channel, but are visible and usable only on the channel on which they are defined(thus it is not possible to define a context on channel 2 and activate it on channel 3). GPRS connections can be estab-lished on two channels at a time.

Table 4.2: Summary of AT commands with Different Behavior in Multiplex Mode

<mode>(num)

Command Behavior on channel 1 Behavior on channel 2+3+++ not usable, but see note 2) not usable, but see note 2)

AT+CBST as described not usableAT+CRLP as described not usableAT+CG... (GPRS commands) as described see note 3)

AT+F... (Fax commands) as described not usableAT&S as described not usableATA as described no Data CallsATD as described no Data CallsATDI as described not usableATL as described not usableATM as described not usableATO as described not usableATS6 1) as described not usableATS7 1) as described not usableATS8 1) as described not usableATS10 1) as described not usableATS18 1) as described not usable

Command DescriptionAT\Q It is recommended to use hardware flow control (AT\Q3). XON/XOFF flow control

(AT\Q1) is not supported in Multiplex mode.See note regarding AT\Qn settings stored with AT&W if Multiplex mode is active.

AT&V Different default configurations on channels 1, 2 and 3.



AT&W Different user profiles can be stored on each channel.AT+IPR In Multiplex mode, the write command AT+IPR=<rate> will not change the bit rate

currently used, but the new bit rate will be stored and becomes active, when the module is restarted.

AT+IPR=0 Multiplex mode cannot be activated while autobauding is enabled. AT+CMEE Presentation mode can be separately configured for each channel. AT+CNMA If Multiplex mode is activated the +CNMI parameter will be set to zero on all chan-

nels, if one channel fails to acknowledge an incoming message within the required time.

AT+CNMI Phase 2+ parameters can only be used on one channel. The parameter for <mt> and <ds> on the other channels have to be set to zero. If either a SM or a Status Report is not acknowledged, all +CNMI parameter will be set to zero on all chan-nels.

AT+CFUN If the ME is in Multiplexer mode, it is not recommended to activate SLEEP mode with AT+CFUN=<fun>. The best approach to properly control SLEEP mode in this case is to issue the PSC messages described in [4], Section "Power saving control (PSC)".

AT+CPMS Parameter <mem3> will be the same on all instances, but the settings of <mem1> and <mem2> may vary on each instance.

AT^SSDA If one instance is set to <da>=1 and <mt>=1, then all other instances must be con-figured for <mt>=0.

Command Description

BGS3 AT Command Set 5. Security Commands


5. Security Commands

The AT Commands described in this chapter allow the external application to determine various security relatedsettings.

5.1 AT+CPIN PIN Authentication

The AT+CPIN write command can be used to enter one of the passwords listed below. The read command canbe used to check whether or not the ME is waiting for a password, or which type of password is required.

This may be for example the SIM PIN1 to register to the GSM network, or the SIM PUK1 to replace a disabledSIM PIN1 with a new one, or the PH-SIM PIN if the client has taken precautions for preventing damage in theevent of loss or theft etc. If requested by the ME AT+CPIN may also be used for the SIM PIN2 or SIM PUK2.

If no PIN1 request is pending (for example if PIN1 authentication has been done and the same PIN1 is enteredagain) BGS3 responds "+CME ERROR: operation not allowed"; no further action is required.

Each time a password is entered with AT+CPIN the module starts reading data from the SIM. The duration ofreading varies with the SIM card. This may cause a delay of several seconds before all commands which needaccess to SIM data are effective. See Section 20.1, Restricted access to SIM data after SIM PIN authenticationfor further detail.

SyntaxTest Command

AT+CPIN=?Response(s)

OK

Read Command

AT+CPIN?Response(s)

+CPIN: <code>OK ERROR +CME ERROR: <err>

Write Command

AT+CPIN=<pin>[, <new pin>]Response(s)



- + + + + + - - GSM 07.07

BGS3 AT Command Set 5.1 AT+CPIN



Password (string type), usually SIM PIN1.If the requested password was a PUK, such as SIM PUK1 or PH-FSIM PUK or another password, then <pin>must be followed by <new pin>.

If the requested code was a PUK: specify a new password or restore the former disabled password. See Section5.1.1, What to do if PIN or password authentication fails? for more information about when you may need toenter the PUK.

SIM PIN authentication READY PIN has already been entered. No further entry needed.SIM PIN ME is waiting for SIM PIN1.SIM PUK ME is waiting for SIM PUK1 if PIN1 was disabled after three failed attempts to

enter PIN1.SIM PIN2 ME is waiting for PIN2. This is only applicable when an attempt to access a

PIN2 related feature was acknowledged with +CME ERROR: 17 ("SIM PIN2required"), for example when the client attempts to edit the FD phonebook). Inthis case the read command AT+CPIN? also prompts for SIM PIN2. Normally,the AT+CPIN2 command is intended for SIM PIN2.

SIM PUK2 ME is waiting for PUK2 to unblock a disabled PIN2. As above, this is only nec-essary when the preceding command was acknowledged with +CME ERROR:18 ("SIM PUK2 required") and only if the read command AT+CPIN? alsoprompts for SIM PUK2. Normally, the AT+CPIN2 command is intended for SIMPUK2.

Phone security locks set by client or factoryPH-SIM PIN ME is waiting for phone-to-SIM card password if "PS" lock is active and the cli-

ent inserts other SIM card than the one used for the lock. ("PS" lock is alsoreferred to as phone or antitheft lock).

PH-SIM PUK ME is waiting for Master Phone Code, if the above "PS" lock password wasincorrectly entered three times.

PH-FSIM PIN ME is waiting for phone-to-very-first-SIM card. Necessary when "PF" lock wasset. When powered up the first time, ME locks itself to the first SIM card put intothe card holder. As a result, operation of the mobile is restricted to this one SIMcard (unless the PH-FSIM PUK is used as described below).

PH-FSIM PUK ME is waiting for phone-to-very-first-SIM card unblocking password to begiven. Necessary when "PF" lock is active and other than first SIM card isinserted.

PH-NET PUK ME is waiting for network personalisation unblocking passwordPH-NS PIN ME is waiting for network subset personalisation passwordPH-NS PUK ME is waiting for network subset unblocking passwordPH-SP PIN ME is waiting for service provider personalisation passwordPH-SP PUK ME is waiting for service provider personalisation unblocking passwordPH-C PIN ME is waiting for corporate personalisation passwordPH-C PUK ME is waiting for corprorate personalisation un-blocking password

<pin>(str)

<new pin>(text)

<code>(text)



Notes• Successful PIN authentication only confirms that the entered PIN was recognized and correct. The output of

the result code OK does not necessarily imply that the mobile is registered to the desired network.Typical example: PIN was entered and accepted with OK, but the ME fails to register to the network. This maybe due to missing network coverage, denied network access with currently used SIM card, no valid roamingagreement between home network and currently available operators etc.BGS3 offers various options to verify the present status of network registration: For example, the AT+COPScommand indicates the currently used network. With AT+CREG you can also check the current status and acti-vate an unsolicited result code which appears whenever the status of the network registration changes (e.g.when the ME is powered up, or when the network cell changes).

• <pin> and <new pin> can also be entered in quotation marks (e.g. "1234").• To check the number of remaining attempts to enter the passwords use the AT^SPIC command.• See AT+CPWD and AT^SPWD for information on passwords.• See AT+CLCK and AT^SLCK for information on lock types.

5.1.1 What to do if PIN or password authentication fails?

PIN1 / PUK1:After three failures to enter PIN 1, the SIM card is blocked (except for emergency calls). +CME ERROR: 12 willprompt the client to unblock the SIM card by entering the associated PUK (= PIN Unblocking Key / PersonalUnblocking Key). After ten failed attempts to enter the PUK, the SIM card will be invalidated and no longer oper-able (the device will respond with: +CME ERROR: 770, which stands for: SIM invalid - network reject). In sucha case, the card needs to be replaced. PIN1 consists of 4 to 8 digits, PUK1 is an 8-digit code only.To unblock a disabled PIN1 you have two options: • You can enter AT+CPIN=PUK1,new PIN1.• You can use the ATD command followed by the GSM code **05*PUK*newPIN*newPIN#;.

PIN2 / PUK2: PIN2 prevents unauthorized access to the features listed in AT+CPIN2. The handling of PIN2 varies with the pro-vider. PIN2 may either be a specific code supplied along with an associated PUK2, or a default code such as0000. In either case, the client is advised to replace it with an individual code. Incorrect input of PUK2 will per-manently block the additional features subject to PIN2 authentification, but usually has no effect on PIN1. PIN2consists of 4 digits, PUK2 is an 8-digit code only.To unblock a disabled PIN2 you have two options: • You can enter AT+CPIN2=PUK2,new PIN2.• You can use the ATD command followed by the GSM code **052*PUK2*newPIN2*newPIN2#;.

Phone lock: If the mobile was locked to a specific SIM card (= "PS" lock or phone lock), the PUK that came with the SIM cardcannot be used to remove the lock. After three failed attempts to enter the correct password, ME returns +CPIN:PH-SIM PUK (= response to read command AT+CPIN?), i.e. it is now waiting for the Master Phone Code. Thisis an 8-digit device code associated to the IMEI number of the mobile which can only by obtained from the man-ufacturer or provider. When needed, contact Cinterion Wireless Modules GmbH and request the Master PhoneCode of the specific module.There are two ways to enter the Master Phone code: • You can enter AT+CPIN=Master Phone Code• You can use the ATD command followed by the GSM code *#0003*Master Phone Code#;.Usually, the Master Phone Code will be supplied by mail or e-mail. If the received number is enclosed in the *#codes typically used for the ATD option, it is important to crop the preceding *#0003* characters and theappended #. Example: You may be given the string *#0003*12345678#. When prompted for the PH-SIM PUK simply enter12345678.If incorrectly input, the Master Phone Code is governed by a specific timing algorithm: (n-1)*256 seconds (seetable below). The timing should be considered by system integrators when designing an individual MMI.



SIM locks: These are factory set locks, such as "PF", "PN", "PU", "PP", "PC". An 8-digit unlocking code is required to operatethe mobile with a different SIM card, or to lift the lock. The code can only be obtained from the provider.Failure to enter the password is subject to the same timing algorithm as the Master Phone Code (see Tableabove).

Call barring: Supported modes are "AO", "OI", "OX", "AI", "IR", "AB", "AG", "AC". If the call barring password is entered incor-rectly three times, the client will need to contact the service provider to obtain a new one.

Related sections: "+CME ERROR: <err>" values are specified at Section 2.12.1, CME/CMS Error Code Overview. For furtherinstructions and examples see AT+CLCK, AT^SLCK, AT+CPWD and AT^SPWD. For a complete list of Star-Hash codes please refer Section 20.2, Star-Hash (*#) Network Commands.

Number of failed attempts Time to wait before next input is allowed1st failed attempt No time to wait2nd failed attempt 4 seconds3rd failed attempt 3 * 256 seconds4th failed attempt 4 * 256 seconds5th failed attempt 5 * 256 seconds6th failed attempt and so forth 6 * 256 seconds and so forth

BGS3 AT Command Set 5.2 AT+CPIN2


5.2 AT+CPIN2 PIN2 Authentication

AT+CPIN2 controls network authentication of the BGS3. The read command returns an alphanumeric string indicating whether or not network authentication is required. The write command allows the BGS3 to store the entered password. This may be for example the SIM PIN2 tobenefit from the features listed below, or the SIM PUK2 to replace a disabled PIN2 with a new one. Note thatPIN2 can only be entered if PIN1 authentication was done. If the BGS3 is requesting SIM PUK2, use <pin> to enter the PUK2, followed by <new pin> to specify the newPIN2.

Syntax


Password (string type), usually SIM PIN2 or, if requested, SIM PUK2.

If the requested code was SIM PUK2: new password (PIN2).See Section 5.1.1, What to do if PIN or password authentication fails? for more information about when you mayneed to enter the PUK.

READY ME is not pending for any password.SIM PIN2 ME is waiting for SIM PIN2.

This <code> is returned only when PIN2 authentication has not yet been doneor has failed ("+CME ERROR: 17").

SIM PUK2 ME is waiting for SIM PUK2.This <code> is returned only when PIN2 authentication has failed and ME ispending for SIM PUK2 (i.e. "+CME ERROR: 18").

Test Command

AT+CPIN2=?Response(s)

OK

Read Command

AT+CPIN2?Response(s)

+CPIN2: <code>OKERROR+CME ERROR: <err>

Write Command

AT+CPIN2=<pin>[, <new pin>]Response(s)



+ + + + + + - - GSM 07.07

<pin>(str)

<new pin>(str)

<code>(text)

BGS3 AT Command Set 5.2 AT+CPIN2


Note• Functions accessible only after PIN2 authentication:

AT+CACM: Accumulated call meter (ACM) reset or queryAT+CAMM: Accumulated call meter maximum (ACMmax) set or queryAT+CLCK: Facility lock to "FD" (Fixed dialing phonebook)AT^SLCK: Facility lock to "FD" (Fixed dialing phonebook)AT+CPWD: Change "P2"passwordAT^SPWD: Change "P2"passwordAT+CPUC: Price per unit and currency tableAT+CPIN2: Enter SIM PIN2 or SIM PUK2 if requested.

For example, SIM PIN2 will be needed when you attempt to edit the "FD" phonebook and ME returns "+CMEERROR: 17" or "+CPIN: SIM PIN2".Once the required <pin> has been entered correctly, PIN2 authentication code changes to READY. After300s, a repetition of the authentication process is required (PIN2 authentication code changes from READYto SIM PIN2).

ExamplesEXAMPLE 1

Change PIN2

EXAMPLE 2

Unblock a disabled PIN2

EXAMPLE 3

Write into "FD" phonebook

AT+CPWD="P2","0000","8888" (where "0000" = old PIN2 and "8888" = new PIN2) OK

AT+CPIN2?+CPIN2: SIM PUK2 PIN2 has been disabled, PUK2 must be entered OK to define a new PIN2 AT+CPIN2=12345678,8888 where "12345678" is the PUK2, and "8888" the new

PIN2.

AT+CPBS="FD"OKAT+CPBW=2,"+493012345678",145,"Charly"+CME ERROR: 17 access denied due to missing PIN2 authentication AT+CPIN2=8888OKAT+CPBW=2,"+493012345678",145,"Charly"OK

BGS3 AT Command Set 5.3 AT^SPIC


5.3 AT^SPIC Display PIN counter

The AT^SPIC command can be used to find out whether the ME is waiting for a password and, if so, how manyattempts are left to enter the password.

The execute command returns the number of attempts still available for entering the currently required password,for example the PIN, PUK, PH-SIM PUK etc.

The read command AT^SPIC? indicates which password the number of attempts stated by the execute com-mand actually refers to. Also, the write command may be used to query the counter for a specific password: Itindicates the number of attempts still available for entering the password identified by <facility>, for examplethe PIN, PIN2, PH-SIM PIN etc.

To check whether or not you need to enter a password use the read commands AT+CPIN?, AT+CPIN2? andAT^SPIC?. If the response to AT+CPIN? is "READY" the counter of the execute command AT^SPIC relates toPIN2. See last example. If the responses to AT+CPIN? and AT+CPIN2? both read "READY", no password iscurrently required, and the referrer of the execute command AT^SPIC is explicitly undefined.

Syntax


Number of attempts left to enter the currently required password. This number will be counted down after eachfailure.

Test Command

AT^SPIC=?Response(s)

OK

Read Command

AT^SPIC?Response(s)

^SPIC: <code>OK

Exec Command

AT^SPICResponse(s)

^SPIC: <counter>OK

Write Command

AT^SPIC=<facility>Response(s)

^SPIC: <counter>OKERROR+CME ERROR: <err>


- + + + + + - -

<counter>(num)



Password for which the corresponding PIN counter is to be displayed.“SC“ SIM PIN or SIM PUK. If the SIM PIN has been deactivated after three failed

attempts, the counter for SIM PUK will be returned instead. “PS“ "Phone code" or "device code" (cf. AT+CLCK and AT+CPWD). If incorrectly

entered three times, the Master Phone Code is required to lift the lock and thenumber of remaining attempts for the master phonecode will be returned.

“P2“ SIM PIN2 or SIM PUK2. If the SIM PIN2 has been deactivated after three failedattempts, the counter for SIM PUK2 will be returned instead.

“PN“ Network Personalisation

Identification of the currently required password.SIM PIN ME is waiting for SIM PIN1.SIM PUK ME is waiting for SIM PUK1 if PIN1 was disabled after three failed attempts to

enter PIN1.SIM PIN2 ME is waiting for PIN2, when the attempt to access PIN2 requiring features was

acknowledged with "+CME ERROR: 17" (e.g. if the user attempts to edit theFD phonebook).

SIM PUK2 ME is waiting for PUK2 to unblock a disabled PIN2. Necessary if precedingcommand was acknowledged with "+CME ERROR: 18".

PH-SIM PIN ME is waiting for phone-to-SIM card password if ''PS'' lock is active and userinserts other SIM card than the one used for the lock. (''PS'' lock is also referredto as phone or antitheft lock).

PH-SIM PUK ME is waiting for Master Phone Code, if the above ''PS'' lock password wasincorrectly entered three times.

PH-NET PUK ME is waiting for network personalisation unblocking password

Notes• Whenever the required password changes, <counter> changes to reflect that change. Please refer to the

examples below.• For passwords associated to the phone lock (''PS'' lock set by user or factory) or other factory set locks, such

as ''PF'', ''PN'', ''PU'', ''PP'', ''PC'' the number of attempts is subject to a timing algorithm explained inAT+CPIN. If these passwords are incorrectly entered the counter first returns 3, 2 and 1 remaining attempt(s),but then gives the total number of attempts which amounts to 63 (see example below).

• See also Chapters AT+CLCK, AT+CPIN, AT+CPIN2, AT+CPWD, AT^SLCK for further information on locks andpasswords.

ExamplesEXAMPLE 1

The user fails to provide a correct SIM PIN three times. The counter decreases each time. After the counterreaches zero, the SIM PUK is required. After each failure to enter a correct SIM PUK, the counter decreases.

<facility>(str)

<code>(text)

at+cpin?+CPIN: SIM PINOK Currently required password is PIN1.at^spic^SPIC: 3OK 3 attempts left.at+cpin=9999+CME ERROR: incorrect password



EXAMPLE 2

Though a mobile is locked to a specific SIM card (phone lock), the user attempts to operate it with anotherSIM card. The user correctly enters the SIM PIN of the SIM card currently inserted, but then fails to give the''PS'' lock password (PH-SIM PUK):

at^spic^SPIC: 2 2 attempts left.OKat+cpin=9999+CME ERROR: incorrect passwordOKat^spic^SPIC: 1 1 attempt left.OKat+cpin=9999+CME ERROR: incorrect passwordat+cpin?+CPIN: SIM PUK OK Now required password is PUK 1.at^spic^SPIC: 10OK 10 attempts left for PUK 1.at+cpin=01234567,1234+CME ERROR: incorrect passwordat^spic^SPIC: 9OK 9 attempts left for PUK 1.

at+cpin=9999OKat+cpin?+CPIN: PH-SIM PIN ME is waiting for the phone lock password.OKat^spic^SPIC: 3 3 attempts left.OKat+cpin=4711+CME ERROR: incorrect passwordat^spic?^SPIC: 2 2 attempts left.OKat+cpin=4712+CME ERROR: incorrect passwordat^spic^SPIC: 1 1 attempt left.OKat^spic?^SPIC: PH-SIM PIN Displayed counter refers to phone lock password.OK

at+cpin=4713+CME ERROR: incorrect passwordat^spic^SPIC: 63OKat^spic?^SPIC: PH-SIM PUK Displayed counter refers to master phone code.OK



EXAMPLE 3

This example shows that after successful SIM PIN1 authentication the counter of the AT^SPIC execute andread command refers to SIM PIN2, i.e. it does not reflect the status of SIM PIN1. This may be a problem ifthe user enters a wrong PIN1 and is not aware that the number of attempts left to enter SIM PIN1 is counteddown.

To avoid conflicts we recommend to use the AT^SPIC read and write commands rather than the execute com-mand only. The read command clearly states the currently required password, and the write command maybe used to get the counter for a specific <facility>, in this case for example "P2".

at+cpin=4714+CME ERROR: incorrect passwordat^spic^SPIC: 63OK

+CREG: 0at+cpin=1234OK+CREG: 2

+CREG: 1 The mobile ist properly registered to the network.at+cpin?+CPIN: READY The AT+CPIN? read command confirms that SIM

PIN1 authentication was successful.at^spic^SPIC: 3 As SIM PIN1 authentication was successful, the

counter relates to SIM PIN2 and correctly indicatesthat the user has 3 attempts to enter SIM PIN2.

OKAT^SPIC? Likewise, the read command notifies that the ME is

waiting for SIM PIN2.^SPIC: SIM PIN2OKat+clck="SC",0,456789 First attempt to enter a wrong SIM PIN1.+CME ERROR: incorrect passwordat^spic^SPIC: 3 SIM PIN1 authentication is still valid, and the counter

relates to SIM PIN2.at+clck="SC",0,456789 Second attempt to enter a wrong SIM PIN1.+CME ERROR: incorrect passwordat^spic^SPIC: 3 SIM PIN1 authentication is still valid, and the counter

relates to SIM PIN2.at+clck="SC",0,456789 Third attempt to enter a wrong SIM PIN1.+CME ERROR: incorrect password

+CREG: 0 SIM PIN1 authentication is no longer valid.at^spic^SPIC: 10 This time, after the SIM PIN1 code has been dis-

abled, the counter indicates the status of SIM PIN1and notifies that 10 attempts are left to enter the SIMPUK.

BGS3 AT Command Set 5.4 AT+CLCK


5.4 AT+CLCK Facility lock

AT+CLCK can be used to lock, unlock or interrogate a network or ME <facility>. The command can beaborted when network facilities are being set or interrogated.

Syntax


Phone security locks set by client or factoryPrimarily intended for the client to take safety precautions, "SC", "PS" and "FD" can be configured individually."PS" may also be factory set. Parameter <class> is not applicable to security locks.See examples below for further details. “SC“ SIM (lock SIM cards). SIM requests password upon ME power-up and when

this lock command is issued.<password>: SIM PIN1.

“PS“ Phone locked to SIM card. ME requests password when other than current SIMcard is inserted."PS" lock is frequently referred to as "phone lock", or "device lock". Accord-ingly, the password may be called "phone code" or "device code". The "PS"password is not associated with the PUK of the SIM card. If incorrectly enteredthree times, the Master Phone Code is required to lift the lock. This is an 8-digitdevice code associated to the IMEI number of the mobile which can only beobtained from the manufacturer of the module. Once the Master Phone Codehas been acctepted, the mobile is operational, and the "PS" lock is no longeractive. If needed it must be set once again.

Test Command

AT+CLCK=?Response(s)

+CLCK:list of supported <facility>s OK

Write Command

AT+CLCK=<facility>, <mode>[, <password>][, <class>]Response(s)

if <mode> is not equal 2 and command successful: OKif <mode>= 2 and command successful: +CLCK: <status>[, <class>][+CLCK: <status>[, <class>]][+CLCK: ...]OKERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07, GSM 02.04, GSM 02.88, GSM 03.88, GSM 04.88

<facility>(str)



<password>: User defined password. It is needed before the first use of<facility> "PS" and, therefore, must first be specified with AT+CPWD orAT^SPWD, if it has not been predefined by factory settings. If set by factory (e.g.for a prepaid mobile), the password is supplied by the provider or operator.

“FD“ SIM fixed dialing memory: If the mobile is locked to "FD", only dial strings start-ing with numbers specified in the "FD" memory can be called. This applies alsoto the ATD*#code string required for Call Forwarding. The capacity of the "FD"phonebook is depending on the SIM card.<password>: SIM PIN 2.Any attempt to dial a number not specified in the "FD" phonebook will bedenied, causing the result code "+CME ERROR: call barred" to appear.

Handling of AT+CCFC if "FD" lock is set:The "FD" lock is effective only for AT+CCFC <mode> 3 (registering the CF des-tination number), i.e. registering the CF destination <number> requires theexact number be stored in the "FD" phonebook. All other functions provided byAT+CCFC are not restricted by the "FD" lock.

Factory defined SIM locks:Typical examples of factory set SIM locks are prepaid phones or network locks, used to restrict the operation ofa mobile to a specific provider or operator. The client should be aware that each of these lock types can only beunlocked if the associated password is available. For example, a mobile can be locked to accept only SIM cardsfrom the respective provider, or even one single SIM card. Once a different SIM card is inserted the ME willprompt the client to enter a specific code. This is not the PUK of the SIM card, but usually an 8-digit code whichneeds to be requested from the provider.The locks can only be set by the manufacturer and need to be agreed upon between the parties concerned, e.g.provider, operator, distributor etc. on the one side and the manufacturer on the other side. For details contactyour local dealer or Cinterion Wireless Modules GmbH.Parameter <class> is not applicable to SIM locks.<password> and instructions for unlocking must be obtained from the network provider. “PF“ lock Phone to the very First SIM card “PN“ Network Personalisation “PU“ Network subset Personalisation “PP“ Service Provider Personalisation “PC“ Corporate Personalisation

Supplementary Service Call Barring:Supplementary Service "Call Barring" allows to specify conditions under which calls will be disallowed by thenetwork.The availability of the Supplementary Services varies with the network. To benefit from call barring the client willneed to subscribe them, though a limited number of call barring types may be included in the basic tariff pack-age. When you attempt to set a <facility> or <class> which is not provisioned, not yet subscribed to, or not sup-ported by the module, the setting will not take effect regardless of the response returned. The responses in thesecases vary with the network (for example "OK", "+CME ERROR: operation not allowed", "+CME ERROR: oper-ation not supported" etc.). To make sure check the extended error response with AT+CEER and the lock statuswith <mode>=2. <password>: Network password supplied from the provider or operator. Usually there is one password whichapplies to all call barring options. For details contact your provider. “AO“ BAOC (Bar All Outgoing Calls) “OI“ BOIC (Bar Outgoing International Calls) “OX“ BOIC-exHC (Bar Outgoing International Calls except to Home Country) “AI“ BAIC (Bar All Incoming Calls) “IR“ BIC-Roam (Bar Incoming Calls when Roaming outside the home country) “AB“ All Barring services (applicable only for <mode>=0)



“AG“ All outGoing barring services (applicable only for <mode>=0) “AC“ All inComing barring services (applicable only for <mode>=0)

0 unlock 1 lock 2 query status

0 lock is inactive1 lock is active

Password string used to lock and to unlock a <facility>. Length and authority for passwords depend on the<facility> in question and are therefore listed in the section on parameter <facility>. Passwords can bemodified with AT+CPWD or AT^SPWD.

Integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication ser-vice or bearer service group as defined in "GSM 02.04". 1 voice2 class 2 ("data") comprises all those individual data classes between 16 and

128, that are supported both by the network and the MS. This means, a settingmade for class 2 applies to all individual data classes (if supported). In addition,you can assign a different setting to a specific class. For example, you can acti-vate Call Forwarding for all data classes, but deactivate it for data class 64,"dedicated packet access".

4 fax8 SMS16 data circuit sync32 data circuit async64 dedicated packet access128 dedicated PAD access1...[7]...255 combination of some of the above classes.

For example, the default setting 7 represents the sum of the integers 1, 2 and4 (voice, data and fax).The value 255 covers all classes. If parameter "class" is omitted, the default value 7 is used.

Notes• The AT+CLCK command offers the full range of <class> parameters according to the GSM specifications.

However, when you attempt to use a service option which is not provisioned or not yet subscribed to, the set-ting will not take effect regardless of the response returned.The responses in these cases vary with the network (for example "OK", "Operation not allowed", "Operationnot supported" etc.). To make sure check the extended error response with AT+CEER and the lock status with<mode>=2.

• The command has been implemented with the full set of <class> parameters according to GSM 07.07. Foractual applicability of a desired Call barring service to a specific service or service group (a specific <class>value) please consult table A.1 of GSM 02.04.

<mode>(num)

<status>(num)

<password>(str)

<class>(num)



• If an outgoing Fax or Data Call is rejected due to an active ''call barring'' supplementary service, the call willbe terminated with result code NO CARRIER.Under the same conditions, an outgoing Voice call will be terminated with result code NO DIALTONE.

• If an invalid <password> is entered several times in succession, a delay incremented after each failedattempt will increase the time to wait before the input of the <password> is accepted. To avoid blocking theserial interface the running AT+CLCK command is aborted after a short timeout and returns "+CME ERROR:unknown" (+CME ERROR: 100). If then the AT+CLCK command is issued once again execution is deniedwith "+CME ERROR: operation temporary not allowed" (+CME ERROR: 256). For details regarding the delaysee Section 5.1.1, What to do if PIN or password authentication fails?.

• If the user tries to set a lock although it is already active or, the other way round, tries to unlock an inactivelock, the response will be OK, but the <password> will not be checked or verified.

ExamplesEXAMPLE 1

Lock SIM card (<facility>= "SC")

To query the status of the SIM card lock:

AT+CLCK="SC",1,"9999" The "SC" parameter enables or disables the SIM PIN authentication(PIN 1) when you power up the GSM engine

OK SIM card locked. As a result, SIM PIN 1 must be entered to enable MEto register to the GSM network.

AT+CLCK="SC",0,"9999" Unlocks SIM card. OK When powered up, ME registers to the GSM network without requesting

SIM PIN1. Note: Depending on the services offered by the provider, this feature isnot supported by all SIM card types. If so, the command returns ERRORwhen you attempt to unlock the card.

AT+CLCK="SC",2 Query the status of SIM card lock. +CLCK: 1 SIM card is locked. SIM PIN1 must be entered to enable ME to register

to the GSM network. OK



EXAMPLE 2

Phone lock (<facility>="PS")

To lock the ME to the currently inserted SIM card, first specify a password for <facility> "PS":

Optionally, if "PS" password was defined before, change existing password:

Then, activate the Phone Lock:

To operate the mobile with the SIM card for which "PS" lock was activated:

To operate the mobile with other SIM card than the one used for the "PS" lock: Enter SIM PIN of present card, followed by "PS" lock password.

To deactivate the Phone Lock:

AT+CPIN? Make sure that PIN1 authentication is valid. OK

AT+CPWD="PS",,"1234" If "PS" lock has not been set before: enter new password. OK

AT+CPWD="PS","1234","3333" To replace existing "PS" password: Enter old and new password. OK

AT+CLCK="PS",1,"3333" Locks the mobile to the current SIM card. OK

AT+CPIN? +CPIN: SIM PIN OK AT+CPIN="9999" OK No additional password is required for operation (SIM recognized by

mobile).

AT+CPIN? +CPIN: SIM PIN OK AT+CPIN="1111" OK PIN authentication accepted. AT+CPIN? +CPIN: PH-SIM PIN "PS" lock password is required. OK AT+CPIN="3333" OK "PS" Lock password has been accepted. ME is fully operational now.

AT+CLCK="PS",0,"3333" Phone Lock password has to be provided again. OK Now the mobile can be used with any SIM card, without the need of the

phone lock password.

BGS3 AT Command Set 5.5 AT^SLCK


5.5 AT^SLCK Facility lock

AT^SLCK provides the "Facility lock" function as defined for the GSM 07.07 command AT+CLCK. The commandcan be used to lock, unlock or interrogate a network or ME <facility>.AT^SLCK is, in every respect, identical with AT+CLCK, except that the command syntax and response prefix is"^SLCK" instead of "+CLCK". For further details please refer to AT+CLCK.The command can be aborted when network facilities are being set or interrogated.

SyntaxTest Command

AT^SLCK=?Response(s)

^SLCK:list of supported <facility>s OK

Write Command

AT^SLCK=<facility>, <mode>[, <password>][, <class>]Response(s)

if <mode> is not equal 2 and command successful: OKif <mode>= 2 and command successful: ^SLCK: <status>, <class>[^SLCK: <status>, <class>][^SLCK: ...]OKIf error is related to ME functionality ERROR+CME ERROR: <err>



BGS3 AT Command Set 5.6 AT+CPWD


5.6 AT+CPWD Change Password

AT+CPWD allows to define a new password for a password protected <facility> lock function. Each passwordis a string of digits, the length of which varies with the associated <facility>. The test command returns a listof pairs which represent the available facilities and the maximum length of the associated password. See ATcommands AT+CLCK and AT^SLCK for more information on the various lock features.

Specifically the command can be used to • change PIN1 or PIN2, • change the password supplied from your provider for the "call barring" supplementary service, • set individual phone security passwords, • enter the unblocking key (Master Phone Code) to restore a disabled "PS" password. To delete a password use the following syntax: at+cpwd=<facility>,<old password>

Syntax


Phone security locks set by client or factory:Primarily intended for the client to take safety precautions, passwords "SC" (SIM PIN) and "P2" (SIM PIN2) areusually predefined, but can be configured individually. The password for lock facility "PS" may also be factoryset. “SC“ SIM PIN. SIM requests password upon ME power-up and when this lock com-

mand is issued.If incorrectly entered three times, the SIM PUK is required to perform authen-tication. Input of the SIM PUK password is possible only with AT commandAT+CPIN or ATD. For further details please refer to Section 5.1.1, What to doif PIN or password authentication fails?.<password length>: 4 to 8 digits.

Test Command

AT+CPWD=?Response(s)

+CPWD:list of supported (<facility>, <password length>) OK

Write Command

AT+CPWD=<facility>, <old password>[, <new password>]Response(s)

New password has been registered for the facility lock function. OKIf parameter <old password> was not correct:+CME ERROR: 16 (+CME ERROR: incorrect password)If the password for the selected <facility> has been invalidated due to too many failed attempts:+CME ERROR: ...If error is related to ME functionality: +CME ERROR: <err>


+ + + + + + - - GSM 07.07

<facility>(str)



“PS“ Phone locked to SIM card. ME requests password when other than current SIMcard is inserted."PS" lock is frequently referred to as "phone lock", or "device lock". Accord-ingly, the password may be called "phone code" or "device code". The "PS"password is not associated with the PUK of the SIM card. It must be definedbefore the first use of <facility> "PS" with AT+CLCK. <password length>: 4 digits. If incorrectly entered three times, the Master Phone Code is required to lift thelock. This Unblocking procedure is performed with AT+CPWD using the follow-ing parameters: <facility>="PS", <old password>= Master Phone Code(to be obtained from the module manufacturer), and <new password>= thenew phone code ("PS" password for lock facility), if desired.Mind that successful PIN authentication is a prerequisite for use of AT com-mand AT+CPWD. If Pin authentication has not been completed, input of theMaster Phone code password is possible only with AT command AT+CPIN orATD. For further detail please refer to Section 5.1.1, What to do if PIN or pass-word authentication fails?.Once the Master Phone Code has been acctepted, the mobile is operational,and the "PS" lock is no longer active. If needed it must be set once again withAT+CLCK.

“P2“ SIM PIN 2, e.g. required for authentication with facility lock "FD" (cf. AT+CLCK).If incorrectly entered three times, the SIM PUK 2 is required to perform authen-tication. Input of the SIM PUK 2 password is possible only with AT commandAT+CPIN2 or ATD. For further detail please refer to Section 5.1.1, What to doif PIN or password authentication fails?.<password length>: 4 to 8 digits.

Factory defined SIM locks:Typical examples of factory set SIM locks are prepaid phones or network locks, used to restrict the operation ofa mobile to a specific provider or operator. The client should be aware that each of these lock types can only beunlocked if the associated password is available. For example, a mobile can be locked to accept only SIM cardsfrom the respective provider, or even one single SIM card. Once a different SIM card is inserted the ME willprompt the client to enter a specific code. This is not the PUK of the SIM card, but usually an 8-digit code whichneeds to be requested from the provider.The locks can only be set by the manufacturer and need to be agreed upon between the parties concerned, e.g.provider, operator, distributor etc. on the one side and the manufacturer on the other side. For details contactyour local dealer or Cinterion Wireless Modules GmbH.“PF“ Lock Phone to the very First SIM card “PN“ Network Personalisation “PU“ Network subset Personalisation “PP“ Service Provider Personalisation “PC“ Corporate Personalisation

Supplementary Service Call Barring:Supplementary Service "Call Barring" allows to specify conditions under which calls will be disallowed by thenetwork.The availability of the Supplementary Services varies with the network. To benefit from call barring the client willneed to subscribe them, though a limited number of call barring types may be included in the basic tariff pack-age. <password length>: The Network Password needs to be supplied from the network provider or network oper-ator. Usually there is one 4 digit password which applies to all call barring options. For details contact your pro-vider. “AO“ BAOC (Bar All Outgoing Calls) “OI“ BOIC (Bar Outgoing International Calls) “OX“ BOIC-exHC (Bar Outgoing International Calls except to Home Country) “AI“ BAIC (Bar All Incoming Calls)



“IR“ BIC-Roam (Bar Incoming Calls when Roaming outside the home country) “AB“ All Barring services “AG“ All outGoing barring services“AC“ All inComing barring services

4...8 Length of password. The range of permitted length for a password depends onthe associated <facility>. It is available from the test command response,or in the description of parameter <facility>.

Password specified for the facility. Parameter <old password> can be ignored if no old password was allocated to the facility. Take into account that a password may have already been set by factory, or that the service is subject to a pass-word issued by the provider. See notes above or contact provider.

New password. Mandatory, if <old password> was an unblocking key (such as the Master Phone Code).

Note• When changing PIN2 (<facility>="P2") it is recommended to check the new state of PIN2 by using the

AT+CPIN2 command.

ExamplesEXAMPLE 1

To change PIN2

EXAMPLE 2

To set password used to enable or disable barring of all outgoing calls:

EXAMPLE 3

Handling of the "PS" lock password

<password length>(num)

<old password>(str)

<new password>(str)

AT+CPWD="P2","0000","8888" (where "0000" = old PIN2 and "8888" = new PIN2) OK PIN2 Password has been changed to "8888"

AT+CPWD="AO","0000","3333" Requests the network to change the password forsupplementary service "call barring".

OK Usually this request will affect all barring services,even though the request is issued for SupplementaryService BAOC ("Barring of all outgoing calls") only.Refer to the respective network provider for detail.

AT+CMEE=2 Enable text output of CME Error information AT+CPWD="PS","1111","2222" (where "1111" = old password and "2222" = new

password) OK Password for facility "PS" is now "2222" AT+CPWD="PS","1111","2222" Repeat command to provoke error "incorrect pass-

word" +CME ERROR: incorrect password ("1111" is no longer the correct password)



EXAMPLE 4

To specify a new "PS" lock password, after the old password was disabled (e.g. after three failed attempts tochange the "PS" password): use the master phone code. CAUTION: THIS TEST SHOULD BE PERFORMED ONLY IF THE CORRECT MASTER PHONE CODE FORTHE INDIVIDUAL ME USED IS DEFINITELY AVAILABLE! Otherwise the module used will be rendered use-less until the correct master phone code is entered!:

Alternatively, without giving a new password:

AT+CPWD="PS","12345678","1111" where 12345678 is the Master Phone Code and1111 is the new password. You may also use <newpassword> to restore the former disabled pass-word.

OK

AT+CPWD="PS","12345678" (where 12345678 is the Master Phone Code). Deac-tivates the present phone lock.

OK

BGS3 AT Command Set 5.7 AT^SPWD


5.7 AT^SPWD Change Password

The AT^SPWD command comprises all functions of the AT+CPWD command. Apart from the different prefixes"^SPWD" and "+CPWD", the major difference is that the <facility> list of AT^SPWD includes the additional"CM" password dedicated to the Customer SIM Lock. Set with the command AT^SCSL, this type of lock allowsthe application manufacturer to lock a mobile to specific operators.

The Customer SIM Lock feature is designed to be configurable during the production of the mobile application.Therefore, to program the "CM" password, the AT^SPWD write command can be used no matter whether the SIMis inserted or PIN authentication has been done. Opposite to that, passwords for all other facilities can only beedited if the SIM is present and PIN authentication completed.

IMPORTANT: Please note that, even though there is no need for a factory set Customer SIM Lock, you arestrongly advised to specify at least a "CM" password, avoiding that end users ever have a chance to activate thislock type.

Each password is a string of digits the length of which varies with the associated facility. The test commandreturns a list of pairs which represent the available facilities and the maximum length of the associated password.

See also AT commands AT+CLCK and AT^SLCK as well as AT^SCSL for more detail on the various lock features.

SyntaxTest Command

AT^SPWD=?Response(s)

^SPWD:list of supported ( <facility>, <password length>) OK

Write Command

AT^SPWD=<facility>[, <old password>][, <new password>]Response(s)

New password has been registered for the facility lock function. OKIf parameter <old password> was not correct:+CME ERROR: 16 (+CME ERROR: incorrect password)If the password for the selected <facility> has been invalidated due to too many failed attempts:+CME ERROR: ...In case of trying to set a "CM" password although another type of factory set SIM lock is already active: +CME ERROR: operation not supported. If error is related to ME functionality: +CME ERROR: <err>


± + + + + + - -

BGS3 AT Command Set 5.7 AT^SPWD



“CM“ Password used as Customer Mastercode for Customer SIM Lock. Defining the "CM" password allows the application manufacturer to set a Cus-tomer SIM Lock by activating a Network Personalization ("PN") with theAT^SCSL command. The "CM" password is mandatory for each operation withAT^SCSL. <password length> of "CM": 8 digits. To delete the "CM" password use the following syntax: AT^SPWD=<facil-ity>,<old password>. Please note that this action will delete all personali-sation data programmed by the manufacturer with AT^SCSL (including theoperator list).

A description of all other passwords commonly supported by AT+CPWD and AT^SPWD can be found in Section5.6, AT+CPWD. The "CM" password cannot be edited with AT+CPWD.

Note• When changing the PIN2 (<facility>="P2") it is recommended to check the new state of PIN2 using the

AT+CPIN2 command.

ExamplesEXAMPLE 1

To specify the "CM" password required as Customer Mastercode for the Customer SIM Lock:

EXAMPLE 2

To change the Customer Mastercode:

EXAMPLE 3

To delete the Customer Mastercode:

<facility>(str)

AT^SPWD="CM" Check if the Customer Mastercode was already set. ERROR No, it was not. AT^SPWD="CM", ,"12345678" Specify a new Customer Mastercode (where <old

password> is omitted and <new pass-word>"12345678" = new Customer Mastercode)

OK The Customer Mastercode has been set to"12345678".

AT^SPWD="CM" Checking again. OK Yes, it is active now.

AT^SPWD="CM","12345678","44444444" (where "12345678" = old Customer Mastercode, and"44444444" = new Customer Mastercode).

OK The Customer Mastercode has been changed from"12345678" to "44444444".

AT^SPWD="CM","44444444" Delete the Customer Mastercode by omitting <newpassword> and entering only the <old pass-word> "44444444".

OK The Customer Mastercode as well as all personali-sation data programmed by the manufacturer withAT^SCSL were deleted.

BGS3 AT Command Set 5.8 AT^SCSL


5.8 AT^SCSL Customer SIM Lock

The AT^SCSL command is designed to manage the Customer SIM Lock feature. This feature allows applicationmanufacturers to lock a mobile to specific operators by activating a Network Personalization ("PN"). If the lock isenabled the mobile will accept only SIM cards from the given operators.

The Customer SIM Lock is protected by two different passwords: • <password> = Network Personalisation password "CM" defined with AT^SPWD and necessary for program-

ming the Customer SIM Lock with AT^SCSL. • <PUK> = Lock/Unlock Code defined with AT^SCSL and used to set the Customer SIM Lock with AT^SCSL.

Also used to deactivate a given lock or activate a new one via AT+CLCK or AT^SLCK. The PUK may be pro-visioned to the end user.

The AT^SCSL write command serves to configure a Customer SIM Lock and to query the current settings.

Syntax


“PN“ Network Personalisation (= Customer SIM Lock)

Set or remove a Customer SIM Lock, or list the locks currently activated. 0 Remove the given Customer SIM Lock from ME.

Required parameters: <facility>="PN", <action>=0, <password>. Removing the Customer SIM Lock deletes both the <PUK> and all <data>, i.e.the entire list of operators.

1 Write Customer SIM Lock data to the ME and activate the lock.Required parameters: <facility>="PN", <action>=1, <password>,<PUK>, <data>.

2 Retrieve the list of operators the ME is currently locked to.Required parameters: <facility>="PN", <action>=2, <password>.

Test Command

AT^SCSL=?Response(s)

OK

Write Command

AT^SCSL=<facility>, <action>, <password>[, <PUK>, <data>]Response(s)

OKERROR+CME ERROR: <err>If <action>= 2 and command successful: ^SCSL: <data>[:<data>:<data>: ...]If <action>= 2 and operator list is empty: ^SCSL:


- + + + + + - -

<facility>(str)

<action>(num)



Password for programming the Customer SIM Lock.8-digit "CM" password for the facility "PN" that needs to be created with AT^SPWD (see note below for furtherdetails). This password is mandatory for each operation performed with AT^SCSL.

PUK created and required when entering the Customer SIM Lock data with AT^SCSL, i.e. if <action>=1. Alsoused to deactivate a given "PN" lock or to activate a new "PN" lock for another SIM card via AT+CLCK orAT^SLCK. The length of the <PUK> is also 8 digits.Each time the AT^SCSL write command is issued with parameter <action>=1 you are free to use the same<PUK> or to set a new one. In any case, a new <PUK> overwrites the previous one.

Data of the allowed network operators.Each operator code consists of the "Mobile Country Code" MCC and the "Mobile Network Code" MNC, both sep-arated by a dot, e.g. MCC1.MNC1. If more than one operator is entered on the same line, then a colon must beset between each operator code, e.g. MCC1.MNC1:MCC2.MNC2:MCC3.MNC3. For example, for the threeoperators T-Mobile D, Vodafone D2 and E-Plus you would enter the following data: 262.01:262.02:262.03Note that each time the AT^SCSL write command is executed using the parameter <action>=1 the existingoperator codes will not be overwritten, but all new data will be added to the list. This applies no matter whetherthe same operator code is already listed, i.e. entering the same operator again causes double entries. The maximum number of entries in the operator list is 50.

Notes• The use of the Customer SIM lock features may be restricted by existing facility locks. For example it is not

possible to enable Customer SIM lock while the "PS" device lock is in place. • All parameters of AT^SCSL as well as the "CM" password of AT^SPWD can be used no matter whether or not

the SIM card is inserted or PIN authentication has been done. This allows the application manufacturer to setthe "CM" password and activate the Customer SIM Lock during the production process.

• The Customer SIM Lock takes effect after the AT^SCSL write command was successfully executed withparameter <action>=1. Then, after the reboot, the mobile will accept only SIM cards from the supportedoperators.

• To remove the Customer SIM Lock use the write command AT^SCSL with <action>=0 and <password>:AT^SCSL="PN",0,password. This will delete both the <PUK> and the list of operators. The mobile will acceptany SIM card.

• Another way to operate the mobile with other SIM cards is to deactivate the Customer SIM Lock using thecommand AT+CLCK="PN",0,PUK. This will delete the list of operators specified with the Customer SIM Lock,but the <PUK> created for the Customer SIM Lock remains valid. The mobile will accept any SIM card.

• If the Customer SIM Lock is deactivated and, therefore, operable with any SIM card, the end user may usethe <PUK> to set a new SIM lock. To do so, it is necessary to enter the command AT+CLCK="PN",1,PUK first,then insert a different SIM card and finally restart the mobile. When restarted, the mobile will read out andaccept the list of operators of the currently inserted SIM card. As a result, a new Customer SIM Lock takeseffect for the operator(s) listed on this SIM card.

• If the Customer SIM Lock is active, but the end user inserts an unsupported SIM card and enters PIN1 themobile returns OK, although access to SIM related commands (such as dialing out, access to phonebooks,SMS etc.) will be denied. If then the read command AT+CPIN is executed the mobile will request the PH-NETPUK. In this case, you have two options: Use the AT+CPIN command to enter the correct <PUK> of the Cus-tomer SIM Lock. After this, the mobile can be operated with the new SIM card. As an alternative, re-insert thecorrect SIM card associated with the Customer SIM Lock and deactivate the lock via AT+CLCK="PN",0,PUK.

• If an invalid <password> or <PUK> is entered several times in succession, a delay incremented after eachfailed attempt will increase the time to wait before the next input is accepted. The delay follows the same tim-ing algorithm specified for the PH-SIM PUK (Master Phone Code). For details regarding the delay see Section5.1.1, What to do if PIN or password authentication fails?.

<password>(str)

<PUK>(str)

<data>(str)



ExamplesEXAMPLE 1

Prerequisite for using the AT^SCSL command is a valid "CM" password created with AT^SPWD. Therefore,first check the "CM" password. A more detailed example can be found in Section 5.7, AT^SPWD.

EXAMPLE 2

To check, configure and remove a "PN" lock (= Customer SIM Lock):

EXAMPLE 3

If the Customer SIM Lock is active, but the user inserts a different SIM card not supported by the list of oper-ators defined in <data> the <PUK> must be at hand:

AT^SPWD="CM",, Check that the "CM" password was already set.OK Yes, the "CM" password is valid.

AT^SCSL="PN",2,44444444 Check the current status of the Customer SIM Lock.44444444 is the "CM" password created withAT^SPWD.

Operator list is still empty, Customer SIM Lock hasnot yet been set.

^SCSL:

OKAT^SCSL="PN",1,44444444,12345678,262.01:262.02

Set a "PN" Lock, where 44444444 = "CM" password,12345678 = PH-NET PUK, 262.01 = MCC/MNC ofGerman operator T-Mobile D and 262.02 = MCC/MNC of Vodafone D2.

OKAT^SCSL="PN",2,44444444 Check again. ^SCSL: 262.01:262.02 The mobile is locked to the two network operators T-

Mobile D and Vodafone D2. OKAT^SCSL="PN",1,44444444,12345678,262.03 Add another operator (262.03 = MCC/MNC of Ger-

man network operator E-Plus). OKAT^SCSL="PN",1,44444444,11223344,262.04 Add another operator. In this case, a new PH-NET-

PUK was used. Keep in mind that the new passwordoverwrites the old one.

OKAT^SCSL="PN",0,44444444 Remove the Customer SIM Lock. Keep in mind that

this action deletes the entire list of network operatorscontained in <data>. As a result, the mobile willaccept any SIM card.

OK

AT^SCSL="PN",2,44444444 For the purpose of this example, we check the cur-rent status of the Customer SIM Lock.

The mobile lis locked to the German operators T-Molile D and Vodafone D2.

^SCSL: 262.01:262.02

OKAT+CPIN=1111 PIN1 is accepted and the mobile is operable, except

for SIM related AT commands. OKAT+CMGF=1 AT command that does not require SIM authentica-

tion. OKAT+CPBS? Attempt to use a phonebook command. +CME ERROR: network personalisation PUK required

Access to phonebook fails because of lack of SIMdata.

AT+CPIN? Check status of PIN authentication. +CPIN: PH-NET PUK The mobile is waiting for the PH-NET-PUK. OK



AT+CPIN=11223344 PH-NET PUK is given with AT+CPIN. This actiondeletes the entire operator list and, thus, removesthe Customer SIM Lock.

OK

AT+CPIN? Query status of PIN authentication.+CPIN: READYOKAT^SCSL="PN",2,44444444 Check the status of the Customer SIM Lock.^SCSL: Entire operator list is empty, Customer SIM Lock is

no longer active.OK

BGS3 AT Command Set 6. Identification Commands


6. Identification Commands

The AT Commands described in this chapter allow the external application to obtain various identification infor-mation related to the BGS3 and linked entities.

6.1 ATI Display product identification information

The ATI execute command delivers a product information text.The "Revision" information consists of the following parts: Version xx and variant yyy of software release.

Syntax


Values are not supported and only return OK.

Note• "A-REVISION aa.bbb.cc" information consists of the following parts:

Application Revision Number 'aa' as an indication of the supported application ('01' ... no dedicated applica-tion is present, ATC is the default application).Application Revision Version 'bbb' as an assignment to changes in customer application.'cc' as an additional number, e.g. defined by customer.

Exec Command

ATIResponse(s)

CinterionBGS3REVISION xx.yyyOK

Exec Command

ATI[<value>]Response(s)

OK

Exec Command

ATI1Response(s)

CinterionBGS3REVISION xx.yyyA-REVISION aa.bbb.ccOK


- + + + + + - - V.250

<value>(num)

BGS3 AT Command Set 6.2 AT+CGMI


6.2 AT+CGMI Request manufacturer identification

AT+CGMI returns a manufacturer identification text. See also: AT+GMI.

Syntax

6.3 AT+GMI Request manufacturer identification

AT+GMI returns a manufacturer identification text. See also: AT+CGMI.

Syntax

Test Command

AT+CGMI=?Response(s)

OK

Exec Command

AT+CGMIResponse(s)

CinterionOK


- + + + + + - - GSM 07.07

Test Command

AT+GMI=?Response(s)

OK

Exec Command

AT+GMIResponse(s)

CinterionOK


- + + + + + - - V.250

BGS3 AT Command Set 6.4 AT+CGMM


6.4 AT+CGMM Request model identification

AT+CGMM returns a product model identification text. Command is identical with AT+GMM.

Syntax

6.5 AT+GMM Request model identification

AT+GMM returns a product model identification text. Command is identical with AT+CGMM.

Syntax

Test Command

AT+CGMM=?Response(s)

OK

Exec Command

AT+CGMMResponse(s)

BGS3OK


- + + + + + - - GSM 07.07

Test Command

AT+GMM=?Response(s)

OK

Exec Command

AT+GMMResponse(s)

BGS3OK


- + + + + + - - V.250

BGS3 AT Command Set 6.6 AT+CGMR


6.6 AT+CGMR Request revision identification of software status

AT+CGMR delivers a product firmware version identification. Command is identical with AT+GMR.

Syntax


Version xx and variant yyy of software release.

6.7 AT+GMR Request revision identification of software status

AT+GMR delivers a product firmware version identification. Command is identical with AT+CGMR.

Syntax


Version xx and variant yyy of software release.

Test Command

AT+CGMR=?Response(s)

OK

Exec Command

AT+CGMRResponse(s)

REVISION <number>OK


- + + + + + - - GSM 07.07

<number>(str)

Test Command

AT+GMR=?Response(s)

OK

Exec Command

AT+GMRResponse(s)

REVISION <number>OK


- + + + + + - - V.250

<number>(text)

BGS3 AT Command Set 6.8 AT+CGSN


6.8 AT+CGSN Request International Mobile Equipment Identity (IMEI)

AT+CGSN delivers the International Mobile Equipment Identity (IMEI). Command is identical with: AT+GSN.

Syntax


International Mobile Equipment Identity (IMEI) used to identify a GSM mobile equipment to the GSM network

6.9 AT+GSN Request International Mobile Equipment Identity (IMEI)

AT+GSN delivers the International Mobile Equipment Identity (IMEI). Command is identical with AT+CGSN

Syntax


International Mobile Equipment Identity (IMEI) used to identify a GSM mobile equipment to the GSM network.

Test Command

AT+CGSN=?Response(s)

OK

Exec Command

AT+CGSNResponse(s)

<sn>OK


- + + + + + - - GSM 07.07

<sn>(str)

Test Command

AT+GSN=?Response(s)

OK

Exec Command

AT+GSNResponse(s)

<sn>OK


- + + + + + - - V.250

<sn>(str)

BGS3 AT Command Set 6.10 AT+CIMI


6.10 AT+CIMI Request International Mobile Subscriber Identity (IMSI)

AT+CIMI delivers the International Mobile Subscriber Identity (IMSI). The IMSI permits the TE to identify the indi-vidual SIM attached to the ME.

Syntax


International Mobile Subscriber Identity (string without quotes).

Test Command

AT+CIMI=?Response(s)

OK

Exec Command

AT+CIMIResponse(s)

<imsi>OKERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07

<imsi>(str)

BGS3 AT Command Set 7. Call related Commands


7. Call related Commands

The AT Commands described in this chapter are related to Mobile Originated (MOC, i.e. outgoing) Calls andMobile Terminated (MTC, i.e. incoming) Calls.

7.1 Call Status Information

For Circuit switched calls, including voice, fax and data calls, call status information is available with URC"+CIEV: call" (configurable via AT commands AT+CIND and AT+CMER) or - in more detail - from the list of currentcalls. This list can be displayed on request via at commands AT+CLCC and AT^SLCC. It can also be issued bythe ME in the form of an unsolicited result code "^SLCC" if configured with AT^SLCC and AT+CMER.URC "+CIEV: call" and URC "^SLCC" can be configured using AT command AT^SCFG. An overview of the pos-sible configurations and their consequences for the availability of call status information will be given here.

Generally speaking, the call status values recognized by the ME are as follows: • active• held• dialing (MOC)• alerting (MOC)• incoming (MTC)• waiting (MTC)• terminating: The call is not active anymore, but inband information is still available.• dropped: The call has been suspended by the network, but may be resumed later.The values "terminating" and "dropped" are not standardized for AT command AT+CLCC, and therefore onlyavailable for command AT^SLCC. A call in any of these two states will not appear in the list of current calls asdisplayed with AT+CLCC. A call that is not recognized by the ME is considered to be in "unknown" state.Some networks may schedule a traffic channel for a call that is not yet in the "active" state. This is reflected inparameter <traffic channel assigned> of AT command AT^SLCC and the corresponding URC.Depending on the value of AT^SCFG setting <succ>, Indicator "+CIEV" will be issued (if configured withAT+CIND and AT+CMER) • when a state transition ends in state "active" or in state "unknown"

(if AT^SCFG setting <succ>=''restricted''). • when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of

active calls, or when a traffic channel is established(if AT^SCFG setting <succ>=''verbose'').

The indicator value for indicator "+CIEV: call" will be "1" if at least one call is in states "held" or "active", and "0"otherwise.

Depending on the value of AT^SCFG setting <sucs>, Indicator "^SLCC" will be issued (if configured with writecommand AT^SLCC and AT+CMER) • when a state transition ends in state "active" or in state "unknown" (if AT^SCFG setting <sucs>="restricted") • when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of

active calls, or when a voice channel is established (if AT^SCFG setting <sucs>="verbose"). Due to compatibility considerations, the powerup default for AT^SCFG setting <succ> is "restricted", offeringcompatibility to the standard behaviour of indicator "+CIEV: call", while the default for setting <sucs> is "ver-bose".In order to see the URCs, event reporting for both indicators must be explicitly configured with the appropriateAT commands.

BGS3 AT Command Set 7.2 ATA


7.2 ATA Answer a call

Syntax

Command DescriptionTA causes remote station to go off-hook (e.g. answer call).


Connection statusoutput only if ATX parameter setting with value greater 0. Connection speed values: “300““1200““2400““4800““9600““14400“

Notes• Any additional commands on the same command line are ignored. • The command may be aborted generally by receiving a character during execution. It can't be aborted in

some connection setup states, such as handshaking. • If AT+FCLASS setting is 1 or 2, all incoming calls will be answered as fax calls, when ATA is issued on multi-

plexer channel 1 resp. ASC0. For calls explicitly signalled as voice or data calls, this procedure will fail withresult code "NO CARRIER", but the call in question will continue to ring.It is possible to change the setting for AT+FCLASS to 0 while the call is ringing, and accept the call normallyafterwards with ATA.

• The ATA command may be used also to accept a network request for a PDP context activation (see ATA). • See also ATX for <text>. • If an incoming call is no longer available (already disconnected/hanged up)a "NO CARRIER" result code will

be given.

Exec Command

ATAResponse(s)

In case of data call, if successfully connected (TA switches to data mode):CONNECT <text>In case of voice call, if successfully connected:OKWhen TA returns to command mode after call release:OKIf no connection:NO CARRIER


+ + + + + + - - V.250

<text>(str)

BGS3 AT Command Set 7.3 ATD


7.3 ATD Mobile originated call to specified number

Syntax

Command DescriptionThis command can be used to set up outgoing voice, data or fax calls. It also serves to control SupplementaryServices. The termination character ";" is mandatory to set up voice calls or to send *# codes for SupplementaryServices. It must not be used for data and fax calls.

Additional notes on the responses returned after dialing with ATD: • For voice calls, you have the choice of two different response modes that can be selected with AT^SM20:

AT^SM20=1 (factory default) causes the ME to respond once the call setup is completed either successfully("OK") or unsuccessfully ("NO CARRIER", "NO DIALTONE", "BUSY"). AT^SM20=0 causes the ME to return "OK" immediately after dialing was completed (i.e. before call setup ter-minates successfully or unsuccessfully).

• For data connections, call setup always terminates when the call has been established (indicated by the resultcode "CONNECT <text>"), or when it fails (indicated by "NO CARRIER"). The settings of AT^SM20 do notapply.

Different call release indications: • Upon termination, an outgoing fax or data call may show a different result code than a voice call would show

under identical conditions. In order to track down the actual reason for call termination, AT+CEER or ATS18should be used for all applicable connections.

Using ATD during an active call: • When a user originates a second voice call while there is already an active voice call, the first call will auto-

matically put on hold. The second call attempt is acknowledged with "OK" immediately after dialing with ATDhas completed, without relation to a successful call setup. In case of failure, the additional result codes "NOCARRIER", "NO DIALTONE", "NO CARRIER" will be presented afterwards (see example below).


String of dialing digits and optional V.250 modifiers: 0-9, *, #, +, A, B, CThe following V.250 modifiers are ignored: ,(comma), T, P, !, W ,@

Exec Command

ATD<n>[<mgsm>][;]Response(s)

If no dialtone (parameter setting ATX2 or ATX4):NO DIALTONEIf busy (parameter setting ATX3 or ATX4):BUSYIf a connection cannot be set up:NO CARRIERNO DIALTONEIf successfully connected and non-voice call (TA switches to online data mode):CONNECT <text>When TA returns to command mode after call release:OKIf successfully connected and voice call:OK


± + ± + ± ± - - V.250

<n>(text)

BGS3 AT Command Set 7.3 ATD


String of GSM modifiers:I Activates CLIR (disables presentation of own phone number to called party)i Deactivates CLIR (enables presentation of own phone number to called party)G Activate Closed User Group explicit invocation for this call only.g Deactivate Closed User Group explicit invocation for this call only.

Notes• The command may be aborted generally when receiving a character during execution. It cannot be aborted

in some connection setup states, such as handshaking. • Parameter "I" and "i" only if no *#-code is within the dial string.• <mgsm> is not supported for data calls.• <n> is default for last number that can be dialled by ATDL.• See also ATX for <text>.• If ATD is used with a USSD command (e.g. ATD*100#;) an AT+CUSD=1 is executed implicitly (see AT+CUSD).• Parameter 'G' or 'g' will be ignored if Closed User Group was already activated, respectively deactivated with

AT+CCUG command before. Call by call invocation of CUG uses the settings provisioned by the provider or,if available, the settings of the parameters <index> and <info> made with AT+CCUG.

• The ME is equipped with a "Blacklist" function according to GSM02.07 Annex A. The handling of failed callattempts follows the timing restrictions specified there. When the maximum number of failed call attempts isreached the number will be blacklisted. Call attempts to blacklisted numbers will be barred by the ME and notsignalled to the network.An attempt to start a voice call to a barred phone number is denied with a "+CME ERROR: call barred".An attempt to start a data or fax call to a barred phone number is denied with "NO CARRIER".According to GSM02.07 Annex A, the barred numbers will be removed from the blacklist after a call attemptwas successful or after module restart.

• Emergency calls: If no SIM is inserted, call numbers 000, 08, 110, 112, 118,119, 911 and 999 cause an emergency call setup.If a SIM with ECC file is inserted, 112 and 911 and all additional call numbers stored in the ECC file cause anemergency call setup.If a SIM without ECC file is inserted, call numbers 112 and 911 and in addition all call numbers specified withAT^SCFG, "Call/ECC", parameter <ecc> will cause an emergency call setup.

• To start ATD via BGS3's DTR line AT^SCFG may be used, refer parameter <AutoExecATC>. • When using the command on the second serial interface please see also Section 1.9.

Example

The following example shows the call setup procedure when a call is already active and a second call attemptfails because the line of the called party is busy:

<mgsm>(str)

ATD03012345678; Dialing out the first party's number.OK The first call is established.ATD03022222222; The number of the second party is dialed.OK The response "OK" is issued immediately though no call is established

(same behavior as is you had chosen AT^SM20=0.)BUSY Line of the second called party is busy.

BGS3 AT Command Set 7.4 ATD><mem><n>


7.4 ATD><mem><n> Mobile originated call using specific memory and index number

Syntax

Command DescriptionTA attempts to set up an outgoing call to the specified number. The termination character ";" is mandatory sincedialing from a phonebook is only supported for voice calls and for sending *# codes of Supplementary Servicesor other functions.


Phonebook storage:For detailed description of storages see AT+CPBS. “FD“ Fixed dialing phonebook“SM“ SIM phonebook“ON“ MSISDN list“ME“ Mobile Equipment Phonebook“LD“ Last number dialed phonebook“MC“ Missed (unanswered received) calls list“RC“ Received calls list“VM“ CPHS voice mailbox phonebook

Integer type memory location in the range of locations available in the selected memory, i.e. the index numberreturned by AT+CPBR.

Exec Command

ATD><mem><n>[<mgsm>];Response(s)

ERROR+CME ERROR: <err>If no dialtone (parameter ATX2 or ATX4):NO DIALTONEIf busy (parameter setting ATX3 or ATX4):BUSYIf connection cannot be set up:NO CARRIERNO DIALTONEWhen TA returns to command mode after call release:OKIf successfully connected:OK


+ + ± + ± ± - - V.250

<mem>(str)

<n>(num)

BGS3 AT Command Set 7.4 ATD><mem><n>


String of GSM modifiers:I Activates CLIR (disables presentation of own phone number to called party)i Deactivates CLIR (enables presentation of own phone number to called party)

Notes• This command may be aborted generally by receiving a character during execution. Abortion is not possible

during some states of connection setup such as handshaking. • There is no <mem> for emergency call ("EN").• The command is not applicable to data calls. Any attempt to dial a data call number from <mem> causes the

result code "NO CARRIER" to appear.• Parameter <mgsm> only if no *# code is within the dialing string.• See ATX for setting result code and call monitoring parameters. • Any string after <mgsm> and before ';' are ignored.

ExamplesEXAMPLE 1

To query the location number of the phonebook entry:

TA returns the entries available in the active phonebook.

EXAMPLE 2

To dial a number from the SIM phonebook, for example the number stored to location 15:

EXAMPLE 3

To dial a phone number stored in the last dial memory on the SIM card:

<mgsm>(str)

AT+CPBR=1,xx

ATD>"SM"15;OK

ATD>"LD"9;OK

BGS3 AT Command Set 7.5 ATD><n>


7.5 ATD><n> Mobile originated call from active memory using index number

Syntax

Command DescriptionTA attempts to set up an outgoing call to the stored number. The termination character ";" is mandatory sincedialing from a phonebook is only supported for voice calls and for sending *# codes of Supplementary Servicesor other functions.


Integer type memory location in the range of locations available in the selected memory, i.e. the index numberreturned by AT+CPBR.



during some states of connection setup such as handshaking. • The command is not applicable to data calls. Any attempt to dial a data call number from <n> causes the

result code "NO CARRIER" to appear.• Parameter <mgsm> only if no *# code is within the dialing string.

Exec Command

ATD><n>[<mgsm>];Response(s)



+ + ± + ± ± - - V.250

<n>(num)

<mgsm>(str)

BGS3 AT Command Set 7.6 ATD><str>


7.6 ATD><str> Mobile originated call from active memory using cor-responding field

Syntax

Command DescriptionThis command searches the active phonebook for a given string <str> and dials the assigned phone number.The termination character ";" is mandatory since dialing from a phonebook is only supported for voice calls andfor sending *# codes of Supplementary Services or other functions.


String type value ("x"), which should equal an alphanumeric field in at least one phonebook entry in the searchedmemories; used character set should be the one selected with AT+CSCS. <str> can contain escape sequencesas described in chapter "Supported character sets".<str> must be wrapped in quotation marks (""), if escape sequences or parameter <mgsm> are used or if thealphanumeric strings contains a blank. If not, quotation marks are optional.If AT+CSCS is set to "UCS2", with respect to the coding of UCS2-characters only phonebook entries that containan alphanumeric string with a size less than the half of the parameter <tlength> from AT+CPBW can be dialed.



during some states of connection setup such as handshaking. • The command is not applicable to data calls. Any attempt to dial <str> without semicolon ";" causes the

result code "NO CARRIER" to appear.• Parameter <mgsm> only if no *# code is within the dialing string.

Exec Command

ATD><str>[<mgsm>];Response(s)



+ + ± + ± ± - - V.250

<str>(str)(+CSCS)

<mgsm>(str)

BGS3 AT Command Set 7.7 ATDI


7.7 ATDI Mobile originated call to ISDN number

Syntax

Command DescriptionTA attempts to set up an outgoing call to ISDN number. The termination character ";" is mandatory to set up voicecalls or to send *# codes for Supplementary Services. It must not be used for data and fax calls.


ISDN numberString with maximum length of 20 characters. Allowed characters: +, 0-9, A, B, C.

Note• This command may be aborted generally by receiving a character during execution. Abortion is not possible

during some states of connection setup such as handshaking.

Exec Command

ATDI<n>[;]Response(s)

If no dialtone (parameter ATX2 or ATX4):NO DIALTONEIf busy (parameter setting ATX3 or ATX4):BUSYIf connection cannot be set up:NO CARRIERNO DIALTONEAll other error reasons:+CME ERROR: <err>If successfully connected and non-voice call (TA switches to data state):CONNECT <text>When TA returns to command mode after call release:OKIf successfully connected and voice call:OK


+ + - + - - - - V.250

<n>(str)

BGS3 AT Command Set 7.8 ATDL


7.8 ATDL Redial last number used

Syntax

Command DescriptionThis command redials the last voice and data call number used in the ATD command. If terminated with semi-colon ";" ATDL dials the last voice call number stored in the "LD" phonebook. Otherwise, the last dialed data orfax number will be used (not contained in the "LD" phonebook).


during some states of connection setup such as handshaking. • Parameter "I" and "i" only if no *#-code is within the dial string.

Exec Command

ATDL[;]Response(s)

If there is no last number or number is not valid:+CME ERROR: <err>If no dialtone (parameter ATX2 or ATX4):NO DIALTONEIf busy (parameter setting ATX3 or ATX4):BUSYIf connection cannot be set up:NO CARRIERNO DIALTONEIf successfully connected and non-voice call (TA switches to online data mode):CONNECT <text>When TA returns to command mode after call release:OKIf successfully connected and voice call:OK


+ + ± + ± ± - - V.250

BGS3 AT Command Set 7.9 ATH


7.9 ATH Disconnect existing connection

Syntax

Command DescriptionDisconnect existing call from command line by local TE and terminate call.


[0] disconnect from line and terminate call

Notes• OK is issued after circuit 109 (DCD) is turned off, if it was previously on.• ATH terminates every circuit switched call (voice, data or fax), even if it is issued via another interface. This

behavior is in accordance with ITU-T V.250; (07/97, "Hook control": "ATH is terminating any call in progress.").• ATH clears any active PDP context or terminates any existing PPP connection, but only if issued on the same

interface where GPRS is used and if there is no pending network request for PDP context activation. It doesnot affect PDP contexts and PPP connections on other interfaces (see also Section 11.20, Manual rejectionof a network request for PDP context activation.

Exec Command

ATH[<n>]Response(s)

OK


- + + + + + - - V.250

<n>(num)

BGS3 AT Command Set 7.10 AT+CHUP


7.10 AT+CHUP Hang up call

Syntax

Command DescriptionCancels all active and held calls.

Note• AT+CHUP implements the same function as ATH except that it is not supported for Fax. Therefore, Fax con-

nections can be disconnected with ATH only.

Test Command

AT+CHUP=?Response(s)


Exec Command

AT+CHUPResponse(s)



+ + + + + + - - GSM 07.07

BGS3 AT Command Set 7.11 AT^SHUP


7.11 AT^SHUP Hang up call(s) indicating a specific GSM04.08 release cause

The AT^SHUP write command terminates calls known to the ME and indicates a specific GSM04.08 releasecause specified by the user. The command can be used for voice, fax and data calls. Calls will be terminatedregardless of their current call status, which may be any of the states listed with AT+CLCC.

Syntax


Release causeGSM04.08 release cause to be indicated to the network. The BGS3 will release the selected connection(s) with release cause indication "cause" and location "user" (0)in the "disconnect" protocol message to the network. It depends on the network whether or not the release causewill be forwarded to the remote party. 1 Send GSM04.08 release cause "unassigned (unallocated) number"16 Send GSM04.08 release cause "normal call clearing " 17 Send GSM04.08 release cause "user busy "18 Send GSM04.08 release cause "no user responding "27 Send GSM04.08 release cause "destination out of order "31 Send GSM04.08 release cause "normal, unspecified"

Call numberThe "call number" is an optional index used in the list of current calls indicated by AT+CLCC. The AT^SHUP com-mand will terminate the call identified by the given call number. The default call number "0" is not assigned toany call, but signifies "all calls". As "0" is the default value, it may be omitted. [0] Terminate all known calls. 1...7 Terminate the specific call number <cn>.

Test Command

AT^SHUP=?Response(s)

OK

Write Command

AT^SHUP=<cause>[, <cn>]Response(s)

OKERROR


+ + + + + + - -

<cause>(num)

<cn>(num)



7.12 ATS0 Set number of rings before automatically answering a call

Syntax


000(&F) Automatic answer mode is disabled.001-255 Enable automatic answering after specified number of rings.

Notes• This command works for MT data and fax calls.• Autoanswering of CSD data and fax calls is supported on ASC0 /Mux1 only.• If <n> is set to higher values, the calling party may hang up before the call is automatically answered.• The correlation between ATS7 and ATS0 is important.

Example: Call setup may fail if ATS7=30 and ATS0=20.• Setting is local to the interface. It is allowed to have different settings on different interfaces. In such cases

the interface 'wins', which is idle and uses the smallest <n> value. • The ATS0 write command is PIN protected.• According to "3GPP TS 27.007 (GSM 07.07): AT command set for User Equipment (UE)", ATS0 is also used

as GPRS compatibility command to answer automatically to a network request for PDP context activation(see Section 11.21). Therefore, when the ATS0 write command is issued with <n> greater than 0, the ME willattempt to perform a GPRS attach if not yet attached and if configured to do so (due to the settingAT^SCFG="GPRS/ATS0/withAttach","on"). If the automatic GPRS attach fails the ME keeps trying to attach for approx. 5 minutes, before ATS0 ends upwith "ERROR" or "+CME ERROR: unknown", though the new <n> value takes effect. To avoid the risk of longresponse times to ATS0 in such case take care that the parameter AT^SCFG=<gs0aa> is off, if autoanswermode is not needed for GPRS or if the mobile works in non-GPRS networks. The GPRS attach will not be performed on recalling a stored user profile with ATZ or on powerup, even thougha value <n> greater than 0 was stored in the user profile with AT&W.

Read Command

ATS0?Response(s)

<n>OKERROR

Write Command

ATS0=<n>Response(s)

OKERROR


± + + + + + - - V.250

<n>(num)(&W)(&V)



7.13 ATS2 Set escape sequence character

The ATS2=43 is implemented for V.250ter compatibility reasons only, and has no effect.

Syntax


43 The data value

Read Command

ATS2?Response(s)

<n>OK

Write Command

ATS2=<n>Response(s)

OKERROR


- + + + + + - - V.250

<n>(num)



7.14 ATS6 Set pause before blind dialing

Syntax

Command DescriptionNo effect for GSM.


000(&F)...255

Read Command

ATS6?Response(s)

<n>OK

Write Command

ATS6=<n>Response(s)

OKERROR


- + - + - - - - V.250

<n>(num)(&W)(&V)



7.15 ATS7 Set number of seconds to wait for connection completion

ATS7 specifies the number of seconds the TA will wait for the completion of the call setup when answering ororiginating a data call. Also referred to as "no answer timeout". To put it plainly, this is the time to wait for thecarrier signal. If no carrier signal is received within the specified time, the TA hangs up.

Syntax


Number of seconds to wait for connection completion000...060(&F)

Notes• Command ATS7 is only applicable to data calls. • Values greater than 60 (maximum 255) cause no error, but <n> will be restored to the maximum value of 60. • The correlation between ATS7 and ATS0 is important. If the called party has specified a high value for

ATS0=<n> call setup may fail. Example: Call setup may fail if ATS7=30 and ATS0=20.

Read Command

ATS7?Response(s)

<n>OK

Write Command

ATS7=<n>Response(s)

OKERROR


- + - + - - - - V.250

<n>(num)(&W)(&V)



7.16 ATS8 Set number of seconds to wait for comma dialing modifier

This command specifies the amount of time, in seconds, that the DCE shall pause, during signalling of calladdressing information to the network (dialling), when a "," (comma) dial modifier is encountered in a dial string.

Syntax

Command DescriptionNo effect for GSM.


0(&F) DCE does not pause when "," encountered in dial string1...255 Number of seconds to pause

Read Command

ATS8?Response(s)

<n>OK

Write Command

ATS8=<n>Response(s)

OKERROR


- + - + - - - - V.250

<n>(num)(&W)(&V)



7.17 ATS10 Set disconnect delay after indicating the absence of data carrier

Syntax

Command DescriptionThis parameter setting determines the amount of time, that the TA remains connected in absence of a data car-rier. If the data carrier is detected before disconnect, the TA remains connected.


number of tenths of seconds of delay001...2(&F)...254

Read Command

ATS10?Response(s)

<n>OK

Write Command

ATS10=<n>Response(s)

OKERROR


- + - + - - - - V.250

<n>(num)(&W)(&V)

BGS3 AT Command Set 7.18 ATO


7.18 ATO Switch from command mode to data mode / PPP online mode

Syntax

Command DescriptionATO is the corresponding command to the +++ escape sequence: When you have established a CSD call or aGPRS connection and TA is in command mode, ATO causes the TA to resume the data or GPRS connection andtakes you back to data mode or PPP online mode.


[0] Switch from command mode to data mode

Exec Command

ATO[<n>]Response(s)

If connection is not successfully resumed:NO CARRIERorTA returns to data mode from command modeCONNECT <text>Note: <text> output only if ATX parameter setting with value > 0.


- + ± + - - - - V.250

<n>(num)

BGS3 AT Command Set 7.19 +++


7.19 +++ Switch from data mode or PPP online mode to command mode

Syntax

Command DescriptionThis command is only available during a CSD call or a GPRS connection. The +++ character sequence causesthe TA to cancel the data flow over the AT interface and switch to command mode. This allows you to enter ATcommands while maintaining the data connection to the remote device or, accordingly, the GPRS connection. To prevent the +++ escape sequence from being misinterpreted as data, it must be preceded and followed by apause of at least 1000 ms. The +++ characters must be entered in quick succession, all within 1000 ms.

Note• To return from command mode to data or PPP online mode: Enter ATO.

Exec Command

+++Response(s)

OK


- + - - - - - - V.250

BGS3 AT Command Set 7.20 AT+CBST


7.20 AT+CBST Select bearer service type

The AT+CBST write command selects the bearer service <name>, the data rate <speed> and the connectionelement <ce> to be used when data calls are originated. The settings also apply to mobile terminated data calls,especially when single numbering scheme calls or calls from analog devices are received (see AT+CSNS). SeeGSM 02.02[1] for a list of allowed combinations of subparameters.

Syntax


0 Autobauding1 300 bps (V.21)2 1200 bps (V.22)4 2400 bps (V.22bis)6 4800 bps (V.32)[7](&F) 9600 bps (V.32)14 14400 bps (V.34)65 300 bps (V.110)66 1200 bps (V.110)68 2400 bps (V.110)70 4800 bps (V.110)71 9600 bps (V.110)75 14400 bps (V.110)

0(&F) Asynchronous modem

Test Command

AT+CBST=?Response(s)

+CBST: (list of supported<speed>s), (list of supported<name>s), (list of supported<ce>s)OK

Read Command

AT+CBST?Response(s)

+CBST: <speed>, <name>, <ce>OK

Write Command

AT+CBST=<speed>[, <name>[, <ce>]]Response(s)

OKERROR


- + - + - - - - GSM 07.07

<speed>(num)(&W)(&V)

<name>(num)(&W)

BGS3 AT Command Set 7.20 AT+CBST


Transparent mode is not supported.1(&F) Non-transparent

Note• If problems are encountered with CSD connections at 14.4 kbit/s you may be required to change the Fixed

Network User Rate depending on the network. See AT^SFNUR for details.

<ce>(num)(&W)

BGS3 AT Command Set 7.21 AT+CRLP


7.21 AT+CRLP Select radio link protocol parameters for originated non-transparent data calls

The AT+CRLP write command sets radio link protocol (RLP) parameters used when non-transparent data callsare originated. The read command returns the current settings for the supported RLP version 0.

Syntax


Interworking window size (IWF to MS)0...61(&F)

Mobile window size (MS to IWF)0...61(&F)

Acknowledgement timer (T1 in 10 ms units)39...[78](&F)...255

Re-transmission attempts N21...6(&F)...255

Test Command

AT+CRLP=?Response(s)

+CRLP: (list of supported<iws>s), (list of supported<mws>s), (list of supported<T1>s), (list of supported<N2>s)OK

Read Command

AT+CRLP?Response(s)

+CRLP: <iws>, <mws>, <T1>, <N2>OK

Write Command

AT+CRLP=[<iws>[, <mws>[, <T1>[, <N2>]]]]Response(s)



- + - + - - - - GSM 07.07

<iws>(num)(&W)(&V)

<mws>(num)(&W)(&V)

<T1>(num)(&W)(&V)

<N2>(num)(&W)(&V)

BGS3 AT Command Set 7.22 AT+CLCC


7.22 AT+CLCC List of current calls

The execute command lists all current calls. If the command is successful, but no calls are available, no infor-mation response is sent to TE.

Syntax


Call identification number as described in GSM02.30 subclause 4.5.5.1; this number can be used in AT+CHLDcommand operations

0 Mobile originated call (MOC)1 Mobile terminated call (MTC)

State of the call0 Active1 Held2 Dialing (MOC)3 Alerting (MOC)4 Incoming (MTC)5 Waiting (MTC)

Bearer/teleservice0 Voice1 Data2 Fax

Test Command

AT+CLCC=?Response(s)

OK

Exec Command

AT+CLCCResponse(s)

[+CLCC: <idx>, <dir>, <stat>, <mode>, <mpty>[, <number>, <type>[, <alpha>]]][+CLCC: <idx>, <dir>, <stat>, <mode>, <mpty>[, <number>, <type>[, <alpha>]]][+CLCC: ...]OKERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07

<idx>(num)

<dir>(num)

<stat>(num)

<mode>(num)

BGS3 AT Command Set 7.22 AT+CLCC


3 Voice followed by data, voice mode (only in connection with single numberingscheme AT+CSNS)

4 Alternating voice/data, voice mode (only in connection with single numberingscheme AT+CSNS)

5 Alternating voice/fax, voice mode (only in connection with single numberingscheme AT+CSNS)

6 Voice followed by data, data mode (only in connection with single numberingscheme AT+CSNS)

7 Alternating voice/data, data mode (only in connection with single numberingscheme AT+CSNS)

8 Alternating voice/fax, fax mode (only in connection with single numberingscheme AT+CSNS)

9 Unknown

0 Call is not one of multiparty (conference) call parties 1 Call is one of multiparty (conference) call parties

Phone number in format specified by <type>

Type of address octect145 Dialing string <number> includes international access code character '+'128 Number is restricted 129 Otherwise

Alphanumeric representation of <number> corresponding to the entry found in phonebook (see for exampleAT+CPBW, parameter <text>). Due to time constraints on the necessary evaluation of the phonebook, this parameter may show a default valuein early call phases (e.g. for <stat>= ''dialing'', ''incoming'' or ''alerting''), even if a phonebook entry is presentfor the number concerned.

Note• Teleservices other than voice, data, fax are not fully supported by ME. They are used only in connection with

the handling for AT+CSNS, and may therefore occur in parameter <mode> for mobile terminated calls.

<mpty>(num)

<number>(str)

<type>(num)

<alpha>(str)(+CSCS)

BGS3 AT Command Set 7.23 AT^SLCC


7.23 AT^SLCC Extended list of current calls

AT^SLCC covers essentially the same information as GSM 07.07 command AT+CLCC, with the following exten-sions: • The execute command response contains the additional parameter <traffic channel assigned> which

indicates whether the call has been assigned a traffic channel by the network and transmission of DTMFtones is possible.

• The additional write command allows to activate Event reporting for the list of current calls. If event reportingis active for an interface, a call status transition (cf. Call Status Information) and (if desired) theassignment of a traffic channel will generate an event report indication to this interface. In order to receivethis event report as an URC, the URC presentation mode for this interface has to be configured withAT+CMER. Interface settings are saved with AT&W and can be displayed with AT&VThe frequency of event report generation can be configured with AT command AT^SCFG. Refer to CallStatus Information for further detail on the configuration options.

• The additional read command returns an indication whether event reporting is active for the current interface.Mind that the URC will be displayed only if the URC presentation mode for the interface concerned has beenconfigured with AT+CMER.

• The exec command returns, like AT+CLCC, a list of current calls. If the command is successful, but no callsare available, no information response is sent to the TE.

SyntaxTest Command

AT^SLCC=?Response(s)

^SLCC: (list of supported<n>s)OK

Read Command

AT^SLCC?Response(s)

^SLCC: <n>OK

Exec Command

AT^SLCCResponse(s)

[^SLCC:<idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]]][^SLCC:<idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]]][^SLCC:...]OKERROR+CME ERROR: <err>

Write Command

AT^SLCC=[<n>]Response(s)



+ + + + + + - -



Unsolicited Result CodeUnsolicited Call Status information if the list of current calls is empty: ^SLCC:

if one or more calls are currently in the list: ^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]][^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]]][... ]^SLCC:

URC "^SLCC" displays the list of current calls as displayed with the execute command AT^SLCC. The list is dis-played in the state it has at the time of display, not in the state it had when the signal was generated.The URC's occurrence indicates call status changes for any of the calls in the list of current calls.Please refer to Call Status Information and AT^SCFG for further information about the configuration ofthis URC.Event reporting can be enabled separately for each interface. Interface settings are saved with AT&W and can bedisplayed with AT&V. Additionally, The URC presentation mode for the interface must be configured withAT+CMER.Depending on the value of AT^SCFG setting <sucs>, Indicator "^SLCC" will be issued (if configured with writecommand AT^SLCC and AT+CMER) • when a state transition ends in state "active" or in state "unknown" (if AT^SCFG setting <sucs>="restricted") • when any state transition (including transitions beginning or ending in state "unknown") occurs in the list of

active calls, or when a traffic channel is established (if AT^SCFG setting <sucs>="verbose"). If multiple displays of identical list configurations occur, this happens because of short intermediate states of thelist, that have already been overridden by new transitions and states. Thus, it is guaranteed that the configurationdisplayed is always the current configuration at the time of the last display.The list of active calls displayed with this URC will always be terminated with an empty line preceded by prefix"^SLCC: ", in order to indicate the end of the list.


[0](&F) Presentation of URC "^SLCC" disabled 1 Presentation of URC "^SLCC" enabled

Call identification number as described in GSM02.30 subclause 4.5.5.1; this number can be used in AT+CHLDcommand operations.

0 Mobile originated call (MOC)1 Mobile terminated call (MTC)

state of the call0 Active1 Held2 Dialing (MOC)3 Alerting (MOC)4 Incoming (MTC)5 Waiting (MTC)

<n>(num)(&W)(&V)

<idx>(num)

<dir>(num)

<stat>(num)



bearer/teleservice0 Voice1 Data2 Fax3 Voice followed by data, voice mode (only in connection with single numbering

scheme AT+CSNS)4 Alternating voice/data, voice mode (only in connection with single numbering

scheme AT+CSNS)5 Alternating voice/fax, voice mode (only in connection with single numbering

scheme AT+CSNS)6 Voice followed by data, data mode (only in connection with single numbering

scheme AT+CSNS)7 Alternating voice/data, data mode (only in connection with single numbering

scheme AT+CSNS)8 Alternating voice/fax, fax mode (only in connection with single numbering

scheme AT+CSNS)9 Unknown

0 Call is not one of multiparty (conference) call parties 1 Call is one of multiparty (conference) call parties

0 No traffic channel assigned. Transmission of DTMF tones not possible. 1 Traffic channel is assigned and the progress indicator IE has been received

(call setup) or a voice connection has an active state. The parameter indicatesthat the audio path is activated. DTMF tones can be sent with AT+VTS.

Phone number in format specified by <type>

Type of address octect145 Dialing string <number> includes international access code character '+'128 number is restricted 129 Otherwise

Alphanumeric representation of <number> corresponding to the entry found in phonebook (see for exampleAT+CPBW, parameter <text>). Due to time constraints on the necessary evaluation of the phonebook, this parameter may show a default valueduring early call phases (e.g. for <stat>= "dialing", "incoming" or "alerting"), even if a phonebook entry ispresent for the number concerned.

<mode>(num)

<mpty>(num)

<traffic channel assigned>(num)

<number>(str)

<type>(num)

<alpha>(str)(+CSCS)



Notes• Teleservices other than voice, data, fax are not fully supported by ME. They are used only in connection with

the handling for AT+CSNS, and may therefore occur in parameter <mode> for mobile terminated calls.• If a URC "^SLCC" in verbose mode (see AT^SCFG) has been buffered while the interface was in dedicated

mode (depending on the settings of AT+CMER parameter <bfr>), each buffered event indicator will be outputas a separate URC after the interface returns to idle mode. However, the output will deliver the list of current calls in the "current" state (at the time when the output isgenerated), possibly leading to multiple displays of identical list configurations.

• Some parameters of the AT+CHLD command, as well as some situations where the call status in the networkchanges very quickly (e.g. the transition between <stat>= "unknown", "dialing" and "alerting" for a call to areachable subscriber within the registered network) may lead to quasi-simultaneous changes to the states ofone or several calls in the list, possibly leading to multiple displays of identical list configurations.

• If multiple displays of identical list configurations occur, this happens because of intermediate states of thelist, that have already been overridden by new transitions and states. Thus, it is guaranteed that the configu-ration displayed in such cases is the current configuration at the time of the last display.

• It is adviseable to receive URC "^SLCC" on an interface that is not used for call initiation, if verbose output isconfigured. If only voice calls are expected, a setting of AT^SM20= 0 may be used alternatively in order tokeep the call from blocking the interface.

• If a multiparty call is established, the transmission of DTMF tones is not possible anymore till the call isreleased. This behaviour is caused due to an ambiguity between the different transaction identifiers.

ExamplesEXAMPLE 1

^SYSSTARTat+cpin=9999OK

+CREG: 2

+CREG: 1,"0145","0016" We are now registered.at^sm20=0 Command ATD for an outgoing voice call will termi-

nate immediately with response "OK".

OKatd"1234567"; We start a voice call.OK "OK" response is issued immediately because of set-

ting AT^SM20="0". ^SLCC: 1,0,2,0,0,0,"1234567",129,"Called Party"

MO voice call starts, paging B-party.

^SLCC: End of current list^SLCC: 1,0,2,0,0,1,"1234567",129,"Called Party"

Traffic channel established, network may now transmit network announcements,ME may now transmit DTMF tones.


Call is now ringing at B-Party.


B-Party has accepted the call, connection estab-lished.

^SLCC: End of current list.atd23456; We start a second voice call.OK "OK" response is issued immediately because

another call is already active (cf. ATD).^SLCC: 1,0,1,0,0,0,"1234567",129,"Called Party"

The active call is automatically put on hold, triggeringthe display of the list.



EXAMPLE 2

^SLCC: 2,0,2,0,0,1,"23456",129 The second call has already started before the indi-cation for the held call could be displayed

^SLCC: End of current list.^SLCC: 1,0,1,0,0,0,"1234567",129,"Called Party"

The identical list is displayed again, triggered by thestart of the second voice call.

^SLCC: 2,0,2,0,0,1,"23456",129 The status of the second list entry has already beendisplayed with the previous URC.

^SLCC: End of current list.^SLCC: 1,0,1,0,0,0,"1234567",129,"Called Party"

The held call doesn't change status right now.

^SLCC: 2,0,3,0,0,1,"23456",129 The second call is now alerting the B-Party.^SLCC: End of current list.^SLCC: 1,0,0,0,0,1,"1234567",129,"Called Party"

The held call doesn't change status right now.

^SLCC: End of current list: the B-Party of the second call hasnot accepted the call in time, the second call hasended.

NO CARRIER The second call has ended.^SLCC: list is now empty: B-Party has ended the first call.NO CARRIER The first call has ended.

^SLCC: 1,1,4,0,0,1,"1234567",129 Incoming voice call is signalled.Display is triggered by the incoming call, but the cur-rent status of the call at the time of display alreadycomprises an active traffic channel.

^SLCC: End of current list.RING Incoming call is signalled.^SLCC: 1,1,4,0,0,1,"1234567",129 The incoming call had a traffic channel assigned

from the start.This second identical display is triggered by the traf-fic channel assignment.Since the traffic channel was already indicated in theprevious URC, both instances of the URC containidentical information.

^SLCC: End of current list.RING Incoming call is signalled.ata Incoming call is accepted.OK call is established.^SLCC: 1,1,0,0,0,1,"1234567",129 The call is now active.^SLCC: End of current list.ath Hang up the call.OK hang up complete.^SLCC: The list of current calls is empty again.

BGS3 AT Command Set 7.24 AT+CR


7.24 AT+CR Service reporting control

AT+CR configures the TA whether or not to transmit an intermediate result code +CR: <serv> to the TE when acall is being set up. Setting the value of <mode> to 1 may lead to connection failure, if the application (e.g. WinFax) waits for defaultresult code/URC.

Syntax

Intermediate Result CodeIf enabled, an intermediate result code is transmitted during connect negotiation when the TA has determinedthe speed and quality of service to be used, before any error control or data compression reports are transmitted,and before any final result code (e.g. CONNECT) appears. +CR: <serv>


0(&F) Disable1 Enable

“REL ASYNC“ Asynchronous non-transparent“GPRS“ GPRS“SYNC“ Fax connection

Test Command

AT+CR=?Response(s)

+CR: (list of supported<mode>s)OKERROR

Read Command

AT+CR?Response(s)

+CR: <mode>OKERROR

Write Command

AT+CR=<mode>Response(s)

OKERROR


+ + + + + + - - GSM 07.07

<mode>(num)(&W)(&V)

<serv>(str)

BGS3 AT Command Set 7.25 AT+CRC


7.25 AT+CRC Set Cellular Result Codes for incoming call indication

The AT+CRC command controls whether or not to use the extended format of incoming call indication.<mode>=1 may lead to connection failure, if the application (e.g. WinFax) waits for the default URC.

Syntax


URC 1

RING

Indicates incoming call to the TE if <mode>=0.

URC 2

+CRING: <type>

Indicates incoming call to the TE if <mode>=1.


[0](&F) Disable extended format1 Enable extended format

“REL ASYNC“ Asynchronous non-transparent“FAX“ Facsimile“VOICE“ Voice“GPRS“ <PDP_type>, <PDP_addr> [,[<L2P>][,<APN>]] GPRS network request for

PDP context activation

Test Command

AT+CRC=?Response(s)

+CRC: (list of supported<mode>s)OKERROR

Read Command

AT+CRC?Response(s)

+CRC: <mode>OKERROR

Write Command

AT+CRC=[<mode>]Response(s)

OKERROR


- + + + + + - - GSM 07.07

<mode>(num)(&W)(&V)

<type>(str)

BGS3 AT Command Set 7.26 AT+CSNS


7.26 AT+CSNS Single Numbering Scheme

The AT+CSNS command enables the ME to accept incoming calls when no bearer capability information is pro-vided with the call, e.g. single numbering scheme calls or calls originating from analog devices.

Syntax


Parameter is non-volatile. [0](D) Voice: Each call received without bearer element is assumed to be speech2 Fax: Each call received without bearer element is assumed to be an incoming

fax.4 Data: Each call received without bearer element is assumed to be a data call.

Please take into account that the bearer service parameters set with AT+CBSTapply to all data calls including those received without bearer capability.

Notes• The command must be set before the call comes. By default, when you do not modify the settings, all calls

received without bearer element are assumed to be voice. • If problems are encountered with CSD connections at 14.4 kbit/s you may be required to change the Fixed

Network User Rate depending on the network. See AT^SFNUR for details.

Test Command

AT+CSNS=?Response(s)

+CSNS: (list of supported<mode>s)OK

Read Command

AT+CSNS?Response(s)

+CSNS: <mode>OK

Write Command

AT+CSNS=[<mode>]Response(s)



- + + + + + - - GSM 07.07

<mode>(num)

BGS3 AT Command Set 7.27 AT^SCNI


7.27 AT^SCNI List Call Number Information

Syntax

Command DescriptionTA returns a list of current calls of ME.


call identification number as described in GSM 02.30[19] subclause 4.5.5.1; this number can be used inAT+CHLD command operations1...7

Call status of respective call number (first parameter)0 call hold1 call in progress2 waiting call

string type phone number in format specified by <type>

type of address octet in integer format; 145 when dialling string includes international access code character "+",128 when number is restricted otherwise 129

Note• See also GSM 07.07: AT+CLCC

Test Command

AT^SCNI=?Response(s)

OK

Exec Command

AT^SCNIResponse(s)

^SCNI: <id>1[,<cs>[,<number>,<type>]]^SCNI: <id>2[,<cs>[,<number>,<type>]][...]OKERROR+CME ERROR: <err>


+ + + + + + - -

<id>(num)

<cs>(num)

<number>(str)

<type>(num)

BGS3 AT Command Set 7.28 AT^SLCD


7.28 AT^SLCD Display Last Call Duration

Syntax

Command DescriptionTA returns last call duration or current call duration.


Format is "hh:mm:ss", where characters indicate hours, minutes, seconds; E.g. 22:10:00 "22:10:00"Max value is 9999:59:59

Note• The proper working of that command is network dependant.

Test Command

AT^SLCD=?Response(s)


Exec Command

AT^SLCDResponse(s)

^SLCD: <time>OKERROR+CME ERROR: <err>


+ + + + + + - -

<time>(str)

BGS3 AT Command Set 7.29 AT^STCD


7.29 AT^STCD Display Total Call Duration

Syntax

Command DescriptionTA returns total call duration (accumulated duration of all calls).


Format is "hh:mm:ss", where characters indicate hours, minutes, seconds; E.g. 22:10:00 "22:10:00"Max value is 9999:59:59

Notes• The Total Call Duration will not be reset by power off or other means.• The proper working of that command is network dependant and only for MO calls.

Test Command

AT^STCD=?Response(s)


Exec Command

AT^STCDResponse(s)

^STCD: <time>OKERROR+CME ERROR: <err>


+ + + + + + - -

<time>(str)

BGS3 AT Command Set 7.30 ATP


7.30 ATP Select pulse dialing

Syntax

Note• No effect for GSM.

7.31 ATT Select tone dialing

Syntax

Note• No effect for GSM.

Exec Command

ATPResponse(s)

OK


- + - + - - - - V.250

Exec Command

ATTResponse(s)

OK


- + - + - - - - V.250

BGS3 AT Command Set 8. Network Service Commands


8. Network Service Commands

The AT Commands described in this chapter are related to various network services. More commands relatedto this area can be found in Chapter 9., Supplementary Service Commands.

8.1 AT+COPN Read operator names

The AT+COPN command returns the list of operator names from the ME. Each operator code <numericn> thathas an alphanumeric equivalent <alphan> in the ME memory is returned. See also: AT^SPLM.

Syntax


Operator in numeric format; GSM location area identification number.

Operator in long alphanumeric format; can contain up to 26 characters.

Test Command

AT+COPN=?Response(s)


Exec Command

AT+COPNResponse(s)

+COPN: <numericn>, <alphan>+COPN: ...OKERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07

<numericn>(str)

<alphan>(str)

BGS3 AT Command Set 8.2 AT+COPS


8.2 AT+COPS Operator Selection

AT+COPS queries the present status of the BGS3's network registration and allows to determine whether auto-matic or manual network selection shall be used. Additional service is available with AT^SOPS.

Three operator selection modes are available: • Automatic

BGS3 searches for the home operator automatically. If successful the BGS3 registers to the home network.If the home network is not found, BGS3 goes on searching. If a permitted operator is found, BGS3 registersto this operator. If no operator is found the BGS3 remains unregistered.

• Manual Desired operator can be determined using the AT+COPS write command. If the operator is found, BGS3 reg-isters to it immediately. If the selected operator is forbidden, the BGS3 remains unregistered.

• Manual/automatic The ME first tries to find the operator determined via AT+COPS write command. If the ME is able to registerto this operator, it enters the manual operator selection mode. If the ME cannot find this operator or fails toregister to this operator, then it enters the automatic operator selection mode and starts to select the homeoperators network or another (permitted) one. If the ME is registered and the manually selected network isnot available, the ME will remain registered without further result code notification.

The most recently entered operator selection mode is still valid after the ME was restarted (power-off/on).

The AT+COPS test command conists of several parameter sets, each representing an operator present in thenetwork. Each set contains the following information: • an integer indicating the availability of the operator, • long alphanumeric format of the operator's name and • numeric format representation of the operator. Any of the parameters may be unavailable and will then be an empty field (,,). The list of operators comes in thefollowing order: Home network, networks referenced in SIM and other networks. The operator list is followed by a list of the supported <mode>s and <format>s. These lists are delimited fromthe operator list by two commas. If the test command is used during an ongoing GPRS transfer, traffic will be interrupted for up to one minute.

The AT+COPS read command returns the current <mode> and the currently selected operator. If no operator isselected, <format> and <oper> are omitted.

The AT+COPS write command forces an attempt to select and register to the GSM network operator (see notebelow). If the selected operator is not available, no other operator will be selected (except <mode>=4). Theselected operator name <format> will apply to further read commands, too.

Command settings are effective over all serial interfaces of the BGS3.

SyntaxTest Command

AT+COPS=?Response(s)

+COPS: [list of present operators (<opStatus>, long alphanumeric <oper>s,,numeric <oper>s ], , (list of supported <mode>s), (list of supported <format>s)OKERROR+CME ERROR: <err>




Status0 Unknown1 Operator available2 Current operator 3 Operator forbidden

OperatorIf test command: Operator name in long alphanumeric format and numeric format.If read command: Operator name as per <format>.If write command: Operator name in numeric format.

Parameter values 0 and 1 are stored non-volatile in the BGS3.0(D) Automatic mode; <oper> field is ignored. 1 Manual operator selection

Write command requires <oper> in numeric format, i.e. <format> shall be 2. Read command returns the current <mode> and the currently selected<oper>. If no operator is selected, <format> and <oper> are omitted.

2 Manually deregister from network and remain unregistered until <mode>=0 or1 or 4 is selected.

3 Set only <format> (for AT+COPS read command). 4 Automatic / manual selection; if manual selection fails, automatic mode

(<mode>=0) is entered (<oper> field will be present).

Read Command

AT+COPS?Response(s)

+COPS:<mode>[, <format>[, <oper>]]OKERROR+CME ERROR: <err>

Write Command

AT+COPS=<mode>[, <format>[, <oper>]]Response(s)



± + + + + + - - GSM 07.07

<opStatus>(num)

<oper>(str)

<mode>(num)(&V)



0(&F) Long alphanumeric format of <oper>. Can be up to 26 characters long. 2 Numeric format of <oper>. This is the GSM Location Area Identification (LAI)

number, which consists of the 3-digit Mobile Country Code (MCC) plus the 2-or 3-digit Mobile Network Code (MNC).

Notes• It is not recommended to use the AT+COPS command before passing the CHV (card holder verification) / SIM

PIN1 verification. In case of entering of AT+COPS= 0 before PIN1 verification the module will answer with OKand does not try to register to the network. Also, the test command should only be used after PIN1 authenti-cation.

• It's possible to apply a 5- or 6-digit LAI for numeric format of <oper> parameter. Please use the correct 2- or3-digit Mobile Network Code. Otherwise an unintended PLMN could be selected.

• It is not recommended to use the AT+COPS write and test command while BGS3 is searching for a new oper-ator. In this case the module will answer with ERROR. Please use AT+CREG to verify the network registrationstatus.

<format>(num)(&W)(&V)

BGS3 AT Command Set 8.3 AT^SOPS


8.3 AT^SOPS Extended Operator Selection

AT^SOPS queries the present status of the BGS3's network registration. Since basic operator selection servicesare available with AT+COPS this command uses the methods of the Enhanced Operator Name String (EONS)specification while handling operator name strings. Additional EONS related information is available withAT^SIND.

AT^SOPS test command lists sets of five parameters, each representing an operator present in the network. A set consists of

1. an integer indicating the availability of the operator, 2. specification of the source of the operator name <eonsOperator>, 3. operator name according to EONS Table, 4. Service Provider Name from the SIM Service Table and 5. numeric format representation of the operator.

Any of the parameters may be unavailable and will then be an empty field (,,). The list of operators comes in the following order: Home network, networks referenced in SIM and other net-works. After the operator list the BGS3 returns lists of supported <mode>s and <format>s. These lists are delimitedfrom the operator list by two commas. If the test command is used while an ongoing GPRS transfer, traffic will be interrupted for up to one minute.

Command settings are effective over all serial interfaces of the BGS3.

Syntax


Status0 unknown1 operator available2 current operator3 operator forbidden

Specification of the source of the operator name <eonsOperator>. Details of EONS-supplied operator nametypes are available at AT^SIND.

Operator name; format depends on the source of the operator name, specified by <eonsType>.

Test Command

AT^SOPS=?Response(s)

^SOPS:[list of present operator( <opStatus>, <eonsType>, <eonsOperator>, <servProvider>, <opName>)s ], , (list of supported <mode>)s, (list of supported <format>)sOKERROR+CME ERROR: <err>


+ + + + + + - -

<opStatus>(num)

<eonsType>(num)

<eonsOperator>

BGS3 AT Command Set 8.3 AT^SOPS


Service Provider Name according to setting of Service No. 17 in the SIM Service Table (EFSST).

OperatorOperator name in numerical presentation contains the GSM Location Area Identification (LAI) number, whichconsists of the 3-digit Mobile Country Code (MCC) plus the 2- or 3-digit Mobile Network Code (MNC). Parameter is stored non-volatile to the SIM.

Parameter is not applicable.

Parameter is not applicable.

Notes• The AT^SOPS Test command is only accepted by the module after a valid pin has been entered. • It is not recommended to use the AT^SOPS test command while BGS3 is searching for a new operator. In this

case the module will answer with ERROR. Please use AT+CREG to verify the network registration status.

<servProvider>(str)

<opName>

<mode>(num)

<format>(num)

BGS3 AT Command Set 8.4 AT+CREG


8.4 AT+CREG Network registration

The AT+CREG command serves to verify the network registration status of the ME. For this purpose two types ofURCs are available. The AT+CREG read command returns the URC presentation mode <n> and an integer <stat> that shows theregistration status of the ME. The location information elements <lac> and <ci> are returned only when <n>=2and ME is registered to the network.

Syntax


URC 1

If <n>=1 and there is a change in the ME network registration status: +CREG: <stat>

URC 2

If <n>=2 and there is a change in the ME network registration status or a change of the network cell: +CREG: <stat>[, <lac>, <ci>]


[0](&F) Disable +CREG URC1 Enable URC +CREG:<stat> to report status of network registration 2 Enable URC +CREG:<stat>[,<lac>,<ci>] to report status of network regis-

tration including location information. The optional parameters <lac> and<ci> will not be updated during calls.

Test Command

AT+CREG=?Response(s)

+CREG: (list of supported<n>s)OK

Read Command

AT+CREG?Response(s)

+CREG: <n>, <stat>[, <lac>, <ci>]OKERROR+CME ERROR: <err>

Write Command

AT+CREG=[<n>]Response(s)



- + + + + + - - GSM 07.07

<n>(num)(&W)(&V)



0 Not registered, ME is currently not searching for new operatorNormally, status 0 occurs temporarily between two network search phases(status 2). However, if it persists, one the following reasons may apply:• Automatic network selection is active, but probably there is

- no SIM card available- no PIN entered- no valid Home PLMN entry found on the SIM

• Manual network selection is active and the selected network is available,but login fails due to one of the following reasons: - #11 ... PLMN not allowed- #12 ... Location area not allowed- #13 ... Roaming not allowed in this location area

In either case, user intervention is required. Yet, emergency calls can be madeif any network is available.

1 Registered to home network2 Not registered, but ME is currently searching for a new operator

The ME searches for an available network. Failure to log in until after more thana minute may be due to one of the following reasons: • No network available or insufficient Rx level.• The ME has no access rights to the networks available.• Networks from the SIM list of allowed networks are around, but login fails

due to one of the following reasons: - #11 ... PLMN not allowed- #12 ... Location area not allowed- #13 ... Roaming not allowed in this location areaAfter this, the search will be resumed (if automatic network search isenabled).

• The Home PLMN or an allowed PLMN is available, but login is rejected bythe cell (reasons: Access Class or LAC).

If at least one network is available, emergency calls can be made. 3 Registration denied

• Authentication or registration fails after Location Update Reject due to oneof the following reasons: - #2 ... IMSI unknown at HLR- #3 ... Illegal MS- #6 ... Illegal MEEither the SIM or the MS or the ME are unable to log into any network. Nofurther attempt is made to search or log into a network. User intervention isrequired. Emergency calls can be made, if any network is available.

4 Unknown (not used) 5 Registered, roaming

The ME is registered at a foreign network (national or international network)

Two byte location area code in hexadecimal format (e.g. "00C3" equals 193 in decimal).

<stat>(num)(&V)

<lac>(str)



Two byte cell ID in hexadecimal format.

Note• After the "+CREG: 1" (or "+CREG: 5") URC and before the SIM notification URC "+CIEV: simstatus" it is not

sure that outgoing and incoming calls can be made and short message functions executed. Emergency callsare possible.Outgoing and incoming calls are always possible AFTER having received the "+CREG: 1" (or "+CREG: 5") andSIM notification URC "+CIEV: simstatus". See also Section 20.1, Restricted access to SIM data after SIM PIN authentication.

Example

<ci>(str)

AT+CREG=2 Activates extended URC mode.OKAT+COPS=0 Forces ME to automatically search network operator.OK+CREG: 2 URC reports that ME is currently searching.+CREG: 1,"0145","291A" URC reports that operator has been found.

BGS3 AT Command Set 8.5 AT+CSQ


8.5 AT+CSQ Signal quality

The AT+CSQ execute command indicates the received signal strength <rssi> and the channel bit error rate<ber>.

Syntax


0 -113 dBm or less1 -111 dBm2..30 -109... -53 dBm31 -51 dBm or greater99 not known or not detectable

0..7 as RXQUAL values in the table in GSM 05.08 section 8.2.4.99 not known or not detectable

Note• After using network related commands such as AT+CCWA, AT+CCFC, AT+CLCK, users are advised to wait 3s

before entering AT+CSQ. This is recommended to be sure that any network access required for the precedingcommand has finished.

Test Command

AT+CSQ=?Response(s)

+CSQ: (list of supported<rssi>s), (list of supported<ber>s)OK

Exec Command

AT+CSQResponse(s)

+CSQ: <rssi>,<ber>OK


- + + + + + - - GSM 07.07

<rssi>(num)

<ber>(num)

BGS3 AT Command Set 8.6 AT^SMONC


8.6 AT^SMONC Cell Monitoring

The AT^SMONC execute command delivers cell information containing 9 values from a maximum of 7 base sta-tions. The first base station is the serving cell.

Syntax


Mobile country code3 digits, e.g. 232000 Not decoded

Mobile network code2 digits or 3 digits, e.g. 07 or 003000 Not decoded

Location area code4 hexadecimal digits, e.g. 4EED0000 Not decoded

Cell identifier4 hexadecimal digits, e.g. 4EAF0000 Not decodedFFFF Cell ID currently not available, e.g. because the cell ID information is not yet

read from the Sysinfo 3 transmitted by the base station.

Test Command

AT^SMONC=?Response(s)


Exec Command

AT^SMONCResponse(s)

^SMONC:<MCC>1, <MNC>1, <LAC>1, <cell>1, <BSIC>1, <chann>1, <RSSI>1, <C1>1, <C2>1, <MCC>2, <MNC>2, <LAC>2, <cell>2, <BSIC>2, <chann>2, <RSSI>2, <C1>2, <C2>2, ...OKERROR+CME ERROR: <err>


+ + + + + + - - 3GPP TS 05.08

<MCC>(num)

<MNC>(num)

<LAC>(num)

<cell>(num)

BGS3 AT Command Set 8.6 AT^SMONC


Base station identity code2 digits, e.g. 3200 Not decoded

ARFCN (Absolute Frequency Channel Number)0 Not decoded. In this case, all remaining parameters related to the same chan-

nel are neither decoded. For example, a non-existing cell appears as follows:000,000,0000,0000,00,0,0,-,-

Received signal level of the BCCH carrier (0..63). The indicated value is composed of the measured value indBm plus an offset. This is in accordance with a formula specified in 3GPP TS 05.08

Coefficient for base station reselection, e.g. 30. In dedicated mode, under certain conditions the parameter can-not be updated. In such cases a '-' is presented.

Coefficient for base station reselection, e.g. 30. In dedicated mode, under certain conditions the parameter can-not be updated. In such cases a '-' is presented.

Note• To some extent, the cell monitoring commands AT^MONI, AT^MONP and AT^SMONC cover the same param-

eters. The receiving level, for example, can be queried with all three commands. Yet the resulting values maybe slightly different, even though obtained over a time period of a few seconds. This is quite normal and noth-ing to worry about, as the cell information is permanently updated.

<BSIC>(num)

<chann>(num)

<RSSI>(num)

<C1>(num)

<C2>(num)

BGS3 AT Command Set 8.7 AT^SMOND


8.7 AT^SMOND Cell Monitoring

The AT^SMOND execute command can be used to obtain status information of the service cell and up to six neigh-bour cells. The advantage over other cell monitoring commands is that AT^SMOND delivers more detailed infor-mation about the received signal strength.

Syntax


Serving cell information (comma-separated, no cr/lf included)<MCC>,<MNC>,<LAC>,<cell>,<BSIC>,<chann>,<RxLev>,<RxLev>Full,<RxLev>Sub,<RxQual>,<RxQual>Full,<RxQual>Sub,<Timeslot>If no serving cell is found, unavailable values are omitted:" ,,,,,,<RxLev>,,,0,,,0"

Neighbour cell information for neighbour cell 1 through 6 (comma-separated, no cr/lf included)<MCC>1,<MNC>1,<LAC>1,<cell>1,<BSIC>1,<chann>1,<RxLev>1, (these parameters repeated for neighbourcells 2 through 6 with no CR/LF): ... <MCC>6,<MNC>6,<LAC>6,<cell>6,<BSIC>6,<chann>6,<RxLev>6 An unavailable cell appears as follows: " ,,,,,,0"

Values for RSSI and BER (comma-separated, no cr/lf included)<RSSI>,<BER>

Mobile country code3 digits, e.g. 232000 Not decoded

Test Command

AT^SMOND=?Response(s)


Exec Command

AT^SMONDResponse(s)

^SMOND:[<sci>][, <nci>][, <TA>][, <rssiber>]OKERROR+CME ERROR: <err>


+ + + + + + - - 3GPP TS 05.08

<sci>(str)

<nci>(str)

<rssiber>(str)

<MCC>(num)



Mobile network code2 digits or 3 digits, e.g. 07 or 003000 Not decoded

Location area code4 hexadecimal digits, e.g. 4EED0000 Not decoded

Cell identifier4 hexadecimal digits, e.g. 4EAF0000 Not decodedFFFF Cell ID currently not available, e.g. because the cell ID information is not yet

read from the Sysinfo 3 transmitted by the base station.

Base station identity code2 digits, e.g. 3200 Not decoded

ARFCN (Absolute Frequency Channel Number)

Received signal level in dBm

Received signal quality as defined in GSM05.08

Assigned timeslot. If mobile is in idle mode, timeslot 0 (BCCH timeslot) will be indicated.0...8 Assigned timeslot

Timing advance for the serving cell, in bits.

Receive Level, with value 99 indicating "not known or not detectable"0...31 Signifies the RSSI range from -113dBm or less ("0") to -51dBm or greater

("31") in steps of -2dBm (e.g. "1" = -111 dBm, "2" = -109 dBm ..., "30" = -53dBm)

<MNC>(num)

<LAC>(num)

<cell>(num)

<BSIC>(num)

<chann>(num)

<RxLev>(num)

<RxQual>(num)

<Timeslot>(num)

<TA>(num)

<RSSI>(num)



Bit Error rate, with value 99 indicating "not known or not detectable"0...7 as RXQUAL values RXQUAL0 to RXQUAL7 in GSM 05.08 section 8.2.4

Notes• To some extent, the cell monitoring commands AT^SMOND, AT^MONI, AT^MONP and AT^SMONC cover the

same parameters. The receiving level, for example, can be queried with all three commands. Yet the resultingvalues may be slightly different, even though obtained over a time period of a few seconds. This is quite nor-mal and nothing to worry about, as the cell information is permanently updated.

• During a connection, not all of the neighbour cell information can be decoded. The following restrictions apply: - Information is updated only for neighbour cells that have already been visible at connection setup, and

continue to be included in the list of cells. - New neighbour cells added to the list, for example after handover, cannot be displayed until the connection

is released.

Example

<BER>(num)

at^smond Execute command ^SMOND:262,01,3008,6060,32,100,66,,,0,,,0,262,01,3008,DDD1,35,92,80,262,01,3008,,31,96,83,262,01,3008,BFBE,35,27,86,262,01,3008,,32,98,88,262,01,3008,BB44,32,90,89,262,01,3008,8307,31,22,93,2,23,99

Line breaks inserted for readability in print

BGS3 AT Command Set 8.8 AT^SFNUR


8.8 AT^SFNUR Select the fixed network user rate

The AT^SFNUR command specifies the Fixed Network User Rate (FNUR) parameter. This parameter is impor-tant only for mobile originated 14.4 kbit/s UDI calls (AT+CBST=75) and mobile terminated data calls if the bearercapability information element is delivered without data bearer service (see AT+CSNS and AT+CBST commands).

Changes are recommended only if a CSD call fails. The choice as to which of the values to use depends on theGSM network and the location. Users should be aware that even the same operator may apply varying FNURconfigurations in different regions.

The AT^SFNUR command has no effect on CSD connections controlled by the Internet Service commands. Ifneeded for the Internet Services the Fixed Network User Rate can be set in the connection profile. For detailssee AT^SICS, parameter <conParmValue> "fnur".

Syntax


0 not applicable1 9.6 kbit/s2(P) 14.4 kbit/s3 19.2 kbit/s4 28.8 kbit/s5 38.4 kbit/s6 48.0 kbit/s7 56.7 kbit/s8 64.0 kbit/s

Test Command

AT^SFNUR=?Response(s)

^SFNUR:(list of supported <value>s)OK

Read Command

AT^SFNUR?Response(s)

^SFNUR: <value>OKERROR+CME ERROR: <err>

Write Command

AT^SFNUR=<value>Response(s)



- + + + + + - -

<value>(num)

BGS3 AT Command Set 8.9 AT^MONI


8.9 AT^MONI Monitor idle mode and dedicated mode

The AT^MONI command supplies information of the serving/dedicated cell. There are two ways to retrieve theinformation: once on request by using the execute command or automatically every <period> seconds by usingthe write command. To stop the periodic presentation type "AT" or "at".

Syntax


Display period in seconds1...254

Notes• The two header lines (see Section 8.9.1, AT^MONI responses) are output after every ten data lines. • The length of following output lines exceeds 80 characters. Therefore a terminal program may draw a carriage

return on a screen. However, this is not part of the response. • The parameters LAC and cell are presented as hexadecimal digits, the remaining parameters are composed

of decimal digits. • If the radio cell changes during a connection, the parameters PWR, RXLev and C1 of the 'Serving Cell' part

cannot be updated under certain conditions. • If the BS supports frequency hopping during a connection, the dedicated channel (parameter chann) is not

stable. This mode is indicated by chann = 'h'. • To some extent, the cell monitoring command AT^SMONC covers the same parameters. The receiving level,

for example, can be queried with both commands. Yet the resulting values may be slightly different, eventhough obtained over a time period of a few seconds. This is quite normal and nothing to worry about, as thecell information is permanently updated.

• For compatibility with earlier products and to support legacy applications, any input character may be used tostop the output in certain cases (depending on the settings of AT+IPR and AT+CMUX).

Test Command

AT^MONI=?Response(s)

^MONI:(list of supported <period>s)OK

Exec Command

AT^MONIResponse(s)

See: Section 8.9.1, AT^MONI responsesOK

Write Command

AT^MONI=<period>Response(s)

See: Section 8.9.1, AT^MONI responsesOKERROR+CME ERROR: <err>


- + + + + + - -

<period>(num)



8.9.1 AT^MONI responses

ME is not connected:a) ME is camping on a cell and registered to the network:

b) ME is camping on a cell but not registered to the network (only emergency call allowed):

c) ME camping on a cell, but searching for a better cell (cell reselection):

d) ME is searching and could not (yet) find a suitable cell:

ME is connected (Call in progress):

Columns for Serving Cell:

Columns for Dedicated channel:

Serving Cell I Dedicated channelchann rs dBm MCC MNC LAC cell NCC BCC PWR RXLev C1 I chann TS timAdv PWR dBm Q ChMod1013 21 -71 001 01 1001 0103 7 7 33 -105 33 I No connection

Serving Cell I Dedicated channelchann rs dBm MCC MNC LAC cell NCC BCC PWR RXLev C1 I chann TS timAdv PWR dBm Q ChMod1013 21 -71 001 01 1001 0103 7 7 33 -105 33 I Limited Service

Serving Cell I Dedicated channelchann rs dBm MCC MNC LAC cell NCC BCC PWR RXLev C1 I chann TS timAdv PWR dBm Q ChMod1013 21 -71 001 01 1001 0103 7 7 33 -105 33 I Cell Reselection

Serving Cell I Dedicated channelchann rs dBm MCC MNC LAC cell NCC BCC PWR RXLev C1 I chann TS timAdv PWR dBm Q ChModSearching

Serving Cell I Dedicated channelchann rs dBm MCC MNC LAC cell NCC BCC PWR RXLev C1 I chann TS timAdv PWR dBm Q ChMod1013 19 -76 001 01 1001 0103 7 7 33 -105 33 I 1015 1 0 5 -76 0 S_HR

Column Descriptionchann ARFCN (Absolute Frequency Channel Number) of the BCCH carrierrs RSSI value 0 - 63 (RSSI = Received signal strength indication)dBm Receiving level of the BCCH carrier in dBmMCC Mobile Country Code (first part of the PLMN code)MNC Mobile Network Code (second part of the PLMN code)LAC Location area code, see notecell Cell IDNCC PLMN colour codeBCC Base station colour codePWR Maximal power level used on RACH channel in dBmRXLev Minimal receiving level (in dBm) to allow registrationC1 Coefficient for base station selection

Column Descriptionchann ARFCN (Absolute Frequency Channel Number) of the TCH carrier

Note: <chann> = h indicates frequency hopping.TS Timeslot number



8.9.2 Service states

Depending on the service state, an additional textual output is generated (refer also to the response examples): • 'Searching' - The MS is searching, but could not (yet) find a suitable cell. This output appears after restart of

the MS or after loss of coverage. • 'No connection' - The MS is camping on a cell and registered to the network. The service state is 'idle', i.e.

there is no connection established or a dedicated channel in use. • 'Cell Reselection' - The MS has not yet lost coverage but is searching for a better cell, since the cell reselec-

tion criterion is fulfilled. • 'Limited Service' - The MS is camping on a cell but not registered to the network. Only emergency calls are

allowed. The MS enters this state, for example, when - no SIM card is inserted, or PIN has not been given, - neither Home PLMN nor any other allowed PLMN are found, - registration request was not answered or denied by the network (use command AT+CREG to query the

registration status), - authentication failed.

timAdv Timing advance in bitsPWR Current power leveldBm Receiving level of the traffic channel carrier in dBmQ Receiving quality (0-7)ChMod Channel mode (--: Signalling, S_HR: Half rate, S_FR: Full rate, S_EFR: Enhanced

Full Rate, A_HR: AMR Half rate, A_FR: AMR Full rate)

Column Description

BGS3 AT Command Set 8.10 AT^MONP


8.10 AT^MONP Monitor neighbor cells

The AT^MONP supplies information of up to six neighbor cells. There are two ways to retrieve the information:once on request by using the execute command or automatically every <period> seconds by using the writecommand. To stop the periodic presentation type "AT" or "at".

Syntax


Display period in seconds1...254

Notes• During a connection some neighbor cell parameters cannot be updated. Therefore, the parameters MCC,

MNC, C1 and C2 equal zero until the connection is released. • To some extent, the cell monitoring command AT^SMONC covers the same parameters. The receiving level,

for example, can be queried with both commands. Yet the resulting values may be slightly different, eventhough obtained over a time period of a few seconds. This is quite normal and nothing to worry about, as thecell information is permanently updated.

• For compatibility with earlier products and to support legacy applications, any input character may be used tostop the output in certain cases (depending on the settings of AT+IPR and AT+CMUX).

8.10.1 AT^MONP responses

Response of AT^MONP (Example):

Test Command

AT^MONP=?Response(s)

^MONP:(list of supported <period>s)OK

Exec Command

AT^MONPResponse(s)

See: Section 8.10.1, AT^MONP responsesOK

Write Command

AT^MONP=<period>Response(s)

See: Section 8.10.1, AT^MONP responsesOKERROR+CME ERROR: <err>


- + + + + + - -

<period>(num)

BGS3 AT Command Set 8.10 AT^MONP


chann rs dBm MCC MNC BCC C1 C2 653 26 -84 262 07 0 22 22 660 20 -90 262 07 3 16 16 687 19 -91 262 07 1 15 15 678 14 -96 262 07 3 10 10 671 14 -96 262 07 1 10 10 643 10 -100 262 07 7 6 6

Column DescriptionChann ARFCN (Absolute Radio Frequency Channel Number) of the BCCH carrierrs RSSI value 0 - 63 (RSSI = Received signal strength indication)dBm Receiving level in dBmMCC Mobile Country Code (first part of the PLMN code)MNC Mobile Network Code (second part of the PLMN code)BCC Base Station colour codeC1 cell selection criterionC2 cell reselection criterion

BGS3 AT Command Set 8.11 AT^SMONG


8.11 AT^SMONG Packet Data Monitor

The AT^SMONG command supplies packet data specific cell information. There are two ways to retrieve the infor-mation: once on request by using the execute command or automatically every <period> seconds by using thewrite command. To stop the periodic presentation type "AT" or "at".

Syntax


1 Cell Info Table

Display period in secondsIf <period> is omitted the cell data will be presented only once on a single line (as if Execute command wasissued).If <period> is given, the cell data will be listed repeatedly on 10 data lines. Every 10th data line is followed bythe header, simply to repeat the column titles.1...100

Test Command

AT^SMONG=?Response(s)

^SMONG:(list of supported <table>s), (list of supported <period>s)OKERROR+CME ERROR: <err>

Exec Command

AT^SMONGResponse(s)

GPRS MonitorCell Info Table (see: Section 8.11.1, AT^SMONG Cell Info Table)OKERROR+CME ERROR: <err>

Write Command

AT^SMONG=<table>[, <period>]Response(s)

^SMONG: GPRS MonitorCell Info Table (see: Section 8.11.1, AT^SMONG Cell Info Table)OKERROR+CME ERROR: <err>


+ + + + + + - -

<table>(num)

<period>(num)

BGS3 AT Command Set 8.11 AT^SMONG


Note• For compatibility with earlier products and to support legacy applications, often any input character will stop

the periodic output of the write command. But since this applies only in certain cases (depending on the set-tings of AT+IPR and AT+CMUX), it is recommended to always use "at" or "AT".

8.11.1 AT^SMONG Cell Info Table

Example output for AT^SMONG:

Columns of the cell info table:

GPRS MonitorBCCH G PBCCH PAT MCC MNC NOM TA RAC # Cell #0637 1 - 4 234 05 2 00 0B

Column DescriptionBCCH ARFCN of BCCH carrierG GPRS status:

0 GPRS not available in currently used cell1 GPRS available in currently used cell2 GPRS attachedNote: If the network uses the PBCCH, the correct value can only be displayed if the BGS3 is attached.

PBCCH If PBCCH is present, indication of ARFCN, else ''-'' or if Frequency Hopping is used ''H''PAT Priority Access Threshold (GSM Rec. 04.08 / 10.5.2.37b)

0 Packet access is not allowed in the cell1 Spare, shall be interpreted as "000" (packet access not allowed)2 Spare, shall be interpreted as "000" (packet access not allowed)3 Packet access is allowed for priority level 14 Packet access is allowed for priority level 1 to 2

MCC Mobile Country CodeMNC Mobile Network CodeNOM Network Operation Mode (1...3)TA Timing Advance ValueRAC Routing Area Code (as hexadecimal value)

BGS3 AT Command Set 8.12 AT^SALS


8.12 AT^SALS Alternate Line Service

The AT^SALS command is designed to support Alternate Line Service. This allows the subscriber to use twovoice numbers on the same SIM card (service requires a dual line SIM card). The write command enables or disables the presentation of <view> and specifies the <line> used for outgoingcalls. The read command returns the presentation mode of <view> and the currently selected <line>.

Syntax

Unsolicited Result CodeIf switched on with <view>=1: ^SALS: <line>

Indicates the line used by an incoming call.


Controls the presentation mode of the URC "^SALS" which indicates the line number used by an incoming call: 0(&F)(P) Disables indication of the called line 1 Enables indication of the called line

Selects the line to be used for outgoing calls. Setting is global for the ME and non volatile. 1(&F)(D) ALS Line 1 2 ALS Line 2

Note• If a non ALS SIM is inserted, the <line> will be reset to line 1.

Test Command

AT^SALS=?Response(s)

^SALS:(list of supported <view>s), (list of supported <line>s)OK

Read Command

AT^SALS?Response(s)

^SALS: <view>, <line>OKERROR

Write Command

AT^SALS=<view>[, <line>]Response(s)

OKERROR


+ + + + + + - -

<view>(num)

<line>(num)

BGS3 AT Command Set 8.12 AT^SALS


Example

AT^SALS=1,1 Line 1 has been selected for outgoing calls. "^SALS" URC is enabled.RING You receive a notification that you have an incoming call on line 2.^SALS: 2

BGS3 AT Command Set 8.13 AT^SHOM


8.13 AT^SHOM Display Homezone

The AT^SHOM returns the homezone state. The result is valid only, if network registration state <stat> is 1 (reg-istered) (see AT+CREG). The feature is available only for supported network operators (O2 Germany) and requires a suitable SIM card. Ifthe homezone feature is not supported by the network operator or SIM card, result is always 0.

Syntax


0 ME is out of Homezone and Cityzone1 ME is within the Homezone2 ME is within the Cityzone

Test Command

AT^SHOM=?Response(s)

OK

Exec Command

AT^SHOMResponse(s)

^SHOM: <homezonestate>OKERROR+CME ERROR: <err>


+ + + + + + - -

<homezonestate>(num)

BGS3 AT Command Set 8.14 AT^SPLM


8.14 AT^SPLM Read the PLMN list

The AT^SPLM execute command returns the list of operators from the ME. Each operator code <numeric> thathas an alphanumeric equivalent <alpha> in the ME memory is returned. The list is sorted by operator codes.See also GSM 07.07: AT+COPN, AT+COPS

Syntax


Operator in numeric form; GSM location area identification number

Operator in long alphanumeric format; can contain up to 26 characters

Test Command

AT^SPLM=?Response(s)

OKIf error is related to ME functionality:ERROR+CME ERROR: <err>

Exec Command

AT^SPLMResponse(s)

^SPLM:<numeric>, long <alpha>^SPLM:[... ]OKIf error is related to ME functionality:ERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07

<numeric>(str)

<alpha>(str)

BGS3 AT Command Set 8.15 AT+CPOL


8.15 AT+CPOL Preferred Operator List

The AT+CPOL read command returns the list of the preferred operators. The AT+CPOL write command allows toedit the list of the preferred operators. If <index> is given but <operator> is left out, the entry is deleted.

Syntax


The order number of the operator in the SIM preferred operator list.

2 Numeric format

Operator in numeric format (GSM Location Area Identification number which consists of a 3-digit country codeplus a 2- or 3-digit network code).

Test Command

AT+CPOL=?Response(s)

+CPOL:(list of supported <index>s), (list of supported <format>s)OKERROR+CME ERROR: <err>

Read Command

AT+CPOL?Response(s)

+CPOL: <index>, <format>, <operator>+CPOL: ...OKERROR+CME ERROR: <err>

Write Command

AT+CPOL=<index>[, <format>, <operator>]Response(s)



+ + + + + + - - GSM 07.07

<index>(num)

<format>(num)

<operator>(str)

BGS3 AT Command Set 9. Supplementary Service Commands


9. Supplementary Service Commands

The AT Commands described in this chapter are related to the Supplementary Services offered by the GSM net-work.

9.1 AT+CACM Accumulated call meter (ACM) reset or query

Syntax

Command DescriptionThe read command returns the current ACM value. The write command resets the Advice of Charge related to the accumulated call meter (ACM) value in SIM fileEF(ACM). ACM contains the total number of home units for both the current and preceding calls.


Three bytes of the current ACM value in hexadecimal format (e.g. "00001E" indicates decimal value 30) 000000- FFFFFF.

SIM PIN2

Test Command

AT+CACM=?Response(s)

OK

Read Command

AT+CACM?Response(s)

+CACM: <acm>OKERROR+CME ERROR: <err>

Write Command

AT+CACM=[<passwd>]Response(s)



+ + + + + + - - GSM 07.07

<acm>(str)

<passwd>(str)

BGS3 AT Command Set 9.2 AT^SACM


9.2 AT^SACM Advice of charge and query of ACM and ACMmax

Syntax

Unsolicited Result Code+CCCM: <ccm>

When activated, an unsolicited result code is sent when the CCM value changes, but not more often than every10 seconds.

Command DescriptionThe execute command can be used to query the current mode of the Advice of Charge supplementary service,the SIM values of the accumulated call meter (ACM) and accumulated call meter maximum (ACMmax). The write command enables or disables the presentation of unsolicited result codes to report the call charges.


[0](&F) suppress unsolicited result code1 display unsolicited result code

Three bytes of the current ACM value in hexadecimal format (e.g. "00001E" indicates decimal value 30) 000000-FFFFFF

Three bytes of the max. ACM value in hexadecimal format (e.g. "00001E" indicates decimal value 30) 000000disable ACMmax feature 000001-FFFFFF

Test Command

AT^SACM=?Response(s)

^SACM:(list of supported <n>s)OK

Exec Command

AT^SACMResponse(s)

^SACM: <n>, <acm>, <acmMax>OKERROR+CME ERROR: <err>

Write Command

AT^SACM=<n>Response(s)



+ + + + + + - -

<n>(num)(&W)(&V)

<acm>(str)(&V)

<acmMax>(str)(&V)

BGS3 AT Command Set 9.2 AT^SACM


Three bytes of the current CCM value in hexadecimal format (e.g. "00001E" indicates decimal value 30); bytesare coded in the same way as ACMmax value in the SIM 000000-FFFFFF

Notes• When you power down or reset the ME with AT+CFUN=1,1 the URC presentation mode will be reset to its

default. To benefit from the URC it is recommended to have the setting included in the user profile saved withAT&W, or to select <n>=1 every time you reboot the ME.

• See also GSM07.07: AT+CACM, AT+CAMM, AT+CAOC.

<ccm>(str)

BGS3 AT Command Set 9.3 AT+CAMM


9.3 AT+CAMM Accumulated call meter maximum (ACMmax) set or query

Syntax

Command DescriptionThe read command returns the current ACMmax value. The write command sets the Advice of Charge related to the accumulated call meter maximum value in SIM fileEF (ACMmax). ACMmax contains the maximum number of home units allowed to be consumed by the sub-scriber.


Three bytes of the max. ACM value in hexadecimal format (e.g. "00001E" indicates decimal value 30) 000000disable ACMmax feature 000001-FFFFFF.

SIM PIN2

Test Command

AT+CAMM=?Response(s)

OK

Read Command

AT+CAMM?Response(s)

+CAMM: <acmmax>OKERROR+CME ERROR: <err>

Write Command

AT+CAMM=<acmmax>[, <passwd>]Response(s)



+ + + + + + - - GSM 07.07

<acmmax>(str)

<passwd>(str)

BGS3 AT Command Set 9.4 AT+CAOC


9.4 AT+CAOC Advice of Charge information

Syntax

Command DescriptionExecute command returns the current call meter value. The write command sets the Advice of Charge supplementary service function mode.


0 query CCM value

Three bytes of the current CCM value in hexadecimal format (e.g. "00001E" indicates decimal value 30); bytesare similarly coded as ACMmax value in the SIM 000000-FFFFFF.

Test Command

AT+CAOC=?Response(s)

+CAOC: (list of supported<mode>s)OK

Read Command

AT+CAOC?Response(s)

+CAOC: <mode>OK

Exec Command

AT+CAOCResponse(s)

ERROR+CME ERROR: <err>If <mode>=0, TA returns the current call meter value:+CAOC: <ccm>OK

Write Command

AT+CAOC=[<mode>]Response(s)

ERROR+CME ERROR: <err>If <mode>=0, TA returns the current call meter value.OK


+ + + + + + - - GSM 07.07

<mode>(num)(&V)

<ccm>(str)

BGS3 AT Command Set 9.5 AT+CCUG


9.5 AT+CCUG Closed User Group

Syntax

Command DescriptionThe Test command returns the supported parameters. The Read command returns if the Explicit CUG invocation is activated (in parameter <n>), which CUG <index>is chosen, and if Preferential Group or Outgoing Access is suppressed (in parameter <info>). The write command serves to activate or deactivate the explicit CUG invocation, to set the desired index, and tospecify if Preferential Group or Outgoing Access shall be suppressed.


explicit CUG invocation options0(D) Deactivate explicit CUG invocation 1 Activate explicit CUG invocation

0-9 explicit selection of CUG index10(D) No index (preferred CUG taken from subscriber data)

Test Command

AT+CCUG=?Response(s)

list of supported <n>, range of supported <index>, range of supported <info>OKERROR+CME ERROR: <err>

Read Command

AT+CCUG?Response(s)

+CCUG:<n>, <index>, <info>OKERROR+CME ERROR: <err>

Write Command

AT+CCUG=[[<n>][, <index>][, <info>]]Response(s)



+ + + + + + - - GSM 07.07, GSM 02.85, GSM 03.85, GSM 04.85

<n>(num)

<index>(num)

BGS3 AT Command Set 9.5 AT+CCUG


state of the call0(D) no information1 suppress outgoing access2 suppress preferential CUG3 Suppress preferential CUG and Outgoing Access.

Notes• The active settings for omitted parameters are retained without changes. • Explicit CUG invocation means that at each call setup, CUG information is added to the called number. • Upon delivery, settings are predefined with

<n>=0, <index>=10, <info>=0. These delivery defaults cannot be recalled automatically.

• When starting a call with ATD, Parameter 'G' or 'g' of command ATD will have no effect if the option selectedfor this single call is identical to the option already selected with AT+CCUG.

• Current settings are saved in the ME automatically. • ATZ or AT&F do not influence the current settings. • some combinations of parameters may lead to rejection of CUG calls by the network. For more information,

please consult GSM 04.85

<info>(num)

BGS3 AT Command Set 9.6 AT+CCFC


9.6 AT+CCFC Call forwarding number and conditions control

AT+CCFC controls the call forwarding supplementary service. Registration, erasure, activation, deactivation andstatus query are supported.

Syntax


Reason for call forwarding 0 unconditional1 mobile busy2 no reply3 not reachable4 all call forwarding (includes reasons 0, 1, 2 and 3)5 all conditional call forwarding (includes reasons 1, 2 and 3)

Network operation to be performed for Supplementary service "call forwarding"0 disable call forwarding (disable service)1 enable call forwarding (enable service)2 query status of call forwarding (query service status)3 register <number> and activate call forwarding (register service)4 erase <number> and deactivate call forwarding (erase service)

Test Command

AT+CCFC=?Response(s)

+CCFC:(list/range of supported <reason>s) OK

Write Command

AT+CCFC=<reason>, <mode>[, <number>[, <type>[, <class>[, <time>]]]]Response(s)

If <mode> is not equal 2 and command successful: OKIf <mode>= 2, <reason> is not equal 2 and command successful: +CCFC: <status>, <class>[, <number>, <type>]OKIf <mode>= 2, <reason>= 2 and command successful: +CCFC: <status>, <class>[, <number>, <type>, <time>]OKIf error is related to ME functionality ERROR+CME ERROR: <err>



<reason>(num)

<mode>(num)



String type phone number of forwarding address in format specified by <type>. If you select <mode>= 3, thephone <number> will be registered in the network. This allows you to disable / enable CF to the same destinationwithout the need to enter the phone number once again. Depending on the services offered by the provider theregistration may be mandatory before CF can be used. The number remains registered in the network until youregister another number or erase it using <mode> = 4.

Type of address octect145 dialing string <number> includes international access code character '+'129 otherwise

Integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication ser-vice or bearer service group as defined in "GSM 02.04" 1 voice2 data

<class> 2 (data) comprises all those <class> values between 16 and 128, thatare supported both by the network and the MS. This means, a setting made for<class> 2 applies to all remaining data classes (if supported). In addition, youcan assign a different setting to a specific class. For example, you can activateCall Forwarding for all data classes, but deactivate it for a specific data class.

4 fax8 SMS16 data circuit sync32 data circuit async64 dedicated packet access128 dedicated PAD access1...[7]...255 combination of some of the above classes. For example, the default setting 7

represents the sum of the integers 1, 2 and 4 (CF for voice, data and fax). Thevalue 255 covers all classes. If the <class> parameter is omitted, the defaultvalue 7 is used.

5...[20]...30 Time to wait before call is forwarded, rounded to a multiple of 5 sec. (only for<reason>=no reply)

0 Call Forwarding not active1 Call Forwarding active

Notes• You can register, disable, enable and erase <reason> 4 and 5 as described above. However, querying the

status of <reason> 4 and 5 with AT+CCFC will result in an error ("+CME ERROR: operation not supported").As an alternative, you may use the ATD command followed by *'# codes to check the status of these two rea-sons. See Star-Hash (*#) Network Commands for a complete list of *# GSM codes. See also examplesbelow.

• Most networks will not permit registration of new parameters for conditional call forwarding (reasons 1,2,3,5)while unconditional call forwarding is enabled.

<number>(str)

<type>(num)

<class>(num)

<time>(num)

<status>(num)



• The AT+CCFC command offers a broad range of call forwarding options according to the GSM specifications.However, when you attempt to set a call forwarding option which is not provisioned or not yet subscribed to,the setting will not take effect regardless of the response returned. The responses in these cases vary withthe network (for example "OK", "Operation not allowed", "Operation not supported" etc.). To make sure checkthe call forwarding status with <mode>=2.

• Some networks may choose to have certain call forwarding condtions permanently enabled (e.g. forwardingto a mailbox if the mobile is not reachable). In this case, erasure or deactivation of call forwarding for theseconditions will not be successful, even if the CCFC request is answered with response "OK".

• The command has been implemented with the full set of <class> parameters according to GSM 07.07. Foractual applicability of SS "call forwarding" to a specific service or service group (a specific <class> value)please consult table A.1 of GSM 02.04.

• There is currently no release of GSM standard "GSM 02.04", in which the "Call Forwarding" SupplementaryService is defined as applicable to SMS services.

Example

Please note that when you configure or query call forwarding without specifying any classes, the settings willrefer to classes 1, 2 and 4 only (=default). The handling of classes is equivalent to AT+CLCK. • To register the destination number for unconditional call forwarding (CFU):

The destination number will be registered for voice, data and fax services (default <class> 7).In most networks, the registration will also cause call forwarding to be activated for these <class> values.

• To query the status of CFU without specifying <class>:

• To deactivate CFU without specifying <class>:

To check whether CFU was successfully deactivated (note that the destination number remains registered inthe network when you disable CFU):

• To erase the registered CFU destination number:

Now, when you check the status, no destination number will be indicated:

at+ccfc=0,3,"+493012345678",145 OK

at+ccfc=0,2 +CCFC: 1,1,"+493012345678",145 +CCFC: 1,2,"+493012345678",145 +CCFC: 1,4,"+493012345678",145 OK

at+ccfc=0,0 OK

at+ccfc=0,2 +CCFC: 0,1,"+493012345678",145 +CCFC: 0,2,"+493012345678",145 +CCFC: 0,4,"+493012345678",145 OK

at+ccfc=0,4 OK

at+ccfc=0,2 +CCFC: 0,1 +CCFC: 0,2 +CCFC: 0,4 OK



• To query the status of CFU for all classes:

• <reason> 4 or 5 cannot be used to query the status of all call forwarding reasons (see also notes above):

at+ccfc=0,2,,,255 +CCFC: 0,1 +CCFC: 0,2 +CCFC: 0,4 +CCFC: 0,8 +CCFC: 0,16 +CCFC: 0,32 +CCFC: 0,64 +CCFC: 0,128 OK

at+ccfc=4,2 +CME ERROR: operation not supported at+ccfc=5,2 +CME ERROR: operation not supported

BGS3 AT Command Set 9.7 AT+CCWA


9.7 AT+CCWA Call Waiting

The AT+CCWA write command controls the "Call Waiting" supplementary service according to GSM 02.83. Acti-vation, deactivation and status query are supported. The read command returns the current value of <n>.

Syntax


URC 1

Indication of a call that is currently waiting and can be accepted.+CCWA: <calling number>, <type of number>, <class>, , <CLI validity>

If <n>=1 and the call waiting supplementary service is enabled in the network, URC "+CCWA" indicates a wait-ing call to the TE. It appears while the waiting call is still ringing.

URC 2

Indication of a call that has been waiting.^SCWA:

If <n>=1 and the call waiting supplementary service is enabled in the network, this URC indicates that a wait-ing call rang when the ME was in online mode during a CSD call, but the calling party hung up before the MEwent back to command mode.

Test Command

AT+CCWA=?Response(s)

+CCWA:(list of supported <n>s) OK

Read Command

AT+CCWA?Response(s)

+CCWA:<n> OK

Write Command

AT+CCWA=[[<n>][, <mode>][, <class>]]Response(s)

If <mode> is not equal 2 and command successful: OKIf <mode>= 2 and command successful: +CCWA: <status>, <class>[+CCWA: <status>, <class>][+CCWA: ...]OKIf error is related to ME functionality +CME ERROR: <err>






Switch URCs "+CCWA" and "^SCWA" for call waiting on/off0 Disable display of URCs "+CCWA" and "^SCWA" 1 Enable display of URCs "+CCWA" and "^SCWA"

Network operation to be performed for Supplementary service call waiting0 Disable call waiting (disable service)1 Enable call waiting (enable service)2 Query status of call waiting (query service status)

Integer or sum of integers each representing a class of information, i.e. a bearer service, telecommunication ser-vice or bearer service group as defined in "GSM 02.04".In the write command, parameter <class> specifies the class of the active call during which an incoming callof any class is to be regarded as a waiting call.In URC "+CCWA: <calling number>, <type of number>, <class>, , <CLI validity>", parameter<class> specifies the class of the waiting call. 1 Voice2 Data

<class> 2 (data) comprises all those <class> values between 16 and 128, thatare supported both by the network and the MS. This means, a setting made for<class> 2 applies to all remaining data classes (if supported). In addition, youcan assign a different setting to a specific class. For example, you can activatecall waiting for all data classes, but deactivate it for a specific data class.

4 Fax[7] Voice, data and fax (1+2+4)16 Data circuit sync32 Data circuit async64 Dedicated packet access128 Dedicated PAD access1...[7]...255 Combination of some of the above classes. For example, the default setting 7

represents the sum of the integers 1, 2 and 4 (CF for voice, data and fax). Thevalue 255 covers all classes. If parameter "class"is omitted, the default value 7is used.

0 Call waiting service is not active1 Call waiting service is active

Phone number of waiting caller in the format specified by parameter <type of number>.

Type of address octet in integer format (refer to GSM 04.08, subclause 10.5.4.7) 145 <calling number> includes international access code character '+'

<n>(num)

<mode>(num)

<class>(num)

<status>(num)

<calling number>(str)

<type of number>(num)



128 number restricted129 Otherwise

0 CLI valid 1 CLI has been withheld 2 CLI is not available

Notes• If the active call is a CSD call, and a waiting call is received, then the ME produces a BREAK while still in

online mode, and displays - the +CCWA URC (as above) when the ME goes back to command mode while the waiting call is still active

and can be accepted; - or the ^SCWA URC (as above) when the ME goes back to command mode after the waiting call has

ended. • With the AT+CHLD command, it is possible to establish a multiparty call or to set the active voice call on hold

and then accept a waiting voice call (not possible with fax and data call). See also AT+CHLD • Users should be aware that if call waiting is activated (<mode>=1), the presentation of URCs needs to be

enabled, too (<n>=1). Otherwise, on the one hand, a waiting caller would be kept waiting due to lack of BUSY signals, while, on theother hand, the waiting call would not be indicated to the called party.

• The AT+CCWA command offers a broad range of options according to the GSM specifications. However,when you attempt to enable call waiting for a <class> for which the service is not provisioned or not sup-ported , the setting will not take effect regardless of the response returned. The responses in these cases varywith the network (for example "OK", "Operation not allowed", "Operation not supported" etc.). To make surecheck the current call waiting settings with <mode>=2.

• The AT+CCWA command has been implemented with the full set of <class> parameters according toGSM 07.07. For actual applicability of SS call waiting to a specific service or service group (a specific<class> value) please consult table A.1 of GSM 02.04

• Despite the specifications stated in GSM 02.04 call waiting is not handled uniformly among all networks: GSM 02.04, Annex A, provides the following specification: "The applicability of call waiting refers to the telecommunication service of the active call and not of the waitingcall. The incoming, waiting, call may be of any kind." Nevertheless, networks do differ on the actual imple-mentation of the service. For example, the activation of call waiting for <class> 4, "fax", causes some net-works to send a call waiting indication if a call "of any kind" comes in during an active fax call, but others may(with the same settings active) indicate a waiting fax call during any kind of active call. Thus, the only reliableway to receive or prevent a call waiting indication under any circumstances and in any network, is to activateor deactivate call waiting for all tele- and bearer services (<class> 255).

<CLI validity>(num)



ExamplesEXAMPLE 1

Parameter <n>

EXAMPLE 2

Parameter <mode>

EXAMPLE 3

Parameter <class>

at+ccwa=1 To enable the presentation of the URC OK

at+ccwa=,1 To activate the supplementary service in the network for voice, data,and fax calls (default classes). Note that parameter <n> is left out. In this case, the current value of <n>will be retained.

OK at+ccwa=,2 To query the network status of call waiting for default classes at+ccwa=1,1 Call Waiting is activated during voice calls. at+ccwa=1,2 Call Waiting is activated during data calls. at+ccwa=1,4 Call Waiting is activated during fax calls. OK

AT+CCWA=,0,1 To deactivate call waiting for voice calls. OK

BGS3 AT Command Set 9.8 AT+CHLD


9.8 AT+CHLD Call Hold and Multiparty

The AT+CHLD command controls the Supplementary Services Call Hold and Multiparty. Calls can be put on hold,recovered, released and added to a conversation.Like for all Supplementary Services, the availability and detailed functionality of Call Hold and Multiparty servicesdepends on the configuration of the GSM network. The BGS3 can only request the service, but the networkdecides whether and how the request will be answered.

Syntax


0 Release all held calls or set User Determined User Busy (UDUB) for a waitingcall: • If a call is waiting, release the waiting call. The calling party will receive a

"BUSY" indication (Supplementary Service User Determined User Busy"UDUB")

• Otherwise, terminate all held calls (if any). 1 Terminate all active calls (if any) and accept "the other call" as the active call:

• If a call is waiting, the waiting call will be accepted. • Otherwise, if a held call is present, the held call becomes active.

1X Terminate a specific call X. The call may be active, held or waiting. The remoteparty of the terminated call will receive a "NO CARRIER" indication. Parameter X is the call number <idx> in the list of current calls indicated byAT+CLCC. Instead of AT+CLCC, the AT^SLCC command with parameter <idx>can be used.

2 Place all active calls on hold (if any) and accept "the other call" as the activecall: • If a call is waiting, the waiting call will be accepted. • Otherwise, if a held call is present, the held call becomes active.

2X Place all active calls on hold except call X.Parameter X is the call number <idx> in the list of current calls indicated byAT+CLCC. Instead of AT+CLCC, the AT^SLCC command with parameter <idx>can be used.

3 Add a held call to the active calls in order to set up a conference (multiparty)call.

Test Command

AT+CHLD=?Response(s)

+CHLD: (list of supported <n>s)OK

Write Command

AT+CHLD=[<n>]Response(s)



+ + + + + + - - GSM 07.07

<n>(num)

BGS3 AT Command Set 9.8 AT+CHLD


Notes• The AT+CHLD command offers a broad range of options according to the GSM specifications. However, if you

attempt to invoke an option which is not provisioned by the network, or not subscribed to, invocation of thisoption will fail. The responses in these cases may vary with the network (for example "Operation not allowed","Operation not supported" etc.).

• The handling of the supplementary service Call hold and Multiparty varies with the types of calls. This isbecause only voice calls can be put on hold, while data or fax calls cannot. The following procedures apply:With AT+CHLD=2 the user can simultaneously place a voice call on hold and accept another waiting voice,data or fax call. If the waiting call is a data or fax call, it is also possible to put the voice call on hold. To switchback from the active data or fax call to the held voice call the active call must be terminated with AT+CHLD=1.If all active and held calls are voice calls it is possible to switch back and forth with AT+CHLD=2.

• In conflict situations, e.g. when a waiting call comes while there are already held calls, the above proceduresapply to the waiting call only. For example, <n>=0 rejects the waiting call, but does not affect the held calls.

• See also the AT+CCWA command for details on how to display waiting calls.

Example

^SYSSTARTat+cpin="9999"OK+CREG: 2+CREG: 1,"0145","0016" The mobile is now registered.at+ccwa=1,1,1 You activate the indication of waiting calls during

voice calls.OKatd"1234567"; You make a voice call.OK+CCWA: "+491791292364",145,32,,0 You receive a URC indicating a waiting data call.at+chld=2 You put the voice call on hold.CONNECT 9600/RLP The data connection is set up.hello+++ With ''+++'' you go in command mode.OKat+clcc You interrogate the status of all established calls.+CLCC: 1,0,1,0,0,"03038639268",129+CLCC: 2,1,0,1,0,"+491791292364",145OKat+chld=1 The active data call is terminated and the held voice

call becomes active.OKat+clcc+CLCC: 1,0,0,0,0,"03038639268",129OK

BGS3 AT Command Set 9.9 AT+CLIP


9.9 AT+CLIP Calling Line Identification Presentation

This command refers to the GSM supplementary service CLIP (Calling Line Identification Presentation) thatenables a called subscriber to get the calling line identity (CLI) of the calling party when receiving a mobile ter-minated call. The AT+CLIP write command enables or disables the presentation of the CLI at the TE. It has no effect on theexecution of the supplementary service CLIP in the network. The AT+CLIP read command gives the status of <n>, and also triggers an interrogation of the provision statusof the CLIP service according to GSM 02.81 (given in <m>). If no SIM card is available or the SIM-PIN is notentered, the command response is "ERROR".

Syntax

Unsolicited Result Code+CLIP: <number>, <type>[, , [, [<alpha>][, <CLI validity>]]]

When CLIP is enabled at the TE (and is permitted by the calling subscriber), this URC is delivered after every"RING" or "+CRING" URC when a mobile terminated call occurs.


[0](&F) Suppress unsolicited result codes1 Display unsolicited result codes

0 CLIP not provisioned1 CLIP provisioned2 Unknown

Test Command

AT+CLIP=?Response(s)

+CLIP: (list of supported<n>s)OK

Read Command

AT+CLIP?Response(s)

+CLIP: <n>, <m>OKERROR+CME ERROR: <err>

Write Command

AT+CLIP=<n>Response(s)



± + + + + + - - GSM 07.07, GSM 02.81

<n>(num)(&W)(&V)

<m>(num)(&V)

BGS3 AT Command Set 9.9 AT+CLIP


String type phone number of calling address in format specified by <type>.

Type of address octet in integer format; 145 when dialing string includes international access code character"+",128 when number is restricted otherwise 129.

String type alphanumeric representation of <number> corresponding to the entry found in phonebook; usedcharacter set is the one selected with AT+CSCS.

0 CLI valid1 CLI has been withheld by the originator.2 CLI is not available due to interworking problems or limitations of originating

network. <number> shall be an empty string ("") and <type> value will not besignificant.

When CLI is not available ( <CLI validity>=2), <number> shall be an empty string ("") and <type> valuewill not be significant. Nevertheless, TA shall return the recommended value 128 for <type> (TON/NPIunknown in accordance with GSM 04.08 subclause 10.5.4.7). When CLI has been withheld by the originator, (<CLI validity>=1) and the CLIP is provisioned with the"override category" option (refer GSM 02.81 and GSM 03.81), <number> and <type> is provided. Otherwise,TA shall return the same setting for <number> and <type> as if the CLI was not available.

<number>(str)

<type>(num)

<alpha>(str)

<CLI validity>(num)

BGS3 AT Command Set 9.10 AT+CLIR


9.10 AT+CLIR Calling Line Identification Restriction

The AT+CLIR command refers to the GSM supplementary service CLIR (Calling Line Identification Restriction).

Syntax


Parameter shows the settings for outgoing calls:[0](P) Presentation indicator is used according to the subscription of the CLIR service1 CLIR invocation2 CLIR suppression

Parameter shows the subscriber CLIR service status in the network:0 CLIR not provisioned1 CLIR provisioned in permanent mode2 Unknown (e.g. no network, etc.)3 CLIR temporary mode presentation restricted4 CLIR temporary mode presentation allowed

Note• The settings made with AT+CLIR=1 or AT+CLIR=2 are used for all outgoing calls until the ME is switched off

or AT+CLIR=0 is used.

Test Command

AT+CLIR=?Response(s)

+CLIR: (list of supported <n>s)OK

Read Command

AT+CLIR?Response(s)

+CLIR<n>, <m>OKERROR+CME ERROR: <err>

Write Command

AT+CLIR=[<n>]Response(s)



+ + + + + + - - GSM 07.07

<n>(num)

<m>(num)

BGS3 AT Command Set 9.11 AT+COLP


9.11 AT+COLP Connected Line Identification Presentation

This command refers to the GSM supplementary service COLP (Connected Line Identification Presentation) thatenables a calling subscriber to get the connected line identity (COL) of the called party after setting up a mobileoriginated call. The command enables or disables the presentation of the COL at the TE. It has no effect on theexecution of the supplementary service COLR in the network.

Syntax

Unsolicited Result CodeCall response format: +COLP: <number>, <type>


0 Disable - suppress unsolicited result codes 1 Enable - display unsolicited result codes

0 COLP not provisioned (no presentation)1 COLP provisioned2 Unknown

String type phone number of connected address in format specified by <type>

Test Command

AT+COLP=?Response(s)

+COLP:(list of supported <n>s)OK

Read Command

AT+COLP?Response(s)

+COLP: <n>, <m>OKERROR+CME ERROR: <err>

Write Command

AT+COLP=[<n>]Response(s)



+ + + + + + - - GSM 07.07

<n>(num)

<m>(num)

<number>(str)

BGS3 AT Command Set 9.11 AT+COLP


Type of address octet in integer format; 145 when dialling string includes international access code character"+", otherwise 129.

<type>(num)

BGS3 AT Command Set 9.12 AT+CPUC


9.12 AT+CPUC Price per unit and currency table

Syntax

Command DescriptionRead command returns the current parameters of PUC. Write command sets the parameters of Advice of Charge related price per unit and currency table. SIM PIN2 isusually required to set the parameters.


Three-character currency code (e.g. "GBP", "EUR"). If the currency name is longer than three characters, allcharacters will be cut off after the third position. Before they are written to the SIM Card, these characters areconverted to the standard GSM alphabet.

Price per unit; dot is used as a decimal separator (e.g. "2.66"). The length is limited to 20 characters. If the stringlength is exceeded, the command is terminated with an error. This string may only contain digits and a dot. Lead-ing zeros are removed from the string. The minimum and maximum value are determined by the structure of theSIM-PUCT file. The maximum price per unit value is 999 999 999.00. When successfully entered, this value isrounded to maximum accuracy.Note: Due to storage in mantisse (range 0-4095) and exponent (-7 to 7) it is possible that rounding errors occur.

SIM PIN2. String parameter which can contain any combination of digits. The maximum string length is limitedto 8 digits. If this value is exceeded, the command terminates with an error message. If the PIN2 is incorrect, aCME error (+CME ERROR: incorrect password) is output.

Test Command

AT+CPUC=?Response(s)

OK

Read Command

AT+CPUC?Response(s)

+CPUC: <currency>, <ppu>OKERROR+CME ERROR: <err>

Write Command

AT+CPUC=<currency>, <ppu>[, <passwd>]Response(s)



+ + + + + + - - GSM 07.07

<currency>(str)(+CSCS)

<ppu>(str)

<passwd>(str)

BGS3 AT Command Set 9.12 AT+CPUC


Example

To change currency and/or price per unit you have two ways:

You can enter PIN2 along with the AT+CPUC command:

Alternatively, you can first use the AT+CPIN2 command to enter PIN2. When you execute the AT+CPUC com-mand, subsequently, take into account that PIN2 authentication expires after 300ms (see notes in AT+CPIN2).

AT+CPUC="EUR","0.10","8888" (where "8888" = PIN2)OK

AT+CPUC="EUR","0.10"OK SuccessfulAT+CPUC="EUR","0.10"+CME ERROR: SIM PIN2 required Attempt not successful. PIN2 authentication has

expired.

BGS3 AT Command Set 9.13 AT+CSSN


9.13 AT+CSSN Supplementary service notifications

Syntax


URC 1

+CSSI: <code 1>

When <n>=1 and a supplementary service notification is received after a mobile originated call setup, inter-mediate result code "+CSSI: <code 1>" is sent to TE before any other MO call setup result codes

URC 2

+CSSU: <code 2>

When <m>=1 and a supplementary service notification is received during a mobile terminated call setup orduring a call, unsolicited result code "+CSSU: <code 2>" is sent to TE.

Command DescriptionThe write command enables or disables the presentation of URCs for supplementary services.


0(&F)(P) Suppress "+CSSI" URCs 1 Activate "+CSSI" URCs

0(&F)(P) Suppress "+CSSU" URCs 1 Activate "+CSSU" URCs

Test Command

AT+CSSN=?Response(s)

+CSSN: (list of supported<n>s), (list of supported<m>s)OK

Read Command

AT+CSSN?Response(s)

+CSSN: <n>, <m>OK

Write Command

AT+CSSN=<n>[, <m>]Response(s)



- + + + + + - - GSM 07.07

<n>(num)

<m>(num)

BGS3 AT Command Set 9.13 AT+CSSN


0 unconditional call forwarding is active 1 some of the conditional call forwardings are active 2 call has been forwarded 3 Waiting call is pending

0 The incoming call is a forwarded call. 5 Held call was terminated by other party 10 additional incoming call forwarded

Note• URCs will be displayed only if the call concerned is a voice call, but some URCs will be displayed as well as

for data calls (like "+CSSU"=0).

<code 1>(num)

<code 2>(num)

BGS3 AT Command Set 9.14 AT+CUSD


9.14 AT+CUSD Unstructured supplementary service data

AT+CUSD allows control of the Unstructured Supplementary Service Data (USSD) according to GSM 02.90. Bothnetwork and mobile initiated operations are supported. The interaction of this command with other commandsbased on other GSM supplementary services is described in the GSM standard.

Parameter <n> is used to disable/enable the presentation of an unsolicited result code (USSD response fromthe network, or network initiated operation) "+CUSD: <m>[, <str_urc>[, <dcs>]]" to the TE.

When parameter <str_write> is given, a mobile initiated USSD string or a response USSD string to a networkinitiated operation is sent to the network. The response USSD string from the network is returned in a subsequentunsolicited result code "+CUSD"

Syntax

Unsolicited Result Code+CUSD: <m>[, <str_urc>[, <dcs>]]

URC "+CUSD" indicates an USSD response from the network, or network initiated operation


0(&F) Disable the result code presentation in the TA 1 Enable the result code presentation in the TA 2 Cancel session (not applicable to read command response)

String type USSD-string (when <str_write> parameter is not given, network is not interrogated). For the write command, only <dcs>= 15 is supported.

Test Command

AT+CUSD=?Response(s)

+CUSD: (list of supported<n>s)OK

Read Command

AT+CUSD?Response(s)

+CUSD: <n>OK

Write Command

AT+CUSD=<n>[, <str_write>[, <dcs>]]Response(s)



+ + + + + + - + GSM 07.07, GSM 02.90, GSM 03.90, GSM 04.90

<n>(num)

<str_write>(str)

BGS3 AT Command Set 9.14 AT+CUSD


String type USSD-string . If <dcs> indicates that GSM 03.38 default alphabet is used TA converts GSM alphabet into current TE characterset according to rules of GSM 07.05 Annex A. Otherwise in case of invalid or omitted <dcs> conversion of<str_urc> is not possible.

GSM 03.38 Cell Broadcast Data Coding Scheme in integer format (default 15). In case of an invalid or omitted<dcs> from the network side (MT) <dcs> will not be given out.

0 No further user action required (network initiated USSD-Notify, or no furtherinformation needed after mobile initiated operation)

1 Further user action required (network initiated USSD-Request, or further infor-mation needed after mobile initiated operation). If <m>=1, then the URC ends with ">" to prompt the user for input. The useraction is finished with <CTRL-Z> or aborted with <ESC>.

2 USSD terminated by network. 4 operation not supported 5 network time out

Notes• When a USSD string is sent via ATD, a "AT+CUSD=1" is executed implicitly. • It is recommended to finalize or escape a pending USSD user interaction before further actions are done to

prevent blocking situations.

<str_urc>(str)(+CSCS)

<dcs>(num)

<m>(num)

BGS3 AT Command Set 10. Internet Service Commands


10. Internet Service Commands

BGS3 has an embedded TCP/IP stack that is driven by AT commands and enables the host application to easilyaccess the Internet. The advantage of this solution is that it eliminates the need for the application manufacturerto implement own TCP/IP and PPP stacks, thus minimizing cost and time to integrate Internet connectivity intoa new or existing host application. This chapter is a reference guide to all the AT commands and responsesdefined for use with the TCP/IP stack.

Access is provided to the following Internet Services: 1. Socket Client and Server for TCP, Client for UDP 2. Transparent TCP Client 3. FTP Client 4. HTTP Client 5. SMTP Client 6. POP3 Client

Two design strategies for using Internet Service AT commands - URC mode or polling mode: The BGS3 offers two modes of controlling an Internet session opened with AT^SISO. To select the mode thatbest suits the preferences of your application design use the AT^SCFG command, parameter "Tcp/WithURCs"(refer to <tcpWithUrc>). • URC mode (delivery default):

The progress of an Internet session is URC driven. The URCs notify the host whether data can be sent orreceived, whether data transfer has completed, whether the service can be closed or whether an error hasoccurred. This mechanism eliminates the need to poll the service until the necessary progress information isreceived.To enable the URC mode select: AT^SCFG="Tcp/WithURCs",on.

• Polling mode:In polling mode, the presentation of URCs related to the Internet Services is disabled. The host is responsibleto retrieve all the status information needed for controlling the Internet session. This is done by polling, wherethe host application keeps sending the commands AT^SISR, AT^SISW, AT^SISI. To enable the polling mode select: AT^SCFG="Tcp/WithURCs",off.The disabled URCs are the following: "^SISR" URC, "^SISW" URC and "^SIS" URC for parameter <urc-Cause>=0 (Internet service events), but not for <urcCause>=1 or 2 (needed for Socket listener and alwaysenabled).

Step-by-step overview of how to configure and use TCP/IP communications with BGS3: • Select URC mode or polling mode as described above. • First of all, create a CSD or GPRS connection profile with AT^SICS. The connection profile is a set of basic

parameters which determines the type of connection to use for an Internet service. The connection type isalso referred to as bearer. Up to 6 connection profiles can be defined, each identified by the <conPro-fileId>.

• Secondly, use AT^SISS to create a service profile based on one of the connection profiles. Up to 10 serviceprofiles can be defined, each identified by the <srvProfileId>. The service profile specifies the type ofInternet service to use, i.e. Socket, FTP, HTTP, or one of the email services. To assign a connection profileto a service profile, the <conProfileId> of AT^SICS must be entered as "conId" value of the AT^SISSparameter <srvParmTag>. This offers great flexibility to combine connection profiles and service profiles. For example, you may haveone connection profile (CSD or GPRS) specified with AT^SICS which can be associated with an SMTP ser-vice profile for sending emails and a POP3 service profile for retrieving emails.

• Once the connection profile and the service profile are created, an Internet session can be opened by enteringthe AT^SISO write command and the desired <srvProfileId>. In URC mode, the "^SISR" or "^SISW" URC indicates whether the service is ready to receive or send data.This means, that the AT^SISR or AT^SISW command shall be entered after the URC was received. If an error

BGS3 AT Command Set


occurs the "^SIS" URC is delivered instead. In polling mode, you can enter the AT^SISR or AT^SISW command straight after AT^SISO though you mayneed to do so several times until the service confirms that data can be sent or received.

• The first parameter of the AT^SISR or AT^SISW commands is always the <srvProfileId>, the secondparameter is the number of bytes which the host either wants to send to or is able to receive from the module.The way the module handles the data transfer follows the rules of the ordinary socket interface and is awarethat a host may be limited by its input buffer size. The maximum data size supported by BGS3 is 1500 bytesin both directions (read or write). To send or receive more than 1500 bytes, the read or write action shall berepeated until the data transfer has completed. Each read or write action requires that the command response(of AT^SISR or AT^SISW) confirms that the service is ready to send or receive data. To end an upload data stream set the <eodFlag> in the last AT^SISW command.

• For Transparent TCP service the AT command AT^SIST provides a specific mode for data exchange andaccepts <srvProfileId> only. In that mode the service is connected to the interface in a transparent man-ner and exchanging data is not related to the AT^SISW and AT^SISR cycles. To resume AT command modeenter the +++ escape sequence or toggle the DTR line.

• The AT^SISI command shall be used to monitor the progress of the session. The command reports the ser-vice state of the used service profile and indicates the number of bytes received, the number of bytes sentand, in the case of sending, the number of bytes acknowledged or unacknowledged at TCP layer.

• If an error occurs during a session you can enter the AT^SISE command and the <srvProfileId> to iden-tify the reason. This is especially important in polling mode.

• Finally, to end a session, enter the AT^SISC write command and the <srvProfileId>.

Additional AT commands designed for controlling and monitoring the connection profiles (bearers): • The AT^SICI command can be used any time to query the current status of one or all connection profile(s). • The AT^SICO command opens a connection and keeps it open until closed with AT^SICC or disconnected

by the network. • The AT^SICC command closes a connection set up with AT^SICO. • The AT^SISX command sends ICMP (Interntet Control Message Protocol) Echo Requests to a target IP

address or host name to verify the TCP/IP network connection.

Maximum number of profiles defined / used: • Up to 6 connection profiles can be created (with AT^SICS). • Up to 10 service profiles can be created (with AT^SISS), but the number of parallel profiles of the same ser-

vice type is limited as listed below. If the maximum number of a service profile type is already defined, anyattempt to set up another profile for the same type will be denied with "+CME ERROR: operation of servicetemporary not allowed". - Maximum 3 HTTP profiles- Maximum 6 socket profiles: Only 2 instances can be opened for listener, meaning that if 2 listeners are

established another 4 instances can be opened for clients. Also, the socket service can accept an incom-ing connection only when at least one service profile is still free (not yet created with AT^SISS), otherwisethe incoming connection will be rejected from the listener. If there is no listener established all 6 socketprofiles can be configured as client.

- 2 Transparent TCP profiles- 1 FTP profile- 1 POP3 profile- 1 SMTP profile

• The TCP/IP stack of BGS3 supports using several service profiles at the same time, provided all of them arerunning on the same connection profile (bearer). For example, it is possible to download files from an FTPserver, while sending and receiving emails at the same time.

Using Internet Service AT commands on several interfaces (ASC0, ASC1 or Multiplex mode on ASC0):• A connection profile can be created on one interface and then viewed or changed on all other interfaces.

BGS3 AT Command Set


• A service profile can be used only on one interface at a time: - Service profiles can only be opened on the interface where they have been defined with AT^SISS. - Accordingly, on each interface the read commands AT^SISO? and AT^SISI? deliver full status informa-

tion for the service profiles configured / opened on this interface, while service profiles related to otherinterfaces are only listed by <srvProfileId> and service type name (= <srvParmTag> value "srv-Type") without any status parameters.

- Changes to a service profile are allowed only on the same interface where it was created, trying to changeit on another interface is denied with "+CME ERROR: invalid index". If queried with the read commandAT^SISS? the entire profile is returned on the interface where the service profile was created, while on allother interfaces only the service type of the profile is stated.

- To free a service profile for use on another interface, use the AT^SISS command and select service type= "none". This action deletes the entire profile and restores all parameters of the profile to their initialpower-up state (all values are empty). For example, to remove the service profile 3, set AT^SISS=3,srv-Type,none. After this, a new profile 3 can be created on any other interface.

Address notationServer addresses must be provided as IP addresses in standard dot-format (e.g. "192.168.1.2") or as serveraddress names resolvable by a DNS server (e.g. "smtp.myserver.de" or "pop3.myserver.de").

TimeoutsTimeouts are not part of the Internet AT command functionality implemented in BGS3 and, if desired, are theresponsibility of the host application. It is recommended that the host application validates URCs and AT com-mand responses and reacts adequately, for example by sending a close message or starting a timer.

Socket service used with UDP protocolThe significant differences between the TCP and UDP protocols imply that UDP sometimes requires particularprocedures or even specific parameters. Details on how to handle UDP services can be found in extra notes orare included in the general parameter descriptions. The BGS3 offers two kinds of Socket service with UDP protocol. One is referred to as UDP client intended forconnections to a given remote host. In this case the IP address and the UDP port of the remote host are set asa fixed parameter in the service profile. The other type is referred to as UDP endpoint where IP address and UDPport of the remote hosts are handled in each read (AT^SISR) and write (AT^SISW) request. This enables thehost application to communicate with different remote hosts.

Using the DCD line to detect the connection status of Internet servicesWith AT&C you can configure the DCD line of the used serial interface to indicate whether an Internet service isactive. For Socket, HTTP, SMTP and POP3 the states "Up" or "Connecting" are indicated, for FTP and transpar-ent TCP only the state "Up".

BGS3 AT Command Set 10.1 AT^SICS


10.1 AT^SICS Internet Connection Setup Profile

AT^SICS serves to create and edit Internet connection profiles. A connection profile can be assigned to one ormore service profiles defined with AT^SISS, and thus, determines which type of connection is to be establishedwhen opening a service profile with AT^SISO.

The AT^SICS read command requests the current settings of all Internet connection profiles. One line is issuedfor every possible parameter of a given <conParmTag> "conType" value.

The AT^SICS write command specifies all parameters of a connection profile identified by <conProfileId>.At first the type of Internet connection needs to be selected via <conParmTag> value "conType". This deter-mines the applicability of all other <conParmTag> values related to this "conType" and automatically sets theirdefaults. An exception is the <conParmValue-alphabet> which can be set before or after selecting "con-Type".

To change the settings the write command needs to be executed for each single <conParmTag>. All profileparameters set with AT^SICS are volatile.

Table 10.1: Applicability of AT^SICS <conParmTag> values

Syntax

<conParmTag> value CSD GPRS0"conType" mandatory mandatory "user" optional optional "passwd" optional optional "apn" ø mandatory "inactTO" optional optional "calledNum" mandatory ø "dataRate" mandatory ø "dataType" mandatory ø "authMode" mandatory optional "fnur" optional optional "dns1" optional optional "dns2" optional optional "alphabet" optional optional

Test Command

AT^SICS=?Response(s)

OK

Read Command

AT^SICS?Response(s)

^SICS: <conProfileId>, <conParmTag>, <conParmValue>OK




0...5 Internet connection profile identifier.The <conProfileId> identifies all parameters of a connection profile, and,when a service profile is created with AT^SISS the <conProfileId> needsto be set as "conId" value of the AT^SISS parameter <srvParmTag>.

Internet connection parameter. “conType“ Type of Internet connection.

For supported values of <conParmValue> refer to <conParmValue-con-Type>.

“alphabet“ Selects the character set for input and output of string parameters within a pro-file. The selected value is bound to the specific profile. This means that differentprofiles may use different alphabets. Unlike other parameters the alphabet canbe changed no matter whether the <conParmTag> value "conType" has beenset. For supported values of <conParmValue> refer to <conParmValue-alphabet>.

“user“ User name string: maximum 32 characters (where "" is default). “passwd“ Password string: maximum 32 characters (where ***** is default).

If <conParmValue-authMode> is "MsChapV1" then the maximum passwordlength is 16 characters.

“apn“ Access point name string value: maximum 100 characters (where "" is default). “inactTO“ Inactivity timeout value in seconds: 0 ... 216-1, default = 20

Number of seconds the bearer remains open although the service no longerneeds the bearer connection. Do not set the timeout value below 3 sec. This may result in problems whenusing the <eodFlag> (set in the last AT^SISW command to terminate anupload data stream). The value -1 indicates that, after opening the bearer with AT^SICO, the inac-tivity timeout is currently disabled. Closing the bearer with AT^SICC restoresthe previously set "inactTO" value of the concerned connection profile.

“calledNum“ Called BCD number. “dataRate“ Data rate.

For supported values of <conParmValue> refer to <conParmValue-dat-aRate>.

“dataType“ Data call type. For supported values of <conParmValue> refer to <conParmValue-dataType>.

Write Command

AT^SICS=<conProfileId>, <conParmTag>, <conParmValue>Response(s)



- + + + + + - -

<conProfileId>(num)

<conParmTag>(str)



“authMode“ Authentication mode. For supported values of <conParmValue> refer to <conParmValue-auth-Mode>.

“fnur“ Fixed Network User Rate. For supported values of <conParmValue> refer to <conParmValue-fnur>.

“dns1“ Primary DNS server address (IP address in dotted-four-byte format).This value determines whether to use the DNS server addresses dynamicallyassigned by the network or a specific DNS server address given by the user. "dns1" = "0.0.0.0" (default) means that the CSD or GPRS connection profileuses dynamic DNS assignment. Any other address means that the PrimaryDNS is manually set.The default value applies automatically if no other address is set. Note that theAT^SICS read command only returns a manually configured IP address, whilethe value "0.0.0.0" is not indicated at all, no matter whether assumed by defaultor explicitly specified. See also note below.

“dns2“ Secondary DNS server address (IP address in dotted-four-byte format).If "dns1" = "0.0.0.0" this setting will be ignored. Otherwise this value can beused to manually configure an alternate server for the DNS1. If "dns1" is not equal "0.0.0.0" and no "dns2" address is given, then"dns2"="0.0.0.0" will be assumed automatically. The AT^SICS read commandonly returns a manually configured IP address, while the value "0.0.0.0" is notindicated at all, no matter whether assumed by default or explicitly specified.

Parameter value; type and supported content depend on related <conParmTag>.

Supported connection type values in <conParmValue> for <conParmTag> value "conType". “CSD“ Circuit-switched data call. “GPRS0“ GPRS connection.

Settings of GPRS related commands are not used, e.g. AT+CGDCONT. When aservice based on a GPRS connection profile is started after entering AT^SISOBGS3 automatically tries to attach to the GPRS. Yet, the only exception isAT+CGATT which can be used any time to detach from the GPRS and thus dis-connect the bearer opened with AT^SISO.

“none“ Clears the connection profile.

Character set selectable with <conParmValue> for <conParmTag> value "alphabet". [“0“] Character set determined with AT+CSCS applies. “1“ International Reference Alphabet (IRA, seven bit ASCII) applies.

Supported data rate values in <conParmValue> for <conParmTag> value "dataRate". “0“ 14.4 KBaud [“1“] 9.6 KBaud

<conParmValue>(str)

<conParmValue-conType>(str)

<conParmValue-alphabet>(str)

<conParmValue-dataRate>(str)



Supported data call type values in <conParmValue> for <conParmTag> value "dataType". “0“ ISDN [“1“] Analog

Supported authentication mode values in <conParmValue> for <conParmTag> value "authMode". Changingthe <conParmValue-authMode> will restore the password to its default (*****). “none“[“PAP“]“CHAP““MsChapV1“

Fixed Network User Rate (FNUR) set with <conParmValue>.This parameter is only required for 14.4 kbit/s UDI calls (Unrestricted Digital Information). Changes are recom-mended only if an originated CSD call fails. The choice as to which of the values to use depends on the GSMnetwork and the location. Users should be aware that even the same operator may apply varying FNUR config-urations in different regions. See also AT^SFNUR command. 0 not applicable[1] 9.6 kbit/s2 14.4 kbit/s3 19.2 kbit/s4 28.8 kbit/s5 38.4 kbit/s6 48.0 kbit/s7 56.7 kbit/s8 64.0 kbit/s

Notes• Before opening a service profile based on a connection profile recently used, check with AT^SICI that the

previous connection was properly closed. If AT^SICI confirms that the connection profile is in <conState>0 (Down) the connection profile may be used again.

• If a GPRS network does not support or is not correctly configured for automatic DNS address assignment theTCP/IP stack cannot resolve fully qualified domain names. In this case, a warning message will be returnedwhen trying to open an Internet service configured for automatic DNS address assignment.

10.1.1 Example: Default values of a CSD connection profile

As stated earlier, the "conType" selected with AT^SICS determines all other matching profile parameters relatedto this "conType". Once "conType" is set in a new profile, the default values of all other related parameters areassumed. To view the default settings you can use the read command AT^SICS?.

<conParmValue-dataType>(str)

<conParmValue-authMode>(str)

<conParmValue-fnur>(num)

at^sics=1,conType,CSD Select connection type CSD, identified by <con-ProfileId>1

OKat^sics? Query current profiles.



10.1.2 Example: GPRS connection profile

^SICS: 0, "conType", "" Profile with <conProfileId> 0 is still empty.^SICS: 1, "conType", "CSD" The new CSD profile just created is indicated with all

related parameters set to their default.^SICS: 1, "alphabet", "0" Character set determined with AT+CSCS applies

when string parameters are input with AT^SICS.^SICS: 1, "user", "" No user name set.^SICS: 1, "passwd", "*****" Password masked with asteriks.^SICS: 1, "authMode", "PAP" Authentication protocol PAP is assumed as default.^SICS: 1, "inactTO", "0" No inactivity timeout set.^SICS: 1, "calledNum", "" No destination set.^SICS: 1, "dataRate", "1" Data rate set to 9.6 kbaud.^SICS: 1, "dataType", "1" Remote device is analog, e.g. an analog modem.^SICS: 2, "conType", "" Profile with <conProfileId> 2 is still empty.^SICS: 3, "conType", "" Profile with <conProfileId> 3 is still empty.^SICS: 4, "conType", "" Profile with <conProfileId> 4 is still empty.^SICS: 5, "conType", "" Profile with <conProfileId> 5 is still empty.OK

at^sics=0,conType,GPRS0 Select connection type GPRS0.OKAT^SICS=0,inactTO,"0" Inactivitiy timeout = 0 (default).OKAT^SICS=0,dns1,"193.254.160.1" IP address of Primary DNS server.OKAT^SICS=0,authMode,"PAP" Authentication protocol PAP (default).OKAT^SICS=0,passwd,t-d1 Password for GPRS services provided by the Ger-

man operator T-D1.OKAT^SICS=0,apn,"internet.t-d1.de" APN to access the GPRS services provided by the

German operator T-D1.OK

BGS3 AT Command Set 10.2 AT^SICI


10.2 AT^SICI Internet Connection Information

The AT^SICI read command requests the current status of the Internet connection profiles currently definedwith AT^SICS.

The AT^SICI write command displays the status of the specified Internet connection profile. If the connectionprofile is not defined yet, the command returns a "+CME ERROR" response.

Syntax


Internet connection profile identifier as defined by AT^SICS (<conProfileId>). 0...5

State of the Internet connection profile. 0 Down - Internet connection is defined but not connected. 1 Connecting - A service has been opened and so the Internet connection is ini-

tated. 2 Up - Internet connection is established and usable by one or more services. 3 Limited Up - Internet connection is established, but temporarily no network cov-

erage.This state applies only to GPRS profiles (it does not occur with CSD).

4 Closing - Internet connection is terminating.

Test Command

AT^SICI=?Response(s)

[^SICI:(list of defined <conProfileId>s)]OK

Read Command

AT^SICI?Response(s)

[^SICI: <conProfileId>, <conState>, <numServices>, <conAddr>][^SICI: ...]OK

Write Command

AT^SICI=<conProfileId>Response(s)

^SICI: <conProfileId>, <conState>, <numServices>, <conAddr>OKERROR+CME ERROR: <err>


- + + + + + - -

<conProfileId>(num)

<conState>(num)



Number of services using this Internet connection profile. 0...9

Local IP address of the Internet connection profile (empty if no address is associated yet).

Notes• Before opening a service profile based on a connection profile recently used, check with AT^SICI that the

previous connection was properly closed. If AT^SICI confirms that the connection profile is in <conState>0 (Down) the connection profile may be used again.

• If AT^SICI is used simultaneously on different instances (e.g. Mux channels) only one request can be han-dled at a time. On the other instance(s) "+CME ERROR: operation temporary not allowed" will be displayed.If so, repeat the command on this instance.

• After closing the last service which uses this connection profile, parameter value <numServices> isdecreased after the expiry of the inactivity timeout "inactTO" of AT^SICS only.

10.2.1 Checking Connection Profile Status

Assume the network connection is temporarily not available. (If URC presentation mode of network registrationis enabled the state is shown by the URC "+CREG: 2").

The network connection is temporarily not available but the Internet connection is still established, so the hostmay decide to stop the data transfer to minimize the risk of losing data due to memory limitations.

Another service has been opened with AT^SISO:

After closing one service with AT^SISC:

<numServices>(num)

<conAddr>(str)

at^sici? Query the current status of the connection profile.^SICI: 1,2,1,"10.10.0.161" One connection profile has been created at <con-

ProfileId>=1, and one service is opened usingthis connection profile. The Internet connection is in<conState>=2 ("Up").

OK

at^sici? Query once again the current status of the connec-tion profile.

^SICI: 1,3,1,"10.10.0.161" Parameter <conState> has changed to state "Lim-ited up".

OK


^SICI: 1,2,1,"10.10.0.161" After re-establishing the network connection, <con-State> reverts to state "Up".

OK


^SICI: 1,2,2,"10.10.0.161" After opening another service, parameter <numSer-vices> has increased.

OK



After closing the last service with AT^SISC:


^SICI: 1,2,1,"10.10.0.161" Parameter <numServices> has decreased. OK


^SICI: 1,2,1,"10.10.0.161" The bearer is still open because of the inactivity tim-eout "inactTO" of AT^SICS.

OKat^sici? Query again the current status.^SICI: 1,0,0,"0.0.0.0" The inactivity timeout "inactTO" of AT^SICS has

expired, therefore the bearer is closed now. Param-eter <numServices> has decreased.

OK

BGS3 AT Command Set 10.3 AT^SISS


10.3 AT^SISS Internet Service Setup Profile

AT^SISS serves to set up the necessary parameters in the Internet service profiles. Any service profile can thenbe used to control a data link in conjunction with AT^SISI, AT^SISO, AT^SISC, AT^SISR, AT^SISW, AT^SISTand AT^SISE.

The AT^SISS read command requests the current settings of all Internet service profiles. One line is issued forevery possible parameter of a given <srvParmTag> "srvType" value.

The AT^SISS write command specifies the parameters for a service profile identified by <srvProfileId>. Atfirst the type of Internet service needs to be selected via <srvParmTag> value "srvType". This determines theapplicability of all other <srvParmTag> values related to this "srvType" and sets their defaults. Changing the<srvParmTag> "srvType" of an existing service profile will reset all <srvParmTag> default values to suit thenew "srvType". An exception is the <srvParmValue-alphabet> which can be set before or after selecting"srvType" and is not reset when "srvType" changes.

To change the settings the write command needs to be executed for each single <srvParmTag>. All profileparameters set with AT^SISS are volatile.

The list below shows which <srvParmTag> parameters apply to each Internet service and which of them aremandatory or optional.

Table 10.2: Applicability of AT^SISS <srvParmTag> values

<srvParmTag> Mandatory or optional

Socket service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "tcpMR" optional "tcpOT" optional

Transparent service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "tcpMR" optional "tcpOT" optional

FTP service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "tcpMR" optional "tcpOT" optional

HTTP service



"srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "user" optional "password" optional "hcContent" optional "hcContLen" optional "hcUserAgent" optional "hcMethod" mandatory "hcProp" optional "hcRedir" optional "hcAuth" optional "tcpMR" optional "tcpOT" optional

SMTP service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "user" optional "password" optional "tcpPort" optional "smFrom" mandatory "smRcpt" mandatory "smCC" optional "smSubj" optional "smHdr" optional "smAuth" optional "tcpMR" optional "tcpOT" optional

POP3 service "srvType" mandatory "conId" mandatory "alphabet" optional "address" mandatory "user" mandatory "password" mandatory "tcpPort" optional "pCmd" mandatory




Syntax


Internet service profile identifier.The <srvProfileId> is used to reference all parameters related to the same service profile. Furthermore,when using the AT commands AT^SISO, AT^SISR, AT^SISW, AT^SIST and AT^SISC the <srvProfileId>is needed to select a specific service profile. 0...9

Internet service profile parameter. srvType Type of Internet service to be configured with consecutive usage of AT^SISS.

For supported values of <srvParmValue> refer to <srvParmValue-srv-Type>.

alphabet Selects the character set for input and output of string parameters within a pro-file. The selected value is bound to the specific profile. This means that differentprofiles may use different alphabets. Unlike other parameters the alphabet can

"pNumber" optional "pLength" optional "pDelFlag" optional "tcpMR" optional "tcpOT" optional

Test Command

AT^SISS=?Response(s)

OK

Read Command

AT^SISS?Response(s)

^SISS: <srvProfileId>, <srvParmTag>, <srvParmValue>OKERROR+CME ERROR: <err>

Write Command

AT^SISS=<srvProfileId>, <srvParmTag>, <srvParmValue>Response(s)



- + + + + + - -

<srvProfileId>(num)

<srvParmTag>




be changed no matter whether the <srvParmTag> value "srvType" has beenset. For supported values of <srvParmValue> refer to <srvParmValue-alphabet>.

user User name string 1. Socket

Not applicable. 2. Transparent

Not applicable. 3. FTP

Not applicable; set within "address" parameter. 4. HTTP

Length: 2 ... 31User name for the HTTP authentication mechanism. Currently only HTTPsimple authentication is supported.

5. SMTP User name to be used for SMTP authentication (string).Length: 4 ... 64. If SMTP authentication is disabled, i.e. "smAuth" flag not set, user nameparameter will be ignored.

6. POP3 User name identifying a mailbox, i.e. mailbox name (string).Length: 1 ... 64.

passwd Password string 1. Socket

Not applicable. 2. Transparent

Not applicable. 3. FTP

Not applicable; set within "address" parameter. 4. HTTP

Length: 2 ... 31Password for the HTTP authentication mechanism. Currently HTTP simpleauthentication is supported only.

5. SMTP Password to be used for SMTP authentication (string).Length: 4 ... 64. If SMTP authentication is disabled, i.e. "smAuth" flag not set, passwordparameter will be ignored.

6. POP3 Server/mailbox-specific password (string).Length: 1 ... 64. Used to perform authentication with a POP3 server.

conId Internet connection profile to be used, for details refer AT^SICS. tcpPort TCP Port Number

1. Socket Not applicable; set within "address" parameter.

2. Transparent Not applicable; set within "address" parameter.

3. FTP Not applicable; set within "address" parameter.

4. HTTP Not applicable; set within "address" parameter. If parameter is omitted the service connects to HTTP default port 80.



5. SMTP SMTP server TCP port number (numeric) Length: 0 ... 216-1If this parameter is not set, SMTP default port number 25 is used.

6. POP3 POP3 server TCP port number (numeric)Length: 0 ... 216-1If this parameter is not set, POP3 default port number 110 is used.

address String value, depending on the service type either a URL in the case of Socket,FTP and HTTP or an address in the case of SMTP and POP3: 1. Socket

- Socket type TCP client URL "socktcp://'host':'remote tcpPort'[;disnagle='0|1'] " "disnagle" is optional for disabling the TCP Nagle algorithm. 0: Nagle algorithm is enabled (default). 1: Nagle algorithm is disabled.

- Socket type TCP server URL "socktcp://listener:'local tcpPort' "

- Socket type UDP endpoint URL "sockudp://:'local udpPort' "

- Socket type UDP client URL "sockudp://'host':'remote udpPort'[;size='byte'][;port='word']" Parameter "size" (optional): 0: PDU size is variable (default). 1 ... 1500: Fixed PDU size in bytes.Parameter "port" (optional):0: Port number will be assigned from service (default).1 ... 216-1: defines the local port number for the UDP client.

2. Transparent "'host':'remote TcpPort'[;timer=100][;etx=<etxChar>]" Parameter "timer" (optional): 20 ... 500 milliseconds in steps of 20. Defaultif parameter is not specified: 100ms. The parameter configures the Naglealgorithm, which is used in transparent access mode.Parameter "etx" (optional): Specifies the character used to change fromtransparent access mode to AT command mode. Range of <etxChar>: 1 ...15, 17 ... 255. 16 is not allowed because definedas DLE (0x10). If value is not set no escaping is configured, thus requiring either +++ orDTR ON-OFF transition for changing to AT command mode. If value is set,the transmitted bytes are parsed for the DLE (0x10) character followed bythe specified <etxChar> value. If both characters are found the servicereturns to AT command mode without transmitting these two bytes. Thisbehavior differs from +++ handling, where +++ is transmitted over the air.If you wish to send DLE characters as normal text string within your payloaddata the characters shall be doubled (DLE DLE).

3. FTP - FTP client URL (get)

"ftp://'user':'password'@'host':'tcpPort'/'url-path' [;type='a|i|d'] "Refer to "IETF-RFC 1738".

- FTP client URL (put)"ftpput://'user':'password'@'host':'tcpPort'/'url-path'/'element name'[;type='a|i'][;mode='u|a|d'] "

Used parameters:"host" is mandatory, all other parameters are optional. If "password" is set then "user" must be set as well. If "user" is omitted the string "anonymous" is selected for "user" and "pass-word". If "password" is omitted the password request is served by an empty string.



If "tcpPort" is omitted the service connects to the FTP default port 21. If "url-path" contains only the IP address a directory listing is requested. If "url-path" contains the IP address and has a slash '/' appended a detaileddirectory listing is requested. "type": [a)scii | i)mage | d)irectory] "mode": [u)nique | a)ppend | d)elete] "u)nique" selects the FTP Store Unique command to create a file nameunique to the current directory. If the file name is assigned by the serverthen the "^SIS" URC will appear, indicating <urcInfoId> 2100 and thefile name. "d)elete" clears given 'element name'. If "mode" is omitted "replace mode" is default setting.

4. HTTPHTTP client URLLength: 6 ... 255"http://'server'/'path':'tcpPort' ""server": FQDN or IP-address "path": path of file or directory "tcpPort": If parameter is omitted the service connects to HTTP default port80. Refer to "IETF-RFC 2616".

5. SMTPSMTP server address (string). Length: 4 ... 256.

6. POP3POP3 server address (string). Length: 4 ... 256.

hcContent Optional parameter for HTTP method "Post".Length: 0 ... 127Can be used to transfer a small amount of data. The content of this string willonly be sent if "hcContLen" = 0. The maximum length of "hcContent" is 127bytes. To transmit a larger amount of data "hcContLen" must be set to a non-zerovalue. In this case the "hcContent" string will be ignored, and data transmissionfrom the client to the server is done with AT^SISW.

hcContLen Mandatory parameter for HTTP method "Post".Length: 0 ... 231-1The content length shall be set in the header of the HTTP "Post" request beforethe data part is transferred.If "hcContLen" = 0 then the data given in the "hcContent" string will be posted.If "hcContLen" > 0 then the AT^SISW command will be used to send data fromthe client to the server. In this case, "hcContLen" specifies the total amount ofdata to be sent. The data can be sent in one or several parts. For each part,the transmission is triggered by the URC "^SISW: x, 1", then the AT^SISW writecommand can be executed. After the exact number of bytes are transferred viathe serial interface, the HTTP client will go from service state "Up" to servicestate "Closing" (see parameters <srvState> and <srvState> for detail).Finally, the URC "^SISW: x, 2" indicates that all data have been transferred andthe service can be closed with AT^SISC.

hcUsrAgent The user agent string must be set by the application to identify the mobile. Usu-ally operation system and software version info is set with this browser identi-fier. Length: 0 ... 63

hcMethod HTTP method specification: 0=GET, 1=POST, 2=HEAD.



hcProp Parameter for several HTTP settings. Length: 0 ... 127The general format is 'key': <space> 'value' Multiple settings can be given separated by "\0d\0a" sequences within thestring, do not put them at the end. Possible 'key' values are defined at HTTP/1.1 Standard RFC 2616.

hcRedir This flag controls the redirection mechanism of the BGS3 acting as HTTP client(numeric).If "hcRedir" = 0: No redirection.If "hcRedir" = 1: The client automatically sends a new HTTP request if theserver answers with a redirect code (range 30x).Default is 1.

hcAuth If set ("hcAuth" = 1) this flag determines that the HTTP client will automaticallyanswer on authentication requests from the server with the current "passwd"and "user" parameter settings. If these parameters are not specified the BGS3will terminate the HTTP connection and send an indication to the TA.Default is 1.

smFrom Email sender address, i.e. "MAIL FROM" address (string). Length: 6 ... 256A valid address parameter consists of local part and domain name delimited bya '@' character, e.g. "[email protected]".

smRcpt Recipient address of the email, i.e. "RCPT TO" address (string). Length: 6 ... 256If multiple recipient addresses are to be supplied the comma character is usedas delimiter to separate individual address values, e.g. "[email protected],[email protected]". Some mail servers do not accept recip-ient addresses without brackets <>. It is recommended to use the "RCPT TO"variable with brackets.

smCC CC recipient address of the email (string). Length: 6 ... 256If multiple CC recipient addresses are to be supplied the comma character isused as delimiter to separate individual address values, e.g."[email protected],[email protected]".

smSubj Subject content of the email (string).Length: 0 ... 256If no subject is supplied the email will be sent with an empty subject.

smHdr This parameter, if set, will be appended at the end of the email header section(string).Length: 0... 256Hence, it serves as a generic header field parameter which allows the user toprovide any email header field. It is the user's responsibility to provide correctheader fields!String of max. 256 characters. Example for multipart MIME messages: "Content-Type: multipart/mixed".

smAuth SMTP authentication control flag (numeric). If disabled (<srvParmValue> "0" by default), BGS3 performs action withoutSMTP authentication. If enabled (<srvParmValue> "1") authentication procedure with the SMTPserver will be performed by means of supported authentication methods, usingvalues of "user" and "passwd" parameters. If BGS3 and SMTP server are notable to negotiate an authentication mechanism supported by both parties, theBGS3 continues action without authentication.BGS3 supports SMTP authentication.

pCmd POP3 user command to be executed by the POP3 service (numeric). For supported values of <srvParmValue> refer to <srvParmValue-pCmd>.



pNumber Optional message number argument used by the POP3 commands List ("2"),Retrieve ("3") and Delete ("4"). For POP3 commands see <srvParmTag>value "pCmd". Length: 0 ... 231-1If no specific value is set in the service profile, the value "0" is assumed bydefault, i.e. "pNumber" is disabled.

pLength Maximum message length (string, optional)Length: 0 ... 231-1"pLength" can be used to specify the length of the message(s) to be retrievedfrom or deleted on the POP3 server. If no specific value is set in the serviceprofile, the default value "0" is assumed, which means that there is no limit onthe message size. A warning will be issued inthe following cases: • If "pNumber" > 0 and a specific message to be retrieved from / deleted on

the server is longer than "pLength".• If "pNumber" = 0 and all messages to be retrieved from / deleted on the

server are longer than "pLength".No warning will be issued in the following cases: • If there are no messages at all on the server.• If the server has message(s) below and above the "pLength" specified. In

this case, the message(s) within the range of "pLength" can be successfullyretrieved or deleted, but the message(s) above "pLength" remain on theserver without any further notification given to the user.

• Therefore, after retrieving / deleting messages, it is recommended to checkthe message status on the server. This can be done by adding a furtherPOP3 service profile using the POP3 user command List ("2").

pDelFlag Flag to be used with the POP3 user command Retrieve ("3"). Specifies whetheror not to delete retrieved emails on the server (optional). For supported values of <srvParmValue> refer to <srvParmValue-pDelFlag>.

tcpMR Parameter can be used to overwrite the global AT^SCFG parameter "Tcp/MaxRetransmissions" <tcpMr> for a specific Internet Service connection pro-file. If the parameter is not specified the value specified with AT^SCFG will beused. Supported values <srvParmValue> for this parameter are the same asdescribed for <tcpMr>. Setting is not relevant for Internet Service "Socket" with type "UDP".

tcpOT Parameter can be used to overwrite the global AT^SCFG parameter "Tcp/Over-allTimeout" <tcpOt> for a specific Internet Service connection profile. If theparameter is not specified the value specified with AT^SCFG will be used. Supported values <srvParmValue> for this parameter are the same asdescribed for <tcpOt>. Setting is not relevant for Internet Service "Socket" with type "UDP".

Parameter value; type and supported content depend on related <srvParmTag>.

Supported Internet service type values in <srvParmValue> for <srvParmTag> value "srvType".Before changing the "srvType" of an existing service profile be sure that the profile is closed. To verify the con-nection state of the service profile enter the read command AT^SISI. Only when <srvState>=2 is returnedfor this specific service profile you can change its service type. “Socket“ BGS3 acting as client or server (listener) for TCP or UDP.

If BGS3 is TCP listener at least two service profiles are required. The firstsocket profile must be configured as listener. The second service profile will bedynamically assigned when a socket connection request from a remote client

<srvParmValue>(str)

<srvParmValue-srvType>(str)



is incoming. For this purpose, one service profile must be left free (= not con-figured with AT^SISS). An incoming socket connection request will be indi-cated by the "^SIS" URC, with the next free <srvProfileId> shown insidethe URC as parameter <urcInfoId>. The connection request can beaccepted or rejected by using the commands AT^SISO or AT^SISC and the IDretrieved from the "^SIS".

“Transparent“ BGS3 acting as Transparent TCP socket client. “Ftp“ BGS3 acting as FTP client. “Http“ BGS3 acting as HTTP client. “Smtp“ BGS3 acting as SMTP client. “Pop3“ BGS3 acting as POP3 client. “none“ Reset Internet service profile settings. Operation is not allowed if profile is in

use, i.e. it was activated via AT^SISO.

Supported string parameter character set selections in <srvParmValue> for <srvParmTag> value "alphabet". [“0“] Applicable character set is determined by current setting of AT+CSCS. “1“ International Reference Alphabet (IRA, seven bit ASCII).

Supported POP3 user command values in <srvParmValue> for <srvParmTag> value "pCmd". 1 Status command.

This command retrieves the "drop listing" of a POP3 server. A "drop listing"consists of a single line containing the number of messages in the maildrop listfollowed by the total size of the maildrop list in bytes. Each drop listing will befinished by a so-called "dotline", i.e. a new line with just a single dot.

2 List command. If <srvParmTag> value "pNumber" is set to a non-zero value the "List" com-mand returns the "scan listing", consisting of a single line which contains themessage number and the message size in bytes if the specified messageexists in the maildrop list on the POP3 server. If no such message exists on the server than the POP3 service issues an errorresponse to the user. If <srvParmTag> value "pNumber" is zero the "List" command returns a multi-line "scan listing". For each message on the maildrop list of the server thePOP3 service returns a line containing the message number and its size inbytes. A final "dotline" will be printed at the end of the "scan listing". If there are no messages on the maildrop list of the server, the POP3 servicereturns a positive response, i.e. it doesn't issue an error response, but the"scan listing" will be empty.In either case, each scan listing will be finished by a so-called "dotline", i.e. anew line with just a single dot.

3 Retrieve command. If <srvParmTag> value "pNumber" is set to a non-zero value this commandretrieves the related message from the POP3 server's maildrop list. If no such message exists on the server the POP3 service issues an errorresponse to the user. It depends on the parameter "pDelFlag" if the message will be deleted from thePOP3 server upon successful retrieval. If <srvParmTag> value "pNumber" is zero the "Retrieve" command returns allmessages pending in the POP3 server's maildrop. If there are no messages on the maildrop list of the server the POP3 service

<srvParmValue-alphabet>(str)

<srvParmValue-pCmd>(num)



returns with a positive response, i.e. it doesn't issue an error response, but thereturned list will be empty.Each email will be finished by a so-called "dotline", i.e. a new line with just asingle dot.

4 Delete commandIf <srvParmTag> value "pNumber" is set to a non-zero value the commanddeletes the related message from the POP3 server's maildrop list. In fact, themessage is marked as deleted on the server and will be deleted permanentlyif the POP3 service command executes successfully. In case an error hasoccurred, e.g. network loss, the message will not be deleted on the server eventhough the POP3 service command has been finished. If <srvParmTag> value "pNumber" is zero the "Delete" command deletes allmessages from the POP3 server's maildrop list. In fact, the messages aremarked as deleted on the server and will be deleted permanently if the POP3service command executes successfully. In case an error has occurred, themessages will not be deleted on the server even though the POP3 servicecommand has been finished.

Supported flag values in <srvParmValue> for <srvParmTag> value "pDelFlag". Only applicable if the profilecontains the POP3 user command Retrieve ("3"). [0] Messages will not be deleted on the server. 1 Delete messages on the server which have been retrieved successfully.

Notes• String parameters are truncated if greater than the maximum length specified above. • If AT^SISS is used simultaneously on different instances (e.g. Mux channels) only one request can be han-

dled at a time. On the other instance(s) "+CME ERROR: operation temporary not allowed" will be displayed.If so, repeat the command on this instance.

<srvParmValue-pDelFlag>(num)

BGS3 AT Command Set 10.4 AT^SISI


10.4 AT^SISI Internet Service Information

AT^SISI serves to monitor the status of Internet service profiles defined with AT^SISS.

The AT^SISI read command requests the current status of all defined Internet service profiles.

The AT^SISI write command requests the status of the specified Internet service profile. If the specified serviceprofile is not defined yet, "+CME ERROR" is returned.

SyntaxTest Command

AT^SISI=?Response(s)

[^SISI:(list of defined <srvProfileId>s)]OK

Read Command

AT^SISI?Response(s)

If response is related to service profile(s) created / opened on this interface:[^SISI: <srvProfileId>, <srvState>, <rxCount>, <txCount>, <ackData>, <unackData>][^SISI: ...]

If response is related to service profile(s) created / opened on other interface(s):[^SISI: <srvProfileId>, <srvParmTag>value "srvType"][^SISI: ...]OKERROR

Write Command

AT^SISI=<srvProfileId>Response(s)

^SISI: <srvProfileId>, <srvState>, <rxCount>, <txCount>, <ackData>, <unackData>OKERROR+CME ERROR: <err>


- + + + + + - -

BGS3 AT Command Set 10.4 AT^SISI



Internet service profile identifier as defined by AT^SISS (<srvProfileId>). 0...9

Internet service state (for details see AT^SISO parameter <srvState>). 2 Allocated3 Connecting4 Up5 Closing6 Down

Number of bytes received via AT^SISR or AT^SIST since last successful AT^SISO write command. This is the same value as displayed by the AT^SISO read command with the parameter <rxCount>.

Number of bytes sent via AT^SISW or AT^SIST since last successful AT^SISO write command. This is the same value as displayed by the AT^SISO read command with the parameter <txCount>.

Number of data bytes already sent and acknowledged at TCP layer. Value 0 indicates that no sent data isacknowledged yet. Parameter is not applicable to HTTP, POP3, SMTP and Socket with UDP. For these services the counter isalways set to 0.

Number of data bytes already sent but not yet acknowledged at TCP layer. A value 0 indicates that all sent datais already acknowledged. This is the same value as displayed in the response of the AT^SISW write command with the parameter<unackData>. Parameter is not applicable to HTTP, POP3, SMTP and Socket with UDP. For these services the counter isalways set to 0.

Note• If a service is in state "Down" the responses for <rxCount>, <txCount>, <ackData> and <unackData>

are the last known values for the service in the states "Connecting", "Up" and "Closing".

<srvProfileId>(num)

<srvState>(num)

<rxCount>(num)

<txCount>(num)

<ackData>(num)

<unackData>(num)

BGS3 AT Command Set 10.5 AT^SISO


10.5 AT^SISO Internet Service Open

The AT^SISO write command starts the Internet session configured by the service profile. All further stepsneeded to control the session depend on whether you are using URC mode or polling mode. The AT^SISO readcommand returns the current status of all services.

URC mode:If the service opens successfully, the URCs "^SISW" and "^SISR" will trigger the action to follow, either writingdata with AT^SISW or reading data with AT^SISR. To terminate an upload data stream set the <eodFlag>within the last AT^SISW command. If the URCs notify that a data transfer has been successful ("^SISR: x, 2" or"^SISW: x, 2"), the service can be closed with AT^SISC. If a special event occurs, e.g. an error or a warning,after opening or while using a service then the URC type "^SIS" will be delivered.

Polling mode:After opening the service, all progress information needed to control the session shall be explicitly requested bythe host application. The particular sequence of AT commands varies depending on the service used. The fol-lowing list summarizes, by way of an example, the steps normally involved in managing an upload or downloadjob. • Upload (Socket, FTP, HTTP,SMTP):

- Enter the AT^SISO command, e.g. AT^SISO=9.- Enter AT^SISW, specify <reqWriteLength>, e.g. AT^SISW=9,20. Check resulting response for <cnf-

WriteLength>. Optionally, check error with AT^SISE, e.g. AT^SISE=9. If necessary, repeat thesequence several times.

- Enter last AT^SISW command and enable <eodFlag>, e.g. AT^SISW=9,0,1. If Socket service: Query available data with AT^SISR, e.g. AT^SISR=9,1430.

- Check service state with AT^SISI, e.g. AT^SISI=9, if necessary several times until <srvState>=6("Down").

- Check error with AT^SISE, e.g. AT^SISE=9. - Close service with AT^SISC, e.g. AT^SISC=9.

• Download (Socket, FTP, HTTP, POP3): - Enter the AT^SISO command, e.g. AT^SISO=9.- Enter AT^SISR, specify <reqReadLength>, e.g. AT^SISR=9,1000. Check resulting response for

<cnfReadLength>. If necessary, repeat the sequence several times until <cnfReadLength>= -2 (endof data) or ERROR.

- Check error with AT^SISE, e.g. AT^SISE=9. - Close service with AT^SISC, e.g. AT^SISC=9.

• Socket service (upload and download possible in one session): - Recommended: Set AT+CMEE=2 to enable extended error text. - Enter the AT^SISO command, e.g. AT^SISO=9.- Enter AT^SISR or AT^SISW, specifying <reqReadLength> or <reqWriteLength>, e.g.

AT^SISR=9,20 or AT^SISW=9,20. Check resulting response for <cnfReadLength> or <cnfWrite-Length>. If necessary, repeat the sequence several times.

- Check error with AT^SISE, e.g. AT^SISE=9. - If write action: Enter last AT^SISW command and enable <eodFlag>, e.g. AT^SISW=9,0,1.

If Socket service: Query available data with AT^SISR, e.g. AT^SISR=9,1430. - Close service with AT^SISC, e.g. AT^SISC=9.

• Transparent TCP service: - Enter the AT^SISO command, e.g. AT^SISO=9.- Enter AT^SIST to enter transparent data mode. After communication has finished return to AT command

mode via +++ escape sequence.- Check error with AT^SISE, e.g. AT^SISE=9. - Close service with AT^SISC, e.g. AT^SISC=9.



Syntax


<srvProfileId> 0 ... 9 specified with AT^SISS.

Internet service state. Please note, that the state of an Internet service may influence the state of the serial DCD line. For details seedescription of value 2 for parameter <value> of command AT&C. 2 Allocated

Service profile resources are allocated, i.e. at least the service type has beenset (parameter <srvParmTag>, value "srvType" of AT^SISS). The service isnot opened, but ready for configuration.

3 Connecting State after opening a service with AT^SISO where the connection is beingestablished. If connection setup is successful the service proceeds to the state "4" (Up) andone of the URCs "^SISW" and "^SISR" may follow. If connection setup is notsuccessful, the "^SIS" URC may appear and the service enters <srvState>6 (Down). In the case of FTP, <srvState>=3 means that the command channel is beingestablished.If the service profile is configured as Socket listener, then the listener alwaysstays at <srvState>=3 and <socketState>=3 (LISTENER), while the<srvState> and <socketState> of the dynamically assigned service pro-file may change. See examples in Section 10.5.1.

Test Command

AT^SISO=?Response(s)

OK

Read Command

AT^SISO?Response(s)

^SISO: <srvProfileId>, <srvParmTag>value "srvType" [, <srvState>, <socketState>, <rxCount>, <txCount>, <locAddr>, <remAddr>][^SISO: ...]OK

Write Command

AT^SISO=<srvProfileId>Response(s)



± + + + + + - -

<srvProfileId>(num)

<srvState>(num)



4 Up The service performs its purpose. The data transfer process is the major func-tion at this state.FTP: Data channel is up.SMTP: The SMTP service will not enter <srvState>=4 until the host has writ-ten the first data packet with AT^SISW.

5 Closing Internet Service is closing the network connection.FTP: Command channel is released.

6 Down This state is entered if - the service has successfully finished its session (see note on Socket), - the remote peer has reset the connection or - the IP connection has been closed because of an error (see note below onservice or network errors).

If a service in this state be sure to close it with AT^SISC before reopening it.

Socket state identifier. 0 Same as value "1", but applicable only if service profile is POP3. 1 Socket not assigned, i.e. no TCP/UDP connection active. 2 Socket assigned as CLIENT. 3 Socket assigned as LISTENER. 4 Socket assigned as SERVER.

Number of bytes received via AT^SISR or AT^SIST since last successful AT^SISO write command.

Number of bytes sent via AT^SISW or AT^SIST since last successful AT^SISO write command.

Recently used local IP address in dotted-four-byte format and TCP port, separated by colon, e.g."192.60.10.10:80".

Remote IP address in dotted-four-byte format and TCP port, separated by colon, e.g. "192.60.10.10:80".

Notes• If the bearer cannot be established and AT^SISO returns an error there might be a general GSM/GPRS prob-

lem. To identify the reason you can take advantage of the AT+CEER command. Using AT+CEER is especiallyrecommended when the <infoID> parameter of the AT^SISE command equals 0.

• If a service or network error occurs during an IP session and the "^SIS" URC or the AT^SISE command dis-play an error message, the service enters <srvState>=5 and then 6, i.e. the IP connection is closed. In thiscase, the service still allows reading the data stored in the buffer, but writing data is denied. After reading,close the service and open it again.

<socketState>(num)

<rxCount>(num)

<txCount>(num)

<locAddr>(str)

<remAddr>(str)



• As in polling mode no error URCs are available you are advised to integrate the commands AT^SISI andAT^SISE into the command sequences for upload and download jobs. So, the AT^SISO command may befollowed by AT^SISI to check that the service has entered the <srvState>=4 before sending AT^SISR,AT^SISW or AT^SIST. This helps you to detect errors even though the "^SIS" URCs are disabled. A typicalexample is that the service fails to be opened because the service profile contains a wrong destinationaddress. In such a case, after opening with AT^SISO and OK response, the service quickly enters the states<srvState>=2, 4 and 6, with an error being returned no earlier than after sending the first AT^SISR orAT^SISW command. In URC mode, an error URC, such as "Host not found" would be received in this situa-tion, but in polling mode the only way to detect the state is using AT^SISI or, alternatively, AT^SISO.

• If the user rapidly closes and opens TCP/IP connections based on the embedded TCP/IP stack the servicemay display the error "No buffer space available", meaning that all TCP/IP socket resources are exhausted.In the worst case, opening further TCP/IP connections is locked for up to 60 seconds.

• The Socket Listener may not work properly if the service is re-opened shortly after having closed the SocketListener. To ensure that the service works correctly the host is required to wait at least two minutes before re-opening a Listener.



10.5.1 Example: Accepting / Rejecting Socket Connection Request from Remote Client

Host 1 configured as Socket listener with IP address 10.10.0.187 at port 65534 is receiving a connection requestfrom the remote client 10.10.0.185 (at port 1024). The example assumes that connection and service profileshave been created as stated earlier.

Start the Socket service in listener mode, then query the IP address dynamically assigned to the Socket listener:

Indication of incoming Socket connection request:

Host 1 accepts the Socket connection request:

at^siso=4 Host 1 opens the Socket service.at^siso? Query the current status of all services. All service

profiles are unused, except for service profile 4which is running in listener mode, where<srvState>=3 (listening) and <socketState>=3(LISTENER). The response also indicates the IPaddress dynamically assigned to the listener. The lis-tener's access data (IP address and TCP port num-ber) shall be passed on to the client.

^SISO: 0, ""^SISO: 1, ""^SISO: 2, ""^SISO: 3, ""

^SISO: 4, "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0"^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OK

^SIS: 4, 1, 0 The URC indicates that the listener configured onservice profile 4 is receiving a Socket connectionrequest (<urcCause>=1) from the remote client.The last URC parameter <urcInfoId> representsthe ID of the dynamically assigned service profile,here 0.

at^siso? Query the current status of services.^SISO: 0, "Socket","2","4","0","0", "10.10.0.187:0","10.10.0.185:1024"

Indication on host 1 that the connection request fromthe remote client has been dynamically assigned toservice profile 0 which is set to Server mode(<socketState>=4).

^SISO: 1, ""^SISO: 2, ""^SISO: 3, ""^SISO: 4, "Socket","3","3","0","0", "10.10.0.187:65534","0.0.0.0:0"^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OK

at^siso=0 Host 1 accepts the connection request, where 0 isthe ID of the dynamically assigned service profile.OK

^SISW: 0, 1 The URC indicates that data transmission to theremote client is possible. If the remote client hasalready sent some data the additional URC ^SISR:0,1 is displayed.

at^siso? Query the current status of services.^SISO: 0, "Socket","4","4","0","0", "10.10.0.187:65534","10.10.0.185:1024"

The socket connection between host 1 and remoteclient is successfully established.

^SISO: 1, ""^SISO: 2, ""^SISO: 3, ""^SISO: 4, "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0"



Host 1 rejects the Socket connection request:

^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OK

at^sisc=0 Host 1 rejects the connection request, where 0 is theID of the dynamically assigned service profile.OK

at^siso? Query the current status of services.^SISO: 0, "" The dynamically assigned service profile is free

again. The Socket listener stays at <srvState>=3(listening) and <socketState>=3 (LISTENER).

^SISO: 1, ""^SISO: 2, ""^SISO: 3, ""^SISO: 4, "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0"^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OK

BGS3 AT Command Set 10.6 AT^SISC


10.6 AT^SISC Internet Service Close

The AT^SISC write command closes the TCP/IP connection to the remote peer which was opened withAT^SISO. All resources are released, all status information parameters, e.g. <srvState>, <unackData>,<ackData>, <rxCount> and <txCount> counters, are reset. Only the initial configuration settings are pre-served. The service can be restarted any time, using the same configuration or a new one.

Syntax


0...9 <srvProfileId> specified with AT^SISS.

Test Command

AT^SISC=?Response(s)

OK

Write Command

AT^SISC=<srvProfileId>Response(s)



± + + + + + - -

<srvProfileId>(num)

BGS3 AT Command Set 10.7 AT^SISR


10.7 AT^SISR Internet Service Read Data

The AT^SISR command either triggers a read operation (download) or queries the number of bytes in the internalbuffer. The "^SISR: x, 1" URC is also used to report status changes of the transparent TCP service while the client isin AT command mode.

The AT^SISR write command may return the following errors: • "+CME ERROR: operation failed" if there is a problem on application, socket, PPP or GPRS/GSM level. The

AT^SISE command and the "^SIS" URC offer additional error information. • "+CME ERROR: operation temporary not allowed" e.g. if the service has not network resources allocated. • "+CME ERROR: operation not allowed" e.g. if the service is not configured.

Syntax

Unsolicited Result Code^SISR: <srvProfileId>, <urcCauseId>

Data availability status of the Internet service configured with AT^SISS has changed. The URC is issued when: • data is available after opening an Internet service or • less data was confirmed (in <cnfReadLength>) than requested (with <reqReadLength>) during the last

"Read Data" operation and new data is available. The URC is disabled in polling mode. See AT^SCFG, parameter "Tcp/WithURCs", <tcpWithUrc>.



Test Command

AT^SISR=?Response(s)

OK

Write Command

AT^SISR=<srvProfileId>, <reqReadLength>Response(s)

^SISR: <srvProfileId>, <cnfReadLength>[, <remainUdpPacketLength>[, <optServParm>]]Number of data bytes are sent as specified by <cnfReadLength>. If peek operator was used no data bytes are sent. OKERROR+CME ERROR: <err>


± + + + + + - +

<srvProfileId>(num)



0 Peek Operator: Query number of received bytes within internal buffers. The behaviour of the peek operator depends on the selected Internet service,i.e. it may not be supported by all IP Services. For "Socket" service configured for UDP the size of the next available UDPpacket is returned.

1...1500 Requested number of data bytes to be read via the Internet service specifiedin <srvProfileId>.

-2 Indicates end of data. Data transfer has been finished (all data have been read)and the service can be closed with AT^SISC.

-1 Applies only to HTTP: Querying number of available bytes is not supported bythe HTTP service.

0 Indicates that no further data is available at the moment. >0 Number of available data bytes. The range is determined by

<reqReadLength>:If <reqReadLength> was greater than 0, then <cnfReadLength> may beless or equal to the value requested with <reqReadLength>. If <reqReadLength> equals 0 (peek operator) the value indicated by<cnfReadLength> may be greater than 1500.

Indicates whether or not data is available for reading with AT^SISR and AT^SIST. 1 Meaning of value "1" for all services except Transparent TCP service:

Data is available and can be read by sending the AT^SISR command. TheURC appears when less data was confirmed (in <cnfReadLength>) thanrequested (with <reqReadLength>) during the last "Read Data" operationand new data is available.

Meaning of value "1" for Transparent TCP service: If the Transparent TCP service is in AT command mode the "^SISR: x, 1" URCnotifies the client that the server has sent new data. In this case the client shallenter the AT^SIST command to go to transparent access mode and read thedata.

2 End of data. Data transfer has completed (all data read). The service can beclosed with AT^SISC.

Optional third parameter of the AT^SISR write command response displayed only if the Socket service uses theUDP protocol. The reception of each datagram must be completed before the next datagram can be received. This may be aproblem if the buffer of the host application is limited and not designed to handle the maximum packet size of1500 bytes. To compensate this, the host is advised to request, via <reqReadLength>, an amount less orequal its maxmimum buffer capacity and wait for the resulting AT^SISR write command response with param-eter <remainUdpPacketLength>. The benefit of this approach is that the host may properly receive all partsof a UDP datagram, as after each received data part the number of remaining bytes is synchronized, until read-ing the datagram is finished.

<reqReadLength>(num)

<cnfReadLength>(num)

<urcCauseId>(num)

<remainUdpPacketLength>(num)



If the currently read datagram is smaller than the number of bytes requested by the host the <remainUdpPack-etLength> parameter is omitted. Further write attempts with AT^SISR are denied as long as the <remainUdpPacketLength> is unequal 0 oris not omitted. In this case the service returns "+CME ERROR: operation of service temporary not allowed". 0 Indicates that all bytes of the current UDP datagram are read. 1...(max. data size)-1 Indicates that the currently read UDP datagram is not yet complete. The dis-

played value is the remaining number of bytes. <remainUdpPacketLength> is unequal 0 until reading all parts of the cur-rent datagram is finished.

Service specific parameter of the AT^SISR write command response. If the Socket service is configured as UDPendpoint this parameter returns the IP address and the UDP port of the remote host that has sent the currentUDP data.

10.7.1 Example: Socket Host Reads Small Amounts of UDP Data Pack-ets (URC Mode)

This section applies only to the Socket service using the UDP protocol. The example shows how to read UDPpackets if the buffer of the host application can handle only a few bytes. There are two datagrams available forreading. Buffer size: 6 bytesDatagram A = 18 bytes (content "THIS_IS_DATAGRAM_A")Datagram B = 3 bytes (content "NEW")

<optServParm>(str)

^SISR: 0,1 Service profile 0 is configured for Socket service and UDP. The URCnotifies host that data is available for reading.

at^sisr=0,6 The host requests to read 6 bytes.^SISR: 0,6,12THIS_I

The first 6 bytes of datagram A are confirmed and transmitted. Another12 bytes are still available.

OKat^sisr=0,6 The host requests to read the next part of 6 bytes.^SISR: 0,6,6S_DATA

The next 6 bytes of datagram A are confirmed and transmitted. Another6 bytes are still available.

OKat^sisr=0,6 The host requests to read the next part of 6 bytes.^SISR: 0,6,0GRAM_A

Last part of datagram A was received, no remainder is left.

OKat^sisr=0,6 Again, the host requests to read 6 bytes. This time, the request refers to

datagram B which has only 3 bytes. As the read datagram is smallerthan the size requested by the host, the response does not include the<remainUdpPacketLength>.

^SISR: 0,3NEW

3 bytes are confirmed and transmitted. Datagram B was properlyreceived.

OK

BGS3 AT Command Set 10.8 AT^SISW


10.8 AT^SISW Internet Service Write Data

The AT^SISW command triggers a write operation (upload) and queries the amount of data already sent, but notacknowledged at the TCP layer. The write operation may be run in binary mode, or in interactive text mode.

The AT^SISW write command may return the following errors: • "+CME ERROR: operation failed" if there is a problem on application, socket, PPP or GPRS/GSM level. The

AT^SISE command and the "^SIS" URC offer additional error information. • "+CME ERROR: operation temporary not allowed" e.g. if the service has not network resources allocated. • "+CME ERROR: operation not allowed" e.g. if the service is not configured.

Syntax

Unsolicited Result Code^SISW: <srvProfileId>, <urcCauseId>

Data availability status of the Internet service configured with AT^SISS has changed. The URC is issued whenthe service is ready to accept new user data. In this context the URC is also issued for Transparent TCP servicethat supports data transfer via AT^SIST only. The URC is disabled in polling mode. See AT^SCFG, parameter "Tcp/WithURCs", <tcpWithUrc>.



0...1500Specifies the number of bytes to be sent with AT^SISW or, if set to 0, requests the amount of data already sentwith AT^SISW but not yet acknowledged: • Parameter <reqWriteLength> may be 1...1500 bytes to specify the amount of data to be sent withAT^SISW.

• If parameter <reqWriteLength> equals 0, AT^SISW does not expect any data, but a normal query is per-fomed. This allows the application to explictly request, in particular at the end of an upload job, the amount ofunacknowledged data at the TCP layer indicated by <unackData>.

• In interactive text mode, <reqWriteLength> must be set to any value greater than 0 (but not necessarilythe precise number of bytes). If set to 0 in interactive text mode, <reqWriteLength> would be interpreted

Test Command

AT^SISW=?Response(s)

OK

Write Command

AT^SISW=<srvProfileId>, <reqWriteLength>[, <eodFlag>[, <mode>[, <optServParam>]]]Response(s)

^SISW: <srvProfileId>, <cnfWriteLength>, <unackData>Number of data bytes as specified by <cnfWriteLength>. OKERROR+CME ERROR: <err>


± + + + + + - +

<srvProfileId>(num)

<reqWriteLength>(num)



as query for unacknowledged data and, thus, prevent data transfer. • If Socket service is selected with UDP protocol

- <reqWriteLength>=0 can be used to send an empty UDP packet; - it is recommended that the size of each data packet be limited to 1472 bytes. Otherwise, it is possible that

the following URC occurs: "^SIS: <id>, 0, 9, The supplied buffer was too small / large".

End of data indication flag.Parameter is ignored for HTTP, POP3, FTP download, Socket with UDP protocol. [0] No end of data. Other data may follow to be transmitted via the Internet service. 1 End of data is signalled to the Internet Service. Further AT^SISW write com-

mands return an error response. However, reading data may be possible. The<eodFlag> is effective only if the <reqWriteLength> equals <cnfWrite-Length>, in particular if the <reqWriteLength> equals 0.If <mode> equals 1 the <eodFlag> is effective only if the write operation hasbeen finished with CTRL-Z.

Control how the application provides the data bytes to be sent. [0] Binary mode

This mode allows sending a number of bytes defined with parameter<reqWriteLength>.

1 Interactive text mode This mode allows the user to type and send 8-bit ASCII characters while theservice is open. Ctrl-Z terminates data input and causes the data to be trans-ferred.Interactive text mode requires that the <reqWriteLength> is set to any valuegreater than 0 (though it is not necessary to specify the precise number ofbytes). In this case the <cnfWriteLength> parameter indicates the maxi-mum length of the data stream without control character CTRL-Z. In interactive text mode, the following characters are predefined as controlcodes: • BACKSPACE ("\x08") deletes the last given character, • CTRL-Z ("\x1a") terminates the input, • ESC ("\x1b") aborts the command. An <eodFlag> is ignored in this case. The V.25 command ATE also controls the echo mode of the interactive textmode. If echo is enabled (ATE1) all characters are echoed until <cnfWrite-Length> is reached. Any attempt to input further data ends up with the warn-ing message 4001 indicated after the data stream has been completed withCTRL-Z, nevertheless all data within the range of <cnfWriteLength> will besent. See also Section 10.14, Internet Service URC "^SIS". ATE0 disables theecho mode generally.

Service specific parameter of the AT^SISW write command. If the Socket service is configured as UDP endpointthis parameter is mandatory and specifies the IP address (in dotted format) and the UDP port of the remote host.For each write request another IP address and UDP port may be given.

0...1500 Confirmed number of data bytes which can be transmitted via the Internet ser-vice configured in <srvProfileId>. In binary mode (see <mode>) this num-ber may be less or equal to the value requested with <reqWriteLength>.The application has to deliver exactly the number of bytes indicated by <cnf-

<eodFlag>(num)

<mode>(num)

<optServParam>(str)

<cnfWriteLength>(num)



WriteLength>. A 0 value means that no data can be written at this time, i.e.it serves as a flow control mechanism. In interactive text mode, <cnfWriteLength> indicates the maximum numberof bytes it can process. Characters above the indicated number are ignored.

Number of data bytes already sent but not yet acknowledged at the TCP layer. The value is constantly changing until the entire upload job has completed. If the value equals 0 all data sent sofar is acknowledged. In binary mode, <unackData> includes the <cnfWriteLength> value of the pending write operation. There-fore, the very first write operation of an upload job returns identical values for <cnfWriteLength> and<unackData>. This mechanism allows the host application to easily verify whether or not the remote host has successfullyreceived the data. Parameter is not applicable to HTTP, POP3, SMTP and Socket with UDP protocol. For these services thecounter is always set to 0.

1 The service is ready to accept new user data. 2 Data transfer has been finished successfully and Internet service may be

closed without loss of data.

Notes• The AT^SISW write command must be terminated only with the ASCII character set with ATS3. The factory

default for S3 is #13 (Carriage Return). Do not send any further characters after the S3 end-of-line identifier,until the response "^SISW" is received. This is necessary to avoid that any characters related to the AT com-mand can be interpreted as being part of the data stream to be transferred. Also refer to Section 1.4, AT Com-mand Syntax.

• If the Socket service is configured for use as UDP client and fixed size and the interactive text mode is active,the PDU length always equals the specified fixed length. If the input characters exceed the specified fixedlength, then all surplus characters will be ignored. If the input characters are less than the specified fixedlength, then the remaining range will be filled with "\0" bytes.

10.8.1 Usage of parameter <eodFlag>

<unackData>(num)

<urcCauseId>(num)

Service type Socket After the service accepts the end-of-data flag the service state changes to "Closing". No fur-

ther user data is accepted. After releasing the TCP link the service remains in state "Down".Parameter is not applicable to Socket with UDP protocol, i.e. value is ignored.

FTP Parameter only applicable for FTP upload session. After accepting the end-of-data flag the service state changes to "Closing" and starts to end the running FTP session. No further user data is accepted. After the FTP session is completed on FTP protocol level the service state switches to "Down". In case of successful completion the URC "^SISW: x,2" is generated.



SMTP SMTP service sends some "closing" commands to the SMTP server which are necessary to mark the email as successfully sent on the server. The service enters "Closing" state and remains in it until the final protocol exchange with the SMTP server has been completed. The "OK" response following AT^SISW indicates that the SMTP service has accepted the last data - IT DOES NOT indicate the successful completion of the SMTP service. Successful completion will be indicated either by the appropriate URC "^SISW:x,2" or due to the fact that the SMTP service state changes to "Down" state without any error.

HTTP / POP3 Parameter not applicable, i.e. value is ignored.

Service type

BGS3 AT Command Set 10.9 AT^SIST


10.9 AT^SIST Enter Transparent Access Mode

The AT^SIST command applies only to the Transparent TCP service defined with AT^SISS. It can be used afterthe Transparent service has been opened with AT^SISO and is in "Up" state (<srvState>=4). If the service isnot "Up" trying to open it will be denied with "+CME ERROR: operation temporary not allowed".

There are two ways to verify that the service is "Up": Each time after opening the service with AT^SISO wait forthe "^SISW: x, 1" URC (if URC mode is enabled). In addition, or when using Polling mode, you can request the<srvState> with AT^SISO or AT^SISI.

Then, after entering the AT^SIST command, the CONNECT response notifies that the service has entered trans-parent access mode and is ready to transparently send and receive payload data over the serial interface. In thismode, the signaling of URCs is dependent on the settings made with AT^SCFG, parameter <udri>.

There are several ways to quit the transparent access mode and revert to AT command mode: • +++ escape sequence (also transmitted over the air) • DTR ON-OFF transition (see AT&D for configuring DTR line) • "etx" parameter set within the server address for transparent access mode (see AT^SISS, <srvParmTag>

"address". Switching back and forth between both modes does not affect the underlying socket and has no influence on theservice <srvState>. If the service is in AT command mode the "^SISR: x, 1" URC appears once notifying the client that the serverhas sent new data. In this case, the client shall enter AT^SIST to go to transparent access mode and read outthe new data.

If the Transparent service is released by the server the following applies:• If the service is in transparent access mode (CONNECT mode): ME returns to AT command mode, issues a

specific "NO CARRIER" result code and goes to <srvState> 6 ("Down"). The "NO CARRIER" result codestarts with 0x10 (DLE) and 0x04 (EOT) and ends with the characters defined by ATS3 and ATS4.

• If the service is in AT command mode the "^SISR: x, 1" URC appears once notifying the client that the statusof the transparent TCP service has changed. In this case, the client shall go to transparent access mode withAT^SIST in order to read remaining data (if any) and get the "NO CARRIER" result code. After this, the ser-vice changes to <srvState> 6 ("Down"). Otherwise, if the client does not go to transparent access modeafter receiving "^SISR: x, 1" URC the service remains in <srvState> 4 ("Up") even though the remoteserver has shut down. In some cases, depending on the remote server and the network, it is possible that "^SIS" URCs may bereported, for example "^SIS" URCs with <urcInfoId> 15 ("Remote host has reset the connection") and 19("Socket has been shut down). See Section 10.14, Internet Service URC "^SIS" for a list of possible URCs.

• In all above scenarios, the Transparent TCP service shall be closed with AT^SISC. Trying to return to trans-parent access mode with AT^SIST would only end up with "NO CARRIER" once again and is not recom-mended.

• Use AT^SISO and AT^SISI to check the <srvState>.

SyntaxTest Command

AT^SIST=?Response(s)

OK

Write Command

AT^SIST=<srvProfileId>Response(s)

CONNECT(indicates that ME has entered transparent access mode)OK

BGS3 AT Command Set 10.9 AT^SIST




ERROR+CME ERROR: <err>


- + + + + + - +

<srvProfileId>(num)

Write Command (Continued)

AT^SIST=<srvProfileId>Response(s)

BGS3 AT Command Set 10.10 AT^SICO


10.10 AT^SICO Internet Connection Open

The AT^SICO write command opens a connection profile (also referred to as bearer). Unlike the AT^SISO com-mand which starts a connection profile and the service profile bound to it, AT^SICO activates only the selectedconnection profile. Another difference over AT^SISO is that AT^SICO disables the inactivity timeout of theselected connection profile and, therefore, sets the "inactTO" value to -1 (see also AT^SICS). To release theconnection use the close command AT^SICC. Closing the bearer restores the previously set "inactTO" value ofthe concerned connection profile.

The AT^SICO command may be used, for example, to keep a bearer open while no service is active (i.e. whileno service has been opened with AT^SISO). Also, the AT^SICO command is necessary for running the Pingcommand AT^SISX when no service has been opened with AT^SISO.

A connection opened with AT^SICO remains open until closed with AT^SICC or, in case of inactivity, discon-nected by the network after 25 hours usually. The network initiated disconnection can be avoided by sendingAT^SISX at regular intervals (Ping). The Round Trip Time (RTT) of the AT^SISX command strongly dependson the data traffic of the IP services or DUN connections used at the same time.

Please note that after sending the AT^SICO write command the AT channel is blocked until the connection isestablished. The command may be aborted when receiving any character during execution, e.g. "AT" or "at".

The AT^SICO read command requests the current settings of all Internet connection profiles set with AT^SISC.The output is identical with the read command response of AT^SISC. One line is issued for every possibleparameter of a given <conParmTag> value.

Syntax


0...5 Internet connection profile identifier defined with parameter <conProfileId>of AT^SICS.

Test Command

AT^SICO=?Response(s)

[^SICO:(list of defined <conProfileId>s)]OK

Read Command

AT^SICO?Response(s)

[^SICO: <conProfileId>, <conParmTag>, <conParmValue>][^SICO: ...]OK

Write Command

AT^SICO=<conProfileId>Response(s)



+ + + + + + - -

<conProfileId>(num)

BGS3 AT Command Set 10.10 AT^SICO


Internet connection profile identifier defined with parameter <conParmTag> of AT^SICS. See parameterdescription of AT^SICS.

Internet connection parameter set with <conParmValue> of AT^SICS. See parameter description of AT^SICS.

Note• Be sure not to mix up the start and close commands for connection profiles and service profiles. It is allowed

to use only the combinations AT^SICO / AT^SICC or AT^SISO / AT^SISC.

<conParmTag>(str)

<conParmValue>(str)

BGS3 AT Command Set 10.11 AT^SICC


10.11 AT^SICC Internet Connection Close

The AT^SICC write command releases a connection opened with AT^SICO and restores the previously set inac-tivity timeout "inactTO" of the selected connection profile.

The command returns an error if any services are bound to this profile. Before using the AT^SICC write com-mand be sure that all services were closed with AT^SISC.

Syntax



Note• Be sure not to mix up the start and close commands connection profiles and service profiles. It is allowed to

use only the combinations AT^SICO / AT^SICC or AT^SISO / AT^SISC.

Test Command

AT^SICC=?Response(s)

[^SICC:(list of defined <conProfileId>s)]OK

Write Command

AT^SICC=<conProfileId>Response(s)



+ + + + + + - -

<conProfileId>(num)

BGS3 AT Command Set 10.12 AT^SISX


10.12 AT^SISX Internet Service Execution

The AT^SISX command sends ICMP (Internet Control Message Protocol) Echo Requests to a target IP addressor host name (also referred to as Ping command).

The AT^SISX command can be used any time while a connection profile, i.e. a bearer, is active. The bearer mayhave been started either with AT^SICO, or if a service is in use, with AT^SISO. If issued although no bearer isactive or no connection profile created at all, AT^SISX returns ERROR.

The AT^SISX write command starts the available service type <service>, i.e. the ping command. The com-mand returns one row for every ICMP Echo Request (max. 30 lines, see parameter <request>). The last Pingresponse line is followed by an empty line, then another two lines appear to report a statistic calculated from theEcho Request responses. To stop the periodic ping type any character, e.g. "AT" or "at". After calling the pingcommand the AT channel is blocked until all ICMP requests are executed.

Sending the Ping command does not restart the inactivity timeout "inactTO" of the used connection profile (seeAT^SICS), i.e. if the bearer was opened with AT^SICO the "inactTO" value remains "-1" (= inactivity timeout dis-abled), and if the bearer was opened with AT^SISO the "inactTO" value set with AT^SICS remains applicable.The Ping command can only be used to prevent that a network initiated inactivity timeout closes the bearer (seealso description of AT^SICO).

SyntaxTest Command

AT^SISX=?Response(s)

^SISX:<service>, (list of supported <conProfileId>s), <address>, (range of <request>), (range of <timelimit>)OK

Write Command

AT^SISX=<service>, <conProfileId>, <address>[, <request>, <timelimit>]Response(s)

In case of <pingInfoType>= 1: ICMP Echo Requests (1 - 30 rows)^SISX:<service>, <pingInfoType>, <conProfileId>, <address>, <roundTripTime>[...]

In case of <pingInfoType>= 2: Packet statistic (1 row)^SISX:<service>, <pingInfoType>, <conProfileId>, <sent>, <received>, <lost>, <lostPercent>

In case of <pingInfoType>= 3: Time statistic (1 row)^SISX:<service>, <pingInfoType>, <conProfileId>, <minRTT>, <maxRTT>, <meanRTT>



+ + + + + + - -




“Ping“ Service type.


Target host name or IP address for pinging (i.e. 192.168.1.3).

[1]...30 Number of ping requests (ICMP Echo Requests).

200...[5000]...10000 Amount of time, in milliseconds, to wait for an Echo Response message relatedto a sent Echo Request message.

Marks the type and format of the information given in the command responses (see syntax of the AT^SISX writecommand above). 1 Ping response(s) received for the ICMP Echo Request(s). Depending on

parameter <request> 1 - 30 rows. Address and Round Trip Time are returnedfor each request.

2 1-row packet statistic calculated from the ping response(s) received for<pingInfoType>=1.

3 1-row time statistics calculated from the ping response(s) received for <ping-InfoType>=1.

Round Trip Time in milliseconds. If the Echo Response message is not received within the time specified by<timelimit> the value -1 is returned (e.g. when the bearer shuts down during command execution).

Number of sent packets.

Number of received packets.

Number of lost packets.

Lost packets in percent.

Minimum Round Trip Time in milliseconds.

<service>(str)

<conProfileId>(num)

<address>(str)

<request>(num)

<timelimit>(num)

<pingInfoType>(num)

<roundTripTime>(num)

<sent>(num)

<received>(num)

<lost>(num)

<lostPercent>(num)

<minRTT>(num)



Maximum Round Trip Time in milliseconds.

Average Round Trip Time in milliseconds.

10.12.1 Example: Ping

The following example shows a Ping output:

<maxRTT>(num)

<meanRTT>(num)

AT^SICS=0,conType,GPRS0 Select connection type GPRS0.OKAT^SICS=0,apn,"GPRS02.point.de"AT^SICO=0OKAT^SISX="Ping",0,192.168.1.2,4,2000^SISX: "Ping",1,0,"192.168.1.2",1043^SISX: "Ping",1,0,"192.168.1.2",586^SISX: "Ping",1,0,"192.168.1.2",531^SISX: "Ping",1,0,"192.168.1.2",415

^SISX: "Ping",2,1,4,4,0,0^SISX: "Ping",3,1,415,1043,643OK

BGS3 AT Command Set 10.13 AT^SISE


10.13 AT^SISE Internet Service Error Report

The AT^SISE write command returns the current error status of the specified Internet service profile. If the ser-vice profile is not defined or the value is invalid "+CME ERROR" response is returned. The error status is identical to the content of the "^SIS" URC last issued. If a service fails the commands AT^SISR, AT^SISW or AT^SIST will return an error response. However, if theAT^SISE command returns <infoID>=0 it is recommended to use the AT+CEER command because a generalGSM/GPRS problem might be the reason.

Syntax


Internet service profile identifier as defined by AT^SISS <srvProfileId>. 0...9

Reason for Internet service error. This is a subset of the <urcInfoId>s which can be found in Section 10.14,Internet Service URC "^SIS". The value 0 indicates there is no special Internet service error. In this case the application may use AT+CEERto check for general GSM/GPRS problems.

Information text related to <infoID>. This is a subset of the <urcInfoText>s which can be found in Section10.14, Internet Service URC "^SIS".

Note• In particular cases, the AT^SISE command may deliver information and warnings. This applies the following

services:FTP: Information 2100POP3: WarningsSMTP: WarningsIf an error occurs the information and warning messages are overwritten by error messages.

Test Command

AT^SISE=?Response(s)

OK

Write Command

AT^SISE=<srvProfileId>Response(s)

^SISE: <srvProfileId>, <infoID>[, <info>]OKERROR+CME ERROR: <err>


- + + + + + - -

<srvProfileId>(num)

<infoID>(num)

<info>(str)

BGS3 AT Command Set 10.14 Internet Service URC "^SIS"


10.14 Internet Service URC "^SIS"

This section first describes the syntax and the parameters of the "^SIS" URC. The second part consists of tableslisting the information elements delivered within the "^SIS" URC and the command response of AT^SISE.

The presentation of the "^SIS" URC containing the parameter <urcCause>=0 can be disabled or enableddepending on whether polling mode or URC mode is preferred. To do so, use the AT^SCFG command, parameter"Tcp/WithURCs" (refer to <tcpWithUrc>). However, if related to <urcCause>=1 or 2, the "^SIS" URC willalways be delivered regardless of the setting made with AT^SCFG.

Unsolicited Result CodeIndicates an event, an error or an information element. The same information can be obtained via AT^SISE. ^SIS: <srvProfileId>, <urcCause>[, [<urcInfoId>][, <urcInfoText>]]

The URC may appear if an event or an error occurs, for example after opening an Internet service with AT^SISOor any time during operation. The URC also indicates a request for a mobile terminated Internet service clientconnection, or a failure if a mobile terminated request is rejected. Furthermore, the URC may deliver an informa-tion element resulting from a specific command given in the service profile.

A list of possible causes can be found in the tables below. The tables contain the <urcInfoId> and, if applica-ble, a specific <urcInfoText>. If marked with *) the precise text related to a <urcInfoId> varies greatlydepending on the scenario and the implementation of the remote server. In these cases, only a brief explanationof the scenario can be found in the table column "Description".


URC cause identifier. 0 An event has occurred after opening or while using an Internet service.

The event number is presented via <urcInfoId> and may be an error, awarning, an information element or a note. Optionally additional informationmay be supplied via <urcInfoText>.

1 Indicates that an opened Socket listener service is receiving a connectionrequest from a remote client. The incoming socket connection is dynamically assigned to the next free Inter-net service profile. In this case, the parameter <urcInfoId> inside the "^SIS"URC equals the <srvProfileId> of the dynamically assigned service pro-file. This ID shall be used to accept the connection request with AT^SISO or toreject it with AT^SISC. The connection status may be requested by using the AT^SISI read or writecommand or the AT^SISO read command. Among other details, the responseindicates the IP address of the remote client (parameter <remAddr>). Thismay be helpful to decide whether to accept or reject the request.

2 Incoming Socket service client connection has failed. The client request wasrejected automatically because no free Internet service profile was available.

Information identifier related to <urcCause>. See tables below for further detail. The <urcInfoId> numberranges indicate the type of information element:0: Service is working properly.1 - 2000: Error, service is aborted and enters <srvState>=6 (Down).2001 - 4000: Information related to progress of service.4001 - 6000: Warning, but no service abort.6001 - 8000: NotesAdditional information for Socket service: As stated above, if a Socket connection request from a remote clientis received (see <urcCause>=1) the <urcInfoId> equals the <srvProfileId> of the dynamically assignedfree service profile.

<urcCause>(num)

<urcInfoId>(num)



Information text related to <urcCause>. See tables below for further detail.

10.14.1 Information Elements Related to the Service Application

The following table lists the informatiomation elements which may be returned by all supported services withinthe "^SIS" URC and the command response of AT^SISE. It should be noted that TCP/IP socket problems mayoccur in all Internet service connections (Socket, Transparent TCP, FTP,HTTP, POP3 or SMTP).

<urcInfoText>(str)

<urcInfoId> <urcInfoText> DescriptionInformation Elements Returned by the TCP/IP socket2 Invalid socket descriptor Socket error3 Bad address specified Socket error4 Invalid operation Socket error5 No free socket descriptors Socket error6 The operation would block Socket error7 A previous attempt at this operation is still ongoing Socket error8 Socket is not bound Socket error9 The supplied buffer is too small / large Socket error10 Flags not supported Socket error11 Operation not supported Socket error12 The address is already in use Socket error13 The network is unavailable Socket error14 An established connection was aborted (transmission

time-out or protocol error)Socket error

15 Remote host has reset the connection Socket error16 No buffer space available Socket error17 The socket is already connected Socket error18 For TCP/IP sockets, the socket is not connected Socket error19 Socket has been shut down Socket error20 Connection timed out Socket error21 Remote host has rejected the connection Socket error22 Remote host is unreachable Socket error23 An unexpected error occurred Socket error24 Host not found DNS error25 An error occurred that may be transient; a further attempt

may succeed.DNS error

26 An unrecoverable error occurred DNS errorGeneral Information Elements46 Fatal: The service has detected an unknown error47 *) Indicates that the remote ser-

vice has closed the connection. The host shall close the service.



*) Text varies depending on scenario.

10.14.2 Information Elements Related to FTP Service

**) Text varies depending on FTP server implementation. See RFC 959 for possible responses.

48 Remote peer has closed the connection Remote peer has closed the connection unexpectedly, and no data are available. The host shall close the service.Note that the "^SIS" URC only indicates the <urcInfoId>, but the AT^SISE command indicates both the <urcIn-foId> and the <urcInfo-Text>.

49 Fatal: No memory is available for service action50 Fatal: Service has detected an internal error80 Connection profile not defined.84 PPP LCP FAILED PPP error85 PAP Authentication failed PPP error86 CHAP Authentication failed PPP error87 IPCP failed PPP errorWarnings4001 Applies only to interactive text

mode: Indicates that number of input characters is greater than <cnfWriteLength>.

General Information Elements6001 General progress information

for connection setup.

<urcInfoId> <urcInfoText> Description100 **) FTP Server rejects session.101 **) FTP Server rejects USER com-

mand.102 **) FTP Server rejects PASS com-

mand.103 **) FTP Server rejects PASV com-

mand or client can't detect remote IP address.

104 **) FTP Server rejects requested client action.

105 **) The given path segment is wrong.

2100 FILE: <filename> File name assigned by FTP server if mode=u is used.

<urcInfoId> <urcInfoText> Description



10.14.3 Information Elements Related to HTTP Service

10.14.4 Information Elements Related to POP3 Service

10.14.5 Information Elements Related to SMTP Service

***) Text varies depending on scenario.

<urcInfoId> <urcInfoText> DescriptionError URCs200 HTTP-ERR: Not connected - cannot send request

HTTP-ERR: failed on sending request 201 <HTTP Response Str> Client error202 <HTTP Response Str>

HTTP-ERR: Service unavailable Server error

203 HTTP-ERR: Redirect failed - too many redirectsHTTP-ERR: Redirect failed - not allowedHTTP-ERR: Redirect failed - location missing

Max. number of allowed redi-rects: 6

204 HTTP-ERR: auth failed - user name or password missingHTTP-ERR: auth failed - user name or password wrongHTTP-ERR: Authority required for this URLHTTP-ERR: No access to this URL allowed

Info URCs2200 HTTP Redirect to: <Host>:<Port> <Path>2201 HTTP Response <Response code>

Example: ^SIS: 2,3,2201, "HTTP Response: HTTP/1.1 200 OK"

<urcInfoId> <urcInfoText> DescriptionErrors300 ***) Indicates that the POP3 User Command could

not be executed successfully.Warnings4300 ***) POP3 specific warning

<urcInfoId> <urcInfoText> DescriptionErrors400 ***) Indicates that the SMTP service could not be

executed successfully.Warnings4400 ***) SMTP specific warning

BGS3 AT Command Set 10.15 Examples of how to Configure and Use Internet Service Profiles


10.15 Examples of how to Configure and Use Internet Service Profiles

Below you can find selective examples of how to configure and use Internet service profiles. To visualize the dif-ference between URC mode and polling mode the operation of services (after opening with AT^SISO) isexplained in separate examples for either mode.

10.15.1 Selecting URC Mode or Polling Mode

To enable or disable the presentation of URCs for the Internet services use the AT^SCFG command, type "TcpIp/WithURCs" and select "on" or "off" for parameter <tcpWithUrc>.

10.15.2 Configuring Socket Listener

The example assumes that a connection profile has been created as explained in Section 10.1.1 or Section10.1.2. Keep in mind that if the host is configured as listener another service profile must be left free to be dynam-ically assigned as Server when the listener receives a connection request from a remote client.

Configure the service profile 4 for use as Socket listener:

Open the Socket service and query the IP address dynamically assigned to the Socket listener:

at^scfg=tcp/withurcs Query the current setting.^SCFG: "Tcp/WithURCs","on" URC mode is enabled (delivery detault).OKat^scfg=tcp/withurcs,off Select polling mode (by switching off URC mode).^SCFG: "Tcp/WithURCs","off" Polling mode is accepted.OK

at^siss=4,srvType,socket Select service type Socket.OKat^siss=4,conId,0 Select connection profile 0.OKat^siss=4,address,"socktcp://lis-tener:65534"

The host specifies its local port 65534 to be used forthe Socket listener service. The local IP address willbe dynamically assigned when the service is openedwith AT^SISO.

OK

at^siso=4 Open the Socket service.OKat^siso? Query the current status of services. All service pro-

files are unused, except for service profile 4 which isrunning in listener mode, where <srvState>=3 (lis-tening) and <socketState>=3 (LISTENER). Theresponse also indicates the IP address dynamicallyassigned to the listener.

^SISO: 0, ""^SISO: 1, ""

^SISO: 2, ""^SISO: 3, ""^SISO: 4, "Socket","3","3","0","0","10.10.0.187:65534","0.0.0.0:0"^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OK



10.15.3 Configuring Socket Client for Calling a Socket Listener on Another Host

The example assumes that a connection profile has been created as explained in Section 10.1.1 or Section10.1.2.

Configure the client's service profile 1 for calling a Socket listener on another host:

10.15.4 Socket Client Sends Data via TCP Connection (Polling Mode)

The example uses service profile 0 configured for Socket service and TCP.

at^siss=1,srvType,socket Select service type Socket.OKat^siss=1,conId,0 Select connection profile 0.OKat^siss=1,address,"socktcp://10.10.0.187:65534"

The service profile of the client contains the IPaddress and the TCP port of the remote host.

OK

AT^SISO=0 The host opens service profile 0.OK Note: URC ^SISW:0, 1 does not appear! The host

must poll the service state by means of AT^SISI untilthe service is in <srvState> "Up".

AT^SISI=0^SISI: 0,3,0,0,0,0 The service is still in <srvState> "Connecting".OKAT^SISI=0^SISI: 0,4,0,0,0,0 The service is now in <srvState> "Up" and is

ready to accept data.OKAT^SISW=0,10 The host requests to write 10 bytes.^SISW: 0,10,10 Response that 10 bytes can be sent and are unac-

knowledged.0123456789OKAT^SISW=0,10,1 The host requests to write next 10 bytes and enables

the end-of-data flag.^SISW: 0,0,10 But the service refuses the request, even the end-of-

data flag remains without effect.OKAT^SISW=0,10,1 Next try (polling).^SISW: 0,10,20 Response that the service accepts 10 bytes and this

data and the previously sent data are unacknowl-edged.

0123456789OKAT^SISW=0,0,0 Polling to request unacknowledged data.^SISW: 0,0,10 There are 10 bytes still unacknowledged.OKAT^SISI=0 Polling for <srvState> change ("Closing" ->

"Down").^SISI: 0,5,0,20,10,10 20 bytes are transfered via serial interface, 10 bytes

are acknowledged by remote peer, 10 bytes are onthe way.

OK



10.15.5 Socket client sends data via TCP connection with URCs

The example uses service profile 0 configured for Socket service and TCP.

10.15.6 Socket Scenario with UDP Endpoint

The following example shows a communication between a UDP endpoint (host 1) and a UDP client (host 2).The first part of the example refers to the UDP endpoint and shows the configuration which allows the UDP end-point to communicate with any UDP client.The second part shows the settings of a UDP client. The third and the fourth part are running in parallel: The third part shows the procedures on the UDP endpointside done when communicating with a UDP client. The fourth part shows the equivalent steps done by the UDPclient when communicating with the UDP endpoint.

Part 1 - host 1 is configured for use as UDP endpoint:

AT^SISI=0 Polling for <srvState> change ("Closing" ->"Down").

^SISI: 0,6,0,20,20,0 The Service is in state "Down" and all data is con-firmed by the remote peer.

OKAT^SISC=0 Closing the Socket service.OK

AT^SISO=0 The host opens service profile 0.OK^SISW: 0,1 Socket service is ready for upload.AT^SISW=0,10 The host requests to write 10 bytes.^SISW: 0,10,10 Response that 10 bytes can be sent and are unac-

knowledged.0123456789OK^SISW: 0,1 The URC indicates that the Socket service is ready

to transfer more data. Data of the last AT^SISWcommand are transferred to the remote host.

AT^SISW=0,10,1 The host requests to write next 10 bytes and enablesthe end-of-data flag to notify that these are the last10 bytes of the session.

^SISW: 0,10,20 Response that the service accepts 10 bytes and thisdata and the previously sent data are unacknowl-edged.

0123456789OK------ Waiting for URC. ^SISW: 0,2 Data transfer has been finished. AT^SISC=0 Closing the Socket service. OK

AT^SISS=0,srvtype,socket Select service type Socket.OKAT^SISS=0,conid,1 Select connection profile 1.OKAT^SISS=0,alphabet,1 Choose ASCII alphabet.OKAT^SISS=0,address,"sockudp://:6666" Specify the local UDP port.OK



Part 2 - host 2 is configured for use as UDP client:

Part 3 - host 1 opens the service and communicates with host 2:

Part 4 - host 2 opens the service and communicates with host 1:

AT^SISS=0,srvtype,socket Select service type Socket.OKAT^SISS=0,conid,1 Select connection profile 1.OKAT^SISS=0,alphabet,1 Choose ASCII alphabet.OKAT^SISS=0,address,"sockudp://10.10.0.219:6666"

Specify the address of host 1.

OK

AT^SISO=0 Open the service.OK^SISW: 0, 1 The URC indicates that host 1 is waiting on UDP port

6666 and can send data to any UDP client. ^SISR: 0, 1 The URC indicates that host 2 has opened the con-

nection to host 1 and has sent some data. AT^SISR=0, 100 Host 1 requests to read 100 bytes.OK^SISR: 0, 23, 0, 10.10.0.22:6561 Hello, I'm the client!

Host 1 is reading the text string received from host 2and gets information about the remote client, i.e. theaddress of host 2.

OKAT^SISW=0,1,0,1,"10.10.0.22:6561" Host 1 starts sending a text string to host 2, using

<mode> 1 (interactive text mode).^SISW: 0, 1500, 0Hi, I'm the UDP endpoint!<CTRl-Z>

Host 1 is sending a text string to host 2. As a result,host 2 is receiving the URC "^SISR: 0, 1" shownbelow in part 4 of the example.

OK^SISW: 0, 1 The URC confirms that host 1 can send data again.AT^SISC=0 Close the service.OK

AT^SISO=0 Open the service.OK^SISW: 0, 1 The URC indicates that the service is ready.AT^SISW=0,1,0,1 Host 2 has entered interactive text mode and starts

to write.^SISW: 0, 1500, 0Hello, I'm the client!<CTRl-Z>

Host 2 is writing a text string. As a result, host 1 isreceiving the URC "^SISR: 0, 1" shown above in part3 of this example.

OK^SISW: 0, 1 The URC confirms that there is no further data avail-

able.^SISR: 0, 1 The URC indicates that data has been received.AT^SISR=0,100 Host 1 requests to read 100 bytes.OK^SISR: 0, 26Hi, I'm the UDP endpoint.

The response indicates that host 2 has received 26characters from host 1.

OKAT^SISC=0 Close the service.OK



10.15.7 Configuring and Using FTP Download (URC Mode)

First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameterswhich are mandatory for the connection profile.

Configure the service profile 1 for FTP:

Make an FTP connection:

10.15.8 Configuring and Using FTP Upload (URC Mode)

First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameterswhich are mandatory for the connection profile.

Configure the service profile 1 for FTP:

Make an FTP connection:

at^siss=1,srvType,ftp Select service type FTP.OKat^siss=1,conId,0 Select connection profile 0.OKat^siss=1,address,"ftp://192.168.1.2;type=d"

Specify FTP address with user and password anon-ymous.

OK

at^siso=1 Open the service.OK Bearer is established, service is getting started.^SISR: 1, 1 Data is available.at^sisr=1,1500 Request to read 1500 bytes.^SISR: 1, 50 50 bytes are now available.hardwareinttestsoftwaresupportsystemtestOK^SISR: 1, 2 Data transfer finished. No more data available. The

connection to the FTP server is closed.at^sisc=1 Close the service.OK

at^siss=1,srvType,ftp Select service type FTP.OKat^siss=1,conId,0 Select connection profile 0.OKat^siss=1,address,"ftpput://myname:[email protected]/upload/exam-ple.bin;type=i"

Specify FTP address with individual user name andpassword. The file "example.bin" shall be created onthe FTP server.

OK

at^siso=1 Open the service.OK Bearer is established, service is getting started.^SISW: 1, 1 FTP service is ready for upload.at^sisw=1,100 Client requests to send 100 bytes.^SISW: 1,100,100 The write command response confirms that 100

bytes must be transferred now.



10.15.9 Configuring SMTP Service Profile

First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameterswhich are mandatory for a CSD or GPRS profile. The example uses the connection profile ID 1 and the serviceprofile ID 9.

0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789

User data is transferred.

OK^SISW: 1, 1 URC indicates that the FTP service is ready to trans-

fer more data. Data of the last AT^SISW command istransferred to the remote host.

at^sisw=1,0,1 No more data available. The file "example.bin" shallbe closed on the FTP server.OK

^SISW: 1, 2 Data transfer finished successfully. The connectionto the FTP server is closed.

at^sisc=1 Close the FTP service.

at^siss=9,srvType,"Smtp" Select service type SMTP.OKat^siss=9,alphabet,"1" Choose ASCII alphabet.OKat^siss=9,conId,"1" Select connection profile 1.OKat^siss=9,address,"192.168.1.2" Specify SMTP server address.OKat^siss=9,user,"subscriber1" Specify sender's user name required for SMTP

authentication.OKat^siss=9,passwd,"subscr1" Specify password used by the sender for SMTP

authentication.OKat^siss=9,smFrom,"[email protected]"

Sender's email address.

OKat^siss=9,smRcpt,"[email protected]"

Recipient's email address.

OKat^siss=9,smSubj,"Meeting Request Sunday Morning"

Enter text for subject field.

OKat^siss=9,smAuth,"1" Sender name and password can be used for SMTP

authentication.OKat^siss? To check the profile enter the AT^SISS read com-

mand. The response includes the values of all 10connection profiles. In this example, no values areset for the profiles 0 through 8. Service profile 9 con-tains the values specified above and the values auto-matically assumed by default.

^SISS: 0, "srvType", ""^SISS: 1, "srvType", ""^SISS: 2, "srvType", ""^SISS: 3, "srvType", ""^SISS: 4, "srvType", ""^SISS: 6, "srvType", ""^SISS: 7, "srvType", ""^SISS: 8, "srvType", ""^SISS: 9, "srvType", "Smtp"^SISS: 9, "conId", "1"^SISS: 9, "alphabet", "1"^SISS: 9, "address", "192.168.1.2"^SISS: 9, "user", "subscriber1"^SISS: 9, "passwd", "*******"



10.15.10 Sending Email (URC Mode)

This example uses the service profile described in Section 10.15.9.

10.15.11 Sending Email (Polling Mode)


^SISS: 9, "smFrom", "[email protected]"^SISS: 9, "smRcpt", "[email protected]"^SISS: 9, "smCC", ""^SISS: 9, "smSubj", "Meeting Request Sunday Morning"^SISS: 9, "smHdr", ""^SISS: 9, "tcPort", "25" Default: TCP port number commonly used for SMTP.^SISS: 9, "smAuth", "1"^SISS: 9, "tcpMR", "10" Default: Number of retransmission attempts for TCP

packets is 10 (= default of AT^SCFG).^SISS: 9, "tcpOT", "6000" Default: Timeout before closing outstanding TCP

connection is 6000 sec (= default of AT^SCFG).OK

at^siso=9 Open the service, i.e. start to send the email. OK^SISW: 9, 1 The "^SISW" URC indicates that email data can be

transferred. at^sisw=9,87 The email to be sent has 87 bytes. ^SISW: 9,87,87 The write command response confirms that 87 bytes

are available for transmission. Good Morning everyone, we are delighted to announce our next meeting on Sunday morning.

Write the message text.

OKat^sisw=9,0,1 Set the <eodFlag> to mark the end of the email

body.^SISW: 9,0,0 The <eodFlag> is accepted by the service.^SISW: 9,2 The "^SISW" URC confirms that all data is sent suc-

cessfully.at^sisi=9 Check the connection state of the service profile 9. ^SISI: 9,6,0,87,0,0 The command response confirms that the SMTP

service is in state "6" (Down) and that 87 bytes havebeen transferred.

at^sisc=9 Close the service. OK

at^siso=9 Open the service, i.e. start to send the email. OKat^sisw=9,10 Try to write 10 bytes.^SISW: 9, 10, 0 The service response indicates that 10 bytes can be

written. Hallo Tom! Write 10 bytes. OKat^sisw=9,10 Try to write 10 bytes.^SISW: 9, 0, 0 The service response indicates that the service

refuses to accept any data at the moment. OKat^sisw0=9,12 Try to write 12 bytes.



10.15.12 Configuring POP3 Service Profile

First set up a connection profile as explained in Section 10.1.1 or Section 10.1.2. Enter at least all parameterswhich are mandatory for a GPRS profile. The example uses the connection profile ID 1 and the service profileID 1. The service profile is set up to retrieve a specific email (email number 2).

^SISW: 9, 12, 0 The service response indicates that 12 bytes can bewritten.

Bye Bye Tom! Write 12 bytes. OKat^sisw=9,0,1 Set the <eodFlag> to mark the end of the email

body.^SISW: 9,0,0 The <eodFlag> is accepted by the service.OKat^sisi=9 Check the connection state of service profile 9. ^SISI: 9,5,0,22,0,0 The command response confirms that the SMTP

service is in state "5" (Closing) and that 22 byteshave been written.

OK

at^sisi=9 Check the connection state of service profile 9. ^SISI: 9,6,0,22,0,0 The command response confirms that the SMTP

service is in state "6" (Down) and that 22 bytes havebeen written.

OK

at^sise=9 Check error status of service profile 9. ^SISE: 9,0 The command response confirms that no error

occurred. OKat^sisc=9 Close the service. OK

at^siss=1,srvType,"Pop3" Select service type POP3.OKat^siss=1,conId,"1" Select connection profile 1.OKat^siss=1,address,"192.168.1.2" Specify POP3 server address.OKat^siss=1,user,"subscriber1" Specify recipient's mailbox name.OKat^siss=1,passwd,"subscr1" Password used by recipient for authentication to

POP3 server.OKat^siss=1,pCmd,"3" Command used to retrieve emails.OKat^siss=1,pNumber,"2" Email message number 2 shall be retrieved. OKat^siss? To check the profile enter the AT^SISS read com-

mand. The response includes the values of all 10connection profiles. Service profile 1 contains thevalues specified above and the values automaticallyassumed by default.

^SISS: 0, "srvType", ""^SISS: 1, "srvType", "Pop3"^SISS: 1, "conId", "1"

^SISS: 1, "alphabet", "0" Default: Character set enabled with AT+CSCS shallbe used.

^SISS: 1, "address", "192.168.1.2"^SISS: 1, "user", "subscriber1"^SISS: 1, "passwd", "*******"^SISS: 1, "pCmd", "3"^SISS: 1, "tcPort", "110" Default: TCP port number commonly used for POP3.^SISS: 1, "pNumber", "2"^SISS: 1, "pLength", "0" Default: Message size shall not be limited.



^SISS: 1, "pDelFlag", "0" Default: Retrieved message shall not be deleted onPOP3 server.

^SISS: 1, "tcpMR", "10" Default: Number of retransmission attempts for TCPpackets is 10 (= default of AT^SCFG).

^SISS: 1, "tcpOT", "6000" Default: Timeout before closing outstanding TCPconnection is 6000 sec (= default of AT^SCFG).

^SISS: 2, "srvType", ""^SISS: 3, "srvType", ""^SISS: 4, "srvType", ""^SISS: 6, "srvType", ""^SISS: 7, "srvType", ""^SISS: 8, "srvType", ""^SISS: 9, "srvType", ""OK



10.15.13 Retrieving Email (URC Mode)


10.15.14 Retrieving Email (Polling Mode)


at^siso=1 Open the service that was created to retrieve emailnumber 2 from the POP3 server.

OK^SISR: 1, 1 The "^SISR" indicates that data is available for read-

ing.at^sisr=1,500 Try to read 500 bytes.^SISR: 1, 500 Command response indicates that 500 bytes will be

transferred, i.e. there will be no other URC since therequested length equals the confirmed length.

Return-Path: <[email protected]> X-Original-To: [email protected] Delivered-To: [email protected] Received: from 10.10.0.132 (unknown [10.10.0.132]) by testdomain.com (Postfix) with SMTP id 379321D004 for <[email protected]>; Tue, 20 Dec 2005 08:00:07 +0100 (CET) To: [email protected] Cc: From: [email protected] Subject: TestMail Message-Id: <[email protected] > Date: Tue, 20 Dec 2005 08:00:07 +0100OKat^sisr=1,500 Try to read another 500 bytes.at^sisr=1,78 Command response indicates that only 78 bytes will

transferred.(CET)X-UIDL: &lL"!(Z6"!^cl!!1+%"! Status: RO

Hallo Tom!Bye Bye Tom! . Dot indicates end of mail according to RFC 2821.OK^SISR: 1, 2 Parameter <urcCauseId> of the "^SISR" URC

confirms that all data is transferred successfully.at^sisc=1 Close the service. OK

at^siso=1 Open the service that was created to retrieve emailnumber 2 from the POP3 server.

OKat^sisr=1,1000 Try to read 1000 bytes.^SISR: 1, 0 Command response indicates that currently no data

is available.OKat^sisr=1,1000 Again, try to read 1000 bytes.^SISR: 1, 0 Command response indicates that currently no data

is available.OKat^sisr=1,1000 Again, try to read 1000 bytes.



10.15.15 HTTP POST (Polling Mode)

^SISR: 1, 578 Command response indicates that 578 bytes areavailable for reading.

Return-Path: <[email protected]> X-Original-To: [email protected] Delivered-To: [email protected] Received: from 10.10.0.132 (unknown [10.10.0.132]) by testdomain.com (Postfix) with SMTP id 379321D004 for <[email protected]>; Tue, 20 Dec 2005 08:00:07 +0100 (CET) To: [email protected] Cc: From: [email protected] Subject: TestMail Message-Id: <[email protected] > Date: Tue, 20 Dec 2005 08:00:07 +0100 (CET) X-UIDL: &lL"!(Z6"!^cl!!1+%"! Status: RO

Hallo Tom!Bye Bye Tom! . Dot indicates end of mail according to RFC 2821.OKat^sisr=1,1000 Try to read 1000 bytes once again.^SISR: 1,-2 No more data available to read, i.e. the service has

finished.OKat^sisi=1 Check the connection state of service profile 1. ^SISI: 1,6,578,0,0,0 The command response indicates that the POP3

service is in state "6" (Down) and that 578 bytes havebeen retrieved.

OK



at^siss=1,srvType,"Http" Select service type HTTP.OKat^siss=1,conId,1 Select connection profile 1.OKat^siss=1,hcMethod,1 Select "Post" method.OKat^siss=1,address,"http://192.168.1.3/datafiles/dummy/dummy.txt"OKat^siss=1,hcContLen,180 Try to upload 180 bytes.OKat^siso=1 Open the service.OKat^sisw=1,100 Send the first 100 bytes. ^SISW: 1, 100, 0OKat^sisw=1,100 Try to send again 100 bytes.^SISW: 1, 80, 0 80 bytes are sent. OKat^sisw=1,40 Try to write data once again.



10.15.16 HTTP GET (Polling Mode)

^SISW: 1, 0, 0 No further data available, i.e. the service has fin-ished.

OKat^sisi?^SISI: 1,6,0,180,0,0 The command response indicates that HTTP service

is in state "6" (Down) and that 180 bytes have beensent.

OK



at^siss=0,srvType,"Http" Select service type HTTP.OKat^siss=0,conId,1 Select connection profile 1.OKat^siss=0,hcMethod,0OKat^siss=0,address,http://192.168.1.4/OKat^siso=0OKat^sisr=0,1500 Start reading data in polling mode.^SISR: 0, 1264...DATA...OKat^sisr=0,1500^SISR: 0, 1500...DATA...OKat^sisr=0,1500^SISR: 0, 602...DATA...OKat^sisr=0,1500 Again, try to read 1500 bytes.^SISR: 0, -2 No more data to read, i.e. the service has finished. OKat^sisi?^SISI: 0,6,0,3366,0,0 The command response indicates that the HTTP

service is in state "6" (Down) and that 3366 byteshave been read.

OK





10.15.17 Creating Transparent TCP Socket Client

10.15.18 Opening and Closing Transparent TCP Service

at^siss=1,srvType,"Transparent" Select service type "Transparent".OKat^siss=1,conId,1 Select connection profile 1.OKat^siss=1,address,"10.10.0.110:9996:timer=200"

Specify server address.

OK

at^siso=1 Open Transparent TCP service.OK^SISW: 1,1 URC indicates that Transparent TCP service is

ready.at^sist=1 Open transparent access mode.CONNECT Service is ready to send or receive data.

Client is sending data, e.g Good Morning (not visiblein example).Client types +++ to return to AT command mode(+++ not visible in example).

OKat^sisi=1 Check the service state of service profile 1. ^SISI: 1,4,0,16,16,0 Service is in state "Up" (4). 0 bytes received, 16

bytes sent and acknowledged.OKat^siso? Check the service state of service profile 1. ^SISO: 0, ""^SISO: 1, "Transpar-ent","4","2","0","16","10.10.0.200:1024","10.10.0.108:65532"

Service is in state "Up" (4). Socket is assigned. 0bytes received, 16 bytes sent. Local and remote IPaddress are assigned.

^SISO: 2, ""^SISO: 3, ""^SISO: 4, ""^SISO: 5, ""^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OKat^sici? Check the state of the Internet connection profile. ^SICI: 0,2,1,"10.10.0.200" Internet connection profile is in state "Up". Local IP

address is assigned.OKat^sisc=1 Close the service. OKat^sisi=1 Check the service state of service profile 1. ^SISI: 1,2,0,0,0,0 Service profile 1 is in state "Allocated" (2).OKat^siso? Check the service state of service profile 1. ^SISO: 0, ""^SISO: 1, "Transpar-ent","2","1","0","0","0.0.0.0:0","0.0.0.0:0"

Service is in state "Allocated" (2). Socket notassigned.



10.15.19 Transparent TCP Client Receives Data While in AT Command Mode

^SISO: 2, ""^SISO: 3, ""^SISO: 4, ""^SISO: 5, ""^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OKat^sici? Check the state of the Internet connection profile. ^SICI: 0,0,0,"0.0.0.0" No Internet connection profile currently used. OK


ready.at^sist=1 Open transparent access mode.CONNECT Service is ready to send or receive data.Hello Client is reading received data.

Client types +++ to return to AT command mode(+++ not visible in example).

OK^SISR: 1,1 URC indicates that new data is available for the cli-

ent.at^sist=1 Return to transparent access mode.CONNECT Service is ready to send or receive data.Goodbye Client is reading received data.

Client types +++ to return to AT command mode (notvisible in example).

OKat^sisi=1 Check the service state of service profile 1. ^SISI: 1,4,12,6,6,0 Service is in state "Up" (4). 12 bytes received, 6

bytes sent and acknowledged.OKat^siso? Check the service state of service profile 1. ^SISO: 0, ""^SISO: 1, "Transpar-ent","4","2","12","6","10.10.0.200:1025","10.10.0.108:65532"

Service is in state "Up" (4). Socket is assigned. 12bytes received, 6 bytes sent. Local and remote IPaddress are assigned.

^SISO: 2, ""^SISO: 3, ""^SISO: 4, ""^SISO: 5, ""^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OKat^sici? Check the state of the Internet connection profile. ^SICI: 0,2,1,"10.10.0.200" Internet connection profile is in state "Up". Local IP

address is assigned.



10.15.20 Server Disconnects While Transparent TCP Service is in Trans-parent Access Mode

OKat^sisc=1 Close the service. OKat^sisi=1 Check the service state of service profile 1. ^SISI: 1,2,0,0,0,0 Service profile 1 is in state "Allocated" (2).OKat^siso? Check the service state of service profile 1. ^SISO: 0, ""^SISO: 1, "Transpar-ent","2","1","0","0","0.0.0.0:0","0.0.0.0:0"

Service is in state "Allocated" (2). Socket notassigned.

^SISO: 2, ""^SISO: 3, ""^SISO: 4, ""^SISO: 5, ""^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OKat^sici? Check the state of the Internet connection profile. ^SICI: 0,0,0,"0.0.0.0" No Internet connection profile currently used. OK


ready.at^sist=1 Open transparent access mode.CONNECT Service is ready to send or receive data.Good Morning NO CARRIER Server has sent data and disconnected. Client reads

data. Then client gets NO CARRIER in AT commandmode.

at^sisi=1 Check the service state of service profile 1. ^SISI: 1,6,12,0,0,0 Service is in state "Down" (6). 12 bytes received.OKat^siso? Check the service state of service profile 1. ^SISO: 0, ""^SISO: 1, "Transpar-ent","6","2","12","0","10.10.0.200:1026","10.10.0.108:65532"

Service is in state "Down" (6). Socket is assigned. 6bytes received. 12 bytes sent. Local and remote IPaddress are assigned.

^SISO: 2, ""^SISO: 3, ""^SISO: 4, ""^SISO: 5, ""^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OKat^sici? Check the state of the Internet connection profile.



10.15.21 Server Disconnects While Transparent TCP Service is in AT Command Mode and Data is Pending

^SICI: 0,2,1,"10.10.0.200" Internet connection profile is in state "Up". Local IPaddress is assigned.

OKat^sisc=1 Close the service. OKat^sisi=1 Check the service state of service profile 1. ^SISI: 1,2,0,0,0,0 Service profile 1 is in state "Allocated" (2).OK


ready.at^sist=1 Open transparent access mode.CONNECT Service is ready to send or receive data.Good Morning Client is reading data.

Client types +++ to return to AT command mode (notvisible in example).

OK^SISR: 1,1 Remote server has sent data and closed the connec-

tion (not visualized in this example). URC indicatesthat remaining data is available for reading.

at^sisi=1 Check service state of service profile 1.OK^SISI: 1,4,12,3,3,0 Service profile 1 is in state "Up" (4). 12 bytes

received. 3 bytes sent and acknowledged.OKat^siso? Check the service state of service profile 1. ^SISO: 0, ""^SISO: 1, "Transpar-ent","4","2","12","3","10.10.0.200:1027","10.10.0.108:65532"

Service is in state "Up" (4). Socket is assigned. 12bytes received. 3 bytes sent. Local and remote IPaddress are assigned.

^SISO: 2, ""^SISO: 3, ""^SISO: 4, ""^SISO: 5, ""^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OKat^sist=1 Return to transparent access mode.CONNECT Service is ready to send or receive data.Good bye NO CARRIER Client reads remaining data. Then client gets NO

CARRIER in AT command mode.at^sisi? Check service state of service profile 1.^SISI: 1,6,20,3,3,0 Service is in service "Down" state (6). 20 bytes

received. 3 bytes sent and acknowledged.OKat^siso? Check the service state of service profile 1. ^SISO: 0, ""



^SISO: 1, "Transpar-ent","6","2","20","3","10.10.0.200:1027","10.10.0.108:65532"

Service is in state "Down" (6). Socket is assigned. 20bytes received. 3 bytes sent. Local and remote IPaddress are assigned.

^SISO: 2, ""^SISO: 3, ""^SISO: 4, ""^SISO: 5, ""^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OKat^sisc=1 Close the service.OKat^sisi=1 Check service state of service profile 1.^SISI: 1,2,0,0,0,0 Service profile 1 is in state "Allocated" (2).OKat^siso? Check the service state of service profile 1. ^SISO: 0, ""^SISO: 1, "Transpar-ent","2","1","0","0","0.0.0.0:0","0.0.0.0:0"

Service is in state "Allocated" (2). Socket is notassigned. Local and remote IP address notassigned.

^SISO: 2, ""^SISO: 3, ""^SISO: 4, ""^SISO: 5, ""^SISO: 6, ""^SISO: 7, ""^SISO: 8, ""^SISO: 9, ""OK

BGS3 AT Command Set 11. GPRS Commands


11. GPRS Commands

This chapter describes AT commands that a TE (Terminal Equipment, e.g. an application running on a controllingPC) may use to control the BGS3 acting as GPRS Mobile Termination (MT). Please use chapter "Using GPRSAT commands (Examples)" as a first guidance.

11.1 AT+CGACT PDP context activate or deactivate

Syntax

Command DescriptionThe test command is used for requesting information on the supported PDP context activation states. The read command returns the current activation states for all the defined PDP contexts. The write command is used to activate or deactivate the specified PDP context(s). After the command has com-pleted, the MT remains in V.250 command state. If any PDP context is already in the requested state, the statefor that context remains unchanged. If the MT is not GPRS attached when the activation form of the commandis executed, the MT first performs a GPRS attach and them attempts to activate the specified contexts. If no<cid>s are specified the activation/deactivation form of the command activates/deactivates all defined contexts.


Indicates the state of PDP context activation.0 detached[1] attached

Test Command

AT+CGACT=?Response(s)

+CGACT: (list of supported <state>s)OK

Read Command

AT+CGACT?Response(s)

+CGACT: <cid>, <state>[+CGACT: <cid>, <state>]...OK

Write Command

AT+CGACT=[<state>[, <cid>[, <cid>[,... ]]]]Response(s)



+ + + + + + - - GSM 07.07

<state>(num)

BGS3 AT Command Set 11.1 AT+CGACT


PDP Context Identifier is a numeric parameter which specifies a particular PDP context definition. The param-eter is local to the TE-MT interface and is used in other PDP context-related commands. 1...2

Note• ATH will deactivate any PDP context.

<cid>(num)

BGS3 AT Command Set 11.2 AT+CGANS


11.2 AT+CGANS Manual response to a network request for PDP con-text activation

Syntax

Command DescriptionThe write command requests the MT to respond to a network request for GPRS PDP context activation whichhas been signaled to the TE by the RING or CRING unsolicited result code. The <response> parameter allowsthe TE to accept or reject the request.


[0] the request is rejected and the MT returns OK to the TE1 accept and request that the PDP context be activated

a string parameter which indicates the layer 2 protocol to be used (see AT+CGDATA command)

a numeric parameter which specifies a particular PDP context definition (see AT+CGDCONT command).

Note• If <response> is 1, the following procedure is followed by the MT:

If the <L2P> parameter value is unacceptable to the MT, the MT will return an "ERROR" or "+CME ERROR:<err>" response. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 onlinedata state.A <cid> may be specified for use in the context activation request.During the PDP startup procedure the MT has the PDP type and the PDP address provided by the networkin the Request PDP context activation message. If this is in conflict with the information provided by a spec-ified <cid>, the command will fail. There will be no conflict, if the PDP type matches exactly and the PDPaddress given by the context definition for <cid> is empty or matches exactly with the address specified withthe network PDP context activation message.The context will be activated using the values for PDP type and address provided by the network, togetherwith all other information found in the PDP context definition. An APN may or may not be required, dependingon the application.

Test Command

AT+CGANS=?Response(s)

+CGANS: (list of supported <response>s), (list of supported <L2P>s)OK

Write Command

AT+CGANS=[<response>[, <L2P>[, <cid>]]]Response(s)

CONNECTNO CARRIERERROR+CME ERROR: <err>


+ + + + + + - + GSM 07.07

<response>(num)

<L2P>(str)

<cid>(num)

BGS3 AT Command Set 11.2 AT+CGANS


If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the contextusing the values for PDP type and address provided by the network. The other parameters will be set to theirdefault values (see AT+CGDCONT).If activation is successful, data transfer may proceed.After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully,the V.250 command state is reentered and the MT returns the final result code OK.In the event of an erroneous termination or a failure to start up, the V.250 command state is re-entered andthe MT returns the final result code NO CARRIER, or if enabled, "+CME ERROR: <err>". Attach, activate andother errors may be reported. It is also an error to issue the AT+CGANS command when there is no pendingnetwork request.The command may be used in both normal and modem compatibility modes.

BGS3 AT Command Set 11.3 AT+CGATT


11.3 AT+CGATT GPRS attach or detach

Syntax

Command DescriptionThe test command is used for requesting information on the supported GPRS service states. The read command returns the current GPRS service state. The write command is used to attach the MT to, or detach the MT from the GPRS service. After the commandhas completed, the MT remains in V.250 command state. If the MT is already in the requested state, the com-mand is ignored and the OK response is returned. Any active PDP contexts will be automatically deactivatedwhen the attachment state changes to detached.


Indicates the state of GPRS attachement.0(P) detached[1] attached

Notes• If the MT is in dedicated mode, write command returns "+CME ERROR: operation temporary not allowed". • When the module is GPRS attached and a PLMN reselection occurs to a non-GPRS network or to a network

where the SIM is not subscribed to for using GPRS, the resulting GMM (GPRS mobility management) stateaccording to GSM 24.008 is REGISTERED/NO CELL, meaning that the read command will still show<state>=1.

• Under some network conditions the GPRS attach command fails, if entered immediately after a "+CREG: 1"URC. This can be avoided by waiting at least 1s before entering the GPRS attach command.

Test Command

AT+CGATT=?Response(s)

+CGATT: (list of supported <state>s)OK

Read Command

AT+CGATT?Response(s)

+CGATT: <state>OK

Write Command

AT+CGATT=[<state>]Response(s)



+ + + + + + - - GSM 07.07

<state>(num)

BGS3 AT Command Set 11.4 AT+CGAUTO


11.4 AT+CGAUTO Automatic response to a network request for PDP context activation

Syntax

Command DescriptionThe test command returns the values of <n> supported by the MT as a compound value. The write command disables or enables an automatic positive response (auto-answer) to the receipt of aRequest PDP Context Activation message from the network. It also provides control over the use of the V.250basic commands ATS0, ATA and ATH for handling network requests for PDP context activation.


0 Disable automatic response for network requests for GPRS PDP context acti-vation. GPRS network requests are manually accepted or rejected by theAT+CGANS command.

1 Enable automatic response for network requests for GPRS PDP context acti-vation. GPRS requests are automatically accepted according to the descriptionbelow.

3(&F)(P) Modem compatibility mode. The automatic acceptance of both GPRS andincoming CSD calls is controlled by the ATS0 command. Manual control usesthe ATA and ATH commands, respectively, to accept or reject GPRS networkrequests or incoming CSD calls.

Notes• It is allowed to have different AT+CGAUTO settings on different interfaces. • When the AT+CGAUTO=0 command is received, the MT will not perform a GPRS detach if it is attached. Sub-

sequently, when the MT announces a network request for PDP context activation by issuing the URC RINGor CRING, the TE may manually accept or reject the request by issuing the AT+CGANS command or may sim-ply ignore the network request.

Test Command

AT+CGAUTO=?Response(s)

+CGAUTO: (list of supported <n>s)OK

Read Command

AT+CGAUTO?Response(s)

+CGAUTO: <n>OK

Write Command

AT+CGAUTO=[<n>]Response(s)



+ + + + + + - - GSM 07.07

<n>(num)

BGS3 AT Command Set 11.4 AT+CGAUTO


• When the AT+CGAUTO=1 command is received, the MT will attempt to perform a GPRS attach if it is not yetattached. Failure will result in ERROR or, if enabled +CME ERROR being returned to the TE. Subsequently,the MT announces a network request for PDP context activation by issuing the URC RING to the TE, followedby the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the sameprocedure as it would after having received a +CGANS=1 with no <L2P> or <cid> values specified.

• If a GPRS attach will be initiated by this command and the MT is not able to attach for more than 385 seconds(timer T3310 expired), command returns with "ERROR" or "+CME ERROR: unknown", but MT is still tryingto attach and the requested automatic mode <n> is in use.

• If a network request for PDP context activation is answered automatically and if another AT command isissued at the same time on the same interface, then this AT command is not executed. Any response belongsto the automatic context activation procedure. If the AT command which caused the collision was a circuitswitched data call, the CONNECT response does not belong to this data call but to the GPRS. This can bedetected if ATX is not set to 0. CS data call will issue CONNECT <text>, GPRS will issue CONNECT only.

BGS3 AT Command Set 11.5 AT+CGDATA


11.5 AT+CGDATA Enter data state

Syntax

Command DescriptionThe test command is used for requesting information on the supported layer 2 protocols to be used between theTE and MT. The write command causes the MT to perform all actions which are necessary to establish communicationbetween the TE and the network using one or more GPRS PDP types. This may include performing a GPRSattach and one or more PDP context activations. Commands following the AT+CGDATA command in the AT com-mand line will not be processed by the MT. If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context withPDP type IP and all other context parameters set to their default values (see AT+CGDCONT, AT+CGQREQ,AT+CGQMIN). If the <L2P> parameter is omitted, the layer 2 protocol is unspecified and PPP will be used. If the write command is successful, the MT issues the intermediate result code CONNECT and enters V.250online data state. After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, thecommand state is reentered and the MT returns the final result code OK. If the <L2P> parameter value is unacceptable to the MT, the MT returns ERROR or +CME ERROR. In the event of erroneous termination or a failure to start up, the command state is reentered and the MT returnsNO CARRIER, or if enabled +CME ERROR.


Layer 2 protocol to be used between the TE and MT. [“PPP“] layer 2 protocol PPP

Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and isused in other PDP context-related commands. 1...2

Test Command

AT+CGDATA=?Response(s)

+CGDATA: (list of supported <L2P>s)OK

Write Command

AT+CGDATA=[<L2P>[, <cid>[, <cid>]]]Response(s)

CONNECTNO CARRIERERROR+CME ERROR: <err>


+ + + + + + - + GSM 07.07

<L2P>(str)

<cid>(num)

BGS3 AT Command Set 11.5 AT+CGDATA


Notes• If the MT is in dedicated mode, write command returns "+CME ERROR: operation temporary not allowed". • It is possible to leave the GPRS data mode and enter the command mode by using the V.250 command +++.

By using the command AT+CGDATA again, the data mode is reentered. Which context is used to return todata mode, depends on the supplied parameter <cid>. If no <cid> is specified, this is equivalent to using the V.250 command ATO, which is usable for GPRS con-nections too. In this case the first context will be used, which is active and already in data mode since it hasbeen activated. It is possible to use AT+CGDATA to enter the data mode for a context, which is not yet in data mode since ithas been activated. With ATO this is not possible.

11.5.1 Automatic deactivation of PDP context during dial-up PPP

When using the AT+CGDATA write command or ATD*99# or ATD*98# the MT issues the intermediate resultcode CONNECT and enters V.250ter online data state. In V.250 online data state, first some LCP protocolexchange between MT and TE is performed to set up the PPP link. After successfully establishing the PPP link,the MT performs the PDP context activation procedure if the context is not already activated. As a result, the MTis in a "PDP context activated" state within the PLMN, the PPP link is established on the mobile side and themobile is ready for IP data transfer. If the TE wants to close the LCP link the MT may perform an LCP termination request procedure on PPP level.After this LCP termination procedure the MT deactivates the PDP context automatically and the MT returns toV.250 command mode and issues the final result code NO CARRIER. During the implicit PDP context deactivation procedure after LCP termination the TE may change into V.250command state (e.g. by using +++ or by toggling DTR if AT&D is set to 1) before the result NO CARRIER occurs.In this case the application should not try to deactivate the PDP context by using the commands AT+CGACT orATH. If DTR is configured to disconnect data connections (AT&D2), then the application should not toggle DTRduring the implicit PDP context deactivation and before "NO CARRIER" is received.

BGS3 AT Command Set 11.6 AT+CGDCONT


11.6 AT+CGDCONT Define PDP Context

Syntax

Command DescriptionThe test command returns supported values as a compound value. The read command returns the current settings for each defined PDP context. The write command specifies the parameters for a PDP context identified by the context identifier <cid>. Thenumber of contexts that may be in a defined state at the same time is given by the range returned by the testcommand. A special form of the write command (AT+CGDCONT=<cid>) causes the values for context <cid> tobecome undefined.


PDP Context IdentifierParameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and isused in other PDP context-related commands. 1...2

Packet Data Protocol typeSpecifies the type of the packet data protocol.“IP“ Internet Protocol (IETF STD 5)

Test Command

AT+CGDCONT=?Response(s)

+CGDCONT: (range of supported<cid>s), <PDP_type>, , , (list of supported <d_comp>s), (list of supported <h_comp>s)OKERROR+CME ERROR: <err>

Read Command

AT+CGDCONT?Response(s)

[+CGDCONT: <cid>, <PDP_type>, <APN>, <PDP_addr>, <d_comp>, <h_comp>][+CGDCONT: ...]OKERROR+CME ERROR: <err>

Write Command

AT+CGDCONT=[<cid>[, <PDP_type>[, <APN>[, <PDP_addr>[, <d_comp>[, <h_comp>]]]]]]Response(s)



+ + + + + + - - GSM 07.07

<cid>(num)

<PDP_type>(str)

BGS3 AT Command Set 11.6 AT+CGDCONT


Access Point NameThe logical name that is used to select the GGSN or the external packet data network. If the value is null oromitted, then the subscription value will be requested.

Packet Data Protocol addressIdentifies the MT in the address space applicable to PDP (e.g. IP V4 address for PDP type IP). If the value isnull or omitted, then a value may be provided by the TE during the PDP startup procedure or, failing that, adynamic address will be requested.

Data CompressionControls the PDP data compression (applicable for Subnetwork Dependent Convergence Protocol (SNDCP)only) 3GPP TS 44.065 [0] off

Header CompressionControls the PDP header compression 3GPP TS 44.065, 3GPP TS 25.323[0] off1 on

Notes• The MT supports PDP type IP only.• All context definitions will be stored non volatile if the ME is configured accordingly (see AT^SCFG parameter

"GPRS/PersistentContexts" (<gpc>)). • If the non volatile storage of CGDCONT settings is not activated by the AT^SCFG parameter "GPRS/Persis-

tentContexts", then AT&F and ATZ will undefine every context which is not active or not online.

<APN>(str)

<PDP_addr>(str)

<d_comp>(num)

<h_comp>(num)

BGS3 AT Command Set 11.7 AT+CGEQMIN


11.7 AT+CGEQMIN Rel. 99 Quality of Service Profile (Minimum accept-able)

Syntax

Command DescriptionThe test command returns values supported as a compound value. The read command returns the current settings for each defined context. The write command allows the TE to specify a Quality of Service Profile for the context identified by the (local)context identification parameter <cid> which is checked by the MT against the negotiated profile returned in theActivate/Modify PDP Context Accept message. A special form of the write command, AT+CGEQMIN=<cid> causes the requested profile for context number<cid> to become undefined.AT&F and ATZ will undefine the QoS profiles of every context which is not active or not online.



Test Command

AT+CGEQMIN=?Response(s)

+CGEQMIN: <PDP_type>, (list of supported <Traffic class>s), (list of supported <Maximum bitrate UL>s), (list of supported <Maximum bitrate DL>s), (list of supported <Guaranteed bitrate UL>s), (list of supported <Guaranteed bitrate DL>s), (list of supported <Delivery order>s), (list of supported <Maximum SDU size>s), (list of supported <SDU error ratio>s), (list of supported <Residual bit error ratio>s), (list of supported <Delivery of erroneous SDUs>s), (list of supported <Transfer delay>s), (list of supported <Traffic handling priority>s)OK

Read Command

AT+CGEQMIN?Response(s)

[+CGEQMIN: <cid>, <Traffic class>, <Maximum bitrate UL>, <Maximum bitrate DL>, <Guaranteed bitrate UL>, <Guaranteed bitrate DL>, <Delivery order>, <Maximum SDU size>, <SDU error ratio>, <Residual bit error ratio>, <Delivery of erroneous SDUs>, <Transfer delay>, <Traffic handling priority>][+CGEQMIN: ...]

Write Command

AT+CGEQMIN=[<cid>[, <Traffic class>[, <Maximum bitrate UL>[, <Maximum bitrate DL>[, <Guaranteed bitrate UL>[, <Guaranteed bitrate DL>[, <Delivery order>[, <Maximum SDU size>[, <SDU error ratio>[, <Residual bit error ratio>[, <Delivery of erroneous SDUs>[, <Transfer delay>[, <Traffic handling priority>]]]]]]]]]]]]]Response(s)



+ + + + + + - - 3GPP TS 27.007

<cid>(num)



0 conversational1 streaming2 interactive3 background[4] subscribed value

This parameter indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As anexample a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQMIN=...,32,...). [0] subscribed value1...6364...128 (value needs to be divisible by 8 without remainder)256512

This parameter indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP. As anexample a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQMIN=...,32,...). [0] subscribed value1...6364...256 (value needs to be divisible by 8 without remainder)512

This parameter indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (providedthat there is data to deliver). As an example a bitrate of 32kbit/s would be specified as 32 (e.g.AT+CGEQMIN=...,32,...). [0] subscribed value1...6364...128 (value needs to be divisible by 8 without remainder)

This parameter indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (pro-vided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as 32 (e.g.AT+CGEQMIN=...,32,...). [0] subscribed value1...6364...256 (value needs to be divisible by 8 without remainder)

This parameter indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not. 0 no1 yes[2] subscribed value

<Traffic class>(num)

<Maximum bitrate UL>(num)

<Maximum bitrate DL>(num)

<Guaranteed bitrate UL>(num)

<Guaranteed bitrate DL>(num)

<Delivery order>(num)



This parameter indicates the maximum allowed SDU size in octets.[0] subscribed value10...1520 (value needs to be divisible by 10 without remainder)1502

This parameter indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratiois defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error ratioof 5*10-3 would be specified as "5E3" (e.g. AT+CGEQMIN=...,"5E3",...). [“0E0“] subscribed value“1E2““7E3““1E3““1E4““1E5““1E6““1E1“

This parameter indicates the target value for the undetected bit error ratio in the delivered SDUs. If no errordetection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value isspecified as "mEe". As an example a target residual bit error ratio of 5*10-3 would be specified as "5E3" (e.g.AT+CGEQMIN=...,"5E3",...). [“0E0“] subscribed value“5E2““1E2““5E3““4E3““1E3““1E4““1E5““1E6““6E8“

This parameter indicates whether SDUs detected as erroneous shall be delivered or not.0 no1 yes2 no detect[3] subscribed value

<Maximum SDU size>(num)

<SDU error ratio>(str)

<Residual bit error ratio>(str)

<Delivery of erroneous SDUs>(num)



This parameter indicates the targeted time between request to transfer an SDU at one SAP to its delivery at theother SAP, in milliseconds. [0] subscribed value10...150 (value needs to be divisible by 10 without remainder)200...950 (value needs to be divisible by 50 without remainder)1000...4000 (value needs to be divisible by 100 without remainder)

This parameter specifies the relative importance for handling of all SDUs belonging to the UMTS bearer com-pared to the SDUs of the other bearers. [0] subscribed123

Packet Data Protocol Type“IP“

Notes• If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default val-

ues. • Definitions of parameters can be found in 3GPP TS 23.107

<Transfer delay>(num)

<Traffic handling priority>(num)

<PDP_type>(str)

BGS3 AT Command Set 11.8 AT+CGEQREQ


11.8 AT+CGEQREQ Rel. 99 Quality of Service Profile (Requested)

Syntax

Command DescriptionThe test command returns values supported as a compound value. The read command returns the current settings for each defined context. The write command allows the TE to specify a Quality of Service Profile for the context identified by the (local)context identification parameter <cid> which is used when the MT sends an Activate PDP Context Requestmessage to the network. A special form of the write command, AT+CGEQREQ=<cid> causes the requested profile for context number<cid> to become undefined.AT&F and ATZ will undefine the QoS profiles of every context which is not active or not online.



Test Command

AT+CGEQREQ=?Response(s)

+CGEQREQ: <PDP_type>, (list of supported <Traffic class>s), (list of supported <Maximum bitrate UL>s), (list of supported <Maximum bitrate DL>s), (list of supported <Guaranteed bitrate UL>s), (list of supported <Guaranteed bitrate DL>s), (list of supported <Delivery order>s), (list of supported <Maximum SDU size>s), (list of supported <SDU error ratio>s), (list of supported <Residual bit error ratio>s), (list of supported <Delivery of erroneous SDUs>s), (list of supported <Transfer delay>s), (list of supported <Traffic handling priority>s)OK

Read Command

AT+CGEQREQ?Response(s)

[+CGEQREQ: <cid>, <Traffic class>, <Maximum bitrate UL>, <Maximum bitrate DL>, <Guaranteed bitrate UL>, <Guaranteed bitrate DL>, <Delivery order>, <Maximum SDU size>, <SDU error ratio>, <Residual bit error ratio>, <Delivery of erroneous SDUs>, <Transfer delay>, <Traffic handling priority>][+CGEQREQ: ...]

Write Command

AT+CGEQREQ=[<cid>[, <Traffic class>[, <Maximum bitrate UL>[, <Maximum bitrate DL>[, <Guaranteed bitrate UL>[, <Guaranteed bitrate DL>[, <Delivery order>[, <Maximum SDU size>[, <SDU error ratio>[, <Residual bit error ratio>[, <Delivery of erroneous SDUs>[, <Transfer delay>[, <Traffic handling priority>]]]]]]]]]]]]]Response(s)



+ + + + + + - - 3GPP TS 27.007

<cid>(num)



0 conversational1 streaming2 interactive3 background[4] subscribed value

This parameter indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As anexample a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQREQ=...,32,...). [0] subscribed value1...6364...128 (value needs to be divisible by 8 without remainder)256512

This parameter indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP. As anexample a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQREQ=...,32,...). [0] subscribed value1...6364...256 (value needs to be divisible by 8 without remainder)512

This parameter indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (providedthat there is data to deliver). As an example a bitrate of 32kbit/s would be specified as 32 (e.g.AT+CGEQREQ=...,32,...). [0] subscribed value1...6364...128 (value needs to be divisible by 8 without remainder)

This parameter indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (pro-vided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as 32 (e.g.AT+CGEQREQ=...,32,...). [0] subscribed value1...6364...256 (value needs to be divisible by 8 without remainder)

This parameter indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not. 0 no1 yes[2] subscribed value

<Traffic class>(num)

<Maximum bitrate UL>(num)

<Maximum bitrate DL>(num)

<Guaranteed bitrate UL>(num)

<Guaranteed bitrate DL>(num)

<Delivery order>(num)



This parameter indicates the maximum allowed SDU size in octets.[0] subscribed value10...1520 (value needs to be divisible by 10 without remainder)1502

This parameter indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratiois defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error ratioof 5*10-3 would be specified as "5E3" (e.g. AT+CGEQREQ=...,"5E3",...). [“0E0“] subscribed value“1E2““7E3““1E3““1E4““1E5““1E6““1E1“

This parameter indicates the target value for the undetected bit error ratio in the delivered SDUs. If no errordetection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value isspecified as "mEe". As an example a target residual bit error ratio of 5*10-3 would be specified as "5E3" (e.g.AT+CGEQREQ=...,"5E3",...). [“0E0“] subscribed value“5E2““1E2““5E3““4E3““1E3““1E4““1E5““1E6““6E8“

This parameter indicates whether SDUs detected as erroneous shall be delivered or not.0 no1 yes2 no detect[3] subscribed value

<Maximum SDU size>(num)

<SDU error ratio>(str)

<Residual bit error ratio>(str)

<Delivery of erroneous SDUs>(num)



This parameter indicates the targeted time between request to transfer an SDU at one SAP to its delivery at theother SAP, in milliseconds. [0] subscribed value10...150 (value needs to be divisible by 10 without remainder)200...950 (value needs to be divisible by 50 without remainder)1000...4000 (value needs to be divisible by 100 without remainder)

This parameter specifies the relative importance for handling of all SDUs belonging to the UMTS bearer com-pared to the SDUs of the other bearers. [0] subscribed123



ues. • Definitions of parameters can be found in 3GPP TS 23.107

<Transfer delay>(num)

<Traffic handling priority>(num)

<PDP_type>(str)

BGS3 AT Command Set 11.9 AT+CGPADDR


11.9 AT+CGPADDR Show PDP address

Syntax

Command DescriptionThe test command returns a list of defined <cid>s. The write command returns a list of PDP addresses for the specified context identifiers. If no <cid> is specified,the addresses for all defined contexts are returned.


A numeric parameter which specifies a particular PDP context definition (see AT+CGDCONT command).

A string that identifies the MT in the address space applicable to the PDP. The address may be static or dynamic.

Note• If no <cid> is specified, the write command will return a list of all defined contexts.

Test Command

AT+CGPADDR=?Response(s)

[+CGPADDR: (list of defined <cid>s)]OK

Write Command

AT+CGPADDR=[<cid>[,<cid>]]Response(s)

[+CGPADDR: <cid>, <PDP_address>][+CGPADDR: <cid>, <PDP_address>]OKERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07

<cid>(num)

<PDP_address>(str)

BGS3 AT Command Set 11.10 AT+CGQMIN


11.10 AT+CGQMIN Quality of Service Profile (Minimum acceptable)

Syntax

Command DescriptionThe test command returns values supported as a compound value. If the MT supports several PDP types, theparameter value ranges for each PDP type are returned on a separate line. The read command returns the current settings for each defined context. This command allows the TE to specify a minimum acceptable profile which is checked by the MT against thenegotiated profile returned in the Activate PDP Context Accept message.The set command specifies a profile for the context identified by the (local) context identification parameter,<cid>.Please note, that the parameters of the minimum acceptable profile need to meet the following condition:

If this condition is not fulfilled or the network does not support all of the specified minimum QoS settings, thenthe activation of the associated context will fail. A special form of the set command, AT+CGQMIN= <cid> causes the minimum acceptable profile for contextnumber <cid> to become undefined. In this case no check is made against the negotiated profile. AT&F and ATZ will undefine the minimum QoS profiles of every context which is not active or not online.

Test Command

AT+CGQMIN=?Response(s)

+CGQMIN: <PDP_type>, (list of supported <precedence>s), (list of supported <delay>s), (list of supported <reliability>s), (list of supported <peak>s), (list of supported <mean>s)OKERROR+CME ERROR: <err>

Read Command

AT+CGQMIN?Response(s)

[+CGQMIN: <cid>, <precedence>, <delay>, <reliability>, <peak>, <mean>][+CGQMIN: ...]OKERROR+CME ERROR: <err>

Write Command

AT+CGQMIN=[<cid>[, <precedence>[, <delay>[, <reliability>[, <peak>[, <mean>]]]]]]Response(s)



+ + + + + + - - GSM 07.07

((AT+CGQMIN.<delay>= 0) OR (AT+CGQREQ.<delay> ≤ AT+CGQMIN.<delay>)) AND ((AT+CGQMIN.<reliability>= 0) OR (AT+CGQREQ.<reliability> ≤ AT+CGQMIN.<reliability>)) AND ((AT+CGQMIN.<peak>= 0) OR (AT+CGQREQ.<peak> ≥ AT+CGQMIN.<peak>)) AND ((AT+CGQMIN.<precedence>= 0) OR (AT+CGQREQ.<precedence> ≤ AT+CGQMIN.<precedence>)) AND (AT+CGQREQ.<mean> ≥ AT+CGQMIN.<mean>)





Precedence class[0] network subscribed value1 High Priority

Service commitments shall be maintained ahead of precedence classes 2 and3

2 Normal priorityService commitments shall be maintained ahead of precedence class 3

3 Low priorityService commitments shall be maintained

Delay classThe delay parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through theGPRS network(s).[0] network subscribed value1..4 SDU size: 128 octets:

SDU size: 1024 octets:

Reliability class[0] network subscribed value1 Non real-time traffic, error-sensitive application that cannot cope with data loss2 Non real-time traffic, error-sensitive application that can cope with infrequent

data loss3 Non real-time traffic, error-sensitive application that can cope with data loss,

GMM/SM, and SMS

<cid>(num)

<precedence>(num)

<delay>(num)

Delay Class Mean Transfer Delay 95 percentile1 (Predictive) <0.5 <1.52 (Predictive) <5 <253 (Predictive) <50 <2504 (Best Effort) Unspecified

Delay Class Mean Transfer Delay 95 percentile1 (Predictive) <0.5 <1.52 (Predictive) <5 <253 (Predictive) <50 <2504 (Best Effort) Unspecified

<reliability>(num)



4 Real-time traffic, error-sensitive application that can cope with data loss5 Real-time traffic, error non-sensitive application that can cope with data loss

Peak throughput class (in octets per second).[0] network subscribed value1 Up to 1 000 (8 kbit/s).2 Up to 2 000 (16 kbit/s).3 Up to 4 000 (32 kbit/s).4 Up to 8 000 (64 kbit/s).5 Up to 16 000 (128 kbit/s).6 Up to 32 000 (256 kbit/s).7 Up to 64 000 (512 kbit/s).8 Up to 128 000 (1024 kbit/s).9 Up to 256 000 (2048 kbit/s).

Mean throughput class(in octets per hour).[0] network subscribed value1 100 (~0.22 bit/s)2 200 (~0.44 bit/s)3 500 (~1.11 bit/s)4 1 000 (~2.2 bit/s)5 2 000 (~4.4 bit/s)6 5 000 (~11.1 bit/s)7 10 000 (~22 bit/s)8 20 000 (~44 bit/s)9 50 000 (~111 bit/s)10 100 000 (~0.22 kbit/s)11 200 000(~0.44 kbit/s)12 500 000(~1.11 kbit/s)13 1 000 000 (~2.2 kbit/s)14 2 000 000 (~4.4 kbit/s)15 5 000 000 (~11.1 kbit/s)16 10 000 000 (~22 kbit/s)17 20 000 000 (~44 kbit/s)18 50 000 000 (~111 kbit/s)31 best effort


<peak>(num)

<mean>(num)

<PDP_type>(str)




ues. • Definitions of parameters in GSM 02.60 and GSM 03.60 paragraph 15.2 "Quality of Service Profile".

Example

If some of the QoS parameters are omitted, they will keep their current value (or the default value if not specifiedso far), e.g.: AT+CGDCONT=1,"IP"OKAT+CGQMIN=OKAT+CGQMIN?+CGQMIN:1,0,0,0,0,0OKAT+CGQMIN=1,0OKAT+CGQMIN?+CGQMIN:1,0,0,0,0,0OKAT+CGQMIN=1,0,0,0,1OKAT+CGQMIN?+CGQMIN:1,0,0,0,1,0OKAT+CGQMIN=1,1OKAT+CGQMIN?+CGQMIN:1,1,0,0,1,0OK

BGS3 AT Command Set 11.11 AT+CGQREQ


11.11 AT+CGQREQ Quality of Service Profile (Requested)

Syntax

Command DescriptionThe test command returns values supported as a compound value. If the MT supports several PDP types, theparameter value ranges for each PDP type are returned on a separate line. The read command returns the current settings for each defined context. This command allows the TE to specify a Quality of Service Profile that is used when the MT sends an ActivatePDP Context Request message to the network.The set command specifies a profile for the context identified by the (local) context identification parameter,<cid>. Please note, that the parameters of the requested QoS profile need to meet the following condition:

If this condition is not fulfilled or the network does not support all of the requested QoS settings, then the activa-tion of the associated context will fail. A special form of the set command, +CGQREQ=<cid> causes the requested profile for context number <cid>to become undefined.AT&F and ATZ will undefine the QoS profiles of every context which is not active or not online.

Test Command

AT+CGQREQ=?Response(s)

+CGQREQ: <PDP_type>, (list of supported <precedence>s), (list of supported <delay>s), (list of supported <reliability>s), (list of supported <peak>s), (list of supported <mean>s)OK

Read Command

AT+CGQREQ?Response(s)

[+CGQREQ: <cid>, <precedence>, <delay>, <reliability>, <peak>, <mean>][+CGQREQ: ...]

Write Command

AT+CGQREQ=[<cid>[, <precedence>[, <delay>[, <reliability>[, <peak>[, <mean>]]]]]]Response(s)



+ + + + + + - - GSM 07.07

((AT+CGQMIN.<delay>= 0) OR (AT+CGQREQ.<delay> ≤ AT+CGQMIN.<delay>)) AND ((AT+CGQMIN.<reliability>= 0) OR (AT+CGQREQ.<reliability> ≤ AT+CGQMIN.<reliability>)) AND ((AT+CGQMIN.<peak>= 0) OR (AT+CGQREQ.<peak> ≥ AT+CGQMIN.<peak>)) AND ((AT+CGQMIN.<precedence>= 0) OR (AT+CGQREQ.<precedence> ≤ AT+CGQMIN.<precedence>)) AND (AT+CGQREQ.<mean> ≥ AT+CGQMIN.<mean>)





Precedence class[0] network subscribed value1 High Priority

Service commitments shall be maintained ahead of precedence classes 2 and3

2 Normal priorityService commitments shall be maintained ahead of precedence class 3

3 Low priorityService commitments shall be maintained

Delay classThis parameter defines the end-to-end transfer delay incurred in the transmission of SDUs through the GPRSnetwork(s).[0] network subscribed value1..4 with SDU size = 128 octets:

with SDU size = 1024 octets:

Reliability class[0] network subscribed value1 Non real-time traffic, error-sensitive application that cannot cope with data loss2 Non real-time traffic, error-sensitive application that can cope with infrequent

data loss3 Non real-time traffic, error-sensitive application that can cope with data loss,

GMM/SM, and SMS

<cid>(num)

<precedence>(num)

<delay>(num)

Delay Class Mean Transfer Delay 95 percentile1 (Predictive) <0.5 <1.52 (Predictive) <5 <253 (Predictive) <50 <2504 (Best Effort) Unspecified -

Delay Class Mean Transfer Delay 95 percentile1 (Predictive) <0.5 <1.52 (Predictive) <5 <253 (Predictive) <50 <2504 (Best Effort) Unspecified -

<reliability>(num)



4 Real-time traffic, error-sensitive application that can cope with data loss5 Real-time traffic, error non-sensitive application that can cope with data loss

Peak throughput classin octets per second[0] network subscribed value1 Up to 1 000 (8 kbit/s)2 Up to 2 000 (16 kbit/s)3 Up to 4 000 (32 kbit/s)4 Up to 8 000 (64 kbit/s)5 Up to 16 000 (128 kbit/s)6 Up to 32 000 (256 kbit/s)7 Up to 64 000 (512 kbit/s)8 Up to 128 000 (1024 kbit/s)9 Up to 256 000 (2048 kbit/s)

Mean throughput classin octets per hour[0] network subscribed value1 100 (~0.22 bit/s)2 200 (~0.44 bit/s)3 500 (~1.11 bit/s)4 1 000 (~2.2 bit/s)5 2 000 (~4.4 bit/s)6 5 000 (~11.1 bit/s)7 10 000 (~22 bit/s)8 20 000 (~44 bit/s)9 50 000 (~111 bit/s)10 100 000 (~0.22 kbit/s)11 200 000(~0.44 kbit/s)12 500 000(~1.11 kbit/s)13 1 000 000 (~2.2 kbit/s)14 2 000 000 (~4.4 kbit/s)15 5 000 000 (~11.1 kbit/s)16 10 000 000 (~22 kbit/s)17 20 000 000 (~44 kbit/s)18 50 000 000 (~111 kbit/s)31 best effort

Packet Data Protocol type“IP“

<peak>(num)

<mean>(num)

<PDP_type>(str)




ues. • Definitions of parameters in GSM 02.60 and GSM 03.60 paragraph 15.2 "Quality of Service Profile".

Example

If some of the QoS parameters are omitted, they will keep their current value (or the default value if not specifiedso far), e.g.: AT+CGDCONT=1,"IP"OKAT+CGQREQ=OKAT+CGQREQ?+CGQREQ:1,0,0,0,0,0OKAT+CGQREQ=1,0OKAT+CGQMIN?+CGQREQ:1,0,0,0,0,0OKAT+CGQREQ=1,0,0,0,1OKAT+CGQREQ?+CGQREQ:1,0,0,0,1,0OKAT+CGQREQ=1,1OKAT+CGQREQ?+CGQREQ:1,1,0,0,1,0OK

BGS3 AT Command Set 11.12 AT+CGREG


11.12 AT+CGREG GPRS Network Registration Status

AT+CGREG write command enables presentation of URC "+CGREG: <stat>" when <n>=1 and ME's GPRS net-work registration status changes, or URC "+CGREG: <stat>, <lac>, <ci>" when <n>=2 and the current net-work cell changes. AT+CGREG read command queries the current URC presentation status and <stat> which shows whether thenetwork has currently indicated the registration of the ME. Location information elements <lac> and <ci> arereturned only if <n>=2 and ME is registered to the network.

Syntax


URC 1

+CGREG: <stat>

Indicates a change in the ME's GPRS network registration status.

URC 2

+CGREG: <stat>, <lac>, <ci>

Indicates a change in the ME's GPRS network registration status or a change of the network cell includinglocation information.


0(&F)(P) Disable network registration unsolicited result code1 Enable network registration URC "+CGREG: <stat>" 2 Enable network registration URC "+CGREG: <stat>, <lac>, <ci>"

Test Command

AT+CGREG=?Response(s)

+CGREG: (list of supported <n>s)OK

Read Command

AT+CGREG?Response(s)

+CGREG: <n>, <stat>[, <lac>, <ci>]OK

Write Command

AT+CGREG=[<n>]Response(s)



+ + + + + + - - GSM 07.07

<n>(num)

BGS3 AT Command Set 11.12 AT+CGREG


0 Not registered, ME is not currently searching an operator to register to. The MEis in GMM state GMM-NULL or GMM-DEREGISTERED-INITIATED.GPRS service is disabled, the ME is allowed to attach to GPRS if requested bythe user.

1 Registered, home network. The ME is in GMM state GMM-REGISTERED orGMM-ROUTING-AREA-UPDATING-INITIATED INITIATED on the homePLMN

2 Not registered, but ME is currently trying to attach or searching an operator toregister to. The ME is in GMM state GMM-DEREGISTERED or GMM-REGIS-TERED-INITIATED. The GPRS service is enabled, but an allowable PLMN iscurrently not available. The ME will start a GPRS attach as soon as an allow-able PLMN is available.

3 Registration denied. The ME is in GMM state GMM-NULL. The GPRS serviceis disabled, the ME is not allowed to attach to GPRS if requested by the user.

4 Unknown5 Registered, roaming. The ME is in GMM state GMM-REGISTERED or GMM-

ROUTING-AREA-UPDATING-INITIATED on a visited PLMN.

Two byte location area code in hexadecimal format.

Two byte cell ID in hexadecimal format.

Note• When the module is GPRS attached and a PLMN reselection occurs to a non-GPRS network or to a network

where the SIM is not subscribed to for using GPRS, the resulting GMM (GPRS mobility management) stateaccording to GSM 24.008 is REGISTERED/NO CELL, meaning that the read command will still show<stat>=1 or <stat>=5.

<stat>(num)

<lac>(str)

<ci>(str)

BGS3 AT Command Set 11.13 AT+CGSMS


11.13 AT+CGSMS Select service for MO SMS messages

Syntax

Command DescriptionThe test command is used for requesting information on which services and service preferences can be set byusing the AT+CGSMS write command The read command returns the currently selected service or service preference. The write command is used to specify the service or service preference that the MT will use to send MO SMSmessages. If parameter <service> is not given, the current value remains unchanged.


A numeric parameter which indicates the service or service preference to be used. Parameter is global for allinterfaces and volatile. 0 GPRS 1 Circuit switched 2 GPRS preferred (use circuit switched SMS transfer if GPRS SMS transfer is

not possible, for example when the mobile is not GPRS attached or the networkdoes not support SMS over GPRS)

3(&F)(P) Circuit switched preferred (use GPRS if circuit switched is not available)

Note• Sending SMS via GPRS is only possible when mobile is attached using AT+CGATT.

Test Command

AT+CGSMS=?Response(s)

+CGSMS: (list of supported <service>s)OK

Read Command

AT+CGSMS?Response(s)

+CGSMS: <service>OK

Write Command

AT+CGSMS=[<service>]Response(s)



+ + + + + + - - GSM 07.07

<service>(num)

BGS3 AT Command Set 11.14 AT^SGACT


11.14 AT^SGACT Query all PDP context activations

Syntax

Command DescriptionThe test command returns supported interfaces and states. The read command lists the activation states for all activated PDP contexts of the ME. Contexts, which are cre-ated internally by the GPRS modem compatibility commands, will displayed only, if they are activated. The Out-put of this command is unsorted. The exec command returns the sum of all activated PDP contexts of the ME.


InterfaceIndicates the interface on which a particular PDP context was defined. Every PDP context defined with the com-mand AT+CGDCONT or internally by the GPRS modem compatibility commands is identified one-to-one by its(local) context identifier and the interface on which it was defined. The range of supported interfaces is returnedby the test command. 0 ASC0 or Multiplex channel 11 ASC1 or Multiplex channel 22 Multiplex channel 3

PDP context identifierThe interface local identifier which was used to define a PDP context using the command AT+CGDCONT or whichwas created internally by using the GPRS modem compatibility commands ATD*98# or ATD*99#. The rangeof supported values is returned by the AT+CGDCONT test command. Values 3 and 4 will be used by the GPRSmodem compatibility commands ATD*98# or ATD*99# if no context identifier was specified as the commandwas invoked.

Test Command

AT^SGACT=?Response(s)

^SGACT: (range of supported <ifc>s) , (range of supported <state>s)OK

Read Command

AT^SGACT?Response(s)

[^SGACT: <ifc>, <cid>, <state>][^SGACT: <ifc>, <cid>, <state>][^SGACT: ...]OK

Exec Command

AT^SGACTResponse(s)

^SGACT: <sum>OK


+ + + + + + - -

<ifc>(num)

<cid>(num)

BGS3 AT Command Set 11.14 AT^SGACT


PDP context activation stateIndicates the state of the PDP context activation. 0 Deactivated1 Activated

The sum of all activated PDP contexts of the ME.

<state>(num)

<sum>(num)

BGS3 AT Command Set 11.15 AT^SGAUTH


11.15 AT^SGAUTH Set type of authentication for PPP connection

Syntax


Indicates types of supported authentication.0 none1(&F)(P) PAP2 CHAP3 MS-CHAP-V1, CHAP and PAP

Test Command

AT^SGAUTH=?Response(s)

^SGAUTH: (list of supported <auth>s)OKERROR+CME ERROR: <err>

Read Command

AT^SGAUTH?Response(s)

^SGAUTH: <auth>OKERROR+CME ERROR: <err>

Write Command

AT^SGAUTH=<auth>Response(s)



- + + + + + - -

<auth>(num)

BGS3 AT Command Set 11.16 AT^SGCONF


11.16 AT^SGCONF Configuration of GPRS related Parameters

Syntax


The maximum number of octets in an information field of Unnumbered (U) frames. Parameter is non-volatile. 0 No negotiation with network (500 will be used).140...500(D)...1520 Lower values diminish performance.

The maximum number of octets in an information field of Combined Information (I) frames. Parameter is non-volatile. 0 No negotiation with network (500 will be used).140...500(D)...1520 Lower values diminish performance.

GPRS Multislot Class. The value can be one of the classes indicated with the Test command. The value set isvolatile and powerup value is the maximum allowed.

Note• AT^SGCONF will respond with "+CME ERROR: operation temporary not allowed" if the module is already

GPRS attached (see AT+CGATT). The same error response is sent during background protocol stack activity,e.g. during network registration.

Test Command

AT^SGCONF=?Response(s)

^SGCONF: (list of supported <llc_pdu_length_U>s), (list of supported <llc_pdu_length_I>s), (list of supported <GPRS msclass>es)OK

Read Command

AT^SGCONF?Response(s)

^SGCONF: <llc_pdu_length_U>, <llc_pdu_length_I>, <GPRS msclass>OK

Write Command

AT^SGCONF=[<llc_pdu_length_U>][, [<llc_pdu_length_I>][, [<GPRS msclass>]]]Response(s)



- + + + + + - -

<llc_pdu_length_U>(num)

<llc_pdu_length_I>(num)

<GPRS msclass>(num)

BGS3 AT Command Set 11.17 ATA


11.17 ATA Manual response to a network request for PDP context acti-vation

The V.250 ATA command may be used to accept a network request for a PDP context activation announced bythe unsolicited result codes "RING" or "+CRING: GPRS". The MT responds with CONNECT, enters V.250 onlinedata state and follows the same procedure as it would after having received a AT+CGANS=1 with no <L2P> or<cid> values specified. If you try to answer a request which is no longer present or which is already answered by another instance, NOCARRIER is returned.

SyntaxExec Command

ATAResponse(s)

CONNECTNO CARRIER


+ + + + + + - + GSM 07.07

BGS3 AT Command Set 11.18 ATD*99#


11.18 ATD*99# Request GPRS service

This command causes the MT to perform whatever actions are necessary to establish a communication betweenthe TE and the external PDN.The V.250 'D' (Dial) command causes the MT to enter the V.250 online data state and, with the TE, to start thespecified layer 2 protocol. No further commands may follow on the AT command line. GPRS attachment andPDP context activation procedures may take place prior to or during the PDP startup if they have not alreadybeen performed using the AT+CGATT and AT+CGACT commands. Examples on how to use this command are provided in "Section 11.22, Using GPRS AT commands (Examples)". To confirm acceptance of the command before entering the V.250 online data state command will respond withCONNECT. When the layer 2 protocol has terminated, either as a result of an orderly shut down of the PDP or an error, theMT enters V.250 command state and returns NO CARRIER (for details refer to Section 11.5.1, Automatic deac-tivation of PDP context during dial-up PPP).

Syntax


This parameter is currently not used and needs not to be specified.

Layer 2 protocol to be used between the TE and MT. “PPP“ layer 2 protocol PPP“1“ layer 2 protocol PPP

Parameter specifies a particular PDP context definition (see AT+CGDCONT command). If no context is specified,an internal context with default properties is used (see AT+CGDCONT, AT+CGQREQ and AT+CGQMIN). 1...2

Notes• If BGS3 is in dedicated mode, command returns the result code BUSY.• ATD is used as a standard V.250 AT command, too.• When using the command on the second serial interface please see also Section 1.9.

Exec Command

ATD*99[* [<called_address>][* [<L2P>][* [<cid>]]]]# Response(s)

CONNECTNO CARRIER


+ + + + + + - + GSM 07.07

<called_address>(str)

<L2P>(str)

<cid>(num)

BGS3 AT Command Set 11.19 ATD*98#


11.19 ATD*98# Request GPRS IP service

This command causes the MT to perform whatever actions are necessary to establish a communication betweenthe TE and the external PDN.The V.250 'D' (Dial) command causes the MT to enter the V.250 online data state and, with the TE, to start thelayer 2 protocol. GPRS attachment and PDP context activation procedures may take place prior to or during the PDP startup ifthey have not already been performed using the AT+CGATT and AT+CGACT commands. To confirm acceptance of the command before entering the V.250 online data state command will respond withCONNECT. When the layer 2 protocol has terminated, either as a result of an orderly shut down of the PDP or an error, theMT enters V.250 command state and returns NO CARRIER (for details refer to Section 11.5.1, Automatic deac-tivation of PDP context during dial-up PPP).

Syntax


Parameter specifies a particular PDP context definition (see AT+CGDCONT command). If no context is specified,an internal context with default properties is used (see AT+CGDCONT, AT+CGQREQ and AT+CGQMIN). 1...2

Notes• If BGS3 is in dedicated mode, command returns the result code BUSY.• ATD is used as a standard V.250 AT command, too.• When using the command on the second serial interface please see also Section 1.9.

Exec Command

ATD*98[* <cid>]# Response(s)

CONNECTNO CARRIER


+ + + + + + - + GSM 07.07

<cid>(num)

BGS3 AT Command Set 11.20 ATH


11.20 ATH Manual rejection of a network request for PDP context acti-vation

The V.250 ATH command may be used to deactivate all PDP contexts which are active or online on the sameinterface. This command should not be used to deactivate PDP contexts during the implicit PDP context deacti-vation procedure which is started automatically after LCP termination or by dropping the DTR line (if AT&D2 isconfigured). For details refer to Section 11.5.1, Automatic deactivation of PDP context during dial-up PPP. The ATH command may also be used to reject a network request for PDP context activation announced by theunsolicited result codes "RING: GPRS" or "+CRING: GPRS".

Syntax

Notes• In contrast to GSM 07.07 it is possible to cancel a connection with ATH after a break. This is done for com-

patibility reasons due to the "dial-up network" drivers of Microsoft Windows. • ATH is used as a standard V.250 AT command, too.• If ATH is used to reject a network request for PDP context activation, then other PDP contexts on the same

interface which are active or online will not be deactivated.

Exec Command

ATHResponse(s)

OK


+ + ± + ± ± - - GSM 07.07



11.21 ATS0 Automatic response to a network request for PDP context activation

The V.250 ATS0=<n> (Automatic answer) command may be used to turn off (n=0) and on (n>0) the automaticresponse to a network request for a PDP context activation. See also "3GPP TS 27.007 (GSM 07.07): AT com-mand set for User Equipment (UE)". When the ATS0=<n> (<n> > 0) command is received, the MT will attempt to perform a GPRS attach if not yetattached and if configured to do so (see AT^SCFG, parameter <gs0aa>). Subsequently, the MT will announcea network request for PDP context activation by issuing the URC RING or CRING to the TE, followed by the inter-mediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure asit would after receiving a AT+CGANS=1 command with no <L2P> or <cid> values specified.ATS0=0 does not perform an automatic GPRS detach.

Syntax


000(&F) Disables automatic answer mode.001-255 Enables automatic answering after specified number of rings.

Notes• If different settings are used on each interface, and a request for PDP context activation is received, the inter-

face 'wins' which is idle and uses the smallest ATS0 value.• When a network request for PDP context activation is answered automatically and another AT command is

issued at the same time on the same interface then this AT command will not be executed. Any responserelates to the automatic context activation procedure. If the AT command which caused the collision was aCS data call, the CONNECT response does not pertain to this data call but to GPRS. This can be detected ifATX is not set to 0. The CS data call will issue CONNECT <text>, GPRS will issue CONNECT only.

• A network request for PDP context activation has a maximum duration of approximately 40 seconds (fordetails see GSM 04.08). A RING/CRING URC is issued every 5 seconds, so setting parameter <n> to valuesgreater than 7 will not allow a successful context activation and is not recommended.

• Automatic GPRS attach will not be performed on recalling a stored user profile with ATZ or on power-up, eventhough a value <n> greater than 0 was stored in the user profile with AT&W.

• If AT^SCFG="GPRS/ATS0/withAttach","on" is selected, but the automatic GPRS attach attempt fails (e.g. thenetwork rejects the attach request), the ATS0 write command ends up with "ERROR" or "+CME ERROR:unknown" after approx. 5 minutes, though the new <n> value takes effect. This is necessary because ATS0is used for circuit switched calls too.

• ATS0 write command is PIN protected.

Read Command

ATS0?Response(s)

<n>OK

Write Command

ATS0=<n>Response(s)

OK


± + + + + + - - GSM 07.07

<n>(num)(&W)(&V)

BGS3 AT Command Set 11.22 Using GPRS AT commands (Examples)


11.22 Using GPRS AT commands (Examples)

ExamplesEXAMPLE 1

Defining and using a Context Definition ID (CID): Every time a CID is used as a parameter for a GPRS command the CID has to be defined before by usingthe AT+CGDCONT command. To get the parameter of a CID use the AT+CGDCONT read option. If the responseof 'AT+CGDCONT?' is OK only, there is no CID defined.

All parameters of the CID are initiated by NULL or not present values, and the CID itself is set to be undefined.To define a CID use the AT+CGDCONT command with at least one CID parameter. At the moment the mobilesupports CID 1 and CID 2 by using the AT+CGDCONT command.

Define CID 1 and set the PDP type to IP, access point name and IP address are not set:

Define CID 2 and sets PDP type, APN and IP addr:

A following read command will respond:

Set the CID 1 to be undefined:


AT+CGDCONT?OK There is no CID defined

AT+CGDCONT=1,"IP"OK

AT+CGDCONT=2,"IP", "internet.t-d1.gprs", 111.222.123.234OK

AT+CGDCONT?+CGDCONT:1,"IP","","",0,0+CGDCONT:2,"IP","internet.t-d1.gprs",111.222.123.234OK

AT+CGDCONT=1OK

AT+CGDCONT?+CGDCONT:2,"IP","internet.t-d1.gprs",111.222.123.234OK

BGS3 AT Command Set 11.22 Using GPRS AT commands (Examples)


EXAMPLE 2

Quality of Service (QoS) is a special parameter of a CID which consists of several parameters itself.The QoS consists of - the precedence class- the delay class- the reliability class- the peak throughput class- the mean throughput classand is divided in "requested QoS" and "minimum acceptable QoS".

All parameters of the QoS are initiated by default to the "network subscribed value (= 0)" but the QoS itself isset to be undefined. To define a QoS use the AT+CGQREQ or AT+CGQMIN command.

Overwrite the precedence class of QoS of CID 1 and set the QoS of CID 1 to be present:


All QoS values of CID 1 are set to network subscribed now, except precedence class which is set to 2. Nowset the QoS of CID 1 to not present:

Once defined, the CID it can be activated. To activate CID 2 use:

If the CID is already active, the mobile responds OK at once.If no CID and no STATE is given, all defined CIDs will be activated by:

If no CID is defined the mobile responds +CME ERROR: invalid indexRemark: If the mobile is NOT attached by AT+CGATT=1 before activating, the attach is automatically done bythe AT+CGACT command.

After defining and activating a CID it may be used to get online by:

The mobile supports Layer 2 Protocol (L2P) PPP only.Remark: If the mobile is NOT attached by AT+CGATT=1 and the CID is NOT activated before connecting,attaching and activating is automatically done by the AT+CGDATA command.

AT+CGQREQ=1,2OK

AT+CGQREQ?+CGQREQ: 1,2,0,0,0,0OK

AT+CGQREQ=1OK

AT+CGACT=1,2OK

AT+CGACT=OK

AT+CGDATA="PPP",1CONNECT The mobile is connected using the parameters of CID 1.

AT+CGDATA=CONNECT The mobile is connected using default parameters (<L2P>="PPP" and

<cid> as described for command AT+CGDATA).

BGS3 AT Command Set 11.23 Using the GPRS dial command ATD


11.23 Using the GPRS dial command ATD

Example

In addition to the GPRS AT commands you can use the "D" command to dial into to the GPRS network.

There are two GPRS Service Codes for the ATD command: Values 98 and 99.Examples: ATD*99#CONNECT Establish a connection by service code 99.

ATD*99*123.124.125.126*PPP*1#CONNECT Establish a connection by service code 99, IP

address 123 and L2P = PPP and using CID 1.The CID has to be defined by AT+CGDCONT.

ATD*99**PPP#CONNECT Establish a connection by service code 99 and L2P

= PPP.

ATD*99***1#CONNECT Establish a connection by service code 99 and using

CID 1.

ATD*99**PPP*1#CONNECT Establish a connection by service code 99 and L2P

= PPP and using CID 1. The CID has to be definedby AT+CGDCONT.

ATD*98#CONNECT Establish a connection by service code 98.

ATD*98*1#CONNECT Establish an IP connection by service code 98 using

CID 1. The CID has to be defined by AT+CGDCONT.

BGS3 AT Command Set 12. FAX Commands


12. FAX Commands

This chapter describes the AT commands used for fax communications. If the ME is acting as a fax modem for a PC based fax application it is necessary to select the proper ServiceClass (Fax Class) provided by the ME. The ME reports its Service Class capabilities, i.e. the current setting andthe range of services available. This is provided by the AT+FCLASS command.

Service Classes supported by the ME:

During an active fax connection the AT parser functionality on the used channel is limited to the AT commandswhich according to the ITU V.250 and T.31 specifications are mandatory for fax communications. The functionsof these AT commands are usually supported by commonly used fax applications.

12.1 FAX parameters

This section describes the parameter <mod> used by some of the fax-specific AT commands. To find out thevalue(s) actually supported by the <mod> parameter use the test commands either in on-hook or off-hook mode.


Modulation scheme3 V21 Ch2 - 300 bps 24 V.27ter - 2400 bps 48 V.27ter - 4800 bps 72 V.29 - 7200 bps 96 V.29 - 9600 bps

Note• For AT+FRH and AT+FTH, parameter <mod> can take value 3 only, while AT+FRM and AT+FTM never support

<mod>=3.

12.1.1 Fax Result CodesTable 12.1: Fax Result Codes

AT+FCLASS Parameter Service class Reference, Standard0 Data modem e.g. TIA/EIA-602 or ITU V.2501 Service Class 1 EIA/TIA-578-A

<mod>(num)

Result Code Meaning+FCERROR This facsimile error message notifies the DTE that the DCE has

received a different signal (tone or carrier) than expected. This allows the DTE to recover by requesting the DCE to look for an alternative tone or carrier signal.

BGS3 AT Command Set 12.2 AT+FCLASS


12.2 AT+FCLASS Fax: Select, read or test service class

AT+FCLASS sets the ME to a particular mode of operation (data, fax). This allows the ME to process informationin a manner suitable for that type of information.

Syntax


0(&F) Data (e.g. EIA/TIA-602 or ITU V.250)1 Fax class 1 (EIA/TIA-578-A, Service Class 1)

Notes• Using Error Correcting Mode (ECM) when sending FAXes over GSM should be avoided. • If <n> is set to 1, all incoming calls will be answered as fax calls when ATA is issued on multiplexer channel

1 resp. ASC0. For calls explicitly signaled as voice or data calls, this procedure will fail with result code "NOCARRIER", but the incoming call will continue to ring.It is possible to change the setting of <n> to 0 while the call is ringing, and accept the call afterwards with ATA.

Test Command

AT+FCLASS=?Response(s)

(list of supported <n>s)OK

Read Command

AT+FCLASS?Response(s)

<n>OK

Write Command

AT+FCLASS=<n>Response(s)

OK


- + - + - - - - EIA/TIA-592-A

<n>(num)(&W)(&V)

BGS3 AT Command Set 12.3 AT+FRH


12.3 AT+FRH Receive Data Using HDLC Framing

The AT+FRH command enables the TA to receive frames using the HDLC protocol and the modulation scheme<mod>=3.

An ERROR response code results if the write command is issued while the modem is on-hook. The test com-mand can be used either in on-hook or off-hook mode to check the value supported by the <mod> parameter.

Syntax

Note• BGS3 supports only <mod>=3.

Test Command

AT+FRH=?Response(s)

+FRH:(list of <mod>s)OK

Write Command

AT+FRH=<mod>Response(s)

CONNECTIf error is related to ME functionalityERROR


- + - + - - - - TIA/EIA-578

BGS3 AT Command Set 12.4 AT+FRM


12.4 AT+FRM Receive Data

The AT+FRM command causes the TA to enter the receive mode, using one of the modulation schemes definedin Section 12.1, FAX parameters.

An ERROR response code results if the write command is issued while the modem is on-hook. The test com-mand can be used in on-hook or off-hook mode to check the modulation schemes supported by BGS3.

Syntax

Note• <mod>= 3 is not possible.

Test Command

AT+FRM=?Response(s)

(list of <mod>s)OK

Write Command

AT+FRM=<mod>Response(s)

CONNECTIf error is related to ME functionality:ERROR


- + - + - - - - TIA/EIA-578

BGS3 AT Command Set 12.5 AT+FRS


12.5 AT+FRS Receive Silence

<time>=n causes the TA to report an OK result code to the TE after the specified period of silence was detectedon the line. The command is aborted if any character is received by the TE. The modem discards the aborting character andissues an OK result code. An ERROR response code results if this command is issued while the mode is on-hook.

Syntax


Number of 10 millisecond intervals 0...255

Write Command

AT+FRS=<time>Response(s)

OKIf error is related to ME functionality:ERROR


- + - + - - - - TIA/EIA-578

<time>(num)

BGS3 AT Command Set 12.6 AT+FTH


12.6 AT+FTH Transmit Data Using HDLC Framing

The AT+FTH command causes the TA to transmit data using the HDLC protocol and the modulation scheme<mod>=3.

An ERROR response code results if the write command is issued while the modem is on-hook. The test com-mand can be used either in on-hook or off-hook mode to check the value supported by the <mod> parameter.

Syntax

Note• BGS3 supports only <mod>=3.

Test Command

AT+FTH=?Response(s)

+FTH:(list of <mod>s)OK

Write Command

AT+FTH=<mod>Response(s)

CONNECT


- + - + - - - - TIA/EIA-578

BGS3 AT Command Set 12.7 AT+FTM


12.7 AT+FTM Transmit Data

The AT+FTM command causes the TA to transmit data, using one of the modulation schemes defined in Section12.1, FAX parameters.

An ERROR response code results if the write command is issued while the modem is on-hook. The test com-mand can be used in on-hook or off-hook mode to check the modulation schemes supported by BGS3.

Syntax

Note• <mod>= 3 is not possible

Test Command

AT+FTM=?Response(s)

(list of <mod>s)OK

Write Command

AT+FTM=<mod>Response(s)

CONNECTIf error is related to ME functionality:ERROR


- + - + - - - - TIA/EIA-578

BGS3 AT Command Set 12.8 AT+FTS


12.8 AT+FTS Stop Transmission and Wait

This command causes the TA to terminate a transmission and wait for <time> 10 millisecond intervals beforesending the OK result code to the TE.

Syntax


no. of 10 millisecond intervals 0...85

Write Command

AT+FTS=<time>Response(s)

OKIn on-hook mode:ERROR


- + - + - - - - TIA/EIA-578

<time>(num)

BGS3 AT Command Set 13. Short Message Service (SMS) Commands


13. Short Message Service (SMS) Commands

The AT Commands described in this chapter allow an external application to use the Short Message Service withthe BGS3.

13.1 SMS parameters


Format is same for <pdu> in case of SMS, but without GSM 24.11 SC address field and parameter shall bebounded by double quote characters like a normal string type parameter

String type alphanumeric representation of <da> or <oa> corresponding to the entry found in phonebook; thisfeature is not supported

Command DataGSM 03.40 TP-Command-Data in text mode responses; ME/TA converts each 8-bit octet into two IRA characterlong hexadecimal numbers (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50and 65))

Command TypeGSM 03.40 TP-Command-Type in integer format [0]...255

Destination AddressGSM 03.40 TP- Destination-Address Address-Value field in string format; BCD numbers (or GSM default alpha-bet characters) are converted into characters; type of address given by <toda>

User DataIn case of SMS: GSM 03.40 TP-User-Data in text mode responses; format:• If <dcs> indicates that GSM 03.38 default alphabet is used and <fo> indicates that GSM 03.40 TP-User-

Data-Header-Indication is not set: ME/TA converts GSM alphabet into current TE character set according torules covered in Annex A.

• If <dcs> indicates that 8-bit or UCS2 data coding scheme is used, or <fo> indicates that GSM 03.40 TP-User-Data-Header-Indication is set: ME/TA converts each 8-bit octet into hexadecimal numbers con-tainingtwo IRA characters (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65).

In case of CBS: GSM 03.41 CBM Content of Message in text mode responses; format:• If <dcs> indicates that GSM 03.38 default alphabet is used: ME/TA converts GSM alphabet into current TE

character set according to rules covered in Annex A.• If <dcs> indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts each 8-bit octet into hexa-

decimal numbers containing two IRA characters.

<ackpdu>(num)

<alpha>(str)(+CSCS)

<cdata>(num)

<ct>(num)

<da>(num)(+CSCS)

<data>(num)(+CSCS)

BGS3 AT Command Set 13.1 SMS parameters


Discharge TimeGSM 03.40 TP-Discharge-Time in time-string format: "yy/MM/dd,hh:mm:ss+zz", where characters indicate year(two last digits), month, day, hour, minutes, seconds and time zone. For example, 6th of May 1994, 22:10:00GMT+2 hours equals "94/05/06,22:10:00+08"

IEIa (Information Element Identifier octet) of the concatenated SMS. 8 Concatenated short messages, 8-bit reference number 16 Concatenated short messages, 16-bit reference number

Integer type; value in the range of location numbers supported by the associated memory

Message LengthInteger type value indicating in the text mode (AT+CMGF=1) the length of the message body <data> (or<cdata>) in characters; or in PDU mode (AT+CMGF=0), the length of the actual TP data unit in octets (i.e. theRP layer SMSC address octets are not counted in the length) In text mode, the maximum length of an SMSdepends on the used coding scheme: It is 160 characters if the 7 bit GSM coding scheme is used, and 140 char-acters according to the 8 bit GSM coding scheme. If the SMS message format is ''text mode'' (AT+CMGF=1) and the character set is set to ''UCS2'' with AT+CSCSand the SMS is also coded as "UCS2" (see <dcs> of AT+CSMP), then the length is in octets instead of charac-ters. For concatenated SMS messages the maximum length will be reduced by the length of the user data headerwith respect to <ieia> (6 bytes for <ieia>=8 and 7 bytes for <ieia>=16). In the case of 8-bit data, the max-imum length of the short message field is: 140 octets - (6 or 7) = 134 or 133. In the case of GSM 7 bit defaultalphabet data, the maximum length of the short message is (140 - (6 or 7))*8/7 = 153 or 152 characters. In thecase of 16 bit UC2 data, the maximum length of the short message is: (140 - (6 or 7))/2)= 67 or 66 characters.

Maximum number of all segments to be concatenated into one SMS, beginning with 1. <max>=0 means: ignore the value. This will result in a non-concatenated SMS. 0...255

Memory to be used when listing, reading and deleting messages: “SM“ SIM message storage“ME“ Mobile Equipment message storage“MT“(D) Sum of "SM" and "ME" storages

Memory to be used when writing and sending messages: “SM“ SIM message storage“ME“ Mobile Equipment message storage“MT“(D) Sum of "SM" and "ME" storages

<dt>(num)

<ieia>(num)

<index>(num)

<length>(num)

<max>(num)

<mem1>(str)

<mem2>(str)



Received messages will be placed in this memory storage if routing to TE is not set. See command AT+CNMIwith parameter <mt>=2. “SM“ SIM message storage“MT“(D) Sum of "SM" and "ME" storages

Message IdentifierGSM 03.41 CBM Message Identifier in integer format

Message NumberGSM 03.40 TP-Message-Number in integer format

Message ReferenceGSM 03.40 TP-Message-Reference in integer format

Originating AddressGSM 03.40 TP-Originating-Address Address-Value field in string format; BCD numbers (or GSM default alpha-bet characters) are converted into characters; type of address given by <tooa>

Page ParameterGSM 03.41 CBM Page Parameter bits 4-7 in integer format

Page ParameterGSM 03.41 CBM Page Parameter bits 0-3 in integer format

In the case of SMS: GSM 04.11 SC address followed by GSM 03.40 TPDU in hexadecimal format: ME/TA con-verts each octet of TP data unit into hexadecimal numbers containing two IRA characters (e.g. octet with integervalue 42 is presented to TE as two characters 2A (IRA 50 and 65)). In the case of CBS: <ra> GSM 03.40 TP-Recipient-Address Ad-dress-Value field in string format; BCD numbers (or GSM default alphabet characters)are converted into characters; type of address given by <tora>

Recipient AddressGSM 03.40 TP-Recipient-Address Address-Value field in string format; BCD numbers (or GSM default alphabetcharacters) are converted to characters of the currently selected TE character set (refer to commandAT+CSCS.); type of address given by <tora>

<mem3>(str)

<mid>(num)

<mn>(num)

<mr>(num)

<oa>(num)(+CSCS)

<page>(num)

<pages>(num)

<pdu>(num)

<ra>(num)(+CSCS)



Reference number to identify all segments of the concatenated SMS (i.e. the number needs to be the same foreach segment). If <ieia>=8 then max=255, otherwise 65535. 0...2550...65535

Service Center AddressGSM 04.11 RP SC address Address-Value field in string format; BCD numbers (or GSM default alphabet char-acters) are converted to characters of the currently selected TE character set (refer to command AT+CSCS); typeof address given by <tosca>

Service Centre Time StampGSM 03.40 TP-Service-Centre-Time-Stamp in time-string format (refer <dt>)

Sequence number of the concatenated SMS beginning with 1. The number must be incremented by one foreach segment of the concatenated short message. <seq>=0 means: ignore the value. This will result in a non-concatenated SMS. 0...255

Serial NumberGSM 03.41 CBM Serial Number in integer format

StatusGSM 03.40 TP-Status in integer format 0...255

Message status3GPP 27.005 Interface of SMS and CB. Indicates the status of message in memory.

<ref>(num)

<sca>(num)(+CSCS)

<scts>(num)

<seq>(num)

<sn>(num)

<st>(num)

<stat>(str)

Description text mode (<mode>=1) PDU mode (<mode>=0) DefaultReceived unread mes-sages

"REC UNREAD" 0 for SMS reading com-mands

Received read messages "REC READ" 1 Stored unsent messages "STO UNSENT" 2 for SMS writing com-

mands Stored sent messages "STO SENT" 3 All messages "ALL" 4



Type of Destination AddressGSM 04.11 TP-Destination-Address Type-of-Address octet in integer format (when first character of <da> is +(IRA 43) default is 145, otherwise default is 129) 0...255

Type of Originating AddressGSM 04.11 TP-Originating-Address Type-of-Address octet in integer format (default refer <toda>)

Type of Recipient AddressGSM 04.11 TP-Recipient-Address Type-of-Address octet in integer format (default refer <toda>)

Type of Service Center AddressGSM 04.11 RP SC address Type-of-Address octet in integer format (default refer <toda>)

<toda>(num)

<tooa>(num)

<tora>(num)

<tosca>(num)

BGS3 AT Command Set 13.2 AT+CMGC


13.2 AT+CMGC Send an SMS command

Syntax

Notes• After invoking the commands AT+CMGW, AT+CMGS or AT+CMGC it is necessary to wait for the prompt ">"

before entering text or PDU. After the prompt a timer will be started to observe the input. • At baudrates below 19200 it is recommended to use the line termination character only (refer to ATS3, default

<CR>) before entering the text or PDU. Use of the line termination character followed by the response format-ting character (refer to ATS4, default <LF> can cause problems

Test Command

AT+CMGC=?Response(s)

OK

Write Command

If text mode (see AT+CMGF=1) AT+CMGC=<fo>, <ct>[, <pid>[, <mn>[, <da>[, <toda>]]]]<CR> Text can be entered <CTRL-Z>/<ESC>Response(s)

+CMGC: <mr>[, <scts>]If sending failsERROR+CMS ERROR: <err>

Write Command

If PDU mode (see AT+CMGF=0) AT+CMGC=<length><CR> PDU can be entered <CTRL-Z>/<ESC>Response(s)

+CMGC: <mr>[, <ackpdu>]OKIf sending failsERROR+CMS ERROR: <err>


+ + + + + + - - GSM 07.05

BGS3 AT Command Set 13.3 AT+CMGD


13.3 AT+CMGD Delete short message

The write command deletes a short message from the preferred message storage <mem1> location <index>.

Syntax

Notes• If there is no short message stored at the selected index, the response is OK too. • 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 20.1, Restricted access to SIM data after SIM PIN authentication for further detail.

Test Command

AT+CMGD=?Response(s)

OK

Write Command

AT+CMGD=<index>Response(s)

OKERROR+CMS ERROR: <err>


+ + + + + + - - GSM 07.05

BGS3 AT Command Set 13.4 AT+CMGF


13.4 AT+CMGF Select SMS message format

The AT+CMGF command specifies the input and output format of the short messages.

Syntax


[0](&F) PDU mode 1 Text mode

Test Command

AT+CMGF=?Response(s)

+CMGF: (list of supported<mode>s)OK

Read Command

AT+CMGF?Response(s)

+CMGF: <mode>OKERROR+CMS ERROR: <err>

Write Command

AT+CMGF=<mode>Response(s)



- + + + + + - - GSM 07.05

<mode>(num)(&W)(&V)

BGS3 AT Command Set 13.5 AT+CMGL


13.5 AT+CMGL List SMS messages from preferred store

The write command returns messages with status value <stat> from message storage <mem1> to the TE. If thestatus of the message is 'received unread', the status in the storage changes to 'received read'.The execute command is the same as the write command with the given default for <stat>.

SyntaxTest Command

AT+CMGL=?Response(s)

+CMGL: (list of supported <stat>s)OK

Exec Command

AT+CMGLResponse(s)

+CMGL: (see write command for default of <stat>)OK

Write Command

AT+CMGL=<stat>Response(s)

Output if text mode (AT+CMGF=1) and command successful: For SMS- SUBMITs and/or SMS-DELIVERs +CMGL: <index>, <stat>, <oa>/<da>, [<alpha>], [<scts>][, <tooa>/<toda>, <length>]<data>[... ]OK

For SMS-STATUS-REPORTs +CMGL: <index>, <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st>[... ]OK

For SMS-Commands +CMGL: <index>, <stat>, <fo>, <ct>[... ]OK

Output if PDU mode AT+CMGF=0 and command successful: For SMS-SUBMITs and/or SMS-DELIVERs +CMGL: <index>, <stat>, [<alpha>], <length><pdu>[... ]OK

If error is related to ME functionalityERROR+CMS ERROR: <err>


+ + + + + + - - GSM 07.05

BGS3 AT Command Set 13.5 AT+CMGL


Notes• The selected <mem1> can contain different types of SMs (e.g. SMS-DELIVERs, SMS-SUBMITs, SMS-STA-

TUS-REPORTs and SMS-COMMANDs), the response may be a mix of the responses of different SM types.TE application can recognize the response format by examining the third response parameter.

• The parameters <ra> and <tora> will only be displayed if parameter <ra> of the AT^SSCONF command isset to 1.

• Users should be aware that when using this AT command quickly after SIM PIN authentication the SIM datamay not yet be accessible, resulting in a short delay before the requested AT command response is returned.See Section 20.1, Restricted access to SIM data after SIM PIN authentication for further detail.

BGS3 AT Command Set 13.6 AT+CMGR


13.6 AT+CMGR Read SMS messages

The write command returns SMS message with location value <index> from message storage <mem1> to theTE. If status of the message is 'received unread', status in the storage changes to 'received read'.

SyntaxTest Command

AT+CMGR=?Response(s)

OK

Write Command

AT+CMGR=<index>Response(s)

Output if text mode (AT+CMGF=1) and command successful: For SMS-DELIVER +CMGR: <stat>, <oa>, [<alpha>], <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>]<data>[... ]OK

For SMS-SUBMIT +CMGR: <stat>, <da>, [<alpha>][, <toda>, <fo>, <pid>, <dcs>, [<vp>], <sca>, <tosca>, <length>]<data>[... ]OK

For SMS-STATUS-REPORT +CMGR: <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st><data>[... ]OK

For SMS-Commands +CMGR: <stat>, <fo>, <ct>[, <pid>, [<mn>], [<da>], [<toda>], <length>]<data>[... ]OK

Output if PDU mode (AT+CMGF=0) and command successful: For SMS-SUBMITs and/or SMS-DELIVERs +CMGR: <stat>, [<alpha>], <length><pdu>[... ]OKERROR+CMS ERROR: <err>


+ + + + + + - - GSM 07.05

BGS3 AT Command Set 13.6 AT+CMGR


Notes• Response if AT+CMGR is used to read an empty record index: +CMGR: 0,,0 • Response if AT+CMGR is used to read a non-existent record index: +CMS ERROR: invalid memory index • The parameters <ra> and <tora> will only be displayed if parameter <ra> of the AT^SSCONF command is

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


BGS3 AT Command Set 13.7 AT+CMGS


13.7 AT+CMGS Send Short Message

The write command transmits a short message from TE to network (SMS-SUBMIT).After invoking the write command wait for the prompt ">" and then start to write the message. To send the mes-sage simply enter <CTRL-Z>. After the prompt a timer will be started to observe the input.To abort sending use <ESC>. Abortion is acknowledged with "OK", though the message will not be sent.The message reference <mr> is returned to the TE on successful message delivery. The value can be used toidentify the message in a delivery status report provided as an unsolicited result code.

Syntax

Notes• If sending fails, for example, if a message is too long, the result code depends on the current setting of the

AT^SM20 command:If the AT^SM20 <CmgwMode> equals 1 (factory default) any failure to send a message is responded with "OK".Users should be aware, that despite the "OK" response, the message will not be sent to the subscriber.If the AT^SM20 <CmgwMode> equals 0 any failure to send a message is responded with "ERROR".

• If sending fails due to timeout, then AT^SM20 <CmgwMode>=1 causes "+CMS ERROR: unknown error" to be returned;AT^SM20 <CmgwMode>=0 causes "+CMS ERROR: timer expired" to be returned.

• Note that some providers do not recognize an @ symbol used in a short message. A widely used alternativeis typing "*" as defined in GSM 03.40 (GPP TS 23.40).

• All characters entered behind the prompt ">" will be recognized as GSM characters. For example, "Back-space" (ASCII character 8) does not delete a character, but will be inserted into the short message as an addi-tional physical character. As a result, the character you wanted to delete still appears in the text, plus the GSMcode equivalent of the Backspace key.

Test Command

AT+CMGS=?Response(s)

OK

Write Command

If text mode (see AT+CMGF=1) AT+CMGS=<da>[, <toda>]<CR> Text can be entered. <CTRL-Z>/<ESC>Response(s)

+CMGS: <mr>[, <scts>]OKIf sending fails see notes below.

Write Command

If PDU mode (see AT+CMGF=0) AT+CMGS=<length><CR> PDU can be entered. <CTRL-Z>/<ESC>Response(s)

+CMGS: <mr>[, <ackpdu>]OKIf sending fails see notes below.


+ + + + + + - - GSM 07.05

BGS3 AT Command Set 13.7 AT+CMGS


• Message Length in Text ModeThe maximum length of a short message depends on the used coding scheme: It is 160 characters if the 7bit GSM coding scheme is used, and 140 characters according to the 8 bit GSM coding scheme.In case UCS2 character set selected it is highly recommended to set Data Coding Scheme (<dcs> ofAT+CSMP) to 16-bit data, otherwise the length of sms user data is restricted to 88 octets. Even better for mes-sages with UCS2 character set is the PDU Mode.

• At baudrates lower than 19200 it is recommended to use the line termination character only (refer to <n> ofATS3, default <CR>) before entering text or PDU. Use of the line termination character followed by theresponse formatting character (see <n> of ATS4, default <LF>) can cause problems.

• During a pending USSD user interaction the AT+CMGS write command returns "+CME ERROR: operationtemporary not allowed" to prevent blocking situations.

BGS3 AT Command Set 13.8 AT+CMGW


13.8 AT+CMGW Write Short Messages to Memory

The execute and write commands transmit a short message (either SMS-DELIVER or SMS-SUBMIT) from TEto memory storage <mem2>. Memory location <index> of the stored message is returned. Message status willbe set to 'stored unsent' unless otherwise given in parameter <stat>.After invoking the execute or write command wait for the prompt ">" and then start to write the message. To savethe message simply enter <CTRL-Z>. After the prompt a timer will be started to observe the input.To abort writing use <ESC>. Abortion is acknowledged with "OK", though the message will not be saved.

Syntax

Notes• If writing fails, for example, if a message is too long, the result code depends on the current setting of the

AT^SM20 command:If the AT^SM20 <CmgwMode>=1 (factory default) any failure to send a message is responded with "OK". Usersshould be aware, that despite the "OK" response, the message will not be written to the selected SMS stor-age.If the AT^SM20 <CmgwMode> equals 0 any failure to write a message is responded with "ERROR".

Test Command

AT+CMGW=?Response(s)

OK

Exec Command

If text mode (see AT+CMGF=1): AT+CMGWResponse(s)

<CR> Text can be entered. <CTRL-Z>/<ESC> +CMGW: <index>OKIf writing failsERROR+CMS ERROR: <err>

Write Command

If text mode (see AT+CMGF=1): AT+CMGW=<oa>/<da>[, [<tooa>/<toda>][, <stat>]]<CR> Text can be entered. <CTRL-Z>/<ESC>Response(s)

+CMGW: <index>OKIf writing fails see notes below.

Write Command

If PDU mode (see AT+CMGF=0): AT+CMGW=<length>[, <stat>]<CR> PDU can be entered. <CTRL-Z>/<ESC>Response(s)

+CMGW: <index>OKIf writing fails see notes below.


+ + + + + + - - GSM 07.05

BGS3 AT Command Set 13.8 AT+CMGW


• If writing fails due to timeout, then AT^SM20 <CmgwMode>=1 causes "+CMS ERROR: unknown error" to be returned;AT^SM20 <CmgwMode>=0 causes "+CMS ERROR: timer expired" to be returned.

• Note that some providers do not recognize an @ symbol used in a short message. A widely used alternativeis typing "*" as defined in GSM 03.40 (GPP TS 23.40).

• For baudrates lower than 19200 it is recommended to use the line termination character only (refer to ATS3=<n>, default <CR>) before entering the text or PDU. Use of the line termination character followed by theresponse formating character (see ATS4= <n>, default <LF>) may cause problems.

• SMS-COMMANDs and SMS-STATUS-REPORTs cannot be stored in text mode. • All characters entered behind the ">" prompt will be recognized as GSM characters. For example, "Back-

space" (ASCII character 8) does not delete a character, but will be inserted into the short message as an addi-tional physical character. As a result, the character you wanted to delete still appears in the text, plus the GSMcode equivalent of the Backspace key.

• Message Length in Text ModeThe maximum length of a short message depends on the used coding scheme: It is 160 characters if the 7bit GSM coding scheme is used, and 140 characters according to the 8 bit GSM coding scheme.In case UCS2 character set selected it is highly recommended to set Data Coding Scheme (<dcs> ofAT+CSMP) to 16-bit data, otherwise the length of sms user data is restricted to 88 octets. Even better for mes-sages with UCS2 character set is the PDU Mode.

• The length of 8-bit data coded short messages has to be greater than 0.

BGS3 AT Command Set 13.9 AT+CMSS


13.9 AT+CMSS Send short messages from storage

The write command sends message with location value <index> from message storage <mem2> to the network(SMS-SUBMIT or SMS-COMMAND). If new recipient address <da> is given for SMS-SUBMIT, it shall be usedinstead of the one stored with the message. Reference value <mr> is returned to the TE on successful messagedelivery. Value can be used to identify message upon unsolicited delivery status report result code.If the optional parameter <da> is given, the old status of the short message at <index> remains unchanged(see <stat>).

SyntaxTest Command

AT+CMSS=?Response(s)

OK

Write Command

If text mode (AT+CMGF=1): AT+CMSS=<index>[, <da>[, <toda>]]Response(s)

+CMSS: <mr>[, <scts>]OKIf sending failsERROR+CMS ERROR: <err>

Write Command

If PDU mode (AT+CMGF=0): AT+CMSS=<index>[, <da>[, <toda>]]Response(s)

+CMSS: <mr>[, <ackpdu>]OKIf sending failsERROR+CMS ERROR: <err>


+ + + + + + - - GSM 07.05

BGS3 AT Command Set 13.10 AT+CNMA


13.10 AT+CNMA New Message Acknowledgement to ME/TE, only phase 2+

The write / execute command confirms successful receipt of a new message (SMS-DELIVER or SMS-STATUS-REPORT) routed directly to the TE. TA shall not send another +CMT or +CDS result code to TE until previousone is acknowledged. If ME does not receive acknowledgement within required time (network time-out), MEsends RP-ERROR to the network. TA shall automatically disable routing to TE by setting both <mt> and <ds>values of AT+CNMI to zero.

Syntax


Parameter required only for PDU mode.0 Command operates similarly as in text mode.

Notes• The execute / write command shall only be used when AT+CSMS parameter <service> equals 1 (= phase

2+). • The execute command can be used no matter whether text mode or PDU mode is activated. The write com-

mand is designed for the PDU mode only. • If multiplex mode is activated (AT+CMUX=0) the AT+CNMI parameter will be set to zero on all channels, if one

channel fails to acknowledge an incoming message within the required time.

Test Command

AT+CNMA=?Response(s)

+CNMA: (list of supported <n>s)OK

Exec Command

AT+CNMAResponse(s)


Write Command

AT+CNMA=<n>Response(s)



+ + + + + + - - GSM 07.05

<n>(num)

BGS3 AT Command Set 13.11 AT+CNMI


13.11 AT+CNMI New short Message Indication

The write command selects the procedure how the receipt of new short messages from the network is indicatedto the TE when TE is active, e.g. DTR signal is ON. If TE is inactive (e.g. DTR signal is OFF), message receivingshould be done as specified in GSM 03.38. If the DTR signal is not available or the state of the signal is ignored(V.250 command AT&D0, reliable message transfer can be assured by using AT+CNMA acknowledgment proce-dure. The rules <mt>=2 and <mt>=3 for storing received messages are possible only if phase 2+ compatibilityis activated with AT+CSMS=1. The parameter <ds>=1 is only available in phase 2+

Syntax


URC 1

<mt>=1: +CMTI: <mem3>, <index>

Indicates that new message has been received

URC 2

<mt>=2 (PDU mode enabled): +CMT: <length><CR><LF><pdu>


URC 3

<mt>=2 (text mode enabled): +CMT: <oa>, <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>]<CR><LF><data>


Test Command

AT+CNMI=?Response(s)

+CNMI: (list of supported<mode>s), (list of supported <mt>s), (list of supported <bm>s), (list of supported <ds>s), (list of supported <bfr>s)OK

Read Command

AT+CNMI?Response(s)

+CNMI: <mode>, <mt>, <bm>, <ds>, <bfr>OK

Write Command

AT+CNMI=<mode>[, <mt>[, <bm>[, <ds>[, <bfr>]]]]Response(s)



+ + + + + + - - GSM 07.05



URC 4

<bm>=2 (PDU mode enabled): +CBM: <length><CR><LF><pdu>

Indicates that new cell broadcast message has been received

URC 5

<bm>=2 (text mode enabled): +CBM: <sn>, <mid>, <dcs>, <page>, <pages><CR><LF><data>

Indicates that new cell broadcast message has been received

URC 6

<ds>=1 (PDU mode enabled): +CDS: <length><CR><LF><pdu>

Indicates that new SMS status report has been received

URC 7

<ds>=1 (text mode enabled): +CDS: <fo>, <mr>[, <ra>][, <tora>], <scts>, <dt>, <st>


URC 8

<ds>=2: +CDSI: <mem3>, <index>



[0](&F) Buffer unsolicited result codes in the TA. If TA result code buffer is full, indica-tions can be buffered in some other place or the oldest indications may be dis-carded and replaced with the new received indications.

1 Discard indication and reject new received message unsolicited result codeswhen TA-TE link is reserved (e.g. in on-line data mode). Otherwise forwardthem directly to the TE.

2 Buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. inonline data mode) and flush them to the TE after reservation. Otherwise for-ward them directly to the TE.

3 Forward unsolicited result codes directly to the TE. When TA-TE link isreserved (e.g. in online data mode) the URCs are signaled according to theAT^SCFG parameters <uri>, <udri> and <urat>.

Rules for storing received short messages depend on the relevant data coding method (refer to GSM 03.38),preferred memory storage (AT+CPMS) setting and this value.Note: If AT command interface is acting as the only display device, the ME must support storage of class 0 mes-sages and messages in the message waiting indication group (discard message) [0](&F) No SMS-DELIVER indications are routed to the TE.1 If SMS-DELIVER is stored in ME/TA, indication of the memory location is

routed to the TE using unsolicited result code.

<mode>(num)(&W)

<mt>(num)(&W)(&V)



2 SMS-DELIVERs, except class 2 messages and messages in the messagewaiting indication group (store message) are routed directly to the TE usingunsolicited result code.

3 Class 3 SMS-DELIVERs are routed directly to the TE using unsolicited resultcodes defined in <mt>=2. Messages of other data coding schemes result inindication as defined in <mt>=1.

Rules for storing received CBMs depend on the relevant data coding method (refer to GSM 03.38), the settingof Select CBM Types (AT+CSCB) and this value: [0](&F) No CBM indications are routed to the TE.2 New CBMs are routed directly to the TE using unsolicited result code. 3 Class 3 CBMs are routed directly to TE using unsolicited result codes defined

in <bm>=2.

[0](&F) No SMS-STATUS-REPORTs are routed to the TE.1 SMS-STATUS-REPORTs are routed to the TE using unsolicited result code. 2 If SMS-STATUS-REPORT is routed into ME/TA, indication of the memory

location is routed to the TE using unsolicited result code.

[1](&F) TA buffer of unsolicited result codes defined within this command is clearedwhen <mode> changes from 0 to 1...3.

Integer type; value in the range of location numbers supported by the associated memory

Notes• Parameters <mt>=2,3 and <ds>=1 are only available with GSM phase 2+ (see AT+CSMS=1). Incoming SMs

or Status Reports have to be acknowledged with AT+CNMA=0 when using these phase 2+ parameters. • Requirements specific to Multiplex mode:

In multiplex mode (AT+CMUX=0) only one channel can use a phase 2+ parameter. The parameter for <mt>and <ds> on the other channels have to be set to zero. If either a SM or a Status Report is not acknowledged,all AT+CNMI parameter in all channels will be set to zero.

• If the ME operates on different instances ( MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings forrouting and indicating short messages. For example, if messages shall be routed directly to one instance ofthe TE (set with AT+CNMI, AT^SSDA), it is not possible to activate the presentation of URCs with AT+CMERor AT+CNMI on another instance. Any attempt to activate settings that conflict with existing settings onanother interface, will result in "+CME ERROR", or accordingly "+CMS ERROR".

• Handling of Class 0 short messages: If the host application is provided with a display and AT^SSDA=1 has been set Class 0 short messages canbe displayed immediately.If the host application does not include a display, ME handles Class 0 short messages as though there wasno message class, i.e. it will ignore bits 0 and 1 in the <dcs> and normal rules for exceeded memory capacityshall apply. This approach is compliant with GSM 03.38 .

• The parameters <ra> and <tora> will only be displayed if <ra> of the AT^SSCONF command is set to 1. • If either a SM or a Status Report is not acknowledged, all AT+CNMI parameter in all channels will be set to

zero.

<bm>(num)(&W)(&V)

<ds>(num)(&W)(&V)

<bfr>(num)(&V)

<index>(num)

BGS3 AT Command Set 13.12 AT+CPMS


13.12 AT+CPMS Preferred SMS message storage

The write command selects memory storages <mem1>,<mem2>, <mem3> to be used for reading, writing, etc.

Syntax


Number of messages currently in <mem1>



Number of messages storable in <mem1>



Test Command

AT+CPMS=?Response(s)

+CPMS: (list of supported <mem1>s), (list of supported <mem2>s), (list of supported <mem3>s)OK

Read Command

AT+CPMS?Response(s)

+CPMS: <mem1>, <used1>, <total1>, <mem2>, <used2>, <total2>, <mem3>, <used3>, <total3>OKERROR+CMS ERROR: <err>

Write Command

AT+CPMS=<mem1>[, <mem2>[, <mem3>]]Response(s)

+CPMS: <used1>, <total1>, <used2>, <total2>, <used3>, <total3>OKERROR+CMS ERROR: <err>


+ + + + + + - - GSM 07.05

<used1>(num)

<used2>(num)

<used3>(num)

<total1>(num)

<total2>(num)

<total3>(num)

BGS3 AT Command Set 13.12 AT+CPMS


Notes• The Mobile Equipment storage ''ME'' offers space for 25 short messages, see <mem1>. • ''MT'' is the sum of ''ME'' (= 25 locations) and ''SM'' (capacity varies with SIM card). The indices <index> of

the ''MT'' storage are dependent on the order selected with AT^SSMSS • The <mem1>, <mem2> and <mem3> parameter will be stored in non-volatile memory. • The user should be aware that the setting ''MT'' involves ''ME'' and ''SM'', with ''ME'' being filled up first. If the

''ME'' storage is full, BGS3 will proceed with the ''SM'' storage. Incoming Class 1 short messages (ME specific) will be preferably stored to ''ME'' and may be transferred tothe ''SM'' storage if ''ME'' is used up. Incoming Class 2 messages (SIM specific) will be stored to the SIM card only, no matter whether or not thereis free ''ME'' space. As a result, the ^SMGO: 2 indication (see AT^SMGO) may be presented without prior indi-cation of ^SMGO: 1. For more information regarding SIM and ME specific message classes refer to <dcs>and the following specifications: GSM 03.38 and 3GPP TS23038.

• Multiplexer: In Multiplex mode or when the two physical serial interfaces are connected, the parameter<mem3> will be the same on all instances, but the settings of <mem1> and <mem2> may vary on each channel/ interface. As a result, changes on parameter <mem1> and/or <mem2> befor activating the multiplexer or dif-ferences values for other instanes can result in not desired behaviours like different outputs for AT+CMGL andso on.

• While <mem3> equals ''SM'' and <mem1> equals ''ME'' it is possible that, after deleting short messages from''ME'', the freed space on ''ME'' is reclaimed for new incoming short messages, when there is no space left onthe ''SM'' storage. As it is often the clients concern to have received short messages stored only to the SIMcard, inconsistent settings should be generally avoided. This can be achieved simply by using the sameparameter for all memory indices.


• The indices <index> of the storage are dependent on the order selected with AT^SSMSS.

BGS3 AT Command Set 13.13 AT+CSCA


13.13 AT+CSCA SMS Service Center Address

Write command updates the SMSC address, through which mobile originated SMs are transmitted. In text mode,setting is used by send and write commands. In PDU mode, setting is used by the same commands, but onlywhen the length of the SMSC address coded into the <pdu> parameter equals zero.

Syntax

Notes• In case of using no parameter after AT+CSCA= the content of <sca> will be deleted. • This command writes the service center address to non-volatile memo. • The SMS service center address should be entered as specified by the service provider.

Test Command

AT+CSCA=?Response(s)

OK

Read Command

AT+CSCA?Response(s)

+CSCA: <sca>, <tosca>OK

Write Command

AT+CSCA=<sca>[, <tosca>]Response(s)

OK


+ + + + + + - - GSM 07.05

BGS3 AT Command Set 13.14 AT+CSCB


13.14 AT+CSCB Select Cell Broadcast Message Indication

The test command returns the supported modes as a compound value.The write command selects which types of CBMs are to be received by the ME.

Syntax


Message mode0(&F) Accept messages that are defined in <mids> and <dcss> 1 Forbid messages that are defined in <mids> and <dcss>

Cell Broadcast Message ID specification[““](&F) default value of this parameter is empty string, and it means that no CBM iden-

tifiers are specified.• For <mode>=0: Six different possible combinations of CBM IDs (e.g. "0,1,5,320-478,922,2000-3000").

In certain configurations, e.g. if using SIMs that contain data in Elementary File EF-CBMID (Cell BroadcastMessage Identifier for Data download) less than six combinations may be available. To access a SIM's Elementary File data refer to command AT+CRSM.

• For <mode>=1: One CBM ID or range of IDs (e.g. "320-478").

CBM data coding scheme specification[““](&F) default value of this parameter is empty stringAll different possible combinations of CBM data coding schemes (e.g. "0-3,5"). Using default empty string leadsto get all CBMs independent of their dcss. A given <dcss> replaces any former value and is used for consecutive requests.

Test Command

AT+CSCB=?Response(s)

+CSCB: (list of supported <mode>s)OK

Read Command

AT+CSCB?Response(s)

+CSCB: <mode>, <mids>, <dcss>OK

Write Command

AT+CSCB=<mode>[, <mids>[, <dcss>]]Response(s)

OK


+ + + + + + - - GSM 07.05

<mode>(num)

<mids>(str)

<dcss>(str)

BGS3 AT Command Set 13.15 AT+CSDH


13.15 AT+CSDH Show SMS text mode parameters

The write command sets whether or not detailed header information is shown in text mode result codes.

Syntax


[0](&F) Do not show header values defined in commands AT+CSCA and AT+CSMP(<sca>, <tosca>,<fo>,<vp>, <pid> and <dcs>) nor <length>, <toda> or<tooa> in "+CMTI", AT+CMGL, AT+CMGR result codes for SMS-DELIVERs andSMS-SUBMITs in text mode; for SMS-COMMANDs in +CMGR result code, donot show <pid>,<mn>,<da>, <toda>, <length> or <cdata>

1 Show the values in result codes

Test Command

AT+CSDH=?Response(s)

+CSDH: ((list of supported <show>s)OK

Read Command

AT+CSDH?Response(s)

+CSDH:<show>OK

Write Command

AT+CSDH=<show>Response(s)

+CSDH: <show>OK


+ + + + + + - - GSM 07.05

<show>(num)(&W)

BGS3 AT Command Set 13.16 AT+CSMP


13.16 AT+CSMP Set SMS text Mode Parameters

The write command selects values for additional parameters needed when the short message is sent to the net-work or placed in a storage when text format message mode is selected. It is possible to set the validity period starting from the time when the short message is received by the SMSC(<vp> is in range 0... 255) or define the absolute time of the validity period termination (<vp> is a string). Theformat of <vp> is given by <fo>. If TA supports the enhanced validity period format, see GSM 03.40), it shall begiven as a hexadecimal coded string (e.g. <pdu>) with quotes.

Syntax


First Octetdepending on the command or result code: first octet of GSM 03.40 SMS-DELIVER, SMS-SUBMIT (default 17),SMS-STATUS-REPORT, or SMS-COMMAND (default 2) in integer format 0...17(&F)...255

Depending on SMS-SUBMIT <fo> setting: GSM 03.40 TP-Validity-Period either in integer format or in time-string format (refer <dt>) 0...167(&F)...255

Data Coding SchemeGSM 03.38 SMS Data Coding Scheme, or Cell Broadcast Data Coding Scheme in integer format 0(&F)...247

Test Command

AT+CSMP=?Response(s)

OK

Read Command

AT+CSMP?Response(s)

+CSMP:<fo>, <vp>/ <scts>, <pid>, <dcs>OK

Write Command

AT+CSMP=<fo>[, <vp>/<scts>[, <pid>[, <dcs>]]]Response(s)

+CSMP: <index>OKIf sending failsERROR+CMS ERROR: <err>


+ + + + + + - - GSM 07.05

<fo>(num)

<vp>(num)

<dcs>(num)

BGS3 AT Command Set 13.16 AT+CSMP


Protocol IdentifierGSM 03.40 TP-Protocol-Identifier in integer format 0(&F)...255

Notes• When storing a SMS DELIVER from the TE to the preferred memory storage in text mode (using the AT+CMGW

write command), <vp> field can be used for <scts>. • The command writes the parameters to the non-volatile memory.

<pid>(num)

BGS3 AT Command Set 13.17 AT+CSMS


13.17 AT+CSMS Select Message Service

Syntax


0(&F) GSM 03.40 and GSM 03.41 (the syntax of SMS AT commands is compatiblewith GSM 07.05 Phase 2 version 4.7.0; Phase 2+ features which do not requirenew command syntax may be supported, e.g. correct routing of messages withnew Phase 2+ data coding schemes)

1 GSM 03.40 and GSM 03.41 (the syntax of SMS AT commands is compatiblewith GSM 07.05 Phase 2+ version; the requirement of <service> setting 1 ismentioned under corresponding command descriptions).

Mobile Terminated Messages:0 Type not supported 1 Type supported

Mobile Originated Messages:0 Type not supported 1 Type supported

Test Command

AT+CSMS=?Response(s)

+CSMS: (list of supported<service>s)OK

Read Command

AT+CSMS?Response(s)

+CSMS: <service>, <mt>, <mo>, <bm>OK

Write Command

AT+CSMS=<service>Response(s)

+CSMS: <mt>, <mo>, <bm>OKERROR+CMS ERROR: <err>


+ + + + + + - - GSM 07.05

<service>(num)(&W)(&V)

<mt>(num)

<mo>(num)

BGS3 AT Command Set 13.17 AT+CSMS


Broadcast Type Messages:0 Type not supported 1 Type supported

Notes• If CSMS mode is switched from Phase 2+ to Phase 2 and one or more AT+CNMI Parameter are Phase 2+

specific a "+CMS ERROR: unknown error" will appear. It is recommended to switch the AT+CNMI Parametersto Phase 2 specific values before entering Phase 2.

• Phase 2+ (<service>=1) must be set before the following features can be used: - Configuring procedures for indicating received short messages with the AT+CNMI parameters <mt>=2 or<mt>=3 and <ds>=1. - Acknowledging incoming short messages with AT+CNMA. - Receiving Status Reports and acknowledging them with AT+CNMA.

<bm>(num)

BGS3 AT Command Set 13.18 AT^SCML


13.18 AT^SCML List Concatenated Short Messages from preferred store

The write command returns messages with status value <stat> from message storage <mem1> to the TE. If thestatus of the message is 'received unread', the status in the storage changes to 'received read'. The executecommand is the same as the write command with the given default for <stat>. See notes of AT+CMGL.

SyntaxTest Command

AT^SCML=?Response(s)

^SCML: (list of supported <stat>s)OK

Exec Command

AT^SCMLResponse(s)

^SCML: (see write command for default of <stat>)OK

Write Command

AT^SCML=<stat>Response(s)

Output if text mode (AT+CMGF=1) and command successful: For SMS-SUBMITs and/or SMS-DELIVERs ^SCML: <index>, <stat>, <oa>/<da>, [<alpha>], [<scts>][, <tooa>/<toda>, <length>][, <seq>, <max>, <ieia>, <ref>]<data>[... ]OK

For SMS-STATUS-REPORTs ^SCML: <index>, <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st>[... ]OK

For SMS-Commands ^SCML: <index>, <stat>, <fo>, <ct>[... ]OK

Output if PDU mode (AT+CMGF=0) and command successful: For SMS- SUBMITs and/or SMS-DELIVERs ^SCML: <index>, <stat>, [<alpha>], <length><pdu>[... ]OK

If error is related to ME functionalityERROR+CMS ERROR: <err>


+ + + + + + - -

BGS3 AT Command Set 13.19 AT^SCMR


13.19 AT^SCMR Read Concatenated Short Messages

The write command returns the message with location value <index> from message storage <mem1> to the TE.If the status of the message is 'received unread', the status in the storage changes to 'received read'. See notesof AT+CMGR.

SyntaxTest Command

AT^SCMR=?Response(s)

OK

Write Command

AT^SCMR=<index>Response(s)

Output if text mode (AT+CMGF=1) and command successful: For SMS-DELIVER ^SCMR: <stat>, <oa>, [<alpha>], <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>, <length>][, <seq>, <max>, <ieia>, <ref>]<data>[... ]OK

For SMS-SUBMIT ^SCMR: <stat>, <da>, [<alpha>][, <toda>, <fo>, <pid>, <dcs>, [<vp>], <sca>, <tosca>, <length>][, <seq>, <max>, <ieia>, <ref>]<data>[... ]OK

For SMS-STATUS-REPORT ^SCMR: <stat>, <fo>, <mr>, [<ra>], [<tora>], <scts>, <dt>, <st><data>[... ]OK

For SMS-Commands ^SCMR: <stat>, <fo>, <ct>[, <pid>, [<mn>], [<da>], [<toda>], <length>]<data>[... ]OK

Output if PDU mode (AT+CMGF=0) and command successful: For SMS-SUBMITs and/or SMS-DELIVERs ^SCMR: <stat>, [<alpha>], <length><pdu>[... ]OK

ERROR+CMS ERROR: <err>


+ + + + + + - -

BGS3 AT Command Set 13.20 AT^SCMS


13.20 AT^SCMS Send Concatenated Short Messages

Sending a concatenated message is similar to sending a "normal" message, except that each segment of theconcatenated message must be identified by the additional parameters <seq>, <ieia> and <ref>. To send allsegments of the message one by one, the AT^SCMS write command must be executed for each segment. The write command transmits one segment of a concatenated short message from TE to network (SMS-SUB-MIT).After invoking the write command wait for the prompt ">" and then start to write the message. To send the mes-sage simply enter <CTRL-Z>. After the prompt a timer will be started to observe the input.To abort sending use <ESC>. Abortion is acknowledged with "OK", though the message will not be sent.The message reference <mr> is returned to the TE on successful message delivery. The value can be used toidentify the message in a delivery status report provided as an unsolicited result code.

Syntax

Notes• See notes provided for AT+CMGS. • Command is only available if AT+CMGF=1.

Test Command

AT^SCMS=?Response(s)

OK

Write Command

Command syntax for text mode (see AT+CMGF=1): AT^SCMS=<da>[, <toda>], <seq>, <max>, <ieia>, <ref><CR> Text can be entered <CTRL-Z>/<ESC>Response(s)

^SCMS: <mr>[, <scts>]OKIf sending failsERROR+CMS ERROR: <err>


+ + + + + + - -

BGS3 AT Command Set 13.21 AT^SCMW


13.21 AT^SCMW Write Concatenated Short Messages to Memory

Writing a concatenated message to the memory is similar to writing a "normal" message, except that each seg-ment of the concatenated message must be identified by the additional parameters <seq>, <ieia> and <ref>.To store all segments of the message one by one, the AT^SCMW write command must be executed for each seg-ment.The write commands transmits one segment of a concatenated SMS (either SMS-DELIVER or SMS-SUBMIT)from TE to memory storage <mem2>. Memory location <index> of the stored message is returned. Messagestatus will be set to 'stored unsent' unless otherwise given in parameter <stat>.

Syntax

Notes• Command is only available if AT+CMGF=1. • To send or delete a concatenated short message please use the known SMS commands, see AT+CMSS for

sending and AT+CMGD for deleting. • See notes provided for AT+CMGW.

Test Command

AT^SCMW=?Response(s)

OK

Write Command

If text mode (see AT+CMGF=1) AT^SCMW=<oa>/<da>, [<tooa>/<toda>][, <stat>], <seq>, <max>, <ieia>, <ref><CR> Text can be entered. <CTRL-Z>/<ESC>Response(s)

^SCMW: <index>OKIf writing failsERROR+CMS ERROR: <err>


+ + + + + + - -

BGS3 AT Command Set 13.22 AT^SLMS


13.22 AT^SLMS List SMS Memory Storage

AT^SLMS indicates the max. capacity of each SMS storage type and the number of locations currently used.

Syntax


Maximum number of messages storable in the SMS memory of the SIM (physical storage "SM")

Maximum number of messages storable in the SMS memory of the Mobile Equipment (physical storage "ME")

Sum of "SM" and "ME", indicated as "MT". Maximum number of all messages storable in the SIM memory andthe Mobile Equipment memory.

Number of messages currently stored in the SMS memory of the SIM (physical storage "SM")

Number of messages currently stored in the SMS memory of the Mobile Equipment (physical storage "ME")

Concatenated logical SMS storages of SIM ("SM") and Mobile Equipment ("ME"). Sum of all messages currentlystored, indicated as "MT".

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


Test Command

AT^SLMS=?Response(s)

OK

Exec Command

AT^SLMSResponse(s)

^SLMS: ''MT'',<total3>, <used3>^SLMS: ''SM'',<total1>, <used1>^SLMS: ''ME'',<total2>, <used2>OKERROR+CMS ERROR: <err>


+ + + + + + - -

<total1>(num)

<total2>(num)

<total3>(num)

<used1>(num)

<used2>(num)

<used3>(num)

BGS3 AT Command Set 13.23 AT^SMGL


13.23 AT^SMGL List Short Messages from preferred store without set-ting status to REC READ

The write command allows to select a status type and lists, from the message storage <mem1>, all messagesthat currently have the specified <stat>. The major difference over the standard command AT+CMGL is that thestatus of the listed messages remains u n c h a n g e d (unread remains unread).The execute command is the same as the write command, but uses the given default of <stat>.

Syntax

Notes• The selected <mem1> can contain different types of SMs (e.g. SMS-DELIVERs, SMS-SUBMITs, SMS-STA-

TUS-REPORTs and SMS-COMMANDs), the response may be a mix of the responses of different SM types.TE application can recognize the response format by examining the third response parameter.


Test Command

AT^SMGL=?Response(s)

same as AT+CMGL

Exec Command

AT^SMGLResponse(s)

^SMGL: (For default values of <stat>, see "Section 13.1, SMS parameters.)OK

Write Command

AT^SMGL=<stat>Response(s)

same as AT+CMGL


+ + + + + + - -

BGS3 AT Command Set 13.24 AT^SMGO


13.24 AT^SMGO Set or query SMS overflow presentation mode or query SMS overflow

The write command sets the overflow presentation mode.The read command returns the overflow presentation mode and the SMS overflow status.

Syntax

Unsolicited Result CodeSMS buffer change: ^SMGO: <mode>

Status of SMS buffer has changed.


SMS overflow presentation mode[0](&F) Disable 1 Enable

SMS overflow status0 Space available1 SMS buffer full (The buffer for received short messages is <mem3>. See

AT+CPMS.)2 Buffer full and new message waiting in SC for delivery to phone

Test Command

AT^SMGO=?Response(s)

^SMGO: (list of supported<n>s)OK

Read Command

AT^SMGO?Response(s)

^SMGO: <n>, <mode>OKERROR+CMS ERROR: <err>

Write Command

AT^SMGO=<n>Response(s)



+ + + + + + - -

<n>(num)(&W)(&V)

<mode>(num)(&V)

BGS3 AT Command Set 13.24 AT^SMGO


Notes• Incoming short messages with message class 1 (ME specific short messages) or class 2 (SIM specific short

messages), see <dcs> in GSM 03.38, will be stored either in ''ME'' or in ''SM'' storage. Therefore the "^SMGO:2" indication could occur, without issuing the indication "^SMGO: 1" before. The indication "^SMGO: 1" meansthat both buffers (''ME'' and ''SM'') are full.

• For more information regarding SIM and ME specific message classes refer to <dcs> and the following spec-ifications: GSM 03.38 and 3GPP TS 23.038 .

BGS3 AT Command Set 13.25 AT^SMGR


13.25 AT^SMGR Read short message without setting status to REC READ

The AT^SMGR command is a proprietary command which has the same syntax as AT+CMGR. The only functionaldifference is that the status "REC UNREAD" of a short message is not overwritten to "REC READ".

Syntax



Test Command

AT^SMGR=?Response(s)

^SMGR: OK

Write Command

AT^SMGR=<index>Response(s)

see AT+CMGR


+ + + + + + - -

BGS3 AT Command Set 13.26 AT^SSCONF


13.26 AT^SSCONF SMS Command Configuration

AT^SSCONF controls details of some SMS releated commands. Please note that AT^SSCONF settings are storedvolatile, i.e. after restart or reset the default values will be restored.

Syntax


Display recipient address[0](&F) BGS3 does not display <ra> and <tora>. These parameters are used with

the result codes of AT+CMGL, AT^SMGL, AT+CMGR, AT^SMGR and the URC"+CDS".

1 BGS3 displays <ra> and <tora>.

Test Command

AT^SSCONF=?Response(s)

^SSCONF:list of supported <ra>s OK

Read Command

AT^SSCONF?Response(s)

^SSCONF:<ra>OK

Write Command

AT^SSCONF=<ra>Response(s)

OK


- + + + + + - -

<ra>(num)

BGS3 AT Command Set 13.27 AT^SSDA


13.27 AT^SSDA Set SMS Display Availability

This command allows to notify the BGS3 of its controlling application's capability to immediately display incomingSMS on a display. If the application is able to display incoming short messages, a class 0 message shall be displayed immediately.However, if it does not, class 0 messages shall be treated as if no message class is determined (GSM 03.38[17]). The effect of this command if <da>=1 is to determine the behavior of parameter <mt> of AT+CNMI: If multiplex mode is enabled (AT+CMUX) and <da>=1 with <mt>=1 is set on any logical channel, all other chan-nels have to use <mt>=0.

Syntax


Display Availability0(&F) Application is not able to display incoming short message1 Application is able to display incoming short message

Note• If the ME operates on different instances (MUX channels 1, 2, 3 or ASC0/ASC1) avoid different settings for

routing and indicating short messages. For example, if messages shall be routed directly to one instance ofthe TE (set with AT+CNMI, AT^SSDA), it is not possible to activate the presentation of URCs with AT+CMERor AT+CNMI on another instance. Any attempt to activate settings that conflict with existing settings onanother interface, will result in "+CME ERROR", or accordingly "+CMS ERROR".

Test Command

AT^SSDA=?Response(s)

^SSDA:list of supported <da>s OK

Read Command

AT^SSDA?Response(s)

^SSDA:<da>OK

Write Command

AT^SSDA=<da>Response(s)

OK


- + + + + + - -

<da>(num)

BGS3 AT Command Set 13.28 AT^SSMSS


13.28 AT^SSMSS Set Short Message Storage Sequence

The short message storage ''MT'' (see AT+CPMS) is a logical storage. It consists of two physical storages ''ME''and ''SM''. This command allows to select the sequence of addressing this storage.

Syntax


MT sequence 0(&F) ''MT'' storage is ''ME'' then ''SM1 ''MT'' storage is ''SM'' then ''ME''

Note• The <seq> parameter will be stored in non-volatile memory.

Test Command

AT^SSMSS=?Response(s)

^SSMSS: (list of supported) <seq>s

Read Command

AT^SSMSS?Response(s)

^SSMSS: <seq>OK

Write Command

AT^SSMSS=<seq>Response(s)

OK


+ + + + + + - -

<seq>(num)

BGS3 AT Command Set 14. SIM related Commands


14. SIM related Commands

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

Note:If using data from the SIM please bear in mind that the content of all Elementary Files is subject to change at anymoment!This is 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, [22]. To get informed that changing Elementary Files has taken place the TA needs to hook to the SAT Proactive Com-mand "REFRESH". For more information please refer to Chapter 15., SIM Application Toolkit (SAT) Commandsand AT^SSTGI in particular.

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 thecommands 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 [21]. BGS3 handles internally all required SIMinterface locking and file selection routines. As response to the command, the BGS3 sends the actual SIM information parameters and response data. Errorresult code "+CME ERROR" may be returned if the command cannot be passed to the SIM, e.g. if the SIM is notinserted. 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> "READRECORD" 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:

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

Syntax

EF Symbol EF Name EF ID (hex.) EF ID (dec.)EFICCID ICC identification 2FE2 12258EFELP Extended language pref-

erence2F05 12037

EFLP Language preference 6F05 28421EFSPN Service provider name 6F46 28486EFAD Administrative data 6FAD 28589EFPhase Phase identification 6FAE 28590EFECC Emergency call codes 6FB7 28599

Test Command

AT+CRSM=?Response(s)

OK

BGS3 AT Command Set 14.1 AT+CRSM



SIM command number.176 READ BINARY178 READ RECORD192 GET RESPONSE214 UPDATE BINARY220 UPDATE RECORD242 STATUS

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

Parameter to be passed on by the BGS3 to the SIM. 0...255



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

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

Write Command

AT+CRSM=<command>[, <fileID>[, <P1>, <P2>, <P3>[, <data>]]]Response(s)

+CRSM: <sw1>,<sw2>[,<response>] OK ERROR +CME ERROR: <err>


± + + + + + - - GSM 07.07

<command>(num)

<fileID>(num)

<P1>(num)

<P2>(num)

<P3>(num)

<data>(str)

<sw1>(num)

BGS3 AT Command Set 14.1 AT+CRSM



Response data in case of a successful completion of the previously issued command. "STATUS" and "GET RESPONSE" commands return data, which gives information about the currently selectedelementary data field. This information includes the type of file and its size. After "READ BINARY" or "READ RECORD" commands the requested data will be returned. <response> is empty after "UPDATE BINARY" or "UPDATE RECORD" commands.

<sw2>(num)

<response>(str)

BGS3 AT Command Set 14.2 AT^SATR


14.2 AT^SATR Query SIM's Answer to Reset Data

AT^SATR queries the Answer to Reset (ATR) data of the current SIM ISO/IEC 7816-3. The response to the exe-cute command is a data string of max. 33 bytes sent from the SIM card to the module, containing informationabout the SIM and the used data transmission protocols. For ATR coding please refer to GSM 11.11 [21].

Syntax


Answer to Reset (ATR) data of current SIM.

Test Command

AT^SATR=?Response(s)

OK

Exec Command

AT^SATRResponse(s)

^SATR: <response>OKERROR+CME ERROR: <err>


- + + + + + - -

<response>(str)

BGS3 AT Command Set 14.3 AT^SXSM


14.3 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 [21]. BGS3 handles internally all required SIMinterface locking and file selection routines. BGS3 may return error result code "+CME ERROR" if the command cannot be passed to the SIM, e.g. if no SIMis inserted. However, errors related to SIM action are reported in <sw1> and <sw2> parameters as defined inGSM 11.11 [21].

Syntax


136 RUN GSM ALGORITHM Start the authentication mechanism and cipher key generation on the SIM. Itruns the algorithms A3 and A8 using a 16 byte random number and the sub-scriber authentication key Ki, which is stored in the SIM.

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

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



If <command>=136 (RUN GSM ALGORITHM): 16 byte random number.

Test Command

AT^SXSM=?Response(s)

OK

Write Command

AT^SXSM=<command>[, <fileID>[, <P1>, <P2>, <P3>[, <data>]]]Response(s)

^SXSM: <sw1>, <sw2>[,<response>] OK ERROR +CME ERROR: <err>


+ + + + + + - -

<command>(num)

<fileID>(num)

<P1>(num)

<P2>(num)

<P3>(num)

<data>(str)

BGS3 AT Command Set 14.3 AT^SXSM




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

If <command>=136 (RUN GSM ALGORITHM): BGS3 returns SRES and cipher key Kc as calculated by the SIM.

Example

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

<sw1>(num)

<sw2>(num)

<response>(str)

Byte(s) Description Length1 - 4 SRES - Signed RESponse 4 5 - 12 Kc - Cipher Key 8

at^sxsm=136,,0,0,16,"00112233445566778899AABBCCDDEEFF"

Start SIM command "RUN GSM ALGORITHM" with 16 byte randomnumber.

^SXSM: 144,0,00112233445566778899AABB

SRES (bytes 1-4) and Cypher Key Kc (bytes 5-12) values as returnedby the SIM.

OK

BGS3 AT Command Set 14.4 AT^SCKS


14.4 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 andthe card holder tray of the BGS3.

Syntax

Unsolicited Result Code^SCKS: <SimStatus>

If the SIM connection status has changed an unsolicited result code (URC) is issued.


0(&F) Suppress unsolicited result codes1 Output unsolicited result codes

0 Card holder tray removed or SIM connection error 1 SIM inserted (refer to note)2 The SIM interface hardware has been deactivated to prevent possible damage

(e.g. if a SIM with invalid or unsupported electrical specifications has beendetected).The SIM interface can be reactivated by inserting a valid SIM or by restartingthe module, e.g. with "AT+CFUN= n,1".

Test Command

AT^SCKS=?Response(s)

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

Read Command

AT^SCKS?Response(s)

^SCKS: <mode>, <SimStatus>OKERROR+CME ERROR: <err>

Write Command

AT^SCKS=<mode>Response(s)



- + + + + + - -

<mode>(num)(&W)(&V)

<SimStatus>(num)(&V)

BGS3 AT Command Set 14.4 AT^SCKS


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

tray is inserted, two URCs will be presented, indicating the status 1 followed by 0. See example.

Example

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

AT^SCKS=1 Activates the presentation of unsolicited result codesOK

^SCKS: 1 Tray connected^SCKS: 0 No SIM card found

BGS3 AT Command Set 14.5 AT^SCID


14.5 AT^SCID Display SIM card identification number

Syntax

Command DescriptionTA returns the card identification number in SIM (SIM file EFICCID, see GSM 11.11 Chap.10.1.1) as string type.


card identification number of SIM card

Test Command

AT^SCID=?Response(s)

OK

Exec Command

AT^SCIDResponse(s)

^SCID: <cid>OKERROR+CME ERROR: <err>


- + + + + + - -

<cid>(str)

BGS3 AT Command Set 14.6 AT+CXXCID


14.6 AT+CXXCID Display card ID

Syntax

Command DescriptionTA returns the card identification number in SIM (SIM file EF ICCID, see GSM 11.11 Chap.10.1.1) as string type.

Note• See also: AT^SCID.

Test Command

AT+CXXCID=?Response(s)

OK

Exec Command

AT+CXXCIDResponse(s)

+CXXCID: <cid>OKERROR+CME ERROR: <err>


- + + + + + - -

BGS3 AT Command Set 15. SIM Application Toolkit (SAT) Commands


15. SIM Application Toolkit (SAT) Commands

This chapter describes AT commands and responses related to the BGS3's SIM Application Toolkit (SAT) imple-mentation.

3GPP document GSM 11.14 [22] specifies SAT in detail.

SIM Application Toolkit (SAT) is a technology that allows an application running on the SIM to control the MobileEquipment (ME). Remote-SAT (RSAT) provides a link between applications located on the SIM and a customerapplication (TA). The purpose of Remote-SAT is to allow the TA to send AT commands to the SAT interface andto display all SAT activities on the user interface of the customer application. The overall scenario is illustratedin the context diagram below.

Two groups of commands are exchanged between the SAT located on the BGS3 and the SIM Application run-ning on the SIM: • Proactive commands are sent from the SIM application to the BGS3's SAT, such as "DISPLAY TEXT". • Envelope commands are sent from the BGS3's SAT to the SIM application, such as "MENU SELECTION".

BGS3 AT Command Set


Figure 15.1: Remote-SAT Context diagram

BGS3 AT Command Set 15.1 Usage of Remote-SAT


15.1 Usage of Remote-SAT

If SAT functionality is delivered by the SIM provider, the related SAT commands have to be handled. Otherwiseother SIM functionality may not working correctly (e.g. SMS-PP downloads).Therefore two possible modes are available.

15.1.1 Automatic Response Mode (AR Mode)

If the ME operates in this (default) mode, usage of any Remote-Sat AT commands is not necessary. In this case,all commands and responses are exchanged automatically between the ME and the SIM application. The typeof Terminal Response (TR) to a SAT Proactive Command issued by the SIM application used in AR mode islisted at 1.1.7 Remote-SAT Command Type Table, column "Auto Terminal Response".To take full advantage of Remote-SAT the ER mode has to be enabled using AT^SSTA=1. This setting is storednon-volatile and takes effect after next switch-on of the ME.

15.1.2 Explicit Response Mode (ER Mode)

As a Wireless Modem does not have an MMI, Remote-SAT differs from a phone implementation of SAT. It usesa special set of AT commands to pass data, e.g. a list of menu items, to the TA and to receive responses, e.g. aselected menu item.The TA is required to monitor the status of an ongoing SAT Proactive Command (PAC) and, if required, sendsappropriate AT commands, depending upon users input.

15.1.3 Character Sets

Strings are passed as UCS2 characters, but using the GSM alphabet is also possible. Use of GSM alphabet isnot recommended since a SIM can contain text which might be not displayable, e.g. greek characters. UseAT^SSTA command to select the type of alphabet both for input and output. UCS is specified in ISO/IEC 10646.There are 2 and 4 octet versions available, of which only the 2-octet variant is used, known as UCS2. The 65536positions in the 2-octet form of UCS are divided into 256 rows, each with 256 cells. The first octet of a characterrepresentation gives the row number, the second the cell number. The first row, row 0, contains exactly the samecharacters as ISO/IEC 8859-1. The first 128 characters are thus the ASCII characters. The octet representingan ISO/IEC 8859-1 character is easily transformed to the representation in UCS by putting a 0 octet in front of it.UCS includes the same control characters as ISO/IEC 8859 which are located in row 0.

15.1.4 SIM Update Initiated by the Network

If a terminal adapter (TA) uses data of the SIM card please consider that the contents of all elementary files aresubject to change at any time. This happens because the network can change the SIM card data in the back-ground via the SIM Application Toolkit (SAT) procedure "Data download to SIM". For a detailed description referto GSM 11.14. In order to receive the information that an elementary file has been changed the TA has to activateRemote SAT and needs to look for the SAT Proactive Command "REFRESH", see chapter 1.4.2.

15.1.5 Icon Handling

Several SAT Proactive commands may provide an icon identifier. Icons are intended to enhance the MMI by pro-viding graphical information to the user. The display of icons is optional for the ME.The SIM indicates to the ME whether the icon replaces an alpha identifier or text string, or whether it accompa-nies it (icon qualifier).

BGS3 AT Command Set 15.1 Usage of Remote-SAT


If both an alpha identifier or text string, and an icon are provided with a proactive command, and both arerequested to be displayed, but the ME is not able to display both together on the screen, then the alpha identifieror text string takes precedence over the icon.

If the SIM provides an icon identifier with a proactive command, then the ME shall inform the SIM if the icon couldnot be displayed by sending the response "Command performed successfully, but requested icon could not bedisplayed" (via AT^SSTR).

The icon data can be fetched directly from the SIM via command AT+CRSM, for details please refer to GSM11.11, Annex G. The icon data can be read from the SIM on system start then cached.

15.1.6 Using SMS Related AT Commands

ME activities triggered by SAT often end up with sending or receiving short messages. Usually, a short messagecontaining a service request, is sent to the network provider, for example a request to send the latest news. Theprovider then returns a short message with the requested information.

The short message needs to read by the application running on the TA. This is done by means of the standardAT commands described in [1]. Set SMS text modeAT+CMGF=1

Activate the display of a URC on every received SMSAT+CNMI=1,1

If needed activate extended SMS text mode parameter outputAT+CSDH=1This is useful in order to obtain more detailed header information along with the incoming SMS (e.g. SMS class).Please refer to 3GPP standard GSM 03.38 for details.As a result, a URC will be output each time a short message is received+CMTI: "MT", 1 where• the first parameter "MT" specifies the storage type of the SMS• the second parameter contains a unique location number.In the given example, the short message was stored to the memory type "MT" at location number 1.The short message storage "MT" is a logical storage. It is the sum of the two physical storages "ME" (MobileEquipment message storage) and "SM" (SIM message storage). For more detailed information please refer to[1], particularly AT+CPMS and AT^SSMSS.

To read the SMS data useAT+CMGR=<location>where <location> is the location number of the received SMS, e.g. 1 in the example above.

To list all stored short messages useAT+CMGL="ALL"

To delete a certain SMS after reading useAT+CMGD=<location>

BGS3 AT Command Set 15.2 Remote-SAT States


15.2 Remote-SAT States

In order to communicate with the SIM Application Toolkit it is necessary to use AT commands which areexplained in detail in the following chapters. In general, the type of AT command which should be issued dependson the current state of the Remote-SAT interface. The current state of Remote-SAT is determined by

1. the Remote-SAT operating mode (AR or ER mode), 2. the application running on the SIM, 3. the application running on the TA (in case of ER mode only), and 4. internal actions of the ME (especially SAT and Call Control).



15.2.1 Remote-SAT State Transition Diagram

Figure 15.2: Remote-SAT State Transition Diagram



15.2.2 Remote-SAT State Transition Table

The following table outlines which AT commands can be issued during certain states. However, the test and readAT commands are available at any time. This way it is possible to determine the current state of the interface viaAT^SSTA?.

Meaning of options usable in column "M/O/X" of the following tables:M: The TA has to issue the AT command to get Remote-SAT service (mandatory).O: Usage of AT command is optional.X: Usage of AT command is not allowed or not useful at this time and may cause an error message.

Table 15.1: State: RESET description

Table 15.2: State: OFF description

Table 15.3: State: IDLE description

RESET: State after power on the ME. AT command M/O/X Description^SSTA=0,n O Enable AR Mode (with alphabet

type <n>)^SSTA=1,n O Enable ER Mode (with alphabet

type <n>)^SSTGI=<pac> X^SSTR=<pac> X^SSTR=<event> X

OFF: ME is in Auto Response Mode. AT command M/O/X Description^SSTA=0,n O Enable AR Mode (with alphabet


type <n>)^SSTGI=<pac> X^SSTR=<pac> X^SSTR=<event> X

IDLE: ME is in Explicit Response Mode. AT command M/O/X Description^SSTA=0,n O Enable AR Mode (with alphabet


type <n>)^SSTGI=<pac> O Show PAC information^SSTR=<pac> X^SSTR=<event> O



Table 15.4: State: PAC description

Table 15.5: State: WAIT description

1) To limit the time Remote-SAT is kept in states PAC or WAIT, any ongoing (but unanswered) PAC will beaborted after 5 minutes automatically.

PAC1: SIM application has issued a proactive command.This event is signalled to the TA via ^SSTN: <cmdType>. AT command M/O/X Description^SSTA=0,n O Enable AR Mode (with alphabet


type <n>)^SSTGI=<pac> M Show PAC information^SSTR=<pac> X^SSTR=<event> X

WAIT1: SIM application is waiting for theresponse to the ongoing proactive command.AT command M/O/X Description^SSTA=0,n O Enable AR Mode (with alphabet


type <n>)^SSTGI=<pac> O Show PAC information^SSTR=<pac> M^SSTR=<event> X

BGS3 AT Command Set 15.3 Remote-SAT Command Types


15.3 Remote-SAT Command Types

The Command Type value (cmdType) identifies the type of command or associated response passed betweenthe TA and the ME.

cmdType is the parameter that comes first in AT commands, in responses to AT^SSTGI and AT^SSTR com-mands, and in the "^SSTN" URC. Also, the cmdType values may be used as Next Action Indicator for the SETUPMENU and for SELECT ITEM.

The SAT implementation supports SAT class 3 (GSM 11.14 Release 99, letter class "c"). Therefore, Table 15.6summarizes only those command types and parameters which may appear on the user interface (UI) and thus,allow the user to take an action. Command types that are transparent to the user are not listed in the table,although they are supported by Remote-SAT as specified in GSM 11.14.

Table 15.6: Command Type Table

Command types supported by Remote-SAT; i.e. UI relatedcmdType value (dec.)

SSTGI applicable

Used as Next Action Indicator as speci-fied in GSM 11.14

SSTR required

Auto Ter-minal Response

Timeout Terminal Response

Command Name

Proactive commands (TA <- ME <- SIM), follows GSM 11.14 (version 8.5.0 2000-12) Section 13.41 X X 0 32 REFRESH5 X X 0 32 SET UP EVENT LIST16 X X X 48 32 SET UP CALL17 X X X 48 32 SEND SS18 X X X 48 32 SEND USSD19 X X X 48 32 SEND SHORT MESSAGE20 X X 48 32 SEND DTMF21 X X 48 32 LAUNCH BROWSER32 X X X 48 32 PLAY TONE33 X X X 0 18 DISPLAY TEXT34 X X X 48 18 GET INKEY35 X X X 48 18 GET INPUT36 X X X 48 18 SELECT ITEM37 X X X 0 0 SET UP MENU40 X X X 0 32 SET UP IDLE MODE TEXT53 X X 0 32 LANGUAGE NOTIFICATIONTermination of proactive commands (URCs, TA <- ME <- SIM)101 Terminate REFRESH105 Terminate SET UP EVENT

LIST116 Terminate SET UP CALL117 Terminate SEND SS118 Terminate SEND USSD119 Terminate SEND SHORT

MESSAGE120 Terminate SEND DTMF

BGS3 AT Command Set 15.3 Remote-SAT Command Types


121 Terminate LAUNCH BROWSER

132 Terminate PLAY TONE133 Terminate DISPLAY TEXT134 Terminate GET INKEY135 Terminate GET INPUT136 Terminate SELECT ITEM137 Terminate SET UP MENU140 Terminate SET UP IDLE

MODE TEXT153 Terminate LANGUAGE

NOTIFICATIONEvent commands (TA -<ME -<SIM)211 X User Menu Item Selection232 X User activity233 X Idle screen available235 X Language selection236 X Browser TerminationAdditional commands (URCs, TA <- ME <- SIM)254 X X Notification: SIM Application

returns to main menu <CR>Response: Terminate Command

255 Notification: REFRESH "SIM RESET"

Command types supported by Remote-SAT; i.e. UI relatedcmdType value (dec.)

SSTGI applicable

Used as Next Action Indicator as speci-fied in GSM 11.14

SSTR required

Auto Ter-minal Response

Timeout Terminal Response

Command Name

BGS3 AT Command Set 15.4 AT^SSTA


15.4 AT^SSTA Remote-SAT Interface Activation

AT^SSTA write command can be used to determine the Remote-SAT activation mode <mode> and, if ExplicitResponse mode is enabled, to activate the Remote-SAT interface. Removing and inserting the SIM does notaffect the activation status. SAT commands which are not using the AT interface (non MMI related SAT commands, e.g. PROVIDE LOCALINFORMATION) are executed without activating Remote-SAT. The read command can be used to request the current operating status and the used alphabet of the Remote-SAT interface.

Syntax


BGS3 Remote-SAT interface states 0 RESET 1 OFF 2 IDLE 3 PAC 4 WAIT

Parameter is stored non-volatile and takes effect after next restart of the ME. 0(D) GSM character set

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

To display the 16 bit value of characters represented in UCS2 alphabet a 4 bytestring is required, e.g. "0059" is coding the character "Y". For details pleaserefer to ISO/IEC 10646.

Test Command

AT^SSTA=?Response(s)

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

Read Command

AT^SSTA?Response(s)

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

Write Command

AT^SSTA=<mode>[, <Alphabet>]Response(s)

OK


- + + + + + - -

<state>(num)

<Alphabet>(num)

BGS3 AT Command Set 15.4 AT^SSTA


Remote-SAT handling (i.e. ^SSTN, AT^SSTGI and AT^SSTR sequence) is only usable via the serial channnelon which the Explicit Response (ER) mode was activated. To change the serial channel execute AT^SSTA=1 on the desired channel and perform a restart. 0 SAT is already used on another instance (logical channel in case of the multi-

plex protocol). Only test and read commands can be used. 1 SAT may be started on this instance via the write version of this command.

SAT profile according to GSM 11.14 [22].The profile tells the SIM Application which features (e.g. Proactive Commands) are supported by the SIM Appli-cation Toolkit implementation of the BGS3.

Select Remote-SAT activation mode.Parameter is stored non-volatile and takes effect after next restart of the ME. Removing and inserting the SIMdoes not affect the activation status. 0(D) Automatic Response (AR) mode.

All commands and responses are exchanged automatically between the MEand the SIM application. This eliminates the need to enter any Remote-SATcommands including the AT^SSTA command.If AR mode is enabled the ME enters the OFF state (<state>=1) after restart.

1 Explicit Response (ER) mode.This mode is intended for use with an MMI. If ER mode is enabled the MMI isrequired to handle, via BGS3's Remote-SAT interface, all commands andresponses transmitted to or from the SIM or USIM. If ER mode is enabled the ME enters the IDLE state (<state>=2) after reboot.

<allowedInstance>(num)

<SatProfile>(str)

<mode>(num)

BGS3 AT Command Set 15.5 ^SSTN


15.5 ^SSTN SAT Notification


URC 1

Proactive command notification ^SSTN: <cmdType>

Every time the SIM Application issues an MMI relevant proactive command, via the ME, the TA will receive anotification. 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 ofthe 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 willbe terminated later. URC "^SSTN" is sent with a different proactive command type number (added terminateoffset 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 to the TA when the SIM Application has finished a command cycle and does not issue a subse-quent proactive command. ^SSTN: 254

The TA does not need to respond directly, i.e. AT^SSTR is not required. The next action is left as an imple-mentation decision to the manufacturer of the customer application (TA). Examples: • If a Toolkit menu "^SSTN: 37" (SET UP MENU) proactive command was received at startup, the customer

application can return to this Toolkit menu again after receiving the "^SSTN: 254" URC. • In a Windows Mobile environment, the ToolkitUI application can be closed after receiving this URC. Important notes: • The Idle Mode text transferred with the SET UP IDLE MODE TEXT proactive command should not be

removed as a result of this URC. • If the text transferred with the DISPLAY TEXT proactive command is coded with an immediate response

object set to "1" (see parameter <immediateResponse> of the AT^SSTGI=33 command), the textshould not be removed as a result of this URC.

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 fromthe beginning, too.The TA does not need to respond directly, i.e. related AT^SSTGI and AT^SSTR are neither required norallowed.Since the ME is still busy on SIM access the ME may respond with "+CME ERROR: SIM blocked" or "+CMEERROR: SIM busy" on following PIN required AT Commands for a while. Then TA shall retry until the MEresponds with "OK". The time needed for this process depends on the SIM and may take more than 10 sec-onds.

BGS3 AT Command Set 15.5 ^SSTN



Proactive Command number

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

<cmdType>(num)

<cmdTerminateValue>(num)

BGS3 AT Command Set 15.6 AT^SSTGI


15.6 AT^SSTGI SAT Get Information

Regularly this command is used upon receipt of an URC "^SSTN" to request the parameters of the ProactiveCommand. Then the TA is expected to acknowledge the AT^SSTGI response with AT^SSTR to confirm that the ProactiveCommand 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



Related Proactive Command

Test Command

AT^SSTGI=?Response(s)

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

Read Command

AT^SSTGI?Response(s)

^SSTGI: <state>, <cmdType>OK

Write Command

AT^SSTGI=<cmdType>Response(s)



- + + + + + - - CINTERION

<state>(num)

<cmdType>(num)



15.7 AT^SSTGI SAT Get Information - Refresh (1)

The AT^SSTGI=1 command shall be used after receiving the URC "^SSTN: 1". This URC notifies the TA thatone or more Elementary Files on the SIM have been changed as a result of a SIM application activity, usuallycaused by the network provider. The response to the AT^SSTGI=1 command indicates what type of SIM refreshhas occurred. The change requires that the Elementary Files of the SIM be synchronized with the equivalentinformation (if any) stored inside the TA. Depending on the type of SIM refresh the TA may need to use theAT+CRSM command to read out the Elementary Files and store the refreshed information.

The response parameters <pathLen>, <fileNum> and <fileList> are mandatory if <commandDetails>equals 1 or 2. In all other cases they are optional and can be ignored.

Syntax


1 Proactive command ID, see Section 15.3, Remote-SAT Command Types andTable 15.6.

For every return value of <commandDetails> other than 4 (SIM Reset) the TA shall complete the proactivecommand cycle using AT^SSTGI=1.0 SIM Initialization and Full File Change Notification1 File Change Notification2 SIM Initialization and File Change Notification3 SIM Initialization4 Value "4" means SIM Reset, but the value itself never appears. This is because

value "4" is mapped to the URC "^SSTN: 255" which will be sent when a SIMreset occurs. In this case, the TA does not need to respond, i.e. the SIMRefresh commands AT^SSTGI and AT^SSTR are neither required nor allowed.Instead, as the SIM application restarts, the Toolkit application inside the TAshould also return to initial state after receiving the URC "^SSTN: 255". Formore information on SIM reset and the URC "^SSTN: 255" refer to Section15.5, SAT Notification.

5...255 Reserved values

Number of bytes coded in <fileList>

Write Command

AT^SSTGI=1Response(s)

^SSTGI: <cmdType>, <commandDetails>[, <pathLen>, <fileNum>, <fileList>]OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)

<commandDetails>(num)

<pathLen>(num)



Number of updated Elementary Files (EF) with path given in <fileList>

String containing Elementary File paths. Each path contains at least two file entries; each file entry (MF, EF orDF) consists of two bytes, e.g. '3F002FE2' or '3F007F206FAD'. Every path in the file description begins with theMaster File (MF). There can be any number of Dedicated File (DF) entries between Master File and ElementaryFile.

Example

If the SIM contains an AT&T Customer Service Profile (CSP) the TA shall react to the URC "^SSTN: 1" as follows:When <commandDetails> equals 0, 2, 3 or 4 the TA shall synchronize the SIM information by using AT+CRSM.When <commandDetails> equals 1, reloading the SIM information with AT+CRSM is necessary only if the Ele-mentary File EF_CSP is found in the <fileList>. The example shows the latter case:

This is an example for a Refresh with File Change Notification at EF_FDN for USIM.

<fileNum>(num)

<fileList>(num)

^SSTN: 1 Indicates that a SIM Refresh has occurred.AT^SSTGI=1 Request type of SIM Refresh.^SSTGI: 1,1,68,5,"3F007F665F304F313F007F665F304F343F007FFF6F153F007F206FC63F007F206FC5"OK The Elementary File EF_CSP is included in the

Refresh File List, indicating that its contents mayhave changed.

AT^SSTR=1,0 Terminate the proactive command.OKAT+CRSM=176,28437,0,0,26 TA reads the EF_CSP.+CRSM: 144,0,"01F00200038004C005C00600070008830984C0DDFF00FF00FF00"

The SIM Refresh concerns the PLMN mode bit thathas been enabled.

OK

^SSTN: 1 Indicates that a SIM Refresh has occurred.AT^SSTGI=1 Request type of SIM Refresh.^SSTGI: 1,1,6,1,"3F007FFF6F3B"OK The Elementary File EF_FDN is included in the

Refresh File List, indicating that its contents mayhave changed.

AT^SSTR=1,0 Terminate the proactive command.OK



15.8 AT^SSTGI SAT Get Information - Set Up Event List (5)

This command shall be used after receiving the URC ^SSTN: 5.However, please refer to the note below.The response informs the TA of the events that it must monitor within itself. If any of these events occur the TAmust report them to the ME.

Syntax


5 Proactive command ID, see Table 15.6, Command Type Table.

This byte is RFU.

The event list tells the TA which events have to be reported to the ME via the related commandsAT^SSTR=(232, 233, 235, 236)0...255 Used as bit fieldbit 1-4 RFUbit 5 0: User Activity not in Event List

1: Any user activity (keyboard press) has to be signaled to the ME bit 6 0: Idle Screen Available not in Event List

1: Any idle screen available event has to be signaled to the ME. bit 7 RFUbit 8 0: Language Selection not in Event List

1: Language Selection events have to be signaled to the ME.bit 9 0: Browser Termination not in Event List

1: Browser Termination events have to be signaled to the MEbit 10-16 RFU

Note• It is possible to issue AT^SSTGI during states IDLE, PAC and WAIT for this proactive command without pre-

viously receiving a URC ^SSTN:<cmdType>, see AT^SSTGI.

Write Command


^SSTGI: <cmdType>, <commandDetails>, <eventList>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<eventList>(num)



15.9 AT^SSTGI SAT Get Information - Set Up Call (16)

This command shall be used after receiving the URC ^SSTN: 16. If the SIM Application attempts to set up a callit uses this response to inform the TA of the call parameters.

The sequence of events is as follows:1. After the Remote-SAT notification 16 was issued the TA has to request the command parameter usingAT^SSTGI=16.2. If the SIM Application does not supply a confirmation text or icon parameter, the TA gives other information tothe user, e.g. the telephone number. In this case refer to step 4.3. If the SIM Application supplies a non empty confirmation text or icon parameter, the TA uses only these to askthe user whether or not he wishes to set up the call.4. If the user confirms to set up the call, AT^SSTR=16,0 shall be responded.5. If the user denies to set up the call, AT^SSTR=16,34 shall be responded.6. After confirmation phase the TA may present a dialing animation on the screen until a mandatory parameterline ^SSTR: 16, <TermQualifier>, <TerminationCauseText> is issued.7. If <TermQualifier> is not equal to 0 the call setup process has not been successfully. If <TerminationCause-Text> is not an empty string, this text shall be shown to the user for an appropriate time, e.g. 2 seconds. The textcontains information regarding the dial termination cause, e.g. call barring through Call Control by SIM mecha-nism. If <TerminationCauseText> is an empty string, the TA shall give an own indication to the user.8. If <TermQualifier> is equal to 0, the call setup process has been started:If <TerminationCauseText> is not an empty string, this text shall be used to inform the user during the call setup.If <TerminationCauseText> is an empty string, <callSetupText> and/or <confirmationIconId> shall beused to inform the user during call setup. However, if <callSetupText> contains no data, too, no indicationshall be shown.9. The TA shall give the user an opportunity to end an ongoing call, set up by the Proactive Command. In thiscase the TA shall issue an ATH command to the ME.

Syntax



0 Set up call, but only if not currently busy on another call1 Set up call, but only if not currently busy on another call, with redial2 Set up call, putting all other calls (if any) on hold3 Set up call, putting all other calls (if any) on hold, with redial4 Set up call, disconnecting all other calls (if any)

Write Command


^SSTGI: <cmdType>, <commandDetails>, <confirmationText>, <calledNumber>, <callSetupText>, <confirmationIconQualifier>, <confirmationIconId>, <callSetupIconQualifier>, <callSetupIconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)




5 Set up call, disconnecting all other calls (if any), with redial6...255 Reserved Values

String for user confirmation stage

String containing called number

String for call set up stage

0...255 Used as bit fieldbit 1 0: Icon is self explanatory and replaces text

1: Icon is not self-explanatory and shall be displayed with the text Determinedvalue only if associated icon ID is not 0 (an icon exists).

bit 2-8 RFU

0...2550 No Icon



bit 2-8 RFU

0...2550 No Icon

Note• If the Fixed Dialling Number service is enabled, the number included in the SET UP CALL proactive command

shall not be checked against those of the FDN list.

<confirmationText>(str)

<calledNumber>(num)

<callSetupText>(str)

<confirmationIconQualifier>(num)

<confirmationIconId>(num)

<callSetupIconQualifier>(num)

<callSetupIconId>(num)



15.10 AT^SSTGI SAT Get Information - Send SS (17)

This command shall be used after receiving the URC ^SSTN: 17The module is sending a supplementary service request to the network, and is alerting the user of this. Text andan icon identifier shall be passed to the TA to display to the user.

Syntax



This byte is RFU.

String to provide the user with information.If the string is provided by the SIM, the TA shall use it to inform the user. This is also an indication that the TAshould not give any other information to the user on the fact that the ME is sending a short message.If the alpha identifier is not provided by the SIM, the ME may give information to the user concerning what ishappening.



bit 2-8 RFU

0...2550 No Icon

Write Command


^SSTGI: <cmdType>[, <commandDetails>][, <text>], <iconQualifier>, <iconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<text>(str)

<iconQualifier>(num)

<iconId>(num)



15.11 AT^SSTGI SAT Get Information - Send USSD (18)

This command shall be used after receiving the URC ^SSTN: 18The module is sending an unstructured supplementary service request to the network, and is alerting the user ofthis.Text and an icon identifier shall be passed to the TA to display to the user.

Syntax



This byte is RFU.




bit 2-8 RFU

0...2550 No Icon

Write Command


^SSTGI: <cmdType>[, <commandDetails>][, <text>], <iconQualifier>, <iconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<text>(str)


<iconId>(num)



15.12 AT^SSTGI SAT Get Information - Send Short Message (19)

This command shall be used after receiving the URC ^SSTN: 19The SIM Application is sending a Short Message and the TA is informed of this. The user can be passed a stringcontaining information to display.

Syntax



This byte is RFU.




bit 2-8 RFU

0...2550 No Icon1 An icon is provided by the SIM, the icon indicated in the command may be used

by the ME to inform the user, in addition to, or instead of the alpha identifier, asindicated with the icon qualifier.

Write Command


^SSTGI: <cmdType>, <commandDetails>, <textInfo>, <iconQualifier>, <iconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<textInfo>(str)


<iconId>(num)



15.13 AT^SSTGI SAT Get Information - Send DTMF (20)

This command shall be used after receiving the URC ^SSTN: 20The SIM Application is sending DTMF tones to the network, and can provide the TA with some information aboutthis.Text and an icon identifier can be passed to the TA to display to the user.

Syntax



This byte is RFU.




bit 2-8 RFU

0...2550 No Icon

Write Command


^SSTGI: <cmdType>, <commandDetails>, <text>, <iconQualifier>, <iconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<text>(str)


<iconId>(num)



15.14 AT^SSTGI SAT Get Information - Launch Browser (21)

This command shall be used after receiving the URC ^SSTN: 21.If the SIM Application attempts to start an Internet Browser, it uses this response to inform the TA of the launchparameters.

The sequence of events is as follows:1. After the Remote-SAT notification 21 was issued the TA shall ask for the command parameters viaAT^SSTGI=21.2. The ME shall ask the user for confirmation using the Alpha Identifier/Icon Identifier (user confirmation phase)if present, when it receives a LAUNCH BROWSER command which requests to connect the existing browsersession to a new URL or to terminate a browser session.3. If the user confirms to start the browser, AT^SSTR=21,0 shall be responded.4. If the user denies to start the browser, AT^SSTR=21,34 shall be responded.5. The SIM Application will end the proactive session. 6. The ME shall request content using the given URL. However, if no URL string is supplied a default URL shallbe used.7. On response AT^SSTR=21,0 the browser session may still be active while a next proactive command isissued. Therefore the end of the browser session shall be reported to the ME via browser termination event com-mand asynchronously if determined by the event list.For details please refer to AT^SSTR.

Syntax


21 Proactive command ID, see Remote-SAT Command Types

This byte is RFU.

String for user confirmation stage


Write Command


^SSTGI: <cmdType>, <commandDetails>, <confirmationText>, <confirmationIconQualifier>, <iconId>, <browserIdentity>, <url>, <bearerList>, <fileRefList>, <gatewayIdentity>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<confirmationText>(str)

<confirmationIconQualifier>(num)




bit 2-8 RFU

0...2550 No Icon

0...255 Browser to be used0 Default Browser shall be used.1...255 RFU

String containing URL to be used by the TA to request content. The way the ME requests content using the URLis out of the scope of the present document. This is specified in RFC 1738 Annex K for example.

“00“ SMS“01“ CSD“02“ USSD“03“ GPRS04...FF RFU

String containing full path to the provisioning file. The first byte contains the number of files. Every comma sep-arated path is the concatenation of file identifiers starting from the Master File (e.g. 3F007F206FXY). The filecontains a single unambiguous set of parameters required to make the connection. The content of the file isexpected to be consistent with the format defined for provisioning information for the requested type of browser.

String containing the Gateway/Proxy Identity which gives to the mobile the name/identity of the Gateway/Proxyto be used for connecting to the URL. This Gateway/Proxy identity is required when the bearer data object ispresent.

<iconId>(num)

<browserIdentity>(num)

<url>(str)

<bearerList>(str)

<fileRefList>(str)

<gatewayIdentity>(str)



15.15 AT^SSTGI SAT Get Information - Play Tone (32)

This command shall be used after receiving the URC ^SSTN: 32.The ME has been instructed to generate an audible tone, and may pass to the TA some information to supportthis.Text and an icon identifier are passed to the TA for display to the user.

Syntax



This byte is RFU.

String to accompany tone

Tone generated by the ME01...08 Standard supervisory tones:“01“ Dial tone“02“ Called subscriber busy“03“ Congestion“04“ Radio path acknowledge“05“ Radio path not available / Call dropped“06“ Error / Special information“07“ Call waiting tone“08“ Ringing tone16...18 ME proprietary tones:“16“ General beep“17“ Positive acknowledgement tone“18“ Negative acknowledgement or error tone

Write Command


^SSTGI: <cmdType>, <commandDetails>, <infoText>, <tone>, <durationUnit>, <duration>, <iconQualifier>, <iconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<infoText>(str)

<tone>(str)



0 Minutes1 Seconds2 Tenth of Seconds

1...255 Duration of tone, expressed in units



bit 2-8 RFU

0...2550 No Icon

<durationUnit>(num)

<duration>(num)


<iconId>(num)



15.16 AT^SSTGI SAT Get Information - Display Text (33)

This command shall be used after receiving the URC ^SSTN: 33. The TA gets a message to be displayed to theuser. The message can have different display characteristics. Text and icon identifier can be passed to the TAto be displayed.

Syntax


33 Proactive command ID, see Section 15.3, Remote-SAT Command Types andTable 15.6.

0...255 Used as bit fieldbit 1 0: Normal priority (see note).

1: High priority (see note).bit 2-7 RFUbit 8 0: Clear message after a delay.

1: Wait for user to clear message.

String to be displayed (up to 240 bytes)

This parameter indicates whether the ME should sustain the display beyond sending the TERMINALRESPONSE. 0 Send TERMINAL RESPONSE when text is cleared from screen.1 Send TERMINAL RESPONSE immediately and continue to display the text

until one of the following events occurs: • A subsequent proactive command is received, containing display data.• A short delay notified with <commandDetails> has expired.• User intervention.

Write Command


^SSTGI: <cmdType>, <commandDetails>, <text>, <immediateResponse>, <iconQualifier>, <iconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<text>(str)

<immediateResponse>(num)



• A higher priority event occurs, e.g. a mobile terminated call.No further TERMINAL RESPONSE shall be sent when the ME removes thetext from the display, regardless of the cause.If the <immediateResponse> parameter equals "1" the subsequent "^SSTN:254" URC should not be used to clear the text from the screen - in this case thetext should remain on the screen until one of the above events occurs.

0...255 Used as bit fieldbit 1 0: Icon is self explanatory and replaces text.


bit 2-8 RFU

0...2550 No Icon

Notes• The MMI shall reject normal priority text commands if the screen is currently used for more than its normal

standby display, e.g. if the MMI is in sub-menu. If the command is rejected, the MMI sends the TERMINALRESPONSE message to the SIM (ME currently unable to process command - screen busy).

• High priority text shall be displayed on the screen immediately, except if a priority conflict of the alerting eventsoccurs, e.g. incoming call or a URC if the battery needs to be charged, see GSM 11.14, Chapter "ProactiveSIM commands and procedures, Display Text".


<iconId>(num)



15.17 AT^SSTGI SAT Get Information - Get Inkey (34)

This command shall be used after receiving the URC ^SSTN: 34.The TA is asked to prompt the user for an input, which is a single character. Help can be requested by the user,if available.Text and an icon identifier can be passed to the TA to be displayed.

Syntax



0...255 Used as bit fieldbit 1 0: Digits only (0 9, *, # and +)

1: Alphabet setbit 2 0: SMS default alphabet (GSM character set)

1: UCS2 alphabetbit 3 0: Character sets defined by bit 1 and bit 2 are enabled

1: Character sets defined by bit 1 and bit 2 are disabled and the "Yes/No"response is requested

bit 4-7 RFUbit 8 0: No help information available

1: Help information available

String as prompt for text.



bit 2-8 RFU

Write Command




- + + + + + - -

<cmdType>(num)


<text>(str)




0...2550 No Icon

<iconId>(num)



15.18 AT^SSTGI SAT Get Information - Get Input (35)

This command shall be used after receiving the URC ^SSTN: 35.The TA is asked to prompt the user for an input, of a specified length and type, e.g. digits only. Help can berequested by the user, if available.Text and an icon identifier can be passed to the TA to be displayed.

Syntax



0...255 Used as bit fieldbit 1 0: Digits only (0 9, *, # and +)

1: Alphabet setbit 2 0: SMS default alphabet (GSM character set)

1: UCS2 alphabetbit 3 0: ME may echo user input on the display

1: User input shall not be revealed in any way (see note)bit 4 0: User input to be in unpacked format

1: User input to be in SMS packed formatbit 5-7 RFUbit 8 0: No help information available


String as prompt for text

0...255 Minimum length of user input.

0...255 Maximum length of user input.

Write Command


^SSTGI: <cmdType>, <commandDetails>, <text>, <responseMin>, <responseMax>[, <defaultText>], <iconQualifier>, <iconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<text>(str)

<responseMin>(num)

<responseMax>(num)



String supplied as default response text



bit 2-8 RFU

0...2550 No Icon

Note• Hidden entry mode (see GSM 11.14) is only available when using digit input. In hidden entry mode only char-

acters ('0', '9', '*' and '#') are allowed.

<defaultText>(str)


<iconId>(num)



15.19 AT^SSTGI SAT Get Information - Select Item (36)

This command shall be used after receiving the URC ^SSTN: 36.The TA is supplied with a list of items allowing the user to select one. Help can be requested by the user, if avail-able and the presentation style is specified. In addition to text strings and icon identifiers, a next action indicatorinforms the user of the likely result of selecting a chosen item.

Syntax



0...255 Used as bit fieldbit 1 0: Presentation type is not specified

1: Presentation type is specified in bit 2bit 2 0: Presentation as a choice of data values, if bit 1 = '1'

1: Presentation as a choice of navigation options if bit 1 is '1'bit 3 0: No selection preference

1: Selection using soft key preferredbit 4-7 RFUbit 8 0: No help information available


Number of items in the list

String giving menu title

Write Command


The first line of output from the ME is:^SSTGI: <cmdType>, <commandDetails>, <numOfItems>, <titleText>, <defaultItemId>, <itemIconsPresent>, <itemIconsQualifier>, <titleIconQualifier>, <titleIconId>One line follows for every item, repeated for <numOfItems>:^SSTGI: <cmdType>, <itemId>, <itemText>, <nextActionId>, <iconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<numOfItems>(num)

<titleText>(str)



ID of default itemThe SIM may supply with the list an indication of the default item, e.g. the previously selected item 0 No default item issued by the SIM application1...255 Id of the default Item

0 No icons1 Icons present



bit 2-8 RFU



bit 2-8 RFU

0...2550 No Icon

Item identifier (1 - <numOfItems>)

String giving menu title

The next proactive command type to be issued upon execution of the menu item. See Remote-SAT CommandTypes

0 Next Action information available

0...2550 No Icon

<defaultItemId>(num)

<itemIconsPresent>(num)

<itemIconsQualifier>(num)

<titleIconQualifier>(num)

<titleIconId>(num)

<itemId>(num)

<itemText>(str)

<nextActionId>(num)

<iconId>(num)



15.20 AT^SSTGI SAT Get Information - Set up Menu (37)

This command shall be used after receiving the URC ^SSTN: 37.However, please refer to note below. The response provides the main menu of the SIM Application to the TA. Itwill be stored by the TA so that it can be displayed without invoking a proactive session.

Syntax



0...255 Used as bit fieldbit 1 0: No selection preference

1: Selection using soft key preferredbit 2-7 RFUbit 8 0: No help information available


Number of menu items in the list

String displaying menu title

0 No icons1 Icons present

0...255 Used as bit field

Write Command


The first line of output from the ME is:^SSTGI: <cmdType>, <commandDetails>, <numOfItems>, <titleText>, <menuItemIconsPresent>, <menuItemIconsQualifier>, <titleIconQualifier>, <titleIconId>One line follows for every item, repeated for <numOfItems>:^SSTGI: <cmdType>, <itemId>, <itemText>, <nextActionId>, <iconId>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<numOfItems>(num)

<titleText>(str)

<menuItemIconsPresent>(num)

<menuItemIconsQualifier>(num)



bit 1 0: Icon is self explanatory and replaces text 1: Icon is not self-explanatory and shall be displayed with the text Determined

value only if associated icon ID is not 0 (an icon exists). bit 2-8 RFU



bit 2-8 RFU

0...2550 No Icon

Menu item identifier (1 - <numOfItems>)

Title of menu item

The next proactive command type to be issued upon execution of the menu item. See Remote-SAT CommandTypes

0 No next Action information available

0...2550 No Icon

Notes• As with every proactive command the TA is expected to acknowledge the ^SSTGI response with AT^SSTR

to confirm that the proactive command has been executed.Terminal response via AT^SSTR will not provide any user information in case of this proactive command.Refer to AT^SSTR.

• AT^SSTGI can be issued during states IDLE, PAC and WAIT for this proactive command without previouslyreceiving a URC ^SSTN:<cmdType>, see AT^SSTGI.

<titleIconQualifier>(num)

<titleIconId>(num)

<itemId>(num)

<itemText>(str)

<nextActionId>(num)

<iconId>(num)



15.21 AT^SSTGI SAT Get Information - Set up Idle Mode Text (40)

This command shall be used after receiving the URC ^SSTN: 40.It provides text and optionally an icon to be displayed by the TA when the display is Idle.

Syntax



This byte is RFU.

to display when TA in IDLE mode



bit 2-8 RFU

0...2550 No Icon

Note• AT^SSTGI can be issued during states IDLE, PAC and WAIT for this proactive command without previously

receiving a URC ^SSTN:<cmdType>, see AT^SSTGI.

Write Command




- + + + + + - -

<cmdType>(num)


<text>(str)


<iconId>(num)



15.22 AT^SSTGI SAT Get Information - Language Notification (53)

This command shall be used after receiving the URC ^SSTN: 53.It provides text to inform the TA about the language currently used for any text string within proactive commandsor envelope command responses.The notified language remains valid until the end of the card session or upon executing another LANGUAGENOTIFICATION command.If the Toolkit application is not aware of the currently selected language, no specific language or several lan-guages will be used. The SIM may notify non-specific language. All LANGUAGE NOTIFICATION previouslymade will be cancelled.Two types of language notification are defined:• specific, where a two-character language notification is issued in <langText>,• non-specific, where no language notification is issued, i.e. <langText> is an empty string.The TA may use the language included in LANGUAGE NOTIFICATION as appropriate. For instance, this couldbe done to avoid a mix of languages in screen displays combining ME MMI and SIM Toolkit originating textstrings.

Syntax



0...255 Used as bit fieldbit 1 0: non-specific language notification

1: specific language notificationbit 2-8 RFU

Language code string provided as a pair of alpha-numeric characters, defined in ISO 639. Each alphanumericcharacter is coded on one byte using the SMS default 7-bit coded alphabet as defined in 3GPP TS 23.038[17].

Note• AT^SSTGI can be issued during states IDLE, PAC and WAIT for this proactive command without previously

receiving a URC ^SSTN:<cmdType>, see AT^SSTGI.

Write Command


^SSTGI: <cmdType>, <commandDetails>, <langText>OKERROR+CME ERROR: <err>


- + + + + + - -

<cmdType>(num)


<langText>(str)

BGS3 AT Command Set 15.23 AT^SSTR


15.23 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



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

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 [22].

Response number entered by user

Response string entered by user

Test Command

AT^SSTR=?Response(s)

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

Read Command

AT^SSTR?Response(s)

^SSTR: <state>, <cmdType>OK

Write Command

AT^SSTR=<cmdType>, <status>[, <inputNumber>][, <inputString>][, <statAddInfo>]Response(s)

OK


- + + + + + - - CINTERION

<state>(num)

<cmdType>(num)

<status>(num)

<inputNumber>(num)

<inputString>(str)



Optional additional command status; for possible values refer to GSM 11.14 [22].

<statAddInfo>(num)



15.24 AT^SSTR SAT Response - Refresh (1)

The TA is expected to acknowledge the AT^SSTGI response with AT^SSTR to confirm that the Proactive Com-mand has been executed.

Syntax


0...2550 Command performed successfully32 TA currently unable to process command132 TA currently unable to process command because screen is busy

Optional additional command status; for possible values refer to GSM 11.14 [22]. 0...255

Note• The refresh action (SIM data cache update) will be performed in any case, i.e. <status> values other than

0 will be ignored.

Write Command

AT^SSTR=1, <status>, , [, <statAddInfo>]Response(s)

OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.25 AT^SSTR SAT Response - Set Up Event List (5)

The TA is expected to acknowledge the AT^SSTGI response with AT^SSTR to confirm that the Proactive Com-mand has been executed. The TA is acknowledging that the event list has been set up correctly.

Syntax


0...2550 Command performed successfully32 TA currently unable to process command132 TA currently unable to process command because screen is busy


Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.26 AT^SSTR SAT Response - Set Up Call (16)


Syntax


0...2550 Command performed successfully. Indicate that the user has accepted the call

request.4 Command performed successfully, but requested icon could not be displayed.16 Proactive SIM session terminated by user20 USSD/SS Transact terminated by user32 TA currently unable to process command132 TA currently unable to process command because screen is busy34 User did not accept the proactive command. Indicate that the user has denied

the call request35 User cleared down call before connection or network release


Note• After confirmation phase the TA may show a dialling animation on the screen until a mandatory response

parameter is issued.^SSTR: <cmdType>, <TermQualifier>, <TerminationCauseText>

Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.27 AT^SSTR SAT Response - Send SS (17)


Syntax


0...2550 Command performed successfully. Indicate that the user has accepted the SS

request.4 Command performed successfully, but requested icon could not be displayed.20 USSD/SS Transact terminated by user32 TA currently unable to process command132 TA currently unable to process command because screen is busy33 Network currently unable to process command


Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.28 AT^SSTR SAT Response - Send USSD (18)


Syntax


0...2550 Command performed successfully. Indicate that the user has accepted the

USSD request.4 Command performed successfully, but requested icon could not be displayed.20 USSD/SS Transact terminated by user32 TA currently unable to process command132 TA currently unable to process command because screen is busy33 Network currently unable to process command


Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.29 AT^SSTR SAT Response - Send Short Message (19)


Syntax



Send SMS request.4 Command performed successfully, but requested icon could not be displayed.20 USSD/SS Transact terminated by user32 TA currently unable to process command132 TA currently unable to process command because screen is busy33 Network currently unable to process command


Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.30 AT^SSTR SAT Response - Send DTMF (20)


Syntax



Send DTMF request.4 Command performed successfully, but requested icon could not be displayed.32 TA currently unable to process command132 TA currently unable to process command because screen is busy


Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.31 AT^SSTR SAT Response - Launch Browser (21)


Syntax



Launch Browser request.4 Command performed successfully, but requested icon could not be displayed.32 TA currently unable to process command34 User did not accept the proactive command. Indicate that the user has denied

the Launch Browser request38 Launch Browser generic error with additional information "No specific cause

can be given".132 TA currently unable to process command because screen is busy138 Launch Browser generic error with additional information "Bearer unavailable".238 Launch Browser generic error with additional information "Browser unavail-

able".239 Launch Browser generic error with additional information "ME unable to read

the provisioning data".

For the general result "Launch Browser generic error code", it is mandatory for the ME to provide additional infor-mation. 0...2550 "No specific cause can be given"1 "Bearer unavailable"2 "Browser unavailable"3 "ME unable to read the provisioning data"

Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.32 AT^SSTR SAT Response - Play Tone (32)


Syntax



request.4 Command performed successfully, but requested icon could not be displayed.16 Proactive SIM session terminated by user32 TA currently unable to process command132 TA currently unable to process command because screen is busy


Note• This command starts playing the tone by the ME. It is possible for the TA to stop playing the tone via user

break, i.e. issuing any character whilst the command is running.

Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.33 AT^SSTR SAT Response - Display Text (33)


Syntax



request.4 Command performed successfully, but requested icon could not be displayed.16 Proactive SIM session terminated by user17 Backward move in the proactive SIM session requested by the user18 No response from user32 TA currently unable to process command132 TA currently unable to process command because screen is busy


Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.34 AT^SSTR SAT Response - Get Inkey (34)


Syntax



request.4 Command performed successfully, but requested icon could not be displayed.16 Proactive SIM session terminated by user17 Backward move in the proactive SIM session requested by the user18 No response from user19 Help information required by the user32 TA currently unable to process command132 TA currently unable to process command because screen is busy

User response entered as a string parameter


Notes• Coding of any input character is related to the selected alphabet:

• Input of a character in case of GSM character set requests one byte, e.g. "Y".• Input of any characters in UCS2 alphabet requests a 4 byte set, e.g. "0059" is coding the same character "Y".• If, as a user response, a binary choice (Yes/No) is requested by the SIM application using bit 3 of the <com-mandDetails> parameter the valid content of the <inputString> is:a) GSM alphabet: "Y" or "y" (positive answer) and "N" or "n" (negative answer).b) UCS2 alphabet "0079" or "0059" (positive answer) and "006E" or "004E" (negative answer) For moredetailed information refer to AT^SSTGI.• Coding of an empty string is done as a "\1b" string with every alphabet.

• The alphabet - and therefore the set of allowed characters - is specified by the ME in the response to therelated AT^SSTGI. However, do not mix up this alphabet with the one selected for the alphabet format on thetransmission line on SAT activation, i.e. second parameter of AT^SSTA).

Write Command

AT^SSTR=34, <status>, , <inputString>[, <statAddInfo>]Response(s)

OK


- + + + + + - -

<status>(num)

<inputString>(str)

<statAddInfo>(num)



15.35 AT^SSTR SAT Response - Get Input (35)


Syntax




User response entered as a string, length depends on values of <responseMin> and <responseMax> returnedby the related AT^SSTGI command


Notes• Coding of any input character is related to the selected alphabet:

• Input of a character in case of GSM character set requests one byte, e.g. "Y".• Input of any characters in UCS2 alphabet requests a 4 byte set, e.g. "0059" is coding the same character "Y".• Coding of an empty string is done as a "\1b" string with every alphabet.


Write Command

AT^SSTR=33, <status>, , <inputString>[, <statAddInfo>]Response(s)

OK


- + + + + + - -

<status>(num)

<inputString>(str)

<statAddInfo>(num)



15.36 AT^SSTR SAT Response - Select Item (36)

The TA is expected to acknowledge the AT^SSTGI response with AT^SSTR to confirm that the Proactive Com-mand has been executed. The TA sends a response that can indicate the user's intentions, e.g. when the useris requesting help or selecting a menu item.GSM11.14 states:

Syntax




Item IDs are supplied by the SIM Application1...255 ID of selected item can be issued if a <status> value of 0 is returned


Notes• "When the ME issues a successful TERMINAL RESPONSE ('0X' result value ...) for a SELECT ITEM com-

mand, it shall supply the identifier of the item selected by the user in the Item identifier data object. If the MEissues a TERMINAL RESPONSE with result "Help information required by the user" for a SELECT ITEMcommand, it shall supply the identifier of the item for which the user is requiring help information. All othertypes of TERMINAL RESPONSE do not need to include Item identifier. If one is included by the ME, the SIMshall ignore it.".

• For compatibility reasons <itemId> is optional in case of <status>=19 ("Help information required by theuser"). In this case <itemId>=0 is sent to the SIM.

Write Command

AT^SSTR=36, <status>, <itemId>, [, <statAddInfo>]Response(s)

OK


- + + + + + - -

<status>(num)

<itemId>(num)

<statAddInfo>(num)



15.37 AT^SSTR SAT Response - Setup Menu (37)


Syntax



request.4 Command performed successfully, but requested icon could not be displayed.32 TA currently unable to process command132 TA currently unable to process command because screen is busy


Notes• The response simply conveys, to the SAT, the information that the main menu was received and set up on

the user interface. It does not transmit any information about a selected item, like in the case of AT^SSTR.

Once this command was executed the user can proceed as described in the AT^SSTR SAT Response - SetupMenu (37).

• As with every proactive command the TA is expected to acknowledge the ^SSTGI response with AT^SSTRto confirm that the proactive command has been executed.

Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.38 AT^SSTR SAT Response - Set Up Idle Mode Text (40)


Syntax



request.32 TA currently unable to process command132 TA currently unable to process command because screen is busy


Write Command


OK


- + + + + + - -

<status>(num)

<statAddInfo>(num)



15.39 AT^SSTR SAT Response - Language Notification (53)

The TA is expected to acknowledge the AT^SSTGI response with AT^SSTR to confirm that the Proactive Com-mand has been executed. The TA indicates whether the Language Notification command was correctly exe-cuted.

Syntax




request.32 TA currently unable to process command132 TA currently unable to process command because screen is busy


Write Command


OK


- + + + + + - -

<cmdType>(num)

<status>(num)

<statAddInfo>(num)



15.40 AT^SSTR SAT Event - Menu Selection (211)

The TA specifies the user's selection of an item from the main menu, which was set up using SETUP MENUcommand. Alternatively help can be requested.

Syntax


0...2550 Command performed successfully.19 Help information required by the user, no other value can be returned.

ID of selected item0...255

Write Command

AT^SSTR=211, <status>, <itemId>Response(s)

OK


- + + + + + - -

<status>(num)

<itemId>(num)



15.41 AT^SSTR SAT Event - User Activity (232)

Sent by the customer application to indicate that a key has been pressed.

SyntaxWrite Command

AT^SSTR=232Response(s)

OK


- + + + + + - -



15.42 AT^SSTR SAT Event - Idle Screen Available (233)

Sent by the customer application to indicate that the screen has become idle.

SyntaxWrite Command


OK


- + + + + + - -



15.43 AT^SSTR SAT Event - Language Selection (235)

Sent by the customer application to indicate that the customer application has changed the language.The last value given via this command is also provided to the SIM as response to the proactive command "Pro-vide Local Information (Language Setting)".

Syntax


Two character language tag, e.g. "en" for English or "de" for German. Default value is "en".

Write Command

AT^SSTR=235, , , <inputString>Response(s)

OK


- + + + + + - -

<inputString>(str)



15.44 AT^SSTR SAT Event - Browser Termination (236)

Sent by the customer application to indicate that the internet browser application has been terminated.

Syntax


Browser Termination Cause0...2550 User termination1 Error termination

Write Command

AT^SSTR=236, , , <TermCause>Response(s)

OK


- + + + + + - -

<TermCause>(num)



15.45 AT^SSTR SAT Event - Terminate Command (254)

This command allows the TA to finish an ongoing proactive command. This is done by sending repeatedly a ter-minal response "ME currently unable to process command" to the SIM (see GSM 11.14 [22]), if issued in statesPAC or WAIT. No action is performed if the interface is already in IDLE state. However, the command returns"OK".The reaction to the terminal response depends on the SIM application. The command can be used to return toIDLE state regardless whether a proactive command is ongoing or not.

Syntax

Note• This command is allowed in states IDLE, PAC and WAIT and forces a return to IDLE state.

Write Command


OK


- + + + + + - -

BGS3 AT Command Set 15.46 Examples for Using Remote-SAT


15.46 Examples for Using Remote-SAT

To give you an idea of how to start and use Remote-SAT, you may follow the steps described below:

// Start after switch on the moduleatOK

// Switch on verbose error messagesat+cmee=2OK

// Enter the PIN code (if necessary due to SIM configuration)at+cpin=1234OK

// Query the Remote-SAT activation statusat^ssta?^SSTA: 1,0,1,"6FFFFFFF7F0300DF7F" OK// First '1' indicates that the interface is in OFF state, i.e. the Automatic Response (AR) mode is enabled. Duringthis mode all SAT Proactive Commands are handled internally by the ME.

// Tell the module that the TA is interested in handling SAT, i.e. switch to Explicit Response (ER) mode.at^ssta=1,0OK

// This setting takes effect after next start of the ME only, so switch off firstAT^SMSO^SMSO: MS OFFOK ^SHUTDOWN

// Switch on ME again and wait until system start indication (if not in autobaud mode, refer AT+IPR)^SYSSTART


// Enter the PIN code (if necessary due to SIM configuration)at+cpin=1234OK

// Receiving the first proactive command (if the mounted SIM carries a SIM Application)^SSTN:37

// Requesting parameter detailsat^sstgi=37

// These are the details:^SSTGI: 37,0,3,"SAT Special Menu",0,1,1,0^SSTGI: 37,1,"News",0,0^SSTGI: 37,2,"EMail",0,0^SSTGI: 37,3,"Banking",0,0

OK

// To query the status of the proactive commandat^sstr=37,0



OK

// SAT indicates that the proactive session has ended and enters its main menu (which should then be openedon the screen by an MMI): ^SSTN:254

// Selecting item number 1 of the menu sent before:at^sstr=211,0,1

OK

// Receiving the next proactive command:^SSTN:36

// Requesting more information...at^sstgi=36

// ... and get it:^SSTGI: 36,0,12,"Rubriken >",0,0,1,1,0^SSTGI: 36,1,"News >",0,0^SSTGI: 36,2,"Stock Infos>",0,0^SSTGI: 36,3,"Aktien D >",0,0^SSTGI: 36,4,"Aktien INT >",0,0^SSTGI: 36,5,"Sports >",0,0^SSTGI: 36,6,"1.BL-Clubs >",0,0^SSTGI: 36,7,"Unterhaltung>",0,0^SSTGI: 36,8,"Horoskop >",0,0^SSTGI: 36,9,"Wetter D >",0,0^SSTGI: 36,10,"Wetter INT >",0,0^SSTGI: 36,11,"Wetter spez>",0,0^SSTGI: 36,63,"Extras >",0,0

OK

// Remember to acknowledge:at^sstr=36,0,63

OK

// And again: Receiving the next proactive command:^SSTN:36// ...

ExamplesEXAMPLE 1


EXAMPLE 2

// Enter the PIN codeat+cpin=1234OK

EXAMPLE 3

// Start Remote-SATat^ssta=1,0OK

EXAMPLE 4

// Proactive command "GET INKEY" is issued by the SIM^SSTN: 34



EXAMPLE 5

// Get complete dataat^sstgi=34^SSTGI: 34,0,"<COLOUR-ICON>",1,2OK

EXAMPLE 6

// Use GET RESPONSE command (192) to analyze SIM file EF-IMG (hex. 4F20)at+crsm=192,20256,0,0,15+CRSM: 144,0,000000644F20040014F04401020114OK

EXAMPLE 7

// Use READ RECORD command (178) to get its contentat+crsm=178,20256,2,4,20+CRSM: 144,0,010808214F0200000016FFFFFFFFFFFFFFFFFFFFOK

EXAMPLE 8

// Use READ BINARY command (176) to get content of image instance data file (e.g. hex 4F02)at+crsm=176,20226,0,0,22+CRSM: 144,0,080802030016AAAA800285428142814281528002AAAAOK

at+crsm=176,20226,0,22,9+CRSM: 144,0,FF000000FF000000FFOK

EXAMPLE 9

// Finalize Proactive Command sessionat^sstr=34,0,,"+"OK

EXAMPLE 10

// Session end indication, i.e. display SAT main menu^SSTN: 254

BGS3 AT Command Set 16. Phonebook Commands


16. Phonebook Commands

The AT commands described in this chapter allow the external application to access the phonebooks located inthe BGS3's memory or on the attached Subscriber Identity Module (SIM).

16.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 #10is used in order to determine collation weights for Code points between 0000 and 06FF, and composed keys areused for Code points from ranges 0700 to 33FF, A000 to D7FF and E000 to FFFD. Code Points not referencedin 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 convertedinternally 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 whichthese marks appear as compared to other non-alphabetical characters from the same group is determinedby 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 characterset, will be sorted according to their underlying base characters, plus the collation weights of their accentsigns.

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

BGS3 AT Command Set 16.2 AT+CNUM


16.2 AT+CNUM Read own numbers

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

Syntax


Optional alphanumeric string associated with <number>.

Phone number in format specified by <type>.

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


may not yet be accessible, resulting in a short delay before the requested AT command response is returned.See Section 20.1, Restricted access to SIM data after SIM PIN authentication for furtherdetail.

Test Command

AT+CNUM=?Response(s)

OK

Exec Command

AT+CNUMResponse(s)

[+CNUM: [<alpha>], <number>, <type>][+CNUM: ... ]OKERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07

<alpha>(str)

<number>(str)

<type>(str)

BGS3 AT Command Set 16.3 AT+CPBR


16.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 formatinformation, the format list contains empty parenthesizes.

The AT+CPBR write command determines the phonebook entry to be displayed with <location1> or a locationrange 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


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. If <location1> exceeds the upper bound <maxloc> (as indicated by the test command), command willrespond with "+CME ERROR: invalid index".

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 willbe output but terminated with "+CME ERROR: invalid index". Note: The maximum value of <location2> is 255, regardless of the phonebook type and its range indicatedby <maxloc>. If a value greater than 255 is used the query returns no phonebook records, and only "+CMEERROR: invalid index" is shown.

Test Command

AT+CPBR=?Response(s)

+CPBR: (1-<maxloc>), <nlength>, <tlength>OKERROR+CME ERROR: <err>

Write Command

AT+CPBR=<location1>[, <location2>]Response(s)

[+CPBR: <location1>, <number>, <type>, <text>][+CPBR: <location2>, <number>, <type>, <text>]OKERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07, GSM 11.11

<location1>(num)

<location2>(num)



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

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, dependingon the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> ofAT+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 savedwith 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 assigned to a phone number. The maximum length for this parameter is given with test command responseparameter <tlength>. If using an ASCII terminal characters which are coded differently in ASCII and GSM have to be entered viaescape sequences as described in Section 1.6, Supported character sets.

Maximum location number for the currently selected storage. For phonebooks located on the SIM this valuedepends on the SIM card type.

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 thestandard length, which is 2*<nlength> digits for normal numbers, but only <nlength> digits for numberssaved with <type>=209.

Maximum length of <text> assigned to the telephone number. The value indicated by the test command isgiven 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 alphafield of the SIM according to GSM 11.11, Annex B [21]. In the worst case the number of UCS2 characters is atleast one less than half the number of GSM characters.



<number>(str)

<type>(num)

<text>(str)(+CSCS)

<maxloc>(num)

<nlength>(num)

<tlength>(num)



Example

AT+CPBR=? First run the AT+CPBR test command to find out themaximum range of entries stored in the activephonebook.

+CPBR:(1-100),20,17 BGS3 returns the supported values, where 100 is thesupported range of location numbers, 20 is thelength of the phone number and 17 is the maximumlength of the associated text.

AT+CPBR =1,3 Then use the AT+CPBR write command to displaythe phonebook entries sorted by location numbers. +CPBR:1,"+999999",145,"Charlie"

+CPBR:2,"+777777",145,"Bill" +CPBR:3,"+888888",145,"Arthur"

BGS3 AT Command Set 16.4 AT+CPBS


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

Syntax


“FD“ Fixed dialing phonebookCapacity: depending on SIMLocation: SIM

“SM“(&F)(P) SIM phonebookCapacity: depending on SIMLocation: SIM

“ON“ MSISDN listCapacity: depending on SIMLocation: SIM

“ME“ Mobile Equipment PhonebookCapacity: max. 250 entriesLocation: ME

Test Command

AT+CPBS=?Response(s)

+CPBS: (list of supported <storage>s)OKERROR+CME ERROR: <err>

Read Command

AT+CPBS?Response(s)

+CPBS: <storage>, <used>, <total>OKERROR+CME ERROR: <err>

Write Command

AT+CPBS=<storage>Response(s)



+ + + + + + - - GSM07.07

<storage>(str)

BGS3 AT Command Set 16.4 AT+CPBS


“LD“ Last number dialed phonebook. Stores all voice call numbers dialed with ATD,but no data call numbers.Capacity: max. 10 entriesLocation: MEAT+CPBW command is not applicable to this storage. The LD list can be deletedwith AT^SDLD or with AT^SPBD.

“MC“ Missed (unanswered received) calls listCapacity: max. 10 entriesLocation: MEAT+CPBW command is not applicable to this storage. The MC list can bedeleted with AT^SPBD.

“RC“ Received calls listCapacity: max. 10 entriesLocation: MEAT+CPBW command is not applicable to this storage. The RC list can bedeleted with AT^SPBD.

“VM“ CPHS voice mailbox phonebookCapacity: 1 or 2 entries, depending on SIM1 - Line 1 mailbox2 - Line 2 mailboxLocation: SIM

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

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


• If the SIM card is changed, all records of the "MC", "RC" and "LD" phonebooks stored on the ME will bedeleted automatically. If the same SIM is removed and reinserted, no automatic deletion is performed. Callsmade after last switch-on will be cleared from the "MC", "RC" and "LD" phonebook, if the SIM is removed andreinserted during normal operation.

• The following call history rule applies to the phonebook types "LD", "MC" and "RC": When the same number is dialed several times in direct succession the "LD" phonebook will store one singleentry. When dialed several times, but in a row with different numbers, the same number will be logged eachtime after dialing, resulting in double or multiple "LD" phonebook entries related to this number. The optional <text> in AT+CPBW write command must be stored in any phonebook when reading the<text> with AT+CPBR write command in the "LD" phonebook after having dialed with ATD or another dialcommand. Likewise, the "MC" or "RC" phonebook will store only a single entry when calls from the same number arereceived in direct succession, and double or multiple entries when calls from the same number are receivedseveral times, but amongst other incoming calls from different numbers.

<used>(num)

<total>(num)

BGS3 AT Command Set 16.5 AT+CPBW


16.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> ofthe active storage selected with AT+CPBS.If <storage>="FD" (SIM fixed dialing numbers) is selected, PIN2 authentication has to be performed prior toany write access.

The AT+CPBW test command returns the location range supported by the current storage, the maximum lengthof 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


Location number within phonebook memory. The maximum range supported by each storage type is indicatedin 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.

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

Test Command

AT+CPBW=?Response(s)

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

Write Command

AT+CPBW=[<location>][, <number>[[, <type>][, <text>]]]Response(s)



+ + + + + + - - GSM 07.07, GSM 04.08

<location>(num)

<number>(str)



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, dependingon 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 charactersother than "*", "#" or "+" are included in <number>.Note that phonebook entries saved with this type cannot be dialed.


129 Unknown number. If <type> is unknown and the <number> contains a lead-ing "+", <type>=145 (international) is used.

Text assigned to the phone number. The maximum length of this parameter is given in the test commandresponse <tlength>. When using an ASCII terminal, characters which are coded differently in ASCII and GSMhave to be entered via escape sequences as described in Section 1.6, Supported character sets.

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.

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 thestandard length, which is 2*<nlength> digits for normal numbers, but only <nlength> digits for numberssaved with parameter <type>= 209. If all extended locations of the selected phonebook are used up, then anyattempt to write a number which requires extended memory will be denied with "+CME ERROR: invalid dialstring".

Maximum length of <text> assigned to the telephone number. The value indicated by the test command isgiven 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 forthe alpha field of the SIM. In the worst case the number of UCS2 characters is at least one less than half thenumber of GSM characters.For a detailed description please refer to GSM 11.11, Annex B [21].



• During AT+CPBW write command it is possible that in some cases returns "+CME ERROR: operation tempo-rary not allowed". Use AT+CPBW write command again.

• After having used AT+CPBW write command it is possible that the external SIM memory for long dial stringsis full. It returns "+CME ERROR: dial string too long". Check the phonebook entry by using AT+CPBR readcommand.

<type>(num)

<text>(str)(+CSCS)

<maxloc>(num)

<nlength>(num)

<tlength>(num)



ExamplesEXAMPLE 1

Make a new phonebook entry at the first free location

EXAMPLE 2

Delete entry at location 1

EXAMPLE 3

The following examples are provided to illustrate the effect of writing phonebook entries with different typesof dial string modifiers in <number>

EXAMPLE 4

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

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

AT+CPBW=1

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"

+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"

BGS3 AT Command Set 16.6 AT^SPBW


16.6 AT^SPBW Write into Phonebook with location report

The AT^SPBW write command can be used to create, edit and delete a phonebook entry at a <location> ofthe active storage selected with AT+CPBS. After having written the phonebook entry <location> is shown.If <storage>="FD" (SIM fixed dialing numbers) is selected, PIN2 authentication has to be performed prior toany write access.

The AT^SPBW test command returns the location range supported by the current storage, the maximum lengthof 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


Location number within phonebook memory. The maximum range supported by each storage type is indicatedin 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.

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

Test Command

AT^SPBW=?Response(s)

^SPBW: (1-<maxloc>), <nlength>, (list of supported <type>s), <tlength>OKERROR+CME ERROR: <err>

Write Command

AT^SPBW=[<location>][, <number>[[, <type>][, <text>]]]Response(s)

^SPBW: <location>OKERROR+CME ERROR: <err>


+ + + + + + - - GSM 07.07, GSM 04.08

<location>(num)

<number>(str)



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, dependingon 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 charactersother than "*", "#" or "+" are included in <number>.Note that phonebook entries saved with this type cannot be dialed.


129 Unknown number. If <type> is unknown and the <number> contains a lead-ing "+", <type>=145 (international) is used.

Text assigned to the phone number. The maximum length of this parameter is given in the test commandresponse <tlength>. When using an ASCII terminal, characters which are coded differently in ASCII and GSMhave to be entered via escape sequences as described in Section 1.6, Supported character sets.

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.

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 thestandard length, which is 2*<nlength> digits for normal numbers, but only <nlength> digits for numberssaved with parameter <type>= 209. If all extended locations of the selected phonebook are used up, then anyattempt to write a number which requires extended memory will be denied with "+CME ERROR: invalid dialstring".

Maximum length of <text> assigned to the telephone number. The value indicated by the test command isgiven 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 forthe alpha field of the SIM. In the worst case the number of UCS2 characters is at least one less than half thenumber of GSM characters.For a detailed description please refer to GSM 11.11, Annex B [21].



• During AT^SPBW write command it is possible that in some cases returns "+CME ERROR: operation tempo-rary not allowed". Use AT^SPBW write command again.

• After having used AT^SPBW write command it is possible that the external SIM memory for long dial stringsis full. It returns "+CME ERROR: dial string too long". Check the phonebook entry by using AT+CPBR readcommand.

<type>(num)

<text>(str)(+CSCS)

<maxloc>(num)

<nlength>(num)

<tlength>(num)



ExamplesEXAMPLE 1

Make a new phonebook entry at the first free location (here location 3)

EXAMPLE 2

Delete entry at location 3

EXAMPLE 3

The following examples are provided to illustrate the effect of writing phonebook entries with different typesof dial string modifiers in <number>

EXAMPLE 4

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

AT^SPBW=,"+431234567",145,"international" ^SPBW: 3

AT^SPBW=3

AT^SPBW=5,"12345678",,"Arthur" ^SPBW: 5 AT^SPBW=6,"432!+-765()&54*654#",,"John" ^SPBW: 6 AT^SPBW=7,"432!+-765()&54*654#",129,"Eve" ^SPBW: 7 AT^SPBW=8,"432!+-765()&54*654#",145,"Tom" ^SPBW: 8 AT^SPBW=9,"432!+-765()&54*654#",209,"Richard" ^SPBW: 9

+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"

BGS3 AT Command Set 16.7 AT^SDLD


16.7 AT^SDLD Delete the 'last number redial' memory

AT^SDLD deletes all numbers stored in the "LD" memory.

Syntax



Test Command

AT^SDLD=?Response(s)

OK

Exec Command

AT^SDLDResponse(s)



+ + + + + + - -

BGS3 AT Command Set 16.8 AT^SPBC


16.8 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) entrythat matches the character specified with <schar>. The AT^SPBC test command returns the list of phonebookswhich 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 identicalwith the physical location numbers used in the various phonebooks. Therefore, do not use the index numbersretrieved with AT^SPBC to dial out or modify phonebook entries.

Syntax


Response parameter of AT^SPBC test command. For a detailed description of storages see AT+CPBS. “FD“ Fixed dialing phonebook “SM“ SIM phonebook“ME“ Mobile Equipment Phonebook

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

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 phonebookentry is found, <index>=0 will be returned.



Test Command

AT^SPBC=?Response(s)

^SPBC: (list of supported <storage>s)OKERROR+CME ERROR: <err>

Write Command

AT^SPBC=<schar>Response(s)

^spbc: <index>OKERROR+CME ERROR: <err>


+ + + + + + - -

<storage>(str)

<schar>(str)

<index>(num)

BGS3 AT Command Set 16.9 AT^SPBD


16.9 AT^SPBD Purge phonebook memory storage

AT^SPBD can be used to purge the selected phonebook <storage> manually, i.e. all entries stored in theselected 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 differentSIM card. This affects the ME based part of the "LD" storage, and storages "MC" and "RC". Storage "ME" is notaffected.

Syntax


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



Test Command

AT^SPBD=?Response(s)

^SPBD: (list of supported <storage>s)OKERROR+CME ERROR: <err>

Write Command

AT^SPBD=<storage>Response(s)



+ + + + + + - -

<storage>(str)

BGS3 AT Command Set 16.10 AT^SPBG


16.10 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 16.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 phonebooksAT^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 editingwith AT+CPBW or dialing with ATD><mem><n>. The first index number of each entry is only the serial numberof the sorted list.

Before using the AT^SPBG write command it is recommended to query the number of records currently stored inthe 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


First index number in the sorted list where to start reading. The supported range is given in the test commandresponse.If <index 1> exceeds the upper bound <used>, "+CME ERROR: invalid index" will be returned.

Last index number in the sorted list where to stop reading. The supported range is given in the test commandresponse.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 listof entries will be output and terminated with OK.If <index2> exceeds the range indicated by the test command parameter <used>, the list of entries will be

Test Command

AT^SPBG=?Response(s)

^SPBG: (1-<used>), <nlength>, <tlength>OKERROR+CME ERROR: <err>

Write Command

AT^SPBG=<index1>[, <index2>][, <RealLocReq>]Response(s)

[^SPBG: <index1>, <number>, <type>, <text>[, <location>]][^SPBG: <index2>, <number>, <type>, <text>[, <location>]]OKERROR+CME ERROR: <err>


+ + + + + + - -

<index1>(num)

<index2>(num)



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 bythe parameter <used>. If a value greater than 255 is used the query returns no phonebook records, and only"+CME ERROR: invalid index" is shown.

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. 1 Show the "real" location number as parameter <location> at the end of each

entry.

String type phone number in format specified by <type>.The number parameter may be an empty string.

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, dependingon the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> ofAT+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-



129 Otherwise

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

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

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

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.

<RealLocReq>(num)

<number>(str)

<type>(num)

<text>(str)(+CSCS)

<used>(num)

<location>(num)

<nlength>(num)



Maximum length of <text> assigned to the telephone number. The value indicated by the test command isgiven 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 forthe alpha field of the SIM according to GSM 11.11, Annex B [21]. 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


ExamplesEXAMPLE 1

Using AT^SPBG without <RealLocReq>:

The numbers at the beginning of each line are not the memory locations in the phonebook, but only serialnumbers assigned to the entries' positions in the alphabetical list.

EXAMPLE 2

Using AT^SPBG with <RealLocReq>:

The numbers at the end of each line are the memory locations in the phonebook and can be used for dialingor editing phonebook entries:

<tlength>(num)

AT^SPBG=? First run the AT^SPBG test command to find out therange of entries stored in the current phonebook.

^SPBG: (1-33),20,17 TA returns the range, where 33 is the number ofentries stored in the current phonebook.

AT^SPBG=1,33 Now, enter the write command. To obtain bestresults it is recommended to query the full range ofentries. TA returns phonebook entries in alphabeticalorder.

^SPBG:1,"+999999",145,"Arthur"^SPBG:2,"+777777",145,"Bill"^SPBG:3,"+888888",145,"Charlie"......................

AT^SPBG=? First run the AT^SPBG test command to find out therange of entries stored in the current phonebook.

^SPBG: (1-33),20,17 TA returns the range, where 33 is the number ofentries stored in the current phonebook.

AT^SPBG=1,33,1 Now, enter the write command including parameter<RealLocReq>=1 to get the actual location num-bers.

^SPBG:1,"+999999",145,"Arthur",27^SPBG:2,"+777777",145,"Bill",6^SPBG:3,"+888888",145,"Charlie",15......................

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

BGS3 AT Command Set 16.11 AT^SPBS


16.11 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 withthe next one. The actual index depends on parameter <value>. This parameter determines whether the indexwill 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 thefirst 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 canbe used for reading only. For example, it helps you find entries starting with matching characters. Do not usethe 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 editingwith AT+CPBW or dialing with ATD><mem><n>. The first index number of each entry is only the serial numberof the sorted list.

See examples below.

Syntax


1 To make a step forward in the alphabetically sorted phonebook.2 To make a step backward in the alphabetically sorted phonebook.

1...maxindex The index in the sorted list of phonebook entries that identifies the first entrydisplayed.The value of <index-a> is determined by the value of the <internal-counter> and by parameter <value>.

Test Command

AT^SPBS=?Response(s)

^SPBS: (list of supported <value>) OK

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>]OKERROR+CME ERROR: <err>


+ + + + + + - -

<value>(num)

<index-a>(num)



After a write command has terminated successfully with "OK", the value fromparameter <index-a> is saved and retained as the new <internal-counter> value.Mind after the last record of phonebook, the first entry follows.

1...maxindex The index in the sorted list of phonebook entries that identifies the second entrydisplayed.<index-b>= (<index-a>+1).Mind after the last record of phonebook, the first entry follows.

1...maxindex The index in the sorted list of phonebook entries that identifies the third entrydisplayed.<index-c>= (<index-b>+1).Mind after the last record of phonebook, the first entry follows.

String type phone number in format specified by <type>.the number parameter may be an empty string.

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, dependingon the network, not always possible (refer to GSM 04.08 subclause 10.5.4.7 for details). See also <type> ofAT+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-



129 Otherwise

Text assigned to the phone number.

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 1 Show the "real" location number as parameter <location> at the end of the

entry

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

<index-b>(num)

<index-c>(num)

<number>(str)

<type>(num)

<text>(str)(+CSCS)

<RealLocReq>(num)

<location>(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


ExamplesEXAMPLE 1

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

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.

<internal-counter>(num)

at&f First, AT&F is issued to make sure that AT^SPBS=1starts from the first character in alphabetical order.OK

at^spbs=1^SPBS:1,"+999999",145,"Arthur"^SPBS:2,"+777777",145,"Bill"^SPBS:3,"+888888",145,"Charlie"

OK at^spbs=1^SPBS:2,"+777777",145,"Bill"^SPBS:3,"+888888",145,"Charlie"^SPBS:4,"0304444444",129,"Esther"

OK at^spbs=1^SPBS:3,"+888888",145,"Charlie"^SPBS:4,"0304444444",129,"Esther"^SPBS:5,"03033333333",129,"Harry"

OK at^spbs=2^SPBS:2,"+777777",145,"Bill"^SPBS:3,"+888888",145,"Charlie"^SPBS:4,"0304444444",129,"Esther"

OK

at&f Reset internal counter to 0.OKat^spbs=2 Step down one entry starting from (internal

counter)=0 - overflow occurs.^SPBS:33,"+49301234567",145,"TomTailor"^SPBS:1,"+999999",145,"Arthur"^SPBS:2,"+777777",145,"Bill"

OK



EXAMPLE 3

Using AT^SPBS with <RealLocReq>=1 in order to obtain the entries' location numbers:

The numbers at the end of each line are the memory locations in the phonebook and can be used for dialingor editing phonebook entries:

at^spbs=1,1

^SPBS:1,"+999999",145,"Arthur",27^SPBS:2,"+777777",145,"Bill",6^SPBS:3,"+888888",145,"Charlie",15

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

BGS3 AT Command Set 17. Audio Commands


17. Audio Commands

The AT Commands described in this chapter are related to the BGS3's audio interface.

17.1 Audio programming model

The following figure illustrates how the signal path can be adjusted with the parameters <inCalibrate>,<inBbcGain>, <outBbcGain>, <outCalibrate> and <sideTone> as well as <io>, <mic> and <ep>.

Figure 17.1: Audio programming model for BGS3 Module

BGS3 AT Command Set 17.2 ATL


17.2 ATL Set monitor speaker loudness

ATL is implemented for V.250ter compatibility reasons only, and has no effect. In multiplex mode (referAT+CMUX) the command is supported on logical channel 1 only.

Syntax


17.3 ATM Set monitor speaker mode

ATM is implemented for V.250ter compatibility reasons only, and has no effect. In multiplex mode (referAT+CMUX) the command is supported on logical channel 1 only.

Syntax


Exec Command

ATL[<val>]Response(s)



- + - + - - - - V.250

<val>(num)

Exec Command

ATM[<val>]Response(s)



- + - + - - - - V.250

<val>(num)

BGS3 AT Command Set 17.4 AT+CLVL


17.4 AT+CLVL Loudspeaker volume level

Syntax


Loudspeaker Volume Level0...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 withAT+CFUN=1,1.

Test Command

AT+CLVL=?Response(s)

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

Read Command

AT+CLVL?Response(s)

+CLVL: <level>OKERROR+CME ERROR: <err>

Write Command

AT+CLVL=<level>Response(s)



- + + + + + - - GSM 07.07

<level>(num)

BGS3 AT Command Set 17.5 AT+CMUT


17.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),during a voice call only. See AT^SNFS for more details on the various audio modes. As alternative, you can usethe 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 untilexplicitly changed.

Syntax


0(P) Mute off1 Mute on

Test Command

AT+CMUT=?Response(s)

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

Read Command

AT+CMUT?Response(s)

+CMUT: <mute>OKERROR+CME ERROR: <err>

Write Command

AT+CMUT=<mute>Response(s)



- + + + + + - - GSM 07.07

<mute>(num)

BGS3 AT Command Set 17.6 AT+VTD


17.6 AT+VTD Tone duration

This command refers to an integer <duration> that defines the length of tones transmitted with the AT+VTScommand.

Syntax


Duration of the DTMF signal in 1/10 seconds with tolerance. The minimum duration of DTMF signals is 300ms. 1(&F)(P)...255

Test Command

AT+VTD=?Response(s)

+VTD: (list of supported<duration>s)OK

Read Command

AT+VTD?Response(s)

<duration>OKERROR+CME ERROR: <err>

Write Command

AT+VTD=<duration>Response(s)



- + + + + + - - GSM 07.07

<duration>(num)

BGS3 AT Command Set 17.7 AT+VTS


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


String of ASCII characters in the set 0-9,#,*,A, B, C, D. Maximal length of the string is 29. The string must beenclosed in quotation marks ("...").

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

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

Test Command

AT+VTS=?Response(s)

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

Write Command

AT+VTS=<dtmfString>Response(s)


Write Command

AT+VTS=<dtmf>[, <duration>]Response(s)



- + + + + + - - GSM 07.07

<dtmfString>(str)

<dtmf>(str)

<duration>(num)

BGS3 AT Command Set 17.8 AT^SAIC


17.8 AT^SAIC Audio Interface Configuration

AT^SAIC configures the interface connections of the active audio mode. The write command is usable in audiomodes 2 to 6 only. If AT^SNFS=1, any attempt to use AT^SAIC write command is rejected with error response. This is because alldefault 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 andthen choose the interface using AT^SAIC.

Syntax


Input and output selection1 Digital input and output2 Analog input and output

Microphone selection1 Microphone 12 Microphone 2

Select differential earpiece amplifier1 Selects the earpiece amplifier 1

Test Command

AT^SAIC=?Response(s)

^SAIC:(list of supported <io>s), (list of supported<mic>s), (list of supported<ep>s), (list of supported<clock>s), (list of supported<mode>s), (list of supported<frame_mode>s)OK

Read Command

AT^SAIC?Response(s)

^SAIC: <io>, <mic>, <ep>, <clock>, <mode>, <frame_mode>OKERROR+CME ERROR: <err>

Write Command

AT^SAIC=<io>[, <mic>[, <ep>][, <clock>, <mode>, <frame_mode>]]Response(s)



- + + + + + - -

<io>(num)(^SNFW)

<mic>(num)(^SNFW)

<ep>(num)(^SNFW)

BGS3 AT Command Set 17.8 AT^SAIC


2 Selects the earpiece amplifier 2 3 Selects both amplifiers. Note that both amplifiers are connected in parallel and

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

Parameter is mandatory if <io>=1 (digital). 0 256kHz clock1 512kHz clock

Parameter is mandatory if <io>=1 (digital). 0 Master mode1 Slave mode

Parameter is mandatory if <io>=1 (digital). 0 Short frame1 Long frame

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,0,0,0. If AT^SNFS=2 or 3 or 6, then AT^SAIC=2,2,2,0,0,0. 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 audioprofile saved with AT^SNFW. Otherwise, audio mode 1 (AT^SNFS=1) and audio interface 2(AT^SAIC=2,1,1,0,0,0) will be active each time the ME is powered up.

• The parameters <clock>, <mode> and <frame_mode> are mandatory, if parameter <io> is set to 1 (digi-tal). These parameters can be used to configure the PCM functionality over the digital audio interface (DAI).The PCM interface supports master or slave mode, short frame or long frame synchronization and 256 kHzor 512 kHz bit clock frequency. In slave mode the clock frequency setting has no influence, because of theBCLKIN signal being directly used for data shifting. The setting may therefore be either 0 or 1. The table belowlists possible configuration combinations.

<clock>(num)(^SNFW)

<mode>(num)(^SNFW)

<frame_mode>(num)(^SNFW)

Configuration <clock> <mode> <framemode>Master, 256kHz, short frame 0 0 0Master, 256kHz, long frame 0 0 1Master, 512kHz, short frame 1 0 0Master, 512kHz, long frame 1 0 1Slave, 256kHz, short frame 0 or 1 1 0Slave, 256kHz, long frame 0 or 1 1 1Slave, 512kHz, short frame 0 or 1 1 0Slave, 512kHz, long frame 0 or 1 1 1

BGS3 AT Command Set 17.9 AT^SNFA


17.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 selectedwith AT^SNFS. The write command is only available in audio modes 2 to 6.

Syntax


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)...655350 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 returnedonly by the read command AT^SNFA? after the microphone was muted withAT^SNFM=0 during an active call.

32767 No attenuation on the microphone pathValues 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.

Test Command

AT^SNFA=?Response(s)

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

Read Command

AT^SNFA?Response(s)

^SNFA: <atten>OKERROR+CME ERROR: <err>

Write Command

AT^SNFA=<atten>Response(s)



- + + + + + - -

<atten>(num)(^SNFW)

BGS3 AT Command Set 17.9 AT^SNFA


Example

^SYSSTARTat^snfa=?^SNFA: (0-65535)OKat^snfa?^SNFA: 32767OKat^snfs=4OKat^snfa=1OKat^snfa?^SNFA: 1OKat^snfi?^SNFI: 5,1OKat^snfi=5,45OKat^snfa?^SNFA: 45OK

BGS3 AT Command Set 17.10 AT^SNFD


17.10 AT^SNFD Set audio parameters to manufacturer default values

AT^SNFD sets the active audio parameters to manufacturer defined default values. These default values can bechanged and stored by the user and also by download with a new set of parameters.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

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 inaudio modes 2 - 6. This means, if <audMode>=1, the read commands AT^SNFO, AT^SNFV and AT+CLVL willalways deliver <outStep>=4. In all other modes the <outStep> value is retained until explicitly changed.

Test Command

AT^SNFD=?Response(s)

OK

Exec Command

AT^SNFDResponse(s)



- + + + + + - -

BGS3 AT Command Set 17.11 AT^SNFG


17.11 AT^SNFG Generate Tone

The AT^SNFG write command generates a 'local tone' via the selected audio output device.Beside the duration up to 3 combinations of frequency and amplitude can be used to compose a local tone.

Syntax


in Milliseconds.0...655350 Mutes the currently played tone immediately.65535 Activates a tone with infinit duration.

in Hertz200...3400to be input in 1 Hz steps. Audible bandwidth is limited due to the voice band filters.

of the tone generator belonging to a frequency. 0...100The output level at the speaker is dependent of the <outBbcGain> value (see AT^SNFO).If more than one tone should be played, each amplitude level will be divided by the number of running tones toavoid overdriving of the internal amplifier. For example, if three tones with amplitude of 30 units should be gen-erated each amplitude is reduced to 10. Setting of amplitude to 100 corresponds with using of current <outB-bcGain> value (see AT^SNFO), 0 is mute.

Test Command

AT^SNFG=?Response(s)

^SNFG:(list of supported <duration>s), (list of supported <frequency>s), (list of supported <amplitude>s)[, ...]OK

Write Command

AT^SNFG=<duration>, <frequency>, <amplitude>[, <frequency>, <amplitude>[, <frequency>, <amplitude>]]Response(s)



- + + + + + - -

<duration>(num)

<frequency>(num)

<amplitude>(num)

BGS3 AT Command Set 17.11 AT^SNFG


Notes• Response of the command is always "OK" as long as the input parameters are valid. • If more than one pair of <frequency> and <amplitude> is used then the amplitude for each frequency is

devided by the number of pairs. • Tone priorities

Ring tones (incoming call/short message), Supervisory tones,Call Progress tones, Battery tones, RTC tonesand DTMF tones always have higher priority than a local tone. This means a local tone will be played only ifno module tone with a higher priority is being played. A local tone will be stopped and ended when a tone ormelody from the module starts to play.

• To suspend a local tone from playing use "AT^SNFG=0". • Switching the tone generator on and off will trigger AT+CIND indicator "sounder" depending on current

AT+CMER settings. • If there is a voice call active then the local tone is mixed into the voice signal. In case of a multi party call the

local tones are not available.

BGS3 AT Command Set 17.12 AT^SNFI


17.12 AT^SNFI Set microphone path parameters

AT^SNFI controls the microphone path amplification. Read and write options of this command refer to the activeaudio mode. The write command works only in audio modes 2 to 6.

Syntax


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

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!

Test Command

AT^SNFI=?Response(s)

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

Read Command

AT^SNFI?Response(s)

^SNFI: <inBbcGain>, <inCalibrate>OKERROR+CME ERROR: <err>

Write Command

AT^SNFI=<inBbcGain>, <inCalibrate>Response(s)



- + + + + + - -

<inBbcGain>(num)(^SNFW)

<inCalibrate>(num)(^SNFW)

BGS3 AT Command Set 17.13 AT^SNFM


17.13 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 BGS3 Module. The microphone can be muted or activated by changing <MicSwitch> in all audio modes (1 to 6), during a voicecall only. As an alternative, you can use the AT+CMUT command to mute the microphone.

Syntax


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. 0 Mutes the microphone.1(P) Activates the microphone.

Microphone supply voltage control parameter. Controls the power supply VMIC of the two microphone inputs ofthe BGS3 Module. CME error is given if <MicSwitch> is not omitted. Enter for example AT^SNFM=,1 or AT^SNFM=,2. 0 Supply voltage is always switched off. 1 Supply voltage is always switched on. 2(P) Supply voltage state during voice calls is controlled by the ME. The actual

value is determined by the parameter data set of the selected audio mode.

Test Command

AT^SNFM=?Response(s)

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

Read Command

AT^SNFM?Response(s)

^SNFM: <MicSwitch>, <MicVccState>OKERROR+CME ERROR: <err>

Write Command

AT^SNFM=[<MicSwitch>][, <MicVccCtl>]Response(s)



- + + + + + - -

<MicSwitch>(num)

<MicVccCtl>(num)

BGS3 AT Command Set 17.13 AT^SNFM


Microphone supply voltage control status. 0 Supply voltage was set to a constant value. 2 Supply voltage state is controlled by the ME and depends on the 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 ofthe extended usage of the analog audio interfaces can be found in [8].

• During an active call, users should be aware that when they switch back and forth between different audiomodes (for example handsfree on/off) the value of <MicSwitch> does not change, i.e. the microphone modeis retained until explicitly changed.

<MicVccState>(num)

BGS3 AT Command Set 17.14 AT^SNFO


17.14 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


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

Formula to calculate the value of the 5 volume steps selectable with parameter <outStep>:Attenuation = 20 * log (2 * outCalibrate[n] / 32768)0...32767

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

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)OK

Read Command

AT^SNFO?Response(s)

^SNFO: <outBbcGain>, <outCalibrate>[0] , <outCalibrate>[1] , <outCalibrate>[2] , <outCalibrate>[3] , <outCalibrate>[4] , <outStep>, <sideTone>OKERROR+CME ERROR: <err>

Write Command

AT^SNFO=<outBbcGain>, <outCalibrate>[0] , <outCalibrate>[1] , <outCalibrate>[2] , <outCalibrate>[3] , <outCalibrate>[4] , <outStep>, <sideTone>Response(s)



- + + + + + - -

<outBbcGain>(num)(^SNFW)

<outCalibrate>(num)(^SNFW)

<outStep>(num)

BGS3 AT Command Set 17.14 AT^SNFO


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

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 causean 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> andthen select another mode with AT^SNFS, the same step will be applied. Nevertheless, the sound quality andthe amount of volume are not necessarily the same, since all remaining audio parameters can use differentvalues in either mode.

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

• The value of <outStep> is stored non-volatile when the ME is powered down with AT^SMSO or reset withAT+CFUN=x,1. Any other parameters changed with AT^SNFO need to be saved with AT^SNFW for use afterrestart. 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!

<sideTone>(num)(^SNFW)

BGS3 AT Command Set 17.15 AT^SNFPT


17.15 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


0 Disables Call Progress Tones1(P) Enables Call Progress Tones (audible tones shortly heard on the phone when

ME starts to set up a call.)

Test Command

AT^SNFPT=?Response(s)

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

Read Command

AT^SNFPT?Response(s)

^SNFPT: <pt>OKERROR+CME ERROR: <err>

Write Command

AT^SNFPT=<pt>Response(s)



- + + + + + - -

<pt>(num)

BGS3 AT Command Set 17.16 AT^SNFS


17.16 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 areoperated 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 finallyenter AT^SNFW to store the settings to your audio profile. To switch back and forth it is sufficient to use AT^SNFS.

Syntax


1(P) Audio mode 1: Standard mode optimized for the reference handset, that canbe connected to the analog interface 1 (see "BGS3 Hardware InterfaceDescription" for information on this handset.) To adjust the volume use theknob of the reference handset. In audio mode 4, this handset can be used withuser defined parameters. Note: The default parameters are determined for type approval and are notadjustable with AT commands. AT^SNFD restores <audMode> 1.

2 Audio mode 2: Customer specific mode for a basic handsfree (speakerphone)device (Siemens Car Kit Portable).Analog interface 2 is assumed as default.

3 Audio mode 3: Customer specific mode for a mono-headset.Analog interface 2 is assumed as default.

4 Audio mode 4: Customer specific mode for a user handset.Analog interface 1 is assumed as default.

Test Command

AT^SNFS=?Response(s)

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

Read Command

AT^SNFS?Response(s)

^SNFS: <audMode>OKERROR+CME ERROR: <err>

Write Command

AT^SNFS=<audMode>Response(s)



- + + + + + - -

<audMode>(num)(^SNFW)



5 Audio mode 5: Customer specific mode. Analog interface 1 is assumed as default.

6 Audio mode 6: Customer specific mode.Analog interface 2 is assumed as default.

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 setwith AT^SNFM or AT+CMUT: If the microphone is muted and the user selects another audio mode during thecall, then the microphone remains muted until explicitly changed. Exception: In audio mode 1 <outStep>=4is fix.

• For use after restart of the module, you are advised to store the selected mode to the audio profile saved withAT^SNFW. Otherwise, audio mode 1 will be active each time the module is powered up.

• Users should be aware that when using this AT command quickly after "^SYSSTART" a "+CME ERROR:operation temporary not allowed" is received. The audio data may not yet be accessible, resulting in a shortdelay (less than 400ms) before the requested AT command response is returned.

ExamplesEXAMPLE 1

Suppose a user wishes to use alternatively a handsfree device (speakerphone) and a handset. The handsetcan be connected to the first analog interface and adjusted to audio mode 4. The handsfree device can beattached to the second analog interface and adjusted to audio mode 2. The factory defaults of AT^SAIC neednot be changed.Settings for the handset:

Settings for the handsfree device:

To store the configuration to the user defined audio profile:

To switch back and forth:

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=4OKAT^SAIC? Factory default of AT^SAIC assigned to audio mode 4.^SAIC: 2,1,1OK

AT^SNFS=2OKAT^SAIC? Factory default of AT^SAIC assigned to audio mode 2.^SAIC: 2,2,2OK

AT^SNFW Stores the audio mode and the interface.OK

AT^SNFS=4 Switches to the handset connected to analog interface 1.OKAT^SNFS=2 Switches to the handsfree device at analog interface 2.OK

AT^SNFS=4OK



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

To store the configuration to the user defined audio profile:

To switch back and forth:

AT^SAIC=2,2,2OK

AT^SNFS=2OKAT^SAIC=2,1,1OK

AT^SNFW Stores the audio mode and the interface.OK

AT^SNFS=4 Switches to the handset connected to analog interface 1.OKAT^SNFS=2 Switches to the handsfree device at analog interface 2.OK

BGS3 AT Command Set 17.17 AT^SNFTTY


17.17 AT^SNFTTY Signal TTY/CTM audio mode capability

BGS3 offers basic support for equipment using the CTM standard (Cellular Text Telephone Modems). The ben-efit of CTM is that text characters typed on a TTY device (Text Telephone Type-writer) can be transformed intospecial 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) callsand incoming calls with this bearer capability bit set are accepted. The TE needs to decode the special audioburst signals. If CTM mode is disabled, the ME will clear the bearer capability bit on mobile originated calls and incoming callswith the bearer capability bit set are rejected because the BGS3 expects that CTM coded speech data cannotbe decoded by the TE. Designed to set the module's speech system into CTM mode, the AT^SNFTTY command allows a CTM deviceto be connected to one of the three audio interfaces of BGS3. Traditional TTY devices that do not incorporateCTM 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 3GPPTS 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 connectTTY/CTM equipment to the BGS3.

Requirements for using TTY/CTM features:• The TTY/CTM functionality requires audio mode 5 or 6 which is set by AT^SNFS. When the appropriate audio

settings are enabled you may select either AT^SNFTTY=1 or 2. • Depending on which audio interface the CTM device is connected to, select the appropriate settings via

AT^SAIC.

Syntax


0(P) Audio path is in normal speech mode.

Test Command

AT^SNFTTY=?Response(s)

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

Read Command

AT^SNFTTY?Response(s)

^SNFTTY: <audioState>OKERROR+CME ERROR: <err>

Write Command

AT^SNFTTY=<audioState>Response(s)



- + + + + + - -

<audioState>(num)

BGS3 AT Command Set 17.17 AT^SNFTTY


1 Audio path is in TTY/CTM mode (external CTM modem).2 Audio path is in TTY/CTM mode (internal CTM modem).

BGS3 AT Command Set 17.18 AT^SNFV


17.18 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 audiomodes 2 to 6.

Syntax


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 canbe quite different, depending on the values of <outCalibrate> set in each mode. The only exception isaudio 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 17.14) and AT+CLVL (Section 17.4). • Users should be aware that when using this AT command quickly after "^SYSSTART" a "+CME ERROR:

operation temporary not allowed" is received. The audio data may not yet be accessible, resulting in a shortdelay (less than 400ms) before the requested AT command response is returned.

Test Command

AT^SNFV=?Response(s)

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

Read Command

AT^SNFV?Response(s)

^SNFV: <outStep>OKERROR+CME ERROR: <err>

Write Command

AT^SNFV=<outStep>Response(s)



- + + + + + - -

<outStep>(num)

BGS3 AT Command Set 17.19 AT^SNFW


17.19 AT^SNFW Write audio setting in non-volatile store

AT^SNFW causes the TA to write the currently selected audio parameters to non-volatile store. The saved audioprofile includes the following parameters: AT^SNFA: <atten> AT^SNFI: <inBbcGain>, <inCalibrate> AT^SNFO: <outBbcGain>, <outCalibrate>[0 to 4], <sideTone> AT^SNFS: <audMode> AT^SAIC: <io>, <mic>, <ep>.

SyntaxTest Command

AT^SNFW=?Response(s)

OK

Exec Command

AT^SNFWResponse(s)



- + + + + + - -

BGS3 AT Command Set 17.20 AT^SRTC


17.20 AT^SRTC Ring tone configuration

The AT^SRTC read command returns the current <type> and current <volume>. The read command can beused while test playback is off or on. In the latter case, see execute command for details.

The AT^SRTC execute command is intended only for testing. It starts to play a melody from the audio output cur-rently 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 statusof playback (on / off).

The AT^SRTC write command chooses the type and volume of ring tones. The selected <type> and <volume>are stored non-volatile. The only exception is <type>=0 which is not stored because it is intended only to quicklymute the tone currently played. So <type>=0 only stops immediately the audible ring tone, but does not termi-nate the RING URC.

SyntaxTest Command

AT^SRTC=?Response(s)

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

Read Command

AT^SRTC?Response(s)

^SRTC: <type>, <volume>, <status>OKERROR+CME ERROR: <err>

Exec Command

AT^SRTCResponse(s)


Write Command

AT^SRTC=[<type>][, <volume>]Response(s)

^SRTC: <type>, <volume>OKERROR+CME ERROR: <err>


- + + + + + - -

BGS3 AT Command Set 17.20 AT^SRTC



Type of ring tone. You have a choice of 7 different ring tones and melodies. All will be played from the audiooutput selected with the AT^SNFS command. <type>=0 is only intended for muting. 0 Mutes the currently played tone immediately. 1 Sequence 1 2 Sequence 2 3(D) Sequence 3 4 Sequence 4 5 Sequence 5 6 Sequence 6 7 Sequence 7

Volume of ring tone, varies from low to high 0(D) Mute 1 Very low 2 Identical with 1 3 Low 4 Identical with 3 5 Middle 6 Identical with 5 7 High

Status of test ringing. Indicates whether or not a melody is currently being played back for testing 0 Switched off 1 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, factorysetting is AT^SRTC=3,0,0 (ring tones are muted). To activate ring tones for the very first time, first enter thewrite command and simply change the volume. After applying a firmware update the volume and typeselected before the firmware update will be preserved.

• If the <type> is changed while a call is ringing (RING URC) or active, the ME returns OK, but the new melodydoes not take effect until after the call has ended.

• Users should be aware that when using this AT command quickly after "^SYSSTART" a "+CME ERROR:operation temporary not allowed" is received. The audio data may not yet be accessible, resulting in a shortdelay (less than 400ms) before the requested AT command response is returned.

<type>(num)

<volume>(num)

<status>(num)

BGS3 AT Command Set 18. Hardware related Commands


18. Hardware related Commands

All AT commands described in this chapter are related to the hardware interface of the BGS3. Further informationregarding this interface is available in the "BGS3 Hardware Interface Description" [2].

18.1 AT+CCLK Real Time Clock

Syntax


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 BGS3 is restarted it takes 2s to re-initialize the RTC and to update the current time.

Test Command

AT+CCLK=?Response(s)

OK

Read Command

AT+CCLK?Response(s)

+CCLK: <time>OK

Write Command

AT+CCLK=<time>Response(s)



- + + + + + + - GSM 07.07

<time>(str)

BGS3 AT Command Set 18.2 AT^SBC


18.2 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 themodule switches off. The automatic shutdown caused by undervoltage or overvoltage is equivalent to thepower-down initiated with the AT^SMSO command, i.e. ME logs off from the network and the software entersa 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 ratingsplease 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 BGS3 works only if the requirementsdescribed 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 doesnot incorporate an NTC, or the battery and the NTC are not compliant with the specified requirements thebattery cannot be detected by BGS3.

Syntax


URC 1

^SBC: Undervoltage

The message will be reported, for example, when the user attempts to set up a call while the voltage is closeto 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 moduleswitches off.In applications which are not battery operated, i.e. where no NTC is connected to the BATT_TEMP pin, BGS3will present the undervoltage URC only once and will then switch off without sending any further messages.

Test Command

AT^SBC=?Response(s)

^SBC:(list of supported <bcs>s), (list of supported <bcl>s), (list of supported <mpc>s)OK

Read Command

AT^SBC?Response(s)

^SBC: <bcs>, <bcl>, <mpc>OKERROR+CME ERROR: <err>

Write Command

AT^SBC=<current>Response(s)



- + + + + + ± -



URC 2

^SBC: Overvoltage warning

This URC is an alarm indicator displayed when the supply voltage approaches its maximum level. The URCappears only once.

URC 3

^SBC: Overvoltage shutdown

This URC will be reported when the voltage exceeds the maximum level specified in the Hardware InterfaceDescription [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 examplecaused 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.


Connection status of battery pack0 No charging adapter is connected1 Charging adapter is connected2 Charging adapter is connected, charging in progress3 Charging adapter is connected, charging has finished4 Charging error, charging is interrupted5 False charging temperature, charging is interrupted while temperature is

beyond allowed range

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. "100" indicates a remain-ing capacity between 81 and 100 percent, "80" indicates 61 ... 81 percent, and so on.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.

Current consumption of the host application as specified with parameter <current>.

0(P)...5000 Enter the current consumption of your host application in mA. This informationenables BGS3 to correctly determine the end of charging and terminate charg-ing automatically when the battery is fully charged. Note that if <current> isinaccurate, and the application draws a current higher than the final chargecurrent, either charging will not be terminated or the battery fails to reach itsmaximum voltage. Therefore, the termination condition is defined as: currentconsumption dependent on operating mode of the ME plus current consump-tion of the external application. If used, the current flowing over the VEXT pinof the application interface must be added, too. The specified value will also be displayed as parameter <mpc> of the AT^SBCread command. When the BGS3 is powered down or reset, the value of <current> is restoredto its default. This affects the charging control. Therefore, the parameter shouldbe set every time when needed after rebooting the BGS3.

<bcs>(num)

<bcl>(num)

<mpc>(num)

<current>(num)



Notes• If multiplex mode (AT+CMUX) is active, any virtual channel can be used for entering the read or write com-

mand. The undervoltage URC will be issued simultaneously on all three channels. • Another URC type required for battery powered applications is the URC "^SYSSTART CHARGE ONLY MODE".

It is indicated automatically when the module enters this mode (except when autobauding is active). SeeAT+CFUN for details.

18.2.1 Responses returned by read command

Responses returned by the AT^SBC read command vary with the operating mode of the BGS3:• Normal mode: BGS3 is switched on by Ignition pin and running in SLEEP, IDLE, TALK or DATA mode.

Charger is not connected. The AT^SBC read command indicates the battery capacity and the current con-sumption of the application (if value of application was specified before as <current>).

• Normal mode + charging: Allows charging while BGS3 is switched on by Ignition pin and running in SLEEP,IDLE, TALK or DATA mode. The AT^SBC read command returns only charger status and current consump-tion of the application. Percentage of battery capacity is not available.

• CHARGE ONLY mode: Allows charging while BGS3 is detached from GSM network. When started, the modeis indicated by the URC "^SYSSTART CHARGE ONLY MODE". The AT^SBC read command returns only thecharger status and current consumption of the application. Percentage of battery capacity is not available. InCHARGE ONLY mode a limited number of AT commands is accessible (see Appendix). There are severalways to activate the CHARGE ONLY mode: - from POWER DOWN mode: Connect charger while the BGS3 was powered down with AT^SMSO- from Normal mode: Connect charger, then enter AT^SMSO.

BGS3 AT Command Set 18.3 AT^SBV


18.3 AT^SBV Battery/Supply Voltage

The AT^SBV execute command allows to monitor the supply (or battery) voltage of the module. The voltage iscontinuously measured at intervals depending on the operating mode of the RF interface. The duration of a mea-surement period ranges from 0.5s in TALK / DATA mode up to 50s when BGS3 is in IDLE mode or Limited Ser-vice (deregistered). The displayed value is averaged over the last measuring period before the AT^SBVcommand was executed.

The measurement is related to the reference points of BATT+ and GND. For details on the reference pointsplease refer to the Hardware Interface Description [2].

Syntax


Supply (or battery) voltage in mV

Test Command

AT^SBV=?Response(s)


Exec Command

AT^SBVResponse(s)

^SBV: <value>OKERROR+CME ERROR: <err>


- + + + + + + -

<value>(num)

BGS3 AT Command Set 18.4 AT^SCTM


18.4 AT^SCTM Critical Operating Temperature Monitoring

AT^SCTM allows to monitor the operating temperature range of the BGS3 device and a connected battery. Referto "BGS3 Hardware Interface Description" [2] for specifications on critical temperature ranges. AT^SCTM write command controls the presentation of URCs to report critical operating temperature limits.Use parameter <UrcMode> to enable (1) and disable (0) URC presentation. Important: Even if setting is <UrcMode>=0 URC presentation is enabled during the two minute guard periodafter the module was switched on. After expiry of the two minute guard period, the presentation will be disabled,i.e. no URCs with alert levels "1" or ''-1" will be generated. During this period BGS3 will not switch off, even if thecritical temperature limit is exceeded. This allows the TA to setup emergency calls before BGS3 switches off. Fordetails refer to Section 18.4.1, Deferred shutdown. To avoid damage the module will shut down once the critical temperature is exceeded.The procedure is equivalent to the power-down initiated with AT^SMSO.

Level "2" or "-2" URCs are followed by immediate shutdown, except in cases described in Section 18.4.1,Deferred shutdown. The presentation of these URCs is always enabled, i.e. they will be output even though thefactory setting AT^SCTM=0 was never changed. URCs indicating alert levels "1" or "-1" are intended to enablethe TA to take appropriate precautions, such as protect BGS3 and a connected battery from exposure to extremeconditions, or save or back up data etc.

AT^SCTM read command returns: • The URC presentation mode.• Information about the current temperature range of the BGS3 device.• The board temperature (in degree Celsius) if parameter <tempCtrl>=1.Please note that the read command does not indicate the temperature range of the battery. The battery temper-ature can only be reported by an Unsolicited Result Code.

SyntaxTest Command

AT^SCTM=?Response(s)

^SCTM:(list of supported <UrcMode>s)[, (range of <temp>in Celsius)]OK

Read Command

AT^SCTM?Response(s)

^SCTM: <UrcMode>, <UrcCause>[, <temp>]OKERROR+CME ERROR: <err>

Write Command

AT^SCTM=<UrcMode>[, <tempCtrl>]Response(s)



- + + + + + + -




URC 1

URCs will be automatically sent to the TA when the temperature reaches or exceeds the critical level, or whenit is back to normal. ^SCTM_A: <UrcCause>

URC for battery temperature warning.

URC 2

^SCTM_B: <UrcCause>

URC for BGS3 device temperature warning.


URC presentation mode. Setting will not be stored during power-down, i.e. after next restart default setting willbe restored. 0(&F)(P) Disable URC presentation (except for <UrcCause> equal to -2 or +2). 1 Enable URC presentation.

-2 Below lowest temperature limit (causes immediate switch-off) -1 Below low temperature alert limit0 Normal operating temperature1 Above upper temperature alert limit2 Above uppermost temperature limit (causes immediate switch-off)

0(&F)(P) Suppress output of <temp> in read command.1 Output <temp> in test and read command.

Board temperature in Celsius. Is comprised between the lowest temperature warning level and the uppermosttemperature warning level.

ExamplesEXAMPLE 1

URCs issued when the operating temperature is out of range:

EXAMPLE 2

URCs issued when the temperature is back to normal (URC is output once):

<UrcMode>(num)

<UrcCause>(num)

<tempCtrl>(num)

<temp>(num)

^SCTM_A: 1 Caution: Battery close to overtemperature limit. ^SCTM_A: 2 Alert: Battery above overtemperature limit. Engine switches off. ^SCTM_B: 1 Caution: Module close to overtemperature limit. ^SCTM_B: 2 Alert: Module is above overtemperature limit and switches off. ^SCTM_A: -1 Caution: Battery close to undertemperature limit. ^SCTM_A: -2 Alert: Battery below undertemperature limit. Engine switches off.^SCTM_B: -1 Caution: Module close to undertemperature limit. ^SCTM_B: -2 Alert: Module is below undertemperature limit and switches off.



18.4.1 Deferred shutdown

In the following cases, automatic shutdown will be deferred if a critical temperature limit is exceeded: • while an emergency call is in progress • during a two minute guard period after powerup. This guard period has been introduced in order to allow for

the user to make an emergency call. The start of any one of these calls extends the guard period until the endof the call. Any other network activity may be terminated by shutdown upon expiry of the guard time.

While in a "deferred shutdown" situation, the engine continues to measure the temperature and to deliver alertmessages, but deactivates the shutdown functionality. Once the guard period is expired or the call is terminated,full temperature control will be resumed. If the temperature is still out of range, ME switches off immediately (with-out another alert message).CAUTION! Automatic shutdown is a safety feature intended to prevent damage to the module. Extended usageof the deferred shutdown facilities provided may result in damage to the module, and possibly other severe con-sequences.

^SCTM_A: 0 Battery temperature back to normal temperature. ^SCTM_B: 0 Module back to normal temperature.

BGS3 AT Command Set 18.5 AT^SSYNC


18.5 AT^SSYNC Configure SYNC Pin

The AT^SSYNC command serves to configure the SYNC pin of the application interface. Please note that theSYNC pin may be assigned different functions: Depending on the design of the host application, the pin caneither be used to indicate the current consumption in a transmit burst or to drive a status LED connected to thepin as specified in [2]. For detailed information on the SYNC pin and its LED functionality refer to [2]. Beforechanging the mode of the SYNC pin, carefully read the technical specifications.

Syntax


Operation mode of the SYNC pin. Setting is stored non-volatile. 0(D) SYNC mode:

Enables the SYNC pin to indicate growing power consumption during a trans-mit burst. You can make use of the signal generated by the SYNC pin, if powerconsumption is your concern. To do so, ensure that your application is capableof processing the signal. Your platform design must be such that the incomingsignal causes other components to draw less current. In short, this allows yourapplication to accommodate current drain and thus, supply sufficient current tothe GSM engine if required.

1 LED mode:Enables the SYNC pin to drive a status LED installed in your applicationaccording to the specifications provided in [2].The coding of the LED is described in Section 18.5.1, ME status indicated bystatus LED patterns.

2 LED mode:Like <mode>=1, but, additionally, enables different LED signalization in SLEEPmode depending on the status of PIN authentication and network registration.Please see AT+CFUN for details on SLEEP mode.

Test Command

AT^SSYNC=?Response(s)

^SSYNC:list of supported <mode>s OK

Read Command

AT^SSYNC?Response(s)

^SSYNC:<mode>OK

Write Command

AT^SSYNC=<mode>Response(s)

OK


- + + + + + - -

<mode>(num)



18.5.1 ME status indicated by status LED patterns

The following table lists the possible patterns of status LED behavior, and describes the ME operating status indi-cated by each pattern if AT^SSYNC parameter <mode>=1 and <mode>=2. To better monitor the operating stateswhile power saving is enabled, we recommend that priority be given to <mode>=2.

During the transition from one LED pattern to another the "on" and/or "off" periods of the LED may vary in length.This is because an event that triggers the change may occur any time and, thus, truncate the current LED patternat any point.

Table 18.1: Modes of the LED and indicated ME functions

1) When a temporary wake-up event (for example a call, a URC, a packet switched transfer) occurs in CYCLIC SLEEP modethe LED flashes according to the patterns listed above. See Section 2.9.1, Wake up the ME from SLEEP mode for detailson the various SLEEP modes and wake-up events.

LED behavior ME operating status if AT^SSYNC=1 ME operating status if AT^SSYNC=2 Permanently off ME is in one of the following modes:

- POWER DOWN mode - CHARGE ONLY mode - NON-CYCLIC SLEEP mode- CYCLIC SLEEP mode with no tempo-rary wake-up event in progress 1)

ME is in one of the following modes: - POWER DOWN mode - CHARGE ONLY mode

600 ms on / 600ms off Limited Network Service: No SIM card inserted or no PIN entered, or network search in progress, or ongoing user authentication, or network login in progress.

Same as for AT^SSYNC=1

75 ms on / 3 s off IDLE mode: The mobile is registered to the GSM network (monitoring control channels and user interactions). No call is in progress.


75 ms on / 75 ms off /75 ms on / 3 s off

One or more GPRS PDP contexts acti-vated.


500 ms on / 50 ms off Packet switched data transfer is in progress.


Permanently on Depending on type of call:Voice call: Connected to remote party.Data call: Connected to remote party or exchange of parameters while setting up or disconnecting a call.


<n> ms on / <n> ms off 2) Not possible: With AT^SSYNC=1, LED signalization is disabled in SLEEP mode.

SLEEP mode is activated (AT+CFUN parameter <fun> ≠ 1), but the ME is not registered to the GSM network (e.g. SIM not inserted or PIN not entered, and therefore, either no network service or only Limited Network Service is avail-able.

25 ms on / 4 * <n> ms off 2) Not possible: With AT^SSYNC=1, LED signalization is disabled in SLEEP mode.

SLEEP mode is activated (AT+CFUN parameter <fun> ≠ 1) while the ME is registered to the GSM network and in IDLE mode.

25 ms on / <m> ms off /25 ms on / 3 * <m> ms off 2)

Not possible: With AT^SSYNC=1, LED signalization is disabled in SLEEP mode.

SLEEP mode is activated (AT+CFUN parameter <fun> ≠ 1) while the ME is registered to the GSM network. Addi-tionally, PDP context is activated.



2) The duration of <n>and <m>depends on the network: In SLEEP mode, the module can only change its LED status duringintermittent wake-up periods when listening to paging information from the base station. Therefore the values of <n>and<m>vary as follows: <n>= value from 471 ms to 2118 ms<m>= 3000 ms

BGS3 AT Command Set 19. Miscellaneous Commands


19. Miscellaneous Commands

The AT Commands described in this chapter are related to various areas.

19.1 A/ Repeat previous command line

Syntax

Command DescriptionRepeat previous command line.

Notes• Line does not need to end with terminating character. • After beginning with the character "a" or "A" a second character "t", "T" or "/" has to follow. In case of using a

wrong second character, it is necessary to start again with character "a" or "A". • If autobauding is active, the command A/ cannot be used (see AT+IPR).

Exec Command

A/Response(s)


- + + + + + - - V.250



19.2 ATS3 Set command line termination character

The ATS3 command determines the character recognized by the TA to terminate an incoming command line. Itis also generated for result codes and information text, along with the ATS4 parameter.

Syntax


command line termination character000...13(&F)...127

Notes• Using a value other than the default 13 may cause problems when entering commands. • Whenever you change the setting take into account that the new value has no effect on the URC "^SHUT-

DOWN".

Read Command

ATS3?Response(s)

<n>OK

Write Command

ATS3=<n>Response(s)

OKERROR


- + + + + + - - V.250

<n>(num)(&W)(&V)



19.3 ATS4 Set response formatting character

The ATS4 command determines the character generated by the TA for result code and information text, alongwith the ATS3 parameter .

Syntax


response formatting character000...10(&F)...127

Note• Whenever you change the setting take into account that the new value has no effect on the URC "^SHUT-

DOWN".

Read Command

ATS4?Response(s)

<n>OK

Write Command

ATS4=<n>Response(s)

OKERROR


- + + + + + - - V.250

<n>(num)(&W)(&V)



19.4 ATS5 Write command line editing character

Syntax

Command DescriptionThis parameter setting determines the character recognized by TA as a request to delete the immediately pre-ceding character from the command line.


command line editing character000...8(&F)...127

Read Command

ATS5?Response(s)

<n>OK

Write Command

ATS5=<n>Response(s)

OK


- + + + - - - - V.250

<n>(num)(&W)(&V)

BGS3 AT Command Set 19.5 AT^SFDL


19.5 AT^SFDL Enter Firmware Download Mode

The AT^SFDL command allows the application manufacturer to download BGS3 firmware into the module bystarting the download process from a customer-designed update tool.

For this purpose, the BGS3 firmware update file must be available in *.USF format. The *.USF file is part of eachmodule specific firmware package supplied by Cinterion Wireless Modules GmbH. The firmware file consists ofrecords to be transferred one by one from the update tool to the module.

This manual only describes the syntax of the AT^SFDL command. Details on technical requirements and stepsto prepare the host application for this download solution can be found in "Application Note 16: Updating BGS3Firmware" [9]. An example for developing an appropriate update tool is included.

The command causes the module to reset and enter the firmware download mode (this may take some millisec-onds). After entering the download mode the module sends the start pattern HEX 0x01 ("ANSWER_OK") to theupdate tool to indicate its ready state. Next, the update tool shall start to send the records of the firmware file.Each record received on the module is acknowledged to the update tool. Once all records are successfullyreceived, the module shuts down automatically.

If the module is switched on although it has no valid firmware installed, it waits 60s for the AT^SFDL command(or for another download method to be started). If neither the AT^SFDL command nor equivalent characters fromanother download method are received the module switches off after a 60s timeout.

If a valid firmware is still installed, but the AT^SFDL command is issued without sending any firmware afterwardsthe module will stay in ready state. In this case it must be switched off.

SyntaxTest Command

AT^SFDL=?Response(s)

OK

Exec Command

AT^SFDLResponse(s)

OK0x01


- + + - - - - +

BGS3 AT Command Set 20. Appendix


20. Appendix

20.1 Restricted access to SIM data after SIM PIN authentication

Users should be aware that when using a phonebook, SMS or Remote SAT command quickly after SIM PINauthentication the SIM data may not yet be accessible, resulting in a short delay before the requested AT com-mand response is returned. This delay is due to the initial process of loading SIM data once after SIM PIN authen-tication. The duration of loading SIM data is dependent on the SIM card used and may take a couple of seconds.

The "+CIEV: simstatus" URC enabled with AT^SIND can be used to notify the user when the ME has finishedreading the SIM card and SIM data are accessible after SIM PIN authentication. Of course, all phonebook andSMS commands may be issued before the SIM notification URC is delivered. In this case the AT commandresponse (for example the complete phonebook) will appear after the delay mentioned above, but before the"+CIEV: simstatus" URC is displayed. See example below.

After the "+CREG: 1" (or "+CREG: 5") URC and before the SIM notification URC "+CIEV: simstatus" it is not surethat outgoing and incoming calls can be made and short message functions executed. Emergency calls are pos-sible. Outgoing and incoming calls are always possible AFTER having received the "+CREG: 1" (or "+CREG: 5")URC and the SIM notification URC "+CIEV: simstatus". See also Section 8.4, Network registration.

If SIM cards with EFOPL and EFPNN fields are inserted, it is possible that the initial process of reading EONS datacauses an additional delay of 2 seconds before the SIM is fully accessible. Therefore, trying to access the SIMduring this time may cause the CME Error 14 or CMS Error 315 ("SIM busy") to occur even though the "+CIEV:simstatus" URC was already output. For details please see the note appended to AT^SIND, "eons" indicator.

Example:AT+CREG=1 Activate the "+CREG" URC.OKAT&W Store the presentation mode of the "+CREG" URC to

the user profile.OKAT+CFUN=1,1 Restart the ME. OK^SYSSTART The ME was restarted. AT^SIND=simstatus,1 Switch on the "simstatus" URC.^SIND: simstatus,1,1 The "+CIEV: simstatus" URC is switched on. The

SIM is inserted.OKAT+CMER=3,0,0,2 Activate the presentation of "+CIEV:..." URCs.OK+CIEV: battchg,5+CIEV: signal,99+CIEV: service,0+CIEV: sounder,0+CIEV: message,0+CIEV: call,0+CIEV: roam,0+CIEV: smsfull,0+CIEV: rssi,3+CIEV: simstatus,1AT+CPIN Enter the SIM PIN. OK+CIEV: simstatus,4 CHV data verified.AT+CPBW=50,"+4030123456789",145,"Paul" Write a new phonebook record.OK+CIEV: service,1 ME has registered to the network.

BGS3 AT Command Set 20.1 Restricted access to SIM data after SIM PIN authentication


+CREG: 1+CIEV: simstatus,5 SIM initialization completed - ME has finished read-

ing SIM data.AT+CPBR=50,50 Read the phonebook entered before.+CPBR: 50,"+4030123456789",145,"Paul" The phonebook entry was properly saved.

BGS3 AT Command Set 20.2 Star-Hash (*#) Network Commands


20.2 Star-Hash (*#) Network Commands

The following command strings can be sent to the network via ATD and have to be terminated with a semicolon.The command strings are defined with GSM 2.30 [16].

Table 20.1: Star-Hash (*#) Command Overview

Star-Hash Code Functionality Response, also refer to Table 20.3

Phone Security*#06# Query IMEI <IMEI> OK **04[2]*oldPin[2]*newPin[2]*new-Pin[2]#

Change SIM pwd +CME ERROR: <err> / OK

**05[2]*unblKey[2]*newPin[2]*new-Pin[2]#

Change/Unblocking SIM pwd +CME ERROR: <err> / OK

*#0003*MasterPhoneCode# Unlock ''PS'' lock with Master Phone Code

+CME ERROR: <err> / OK

*[*]03*[ZZ]*oldPw*newPw*newPw# Registration of net password +CME ERROR: <err> / OK

Phone number presentation*#30# Check status of CLIP (Calling Line

Identification Presentation) +CLIP : <n>,<m> OK (see AT+CLIP)

*#31# Check status of CLIR (Calling Line Identification Restriction)

+CLIR : <n>,<m> OK (see AT+CLIR)

*31#<Phonenumber>[;] Suppress CLIR (see AT+CLIR)#31#<Phonenumber>[;] Activate CLIR (see AT+CLIR)*#76# Check status of COLP (Connected

Line Identification Presentation) +COLP : <n>,<m> OK (see: AT+COLP)

*#77# Check status of COLR (Connected Line Identification Restriction)

+COLR : 0,<m> OK (where <m> = active or not active)

Call forwarding(choice of *,#,*#,**,##)21*DN*BS# Act/deact/int/reg/eras CFU ^SCCFC : <reason>, <status>,

<class> [,...] like +CCFC *) (see: AT+CCFC)

(choice of *,#,*#,**,##)67*DN*BS# Act/deact/int/reg/eras CF busy see above(choice of *,#,*#,**,##)61*DN*BS*T#

Act/deact/int/reg/eras CF no reply see above

(choice of *,#,*#,**,##)62*DN*BS# Act/deact/int/reg/eras CF no reach see above(choice of *,#,*#,**,##)002*DN*BS*T#

Act/deact/int/reg/eras CF all see above

(choice of *,#,*#,**,##)004*DN*BS*T#

Act/deact/int/reg/eras CF all cond. see above

Call waiting(choice of *,#,*#)43*BS# Activation/deactivation/int WAIT +CCWA : <status>, <class> [,...]

like +CCWA *) (see: AT+CCWA)



*) Notes on ^SCCFC, +CCWA, ^SCLCK: The output depends on the affected basic service of the Star-Hash code. One linewill be output for every tele- or bearer service coded in basic service code BS.^SCCFC and ^SCLCK are modified by giving an additional <reason> or <fac> in front of the regular output string gener-ated by the standard commands +CCFC and +CLCK.

Table 20.2: Abbreviations of Codes and Parameters used in Table 20.1

Call barring(choice of *,#,*#)33*Pw*BS# Act/deact/int BAOC ^SCLCK : <fac>, <status>, <class>

[, ...] like +CLCK *) (Refer to AT+CLCK)

(choice of *,#,*#)331*Pw*BS# Act/deact/int BAOIC see above(choice of *,#,*#)332*Pw*BS# Act/deact/int BAOIC exc.home see above(choice of *,#,*#)35*Pw*BS# Act/deact/int. BAIC see above(choice of *,#,*#)351*Pw*BS# Act/deact/int BAIC roaming see above#330*Pw*BS# Deact. All Barring Services see above#333*Pw*BS# Deact. All Outg.Barring Services see above#353*Pw*BS# Deact. All Inc.Barring Services see above

Call Hold / MultipartyC[C] in call Call hold and multiparty +CME ERROR: <err> / OK

USSD messages[C]...[C]# Send USSD message +CME ERROR: <err> / OK C[C] (excluded 1[C]) Send USSD message +CME ERROR: <err> / OK

Abbreviation Meaning ValueZZ Type of supplementary services:

Barring servicesAll services

330Not specified

DN Dialing number String of digits 0-9BS Basic service equivalent to parameter class:

VoiceFAXSMSSMS+FAXData circuit asynchronData circuit synchrondedicated PAD accessdedicated Packet accessData circuit asynchron+PADData circuit synchron+PacketData circuit asynchron+synchron+Packet+PADAll Services

1113161225242726212220--

T Time in seconds In contrast to AT+CCFC, parameter T has no default value. If T is not specified, an operator defined default or the last known value may be used, depending on the network operator.

Star-Hash Code Functionality Response, also refer to Table 20.3



Table 20.3: Star-Hash Command Response Parameters

For exact specification of format and parameters for Star-Hash commands refer to GSM 02.04, Table 3.2 [15]and GSM 02.30, Annex C [16].

Table 20.4: Star-Hash Commands for Supplementary Services

PW Password -- C Character of TE character set (e.g. asterisk, hash

or digit in case of USSD, or digits in case of held calls or multiparty calls)

--

Parameter Meaning<m> Mode: 0 = not active, 1 = active <n> Unsolicited result code: 0 = presentation disabled, 1 = presentation enabled <status> Status: 0 = not active, 1 = active <class> Represents BS = basic service, refer to AT+CCFC, AT+CLCK <fac> Facility lock, refer to AT+CLCK <reason> Call forwarding reason

Star-Hash Code Abbreviations in Table 20.1 Functionality * act Activate (except for CLIR, see list above)** reg Register and activate*# int Check status (interrogate)# deact Deactivate (except for CLIR, see list above)## eras Unregister and deactivate

Abbreviation Meaning Value

BGS3 AT Command Set 20.3 Available AT Commands and Dependency on SIM PIN


20.3 Available AT Commands and Dependency on SIM PIN

ø ... Command not available- ... Command does not require PIN1+ ... Command requires PIN1± ... Command sometimes requires PIN1

Table 20.5: Available AT Commands and Dependency on SIM PIN

AT Command Exec Test Read Write

Configuration CommandsAT&F - ø ø øAT&V - ø ø øAT&W - ø ø øATQ - ø ø øATV - ø ø øATX - ø ø øAT\V - ø ø øATZ - ø ø øAT+CFUN ø - - -AT^SMSO - - ø øAT+GCAP - - ø øAT+CMEE ø - - -AT+CSCS ø - - -AT^SCFG ø - - -AT^SM20 ø - - -

Status Control CommandsAT+CMER ø - - -AT+CIND ø - - -AT^SIND ø - - -AT+CEER + + ø øATS18 ø ø - -AT+CPAS - - ø øAT+WS46 ø - - -

Serial Interface Control CommandsATE - ø ø øAT&C - ø ø øAT&D - ø ø øAT&S - ø ø øAT\Q - ø ø øAT+IFC ø - - -AT+ILRR ø + + +



AT+IPR ø - - -AT+CMUX ø - - -

Security CommandsAT+CPIN ø - - -AT+CPIN2 ø + + +AT^SPIC - - - -AT+CLCK ø + ø +AT^SLCK ø + ø +AT+CPWD ø + ø +AT^SPWD ø ± ø ±AT^SCSL ø - ø -

Identification CommandsATI - ø ø øAT+CGMI - - ø øAT+GMI - - ø øAT+CGMM - - ø øAT+GMM - - ø øAT+CGMR - - ø øAT+GMR - - ø øAT+CGSN - - ø øAT+GSN - - ø øAT+CIMI + + ø ø

Call related CommandsATA + ø ø øATD ± ø ø øATD><mem><n> + ø ø øATD><n> + ø ø øATD><str> + ø ø øATDI + ø ø øATDL + ø ø øATH - ø ø øAT+CHUP + + ø øAT^SHUP ø + ø +ATS0 ø ø - +ATS2 ø ø - -ATS6 ø ø - -ATS7 ø ø - -ATS8 ø ø - -ATS10 ø ø - -ATO - ø ø ø




+++ - ø ø øAT+CBST ø - - -AT+CRLP ø - - -AT+CLCC + + ø øAT^SLCC + + + +AT+CR ø + + +AT+CRC ø - - -AT+CSNS ø - - -AT^SCNI + + ø øAT^SLCD + + ø øAT^STCD + + ø øATP - ø ø øATT - ø ø ø

Network Service CommandsAT+COPN + + ø øAT+COPS ø - ± ±AT^SOPS ø + ø øAT+CREG ø - - -AT+CSQ - - ø øAT^SMONC + + ø øAT^SMOND + + ø øAT^SFNUR ø - - -AT^MONI - - ø -AT^MONP - - ø -AT^SMONG + + ø +AT^SALS ø + + +AT^SHOM + + ø øAT^SPLM + + ø øAT+CPOL ø + + +

Supplementary Service CommandsAT+CACM ø + + +AT^SACM + + ø +AT+CAMM ø + + +AT+CAOC + + + +AT+CCUG ø + + +AT+CCFC ø + ø +AT+CCWA ø + + +AT+CHLD ø + ø +AT+CLIP ø - + -AT+CLIR ø + + +




AT+COLP ø + + +AT+CPUC ø + + +AT+CSSN ø - - -AT+CUSD ø + + +

Internet Service CommandsAT^SICS ø - - -AT^SICI ø - - -AT^SISS ø - - -AT^SISI ø - - -AT^SISO ø - - +AT^SISC ø - ø +AT^SISR ø - ø +AT^SISW ø - ø +AT^SIST ø - ø -AT^SICO ø + + +AT^SICC ø + ø +AT^SISX ø + ø +AT^SISE ø - ø -

GPRS CommandsAT+CGACT ø + + +AT+CGANS ø + ø +AT+CGATT ø + + +AT+CGAUTO ø + + +AT+CGDATA ø + ø +AT+CGDCONT ø + + +AT+CGEQMIN ø + + +AT+CGEQREQ ø + + +AT+CGPADDR ø + ø +AT+CGQMIN ø + + +AT+CGQREQ ø + + +AT+CGREG ø + + +AT+CGSMS ø + + +AT^SGACT + + + øAT^SGAUTH ø - - -AT^SGCONF ø - - -ATA + ø ø øATD*99# + ø ø øATD*98# + ø ø øATH + ø ø øATS0 ø ø - +




FAX CommandsAT+FCLASS ø - - -AT+FRH ø - ø -AT+FRM ø - ø -AT+FRS ø ø ø -AT+FTH ø - ø -AT+FTM ø - ø -AT+FTS ø ø ø -

Short Message Service (SMS) CommandsAT+CMGC ø + ø +AT+CMGD ø + ø +AT+CMGF ø - - -AT+CMGL + + ø +AT+CMGR ø + ø +AT+CMGS ø + ø +AT+CMGW + + ø +AT+CMSS ø + ø +AT+CNMA + + ø +AT+CNMI ø + + +AT+CPMS ø + + +AT+CSCA ø + + +AT+CSCB ø + + +AT+CSDH ø + + +AT+CSMP ø + + +AT+CSMS ø + + +AT^SCML + + ø +AT^SCMR ø + ø +AT^SCMS ø + ø +AT^SCMW ø + ø +AT^SLMS + + ø øAT^SMGL + + ø +AT^SMGO ø + + +AT^SMGR ø + ø +AT^SSCONF ø - - -AT^SSDA ø - - -AT^SSMSS ø + + +

SIM related CommandsAT+CRSM ø ± ø ±AT^SATR - - ø øAT^SXSM ø + ø +




AT^SCKS ø - - -AT^SCID - - ø øAT+CXXCID - - ø ø

SIM Application Toolkit (SAT) CommandsAT^SSTA ø - - -^SSTN ø ø ø øAT^SSTGI ø - - -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTGI ø ø ø -AT^SSTR ø - - -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -




AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -AT^SSTR ø ø ø -

Phonebook CommandsAT+CNUM + + ø øAT+CPBR ø + ø +AT+CPBS ø + + +AT+CPBW ø + ø +AT^SPBW ø + ø +AT^SDLD + + ø øAT^SPBC ø + ø +AT^SPBD ø + ø +AT^SPBG ø + ø +AT^SPBS ø + ø +

Audio CommandsATL - ø ø øATM - ø ø øAT+CLVL ø - - -AT+CMUT ø - - -AT+VTD ø - - -AT+VTS ø - ø -AT^SAIC ø - - -AT^SNFA ø - - -AT^SNFD - - ø øAT^SNFG ø - ø -AT^SNFI ø - - -AT^SNFM ø - - -AT^SNFO ø - - -AT^SNFPT ø - - -AT^SNFS ø - - -AT^SNFTTY ø - - -AT^SNFV ø - - -AT^SNFW - - ø øAT^SRTC - - - -

Hardware related CommandsAT+CCLK ø - - -AT^SBC ø - - -AT^SBV - - ø ø




AT^SCTM ø - - -AT^SSYNC ø - - -

Miscellaneous CommandsA/ - ø ø øATS3 ø ø - -ATS4 ø ø - -ATS5 ø ø - -AT^SFDL - - ø ø


BGS3 AT Command Set 20.4 AT Command Settings storable with AT&W


20.4 AT Command Settings storable with AT&W

Table 20.6: Settings Stored to User Profile on ASC0 / MUX Channel 1

AT Command Stored Parameters

Configuration CommandsATQ <n>

ATV <value>

ATX <value>

AT\V <value>

AT+CMEE <errMode>

Status Control CommandsATS18 <n>

Serial Interface Control CommandsATE <value>

AT&C <value>

AT&D <value>

AT&S <value>

AT\Q <n>

AT+IFC <TEflowcontrol>, <TAflowcontrol>AT+ILRR <value>

Call related CommandsATS0 <n>

ATS6 <n>

ATS7 <n>

ATS8 <n>

ATS10 <n>

AT+CBST <speed>, <name>, <ce>AT+CRLP <iws>, <mws>, <T1>, <N2>AT^SLCC <n>

AT+CR <mode>

AT+CRC <mode>

Network Service CommandsAT+COPS <format>

AT+CREG <n>

Supplementary Service CommandsAT^SACM <n>

AT+CLIP <n>



Table 20.7: Settings Stored to User Profile on ASC1 / MUX Channels 2 and 3

GPRS CommandsATS0 <n>

FAX CommandsAT+FCLASS <n>

Short Message Service (SMS) CommandsAT+CMGF <mode>

AT+CNMI <mode>, <mt>, <bm>, <ds>AT+CSDH <show>

AT+CSMS <service>

AT^SMGO <n>

SIM related CommandsAT^SCKS <mode>

Miscellaneous CommandsATS3 <n>

ATS4 <n>

ATS5 <n>


Configuration CommandsATQ <n>

ATV <value>

ATX <value>

AT+CMEE <errMode>

Serial Interface Control CommandsATE <value>

AT&C <value>

AT&D <value>

AT&S <value>

AT\Q <n>

AT+IFC <TEflowcontrol>, <TAflowcontrol>

Call related CommandsATS0 <n>

AT^SLCC <n>

AT+CR <mode>




AT+CRC <mode>

Network Service CommandsAT+COPS <format>

AT+CREG <n>

Supplementary Service CommandsAT^SACM <n>

AT+CLIP <n>

GPRS CommandsATS0 <n>

Short Message Service (SMS) CommandsAT+CMGF <mode>

AT+CNMI <mode>, <mt>, <bm>, <ds>AT+CSDH <show>

AT+CSMS <service>

AT^SMGO <n>

SIM related CommandsAT^SCKS <mode>

Miscellaneous CommandsATS3 <n>

ATS4 <n>

ATS5 <n>


BGS3 AT Command Set 20.5 Factory Default Settings Restorable with AT&F


20.5 Factory Default Settings Restorable with AT&F

Table 20.8: Factory Default Settings Restorable with AT&F

AT Command Factory Defaults

Configuration CommandsATQ <n>=0ATV <value>=1ATX <value>=4AT\V <value>=1AT+CFUN <fun>=1AT+CMEE <errMode>=0AT+CSCS <chset>="GSM"AT^SM20 <CallMode>=1, <CmgwMode>=1AT^SCFG <tcpBufSize>="5200", <tcpIrt>="3", <tcpMr>="10",

<tcpOt>="6000", <tcpWithUrc>="on"

Status Control CommandsAT+CMER <mode>=0, <keyp>=0, <disp>=0, <ind>=0, <bfr>=0AT+CIND <mode>=1ATS18 <n>=0

Serial Interface Control CommandsATE <value>=1AT&C <value>=1AT&D <value>=2AT&S <value>=0AT\Q <n>=0AT+IFC <TEflowcontrol>=0, <TAflowcontrol>=0AT+ILRR <value>=0

Call related CommandsATS0 <n>=000ATS6 <n>=000ATS7 <n>=060ATS8 <n>=0ATS10 <n>=002AT+CBST <speed>=7, <name>=0, <ce>=1AT+CRLP <iws>=61, <mws>=61, <T1>=78, <N2>=6AT^SLCC <n>=0AT+CR <mode>=0AT+CRC <mode>=0



Network Service CommandsAT+COPS <format>=0AT+CREG <n>=0AT^SALS <view>=0, <line>=1

Supplementary Service CommandsAT^SACM <n>=0AT+CLIP <n>=0AT+CSSN <n>=0, <m>=0AT+CUSD <n>=0

GPRS CommandsAT+CGAUTO <n>=3AT+CGREG <n>=0AT+CGSMS <service>=3AT^SGAUTH <auth>=1ATS0 <n>=000

FAX CommandsAT+FCLASS <n>=0

Short Message Service (SMS) CommandsAT+CMGF <mode>=0AT+CNMI <mode>=0, <mt>=0, <bm>=0, <ds>=0, <bfr>=1AT+CSCB <mode>=0, <mids>=" ", <dcss>=" "AT+CSDH <show>=0AT+CSMP <fo>=17, <vp>=167, <dcs>=0, <pid>=0AT+CSMS <service>=0AT^SMGO <n>=0AT^SSCONF <ra>=0AT^SSDA <da>=0AT^SSMSS <seq>=0

SIM related CommandsAT^SCKS <mode>=0

Phonebook CommandsAT+CPBS <storage>="SM"AT^SPBS <internal-counter>=0

Audio CommandsAT+VTD <duration>=1




Hardware related CommandsAT^SCTM <UrcMode>=0, <tempCtrl>=0

Miscellaneous CommandsATS3 <n>=013ATS4 <n>=010ATS5 <n>=008


BGS3 AT Command Set 20.6 Summary of Unsolicited Result Codes (URC)


20.6 Summary of Unsolicited Result Codes (URC)

Table 20.9: Summary of Unsolicited Result Codes (URC)

AT Command URC

Configuration CommandsAT+CFUN ^SYSSTART

AT+CFUN ^SYSSTART CHARGE ONLY MODE

AT^SMSO ^SHUTDOWN

AT^SCFG ^SCFG: "AutoExec", <AutoExecState>, <AutoExecType>, <AutoExecIndex>, <AutoExecMode>, <AutoExecATC>

Status Control CommandsAT+CMER +CIEV: <indDescr>, <indValue>1[, <indValue>2]AT^SIND +CIEV: <indDescr>, <indValue>AT^SIND +CIEV: <indDescr>, <indValue>, <vmCounter>AT^SIND +CIEV: <indDescr>, <indValue>, <eonsOperator>, <servProvider>AT^SIND +CIEV: <indDescr>, <nitzUT>, <nitzTZ>, <nitzDST>AT^SIND +CIEV: <indDescr>, <indValue>, <lstaEdv>, <lstaRssi>AT^SIND +CIEV: <indDescr>, <indValue>, <lstaNo>, <lstaMin>, <lstaMax>,

<lstaMean>, <lstaVar>

Call related CommandsAT^SLCC if the list of current calls is empty:

^SLCC: if one or more calls are currently in the list: ^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]][^SLCC: <idx>, <dir>, <stat>, <mode>, <mpty>, <traffic channel assigned>[, <number>, <type>[, <alpha>]]][... ]^SLCC:

AT+CRC RING

AT+CRC +CRING: <type>

Network Service CommandsAT+CREG +CREG: <stat>AT+CREG +CREG: <stat>[, <lac>, <ci>]AT^SALS ^SALS: <line>

Supplementary Service CommandsAT^SACM +CCCM: <ccm>AT+CCWA +CCWA: <calling number>, <type of number>, <class>, , <CLI validity>AT+CCWA ^SCWA:AT+CLIP +CLIP: <number>, <type>[, , [, [<alpha>][, <CLI validity>]]]AT+COLP +COLP: <number>, <type>AT+CSSN +CSSI: <code 1>

BGS3 AT Command Set 20.6 Summary of Unsolicited Result Codes (URC)


AT+CSSN +CSSU: <code 2>AT+CUSD +CUSD: <m>[, <str_urc>[, <dcs>]]

Internet Service CommandsAT^SISR ^SISR: <srvProfileId>, <urcCauseId>AT^SISW ^SISW: <srvProfileId>, <urcCauseId>Internet Ser-vice URC "^SIS"

^SIS: <srvProfileId>, <urcCause>[, [<urcInfoId>][, <urcInfoText>]]

GPRS CommandsAT+CGREG +CGREG: <stat>AT+CGREG +CGREG: <stat>, <lac>, <ci>

Short Message Service (SMS) CommandsAT+CNMI +CMTI: <mem3>, <index>AT+CNMI +CMT: <length><CR><LF><pdu>AT+CNMI +CMT: <oa>, <scts>[, <tooa>, <fo>, <pid>, <dcs>, <sca>, <tosca>,

<length>]<CR><LF><data>AT+CNMI +CBM: <length><CR><LF><pdu>AT+CNMI +CBM: <sn>, <mid>, <dcs>, <page>, <pages><CR><LF><data>AT+CNMI +CDS: <length><CR><LF><pdu>AT+CNMI +CDS: <fo>, <mr>[, <ra>][, <tora>], <scts>, <dt>, <st>AT+CNMI +CDSI: <mem3>, <index>AT^SMGO ^SMGO: <mode>

SIM related CommandsAT^SCKS ^SCKS: <SimStatus>

SIM Application Toolkit (SAT) Commands^SSTN ^SSTN: <cmdType>^SSTN ^SSTN: <cmdTerminateValue>^SSTN ^SSTN: 254^SSTN ^SSTN: 255

Hardware related CommandsAT^SBC ^SBC: UndervoltageAT^SBC ^SBC: Overvoltage warningAT^SBC ^SBC: Overvoltage shutdownAT^SCTM ^SCTM_A: <UrcCause>AT^SCTM ^SCTM_B: <UrcCause>

AT Command URC

BGS3 AT Command Set 20.7 Alphabetical List of AT Commands


20.7 Alphabetical List of AT Commands

Table 20.10: Alphabetical List of AT Commands

AT Command Description Section and Page+++ Switch from data mode or PPP online mode to command

modeSection 7.19, page 168

^SSTN SAT Notification Section 15.5, page 424A/ Repeat previous command line Section 19.1, page 542AT&C Set Data Carrier Detect (DCD) Line mode Section 4.2, page 102AT&D Set Data Terminal Ready (DTR) line mode Section 4.3, page 103AT&F Set all current parameters to manufacturer defaults Section 2.1, page 32AT&S Set Data Set Ready (DSR) line mode Section 4.4, page 104AT&V Display current configuration Section 2.2, page 33AT&W Stores current configuration to user defined profile Section 2.3, page 36AT+CACM Accumulated call meter (ACM) reset or query Section 9.1, page 214AT+CAMM Accumulated call meter maximum (ACMmax) set or query Section 9.3, page 217AT+CAOC Advice of Charge information Section 9.4, page 218AT+CBST Select bearer service type Section 7.20, page 169AT+CCFC Call forwarding number and conditions control Section 9.6, page 221AT+CCLK Real Time Clock Section 18.1, page 531AT+CCUG Closed User Group Section 9.5, page 219AT+CCWA Call Waiting Section 9.7, page 225AT+CEER Extended Error Report Section 3.4, page 88AT+CFUN Set phone functionality Section 2.9, page 42AT+CGACT PDP context activate or deactivate Section 11.1, page 309AT+CGANS Manual response to a network request for PDP context

activationSection 11.2, page 311

AT+CGATT GPRS attach or detach Section 11.3, page 313AT+CGAUTO Automatic response to a network request for PDP context


AT+CGDATA Enter data state Section 11.5, page 316AT+CGDCONT Define PDP Context Section 11.6, page 318AT+CGEQMIN Rel. 99 Quality of Service Profile (Minimum acceptable) Section 11.7, page 320AT+CGEQREQ Rel. 99 Quality of Service Profile (Requested) Section 11.8, page 324AT+CGMI Request manufacturer identification Section 6.2, page 143AT+CGMM Request model identification Section 6.4, page 144AT+CGMR Request revision identification of software status Section 6.6, page 145AT+CGPADDR Show PDP address Section 11.9, page 328AT+CGQMIN Quality of Service Profile (Minimum acceptable) Section 11.10, page 329AT+CGQREQ Quality of Service Profile (Requested) Section 11.11, page 333AT+CGREG GPRS Network Registration Status Section 11.12, page 337AT+CGSMS Select service for MO SMS messages Section 11.13, page 339AT+CGSN Request International Mobile Equipment Identity (IMEI) Section 6.8, page 146AT+CHLD Call Hold and Multiparty Section 9.8, page 229



AT+CHUP Hang up call Section 7.10, page 159AT+CIMI Request International Mobile Subscriber Identity (IMSI) Section 6.10, page 147AT+CIND Indicator control Section 3.2, page 77AT+CLCC List of current calls Section 7.22, page 172AT+CLCK Facility lock Section 5.4, page 126AT+CLIP Calling Line Identification Presentation Section 9.9, page 231AT+CLIR Calling Line Identification Restriction Section 9.10, page 233AT+CLVL Loudspeaker volume level Section 17.4, page 505AT+CMEE Mobile Equipment Error Message Format Section 2.12, page 48AT+CMER Mobile Equipment Event Reporting Section 3.1, page 75AT+CMGC Send an SMS command Section 13.2, page 365AT+CMGD Delete short message Section 13.3, page 366AT+CMGF Select SMS message format Section 13.4, page 367AT+CMGL List SMS messages from preferred store Section 13.5, page 368AT+CMGR Read SMS messages Section 13.6, page 370AT+CMGS Send Short Message Section 13.7, page 372AT+CMGW Write Short Messages to Memory Section 13.8, page 374AT+CMSS Send short messages from storage Section 13.9, page 376AT+CMUT Mute control Section 17.5, page 506AT+CMUX Multiplex Mode Section 4.9, page 113AT+CNMA New Message Acknowledgement to ME/TE, only phase

2+Section 13.10, page 377

AT+CNMI New short Message Indication Section 13.11, page 378AT+CNUM Read own numbers Section 16.2, page 481AT+COLP Connected Line Identification Presentation Section 9.11, page 234AT+COPN Read operator names Section 8.1, page 186AT+COPS Operator Selection Section 8.2, page 187AT+CPAS Mobile equipment activity status Section 3.6, page 99AT+CPBR Read from Phonebook Section 16.3, page 482AT+CPBS Select phonebook memory storage Section 16.4, page 485AT+CPBW Write into Phonebook Section 16.5, page 487AT+CPIN PIN Authentication Section 5.1, page 116AT+CPIN2 PIN2 Authentication Section 5.2, page 120AT+CPMS Preferred SMS message storage Section 13.12, page 381AT+CPOL Preferred Operator List Section 8.15, page 213AT+CPUC Price per unit and currency table Section 9.12, page 236AT+CPWD Change Password Section 5.6, page 132AT+CR Service reporting control Section 7.24, page 179AT+CRC Set Cellular Result Codes for incoming call indication Section 7.25, page 180AT+CREG Network registration Section 8.4, page 192AT+CRLP Select radio link protocol parameters for originated non-

transparent data callsSection 7.21, page 171

AT Command Description Section and Page



AT+CRSM Restricted SIM Access Section 14.1, page 402AT+CSCA SMS Service Center Address Section 13.13, page 383AT+CSCB Select Cell Broadcast Message Indication Section 13.14, page 384AT+CSCS Select TE character set Section 2.13, page 56AT+CSDH Show SMS text mode parameters Section 13.15, page 385AT+CSMP Set SMS text Mode Parameters Section 13.16, page 386AT+CSMS Select Message Service Section 13.17, page 388AT+CSNS Single Numbering Scheme Section 7.26, page 181AT+CSQ Signal quality Section 8.5, page 195AT+CSSN Supplementary service notifications Section 9.13, page 238AT+CUSD Unstructured supplementary service data Section 9.14, page 240AT+CXXCID Display card ID Section 14.6, page 411AT+FCLASS Fax: Select, read or test service class Section 12.2, page 353AT+FRH Receive Data Using HDLC Framing Section 12.3, page 354AT+FRM Receive Data Section 12.4, page 355AT+FRS Receive Silence Section 12.5, page 356AT+FTH Transmit Data Using HDLC Framing Section 12.6, page 357AT+FTM Transmit Data Section 12.7, page 358AT+FTS Stop Transmission and Wait Section 12.8, page 359AT+GCAP Request complete TA capabilities list Section 2.11, page 47AT+GMI Request manufacturer identification Section 6.3, page 143AT+GMM Request model identification Section 6.5, page 144AT+GMR Request revision identification of software status Section 6.7, page 145AT+GSN Request International Mobile Equipment Identity (IMEI) Section 6.9, page 146AT+IFC Flow Control Section 4.6, page 106AT+ILRR Set TE-TA local rate reporting Section 4.7, page 108AT+IPR Bit Rate Section 4.8, page 110AT+VTD Tone duration Section 17.6, page 507AT+VTS DTMF and tone generation Section 17.7, page 508AT+WS46 Select wireless network Section 3.7, page 100AT\Q Flow control Section 4.5, page 105AT\V Set CONNECT result code format Section 2.7, page 40AT^MONI Monitor idle mode and dedicated mode Section 8.9, page 202AT^MONP Monitor neighbor cells Section 8.10, page 205AT^SACM Advice of charge and query of ACM and ACMmax Section 9.2, page 215AT^SAIC Audio Interface Configuration Section 17.8, page 509AT^SALS Alternate Line Service Section 8.12, page 209AT^SATR Query SIM's Answer to Reset Data Section 14.2, page 405AT^SBC Battery Charge Control Section 18.2, page 532AT^SBV Battery/Supply Voltage Section 18.3, page 535AT^SCFG Extended Configuration Settings Section 2.14, page 57AT^SCID Display SIM card identification number Section 14.5, page 410




AT^SCKS Query SIM and Chip Card Holder Status Section 14.4, page 408AT^SCML List Concatenated Short Messages from preferred store Section 13.18, page 390AT^SCMR Read Concatenated Short Messages Section 13.19, page 391AT^SCMS Send Concatenated Short Messages Section 13.20, page 392AT^SCMW Write Concatenated Short Messages to Memory Section 13.21, page 393AT^SCNI List Call Number Information Section 7.27, page 182AT^SCSL Customer SIM Lock Section 5.8, page 138AT^SCTM Critical Operating Temperature Monitoring Section 18.4, page 536AT^SDLD Delete the 'last number redial' memory Section 16.7, page 493AT^SFDL Enter Firmware Download Mode Section 19.5, page 546AT^SFNUR Select the fixed network user rate Section 8.8, page 201AT^SGACT Query all PDP context activations Section 11.14, page 340AT^SGAUTH Set type of authentication for PPP connection Section 11.15, page 342AT^SGCONF Configuration of GPRS related Parameters Section 11.16, page 343AT^SHOM Display Homezone Section 8.13, page 211AT^SHUP Hang up call(s) indicating a specific GSM04.08 release

causeSection 7.11, page 160

AT^SICC Internet Connection Close Section 10.11, page 283AT^SICI Internet Connection Information Section 10.2, page 250AT^SICO Internet Connection Open Section 10.10, page 281AT^SICS Internet Connection Setup Profile Section 10.1, page 245AT^SIND Extended Indicator Control Section 3.3, page 80AT^SISC Internet Service Close Section 10.6, page 271AT^SISE Internet Service Error Report Section 10.13, page 287AT^SISI Internet Service Information Section 10.4, page 263AT^SISO Internet Service Open Section 10.5, page 265AT^SISR Internet Service Read Data Section 10.7, page 272AT^SISS Internet Service Setup Profile Section 10.3, page 253AT^SIST Enter Transparent Access Mode Section 10.9, page 279AT^SISW Internet Service Write Data Section 10.8, page 275AT^SISX Internet Service Execution Section 10.12, page 284AT^SLCC Extended list of current calls Section 7.23, page 174AT^SLCD Display Last Call Duration Section 7.28, page 183AT^SLCK Facility lock Section 5.5, page 131AT^SLMS List SMS Memory Storage Section 13.22, page 394AT^SM20 Set M20 compatibility mode Section 2.15, page 74AT^SMGL List Short Messages from preferred store without setting

status to REC READSection 13.23, page 395

AT^SMGO Set or query SMS overflow presentation mode or query SMS overflow

Section 13.24, page 396

AT^SMGR Read short message without setting status to REC READ Section 13.25, page 398AT^SMONC Cell Monitoring Section 8.6, page 196AT^SMOND Cell Monitoring Section 8.7, page 198




AT^SMONG Packet Data Monitor Section 8.11, page 207AT^SMSO Switch off mobile station Section 2.10, page 46AT^SNFA Set or query of microphone attenuation Section 17.9, page 511AT^SNFD Set audio parameters to manufacturer default values Section 17.10, page 513AT^SNFG Generate Tone Section 17.11, page 514AT^SNFI Set microphone path parameters Section 17.12, page 516AT^SNFM Set microphone audio path and power supply Section 17.13, page 517AT^SNFO Set audio output (= loudspeaker path) parameter Section 17.14, page 519AT^SNFPT Set progress tones Section 17.15, page 521AT^SNFS Select audio hardware set Section 17.16, page 522AT^SNFTTY Signal TTY/CTM audio mode capability Section 17.17, page 525AT^SNFV Set loudspeaker volume Section 17.18, page 527AT^SNFW Write audio setting in non-volatile store Section 17.19, page 528AT^SOPS Extended Operator Selection Section 8.3, page 190AT^SPBC Find first matching entry in sorted phonebook Section 16.8, page 494AT^SPBD Purge phonebook memory storage Section 16.9, page 495AT^SPBG Display phonebook entries in alphabetical order Section 16.10, page 496AT^SPBS Step through the selected phonebook alphabetically Section 16.11, page 499AT^SPBW Write into Phonebook with location report Section 16.6, page 490AT^SPIC Display PIN counter Section 5.3, page 122AT^SPLM Read the PLMN list Section 8.14, page 212AT^SPWD Change Password Section 5.7, page 136AT^SRTC Ring tone configuration Section 17.20, page 529AT^SSCONF SMS Command Configuration Section 13.26, page 399AT^SSDA Set SMS Display Availability Section 13.27, page 400AT^SSMSS Set Short Message Storage Sequence Section 13.28, page 401AT^SSTA Remote-SAT Interface Activation Section 15.4, page 422AT^SSTGI SAT Get Information Section 15.6, page 426AT^SSTGI SAT Get Information - Refresh (1) Section 15.7, page 427AT^SSTGI SAT Get Information - Set Up Event List (5) Section 15.8, page 429AT^SSTGI SAT Get Information - Set Up Call (16) Section 15.9, page 430AT^SSTGI SAT Get Information - Send SS (17) Section 15.10, page 432AT^SSTGI SAT Get Information - Send USSD (18) Section 15.11, page 433AT^SSTGI SAT Get Information - Send Short Message (19) Section 15.12, page 434AT^SSTGI SAT Get Information - Send DTMF (20) Section 15.13, page 435AT^SSTGI SAT Get Information - Launch Browser (21) Section 15.14, page 436AT^SSTGI SAT Get Information - Play Tone (32) Section 15.15, page 438AT^SSTGI SAT Get Information - Display Text (33) Section 15.16, page 440AT^SSTGI SAT Get Information - Get Inkey (34) Section 15.17, page 442AT^SSTGI SAT Get Information - Get Input (35) Section 15.18, page 444AT^SSTGI SAT Get Information - Select Item (36) Section 15.19, page 446AT^SSTGI SAT Get Information - Set up Menu (37) Section 15.20, page 448




AT^SSTGI SAT Get Information - Set up Idle Mode Text (40) Section 15.21, page 450AT^SSTGI SAT Get Information - Language Notification (53) Section 15.22, page 451AT^SSTR SAT Response Section 15.23, page 452AT^SSTR SAT Response - Refresh (1) Section 15.24, page 454AT^SSTR SAT Response - Set Up Event List (5) Section 15.25, page 455AT^SSTR SAT Response - Set Up Call (16) Section 15.26, page 456AT^SSTR SAT Response - Send SS (17) Section 15.27, page 457AT^SSTR SAT Response - Send USSD (18) Section 15.28, page 458AT^SSTR SAT Response - Send Short Message (19) Section 15.29, page 459AT^SSTR SAT Response - Send DTMF (20) Section 15.30, page 460AT^SSTR SAT Response - Launch Browser (21) Section 15.31, page 461AT^SSTR SAT Response - Play Tone (32) Section 15.32, page 462AT^SSTR SAT Response - Display Text (33) Section 15.33, page 463AT^SSTR SAT Response - Get Inkey (34) Section 15.34, page 464AT^SSTR SAT Response - Get Input (35) Section 15.35, page 465AT^SSTR SAT Response - Select Item (36) Section 15.36, page 466AT^SSTR SAT Response - Setup Menu (37) Section 15.37, page 468AT^SSTR SAT Response - Set Up Idle Mode Text (40) Section 15.38, page 469AT^SSTR SAT Response - Language Notification (53) Section 15.39, page 470AT^SSTR SAT Event - Menu Selection (211) Section 15.40, page 471AT^SSTR SAT Event - User Activity (232) Section 15.41, page 472AT^SSTR SAT Event - Idle Screen Available (233) Section 15.42, page 473AT^SSTR SAT Event - Language Selection (235) Section 15.43, page 474AT^SSTR SAT Event - Browser Termination (236) Section 15.44, page 475AT^SSTR SAT Event - Terminate Command (254) Section 15.45, page 476AT^SSYNC Configure SYNC Pin Section 18.5, page 539AT^STCD Display Total Call Duration Section 7.29, page 184AT^SXSM Extended SIM Access Section 14.3, page 406ATA Answer a call Section 7.2, page 149ATA Manual response to a network request for PDP context


ATD Mobile originated call to specified number Section 7.3, page 150ATD*98# Request GPRS IP service Section 11.19, page 346ATD*99# Request GPRS service Section 11.18, page 345ATD><mem><n> Mobile originated call using specific memory and index

numberSection 7.4, page 152

ATD><n> Mobile originated call from active memory using index number


ATD><str> Mobile originated call from active memory using corre-sponding field


ATDI Mobile originated call to ISDN number Section 7.7, page 156ATDL Redial last number used Section 7.8, page 157ATE Enable command echo Section 4.1, page 101




ATH Disconnect existing connection Section 7.9, page 158ATH Manual rejection of a network request for PDP context


ATI Display product identification information Section 6.1, page 142ATL Set monitor speaker loudness Section 17.2, page 504ATM Set monitor speaker mode Section 17.3, page 504ATO Switch from command mode to data mode / PPP online

modeSection 7.18, page 167

ATP Select pulse dialing Section 7.30, page 185ATQ Result code presentation mode Section 2.4, page 37ATS0 Set number of rings before automatically answering a call Section 7.12, page 161ATS0 Automatic response to a network request for PDP context


ATS10 Set disconnect delay after indicating the absence of data carrier


ATS18 Extended call release report Section 3.5, page 97ATS2 Set escape sequence character Section 7.13, page 162ATS3 Set command line termination character Section 19.2, page 543ATS4 Set response formatting character Section 19.3, page 544ATS5 Write command line editing character Section 19.4, page 545ATS6 Set pause before blind dialing Section 7.14, page 163ATS7 Set number of seconds to wait for connection completion Section 7.15, page 164ATS8 Set number of seconds to wait for comma dialing modifier Section 7.16, page 165ATT Select tone dialing Section 7.31, page 185ATV Result code format mode Section 2.5, page 38ATX Set CONNECT result code format and call monitoring Section 2.6, page 39ATZ Set all current parameters to user defined profile Section 2.8, page 41


bgs3_atc_v01000a

Documents

product andthis document

document areproperty

document conventions

contents bgs3

product issubject

registered trademarks

command syntax

release note