Small Cell Forum (SCF) announced the release of three updated specifications within the 5G FAPI suite – 5G FAPI PHY API, 5G FAPI: P19 RF and Digital Frontend Control API, and 5G nFAPI.
The specifications are used in millions of the world’s system-on-a-chip (SoC) small cells. FAPI sits at the crucial confluence of L1 hardware and L2 application and can be utilized in a variety of disaggregated RAN architectures (ranging from fully integrated to split-2/6/7.2x).
nFAPI is an interface for supporting a virtualized MAC/PHY split and is pivotal in ensuring interoperability for virtual small cell networks, enabling multivendor C-RAN economics today as well as a smooth evolution path to 5G.
The continual development of the FAPI specifications by SCF, with commitment to regular release updates, ensures the maturity, performance and relevance of the APIs, as well as their alignment with other major industry standards.
New and updated features in SCF222 5G FAPI PHY API:
New features:
- New radio (NR) positioning (Rel-16)
- 7.2x FH status awareness
Updated features:
- Delay Management: added timestamp-free option
- Shared-memory: streamlined throughout the specification; support for 64-bit pointers
- Robust error handling: extended status report, P5 timeouts
- Mixed numerology: updated to account for new features since FAPIv2, clarity and performance.
New and updated features in 5G nFAPI:
- Continuing alignment with evolution of FAPI specifications
- Optimizations in nFAPI headers and messages
- Recommendations for non-ideal fronthaul as nFAPI transport
SCF member companies involved in the development of the upgraded specifications this year were: Qualcomm, Radisys, Picocom, Reliance Jio, BT and Analog Devices.
Andrei Radulescu, FAPI Rapporteur and Senior Staff Engineer, Qualcomm Technologies
Small Cell Forum is a key enabler for RAN disaggregation. Multiple splits associated with virtualized open network architectures are made possible by the Forum’s continuing evolution of the FAPI interface, which provides the essential link between the software functions of the MAC and hardware functions of the physical layer.
