Mobility Management Entity Tracking Area Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face challenges in reducing latency during serving gateway selection and tracking area identity list generation, leading to inefficient resource allocation and increased latency in paging and tracking area updates.
Innovation Solution
Implementing a mobility management entity that performs DNS queries to store and select serving gateways based on tracking area identities, and generates user equipment's tracking area identity lists considering paging load, tracking area update load, and mobility characteristics, thereby reducing unnecessary resource usage and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If traditional serving gateway selection methods are used, then network coverage is maintained, but latency in gateway selection and tracking area identity list generation increases
Solution Approach 1:
The system pre-establishes mapping relationships between tracking area identities and serving gateway addresses before they are needed. When a mobile device enters a tracking area, the gateway address is already available in the mobility management entity, eliminating the need for real-time DNS queries and reducing selection latency
Solution Approach 2:
The mobility management entity pre-generates tracking area identity lists for mobile devices based on their mobility characteristics and current location. This eliminates the need for real-time list generation when the device needs to move, reducing signaling overhead and latency
2Reliability
If comprehensive tracking area identity lists are provided to user equipment, then mobility support is improved, but unnecessary paging and tracking area updates increase
Solution Approach 1:
The system provides different tracking area identity lists to different mobile devices based on their specific mobility characteristics, current location, and service requirements. Instead of using a uniform comprehensive list for all devices, each device receives a customized list that is optimally sized for its needs, reducing unnecessary paging and tracking area updates
Solution Approach 2:
The tracking area identity lists are dynamically adjusted based on mobile device behavior patterns, mobility speed, and current network conditions. The system can modify the list size and content in real-time to balance mobility support with reduction of unnecessary signaling
3Measurement precision
If real-time DNS queries are performed for each tracking area, then accurate serving gateway information is obtained, but processing time and network overhead increase
Solution Approach 1:
The system performs DNS queries and resolves gateway addresses in advance, before they are needed for mobile device service. The resolved gateway addresses are cached in the mobility management entity, so when a device enters a tracking area, the pre-resolved address can be used immediately without performing a new DNS query
Solution Approach 2:
Instead of performing original DNS queries for each tracking area entry, the system uses cached copies of previously resolved gateway address information. These copies are stored and reused whenever the same tracking area is encountered, dramatically reducing processing time while maintaining accuracy
Data Source
AI summary
Some embodiments provide methods for selecting tracking areas, including: receiving a plurality of messages from a plurality of base transceiver stations, each message including a list of tracking areas handled by the base transceiver station from which the message is received; performing domain name system queries for the tracking areas to retrieve information identifying serving gateways serving the tracking areas; based on the information identifying serving gateways, storing, in a local memory, a list of tracking area identities handled by each identified serving gateway; receiving a message from user equipment indicating a first tracking area; selecting at least one tracking area handled by a serving gateway serving the first tracking area based on the list of tracking areas handled by each identified serving gateway stored in the memory; and sending a tracking area identity list to the user equipment based on the selected at least one tracking area.