179606351 qos management eran3!0!02 pdf

QoS Management eRAN3.0

Feature Parameter Description

Issue 02

Date 2013-05-16

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/

mailto:[email protected]

eRAN

QoS Management Contents

02 (2013-05-16) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

Contents

1 Introduction ................................................................................................................................ 1-1

1.1 Scope ............................................................................................................................................ 1-1

1.2 Intended Audience......................................................................................................................... 1-1

1.3 Change History .............................................................................................................................. 1-1

2 Overview of QoS Management .............................................................................................. 2-1

3 Basic Principles ........................................................................................................................ 3-1

3.1 EPS Bearer Architecture ............................................................................................................... 3-1

3.2 Bearer-Level QoS Parameters ...................................................................................................... 3-2

3.3 eNodeB QoS Management Mechanism ....................................................................................... 3-3

4 QoS Management Policies ..................................................................................................... 4-1

4.1 QoS Guarantees for a Single Subscriber ...................................................................................... 4-1

4.1.1 Service Setup Request Phase ............................................................................................. 4-1

4.1.2 Post-Service-Setup Phase ................................................................................................... 4-1

4.2 Differentiated Services for Multiple Subscribers ........................................................................... 4-2

4.2.1 Principles of Differentiated Services ..................................................................................... 4-2

4.2.2 Implementation of Differentiated Services ............................................................................ 4-3

5 QoS Management Methods .................................................................................................... 5-1

5.1 ARP-based QoS Management ...................................................................................................... 5-1

5.2 QCI-based QoS Management ....................................................................................................... 5-1

5.2.1 Standardized and Extended QCIs ........................................................................................ 5-1

5.2.2 QCI-Related Parameter Setting ........................................................................................... 5-2

5.3 GBR-/MBR-based QoS Management ........................................................................................... 5-4

5.4 AMBR-based QoS Management ................................................................................................... 5-4

6 Related Feature ......................................................................................................................... 6-1

6.1 Required Features......................................................................................................................... 6-1

6.2 Mutually Exclusive Features ......................................................................................................... 6-1

6.3 Affected Features .......................................................................................................................... 6-1

7 Impact on the Network............................................................................................................. 7-1

7.1 Impact on System Capacity........................................................................................................... 7-1

7.2 Impact on Network Performance ................................................................................................... 7-1

8 Engineering Guidelines ........................................................................................................... 8-1

8.1 When to Use QCI-based QoS Management ................................................................................. 8-1

8.2 Information to be Collected ........................................................................................................... 8-1

8.3 Network Planning .......................................................................................................................... 8-1

8.4 Overall Deployment Procedure ..................................................................................................... 8-1

8.5 Deploying QCI-based QoS Management ..................................................................................... 8-1

8.5.1 Deployment Procedure ......................................................................................................... 8-1

eRAN

QoS Management Contents



ii

8.5.2 Deployment Requirements ................................................................................................... 8-1

8.5.3 Data Preparation................................................................................................................... 8-1

8.5.4 Precautions ........................................................................................................................... 8-8

8.5.5 Hardware Adjustment ........................................................................................................... 8-8

8.5.6 Initial Configuration ............................................................................................................... 8-8

8.5.7 Activation Observation ........................................................................................................ 8-15

8.5.8 Reconfiguration .................................................................................................................. 8-20

8.5.9 Deactivation ........................................................................................................................ 8-20

8.6 Performance Optimization ........................................................................................................... 8-20

8.7 Troubleshooting ........................................................................................................................... 8-20

8.7.1 Fault Description ................................................................................................................. 8-20

8.7.2 Fault Handling .................................................................................................................... 8-20

9 Parameters.................................................................................................................................. 9-1

10 Counters.................................................................................................................................. 10-1

11 Glossary .................................................................................................................................. 11-1

12 Reference Documents ......................................................................................................... 12-1

eRAN

QoS Management 1 Introduction



1-1

1 Introduction

1.1 Scope

This document describes the key techniques of and engineering guidelines for the quality of service (QoS) management feature.

Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to the software release delivered with this document. In the event of updates, the updates will be described in the product documentation delivered with the latest software release.

In this document, E-UTRAN NodeB (eNodeB) refers to the BTS3202E.

1.2 Intended Audience

This document is intended for:

Personnel who need to understand QoS management

Personnel who work with Huawei Long Term Evolution (LTE) products

1.3 Change History

This section provides information about the changes in different document versions.

There are two types of changes, which are defined as follows:

Feature change: refers to a change in the QoS management feature of a specific product version.

Editorial change: refers to a change in wording or the addition of information that was not described in the earlier version.

Document Issues

The document issues are as follows:

02 (2013-05-16)

01 (2013-04-12)

Draft B (2013-02-08)

Draft A (2012-06-29)

02 (2013-05-16)

This is the official release.

Compared with 01 (2013-04-12) of eRAN3.0, 02 (2013-05-16) of eRAN3.0 incorporates no changes.

Change Type Change Description Parameter Change

Feature change

None. None.

Editorial change

Revided some descriptions in section “8.5.7 Activation Observation”.

None.

eRAN

QoS Management 1 Introduction



1-2

01 (2013-04-12)

This is the official release.

Compared with Draft B (2013-02-08) of eRAN3.0, 01 (2013-04-12) of eRAN3.0 incorporates no changes.

Draft B (2013-02-08)

Compared with Draft A (2012-06-29) of eRAN3.0, Draft B (2013-02-08) of eRAN3.0 includes the following changes.

Change Type Change Description Parameter Change

Feature change None None

Editorial change Optimized the description. None

Draft A (2012-06-29)

This is a draft.

eRAN

QoS Management 2 Overview of QoS Management



2-1

2 Overview of QoS Management

QoS of an Evolved Packet System (EPS) defines the comprehensive service capability of the EPS and determines the customers' satisfaction with services provided by operators. Therefore, QoS is a key indicator as to the performance of the EPS. An EPS includes an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and an Evolved Packet Core (EPC).

QoS management is a mechanism that helps an EPS meet service quality requirements. QoS management requires coordination among all the network elements (NEs) involved from service initiation to service response.

Figure 2-1 shows an EPS network.

Figure 2-1 EPS network

AF: application function eNodeB: E-UTRAN NodeB

HSS: home subscriber server MME: mobility management entity

PCRF: policy and charging rules function P-GW: packet data network gateway

S-GW: serving gateway UE: user equipment

QoS management is performed on EPS bearers. The NEs involved in QoS management are described as follows:

The PCRF determines the QoS parameters of a service data flow (SDF) and the associated traffic flow template (TFT). The PCRF then sends them to the S-GW/P-GW.

The S-GW/P-GW identifies an SDF according to the TFT and binds the SDF to an available EPS bearer or sets up a new EPS bearer for the SDF based on the QoS parameters.

The MME obtains UE subscription data from the HSS and transfers the QoS parameters among the NEs.

The HSS stores UE subscription data and subscriber information.

The eNodeB admits UE bearers and schedules UE data based on the QoS parameter settings and the status of radio resources and transport resources. The eNodeB uses differentiated resource management and allocation policies to meet the QoS requirements of UE bearers.

For details about EPS bearers in QoS management, see 3GPP TS 36.300.

eRAN

QoS Management 3 Basic Principles



3-1

3 Basic Principles

3.1 EPS Bearer Architecture

In the EPS, the basic unit for QoS management is an EPS bearer. The same QoS management policies are applied to SDFs on the same EPS bearer. These policies include a scheduling policy and a radio bearer policy. To provide different QoS management policies for different SDFs, these SDFs must be mapped to different EPS bearers.

Figure 3-1 shows the EPS bearer architecture defined in 3GPP specifications.

Figure 3-1 EPS bearer architecture

The end-to-end bearers in the EPS are divided by layer. An EPS bearer carries one or more SDFs and transfers corresponding packets between the UE and the P-GW.

EPS bearers can be divided into GBR bearers and non-GBR bearers.

Table 3-1 EPS bearer type (I)

Bearer Type Description

GBR bearer A GBR bearer is permanently allocated dedicated network resources to guarantee the GBR. For details, see 3GPP TS 36.300.

Non-GBR bearer A non-GBR bearer is not permanently allocated dedicated network resources.

EPS bearers can also be divided into the default bearer and dedicated bearers.

eRAN




3-2

Table 3-2 EPS bearer type (II)

Bearer Type Description

Default bearer A default bearer is allocated by the EPC to a UE when the UE initially accesses the EPS. The default bearer remains established to ensure a short delay for the UE to start a service and provide the UE with always-on IP connectivity.

The default bearer is a non-GBR bearer.

Dedicated bearer

A dedicated bearer is set up for a UE if the default bearer cannot meet the QoS requirements.

A dedicated bearer can generally meet the requirements for more stringent QoS than the default bearer.

A dedicated bearer can be a GBR or non-GBR bearer.

3.2 Bearer-Level QoS Parameters

The EPS provides various packet services such as videophones, audio, video, web browsing, and email. Subscriber requirements vary according to the service type. For example, subscribers demand clear voice, smooth video, and fast web browsing. The EPS maps these requirements to QoS parameters, which can be recognized and processed by each NE. Table 3-3 describes the QoS parameters of EPS bearers.

Table 3-3 QoS parameters of EPS bearers

QoS Parameter Description

QCI 3GPP specifications define nine QoS class identifiers (QCIs) for different services based on QoS requirements. These QCIs standardize QoS requirements. Each QCI specifies a set of requirements for the priority, delay, and packet loss rate of a resource type. QCIs are transmitted between network nodes, without requiring negotiation and large-scale transmission of QoS parameters. The EPS implements QoS management policies based on the QCIs.

SDFs with different QCIs are mapped to different EPS bearers.

ARP An allocation/retention priority (ARP) is the priority of an EPS bearer during resource allocation. Based on the ARP, the eNodeB decides whether to accept or reject a bearer establishment or modification request when resources are insufficient. In addition, the eNodeB uses the ARP to determine which bearers will be released during network congestion.

GBR and MBR A GBR is the bit rate that is guaranteed to a GBR bearer, and a maximum bit rate (MBR) is the maximum bit rate provided for a GBR bearer.

The GBR and MBR are used for managing the bandwidths of GBR bearers. The EPS admits all SDFs at bit rates equal to or lower than the GBR by reserving resources and rejects all SDFs at bit rates higher than the MBR. If the bit rates of SDFs are higher than the GBR but lower than the MBR, the EPS rejects the SDFs when the network is congested or admits the SDFs when the network is not congested.

The MBR and GBR for a GBR bearer are the same in the current version.

eRAN




3-3

QoS Parameter Description

UE-AMBR or APN-AMBR

An Aggregate Maximum Bit Rate (AMBR) is used by the EPS to limit the total bit rate of a group of non-GBR bearers within the AMBR. AMBRs are categorized as follows:

