ETSI TS 123 107 V8.2.0 (2012-01)

Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Quality of Service (QoS) concept and architecture (3GPP TS 23.107 version 8.2.0 Release 8)

RTS/TSGS-0223107v820

General Information

• Status: Published
• Publication Date: 08-Jan-2012
• Technical Committee: 3GPP SA 2 - Architecture
• Current Stage: 12 - Completion
• Due Date: 03-Jan-2012
• Completion Date: 09-Jan-2012

Standards Content (Sample)

Technical Specification
Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
LTE;
Quality of Service (QoS) concept and architecture
(3GPP TS 23.107 version 8.2.0 Release 8)

3GPP TS 23.107 version 8.2.0 Release 8 1 ETSI TS 123 107 V8.2.0 (2012-01)

Reference
RTS/TSGS-0223107v820
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2012.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 2 ETSI TS 123 107 V8.2.0 (2012-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 3 ETSI TS 123 107 V8.2.0 (2012-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Abbreviations . 6
4 High Level Requirements . 7
4.1 End User QoS Requirements . 7
4.2 General Requirements for QoS . 8
4.3 Technical Requirements for QoS . 8
5 CS QoS in release 1999 . 9
6 QoS Architecture . 9
6.1 Overview of Different Levels of QoS . 9
6.1.1 The End-to-End Service and UMTS Bearer Service . 10
6.1.2 The Radio Access Bearer Service and the Core Network Bearer Service . 10
6.1.3 The Radio Bearer Service and the RAN Access Bearer Service . 11
6.1.4 The Backbone Network Service . 11
6.2 QoS Management Functions in the Network . 11
6.2.1 Description of functions . 12
6.2.1.1 QoS management functions for UMTS bearer service in the control plane . 12
6.2.1.2 Functions for UMTS bearer service in the user plane . 12
6.2.2 Allocation of QoS management functions . 12
6.2.2.1 QoS management functions for UMTS bearer service in the control plane . 12
6.2.2.2 QoS management functions for the UMTS bearer service in the user plane . 14
6.3 UMTS QoS Classes . 15
6.3.1 Conversational class . 15
6.3.2 Streaming class . 16
6.3.3 Interactive class . 16
6.3.4 Background class . 16
6.4 QoS Attributes . 17
6.4.1 Asymmetric Bearers . 17
6.4.2 Sources of UMTS Bearer Service Attributes . 17
6.4.3 UMTS Bearer Service Attributes . 18
6.4.3.1 List of attributes . 18
6.4.3.2 Attributes discussed per traffic class . 20
6.4.3.3 UMTS bearer attributes: summary . 22
6.4.4 Radio Access Bearer Service Attributes . 22
6.4.4.1 List of attributes . 22
6.4.4.2 Attributes discussed per traffic class . 25
6.4.4.3 Radio Access Bearer attributes: summary . 26
6.4.5 Radio Bearer Service Attributes . 26
6.4.6 RAN Access Bearer Service Attributes . 27
6.4.7 Core Network Bearer Service Attributes . 27
6.5 Attribute Value Ranges . 27
6.5.1 Ranges of UMTS Bearer Service Attributes . 27
6.5.2 Ranges of Radio Access Bearer Service Attributes for UTRAN and for GERAN . 28
7 Void . 29
8 QoS Attribute Mapping . 29
8.1 From Application Attributes to UMTS Bearer Service Attributes . 29
8.2 From UMTS Bearer Service Attributes to Radio Access Bearer Service Attributes . 30
8.3 From UMTS Bearer Service Attributes to CN Bearer Service Attributes . 31
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 4 ETSI TS 123 107 V8.2.0 (2012-01)
9 Interworking . 31
9.1 UMTS-GSM CS/GPRS . 31
9.1.1 UMTS-GSM CS . 31
9.1.1.1 Handover from UMTS to GSM . 31
9.1.1.2 Handover from GSM to UMTS . 31
9.1.2 UMTS-GPRS . 31
9.1.2.1 General rules . 32
9.1.2.2 Determining R99 attributes from R97/98 attributes . 32
9.1.2.3 Determining R97/98 attributes from R99 attributes . 33
9.2 UMTS-PSTN . 34
9.3 UMTS-ISDN . 34
9.4 UMTS-Internet . 35
Annex A (informative): Error resilience in real-time packet multimedia payloads . 36
A.1 Introduction . 36
A.1.1 Factors affecting error resilience . 36
A.2 Example figures . 36
Annex B (normative): Reference Algorithm for Conformance Definition of Bitrate . 38
Annex C (normative): Determine which QoS profile is of highest QoS . 39
Annex D (normative): Determine Traffic Class weights in HLR QoS profile . 40
Annex E (informative): Change history . 41
History . 42

ETSI
3GPP TS 23.107 version 8.2.0 Release 8 5 ETSI TS 123 107 V8.2.0 (2012-01)
Foreword
rd
This Technical Specification (TS) has been produced by the 3 Generation Partnership Project (3GPP).
The present document identifies the Quality of Service (QoS) aspects for the 3GPP system.
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 6 ETSI TS 123 107 V8.2.0 (2012-01)
1 Scope
The present document provides the framework for Quality of Service within the 3GPP system. The main purpose is to
specify the list of attributes applicable to the UMTS Bearer Service and the Radio Access Bearer Service, as well as
describe the Quality of Service architecture to be used in the 3GPP system.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TS 23.110: "UMTS Access Stratum - Services and Functions".
[2] 3GPP TS 22.100: "UMTS Phase 1".
[3] 3GPP TS 23.121: "Architectural Requirements for Release 1999".
[4] Void.
[5] 3GPP TS 22.105: "Services & Service capabilities".
[6] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols –
Stage 3".
[7] 3GPP TS 23.207: "End-to-end QoS concept and architecture".
[8] 3GPP TS 23.008: "Organization of subscriber data".
[9] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) -
Stage 2".
[10] 3GPP TS 03.60 (Release 1998): "Digital cellular telecommunications system (Phase 2+); General
Packet Radio Service (GPRS); Service description; Stage 2 (Release 1998)".
[11] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
3 Abbreviations
For the purpose of the present document, the following abbreviations apply:
3G 3rd Generation
AMR Adaptive Multirate speech codec
ATM Asynchronous Transfer Mode
BER Bit Error Rate
BS Bearer Service
CC Call Control
CN Core Network
CRC Cyclic Redundancy Check
CS Circuit Switched
DTX Discontinuous Transmission
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 7 ETSI TS 123 107 V8.2.0 (2012-01)
FDD Frequency Division Duplex
FER Frame Erasure Ratio
FTP File Transfer Protocol
GERAN GSM/EDGE Radio Access Network
GPRS General Packet Radio Service
GSM Global System for Mobile Communication
IETF Internet Engineering Task Force
IP Internet Protocol
ISDN Integrated Services Digital Network
MO Mobile Originating Call
MPEG Moving Pictures Expert Group
MT Mobile Terminal
MTC Mobile Terminated Call
NS Network Service
PDP Packet Data Protocol
PDU Protocol Data Unit
PS Packet Switched
PSTN Public Switched Telephone Network
QoS Quality of Service
RA Routing Area
RAB Radio Access Bearer
RAN Radio Access Network
RLC Radio Link Control
RSVP Resource Reservation Protocol
RT Real Time
RTP Real Time Transport Protocol
SAP Service Access Point
SDU Service Data Unit
SGSN Serving GPRS Support Node
SLA Service Level Agreement
SMS Short Message Service
SVC Switched Virtual Circuit
UDP User Datagram Protocol
TBC Token Bucket Counter
TDD Time Division Duplex
TE Terminal Equipment
TSPEC Traffic Specification
UE User Equipment
UMTS Universal Mobile Telecommunication System
UTRA UMTS Terrestrial Radio Access
UTRAN UMTS Terrestrial Radio Access Network
4 High Level Requirements
4.1 End User QoS Requirements
Generally, end users care only the issues that are visible to them. The involvement of the user leads to the following
conclusions. From the end-user point of view:
- only the QoS perceived by end-user matter;
- the number of user defined/controlled attributes has to be as small as possible;
- derivation/definition of QoS attributes from the application requirements has to be simple;
- QoS attributes shall be able to support all applications that are used, a certain number of applications have the
characteristic of asymmetric nature between two directions, uplink/downlink;
- QoS definitions have to be future proof;
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 8 ETSI TS 123 107 V8.2.0 (2012-01)
- QoS has to be provided end-to-end.
4.2 General Requirements for QoS
- QoS attributes (or mapping of them) should not be restricted to one or few external QoS control mechanisms but
the QoS concept should be capable of providing different levels of QoS by using UMTS specific control
mechanisms (not related to QoS mechanisms in the external networks).
- All attributes have to have unambiguous meaning.
- QoS mechanism have to allow efficient use of radio capacity.
- Allow independent evolution of Core and Access networks.
- Allow evolution of UMTS network, (i.e., eliminate or minimise the impact of evolution of transport technologies
in the wireline world).
- All attribute combinations have to have unambiguous meaning.
4.3 Technical Requirements for QoS
This clause presents the general high-level technical requirements for the UMTS QoS. QoS will be defined with a set of
attributes. These attributes should meet the following criteria:
- UMTS QoS control mechanisms shall provide QoS attribute control on a peer to peer basis between UE and 3G
gateway node;
- the UMTS QoS mechanisms shall provide a mapping between application requirements and UMTS services;
- the UMTS QoS control mechanisms shall be able to efficiently interwork with current QoS schemes. Further, the
QoS concept should be capable of providing different levels of QoS by using UMTS specific control
mechanisms (not related to QoS mechanisms in the external networks);
- a session based approach needs to be adopted for all packet mode communication within the 3G serving node
with which UMTS QoS approach shall be intimately linked, essential features are multiple QoS streams per
address;
- the UMTS shall provide a finite set of QoS definitions;
- the overhead and additional complexity caused by the QoS scheme should be kept reasonably low, as well as the
amount of state information transmitted and stored in the network;
- QoS shall support efficient resource utilisation;
- the QoS attributes are needed to support asymmetric bearers;
- applications (or special software in UE or 3G gateway node) should be able to indicate QoS values for their data
transmissions;
- QoS behaviour should be dynamic , i.e., it shall be possible to modify QoS attributes during an active session;
- number of attributes should be kept reasonably low (increasing number of attributes, increase system
complexity);
- user QoS requirements shall be satisfied by the system, including when change of SGSN within the Core
Network occurs.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 9 ETSI TS 123 107 V8.2.0 (2012-01)
5 CS QoS in release 1999
For UMTS release '99 CS-CC, the QoS related bearer definitions of GSM (as defined in bearer capability information
element, octet 6 and its extensions) are sufficient.
Based on the Bearer Capability information element the following services can be identified:
a) speech: from the Information Transfer Capability (ITC) parameter;
b) data, non-transparent: from the ITC and Connection element (CE) parameters;
c) data, transparent: from the ITC and CE parameters.
For each of the above services, associated call control parameters, including the Bearer Capability information element,
can be considered to define the UMTS bearer service.
The further mapping to Radio Access Bearer attributes is done according to the principles described in clause 8.
NOTE: The mapping from GSM CC to UMTS RAB attributes is in the responsibility of CN WG1 and CN WG3.
6 QoS Architecture
6.1 Overview of Different Levels of QoS
Network Services are considered end-to-end, this means from a Terminal Equipment (TE) to another TE. An End-to-
End Service may have a certain Quality of Service (QoS) which is provided for the user of a network service. It is the
user that decides whether he is satisfied with the provided QoS or not.
To realise a certain network QoS a Bearer Service with clearly defined characteristics and functionality is to be set up
from the source to the destination of a service.
A bearer service includes all aspects to enable the provision of a contracted QoS. These aspects are among others the
control signalling, user plane transport and QoS management functionality. A UMTS bearer service layered architecture
is depicted in figure 1, each bearer service on a specific layer offers it's individual services using services provided by
the layers below.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 10 ETSI TS 123 107 V8.2.0 (2012-01)

