10.1.12 Enter data state +CGDATA

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

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

Table 122: +CGDATA action command syntax

Command	Possible Response(s)
+CGDATA[=<L2P>[,<cid>[,<cid>[,…]]]]	CONNECT ERROR +CME ERROR: <err>
+CGDATA=?	+CGDATA: (list of supported <L2P>s)
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 +CGDATA=[<L2P>[,<cid>[,<cid>[,…]]]].

Description

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 clause 9.2 for possible <err> values. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state.

NOTE: If the initial PDP context is supported, the context with <cid>=0 is automatically defined at startup, see clause 10.1.0.

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 3GPP TS 27.060 [34] and in more detail in 3GPP TS 29.061 [39] 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 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.

Defined values

<L2P>: string type; indicates the layer 2 protocol to be used between the TE and MT

NULL none, for PDP type OSP:IHOSS (Obsolete)

PPP Point-to-point protocol for a PDP such as IP

PAD character stream for X.25 character (triple X PAD) mode (Obsolete)

X25 X.25 L2 (LAPB) for X.25 packet mode (Obsolete)

M-xxxx manufacturer-specific protocol (xxxx is an alphanumeric string)

If the value is omitted, the layer 2 protocol is unspecified. Other values are reserved and will result in an ERROR response.

<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands).

Implementation

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