7 Network service related commands

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

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

7.0 General

This clause describes network related commands, which are not covered in call control clause of the present document. Commands include supplementary service handling, MSISDN query, MT and network facility locking, and network registration information query.

7.1 Subscriber number +CNUM

Table 34: +CNUM action command syntax

Command

Possible response(s)

+CNUM

+CNUM: [<alpha1>],<number1>,<type1>[,<speed>,<service>[,<itc>]]

[<CR><LF>+CNUM: [<alpha2>],<number2>,<type2>[,<speed>,<service>[,<itc>]]

[…]]

+CME ERROR: <err>

+CNUM=?

Description

Action command returns the MSISDNs related to the subscriber (this information can be stored in the SIM/UICC or in the MT). When storing information in the SIM/UICC, if the currently selected card slot contains a SIM card or a UICC with an active GSM application, the information is stored in the EF_MSISDN under DF_Telecom. If the currently selected card slot contains a UICC with an active USIM application, the information is stored in the EF_MSISDN under ADF_USIM). If subscriber has different MSISDN for different services, each MSISDN is returned on a separate line. Refer clause 9.2 for possible <err> values.

Defined values

<alphax>: optional alphanumeric string associated with <numberx>; used character set should be the one selected with command select TE character set +CSCS

<numberx>: string type phone number of format specified by <typex>

<typex>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7)

<speed>: integer type as defined in clause 6.7

<service>: integer type (service related to the phone number)

0 asynchronous modem

1 synchronous modem

2 PAD Access (asynchronous)

3 Packet Access (synchronous)

4 voice

5 fax

all other values below 128 are reserved by the present document

<itc>: integer type (information transfer capability)

0 3,1 kHz

1 UDI

Implementation

Optional.

7.2 Network registration +CREG

Table 35: +CREG parameter command syntax

Command	Possible response(s)
+CREG=[<n>]	+CME ERROR: <err>
+CREG?	+CREG: <n>,<stat>[,[<lac>],[<ci>],[<AcT>][,<cause_type>,<reject_cause>]]
+CREG=?	+CREG: (list of supported <n>s)

Description

Set command controls the presentation of an unsolicited result code +CREG: <stat> when <n>=1 and there is a change in the MT’s circuit mode network registration status in GERAN/UTRAN/E-UTRAN, or unsolicited result code +CREG: <stat>[,[<lac>],[<ci>],[<AcT>]] when <n>=2 and there is a change of the network cell in GERAN/UTRAN/E-UTRAN. The parameters <AcT>, <lac> and <ci> are sent only if available. The value <n>=3 further extends the unsolicited result code with [,<cause_type>,<reject_cause>], when available, when the value of <stat> changes.

NOTE 1: If the MT also supports one or more of the GPRS services, EPS services or 5G services, the +CGREG command and +CGREG: result codes, the +CEREG command and +CEREG: result codes and the +C5GREG command and +C5GREG: result codes apply to the registration status and location information for those services.

Read command returns the status of result code presentation and an integer <stat> which shows whether the network has currently indicated the registration of the MT. Location information elements <lac>, <ci> and <AcT>, if available, are returned only when <n>=2 and MT is registered in the network. The parameters [,<cause_type>,<reject_cause>], if available, are returned when <n>=3. Refer clause 9.2 for possible <err> values.

Test command returns values supported as a compound value.

Defined values

<n>: integer type

0 disable network registration unsolicited result code

1 enable network registration unsolicited result code +CREG: <stat>

2 enable network registration and location information unsolicited result code +CREG: <stat>[,[<lac>],[<ci>],[<AcT>]]

3 enable network registration, location information and cause value information unsolicited result code +CREG: <stat>[,[<lac>],[<ci>],[<AcT>][,<cause_type>,<reject_cause>]]

<stat>: integer type; circuit mode registration status.

0 not registered, MT is not currently searching a new operator to register to

1 registered, home network

2 not registered, but MT is currently searching a new operator to register to

3 registration denied

4 unknown (e.g. out of GERAN/UTRAN/E-UTRAN coverage)

5 registered, roaming

6 registered for "SMS only", home network (applicable only when <AcT> indicates E-UTRAN)

7 registered for "SMS only", roaming (applicable only when <AcT> indicates E-UTRAN)

8 attached for emergency bearer services only (see NOTE 2) (not applicable)

9 registered for "CSFB not preferred", home network (applicable only when <AcT> indicates E-UTRAN)

10 registered for "CSFB not preferred", roaming (applicable only when <AcT> indicates E-UTRAN)

11 attached for access to RLOS (see NOTE 2a) (applicable only when <AcT> indicates E-UTRAN)

NOTE 2: 3GPP TS 24.008 [8] and 3GPP TS 24.301 [83] specify the condition when the MT is considered as attached for emergency bearer services.

NOTE 2a: 3GPP TS 24.301 [83] specifies the condition when the MT is considered as attached for access to RLOS.

<lac>: string type; two byte location area code (when <AcT> indicates value 0 to 6), or tracking area code (when <AcT> indicates value 7). In hexadecimal format (e.g. "00C3" equals 195 in decimal).

<ci>: string type; four byte GERAN/UTRAN/E-UTRAN cell ID in hexadecimal format.

<AcT>: integer type; access technology of the serving cell.

0 GSM

1 GSM Compact

2 UTRAN

3 GSM w/EGPRS (see NOTE 3)

4 UTRAN w/HSDPA (see NOTE 4)

5 UTRAN w/HSUPA (see NOTE 4)

6 UTRAN w/HSDPA and HSUPA (see NOTE 4)

7 E-UTRAN

8 EC-GSM-IoT (A/Gb mode) (see NOTE 5)

9 E-UTRAN (NB-S1 mode) (see NOTE 6)

10 E-UTRA connected to a 5GCN (see NOTE 7) (not applicable)

11 NR connected to a 5GCN (see NOTE 7) (not applicable)

12 NG-RAN (not applicable)

13 E-UTRA-NR dual connectivity (see NOTE 8)

NOTE 3: 3GPP TS 44.018 [156] specifies the System Information messages which give the information about whether the serving cell supports EGPRS.

NOTE 4: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether the serving cell supports HSDPA or HSUPA.

NOTE 5: 3GPP TS 44.018 [156] specifies the EC-SCH INFORMATION message which, if present, indicates that the serving cell supports EC-GSM-IoT.

NOTE 6: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving cell supports NB-IoT, which corresponds to E-UTRAN (NB-S1 mode).

NOTE 7: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is connected to a 5GCN.

NOTE 8: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is supporting dual connectivity of E-UTRA with NR and is connected to an EPS core.

<cause_type>: integer type; indicates the type of <reject_cause>.

0 Indicates that <reject_cause> contains an MM cause value, see 3GPP TS 24.008 [8] Annex G.

1 Indicates that <reject_cause> contains a manufacturer specific cause.

<reject_cause>: integer type; contains the cause of the failed registration. The value is of type as defined by <cause_type>.

Implementation

Optional.

This command is not applicable to UEs in NG-RAN.

7.3 PLMN selection +COPS

Table 36: +COPS parameter command syntax

Command	Possible response(s)
+COPS=[<mode>[,<format> [,<oper>[,<AcT>]]]]	+CME ERROR: <err>
+COPS?	+COPS: <mode>[,<format>,<oper>[,<AcT>]] +CME ERROR: <err>
+COPS=?	+COPS: [list of supported (<stat>,long alphanumeric <oper>,short alphanumeric <oper>,numeric <oper>[,<AcT>])s][,,(list of supported <mode>s),(list of supported <format>s)] +CME ERROR: <err>

Description

Set command forces an attempt to select and register to the GSM/UMTS/EPS/5GS network operator using the SIM/USIM card installed in the currently selected card slot. <mode> is used to select whether the selection is done automatically by the MT or is forced by this command to operator <oper> (it shall be given in format <format>) to a certain access technology, indicated in <AcT>. <regtype> indicates if the registration procedure shall be performed for disaster roaming service (see 3GPP TS 24.501 [161]). If <regtype> is not included then the UE performs a normal registration i.e. a registration not for disaster roaming service (see 3GPP TS 24.501 [161]). If the selected operator is not available, no other operator shall be selected (except <mode>=4). If the selected access technology is not available, then the same operator shall be selected in other access technology. The selected operator name format shall apply to further read commands (+COPS?) also. <mode>=2 forces an attempt to deregister from the network. The selected mode affects to all further network registration (e.g. after <mode>=2, MT shall be unregistered until <mode>=0 or 1 is selected). Refer clause 9.2 for possible <err> values. This command should be abortable when registration/deregistration attempt is made.

Read command returns the current mode, the currently selected operator and the current Access Technology. If no operator is selected, <format>, <oper> and <AcT> are omitted.

Test command returns a set of five parameters, each representing an operator present in the network. A set consists of an integer indicating the availability of the operator <stat>, long and short alphanumeric format of the name of the operator, numeric format representation of the operator and access technology. Any of the formats may be unavailable and should then be an empty field. The list of operators shall be in order: home network, networks referenced in SIM or active application in the UICC (GSM or USIM) in the following order: HPLMN selector, User controlled PLMN selector, Operator controlled PLMN selector and PLMN selector (in the SIM or GSM application), and other networks.

It is recommended (although optional) that after the operator list TA returns lists of supported <mode>s and <format>s. These lists shall be delimited from the operator list by two commas.

The access technology selected parameters, <AcT>, should only be used in terminals capable to register to more than one access technology. Selection of <AcT> does not limit the capability to cell reselections, even though an attempt is made to select an access technology, the phone may still re-select a cell in another access technology.

Defined values

<mode>: integer type

0 automatic (<oper> field is ignored)

1 manual (<oper> field shall be present, and <AcT> optionally)

2 deregister from network

3 set only <format> (for read command +COPS?), do not attempt registration/deregistration (<oper> and <AcT> fields are ignored); this value is not applicable in read command response

4 manual/automatic (<oper> field shall be present); if manual selection fails, automatic mode (<mode>=0) is entered

<format>: integer type

0 long format alphanumeric <oper>

1 short format alphanumeric <oper>

2 numeric <oper>

<regtype>: integer type

0 register not for disaster roaming service.

1 register for disaster roaming service.

<oper>: string type; <format> indicates if the format is alphanumeric or numeric; long alphanumeric format can be upto 16 characters long and short format up to 8 characters (refer GSM MoU SE.13 [9]); numeric format is the Location Area Identification number (refer 3GPP TS 24.008 [8] clause 10.5.1.3) which consists of a three BCD digit country code coded as in ITU‑T Recommendation E.212 [10] Annex A, plus a two BCD digit network code, which is administration specific; returned <oper> shall not be in BCD format, but in IRA characters converted from BCD; hence the number has structure: (country code digit 3)(country code digit 2)(country code digit 1)(network code digit 3)(network code digit 2)(network code digit 1)

<stat>: integer type

0 unknown

1 available

2 current

3 forbidden

4 forbidden and supports disaster roaming

<AcT>: integer type; access technology selected

0 GSM

1 GSM Compact

2 UTRAN

3 GSM w/EGPRS (see NOTE 1)

4 UTRAN w/HSDPA (see NOTE 2)

5 UTRAN w/HSUPA (see NOTE 2)

6 UTRAN w/HSDPA and HSUPA (see NOTE 2)

7 E-UTRAN

8 EC-GSM-IoT (A/Gb mode) (see NOTE 3)

9 E-UTRAN (NB-S1 mode) (see NOTE 4)

10 E-UTRA connected to a 5GCN (see NOTE 5)

11 NR connected to a 5GCN (see NOTE 5)

12 NG-RAN

13 E-UTRA-NR dual connectivity (see NOTE 6)

NOTE 1: 3GPP TS 44.018 [156] specifies the System Information messages which give the information about whether the serving cell supports EGPRS.

NOTE 2: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether the serving cell supports HSDPA or HSUPA.

NOTE 3: 3GPP TS 44.018 [156] specifies the EC-SCH INFORMATION message which, if present, indicates that the serving cell supports EC-GSM-IoT.

NOTE 4: 3GPP TS 36.331 [86] specifies the System Information blocks which give the information about whether the serving cell supports NB-IoT, which corresponds to E-UTRAN (NB-S1 mode).

NOTE 5: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is connected to a 5G CN. This value is not applicable in set command.

NOTE 6: 3GPP TS 38.331 [160] specifies the information which, if present, indicates that the serving cell is supporting dual connectivity of E-UTRA with NR and is connected to an EPS core.

Implementation

Optional.

7.4 Facility lock +CLCK

Table 37: +CLCK action command syntax

Command

Possible response(s)

+CLCK=<fac>,<mode>[,<passwd>[,<class>]]

+CME ERROR: <err>

when <mode>=2 and command successful:

