u-blox

Packet switched data services

PDP contexts and parameter definition

Primary and secondary PDP contexts

A PDP context can be either primary or secondary. In LTE, PS data connections are referred to as EPS bearers: EPS bearers are conceptually equivalent to the legacy PDP contexts, which are often referred to for sake of simplicity. Similarly to a PDP context, the EPS bearer can be a default (primary) or dedicated (secondary) one. The initial EPS bearer established during LTE attach procedure is actually a default EPS bearer. A secondary PDP context uses the same IP address of a primary PDP context (the usual PDP context activated e.g. via dial-up). The Traffic Flow Filters for such secondary contexts shall be specified according to 3GPP TS 23.060 [46].
The typical usage of the secondary PDP contexts is in VoIP calls, where RTP (speech) packets are conveyed on one PDP context (e.g. the primary one) with a given QoS (e.g. low reliability) whereas SIP signalling is routed on a different PDP context (e.g. the secondary one, with the same IP address but different port numbers) with a more reliable QoS.
A Traffic Flow Template (i.e. a filter based on port number, specifying relative flow precedence) shall be configured for the secondary context to instruct the GGSN to route down-link packets onto different QoS flows towards the TE.
PDP context typeActivation procedure
Primary
Used to establish a logical connection through the network from the UE to the GGSN with a specifically negotiated Quality of Service (QoS).
The UE initiates the PDP context activation: it changes the session management state to active, creates the PDP context, obtains the IP address and reserves radio resources. After the activation, the UE is able to send IP packets over the air interface.
Secondary
Used to establish a second PDP context with the same IP address and the same APN as the primary PDP context.
The two contexts may have different QoS profiles, which makes the feature useful for applications that have different QoS requirements (e.g. IP multimedia); QoS is applied based on port number addressing.
At most 1 PDP context can be used with dial-up.

Multiple PDP contexts

The section does not apply to this module series.
Two PDP context types are defined:
  • "external" PDP context: IP packets are built by the DTE, the MT’s IP instance runs the IP relay function only;
  • "internal" PDP context: the PDP context (relying on the MT’s embedded TCP/IP stack) is configured, established and handled via the data connection management AT commands.
Multiple PDP contexts are supported. The DTE can access these PDP contexts either alternatively through the physical serial interface, or simultaneously through the virtual serial ports of the multiplexer (multiplexing mode MUX), with the following constraints:
  • Using the MT’s embedded TCP/IP stack, only an internal PDP context is supported. This IP instance supports up to 7 sockets;
  • The sum of active external and internal PDP contexts cannot exceed the maximum number of active PDP contexts indicated in the <cid> parameter description;
  • Using external PDP contexts via dial-up, it is usually possible to have at most 3 PPP instances simultaneously active.

Parameter definition

<APN>

The Access Point Name (APN) is a string parameter, which is a logical name, valid in the current PLMN’s domain, used to select the Gateway GPRS Support Node (GGSN) or the external packet data network to be connected to.
The APN can be omitted: this is the so-called "blank APN" setting, which may be required by some mobile network operators; in this case the APN string is not included in the message sent to the network, which will provide the module with the assigned APN in the message response. When "blank APN" is used by the module, some mobile network operators do not provide a valid APN and assign an "anchor" or "default" APN, which does not allow bi-directional traffic with the packet data network: in these cases the network specific APN shall be known in advance and defined before establishing the PDP context/PDN connection.
The maximum length of the parameter is:
  • 99 characters (the maximum length of coded APN is 100 octets, see 3GPP TS 23.003 [47], subclause 9.1)

<cid>

PDP context identifier. A numeric parameter specifying a particular PDP context definition. This parameter is valid only locally on the interface DTE-MT.
The maximum number of definable and active PDP contexts depend(s) on the product version:[1]
ProductMax number of definable PDP contextsMax number of active PDP contexts
LEXI-R10 / SARA-R10
11
3
The <cid> range goes from 1 to 11.

<PDP_addr>

String parameter identifying the MT in the IP-address space applicable to the PDP service. If the value is null or omitted (dynamic IP addressing), then a value may be provided by the DTE during the PDP startup procedure or, failing that, a dynamic address will be requested via DHCP. It can be read with the command AT+CGPADDR or AT+CGDCONT read command.
To request a static IP address, a fixed IP address shall be specified for the <PDP_addr> parameter of the +CGDCONT set command and the user shall not rely on PPP negotiation via IPCP CONFREQ option.
Depending on the IP-version, the <PDP_addr> consists of 4 octets (IPv4) or 16 octets (IPv6):
  • IPv4: "ddd.ddd.ddd.ddd"
  • IPv4v6: "ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd"
  • IPv6: "ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd.ddd"
In AT+CGDCONT set command, the parameter is ignored.

<PDP_type>

The Packet Data Protocol (PDP) type is a string parameter which specifies the type of packet data protocol:
  • "IP": Internet Protocol (IETF STD 5)
  • "Non-IP": Non IP
  • "IPV4V6": virtual <PDP_type> introduced to handle dual IP stack UE capability (see the 3GPP TS 24.301 [22])
  • "IPV6": Internet Protocol, version 6 (see RFC 2460 [48])
<PDP_type>="Non-IP" is not supported.

PPP LCP handshake behavior

When a data call is initiated by means of D* AT command, the module switches to PPP mode just after the CONNECT intermediate result code. The first step of the PPP procedure is the LCP handshake, in this phase the behavior of module series differ between them.
Entering OnLine Command Mode (OLCM) during LCP handshake phase is strongly discouraged because the handshake procedure could be broken and should be restarted from the beginning.

PDP context definition +CGDCONT

+CGDCONT
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
partial
Yes
NVM / OP
No
-
+CME Error

Description

Defines the connection parameters for a PDP context, identified by the local context identification parameter <cid>. If the command is used only with parameter <cid>, the corresponding PDP context becomes undefined.
Each context is permanently stored so that its definition is persistent over power cycles.
The command is used to set up the PDP context parameters for an external context, i.e. a data connection using the external IP stack (e.g. Windows dial-up) and PPP link over the serial interface.
Usage of static i.e. user defined IP address is possible in UTRAN and GERAN but not in EUTRAN; to prevent inconsistent addressing methods across various RATs, static IP addressing is not recommended for LTE modules: 3GPP TS 23.060 [46] Rel.8 and later releases specify that a UE with EUTRAN/UTRAN/GERAN capabilities shall not include a static PDP address in PDP context activation requests.
The information text response to the read command provides the configuration of all the PDP context / EPS bearers that have already been defined. The test command returns a different row for each <PDP_type> value supported by the module.
For initial default EPS bearer, when defining context authentication parameters username/password with +CGAUTH AT command, the <secure_PCO> flag must be set.

Syntax

TypeSyntaxResponseExample
Set
AT+CGDCONT=[<cid>[,<PDP_type>[,<APN>[,<PDP_addr>[,<d_comp>[,<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>[,<secure_PCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>[,<Non_IP_MTU_discovery>]]]]]]]]]]]]]]]
OK
IPv4 example
AT+CGDCONT=1,"IP","APN_name","1.2.3.4",0,0
OK
IPv4v6 example
AT+CGDCONT=1,"IPV4V6","APN","0.0.0.0 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0
OK
IPv6 example
AT+CGDCONT=1,"IPV6","APN","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0
OK
Read
AT+CGDCONT?
+CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_comp>[,<IPv4AddrAlloc>,<request_type>,<P-CSCF_discovery>,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>[,<secure_PCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>[,<Non_IP_MTU_discovery>]]]]]]
[+CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_comp>[,<IPv4AddrAlloc>,<request_type>,<P-CSCF_discovery>,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>[,<secure_PCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>[,<Non_IP_MTU_discovery>]]]]]]]
OK
+CGDCONT: 1,"IP","web.omnitel.it","91.80.140.199",0,0,0,2,0,0,0,0,0,0
OK
Test
AT+CGDCONT=?
+CGDCONT: (list of supported <cid>s),<PDP_type>,,,(list of supported <d_comp>s),(list of supported <h_comp>s),(list of supported <IPv4AllocAddr>s),(list of supported <request_type>s),(list of supported <P-CSCF_discovery>s),(list of supported <IM_CN_Signalling_Flag_Ind>s),(list of supported <NSLPI>s),(list of supported <secure_PCO>s),(list of supported <IPv4_MTU_discovery>s),(list of supported <Local_Addr_Ind>s),(list of supported <Non_IP_MTU_discovery>s)
[+CGDCONT: (list of supported <cid>s),<PDP_type>,,,(list of supported <d_comp>s),(list of supported <h_comp>s),(list of supported <IPv4AllocAddr>s),(list of supported <request_type>s),(list of supported <P-CSCF_discovery>s),(list of supported <IM_CN_Signalling_Flag_Ind>s),(list of supported <NSLPI>s),(list of supported <secure_PCO>s),(list of supported <IPv4_MTU_discovery>s),(list of supported <Local_Addr_Ind>s),(list of supported <Non_IP_MTU_discovery>s)]
OK
+CGDCONT: (0-11),"IP",,,(0-2),(0-4),(0,1),(0,3),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1)
+CGDCONT: (0-11),"IPV6",,,(0-2),(0-4),(0,1),(0,3),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1)
+CGDCONT: (0-11),"IPV4V6",,,(0-2),(0-4),(0,1),(0,3),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1)
+CGDCONT: (0-11),"Non-IP",,,(0-2),(0-4),(0,1),(0,3),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1)
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>. The default value is 1.
<PDP_type>
String
See <PDP_type>. The default value is "IP".
<APN>
String
See <APN>. The default value is "" (blank APN).
<PDP_addr>
Number
See <PDP_addr>. The default value is "0.0.0.0"
<d_comp>
Number
PDP data compression:
  • 0 (default value): off
  • 1: on (predefined compression type i.e. V.42bis data compression)
  • 2: V.42bis data compression
  • 3: V.44
