eCPRI Transport Network V1 - Common Public …

1 eCPRI Transport Network (2017-10-24). Requirements Specification Common Public Radio Interface: Requirements for the eCPRI Transport Network The eCPRI Transport Network Requirements Specification has been developed by Ericsson AB, Huawei Technologies Co. Ltd, NEC Corporation and Nokia (the Parties ) and may be updated from time to time. Further information about this requirements document and the latest version may be found at BY USING THE REQUIREMENTS FOR THE eCPRI Transport Network SPECIFICATION, YOU ACCEPT THE Interface Specification Download Terms and Conditions FOUND AT IN ORDER TO AVOID ANY DOUBT, BY DOWNLOADING AND/OR USING THE REQUIREMENTS FOR THE eCPRI Transport Network .. SPECIFICATION NO EXPRESS OR IMPLIED LICENSE AND/OR ANY OTHER RIGHTS WHATSOEVER ARE GRANTED FROM ANYBODY.

2 2017 Ericsson AB, Huawei Technologies Co. Ltd, NEC Corporation and Nokia. 2 eCPRI Transport Network (2017-10-24). 1 Table of Contents 2 1. 3. 3 2. Transport Network Terminology and Services .. 4. 4 User Network Interface .. 4. 5 Transport Connection .. 4. 6 EVC Service Attributes .. 5. 7 One-way Frame Delay Performance .. 5. 8 One-way Frame Loss Ratio Performance .. 5. 9 EVC per UNI Service 5. 10 3. Traffic Characterization .. 6. 11 Generic 6. 12 Constant Bitrate traffic .. 6. 13 ON/OFF traffic .. 7. 14 4. Requirements .. 8. 15 Per flow 8. 16 Split E and splits ID, IID, IU when running E-UTRA .. 8. 17 Timing accuracy requirements .. 8. 18 Phase noise and MTIE requirements .. 10. 19 Phase noise characteristic at UNI.

3 10. 20 MTIE mask at UNI .. 10. 21 In-order delivery .. 10. 22 5. Annex A: Service Agreement considerations .. 11. 23 6. List of Abbreviations .. 12. 24 7. References .. 13. 25 8. History .. 14. 26. CPRI. 3 eCPRI Transport Network (2017-10-24). 1 1. Introduction 2 The Common Public Radio Interface (CPRI) is an industry cooperation aimed at defining publicly available 3 specifications for the key internal interface of radio base stations, such as eCPRI connecting the eCPRI . 4 Radio Equipment Control (eREC) and the eCPRI Radio Equipment (eRE) via a so-called fronthaul Transport 5 Network . The parties cooperating to define the specification are Ericsson AB, Huawei Technologies Co. Ltd, 6 NEC Corporation and Nokia.

4 7 The eCPRI Interface Specification [1] can be supported by Ethernet-switched or IP-routed fronthaul 8 networks, or similar types of Transport networks. This specification describes the requirements that the 9 packet switched Transport Network must fulfill in order to support eCPRI services. 10. 11 Scope of Specification: 12 This specification defines the details necessary to qualify and quantify the requirements on the underlying 13 Transport Network needed by the eCPRI layers to provide its services to the application. 14. eCPRI Radio Equipment Control (eREC) eCPRI Radio Equipment (eRE). Control Control User Plane Sync User Plane Sync & Mgmnt & Mgmnt Scope of this specification SAPU SAPS SAPCM SAPU SAPS SAPCM.

5 eCPRI Standard eCPRI Standard specific Protocols specific Protocols Transport Network Interface Transport Network Interface Transport Network Transport Network Layer Transport Network Layer 15. 16 Figure 1 Scope definition 17 Equipment of independent vendors can share a Common Network . Thus, there must be no dependencies 18 (explicit or implied) between equipment of different vendors that use the same Transport Network . The details 19 of the Network implementation shall be separated from the details of its users, , the eCPRI equipment, by 20 means of a Transport Network Interface. This specification provides the eCPRI requirements to enable such 21 separation. 22 The packet switched Transport Network requirements to support eCPRI are independent of the technology 23 used by a given packet Transport Network supporting eCPRI , , the same requirements apply to Ethernet or 24 IP Transport networks.

6 This document refers to the Carrier Ethernet services specified by the MEF Forum, 25 especially the Ethernet Service Attributes defined in [2]. However, Ethernet Transport services are only 26 shown as an example, which are applicable, , to Ethernet-based Transport networks. The requirements 27 (and corresponding definitions) described in this document are equally applicable to other packet Transport 28 networks based on different Transport technologies ( , MPLS or IP) that can provide Transport services 29 similar to the MEF Transport services. 30 In MEF terminology, the Service Provider is the organization providing Ethernet Service(s) and the Transport 31 Network illustrated in Figure 1 is a Network from a Service Provider or Network Operator supporting the MEF.

7 32 service and architecture models. The Subscriber is the organization purchasing and/or using Ethernet 33 Services, , the eRE and eREC illustrated in Figure 1 belong to a Subscriber of Transport service(s). The 34 technical specification of the service level being offered by the Service Provider to the Subscriber is referred 35 to as Service Level Specification (SLS). CPRI. 4 eCPRI Transport Network (2017-10-24). 1 2. Transport Network Terminology and Services 2 This section describes terminology, services, service attributes, etc. that are widely used for Transport 3 networks. Although, this section largely refers to the terminology used by the MEF Forum, neither the 4 Transport Network nor the service provided is limited to Ethernet, other technologies and services, , IP.

8 5 can also be 6 User Network Interface 7 The User Network Interface (UNI) is the physical demarcation point between the responsibility of the Service 8 Provider and the responsibility of the Subscriber (section 7 in [2]). Figure 2 illustrates UNIs between eCPRI . 9 equipment (eRE/eREC) and a Transport Network . It may contain one or more physical termination points ( , 10 Ethernet physical interfaces, see section in [2]). Usually all physical termination points of an eCPRI unit 11 are part of the same UNI. Transport Network eREC eRE. UNI UNI. 12. 13 Figure 2 UNI between a eRE/eREC and a Transport Network 14 Note that the equipment on the Subscriber side of the UNI, , eRE and eREC are referred to as Customer 15 Edge (CE) in [2].

9 16 Transport Connection 17 The connection is the key component of the service(s) provided by a Transport Network . 18 A fundamental aspect of Ethernet Services is the Ethernet Virtual Connection (EVC). An EVC is an 19 association of two or more UNIs. The UNIs associated by an EVC are said to be in the EVC . A given UNI. 20 can support more than one EVC (See section 8 in [2]). Service Frames are transmitted via a MEF UNI, 21 where a Service Frame is from the first bit of the Destination MAC Address through the last bit of the Frame 22 Check Sequence of an IEEE Packet ([2]). 1 The definition of IP Services is an ongoing work at MEF. CPRI. 5 eCPRI Transport Network (2017-10-24). EVC. Transport Network eREC eRE.

10 UNI UNI. 1. 2 Figure 3 Example of EVC and its relation to the UNI. 3 Note that the same packet format is used at each UNI belonging to a particular service provided by a 4 Transport Network . For instance, Ethernet Service Frame on each UNI in the case of an Ethernet service. 5 Alternatively, it can be , IP packet at each UNI. 6 UNI Service Attributes are described in section 9 in [2]. 7 EVC Service Attributes 8 A Transport service is specified using service attributes. Each of these attributes defines specific information 9 about the service that is agreed between a Subscriber and a Provider of the Transport service. It is outside 10 the scope of this document how an agreement is established between a Subscriber and a Provider.