Huawei HQoS

Technical White Paper

Huawei HQoS
Technical White Paper
Abstract ............................................................................................................................1
1 Overview .......................................................................................................................2
1.1 OAN ..............................................................................................................................2
1.2 HQoS Requirements Scenario ........................................................................................4
1.3 HQoS Concepts .............................................................................................................6
2 Solution .........................................................................................................................7
2.1 HQoS Service Model ......................................................................................................7
2.2 HQoS Implementation ...................................................................................................7
Acronyms and Abbreviations ...........................................................................................10
1
Abstract
Hierarchical quality of service (HQoS) is a QoS technology that hierarchically
controls services and users in an open access network (OAN). It controls not
only bandwidth of different services under a content provider (CP) but that
of a user. Using HQoS, traffic within the committed information rate (CIR)
passes absolutely, and traffc with the peak information rate (PIR) passes fairly.
This technical white paper covers the basic HQoS concepts, principle, and
procedure, and analyzes HQoS requirements and technologies according to
specifc scenarios.
HQoS user: In this technical white paper, HQoS users are level-1 users. At this
level, the total bandwidth of an HQoS user is controlled and when congestion
occurs, the bandwidth of each HQoS user can be ensured.
HQoS user group: In this technical white paper, an HQoS user group is a
type of service under a CP. At this level, bandwidth of each service in a CP is
ensured and when congestion occurs, CIR of each service is ensured, or even
PIR if remaining bandwidth permits.
CIR: When a user is provided with the CIR (assured bandwidth), all the traffc
within this bandwidth is allowed to pass.
PIR: Traffc confgured with PIR is allowed to exceed the assured bandwidth.
2
1 Overview
In the conventional IP network, all IP packets are treated equally. Each IP
device processes IP packets using the frst in frst out (FIFO) policy and sends
packets to their destinations with best effort. However, this practice does not
guarantee the packet transmission reliability, delay, and other performance
specifcations. Under such a background, carriers raise QoS requirements for
IP device deployment and operation over live networks.
The QoS technology includes packet classification, congestion avoidance,
congestion management, and traffc policing and shaping.
Packet classification: To classify IP packets according to the information
such as CoS priority, 802.1p priority of the L2 VLAN tag, and EXP feld of
MPLS for differentiated processing.
Congestion avoidance: To drop unqualifed packets in advance using the
random early detection (RED) or weighted random early detection (WRED)
technology in the case of congestion to ensure bandwidth for qualifed
services.
Congestion management: To manage traffc on a device using different
algorithms for queue scheduling. Such algorithms include priority queuing
(PQ) and weighted round robin (WRR).
Traffc policing and shaping: To balance and stabilize rates of ports on a
device to mitigate impact on the upper-layer devices, thereby achieving
traffic management. The common technologies used in traffic policing
and shaping include committed access rate (CAR) and shaping.
Backed by the preceding QoS technologies, the packet forwarding quality
of a device is greatly improved, compared with the original best-effort
forwarding. An OAN provides carriers with an end-to-end (E2E) service
channel, and different retail service providers (RSPs) provide services for users
with bandwidth leased by carriers. In such a network, to ensure bandwidth
experience of each user and manage bandwidth of different services, HQoS is
introduced.
1.1 OAN
OAN is an open and horizontally layered network architecture, in which the
access layer and the network layer are independent of each other without
affecting service provisioning. Different RSPs share the entire OAN, which
3
helps greatly reduce device investments and maintenance costs. The OAN is
able to provide more diversifed services for users and speed up information
exchange. With such features, it is a powerful weapon for carriers to boost
their competitive edges.
The following fgure shows the OAN model.
Figure 1-1 OAN model
Applications/services
Core
Access
CPE
Residential/Commercial Users
N
e
t
w
o
r
k

M
a
n
a
g
e
m
e
n
t

