SIST ETS 300 642 E2:2003
(Main)Digital cellular telecommunications system (Phase 2) (GSM); AT command set for GSM Mobile Equipment (ME) (GSM 07.07 version 4.2.1)
Digital cellular telecommunications system (Phase 2) (GSM); AT command set for GSM Mobile Equipment (ME) (GSM 07.07 version 4.2.1)
SUBJECT AT+CPIN or AT+CKPD must be mandatory in some cases (phase 2)
Digitalni celični telekomunikacijski sistem (faza 2) ¬– Nabor ukazov AT za GSM mobilno opremo (ME) (GSM 07.07, različica 4.2.1)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital cellular telecommunications system (Phase 2) (GSM); AT command set for GSM Mobile Equipment (ME) (GSM 07.07 version 4.2.1)33.070.50Globalni sistem za mobilno telekomunikacijo (GSM)Global System for Mobile Communication (GSM)ICS:Ta slovenski standard je istoveten z:ETS 300 642 Edition 2SIST ETS 300 642 E2:2003en01-december-2003SIST ETS 300 642 E2:2003SLOVENSKI
STANDARD
SIST ETS 300 642 E2:2003
EUROPEANETS 300 642TELECOMMUNICATIONJuly 1998STANDARDSecond EditionSource: SMGReference: RE/SMG-040707PR1ICS:33.020Key words:Digital cellular telecommunications system, Global System for Mobile communications (GSM)GLOBAL SYSTEM
FOR MOBILE COMMUNICATIONSRDigital cellular telecommunications system (Phase 2);AT command set for GSM Mobile Equipment (ME)(GSM 07.07 version 4.2.1)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEInternet: secretariat@etsi.fr - http://www.etsi.fr - http://www.etsi.orgTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998. All rights reserved.SIST ETS 300 642 E2:2003
Page 2ETS 300 642 (GSM 07.07 version 4.2.1): July 1998Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 642 E2:2003
Page 3ETS 300 642 (GSM 07.07 version 4.2.1): July 1998ContentsForeword.51Scope.72References.73Abbreviations and definitions.93.1Abbreviations.93.2Definitions.94AT command syntax.104.1Command line.104.2Information responses and result codes.104.3ITU-T V.25ter [14] TE-TA interface commands.115General commands.115.1Request manufacturer identification +CGMI.115.2Request model identification +CGMM.125.3Request revision identification +CGMR.125.4Request product serial number identification +CGSN.135.5Select TE character set +CSCS.135.6ITU-T V.25ter [14] generic TA control commands.145.7PCCA STD-101 [17] select wireless network +WS46.145.8Informative examples.156Call control commands and methods.176.1Select type of address +CSTA.176.2ITU-T V.25ter [14] dial command D.176.3Direct dialing from phonebooks.186.4Call mode +CMOD.196.5Hangup call +CHUP.196.6Alternating mode call control method.206.7Select bearer service type +CBST.226.8Radio link protocol +CRLP.236.9Service reporting control +CR.236.10Extended error report +CEER.246.11Cellular result codes +CRC.256.12ITU-T V.25ter [14] call control commands.266.13ITU-T V.25ter [14] data compression commands.266.14Informative examples.267Network service related commands.287.1Subscriber number +CNUM.287.2Network registration +CREG.297.3Operator selection +COPS.297.4Facility lock +CLCK.317.5Change password +CPWD.327.6Calling line identification presentation +CLIP.327.7Calling line identification restriction +CLIR.337.8Connected line identification presentation +COLP.347.9Closed user group +CCUG.357.10Call forwarding number and conditions +CCFC.367.11Call waiting +CCWA.377.12Call hold and multiparty +CHLD.387.13Call transfer +CTFR.387.14Unsupported GSM supplementary services.397.15Informative examples.39SIST ETS 300 642 E2:2003
Page 4ETS 300 642 (GSM 07.07 version 4.2.1): July 19988Mobile Equipment control and status commands.418.1Phone activity status +CPAS.428.2Set phone functionality +CFUN.428.3Enter PIN +CPIN.438.4Battery charge +CBC.448.5Signal quality +CSQ.448.6Mobile Equipment control mode +CMEC.458.7Keypad control +CKPD.468.8Display control +CDIS.478.9Indicator control +CIND.488.10Mobile Equipment event reporting +CMER.498.11Select phonebook memory storage +CPBS.508.12Read phonebook entries +CPBR.518.13Find phonebook entries +CPBF.528.14Write phonebook entry +CPBW.538.15Clock +CCLK.548.16Alarm +CALA.548.17Generic SIM access +CSIM.558.18Informative examples.569 Mobile Equipment errors.609.1Report Mobile Equipment error +CMEE.609.2Mobile Equipment error result code +CME ERROR.609.3Informative examples.61Annex A (normative):Summary of commands from other standards.62Annex B (normative):Summary of result codes.64Annex C (informative):Commands from TIA IS-101.65C.1Select mode +FCLASS.66C.2Buffer threshold setting +VBT.66C.3Calling number ID presentation +VCID.67C.4Receive gain selection +VGR.67C.5Transmit gain selection +VGT.67C.6Initialise voice parameters +VIP.68C.7Inactivity timer +VIT.68C.8Line selection +VLS.68C.9Receive data state +VRX.70C.10Select compression method +VSM.70C.11DTMF and tone generation +VTS.70C.12Tone duration +VTD.71C.13Transmit data state +VTX.71Annex D (informative):Bibliography.72Annex E (informative):Mobile originated alternating voice/data call example.73Annex F (informative):Mobile terminated voice followed by data call example.74Annex G (informative):Voice call example.75History.76SIST ETS 300 642 E2:2003
Page 5ETS 300 642 (GSM 07.07 version 4.2.1): July 1998ForewordThis draft second edition European Telecommunication Standard (ETS) has been produced by theSpecial Mobile Group (SMG) of the European Telecommunications Standards Institute (ETSI).This ETS specifies a profile of AT commands and recommends that this profile be used for controllingMobile Equipment (ME) functions and GSM network services from a Terminal Equipment (TE) throughTerminal Adaptor (TA) for the Digital cellular telecommunications system.Transposition datesDate of adoption of this ETS:19 June 1998Date of latest announcement of this ETS (doa):31 October 1998Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 April 1999Date of withdrawal of any conflicting National Standard (dow):30 April 1999SIST ETS 300 642 E2:2003
Page 6ETS 300 642 (GSM 07.07 version 4.2.1): July 1998Blank pageSIST ETS 300 642 E2:2003
Page 7ETS 300 642 (GSM 07.07 version 4.2.1): July 19981ScopeThis European Telecommunications Standard (ETS) specifies a profile of AT commands andrecommends that this profile be used for controlling Mobile Equipment (ME) functions and GSM networkservices from a Terminal Equipment (TE) through Terminal Adaptor (TA). The command prefix +C isreserved for Digital Cellular in ITU-T Recommendation V.25ter [14]. This ETS has also the syntax detailsused to construct these extended GSM commands. Commands from ITU-T Recommendation V.25ter[14] and existing digital cellular standards (TIA IS-99 [15] and TIA IS-135 [16]) are used wheneverapplicable. Some of the new commands are defined such way that they can be easily applied to ME ofnetworks other than GSM. ITU-T T.31 [11] and ITU-T T.32 [12] fax AT commands may be used for GSMfax transmission from TE.This ETS assumes an abstract architecture comprising a TE (e.g. a computer) and a ME interfaced by aTA (see figure 1). The span of control of the defined commands should allow to handle any physicalimplementation that this abstract architecture may lead to:-TA, ME and TE as three separate entities;-TA integrated under the ME cover, and the TE implemented as a separate entity;-TA integrated under the TE cover, and the ME implemented as a separate entity;-TA and ME integrated under the TE cover as a single entity.The commands described in this ETS may be observed on the link between the TE and the TA. However,most of the commands retrieve information about the ME, not about the TA.TETAMEAT cmdsresponsesME controlME statusUSER & APPLICATIONSNETWORKnetwork messagesFigure 1: SetupInterface between TE and TA is intended to operate over existing serial (ITU-T Recommendation V.24)cables, infrared link, and all link types with similar behaviour. For correct operation many of the definedcommands require eight bit data and therefore it is recommended that TE-TA link is set to eight bits/ bytemode. (For infrared operation implementation refer informative references IrDA and TIA-617.) Interfacebetween TA and ME is dependent on the interface in the ME.2ReferencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]GSM 02.02 (ETS 300 501): "Digital cellular telecommunication system(Phase 2); Bearer Services (BS) supported by a GSM Public Land MobileNetwork (PLMN)".[2]GSM 02.03 (ETS 300 502): "Digital cellular telecommunication system(Phase 2); Teleservices supported by a GSM Public Land Mobile Network(PLMN)".[3]GSM 02.81 (ETS 300 514): "Digital cellular telecommunication system(Phase 2); Line identification supplementary services - Stage 1".SIST ETS 300 642 E2:2003
Page 8ETS 300 642 (GSM 07.07 version 4.2.1): July 1998[4]GSM 02.82 (ETS 300 515): "Digital cellular telecommunication system(Phase 2); Call Forwarding (CF) supplementary services - Stage 1".[5]GSM 02.83 (ETS 300 516): "Digital cellular telecommunication system(Phase 2); Call Waiting (CW) and Call Hold (HOLD) supplementary services -Stage 1".[6]GSM 02.88 (ETS 300 520): "Digital cellular telecommunication system(Phase 2); Call Barring (CB)
supplementary services - Stage 1".[7]GSM 03.03 (ETS 300 523): "Digital cellular telecommunication system(Phase 2); Numbering, addressing and identification".[8]GSM 04.08 (ETS 300 557): "Digital cellular telecommunication system(Phase 2); Mobile radio interface layer 3 specification".[9]GSM MoU SE.13, GSM MoU Association Permanent Reference DocumentSE.13 (October 1994): "GSM Mobile Network Codes and Names".[10]ITU-T Recommendation E.212: "Identification plan for land mobile stations".[11]ITU-T Recommendation T.31: "Asynchronous facsimile DCE control, serviceclass 1".[12]ITU-T Recommendation T.32: "Asynchronous facsimile DCE control, serviceclass 2".[13]ITU-T Recommendation T.50: "International Reference Alphabet (IRA)(Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bitcoded character set for information exchange".[14]ITU-T Draft new Recommendation V.25ter: "Serial asynchronous automaticdialling and control".[15]Telecommunications Industry Association TIA IS-99: "Data Services OptionStandard for Wideband Spread Spectrum Digital Cellular System”.[16]Telecommunications Industry Association TIA IS-135: "800 MHz CellularSystems, TDMA Services, Async Data and Fax".[17]Portable Computer and Communications Association PCCA STD-101 DataTransmission Systems and Equipment: “Serial Asynchronous Automatic Dialingand Control for Character Mode DCE on Wireless Data Services”[18]GSM 04.22 (ETS 300 563): "Digital cellular telecommunication system(Phase 2); Radio Link Protocol (RLP) for data and telematic services on theMobile Station - Base Station System (MS - BSS) interface and the Base StationSystem - Mobile-services Switching Centre (BSS - MSC) interface".[19]GSM 02.30 (ETS 300 511): "Digital cellular telecommunication system(Phase 2); Man Machine Interface (MMI) of the Mobile Station (MS)”.[20]GSM 05.08 (ETS 300 578): "Digital cellular telecommunication system(Phase 2); Radiosubsystem link control”.[21]GSM 02.85 (ETS 300 518): "Digital cellular telecommunication system(Phase 2); Closed User Group (CUG) supplementary services - Stage 1”.[22]GSM 02.84 (ETS 300 517): “Digital cellular telecommunication system(Phase 2); MultiParty (MPTY) supplementary services - Stage 1”.SIST ETS 300 642 E2:2003
Page 9ETS 300 642 (GSM 07.07 version 4.2.1): July 19983Abbreviations and definitions3.1AbbreviationsFor the purposes of this ETS the following abbreviations apply:ATATtention; this two-character abbreviation is always used to start a command line to besent from TE to TABCDBinary Coded DecimalETSIEuropean Telecommunications Standards InstituteIMEIInternational Mobile station Equipment IdentityIRAInternational Reference Alphabet (ITU-T T.50 [13])IrDAInfrared Data AssociationISOInternational Standards OrganisationITU-TInternational Telecommunication Union - Telecommunications Standardization SectorMEMobile Equipment, e.g. a GSM phone (equal to MS; Mobile Station)MoUMemorandum of Understanding (GSM operator joint)PCCAPortable Computer and Communications AssociationRLPRadio Link ProtocolSIMSubscriber Identity ModuleTATerminal Adaptor, e.g. a GSM data card (equal to DCE; Data Circuit terminatingEquipment)TETerminal Equipment, e.g. a computer (equal to DTE; Data Terminal Equipment)TIATelecommunications Industry Association3.2DefinitionsFor the purposes of this ETS the following syntactical definitions apply (refer also clause 4):Carriage return character, which value is specified with command S3.Linefeed character, which value is specified with command S4.<.>Name enclosed in angle brackets is a syntactical element. Brackets themselvesdo not appear in the command line.[.]Optional subparameter of a command or an optional part of TA informationresponse is enclosed in square brackets. Brackets themselves do not appear inthe command line. When subparameter is not given in parameter typecommands, new value equals to its previous value. In action type commands,action should be done on the basis of the recommended default setting of thesubparameter.underlineUnderlined defined subparameter value is the recommended default setting ofthis subparameter. In parameter type commands, this value should be used infactory settings which are configured by V.25ter [14] command &F0. In actiontype commands, this value should be used when subparameter is not given.SIST ETS 300 642 E2:2003
Page 10ETS 300 642 (GSM 07.07 version 4.2.1): July 19984AT command syntaxThis clause summarizes general aspects on AT commands and issues related to them. For furtherinformation refer ITU-T Recommendation V.25ter [14].4.1Command lineSee figure 2 for general structure of a command line. Standardized basic commands are found only inV.25ter [14]. GSM commands use syntax rules of extended commands. Every extended command has atest command (trailing =?) to test the existence of the command and to give information about the type ofits subparameters. Parameter type commands also have a read command (trailing ?) to check the currentvalues of subparameters. Action type commands do not store the values of any of their possiblesubparameters, and therefore do not have a read command.ATCMD1 CMD2=12; +CMD1; +CMD2=,,15; +CMD2?; +CMD2=?command line prefixbasic command(no + prefix)subparameterextended command(prefixed with +)extended commands aredelimited with semicolonsubparametersmay be omittedcommand linetermination characterread command for checkingcurrent subparameter valuestest command for checkingpossible subparameter valuesFigure 2: Basic structure of a command lineIf verbose responses are enabled with command V1 and all commands in a command line has beenperformed successfully, result code OK is sent from the TA to the TE. If numericresponses are enabled with command V0, result code 0 is sent instead.If verbose responses are enabled with command V1 and subparameter values of a command are notaccepted by the TA (or command itself is invalid, or command cannot be performed for some reason),result code ERROR is sent to the TE and no subsequent commands in the commandline are processed. If numeric responses are enabled with command V0, result code 4 is sentinstead. ERROR (or 4) response may be replaced by +CME ERROR: (refer clause 9) whencommand was not processed due to an error related to ME operation.4.2Information responses and result codesThe TA response for the example command line of figure 2 could be as shown in figure 3. Here, verboseresponse format is enabled with command V1. If numeric format V0 would have been used, headers of information responses would have been left out and final result code changed to 0.+CMD2: 3,0,15,"GSM"+CMD2: (0-3),(0,1),(0-12,15),("GSM","IRA")OKinformation response to +CMD2?information response to +CMD2=?final result codealso string type subparameters possibleshows acceptable ranges of each subparameterFigure 3: Response to a command lineSIST ETS 300 642 E2:2003
Page 11ETS 300 642 (GSM 07.07 version 4.2.1): July 1998So called intermediate result codes inform about progress of TA operation (e.g. connection establishmentCONNECT), and so called unsolicited result codes indicate occurrence of an event not directly associatedwith issuance of a command from TE (e.g. ring indication RING).4.3ITU-T V.25ter [14] TE-TA interface commandsTable 1 summarizes V.25ter [14] commands relating to command line and response formatting, and TA-TE interface operation. All are applicable to GSM terminals.Table 1: V.25ter commands relating to TE-TA interfaceCommandSectionImpl.Use in GSMS3=[]6.2.1mand.command line termination character (mandatory default setting IRA13)S4=[]6.2.2mand.response formatting character (recommended default IRA 10)S5=[]6.2.3mand.command line editing character (recommended default IRA 8)E[]6.2.4mand.command echo (recommended default 1 i.e. TA echoes commandsback)Q[]6.2.5mand.result code suppression (recommended default 0 i.e. TA transmitsresult codes)V[]6.2.6mand.TA response format (recommended default 1 i.e. verbose format)X[]6.2.7mand.defines CONNECT result code format; values manufacturer specific&C[]6.2.8mand.determines how ITU-T V.24 circuit 109 (or equivalent) relates to thedetection of received line signal from remote end (recommendeddefault 1 i.e. 109 operation relates to detection of received signal)&D[]6.2.9mand.determines how TA responds when ITU-T V.24 circuit 108/2 (orequivalent) is changed from ON to OFF condition during online datastate+IPR=[]6.2.10opt.fixed TE data rate (recommended default 0 i.e. automatic detection)+ICF=[[,]]6.2.11opt.TE-TA character framing (recommended default 3,3 i.e. eight databits, no parity, 1 stop bit)+IFC=[[,]]6.2.12opt.TE-TA local flow control (recommended default 2,2 i.e. TE uses ITU-TV.24 circuit 133 (or equivalent), and TA circuit 106 (or equivalent))+ILRR=[]6.2.13opt.determines whether the used local TE-TA data rate is informed usingintermediate result code +ILRR:
before going online datastate after call answering or originating5General commandsITU-T Recommendation V.25ter [14] includes 'Generic DCE Control' commands with the prefix +G. Thesecommands are for the identification of the TA. Four of those commands are adapted here to be theidentification commands of the ME. Syntax is otherwise similar but the prefix is +CG. TIA IS-99 [15] usessame commands for ME identification.5.1Request manufacturer identification +CGMITable 2: +CGMI action command syntaxCommandPossible response(s)+CGMI+CME ERROR: +CGMI=?DescriptionExecution command causes the TA to return one or more lines of information text ,determined by the ME manufacturer, which is intended to permit the user of the TA to identify themanufacturer of the ME to which it is connected to. Typically, the text will consist of a single line containingthe name of the manufacturer, but manufacturers may choose to provide more information if desired.Refer subclause 9.2 for possible values.SIST ETS 300 642 E2:2003
Page 12ETS 300 642 (GSM 07.07 version 4.2.1): July 1998Defined values: the total number of characters, including line terminators, in the information text shallnot exceed 2048 characters.Text shall not contain the sequence 0 or OKImplementationOptional.5.2Request model identification +CGMMTable 3: +CGMM action command syntaxCommandPossible response(s)+CGMM+CME ERROR: +CGMM=?DescriptionExecution command causes the TA to return one or more lines of information text , determinedby the ME manufacturer, which is intended to permit the user of the TA to identify the specific model of theME to which it is connected to. Typically, the text will consist of a single line containing the name of theproduct, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 forpossible values.Defined values: the total number of characters, including line terminators, in the information text shall notexceed 2048 characters.Text shall not contain the sequence 0 or OKImplementationOptional.5.3Request revision identification +CGMRTable 4: +CGMR action command syntaxCommandPossible response(s)+CGMR+CME ERROR: +CGMR=?DescriptionExecution command causes the TA to return one or more lines of information text ,determined by the ME manufacturer, which is intended to permit the user of the TA to identify the version,revision level or date, or other pertinent information of the ME to which it is connected to. Typically, thetext will consist of a single line containi
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.