Internal Use Only▲

Qos setting introduction

Layer 2 QoS standards

802.1p (dot1p)
There is currently only one QoS standard in widespread use on LANs for priority marking of
frames at Layer2.
This is the IEEE 802.1p standard, which specifies 8 priority levels, called Class of Service (CoS)
levels. These are numbered 0-7, with 0 being the lowest priority and 7 the highest. CoS level 0 is
the default for most frames.
A frames CoS level is marked using 3 bits in the Tag Control Information (TCI) field in the 802.3
Layer 2 frame header:

The 8 CoS priority levels are named as follows. Note that for simplicity these are named the same
as the 8 priority levels provided at Layer3 by the IP Precedence standard discussed in the next
section:
Decimal value Binary (802.1p bits) CoS name
0 000 Routine
1 001 Priority
2 010 Immediate
3 011 Flash
4 100 Flash Override
5 101 Critical
6 110 Internetwork Control
7 111 Network Control

<以上所有信息均为中兴通讯股份有限公司所有，不得外传> 第1页
All Rights reserved, No Spreading without Permission of ZTE
 Internal Use Only▲

Layer 3 QoS standards

Type of Service (ToS)

The ToS standard, as defined by RFC1349, can be used to mark packets with 5 levels of priority:
Normal-Service Minimize-Cost Maximize-Reliability Maximize-Throughput Minimize-Delay Earlier
versions of the ToS RFC only defined 4 types of service, they did not include “Minimize Cost”. The
“Minimize-Cost” ToS attempts to minimize the financial cost of passing traffic, not to be confused
with normal IP routing protocols which try to route packets based on minimum “Hops” or
”Metrics”, often referred to as “Costs”. The required ToS is marked in a packet header by setting
or un-setting bits 4-7 of the ToS byte (note that bit 8, the MBZ (must be zero) bit, is always zero):
Bits, ToS byte: 1 2 3 4 5 6 7 8

IP Maximize
IP IP Minimize Maximize Minimize Unused
Precedenc Throughpu
Precedence Precedence Delay Reliability Cost MBZ
e t

Normal Service 0 0 0 0 0 0 0 0

Minimize Delay 0 0 0 1 0 0 0 0

Maximize
0 0 0 0 1 0 0 0
Throughput

Maximize
0 0 0 0 0 1 0 0
Reliability

Minimize Cost 0 0 0 0 0 0 1 0

<以上所有信息均为中兴通讯股份有限公司所有，不得外传> 第2页
All Rights reserved, No Spreading without Permission of ZTE
 Internal Use Only▲

IP Precedence

The IP Precedence standard uses the first 3 bits of the ToS byte to mark packets with 8 levels of
priority, numbered 0-7, with 0 being the lowest priority and 7 the highest. These levels are given
the same names as the 8 priority levels provided at Layer2 by the 802.1p standard :
Bits, ToS byte: 1 2 3 4 5 6 7 8

IP Maximize
IP IP Minimize Maximize Minimize Unused
Precedenc Throughpu
Precedence Precedence Delay Reliability Cost MBZ
e t

Routine 0 0 0 0 0 0 0 0

Priority 0 0 1 0 0 0 0 0

Immediate 0 1 0 0 0 0 0 0

Flash 0 1 1 0 0 0 0 0

Flash
1 0 0 0 0 0 0 0
Override
Critical 1 0 1 0 0 0 0 0

Internetwork
1 1 0 0 0 0 0 0
Control
Network
1 1 1 0 0 0 0 0
Control

<以上所有信息均为中兴通讯股份有限公司所有，不得外传> 第3页
All Rights reserved, No Spreading without Permission of ZTE
 Internal Use Only▲

Differentiated Services Code Point

The DiffServ standard uses the first 3 bits of the ToS byte to mark packets with 6 levels of priority,
called Class Selectors (CS). These are called “default”, CS1, CS2, CS3, CS4 and “Expedited
Forwarding(EF)” , and to maintain backward compatibility they correspond exactly to the first 6
priority levels specified by the IP Precedence standard:
DiffServ Class IP Precedence
bit 1 bit 2 bit 3 Decimal value
Selector name
0 0 0 0 default Routine

0 0 1 1 CS1 Priority

0 1 0 2 CS2 Immediate

0 1 1 3 CS3 Flash

1 0 0 4 CS4 Flash Override

1 0 1 5 EF Critical

1 1 0 6 Internetwork Control

1 1 1 7 Network Control

