Mobility Management Node Direct T5 Interface Caching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems require frequent HSS/HLR queries for T5 communications in mobility management, leading to inefficient handling of M2M device mobility and increased communication overhead, especially in 3GPP Release 12 scenarios.
Innovation Solution
Implementing direct communication methods between mobility management nodes and MTC-IWF nodes through state-full and semi-state-full communication management approaches, where the MME and MTC-IWF maintain address information to facilitate direct T5 interface usage, reducing the need for HSS/HLR queries by maintaining a persistent connection and using Combined MTC Attach and TAU procedures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If frequent HSS/HLR queries are performed for T5 communications, then communication routing information can be obtained, but communication overhead increases and system efficiency decreases
Solution Approach 1:
The mobility management node performs HSS/HLR queries in advance to obtain T5 communication routing information, and caches this information locally. This preliminary action allows the node to use cached routing information for subsequent communications without repeated queries, reducing communication overhead while maintaining routing accuracy.
Solution Approach 2:
The patent introduces a caching mechanism as an intermediary between the mobility management node and the HSS/HLR. This cache stores routing information locally, acting as a mediator that reduces the need for direct HSS/HLR queries while ensuring accurate routing information is available for T5 communications.
2Productivity
If direct T5 communications are established between mobility management node and MTC-IWF node, then communication overhead is reduced, but device mobility handling becomes more complex
Solution Approach 1:
The mobility management node maintains its own cache of T5 communication routing information and performs self-service by using this cached information for direct communications with MTC-IWF nodes. This self-service approach enables efficient direct T5 communications while the node independently manages its own mobility routing without requiring complex centralized coordination.
3Productivity
If HSS/HLR queries are minimized through caching, then system resource usage is optimized, but information freshness may be compromised
Solution Approach 1:
The mobility management node periodically updates its cached T5 communication routing information from the HSS/HLR. This periodic refresh mechanism ensures that cached information remains fresh and accurate while minimizing the frequency of HSS/HLR queries, thus optimizing system resource usage without compromising information freshness.
Data Source
AI summary
Example embodiments presented herein are directed towards providing direct communications between a mobility management node (e.g., SGSN, S4-SGSN or MME) and an MTC-IWF node via a T5 interface. With the use of the direct communications unnecessary queries to a HSS or HLR may be avoided. The direct communications are established by the mobility management node and the MTC-IWF node saving identifying information of the other node.