+CLCK: <status>[,<class1>

[<CR><LF>+CLCK: <status>,<class2>

[…]]

+CLCK=?

+CLCK: (list of supported <fac>s)

+CME ERROR: <err>

Description

Execute command is used to lock, unlock or interrogate a MT or a network facility <fac>. Password is normally needed to do such actions. When querying the status of a network service (<mode>=2) the response line for ‘not active’ case (<status>=0) should be returned only if service is not active for any <class>. Refer clause 9.2 for possible <err> values. This command should be abortable when network facilities are set or interrogated.

Call barring facilities are based on supplementary services (refer 3GPP TS 22.088 [6]). The interaction of these with other commands based on other supplementary services is described in the specification of the relevant supplementary service.

Test command returns facility values supported as a compound value.

Defined values

<fac> values reserved by the present document:

"CS" CNTRL (lock CoNTRoL surface (e.g. phone keyboard))

"PS" PH‑SIM (lock PHone to SIM/UICC card installed in the currently selected card slot) (MT asks password when other than current SIM/UICC card inserted; MT may remember certain amount of previously used cards thus not requiring password when they are inserted)

"PF" lock Phone to the very First inserted SIM/UICC card (also referred in the present document as PH-FSIM) (MT asks password when other than the first SIM/UICC card is inserted)

"SC" SIM (lock SIM/UICC card installed in the currently selected card slot) (SIM/UICC asks password in MT power‑up and when this lock command issued)

"AO" BAOC (Barr All Outgoing Calls) (refer 3GPP TS 22.088 [6] clause 1)

"OI" BOIC (Barr Outgoing International Calls) (refer 3GPP TS 22.088 [6] clause 1)

"OX" BOIC‑exHC (Barr Outgoing International Calls except to Home Country) (refer 3GPP TS 22.088 [6] clause 1)

"AI" BAIC (Barr All Incoming Calls) (refer 3GPP TS 22.088 [6] clause 2)

"IR" BIC‑Roam (Barr Incoming Calls when Roaming outside the home country) (refer 3GPP TS 22.088 [6] clause 2)

"NT" barr incoming calls from numbers Not stored to TA memory

"NM" barr incoming calls from numbers Not stored to MT memory

"NS" barr incoming calls from numbers Not stored to SIM/UICC memory

"NA" barr incoming calls from numbers Not stored in Any memory

"AB" All Barring services (refer 3GPP TS 22.030 [19]) (applicable only for <mode>=0)

"AG" All outGoing barring services (refer 3GPP TS 22.030 [19]) (applicable only for <mode>=0)

"AC" All inComing barring services (refer 3GPP TS 22.030 [19]) (applicable only for <mode>=0)

"FD" SIM card or active application in the UICC (GSM or USIM) fixed dialling memory feature (if PIN2 authentication has not been done during the current session, PIN2 is required as <passwd>)

"PN" Network Personalization (refer 3GPP TS 22.022 [33])

"PU" network sUbset Personalization (refer 3GPP TS 22.022 [33])

"PP" service Provider Personalization (refer 3GPP TS 22.022 [33])

"PC" Corporate Personalization (refer 3GPP TS 22.022 [33])

<mode>: integer type

0 unlock

1 lock

2 query status

<status>: integer type

0 not active

1 active

<passwd>: string type; shall be the same as password specified for the facility from the MT user interface or with command Change Password +CPWD

<classx> is a sum of integers each representing a class of information (default 7 – voice, data and fax):

1 voice (telephony)

2 data (refers to all bearer services; with <mode>=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128)

4 fax (facsimile services)

8 short message service

16 data circuit sync

32 data circuit async

64 dedicated packet access

128 dedicated PAD access

Implementation

The call barring supplementary service control is mandatory for MT supporting AT commands only and not supporting the control through dial command D.

7.5 Change password +CPWD

Table 38: +CPWD action command syntax

Command

Possible response(s)

+CPWD=<fac>,<oldpwd>,<newpwd>

+CME ERROR: <err>

+CPWD=?

+CPWD: list of supported (<fac>,<pwdlength>)s

+CME ERROR: <err>

Description

Action command sets a new password for the facility lock function defined by command Facility Lock +CLCK. Refer clause 9.2 for possible <err> values.

Test command returns a list of pairs which present the available facilities and the maximum length of their password.

Defined values

<fac>:

"P2" SIM PIN2

refer Facility Lock +CLCK for other values

<oldpwd>, <newpwd>: string type; <oldpwd> shall be the same as password specified for the facility from the MT user interface or with command Change Password +CPWD and <newpwd> is the new password; maximum length of password can be determined with <pwdlength>

<pwdlength>: integer type maximum length of the password for the facility

Implementation

Optional.

7.6 Calling line identification presentation +CLIP

Table 39: +CLIP parameter command syntax

Command	Possible response(s)
+CLIP=[<n>]
+CLIP?	+CLIP: <n>,<m>
+CLIP=?	+CLIP: (list of supported <n>s)

Description

This command refers to the supplementary service CLIP (Calling Line Identification Presentation) according to 3GPP TS 22.081 [3] and OIP (Originating Identification Presentation) according to 3GPP TS 24.607 [119] that enables a called subscriber to get the calling line identity (CLI) of the calling party when receiving a mobile terminated call. Set command enables or disables the presentation of the CLI at the TE. It has no effect on the execution of the supplementary service CLIP / OIP in the network.

When <n>=1, the presentation of the calling line identity at the TE is enabled and when the calling subscriber allows, the unsolicited result code +CLIP: <number>,<type>[,<subaddr>,<satype>[,[<alpha>][,<CLI_validity>]]] is returned after every RING (or +CRING: <type>; refer clause "Cellular result codes +CRC") result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. The unsolicited result code +CLIP does not support numbers of the SIP URI format.

When <n>=0, the presentation of the calling line identity at the TE with unsolicited result code +CLIP is disabled.

The calling line identity can also be reported in unsolicited result codes +CMCCSS<x> / +CMCCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCCSS<x> / +CMCCSSEND support numbers of the SIP URI format. Read command gives the status of <n>, and also triggers an interrogation of the provision status of the CLIP supplementary service according to 3GPP TS 22.081 [3] and OIP supplementary service according to 3GPP TS 24.607 [119] (given in <m>).

Read command returns the current settings.

Test command returns values supported as a compound value.

Defined values

<n>: integer type (parameter sets/shows the result code presentation status to the TE).

0 disable

1 enable

<m>: integer type (parameter shows the subscriber CLIP / OIP service status in the network).

0 CLIP / OIP not provisioned

1 CLIP / OIP provisioned

2 unknown (e.g. no network, etc.)

<number>: string type phone number of format specified by <type>.

<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7).

<subaddr>: string type subaddress of format specified by <satype>

<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8).

<alpha>: optional string type alphanumeric representation of <number> corresponding to the entry found in phonebook; used character set should be the one selected with command select TE character set +CSCS.

<CLI_validity>: integer type. This parameter can provide details why <number> does not contain a calling party BCD number (refer 3GPP TS 24.008 [8] clause 10.5.4.30).

0 CLI valid

1 CLI has been withheld by the originator (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Reject by user")

2 CLI is not available due to interworking problems or limitations of originating network (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Interaction with other service")

3 CLI is not available due to calling party being of type payphone (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone")

4 CLI is not available due to other reasons (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Unavailable").

When CLI is not available (<CLI_validity>=2, <CLI_validity>=3 or <CLI_validity>=4), <number> shall be an empty string ("") and <type> value will not be significant. Nevertheless, TA may return the recommended value 128 for <type> (TON/NPI unknown in accordance with 3GPP TS 24.008 [8] clause 10.5.4.7).

When CLI has been withheld by the originator, (<CLI_validity>=1) and the CLIP is provisioned with the "override category" option (refer 3GPP TS 22.081 [3] and 3GPP TS 23.081 [40]), <number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available.

Implementation

Optional.

7.7 Calling line identification restriction +CLIR

Table 40: +CLIR parameter command syntax

Command	Possible response(s)
+CLIR=[<n>]
+CLIR?	+CLIR: <n>,<m>
+CLIR=?	+CLIR: (list of supported <n>s)

Description

This command refers to the supplementary service CLIR (Calling Line Identification Restriction) according to 3GPP TS 22.081 [3] and OIR (Originating Identification Restriction) according to 3GPP TS 24.607 [119] that allows a calling subscriber to enable or disable the presentation of the calling line identity (CLI) to the called party when originating a call.

Set command overrides the CLIR / OIR subscription (default is restricted or allowed) when temporary mode is provisioned as a default adjustment for all following outgoing calls. This adjustment can be revoked by using the opposite command. If this command is used by a subscriber without provision of CLIR / OIR in permanent mode the network will act according to 3GPP TS 22.081 [3] and 3GPP TS 24.607 [119]).

Read command gives the default adjustment for all outgoing calls (given in <n>), and also triggers an interrogation of the provision status of the CLIR / OIR service (given in <m>).

Test command returns values supported as a compound value.

NOTE: On a per call basis CLIR / OIR functionality is explained in clauses "ITU‑T Recommendation V.250 [14] dial command D" and "Dial URI +CDU".

Defined values

<n>: integer type (parameter sets the adjustment for outgoing calls).

0 presentation indicator is used according to the subscription of the CLIR / OIR service.

1 CLIR / OIR invocation

2 CLIR / OIR suppression

<m>: integer type (parameter shows the subscriber CLIR / OIR service status in the network).

0 CLIR / OIR not provisioned

1 CLIR / OIR provisioned in permanent mode

2 unknown (e.g. no network, etc.)

3 CLIR / OIR temporary mode presentation restricted

4 CLIR / OIR temporary mode presentation allowed

Implementation

Optional.

7.8 Connected line identification presentation +COLP

Table 41: +COLP parameter command syntax

Command	Possible response(s)
+COLP=[<n>]
+COLP?	+COLP: <n>,<m>
+COLP=?	+COLP: (list of supported <n>s)

Description

This command refers to the supplementary service COLP (Connected Line Identification Presentation) according to 3GPP TS 22.081 [3] and TIP (Terminating Identification Presentation) according to 3GPP TS 24.608 [120] that enables a calling subscriber to get the connected line identity (COL) of the called party after setting up a mobile originated call. The command enables or disables the presentation of the COL at the TE. It has no effect on the execution of the supplementary service COLR / TIR in the network.

When <n>=1, the presentation of the connected line identity at the TE enabled and when the called subscriber allows the intermediate result code, +COLP: <number>,<type>[,<subaddr>,<satype> [,<alpha>]] is returned from TA to TE before any +CR or ITU‑T Recommendation V.250 [14] responses. It is manufacturer specific if this response is used when normal voice call is established. The intermediate result code +COLP does not support numbers of the SIP URI format.

NOTE: If the connected line identity is available in the TE after reception of the final response to the call setup, +COLP is not returned as an intermediate result code but as an unsolicited result code.

When <n>=0, the presentation of the connected line identity at the TE is disabled.

The connected line identity can also be reported in unsolicited result codes +CMCCSS<x> / +CMCCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCCSS<x> / +CMCCSSEND support numbers of the SIP URI format.

Read command gives the status of <n>, and also triggers an interrogation of the provision status of the COLP supplementary service according 3GPP TS 22.081 [3] and TIP supplementary service according to 3GPP TS 24.608 [120] (given in <m>).

Test command returns values supported as a compound value.

Defined values

<n>: integer type (parameter sets/shows the result code presentation status to the TE).

0 disable

1 enable

<m>: integer type (parameter shows the subscriber COLP service status in the network).

0 COLP / TIP not provisioned

1 COLP / TIP provisioned

2 unknown (e.g. no network, etc.)

<number>, <type>, <subaddr>, <satype>, <alpha>: refer +CLIP.

Implementation

Optional.

7.9 Called line identification presentation +CDIP

Table 42: +CDIP parameter command syntax

Command	Possible response(s)
+CDIP=[<n>]
+CDIP?	+CDIP: <n>,<m>
+CDIP=?	+CDIP: (list of supported <n>s)

Description

This command related to a network service that provides "multiple called numbers (called line identifications) service" to an MT. This command enables a called subscriber to get the called line identification of the called party when receiving a mobile terminated call. Set command enables or disables the presentation of the called line identifications at the TE.

When <n>=1, the presentation of the called line identification at the TE is enabled, the unsolicited result code +CDIP: <number>,<type>[,<subaddr>,<satype>] is returned after every RING (or +CRING: <type>; refer clause "Cellular result codes +CRC") result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. The unsolicited result code +CDIP does not support numbers of the SIP URI format.

When <n>=0, the presentation of the called line identification at the TE is disabled.

The called line identification can also be reported in unsolicited result codes +CMCCSS<x> / +CMCCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCCSS<x> / +CMCCSSEND support numbers of the SIP URI format.

Read command gives the status of <n>, and also triggers an interrogation of the provision status of the "multiple called numbers" service.

Test command returns values supported as a compound value.

Defined values

<n>: integer type (parameter sets/shows the result code presentation status to the TE)

0 disable

1 enable

<m>: integer type (parameter shows the subscriber "multiple called numbers" service status in the network)

0 "multiple called numbers service" is not provisioned

1 "multiple called numbers service" is provisioned

2 unknown (e.g. no network, etc.)

<number>: string type phone number of format specified by <type>

<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7)

<subaddr>: string type subaddress of format specified by <satype>

<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8)

Implementation

Optional.

7.10 Closed user group +CCUG

Table 43: +CCUG parameter command syntax

Command	Possible response(s)
+CCUG=[<n>[,<index>[,<info>]]]
+CCUG?	+CCUG: <n>,<index>,<info>
+CCUG=?

Description

This command allows control of the Closed User Group supplementary service (refer 3GPP TS 22.085 [21]). Set command enables the served subscriber to select a CUG index, to suppress the Outgoing Access (OA), and to suppress the preferential CUG.

Set command with <n>=1 enables to control the CUG information on the air interface as a default adjustment for all following outgoing calls. The interaction of this command with other commands based on other supplementary services is described in the specification of the relevant supplementary service.

NOTE: On a per call basis CUG functionality is explained in clause "ITU‑T Recommendation V.250 [14] dial command D".

Read command returns the current settings.

Defined values

<n>: integer type

0 disable CUG temporary mode

1 enable CUG temporary mode

<index>: integer type

0…9 CUG index

10 no index (preferred CUG taken from subscriber data)

<info>: integer type

0 no information

1 suppress OA

2 suppress preferential CUG

3 suppress OA and preferential CUG

Implementation

Optional. This command is superfluous when the command +CECUG is supported.

7.11 Call forwarding number and conditions +CCFC

Table 44: +CCFC action command syntax

Command

Possible response(s)

+CCFC=<reason>,<mode>[,<number>[,<type>[,<class>

[,<subaddr>[,<satype>[,<time>]]]]]]

+CME ERROR: <err>

when <mode>=2 and command successful:

+CCFC: <status>,<class1>[,<number>,<type>[,<subaddr>,<satype>[,<time>]]]

[<CR><LF>+CCFC: <status>,<class2>[,<number>,<type>[,<subaddr>,<satype>[,<time>]]]

[…]]

+CCFC=?

+CCFC: (list of supported <reason>s)

Description

This command allows control of the call forwarding supplementary service according to 3GPP TS 22.082 [4]. Registration, erasure, activation, deactivation, and status query are supported. When querying the status of a network service (<mode>=2) the response line for ‘not active’ case (<status>=0) should be returned only if service is not active for any <class>. Refer clause 9.2 for possible <err> values.

Test command returns reason values supported as a compound value.

NOTE: This command cannot be used with URIs. For communication forwarding control with URI support see AT command call forwarding number and conditions with URI support +CCFCU.

Defined values

<reason>: integer type

0 unconditional

1 mobile busy

2 no reply

3 not reachable

4 all call forwarding (refer 3GPP TS 22.030 [19])

5 all conditional call forwarding (refer 3GPP TS 22.030 [19])

<mode>: integer type

0 disable

1 enable

2 query status

3 registration

4 erasure

<number>: string type phone number of forwarding address in format specified by <type>

<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7); default 145 when dialling string includes international access code character "+", otherwise 129

