AT Commands For GPRS/PS
No | Command | Description |
L0801 | AT+CGREG | GPRS network registration status |
L0802 | AT+CGATT | Packet domain attach or detach |
L0803 | AT+CGACT | GPRS network registration status |
L0804 | AT+CGDCONT | Define PDP context |
L0805 | AT+CGDSCONT | Define Secondary PDP Context |
L0806 | AT+CGTFT | Traffic Flow Template |
L0807 | AT+CGQREQ | Quality of service profile (requested) |
L0808 | AT+CGEQREQ | 3G quality of service profile (requested) |
L0809 | AT+CGQMIN | Quality of service profile (minimum acceptable) |
L0810 | AT+CGEQMIN | 3G quality of service profile (minimum acceptable) |
L0811 | AT+CGDATA | Enter data state |
L0812 | AT+CGPADDR | Show PDP address |
L0813 | AT+CGCLASS | GPRS mobile station class |
L0814 | AT+CGEREP | GPRS event reporting |
L0815 | AT+CGAUTH | Set type of authentication for PDP-IP connections of GPRS |
L0801 AT+CGREG GPRS Network Registration Status
This command controls the presentation of an unsolicited result code “+CGREG: <stat>”
when <n>=1 and there is a change in the MT’s GPRS network registration status.
The read command returns the status of result code presentation and an integer <stat>
which shows whether the network has currently indicated the registration of the MT.
T) AT+CGREG=? | +CGREG: (list of supported <n>s) OK |
R) AT+CGREG? | +CGREG: <n>,<stat>[,<lac>,<ci>] OK |
W) AT+CGREG=<n> | OK |
E) AT+CGREG | OK |
<n> |
0 disable network registration unsolicited result code 1 enable network registration unsolicited result code +CGREG: <stat> 2 there is a change in the ME network registration status or a change of the network cell: +CGREG: <stat>[,<lac>,<ci>] |
<stat> |
0 not registered, ME is not currently searching an operator to register to 1 registered, home network 2 not registered, but ME is currently trying to attachor searching an operator to register to 3 registration denied 4 unknown 5 registered, roaming |
<lac> | Two bytes location area code in hexadecimal format (e.g.”00C3” equals 193in decimal). |
<ci> |
Cell ID in hexadecimal format. GSM Maximum is two byte WCDMA Maximum is four byte TDS-CDMA Maximum is four byte |
NOTE
The <lac> not supported in CDMA/HDR mode
The <ci> not supported in CDMA/HDR mode
Example |
AT+CGREG=? +CGREG: (0-1) OK AT+CGREG? +CGREG: 0,0 OK |
L0802 AT+CGATT Packet Domain Attach or Detach
The write command is used to attach the MT to, or detach the MT from, the Packet Domain service.
The read command returns the current Packet Domain service state.
T) AT+CGATT=? | +CGATT: (list of supported <state>s) OK |
R) AT+CGATT? | +CGATT: <state> OK |
W) AT+CGATT=<state> |
OK or ERROR or +CME ERROR: <err> |
<state> |
Indicates the state of Packet Domain attachment: 0 detached 1 attached |
Example |
AT+CGATT? +CGATT: 0 OK AT+CGATT=1 OK |
L0803 AT+CGACT PDP context activate or deactivate
The write command is used to activate or deactivate the specified PDP context (s).
T) AT+CGACT=? | + CGACT: (list of supported <state>s) OK |
R) AT+CGACT? | +CGACT: [<cid>, <state> [<CR><LF>+CGACT: <cid>, <state> […]]] OK |
W) AT+CGACT=<state>[,<cid>] |
OK or ERROR or +CME ERROR: <err> |
<state> |
Indicates the state of PDP context activation: 0 deactivated 1 activated |
<cid> |
A numeric parameter which specifies a particular PDP context definition (see AT+CGDCONT command).1…16 |
Example |
AT+CGACT=? +CGACT: (0,1) OK AT+CGACT? +CGACT: 1,1 OK AT+CGACT=0,1 OK |
L0804 AT+CGDCONT Define PDP Context
The set command specifies PDP context parameter values for a PDP context identified by the (local) context identification parameter <cid>.
The number of PDP contexts that may be in a defined state at the same time is given by the range returned by the test command.
A special form of the write command (AT+CGDCONT=<cid>) causes the values for context <cid> to become undefined.
T) AT+CGDCONT=? |
+CGDCONT: (range of supported<cid>s),<PDP_type>,,,(list of supported <d_comp>s),(list of supported <h_comp>s) (list of <ipv4_ctrl>s),(list of <emergency_flag>s) OK or ERROR |
R) AT+CGDCONT? |
+CGDCONT: [<cid>, <PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_comp><ipv4_ctrl>,<emergency_flag>[<CR><LF> +CGDCONT: <cid>, <PDP_type>, <APN>,<PDP_addr>, <d_comp>,<h_comp>< ipv4_ctrl>,<emergency_flag>[…]]] OK or ERROR |
W) AT+CGDCONT=<cid>[,<PDP_type>[,<APN>[,<PDP_addr>[,<d_comp>[,<h_comp>[,<pv4_ctrl>[,<emergency_flag>]]]]]] |
OK or ERROR |
E) AT+CGDCONT |
OK or ERROR |
<cid> |
(PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition. The parameter is local to the TE-MT interface & is used in other PDP context-related commands. The range of permitted values (minimum value = 1) is returned by the test form of the command.1…16,100…179 |
<PDP_type> |
(Packet Data Protocol type) a string parameter which specifies the type of packet data protocol. IP Internet Protocol PPP Point to Point Protocol IPV6 Internet Protocol Version 6 IPV4V6 Dual PDN Stack |
<APN> |
(Access Point Name) a string parameter which is a logical name that is used to select the GGSN or the external packet data network. |
<PDP_addr> |
A string parameter that identifies the MT in the address space applicable to the PDP. Read command will continue to return the null string even if an address has been allocated during the PDP startup procedure. The allocated address may be read using command AT+CGPADDR. |
<d_comp> |
A numeric parameter that controls PDP data compression, this value may depend on platform: 0 off (default if value is omitted) 1 on 2 V.42bis |
<h_comp> |
A numeric parameter that controls PDP header compression, this value may depend on platform: 0 off (default if value is omitted) 1 on 2 RFC1144 3 RFC2507 4 RFC3095 |
Example |
AT+CGDCONT =? +CGDCONT: (1-24,100-179),”IP”,,,(0-2),(0-4),(0-1),(0-1) +CGDCONT: (1-24,100-179),”PPP”,,,(0-2),(0-4),(0-1),(0-1) +CGDCONT: (1-24,100-179),”IPV6″,,,(0-2),(0-4),(0-1),(0-1) +CGDCONT: (1-24,100-179),”IPV4V6″,,,(0-2),(0-4),(0-1),(0-1) OK AT+ CGDCONT? +CGDCONT: 1,”IP”,””,”0.0.0.0″,0,0 OK |
L0805 AT+CGDSCONT Define Secondary PDP Context
The set command specifies PDP context parameter values for a Secondary PDP context identified
by the (local) context identification parameter, <cid>. The number of PDP contexts
that may be in a defined state at the same time is given by the range returned by the test command.
A special form of the set command, AT+CGDSCONT=<cid> causes the values for context number <cid> to become undefined.
T) AT+CGDSCONT=? |
+CGDSCONT: (range of supported <cid>s),(list of <p_cid>s for active primary contexts), <PDP_type>,,,(list of supported<d_comp>s),(list of supported <h_comp>s) OK or ERROR |
R) AT+CGDSCONT? |
+CGDSCONT: [<cid>,<p_cid>,<d_comp>,<h_comp> [<CR><LF>+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp> […]]] OK or ERROR |
W) AT+CGDSCONT=<cid>[,<p_cid>[,<d_comp>[,<h_comp>]]] |
OK or ERROR |
<cid> | a numeric parameter which specifies a particular PDP context definition.The parameter is local to the TE-MT interface and is used in other PDP context-related commands. The range of permitted values (minimum value =1) is returned by the test form of the command. |
<p_cid> | a numeric parameter which specifies a particular PDP context definition which has been specified by use of the +CGDCONT command. The parameter is local to the TE-MT interface. The list of permitted values isreturned by the test form of the command. |
<PDP_type> |
(Packet Data Protocol type) a string parameter which specifies the type of packet data protocol. IP Internet Protocol PPP Point to Point Protocol IPV6 Internet Protocol Version 6 IPV4V6 Dual PDN Stack |
<d_comp> |
a numeric parameter that controls PDP data compression (applicable for SNDCPonly) (refer 3GPP TS 44.065 [61]) 0 off 1 on (manufacturer preferred compression) 2 V.42bis Other values are reserved. |
<h_comp> |
a numeric parameter that controls PDP header compression (refer 3GPP TS 44.065 [61] and 3GPP TS 25.323 [62]) 0 off 1 on (manufacturer preferred compression) 2 RFC1144 (applicable for SNDCP only) 3 RFC2507 4 RFC3095 (applicable for PDCP only) Other values are reserved. |
NOTE
The <cid>s for network-initiated PDP contexts will have values outside the ranges
indicated for the <cid> in the test form of the commands +CGDCONT and +CGDSCONT.
Example |
AT+CGDSCONT=? +CGDSCONT: (1-24,100-179),(),”IP”,(0-2),(0-4) +CGDSCONT: (1-24,100-179),(),”PPP”,(0-2),(0-4) +CGDSCONT: (1-24,100-179),(),”IPV6″,(0-2),(0-4) +CGDSCONT: (1-24,100-179),(),”IPV4V6″,(0-2),(0-4) OK AT+CGDSCONT?+CGDSCONT: 2,1,0,0 OK AT+CGDSCONT=2,1 OK |
L0806 AT+CGTFT Traffic Flow Template
This command allows the TE to specify a Packet Filter – PF for a Traffic Flow Template – TFT
that is used in the GGSN in UMTS/GPRS and Packet GW in EPS for routing of packets onto different QoS flows towards the TE.
The concept is further described in the 3GPP TS 23.060 [47].
A TFT consists of from one and up to 16 Packet Filters, each identified by a unique <packet filter identifier>.
A Packet Filter also has an <evaluation precedence index> that is unique within all TFTs associated
with all PDP contexts that are associated with the same PDP address.
T) AT+CGTFT=? |
+CGTFT: <PDP_type>,(list of supported <packet filter identifier>s),(list of supported <evaluation precedence index>s),(list of supported <source address and subnet mask>s),(list of supported <protocol number (ipv4) / next header (ipv6)>s),(list of supported <destination port range>s),(list of supported <source port range>s),(list of supported <ipsec security parameter index (spi)>s),(list of supported <type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>s),(list of supported <flow label (ipv6)>s),(list of supported<direction>s)[<CR><LF>+CGTFT: <PDP_type>,(list of supported <packet filter identifier>s),(list of supported <evaluation precedence index>s),(list of supported <source address and subnet mask>s),(list of supported <protocol number (ipv4) / next header (ipv6)>s),(list of supported <destination port range>s),(list of supported <source port range>s),(list of supported <ipsec security parameter index (spi)>s),(list of supported <type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>s),(list of supported <flow label (ipv6)>s),(list of supported<direction>s) […]] OK or ERROR |
R) AT+CGTFT? |
+CGTFT: [<cid>,<packet filter identifier>,<evaluation precedence index>,<source address and subnet mask>,<protocol number (ipv4) / next header (ipv6)>,<destination port range>,<source port range>,<ipsec security parameter index (spi)>,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>,<flow label (ipv6)>,<direction>[<CR><LF>+CGTFT: <cid>,<packet filter identifier>,<evaluation precedence index>,<source address and subnet mask>,<protocol number (ipv4) / next header (ipv6)>,<destination port range>,<source port range>,<ipsec security parameter index (spi)>,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>,<flow label (ipv6)>,<direction>[…]]] OK or ERROR |
W) AT+CGTFT=<cid>[,[<packetfilter identifier>,<evaluationprecedenceindex>[,<source address and subnet mask>[,<protocol number (ipv4) / next header (ipv6)>[,<destination port range>[,<source port range>[,<ipsec security parameter index (spi)>[,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>[,<flow label (ipv6)>[,<direction>]]]]]]]]]] |
OK or ERROR |
E) AT+CGTFT |
OK or ERROR |
<cid> |
a numeric parameter which specifies a particular PDP context definition (see the AT+CGDCONT and AT+CGDSCONT commands). |
<PDP_type> |
(Packet Data Protocol type) a string parameter which specifies the type of packet data protocol. IP Internet Protocol PPP Point to Point Protocol IPV6 Internet Protocol Version 6 IPV4V6 Dual PDN Stack |
<packet filter identifier> | a numeric parameter, value range from 1 to 16. |
<evaluation precedenceindex> | a numeric parameter. The value range is from 0 to 255. |
<source address and subnet mask> |
string type The string is given as dot-separated numeric (0-255) parameters on the form: “a1.a2.a3.a4.m1.m2.m3.m4” for IPv4 or “a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10. m11.m12.m13.m14.m15.m16″, for IPv6. |
<protocol number (ipv4) /next header (ipv6)> | a numeric parameter, value range from 0 to 255. |
<destination port range> | string type. The string is given as dot-separated numeric (0-65535)parameters on the form “f.t”. |
<source port range> | string type. The string is given as dot-separated numeric (0-65535)parameters on the form “f.t”. |
<ipsec securityparameter index (spi)> | numeric value in hexadecimal format. The value range is from 00000000to FFFFFFFF. |
<type of service (tos) (ipv4) and mask / trafficclass (ipv6) and mask> | string type. The string is given as dot-separated numeric (0-255) parameters on the form “t.m”. |
<flow label (ipv6)> | numeric value in hexadecimal format. The value range is from 00000 toFFFFF. Valid for IPv6 only. |
<direction> |
a numeric parameter which specifies the transmission direction in which the packet filter shall be applied. 0 Pre-Release 7 TFT filter (see 3GPP TS 24.008 [8], table 10.5.162) 1 Uplink 2 Downlink 3 Birectional (Up & Downlink) |
Example |
AT+CGTFT=? +CGTFT: “IP”,(1-16),(0-255),,(0-255),(0-65535.0-65535),(0-65535.0-65535),(0-FFFFFFFF),(0-255.0-255),(0-FF FFF) +CGTFT:”PPP”,(1-16),(0-255),,(0-255),(0-65535.0-65535),(0-65535.0-65535),(0-FFFFFFFF),(0-255.0-255),(0- FFFFF) +CGTFT:”IPV6″,(1-16),(0-255),,(0-255),(0-65535.0-65535),(0-65535.0-65535),(0-FFFFFFFF),(0-255.0-255),(0- FFFFF) +CGTFT:”IPV4V6″,(1-16),(0-255),,(0-255),(0-65535.0-65535),(0-65535.0-65535),(0-FFFFFFFF),(0-255.0-255),( 0-FFFFF) OK AT+CGTFT? +CGTFT: 2,1,0,”74.125.71.99.255.255.255.255″,0,0.0,0.0,0,0.0,0 OK AT+CGTFT=2,1,0,”74.125.71.99.255.255.255.255″ |
L0807 AT+CGQREQ Quality of Service Profile (Requested)
This command allows the TE to specify a Quality of Service Profile that is used
when the MT sends an Activate PDP Context Request message to the network.
A special form of the set command (AT+CGQREQ=<cid>) causes the requested profile for context number <cid> to become undefined.
T) AT+CGQREQ=? |
+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) [<CR><LF>+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 or ERROR |
R) AT+CGQREQ? |
+CGQREQ: [<cid>, <precedence >, <delay>, <reliability>, <peak>, <mean>[<CR><LF> +CGQREQ: <cid>, <precedence >, <delay>, <reliability.>, <peak>, <mean>[…]]] OK or ERROR |
W) AT+CGQREQ=<cid>[,<precedence>[,<delay>[,<reliability>[,<peak> [,<mean>]]]]] |
OK or ERROR |
E) AT+CGQREQ |
OK or ERROR |
<cid> | A numeric parameter which specifies a particular PDP context definition (seeAT+CGDCONT command). The range is from 1 to 42,100 to 179. |
<PDP_type> |
(Packet Data Protocol type) a string parameter which specifies the type of packet data protocol. IP Internet Protocol PPP Point to Point Protocol IPV6 Internet Protocol Version 6 IPV4V6 Dual PDN Stack |
<precedence> |
A numeric parameter which specifies the precedence class: 0 network subscribed value 1 high priority 2 normal priority 3 low priority |
<delay> |
A numeric parameter which specifies the delay class: 0 network subscribed value 1 delay class 1 2 delay class 2 3 delay class 3 4 delay class 4 |
<reliability> |
A numeric parameter which specifies the reliability class: 0 network subscribed value 1 Non real-time traffic, error-sensitive application that cannot cope with data loss 2 Non real-time traffic, error-sensitive application that can cope with infrequent data loss 3 Non real-time traffic, error-sensitive application that can cope with data loss, GMM/-SM, and SMS 4 Real-time traffic, error-sensitive application that can cope with data loss 5 Real-time traffic error non-sensitive application that can cope with data loss |
<peak> |
A numeric parameter which specifies the peak throughput class: 0 network subscribed value 1 Up to 1000 (8 kbit/s) 2 Up to 2000 (16 kbit/s) 3 Up to 4000 (32 kbit/s) 4 Up to 8000 (64 kbit/s) 5 Up to 16000 (128 kbit/s) 6 Up to 32000 (256 kbit/s) 7 Up to 64000 (512 kbit/s) 8 Up to 128000 (1024 kbit/s) 9 Up to 256000 (2048 kbit/s) |
<mean> |
A numeric parameter which specifies the mean throughput class: 0 network subscribed value 1 100 (~0.22 bit/s) 2 200 (~0.44 bit/s) 3 500 (~1.11 bit/s) 4 1000 (~2.2 bit/s) 5 2000 (~4.4 bit/s) 6 5000 (~11.1 bit/s) 7 10000 (~22 bit/s) 8 20000 (~44 bit/s) 9 50000 (~111 bit/s) 10 100000 (~0.22 kbit/s) 11 200000 (~0.44 kbit/s) 12 500000 (~1.11 kbit/s) 13 1000000 (~2.2 kbit/s) 14 2000000 (~4.4 kbit/s) 15 5000000 (~11.1 kbit/s) 16 10000000 (~22 kbit/s) 17 20000000 (~44 kbit/s) 18 50000000 (~111 kbit/s) 31 optimization |
Example |
AT+CGQREQ=? +CGQREQ: “IP”,(0-3),(0-4),(0-5),(0-9),(0-18,31) +CGQREQ: “PPP”,(0-3),(0-4),(0-5),(0-9),(0-18,31) +CGQREQ: “IPV6”,(0-3),(0-4),(0-5),(0-9),(0-18,31) +CGQREQ: “IPV4V6”,(0-3),(0-4),(0-5),(0-9),(0-18,31) OK AT+CGREG?+CGQREQ: OK |
L0808 AT+CGEQREQ 3G Quality of Service Profile (Requested)
The test command returns values supported as a compound value.
The read command returns the current settings for each defined context for which a QOS was explicitly specified.
The write command allows the TE to specify a Quality of Service Profile for the context identified
by the context identification parameter <cid> which is used
when the MT sends an Activate PDP Context Request message to the network.
A special form of the write command, AT+CGEQREQ=<cid> causes the requested
profile for context number <cid> to become undefined.
T) AT+CGEQREQ=? |
+CGEQREQ: <PDP_type>,(list of supported <Traffic class>s),(list of supported <Maximum bitrate UL>s),(list of supported <Maxim um bitrate DL>s),(list of supported <Guaranteed bitrate UL>s,(list of supported <Guaranteed bitrate DL>s),(list of supported <Deliv ery order>s),(list of supported <Maximum SDU size>s),(list of supported <SDU error ratio>s),(list of supported <Residual bit errorRatio>s),(list of supported <Delivery of erroneous SDUs>s),(list ofSupported <Transfer delay>s),(list of supported <Traffic handling priority>s) OK or ERROR |
R) AT+CGEQREQ? |
+CGEQREQ: [<cid>,<Traffic class>,<Maximum bitrate UL>,<Maximum bitrate DL>,<Guaranteed bitrate UL>,<Guaranteed bitrateDL>,<Delivery order>,<Maximum SDU size>,<SDU error ratio>,<Residual bit error ratio>,<Delivery of erroneous SDUs>,<TransferDelay>,<Traffic handling priority>][<CR><LF>+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>[…]] OK or ERROR |
W) AT+CGEQREQ=<cid>[,<Traffic class>[,<Maximum bitrate UL>[,<Maximum bitrate DL>[,<Guaranteed bitrateUL>[,<Guaranteed bitrate DL>[,<Delivery order>[,<Maximum SDU size>[,<SDU error ratio>[,<Residual bit error ratio>[,<Delivery of erroneous SDUs>[,<Transfer delay>[,<Traffic handling priority>]]]]]]]]]]]] |
OK or ERROR or +CME ERROR: <err> |
E) AT+ CGEQREQ |
OK or ERROR |
<cid> |
Parameter specifies a particular PDP context definition. The parameter is also used in other PDP context-related commands. The range is from 1 to 24,100 to 179. |
<Traffic class> |
0 conversational 1 streaming 2 interactive 3 background 4 subscribed value |
<Maximum bitrate UL> |
This parameter indicates the maximum number of kbits/s delivered to UMTS(up-link traffic)at a SAP. As an example a bitrate of 32kbit/s would be specified as 32(e.g. AT+CGEQREQ=…,32,…). The range is from 0 to 8460. The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Maximum bitrate DL> |
This parameter indicates the maximum number of kbits/s delivered to UMTS(down-link traffic)at a SAP. As an example a bitrate of 32kbit/s would be specified as 32(e.g. AT+CGEQREQ=…,32,…). The range is from 0 to 8460. The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Guaranteed bitrate UL> |
This parameter indicates the guaranteed number of kbit/s delivered to UMTS(up-link traffic)at a SAP(provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as 32(e.g.AT+CGEQREQ=…,32,…). The range is from 0 to 8460. The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Guaranteed bitrate DL> |
This parameter indicates the guaranteed number of kbit/s delivered to UMTS(down-link traffic)at a SAP(provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as 32(e.g.AT+CGEQREQ=…,32,…). The range is from 0 to 8460. The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Delivery order> |
This parameter indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not. 0 no 1 yes 2 subscribed value |
<Maximum SDU size> |
This parameter indicates the maximum allowed SDU size in octets. The range is from 0 to 1520. The default value is 0. If the parameter is set to ‘0’ the subscribed value will be requested. |
<SDU error ratio> |
This parameter indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. As an example a target SDU error ratio of 5*10-3 would be specified as “5E3”(e.g.AT+CGEQREQ=..,”5E3”,…). “0E0” subscribed value “1E2” “7E3” “1E3” “1E4” “1E5” “1E6” “1E1” |
<Residual bit error ratio> |
This parameter indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. 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” |
<Delivery of erroneous SDUs> |
This parameter indicates whether SDUs detected as erroneous shall be delivered or not. 0 no 1 yes 2 no detect 3 subscribed value |
<Transfer delay> |
This parameter indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP,in milliseconds.The range is from 0 to 4000. The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Traffic handling priority> |
This parameter specifies the relative importance for handling of all SDUs belonging to the UMTSBearer compared to the SDUs of the other bearers.The range is from 0 to 3. The default value is 0. If the parameter is set to ‘0’ the subscribed value will be requested. |
<PDP_type> |
(Packet Data Protocol type) a string parameter which specifies the type of packet data protocol. IP Internet Protocol PPP Point to Point Protocol IPV6 Internet Protocol Version 6 IPV4V6 Dual PDN Stack |
Example |
AT+CGEQREQ=? +CGEQREQ: “IP”,(0-4),(0-384),(0-7168),(0-384),(0-7168),(0-2),(0-1520),(“0E0″,”1E1″,”1E2″,”7E3″,”1E3″,”1E4″,”1E5″,”1E6”),(“0E0″,”5E2″,”1E2″,”5E3″,”4E3″,”1E3″,”1E4″,”1E5″,”1E6″,”6E8”),(0-3),(0-4000),(0-3) ,(0,1),(0,1)+CGEQREQ: “PPP”,(0-4),(0-384),(0-7168),(0-384),(0-7168),(0-2),(0-1520),(“0E0″,”1E1″,”1E2″,”7E3″,”1E3″,”1E4″,”1E5″,”1E6”),(“0E0″,”5E2″,”1E2″,”5E3″,”4E3″,”1E3″,”1E4″,”1E5″,”1E6″,”6E8”),(0-3),(0-4000),(0-3) ,(0,1),(0,1)+CGEQREQ: “IPV6”,(0-4),(0-384),(0-7168),(0-384),(0-7168),(0-2),(0-1520),(“0E0″,”1E1″,”1E2″,”7E3″,”1E3″,”1E4″,”1E5″,”1E6”),(“0E0″,”5E2″,”1E2″,”5E3″,”4E3″,”1E3″,”1E4″,”1E5″,”1E6″,”6E8″),(0-3),(0-4000),(0-3) ,(0,1),(0,1)+CGEQREQ:”IPV4V6”,(0-4),(0-5760),(0-14000),(0-5760),(0-14000),(0-2),(0-1520),(“0E0″,”1E1″,”1E2″,”7E3″,”1E3″,”1E4″,”1E5″,”1E6”),(“0E0″,”5E2″,”1E2″,”5E3″,”4E3″,”1E3″,”1E4″,”1E5″,”1E6″,”6 E8”),(0-3),(0-4000),(0-3),(0,1),(0,1) OK AT+CGEQREQ? +CGEQREQ: OK |
L0809 AT+CGQMIN Quality of Service Profile (Minimum Acceptable)
This command allows the TE to specify a minimum acceptable profile
which is checked by the MT against the negotiated profile returned in the Activate PDP Context Accept message.
A special form of the set command. AT+CGQMIN=<cid> causes
the minimum acceptable profile for context number <cid> to become undefined.
T) AT+CGQMIN=? |
+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) [<CR> <LF>+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) […]] OK or ERROR |
R) AT+CGQMIN? |
+CGQMIN: [<cid>,<precedence>,<delay>,<reliability>,<peak>,<mean>[<CR><LF>+CGQMIN: <cid>,<precedence>,<delay>,<reliability.>,<peak>,<mean>[…]]] OK or ERROR |
W) AT+CGQMIN=<cid>[,<precedence>[,<delay>[,<reliability>[,<peak> [,<mean>]]]]] |
OK or ERROR |
E) AT+CGQMIN |
OK or ERROR |
<cid> |
A numeric parameter which specifies a particular PDP context definition (seeAT+CGDCONT command). The range is from 1 to 24,100 to 179. |
<PDP_type> |
(Packet Data Protocol type) a string parameter which specifies the type of packet data protocol. IP Internet Protocol PPP Point to Point Protocol IPV6 Internet Protocol Version 6 IPV4V6 Dual PDN Stack |
<precedence> |
A numeric parameter which specifies the precedence class: 0 network subscribed value 1 high priority 2 normal priority 3 low priority |
<delay> |
A numeric parameter which specifies the delay class: 0 network subscribed value 1 delay class 1 2 delay class 2 3 delay class 3 4 delay class 4 |
<reliability> |
A numeric parameter which specifies the reliability class: 0 network subscribed value 1 Non real-time traffic, error-sensitive application that cannot cope with data loss 2 Non real-time traffic, error-sensitive application that can cope with infrequent data loss 3 Non real-time traffic, error-sensitive application that can cope with data loss, GMM/-SM, and SMS 4 Real-time traffic, error-sensitive application that can cope with data loss 5 Real-time traffic error non-sensitive application that can cope with data loss |
<peak> |
A numeric parameter which specifies the peak throughput class: 0 network subscribed value 1 Up to 1000 (8 kbit/s) 2 Up to 2000 (16 kbit/s) 3 Up to 4000 (32 kbit/s) 4 Up to 8000 (64 kbit/s) 5 Up to 16000 (128 kbit/s) 6 Up to 32000 (256 kbit/s) 7 Up to 64000 (512 kbit/s) 8 Up to 128000 (1024 kbit/s) 9 Up to 256000 (2048 kbit/s) |
<mean> |
A numeric parameter which specifies the mean throughput class: 0 network subscribed value 1 100 (~0.22 bit/s) 2 200 (~0.44 bit/s) 3 500 (~1.11 bit/s) 4 1000 (~2.2 bit/s) 5 2000 (~4.4 bit/s) 6 5000 (~11.1 bit/s) 7 10000 (~22 bit/s) 8 20000 (~44 bit/s) 9 50000 (~111 bit/s) 10 100000 (~0.22 kbit/s) 11 200000 (~0.44 kbit/s) 12 500000 (~1.11 kbit/s) 13 1000000 (~2.2 kbit/s) 14 2000000 (~4.4 kbit/s) 15 5000000 (~11.1 kbit/s) 16 10000000 (~22 kbit/s) 17 20000000 (~44 kbit/s) 18 50000000 (~111 kbit/s) 31 optimization |
Example |
AT+CGQMIN=? +CGQMIN: “IP”,(0-3),(0-4),(0-5),(0-9),(0-18,31) +CGQMIN: “PPP”,(0-3),(0-4),(0-5),(0-9),(0-18,31) +CGQMIN: “IPV6”,(0-3),(0-4),(0-5),(0-9),(0-18,31) +CGQMIN:”IPV4V6″,(0-3),(0-4),(0-5),(0-9),(0-18,31) OK AT+CGQMIN?+CGQMIN: OK |
L0810 AT+CGEQMIN 3G Quarlity of Service Profile (Minimum Acceptable)
The test command returns values supported as a compound value.
The read command returns the current settings for each defined context for which a QOS was explicitly specified.
T) AT+CGEQMIN=? |
+CGEQMIN: <PDP_type>,(list of supported <Traffic class>s),(list of supported <Maximum bitrate UL>s),(list of supported <Maxim um 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 errorRatio>s),(list of supported <Delivery of erroneous SDUs>s),(list ofSupported <Transfer delay>s), (list of supported <Traffic handling priority>s) OK or ERROR |
R) AT+CGEQMIN? |
+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>][<CR><LF> +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> […]] OK or ERROR |
W) 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>]]]]]]]]]]]] |
OK or ERROR or +CME ERROR: <err> |
E) AT+ CGEQMIN |
OK or ERROR |
<cid> |
Parameter specifies a particular PDP context definition.The parameter is also used in other PDP context-related commands.The range is from 1 to24,100 to 179. |
<Traffic class> |
0 conversational 1 streaming 2 interactive 3 background 4 subscribed value |
<Maximum bitrate UL> |
This parameter indicates the maximum number of kbits/s delivered to UMTS(up-link traffic)at a SAP.As an example a bitrate of 32kbit/s would be specified as 32(e.g. AT+CGEQMIN=…,32,…).The range is from 0 to 8460.The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Maximum bitrate DL> |
This parameter indicates the maximum number of kbits/s delivered to UMTS(down-link traffic)at a SAP.As an example a bitrate of 32kbit/s would be specified as 32(e.g. AT+CGEQMIN=…,32,…).The range is from 0 to 8460. The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Guaranteed bitrate UL> |
This parameter indicates the guaranteed number of kbit/s delivered to UMTS(up-link traffic)at a SAP(provided that there is data to deliver).As an example a bitrate of 32kbit/s would be specified as 32(e.g.AT+CGEQMIN=…,32,…).The range is from 0 to 8460. The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Guaranteed bitrate DL> |
This parameter indicates the guaranteed number of kbit/s delivered to UMTS(down-link traffic)at a SAP(provided that there is data to deliver).As an example a bitrate of 32kbit/s would be specified as 32(e.g.AT+CGEQMIN=…,32,…).The range is from 0 to 8460. The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Delivery order> |
This parameter indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not. 0 no 1 yes 2 subscribed value |
<Maximum SDU size> |
This parameter indicates the maximum allowed SDU size inoctets.The range is from 0 to 1520. The default value is 0. If the parameter is set to ‘0’ the subscribed value will be requested. |
<SDU error ratio> |
This parameter indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. As an example a target SDU error ratio of 5*10-3 would be specified as “5E3”(e.g.AT+CGEQMIN=..,”5E3”,…). “0E0” subscribed value “1E2” “7E3” “1E3” “1E4” “1E5” “1E6” “1E1” |
<Residual bit error ratio> |
This parameter indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested,Residual bit error ratio indicates the bit error ratio in the delivered SDUs. 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” |
<Delivery of erroneous SDUs> |
This parameter indicates whether SDUs detected as erroneous shall be delivered or not. 0 no 1 yes 2 no detect 3 subscribed value |
<Transfer delay> |
This parameter indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP,in milliseconds.The range is from 0 to 4000. The default value is 0. If the parameter is set to’0′ the subscribed value will be requested. |
<Traffic handling priority> |
This parameter specifies the relative importance for handling of all SDUs belonging to the UMTSBearer compared to the SDUs of the other bearers.The range is from 0 to 3. The default value is 0. If the parameter is set to ‘0’ the subscribed value will be requested. |
<PDP_type> |
(Packet Data Protocol type) a string parameter which specifies the type of packet data protocol. IP Internet Protocol PPP Point to Point Protocol IPV6 Internet Protocol Version 6 IPV4V6 Dual PDN Stack |
Example |
AT+CGEQMIN=? +CGEQMIN:”IP”,(0-4),(0-11520),(0-42200),(0-11520),(0-42200),(0-2),(0-1520), (“0E0″,”1E1″,”1E2″,”7E3″,”1E3″,” 1E4″,”1E5″,”1E6″),(“0E0″,”5E2″,”1E2″,”5E3″,”4E3″,”1E3″,”1E4″,”1E5″,”1E6″,”6E8”),(0-3),(0,100- 4000),(0-3),(0-1),(0-1)+CGEQMIN:”PPP”,(0-4),(0-11520),(0-42200),(0-11520),(0-42200),(0-2),(0-1520), (“0E0″,”1E1″,”1E2″,”7E3″,”1E3″,”1E4″,”1E5″,”1E6”), (“0E0″,”5E2″,”1E2″,”5E3″,”4E3″,”1E3″,”1E4″,”1E5″,”1E6″,”6E8”),(0-3),(0,1 00-4000),(0-3),(0-1),(0- 1)+CGEQMIN:”IPV6″,(0-4),(0-11520),(0-42200),(0-11520),(0-42200),(0-2),(0-1520), (“0E0″,”1E1″,”1E2″,”7E3″,”1E3″,”1E4″,”1E5″,”1E6”), (“0E0″,”5E2″,”1E2″,”5E3″,”4E3″,”1E3″,”1E4″,”1E5″,”1E6″,”6E8”),(0-3),(0,1 00-4000),(0-3),(0-1),(0- 1)+CGEQMIN:”IPV4V6″,(0-4),(0-11520),(0-42200),(0-11520),(0-42200),(0-2),(0-1520), (“0E0″,”1E1″,”1E2″,”7E3″,”1E3″,”1E4″,”1E5″,”1E6”), (“0E0″,”5E2″,”1E2″,”5E3″,”4E3″,”1E3″,”1E4″,”1E5″,”1E6″,”6E8”),(0-3),(0,100-4000),(0-3),(0-1),(0-1) OK AT+CGEQMIN? +CGEQMIN: OK |
L0811 AT+CGDATA Enter Data State
The command causes the MT to perform whatever actions are necessary
to establish communication between the TE and the network using one or more Packet Domain PDP types.
This may include performing a PS attach and one or more PDP context activations.
T) AT+ CGDATA=? |
+ CGDATA: (list of supported <L2P>s) OK or ERROR |
W) AT+CGDATA=[<L2P>,[<cid>]] |
NO CARRIER or OK or ERROR or +CME ERROR: <err> |
<L2P> |
A string parameter that indicates the layer 2 protocol to be used between the TE and MT. PPP Point-to-point protocol for a PDP such as IP |
<text> | CONNECT result code string; the string formats please refer ATX/AT\V/AT&E command. |
<cid> | A numeric parameter which specifies a particular PDP context definition (see AT+CGDCONT command).1…16 |
Example |
AT+CGDATA=? +CGDATA: (“PPP”) OK AT+CGDATA=”PPP”,1 CONNECT 115200 |
L0812 AT+CGPADDR Show PDP Address
The write command returns a list of PDP addresses for the specified context identifiers.
T) AT+CGPADDR=? |
[+CGPADDR: (list of defined <cid>s)] OK or ERROR |
W) AT+CGPADDR=<cid>[,<cid>[,…]] |
OK or ERROR or +CME ERROR: <err> |
E) AT+CGPADDR | [+CGPADDR: <cid>,<PDP_addr>] |
<cid> |
A numeric parameter which specifies a particular PDP context definition (see AT+CGDCONT command). If no <cid> is specified, the addresses for all defined contexts are returned.1… 24,100…179 |
<PDP_addr> |
A string that identifies the MT in the address space applicable to the PDP. The address may be static or dynamic. For a static address, it will be the one set by the AT+CGDCONT command when the context was defined. For a dynamic address it will be the one assigned during the last PDP context activation that used the context definition referred to by <cid>. <PDP_addr>is omitted if none is available. |
Example |
AT+CGPADDR=? +CGPADDR: (1) OK AT+CGPADDR=1 +CGPADDR: 1,”0.0.0.0″ OK |
L0813 AT+CGCLASS GPRS Network Registration Status
This command is used to set the MT to operate according to the specified GPRS mobile class.
T) AT+CGCLASS=? |
+CGCLASS:(list of supported <class>s) OK or ERROR |
R) AT+CGCLASS? |
+CGCLASS: <class> OK or ERROR |
W) AT+CGCLASS=<class> |
OK or ERROR or +CME ERROR: <err> |
E) Set default value: AT+CGCLASS |
OK or ERROR |
<class> |
A string parameter which indicates the GPRS mobile class (in descending order of functionality) A class A (highest) |
Example |
AT+CGCLASS=? +CGCLASS: (“A”) OK AT+CGCLASS? +CGCLASS: “A” OK |
L0814 AT+CGEREP GPRS Event Reporting
The write command enables or disables sending of unsolicited result codes,
“+CGEV” from MT to TE in the case of certain events occurring in the Packet Domain MT or the network.
<mode> controls the processing of unsolicited result codes specified within this command.
<bfr> controls the effect on buffered codes when <mode> 1 or 2 is entered.
If a setting is not supported by the MT, ERROR or +CME ERROR: is returned.
Read command returns the current <mode> and buffer settings.
Test command returns the modes and buffer settings supported by the MT as compound values.
T) AT+CGEREP=? |
+CGEREP: (list of supported <mode>s), (list of supported <bfr>s) OK or ERROR |
R) AT+CGEREP? |
+CGEREP: <mode>,<bfr> OK or ERROR |
W) AT+CGEREP=<mode>[,<bfr>] |
OK or ERROR or +CME ERROR: <err> |
E) AT+CGEREP |
OK or ERROR |
<mode> |
0 buffer unsolicited result codes in the MT; if MT result code buffer is full, the oldest ones can be discarded. No codes are forwarded to the TE. |
<bfr> |
0 MT buffer of unsolicited result codes defined within this command is cleared when <mode> 1 or 2 is entered. |
The following unsolicited result codes and the corresponding events are defined:
+CGEV: REJECT <PDP_type>,<PDP_addr>
A network request for PDP context activation occurred when the MT was unable to report it to the TE with a +CRING unsolicited result code and was automatically rejected.
+CGEV: NW REACT <PDP_type>,<PDP_addr>,[<cid>]
The network has requested a context reactivation. The <cid> that was used to reactivate the context is provided if known to the MT.
+CGEV: NW DEACT <PDP_type>,<PDP_addr>,[<cid>]
The network has forced a context deactivation. The <cid> that was used to activate the context is provided if known to the MT.
+CGEV: ME DEACT <PDP_type>,<PDP_addr>,[<cid>]
The mobile equipment has forced a context deactivation. The <cid> that was used to activate the context is provided if known to the MT.
+CGEV: NW DETACH
The network has forced a Packet Domain detach. This implies that all active contexts have been deactivated. These are not reported separately.
+CGEV: ME DETACH
The mobile equipment has forced a Packet Domain detach. This implies that all active contexts have been deactivated. These are not reported separately.
+CGEV: NW CLASS <class>
The network has forced a change of MS class. The highest available class is reported (see AT+CGCLASS).
+CGEV: ME CLASS <class>
The mobile equipment has forced a change of MS class. The highest available class is reported (see AT+CGCLASS).
NOTE
The <lac> not supported in CDMA/HDR mode
The <ci> not supported in CDMA/HDR mode
Example |
AT+CGEREP=? +CGEREP: (0-2),(0-1) OK AT+CGEREP? +CGEREP: 0,0 OK |
L0815 AT+CGAUTH Set Type Of Authentication For PDP-IP Connections Of GPRS
This command is used to set type of authentication for PDP-IP connections of GPRS.
T) AT+CGAUTH=? |
+CGAUTH: ,,127,127(for CDMA1x-EvDo only) +CGAUTH: (range of supported<cid>s),(list of supported <auth_ type>s),, OK or ERROR or +CME ERROR: <err> |
R) AT+CGAUTH? |
+CGAUTH: <cid>,<auth_type>[,<user>]<CR><LF> +CGAUTH: <cid>,<auth_type>[,<user>]<CR><LF> … OK
OK or ERROR or +CME ERROR: <err> |
W) AT+CGAUTH=<cid>[,<auth_type>[,<passwd>[,<user>]]] |
OK or ERROR or +CME ERROR: <err> |
E) AT+CGAUTH |
OK or ERROR or +CME ERROR: <err> |
<cid> |
Parameter specifies a particular PDP context definition. This is also used in other PDP context-related commands. 1…42,100…179 |
<auth_type> |
Indicate the type of authentication to be used for the specified context. If CHAP is selected another parameter <passwd> needs to be specified. If PAP is selected two additional parameters <passwd> and <user> need to specified. 0 none 1 PAP 2 CHAP 3 PAP or CHAP |
<passwd> | Parameter specifies the password used for authentication. |
<user> | Parameter specifies the user name used for authentication. |
Example
Example |
AT+CGAUTH=? +CGAUTH: ,,127,127(for CDMA1x-EvDo only) +CGAUTH: (1-24,100-179),(0-3),127,127 OK AT+CGAUTH=1,1,”123″,”SIMCOM” OK |