Wireless communication method operable in a scheduled entity, memory, and wireless communication device.

Abstract

Aspects related to new radio (NR) transmissions of uplink control information (UCI) are revealed. In a particular example, a priority is assigned to each of the various UCI components such that the priority is assigned according to at least one of the types or sizes of payload respectively associated with each of the various UCI components. The various UCI components are then transmitted based on the priority assigned respectively to each of the various UCI components.

Description

1 / 60 “WIRELESS COMMUNICATION METHOD OPERATED IN A SCHEDULED ENTITY, MEMORY, AND WIRELESS COMMUNICATION DEVICE CROSS-REFERENCE WITH RELATED REQUEST(S)

[0001] This application claims priority and benefit of U.S. Provisional Patent Application No. 62 / 517,090, filed June 8, 2017; and of Patent Application No. US Provisional No. 16 / 002,912, filed on June 7, 2018, the contents of which are incorporated herein by reference as if fully set forth below in their entirety and for all applicable purposes. TECHNICAL FIELD

[0002] The technology discussed below generally relates to wireless communication systems, and more particularly to New Radio (NR) transmissions of uplink control information (UCI). INTRODUCTION

[0003] As the demand for mobile broadband access continues to increase, research and development continues to advance wireless communication technologies, not only to meet the growing demand for mobile broadband access, but also to advance and enhance the user experience with mobile communications. New Radio access technologies, such as New Radio Access (NR) 5G technology, promise to make wireless broadband indistinguishable from fixed networks with fiber-like performance at a significantly lower cost per bit.

[0004] In NR, uplink control information (UTI) and / or data can be transmitted via bursts. Petition 870250102952, dated 11 / 11 / 2025, p. 6 / 153 2 / 60 uplink shorts (UL). For example, acknowledgment (ACK) bits can be transmitted via short UL bursts of one or two symbols. However, UCI payloads are generally very large, requiring more than two symbols. With regard to channel status information (CSI) reporting, for example, payloads can be on the order of tens of bits per component carrier (CC) for periodic CSI reporting and on the order of hundreds of bits per CC for aperiodic CSI reporting. Other factors that can generate larger payloads include whether a multiple CC scheme is used (e.g., 32 bits per CC in LTE), as well as the particular encoding scheme used (e.g., when encoding UCI with polar code, output bits can be up to 1024 bits).

[0005] Currently, several techniques exist for transmitting large UCI payloads. For example, such techniques include reducing the number of simultaneous CCs in a CSI report (e.g., five CCs for spectrum bands below 6 GHz and ten CCs for millimeter wave spectrum bands), encoding with low-density parity check code (LDPC) (i.e., transmitted in PUSCH), and segmenting the payload into multiple polar-encoded code blocks. However, these techniques may not be practical or sufficient for NR. Consequently, it would be desirable to provide techniques for transmitting large UCI payloads in NR that are both reliable and efficient. A brief summary of some examples.

[0006] The following is a simplified summary of one or more aspects of the present disclosure, Petition 870250102952, dated 11 / 11 / 2025, page 7 / 153 3 / 60 in order to provide a basic understanding of such aspects. This summary is not a comprehensive overview of all the features contemplated in the revelation and is not intended to identify key or critical elements of all aspects of the revelation, nor to delineate the scope of one or all aspects of the revelation. Its sole purpose is to present some concepts of one or more aspects of the revelation in a simplified way as a prelude to the more detailed description that will be presented later.

[0007] Several aspects directed at a scheduled entity (e.g., a user equipment (UE)) are revealed. In one example, a method is revealed which includes assigning a priority to each of the various uplink control information (UCI) components, such that the priority is assigned according to at least one of a payload type or size respectively associated with each of the various UCI components. The method further includes transmitting the various UCI components based on the priority respectively assigned to each of the various UCI components.

[0008] In another aspect directed at a scheduling entity, a wireless communication device is revealed, which includes the assignment circuit system and the transmission circuit system. For this example, the assignment circuit system is configured to assign a priority to each of the various UCI components, such that the priority is assigned according to at least one of a type or size of payload respectively associated with each of the various components. Petition 870250102952, dated 11 / 11 / 2025, page 8 / 153 4 / 60 UCI components. The transmission circuit system is then configured to transmit the various UCI components based on the priority assigned to each of the various UCI components, respectively.

[0009] In a further aspect of the disclosure, a computer-readable medium storing executable computer code is disclosed, which includes instructions for causing a processor to perform several acts. For this example, the acts include assigning a priority to each of the various UCI components, such that the priority is assigned according to at least one of a type or size of payload respectively associated with each of the various UCI components. The acts further include transmitting the various UCI components based on the priority assigned, respectively, to each of the various UCI components.

[0010] In yet another aspect of the disclosure, a wireless communication device is disclosed, which includes a means for assigning and a means for transmitting. For this example, the means for assigning is configured to assign a priority to each of the various UCI components, such that the priority is assigned according to at least one of a type or size of payload respectively associated with each of the various UCI components. The means for transmitting is then configured to transmit the various UCI components based on the priority assigned respectively to each of the various UCI components.

[0011] These and other aspects of the invention will become more fully understood by inspecting the detailed description that follows. Other aspects, Petition 870250102952, dated 11 / 11 / 2025, page 9 / 153 5 / 60 The features and embodiments of the present invention will become apparent to those skilled in the art upon inspection of the following description of specific illustrative embodiments of the present invention in conjunction with the accompanying figures. Although the features of the present invention may be discussed in relation to some embodiments and figures below, all embodiments of the present invention may include one or more of the advantageous features discussed in this document. In other words, while one or more embodiments may be discussed as possessing some advantageous features, one or more of these features may also be utilized in accordance with the various embodiments of the invention discussed in this document.Similarly, although illustrative embodiments may be discussed below as device, system, or method embodiments, it should be understood that such illustrative embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG. 1 is a schematic illustration of a wireless communication system.

[0013] FIG. 2 is a conceptual illustration of an example of a radio access network.

[0014] FIG. 3 is a schematic illustration of a wireless resource organization on an air interface using orthogonal frequency division multiplexing (OFDM).

[0015] FIG. 4 is a schematic illustration of autonomous partitions illustrative of some Petition 870250102952, dated 11 / 11 / 2025, page 10 / 153 6 / 60 aspects of the revelation.

[0016] FIG. 5 illustrates illustrative partition structures for transmitting uplink control information (UCI) components according to some aspects of the present disclosure.

[0017] FIG. 6 illustrates illustrative energy transitions for transmitting UCI components according to some aspects of the present disclosure.

[0018] FIG. 7 is a block diagram illustrating an example of a hardware implementation for a scheduling entity employing a processing system.

[0019] FIG. 8 is a flowchart illustrating an illustrative process for processing received UCI components in accordance with some aspects of the present disclosure.

[0020] FIG. 9 is a block diagram illustrating an example of a hardware implementation for a scheduled entity employing a processing system.

[0021] FIG. 10 is a block diagram illustrating a first set of illustrative subcomponents corresponding to the scheduled entity illustrated in FIG. 9

[0022] FIG. 11 is a block diagram illustrating a second set of illustrative subcomponents corresponding to the scheduled entity illustrated in FIG. 9.

[0023] FIG. 12 is a flowchart illustrating an illustrative process for transmitting UCI components in accordance with some aspects of the present disclosure. Petition 870250102952, dated 11 / 11 / 2025, page 11 / 153 7 / 60 DETAILED DESCRIPTION

[0024] The detailed description set forth below, in connection with the accompanying drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described in this document may be practiced. The detailed description includes particular details with the aim of providing a complete understanding of various concepts. However, it will be evident to those skilled in the art that these concepts can be practiced without these particular details. In some cases, well-known structures and components are presented in block diagram form to avoid obscuring these concepts.

[0025] As will be discussed in more detail in this document, the present disclosure includes aspects directed towards new radio (NR) transmissions of uplink control information (UCI). In one particular aspect, techniques for transmitting large UCI payloads are disclosed. For example, when a UCI payload size exceeds a limit, it is contemplated that the transmission of that payload may comprise the transmission of UCI components across multiple packets (e.g., multiple code blocks or in different partitions). For example, a large UCI payload can be divided into multiple code blocks similar to PUSCH through code segmentation. Each code block can be encoded separately with Polar code.

[0026] It is also contemplated that the transmission of large UCI payloads may involve reporting a larger number of component carriers when transmitting a Petition 870250102952, dated 11 / 11 / 2025, page 12 / 153 8 / 60 higher priority UCI component transmission in relation to lower priority UCI component transmission. Several aspects for UCI component transmission according to UCI type are also revealed. For example, it is contemplated that UCI components of a channel status information (CSI) type may be transmitted with a lower priority than UCI components of an acknowledgment (ACK) type and / or scheduling request (SR) type. DEFINITIONS

