Wireless Handoff via R0KH Table Lookup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless network handoff processes, particularly in IEEE802.11r protocols, face issues with incorrect identification of inter-MD movements as intra-MD movements due to non-unique Mobility Domain Identifiers (MDIDs) assigned by different vendors, leading to inappropriate handoff processes and failure in generating Pairwise Transient Keys (PTKs).
Innovation Solution
Each Access Point (AP) stores a R0KH table containing IDs of all accessible R0KHs, allowing the AP to determine the appropriate handoff process by searching this table based on the R0KH ID in authentication requests, eliminating the need for MDIDs and ensuring correct identification of inter-MD or intra-MD movements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If MDID is used to identify movement type, then handoff process selection is simplified, but identification accuracy deteriorates due to non-unique MDIDs from different vendors
Solution Approach 1:
The patent extracts and removes the MDID field from the authentication request message, eliminating the source of identification errors. Instead of relying on MDID to distinguish between intra-MD and inter-MD movements, the system uses the presence or absence of R0KH ID information to determine the movement type and select the appropriate handoff process.
Solution Approach 2:
The patent introduces R0KH ID as an intermediary identifier to replace MDID. The R0KH ID serves as a more reliable mediator for identifying movement types because it is uniquely associated with specific key holders and does not suffer from vendor-specific duplication issues. The authentication request message is modified to include R0KH ID information, which then becomes the basis for accurate movement type determination.
2Speed
If Fast BSS handoff process is executed for inter-MD movement, then handoff speed is improved, but PTK generation fails due to incorrect process selection
Solution Approach 1:
The patent implements a feedback mechanism where the authentication request message includes R0KH ID information that provides feedback about the client's movement history and current context. This feedback allows the authentication server to accurately determine whether the client is performing intra-MD or inter-MD movement and select the appropriate handoff process accordingly, ensuring PTK generation succeeds.
Solution Approach 2:
The patent performs preliminary identification of movement type before executing the handoff process. By checking the R0KH ID information in the authentication request message beforehand, the system determines the correct handoff process type (Fast BSS or initial MD association) in advance, preventing incorrect process selection and ensuring smooth PTK generation.
3Measurement precision
If MDID is removed from authentication request, then identification accuracy is improved, but message structure complexity increases
Solution Approach 1:
The patent changes the parameter used for movement type identification from MDID to R0KH ID. This parameter change maintains or improves identification accuracy while working within the existing message structure framework. The authentication request message is modified to include R0KH ID information instead of MDID, leveraging the existing key holder identification mechanism rather than creating an entirely new approach.
Data Source
AI summary
Disclosed is an apparatus and method for executing the handoff process in the wireless networks. The apparatus comprises a processor to execute an identity checking mechanism. When a wireless network station wants to move from a source AP to a destination AP, the wireless network station sends an authentication request message to the destination AP. The identity checking mechanism searches a R0KH table of the destination AP for the R0KH ID contained in the authentication request message, and determines a setting parameter for executing a handoff process. Thereby, the wireless network station may execute the handoff process. A R0KH table of an AP consists of all IDs of R0KHs that can be accessed by the AP.