<h_comp>
Number
PDP header compression:
  • 0 (default value): off
  • 1: on (predefined compression type, i.e. RFC1144)
  • 2: RFC1144
  • 3: RFC2507
  • 4: RFC3095
The available head-compressions dependends on configuration of the stack (configured via features in the stack)
Internal warning: on Intel based products the parameter is effective on 2G.
<IPv4AddrAlloc>
Number
Controls how the MT/TA requests to get the IPv4 address information:
  • 0 (default value): IPv4 Address Allocation through NAS Signalling
  • 1: IPv4 Address Allocated through DHCP
<emergency_indication>
Number
Indicates whether the PDP context is for emergency bearer services or not:
  • 0 (default value): PDP context is not for emergency bearer services
  • 1: PDP context is for emergency bearer services
<request_type>
Number
Indicates the type of PDP context activation request for the PDP context:
  • 0: PDP context is for new PDP context establishment or for handover from a non-3GPP access network (how the MT decides whether the PDP context is for new PDP context establishment or for handover is implementation specific)
  • 1: PDP context is for emergency bearer services
  • 2 (default value): PDP context is for new PDP context establishment
  • 3: PDP context is for handover from a non-3GPP access network
<P-CSCF_discovery>
Number
Influences how the MT/TA requests to get the P-CSCF address, see 3GPP TS 24.229 [49] annex B and annex L:
  • 0 (default value): preference of P-CSCF address discovery not influenced by +CGDCONT
  • 1: preference of P-CSCF address discovery through NAS Signalling
  • 2: preference of P-CSCF address discovery through DHCP
<IM_CN_Signalling_Flag_Ind>
Number
Shows whether the PDP context is for IM CN subsystem-related signalling only or not:
  • 0: PDP context is not for IM CN subsystem-related signalling only
  • 1: PDP context is for IM CN subsystem-related signalling only
<NSLPI>
Number
Indicates the NAS signalling priority requested for the corresponding PDP context:
  • 0 (default value): indicates that the PDP context has to be activated with the value for the low priority indicator configured in the MT.
  • 1: indicates that the PDP context has to be activated with the value for the low priority indicator set to "MS is not configured for NAS signalling low priority".
The MT utilises the NSLPI information provided as specified in 3GPP TS 24.301 [22] and 3GPP TS 24.008 [12].
<secure_PCO>
Number
Specifies if security protected transmission of PCO is requested or not (applicable for EPS only):
  • 0 (default value): Security protected transmission of PCO is not requested.
  • 1: Security protected transmission of PCO is requested.
<IPv4_MTU_discovery>
Number
Influences how the MT/TA requests to get the IPv4 MTU size:
  • 0 (default value): Preference of IPv4 MTU size discovery not influenced by +CGDCONT.
  • 1: Preference of IPv4 MTU size discovery through NAS signalling.
<Local_Addr_Ind>
Number
Indicates to the network whether or not the MS supports local IP address in TFTs:
  • 0 (default value): indicates that the MS does not support local IP address in TFTs.
  • 1: indicates that the MS supports local IP address in TFTs.
<Non_IP_MTU_discovery>
Number
Influences how the MT/TA requests to get the Non-IP MTU size (for more details, see 3GPP TS 24.008 [12]):
  • 0 (default value): preference of Non-IP MTU size discovery not influenced by +CGDCONT.
  • 1: preference of Non-IP MTU size discovery through NAS signalling.

Notes

Additional examples:
CommandResponseDescription
Configure the error result code format by means of the +CMEE AT command
AT+CGDCONT=?
+CGDCONT: (1-3),"IP",,,(0),(0-1)
OK
Test command
AT+CGDCONT=4,"IP","internet"
+CME ERROR: operation not allowed
Define out of range PDP contexts
AT+CGDCONT=2,"IP","internet"
OK
Define allowed PDP contexts
AT+CGDCONT=1,"IP","STATREAL"
OK
Define allowed PDP contexts
AT+CGDCONT=3,"IP","tim.ibox.it"
OK
Define allowed PDP contexts
AT+CGDCONT=253,"IP","internet"
+CME ERROR: operation not allowed
Define out of range PDP contexts
AT+CGDCONT?
+CGDCONT: 2,"IP","internet","0.0.0.0",0,0
+CGDCONT: 1,"IP","STATREAL","0.0.0.0",0,0
+CGDCONT: 3,"IP","tim.ibox.it","0.0.0.0",0,0
OK
Read command
  • The PIN insertion is not mandatory before the command execution.
  • <request_type> allowed values are 0, 1 and 2.
  • The <IM_CN_Signalling_Flag_Ind> allowed value is 0.
  • The <PDP_addr>, <d_comp>, <h_comp>, <Local_Addr_Ind> and <Non_IP_MTU_discovery> parameters in AT+CGDCONT set command are ignored.
  • The <IPv4AddrAlloc> parameter in AT+CGDCONT set command is ignored when <PDP_type> is "IPV6".
  • Undefining an active PDP context is not allowed. If a PDP context is defined with the same settings several times, the same number of AT+CGDCONT=<cid> AT commands shall be issued to undefine it.
  • In +UMNOPROF: 2 (AT&T), +UMNOPROF: 3 (Verizon) and +UMNOPROF: 206 (AT&T FirstNet) MNO profiles, the default <cid> settings can be changed only when the SIM initialization has been completed (i.e. if +CPIN read command returns "READY").
  • In +UMNOPROF: 2 (AT&T), +UMNOPROF: 3 (Verizon) and +UMNOPROF: 206 (AT&T FirstNet) MNO profiles, when changing the default <cid> settings, only the <PDP_type> and <APN> parameters are persistent across power cycles.

Default CID and preferred protocol type configuration +UDCONF=19

+UDCONF=19
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
Yes
NVM
No
-
+CME Error

Description

Specifies the default internal PDP context ID and the preferred IP type. If not explicitly specified otherwise, these parameters are used by internal applications that require IP connectivity, e.g., MQTT and HTTP.
Reboot the module (e.g. by means of the AT+CFUN=15/AT+CFUN=16 command) to make the change effective.
The read command reports the current effective setting.

Syntax

TypeSyntaxResponseExample
Set
AT+UDCONF=19,<cid>,<preferred_protocol_type>
OK
AT+UDCONF=19,1,0
OK
Read
AT+UDCONF=19
+UDCONF: 19,<cid>,<preferred_protocol_type>
OK
AT+UDCONF=19
+UDCONF: 19,2,1
OK

Defined values

ParameterTypeDescription
<cid>
Number
Internal PDP context identifier used by default by AT commands. For the parameter allowed range, see <cid>. The factory-programmed value is 1.
<preferred_protocol_type>
Number
Preferred protocol type to be specified when the <cid> protocol type is IPv4v6. Allowed values:
  • 0 (factory-programmed value): IPv4
  • 1: IPv6

PS attach or detach +CGATT

+CGATT
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
Yes
No
Yes
Section B.2
+CME Error

Description

Register (attach) the MT to, or deregister (detach) the MT from the packet switched (PS) services. After this command the MT remains in AT command mode. If the MT is already in the requested state (attached or detached), the command is ignored and OK result code is returned. If the requested state cannot be reached, an error result code is returned. The command can be aborted if a character is sent to the DCE during the command execution. Any active PDP context will be automatically deactivated when the PS registration state changes to detached.
The user should not enter colliding requests (e.g. AT+CGATT=1 and AT+CGATT=0) on different communication ports, because this might cause interoperability issues if overlapping attach and detach requests are not handled by the network, and could result in an unpredictable registration state. Similarly, when notified of a mobile terminated detach event (e.g. via +CGEV URC), it is recommended to wait a few seconds before entering AT+CGATT=0 in order to let the pending attach procedure (automatically triggered by the module in most cases) successfully end.
The deregistration action is carried out even if the command is aborted.

Syntax