<subaddr>: string type subaddress of format specified by <satype>

<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8); default 128

<classx> is a sum of integers each representing a class of information (default 7 – voice, data and fax):

1 voice (telephony)

2 data (refers to all bearer services; with <mode>=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128)

4 fax (facsimile services)

8 short message service

16 data circuit sync

32 data circuit async

64 dedicated packet access

128 dedicated PAD access

<time>: integer type

1…30 when "no reply", "all call forwarding" or "all conditional call fowarding" is enabled or queried, this gives the time in seconds to wait before call is forwarded, default value 20

<status>: integer type

0 not active

1 active

Implementation

Mandatory for MT supporting AT commands only and not supporting the control through dial command D.

7.12 Call waiting +CCWA

Table 45: +CCWA parameter command syntax

Command	Possible response(s)
+CCWA=[<n>[,<mode>[,<class>]]]	+CME ERROR: <err> when <mode>=2 and command successful +CCWA: <status>,<class1> [<CR><LF>+CCWA: <status>,<class2> […]]
+CCWA?	+CCWA: <n>
+CCWA=?	+CCWA: (list of supported <n>s)

Description

This command allows control of the supplementary service Call Waiting according to 3GPP TS 22.083 [5] and Communication Waiting according to 3GPP TS 24.607 [137]. Activation, deactivation and status query are supported. When querying the status of a network service (<mode>=2) the response line for ‘not active’ case (<status>=0) should be returned only if service is not active for any <class>. Refer clause 9.2 for possible <err> values.

Parameter <n> is used to disable/enable the presentation of an unsolicited result code +CCWA: <number>,<type>,<class>,[<alpha>][,<CLI_validity>[,<subaddr>,<satype>[,<priority>]]] to the TE when call waiting service is enabled. The unsolicited result code +CCWA does not support numbers of the SIP URI format.

The call waiting information can also be reported in unsolicited result codes +CMCCSS<x> / +CMCCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCCSS<x> / +CMCCSSEND support numbers of the SIP URI format.

Command should be abortable when network is interrogated.

Read command returns the current value of <n>.

Test command returns values supported as a compound value.

Defined values

<n>: integer type (sets/shows the result code presentation status to the TE).

0 disable

1 enable

<mode>: integer type (when <mode> parameter is not given, network is not interrogated).

0 disable

1 enable

2 query status

<classx>: is a sum of integers each representing a class of information (default 7 – voice, data and fax).

1 voice (telephony)

2 data (refers to all bearer services; with <mode>=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128)

4 fax (facsimile services)

8 short message service

16 data circuit sync

32 data circuit async

64 dedicated packet access

128 dedicated PAD access

<status>: integer type

0 not active

1 active

<number>: string type phone number of calling address in format specified by <type>.

<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7).

<CLI_validity>: integer type. This parameter can provide details why <number> does not contain a calling party BCD number (refer 3GPP TS 24.008 [8] clause 10.5.4.30).

0 CLI valid

1 CLI has been withheld by the originator (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Reject by user")

2 CLI is not available due to interworking problems or limitations of originating network (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Interaction with other service")

3 CLI is not available due to calling party being of type payphone (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone")

4 CLI is not available due to other reasons (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Unavailable")

When CLI is not available (<CLI_validity>=2, <CLI_validity>=3 or <CLI_validity>=4), <number> shall be an empty string ("") and <type> value will not be significant. Nevertheless, TA may return the recommended value 128 for <type> ((TON/NPI unknown in accordance with 3GPP TS 24.008 [8] clause 10.5.4.7).

<subaddr>: string type subaddress of format specified by <satype>.

<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8).

<priority>: optional digit type parameter indicating that the eMLPP priority level of the incoming call. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54].

Implementation

Optional.

7.13 Call related supplementary services +CHLD

Table 46: +CHLD action command syntax

Command	Possible response(s)
+CHLD=<n>	+CME ERROR: <err>
+CHLD=?	+CHLD: (list of supported <n>s)

Description

This command allows the control of the following call related services:

– a call can be temporarily disconnected from the MT but the connection is retained by the network;

– multiparty conversation (conference calls);

– the served subscriber who has two calls (one held and the other either active or alerting) can connect the other parties and release the served subscriber’s own connection.

Calls can be put on hold, recovered, released, added to conversation, and transferred similarly as defined in 3GPP TS 22.030 [19]. Refer clause 9.2 for possible <err> values.

This is based on the supplementary services HOLD (Call Hold; refer 3GPP TS 22.083 [5] clause 2 and 3GPP TS 24.610 [135]), MPTY / CONF (MultiParty; refer 3GPP TS 22.084 [22] and Conference; refer 3GPP TS 24.605 [133]) and ECT (Explicit Call Transfer; refer 3GPP TS 22.091 [30] and 3GPP TS 24.629 [139]).

NOTE 1: In the CS-domain, Call Hold, MultiParty and Explicit Call Transfer are only applicable to teleservice 11.

Test command returns a list of operations which are supported. The call number required by some operations shall be denoted by "x" (e.g. +CHLD: (0,1,1x,2,2x,3)).

Defined values

<n>: integer type; equals to numbers entered before SEND button in 3GPP TS 22.030 [19] clause 6.5.5.1.

NOTE 2: The "directory number" case shall be handled with dial command D, and the END case with hangup command H (or +CHUP). The 4*"directory number" case is handled with +CTFR command.

Implementation

Optional.

7.14 Call deflection +CTFR

Table 47: +CTFR action command syntax

Command	Possible response(s)
+CTFR=<number>[,<type>[,<subaddr>[,<satype>]]]	+CME ERROR: <err>
+CTFR=?

Description

This refers to a service that causes an incoming alerting call to be forwarded to a specified number. Action command does this. Refer clause 9.2 for possible <err> values.

This is based on the supplementary service CD (Call Deflection; refer 3GPP TS 22.072 [31]). The interaction of this command with other commands based on other supplementary services is described in the specification of the relevant supplementary service.

NOTE 1: Call Deflection is only applicable to teleservice 11.

NOTE 2: This command cannot be used with URIs. For communication forwarding control with URI support see AT command call forwarding number and conditions with URI support +CCFCU.

Defined values

<number>: string type phone number of format specified by <type>

<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7); default 145 when dialling string includes international access code character "+", otherwise 129

<subaddr>: string type subaddress of format specified by <satype>

<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8); default 128

Implementation

Optional.

7.15 Unstructured supplementary service data +CUSD

Table 48: +CUSD parameter command syntax

Command	Possible response(s)
+CUSD=[<n>[,<str>[,<dcs>]]]	+CME ERROR: <err>
+CUSD?	+CUSD: <n>
+CUSD=?	+CUSD: (list of supported <n>s)

Description

This command allows control of the Unstructured Supplementary Service Data (USSD) according to 3GPP TS 22.090 [23], 3GPP TS 24.090 [148] and 3GPP TS 24.390 [131]. Both network and mobile initiated operations are supported. Parameter <n> is used to disable/enable the presentation of an unsolicited result code. The value <n>=2 is used to cancel an ongoing USSD session. For an USSD response from the network, or a network initiated operation, the format is: +CUSD: <m>[,<str>,<dcs>].

NOTE 1: If the MT supports USSD according to 3GPP TS 24.090 [148] and USSD according to 3GPP TS 24.390 [131] then the MT decides which to invoke. The decision is out of scope of this specification.

When <str> is given, a mobile initiated USSD‑string or a response USSD‑string to a network initiated operation is sent to the network. The response USSD‑string from the network is returned in a subsequent unsolicited +CUSD result code. Refer clause 9.2 for possible <err> values.

NOTE 2: In case of successful mobile initiated operation, TA implemented according to a version prior to 6 of this standard, waits the USSD response from the network and sends it to the TE before the final result code. This will block the AT command interface for the period of the operation. Such TA does not support <n> value 2.

The interaction of this command with other commands based on other supplementary services is described in the specification of the relevant supplementary service.

Read command returns the current value of <n>.

Test command returns values supported as a compound value.

Defined values

<n>: integer type (sets/shows the result code presentation status to the TE).

0 disable the result code presentation to the TE

1 enable the result code presentation to the TE

2 cancel session (not applicable to read command response)

<str>: string type USSD‑string (when <str> parameter is not given, network is not interrogated):

‑ if <dcs> indicates that 3GPP TS 23.038 [25] 7 bit default alphabet is used:

‑ if TE character set other than "HEX" (refer command select TE character set +CSCS): MT/TA converts GSM alphabet into current TE character set according to rules of 3GPP TS 27.005 [24] Annex A

‑ if TE character set is "HEX": MT/TA converts each 7‑bit character of GSM alphabet into two IRA character long hexadecimal number (e.g. character Π (GSM 23) is presented as 17 (IRA 49 and 55))

‑ if <dcs> indicates that 8‑bit data coding scheme is used: MT/TA converts each 8‑bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65))

– if <dcs> indicates that 16-bit data coding scheme (UCS2) is used: MT/TA splits the 16 bits into two 8-bit octets. Each of those octets are converted as per the 8-bit data coding scheme, with the most significant octet first (e.g. decimal value 4906 is presented to TE as four characters 132A (IRA 49, 51, 50 and 65))

<dcs>: integer type (shows Cell Broadcast Data Coding Scheme, see 3GPP TS 23.038 [25]). Default value is 0.

<m>: integer type (shows the USSD response from the network or the network initiated operation).

0 no further user action required (network initiated USSD‑Notify, or no further information needed after mobile initiated operation)

1 further user action required (network initiated USSD‑Request, or further information needed after mobile initiated operation)

2 USSD terminated by network

3 other local client has responded

4 operation not supported

5 network time out

Implementation

Optional.

7.16 Advice of charge +CAOC

Table 49: +CAOC parameter command syntax

Command	Possible response(s)
+CAOC[=<mode>]	[+CAOC: <ccm>] +CME ERROR: <err>
+CAOC?	+CAOC: <mode>
+CAOC=?	+CAOC: (list of supported <mode>s)

Description

This refers to Advice of Charge supplementary service (3GPP TS 22.024 [26] and 3GPP TS 22.086 [27]) that enables subscriber to get information about the cost of calls. With <mode>=0, the execute command returns the current call meter value from the MT.

The command also includes the possibility to enable/disable reporting of the CCM information with unsolicited result code +CCCM: <ccm>. When enabled, this unsolicited result code is sent when the CCM value changes, but not more frequently than at every 10 seconds.

Refer clause 9.2 for possible <err> values.

NOTE: Advice of Charge values stored in the SIM card or in the active application in the UICC (GSM or USIM) (ACM, ACMmax, PUCT) can be accessed with generic or restricted SIM access command (+CSIM or +CRSM)). Those values can be more readily accessed with commands +CACM, +CAMM and +CPUC.

Read command indicates whether the unsolicited reporting is activated or not.

Test command returns the supported mode values as a compound value.

Defined values

<mode>: integer type

0 query CCM value

1 deactivate the unsolicited reporting of CCM value

2 activate the unsolicited reporting of CCM value

<ccm>: string type; three bytes of the current call meter value in hexadecimal format (e.g. "00001E" indicates decimal value 30); value is in home units and bytes are similarly coded as ACMmax value in the SIM card or in the active application in the UICC (GSM or USIM)

Implementation

Optional.

7.17 Supplementary service notifications +CSSN

Table 50: +CSSN parameter command syntax

Command	Possible response(s)
+CSSN=[<n>[,<m>]]
+CSSN?	+CSSN: <n>,<m>
+CSSN=?	+CSSN: (list of supported <n>s),(list of supported <m>s)

Description

This command refers to supplementary service related network initiated notifications. The set command enables/disables the presentation of notification result codes from TA to TE.

When <n>=1 and a supplementary service notification is received after a mobile originated call setup, intermediate result code +CSSI: <code1>[,[<index>][,<SS_code>]] is sent to TE before any other MO call setup result codes presented in the present document or in ITU‑T Recommendation V.250 [14]. When several different <code1>s are received from the network, each of them shall have its own +CSSI result code.

NOTE: If the supplemenary service notification is available in the TE after reception of the final response to the call setup, +CSSI is not returned as an intermediate result code but as an unsolicited result code.

When <m>=1 and a supplementary service notification is received during a mobile terminated call setup or during a call, or when a forward check supplementary service notification is received, unsolicited result code +CSSU: <code2>[,<index>[,[<number>],[<type>][,[<subaddr>],[<satype>]][,<SS_code>]]] is sent to TE. In case of MT call setup, result code is sent after every +CLIP result code (refer command Calling line identification presentation +CLIP) and when several different <code2>s are received from the network, each of them shall have its own +CSSU result code. <code2>=5 does not reflect any supplementary service, and the parameter <SS_code> will not be provided.

The supplementary service notification can also be reported in unsolicited result codes +CMCCSS<x> / +CMCCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCCSS<x> / +CMCCSSEND support numbers of the SIP URI format.

Read command returns the current settings.

Test command returns values supported as a compound value.

Defined values

<n>: integer type (parameter sets/shows the +CSSI intermediate result code presentation status to the TE)

0 disable

1 enable

<m>: integer type (parameter sets/shows the +CSSU unsolicited result code presentation status to the TE)

0 disable

1 enable

<code1>: integer type (it is manufacturer specific, which of these codes are supported)

0 unconditional call forwarding is active

