WGFD-050400 Conversational Traffic Class QoS Service Bearing http://localhost:7890/printtopics.html?time=Tue Feb 24 2015 11:29:48...

WGFD-050400 Conversational Traffic Class QoS

Service Bearing
Contents
3.6.2.6.4 WGFD-050400 Conversational Traffic Class QoS Service Bearing

3.6.2.6.4 WGFD-050400 Conversational Traffic Class QoS Service Bearing

Definition
Benefits
Requirements

Impact on the System

Application Limitations
Interaction with Other Features
Application Scenario
Implementation Principle
Specifications

Standard Compliance
Release History
Related Topics

Definition

Conversational quality of service (QoS) guarantee means that the GGSN9811 performs operations such as traffic
classification, QoS remark, bandwidth management, and sending packets in the high-priority queue on data packets
when sending packets to ensure the forwarding of conversational service data.

Benefits

For... Benefits

Carriers This feature enables carriers to provide high-quality video and audio services for
subscribers.

Subscribers This feature enables subscribers to enjoy better guaranteed video and audio services.

Requirements

Involved NEs

Table 1 lists the network elements (NEs) involved in implementing the conversational QoS guarantee feature.

1 of 6 2/24/2015 11:29 AM
WGFD-050400 Conversational Traffic Class QoS Service Bearing http://localhost:7890/printtopics.html?time=Tue Feb 24 2015 11:29:48...

Table 1 NEs involved in implementing the conversational QoS guarantee feature

MS RNC SGSN GGSN CG OCS PCRF M2000

√ √ √ √ - - - -

NOTE:
In table, the sign √ indicates that the NE is required, and - indicates that the NE is not required.

Functions of the NEs

Table 2 Functions of the NEs involved in implementing the conversational QoS guarantee feature
NE Function Description

GGSN Performs operations such as traffic classification, QoS remark, bandwidth

management, and sending packets in the high-priority queue on data packets to
ensure the forwarding of service data.

SGSN Performs QoS negotiation with the GGSN.

Supporting Versions
Table 3 lists the versions of Huawei GGSN9811 that supports the conversational QoS guarantee feature.

Table 3 Versions of Huawei GGSN9811 that supports the conversational QoS guarantee feature
Product Earliest Supporting Version

GGSN9811 V900R007C01 or later

SGSN None

Requirement for the License

This feature is an optional feature and requires a license. The license control item for this feature is "PDP Context
Numbers of Supporting Service Control-Conversational Traffic Class QoS Service Bearing".

Impact on the System

To implement conversational QoS guarantee, bandwidth management must be enabled for all the traffic on the
GGSN and the QoS remark function must be enabled for conversational services. This, however, reduces the
forwarding performance to some extent.

Application Limitations

No application limitation is involved.

Interaction with Other Features

No interaction with other features is involved.

Application Scenario

This feature is applicable to the scenario where IP-based session services such as voice over IP (VoIP), video calls,
and video conferences require high-level service guarantee.

2 of 6 2/24/2015 11:29 AM
WGFD-050400 Conversational Traffic Class QoS Service Bearing http://localhost:7890/printtopics.html?time=Tue Feb 24 2015 11:29:48...

Implementation Principle

Related Concepts

End-to-end (E2E) QoS on the mobile packet network

To implement E2E QoS, the clearly defined bearer service must be established when a service is initiated
and stopped on the mobile packet network. In 3rd Generation Partnership Project (3GPP) 23.107, the E2E
QoS system structure and QoS guarantee methods of the universal mobile telecommunications system
(UMTS) are clearly defined, as shown in Figure 1.

Figure 1 E2E QoS on the mobile packet network

According to the QoS system structure of the UMTS in Figure 1, the bearer service at each layer is
provided by the bearer service of the lower layer.

