10.1.23 PDP context read dynamic parameters +CGCONTRDP
27.0073GPPAT command set for User Equipment (UE)Release 18TS
Table 10.1.23-1: +CGCONTRDP action command syntax
Command |
Possible response(s) |
+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>[,<LIPA_indication>[,<IPv4_MTU>[,<WLAN_Offload>[,<Local_Addr_Ind>[,<Non-IP_MTU>[,<Serving_PLMN_rate_control_value>[,<Reliable_Data_Service>[,<PS_Data_Off_Support>[,<PDU_session_id>,<QFI>[,<SSC_mode>[,<S-NSSAI>[,<Access_type>[,<RQ_timer>[,<Always-on_ind>[,<Ethernet_MTU>[,<Unstructured_Link_MTU>[,<PDP_type>[,<EDC_policy_ind>[,<RSN>[,<ECSConf_info_ind>]]]]]]]]]]]]]]]]]]]]]]]]]]]] [<CR><LF>+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>[,<LIPA_indication>[,<IPv4_MTU>[,<WLAN_Offload>[,<Local_Addr_Ind>[,<Non-IP_MTU>[,<Serving_PLMN_rate_control_value>[,<Reliable_Data_Service>[,<PS_Data_Off_Support>[,<PDU_session_id>,<QFI>[,<SSC_mode>[,<S-NSSAI>[,<Access_type>[,<RQ_timer>[,<Always-on_ind>[,<Ethernet_MTU>[,<Unstructured_Link_MTU>[,<PDP_type>[,<EDC_policy_ind>[,<RSN>[,<ECSConf_info_ind>]]]]]]]]]]]]]]]]]]]]]]]]]]] […]] |
+CGCONTRDP=? |
+CGCONTRDP: (list of <cid>s associated with active contexts) |
NOTE: The syntax of the AT Set Command is corrected to be according to ITU‑T Recommendation V.250 [14]. Older versions of the specification specify incorrect syntax +CGCONTRDP=[<cid>] |
Description
The execution command 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>, <LIPA_indication>, <IPv4_MTU>, <WLAN_Offload>, <Non-IP_MTU>, <Serving_PLMN_rate_control_value>, <Reliable_Data_Service>, <PS_Data_Off_Support>, <PDU_session_id>, <QFI>, <SSC_mode>, <S-NSSAI>, <Access_type>, <RQ_timer>, <Always-on_ind>, <Ethernet_MTU>, <Unstructured_Link_MTU>, < PDP_type>, <EDC_policy_ind> and <ECSConf_info_ind>for an active non secondary PDP context or a QoS flow of the default QoS rule 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.
If the MT has dual stack capabilities, at least one pair of lines with information is returned per <cid>. First one line with the IPv4 parameters followed by one line with the IPv6 parameters. If this MT with dual stack capabilities indicates more than two IP addresses of P-CSCF servers or more than two IP addresses of DNS servers, multiple of such pairs of lines are returned.
NOTE: If the MT doesn’t have all the IP addresses to be included in a line, e.g. in case the UE received four IP addresses of DNS servers and two IP addresses of P-CSCF servers, the parameter value representing an IP address that can not be populated is set to an empty string or an absent string.
If the parameter <cid> is omitted, the relevant information for all active non secondary PDP contexts is returned.
The test command returns a list of <cid>s associated with active non secondary contexts.
Defined values
<cid>: integer type; specifies a particular non secondary PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands (see the +CGDCONT and +CGDSCONT commands).
<bearer_id>: integer type; identifies the bearer, i.e. the EPS bearer and the NSAPI.
<apn>: string type; a logical name that was used to select the GGSN or the external packet data network.
<local_addr and subnet_mask>: string type; shows the 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 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.
When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP.
<gw_addr>: string type; shows the Gateway Address of the MT. The string is given as dot-separated numeric (0-255) parameters.
When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP.
<DNS_prim_addr>: string type; shows the IP address of the primary DNS server.
When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP.
<DNS_sec_addr>: string type; shows the IP address of the secondary DNS server.
When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP.
<P_CSCF_prim_addr>: string type; shows the IP address of the primary P-CSCF server.
When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP.
<P_CSCF_sec_addr>: string type; shows the IP address of the secondary P-CSCF server.
When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form of +CGCONTRDP.
<IM_CN_Signalling_Flag>: integer type; 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>: integer type; 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>: integer type; shows the IPv4 MTU size in octets.
<WLAN_Offload>: integer type; indicates whether traffic can be offloaded using the specified PDN connection via a WLAN or not. This refers to bits 1 and 2 of the WLAN offload acceptability IE as specified in 3GPP TS 24.008 [8] clause 10.5.6.20.
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>: integer type; indicates whether or not the MS and the network support 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 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>: integer type; shows the Non-IP MTU size in octets.
<Serving_PLMN_rate_control_value>: integer type; indicates the maximum number of uplink messages the UE is allowed to send in a 6 minute interval. This refers to octet 3 to 4 of the Serving PLMN rate control IE as specified in 3GPP TS 24.301 [8] clause 9.9.4.28.
<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
<PS_Data_Off_Support>: integer type; indicates whether the network supports PS data off or not, see 3GPP TS 24.008 [8] clause 4.7.1.10 and 3GPP TS 24.301 [83] clause 6.3.10.
0 indicates that the network does not support PS data off
1 indicates that the network supports PS data off
<PDU_session_id>: integer type; identifies the PDU session, see 3GPP TS 24.501 [161].
<QFI>: integer type; identifies the QoS flow, see 3GPP TS 24.501 [161].
<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 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]. Refer parameter <S-NSSAI> in clause 10.1.1. This parameter shall not be subject to conventional character conversion as per +CSCS.
<Access_type>: integer type; indicates the access type over which the PDU session is established in 5GS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161].
0 indicates that the established PDU is associated with 3GPP access
1 indicates that the established PDU is associated with non-3GPP access
<RQ_timer>: integer type; indicates the timer value in seconds for reflective QoS, see 3GPP TS 23.501 [165] and 3GPP TS 24.501 [161].
<Always-on_ind>: integer type; indicates whether the PDU session is an always-on PDU session, see 3GPP TS 24.501 [161].
0 indicates that the PDU session is not an always-on PDU session
1 indicates that the PDU session is an always-on PDU session
<Ethernet_MTU>: integer type; shows the Ethernet frame payload MTU size in octets.
<Unstructure_Link_MTU>: integer type; shows the unstructured link MTU size in octets.
<PDP_type>: string type; indicates the type of packet data protocol (see the +CGDCONT command)
<EDC_policy_ind>: integer type; indicates whether the network allows EDC for the PDU session or the network requires EDC for the PDU session, see 3GPP TS 24.501 [161].
0 indicates that the EDC is allowed for the PDU session
1 indicates that the EDC is required for the PDU session
<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
Optional.