UMTS
TE MT RAN CN TE
CN
Gateway
EDGE
NODE
End-to-End Service
TE/MT Local UMTUMTSS B Beeararerer SSeerrvviiccee External Bearer
Bearer Service Service
Radio Access Bearer Service CN Bearer
Service
Radio Bearer RAN Access Backbone
Service Bearer Service Bearer Service
Physical Radio Physical
Bearer Service Bearer Service
Figure 1: UMTS QoS Architecture
6.1.1 The End-to-End Service and UMTS Bearer Service
On its way from the TE to another TE the traffic has to pass different bearer services of the network(s). A TE is
connected to the UMTS network by use of a Mobile Termination (MT). The End-to-End Service on the application
level uses the bearer services of the underlying network(s). As the End-to-End Service is conveyed over several
networks (not only UMTS) it is not subject for further elaboration in the present document.
The End-to-End-Service used by the TE will be realised using a TE/MT Local Bearer Service, a UMTS Bearer
Service, and an External Bearer Service.
TE/MT Local Bearer Service is not further elaborated here as this bearer service is outside the scope of the UMTS
network.
Having said that the End-to-End Bearer Service is beyond the scope of the present document it is however the various
services offered by the UMTS Bearer Service that the UMTS operator offers. It is this bearer service that provides the
UMTS QoS.
The External Bearer Service is not further elaborated here as this bearer may be using several network services, e.g.
another UMTS Bearer Service.
6.1.2 The Radio Access Bearer Service and the Core Network Bearer
Service
As described in the previous clause it is the UMTS Bearer Service that provides the UMTS QoS. The UMTS Bearer
Service consists of two parts, the Radio Access Bearer Service and the Core Network Bearer Service. Both services
reflects the optimised way to realise the UMTS Bearer Service over the respective cellular network topology taking into
account such aspects as e.g. mobility and mobile subscriber profiles.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 11 ETSI TS 123 107 V8.2.0 (2012-01)
The Radio Access Bearer Service provides confidential transport of signalling and user data between MT and CN Edge
Node with the QoS adequate to the negotiated UMTS Bearer Service or with the default QoS for signalling. This
service is based on the characteristics of the radio interface and is maintained for a moving MT.
If unequal error protection shall be supported, it is provided by underlying Radio Bearer Services. In this case the
payload of the user data SDU, transported by the Radio Access Bearer Service, shall conform to a SDU format defined
with possible exact sizes and the payload bits statically structured per size. Each bit of the SDU payload belongs to a
defined subflow. At Radio Access Bearer Service establishment, the exact SDU payload format and required reliability
per subflow is signalled to RAN using standardised attributes (see clause 6.4.3).
In release 1999, unequal error protection for a Radio Access Bearer is only applicable for services using a codec
integrated in the core network. This implies that UMTS Bearer service can not use the attribute SDU format information
to define subflows and the payload bits of the SDUs will therefore be equally protected.
The Core Network Bearer Service of the UMTS core network connects the UMTS CN Edge Node with the CN
Gateway to the external network. The role of this service is to efficiently control and utilise the backbone network in
order to provide the contracted UMTS bearer service. The UMTS packet core network shall support different backbone
bearer services for variety of QoS.
6.1.3 The Radio Bearer Service and the RAN Access Bearer Service
The Radio Access Bearer Service is realised by a Radio Bearer Service and an RAN Access -Bearer Service.
The Radio Bearer Service covers all the aspects of the radio interface transport. This bearer service is provided by the
UTRAN FDD/TDD or the GERAN, which are not elaborated further in the present document.
To support unequal error protection, RAN and MT shall have the ability to segment/reassemble the user flows into the
different subflows requested by the Radio Access Bearer Service. The segmentation/ reassemble is given by the SDU
payload format signalled at Radio Access Bearer establishment. The Radio Bearer service handles the part of the user
flow belonging to one subflow, according to the reliability requirements for that subflow.
The RAN Access Bearer Service together with the Physical Bearer Service provides the transport between RAN and
CN. RAN Access bearer services for packet traffic shall provide different bearer services for variety of QoS. The RAN
Access Bearer Service is provided by the Iu or the Gb Bearer Service.
6.1.4 The Backbone Network Service
The Core Network Bearer Service uses a generic Backbone Network Service.
The Backbone Network Service covers the layer 1/Layer2 functionality and is selected according to operator's choice in
order to fulfil the QoS requirements of the Core Network Bearer Service. The Backbone Network Service is not specific
to UMTS but may reuse an existing standard.
6.2 QoS Management Functions in the Network
The purpose of this clause is to give a comprehensive overview of functionality needed to establish, modify and
maintain a UMTS Bearer Service with a specific QoS. The relations between the functions internal to the nodes are
implementation specific. The allocation of these functions to the UMTS entities shall indicate the requirement for the
specific entity to enforce the QoS commitments negotiated for the UMTS bearer service. The specific realisation of
these functions is implementation dependent and has only to maintain the specified QoS characteristics. The QoS
management functions of all UMTS entities together shall ensure the provision of the negotiated service between the
access points of the UMTS bearer service. The end-to-end service is provided by translation/mapping with UMTS
external services.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 12 ETSI TS 123 107 V8.2.0 (2012-01)
6.2.1 Description of functions
6.2.1.1 QoS management functions for UMTS bearer service in the control
plane
Service Manager co-ordinates the functions of the control plane for establishing, modifying and maintaining the
service it is responsible for. And, it provides all user plane QoS management functions with the relevant attributes. The
service manager offers services to other instances, it signals with peer service managers and uses services provided by
other instances. The service manager may perform an attribute translation to request lower layer services. Furthermore,
it may interrogate other control functions to receive permission for service provision.
Translation function converts between the internal service primitives for UMTS bearer service control and the various
protocols for service control of interfacing external networks. The translation includes the converting between UMTS
bearer service attributes and QoS attributes of the external networks service control protocol (e.g. between IETF TSPEC
and UMTS service attributes). The service manager may include a translation function to convert between its service
attributes and the attributes of a lower layer service it is using.
Admission/Capability control maintains information about all available resources of a network entity and about all
resources allocated to UMTS bearer services. It determines for each UMTS bearer service request or modification
whether the required resources can be provided by this entity and it reserves these resources if allocated to the UMTS
bearer service. The function checks also the capability of the network entity to provide the requested service, i.e.
whether the specific service is implemented and not blocked for administrative reasons. The resource control performed
by the admission control supports also the service retention.
Subscription Control checks the administrative rights of the UMTS bearer service user to use the requested service
with the specified QoS attributes.
6.2.1.2 Functions for UMTS bearer service in the user plane
User plane QoS management functions maintain the signalling and user data traffic within certain limits, defined by
specific QoS attributes. UMTS bearer services with different QoS attribute values shall be supported by the QoS
management functions. These functions ensure the provision of the QoS negotiated for a UMTS bearer service.
Mapping function provides each data unit with the specific marking required to receive the intended QoS at the
transfer by a bearer service.
Classification function assigns data units to the established services of a MT according to the related QoS attributes if
the MT has multiple UMTS bearer services established. The appropriate UMTS bearer service is derived from the data
unit header or from traffic characteristics of the data.
Resource Manager distributes the available resources between all services sharing the same resource. The resource
manager distributes the resources according to the required QoS. Example means for resource management are
scheduling, bandwidth management and power control for the radio bearer.
Traffic conditioner provides conformance between the negotiated QoS for a service and the data unit traffic. Traffic
conditioning is performed by policing or by traffic shaping. The policing function compares the data unit traffic with the
related QoS attributes. Data units not matching the relevant attributes will be dropped or marked as not matching, for
preferential dropping in case of congestion. The traffic shaper forms the data unit traffic according to the QoS of the
service. The reference algorithm for traffic conditioning is described in Annex B. This reference algorithm should not
be interpreted as a required implementation algorithm.
6.2.2 Allocation of QoS management functions
6.2.2.1 QoS management functions for UMTS bearer service in the control
plane
The QoS management functions for controlling the UMTS bearer service are shown in figure 2. These control functions
support the establishment and the modification of a UMTS bearer service by signalling/negotiation with the UMTS
external services and by the establishment or modification of all UMTS internal services with the required
characteristics.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 13 ETSI TS 123 107 V8.2.0 (2012-01)

