> 11.7 | AT+CGEQMIN 3G Quality of Service Profile (Minimum acceptable)

> Syntax

> Test Command AT+CGEQMIN=?
> Response(s)
> +CGEQMIN: <PDP_type>, (list of supported <Traffic class>s), (list of supported <Maximum bitrate UL>s), (list of supported <Maximum bitrate DL>s), (list of supported <Guaranteed bitrate UL>s), (list of supported <Guaranteed bitrate DL>s), (list of supported <Delivery order>s), (list of supported <Maximum SDU size>s), (list of supported <SDU error ratio>s), (list of supported <Residual bit error ratio>s), (list of supported <Delivery of erroneous SDUs>s), (list of supported <Transfer delay>s), (list of supported <Traffic handling priority>s)
> OK

> Read Command AT+CGEQMIN?
> Response(s)
> [+CGEQMIN: <cid>, <Traffic class>, <Maximum bitrate UL>, <Maximum bitrate DL>, <Guaranteed bitrate UL>, <Guaranteed bitrate DL>, <Delivery order>, <Maximum SDU size>, <SDU error ratio>, <Residual bit error ratio>, <Delivery of erroneous SDUs>, <Transfer delay>, <Traffic handling priority>]
> [+CGEQMIN: ...]

> Write Command AT+CGEQMIN=[<cid>[, <Traffic class>[, <Maximum bitrate UL>[, <Maximum bitrate DL>[, <Guaranteed bitrate UL>[, <Guaranteed bitrate DL>[, <Delivery order>[, <Maximum SDU size>[, <SDU error ratio>[, <Residual bit error ratio>[, <Delivery of erroneous SDUs>[, <Transfer delay>[, <Traffic handling priority>]]]]]]]]]]]]]
> Response(s)
> OK
> ERROR
> +CME ERROR

> Reference(s) |  | PIN |  | ASC0 | ASC1 | USB | MUX1 | MUX2 | MUX3 |  |  | Charge | Q | Last
> 3GPP TS 27.007 |  | + |  | + | + | + | + | + | + |  |  | - | + | -

> Command Description
> The test command returns values supported as a compound value.
> The read command returns the current settings for each defined context.
> The write command allows the TE to specify a Quality of Service Profile for the context identified by the (local) context identification parameter <cid> which is checked by the MT against the negotiated profile returned in the Activate/Modify PDP Context Accept message.
> A special form of the write command, AT+CGEQMIN=<cid> causes the requested profile for context number <cid> to become undefined.
> AT&F and ATZ will undefine the QoS profiles of every context which is not active or not online.
> Parameter Description

> <cid>(num)

> Parameter specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands.
> 1...2

> <Traffic class>(num)

> 0
> conversational
> 1
> streaming
> 2
> interactive
> 3
> background
> [4]
> subscribed value

> <Maximum bitrate UL>(num)

> This parameter indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQMIN=...,32,...).
> [0]
> subscribed value
> 1...63
> 64...128
> (value needs to be divisible by 8 without remainder)
> 256
> 512

> <Maximum bitrate DL>(num)

> This parameter indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP. As an example a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQMIN=...,32,...).
> [0]
> subscribed value
> 1...63
> 64...256
> (value needs to be divisible by 8 without remainder)
> 512

> <Guaranteed bitrate UL>(num)

> This parameter indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQMIN=...,32,...).
> [0]
> subscribed value
> 1...63
> 64...128
> (value needs to be divisible by 8 without remainder)

> <Guaranteed bitrate DL>(num)

> This parameter indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as 32 (e.g. AT+CGEQMIN=...,32,...).
> [0]
> subscribed value
> 1...63
> 64...256
> (value needs to be divisible by 8 without remainder)

> <Delivery order>(num)

> This parameter indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not.
> 0
> no
> 1
> yes
> [2]
> subscribed value

> <Maximum SDU size>(num)

> This parameter indicates the maximum allowed SDU size in octets.
> [0]
> subscribed value
> 10...1520
> (value needs to be divisible by 10 without remainder)
> 1502

> <SDU error ratio>(str)

> This parameter indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU error ratio is defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error ratio of 5*10-3 would be specified as "5E3" (e.g. AT+CGEQMIN=...,"5E3",...).
> [“0E0“]
> subscribed value
> “1E2“
> “7E3“
> “1E3“
> “1E4“
> “1E5“
> “1E6“
> “1E1“

> <Residual bit error ratio>(str)

> This parameter indicates the target value for the undetected bit error ratio in the delivered SDUs. If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The value is specified as "mEe". As an example a target residual bit error ratio of 5*10-3 would be specified as "5E3" (e.g. AT+CGEQMIN=...,"5E3",...).
> [“0E0“]
> subscribed value
> “5E2“
> “1E2“
> “5E3“
> “4E3“
> “1E3“
> “1E4“
> “1E5“
> “1E6“
> “6E8“

> <Delivery of erroneous SDUs>(num)

> This parameter indicates whether SDUs detected as erroneous shall be delivered or not.
> 0
> no
> 1
> yes
> 2
> no detect
> [3]
> subscribed value

> <Transfer delay>(num)

> This parameter indicates the targeted time between request to transfer an SDU at one SAP to its delivery at the other SAP, in milliseconds.
> [0]
> subscribed value
> 10...150
> (value needs to be divisible by 10 without remainder)
> 200...950
> (value needs to be divisible by 50 without remainder)
> 1000...4000
> (value needs to be divisible by 100 without remainder)

> <Traffic handling priority>(num)

> This parameter specifies the relative importance for handling of all SDUs belonging to the UMTS bearer compared to the SDUs of the other bearers.
> [0]
> subscribed
> 1
> 2
> 3

> <PDP_type>(str)

> Packet Data Protocol Type
> “IP“
> Notes

> • | If parameters are not defined, the parameter default values depend on the HLR-stored subscribed default values.

> • | Definitions of parameters can be found in 3GPP TS 23.107