1 some of the conditional call forwardings are active

2 call has been forwarded

3 call is waiting

4 this is a CUG call (also <index> present)

5 outgoing calls are barred

6 incoming calls are barred

7 CLIR suppression rejected

8 call has been deflected

<index>: integer type (refer Closed user group +CCUG command)

<SS_code>: integer type used to present the code identifying a single supplementary service (see 3GPP TS 24.080 [109] and 3GPP TS 29.002 [110] clause 17.7.5)

<code2>: integer type (it is manufacturer specific, which of these codes are supported)

0 this is a forwarded call (MT call setup)

1 this is a CUG call (also <index> present) (MT call setup)

2 call has been put on hold (during a voice call)

3 call has been retrieved (during a voice call)

4 multiparty call entered (during a voice call)

5 call on hold has been released (this is not a SS notification) (during a voice call)

6 forward check SS message received (can be received whenever)

7 call is being connected (alerting) with the remote party in alerting state in explicit call transfer operation (during a voice call)

8 call has been connected with the other remote party in explicit call transfer operation (also number and subaddress parameters may be present) (during a voice call or MT call setup)

9 this is a deflected call (MT call setup)

10 additional incoming call forwarded

<number>: string type phone number of format specified by <type>

<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7)

<subaddr>: string type subaddress of format specified by <satype>

<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8)

Implementation

Optional.

7.18 List current calls +CLCC

Table 51: +CLCC action command syntax

Command

Possible response(s)

+CLCC

[+CLCC: <ccid1>,<dir>,<stat>,<mode>,<mpty>[,<number>,<type>[,<alpha>[,<priority>[,<CLI validity>]]]]

[<CR><LF>+CLCC: <ccid2>,<dir>,<stat>,<mode>,<mpty>[,<number>,<type>[,<alpha>[,<priority>[,<CLI validity>]]]]

[…]]]

+CME ERROR: <err>

+CLCC=?

Description

Returns list of current calls of MT. If command succeeds but no calls are available, no information response is sent to TE. Refer clause 9.2 for possible <err> values. See also AT command +CLCCS.

Defined values

<ccidx>: integer type. Call identification number as described in 3GPP TS 22.030 [19] clause 6.5.5.1. This number can be used in +CHLD command operations. Value range is from 1 to N. N, the maximum number of simultaneous call control processes is implementation specific.

<dir>: integer type

0 mobile originated (MO) call

1 mobile terminated (MT) call

<stat>: integer type (state of the call)

0 active

1 held

2 dialing (MO call)

3 alerting (MO call)

4 incoming (MT call)

5 waiting (MT call)

<mode>: integer type (bearer/teleservice)

0 voice

1 data

2 fax

3 voice followed by data, voice mode

4 alternating voice/data, voice mode

5 alternating voice/fax, voice mode

6 voice followed by data, data mode

7 alternating voice/data, data mode

8 alternating voice/fax, fax mode

9 unknown

<mpty>: integer type

0 call is not one of multiparty (conference) call parties

1 call is one of multiparty (conference) call parties

<number>: string type phone number in format specified by <type>.

<type>: type of address octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7).

<alpha>: string type alphanumeric representation of <number> corresponding to the entry found in phonebook; used character set should be the one selected with command select TE character set +CSCS.

<priority>: integer type parameter indicating the eMLPP priority level of the call, values specified in 3GPP TS 22.067 [54].

<CLI validity>: integer type. This parameter can provide details why <number> does not contain a calling party BCD number (refer 3GPP TS 24.008 [8] clause 10.5.4.30). The parameter is not present for MO call types.

0 CLI valid

