Serving Gateway Paging Trigger Logic for eMPS Priority
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing service implementation methods in 3GPP networks fail to ensure users with Enhanced Multimedia Priority Service (eMPS) capabilities have priority access to network resources, especially during network congestion, leading to pressure on the air interface and inadequate prioritization.
Innovation Solution
A service implementation method where a serving gateway and mobility management element dynamically determine whether to send paging trigger messages based on the priority of data packets, skipping unnecessary messages to prevent air interface pressure and ensure eMPS users are prioritized.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If the serving gateway sends a paging trigger message for every downlink data packet received, then the terminal device can be promptly notified of data arrival, but the air interface experiences excessive pressure and network resources are wasted
Solution Approach 1:
The serving gateway implements periodic triggering of paging messages through a timer mechanism. Instead of sending a paging trigger for every downlink data packet, the gateway waits for a predetermined time interval before triggering the next paging message, thereby reducing air interface pressure while still ensuring timely notification of the terminal device
Solution Approach 2:
The serving gateway determines in advance whether to trigger a paging message based on the eMPS capability of the terminal device and the priority of the data packet. For high-priority eMPS users, the gateway proactively triggers paging messages even during network congestion, ensuring these users receive timely notification before the periodic timer expires
2Reliability
If the mobility management element pages the terminal device for every paging trigger message received, then the terminal device is notified of all data arrivals, but the air interface is overwhelmed during network congestion
Solution Approach 1:
The mobility management element implements periodic paging through a timer mechanism. When a paging trigger message is received, the element starts a timer and only triggers the next paging message after the timer expires, reducing air interface pressure by preventing continuous paging while maintaining reliable notification for eMPS users
Solution Approach 2:
The mobility management element applies different paging behaviors based on the eMPS capability of the terminal device. For eMPS-capable users, the element ensures paging messages are sent with higher reliability and lower delay, while for non-eMPS users, it applies stricter rate limiting, thereby protecting the air interface from overload
3Object-affected harmful factors
If the serving gateway skips sending paging trigger messages during network congestion, then air interface pressure is reduced, but eMPS users lose priority access to network resources
Solution Approach 1:
The serving gateway applies different paging strategies based on the eMPS capability and data packet priority. For eMPS-capable users with high-priority data packets, the gateway ensures paging trigger messages are sent even during network congestion, while for non-eMPS users or low-priority traffic, it implements rate limiting, thereby guaranteeing priority service for eMPS users while protecting the air interface
Solution Approach 2:
The serving gateway determines in advance whether a terminal device has eMPS capability and configures appropriate paging behavior. When high-priority data packets arrive for eMPS users, the gateway proactively triggers paging messages without waiting for the periodic timer, ensuring these users maintain priority access even during network congestion
4Object-affected harmful factors
If the mobility management element skips sending paging messages when a timer is running, then air interface pressure is reduced, but eMPS users with high-priority data packets experience delayed notification
Solution Approach 1:
The mobility management element applies different timer behaviors based on eMPS capability and data priority. For eMPS-capable users with high-priority data packets, the element either skips the timer waiting and sends the paging message immediately, or extends the timer duration, thereby ensuring these users experience minimal delay while other users benefit from rate limiting
Solution Approach 2:
The mobility management element determines in advance whether a terminal device has eMPS capability and configures appropriate timer behavior. When high-priority data packets arrive for eMPS users, the element proactively adjusts the timer configuration to ensure timely paging notification, preventing delay while maintaining air interface protection for other traffic
Data Source
AI summary
A service implementation method, apparatus, and system are disclosed. The service implementation method includes: receiving, by a serving gateway, a data packet of a terminal device sent by a packet data network gateway; if the data packet is a data packet with a serving priority and the serving gateway has sent a paging trigger message with a serving priority to a mobility management element, skipping, by the serving gateway, sending a paging trigger message to the mobility management element; or if the data packet is a data packet with a serving priority and the serving gateway has sent no paging trigger message with a serving priority to a mobility management element, sending, by the serving gateway, a paging trigger message to the mobility management element; wherein the paging trigger message is used to enable the mobility management element to page the terminal device.