IBM Cloud patterns: Private wireless networks on IBM Cloud Satellite

Communications service providers (CSPs) are partnering with hyperscalers to provide private wireless networks that are owned and fully managed by those who build them. Private wireless networks (PWNs) provide the same kind of connectivity as public wireless networks, so businesses must weigh the pros and cons of private wireless networks using 5G technology. It is important to understand some common patterns as well as the management aspects of these networks, including the components required to create a PWN and its architecture.

Components of a Private Wireless Network

There are many components that make up a private wireless network, but here are the core essentials:

• Spectrum refers to radio frequencies used (and allocated by states) for communications. The choice between licensed and unlicensed wireless spectrum depends on coverage requirements, interference conditions, and regulatory compliance.

• The network core is a control center that provides packet switching, policy control, authentication, session management, access and mobility functions, routing, and network management.

• Radio access network (RAN) includes open RAN-based virtual centralized units (vCUs), virtual distribution units (vDUs), radio units (RUs), gateways, and other equipment that enable wireless communication between end-user devices and the network core. It’s possible. Reliable, efficient and smooth.

When building a private wireless network, complementary elements such as orchestration, service assurance, management, monitoring, and security are required. These components play a pivotal role in ensuring the smooth operation, optimization, and security of private wireless networks, contributing to their resilience and high-performance capabilities.

There are basically three types of companies building these solutions:

• Telecommunications (telecom) providers such as Nokia, Ericsson, Samsung and Mavenir
• Hyperscalers such as IBM, AWS, Azure, and GCP

• Telecommunications service providers such as AT&T, Verizon, and TELUS

Telecom providers work with cloud providers to provide private wireless networks to enterprises, either directly or through telecom service provider or systems integrator (SI) partners.

Figure 1. Network-related components of a private wireless network

Figure 1 shows the networking components needed by a CSP to help customers configure private wireless networks. These are standard network-related components that CSPs use to deploy. Historically, many of these elements were constructed using dedicated hardware. However, significant changes have occurred as the number of these components has shifted to a cloud-native, software-based paradigm. That is, it is a virtualized (and in most cases containerized) wireless access network that includes related components such as vCUs, vDUs, and networks. Virtualized network core.

Figure 2 shows an example of a representative container-based vDU architecture, showing how software has replaced purpose-built hardware in network components. Figure 2 also shows the components of the 5G core service-based architecture. All components are virtualized or containerized. This is important because it presents a huge opportunity for hyperscalers in a space dominated by telcos.

Figure 2 vDU architecture and 5G key components

The other half of the solution involves the software components that the cloud provider brings in to power and complete the solution. These range from automation scripts to orchestration, service assurance, monitoring and logging. The most important aspect is that hyperscalers provide a cloud platform to host the solution and its cloud services. This is indicated by the beige box in Figure 3.

Figure 3. Software-related support functions of private wireless network

Benefits of a Private Wireless Network

These standalone networks can be deployed in industrial environments such as manufacturing floors, warehouses, large hospitals, sports stadiums, and corporate campuses. Enterprises don’t have to meet the constraints of public networks. Instead, you can deploy and control a private network that meets your exact needs.

Figure 4 shows an example architecture where a private wireless network consisting of 5G RAN and 5G core is deployed on a hyperscaler platform with edge applications. One of the key requirements is that the PWN must be deployed on-premises. That topology fits the IBM Cloud Satellite® paradigm, where an on-premises location can be an IBM Cloud Satellite location connected to an IBM Cloud® region via a secure IBM Cloud Satellite link. This design can benefit enterprise customers looking for proximity to essential 5G network components that provide low latency and high throughput capabilities.

Figure 4. Block diagram of a private wireless network.

This architectural pattern meets the need to deliver end users, devices, and applications closer to where they are. User plane applications are deployed in IBM Cloud Satellite locations to support real-time mission-critical use cases. These satellite locations can be on-premises edge data centers or public cloud locations.

Designing a private wireless network on IBM Cloud

By implementing a private 5G network, large enterprises can bring a customized 5G network to their facilities and use high-speed, high-bandwidth, low-latency capabilities while maintaining security. Like most networking solutions, there are two parts: a “managed” component and a “managed” component. The “managed” component is hosted in the partner’s hyperscaler cloud, while the “managed” component is located on the enterprise premises, typically over a secure, high-speed connection between the two locations. In this example, IBM Cloud hosts the “managed” component, while the satellite location runs the “managed” component.

Figure 5 shows the pattern with a private wireless network deployed on-premises on the left (the “remote” IBM Cloud Satellite location). Workloads running in those satellite locations can access support services hosted on IBM Cloud on the right. Network components provided by your carrier are shown in blue. Most of these are deployed in satellite locations, but some carrier management systems can run in the cloud and potentially provide multi-tenant capabilities to support multiple enterprises.

Figure 5. Private wireless network architecture for IBM Cloud Satellite on-premises location.

Imagine a manufacturing plant with a variety of mobile and stationary robots and other programmable devices operating within the plant. Companies may choose to use private wireless networks because they increase the speed of intercommunication required to operate devices while keeping things secure.

In these scenarios, a manufacturing plant can be configured with a remote IBM Cloud Satellite location that runs essential workloads and cloud-related components on-premises. More importantly, the network connectivity required for that location is provided by the PWN. This setup can be replicated at other manufacturing units in the company or at partner suppliers across the state or country. Each unit has its own PWN and is configured as an IBM Cloud Satellite location. All of these satellite locations are managed in IBM Cloud regions.

There is a master control plane running on IBM Cloud that monitors all Satellite locations and provides centralized logging and security services as part of its management services. IBM Cloud site reliability engineers manage all system upgrades and patches. It was mentioned that the satellite link between IBM Cloud Satellite locations and IBM Cloud is a highly secure TLS 1.3 tunnel. Businesses can also connect using IBM’s Direct Link service. All network connections described in this topology are secure.

IBM’s Cloud Pak for Network Automation (CP4NA) provides service orchestration and service assurance capabilities in conjunction with carrier element management systems. IBM Cloud provides monitoring and logging services along with identity access management for accessing cloud environments. CSP may provide additional network monitoring services. This highlights the need for cloud providers to work closely with telco providers. From an enterprise perspective, the enterprise user interface masks complexity by providing a unified interface for simplified management, service provisioning, and comprehensive monitoring and logging. This user interface acts as a single control hub, simplifying operations and improving overall efficiency.

Businesses looking to set up a private wireless network can do so themselves or outsource it to a hyperscaler like IBM. Hyperscalers ultimately work with CSPs to build and manage these networks. It is very important to ensure that your network is built on a flexible platform and can be expanded in the future. Although businesses must be aware of the costs, more and more companies are choosing PWNs because they offer a secure and reliable alternative to public networks.

Learn more about IBM Cloud Pak for network automation