[0027] RAT: Radio Access Technology. The type of technology or communication standard used for radio access and communication through a wireless air interface. Just a few examples of RATs include GSM, UTRA, E-UTRA (LTE), Bluetooth, and Wi-Fi.

[0028] NR: new radio. Generally refers to 5G technologies and new radio access technology, undergoing definition and standardization by 3GPP Version 15.

[0029] OFDM: Orthogonal Frequency Division Multiplexing. An air interface can be defined according to a two-dimensional grid of feature elements, defined by frequency separation of features, by defining a set of closely spaced frequency tones or subcarriers, and time separation by defining a sequence of symbols having a given duration. By defining the spacing between tones based on the symbol rate, interference between symbols can be eliminated. OFDM channels provide high data rates by allocating a parallel data stream across multiple Petition 870250102952, dated 11 / 11 / 2025, page 13 / 153 9 / 60 subcarriers.

[0030] The various concepts presented through this disclosure can be implemented in a wide variety of telecommunications systems, network architectures, and communication standards. With reference now to FIG. 1, as an illustrative example without limitation, several aspects of the present disclosure are illustrated with reference to a wireless communication system 100. The wireless communication system 100 includes three interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By virtue of the wireless communication system 100, the UE 106 can be enabled to perform data communication with an external data network 110, such as (but not limited to) the Internet.

[0031] RAN 104 may implement any suitable wireless communication technology or technologies to provide radio access to UE 106. As an example, RAN 104 may operate in accordance with the New Radio (NR) specifications of the Third Generation Partnership Project (3GPP), often referred to as 5G. As another example, RAN 104 may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as LTE. 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN. Obviously, many other examples could be used within the scope of this disclosure.

[0032] As illustrated, RAN 104 includes several base stations 108. In general terms, a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells. Petition 870250102952, dated 11 / 11 / 2025, p. 14 / 153 10 / 60 to or from an EU. In different technologies, standards, or contexts, a base station may be referred to variously 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 B Node (NB), an eNode B (eNB), a gNode B (gNB), or some other suitable terminology.

[0033] The 104 radio access network is further illustrated supporting wireless communication for various mobile devices. A mobile device may be referred to as user equipment (UE) in the 3GPP standards, but may 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 communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, terminal, user agent, mobile client, client, or other suitable terminology. A UE may be a device that provides the user with access to network services.

[0034] In this document, a mobile device does not necessarily need to have the ability to move and can be stationary. The term mobile device or mobile appliance refers broadly to a variety of device sets and technologies. Mobile appliances can include various scaled hardware structural components, Petition 870250102952, dated 11 / 11 / 2025, page 15 / 153 11 / 60 modeled and arranged to aid in communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to one another. For example, some non-limiting examples of a mobile device include a cell phone, a mobile phone (cellular), a smartphone, 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 wide range of embedded systems, for example, corresponding to an Internet of Things (IoT).A mobile device may additionally be a car or other means of transport, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multicopter, a quadcopter, a remote control device, a wearable and / or consumer device such as glasses, a wearable camera, a virtual reality device, a smartwatch, a health or fitness tracker, a digital audio player (e.g., MP3 player), a camera, a game console, etc. A mobile device may additionally be a digital home device or smart home device, such as an audio, video and / or multimedia home device, an appliance, a vending machine, smart lighting, a home security system, a smart meter, etc.A mobile device can also be a smart energy device, a security device, a solar panel, or... Petition 870250102952, dated 11 / 11 / 2025, page 16 / 153 A 12 / 60 photovoltaic solar panel; a municipal infrastructure device controlling electricity (e.g., a smart grid), lighting, water, etc.; a corporate and industrial automation device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weaponry, etc. Additionally, a mobile device can provide connected medical or telemedicine support, for example, remote medical assistance. Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may receive preferential treatment or prioritized access to other types of information, for example, in terms of priority access for critical service data transport and / or relevant QoS for critical service data transport.

[0035] Wireless communication between a RAN 104 and a UE 106 can be described as using an air interface. Transmissions through the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmission. According to some aspects of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating from a scheduling entity (described further below; e.g., base station 108). Another way to describe this scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be termed uplink (UL) transmissions. Petition 870250102952, dated 11 / 11 / 2025, p. 17 / 153 13 / 60 In accordance with additional aspects of this disclosure, the term uplink may refer to a point-to-point transmission originating from a scheduled entity (further described below; for example, UE 106).

[0036] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station 108) allocates resources for communication between some or all devices and equipment within its server area or cell. Within the present disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources to one or more scheduled entities. That is, for scheduled communication, UEs 106, which may be scheduled entities, may utilize the resources allocated by scheduling entity 108.

[0037] Base stations 108 are not the only entities that can function as scheduling entities. That is, in some examples, a UE can function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs).

[0038] As illustrated in FIG. 1, a scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106. In general terms, the scheduling entity 108 is a node or device responsible for scheduling traffic on a wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is Petition 870250102952, dated 11 / 11 / 2025, p. 18 / 153 14 / 60 a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., a lease), synchronization or timing information, or other control information from another entity on the wireless communication network, such as the scheduling entity 108.

[0039] In general, base stations 108 may include a return transport channel interface for communication with a portion of the return transport channel 120 of the wireless communication system. The return transport channel 120 may provide a link between a base station 108 and the core network 102. Additionally, in some examples, a return transport channel network may provide interconnection between the respective base stations 108. Various types of return transport channel interfaces may be employed, such as a direct physical connection, a virtual network, among others, using any suitable transport network.

[0040] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, core network 102 may be configured according to an evolved 4G packet core (EPC), or any other suitable standard or configuration.

[0041] With reference now to FIG. 2, by way of example and without limitation, a schematic illustration of a RAN 200 is provided. In some instances, the RAN 200 may be the same as the RAN 104 described above and illustrated in Petition 870250102952, dated 11 / 11 / 2025, page 19 / 153 15 / 60 FIG. 1. The geographic area covered by RAN 200 can be divided into cellular regions (cells) that can be uniquely identified by a user device (UD) based on an identification transmitted by broadcast from an access point or base station. FIG. 2 illustrates macrocells 202, 204, and 206 and a small cell. 208, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors in a cell are served by the same base station. A radio link within a sector can be identified by a unique logical identifier belonging to that sector. In a cell that is divided into sectors, the various sectors within a cell may be formed by groups of antennas with each antenna responsible for communication with the UEs in a part of the cell.

[0042] In FIG. 2, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, a base station may have an integrated antenna or may be connected to an antenna or RRH by feeder cables. In the illustrated example, cells 202, 204 and 126 can be referred to as macrocells, as base stations 210, 212 and 214 supports cells with a large size. Additionally, a base station 218 is represented in small cell 208 (e.g., a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc.) which may overlap one or more macrocells. In this example, cell 208 can be referred to as a small cell because base station 218 supports a Petition 870250102952, dated 11 / 11 / 2025, page 20 / 153 16 / 60 cell with a relatively small size. Cell sizing can be done according to the system design as well as component constraints.

[0043] It should be understood that the 200 radio access network can include any number of base stations and wireless cells. Additionally, a relay node can be implemented to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points for a core network for any number of mobile devices. In some examples, base stations 210, 212, 214 and / or 218 may be the same as the base station / scheduling entity 108 described above and illustrated in FIG. 1.

[0044] FIG. 2 also includes a quadcopter or drone 220, which can be configured to function as a base station. That is, in some examples, a cell may not necessarily be stationary and the geographic area of ​​the cell may move according to the location of a mobile base station, such as the quadcopter 220.

[0045] Within RAN 200, cells may include UEs that may be in communication with one or more sectors of each cell. Additionally, each base station 210, 212, 214, 218, and 220 may be configured to provide an access point to a core network 102 (see FIG. 1) for all UEs in the respective cells. For example, UEs 222 and 224 may be in communication with base station 210; UEs 226 and 228 may be in communication with base station 212; UEs 230 and 232 may be in communication with base station 214 via RRH 216; UE Petition 870250102952, dated 11 / 11 / 2025, page 21 / 153 17 / 60 234 may be in communication with base station 218; and UE 236 may be in communication with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 may be the same as the UE / scheduled entity 106 described above and illustrated in FIG. 1.

[0046] In some examples, a mobile network node (e.g., quadcopter 220) can be configured to function as a UE. For example, quadcopter 220 can operate within cell 202 by communicating with base station 210.