1 CLI has been withheld by the originator (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Reject by user")

2 CLI is not available due to interworking problems or limitations of originating network (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Interaction with other service")

3 CLI is not available due to calling party being of type payphone (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Coin line/payphone")

4 CLI is not available due to other reasons (refer 3GPP TS 24.008 [8] table 10.5.135a/3GPP TS 24.008 code "Unavailable")

When CLI is not available (<CLI validity>=2, <CLI validity>=3 or <CLI validity>=4), <number> shall be an empty string ("") and <type> value will not be significant. Nevertheless, TA may return the recommended value 128 for <type> (TON/NPI unknown in accordance with 3GPP TS 24.008 [8] clause 10.5.4.7).

When CLI has been withheld by the originator, (<CLI validity>=1) and the CLIP is provisioned with the "override category" option (refer 3GPP TS 22.081 [3] and 3GPP TS 23.081 [40]), <number> and <type> is provided. Otherwise, TA shall return the same setting for <number> and <type> as if the CLI was not available.

Implementation

Optional. Recommended when +CHLD command is implemented.

When +CDU is supported and SIP URIs are used in the MT, the AT command +CLCC is fully replaced by +CLCCS.

7.19 Preferred PLMN list +CPOL

Table 52: +CPOL parameter command syntax

Command	Possible response(s)
+CPOL=[<index>][,<format>[,<oper>[,<GSM_AcT>,<GSM_Compact_AcT>,<UTRAN_AcT>,<E-UTRAN_AcT>,<NG-RAN_AcT>]]]	+CME ERROR: <err>
+CPOL?	+CPOL: <index1>,<format>,<oper1>[,<GSM_AcT1>,<GSM_Compact_AcT1>,<UTRAN_AcT1>,<E-UTRAN_AcT1>,<NG-RAN_AcT1>] [<CR><LF>+CPOL: <index2>,<format>,<oper2>[,<GSM_AcT2>,<GSM_Compact_AcT2>,<UTRAN_AcT2>,<E-UTRAN_AcT2,<NG-RAN_AcT2>>] […]] +CME ERROR: <err>
+CPOL=?	+CPOL: (list of supported <index>s),(list of supported <format>s) +CME ERROR: <err>

Description

This command is used to edit the PLMN selector with Access Technology lists in the SIM card or active application in the UICC (GSM or USIM).

Execute command writes an entry in the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS. If no list has been previously selected, the User controlled PLMN selector with Access Technology, EF_PLMNwAcT,is the one accessed by default. If <index> is given but <oper> is left out, entry is deleted. If <oper> is given but <index> is left out, <oper> is put in the next free location. If only <format> is given, the format of the <oper> in the read command is changed. The Access Technology selection parameters, <GSM_AcT>, <GSM_Compact_AcT>, <UTRAN_AcT>, <E-UTRAN_AcT> and <NG-RAN_AcT> are required when writing User controlled PLMN selector with Access Technology, EF_PLMNwAcT, Operator controlled PLMN selector with Access Technology EF_OPLMNwAcT and HPLMN selector with Access Technology EF_HPLMNwAcT, see 3GPP TS 31.102 [59]. Refer clause 9.2 for possible <err> values.

NOTE 1: MT can also update the User controlled PLMN selector with Access Technology, EF_PLMNwAcT, automatically when new networks are selected.

NOTE 2: The Operator controlled PLMN selector with Access Technology EF_OPLMNwAcT, can only be written if the write access condition in the SIM/USIM has been previously verified.

Read command returns all used entries from the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS, with the Access Technologies for each PLMN in the list.

Test command returns the whole index range supported by the SIM as compound values.

Defined values

<indexn>: integer type; the order number of operator in the SIM/USIM preferred operator list

<format>: integer type

0 long format alphanumeric <oper>

1 short format alphanumeric <oper>

2 numeric <oper>

<opern>: string type; <format> indicates if the format is alphanumeric or numeric (see +COPS)

<GSM_AcTn>: integer type; GSM access technology:

0 access technology not selected

1 access technology selected

<GSM_Compact_AcTn>: integer type; GSM compact access technology

0 access technology not selected

1 access technology selected

<UTRAN_AcTn>: integer type; UTRAN access technology

0 access technology not selected

1 access technology selected

<E-UTRAN_AcTn>: integer type; E-UTRAN access technology

0 access technology not selected

1 access technology selected

<NG-RAN_AcTn>: integer type; NG-RAN access technology

0 access technology not selected

1 access technology selected

Implementation

Optional.

7.20 Selection of preferred PLMN list +CPLS

Table 53: +CPLS parameter command syntax

Command	Possible response(s)
+CPLS=[<list>]	+CME ERROR: <err>
+CPLS?	+CPLS: <list> +CME ERROR: <err>
+CPLS=?	+CPLS: (list of supported <list>s) +CME ERROR: <err>

Description

This command is used to select one PLMN selector with Access Technology list in the SIM card or active application in the UICC (GSM or USIM), that is used by +CPOL command.

Execute command selects a list in the SIM/USIM. Refer clause 9.2 for possible <err> values.

Read command returns the selected PLMN selector list from the SIM/USIM.

Test command returns the whole index range supported lists by the SIM/USIM as a compound value.

Defined values

<list>: integer type

0 User controlled PLMN selector with Access Technology EF_PLMNwAcT, if not found in the SIM/UICC then PLMN preferred list EF_PLMNsel (this file is only available in SIM card or GSM application selected in UICC)

1 Operator controlled PLMN selector with Access Technology EF_OPLMNwAcT

2 HPLMN selector with Access Technology EF_HPLMNwAcT

Implementation

Optional.

7.21 Read operator names +COPN

Table 54: +COPN action command syntax

Command

Possible response(s)

+COPN

+COPN: <numeric1>,<alpha1>

[<CR><LF>+COPN: <numeric2>,<alpha2>

[…]]

+CME ERROR: <err>

+COPN=?

Description

Execute command returns the list of operator names from the MT. Each operator code <numericn> that has an alphanumeric equivalent <alphan> in the MT memory shall be returned. Refer clause 9.2 for possible <err> values.

Defined values

<numericn>: string type; operator in numeric format (see +COPS)

<alphan>: string type; operator in long alphanumeric format (see +COPS)

Implementation

Optional.

7.22 eMLPP priority registration and interrogation +CAEMLPP

Table 55: +CAEMLPP parameter command syntax

Command	Possible Response(s)
+CAEMLPP=<priority>	+CME ERROR: <err>
+CAEMLPP?	+CAEMLPP: <default_priority>,<max_priority> +CME ERROR: <err>
+CAEMLPP=?

Description

The execute command is used to change the default priority level of the user in the network. The requested priority level is checked against the eMLPP subscription of the user stored on the SIM card or in the active application in the UICC (GSM or USIM) EF_eMLPP. If the user doesn’t have subscription for the requested priority level an ERROR or +CME ERROR result code is returned. Refer clause 9.2 for possible <err> values.

The read command triggers an interrogation of the provision of the maximum priority level which the service subscriber is allowed to use and default priority level activated by the user.

If the service is not provisioned, a result code including the SS-Status (?) parameter is returned.

Defined values

<priority>: integer type parameter which identifies the default priority level to be activated in the network, values specified in 3GPP TS 22.067 [54]

<default_priority>: integer type parameter which identifies the default priority level which is activated in the network, values specified in 3GPP TS 22.067 [54]

<max_priority>: integer type parameter which identifies the maximum priority level for which the service subscriber has a subscription in the network, values specified in 3GPP TS 22.067 [54]

Implementation

Mandatory for an MT supporting AT commands only and supplementary service eMLPP is implemented.

7.23 eMLPP subscriptions +CPPS

Table 56: +CPPS action command syntax

Command

Possible response(s)

+CPPS

[+CPPS: <priority>[,<priority>

[…]]]

+CME ERROR: <err>

+CPPS=?

Description

This command returns all eMLPP priority subscriptions of the user stored on the SIM card or in the active application in the UICC (GSM or USIM) EF_eMLPP. If no explicit priority level subscription is stored on the SIM card or in the active application in the UICC (GSM or USIM) EF_eMLPP the result code OK is returned. Refer clause 9.2 for possible <err> values.

Defined values

<priority>: integer type, eMLPP subscription to priority level {0,1,..,4} as defined in 3GPP TS 22.067 [54].

Implementation

Mandatory for a MT supporting AT commands only and eMLPP is implemented.

7.24 Fast call setup conditions +CFCS

Table 57: +CFCS parameter command syntax

Command	Possible response(s)
+CFCS=<priority>,<status>	+CME ERROR: <err>
+CFCS?	[+CFCS: <priority>[,<priority> […]]] +CME ERROR: <err>
+CFCS=?	+CFCS: (list of supported <priority>,<status>s)

Description

The set command is used to edit the status of the priority level for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EF_eMLPP. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. Refer clause 9.2 for possible <err> values.

The read command returns all enabled priority levels for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EF_eMLPP. If no priority level is enabled for fast call set-up, the result code OK is returned.

Test command returns the values supported by the UE.

Defined values

<priority>: integer type, eMLPP fast call set-up priority level {0,1,..,4} as defined in 3GPP TS 22.067 [54]

<status>: integer type

0 disable <priority> for fast call set-up

1 enable <priority> for fast call set-up

Implementation

Mandatory for a MT supporting AT commands only and eMLPP is implemented.

7.25 Automatic answer for eMLPP service +CAAP

Table 58: +CAAP parameter command syntax

Command	Possible response(s)
+CAAP=<priority>,<status>	+CME ERROR: <err>
+CAAP?	[+CAAP: <priority>[,<priority> […]]] +CME ERROR: <err>
+CAAP=?	+CAAP: (list of supported <priority>,<status>s)

Description

The set command is used to edit the status of the priority level for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EF_AAeM. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. Refer clause 9.2 for possible <err> values.

The read command returns all enabled priority levels for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EF_AAeM. If no priority level is enabled for automatic answering for eMLPP, the result code OK is returned.

Test command returns the values supported by the UE.

Defined values

<priority>: eMLPP automatic answer priority level value {A,B,0,1,..,4} as defined in 3GPP TS 22.067 [54]

<status>: integer type

0 disable eMLPP <priority> for automatic answering

1 enable eMLPP <priority> for automatic answering

Implementation

Mandatory for a MT supporting AT commands only and eMLPP is implemented.

7.26 User to user signalling service 1 +CUUS1

Table 59: +CUUS1 parameter command syntax

Command	Possible response(s)
+CUUS1=[<n>[,<m>[,<message>[,<UUIE>[,<message>[,<UUIE>[,…]]]]]]]	+CME ERROR: <err>
+CUUS1?	+CUUS1: <n>,<m>[,<message>,<UUIE>[,<message>,<UUIE>[,…]]]
+CUUS1=?	+CUUS1: (list of supported <n>s),(list of supported <m>s),(list of supported <message>s),(list of supported <messageI>s),(list of supported <messageU>s)

Description

This command allows control of the User-to-User Signalling Supplementary Service 1 (UUS1) according to 3GPP TS 22.087 [58].

Parameters <message> and <UUIE> are used to activate/deactivate the implicit request of the User-to-User Signalling Supplementary Service 1.

When <message> and <UUIE> are both present the string specified in <UUIE> is included as the value part of the User-to-User Information Element (as defined in 3GPP TS 24.008 [8]) into all subsequent messages of type <message>. If parameter <message> is present but parameter <UUIE> is not present then the User-to-User Information Element shall not be present in subsequent messages of type <message>.

Parameters <n> and <m> are used to enable/disable the presentation of incoming User-to-User Information Elements.

When <n>=1 and a User-to-User Information is received after a mobile originated call setup or after hanging up a call, intermediate result code +CUUS1I: <messageI>,<UUIE> is sent to the TE.

When <m>=1 and a User-to-User Information is received during a mobile terminated call setup or during a remote party call hangup, unsolicited result code +CUUS1U: <messageU>,<UUIE> is sent to the TE.

Refer clause 9.2 for possible <err> values.

Test command returns values supported as compound values.

Defined values

<n>: integer type (parameter sets/shows the +CUUS1I result code presentation status in the TA).

0 disable.

1 enable.

<m>: integer type (parameter sets/shows the +CUUS1U result code presentation status in the TA).

0 disable.

1 enable.

<message>: integer type (type of message containing the outgoing User-to-User Information Element).

0 ANY

1 SETUP

2 ALERT

3 CONNECT

4 DISCONNECT

5 RELEASE

6 RELEASE_COMPLETE

<messageI>: integer type (type of message containing the intermediate User-to-User Information Element).

0 ANY

1 ALERT

2 PROGRESS

3 CONNECT (sent after +COLP if enabled)

4 RELEASE

<messageU>: integer type (type of message containing the unsollicited User-to-User Information Element).

0 ANY

1 SETUP (returned after +CLIP if presented, otherwise after every RING or +CRING)

2 DISCONNECT

3 RELEASE_COMPLETE

<UUIE>: the User-user Information Element (as defined in 3GPP TS 24.008 [8]) in hexadecimal character format (for hexadecimal format, refer +CSCS).

NOTE: If the TA does not distinguish the type of message containing the User-to-user Information Element, it can use the value for ANY message.

Implementation

Optional.

7.27 Preferred network indication +CPNET

Table 59A: +CPNET parameter command syntax

Command	Possible response(s)
+CPNET=[<Pref_net>]
+CPNET?	+CPNET: <Pref_net>
+CPNET=?	+CPNET: (list of supported <Pref_net>s)

Description

This command indicates whether the terminal has preference <Pref_net> for GERAN/UTRAN/E-UTRAN/NG-RAN or GAN, see 3GPP TS 44.318 [70].

Read command returns the current preference for GERAN/UTRAN/E-UTRAN/NG-RAN or GAN.

Test command returns the parameter indicating preference <Pref_net> for GERAN/UTRAN/E-UTRAN/NG-RAN or GAN as a compound value.

Defined values

<Pref_net>: integer type; indicates the preference for GERAN/UTRAN/E-UTRAN/NG-RAN or GAN.

0 GERAN/UTRAN/E-UTRAN/NG-RAN shall be used. The terminal uses GERAN/UTRAN/E-UTRAN/NG-RAN coverage only.

1 GAN shall be used. The terminal used GAN coverage only.

2 GERAN/UTRAN/E-UTRAN/NG-RAN preferred. The terminal prefers to stay in GERAN/UTRAN/E-UTRAN/NG-RAN rather than GAN.

3 GAN preferred. The terminal prefers to stay in GAN rather than GERAN/UTRAN/E-UTRAN/NG-RAN.

NOTE: Usage of value 0 or 1 will prevent the terminal from changing between GERAN/UTRAN/E-UTRAN/NG-RAN and GAN. E.g. setting <Pref_net> to 1 indicates that only GAN will be used, and prevents the terminal from using available GERAN/UTRAN/E-UTRAN/NG-RAN coverage.

Implementation

Optional.

7.28 Preferred network status +CPNSTAT

Table 59B: +CPNSTAT parameter command syntax

Command	Possible response(s)
+CPNSTAT=[<n>]
+CPNSTAT?	+CPNSTAT: <n>,<stat>
+CPNSTAT=?	+CPNSTAT: (list of supported <n>s)

Description

Set command controls the presentation of an unsolicited result code +CPNSTAT: <stat> when <n>=1 and there is a change in the preferred network indication status.

Read command returns the status of result code presentation <n> and an integer <stat> which shows whether the terminal is in GERAN/UTRAN/E-UTRAN/NG-RAN or GAN, see 3GPP TS 44.318 [70].

NOTE: Further details about registration status are available using commands +CREG (see clause 7.2), +CGREG (see clause 10.1.19), +CEREG (see clause 10.1.21) and +CNRREG (see clause 10.1.47.

Test command returns the list of supported unsolicited result codes as a compound value.

Defined values

<n>: integer type

0 disable preferred network indication unsolicited result code.

1 enable preferred network indication unsolicited result code +CPNSTAT: <stat>.

<stat>: integer type; preferred network indication status.

0 Requested network not available.

1 GERAN/UTRAN/E-UTRAN/NG-RAN used.

2 GAN used.

Implementation

Optional.

7.29 Current packet switched bearer +CPSB

Table 59C: +CPSB parameter command syntax

Command	Possible response(s)
+CPSB=[<n>]	+CME ERROR: <err>
+CPSB?	+CPSB: <n>[,<cid>,<curr_bearer>] [<CR><LF>+CPSB: <n>,<cid>,<curr_bearer> […]] +CME ERROR: <err>
+CPSB=?	+CPSB: (list of supported <n>s)

Description

Set command controls the presentation of an unsolicited result code +CPSB: <cid>,<curr_bearer> when <n>=1 and the <cid> corresponds to a PDP context in the PDP-ACTIVE state, to an EPS bearer context in the BEARER CONTEXT ACTIVE state or to a 5GS QoS flow of a PDU session in the PDU SESSION ACTIVE state and there is a change in the current value of <curr_bearer> due to the reception of a control or signalling message from the network as specified in 3GPP TS 44.060 [71], 3GPP TS 25.331 [74], 3GPP TS 36.331 [86] or 3GPP TS 38.331 [160].

Read command returns the current status of the unsolicited result code presentation <n>. The parameters <cid> and <curr_bearer> are returned for each defined context when <n>=1 for <cid>s that correspond to a PDP context in the PDP-ACTIVE state, to an EPS bearer context in the BEARER CONTEXT ACTIVE state or to a 5GS QoS flow of a PDU session in the PDU SESSION ACTIVE state.

Refer clause 9.2 for possible <err> values.

Test command returns the list of supported <n>s as a compound value.

Defined values

<n>: integer type

0 disable the presentation of the unsolicited result code

1 enable the presentation of the unsolicited result code
+CPSB: <cid>,<curr_bearer>

<cid>: A numeric parameter which specifies a particular PDP context,an EPS bearer context or a 5GS QoS flow. The <cid> parameter is local to the TE-MT interface and identifies only those PDP contexts, EPS bearer contexts or 5GS QoS flows which have been setup via AT command (see the +CGDCONT and +CGDSCONT commands).

<curr_bearer>: integer type; the current packet switched bearer which is established between the UE and network.

0 There is currently no packet switched bearer between the UE and the network (e.g. RAB is released in UMTS or the TBF is released in GSM). This would mean that there is no bearer associated to the PDP context referred to by the <cid> parameter and hence no data transfer is currently occuring on that particular PDP context. This result code covers the case where the PDP context is active but there is no bearer associated with it.

1 GPRS. (See 3GPP TS 44.060 [71] for definition of GPRS TBF Mode)

2 EGPRS. (See 3GPP TS 44.060 [71] for definition of EGPRS TBF Mode)

3 Non-HSUPA in uplink and non-HSDPA in downlink. (See NOTE 1 to NOTE 3)

4 HSUPA in uplink and non-HSDPA in downlink. (See NOTE 1 to NOTE 4)

5 Non-HSUPA in uplink and HSDPA in downlink. (See NOTE 1 to NOTE 4)

6 HSUPA in uplink and HSDPA in downlink. (See NOTE 1 to NOTE 4)

7 EPS (See NOTE 5)

8 5GS (See NOTE 6)

NOTE 1: The term "non-HSDPA" means a non-HSDPA UMTS bearer. 3GPP TS 25.331 [74] specifies the criterion to be satisfied in order for a downlink UMTS RAB to be termed as HSDPA. If those criterion are not met, then the downlink UMTS RAB would be termed as "non-HSDPA" by this AT command.

NOTE 2: The term "non-HSUPA" means a non-HSUPA UMTS bearer. 3GPP TS 25.331 [74] specifies the criterion to be satisfied in order for an uplink UMTS RAB to be termed as HSUPA (or Enhanced uplink DCH). If those criterion are not met, then the uplink UMTS RAB would be termed as "non-HSUPA" by this AT command.

NOTE 3: The terms "non-HSDPA", "non-HSUPA" indicate R99 to pre- HSDPA or pre-HSUPA UMTS bearers. They do not imply GPRS or EGPRS bearers.

NOTE 4: See 3GPP TS 25.308 [72] for HSDPA and 3GPP TS 25.319 [73] for HSUPA.

NOTE 5: The term "EPS" means an EPS bearer (see 3GPP TS 36.331 [86]).

NOTE 6: The term "5GS" means a 5GS QoS flow (see 3GPP TS 38.331 [160]).

Implementation

Optional.

7.30 Calling name identification presentation +CNAP

Table 59D: +CNAP parameter command syntax

Command	Possible response(s)
+CNAP=[<n>]
+CNAP?	+CNAP: <n>,<m>
+CNAP=?	+CNAP: (list of supported <n>s)

Description

This command refers to the supplementary service CNAP (Calling Name Presentation) according to 3GPP TS 22.096 [93] that enables a called subscriber to get a calling name indication (CNI) of the calling party when receiving a mobile terminated call. Set command enables or disables the presentation of the CNI at the TE. It has no effect on the execution of the supplementary service CNAP in the network.

When <n>=1, the presentation of the calling name indication at the TE is enabled and CNI is provided the unsolicited result code, +CNAP: <name>[,<CNI_validity>] is returned after every RING (or +CRING: <type>; refer clause "Cellular result codes +CRC") result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered.

The calling name indication can also be reported in unsolicited result codes +CMCCSS<x> / +CMCCSSEND, enabled with +CMCCS=3 (see AT command monitor of current calls +CMCCS). The unsolicited result codes +CMCCSS<x> / +CMCCSSEND support numbers of the SIP URI format.

Read command gives the status of <n>, and also triggers an interrogation of the provision status of the CNAP service according 3GPP TS 22.096 [93] (given in <m>).

Test command returns values supported as a compound value.

Defined values

<n>: integer type (parameter sets/shows the result code presentation status to the TE)

0 disable

1 enable

<m>: integer type (parameter shows the subscriber CNAP service status in the network)

0 CNAP not provisioned

1 CNAP provisioned

2 unknown (e.g. no network, etc.)

<name>: string type, up to 80 characters long string containing the calling name

<CNI_validity>: integer type

0 CNI valid

1 CNI has been withheld by the originator.

2 CNI is not available due to interworking problems or limitations of originating network.

When CNI is not available ( <CNI_validity>=2), <name> shall be an empty string ("").

When CNI has been withheld by the originator, (<CNI_validity>=1) and the CNAP is provisioned with the "override category" option (refer 3GPP TS 22.096 [93] and 3GPP TS 23.096 [94]), <name> is provided. Otherwise, TA shall return the same setting for <name> as if the CNI was not available.

Implementation

Optional.

7.31 Connected line identification restriction status +COLR

Table 59E: +COLR action command syntax

Command	Possible response(s)
+COLR	+COLR: <m>
+COLR=?

Description

This command refers to the supplementary service COLR (Connected Line Identification Restriction) according to 3GPP TS 22.081 [3] and supplementary service TIR (Terminating Identification Restriction) according to 3GPP TS 24.608 [120] that enables a called subscriber to restrict the possibility of presentation of connected line identity (COL) to the calling party after receiving a mobile terminated call. The command displays the status of the COL presentation in the network. It has no effect on the execution of the supplementary services COLR / TIR in the network.

The command triggers an interrogation of the activation status of the COLR supplementary service according to 3GPP TS 22.081 [3] and the TIR supplementary service according to 3GPP TS 24.608 [120] (given in <m>).

Activation, deactivation, registration and erasure of the supplementary service COLR / TIR are not applicable.

Defined values

<m>: integer type (parameter shows the subscriber COLR / TIR service status in the network).

0 COLR / TIR not provisioned

1 COLR / TIR provisioned

2 unknown (e.g. no network, etc.)

Implementation

Optional.

7.32 Service specific access control restriction status +CSSAC

Table 7.32-1: +CSSAC action command syntax

Command	Possible response(s)
+CSSAC	+CSSAC: <BFVoice>,<BFVideo>,<BTVoice>,<BTVideo>
+CSSAC=?

Description

This command refers to SSAC (Service Specific Access Control) related information which is used by MMTEL application (see 3GPP TS 24.173 [87]). The command provides the current status of the parameters for SSAC, <BFVoice>, <BFVideo>, <BTVoice> and <BTVideo>. The AT command has no effect on the execution of SSAC.

Defined values

<BFVoice> integer type; parameter shows the barring factor for MMTEL voice. <BFVoice> is mapped to the BarringFactorForMMTEL-Voice as in table 7.32-2.

Table 7.32-2: Value of BFVoice and its interpretation by MMTEL application

<BFVoice>	BarringFactorForMMTEL-Voice as specified in 3GPP TS 24.173 [87]
0	0
1	0,05
2	0,1
3	0,15
4	0,2
5	0,25
6	0,3
7	0,4
8	0,5
9	0,6
10	0,7
11	0,75
12	0,8
13	0,85
14	0,9
15	0,95
16	1

<BFVideo> integer type; parameter shows the barring factor for MMTEL video. <BFVideo> is mapped to the BarringFactorForMMTEL-Video as in table 7.32-3.

Table 7.32-3: Value of BFVideo and its interpretation by MMTEL application

<BFVideo>	BarringFactorForMMTEL-Video as specified in 3GPP TS 24.173 [87]
0	0
1	0,05
2	0,1
3	0,15
4	0,2
5	0,25
6	0,3
7	0,4
8	0,5
9	0,6
10	0,7
11	0,75
12	0,8
13	0,85
14	0,9
15	0,95
16	1

<BTVoice> integer type; parameter shows the barring timer for MMTEL voice. <BTVoice> is mapped to the BarringTimeForMMTEL-Voice as in table 7.32-4.

Table 7.32-4: Value of BTVoice and its interpretation by MMTEL application

<BTVoice>	BarringTimeForMMTEL-Voice as specified in 3GPP TS 24.173 [87]
0	0
1	4
2	8
3	16
4	32
5	64
6	128
7	256
8	512

<BTVideo> integer type; parameter shows the barring timer for MMTEL video. <BTVideo> is mapped to the BarringTimeForMMTEL-Video as in table 7.32-5.

Table 7.32-5: Value of BTVideo and its interpretation by MMTEL application

<BTVideo>	BarringTimeForMMTEL-Video as specified in 3GPP TS 24.173 [87]
0	0
1	4
2	8
3	16
4	32
5	64
6	128
7	256
8	512

Implementation

Optional.

This command is only applicable to UEs in E-UTRAN.

7.33 Network emergency (bearer) services support +CNEM

Table 7.33-1: +CNEM parameter command syntax

Command	Possible response(s)
+CNEM=[<reporting>]	+CME ERROR: <err>
+CNEM?	+CNEM: <reporting>[,<emb_Iu_supp>[,<emb_S1_supp>[,<ems_5G_supp>,<emf_5G_supp>,<emcn3_5G_supp>]]]
+CNEM=?	+CNEM: (list of supported <reporting>s)

Description

Set command enables reporting of changes in the emergency (bearer) services support indicators and emergency services fallback indicator with the unsolicited result code +CNEMIU: <emb_Iu_supp> according to the network feature support information element, see 3GPP TS 24.008 [8] clause 10.5.5.23, the unsolicited result code +CNEMS1: <emb_S1_supp> according to the EPS network feature support information element, see 3GPP TS 24.301 [83] clause 9.9.3.12A, and the unsolicited result code +CNEM5G: <ems_5G_supp>,<emf_5G_supp>,<emcn3_5G_supp> according to the 5GS network feature support information element, see 3GPP TS 24.501 [161] clause 9.11.3.5. Refer clause 9.2 for possible <err> values.

Read command returns current command setting and if enabled, the settings of the emergency bearer services support indicator in Iu mode and the emergency bearer services support indicator in S1 mode for the network where the UE is attached. The read command also returns the emergency services support indicator in 5G and the emergency services fallback indicator in 5G for the network where the UE is registered.

Test command returns values supported as a compound value.

Defined values

<reporting>: integer type

0 Reporting not enabled

1 Reporting enabled

<emb_Iu_supp>: integer type. Emergency bearer services support indicator for Iu mode (See NOTE).

0 Emergency bearer services in Iu mode and A/Gb mode not supported

1 Emergency bearer services supported in Iu mode, but not supported in A/Gb mode

<emb_S1_supp>: integer type. Emergency bearer services support indicator for S1 mode (See NOTE).

0 Emergency bearer services in S1 mode not supported

1 Emergency bearer services in S1 mode supported

<ems_5G_supp>: integer type. Emergency services support indicator for 5G (See NOTE).

0 Emergency services in 5G not supported

1 Emergency services supported in NR connected to 5GC only

2 Emergency services supported in E-UTRA connected to 5GC only

3 Emergency services supported in NR connected to 5GC and E-UTRA connected to 5GC

<emf_5G_supp>: integer type. Emergency services fallback indicator for 5G (See NOTE).

0 Emergency services fallback in 5G not supported

1 Emergency services fallback supported in NR connected to 5GC only

2 Emergency services fallback supported in E-UTRA connected to 5GC only

3 Emergency services fallback supported in NR connected to 5GC and E-UTRA connected to 5GC

<emcn3_5G_supp>: integer type. Emergency services support indicator for non-3GPP access (See NOTE).

0 Emergency services not supported over non-3GPP access

1 Emergency services supported over non-3GPP access

NOTE: The indicators <emb_Iu_supp>, <emb_S1_supp>, <ems_5G_supp>, <emf_5G_supp> and <emcn3_5G_supp> are only set to supported when explicitly signalled from the network. When an emergency (bearer) services support indicator is not signalled from the network or if no network is available, this is interpreted as "Emergency (bearer) services not supported". When the emergency services fallback indicator is not signalled from the network or if no network is available, this is interpreted as "Emergency services fallback in 5G not supported".

Implementation

Optional.

7.34 Enhanced closed user group +CECUG

Table 7.34-1: +CECUG parameter command syntax

Command	Possible response(s)
+CECUG=<n>,[<CUG_pointer>[,<CUG_index>,<CUG_info>]]
+CECUG?	[+CECUG: <n>,<CUG_pointer>,<CUG_index>,<CUG_info> [<CR><LF>+CECUG: <n>,<CUG_pointer>,<CUG_index>,<CUG_info> […]]]
+CECUG=?	+CECUG: (list of supported <n>s),(range of supported <CUG_pointer>s)

Description

This command allows control of the Closed User Group supplementary service (refer 3GPP TS 22.085 [21] and 3GPP TS 24.654 [121]). Set command enables the served subscriber to create a number of <CUG_pointer>s that each define a <CUG_index> and a <CUG_info> to define how the preferential CUG and the Outgoing Access (OA) is handled for outgoing calls.

Set command with <n>=0 disable settings in the MT and use the subscribed settings, while <n>=1 enables to control the CUG information on the air interface as adjustments for outgoing calls according to the settings defined by the parameters <CUG_pointer>s, <CUG_index> and <CUG_info>. For calls initated using the dial command D, the dial string modifiers ‘G’ or ‘g’ can not indicate a <CUG_pointer> and the <CUG_index> and <CUG_info> as defined for <CUG_pointer>=1 shall be used.

NOTE 1: On a per call basis CUG functionality is explained in the clauses "ITU‑T Recommendation V.250 [14] dial command D" and "Dial URI +CDU".

A special form of the set command, +CECUG=<n>,<CUG_pointer> causes the value of <CUG_index> and <CUG_info> for the CUG pointer <CUG_pointer> to become undefined. The set command, +CECUG=0 that can be used to disable the CUG temporary mode will not make previously defined CUG pointers and the corresponding defined <CUG_index> and <CUG_info> undefined.

The read command returns the current settings for each defined CUG pointer.

The test command returns values supported as compound values.

Defined values

<n>: integer type. This parameter sets CUG activation on a per call basis.

0 disable CUG temporary mode. All calls initiated using the dial command D or +CDU use the subscribed CUG settings. The parameters <CUG_index> and <CUG_info> are ignored at call initiation. For calls initated using the dial command D, the dial string modifiers ‘G’ or ‘g’ have no effect (see clause "ITU T Recommendation V.250 [14] dial command D"). For calls initated using +CDU, the parameter <CUG_pointer> has no effect (see clause "Dial URI +CDU").

1 enable CUG temporary mode. Values for <CUG_index> and <CUG_info> are applied for:

– all calls initiated using the dial command D where the dial modifier ‘G’ or ‘g’ (see clause "ITU T Recommendation V.250 [14] dial command D") is present as part of the dial string.

– all calls initated using +CDU where parameter <CUG_pointer> is set to 1 (see clause "Dial URI +CDU")

If ‘G’ or ‘g’ is not applied (for the dial command D) or <CUG_pointer> is set to 0 (for +CDU) <CUG_index> and <CUG_info> are ignored. In that case only the subscribed CUG settings apply.

<CUG_pointer>: integer type. A numeric parameter which specifies a particular set of CUG data. The <CUG_pointer> is local to the TE-MT interface and identifies a particular <CUG_index> and <CUG_info> which indicates per call basis changes provided to the supplementary service closed user group. The range of permitted values is from 1-n. The maximum value of n is implementation specific.

NOTE 2: 3GPP TS 22.085 [21] indicates that each individual subscriber can be a member of a maximum of 10 CUGs.

<CUG_index>: string type. The parameter sets the CUG index for this <CUG_pointer>.

"0" … "32767" CUG index

"" no CUG index, indicated by empty string. Preferential CUG taken from subscriber data.

<CUG_info>: integer type. The parameter sets the CUG information for this <CUG_pointer>.

0 no information

1 suppress OA

2 suppress preferential CUG

3 suppress OA and preferential CUG

Implementation

Optional. This command can replace the command +CCUG.

7.35 Communication forwarding number and conditions with URI support +CCFCU

Table 7.35-1: +CCFCU action command syntax

Command

Possible response(s)

+CCFCU=<reason>,<mode>[,<numbertype>,<ton>,<number>[,<class>,<ruleset>

[,<subaddr>[,<satype>[,<time>]]]]]

+CME ERROR: <err>

when <mode>=2 and command successful:

+CCFCU: <status>,<class1>[,<numbertype>,<ton>,<number>[,<subaddr>,<satype>[,<time>]]]

[<CR><LF>+CCFCU: <status>,<class2>[,<number>,<type>[,<subaddr>,<satype>[,<time>]]]

[…]]

+CCFCU=?

+CCFCU: (list of supported <reason>s)

Description

The command allows control of the communication forwarding supplementary service according to 3GPP TS 22.072 [31], 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]. This command is an extended version of AT commands +CCFC and +CTFR which also supports numbers of the SIP URI format. Registration, erasure, activation, deactivation, and status query are supported. When querying the status of a network service (<mode>=2) the response line for ‘not active’ case (<status>=0) should be returned only if service is not active for any <class>.

Test command returns reason values supported as a compound value.

Defined values

<reason>: integer type

0 communication forwarding unconditional – CFU, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]

1 communication forwarding on busy user – CFB, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]

2 communication forwarding on no reply – CFNR, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]