The DiffServ standard also uses the next 3 bits (bits 4,5 and 6) of the ToS byte to mark packets
with a Drop Precedence. The standard specifies that bit 6 always has a value of zero and is
ignored. This leaves 2 bits (bits 4 and 5), giving 4 possible values of Drop Precedence:
bit 4 bit 5 Decimal value DiffServ Drop Precedence
0 0 0 default

<以上所有信息均为中兴通讯股份有限公司所有，不得外传> 第4页
All Rights reserved, No Spreading without Permission of ZTE
 Internal Use Only▲

0 1 1 Low Drop Probability

1 0 2 Medium Drop Probability
1 1 3 High Drop Probability
The first 6 bits of the ToS byte, used to mark packets with a DiffServ Class Selector and Drop
Precedence, are called the Differentiated Services Code Point (DSCP). The final 2 bits of the ToS
byte may be unused, or they may be used for Explicit Congestion Notification (ECN):
Bits:1 2 3 4 5 6 7 8
Drop Drop Drop
Priority Priority Priority Unused Unused
Precedence Precedence Precedence
Class Selector Drop Precedence Ignore Unused or ECN
Differentiated Services Code Point (DSCP)
There is a naming standard for various combinations of Class Selector and Drop Precedence. This
is: “Assured Forwarding (AF)” ,Note that although the DSCP is 6 bits long and could therefore hold
64 values, this table shows that only 14 of those possible values are valid values.

ZTE 3G IP interface qos mapping

For each IP interface on RNC, DSCP value can be mapped to desired COS value
flexibly. The default mapping relation is shown in the table below:

Table DSCP and COS default Mapping Relationships

<以上所有信息均为中兴通讯股份有限公司所有，不得外传> 第5页
All Rights reserved, No Spreading without Permission of ZTE
 Internal Use Only▲

User can configure the DSCP (INFO3_BIT05) for signaling transmission and the DSCP (IUIpDscp[],

DSCP COS
0~7 0
8~15 1
16~23 2
24~31 3
32~39 4
40~47 5
48~55 6
56~63 7

IubCChIpDscp, IpDscp or IpTos) for service transmission on the OMCR.

RNC offers two methods to transfer the QoS mapping (QosProfileType) and set DSCP flags for
different services.

Method 1: Configure the QoS in combination with the ARP/THP/TC. Classify

services into the basic priority segment (BPSeg) based on the mapping between
the traffic category (Traffic Class and THP) and user priorities (ARP), and then
configure the QoS flag (IpDscp) for each BPSeg based on the BearerType (DCH,
HSPA and MBMS).

Method 2: Configure the QoS flag (IpTos) directly based on the traffic category
(TrafficCategory).

The following table is the default DSCP mapping value for various type of traffic.

Table Default DSCP Marks for lub/Iur Interface according to ARP/THP/TC

DSCP IP
Traffic Type Remark
(Bit) TOS
Iub NBAP Signaling[1] 101110 0xB8 EF(Expedited Forwarding)
Iub Common Transport Channel[1] 101110 0xB8 EF(Expedited Forwarding)
RRC Connection[2] 100100 0x90 AF42(Class4, Med Drop)
R99 Conversational[2] 100100 0x90 AF42(Class4, Med Drop)
R99 Streaming[2] 100100 0x90 AF42(Class4, Med Drop)
R99 Interactive[2] 010100 0x50 AF22(Class2, Med Drop)
R99 Background[2] 000000 0x00 Best effort
HSPA Conversational[2] 100110 0x98 AF43(Class4, High Drop)
HSPA Streaming[2] 100110 0x98 AF43(Class4, High Drop)

<以上所有信息均为中兴通讯股份有限公司所有，不得外传> 第6页
All Rights reserved, No Spreading without Permission of ZTE
 Internal Use Only▲

DSCP IP
Traffic Type Remark
(Bit) TOS
HSPA Interactive[2] 010110 0x58 AF23(Class2, High Drop)
HSPA Background[2] 000000 0x00 Best effort
O&M[3] 000000 0x00 Best effort
Clock over IP (PTP) [3] 101110 0xB8 EF(Expedited Forwarding)
SLA[3] 110000 0xc0 CS
[3]
BFD 000000 0x00 Best effort
[1] Uplink traffic is not configurable.
[2] Both uplink and downlink are configurable.
[3] Both uplink and downlink are not configurable.

Table Default DSCP Marks for lub/Iur Interface according to traffic category

TrafficCategory DSCP (Bit) IpTos Remark