UE-AMBR: per UE aggregate maximum bit rate. Bandwidth management based on UE-AMBR limits the total bit rates used by all the non-GBR bearers created by a UE.

APN-AMBR: per APN aggregate maximum bit rate. Bandwidth management based on APN-AMBR limits the total bit rates of all the non-GBR bearers created by a UE under an access point name (APN).

The relationships between these parameters and bearers are as follows:

QCI and ARP are GBR and non-GBR bearer parameters.

GBR and MBR are GBR bearer parameters. GBR bearers (including dedicated GBR bearers) are used to carry real-time services such as voice, video, and real-time gaming services.

AMBR is an attribute of non-GBR bearers. Non-GBR bearers are used to carry non-real-time services such as emails, File Transfer Protocol (FTP) services, and Hypertext Transfer Protocol (HTTP) services. If other EPS bearers are not carrying any data, any non-GBR bearer can use up the AMBR. The P-GW or UE implement the APN-AMBR. The eNodeB implements the UE-AMBR.

Table 3-4 lists the QoS parameters of the NEs.

Table 3-4 QoS parameters of the NEs

QoS Parameter QCI ARP GBR MBR UE-AMBR APN-AMBR

HSS Yes Yes No No Yes Yes

P-GW Yes Yes Yes Yes No Yes

eNodeB Yes Yes Yes Yes Yes No

UE Yes No Yes Yes No Yes

3.3 eNodeB QoS Management Mechanism

When a UE subscribes to the network, subscription data is saved on the HSS. When the UE requests a service, the PCRF determines the QoS parameters based on the QoS commitments contained in the subscription data and transmits the QoS parameters to the S-GW/P-GW and eNodeB. The S-GW/P-GW and eNodeB provide services for the UE based on these QoS parameters.

Figure 3-2 shows the eNodeB QoS management mechanism.

eRAN




3-4

Figure 3-2 eNodeB QoS management mechanism

RRM: radio resource management TRM: transport resource management

The eNodeB QoS management mechanism is implemented as follows:

1. The EPC transmits the QoS parameters related to a service to the eNodeB over the S1 interface.

2. The eNodeB maps the received QoS parameters to internal parameters used in the eNodeB.

3. Based on the QoS parameters, the eNodeB manages and allocates resources such as radio resources and transport resources, providing differentiated services (DiffServ) to subscribers.

eRAN

QoS Management 4 QoS Management Policies



4-1

4 QoS Management Policies

eNodeB QoS management helps provide services of committed quality for a single subscriber and provides DiffServ for multiple subscribers.

eNodeB QoS management uses the following policies:

For a single subscriber: radio bearer control, power control, and handover are performed from the initial service setup to ensure service quality and continuity.

For multiple subscribers in a cell: load control, scheduling, and flow control on S1/X2 interfaces coordinate resources among subscribers to provide DiffServ and maximize system capacity.

4.1 QoS Guarantees for a Single Subscriber

QoS management provides QoS guarantees for a single subscriber by using a variety of functions. These functions provide the basic service quality for the subscriber by binding the service to an appropriate radio bearer and setting associated parameters. In addition, these functions ensure service continuity by monitoring link quality during UE movements.

QoS management provides QoS guarantees for an entire service process are implemented during the service setup request phase and post-service-setup phase.

4.1.1 Service Setup Request Phase

The service setup request phase requires bearer selection, initial power control, and admission control functions based on the availability of cell resources.

When a subscriber requests a service setup, the eNodeB selects the appropriate parameters related to, for example, the radio bearer, initial power control, and transport resource configuration based on service parameters such as the QCI, GBR, and MBR. This function ensures correct data transmission. For details about radio bearers, initial power control, and transport resource configuration, see Connection Management Feature Parameter Description, Power Control Feature Parameter Description, and Transport Resource Management Feature Parameter Description, respectively.

Admission control in each cell prevents an excessive number of subscribers from accessing the cell and ensures that the cell is not overloaded. During admission control, the eNodeB monitors the current cell loads and estimates the increase in load due to adding a new service, to decide whether the cell will be overloaded if the service is admitted. Admission control helps ensure the quality of admitted services and expected quality of the new service. If the new service is rejected because of the cell loads, admission control will attempt another cell at a different frequency in the same coverage area. For details about admission control on the radio interface, see Admission and Congestion Control Feature Parameter Description. For details about admission control in the transport network, see Transport Resource Management Feature Parameter Description.

4.1.2 Post-Service-Setup Phase

Power Control

After a service is set up, power control limits the transmit power for the service within an appropriate range. This function ensures correct data reception and improves power efficiency. For details about power control, see Power Control Feature Parameter Description.

Mobility Management

Service quality may deteriorate when the subscriber moves to a cell edge. By using the handover function, the eNodeB promptly triggers a handover to enable the UE to be served by another cell and

eRAN




4-2

ensure service continuity. For details about handover, see Mobility Management in Connected Mode Feature Parameter Description.

Scheduling

Scheduling helps ensure basic quality for services. For example, scheduling ensures acceptable transmission delay for data packets of delay-sensitive voice over IP (VoIP) services, and ensures the service rate and packet delay budget (PDB) delay for GBR services. Scheduling also ensures that the rates of FTP services are not lower than min_GBR, which are throughput-sensitive services. For details about scheduling and min_GRB, see Scheduling Feature Parameter Description.

Load Balancing

Load balancing distributes loads between neighboring cells to allow UEs in a high-load cell to move to a low-load cell, maximizing resource usage. For details about load balancing, see MLB Feature Parameter Description.

Congestion Control

Cells become congested when cell loads increase to high levels. To solve this problem, congestion control is used to control the cell load, ensuring the overall QoS satisfaction and system stability. For details about congestion control, see Admission and Congestion Control Feature Parameter Description and Transport Resource Management Feature Parameter Description.

4.2 Differentiated Services for Multiple Subscribers

Differentiated services (DiffServ) aim to serve more subscribers with limited system resources.

4.2.1 Principles of Differentiated Services

DiffServ is provided to services based on service priorities. High-priority services are preferentially scheduled. For example, gold services are more easily admitted than bronze services.

DiffServ is also provided to services based on service types. During scheduling of radio resources and transport resources, delay-sensitive services are more easily admitted than throughput-sensitive services. For example, VoIP services take priority over FTP services.

The following parameters are used to achieve DiffServ:

Service priority

Services in the network have different priorities, which are specified by the ARPs contained in the subscription data in the EPC. The eNodeB maps ARPs to service priorities, which are divided into gold, silver, and bronze. Based on these priorities, admission control and congestion control are performed.

Scheduling priority

Scheduling priority factors can be configured for QCIs on the eNodeB and be used to adjust the scheduling priorities of services with different QCIs.

Extended QCI

The EPS allows operators to define their own extended QCIs. Services of the same type can be mapped to different extended QCIs, and each extended QCI is mapped to a service class. Based on extended QCIs, operators can meet the service quality requirements for different service classes.

eRAN




4-3

4.2.2 Implementation of Differentiated Services

Service Setup Request Phase

Admission control in this phase ensures DiffServ based on service priorities. High-priority services have looser admission criteria than low-priority services, ensuring a higher admission success rate for high-priority services.

If a high-priority service fails to be admitted to a cell, admission control can preempt resources of low-priority services to increase the admission success rate for high-priority services.

Emergency services have the highest priority during admission, ensuring a highest admission success rate.

For details about DiffServ during the service setup request phase, see Admission and Congestion Control Feature Parameter Description and Transport Resource Management Feature Parameter Description.

Post-Service-Setup Phase

If the network is congested, the eNodeB releases resources of some admitted services, excluding emergency services. This mechanism reduces cell loads to maintain system stability or reserve resources for new services. Low-priority services are usually selected first for resource release.

For details about congestion control, see Admission and Congestion Control Feature Parameter Description and Transport Resource Management Feature Parameter Description.

eRAN

QoS Management 5 QoS Management Methods



5-1

5 QoS Management Methods

5.1 ARP-based QoS Management

ARP-based QoS management address the issue in traditional packet services that allowed different types of subscribers to equally use resources, which meant that these traditional services could not fully meet the requirements of high-priority subscribers.

ARP-based QoS management provides DiffServ by using admission and congestion control based on service priority information contained in subscription data.

During the setup of an E-UTRAN radio access bearer (E-RAB), the EPC transmits an ARP (which includes subscription data) to the eNodeB. The eNodeB then maps the ARP to a service priority (gold, silver, or bronze). The mapping between ARPs and service priorities can be set by CellRacThd.GoldServiceArpThd (ARP threshold for gold services) or CellRacThd.SilverServiceArpThd (ARP threshold for silver services). If the mapping is not specified by either parameter, the ARP is mapped to a bronze service. A larger ARP value indicates a lower priority.

Next, the eNodeB determines load control policies for services based on ARPs or service priorities. For example, different admission thresholds are set for gold, silver, and bronze services for admission control; different resource release thresholds are set for gold, silver, and bronze services for congestion control. For details, see Admission and Congestion Control Feature Parameter Description.

5.2 QCI-based QoS Management

5.2.1 Standardized and Extended QCIs

This section describes LBFD-002032 Extended-QCI.

3GPP specifications define standardized QCIs 1 to 9 for different service types, indicating the corresponding service quality requirements and service priorities. Table 5-1 describes these QCIs.

The standardized QCIs differentiate service types, but not subscriber classes. Therefore, using only these QCIs is not enough to provide different services for different subscribers.

To solve this problem, 3GPP specifications introduce extended QCIs 10 to 254, enabling operators to define their own QCIs. Extended QCIs defined by Huawei are used to provide only different non-GBR services for different subscribers.

Table 5-1 Examples of standardized QCIs and extended QCIs

Type QCI Value

Priority Packet Delay Budget (PDB)

Packet Loss Rate

Example Service

3GPP-defined QCIs for GBR services

1 2 100 ms 10-2

Conversational voice

2 4 150 ms 10-3

Conversational video

3 3 50 ms 10-3

Real-time gaming

4 5 300 ms 10-6

Streaming (non-conversational video)

3GPP-defined QCIs for non-GBR services

5 1 100 ms 10-6

IP Multimedia Subsystem (IMS) signaling

6 6 300 ms 10-6

Video (buffered streaming) and Transmission Control Protocol (TCP)-based services such as web

eRAN




5-2

Type QCI Value

Priority Packet Delay Budget (PDB)

Packet Loss Rate

Example Service

browsing, email, chatting, FTP, P2P file sharing, and progressive video

7 7 100 ms 10-3

Voice, video (live streaming), and interactive gaming

8 8 300 ms 10-6

Video (buffered streaming) and TCP-based services such as web browsing, email, chatting, FTP, P2P file sharing, and progressive video

9 9

Operator-defined QCIs

130 N/A IMS and voice-related signaling (gold)

131 N/A Gaming and other low-delay services (gold)

… … …

… … …

