Multiplexing uplink control information (UCI) on uplink data transmissions with multiple transport blocks
By multiplexing UCI and multiple TBs in PUSCH transmission and utilizing TB priority indexing and code rate adjustment, the inefficiency of control information and transport block multiplexing is solved, thereby improving the data rate and spectrum efficiency of the wireless communication system.
Patent Information
- Application Number
- CN202380027335.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-21
- Filing Date
- 2023-02-23
- Publication Date
- 2024-11-08
AI Technical Summary
In the existing technology, the multiplexing of control information and transmission blocks has failed to effectively improve the data rate and network capacity of wireless communication systems, resulting in low spectrum efficiency.
By employing multiple transport blocks (TBs) and uplink control information (UCI) multiplexing methods in the Physical Uplink Shared Channel (PUSCH) transmission, and utilizing TB priority indexing and code rate adjustment, the resource allocation and mapping of UCI are optimized to improve data transmission efficiency.
It achieves higher data rates, improved network capacity and spectrum efficiency, and enhances the overall performance of wireless communication systems.
Smart Images

Figure CN118923073A_ABST
Abstract
Description
[0001] This application claims priority to U.S. patent application No. 17 / 700,156, filed on March 21, 2022, the entire contents of which are incorporated herein by reference. Technical Field
[0002] The techniques discussed below relate generally to wireless communication systems, and more particularly, to multiplexing uplink control information (UCI) on an uplink data transmission having multiple transport blocks. Background Art
[0003] A transport block (TB) is a packet or block of information carried on a transport channel between the MAC and physical layers of a communication network. As commonly used in modern wireless communication networks, one or more transport blocks may be carried in a scheduled transmission. At the physical layer, user data corresponding to a transport block is typically separated from control information carried on a physical control channel. However, in some cases, control information may be piggybacked or multiplexed onto a transport block. Summary of the invention
[0004] A simplified summary of one or more aspects of the present disclosure is provided below to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to provide some concepts of one or more aspects of the present disclosure in a simplified form as a preface to a more detailed description given later. Although some examples may be discussed as including certain aspects or features, all discussed examples may include any of the discussed features. And unless explicitly described, no aspect or feature is necessary to achieve the technical effects or solutions discussed herein.
[0005] In one example, a method for wireless communication is disclosed. The method includes receiving an uplink (UL) grant, the uplink (UL) grant including a grant for a physical uplink shared channel (PUSCH) transmission. The PUSCH transmission includes a plurality of transport blocks (TBs), each respective TB in the plurality of TBs being associated with a respective TB priority index. The method also includes transmitting a PUSCH including the plurality of TBs.
[0006] In another example, another method of wireless communication is disclosed. The method includes sending an uplink (UL) grant, the uplink (UL) grant including a grant for a physical uplink shared channel (PUSCH) transmission. The PUSCH transmission includes a plurality of transport blocks (TBs), each respective TB in the plurality of TBs being associated with a respective TB priority index. The method also includes receiving a PUSCH including the plurality of TBs.
[0007] In another example, an apparatus for wireless communication is disclosed. The apparatus includes a processor, a memory, and a transceiver coupled to the processor. The processor is coupled to the memory and is configured to receive an uplink (UL) grant via the transceiver, the uplink (UL) grant including a grant for a physical uplink shared channel (PUSCH) transmission. The PUSCH transmission includes a plurality of transport blocks (TBs), each corresponding TB in the plurality of TBs being associated with a corresponding TB priority index. The processor is further configured to transmit the PUSCH including the plurality of TBs via the transceiver.
[0008] In another example, another apparatus for wireless communication is disclosed. The apparatus includes a processor, a memory, and a transceiver coupled to the processor. The processor is coupled to the memory and is configured to send an uplink (UL) grant via the transceiver, the uplink (UL) grant including a grant for a physical uplink shared channel (PUSCH) transmission. The PUSCH transmission includes a plurality of transport blocks (TBs), each corresponding TB in the plurality of TBs being associated with a corresponding TB priority index. The processor is further configured to receive a PUSCH including the plurality of TBs via the transceiver.
[0009] After reading the following specific embodiments, these and other aspects of the technology discussed herein will become more fully appreciated. After reading the description of the following specific examples in conjunction with the accompanying drawings, other aspects and features will become apparent to those of ordinary skill in the art. Although the following description may discuss various advantages and features with respect to certain examples, specific implementations, and accompanying drawings, all examples may include one or more of the advantageous features discussed herein. In other words, although this description may discuss one or more examples as having certain advantageous features, one or more such features may also be used according to other various examples discussed herein. In a similar manner, although this description may discuss certain examples as devices, systems, or methods, it should be understood that such examples of the teachings of the present disclosure may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 is a schematic diagram of a wireless communication system according to some aspects of the present disclosure.
[0011] Figure 2 is a schematic diagram of an example of a radio access network according to some aspects of the present disclosure.
[0012] Figure 3 is a schematic diagram of an example of a disaggregated base station architecture according to some aspects of the present disclosure.
[0013] Figure 4is a block diagram illustrating a radio protocol architecture in a wireless communication system according to some aspects of the present disclosure.
[0014] Figure 5 is a schematic diagram of the organization of wireless resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects of the present disclosure.
[0015] Figure 6 is a block diagram conceptually illustrating an example of a hardware implementation of a radio access network node according to some aspects of the present disclosure.
[0016] Figure 7 is a block diagram conceptually illustrating an example of a hardware implementation for a user equipment (UE) according to some aspects of the present disclosure.
[0017] Figure 8 is a schematic diagram of uplink time slots according to some aspects of the present disclosure.
[0018] Fig. 9 is a flow chart illustrating an example of a process for physical uplink shared channel (PUSCH) transmission with multiple transport blocks (TBs) according to some aspects of the present disclosure.
[0019] Fig.10 is a flow chart illustrating an example of a process for PUSCH transmission with multiple uplink control information (UCI) multiplexed with multiple TBs in accordance with some aspects of the present disclosure.
[0020] Fig.11 is a flow chart illustrating an example of a process for determining a coding rate for each of a plurality of UCIs transmitted with a plurality of TBs according to some aspects of the present disclosure.
[0021] Fig.12 is a flow chart illustrating another example of a process for determining a coding rate for each of a plurality of UCIs transmitted with a plurality of TBs according to some aspects of the present disclosure.
[0022] Fig.13 is a flow chart illustrating an example of a process for determining an upper bound on the amount of resources used to carry control information over multiple TBs in a PUSCH transmission in accordance with some aspects of the present disclosure.
[0023] Fig.14 is a flow chart illustrating another example of a process for determining an upper bound on the amount of resources used to carry control information over multiple TBs in a PUSCH transmission in accordance with some aspects of the present disclosure.
[0024] Fig.15 is a schematic diagram of multiplexing multiple UCIs with multiple TBs according to some aspects of the present disclosure.
[0025] Fig.16 is a flow chart illustrating an example of a process for channel state information (CSI) reporting omission in multi-TB PUSCH transmissions according to some aspects of the present disclosure.
[0026] Fig.17 is a flow chart illustrating an example of a process for physical uplink shared channel (PUSCH) reception with multiple transport blocks (TBs) according to some aspects of the present disclosure. DETAILED DESCRIPTION
[0027] In a wireless communication network, an uplink shared channel transmission may carry multiple transport blocks (TBs). And in addition, such uplink shared channel transmissions may carry multiple uplink control information (UCI). In various aspects, the present disclosure provides methods and devices for piggybacking or multiplexing UCI on multi-TB uplink shared channel transmissions. By utilizing the various aspects described herein, a wireless communication network can achieve higher data rates, improved network capacity, and / or improved spectral efficiency by multiplexing UCI onto multi-TB uplink shared channel transmissions.
[0028] The following disclosure presents various concepts that can be implemented across various telecommunication systems, network architectures, and communication standards. Figure 1 , by way of illustrative example and not limitation, the schematic diagram shows various aspects of the present disclosure with reference to a wireless communication system 100. The wireless communication system 100 includes several interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.
[0029] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G or 5G NR. In some examples, the RAN 104 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to this hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.
[0030] As illustrated, the RAN 104 includes a plurality of base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a "base station" as a transceiver base station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an evolved Node B (eNB), a gNode B (gNB), a 5G NB, a transmit receive point (TRP), or some other suitable terminology.
[0031] The radio access network (RAN) 104 supports wireless communications for multiple mobile devices. Those skilled in the art may refer to mobile devices as UEs as in the 3GPP specifications, but UEs may also be referred to as mobile stations (MSs), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, or some other suitable terms. A UE may be a device that provides access to network services. A UE may take many forms and may include a range of devices.
[0032] Within this document, a "mobile" device (also referred to as a UE) does not necessarily need to have the ability to move, and can be stationary. The term mobile device or mobile device refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components of a size, shape, and arrangement that facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide range of embedded systems, for example, corresponding to the "Internet of Things" (IoT). A mobile device may additionally be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, wearable cameras, virtual reality devices, smart watches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc.). The mobile device may additionally be a digital home or smart home device, such as home audio, video and / or multimedia devices, appliances, vending machines, smart lighting, home security systems, smart meters, and the like. The mobile device may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls power (e.g., smart grid), lighting, water, and the like; industrial automation and enterprise devices; logistics controllers; and agricultural equipment; and the like. Further, the mobile device may provide connected medicine or telemedicine support, such as health care at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or access over other types of information, such as priority access for transmission of critical service data and / or related QoS for transmission of critical service data. The mobile device may additionally include two or more decomposed devices that communicate with each other, including, for example, a wearable device paired with a smart phone, a tactile sensor, a limb movement sensor, an eye movement sensor, and the like. In various examples, such decomposed devices may communicate directly with each other via any suitable communication channel or interface, or may communicate indirectly with each other via a network (e.g., a local area network (LAN)).
[0033] Wireless communication between RAN 104 and UE 106 may be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term "downlink" may refer to downlink transmissions at a scheduling entity (described further below; e.g., network node 108). Another way to describe this approach 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) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term "uplink" may refer to point-to-point transmissions initiated at a scheduled entity (described further below; e.g., UE 106).
[0034] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a network node 108) allocates resources for communication between some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE 106 (which may be a scheduled entity) may utilize resources allocated by the scheduling entity 108.
[0035] The base station is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE or a network node can act as a scheduling entity, scheduling resources for one or more scheduled entities (eg, one or more UEs).
[0036] like Figure 1 As shown, the network node 108 may broadcast downlink traffic 112 to one or more UEs 106. In a broad sense, a network node 108 is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and (in some examples) uplink traffic 116 from one or more UEs 106 to the network node 108. On the other hand, a UE 106 is a node or device that receives downlink control information 114 (including, but not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network, such as the network node 108.
[0037] Generally speaking, the network nodes 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the network nodes 108 and the core network 102. Furthermore, in some examples, the backhaul network may provide interconnections between the respective network nodes 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, or the like.
[0038] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured according to a 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.
[0039] By way of example and not limitation, Figure 2 A schematic diagram of a RAN 200 is provided. In some examples, the RAN 200 may be similar to the ones described above and in Figure 1 The geographic area covered by the RAN 200 may be divided into cellular areas (cells), and user equipment (UE) may be uniquely identified based on an identity broadcast from an access point, base station, or network node. Figure 2 Macro cells 202, 204, and 206 and a small cell 208 are illustrated.
[0040] Figure 2 Two of the three network nodes 210, 212, and 214 in cells 202, 204, and 206 are shown. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells, since network nodes 210, 212, and 214 support cells having larger sizes. In addition, network node 218 is shown in small cell 208 (e.g., micro cell, pico cell, femto cell, home base station, home Node B, home eNode B, etc.), which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell, since network node 218 supports cells having relatively smaller sizes. Cell size settings may be made based on system design and component constraints.
[0041] RAN 200 may include any number of radio network nodes and cells. In addition, the RAN may include relay nodes to extend the size or coverage area of a given cell. Network nodes 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, network nodes 210, 212, 214, and / or 218 may be similar to those described above and Figure 1 is the same as the base station / scheduling entity 108 illustrated in .
[0042] Figure 2 Also included is a quadcopter or drone 220 configured to function as a network node. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move depending on the location of a mobile network node such as a quadcopter 220.
[0043] Within the RAN 200, each network node 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with network node 210. UEs 226 and 228 may communicate with network node 212; UEs 230 and 232 may communicate with network node 214; UE 234 may communicate with network node 218; and UE 236 may communicate with mobile network node 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the mobile network nodes described above and in Figure 1 The UE / scheduled entity 106 illustrated in FIG.
[0044] In some examples, a mobile network node (eg, quadcopter 220 ) may be configured to function as a UE. For example, quadcopter 220 may operate within cell 202 by communicating with network node 210 .
[0045] In another aspect of RAN 200, sidelink signals may be used between UEs without having to rely on scheduling or control information from a network node (e.g., a scheduling entity). For example, two or more UEs (e.g., UEs 226 and 228) may communicate with each other using peer-to-peer (P2P) or sidelink signals 227 without relaying the communication through a network node. In another example, UE 238 is illustrated as communicating with UEs 240 and 242. Here, UE 238 may be used as a scheduling entity or a primary sidelink device, and UE 240 or 242 may be used as a scheduled entity or a non-primary (e.g., secondary) sidelink device. In yet another example, a UE may be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P) or vehicle-to-vehicle (V2V) network and / or a mesh network. In the mesh network example, in addition to communicating with the scheduling entity 238, UEs 240 and 242 may optionally communicate directly with each other. Therefore, in a wireless communication system with scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate using the scheduled resources.
[0046] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS 108 (such as a NodeB (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also called an independent BS or a monolithic BS) or a decomposed base station.
[0047] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0048] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0049] Figure 3A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 106 via one or more radio frequency (RF) access links. In some implementations, a UE 106 may be served simultaneously by multiple RUs 340.
[0050] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.
[0051] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 310. CU310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.
[0052] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split, such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.
[0053] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 106. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).
[0054] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 311 via the O1 interface. In addition, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .
[0055] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.
[0056] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).
[0057] In some aspects of the present disclosure, RAN nodes and / or UEs may be configured with multiple antennas for beamforming and / or multiple-input multiple-output (MIMO) technology. The use of such multiple-antenna technology enables wireless communication systems to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity.
[0058] Beamforming generally refers to directional signal transmission or reception. For beamforming transmission, the transmitting device can pre-code or control the amplitude and phase of each antenna in the antenna array to create a desired (e.g., directional) pattern of constructive and destructive interference in the wavefront. In a MIMO system, a transmitting device (e.g., a RAN node 108) includes multiple transmit antennas (e.g., N transmit antennas), and a receiving device (e.g., a UE 106) includes multiple receive antennas (e.g., M receive antennas). Therefore, there are N×M signal paths from the transmit antenna to the receive antenna. Each of the transmitting device and the receiving device can be implemented, for example, in the scheduling entity 108, the scheduled entity 106, or any other suitable wireless communication device.
[0059] In a MIMO system, spatial multiplexing can be used to simultaneously transmit multiple different data streams (also referred to as layers) on the same time-frequency resources. In some examples, a transmitting device may transmit multiple data streams to a single receiver. In this way, a MIMO system utilizes the capacity gain and / or increased data rate associated with using multiple antennas in a rich scattering environment in which channel changes can be tracked. Here, the receiving device can track these channel changes and provide corresponding feedback to the transmitting device. In an example case, a rank 2 (i.e., including 2 data streams) spatial multiplexing transmission on a 2x2 MIMO antenna configuration will send two data streams via two transmitting antennas. The signal from each transmitting antenna arrives at each receiving antenna along different signal paths. The receiving device 106 can then reconstruct these data streams using the signals received from each receiving antenna.
[0060] In some examples, the transmitter can transmit multiple data streams to multiple receivers. This is generally referred to as multi-user MIMO (MU-MIMO). In this way, the MU-MIMO system takes advantage of multipath signal propagation to increase overall network capacity by improving throughput and spectral efficiency and reducing the required transmission energy. This is achieved by the transmitting device 108 spatially precoding each data stream (in some examples, based on known channel state information) (i.e., multiplying these data streams by different weights and phase shifts) and then using the same allocated time-frequency resources to send each spatially precoded stream to the receiving device through multiple transmit antennas. The receiver (e.g., receiving device 106) may send feedback including a quantized version of the channel so that the transmitting device 108 can schedule the receiver according to good channel spacing. The spatially precoded data stream arrives at a receiver with different spatial signatures, which enables the receiver to separate these streams from each other (in some examples, combined with known channel state information) and recover the data stream destined for the receiver. In the other direction, multiple transmitters can each send a spatially precoded data stream to a single receiver, which enables the receiver to identify the source of each spatially precoded data stream.
[0061] The number of data streams or layers in a MIMO or MU-MIMO (commonly referred to as MIMO) system corresponds to the rank of transmission. In general, the rank of a MIMO system is limited by the number of transmit or receive antennas (whichever is lower). In addition, the channel conditions at the receiving device 106 and other considerations (such as the available resources at the transmitting device 108) may also affect the transmission rank. For example, a RAN node (e.g., a transmitting device 108) in the RAN may assign a rank (and therefore, the number of data streams) for DL transmission to a specific UE (e.g., a receiving device 106) based on a rank indicator (RI) sent by the UE to the RAN node. The UE may determine the RI based on the antenna configuration (e.g., the number of transmit antennas and receive antennas) and the signal to interference and noise ratio (SINR) measured on each receive antenna. For example, the RI may indicate the number of layers that the UE can support under the current channel conditions. The RAN node may use the RI together with resource information (e.g., available resources and the amount of data to be scheduled for the UE) to assign a DL transmission rank to the UE.
[0062] The transmitting device 108 determines the precoding of the transmitted one or more data streams based on, for example, known channel state information of the channel on which the transmitting device 108 transmits the data streams. For example, the transmitting device 108 may transmit one or more suitable reference signals (e.g., channel state information reference signals or CSI-RS) that the receiving device 106 may measure. The receiving device 106 may then report the measured channel quality information (CQI) back to the transmitting device 108. This CQI typically reports the current communication channel quality and, in some examples, reports the requested transport block size (TBS) for future transmissions to the receiver. In some examples, the receiving device 106 may further report a precoding matrix indicator (PMI) to the transmitting device 108. The PMI typically reports the preferred precoding matrix of the receiving device for use by the transmitting device 108 and may be indexed into a predefined codebook. The transmitting device 108 may then utilize this CQI / PMI to determine a suitable precoding matrix for transmission to the receiver 306.
[0063] In order to transmit on the RAN 104 to obtain a low block error rate (BLER) while still achieving very high data rates, the transmitter may use channel coding. That is, wireless communications may typically utilize suitable error-correcting block codes. In a typical block code, the transmitter splits an information message or sequence into code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message may improve the reliability of the message, thereby enabling correction of bit errors that may occur due to noise.
[0064] In the 5G NR specification (Release 15), data is coded in different ways. User data (e.g., data, data traffic, traffic, etc.) can be coded using quasi-cyclic low-density parity check (LDPC) with two different basemaps. One basemap is used for large code blocks and / or high code rates, while the other basemap is used for other cases. Control information and physical broadcast channel (PBCH) can be coded using polar coding (e.g., based on nested sequences). For control information and PBCH, rate matching is performed using puncturing, shortening, and repetition.
[0065] Those skilled in the art will appreciate that aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of the scheduling entity 108 and the scheduled entity 106 may include suitable hardware and capabilities (e.g., encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communication.
[0066] In some examples, rate matching may be used to modify the size of the encoded transmission by, for example, puncturing a portion of the systematic bits.Channel coding techniques, code rates, and rate matching may be referred to as coding schemes.
[0067] Figure 4 402 and 452 according to some aspects of the present disclosure. In wireless telecommunications systems, the communication protocol architecture can take on many forms depending on the application. For example, in a 3GPP NR system, the signaling protocol stack is divided into non-access stratum (NAS, 458) and access stratum (AS, 402-406 and 452-457) layers and protocols. NAS protocol 458 provides an upper layer for UE 106 to communicate with core network 102 (refer to Figure 1 ). AS protocols 402-406 and 452-457 provide lower layers for signaling between the RAN 104 (e.g., gNB or other network node 108) and the UE 106.
[0068] Go to Figure 4 , the radio protocol architecture is illustrated with a user plane protocol stack 402 and a control plane protocol stack 452, which show their corresponding layers or sublayers. The radio bearers between the network node 108 and the UE 106 can be classified into data radio bearers (DRBs) for carrying user plane data corresponding to the user plane protocol 402; and signaling radio bearers (SRBs) for carrying control plane data corresponding to the control plane protocol 452.
[0069] In the AS, both the user plane 402 and the control plane 452 protocols include a physical layer (PHY) 402 / 452, a medium access control layer (MAC) 403 / 453, a radio link control layer (RLC) 404 / 454, and a packet data convergence protocol layer (PDCP) 405 / 455. PHY 402 / 452 is the lowest layer and implements various physical layer signal processing functions. The MAC layer 403 / 453 provides multiplexing between logical channels and transport channels and is responsible for various functions. For example, the MAC layer 403 / 453 is responsible for reporting scheduling information, priority processing and priority determination, and error correction through hybrid automatic repeat request (HARQ) operations. The RLC layer 404 / 454 provides functions such as sequence numbering, segmentation and reassembly of upper layer data packets, and duplicate packet detection. The PDCP layer 405 / 455 provides functions including header compression of upper layer data packets to reduce radio transmission overhead, security by encrypting data packets, and integrity protection and verification.
[0070] In the user plane protocol stack 402, the service data adaptation protocol (SDAP) layer 406 provides services and functions for maintaining the desired quality of service (QoS). And in the control plane protocol stack 452, the radio resource control (RRC) layer 457 includes multiple functional entities for routing higher layer messages, handling broadcast and paging functions, establishing and configuring radio bearers, NAS message transmission between NAS and UE, etc. RRC signaling can provide a mechanism for configuring UE communications (such as setting a priority index for a given transmission).
[0071] The NAS protocol layer 458 provides various control functions between the UE 106 and the core network 102. These functions include, for example, registration management functions, connection management functions, and user plane connection activation and deactivation.
[0072] Figure 5 Various aspects of the present disclosure are schematically illustrated with reference to OFDM waveforms. It will be appreciated by those of ordinary skill in the art that various aspects of the present disclosure may be applied to DFT-s-OFDMA waveforms in substantially the same manner as described below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles may also be applied to DFT-s-OFDMA waveforms.
[0073] In some examples, a frame may refer to a predetermined time duration (e.g., 10 ms) used for wireless transmissions. And further, each frame may include a set of subframes (e.g., 10 subframes of 1 ms each). A given carrier may include one set of frames in the UL and another set of frames in the DL. Figure 5 An expanded view of an exemplary DL subframe 502 is illustrated, showing an OFDM resource grid 504. However, as will be readily apparent to one skilled in the art, the PHY transmission structure for any application may differ from the examples described herein, depending on any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and frequency is in units of subcarriers or tones in the vertical direction.
[0074] The resource grid 504 may schematically represent the time-frequency resources for a given antenna port. That is, in a MIMO implementation with multiple available antenna ports, a corresponding number of resource grids 504 may be available for communication. The resource grid 504 is divided into a plurality of resource elements (REs) 506. An RE (which is 1 subcarrier x 1 symbol) is the smallest discrete portion of the time-frequency grid and may contain a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular 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 resource block (PRB), or more simply a resource block (RB) 508, which may include any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may span 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain.
[0075] A given UE typically utilizes only a subset of the resource grid 504. An RB may be the smallest resource unit that a scheduler may allocate to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE.
[0076] In this illustration, RB 508 occupies less than the entire bandwidth of subframe 502, with some subcarriers illustrated above and below RB 508. In a given implementation, subframe 502 may have a bandwidth corresponding to any number of one or more RBs 508. Additionally, RB 508 is shown as occupying less than the entire duration of subframe 502, although this is only one possible example.
[0077] Each 1 ms subframe 502 may include one or more adjacent time slots. Figure 5 In the embodiment of the present invention, a subframe 502 includes four time slots 510 as an illustrative example. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Other examples may include mini-slots with shorter durations (e.g., one or two OFDM symbols). In some cases, a network node may occupy resources scheduled for ongoing time slot transmissions for the same or different UEs to transmit these mini-slots.
[0078] The expanded view of one of the time slots 510 illustrates that the time slot 510 includes a control region 512 and a data region 514. Generally speaking, the control region 512 may carry a control channel (e.g., PDCCH), and the data region 514 may carry a data channel (e.g., PDSCH or PUSCH). Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 5 The structures illustrated in are merely exemplary in nature, and different slot structures may be utilized, and these slot structures may include one or more of each of the control region and the data region.
[0079] Although not in Figure 5 508, but each RE 506 within an RB 508 may carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 506 within an RB 508 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of a control channel and / or a data channel within the RB 508.
[0080] In a DL transmission, a transmitting device (e.g., a network node 108) may allocate one or more REs 506 (e.g., within a control region 512) to carry one or more DL control channels. These DL control channels include DL control information (DCI) 114, which typically carries information originating from higher layers (such as a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc.) to one or more UEs 106. In addition, a network node may allocate one or more DL REs to carry DL physical signals that typically do not carry information originating from higher layers. These DL physical signals may include a primary synchronization signal (PSS); a secondary synchronization signal (SSS); a demodulation reference signal (DM-RS); a phase tracking reference signal (PT-RS); a channel state information reference signal (CSI-RS); etc.
[0081] The network node may send synchronization signals PSS and SSS (collectively referred to as SS) in an SS block comprising 4 consecutive OFDM symbols, and in some examples, PBCH. In the frequency domain, the SS block may extend over 240 consecutive subcarriers. Of course, the present disclosure is not limited to this particular SS block configuration. Within the scope of the present disclosure, other non-limiting examples may utilize more or less than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit the PBCH; and / or may use non-continuous symbols for the SS block.
[0082] The PDCCH may carry downlink control information (DCI) for one or more UEs in the cell. This may include, but is not limited to, power control commands for DL and UL transmissions, scheduling information, grants, and / or assignments to REs.
[0083] In UL transmission, a transmitting device (e.g., UE 106) may utilize one or more REs 506 to carry one or more UL control channels, such as a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc. These UL control channels include UL control information (UCI) 118, which typically carries information originating from higher layers. In addition, UL REs may carry UL physical signals that typically do not carry information originating from higher layers, such as a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), a sounding reference signal (SRS), etc. In some examples, the control information 118 may include a scheduling request (SR), i.e., a request for the network node 108 to schedule an uplink transmission. Here, in response to the SR sent on the UL control channel 118 (e.g., PUCCH), the network node 108 may send downlink control information (DCI) 114, which may schedule resources for uplink packet transmission.
[0084] UL control information (UCI) may also include hybrid automatic repeat request (HARQ) feedback, such as an acknowledgement (ACK) or negative acknowledgement (NACK), channel state information (CSI), or any other suitable UL control information. HARQ is a technology known to those of ordinary skill in the art, wherein a receiving device may check the integrity of a packet transmission for accuracy, for example, using any appropriate integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC). If the receiving device confirms the integrity of the transmission, it may send an ACK, and if the integrity of the transmission is not confirmed, it may send a NACK. In response to the NACK, the transmitting device may transmit a HARQ retransmission, which may implement tracking combining, incremental redundancy, etc.
[0085] As used in the present disclosure, UCI may include a set of UL control information types including, for example, one or more HARQ-ACKs, one or more CSI reports, one or more scheduling requests (SRs), etc. That is, a single UCI may refer to a set of multiple UCI types in a given transmission.
[0086] In some examples, a given UCI may be associated with a priority index indicating the priority of the corresponding UCI. For example, a high priority (HP) UCI may be associated with a priority index of 1, and a low priority (LP) UCI may be associated with a priority index of 0, although this is merely an example and any suitable number of priorities may exist. In another example, each UCI may be associated with a corresponding priority index. A given UCI may be associated with its priority index in any of several different ways. For example, a downlink grant for a UE to send HARQ-ACK feedback may explicitly notify the UE whether the HARQ-ACK feedback will be HP or LP. In other examples, the UE may be an RRC configured to adopt a given priority index for one or more UCIs of a given group. In another example, a priority index may be associated with the UCI based on the type of information carried on a given UCI. Other techniques known to those of ordinary skill in the art for associating a priority index with a UCI may be used.
[0087] In addition to control information, one or more REs 506 (e.g., within the data region 514) may also be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as, for DL transmissions, on a physical downlink shared channel (PDSCH) or, for UL transmissions, on a physical uplink shared channel (PUSCH).
[0088] In some examples, the physical layer may typically multiplex these physical channels described above and map them to transport channels for processing at a medium access control (MAC) layer entity. The transport channels carry blocks of information called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits in a TB, may be a controlled parameter.
[0089] On the uplink, much like UCI, a given uplink data transmission via PUSCH may be associated with a priority index. In some examples, the same priority scheme used for UCI may be used for PUSCH transmissions, with a high priority (HP) PUSCH transmission associated with priority index 1 and a low priority (LP) PUSCH transmission associated with priority index 0. Here, priorities for PUSCH transmissions may be provided on a per-grant basis, with each grant for a PUSCH transmission having an associated priority for that PUSCH transmission. A particular priority may be associated with a particular PUSCH transmission in a variety of ways, including, but not limited to, explicitly indicated in its corresponding grant; configured via RRC signaling; based on the type of data carried on the PUSCH transmission, etc.
[0090] Figure 6 614 is a block diagram illustrating an example of a hardware implementation of a RAN node 600 employing a processing system 614. For example, the RAN node 600 may be a Figure 1 , Figure 2 and / or Figure 3 In another example, the RAN node 600 may be a user equipment (UE) as illustrated in any one or more of Figure 1 and Figure 2 In yet another example, the RAN node 600 may be a component of a decomposed RAN, such as Figure 3 The CU, DU and / or RU illustrated.
[0091] The RAN node 600 may include a processing system 614 having one or more processors 604. Examples of the processor 604 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic, a discrete hardware circuit, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, the RAN node 600 may be configured to perform any one or more of the functions described herein. For example, the processor 604 as utilized in the RAN node 600 may be configured (e.g., in coordination with the memory 605) to implement the functions described below and Fig.17 Any one or more of the processes and procedures illustrated in .
[0092] The processing system 614 may be implemented with a bus architecture, which is generally represented by bus 602. Bus 602 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 614 and the overall design constraints. Bus 602 communicatively couples various circuits including one or more processors (generally represented by processor 604), memory 605, and computer-readable media (generally represented by computer-readable media 606). Bus 602 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 608 provides an interface between bus 602 and transceiver 610. Transceiver 610 provides a communication interface or component for communicating with various other devices through a transmission medium. Depending on the nature of the device, a user interface 612 (e.g., keyboard, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 612 is optional, and some examples such as base stations may omit it.
[0093] In some aspects of the disclosure, processor 604 may include scheduling circuitry 640 configured (e.g., in coordination with memory 605) for various functions, including, for example, generating and sending scheduling information (such as scheduling grants, DCI, etc.) for transmission via transceiver 610. Processor 604 may also include communication control circuitry 642 configured (e.g., in coordination with memory 605) for various functions, including, for example, receiving and processing UL transmissions (including, but not limited to, PUSCH and PUCCH transmissions).
[0094] The processor 604 is responsible for managing the bus 602 and general processing, which includes executing software stored on a computer-readable medium 606. The software, when executed by the processor 604, causes the processing system 614 to perform the various functions described below for any particular device. The processor 604 may also use the computer-readable medium 606 and the memory 605 for storing data that the processor 604 manipulates when executing the software.
[0095] One or more processors 604 in the processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language or other. Software may reside on a computer-readable medium 606. Computer-readable medium 606 may be a non-transient computer-readable medium. By way of example, non-transient computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer readable medium 606 may reside in the processing system 614, be external to the processing system 614, or be distributed across multiple entities including the processing system 614. The computer readable medium 606 may be embodied in a computer program product. By way of example, a computer program product may include a computer readable medium in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system.
[0096] In one or more examples, the computer-readable storage medium 606 may store computer-executable code including scheduling instructions 652 that configure the RAN node 600 for various functions, including, for example, generating and sending scheduling information (such as scheduling grants, DCI, etc.) for transmission via the transceiver 610. The computer-readable storage medium 606 may also store computer-executable code including communication control instructions 654 that configure the RAN node 600 for various functions, including, for example, receiving and processing UL transmissions (including but not limited to PUSCH and PUCCH transmissions).
[0097] In one configuration, the RAN node 600 includes means for sending an UL grant and means for receiving a PUSCH transmission. In one aspect, the aforementioned means may be in Figure 6 The processor 604 shown in , the processor is configured to perform the functions described by the aforementioned components. On the other hand, the aforementioned components can be a circuit or any device configured to perform the functions described by the aforementioned components.
[0098] Of course, in the above examples, the circuit system included in the processor 604 is provided only as an example, and other components for 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 606 or in Figure 1 , Figure 2 , Figure 3 and / or Figure 6 Any of the descriptions and use of the foregoing Fig.17 Any other suitable means or components of the described processes and / or algorithms.
[0099] Figure 7 700 is a conceptual diagram illustrating an example of a hardware implementation of an exemplary scheduled entity or UE 700 employing a processing system 714. According to various aspects of the present disclosure, the processing system 714 may include an element, or any portion of an element, or any combination of elements, having one or more processors 704. For example, the UE 700 may be as in Figure 1 , Figure 2 and / or Figure 3 A user equipment (UE) or scheduled entity illustrated in any one or more of .
[0100] The processing system 714 may be used with Figure 6 The illustrated processing system 614 is substantially the same, including a bus interface 708, a bus 702, a memory 705, a processor 704, and a computer-readable medium 706. In addition, the UE 700 may include substantially the same as described above in Figure 6That is, the processor 704 as used in the UE 700 may be configured (eg, in coordination with the memory 705) to implement the following description and in Fig. 9 , Fig.10 , Fig.11 , Fig.12 , Fig.13 , Fig.14 and / or Fig.16 Any one or more of the illustrated processes.
[0101] In some aspects of the present disclosure, processor 704 may include communication control circuitry 740 configured (e.g., in coordination with memory 705) for various functions, including, for example, receiving and processing scheduling information (e.g., scheduling DCI, UL grants, etc.) from a scheduling entity, generating and sending a PUSCH transmission, channel decoding (e.g., encoding) a data packet for transmission, etc. Processor 704 may also include UCI to TB mapping circuitry 742 configured (e.g., in coordination with memory 705) for various functions, including, for example, mapping a set of UCIs to a TB based on, for example, a UCI priority index, a TB priority index, a TB index, an MCS of the TB, an amount of UCI resources available on the TB, a number of layers of the TB, etc. The processor 704 may also include a UCI multiplexing / piggybacking circuit system 744, which is configured (e.g., coordinated with the memory 705) for various functions, including, for example, sending (e.g., coordinated with the transceiver 710) UCI multiplexed with PUSCH transmission, rate matching TBs around UCI, puncturing TBs, etc.
[0102] And further, the computer-readable storage medium 706 may store computer-executable code including communication control instructions 752 that configure the UE 700 for various functions including, for example, receiving and processing scheduling information (e.g., scheduling DCI, UL grants, etc.) from a scheduling entity, generating and sending a PUSCH transmission, channel decoding (e.g., encoding) data packets for transmission, etc. The computer-readable storage medium 706 may also store computer-executable code including UCI to TB mapping instructions 754 that configure the UE 700 for various functions including, for example, mapping a set of UCIs to TBs based on, for example, a UCI priority index, a TB priority index, a TB index, an MCS of the TB, an amount of UCI resources available on the TB, a number of layers of the TB, etc. The computer-readable storage medium 706 may also store computer-executable code including UCI multiplexing / piggybacking instructions 756 that configure the UE 700 for various functions, including, for example, sending (e.g., coordinating with the transceiver 710) UCI multiplexed with PUSCH transmissions, rate matching TBs around the UCI, puncturing TBs, etc.
[0103] In one configuration, the UE 700 includes means for receiving information, means for sending information, means for multiplexing UCI onto TBs, means for encoding, means for decoding, means for determining an amount of resources for carrying control information on TBs, means for mapping UCI onto TBs, and means for abandoning sending information. In one aspect, the aforementioned means may be in Figure 7 The processor 704 shown in the figure is configured to perform the functions described by the aforementioned components. On the other hand, the aforementioned components can be a circuit or any device configured to perform the functions described by the aforementioned components.
[0104] Of course, in the above examples, the circuit system included in the processor 704 is provided only as an example, and other components for 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 706 or in Figure 1 , Figure 2 and / or Figure 3 Any of the descriptions and use of the foregoing Fig. 9 , Fig.10 , Fig.11 , Fig.12 , Fig.13 , Fig.14 and / or Fig.16 Any other suitable means or components of the described processes and / or algorithms.
[0105] Figure 8Another example of a time slot 850 according to some aspects of the present disclosure is illustrated. The time slot may correspond to the time slot described above and Figure 5 514 is illustrated in FIG. As illustrated, time slot 850 includes a DL control region 852, a guard period (GP) 854, and a UL region 856. That is, the illustrated example shows a time slot having a portion of resources designated for UL transmission by a UE. However, the illustrated time slot format is only one example, and any suitable time slot structure or format including one or more UL regions may be adopted within the scope of the present disclosure.
[0106] Figure 8 The center portion of the UL region 856 shows an expanded view of the UL region 856, which illustrates two different examples according to various aspects. In the first example, the UL region 856 may include a UL control portion 802 and a UL data portion 804. In this example, the UL region 856 may carry a PUCCH in the UL control portion 802 and a PUSCH in the UL data portion 804. Here, the PUCCH may carry one or more UCIs, and the PUSCH may carry one or more TBs. However, in some examples, one or more UCIs may be piggybacked or multiplexed onto the PUSCH. For example, the UL control and data region 806 may include a PUSCH carrying one or more TBs multiplexed with one or more UCIs, without a separate PUCCH. For example, when the scheduled UE transmission of UCI overlaps with the scheduled transmission of PUSCH in the time domain, piggybacking or multiplexing of UCI onto the PUSCH may be performed. In this case, the UE may discard the PUCCH transmission 802 and multiplex the UCI onto the PUSCH 806. That is, UCI may be sent on PUSCH 806 together with user data or traffic. In some cases, UCI may be piggybacked or multiplexed on PUSCH by puncturing PUSCH. In other cases, UCI may be piggybacked on PUSCH by rate matching PUSCH around UCI.
[0107] In the context of the present disclosure, multiplexing (or equivalently, piggybacking) UCI on PUSCH refers to carrying UCI on PUSCH without a corresponding same-slot PUCCH. That is, unlike sending a slot with UCI on PUCCH and TB on PUSCH, when UCI is multiplexed with PUSCH in the present disclosure, UCI may be multiplexed by, for example, puncturing the TB on PUSCH or rate matching the TB on PUSCH so that both UCI and TB are carried on PUSCH.
[0108] When UCI is multiplexed onto PUSCH, the UE may have limited space available for UCI in PUSCH. Therefore, the UE may determine the amount of resources available for UCI on PUSCH. That is, although PUSCH may contain a given set of resources, some of these resources may be allocated for data transmission and may not be available for carrying UCI. To determine the PUSCH resources for UCI, the UE may employ parameters α and β. As discussed below, the UE may determine that the amount of resources available for UCI is the minimum between the upper bound (based on the α factor) and the encoded UCI size (based on the β offset).
[0109] For example, to determine the size of the encoded UCI, the UE may determine the code rate to be used for channel decoding or encoding the UCI. According to some examples, when UCI is multiplexed onto a TB, a parameter that may be referred to as a "β offset" or β factor may be used to scale the spectral efficiency (i.e., code rate) of the UCI relative to the known spectral efficiency (i.e., code rate) of the user data on the TB. That is, when UCI is multiplexed with data on a TB, the β offset scales the code rate of the UCI relative to the known code rate of the user data on the TB. For example, relative to the reliability of the data on the PUSCH, scaling down to a lower code rate may provide higher reliability for the UCI. In another example, when the PUSCH has a higher priority than the UCI, scaling up to a higher code rate may reduce the UCI overhead. The larger the β offset, the lower the UCI code rate. That is, a larger β offset means that the UCI occupies more resources in the PUSCH.
[0110] In addition, a parameter, which may be referred to as an "α factor", may define an upper bound on the amount of PUSCH resources available for UCI. For example, if the total amount of resources on a TB is equal to N, the maximum amount of resources that can be used for UCI on the TB may be equal to α multiplied by N.
[0111] The UE may determine the actual resources used for UCI on a given TB based on both the β factor and the α factor. For example, the UCI resources may be determined as the minimum resources between the resources based on the β offset and the upper bound based on the α factor.
[0112] In some aspects of the present disclosure, the PUSCH may carry multiple TBs. For example, when the PUSCH contains more than 4 layers, the 3GPP specification for 5GNR may support multiple TBs in the PUSCH transmission. In a multi-TB PUSCH transmission, different TBs may have different modulation and coding schemes (MCS), different redundancy versions (RV), different numbers of layers, and / or other characteristics that are different from each other. In some cases, as a rule, the UE may assign the same priority index to all TBs in a given PUSCH. In these cases, the network may use conventional signaling to indicate the priority of the PUSCH to the UE, as discussed above. In other cases, the UE may assign different priority indexes to different TBs on a given PUSCH. For example, the multiplexed UCI and PUSCH 806 may carry two TBs, one of which is a high priority TB and the other is a low priority TB. In these cases, the RAN node may provide the UE with an UL scheduling DCI (e.g., a scheduling grant) that provides multiple priority index fields corresponding to multiple TBs. For example, the UL scheduling DCI may include a set of two priority index indicator fields for indicating the priority indexes assigned by the UE to a set of two TBs in a given multi-TB PUSCH transmission.
[0113] In another aspect of the present disclosure, the PUSCH may carry multiple UCIs. That is, multiple UCIs may be multiplexed or piggybacked on the PUSCH 806 along with a group of one or more TBs as described above. Figure 8 , as an illustrative example, UL control and data 806 is shown in an expanded view, including two UCIs 810 and 814 and two TBs 812 and 816. The corresponding UCIs and TBs are labeled as UCI1 810 with priority index (PI) A, UCI2 814 with PI B, TB1 with PI C, and TB2 with PID 0. Any of PI A, B, C, and D may have any suitable value, such as PI 1 indicating a high priority and PI 0 indicating a low priority.
[0114] Fig. 9 9 is a flow chart illustrating an exemplary process 900 for PUSCH transmission with multiple TBs according to some aspects of the present disclosure. As described below, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Figure 7 The UE 700 illustrated in FIG. 7 may be configured to perform process 900. In some examples, process 900 may be performed by any suitable device or component for performing the functions or algorithms described below.
[0115] At block 902, UE 700 receives (e.g., using transceiver 710) an UL grant or UL scheduling DCI that includes a grant for a PUSCH transmission with multiple TBs. Here, each respective TB in the multiple TBs is associated with a respective TB priority index. For example, communication control circuit system 740 may process scheduling information from scheduling entity 600, including scheduling DCI. When each respective TB is associated with a respective TB priority index, a single PUSCH transmission may carry multiple TBs with different priorities.
[0116] At block 904, the UE 700 transmits a scheduled PUSCH including a plurality of TBs. For example, the transceiver 710 may be used to transmit a scheduled transmission including TBs with a configured MCS, number of layers, and the like.
[0117] In the case where a PUSCH transmission includes multiple TBs and multiple UCIs are to be multiplexed onto the same PUSCH transmission, this raises the question of which UCI is mapped to which TB. That is, in some examples, all UCIs may be mapped to the first TB. However, the amount of resources available for UCI on a given TB may be limited, as described above with respect to parameters α and β. Therefore, the set of control information may be segmented into multiple UCIs for multiplexing on multiple TBs.
[0118] In particular, when UCIs having different priority indexes are mapped to TBs having the same priority index as each other, it may be unclear how to map the UCIs to the TBs. Various aspects of the present disclosure address these and other related questions and problems.
[0119] Fig.10 1 is a flow chart illustrating an example process 1000 for PUSCH transmission with multiple UCIs multiplexed with multiple TBs according to some aspects of the present disclosure. As described below, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Figure 7 The UE 700 illustrated in FIG. 1000 may be configured to perform process 1000. In some examples, process 1000 may be performed by any suitable device or component for performing the functions or algorithms described below.
[0120] At block 1002, UE 700 receives (e.g., using transceiver 710) an UL grant or UL scheduling DCI that includes a grant for a PUSCH transmission with multiple TBs. Here, each respective TB in the multiple TBs is associated with a respective TB priority index. For example, communication control circuit system 740 may process scheduling information from scheduling entity 600, including scheduling DCI. When each respective TB is associated with a respective TB priority index, a single PUSCH transmission may carry multiple TBs with the same or different priorities.
[0121] At block 1004, the UE 700 may map the first set of one or more UCIs to a first TB of the plurality of TBs, and at block 1006, the UE 700 may map the second set of one or more UCIs to a second TB of the plurality of TBs. For example, the UE 700 may employ the UCI-to-TB mapping circuit 742 to determine which UCI(s) to map to which TB based on one or more factors such as a UCI priority index, a TB priority index, a TB index, a TB MCS, a number of layers, etc., as further described below.
[0122] In some examples, the RAN may provide a control message (e.g., RRC message, MAC-CE, DCI, etc.) to indicate to the UE 700 which UCI is multiplexed to which TB. For example, the RAN may indicate that the UCI may be multiplexed only to a specific TB among multiple TBs. In this case, the UCI-to-TB mapping circuit 742 will simply follow the instruction and map any UCI to the indicated TB. In another example, the RAN may indicate that the UCI may be multiplexed on two (or more) TBs. In this case, the UCI-to-TB mapping circuit 742 may determine which TB to map the UCI to based on one or more factors as described below.
[0123] At optional block 1008, UE 700 may forgo sending at least one CSI report. For example, UE 700 may forgo sending a CSI report having a lower CSI report priority index than the CSI report priority index associated with the first TB1 and the second TB2. Fig.16 The box is further described with reference to the description of the omission of CSI reporting.
[0124] At block 1010, UE 700 may transmit (e.g., using transceiver 710) a PUSCH transmission including a plurality of UCIs multiplexed with a plurality of TBs. Here, each UCI in the plurality of UCIs is associated with a corresponding UCI priority index. That is, each TB is associated with a corresponding TB priority index, and each multiplexed UCI is associated with a corresponding UCI priority index.
[0125] When the UE is to multiplex multiple UCIs onto a PUSCH with multiple TBs, the UE may apply the same β offset to each UCI, or apply different β offsets to different UCIs mapped to different TBs. For example, if different TBs are sent on different layers or on channels with different channel characteristics, the channel quality may be different for different TBs. Therefore, the decoding rates for those corresponding TBs may be different. For the UCIs mapped to those TBs, there may be different reliability requirements based on, for example, UCI priorities. Therefore, in order to improve or optimize the probability that each UCI is correctly decoded by the receiver, the UE may apply different β offsets to different UCIs mapped to different TBs.
[0126] In some examples, the RAN node may provide the UE with an UL grant or scheduling DCI including multiple β offset fields. For example, for a PUSCH scheduled for two TBs, the UL grant may provide two separate β offset fields, one β offset field corresponding to each TB. In this way, when the UCI is mapped to the corresponding TB, the UE may apply the corresponding β offset to scale the code rate of the corresponding UCI.
[0127] In another example, the UL grant or scheduling DCI may provide a single β offset field, even though the UL grant schedules multiple TBs. In these examples, the UE may apply the same β offset value to each TB or may apply different β offset values to different TBs. For example, the RAN node may provide RRC signaling to the UE that configures the UE with multiple (e.g., 2) β offset tables or values corresponding to the TBs. Here, the UE may apply different β offsets to different TBs based on the corresponding β offset tables or values for the different TBs. In another example, the UE may select the β offset to be used for each TB based on some suitable factor, such as a maximum β offset value based on a received β offset parameter and multiple configured β offset tables or values. By selecting the maximum β offset, the UE may increase the likelihood that the two UCIs will be correctly decoded by the receiver.
[0128] Fig.11 1 is a flow chart illustrating an exemplary process 1100 for determining a code rate for each of a plurality of UCIs sent with a plurality of TBs according to some aspects of the present disclosure. As described below, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Figure 7 The UE 700 illustrated in FIG. 10 may be configured to perform process 1100. In some examples, process 1100 may be performed by any suitable device or component for performing the functions or algorithms described below.
[0129] At block 1102, UE 700 receives (e.g., using transceiver 710) an UL grant or UL scheduling DCI, which includes a grant for a PUSCH transmission with multiple TBs. Here, each respective TB in the multiple TBs is associated with a respective TB priority index. In addition, the UL grant includes multiple beta offsets. For example, communication control circuit system 740 may process scheduling information from scheduling entity 600, including scheduling DCI.
[0130] At block 1104, the UE 700 may encode a first UCI among the plurality of UCIs at a first code rate based on the first β offset; and at block 1106, the UE 700 may encode a second UCI among the plurality of UCIs at a second code rate based on the second β offset. That is, the UE may map the corresponding UCI to the corresponding TB, wherein the code rate of the corresponding TB is known. The UE 700 may determine the code rate of the corresponding UCI based on the corresponding TB of the corresponding UCI using the β offset received at block 1102.
[0131] At block 1108, UE 700 may transmit (eg, utilizing transceiver 710) a PUSCH transmission including a plurality of UCIs multiplexed with a plurality of TBs. Here, each UCI in the plurality of UCIs is associated with a respective UCI priority index and encoded at a suitable code rate as described above.
[0132] Fig.12 1 is a flow chart illustrating an exemplary process 1200 for determining a code rate for each of a plurality of UCIs sent with a plurality of TBs according to further aspects of the present disclosure. As described below, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Figure 7 The UE 700 illustrated in FIG. 1 may be configured to perform process 1200. In some examples, process 1200 may be performed by any suitable device or component for performing the functions or algorithms described below.
[0133] At block 1202, UE 700 receives (e.g., using transceiver 710) an UL grant or UL scheduling DCI, which includes a grant for a PUSCH transmission with multiple TBs. Here, each respective TB in the plurality of TBs is associated with a respective TB priority index. In addition, the UL grant includes a beta offset parameter. For example, communication control circuit system 740 may process scheduling information from scheduling entity 600, including scheduling DCI.
[0134] At block 1204, the UE 700 may encode a first UCI among the plurality of UCIs at a first code rate based on the β offset; and at block 1106, the UE 700 may encode a second UCI among the plurality of UCIs at a second code rate based on the β offset. That is, the UE may map the respective UCI to the respective TBs, wherein the code rate of the respective TBs is known. The UE 700 may determine the code rate of the respective UCI based on the corresponding TB of the respective UCI using the β offset received at block 1202. As described above, the first code rate and the second code rate may be the same or may be different. For example, the UE 700 may be an RRC configured with two β offset tables or values, such that the UE may determine the β offset to be applied based on the β offset parameter received at block 1202 and the corresponding stored β offset table or value. And in other examples, the UE may select the β offset to be used for each TB based on some suitable factor, such as the maximum β offset value based on the received β offset parameter and the corresponding β offset table or value.
[0135] At block 1208, UE 700 may transmit (eg, utilizing transceiver 710) a PUSCH transmission including a plurality of UCIs multiplexed with a plurality of TBs. Here, each UCI in the plurality of UCIs is associated with a respective UCI priority index and encoded at a suitable code rate as described above.
[0136] In addition, when the UE is to multiplex multiple UCIs onto a PUSCH having multiple TBs, the UE may apply the same α factor to each TB or may apply different α factors to different corresponding TBs. For example, the UE may be an RRC configured with an α factor applied to each of the multiple TBs. In another example, the UE may be an RRC configured with multiple (e.g., 2) α factors to be applied to the multiple corresponding TBs. In examples where the UE is configured with multiple α factors, in some examples, when the UL scheduling DCI schedules only one TB in the PUSCH, the UE may apply the first α factor of these multiple α factors.
[0137] Fig.13 1 is a flow chart illustrating an exemplary process 1300 for determining an upper bound on the amount of resources used to carry control information on multiple TBs in a PUSCH transmission according to some aspects of the present disclosure. As described below, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Figure 7 The UE 700 illustrated in FIG. 1 may be configured to perform process 1300. In some examples, process 1300 may be performed by any suitable device or component for performing the functions or algorithms described below.
[0138] At block 1302, UE 700 receives (e.g., using transceiver 710) an UL grant or UL scheduling DCI, which includes a grant for a PUSCH transmission with multiple TBs. Here, each respective TB in the plurality of TBs is associated with a respective TB priority index. For example, communication control circuit system 740 may process scheduling information from scheduling entity 600, including scheduling DCI.
[0139] At block 1304, UE 700 receives (eg, utilizing transceiver 710) an alpha parameter. As described above, the alpha parameter may be received utilizing any suitable control signaling, including but not limited to RRC signaling, via MAC-CE, via DCI, etc.
[0140] At block 1306, the UE 700 may determine an upper bound on the amount of resources (e.g., UCI resources) used to carry control information on each corresponding TB in the plurality of TBs based on the α parameter. For example, if the total amount of resources on a TB is equal to N, the maximum amount of resources available for UCI on the TB may be equal to α multiplied by N.
[0141] At block 1308, UE 700 may transmit (e.g., using transceiver 710) a PUSCH transmission including a plurality of UCIs multiplexed with a plurality of TBs. Here, each UCI in the plurality of UCIs is associated with a corresponding UCI priority index. That is, each TB is associated with a corresponding TB priority index, and each multiplexed UCI is associated with a corresponding UCI priority index.
[0142] Fig.14 1 is a flow chart illustrating another exemplary process 1300 for determining an upper bound on the amount of resources used to carry control information on multiple TBs in a PUSCH transmission according to further aspects of the present disclosure. As described below, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Figure 7 The UE 700 illustrated in FIG. 1 may be configured to perform process 1300. In some examples, process 1300 may be performed by any suitable device or component for performing the functions or algorithms described below.
[0143] At block 1402, UE 700 receives (e.g., using transceiver 710) an UL grant or UL scheduling DCI, which includes a grant for a PUSCH transmission with multiple TBs. Here, each respective TB in the plurality of TBs is associated with a respective TB priority index. For example, communication control circuit system 740 may process scheduling information from scheduling entity 600, including scheduling DCI.
[0144] At block 1404, UE 700 receives (eg, utilizing transceiver 710) a plurality of alpha parameters. As described above, the alpha parameters may be received utilizing any suitable control signaling, including, but not limited to, RRC signaling.
[0145] At block 1406, the UE 700 may determine an upper bound on the amount of resources (e.g., UCI resources) used to carry control information on each corresponding TB in the plurality of TBs based on a corresponding α parameter in the plurality of α parameters. For example, if the total amount of resources on a given TB is equal to N, the maximum amount of resources available for UCI on the TB may be equal to the corresponding α parameter multiplied by N.
[0146] At block 1408, UE 700 may transmit (e.g., using transceiver 710) a PUSCH transmission including a plurality of UCIs multiplexed with a plurality of TBs. Here, each UCI in the plurality of UCIs is associated with a corresponding UCI priority index. That is, each TB is associated with a corresponding TB priority index, and each multiplexed UCI is associated with a corresponding UCI priority index.
[0147] According to another aspect of the present disclosure, when multiple UCIs are multiplexed or piggybacked onto multiple TBs for PUSCH transmission, the UE may continue to determine which UCI is mapped to which TB. Fig.15 Several examples of UCI mapping to TBs are illustrated according to a scenario where two UCIs are mapped to two TBs. A person skilled in the art will recognize that Fig.15 The concepts illustrated in and described below can be easily extended to any suitable number of UCIs and TBs in a PUSCH transmission. Figure 8 In the PUSCH 806 illustrated in FIG. 8 , two UCIs are labeled UCI1 and UCI2, and two TBs are labeled TB1 and TB2. Each UCI may have its own UCI priority index (PIA or PIB), and each TB may have its own TB priority index (PIC or PID). The UCI priority indexes may be the same or different; and the TB priority indexes may be the same or different. In addition, each TB may have a corresponding TB index, MCS, and number of layers.
[0148] In a first example, if UCI1 and UCI2 have the same priority index (i.e., PIA=PIB), the UE may process the two UCIs in the same manner as each other. For example, as shown in scenario 1502, if the first UCI1 is mapped to the first TB1, the second UCI2 may be mapped to the second TB2. In another example, if UCI1 and UCI2 have the same priority as each other, the UE may map the UCI to a TB (if one exists) having the same priority index as the UCI. For example, when PIA=PIB=PIC, both UCI1 and UCI2 may be mapped to TB1.
[0149] However, when the priority indices of different UCIs multiplexed into a given PUSCH are different from each other, it may not be clear which UCI is mapped to which TB. In some examples, the UE may apply scenario 1502 and may map the UCIs to different corresponding TBs. For example, a first UCI1 may be mapped to a first TB1, and a second UCI2 may be mapped to a second TB2 (or vice versa). In some other examples, the UE may apply one of scenarios 1504, 1506, or 1508, and may map a first UCI to both TB1 and TB2, and may map a second UCI to a second TB2. As an example, a UCI with a high priority (e.g., priority index 1) may be mapped to both TB1 and TB2, and a UCI with a low priority (e.g., priority index 0) may be mapped to a second TB2.
[0150] When the UE maps two UCIs to a given TB (such as, for example, in scenarios 1504, 1506, 1508, 1510, or 1512), the corresponding UCIs may have the same priority as each other, or different priorities from each other. In some examples, the UE may avoid mapping UCIs of different priorities to the same TB. That is, when UCIs of different priorities are to be mapped to different TBs, the UE may map the corresponding UCIs to different TBs, regardless of whether the two TBs are associated with the same priority or different priorities.
[0151] When the UE maps the UCI to multiple TBs, the UE may complete the mapping in various suitable ways. For example, as illustrated in scenarios 1504 and 1506, the first UCI1 may be repeated on both TB1 and TB2. In another example, as illustrated in scenario 1508, the first UCI1 (e.g., high priority HP UCI) is mapped across both TB1 and TB2. For example, the UE may encode the payload of the first UCI1 into a joint coded message and then split the joint coded message across two TBs.
[0152] Scenario 1506 shows an example in which a first UCI1 (e.g., HP UCI) is repeated on two UCIs, while a second UCI2 (e.g., LPUCI) is jointly encoded and mapped across two TBs. Scenario 1508 shows an example in which a first UCI1 is jointly encoded and mapped across two TBs, while a second UCI2 is mapped to a second TB2. Scenario 1510 shows an example in which a first UCI1 is mapped to a first TB1 and a second UCI2 is jointly encoded and mapped across two TBs. And scenario 1512 shows an example in which both UCI1 and UCI2 are jointly encoded and mapped to two TBs. The choice of which mapping scheme to adopt may depend on the priority of the corresponding UCI, and may depend on the availability of resources for carrying the UCI. In some examples described below, if the UCI resources are insufficient to carry a complete UCI, at least a portion of the UCI may be omitted from the TB.
[0153] The above discussion relates to the first TB1 and the second TB2. In various aspects of the present disclosure, for the purpose of mapping, the first TB and the second TB may be distinguished by any one of a variety of factors or a combination of these factors, including, for example, a UCI priority index of the corresponding UCI, an MCS of the corresponding TB, a TB index, a redundancy version (RV) of the corresponding TB or a new data indicator (NDI) of the corresponding TB, UCI resource availability, a number of layers of the corresponding TB, or a TB priority index.
[0154] For example, the UE may map multiple UCIs to multiple TBs based on different TB indices of those TBs. For example, a high priority UCI may be mapped to a lower TB index, while a low priority UCI may be mapped to a higher TB index (or vice versa). This is a simple mechanism that utilizes the already existing TB indexes for sorting and sequencing the TBs.
[0155] In another example, the UE may map UCI to its corresponding TB based on different modulation and coding schemes (MCS) used for the corresponding TBs. For example, the UE may map high-priority UCI to a TB with a higher MCS (e.g., higher order modulation, higher code rate, etc.), and may map low-priority UCI to a TB with a lower MCS, or vice versa. In the example of mapping high-priority UCI to a TB with a lower MCS, this may improve the reliability of communication of the high-priority UCI.
[0156] In another example, the UE may map the UCI to its corresponding TB based on different new data indicators (NDIs) associated with the corresponding TBs. For example, if two TBs are scheduled with different NDIs (i.e., one TB is a new transmission of a TB and the other TB is a retransmission of a previously failed TB), the UE may prioritize the TB whose NDI indicates new data as the first TB and treat the TB whose NDI indicates retransmission as the second TB.
[0157] In another example, the UE may map the UCI to its corresponding TB based on different redundancy version (RV) indicators associated with the corresponding TBs. For example, the UE may determine whether a TB is a first TB or a second TB according to a predefined RV order (e.g., RV0>RV2>RV3>RV1, or RV0>RV1>RV2>RV3, etc.). For example, if two TBs are associated with RV2 and RV3, the TB associated with RV2 may be the first TB, and the TB associated with RV3 may be the second TB. In another example, the UE may determine that a TB with RV 0 is the first TB, and a TB associated with any other TB is the second TB.
[0158] In another example, the UE may map the UCI to its corresponding TB based on the different number of layers of the corresponding TB. For example, the UE may map a first UCI (e.g., a high priority UCI) to a TB with more (or fewer) layers, and may map a second UCI (e.g., a low priority UCI) to a TB with fewer (or more) layers. In some examples, the UE may select a TB with fewer layers to carry the high priority UCI, and select a TB with more layers to carry the low priority UCI. This is because the fewer the number of layers, the smaller the channel quality difference between the corresponding layers, and thus a TB with fewer layers can provide greater communication stability for the high priority UCI.
[0159] In yet another example, the UE may map UCIs to their corresponding TBs based on different TB priority indexes. For example, the UE may map a first UCI (e.g., a high priority UCI) to a high priority TB, and a second UCI (e.g., a low priority UCI) to a low priority TB (or vice versa). In some cases, the UE may adopt a rule of mapping UCIs only to TBs with the same or corresponding priority indexes. For example, in the case of having high priority TBs and low priority TBs, the UE may multiplex the high priority UCI with the high priority TBs, and may multiplex the low priority UCI with the low priority TBs.
[0160] In another example, the UE may map UCI to its corresponding TB based on different UCI resource availabilities in the corresponding TBs. For example, the UE may identify the first TB (for mapping, for example, high-priority UCI) as a TB with more (or less) UCI resource availability. The UCI resource availability may be based on the size of the TB and the above-mentioned α factor, which sets an upper bound on the UCI resource availability in the TB. In this way, for example, the probability that the entire high-priority UCI is multiplexed onto its corresponding TB without omitting any part (the omission rules are described below) may be increased.
[0161] In the above example, the UE may map multiple UCIs to multiple TBs based on one or more suitable factors. For example, if the UE maps based on the MCS of the TBs, and two TBs use the same MCS, the UE may use one or more other factors (such as the number of layers of the TBs) to sort the TBs. A person of ordinary skill in the art will recognize that any combination of factors may be used in this manner to map the UCIs to the TBs. In addition, the UE may apply the set of factors in any suitable order or sequence. For example, the sorting may be: TB priority index first, MCS second, number of layers third, and TB index fourth. In this example, the UE may first check the priority levels of the two TBs. If the TBs have different priorities, the UE will follow the rules for mapping UCIs based on the TB priority index explained above. However, if the TBs have the same priority as each other, the UE may check the MCSs of the two TBs for the second time. If the TBs have different MCSs, the UE will follow the rules for mapping UCIs based on the MCS explained above. However, if the TBs have the same MCS, the UE may check the number of layers of the two TBs for the third time. If the TBs have different numbers of layers, the UE will follow the rules for mapping UCI based on the number of layers explained above. However, if the TBs have the same number of layers, the UE may check the TB index a fourth time and follow the rules for mapping UCI based on the TB index explained above. In another example, the ordering may be: TB priority index first, number of layers second, MCS third, and NDI fourth, RV fifth, and TB index sixth. Of course, any suitable ordering or sequence of any suitable combination of some or all of the factors discussed above may be utilized in a given implementation.
[0162] In addition, the mapping of UCI may depend on the amount of UCI resources available on one or two TBs. Fig.15 , in scenario 1504, high priority UCI1 is repeated on both the first TB1 and the second TB2. In the illustrated example, low priority UCI2 is mapped to the second TB2. However, it may be the case that not enough UCI resources are available for UCI2 in TB2. Therefore, the UE may map a portion of the second UCI2 to the second TB2 and may omit a portion of the second UCI2.
[0163] Similarly, in scenario 1506, the high-priority UCI1 is repeated on two TBs, while the low-priority UCI2 is jointly mapped across two TBs. In this case, the UE may map the low-priority UCI2 to the remaining resources on TB1 and TB2. For example, a part of UCI2 may be allocated to the remaining UCI resources in the first TB1, and a part of UCI2 may be allocated to the remaining UCI resources in the second TB2. However, it may happen that there are not enough UCI resources in TB1 and TB2 available for UCI2. Therefore, the UE may omit a part of the second UCI2.
[0164] In another aspect of the present disclosure, the UE may determine which part of the UCI to omit based on UCI resource availability. For example, if there are not enough UCI resources available on a TB (or a set of TBs) to multiplex a given UCI, the UE may simply discard the UCI with the lower priority. In another example, the UE may map a part of the UCI to a TB and may omit or discard a part of the UCI. In some aspects, the UE may adopt CSI priority levels to identify which part of the UCI to omit or discard.
[0165] In some wireless communication networks, as discussed above, the UCI may include various information types, such as but not limited to CSI reports, HARQ-ACK feedback, SR, etc. In some examples, a given UCI may include multiple information elements of these types. When the UCI includes a set of K CSI reports, the UE may sort the set of K CSI reports based on their priority levels. Note that this CSI priority level is different from the UCI priority index and the PUSCH priority index discussed above. According to one aspect of the present disclosure, if the amount of UCI resources available for UCI multiplexing in the PUSCH is not sufficient to contain the entire set of K CSI reports, the UE may multiplex a subgroup of K' < K CSI reports with the highest priority among the K CSI reports. Here, K' is such that K' CSI reports can be included in the PUSCH, but K'+1 CSI reports cannot be included in the PUSCH due to limited resource availability. As discussed above, the upper bound of the UCI resource availability in the PUSCH can be determined by adopting an appropriate α factor.
[0166] According to another aspect of the present disclosure, it may happen that a RAN node requests a UE to send an aperiodic CSI report (A-CSI) or a semi-persistent CSI report (SP-CSI) together with a PUSCH transmission. That is, the RAN node may provide an UL grant (or schedule DCI) that schedules PUSCH transmission and requests an A-CSI report or SP-CSI report. In some examples, the RAN node may indicate (e.g., via an UL grant, via MAC-CE, via RRC signaling, or any other suitable control signaling) the priority of the associated A-CSI or SP-CSI. In other examples, the UE may adopt a rule that always considers such an A-CSI or SP-CSI request as a high priority (or, in other examples, as a low priority).
[0167] Fig.16 16 is a flow chart illustrating an exemplary process 1600 for CSI report omission in multi-TB PUSCH transmissions according to some aspects of the present disclosure. As described below, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Figure 7 The UE 700 illustrated in FIG. 1600 may be configured to perform process 1600. In some examples, any suitable device or component for performing the functions or algorithms described below may perform process 1600.
[0168] In the illustrated process 1600, a UE is scheduled for a 2-TB PUSCH transmission and has a set of UCI (HARQ-ACK, CSI reports, SR, etc.) that it wishes to map to those TBs for transmission on the PUSCH. The set of UCI includes a set of K CSI reports, each CSI report having a corresponding CSI priority associated therewith.
[0169] At block 1602, the UE may determine a TB ranking or sequencing based on one of the following: a TB index, a TB MCS, a RV, a NDI, a TB UCI resource availability, a TB layer number, or a TB priority index, or some combination thereof. As described above, the TB ranking may be used to determine a first TB for mapping a high priority UCI and a second TB for mapping a low priority UCI.
[0170] At optional block 1604, the UE may map a set of HARQ-ACKs to one or two TBs. That is, in some examples, resources may be allocated for HARQ-ACK feedback before resources are allocated for CSI reporting, so that HARQ-ACK feedback may not be omitted from mapping to TBs. Some examples may include other UCI types, such as a scheduling request (SR) in block 1604.
[0171] At block 1606, the UE may determine the UCI resource availability on the first TB. For example, as described above, the UE may determine an upper bound on the amount of resources available for carrying UCI based on the total amount of resources on the first TB multiplied by a factor (α factor) configurable by RRC signaling.
[0172] At block 1608, the UE may map a set of K1 CSI reports to the first TB. Here, K1 ≤ K is the maximum number of CSI reports that may be included in the first TB. In some examples, K1 may include the set of highest-priority CSI reports. That is, the UE may sort a set of K CSI reports in order of priority and map the subgroup K1 of the highest-priority CSI reports according to that sorting such that the UCI resources for carrying the K1 CSI reports (excluding those UCI resources already allocated for HARQ-ACK, etc. at block 1604) are not greater than the upper bound on the UCI resource availability in the TB determined at block 1606. For example, K1 + 1 CSI reports would require an amount of UCI resources greater than the upper bound. In another example, K may be part of the CSI reports having the same priority as the first TB. For example, when the first TB is a high-priority TB, the UE may map high-priority CSI reports to the first TB.
[0173] At block 1610, if K1 < K such that there are still CSI reports to be sent, the UE may determine the UCI resource availability on the second TB. For example, as described above, the UE may determine an upper bound on the amount of resources for carrying UCI based on the total amount of resources on the second TB multiplied by a factor (α factor) configurable by RRC signaling.
[0174] At block 1612, the UE may map a set of K2 remaining CSI reports to the second TB. Here, (K1 + K2) ≤ K such that K2 is the maximum number of remaining CSI reports that may be included in the second TB. In some examples, K2 may include the set of highest-priority remaining CSI reports. In other examples, K2 may be part of the CSI reports having the same priority as the second TB. For example, when the second TB is a low-priority TB, the UE may map low-priority CSI reports to the second TB. Generally, the determination of K2 follows the principle described above for the determination of K1, i.e., fitting as many of the highest-priority CSI reports as possible.
[0175] At block 1614, if there are any remaining CSI reports (i.e., if K - (K1 + K2) > 0), then these remaining lowest-priority CSI reports are discarded by the UE. And at block 1616, the UE may transmit (e.g., using transceiver 710) a PUSCH including the UCI mapped to the first TB and the second TB.
[0176] Fig.17 1700 is a flow chart illustrating an exemplary process 1700 for PUSCH reception with multiple TBs according to some aspects of the present disclosure. As described below, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Figure 6 The RAN node 600 illustrated in FIG. 17 may be configured to perform process 1700. In some examples, process 1700 may be performed by any suitable device or means for performing the functions or algorithms described below.
[0177] At block 1702, the RAN node 600 transmits (e.g., using the transceiver 610) an UL grant or UL scheduling DCI that includes a grant for a PUSCH transmission with multiple TBs. Here, each respective TB in the multiple TBs is associated with a respective TB priority index. For example, the scheduling circuitry 640 may generate scheduling information including the scheduling DCI. When each respective TB is associated with a respective TB priority index, a single PUSCH transmission may carry multiple TBs with different priorities.
[0178] At block 1704, the RAN node 600 receives a scheduled PUSCH including a plurality of TBs. For example, the transceiver 610 may be used to receive a scheduled transmission including TBs with a configured MCS, number of layers, etc. from a UE.
[0179] Other embodiments with various features :
[0180] Embodiment 1: A method, apparatus, and non-transitory computer-readable medium for receiving an UL grant, the UL grant comprising a grant for sending a PUSCH having multiple TBs, each respective TB in the multiple TBs being associated with a respective TB priority index; and sending the PUSCH comprising the multiple TBs.
[0181] Embodiment 2: A method, apparatus, and non-transitory computer-readable medium according to embodiment 1, wherein at least two of the multiple TBs are associated with respective TB priority indexes that are different from each other, and wherein the UL grant includes a set of respective TB priority index indicators for indicating the corresponding TB priority index of each respective TB of the multiple TBs.
[0182] Embodiment 3: The method, apparatus, and non-transitory computer-readable medium according to any one of embodiments 1 to 2 further includes sending a plurality of UL control information (UCI) multiplexed with the PUSCH.
[0183] Embodiment 4: A method, an apparatus, and a non-transitory computer-readable medium according to any one of Embodiments 1 to 3, wherein the UL grant indicates multiple β offsets, and further includes: encoding a first UCI among the multiple UCIs at a first coding rate based on a first β offset among the multiple β offsets; and encoding a second UCI among the multiple UCIs at a second coding rate based on a second β offset among the multiple β offsets.
[0184] Embodiment 5: A method, an apparatus, and a non-transitory computer-readable medium according to any one of Embodiments 1 to 3, wherein the UL grant indicates a β offset, and further includes: encoding a first UCI among the multiple UCIs at a first coding rate based on the β offset; and encoding a second UCI among the multiple UCIs at a second coding rate based on the β offset.
[0185] Embodiment 6: The method, apparatus, and non-transitory computer-readable medium according to any one of Embodiments 1 to 5 further include receiving an α parameter; and determining an upper bound on the amount of resources used to carry control information on each corresponding TB in the multiple TBs based on the α parameter.
[0186] Embodiment 7: The method, apparatus, and non-transitory computer-readable medium according to any one of Embodiments 1 to 5 further include receiving multiple α parameters corresponding to the multiple TBs; and determining a corresponding upper bound on the amount of resources used to carry control information on each corresponding TB in the multiple TBs based on corresponding α parameters in the multiple α parameters.
[0187] Embodiment 8: The method, apparatus, and non-transitory computer-readable medium of any one of Embodiments 1 to 7, wherein each UCI of the plurality of UCIs is associated with a corresponding UCI priority index.
[0188] Embodiment 9: The method, apparatus, and non-transitory computer-readable medium according to any one of Embodiments 1 to 8 further include mapping a first group of one or more UCIs among the multiple UCIs to a first TB among the multiple TBs; and mapping a second group of one or more UCIs among the multiple UCIs to a second TB among the multiple TBs, wherein the first TB includes at least one of the following: a TB priority index different from that of the second TB; a TB index different from that of the second TB; a redundancy version different from that of the second TB; a new data indicator different from that of the second TB; a modulation and coding scheme (MCS) different from that of the second TB; a different amount of UCI resource availability from that of the second TB; or a different number of layers from that of the second TB.
[0189] Embodiment 10: A method, an apparatus, and a non-transitory computer-readable medium according to any one of Embodiments 1 to 9, wherein: the multiple UCIs include multiple channel state information (CSI) reports, each corresponding CSI report in the multiple CSI reports has a corresponding CSI report priority index; the first group of one or more UCIs includes a first group of one or more CSI reports in the multiple CSI reports; the second group of one or more UCIs includes a second group of one or more CSI reports in the multiple CSI reports; and each corresponding CSI report in the first group of one or more CSI reports has a higher CSI report priority index than each corresponding CSI report in the second group of one or more CSI reports.
[0190] Embodiment 11: A method, apparatus, and non-transitory computer-readable medium according to any one of embodiments 1 to 10, wherein mapping the first group of one or more UCIs to the first TB also includes determining the number of the first group of one or more CSI reports based on: an upper bound on the amount of resources used to carry control information on the first TB; and a corresponding size of each corresponding CSI report in the multiple CSI reports.
[0191] Embodiment 12: The method, apparatus, and non-transitory computer-readable medium according to any one of embodiments 1 to 11 further includes abandoning sending at least one CSI report having a lower CSI report priority index than each corresponding CSI report in the second group of one or more CSI reports.
[0192] Embodiment 13: The method, apparatus, and non-transitory computer-readable medium according to any one of Embodiments 1 to 11 further include determining a first amount of resources that can be used to carry the UCI on the first TB and a second amount of resources that can be used to carry the UCI on the second TB; and abandoning sending the at least one CSI report when the first amount of resources and the second amount of resources are insufficient to include at least one CSI report among the multiple CSI reports, wherein the at least one CSI report has a lower CSI report priority index than each CSI report in the second group of one or more CSI reports.
[0193] Embodiment 14: The method, apparatus, and non-transitory computer-readable medium according to any one of Embodiments 1 to 13 further includes receiving a mapping indication, wherein the mapping indication is used to indicate whether the multiple UCIs are mapped to one TB among the multiple TBs or to more than one TB among the multiple TBs.
[0194] Embodiment 15: The method, apparatus, and non-transitory computer-readable medium according to any one of Embodiments 1 to 14 further includes mapping a first UCI among the multiple UCIs to a first TB among the multiple TBs, and mapping a second UCI among the multiple UCIs to a second TB among the multiple TBs, wherein the first TB has the same priority as the second TB.
[0195] The detailed descriptions set forth above in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, those skilled in the art will readily appreciate that these concepts may be practiced without these specific details. In some cases, this specification provides well-known structures and components in block diagram form in order to avoid blurring such concepts.
[0196] Although this specification describes certain aspects and examples with reference to some illustrations, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, each specific implementation and / or use may be generated via an integrated chip (IC) implementation and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of the described innovations may occur. The specific implementation may span the spectrum from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the spectrum of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the disclosed technology. In some actual settings, the device in conjunction with the aspects and features may also necessarily include additional components and features for the specific implementation and practice of the embodiments protected and described by the claims. For example, the transmission and reception of wireless signals includes several components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the disclosed technology can be practiced in various devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having various sizes, shapes, and configurations.
[0197] By way of example, various aspects of the present disclosure may be implemented within systems defined by 3GPP, such as Fifth Generation New Radio (5G NR), Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may 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 actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.
[0198] The present disclosure uses the word "exemplary" to mean "serving as an example, instance, or illustration". Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The present disclosure uses the terms "coupled" and / or "communicatively coupled" to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C can still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object can be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The present disclosure uses the terms "circuit" and "circuitry" broadly to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuits) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure).
[0199] Figures 1 to 17 One or more of the components, steps, features, and / or functions illustrated in the disclosure may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 17 The apparatus, devices and / or components illustrated in the examples may be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.
[0200] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The attached method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented unless specifically stated herein.
[0201] The applicant provides this description to enable any person skilled in the art to practice the various aspects described herein. Those skilled in the art will readily recognize various modifications to these aspects, and the general principles defined herein may be applied to other aspects. The applicant does not intend that the claims be limited to the various aspects shown herein, but should be given the full scope consistent with the language of the claims, wherein unless specifically stated otherwise, references to elements in the singular form are not intended to mean "one and only one", but "one or more". Unless otherwise specifically stated, the present disclosure uses the term "some" to refer to one or more. The phrase "at least one" referring to a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to those of ordinary skill in the art are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be disclosed to the public, regardless of whether such disclosure is explicitly stated in the claims. No claim element is to be construed under 35 USC §112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the phrase “step for.”
Claims
1. A device for wireless communication, comprising: processor; Memory; as well as a transceiver coupled to the processor, wherein the processor is coupled to the memory and is configured to: receiving, via the transceiver, an uplink (UL) grant comprising a grant for a physical uplink shared channel (PUSCH) transmission having a plurality of transport blocks (TBs), each respective TB of the plurality of TBs being associated with a respective TB priority index; and The PUSCH including the plurality of TBs is transmitted via the transceiver.
2. The device according to claim 1, wherein at least two TBs of the plurality of TBs are associated with respective TB priority indexes that are different from each other, and The UL grant includes a set of respective TB priority index indicators for indicating a corresponding TB priority index of each respective TB in the plurality of TBs.
3. The apparatus of claim 1 , wherein the processor is further configured to: A plurality of UL control information (UCI) multiplexed with the PUSCH is transmitted via the transceiver.
4. The apparatus of claim 3, wherein the UL grant indicates a plurality of β offsets, and The processor is further configured to: encoding a first UCI among the plurality of UCIs at a first coding rate based on a first β offset among the plurality of β offsets; and A second UCI among the plurality of UCIs is encoded at a second coding rate based on a second β offset among the plurality of β offsets.
5. The device according to claim 3, wherein the UL grant indicates a β offset, and The processor is further configured to: encoding a first UCI among the plurality of UCIs at a first coding rate based on the β offset; and A second UCI among the plurality of UCIs is encoded at a second coding rate based on the β offset.
6. The apparatus of claim 3, wherein the processor is further configured to: receiving, via the transceiver, an alpha parameter; and An upper bound on the amount of resources used to carry control information on each corresponding TB in the plurality of TBs is determined based on the α parameter.
7. The apparatus of claim 3, wherein the processor is further configured to: receiving, via the transceiver, a plurality of alpha parameters corresponding to the plurality of TBs; and A respective upper bound on an amount of resources used to carry control information on each respective TB in the plurality of TBs is determined based on a respective α parameter in the plurality of α parameters. The apparatus of claim 3 , wherein each UCI of the plurality of UCIs is associated with a corresponding UCI priority index.
9. The apparatus of claim 8, wherein the processor is further configured to: Mapping a first group of one or more UCIs in the plurality of UCIs to a first TB in the plurality of TBs; and mapping a second set of one or more UCIs in the plurality of UCIs to a second TB in the plurality of TBs, The first TB includes at least one of the following: a TB priority index different from that of the second TB; a TB index different from the second TB; a redundancy version different from that of the second TB; an indicator of new data different from the second TB; a modulation and coding scheme (MCS) different from that of the second TB; A different amount of UCI resource availability than the second TB; or A different number of layers than the second TB.
10. The device according to claim 9, wherein: The plurality of UCIs include a plurality of channel state information (CSI) reports, each respective CSI report in the plurality of CSI reports having a respective CSI report priority index; The first set of one or more UCIs includes a first set of one or more CSI reports among the plurality of CSI reports; The second set of one or more UCIs comprises a second set of one or more CSI reports among the plurality of CSI reports; and Each respective CSI report in the first set of one or more CSI reports has a higher CSI reporting priority index than each respective CSI report in the second set of one or more CSI reports.
11. The apparatus of claim 10, wherein the processor configured to map the first set of one or more UCIs to the first TB is further configured to determine a quantity of the first set of one or more CSI reports based on: an upper bound on the amount of resources used to carry control information on the first TB; and a respective size of each respective CSI report in the plurality of CSI reports.
12. The apparatus of claim 10, wherein the processor is further configured to: Sending at least one CSI report having a lower CSI report priority index than each corresponding CSI report in the second set of one or more CSI reports is abandoned.
13. The apparatus of claim 10, wherein the processor is further configured to: Determine a first amount of resources that can be used to carry the UCI on the first TB and a second amount of resources that can be used to carry the UCI on the second TB; and when the first amount of resources and the second amount of resources are insufficient to include at least one CSI report among the multiple CSI reports, giving up sending the at least one CSI report, The at least one CSI report has a lower CSI report priority index than each CSI report in the second set of one or more CSI reports.
14. The apparatus of claim 3, wherein the processor is further configured to: A mapping indication is received via the transceiver, the mapping indication being used to indicate whether the plurality of UCIs are mapped to one TB among the plurality of TBs or to more than one TB among the plurality of TBs.
15. The apparatus of claim 3, wherein the processor is further configured to: mapping a first UCI among the plurality of UCIs to a first TB among the plurality of TBs, and A second UCI among the plurality of UCIs is mapped to a second TB among the plurality of TBs, wherein the first TB has the same priority as the second TB.
16. A method of wireless communication, comprising: receiving an uplink (UL) grant comprising a grant for a physical uplink shared channel (PUSCH) transmission having a plurality of transport blocks (TBs), each respective TB of the plurality of TBs being associated with a respective TB priority index; as well as The PUSCH including the multiple TBs is transmitted.
17. The method according to claim 16, wherein at least two TBs of the plurality of TBs are associated with respective TB priority indexes that are different from each other, and The UL grant includes a set of respective TB priority index indicators for indicating a corresponding TB priority index of each respective TB in the plurality of TBs.
18. The method according to claim 16, further comprising: A plurality of UL control information (UCI) multiplexed with the PUSCH is transmitted.
19. The method of claim 18, wherein the UL grant indicates a plurality of beta offsets, The method further comprises: encoding a first UCI among the plurality of UCIs at a first coding rate based on a first β offset among the plurality of β offsets; as well as A second UCI among the plurality of UCIs is encoded at a second coding rate based on a second β offset among the plurality of β offsets.
20. The method according to claim 18, wherein the UL grant indicates a β offset, The method further comprises: encoding a first UCI among the plurality of UCIs at a first coding rate based on the β offset; as well as A second UCI among the plurality of UCIs is encoded at a second coding rate based on the β offset.
21. The method of claim 18, further comprising: Receive α parameter; as well as An upper bound on the amount of resources used to carry control information on each corresponding TB in the plurality of TBs is determined based on the α parameter.
22. The method of claim 18, further comprising: receiving a plurality of alpha parameters corresponding to the plurality of TBs; as well as A respective upper bound on an amount of resources used to carry control information on each respective TB in the plurality of TBs is determined based on a respective α parameter in the plurality of α parameters.
23. The method of claim 18, wherein each UCI of the plurality of UCIs is associated with a corresponding UCI priority index.
24. The method according to claim 23, further comprising: Mapping a first group of one or more UCIs in the plurality of UCIs to a first TB in the plurality of TBs; as well as mapping a second set of one or more UCIs in the plurality of UCIs to a second TB in the plurality of TBs, The first TB includes at least one of the following: a TB priority index different from that of the second TB; a TB index different from the second TB; a redundancy version different from that of the second TB; an indicator of new data different from the second TB; a modulation and coding scheme (MCS) different from that of the second TB; A different amount of UCI resource availability than the second TB; or A different number of layers than the second TB.
25. The method of claim 24, wherein: The plurality of UCIs include a plurality of channel state information (CSI) reports, each respective CSI report in the plurality of CSI reports having a respective CSI report priority index; The first set of one or more UCIs includes a first set of one or more CSI reports among the plurality of CSI reports; The second set of one or more UCIs comprises a second set of one or more CSI reports among the plurality of CSI reports; and Each respective CSI report in the first set of one or more CSI reports has a higher CSI reporting priority index than each respective CSI report in the second set of one or more CSI reports.
26. The method of claim 25, wherein mapping the first set of one or more UCIs to the first TB comprises determining a number of the first set of one or more CSI reports based on: an upper bound on the amount of resources used to carry control information on the first TB; and a respective size of each respective CSI report in the plurality of CSI reports.
27. The method of claim 25, further comprising: Sending at least one CSI report having a lower CSI report priority index than each corresponding CSI report in the second set of one or more CSI reports is abandoned.
28. The method of claim 25, further comprising: Determine a first resource amount that can be used to carry the UCI on the first TB and a second resource amount that can be used to carry the UCI on the second TB; as well as when the first amount of resources and the second amount of resources are insufficient to include at least one CSI report among the multiple CSI reports, giving up sending the at least one CSI report, The at least one CSI report has a lower CSI report priority index than each CSI report in the second set of one or more CSI reports.
29. The method of claim 18, further comprising: A mapping indication is received, the mapping indication being used to indicate whether the plurality of UCIs are mapped to one TB among the plurality of TBs or to more than one TB among the plurality of TBs.
30. The method of claim 18, further comprising: mapping a first UCI among the plurality of UCIs to a first TB among the plurality of TBs, and mapping a second UCI among the plurality of UCIs to a second TB among the plurality of TBs, The first TB has the same priority as the second TB.
31. An apparatus for wireless communication, comprising: processor; a memory coupled to the processor; as well as a transceiver coupled to the processor, The processor is configured to: transmitting, via the transceiver, an uplink (UL) grant, the uplink (UL) grant comprising a grant for a physical uplink shared channel (PUSCH) transmission having a plurality of transport blocks (TBs), each respective TB of the plurality of TBs being associated with a respective TB priority index; as well as The PUSCH including the plurality of TBs is received via the transceiver.
32. A method of wireless communication, comprising: transmitting an uplink (UL) grant, the uplink (UL) grant comprising a grant for a physical uplink shared channel (PUSCH) transmission having a plurality of transport blocks (TBs), each respective TB of the plurality of TBs being associated with a respective TB priority index; as well as The PUSCH including the plurality of TBs is received.
