1、 ETSI TS 138 415 V15.0.0 (2018-07) 5G; NG-RAN; PDU Session User Plane protocol (3GPP TS 38.415 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 138 415 V15.0.0 (2018-07)13GPP TS 38.415 version 15.0.0 Release 15Reference RTS/TSGR-0338415vf00 Keywords 5G ETSI 650 Route des Lucioles F-06
2、921 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-searc
3、h 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 document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between
4、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 within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information
5、 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 present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notifi
6、cation No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright a
7、nd the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the
8、 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 138 415 V15.0.0 (2018-07)23GPP TS 38.415 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs e
9、ssential or potentially essential to normative deliverables 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 pot
10、entially 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 (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI.
11、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. Trademarks The present document may include trademarks and/or tradenames which are asserted an
12、d/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI
13、 of products, services or organizations associated with those trademarks. 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
14、 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“
15、, “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 citat
16、ion. ETSI ETSI TS 138 415 V15.0.0 (2018-07)33GPP TS 38.415 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 General . 5g
17、34.1 General aspects . 5g35 PDU Session user plane protocol . 6g35.1 General . 6g35.2 PDU Session user plane protocol layer services . 6g35.3 Services expected from the Transport Network Layer . 6g35.4 Elementary procedures . 6g35.4.1 Transfer of DL PDU Session Information 6g35.4.1.1 Successful oper
18、ation 6g35.4.1.2 Unsuccessful operation . 6g35.4.2 Transfer of UL PDU Session Information 7g35.4.2.1 Successful operation 7g35.4.2.2 Unsuccessful operation . 7g35.5 Elements for the PDU Session user plane protocol 7g35.5.1 General 7g35.5.2 Frame format for the PDU Session user plane protocol 8g35.5.
19、2.1 DL PDU SESSION INFORMATION (PDU Type 0) . 8g35.5.2.2 UL PDU SESSION INFORMATION (PDU Type 1) . 8g35.5.3 Coding of information elements in frames . 9g35.5.3.1 PDU Type . 9g35.5.3.2 Spare . 9g35.5.3.3 QoS Flow Identifier (QFI) 9g35.5.3.4 Reflective QoS Indicator (RQI) 9g35.5.3.5 Padding . 9g35.5.4
20、 Timers . 10g35.6 Handling of unknown, unforeseen and erroneous protocol data 10g3Annex A (informative): Example of using Future Extension Field 11g3A.1 Example of using Future Extension field . 11g3A.1.1 New IE Flags 11g3Annex B (informative): Change history . 12g3History 13g3ETSI ETSI TS 138 415 V
21、15.0.0 (2018-07)43GPP TS 38.415 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rd Generation 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 t
22、he 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 ind
23、icates 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 ETSI TS 138 415 V15.0.0
24、 (2018-07)53GPP TS 38.415 version 15.0.0 Release 151 Scope The present document specifies the PDU Session user plane protocol being used over the NG-U, Xn-U and N9 interfaces. Applicability to other interfaces is not precluded. 2 References The following documents contain provisions which, through r
25、eference 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
26、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 TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 38.300: “NextGen
27、 Radio Access Network (NG-RAN); Overall description; Stage 2“. 3 3GPP TS 29.281: “General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905
28、1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. NG-U: logical interface between NG-RAN node and UPF as described in TS 38.300 2. Xn-U: logical interface between NG-RAN nodes as defined in TS 38.300
29、2. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. QFI QoS Flow Identifier RQA
30、Reflective QoS Attribute RQI Reflective QoS Indication UP User Plane UPF User Plane Function 4 General 4.1 General aspects The PDU Session User Plane protocol is located in the User Plane of the Radio Network Layer above the Transport Network Layer of the interface. ETSI ETSI TS 138 415 V15.0.0 (201
31、8-07)63GPP TS 38.415 version 15.0.0 Release 15Each PDU session User Plane protocol instance is associated to one PDU Session. In this version of the present document, the PDU session user plane protocol data is conveyed by GTP-U protocol means, more specifically, by means of the “GTP-U Container“ GT
32、P-U Extension Header as defined in TS 29.281 3. 5 PDU Session user plane protocol 5.1 General The PDU session UP layer uses services of the Transport Network Layer in order to send its packets over the interface. 5.2 PDU Session user plane protocol layer services The following functions are provided
33、 by the PDU Session User Plane protocol: - Provision of control information elements (e.g. QFI, RQI) associated with a PDU session. 5.3 Services expected from the Transport Network Layer The PDU session UP layer expects the following services from the Transport Network Layer: - Transfer of PDU sessi
34、on User Plane PDUs. 5.4 Elementary procedures 5.4.1 Transfer of DL PDU Session Information 5.4.1.1 Successful operation The purpose of the Transfer of DL PDU Session Information procedure is to send control information elements related to the PDU Session from UPF/NG-RAN to NG-RAN. A PDU Session user
35、 plane instance making use of the Transfer of DL PDU Session Information procedure is associated to a single PDU Session. The Transfer of DL PDU Session Information procedure may be invoked whenever packets for that particular PDU Session need to be transferred across the related interface instance.
36、 The DL PDU Session Information frame includes a QoS Flow Identifier (QFI) field associated with the transferred packet. The NG-RAN shall use the received QFI to determine the QoS flow and QoS profile which are associated with the received packet. The DL PDU Session Information frame shall also incl
37、ude the Reflective QoS Indicator (RQI) field to indicate that user plane Reflective QoS shall be activated or not. The NG-RAN shall, if RQA has been configured for the involved QoS flow, take the RQI into account and propagate the activation towards the UE or a peer NG-RAN node for this particular p
38、acket. Figure 5.4.1.1-1: Successful Transfer of DL PDU Session Information 5.4.1.2 Unsuccessful operation Void. NG-RAN UPF/NG-RANDL PDU SESSION INFORMATIONETSI ETSI TS 138 415 V15.0.0 (2018-07)73GPP TS 38.415 version 15.0.0 Release 155.4.2 Transfer of UL PDU Session Information 5.4.2.1 Successful op
39、eration The purpose of the Transfer of UL PDU Session Information procedure is to send control information elements related to the PDU Session from NG-RAN to UPF. An UL PDU Session user plane instance making use of the Transfer of UL PDU Session Information procedure is associated to a single PDU Se
40、ssion. The Transfer of UL PDU Session Information procedure may be invoked whenever packets for that particular PDU Session need to be transferred across the related interface instance. The UL PDU Session Information frame includes a QoS Flow Identifier (QFI) field associated with the transferred pa
41、cket. The UPF shall use the received QFI to determine the QoS flow and QoS profile which are associated with the received packet. Figure 5.4.2.1-1: Successful Transfer of UL PDU Session Information 5.4.2.2 Unsuccessful operation Void. 5.5 Elements for the PDU Session user plane protocol 5.5.1 Genera
42、l In the present document the structure of frames are specified by using figures similar to figure 5.5.1-1. Bits Number of Octets7 6 5 4 3 2 1 0 Field 1 Field 2 1 Octet 1 Field 3 Field 4 2 Octet 2 Field 4 continue Spare Octet 3 Field 6 2 Octet 4 Octet 5 Field 6 continue Padding bits Future Extension
43、 0-m Padding 0-3Figure 5.5.1-1: Example frame format NG-RAN UPFUL PDU SESSION INFORMATIONETSI ETSI TS 138 415 V15.0.0 (2018-07)83GPP TS 38.415 version 15.0.0 Release 15Unless otherwise indicated, fields which consist of multiple bits within an octet have the most significant bit located at the highe
44、r bit position (indicated above frame in figure 5.5.1-1). In addition, if a field spans several octets, most significant bits are located in lower numbered octets (right of frame in figure 5.5.1-1). On the NG interface, the frame is transmitted starting from the lowest numbered octet. Within each oc
45、tet, the bits are sent according to decreasing bit position (bit position 7 first). Spare bits should be set to “0“ by the sender and should not be checked by the receiver. The header part of the frame is always an integer number of octets. The payload part is octet aligned (by adding Padding Bits w
46、hen needed). The receiver should be able to remove an additional Future Extension field that may be present. See description of Future Extension field in A.1. Padding octets may be added at the end of the frame, see Padding in 5.5.3.5. 5.5.2 Frame format for the PDU Session user plane protocol 5.5.2
47、.1 DL PDU SESSION INFORMATION (PDU Type 0) This frame format is defined to allow the NG-RAN to receive some control information elements which are associated with the transfer of a packet over the interface. The following shows the respective DL PDU SESSION INFORMATION frame. Bits Number of Octets7
48、6 5 4 3 2 1 0 PDU Type (=0) Spare 1 Spare RQI QoS Flow Identifier 1 Padding 0-3 Figure 5.5.2.1-1: DL PDU SESSION INFORMATION (PDU Type 0) Format 5.5.2.2 UL PDU SESSION INFORMATION (PDU Type 1) This frame format is defined to allow the UPF to receive some control information elements which are associ
49、ated with the transfer of a packet over the interface. The following shows the respective UL PDU SESSION INFORMATION frame. ETSI ETSI TS 138 415 V15.0.0 (2018-07)93GPP TS 38.415 version 15.0.0 Release 15Bits Number of Octets7 6 5 4 3 2 1 0 PDU Type (=1) Spare 1 Spare QoS Flow Identifier 1 Padding 0-3 Figure 5.5.2.2-1: UL PDU SESSION INFORMATION (PDU Type 1) Format 5.5.3 Coding of information elements in frames 5.5.3.1 PDU Type Description: The PDU Type indicates the structure of the PDU session UP frame. The field takes the value of the PDU Type it identi