150 N/A IMS and voice-related signaling (silver)

151 N/A Gaming and other low-delay services (silver)

… … …

… … …

170 N/A IMS and voice-related signaling (bronze)

171 N/A Gaming and other low-delay services (bronze)

… … …

… … …

5.2.2 QCI-Related Parameter Setting

Standardized QCIs and extended QCIs are sent by the MME to the eNodeB. The eNodeB then performs QoS management based on these QCIs.

Operators can set radio bearer parameters and transmission parameters on the eNodeB for QCIs. Radio bearer parameters include RLC-related parameters, PDCP-related parameters, media access control (MAC) scheduling parameters, and handover parameters.

To set the QCIs, operators can run the following commands:

MOD STANDARDQCI and MOD CELLSTANDARDQCI: used to modify parameters related to standardized QCIs

ADD EXTENDEDQCI and ADD CELLEXTENDEDQCI: used to set parameters related to extended QCIs

eRAN




5-3

Operators can define their own extended QCIs in an EPS. Each of standardized QCIs 5 to 9 can be extended to multiple QCIs that correspond to different subscriber classes. Operators can provide different QoS policies for different classes of subscribers when these subscribers use the same service. As a result, high-priority users are preferentially admitted to cells, allocated resources, and scheduled for services. In addition, operators can provide different services for different service types.

Extended QCIs are defined by operators and need to be negotiated between the EPC and the E-UTRAN to ensure consistent QoS policies.

Radio Bearer Parameter Setting

The eNodeB configures QoS parameters and sets up radio bearers based on QCIs, enabling radio bearers to meet QoS requirements for different service types. The parameters in the RlcPdcpParaGroup MO can be set by running the ADD RLCPDCPPARAGROUP command. Standardized and extended QCIs can be set by referring to RlcPdcpParaGroup.RlcPdcpParaGroupId in the RlcPdcpParaGroup MO. MO stands for managed object.

Scheduling Parameter Setting

The eNodeB provides different scheduling services on radio interfaces based on their QCIs. During scheduling, the eNodeB categorizes data packets into different priority queues based on the QCIs, and preferentially schedules data packets in a high-priority queue. For example, the eNodeB schedules downlink data packets as follows:

The eNodeB considers the packet delay budget (PDB) of a GBR service. If the duration that a GBR data packet is buffered on the eNodeB is closer to the PDB, this data packet has a higher scheduling priority.

The eNodeB guarantees the GBR of a GBR service and the min_GBR of a non-GBR service during scheduling.

The eNodeB allocates available resources for non-GBR services based on service weights and ensures that the total AMBR of all the non-GBR services of a UE is lower than the UE-AMBR, which is sent by the EPC to the eNodeB.

For details about scheduling, see Scheduling Feature Parameter Description.

Handover Parameter Setting

The eNodeB can configure different handover parameters and policies for different service types based on the QCIs of these services. This function meets the key requirements for mobility, coverage continuity, and call drop rates. In addition, this function helps perform handover promptly, improve UE data transmission performance before the handover, decrease the number of UE measurements, reduce the number of handovers, and lower the probability of ping-pong handovers.

For details about handover, see Mobility Management in Connected Mode Feature Parameter Description.

Transmission Parameter Setting

The eNodeB transmits S1/X2 interface data through an IP network. QoS management in the IP network classifies services and defines QoS requirements based on differentiated services code points (DSCPs). QoS management uses per-hop behavior (PHB) policies such as resource allocation, queue scheduling, and packet discarding policies. All the network nodes comply with PHB policies according to the DSCP in the IP packet. The IP network specifies PHB policies for IP packets based on DSCPs. A larger DSCP value indicates a higher DSCP priority.

The eNodeB maps QCIs to DSCPs and specifies DSCPs for uplink IP packets. Performing these actions enables eNodeB interface boards to differentiate service data packets transmitted over an eNodeB interface board. The EPC maps QCIs to DSCPs and sets the DSCPs of downlink IP packets.

eRAN




5-4

For details about transport resource management (TRM), see Transport Resource Management Feature Parameter Description.

5.3 GBR-/MBR-based QoS Management

QoS management for GBR services is based on GBR and MBR, whereas QoS management for non-GBR services is not based on GBR or MBR.

The GBR and MBR are sent by the EPC to the eNodeB. The eNodeB then manages the bandwidth for GBR services based on the GBR.

The eNodeB accepts or rejects the admission request of a GBR service based on the GBR QoS satisfaction level, PRB admission policy, and ARP. During uplink and downlink scheduling, the eNodeB must preferentially meet the data rate and delay requirements of GBR services.

The eNodeB does not ensure the data rates and PDBs of non-GBR services. Operators, however, can set the StandardQci.UlMinGbr, ExtendedQci.UlMinGbr, StandardQci.DlMinGbr and ExtendedQci.DlMinGbr parameters on the eNodeB to satisfy the downlink min_GBR for non-GBR services. This prevents non-GBR services from starvation. Currently, the eNodeB does not ensure that the uplink min-GBR is satisfied because UEs support PBR. For details, see Scheduling Feature Parameter Description.

5.4 AMBR-based QoS Management

The UE and P-GW ensure that the total bit rate of all the non-GBR bearers created by a UE under an APN does not exceed the APN-AMBR. The eNodeB ensures that the total bit rate of all the non-GBR bearers created by a UE does not exceed the UE-AMBR.

The eNodeB limits the data rates of non-GBR services based on the UE-AMBR at the transport layer. If the buffer time at the transport layer is longer than the congestion time threshold RSCGRPALG.CTTH, the data packets arriving at the transport layer are not transmitted. If the number of buffered queues at the transport layer is greater than the threshold for the number of lost packets RSCGRPALG.DROPPKTNUM, the data packets arriving at the transport layer are discarded.

The eNodeB preferentially schedules UEs whose bit rates have not reached the UE-AMBR.

eRAN

QoS Management 6 Related Feature



6-1

6 Related Feature

6.1 Required Features

The end-to-end QoS management requires the following E-UTRAN features:

LBFD-002023 Admission Control

LBFD-002024 Congestion Control

LBFD-002016 Dynamic Downlink Power Allocation

LBFD-002026 Uplink Power Control

LOFD-001015 Enhanced Scheduling

LBFD-002018 Mobility Management

LBFD-003002 Basic Qos Management

LOFD-001032 Intra-LTE Load Balancing

LOFD-003011 Enhanced Transmission QoS Management

LOFD-003012 IP Performance Monitoring

6.2 Mutually Exclusive Features

None

6.3 Affected Features

None

eRAN

QoS Management 7 Impact on the Network



7-1

7 Impact on the Network

7.1 Impact on System Capacity

The E-UTRAN QoS features have the following impact on system capacity:

The admission control and congestion control algorithms satisfy the QoS requirements of admitted UEs and maximize system capacity in both the radio access network and the transport network.

Uplink scheduling and uplink power control ensure uplink coverage, minimize uplink interference, and maximize uplink capacity.

Downlink scheduling and downlink power control ensure downlink coverage and maximize downlink capacity.

Intra-LTE load balancing balances inter-cell loads and maximizes the system load.

7.2 Impact on Network Performance

The E-UTRAN QoS features have the following impact on network performance:

Inappropriate admission control and congestion control increase the service drop rate and decrease the access success rate in both the radio access network and the transport network.

Uplink and downlink scheduling features affect the cell throughput, and the throughput and QoS satisfaction level of cell-edge UEs.

Uplink and downlink power control features affect the cell throughput.

Mobility-related features affect the service drop rate and handover success rate. During handovers, the QoS requirements of services must be satisfied, and at the same time the service drop rate and handover success rate must be maintained.

eRAN

QoS Management 8 Engineering Guidelines



8-1

8 Engineering Guidelines

QoS management for the E-UTRAN is achieved through features such as scheduling, power control, load control, mobility management, load balancing, and transport resource management. QoS management can take effect only after these features are enabled. This chapter provides engineering guidelines for configuring QCIs. For engineering guidelines for these features, see their parameter description documents.

8.1 When to Use QCI-based QoS Management

To provide service quality based on only service types, operators can deploy QoS management based on standardized QCIs. The standardized QCIs are the basis for QoS management and are automatically created.

To provide service quality based on both service types and service priorities, operators need to deploy QoS management based on extended QCIs. One service type can be mapped to multiple extended QCIs, and each of these QCIs corresponds to a service priority. Extended QCIs need to be manually configured, and relevant parameters need to be planned.

8.2 Information to be Collected

None

8.3 Network Planning

None

8.4 Overall Deployment Procedure

None

8.5 Deploying QCI-based QoS Management

8.5.1 Deployment Procedure

None

8.5.2 Deployment Requirements

Requirements for the Operating Environment

Extended QCIs are defined by operators. NEs in the EPS must negotiate extended QCIs for consistent QoS policies.

Requirements for Transmission Networking

None

Requirement for Licenses

None

8.5.3 Data Preparation

This section describes generic data and scenario-specific data to be collected. Generic data is necessary for all scenarios and must always be collected. Scenario-specific data is collected only when necessary for a specific scenario.

eRAN




8-2

There are three types of data sources:

Network plan (negotiation required): Parameters are planned by operators and negotiated with the EPC or peer transmission equipment.

Network plan (negotiation not required): Parameters are planned and set by operators.

User-defined: Parameters are set as required by users.

eNodeB-Level QCIs

Standardized QCIs

The following table describes the parameters that must be set in a StandardQci MO to configure a standardized QCI.

Parameter Name Parameter ID Source Setting Description

QoS Class Indication

StandardQci.Qci Network planning (negotiation not required)

By default, standardized QCIs 1 to 9 are supported, and manual configuration is not necessary.

Ulsch priority factor

StandardQci.UlschPriorityFactor

Network planning (negotiation not required)

Set this parameter based on the network plan. Retain its default value unless there are special requirements. This parameter applies to QCIs 6 to 9.

Dlsch priority factor

StandardQci.DlschPriorityFactor



Downlink MinGBR StandardQci.DlMinGbr Network planning (negotiation not required)


Pre-allocation weight

StandardQci.PreAllocationWeight



InterRAT policy config group ID

StandardQci.InterRatPolicyCfgGroupId


Set this parameter based on the network plan. Retain its default value unless there are special requirements.

RLC PDCP parameter group ID

StandardQci.RlcPdcpParaGroupId



eRAN




8-3


Logical channel priority

StandardQci.LogicalChannelPriority



Flow Control Type StandardQci.FLOWCTRLTYPE



Extended QCIs

The following table describes the parameters that must be set in an ExtendedQci MO to configure an extended QCI. This MO needs to be added or removed manually. Parameters related to the extended QCI can be customized.


Extended QoS Class Identifier

ExtendedQci.ExtendedQci


Set this parameter based on the network plan. Extended QCIs are used by operators to differentiate between users. Extended QCIs are numbered from 10 to 254, depending on operators' plans.