3 communication forwarding on subscriber not reachable – CFNRc, refer 3GPP TS 22.082 [4] and 3GPP TS 24.604 [132]

4 all call forwarding (refer to "all CF" in 3GPP TS 22.030 [19])

5 all conditional call forwarding (refer to "all conditional CF" in 3GPP TS 22.030 [19])

6 communication deflection – CD, refer 3GPP TS 22.072 [31] and 3GPP TS 24.604 [132]

7 communication forwarding on not logged-in – CFNL, refer 3GPP TS 24.604 [132]

<mode>: integer type

0 disable

1 enable

2 query status

3 registration

4 erasure

<numbertype>: integer type. Indicating type of information in parameter <number>.

0 No valid information in parameter <number>. <number> shall then be set to empty string ("").

1 Number in <number> according to URI including the prefix specifying the URI type (see command +CDU). Parameter <ton> has no relevant information and is set to zero.

2 Number in <number> according to one of the formats supported by 3GPP TS 24.008 [8] clause 10.5.4.7)

<ton>: type of number in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.7). The parameter is also set to zero when it has no meaningful content, e.g. when <numbertype>=1.

<number>: string type phone number in format specified by <numbertype>. The used character set should be the one selected with command select TE character set +CSCS. When no number is available, <number> shall be set to empty string ("").

<subaddr>: string type subaddress of format specified by <satype>.

<satype>: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] clause 10.5.4.8); default 128.

<classx> is a sum of integers each representing a class of information (default 7 – voice, data and fax):

0 communication forwarding without differentiation on class of information

1 voice (telephony)

2 data (refers to all bearer services; with <mode>=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128)

4 fax (facsimile services)

8 short message service

16 data circuit sync

32 data circuit async

64 dedicated packet access

128 dedicated PAD access

<ruleset>: string type ruleset value of XML element of communication diversion XML document (refer 3GPP TS 24.604 [132]). If XML ruleset values are not supported or intended to be used, the parameter shall be set to an empty string ("").

<time>: integer type

1…30 when "no reply", "all call forwarding" or "all conditional call fowarding" is enabled or queried, this gives the time in seconds to wait before call is forwarded, default value 20.

<status>: integer type

0 not active

1 active

Implementation

Optional.

7.36 Message waiting indication control +CMWI

Table 7.36-1: +CMWI parameter command syntax

Command	Possible response(s)
+CMWI=[<state>[,<expiry_time>]]	+CME ERROR: <err>
+CMWI?	+CMWI: <state>[,<expiry_time>]
+CMWI=?	+CMWI: (list of supported <state>s),(maximum <expiry_time>)

Description

The command allows to control the message waiting indication service according to 3GPP TS 24.606 [134].

The set command invokes the service for a certain <expiry_time> or deactivates the service. Refer clause 9.2 for possible <err> values.

When the message waiting indication service is activated the unsolicited result code +CMWN: <mw_notification> is provided to indicate waiting messages.

The read command returns the message waiting indication service state and the time remaining for the service to be active if available.

Test command returns values supported as compound values. <expiry_time>s are supported from 0 to (maximum <expiry_time>) in seconds.

Defined values

<state>: integer type. Indicates the state of the message waiting indication service.

0 not active

1 active

<expiry_time>: integer type. Indicates the time in seconds after which the message waiting indication service will become inactive. The range of permitted values is from 0 to (2**32)-1. The default value is implementation specific.

<mw_notification>: string type. Indicates waiting message information in application/simple-message-summary MIME type format according to 3GPP TS 24.606 [134].

Implementation

Optional.

