Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 27.007  Word version:  17.6.0

Top   Top   Up   Prev   Next
1…   4…   5…   6…   6.10…   6.20…   7…   7.10…   7.20…   7.30…   7.40…   8…   8.10…   8.20…   8.30…   8.40…   8.50…   8.55   8.56…   8.60…   8.70…   8.80…   9…   10…   10.1.3…   10.1.10…   10.1.20…   10.1.30…   10.1.40…   10.1.50…   10.1.60…   10.1.70…   10.2…   11…   12…   13…   14…   15…   16…   17…   18…   A   B   C…   E   F   G…

 

10  Commands for packet domainWord‑p. 242

10.0  General |R8|Word‑p. 242

This clause defines commands that a TE can use to control a MT supporting packet switched services.
Packet Domain MTs vary widely in functionality. At one extreme, an advanced MT can support multiple PDP types, and use multiple external networks and QoS profiles. At the other extreme, an MT can support only a single PDP type using a single external network, and rely on the HLR to contain the PDP context definition.
A comprehensive set of Packet Domain-specific commands is defined in clause 10.1 to provide the flexibility needed by the more complex MT. The commands are designed to be expandable to accommodate new PDP types and interface protocols, merely by defining new values for many of the parameters. Multiple contexts can be activated if the interface link-layer protocol is able to support them. The commands use the extended information and error message capabilities described in this specification.
For MTs of intermediate complexity, most commands have simplified forms where certain parameters can be omitted.
For certain simple MTs, and for backwards compatibility with existing communications software as defined in TS 23.060, it is possible to control access to the Packet Domain using existing modem-compatible commands. A special dial-string syntax is defined for use with the D command. This "modem compatible" mode of operation is described in clause 10.2.
A discussion on the interaction of the AT commands, Packet Domain Management and Packet Data Protocols, together with examples of command sequences for some applications can be found in TS 23.060 and TS 27.060.
Up

10.1  Commands specific to MTs supporting the packet domainWord‑p. 242

10.1.0  General remark about EPS bearer contexts and PDP contexts |R8|Word‑p. 242

According to TS 23.401, there is a 1 to 1 mapping between active EPS bearer context and active PDP context:
  • An active default EPS bearer context is associated with an active non secondary PDP context.
  • An active dedicated EPS bearer context is associated with an active secondary PDP context.
In consequence to the implicit logical relation between EPS PDN connection and its associated Default EPS Bearer, hereafter a same non secondary PDP context identifier <p_cid> can be used to refer either an EPS PDN connection context or its associated Default EPS Bearer context.
As dedicated EPS bearer contexts are activated by the network, the network can then activate a new dedicated EPS bearer or modify an existing one to fulfil the request. For bearer resources activated by the network a context identifier is allocated by the MT/TA.
For easy reading the term PDP context is used for PDP contexts in UMTS/GPRS as well as PDN/default EPS bearers and traffic flows in EPS.
The feature "initial PDP context" may be supported and is a manufacturer specific option. For this option, the context with <cid>=0 (context number 0) is defined upon startup and does not need to be created with the +CGDCONT command. The initial PDP context has particular manufacturer specific default settings disassociated with any other default settings of +CGDCONT. When in E-UTRAN or according to the AT-command +CIPCA in GERAN and UTRAN, the initial PDP context is automatically activated by the MT following a successful registration to the network. If all active contexts are deactivated, the initial PDP context can be (re)established. This is manufacturer specific and depends on the current RAT as well as how the active contexts are deactivated.
AT commands Comments
+CGDCONTUsed to define PDN connection for EPS.
+CGACTUsed to activate a bearer resource for EPS.
+CGCONTRDPUsed to show dynamically allocated PDN parameters.
+CGEV: xxx ...Used to indicate EPS bearers operations status.
AT commands Comments
+CGACTUsed to activate a modification of a PDP context or EPS bearer resource.
+CGDSCONTUsed to define EPS Bearer Resource for a specific PDN for EPS.
+CGSCONTRDPUsed to show dynamically allocated EPS Bearer Resource parameters.
+CGCMODUsed to request a modification of a PDP context or EPS Bearer Resource.
+CGTFTUsed to define a Traffic Flow Template for a PDP context or a Traffic Flow Aggregate for an EPS bearer resource.
+CGTFTRDPUsed to show the network assigned Traffic Flow Template for an EPS bearer resource.
+CGEQOSUsed to define the EPS bearer resource Quality of Service parameter.
In UMTS/GPRS mode this would hold a mapping function to the UMTS/GPRS QoS parameters.
+CGEQOSRDPUsed to show the network assigned EPS QoS parameters for an EPS bearer resource.
In UMTS/GPRS mode this would hold a mapping function to the UMTS/GPRS QoS parameters.
+CGEV: xxx ...Used to indicate EPS PDN connection and bearer resources operations status
AT commands Comments
+CGATTUsed to attach/detach the MT from the Packet Domain service.
Up