Service type ExtendedQci.ServiceType


Set this parameter based on the network plan.

Uplink scheduling priority factor

ExtendedQci.UlschPriorityFactor



Downlink scheduling priority factor

ExtendedQci.DlschPriorityFactor



Downlink MinGBR ExtendedQci.DlMinGbr



Pre-allocation weight

ExtendedQci.PreAllocationWeight



InterRAT policy config group ID

ExtendedQci.InterRatPolicyCfgGroupId



eRAN




8-4


Prioritised bit rate ExtendedQci.PrioritisedBitRate



Logical channel priority

ExtendedQci.LogicalChannelPriority




ExtendedQci.RlcPdcpParaGroupId



Free user flag ExtendedQci.FreeUserFlag



Flow Control Type ExtendedQci.FLOWCTRLTYPE



Transmission Parameter Groups for Extended User Data Types

The following table describes the parameters that must be set in an EXTUDTPARAGRP MO to configure a transmission parameter group for extended user data types. This MO is used to support gold-, silver-, and bronze-level services.


Extern User Data Type Transfer Parameter Group ID.

EXTUDTPARAGRP.EXTUDTPARAGRPID



Priority EXTUDTPARAGRP.PRI


Set this parameter based on the network plan. This parameter specifies a DSCP value for extended QCIs.

Act Factor EXTUDTPARAGRP.ACTFACTOR



Primary Transport Resource Type

EXTUDTPARAGRP.PRIMTRANRSCTYPE



eRAN




8-5


Primary Port Load Threshold

EXTUDTPARAGRP.PRIMPTLOADTH



Primary To Secondary Port Load Ratio Threshold

EXTUDTPARAGRP.PRIM2SECPTLOADRATH



Extended User Data Types

The following table describes the parameters that must be set in an EXTUDT MO to add an extended user data type and bind it to a transmission parameter group.


User Data Type Number

EXTUDT.EXTUDTNO



Extern User Data Type Transfer Parameter Group ID.

EXTUDT.EXTUDTPARAGRPID



Cell-Level QCIs

Cell-Level Standardized QCIs

The following table describes the parameters that must be set in a CellStandardQci MO to configure a standardized QCI for a cell. These parameters include DRX, SRI, and handover parameters. Retain the default values of the other parameters unless the network plan requires different values.


Local cell identity CellStandardQci.LocalCellId


When a cell is added, standardized QCI configuration is automatically generated, requiring no manual operation.

QoS Class Indication CellStandardQci.Qci


When a cell is added, standardized QCI configuration is automatically generated, requiring no manual operation.

Interfreq handover group ID

CellStandardQci.InterFreqHoGroupId


When a cell is added, standardized QCI configuration is

eRAN




8-6


InterRAT handover to CDMA20001xRTT group ID

CellStandardQci.InterRatHoCdma1xRttGroupId


automatically generated. If the value of this parameter needs to be changed, refer to the network plan.

InterRAT handover to CDMA2000HRPD group ID

CellStandardQci.InterRatHoCdmaHrpdGroupId


InterRAT handover common group ID

CellStandardQci.InterRatHoCommGroupId


InterRAT handover to GERAN group ID

CellStandardQci.InterRatHoGeranGroupId


InterRAT handover to UTRAN Group ID

CellStandardQci.InterRatHoUtranGroupId


Intrafreq handover group ID

CellStandardQci.IntraFreqHoGroupId


DRX parameter group ID CellStandardQci.DrxParaGroupId


SRI Period CellStandardQci.SriPeriod


RLF timer and constants indication

CellStandardQci.RlfTimerConstCfgInd


RLF timer and constants group ID

CellStandardQci.RlfTimerConstGroupId


Cell-Level Extended QCIs

The following table describes the parameters that must be set in a CellExtendedQci MO to configure an extended QCI for a cell. These parameters include DRX, SRI, and handover parameters. Retain the default values of the other parameters unless the network plan requires different values.


Extended QCI CellExtendedQci.ExtendedQci



eRAN




8-7


Local cell identity CellExtendedQci.LocalCellId


Interfreq handover group ID

CellExtendedQci.InterFreqHoGroupId


InterRAT handover to CDMA20001xRTT group ID

CellExtendedQci.InterRatHoCdma1xRttGroupId


InterRAT handover to CDMA2000HRPD group ID

CellExtendedQci.InterRatHoCdmaHrpdGroupId


InterRAT handover common group ID

CellExtendedQci.InterRatHoCommGroupId


InterRAT handover to GERAN group ID

CellExtendedQci.InterRatHoGeranGroupId


InterRAT handover to UTRAN Group ID

CellExtendedQci.InterRatHoUtranGroupId


Intrafreq handover group ID

CellExtendedQci.IntraFreqHoGroupId


DRX parameter group ID CellExtendedQci.DrxParaGroupId


RLF timer and constants indication

CellExtendedQci.RlfTimerConstCfgInd


RLF timer and constants group ID

CellExtendedQci.RlfTimerConstGroupId


Operator-Level QCIs

Operator Information

For details about data to be collected for a CnOperator MO, see RAN Sharing Feature Parameter Description.

Operator-Level Extended QCIs

eRAN




8-8

The following table describes the parameters that must be set in a CnOperatorExtendedQci MO to configure an extended QCI for an operator. This MO need to be manually added or removed.


CN Operator ID CnOperatorExtendedQci.CnOperatorId



CN Operator extended QCI

CnOperatorExtendedQci.ExtendedQci



Service-based inter-RAT handover policy group ID

CnOperatorExtendedQci.ServiceIrHoCfgGroupId



8.5.4 Precautions

None

8.5.5 Hardware Adjustment

N/A

8.5.6 Initial Configuration

Configuring a Single eNodeB Using the GUI

Configure a single eNodeB using the Configuration Management Express (CME) graphical user interface (GUI) based on the collected data described in section 8.5.3 "Data Preparation." For details, see the procedure for configuring a single eNodeB on the CME GUI described in BTS3202E Initial Configuration Guide.

Configuring eNodeBs in Batches

To configure eNodeBs in batches, perform the following steps:

Step 1 Import a scenario-specific summary data file into the CME.

Step 2 If more parameters are required, customize these additional parameters in the summary data file by using the customization tool.

The parameters are described in section 8.5.3 "Data Preparation."

----End

The information about the file and all parameters involved is provided in this section, including:

Name of each recommended scenario-specific summary data file

Sheet where the parameters of an MO are customized in the summary data file

Name of the parameter group corresponding to the MO

Parameters in the group

eRAN




8-9

For descriptions of summary data files and the detailed procedure for configuring eNodeBs in batches, see BTS3202E Initial Configuration Guide.

eNodeB-Level QCIs

A user-defined data file is required. It is recommended that you customize the CME-provided file En_Basic and arrange the eNodeB-level QCI parameters in the MO on the New QoS Pattern sheet in this file. See the related data file to learn which MOs need to be modified. The following table provides a suggestion on distribution of MOs in the data file.

MO Sheet Parameter Group Name

Parameter Remarks

STANDARDQCI

QoS Pattern STANDARDQCI QoS Class Indication, Ulsch priority factor (0.001), Dlsch priority factor (0.001), Uplink MinGBR (KB/s), Downlink MinGBR (KB/s), Pre-allocation weight (0.1), InterRAT policy config group ID, RLC PDCP parameter group ID, Prioritised bit rate (KB/s), Logical channel priority(KB/s), Flow control type

It is recommended that the default values for parameters in this MO be retained. If you need to change their values, use the En_Basic data file.

EXTENDEDQCI

QoS Pattern EXTENDEDQCI Extended QoS Class Identifier, Service type, link scheduling priority factor (0.001), Downlink scheduling priority factor (0.001), Uplink MinGBR (KB/s), Downlink MinGBR (KB/s), Pre-allocation weight (0.1), InterRAT policy config group ID, Prioritised bit rate (KB/s), Logical channel priority, RLC PDCP parameter group ID, Free user flag, Flow control type

This MO needs to be configured only if extended QCIs are required.

EXTUDTPARAGRP

QoS EXTUDTPARAGRP

Extern User Data Type Transfer Parameter Group ID., Priority, Act Factor (%), Primary Transport Resource Type, Primary Port Load Threshold (%), Primary To Secondary Port Load Ratio Threshold (%), Flow Control Type


eRAN




8-10


Parameter Remarks

EXTUDT QoS EXTUDT User Data Type Number, Extern User Data Type Transfer Parameter Group ID.


INTERRATPOLICYCFGGROUP

QoS Pattern INTERRATPOLICYCFGGROUP

InterRAT policy config group ID, UTRAN handover policy Configuration, GERAN GSM handover policy Configuration, GERAN GPRS EDGE handover policy Configuration, CDMA2000 1XRTT handover policy Configuration, CDMA2000 HRPD handover policy Configuration, No handover flag, No fast ANR flag

By default, four policy configuration groups are available, numbered from 0 to 3. This default configuration is recommended. If you need to modify the existing or add new groups, use this MO.

RLCPDCPPARAGROUP

QoS Pattern RLCPDCPPARAGROUP


By default, RLC/PDCP parameter groups are configured. If you need to modify the existing or add new groups, use this MO.

DIFPRI Common Data

DIFPRI Priority Rule, Signaling Priority, OM High Priority, OM Low Priority, IPClock Priority, User Data 1 Priority, User Data 2 Priority, User Data 3 Priority, User Data 4 Priority, User Data 5 Priority, User Data 6 Priority, User Data 7 Priority, User Data 8 Priority, User Data 9 Priority

By default, one DIFPRI MO is configured. Retain the default values unless there are special requirements.

Cell-Level QCIs

A user-defined data file is required. It is recommended that you customize the CME-provided file En_Basic and arrange the cell-level QCI parameters in the MO on the New QoS Pattern sheet. See the related data file to learn which MOs need to be modified in the data file. The following table provides a suggestion on distribution of MOs in the data file.

eRAN




8-11


Parameter Remarks

CELLSTANDARDQCI

QoS Pattern CELLSTANDARDQCI

Local cell ID, QoS Class Indication, Interfreq handover group ID, InterRAT handover to CDMA20001xRTT group ID, InterRAT handover to CDMA2000HRPD group ID, InterRAT handover common group ID, InterRAT handover to GERAN group ID, InterRAT handover to UTRAN Group ID, Intrafreq handover group ID, DRX parameter group ID, SRI Period

When a cell is added, standardized QCI configuration is automatically generated, requiring no manual operation. This data file is used for modifying parameters.

CELLEXTENDEDQCI

QoS Pattern CELLEXTENDEDQCI

Extended QCI, Local cell ID, Interfreq handover group ID, InterRAT handover to CDMA20001xRTT group ID, InterRAT handover to CDMA2000HRPD group ID, InterRAT handover common group ID, InterRAT handover to GERAN group ID, InterRAT handover to UTRAN Group ID, Intrafreq handover group ID, DRX parameter group ID