7.37 Session start and stop for MMTEL and SMSoverIP applications +CSCM

Table 7.37-1: +CSCM action command syntax

Command	Possible response(s)
+CSCM=<application>,<start-end_indication>	+CME ERROR: <err>
+CSCM=?	+CSCM: (list of supported <application>s),(list of supported <start-end_indication>s)

Description

This command allows the MMTEL and SMS over IP applications to provide start and stop indications to the MT, for MMTEL voice, MMTEL video or SMSoverIP sessions, in support of

– SCM (smart congestion mitigation) in E-UTRAN; and

– ACDC (Application specific Congestion control for Data Communications) in E-UTRAN and UTRAN.

The set command allows the:

– MMTEL application to provide an indication to the MT when an originating multimedia telephony session for voice communication is started or ended according to the conditions in 3GPP TS 24.173 [87]).

– MMTEL application to provide an indication to the MT when an originating multimedia telephony session for video communication is started or ended according to the conditions in 3GPP TS 24.173 [87]).

– SMS over IP application to provide an indication to the MT when an originating SMS over IP is started or ended according to the conditions in 3GPP TS 24.341 [101].

Refer clause 9.2 for possible <err> values.

The test command returns the supported values as compound values.

Defined values

<application>: integer type. Type of application.

0 MMTEL voice

1 MMTEL video

2 SMS over IP

<start-end_indication>: integer type. Indication of the start or the end of the session as indicated by <application>.

1 Start indication

2 End indication

Implementation

Optional.

For SCM, this command is only applicable to UEs in E-UTRAN.

For ACDC, this command is only applicable to UEs in UTRAN and E-UTRAN.

7.38 Power saving mode setting +CPSMS

Table 7.38-1: +CPSMS parameter command syntax

Command	Possible response(s)
+CPSMS=[<mode>[,<Requested_Periodic-RAU>[,<Requested_GPRS-READY-timer>[,<Requested_Periodic-TAU>[,<Requested_Active-Time>]]]]]	+CME ERROR: <err>
+CPSMS?	+CPSMS: <mode>,[<Requested_Periodic-RAU>],[<Requested_GPRS-READY-timer>],[<Requested_Periodic-TAU>],[<Requested_Active-Time>]
+CPSMS=?	+CPSMS: (list of supported <mode>s),(list of supported <Requested_Periodic-RAU>s),(list of supported <Requested_GPRS-READY-timer>s),(list of supported <Requested_Periodic-TAU>s),(list of supported <Requested_Active-Time>s)

Description

The set command controls the setting of the UE’s power saving mode (PSM) parameters. The command controls whether the UE wants to apply PSM or not, as well as the requested extended periodic RAU value and the requested GPRS READY timer value in GERAN/UTRAN, the requested extended periodic TAU value in E-UTRAN and the requested Active Time value. See the unsolicited result codes provided by commands +CGREG for the Active Time value, the extended periodic RAU value and the GPRS READY timer value that are allocated to the UE by the network in GERAN/UTRAN and +CEREG for the Active Time value and the extended periodic TAU value that are allocated to the UE by the network in E-UTRAN.

A special form of the command can be given as +CPSMS=2. In this form, the use of PSM will be disabled and data for all parameters in the command +CPSMS will be removed or, if available, set to the manufacturer specific default values.

Refer clause 9.2 for possible <err> values.

The read command returns the current parameter values.

The test command returns the supported <mode>s and the value ranges for the requested extended periodic RAU value and the requested GPRS READY timer value in GERAN/UTRAN, the requested extended periodic TAU value in E-UTRAN and the requested Active Time value as compound values.

Defined values

<mode>: integer type. Indication to disable or enable the use of PSM in the UE.

0 Disable the use of PSM

1 Enable the use of PSM

2 Disable the use of PSM and discard all parameters for PSM or, if available, reset to the manufacturer specific default values.

<Requested_Periodic-RAU>: string type; one byte in an 8 bit format. Requested extended periodic RAU value (T3312) to be allocated to the UE in GERAN/UTRAN. The requested extended periodic RAU value is coded as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000111" equals 70 hours). For the coding and the value range, see the GPRS Timer 3 IE in 3GPP TS 24.008 [8] Table 10.5.163a/3GPP TS 24.008. See also 3GPP TS 23.682 [149] and 3GPP TS 23.060 [47]. The default value, if available, is manufacturer specific.

<Requested_GPRS-READY-timer>: string type; one byte in an 8 bit format. Requested GPRS READY timer value (T3314) to be allocated to the UE in GERAN/UTRAN. The requested GPRS READY timer value is coded as one byte (octet 2) of the GPRS Timer information element coded as bit format (e.g. "01000011" equals 3 decihours or 18 minutes). For the coding and the value range, see the GPRS Timer IE in 3GPP TS 24.008 [8] Table 10.5.172/3GPP TS 24.008. See also 3GPP TS 23.060 [47]. The default value, if available, is manufacturer specific.

<Requested_Periodic-TAU>: string type; one byte in an 8 bit format. Requested extended periodic TAU value (T3412) to be allocated to the UE in E-UTRAN. The requested extended periodic TAU value is coded as one byte (octet 3) of the GPRS Timer 3 information element coded as bit format (e.g. "01000111" equals 70 hours). For the coding and the value range, see the GPRS Timer 3 IE in 3GPP TS 24.008 [8] Table 10.5.163a/3GPP TS 24.008. See also 3GPP TS 23.682 [149] and 3GPP TS 23.401 [82]. The default value, if available, is manufacturer specific.

<Requested_Active-Time>: string type; one byte in an 8 bit format. Requested Active Time value (T3324) to be allocated to the UE. The requested Active Time value is coded as one byte (octet 3) of the GPRS Timer 2 information element coded as bit format (e.g. "00100100" equals 4 minutes). For the coding and the value range, see the GPRS Timer 2 IE in 3GPP TS 24.008 [8] Table 10.5.163/3GPP TS 24.008. See also 3GPP TS 23.682 [149], 3GPP TS 23.060 [47] and 3GPP TS 23.401 [82]. The default value, if available, is manufacturer specific.

Implementation

Optional.

This command is not applicable to UEs in NG-RAN in this release of the specification.

7.39 Application Start and Stop indication for applications other than MMTEL and SMSoverIP +CACDC

Table 7.39-1: +CACDC action command syntax

Command	Possible response(s)
+CACDC=<OSid>,<OSappid>,<start-stop-indication>	+CME ERROR: <err>
+CACDC=?	+CACDC: (list of supported <OSid>,<OSappid> pairs),(list of supported <start-stop-indication>s)

Description

This command allows the operating system on the TE to provide start and stop indications other than MMTEL and SMSoverIP to the MT for a particular application in support of ACDC. Each application is identified by an application identity which consists of two parts:

<OSid> an operating system identifier. This identifier identifies the operating system.

<OSappid> an OS specific application identifier. This identifier is associated with a given application and uniquely identifies the application within the UE for a given operating system.

The supported <OSid>s and <OSappid>s are manufacturer specific.

Refer clause 9.2 for possible <err> values.

The test command returns the supported values as compound values.

Defined values

<OSid>: string type. Operating system identifier. The format of the OS ID is a Universally Unique IDentifier (UUID) as specified in RFC 4122 [155].

<OSappid>: string type. A string containing the OS specific application identifier. The format of the OS specific application identifier is manufacturer specific.

<start-stop-indication>: integer type. Indication to start sending data and the indication to stop sending data, for the application identified by <OSid> and <OSappid>.

0 indication to start sending data

1 indication to stop sending data

Implementation

Optional.

This command is only applicable to UEs in UTRAN and E-UTRAN.

7.40 eDRX setting +CEDRXS

Table 7.40-1: +CEDRXS parameter command syntax

Command	Possible response(s)
+CEDRXS=[<mode>,[,<AcT-type>[,<Requested_eDRX_value>]]]	+CME ERROR: <err>
+CEDRXS?	[+CEDRXS: <AcT-type>,<Requested_eDRX_value> [<CR><LF>+CEDRXS: <AcT-type>,<Requested_eDRX_value> […]]]
+CEDRXS=?	+CEDRXS: (list of supported <mode>s),(list of supported <AcT-type>s),(list of supported <Requested_eDRX_value>s)

Description

The set command controls the setting of the UEs eDRX parameters. The command controls whether the UE wants to apply eDRX or not, as well as the requested eDRX value for each specified type of access technology.

The set command also controls the presentation of an unsolicited result code +CEDRXP: <AcT-type>[,<Requested_eDRX_value>[,<NW-provided_eDRX_value>[,<Paging_time_window>]]] when <n>=2 and there is a change in the eDRX parameters provided by the network.

A special form of the command can be given as +CEDRXS=3. In this form, eDRX will be disabled and data for all parameters in the command +CEDRXS will be removed or, if available, set to the manufacturer specific default values.

Refer clause 9.2 for possible <err> values.

The read command returns the current settings for each defined value of <AcT-type>.

The test command returns the supported <mode>s and the value ranges for the access technology and the requested eDRX value as compound values.

Defined values

<mode>: integer type, indicates to disable or enable the use of eDRX in the UE. This parameter is applicable to all specified types of access technology, i.e. the most recent setting of <mode> will take effect for all specified values of <AcT>.

0 Disable the use of eDRX

1 Enable the use of eDRX

2 Enable the use of eDRX and enable the unsolicited result code
+CEDRXP: <AcT-type>[,<Requested_eDRX_value>[,<NW-provided_eDRX_value>[,<Paging_time_window>]]]

3 Disable the use of eDRX and discard all parameters for eDRX or, if available, reset to the manufacturer specific default values.

<AcT-type>: integer type, indicates the type of access technology. This AT-command is used to specify the relationship between the type of access technology and the requested eDRX value.

0 Access technology is not using eDRX. This parameter value is only used in the unsolicited result code.

1 EC-GSM-IoT (A/Gb mode)

2 GSM (A/Gb mode)

3 UTRAN (Iu mode)

4 E-UTRAN (WB-S1 mode)

5 E-UTRAN (NB-S1 mode)

<Requested_eDRX_value>: string type; half a byte in a 4 bit format. The eDRX value refers to bit 4 to 1 of octet 3 of the Extended DRX parameters information element (see clause 10.5.5.32 of 3GPP TS 24.008 [8]). For the coding and the value range, see Extended DRX parameters information element in 3GPP TS 24.008 [8] Table 10.5.5.32/3GPP TS 24.008. The default value, if available, is manufacturer specific.

<NW-provided_eDRX_value>: string type; half a byte in a 4 bit format. The eDRX value refers to bit 4 to 1 of octet 3 of the Extended DRX parameters information element (see clause 10.5.5.32 of 3GPP TS 24.008 [8]). For the coding and the value range, see Extended DRX parameters information element in 3GPP TS 24.008 [8] Table 10.5.5.32/3GPP TS 24.008.

<Paging_time_window>: string type; half a byte in a 4 bit format. The paging time window referes to bit 8 to 5 of octet 3 of the Extended DRX parameters information element (see clause 10.5.5.32 of 3GPP TS 24.008 [8]). For the coding and the value range, see the Extended DRX parameters information element in 3GPP TS 24.008 [8] Table 10.5.5.32/3GPP TS 24.008.

Implementation

Optional.

7.41 eDRX read dynamic parameters +CEDRXRDP

Table 7.41-1: +CEDRXRDP action command syntax

Command	Possible response(s)
+CEDRXRDP	+CEDRXRDP: <AcT-type>[,<Requested_eDRX_value>[,<NW-provided_eDRX_value>[,<Paging_time_window>]]]
+CEDRXRDP=?

Description

The execution command returns <AcT-type> and <Requested_eDRX_value>, <NW-provided_eDRX_value> and <Paging_time_window> if eDRX is used for the cell that the MS is currently registered to.

If the cell that the MS is currently registered to is not using eDRX, AcT-type=0 is returned.

Defined values

<AcT-type>: integer type, indicates the type of access technology. This AT-command is used to specify the relationship between the type of access technology and the requested eDRX value.

0 Access technology is not using eDRX

1 EC-GSM-IoT (A/Gb mode)

2 GSM (A/Gb mode)

3 UTRAN (Iu mode)

4 E-UTRAN (WB-S1 mode)

5 E-UTRAN (NB-S1 mode)

Implementation

Optional.

7.42 CIoT optimization configuration +CCIOTOPT

Table 7.42-1: CCIOTOPT parameter command syntax

Command	Possible Response(s)
+CCIOTOPT=[<n>,[<supported_UE_opt>[,<preferred_UE_opt>]]]	+CME ERROR: <err>
+CCIOTOPT?	+CCIOTOPT :<n>,<supported_UE_opt>,<preferred_UE_opt>
+CCIOTOPT=?	+CCIOTOPT: (list of supported <n>s),(list of supported <supported_UE_opt>s),(list of supported <preferred_UE_opt>s)

Description

The set command controls which CIoT optimizations the UE indicates as supported and preferred in EPS and in 5GS.

A UE supporting CIoT functionality may support,

– control plane CIoT EPS optimization or user plane CIoT EPS optimization or both (see 3GPP TS 24.301 [83], clause 9.9.3.34) when the UE is connected to EPC; or

– control plane CIoT 5GS optimization or user plane CIoT 5GS optimization or both (see 3GPP TS 24.501 [161], clause 5.3.21) when the UE is connected to 5GCN.

Based on the application characteristics the UE may prefer to be registered for,

– control plane CIoT EPS optimization or for user plane CIoT EPS optimization (see 3GPP TS 24.301 [83], clause 9.9.3.0B) when the UE is connected to EPC; or

– control plane CIoT 5GS optimization or for user plane CIoT 5GS optimization (see 3GPP TS 24.501 [161], clause 5.3.21) when the UE is connected to 5GCN.

Further,

– in EPS the network can support control plane CIoT EPS optimization or user plane CIoT EPS optimization or both (see 3GPP TS 24.301 [83], clause 9.9.3.12A); and

– in 5GS the network can support control plane CIoT 5GS optimization or user plane CIoT 5GS optimization or both (see 3GPP TS 24.501 [161], clause 5.3.21)

