Subscription-Based Event Notification for Mobile Network Data Buffering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a need for techniques to reduce data buffering in mobile networks for delivering data to unavailable user equipment (UE), particularly for Internet of Things (IoT) devices with extended discontinuous reception (eDRX) cycles and Power Saving Modes (PSMs), as existing methods are inefficient in managing data delivery during these scenarios.
Innovation Solution
The implementation of subscription-based event notification techniques within 5G and 4G/LTE mobile networks, where an application server requests event subscriptions for UE events, and upon event occurrence, notifications are sent to trigger immediate data delivery or buffer data accordingly, utilizing entities like Network Exposure Function (NEF) and Service Capability Exposure Function (SCEF) to manage data delivery effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is buffered in the network for unavailable UEs, then data delivery reliability is improved, but data buffering requirements and network resource consumption increase
Solution Approach 1:
The system performs preliminary actions by establishing event subscriptions before data arrives. When a UE becomes available, the network has already prepared event notifications, eliminating the need to buffer data waiting for UE availability. The event subscription mechanism is set up in advance so that when data needs to be delivered, the system can immediately notify the UE through pre-configured event triggers.
Solution Approach 2:
The invention extracts the event notification function from the data buffering process. Instead of buffering data and waiting for UE availability, the system separates data delivery from availability checking by using independent event subscriptions. The event notification system operates independently to trigger data delivery only when the UE is actually available, eliminating unnecessary buffering.
2Adaptability or versatility
If traditional data delivery methods are used for IoT devices with eDRX and PSM, then device compatibility is maintained, but data delivery latency increases
Solution Approach 1:
The system dynamically adapts to IoT device states by using event subscriptions that can detect when UEs transition between available and unavailable states. The event notification mechanism adjusts to the dynamic nature of eDRX and PSM cycles, triggering data delivery precisely when devices wake up and become available, rather than using fixed timing or continuous monitoring approaches.
Solution Approach 2:
The event subscription mechanism provides feedback about UE availability status to the network. When a UE transitions to an available state, the event notification system detects this change and feeds back the availability information, enabling the network to immediately deliver data without waiting or guessing when the device might be available. This feedback loop eliminates the latency inherent in traditional polling or fixed-schedule approaches.
3Loss of time
If continuous monitoring of UE availability is implemented, then data delivery timing is improved, but network signaling overhead and energy consumption increase
Solution Approach 1:
Instead of continuous monitoring, the system uses periodic event-triggered actions. Event subscriptions are established that only activate when specific conditions change (UE availability state transitions). This periodic, event-driven approach replaces continuous monitoring, reducing signaling overhead while maintaining accurate detection of when data delivery should occur.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
Subscription-based, user equipment (UE) event notification techniques for use in a mobile network are described. In one illustrative example, an event subscription request from an application server may be received at a network exposure function (NEF) entity of a 5G mobile network. The event subscription request may include a list of one or more subscribed events for a UE, which may include a UE attach event and/or a UE detach event. A context which indicates the one or more subscribed events may be created for the UE. Sometime during network operation, an indication of an occurrence of an event associated with the UE is received. The indication is received from a policy and charging function (PCF) entity when the UE is configured for IP data delivery, or from an access and mobility management function (AMF) entity when the UE is configured for non-IP data delivery (NIDD).