0(R99 Signal) 100100 0x90 AF42(Class4, Med Drop)
1(HSDPA Signal) 100110 0x98 AF43(Class4, High Drop)
2(HSUPA Signal) 100110 0x98 AF43(Class4, High Drop)
3(R99 AMR) 100100 0x90 AF42(Class4, Med Drop)
4(HSDPA AMR) 100110 0x98 AF43(Class4, High Drop)
5(HSUPA AMR) 100110 0x98 AF43(Class4, High Drop)
6(R99 Video) 100100 0x90 AF42(Class4, Med Drop)
7(HSDPA Video) 100110 0x98 AF43(Class4, High Drop)
8(HSUPA Video) 100110 0x98 AF43(Class4, High Drop)
9(R99 CS conversational (D side)) 100100 0x90 AF42(Class4, Med Drop)
10(R99 CS streaming) 010100 0x50 AF22(Class2, Med Drop)
11(R99 PS conversational) 100100 0x90 AF42(Class4, Med Drop)
12(R99 PS streaming) 010100 0x50 AF22(Class2, Med Drop)
13(R99 PS interactive high priority) 010100 0x50 AF22(Class2, Med Drop)
14(R99 PS interactive middle priority) 000000 0x00 Best effort
15(R99 PS interactive low priority) 000000 0x00 Best effort
16(R99 PS background) 000000 0x00 Best effort
17(HSDPA conversational (D side)) 100110 0x98 AF43(Class4, High Drop)
18(HSDPA streaming) 010110 0x58 AF23(Class2, High Drop)
19(HSDPA interactive high priority) 010110 0x58 AF23(Class2, High Drop)

<以上所有信息均为中兴通讯股份有限公司所有，不得外传> 第7页
All Rights reserved, No Spreading without Permission of ZTE
 Internal Use Only▲

20(HSDPA interactive middle priority) 000000 0x00 Best effort

21(HSDPA interactive low priority) 000000 0x00 Best effort
22(HSDPA background) 000000 0x00 Best effort
23(HSUPA conversational (D side)) 100110 0x98 AF43(Class4, High Drop)
24(HSUPA streaming) 010110 0x58 AF23(Class2, High Drop)
25(HSUPA interactive high priority) 010110 0x58 AF23(Class2, High Drop)
26(HSUPA interactive middle priority) 000000 0x00 Best effort
27(HSUPA interactive low priority) 000000 0x00 Best effort
28(HSUPA background) 000000 0x00 Best effort
29(MBMS streaming) 010100 0x50 AF22(Class2, Med Drop)
30(MBMS interactive high priority) 010100 0x50 AF22(Class2, Med Drop)
31(MBMS interactive middle priority) 000000 0x00 Best effort
32(MBMS interactive low priority) 000000 0x00 Best effort
33(MBMS background) 000000 0x00 Best effort
34(IMS Signaling) 100100 0x90 AF42(Class4, Med Drop)

Table 3-1 DSCP Marks of Default Messages on lu Interface

DSCP IP
Traffic Type Remark
(Bit) TOS
Signalling (RANAP) 101110 0xB8 EF(Expedited Forwarding)
Conversational 100100 0x90 AF42(Class4, Med Drop)
Streaming 100100 0x90 AF42(Class4, Med Drop)
Interactive 010100 0x50 AF22(Class2, Med Drop)
Background 000000 0x00 Best effort
SLA 110000 0xc0 CS
BFD 000000 0x00 Best effort

According to the above rule, The RNL layer QOS mark would mapped into TNL
layer QOS mark. All the implementations should follow the RFC 2475 (system
architecture of DiffServ) and RFC 2474 (definition of DiffServ field (DS) of IPv4 and
IPv6 headers).

<以上所有信息均为中兴通讯股份有限公司所有，不得外传> 第8页
All Rights reserved, No Spreading without Permission of ZTE
 Internal Use Only▲

ZTE 2G DiffServ Based QoS Feature

Case Tested

Libyana and ZTE tested this case at Misrata area link, decrease the bandwidth to make the
transmission congestion on 2017-11-18

When DSCP configuration done, seen that the CS traffic keep increasing and PS traffic decrease.

CS and PS traffic during band width limited

1400000.0000 120.0000
1200000.0000 100.0000
1000000.0000
80.0000
800000.0000
60.0000
600000.0000
40.0000
400000.0000
200000.0000 20.0000
0.0000 0.0000
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
:0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0
:00 :30 :00 :30 :00 :30 :00 :30 :00 :30 :00 :30 :00 :30 :00 :30 :00
12 12 13 13 14 14 15 15 16 16 17 17 18 18 19 19 20

300681:Cell DL Traffic Volume, PS(FP)(kBytes) 300532:Cell Traffic Volume, CS(Erl)

<以上所有信息均为中兴通讯股份有限公司所有，不得外传> 第9页
All Rights reserved, No Spreading without Permission of ZTE