10.1.26 Define EPS quality of service +CGEQOS

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

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

Table 10.1.26-1: +CGEQOS parameter command syntax

Command	Possible Response(s)
+CGEQOS=<cid>[,<QCI>[,<DL_GBR>,<UL_GBR>[,<DL_MBR>,<UL_MBR>]]]	+CME ERROR: <err>
+CGEQOS?	[+CGEQOS: <cid>,<QCI>,[<DL_GBR>,<UL_GBR>],[<DL_MBR>,<UL_MBR>]] [<CR><LF>+CGEQOS: <cid>,<QCI>,[<DL_GBR>,<UL_GBR>],[<DL_MBR>,<UL_MBR>] […]]
+CGEQOS=?	+CGEQOS: (range of supported <cid>s),(list of supported <QCI>s),(list of supported <DL_GBR>s),(list of supported <UL_GBR>s),(list of supported <DL_MBR>s),(list of supported <UL_MBR>s)
NOTE: The syntax of the AT Set Command is corrected to make the parameter <cid> mandatory. Older versions of the specification had defined the parameter <cid> optional, however the UE behaviour was not defined.

Description

The set command allows the TE to specify the EPS Quality of Service parameters <cid>, <QCI>, [<DL_GBR> and <UL_GBR>] and [<DL_MBR> and <UL_MBR>] for a PDP context or Traffic Flows (see 3GPP TS 24.301 [83] and 3GPP TS 23.203 [85]). When in UMTS/GPRS the MT applies a mapping function to UTMS/GPRS Quality of Service. Refer clause 9.2 for possible <err> values.

A special form of the set command, +CGEQOS= <cid> causes the values for context number <cid> to become undefined.

The read command returns the current settings for each defined QoS.

The test command returns the ranges of the supported parameters as compound values.

Defined values

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

<QCI>: integer type; specifies a class of EPS QoS (see 3GPP TS 23.203 [85] and 3GPP TS 24.301 [83]).

0 QCI is selected by network

[1 – 4] value range for guaranteed bit rate Traffic Flows

[71 – 76] value range for guaranteed bit rate Traffic Flows

[82 – 85] value range for guaranteed bit rate Traffic Flows

[5 – 10] value range for non-guaranteed bit rate Traffic Flows

79, 80 value for non-guaranteed bit rate Traffic Flows

[128 – 254] value range for Operator-specific QCIs

The QCI values 65, 66, 67, 69 and 70 are not allowed to be requested by the UE. If the TE requests a QCI parameter 65, 66, 67, 69 or 70, the MT responds with result code +CME ERROR: 181 (unsupported QCI value).

The QCI value of 10 can be requested by the UE only when in satellite E-UTRAN access. If the TE requests a QCI value 10 over another access, the MT responds with result code +CME ERROR: 181 (unsupported QCI value).

<DL_GBR>: integer type; indicates DL GBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]).

<UL_GBR>: integer type; indicates UL GBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]).

<DL_MBR>: integer type; indicates DL MBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]).

<UL_MBR>: integer type; indicates UL MBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a non-GBR QCI (see 3GPP TS 24.301 [83]).

Implementation

Optional.