MT RAN Gateway
TE CN EDGE Ext.
Netw.
Adm./Cap. Adm./Cap. Subscr. Adm./Cap.
Adm ./Cap.
Transl. Control Control Control Control Control Transl.
Local Ext.
Service Service
Control UMTS BS UMTS BS UMTS BS Control
Manager Manager Manager
RAB
Manager
Local BS Radio BS Radio BS RA BS RA BS CN BS CN BS Ext. BS
Manager Manager Manager Manager Manager Manager Manager Manager
RAN RAN RA NS BB NS BB NS
RA NS
ph. BS M ph. BS M Manager Manager Manager Manager
service primitive interface
protocol interface
Figure 2: QoS management functions for UMTS bearer service in the control plane
The translation functions (Trans.) in the MT and the Gateway convert between external service signalling and internal
service primitives including the translation of the service attributes. The translation function in the Gateway is FFS
regarding packet oriented services.
The UMTS BS manager in the MT, CN EDGE and the Gateway signal between each other and via the translation
function with external instances to establish or modify a UMTS bearer service. Each of the UMTS BS managers
interrogates its associated admission/capability control whether the network entity supports the specific requested
service and whether the required resources are available. Additionally, the CN EDGE UMTS BS manager verifies with
the subscription control the administrative rights for using the service.
The UMTS BS manager of the MT translates the UMTS bearer service attributes into attributes for the local bearer
service and requests this service from the local BS manager.
The UMTS BS manager of the CN EDGE translates the UMTS bearer service attributes into RAB service attributes and
RAN Access bearer service attributes and it translates UMTS bearer service attributes into CN bearer service attributes.
Also, the UMTS BS manager of the CN EDGE requests its RAN Access BS manager, its CN BS manager and the RAB
manager in the RAN to provide the required services.
The RAB manager verifies with its admission/capability control whether the RAN supports the specific requested
service and whether the required resources are available. It translates the RAB service attributes into radio bearer
service and RAN Access bearer service attributes and requests the radio BS manager and the RAN Access BS manager
to provide bearer services with the required attributes.
The Gateway UMTS BS manager translates the UMTS bearer service attributes into CN bearer service attributes and
requests its CN BS manager to provide the service. Furthermore, it translates the UMTS bearer service attributes into
the external bearer service attributes and requests this service from the external BS manager.
Radio, RAN Access and CN BS managers use services provided by lower layers as indicated in figure 2.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 14 ETSI TS 123 107 V8.2.0 (2012-01)
6.2.2.2 QoS management functions for the UMTS bearer service in the user
plane
The QoS management functions of the UMTS BS for the user plane are shown in figure 3. These functions maintain the
data transfer characteristics according to the commitments established by the UMTS BS control functions and expressed
by the bearer service attributes. The QoS management user plane functions are provided with the relevant attributes by
the QoS management control functions.