TypeSyntaxResponseExample
Set
AT+CGATT=[<state>]
OK
AT+CGATT=1
OK
Read
AT+CGATT?
+CGATT: <state>
OK
+CGATT: 1
OK
Test
AT+CGATT=?
+CGATT: (list of supported <state>s)
OK
+CGATT: (0-1)
OK

Defined values

ParameterTypeDescription
<state>
Number
Indicates the state of GPRS attachment:
  • 0: detached
  • 1 (default value): attached

PDP context activate or deactivate +CGACT

+CGACT
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
Yes
No
Yes
Section B.2
+CME Error

Description

Activates or deactivates the specified PDP context. After the command, the MT remains in AT command mode. If any context is already in the requested state, the state for the context remains unchanged. If the required action cannot succeed, an error result code is returned. If the MT is not GPRS attached when the activation of a PDP context is required, the MT first performs a GPRS attach and then attempts to activate the specified context.
The maximum expected response time is different whenever the activation or the deactivation of a PDP context is performed: for more details, see Estimated command response time.

Syntax

TypeSyntaxResponseExample
Set
AT+CGACT=[<status>[,<cid>[,…​]]]
OK
AT+CGACT=1,1
OK
Read
AT+CGACT?
[+CGACT: <cid>,<status>
[+CGACT: <cid>,<status>
[…​]]]
OK
+CGACT: 1,1
OK
Test
AT+CGACT=?
+CGACT: (list of supported <status>s)
OK
+CGACT: (0-1)
OK

Defined values

ParameterTypeDescription
<status>
Number
Indicates the state of PDP context activation:
  • 0: deactivated
  • 1: activated
<cid>
Number
See <cid>.

Notes

  • If AT+CGACT=1,<cid> is issued multiple times on the same active <cid>, before being able to deactivate it the same number of AT+CGACT=0,<cid> AT commands shall be issued and the error result code "+CME ERROR: CID active counter value greater than ZERO" will be returned.

Enter PPP state/GPRS dial-up D*

D*
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
Yes
No
No
Section B.2
+CME Error

Description

The V.24 dial command "D", similar to the command with the syntax AT+CGDATA="PPP",<cid>, causes the MT to perform the necessary actions to establish the communication between the DTE and the external PDP network through the PPP protocol. This can include performing a PS attach and, if the PPP server on the DTE side starts communication, PDP context activation on the specified PDP context identifier (if not already requested by means of +CGATT and +CGACT commands).
If the command is accepted and the preliminary PS procedures have succeeded, the "CONNECT" intermediate result code is returned, the MT enters the V.25ter online data state and the PPP L2 protocol between the MT and the DTE is started.
The data session is terminated by one of the following events:
  • Sending the escape sequence "+++" or "~+++" (see &D where supported).
  • Via a DTR transition from ON to OFF (see &D where supported).
  • Sending an LCP Terminate Request.

Syntax

TypeSyntaxResponseExample
Set
ATD[<dialing_type_char>]*<dialing_number>[\*[<address>][*[<L2P>][*[<cid>]]]]#
CONNECT
(data transfer starts)
ATD*99***1#
CONNECT

Defined values

ParameterTypeDescription
<dialing_type_char>
String
Optional (legacy) "T" or "P" character indicating the tone dialing or pulse dialing respectively
<dialing_number>
Number
List all the supported values
<address>
-
Ignored
<L2P>
String
Layer 2 protocol to be used between the DTE and MT; allowed values:
  • "PPP" (default value)
  • "M-HEX"
  • "M-RAW_IP"
  • "M-OPT-PPP"
The application on the remote side must support the selected protocol as well.
<cid>
Number
See <cid>

Notes

  • Dial-up with PAP/CHAP authentication is not supported on an already active PDP context that was activated without authentication.
  • The context identifier <cid> is mapped to 1 if not specified.
  • The GPRS dial-up command maps to AT+CGDATA="PPP",<cid>.
  • If FDN is enabled and FDN check for PS data call is supported by the module, to perform a GPRS dial-up one of the following entries must be stored in the FDN phonebook: *99#, *99*#, *99**# or *99***#.

Show PDP address +CGPADDR

+CGPADDR
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
Yes
No
No
-
+CME Error

Description

Returns a list of PDP addresses for the specified context identifiers. Only defined PDP contexts are displayed.
If the <cid> parameter is omitted, the addresses for all defined contexts are returned.

Syntax

TypeSyntaxResponseExample
Set
AT+CGPADDR=[<cid>[,<cid> [,…​]]]
+CGPADDR: <cid>,<PDP_addr>
[+CGPADDR: <cid>,<PDP_addr>
[…​]]
OK
AT+CGPADDR=1
+CGPADDR: 1,"1.2.3.4"
OK
Test
AT+CGPADDR=?
+CGPADDR: [(list of defined <cid>s)]
OK
+CGPADDR: 1,3
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>
<PDP_addr>
Number

Packet switched event reporting +CGEREP

+CGEREP
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
partial
Yes
Profile
No
-
+CME Error

Description

Configures sending of URCs from MT to the DTE, if certain events occur in the packet switched MT or the network. By the <mode> parameter, it is possible to control the processing of the URCs codes specified within this command. The <bfr> parameter controls the effect on buffered codes when the <mode> parameter is set to 1 (discard URCs when V.24 link is reserved) or 2 (buffer URCs in the MT when link reserved and flush them to the DTE when the link becomes available).

Syntax

TypeSyntaxResponseExample
Set
AT+CGEREP=[<mode>[,<bfr>]]
OK
AT+CGEREP=1,1
OK
Read
AT+CGEREP?
+CGEREP: <mode>,<bfr>
OK
+CGEREP: 0,0
OK
Test
AT+CGEREP=?
+CGEREP: (list of supported <mode>s),(list of supported <bfr>s)
OK
+CGEREP: (0-2),(0-1)
OK
URC
+CGEV: ME PDN ACT <cid>[,<reason>[,<cid_other>]]
+CGEV: NW CLASS "CC"
+CGEV: ME ACT <p_cid>,<cid>,<event_type>
+CGEV: ME PDN DEACT <cid>
+CGEV: PDN DEACT <cid>
+CGEV: ME DEACT <PDP_type>,<PDP_addr>,[<cid>]
+CGEV: ME DEACT,<p_cid>,<cid>,0
+CGEV: ME DEACT <p_cid>,<cid>,<event_type>
+CGEV: ME MODIFY <cid>,<change_reason>,<event_type>
+CGEV: ME DETACH
+CGEV: ME CLASS <class>
+CGEV: NW PDN ACT <cid>[,<reason>]
+CGEV: NW ACT <p_cid>,<cid>,<event_type>
+CGEV: NW PDN DEACT <cid>
+CGEV: NW DEACT <p_cid>,<cid>,0
+CGEV: NW DEACT <p_cid>,<cid>,<event_type>
+CGEV: NW DEACT <PDP_type>,<PDP_addr>,[<cid>]
+CGEV: NW MODIFY <cid>,<change_reason>,<event_type>
+CGEV: NW DETACH
+CGEV: NW CLASS <class>
+CGEV: VZW_SUBS_ACTION_NORMAL (0) - No restriction to data traffic
+CGEV: REJECT <PDP_type>,<PDP_addr>
+CGEV: NW REACT <PDP_type>,<cid>
+CGEV: NW ACT <PDP_type>,<cid>

Defined values

ParameterTypeDescription
<mode>
Number
Controls the processing of URCs specified within this command. Allowed values:
  • 0 (default value): buffer URCs in the MT; if the buffer is full the oldest ones will be discarded
  • 1: discard URCs when V.24 link is reserved (online); otherwise forward them directly to the DTE
  • 2: buffer URCs in the MT when link reserved (online) and flush them to the DTE when the link becomes available; otherwise forward them directly to the DTE
<bfr>
Number
Controls the effect on buffered codes when <mode> 1 or 2 is entered. Allowed values:
  • 0 (default value): MT buffer of URCs defined within this command is cleared when <mode> 1 or 2 is entered
  • 1: MT buffer of URCs defined within this command is flushed to the DTE when <mode> 1 or 2 is entered (OK is given before flushing the codes)
<cid>
Number
See <cid>
<reason>
Number
Indicates whether the reason why the context activation request for PDP type IPv4v6 was not granted:
  • 0: IPv4 only allowed
  • 1: IPv6 only allowed
  • 2: single address bearers only allowed
  • 3: single address bearers only allowed and MT initiated context activation for a second address type bearer was not successful
<cid_other>
Number
Indicates whether the context identifier allocated by MT for an MT initiated context of a second address type
<p_cid>
Number
Numeric parameter that identifies the particular PDP context definition, specified using +CGDCONT, to which a secondary PDP context definition will be associated using +CGDSCONT.
This parameter is only locally valid on the interface TE-MT.
<event_type>
Number
Indicates whether the event is informational or whether the TE has to acknowledge it:
  • 0: informational event
  • 1: information request: acknowledgement required
<change_reason>
Number
Indicates what kind of change occurred:
  • 1: TFT only changed
  • 2: QoS only changed
  • 3: both TFT and QoS changed
