eLTE Broadband Access Solution

QoS Technical Guide

Issue V1.0

Date 2014-09-29

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd.2014. 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 a 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: support@huawei.com
 Contents

1 Overview ................................................................................................................................... 5
2 Introduction to QoS ................................................................................................................. 6
2.1 Basic QoS Concepts .............................................................................................................................................. 6
2.2 Application Scenarios ............................................................................................................................................ 6
2.3 QoS Parameters ..................................................................................................................................................... 7

3 QoS Principles .......................................................................................................................... 9

3.1 EPS QoS Architecture............................................................................................................................................ 9
3.1.1 QoS Parameter Determination ............................................................................................................................. 9
3.1.2 QoS Parameter Mapping in an EPS Network ......................................................................................................10
3.2 Delivery and Application of QoS Parameters.........................................................................................................12
3.2.1 Delivery and Application of QoS Parameters During Default Bearer Activation ..................................................12
3.2.2 Delivery and Application of QoS Parameters During Dedicated Bearer Activation ..............................................14
3.2.3 Delivery and Application of QoS Parameters During Bearer Modification ..........................................................15

4 QoS Functions of NEs ............................................................................................................ 17

4.1 QoS Functions of NEs in the EPC .........................................................................................................................17
4.1.1 QoS Functions Performed During Service Requests ...........................................................................................17
4.1.2 QoS Control After Service Setup ........................................................................................................................17
4.2 QoS Functions of the eNodeB ...............................................................................................................................18
4.2.1 QoS Functions Performed During Service Requests ...........................................................................................18
4.2.2 QoS Control After Service Setup ........................................................................................................................20
4.2.3 Service Preemption ............................................................................................................................................21
4.2.4 Congestion Control ............................................................................................................................................22

5 QoS Configuration for Typical Services ............................................................................. 25

5.1 QoS Configuration Principles ...............................................................................................................................25
5.1.1 Differentiation Between GBR Bearers and Non-GBR Bearers ............................................................................25
5.1.2 QoS Design for GBR Bearers.............................................................................................................................25
5.1.3 QoS Design for non-GBR Bearers......................................................................................................................26
5.2 QoS Design for the Combined Video and Voice Service ........................................................................................27
5.2.1 Data Flow Identification ....................................................................................................................................27
5.2.2 QoS Design Analysis .........................................................................................................................................28
5.2.3 EPS Bearer Planning..........................................................................................................................................29
 1 Overview

This document describes the EPS quality of service (QoS) architecture and basic QoS
concepts, including QoS parameters, parameter descriptions, and QoS functions supported by
each network element (NE). It focuses on the Huawei EPS QoS solution, including the
extended QoS class identifiers (QCIs), QoS mapping, and QoS monitoring supported by the
MME, P-GW, and eNodeB. This document also describes the QoS configuration principles
for typical services and provides a QoS design example for the combined video and voice
service.
 2 Introduction to QoS

2.1 Basic QoS Concepts

QoS defines a set of service requirements, which must be met to ensure an appropriate service
level for data transmission on the network. The service requirements are based on the
industrial standards for QoS functions. QoS enables real-time programs to fully use network
bandwidth resources. QoS can provide sufficient network resources for a specific guarantee
level and therefore it can provide a service level on a shared network similar to that on a
private network.
QoS guarantee means that devices transmit data at a specified rate in a specified period. The
objective of QoS is to set up a reliable transmission system for network communication.
On traditional IP-based networks, each forwarding node equally processes all packets. That is,
the forwarding nodes transmit packets to the destination using the "first-in, first-out" policy.
In this case, data packet transmission performance, such as reliability and transmission delay,
cannot be ensured. On an EPS network, different types of services have different network
performance requirements. Accordingly, the EPS network must provide different levels of
service quality to satisfy subscriber requirements. As the competition between carriers
(especially in winning high-end subscribers) becomes fierce, carriers must consider how to
better use network resources to provide differentiated services for subscribers and therefore
make more profits.
The essential dimensions for evaluating QoS are as follows:
 Bandwidth/throughput: the average traffic flow rate of a specific application between
two network nodes.
 Delay: the mean round-trip time of packet transmission between two network nodes.
 Jitter: the delay variance.
 Packet loss rate: the percentage of packets lost during transmission on the network. It is
used to indicate the capability of the network to correctly forward user data.

2.2 Application Scenarios

With the amount of radio resources unchanged, QoS solutions increase revenue for carriers
and ensure better user experience. Based on resource consumption by each subscriber, carriers
can formulate different charging policies and provide differentiated services. For example,
 carriers can divide subscribers into three levels: gold, silver, and bronze. When subscribers
compete for network resources, services of gold-level subscribers are preferentially provided.
Carriers also need to formulate different operation policies and charging policies for various
services. For example, videophone and common downloads are charged differently.
High-priority subscribers and special services are preferentially satisfied by using QoS
mechanisms. For common subscribers who are the majority, resources are allocated to
subscribers in good radio environments to increase the throughput of the entire system on the
basis that fairness is ensured to some extent. In this way, radio resources are more efficiently
used.
For an enterprise network, the number of service types is limited. However, the services of
each industry have characteristics specific to the industry. While one service may have a high
requirement for real-time performance, another service may involve a large amount of data.
The quality of these services must be ensured by using different QoS levels.

2.3 QoS Parameters

The EPS network uses the QoS solution described in 3GPP specifications Release 8. Simply,
this solution is called R8 QoS solution. On an EPS network, QoS is guaranteed on a per
bearer basis. The QoS can vary with bearers. A subscriber has one default bearer and multiple
dedicated EPS bearers.
The following describes R8 QoS parameters. On an EPS network, the following parameters
are used to define the QoS requirements of the service on a specific bearer.
QCI: indicates the QoS requirements, including the bearer type (GBR or non-GBR), delay,
and scheduling priority, that must be met during packet forwarding for a service on a specific
bearer. (GBR is short for guaranteed bit rate.) 3GPP specifications define nine QCIs (QCIs 1
to 9) and corresponding parameters. Table 2-1 lists the QCIs and corresponding parameters.

Table 2-1 QCIs 1 to 9

QCI Resource Priority Packet Packet Error Example Services

Type Delay Loss Rate
Budget

1 2 100 ms 1.00E-02 Conversational voice

Conversational video (Live

2 4 150 ms 1.00E-03
streaming)
GBR
3 3 50 ms 1.00E-03 Real-time gaming

Non-conversational video
4 5 300 ms 1.00E-06
(Buffered streaming)

5 1 100 ms 1.00E-06 IMS signaling

Non-GBR
Video (Buffered streaming),
6 6 300 ms 1.00E-06 TCP-based (for example, www,
e-mail, chat, ftp, p2p file sharing,
 progressive video.)

Voice, video (Live streaming),

7 7 100 ms 1.00E-03
interactive gaming

8 8 Video (Buffered streaming),

TCP-based (for example, www,
300 ms 1.00E-06
e-mail, chat, ftp, p2p file sharing,
9 9 progressive video.)