[0047] In a further aspect of RAN 200, sidelink signals can be used between UEs without necessarily depending on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 226 and 228) can communicate with each other using point-to-point (P2P) signals or sidelink signals 227 without relaying this communication through a base station (e.g., base station 212). In a further example, UE 238 is illustrated communicating with UEs 240 and 242. Here, UE 238 can function as a scheduling entity or a primary sidelink device, and UEs 240 and 242 can function as a scheduled entity or as a non-primary (e.g., secondary) sidelink device. In yet another example, a UE can function as a scheduling entity in a device-to-device (D2D), point-to-point (P2P), or vehicle-to-vehicle (V2V) network and / or in a mesh network.In a mesh network example, UEs 240 and 242 can optionally communicate directly with each other. Petition 870250102952, dated 11 / 11 / 2025, page 22 / 153 18 / 60 with the other in addition to communicating with scheduling entity 238. Thus, in a wireless communication system with scheduled access to frequency and time resources and possessing a cellular configuration, a P2P configuration, or a mesh configuration, one scheduled entity and one or more scheduled entities can communicate using the scheduled resources.

[0048] In the 200 radio access network, the ability of an UE to communicate while moving, regardless of its location, is referred to as mobility. The various physical channels between the UE and the radio access network are generally configured, maintained, and released under the control of an access and mobility management function (AMF, not illustrated, part of the 102 core network in FIG. 1), which may include a security context management function (SCMF) that manages the security context for control plane and user plane functionality and a security anchoring function (SEAF) that performs authentication.

[0049] In several aspects of the disclosure, a 200 radio access network can utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, a UE can monitor various signal parameters from its server cell, as well as various parameters from neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more Petition 870250102952, dated 11 / 11 / 2025, page 23 / 153 19 / 60 of neighboring cells. During this period, if the UE moves from one cell to another, or if the signal quality of a neighboring cell exceeds that of the serving cell for a given period of time, the UE may perform a handoff or a handover from the serving cell to the neighboring (target) cell. For example, UE 224 (illustrated as a vehicle, although any suitable UE shape may be used) may move from the geographic area corresponding to its serving cell 202 to the geographic area corresponding to a neighboring cell 206. When the signal strength or quality from neighboring cell 206 exceeds that of its serving cell 202 for a given period of time, UE 224 may transmit a report message to its serving base station 210 indicating this condition. In response, UE 224 may receive a handover command and the UE may undergo a handover to cell 206.

[0050] In a network configured for UL-based mobility, the UL reference signals from each UE can be used by the network to select a server cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs), unified Secondary Synchronization Signals (SSSs), and unified Physical Broadcast Channels (PBCHs). UEs 222, 224, 226, Channels 228, 230, and 232 can receive the unified synchronization signals, derive the carrier frequency and timing partition from the synchronization signals, and in response derive the timing, transmit an uplink pilot or reference signal. The uplink pilot signal Petition 870250102952, dated 11 / 11 / 2025, page 24 / 153 A 20 / 60 signal transmitted by a UE (e.g., UE 224) can be received simultaneously by two or more cells (e.g., base stations 210 and 214 / 216) within the 200 radio access network. Each cell can measure a pilot signal strength, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) can designate a server cell for UE 224. As UE 224 moves through the 200 radio access network, the network can continue to monitor the uplink pilot signal transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds that of the signal strength or quality measured by the server cell, the 200 network can perform handover to UE 224 from the service cell to the neighboring cell, with or without informing UE 224.

[0051] Although the synchronization signal transmitted by base stations 210, 212 and 214 / 216 may be unified, the synchronization signal may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or with the same timing. The use of zones in 5G networks or other next-generation communication networks enables uplink-based mobility infrastructure and enhances the efficiency of the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0052] In various implementations, the air interface in the 200 radio access network may use licensed spectrum, unlicensed spectrum, or spectrum Petition 870250102952, dated 11 / 11 / 2025, p. 25 / 153 21 / 60 shared. Licensed spectrum provides exclusive use of a portion of the spectrum, usually by virtue of a mobile network operator acquiring a license from a government regulatory body. Unlicensed spectrum allows shared use of a portion of the spectrum without the need for a government-granted license. While compliance with some technical rules is still generally required to access unlicensed spectrum, usually any operator or device can gain access. Shared spectrum may fall between licensed and unlicensed spectrum, where rules or technical limitations may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs.For example, the holder of a license for a portion of the licensed spectrum may provide Licensed Shared Access (LSA) to share that spectrum with other groups, for example, with suitable conditions determined by the licensee to gain access.

[0053] The air interface in the 200 radio access network can use one or more duplexing algorithms. Duplexing refers to a point-to-point communication link where the two endpoints can communicate with each other in both directions. Full-duplex means that the two endpoints can communicate simultaneously with each other. Half-duplex means that only one endpoint can send information to the other at a time. In a wireless link, a full-duplex channel generally depends on the physical isolation of a transmitter and receiver and on appropriate interference cancellation technologies. A Petition 870250102952, dated 11 / 11 / 2025, p. 26 / 153 22 / 60 full-duplex emulation is frequently implemented for wireless links, using Frequency Division Duplexing (FDD) or Time Division Duplexing (TDD). In FDD, transmissions in different directions operate on different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time-division multiplexing. That is, at some times the channel is dedicated to transmissions in one direction, while at other times the channel is dedicated to transmissions in the other direction, where the direction can change very quickly, for example, several times per partition.

[0054] In order for transmissions over the 200 radio access network 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, a message or sequence of information is divided into code blocks (CBs) and an encoder (e.g., a CODEC) in the transmitting device then mathematically adds redundancy to the information message. Exploiting this redundancy in the encoded information message can enhance message reliability by allowing the correction of any bit errors that may occur due to noise.

[0055] In the preliminary 5G NR specifications, user data is encoded using quasi-cyclic low-density parity checking (LDPC) with two different base graphs: one base graph is used for Petition 870250102952, dated 11 / 11 / 2025, page 27 / 153 23 / 60 large code blocks and / or high code rates, while the other base graph is used in a different way. The control information and the physical broadcast channel (PBCH) are encoded using Polar coding, based on nested sequences. For these channels, punching, shortening, and repetition are used for rate matching.

[0056] However, those skilled in the art will understand that aspects of the present disclosure can be implemented using any suitable channel code. Various implementations of 108 scheduling entities and 106 scheduled entities may include suitable hardware and capabilities (e.g., an encoder, a decoder, and / or a CODEC) to utilize one or more of these channel codes for wireless communication.

[0057] The air interface in the 200 radio access network may utilize one or more multiplexing and various multiple access algorithms to enable simultaneous communication of multiple devices. For example, the 5G NR specifications provide multiple access for UL transmissions from UEs 222 and 224 to base station 210 and for multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224, using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). Additionally, for UL transmissions, the 5G NR specifications provide support for Discrete Fourier Transform Spreading OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and access Petition 870250102952, dated 11 / 11 / 2025, page 28 / 153 24 / 60 multiple access is not limited to the schemes described above and can be provided using time-division multiple access (TDMA), code-division multiple access (CDMA), frequency-division multiple access (FDMA), sparse-code multiple access (SCMA), resource-spreading multiple access (RSMA), or other suitable multiple access schemes. Additionally, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 can be provided using 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.

[0058] Several aspects of the present disclosure will be described with reference to an OFDM waveform, schematically illustrated in FIG. 3. It should be understood by those skilled in the art that the various aspects of the present disclosure can be applied to a DFT-sOFDMA waveform substantially in the same manner as described in this document below. That is, although some examples of the present disclosure may focus on an OFDM link for clarity, it should be understood that the same principles can also be applied to DFT-s-OFDMA waveforms.

[0059] Within the present disclosure, a frame refers to a duration of 10 ms for wireless transmissions, with each frame consisting of 10 subframes of 1 ms each. On a given carrier, there may be one set of frames in the UL and another set of frames in the DL. With reference now to FIG. 3, an expanded view of a Petition 870250102952, dated 11 / 11 / 2025, p. 29 / 153 The illustrative DL subframe 302 is shown, presenting an OFDM feature grid 304. However, as those skilled in the art will readily appreciate, the PHY transmission structure for any particular application may vary from the example described in this document, depending on any number of factors. In this document, time is in the horizontal direction with OFDM symbol units; and frequency is in the vertical direction with subcarrier or tone units.

[0060] The 304 feature grid can be used to schematically represent the frequency and time resources for a given antenna port. That is, in a MIMO implementation with multiple available antenna ports, a corresponding multiple number of 304 feature grids may be available for communication. The 304 feature grid is divided into several 306 feature elements (REs). A RE, which is 1 symbol x 1 subcarrier, is the smallest discrete part of the frequency and time grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a specific implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical feature block (PRB) or more simply a 308 feature block (RB), which contains any suitable number of consecutive subcarriers in the frequency domain.In one example, an RB might include 12 subcarriers, a number independent of the numerology used. In some examples, depending on the numerology, an RB might include any suitable number of consecutive OFDM symbols in the time domain. Petition 870250102952, dated 11 / 11 / 2025, p. 30 / 153 26 / 60 Within the present disclosure, it is assumed that a single RB such as the RB 308 corresponds entirely to a single direction of communication (transmission or reception to a given device).