<PDP_type>
Number
<PDP_addr>
Number
<class>
String
GPRS mobile class. Allowed values:
  • "A": class A mode of operation (A/Gb mode), or CS/PS mode of operation (Iu mode) (highest mode of operation)
  • "B": class B (circuit-switched and packet-switched data alternatively supported)
  • "CG": class C (one service only) in GPRS mode
  • "CC": class C (one service only) in circuit-switched (GSM) mode

Notes

  • <mode>= 2 is not supported.
  • <bfr>= 1 is not supported.

Explanation of URCs

URCRemarks
+CGEV: ME PDN ACT <cid>[,<reason>[,<cid_other>]]
The MT has activated a primary context.
+CGEV: ME ACT <p_cid>,<cid>,<event_type>
The network has responded to a MT initiated secondary context activation.
+CGEV: ME PDN DEACT <cid>
The MT has forced a primary context deactivation.
+CGEV: PDN DEACT <cid>
A primary context deactivation has been forced either by the MT or by the network.
+CGEV: ME DEACT <PDP_type>,<PDP_addr>,[<cid>]
The MT has forced a context deactivation.
+CGEV: ME DEACT,<p_cid>,<cid>,0
The UE has forced a secondary context deactivation.
+CGEV: ME DEACT <p_cid>,<cid>,<event_type>
The MT has forced a secondary context deactivation.
+CGEV: ME MODIFY <cid>,<change_reason>,<event_type>
The MT has forced a context modification.
+CGEV: ME DETACH
The mobile station has forced a GPRS detach
+CGEV: ME CLASS <class>
The mobile station has forced a change of MT class; the highest available class is reported.
+CGEV: NW PDN ACT <cid>[,<reason>]
The network has activated a primary context.
+CGEV: NW ACT <p_cid>,<cid>,<event_type>
The network has forced a secondary context activation.
+CGEV: NW PDN DEACT <cid>
The network has forced a primary context deactivation.
+CGEV: NW DEACT <p_cid>,<cid>,0
The network has forced a secondary context deactivation.
+CGEV: NW DEACT <p_cid>,<cid>,<event_type>
The network has forced a secondary context deactivation.
+CGEV: NW DEACT <PDP_type>,<PDP_addr>,[<cid>]
The network has forced a context deactivation.
+CGEV: NW MODIFY <cid>,<change_reason>,<event_type>
The network has forced a context modification.
+CGEV: NW DETACH
The network has forced a GPRS detach.
+CGEV: NW CLASS <class>
The network has forced a change of MT class (e.g. due to service detach); the highest available class is reported.
+CGEV: VZW_SUBS_ACTION_NORMAL (0) - No restriction to data traffic
No restriction to data traffic. The URC is provided only on Verizon network.
+CGEV: REJECT <PDP_type>,<PDP_addr>
The context activation is rejected.
+CGEV: NW REACT <PDP_type>,<cid>
The network has forced a context re-activation.
+CGEV: NW ACT <PDP_type>,<cid>
The network has forced a context activation.

Manual deactivation of a PDP context H

H
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
No
No
No
< 20 s
+CME Error

Description

Deactivates an active PDP context with PPP L2 protocol in online command mode. The MT responds with a final result code. For a detailed description, see the H command description. For additional information about OLCM, see the AT command settings .
In GPRS online command mode, entered by typing the escape sequence "+++" or "~+++" (see &D), the ATH command is needed to terminate the connection. Alternatively, in data transfer mode, DTE originated DTR toggling or PPP disconnection may be used.

Syntax

TypeSyntaxResponseExample
Action
ATH
OK

PDP context modify +CGCMOD

+CGCMOD
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
partial
Yes
No
No
Section B.2
+CME Error

Description

This execution command is used to modify the specified PDP context(s) with respect to QoS profiles and TFT’s. After the command is complete, the MT returns to the V.25 online data state. If the requested modification for any specified context cannot be achieved, an error result code is returned. If no <cid>s are specified, the activation form of the command modifies all the active contexts.

Syntax

TypeSyntaxResponseExample
Set
AT+CGCMOD=[<cid>[,<cid>[,,…​]]]
OK
AT+CGCMOD=1
OK
Test
AT+CGCMOD=?
+CGCMOD: (list of <cid>s with active contexts)
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>.

Notes

  • The PIN insertion is not mandatory before the command execution.

Define secondary PDP context +CGDSCONT

+CGDSCONT
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
Yes
No
No
-
+CME Error

Description

Configures the PDP context parameter values for a secondary PDP context, identified by the local context identification parameter <cid>, associated to a primary PDP context identified by the local context identification parameter <p_cid>:
  • The <p_cid> parameter is mandatory when a secondary context is newly defined.
  • The <p_cid> parameter can be omitted only when the context is already defined; in this case the PDP context identified by <cid> becomes undefined.

Syntax

TypeSyntaxResponseExample
Set
AT+CGDSCONT=[<cid>[,<p_cid>[,<d_comp>[,<h_comp>[,<IM_CN_Signalling_Flag_Ind>]]]]]
OK
AT+CGDSCONT=2,1
OK
Read
AT+CGDSCONT?
+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>[,<IM_CN_Signalling_Flag_Ind>]
[+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>[,<IM_CN_Signalling_Flag_Ind>]
[…​]]
OK
+CGDSCONT: 2,1,0,0,0
OK
Test
AT+CGDSCONT=?
+CGDSCONT: (list of supported <cid>s),(list of <cid>s for defined primary contexts),(list of supported <d_comp>s),(list of supported <h_comp>s)[,(list of supported <IM_CN_Signalling_Flag_Ind>)]
OK
+CGDSCONT: (1-8),(4,8),(0-2),(0-2),(0-1)
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>
<p_cid>
Number
Numeric parameter that identifies the particular PDP context definition, specified using +CGDCONT, to which a secondary PDP context definition will be associated using +CGDSCONT.
This parameter is only locally valid on the interface TE-MT.
<d_comp>
Number
PDP data compression; it can have the values:
  • 0 (default value): off
  • 1: on (predefined compression type i.e. V.42bis data compression)
  • 2: V.42bis data compression
<h_comp>
Number
PDP header compression; it can have the values:
  • 0 (default value): off
  • 1: on (predefined compression type, i.e. RFC1144)
  • 2: RFC1144
  • 3: RFC2507
  • 4: RFC3095
<h_comp> the available head-compressions is depending on configuration of the stack (configured via features in the stack)
Internal warning: on Intel based products the parameter is effective on 2G.
<IM_CN_Signalling_Flag_Ind>
Number
Shows whether the PDP context is for IM CN subsystem-related signalling only or not:
  • 0: PDP context is not for IM CN subsystem-related signalling only
  • 1: PDP context is for IM CN subsystem-related signalling only

Notes

  • The PIN insertion is not mandatory before the command execution.
  • The set command is accepted when the <p_cid> is defined and activated via the +CGDCONT and +CGACT AT commands respectively.
  • The read command returns a response when the parameters are configured successfully via the set command, otherwise an error result code is returned.

UE modes of operation for EPS +CEMODE

+CEMODE
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
Yes
NVM / OP
No
-
+CME Error

Description

Sets the MT to operate according to the specified mode of operation for EPS, see 3GPP TS 24.301 [22]. If the requested operation mode is not supported, an error result code is returned.
u-blox cellular modules are certified according to all the capabilities and options stated in the Protocol Implementation Conformance Statement document (PICS) of the module. The PICS, according to 3GPP TS 51.010-2 [27], 3GPP TS 34.121-2 [28], 3GPP TS 36.521-2 [29] and 3GPP TS 36.523-2 [30], is a statement of the implemented and supported capabilities and options of a device. If the user changes the command settings during the certification process, the PICS of the application device integrating a u-blox cellular module must be changed accordingly.

Syntax