Allocation and Retention Priority (ARP): indicates the priority of a bearer activation or
modification request. When resources are insufficient, the ARP determines whether a bearer
can preempt the resources allocated to another bearer and whether the resources allocated to a
bearer can be preempted. Services with different ARPs use different bearers. ARPs are used
only in service admission control and congestion control. ARP involves the preemption
attribute and preemption capability. The preemption attribute indicates whether a service can
preempt resources allocated to other services and whether resources allocated to the service
can be preempted by other services. The preemption capability indicates the preemption
priority whose value range is 1 to 15. A smaller value indicates a higher priority.
GBR: indicates the bandwidth that can be guaranteed by a bearer. The GBR applies only to
GBR bearers.
Maximum bit rate (MBR): indicates the maximum bandwidth that can be provided by a bearer.
The MBR applies only to GBR bearers.
Per APN aggregate maximum bit rate (APN-AMBR): indicates the aggregate bit rate that can
be provided across all non-GBR bearers among all PDN connections of the same APN. It is
the maximum bandwidth of all bearers from a UE to the same P-GW. The UE and P-GW
enforce the APN-AMBR in the uplink. The P-GW enforces the APN-AMBR in the downlink.
Per UE aggregate maximum bit rate (UE-AMBR): indicates the aggregate bit rate that can be
provided across all non-GBR bearers of a UE. It is the maximum bandwidth of all bearers of a
UE. The eNodeB enforces the UE-AMBR in both the uplink and downlink.
 3 QoS Principles

3.1 EPS QoS Architecture

3.1.1 QoS Parameter Determination
Figure 3-1 EPS network architecture

Figure 3-1 shows a typical EPS network architecture defined in 3GPP specifications,
including the MME, S-GW, P-GW, policy and charging rules function (PCRF), and home
subscriber server (HSS). The MME supports signaling plane management. The S-GW
forwards user data and serves as a local mobility anchor. The P-GW also forwards user data
and serves as an entrance from the EPS network to the PDN.
The PCRF supports the determination of QoS and charging policies. The PCRF sends the QoS
and charging policies to the P-GW over the Gx interface. The P-GW supports the functions of
the policy and charging enforcement function (PCEF) entity and implements the QoS and
charging policies locally. The EPS supports the Policy and Charging Control (PCC) function
of Release 8 and defines QoS policies based on PCC rules. (For details about the PCC
function, see the 3GPP TS 23.203 V 10.06.00.)
As shown in Figure 3-1, an EPS network supports two QoS policy configuration modes:
  QoS policy delivery from the PCRF
 Local static QoS policy configuration in the P-GW
Currently, enterprise networks do not support the deployment of PCRF, and therefore only the
local static QoS policy configuration is supported.

3.1.2 QoS Parameter Mapping in an EPS Network

Figure 3-2 Bearers at different layers in an EPS network

Figure 3-2 shows bearers at different layers in an EPS network. The EPS maps the end-to-end
(E2E) QoS requirement layer by layer from the top down. The EPS service bearers can be
classified into the following three layers:
 E2E bearer
 EPS bearer
 Radio bearer, S1 bearer, and S5/S8 bearer
The radio bearer, S1 bearer, and S5/S8 bearer separately implement their QoS. In this way, the
QoS of the EPS bearer is implemented.
Figure 3-3 Mapping between bearers in an EPS network

An EPS bearer consists of the radio bearer, S1 bearer, and S5/S8 bearer with each bearer
controlling its QoS independently. The mapping between the bearers shown in Figure 3-3 is
described as follows:
 The UE uses the local UL-TFT to classify uplink data flows and transmits them over the
corresponding radio bearers. (TFT is short for traffic flow template.)
 The P-GW uses the local DL-TFT to classify downlink data flows and transmits them
over the corresponding S5/S8 bearers.
 The eNodeB and S-GW forwards data based on the one-to-one mapping relationships
between the radio bearer, S1 bearer, and S5/S8 bearer.
The QoS parameters vary with bearers. The UE, eNodeB, S-GW, and P-GW ensure the
service quality of a bearer based on QoS parameters to differentiate bearer service quality
from end to end.
A UE has one default bearer and multiple dedicated bearers.
 The default bearer is activated when the UE attaches to the network and it can carry only
non-GBR services. QoS parameters for the default bearer are defined in the HSS and can
also be pre-configured in the PCRF or P-GW. The QoS parameters are delivered to each
involved NE during the default bearer activation. For details about the procedure, see
section 3.2.1 "Delivery and Application of QoS Parameters During Default Bearer
Activation".
 A dedicated bearer is activated when the UE initiates a service request. A dedicated
bearer can carry both GBR and non-GBR services. QoS parameters for dedicated bearers
are configured in the PCRF or P-GW and are delivered to each involved NE during the
dedicated bearer activation. The dedicated bearer activation procedure for GBR services
and that for non-GBR services are the same. The difference between UE-initiated and
P-GW-initiated dedicated bearer activation procedures is that the UE informs the P-GW
of the service type in a UE-initiated dedicated bearer activation procedure. However, the
P-GW always starts the activation no matter the dedicated bearer activation procedure is
initiated by the UE or P-GW. For details about the procedure, see section 3.2.2 "Delivery
and Application of QoS Parameters During Dedicated Bearer Activation".
3.2 Delivery and Application of QoS Parameters
3.2.1 Delivery and Application of QoS Parameters During Default
Bearer Activation
Figure 3-4 Default bearer activation procedure

UE eNodeB new MME Old Serving GW PDN GW PCRF HSS

MME/SGSN
1. Attach Request
EIR
2. Attach
Request 3. Identification Request
3. Identification Response
4. Identity Request
4. Identity Response
5a. Authentication / Security
5b. Identity Request/Response
5b. ME Identity Check
6. Ciphered Options Request
6. Ciphered Options Response
7. Delete Sesion Request 7. PCEF Initiated IP-CAN
Session Termination
(E) 7. Delete Session Response
(A)
8. Update Location Request
9. Cancel Location
9. Cancel Location Ack

10. Delete Session Request 10. PCEF Initiated IP-CAN

Session Termination
(F) 10. Delete Session Response
(B)

11. Update Location Ack

