ETSI TS 138 472-2018 5G NG-RAN F1 signalling transport (V15 1 0 3GPP TS 38 472 version 15 1 0 Release 15).pdf

1、 ETSI TS 138 472 V15.1.0 (2018-07) 5G; NG-RAN; F1 signalling transport (3GPP TS 38.472 version 15.1.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 138 472 V15.1.0 (2018-07)13GPP TS 38.472 version 15.1.0 Release 15Reference DTS/TSGR-0338472vf10 Keywords 5G ETSI 650 Route des Lucioles F-06921 Soph

2、ia 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-search The pr

3、esent 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 such ver

4、sions 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 on the

5、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 Notification N

6、o 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 and the f

7、oregoing 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 3GPP Or

8、ganizational 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 472 V15.1.0 (2018-07)23GPP TS 38.472 version 15.1.0 Release 15Intellectual Property Rights Essential patents IPRs essential

9、 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 potentially

10、 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. No guara

11、ntee 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 and/or reg

12、istered 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 of prod

13、ucts, 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 or GSM

14、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“, “shoul

15、d“, “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 citation. ETS

16、I ETSI TS 138 472 V15.1.0 (2018-07)33GPP TS 38.472 version 15.1.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. F1-C signalling bea

17、rer 6g34.1 Function and protocol stack 6g35 Data link layer 6g36 IP layer . 6g37 Transport layer . 7g3Annex A (informative): Change History 8g3History 9g3ETSI ETSI TS 138 472 V15.1.0 (2018-07)43GPP TS 38.472 version 15.1.0 Release 15Foreword This Technical Specification has been produced by the 3rd

18、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 the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release

19、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. tech

20、nical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 138 472 V15.1.0 (2018-07)53GPP TS 38.472 version 15.1.0 Release 151 Scope The present document specifies the standards for Signalling Trans

21、port to be used across 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 interconnecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN. The present document describes how the F1AP signalling messages are transported o

22、ver F1. 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. - For a specific reference

23、, 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 document in the same Release as the present document. 1

24、3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 IETF RFC 2460 (1998-12): “Internet Protocol, Version 6 (IPv6) Specification“. 3 IETF RFC 791 (1981-09): “Internet Protocol“. 4 IETF RFC 2474 (1998-12): “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers“. 5

25、 IETF RFC 4960 (2007-09): “Stream Control Transmission Protocol“. 6 3GPP TS 38.300: “NR; Overall description; Stage-2“. 7 3GPP TS 38.401: “NG-RAN; Architecture description“. 8 3GPP TS 37.340: “NR; Multi-connectivity; Overall description; Stage-2“. 3 Definitions and abbreviations 3.1 Definitions For

26、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 defined in TS 37.340 8 F1: interface between a gNB-

27、CU and a gNB-DU, providing an interconnection point between the gNB-CU and the gNB-DU. F1-C: Reference point for the control plane protocol between gNB-CU and gNB-DU. gNB-CU: as defined in TS 38.401 7 gNB-DU: as defined in TS 38.401 7 gNB: as defined in TS 38.300 6 ETSI ETSI TS 138 472 V15.1.0 (2018

28、-07)63GPP TS 38.472 version 15.1.0 Release 153.3 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

29、 TR 21.905 1. DiffServ Differentiated Service IANA Internet Assigned Number Authority IP Internet Protocol PPP Point to Point Protocol SCTP Stream Control Transmission Protocol 4. F1-C signalling bearer 4.1 Function and protocol stack F1-C signalling bearer provides the following functions: - Provis

30、ion of reliable transfer of F1AP message over F1-C interface. - Provision of networking and routeing function. - Provision of redundancy in the signalling network. - Support for flow control and congestion control. The protocol stack for F1-C Signalling Bearer is shown in figure 4.1-1 and details on

31、 each protocol are described in the following clauses. SCTP IP Data link layer F1AP Physical layer Radio Network Layer TransportNetworkLayer Figure 4.1-1: F1-C signalling bearer protocol stack The Transport Network Layer is based on IP transport, comprising SCTP on top of IP. 5 Data link layer The s

32、upport of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented. 6 IP layer The gNB-CU and gNB-DU shall support IPv6 (IETF RFC 2460 2) and/or IPv4 (IETF RFC 791 3). The IP layer of F1-C only supports point-to-point transmission for delivering F1AP message. The gNB-C

33、U and gNB-DU shall support the Diffserv Code Point marking as described in IETF RFC 2474 4. ETSI ETSI TS 138 472 V15.1.0 (2018-07)73GPP TS 38.472 version 15.1.0 Release 157 Transport layer SCTP (IETF RFC 4960 5) shall be supported as the transport layer of F1-C signalling bearer. The Payload Protoco

34、l Identifier assigned by IANA to be used by SCTP for the application layer protocol F1AP is 62. SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network. gNB-DU and gNB-CU s

35、hall support a configuration with a single SCTP association per gNB-DU/gNB-CU pair. Configurations with multiple SCTP endpoints per gNB-DU/gNB-CU pair should be supported. When configurations with multiple SCTP associations are supported, the gNB-CU may request to dynamically add/remove SCTP associa

36、tions between the gNB-DU/gNB-CU pair. The gNB-DU shall establish the SCTP association. The SCTP Destination Port number value assigned by IANA to be used for F1AP is 38472. Within the set of SCTP associations established between one gNB-CU and gNB-DU pair, a single SCTP association shall be employed

37、 for F1AP elementary procedures that utilize non-UE-associated signalling with the possibility of fail-over to a new association to enable robustness. Selection of the SCTP association by the gNB-DU and the gNB-CU is specified in TS 38.401 7. Between one gNB-CU and gNB-DU pair: - A single pair of st

38、ream identifiers shall be reserved over an SCTP association for the sole use of F1AP elementary procedures that utilize non UE-associated signalling. - At least one pair of stream identifiers over one or several SCTP associations shall be reserved for the sole use of F1AP elementary procedures that

39、utilize UE-associated signallings. However, a few pairs (i.e. more than one) should be reserved. - For a single UE-associated signalling, the gNB-DU shall use one SCTP stream and one SCTP stream, and the association/stream should not be changed during the communication of the UE-associated signallin

40、g unless TNL binding update is performed. Transport network redundancy may be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remote SCTP end-point. For SCTP endpoint redundancy an INIT may

41、 be sent from gNB-CU or gNB-DU, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960 5 in sub clause 5.2. The SCTP congestion control may, using an implementation specific mechanism, initiate higher layer protocols to reduce the signalling traff

42、ic at the source and prioritise certain messages. ETSI ETSI TS 138 472 V15.1.0 (2018-07)83GPP TS 38.472 version 15.1.0 Release 15Annex A (informative): Change History Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2017-06 R3 NR#2 R3-172121 - - - First version 0.1.0 2017-07 R

43、3 NR#2 R3-172644 - - - Incorporated agreed TPs from R3 NR#2 Adhoc 0.2.0 2017-08 R3#97 R3-172715 Incorporated Rapporteurs cleanup 0.2.1 2017-08 R3#97 R3-173446 - - - Incorporated agreed TPs from R3#97 0.3.0 2017-10 R3#97b R3-174246 - - - Incorporated agreed TPs from R3#97b 0.4.0 2017-12 R3#98 R3-1750

44、62 - - - Incorporated agreed TPs from R3#98 0.5.0 2017-12 RAN#78 RP-172261 Submitted for approval to RAN 1.0.0 2017-12 RAN#78 TR approved by RAN plenary 15.0.0 2018-06 RAN#80 RP-181238 0002 1 F Clarifications on multiple TNL associations 15.1.0 ETSI ETSI TS 138 472 V15.1.0 (2018-07)93GPP TS 38.472 version 15.1.0 Release 15History Document history V15.1.0 July 2018 Publication