UE NSSAI Storage Management for Roaming Slice Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a roaming scenario, it is unclear how to manage and update the Network Slice Selection Assistance Information (NSSAI) storage for a radio terminal when multiple Mapped S-NSSAIs are associated with a single Serving PLMN S-NSSAI, especially when part or all of these Mapped S-NSSAIs are subject to Network Slice-Specific Authentication and Authorization (NSSAA).
Innovation Solution
The proposed solution involves a UE and a core network node managing and updating NSSAI storage by distinguishing between Mapped S-NSSAIs that are allowed and those subject to NSSAA, with the UE sending registration requests and receiving messages from the core network node to correctly categorize and store these S-NSSAIs, ensuring proper authentication and authorization procedures are followed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple Mapped S-NSSAIs are associated with a single Serving PLMN S-NSSAI in roaming scenario, then network slice selection flexibility is improved, but NSSAI storage management complexity increases
Solution Approach 1:
The patent segments the NSSAI storage management by introducing separate data structures for Allowed NSSAI and Pending NSSAI. When multiple Mapped S-NSSAIs are associated with a single Serving PLMN S-NSSAI, the system divides them into two groups: those that are immediately allowed and those that require NSSAA authentication. This segmentation resolves the management complexity by providing clear organizational rules for different types of network slice selections.
Solution Approach 2:
The patent applies preliminary action by pre-categorizing Mapped S-NSSAIs into Allowed and Pending categories before actual network access. The UE performs preliminary classification of associated Mapped S-NSSAIs based on whether they require NSSAA authentication, and this classification is stored in advance in the NSSAI storage. This preliminary organization simplifies subsequent storage management operations during roaming.
2Productivity
If Mapped S-NSSAIs subject to NSSAA are included in Allowed NSSAI, then service availability is improved, but authentication reliability decreases
Solution Approach 1:
The patent applies preliminary action by pre-identifying and separating Mapped S-NSSAIs that require NSSAA authentication into a Pending NSSAI category. This allows the system to prepare authentication requirements in advance while maintaining clear distinction between immediately allowed slices and those requiring authentication. The UE can indicate support for NSSAA capability in advance, enabling the network to make informed decisions about slice allocation.
Solution Approach 2:
The patent introduces the Pending NSSAI as an intermediary category between Allowed NSSAI and Rejected NSSAI. This intermediary state holds Mapped S-NSSAIs that require NSSAA authentication, allowing the system to maintain service availability by keeping them in the system while ensuring authentication reliability through separate handling. The core network node can then process authentication for these pending items without affecting the Allowed NSSAI.
3Reliability
If NSSAA authentication is performed for all Mapped S-NSSAIs, then authentication reliability is improved, but processing time increases
Solution Approach 1:
The patent applies partial action by performing NSSAA authentication only for Mapped S-NSSAIs that are categorized as requiring authentication, rather than all Mapped S-NSSAIs. The system selectively applies authentication based on the specific requirements of each network slice association. This partial approach maintains authentication reliability for necessary slices while reducing overall processing time by avoiding redundant authentication for slices that don't require it.
Solution Approach 2:
The patent segments the authentication process by dividing Mapped S-NSSAIs into groups that require NSSAA and those that don't. This segmentation allows the system to apply authentication processing only to the necessary subset of slices, thereby maintaining reliability where needed while minimizing time loss through selective processing rather than universal authentication.
4Productivity
If Serving PLMN S-NSSAI is included in both Allowed and Pending NSSAI, then slice service availability is improved, but storage management complexity increases
Solution Approach 1:
The patent segments the storage management by introducing distinct data structures for Allowed NSSAI and Pending NSSAI. When a Serving PLMN S-NSSAI is associated with multiple Mapped S-NSSAIs having different authentication requirements, the system segments them into appropriate categories: Mapped S-NSSAIs that are immediately allowed go into Allowed NSSAI, while those requiring NSSAA go into Pending NSSAI. This segmentation resolves the management complexity by providing clear organizational rules.
Solution Approach 2:
The patent applies local quality by allowing different portions of the NSSAI storage to have different organizational characteristics. The Allowed NSSAI and Pending NSSAI can be structured differently based on their specific purposes: Allowed NSSAI for immediate service and Pending NSSAI for authentication-pending services. This local differentiation simplifies management by tailoring the organizational structure to the specific needs of each category.
Data Source
AI summary
A communication terminal (1) receives a first Single NSSAI (S-NSSAI) included in a configuration update command message, and stores the first S-NSSAI into Rejected NSSAI. In addition, the communication terminal (1) receives a second S-NSSAI included in an Extended rejected NSSAI information element. For example, this allows the communication terminal (1) to properly manage or update its NSSAI storage, when multiple Mapped S-NSSAIs are associated with a single Serving PLMN S-NSSAI and part or all of the multiple Mapped S-NSSAIs are subject to NSSAA.