CME GPP-3 Specifications Page 13

  • Download
  • Add to my manuals
  • Print
  • Page
    / 164
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 12
3GPP
3GPP TS 27.007 V6.3.0 (2003-
06)
1
3
Release 6
4 AT command syntax
This clause summarizes general aspects on AT commands and issues related to them.
TE software implementors must take account that future versions of this specification may include additional
parameters beyond what is expected in any response to an AT Set Command, Read Command, Test Command, or
unsolicited result code. Implementations must therefore analyse all parameters provided from the TA and discard
(ignore) any parameters received following the parameters expected by the TE software.
For further information refer ITU-T Recommendation V.250 [14].
4.1 Command line
See figure 2 for general structure of a command line. Standardized basic commands are found only in V.250 [14].
GSM/UMTS commands use syntax rules of extended commands. Every extended command has a test command
(trailing =?) to test the existence of the command and to give information about the type of its subparameters.
Parameter type commands also have a read command (trailing ?) to check the current values of subparameters. Action
type commands do not store the values of any of their possible subparameters, and therefore do not have a read
command.
ATCMD1 CMD2=12; +CMD1; +CMD2=,,15; +CMD2?; +CMD2=?<CR>
command line prefix
basic command
(no + prefix)
subparameter
extended command
(prefixed with +)
extended commands are
delimited with semicolon
subparameters
may be omitted
command line
termination character
read command for checking
current subparameter values
test command for checking
possible subparameter values
Figure 2: Basic structure of a command line
If verbose responses are enabled with command V1 and all commands in a command line has been performed
successfully, result code <CR><LF>OK<CR><LF> is sent from the TA to the TE. If numeric responses are enabled
with command V0, result code 0<CR> is sent instead.
If verbose responses are enabled with command V1 and subparameter values of a command are not accepted by the TA
(or command itself is invalid, or command cannot be performed for some reason), result code
<CR><LF>ERROR<CR><LF> is sent to the TE and no subsequent commands in the command line are processed. If
numeric responses are enabled with command V0, result code 4<CR> is sent instead. ERROR (or 4) response may be
replaced by +CME ERROR: <err> (refer clause 9) when command was not processed due to an error related to MT
operation.
Page view 12
1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 163 164

Comments to this Manuals

No comments