O-RAN WG7 OMAC-HAR 0-v01 00

O-RAN.WG7.OMAC-HAR.0-v01.
00
Technical Specification
O-RAN White Box Hardware Working Group

Outdoor Macrocell Hardware Architecture and Requirements (FR1)
Specification
This is a re-published version of the attached final specification.
For this re-published version, the prior versions of the IPR Policy will apply, except that the previous requirement
for Adopters (as defined in the earlier IPR Policy) to agree to an O-RAN Adopter License Agreement to access
and use Final Specifications shall no longer apply or be required for these Final Specifications after 1st July 2022.
The copying or incorporation into any other work of part or all of the material available in this specification in any
form without the prior written permission of O-RAN ALLIANCE e.V. is prohibited, save that you may print or
download extracts of the material on this site for your personal use, or copy the material on this site for the
purpose of sending to individual third parties for their information provided that you acknowledge O-RAN
ALLIANCE as the source of the material and that you inform the third party that these conditions apply to them
and that they must comply with them.
O-RAN.WG7.OMAC-HAR.0-v01.00
Technical Specification
O-RAN White Box Hardware Working Group

Outdoor Macrocell Hardware Architecture and Requirements (FR1)
Specification
Copyright © 2021 by O-RAN ALLIANCE e.V.
By using, accessing or downloading any part of this O-RAN specification document, including by copying, saving,
distributing, displaying or preparing derivatives of, you agree to be and are bound to the terms of the O-RAN Adopter License
Agreement contained in the Annex ZZZ of this specification. All other rights reserved.
O-RAN ALLIANCE e.V.

Buschkauler Weg 27, 53347 Alfter, Germany
Register of Associations, Bonn VR 11238
VAT ID DE321720189
Copyright © 2021 O-RAN Alliance e.V. All Rights Reserved. 1

1 Revision History
Date Revision Author Description
2020.10.21 01.00 WG7 Final version for publication
________________________________________________________________________________________________
© 2021 O-RAN Alliance e.V.
Your use is subject to the terms of the O-RAN Adopter License Agreement in Annex ZZZ 2
1 Contents
2 Revision History ......................................................................................................................................... 2
3 Chapter 1 Introductory Material ............................................................................................................. 6
4 1.1 Scope ......................................................................................................................................................... 6
5 1.2 References ................................................................................................................................................. 6
6 1.3 Definitions and Abbreviations ................................................................................................................... 7
7 1.3.1 Definitions............................................................................................................................................ 7
8 1.3.2 Abbreviations ....................................................................................................................................... 8
9 Chapter 2 Deployment Scenarios and White Box Base Station Architecture ...................................... 10
10 2.1 Deployment Scenarios ............................................................................................................................. 10
11 2.2 White Box Base Station Architecture ...................................................................................................... 10
12 Chapter 3 White Box Hardware Architecture ...................................................................................... 12
13 3.1 O-CU Hardware Architecture .................................................................................................................. 12
14 3.1.1 O-CU Architecture Diagram .............................................................................................................. 12
15 3.1.2 O-CU Functional Module Description ............................................................................................... 12
16 3.1.3 O-CU Interfaces ................................................................................................................................. 12
17 3.2 O-DU7-2 Hardware Architecture when deployed at cell site .................................................................... 13
18 3.2.1 O-DU7-2 Functional Module Description ......................................................................................... 13
19 3.2.2 O-DU7-2 Interfaces ............................................................................................................................. 14
20 3.3 O-DU6 Hardware Architecture when deployed at cell site ...................................................................... 16
21 3.4 O-DU8 Hardware Architecture when deployed at cell site....................................................................... 16
22 3.5 FHGW7-2 - Option 7-2 to Option 7-2 Hardware Architecture .................................................................. 16
23 3.6 FHGW6 - Option 6 to Option 6 Hardware Architecture .......................................................................... 16
24 3.7 FHGW7-2->8 - Option 7-2 to Option 8 Hardware Architecture.................................................................. 16
25 3.8 FHGW8 - Option 8 to Option 8 Hardware Architecture .......................................................................... 16
26 3.9 O-RU7-2 Hardware Architecture ............................................................................................................... 16
27 3.9.1 O-RU7-2 Functional Module Description ............................................................................................ 16
28 3.10 O-RU6 Hardware Architecture................................................................................................................. 17
29 3.11 O-RU8 Hardware Architecture ................................................................................................................. 17
30 3.12 Integrated gNB-DU Hardware Architecture ............................................................................................ 17
31 Chapter 4 White Box Hardware Requirements .................................................................................... 17

32 4.1 O-CU Requirements ................................................................................................................................ 17
33 4.1.1 O-CU Performance............................................................................................................................. 18
34 4.1.2 O-CU Interfaces ................................................................................................................................. 18
35 4.1.3 O-CU Environmental and EMC ......................................................................................................... 18
36 4.1.4 O-CU Mechanical, Thermal and Power ............................................................................................. 19
37 4.2 O-DUx Common Requirements ............................................................................................................... 20
38 4.2.1 O-DU7-2 Performance ......................................................................................................................... 20
39 4.2.2 O-DU7-2 Interfaces .............................................................................................................................. 21
40 4.2.3 O-DUx Environmental and EMC ....................................................................................................... 21
41 4.2.4 O-DUx Mechanical, Thermal and Power ........................................................................................... 22
42 4.3 O-DUx Split Option Specific Requirements ............................................................................................ 23
43 4.3.1 O-DU7-2 Specific Requirements ......................................................................................................... 23
44 4.3.2 O-DU6 Specific Requirements ........................................................................................................... 23
45 4.3.3 O-DU8 Specific Requirements ........................................................................................................... 23
46 4.4 O-RUx Common Requirements ............................................................................................................... 24
47 4.4.1 O-RU7-2 Performance ......................................................................................................................... 24
48 4.4.2 O-RU7-2 Interfaces .............................................................................................................................. 27
________________________________________________________________________________________________
1 4.4.3 O-RU7-2 Environmental and EMC ..................................................................................................... 28
2 4.4.4 O-RU7-2 Mechanical, Thermal and Power.......................................................................................... 28
3 4.5 O-RU7-2 Split Option Specific Requirements .......................................................................................... 30
4 4.5.1 O-RU7-2 Specific Requirements ......................................................................................................... 30
5 4.5.2 O-RU6 Specific Requirements ........................................................................................................... 30
6 4.5.3 O-RU8 Specific Requirements ........................................................................................................... 30
7 4.6 FHGWx – Common Requirements .......................................................................................................... 30
8 4.7 FHGWx – Split Option Specific Requirements........................................................................................ 30
9 4.7.1 FHGW7-2 Specific Requirements ........................................................................................................ 30
10 4.7.2 FHGW7-2->8 Specific Requirements .................................................................................................... 30
11 4.7.3 FHGW8 Specific Requirements .......................................................................................................... 31
12 4.8 Integrated gNB-DU Requirements .......................................................................................................... 31
13 Annex ZZZ: O-RAN Adopter License Agreement .................................................................................. 31
14 Section 1: DEFINITIONS ........................................................................................................................................ 31
15 Section 2: COPYRIGHT LICENSE ......................................................................................................................... 32
16 Section 3: FRAND LICENSE .................................................................................................................................. 32
17 Section 4: TERM AND TERMINATION ................................................................................................................ 33
18 Section 5: CONFIDENTIALITY ............................................................................................................................. 33
19 Section 6: INDEMNIFICATION ............................................................................................................................. 33
20 Section 7: LIMITATIONS ON LIABILITY; NO WARRANTY ............................................................................ 33
21 Section 8: ASSIGNMENT ....................................................................................................................................... 34
22 Section 9: THIRD-PARTY BENEFICIARY RIGHTS ............................................................................................ 34
23 Section 10: BINDING ON AFFILIATES ................................................................................................................ 34
24 Section 11: GENERAL ............................................................................................................................................ 34
25
26 Tables
27 Table 2-1 Deployment scenarios ..................................................................................................................... 10
28 Table 4-1 :O-CU Performance Requirements ................................................................................................. 18
29 Table 4-2: O-CU Interface Requirements ....................................................................................................... 18
30 Table 4-3: O-CU EMC Requirements ............................................................................................................. 18
31 Table 4-4: O-CU Mechanical Requirements ................................................................................................... 19
32 Table 4-5: O-CU Thermal Requirements ........................................................................................................ 19
33 Table 4-6: O-DU7-2 Performance Requirements.............................................................................................. 20
34 Table 4-7: O-DU7-2 Interface Requirements .................................................................................................... 21
35 Table 4-8: O-DU7-2 EMC Requirements .......................................................................................................... 21
36 Table 4-9: O-DU7-2 Mechanical Requirements ............................................................................................... 22
37 Table 4-10: O-DU7-2 Thermal Requirements ................................................................................................... 23
38 Table 4-11: O-RU7-2 Performance Requirements ............................................................................................ 24
39 Table 4-12: O-RU7-2 Interface Requirements .................................................................................................. 27
40 Table 4-13: O-RU7-2 Environmental and EMC Requirements ........................................................................ 28
41 Table 4-14: O-RU7-2 Mechanical, Thermal and Power Requirements ............................................................ 28
42
43
________________________________________________________________________________________________
1 Figures
2 Figure 2-1: Outdoor macro-cell architecture with O-DU7-2 at cell site and data center................................... 11
3 Figure 3-1: O-CU Hardware Block Diagram .................................................................................................. 12
4 Figure 3-2: O-DU7-2 with split physical layer function.................................................................................... 13
5 Figure 3-3: O-DU7-2 Functional Block and Interface Diagram. ....................................................................... 14
6 Figure 3-4: Generic O-RU7-2 Functional Module Diagram ............................................................................. 17
7
________________________________________________________________________________________________
1 Chapter 1 Introductory Material