TypeSyntaxResponseExample
Set
AT+CEMODE=[<mode>]
OK
AT+CEMODE=1
OK
Read
AT+CEMODE?
+CEMODE: <mode>
OK
+CEMODE: 1
OK
Test
AT+CEMODE=?
+CEMODE: (list of supported <mode>'s)
OK
+CEMODE: (0-3)
OK

Defined values

ParameterTypeDescription
<mode>
Number
Mode configuration:
  • 0: PS mode 2 of operation. The UE registers only to EPS services, and the UE’s usage setting is "data centric"
  • 1 (default and factory-programmed value for voice capable devices): CS/PS mode 1 of operation. The UE registers to both EPS and non-EPS services, and the UE’s usage setting is "voice centric"
  • 2 (default and factory-programmed value for voice not-capable devices): CS/PS mode 2 of operation. The UE registers to both EPS and non-EPS services, and the UE’s usage setting is "data centric"
  • 3: PS mode 1 of operation. The UE registers only to EPS services, and the UE’s usage setting is "voice centric"

Notes

  • A UE set to "Data centric" does not disable the E-UTRAN capability if voice services cannot be obtained. Upon receiving combined EPS/IMSI attach accept or combined TA/LA Update accept with "SMS-only" indication, a data centric UE stays in the current RAT and is not allowed to use CSFB. Upon receiving combined EPS/IMSI attach accept or combined TA/LA Update accept with "CSFB Not Preferred" indication, a data centric UE stays in the current RAT and is allowed to use CSFB.
  • A UE set to "Voice centric" shall always try to ensure that Voice service is possible. A CSFB and an IMS/CS-voice capable UE set to "Voice centric" unable to obtain voice service in E-UTRAN (e.g. CSFB and IMS voice are not supported or the configured preferences on how to handle voice services prevent usage of any available voice services), shall disable the E-UTRAN capability, which results in re-selecting GERAN or UTRAN. The E-UTRAN capability is re-enabled by the UE under the conditions described in 3GPP TS 24.301 [22].
  • The <mode> parameter is mandatory in the set command.
LEXI-R10801D-00B
  • The command settings are restored to the factory-programmed values after any MNO profile change (see +UMNOPROF).

EPS network registration status +CEREG

+CEREG
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
partial
No
Profile
No
-
+CME Error

Description

Configures the network registration URC related to EPS domain. The URC assumes a different syntax depending on the network and the <n> parameter:
  • +CEREG: <stat> when <n>=1 and there is a change in the MT’s EPS network registration status in E-UTRAN
  • +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>]] when <n>=2 and there is a change of EPS network registration status or network cell in EUTRAN
  • +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,<cause_type>,<reject_cause>]] when <n>=3 and the value of <stat> or the network cell change in EUTRAN
  • +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,,[,[<Assigned_Active_Time>,[<Assigned_Periodic_TAU>]]]]] when <n>=4 and the value of <stat>, the network cell or PSM configuration change in EUTRAN
  • +CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,[<cause_type>],[<reject_cause>][,[<Assigned_Active_Time>,[<Assigned_Periodic_TAU>]]]]] when <n>=5 and the value of <stat>, the network cell or PSM configuration change in EUTRAN
The parameters <AcT>, <tac>, <rac_or_mme>, <ci>, <cause_type>, <reject_cause>, <Assigned_Active_Time> and <Assigned_Periodic_TAU> are provided only if available.
The read command provides the same information issued by the URC together with the current value of the <n> mode configuration parameter. It returns always at least the mode configuration (<n>) and the EPS registration status (<stat>). The location parameters <tac>, <rac_or_mme>, <ci> and <AcT>, if available, are returned only when <n>=2, <n>=3, <n>=4 or <n>=5 and the MT is registered with the network. The parameters <cause_type>, <reject_cause>, if available, are returned when <n>=3 or <n>=5. The PSM related parameter <Assigned_Active_Time> is returned only when <n>=4 or <n>=5, the MT is registered with the network and PSM is granted by the network. The <Assigned_Periodic_TAU> parameter is returned only if when <n>=4 or <n>=5, the MT is registered with the network and an extended periodic TAU value (T3412_ext) is assigned.

Syntax

TypeSyntaxResponseExample
Set
AT+CEREG=[<n>]
OK
AT+CEREG=1
OK
Read
AT+CEREG?
+CEREG: <n>,<stat>[,[<tac>],[<ci>],[<AcT>[,[<cause_type>],[<reject_cause>][,[<Assigned_Active_Time>,[<Assigned_Periodic_TAU>]]]]]]
OK
+CEREG: 2,1,"3a9b","0000c33d",7
OK
Test
AT+CEREG=?
+CEREG: (list of supported <n>s)
OK
+CEREG: (0-4)
OK
URC
+CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,[<cause_type>],[<reject_cause>][,[<Assigned_Active_Time>,[<Assigned_Periodic_TAU>]]]]]
+CEREG: 1,"3a9b","0000c33d",7

Defined values

ParameterTypeDescription
<n>
Number
Mode configuration:
  • 0: network registration URC disabled
  • 1: network registration URC enabled
  • 2: network registration and location information URC enabled
  • 3: network registration, location information and EMM cause value information URC enabled
  • 4: network registration , location information information and PSM configuration URC enabled
  • 5: network registration, location information, EMM cause value information and PSM configuration URC enabled
Allowed values:
  • 0 (default value), 1, 2, 3, 4, 5
<stat>
Number
EPS registration status:
  • 0: not registered
  • 1: registered, home network
  • 2: not registered, but the MT is currently trying to attach or searching an operator to register to
  • 3: registration denied
  • 4: unknown (e.g. out of E-UTRAN coverage)
  • 5: registered, roaming
  • 8: attached for emergency bearer services only (see 3GPP TS 24.008 [12] and 3GPP TS 24.301 [22] that specify the condition when the MS is considered as attached for emergency bearer services)
Allowed values:
  • 0, 1, 2, 3, 4, 5
<tac>
String
Two bytes tracking area code in hexadecimal format. The value FFFF means that the current <tac> value is invalid.
<ci>
String
Four bytes E-UTRAN cell-id in hexadecimal format. The value FFFFFFFF means that the current <ci> value is invalid.
<AcT>
Number
Access technology of the serving cell:
  • 0: GSM
  • 3: GSM/GPRS with EDGE availability
  • 7: E-UTRAN (see 3GPP TS 44.060 [50] that specifies the System Information messages which give the information about whether the serving cell supports EGPRS)
  • 8: E-UTRAN EC-GSM-IoT (A/Gb mode)
  • 9: E-UTRAN (NB-S1 mode)
  • 14: Satellite E-UTRAN (NB-S1 mode)
Allowed values:
  • 7
<cause_type>
Number
<reject_cause> type:
  • 0: indicates that <reject_cause> contains an EMM cause value, see 3GPP TS 24.301 [22] Annex A
  • 1: indicates that <reject_cause> contains a manufacture-specific cause
Allowed values:
  • 0
<reject_cause>
Number
Cause of the failed registration. The value is of type as defined by <cause_type>
<Assigned_Active_Time>
String
One byte in an 8 bit format. Assigned Active Time value (T3324) allocated to the UE. The assigned Active Time value is coded as one byte (octet 3) of the GPRS Timer 2 information element coded as bit format (e.g. "00100100" equals 4 minutes). For the coding and the value range, see the GPRS Timer 2 IE in 3GPP TS 24.008 table 10.5.163/3GPP TS 24.008 [12]. See also 3GPP TS 23.682 [51], 3GPP TS 23.060 [46]) and 3GPP TS 23.401 [52].
<Assigned_Periodic_TAU>
String
One byte in an 8 bit format. Assigned extended periodic TAU value (T3412_ext) allocated to the UE. The assigned extended periodic TAU value is coded as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000111" equals 70 hours). For the coding and the value range, see the GPRS Timer 3 IE in 3GPP TS 24.008 table 10.5.163a/3GPP TS 24.008 [12]. See also 3GPP TS 23.682 [51] and 3GPP TS 23.401 [52].
<rac_or_mme>
String
RAC (Routing Area Code) or MME Code (Mobile Management Entity) in hexadecimal format

Notes

  • The location parameters <tac>, <ci> and <AcT> are returned, if available, also in limited service state (i.e. <stat>=3).
  • If <stat>=0 the MT is not registered and it does not search an operator to register to.

Traffic flow template read dynamic parameters +CGTFTRDP

+CGTFTRDP
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
No
No
No
-
+CME Error

Description

Returns the relevant information about traffic flow template for an active secondary or non secondary PDP context specified by <cid> together with the additional network assigned values when established by the network.
The test command returns a list of <cid>s associated with active secondary and non secondary contexts.
If the parameter <cid> is omitted, the relevant information for all active secondary non secondary PDP contexts is returned.
The parameters of both network and MT/TA initiated PDP contexts will be returned.

Syntax

TypeSyntaxResponseExample
Set
AT+CGTFTRDP=[<cid>]
[+CGTFTRDP: <cid>,<packet_filter_identifier>,<evaluation_precedence_index>,<remote_address_and_subnet_mask>,<protocol_number_(ipv4)/next_header_(ipv6)>,<local_port_range>,<remote_port_range>,<ipsec_security_parameter index (spi)>,<type_of_service_(tos)(ipv4)and_mask/traffic_class(ipv6)and_mask>,<flow_label(ipv6)>,<direction>,<NW_packet_filter_Identifier>,<local_address_and_subnet_mask>]
[+CGTFTRDP: <cid>,<packet_filter_identifier>,<evaluation_precedence_index>,<remote_address_and_subnet_mask>,<protocol_number(ipv4)/next_header_(ipv6)>,<local_port_range>,<remote_port_range>,<ipsec_security_parameter index (spi)>,<type_of_service_(tos)(ipv4)and_mask/traffic_class(ipv6)_and_mask>,<flow_label(ipv6)>,<direction>,<NW_packet_filter_Identifier>,<local_address_and_subnet_mask>
[…​]]
OK
AT+CGTFTRDP=2
+CGTFTRDP: 2,1,1,"8.9.10.11.255.255.0.0",0,0.65535,0.65535,0,0,0,0,0,"1.2.12.11.255.255.0.0"
OK
Test
AT+CGTFTRDP=?
+CGTFTRDP: (list of <cid>s associated with active contexts)
OK
+CGTFTRDP: 1,2
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>
<packet_filter_identifier>
Number
Packet filter:
  • Range: 1 - 8