[0061] A UE typically uses only a subset of the 304 resource grid. An RB can be the smallest unit of resources that can be allocated to a UE. Thus, the more RBs are scheduled for a UE, and the larger the modulation scheme chosen for the air interface, the higher the data rate for the UE.

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

[0063] Each 1 ms 302 subframe may consist of one or more adjacent partitions. In the example shown in FIG. 3, a 302 subframe includes four 310 partitions, as an illustrative example. In some examples, a partition may be defined according to a specific number of OFDM symbols with a given cyclic prefix (CP) length. For example, a partition may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-partitions having a shorter duration (e.g., one or two OFDM symbols). These mini-partitions may in some cases be transmitted Petition 870250102952, dated 11 / 11 / 2025, page 31 / 153 27 / 60 occupying resources scheduled for ongoing partition transmissions to the same or different UEs.

[0064] An expanded view of one of the partitions 310 illustrates partition 310 including a control region 312 and a data region 314. In general, the control region 312 may carry the control channels (e.g., PDCCH), and the data region 314 may carry the data channels (e.g., PDSCH or PUSCH). Obviously, a partition may contain all DLs, all ULs, or at least a portion of DLs and at least a portion of ULs. The simple structure illustrated in FIG. 3 is merely illustrative in nature, and different partition structures may be used and may include one or more of each of the control regions and data regions.

[0065] Although not illustrated in FIG. 3, the various REs 306 within an RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 can also carry pilots or reference signals, including but not limited to a demodulation reference signal (DMRS), a control reference signal (CRS), or a sounding reference signal (SRS). These pilots or reference signals can provide a receiving device with channel estimation of the corresponding channel, which can enable coherent demodulation / detection of the control and / or data channels within the RB 308.

[0066] In a DL transmission, the transmission device (e.g., scheduling entity 108) can allocate one or more REs 306 (e.g., within a Petition 870250102952, dated 11 / 11 / 2025, p. 32 / 153 28 / 60 control region 312) to carry DL control information 114 including one or more DL control channels, such as a PBCH; a PSS; an SSS; a Physical Control Format Indicator Channel (PCFICH); a Hybrid Automatic Repeat Request (HARQ) Physical Indicator Channel (PHICH); and / or a Physical Downlink Control Channel (PDCCH), etc., for one or more scheduled entities 106. The PCFICH provides information to assist a receiving device in receiving and decoding the PDCCH. The PDCCH carries downlink control information (DCI), including but not limited to power control commands, scheduling information, a grant and / or an assignment of REs for DL ​​and UL transmissions. The PHICH carries HARQ feedback transmissions, such as acknowledgment (ACK) or negative acknowledgment (NACK).HARQ is a well-known technique among those skilled in the art, where the integrity of packet transmissions can be verified on the receiving side for accuracy, for example, using any suitable integrity verification mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK can be transmitted, while if not confirmed, a NACK can be transmitted. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement a combination of chasing, incremental redundancy, etc.

[0067] In a UL transmission, the transmission device (e.g., scheduled entity 106) may use one or more REs 306 to carry UL control information 118, including one or more control channels. Petition 870250102952, dated 11 / 11 / 2025, page 33 / 153 UL 29 / 60, as a physical uplink control channel (PUCCH), to scheduling entity 108. UL control information can include a variety of packet types and categories, including pilots, reference signals, and information configured to activate or assist in decoding uplink data transmissions. In some examples, control information 118 may include a scheduling request (SR), for example, a request for scheduling entity 108 to schedule uplink transmissions. In this document, in response to the SR transmitted on control channel 118, scheduling entity 108 may transmit downlink control information 114 which may schedule resources for uplink packet transmissions. UL control information may also include HARQ feedback, channel state feedback (CSF), or any other suitable UL control information.

[0068] In addition to control information, one or more REs 306 (for example, within data region 314) may be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as, for a DL transmission, a shared physical downlink channel (PDSCH); or for a UL transmission, a shared physical uplink channel (PUSCH). In some examples, one or more REs 306 within data region 314 may be configured to carry system information blocks (SIBs), carrying the information that may allow access to a given cell.

[0069] The channels or carriers described above and illustrated in FIGS. 1 and 3 are not necessarily all Petition 870250102952, dated 11 / 11 / 2025, page 34 / 153 30 / 60 the channels or carriers that can be used between a scheduling entity 108 and the scheduled entities 106, and those skilled in the art will recognize that other channels or carriers can be used in addition to those illustrated, such as other traffic, control and feedback channels.

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

[0071] According to one aspect of the disclosure, one or more partitions may be structured as independent partitions. For example, FIG. 4 illustrates two illustrative structures of independent partitions 400 and 450. Independent partitions 400 and / or 450 may be used, in some examples, in place of partition 310 described above and illustrated in FIG. 3.

[0072] In the illustrated example, a DL-centered partition of 400 could be a transmitter-scheduled partition. DL-centered nomenclature generally refers to a structure where more resources are allocated to transmissions in the DL direction (e.g., transmissions from scheduling entity 108 to scheduled entity 106). Similarly, a UL-centered partition of 450 could be a receiver-scheduled partition, where more resources are allocated to transmissions in the UL direction. Petition 870250102952, dated 11 / 11 / 2025, p. 35 / 153 31 / 60 (for example, transmissions from scheduled entity 106 to scheduling entity 108).

[0073] Each partition, such as the independent partitions 400 and 450, may include transmit (Tx) and receive (Rx) parts. For example, in the DL-centric partition 400, scheduling entity 202 first has an opportunity to transmit control information, for example, in a PDCCH, in a DL 402 control region, and then an opportunity to transmit DL user data or traffic, for example, in a PDSCH in a DL 404 data region. Following a guard period (GP) region 406 having a suitable duration 410, scheduling entity 108 has an opportunity to receive UL data and / or UL feedback including any UL scheduling requests, CSF, a HARQ ACK / NACK, etc., in a UL 408 burst from other entities using the carrier.In this document, a partition such as the DL 400-centered partition can be referred to as an independent partition when all data carried in data region 404 is scheduled in control region 402 of the same partition; and additionally, when all data carried in data region 404 is acknowledged (or at least has an opportunity to be acknowledged) in the UL 408 burst of the same partition. In this way, each independent partition can be considered an independent entity, not necessarily requiring another partition to complete a scheduling-transmission acknowledgment cycle for a given packet.

[0074] The GP 406 region can be included to accommodate variability in UL and DL timing. By Petition 870250102952, dated 11 / 11 / 2025, page 36 / 153 32 / 60 For example, latencies due to changes in radio frequency (RF) antenna direction (e.g., from DL to UL) and transmission path latencies can cause scheduled entity 204 to transmit early on UL to coincide with the timing of DL. Such early transmission can interfere with symbols received from scheduling entity 108. Consequently, GP region 406 can allow a certain amount of time after the DL data region 404 to avoid interference, where GP region 406 provides an appropriate amount of time for scheduling entity 108 to change its RF antenna direction, an appropriate amount of time for over-the-air (OTA) transmission, and an appropriate amount of time for ACK processing by the scheduled entity.

[0075] Similarly, the UL 450-centered partition can be configured as a standalone partition. The UL 450-centered partition is substantially similar to the DL 400-centered partition, including a guard period of 454, a data region of UL 456, and a burst region of UL 458.

[0076] The partition structure illustrated in partitions 400 and 450 is only one example of independent partitions. Other examples may include a common DL part at the beginning of each partition, and a common UL part at the end of each partition, with various differences in partition structure between these respective parts. Still other examples may be provided within the scope of the present disclosure. ILLUSTRATIVE TRANSMISSION OF UPLINK CONTROL INFORMATION

[0077] As discussed earlier, the Petition 870250102952, dated 11 / 11 / 2025, page 37 / 153 33 / 60 aspects disclosed in this document are directed towards new radio (NR) transmissions of uplink control information (UCI). In one particular aspect, techniques for transmitting large UCI payloads are disclosed. For example, when a UCI payload size exceeds a size limit, it is contemplated that transmitting such a payload may involve transmitting the UCI components via multiple packets (e.g., multiple code blocks or in different partitions). For example, a large UCI payload can be divided into multiple code blocks similar to PUSCH through code segmentation. Each code block can be encoded separately with Polar code.

