throbber
3GPP TS 23.107 V3.5.0 (2000-12)
`
`Technical Specification
`
`
`
`3rd Generation Partnership Project;
`Technical Specification Group Services and System Aspects;
`QoS Concept and Architecture
`(Release 1999)
`
`
`
`
`
`
`
`The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
`The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
`This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
`Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
`
`1
`
`

`

`
`Release 1999
`
`2
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`
`
`
`
`
`
`
`
`Keywords
`UMTS, architecture, quality
`
`3GPP
`
`Postal address
`
`
`3GPP support office address
`650 Route des Lucioles - Sophia Antipolis
`Valbonne - FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`
`Internet
`http://www.3gpp.org
`
`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.
`
`© 2000, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA, TTC).
`All rights reserved.
`
`
`3GPP
`
`

`

`
`Release 1999
`
`3
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`Contents
`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 '99 ............................................................................................................................... 8
`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 Iu Bearer Service ............................................................................................ 10
`6.1.4
`The Backbone Network Service ............................................................................................................................. 11
`6.2 QoS Management Functions in the Network .............................................................................................................. 11
`6.2.1
`Description of functions .......................................................................................................................................... 11
`6.2.1.1 QoS management functions for UMTS bearer service in the control plane ........................................................ 11
`6.2.1.2
`Functions for UMTS bearer service in the user plane .......................................................................................... 11
`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 ...................................................... 13
`6.3 UMTS QoS Classes ....................................................................................................................................................... 13
`6.3.1
`Conversational class ................................................................................................................................................ 14
`6.3.2
`Streaming class ........................................................................................................................................................ 14
`6.3.3
`Interactive class ....................................................................................................................................................... 15
`6.3.4
`Background class ..................................................................................................................................................... 15
`6.4 QoS Parameters ............................................................................................................................................................. 15
`6.4.1
`Asymmetric Bearers ................................................................................................................................................ 15
`6.4.2
`Sources of UMTS Bearer Service Parameters ....................................................................................................... 16
`6.4.3
`UMTS Bearer Service Attributes ........................................................................................................................... 16
`6.4.3.1 List of attributes ....................................................................................................................................................... 16
`6.4.3.2 Attributes discussed per class ................................................................................................................................. 18
`6.4.3.3 UMTS bearer attributes: summary ......................................................................................................................... 19
`6.4.4
`Radio Access Bearer Service Attributes ................................................................................................................ 20
`6.4.4.1 List of attributes ....................................................................................................................................................... 20
`6.4.4.2 Attributes discussed per class ................................................................................................................................. 22
`6.4.4.3 Radio Access Bearer attributes: summary ............................................................................................................. 23
`6.4.5
`Radio Bearer Service Parameters ........................................................................................................................... 23
`6.4.6
`Iu Bearer Service Parameters ................................................................................................................................. 24
`6.4.7
`Core Network Bearer Service Parameters ............................................................................................................. 24
`6.5
`Parameter Value Ranges ............................................................................................................................................... 24
`6.5.1
`Ranges of UMTS Bearer Service Attributes ......................................................................................................... 24
`6.5.2
`Ranges of Radio Access Bearer Service Attributes .............................................................................................. 25
`7
`Support of QoS Requirement During Inter-SGSN RA Update .............................................................. 26
`8
`QoS Parameter Mapping ........................................................................................................................ 26
`8.1
`From Application Parameters to UMTS Bearer Service Parameters ......................................................................... 26
`8.2
`From UMTS Bearer Service Parameters to Radio Access Bearer Service Parameters ............................................ 26
`8.3
`From UMTS Bearer Service Parameters to CN Bearer Service Parameters ............................................................. 27
`9
`Interworking ........................................................................................................................................... 27
`9.1 UMTS-GSM CS/GPRS ................................................................................................................................................ 27
`
`3GPP
`
`

`

