Trusted WLAN Access with NSWO Reason Code Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face challenges in supporting seamless and non-seamless wireless offload (NSWO) scenarios in trusted wireless local area networks (WLAN) access, particularly in determining network capabilities during Extensible Authentication Protocol (EAP) procedures, which can lead to interworking issues due to differing UE and network capabilities.
Innovation Solution
The method involves a user equipment (UE) requesting a NSWO connection during EAP procedures and receiving a reason code from the network indicating whether NSWO is allowed, allowing the UE to determine network capabilities and adjust its behavior accordingly, such as disconnecting or reauthenticating to request a packet data network (PDN) connection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the UE requests a NSWO connection during EAP procedure, then the UE can attempt to establish non-seamless wireless offload, but the network may not support NSWO leading to authentication failure or inability to establish connection
Solution Approach 1:
The patent applies preliminary action by having the UE send an indication message during the EAP authentication procedure to inform the network of its NSWO capability before actual data transmission. This allows the network to prepare appropriate handling in advance, preventing connection failures that would occur if the UE simply attempted NSWO without prior notification.
Solution Approach 2:
The patent implements feedback mechanisms where the network responds to the UE's NSWO indication with appropriate authorization decisions. The network can send EAP-Success with NSWO authorization, EAP-Failure with retry indication, or other responses that guide the UE's subsequent actions, creating a closed-loop control system that adapts to network capabilities.
2Adaptability or versatility
If the network sends EAP-Failure with retry indication, then the UE can retry authentication, but this increases authentication delay and may lead to repeated failures
Solution Approach 1:
The patent applies dynamics by enabling the UE to dynamically adjust its authentication behavior based on network responses. When the UE receives EAP-Failure with retry indication, it can modify subsequent authentication attempts based on the indicated retry count, progressively adapting its strategy to avoid excessive retries while maintaining connection establishment probability.
Solution Approach 2:
The network provides preliminary guidance by including retry indication information in the EAP-Failure message before the UE attempts reauthentication. This allows the UE to pre-calculate appropriate retry behavior and timing, avoiding unnecessary authentication delays that would occur with blind retry mechanisms.
3Device complexity
If the UE and network do not negotiate capabilities explicitly, then the protocol remains simple, but interworking issues arise due to differing UE and network capabilities
Solution Approach 1:
The patent extracts capability indication from the general authentication flow by introducing a specific indication message format that carries NSWO capability information. This separates capability negotiation from the core authentication mechanism, adding minimal complexity while enabling reliable interworking between UEs and networks with different capabilities.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method to support two scenarios in trusted wireless local area network (WLAN) access is provided herein. The method may be performed, for example, by a user equipment (UE). The method generally includes requesting a nonseamless wireless offload (NSWO) connection to a network during an extensible authentication protocol (EAP) procedure and receiving, after successful authentication, at least one of an internet protocol (IP) address or a reason code from a network entity indicating NSWO is not allowed.