INTRAFREQHOGROUP

QoS Pattern INTRAFREQHOGROUP

Local cell ID, Intrafreq handover group ID, Intrafreq handover hysteresis (0.5dB), Intrafreq handover offset (0.5dB), Intrafreq handover time to trigger (ms)

After a cell is added, an intra-frequency handover parameter group is automatically generated for the cell. If extra configuration is necessary, use this data file.

INTERFREQHOGROUP

QoS Pattern INTERFREQHOGROUP

Local cell ID, Interfreq handover group ID, Interfreq A1A2 hysteresis (0.5dB), Interfreq A1A2 time to trigger (ms), Interfreq A1 RSRP threshold (dBm), Interfreq A1 RSRQ threshold (0.5dB), Interfreq A2 RSRP threshold (dBm), Interfreq A2 RSRQ

After a cell is added, an inter-frequency handover parameter group is automatically generated for the cell. If extra configuration is

eRAN




8-12


Parameter Remarks

threshold (0.5dB), Interfreq handover hysteresis (0.5dB), CoverageBased Interfreq RSRP threshold (dBm), CoverageBased Interfrq RSRQ threshold (0.5dB), Interfreq HandOver Time to Trigger (ms), Load Based Interfreq RSRP threshold (dBm), Load Based Interfrq RSRQ threshold (0.5dB), Freq Priority Based Interfreq A1 RSRP threshold (dBm), Freq Priority Based Interfreq A1 RSRQ threshold (0.5dB), Interfreq A3 offset (0.5dB), A3 based interfreq A1 RSRP threshold (dBm), A3 based Interfreq A2 RSRP threshold (dBm), Freq Priority Based Interfreq A2 RSRP threshold(dBm), Fre Priority Based Interfreq A2 RSRQ threshold(0.5dB)

necessary, use this data file.

INTERRATHOCOMMGROUP

QoS Pattern INTERRATHOCOMMGROUP

Local cell ID, InterRAT handover common group ID, InterRAT A1A2 hysteresis (0.5dB), InterRAT A1A2 time to trigger (ms), InterRAT A1 RSRP trigger threshold (dBm), InterRAT A1 RSRQ trigger threshold (0.5dB), InterRAT A2 RSRP trigger threshold (dBm), InterRAT A2 RSRQ trigger threshold (0.5dB), Blind HO A2 Threshold Offset(1dB)

After a cell is added, a common inter-RAT handover parameter group is automatically generated for the cell. If extra configuration is necessary, use this data file.

eRAN




8-13


Parameter Remarks

DRXPARAGROUP

QoS Pattern DRXPARAGROUP

Local cell ID, DRX parameter group ID, Enter DRX Switch, On Duration Timer (subframe), DRX Inactivity Timer (subframe), DRX Retransmission Timer (subframe), Long DRX Cycle (subframe), Short-cycle DRX supported indication, Short DRX Cycle (subframe), DRX Short Cycle Timer

After a cell is added, four DRX parameter groups are automatically generated. If extra configuration is necessary, use this data file.

Operator-Level QCIs

For details about the CME-provided data file, see RAN Sharing Feature Parameter Description.

A user-defined data file is required for configuring operator-level QCIs. It is recommended that you customize the CME-provided file En_Basic and arrange the operator-level QCI parameters in the MO on the New QoS Pattern sheet. See the related data file to learn which MOs need to be modified in the data file. The following table provides a suggestion on distribution of MOs in the data file.


Parameter Remarks

CNOPERATORSTANDARDQCI

QoS Pattern CNOPERATORSTANDARDQCI

CN Operator ID, QoS Class Indication, Service-based inter-RAT handover policy group ID, Service-based inter-Freq handover policy group ID

This MO is automatically created or removed when a CnOperator MO is created or removed, respectively. If parameters in this MO need to be modified, use this data file.

CNOPERATOREXTENDEDQCI

QoS Pattern CNOPERATOREXTENDEDQCI

CN Operator ID, CN Operator extended QCI, Service-based inter-RAT handover policy group ID, Service-based inter-Freq handover policy group ID


eRAN




8-14


Parameter Remarks

SERVICEIRHOCFGGROUP

QoS Pattern SERVICEIRHOCFGGROUP

CN Operator ID, Service-based inter-RAT handover policy group ID, Inter-RAT handover state

One SERVICEIRHOCFGGROUP MO is automatically created when a CnOperator MO is created. If extra configuration is necessary, use this data file.

Configuring a Single eNodeB Using MML Commands

This section describes how to use MML commands to activate QoS management. You can use the CME-provided data file to modify the default parameter settings when the need arises.

eNodeB-Level QCIs

Only parameters in MOs related to extended QCIs need to be configured. Parameters in the standardized QCI MOs are configured by default. If extended QCIs are not used, skip the following procedure.

To add an extended eNodeB-level QCI and related parameters, perform the following steps:

Step 1 Run the ADD EXTENDEDQCI command to add an extended QCI.

Step 2 Run the ADD EXTUDTPARAGRP command to add a transmission parameter group for extended user data types.

Step 3 Run the ADD EXTUDT command to add an extended user data type.

--End

Cell-Level QCIs

Only parameters in MOs related to extended QCIs need to be configured. Parameters in the cell-level QCI MOs are configured by default. If extended QCIs are not used, skip the following operation.

To add an extended cell-level QCI, run the ADD CELLEXTENDEDQCI command.

Operator-Level QCIs

For details about how to configure a CnOperator MO using MML commands, see RAN Sharing Feature Parameter Description.

Only parameters in MOs related to extended QCIs need to be configured. Parameters in the operator-level QCI MOs are configured by default. If extended QCIs are not used, skip the following operation.

Step 1 To add an operator-level operator, run the ADD CNOPERATOR command.

Step 2 To add an extended QCI for an operator, run the ADD CNOPERATOREXTENDEDQCI command.

eRAN




8-15

--End

8.5.7 Activation Observation

For details about how to observe features such as power control, load control, transport resource management, mobility management, scheduling, and congestion control, see relevant feature parameter description documents.

This section describes how to verify whether QCIs have been correctly configured for established bearers.

Default Bearer(Standardized QCI)

Before you perform the observation, ensure that a standardized QCI (such as QCI9) has been configured on the HSS for the default bearer.

Verify the QoS parameter settings for a default bearer as follows:

Step 1 Start an S1 tracing task as follows:

On the M2000 client, choose Monitoring > Signaling Trace > Signaling Trace Management. In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Application Layer > S1 Interface Trace, and click New.

Step 2 A UE successfully accessed the cell and the QCI for the default bearer is 9.

Step 3 In the S1AP_INITIAL_CONTEXT_SETUP_REQ message, check the QCI of the bearer whose e-RAB-ID is 5. If the QCI is 9, the QoS parameter setting for the default bearer is correct, as shown in Figure 8-1.

Figure 8-1 Configuration example 1

----End

Dedicated Bearer (Standardized QCI)

Before you perform the observation, ensure that a dedicated bearing port has been configured on the core network side.

Verify the QoS parameter settings for a dedicated bearer as follows:

eRAN




8-16



Step 2 A UE successfully accessed the cell and a dedicated bearer with a QCI of 3 is established for the UE.

Step 3 In the S1AP_ERAB_SETUP_REQ message, check whether the QCI of the requested bearer is 3. If the QCI is 3, the QCI parameter setting is correct, as shown in Figure 8-2.


----End

Default Bearer (Extended QCI)

The following provides the procedure for verifying the extended QCI for a default bearer.

Before verifying the extended QCI, ensure that the unified service node (USN) and unified gateway (UGW) are configured with the license for extended QCIs, and that an extended QCI (such as QCI131) has been configured on the HSS for the default bearer.

If an operator does not plan to use extended QCIs, skip the following steps.




Step 2 A UE successfully accessed the cell and the extended QCI for the default bearer is 131.

Step 3 In the S1AP_INITIAL_CONTEXT_SETUP_REQ message, check the QCI of the bearer whose e-RAB-ID is 5. If the QCI is 131, the QoS parameter setting for the default bearer is correct, as shown in Figure 8-3.

eRAN




8-17


----End

Dedicated Bearer (Extended QCI)

The following provides the procedure for verifying the extended QCI for a default bearer.

Before verifying the extended QCI, ensure that the USN and UGW are configured with the license for extended QCIs, and that a dedicated bearing port has been configured on the core network side.

If an operator does not plan to use extended QCIs, skip the following steps.




Step 2 A UE successfully accessed the cell and the extended QCI for the dedicated bearer is 131.

In the S1AP_ERAB_SETUP_REQ message, check the QCI of the bearer whose e-RAB-ID is 6. If the QCI is 131, the QoS parameter setting for the dedicated bearer is correct, as shown in Figure 8-4.

eRAN




8-18


----End

EPS Bearer

Verify the QoS parameter settings for a default bearer and a dedicated bearer as follows:

Step 1 Set the AMBR to 180 Mbit/s, the ARP to 6, and the QCI to 9 for the default bearer of the UE.



Step 3 Enable the UE to access the cell.

Step 4 In the S1AP_INITIAL_CONTEXT_SETUP_REQ message, check the QCI and ARP of the bearer whose eRAB ID is 5 and uplink and downlink AMBRs are both 1.8 Mbit/s. If the QCI is 9 and the ARP is 6, the QoS parameter settings for the default bearer are correct, as shown in Figure 8-5.

eRAN




8-19


Step 5 Set up a dedicated bearer with an ARP of 1, an MBR of 2 Mbit/s, a GBR of 2 Mbit/s, and a QCI of 4. Verify the QoS parameter settings for the dedicated bearer as follows:

In the S1AP_ERAB_SETUP_REQ message, check whether the QoS parameter settings of the bearer whose eRAB ID is 6 are the same as configured, as shown in Figure 8-6.

eRAN




8-20


----End

8.5.8 Reconfiguration

None

8.5.9 Deactivation

None

8.6 Performance Optimization

None

8.7 Troubleshooting

8.7.1 Fault Description

After extended QCIs are configured, UEs cannot access the network or dedicated bearers fail to be set up for UEs.

8.7.2 Fault Handling

Perform the following steps to troubleshoot:

Step 1 On the eNodeB side, run the DSP S1INTERFACE command to check the status of the S1 interface.

eRAN




8-21

If… Then…

The status of the S1 interface is normal

Go to the next step.

The status of the S1 interface is abnormal

Troubleshoot according to the alarm handling suggestion. If the fault persists, contact the EPC administrator or Huawei technical support.

Step 2 On the UE side, check the access parameter settings.

If… Then…

The settings are consistent with the network plan


The settings are inconsistent with the network plan

Change these settings based on the network plan.

Step 3 On the eNodeB side, run the LST EXTENDEDQCI, LST EXTUDTPARAGRP, and LST EXTUDT commands to check the extended QCIs and related parameters.

