Software Control Gateways for Flexible 5G Network Slice Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 5G network architectures lack flexibility in managing network slices for third parties, as access control and authentication are performed before network slice selection, limiting the ability to adapt to the specific needs of different entities.
Innovation Solution
A method and system for decoupling access control and authentication from network functions, allowing third parties to define their own access control policies through software control gateways instantiated within the operator's network, enabling dynamic adaptation and update of access control mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If access control and authentication are performed before network slice selection in the current 5G architecture, then network security is maintained through centralized control, but the system loses flexibility in adapting to specific third-party needs and cannot dynamically customize access policies for different network slices
Solution Approach 1:
The patent segments the network architecture by introducing software control gateways that are specific to each network slice or third party. These gateways handle access control and authentication independently for their respective slices, rather than using a single centralized authentication mechanism for all slices. This segmentation allows each slice to have customized access policies while maintaining overall network security.
Solution Approach 2:
The patent introduces software control gateways as intermediary components between the core network and third-party network slices. These gateways act as mediators that enforce access control policies specific to each third party or network slice, enabling flexible customization without compromising the centralized security architecture of the core network.
2Ease of manufacture
If a centralized network architecture is used for access control, then implementation is standardized and secure, but laborious interventions are required to manage and update access control policies for different third parties
Solution Approach 1:
The patent enables software control gateways to autonomously manage access control policies for their respective network slices. Each gateway can independently authenticate devices, enforce access rules, and manage connections without requiring manual intervention from network operators. This self-service capability significantly reduces the time and effort needed to manage access control for multiple third parties.
Solution Approach 2:
The patent introduces dynamic access control where software gateways can adaptively enforce policies based on real-time conditions, device characteristics, and network slice requirements. Access control rules can be dynamically updated and adjusted without requiring laborious reconfiguration, allowing the system to respond flexibly to changing third-party needs.
3Productivity
If network slices are virtually isolated but share physical infrastructure, then resource utilization is optimized, but third parties cannot fully control access to their specific network layer
Solution Approach 1:
The patent introduces software control gateways that create logical segmentation within each network slice, allowing third parties to control access to their specific virtual network layer while sharing the physical infrastructure. Each gateway manages access control independently for its assigned slice, enabling fine-grained control over which devices can access which network slice without compromising the shared physical resource model.
Data Source
Figure 1~3
Figure 4
AI summary
The management method enables the communication device to benefit from a network connectivity provided by a third party via the operator network, and comprises: - a step (E30) of receiving, from the communication device, a request for attachment to the operator network and an identifier of the third party; - a step (E40) of obtaining, by using the third-party identifier, a piece of contact information of an instantiated software control gateway for controlling access to a section of the network allocated by the operator to the third party, this piece of contact information comprising a reachability address of the software control gateway or an identifier of the section of the network allocated to the third party and for which an access is controlled by the software control gateway; and - a step (E50) of sending a message to the device, containing the piece of contact information and inviting the communication device to attach to the software control gateway using this contact information.