1、 ETSI TS 123 207 V14.0.0 (2017-05) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; End-to-end Quality of Service (QoS) concept and architecture (3GPP TS 23.207 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 123 207
2、 V14.0.0 (2017-05)13GPP TS 23.207 version 14.0.0 Release 14Reference RTS/TSGS-0223207ve00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregi
3、stre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present docu
4、ment shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive with
5、in 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the prese
6、nt document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorize
7、d by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTES
8、TSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are
9、Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 123 207 V14.0.0 (2017-05)23GPP TS 23.207 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these ess
10、ential 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 updat
11、es are available on the ETSI Web server (https:/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 serve
12、r) 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 identitie
13、s 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. Modal verbs terminology In the present document “shall“, “shall not
14、“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct cita
15、tion. ETSI ETSI TS 123 207 V14.0.0 (2017-05)33GPP TS 23.207 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and Abbreviations 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 High Level Re
16、quirements for End-to-End IP QoS . 9g34.1 End-to-End QoS Negotiation Requirements 9g34.2 QoS Policy Requirements 9g35 End-to-End QoS Architecture 9g35.1 QoS Management Functions in the Network . 9g35.1.1 Description of functions 10g35.1.1.1 QoS management functions for end-to-end IP QoS in UMTS Netw
17、ork . 10g35.1.1.2 (void) . 11g35.1.1.3 Interaction to External Networks 11g35.1.1.4 Translation/mapping function in the GGSN and the UE . 11g35.1.2 Allocation of QoS management functions 12g35.1.2.1 QoS management functions for end-to-end IP QoS 12g35.2 Capabilities of Functional Elements . 12g35.2.
18、1 GGSN . 12g35.2.2 UE . 13g35.2.3 Void 13g35.2.3a PCRF 13g35.2.4 Application Function (AF) 14g35.3 Void 14g35.3aVoid 14g35.3b Gx reference point (PCRF GGSN) 14g35.3c Rx reference point (AF - PCRF) 14g35.4 QoS Parameters 15g35.5 QoS Parameter Mapping 15g36 End-to-End QoS Procedures 15g36.1 QoS Proced
19、ures in Functional Elements 15g36.1.1 Procedures in the GGSN . 15g36.1.2 Procedures in the UE 15g36.1.3 Void 16g36.1.3a Procedures in the PCRF 16g36.1.4 Procedures in the AF. 16g36.2 IP Bearer Level / Application Level Binding Mechanism . 17g36.3 Session Flow: QoS Interaction Procedures 17g36.3.1 Vo
20、id 17g36.3.2 Resource Reservation Message Flows 17g36.3.2.1 Void. 17g36.3.2.2 Resource Reservation with IP QoS signalling 17g36.3.2.3 Resource Reservation with IP QoS reservation signalling and Service-based Local Policy . 17g36.3.2.4 (void) . 17g36.3.3 Void 17g36.3.4 Void 17g36.3.5 Void 17g36.3.6 V
21、oid 18g3ETSI ETSI TS 123 207 V14.0.0 (2017-05)43GPP TS 23.207 version 14.0.0 Release 146.3.6a Void 18g36.3.7 Void 18g36.3.8 Void 18g36.4 PDP Context Used for Application Level Signalling Transport . 18g3Annex A (informative): QoS Conceptual Models 19g3A.1 Introduction 19g3A.2 Scenarios 19g3A.2.1 Sce
22、nario 1 . 20g3A.2.2 Scenario 2 . 21g3A.2.3 Scenario 3 . 22g3A.2.4 Scenario 4 . 25g3A.2.5 Scenario 5 . 26g3Annex B (informative): (void) . 28g3Annex C (informative): Sample Mapping of SDP Descriptions Into QoS Authorization 29g3Annex D (informative): Resource reservation and end-to-end RSVP . 32g3D.1
23、 Resource reservation with end-to-end RSVP . 32g3D.2 Resource Reservation with End-to-End RSVP and Service-based Local Policy . 35g3Annex E (informative): Change history . 39g3History 40g3ETSI ETSI TS 123 207 V14.0.0 (2017-05)53GPP TS 23.207 version 14.0.0 Release 14Foreword This Technical Specifica
24、tion has been produced by the 3rdGeneration Partnership Project (3GPP). 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
25、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 al
26、l 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 ETSI TS 123 207 V14.0.0 (2017-05)63GPP TS 23.207 version 14.0.0 Release 141 Scope The present document provides th
27、e framework for end-to-end Quality of Service involving GPRS and complements TS 23.107 3 which describes the framework for Quality of Service within UMTS. The end-to-end QoS architecture is provided in Figure 1. The document describes the interaction between the TE/MT Local Bearer Service, the GPRS
28、Bearer Service, and the External Bearer Service, and how these together provide Quality of Service for the End-to-End Service. The document also describes IP level mechanisms necessary in providing end-to-end Quality of Service involving GPRS networks, including possible interaction between the IP l
29、evel and the GPRS level, as well as the application level and the IP level. This document covers different architectural aspects of the end-to-end Quality of Service concept and architecture with varying level of detail. In general, other specifications shall be referred to for further details; thes
30、e other specifications enable the reader to acquire the full understanding of the end-to-end Quality of Service concept and architecture. In particular, the stage 2 specification for the PCC architecture is specified in TS 23.203 21. The present document does not contain any requirements for the PCC
31、 architecture. In contrast to the TS 23.107 3, the present document is only applicable to GPRS packet switched access services, and includes aspects of interworking to the IM subsystem as well as PSTN and other networks. The document does not cover the circuit switched access services. TE MT UTRAN/
32、GERAN CN Iu EDGE NODE CNGateway TE GPRS End-to-End Service TE/MT Local Bearer Service UMTS Bearer Service External Bearer Service GPR Bearer ServiceRadio Access Bearer Service CN BearerService BackboneBearer Service Iu BearerService Radio BearerService PhysicalRadio Service PhysicalBearer Service Fi
33、gure 1: End-to-End QoS Architecture 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
34、. ETSI ETSI TS 123 207 V14.0.0 (2017-05)73GPP TS 23.207 version 14.0.0 Release 14- 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 referen
35、ce implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 22.228: “Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1“. 2 3GPP TS 23.002: “Network Architecture“. 3 3GPP TS 23.107: “QoS Concept
36、and Architecture“. 4 3GPP TS 23.228: “IP Multimedia (IM) Subsystem stage 2“. 4a Void. 4b Void. 4c Void. 5 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 6 RFC 2475: “An Architecture for Differentiated Services (DiffServ)“. 7 RFC 2753: “A Framework for Policy-based Admission Control “. 8 RFC 2
37、748: “Common Open Policy Service protocol (COPS)“. 9 RFC 2205: “Resource ReSerVation Protocol (RSVP)“. 10 RFC 2209: “Resource ReSerVation Protocol (RSVP) Message Processing Rules“. 11 RFC 2210: “The use of RSVP with IETF integrated Services“. 12 RFC 1633: “Integrated Services in the Internet Archite
38、cture: an Overview“. 13 RFC 3261: “SIP: Session Initiation Protocol“. 14 RFC 2327: “Session Description Protocol“. 15 RFC 2998: “A Framework For Integrated Services Operation Over DiffServ Networks“. 16 RFC 2750: “RSVP Extensions for Policy Control“. 17 RFC 2474: “Definition of the Differentiated Se
39、rvices Field (DS Field) in the IPv4 and IPv6 Headers“. 18 Void. 19 3GPP TS 23.060: “General Packet Radio Service (GPRS) Service description; Stage 2“. 20 3GPP TS 23.221: “Architecture requirements“. 21 3GPP TS 23.203: “Policy and Charging Control Architecture“. 22 3GPP TS 29.212: “Policy and Chargin
40、g Control (PCC); Reference points“. 23 3GPP TS 29.213: “Policy and Charging Control signalling flows and QoS parameter mapping“. 24 3GPP TS 29.214: “Policy and Charging Control over Rx reference point“. 25 3GPP TS 29.208: “End-to-end Quality of Service (QoS) signalling flows“. ETSI ETSI TS 123 207 V
41、14.0.0 (2017-05)83GPP TS 23.207 version 14.0.0 Release 143 Definitions and Abbreviations 3.1 Definitions RSVP: Resource ReSerVation Protocol: The RSVP protocol, RFC 2205 9, is used by a host to request specific qualities of service from the network for particular application data streams or flows. T
42、he network responds by explicitly admitting or rejecting RSVP requests. DiffServ: DiffServ networks classify packets into one of a small number of aggregated flows or “classes“, based on the DiffServ codepoint (DSCP) in the packets IP header. This is known as behaviour aggregate (BA) classification
43、(RFC 2475 6). At each DiffServ router, packets are subjected to a “per-hop behaviour“ (PHB), which is invoked by the DSCP (RFC 2474 17). IntServ: The integrated services architecture RFC 1633 12 defined a set of extensions to the traditional best effort model of the Internet with the goal of allowin
44、g end-to-end QOS to be provided to applications. One of the key components of the architecture is a set of service definitions; the current set of services consists of the controlled load and guaranteed services. The architecture assumes that some explicit setup mechanism is used to convey informati
45、on to routers so that they can provide requested services to flows that require them. While RSVP is the most widely known example of such a setup mechanism, the IntServ architecture is designed to accommodate other mechanisms. Application Function: The Application Function (AF) is an element offerin
46、g applications that require the control of IP bearer resources . The AF is capable of communicating with the PCRF to transfer dynamic QoS-related service information. One example of an AF is the P-CSCF of the IM CN subsystem. AF session: An AF session is established by an application level signallin
47、g protocol offered by the AF that requires a session set-up with explicit session description before the use of the service. One example of an AF session is an IMS session. AF session signalling: AF session signalling is used to control the AF session. One example of AF session signalling is SIP/SDP
48、. Policy control: The process whereby the Policy and Charging Rules Function (PCRF) indicates to the Policy and Charging Enforcement Function (PCEF) how to control the IP-CAN bearer. Policy control includes QoS control and/or gating control. 3.2 Abbreviations For the purpose of the present document,
49、 the following abbreviations apply: AF Application Function APN Access Point Name (*) DiffServ Differentiated ServicesDSCP DiffServ Code Point GERAN GSM/EDGE Radio Access Network (*) GGSN Gateway GPRS Support Node (*) HTTP Hypertext Transfer Protocol (*) IMS IP Multimedia Subsystem IntServ Integrated Services LAN Local Area Network LDP Label Distribution Protocol MPLS Multiprotocol Label Switching Architecture PCC Policy and Charging Control PCEF Policy and Charging Enforcement Function PHB Per Hop Beh
