User-Specific Network Slice Configuration via Token Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G/NR wireless communication systems lack the ability to provide user-specific network slicing, leading to inconsistent service quality and inefficient resource allocation, as network slices are often configured based on user equipment rather than user identity, resulting in suboptimal service levels and resource utilization.
Innovation Solution
Implementing a system that allows for user-specific network slicing by using tokens to identify users and allocate network slices based on their individual service requirements, enabling different levels of service to be provided to multiple users sharing the same user equipment, thereby optimizing resource allocation and ensuring consistent service quality regardless of the equipment used.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If network slices are configured based on user equipment rather than user identity, then device compatibility is improved, but service quality consistency deteriorates
Solution Approach 1:
The patent segments the network slicing configuration by separating user identity identification from user equipment identification. It introduces a token-based mechanism that divides the authentication and authorization process into distinct stages: device authentication, user identity verification, and service-specific slice allocation. This segmentation allows the system to maintain device compatibility while achieving user-specific service quality consistency.
Solution Approach 2:
The patent introduces an intermediary token mechanism that mediates between user equipment and network slice allocation. The token serves as an intermediary carrier that encapsulates user identity information without requiring direct user equipment configuration for each network slice. This intermediary approach resolves the contradiction by enabling user-specific slicing while maintaining broad device compatibility.
2Reliability
If user-specific network slicing is implemented, then service quality consistency is improved, but system complexity increases
Solution Approach 1:
The patent extracts user identity information from the user equipment itself and places it into a separate token structure. This extraction eliminates the need for complex user-specific configurations within each device while maintaining service quality consistency. The complexity is moved from the device level to the network level where it can be managed more efficiently.
Solution Approach 2:
The patent changes the fundamental parameter for network slice allocation from device-based identifiers to user-based tokens. This parameter change simplifies the system by using a universal token format that can represent any user identity without requiring device-specific adaptations, thereby reducing overall system complexity while maintaining service quality consistency.
3Measurement precision
If pre-configuration of user equipment for specific network slices is required, then network slice allocation accuracy is improved, but resource efficiency deteriorates
Solution Approach 1:
The patent performs preliminary user authentication and token generation before network slice allocation, rather than requiring pre-configuration of each device for specific slices. This preliminary action ensures accurate slice allocation based on user identity while avoiding the wasteful pre-computation of device-specific configurations that would never be used.
Solution Approach 2:
The patent uses token copying as a lightweight mechanism to传递 user identity information across the network without requiring expensive device reconfiguration. The token can be copied and reused for authentication purposes, providing accurate slice allocation information at minimal computational cost compared to full device configuration replication.
Data Source
AI summary
A device may receive, from a user equipment, a token request associated with an application, wherein the token request is associated with a device identifier. The device may generate a device token for the application and the user equipment. The device may provide, using the device identifier, the device token to the user equipment to enable a user to access the application via an application platform. The device may receive, from the application platform, a slice request for a network slice of a network that is to be used for an application session. The device may determine that the user equipment is associated with the application session based on the device token and the device identifier. The device may configure a network slice instance of the network slice. The device may determine a user equipment route selection policy for the application session according to the network slice instance.