Content for  TS 27.007  Word version:  18.5.0

The execution command is used to activate or deactivate the specified PDP context (s). After the command has completed, the MT remains in V.250 command state. If any PDP context is already in the requested state, the state for that context remains unchanged. If the requested state for any specified context cannot be achieved, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. If the MT is not PS attached when the activation form of the command is executed, the MT first performs a PS attach and then attempts to activate the specified contexts. If the attach fails then the MT responds with ERROR or, if extended error responses are enabled, with the appropriate failure-to-attach error message. Refer to clause 9.2 for possible <err> values. For EPS, if an attempt is made to disconnect the last PDN connection, then the MT responds with ERROR or, if extended error responses are enabled, a +CME ERROR. For EPS, the activation request for an EPS bearer resource will be answered by the network by either an EPS dedicated bearer activation or EPS bearer modification request. The request must be accepted by the MT before the PDP context can be set in to established state. For 5GS, the command is used to request or delete the specified QoS flow. The request for a specific QoS flow will be answered by the network by a PDU session establishment accept message or a PDU session modification command message. The PDU session establishment accept message or a PDU session modification command message must be accepted by the MT before the QoS flow can be set to active state. If no <cid>s are specified the activation form of the command activates all defined non-emergency contexts. If no <cid>s are specified the deactivation form of the command deactivates all active contexts. The read command returns the current activation states for all the defined PDP contexts. The test command is used for requesting information on the supported PDP context activation states.

<state> <cid>

Optional.

The execution command is used to modify the specified PDP context (s) with repect to QoS profiles, TFTs and MBS sessions. After the command has completed, the MT returns to V.250 online data state. If the requested modification for any specified context cannot be achieved, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer to clause 9.2 for possible <err> values. For EPS, the modification request for an EPS bearer resource will be answered by the network by an EPS bearer modification request. The request must be accepted by the MT before the PDP context is effectively changed. For 5GS, the command is used to modify the specified QoS flow. The modification request for a QoS flow resource will be answered by the network by a PDU session modification command. The command must be accepted by the MT before the QoS flow is effectively changed. If no <cid>s are specified the activation form of the command modifies all active contexts. The test command returns a list of <cid>s associated with active contexts.

<cid>

Optional.

The execution command causes the MT to perform whatever actions are necessary to establish communication between the TE and the network using one or more Packet Domain PDP types. This may include performing a PS attach and one or more PDP context activations. If the <L2P> parameter value is unacceptable to the MT, the MT shall return an ERROR or +CME ERROR response. Refer to clause 9.2 for possible <err> values. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state. Commands following +CGDATA command in the AT command line shall not be processed by the MT. The detailed behaviour after the online data state has been entered is dependent on the PDP type. It is described briefly in TS 27.060 and in more detail in TS 29.061 and the specifications for the relevant PDPs. PS attachment and PDP context activation procedures may take place prior to or during the PDP startup if they have not already been performed using the +CGATT and +CGACT commands. If context activation takes place during the PDP startup, one or more <cid>s may be specified in order to provide the information needed for the context activation request(s). During each PDP startup procedure the MT may have access to some or all of the following information:

• The MT may have a priori knowledge, for example, it may implement only one PDP type.
• The command may have provided an <L2P> parameter value.
• The TE may provide a PDP type and/or PDP address to the MT during in the PDP startup procedure.

If any of this information is in conflict, the command will fail. Any PDP type and/or PDP address present in the above information shall be compared with the PDP type and/or PDP address in any context definitions specified in the command in the order in which their <cid>s appear. For a context definition to match:

• The PDP type must match exactly.
• The PDP addresses are considered to match if they are identical or if either or both addresses are unspecified. For example, a PPP NCP request specifying PDP type = IP and no PDP address would cause the MT to search through the specified context definitions for one with PDP type = IP and any PDP address.

The context shall be activated using the matched value for PDP type and a static PDP address if available, together with the other information found in the PDP context definition. If a static PDP address is not available then a dynamic address is requested. If no <cid> is given or if there is no matching context definition, the MT shall attempt to activate the context with whatever information is available to the MT. The other context parameters shall be set to their default values. If the activation is successful, data transfer may proceed. After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the V.250 command state is re-entered and the MT returns the final result code OK. In the event of an erroneous termination or a failure to start up, the V.250 command state is re-entered and the MT returns the final result code NO CARRIER or, if enabled, +CME ERROR. Refer to clause 9.2 for possible <err> values. Attach, activate and other errors may be reported. The test command is used for requesting information on the supported layer 2 protocols. This command may be used in both normal and modem compatibility modes.

<L2P> <cid>

Optional if the D (dial) command can be used to specify Packet Domain operation.

The execution command returns a list of PDP addresses for the specified context identifiers. If no <cid> is specified, the addresses for all defined contexts are returned. The test command returns a list of defined <cid>s.

<cid> <PDP_addr_1> and <PDP_addr_2>

Optional.

The set command disables or enables an automatic positive or negative response (auto-answer) to the receipt of a NW-initiated Request PDP Context Activation message, NW-initiated Request EPS Bearer Activation/ Modification Request messages and a NW-initiated PDU Session Modification Command message. It also provides control over the use of the V.250 basic commands 'S0', 'A' and 'H' for handling network requests for PDP context activation. The setting does not affect the issuing of the unsolicited result code RING or +CRING. When the +CGAUTO=0 command is received for GERAN, UTRAN or E-UTRAN RATs, the MT shall not perform a PS detach if it is attached. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING, the TE may manually accept or reject the request by issuing the +CGANS command or may simply ignore the network request. When the +CGAUTO=1 command is received for GERAN, UTRAN or E-UTRAN RATs, the MT shall attempt to perform a PS attach if it is not already attached. Failure will result in ERROR or, if enabled, +CME ERROR being returned to the TE. Refer to clause 9.2 for possible <err> values. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING to the TE, this is followed by the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure as it would after having received a +CGANS=1 with no <L2P> or <cid> values specified. The read command returns the current value of <n>. The test command returns the values of <n> supported by the MT as a compound value.