`
`Release 1999
`
`4
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`UMTS-GSM CS ...................................................................................................................................................... 27
`9.1.1
`9.1.1.1 Handover from UMTS to GSM .............................................................................................................................. 27
`9.1.1.2 Handover from GSM to UMTS .............................................................................................................................. 28
`9.1.2
`UMTS-GPRS ........................................................................................................................................................... 28
`9.1.2.1 General rules ............................................................................................................................................................ 28
`9.1.2.2 Determining R99 attributes from R97/98 attributes .............................................................................................. 29
`9.1.2.3 Determining R97/98 attributes from R99 attributes .............................................................................................. 29
`9.2 UMTS-PSTN ................................................................................................................................................................. 30
`9.3 UMTS-ISDN ................................................................................................................................................................. 30
`9.4 UMTS-Internet .............................................................................................................................................................. 30
`Annex A (informative): Error resilience in real-time packet multimedia payloads ................................. 32
`A.1
`Introduction ............................................................................................................................................ 32
`A.1.1
`Factors affecting error resilience ............................................................................................................................ 32
`A.2 Example figures...................................................................................................................................... 33
`Annex B (normative): Reference Algorithm for Conformance Definition of Bitrate .............................. 34
`Annex C (normative): Determine which QoS profile is of highest QoS .................................................... 35
`Annex D (informative): Change history ....................................................................................................... 36
`
`
`3GPP
`
`

`

`
`Release 1999
`
`5
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`Foreword
`This Technical Specification (TS) has been produced by the 3rd 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.
`
`3GPP
`
`

`

`
`Release 1999
`
`6
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`Scope
`1
`The present document provides the framework for Quality of Service within UMTS. The main purpose is to specify the
`list of attributes applicable to UMTS Bearer Service and Radio Access Bearer Service, as well as describe the Quality
`of Service architecture to be used in UMTS networks.
`
`References
`2
`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.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`3GPP TS 23.110: "UMTS Access Stratum - Services and Functions".
`
`3GPP TS 22.100: "Service aspects, Service principles".
`
`3GPP TS 23.121: "Evolution of the GSM platform towards UMTS".
`
`(Void)
`
`3GPP TS 22.105: "Services & Service capabilities".
`
`Abbreviations
`3
`For the purpose of the present document, the following abbreviations apply:
`
`3G
`AMR
`ATM
`BER
`BS
`CC
`CN
`CRC
`CS
`DTX
`FDD
`FER
`FTP
`GPRS
`GSM
`IETF
`IP
`ISDN
`MO
`MPEG
`MT
`MTC
`NS
`PDP
`PDU
`PS
`
`3rd Generation
`Adaptive Multirate speech codec
`Asynchronous Transfer Mode
`Bit Error Rate
`Bearer Service
`Call Control
`Core Network
`Cyclic Redundancy Check
`Circuit Switched
`Discontinuous Transmission
`Frequency Division Duplex
`Frame Erasure Ratio
`File Transfer Protocol
`General Packet Radio Service
`Global System for Mobile Communication
`Internet Engineering Task Force
`Internet Protocol
`Integrated Services Digital Network
`Mobile Originating Call
`Moving Pictures Expert Group
`Mobile Terminal
`Mobile Terminated Call
`Network Service
`Packet Data Protocol
`Protocol Data Unit
`Packet Switched
`
`3GPP
`
`

`

`
`Release 1999
`
`7
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`PSTN
`QoS
`RA
`RAB
`RAN
`RLC
`RSVP
`RT
`RTP
`SAP
`SDU
`SGSN
`SLA
`SMS
`SVC
`UDP
`TBC
`TDD
`TE
`TSPEC
`UE
`UMTS
`UTRA
`UTRAN
`
`Public Switched Telephone Network
`Quality of Service
`Routing Area
`Radio Access Bearer
`Radio Access Network
`Radio Link Control
`Resource Reservation Protocol
`Real Time
`Real Time Transport Protocol
`Service Access Point
`Service Data Unit
`Serving GPRS Support Node
`Service Level Agreement
`Short Message Service
`Switched Virtual Circuit
`User Datagram Protocol
`Token Bucket Counter
`Time Division Duplex
`Terminal Equipment
`Traffic Specification
`User Equipment
`Universal Mobile Telecommunication System
`UMTS Terrestrial Radio Access
`UMTS Terrestrial Radio Access Network
`
`4
`
`High Level Requirements
`
`End User QoS Requirements
`4.1
`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.
`
`3GPP
`
`

