Serving Gateway Buffer Release via MME Paging Feedback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing method for releasing buffered data by a serving gateway is inefficient, as it either prematurely releases data if the timer is set too short or fails to release data in time if set too long, leading to resource wastage and reduced processing efficiency.
Innovation Solution
Implement a method where the MME re-initiates paging and restarts the paging timer if no response is received, and sends a notification message to the Serving GW with an update bearer request indicating no paging response, allowing the Serving GW to set a flag for non-responsive users and discard buffered data accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the timer in the Serving GW is set too short, then the buffered data can be released quickly, but the data may be released prematurely before the UE responds to paging, causing wrong release
Solution Approach 1:
The MME sends a notification message to the Serving GW based on whether the UE responds to paging. This feedback mechanism allows the Serving GW to accurately determine when to release buffered data, avoiding both premature release and delayed release. The notification message acts as feedback from the MME's paging response detection to the Serving GW's data release decision.
2Reliability
If the timer in the Serving GW is set too long, then the buffered data is retained longer ensuring no premature release, but system resources are wasted and processing efficiency is reduced
Solution Approach 1:
The notification message from the MME provides timely feedback to the Serving GW about UE paging response status. This enables the Serving GW to release buffered data as soon as it is safe to do so, optimizing the balance between reliability and productivity. The feedback eliminates the need for conservative long timer settings.
3Reliability
If the MME pages the UE multiple times before notifying the Serving GW, then the probability of reaching the UE increases, but unnecessary paging consumes air interface resources
Solution Approach 1:
The MME provides feedback to the Serving GW only when necessary - when the UE fails to respond to paging. This feedback mechanism allows the MME to stop paging early when successful, avoiding unnecessary air interface resource consumption while ensuring reliable data delivery.
Solution Approach 2:
When the UE successfully responds to paging, the buffered data is delivered and the paging process is discarded (stopped). The air interface resources are recovered by not continuing with further unnecessary paging attempts.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
A method for releasing buffered data of a Serving Gateway is disclosedâ–ˇ the Serving Gateway (Serving GW) buffers downlink data sent to a user and sends a data notification message to a Mobility Management Entity (MME); after receiving the data notification message, the MME initiates a paging to the user and sets a paging timer, if the paging timer expires and no paging response of the user is received, the MME sends a notification message to the Serving GW to inform the Serving GW that there is no paging response from the user; and after receiving the notification message, the Serving GW releases the buffered downlink data. With this method, the Serving GW can release buffered data in time without causing wrong release of the buffered data, so the system efficiency can be improved.