SNPN Authentication Reject Handling via Credential List Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for handling authentication rejects in Stand-alone Non-Public Network (SNPN)-enabled User Equipment (UE) do not effectively manage rejection scenarios when UE attempts to access an SNPN using credentials from a separate entity.
Innovation Solution
A method where the UE is configured with a 'list of subscriber data' containing entries with subscriber identifiers, credentials, and SNPN selection parameters. Upon receiving an authentication reject message, the UE considers the selected entry as invalid, allowing access to the SNPN using credentials from another valid entry in the list.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UE uses a single entry from the list of subscriber data for SNPN access, then the authentication process is simple, but the service continuity is interrupted when authentication is rejected
Solution Approach 1:
The list of subscriber data is segmented into multiple independent entries, each containing alternative subscriber identifiers and credentials. When one entry fails authentication, the UE can switch to another entry without affecting the overall authentication capability, thus maintaining service continuity while managing complexity through modular organization of credential sets.
Solution Approach 2:
The UE pre-configures multiple subscriber identifier and credential sets in the list of subscriber data before authentication is needed. This beforehand preparation creates a cushion against authentication rejection, ensuring that if one credential set fails, alternative credentials are already available to maintain service continuity without interruption.
2Adaptability or versatility
If the UE maintains multiple entries in the list of subscriber data, then the service continuity is improved, but the management complexity increases
Solution Approach 1:
The UE autonomously manages the list of subscriber data entries without requiring external intervention. The device automatically selects, validates, and updates credential entries based on authentication outcomes, performing self-service operations that maintain multiple credential sets while simplifying user interaction and reducing operational complexity.
Solution Approach 2:
The UE dynamically changes parameters such as subscriber identifier format and credential type based on the selected entry in the list. This flexibility allows the system to adapt to different authentication requirements while maintaining a unified management approach, balancing adaptability with ease of operation through parameter-based configuration rather than structural complexity.
3Productivity
If the UE switches to alternative credentials upon authentication rejection, then the service interruption is minimized, but the authentication process time increases
Solution Approach 1:
The UE performs preliminary organization of multiple credential entries in the list of subscriber data before authentication is needed. By pre-structuring the credential sets and establishing selection criteria in advance, the device can quickly switch to alternative credentials upon rejection without time-consuming processing, thus minimizing authentication time while maintaining access efficiency.
Solution Approach 2:
When authentication is rejected, the UE rapidly skips to the next available entry in the list of subscriber data without extensive verification or processing delays. This rushing through of alternative credentials minimizes the time loss associated with authentication retries while maintaining productivity by quickly establishing valid access.
Data Source
AI summary
A method of handling authentication reject upon accessing an SNPN using credentials from a credential holder is proposed. A UE is configured with a “list of subscriber data”. The UE selects an SNPN using the configured list of subscriber data, e.g., based on the SNPN selection parameters contained in a selected entry of the list of subscriber data. Based on the selected entry, the UE selects an SNPN, and then tries to access the selected SNPN using credentials supplied by a subscribed SNPN. When UE receives an authentication reject message from the network, UE considers that the selected entry of the list of subscriber data is invalid. However, other entries related to the current selected SNPN are still valid. UE is still able to access the current selected SNPN, using credentials supplied in another entry of the list of subscriber data.