5G Core Network Slicing for Campus Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Campus Networks face a trade-off between operational efficiency and isolation, as they require efficient component reuse with public networks while maintaining stringent security and reliability through isolation, which is challenging in shared network implementations.

Innovation Solution

A 5G network architecture with functionally separated 5G Core instances, including a central cloud hosting both public and private network slices, and a unified data layer for data management, enables efficient component reuse while ensuring isolation through Network Slicing and dedicated radio resources, allowing for flexible deployment and operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If Campus Networks share components with Public Mobile Network, then operational efficiency is improved through component reuse, but isolation and security are compromised

Engineering Contradiction:
Improveoperational efficiencyVSAvoidisolation and security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The network is segmented into multiple network slices, where each slice represents a logically isolated Campus Network. The 5G Core is divided into separate instances (public 5GC and private 5GC) that can be independently managed while sharing physical infrastructure. This segmentation allows component reuse at the physical level while maintaining logical isolation for security and reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension of isolation by implementing network slicing in the virtualization layer. Instead of physical separation, isolation is achieved through virtual network functions and logical segmentation. The 5GC instances are separated into public and private domains, with dedicated data repositories and control planes, creating isolation in the virtualization dimension while sharing physical resources.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If dedicated networks are deployed for Campus Networks, then isolation and security are improved, but operational complexity and cost increase

Engineering Contradiction:
Improveisolation and securityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Multiple Campus Networks are merged into a single shared 5G infrastructure through network slicing. The public 5GC and private 5GC instances are combined on shared physical infrastructure, including common radio access networks and core network functions. This merging reduces the number of separate physical networks needed while maintaining logical isolation through slice-specific configurations and dedicated data repositories.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The shared 5G infrastructure is designed to serve multiple functions simultaneously. The same physical network components (radio access, transmission, core network) can serve both public mobile network operations and multiple private Campus Networks. The 5GC instances are designed to handle both public and private network traffic, providing multi-functionality that reduces operational complexity compared to fully dedicated networks.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12058611B2Network slicing based campus networks
Publication Date: 2024.08.06 DEUTSCHE TELEKOM AG
  • US12058611B2 patent drawing
  • US12058611B2 patent drawing
  • US12058611B2 patent drawing

AI summary

A 5G network includes an access network (AN), a 5G Core (5GC), one or more campus network components each configured to run 5GC software associated to a campus network, and one or more public network components each configured to run 5GC software associated to a public network. The 5GC comprises a central cloud having functionally separated instances, including: a public 5GC instance configured to host the public network realized as a network slice; a private 5GC instance configured to host one or more campus networks, wherein the one or more campus networks are realized as Network Slices; and a data layer instance configured to host Unified Data Repository (UDR) functionality. Unified Data Management (UDM) functions of both 5GC instances are connected to the data layer instance. A Network Slice Selection Function (NSSF) contains the information about network slices present in both 5GC instances.