A person is holding a smartphone, with a cellular tower structure in the background.

How to Make Automated 5G Network Slicing Work

In this blog we will drill into service activation, turn-up, and lifecycle assurance for network slicing. To kick off, let us briefly review what a network slice is, how the concept evolved from 4G to 5G, and why automation is essential to making slices operational at scale.

What is a network slice?

Early 3rd Generation Partnership Project (3GPP) work describes a network slice as a logical network that provides specific network capabilities and characteristics across an end-to-end set of resources. In practical terms, a slice is a tailored service environment built from network functions, connectivity, policies, and resources that together deliver the performance a service requires. Those requirements may emphasize capacity and throughput, reliability and latency, mobility, security, isolation, or massive device scale.

Specific examples of service types and slice performance needs include:

You can think of network slices as a set of network performance “knobs” which can be tuned for a specific customer, application, or event.

5G brings dynamic, high-scale slicing

Network slices are formed from sub-networks spanning the RAN, transport, core, edge, and application domains. In 4G, service separation often relied on access point names (APNs), bearer routing, and quality of service (QoS) settings to logically segment traffic, with much of the segmentation anchored in the packet core. That model proved useful for services such as Voice over Long-Term Evolution (VoLTE) and enterprise APNs, but it was relatively static and operationally heavy to expand.

5G introduced a more service-aware, end-to-end model that extends from the device through the radio access network (RAN), transport, 5G Core, and data network. The 5G service-based architecture includes functions such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), and policy and exposure functions that help make slices more programmable. The promise is not simply to create slices, but to activate, assure, and change them dynamically as service needs evolve.

5G slicing requires automated assurance

5G network slicing requires automation to fulfill its true potential. That means that operational testing and assurance to design, onboard, deploy, operate, and maintain slices also need to be automated. This includes a set of critical testing and assurance functions such as validating the performance of new slices, proactively monitoring service levels, and isolating faults.

In our 5G engagements with tier-1 providers, operators were exploring a wide range of slicing strategies. Some wanted a small number of standardized slices for broad service categories. Others were planning more granular slices for enterprise, public safety, private 5G, live events, broadcast, and industry-specific services. Either way, manual processes are not fast enough or economical enough to support slice activation and assurance at commercial scale.

Our recommended approach is to integrate automated assurance into slice activation from the beginning, then extend it across the full lifecycle of the slice.

Keysight’s approach to 5G slice activation

Automated assurance for 5G slicing should include distributed active test agents that emulate real service behavior across the user, RAN, transport, core, edge, cloud, and application path. Key performance metrics such as throughput, packet loss, latency, jitter, availability, voice, video, and application responsiveness should be measured from the user or service perspective. The controller and analytics layer should integrate with orchestration, automation, and operational systems so that test results can trigger workflows, validate changes, and support fault isolation.

During design, active test agents help identify which services benefit from a dedicated slice and which QoS, routing, policy, or edge configurations deliver the required experience. During deployment, automated tests should run when a new slice is activated to validate that the service is ready before users depend on it. Once the slice is operational, tests should run continuously to confirm that performance objectives and service-level agreements (SLAs) are being met. If degradation appears, the same active test framework can segment the service path and help determine whether the issue is in the RAN, backhaul, core, edge, cloud, or application domain.

By proactively validating performance during activation and operation, providers can assure they will deliver on the performance promises they have made for the slice. For slices tied to enterprise SLAs, public safety, live events, broadcast, or other high-value services, meeting those promises is about more than customer satisfaction. It protects revenue, reduces operational risk, and creates confidence that the slice can be monetized.

Automated slice assurance is no longer a future-looking concept. Keysight has supported customers such as T-Mobile as they brought advanced 5G services, private 5G, and network slicing to high-profile live environments including the Professional Golfers’ Association (PGA) championships and Formula 1 events. These environments make the value of active assurance concrete: multiple services, stakeholders, and performance expectations operating at once, with little tolerance for blind spots. Active testing helps validate the service before the event, monitor it continuously during operation, isolate where degradation begins, and confirm recovery after a fix. That is how network slicing moves from a technical architecture to a reliable, monetizable service model.

limit
3