If… Then…

The parameter settings are consistent


The parameter settings are inconsistent

Change parameters based on the network plan.

Step 4 Check the QCI-related subscription information and configuration on the EPC.

1. Ask EPC engineers to verify the QCI configuration in the subscription information on the HSS.

2. Ask EPC engineers to verify the step configuration and the QCI on the unified gateway (UGW).

If… Then…

The step configuration is correct and the QCI is on the mapping table


The step configuration is incorrect and the QCI is not on the mapping table

Reconfigure EPC parameters based on the network plan.

Step 5 If the problem persists, seek help from the EPC administrator or Huawei technical support.

----End

eRAN

QoS Management 9 Parameters



9-1

9 Parameters

Table 9-1 Parameter description

MO Parameter ID

MML Command

Feature ID Feature Name Description

EXTUDTPARAGRP

ACTFACTOR

ADD EXTUDTPARAGRP

MOD EXTUDTPARAGRP

LST EXTUDTPARAGRP

LBFD-002032

Extended-QCI Meaning:Indicates the activity factor of the services corresponding to an extended QCI.

GUI Value Range:0~100

Unit:%

Actual Value Range:0~100

Default Value:0

CnOperatorExtendedQci

CnOperatorId

ADD CNOPERATOREXTENDEDQCI

LST CNOPERATOREXTENDEDQCI

MOD CNOPERATOREXTENDEDQCI

RMV CNOPERATOREXTENDEDQCI

None None Meaning:Indicates the index of the operator.

GUI Value Range:0~5

Unit:None


Default Value:None

RSCGRPALG

CTTH SET RSCGRPALG

LST RSCGRPALG

LOFD-00301101

LOFD-00301102

LOFD-00301103

Transport Overbooking

Transport Differentiated Flow Control

Transport Resource Overload Control

Meaning:Indicates the congestion time threshold of a transmission resource group. When TCSW is set to ENABLE, if the buffer time of non-real-time service data in a transmission resource group exceeds the threshold, it indicates that the transmission resource group is congested and the backpressure signals are transmitted.

GUI Value

eRAN




9-2

MO Parameter ID

MML Command


Range:0~500

Unit:ms


Default Value:50

ExtendedQci

DlMinGbr ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

Basic Scheduling

Enhanced Scheduling

Meaning:Indicates the downlink minimum guaranteed bit rate of the non-GBR service.

GUI Value Range:MinGbrRate_0_KB(0KB/s), MinGbrRate_1_KB(1KB/s), MinGbrRate_2_KB(2KB/s), MinGbrRate_4KB(4KB/s), MinGbrRate_8_KB(8KB/s), MinGbrRate_16_KB(16KB/s), MinGbrRate_32_KB(32KB/s), MinGbrRate_64_KB(64KB/s), MinGbrRate_128_KB(128KB/s), MinGbrRate_256_KB(256KB/s), MinGbrRate_512_KB(512KB/s)

Unit:KB/s

Actual Value Range:MinGbrRate_0_KB, MinGbrRate_1_KB, MinGbrRate_2_KB, MinGbrRate_4KB, MinGbrRate_8_KB, MinGbrRate_16_KB, MinGbrRate_32_KB, MinGbrRate_64_KB, MinGbrRate_128_KB, MinGbrRate_256_KB, MinGbrRate_512_KB

eRAN




9-3

MO Parameter ID

MML Command


Default Value:MinGbrRate_1_KB(1KB/s)

StandardQci

DlMinGbr MOD STANDARDQCI

LST STANDARDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

LBFD-003002 / TDLBFD-003002

LOFD-00101502 / TDLOFD-00101502

LOFD-003011 / TDLOFD-003011

Basic Scheduling

Enhanced Scheduling

Basic Qos Management

Dynamic Scheduling

Enhanced Transmission QoS Management

Meaning:Indicates the downlink minimum guaranteed bit rate of the non-GBR service.


Unit:KB/s



eRAN




9-4

MO Parameter ID

MML Command


StandardQci

DlschPriorityFactor

MOD STANDARDQCI

LST STANDARDQCI

LOFD-001015 / TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

Enhanced Scheduling

Dynamic Scheduling

Meaning:Indicates the weight factor used in the calculation of connection priorities during downlink scheduling.


Unit:0.001

Actual Value Range:0.001~1, step:0.001

Default Value:700

ExtendedQci

DlschPriorityFactor

ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

LOFD-001015 / TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

Enhanced Scheduling

Dynamic Scheduling

Meaning:Indicates the weight factor used in the calculation of connection priorities during downlink scheduling.


Unit:0.001


Default Value:700

RSCGRPALG

DROPPKTNUM

SET RSCGRPALG

LST RSCGRPALG

LOFD-00301101

LOFD-00301102

LOFD-00301103




Meaning:Indicates the number threshold of discarded packets. This parameter indicates the capability of the queue in a transmission resource group to buffer packets. A greater parameter value indicates a stronger capability. If this parameter is set to 0, the queue in a transmission resource group cannot buffer packets, and thus all the delayed packets on the TX channel are

eRAN




9-5

MO Parameter ID

MML Command


discarded. The number threshold of discarded packets determines the maximum amount of data that can be buffered in a transmission resource group. The congestion time threshold of a transmission resource group determines the amount of data that is buffered when the transmission resource group is congested. Ensure that the maximum amount of data that can be buffered is not less than the amount of data that is buffered during congestion.


Unit:packet


Default Value:1000

CellStandardQci

DrxParaGroupId

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LBFD-002017 / TDLBFD-002017

DRX Meaning:Indicates the ID of a DRX parameter group.

GUI Value Range:0~9

Unit:None


Default Value:0

CellExtendedQci

DrxParaGroupId

ADD CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

LST

LBFD-002017 / TDLBFD-002017

DRX Meaning:Indicates the ID of a DRX parameter group.

GUI Value Range:0~9

Unit:None

Actual Value

eRAN




9-6

MO Parameter ID

MML Command


CELLEXTENDEDQCI

Range:0~9

Default Value:0

ExtendedQci

ExtendedQci

ADD EXTENDEDQCI

LST EXTENDEDQCI

MOD EXTENDEDQCI

RMV EXTENDEDQCI

LOFD-001015 / TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

Enhanced Scheduling

Dynamic Scheduling

Meaning:Indicates the extended QoS Class Identifier (QCI), which is required by the operator for user differentiation.


Unit:None


Default Value:None


ExtendedQci




RMV CNOPERATOREXTENDEDQCI

None None Meaning:Indicates the extended QoS Class Identifier (QCI), which is required by the operator for user differentiation.


Unit:None


Default Value:None

CellExtendedQci

ExtendedQci

ADD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

RMV CELLEXTENDEDQCI

LOFD-001015 / TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

Enhanced Scheduling

Dynamic Scheduling

Meaning:Indicates the extended QoS Class Identifier (QCI), which is required by the operator for service differentiation.


Unit:None


Default Value:None

eRAN




9-7

MO Parameter ID

MML Command


EXTUDT EXTUDTNO

ADD EXTUDT

MOD EXTUDT

RMV EXTUDT

LST EXTUDT

LBFD-002032

Extended-QCI Meaning:Indicates the number of the extension user data type.


Unit:None


Default Value:None

EXTUDTPARAGRP

EXTUDTPARAGRPID

ADD EXTUDTPARAGRP

LST EXTUDTPARAGRP

MOD EXTUDTPARAGRP

RMV EXTUDTPARAGRP

LBFD-002032

Extended-QCI Meaning:Indicates the ID of the transport parameter group related to the service that corresponds to the extended QCI. It uniquely identifies a transport parameter group.


Unit:None


Default Value:None

EXTUDT EXTUDTPARAGRPID

ADD EXTUDT

MOD EXTUDT

LST EXTUDT

LBFD-002032

Extended-QCI Meaning:Indicates the ID of the transport parameter group related to the services corresponding to an extended QCI.


Unit:None


Default Value:None

ExtendedQci

FlowCtrlType

ADD EXTENDEDQCI

MOD

LOFD-00301101 / TDLOFD-00301101



Meaning:Indicates whether to enable flow control for the QCI.

GUI Value

eRAN




9-8

MO Parameter ID

MML Command


EXTENDEDQCI

LST EXTENDEDQCI

LOFD-00301102 / TDLOFD-00301102

LOFD-00301103 / TDLOFD-00301103

LOFD-00301202 / TDLOFD-00301202

LOFD-003016 / TDLOFD-003016

LOFD-001032 / TDLOFD-001032

LOFD-003011 / TDLOFD-003011


Transport Dynamic Flow Control

Different Transport Paths based on QoS Grade

Intra-LTE Load Balancing


Range:FLOW_CTRL(Flow Control), NON_FLOW_CTRL(Non Flow Control)

Unit:None

Actual Value Range:FLOW_CTRL, NON_FLOW_CTRL

Default Value:FLOW_CTRL(Flow Control)

StandardQci

FlowCtrlType

MOD STANDARDQCI

LST STANDARDQCI

LOFD-00301101 / TDLOFD-00301101

LOFD-00301102 / TDLOFD-00301102

LOFD-00301103 / TDLOFD-00301103

LOFD-00301202 / TDLOFD-00301202

LOFD-003016 / TDLOFD-003016




Transport Dynamic Flow Control

Different Transport Paths based on QoS Grade

Intra-LTE Load Balancing

Meaning:Indicates whether to enable flow control for the QCI.

GUI Value Range:FLOW_CTRL(Flow Control), NON_FLOW_CTRL(Non Flow Control)

Unit:None

Actual Value Range:FLOW_CTRL, NON_FLOW_CTRL

Default Value:FLOW_CTRL(Flow Control)

eRAN




9-9

MO Parameter ID

MML Command


LOFD-001032 / TDLOFD-001032

ExtendedQci

FreeUserFlag

ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

Basic Scheduling

Enhanced Scheduling

Meaning:Indicates whether the extended QCI is specific to free users or paid users.

GUI Value Range:PAID_USER(Paid User), FREE_USER(Free User)

Unit:None

Actual Value Range:PAID_USER, FREE_USER

Default Value:PAID_USER(Paid User)

CellRacThd

GoldServiceArpThd

MOD CELLRACTHD

LST CELLRACTHD

LBFD-002023 / TDLBFD-002023

LBFD-002024 / TDLBFD-002024

LBFD-003002 / TDLBFD-003002

Admission Control

Congestion Control


Meaning:Indicates the Allocation and Retention Priority (ARP) threshold for the Golden-level services. A service is defined as a Golden-level service if its ARP value is smaller than or equal to this threshold. The service priority has a negative correlation with the ARP value.


Unit:None


Default Value:5

CellExtendedQci

InterFreqHoGroupId

ADD CELLEXTENDEDQCI

LBFD-00201802 / TDLBFD-002