[0078] It is also contemplated that transmitting large UCI payloads may involve reporting a larger number of component carriers (CCs) when transmitting a higher priority UCI component relative to transmitting a lower priority UCI component. For example, with respect to transmitting channel status information (CSI), a CSI reporting scheme is contemplated, which depends on the CSI type and / or payload size. Within such an implementation, CSI payload types and sizes are given different priorities, where a higher priority CSI may be associated with fewer restrictions. For example, a higher priority CSI may be triggered in a trigger for up to 10 CCs, compared to 5 CCs for a lower priority CSI.Therefore, it is contemplated that the CSI report may include a larger number of CCs (e.g., 10 CCs) for CSI types considered to be of higher priority (e.g., a classification indicator (RI) type, a beam information type, etc.) and reporting one. Petition 870250102952, dated 11 / 11 / 2025, p. 38 / 153 34 / 60 A smaller number of CCs (e.g., 5 CCs) for CSI types considered to have a lower priority (e.g., a Channel Quality Indicator (CQI) type, a Precoding Matrix Indicator (PMI) type, etc.). Similarly, when prioritizing according to CSI payload size, it is contemplated that the CSI report may include a larger number of CCs (e.g., 10 CCs) for smaller CSI payload sizes that are considered to have a higher priority (e.g., 50 bits of CSI per CC) and reporting a smaller number of CCs (e.g., 5 CCs) for larger CSI payload sizes considered to have a lower priority (e.g., 100 bits of CSI per CC).

[0079] Several aspects are also considered for transmitting particular UCI components together in the same partition. For example, aspects are revealed for separating some CSI components, which are generally assigned a lower priority, from the UCI components, which are generally assigned a higher priority (e.g., acknowledgment (ACK), scheduling request (SR), and / or the higher priority CSI components). The separation can be done with time-division multiplexing and / or by separate encoding of the different UCI components with different priorities. To this end, since co-encoding / transmitting CSI with ACK and / or SR produces the same performance, it is noted that co-encoding / transmitting CSI with ACK and / or SR may be appropriate when the CSI performance target is comparable to the ACK and / or SR performance targets, such as when the CSI is an RI or beam information system. However, when the performance targets are different and Petition 870250102952, dated 11 / 11 / 2025, p. 39 / 153 35 / 60 simultaneous transmission of CSI with an ACK and / or SR in the same partition is desired, separate encoding of such components is contemplated. In some cases, the separately encoded UCI components can be time-division multiplexed using different symbols for transmission. To this end, it is contemplated that such configurations may include determining whether the UCI components should be transmitted within a short uplink burst or a long burst from the same partition.

[0080] Referring below to FIG. 5, illustrative partition structures are provided for transmitting UCI components within the same partition, according to some aspects of the present disclosure. As illustrated in FIG. 5, a first illustrative partition structure 500 comprises a long uplink burst 510 and a short uplink burst 520, where the ACK resource elements 512 and the CSI resource elements 514 are both included in the long uplink burst 510. Different performances for the ACK channel and the CSI channel can be achieved by adjusting the number of resource elements assigned to each channel. Within such an implementation, if ACK 512 is considered a higher priority than CSI 514 (for example, where CSI 514 is of type CQI), more resource elements can be allocated to ACK 512 than to CSI 514.In some cases, more resource elements may be assigned to higher priority UCI components by allocating more symbols (for example, 7 out of 11 symbols allocated to ACK 512 and 4 out of 11 symbols allocated to CSI 514). Additionally, in some cases, the allocated resource elements may not be sufficient for transmission. Petition 870250102952, dated 11 / 11 / 2025, page 40 / 153 36 / 60 The entire UTI payload, i.e., the resulting code rate, may be higher than the maximum code rate configured by gNB. In this case, part or all of the UTI payload may be discarded starting from the component with the lowest priority. Alternatively, as shown in the illustrative partition structure 530, instead of transmitting both UCI components in the same long burst, a first UCI component (i.e., CSI 542) can be transmitted in a long uplink burst 540, while the second UCI component (i.e., ACK 552) can be transmitted in a short uplink burst 550. As illustrated in the illustrative partition structure 560, implementations are also contemplated in which both UCI components (i.e., CSI 582 and ACK 584) are transmitted in the same short uplink burst 580, instead of the long uplink burst 570.

[0081] In another scheme for transmitting UCI components in the same partition, a power control scheme is contemplated, where a first UCI component is assigned a higher priority than a second UCI component, so that the first UCI component is transmitted with more power than the second UCI component. In this document, it should be noted that a closed power control operation (e.g., based on ACK or SR as a reference) can be implemented, where the CSI power control can be determined using the same closed power control loop, but with a particular CSI power offset.

[0082] It should also be noted that the power control design above must take into account a transition period for when a power Petition 870250102952, dated 11 / 11 / 2025, page 41 / 153 37 / 60 transmission alternates between adjacent symbols. In FIG. 6, for example, illustrative power transitions are provided for transmitting an ACK within the same partition as a CSI, where the ACK is transmitted with more power than the CSI (e.g., where the ACK transmission power is 3 dB greater than the CSI transmission power). As illustrated, a first 600 configuration is provided, in which the 605 transition is entirely within CSI 620, instead of ACK 610. Alternatively, as illustrated in the 630 configuration, the 635 transition is entirely within ACK 640, instead of CSI 650. As illustrated in the 660 configuration, implementations are also contemplated in which a first part of the 665 transition is included in ACK 670, and a second part of the 665 transition is included in CSI 680.

[0083] Regarding each of the configurations 600, 630, and 660, illustrated in FIG. 6, it is noted that the respective 600, 630, and 660 transitions can occur when the ACK and CSI are time-division multiplexed in a long burst, or from a long burst to a short burst. It should also be noted that particular settings may be preferred depending on the respective priorities (i.e., performance targets) of the UCI components being transmitted. For example, since the performance target of an ACK is generally higher than the performance target of a CSI, it may be desirable to use the 600 setting to ensure that the last symbols of the ACK are transmitted at full power (i.e., so that the power transition occurs entirely within the lowest priority channel). However, if the ACK and CSI have comparable performance targets (by Petition 870250102952, dated 11 / 11 / 2025, p. 42 / 153 38 / 60 for example, when the CSI is an RI or beam information), it may be desirable to use the 600 configuration so that the transition is evenly split between the ACK and the CSI.

[0084] In another aspect of the disclosure, it should be appreciated that the power control scheme mentioned above is not limited to the UCI, but may also include other channels (e.g., the Physical Uplink Shared Channel (PUSCH) and the probe reference signal (SRS)). Consequently, in addition to the 600, 630, and 660 configurations illustrated in FIG. 6, several other configurations are contemplated. For example, when placing the power transition on a lower priority channel, such configurations may include placing the transition on the SRS (e.g., if the SRS is time-division multiplexed (TDMd) with a CSI, an ACK, or an SR) or placing the transition on the PUSCH (e.g., if the PUSCH is TDMd with an ACK or an SR). Additional configurations are also contemplated for evenly dividing the transition, including, for example, evenly dividing the transition between PUSCH and CSI (i.e., where PUSCH and CSI receive comparable priorities). ILLUSTRATIVE SCHEDULING ENTITY

[0085] FIG. 7 is a block diagram illustrating an example of a hardware implementation for a 700 scheduling entity employing a 714 processing system. For example, the 700 scheduling entity may be a user appliance (UE), as illustrated in any one or more of the figures disclosed in this document. In another example, the 700 scheduling entity may be a base station, as also illustrated in any one or more of the figures disclosed in this document. Petition 870250102952, dated 11 / 11 / 2025, page 43 / 153 39 / 60

[0086] The 700 scheduling entity can be implemented with a 714 processing system that includes one or more 704 processors. Examples of 704 processors include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, blocked logic, discrete hardware circuits, and other suitable hardware configured to perform the various features described throughout this disclosure. In several instances, the 700 scheduling entity can be configured to perform any one or more of the functions described in this document. That is, the 704 processor, as used in a 700 scheduling entity, can be used to implement any one or more of the processes and procedures described below and illustrated in FIG. 8.

[0087] In this example, the 714 processing system can be implemented with a bus architecture, usually represented by the 702 bus. The 702 bus can include any number of interconnecting buses and bridges, depending on the specific application of the 714 processing system and general design constraints. The 702 bus communicatively couples several circuits, including one or more processors (usually represented by the 704 processor), a 705 memory, and computer-readable media (usually represented by the 706 computer-readable media). The 702 bus can also connect various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in Petition 870250102952, dated 11 / 11 / 2025, page 44 / 153 40 / 60 technique and therefore will not be described further. A 708 bus interface provides an interface between the 702 bus and a 710 transceiver. The 710 transceiver provides an interface or means of communication to communicate with various other devices through a transmission medium. Depending on the nature of the device, a 712 user interface (e.g., numeric keypad, video, speaker, microphone, game controller) may also be provided.

[0088] In some aspects of the disclosure, the 704 processor may include a 740 receiving circuit system configured for various functions, including, for example, receiving the uplink control information (UCI) components transmitted by a scheduled entity (e.g., scheduled entity 900), where the UCI components are transmitted to the scheduling entity 700 based on a priority assigned respectively to each of the UCI components. In this document, it is contemplated that the priority is assigned by the scheduled entity (e.g., scheduled entity 900) according to at least one of a payload type or size respectively associated with each of the UCI components. As illustrated, the 704 processor may also include a 742 decoding circuit system configured for various functions.For example, the 742 decoding circuit system can be configured to decode symbols received from a scheduled entity (e.g., scheduled entity 900) to verify the UCI encoded in those symbols. It should also be appreciated that the combination of the 740 receiving circuit system and the decoding circuit system... Petition 870250102952, dated 11 / 11 / 2025, page 45 / 153 41 / 60 742 can be configured to implement one or more of the functions described in this document.

[0089] Again with reference to the remaining components of scheduling entity 700, it should be appreciated that processor 704 is responsible for managing bus 702 and general processing, including the execution of software stored on computer-readable media 706. The software, when executed by processor 704, causes the processing system 714 to perform the various functions described below for any particular device. Computer-readable media 706 and memory 705 can also be used to store data that is manipulated by processor 704 when executing software.