<evaluation_precedence_index>
Number
Evaluation precedence index that is unique within all TFTs associated with the PDP contexts that share the same PDP address:
  • Range: 0-255 (from highest evaluation precedence to lowest evaluation precedence)
<remote_address_and_subnet_mask>
String
Specifies the remote address and subnet mask attribute of a valid packet filter. Consists of dot-separated numeric (0-255) parameters on the form:
  • "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
  • "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)>
Number
Specifies the Protocol Number / Next Header attribute of a valid packet filter. It shall contain either an IPv4 Protocol Number or an IPv6 Next Header value.
  • Range: 0 -255
<local_port_range>
Number
Specifies the destination port range attribute of a valid packet filter:
  • The range goes from 0 to 65535
<remote_port_range>
Number
Specifies the source port range attribute of a valid packet filter:
  • The range goes from 0 to 65535
<ipsec_security_parameter index_(spi)>
String
IPSec SPI attribute of a valid packet filter which is a 32-bit field.
  • Range: 0x00000000 - 0xFFFFFFFF
<type_of_service_(tos)(ipv4)and_mask/traffic_class(ipv6)_and_mask>
String
dot-separated numbers on the form "t.m" that specifies the Type of Service / Traffic Class and Mask attribute of a valid packet filter. It shall contain either an IPv4 TOS octet or an IPv6 Traffic Class octet along with a mask defining which of the 8 bits should be used for matching.
  • Range: 0-65535
<flow_label(ipv6)>
String
Specifies the Flow Label attribute of a valid packet filter. It is only valid for IPv6.
  • Range: 0x00000 - 0xFFFFF
<direction>
Number
Specifies the transmission direction in which the packet filter shall be applied:
  • 0: Pre Release 7 TFT Filter (see 3GPP TS 24.008 [12], table 10.5.162)
  • 1: uplink
  • 2: downlink
  • 3: bidirectional (used for uplink and downlink)
<NW_packet_filter_Identifier>
Number
The value range is from 1 to 16. In LTE the value is assigned by the network when the dedicated EPS bearer is established.
<local_address_and_subnet_mask>
String
Specifies the local address and subnet mask attribute of a valid packet filter. Consists of dot-separated numeric (0-255) parameters on the form:
  • "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
  • "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

Define EPS quality of service +CGEQOS

+CGEQOS
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
partial
No
NVM
No
-
+CME Error

Description

Allows the TE to specify the EPS quality of service parameters <cid>, <QCI>, <DL_GBR>, <UL_GBR>, <DL_MBR> and <UL_MBR> for a PDP context or traffic flows (see 3GPP TS 24.301 [22] and 3GPP TS 23.203 [53]). When in UMTS/GPRS the MT applies a mapping function to UTMS/GPRS quality of service.
The read command returns the current settings for each defined QoS.
The set command +CGEQOS=<cid> causes the values for context number <cid> to become undefined.

Syntax

TypeSyntaxResponseExample
Set
AT+CGEQOS=[<cid>[,<QCI>[,<DL_GBR>,<UL_GBR>[,<DL_MBR>,<UL_MBR>]]]]
OK
AT+CGEQOS=1,1,2500,7000,2500,7000
OK
Read
AT+CGEQOS?
[+CGEQOS: <cid>,<QCI>,[<DL_GBR>,<UL_GBR>],[<DL_MBR>,<UL_MBR>]]
[+CGEQOS: <cid>,<QCI>,[<DL_GBR>,<UL_GBR>],[<DL_MBR>,<UL_MBR>]
[…​]]
OK
+CGEQOS: 1,1,2500,7000,2500,7000
OK
Test
AT+CGEQOS=?
+CGEQOS: (list of supported <cid>s),(list of supported <QCI>s),(list of supported <DL_GBR>s),(list of supported <UL_GBR>s),(list of supported <DL_MBR>s),(list of supported <UL_MBR>s)
OK
+CGEQOS: (1-8),(0-9),(0-5000),(0-21000),(0-5000),(0-21000)
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>.
<QCI>
Number
Specifies a class of EPS QoS (see 3GPP TS 24.301 [22]):
  • 0: QCI is selected by network
  • 1-4: value range for guaranteed bit rate traffic flows
  • 5-9: value range for non-guaranteed bit rate traffic flows
  • 75: value for guaranteed bit rate traffic flows
  • 79: value for non-guaranteed bit rate traffic flows
  • 128-254: value range for Operator-specific QCIs
Allowed values:
  • 0, 1-4, 5-9, 75, 79
<DL_GBR>
Number
Indicates DL guaranteed bit rate (GBR) in case of GBR QCI. The value is expressed in kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [22]).
<UL_GBR>
Number
Indicates UL guaranteed bit rate (GBR) in case of GBR QCI. The value is expressed in kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [22]).
<DL_MBR>
Number
Indicates DL maximum bit rate (MBR) in case of GBR QCI. The value is expressed in kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [22]).
<UL_MBR>
Number
Indicates UL maximum bit rate (MBR) in case of GBR QCI. The value is expressed in kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [22]).

EPS quality of service read dynamic parameters +CGEQOSRDP

+CGEQOSRDP
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
Yes
No
No
-
+CME Error

Description

Returns the quality of service parameters <QCI>, <DL_GBR>, <UL_GBR>, <DL_MBR> and <UL_MBR> of the active secondary or non secondary PDP context associated to the provided context identifier <cid>.
The test command returns a list of <cid>s associated with secondary or non secondary active PDP contexts.
The parameters of both network and MT/TA initiated PDP contexts will be returned.
If the parameter <cid> is omitted, the quality of service parameters for all the secondary and non secondary active PDP contexts are returned.

Syntax

TypeSyntaxResponseExample
Set
AT+CGEQOSRDP=[<cid>]
[+CGEQOSRDP: <cid>,<QCI>,[<DL_GBR>,<UL_GBR>],[<DL_MBR>,<UL_MBR>],[<DL_AMBR>,<UL_AMBR>]]
[+CGEQOSRDP: <cid>,<QCI>,[<DL_GBR>,<UL_GBR>],[<DL_MBR>,<UL_MBR>],[<DL_AMBR>,<UL_AMBR>]
[…​]]
OK
AT+CGEQOSRDP=1
+CGEQOSRDP: 1,7,0,0,0,0,0,0
OK
Test
AT+CGEQOSRDP=?
+CGEQOSRDP: (list of <cid>s associated with active contexts)
OK
+CGEQOSRDP: 1
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>.
<QCI>
Number
Specifies a class of EPS QoS (see 3GPP TS 24.301 [22]):
  • 0: QCI is selected by network
  • 1-4: value range for guaranteed bit rate traffic flows
  • 5-9: value range for non-guaranteed bit rate traffic flows
  • 65-66: value range for guaranteed bit rate traffic flows
  • 69-70: value range for non-guaranteed bit rate traffic flows
  • 75: value for guaranteed bit rate traffic flows
  • 79: value for non-guaranteed bit rate traffic flows
  • 128-254: value range for operator-specific QCIs
<DL_GBR>
Number
Indicates DL guaranteed bit rate (GBR) in case of GBR QCI. The value is expressed in kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [22]).
<UL_GBR>
Number
Indicates UL guaranteed bit rate (GBR) in case of GBR QCI. The value is expressed in kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [22]).
<DL_MBR>
Number
Indicates DL maximum bit rate (MBR) in case of GBR QCI. The value is expressed in kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [22]).
<UL_MBR>
Number
Indicates UL maximum bit rate (MBR) in case of GBR QCI. The value is expressed in kb/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [22]).
<DL_AMBR>
Number
Indicates DL APN aggregate maximum bit rate (MBR) (see 3GPP TS 24.301 [22]). The value is expressed in kb/s.
<UL_AMBR>
Number
Indicates UL APN aggregate maximum bit rate (MBR) (see 3GPP TS 24.301 [22]). The value is expressed in kb/s.

Secondary PDP context read dynamic parameters +CGSCONTRDP

+CGSCONTRDP
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
No
No
No
-
+CME Error

Description

Returns the <p_cid>, <bearer_id> and <IM_CN_Signalling_Flag_Ind> parameters for an active secondary PDP context having the context identifier <cid>. The test command returns the list of <cid>s associated with active secondary PDP contexts.
If the parameter <cid> is omitted, the relevant information for all active secondary PDP contexts is returned.
The parameters for UE initiated and network initiated PDP contexts are returned.
In EPS, the Traffic Flow parameters are returned.

Syntax

