1、 ETSI TS 138 460 V15.0.0 (2018-07) 5G; NG-RAN; E1 general aspects and principles (3GPP TS 38.460 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 138 460 V15.0.0 (2018-07)13GPP TS 38.460 version 15.0.0 Release 15Reference RTS/TSGR-0338460vf00 Keywords 5G ETSI 650 Route des Lucioles F-
2、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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-sea
3、rch 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 betwee
4、n 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. Informati
5、on 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 Noti
6、fication 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
7、 and 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 t
8、he 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 460 V15.0.0 (2018-07)23GPP TS 38.460 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs
9、 essential 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 p
10、otentially 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
12、and/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 ET
13、SI 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 identiti
14、es 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 no
15、t“, “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 cit
16、ation. ETSI ETSI TS 138 460 V15.0.0 (2018-07)33GPP TS 38.460 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.3 Abbreviations . 5g34 General as
17、pects . 6g34.1 E1 interface general principles . 6g34.2 E1 interface specification objectives 6g35 Functions of the E1 interface 6g35.1 General . 6g35.1.1 E1 interface management function . 6g35.1.2 E1 bearer context management function . 7g35.2 TEIDs allocation 7g36 Procedures of the E1 interface 7
18、g36.1 Interface Management procedures . 7g36.2 Bearer Context Management procedures . 7g37 E1 interface protocol structure . 8g38 Other E1 interface specifications . 8g38.1 NG-RAN E1 interface: layer 1 (3GPP TS 38.461) . 8g38.2 NG-RAN E1 interface: signalling transport (3GPP TS 38.462) . 8g38.3 NG-R
19、AN E1 interface: E1AP specification (3GPP TS 38.463) . 8g3Annex A (informative): Change history . 9g3History 10g3ETSI ETSI TS 138 460 V15.0.0 (2018-07)43GPP TS 38.460 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). Th
20、e 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
21、 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,
22、 etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 138 460 V15.0.0 (2018-07)53GPP TS 38.460 version 15.0.0 Release 151 Scope The present document is an introduction to the 3GPP TS 38.46x series of technical specifications that defi
23、ne the E1 interface. The E1 interface provides means for interconnecting a gNB-CU-CP and a gNB-CU-UP of a gNB-CU within an NG-RAN, or for interconnecting a gNB-CU-CP and a gNB-CU-UP of an en-gNB within an E-UTRAN. 2 References The following documents contain provisions which, through reference in th
24、is 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 applie
25、s. 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.401: “NG-RAN; Architecture
26、Description“. 3 3GPP TS 38.461: “NG-RAN; E1 layer 1“. 4 3GPP TS 38.462: “NG-RAN; E1 signalling transport“. 5 3GPP TS 38.463: “NG-RAN; E1 Application Protocol (E1AP)“. 6 3GPP TS 38.300: “NR; Overall description; Stage-2“. 7 3GPP TS 37.340: “NR; Multi-connectivity; Overall description; Stage-2“. 3 Def
27、initions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 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. en-gNB: as defi
28、ned in TS 37.340 7 gNB-CU: as defined in TS 38.401 2 gNB-CU-CP: as defined in TS 38.401 2 gNB-CU-UP: as defined in TS 38.401 2 gNB-DU: as defined in TS 38.401 2 gNB: as defined in TS 38.300 6 3.3 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and
29、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. DL Downlink DRB Data Radio Bearer ETSI ETSI TS 138 460 V15.0.0 (2018-07)63GPP TS 38.460 version 15.0.0 Release 15E1AP E1 Application Protoc
30、ol IP Internet Protocol SCTP Stream Control Transmission Protocol TNL Transport Network Layer4 General aspects This clause captures the E1 interface principles and characteristics. 4.1 E1 interface general principles The general principles for the specification of the E1 interface are as follows: -
31、the E1 interface is open; - the E1 interface supports the exchange of signalling information between the endpoints; - from a logical standpoint, the E1 is a point-to-point interface between a gNB-CU-CP and a gNB-CU-UP. NOTE 1: A point-to-point logical interface should be feasible even in the absence
32、 of a physical direct connection between the endpoints. - the E1 interface separates Radio Network Layer and Transport Network Layer; - the E1 interface enables exchange of UE associated information and non-UE associated information; - the E1 interface is future proof to fulfil different new require
33、ments, support of new services and new functions. NOTE 2: The E1 interface is a control interface and is not used for user data forwarding. 4.2 E1 interface specification objectives The E1 interface specifications facilitate the following: - inter-connection of a gNB-CU-CP and a gNB-CU-UP supplied b
34、y different manufacturers. 5 Functions of the E1 interface 5.1 General The following clauses describe the functions supported over E1. 5.1.1 E1 interface management function The error indication function is used by the gNB-CU-UP or gNB-CU-CP to indicate to the gNB-CU-CP or gNB-CU-UP that an error ha
35、s occurred. The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the gNB-CU-UP and the gNB-CU-CP. The E1 setup function allows to exchange application level data needed for the gNB-CU-UP and gNB-CU-CP to inte
36、roperate correctly on the E1 interface. The E1 setup is initiated by both the gNB-CU-UP and gNB-CU-CP. The gNB-CU-UP Configuration Update and gNB-CU-CP Configuration Update functions allow to update application level configuration data needed between the gNB-CU-CP and the gNB-CU-UP to interoperate c
37、orrectly over the E1 interface. The E1 setup and gNB-CU-UP Configuration Update functions allow to inform NR CGI(s), S-NSSAI(s), PLMN-ID(s) and QoS information supported by the gNB-CU-UP. ETSI ETSI TS 138 460 V15.0.0 (2018-07)73GPP TS 38.460 version 15.0.0 Release 155.1.2 E1 bearer context managemen
38、t function The establishment of the E1 bearer context is initiated by the gNB-CU-CP and accepted or rejected by the gNB-CU-UP based on admission control criteria (e.g., resource not available). The modification of the E1 bearer context can be initiated by either gNB-CU-CP or gNB-CU-UP. The receiving
39、 node can accept or reject the modification. The E1 bearer context management function also supports the release of the bearer context previously established in the gNB-CU-UP. The release of the bearer context is triggered by the gNB-CU-CP either directly or following a request received from the gNB
40、-CU-UP. This function is used to setup and modify the QoS-flow to DRB mapping configuration. The gNB-CU-CP decides flow-to-DRB mapping and provides the generated SDAP and PDCP configuration to the gNB-CU-UP. The gNB-CU-CP also decides the Reflective QoS flow to DRB mapping. For each PDU Session Reso
41、urce to be setup or modified, the S-NSSAI, shall be provided by gNB-CU-CP to the gNB-CU-UP in the E1 bearer context setup procedure and the E1 bearer context modification procedure. This function is used for the gNB-CU-UP to notify the event of DL data arrival detection to the gNB-CU-CP. With this f
42、unction, the gNB-CU-UP requests gNB-CU-CP to trigger paging procedure over F1 to support RRC Inactive state. This function is used for the gNB-CU-UP to notify the event of user inactivity to the gNB-CU-CP. With this function, the gNB-CU-UP indicates that the inactivity timer associated with a bearer
43、 expires or that user data is received for the bearer whose inactivity timer has expired. The gNB-CU-CP consolidates all the serving gNB-CU-UPs for the UE and takes further action. This function is used for the gNB-CU-UP to report data volume to the gNB-CU-CP. This function also allows to support CA
44、 based packet duplication as described in TS 38.300 6, i.e. one data radio bearer should be configured with two GTP-U tunnels between gNB-CU-UP and a gNB-DU. 5.2 TEIDs allocation The gNB-CU-UP is responsible for the allocation of the F1-U UL GTP TEID for each data radio bearer. The gNB-CU-UP is resp
45、onsible for the allocation of the S1-U DL GTP TEID for each E-RAB and the NG-U DL GTP TEID for each PDU Session. The gNB-CU-UP is responsible for the allocation of the X2-U DL/UL GTP TEID or the Xn-U DL/UL GTP TEID for each data radio bearer. 6 Procedures of the E1 interface 6.1 Interface Management
46、 procedures The E1 interface management procedures are listed below: - Reset procedure - Error Indication procedure - gNB-CU-UP E1 Setup procedure - gNB-CU-CP E1 Setup procedure - gNB-CU-UP Configuration Update procedure - gNB-CU-CP Configuration Update procedure - E1 Release procedure 6.2 Bearer Co
47、ntext Management procedures The E1 bearer management procedures are listed below: ETSI ETSI TS 138 460 V15.0.0 (2018-07)83GPP TS 38.460 version 15.0.0 Release 15- Bearer Context Setup procedure - Bearer Context Release Request (gNB-CU-UP initiated) procedure - Bearer Context Release (gNB-CU-CP initi
48、ated) procedure - Bearer Context Modification (gNB-CU-CP initiated) procedure - Bearer Context Modification Required (gNB-CU-UP initiated) procedure - DL Data Notification procedure - Bearer Context Inactivity Notification procedure - Data Usage Report procedure 7 E1 interface protocol structure Fig
49、ure 7.1-1 shows the protocol structure for E1. The TNL is based on IP transport, comprising the SCTP on top of IP. The application layer signalling protocol is referred to as E1AP (E1 Application Protocol). SCTP IP Data link layer E1-AP Physical layer Radio Network Layer TransportNetworkLayer Control Plane Figure 7.1-1: Interface protocol structure for E1 8 Other E1 interface specifications This clause contains the description of the other related 3GPP specifications. 8.1 NG-RAN E1 interface: layer 1 (3GPP TS 38.461) 3GPP TS 38.461 3 speci