10.1.00  General remark about 5GS PDU sessions and EPS PDN connections |R15|Word‑p. 244

According to TS 23.501 and TS 24.501 there exists a one to one mapping between a 5GS PDU session and an EPS PDN connection. A 5GS PDU session is a set of QoS flows consisting of one QoS flow of the default QoS rule and optionally one or more QoS flows of non-default QoS rule. A PDN connection is set of EPS bearer contexts and consists of at least one default EPS bearer context and optionally one or more dedicated EPS bearer contexts. A PDU session can be mapped to one default EPS bearer context and zero or more dedicated bearer EPS bearer contexts. An EPS bearer context can be mapped to one or more QoS flows. The mapping between a QoS flow and an EPS bearer context is not always one to one.
AT commands Comments
+CGDCONTUsed to define a 5GS PDU session
+CGACTUsed to activate a 5GS PDU session.
+CCSTATEREQUsed to change the state of a PDU session
+CGCMODUsed to modify a 5GS PDU session
+CGCONTRDPUsed to show dynamically allocated 5GS PDU session parameters.
+CGEV: xxx ...Used to indicate 5GS PDU session operations status.
AT commands Comments
+CGDSCONTUsed to define a 5GS QoS flow
+CGSCONTRDPUsed to show dynamically allocated 5GS QoS flow parameters
+CGTFTUsed to define QoS rules for a 5GS QoS flow
+CGTFTRDPUsed to show the network assigned QoS rules for a 5GS QoS flow
+C5GQOSUsed to define QoS flows of a 5GS PDU session
+C5GQOSRDPUsed to show the dynamically allocated QoS flows corresponding to a 5GS PDU session.
+C5GPDUAUTHSUsed to define 5G PDU Session Authentication settings.
+C5GPDUAUTHRUsed to indicate 5G PDU Session Authentication Response.
AT commands Comments
+CGATTUsed to attach/detach the MT from the packet domain service.
+C5GREGIndicates 5GS network registration status
Up