12. Create Session Request
13. Create Session Request
14. PCEF Initiated IP-CAN Session
Establishment/Modification
(C)
15. Create Session Response
First Downlink Data (if not handover)
16. Create Session Response
17. Initial Context Setup Request / Attach Accept
18. RRC Connection Reconfiguration
19. RRC Connection Reconfiguration Complete
20. Initial Context Setup Response
21. Direct Transfer
22. Attach Complete
First Uplink Data
23. Modify Bearer Request
23a. Modify Bearer Request
23b. Modify Bearer Response
(D)
24. Modify Bearer Response
First Downlink Data
25. Notify Request
26. Notify Response
The default bearer is activated during the attach procedure. Figure 3-4 shows the attach
procedure defined in the 3GPP specifications. For details about the description of each
message in the procedure, see 3GPP TS 23.401. The following describes only QoS-related
messages.
The Update Location Ack message sent from the HSS in step 11 contains the subscriber's
international mobile subscriber identity (IMSI) and subscription data. The subscription data
contains the QoS parameters for EPS bearers associated with all subscribed APNs and the
APN-AMBR of each APN. The EPS bearer defined in the HSS is a default bearer, and each
APN has a default bearer. The subscription data on the HSS includes one or more subscribed
APNs. The QoS parameters include the QCI and ARP.
The Create Session Request message sent in steps 12 and 13 contains the QoS parameters for
the requested default EPS bearer. The QoS parameters include the QCI, ARP, GBR, MBR,
and APN-AMBR.
If the PCRF is deployed, the P-GW interacts with the PCRF in step 14 to request the QoS and
charging policies. The request message contains all QoS parameters. The PCRF can modify
the QoS parameters in the request message and includes the modified parameters in the
response message. The S-GW and P-GW activate the EPS bearer based on the QoS
parameters delivered from the PCRF. If the PCRF is not deployed, the P-GW checks whether
there are settings for the default bearer based on the PCC rules pre-configured in the PCEF of
the P-GW. If there are settings for the default bearer, the S-GW and P-GW activate the default
bearer based on the QoS parameters pre-configured for the default bearer. If there are no
settings for the default bearer, the S-GW and P-GW activate the default bearer based on the
QoS parameters defined in the HSS. When the bearer between the S-GW and P-GW is
activated, the P-GW generates a TFT template for mapping traffic to the bearer and delivers
the TFT to the MME.
The Create Session Response message sent in step 16 contains parameters such as the bearer
QoS and TFT.
In step 17, the MME instructs the eNodeB to activate an S1-U default bearer between the
eNodeB and the S-GW. The Initial Context Setup Request message includes the UE-AMBR,
QCI, ARP, GBR (for GBR bearers), and TFT.
In step 18, the eNodeB maps the EPS bearer QoS to the radio bearer QoS and then sends an
RRC Connection Reconfiguration message including the radio bearer QoS and TFT to the
UE.
In step 19, the default radio bearer is activated and the TFT is generated and updated in the
UE.
3.2.2 Delivery and Application of QoS Parameters During
Dedicated Bearer Activation
Figure 3-5 Dedicated bearer activation procedure
UE eNodeB MME Serving GW PDN GW PCRF

1. IP-CAN Session
(A)
Modification

2. Create Bearer Request

3. Create Bearer Request

4. Bearer Setup Request/
Session Management Request

5. RRC Connection Reconfiguration

6. RRC Connection Reconfiguration Complete

7. Bearer Setup Response

8. Direct Transfer
9. Session Management Response
10. Create Bearer Response
11. Create Bearer Response
12. IP-CAN Session
Modification
(B)

1. The PCRF delivers the modified QoS parameters including the QCI, ARP, GBR, MBR,
and APN-AMBR to the P-GW. If the PCRF is not deployed, the P-GW can directly
initiate the dedicated bearer activation based on the pre-configured PCC rules.
2. The P-GW uses the QoS policy obtained in step 1 to assign the EPS Bearer QoS, and
assigns a P-GW TEID-U for the dedicated bearer. Then, the P-GW sends the S-GW a
Create Bearer Request message including the IMSI, PTI, EPS Bearer QoS, TFT, S5/S8
TEID, Charging Id, and LBI IEs. (LBI is short for Linked EPS Bearer Identity.) The LBI
is the identity of the default bearer. After receiving the message, the S-GW creates the
dedicated bearer context, and associates the default and dedicated bearers based on the
LBI to generate and update the TFT.
3. The S-GW sends a Create Bearer Request message to the MME.
4. The MME sends the eNodeB a Bearer Setup Request message including the EPS Bearer
Identity, EPS Bearer QoS, Session Management Request, and S1-TEID. The Session
Management Request message sent along the Bearer Setup Request message is built by
the MME. The Session Management Request message includes the PTI, TFT, EPS
Bearer QoS parameters (excluding ARP), Protocol Configuration Options, EPS Bearer
Identity, and the LBI.
5. The eNodeB maps the EPS bearer QoS to the radio bearer QoS, and then sends the UE
an RRC Connection Reconfiguration message including the Radio Bearer QoS, Session
Management Request, and EPS RB Identity. The UE saves the information in the
message, and associates the dedicated and default bearers based on the LBI to generate
and update the TFT.
6. The UE responds to the eNodeB with an RRC Connection Reconfiguration Complete
message to acknowledge the radio bearer activation.
 7. The eNodeB sends a Bearer Setup Response message including the EPS Bearer Identity
and S1-TEID to the MME to acknowledge the radio bearer activation.
8. The UE NAS layer builds a Session Management Response including the EPS Bearer
Identity. The UE then sends a Direct Transfer message including the Session
Management Response message to the eNodeB.
9. The eNodeB sends a Session Management Response message to the MME.
10. Upon reception of the Bearer Setup Response message in step 7 and the Session
Management Response message in step 9, the MME sends a Create Bearer Response
message including the EPS Bearer Identity and S1-TEID to the S-GW to acknowledge
the bearer activation. The S-GW saves the S1-U TEID and activates the S1-U dedicated
bearer between the S-GW and the eNodeB.

3.2.3 Delivery and Application of QoS Parameters During Bearer

Modification
Figure 3-6 P-GW-initiated bearer modification with QoS update
UE eNodeB MME Serving GW PDN GW PCRF

(A) 1. IP-CAN Session

Modification

2. Update Bearer request

3. Update Bearer Request

4. Bearer Modify Request/
Session Management Request
5. RRC Connection Reconfiguration

6. RRC Connection Reconfiguration Complete

7. Bearer Modify Response

8. Direct Transfer
9. Session Management Response
10. Update Bearer Response

11. Update Bearer response

12. IP-CAN Session
(B) Modification

1. If dynamic PCC is deployed, the PCRF sends a PCC decision provision (QoS policy)
message to the P-GW. If dynamic PCC is not deployed, the P-GW applies the local QoS
policy.
2. The P-GW uses the obtained QoS policy to determine that the authorized QoS of a
service data flow has changed or that a service data flow needs to be added to or
removed from an active dedicated bearer. The P-W then determines to initiate a
dedicated bearer modification procedure with QoS update. The P-GW generates the TFT
and updates the EPS Bearer QoS, and then sends the S-GW an Update Bearer Request
message including the EPS Bearer Identity, EPS Bearer QoS, APN-AMBR, and TFT.
3. After receiving the Update Bearer Request message, the S-GW sends the MME an
Update Bearer Request message including the EPS Bearer Identity, EPS Bearer QoS,
APN-AMBR, and TFT.
4. The MME sends a Bearer Modify Request message including a NAS message Modify
EPS Bearer Context Request to the eNodeB.
5. The eNodeB maps the modified EPS bearer QoS to the radio bearer QoS. The eNodeB
then sends an RRC Connection Reconfiguration message to the UE and forwards the
Modify EPS Bearer Context Request message to the UE at the same time.
6. The UE responds to the eNodeB with an RRC Connection Reconfiguration Complete
message to acknowledge the radio bearer modification.
7. The eNodeB sends a Bearer Modify Response (EPS Bearer Identity) message to the
MME to acknowledge the bearer modification. With this message, the eNodeB indicates
whether the requested EPS bearer QoS can be allocated or not.
8. The UE NAS layer builds a Modify EPS Bearer Context Accept message including the
EPS bearer identity. The UE then sends the message to the eNodeB.
9. The eNodeB forwards the Modify EPS Bearer Context Accept message to the MME.
10. Upon reception of the Bearer Modify Response message in step 7 and the Modify EPS
Bearer Context Accept message in step 9, the MME sends an Update Bearer Response
message including the EPS Bearer Identity to the S-GW to acknowledge the bearer
modification.
11. The S-GW sends an Update Bearer Response (EPS Bearer Identity) message to the
P-GW to acknowledge the bearer modification.
 4 QoS Functions of NEs