TypeSyntaxResponseExample
Set
AT+CGSCONTRDP=[<cid>]
[+CGSCONTRDP: <cid>,<p_cid>,<bearer_id>[,<IM_CN_Signalling_Flag_Ind>]]
[+CGSCONTRDP: <cid>,<p_cid>,<bearer_id>[,<IM_CN_Signalling_Flag_Ind>]
[…​]]
OK
AT+CGSCONTRDP=2
+CGSCONTRDP: 2,1,6,0
OK
Test
AT+CGSCONTRDP=?
+CGSCONTRDP: (list of active secondary PDP contexts)
OK
+CGSCONTRDP: 2
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>
<p_cid>
Number
Numeric parameter that identifies the particular PDP context definition, specified using +CGDCONT, to which a secondary PDP context definition will be associated using +CGDSCONT.
This parameter is only locally valid on the interface TE-MT.
<bearer_id>
Number
Bearer identification, i.e. the EPS bearer in EPS and the NSAPI in UMTS/GPRS. The allowed range goes from 5 to 16.
<IM_CN_Signalling_Flag_Ind>
Number
Shows whether the PDP context is for IM CN subsystem-related signalling only or not:
  • 0: PDP context is not for IM CN subsystem-related signalling only
  • 1: PDP context is for IM CN subsystem-related signalling only

PDP context read dynamic parameters +CGCONTRDP

+CGCONTRDP
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
partial
No
No
No
-
+CME Error

Description

Returns the relevant information <bearer_id>, <APN>, <local_addr_and_subnet_mask>, <gw_addr>, <DNS_prim_addr>, <DNS_sec_addr>, <P-CSCF_prim_addr>, <P-CSCF_sec_addr>, <IM_CN_Signalling_Flag_Ind>, <LIPA_indication>, <IPv4_MTU> and <WLAN_offload> for an active non secondary PDP context with the context identifier <cid>.
If the MT indicates more than two IP addresses of P-CSCF servers or more than two IP addresses of DNS servers, multiple lines of information per <cid> will be returned.
A set command with an undefined <cid> provides an error result code.
The command is not effective if the <PDP_type>="Non-IP".

Syntax

TypeSyntaxResponseExample
Set
AT+CGCONTRDP[=<cid>]
[+CGCONTRDP: <cid>,<bearer_id>,<APN>[,<local_addr_and_subnet_mask>[,<gw_addr>[,<DNS_prim_addr>[,<DNS_sec_addr>[,<P-CSCF_prim_addr>[,<P-CSCF_sec_addr>[,<IM_CN_Signalling_Flag_Ind>[,<LIPA_indication>[,<IPv4_MTU>[,<WLAN_offload>[,<Local_Addr_Ind>[,<Non_IP_MTU>[,<Serving_PLMN_rate_control_value>]]]]]]]]]]]]]]
[+CGCONTRDP: <cid>,<bearer_id>,<APN>[,<local_addr_and_subnet_mask> [,<gw_addr>[,<DNS_prim_addr>[,<DNS_sec_addr>[,<P-CSCF_prim_addr>[,<P-CSCF_sec_addr>[,<IM_CN_Signalling_Flag_Ind>[,<LIPA_indication>[,<IPv4_MTU>[,<WLAN_offload>[,<Local_Addr_Ind>[,<Non_IP_MTU>[,<Serving_PLMN_rate_control_value>]]]]]]]]]]]]]
[…​]]
OK
AT+CGCONTRDP=1
+CGCONTRDP: 1,0,"web.omnitel.it", "109.113.62.238.255.255.255.255","109.113.62.201","83.224.70.77", "83.224.70.54",,,,0,0,0,0
OK
Test
AT+CGCONTRDP=?
+CGCONTRDP: (list of active non secondary PDP contexts)
OK
+CGCONTRDP: 1
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>.
<APN>
String
See <APN>.
<bearer_id>
Number
Identifies the bearer, i.e. the EPS bearer in EPS and the NSAPI in UMTS/GPRS. The range goes from 5 to 16.
<local_addr_and_subnet_mask>
String
IP address and subnet mask of the MT. The string is given as dot-separated numeric (0-255) parameters on the form:
  • "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
  • "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
<gw_addr>
String
Gateway address of the MT. The string is given as dot-separated numeric (0-255) parameters.
<DNS_prim_addr>
String
IP address of the primary DNS server.
<DNS_sec_addr>
String
IP address of the secondary DNS server.
<P-CSCF_prim_addr>
String
IP address of the primary P-CSCF server.
<P-CSCF_sec_addr>
String
IP address of the secondary P-CSCF server.
<IM_CN_Signalling_Flag_Ind>
Number
Shows whether the PDP context is for IM CN subsystem-related signalling only or not:
  • 0: PDP context is not for IM CN subsystem-related signalling only
  • 1: PDP context is for IM CN subsystem-related signalling only
<LIPA_indication>
Number
Indicates that the PDP context provides connectivity using a LIPA PDN connection. This parameter cannot be set by the TE:
  • 0: indication not received that the PDP context provides connectivity using a LIPA PDN connection
  • 1: indication received that the PDP context provides connectivity using a LIPA PDN connection
<IPv4_MTU>
Number
Provides the IPv4 MTU size in octets.
<WLAN_offload>
Number
Indicates whether the traffic can be offloaded using the specified PDN connection via a WLAN. This refers to bits 1 and 2 of the WLAN offload acceptability IE as specified in 3GPP TS 24.008 [12] subclause 10.5.6.20. Allowed values:
  • 0: offloading the traffic of the PDN connection via a WLAN when in S1 mode or when in Iu mode is not acceptable
  • 1: offloading the traffic of the PDN connection via a WLAN when in S1 mode is acceptable, but not acceptable in Iu mode
  • 2: offloading the traffic of the PDN connection via a WLAN when in Iu mode is acceptable, but not acceptable in S1 mode
  • 3: offloading the traffic of the PDN connection via a WLAN when in S1 mode or when in Iu mode is acceptable
<Local_Addr_Ind>
Number
Indicates whether the MS and the network support local IP address in TFTs (see 3GPP TS 24.301 [22] and 3GPP TS 24.008 [12] subclause 10.5.6.3). Allowed values:
  • 0: indicates that the MS or the network or both do not support local IP address in TFTs
  • 1: indicates that the MS and the network support local IP address in TFTs
<Non_IP_MTU>
Number
Non-IP MTU size in octets.
<Serving_PLMN_rate_control_value>
Number
Indicates the maximum number of uplink messages the UE is allowed to send in a 6 minutes interval. This refers to octet 3 to 4 of the Serving PLMN rate control IE as specified in 3GPP TS 24.301 [22].

Traffic flow template +CGTFT

+CGTFT
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
Yes
No
No
-
+CME Error

Description

Allows the TE to specify a packet filter (PF) for a traffic flow template (TFT) that is used in the gateway GPRS support node (GGSN) for routing of down-link packets onto different QoS flows towards the TE (see the 3GPP TS 23.060 [46] and 3GPP TS 24.008 [12]). A TFT is identified by a <packet filter identifier> and each packet filter also has an <evaluation precedence index>. The set command specifies a Packet Filters to be added to the TFT stored in the MT and used for the context identified by <cid>. This command is effectively an extension of the +CGDCONT and +CGDSCONT AT commands that shall be issued previously.
The syntax AT+CGTFT=<cid> causes all of the Packet Filters in the TFT for the specified <cid> to become undefined.
Not all the parameters combinations are allowed in a Packet Filter, some may coexist but others are mutually exclusive. The possible combinations are specified in 3GPP TS 23.060 [46].
A valid packet filter must contain a unique identifier and a unique evaluation precedence index within all TFTs for one PDP address. The network will reject the activation of a secondary PDP context if the corresponding packet filter contains an identifier or an evaluation precedence index which is not unique within all TFTs for one PDP address.
The command is not effective if the <PDP_type>="Non-IP".

Syntax

TypeSyntaxResponseExample
Set
AT+CGTFT=[<cid>,<packet_filter_identifier>,<evaluation_precedence_index>[,<remote_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>[,<local_address_and_subnet_mask>]]]]]]]]]]]
OK
AT+CGTFT=2,1,1,"109.115.183.216.255.255.0.0"
OK
Read
AT+CGTFT?
+CGTFT: <cid>,<packet_filter_identifier>,<evaluation_precedence_index>,<remote_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>,<local_address_and_subnet_mask>
[+CGTFT: <cid>,<packet_filter_identifier>,<evaluation_precedence_index>,<remote_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>,<local_address_and_subnet_mask>
[…​]]
OK
+CGTFT: 2,1,1,"109.115.183.216.255.255.0.0",0,"0.0","0.0",00000000,"0.0",00000
OK
Test
AT+CGTFT=?
+CGTFT: <PDP_type>,(list of supported <packet_filter_identifier>s),(list of supported <evaluation_precedence_index>s),(list of supported <remote_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),(list of supported <local_address_and_subnet_mask>s)
[+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),(list of supported <local_address_and_subnet_mask>s)
[…​]]
OK
+CGTFT: IP,(1-16),(0-255),("0.0.0.0.0.0.0.0-255.255.255.255.255.255.255.255"),(0-255),("0.0-65535.65535"),("0.0-65535.65535"),(00000000-ffffffff),("0.0-255.255"),(00000-FFFFF),("0.0.0.0.0.0.0.0-255.255.255.255.255.255.255.255")
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>
<PDP_type>
String
<packet_filter_identifier>
Number
Packet filter:
  • Range: 1-11
