HSDPA Standard At Commands Page 55 of 60 Version 1.2
The execution command is used to modify the specified PDP context (s) with repect to QoS
profiles and TFTs. After the command has completed, the MT returns to V.25ter 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.
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.
Table 38. + CGCMOD parameter command syntax
Command Possible response(s)
+CGCMOD=[<cid>
[,<cid>[,…]]] OK
ERROR
+CGCMOD=? +CGCMOD: (list of <cid>s associated with active contexts)
Value <cid>: a numeric parameter which specifies a particular PDP context definition (see
the +CGDCONT and +CGDSCONT commands).
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. Otherwise, the MT issues the intermediate result code
CONNECT and enters V.25ter 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 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 -