Coverage Based Inter-frequency Handover

Meaning:Indicates the ID of a parameter group related to inter-frequency

eRAN




9-10

MO Parameter ID

MML Command


MOD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

01802 handover.

GUI Value Range:0~9

Unit:None


Default Value:0

CellStandardQci

InterFreqHoGroupId

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LBFD-00201802 / TDLBFD-00201802

Coverage Based Inter-frequency Handover

Meaning:Indicates the ID of a parameter group related to inter-frequency handovers.

GUI Value Range:0~9

Unit:None


Default Value:0

CellExtendedQci

InterRatHoCdma1xRttGroupId

ADD CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

LOFD-001021

PS Inter-RAT Mobility between E-UTRAN and CDMA2000

Meaning:Indicates the ID of a parameter group related to inter-RAT handover to CDMA2000 1xRTT.

GUI Value Range:0~9

Unit:None


Default Value:0

CellStandardQci

InterRatHoCdma1xRttGroupId

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LOFD-001021


Meaning:Indicates the ID of a parameter group related to inter-RAT handover to CDMA2000 1xRTT.

GUI Value Range:0~9

Unit:None


Default Value:0

eRAN




9-11

MO Parameter ID

MML Command


CellStandardQci

InterRatHoCdmaHrpdGroupId

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LOFD-001021


Meaning:Indicates the ID of a parameter group related to inter-RAT handover to CDMA2000 HRPD.

GUI Value Range:0~9

Unit:None


Default Value:0

CellExtendedQci

InterRatHoCdmaHrpdGroupId

ADD CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

LOFD-001021


Meaning:Indicates the ID of a parameter group related to inter-RAT handover to CDMA2000 HRPD.

GUI Value Range:0~9

Unit:None


Default Value:0

CellExtendedQci

InterRatHoCommGroupId

ADD CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

LOFD-001019 / TDLOFD-001019

LOFD-001020 / TDLOFD-001020

LOFD-001021

PS Inter-RAT Mobility between E-UTRAN and UTRAN

PS Inter-RAT Mobility between E-UTRAN and GERAN


Meaning:Indicates the ID of a group of common parameters related to inter-RAT handover.

GUI Value Range:0~9

Unit:None


Default Value:0

CellStandardQci

InterRatHoCommGroupId

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LOFD-001019 / TDLOFD-001019

LOFD-001020 / TDLOFD-001020



PS Inter-RAT Mobility between E-UTRAN and

Meaning:Indicates the ID of a common parameter group related to inter-RAT handover.

GUI Value Range:0~9

Unit:None

Actual Value

eRAN




9-12

MO Parameter ID

MML Command


LOFD-001021

CDMA2000 Range:0~9

Default Value:0

CellExtendedQci

InterRatHoGeranGroupId

ADD CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

LOFD-001020 / TDLOFD-001020


Meaning:Indicates the ID of a parameter group related to inter-RAT handover to GERAN.

GUI Value Range:0~9

Unit:None


Default Value:0

CellStandardQci

InterRatHoGeranGroupId

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LOFD-001020 / TDLOFD-001020


Meaning:Indicates the ID of a parameter group related to inter-RAT handover to GERAN.

GUI Value Range:0~9

Unit:None


Default Value:0

CellExtendedQci

InterRatHoUtranGroupId

ADD CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

LOFD-001019 / TDLOFD-001019


Meaning:Indicates the ID of a parameter group related to inter-RAT handover to UTRAN.

GUI Value Range:0~9

Unit:None


Default Value:0

CellStandardQci

InterRatHoUtranGroupId

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LOFD-001019 / TDLOFD-001019


Meaning:Indicates the ID of a parameter group related to inter-RAT handover to UTRAN.

GUI Value Range:0~9

Unit:None

Actual Value

eRAN




9-13

MO Parameter ID

MML Command


Range:0~9

Default Value:0

StandardQci

InterRatPolicyCfgGroupId

MOD STANDARDQCI

LST STANDARDQCI

LOFD-001019 / TDLOFD-001019

LOFD-001020 / TDLOFD-001020

LOFD-001021

LOFD-001022 / TDLOFD-001022

LOFD-001023 / TDLOFD-001023

LOFD-001043 / TDLOFD-001043

LOFD-001045 / TDLOFD-001045

LOFD-001044 / TDLOFD-001044

LOFD-001046 / TDLOFD-001046

LOFD-001033 / TDLOFD-001033

LOFD-001034 / TDLOFD-001




SRVCC to UTRAN

SRVCC to GERAN

Service based inter-RAT handover to UTRAN

Inter-RAT Load Sharing to GERAN

Inter-RAT Load Sharing to UTRAN

Service based inter-RAT handover to GERAN

CS Fallback to UTRAN

CS Fallback to GERAN

CS Fallback to CDMA2000 1xRTT

Meaning:Indicates the ID of a parameter group related to inter-RAT handover.


Unit:None


Default Value:0

eRAN




9-14

MO Parameter ID

MML Command


034

LOFD-001035

ExtendedQci

InterRatPolicyCfgGroupId

ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

LOFD-001019 / TDLOFD-001019

LOFD-001020 / TDLOFD-001020

LOFD-001021

LOFD-001022 / TDLOFD-001022

LOFD-001023 / TDLOFD-001023

LOFD-001043 / TDLOFD-001043

LOFD-001045 / TDLOFD-001045

LOFD-001044 / TDLOFD-001044

LOFD-001046 / TDLOFD-001046

LOFD-001033 / TDLOFD-001033

LOFD-001034 / TDLOFD-001




SRVCC to UTRAN

SRVCC to GERAN


Inter-RAT Load Sharing to GERAN

Inter-RAT Load Sharing to UTRAN


CS Fallback to UTRAN

CS Fallback to GERAN

CS Fallback to CDMA2000 1xRTT

Meaning:Indicates the group ID of the parameters related to the inter-RAT handover with the extended QCI.


Unit:None


Default Value:0

eRAN




9-15

MO Parameter ID

MML Command


034

LOFD-001035

CellStandardQci

IntraFreqHoGroupId

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LBFD-00201801 / TDLBFD-00201801

Coverage Based Intra-frequency Handover

Meaning:Indicates the ID of a parameter group related to intra-frequency handover.

GUI Value Range:0~9

Unit:None


Default Value:0

CellExtendedQci

IntraFreqHoGroupId

ADD CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

LBFD-00201801 / TDLBFD-00201801

Coverage Based Intra-frequency Handover

Meaning:Indicates the ID of a parameter group related to intra-frequency handover.

GUI Value Range:0~9

Unit:None


Default Value:0

CellExtendedQci

LocalCellId

ADD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

RMV CELLEXTENDEDQCI

LBFD-001001 / TDLBFD-001001

3GPP R8 Specifications Meaning:Indicates the local ID of the cell. It uniquely identifies a cell within a BS.

GUI Value Range:0

Unit:None

Actual Value Range:0

Default Value:None

CellStandardQci

LocalCellId

LST CELLSTANDARDQCI

LBFD-001001 / TDLBFD-001

3GPP R8 Specifications Meaning:Indicates the local ID of the cell. It uniquely identifies a

eRAN




9-16

MO Parameter ID

MML Command


MOD CELLSTANDARDQCI

001 cell within a BS.

GUI Value Range:0

Unit:None

Actual Value Range:0

Default Value:None

StandardQci

LogicalChannelPriority

MOD STANDARDQCI

LST STANDARDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

Basic Scheduling

Enhanced Scheduling

Meaning:Indicates the priority of the logical channel. The UE scheduler guarantees prioritized bit rates of logical channels in an ascending order of logical channel priorities. Resources are allocated in an ascending order of logical channel priorities after the prioritized bit rates of all services are guaranteed. For details, see 3GPP TS 36.321.


Unit:None


Default Value:11

ExtendedQci

LogicalChannelPriority

ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

Basic Scheduling

Enhanced Scheduling

Meaning:Indicates the priority of the logical channel. The UE scheduler guarantees prioritized bit rates of logical channels in descending order of logical channel priority. Resources are allocated in descending order of logical channel priority after the prioritized bit rates of all services are guaranteed. For details, see 3GPP TS 36.321.

eRAN




9-17

MO Parameter ID

MML Command



Unit:None


Default Value:11

StandardQci

PreAllocationWeight

MOD STANDARDQCI

LST STANDARDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

Basic Scheduling

Enhanced Scheduling

Dynamic Scheduling

Meaning:Indicates the pre-allocation weight. The pre-allocation weight of a UE is the pre-allocation weight of services carried by the highest-priority logical channel. If services carried by highest-priority logical channels have different pre-allocation weights, the UE takes the highest pre-allocation weight. When resources are insufficient, pre-allocation weights affect the pre-allocation probabilities of users. The pre-allocation probability has a positive correlation with the pre-allocation weight. This parameter is QCI-specific.


Unit:0.1

Actual Value Range:0~1, step:0.1

Default Value:10

ExtendedQci

PreAllocationWeight

ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST

LBFD-002025 / TDLBFD-002025

LOFD-001015 /

Basic Scheduling

Enhanced Scheduling

Meaning:Indicates the pre-allocation weight. The pre-allocation weight of a UE is the pre-allocation weight of services carried by the

eRAN




9-18

MO Parameter ID

MML Command


EXTENDEDQCI TDLOFD-001015

highest-priority logical channel. If services carried by highest-priority logical channels have different pre-allocation weights, the UE takes the highest pre-allocation weight. When resources are insufficient, pre-allocation weights affect the pre-allocation probabilities of users. The pre-allocation probability has a positive correlation with the pre-allocation weight. This parameter is QCI-specific.


Unit:0.1

Actual Value Range:0~1, step:0.1

Default Value:10

EXTUDTPARAGRP

PRI ADD EXTUDTPARAGRP

MOD EXTUDTPARAGRP

LST EXTUDTPARAGRP

LBFD-002032

Extended-QCI Meaning:Indicates the priority of the service data, which is identified by a DSCP value. The priority of the service data has a positive correlation with the DSCP value.


Unit:None


Default Value:None

EXTUDTPARAGRP

PRIM2SECPTLOADRATH

ADD EXTUDTPARAGRP

MOD EXTUDTPARA

LBFD-002032

Extended-QCI Meaning:Indicates the primary-to-secondary port load ratio threshold of user data in the hybrid transmission

eRAN




9-19

MO Parameter ID

MML Command


GRP

LST EXTUDTPARAGRP

scenario. A smaller value indicates that services are more likely to be admitted to the primary path.


Unit:%


Default Value:None

EXTUDTPARAGRP

PRIMPTLOADTH

ADD EXTUDTPARAGRP

MOD EXTUDTPARAGRP

LST EXTUDTPARAGRP

LBFD-002032

Extended-QCI Meaning:Indicates the primary port load threshold of the user data in the hybrid transmission scenario. A larger value indicates that services are more likely to be admitted to the primary path.


