Techniques for application and accelerator communication for distributed units

Abstract

Methods, systems, and devices for wireless communication are described. Applications and accelerators associated with distributed units (DUs) may be configured to identify contextual information, the context information includes a first identifier associated with the accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a radio unit associated with the DU, or any combination thereof; and exchanging messages with each other based on the identified contextual information.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 18 / 349,108, filed by RADULESCU et al. on July 7, 2023, entitled “TECHNIQUES FOR APPLICATION AND ACCELERTOR COMMUNICATIONS OF A DISTRIBUTED UNIT,” which U.S. patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 388,546, filed by RADULESCU et al. on July 12, 2022, entitled “TECHNIQUES FOR APPLICATION AND ACCELERTOR COMMUNICATIONS OF A DISTRIBUTED UNIT,” which are assigned to the assignee of this application and are expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including techniques for distributed unit (DU) applications and accelerator communications. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may use techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for a communication device, which may be referred to as a user equipment (UE).

[0005] In the context of an open radio access network (O-RAN) architecture, different functions of a base station or network entity may be physically and / or logically divided across multiple devices or components. For example, an O-RAN network entity may include a radio unit (RU) and a distributed unit (DU), wherein the RU performs wireless communications with other devices (e.g., UEs) via a physical layer, and wherein components of the DU perform higher layer functions to support communications performed by the RU. The physical and logical division of the O-RAN network entity may result in information being exchanged between components of the O-RAN network entity and between the O-RAN network entity and other wireless devices such as UEs. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting technology for communication between applications and accelerators of distributed units (DUs). In general, aspects of the present disclosure relate to signaling for efficient communication of data models (DMs) between corresponding devices by supporting the exchange of context information between applications and accelerators of DUs, wherein these DMs support communication between accelerators and radio units (RUs) associated with DUs. For example, an accelerator may provide context information to an application, which may enable the application to retrieve configuration information associated with a DM hosted at an application, RU, or both and provide the configuration information to the accelerator. In contrast, an application may provide context information to an accelerator, which may enable the accelerator to retrieve configuration information associated with a DM hosted at an accelerator and provide the configuration information to the application. In some examples, aspects of the present disclosure may enable a management plane interface (M plane) between an RU of an open radio access network (O-RAN) entity and a DU to terminate at an application of the DU, rather than at an accelerator of the DU.

[0007] A method for wireless communication at an application executable by a DU of a radio access network (RAN) is described. The method may include: identifying context information, the context information including a first identifier associated with an accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and exchanging messages with the accelerator based on the identified context information.

[0008] An apparatus for wireless communication at an application executable by a DU of a RAN is described. The apparatus may include: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory. The instructions may be executable by the at least one processor to cause the apparatus to: identify context information, the context information including a first identifier associated with an accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and exchange messages with the accelerator based on the identified context information.

[0009] Another apparatus for wireless communication at an application executable by a DU of a RAN is described. The apparatus may include: a component for identifying context information, the context information including a first identifier associated with an accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and a component for exchanging messages with the accelerator based on the identified context information.

[0010] A non-transitory computer-readable medium storing code for wireless communication at an application executable by a DU of a RAN is described. The code may include instructions executable by a processor to: identify context information, the context information including a first identifier associated with an accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and exchange messages with the accelerator based on the identified context information.

[0011] In some examples of the methods, devices, and non-transitory computer-readable media described herein, exchanging the message may include operations, features, components, or instructions for: providing the context information to the accelerator; and obtaining, from the accelerator, information associated with the DM hosted at the accelerator based on providing the context information.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, exchanging the message may include operations, features, components, or instructions for: obtaining the context information from the accelerator; and providing to the accelerator information associated with a DM for communication between the accelerator and the RU associated with the DU based on obtaining the context information.

[0013] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: providing a request for the information to the RU via an interface between the application and the RU; and obtaining the information from the RU via the interface and in response to the request. In some examples, the information obtained from the RU is further conveyed to the accelerator via a second interface between the application and the accelerator. In some of these examples, the accelerator uses the information to provide a DM hosted by the accelerator.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining a first message from the accelerator based on providing the information, the first message indicating a result of a validation procedure associated with the information.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first message indicates a failure of the verification procedure, and the methods, apparatus, and non-transitory computer-readable media may include further operations, features, components, or instructions for: providing a second message to the accelerator in response to the failure, the second message instructing the accelerator to transmit additional information about the failure associated with the context information; and obtaining a third message from the accelerator in response to the second message, the third message including the additional information associated with the context information for the communication between the accelerator and the RU.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, second additional information for a second DM is obtained based on the additional information, and a fourth message is provided to the accelerator, the fourth message conveying the second additional information.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first message indicates a failure of the verification procedure, and the methods, apparatus, and non-transitory computer-readable media may include further operations, features, components, or instructions for: providing a second message to the accelerator based on the failure, the second message identifying additional information for a second DM, wherein the additional information includes a modified version of the information.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first message indicates a failure of the verification procedure, and the methods, apparatus, and non-transitory computer-readable media may include further operations, features, components, or instructions for: obtaining an indication of additional information for a second DM from the accelerator based on the failure, the additional information being used to generate a modified version of the information.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the profile instance associated with the accelerator can be associated with a carrier, a physical context, a baseband context associated with the accelerator, or any combination thereof.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the context information also includes an indication of applicable antenna panels associated with the one or more transmit-receive points.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first identifier corresponds to at least two configuration file instances in a set of a plurality of configuration file instances.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the context information includes a first set of multiple identifiers associated with a set of multiple profile instances associated with the accelerator, a second set of multiple identifiers associated with a set of multiple RUs that include the RU, a third set of multiple identifiers associated with a set of multiple applications that include the application, or any combination thereof.

[0023] A method for wireless communication at an accelerator associated with a DU of a RAN is described. The method may include: identifying context information, the context information including a first identifier associated with the accelerator, a second identifier associated with an application of the DU, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and exchanging messages with the application based on the identified context information.

[0024] An apparatus for wireless communication at an accelerator associated with a DU of a RAN is described. The apparatus may include: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory. The instructions may be executable by the at least one processor to cause the apparatus to: identify context information, the context information including a first identifier associated with the accelerator, a second identifier associated with an application of the DU, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and exchange messages with the application based on the identified context information.

[0025] Another apparatus for wireless communication at an accelerator associated with a DU of a RAN is described. The apparatus may include: a component for identifying context information, the context information including a first identifier associated with the accelerator, a second identifier associated with an application of the DU, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and a component for exchanging messages with the application based on the identified context information.

[0026] A non-transitory computer-readable medium storing code for wireless communication at an accelerator associated with a DU of a RAN is described. The code may include instructions executable by a processor to: identify context information, the context information including a first identifier associated with the accelerator, a second identifier associated with an application of the DU, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and exchange messages with the application based on the identified context information.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, exchanging the message may include operations, features, components, or instructions for: obtaining the context information from the application; and providing to the application information associated with the DM hosted at the accelerator based on obtaining the context information.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, exchanging the message may include operations, features, components, or instructions for: providing the context information to the application; and obtaining from the application information associated with the DM used for communication between the accelerator and the RU associated with the DU based on providing the context information.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for providing a first message to the application based on obtaining the information, the first message indicating a result of a validation procedure associated with the information.

[0030] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the first message indicates a failure of the verification procedure, and the methods, devices, and non-transitory computer-readable media may include further operations, features, components, or instructions for: obtaining a second message from the application in response to the failure, the second message instructing the accelerator to transmit additional information about the failure associated with the context information; and providing a third message to the application in response to the second message, the third message including the additional information associated with the context information used for communication between the accelerator and the RU.

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a fourth message from the application in response to the failure, the fourth message including second additional information for the second DM.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a first message from the application, the first message including information related to the second DM; determining a failure of a verification procedure associated with the information; and providing a second message to the application based on the failure, the second message indicating third information, wherein the third information may be associated with a modified version of the information.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the profile instance associated with the accelerator can be associated with a carrier, a physical context, a baseband context associated with the accelerator, or any combination thereof.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the context information also includes an indication of applicable antenna panels associated with one or more transmit-receive points associated with the DU.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first identifier corresponds to at least two configuration file instances in a set of a plurality of configuration file instances.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the context information includes a first set of multiple identifiers associated with a set of multiple profile instances associated with the accelerator, a second set of multiple identifiers associated with a set of multiple RUs that include the RU, a third set of multiple identifiers associated with a set of multiple applications that include the application, or any combination thereof.

[0037] A method for wireless communication at an application executable by a DU of a RAN is described. The method may include: communicating a first message with an accelerator of the DU, the first message including context information associated with a DM hosted at the accelerator or the application; and communicating a second message with the accelerator based on the context information, the second message including configuration information associated with the DM.

[0038] An apparatus for wireless communication at an application executable by a DU of a RAN is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: communicate a first message with an accelerator of the DU, the first message including context information associated with a DM hosted at the accelerator or the application; and communicate a second message with the accelerator based on the context information, the second message including configuration information associated with the DM.

[0039] Another apparatus for wireless communication at an application executable by a DU of a RAN is described. The apparatus may include: a component for communicating a first message with an accelerator of the DU, the first message including context information associated with a DM hosted at the accelerator or the application; and a component for communicating a second message with the accelerator based on the context information, the second message including configuration information associated with the DM.

[0040] A non-transitory computer-readable medium storing code for wireless communication at an application executable by a DU of a RAN is described. The code may include instructions executable by a processor to: communicate a first message with an accelerator of the DU, the first message including context information associated with a DM hosted at the accelerator or the application; and communicate a second message with the accelerator based on the context information, the second message including configuration information associated with the DM.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the context information includes a first identifier associated with the accelerator, a second identifier associated with the RU, a third identifier associated with a profile instance associated with the accelerator, or a fourth identifier associated with the application.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the accelerator may be associated with a set of multiple profile instances including the profile instance, and the first identifier corresponds to at least two profile instances in the set of multiple profile instances.

[0043] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the context information includes a set of multiple identifiers associated with a set of multiple profile instances associated with the accelerator, a set of multiple identifiers associated with a set of multiple RUs including the RU, a set of multiple identifiers associated with a set of multiple applications including the application, or any combination thereof, and the configuration information may be associated with the set of multiple profile instances, the set of multiple RUs, the set of multiple applications, or any combination thereof.

[0044] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining a third message from the accelerator based on providing the second message, the third message indicating a result of a validation procedure associated with the configuration information.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the third message indicates a failure of the verification procedure, and the methods, apparatus, and non-transitory computer-readable media may include further operations, features, components, or instructions for: providing a fourth message to the accelerator in response to the failure, the fourth message instructing the accelerator to modify the context information; obtaining a fifth message from the accelerator in response to the fourth message, the fifth message including additional context information for the communication between the accelerator and the RU; obtaining additional configuration information for the second DM based on the additional context information; and providing a sixth message to the accelerator, the sixth message identifying the additional configuration information.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the third message indicates a failure of the verification procedure, and the methods, apparatus, and non-transitory computer-readable media may include further operations, features, components, or instructions for: providing a fourth message to the accelerator based on the failure, the fourth message identifying additional configuration information for the second DM, wherein the additional configuration information includes a modified version of the configuration information.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the third message indicates a failure of the verification procedure, and the methods, apparatus, and non-transitory computer-readable media may include further operations, features, components, or instructions for: obtaining an indication of additional configuration information for a second DM from the accelerator based on the failure, wherein the additional configuration information includes a modified version of the configuration information.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first message may be obtained from the accelerator via an interface between the application and the accelerator.

[0049] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for communicating an exchange configuration with the accelerator, the exchange configuration being used to exchange information associated with the DM between the application and the accelerator, wherein communicating the first message, communicating the second message, or both may be based on the exchange configuration.

[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the exchange configuration includes one or more rules, one or more conditions, or both for modifying the DM.

[0051] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: providing a request for the configuration information to the RU via an interface between the application and the RU and based on the context information; and obtaining the configuration information from the RU via the interface between the application and the RU and based on the request, wherein communicating the second message may be based on the obtaining.

[0052] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining from the RU additional configuration information associated with the DM used for communication between the accelerator and the RU; and obtaining from the accelerator a third message indicating a failure of a verification procedure associated with the additional configuration information and executed at the accelerator, wherein the configuration information may be obtained from the RU based on the third message. In some examples, the configuration information from the RU may be obtained via an interface between the application and the RU, or in some other examples, the application may retrieve the configuration information from a storage device. In an example as an alternative to a local cache at the application, if the verification failure involves the third message, the accelerator may perform the verification procedure (e.g., a verification check may be performed at the accelerator rather than at the application).

[0053] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining the configuration information via a cache maintained at the application, wherein communicating the second message may be based on the obtaining.

[0054] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the configuration information includes capabilities associated with the RU, a set of parameters associated with communications performed by the RU, or a state associated with processing of the first message, or any combination thereof.

[0055] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: providing the first message including the context information to the accelerator; and obtaining the second message from the accelerator based on providing the first message, wherein the DM may be hosted at the accelerator.

[0056] A method for wireless communication at an accelerator associated with a DU of a RAN is described. The method may include: communicating a first message with an application executable by the DU, the first message including context information associated with a DM hosted at the accelerator or the application; and communicating a second message with the application based on the context information, the second message including configuration information associated with the DM.

[0057] An apparatus for wireless communication at an accelerator associated with a DU of a RAN is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: communicate a first message with an application executable by the DU, the first message including context information associated with a DM hosted at the accelerator or the application; and communicate a second message with the application based on the context information, the second message including configuration information associated with the DM.

[0058] Another apparatus for wireless communication at an accelerator associated with a DU of a RAN is described. The apparatus may include: a component for communicating a first message with an application executable by the DU, the first message including context information associated with a DM hosted at the accelerator or the application; and a component for communicating a second message with the application based on the context information, the second message including configuration information associated with the DM.

[0059] A non-transitory computer-readable medium storing code for wireless communication at an accelerator associated with a DU of a RAN is described. The code may include instructions executable by a processor to: communicate a first message with an application executable by the DU, the first message including context information associated with a DM hosted at the accelerator or the application; and communicate a second message with the application based on the context information, the second message including configuration information associated with the DM.

[0060] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the context information includes a first identifier associated with the accelerator, a second identifier associated with the RU, a third identifier associated with a profile instance associated with the accelerator, or a fourth identifier associated with the application.

[0061] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the accelerator may be associated with a set of multiple profile instances including the profile instance, and the first identifier corresponds to at least two profile instances in the set of multiple profile instances.

[0062] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the context information includes a set of multiple identifiers associated with a set of multiple profile instances associated with the accelerator, a set of multiple identifiers associated with a set of multiple RUs including the RU, a set of multiple identifiers associated with a set of multiple applications including the application, or any combination thereof, and the configuration information may be associated with the set of multiple profile instances, the set of multiple RUs, the set of multiple applications, or any combination thereof.

[0063] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for providing a third message to the application based on obtaining the second message, the third message indicating a result of a verification procedure associated with the configuration information.

[0064] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a third message from the application, the third message including additional configuration information for the second DM; providing a fourth message to the application based on obtaining the third message, the fourth message indicating a failure of a verification procedure associated with the additional configuration information; obtaining a fifth message from the application in response to the failure, the fifth message instructing the accelerator to modify the context information; and providing a sixth message to the application in response to the fifth message, the sixth message including additional context information for the communication between the accelerator and the RU, wherein obtaining the second message including the configuration information may be based on the sixth message.

[0065] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a third message from the application, the third message including additional configuration information for the second DM; and providing a fourth message to the application based on obtaining the third message, the fourth message indicating a failure of a verification procedure associated with the additional configuration information, wherein the second message including the configuration information can be obtained based on the fourth message, and wherein the configuration information includes a modified version of the additional configuration information.

[0066] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a third message from the application, the third message including additional configuration information for the second DM; determining a failure of a verification procedure associated with the additional configuration information; and providing a fourth message to the application based on the failure, the fourth message indicating the configuration information, wherein the configuration information includes a modified version of the additional configuration information.

[0067] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first message may be provided to the application via an interface between the application and the accelerator.

[0068] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for communicating an exchange configuration with the application, the exchange configuration being used to exchange information associated with the DM between the application and the accelerator, wherein providing the first message, obtaining the second message, or both may be based on the exchange configuration.

[0069] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the exchange configuration includes one or more rules, one or more conditions, or both for modifying the DM.

[0070] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the configuration information includes capabilities associated with the RU, a set of parameters associated with communications performed by the RU, a state associated with processing of the first message, or any combination thereof.

[0071] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: providing the first message including the context information to the application; obtaining the second message including the configuration information from the application, wherein the DM may be associated with communication between the accelerator and a RU coupled to the DU; and communicating with the RU based on the configuration information.

[0072] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: Communication with the RU may be performed via a physical layer interface between the accelerator and the RU.

[0073] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining the first message including the context information from the application; and providing the second message to the application based on obtaining the first message, wherein the DM may be hosted at the accelerator.

[0074] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of limitations to the claims.

[0075] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional specific implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, each embodiment and / or use can be generated via an integrated chip embodiment and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. The scope of specific implementation can range from chip-level or module components to non-module, non-chip-level specific implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovation. In some actual settings, the equipment in conjunction with the aspects and features must also include other components and features for the specific implementation and practice of the embodiments protected and described by the claims. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] Figure 1An example of a wireless communication system supporting techniques for application and accelerator communications for a distributed unit (DU) according to one or more aspects of the present disclosure is illustrated.

[0077] Figure 2 An example of a network architecture supporting techniques for application and accelerator communications for a DU according to one or more aspects of the present disclosure is illustrated.

[0078] Figure 3 An example of an open radio access network (O-RAN) architecture that supports techniques for application and accelerator communications for a DU in accordance with one or more aspects of the present disclosure is illustrated.

[0079] Figure 4 An example of an O-RAN entity supporting techniques for application and accelerator communications for a DU according to one or more aspects of the present disclosure is illustrated.

[0080] Figure 5 An example of a process flow for techniques supporting application and accelerator communications for a DU in accordance with one or more aspects of the present disclosure is illustrated.

[0081] Figure 6 An example of a process flow for techniques supporting application and accelerator communications for a DU in accordance with one or more aspects of the present disclosure is illustrated.

[0082] Figure 7 and Figure 8 A block diagram of a device supporting techniques for application and accelerator communication for a DU according to one or more aspects of the present disclosure is shown.

[0083] Fig. 9 A block diagram of a communication manager supporting techniques for application and accelerator communications for a DU in accordance with one or more aspects of the present disclosure is shown.

[0084] Fig.10 A diagram of a system including a device supporting techniques for application and accelerator communication for a DU in accordance with one or more aspects of the present disclosure is shown.

[0085] Figures 11 to 14 A flow chart illustrating a method of supporting techniques for application and accelerator communication for a DU according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0086] In the context of an open radio access network (O-RAN) architecture, different functions of a base station or network entity may be physically and / or logically divided across multiple physical devices or components. For example, an O-RAN network entity may include a radio unit (RU) and a distributed unit (DU), wherein the RU performs wireless communications with other devices (e.g., user equipment (UE)) via a physical (PHY) layer, and wherein components of the DU perform higher layer functions to support communications performed by the RU. The DU may include applications associated with higher layers (e.g., a medium access control (MAC) layer), and an accelerator (e.g., a higher PHY (HiPHY) component) that serves as an interface between the PHY layer of the RU and upper layers of the application.

[0087] The management plane (M-plane) interface between the DU and the RU can be used to provide the DU with configuration and capability information (e.g., data model (DM)) of the RU. In some specific implementations, the M-plane interface terminates at the accelerator (e.g., the M-plane defines the interface between the accelerator and the DU). However, terminating the M-plane at the accelerator may result in increased signaling between the accelerator and the application, because the accelerator may be required to relay the DM from the RU to the application. In addition, requiring the accelerator to relay the DM to the application may result in duplicate functions and processing being performed at both the application and the accelerator. Other specific implementations may terminate the M-plane at the application itself. However, the O-RAN architecture does not provide any signaling or other mechanism that enables information received by the application via the M-plane to be requested and / or provided to the accelerator by the accelerator.

[0088] Therefore, various aspects of the present disclosure relate to techniques and signaling that enable the M-plane interface between the RU and the DU to terminate at the application of the DU rather than at the accelerator of the DU. Specifically, various aspects of the present disclosure relate to signaling that supports the exchange of context information between the application of the DU and the accelerator to achieve efficient communication of the DM between the application and the accelerator.

[0089] For example, an application of the DU may receive context information from an accelerator of the DU, wherein the context information indicates context / parameters associated with the communication between the accelerator and the RU (e.g., applicable carrier, RU identifier, accelerator identifier, etc.). Based on the received context information, the application may retrieve configuration information for the DM associated with the communication between the accelerator and the RU. The application may retrieve the configuration information / DM from the memory, or may send a request to the RU via the M-face between the application and the RU. Subsequently, the application may provide the configuration information / DM to the accelerator so that the accelerator can use the configuration information to communicate with the RU. In some specific implementations, the application and / or the accelerator may perform a verification procedure on the obtained configuration information, and may be able to modify the configuration and / or request new configuration information if the verification fails.

[0090] In contrast, the accelerator of the DU may receive context information from the application of the DU, wherein the context information indicates context / parameters associated with the DM hosted at the accelerator (e.g., applicable carrier, RU identifier, accelerator identifier, etc.). Based on the received context information, the accelerator may retrieve configuration information for the DM and provide the retrieved DM to the application in response to the received context information.

[0091] Aspects of the disclosure are first described in the context of a wireless communication system. Additional aspects of the disclosure are described in the context of example O-RAN entities and example process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams of techniques for application and accelerator communications for DUs.

[0092] Figure 1 An example of a wireless communication system 100 that supports techniques for application and accelerator communications for a DU according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0093] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other names. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area, and the network entity 105 and the UE 115 may support signal communications over the geographic area according to one or more radio access technologies (RATs).

[0094] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0095] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0096] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0097] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0098] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an O-RAN (e.g., a network configuration advocated by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a DU 165, a RU 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC), a RAN intelligent controller (RIC ... The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in a distributed location (e.g., a separate physical location). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as a virtual unit (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0099] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., PHY layer) or L2 (e.g., radio link control (RLC) layer, MAC layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by the other of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0100] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to the core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as host entities or IAB hosts. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a host network entity 105 (e.g., a host base station 140). One or more host network entities 105 (e.g., IAB hosts) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB host. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0101] For example, an access network (AN) or RAN may include an access node (e.g., an IAB host), communications between an IAB node 104, and one or more UEs 115. The IAB host may facilitate a connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB host may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB host may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB host and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB host) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0102] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, the IAB host may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB host may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0103] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child node associated with the IAB host, or both. The IAB host may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB host may relay the transmission to the UE 115 via the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB host may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB host to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB host, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0104] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support techniques for application and accelerator communications for the DU as described herein. For example, some operations described as being performed by the UE 115 or the network entity 105 (e.g., the base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).

[0105] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0106] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0107] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0108] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0109] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, among other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

[0110] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 may have a hardware configuration that supports communications using a particular carrier bandwidth or may be capable of being configured to support communications using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

[0111] The signal waveform transmitted via the carrier wave may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of the communication with the UE 115.

[0112] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0113] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0114] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may also be divided into multiple mini time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0115] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0116] Physical channels may be multiplexed using carriers for communication according to various techniques. For example, physical control channels and physical data channels may be multiplexed via downlink carriers for signaling using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0117] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0118] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety applications or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency are used interchangeably herein.

[0119] In some examples, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may occur between UEs 115 without involving network entity 105 .

[0120] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity for routing packets or interconnecting to an external network (e.g., a serving gateway (S-GW)), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered via the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0121] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0122] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating using unlicensed RF spectrum bands, devices such as network entities 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on carrier aggregation configuration in combination with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0123] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0124] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such technology may be referred to as spatial multiplexing. Multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0125] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a sender device or a receiver device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the sender device and the receiver device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the sender device or the receiver device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the sender device or the receiver device or relative to some other orientation).

[0126] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) a beam direction for later transmission or reception by the network entity 105.

[0127] Some signals, such as data signals associated with a particular receiving device, may be sent by a sending device (e.g., sending network entity 105, sending UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0128] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or non-precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0129] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0130] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0131] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0132] In some specific implementations, the wireless communication system 100 may support technologies and signaling that enable the M-plane interface between the RU of the O-RAN network entity 105 and the DU to terminate at the application of the DU instead of at the accelerator of the DU. Specifically, the wireless communication system 100 may include an O-RAN network entity 105 that supports signaling that enables the exchange of context information between the application of the DU of the O-RAN network entity 105 and the accelerator to achieve efficient communication of DM between the application and the accelerator.

[0133] For example, the wireless communication system 100 may include an O-RAN network entity 105, which includes a DU and a RU. In this example, the application of the DU may receive context information from the accelerator of the DU, wherein the context information indicates the context / parameters associated with the communication between the accelerator and the RU (e.g., applicable carrier, RU identifier, accelerator identifier, etc.). Based on the received context information, the application may retrieve configuration information for the DM associated with the communication between the accelerator and the RU. The application may retrieve the configuration information / DM from the memory, or may send a request to the RU via the M-face between the application and the RU. Subsequently, the application may provide the configuration information / DM to the accelerator so that the accelerator can use the configuration information to communicate with the RU. In some specific implementations, the application and / or the accelerator may perform a verification procedure on the obtained configuration information, and may be able to modify the configuration and / or request new configuration information if the verification fails.

[0134] The techniques described herein may enable the M-plane interface between the DU and the RU of the O-RAN network entity 105 to terminate at the application of the DU rather than at the accelerator of the DU. Specifically, the techniques disclosed herein support signaling between the application of the DU and the accelerator, which signaling enables the M-plane interface to terminate at the application. By enabling the M-plane interface to terminate at the application rather than at the accelerator, the techniques described herein may reduce or eliminate the need for the accelerator to relay DMs received from the RU to the application, thereby reducing the signaling and processing performed at the DU. Additionally, by enabling the M-plane interface to terminate at the application, the techniques described herein may reduce the amount of processing operations replicated across both the application and the accelerator, thereby reducing the power consumption and complexity of the DU and the O-RAN network entity 105.

[0135] Figure 2 An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports techniques for application and accelerator communication for DUs according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served simultaneously by multiple RUs 170-a.

[0136] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

[0137] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU160-a. CU 160-a may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0138] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional splits, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0139] In some examples, lower layer functionality may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, RU170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with RU 170-a may be controlled by corresponding DU 165-a. In some examples, such a configuration may enable DU 165-a and CU160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0140] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) to perform network entity lifecycle management (e.g., instantiating virtualized network entities 105) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate (e.g., via an O1 interface) with components configured according to a 4G RAN. Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0141] The non-RT RIC 175-a may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via an E2 interface) that connects one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 with the near-RT RIC 175-b.

[0142] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (e.g., an A1 policy).

[0143] As will be described in further detail herein, the network architecture 200 may illustrate an example of an O-RAN network entity 105 that supports signaling that enables an M-plane interface between the RU 170 of the O-RAN network entity 105 and the DU 165 to terminate at an application of the DU 165.

[0144] Figure 3 An example of an O-RAN architecture 300 that supports techniques for application and accelerator communication for a DU according to one or more aspects of the present disclosure is illustrated. In some examples, aspects of the O-RAN architecture 300 may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, or both. Specifically, the O-RAN architecture 300 may include an O-RAN network entity that supports signaling that enables an M-plane interface between a RU of the O-RAN network entity 105 and a DU to terminate at an application of the DU, such as with respect to Figure 1 and Figure 2 as described.

[0145] In some specific implementations of the O-RAN architecture 300, an access and mobility management function (AMF 305) or a user plane function (UPF) (hereinafter referred to as AMF 305) may be connected to one or more network entities 105-a, 105-b (e.g., gNB) via a next generation (NG) interface. The network entities 105 may be connected to each other via an Xn interface. The network entity 105 may include a CU 310, which may be connected to one or more DUs 315 via an F1 interface.

[0146] DU 315 may include layer 2 (L2) and layer 3 (L3) (hereinafter referred to as L2 / L3 325), which may be associated with a control layer, an RRC layer, a PDCP layer, an RLC layer, and a MAC layer. L2 / L3 325 may communicate with layer 1 (L1 330) via a functional application platform interface (FAPI 335). FAPI 335 may implement slot-by-slot operation. FAPI 335 may be stateless and may implement air transmission and reception. L1 330 may be associated with a PHY layer and a front end unit (FEU). The PHY layer may be associated with a baseband, which may include digital beamforming. The baseband may communicate with FAPI 335 via a P5 interface that may be associated with PHY control and via a P7 interface that may be associated with PHY control. FEU may be associated with a digital front end (DFE), an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC), and an RF, which may be associated with analog beamforming. The DFE and RF may communicate with the FAPI via a P19 interface, which may be associated with FEU control.

[0147] It should be noted in this article that Figure 3 The O-RAN architecture 300 illustrated in FIG. 3 is provided for example and illustration purposes only. In this regard, other examples of O-RAN architectures may differ from what is described with respect to the O-RAN architecture 300.

[0148] The O-RAN fronthaul (FH) (OFH) may provide a stateless interface operating with symbol resolution between a high PHY layer (e.g., DU 315-a, DU315-b) associated with the O-DU 315 and a low PHY layer (e.g., RU 320-a, 320-b) associated with the O-RU 320. The O-RAN FH may be associated with a control plane (C-plane). The C-plane may provide scheduling and beamforming commands, multiple parameter sets, channel estimation, unlicensed access support, partial extensions for updating beam weights, and / or non-contiguous resource block patterns to the O-RU 320. The O-RAN FH may be associated with a user plane (U-plane). The U-plane may provide support for transmission and / or compression of samples scheduled on the C-plane (or semi-statically configured on the M-plane). The O-RAN FH may be associated with a synchronization plane, which may provide profiles of protocols and mechanisms for ensuring timely delivery of the C-plane and the U-plane.

[0149] FAPI 335 may be an example of an interface between L2 / L3 325 and L1 330 in O-DU 315, while O-RANFH may provide connectivity between O-DU 315 and O-RU 320. In some implementations, FAPI 335 may be independent of O-RANFH.

[0150] The O-DU 315 may employ an accelerator (e.g., a hardware accelerator and associated libraries / drivers) to improve the performance of the O-DU 315. The accelerator may be implemented by using the FAPI 335 to support interactions at the O-DU 315. Since the FAPI 335 has limited awareness of the O-RAN FH (which may provide connectivity between the O-DU 315 and the O-RU 320), the accelerator may need to generate O-RAN FH messages for both the C-plane and the U-plane. However, the value of the accelerator may be primarily applicable to the U-plane relative to in-phase and quadrature (I / Q) signal generation and decoding, or to the C-plane generation of beamforming weights, and a specific O-DU 315 implementation may not require the assistance of an accelerator to generate other C-plane messages or fields. The accelerator may use high-performance hardware that is not well suited for complex data structures, but may be very suitable for processing FH U-plane messages (e.g., I / Q samples to and from the O-RU 320) or beam weights (e.g., complex valued samples to or from the O-RU 320). Therefore, generating or receiving O-RAN FH messages for all C-plane and U-plane messages may not be as valuable as focusing an accelerator on hardware-intensive message generation or reception in the O-DU 315 .

[0151] In some aspects, the O-DU 315 may generate or receive C-Plane messages at an O-DU 315 application executing on the O-DU 315. The O-DU 315 may transmit C-Plane messages between the O-DU 315 application and the O-RU 320 via a run-through of an accelerator of the O-DU 315 consistent with the O-DU 315 application. The C-Plane messages may run through the accelerator of the O-DU 315 and may not be subject to hardware acceleration at the accelerator, except for a possible transposition between the application message payload and the transmission medium. This transposition may involve I / Q sample or beamforming weight compression or decompression or the addition or removal of transmission adaptation. In other words, for the run-through, the message payload may be completely generated or interpreted at the O-DU 315 application, and the accelerator may at most participate in the transposition of compression / decompression.

[0152] In addition, the C-plane message may be a first message, and the O-DU 315 may generate or receive a second control or U-plane message (second message) at the accelerator based at least in part on the FAPI 335 exchange between the accelerator and the O-DU 315 application. The second message may be hardware accelerated at the accelerator. The O-DU 315 may transmit the second message to the O-RU 320 via the accelerator. Therefore, some messages generated at the O-DU 315 (e.g., C-plane messages) may run through the accelerator, while other messages (e.g., C-plane messages and U-plane messages generated at the O-DU 315) may be directed to the accelerator for hardware acceleration, thereby improving the performance of the accelerator.

[0153] In some aspects, some C-plane messages may not terminate at the accelerator in the O-DU 315, so that C-plane transparency can be increased for the accelerator. Certain C-plane messages may be generated or received in the O-DU 315 application, and these C-plane messages may run through the accelerator and exchange with the O-RU 320. The penetration of certain C-plane messages can minimize the bookkeeping at the accelerator, and minimize the amount of conversion without any added value at the accelerator, thereby improving the performance of the accelerator. The penetration of certain C-plane messages at the accelerator may result in additional cycles that can be used for higher value functions at the accelerator. In addition, the management plane may be terminated mainly in the O-DU 315 application rather than in the accelerator. Therefore, the FAPI 335 exchange can be used in a way that accurately extracts as many values ​​as the O-DU315 application requires from the accelerator.

[0154] Figure 4 An example of an O-RAN entity 400 that supports techniques for application and accelerator communication for a DU according to one or more aspects of the present disclosure is illustrated. In some examples, aspects of the O-RAN entity 400 may implement aspects of the wireless communication system 100, the network architecture 200, the O-RAN architecture 300, or any combination thereof, or be implemented by these aspects. Specifically, the O-RAN entity 400 may support signaling that enables an M-plane interface between a RU of the O-RAN entity 400 and a DU to terminate at an application of the DU, such as with respect to Figures 1 to 3 as described.

[0155] The O-RAN entity 400 may include a DU 405 and a RU 410, which may be as shown in FIG. Figure 2 Examples of DU 165 and RU 170 described, and / or as referenced Figure 3 4. An example of a DU 315 and RU 320 is described. In some implementations, the O-RAN entity 400 may include multiple RUs 410 that are communicatively coupled to (e.g., controlled by) a DU 405. In some implementations, lower layer functionality of the O-RAN entity 400 may be implemented by a RU 410 that is controlled by the DU 405. For example, the RU 410 may include or correspond to a logical node that hosts RF processing functions, low PHY layer functions (e.g., FFT, iFFT, digital beamforming, PRACH extraction and filtering, etc.), or both. Figure 4 In the O-RAN entity 400 illustrated in FIG. 4 , the RU 410a may be configured to perform communications (eg, OTA communications) with other wireless devices such as the UE 115 .

[0156] DU 405 may include an application 415 and an accelerator 420. As previously described herein, DU 405 may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of RU 410. In some examples, DU 405 may host, at least in part, one or more of one or more aspects of an RLC layer, a MAC layer, and a PHY layer. For example, application 415 may include or support upper layers, such as MAC and RLC layers, and accelerator 420 may support HiPHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.

[0157] In some aspects, the accelerator 420 may include one or more sets of hardware units, where each hardware unit is associated with an identifier corresponding to the accelerator 420. In some aspects, each hardware unit may include or support a carrier or profile instance (e.g., an accelerator profile instance, where a single profile instance is associated with a FAPI PHY ID), which may be unique within the context of the hardware unit or within the context of the accelerator 420. In some aspects, a profile instance may refer to an accelerator 420 resource dedicated to generating and receiving a baseband carrier when it is applied to FAPI, where the context of the profile instance may be identified by a PHY ID, as shown in Table 1.

[0158] The different operations / functions supported by (or executed at) the DU 405 and the RU 410 may be based on a functional split, such as an underlying functional split, between the respective components. Figure 4 The O-RAN entity 400 shown in the figure illustrates an example of a 7.2x split specific implementation of the corresponding components of the O-RAN entity 400, wherein the RU 410 supports PHY layer communications such as sampling, conversion, etc., the accelerator 420 (e.g., hi-PHY, or upper layer PHY) supports some data processing operations (e.g., digital beamforming, decoding, synchronization, FEC), and the application 415 (e.g., MAC and other upper layers) supports various upper layer functions (e.g., mapping U-plane to TB, synchronization of C-plane, etc.).

[0159] The respective components of the O-RAN entity 400 may communicate with each other via one or more interfaces. For example, the DU 405 and the RU 410 may communicate with each other via the interface 430, which may be an example of a Lo / Hi PHY interface. Furthermore, as previously described herein, the FAPI enables communication between L1 and L2 / L3, and thus may define Figure 4415 and the accelerator 420. The FAPI may be exemplified by one or more interfaces 435-a, 435-b, 435-c, and 435-d between the application 415 and the accelerator 420. The FAPI may define an interface between the MAC and the upper layer PHY, which may be associated with the physical and logical partitioning between hardware applications / operations (supported by the accelerator 420) and software applications / operations (supported by the application 415). In addition to enabling slot-by-slot operation and OTA transmission / reception, the FAPI may also be configured to support heterogeneous architectures within the O-RAN entity 400.

[0160] In addition, if Figure 4 As shown, the O-RAN entity 400 may include an M-plane interface 440 that facilitates communication between the DU 405 and the RU 410. Figure 4 In the context of the 7.2x split implementation illustrated in , the M-Plane interface may terminate at the HiPHY (eg, accelerator 420) or the application 415. However, in some conventional wireless communication systems, neither HiPHY nor application 415 termination may be fully supported.

[0161] In some specific implementations, the M-plane interface 440 may terminate at a HiPHY (e.g., an accelerator 420) (not shown). In such cases where the M-plane interface 440 terminates at an accelerator 420 in the HiPHY, the accelerator 420 may be able to discover RU 410 capabilities and configure RU 410 parameters with minimal assistance from the application 415. In other words, terminating the M-plane interface 440 at the accelerator 420 may enable the accelerator 420 and the RU 410 to exchange DM 425 directly between the respective components. However, terminating the M-plane interface 440 at the accelerator 420 may result in increased signaling between the accelerator 420 and the application 415, because the accelerator 420 may be required to relay the DM 425 from the RU 410 to the application 415. In other words, some O-RAN M-plane interface 440 capabilities and configurations may be expected at the MAC layer, but cannot be directly retrieved by the application 415 (e.g., capabilities not exposed to the MAC via the FAPI). Furthermore, requiring the accelerator 420 to relay information received via the M-plane interface 440 to the application 415 may result in duplicate functions and processing being performed at both the application 415 and the accelerator 420 .

[0162] In contrast, some other specific implementations may terminate the M-plane interface 440 at the application 415 itself. Terminating the M-plane interface 440 at the application 415 may enable the application 415 to discover the RU 410 capabilities and configure the RU 410 parameters. However, some conventional O-RAN architectures do not provide any signaling or other mechanisms that enable the information received by the application 415 via the M-plane interface 440 to be requested by the accelerator 420 and / or provided to the accelerator. In other words, where the M-plane interface 440 terminates at the application 415, there is currently no open support for HiPHY (e.g., accelerator 420) to discover RU 410 capabilities and, when necessary, enable HiPHY to configure parameters at RU 410. Therefore, conventional O-RAN architectures do not support any signaling or mechanisms that can be used to convey O-RU 410 capabilities to HiPHY and extract O-RU 410 configuration information from HiPHY.

[0163] Additionally, in the context of the O-RAN entity 400 architecture, the DU 405 may require failure, configuration, accounting, performance, and security (FCAPS) for DU 405-specific capabilities. In the O-RAN entity 400, DU 405-specific capabilities and configuration parameters are expected to be represented via a YANG model, which is a modeling language used in the O-RAN architecture to model the configuration and operating state of the RU 410. Some of these parameters may be mapped to existing capabilities and parameters (e.g., cell configuration, channel configuration, etc.) exposed via FAPI parameters and configuration APIs (e.g., via P9 interface 435-a). However, other parameters are not constrained by FAPI P5 (e.g., interface 435-a) and may not be communicated via interface 435-a, such as DU405S-plane parameters and DU405-side control user synchronization (CUS) network interface parameters. In other words, where the M-Plane interface 440 terminates at the application 415, the current O-RAN architecture cannot enable all information required / expected at the accelerator 420 to be communicated from the application 415 to the accelerator 420 via the FAPI interface.

[0164] The O-RAN entity 400 can communicate with various DMs 425 (including DM O-RUs 425-a and DM qDUs 425-b) is associated with DM O-RUs 425-a may include a DM 425 for each RU 410, or a DM 425 associated with a corresponding RU 410. For example, DM O-RU 425-a can be used with Figure 4 Specifically, DM O-RU425-a may include or define parameters associated with communication between the RU 410 of the DU 405 and the accelerator 420. Figure 4 As shown, application 415 may be configured to reflect or cache DM locally. O-RU At least a portion of 425-a. DM O-RU The open parameters of 425-a may be documented in the O-RAN QG4M plane specification, and there may be additional proprietary parameters. qDU 425 - b may include DM 425 of HiPHY parameters associated with an entity external to HiPHY (eg, application 415 or above).

[0165] As will be described in further detail herein, some aspects of the present disclosure relate to interfaces 435 (e.g., P9 interface 435-c and P10 interface 435-d) between application 415 and accelerator 420 that enable the exchange of DM between the respective components. O-RU 425-a and DM qDU 425-b. Specifically, Figure 4 As shown, some aspects of the present disclosure relate to a method for accessing a DM O-RU 425-a (e.g., DM O-RU 425-a is transmitted from the accelerator 420 to the application 415) and a P9 interface 435-c configured to access the DM qDU 425-b (for example, DM qDU 425-b is transmitted from the application 415 to the P10 interface 435-d of the accelerator 420).

[0166] In other words, aspects of the present disclosure support communication between the application 415 and the accelerator 420, which enables the respective components to perform read / write operations associated with the DM 425 hosted at the respective components (eg, via the P9 and P10 interfaces 435).

[0167] Aspects of the present disclosure relate to techniques and signaling that enable the M-plane interface 440 between the DU 405 and the RU 410 to terminate at the application 415 of the DU 405, such as Figure 4 Specifically, aspects of the present disclosure relate to supporting signaling for exchanging context information between an application 415 and an accelerator 420 via a FAPI (eg, a P9 interface 435 - c , a P10 interface 435 - d ) to enable efficient communication of a DM 425 between the application 415 and the accelerator 420 .

[0168] For example, referring to the O-RAN entity 400, the application 415 and the accelerator 420 may communicate with each other messages indicating an exchange configuration (e.g., P5PARAM / CONFIG exchange) for exchanging information associated with the DM 425 between the application 415 and the accelerator 420. In some aspects, the exchange configuration may include one or more rules, conditions, or both for modifying the DM associated with the communication between the accelerator 420 and the RU 410. In other words, as will be described in further detail herein, the parameters of the exchange configuration (e.g., " <param> ") may include rules or conditions for changing or modifying YANG parameters. In some aspects, the exchange configuration may be communicated via one or more interfaces (e.g., P5 interface 435-a, P19 interface 435-b, P9 interface 435-c, P10 interface 435-d) between the application 415 and the accelerator 420.

[0169] In some aspects, the application 415 may obtain (e.g., receive, acquire) a message including context information for the communication between the accelerator 420 and the RU 410 (e.g., a message indicating "get <root(s) of interest to qDU"). For example, the application 415 may obtain or receive context information from the accelerator 420 via one or more interfaces (such as the P9 interface 435-c) between the application 415 and the accelerator 420. Additionally or alternatively, the application 415 may receive context information from another entity or component of the DU 505.

[0170] The context information may indicate one or more parameters or characteristics associated with the communication between the accelerator 420 and the RU 410. Specifically, in some embodiments, the context information may be exchanged between the accelerator 420 and the application 415 via the P9 interface 435-c. In this regard, the P9 interface 435-a between the application 415 and the accelerator 420 may enable efficient access and exchange of the DM O-RUs 425-a between the corresponding devices. In other words, the P8 interface 435-c may provide transparent access to the DM O-RUs 425-a to the application 415 and the accelerator 420 (HiPHY) interfaces. The P9 interface 435-c may support various operations associated with the DM 425, including "read" operations, "write" operations, other NETCONF or RESTCONF operations, or any combination thereof. In some embodiments, the context information may exhibit the format illustrated in Table 1 below:

[0171]

[0172] Table 1: Context Information (P9 Interface)

[0173] As shown in Table 1, the context information may include, but is not limited to, an identifier associated with the accelerator 420 (e.g., PNF ID (QDU ID)), a carrier associated with the RU 410 (e.g., PHY ID), an identifier associated with the RU 410 (e.g., O-RU ID), a MAC identifier associated with the application 415 (e.g., application ID), etc.

[0174] In some implementations, the context information may be associated with multiple carriers, multiple RUs 410, multiple applications 415, multiple accelerators, or any combination thereof. In other words, the context information may include or indicate a set of carriers associated with a DM for communication between an accelerator 420 and a RU 410, a set of IDs associated with a set of RUs 410, a set of MAC IDs associated with a set of applications 415, or any combination thereof.

[0175] In other words, the techniques described herein may enable a subset of DMO-RU 425-a to be associated with a HiPHY carrier (e.g., a DMO-RU 425-a transaction may be tagged with a PHY ID that identifies the carrier). In some cases, the subset of DMO-RU 425-a accessed by a PHY-specific transaction may be related to the PHY layer (e.g., Tx / Rx antennas, antenna carriers, eAxC assignments, etc.). Additionally or alternatively, the techniques described herein may enable a subset of DMO-RU 425-a to be publicly accessible to multiple carriers. In other words, various aspects of the present disclosure may support timing windows shared by multiple carriers and / or non-carrier-specific data on Tx antennas. In some cases, a special or reserved PHY ID value (e.g., "0") may be used to indicate whether the requested DMO-RU 425-a is associated with multiple carriers.

[0176] Additionally, aspects of the present disclosure may enable DM O-RUs 425-a can be associated with one or more O-RU related identifiers. In other words, a single DM O-RU 425-a may apply to one or more RUs 410. For example, the O-RU ID, NETCONF session, or another identifier pointing to an O-RU context or subcontext may be used in the context information to indicate the applicable RU 410. Additionally or alternatively, DM O-RUs 425-a may apply to a specific carrier or antenna panel at the applicable RU 410. For example, the context information may indicate applicable antenna panels in different O-RUs 410 for a single PHY layer (e.g., mTRP support).

[0177] Additionally, aspects of the present disclosure may enable multiple applications 415 to access the DM O-RUs 425-a. In other words, DM O-RUs 425-a may be non-application specific or application independent. In this regard, the context information illustrated in Table 1 may indicate the context information associated with the requested DM O-RUs 425-a associated with one or more applications 415 (such as via an operator or application ID when multiple operators share a SoC). Similarly, the context information may indicate the applicable application 415 by indicating a vDU ID or an S-DU ID. In addition, aspects of the present disclosure may enable the message exchange service and operation layer to access the DM O-RUs 425-a. For example, in the context of operation, the application 415 and the accelerator 420 may perform read / write operations to access the DM O-RUs 425-a (eg, similar to a NETCONF get or edit-config command). As another example, in the context of a message exchange service, aspects of the present disclosure may support operations such as request / reply association, error reporting, or additional procedures (eg, similar to a NECONF rpc).

[0178] In this regard, the P9 interface 435-a described herein can facilitate message exchange services and operations. For example, the P9 interface 435-c can facilitate message exchange patterns for data access (e.g., read / write / mode, etc. operations and associated responses), error conditions (e.g., exception responses, exception errors), and other commands (e.g., other commands that allow additional transactions, such as antenna calibration commands).

[0179] In addition, the P9 interface 435-c can facilitate other data access operations, such as read operations, write operations, and mode operations. A read operation can be in the form of "read:get <param> ", and may be issued by a qDU (e.g., accelerator 420) and may include a corresponding data response, similar to a NETCONF get and / or get-config command. In such a case, <param> The YANG modules and / or nodes to be signaled by the application 415 may be identified, and the application 415 may provide the accelerator 420 with an identifier. Additionally or alternatively, the read command may be provided by a "set <param> ", which is issued by application 415 and includes a potential success response.

[0180] The write operation may be in the form of "write:edit-config" and may be issued by a qDU (e.g., accelerator 420) and may include a corresponding successful result response, similar to the NETCONF edit-config command. Additionally or alternatively, the write command may be issued by "extract <param> " and may be issued by application 415 and may include a O-RUs The corresponding data response modified in 425. In the context of a write command, <param> Data that the application 415 expects / allows the accelerator 420 (eg, qDU) to potentially modify (which may be indicated via an exchange configuration) may be identified.

[0181] Similarly, a schema operation may take the form "schema:get-schema" and may be issued by a qDU (e.g., accelerator 420) and may include a corresponding schema reply, similar to a NETCONF get-schema command. Additionally or alternatively, a write command may be issued by application 415 using "set-schema <param> " and may include a possible success response. In the context of a mode command, <param> A pattern in which the application 415 notifies the accelerator 420 may be identified.

[0182] Other commands or data access operations that may be facilitated by the P9 interface 435-c may include, but are not limited to, lock / unlock, support for multiple data sets, delete, session notification, notification of metrics, or related DM O-RUs 425 notification, leaf / node changes, etc.

[0183] In some aspects, the application 415 may be configured to utilize the context information (as illustrated in Table 1) to obtain (e.g., retrieve, receive, acquire) configuration information associated with the DM 425 for communication between the accelerator 420 and the RU 410. In some cases, the application 415 may obtain the configuration information by querying the RU 410 (e.g., via the M-plane interface 440).

[0184] For example, in some implementations, the application 415 may provide or output (e.g., send) a request for configuration information associated with the DM 425 to the RU 410. For example, the application 415 may output the request to the RU 410 via the M-plane interface 440 between the application 415 and the RU 410. The application 415 may send the request based on obtaining context information at 530 or both. For example, in some cases, the request may indicate context information obtained from the accelerator 420 or some other component / entity. Continuing with the same example, the application 415 may receive or obtain configuration information from the RU 410 based on (e.g., in response to) the request. In some implementations, the application 415 may receive or obtain configuration information via the M-plane interface 440 between the application 415 and the RU 410. In some aspects, the application 415 may store or save the received configuration information in a memory or cache at (or accessible by) the application 415.

[0185] Additionally or alternatively, the application 415 may obtain the configuration information by retrieving the configuration information from a memory or cache (e.g., a storage device) at the application 415. For example, the application 415 may retrieve the configuration information for the DM 425 from a cache or memory maintained at (or accessible by) the application 415. The application 415 may retrieve the configuration information based on the context information. In some implementations, the application 415 may retrieve the configuration information from the cache instead of querying the RU 410.

[0186] In some aspects, the accelerator 420 may use the configuration information to provide a DM hosted by the accelerator 420. For example, O-RU The configuration information associated with 425-a may include or be associated with one or more parameters or characteristics associated with communications between the accelerator 420 and the RU 410. For example, in some cases, the configuration information may include capabilities associated with the RU 410, parameters associated with communications performed by the RU 410 (e.g., supported carriers), etc.

[0187] In some aspects, the application 415 may provide (e.g., output, send) a message including the received configuration information to the accelerator 420 (e.g., indicating “<root(s)of interest to qDU> ” message (for example, providing “<root(s)of interest to qDU> ” message of YANG data). In some aspects, the configuration information may be communicated via one or more interfaces between the application 415 and the accelerator 420, such as via the P9 interface 435-c. In some aspects, the P9 interface 435-c may implement strict simplifications that enable the application 415 to signal the cached YANG data file to each PHY and extract the leaves to be modified from the P5 parameters.

[0188] In some specific implementations, such as relative to Figure 5 In further detail, the application 415, the accelerator 420, or both may be configured to validate the received configuration parameters. The application 415 and / or the accelerator 420 may perform a validation procedure to determine whether the received configuration information includes expected parameters or characteristics associated with the communication between the accelerator 420 and the RU 410. In some aspects, the respective components may perform the validation procedure based on (e.g., using) the context information received at 530. In other words, the application 415 and / or the accelerator 420 may be configured to validate the received DM O-RUs 425 - a. In some cases, application 415 may be configured to validate received configuration information before providing the configuration information to accelerator 420 (eg, only provide validated configuration information to accelerator 420 ).

[0189] As will be described in further detail herein, in the event that configuration information received at the application 415 and / or accelerator 420 fails to pass a verification procedure (e.g., fails to pass a write verification), the corresponding components may be configured to utilize various methods or specific implementations to modify or obtain additional configuration information that can pass verification.

[0190] According to a first specific implementation for handling verification failures, the accelerator 420 (e.g., a client of the P9 interface 435-c) may retry sending context information and / or retrieving configuration information until a threshold or maximum number of attempts is reached, and / or for a certain duration of time until a timeout (wherein the threshold / maximum number of attempts and / or the duration of time may be signaled, hard-coded, or capability-based). According to a second specific implementation for handling verification failures, the accelerator 420 may store the verification failure in a memory, and use the edit configuration in a different manner (e.g., swap configuration) based on the stored verification failure. According to a third specific implementation for handling verification failures, the application 415 (e.g., a server of the P9 interface 435-c) may store the verification failure in a memory and notify the accelerator 420 to retry writing in a different manner or means (e.g., notify the accelerator 420 to retry writing in a more conservative manner (e.g., by providing more conservative context information)). In other words, according to the third specific implementation, the application 415 may instruct the accelerator 420 to modify the configuration information to be used to retrieve the configuration information for the DM O-RUs Additionally or alternatively, application 415 may modify configuration information and / or DM O-RU 425-a to limit the editing operations available to the accelerator 420, and / or to provide the accelerator 420 with modified / edited configuration information and / or modified DM O-RU 425-a.

[0191] For example, in the case where the verification procedure fails (e.g., the received configuration information fails to pass the verification procedure), the application 415 and / or the accelerator 420 may modify the received configuration information, retrieve new configuration information, or both. For example, in some cases, the application 415 and / or the accelerator 420 may modify one or more parameters of the configuration information according to the exchange configuration. Specifically, the application 415 and / or the accelerator 420 may modify one or more parameters of the configuration information according to one or more parameters or rules of the DM 425 associated with the communication between the accelerator 420 and the RU 410, as defined by the exchange configuration. In this regard, in the case where the verification procedure fails, the application 415 and / or the accelerator 420 may generate a modified version of the configuration information.

[0192] The application 415 and / or the accelerator 420 modifies the received O-RUIn the case of configuration information of 425-a that is modified by accelerator 420, the corresponding component may notify other components of the modification (e.g., via P5 interface 435-a or other interface / API). In some cases, the indication of the modification may include a short list of the modified YANG parameters (e.g., the indication of the modification may not be in YANG format). For example, in the case where accelerator 420 modifies a single parameter of the received configuration information, accelerator 420 may indicate the single modified parameter to application 415 (rather than returning the complete configuration information with the single modified parameter).

[0193] As another example, in some implementations, in the event that a validation procedure fails, the application 415 may retrieve different configuration information from cache / memory, as shown at 545. Furthermore, in other implementations, the application 415 may requery the RU 410 for new or different configuration information (e.g., via the M-Plane interface 440). In such cases, the application 415 may indicate the failed validation procedure to the RU 410 so that the RU 410 may provide different or modified configuration information (via the M-Plane interface 440) that will pass the validation procedure.

[0194] In additional or alternative specific implementations, in the event that a validation procedure fails, the application 415 may indicate the failure of the validation procedure to the accelerator 420 so that the accelerator may provide new or different context information that can be used to obtain new or different configuration information (e.g., instructing the accelerator 420 to retry writing with more conservative context information). For example, the application 415 may identify the failure of the validation procedure, and may provide a message to the accelerator 420 indicating the failure and instructing the accelerator 420 to modify the context information and / or provide new context information. In this example, the application 415 may receive additional context information from the accelerator 420, and may utilize the additional context information to obtain additional configuration information (e.g., by querying the RU 410 via the M-plane interface 440, or by retrieving the additional context information from a cache). In addition, once the additional context information is obtained, the application 415 may perform a validation procedure on the additional configuration information.

[0195] In the case where the accelerator 420 is configured to perform a validation procedure on the configuration information received from the application 415, the accelerator 420 may provide a message indicating the result of the validation procedure (e.g., validation pass / fail) to the application 415. In other words, the accelerator 420 may indicate whether the received configuration information has been validated. Subsequently, the accelerator 420 may perform a validation procedure based on the received configuration information for the DM O-RU The configuration information of 425-a is communicated to RU 410. For example, in some cases, accelerator 420 may configure one or more parameters at RU 410 according to the configuration information.

[0196] In some aspects, the accelerator 420 may be configured to receive the configuration information (eg, for DM O-RU 425-a) is maintained for a certain time interval until the configuration information is rewritten, until a certain event or condition, or any combination thereof. In other words, the accelerator 420 may utilize different specific implementations to determine whether the DM 425 received from the application 415 is valid or invalid, and to maintain and discard such DM 425. Specifically, the O-RU 410 context state may be maintained (at the accelerator 420) for each O-RU 410 context, where the O-RU 410 context state may be driven or controlled by explicit API calls (e.g., new operations or transactions, out-of-band calls (via FAPIP5), etc.).

[0197] As can be understood from the foregoing description, various operations (eg, read / write operations) may be initiated or triggered by the application 415, the accelerator 420 (eg, HiPHY, qDU), or both. The steps of various operations may differ based on where the corresponding operation is initiated.

[0198] For example, as previously described herein, in the context of a read operation triggered by the accelerator 420 (e.g., a q-DU triggered read), the read operation may include the following steps: (1) the application 415 configures the PHY (FAPI CONFIG); (2) the application 415 determines how to configure the O-RU 410 to serve the carrier intended for the PHY; (3) the application receives a PHY P9 get request (e.g., receiving context information via the P9 interface 435-c); (4) the application converts the PHY request to a NETCONF get (or get-config) toward the O-RU 410 server, or retrieves configuration information from its local cache; (5) the application transmits the configuration information / YANG model (or a subset thereof) associated with the request to the qDU / accelerator 420; and (6) the application 415 receives a FAPI CONFIG.response (e.g., a validation pass / fail response), which may be successful (MSG_OK) or failed (new status code MSG_VALIDATION_FAILURE). Optionally, the application 415 may skip nodes that it deems irrelevant to the PHY. In the context of a read operation initiated by the application 415 (e.g., an application-initiated read), the read operation may include steps 1, 2, 4, and 5 above (e.g., when the application 415 initiates a read, the application 415 does not receive context information and / or a verification response).

[0199] As another example, in the context of a write operation initiated by the accelerator 420 (e.g., a qDU-initiated write), the write operation may include the following steps: (1) the application receives an edit-config from the O-RU 410; (2) the application 415 determines whether the edit-config is allowed; (3) the application 415 caches the edit-config locally, or issues an equivalent edit-config directly to the O-RU 410; and (4) a successful response (if any) may reflect local caching, a successful write to the O-RU 410, or a successful write to the candidate data set. In contrast, in the context of a write operation initiated by the application 415 (e.g., an application-initiated write), the write operation may include the following steps: (1) the application 415 determines which edit-configs are allowed, (2) the application 415 transmits a writable YANG model (e.g., configuration information) to the accelerator 420 / qDU; (3) the accelerator 420 / qDU responds with potential new values ​​in the configuration information / YANG model; (4) the application 415 determines whether the edit-config is allowed; (5) the application 415 caches the edit-config locally, or issues an equivalent edit-config directly to the O-RU 410; and (6) a successful response (if any) may reflect local caching, a successful write to the O-RU 410, or a successful write to the candidate data set.

[0200] In some implementations, the accelerator 420 may be configured to maintain a session with the application 415 (eg, maintain ongoing communications), and the received traffic to the DM may be processed as long as the session is maintained. O-RU The configuration information of 425-a can be valid and consistent across the application 415 and HiPHY (accelerator 420). O-RU The validity of 425-a may be determined by valid = {PHY CONFIG.request, PHY CONFIG, or PHY RUNNING} and invalid = {PHY IDLE}, where this logic extends to PHY ID 0 as a special PHY.

[0201] In the context of read filters (e.g., read operations), full read filters may be associated with xpath and subtree filters. Simplifications to such read techniques may include (1) supporting only subtree filters, (2) supporting only root (module) subtree filters, and (3) not supporting filters. In the context of write operations, full write operations (full support, merge) may include create, delete, replace, remove, merge, or any combination thereof. Simplifications to such write techniques may include signaling writable values ​​in explicit parameters outside of the YANG exchange (e.g., compression values ​​to be used for each eAxC). In the context of mode operations, no support may imply or be associated with support for a base mode / YANG library, where in the event of backward compatibility issues, the application 415 performs a conversion to the correct mode for NETCONF O-RU transactions.

[0202] As previously described herein, the application 415 and the accelerator 420 may be configured to utilize different mechanisms for error handling (e.g., different mechanisms for handling verification failures). In some cases, a component may simplify such error handling by handling a single error "operation failure". For complete error handling / verification failure, a component may implement an operation that indicates a validity failure on the qDU / accelerator 420 side (e.g., the application 415 may be used to fall back to the basic model on the next get request). Additionally or alternatively, a component may support new statistical codes for PHY_CONFIG.reply (e.g., "YANG verification failure"). Other simplifications may include no read verification, support for writable data stores, and no support for notifications and / or locking.

[0203] Some aspects of the present disclosure may support use with DM O-RU Various techniques or simplifications of writable parameters of configuration information associated with 425-a. For example, the priority of coupling selection can be used to establish a preferred order of coupling priorities (e.g., normal, frequency and time, frequency and time with priority, frequency and time with optimized priority), where the list can depend on the part type. Other writable parameters may include priorities for downlink, uplink and bandwidth I / Q compression types (e.g., dynamic, static, possibly by part type), priorities for uplink I / Q compression methods (e.g., dynamic list, static selection), preferred I / Q weights, etc. In some specific implementations, simplifications of writable parameters can be performed for each eAxC-ID (e.g., coupling and compression type, compression method and / or I / Q weight for each uplink / downlink bandwidth).

[0204] The techniques described herein may enable the M-plane interface 440 between the DU 405 and the RU 410 of the O-RAN entity 400 to terminate at the application 415 of the DU 405, rather than at the accelerator 420 of the DU 405. Specifically, the techniques of the present disclosure support signaling between the application 415 of the DU 405 and the accelerator 420, which enables the M-plane interface 440 to terminate at the application 415. By enabling the M-plane interface 440 to terminate at the application 415, rather than at the accelerator 420, the techniques described herein may reduce or eliminate the need for the accelerator 420 to relay the DM 425 received from the RU 410 to the application 415, thereby reducing the signaling and processing performed at the DU 405. Additionally, by enabling the M-plane interface 440 to terminate at the application 415, the techniques described herein may reduce the amount of processing operations replicated across both the application 415 and the accelerator 420, thereby reducing the power consumption and complexity of the DU 405 and the O-RAN entity 400.

[0205] Figure 5 An example of a process flow 500 that supports techniques for application and accelerator communications for a DU in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the process flow 500 may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, the O-RAN architecture 300, the O-RAN entity 400, or any combination thereof.

[0206] The process flow 500 may include a DU 505 and a RU 510 of an O-RAN entity, which may be a reference Figure 1-Figure 4 Examples of DU, RU and O-RAN entities described. For example, Figure 5 The DU 505 and RU 510 illustrated in FIG. 5 may be respectively Figure 4 Examples of DU 405 and RU 410 illustrated in .

[0207] In some examples, the operations illustrated by process flow 500 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. The following alternative examples may be implemented in which some of the steps are performed in an order different from the order described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0208] At 525, the application 515 and the accelerator 520 may communicate messages to each other indicating an exchange configuration for exchanging information associated with the data model between the application 515 and the accelerator 520. In some aspects, the exchange configuration may include a message for modifying a DM associated with communications between the accelerator 520 and the RU 510 (e.g., Figure 4 DM exemplified in O-RUs In some aspects, the exchange configuration may be communicated via one or more interfaces (eg, P5, P19, P9, P10 interfaces) between the application 515 and the accelerator 520.

[0209] At 530, the application 515 may obtain (e.g., receive, acquire) context information for communication between the accelerator 520 and the RU 510 communicatively coupled to the DU 505. For example, Figure 4 As shown, application 515 may obtain or receive context information from accelerator 520. In some aspects, application 515 may obtain (and accelerator 520 may provide) context information at 530 based on obtaining / providing the exchange configuration at 525.

[0210] In some aspects, the context information may be communicated via one or more interfaces (eg, P5, P19, P9, P10 interfaces) between the application 515 and the accelerator 520. Additionally or alternatively, the application 515 may receive the context information from another entity or component of the DU 505.

[0211] The context information may indicate one or more parameters or characteristics associated with the communication between the accelerator 520 and the RU 510. Specifically, in some implementations, the context information may be transmitted via Figure 4 The P9 interface 435-c illustrated in FIG. 4 is exchanged between the accelerator 520 and the application 515, and may exhibit the format illustrated in the above Table 1. For example, as shown in Table 1, the context information may include, but is not limited to, an identifier associated with the accelerator 520 (e.g., PNF ID (QDU ID)), a carrier associated with the RU 510 (e.g., PHY ID), an identifier associated with the RU 510 (e.g., O-RU ID), a MAC identifier associated with the application 515 (e.g., application ID), and the like.

[0212] In addition, in some implementations, the context information may be associated with multiple carriers, multiple RUs 510, multiple applications 515, multiple accelerators, or any combination thereof. In other words, the context information may include or indicate a set of carriers associated with a DM for communication between an accelerator 520 and a RU 510, a set of IDs associated with a set of RUs 510, a set of MAC IDs associated with a set of applications 515, or any combination thereof.

[0213] The application 515 may be configured to utilize the context information received at 530 to obtain (eg, retrieve, receive, acquire) a DM (eg, DM O-RU 425-a). In some cases, the application 515 may obtain the configuration information by querying the RU 510 (e.g., via the M-plane interface 440), as shown in steps 535 and 540. Additionally or alternatively, the application 515 may obtain the configuration information by retrieving the configuration information from a memory or cache at the application 515, as shown in step 545. Various methods for obtaining configuration information based on context information will be described in turn.

[0214] At 535, the application 515 may provide or output (eg, send) configuration information (eg, DM O-RU 425-a) request. For example, Figure 4 , application 515 may output a request to RU 510 via an M-plane interface between application 515 and RU 510. Application 515 may send the request at 535 based on obtaining / providing the exchange configuration at 525, obtaining the context information at 530, or both. For example, in some cases, the request may indicate the context information received at 530.

[0215] At 540, the application 515 may receive or obtain a configuration (eg, DM O-RU 425-a). Specifically, the application 515 may receive the configuration information based on (e.g., in response to) the request at 535. In some implementations, the application 515 may receive or obtain the configuration information via an M-plane interface between the application 515 and the RU 510 at 540. In some aspects, the application 515 may store or save the received configuration information in a memory or cache at (or accessible by) the application 515.

[0216] The configuration information may include or be associated with one or more parameters or characteristics associated with communications between the accelerator 520 and the RU 510. For example, in some cases, the configuration information may include capabilities associated with the RU 510, parameters associated with communications performed by the RU 510 (e.g., supported carriers), etc.

[0217] At 545, the application 515 may retrieve the configuration information from a cache or memory maintained at (or accessible by) the application 515. The application 515 may retrieve the configuration information based on the context information received at 530. In some implementations, the application 515 may retrieve the configuration information from the cache rather than querying the RU 510 at 535 and 540. In this regard, the querying process illustrated at 535 and 540 and the retrieving process illustrated at 545 may be viewed as alternative methods or implementations for obtaining configuration information based on the received context information.

[0218] At 550, the application 515 may perform a validation procedure on the obtained configuration information. The application 515 may perform the validation procedure to determine whether the received configuration information includes expected parameters or characteristics associated with communication between the accelerator 520 and the RU 510. In some aspects, the application 515 may perform the validation procedure based on (e.g., using) the context information received at 530.

[0219] In the event that the validation procedure fails (e.g., the received configuration information does not pass the validation procedure), the application 515 may modify the received configuration information, retrieve new configuration information, or both. For example, in some cases, the application 515 may modify one or more parameters of the configuration information according to the exchange configuration obtained / provided at 525. Specifically, the application 515 may modify one or more parameters of the configuration information according to one or more parameters or rules for modifying the DM associated with the communication between the accelerator 520 and the RU 510, as defined by the exchange configuration. In this regard, in the event that the validation procedure fails, the application 515 may generate a modified version of the configuration information that may be provided to the accelerator 520.

[0220] In additional or alternative implementations, in the event that the validation procedure fails, the application 515 may retrieve different configuration information from the cache / memory, as shown at 545. Furthermore, in other implementations, the application 515 may requery the RU 510 for new or different configuration information, as shown at 535 and 540. In such cases, the application 515 may indicate the failed validation procedure to the RU 510 so that the RU 510 may provide different or modified configuration information that will pass the validation procedure at 550.

[0221] In additional or alternative implementations, in the event that a validation procedure fails, the application 515 may indicate the failure of the validation procedure to the accelerator 520 so that the accelerator may provide new or different context information that can be used to obtain new or different configuration information. For example, the application 515 may identify the failure of the validation procedure at 550, and may provide a message to the accelerator indicating the failure and instructing the accelerator 520 to modify the context information and / or provide new context information. In this example, the application 515 may receive additional context information from the accelerator 520, and may utilize the additional context information to obtain additional configuration information (e.g., via querying the RU 510 at 535 and 540, or by retrieving the additional context information from a cache at 545). In addition, once the additional configuration information is obtained, the application 515 may perform a validation procedure on the additional configuration information at 550.

[0222] At 555, the application 515 can provide (eg, output, send) configuration information to the accelerator 520. In some aspects, the configuration information can be communicated via one or more interfaces between the application 515 and the accelerator 520 (eg, P5, P19, P9, P10 interfaces).

[0223] In some aspects, the application 515 may provide configuration information to the accelerator 520 at 555 based on obtaining / providing the exchange configuration at 525, obtaining context information at 530, obtaining configuration information at 535, 540, and / or 545, performing a validation procedure at 550, or any combination thereof. For example, the application 515 may provide configuration information at 555 based on the configuration information passing the validation procedure at 550.

[0224] As another example, in the event that the original configuration information received at 540 and / or 545 fails to pass the validation procedure, the application 515 may obtain additional configuration information, which may pass the validation procedure at 550 and then be provided to the accelerator 520. In additional or alternative implementations, the application 515 may not be configured to perform a validation procedure, as shown at 550. In such cases, the application 515 may provide the configuration information to the accelerator 520 without performing a validation procedure (e.g., whether the obtained configuration information will pass the validation procedure).

[0225] At 560, the accelerator 520 may perform a validation procedure on the obtained configuration information. The accelerator 520 may perform a validation procedure to determine whether the received configuration information includes expected parameters or characteristics associated with communication between the accelerator 520 and the RU 510. As previously described herein with respect to the validation procedure at 550, the accelerator 520 may perform the validation procedure based on (e.g., using) the context information provided at 530.

[0226] At 565, accelerator 520 may provide a message to application 515 indicating the result of the validation procedure (eg, validation passed / failed) performed at 560. In other words, accelerator 520 may indicate whether the received configuration information has been validated.

[0227] In the event of a verification failure, accelerator 520 may be configured to utilize one or more methods or implementations to obtain new or modified configuration information, as previously described herein with respect to the verification procedure at 555. For example, accelerator 520 may be configured to modify one or more parameters of the configuration information (e.g., based on the exchange configuration), send additional (e.g., modified) context information to accelerator 515 that may be used to obtain additional configuration information, etc. In this regard, any implementations described in the context of the verification procedure at 550 for obtaining additional / modified configuration information in the event of a verification failure may also be applicable to the verification procedure at 560, unless otherwise indicated herein.

[0228] At 570, the accelerator 520 may communicate with the RU 510 based on the configuration information. For example, in some cases, the accelerator 520 may configure one or more parameters at the RU 510 based on the configuration information. In some aspects, the accelerator 520 may communicate with the RU 510 based on verifying the configuration information at 560, based on obtaining additional configuration information that is verified at 560, or based on both. In addition, the accelerator 520 may perform the communication at 570 based on sending a message indicating the result of the verification procedure at 565.

[0229] Figure 6 An example of a process flow 600 that supports techniques for application and accelerator communications for a DU in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the process flow 600 may implement or be implemented by aspects of the wireless communication system 100, the network architecture 200, the O-RAN architecture 300, the O-RAN entity 400, the process flow 500, or any combination thereof.

[0230] The process flow 600 may include a DU 605 and a RU 610 of an O-RAN entity, which may be a reference Figures 1 to 4 Examples of DU, RU and O-RAN entities described. For example, Figure 5 The DU 605 and RU 610 illustrated in FIG. 6 may be respectively Figure 4 Examples of DU 405 and RU 410 illustrated in .

[0231] In some examples, the operations illustrated by process flow 600 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. The following alternative examples may be implemented in which some of the steps are performed in an order different from the order described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0232] At 625, the application 615 and the accelerator 620 may communicate to each other messages indicating an exchange configuration for exchanging information associated with the data model between the application 615 and the accelerator 620. In some aspects, the exchange configuration may include a message for modifying the DM (e.g., Figure 4 DM exemplified in O-RUs 425-a and / or DM qDUs 425 - b) of one or more rules, conditions, or both. In some aspects, the exchange configuration may be communicated via one or more interfaces (eg, P5, P19, P9, P10 interfaces) between the application 615 and the accelerator 620.

[0233] At 630, accelerator 620 may obtain (eg, receive, acquire) context information for the DM from accelerator 620. In some aspects, based on obtaining / providing the exchange configuration at 625, accelerator 620 may obtain (and application 615 may provide) context information at 630.

[0234] In some aspects, the context information may be communicated via one or more interfaces (eg, P5, P19, P9, P10 interfaces) between the application 615 and the accelerator 620. Additionally or alternatively, the application 615 may receive the context information from another entity or component of the DU 605.

[0235] Contextual information can be obtained through Figure 4 The P9 interface 435-c illustrated in FIG. 4 is exchanged between the accelerator 620 and the application 615, and may exhibit the format illustrated in the above Table 1. For example, as shown in Table 1, the context information may include, but is not limited to, an identifier associated with the accelerator 620 (e.g., PNF ID (QDU ID)), a carrier associated with the RU 610 (e.g., PHY ID), an identifier associated with the RU 610 (e.g., O-RU ID), a MAC identifier associated with the application 615 (e.g., application ID), and the like.

[0236] In addition, in some implementations, the context information may be associated with multiple carriers, multiple RUs 610, multiple applications 615, multiple accelerators, or any combination thereof. In other words, the context information may include or indicate a set of carriers associated with DMs used for communication between the accelerator 620 and the RU 610, a set of IDs associated with a set of RUs 610, a set of MAC IDs associated with a set of applications 615, or any combination thereof. The accelerator 620 may be configured to utilize the context information received at 630 to obtain (e.g., retrieve, receive, acquire) information associated with a DM (e.g., DM) hosted at the accelerator 620. qDU 425-b) associated configuration information.

[0237] At 635, the accelerator 620 may obtain or retrieve information related to the DM (eg, DM qDU 425 - b) Associated configuration information. For example, in some cases, the accelerator 620 may obtain the configuration information by retrieving the configuration information from a memory or cache at the accelerator 620 .

[0238] At 640, the accelerator 620 can provide (e.g., output, send) configuration information to the application 615. In some aspects, the configuration information can be communicated via one or more interfaces (e.g., P5, P19, P9, P10 interfaces) between the application 615 and the accelerator 620. In some aspects, the accelerator 620 can provide the configuration information to the application 615 at 640 based on obtaining / providing the exchange configuration at 625, obtaining the context information at 630, retrieving the configuration information at 635, or any combination thereof.

[0239] At 645, the application 615 may perform a validation procedure on the obtained configuration information, as described herein. The application 615 may perform a validation procedure to determine whether the received configuration information includes expected parameters or characteristics associated with the requested DM and / or the provided context information. In this regard, the application 615 may perform the validation procedure based on (e.g., using) the context information provided at 630.

[0240] At 650, application 615 may provide a message to accelerator 620 indicating the result (eg, verification pass / fail) of the verification procedure performed at 645. In other words, application 615 may indicate whether the received configuration information has been verified.

[0241] In the event of a validation failure, the application 615 can be configured to utilize one or more methods or implementations to obtain new or modified configuration information, as previously described herein. For example, the application 615 can be configured to modify one or more parameters of the configuration information (e.g., based on the exchange configuration), send additional (e.g., modified) context information to the accelerator 620 that can be used to obtain additional configuration information, etc.

[0242] At 655, the accelerator 620 may communicate with the RU 610 according to the configuration information. For example, in some cases, the accelerator 620 may configure one or more parameters at the RU 610 according to the configuration information.

[0243] Figure 7 A block diagram 700 of a device 705 supporting techniques for application and accelerator communication for a DU according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the network entity 105 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 or one or more components of the device 705 (e.g., the receiver 710, the transmitter 715, and the communication manager 720) may include at least one processor that may be coupled to at least one memory to support or implement the described techniques individually or collectively. Each of these components may communicate with each other (e.g., via one or more buses).

[0244] Receiver 710 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of device 705. In some examples, receiver 710 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 710 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0245] The transmitter 715 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 705. For example, the transmitter 715 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 715 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 715 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 715 and the receiver 710 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0246] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or various components thereof may be examples of components for performing various aspects of the techniques for application and accelerator communication for a DU as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or components thereof may be capable of performing one or more of the functions described herein.

[0247] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise individually or collectively supports components for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled to the at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in the at least one memory are executed by one or more processors individually or collectively).

[0248] Additionally or alternatively, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured to or otherwise individually or collectively support components for performing the functionality described in the present disclosure).

[0249] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0250] According to the examples disclosed herein, the communication manager 720 may support wireless communications at an application executable by a DU of the RAN. For example, the communication manager 720 is capable of, configured to, or operable to support a component for identifying context information, the context information comprising a first identifier associated with an accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with an RU associated with the DU, or any combination thereof. The communication manager 720 is capable of, configured to, or operable to support a component for exchanging messages with the accelerator based on the identified context information.

[0251] Additionally or alternatively, according to the examples disclosed herein, the communication manager 720 may support wireless communication at an accelerator associated with a DU of the RAN. For example, the communication manager 720 is capable of, configured to, or operable to support a component for identifying context information, the context information including a first identifier associated with the accelerator, a second identifier associated with an application of the DU, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with an RU associated with the DU, or any combination thereof. The communication manager 720 is capable of, configured to, or operable to support a component for exchanging messages with an application based on the identified context information. Additionally or alternatively, according to the examples disclosed herein, the communication manager 720 may support wireless communication at an application that can be executed by a DU of the RAN. For example, the communication manager 720 may be configured to or otherwise support a component for communicating a first message with an accelerator of the DU, the first message including context information associated with a data model hosted at the accelerator or the application. The communication manager 720 may be configured or otherwise support components for communicating a second message with the accelerator based on the context information, the second message including configuration information associated with the data model.

[0252] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communications at an accelerator associated with a DU of the RAN. For example, the communication manager 720 may be configured to or otherwise support a component for communicating a first message with an application executable by the DU, the first message including context information associated with a data model hosted at the accelerator or the application. The communication manager 720 may be configured to or otherwise support a component for communicating a second message with the application based on the context information, the second message including configuration information associated with the data model.

[0253] By including or configuring a communication manager 720 according to an example as described herein, the device 705 (e.g., a processor controlling the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof or otherwise coupled thereto) may support a technique for exchanging context information between an application of the DU and an accelerator, the context information enabling the respective components to perform read / write operations on a DM hosted at the respective components. The techniques described herein may enable the M-plane interface between the DU and the RU of the O-RAN network entity 105 to terminate at the application of the DU rather than at the accelerator of the DU. Specifically, the techniques of the present disclosure support signaling between the application of the DU and the accelerator, which enables the M-plane interface to terminate at the application. By enabling the M-plane interface to terminate at the application rather than at the accelerator, the techniques described herein may reduce or eliminate the need for the accelerator to relay the DM received from the RU to the application, thereby reducing the signaling and processing performed at the DU. Additionally, by enabling the M-plane interface to terminate at the application, the techniques described herein may reduce the amount of processing operations replicated across both the application and the accelerator, thereby reducing power consumption and complexity of the DU and O-RAN network entity 105.

[0254] Figure 8 A block diagram 800 of a device 805 supporting techniques for application and accelerator communication for a DU according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or the network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805, or one or more components of the device 805 (e.g., the receiver 810, the transmitter 815, and the communication manager 820) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0255] The receiver 810 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0256] The transmitter 815 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 805. For example, the transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 815 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 815 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0257] Device 805 or its various components may be examples of components for performing various aspects of the technology for application and accelerator communication for DU as described herein. For example, communication manager 820 may include context information manager 825, accelerator communication manager 830, application communication manager 835, or any combination thereof. Communication manager 820 may be an example of various aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 810, transmitter 815, or both. For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or integrate with receiver 810, transmitter 815, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0258] According to the examples disclosed herein, the communication manager 820 may support wireless communication at an application executable by a DU of the RAN. The context information manager 825 may be configured to support components for identifying context information, the context information including a first identifier associated with an accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with the RU associated with the DU, or any combination thereof. The accelerator communication manager 830 may be configured to support components for exchanging messages with the accelerator based on the identified context information.

[0259] Additionally or alternatively, according to the examples disclosed herein, the communication manager 820 may support wireless communication at an accelerator associated with a DU of the RAN. The context information manager 825 is capable of, configured to, or operable to support a component for identifying context information, the context information including a first identifier associated with the accelerator, a second identifier associated with an application of the DU, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with an RU associated with the DU, or any combination thereof. The application communication manager 835 is capable of, configured to, or operable to support a component for exchanging messages with an application based on the identified context information. Additionally or alternatively, according to the examples disclosed herein, the communication manager 820 may support wireless communication at an application that can be executed by a DU of the RAN. The accelerator communication manager 830 may be configured to or otherwise support a component for communicating a first message with an accelerator of the DU, the first message including context information associated with a data model hosted at the accelerator or the application. The accelerator communication manager 830 may be configured or otherwise support components for communicating a second message with the accelerator based on the context information, the second message including configuration information associated with the data model.