`

`
`Release 1999
`
`8
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`General Requirements for QoS
`4.2
`- 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.
`
`Technical Requirements for QoS
`4.3
`This subclause 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.
`
`CS QoS in release 1999
`5
`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;
`
`3GPP
`
`

`

`
`Release 1999
`
`9
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`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
`
`Overview of Different Levels of QoS
`6.1
`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.
`
`TE
`
`MT
`
`UMTS
`
`UTRAN
`
`CN Iu
`EDGE
`NODE
`End-to-End Service
`
`CN
`Gateway
`
`TE
`
`TE/MT Local
`Bearer Service
`
`UMTS Bearer Service
`UMTS Bearer Service
`
`External Bearer
`Service
`
`Radio Access Bearer Service
`
`CN Bearer
`Service
`
`Radio Bearer
`Service
`
`Iu Bearer
`Service
`
`Backbone
`Bearer Service
`
`UTRA
`FDD/TDD
`Service
`
`Physical
`Bearer Service
`
`Figure 1: UMTS QoS Architecture
`
`3GPP
`
`
`
`

`

`
`Release 1999
`
`10
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`The End-to-End Service and UMTS Bearer Service
`6.1.1
`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 subclause 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.
`
`The Radio Access Bearer Service provides confidential transport of signalling and user data between MT and CN Iu
`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 UTRAN using standardised attributes (see subclause 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 Iu 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.
`
`The Radio Bearer Service and the Iu Bearer Service
`6.1.3
`The Radio Access Bearer Service is realised by a Radio Bearer Service and an Iu-Bearer Service.
`
`The role of the Radio Bearer Service is to cover all the aspects of the radio interface transport. This bearer service uses
`the UTRA FDD/TDD, which is not elaborated further in the present document.
`
`To support unequal error protection, UTRAN 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 Iu-Bearer Service together with the Physical Bearer Service provides the transport between UTRAN and CN. Iu
`bearer services for packet traffic shall provide different bearer services for variety of QoS.
`
`3GPP
`
`

`

`
`Release 1999
`
`11
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`The Backbone Network Service
`6.1.4
`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.
`
`QoS Management Functions in the Network
`6.2
`The purpose of this subclause 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.
`
`6.2.1
`
`Description of functions
`
`QoS management functions for UMTS bearer service in the control plane
`6.2.1.1
`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.
`
`Functions for UMTS bearer service in the user plane
`6.2.1.2
`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.
`
`3GPP
`
`

`

`
`Release 1999
`
`12
`
`3GPP TS 23.107 V3.5.0 (2000-12)
`
`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
`
`QoS management functions for UMTS bearer service in the control plane
`6.2.2.1
`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.
`
`TE
`
`MT
`
`Local
`Service
`Control
`
`Transl.
`
`Adm./Cap.
`Control
`
`UMTS BS
`Manager
`
`UTRAN
`
`Adm./Cap.
`Control
`
`RAB
`Manager
`
`CN EDGE
`
`Gateway
`
`Adm./Cap.
`Control
`
`Subscr.
`Control
`
`Adm./Cap.
`Control
`
`Transl.
`
`UMTS BS
`Manager
`
`UMTS BS
`Manager
`
`Ext.
`Netw.
`
`Ext.
`Service
`Control
`
`Local BS
`Manager
`
`Radio BS
`Manager
`
`Radio BS
`Manager
`
`Iu BS
`Manager
`
`Adm.
`Iu BS
`Contr
`Manager
`
`CN BS
`Manager
`
`CN BS
`Manager
`
`Ext. BS
`Manager
`
`UTRA
`ph. BS M
`
`UTRA
`ph. BS M
`
`Iu NS
`Manager
`
`Iu NS
`Manager
`
`BB NS
`Manager
`
`BB NS
`Manager
`
`protocol interface
`
`service primitive 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

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket