Network Slicing 5G Virtual Networks Use Cases

Understanding 5G network slicing architecture, slice types (eMBB, URLLC, mMTC), isolation mechanisms, orchestration, and how slicing enables diverse services on shared infrastructure.

What is a Network Slice?

A network slice is an end-to-end logical network comprising radio access, transport, and core network resources, configured and optimized to meet specific service requirements. Think of it as creating multiple "virtual operators" on one physical network.

Slice Characteristics

Standard Slice Types (3GPP)

SST (Slice/Service Type) Categories

Slice Requirements Comparison

Network Slicing Architecture

End-to-End Slice Structure

Core Network Slicing

The 5G Service-Based Architecture (SBA) naturally supports slicing because network functions (NFs) are deployed as microservices. Each slice can have:

• Dedicated NFs — Its own SMF, UPF, PCF instances with custom configurations
• Shared NFs — AMF (Access Management) is typically shared across slices to handle common registration
• NSSF (Network Slice Selection Function) — Determines which slice(s) a device should connect to

RAN Slicing

The radio access network is the hardest part to slice because radio resources (spectrum, power, time) are inherently shared:

Slice Isolation

Why Isolation Matters

If a massive DDoS attack overwhelms the eMBB slice (gaming users), the URLLC slice (hospital) must continue operating perfectly. Isolation ensures:

• Performance isolation — One slice's overload does not degrade another's QoS
• Security isolation — Compromise of one slice does not expose another's data
• Fault isolation — Software bug in one slice does not crash another

Isolation Mechanisms

Slice Lifecycle Management

MANO (Management and Orchestration)

Slice lifecycle follows: Design → Instantiate → Activate → Monitor → Modify → Deactivate → Terminate

A slice can be created in minutes (for emergency services during a disaster) or operate for years (permanent enterprise service). The orchestrator manages:

• Resource allocation across physical infrastructure
• NF instantiation and chaining
• SLA monitoring and auto-scaling
• Multi-domain coordination (if slice spans multiple operators)

Business Models

Who Uses Network Slices?

Current Deployment Status

As of 2024-2025:

• Network slicing is specified in 3GPP Release 16+ and commercially available from major vendors
• Most deployments are 2-3 slices (eMBB + enterprise + IoT)
• Full dynamic slicing with real-time creation/deletion is still maturing
• Korea (SK Telecom), China (China Mobile), and Germany (Deutsche Telekom) lead deployments
• Main challenge: RAN slicing with strict isolation remains complex

Key Takeaways

1. Network slicing creates multiple isolated virtual networks on shared physical infrastructure, each optimized for different service requirements (eMBB, URLLC, mMTC)
2. Each slice is end-to-end (RAN + transport + core) and appears as an independent network to its tenant with guaranteed SLA
3. 5G Service-Based Architecture enables core slicing through independent microservice NF instances per slice
4. RAN slicing is the most challenging aspect because radio resources must be shared across slices with strict isolation guarantees
5. Performance, security, and fault isolation between slices ensures that problems in one slice cannot affect others
6. Network slicing enables new business models — operators can sell customized virtual networks to enterprises, MVNOs, and vertical industries
7. Full dynamic slicing (create/modify/destroy slices in real-time) is the vision; current deployments offer semi-static 2-3 slice configurations