[0260] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at an accelerator associated with a DU of the RAN. The application communication manager 835 may be configured to or otherwise support components for communicating a first message with an application executable by the DU, the first message including context information associated with a data model hosted at the accelerator or the application. The application communication manager 835 may be configured to or otherwise support components for communicating a second message with the application based on the context information, the second message including configuration information associated with the data model.

[0261] Fig. 9A block diagram 900 of a communication manager 920 supporting technology for application and accelerator communication for DU according to one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of components for performing various aspects of the technology for application and accelerator communication for DU as described herein. For example, the communication manager 920 may include a context information manager 925, an accelerator communication manager 930, an application communication manager 935, a RU communication manager 940, a configuration information manager 945, a verification procedure manager 950, or any combination thereof. These components, or each of their components or subcomponents (e.g., one or more processors, one or more memories) may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0262] According to the examples disclosed herein, the communication manager 920 may support wireless communication at an application executable by a DU of the RAN. The context information manager 925 may be capable of, configured to, or operable to support components for identifying context information, the context information including a first identifier associated with an accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with the RU associated with the DU, or any combination thereof. The accelerator communication manager 930 may be capable of, configured to, or operable to support components for exchanging messages with the accelerator based on the identified context information.

[0263] In some examples, to support exchanging messages, the accelerator communication manager 930 can be, configured to, or operable to support components for providing context information to the accelerator. In some examples, to support exchanging messages, the accelerator communication manager 930 can be, configured to, or operable to support components for obtaining information associated with a data model hosted at the accelerator from the accelerator based on providing context information.

[0264] In some examples, to support exchanging messages, the accelerator communication manager 930 can be, configured to, or operable to support components for obtaining context information from the accelerator. In some examples, to support exchanging messages, the accelerator communication manager 930 can be, configured to, or operable to support components for providing information associated with a data model for communication between the accelerator and the RU associated with the DU to the accelerator based on obtaining context information.

[0265] In some examples, the RU communication manager 940 is capable of, configured to, or operable to support components for providing a request for information to the RU via an interface between the application and the RU. In some examples, the RU communication manager 940 is capable of, configured to, or operable to support components for obtaining information from the RU via an interface and in response to a request. In some examples, the information obtained from the RU is further delivered to the accelerator via a second interface between the application and the accelerator.

[0266] In some examples, the accelerator communication manager 930 is capable, configured, or operable to support components for obtaining a first message from the accelerator based on providing the information, the first message indicating a result of a validation procedure associated with the information.

[0267] In some examples, the first message indicates a failure of the verification procedure, and the accelerator communication manager 930 is capable, configured, or operable to support a component for providing a second message to the accelerator in response to the failure, the second message instructing the accelerator to convey additional information about the failure associated with the context information. In some examples, the first message indicates a failure of the verification procedure, and the accelerator communication manager 930 is capable, configured, or operable to support a component for obtaining a third message from the accelerator in response to the second message, the third message including additional information associated with the context information for communication between the accelerator and the RU.

[0268] In some examples, the configuration information manager 945 can be configured to or operable to support a component for obtaining second additional information for a second data model based on the additional information. In some examples, the accelerator communication manager 930 can be configured to or operable to support a component for providing a fourth message to the accelerator, the fourth message conveying the second additional information.

[0269] In some examples, the first message indicates a failure of a validation procedure, and the accelerator communication manager 930 is capable, configured, or operable to support components for providing a second message to the accelerator based on the failure, the second message identifying additional information for the second data model, wherein the additional information includes a modified version of the information.

[0270] In some examples, the first message indicates a failure of the validation procedure, and the accelerator communication manager 930 is capable, configured, or operable to support components for obtaining an indication of additional information for the second data model from the accelerator based on the failure, the additional information being used to generate a modified version of the information.

[0271] In some examples, the profile instance associated with the accelerator is associated with a carrier, a physical context, a baseband context associated with the accelerator, or any combination thereof. In some examples, the context information also includes an indication of an applicable antenna panel associated with one or more transmit-receive points. In some examples, the first identifier corresponds to at least two profile instances in the set of multiple profile instances.

[0272] In some examples, the context information includes a first set of multiple identifiers associated with a set of multiple profile instances associated with an accelerator, a second set of multiple identifiers associated with a set of multiple RUs including RUs, a third set of multiple identifiers associated with a set of multiple applications including applications, or any combination thereof.

[0273] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at an accelerator associated with a DU of the RAN. In some examples, the context information manager 925 is capable of, configured to, or operable to support components for identifying context information, the context information comprising a first identifier associated with the accelerator, a second identifier associated with an application of the DU, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with the RU associated with the DU, or any combination thereof. The application communication manager 935 is capable of, configured to, or operable to support components for exchanging messages with an application based on the identified context information.

[0274] In some examples, to support exchanging messages, the application communication manager 935 can be, configured, or operable to support components for obtaining context information from the application. In some examples, to support exchanging messages, the application communication manager 935 can be, configured, or operable to support components for providing information associated with a data model hosted at the accelerator to the application based on obtaining context information.

[0275] In some examples, to support exchanging messages, the application communication manager 935 can be, configured, or operable to support components for providing context information to the application. In some examples, to support exchanging messages, the application communication manager 935 can be, configured, or operable to support components for obtaining information associated with a data model for communication between an accelerator and a RU associated with the DU from the application based on providing context information.

[0276] In some examples, the application communication manager 935 is capable, configured, or operable to support components for providing a first message to the application indicating a result of a validation procedure associated with the information based on obtaining the information.

[0277] In some examples, the first message indicates a failure of the verification procedure, and the application communication manager 935 is capable, configured, or operable to support a component for obtaining a second message from the application in response to the failure, the second message indicating that the accelerator conveys additional information about the failure associated with the context information. In some examples, the first message indicates a failure of the verification procedure, and the application communication manager 935 is capable, configured, or operable to support a component for providing a third message to the application in response to the second message, the third message including additional information associated with the context information for communication between the accelerator and the RU.

[0278] In some examples, configuration information manager 945 is capable, configured, or operable to support means for obtaining, in response to the failure, a fourth message from the application, the fourth message including second additional information for the second data model.

[0279] In some examples, the configuration information manager 945 is capable, configured, or operable to support components for obtaining a first message from an application, the first message including information related to the second data model. In some examples, the validation procedure manager 950 is capable, configured, or operable to support components for determining a failure of a validation procedure associated with the information. In some examples, the application communication manager 935 is capable, configured, or operable to support components for providing a second message to the application based on the failure, the second message indicating third information, wherein the third information is associated with a modified version of the information.

[0280] In some examples, the profile instance associated with the accelerator is associated with a carrier, a physical context, a baseband context associated with the accelerator, or any combination thereof. In some examples, the context information also includes an indication of an applicable antenna panel associated with one or more transmit-receive points associated with the DU. In some examples, the first identifier corresponds to at least two profile instances in the set of multiple profile instances.

[0281] In some examples, the context information includes a first set of multiple identifiers associated with a set of multiple profile instances associated with an accelerator, a second set of multiple identifiers associated with a set of multiple RUs including RUs, a third set of multiple identifiers associated with a set of multiple applications including applications, or any combination thereof.

[0282] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at an application executable by a DU of the RAN. In some examples, the accelerator communication manager 930 may be configured to or otherwise support a component for communicating a first message with an accelerator of the DU, the first message including context information associated with a data model hosted at the accelerator or the application. In some examples, the accelerator communication manager 930 may be configured to or otherwise support a component for communicating a second message with the accelerator based on the context information, the second message including configuration information associated with the data model.

[0283] In some examples, the context information includes a first identifier associated with the accelerator, a second identifier associated with the RU, a third identifier associated with a profile instance associated with the accelerator, or a fourth identifier associated with the application.

[0284] In some examples, the accelerator is associated with a set of a plurality of configuration file instances including the configuration file instance. In some examples, the first identifier corresponds to at least two configuration file instances in the set of a plurality of configuration file instances.

[0285] In some examples, the context information includes a set of multiple identifiers associated with a set of multiple configuration file instances associated with the accelerator, a set of multiple identifiers associated with a set of multiple RUs including RUs, a set of multiple identifiers associated with a set of multiple applications including applications, or any combination thereof. In some examples, the configuration information is associated with a set of multiple configuration file instances, a set of multiple RUs, a set of multiple applications, or any combination thereof.

[0286] In some examples, the accelerator communication manager 930 may be configured or otherwise support components for obtaining a third message from the accelerator based on providing the second message, the third message indicating a result of a validation procedure associated with the configuration information.

[0287] In some examples, the third message indicates the failure of the verification procedure, and the accelerator communication manager 930 may be configured to or otherwise support a component for providing a fourth message to the accelerator in response to the failure, the fourth message indicating that the accelerator modifies the context information. In some examples, the third message indicates the failure of the verification procedure, and the accelerator communication manager 930 may be configured to or otherwise support a component for obtaining a fifth message from the accelerator in response to the fourth message, the fifth message including additional context information for communication between the accelerator and the RU. In some examples, the third message indicates the failure of the verification procedure, and the configuration information manager 945 may be configured to or otherwise support a component for obtaining additional configuration information for the second data model based on the additional context information. In some examples, the third message indicates the failure of the verification procedure, and the accelerator communication manager 930 may be configured to or otherwise support a component for providing a sixth message to the accelerator, the sixth message identifying additional configuration information.

[0288] In some examples, the third message indicates a failure of the validation procedure, and the accelerator communication manager 930 may be configured to or otherwise support components for providing a fourth message to the accelerator based on the failure, the fourth message identifying additional configuration information for the second data model, wherein the additional configuration information includes a modified version of the configuration information.

[0289] In some examples, the third message indicates a failure of the validation procedure, and the accelerator communication manager 930 may be configured to or otherwise support components for obtaining an indication of additional configuration information for the second data model from the accelerator based on the failure, wherein the additional configuration information includes a modified version of the configuration information.

[0290] In some examples, the first message is obtained from the accelerator via an interface between the application and the accelerator.

[0291] In some examples, the accelerator communication manager 930 may be configured to or otherwise support components for communicating an exchange configuration with the accelerator for exchanging information associated with a data model between the application and the accelerator, wherein communicating the first message, communicating the second message, or both are based on the exchange configuration.

[0292] In some examples, an exchange configuration includes one or more rules, one or more conditions, or both for modifying a data model.

[0293] In some examples, the RU communication manager 940 may be configured as or otherwise support a component for providing a request for configuration information to the RU via an interface between the application and the RU and based on the context information. In some examples, the RU communication manager 940 may be configured as or otherwise support a component for obtaining configuration information from the RU via an interface between the application and the RU and based on the request, wherein communicating the second message is based on the obtaining.

[0294] In some examples, the RU communication manager 940 may be configured as or otherwise support components for obtaining additional configuration information associated with a data model for communication between the accelerator and the RU from the RU via an interface between the application and the RU. In some examples, the RU communication manager 940 may be configured as or otherwise support components for providing a third message to the RU indicating a failure of a verification procedure associated with the additional configuration information and performed at the application, wherein the configuration information is obtained from the RU based on the third message.

[0295] In some examples, configuration information manager 945 may be configured or otherwise support means for obtaining configuration information via a cache maintained at the application, wherein communicating the second message is based on the obtaining.

[0296] In some examples, the configuration information includes capabilities associated with the RU, a set of parameters associated with communications performed by the RU, or a state associated with processing of the first message, or any combination thereof.

[0297] In some examples, the accelerator communication manager 930 may be configured to or otherwise support a component for providing a first message including context information to the accelerator. In some examples, the accelerator communication manager 930 may be configured to or otherwise support a component for obtaining a second message from the accelerator based on providing the first message, wherein the data model is hosted at the accelerator.

[0298] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at an accelerator associated with a DU of the RAN. In some examples, the application communication manager 935 may be configured to or otherwise support components for communicating a first message with an application executable by the DU, the first message including context information associated with a data model hosted at the accelerator or the application. In some examples, the application communication manager 935 may be configured to or otherwise support components for communicating a second message with the application based on the context information, the second message including configuration information associated with the data model.

[0299] In some examples, the context information includes a first identifier associated with the accelerator, a second identifier associated with the RU, a third identifier associated with a profile instance associated with the accelerator, or a fourth identifier associated with the application.

[0300] In some examples, the accelerator is associated with a set of a plurality of configuration file instances including the configuration file instance. In some examples, the first identifier corresponds to at least two configuration file instances in the set of a plurality of configuration file instances.

[0301] In some examples, the context information includes a set of multiple identifiers associated with a set of multiple configuration file instances associated with the accelerator, a set of multiple identifiers associated with a set of multiple RUs including RUs, a set of multiple identifiers associated with a set of multiple applications including applications, or any combination thereof. In some examples, the configuration information is associated with a set of multiple configuration file instances, a set of multiple RUs, a set of multiple applications, or any combination thereof.

[0302] In some examples, application communications manager 935 may be configured or otherwise support components for providing a third message to the application based on obtaining the second message, the third message indicating a result of a validation procedure associated with the configuration information.

[0303] In some examples, the application communication manager 935 may be configured to or otherwise support a component for obtaining a third message from the application, the third message including additional configuration information for the second data model. In some examples, the application communication manager 935 may be configured to or otherwise support a component for providing a fourth message to the application based on obtaining the third message, the fourth message indicating the failure of the verification procedure associated with the additional configuration information. In some examples, the application communication manager 935 may be configured to or otherwise support a component for obtaining a fifth message from the application in response to a failure, the fifth message indicating that the accelerator modifies the context information. In some examples, the application communication manager 935 may be configured to or otherwise support a component for providing a sixth message to the application in response to the fifth message, the sixth message including additional context information for communication between the accelerator and the RU, wherein obtaining the second message including the configuration information is based on the sixth message.

[0304] In some examples, the configuration information manager 945 may be configured or otherwise support a component for obtaining a third message from the application, the third message including additional configuration information for the second data model. In some examples, the application communication manager 935 may be configured or otherwise support a component for providing a fourth message to the application based on obtaining the third message, the fourth message indicating a failure of a verification procedure associated with the additional configuration information, wherein the second message including the configuration information is obtained based on the fourth message, and wherein the configuration information includes a modified version of the additional configuration information.

[0305] In some examples, the configuration information manager 945 may be configured or otherwise support components for obtaining a third message from the application, the third message including additional configuration information for the second data model. In some examples, the validation procedure manager 950 may be configured or otherwise support components for determining a failure of a validation procedure associated with the additional configuration information. In some examples, the application communication manager 935 may be configured or otherwise support components for providing a fourth message to the application based on the failure, the fourth message indicating configuration information, wherein the configuration information includes a modified version of the additional configuration information.

[0306] In some examples, the first message is provided to the application via an interface between the application and the accelerator.

[0307] In some examples, the application communication manager 935 may be configured as or otherwise support components for communicating an exchange configuration with an application, the exchange configuration being used to exchange information associated with a data model between the application and the accelerator, wherein providing a first message, obtaining a second message, or both is based on the exchange configuration.

[0308] In some examples, an exchange configuration includes one or more rules, one or more conditions, or both for modifying a data model.

[0309] In some examples, the configuration information includes capabilities associated with the RU, a set of parameters associated with communications performed by the RU, a state associated with processing of the first message, or any combination thereof.

[0310] In some examples, the application communication manager 935 may be configured to or otherwise support a component for providing a first message including context information to the application. In some examples, the application communication manager 935 may be configured to or otherwise support a component for obtaining a second message including configuration information from the application, wherein the data model is associated with communication between the accelerator and the RU coupled to the DU. In some examples, the RU communication manager 940 may be configured to or otherwise support a component for communicating with the RU based on the configuration information.

[0311] In some examples, communication with the RU is performed via a physical layer interface between the accelerator and the RU.

[0312] In some examples, the application communication manager 935 may be configured or otherwise support a component for obtaining a first message including context information from an application. In some examples, the application communication manager 935 may be configured or otherwise support a component for providing a second message to an application based on obtaining the first message, wherein the data model is hosted at the accelerator.

[0313] Fig.10 A diagram of a system 1000 including a device 1005 supporting technology for application and accelerator communication for a DU according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a network entity 105 as described herein, or include components of these devices. The device 1005 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1005 may include components that support output and acquisition of communications, such as a communication manager 1020, a transceiver 1010, an antenna 1015, a memory 1025, a code 1030, and a processor 1035. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1040).