TE MT RAN CN EDGE Gateway Ext.
Netw.
Class
if.
Class
if.
Cond.
Cond.
Cond. Mapper Mapper Mapper
Resource Resource Resource Resource Resource Resource
Local BS External BS
Manager Manager Manager Manager Manager Manager
RAN phys. BS RAN Access network service BB network service
data flow with indication of direc tion

Figure 3: QoS management functions for the UMTS bearer service in the user plane
The classification function (Class.) in the Gateway and in the MT assign user data units received from the external
bearer service or the local bearer service to the appropriate UMTS bearer service according to the QoS requirements of
each user data unit. The classification function in the MT is FFS.
The traffic conditioner (Cond.) in the MT provides conformance of the uplink user data traffic with the QoS attributes
of the relevant UMTS bearer service. In the Gateway a traffic conditioner may provide conformance of the downlink
user data traffic with the QoS attributes of the relevant UMTS bearer service; i.e., on a per PDP context basis. The
packet oriented transport of the downlink data units from the external bearer service to the RAN and the buffering in the
RAN may result in bursts of downlink data units not conformant with the UMTS BS QoS attributes. A traffic
conditioner in the RAN forms this downlink data unit traffic according to the relevant QoS attributes.
The traffic conditioners are not necessarily separated functions. For example a resource manager may also provide
conformance with the relevant QoS attributes by appropriate data unit scheduling. Or, if fixed resources are dedicated to
one bearer service the resource limitations implicitly condition the traffic.
The mapping function marks each data unit with the specific QoS indication related to the bearer service performing the
transfer of the data unit.
Each of the resource managers of a network entity is responsible for a specific resource. The resource manager
distributes its resources between all bearer services requesting transfer of data units on these resources. Thereby, the
resource manager attempts to provide the QoS attributes required for each individual bearer service.
ETSI
3GPP TS 23.107 version 8.2.0 Release 8 15 ETSI TS 123 107 V8.2.0 (2012-01)
6.3 UMTS QoS Classes
When defining the UMTS QoS classes, also referred to as traffic classes, the restrictions and limitations of the air
interface have to be taken into account. It is not reasonable to define complex mechanisms as have been in fixed
networks due to different error characteristics of the air interface. The QoS mechanisms provided in the cellular
network have to be robust and capable of providing reasonable QoS resolution. Table 1 illustrates the QoS classes for
UMTS.
There are four different QoS classes:
- conversational class;
- streaming class;
- interactive class; and
- background class.
The main distinguishing factor between these QoS classes is how delay sensitive the traffic is: Conversational class is
meant for traffic which is very delay sensitive while Background class is the most delay insensitive traffic class.
Conversational and Streaming classes are mainly intended to be used to carry real-time traffic flows. The main divider
between them is how delay sensitive the traffic is. Conversational real-time services, like video telephony, are the most
delay sensitive applications and those data streams should be carried in Conversational class.
Interactive class and Background are mainly meant to be used by traditional Internet applications like WWW, Email,
Telnet, FTP and News. Due to looser delay requirements, compare to conversational and streaming classes, both
provide better error rate by means of channel coding and retransmission. The main difference between Interactive and
Background class is that Interactive class is mainly used by interactive applications, e.g. interactive Email or interactive
Web browsing, while Background class is meant for background traffic, e.g. background download of Emails or
background file downloading. Responsiveness of the interactive applications is ensured by separating interactive and
background applications. Traffic in the Interactive class has higher priority in scheduling than Background class traffic,
so background applications use transmission resources only when interactive applications do not need them. This is
very important in wireless environment where the bandwidth is low compared to fixed networks.
However, these are only typical examples of usage of the traffic classes. There is in particular no strict one-to-one
mapping between classes of service (as defined in TS 22.105 [5]) and the traffic classes defined in this TS. For instance,
a service interactive by nature can very well use the Conversational traffic class if the application or the user has tight
requirements on delay.
6.3.1 Conversational class
The most well known use of this scheme is telephony speech (e.g. GSM). But with Internet and multimedia a number of
new applications will require this scheme, for example voice over IP and video conferencing tools. Real time
conversation is always performed between peers (or groups) of live (human) end-users. This is the only scheme where
the required characteristics are strictly given by human perception.
Real time conversation scheme is characterised by that the transfer time shall be low because of the conversational
nature of the scheme and at the same time that the time relation (variation) between information entities of the stream
shall be preserved in the same way as for real time streams. The maximum transfer delay is given by the human
perception of video and audio conversation. Therefore the limit for acceptable transfer delay is very strict, as failure to
provide low enoug
...