Unit:%


Default Value:None

EXTUDTPARAGRP

PRIMTRANRSCTYPE

ADD EXTUDTPARAGRP

MOD EXTUDTPARAGRP

LST EXTUDTPARAGRP

LBFD-002032

Extended-QCI Meaning:Indicates the type of primary transport resource used to transmit the user date when hybrid transmission is adopted. HQ indicates that high-quality transport resources are used, while LQ indicates that low-quality transport resources are used. When a new service requests admission and admission control is performed, one of the IP path routes with

eRAN




9-20

MO Parameter ID

MML Command


transport resources of the same quality is used as the primary transport path.

GUI Value Range:HQ(High Quality), LQ(Low Quality)

Unit:None

Actual Value Range:HQ, LQ

Default Value:None

ExtendedQci

PrioritisedBitRate

ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

Basic Scheduling

Enhanced Scheduling

Meaning:Indicates the prioritized bit rate of the logical channel. The UE scheduler guarantees prioritized bit rates of logical channels in descending order of logical channel priority. For details, see 3GPP TS 36.321.

GUI Value Range:PBR_0_KBps(0KB/s), PBR_8_KBps(8KB/s), PBR_16_KBps(16KB/s), PBR_32_KBps(32KB/s), PBR_64_KBps(64KB/s), PBR_128_KBps(128KB/s), PBR_256_KBps(256KB/s), PBR_INFINITY(Infinity)

Unit:KB/s

Actual Value Range:PBR_0_KBps, PBR_8_KBps, PBR_16_KBps, PBR_32_KBps, PBR_64_KBps, PBR_128_KBps, PBR_256_KBps,

eRAN




9-21

MO Parameter ID

MML Command


PBR_INFINITY

Default Value:PBR_8_KBps(8KB/s)

CellStandardQci

Qci LST CELLSTANDARDQCI

MOD CELLSTANDARDQCI

LOFD-001015 / TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

Enhanced Scheduling

Dynamic Scheduling

Meaning:Indicates the QoS class identifier (QCI) of an evolved packet system (EPS) bearer. Different QCIs indicate different QoS requirements, such as the packet delay budget, packet error loss rate, and resource type. For details, see Table 6.1.7 in 3GPP TS 23.203.

GUI Value Range:QCI1(QCI 1), QCI2(QCI 2), QCI3(QCI 3), QCI4(QCI 4), QCI5(QCI 5), QCI6(QCI 6), QCI7(QCI 7), QCI8(QCI 8), QCI9(QCI 9)

Unit:None

Actual Value Range:QCI1, QCI2, QCI3, QCI4, QCI5, QCI6, QCI7, QCI8, QCI9

Default Value:None

StandardQci

Qci LST STANDARDQCI

MOD STANDARDQCI

LOFD-001015 / TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

Enhanced Scheduling

Dynamic Scheduling

Meaning:Indicates the QoS Class Identifier (QCI) of an EPS bearer. Different QCIs represent different QoS specifications such as the packet delay budget, packet error loss rate, and resource type (whether the service is a GBR service or not). For

eRAN




9-22

MO Parameter ID

MML Command


details, see Table 6.1.7 in 3GPP TS 23.203.

GUI Value Range:QCI1(QCI 1), QCI2(QCI 2), QCI3(QCI 3), QCI4(QCI 4), QCI5(QCI 5), QCI6(QCI 6), QCI7(QCI 7), QCI8(QCI 8), QCI9(QCI 9)

Unit:None

Actual Value Range:QCI1, QCI2, QCI3, QCI4, QCI5, QCI6, QCI7, QCI8, QCI9

Default Value:None

RlcPdcpParaGroup

RlcPdcpParaGroupId

ADD RLCPDCPPARAGROUP

LST RLCPDCPPARAGROUP

MOD RLCPDCPPARAGROUP

RMV RLCPDCPPARAGROUP

LBFD-002008 / TDLBFD-002008

Radio Bearer Management

Meaning:Indicates the ID of the RLC/PDCP parameter group.


Unit:None


Default Value:None

StandardQci

RlcPdcpParaGroupId

MOD STANDARDQCI

LST STANDARDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

Basic Scheduling

Enhanced Scheduling

Meaning:Indicates the ID of an RLC/PDCP parameter group.


Unit:None


Default Value:0

ExtendedQ RlcPdcpParaGroupI

ADD LBFD-002008 /

Radio Bearer Meaning:Indicates the ID of an RLC/PDCP

eRAN




9-23

MO Parameter ID

MML Command


ci d EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

TDLBFD-002008

Management parameter group.


Unit:None


Default Value:5

CellStandardQci

RlfTimerConstCfgInd

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LBFD-002007

RRC Connection Management

Meaning:Indicates whether to config the parameters related to RLF timer and constants values.

GUI Value Range:NOT_CFG(NOT_CFG), CFG(CFG)

Unit:None

Actual Value Range:NOT_CFG, CFG

Default Value:NOT_CFG(NOT_CFG)

CellExtendedQci

RlfTimerConstCfgInd

ADD CELLEXTENDEDQCI

MOD CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

LBFD-002007


Meaning:Indicates whether to config the parameters related to RLF timer and constants values.

GUI Value Range:NOT_CFG(NOT_CFG), CFG(CFG)

Unit:None

Actual Value Range:NOT_CFG, CFG

Default Value:NOT_CFG(NOT_CFG)

CellExtendedQci

RlfTimerConstGroupId

ADD CELLEXTENDEDQCI

MOD

LBFD-002007


Meaning:Indicates the ID of the parameter group related to RLF timer and constants

eRAN




9-24

MO Parameter ID

MML Command


CELLEXTENDEDQCI

LST CELLEXTENDEDQCI

values.

GUI Value Range:0~9

Unit:None


Default Value:0

CellStandardQci

RlfTimerConstGroupId

MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LBFD-002007


Meaning:Indicates the ID of the parameter group related to RLF timer and constants values.

GUI Value Range:0~9

Unit:None


Default Value:0


ServiceIrHoCfgGroupId




LOFD-001043 / TDLOFD-001043

LOFD-001046 / TDLOFD-001046



Meaning:Indicates the ID of a service-based inter-RAT handover policy group.

GUI Value Range:0~9

Unit:None


Default Value:0

ExtendedQci

ServiceType

ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

LOFD-001015 / TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

Enhanced Scheduling

Dynamic Scheduling

Meaning:Indicates the service type corresponding to the extended QCI.

GUI Value Range:IMSSignalling(IMS Signalling), LowDelay(Low Delay), TCPorBuffStreaming(TCP Based or Buffered Streaming)

Unit:None

Actual Value

eRAN




9-25

MO Parameter ID

MML Command


Range:IMSSignalling, LowDelay, TCPorBuffStreaming

Default Value:TCPorBuffStreaming(TCP Based or Buffered Streaming)

CellRacThd

SilverServiceArpThd

MOD CELLRACTHD

LST CELLRACTHD

LBFD-002023 / TDLBFD-002023

LBFD-002024 / TDLBFD-002024

LBFD-003002 / TDLBFD-003002

Admission Control

Congestion Control


Meaning:Indicates the Allocation and Retention Priority (ARP) threshold for the Silver-level services. A service is defined as a Silver-level service if its ARP value is smaller than or equal to the value of this parameter and is larger than the value of GoldServiceArpThd. A service is defined as a Bronze-level service if its ARP value is larger than the value of this parameter. The service priority has a negative correlation with the ARP value.


Unit:None


Default Value:10

CellStandardQci

SriPeriod MOD CELLSTANDARDQCI

LST CELLSTANDARDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

LBFD-002003 / TDLBFD-002

Basic Scheduling

Enhanced Scheduling

Physical Channel Management

Meaning:Indicates the interval at which scheduling request indicators are sent.

GUI Value Range:ms5(SRI 5ms), ms10(SRI 10ms), ms20(SRI 20ms), ms40(SRI 40ms), ms80(SRI 80ms)

Unit:None

eRAN




9-26

MO Parameter ID

MML Command


003 Actual Value Range:ms5, ms10, ms20, ms40, ms80

Default Value:ms10(SRI 10ms)

ExtendedQci

UlMinGbr ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

Basic Scheduling

Enhanced Scheduling

Meaning:Indicates the uplink minimum guaranteed bit rate of the non-GBR service.


Unit:KB/s


Default Value:MinGbrRate_1_K

eRAN




9-27

MO Parameter ID

MML Command


B(1KB/s)

StandardQci

UlMinGbr MOD STANDARDQCI

LST STANDARDQCI

LBFD-002025 / TDLBFD-002025

LOFD-001015 / TDLOFD-001015

LBFD-003002 / TDLBFD-003002

LOFD-00101502 / TDLOFD-00101502

LOFD-003011 / TDLOFD-003011

Basic Scheduling

Enhanced Scheduling


Dynamic Scheduling


Meaning:Indicates the uplink minimum guaranteed bit rate of the non-GBR service.


Unit:KB/s



StandardQ UlschPriori MOD LOFD-001015 /

Enhanced Scheduling Meaning:Indicates the weight factor used

eRAN




9-28

MO Parameter ID

MML Command


ci tyFactor STANDARDQCI

LST STANDARDQCI

TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

LOFD-003011 / TDLOFD-003011

Dynamic Scheduling


in the calculation of connection priorities during uplink scheduling.


Unit:0.001


Default Value:700

ExtendedQci

UlschPriorityFactor

ADD EXTENDEDQCI

MOD EXTENDEDQCI

LST EXTENDEDQCI

LOFD-001015 / TDLOFD-001015

LOFD-00101502 / TDLOFD-00101502

LOFD-003011 / TDLOFD-003011

Enhanced Scheduling

Dynamic Scheduling


Meaning:Indicates the weight factor used in the calculation of connection priorities during uplink scheduling.


Unit:0.001


Default Value:700

eRAN

QoS Management 10 Counters



10-1

10 Counters

There are no specific counters associated with this feature.

eRAN

QoS Management 11 Glossary



11-1

11 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN

QoS Management 12 Reference Documents



12-1

12 Reference Documents

This chapter lists the reference documents related to QoS management.

[1] 3GPP TS 36.300 "Overall description"

[2] Connection Management Feature Parameter Description

[3] Admission and Congestion Control Feature Parameter Description

[4] MLB Feature Parameter Description

[5] Power Control Feature Parameter Description

[6] Transport Resource Management Feature Parameter Description

[7] Mobility Management in Connected Mode Feature Parameter Description

[8] Scheduling Feature Parameter Description

[9] RAN Sharing Feature Parameter Description

[10] BTS3202E Initial Configuration Guide

[11] BTS3202E MO Reference

179606351 qos management eran3!0!02 pdf

Documents

huawei trademarks

huawei proprietary

qos guarantees

qos management eran3

overview of qos management

qos management policies

eran qos management

huawei industrial base