Design
5 minute read
Key elements necessary for deploying the HPE Aruba Networking Private 5G turnkey option are detailed, starting with an overview of the general architecture. Guidance is provided on planning and determining the specific hardware and software subscriptions required for a particular site, ensuring optimal network performance and coverage. Additionally, comprehensive plans for the necessary network infrastructure are included, encompassing all critical components and configurations needed to establish a robust and efficient private 5G deployment.
General architecture
Building on the key components of the private 5G turnkey deployment, the integration of these components within the overall architecture is examined. The analysis highlights the placement of each element—such as small cell radios, the 4G/5G combo core, and other critical infrastructure within the private 5G network—illustrating their roles and interactions in delivering comprehensive and efficient network services.
-
Cloud management dashboard:
-
Starting point for managing the private 5G network at the customer site, including configuration of core, SIM/subscriber information, network services, PLMNs, etc.
-
License or subscription enablement occurs here for licensing the radios and UEs.
-
All the services and orchestration are implemented and run here
-
-
Hardware appliance (resides on-premises)
-
The M2000 core appliances are mounted and deployed on-premises at customer site
-
Serves as the demarcation for ingress/egress of Private 5G traffic
-
Terminates traffic from indoor and outdoor 4G and 5G small cell radios
-
-
Small cell radios: (resides on-premises)
-
4 options: 4G indoor or outdoor radio, 5G indoor or outdoor radio
-
5G small cell radios are designed for higher performance, offering faster speeds, lower latency, and greater network efficiency. However, they exclusively support 5G UEs, meaning older 4G-only devices cannot connect. These radios are ideal for applications requiring advanced 5G capabilities, such as ultra-reliable low-latency communication (URLLC) and high-bandwidth applications.
-
4G small cell radios support a wide range of devices, including older and typically more cost-effective UEs. These radios are compatible with both 4G and 5G UEs, allowing seamless connectivity for legacy and modern devices alike. However, when used with a 5G UE, connectivity is limited to 4G capabilities.
-
-
SIMs/eSIMs: (resides in UE - User Equipment)
-
Both physical SIM and eSIMs are supported
-
SIM provisioning is orchestrated through cloud management dashboard
-

Procurement workflow
Deploying the private 5G turnkey option includes purchasing both hardware appliances as well as software subscriptions. Determining the number of hardware and software subscriptions required for a private 5G deployment involves assessing the specific coverage area, user density, and network performance needs. This process includes:
-
Evaluate the necessary small cell radios options from the RF design perspective
- Indoor and/or Outdoor, 4G and/or 5G small cell radios
-
Determine the number of M2000 core appliances are required (two are required for full redundancy)
-
One core appliance (standalone) supports up to 150 small cell radios and 4000 subscribers
-
Two core appliances (redundancy) support up to 250 small cell radios and 6000 subscribers
-
-
Based on the small cell RF design, define:
-
Type and quantity of small cell radios
-
Duration of small cell radio subscriptions (1, 3, 5, 7, and 10-year subscriptions)
-
-
Based on end user device survey, define the User Equipment (UE)/Device subscription
-
Determine the quantity of SIMs/eSIM required
-
Duration of user device subscriptions (1, 3, 5, 7, and 10-year subscriptions)
-
Once the requirements are established, the ordering process can be streamlined by working with HPE Aruba’s sales and support teams to ensure a tailored and efficient deployment.
Network planning
The private 5G turnkey option includes M2000 core appliance(s) and small cell radios that will be deployed on-premises alongside the customer’s existing network infrastructure. This deployment involves the small cell radios communicating with the M2000 core appliance, the M2000 core appliance interacting with the cloud dashboard, and the small cell radios connecting with the Spectrum Access System (SAS) in the United States. Additionally, managing data traffic requires careful network planning. Therefore, it is essential to identify requirements such as VLAN reservations, switch connectivity, and the specific ports that need to be opened on the customer site’s firewall.

Required VLANs for M2000 core
Required VLANs for M2000 core | Purpose | Uplink port config on switch (tagged/untagged) | |
---|---|---|---|
Management | To communicate to cloud dashboard | untagged | |
Radio | For radios to communicate to core | tagged | |
Service | For UE’s data traffic from M2000 core to outside | tagged | |
Reserved | For internal use of M2000 core (4 sequential VLANs) | N/A | |
UE’s IP pool | For M2000 core to provide DHCP IPs to UEs | N/A | |
Additional Service(s) | (optional) | tagged |
Required VLANs for small cell radios
Required VLAN for small cell radios | Purpose | Uplink port config on switch (tagged/untagged) | |
---|---|---|---|
Management | For radios to communicate to Radio VLAN IP of P5G M2000 core and to SAS | untagged |
The small cell radios should be able to communicate both to the Radio VLAN IP addresses defined on the M2000 core and to SAS (https://spectrum-connect.federatedwireless.com/v1.2) on the Internet for US. DNS should be configured (manual or through DHCP) on radio. For handoffs between radios, PTP grandmaster can be used. If PTP grandmaster is planned to be used on site, the small cell radios should be able to reach the PTP grandmaster.
Ports to be opened in on-premises firewall
Ports to be open | Protocol | |
---|---|---|
443 | TLS | For radio to communicate with SAS via HTTPS |
4500 | TCP | For M2000 core to communicate to cloud |