[0314] The transceiver 1010 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1010 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1010 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1005 may include one or more antennas 1015, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1010 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1015, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1015, from a wired receiver), and for demodulating a signal. In some implementations, the transceiver 1010 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1015 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1015 configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1010 may include or be configured to be coupled to one or more processors or memory components, which are operable to: perform or support operations based on received or obtained information or signals; or generate information or other signals for transmission or other output; or any combination thereof. In some implementations, the transceiver 1010, or the transceiver 1010 and one or more antennas 1015, or the transceiver 1010 and one or more antennas 1015 and one or more processors or memory components (e.g., processor 1035, or memory 1025, or both) may be included in a chip or chip assembly installed in the device 1005. Where applicable, transceiver 1010 or transceiver 1010 and one or more antennas 1015 or wired interfaces may be examples of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or any components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0315] The memory 1025 may include RAM and ROM. The memory 1025 may store computer-readable, computer-executable code 1030 including instructions that, when executed by the processor 1035, cause the device 1005 to perform various functions described herein. The code 1030 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1030 may not be directly executable by the processor 1035, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1025 may include a BIOS, etc., which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0316] Processor 1035 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, ASIC, CPU, FPGA, microcontroller, programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1035 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1035. Processor 1035 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1025) to enable device 1005 to perform various functions (e.g., functions or tasks of technologies supporting applications and accelerator communications for DU). For example, device 1005 or a component of device 1005 may include processor 1035 and memory 1025 coupled to processor 1035, and processor 1035 and memory 1025 are configured to perform various functions described herein. Processor 1035 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions (e.g., by executing code 1030) to perform functions of device 1005. The processor 1035 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1005 (such as in the memory 1025). In some specific implementations, the processor 1035 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce an output set (which may be passed to other systems or components of the device 1005, for example). For example, the processing system of the device 1005 may refer to a system including various other components or subcomponents of the device 1005, such as the processor 1035, or the transceiver 1010, or the communication manager 1020, or other components or combinations of components of the device 1005. The processing system of the device 1005 may interface with other components of the device 1005, and may process information (such as input or signals) received from other components, or output information to other components. For example, a chip or modem of the device 1005 may include a processing system and an interface for outputting information or for obtaining information or both. The interface may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information. In some implementations, the first interface may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1005 can send information output from the chip or modem. In some implementations, the second interface may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1005 can obtain information or signal input, and the information can be passed to the processing system. Those of ordinary skill in the art will readily appreciate that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0317] In some examples, bus 1040 may support communications of a protocol layer of a protocol stack (e.g., within the protocol layer). In some examples, bus 1040 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communications performed within a component of device 1005 or between different components of device 1005 that may be co-located or located in different locations (e.g., where device 1005 may refer to a system where one or more of communication manager 1020, transceiver 1010, memory 1025, code 1030, and processor 1035 may be located in one of the different components or divided between the different components).

[0318] In some examples, the communication manager 1020 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1020 may manage the delivery of data communications for client devices such as one or more UEs 115. In some examples, the communication manager 1020 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UEs 115 in coordination with the other network entities 105. In some examples, the communication manager 1020 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0319] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at an application executable by a DU of the RAN. For example, the communication manager 1020 may be configured to or otherwise support a component for identifying context information, the context information comprising a first identifier associated with an accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with the RU associated with the DU, or any combination thereof. The communication manager 1020 is capable of, configured to, or operable to support a component for exchanging messages with the accelerator based on the identified context information.

[0320] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at an accelerator associated with a DU of the RAN. For example, the communication manager 1020 may be configured to or otherwise support a component for identifying context information, the context information comprising a first identifier associated with the accelerator, a second identifier associated with an application of the DU, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof. The communication manager 1020 is capable of, configured to, or operable to support a component for exchanging messages with the application based on the identified context information.

[0321] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at an application executable by a DU of the RAN. For example, the communication manager 1020 may be configured to or otherwise support a component for communicating a first message with an accelerator of the DU, the first message including context information associated with a data model hosted at the accelerator or the application. The communication manager 1020 may be configured to or otherwise support a component for communicating a second message with the accelerator based on the context information, the second message including configuration information associated with the data model.

[0322] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at an accelerator associated with a DU of the RAN. For example, the communication manager 1020 may be configured to or otherwise support a component for communicating a first message with an application executable by the DU, the first message including context information associated with a data model hosted at the accelerator or the application. The communication manager 1020 may be configured to or otherwise support a component for communicating a second message with the application based on the context information, the second message including configuration information associated with the data model.

[0323] By including or configuring a communication manager 1020 according to an example as described herein, the device 1005 may support a technique for exchanging context information between an application of a DU and an accelerator, the context information enabling the corresponding component to perform read / write operations on a DM hosted at the corresponding component. The techniques described herein may enable the M-plane interface between the DU and the RU of the O-RAN network entity 105 to terminate at the application of the DU, rather than at the accelerator of the DU. Specifically, the techniques disclosed herein support signaling between the application of the DU and the accelerator, which enables the M-plane interface to terminate at the application. By enabling the M-plane interface to terminate at the application, rather than at the accelerator, the techniques described herein may reduce or eliminate the need for the accelerator to relay the DM received from the RU to the application, thereby reducing the signaling and processing performed at the DU. Additionally, by enabling the M-plane interface to terminate at the application, the techniques described herein may reduce the amount of processing operations replicated across both the application and the accelerator, thereby reducing the power consumption and complexity of the DU and the O-RAN network entity 105.

[0324] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1010, one or more antennas 1015 (e.g., where applicable), or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1035, the memory 1025, the code 1030, the transceiver 1010, or any combination thereof. For example, the code 1030 may include instructions that are executable by the processor 1035 to cause the device 1005 to perform various aspects of the techniques for application and accelerator communications for the DU as described herein, or the processor 1035 and the memory 1025 may be otherwise configured to perform or support such operations.

[0325] Fig.11 1 is a flowchart illustrating a method 1100 of supporting techniques for communication between an application and an accelerator for a DU according to one or more aspects of the present disclosure. The operations of the method 1100 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1100 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 10 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0326] At 1105, the method may include identifying context information including a first identifier associated with an accelerator of the DU, a second identifier associated with an application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof. The operations of block 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of block 1105 may be performed as described in reference to Fig. 9 The described context information manager 925 is executed.

[0327] At 1110, the method may include exchanging messages with the accelerator based on the identified context information. The operations of block 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of block 1110 may be performed as described in reference to Fig. 9 The accelerator communication manager 930 described above is executed.

[0328] Fig.12 1 is a flowchart illustrating a method 1200 of supporting techniques for communication between an application and an accelerator for a DU according to one or more aspects of the present disclosure. The operations of the method 1200 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 10 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0329] At 1205, the method may include identifying context information including a first identifier associated with the accelerator, a second identifier associated with the application of the DU, a third identifier associated with the profile instance associated with the accelerator, a fourth identifier associated with the RU associated with the DU, or any combination thereof. The operations of block 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of block 1205 may be performed as described in reference to Fig. 9 The described context information manager 925 is executed.

[0330] At 1210, the method may include exchanging messages with the application based on the identified context information. The operations of block 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Fig. 9 The described application communication manager 935 is executed.

[0331] Fig.131300 is a flowchart illustrating a method 1300 for supporting technology for communication between an application and an accelerator for a DU according to one or more aspects of the present disclosure. The operations of the method 1300 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 10 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0332] At 1305, the method may include communicating a first message with an accelerator of the DU, the first message including context information associated with a data model hosted at the accelerator or the application. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Fig. 9 The accelerator communication manager 930 described above is executed.

[0333] At 1310, the method may include communicating a second message with the accelerator based on the context information, the second message including configuration information associated with the data model. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Fig. 9 The accelerator communication manager 930 described above is executed.

[0334] Fig.14 1400 is a flowchart illustrating a method 1400 of supporting techniques for communication between an application and an accelerator for a DU according to one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 10 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0335] At 1405, the method may include communicating a first message with an application executable by the DU, the first message including context information associated with a data model hosted at the accelerator or the application. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference Fig. 9 The described application communication manager 935 is executed.

[0336] At 1410, the method may include communicating a second message with the application based on the context information, the second message including configuration information associated with the data model. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Fig. 9 The described application communication manager 935 is executed.

[0337] The following provides an overview of various aspects of the disclosure:

[0338] Aspect 1: A method for wireless communication at an application capable of being executed by a DU of a RAN, the method comprising: identifying context information, the context information comprising a first identifier associated with an accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and exchanging messages with the accelerator based at least in part on the identified context information.

[0339] Aspect 2: The method according to aspect 1, wherein exchanging the message further comprises: providing the context information to the accelerator; and obtaining, from the accelerator, information associated with the DM hosted at the accelerator based at least in part on providing the context information.

[0340] Aspect 3: A method according to any one of Aspects 1 to 2, wherein exchanging the message further comprises: obtaining the context information from the accelerator; and providing to the accelerator information associated with a DM used for communication between the accelerator and the RU associated with the DU based at least in part on obtaining the context information.

[0341] Aspect 4: According to the method described in Aspect 3, the method also includes: providing a request for the information to the RU via an interface between the application and the RU; and obtaining the information from the RU via the interface and in response to the request, wherein the information obtained from the RU is further transmitted to the accelerator via a second interface between the application and the accelerator.

[0342] Aspect 5: The method according to any one of aspects 3 to 4, further comprising: obtaining a first message from the accelerator based at least in part on providing the information, the first message indicating a result of a verification procedure associated with the information.

[0343] Aspect 6: A method according to Aspect 5, wherein the first message indicates a failure of the verification procedure, the method further comprising: providing a second message to the accelerator in response to the failure, the second message instructing the accelerator to transmit additional information about the failure associated with the context information; and obtaining a third message from the accelerator in response to the second message, the third message including the additional information associated with the context information used for the communication between the accelerator and the RU.

[0344] Aspect 7: The method according to aspect 6, further comprising: obtaining second additional information for a second DM based at least in part on the additional information; and providing a fourth message to the accelerator, the fourth message conveying the second additional information.

[0345] Aspect 8: A method according to Aspect 5, wherein the first message indicates a failure of the verification procedure, and the method further comprises: providing a second message to the accelerator based at least in part on the failure, the second message identifying additional information for a second DM, wherein the additional information comprises a modified version of the information.

[0346] Aspect 9: A method according to any one of Aspects 5 to 7, wherein the first message indicates a failure of the verification procedure, and the method further includes: obtaining an indication of additional information for a second DM from the accelerator based at least in part on the failure, the additional information being used to generate a modified version of the information.

[0347] Aspect 10: The method according to any one of aspects 1 to 9, wherein the profile instance associated with the accelerator is associated with a carrier, a physical context, a baseband context associated with the accelerator, or any combination thereof.

[0348] Aspect 11: The method according to any one of aspects 1 to 10, wherein the context information further comprises an indication of applicable antenna panels associated with one or more transmit-receive points.

[0349] Aspect 12: The method according to any one of aspects 1 to 11, wherein the first identifier corresponds to at least two configuration file instances among a plurality of configuration file instances.

[0350] Aspect 13: A method according to any one of Aspects 1 to 12, wherein the context information includes a first plurality of identifiers associated with multiple profile instances associated with the accelerator, a second plurality of identifiers associated with multiple RUs including the RU, a third plurality of identifiers associated with multiple applications including the application, or any combination thereof.

[0351] Aspect 14: A method for wireless communication at an accelerator associated with a DU of a RAN, the method comprising: identifying context information, the context information comprising a first identifier associated with the accelerator of the DU, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a RU associated with the DU, or any combination thereof; and exchanging messages with the application based at least in part on the identified context information.

[0352] Aspect 15: The method according to aspect 14, wherein exchanging the message further comprises: obtaining the context information from the application; and providing information associated with the DM hosted at the accelerator to the application based at least in part on obtaining the context information.

[0353] Aspect 16: A method according to any one of Aspects 14 to 15, wherein exchanging the message further comprises: providing the context information to the application; and obtaining from the application information associated with the DM used for communication between the accelerator and the RU associated with the DU based at least in part on providing the context information.

[0354] Aspect 17: The method of aspect 16, further comprising: providing a first message to the application based at least in part on obtaining the information, the first message indicating a result of a validation procedure associated with the information.

[0355] Aspect 18: A method according to Aspect 17, wherein the first message indicates a failure of the verification procedure, the method further comprising: obtaining a second message from the application in response to the failure, the second message instructing the accelerator to transmit additional information about the failure associated with the context information; and providing a third message to the application in response to the second message, the third message including the additional information associated with the context information used for communication between the accelerator and the RU.

[0356] Aspect 19: The method according to Aspect 18, further comprising: obtaining a fourth message from the application in response to the failure, the fourth message comprising second additional information for the second DM.

[0357] Aspect 20: According to the method described in any one of Aspects 14 to 16, the method also includes: obtaining a first message from the application, the first message including information related to the second DM; determining the failure of the verification procedure associated with the information; and providing a second message to the application based at least in part on the failure, the second message indicating third information, wherein the third information is associated with a modified version of the information.

[0358] Aspect 21: The method according to any one of aspects 14 to 20, wherein the profile instance associated with the accelerator is associated with a carrier, a physical context, a baseband context associated with the accelerator, or any combination thereof.

[0359] Aspect 22: The method according to any one of aspects 14 to 21, wherein the context information further comprises an indication of applicable antenna panels associated with one or more transmit-receive points associated with the DU.

[0360] Aspect 23: The method according to any one of aspects 14 to 22, wherein the first identifier corresponds to at least two configuration file instances among a plurality of configuration file instances.

[0361] Aspect 24: A method according to any one of Aspects 14 to 23, wherein the context information includes a first plurality of identifiers associated with multiple profile instances associated with the accelerator, a second plurality of identifiers associated with multiple RUs including the RU, a third plurality of identifiers associated with multiple applications including the application, or any combination thereof.

[0362] Aspect 25: An apparatus for wireless communication at an application capable of being executed by a DU of a RAN, the apparatus comprising: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of Aspects 1 to 13.

[0363] Aspect 26: An apparatus for wireless communication at an application executable by a DU of a RAN, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 13.

[0364] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication at an application executable by a DU of a RAN, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 13.

[0365] Aspect 28: An apparatus for wireless communication at an accelerator associated with a DU of a RAN, the apparatus comprising: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform a method according to any one of Aspects 14 to 24.

[0366] Aspect 29: An apparatus for wireless communication at an accelerator associated with a DU of a RAN, the apparatus comprising at least one component for performing the method according to any one of aspects 14 to 24.

[0367] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication at an accelerator associated with a DU of a RAN, the code comprising instructions executable by a processor to perform the method according to any one of aspects 14 to 24.

[0368] Aspect 31: A method for wireless communication at an application capable of being executed by a DU of a RAN, the method comprising: communicating a first message with an accelerator of the DU, the first message comprising context information associated with a DM hosted at the accelerator or the application; and communicating a second message with the accelerator based at least in part on the context information, the second message comprising configuration information associated with the DM.

[0369] Aspect 32: A method according to Aspect 31, wherein the context information includes a first identifier associated with the accelerator, a second identifier associated with the RU, a third identifier associated with a profile instance associated with the accelerator, or a fourth identifier associated with the application.

[0370] Aspect 33: The method according to aspect 32, wherein the accelerator is associated with a plurality of configuration file instances including the configuration file instance, and the first identifier corresponds to at least two configuration file instances of the plurality of configuration file instances.

[0371] Aspect 34: A method according to any one of Aspects 31 to 33, wherein the context information includes multiple identifiers associated with multiple configuration file instances associated with the accelerator, multiple identifiers associated with multiple RUs including the RU, multiple identifiers associated with multiple applications including the application, or any combination thereof, and the configuration information is associated with the multiple configuration file instances, the multiple RUs, the multiple applications, or any combination thereof.

[0372] Aspect 35: The method according to any one of Aspects 31 to 34, further comprising: obtaining a third message from the accelerator based at least in part on providing the second message, the third message indicating a result of a verification procedure associated with the configuration information.

[0373] Aspect 36: A method according to Aspect 35, wherein the third message indicates a failure of the verification procedure, the method further comprising: providing a fourth message to the accelerator in response to the failure, the fourth message instructing the accelerator to modify the context information; obtaining a fifth message from the accelerator in response to the fourth message, the fifth message including additional context information for the communication between the accelerator and the RU; obtaining additional configuration information for a second DM based at least in part on the additional context information; and providing a sixth message to the accelerator, the sixth message identifying the additional configuration information.

