Network Slice Authentication Handling Roaming Collisions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network slice-specific authentication and authorization (NSSAA) procedures in 3GPP 5G systems do not adequately handle roaming scenarios, collisions between different procedures, and abnormal cases, leading to potential disruptions in user experience and incorrect release of PDU sessions.
Innovation Solution
The proposed solution involves enhancing the NSSAA procedure to consider the requested mapped NSSAI IE during roaming, handling collisions between NSSAA and other procedures, and providing methods to manage abnormal cases such as transmission failures and unnecessary release of NAS connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the NSSAA procedure is performed for all requested S-NSSAIs, then network security and authorization are improved, but the complexity of the authentication procedure increases
Solution Approach 1:
The authentication procedure is segmented into two distinct phases: initial authentication using the 5GMM authentication method, followed by a separate NSSAA phase for network slice-specific authorization. This segmentation allows each phase to handle specific tasks independently, improving security while managing complexity through structured separation of concerns.
Solution Approach 2:
The 5GMM authentication is performed as a preliminary action before the NSSAA procedure. By establishing basic authentication credentials first, the system prepares the groundwork for subsequent slice-specific authorization, reducing the complexity of the overall process by breaking it into preparatory and execution stages.
2Measurement precision
If the NSSAA procedure is enhanced to handle roaming scenarios with requested mapped NSSAI IE, then the accuracy of PDU session management during roaming is improved, but the device complexity increases
Solution Approach 1:
The NSSAA procedure is enhanced with local quality by specifically handling roaming scenarios through the requested mapped NSSAI IE. This targeted enhancement adds precision for roaming cases without unnecessarily complicating the procedure for non-roaming scenarios, maintaining simplicity where it is not needed while improving accuracy where required.
Solution Approach 2:
The requested mapped NSSAI IE acts as an intermediary element that carries slice selection information between the UE and network during roaming. This intermediary structure enables accurate PDU session management in roaming scenarios by providing the necessary mapping information without requiring complex direct handling mechanisms.
3Reliability
If the NSSAA procedure handles procedure collisions and abnormal cases, then the reliability of user experience is improved, but the complexity of error handling increases
Solution Approach 1:
The NSSAA procedure incorporates beforehand cushioning by implementing proactive error handling mechanisms that anticipate and prepare for procedure collisions and abnormal cases. By establishing fallback procedures and collision detection mechanisms in advance, the system maintains user experience reliability without requiring complex reactive error handling, as the cushioning measures prevent many errors from occurring in the first place.
Data Source
AI summary
The present disclosure relates to a pre-5th-Generation (5G) or 5G communication system to be provided for supporting higher data rates Beyond 4th-Generation (4G) communication system such as Long Term Evolution (LTE). A method, for a user equipment (UE) is disclosed. The method comprises: transmitting, by the UE to a network entity, a registration request message including a registration type information element (IE) indicating a periodic registration updating or a mobility registration updating; receiving, by the UE from the network entity, a registration accept message including a pending network slice selection assistant information (NSSAI); and determining, by the UE, that a previously received allowed NSSAI as invalid based on the registration accept message.