4.1 QoS Functions of NEs in the EPC

4.1.1 QoS Functions Performed During Service Requests
 QoS restriction for roaming subscribers
Huawei products support QoS restriction for roaming subscribers. IMSI
number segments, uplink UE-AMBR, downlink UE-AMBR, uplink
APN-AMBR, and downlink APN-AMBR can be configured for the QoS
restriction. The configured QoS parameters take effect for all the subscribers
whose IMSIs match the configured IMSI prefixes.
 Admission control
For a GBR bearer, the P-GW checks whether the requested bandwidth
resource exceeds the remaining resource in the system. If the requested
bandwidth resource exceeds the remaining resource in the system, the P-GW
rejects the bearer activation. QoS negotiation is not performed on an EPS
network. When the resource is insufficient, the P-GW directly rejects the
service request. For a non-GBR bearer, the P-GW does not perform the check
because the resource is shared by non-GBR bearers.

4.1.2 QoS Control After Service Setup

 QoS enhancement for control plane signaling
The MME handles only signaling and does not handle user plane data. The
MME supports the smart paging function. In this function, the paging duration,
paging request retransmission times, and paging interval vary with the QCI
values of bearers. The paging interval can gradually increase with the paging
request retransmission times to reduce the signaling amount on the network.
The QCI, paging duration, paging request retransmission times, and paging
interval can be configured on the MME.
 Traffic policing (TP)
The P-GW supports the TP function. This function monitors the traffic in
devices and prevents the user traffic from exceeding the maximum bandwidth.
 Committed access rate (CAR)
 The P-GW supports the CAR function to limit the traffic of specified types of
services. For example, the traffic of Hypertext Transfer Protocol (HTTP)
services cannot exceed 50% of the total traffic on the network. The UGW9811
classifies incoming packets into different groups based on the service types
and forwards the packets in these groups at configured rates. If the traffic
exceeds the limit, the excess amount is discarded or the priority is
reconfigured.
 Traffic shaping (TS)
The P-GW supports the TS function. This function controls the traffic
transmission so that packets can be transmitted evenly to prevent traffic bursts
from affecting the network performance. Depending on the configuration,
packets can also be directly forwarded without traffic shaping. The TP
function is implemented using token control. After receiving packets, the
P-GW compares the number of packets with the number of tokens in the token
bucket. If the number of tokens is greater than the number of packets, the
P-GW directly forwards the packets and reduces the number of tokens. If the
number of tokens is less than the number of packets, the packets are buffered.
The P-GW generates tokens based on the configured rate. When the buffer
queue is full, the P-GW directly discards the packets that cannot be forwarded.

4.2 QoS Functions of the eNodeB

4.2.1 QoS Functions Performed During Service Requests
In admission control, the eNodeB provides differentiated services based on
subscriber priorities. The admission criteria set for high-priority subscribers
are less strict than the admission criteria set for low-priority subscribers,
ensuring a higher admission success rate for high-priority subscribers. If the
service of a high-priority subscriber initially fails to be admitted, the service
can preempt the resource allocated to the service of a low-priority subscriber
to increase the admission success rate. Emergency services have the highest
priority during admission, ensuring a highest admission success rate. The
eNodeB selects appropriate bearer schemes and performs initial power control
and cell-level admission control to guarantee the QoS and provide
differentiated services.
A radio bearer is activated based on parameters such as the QCI, GBR, and
MBR. Radio bearers are classified into signaling radio bearers (SRBs) and
data radio bearers (DRBs) based on what is carried on the bearers. The
number of DBRs activated between a UE and the eNodeB varies with the QoS,
and a maximum of eight DRBs can be activated between a UE and the
eNodeB.
The purpose of initial power control is to reduce interference to the minimum
when the QoS is satisfied.
The purpose of cell-level admission control is to prevent cell overload by
limiting the number of admitted subscribers. The admission control function is
available for every cell. The eNodeB monitors the current cell load and
estimates the load increase caused by the admission of new services to
determine whether cell overload will occur after the new services are admitted.
Admission control helps ensure the quality of admitted services and the
expected quality of the new services. If the access of a new subscriber is
rejected due to admission control, the subscriber needs to access another cell
on a different frequency in the same coverage area. The rules for cell-level
admission control are as follows:
 For non-GBR services, admission control is performed not based on the
QoS satisfaction rate but based on the current number of bearers for
non-GBR services in the cell. The MaxNonGBRBearerNum parameter
specifies the maximum number of bearers for non-GBR services in a cell.
If the admission of new non-GBR services does not cause the number of
bearers for non-GBR services to exceed the value of
MaxNonGBRBearerNum, the new non-GBR services can be admitted.
IMS services are directly admitted without considering the QoS
satisfaction rate or the MaxNonGBRBearerNum parameter.
Extended QCIs are configured based on the requirements of enterprise
customers. Extended QCIs apply to non-GBR services and therefore
MaxNonGBRBearerNum also applies to the admission of services
using extended QCIs.
If the service preemption function is enabled, a service that initially fails
to be admitted can preempt resources allocated to other services. For
details about the preemption procedure, see section 4.2.3 "Service
Preemption". If the preemption also fails, the admission fails.
 Figure 4-1 shows the downlink admission control procedure for a new
GBR service. If the switch for checking the number of physical resource
blocks (PRBs) used by GBR services is turned on, the eNodeB checks
the PRB usage of GBR services in the cell to determine whether to admit
the new GBR service when the eNodeB receives a new GBR service
admission request. The eNodeB does not perform the check for
handovers. By limiting the amount of resources occupied by GBR
services, the eNodeB prevents data rate of non-GBR services from
dropping to zero due to resource unavailability.
If the PRB usage is high or the power is limited and downlink admission
based on QoS satisfaction rates is enabled, the eNodeB needs to evaluate
the QoS satisfaction rate of services of the same type. Different QoS
satisfaction thresholds are set for services of the same type but of
different subscriber priorities. The new service can be admitted only
when the QoS satisfaction rate is higher than the corresponding threshold.
If the service preemption function is enabled, a service that initially fails
to be admitted can preempt resources allocated to other services. For
details about the preemption procedure, see section 4.2.3 "Service
Preemption". If the preemption also fails, the admission fails. The
admission of handovers for GBR services is controlled based on different
QoS satisfaction rates.
 Figure 4-1 Downlink admission procedure for GBR services

