Prioritization handling of high priority data segments in a communication system

Abstract

Aspects relate to providing a control message, such as an extension data segment, that includes an indication of a repetition of a highest priority data segment. The control message can be generated in a distributed unit (DU) and communicated to a radio unit (RU) via a fronthaul link. The control message can include a flag or a bit in a field of the extension data segment that allows the RU to determine the repetition of the highest priority data segment based on receiving the flag or processing the bit value in the field. Additionally, the indication of the repetition of the highest priority segment can be based on a segment identifier communicated by the DU, where a RU receiving the segment identifier can determine the repetition of the highest priority data segment by tracking the received segment identifiers.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of Non-Provisional Application No. 17 / 481,244 filed in the U.S. Patent and Trademark Office on September 21, 2021, and Provisional Application No. 63 / 082,446 filed in the U.S. Patent and Trademark Office on September 23, 2020, the entire contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. TECHNICAL FIELD

[0003] The technology discussed below relates generally to wireless communication networks, and more particularly, to prioritized handling or indication of high priority data segments in a communication system.

[0004] INTRODUCTION

[0005] Next generation wireless communication systems (e.g., 5G systems) can include a 5G core network and a 5G radio access network (RAN), such as an open radio access network (O-RAN) specified by the O-RAN Alliance. A typical RAN supports wireless communication with mobile devices (e.g., user equipment (UE)) via one or more cells (more specifically, via remote radio units (RRU) / remote radio heads (RRH)). However, in O-RAN, the RRUs / RRHs are connected to a baseband unit (BBU) by a physical link called the fronthaul, which can include further elements such as a distributed unit (DU).

[0006] BRIEF OVERVIEW OF SOME EXAMPLES

[0007] The following presents a summary of one or more aspects of the disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects of the disclosure, and is intended neither to identify key or critical elements of all aspects of the disclosure nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in a form that is brief, so as to

[0008] The present disclosure relates, in some aspects, to providing an indication of repetition of a highest priority data segment in a RAN, such as an O-RAN. For example, a control plane message between a distributed unit (DU) and a radio unit (RU) of a RAN (e.g., an O-RAN) can include an indication that a high priority data segment can be repeated on a fronthaul link.

[0009] In some examples, a method of communicating at a network node, such as a DU, is disclosed. The method includes generating a control message, where the control message includes at least one field indicating when transmission of a prioritized data section is repeated. Additionally, the method includes transmitting the control message to a radio unit (RU) over a fronthaul link.

[0010] In other examples, a network node, such as a DU, is disclosed that includes a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and memory are configured to generate a control message, where the control message includes at least one field indicating when transmission of a prioritized data section is repeated. Further, the processor and memory are configured to transmit the control message to a radio unit (RU) over a fronthaul link using the transceiver.

[0011] In yet other examples, a method of communicating at a radio unit (RU) is disclosed. The method includes receiving a control message from a network node over a fronthaul link, where the control message includes at least one field indicating when transmission of a prioritized data section is repeated. Further, the method includes processing the control message including the prioritized data section that is repeated based on the indication of the at least one field.

[0012] In yet other examples, a network device, such as a radio unit (RU), is disclosed that includes a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and memory are configured to receive a control message from a network node over a fronthaul link, where the control message includes at least one field indicating when transmission of a prioritized data section is repeated. Further, the processor and memory are configured to process the control message including the prioritized data section that is repeated based on the indication of the at least one field.

[0013] These and other aspects of the present disclosure will become more fully understood upon review of the following detailed description in conjunction with the accompanying drawings. Other aspects, features, and embodiments of the disclosure will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific example embodiments of the present disclosure in conjunction with the accompanying figures. While features of the present disclosure can be discussed relative to certain embodiments and figures below, all embodiments of the present disclosure can include one or more of the advantageous features discussed herein. In other words, while one or more embodiments can be discussed as having certain advantageous features, one or more of such features can also be used in accordance with the various embodiments of the present disclosure discussed herein. In a similar manner, different embodiments of the present disclosure can be discussed herein in relation to a device, system, or method embodiment. It should be appreciated that such examples can apply to a variety of embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1 is a conceptual illustration of an example of a radio access network according to some aspects.

[0016] Figure 2 is a schematic illustration of a wireless communication system according to some aspects.

[0017] Figure 3 is a diagram illustrating an example of a frame structure for use in a radio access network according to some aspects.

[0018] Figure 4 is a block diagram illustrating an example of an open radio access network (O-RAN) according to some aspects.

[0019] Figure 5 is a diagram illustrating another example of an O-RAN according to some aspects.

[0020] Figure 6 is a diagram illustrating an example of a front-haul communication according to some aspects.

[0021] Figure 7 is a diagram illustrating an example of a control plane section in a time / frequency resource grid according to some aspects.

[0022] Figure 8 is a diagram illustrating another example of a control plane section with high priority in a time / frequency resource grid according to some aspects.

[0023] Figure 9 is a diagram illustrating a message format for transmission of multiple messages according to some aspects.

[0024] Figure 10 is a diagram illustrating another example of a control plane section with high priority and multiple users in a time / frequency resource grid according to some aspects.

[0025] Figure 11 is a diagram illustrating an example of an information element according to some aspects.

[0026] Figure 12 is a diagram illustrating another example of an information element according to some aspects.

[0027] Figure 13 is a block diagram illustrating an example of a hardware implementation for a radio according to some aspects employing a processing system.

[0028] Figure 14 is a flow diagram of an example process for receiving a control message with a repetition section according to some aspects.

[0029] Figure 15is a block diagram illustrating an example of a hardware implementation for a network node (e.g., a distributed unit) employing a processing system in accordance with some aspects.

[0030] Figure 16 is a flow diagram of an example process for communicating a control message indicating a repetition section in accordance with some aspects.

[0031] DETAILED DESCRIPTION

[0032] The detailed description set forth below, in connection with the appended drawings and embodiments described herinin, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without

[0033] The electromagnetic spectrum is often subdivided based on frequency / wavelength into various classes, bands, channels, and so on. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclatural issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in various documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is designated as a “millimeter wave” band by the International Telecommunications Union (ITU).

[0034] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and as such can effectively extend features of FR1 and / or FR2 into the mid-band frequencies. Additionally, higher bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands falls within the EHF band.

[0035] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like, if used herein, can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like, if used herein, can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF frequency band.

[0036] Various aspects of the present disclosure relate to providing an indication of repetition of a highest priority data segment in a RAN, such as an O-RAN (such as specified by the O-RAN Alliance). In an aspect, a control plane message (i.e., a C-plane message) between a distributed unit (DU) and a radio unit (RU) of a RAN (e.g., an O-RAN) can include an indication that a high priority data segment can be repeated on a fronthaul link. Note that a control message repeated across multiple messages ensures that the highest priority segment description repeated across messages is correctly interpreted. A repeated message can result in the RU applying beamforming weights for resource elements (REs) in the highest priority segment multiple times, where the RU tracks the weights that have already been processed for each RE. This tracking requires the RU to maintain state information on a per-RE basis across all layers and symbols, which is costly in terms of memory and hardware size and latency. Accordingly, providing an indication of when a highest priority segment is repeated, as described herein according to at least some aspects, can alleviate cost and latency.

[0037] While aspects and examples are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases can come about in many different arrangements and scenarios. The innovations described herein can be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, some aspects and / or uses can come about through use of integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples can or can not be specifically directed to use cases or applications, a wide assortment of applicability can occur across a number of different scenarios. Implementations can range from full-fledged chips to system on chips (SoCs) to small parts of a chip to individual components to modularity implemented across multiple devices. Similarly, the

[0038] The various concepts presented throughout this disclosure can be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Referring now to Figure 1 , as an illustrative example without limitation, a schematic illustration of a radio access network (RAN) 100 is provided. The RAN 100 can implement any suitable wireless communication technology or technologies to provide radio access for one or more user equipment (UE). As one example, the RAN 100 can operate according to 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G. As another example, the RAN 100 can operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE. The 3GPP refers to this hybrid RAN as the Next Generation RAN, or NG-RAN. Further, in some aspects, the RAN 100 can be configured to be an O-RAN. Of course, many other examples can be utilized within the scope of the present disclosure.

[0039] The geographic region covered by the radio access network 100 can be divided into a number of cells (cellular regions). A cell is a geographical area that is served by a transceiver or base station and within which a user equipment (UE) can be located. A cell can be further described as a base station subsystem or access node that is configured to handle radio communication resources for the UEs located within the cell. Figure 1Cellular regions 102, 104, 106, and 108 are illustrated, each of which can include one or more sectors (not shown). A sector is a sub-area of a cell. All sectors within one cell are served by the same base station. A radio link within a sector can be identified by a single logical identity belonging to that sector. In a cell partitioned into sectors, multiple sectors within a cell can be formed by an antenna group, where each antenna is responsible for communication with UEs in a portion of the cell.

[0040] Generally, respective base stations (BSs) serve the respective cells. Broadly, a base station is a network element in a radio access network responsible for radio transmission and reception to and from UEs in one or more cells. A BS can also be referred to by those skilled in the art as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an evolved Node B (eNB), a g Node B (gNB), a transmit receive point (TRP), or some other suitable terminology. In some examples, a base station can include two or more TRPs that can or can not be co-located. Each TRP can communicate on the same or different carrier frequencies. In examples where the RAN 100 operates according to both LTE and 5G NR standards, one of the base stations can be an LTE base station, while another base station can be a 5G NR base station.

[0041] Various base station arrangements can be utilized. For example, in Figure 1 two base stations 110 and 112 are shown in the cellular regions 102 and 104, and a third base station 114 is shown controlling a remote radio head (RRH) 116 in the cellular region 106. That is, a base station can have integrated antennas, or can be connected by feed cabling to antennas or RRHs. In the illustrated example, the cellular regions 102, 104, and 106 can be referred to as macro cellular regions because the base stations 110, 112, and 114 support cellular regions with large sizes. Further, a base station 118 is shown in the cellular region 108, which can overlap with one or more macro cellular regions. In this example, the cellular region 108 can be referred to as a small cellular region (e.g., a microcell, a picocell, a femtocell, a home base station, a home NodeB, a home eNodeB, etc.) because the base station 118 supports a cellular region with a relatively small size. The cellular region size setting can be done according to system design and component constraints.

[0042] It will be appreciated that the radio access network 100 can include any number of wireless base stations and cells. In addition, relay nodes can be deployed to extend the size or coverage area of a given cell. Base stations 110, 112, 114, 118 provide wireless access points to a core network for any number of mobile

[0043] Figure 1 Further included is an unmanned aerial vehicle (UAV) 120, which can be a drone or quadcopter. The UAV 120 can be configured to function as a base station, or more specifically, as a mobile base station. That is, in some examples, a cell can not necessarily be stationary, and the geographic area of a cell can move according to the location of a mobile base station, such as the UAV 120.

[0044] Generally, a base station can include a backhaul interface for communication with a backhaul portion of a network (not shown). The backhaul can provide a link between a base station and a core network (not shown), and in some examples, can provide interconnection between respective base stations. The core network can be part of the wireless communication system, and can be independent of the radio access technology used in the radio access network. Various types of backhaul interfaces can be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.

[0045] The RAN 100 is illustrated supporting wireless communication for multiple mobile apparatuses. A mobile apparatus is commonly referred to as user equipment (UE) in standards and specifications promulgated by the third generation partnership project (3 GPP), but can also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE can be an apparatus that provides access to network services for a user.

[0046] Within the present document, a "mobile" device need not have a mobile capability, and can be static. The term mobile device or mobile equipment refers to a broad variety of devices and technologies. For example, some non-limiting examples of a mobile device include a mobile device, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC), a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA), and a vast range of embedded systems, e.g., corresponding to "Internet of Things" (IoT). Additionally, a mobile device can be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and / or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a camera, a game console, etc. A mobile device additionally can be a digital home or smart home device, such as a home audio, video, and / or multimedia device, a domestic appliance, an automatic vending machine, a smart lighting device, a home security system, a smart meter, etc. Additionally, a mobile device can be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling / monitoring traffic, power, utility, etc. (e.g., smart grid), an industrial automation and enterprise device, a logistics controller / monitor, agricultural equipment, etc. Still further, a mobile device can provide for connected medicine or remote healthcare, i.e., health care at a distance. Telehealth devices can include telehealth monitoring devices and telehealth administration devices, whose communication can be given prioritized access over, and / or prioritized

[0047] Within the RAN 100, a cell can include UEs that can be in communication with one or more sectors of each cell. For example, UEs 122 and 124 can be in communication with base station 110; UEs 126 and 128 can be in communication with base station 112; UEs 130 and 132 can be in communication with base station 116 via RRH 114; UE 134 can be in communication with base station 118; and UE 136 can be in communication with mobile base station 120. Here, each base station 110, 112, 114, 118, and 120 can be configured as an access point to a core network (not shown) for all the UEs in the corresponding cell. In some examples, UAV 120 (e.g., quadcopter) can be a mobile network node and can be configured to function as a UE. For example, UAV 120 can operate within cell 102 by communicating with base station 110.

[0048] Wireless communication between a RAN 100 and a UE (e.g., UE 122 or 124) can be described as utilizing an air interface that transmits over a wireless radio frequency spectrum. The air interface can utilize any suitable wireless communication protocol, including but not limited to, Wi-Fi, Bluetooth, and / or a cellular communication protocol. The air interface can be configured to transmit and receive signals, messages, and / or data in a designated spectrum, either licensed or unlicensed, according to pre-defined specifications for a particular wireless communication protocol. In some examples, the air interface can utilize a frequency-hopping spread spectrum (FHSS) approach to transmitting signals, messages, and / or data. In such examples, the air interface can hop across a designated spectrum according to a pre-defined frequency-hopping sequence. In some examples, the air interface can utilize a direct-sequence spread spectrum (DSSS) approach to transmitting signals, messages, and / or data. In such examples, the air interface can spread the transmitted signals, messages, and / or data across a designated spectrum.

[0049] For example, a DL transmission can include unicast or broadcast transmissions of control information and / or traffic information (e.g., user data traffic) from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124), while a UL transmission can include transmissions of control information and / or traffic information originating at a UE (e.g., UE 122). Additionally, uplink and / or downlink control information and / or traffic information can be partitioned in time into frames, subframes, slots, and / or symbols. As used herein, a symbol can refer to a time unit of one resource element (RE) per subcarrier in an orthogonal frequency-division multiplexing (OFDM) waveform. A slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 ms. Multiple subframes or slots can be grouped together to form a single frame or radio frame. Within the present disclosure, a frame can refer to a predetermined duration (e.g., 10 ms) for wireless transmissions, where each frame includes, for example, 10 subframes of 1 ms each. Of course, these definitions are not required and waveforms can be organized using any suitable approach, and various time divisions of a waveform can have any suitable duration.

[0050] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources (e.g., time-frequency resources) for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, the scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, a UE or scheduled entity utilizes resources allocated by the scheduling entity.

[0051] A base station is not the only entity that can function as a scheduling entity. That is, in some examples, UEs can function as scheduling entities, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, two or more UEs (e.g., UEs 138, 140 and 142) can communicate with each other using sidelink signals 137 without relaying that communication through a base station. In some examples, UEs 138, 140, and 142 can each act as a scheduling entity or transmitting side link device and / or a scheduled entity or receiving side link device to schedule resources and communicate sidelink signals 137 therebetween without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 126 and 128) within the coverage area of a base station (e.g., base station 112) can also communicate sidelink signals 127 over a direct link (sidelink) without relaying that communication through base station 112. In this example, base station 112 can allocate resources to UEs 126 and 128 for sidelink communication. In either case, such sidelink signaling 127 and 137 can be implemented in a peer-to-peer (P2P) network, device-to-device (D2D) network, vehicle-to-vehicle (V2V) network, vehicle-to-everything (V2X), mesh network, or other suitable direct link network.

[0052] In some examples, a D2D relay framework can be included within a cellular network to facilitate relaying of communications to / from a base station 112 via a D2D link (e.g., sidelink 127 or 137). For example, one or more UEs (e.g., UE 128) within the coverage area of base station 112 can operate as a relay UE to extend coverage of base station 112, improve transmission reliability to one or more UEs (e.g., UE 126), and / or allow the base station to recover from a failed UE link due to, for example, blockage or fading. Two main technologies that can be used by V2X networks include Dedicated Short-Range Communications (DSRC) based on the IEEE 802.1 lp standard and cellular V2X based on LTE and / or 5G (New Radio) standards. Various aspects of the present disclosure can relate to New Radio (NR) cellular V2X networks, which are referred to herein for simplicity as V2X networks. However, it should be understood that the concepts disclosed herein can not be limited to a particular V2X standard, or can refer to sidelink networks other than V2X networks.

[0053] In some further examples, the RAN 100 can include an RF repeater 144 in communication with a base station or gNB, such as the base station 112. The RF repeater 144 is configured to relay UL and DL transmissions between the base station 112 and one or more UEs, such as the UE 146, for example. Moreover, as will be discussed later, the RF repeater 144 can be configured to utilize beamforming for transmissions to a UE, such as the UE 146.

[0054] To enable transmissions over the air interface to achieve a low block error rate (BLER) while still achieving very high data rates, channel coding can be used. That is, wireless communication can generally utilize a suitable error correcting block code. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. This redundancy in the encoded information message can improve the reliability of the message, enabling any bit errors that can occur due to noise to be corrected.

[0055] Data coding can be implemented in a variety of ways. In earlier 5G NR specifications, user data is coded using quasi-cyclic low-density parity check (LDPC) with two different base graphs: one base graph is used for large code blocks and / or high code rates, while the other base graph is used otherwise. Control information and physical broadcast channel (PBCH) are coded using polar coding, based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0056] Aspects of the present disclosure can utilize any suitable channel code for implementation. Various implementations of base stations and UEs can include suitable hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communication.

[0057] In the RAN 100, the ability for a UE to communicate while moving between different locations is referred to as mobility. The various physical channels established for the UE to communicate with the RAN are generally set up under the control of an access and mobility management function (AMF). In some scenarios, the AMF can include a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF can manage the security context for both control plane and user plane functionality, in whole or in part.

[0058] In some examples, the RAN 100 can enable mobility and handovers (i.e., transfer of a UE’s connection from one radio channel to another). For example, during a call with a scheduling entity, or at any other time, a UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds that of the serving cell for a given amount of time, the UE can hand over or hand in from the serving cell to the neighboring (target) cell. For example, the UE 124 can move from the geographic area corresponding to its serving cell 102 to the geographic area corresponding to a neighbor cell 106. When the signal strength or quality from the neighbor cell 106 exceeds that of its serving cell 102 for a given amount of time, the UE 124 can transmit a reporting message to its serving base station 110 indicating this condition. In response, the UE 124 can receive a handover command and the UE can undergo a handover to cell 106.

[0059] In various implementations, the air interface in the RAN 100 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides for exclusive use of a portion of the spectrum to one or more licensees. Unlicensed spectrum is available for use by any operator or device on a contention-based basis, without a government-issued license. Shared spectrum can fall between licensed and unlicensed spectrum, where technology rules can be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties, such as with suitable licensee-determined conditions to gain access.

[0060] The air interface in the RAN 100 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication with multiple devices. For example, 5G NR specifications provide multiple access for UEs 122 and 124 to the base station 110 on the UL, or reverse, link and for UEs 122 and 124 to the base station 110 on the DL, or forward, link utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). Additionally, for UL transmission, 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided utilizing time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA), or other suitable multiple access schemes. Further, multiplexing of the DL transmission from the base station 110 to UEs 122 and 124 can be provided utilizing time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0061] Further, the air interface in the RAN 100 can utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which both endpoints can communicate with one another. Full duplex means both endpoints can simultaneously communicate with one another. Half duplex means only one endpoint in a link can send information to the other at a time. Half duplex emulation is commonly accomplished on wireless links through time division duplex (TDD), where the two endpoints only talk at different times, e.g., one in the downlink (DL) and the other in the uplink (UL). The appropriate time for transmission or reception is controlled by a scheduler, which divides time into scheduled periods, e.g., slots. In full duplex emulation, the endpoints talk at the same time, but the scheduler coordinates this such that the transmitter and receiver do not interfere with one another. This is commonly accomplished by utilizing separate transmit and receive carriers, e.g., frequency division duplex (FDD), or separate transmit and receive times, e.g., time division duplex (TDD). In other examples, full duplex emulation can be achieved on a single carrier through scheduling and cancellation, where the scheduler allocates transmission and reception times to the endpoints and cancels the transmitter or receiver during the reception or transmission times, respectively. In still other examples, full duplex emulation can be achieved on a single carrier through transmit and receive beamforming, where the scheduler allocates transmission and reception times to the endpoints and forms a beam for transmission or reception during the allocated times.

[0062] As another illustrative example, but not by way of limitation, Figure 2Aspects are illustrated by reference to a schematic of a wireless communication system 200. The wireless communication system 200 includes three interacting domains: a core network 202, a radio access network (RAN) 204, and a user equipment (UE) 206. Via the wireless communication system 200, the UE 206 can be enabled to carry out data communication with an external data network 210, such as (but not limited to) the Internet.

[0063] The RAN 204 can implement any suitable wireless communication technology or technologies to provide radio access to the UEs 206. As one example, the RAN 204 can operate according to 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G. As another example, the RAN 204, such as in a non-standalone (NSA) system (including EN-DC systems), can operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE. The 3GPP also refers to this hybrid RAN as Next Generation RAN, or NG-RAN. Additionally, many other examples can be utilized within the scope of the present disclosure.

[0064] As Figure 2 As illustrated in FIG. 1, the RAN 204 includes a plurality of base stations 208. In different technologies, standards, or contexts, a base station 208 can variously be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a NodeB (NB), an eNodeB (eNB), a next Generation NodeB (gNB), a transmit receive point (TRP), or some other suitable terminology. In some examples, a base station can include two or more TRPs that can be co-located or non-co-located. Each TRP can communicate on the same or different carrier frequencies.

[0065] The RAN 204 is further illustrated supporting wireless communication for multiple mobile apparatuses. A mobile apparatus can be referred to as user equipment (UE) in 3GPP standards, but can also be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE can be an apparatus (e.g., mobile apparatus) that provides a user with access to network services.

[0066] Wireless communication between a RAN 204 and a UE 206 can be described as utilizing an air interface. Transmissions over the air interface from a base station, such as base station 208, to a UE, such as UE 206, can be referred to as downlink (DL) transmission. In accordance with certain aspects of the present disclosure, the term downlink can refer to a point-to-multipoint transmission from a scheduling entity (described further below; e.g., base station 108) to a set of one or more terminal devices (e.g., UEs 206). Another way to describe this scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 206) to a base station (e.g., base station 208) can be referred to as uplink (UL) transmissions. In accordance with further aspects of the present disclosure, the term uplink can refer to a point-to-point transmission from a terminal device (e.g., UE 206) to a scheduling entity (e.g., base station 208).

[0067] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 208) allocates resources (e.g., in time, frequency, or both) to devices and equipment within its service area or cell. Within the present disclosure, the scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, a UE 206 (which can be a scheduled entity) can utilize resources allocated by the scheduling entity 208.

[0068] As Figure 2 As illustrated in FIG. 2, the base station or scheduling entity 208 can broadcast downlink traffic 212 to one or more UEs, such as UE 206. Broadly, the base station or scheduling entity 208 can be configured as a node or device responsible for scheduling traffic (including the downlink traffic 212 and, in some examples, also including uplink traffic 216 from UEs 206 to scheduling entity 208) in a wireless communication network. The UE 206 can be configured as a node or device that also receives downlink control information 214 (including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network, such as the scheduling entity 208. Further, the UE 206 can transmit uplink control information 218 to the base station 208, including but not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information.

[0069] Generally, the base station 208 can include a backhaul interface for communication with a backhaul portion 222 of the wireless communication system. The backhaul 222 can provide a link between the base station 208 and the core network 202. Further, in some examples, the backhaul interface can provide interconnection between respective base stations 208. Various types of backhaul interfaces can be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.

[0070] The core network 202 can be a part of the wireless communication system 200, and can be independent of the radio access technology used by the RAN 204. In some examples, the core network 202 can be configured according to 5G standards (e.g., 5GC). In other examples, the core network 202 can be configured according to a 4G Evolved Packet Core (EPC), or any other suitable standard or configuration.

[0071] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station 208) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, a scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities as discussed infra. That is, for scheduled communication, a UE 206 (which can be a scheduled entity) can utilize resources assigned by a base station or scheduling entity 208.

[0072] Various aspects of the present disclosure will be described in reference to an OFDM waveform, which is schematically illustrated in Figure 3 The skilled practitioner will appreciate that the various aspects of the present disclosure can be applied in substantially the same way to SC-FDMA waveforms as described infra. That is, while some examples of the present disclosure can focus on OFDM links for clarity, it will be understood that the same principles apply to SC-FDMA waveforms.

[0073] The various aspects of the present disclosure will be described in reference to an OFDM waveform, which is schematically illustrated in Figure 3 The skilled practitioner will appreciate that the various aspects of the present disclosure can be applied in substantially the same way to SC-FDMA waveforms as described infra. That is, while some examples of the present disclosure can focus on OFDM links for clarity, it will be understood that the same principles apply to SC-FDMA waveforms.

[0074] Within the present disclosure, a frame 300 refers to a 10 ms duration for wireless transmissions, where each frame includes 10 subframes, each of 1 ms. A transmission burst can include a plurality of frames. On a given carrier, there can be one set of frames in the UL, and another set of frames in the DL. Referring now to Figure 3 , a spread view of an exemplary subframe 302 is illustrated, showing an OFDM resource grid. However, as the skilled artisan will appreciate, the PHY transmission structure for any particular application can differ from the examples described herein, depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols; while frequency is in the vertical direction in units of subcarriers or tones.

[0075] The resource grid 304 can be used to schematically represent time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding multiple resource grids 304 can be available for communication. The resource grid 304 is divided into multiple resource elements (REs) 306. An RE, which comprises 1 subcarrier x 1 symbol, is the smallest discrete part of the time-frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation selected, each RE can represent one or more information bits. In some examples, a block of REs can be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, a RB can include 12 subcarriers, this number being independent of the numerology used. In some examples, depending on the numerology, a RB can include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB such as the RB 308 entirely corresponds to a single direction of communication (transmission or reception for a given device).

[0076] A set of contiguous or non-contiguous resource blocks can be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A set of subbands or BWPs can span the entire bandwidth. Scheduling of a UE (scheduled entity) for downlink or uplink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Thus, a UE generally utilizes only a subset of the resource grid 304. An RB can be the smallest unit of resources that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme chosen for the air interface, the higher the data rate for the UE.

[0077] In this illustration, the RB 308 is shown as occupying less than the entire bandwidth of the subframe 302, with some subcarriers illustrated above and below the RB 308. In a given implementation, the subframe 302 can have a bandwidth corresponding to any number of one or more RBs 308. Also, in this illustration, the RB 308 is shown as occupying less than the entire duration of the subframe 302, although this is merely one possible example.

[0078] Each subframe 302 (e.g., a 1 ms subframe) can include one or more adjacent slots. In Figure 3In the illustrative example shown, a subframe 310 includes four time slots. In some examples, time slots may be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-time slots with shorter durations (e.g., one or two OFDM symbols). In some cases, these mini-time slots or shortened TTIs may occupy resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0079] An expanded view of a time slot 312 in subframe 310 interprets time slot 312 as including a control region 314 and a data region 316. In a first example of time slot 312, control region 314 may carry a control channel (e.g., Physical Downlink Control Channel (PDCCH)) and data region 316 may carry a data channel (e.g., Physical Downlink Shared Channel (PDSCH)). In a second example of time slot 312, control region 314 may carry a control channel (e.g., Physical Uplink Control Channel (PUCCH)) and data region 316 may carry a data channel (e.g., Physical Uplink Shared Channel (PUSCH)). Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure described herein is merely exemplary in nature and may utilize different time slot structures, and may include one or more for each of the control region and data region.

[0080] Although not in Figure 3 The explanation is as follows: Each RE 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals, including but not limited to demodulation reference signals (DMRS), control reference signals (CRS), channel state information reference signals (CSI-RS), and / or probe reference signals (SRS). These pilot or reference signals can be used by the receiver equipment to perform channel estimation for the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0081] In some examples, time slot 312 can be used for broadcast or unicast communication. For example, broadcast, multicast, or ensemble communication can refer to point-to-multipoint transmission from one device (e.g., a base station, UE, or other similar device) to other devices. As used herein, broadcast communication is delivered to all devices, while multicast communication is delivered to multiple intended receiving devices. Unicast communication can refer to point-to-point transmission from one device to a single other device.

[0082] In a DL transmission, the transmitting device (e.g., scheduling entity / base station 108) can allocate one or more REs 306 (e.g., within the control region 314) to carry DL control information (DCI) to one or more scheduled entities (e.g., UEs / scheduled entities 106), which can include one or more DL control 114 channels that can carry, for example, information derived from higher layers, such as a physical broadcast channel (PBCH), a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), a physical downlink control channel (PDCCH), etc. The physical control format indicator channel (PCFICH) can provide information to assist the receiving device in receiving and decoding the PDCCH and / or physical HARQ indicator channel (PHICH). The PHICH carries HARQ feedback transmissions such as acknowledgments (ACK) or negative acknowledgments (NACK). HARQ is a technique well-known to those of ordinary skill in the art, implemented by many communication systems to ensure reliable delivery of data between a sender and a receiver in a noisy and / or error-prone

[0083] The base station can further allocate one or more REs 306 to carry other DL signals such as demodulation reference signals (DMRS); phase-tracking reference signals (PT-RS); positioning reference signals (PRS); channel state information reference signals (CSI-RS); a primary synchronization signal (PSS); and a secondary synchronization signal (SSS). These DL signals, which can also be referred to as downlink physical signals, can correspond to sets of resource elements used by the physical layer but generally do not carry information derived from a higher layer. The UE can utilize the PSS and SSS to achieve radio frame, subframe, slot, and symbol synchronization in the time domain; to identify the center of the channel (system) bandwidth in the frequency domain; and to identify the physical cell identifier or ID (PCI) of the cell. The synchronization signals PSS and SSS, and in some examples also the PBCH and PBCH DMRS, can be transmitted in a synchronization signal block (SSB). The PBCH can further include a master information block (MIB) that includes various system information along with parameters for decoding a system information block (SIB). The SIB can be, for example, System Information Type 1 (SystemInformationType1) (SIB1), which can include various additional system information. Examples of system information transmitted in the MIB can include, but are not limited to, subcarrier spacing, system frame number, configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), and search space for SIB1. Examples of additional system information transmitted in SIB1 can include, but are not limited to, random access search space, downlink configuration information, and uplink configuration information. The MIB and SIB1 together provide the minimum system information (SI) for initial access.

[0084] The synchronization signals PSS and SSS (collectively referred to as SS) and, in some examples, also the PBCH can be transmitted in an SS block that includes 4 consecutive OFDM symbols numbered in increasing order from 0 to 3 via a time index. In the frequency domain, the SS block can extend over 240 contiguous subcarriers, with the subcarriers numbered in increasing order from 0 to 239 via a frequency index. Of course, the present disclosure is not limited to this particular SS block configuration. It is within the scope of the present disclosure for other non-limiting examples to utilize more or fewer than two synchronization signals; to include one or more supplemental channels in addition to the PBCH; to omit the PBCH; and / or to utilize non-consecutive symbols for the SS block.

[0085] In UL transmissions, a transmitting device (e.g., UE / scheduled entity 106) can utilize one or more REs 306, including one or more UL control 118 channels that can carry uplink control information (UCI) to, for example, a scheduling entity / base station 108. UCI can include various groupings and categories of information, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. In some examples, the uplink control information can include a scheduling request (SR), i.e., a request to the scheduling entity to schedule uplink transmissions. Here, in response to the SR transmitted on the uplink control 118 channel from the scheduled entity 106, the scheduling entity / base station 108 can transmit downlink control information (DCI) that can schedule resources for uplink packet transmissions. UCI can also include HARQ feedback (such as an acknowledgement (ACK) or negative

[0086] In addition to control information, one or more REs 306 (e.g., within data region 314) can also be allocated for user data traffic. Such traffic can be carried in one or more traffic channels, such as a physical downlink shared channel (PDSCH) for DL transmissions, or a physical uplink shared channel (PUSCH) for UL transmissions. In some examples, one or more REs 306 within data region 314 can be configured to carry a SIB (e.g., SIB1), which carries information that can enable access to a given cell.

[0087] The physical channels described above are generally multiplexed and mapped to transport channels for handling at the medium access control (MAC) layer. Transport channels carry information blocks, which are known as transport blocks (TBs). Transport block size (TBS), which can correspond to a number of information bits, can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0088] The above is described in connection with Figures 1-3The channels or carriers described are not necessarily all the channels or carriers available between the scheduling entity and the scheduled entity, and those skilled in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be available in addition to those described.

[0089] In some examples, the Open Radio Access Network (O-RAN) architecture can be based on 3GPP technologies discussed above (e.g., 5G and / or LTE), where O-RAN employs virtualized network elements, white-box hardware, and standardized interfaces that support network intelligence and open interfaces. For example, O-RAN can be self-driving and capable of leveraging new learning-based technologies to automate the operation of network functions. Additionally, O-RAN can employ open interfaces that enable vendors and operators to introduce their own services or custom networks to meet their unique needs.

[0090] To this end, O-RAN can employ a flexible and distributed baseband architecture, where the functionality of the baseband unit (e.g., incorporating modem functionality) can be split between one or more control units and one or more distributed units (which may also be referred to as data units). For example, a baseband unit may include multiple control units, each supporting multiple distributed units. Each distributed unit may in turn support one or more radio units. The control units, distributed units, and radio units provide different communication protocol layer functionalities and other related functionalities.

[0091] Figure 4 This is a block diagram illustrating examples of several components of O-RAN 400 according to some aspects. In practice, note that O-RAN 400 may include, in addition to... Figure 4 Other components besides those described. The baseband unit (BBU) communicates with the core network 404 via backhaul link 406 and with at least one radio unit 410 via outbound link 412. The baseband unit 402 includes at least one control unit (CU) 414 and at least one distributed unit (DU) 416 communicating via at least one midrange link 418. Each radio unit 410 communicates with at least one UE 420 via RF signaling.

[0092] In some examples, the control unit (such as CU 414) is a logical node for the Main Memory Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, Serving Data Adaptation Protocol (SDAP) layer, and other control functions. The control unit can also terminate at the interfaces of network nodes (e.g., nodes in the core network). Figure 4 E1, E2, etc. (not shown in the image). F1 interface ( Figure 4The F1 interface (not shown in FIG. 5) can provide a mechanism to interconnect control units (e.g., PDCP layer and higher) and distributed units (e.g., RLC layer and lower). In some aspects, the F1 interface can provide control plane and user plane functions (e.g., interface management, system information management, UE context management, RRC message transfer, etc.). The F1AP is an application protocol for F1, which in some examples defines the signaling procedures for F1. The F1 interface supports F1-C over the control plane and F1-U over the user plane.

[0093] In some examples, a distributed unit, such as the DU 416, is a logical node hosting a radio link control (RLC) layer, a medium access control (MAC) layer, and a high physical (PHY) layer based on lower layer function splitting (LLS). In some aspects, the distributed unit can control operation of at least one radio unit. The distributed unit can also terminate interfaces to the control unit and / or other network nodes (e.g., F1 interface, E2 interface, etc.). In some examples, the high PHY includes portions of PHY processing, such as forward error correction 1 (FEC 1) encoding and decoding, scrambling, modulation, and demodulation.

[0094] In some examples, a radio unit, such as the RU 410, is a logical node hosting a low PHY layer and radio frequency (RF) processing based on lower layer function splitting. In some examples, the radio unit can be similar to a 3GPP transmission and reception point (TRP) or a remote radio head (RRH), while also including the low PHY layer. In some examples, the low PHY includes portions of PHY processing, such as fast Fourier transform (FFT), inverse FFT (IFFT), digital beamforming, and physical random access channel (PRACH) extraction and filtering. The radio unit can also include a radio chain for communicating with one or more UEs.

[0095] Figure 5 is a diagram illustrating an example of the distributed nature of the O-RAN 500, according to some aspects. The O-RAN 500 can be similar to the radio access network 200 shown in FIG. 5, as the O-RAN 500 can be divided into a number of cells (e.g., cell 522), each of which can be served by a respective network node (e.g., control unit, distributed unit, and radio unit). The network nodes can constitute access points, base stations (BSs), eNBs, gNBs, or other nodes that support access to wireless frequencies (e.g., radio frequencies (RF) frequencies) and / or other communication links for one or more UEs located within a cell. Figure 2

[0096] In some aspects, the O-RAN 500 can be a 5G network. In some aspects, the O-RAN 500 can be a 4G network. In some aspects, the O-RAN 500 can be a 3G network. In some aspects, the O-RAN 500 can be a 2G network. In some aspects, the O-RAN 500 can be a combination of 2G, 3G, 4G, and / or 5G networks. Figure 5 ​In the example of FIG. 5, a control unit (CU) 502 communicates with a core network 504 via a backhaul link, and with first and second distributed units (DUs) 506 and 508 via respective midhaul links. The first distributed unit 506 communicates with first and second radio units (RUs) 510 and 512 via respective fronthaul links. The second distributed unit 508 communicates with a third radio unit 514 via a fronthaul link. The first radio unit 510 communicates with at least one UE 516 via at least one RF access link. The second radio unit 512 communicates with at least one UE 518 via at least one RF access link. The third radio unit 514 communicates with at least one UE 520 via at least one RF access link.

[0097] Figure 6 FIG. 6 is a diagram illustrating an example of an eNB or gNB 602 including a distributed unit (DU) 604 and a radio unit (RU) 606, which can or can not be co-located. The distributed unit 604 and the radio unit 606 exchange control plane and user plane information over a fronthaul link via a lower layer split (LLS) control, user, and synchronization (CUS) interface. The LLS-CUS can include LLS-C and LLS-U interfaces that provide control plane (C-plane) and user plane (U-plane), respectively. In some examples, the control plane refers to real-time control between a distributed unit (DU) and a radio unit (RU). In some aspects, this can be in contrast to a management plane (M-plane), which can provide non-real-time management operations. The distributed unit 604 and the radio unit 606 exchange management information over the fronthaul link via an LLS-M interface.

[0098] The eNB or gNB 602 can include an RRC protocol layer 608 and a PDCP-C protocol layer 610 for control plane signaling, and an SDAP protocol layer 612 and a PDCP-C protocol layer 614 for user plane signaling. In some examples, such functionality can be implemented in one or more control units (not shown in FIG. 6). Figure 6

[0099] The distributed unit 604 includes an RLC protocol layer 616, a MAC protocol layer 618, and higher layer functionality of a physical layer (PHY-high 620). A CUS plane protocol layer 622 communicates control plane and user plane information via the LLS-CUS interface. An M-plane protocol layer 624 communicates management plane information via the LLS-M interface.

[0100] ​The radio unit 606 includes a CUS plane protocol layer 626 that communicates control plane and user plane information via the LLS-CUS interface, and an M plane protocol layer 628 that communicates management plane information via the LLS-M interface. The radio unit 606 includes lower layer functionality of the physical layer (PHY-low 630) and at least one RF chain 632.

[0101] As discussed above, a network can schedule resources for UL and / or DL communications between the network and a UE. For example, the network can schedule a slot for a UE, where the slot includes a number of symbols (e.g., 14 symbols) and a number of resource elements (e.g., 12 REs). As discussed previously, in some examples, a slot can be subdivided into segments, where different segments can carry different types of information (e.g., PDSCH and DMRS). Different modulation schemes can be used to modulate these different types of information. In O-RAN, the scheduling information described above can be sent from the network to the UE via the control plane between the distributed unit and the radio unit.

[0102] In O-RAN systems, C-plane messages are encapsulated using a double-layer header approach. The first layer includes an enhanced common public radio interface (eCPRI) common header or IEEE 1914.3 common header, including a corresponding field to indicate the message type. The second layer is an application layer that includes necessary fields for control and synchronization. Within this application layer, a “segment” defines the characteristics of the U-plane data to be transmitted or received from a beam with one mode identifier (ID). Generally, the transport header, application header, and segment are all intended to be aligned on 4-byte boundaries and transmitted in “network byte order,” which means the most significant byte of a multi-byte parameter is transmitted first.

[0103] Figure 7 An example of a control plane segment configured according to the O-RAN specification is illustrated. As shown, a number of resource elements have time and frequency for PDSCH (i.e., symbols 0-13 in the time dimension and a number of resource blocks in the frequency). The purpose of each segment (e.g., 702, 704, 706) is to collect a group of tones and associate them with a particular attribute, such as, for example, beamforming weights. In this example, each segment is non-overlapping, and segments are created for groups of symbols / RBs with the same mode (e.g., 704-1, 704-2, and 704-3 have the same mode, and 706-1 and 706-2 share another mode).

[0104] Further, each segment can be further divided into “segment invocations” with different RE masks (resource element masks are also referred to as tone masks). In this example, a set of weights can be applied to each segment invocation, and each segment can have a unique segment ID. For example, symbol 0 can have a segment ID, but three invocations, where: (1) invocation 1 is CSI RS port 1 (e.g., such as shown in hatching at 708) and RE mask: 0000 0011 0000; (2) invocation 2 is CSI RS port 2 (e.g., such as shown in hatching at 710) with RE mask: 0011 0000 0000; and (3) invocation 3, which is PDSCH (e.g., such as shown in light hatching at 712) with RE mask: 1100 1100 1111.

[0105] In another example, symbols 1, 2, 3, 5, 6, 7, 10, 11, 12, 13 have a segment ID, but only a single invocation for that segment (i.e., segment 704), which can be invocation 4 (shown in light hatching) that is PDSCH with RE mask: 1111 1111 1111. Yet further, a third segment 706 at symbols 4 and 8 can also have a segment ID that includes two invocations: (1) invocation 5, which includes a tracking reference signal (TRS), e.g., such as shown in dark hatching at 714, and has RE mask: 01000100 010; and (2) and invocation 6, which is PDSCH (light hatching) and has RE mask: 1011 1011 1011. Thus, note that in this example, there are six invocations. Figure 7

[0106] Further of note is that O-RAN specifications (e.g., O-RAN WG4.CUS.0-v04.00 or O-RAN WG4.CUS.0-v06.00) include methodologies to couple user plane and control plane. One methodology includes coupling user plane and control plane via frequency and time (see, e.g., O-RAN WG4.CUS.0, Chapter 5.4.1.2.2). Another methodology includes coupling user plane and control plane via frequency and time with priority (e.g., O-RAN WG4.CUS.0, Chapter 5.4.1.2.3). In the case of coupling via frequency and time with priority, the mechanism allows more than one data segment to describe a single resource element (RE) in a single C-plane message. Data segments referring to the same RE within the same C-plane message can have different priorities in order to avoid ambiguity.

[0107] Figure 8 ​An example of segments in a time / frequency grid including priorities as specified in the O-RAN specification is illustrated. In this example, using a mechanism coupled with priorities can allow segments to overlap, as can be seen higher priority segments 802 and 804 overlap with lower priority segments 806 or 808. Additionally, these segments do not need unique IDs, such as Figure 7 In the example. Base segments or layers 806 or 808 have a low priority, which can overlap with high priority segments or layers (e.g., 802 or 804), such that the low priority tones of the base segments or layers can be punctured. Additionally, note that for the high priority segment 802 occurring during symbol 0, this single segment has 2 invocations: invocation 2, which is CSI RS port 1 (e.g., shown at shade 810) and has an RE mask of: 0000 0011 0000; and invocation 3, which is CSI RS port 2 (e.g., shown at shade 812) and has an RE mask of 0011 0000 0000. Further, the high priority segment 804 at symbols 4 and 8 has one invocation, which can be denoted as invocation 4, which includes TRS (e.g., shown in dark shade 814) and has an RE mask of 0100 0100 0100. Still further, the low priority segments 806 or 808 are base segments that include all symbols and all RBs. These segments include invocation 1, which is for PDSCH and has an RE mask of 1111 1111 1111. Note that in this example, only 4 segment invocations provide the savings of the required invocations (e.g., compared to 6 invocations in the example of Figure 7 4 invocations represents a 1.5x savings compared to 6 invocations in the example of). In more complex examples, the savings can be even more significant, with more than a three-fold savings. It is important to note that the generation of such segments is much easier for the DU to create, but they are much more complex for the RU to handle.

[0108] According to the O-RAN specification, if a prioritized segment set description does not fit into one C-Plane message, the segment can be split into several messages. In Figure 9 An example illustrating this bifurcation showing two messages 902 and 904 is illustrated in. Further note that if a segment description set does not fit into one C-Plane message, the sender (e.g., DU) will duplicate the highest priority data segment description. This can be seen at 906 in Figure 9 where the high priority value (+1) is shown for the particular high priority segment description (e.g., reference signaling) that is being repeated or duplicated. In one particular example, the C-Plane message can be concerned with beamforming configuration, where the complete configuration can not be transmitted in a single message from the DU to the RU. Each C-Plane message will contain the highest priority segment description that references any REs referenced in the message. This ensures that the RU will correctly interpret the configuration received in each message.

[0109] As a further illustration, Figure 10 A message one 1002 for a first user (user 1) is shown on the left, which contains a high priority reference signal (1004). Additionally, a message two 1006 on the right is transmitted, which has a second copy of the high priority reference signal 1004 and contains a second user (user 2) in a different resource block. This example illustrates that splitting and repetition of the high priority section can be performed. Additionally, the same high priority descriptor (or message) for the reference signal can be repeated in two or more messages.

[0110] Notably, according to the above Figure 9 and 10 example, the highest priority section description can be repeated across multiple messages in order to properly interpret each message. However, this can cause problems for the receiving RU. Specifically, typically each message will be processed independently in the RU, possibly by different processors, with no coordination between them. For example, in the case of a section of interest beamforming configuration, this can result in the RU applying beamforming weights for the REs in the highest priority section multiple times. To avoid this problem, the RU can be configured to track the weights that have been processed for each RE. This requires the RU to maintain state on a per-RE basis across all layers and symbols. Such state management is memory intensive. As an example, to maintain state for 64 layers, 275 RBs, 12 REs, and 14 symbols requires 275*64*12*14 states, which would require approximately 3M bits of memory. Maintaining such state requires, for example, high speed dedicated memory as part of the beamforming hardware block in the RU. This amount of memory would significantly increase the hardware size of the RU, and thus the cost of the RU. Furthermore, such stateful operations can require synchronization between independent processing entities in the RU, resulting in unacceptable latency.

[0111] In view of the above, the present disclosure, in some aspects, is directed to alleviating the need to maintain memory state by providing an indication as to when a high priority section (e.g., the highest priority section with the largest priority value) is being repeated. In some aspects, this indication can be conveyed in a control message, such as an extension to the section header included in the data section. In a particular example, the indication that a high priority section is being repeated can be implemented by placing a value or indication in a particular section extension, such as section extension 6 (i.e., extType 6) as defined by the O-RAN specification. Note that while the present example discussed below illustrates the conveyance of a repeated high priority section, different sections, section extension types, and / or particular fields or IDs can be used.

[0112] In some examples, as Figure 11As shown, an extended Type 6 information element 1100 can be used, although the present disclosure is not so limited. In this particular example, the DU (e.g., DU 416 in FIG. 4, Figure 4 DU 506 or 508 in FIG. 5, or Figure 5 DU 604 in FIG. 6) can be configured to use the priority field 1102 in the N+6 octets of the extension 1100, which in some examples can be a two-bit field. Specifically, the priority value in this field 1102 can be predetermined to be a value that has not been previously utilized, such as the value -2 in one example. Thus, when the RU (e.g., RU 410 in FIG. 4, Figure 6 RU 510, 512, or 514 in FIG. 5, or Figure 4 DU 606 in FIG. 6) receives and parses this extension 1100 (and in particular the priority field 1102), the RU is informed. Figure 5 Figure 6 Another example of an extended Type 6 information element 1200 that can be used is illustrated, where a field is utilized to indicate to the RU that a high priority section will be repeated. In this particular example, the DU can be configured to use the reserved field 1202 in the N+2 octets of the extension 1200. Specifically, the priority value in this field 1202 can be a single bit value, where the setting of this bit (e.g., set to state "1") is used to indicate to the receiving RU that a high priority section (e.g., the highest value priority section) will be repeated.

[0113] Figure 12 According to yet further aspects, the DU can provide the indication of a repeated high priority section by using other types of control messages. That is, in one example, the control message can include a "Section ID" which is referred to as "sectionld" in the RAN WG4.CUS.0 specification, which is then used to identify any repeated high priority section. In one aspect, this section ID is another extension or another field in another section used to provide identification of the section. At the receiving side (i.e., at the RU), note that the RU can be configured to track which section IDs have been processed. Based on the tracking of the processed section IDs, the RU can determine when a high priority section is repeated or will be repeated.

[0114] According to yet further aspects, the DU can provide the indication of a repeated high priority section by using other types of control messages. That is, in one example, the control message can include a "Section ID" which is referred to as "sectionld" in the RAN WG4.CUS.0 specification, which is then used to identify any repeated high priority section. In one aspect, this section ID is another extension or another field in another section used to provide identification of the section. At the receiving side (i.e., at the RU), note that the RU can be configured to track which section IDs have been processed. Based on the tracking of the processed section IDs, the RU can determine when a high priority section is repeated or will be repeated.

[0115] ​In a further aspect, it is noted that there can be an extreme case when no repetition indication or message, the DU is forced to send beam weights (e.g., “beamWeights”) on all repetitions to the RU, which significantly wastes the fronthaul bandwidth. Accordingly, in a further aspect, it is noted that when a control message is used to indicate the repetition of a high priority section, whether by using a field in the section extension (or a repetition flag or bit in the field), or a section ID, the DU can be further configured to include transmitting beam weights (e.g., beamWeights) along with beam identifiers (e.g., beamId) on the first repetition of the highest priority section sent over the fronthaul to the RU. However, for subsequent repetitions, the DU can be configured to only send beam identifiers (beamId). This configuration allows the DU to not repeat sending beam weights, which results in a saving of fronthaul bandwidth.

[0116] Figure 13 is a block diagram illustrating an example of a hardware implementation for a radio 1300 employing a processing system 1314, e.g., an O-RU configured for an O-RAN system. For example, the radio 1300 can be configured to wirelessly communicate with a UE as discussed in any one or more of 1, 2, 3, 4, or 5. In some examples, the radio 1300 can equivalently be referred to as a radio device, a network node, a scheduling entity, a base station, or referenced in some other manner. In some implementations, the radio (RU) 1300 can correspond to at least a portion of any of the BSs (e.g., eNBs and / or gNBs) or scheduling entities illustrated in FIGs. 1, 2, 3, 4, 5, and / or 6. Figure 1 、 2 Figure 1 、 2

[0117] According to various aspects of the disclosure, an element, or any portion of an element, or any combination of elements can be implemented with a processing system 1314. The processing system 1314 can include one or more processors 1304. Examples of processors 1304 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described

[0118] ​​In some examples, the processor 1304 can be implemented via a baseband or modem chip, while in other implementations the processor 1304 can itself include a number of distinct devices (e.g., in such scenarios that can work cooperatively to achieve the embodiments discussed herein) that are separate and distinct from a baseband or modem chip. And as mentioned above, various hardware arrangements and components outside of a baseband modem processor can be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0119] In this example, the processing system 1314 can be implemented with a bus architecture, as represented generally by the bus 1302. The bus 1302 can include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1314 and the overall design constraints. The bus 1302 communicatively couples various circuits including one or more processors (represented generally by the processor 1304), memory 1305, and computer-readable media (represented generally by the computer-readable media 1306). The bus 1302 can also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be further described. A bus interface 1308 provides an interface between the bus 1302 and a transceiver 1310 and between the bus 1302 and an interface 1330. The transceiver 1310 provides a communication interface or means for communicating with various other apparatus over a wireless transmission medium. In some examples, a radio can include two or more transceivers 1310 each configured to communicate with a respective network type (e.g., terrestrial or non-terrestrial). The interface 1330 provides a communication interface or means for communicating with various other devices and equipment such as other devices housed within the same apparatus as the radio unit or other external devices over an internal bus or an external transmission medium such as an Ethernet cable. Depending upon the nature of the apparatus, the interface 1330 can include a user interface. Of course, such a user interface is optional and can be omitted in some examples.

