Azcom Technology provide a set of SW/FPGA building blocks – Low-PHY, DFE Chains (DUC, DDC, CFR) – to accelerate customer O-RAN RU development. This O-RAN compliant solution can easily be scaled to support different band and bandwidths, number of carriers and MIMO. Azcom also provides O-RAN compliant M-Plane framework adaptable to different hardware platform and C/U/S-Plane implementation.
Low-PHY, DUC, DDC, CFR IPRs
| Key Overall Feature Support | |
| O-RAN Standard | O-RAN v.9.0 |
| Wireless Standard | 5G, 4G and NB-IoT |
| Lower-Layer Split (LLS) Architecture | O-RAN 7.2x |
| RU Category | Category A, Category B |
| IQ compression | Fixed, BFP and Modulation |
| Duplex mode | FDD, TDD |
| Sub-Carrier Spacing (SCS) | 15/30/60 kHz (5G Numerology 0-1-2) |
| Cyclic prefix | Normal |
| PRACH formats | All Long and Short formats |
| Up/Downlink instantaneous bandwidth | up to 100 MHz |
| Number of Component Carriers | 1/2/3/4 |
| Number of antennas | 4/8/16/32 |
| Beamforming mode | Frequency domain |
| O-RAN Beamforming modalities | Predefined-beam, Weight-based dynamic |
| 5G-NR frequency bandwidth | 5 – 100 MHz (FR1) |
| LTE frequency bandwidth | 1.4 – 20 MHz |
| Ethernet Protocol | O-RAN over eCPRI |
| Ethernet Rate | 10G/25G/50G |
M-Plane
O-RAN compliant M-Plane, adaptable to different hardware, C/U/S-Plane implementations and frameworks to accelerate customer programs. The reference M-Plane procedures are made up of replaceable and reusable components over an innovative event-based middleware. Using an efficient and broker-less publish/subscribe engine, the components can be dynamically and loosely linked so that the M-Plane process orchestration logic can be reused
M-Plane Framework Key Value
- O-RAN v15.00 compliant: most complex features (e.g. supervision, software management, LBM) supported
- Adaptable to 3rd party systems by just replacing thin connectors to vendor’s hardware/firmware
- The publish/subscribe event driven Middleware layer introduces flexibility, modularity and ease of integration
- Free displacement: components reference each other by URI, not by address
- Easy to stub/simulate/refactor components for module testing purposes, also usable for O-DU
M-Plane validation - Availability of debug tools for complete inspection and data injection
