Anchor Node Selection in Distributed Mobility Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Dense networks face challenges in managing traffic offload due to increased handovers between anchor nodes, leading to poor user experience and network performance, as current Distributed Mobility Management (DMM) techniques result in frequent handovers and inefficient data path utilization.
Innovation Solution
Implement systems and methods for selecting the most appropriate anchor node based on capability information, load information, and historical data, using techniques such as groupings and route prediction to minimize handovers and optimize data paths in dense networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If DMM is used in dense networks with multiple anchor nodes, then traffic offload capability is improved, but handover frequency increases and user experience deteriorates
Solution Approach 1:
The system performs preliminary anchor node selection based on capability information, load information, and grouping data before handover occurs. This advance preparation allows the device to choose optimal anchor nodes, reducing unnecessary handovers and improving user experience while maintaining traffic offload benefits
Solution Approach 2:
The system uses feedback mechanisms where anchor nodes provide capability information and load information to devices. Devices use this feedback to make intelligent selection decisions, avoiding overloaded nodes and reducing handover frequency, thus resolving the contradiction between traffic offload and user experience
2Quantity of substance
If multiple anchor nodes are deployed in dense networks, then network capacity is improved, but device complexity increases due to multiple IP addresses and tunnels
Solution Approach 1:
The system segments anchor nodes into different groups based on their capabilities and roles. This segmentation allows devices to interact with simplified node representations within groups, reducing the complexity of managing multiple IP addresses and tunnels while maintaining the network capacity benefits of multiple anchor nodes
Solution Approach 2:
The patent introduces grouping information as an intermediary layer between devices and multiple anchor nodes. This intermediary structure simplifies device complexity by providing a standardized interface for interacting with multiple nodes, while the backend grouping mechanism manages the complexity of multiple IP addresses and tunnels
3Speed
If anchor nodes are selected based on proximity, then data path efficiency is improved, but handover frequency increases when devices move between dense anchor node locations
Solution Approach 1:
The system performs preliminary anchor node selection considering not only proximity but also load information and capability matching. This advance selection with multiple criteria reduces the likelihood of frequent handovers when devices move, while still maintaining data path efficiency by selecting appropriate anchor nodes before movement occurs
Solution Approach 2:
The system changes the selection parameters from simple proximity-based selection to multi-parameter selection including capability information, load information, and grouping data. This parameter expansion allows the system to balance data path efficiency with handover reduction by considering overall node suitability rather than just distance
Data Source
AI summary
Systems and/or methods may be used to select an anchor node. For example, a device may detect or more anchor nodes that may be available for the device to connect to. The device may determine whether to handover to one of the detected anchor nodes based on capability information including load information of the anchor nodes. The device may connect to a detected anchor node based on the capability information including the load information. The detected anchor nodes may be grouped and the device may select and connect to an anchor node based on the groupings. The device may also store a history including a route of the device and anchor nodes on the route and may use such information to determine whether to connect to detected anchor node. The device may further use proximity to content to determine whether to connect to a detected anchor node.