[0120] The processor 1304 is responsible for managing the bus 1302 and general processing, including the execution of software stored on the computer-readable medium 1306. The software, when executed by the processor 1304, causes the processing system 1314 to perform the various functions described below for any particular apparatus. The computer-readable medium 1306 and the memory 1305 can also be used for storing data used by the processor 1304 when executing software.

[0121] One or more processors 1304 in the processing system can execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software can reside on a computer-readable medium 1306.

[0122] Computer-readable medium 1306 can be a non-transitory computer-readable medium. A non-transitory computer-readable medium includes, for example, magnetic storage devices (e.g., hard disk; floppy disk); optical disk devices (e.g., compact disk (CD); digital versatile disk (DVD)); smart cards; flash memory devices (e.g., card; stick; key drive); random access memories (RAMs); read only memories (ROMs); programmable ROMs (PROMs); erasable PROMs (EPROMs); electrically erasable PROMs (EEPROMs); registers; removable disk; and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 1306 can reside in the processing system 1314, external to the processing system 1314, or distributed across multiple entities including the processing system 1314. Computer-readable medium 1306 can be embodied in a computer program product. By way of example, a computer program product can include a computer-readable medium in packaging material. Those skilled in the art will recognize how to best im plement the described functionality for each aspect of the disclosure, given the

