Controlling
Process Related QCI on S6A
In Release 20.0,
MME has been enhanced to support new standardized QCIs 65, 66, 69 and 70. Also,
MME also supports operator specific (non-standard) QCIs from 128 to 254. The
non-standard QCIs provides Operator Specific QoS for M2M and other mission
critical communications.
The
operator-defined-qci command under the QoS profile
configuration is provisioned to enable or disable Operator Specific QCI. When
enabled, MME accepts Operator Specific QCI values (128-254) both from HSS and
PGW. If not enabled, MME will reject the procedure on receiving any Operator
Specific QCI value.
Additionally, this
chapter describes the mapping of operator specific QCIs to Pre-Release8 QoS
parameters during a handover to UTRAN/GERAN.
The Operator
Specific QCI Support feature is license controlled. Contact your Cisco Account
or Support representative for information on how to obtain a license.
The Operator
Specific QCI feature provides the following functionalities:
-
MME provides a
CLI to enable/disable 'operator-defined-qci' under QOS-Profile.
-
Operator
Specific QCI value ranges from 128 to 254.
-
The new
standardized QCI values 65, 66, 69 and 70 is accepted for configuration under
all existing CLIs that involves QCI.
-
QCI validation
is performed during configuration to avoid invalid values.
-
Existing QOS
control on all bearers is extended to the new QCIs values. A specific QCI or a
range of QCIs can be associated to a Bearer Control Profile under QoS-Profile.
An operator specific QCI can be re-mapped to another QCI using this Bearer
Control Profile. Bearer level parameters such as ARP, MBR, GBR values can be
configured independently for default/dedicated bearer along with action such as
prefer-as-cap or
pgw-upgrade in the Bearer Control Profile.
-
MME rejects the
default/dedicated bearers with QCIs that are configured to be rejected under
QoS-Profile.
-
MME provides
CLI configuration under the Bearer Control Profile to map Operator Specific QCI
to Pre-Release8 QoS parameters or a standard QCI.
-
The
standardized QCI mapping is defined according to the TS 23.401 3GPP
specification.
-
Every Standard
QCI GBR/Non-GBR is associated with a priority level as shown below:
QCI
|
Resource Type
|
Priority
|
1
|
GBR
|
2
|
2
|
GBR
|
4
|
3
|
GBR
|
3
|
4
|
GBR
|
5
|
5
|
Non-GBR
|
1
|
6
|
Non-GBR
|
6
|
7
|
Non-GBR
|
7
|
8
|
Non-GBR
|
8
|
9
|
Non-GBR
|
9
|
65
|
GBR
|
0.7
|
66
|
GBR
|
2
|
69
|
Non-GBR
|
0.5
|
70
|
Non-GBR
|
5.5
|
-
Priority
Level 1 has the highest priority and in case of congestion lowest priority
level traffic would be the first to be discarded.
-
The
operator specific QCIs from 128 to 254 shall have the lowest priority. These
priority values are considered while deriving resultant QoS values for the
Minimum and Reject-if-exceed actions configured in prefer-as-cap or pgw-upgrade
-
The
paging-map CLI is enhanced to accommodate QCI values - 65,
66, 69 and 70.
-
The
qci-reject CLI under QoS-Profile is modified to accept
Operator Specific QCI values.
Note |
MME supports
standardized QCIs from 1 to 9. It accepts the new standardized QCI values 69
and 70 for default bearer creation and 65, 66, 69 and 70 for dedicated bearer
creation. Any other QCI value is considered invalid.
|
Standardized
Non-GBR QCI values 69 and 70, and operator specific QCI values in the range 128
to 254 enabled using the
operator-defined-qci CLI under QoS-Profile is accepted from
the subscription (HSS). If the CLI is not enabled, MME will reject all Operator
Specific values.
Standardized QCI
values 65, 66, 69 and 70, and operator specific QCI values in the range 128 to
254 enabled using the
operator-defined-qci CLI under QoS-Profile is accepted from
the S-GW. If the CLI is not enabled, MME will reject all Operator Specific
values.
Note |
|
Mapping of
Operator Specific QCIs to Pre-Release8 QoS parameters is supported for
successful handover of bearers to UTRAN/GERAN during handoff
A new CLI is
implemented in MME to map standard or non-standardized QCI's to PreRelease8QoS
parameters so that the bearers are transferred during a handover to Gn-Gp SGSN.
The mapped QoS values would be sent in GTPv1 SGSN-Context-Response or
Forward-Relocation-Request messages to peer SGSN.
One of the
following values can be used to map EPC QoS from non-standard QCIs to 3GPP
pre-release8 QoS:
To support
mapping, a new CLI is added in the Bearer Control Profile Configuration Mode.
If this configuration is not available, MME uses background class values as
default, and maps the QCIs to the background class and its associated QoS
parameters.
The Non-Standard and Operator Specific QCI feature complies with the
following standards:
-
LTE; General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access (3GPP TS 23.401
version 12.8.0 Release 12).
-
LTE; Quality of Service (QoS) concept and architecture (3GPP TS
23.107 version 12.0.0 Release 12).
-
LTE; Policy and charging control architecture (3GPP TS 23.203
version 13.1.0).