Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.107  Word version:  18.0.0

Top   Top   None   None   Next
1…   6…   6.4…   8…   A…

 

1  Scopep. 6

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  Referencesp. 6

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]
TS 23.110: "UMTS Access Stratum - Services and Functions".
[2]
TS 22.100: "UMTS Phase 1".
[3]
TS 23.121: "Architectural Requirements for Release 1999".
[4]  Void.
[5]
TS 22.105: "Services & Service capabilities".
[6]
TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols - Stage 3".
[7]
TS 23.207: "End-to-end QoS concept and architecture".
[8]
TS 23.008: "Organization of subscriber data".
[9]
TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 2".
[10]
GSM TS 03.60 (Release 1998): "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 2 (Release 1998)".
[11]
TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
Up

3  Abbreviationsp. 6

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
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
Up

4  High Level Requirementsp. 7

4.1  End User QoS Requirementsp. 7

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;
  • QoS has to be provided end-to-end.
Up

4.2  General Requirements for QoSp. 8

  • 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.
Up

4.3  Technical Requirements for QoSp. 8

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.
Up

5  CS QoS in release 1999p. 9

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:
  1. speech: from the Information Transfer Capability (ITC) parameter;
  2. data, non-transparent: from the ITC and Connection element (CE) parameters;
  3. 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.
Up

Up   Top   ToC