[0374] Aspect 37: A method according to any one of Aspects 35 to 36, wherein the third message indicates a failure of the verification procedure, and the method further includes: providing a fourth message to the accelerator based at least in part on the failure, wherein the fourth message identifies additional configuration information for the second DM, wherein the additional configuration information includes a modified version of the configuration information.

[0375] Aspect 38: A method according to any one of Aspects 35 to 37, wherein the third message indicates a failure of the verification procedure, and the method further includes: obtaining an indication of additional configuration information for a second DM from the accelerator based at least in part on the failure, wherein the additional configuration information includes a modified version of the configuration information.

[0376] Aspect 39: The method according to any one of Aspects 31 to 38, wherein the first message is obtained from the accelerator via an interface between the application and the accelerator.

[0377] Aspect 40: According to the method described in any one of Aspects 31 to 39, the method further includes: communicating an exchange configuration with the accelerator, the exchange configuration being used to exchange information associated with the DM between the application and the accelerator, wherein communicating the first message, communicating the second message, or both are at least partially based on the exchange configuration.

[0378] Aspect 41: The method according to aspect 40, wherein the exchange configuration includes one or more rules, one or more conditions, or both for modifying the DM.

[0379] Aspect 42: According to the method described in any one of Aspects 31 to 41, the method further includes: providing a request for the configuration information to the RU via an interface between the application and the RU and at least partially based on the context information; and obtaining the configuration information from the RU via the interface between the application and the RU and at least partially based on the request, wherein communicating the second message is at least partially based on the obtaining.

[0380] Aspect 43: According to the method described in any one of Aspects 31 to 42, the method further includes: obtaining additional configuration information associated with the DM used for communication between the accelerator and the RU from the RU via an interface between the application and the RU; and providing a third message to the RU, the third message indicating a failure of a verification procedure associated with the additional configuration information and performed at the application, wherein the configuration information is obtained from the RU at least in part based on the third message.

[0381] Aspect 44: The method according to any one of Aspects 31 to 43, the method further comprising: obtaining the configuration information via a cache maintained at the application, wherein communicating the second message is based at least in part on the obtaining.

[0382] Aspect 45: A method according to any one of Aspects 31 to 44, wherein the configuration information includes capabilities associated with the RU, a set of parameters associated with communications performed by the RU, or a state associated with processing of the first message, or any combination thereof.

[0383] Aspect 46: According to any one of Aspects 31 to 45, the method also includes: providing the first message including the context information to the accelerator; and obtaining the second message from the accelerator based at least in part on providing the first message, wherein the DM is hosted at the accelerator.

[0384] Aspect 47: A method for wireless communication at an accelerator associated with a DU of a RAN, the method comprising: communicating a first message with an application executable by the DU, the first message comprising context information associated with a DM hosted at the accelerator or the application; and communicating a second message with the application based at least in part on the context information, the second message comprising configuration information associated with the DM.

[0385] Aspect 48: A method according to Aspect 47, wherein the context information includes a first identifier associated with the accelerator, a second identifier associated with the RU, a third identifier associated with a profile instance associated with the accelerator, or a fourth identifier associated with the application.

[0386] Aspect 49: The method according to Aspect 48, wherein the accelerator is associated with a plurality of configuration file instances including the configuration file instance, and the first identifier corresponds to at least two configuration file instances of the plurality of configuration file instances.

[0387] Aspect 50: A method according to any one of Aspects 47 to 49, wherein the context information includes multiple identifiers associated with multiple configuration file instances associated with the accelerator, multiple identifiers associated with multiple RUs including the RU, multiple identifiers associated with multiple applications including the application, or any combination thereof, and the configuration information is associated with the multiple configuration file instances, the multiple RUs, the multiple applications, or any combination thereof.

[0388] Aspect 51: According to any one of aspects 47 to 50, the method further includes: providing a third message to the application based at least in part on obtaining the second message, the third message indicating a result of a verification procedure associated with the configuration information.

[0389] Aspect 52: According to the method described in any one of Aspects 47 to 51, the method further includes: obtaining a third message from the application, the third message including additional configuration information for the second DM; providing a fourth message to the application based at least in part on obtaining the third message, the fourth message indicating a failure of a verification procedure associated with the additional configuration information; obtaining a fifth message from the application in response to the failure, the fifth message instructing the accelerator to modify the context information; and providing a sixth message to the application in response to the fifth message, the sixth message including additional context information for the communication between the accelerator and the RU, wherein obtaining the second message including the configuration information is based at least in part on the sixth message.

[0390] Aspect 53: According to the method described in any one of Aspects 47 to 52, the method also includes: obtaining a third message from the application, the third message including additional configuration information for the second DM; and providing a fourth message to the application based at least in part on obtaining the third message, the fourth message indicating the failure of a verification procedure associated with the additional configuration information, wherein the second message including the configuration information is obtained at least in part based on the fourth message, and wherein the configuration information includes a modified version of the additional configuration information.

[0391] Aspect 54: According to the method described in any one of Aspects 47 to 53, the method also includes: obtaining a third message from the application, the third message including additional configuration information for the second DM; determining the failure of the verification procedure associated with the additional configuration information; and providing a fourth message to the application based at least in part on the failure, the fourth message indicating the configuration information, wherein the configuration information includes a modified version of the additional configuration information.

[0392] Aspect 55: The method according to any one of Aspects 47 to 54, wherein the first message is provided to the application via an interface between the application and the accelerator.

[0393] Aspect 56: According to the method described in any one of Aspects 47 to 55, the method further includes: communicating an exchange configuration with the application, the exchange configuration being used to exchange information associated with the DM between the application and the accelerator, wherein providing the first message, obtaining the second message, or both is based at least in part on the exchange configuration.

[0394] Aspect 57: The method according to aspect 56, wherein the exchange configuration includes one or more rules, one or more conditions, or both for modifying the DM.

[0395] Aspect 58: A method according to any one of Aspects 47 to 57, wherein the configuration information includes capabilities associated with the RU, a set of parameters associated with communications performed by the RU, a state associated with processing of the first message, or any combination thereof.

[0396] Aspect 59: According to the method described in any one of Aspects 47 to 58, the method further includes: providing the first message including the context information to the application; obtaining the second message including the configuration information from the application, wherein the DM is associated with communication between the accelerator and the RU coupled to the DU; and communicating with the RU according to the configuration information.

[0397] Aspect 60: The method according to Aspect 59, wherein the communication with the RU is performed via a physical layer interface between the accelerator and the RU.

[0398] Aspect 61: According to the method described in any one of Aspects 47 to 60, the method also includes: obtaining the first message including the context information from the application; and providing the second message to the application based at least in part on obtaining the first message, wherein the DM is hosted at the accelerator.

[0399] Aspect 62: An apparatus for wireless communication at an application executable by a DU of a RAN, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 31 to 46.

[0400] Aspect 63: An apparatus for wireless communication at an application executable by a DU of a RAN, the apparatus comprising at least one component for performing a method according to any one of aspects 31 to 46.

[0401] Aspect 64: A non-transitory computer-readable medium storing code for wireless communication at an application executable by a DU of a RAN, the code comprising instructions executable by a processor to perform a method according to any one of aspects 31 to 46.

[0402] Aspect 65: An apparatus for wireless communication at an accelerator associated with a DU of a RAN, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 47 to 61.

[0403] Aspect 66: An apparatus for wireless communication at an accelerator associated with a DU of a RAN, the apparatus comprising at least one component for performing a method according to any one of aspects 47 to 61.

[0404] Aspect 67: A non-transitory computer-readable medium storing code for wireless communication at an accelerator associated with a DU of a RAN, the code comprising instructions executable by a processor to perform the method according to any one of aspects 47 to 61.

[0405] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0406] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0407] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0408] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0409] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using the one or more instructions or codes. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0410] Computer-readable medium includes both non-transient computer storage medium and communication medium, including any medium that facilitates computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used for carrying or storing desired program code parts and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0411] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0412] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.

[0413] As used herein (including in the claims), the articles "a" and "an" before nouns are open-ended and are understood to mean "at least one" of these nouns or "one or more" of these nouns. Therefore, the terms "a", "at least one", "one or more", and "at least one of one or more" are interchangeable. For example, if a claim lists a "component" that performs one or more functions, each of these individual functions may be performed by a single component or by any combination of multiple components. Therefore, the term "component" having a characteristic or performing a function may refer to "at least one of one or more components" having a specific characteristic or performing a specific function. Subsequent references to components introduced with the article "a" using the term "the" or "the" may refer to any or all of the one or more components. For example, a component introduced with the article "a" may be understood to mean "one or more components", and subsequent references to "the component" in the claims may be understood to be equivalent to referring to "at least one of one or more components". Similarly, references to components introduced as "one or more components" using the term "the" or "the" may refer to any or all of the one or more components. For example, referring to "one or more components" later in a claim may be understood as being equivalent to referring to "at least one of the one or more components."

[0414] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0415] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described technology. However, these technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0416] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at an application executable by a distributed unit of a radio access network (RAN), the apparatus comprising: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to: identifying context information, the context information comprising a first identifier associated with an accelerator of the distributed unit, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a radio unit associated with the distributed unit, or any combination thereof; and Messages are exchanged with the accelerator based at least in part on the identified context information.

2. The apparatus of claim 1 , wherein the instructions for exchanging the messages are executable by the at least one processor to cause the apparatus to: providing the context information to the accelerator; and Information associated with a data model hosted at the accelerator is obtained from the accelerator based at least in part on providing the context information.

3. The apparatus of claim 1 , wherein the instructions for exchanging the messages are executable by the at least one processor to cause the apparatus to: obtaining the context information from the accelerator; and Information associated with a data model for communications between the accelerator and the radio unit associated with the distributed unit is provided to the accelerator based at least in part on obtaining the context information.

4. The apparatus of claim 3, wherein the instructions are further executable by the at least one processor to cause the apparatus to: providing a request for the information to the radio unit via an interface between the application and the radio unit; and The information is obtained from the radio unit via the interface and in response to the request, wherein the information from the radio unit is further conveyed to the accelerator via a second interface between the application and the accelerator.

5. The apparatus of claim 3, wherein the instructions are further executable by the at least one processor to cause the apparatus to: A first message is obtained from the accelerator based at least in part on providing the information, the first message indicating a result of a validation procedure associated with the information.

6. The apparatus of claim 5, wherein the first message indicates a failure of the authentication procedure, and the instructions are further executable by the at least one processor to cause the apparatus to: providing a second message to the accelerator in response to the failure, the second message instructing the accelerator to convey additional information about the failure associated with the context information; and A third message is obtained from the accelerator in response to the second message, the third message including the additional information associated with the context information for the communication between the accelerator and the radio unit.

7. The apparatus of claim 6, wherein the instructions are further executable by the at least one processor to cause the apparatus to: obtaining second additional information for a second data model based at least in part on the additional information; and A fourth message is provided to the accelerator, the fourth message conveying the second additional information.

8. The apparatus of claim 5, wherein the first message indicates a failure of the authentication procedure, and the instructions are further executable by the at least one processor to cause the apparatus to: Based at least in part on the failure, providing a second message to the accelerator, the second message identifying additional information for a second data model, wherein the additional information includes a modified version of the information.

9. The apparatus of claim 5, wherein the first message indicates a failure of the authentication procedure, and the instructions are further executable by the at least one processor to cause the apparatus to: An indication of additional information for a second data model is obtained from the accelerator based at least in part on the failure, the additional information being used to generate a modified version of the information.

10. The apparatus of claim 1, wherein the profile instance associated with the accelerator is associated with a carrier, a physical context, a baseband context associated with the accelerator, or any combination thereof.

11. The apparatus of claim 1, wherein the context information further comprises an indication of applicable antenna panels associated with one or more transmit-receive points.

12. The apparatus of claim 1, wherein the first identifier corresponds to at least two configuration file instances among a plurality of configuration file instances.

13. The apparatus of claim 1 , wherein the context information comprises a first plurality of identifiers associated with a plurality of profile instances associated with the accelerator, a second plurality of identifiers associated with a plurality of radio units including the radio unit, a third plurality of identifiers associated with a plurality of applications including the application, or any combination thereof.

14. An apparatus for wireless communication at an accelerator associated with a distributed unit of a radio access network (RAN), the apparatus comprising: at least one processor; at least one memory coupled to the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to: identifying context information, the context information comprising a first identifier associated with the accelerator, a second identifier associated with an application of the distributed unit, a third identifier associated with a configuration file instance associated with the accelerator, a fourth identifier associated with a radio unit associated with the distributed unit, or any combination thereof; and Messages are exchanged with the application based at least in part on the identified context information.

15. The apparatus of claim 14, wherein the instructions for exchanging the messages are executable by the at least one processor to cause the apparatus to: obtaining the context information from the application; and Information associated with a data model hosted at the accelerator is provided to the application based at least in part on obtaining the context information.

16. The apparatus of claim 14, wherein the instructions for exchanging the messages are executable by the at least one processor to cause the apparatus to: providing the context information to the application; and Information associated with a data model for communications between the accelerator and the radio unit associated with the distributed unit is obtained from the application based at least in part on providing the context information.

17. The apparatus of claim 16, wherein the instructions are further executable by the at least one processor to cause the apparatus to: A first message is provided to the application based at least in part on obtaining the information, the first message indicating a result of a validation procedure associated with the information.

18. The apparatus of claim 17, wherein the first message indicates a failure of the authentication procedure, and the instructions are further executable by the at least one processor to cause the apparatus to: obtaining, in response to the failure, a second message from the application, the second message instructing the accelerator to convey additional information about the failure associated with the context information; and A third message is provided to the application in response to the second message, the third message including the additional information associated with the context information for communications between the accelerator and the radio unit.

19. The apparatus of claim 18, wherein the instructions are further executable by the at least one processor to cause the apparatus to: A fourth message is obtained from the application in response to the failure, the fourth message including second additional information for a second data model.

20. The apparatus of claim 14, wherein the instructions are further executable by the at least one processor to cause the apparatus to: obtaining a first message from the application, the first message including information related to a second data model; determining a failure of a validation procedure associated with the information; as well as Based at least in part on the failure, a second message is provided to the application, the second message indicating third information, wherein the third information is associated with a modified version of the information.

21. The apparatus of claim 14, wherein the profile instance associated with the accelerator is associated with a carrier, a physical context, a baseband context associated with the accelerator, or any combination thereof.

22. The apparatus of claim 14, wherein the context information further comprises an indication of applicable antenna panels associated with one or more transmit-receive points associated with the distributed unit.

23. The apparatus of claim 14, wherein the first identifier corresponds to at least two configuration file instances among a plurality of configuration file instances.

24. The apparatus of claim 14, wherein the context information comprises a first plurality of identifiers associated with a plurality of profile instances associated with the accelerator, a second plurality of identifiers associated with a plurality of radio units including the radio unit, a third plurality of identifiers associated with a plurality of applications including the application, or any combination thereof.

25. A method for wireless communication at an application executable by a distributed element of a radio access network (RAN), the method comprising: identifying context information, the context information comprising a first identifier associated with an accelerator of the distributed unit, a second identifier associated with the application, a third identifier associated with a profile instance associated with the accelerator, a fourth identifier associated with a radio unit associated with the distributed unit, or any combination thereof; and Messages are exchanged with the accelerator based at least in part on the identified context information.

26. The method of claim 25, wherein exchanging the messages further comprises: providing the context information to the accelerator; as well as Information associated with a data model hosted at the accelerator is obtained from the accelerator based at least in part on providing the context information.

27. The method of claim 25, wherein exchanging the messages further comprises: obtaining the context information from the accelerator; as well as Information associated with a data model for communications between the accelerator and the radio unit associated with the distributed unit is provided to the accelerator based at least in part on obtaining the context information.

28. A method for wireless communication at an accelerator associated with a distributed unit of a radio access network (RAN), the method comprising: identifying context information, the context information comprising a first identifier associated with the accelerator, a second identifier associated with an application of the distributed unit, a third identifier associated with a configuration file instance associated with the accelerator, a fourth identifier associated with a radio unit associated with the distributed unit, or any combination thereof; and Messages are exchanged with the application based at least in part on the identified context information.

29. The method of claim 28, wherein exchanging the messages further comprises: obtaining the context information from the application; as well as Information associated with a data model hosted at the accelerator is provided to the application based at least in part on obtaining the context information.

30. The method of claim 28, wherein exchanging the messages further comprises: providing the context information to the application; as well as Information associated with a data model for communications between the accelerator and the radio unit associated with the distributed unit is obtained from the application based at least in part on providing the context information.

Images