10.1.1 Define PDP context +CGDCONT

27.0073GPPAT command set for User Equipment (UE)Release 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

Table 111: +CGDCONT parameter command syntax

Command		Possible response(s)
+CGDCONT=<cid>[,<PDP_type>[,<APN>[,<PDP_addr>[,<d_comp>[,<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>[,<securePCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>[,<Non-IP_MTU_discovery>[,<Reliable_Data_Service>[,<SSC_mode>[,<S-NSSAI>[,<Pref_access_type>[,<RQoS_ind>[,<MH6-PDU>[,<Always-on_req>[,<old-cid>[,<ATSSS-ST>[,<LADN-DNN_ind>[,<MA-PDU-session-information>[,<Ethernet_MTU_discovery>[,<Unstructured_Link_MTU_discovery>[,<PDU_Pair_ID>[,<RSN>[,<ECSConf_info_ind>]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
+CGDCONT?		[+CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>[,<securePCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>[,<Non-IP_MTU_discovery>[,<Reliable_Data_Service>[,<SSC_mode>[,<S-NSSAI>[,<Pref_access_type>[,<RQoS_ind>[,<MH6-PDU>[,<Always-on_req>[,<old-cid>[,<ATSSS-ST>[,<LADN-DNN_ind>[,<MA-PDU-session-information>[,<Ethernet_MTU_discovery>[,<Unstructured_Link_MTU_discovery>[,<PDU_Pair_ID>[,<RSN>[,<ECSConf_info_ind>]]]]]]]]]]]]]]]]]]]]]]]]] [<CR><LF>+CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>[,<securePCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>[,<Non-IP_MTU_discovery>[,<Reliable_Data_Service>[,<SSC_mode>[,<S-NSSAI>[,<Pref_access_type>[,<RQoS_ind>[,<MH6-PDU>[,<Always-on_req>[,<old-cid>[,<ATSSS-ST>[,<LADN-DNN_ind>[,<MA-PDU-session-information>[,<Ethernet_MTU_discovery>[,<Unstructured_Link_MTU_discovery>[,<PDU_Pair_ID>[,<RSN>[,<ECSConf_info_ind>]]]]]]]]]]]]]]]]]]]]]]]]] […]]]
+CGDCONT=?		+CGDCONT: (range of supported <cid>s),<PDP_type>,,,(list of supported <d_comp>s),(list of supported <h_comp>s),(list of supported <IPv4AddrAlloc>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 <securePCO>s),(list of supported <IPv4_MTU_discovery>s),(list of supported <Local_Addr_Ind>s),(list of supported <Non-IP_MTU_discovery>s),(list of supported <Reliable_Data_Service>s),(list of supported <SSC_mode>s),,(list of supported <Pref_access_type>s),(list of supported <RQoS_ind>s),(list of supported <MH6-PDU>s),(list of supported <Always-on_req>s),(range of supported <old-cid>s),(list of supported <ATSSS-ST>s),(list of supported <LADN-DNN_ind>s),(list of supported <MA-PDU-session-information>s),(list of supported <Ethernet_MTU_discovery>s),(list of supported <Unstructured_Link_MTU_discovery>s),(range of supported <PDU_Pair_ID>s),(list of supported <RSN>s),(list of supported <ECSConf_info_ind>s) [<CR><LF>+CGDCONT: (range of supported <cid>s),<PDP_type>,,,(list of supported <d_comp>s),(list of supported <h_comp>s),(list of supported <IPv4AddrAlloc>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 <securePCO>s),(list of supported <IPv4_MTU_discovery>s),(list of supported <Local_Addr_Ind>s),(list of supported <Non-IP_MTU_discovery>s),(list of supported <Reliable_Data_Service>s),(list of supported <SSC_mode>s),,(list of supported <Pref_access_type>s),(list of supported <RQoS_ind>s),(list of supported <MH6-PDU>s),(list of supported <Always-on_req>s),(range of supported <old-cid>s),(list of supported <ATSSS-ST>s),(list of supported <LADN-DNN_ind>s),(list of supported <MA-PDU-session-information>s),(list of supported <Ethernet_MTU_discovery>s),(list of supported <Unstructured_Link_MTU_discovery>s),(range of supported <PDU_Pair_ID>s),(list of supported <RSN>s),( list of supported <ECSConf_info_ind>s) […]]
NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined.

Description

The set command specifies PDP context parameter values for a PDP context identified by the (local) context identification parameter, <cid> and also allows the TE to specify whether security protected transmission of ESM information is requested, because the PCO can include information that requires ciphering. There can be other reasons for the UE to use security protected transmission of ESM information, e.g. if the UE needs to transfer an APN. 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.

For EPS the PDN connection and its associated EPS default bearer is identified herewith.

For 5GS the PDU session and its associated QoS flow of the default QoS rule is identified herewith.

A special form of the set command, +CGDCONT=<cid> causes the values for context number <cid> to become undefined.

If the initial PDP context is supported, the context with <cid>=0 is automatically defined at startup, see clause 10.1.0. As all other contexts, the parameters for <cid>=0 can be modified with +CGDCONT. If the initial PDP context is supported, +CGDCONT=0 resets context number 0 to its particular default settings.

The read command returns the current settings for each defined context.

The test command returns values supported as compound values. If the MT supports several PDP types, <PDP_type>, the parameter value ranges for each <PDP_type> are returned on a separate line.

Defined values

<cid>: integer type; 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 or if the initial PDP context is supported (see clause 10.1.0), minimum value = 0) is returned by the test form of the command.

NOTE 1: 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.

<PDP_type>: string type; specifies the type of packet data protocol. The default value is manufacturer specific.

X.25 ITU-T/CCITT X.25 layer 3 (Obsolete)

IP Internet Protocol (IETF STD 5 [103])

IPV6 Internet Protocol, version 6 (see RFC 2460 [106])

IPV4V6 Virtual <PDP_type> introduced to handle dual IP stack UE capability. (See 3GPP TS 24.301 [83])

OSPIH Internet Hosted Octect Stream Protocol (Obsolete)

PPP Point to Point Protocol (IETF STD 51 [104])

Non-IP Transfer of Non-IP data to external packet data network (see 3GPP TS 23.401 [82])

Ethernet Ethernet protocol (IEEE 802.3)

Unstructured Transfer of Unstructured data to the Data Network via N6 (see 3GPP TS 23.501 [165])

NOTE 2: Only IP, IPV6, IPV4V6, Non-IP and Ethernet values are supported for EPS services. Only IP, IPV6, IPV4V6, Ethernet and Unstructured values are supported for 5GS service.

<APN>: string type; a logical name that is used to select the GGSN or the external packet data network.

If the value is null or omitted, then the subscription value will be requested.

<PDP_addr>: string type; identifies the MT in the address space applicable to the PDP.

When +CGPIAF is supported, its settings can influence the format of this parameter returned with the read form of +CGDCONT.

NOTE 3: The value of this parameter is ignored with the set command. The parameter is included in the set command for backwards compatibility reasons only.

<d_comp>: integer type; controls PDP data compression (applicable for SNDCP only) (refer 3GPP TS 44.065 [61]).

0 off

1 on (manufacturer preferred compression)

2 V.42bis

3 V.44

<h_comp>: integer type; controls PDP header compression (refer 3GPP TS 44.065 [61] and 3GPP TS 25.323 [62]).

0 off

1 on (manufacturer preferred compression)

2 RFC 1144 [105] (applicable for SNDCP only)

3 RFC 2507 [107]

4 RFC 3095 [108] (applicable for PDCP only)

<IPv4AddrAlloc>: integer type; controls how the MT/TA requests to get the IPv4 address information.

0 IPv4 address allocation through NAS signalling

1 IPv4 address allocated through DHCP

<request_type>: integer type; indicates the type of PDP context activation request for the PDP context, see 3GPP TS 24.501 [161] (clause 6.4.1), 3GPP TS 24.301 [83] (clause 6.5.1.2) and 3GPP TS 24.008 [8] (clause 10.5.6.17). If the initial PDP context is supported (see clause 10.1.0) it is not allowed to assign <cid>=0 for emergency (bearer) services. According to 3GPP TS 24.008 [8] (clause 4.2.4.2.2 and clause 4.2.5.1.4) and 3GPP TS 24.301 [83] (clause 5.2.2.3.3 and clause 5.2.3.2.2), a separate PDP context must be established for emergency (bearer) services.

NOTE 4: If the PDP context for emergency (bearer) services is the only activated context, only emergency calls are allowed, see 3GPP TS 23.401 [82] clause 4.3.12.9.

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 PDP context is for new PDP context establishment

3 PDP context is for handover from a non-3GPP access network

4 PDP context is for handover of emergency (bearer) services from a non-3GPP access network

5 context is for MA PDU session establishment

NOTE 5: A PDP context established for handover of emergency (bearer) services from a non-3GPP access network has the same status as a PDP context for emergency (bearer) services.

<P-CSCF_discovery>: integer type; influences how the MT/TA requests to get the P-CSCF address, see 3GPP TS 24.229 [89] annex B and annex L.

0 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>: integer type; indicates to the network whether the PDP context is for IM CN subsystem-related signalling only or not.

0 UE indicates that the PDP context is not for IM CN subsystem-related signalling only

1 UE indicates that the PDP context is for IM CN subsystem-related signalling only

<NSLPI>: integer type; indicates the NAS signalling priority requested for this PDP context:

0 indicates that this PDP context is to be activated with the value for the low priority indicator configured in the MT.

1 indicates that this PDP context is to be activated with the value for the low priority indicator set to "MS is not configured for NAS signalling low priority".

NOTE 6: The MT utilises the provide NSLPI information as specified in 3GPP TS 24.301 [83] and 3GPP TS 24.008 [8].

<securePCO>: integer type. Specifies if security protected transmission of PCO is requested or not (applicable for EPS only, see 3GPP TS 23.401 [82] clause 6.5.1.2).

0 Security protected transmission of PCO is not requested

1 Security protected transmission of PCO is requested

<IPv4_MTU_discovery>: integer type; influences how the MT/TA requests to get the IPv4 MTU size, see 3GPP TS 24.008 [8] clause 10.5.6.3.

0 Preference of IPv4 MTU size discovery not influenced by +CGDCONT

1 Preference of IPv4 MTU size discovery through NAS signalling

<Local_Addr_Ind>: integer type; indicates to the network whether or not the MS supports local IP address in TFTs (see 3GPP TS 24.301 [83] and 3GPP TS 24.008 [8] clause 10.5.6.3).

0 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>: integer type; influences how the MT/TA requests to get the Non-IP MTU size, see 3GPP TS 24.008 [8] clause 10.5.6.3.

0 Preference of Non-IP MTU size discovery not influenced by +CGDCONT

1 Preference of Non-IP MTU size discovery through NAS signalling

<Reliable_Data_Service>: integer type; indicates whether the UE is using Reliable Data Service for a PDN connection or not, see 3GPP TS 24.301 [83] and 3GPP TS 24.008 [8] clause 10.5.6.3.

0 Reliable Data Service is not being used for the PDN connection

1 Reliable Data Service is being used for the PDN connection

<SSC_mode>: integer type; indicates the session and service continuity (SSC) mode for the PDU session in 5GS, see 3GPP TS 23.501 [165].

0 indicates that the PDU session is associated with SSC mode 1

1 indicates that the PDU session is associated with SSC mode 2

2 indicates that the PDU session is associated with SSC mode 3

<S-NSSAI>: string type in hexadecimal character format. Dependent of the form, the string can be separated by dot(s) and semicolon(s). The S-NSSAI is associated with the PDU session for identifying a network slice in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161]. For the format and the encoding of S-NSSAI, see also 3GPP TS 23.003 [7]. This parameter shall not be subject to conventional character conversion as per +CSCS. The <S-NSSAI> has one of the forms:

sst only slice/service type (SST) is present
sst;mapped_sst SST and mapped configured SST are present
sst.sd SST and slice differentiator (SD) are present
sst.sd;mapped_sst SST, SD and mapped configured SST are present
sst.sd;mapped_sst.mapped_sd SST, SD, mapped configured SST and mapped configured SD are present

<Pref_access_type>: integer type; indicates the preferred access type for the PDU session in 5GS, see 3GPP TS 23.503 [184] and 3GPP TS 24.526 [185].

0 indicates that the preferred access type is 3GPP access

1 indicates that the preferred access type is non-3GPP access

<RQoS_ind>: integer type; indicates whether the UE supports reflective QoS for the PDU session, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161].

0 indicates that reflective QoS is not supported for the PDU session

1 indicates that reflective QoS is supported for the PDU session

<MH6-PDU>: integer type; indicates whether the UE supports IPv6 multi-homing for the PDU session, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161].

0 indicates that IPv6 multi-homing is not supported for the PDU session

1 indicates that IPv6 multi-homing is supported for the PDU session

<Always-on_req>: integer type; indicates whether the UE requests to establish the PDU session as an always-on PDU session, see 3GPP TS 24.501 [161].

0 always-on PDU session is not requested

1 always-on PDU session is requested

<old-cid>: integer type; indicates the context identifier of the QoS flow of the default QoS rule of the SSC mode 2 or SSC mode 3 PDU session where the network requests relocation of the PDU session anchor.

<ATSSS-ST>: integer type; indicates the "Supported ATSSS steering functionalities and steering modes (ATSSS-ST)" for the PDU session in 5GS, see 3GPP TS 24.501 [161].

0 ATSSS not supported

1 ATSSS Low-Layer functionality with any steering mode supported

2 MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported

3 MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode supported

<LADN-DNN_ind>: integer type; indicates whether the PDP context is for a LADN DNN, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161].

0 indicates that the PDP context is not for a LADN DNN

1 indicates that the PDP context is for a LADN DNN

<MA-PDU-session-information>: integer type; indicates the value of MA PDU session information, see 3GPP TS 24.501 [161].

1 MA PDU session network upgrade is allowed

<Ethernet_MTU_discovery>: integer type; influences how the MT/TA requests to get the Ethernet frame payload MTU size, see 3GPP TS 24.008 [8] clause 10.5.6.3.

0 Preference of Ethernet frame payload MTU size discovery not influenced by +CGDCONT

1 Preference of Ethernet frame payload MTU size discovery through NAS signalling

<Unstructured_Link_MTU_discovery>: integer type; influences how the MT/TA requests to get the unstructured link MTU size, see 3GPP TS 24.008 [8] clause 10.5.6.3.

0 Preference of unstructured link MTU size discovery not influenced by +CGDCONT

1 Preference of unstructured link MTU size discovery through NAS signalling

<PDU_Pair_ID>: integer type; indicates the value of PDU session pair ID, see 3GPP TS 24.501 [161] and 3GPP TS 24.526 [185].

<RSN>: integer type; indicates the value of RSN, see 3GPP TS 24.501 [161] and 3GPP TS 24.526 [185].

0 indicates that the RSN is set to v1

1 indicates that the RSN is set to v2

<ECSConf_info_ind>: integer type; indicates whether the PDP context is for an ECS Configuration information, see 3GPP TS 23.558 [187] and 3GPP TS 24.501 [161].

0 indicates that ECS Configuration information is requested in the PCO

1 indicates that ECS Configuration information is not requested in the PCO

Implementation

Mandatory unless only a single subscribed context is supported.