RAN Edge Network Slicing for Low-Latency Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G wireless telecommunications networks, low-latency services such as V2X and edge computing face challenges in meeting service level agreements (SLAs) due to application servers being remote from the radio interface, leading to potential compliance issues with Quality of Service (QoS) requirements.
Innovation Solution
Configuring radio access network (RAN) nodes with intelligence to serve low-latency traffic locally, mapping applications to low-latency radio bearers, and moving context information between RAN sites to ensure continuous compliance with SLAs during handovers, thereby offloading low-latency traffic from core networks and conserving resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If application servers are placed remote from the radio interface to support diverse use cases, then network versatility is improved, but latency increases and QoS requirements cannot be met
Solution Approach 1:
The patent segments the network into multiple network slices, each dedicated to specific service types with different QoS requirements. Low-latency services are routed through dedicated paths with local edge computing resources, while other services use remote application servers. This segmentation allows the network to simultaneously support both low-latency applications and diverse use cases without compromising latency requirements.
Solution Approach 2:
The patent introduces network slicing as an intermediary mechanism that mediates between remote application servers and radio interface requirements. The network slice acts as a dedicated virtual network that provides low-latency paths and local edge computing capabilities, enabling applications to meet QoS requirements while maintaining the benefits of remote server deployment and network versatility.
2Productivity
If traffic is handled through core network, then network resource utilization is improved, but service quality deteriorates for low-latency applications
Solution Approach 1:
The patent implements local quality by deploying edge computing resources and low-latency service handling at the radio access network edge, close to user equipment. This allows low-latency applications to be serviced locally with guaranteed QoS, while other traffic continues to use core network resources efficiently. The differentiated handling ensures service quality for time-sensitive applications without compromising overall network resource utilization.
Solution Approach 2:
The patent introduces dynamic traffic routing that adapts based on application requirements. The system dynamically directs low-latency traffic through dedicated network slices with local edge computing, while routing other traffic through standard core network paths. This dynamic approach optimizes both service quality for critical applications and overall network resource utilization across different traffic types.
3Stability of the object's composition
If context information is moved between RAN sites during handover, then service continuity is improved, but network complexity increases
Solution Approach 1:
The patent implements preliminary action by pre-configuring and caching context information at multiple RAN sites before handover occurs. When a user equipment moves between coverage areas, the target RAN site already has the necessary context information ready, enabling seamless service continuity without complex real-time information exchange during the handover event itself.
Solution Approach 2:
The patent uses copying by creating and distributing copies of context information to multiple RAN sites in advance. Instead of complex real-time synchronization during handover, the system maintains simplified copies of necessary context data at potential target sites, reducing the complexity of inter-site communication while ensuring service continuity through available local copies.
Data Source
AI summary
A radio access network (RAN) node can receive, from a user equipment (UE), a request to establish a session associated with a low-latency service level agreement (SLA). The session can be mapped to a radio bearer associated with a network slice configured to support the low-latency SLA, wherein the network slice can include a RAN portion and a core network portion that are co-located at a RAN edge to support the low-latency SLA. The RAN node can provide information related to the radio bearer to a distributed unit (DU) associated with the RAN portion of the network slice and route traffic associated with the session through the network slice configured to support the low-latency SLA via the radio bearer mapped to the session. As such, the session can have a context maintained in the RAN portion and the core network portion of the network slice.