2 1.1 Scope
3 This Technical Specification has been produced by the O-RAN.org.
4 The contents of the present document are subject to continuing work within O-RAN WG7 and may change
5 following formal O-RAN approval. Should the O-RAN.org modify the contents of the present document, it
6 will be re-released by O-RAN Alliance with an identifying change of release date and an increase in version
7 number as follows:
8 Release x.y.z
9 where:
10 x the first digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,
11 etc. (the initial approved document will have x=01).
12 y the second digit is incremented when editorial only changes have been incorporated in the document.
13 z the third digit included only in working versions of the document indicating incremental changes during the
14 editing process. This variable is for internal WG7 use only.
15 The present document specifies system requirements and high-level architecture for the Outdoor Macrocell
16 deployment scenario case as specified in the Deployment Scenarios and Base Station Classes document [1].
17
18 1.2 References
19 The following documents contain provisions which, through reference in this text, constitute provisions of
20 the present document.
21 [1] ORAN-WG7.DSC.0-V02.00 Technical Specification, ‘Deployment Scenarios and Base Station

22 Classes for White Box Hardware’.
23 [2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
24 [3] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". (Rel-16.3.0)
25 [4] ORAN-WG4.CUS.0-v04.00 Technical Specification, ‘O-RAN Fronthaul Working Group Control,
26 User and Synchronization Plane Specification’.
27 [5] Small Cell Forum, SCF222.10.02 5G FAPI: PHY API Specification,
28 https://scf.io/en/documents/222_5G_FAPI_PHY_API_Specification.php
29 [6] Small Cell Forum, SCF223.10.01 5G FAPI: RF and Digital Frontend Control API,
30 https://scf.io/en/documents/223_5G_FAPI_RF_and_Digital_Frontend_Control_API.php
31 [7] 3GPP TS 38.113: “NR: Base Station (BS) Electromagnetic Compatibility (EMC)
32 [8] O-RAN Architecture Description, O-RAN-WG1-O-RAN Architecture Description - v01.00.00
33 [9] O-RAN WG6, Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN.
34 [10] ORAN-WG4.MP.0-v04.00 Technical Specification, WG4 O-RAN Management Plane Specification’.
35 [11] O-RAN TIFG O-RAN End-to-End System Testing Framework v1.0.
36 [12] O-RAN White Box Hardware Working Group Outdoor Macrocell Hardware Reference Design
37 Specification
38
________________________________________________________________________________________________
1
2 1.3 Definitions and Abbreviations
3 1.3.1 Definitions
4 For the purposes of the present document, the terms and definitions given in [2] and the following apply. A
5 term defined in the present document takes precedence over the definition of the same term, if any, in [2]. For
6 the base station classes of Pico, Micro and Macro, the definitions are given in [3].
7 Carrier Frequency: Center frequency of the cell.

8 F1 interface: The standard interface between an O-CU and an O-DUx specified in [8].
9 Integrated architecture: An architecture wherein the O-RUx and O-DUx are implemented on one platform.
10 Each O-RUx and RF frontend are associated with one O-DUx and are connected to O-CU via F1 interface
11 Split architecture: An architecture wherein the O-RUx and O-DUx are physically separated from one another.
12 A switch may aggregate multiple O-RUx (s) to one O-DUx. The O-DUx, switch and O-RUx (s) are connected
13 by the fronthaul interface as defined in [4].
14 Transmission Reception Point (TRxP): Antenna array with one or more antenna elements available to the
15 network located at a specific geographical location for a specific area.
16 Occupied Bandwidth (OBW): It refers to the bandwidth occupied by the base station when operated, defined
17 by the sum of the active bandwidths of the band allocation(s) operated. As defined by 3GPP TS 34.121 section
18 5.8, occupied bandwidth is the bandwidth containing 99% of the total integrated power of the transmitted
19 spectrum, centered on the assigned channel frequency. The bandwidth between the 0.5% power frequency
20 points is the occupied bandwidth.
21 Instantaneous Bandwidth (IBW): It refers to the bandwidth in which all frequency components can be
22 simultaneously analyzed. It is defined by the frequency boundaries of the operating band(s).
23 Frequency Range: It refers to bandwidth defined by the frequency range within which the Base Station can
24 be operated, defined by the band-pass filter of the BS; e.g., 3.4 – 3.8 GHz (400 MHz)
25 gNB: A RAN node providing NR user plane and control plane protocol terminations towards the UE, and
26 connected via the NG interface to the 5GC
27 Frequency Band: A designated frequency range for the operation of the base station and the UE radios. 5G
28 NR frequency bands are divided into two different frequency ranges: Frequency Range 1 (FR1) that mainly
29 includes sub-6GHz frequency bands, some of which are bands traditionally used by previous standards but
30 has been extended to cover potential new spectrum offerings from 410MHz to 7125MHz; Frequency Range
31 2 (FR2) that includes frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range
32 have shorter range but higher available bandwidth than bands in the FR1.
33 Fronthaul Gateway (FHGW): A fronthaul gateway is a physical entity that is located between a distributed
34 unit and one or more radio units where it distributes, aggregates, and/or converts fronthaul protocols between
35 the distributed unit and multiple radio units.
36 Normative terms used in this specification are defined in following manner:
37 Shall: indicates a normative requirement
38 Should: indicated as recommendation
________________________________________________________________________________________________
1 May: indicates a permission
2 1.3.2 Abbreviations
3 For the purposes of the present document, the abbreviations given in [2] and the following apply. An
4 abbreviation defined in the present document takes precedence over the definition of the same abbreviation,
5 if any, as in [2].
6 7-2 Fronthaul interface split option as defined by O-RAN WG4, also referred to as 7-2x
7 3GPP Third Generation Partnership Project
8 5G Fifth-Generation [Mobile Communications]
9 5GC 5G Core
10 ACS Adjacent Channel Selectivity
11 ADC Analog to Digital Converter
12 BMCA Best Master Clock Algorithm
13 BPSK Binary Phase Shift Keying
14 BS Base Station
15 CFR Crest Factor Reduction
16 CLK Clock
17 CPRI Common Public Radio Interface
18 CU Central Unit
19 DAC Digital to Analog Converter
20 DDC Digital Down Conversion
21 DDR Double Data Rate
22 DL Downlink
23 DPD Digital Pre-Distortion
24 DSP Digital Signal Processor
25 DU Distributed Unit
26 DUC Digital Up Conversion
27 eCPRI Enhanced Common Public Radio Interface
28 EMC ElectroMagnetic Compatibility
29 EVM Error Vector Magnitude
30 FAPI Functional Application Platform Interface
31 FEC Forward Error Correction
32 FFT Fast Fourier Transform
33 FH Fronthaul
34 FHGW Fronthaul Gateway
35 FHGWx Fronthaul gateway with no FH protocol translation, supporting an O-DUx with split
36 option x and an O-RUx with split option x, with currently available options 66, 7-27-
37 2 and 88
38 FHGWx→y Fronthaul Gateway that can translate FH protocol from an O-DUx with split option x to
39 an O-RUy with split option y, with currently available option 7-28.
40 FPGA Field Programmable Gate Array
41 GbE Gigabit Ethernet
42 GPP General Purpose Processor
43 IEEE Institute of Electrical and Electronics Engineers
44 IMD InterModulation Distortion
45 IP Internet Protocol
________________________________________________________________________________________________
1 I/O Input/Output
2 JTAG Joint Test Action Group
3 L1 Layer 1, also referred to as PHY or Physical Layer
4 L2 Layer 2, also referred to as Data Link layer in OSI model
5 L3 Layer 3, also referred to as Network layer in OSI model
6 LLS Lower Layer Split
7 LNA Low Noise Amplifier
8 LTE Long Term Evolution
9 MAC Media Access Control
10 MIMO Multiple Input Multiple Output
11 MCP Multi-Chip Package
12 nFAPI Network Functional Application Platform Interface
13 NG Next Generation
14 NR New Radio
15 OAM Operations, Administrations and Maintenance
16 O-CU O-RAN Centralized Unit as defined by O-RAN
17 O-DU O-RAN Distributed Unit as defined by O-RAN
18 O-DUx A specific O-RAN Distributed Unit having fronthaul split option x where x may be 6, 7-2
19 (as defined by WG4) or 8
20 O-RU O-RAN Radio Unit as defined by O-RAN
21 O-RUx A specific O-RAN Radio Unit having fronthaul split option x, where x is 6, 7-2 (as
22 defined by WG4) or 8, and which is used in a configuration where the fronthaul interface
23 is the same at the O-DUx
24 PA Power Amplifier
25 PCIe Peripheral Component Interface Express
26 PDCP Packet Data Convergence Protocol
27 PHY Physical Layer, also referred as L1
28 PLL Phase Locked Loop
29 POE Power over Ethernet
30 QAM Quadrature Amplitude Modulation
31 QPSK Quadrature Phase Shift Keying
32 RAN Radio Access Network
33 RF Radio Frequency
34 RLC Radio Link Controller
35 RRC Radio Resource Controller
36 RU Radio Unit as defined by 3GPP
37 RX Receiver
38 SDU Service Data Unit
39 SFP Small Form-factor Pluggable
40 SFP+ Small Form-factor Pluggable Transceiver
41 SoC System on Chip
42 SPI Serial Peripheral Interface
43 TR Technical Report
44 TS Technical Specification
45 TX Transmitter
46 UL Uplink
47 USB Universal Serial Bus
48 WG Working Group
________________________________________________________________________________________________
1
2 Chapter 2 Deployment Scenarios and White Box Base

3 Station Architecture
4 This chapter consists of two parts: the deployment scenario and the white box architecture. The deployment
5 scenarios outline more specific functional requirements of the base station. All the reference designs shall meet
6 these requirements in order to comply with O-RAN white box standard. In the white box hardware architecture
7 section, it describes the overall gNB hardware architecture and function partition that meet the design
8 requirements. The details on each of these topics are described in the following sections.
9 2.1 Deployment Scenarios

10 The outdoor macro-cell is the targeted deployment scenario of this specification. The requirements of the
11 outdoor macro-cell base station are listed in the white-box Deployment Scenarios and Base Station Classes
12 document [1]. Some of the key requirements described in that document are highlighted here.
13 Table 2-1 Deployment scenarios
Cell type Outdoor Macro-cell

Frequency Band FR1 (n26, n29, n71, n66, n70, n77, n78)
up to 168 MHz for FDD
Instantaneous Bandwidth
up to 280 MHz for TDD
Up to 168 MHz for FDD
Occupied Bandwidth
up to 200 MHz for TDD
Inter site distance 0.5 ~ 2 mile(s)
Antenna Configuration 4T4R ~ 64T64R
O-RAN FH, Split Option 7.2x
Fronthaul Type
CAT-A and CAT-B Radio Units
Midhaul Split Option 2
14
15 2.2 White Box Base Station Architecture

16 In general, the base station hardware architecture can be classified when O-DU7-2 is at cell site or O-DU7-2 is at
17 the data center. In both cases, O-RAN fronthaul split 7-2 and 3GPP standard interface F1 will be used.
18 When O-DU7-2 is at the cell site, the O-RUs will be connected from a multi-sector cell site to the O-DU7-2 . An
19 optional switch/cell site router may be used between cell site O-RUs and O-DU7-2 (i.e. Scenario E.1 from
20 WG6).
21 When O-DU7-2 is at a data center (i.e., the Edge Cloud from [9]), cell site routers/switches will aggregate O-
22 RUs from multiple cell sites to the O-DU7-2. The O-DU7-2 will be connected to the O-CU-CP and O-CU-UP in
23 the mid-haul through F1-C and F1-U interface. The O-CU-CP/O-CU-UP can be in a remote data center (i.e.
24 the Regional Cloud in Scenario C from [9]) or, respectively the O-CU-CP/O-CU-UP can be co-located with
25 O-DU7-2 in the data center (i.e. the Edge Cloud in Scenario B from [9]). Accordingly, when the O-DU7-2 is
26 deployed at a data center site (i.e., on the Edge Cloud, either on a bare-metal machine or as a container/virtual-
27 machine), the servers running the O-DU7-2 shall follow the existing and upcoming specifications from O-RAN
________________________________________________________________________________________________
1 WG6. The cell site cloud specifications are for further study in WG6.
2 The architecture when O-DU7-2 is at the cell site is shown in Figure 2-1. The O-DU7-2 with integrated switch/cell
3 site router is considered for this architecture.
O-RU 7-2
O-CU-CP O-CU-UP O-DU 7-2

FHGW/Switch/
Connectivity (Ethernet) Connectivity (Ethernet) Router O-RU 7-2
(Optional)
O-CU O-DU7-2
O-RU 7-2
O-RAN Fronthaul
6 (Split Option 7-2x)
7 Figure 2-1: Outdoor macro-cell architecture with O-DU7-2 at cell site and data center
________________________________________________________________________________________________
1 Chapter 3 White Box Hardware Architecture

2 Based on the gNB physical implementation architectures discussed earlier, this chapter provides the
3 architecture, major building blocks and all external/internal interfaces for each whitebox.
4 3.1 O-CU Hardware Architecture

5 In 3GPP system architecture, the gNB Central Unit (CU) communicates with the Distributed Unit (DU) via an
6 F1 interface [8]. This interface has been adopted by O-RAN Alliance for O-CU and O-DU connection. F1 is
7 an IP-based protocol interface. F1 interface is split into F1-C and F1-U interfaces.
8 F1-C interface is used for the management of interface setup/configuration, system information, UE context,
9 RRC transfer, paging and warning message transfer. F1-U interface is used for user data transfer and flow
10 control.
11 3.1.1 O-CU Architecture Diagram
12 The O-CU can be implemented with any General-Purpose Processor (GPP) based platform having an optional
13 hardware accelerator block. The O-CU functions can be implemented either on separated hardware platforms
14 or on the same hardware platforms integrated with O-DUx functions. In either case, the O-CU hosts L2/L3
15 functions, whereas O-DU hosts L2/L1 functions which require different CPU, Storage, Acceleration and
16 Networking capabilities. Figure 3-1 shows the hardware blocks and interfaces within the O-CU white box.
Ethernet Digital Processing Hardware

Interface Unit Accelerator
Backhaul
(Ethernet
or
Wireless) Ethernet
Interface
F1
Interface
O-CU (Ethernet)
17
18 Figure 3-1: O-CU Hardware Block Diagram
19 3.1.2 O-CU Functional Module Description
20 The O-CU functional architecture comprises Digital Signal Processing, optional HW Acceleration, and
21 Connectivity (GbE) units as well as memory and storage units as shown in Figure 3-1
22 3.1.3 O-CU Interfaces
23 The O-CU interfaces through backhaul with the vEPC or 5GC core network and via F1 interface with the O-
24 DU7-2. The backhaul and the F1 interfaces are typically implemented with GbE transport/connections.
________________________________________________________________________________________________
1 3.2 O-DU7-2 Hardware Architecture when deployed at cell site

2 Depending on the 3GPP standards and category of the radio unit, the split function blocks within O-DU7-2 and
3 O-RU7-2 may vary accordingly. The O-RAN fronthaul C/U/S-plane specification [4] provides comprehensive
4 information on this topic. The hardware functional partition architecture is shown in Figure 3-2. The High-
5 PHY functions in O-DU7-2 are run on Digital Processing Unit, Hardware Accelerator, or both.
Hardware
Accelerator
Ethernet Digital Timing and

Synchronization 1 PPS (IN or OUT)
Interface Processing Unit (IEEE 1588)
F1
Interface
O-RAN FH
Interface
Ethernet Low
Interface PHY
O-DU7-2 O-RU7-
8 Figure 3-2: O-DU7-2 with split physical layer function
9 3.2.1 O-DU7-2 Functional Module Description
10 The choice of O-DU7-2 hardware components depends on the product design requirements and is outside the
11 scope of this specification. Their descriptions are as follows:
12 Digital Processing Unit

13 The processing unit can be any GPP, FPGA or digital signal processor (DSP), with I/O chipset. It may also
14 be in the form of System-On-Chip (SOC), or Multi-Chip Package (MCP).
15 Memory
16 DDR memory devices are used to store the runtime data and software for the processing unit.
17 Flash Memory
18 On board non-volatile storage device is used to store the firmware and non-volatile data, such as log data.
19 Board Management Controller

20 The controller is used to manage/control the power and monitors the operational status of the board.
21 Storage Device
22 The storage device such as hard drive is used to store OS, driver and applications software.
23 Ethernet Controller
________________________________________________________________________________________________
1 The Ethernet ports transport the fronthaul or backhaul traffic according to the gNB hardware node
2 requirements. The Ethernet device shall support IEEE1588 based timing synchronization.
3 Hardware Accelerator
4 The hardware accelerator is an optional device. For performance improvement, hardware accelerator can be
5 used to process computationally intensive functions (e.g., Forward Error Correction (FEC)) and to offload
6 the processor.
Hardware
PCIe
Accelerator
USB Ports Memory

USB DDR RAM
Channel
Video Port VGA Flash

SPI
Memory
PCIe Slots PCIe Digital Processing Unit SMbus SMBus Port
Serial Ports RS232 Storage

SATA
Drives
Timing Ethernet
Timing Signal Ethernet
Ports
8 Figure 3-3: O-DU7-2 Functional Block and Interface Diagram.
9 3.2.2 O-DU7-2 Interfaces
10 The O-DU7-2 supported interfaces described below are also shown in The choice of O-DU7-2 hardware
11 components depends on the product design requirements and is outside the scope of this specification. Their
12 descriptions are as follows:
13 Digital Processing Unit

14 The processing unit can be any GPP, FPGA or digital signal processor (DSP), with I/O chipset. It may also
15 be in the form of System-On-Chip (SOC), or Multi-Chip Package (MCP).
16 Memory
17 DDR memory devices are used to store the runtime data and software for the processing unit.
18 Flash Memory
19 On board non-volatile storage device is used to store the firmware and non-volatile data, such as log data.
20 Board Management Controller

21 The controller is used to manage/control the power and monitors the operational status of the board.
22 Storage Device
23 The storage device such as hard drive is used to store OS, driver and applications software.
24 Ethernet Controller
________________________________________________________________________________________________
1 The Ethernet ports transport the fronthaul or backhaul traffic according to the gNB hardware node
2 requirements. The Ethernet device shall support IEEE1588 based timing synchronization.
3 Hardware Accelerator
4 The hardware accelerator is an optional device. For performance improvement, hardware accelerator can be
5 used to process computationally intensive functions (e.g., Forward Error Correction (FEC)) and to offload
6 the processor.
Hardware
PCIe
Accelerator
USB Ports Memory

USB DDR RAM
Channel
Video Port VGA Flash

SPI
Memory
PCIe Slots PCIe Digital Processing Unit SMbus SMBus Port
Serial Ports RS232 Storage

SATA
Drives
Timing Ethernet
Timing Signal Ethernet
Ports
8 Figure 3-3: O-DU7-2 Functional Block and Interface Diagram.
9 .
10 Memory Channel Interface

11 Support DDR4 and later memory interface.
12 PCIe Interface
13 Support for PCIe Gen3 x16 and later interface versions; the bandwidth depends on the use cases, and it can
14 be used to connect an accelerator device or network card.
15 Ethernet Interfaces
16 Supports any one or combination of 1GbE/10GbE/25GbE/40GbE links.
17 Serial ATA Interface

18 SATA3 shall be supported in case of software storage, such as hard drive.
19 SPI Interface
20 The SPI interface connects the processor with flash type of device for firmware.
21 Video Interface
22 Video interface is optional
23 USB Interface
24 Used to connect with local device for debug or on-board firmware update.
________________________________________________________________________________________________
1 Miscellaneous Interface
2 Other interfaces that may be needed such as serial port, JTAG, etc.
3 3.3 O-DU6 Hardware Architecture when deployed at cell site

4 ‘This section intentionally left blank’
5 3.4 O-DU8 Hardware Architecture when deployed at cell site

7 3.5 FHGW7-2 - Option 7-2 to Option 7-2 Hardware Architecture

8 The FHGW in the case of split option 7-2 to 7-2 is a multiplexer or a switch where the received data packets
9 are distributed among or aggregated from one or more O-RUs and the signaling and management are
10 appropriately routed to or from specific O-RUs.
11 3.6 FHGW6 - Option 6 to Option 6 Hardware Architecture

13 3.7 FHGW7-2->8 - Option 7-2 to Option 8 Hardware Architecture

14 ‘This section intentionally left blank’. Additional details will be provided in a separate document from the
15 fronthaul gateway task group.
16 3.8 FHGW8 - Option 8 to Option 8 Hardware Architecture

17 ‘This section intentionally left blank’. Additional details will be provided in a separate document from the
18 fronthaul gateway task group.
19 3.9 O-RU7-2 Hardware Architecture
20 3.9.1 O-RU7-2 Functional Module Description
21 In
22 Figure 3-4, we illustrate O-RU7-2 functional blocks that support O-RAN FH with split option 7-2x. There is at
23 least one interface port which supports all fronthaul interface and PoE functionalities. The digital processing
24 unit block of O-RU7-2 is responsible for low-PHY functions such as FFT/IFFT, CP addition/removal, and
25 PRACH filtering. Digital Down Converter (DDC), Digital Up Converter (DUC), Crest Factor Reduction
26 (CFR) and Digital Pre-Distortion (DPD) functions are also performed in digital processing unit. For bandwidth
27 reduction, O-RU7-2 architecture also supports the optional compression and decompression functions of FH
28 interface. The ADC and DAC are mixed signal devices responsible for conversion of data between the digital
29 and analog domains. As such, this block can be included as part of the either the digital processing unit or the
30 radio processing unit. The RF Processing Unit consists of an optional frequency converter (mixer), Power
31 Amplifier (PA)/ Low Noise Amplifier (LNA) and TX/RX filters. An antenna module follows that comprises
________________________________________________________________________________________________
1 physical antennae, RF feed distribution/aggregation network, and calibration network. The timing unit
2 includes any clock and frequency synthesis required as well as other timing and synchronization circuits. The
3 Timing Unit shall derive timing and synchronization for the O-RU7-2 based on the IEEE 1588v2 protocol. In
4 addition, syncE may also be used for timing as defined in O-RAN FH WG4 specifications [4]. In any given
5 implementation, the physical boundaries between blocks may be slightly different, but the logical interfaces
6 between will generally follow those shown in
7 Figure 3-4.
Digital Signal Processing Module RF Processing and Antenna Module s

Optical Interface
(De-)
O-RAN FH/ DDC/ CFR/ ADC/ PA/LNA/ and Antenna
eCPRI Compress ion Mixer
IEEE 1588v2 DUC DPD DAC TX/RX Filters Module
To/From Low-PHY
O-DU7-2x
O-RU7-2x
Timing/LO
10 Figure 3-4: Generic O-RU7-2 Functional Module Diagram
11 3.10 O-RU6 Hardware Architecture

13 3.11 O-RU8 Hardware Architecture

15 3.12 Integrated gNB-DU Hardware Architecture

17 Chapter 4 White Box Hardware Requirements

18 This chapter provides the requirements for various white boxes used within the outdoor macro cell base station.
19 These white boxes are O-CU, O-DU7-2 and O-RU7-2. The O-CU and O-DU7-2 can be implemented in an
20 integrated fashion into one white box hardware or they can be separated. The details of the testing and
21 compliance to these requirements would be taken as part of the TIFG specification [11]. These requirements
22 will be used to define a hardware reference design specification for the outdoor macro cell base station [12].
23 4.1 O-CU Requirements

24 O-CU requirements are described in the following sections, which include the performance, interface,
25 environmental, EMC, mechanical, thermal and power requirements.
________________________________________________________________________________________________
1 4.1.1 O-CU Performance
2 The performance requirements of the O-CU are listed in Table 4-1.
3 Table 4-1 :O-CU Performance Requirements
Parameter Requirement Priority
Synchronization • The solution shall support 1588v2 Synchronization. High

• The solution shall support T-TSC (Telecom Time Slave Clock).
Peak Data Rate Peak data rate shall be calculated as defined in 3GPP TS 38.306
Control Plane < 20 ms (def: message1 to message 5)

Latency High
User Plane < 4 ms (def: PDCP SDU → PDCP SDU)
4 4.1.2 O-CU Interfaces
5 The interface requirements of the O-CU are listed in Table 4-2
6 Table 4-2: O-CU Interface Requirements

1/10 GbE F1 Interface to connect with O-DU7-2 at cell site or
High
25 GbE F1 Interface to connect with O-DU7-2 at data center
Transport Interface
1/10 GbE NG interface to connect with 5G core when O-DU7-2 is at cell
site or 25/100 GbE NG interface to connect with 5G core when O-DU7-2 is High
at data center
7 4.1.3 O-CU Environmental and EMC
8 The EMC requirements of the O-CU are listed in Table 4-3.
9 Table 4-3: O-CU EMC Requirements
Safety, EMC The solution shall comply with the requirements of 3GPP TS 38.113
High
(2017-12R15) [7] for equipment used in telecommunication room
Safety, EMC The solution shall be certified for the required regulatory compliance High
related to EMC and safety
Safety,
Environment and The solution shall support Front to Back airflow High
Reliability
________________________________________________________________________________________________
Safety,
Environment and The solution shall support Front Serviceability High
Reliability
Safety, The solution should support IP65 rated version (if implemented
Environment and outdoors). High
Reliability
1 4.1.4 O-CU Mechanical, Thermal and Power
2 The mechanical, thermal, and power requirements of the O-CU are listed in Table 4-4 and Table 4-5
3 Table 4-4: O-CU Mechanical Requirements
Dimension The solution shall be 1 rack unit in height High
The sled shall meet dimensions of 41 mm (Height) x 215 mm (Width) x

Dimension High
427.5 mm (Depth)
At least include the following status indicators:

Status Indicator
High
LED • 1 LED indicating on/off status of the power supply
• 1 LED indicating on/off status of the transmission link
Power Supply The solution shall support -48V DC power. The tolerance range should High
be within -42V and -58V DC
Power Dissipation The maximum power consumption of the solution in normal conditions High
shall not exceed 400W
Power Drain The solution shall have the ability to reduce the power drain when not at High
full load
5 Table 4-5: O-CU Thermal Requirements
Environment and The solution shall support operating temperature ranges from 0℃ to High
Reliability 50℃ indoors.
Environment and
The solution may have FANs to support temperature requirements. High
Reliability
________________________________________________________________________________________________
Environment and The solution should support extended temperature range (-40℃ to +65 Low
Reliability
℃) if implemented outdoors.
1 4.2 O-DUx Common Requirements

2 The common requirements apply to all the O-DUX regardless of the split option. However, in this version of
3 the specification, the focus will be on O-DU7-2. If more options get standardized in a future version of this
4 document, some of these common requirements may be moved to the specific sub-sections in section 4.3.
5 4.2.1 O-DU7-2 Performance
6 The performance requirements of the O-DU7-2 are listed in Table 4-6.
7 Table 4-6: O-DU7-2 Performance Requirements

For the O-DU7-2 at cell site serving the FDD bands with 4T4R radios, the
solution shall support at least 210 MHz in downlink and 105 MHz in uplink
O-DU7-2 server
For the O-DU7-2 at data center serving the FDD bands with 4T4R radios, the High
Processing
solution shall support at least 2 x 210 MHz in downlink and 2 x 105 MHz in
uplink
Transmission Directly connected with O-RUs at cell site or Connected with O-RUs 40 km High
distance apart
For O-DU7-2 at cell site:
• The solution shall have a built-in GPS receiver for timing that
supports PTP distribution compliant to G.8272.
• The solution shall comply with the following ITU-T specifications
for SyncE:
o Definitions: ITU-T G.8260
o Architecture: ITU-T G.8261
o SSM transport channel and format: ITU-T G.8264
o Clock specifications: ITU-T G.8262 (EEC)
o Functional model and SSM processing: ITU-T G.781
Synchronization • The solution shall support IEEE 1588 Telecom Grand Master (T-
TGM) using G8275.1 profile.
• The solution shall support T-GM conversion to Telecom Boundary
Clock (T-TBC) when GPS is lost.
• The solution shall support Telecom Boundary Clock (T-TBC) per
ITU-T G.8273.2.
• The solution shall meet 4 hour holdover time of frequency,
time/phase.
• The solution shall comply with input and output jitter and wander
requirements specified in ITU-T G.8262 (for EEC).
• For timing synchronization, the solution shall support ORAN LLS-
C1/C2 configuration.
• The solution shall support alternate BMCA specified in G.8275.1
Synchronization For O-DU7-2 at data center: High
________________________________________________________________________________________________
• For timing synchronization, the solution shall support ORAN LLS-
C3 configuration.
• The solution shall support T-TSC.
Peak data rate to be calculated based on the formula provided in 3GPP TS
Peak Rate High
38.306
DL: QPSK, 16QAM, 64QAM, 256QAM, (1024 QAM desired)

Modulation High
UL: π/2-BPSK, QPSK, 16QAM, 64QAM (256QAM/1024 QAM desired)
Latency Up to 200 us fronthaul latency High
1 4.2.2 O-DU7-2 Interfaces
2 The interface requirements of the O-DU7-2 are listed in Table 4-7.
3 Table 4-7: O-DU7-2 Interface Requirements
Fronthaul interfaces connected with either radio unit or fronthaul gateway High
At least one NG interface to 5GC High

Transport Interface
At least one 1/10 GbE F1 Interface to connect with O-DU7-2 at cell site or
High
25 GbE F1 Interface to connect with O-DU7-2 at data center
5 4.2.3 O-DUx Environmental and EMC
6 The EMC requirements of the O-DU7-2 are listed in Table 4-8.
7 Table 4-8: O-DU7-2 EMC Requirements
Safety, EMC The solution shall comply with the requirements of 3GPP TS 38.113 (2017-
High
12R15) [7] for equipment used in telecommunication room
Safety, EMC The solution shall be certified for the required regulatory compliance High
related to EMC and safety
Safety,
Environment and The solution shall support Front to Back airflow High
Reliability
Safety,
Environment and The solution shall support Front Serviceability High
Reliability
Safety, The solution should support IP65 rated version. (if implemented
Environment and outdoors) High
Reliability
________________________________________________________________________________________________
1
2 4.2.4 O-DUx Mechanical, Thermal and Power
3 The mechanical and power requirements of the O-DU7-2 are listed in Table 4-9.
4 Table 4-9: O-DU7-2 Mechanical Requirements
Dimension The solution shall be 1 rack unit in height High
For the O-DU7-2 at cell site, the solution dimensions shall not exceed 19
inch width and 18 inch depth
Dimension High
For the O-DU7-2 at data center, the sled shall meet dimensions of 41
mm (Height) x 215 mm (Width) x 427.5 mm (Depth)
Dimension The solution shall have PCIe Gen 3/4 x16 low profile or half-length slot High
to add to support FEC Accelerator
Dimension The solution shall support a minimum of 64 GB DDR4 or better DRAM High
using all available DIMM slots to maximize memory bandwidth. 8
DIMM slots are preferred.
Dimension The solution shall have at least 2x 240GB SSD drives High
Dimension For the O-DU7-2 at the cell site, the solution with minimum 16 Core and High
clock speed of 2.3 GHz is recommended. Equivalent/higher alternative
processor technology and core counts including combinations of CPUs,
GPUs, FPGAs and ASICs and clock frequencies are acceptable.
For the O-DU7-2 at the data center, the solution with minimum 24 Core
and clock speed of 2.4 GHz is recommended. Equivalent/higher
alternative processor technology and core counts including combinations
of CPUs, GPUs, FPGAs and ASICs and clock frequencies are
acceptable.
Dimension For the O-DU7-2 at the cell site, the solution shall have at least 6x 10G High
ports to carry eCPRI ORAN 7.2x fronthaul traffic from O-RUs to the O-
DU7-2
For the O-DU7-2 at the data center, the solution shall have at least 4x
25G ports to carry eCPRI fronthaul and midhaul traffic
Dimension For the O-DU7-2 at the cell site, the solution shall have 2x 1/10G ports to High
carry ORAN Split 2 midhaul traffic from O-DU7-2 to O-CU
At least include the following status indicators:

Status Indicator
High
LED • 1 LED indicating on/off status of the power supply
• 1 LED indicating on/off status of the transmission link
________________________________________________________________________________________________
For the O-DU7-2 at the cell site, the solution shall have a single DC power
supply. For the O-DU7-2 at the data center, the solution shall have a single
Power Supply AC/DC power supply. High
The solution shall support -48V DC power. The tolerance range should be
within -42V and -58V DC
Power The maximum power consumption of the solution in normal conditions

High
Dissipation shall not exceed 400W
The solution shall have the ability to reduce the power drain when not at
Power Drain High
full load
1
2
3 The thermal requirements of the O-DU7-2 are listed in Table 4-10.
4 Table 4-10: O-DU7-2 Thermal Requirements
Environment and The solution shall support operating temperature ranges from 0℃ to
High
Reliability 50℃ for data center.
Environment and The solution may have FANs to support temperature requirements. High
Reliability
Environment and The solution should support extended temperature range (-40℃ to +55
Reliability ℃) if implemented outdoors. Low
Environment and The solution shall support in-band Redfish Chassis management High
Reliability
Environment and The solution shall have at least 4 dry contact inputs and ability for
Reliability environmental and cabinet alarms monitoring. High
6 4.3 O-DUx Split Option Specific Requirements
7 4.3.1 O-DU7-2 Specific Requirements
8 ‘This section intentionally left blank’.
9 4.3.2 O-DU6 Specific Requirements
11 4.3.3 O-DU8 Specific Requirements
________________________________________________________________________________________________
1 4.4 O-RUx Common Requirements

2 The common requirements apply to all the O-RUX regardless of the split option. However, in this version of
3 the specification, the focus will be on O-RU7-2. If more options get standardized in a future version of this
4 document, some of these common requirements may be moved to the specific sub-sections in section 4.5.
5 In the outdoor environment, the O-RU7-2 hardware is placed on the rooftop, pole or wall of the coverage
6 building; it converts the baseband signals to RF signals for transmission over the air or vice versa. All radio
7 requirements are subject to local regulatory limits, where applicable.
8 4.4.1 O-RU7-2 Performance
9 The O-RU7-2 performance requirements cover all the aspects of radio unit including frequency bands, antenna
10 configurations, power efficiency, etc. Table 4-11 lists the performance parameters related to O-RU7-2.
11 Table 4-11: O-RU7-2 Performance Requirements

Operating band n26, n29, n66, n70, n71, n77, n78 High
The IBW of the n66 O-RU7-2 shall be 90 MHz

The OBW of the n66 O-RU7-2 shall be 90MHz.
The DL IBW of the n70 O-RU7-2 shall be 25MHz, and its UL IBW shall be
15MHz.
The DL OBW of the n70 O-RU7-2 shall be 25MHz, and its UL OBW shall
be 15MHz.
The IBW of the n26 O-RU7-2 shall be 7MHz.
Bandwidth The IBW of the n29 O-RU7-2 shall be 11MHz. High

The IBW of n78 O-RU7-2 shall be 300MHz.
The OBW of n78 O-RU7-2 shall be 200MHz.
Tri-band: n26+n29+n71
O-RU7-2 Multi-
The O-RU7-2 shall have at least 4 RF ports, with n71, n29, and n26 sharing High
band operation
the same RF ports.
________________________________________________________________________________________________
Dual-band: n66+n70
The O-RU7-2 shall have at least 4 RF ports, with n66 and n70 sharing the High
same RF ports.
Expected Multi- Tri-band (n26+n29+n71): 4T4R High

mode and
Transceiver Dual-band (n66+n70): 4T4R High
Configuration Single-band (n77): 8T8R High
(Number of
Transmit/Receive Single-band (n77): 64T64R High
Paths)
Single-band (n78): 32T32R High
The EIRP/output power of the O-RU7-2 shall follow 3GPP TS38.141-1 and
Output Power TS38-141-2 requirements for normal and extreme conditions as well as for
High
Accuracy radiated and conducted tests. (It is desirable to remain within +/- 1dB of the
set power under all operation condition.)
TX off Power Less than -85 dBm/MHz (-89 dBm/MHz desired) per antenna connector or
High
Level TAB connector as per 3GPP TS 38.104 [3]
64QAM: EVM smaller than 8% (5% desired)

EVM at
maximum output 256QAM: EVM smaller than 3.5% High
power
For other modulations, refer to 3GPP TS 38.104 [3]
Operating band
The operating band unwanted emissions must satisfy the Category B limit
unwanted High
defined by the section 6.6.4 in 3GPP TS 38.104 [3].
emissions
Transmitter
The Operating band unwanted emissions must satisfy the Category B limit
spurious High
defined by the section 6.6.5 in 3GPP TS 38.104 [3].
emissions
The Noise Figure of the O-RU7-2 for 4T4R radios shall be lower than 2.5
dB in normal case and lower than 3 dB in worst case (it is desired to have
Noise Figure High
the noise figure below 2.2 dB for the worst case). For massive MIMO, the
noise figure requirement shall be lower than 3.5 dB
The throughput shall be ≥ 95% of the maximum throughput of the reference

Rx sensitivity measurement channel as specified in annex A.1 with parameters specified High
in 3GPP TS 38.104 table 7.2.2-1 for Wide Area BS.
In channel selection, ACS, In-band blocking, out-band blocking, IMD and

other receiver specification must follow the 3GPP guidelines for the
Blocking High
reference sensitivity is allowed to degrade at most 6 dB under all scenarios
of interference signal and corresponding level, as per table 7.4.1.2-1 of [3].
Other Except for all the RF specifications listed above, other RF specifications
High
specifications must follow the requirement in [3].
Modulation DL: QPSK, 16QAM, 64QAM, 256QAM, (1024 QAM desired)

High
Mode UL: π/2-BPSK, QPSK, 16QAM, 64QAM (256QAM/1024 QAM desired)
The tri-band O-RU7-2 (n26+n29+n71): High
________________________________________________________________________________________________
4T4R - n26 shall be 10W per port
4T4R - n29 shall be 40W per port High
4T4R - n71 shall be 30W per port
The dual-band O-RU7-2 (n66+n70): The combined output power shall be at
least 80W per port, under all operating conditions.
The O-RU7-2 shall be able to allocate higher power level for n66 (example: High
Min. Output 60W) and lower power level for n70 (example: 20W). The power setting
power shall be configurable by the operator.
Single band O-RU7-2 (n77):

- 8T8R: 40W per port High
- 64T64R: 80dBm EIRP (integrated antenna)

Single band O-RU7-2 (n78):
High
32T32R: 75 dBm EIRP (integrated antenna)
For n26 band, the O-RU7-2 shall have a feature limiting its TX power and
Regulation High
meet FCC rules on output power as outlined in part 90 and part 22.
The EIRP/output power of the O-RU7-2 shall follow 3GPP TS38.141-1 and
TS38-141-2 requirements for normal and extreme conditions as well as for
EIRP Stability High
radiated and conducted tests. (It is desirable to remain within +/- 1dB of the
set power under all operation condition.)
The O-RU7-2 shall support GPS and/or IEEE 1588v2 for timing
High
synchronization based on O-RAN CUS plane specification [4].
The O-RU7-2 shall support Telecom Slave Clock (T-TSC) to the protocol(s)
as defined for the fronthaul interface. Furthermore, the O-RU7-2 shall
Synchronization High
provide additional noise filtering to filter fronthaul interface dynamic noise
which will help meeting 3GPP frequency accuracy requirement
For timing synchronization, the O-RU7-2 shall support the mandatory

High
configurations as defined by O-RAN WG4 specification [4]
For 4T4R radios:

High
- At least one SFP 10G interface.
For massive MIMO radios:
Optical Interface -At least (1xSFP28) or (2 SFP+) or (1 QSFP) for Fronthaul interface
with 8 MIMO layers High
- At least (2xSFP28) or (1 SFP+ and 1 QSFP) or (2 QSFP) with
Fronthaul interface for 16 MIMO layers
Beamforming Number of Beams: At least 8 SSB beams High
support (for
massive MIMO Horizontal steering angle: 90°-120° High
radios) Vertical steering angle: 15°-30° High
________________________________________________________________________________________________
1 4.4.2 O-RU7-2 Interfaces
2 The interface related requirements of the O-RU7-2 are listed in Table 4-12
3 Table 4-12: O-RU7-2 Interface Requirements

Fronthaul The O-RU7-2 shall be compliant to O-RAN CUS plane specification [4] High
interface
Fronthaul The O-RU7-2 shall be compliant to O-RAN M-plane specification [10] High
interface
Fronthaul The O-RU7-2 shall comply to M-Plane IOT Profile 1 specified in O-RAN M- High
interface plane specification [10]
The O-RU7-2 shall support at least one of the following NETCONF/YANG High
based models for management plane as specified in O-RAN M-plane
Fronthaul
specification [10]:
interface
(a) hierarchical architecture model
(b) hybrid architecture model
The O-RU7-2 shall support direct connection between O-RU7-2 and O-DU7-2 High
Fronthaul
for fronthaul synchronization as specified in O-RAN CUS plane
interface
specification [4]
The O-RU7-2 shall support LLS-C2 and LLS-C3 bridged connection between High
Fronthaul
O-RU7-2 and O-DU7-2 for fronthaul synchronization as specified in O-RAN
interface
CUS plane specification [4].
Fronthaul The O-RU7-2 shall comply to all the test cases specified in O-RAN IOT High
interface specification [11]
The O-RU7-2 shall support Block floating point compression as specified in High
Fronthaul
O-RAN CUS plane specification [4]. The compression bits shall be
interface
configurable through EMS.
Fronthaul The O-RU7-2 shall support Pre-configured Transport Delay Method as High
interface specified in O-RAN CUS plane specification [4]
Fronthaul The O-RU7-2 shall support transmission blanking as specified in O-RAN High
interface CUS plane specification [4]
Fronthaul The O-RU7-2 shall support the counters specified in O-RAN CUS plane High
interface specification [4]
Fronthaul The O-RU7-2 shall support the eCPRI header format, section type and section High
interface extension type messages as specified in O-RAN CUS plane specification [4]
Fronthaul The O-RU7-2 shall support G.8275.1 synchronization as specified in O-RAN High
Fronthaul The O-RU7-2 shall support G.8275.2 synchronization as specified in O-RAN High
________________________________________________________________________________________________
Fronthaul The O-RU7-2 shall support IEEE 1914.3, ITU-T G.826x, G.827x series High
interface specified in O-RAN CUS plane specification [4]
2 4.4.3 O-RU7-2 Environmental and EMC
3 The environmental and EMC requirements of the O-RU7-2 are listed in Table 4-13
4 Table 4-13: O-RU7-2 Environmental and EMC Requirements
Mounting Back of antenna, Tower, Roof top, Pole, or Wall High

method
RF Connector RF connector type should be 4.3-10 female. Location should be on the High
bottom of O-RU7-2, on left side of connector panel arranged in a single 1x4
row and dimensioned from the backside face.
AISG Connector AISG Connector should be standard 8 pin female connector. Location should High
be on the bottom of O-RU7-2 and dimensioned from the backside face.
Optical Optical Connector should be SFP+. Location should be on the bottom of the High
Connector O-RU7-2 and dimensioned from the backside face.
Power Power connector should be: DC Circular Connector, Receptacle, 2-Pin Male. High
Connector Location should be on the bottom of O-RU7-2 and dimensioned from the
backside face. Also, connector should be located on the far-right side of
connector panel to allow ease of installation
Lightning O-RU7-2 shall have lightning protection High

Protection
Grounding The O-RU7-2 shall support grounding. Ground connector should be a two- High
wire ground lug. Grounding lug location should be on the bottom of the O-
RU7-2 and dimensioned from the backside face
The O-RU7-2 shall comply to the following EMC, Safety, Storage, and
EMC, Safety, Transportation Requirements: CFR 47, Part 1.130, Part 15B, UL 62368-1,
Storage, and UL 50E, UL 60950-22, 3GPP 38.113, ETSI EN 300 019-2-4, Severity class High
Transportation 1, Telcordia GR-63, Zone4, Telcordia GR 487, Telcordia GR 63, ETSI 300
019-1-1 Class 1.3, and IEC-61000-4-5.
6 4.4.4 O-RU7-2 Mechanical, Thermal and Power
7 The mechanical, thermal and power requirements of the O-RU7-2 are listed in Table 4-14
8 Table 4-14: O-RU7-2 Mechanical, Thermal and Power Requirements
________________________________________________________________________________________________
The weight of the tri-band O-RU7-2 (n26+n29+n71) shall be less than 35kg. High
Weight The weight of the dual-band O-RU7-2 (n66+n70) shall be less than 30kg. High
(excluding
The weight of the single band 64T64R O-RU7-2 (n77) shall be less than 50kg High
mounting kit)
The volume of the tri-band O-RU7-2 (n26+n29+n71) shall be less than 33

High
Liter.
The volume of the dual-band O-RU7-2 (n66+n70) shall be less than 28 Liter. High
The volume of the single-band 64T64R O-RU7-2 (n77) shall be less than 81
High
Volume Liters.
The volume of the single-band 8T8R O-RU7-2 (n77) shall be less than 42.5
High
Liters.
The volume of the single-band 32T32R O-RU7-2 (n78) shall be less than 45
High
Liters.
Dimensions Maximum dimensions of tri-band O-RU7-2 (n26+n29+n71) and dual-band High

O-RU7-2 (n66+n70) should be 462mm (L) x 340mm (W) x 177 mm (D).
Physical dimensions shall not exceed 890mm x 500mm x 250mm for
64T64R n77 radio. Physical dimensions shall not exceed 420mm x 420mm
x 240mm for 8T8R n77 radio.
Mounting Holes A pattern of M8 mounting holes should be located on backside of the O- High
RU7-2, with a total of 8 holes (4 towards top and 4 towards bottom).
Reliability MTBF ≥ 200,000 hours High
The tri-band O-RU7-2 (n26+n29+n71): shall be less than 1,200 Watt at 100%
High
full loading, under all operational conditions.
The dual-band O-RU7-2 (n66+n70): shall be less than 1,200W at 100% full High
loading, under all operational conditions.
Power The single-band 64T64R O-RU7-2 (n77) shall be less than 1,810W at 100% High
Consumption full loading, under all operational conditions. Typical power measurement
for 100% load may be done following 3GPP procedures for TDD with
7D1S2U configuration using TM1.1 with ~75% DL ratio in the slot.
The single-band 32T32R O-RU7-2 (n78) shall be less than 800W at 100% High
full loading, under all operational conditions. Typical power measurement
for 100% load may be done following 3GPP procedures for TDD with
7D1S2U configuration using TM1.1 with ~75% DL ratio in the slot.
The O-RU7-2 shall operate with the nominal voltage of -48V High
Power supply
The O-RU7-2 shall have protection from power transients and surges with no
High
impact/degradation to its performance or operation.
________________________________________________________________________________________________
In case of power loss to the O-RU7-2, and after the power is restored, the O-
RU7-2 shall be fully functional and operational without any human High
interaction/intervention.
Level of
O-RU7-2 shall be at a minimum IP65 rated if deployed outdoors High
protection
O-RU7-2 shall operate at the temperature range of -40℃ to ＋55℃ with both
Temperature High
cold start and hot start options.
Humidity O-RU7-2 shall operate between 0.03 g/m3 and 30 g/m3 of absolute humidity High
Atmospheric
O-RU7-2 shall operate between 70 kPa and 106 kPa atmospheric pressure High
pressure
Cooling mode O-RU7-2 shall support convection air cooling High
1 4.5 O-RU7-2 Split Option Specific Requirements

2 Besides the common requirements which shall apply to all the radio unit types. The following sections list all
3 the specific requirements that only apply to the designated split option.
4 4.5.1 O-RU7-2 Specific Requirements
6 4.5.2 O-RU6 Specific Requirements
8 4.5.3 O-RU8 Specific Requirements
10 4.6 FHGWx – Common Requirements

12 4.7 FHGWx – Split Option Specific Requirements

14 4.7.1 FHGW7-2 Specific Requirements
16 4.7.2 FHGW7-2->8 Specific Requirements
________________________________________________________________________________________________
1 4.7.3 FHGW8 Specific Requirements
3 4.8 Integrated gNB-DU Requirements

6 Annex ZZZ: O-RAN Adopter License Agreement

7 BY DOWNLOADING, USING OR OTHERWISE ACCESSING ANY O-RAN SPECIFICATION,
8 ADOPTER AGREES TO THE TERMS OF THIS AGREEMENT.
9 This O-RAN Adopter License Agreement (the “Agreement”) is made by and between the O-RAN Alliance
10 and the entity that downloads, uses or otherwise accesses any O-RAN Specification, including its Affiliates
11 (the “Adopter”).
12 This is a license agreement for entities who wish to adopt any O-RAN Specification.
13 Section 1: DEFINITIONS
14 1.1 “Affiliate” means an entity that directly or indirectly controls, is controlled by, or is under common
15 control with another entity, so long as such control exists. For the purpose of this Section, “Control” means
16 beneficial ownership of fifty (50%) percent or more of the voting stock or equity in an entity.
17 1.2 “Compliant Implementation” means any system, device, method or operation (whether implemented in
18 hardware, software or combinations thereof) that fully conforms to a Final Specification.
19 1.3 “Adopter(s)” means all entities, who are not Members, Contributors or Academic Contributors, including
20 their Affiliates, who wish to download, use or otherwise access O-RAN Specifications.
21 1.4 “Minor Update” means an update or revision to an O-RAN Specification published by O-RAN Alliance
22 that does not add any significant new features or functionality and remains interoperable with the prior
23 version of an O-RAN Specification. The term “O-RAN Specifications” includes Minor Updates.
24 1.5 “Necessary Claims” means those claims of all present and future patents and patent applications, other
25 than design patents and design registrations, throughout the world, which (i) are owned or otherwise
26 licensable by a Member, Contributor or Academic Contributor during the term of its Member, Contributor or
27 Academic Contributorship; (ii) such Member, Contributor or Academic Contributor has the right to grant a
28 license without the payment of consideration to a third party; and (iii) are necessarily infringed by a
29 Compliant Implementation (without considering any Contributions not included in the Final Specification).
30 A claim is necessarily infringed only when it is not possible on technical (but not commercial) grounds,
31 taking into account normal technical practice and the state of the art generally available at the date any Final
32 Specification was published by the O-RAN Alliance or the date the patent claim first came into existence,
33 whichever last occurred, to make, sell, lease, otherwise dispose of, repair, use or operate a Compliant
34 Implementation without infringing that claim. For the avoidance of doubt in exceptional cases where a Final
35 Specification can only be implemented by technical solutions, all of which infringe patent claims, all such
36 patent claims shall be considered Necessary Claims.
________________________________________________________________________________________________
1 1.6 “Defensive Suspension” means for the purposes of any license grant pursuant to Section 3, Member,
2 Contributor, Academic Contributor, Adopter, or any of their Affiliates, may have the discretion to include in
3 their license a term allowing the licensor to suspend the license against a licensee who brings a patent
4 infringement suit against the licensing Member, Contributor, Academic Contributor, Adopter, or any of their
5 Affiliates.
6 Section 2: COPYRIGHT LICENSE

7 2.1 Subject to the terms and conditions of this Agreement, O-RAN Alliance hereby grants to Adopter a
8 nonexclusive, nontransferable, irrevocable, non-sublicensable, worldwide copyright license to obtain, use
9 and modify O-RAN Specifications, but not to further distribute such O-RAN Specification in any modified
10 or unmodified way, solely in furtherance of implementations of an ORAN
11 Specification.
12 2.2 Adopter shall not use O-RAN Specifications except as expressly set forth in this Agreement or in a
13 separate written agreement with O-RAN Alliance.
14 Section 3: FRAND LICENSE

15 3.1 Members, Contributors and Academic Contributors and their Affiliates are prepared to grant based on a
16 separate Patent License Agreement to each Adopter under Fair Reasonable And Non- Discriminatory
17 (FRAND) terms and conditions with or without compensation (royalties) a nonexclusive, non-transferable,
18 irrevocable (but subject to Defensive Suspension), non-sublicensable, worldwide patent license under their
19 Necessary Claims to make, have made, use, import, offer to sell, lease, sell and otherwise distribute
20 Compliant Implementations; provided, however, that such license shall not extend: (a) to any part or function
21 of a product in which a Compliant Implementation is incorporated that is not itself part of the Compliant
22 Implementation; or (b) to any Adopter if that Adopter is not making a reciprocal grant to Members,
23 Contributors and Academic Contributors, as set forth in Section 3.3. For the avoidance of doubt, the
24 foregoing licensing commitment includes the distribution by the Adopter’s distributors and the use by the
25 Adopter’s customers of such licensed Compliant Implementations.
26 3.2 Notwithstanding the above, if any Member, Contributor or Academic Contributor, Adopter or their
27 Affiliates has reserved the right to charge a FRAND royalty or other fee for its license of Necessary Claims
28 to Adopter, then Adopter is entitled to charge a FRAND royalty or other fee to such Member, Contributor or
29 Academic Contributor, Adopter and its Affiliates for its license of Necessary Claims to its licensees.
30 3.3 Adopter, on behalf of itself and its Affiliates, shall be prepared to grant based on a separate Patent
31 License Agreement to each Members, Contributors, Academic Contributors, Adopters and their Affiliates
32 under Fair Reasonable And Non-Discriminatory (FRAND) terms and conditions with or without
33 compensation (royalties) a nonexclusive, non-transferable, irrevocable (but subject to Defensive
34 Suspension), non-sublicensable, worldwide patent license under their Necessary Claims to make, have made,
35 use, import, offer to sell, lease, sell and otherwise distribute Compliant Implementations; provided, however,
36 that such license will not extend: (a) to any part or function of a product in which a Compliant
37 Implementation is incorporated that is not itself part of the Compliant Implementation; or (b) to any
38 Members, Contributors, Academic Contributors, Adopters and their Affiliates that is not making a reciprocal
39 grant to Adopter, as set forth in Section 3.1. For the avoidance of doubt, the foregoing licensing commitment
40 includes the distribution by the Members’, Contributors’, Academic Contributors’, Adopters’ and their
41 Affiliates’ distributors and the use by the Members’, Contributors’, Academic Contributors’, Adopters’ and
42 their Affiliates’ customers of such licensed Compliant Implementations.
________________________________________________________________________________________________
1 Section 4: TERM AND TERMINATION

2 4.1 This Agreement shall remain in force, unless early terminated according to this Section 4.
3 4.2 O-RAN Alliance on behalf of its Members, Contributors and Academic Contributors may terminate this
4 Agreement if Adopter materially breaches this Agreement and does not cure or is not capable of curing such
5 breach within thirty (30) days after being given notice specifying the breach.
6 4.3 Sections 1, 3, 5 - 11 of this Agreement shall survive any termination of this Agreement. Under surviving
7 Section 3, after termination of this Agreement, Adopter will continue to grant licenses (a) to entities who
8 become Adopters after the date of termination; and (b) for future versions of ORAN Specifications that are
9 backwards compatible with the version that was current as of the date of termination.
10 Section 5: CONFIDENTIALITY
11 Adopter will use the same care and discretion to avoid disclosure, publication, and dissemination of O-RAN
12 Specifications to third parties, as Adopter employs with its own confidential information, but no less than
13 reasonable care. Any disclosure by Adopter to its Affiliates, contractors and consultants should be subject to
14 an obligation of confidentiality at least as restrictive as those contained in this Section. The foregoing
15 obligation shall not apply to any information which is: (1) rightfully known by Adopter without any
16 limitation on use or disclosure prior to disclosure; (2) publicly available through no fault of Adopter; (3)
17 rightfully received without a duty of confidentiality; (4) disclosed by O-RAN Alliance or a Member,
18 Contributor or Academic Contributor to a third party without a duty of confidentiality on such third party;
19 (5) independently developed by Adopter; (6) disclosed pursuant to the order of a court or other authorized
20 governmental body, or as required by law, provided that Adopter provides reasonable prior written notice to
21 O-RAN Alliance, and cooperates with O-RAN Alliance and/or the applicable Member, Contributor or
22 Academic Contributor to have the opportunity to oppose any such order; or (7) disclosed by Adopter with O-
23 RAN Alliance’s prior written approval.
24 Section 6: INDEMNIFICATION
25 Adopter shall indemnify, defend, and hold harmless the O-RAN Alliance, its Members, Contributors or
26 Academic Contributors, and their employees, and agents and their respective successors, heirs and assigns
27 (the “Indemnitees”), against any liability, damage, loss, or expense (including reasonable attorneys’ fees and
28 expenses) incurred by or imposed upon any of the Indemnitees in connection with any claims, suits,
29 investigations, actions, demands or judgments arising out of Adopter’s use of the licensed O-RAN
30 Specifications or Adopter’s commercialization of products that comply with O-RAN Specifications.
31 Section 7: LIMITATIONS ON LIABILITY; NO WARRANTY

32 EXCEPT FOR BREACH OF CONFIDENTIALITY, ADOPTER’S BREACH OF SECTION 3, AND
33 ADOPTER’S INDEMNIFICATION OBLIGATIONS, IN NO EVENT SHALL ANY PARTY BE LIABLE
34 TO ANY OTHER PARTY OR THIRD PARTY FOR ANY INDIRECT, SPECIAL, INCIDENTAL,
35 PUNITIVE OR CONSEQUENTIAL DAMAGES RESULTING FROM ITS PERFORMANCE OR NON-
36 PERFORMANCE UNDER THIS AGREEMENT, IN EACH CASE WHETHER UNDER CONTRACT,
37 TORT, WARRANTY, OR OTHERWISE, AND WHETHER OR NOT SUCH PARTY HAD ADVANCE
38 NOTICE OF THE POSSIBILITY OF SUCH DAMAGES. O-RAN SPECIFICATIONS ARE PROVIDED
39 “AS IS” WITH NO WARRANTIES OR CONDITIONS WHATSOEVER, WHETHER EXPRESS,
________________________________________________________________________________________________
1 IMPLIED, STATUTORY, OR OTHERWISE. THE O-RAN ALLIANCE AND THE MEMBERS,
2 CONTRIBUTORS OR ACADEMIC CONTRIBUTORS EXPRESSLY DISCLAIM ANY WARRANTY
3 OR CONDITION OF MERCHANTABILITY, SECURITY, SATISFACTORY QUALITY,
4 NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, ERROR-FREE OPERATION,
5 OR ANY WARRANTY OR CONDITION FOR O-RAN SPECIFICATIONS.
6 Section 8: ASSIGNMENT
7 Adopter may not assign the Agreement or any of its rights or obligations under this Agreement or make any
8 grants or other sublicenses to this Agreement, except as expressly authorized hereunder, without having first
9 received the prior, written consent of the O-RAN Alliance, which consent may be withheld in O-RAN
10 Alliance’s sole discretion. O-RAN Alliance may freely assign this Agreement.
11 Section 9: THIRD-PARTY BENEFICIARY RIGHTS

12 Adopter acknowledges and agrees that Members, Contributors and Academic Contributors (including future
13 Members, Contributors and Academic Contributors) are entitled to rights as a third-party beneficiary under
14 this Agreement, including as licensees under Section 3.
15 Section 10: BINDING ON AFFILIATES

16 Execution of this Agreement by Adopter in its capacity as a legal entity or association constitutes that legal
17 entity’s or association’s agreement that its Affiliates are likewise bound to the obligations that are applicable
18 to Adopter hereunder and are also entitled to the benefits of the rights of Adopter hereunder.
19 Section 11: GENERAL

20 This Agreement is governed by the laws of Germany without regard to its conflict or choice of law
21 provisions.
22 This Agreement constitutes the entire agreement between the parties as to its express subject matter and
23 expressly supersedes and replaces any prior or contemporaneous agreements between the parties, whether
24 written or oral, relating to the subject matter of this Agreement.
25 Adopter, on behalf of itself and its Affiliates, agrees to comply at all times with all applicable laws, rules and
26 regulations with respect to its and its Affiliates’ performance under this Agreement, including without
27 limitation, export control and antitrust laws. Without limiting the generality of the foregoing, Adopter
28 acknowledges that this Agreement prohibits any communication that would violate the antitrust laws.
29 By execution hereof, no form of any partnership, joint venture or other special relationship is created
30 between Adopter, or O-RAN Alliance or its Members, Contributors or Academic Contributors. Except as
31 expressly set forth in this Agreement, no party is authorized to make any commitment on behalf of Adopter,
32 or O-RAN Alliance or its Members, Contributors or Academic Contributors.
33 In the event that any provision of this Agreement conflicts with governing law or if any provision is held to
34 be null, void or otherwise ineffective or invalid by a court of competent jurisdiction, (i) such provisions will
35 be deemed stricken from the contract, and (ii) the remaining terms, provisions, covenants and restrictions of
36 this Agreement will remain in full force and effect.
________________________________________________________________________________________________
________________________________________________________________________________________________

O-RAN WG7 OMAC-HAR 0-v01 00

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

O-RAN WG7 OMAC-HAR 0-v01 00

Uploaded by

Copyright:

Available Formats

O-RAN.WG7.OMAC-HAR.0-v01.

O-RAN White Box Hardware Working Group

This is a re-published version of the attached final specification.

O-RAN White Box Hardware Working Group

Copyright © 2021 by O-RAN ALLIANCE e.V.

O-RAN ALLIANCE e.V.

Copyright © 2021 O-RAN Alliance e.V. All Rights Reserved. 1

31 Chapter 4 White Box Hardware Requirements .................................................................................... 17

1 Chapter 1 Introductory Material

21 [1] ORAN-WG7.DSC.0-V02.00 Technical Specification, ‘Deployment Scenarios and Base Station

2 1.3 Definitions and Abbreviations

7 Carrier Frequency: Center frequency of the cell.

36 Normative terms used in this specification are defined in following manner:

37 Shall: indicates a normative requirement

38 Should: indicated as recommendation

2 Chapter 2 Deployment Scenarios and White Box Base

9 2.1 Deployment Scenarios

13 Table 2-1 Deployment scenarios

Cell type Outdoor Macro-cell

15 2.2 White Box Base Station Architecture

O-CU-CP O-CU-UP O-DU 7-2

6 (Split Option 7-2x)

1 Chapter 3 White Box Hardware Architecture

4 3.1 O-CU Hardware Architecture

11 3.1.1 O-CU Architecture Diagram

Ethernet Digital Processing Hardware

18 Figure 3-1: O-CU Hardware Block Diagram

19 3.1.2 O-CU Functional Module Description

22 3.1.3 O-CU Interfaces

1 3.2 O-DU7-2 Hardware Architecture when deployed at cell site

Ethernet Digital Timing and

8 Figure 3-2: O-DU7-2 with split physical layer function

9 3.2.1 O-DU7-2 Functional Module Description

12 Digital Processing Unit

19 Board Management Controller

USB Ports Memory

Video Port VGA Flash

PCIe Slots PCIe Digital Processing Unit SMbus SMBus Port

Serial Ports RS232 Storage

8 Figure 3-3: O-DU7-2 Functional Block and Interface Diagram.

9 3.2.2 O-DU7-2 Interfaces

13 Digital Processing Unit

20 Board Management Controller

USB Ports Memory

Video Port VGA Flash

PCIe Slots PCIe Digital Processing Unit SMbus SMBus Port

Serial Ports RS232 Storage

8 Figure 3-3: O-DU7-2 Functional Block and Interface Diagram.

10 Memory Channel Interface

17 Serial ATA Interface

3 3.3 O-DU6 Hardware Architecture when deployed at cell site

5 3.4 O-DU8 Hardware Architecture when deployed at cell site

7 3.5 FHGW7-2 - Option 7-2 to Option 7-2 Hardware Architecture

11 3.6 FHGW6 - Option 6 to Option 6 Hardware Architecture

13 3.7 FHGW7-2->8 - Option 7-2 to Option 8 Hardware Architecture

16 3.8 FHGW8 - Option 8 to Option 8 Hardware Architecture

19 3.9 O-RU7-2 Hardware Architecture

20 3.9.1 O-RU7-2 Functional Module Description

Digital Signal Processing Module RF Processing and Antenna Module s

10 Figure 3-4: Generic O-RU7-2 Functional Module Diagram

11 3.10 O-RU6 Hardware Architecture

13 3.11 O-RU8 Hardware Architecture

15 3.12 Integrated gNB-DU Hardware Architecture