Network Slice Migration via Group Identifier Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network slicing technologies face inefficiencies in migrating user devices between network slices, requiring bulk updates to subscriber profiles and generating significant signaling traffic, which is operationally intensive and resource-consuming.
Innovation Solution
Implementing a group identifier as a symbolic representation of network slice identifiers, allowing the Mobility Management Entity (MME) to translate and update mapping information in a database server, enabling user devices to be moved between network slices without modifying individual subscriber profiles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If bulk updates to subscriber profiles are performed to migrate user devices between network slices, then network slice migration is achieved, but processor and memory resources in HSS and MME are consumed and signaling traffic increases
Solution Approach 1:
The patent introduces a database server as an intermediary component that stores mapping information between group identifiers and network slice identifiers. The MME queries this database server to resolve group identifiers to network slice identifiers, eliminating the need for bulk HSS profile updates. This intermediary database absorbs the complexity of mapping management, allowing the HSS and MME to operate with reduced resource consumption and signaling traffic.
2Reliability
If individual subscriber profiles are updated for each user device migration, then accurate network slice assignment is maintained, but the process becomes operationally intensive and time-consuming
Solution Approach 1:
The patent merges multiple individual subscriber profile management operations into a single group identifier-based approach. Instead of updating each subscriber profile individually in the HSS, the system uses a common group identifier that can be resolved to the appropriate network slice identifier through the database server. This consolidation maintains accurate network slice assignment while dramatically improving migration efficiency by eliminating repetitive individual updates.
3Productivity
If mapping information is stored and updated in a database server, then bulk updates can be performed efficiently, but additional storage and data management infrastructure is required
Solution Approach 1:
The database server performs multiple functions: it stores mapping information between group identifiers and network slice identifiers, resolves group identifiers to network slice identifiers upon MME queries, and enables efficient bulk updates. By consolidating these diverse functions into a single universal component, the system achieves high bulk update efficiency without proportionally increasing overall system complexity. The database server becomes a multi-functional hub that handles various aspects of network slice management.
Data Source
AI summary
A first device can receive an attach request that includes information associated with a user device. The user device can provide the attach request to request access to a network. The first device can provide, to a second device and using the information associated with the user device, a request for information associated with a group identifier that is associated with the user device. The first device can receive, from the second device, the information associated with the group identifier that is associated with the user device based on providing the request for information associated with the group identifier. The first device can determine a network slice identifier that is associated with the user device based on the information associated with the group identifier that is associated with the user device. The first device can permit the user device to access a network slice, of the network, that is associated with the network slice identifier based on determining the network slice identifier.