Take a 3G terminal using a packet data service as an example. The service used by the 3G terminal
usually needs to pass the user equipment (UE) such as the terminal equipment (TE) and mobile terminal
(MT), radio access network (RAN) equipment such as the eNodeB and radio network controller (RNC),
serving GPRS support node (SGSN), and gateway GPRS support node (GGSN) to reach the Internet
server. Based on the QoS system structure of the UMTS, the packet data service needs to be guaranteed
by the following QoS systems:
Radio access bearer QoS between the UE and the SGSN
The RAB QoS is composed of the GPRS Tunnel Protocol (GTP) tunnel between the RNC and
the SGSN and the radio bearer QoS between the RNC and the UE. The backbone network
bearer QoS and bottom layer physical bearer QoS are also used during transmission.

3 of 6 2/24/2015 11:29 AM
WGFD-050400 Conversational Traffic Class QoS Service Bearing http://localhost:7890/printtopics.html?time=Tue Feb 24 2015 11:29:48...

GTP tunnel QoS between the SGSN and the GGSN

QoS negotiation
The GGSN performs QoS negotiation according to the requested QoS (QoS Requested) carried in the
context activation request of a mobile station (MS) and the QoS configured on the GGSN, and then sends
the negotiation result (QoS Negotiated) to the MS through the context activation response message.
QoS mapping and remark
Mobile service data flows are transmitted among NEs over the IP network. Therefore, 3GPP QoS
parameters are mapped and remarked to the IP network to implement the QoS guarantee of the packet
data transmitted among NEs.
The GGSN can map the 3GPP QoS parameters negotiated during context activation to the differentiated
services code point (DSCP) or type of service (ToS) on the IP network according to certain rules. The
transmission device on the IP network then senses the DSCP or ToS to perform QoS guarantee.
Bandwidth management
In 3GPP, there are many means of implementing QoS guarantee for the packet data transmitted among
NEs, such as the access control in session management and bandwidth restriction during packet data
transmission.
The GGSN can reserve bandwidth resources for each Packet Data Protocol (PDP) context that has
requirement for bandwidth guarantee during activation. If the remaining bandwidth resources cannot meet
the activation request of the PDP context, the GGSN restricts the bandwidth resources that are actually
occupied by each PDP context during packet data transmission to prevent PDP contexts from preempting
bandwidth resources and to ensure the bandwidth resources used by each PDP context.

Queue scheduling
In 3GPP, there are many means of QoS guarantee for the packet data transmitted among NEs, such as
queue scheduling during packet data transmission. Various queue scheduling algorithms are supported on
the GGSN, such as first in first out (FIFO), priority queuing (PQ), and weighted fair queuing (WFQ).

System Implementation
In 3GPP UMTS QoS, traffic is classified into four classes based on the degree of sensitivity to delay: conversational,
streaming, interactive, and background. As shown in Table 4, the conversational class is the most sensitive to delay
and the background class is the least sensitive to delay.

Conversational and streaming classes are used to carry real-time data flows. The difference between the
two classes is the degree of sensitivity to delay. The conversational class is typically applied to voice calls
and video conferences; the streaming class is typically applied to real-time audio and video streams.
Interactive and the background classes are used for traditional Internet applications. Compared with
conversational and streaming services, interactive and background services are less sensitive to delay.
The interactive class is used for interactive applications such as the interactive Web browsing whereas the
background class is used for background traffic such as background file downloading. Therefore, the
priority of the interactive applications is higher than that of background applications. Background
applications can use bandwidth resources only when interactive applications do not use relay resources.
This is especially important in radio networking and the scenario of fixed bandwidth.

Table 4 Service types

Service Type Function Description Application Example

Conversational Time relations among the information entities are kept in the Voices
traffic. Conversational model features compact and low

4 of 6 2/24/2015 11:29 AM
WGFD-050400 Conversational Traffic Class QoS Service Bearing http://localhost:7890/printtopics.html?time=Tue Feb 24 2015 11:29:48...

Service Type Function Description Application Example

delay.

Streaming Time relations among the information entities are kept in the Videos
traffic.