4.2.2 QoS Control After Service Setup

If the network is congested, the eNodeB releases some admitted UEs or
reduces data rates for some admitted UEs (excluding UEs performing
emergency services) to maintain system stability or reserve resources for new
services. After the UEs are released or the data rates are reduced, the cell load
is decreased. Low-priority subscribers are usually selected preferentially for
UE release and data rate reduction, which ensures the overall service quality
in a cell at the cost of the service quality of low-priority subscribers. The
eNodeB performs power control, mobility management, scheduling, load
balancing, and congestion control to guarantee the QoS and the differentiation
between services and between subscribers.
  Power control: After a service is set up, power control enables the data of
the service to be transmitted using appropriate power, ensuring correct
data reception without power waste.
 Mobility management: When a UE moves to the cell edge, the service
quality may decrease. The handover function enables the UE to select
another more appropriate cell in a timely manner, ensuring service
continuity.
 Scheduling: Scheduling ensures that subscribers enjoy satisfactory
service quality to the largest extent. For example, the packet transmission
delay for delay-sensitive VoIP services is in an acceptable range; the
GBR and packet delay budget (PDB) are guaranteed for GBR services;
the data rate for non-GBR services such as FTP is not lower than the
minimum GBR (min-GBR). The scheduling principles are as follows:
Resources are first scheduled to guarantee the PDB of GBR services,
then scheduled to guarantee the GBR of GBR services and min-GBR of
non-GBR services, and last scheduled for non-GBR services based on
the service weights to guarantee that the aggregate data rate of all
non-GBR services of the UE is less than the UE-AMBR.
 Load balancing. Load balancing distributes load between neighboring
cells by transferring UEs in a high-load cell to move to a low-load cell,
maximizing resource usage.
 Congestion control. The system becomes congested when the system
load increases to a high level. If the system is congested, the congestion
control algorithm needs to be used to control the system load to ensure
the overall QoS satisfaction rate and system stability. For details about
the congestion control principles, see section 4.2.4 "Congestion Control".

4.2.3 Service Preemption

A service can preempt the resources allocated to other services only if the
value of its ARP information element (IE) "pre-emption capability" is "may
trigger pre-emption". If a service is not capable of preemption, it cannot be
admitted. If a service is capable of preemption, it can preempt a service that
meets all of the following conditions:
 SRBs, IMS signaling, and emergency calls cannot be preempted.
 The service to be preempted is a GBR service if the preempting service
is a GBR service, or the service to be preempted is a non-GBR service if
the preempting service is a non-GBR service.
 The value of the ARP IE "pre-emption vulnerability" of the service to be
preempted is "pre-emptable".
 The value of the ARP IE "priority level" of the service to be preempted is
greater than that of the preempting service.
 If the service to be preempted is a GBR service, the resources allocated
to it are greater than or equal to the resources required by the preempting
GBR service.
The preemption fails if any of the preceding conditions is not met. If
redirection is enabled, a UE is redirected in case that none of the services of
the UE is admitted during initial access and preemption for the services of the
UE fails. If preemption for a handover fails, the eNodeB handles the failure
based on the actual situation.
4.2.3.1 GBR Service Preemption
The eNodeB first groups GBR services with low priorities and then selects
services that can be preempted from the group. The procedure is as follows:
1. The eNodeB groups the GBR services with low priorities.
The eNodeB first selects releasable GBR services and then groups the services
with the lowest priorities among them. A releasable GBR service must meet
the following conditions:
 The value of the ARP IE "pre-emption vulnerability" of the service is
"pre-emptable".
 The service is not an emergency call.
 The service rate is not 0.
The eNodeB sorts these GBR services based on the following rule: The
service with the largest value of the ARP IE "priority level" has the lowest
priority and ranks first. If two services have the same "priority level" value,
the service that occupies more resource blocks (RBs) ranks ahead of the other.
2. The eNodeB selects services to be preempted.
The eNodeB estimates the number of RBs required by a preempting service
based on the average spectral efficiency of the cell. The eNodeB calculates the
number of RBs released from the group of GBR services with low priorities.
The release stops after the number of released RBs meets the requirements of
the preempting service. The preemption fails if no service can be preempted
or the preempting service requires more RBs even after RBs of ten preempted
services have been released.

4.2.3.2 Non-GBR Service Preemption

A non-GBR service can only preempt resources of another non-GBR service.
The eNodeB selects non-GBR services for the preemption as follows:
1. The eNodeB selects non-GBR services for which the ARP IE
"pre-emption vulnerability"is "pre-emptable".
2. The eNodeB excludes IMS signaling and emergency calls from the
selected services.
3. The eNodeB sorts out the non-GBR services whose ARP IE "priority
level" values are greater than the ARP IE "priority level" value of the
preempting service. The service with the largest value of the ARP IE
"priority level" has the lowest priority and ranks first.
The services ranking the first is preempted first. If no suitable service is found
for the preemption, the preemption fails.

4.2.4 Congestion Control

Congestion control reduces congestion caused by radio or transport resource
insufficiency. Congestion control is performed after services are admitted in
the following case: Congestion occurs because of resource insufficiency
which is a result of radio condition change or transport network condition
change.
4.2.4.1 Transport Congestion Control
Transport congestion control involves transport differentiated flow control and
transport dynamic flow control. Table 4-1 lists the involved algorithms.

Table 4-1 Algorithms for transport congestion control

Scenario Level -1 Level-2 Description

Algorithm Algorithm

Congestion on Transport Traffic Traffic shaping covers transport resource groups

transport boards differentiated shaping and physical ports. By using traffic shaping, TX
in the eNodeB flow control traffic in the uplink is limited to the configured
bandwidth.

Physical port The ports on LMPT, UMPT, and UTRPc boards

scheduling use Weighted Round Robin (WRR) for resource
scheduling. The ports on UTRP boards use
Round Robin (RR) for resource scheduling.

Scheduling Both priority queuing (PQ) scheduling and

on transport non-PQ scheduling are used for each queue in a
resource transport resource group. In non-PQ scheduling
groups mode, WRR is used.

Back-pressure Back-pressure preferentially schedules

non-flow-controllable services to ensure their
service quality and limits the rates of
non-real-time services to differentiate bandwidth
allocation among non-real-time services.

Congestion in the Transport IP PM The IP PM function is a Huawei proprietary

network (not dynamic flow function. It monitors end-to-end network
inside the control performance to obtain network quality
eNodeB) information such as traffic volume, packet loss
rate, and delay variation. IP PM enhances system
maintainability and testability and improves
system performance.
If differentiated services code points (DSCPs)
may be dynamically changed on the transport
network, the IP PM triplet is recommended. If
DSCPs are not dynamically changed on the
transport network, the IP PM quadruple is
recommended.

Dynamic Dynamic bandwidth adjustment estimates the

