IAB Node MEC Configuration for Low Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face challenges in providing multi-access edge computing (MEC) functionality within integrated access and backhaul (IAB) networks, particularly in ultradense mmWave deployments, where fiber backhaul is costly and difficult to implement, leading to latency and reliability issues due to multi-hop routing.
Innovation Solution
Implementing IAB nodes with MEC functionality, where each node acts as both an access point for user equipment and a wireless backhaul link to other nodes or a donor node, utilizing a backhaul adaptation protocol for efficient routing and data transfer, and locating MEC functionality at IAB nodes instead of the core network to reduce latency and increase reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If fiber backhaul is used to connect base stations in ultradense mmWave deployments, then communication reliability is improved, but deployment cost and complexity increase significantly
Solution Approach 1:
The patent replaces the mechanical/fiber-based backhaul infrastructure with a wireless backhaul system using IAB nodes. Instead of physically laying fiber cables between base stations, the system uses wireless links where IAB nodes relay traffic between donor base stations and user equipment, thereby eliminating the need for complex fiber deployment while maintaining communication reliability
Solution Approach 2:
The IAB node is designed as a multi-functional device that simultaneously serves as both an access point for user equipment and a backhaul relay for other nodes. This universal functionality allows a single node to perform multiple roles in the network hierarchy, simplifying the overall system architecture compared to dedicated fiber-based solutions
2Adaptability or versatility
If multi-hop routing is used in wireless backhaul IAB networks, then deployment flexibility is improved, but latency increases
Solution Approach 1:
The patent segments the network into hierarchical levels with donor base stations at the top and IAB nodes forming intermediate layers. This segmentation allows traffic to be routed through multiple hops for deployment flexibility while enabling the system to optimize paths to minimize latency by selecting appropriate routing segments based on network conditions
Solution Approach 2:
The system dynamically selects optimal routing paths through the IAB network based on real-time network conditions, available resources, and latency requirements. This dynamic routing capability allows the system to adapt to changing conditions and select paths that balance flexibility with latency performance
3Ease of operation
If MEC functionality is located at the core network, then network management simplicity is improved, but communication latency increases
Solution Approach 1:
The patent implements MEC functionality locally at IAB nodes rather than centralizing it at the core network. Each IAB node hosts MEC functions that are geographically and functionally closer to user equipment, enabling low-latency processing and data access while maintaining simplified network management through the standardized IAB node architecture
Solution Approach 2:
The system distributes MEC functionality across multiple dimensions of the network hierarchy, placing it at IAB nodes at various levels between the core network and user equipment. This dimensional distribution reduces the physical and topological distance for data transmission while preserving manageable network architecture through standardized interfaces
Data Source
AI summary
Systems and methods are disclosed herein for using integrated access and backhaul (IAB) nodes configured to provide multi-access edge computing (MEC) functionality. An IAB node may include a MEC functionality that includes an instance of an application configured for MEC. A UE using the application connects to the network through an access link with the IAB node and establishes a PDU session for traffic of the application with a core network (CN). The CN may determine that the traffic corresponds to the application, and that an instance of the application is present on the IAB node. Accordingly, the CN may instruct the IAB donor to instantiate a remote packet data convergence protocol (PDCP) layer and, in some cases, a remote service data application (SDAP) layer that are configured to route the traffic from the UE for the application to the instance of the application on the IAB node.


