1、 ETSI TS 138 470 V15.2.0 (2018-07) 5G; NG-RAN; F1 general aspects and principles (3GPP TS 38.470 version 15.2.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 138 470 V15.2.0 (2018-07)13GPP TS 38.470 version 15.2.0 Release 15Reference DTS/TSGR-0338470vf20 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 470 V15.2.0 (2018-07)23GPP TS 38.470 version 15.2.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 470 V15.2.0 (2018-07)33GPP TS 38.470 version 15.2.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 . 6g34 General as
17、pects . 6g34.1 F1 interface general principles . 6g34.2 F1 interface specification objectives 6g34.3 F1 interface capabilities 7g34.4 F1 interface characteristics . 7g35 Functions of the F1 interface 7g35.1 General . 7g35.2 F1-C functions 7g35.2.1 F1 interface management function 7g35.2.2 System Inf
18、ormation management function . 7g35.2.3 F1 UE context management function 7g35.2.4 RRC message transfer function 8g35.2.5 Paging function . 8g35.2.6 Warning messages information transfer function . 8g35.3 F1-U functions 8g35.3.1 Transfer of user data . 8g35.3.2 Flow control function 8g36 Procedures
19、of the F1 interface 8g36.1 Control plane procedures 8g36.1.1 Interface Management procedures 8g36.1.2 Context Management procedures . 9g36.1.3 RRC Message Transfer procedures 9g36.1.4 System Information procedures 9g36.1.5 Paging procedures . 9g36.1.6 Resource Coordination procedure . 9g36.2 User pl
20、ane procedures 9g37 F1 interface protocol structure . 9g37.1 F1 Control Plane Protocol (F1-C) 9g37.2 F1 User Plane Protocol (F1-U) . 10g38 Other F1 interface specifications 10g38.1 NG-RAN F1 interface: layer 1 (3GPP TS 38.471) . 10g38.2 NG-RAN F1 interface: signalling transport (3GPP TS 38.472) . 10
21、g38.3 NG-RAN F1 interface: F1AP specification (3GPP TS 38.473) . 10g38.4 NG-RAN F1 interface: data transport and transport signalling (3GPP TS 38.474) 11g38.5 NG-RAN F1 interface: user plane protocol (3GPP TS 38.425) . 11g3Annex A (informative): Change history . 12g3History 13g3ETSI ETSI TS 138 470
22、V15.2.0 (2018-07)43GPP TS 38.470 version 15.2.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
23、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 in
24、dicates 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 470 V15.2.
25、0 (2018-07)53GPP TS 38.470 version 15.2.0 Release 151 Scope The present document is an introduction to the 3GPP TS 38.47x series of technical specifications that define the F1 interface. The F1 interface provides means for interconnecting a gNB-CU and a gNB-DU of a gNB within an NG-RAN, or for inter
26、connecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN. 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
27、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
28、 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 Description“. 3 3GPP TS 38.471: “NG-RAN; F1 layer 1“. 4 3GPP TS 38.472: “NG-RAN; F1 signalling transport“. 5 3GPP TS 38.473: “NG-RAN; F1 Application
29、Protocol (FnAP)“. 6 3GPP TS 38.474: “NG-RAN; F1 data transport“. 7 3GPP TS 38.425: “NG-RAN; Xn interface user plane protocol“. 8 3GPP TS 38.300: “NR; Overall description; Stage-2“. 9 3GPP TS 37.340: “NR; Multi-connectivity; Overall description; Stage-2“. 10 3GPP TS 38.321: “NR; Medium Access Control
30、 (MAC) protocol specification“. 3 Definitions 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,
31、 in 3GPP TR 21.905 1. en-gNB: as defined in TS 37.340 9 gNB-CU: as defined in TS 38.401 2 gNB-DU: as defined in TS 38.401 2 gNB: as defined in TS 38.300 8 ETSI ETSI TS 138 470 V15.2.0 (2018-07)63GPP TS 38.470 version 15.2.0 Release 153.3 Abbreviations For the purposes of the present document, the ab
32、breviations 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. DRB Data Radio Bearers F1-U F1 User plane interface F1-C F1 Control plane interface F1AP F1 Appli
33、cation Protocol GTP-U GPRS Tunnelling Protocol IP Internet Protocol NR-MIB NR-Master Information Block O - the F1 interface supports the exchange of signalling information between the endpoints, in addition the interface supports data transmission to the respective endpoints; - from a logical standp
34、oint, the F1 is a point-to-point interface between the endpoints. NOTE: A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints. - the F1 interface supports control plane and user plane separation; - the F1 interface separates R
35、adio Network Layer and Transport Network Layer; - the F1 interface enables exchange of UE associated information and non-UE associated information; - the F1 interface is designed in a future proof way to fulfil different new requirements, support new services and new functions; - one gNB-CU and a se
36、t of gNB-DUs are visible to other logical nodes as a gNB or an en-gNB where the gNB terminates the Xn and the NG interfaces, and the en-gNB terminates the X2 and the S1-U interfaces; - the gNB-CU may be separated in control plane (CP) and user plane (UP). 4.2 F1 interface specification objectives Th
37、e F1 interface specifications facilitate the following: - inter-connection of a gNB-CU and a gNB-DU supplied by different manufacturers. ETSI ETSI TS 138 470 V15.2.0 (2018-07)73GPP TS 38.470 version 15.2.0 Release 154.3 F1 interface capabilities 4.4 F1 interface characteristics 5 Functions of the F1
38、 interface 5.1 General The following clauses describe the functions supported over F1-C and F1-U. 5.2 F1-C functions 5.2.1 F1 interface management function The error indication function is used by the gNB-DU or gNB-CU to indicate to the gNB-CU or gNB-DU that an error has occurred. The reset function
39、 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-DU and the gNB-CU. The F1 setup function allows to exchange application level data needed for the gNB-DU and gNB-CU to interoperate correctly on the F1 interface. Th
40、e F1 setup is initiated by the gNB-DU. The gNB-CU Configuration Update and gNB-DU Configuration Update functions allow to update application level configuration data needed between gNB-CU and gNB-DU to interoperate correctly over the F1 interface, and may activate or deactivate cells. The F1 setup a
41、nd gNB-DU Configuration Update functions allow to inform the S-NSSAI(s) supported by the gNB-DU. The F1 resource coordination function is used to transfer information about frequency resource sharing between gNB-CU and gNB-DU. 5.2.2 System Information management function Scheduling of system broadca
42、st information is carried out in the gNB-DU. The gNB-DU is responsible for transmitting the system information according to the scheduling parameters available. The gNB-DU is responsible for the encoding of NR-MIB. In case broadcast of SIB1 and other SI messages is needed, the gNB-DU is responsible
43、for the encoding of SIB1 and the gNB-CU is responsible for the encoding of other SI messages. 5.2.3 F1 UE context management function The F1 UE context management function supports the establishment and modification of the necessary overall UE context. The establishment of the F1 UE context is initi
44、ated by the gNB-CU and accepted or rejected by the gNB-DU based on admission control criteria (e.g., resource not available). The modification of the F1 UE context can be initiated by either gNB-CU or gNB-DU. The receiving node can accept or reject the modification. The F1 UE context management func
45、tion also supports the release of the context previously established in the gNB-DU. The release of the context is triggered by the gNB-CU either directly or following a request received from the gNB-DU. The gNB-CU request the gNB-DU to release the UE Context when the UE enters RRC_IDLE or RRC_INACTI
46、VE. This function can be also used to manage DRBs and SRBs, i.e., establishing, modifying and releasing DRB and SRB resources. The establishment and modification of DRB resources are triggered by the gNB-CU and accepted/rejected by the gNB-DU based on resource reservation information and QoS informa
47、tion to be provided to the gNB-DU. For each DRB to be setup or modified, the S-NSSAI may be provided by gNB-CU to the gNB-DU in the UE Context Setup procedure and the UE Context Modification procedure. ETSI ETSI TS 138 470 V15.2.0 (2018-07)83GPP TS 38.470 version 15.2.0 Release 15The mapping between
48、 QoS flows and radio bearers is performed by gNB-CU and the granularity of bearer related management over F1 is radio bearer level. For NG-RAN, the gNB-CU provides an aggregated DRB QoS profile and QoS flow profile to the gNB-DU, and the gNB-DU either accepts the request or rejects it with appropria
49、te cause value. To support packet duplication for intra-gNB-DU CA as described in TS 38.300 8, one data radio bearer should be configured with two GTP-U tunnels between gNB-CU and a gNB-DU. With this function, gNB-CU requests the gNB-DU to setup or change of the SpCell (as defined in TS 38.32110) for the UE, and the gNB-DU either accepts or rejects the request with appropriate cause value. With this function, the gNB-CU requests the setup of the SCell(s) at the gNB-DU side, and the gNB-DU accepts all, some or none of the SCell(s) and rep