[0090] One or more 704 processors in the processing system may execute software. Software should be broadly defined to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software may reside on a 706 computer-readable medium. A 706 computer-readable medium may be a non-temporary computer-readable medium. A non-temporary computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic stripe), an optical disc (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a card Petition 870250102952, dated 11 / 11 / 2025, p. 46 / 153 42 / 60 intelligent, a flash memory device (e.g., a card, a pen drive, or a key drive), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable means for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium may also include, by way of example, a carrier wave, a transmission line, and any other suitable means for transmitting software and / or instructions that can be accessed and read by a computer. The computer-readable medium 706 may reside in the processing system 714, external to the processing system 714, or distributed across various entities, including the processing system 714. The computer-readable medium 706 may be incorporated into a computer program product.By way of example, a computer program product might include a computer-readable medium in packaging materials. Those skilled in the art will recognize the best way to implement the described functionality presented throughout this disclosure, depending on the specific application and the general design constraints imposed on the overall system.

[0091] In one or more instances, the computer-readable storage medium 706 may include the receiving software 750 configured for various functions, including, for example, receiving UCI components transmitted by a scheduled entity (e.g., scheduled entity 900), where the UCI components are transmitted to the scheduling entity 700 based on Petition 870250102952, dated 11 / 11 / 2025, page 47 / 153 43 / 60 a priority is assigned, respectively, to each of the UCI components. In this document, it is contemplated that the priority is assigned by the scheduled entity (e.g., scheduled entity 900) according to at least one of a payload type or size, respectively, associated with each of the UCI components. As illustrated, the computer-readable storage medium 706 may also include decoding software 752 configured for various functions. For example, decoding software 752 may be configured to decode symbols received from a scheduled entity (e.g., scheduled entity 900) to verify the UCI encoded in those symbols.

[0092] In a specific configuration, it is also contemplated that the scheduling entity 700 includes the means to receive the UCI components transmitted by a scheduled entity (for example, the scheduled entity 900), and the means to decode the symbols corresponding to the UCI components. In one aspect, the aforementioned means may be the processor(s) 704 configured to perform the functions mentioned by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any apparatus configured to perform the functions mentioned by the aforementioned means.

[0093] Obviously, in the above examples, the circuit system included in the 704 processor is merely provided as an example, and other means of performing the described functions may be included within various aspects of the present disclosure, including, but not limited to, instructions stored in the readable storage medium. Petition 870250102952, dated 11 / 11 / 2025, page 48 / 153 44 / 60 computer 706, or any other suitable device or means described in this document, and using, for example, the processes and / or algorithms described in relation to FIG. 8.

[0094] In FIG. 8, a flowchart is provided, which illustrates an illustrative scheduling entity process that facilitates some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in a specific implementation within the scope of the present disclosure, and some illustrated features may not be necessary for the implementation of all embodiments. In some examples, process 800 may be performed by scheduling entity 700 illustrated in FIG. 7. In some examples, process 800 may be performed by any apparatus or means suitable for performing the functions or algorithms described below.

[0095] Process 800 begins in block 802 with scheduling entity 700 receiving transmitted UCI components according to a priority assigned to each of the UCI components. Process 800 then ends in block 804, where scheduling entity 700 decodes the symbols corresponding to the UCI components. ILLUSTRATIVE SCHEDULED ENTITY

[0096] FIG. 9 is a conceptual diagram illustrating an example of hardware implementation for an illustrative scheduled entity 900 employing a processing system 914. According to the various aspects of the revelation, an element or any part of an element or any combination of elements can be implemented with Petition 870250102952, dated 11 / 11 / 2025, page 49 / 153 45 / 60 a processing system 914 that includes one or more processors 904. For example, the scheduled entity 900 may be a user equipment (UE) as illustrated in any one or more of the FIGS disclosed in this document.

[0097] The processing system 914 may be substantially the same as the processing system 714 illustrated in FIG. 7, including a bus interface 908, a bus 902, memory 905, a processor 904, and a computer-readable medium 906. Additionally, the scheduled entity 900 may include a user interface 912 and a transceiver 910 substantially similar to those described above in FIG. 7. That is, the processor 904, as used in a scheduled entity 900, may be used to implement any one or more of the processes described below and illustrated in the various figures.

[0098] In some aspects of the disclosure, the 904 processor may include an assignment circuit system 940 configured for various functions, including, for example, assigning a priority to each of several uplink control information (UCI) components. In this document, it is contemplated that such priority is assigned according to at least one of a type or size of payload, respectively, associated with each of several UCI components. As illustrated, the 904 processor may also include the transmission circuit system 942 configured for various functions. For example, the transmission circuit system 942 may be configured to transmit the various UCI components based on the priority assigned, respectively, to each of the various UCI components. It should also be appreciated Petition 870250102952, dated 11 / 11 / 2025, page 50 / 153 46 / 60 that the combination of the 940 assignment circuit system and the 942 transmission circuit system can be configured to implement one or more of the functions described in this document.

[0099] Similar to the 704 processor, the 904 processor is responsible for managing the 902 bus and general processing, including executing software stored on the computer-readable medium 906. When executed by the 904 processor, the software causes the 914 processing system to perform the various functions described below for any particular device. The computer-readable medium 906 and memory 905 can also be used to store data that is manipulated by the 904 processor when executing the software.

[00100] One or more processors 904 in the processing system may execute the software. Software should be interpreted broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or others. The software may reside on a computer-readable medium 906. Similar to the computer-readable medium 706, the computer-readable medium 906 may be a non-temporary computer-readable medium comprising substantially similar features. The computer-readable medium 906 may reside in the processing system 914, external to Petition 870250102952, dated 11 / 11 / 2025, page 51 / 153 47 / 60 processing system 914, or distributed across the various entities, including processing system 914. It should also be appreciated that, similarly to computer-readable media 706, computer-readable media 906 can be embodied in a computer program product comprising features that are substantially similar.

[00101] In one or more instances, the computer-readable storage medium 906 may include assignment software 950 configured for various functions, including, for example, assigning a priority to each of the various UCI components. In this document, it is again contemplated that this priority is assigned according to at least one of a payload type or size, respectively, associated with each of the various UCI components. As illustrated, the computer-readable storage medium 906 may also include transmission software 952 configured for various functions. For example, transmission software 952 may be configured to transmit the various UCI components based on the priority assigned, respectively, to each of the various UCI components. It should also be appreciated that the combination of assignment software 942 and transmission software 952 may be configured to implement one or more of the functions described in this document.

[00102] In a particular configuration, it is also contemplated that the scheduled entity 900 includes the means to assign a priority to each of the various UCI components, and the means to transmit the various UCI components based on the priority assigned, respectively, to each. Petition 870250102952, dated 11 / 11 / 2025, page 52 / 153 48 / 60 one of several UCI components. In one aspect, the aforementioned means may be the 904 processor(s) configured to perform the functions mentioned by the aforementioned means. In another aspect, the aforementioned means may be a circuit or any apparatus configured to perform the functions mentioned by the aforementioned means.

[00103] Obviously, in the above examples, the circuit system included in the 904 processor is merely provided as an example, and other means of performing the described functions may be included in various aspects of the present disclosure, including, but not limited to, instructions stored in the computer-readable storage medium 906, or any other suitable apparatus or means described herein, and using, for example, the processes and / or algorithms described in relation to FIG. 12.

[00104] Several other aspects for the scheduled entity 900 are also contemplated. For example, referring to FIG. 10 below, illustrative subcomponents of the assignment circuit system 940 and the assignment software 950 are provided. As illustrated, the assignment circuit system 940 may comprise the type circuit subsystem 1000 and the payload size circuit subsystem 1010; while the assignment software 950 may comprise the type instructions 1005 and the payload size instructions 1015.

[00105] In a particular implementation, it is contemplated that the 1000-type circuit subsystem and / or the 1005-type instructions be configured to prioritize UCI components according to the UCI type. For this Petition 870250102952, dated 11 / 11 / 2025, page 53 / 153 49 / 60 Finally, it should be appreciated that the various UCI components may comprise any of several UCI types, including, for example, an Acknowledgment (ACK) type, a Scheduling Request (SR) type, and / or a Channel Status Information (CSI) type. Within such an implementation, the 1000-type circuit subsystem and / or 1005-type instructions may be configured to assign a higher priority to a first UCI component relative to a second UCI component when the first UCI component is an ACK type or SR type, and the second UCI component is a CSI type.

[00106] Although it is contemplated that CSI types generally receive a lower priority than ACK and SR types, it should be noted that there are several CSI types, where the 1000 type circuit subsystem and / or 1005 type instructions can be configured to assign a different priority to each of the various CSI types. For example, the types included in the various UCI components may comprise several CSI types, including, for example, a Classification Indicator (RI) type, a beam information type, a Channel Quality Indicator (CQI) type, and / or a Precoding Matrix Indicator (PMI) type. Within such an implementation, the 1000-type circuit subsystem and / or the 1005-type instructions can be configured to assign a higher priority to a first UCI component over a second UCI component when the first UCI component is an RI type or beam information type, and the second UCI component is a CQI type or PMI type.

[00107] In a further aspect of the revelation, it is Petition 870250102952, dated 11 / 11 / 2025, page 54 / 153 50 / 60 contemplates that the 1010 payload size circuit subsystem and / or the 1015 payload size instructions be configured to prioritize UCI components according to UCI payload size. For example, the 1010 payload size circuit subsystem and / or the 1015 payload size instructions can be configured to assign a higher priority to a first UCI component over a second UCI component when the payload size of the first UCI component is smaller than the payload size of the second UCI component.

[00108] Several other aspects for the scheduled entity 900 are also contemplated. For example, referring to FIG. 11 below, illustrative subcomponents of the transmission circuit system 942 and the transmission software 952 are provided. As illustrated, the transmission circuit system 942 may comprise the reporting circuit subsystem 1100 and the partitioning circuit subsystem 1110; while the transmission software 952 may comprise the reporting instructions 1105 and the partitioning instructions 1115.

[00109] As stated earlier, when reporting CSI, payloads can be on the order of a dozen bits per component carrier (CC) for periodic CSI reports, and on the order of hundreds of bits per CC for aperiodic CSI reports. Other factors that can generate larger payloads include whether a multiple CC scheme is used (e.g., 32 bits per CC in LTE), as well as the particular encoding scheme that is used (e.g., when encoding the UTI with polar code, the bits Petition 870250102952, dated 11 / 11 / 2025, p. 55 / 153 51 / 60 outputs can be up to 1024 bits). Consequently, it is contemplated that the 1100 reporting circuit subsystem and / or the 1105 reporting instructions can be configured to report a higher number of component carriers when transmitting a higher priority UCI component relative to transmitting a lower priority UCI component.

[00110] In another aspect of the disclosure, it is contemplated that the 1110 partitioning circuit subsystem and / or the 1115 partitioning instructions can be configured to determine a partitioning configuration in which the various UCI components are transmitted. For example, with respect to transmitting large UCI payloads, it is contemplated that the 1110 circuit subsystem and / or the 1115 partitioning instructions can be configured to transmit the various UCI components via multiple packets when the size of the various UCI components exceeds a size limit. In a particular implementation, it is contemplated that the 1110 partitioning circuit subsystem and / or the 1115 partitioning instructions can be configured to transmit the various UCI components via the various code blocks or in different partitions.For example, a large UCI payload can be divided into multiple code blocks similar to PUSCH through code segmentation, where each code block can be encoded separately with Polar code.

[00111] It is also contemplated that the partition circuit subsystem 1110 and / or partition instructions 1115 may be configured to transmit a first UCI component and a second UCI component in the same partition, where the first UCI component and the second Petition 870250102952, dated 11 / 11 / 2025, page 56 / 153 52 / 60 UCI components receive different priority levels. Within such an implementation, several schemes for transmitting the UCI components are contemplated.

[00112] In an illustrative scheme for transmitting UCI components in the same partition, a power control scheme is contemplated where the partition circuit subsystem 1110 and / or partition instructions 1115 are configured to assign the first UCI component a higher priority than the second UCI component, and where the partition circuit subsystem 1110 and / or partition instructions 1115 are configured to transmit the first UCI component with more power than the second UCI component. In this document, as stated previously, such a design must take into account a transition period for when transmission power changes between adjacent symbols. For example, the partition circuit subsystem 1110 and / or partition instructions 1115 can be configured to set up a higher-to-lower-power transition to occur during the transmission of the second UCI component.Alternatively, the partitioning circuit subsystem 1110 and / or partitioning instructions 1115 can be configured to set up a first part of a transition from higher power to lower power to occur during a transmission of the first UCI component, and to set up a second part of the transmission to occur during the transmission of the second UCI component.

[00113] In another illustrative diagram for the transmission of UCI components in the same partition, the Petition 870250102952, dated 11 / 11 / 2025, page 57 / 153 53 / 60 Partition Circuit Subsystem 1110 and / or Partition Instructions 1115 can be configured to determine whether UCI components will be transmitted within a short burst or a long uplink burst. For example, Partition Circuit Subsystem 1110 and / or Partition Instructions 1115 can be configured to transmit a first UCI component and a second UCI component in the same long burst. Within such an implementation, if the first UCI component has a higher priority than the second UCI component, Partition Circuit Subsystem 1110 and / or Partition Instructions 1115 can be configured to allocate more resource elements to a transmission of the first UCI component than to a transmission of the second UCI component.Alternatively, instead of transmitting the UCI components in a single long burst, the partitioning circuit subsystem 1110 and / or partitioning instructions 1115 can be configured to transmit the first UCI component and the second UCI component in a single short burst. Implementations are also contemplated in which the partitioning circuit subsystem 1110 and / or partitioning instructions 1115 can be configured to transmit the first UCI component in a long burst and the second UCI component in a short burst. Other contemplated implementations include having the partitioning circuit subsystem 1110 and / or partitioning instructions 1115 configured to encode the first UCI component and the second UCI component separately.

[00114] As mentioned, in some cases, the allocated resource elements may not be sufficient to transmit an entire UCI payload. Petition 870250102952, dated 11 / 11 / 2025, page 58 / 153 54 / 60 (i.e., the resulting code rate may be higher than the maximum code rate configured by gNB). In such cases, it is contemplated that part or all of the UCI payload may be dropped starting from the component with the lowest priority. For example, it is contemplated that the partitioning circuit subsystem 1110 and / or partitioning instructions 1115 may be configured to determine whether the resource elements allocated to transmit one of the various UCI components are sufficient to transmit all of the various UCI components. If the resource elements allocated to transmit the various UCI components are deemed insufficient, the partitioning circuit subsystem 1110 and / or partitioning instructions 1115 may be configured to drop at least a portion of the various UCI components based on the priority respectively assigned to each of the various UCI components.

[00115] Referring hereto to FIG. 12, a flowchart is provided, illustrating an illustrative scheduled entity process for performing some aspects of the disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be necessary for the implementation of all embodiments. In some examples, process 1200 may be performed by scheduled entity 900 illustrated in FIG. 9. In some examples, process 1200 may be performed by any apparatus or means suitable for performing the functions or algorithms described below.

[00116] Process 1200 begins in block 1202 with Petition 870250102952, dated 11 / 11 / 2025, page 59 / 153 55 / 60 the scheduled entity 900 assigning a priority to each of the various UCI components, where the priority is assigned according to at least one of a payload type or size respectively associated with each of the various UCI components. The process 1200 then concludes in block 1204, where the scheduled entity 900 transmits the various UCI components based on the priority assigned respectively to each of the various UCI components.

[00117] It should be appreciated that several other aspects of process 1200 are also contemplated. For example, when assigning a priority in block 1202 according to type, it should be appreciated that the various UCI components may comprise any of several types, including, for example, an ACK type, an SR type, and / or a CSI type. Within such an implementation, the priority assignment performed in block 1202 may comprise assigning a higher priority to a first UCI component relative to a second UCI component when the first UCI component is of the ACK or SR type, and the second UCI component is of the CSI type.

[00118] Although it is contemplated that CSI types will generally have a lower priority than ACK and SR types, it should be noted that there are several CSI types, where each of the various CSI types may have a different priority. For example, the types included in the various UCI components may comprise several CSI types, including, for example, an RI type, a beam information type, a CQI type, and / or a PMI type. Within such an implementation, the priority assignment performed in block 1202 may involve assigning a higher priority. Petition 870250102952, dated 11 / 11 / 2025, page 60 / 153 56 / 60 high for a first UCI component relative to a second UCI component when the first UCI component is an RI type or beam information type, and the second UCI component is a CQI type or PMI type.

[00119] In a further aspect of the disclosure, it is contemplated that the priority assignment performed in block 1202 may be based on the UCI payload size. For example, the assignment performed in block 1202 may comprise assigning a higher priority to a first UCI component relative to a second UCI component when the payload size of the first UCI component is smaller than the payload size of the second UCI component.

[00120] Several aspects of transmission performed in block 1204 are also contemplated. For example, with regard to transmitting large UCI payloads, it is contemplated that transmission performed in block 1204 may involve transmitting the various UCI components across multiple packets when the size of the various UCI components exceeds a size limit. It is also contemplated that transmission performed in block 1204 may involve reporting a higher number of component carriers when transmitting a higher priority UCI component compared to transmitting a lower priority UCI component.

[00121] Several additional aspects related to the transmission performed in block 1204 are also considered. For example, in a specific implementation, the transmission comprises transmitting a first UCI component and a second UCI component in the same partition, where for the first UCI component and for the second component Petition 870250102952, dated 11 / 11 / 2025, page 61 / 153 57 / 60 UCIs are assigned different priority levels. Within such an implementation, several schemes for transmitting UCI components in block 1204 are contemplated.

[00122] In an illustrative scheme for transmitting UCI components in the same partition, a power control scheme is contemplated where the first UCI component receives a higher priority than the second UCI component, and where the transmission involves transmitting the first UCI component with more power than the second UCI component. In this document, as stated previously, such a design must take into account a transition period for when transmission power changes between adjacent symbols. For example, transmission performed in block 1204 may involve configuring a transition from higher power to lower power to occur during transmission of the second UCI component.Alternatively, the transmission may involve setting up a first part of a transition from a higher power to a lower power during a transmission of the first UCI component, and setting up a second part of the transition to occur during a transmission of the second UCI component.

[00123] In another illustrative scheme for transmitting UCI components in the same partition, a determination is made as to whether UCI components will be transmitted within a short burst or a long uplink burst. For example, the transmission performed in block 1204 may involve transmitting a first UCI component and a second UCI component in the same long burst. Within such an implementation, if the first UCI component is Petition 870250102952, dated 11 / 11 / 2025, page 62 / 153 58 / 60 assigned a higher priority than the second UCI component, the transmission may involve allocating more resource elements to a transmission of the first UCI component than to a transmission of the second UCI component. Alternatively, instead of transmitting UCI components in the same long burst, the transmission executed in block 1204 may involve transmitting the first UCI component and the second UCI component in the same short burst. Implementations are also contemplated in which the transmission involves transmitting the first UCI component in a long burst and the second component UCI in a short burst. Additional contemplated implementations include having the transmission run on block 1204 including separate encoding of the first UCI component and the second UCI component.

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

[00125] By way of example, several aspects can be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE), the system of Evolved Packet Systems (EPS), the Universal Mobile Telecommunication System (UMTS), and / or the Global System for Cellular (GSM). Several aspects can also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolving Data Optimized. Petition 870250102952, dated 11 / 11 / 2025, page 63 / 153 59 / 60 (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The telecommunications standard, network architecture, and / or actual communication standard employed will depend on the specific application and the general design constraints imposed on the system.

[00126] Within the present disclosure, the word illustrative is used to mean serving as an example, instance, or illustration. Any implementation or aspect described in this document as illustrative should not necessarily be interpreted as preferred or advantageous over other aspects of the disclosure. Similarly, the term aspects does not require that all aspects of the disclosure include the feature, advantage, or mode of operation discussed. The term coupled is used in this document to refer to the 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 to be coupled with each other—even if they do not directly touch. For example, a first object can be coupled with a second object, even if the first object is never in direct physical contact with the second object.The terms circuit and circuit system are widely used and are intended to include hardware implementations of electrical devices as conductors that, when connected and configured, enable the performance of the functions described in this disclosure, without limitation as to the type of circuits. Petition 870250102952, dated 11 / 11 / 2025, page 64 / 153 60 / 60 electronics, as well as the software implementations of information and instructions that, when executed by a processor, enable the execution of the functions described in this disclosure.

[00127] One or more of the components, steps, features, and / or functions illustrated in FIGS. 1 through 12 may be rearranged and / or combined into a single component, step, feature, or function, or incorporated into multiple components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without deviating from the new features disclosed in this document. The apparatus, devices, and / or components illustrated in FIGS. 1 through 12 may be configured to perform one or more of the methods, features, or steps described in this document. The new algorithms described in this document may also be efficiently implemented in software and / or incorporated into hardware.

[00128] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of illustrative processes. Based on project preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order and are not limited to the specific order or hierarchy presented, unless specifically cited therein. Petition 870250102952, dated 11 / 11 / 2025, p. 65 / 153

Claims

1 / 4 CLAIMS 1. A wireless communication method (1200) operable on a scheduled entity, the method comprising: assigning (1202) a priority to each of a plurality of uplink control information components, UCIs, wherein the priority is assigned according to the payload size respectively associated with each of the plurality of UCI components, the method characterized in that it further comprises: transmitting (1204) the plurality of UCI components based on the priority assigned respectively to each of the plurality of UCI components, including transmitting a first UCI component and a second UCI component in the same partition comprising a long burst and a short burst, the first UCI component being assigned a higher priority than the second UCI component, and wherein more resource elements are assigned to transmit the first UCI component than to transmit the second UCI component.

2. A method according to claim 1, characterized in that the plurality of UCI components comprises at least one of an acknowledgment type, ACK, a scheduling request type, SR, or a channel status information type, CSI.

3. Method according to claim 2, characterized in that: the first UCI component is an ACK type or SR type; and the second UCI component is a CSI type.

4. Method according to claim 1, Petition 870250102952, dated 11 / 11 / 2025, page 66 / 153 2 / 4 characterized in that the plurality of UCI components comprises a plurality of channel state information types, CSI, and in that the plurality of CSI types comprises at least one of a classification indicator type, RI, a beam information type, a channel quality indicator type, CQI, or a pre-coding matrix indicator type, PMI.

5. Method according to claim 4, characterized in that: the first UCI component is a type of RI or beam information type; and the second UCI component is a type of CQI or PMI type.

6. Method according to claim 1, characterized in that a payload size of the first UCI component is smaller than a payload size of the second UCI component.

7. A method according to claim 1, characterized in that the transmission comprises transmitting the plurality of UCI components through multiple packets when the size of the plurality of UCI components exceeds a limit size.

8. Method, according to claim 1, characterized in that the transmission comprises reporting a greater number of component carriers when transmitting a higher priority UCI component compared to transmitting a lower priority UCI component.

9. Method, according to claim 1, characterized in that the transmission comprises transmitting the first UCI component with more power than the second UCI component.

10. Method according to claim 9, characterized in that the transmission further comprises configuring a transition from higher power to lower power to occur during a transmission of the second UCI component.

11. Method according to claim 9, characterized in that the transmission further comprises: configuring a first part of a transition from higher power to lower power to occur during a transmission of the first UCI component; and configuring a second part of the transition to occur during a transmission of the second UCI component.

12. Method according to claim 1, characterized in that the transmission comprises one of the following: transmitting the first UCI component and the second UCI component in the long burst; transmitting the first UCI component and the second UCI component in the short burst; transmitting the first UCI component in the long burst and the second UCI component in the short burst.

13. Memory (906) characterized in that it comprises instructions which, when executed, cause a processor to perform the method as defined in any one of claims 1 to 12.

14. Wireless communication device (900), comprising: Petition 870250102952, dated 11 / 11 / 2025, page.68 / 153 4 / 4 means (940) for assigning a priority to each of a plurality of uplink control information components, UCI, wherein the priority is assigned according to the payload size respectively associated with each of the plurality of UCI components, the device characterized in that it further comprises: means (942) for transmitting the plurality of UCI components based on the priority assigned respectively to each of the plurality of UCI components, including means for transmitting a first UCI component and a second UCI component in the same partition comprising a long burst and a short burst, the first UCI component being assigned a higher priority than the second UCI component, and wherein more resource elements are assigned to transmit the first UCI component than to transmit the second UCI component. Petition 870250102952, dated 11 / 11 / 2025, p. 69 / 153.

Images