User Plane Event Handling for Low-Latency Mobile Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile networks face challenges in dynamically and timely responding to network events due to the separation of control and user planes, leading to increased latency and reduced reliability, especially in ultra-reliable low latency communications (uRLLC) scenarios, which are critical for applications like autonomous driving and holographic communications.
Innovation Solution
A CP entity generates and sends a list of network events and corresponding actions to a UP entity, allowing the UP entity to perform autonomous and real-time actions, and also provides a list of NF entities for event notifications, enhancing the UP's ability to respond dynamically to network events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the control plane and user plane are separated in 5G networks, then network flexibility and scalability are improved, but response latency to network events increases and reliability decreases
Solution Approach 1:
The patent applies preliminary action by pre-configuring event-action rules at the UPF during PDU session establishment. The CP entity provides a list of network events and corresponding actions to the UPF in advance, enabling the user plane to autonomously execute predefined actions when events occur, thereby reducing response latency while maintaining control plane flexibility
Solution Approach 2:
The patent implements self-service by enabling the UPF to autonomously monitor network events and execute corresponding actions without requiring real-time control plane intervention. The UPF independently manages event responses using pre-provided rules, eliminating the latency associated with control-plane-mediated responses while preserving network flexibility through configurable event-action mappings
2Adaptability or versatility
If the control plane and user plane are separated in 5G networks, then network scalability is improved, but event handling reliability decreases
Solution Approach 1:
The patent applies preliminary action by pre-establishing event-action rule mappings at the UPF during session setup. This ensures that when network events occur, the UPF can immediately execute the predetermined reliable actions without waiting for control plane decisions, thereby improving event handling reliability while maintaining scalability
Solution Approach 2:
The patent implements feedback mechanisms where the UPF monitors network events and executes actions based on real-time conditions, with the control plane receiving notifications about event handling. This feedback loop ensures reliable event processing while allowing the control plane to maintain scalability through asynchronous operation
3Speed
If real-time event monitoring is implemented at the user plane, then response speed is improved, but processing complexity increases
Solution Approach 1:
The patent applies preliminary action by providing the UPF with pre-configured event-action rules during PDU session establishment. This eliminates the need for complex real-time decision-making logic at the UPF, as it only needs to match incoming events against predefined rules and execute corresponding actions, thereby achieving fast response without excessive processing complexity
Solution Approach 2:
The patent implements self-service by enabling the UPF to autonomously handle events using simple pattern matching and rule execution mechanisms. The UPF independently monitors events and executes actions without requiring complex processing or control plane involvement, achieving high response speed with minimal processing complexity through autonomous operation
Data Source
AI summary
Related to telecommunications, a method and system include a control-plane (CP) entity and a user-plane (UP) entity. The CP entity is configured to generate a first list and a second list, and send the first list and the second list to the UP entity. The first list indicates a plurality of network events and a plurality of corresponding actions that the UP entity is allowed to perform. The second list indicates a plurality of network functions for notifying the UP entity of the plurality of network events. The UP entity is configured to send one or more subscription requests for subscribing to one or more of the plurality of network events based on the first list and the second list. When receiving a network event trigger, the UP entity may be configured to take a corresponding action in accordance with the first list.