S
y
s
t
e
m
O
S
S
/
B
S
S
An OAN mainly consists of the CPE service layer, access layer, core layer, and
OSS and network management layer.
The CPE is mainly placed at user home and provides various services for
users.
The access-layer device aggregates data transmitted from the CPE and
then transmits the data upstream to the core layer.
The core-layer device provides service interoperability and routing for
different parts of the network.
The OSS and network management system is responsible for the OAN
management and maintenance and relevant service provisioning.
As shown in the following typical OAN topology, all RSPs can provision
services to end users through the wholesale service over the OAN. The access
system is a GPON system, which is able to provide users with higher access
bandwidth. From the CPE to the OLT, the OAN provides different service
channels for different RSPs, and the RSPs can select L2 or L3 devices for
service access. The end user can use only one physical port to fexibly choose
RSPs according to service tariff and experience and need not concern about
the actual network connection.
4
L3 POI
RSP
RSP a
Seamless
Interction
OSS/BSS OSS/BSS
Aggregation
OLT
ONT
Home Network
Splitter
Backbone Core
RSP b
RSP c
OpCo
Access
POI
L2 POI
VoIP Phone
TV
PC
STB
Figure 1-2 OAN topology
1.2 HQoS Requirements Scenario
OAN is an open architecture based on the GPON FTTH technology, with
a core concern for how to build a platform in which residential users
can be equally and freely connected to multiple CPs. In the DSL era, line
openness is generally implemented through copper line lease, which is
actually the openness of physical media. For the PON point-to-multipoint
(P2MP) communication, it is naturally monopolistic, and therefore leasing
wavelengths (spectra) at the access layer is not cost-effective. In this case,
leasing L2 connection and bandwidth through the OAN is a basic feature of
the OAN. To support L2 connection and bandwidth leasing, the OLT must
provide multiple and flexible upstream ports, multi-layer VLAN forwarding
and transforming, and HQoS support. OANs of certain carriers manage only
the network from the OLT to the ONT (including the ODN), and the upper-
layer devices of the OLT and lower-layer devices of the ONT (such as the
home network devices) are all provided by the CPs/RSPs. Generally, different
CPs use different upstream ports, but one CP can use multiple upstream
ports. Different CPs use different ports; therefore the CPs can have the entire
VLAN address space, and VLAN addresses of different CPs may overlap. The
following figure considers a certain carrier as an example to illustrate the
HQoS requirements.
5
As shown in the preceding figure, the carrier plans different products for
CPs on the OAN, and these products have requirements on the upstream
and downstream CIR and PIR of services. The following two services are
considered as an example:
Voice service, with 135 kbit/s CIR upstream and 135 kbit/s CIR downstream
but no PIR
Data service, with 2 Mbit/s CIR (no PIR) upstream and 10 Mbit/s CIR
bandwidth (burst to 30 Mbit/s) downstream
For certain private line services, services of multiple priorities can be provided.
When services of priorities P3 and P4 coexist, the service of a higher priority
occupies the CIR and PIR preferentially.
The conventional QoS, however, fails to ensure the service CIR or allocate PIR
according to the service priority. In such a background, HQoS is introduced.
Figure 1-3 OAN access architecture of a carrier
In Span
Hand-Over
CP Hand-Over Node External Network End User
In Building
Hand-Over
32 way split
32 way split
Port 1
Port 4
ONT 32
28dB
Out of Building
Hand-Over
Cable Lbb
Cable Lbb
Cable Lbb
Cable Lbb
Optical interfaces
Hand-Over Point
Existing Produets
ONBS
ONBS
CP 1
Out side
BT building
CP 2
In same
BT building
CP 3
Remote
Diff erent
BT building
CP 4
Remote
non
BT building
Open reach GEA Products
GEA Data Product
GEA Voice Enablement Product
GEA CP GigE Port Product
T R S
GPON
Line
Card
GPON
Line
Card
ONT 1
Port 1
Port 4
6
1.3 HQoS Concepts
HQoS is to ensure bandwidth of different services for different users, with
level 1 ensuring the bandwidth of all users and level 2 ensuring bandwidth of
different services of each user. This is different from the conventional traffc
management, which fails to ensure the bandwidth of each user on a port due
to its port-based bandwidth scheduling.
CP1
Port 1
User 1
User 2
User 3
User 4
Service 1
Service 2
Service 3
Service 4
Port 2
Figure 1-4 HQoS principle
As shown in the preceding figure, one CP occupies one or more upstream
ports and leases certain bandwidth of the OAN. Each upstream port has
multiple users, and the CP provides multiple access services for each user.
Hierarchical control is performed for services, users, and CPs. As such, HQoS
ensures bandwidth of all users and bandwidth of different services of each
user through the hierarchical scheduling mechanism.
7
2 Solution
2.1 HQoS Service Model
With regard to the HQoS service model in an OAN, CPs are provided with an
E2E L2 private line from the ONT to the OLT, in which services are forwarded
based on SVLAN+CVLAN. The following figure shows the HQoS service
model.
Figure 2-1 HQoS service model
Port1 c- tag=101
Port2 c- tag=102
Port3 c- tag=103
Port4 c- tag=104
Port1 c- tag=101
Port2 c- tag=102
Port3 c- tag=103
Port4 c- tag=104
OLT
CP1
CP2
port2
port1
Port+ (S +C ) /C S+C C
ONT
ONT
The ONT differentiates users by adding different CVLAN tags to packets
according to the port or service type. After a service is transmitted upstream
to the OLT, the OLT translates CVLAN into CVLAN' according to the PON port
information and then adds a unified SVLAN according to the service type.
The system uses SVLAN+CVLAN' to uniquely identify the service. The service
is then forwarded to a port (connected to the CP network) of an HQoS
processing board on the OLT. The HQoS processing board, according to the
CP's port plan, translates SVLAN+CVLAN' into SVLAN'+CVLAN''.
2.2 HQoS Implementation
Two-level CAR, which is the core of HQoS, is performed for services on the
HQoS processing board. Level-1 CAR is a priority-based CAR for HQoS users,
in which traffc is marked in different colors for fair scheduling of different
services for users so that user CIR can be ensured. Level-2 CAR is a color-
based CAR that marks the same type of services in the same color, which
prevents a single type of services from occupying all the bandwidth in a CP. In
8
this way, different services are fairly scheduled to ensure CIR of each service,
or even PIR if bandwidth permits. The following fgure shows the two-level
CAR.
Figure 2-2 HQoS CAR processing
Port
Indicates a CP
CAR for one service
of the CP
CAR for one HQoS
user
Port + VLAN
Flow
The following figure shows the general HQoS solution on the HQoS
processing board.
1. Traffi c cl assi fi cati on: HQoS users are di fferenti ated based on
port+SVLAN+CVLAN on the upstream port of the HQoS processing board.
2. Priority-based CAR for an HQoS user: According to CIR and PIR of the
HQoS user, different packets of the HQoS user are marked in different colors.
Specifcally, packets at a rate within CIR are marked green, packets at a rate
Figure 2-3 General HQoS solution on the HQoS processing board
Priority-
based CAR
for users
Port+SVLAN
color-based
CAR
PQ
4
3
2
1
G Y
DEI =
0
7
DEI =
1
0
6
Traffic
classification
9
between CIR and PIR are marked yellow, and packets at a rate exceeding PIR
are dropped. During coloring, the packet priority also needs to be considered.
That is, packets with a higher priority occupy CIR and PIR of the HQoS user
preferentially.
3. Color-based CAR for an HQoS user group: Green packets can pass. Yellow
packets, if the remaining bandwidth following the passing of green packets
permits, can also pass; otherwise, yellow packets are dropped. Yellow packets
cannot be escalated to green packets.
4. All HQoS users entering the queue of a same priority on the egress: The
queue implements color-based WRED. When the congestion threshold is
reached, yellow packets are dropped.
10
Acronym/Abbreviation Full Name
QoS quality of service
HQoS hierarchical QoS
TM traffc manager
BE best effort
EF expedited forwarding
AF assured forwarding
CIR committed information rate
CBS committed burst size
PIR peak information rate
PBS peak burst size
RED random early detection
WRED weighted random early detection
WRR weighted round robin
WFQ weighted fair queuing
PQ priority queuing
Acronyms and Abbreviations
11
Copyright Huawei Technologies Co., Ltd. 2010. 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.
Trademark Notice
, HUAWEI, and are trademarks or registered trademarks of Huawei Technologies Co., Ltd.
Other trademarks, product, service and company names mentioned are the property of their respective owners.
NO WARRANTY
THE CONTENTS OF THIS MANUAL ARE PROVIDED AS IS. EXCEPT AS REQUIRED BY APPLICABLE LAWS,
NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE MADE IN
RELATION TO THE ACCURACY, RELIABILITY OR CONTENTS OF THIS MANUAL.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO CASE SHALL HUAWEI
TECHNOLOGIES CO., LTD BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL
DAMAGES, OR LOST PROFITS, BUSINESS, REVENUE, DATA, GOODWILL OR ANTICIPATED SAVINGS
ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS MANUAL.
HUAWEI TECHNOLOGIES CO., LTD.
Huawei Industrial Base
Bantian Longgang
Shenzhen 518129, P.R. China
Tel: +86-755-28780808
Version No.: M3-013030802-20100830-C-1.0
www.huawei.com