A multivendor, virtualized and future-proof HetNet \u2013 this is the vision that mobile operators have for their next generation deployments, and many want to move towards that ahead of 5G standards. <\/p>\n
Small Cell Forum\u2019s newly published Release 7 provides a critical enabler of that vision – a set of interfaces that will lay the foundations of an open, virtualized HetNet.<\/p>\n
The Forum has extended one of its most successful specifications, the Functional API (FAPI) multi-vendor platform interface that has led to the accelerated deployments of small cells, to a virtualized small cell architecture, with the addition of nFAPI. nFAPI, a set of interfaces for supporting a virtualised MAC\/PHY split will be pivatol in ensuring future interoperability for virtual small cell networks, enabling multivendor C-RAN economics today as well as a smooth evolution path to 5G. This unified framework which allows small cells from different vendors to work together seamlessly, enabling operators to deploy dense networks that will be interoperable and future-proof, and can combine physical and virtual elements. <\/p>\n
The goal of interoperability has been central to the Forum\u2019s work from its foundation, because an open multivendor platform encourages innovation and revolutionizes mobile network economics. As operators start to deploy dense, self-organizing HetNets \u2013 the overall theme of Release 7 \u2013 the interoperability vision is even more important to MNOs. <\/p>\n
Back in 2014, the Forum\u2019s Operator Group listed a set of issues which would be vital for them to adopt small cell virtualization. Prominent among them were that virtualization must \u201csupport innovation across a multivendor ecosystem\u201d and that it must \u201cdeliver a phased roadmap aligned with longer term 5G directions\u201d. And a major recent MNO survey found that 58% of operators plan to implement small cell virtualization by 2020, but 80% of those believe open APIs are essential to their plans. <\/p>\n
Mark Grayson (Cisco & SCF Virtualisation Champion) commented: \u201cThese priorities have guided the Forum\u2019s work and ensured it has been closely aligned to the commercial requirements of MNOs. Operators are starting to implement centralization of small cell functionality together with virtualization and make plans for 5G, but as they make these significant commitments, they need to be sure that their deployments are open and future-proof.\u201d<\/p>\n
This is why nFAPI is so critical at this time. It aligns with the multi-vendor functional split which FAPI defines between the MAC and PHY layers, but allows the network functions to be virtualized. This provides a unified framework for operators to implement virtualized RAN, a trend which is becoming real in small cells more quickly than in the macro network. <\/p>\n
Deployment of centralized architectures, especially in the enterprise, is already accepted as a way to simplify operations and enhance control of key functions like security, policy and resource co-ordination. nFAPI will accelerate that process by ensuring that no operator is locked into a single vendor\u2019s offering. Operators will be able to deploy a combination of physical and virtualized elements, delivering efficiencies and new applications now; laying the foundations for emerging technologies like mobile edge computing (MEC); and with the flexibility to support 5G standards when they are defined. <\/p>\n
Background information:<\/strong> The FAPI (functional application platform interface) is an initiative within the small cell industry to encourage competition and innovation among suppliers of platform hardware, platform software and application software by providing a common API around which suppliers of each component can compete. <\/p>\n Many vendors therefore contributed to the document. The authors were Intel, IP.access and Cisco, and there was input additionally from L&T Infotech, mimoOn, Radisys, Texas Instruments, ASTRI and Qualcomm Technologies, Inc a subsidiary of Qualcomm Incorporated.<\/p>\n The architecture is generic to 3G or 4G small cells (and can adapt to 5G). <\/p>\n FAPI defines several APIs:<\/p>\n \u2022 P1 \u2013 the security coprocessor interface Our specifications were extended to nFAPI (network functional application platform interface) following a virtualization study undertaken by Small Cell Forum, which examined different functional splits between virtual and physical network functions. <\/p>\n The MAC-PHY interface defined in FAPI was identified in the virtualization study as a suitable split point. This has motivated the Forum to define a transportable interface for the split small cell, to establish a scalable ecosystem with a converged approach to virtualization across multiple suppliers.<\/p>\n The nFAPI APIs are:<\/p>\n \u2022 P2 \u2013 the service discovery interface A multivendor, virtualized and future-proof HetNet \u2013 this is the vision that mobile operators have for their next generation deployments, and many want to move towards that ahead of 5G standards. <\/p>\n
\nThe document, \u2018nFAPI and FAPI Specification\u2019, is published as part of Small Cell Forum\u2019s Release 7, a technical and commercial blueprint for deploying open HetNet and SON (self-optimizing network) and laying the foundations for 5G.<\/p>\n
\n\u2022 P2 \u2013 the service discovery interface
\n\u2022 P3 \u2013 the GPS interface
\n\u2022 P4 \u2013 the network listen results interface
\n\u2022 P5 \u2013 the PHY mode control interface
\n\u2022 P6 \u2013 the ciphering coprocessor interface
\n\u2022 P7 \u2013 the main data path interface
\n\u2022 M1 \u2013 the scheduler interface<\/p>\n
\n\u2022 P3 \u2013 the positioning interface
\n\u2022 P4 \u2013 the network monitor mode interface
\n\u2022 P5 \u2013 the PHY mode control interface
\n\u2022 P7 \u2013 the main data path interface
\n\u2022 P8 \u2013 the PHY diagnostics interface
\n\u2022 P9 \u2013 the OAM interface (to be covered in R8)
\n\u2022 P10 \u2013 the synchronization, frequency, phase and time<\/p>\n","protected":false},"excerpt":{"rendered":"