1、 ETSI GS ORI 001 V4.1.1 (2014-10) Open Radio equipment Interface (ORI); Requirements for Open Radio equipment Interface (ORI) (Release 4) Disclaimer This document has been produced and approved by the Open Radio equipment Interface (ORI) ETSI Industry Specification Group (ISG) and represents the vie
2、ws of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS ORI 001 V4.1.1 (2014-10)2Reference RGS/ORI-0016 Keywords E-UTRA, interface, radio, UTRA ETSI 650 Route des Lucioles F-06921 Sophia Antipolis C
3、edex - 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 The present document may be made avai
4、lable 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 versions and/or in print, the only
5、 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 current status of this and othe
6、r ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced or utilized in any form
7、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 foregoing restriction extend to reproduction in al
8、l media. European Telecommunications Standards Institute 2014. All rights reserved. DECTTM, PLUGTESTSTM, 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 Organiz
9、ational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS ORI 001 V4.1.1 (2014-10)3Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g3Introduction 4g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Inf
10、ormative references 7g32.3 Document structure of the ORI specifications 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 ORI system requirements . 9g34.1 Reference configurations 9g34.1.1 Topology . 9g34.1.2 Specific ORI node requirements on ORI links and ORI ports
11、 11g34.2 Supported radio standards 12g34.2.1 System requirements. 12g34.2.2 Specific ORI node requirements . 12g34.3 Protocol Requirements . 13g34.3.1 Compliance with CPRI . 13g34.3.1.1 System requirements . 13g34.3.1.2 Specific ORI node requirements . 13g34.3.2 C Essential, or potentially Essential
12、, 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 (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be
13、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. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Open Radio equ
14、ipment Interface (ORI). The contents of the present document are subject to continuing work within the ISG. Should the ISG modify the contents of the present document, it will be re-released by the ISG with an identifying change of release date and an increase in version number as follows: Version x
15、.y.z where: x the first digit indicates the release number of ORI specification group starting from Release 1. 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 bee
16、n incorporated in the document. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “may not“, “need“, “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
17、 expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. Introduction Mobile communication networks have evolved from 1stgeneration to 3rd, and now, many operators are preparing to introduce LTE. Economical and efficient deployment o
18、f base stations is one of key issues for the success of mobile services. Operators also consider ecological aspects when renewing a system. In general mobile radio base stations consist of a BaseBand Unit (BBU) and a Radio Frequency Unit (RFU), which usually is a Remote Radio Head (RRH) in a distrib
19、uted base station architecture. Current interfaces between BBU and RRH are provided in a “semi proprietary“ nature, although based on industry standards like CPRI or OBSAI. In order to gain flexibility operators are looking for distributed base station architectures with separate BBUs and RRHs. In o
20、rder to gain interoperability, BBU and RRH are interconnected via an open BBU-RRH Interface (ORI) for flexible combination from different vendors. ETSI ETSI GS ORI 001 V4.1.1 (2014-10)5ORI is about a digitized radio base station interface that establishes a connection between “Radio Equipment Contro
21、l“ (REC) and “Radio Equipment“ (RE) enabling single-hop and multi-hop topologies. Different information flows (User Plane data, Control and Management Plane data, and Synchronization Plane data) are multiplexed over the interface. ORI covers OSI protocol layer 1, Layer 2 up to Layer 7. The present d
22、ocument aims to define a set of system and link requirements that apply to the Open Radio equipment Interface (ORI). ETSI ETSI GS ORI 001 V4.1.1 (2014-10)61 Scope ETSI Group Specifications (GS) are deliverables produced by Industry Specification Groups (ISG). GSs are written with the style of a Tech
23、nical Specification (TS), and represent the sole view of the ISG members. The present document describes system-level requirements that apply to the Open Radio equipment Interface (ORI) and ORI nodes for Release 4. NOTE: Requirements comply with CPRI specification of CPRI forum 1 and focuses on the
24、following 3GPP radio access technologies namely UTRA-FDD 3, 4 and 5, E-UTRA-FDD 6, E-UTRA-TDD 6 and GSM 12. Multiplexing between any combination of UTRA-FDD, E-UTRA-FDD, and GSM on an ORI link is also considered. 2 References References are either specific (identified by date of publication and/or e
25、dition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected l
26、ocation might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are necessary for the application of the pre
27、sent document. 1 “Common Public Radio Interface (CPRI); Interface Specification“ V 6.0. NOTE: Available at http:/www.cpri.info/spec.html. 2 ETSI GS ORI 002-1: “Open Radio equipment Interface (ORI); ORI Interface Specification; Part 1: Low Layers (Release 4)“. 3 ETSI TS 125 104: “Universal Mobile Tel
28、ecommunications System (UMTS); Base Station (BS) radio transmission and reception (FDD) (3GPP TS 25.104)“. 4 ETSI TS 125 215: “Universal Mobile Telecommunications System (UMTS); Physical layer; Measurements (FDD) (3GPP TS 25.215)“. 5 ETSI TS 125 133: “Universal Mobile Telecommunications System (UMTS
29、); Requirements for support of radio resource management (FDD) (3GPP TS 25.133)“. 6 ETSI TS 136 104: “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception (3GPP TS 36.104)“. 7 ETSI GS ORI 002-2: “Open Radio equipment Interface (ORI); ORI Interf
30、ace Specification; Part 2: Control and Management (Release 4)“. 8 ETSI TS 125 461 (V10.2.0): “Universal Mobile Telecommunications System (UMTS); UTRAN Iuant interface: Layer 1 (3GPP TS 25.461 version 10.2.0 Release 10)“. 9 ETSI TS 125 462 (V10.1.0): “Universal Mobile Telecommunications System (UMTS)
31、; UTRAN Iuant interface: Signalling transport (3GPP TS 25.462 version 10.1.0 Release 10)“. 10 ETSI TS 125 466 (V10.3.0): “Universal Mobile Telecommunications System (UMTS); UTRAN Iuant interface: Application part (3GPP TS 25.466 version 10.3.0 Release 10)“. ETSI ETSI GS ORI 001 V4.1.1 (2014-10)711 A
32、ntenna Interface Standards Group, Standard No. AISG v2.0, 13th June 2006: “Control interface for antenna line devices“. 12 ETSI TS 145 005: “GSM/EDGE Radio Access Network; Radio transmission and reception (3GPP TS 45.005)“. 13 ETSI TS 136 141: “LTE; Evolved Universal Terrestrial Radio Access (E-UTRA
33、); Base Station (BS) conformance testing (3GPP TS 36.141)“. 2.2 Informative references The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. 2.3 Document structure of the ORI
34、 specifications Figure 2.3.1: Document structure of the ORI specifications NOTE: The Low Layers specification 2 covers a single ORI link. The C - the capability for data to be transported via AxCs mapped to M slave ports to be able to be switched by the networking RE to/from N master ports, where MN
35、. The capability for the REC to configure an RE that is connected to the REC via a networking RE without affecting radio interface transmission on the networking RE, and vice versa. Figure 4.1.1: Single point-to-point link between one REC and one RE Figure 4.1.2: Multiple point-to-point links betwee
36、n one REC and one RE ETSI ETSI GS ORI 001 V4.1.1 (2014-10)10ORILink(s)ORILink(s)RECREREFigure 4.1.3: Multiple point-to-point links between one REC and several REs (star topology) Figure 4.1.4: Chain topology ORILinkORILinkFigure 4.1.5: Tree topology Figure 4.1.6: Ring topology ETSI ETSI GS ORI 001 V
37、4.1.1 (2014-10)114.1.2 Specific ORI node requirements on ORI links and ORI ports In support of the topology options as specified for the present release of ORI, the following is required of the RE and REC: A hop shall support at least one active link. As per the single-hop topologies defined in clau
38、se 4.1.1 it is assumed REC ports are only master ports and RE ports are only slave ports. As per the single-REC multi-hop topologies defined in clause 4.1.1, it is assumed that REC ports are only master ports and each RE port may take a master port role or a slave port role within the constraints de
39、fined below. The REC shall manage which ORI ports act as a master port in the RE (within the REs ORI port role capabilities). The following requirements shall then apply: The RE without the capability to be a networking RE shall support 1 to 255 ORI ports. The RE with the capability to be a networki
40、ng RE shall support 2 to 255 ORI ports, and shall support the simultaneous configuration of at least one ORI port as a master port and at least one other ORI port as a slave port. The REC shall support 1 to 255 ORI ports. All ORI Links terminated by an ORI port in slave role at the RE shall have the
41、ir timing generated by the same timing source. NOTE: Further restrictions may be needed for multi-REC topologies in the future. In order to support single-REC multi-hop topologies, the RE acting as a networking RE is expected to support the following: At least the simplified solution for networking,
42、 described in section 6.3 of 1. The forwarding of all the SAPs defined in 1 through the unit between relevant master and slave ports, The networking RE shall not forward SAPs defined in 1 from one slave port to another slave port, e.g. in ring topology. The forwarding of the contents of the control
43、words defined within the “ORI reserved field“, the “vendor-specific area“ between the relevant master and slave ports. Given that the RE is only required to terminate one active link at any one time, in the ring topology a break in the ring affecting the routeing of the active link would cause one o
44、r more REs to require C E-UTRA-FDD 6; E-UTRA-TDD 6; GSM 12. 3GPP releases and versions relevant to the above radio standards are specified in 1, section 3.1. Multiplexing between any combination of UTRA-FDD, E-UTRA-FDD, and GSM on an ORI link shall also be supported. 4.2.2 Specific ORI node requirem
45、ents In support of the technology options as specified for the present release of ORI, the following is required of the RE and REC: The RE/REC shall support at least one of UTRA-FDD, E-UTRA-FDD, E-UTRA-TDD, or GSM, and may optionally support multiplexing between any combination of UTRA-FDD, E-UTRA-F
46、DD, and GSM on the ORI Link. The REC and RE shall support the functional separation of radio functionality as described in: - Table 1 in 1 for support of UTRA - Table 1A in 1 in support of E-UTRA - Table 1AA in 1 in support of GSM. ETSI ETSI GS ORI 001 V4.1.1 (2014-10)134.3 Protocol Requirements 4.3
47、.1 Compliance with CPRI 4.3.1.1 System requirements The CPRI specification as specified in 1 shall be the baseline for the ORI Low Layers specification 2. In line with that, the ORI shall be compliant with all of the requirements in 1 for the applicable topologies and radio standards as specified fo
48、r the present release of ORI. Furthermore, in order to make the ORI specification fully inter-operable, it may be necessary to restrict the number of options defined in 1 for usage within ORI. Such restrictions shall be described in the ORI specifications. 4.3.1.2 Specific ORI node requirements The
49、RE/REC compliant to the ORI specifications shall: be fully compliant to CPRI, as defined in section 5.2 of 1; support mandatory requirements defined within ORI that are defined as options within CPRI; support mandatory requirements defined within ORI on all layers (specified in the present document, as well as 2 and 7) that do not refer to functionality in CPRI specifications. 4.3.2 C&M functionality 4.3.2.1 System requirements The following aspects shall be supported