Interactive The request-response mode is adopted. Effective load Web browsing

content is ensured.

Background Data is not expected to arrive in a certain time. Effective Background email
load content is ensured. downloading

1. When using a conversational service, an MS initiates the process of activating or updating a PDP
context.
The MS initiates a PDP context activation or update request. In the request, the requested
QoS parameters, such as the Traffic class, guaranteed bit rate (GBR), and maximum bit rate
(MBR) are carried.
After receiving the request, the RNC initiates a PDP activation or update request carrying
requested QoS parameters to the SGSN.
After receiving the request, the SGSN interacts with the home location register (HLR) to
obtain subscription information. The SGSN checks whether the values of the requested QoS
parameters are within the allowed ranges specified in the subscription information, obtains the
initially negotiated QoS parameters, and then initiates a PDP context activation or update
request to the GGSN.
After receiving the request, the GGSN obtains the QoS control policy from the local or
external device, accepts or modifies the requested QoS parameters, determines whether to
accept the activation or update request according to the remaining bandwidth resources of the
system, and then sends a PDP activation or update response message to the SGSN. If the
GGSN accepts the activation or update request, the QoS parameters confirmed during
negotiation must be carried in the response message.

After receiving the response message, the SGSN or RNC obtains the QoS parameters
confirmed during negotiation, reserves bandwidth resources, and then sends the response
message to the MS.
If the actual traffic of the MS exceeds the negotiated maximum bandwidth, the excess part is
discarded. The traffic between the guaranteed bandwidth and the maximum bandwidth is
forwarded in low priority, the traffic within the guaranteed bandwidth is forwarded in high
priority, and the PQ scheduling means is provided for the PHB (per-hop behavior) whose type
is expedited forwarding (EF) by default.
The data flows subsequently sent by the MS through the PDP context can have the QoS
guarantee.

2. Forwarding flow when the MS is using a conversational service

During data forwarding, the GGSN maps the traffic of the conversational service to the DSCP or ToS,
matches the traffic to a service rule according to the service class, traffic attributes (uplink or downlink
direction and time range), and subscriber attributes (RAT and roaming attributes). Based on the policy of
the service rule, the GGSN performs bandwidth management on the traffic of conversational services,
thus forwarding the traffic conversational services with short delay and high priority.

5 of 6 2/24/2015 11:29 AM
WGFD-050400 Conversational Traffic Class QoS Service Bearing http://localhost:7890/printtopics.html?time=Tue Feb 24 2015 11:29:48...

NOTE:
In the Internet Engineering Task Force (IETF), three PHBs are defined: EF, assured forwarding (AF), and
best-effort (BE).
The default rule of mapping 3GPP QoS parameters to IP QoS parameters is to map the DSCP value of a
conversational service to the DSCP value of the PHB whose type is EF.

Specifications

Table 5 lists the specifications of the local QoS control feature.

Table 5 Specifications of the local QoS control feature

Item Specifications

APN 3000

qos-profile 1000

Standard Compliance

Table 6 lists the standards with which the conversational QoS guarantee feature complies.

Table 6 Standards with which the conversational QoS guarantee feature complies
Category Name

3GPP 3GPP TS 23.060 General Packet Radio Service (GPRS) Service Description; Stage 2

3GPP TS 23.107 Quality of Service (QoS) concept and architecture

3GPP TS 24.008 Mobile radio interface Layer 3 specification; Core network protocols; Stage
3

Release History

Table 7 describes the release history of the conversational QoS guarantee feature.

Table 7 Release history of the conversational QoS guarantee feature

Feature Version Product Version Details

1 GGSN9811 V900R007C01 This feature is released for the first

time.

Related Topics

Feature Deployment
Activating the Conversational QoS Guarantee Feature
Commissioning PDP Context-based Access QoS Control
Deactivating the Conversational QoS Guarantee Feature

Parent topic: WGFD-400000 Service Control

6 of 6 2/24/2015 11:29 AM