bandwidth bottleneck bandwidth and sends the bandwidth
adjustment information to the transport differentiated flow
control algorithm and transport admission
control algorithm.
4.2.4.2 Radio Interface Congestion Control
Radio interface congestion control is enabled when the uplink and downlink
congestion control switches are turned on. Figure 4-2 shows the congestion
control procedure.

Figure 4-2 Procedure for radio interface congestion control

The eNodeB determines the load status by comparing the QoS satisfaction
rates of services of various QCIs with the respective congestion thresholds
and by considering the PRB usage and power limitation conditions. A cell is
regarded as congested if the QoS satisfaction rate of GBR services with
specified QCIs is lower than the corresponding congestion threshold and the
PRB usage is high or the power is limited.
If a cell is congested, congestion control releases the service ranking the first
among the admitted GBR services with low priorities. If the GBR service to
be released is the only GBR service running on a UE and redirection is
enabled, the eNodeB redirects the UE to another frequency or RAT to
increase the access success rate of the UE. After the GBR service is released,
the eNodeB checks whether the QoS satisfaction rate of GBR services is
restored. If the QoS satisfaction rate of GBR services is not restored, the
eNodeB performs the GBR service release procedure again until the
congestion is relieved.
 5 QoS Configuration for Typical
Services

5.1 QoS Configuration Principles

Based on the QoS architecture on the current EPS network and characteristics
of enterprise services, QoS design and configuration are differentiated for
GBR and non-GBR services.

5.1.1 Differentiation Between GBR Bearers and

Non-GBR Bearers
Key services use GBR bearers and non-key services use non-GBR bearers.
The EPS network provides differentiated E2E QoS guarantee for various
services and guarantees short delay and sufficient bandwidth for key services.
During QoS design, services must be first sorted based on their QoS priorities
to determine whether a service needs to use GBR or non-GBR bearers. The
bandwidth and delay are guaranteed preferentially for services on GBR
bearers. A best-effort QoS guarantee is provided for services on non-GBR
bearers.

5.1.2 QoS Design for GBR Bearers

 QCI
The QCI value is selected based on the delay requirement of the service.
QCI values have two functions for Huawei devices. One function is to
distinguish GBR services and non-GBR services, and the other function is to
define the service delay and packet loss rate. Currently, Huawei products
consider only the delay when performing scheduling. VoIP services require
the QCI of 1. When semi-persistent scheduling is enabled, the eNodeB
performs semi-persistent scheduling for VoIP services. If there are no VoIP
services, the QCI for other services can be set to 1. When the QCI is set to 1
for other services, semi-persistent scheduling must be disabled. If
semi-persistent scheduling is not disabled, the eNodeB performs
semi-persistent scheduling for these services. The prerequisite for
semi-persistent scheduling is that there are no other dedicated bearers.

2014-9-29 错误！未知的文档属性名称.
  ARP
ARPs involve preemption attributes and preemption priorities. For key
services, the ARP can be configured to allow key services to preempt other
services but not to be preempted by other services. For non-key services, the
APR can be configured to allow non-key services to preempt other services
and to be preempted by other services. ARP values that indicate high
preemption capabilities can be configured for important services.

 Preemption during admission and service release in case of congestion are both
performed based on service priorities. The priorities are first determined based on
ARPs. If the ARPs are the same, the priorities are further determined based on
QCIs.
 The preemption principle is that GBR services can preempt only GBR services
and non-GBR services can preempt only non-GBR services. Therefore, ARP
values must be designed for the GBR and non-GBR bearers separately.
 The ARP value range is 1 to 15, indicating 15 priorities. When preemption
attribute is configured to be preemptable or not preemptable for all bearers,
preemption can be implemented based on the priorities.
 APR 1 applies to emergency calls. Emergency calls can always be admitted.
Therefore, do not use ARP 1 on enterprise networks.
 GBR and MBR
The GBR and MBR need to be set to the same value and the value must be
higher than the actual bandwidth required by the service.

Currently, Huawei products do not support settings in which the MBR is higher than
the GBR. Therefore, MBRs and GBRs must be set to the same value. This design can
reserve some excess bandwidth for data rate jitter and radio interface rate jitter.

5.1.3 QoS Design for non-GBR Bearers

 QCI
The QCI design principle is the same as that for GBR bearers.

Although services with the QCI of 5 are non-GBR services, the eNodeB does not
perform admission control on these services and these services have the highest
scheduling priority. It is recommended that the QCI of control command services be
set to 5 for devices on enterprise networks.
 ARP
The ARP design principle is the same as that for GBR bearers.
 APN-AMBR and UE-AMBR
The APN-AMBR is not lower than the aggregate bit rate of services on all
non-GBR bearers of the same APN. The UE-AMBR is not lower than the
aggregate bit rate of services on all non-GBR bearers of all APNs for the UE.
APN-AMBR and UE-AMBR are used to limit the rate of non-GBR services.
APN-AMBR is enforced on the P-GW to limit the rate of non-GBR services
associated with the same APN for a UE. UE-AMBR is enforced on the
eNodeB to limit the rate of all non-GBR services of a UE.

2014-9-29 错误！未知的文档属性名称.
 Enterprise customers usually do not have specific QoS requirements for
services. In this case, scheduling and preemption priorities must be designed
based on the importance of the actually used services. The service types
defined in the 3GPP specifications cannot be directly applied to services used
on enterprise networks.

5.2 QoS Design for the Combined Video and

Voice Service
The combined video and voice service is deployed based on the eSpace UC
service platform and is carried on the EPS network. This section focuses on
the EPS QoS design for the combined video and voice service, signaling, and
management commands based on the eSpace unified communication (UC)
service platform.

5.2.1 Data Flow Identification

Traffic flows are identified based on the quintuple information of IP packets.
The quintuple consists of the source IP address, source port number,
destination IP address, destination port number, and transmission layer
protocol. A TFT contains a set of packet filters. These filters use the quintuple
information of IP packets as the filtering criteria to filter packets. An EPS
bearer has an UL TFT and a DL TFT. After traffic flows are filtered, the QoS
parameters for an EPS bearer will be applied to the corresponding traffic
flows.
In a combined video and voice service, the following traffic flows need to be
identified:
 SIP signaling: SIP signaling all passes through the unified session
management (USM) server. The IP address and port number of the USM
server must be specified.
 Video and voice media streams involved in point-to-point (P2P) voice
call, P2P video calls, and voice conferences: The port number on the
terminal side must be specified.
 Video sharing traffic flows and screen sharing traffic flows involved in
multimedia conferences: The IP address and port number of the
conference server MS must be specified.
 Instant message (content)
− Small-sized messages including small-sized P2P messages and
point-to-fixed-group messages (carried in SIP signaling and
forwarded by PGM): The IP address and port number of the USM
server must be specified. (PGM is short for presence group message.)
− Large-sized messages including large-sized P2P messages and
point-to-fixed-group messages (forwarded by the Message Session
Relay Protocol (MSRP) server in the PGM): The IP address and port
number of the PGM server must be specified.
− Temporary group messages including large- and small-sized
temporary-group-targeted messages (forwarded by the MSRP switch

2014-9-29 错误！未知的文档属性名称.
 in the PGM): The IP address and port number of the PGM server
