17593291. SYSTEMS AND METHODS FOR IAB MEC simplified abstract (Apple Inc.)

SYSTEMS AND METHODS FOR IAB MEC

Organization Name

Apple Inc.

Inventor(s)

Sarma V. Vangala of Cupertino CA (US)

Sudeep Manithara Vamanan of Munich, Bavaria-Bayern (CN)

Fangli Xu of Beijing (CN)

Haijing Hu of Cupertino CA (US)

Krisztian Kiss of Cupertino CA (US)

Mona Agnel of Greater London (GB)

Naveen Kumar R Palle Venkata of San Diego CA (US)

Ralf Rossbach of Neubiberg, Bavaria-Bayern (DE)

Sethuraman Gurumoorthy of Cupertino CA (US)

Yuqin Chen of Beijing (CN)

Zhibin Wu of Cupertino CA (US)

SYSTEMS AND METHODS FOR IAB MEC - A simplified explanation of the abstract

This abstract first appeared for US patent application 17593291 titled 'SYSTEMS AND METHODS FOR IAB MEC

Simplified Explanation

The patent application describes systems and methods for using integrated access and backhaul (IAB) nodes to provide multi-access edge computing (MEC) functionality. The IAB node includes a distributed unit (DU) with a local application instance of a MEC-enabled application. The DU communicates with a first user equipment (UE) connected to the IAB node. The mobile termination functionality (MT) of the IAB node uses a packet data convergence protocol (PDCP) layer to transport data of the local application instance between the MT and an IAB donor. The data of the local application instance is also transported between the UE and the IAB node using various methods, including a second PDCP layer at the DU and optionally the use of a service data adaptation protocol (SDAP) layer at each of the DU and the MT, and/or via sidelink.

• The patent application describes a system that integrates access and backhaul nodes to provide multi-access edge computing functionality.
• The system includes a distributed unit with a local application instance of a MEC-enabled application.
• The local application instance communicates with a user equipment connected to the node.
• The mobile termination functionality of the node uses a packet data convergence protocol layer to transport data between the node and an IAB donor.
• Data of the local application instance is transported between the user equipment and the node using various methods, including a second PDCP layer at the distributed unit and optionally the use of a service data adaptation protocol layer at each of the distributed unit and the mobile termination functionality, and/or via sidelink.

Potential applications of this technology:

• Improved communication and data transfer between user equipment and integrated access and backhaul nodes.
• Enhanced multi-access edge computing functionality for local application instances.
• Efficient transport of data between mobile termination functionality and IAB donors.

Problems solved by this technology:

• Integration of access and backhaul nodes for improved communication and data transfer.
• Efficient transport of data between different components of the system.
• Enhanced multi-access edge computing functionality for local application instances.

Benefits of this technology:

• Improved performance and efficiency in communication and data transfer.
• Enhanced capabilities for multi-access edge computing.
• Seamless integration of access and backhaul nodes for improved functionality.

Original Abstract Submitted

Systems and methods for using integrated access and backhaul (IAB) nodes configured to provide multi-access edge computing (MEC) functionality are disclosed herein. An TAB node includes a distributed unit (DU) having a local application instance of a MEC-enabled application. The local application instance is configured for communication with a first user equipment (UE) connected to the TAB node. A mobile termination functionality (MT) of the TAB node uses a packet data convergence protocol (PDCP) layer to transport data of the local application instance between the MT and an IAB donor. Further, data of the local application instance is transported between the UE and the TAB node via one of a variety of methods, including the use of a second PDCP layer at the DU (and optionally the use of service data adaptation protocol (SDAP) layers at each of the DU and the MT), and/or via sidelink.