In 5GENESIS, the Surrey platform is used to demonstrate the capability of 5G networks to use and exploit multiple radio access technologies that can support massive Machine Type Communications (mMTC) services. The platform supports commercial 4G and 5G NR and features such as network slicing, function virtualization, SDN control and mobile edge computing. Both stand-alone and non-standalone network configurations are supported, providing coverage based on commercial Lte & 5G NR operating in 700, 2600, and 3500 MHz bands. The platform also supports mmWave PtP/PtMP and satellite backhauling. The set-up of the platform is foreseen to provide support for NB-IoT and LoRa air interfaces, combined under a flexible Radio Resource Management (RRM) to showcase massive IoT use-case scenarios. The initial plan, in the context of the ICT-17 call (5GENESIS) considers KPIs related to capacity, latency, scalability and reliability. The platform provides experimentation facilities to verticals and is also able to support eMBB and URLLC related use-cases, coming from ICT-19 or from other projects.
The testbed consists of separately managed 4G and 5G RAN and core-network segments. The 5G segment has been designed to employ the best of evolving NFV and SDN implementations and features. This architecture is able to inter-connect with and support different RAN configurations, C-RAN, D-RAN etc., according to available transmission options. The testbed currently covers the whole of the main campus of the University of Surrey, which spans an area of around 4km2. The RAN segment of the testbed is illustrated below.
The Outdoor deployment, consists of 4G ultra-dense C-RAN comprising 3 macro cells (Lte-A TDD, tri-sector), plus 39 Lte-A TDD small-cell sites, all operating at 2.6 GHz (BW = 2x 20 MHz ; 4×4 MIMO) as well as 1x 4G FDD site operating at 700 MHz ; (BW = 10/20 MHz ; 2×2 MIMO), and 8x 5G NR TDD sites, operating at 3.5 GHz (BW = 100 MHz; 64×64 MIMO). Additionally, 28 GHz (PtP), 60GHz (PtMP) mmWave and satellite backhauling are also supported. The Indoor deployment (Lte-A based C-RAN) consists of 6x TDD and 6x FDD cells over 2 floors, and Wi-Fi APs. The Core Network supports separate 4G and 5G core segments. The 4G segment is based on Rel-14 EPC ‘CUPS’. The 5G segment supports virtualised core functions and Rel-15 features such as Context Awareness and simplified control plane. The testbed also supports edge computing to demonstrate MEC (co-located with the access nodes deployed at the campus) capabilities.
Lte-A, WiFi, 5G NR, 5G UEs, NB-IoT, In-house developed slicing, orchestration and virtualization managers, SDN in transport and core, MEC, centralised storage for VNFs (repository), mmWave and satellite backhauling.
Verticals can deploy own services in the platform or can remote connect to the platform (via secure PtP VPN connection using the JANET network). The platform offers the common 5GENESIS Experimenter Interface used to describe services and experiments to be executed on the platform.
Extensions: The platform can be extended with further functionality depending on the vertical requirements and needs.
Projects using the platform: 5Genesis, Clear5G, Sat5G, SoftFIRE/SoftFIRE+, commercial industry projects.
Vendors/Manufacturers/Providers providing support for the platform: Huawei, Quortus, Aruba, MYCOM, Vodafone, FoN, RunEL, INFOLYSIS, Ericsson.
Disclaimer: This document describes a platform to be built in the context of 5GENESIS H2020 project. The technical aspects refer to the platform as expected by the end of 2019 according to the work plan. The objective of the document is to facilitate the preparation of project proposals for the call ICT 19. This is not a contractual document, and features could be changed by 5GENESIS consortium due to incidences or to the feedback from the EC. Any interested entity may approach the platform operators and may request using the platform on a non-profit basis as part of a research and development activity. Usage of the platform is subject of a negotiated legal agreement and compensation scheme covering the associated effort and operational cost of the platform provider and contributors.