must be specified.
 File transfer (file content): The port number on the terminal side must be
specified.
 Interaction between the terminal and servers when the terminal initiates
connection to the servers (for example, interaction with the
authentication and authorization (AA) server, Mobile access agent (MAA)
server, PGM server, element management system (EMS) server, business
management point (BMP) server, Network Time Protocol (NTP) server,
and Dynamic Host Configuration Protocol (DHCP) server): The IP
addresses and port numbers of these servers must be specified.
 Interaction between the terminal and the server when the server initiates
connection to the terminal and interaction between terminals (for
example, active visits from the EMS server and maintenance tool to the
terminal, and P2P file transfer): The port number on the terminal side
must be specified.

Quintuple
Information Used to Assist Service Identification_20140117.xlsx

5.2.2 QoS Design Analysis

A combined video and voice service involves multiple types of services and
each type of service has its own requirements for service quality dimensions
such as delay, jitter, packet loss rate, packet error ratio, and bandwidth. The
QoS requirements of each type of service are as follows:
 SIP signaling has a high requirement for real-timeliness and a low
requirement for bandwidth, and should be carried by non-GBR bearers
with high priorities.
 Interactive media in P2P voice calls, P2P video calls, and voice
conferences are transmitted using the Real-Time Transport Protocol
(RTP), User Datagram Protocol (UDP), and IP, have high requirements
for real-timeliness and data rate, and should be preferentially carried by
GBR bearers.
 Video sharing traffic flows and screen sharing traffic flows in multimedia
conferences are transmitted using HTTP, TCP, and IP, are relatively
tolerant of delay, and require a high bandwidth.
 Other UC services and data services have a relatively low requirement
for real-timeliness but have a high requirement for packet error ratio. The
relative priorities should be differentiated for such services.

5.2.3 EPS Bearer Planning

In section 6.1.7 "Standardized QoS characteristics" of 3GPP TS 23.203
"Policy and charging control architecture", the characteristics of standardized
QCIs and typical services that require standardized QCIs are described.

2014-9-29 错误！未知的文档属性名称.
QCI Resource Priorit Packet Packet Error Example Services
Type y Delay Loss Rate
Budget

1 2 100 ms 1.00E-02 Conversational voice

Conversational video (Live

2 4 150 ms 1.00E-03
streaming)
GBR
3 3 50 ms 1.00E-03 Real-time gaming

Non-conversational video
4 5 300 ms 1.00E-06
(Buffered streaming)

5 1 100 ms 1.00E-06 IMS signaling

6 6
Video (Buffered
streaming), TCP-based (for
300 ms 1.00E-06 example, www, e-mail,
chat, ftp, p2p file sharing,
progressive video.)

Non-GBR Voice, video (Live

7 7 100 ms 1.00E-03 streaming), interactive
gaming

8 8 Video (Buffered
streaming), TCP-based (for
300 ms 1.00E-06 example, www, e-mail,
9 9 chat, ftp, p2p file sharing,
progressive video.)

The services or traffic flows involved in the combined video and voice service
are analyzed as follows:
 SIP signaling has the highest priority which corresponds to QCI 5.
 UC media streams have different priorities based on the requirements for
real-timeliness.
− The media streams of traditional services such as P2P voice calls, P2P
video calls, and voice conferences are transmitted using RTP, UDP,
and IP, have high requirements for real-timeliness and rates, and are
preferentially carried by GBR bearers. The audio stream and video
stream need to be carried on GBR bearers with different QCIs. The
audio stream is carried on GBR bearers with the QCI of 1 and the
video stream is carried on the GBR bearers with the QCI of 2.
Alternatively, non-GBR bearers with the QCI of 7 can be used to
carry the media streams. However, the QoS control capability is weak.
For UEs, bearers with the QCIs of 6, 7, 8, and 9 correspond to the
same logical channel group 3 (LCG 3) (when LCG_Profile_0 is used).
In uplink scheduling, the UEs perform secondary scheduling of the

2014-9-29 错误！未知的文档属性名称.
 logical channels in the LCG and the scheduling result is not always
satisfactory.
− Video sharing traffic flows and screen sharing traffic flows in
multimedia conferences are transmitted using HTTP, TCP, and IP, and
are relatively tolerant of delay. The traffic flows belong to TCP-based
services and can be carried by bearers with the QCIs of 4, 6, 8, and 9.
The traffic flows require a large bandwidth. QCI 4 is not considered
for such traffic flows.
 Other types of services are as follows:
− Key UC services
Key UC services include AA/MAA access, address book query, status
synchronization, and instant messages (including large-sized P2P
messages, large-sized point-to-fixed-group messages, and large- and
small-sized temporary-group-targeted messages, and excluding
small-sized P2P messages carried along with SIP signaling and
small-sized point-to-fixed-group messages).
− Other UC services
These UC services include P2P file transfer and group file sharing.
− Key configuration services
Key configuration services include DHCP, time synchronization,
certificate download, IP phone configuration file download, image
download, and personal login to BMP/portal.
− Network management services
Network management services include device management of the
IAD and IP phone.
− Maintenance services
Maintenance services include maintenance of remote access to the
IDA and IP phone.
− Other services
Other services include upgrade and internet surfing.
The traffic flows of the other types of services can be carried by non-GBR
bearers. The priorities of key UC services and key configuration services are
higher than the priorities of network management services, maintenance
services, other UC services, and other services.
The planned binding relationship between EPS bearers and traffic flows is
described in the attached .xlsx file.

Plan of Binding
Relationship Between EPS Bearers and Serive Data Flows.xlsx

2014-9-29 错误！未知的文档属性名称.
 "√" indicates that the traffic flow of the terminal indicated in the corresponding
column has a binding relationship with the EPS bearer described in the corresponding
line.

The binding relationship is described as follows:

 Bearers with the QCI of 5 are bound to SIP signaling.
 Bearers with the QCI of 1 are bound to voice media streams.
 In mobile scenarios, bearers with the QCI of 2 are bound to P2P video
media streams of mobile terminals accessing the service through a
handset or to P2P video media streams of desktop terminals accessing
the service through a dongle or CPE.
 Bearers with the QCI of 7 are bound to P2P video media streams of UC
terminals accessing the service through a fixed CPE.
 Bearers with the QCI of 6 are bound to key UC services and key
configuration services.
 Bearers with the QCI of 8 are bound to video sharing traffic flows and
screen sharing traffic flows involved in multimedia conferences.
 Bearers with the QCI of 9 are bound to network management services,
maintenance services, other UC services, and other services.
 Due to the importance of voice communication, voice media streams are
always bound to GBR bearers with the QCI of 1 to preferentially
guarantee the QoS of voice services in all conditions.
Considering the uplink scheduling sequence on the eNodeB and high
bandwidth requirement of video services, P2P video media streams accessed
using a fixed CPE are bound to non-GBR bearers with the QCI of 7 instead of
GBR bearers with the QCI of 2 to prevent frequent scheduling of GBR
services from causing non-GBR service congestion.