<n>

Optional. If not implemented, the MT shall behave according to the case of <n>=3.

The execution command requests the MT to respond to a network request for Packet Domain PDP context activation which has been signalled to the TE by the RING, +CRING or +CGEV unsolicited result code. The <response> parameter allows the TE to accept or reject the request. If <response> is 0, the request is rejected and the MT returns OK to the TE. If <response> is 1, the following procedure is followed by the MT. Commands following the +CGANS command in the AT command line shall not be processed by the MT. If the <L2P> parameter value is unacceptable to the MT, the MT shall return an ERROR or +CME ERROR response. Refer to clause 9.2 for possible <err> values. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state. The detailed behaviour after the online data state has been entered is dependent on the PDP type. It is described briefly in TS 27.060 and in more detail in TS 29.061 and the specifications for the relevant PDPs. PDP context activation procedures shall take place prior to or during the PDP startup. One or more <cid>s may be specified in order to provide the values needed for the context activation request. During the PDP startup procedure the MT has the PDP type and the PDP address provided by the network in the Request PDP Context Activation message. The MT may also have some or all of the following information:

• The MT may have a priori knowledge, for example, it may implement only one PDP type.
• The command may have provided an <L2P> parameter value.
• The TE may provide one or both of PDP type and PDP address to the MT in the PDP startup.

If any of this information is in conflict, the command will fail. If one or more <cid> is given then an attempt shall be made to identify an appropriate context definition by matching the PDP type and PDP address in the network request with the PDP type and PDP address in each of the specified context definitions (in the order in which their <cid>s appear in the command) as follows:

• The PDP type must match exactly.
• The PDP addresses are considered to match if they are identical or if the address in the context definition is unspecified.

The context shall be activated using the values for PDP type and PDP address provided by the network, together with the other information found in the PDP context definition. An APN may or may not re required, depending on the application. If no <cid> is given or if there is no matching context definition, the MT will attempt to activate the context using the values for PDP type and PDP address provided by the network, together with any other relevant information known to the MT. The other context parameters will be set to their default values. If the activation is successful, data transfer may proceed. After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the V.250 command state is re-entered and the MT returns the final result code OK In the event of an erroneous termination or a failure to startup, the V.250 command state is re-entered and the MT returns the final result code NO CARRIER or, if enabled, +CME ERROR. Refer to clause 9.2 for possible <err> values. Attach, activate and other errors may be reported. It is also an error to issue the +CGANS command when there is no outstanding network request. The test command returns the values of <response> and <L2P> supported by the MT as compound values. This command may be used in both normal and modem compatibility modes.

<response> <L2P> <cid>

Optional.

The set command is used to set the MT to operate according to the specified mode of operation, see TS 23.060. If the requested mode of operation is not supported, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by the +CMEE command. Refer to clause 9.2 for possible <err> values. The read command returns the mode of operation set by the TE, independent of the current serving cell capability and independent of the current serving cell Access Technology. If no value has been set by the TE previously, the return value shall be the highest mode of operation that can be supported by the MT. The test command is used for requesting information on the supported MT modes of operation as a compound value.

<class>

Optional.

Set command enables or disables sending of unsolicited result codes, +CGEV: XXX from MT to TE in the case of certain events occurring in the Packet Domain MT or the network. <mode> controls the processing of unsolicited result codes specified within this command. <bfr> controls the effect on buffered codes when <mode> 1 or 2 is entered. If a setting is not supported by the MT, ERROR or +CME ERROR: is returned. Refer to clause 9.2 for possible <err> values. Read command returns the current mode and buffer settings. Test command returns the modes and buffer settings supported by the MT as compound values.

<mode> <bfr> Defined events +CGEV: ME PDN ACT <cid>[,<reason>[,<cid_other>[,<WLAN_Offload>[,<SSC>,<old-cid>,[<MA_3GPP>,<MA_N3GPP>]]]]] +CGEV: NW ACT <p_cid>, <cid>, <event_type>[,<WLAN_Offload>] +CGEV: ME ACT <p_cid>, <cid>, <event_type>[,<WLAN_Offload>] For PDP context deactivation, the following unsolicited result codes and the corresponding events are defined: +CGEV: NW DEACT <PDP_type>, <PDP_addr>, [<cid>] +CGEV: ME DEACT <PDP_type>, <PDP_addr>, [<cid>] +CGEV: NW PDN DEACT <cid>[,<WLAN_Offload>[,<SSC>]] +CGEV: ME PDN DEACT <cid> +CGEV: NW DEACT <p_cid>, <cid>, <event_type>[,<WLAN_Offload>] +CGEV: ME DEACT <p_cid>, <cid>, <event_type> For PDP context modification, the following unsolicited result codes and the corresponding events are defined: +CGEV: NW MODIFY <cid>, <change_reason>, <event_type>[,<WLAN_Offload>[,<PDU-lifetime>]] +CGEV: ME MODIFY <cid>, <change_reason>, <event_type>[,<WLAN_Offload>] The mobile termination has modified a context. The associated <cid> is provided to the TE in addition to the <change_reason> and <event_type>. The format of the parameter <cid> is found in command +CGDCONT or +CGDSCONT. The format of the parameters <change_reason>, <event_type> and <WLAN_Offload> are defined above. For other PDP context handling, the following unsolicited result codes and the corresponding events are defined: +CGEV: REJECT <PDP_type>, <PDP_addr> +CGEV: NW REACT <PDP_type>, <PDP_addr>, [<cid>]

Optional.