Mobile Gateway Error Handling via IP Address Lookup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large mobile networks, handling error indication packets with unknown tunnel endpoint identifiers (TEIDs) is time-consuming and resource-intensive, requiring linear scans of subscriber records, which delays data delivery and impacts user experience.
Innovation Solution
Including additional information, such as the Internet Protocol (IP) address, in error indication packets allows service nodes to perform a more efficient lookup using hash tables, reducing the number of operations required to identify subscriber records.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If service nodes perform linear scans of subscriber records to identify unknown TEIDs, then error handling can be performed, but processing time and resource consumption increase significantly
Solution Approach 1:
The patent introduces an intermediary mechanism where the downstream mobile gateway includes the destination IP address in the error indication packet. This IP address serves as a mediator that enables the upstream mobile gateway to perform efficient hash table lookups instead of linear scans, thereby resolving the contradiction between reliable error handling and processing time.
Solution Approach 2:
The patent changes the parameter used for lookup by adding the destination IP address to the error indication packet. This parameter change enables the system to transition from linear scanning (inefficient) to hash table-based lookup (efficient), significantly reducing processing time while maintaining error handling reliability.
2Reliability
If service nodes perform linear scans of subscriber records to identify unknown TEIDs, then error handling can be performed, but processor cycles and memory resources increase significantly
Solution Approach 1:
The destination IP address acts as an intermediary that enables efficient resource utilization. By including this IP address in error indication packets, the system can leverage existing hash table structures in the upstream mobile gateway, avoiding the need for resource-intensive linear scans across all subscriber records.
Solution Approach 2:
The patent replaces the mechanical linear scanning process with a more efficient hash table lookup mechanism. This substitution eliminates the need to sequentially check numerous subscriber records, thereby reducing processor cycle consumption and memory resource usage while maintaining comprehensive error handling.
3Reliability
If service nodes perform linear scans of subscriber records to identify unknown TEIDs, then error handling can be performed, but data delivery speed decreases
Solution Approach 1:
The destination IP address in the error indication packet serves as a fast lookup key. This intermediary enables the upstream mobile gateway to quickly identify the correct subscriber record through hash table search, thereby reducing the time to resolve errors and restore data delivery without compromising handling reliability.
Solution Approach 2:
By changing the lookup parameter from TEID (requiring linear scan) to destination IP address (enabling hash table lookup), the system significantly accelerates error resolution speed. This parameter change allows rapid identification of affected subscriber records, thereby speeding up data delivery while maintaining reliable error handling.
Data Source
AI summary
In general, techniques are described for handling errors in subscriber session management within mobile networks. A downstream mobile gateway comprising a forwarding unit and a service unit may implement the techniques. The forwarding unit receives a packet that includes a destination address for a subscriber and a tunnel endpoint identifier (TEID). The service unit determines whether the TEID is associated with one of a number of subscriber records that store session data for current sessions associated with subscriber devices to communicate with the mobile network. In response to determining that the TEID is not associated with one of the subscriber records, the service unit generates a message that includes the TEID and the destination address and indicates that the downstream mobile gateway has determined that the TEID is not associated with one of the subscriber records. The forwarding unit then sends the message to the upstream mobile gateway.