<evaluation_precedence_index>
Number
Evaluation precedence index that is unique within all TFTs associated with the PDP contexts that share the same PDP address:
  • Range: 0-255 (from highest evaluation precedence to lowest evaluation precedence)
<remote_address_and_subnet_mask>
String
Specifies the remote address and subnet mask attribute of a valid packet filter. Consists of dot-separated numeric (0-255) parameters on the form:
  • "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
  • "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)>
Number
Specifies the Protocol Number / Next Header attribute of a valid packet filter. It shall contain either an IPv4 Protocol Number or an IPv6 Next Header value:
  • Range: 0-255
<destination_port_range>
String
String parameter given as dot-separated numbers on the form "f.t" that specifies the destination port range attribute of a valid packet filter:
  • Range: 0-65535
<source_port_range>
String
Dot-separated numbers on the form "f.t" that specifies the source port range attribute of a valid packet filter:
  • Range: 0-65535
<ipsec_security_parameter_index_(spi)>
Number
IPSec SPI attribute of a valid packet filter which is a 32-bit field:
  • Range: 00000000-FFFFFFFF
<type_of_service_(tos)_(ipv4)_and_mask-traffic_class_(ipv6)_and_mask>
String
Dot-separated numbers on the form "t.m" that specifies the Type of Service / Traffic Class and Mask attribute of a valid packet filter. It shall contain either an IPv4 TOS octet or an IPv6 Traffic Class octet along with a mask defining which of the 8 bits should be used for matching.
  • Range: 0-255
<flow_label(ipv6)>
Number
Specifies the Flow Label attribute of a valid packet filter. It shall contain an IPv6 flow label, which is a 20-bit field. It only is valid for IPv6.
  • Range: 00000-FFFFF
<direction>
Number
Specifies the transmission direction in which the packet filter shall be applied:
  • 0: Pre Release 7 TFT Filter (see 3GPP TS 24.008 [12], table 10.5.162)
  • 1: uplink
  • 2: downlink
  • 3: bidirectional (used for uplink and downlink)
<local_address_and_subnet_mask>
String
Specifies the local address and subnet mask attribute of a valid packet filter. Consists of dot-separated numeric (0-255) parameters on the form:
  • "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4
  • "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

Notes

  • The PIN insertion is not mandatory before the command execution.

Uplink user data plane configuration +UDCONF=9

+UDCONF=9
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
No
No
No
-
+CME Error

Description

Enables or disables the uplink user data plane. When the uplink data traffic is disabled, the module will not be able to transmit data to the cellular network.
The AT command is volatile.

Syntax

TypeSyntaxResponseExample
Set
AT+UDCONF=9,<UUDP_enable>[,<drop_rate>]
OK
AT+UDCONF=9,0,50
OK
Read
AT+UDCONF=9
+UDCONF: 9,<UUDP_enable>,<drop_rate>
OK
AT+UDCONF=9
+UDCONF: 9,0,50
OK

Defined values

ParameterTypeDescription
<UUDP_enable>
Number
Configures the uplink user data plane feature:
  • 0: uplink user data plane disabled
  • 1 (factory-programmed value): uplink user data plane enabled
<drop_rate>
Number
Percentage of dropped packets. To be used in validation mode only. The allowed values are in range 1-100. The parameter can only be set when disabling the data plane (<UUDP_enable>=0), and, if not specified, the percentage of dropped packets is set to 100% by default.

Notes

* The <drop_rate> parameter is not supported. * Only PPP packets and packets sent by the embedded IP stack can be dropped before being sent to the cellular modem.

APN rate control +CGAPNRC

+CGAPNRC
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
No
No
No
-
+CME Error

Description

Returns the APN rate control parameters (see the 3GPP TS 24.008 [12]) associated to the corresponding <cid>.
If the <cid> parameter is omitted, the APN rate control parameters for all active contexts are returned.
The test command returns the list of <cid>s associated with secondary and non secondary active PDP contexts.

Syntax

TypeSyntaxResponseExample
Set
AT+CGAPNRC[=<cid>]
[+CGAPNRC: <cid>[,<Additional_exception_reports>[,<Uplink_time_unit>[,<Maximum_uplink_rate>]]]
[…​]
[+CGAPNRC: <cid>[,<Additional_exception_reports>[,<Uplink_time_unit>[,<Maximum_uplink_rate>]]]]]
OK
AT+CGAPNRC=1
+CGAPNRC: 1,0,2,2
OK
Test
AT+CGAPNRC=?
+CGAPNRC: (list of <cid>s associated with active contexts)
OK
+CGAPNRC: (1,2)
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>
<Additional_exception_reports>
Number
Indicates whether or not additional exception reports are allowed to be sent when the maximum uplink rate is reached. This refers to bit 4 of octet 1 of the APN rate control parameters (see the 3GPP TS 24.008 [12] subclause 10.5.6.3.2):
  • 0: Additional exception reports are not allowed to be sent
  • 1: Additional exception reports are allowed to be sent
<Uplink_time_unit>
Number
Specifies the time unit to be used for the maximum uplink rate. This refers to bit 1 to 3 of octet 1 of the APN rate control parameters (see the 3GPP TS 24.008 [12] subclause 10.5.6.3.2):
  • 0: unrestricted
  • 1: minute
  • 2: hour
  • 3: day
  • 4: week
<Maximum_uplink_rate>
Number
Specifies the maximum number of messages the UE is restricted to send per uplink time unit. This refers to octet 2 to 4 of the APN rate control parameters (see the 3GPP TS 24.008 [12] subclause 10.5.6.3.2).

Define PDP context authentication parameters +CGAUTH

+CGAUTH
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
No
No
No
-
+CME Error

Description

Configures the authentication parameters for a PDP context, identified by the <cid> parameter.
The read command lists the settings for all the defined <cid>s.

Syntax

TypeSyntaxResponseExample
Set
AT+CGAUTH=<cid>[,<auth_prot>[,<userid>[,<password>]]]
OK
AT+CGAUTH=1,2,"1234","4321"
OK
Read
AT+CGAUTH?
[+CGAUTH: <cid>[,<auth_prot>[,<userid>[,<password>]]]
[..]]
OK
+CGAUTH: 1,1,"1234","4321"
OK
Test
AT+CGAUTH=?
+CGAUTH: (list of supported <cid>s),(list of supported <auth_prot>s),(list of supported <userid>s),(list of supported <password>s)
OK
+CGAUTH: (0-10),(0,1,2),(0-60),(0-60)
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>.
<auth_prot>
Number
Authentication protocol used for the PDP context:
  • 0 (default value): none; the <userid> and <password> parameter values are removed if defined previously
  • 1: PAP
  • 2: CHAP
<userid>
String
Username to access the IP network; the maximum length is 60 characters. The parameter will be provided by the network if it supports the PDP context authentication.
<password>
String
Password to access the IP network; the maximum length is 60 characters. The parameter will be provided by the network if it supports the PDP context authentication.

Disable data when roaming +UDCONF=76

+UDCONF=76
Modules
All products
Attributes
Syntax
PIN required
Settings saved
Can be aborted
Response time
Error reference
full
No
NVM
No
-
+CME Error

Description

Disables the packet data when roaming. When data is disabled on the specified PDP context, the module will not be able to send IP packets when roaming on a network. The factory-programmed value is data enabled in roaming.
Configuration changes are effective at the next power on.

Syntax

TypeSyntaxResponseExample
Set
AT+UDCONF=76,<cid>,<data_flag>
OK
AT+UDCONF=76,1,0
OK
Read
AT+UDCONF=76
+UDCONF: 76,<cid>,<data_flag>
OK
AT+UDCONF=76
+UDCONF: 76,1,0
OK

Defined values

ParameterTypeDescription
<cid>
Number
See <cid>.
<data_flag>
Number
Packet data configuration when roaming:
  • 0 (factory-programmed value): OFF - data is enabled when roaming
  • 1: ON - data is disabled when roaming

Notes

  • The <cid> parameter is not supported: it is ignored and can be omitted in the set command, value 255 is returned in the read command response.
  • In Global (+UMNOPROF: 90) and Verizon (+UMNOPROF: 3) MNO profiles the command has no effect, i.e. packet data is not disabled in roaming.
  • The command has no effect on PPP, i.e. PPP data is not disabled in roaming.
LEXI-R10801D-00B
  • The command settings are restored to the factory-programmed values after any MNO profile change (see +UMNOPROF).
Last updated: 13 January 2025
Need help?Contact Support
Questions?Contact us