2014-9-29 错误！未知的文档属性名称.
 Video sharing traffic flows and screen sharing traffic flows involved in
multimedia conferences are bound to non-GBR bearers with the QCI of 8. The
priority of such traffic flows is lower than the priority of key UC services and
key configuration services and is higher than the priority of network
management services, maintenance services, other UC services, and other
services.
Network management services, maintenance services, other UC services, and
other services are bound to non-GBR bearers with the QCI of 9. A bearer
cannot carry traffic flows of four types of services at the same time. Network
management services and maintenance services apply only to IADs and IP
phones. Other UC services and other services apply only to mobile and
desktop software terminals.
The following tables list the planned QoS parameters of EPS bearers in
various access scenarios.

GBR and AMBR Configurations

CPE (Fixed Access) Handset (Mobile Access) Dongle/CPE (Mobile Access)

QCI = GBR (UL/DL) = GBR (UL/DL) = One G.711 audio GBR (UL/DL) = One G.711
1 Maximum number of UC bit rate audio bit rate
terminals that are allowed
to access the CPE x One
G.711 audio bit rate
(For details, see note item
1.)

GBR QCI = GBR (UL/DL) = One GBR (UL/DL) = One

bearer 2 H.264/QVGA/15fps video bit rate H.264/720P/15fps video bit rate
(For details, see note item 2.) (For details, see note item 3.)

QCI =
3

QCI =
4

QCI = AMBR (UL) = 20 Mbit/s AMBR (UL) = 500 kbit/s AMBR (UL) = 2 Mbit/s
5
AMBR (DL) = 40 Mbit/s AMBR (DL) = 1 Mbit/s AMBR (DL) = 2 Mbit/s

QCI = (For details, see note item (For details, see note item 5.) (For details, see note item 6.)
Non- 6 4.)
GBR
bearer QCI =
7

QCI =
8

2014-9-29 错误！未知的文档属性名称.
 QCI =
9

Prioritized Bit Rate (PBR) and min-GBR Configurations (See Note Item 7)

CPE (Fixed Access) Handset (Mobile Dongle/CPE (Mobile

Access) Access)

QCI = 6 When the number of UC PBR = 8 kbit/s PBR = 8 kbit/s

terminals that have accessed
the CPE is less than or equal to min-GBR (DL) = 8 kbit/s min-GBR (DL) = 8 kbit/s
half of the maximum number
of UC terminals that are
allowed to access the CPE:

 PBR = 16 kbit/s
 min-GBR (DL) = 16 kbit/s

When the number of UC

terminals that have accessed
the CPE is greater than half of
the maximum number of UC
terminals that are allowed to
access the CPE:
 PBR = 32 kbit/s
 min-GBR (DL) = 32 kbit/s
Non-GBR
bearer QCI = 7 When the number of Not involved Not involved
video-call-capable UC
terminals that have accessed
the CPE is less than or equal to
half of the maximum number
of UC terminals that are
allowed to access the CPE:

 PBR = 32 kbit/s
 min-GBR (DL) = 32 kbit/s

When the number of

video-call-capable UC
terminals that have accessed
the CPE is greater than half of
the maximum number of UC
terminals that are allowed to
access the CPE:

 PBR = 64 kbit/s
 min-GBR (DL) = 64 kbit/s

2014-9-29 错误！未知的文档属性名称.
QCI = 8 When the number of PBR = 32 kbit/s PBR = 32 kbit/s
multimedia-conference-capable
UC terminals that have min-GBR (DL) = 32 min-GBR (DL) = 32
accessed the CPE is less than kbit/s kbit/s
or equal to half of the
maximum number of UC
terminals that are allowed to
access the CPE:

 PBR = 64 kbit/s
 min-GBR (DL) = 64 kbit/s

When the number of

multimedia-conference-capable
UC terminals that have
accessed the CPE is greater
than half of the maximum
number of UC terminals that
are allowed to access the CPE:

 PBR = 128 kbit/s

 min-GBR (DL) = 128
kbit/s

QCI = 9 When the number of UC PBR = 8 kbit/s PBR = 8 kbit/s

terminals that have accessed
the CPE is less than or equal to min-GBR (DL) = 8 kbit/s min-GBR (DL) = 8 kbit/s
half of the maximum number
of UC terminals that are
allowed to access the CPE:

 PBR = 16 kbit/s
 min-GBR (DL) = 16 kbit/s

When the number of UC

terminals that have accessed
the CPE is greater than half of
the maximum number of UC
terminals that are allowed to
access the CPE:

 PBR = 32 kbit/s
 min-GBR (DL) = 32 kbit/s

2014-9-29 错误！未知的文档属性名称.
  1. One G.711 audio bit rate is the value of 100 kbit/s multiplied by the redundancy
factor. The redundancy factor is 1.2. The redundancy factors in the following
descriptions are also 1.2.
 2. For the eSpace Mobile accessed using a handset, the video bit rate of P2P call
on the GBR bearer is set to one H.264/QVGA/15fps video bit rate that is the value
of 192 kbit/s multiplied by the redundancy factor.
 3. For the eSpace Desktop accessed using a dongle, the video bit rate of P2P call
on the GBR bearer is set to one H.264/720P/15fps video bit rate that is the value
of 1200 kbit/s multiplied by the redundancy factor.
 4. For a CPE, the AMBR allows that all the lower terminals are eSpace Desktops
and supports simultaneous multimedia conference services on all the eSpace
Desktops.
 5. For a handset, the AMBR supports various services on the eSpace Mobile,
including the multimedia conference service.
The maximum bandwidths for traffic flows in a multimedia conference service are as
follows:
Uplink: One H.264/QVGA/15fps video bit rate, which is 192 kbit/s.
Downlink: one H.264/QVGA/15fps video bit rate + one screen sharing bit rate, that is,
192 kbit/s + 200 kbit/s
 6. For a dongle, the AMBR supports various services on the eSpace Desktop,
including the multimedia conference service. (In the mobility restriction scenario,
one 720p video is supported in the downlink.)
The maximum bandwidths for traffic flows in a multimedia conference service are as
follows:
Uplink: one H.264/720p/15fps video bit rate + one H.264/QCIF/15fps video bit rate +
one screen sharing bit rate, that is, 1200 kbit/s + 60 kbit/s + 200 kbit/s
Downlink: one H.264/720p/15fps video bit rate + one screen sharing bit rate, that is,
1200 kbit/s + 200 kbit/s
 7. The purpose of configuring PBRs and min-GBRs is to prevent the data rate of
services carried on the corresponding bearers from dropping to zero.
PBRs can be configured for bearers with the QCIs of 2, 3, 4, 6, 7, 8, and 9.
Min-GBRs are defined by Huawei and can be configured for non-GBR bearers with
the QCIs of 6, 7, 8, and 9 to guarantee the minimum bit rate. Min-GBRs apply only to
the downlink.

2014-9-29 错误！未知的文档属性名称.