The set command is also used to control the reporting of the CIoT optimizations by the unsolicited result code +CCIOTOPTI. The unsolicited result code +CCIOTOPTI: <supported_Network_opt> is used to indicate the CIoT optimizations supported by the network in EPS and in 5GS.

Refer clause 9.2 for possible <err> values.

The read command returns the current settings for supported and preferred CIoT optimizations in EPS, the current settings for supported and preferred CIoT optimizations in 5GS and the current status of unsolicited result code +CCIOTOPTI.

The test command returns values supported as compound values.

Defined values

<n>: integer type. Enables or disables reporting of unsolicited result code +CCIOTOPTI.

0 Disable reporting.

1 Enable reporting.

3 Disable reporting and reset the parameters for supported and preferred CIoT optimizations in EPS and in 5GS to the default values.

<supported_UE_opt>: integer type; a decimal value of the bitmap that indicates the UE’s support for CIoT optimizations in EPS and in 5GS. The <supported_UE_opt> value is determined by summing all the applicable bits in Table 7.42-2.

Table 7.42-2:CIoT optimizations

Bit-number				Description
			Bit 1	Support for control plane CIoT EPS optimization
		Bit 2		Support for user plane CIoT EPS optimization
	Bit 3			Support for control plane CIoT 5GS optimization
Bit 4				Support for user plane CIoT 5GS optimization

EXAMPLE If the values of Support for control plane CIoT EPS optimization (Bit 1) and Support for user plane CIoT EPS optimization (Bit 2) are supported, then the <supported_UE_opt> value is 3. If the values of Support for user plane CIoT EPS optimization (Bit 2) and Support for user plane CIoT 5GS optimization (Bit 4) are supported, then the <supported_UE_opt> value is 10.

0 No support.

all other values are a decimal value of the bitmap (Bit 1, Bit 2, Bit 3 and Bit 4), see Table 7.42-2.

<preferred_UE_opt>: integer type; indicates the UE’s preference for CIoT optimizations in EPS or in 5GS.

0 No preference.

1 Preference for control plane CIoT EPS optimization.

2 Preference for user plane CIoT EPS optimization.

3 Preference for control plane CIoT 5GS optimization.

4 Preference for user plane CIoT 5GS optimization.

<supported_Network_opt>: integer type; indicates the Network support for CIoT optimizations in EPS or in 5GS.

0 No support.

1 Support for control plane CIoT EPS optimization.

2 Support for user plane CIoT EPS optimization.

3 Support for both control plane CIoT EPS optimization and user plane CIoT EPS optimization.

4 Support for control plane CIoT 5GS optimization.

5 Support for user plane CIoT 5GS optimization.

6 Support for both control plane CIoT 5GS optimization and user plane CIoT 5GS optimization.

Implementation

Optional.

7.43 CSG selection +CCSGS

Table 7.43: +CCSGS parameter command syntax

Command	Possible response(s)
+CCSGS=[<mode>[,<format>[,<CSGinfo>[,<AcT>]]]]	+CCSGS: <AcT>
+CCSGS?	+CCSGS: <mode>[,<format>,<CSGinfo>[,<AcT>]]
+CCSGS=?	+CCSGS: (list of supported <mode>s)

Description

Set command forces an attempt to select and register to the CSG Cell in UMTS/EPS network. <mode> is used to determine whether the selection is done automatically by the MT or is forced by this command to select CSG Cell in CSGinfo <CSGinfo> (it shall be given in format <format>) to a certain access technology, indicated in <AcT>. If the selected access technology is not available, then the same CSG id and associated PLMN shall be selected in other access technology. If the selected CSG cell is not available in all supported RATs, then MT shall follow the procedures described in 3GPP TS 23.122 clause 4.4.3.1.3. The selected CSG info format shall apply to further read commands (+CCSGS?) also. <mode>=0 forces an attempt to register to the CSG cell in UMTS/EPS network. <mode>=1 forces an attempt to do manual CSG selection to a CSG cell as per information in CGSinfo <CSGinfo>.<mode>.

This command is used when the ME performs successfully registered to a PLMN i.e. the UE executed Operator Selection (+COPS) command successfully.

Read command returns the current CSG selection mode, the currently selected CSG Cell information <CSGinfo> and the current Access Technology. If ME is not camped on CSG Cell when read command is issued, +CME ERROR: XX (Not camped on CSG Cell) shall be issued.

Test command returns a set of four parameters. A set consists of an integer indicating the availability of the CSG in Operator CSG list or Allowed CSG list <stat>, alphanumeric format of the CSG Type, HNB name, CSG ID and Associated PLMN MCC MNC<CSGinfo>, numeric format representation of the CSG ID and Asssociated PLMN MCC MNC <CSGinfo> and access technology <AcT>. <CSGinfo> consist of CSGType (if available from SIM), HNB name, CSG ID each delimited by comma. CSG Type shall provide the type of a CSG identity in a human readable form. See 3GPP TS 22.011 [170], 3GPP TS 23.003 [7] for details of CSG Type, HNB name and CSG ID representation. Any of the formats may be unavailable and should then be an empty field. The list of found CSG’s shall be in order: CSG’s in the Operator CSG list, CSG’s in the Allowed CSG list, other CSG’s.

It is recommended (although optional) that after the CSG list TA returns lists of supported <mode>s and <format>s. These lists shall be delimited from the CSG list by two commas.

The access technology selected parameters, <AcT>, should only be used in terminals capable to support CSG selection in more than one access technology. Selection of <AcT> does not limit the capability to cell reselections, even though an attempt is made to select a CSG id in an access technology, the phone may still select the same CSG id and associated PLMN in another access technology.

Defined values

<mode>: integer type

0 automatic CSG Selection mode (<CSGinfo> field is ignored)

1 manual CSG Selection mode (<CSGinfo> field shall be present, and <AcT> optionally)

2 set only <format> (for read command +CCSGS?), (<CSGinfo> and <AcT> fields are ignored)

<format>: integer type

0 alphanumeric <CSGinfo>

1 numeric <CSGinfo>

<CSGinfo>: string type; <format> indicates if the format is alphanumeric or numeric

CSGinfo consists of CSGType, HNB Name, CSGID and CSG Associated PLMN MCC MNC each delimited by a comma and in this particular order only. If any of the CSGType, HNB Name,CSGID is unavailable, it shall be an empty field. See 3GPP TS 22.011 [170], 3GPP TS 23.003 [7] for details of CSG Type, HNB name and CSG ID representation. When selecting the CSG using the set command with <mode> as 1, the CSGID and associated PLMN MCC MNC are mandatory while CSG Type and HNB name are optional.

In the alphanumeric format CSGType, HNB Name, CSGID and CSG Associated PLMN MCC MNC would be displayed while in numeric format only CSGID and CSG Associated PLMN MCC MNC would be displayed.

<stat>: integer type

0 unknown CSG

1 present in Allowed CSG list

2 present in Operator CSG list

3 forbidden (Reject cause #25 (Not Authorized for this CSG) has been received for the CSGID which is in Operator CSG List

<AcT>: integer type; access technology selected

0 UTRAN

1 E-UTRAN

Implementation

Optional.

This command is only applicable to UEs in UTRAN and E-UTRAN.

7.44 CAG selection +CCAGS

Table 7.44: +CCAGS parameter command syntax

Command	Possible response(s)
+CCAGS=[<mode>[,<format>[,<CAGinfo>[,<AcT>]]]]	+CCAGS: <AcT>
+CCAGS?	+CCAGS: <mode>[,<format>,<CAGinfo>[,<AcT>]]
+CCAGS=?	+CCAGS: [<stat>,<format>,<CAGinfo>,<AcT> [<CR><LF>+CCAGS:<stat>,<format>,<CAGinfo>,<AcT> […]]] [<CR><LF>+CCAGS:(list of supported <mode>s),(list of supported <format>s)]

Description

Set command triggers the MT to select and register on a CAG cell. <mode> is used to determine whether the selection is done automatically by the MT or is done in manual selection mode on the CAG cell identified by <CAGinfo> (which shall be given in format <format>) to a certain access technology, indicated in <AcT>. If the selected CAG cell is not available, then the MT shall follow the procedures described in 3GPP TS 23.122 clause 4.4.3.1.2. The selected CAG info format shall apply to further read commands (+CCAGS?) also. <mode>=0 forces an attempt to register to the CAG cell in NR/5GS network. <mode>=1 forces an attempt to do manual CAG selection to a CAG cell as per information in CAGinfo <CAGinfo>

This command is used when the ME has successfully registered to a PLMN i.e. the UE executed Operator Selection (+COPS) command successfully.

Read command returns the current CAG selection mode, the currently selected CAG cell information <CAGinfo> and the current Access Technology. If the ME is not camped on a CAG cell when read command is issued, +CME ERROR: XX (Not camped on CAG cell) shall be issued.

Test command returns a set of four parameters. A set consists of an integer indicating whether the CAG-ID is present in the "Allowed CAG list" <stat>, HRNN, CAG ID and Associated PLMN MCC MNC<CAGinfo>, numeric format representation of the CAG ID and Associated PLMN MCC MNC <CAGinfo> and access technology <AcT>. <CAGinfo> consist of HRNN, CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells, each delimited by a comma. See 3GPP TS 23.003 [7] for details of HRNN and CAG ID representation. Any of the formats may be unavailable and should then be an empty field.

It is recommended (although optional) that after the CAG list TA returns lists of supported <mode>s and <format>s. These lists shall be delimited from the CAG list by two commas.

Defined values

<mode>: integer type

0 automatic CAG selection mode (<CAGinfo> field is ignored)

1 manual CAG selection mode (<CAGinfo> field shall be present, and <AcT> optionally)

<format>: integer type

0 alphanumeric <CAGinfo>

1 numeric <CAGinfo>

<CAGinfo>: string type; <format> indicates if the format is alphanumeric or numeric

CAGinfo consists of HRNN, CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells, each delimited by a comma and in this particular order only. If HRNN is unavailable, it shall be an empty field. When selecting the CAG using the set command with <mode> as 1, the CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells are mandatory while the HRNN is optional.

In the alphanumeric format HRNN, CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells would be displayed while in numeric format only CAG ID, Associated PLMN MCC MNC and an indication of whether the MT is only allowed to access the Associated PLMN in 5GS via CAG cells would be displayed.

<stat>: integer type

0 The available CAG cell broadcasting the CAG-ID for the PLMN also broadcasts that the PLMN allows a user to manually select the CAG-ID

1 Present in "Allowed CAG list"

<AcT>: integer type; access technology selected

0 NR

Implementation

Optional.

This command is only applicable to UEs in NG-RAN.

7.45 Informative examples

This clause includes all the GSM/UMTS supplementary service related commands, additional commands to lock MT and SIM/UICC capabilities, and commands to check the network registration status.

An example where MSISDNs of a MT are queried, calls are forwarded to different numbers when mobile is busy (CFB) or when it does not answer (CFNRy). The status of CFNRy is read:

AT+CNUM

+CNUM: ,"+358501234567",145,,4 (voice number)

AT+CCFC=1,1,"931123456" (enable CFB)

AT+CCFC=2,1,"921654321" (enable CFNRy)

AT+CCFC=1,2 (query CFNRy)

+CCFC: 1,7,"+35821654321",145,,,20 (forward after 20 seconds)

An example of Call Waiting (+CCWA), Call Related Supplementary Services (+CHLD), and Connected Line Identification Presentation (+COLP) usage:

AT+CCWA=1,1;+COLP=1 (enable call waiting and COLP result codes)

ATD9311234567; (originate a voice call)

+COLP: "+358311234567",145

…conversation…

+CCWA: "+358317654321",145 (another call is waiting)

AT+CHLD=2 (put first call on hold and answer the second one)

…conversation…

AT+CHLD=1 (release the second (active) call and recover the first (held) call)

ATH (release the first call)

Call barring supplementary services are combined in one command, Facility Lock (+CLCK), which is also used to restrict MT and SIM/UICC functionality Some of the facilities require a password when enabled or disabled. An additional command, Change Password (+CPWD), is defined for changing the password of different barring and restriction facilities. An example where locking status of outgoing international calls is interrogated and then barred, and the password of the SIM/UICC card lock (Personal Identity Number, PIN) is changed:

AT+CLCK="OI",2

+CLCK: 0,7

AT+CLCK="OI",1,"1234"

AT+CPWD="SC","4321","1234"

Operator Selection (+COPS) command is used for querying the status of all GSM/UMTS operators detected in the area, and switching between operators.

Following example illustrates a network selection sequence in Finland. Two operators are found, the status of Tele is unknown and Radiolinja is currently selected. Read command shows that automatic selection mode is on and that Radiolinja is selected. Then an attempt is made to access Tele, but it is denied (shown by +CME ERROR).

AT+COPS=?

+COPS: (2,"RADIOLINJA","RL","24405"),(0,"TELE","TELE","24491")

AT+COPS?

+COPS: 0,0,"RADIOLINJA"

AT+COPS=1,0,"TELE"

+CME ERROR: 3

When a terminal wanders between countries (i.e. networks), an application may follow this e.g. with the following scenario:

AT+CREG=1 (enable +CREG: <stat> unsolicited result code)

AT+CREG?

+CREG: 1,1 (MT is registered in home PLMN)

AT+COPS=3,2;+COPS?;+COPS=3,0;+COPS?

+COPS: 0,2,"24405" (get the country…

+COPS: 0,0,"RADIOLINJA" …and operator name)

…user wanders to another PLMN…

+CREG: 2 (deregistered, roaming ongoing)

+CREG: 5 (registered again, not home PLMN)

AT+COPS=3,2;+COPS?;+COPS=3,0;+COPS?

+COPS: 0,2,"24001" (get the country…

+COPS: 0,0,"TELIA MOBITEL" …and operator name)

…user loses connection, no other PLMNs around…

+CREG: 0

An example of eMLPP Supplementary Service usage for a ptp voice call:

ATD*752#+436644101453; (originate a voice call with the priority level 2, see for priority level definitions GSM 02.30)

OK (call setup was successful)