[0123] The radio 1300 can be configured to perform any one or more of the operations described herein (e.g., as described above in connection with Figures 1-11 and as described below in connection with Figure 14 In some aspects of the disclosure, a processor 1304 as utilized in the radio 1300 can include circuitry configured for the various functions.

[0124] The processor 1304 can include communication and processing circuitry 1341. The communication and processing circuitry 1341 can be configured to communicate with a UE via the transceiver 1310 (or RF elements thereof) and antenna array 1320. In other aspects, the communication and processing circuitry 1341 can be used to communicate with a DU via the transceiver 1310 (or network communication elements thereof) and a fronthaul link.

[0125] In some implementations in which the communication involves receiving information, the communication and processing circuitry 1341 can obtain information from a component of the radio 1300 (e.g., from a transceiver 1310 that receives information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1341 can output the information to another component of the processor 1304, to the memory 1305, or to the bus interface 1308. In some examples, the communication and processing circuitry 1341 can receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1341 can receive the information via one or more channels. In some examples, the communication and processing circuitry 1341 can include functionality for means for receiving.

[0126] In some implementations in which the communication involves sending (e.g., transmitting) information, the communication and processing circuitry 1341 can obtain information from (e.g., from another component of the processor 1304, the memory 1305, or the bus interface 1308), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 1341 can output the information to the transceiver 1310 (e.g., to transmit the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1341 can send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1341 can send the information via one or more channels. In some examples, the communication and processing circuitry 1341 can include functionality for means for sending (e.g., means for transmitting).

[0127] The processor 1304 can include control plane processing circuitry 1342 configured to perform control plane processing related operations as discussed herein (e.g., receiving a control plane message from a DU via a downlink and obtaining an indication of a repeated high priority message from the control plane message). The control plane processing circuitry 1342 can include functionality for means for obtaining an indication of a repeated high priority message from a control message (e.g., an extended Type 6 message). The control plane processing circuitry 1342 can be further configured to execute control plane processing software 1352 included on the computer-readable medium 1306 to implement one or more functions described herein.

[0128] The processor 1304 can include resource management circuitry 1343 configured to perform resource management related operations as discussed herein (e.g., via time slot communication). The resource management circuitry 1343 can include functionality for means for communicating information during a time slot. The resource management circuitry 1343 can be further configured to execute resource management software 1353 included on the computer-readable medium 1306 to implement one or more functions described herein.

[0129] Figure 14 is a flowchart illustrating an example method 1400 for a wireless communication system, in accordance with some aspects of the present disclosure. As described below, some or all illustrated features can be omitted in some implementations, and some illustrated features can not be required for implementation of all embodiments. In some examples, the method 1400 can be performed by a radio unit (RU) 1300 as illustrated in FIG. 13. Figure 13 In some examples, the method 1400 can be performed by any suitable apparatus or means for implementing the functions or algorithms described below.

[0130] At block 1402, the radio unit (such as the radio unit 1300) includes receiving a control message from a network node on a fronthaul link, where the control message includes at least one field indicating when transmission of a prioritized data section is repeated. In an aspect, the transceiver 1310 and / or the communication and processing circuitry 1341, or equivalents thereof, can provide means for receiving the control message from the network node on the fronthaul link.

[0131] Further, the method 1400 includes processing the control message including prioritized data that is repeated based on the indication of the at least one field, as shown in block 1404. In an aspect, the control plane processing circuitry 1342, or equivalents thereof, can provide means for receiving the control message from the network node on the fronthaul link.

[0132] According to a further aspect, the control message is a control plane (C-plane) message configured for transmission on the fronthaul link. Additionally, the C-plane message includes a data section extension including the at least one field indicating when transmission of the prioritized data section is repeated.

[0133] In a further aspect, the data section extension includes an Open Radio Access Network (O-RAN) extension type 6 information element. According to a further aspect, the at least one field is configured to indicate a predetermined bit value signaling that transmission of the prioritized data section is being repeated. As just one example, the predetermined bit value can be negative two. In yet further examples, the at least one field is one of at least one bit of a predetermined priority field of bits in the extension type 6 information element or a reserved bit field of bits in the extension type 6 information element.

[0134] In yet other examples, the prioritized data segment being repeated includes a copy of at least one highest priority data segment description. In yet another example, the prioritized data segment being repeated is related to a beamforming configuration communicated in two or more control messages. Further, the network node in communication with the RU can be a distributed unit (DU), such as in Figure 4 、 5 , 6, or 15 (to be discussed below).

[0135] According to yet further aspects, the method 1400 can include receiving an indication of a repeated highest priority segment based on a segment ID communicated by the DU. Further, the method 1400 can include the RU tracking or determining which segment IDs have been processed, and then determining when the highest priority segment will be repeated based on the tracking. In an aspect, one or more of the transceiver 1310, the communication and processing circuitry 1341, the control plane processing circuitry 1342, or the resource management circuitry 1343 can provide means for receiving and processing segment IDs, tracking processed segment IDs, and determining when the highest priority segment will be repeated based on tracking processed segment IDs.

[0136] In further aspects, the method 1400 can include receiving a transmission of beam weights (e.g., beamWeights) along with a beam identifier (e.g., beamId) from the DU on a first repetition or transmission of the highest priority segment. However, for subsequent repetitions of the highest priority segment, the RU receives only the beam identifier (beamId) from the DU. In an aspect, one or more of the transceiver 1310, the communication and processing circuitry 1341, the control plane processing circuitry 1342, or the resource management circuitry 1343 can provide means for receiving and processing the beamId and beamWeights on the first transmission, and receiving and processing only the beamId on subsequent transmissions when determining when the highest priority segment will be repeated.

[0137] Figure 15 is a conceptual diagram illustrating an example of a hardware implementation for a network node 1500, such as a distributed unit (e.g., an O-DU operable according to O-RAN standards) employing a processing system 1514. In some examples, the network node can equivalently be referred to as a network device, a distributed unit, a scheduling entity, a base station, or referenced in some other manner. In some implementations, the network node 1500 can correspond to any of the BSs (e.g., eNBs and / or gNBs) or scheduling entities shown in Figure 1 、 2 , 4, 5, and / or 6.

[0138] According to various aspects of the disclosure, an element, or any portion of an element, or any combination of elements can be implemented with the processing system 1514. The processing system can include one or more processors 1504. The processing system 1514 can be substantially similar to the processing system 1214 as illustrated in FIG. 12, including bus interface 1508, bus 1502, memory 1505, processor 1504, and computer-readable medium 1506. Moreover, the network node 1500 can include an interface 1530 (e.g., network interface) that provides means for communicating with at least one other apparatus within a core network and within at least one radio access network. Figure 12

[0139] The network node 1500 can be configured to perform any one or more of the operations described herein (e.g., as described above in connection with FIGS. 1-11, and as described below in connection with FIG. 12). In some aspects of the disclosure, the processor 1504, as utilized in the network access node 1500, can include circuitry configured for various functions. Figures 1-12 Figure 16

[0140] The processor 1504 can be configured to generate, schedule, and modify resource assignments or grants of time-frequency resources (e.g., sets of one or more resource elements). For example, the processor 1504 can schedule time-frequency resources within a plurality of time division duplex (TDD) and / or frequency division duplex (FDD) subframes, slots, and / or mini-slots to carry user data traffic and / or control information to and / or from a plurality of UEs. The processor 1504 can be configured to schedule resources for downlink signal transmission. The processor 1504 can be further configured to schedule resources for uplink signal transmission.

[0141] In some aspects of the disclosure, the processor 1504 can include communication and processing circuitry 1541. The communication and processing circuitry 1541 can include one or more hardware components that provide the physical structure that performs various processes related to communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuitry 1541 can further include one or more hardware components that provide the physical structure that performs various processes related to signal processing (e.g., processing a received signal and / or processing a signal for transmission) as described herein. The communication and processing circuitry 1541 can be further configured to execute communication and processing software 1506 included on the computer-readable medium 1551 to implement one or more functions described herein.

[0142] ​​​In some implementations in which the communication involves receiving information, the communication and processing circuitry 1541 can obtain information from a component of the network node 1500 (e.g., from the transceiver 1510 that receives information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1541 can output the information to another component of the processor 1504, to the memory 1505, or to the bus interface 1508. In some examples, the communication and processing circuitry 1541 can receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1541 can receive the information via one or more channels. In some examples, the communication and processing circuitry 1541 can include functionality for means for receiving.

[0143] In some implementations in which the communication involves sending (e.g., transmitting) information, the communication and processing circuitry 1541 can obtain information from (e.g., from another component of the processor 1504, the memory 1505, or the bus interface 1508), process (e.g., encode) the information, and output the processed information. For example, the communication and processing circuitry 1541 can output the information to the transceiver 1510 (e.g., to transmit the information to one or more radio units (RUs) via a fronthaul link). In some examples, the communication and processing circuitry 1541 can send one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1541 can send the information via one or more channels. In some examples, the communication and processing circuitry 1541 can include functionality for means for sending (e.g., means for transmitting).

[0144] The processor 1504 can include priority indication circuitry 1542 configured to perform the indication of repetition of high priority segments as discussed herein. The priority indication circuitry 1542 can include functionality for means for generating a control message. The priority indication circuitry 1542 can be further configured to include priority indication software 1552 included on the computer-readable medium 1506 to implement one or more functions described herein.

[0145] The processor 1504 can further include control plane processing circuitry 1543 configured to perform control plane processing related operations as discussed herein (e.g., generating and transmitting a control plane message including the priority indication to a radio unit). The control plane processing circuitry 1543 can include functionality for means for generating a control message. The control plane processing circuitry 1543 can be further configured to execute control plane processing software 1553 included on the computer-readable medium 1506 to implement one or more functions described herein. In some examples, the priority indication circuitry 1542 and / or the control plane processing circuitry 1543 can be configured to generate and / or transmit a control signal or message including a repetition flag or bit in a field, such as discussed above in connection with Figure 11 or 12. In other examples, the priority indication circuitry 1542 and / or the control plane processing circuitry 1543 can be configured to transmit or generate a control signal or message including a Section ID in a section, where the Section ID is configured to convey or signal to the RU whether a high priority section is to be repeated.

[0146] Figure 16 is a flow diagram illustrating an example method 1600 for a wireless communication system, in accordance with some aspects of the present disclosure. As described below, some or all of the features illustrated can be omitted in some implementations, and some illustrated features can not be required for implementation of all embodiments. In some examples, the method 1600 can be performed by a network node 1500 (e.g., a DU or O-DU) as illustrated in FIG. 15, within the scope of the present disclosure. In some examples, the method 1600 can be performed by any suitable apparatus or means adapted according to the functions or algorithms described below. Figure 15 is a flow diagram illustrating an example method 1600 for a wireless communication system, in accordance with some aspects of the present disclosure. As described below, some or all of the features illustrated can be omitted in some implementations, and some illustrated features can not be required for implementation of all embodiments. In some examples, the method 1600 can be performed by a network node 1500 (e.g., a DU or O-DU) as illustrated in FIG. 15, within the scope of the present disclosure. In some examples, the method 1600 can be performed by any suitable apparatus or means adapted according to the functions or algorithms described below.

[0147] At block 1602, the network node can generate a control message including at least one field indicating when transmission of a prioritized data section is repeated. In an aspect, the priority indication circuitry 1542 and / or the control plane processing circuitry 1543, or equivalents thereof, can provide means for generating a control message including at least one field indicating when transmission of a prioritized data section is repeated.

[0148] Further, the method 1600 includes transmitting the control message to a radio unit (RU) over a fronthaul link, as shown in block 1604. In an aspect, the priority indication control plane processing circuitry 1543, the communication and processing circuitry 1541, and / or the transceiver 1510, or equivalents thereof, can provide means for transmitting the control message to the RU over the fronthaul link.

[0149] According to further examples, the control message is a control plane (C-plane) message configured for transmission on a fronthaul link. In one example, the C-plane message includes a data segment extension that includes at least one field indicating when transmission of a prioritized data segment is being repeated. Further, in another example, the data segment extension includes an Open Radio Access Network (O-RAN) extension type 6 information element. Yet further, in one example, the at least one field is configured to indicate a predetermined bit value that signals that transmission of a prioritized data segment is being repeated. According to some aspects, the predetermined bit value is negative two. Additionally, the at least one field is one of at least one of a predetermined priority field of bits in the extension type 6 information element or a reserved bit field of bits in the extension type 6 information element.

[0150] In some other examples, the prioritized data segment being repeated includes a copy of at least one highest priority data segment description. Additionally, in other examples, the prioritized data segment being repeated is related to a beamforming configuration conveyed in two or more control messages.

[0151] According to yet further aspects, the method 1600 can include providing an indication of a repeated high priority segment by using other types of control messages. In an aspect, the method 1600 can include using a segment ID in another extension or another segment that is used to provide an indication of a repeated highest priority segment. In an aspect, the priority indication circuitry 1542 and / or the control plane processing circuitry 1543, or equivalents thereof, can provide a means for using a segment ID to generate and / or provide a control message to indicate when transmission of a prioritized or highest priority data segment is being repeated.

[0152] In further aspects, the method 1600 can further include providing a beam weight (e.g., beamWeights) to a RU along with a beam identifier (e.g., beamld) on a first repetition of a highest priority segment, and then sending only the beam identifier (beamld) to the RU for subsequent repetitions. In an aspect, one or more of the transceiver 1510, the communication and processing circuitry 1541, the priority indication circuitry 1542, or the control plane processing circuitry 1543 can provide a means for transmitting the beamld and the beamWeights on a first transmission, and transmitting only the beamld on subsequent transmissions when the highest priority segment is to be repeated.

[0153] Several aspects of a wireless communication network have been presented with reference to an example implementation. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure can be extended to other telecommunication systems, network architectures and communication standards.

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

[0155] Aspect 1 : A method of communicating at a network node, the method comprising: generating a control message comprising at least one field indicating when transmission of a prioritized data section is repeated; and transmitting the control message to a radio unit (RU) over a fronthaul link.

[0156] Aspect 2: The method of aspect 1, wherein the control message is a control plane (C-plane) message configured for transmission over the fronthaul link.

[0157] Aspect 3: The method of aspect 2, wherein the C-plane message comprises a data section extension comprising the at least one field indicating when transmission of the prioritized data section is repeated.

[0158] Aspect 4: The method of any of aspects 1-3, wherein the data section extension comprises an Open Radio Access Network (O-RAN) extension type 6 information element.

[0159] Aspect 5: The method of any of aspects 1-4, wherein the at least one field is configured to indicate a predetermined bit value signaling that transmission of the prioritized data section is being repeated.

[0160] Aspect 6: The method of aspect 5, wherein the predetermined bit value is negative two.

[0161] Aspect 7: The method of any of aspects 5 or 6, wherein the at least one field is one of at least one bit of a predetermined priority field of bits in the extension type 6 information element or a reserved bit field of bits in the extension type 6 information element.

[0162] Aspect 8: The method of any of aspects 1-7, wherein the prioritized data section being repeated comprises a copy of at least one highest priority data section description.

[0163] Aspect 9: The method of any of aspects 1-7, wherein the prioritized data section being repeated is related to a beamforming configuration transmitted in two or more control messages.

[0164] Aspect 10: The method of any of aspects 1-9, wherein the control message comprising the at least one field comprises a section identifier.

[0165] Aspect 11 : The method of any of aspects 1-10, further comprising: transmitting a beam weight and a beam identifier over the fronthaul link with a first transmission of the prioritized data section; and transmitting the beam identifier without the beam weight over the fronthaul link for repeated transmissions of the prioritized data section subsequent to the first transmission.

[0166] Aspect 12: The method of any of aspects 1 through 11, wherein the network node comprises a distributed unit (DU).

[0167] Aspect 13: The method of any of aspects 1 through 12, wherein the prioritized data section comprises a highest priority data section.

[0168] Aspect 14: A network node, comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: generate a control message comprising at least one field indicating when transmission of a prioritized data section is repeated; and transmit, using the transceiver, the control message to a radio unit (RU) on a fronthaul link.

[0169] Aspect 15: The network node of aspect 14, wherein the control message is a control plane (C-plane) message configured for transmission on the fronthaul link.

[0170] Aspect 16: The network node of aspect 15, wherein the C-plane message comprises a data section extension comprising the at least one field indicating when transmission of the prioritized data section is repeated.

[0171] Aspect 17: The network node of aspect 16, wherein the data section extension comprises an Open Radio Access Network (O-RAN) extension type 6 information element.

[0172] Aspect 18: The network node of any of aspects 16 through 17, wherein the control message comprising the at least one field comprises a section identifier configured to indicate repetition of the prioritized data section.

[0173] Aspect 19: The network node of any of aspects 14 through 18, wherein the processor and the memory are further configured to: transmit, on the fronthaul link, a beam weight and a beam identifier with a first transmission of the prioritized data section; and transmit, on the fronthaul link after the first transmission, the beam identifier for repeated transmissions of the prioritized section without transmitting the beam weight.

[0174] Aspect 20: The network node of any of aspects 16 through 19, wherein the network node comprises a distributed unit (DU).

[0175] Aspect 21: The network node of any of aspects 16 through 20, wherein the prioritized data section comprises a highest priority data section.

[0176] Aspect 22: A method for communication at a radio unit (RU), the method comprising: receiving a control message from a network node on a fronthaul link, wherein the control message includes at least one field indicating when transmission of a prioritized data section is repeated; and processing the control message including the prioritized data section that is repeated based on the indication of the at least one field.

[0177] Aspect 23: The method of aspect 22, wherein the control message is a control plane (C-plane) message configured for transmission on the fronthaul link.

[0178] Aspect 24: The method of aspect 23, wherein the C-plane message includes a data section extension including the at least one field indicating when transmission of the prioritized data section is repeated.

[0179] Aspect 25: The method of aspect 24, wherein the data section extension includes an Open Radio Access Network (O-RAN) extension type 6 information element.

[0180] Aspect 26: The method of any of aspects 22 through 25, wherein the network node comprises a distributed unit (DU).

[0181] Aspect 27: The method of any of aspects 22 through 26, wherein the control message including the at least one field includes a section identifier configured to indicate repetition of the prioritized data section.

[0182] Aspect 28: The method of any of aspects 22 through 27, further comprising: receiving a beam weight and a beam identifier on the fronthaul link with a first transmission of the prioritized data section; and receiving the beam identifier without the beam weight on the fronthaul link for subsequent repeated transmissions of the prioritized data section after the first transmission.

[0183] Aspect 29: The method of any of aspects 22 through 28, wherein the prioritized data section comprises a highest priority data section.

[0184] Aspect 30: A radio unit (RU), comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: receive a control message from a network node on a fronthaul link, wherein the control message includes at least one field indicating when transmission of a prioritized data section is repeated; and process the control message including the prioritized data section that is repeated based on the indication of the at least one field.

[0185] Aspect 31: An apparatus configured for wireless communication includes at least one means for performing a method of any of aspects 1 through 13 or aspects 22 through 29.

[0186] Aspect 32: A non-transitory computer-readable medium storing computer-executable code including code for causing an apparatus to perform a method of any of aspects 1 through 13 or aspects 22 through 29.

[0187] By way of example, various aspects can be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE), Evolved Packet System (EPS), the Universal Mobile Telecommunication System (UMTS), and / or the Global System for Mobile (GSM). Various aspects can also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wide Band (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0188] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation. The term "coupled" is used herein to express a direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then objects A and C can still be considered coupled to one another, even though they are not directly physically in contact with one another. For instance, a first object can be coupled to a second object even though the first object is never directly physically in contact with the second object. The terms "circuit" and "circuitry" are used broadly, and intended to include both hardware implementations of electrical devices, and software implementations of information and instructions that, when executed by a processor, cause the processor to implement the described functionality of the circuitry. The term "processor" is used broadly herein, and is intended to include a single processor, multiple processors, a combination of processors and circuits, and other processing devices operating as a single processor.

[0189] Figures 1-16 One or more of the components, steps, features and / or functions illustrated in the Figures can be rearranged and / or combined into a single component, step, feature or function or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions can also be added without departing from the novel features disclosed herein. Figure 1 、 2The apparatuses, devices, and / or components illustrated in one or more of FIGs. 1, 4-6, 13, or 15 can be configured to perform one or more of the methods, features, or steps described herein. Novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

[0190] It should be understood that the particular order or hierarchy of steps in the methods disclosed are merely examples of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods can be re-arranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

[0191] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. The phrase "at least one of' a list of items refers to any combination of those items, including single members. As an example, "at least one of: a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

1. A method of communicating at a network node, the method comprising: transmitting a first message in a first slot, the first slot being subdivided into one or more segments, each segment comprising one or more symbols, each symbol comprising one or more resource blocks, each segment having a unique pattern of resource elements, wherein at least one segment has a higher priority than another segment of the one or more segments; transmitting a control message comprising a data segment extension, the data segment extension comprising an Open Radio Access Network (O-RAN) extension type 6 information element, the O-RAN extension type 6 information element indicating that the at least one segment having the higher priority is to be repeated; and transmitting a second message in a second slot, the second slot comprising a repetition of the at least one segment having the higher priority.

2. The method of claim 1, wherein the control message is a control plane (C-plane) message configured for transmission on a fronthaul link.

3. The method of claim 1, wherein the information element is configured to indicate a predetermined bit value signaling that transmission of the at least one segment having the higher priority is to be repeated.

4. The method of claim 3, wherein the predetermined bit value is negative two.

5. The method of claim 1, wherein the information element is one of at least one bit of a predetermined priority field of bits in the extension type 6 information element or a reserved bit field of bits in the extension type 6 information element.

6. The method of claim 1, wherein the at least one segment having the higher priority comprises at least one of: a channel state information reference signal (CSI-RS), or a tracking reference signal (TRS).

7. The method of claim 1, wherein the at least one segment having the higher priority is related to a beamforming configuration transmitted in two or more control messages.

8. The method of claim 1, wherein the control message comprises a segment identifier.

9. The method of claim 1, further comprising: transmitting a beam weight and a beam identifier with the first message; and transmitting the beam identifier without the beam weight with the second message.

10. The method of claim 1, wherein the network node comprises a distributed unit (DU).

11. The method of claim 1, wherein the higher priority of the at least one segment having the higher priority is a highest priority among the one or more segments.

12. A network node, comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: ​ transmitting a first message in a first slot, the first slot being subdivided into one or more segments, each segment comprising one or more symbols, each symbol comprising one or more resource blocks, each segment having a unique pattern of resource elements, wherein at least one segment has a higher priority than another segment of the one or more segments; transmitting a control message comprising a data segment extension, the data segment extension comprising an Open Radio Access Network (O-RAN) extension type 6 information element, the O-RAN extension type 6 information element indicating that the at least one segment having the higher priority is to be repeated; and transmitting a second message in a second slot, the second slot comprising a repetition of the at least one segment having the higher priority.

13. The network node of claim 12, wherein the control message is a control plane (C-plane) message configured for transmission on a fronthaul link.

14. The network node of claim 12, wherein the information element is configured to indicate a predetermined bit value signaling that transmission of the at least one segment having the higher priority is to be repeated.

15. The network node of claim 14, wherein the predetermined bit value is negative two.

16. The network node of claim 12, wherein the information element is one of at least one bit of a predetermined priority field of bits in the extension type 6 information element or a reserved bit field of bits in the extension type 6 information element.

17. The network node of claim 12, wherein the at least one segment having the higher priority comprises at least one of: a channel state information reference signal (CSI-RS), or a tracking reference signal (TRS).

18. The network node of claim 12, wherein the at least one segment having the higher priority relates to beamforming configuration transmitted in two or more control messages.

19. The network node of claim 12, wherein the control message comprises a segment identifier configured to indicate repetition of a prioritized data segment.

20. The network node of claim 12, wherein the processor and the memory are further configured to: transmit a beam weight and a beam identifier with the first message; and transmit the beam identifier without the beam weight with the second message.

21. The network node of claim 12, wherein the network node comprises a distributed unit (DU).

22. The network node of claim 12, wherein the higher priority of the at least one segment having the higher priority is a highest priority among the one or more segments.

23. A method for communicating at a radio unit, the method comprising: transmitting a first message in a first slot, the first slot being subdivided into one or more segments, each segment comprising one or more symbols, each symbol comprising one or more resource blocks, each segment having a unique pattern of resource elements, wherein at least one segment has a higher priority than another segment of the one or more segments; transmitting a control message comprising a data segment extension, the data segment extension comprising an Open Radio Access Network (O-RAN) extension type 6 information element, the O-RAN extension type 6 information element indicating that the at least one segment having the higher priority is to be repeated; and transmitting a second message in a second slot, the second slot comprising a repetition of the at least one segment having the higher priority. receiving a first message in a first slot, the first slot being subdivided into one or more segments, each segment comprising one or more symbols, each symbol comprising one or more resource blocks, each segment having a unique pattern of resource elements, wherein at least one segment has a higher priority than another segment of the one or more segments; receiving a control message comprising a data segment extension, wherein the data segment extension comprises an Open Radio Access Network (O-RAN) extension type 6 information element, the O-RAN extension type 6 information element indicating that the at least one segment having the higher priority is to be repeated; and receiving a second message in a second slot, the second slot comprising a repetition of the at least one segment having the higher priority.

24. The method of claim 23, wherein the control message is a control plane (C-plane) message configured for transmission on a fronthaul link.

25. The method of claim 23, wherein the radio is to receive the first message, the control message, and the second message from a distributed unit (DU).

26. The method of claim 23, further comprising: receiving a beam weight and a beam identifier with the first message; and receiving the beam identifier with the second message without receiving the beam weight.

27. The method of claim 23, wherein the higher priority of the at least one segment having the higher priority is a highest priority among the one or more segments.

28. A radio comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: receive a first message in a first slot, the first slot being subdivided into one or more segments, each segment comprising one or more symbols, each symbol comprising one or more resource blocks, each segment having a unique pattern of resource elements, wherein at least one segment has a higher priority than another segment of the one or more segments; receive a control message comprising a data segment extension, wherein the data segment extension comprises an Open Radio Access Network (O-RAN) extension type 6 information element, the O-RAN extension type 6 information element indicating that the at least one segment having the higher priority is to be repeated; and receive a second message in a second slot, the second slot comprising a repetition of the at least one segment having the higher priority.

29. The radio of claim 28, wherein the control message is a control plane (C-plane) message configured for transmission on a fronthaul link.

30. The radio of claim 28, wherein the radio is to receive the first message, the control message, and the second message from a distributed unit (DU).

31. The radio of claim 28, wherein the processor and the memory are further configured to: receive a beam weight and a beam identifier with the first message; and ​ ​ receiving the beam identifier with the second message without receiving the beam weights.

32. The radio unit of claim 28, wherein the higher priority of the at least one segment having the higher priority is a highest priority among the one or more segments.

Images