10.1.1  Define PDP context +CGDCONTWord‑p. 245

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>]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
+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>]]]]]]]]]]]]]]]]]]]]]]]]
[<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>]]]]]]]]]]]]]]]]]]]]]]]]
[...]]]
+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)
[<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)
[...]]
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.
<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)
IPV4V6
Virtual <PDP_type> introduced to handle dual IP stack UE capability. (See TS 24.301)
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 TS 23.401)
Ethernet
Ethernet protocol (IEEE 802.3)
Unstructured
Transfer of Unstructured data to the Data Network via N6 (see TS 23.501)
<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.
<d_comp>
integer type; controls PDP data compression (applicable for SNDCP only) (refer TS 44.065).
0 (default)
off
1
on (manufacturer preferred compression)
2
V.42bis
3
V.44
<h_comp>
integer type; controls PDP header compression (refer TS 44.065 and TS 25.323).
0 (default)
off
1
on (manufacturer preferred compression)
2
RFC 1144 (applicable for SNDCP only)
3
4
RFC 3095 (applicable for PDCP only)
<IPv4AddrAlloc>
integer type; controls how the MT/TA requests to get the IPv4 address information.
0 (default)
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 TS 24.501, clause 6.4.1), TS 24.301, clause 6.5.1.2) and TS 24.008, 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 TS 24.008, clause 4.2.4.2.2 and clause 4.2.5.1.4) and TS 24.301, clause 5.2.2.3.3 and clause 5.2.3.2.2), a separate PDP context must be established for emergency (bearer) services.
0 (default)
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
<P-CSCF_discovery>
integer type; influences how the MT/TA requests to get the P-CSCF address, see TS 24.229 Annex B and Annex L.
0 (default)
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 (default)
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 (default)
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".
<securePCO>
integer type. Specifies if security protected transmission of PCO is requested or not (applicable for EPS only, see TS 23.401 clause 6.5.1.2).
0 (default)
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 TS 24.008, clause 10.5.6.3.
0 (default)
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 TS 24.301 and TS 24.008, clause 10.5.6.3).
0 (default)
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 TS 24.008, clause 10.5.6.3.
0 (default)
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 TS 24.301 and TS 24.008, clause 10.5.6.3.
0 (default)
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 TS 23.501.
0 (default)
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 TS 23.501 and TS 24.501. For the format and the encoding of S-NSSAI, see also TS 23.003. 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 TS 23.503 and TS 24.526.
0 (default)
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 TS 23.501 and TS 24.501.
0 (default)
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 TS 23.501 and TS 24.501.
0 (default)
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 TS 24.501.
0 (default)
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 TS 24.501.
0 (default)
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 TS 23.501 and TS 24.501.
0 (default)
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 TS 24.501.
1 (default)
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 TS 24.008, clause 10.5.6.3.
0 (default)
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 TS 24.008, clause 10.5.6.3.
0 (default)
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 TS 24.501 and TS 24.526.
<RSN>
integer type; indicates the value of RSN, see TS 24.501 and TS 24.526.
0
indicates that the RSN is set to v1
1
indicates that the RSN is set to v2
Implementation
Mandatory unless only a single subscribed context is supported.
Up

10.1.2  Define secondary PDP context +CGDSCONTWord‑p. 252

Command Possible response(s)
+CGDSCONT=<cid>,<p_cid>[,<d_comp>[,<h_comp>[,<IM_CN_Signalling_Flag_Ind>]]]
+CGDSCONT?[+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>,<IM_CN_Signalling_Flag_Ind>]
[<CR><LF>+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>,<IM_CN_Signalling_Flag_Ind> [...]]
+CGDSCONT=? +CGDSCONT: (range of supported <cid>s),(list of <p_cid>s for active primary contexts),(list of supported <d_comp>s),(list of supported <h_comp>s),(list of supported <IM_CN_Signalling_Flag_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 Secondary PDP context identified by the (local) context identification parameter, <cid>. The number of PDP contexts that may be in a defined state at the same time is given by the range returned by the test command.
In EPS the command is used to define traffic flows.
In 5GS the command is used to define QoS flows of non-default QoS rule.
A special form of the set command, +CGDSCONT=<cid> causes the values for context number <cid> to become undefined.
The read command returns the current settings for each defined context.
The test command returns values supported as compound values.
Defined values
<cid>
integer type; which specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. The range of permitted values (minimum value = 1) is returned by the test form of the command.
<p_cid>
integer type; specifies a particular PDP context definition which has been specified by use of the +CGDCONT command. The parameter is local to the TE-MT interface. The list of permitted values is returned by the test form of the command.
<d_comp>
integer type; controls PDP data compression (applicable for SNDCP only) (refer TS 44.065).
0 (default)
off
1
on (manufacturer preferred compression)
2
V.42bis
3
V.44
<h_comp>
integer type; controls PDP header compression (refer TS 44.065 and TS 25.323).
0 (default)
off
1
on (manufacturer preferred compression)
2
RFC 1144 (applicable for SNDCP only)
3
4
RFC 3095 (applicable for PDCP only)
<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 (default)
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
Implementation
Optional.
Up

Up   Top   ToC