Determining beta offset for uplink control information on uplink shared channel with two transport blocks

Abstract

A method for wireless communication at a user equipment (UE) includes receiving, from a network node, signaling indicating a set of beta offset values associated with one transport block (TB) and two TBs. The method also includes receiving, from the network node, downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH) associated with one or two TBs. The method further includes transmitting uplink control information (UCI) via a number of resource elements (REs) on a PUSCH associated with one TB or both TBs based on receiving the DCI or RRC message. The number of REs can be determined based on beta offset values from a set of beta offset values from a set of sets of beta offset values. The set of beta offset values can be selected based on whether the UCI is transmitted on the PUSCH associated with one TB or both TBs.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly to determining a beta offset for uplink control channel information (UCI) sent on an uplink shared channel associated with two transport blocks (TBs). Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephone, video, data, messaging and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE Advanced is an enhancement set to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the Third Generation Partnership Project (3GPP). Narrowband (NB) Internet of Things (IoT) and enhanced machine type communication (eMTC) are enhancement sets of LTE for machine type communication.

[0003] A wireless communication network may include multiple base stations (BSs) that may support communications for multiple user equipment (UEs). User equipment (UEs) may communicate with a base station (BS) via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a BS to a UE, while an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail, a BS may be referred to as a Node B, an evolved Node B (eNB), a gNB, an access point (AP), a radio head, a transmit and receive point (TRP), a new radio (NR) BS, a 5G Node B, etc.

[0004] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at city, country, region, and even global levels. New Radio (NR) (which may also be referred to as 5G) is an enhancement set of the LTE mobile standard released by the Third Generation Partnership Project (3GPP). NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation, so as to better support mobile broadband Internet access.

[0005] In some examples, the UE may transmit uplink control information (UCI) via an uplink shared channel such as a physical uplink shared channel (PUSCH). The payload of the UCI may include, for example, channel state information (CSI), hybrid automatic repeat request (HARQ) information, or configuration grant uplink control information (CG-UCI). The number of resource elements used to transmit the UCI may be based on an offset value selected from a set of β offset values ​​(e.g., β offset (β 偏移 ) value). Each offset value in the offset value set may correspond to one or both of the UCI type and / or payload of the UCI. The offset value set may be dynamically indicated, for example, in the DCI or semi-statically configured via signaling such as radio resource control (RRC) signaling. Summary of the invention

[0006] In one aspect of the present disclosure, a method for wireless communication at a UE includes receiving signaling from a network node indicating multiple beta offset value sets associated with one transport block (TB) and two TBs. The method also includes receiving downlink control information (DCI) or a radio resource control (RRC) message scheduling a physical uplink shared channel (PUSCH) associated with one TB or two TBs from the network node. The method also includes sending uplink control information (UCI) via a certain number of resource elements (REs) on the PUSCH associated with one TB or two TBs based on receiving the DCI or RRC message. The number of REs can be determined based on a beta offset value from a beta offset value set in a plurality of beta offset value sets. The beta offset value set can be selected from a plurality of beta offset value sets based on whether UCI is sent on a PUSCH associated with one TB or two TBs.

[0007] Another aspect of the present disclosure relates to an apparatus comprising a component for receiving signaling indicating multiple beta offset value sets associated with one TB and two TBs from a network node. The apparatus also includes a component for receiving a DCI or RRC message from the network node that schedules a PUSCH associated with one TB or two TBs. The apparatus further includes a component for sending UCI via a certain number of REs on a PUSCH associated with one TB or two TBs based on receiving a DCI or RRC message. The number of REs can be determined based on a beta offset value of a beta offset value set from a plurality of beta offset value sets. The beta offset value set can be selected from a plurality of beta offset value sets based on whether UCI is sent on a PUSCH associated with one TB or two TBs.

[0008] In another aspect of the present disclosure, a non-transitory computer-readable medium having non-transitory program code recorded thereon is disclosed. The program code is executed by a processor and includes a program code for receiving signaling indicating multiple beta offset value sets associated with one TB and two TBs from a network node. The program code also includes a program code for receiving a DCI or RRC message for scheduling a PUSCH associated with one TB or two TBs from a network node. The program code also includes a program code for sending UCI via a certain number of REs on a PUSCH associated with one TB or two TBs based on receiving a DCI or RRC message. The number of REs can be determined based on a beta offset value of a beta offset value set from a plurality of beta offset value sets. The beta offset value set can be selected from a plurality of beta offset value sets based on whether UCI is sent on a PUSCH associated with one TB or two TBs.

[0009] Another aspect of the present disclosure relates to an apparatus, comprising: a processor; and a memory coupled to the processor and storing instructions that, when executed by the processor, are operable to cause the apparatus to receive signaling indicating multiple beta offset value sets associated with one TB and two TBs from a network node. Execution of the instructions also causes the apparatus to receive a DCI or RRC message scheduling a PUSCH associated with one TB or two TBs from the network node. Execution of the instructions further causes the apparatus to send UCI via a certain number of REs on a PUSCH associated with one TB or two TBs based on receiving the DCI or RRC message. The number of REs may be determined based on a beta offset value from a beta offset value set in a plurality of beta offset value sets. The beta offset value set may be selected from a plurality of beta offset value sets based on whether UCI is sent on a PUSCH associated with one TB or two TBs.

[0010] In one aspect of the present disclosure, a method for wireless communication at a UE includes receiving signaling from a network node indicating multiple beta offset value sets associated with two TBs. The method also includes receiving a DCI or RRC message from the network node that schedules a PUSCH associated with the two TBs. The method also includes sending a first uplink UCI via a certain number of first REs on a PUSCH associated with a first TB of the two TBs based on receiving the DCI or RRC message. The number of first REs can be determined based on beta offset values ​​from a beta offset value set in a plurality of beta offset value sets. The beta offset value set can be selected based on whether a second UCI is multiplexed on a second RE within a second TB of the two TBs, the first RE corresponding to the second RE.

[0011] Another aspect of the present disclosure relates to an apparatus comprising a component for receiving signaling indicating multiple beta offset value sets associated with two TBs from a network node. The apparatus also includes a component for receiving a DCI or RRC message scheduling a PUSCH associated with the two TBs from the network node. The apparatus further includes a component for sending a first uplink UCI via a certain number of first REs on a PUSCH associated with a first TB of the two TBs based on receiving a DCI or RRC message. The number of first REs can be determined based on beta offset values ​​from a beta offset value set in a plurality of beta offset value sets. The beta offset value set can be selected based on whether a second UCI is multiplexed on a second RE within a second TB of the two TBs, the first RE corresponding to the second RE.

[0012] In another aspect of the present disclosure, a non-transitory computer-readable medium having non-transitory program code recorded thereon is disclosed. The program code is executed by a processor and includes a program code for receiving signaling indicating multiple beta offset value sets associated with two TBs from a network node. The program code also includes a program code for receiving a DCI or RRC message for scheduling a PUSCH associated with the two TBs from a network node. The program code also includes a program code for sending a first uplink UCI via a certain number of first REs on a PUSCH associated with a first TB of the two TBs based on receiving a DCI or RRC message. The number of first REs can be determined based on a beta offset value from a beta offset value set in a plurality of beta offset value sets. The beta offset value set can be selected based on whether a second UCI is multiplexed on a second RE within a second TB of the two TBs, and the first RE corresponds to the second RE.

[0013] Another aspect of the present disclosure relates to a device, comprising: a processor; and a memory coupled to the processor and storing instructions that, when executed by the processor, are operable to cause the device to receive signaling indicating multiple beta offset value sets associated with two TBs from a network node. Execution of the instructions further causes the device to receive a DCI or RRC message scheduling a PUSCH associated with the two TBs from the network node. Execution of the instructions also causes the device to send a first uplink UCI via a certain number of first REs on a PUSCH associated with a first TB of the two TBs based on receiving the DCI or RRC message. The number of first REs can be determined based on a beta offset value from a beta offset value set in a plurality of beta offset value sets. The beta offset value set can be selected based on whether a second UCI is multiplexed on a second RE within a second TB of the two TBs, the first RE corresponding to the second RE.

[0014] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices, and processing systems as generally described with reference to and as illustrated in the accompanying drawings and description.

[0015] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above in order to better understand the subsequent specific embodiments. Additional features and advantages will be described. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the disclosed concepts in terms of both their organization and method of operation and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings is provided for the purpose of illustration and description and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order that the features of the present disclosure may be understood in detail, a more specific description may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain aspects of the present disclosure and therefore should not be considered as limiting the scope thereof, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0018] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a user equipment (UE) in a wireless communication network according to various aspects of the present disclosure.

[0019] Figure 3 is a block diagram illustrating an example decomposed base station architecture in accordance with various aspects of the present disclosure.

[0020] Figure 4A is a timing diagram illustrating an example of configuring multiple beta offset value sets associated with one transport block (TB) and two TBs according to various aspects of the present disclosure.

[0021] Figure 4B is a block diagram illustrating an example of a physical uplink shared channel (PUSCH) having one TB and a PUSCH having two TBs.

[0022] Figure 5A is a timing diagram illustrating an example of configuring multiple beta offset value sets associated with two TBs according to various aspects of the present disclosure.

[0023] Figure 5B is a block diagram illustrating an example of a PUSCH with two TBs according to various aspects of the present disclosure.

[0024] Figure 6 is a flow chart illustrating an example process performed, for example, by a user equipment (UE) according to various aspects of the present disclosure.

[0025] Figure 7 is a flow chart illustrating an example process, for example, performed by a UE, according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0026] The following is a more comprehensive description of various aspects of the present disclosure with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. Based on the teachings, those skilled in the art should recognize that the scope of the present disclosure is intended to cover any aspect of the present disclosure, whether the aspect is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect. For example, a device or a method can be implemented using any number of aspects described. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or structures and functionality as a supplement to the various aspects of the present disclosure described or in addition. It should be understood that any aspect of the present disclosure disclosed can be embodied by one or more elements of the claims.

[0027] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] It should be noted that although various aspects may be described using terms commonly associated with 5G and later wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations (such as and including 3G and / or 4G technologies).

[0029] In some examples, a user equipment (UE) may transmit uplink control information (UCI) via an uplink shared channel such as a physical uplink shared channel (PUSCH). The payload of the UCI may include, for example, channel state information (CSI), hybrid automatic repeat request (HARQ) information, or configuration grant uplink control information (CG-UCI). The number of resource elements used to transmit the UCI may be based on an offset value selected from a set of offset values ​​(e.g., a β offset (β 偏移 ) value). Each β offset value in the β offset value set may correspond to one or both of the UCI type and / or the payload of the UCI. The β offset value set may be dynamically indicated, for example, in the DCI or semi-statically configured via signaling such as radio resource control (RRC) signaling.

[0030] Some wireless communication systems may support multi-layer uplink transmissions. In such systems, two codewords may be supported for uplink transmissions with more than one layer. For example, a physical uplink shared channel (PUSCH) may be scheduled using two transport blocks (TBs), each TB being associated with different transmission parameters such as a modulation and coding scheme (MCS), a new data indicator (NDI), a redundancy version (RV), and / or other parameters. In some examples, the number of coded modulation symbols for each layer of UCI transmitted on a PUSCH with a single TB may be different from the number of coded modulation symbols for each layer of UCI transmitted on a PUSCH with multiple TBs. In such examples, a single set of β offset values ​​may not be used for both a PUSCH with one TB and a PUSCH with multiple TBs. Various aspects of the present disclosure relate to configuring one or more sets of β offset values ​​for a PUSCH scheduled with multiple TBs.

[0031] Figure 11 is a diagram illustrating a network 100 in which various aspects of the present disclosure may be practiced. The network 100 may be a 5G or NR network, or some other wireless network (such as an LTE network). The wireless network 100 may include a plurality of BSs 110 (shown as BSs 110a, BSs 110b, BSs 110c, and BSs 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE), and may also be referred to as a base station, an NR BS, a Node B, a gNB, a 5G Node B, an access point, a transmission and reception point (TRP), a network node, a network entity, etc. A base station may be implemented as a clustered base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a side link node, etc. A base station may be implemented in a clustered or monolithic base station architecture, or alternatively, in a decomposed base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0032] Each BS can provide communication coverage for a specific geographical area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0033] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "AP", "Node B", "5G NB", "TRP", and "cell" may be used interchangeably.

[0034] In some aspects, the cell need not be stationary, and the geographic area of ​​the cell may move according to the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transport network.

[0035] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and transmit the transmissions of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown, a relay station 110d may communicate with the macro BS 110a and the UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0036] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0037] For example, BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and core network 130 may exchange communications via backhaul links 132 (e.g., S1, etc.). Base stations 110 may communicate with each other directly or indirectly (e.g., through core network 130) through other backhaul links (e.g., X2, etc.).

[0038] The core network 130 may be an evolved packet core (EPC), which may include at least one mobile management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may be a control node that handles signaling between the UE 120 and the EPC. All user IP packets may be delivered through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to the IP services of the network operator. The operator's IP services may include the Internet, the intranet, the IP multimedia subsystem (IMS), and the packet switched (PS) streaming media services.

[0039] The core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of the base stations 110 or access node controllers (ANCs) may interface with the core network 130 via a backhaul link 132 (e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communications with the UE 120. In some configurations, the various functions of each access network entity or base station 110 may be distributed across various network devices (e.g., radio heads and access network controllers), or merged into a single network device (e.g., base station 110).

[0040] UE 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be stationary or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device or a satellite radio), a component or sensor of a vehicle, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0041] One or more UEs 120 may establish a protocol data unit (PDU) session for a network slice. In some cases, the UE 120 may select a network slice based on an application or subscription service. By enabling different network slices to serve different applications or subscriptions, the UE 120 may improve its resource utilization in the wireless network 100 while also meeting the performance specifications of the respective applications of the UE 120. In some cases, the AMF ( Figure 1 ), to serve the network slice used by UE 120. In addition, session management of the network slice can be performed by an access and mobility management function (AMF).

[0042] UE 120 may include a β offset module 140. For simplicity, only one UE 120d is shown as including a β offset module 140. β offset module 140 may be configured to perform reference Figure 6 and Figure 7Steps of process 600 and / or process 700 are described.

[0043] The core network 130 or the base station 110 may include a β offset module 138 for: sending signaling indicating a plurality of β offset value sets associated with two TBs; sending a DCI or RRC message scheduling a PUSCH associated with the two TBs; and receiving a first uplink UCI via a certain number of first REs on a PUSCH associated with a first TB of the two TBs based on sending the DCI or RRC message. In some examples, the number of first REs may be based on β offset values ​​from a β offset value set in a plurality of β offset value sets. The β offset value set may be selected based on whether a second UCI is multiplexed on a second RE within a second TB of the two TBs. The first RE may correspond to a second RE.

[0044] Additionally or alternatively, the beta offset module 138 may: send signaling indicating a plurality of beta offset value sets associated with one TB and two TBs; send a DCI or RRC message scheduling a PUSCH associated with one TB or two TBs; and receive UCI via a certain number of REs on a PUSCH associated with one TB or two TBs based on sending the DCI or RRC message. The number of REs may be based on a beta offset value from a beta offset value set in a plurality of beta offset value sets. The beta offset value set selected from the plurality of beta offset value sets may be based on whether UCI is received on a PUSCH associated with one TB or two TBs.

[0045] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. For example, MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as customer premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (such as a processor component, a memory component, etc.).

[0046] Generally speaking, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. In a given geographic area, each frequency can support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0047] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein performed by base station 110. For example, base station 110 may configure UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, medium access control-control element (MAC-CE), or via system information (e.g., system information block (SIB)).

[0048] As indicated above, Figure 1 are provided as examples only. Other examples may be found in Figure 1 The examples described are different.

[0049] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown, where the base station and the UE may be Figure 1 A base station in the base station and Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0050] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Reducing the MCS reduces throughput but increases the reliability of transmission. The transmit processor 220 may also process system information (e.g., for semi-static resource allocation information (SRPI) and the like) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM) or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to convey additional information.

[0051] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (where applicable), and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0052] On the uplink, at the UE 120, a transmit processor 264 may receive data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from a controller / processor 280 and process the data and control information. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266 (where applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 254, detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the core network 130 via the communication unit 244. The core network 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0053] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with configuring a β offset value for a PUSCH having multiple TBs, as described in more detail elsewhere. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of may perform or direct e.g. Figure 6 and Figure 7 The processes and / or operations of other processes as described. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0054] In some aspects, UE 120 may include: a component for receiving signaling indicating multiple beta offset value sets associated with two TBs from a network node; a component for receiving a DCI or RRC message from the network node for scheduling a PUSCH associated with the two TBs; and a component for sending a first uplink UCI via a certain number of first REs on a PUSCH associated with a first TB of the two TBs based on receiving the DCI or RRC message. Additionally or alternatively, UE 120 may include: a component for receiving signaling indicating multiple beta offset value sets associated with one TB and two TBs from a network node; a component for receiving a DCI or RRC message from the network node for scheduling a PUSCH associated with one TB or two TBs; and a component for sending UCI via a certain number of REs on a PUSCH associated with one TB or two TBs based on receiving the DCI or RRC message. Such a component may include a combination Figure 2 One or more components of a UE 120 or base station 110 are described.

[0055] As indicated above, Figure 2 are provided as examples only. Other examples may be found in relation to Figure 2 The examples described are different.

[0056] 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 network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit and receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0057] 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 throughout 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 (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0058] 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 utilized 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)). Disaggregation 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.

[0059] 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 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0060] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RTRIC 315, and SMO framework 305) may include one or more interfaces, or may 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 that is configured to receive or send signals to one or more of the other units via 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) that is configured to receive or send signals to one or more of the other units on a wireless transmission medium, or both.

[0061] 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 using an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., 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 DU330 for network control and signaling.

[0062] DU 330 may correspond to a logical unit that includes one or more base station functions to control 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.) depending at least in part on a functional partition such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using 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.

[0063] The 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 120. 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 DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0064] 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) platform 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 an O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via an O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0065] 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 on 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 311 with the near-RT RIC 325.

[0066] In some implementations, in order to generate the 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 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).

[0067] In some examples, the UE may transmit uplink control information (UCI) via an uplink shared channel such as a physical uplink shared channel (PUSCH). The payload of the UCI may include, for example, channel state information (CSI), hybrid automatic repeat request (HARQ) information, or configuration grant uplink control information (CG-UCI). The number of resource elements used to transmit the UCI may be based on a β offset value selected from a set of offset values ​​(e.g., β offset (β 偏移 ) value). Each β offset value in the β offset value set may correspond to one or both of the UCI type and / or the payload of the UCI. The β offset value set may be dynamically indicated, for example, in the DCI or semi-statically configured via signaling such as radio resource control (RRC) signaling.

[0068] In some examples, a semi-static indication of a set of beta offset values ​​may be applied with fallback downlink control information (DCI) for uplink assignments. The same set of beta offset values ​​as the fallback DCI may be reused for HARQ feedback and CSI. In some examples, the set of beta offset values ​​associated with the semi-static indication may be different from the set of beta offset values ​​associated with the dynamic indication. The semi-static indication may be the default configuration for a non-fallback DCI for UL assignments.

[0069] As discussed, one or more sets of offset values ​​(e.g., β offset values) may be configured via RRC signaling. Each set of β offset values ​​may include multiple entries (e.g., β offset values), each β offset value may correspond to a UCI type and / or a UCI payload. In some examples, an index to a set of β offset values ​​may be dynamically indicated. As an example, a downlink control channel such as a physical downlink control channel (PDCCH) may send a message dynamically indicating an index to a set of β offset values. As another example, for fallback DCI, a first set of β offset values ​​may be applied where the dynamic indication is configured via RRC signaling.

[0070] As discussed, the set of beta offset values ​​may include multiple beta offset values. In some examples, the multiple beta offset values ​​may include a first beta offset index value for HARQ feedback, a second beta offset index value for CSI part one, and a third beta offset index value for CSI part two. The values ​​for the first beta offset index value, the second beta offset index value, and the third beta offset index value may be based on values ​​defined in a 3GPP communication standard such as 3GPP 38.213.

[0071] Some wireless communication systems may support multi-layer uplink transmission. Multi-layer uplink transmission may be used to improve uplink throughput and / or reliability via simultaneous multi-panel uplink transmission. In such systems, two codewords may be supported for uplink transmissions with more than one layer. For example, a physical uplink shared channel (PUSCH) may be scheduled using two transport blocks (TBs), each TB being associated with different transmission parameters such as a modulation and coding scheme (MCS), a new data indicator (NDI), a redundancy version (RV), and / or other parameters. In some examples, the number of coded modulation symbols for each layer of UCI transmitted on a PUSCH with a single TB may be different from the number of coded modulation symbols for each layer of UCI transmitted on a PUSCH with multiple TBs. In such examples, a single set of β offset values ​​may not be used for both a PUSCH with one TB and a PUSCH with multiple TBs. Various aspects of the present disclosure relate to one or more sets of β offset values ​​configured for a PUSCH scheduled with multiple TBs.

[0072] Figure 4A 4 is a timing diagram illustrating an example 400 of configuring multiple beta offset value sets associated with one TB and two TBs according to various aspects of the present disclosure. As shown in example 400, UE 120 may communicate with network node 410, such as reference Figure 1 and Figure 2 The base station 110 described or as referenced Figure 3 CU 310, DU 330 or RU 340 as described. Figure 4AAs shown in , at time t1, UE 120 may receive signaling indicating multiple beta offset value sets associated with one TB and two TBs. As discussed, the signaling may be RRC signaling. In some implementations, the multiple beta offset value sets indicated via signaling at time t1 may include a first set of beta offset values ​​and a second set of beta offset values. In such implementations, the first set of beta offset values ​​may be associated with UCI transmission on a PUSCH associated with one TB. In addition, the second set of beta offset values ​​may be associated with UCI transmission on a PUSCH associated with two TBs. Furthermore, in such implementations, the signaling indicating multiple beta offset value sets may be a semi-static indication.

[0073] In some other implementations, the multiple beta offset value sets indicated via signaling at time t1 may include a first set of beta offset value sets and a second set of beta offset value sets. In such implementations, the first set of beta offset value sets may be associated with UCI transmissions on a PUSCH associated with one TB. In addition, the second set of beta offset value sets may be associated with UCI transmissions on a PUSCH associated with two TBs. In some examples, each beta offset value set in the first group and the second group may be associated with a different code point. In some such examples, the beta offset value set is selected from the first set of beta offset sets or the second set of beta offset sets based on a code point indicated via DCI (such as DCI scheduled for PUSCH transmission).

[0074] like Figure 4A As shown in example 400 of , at time t2, network node 410 may send a DCI or RRC message scheduling for a PUSCH transmission with one TB or two TBs. At time t3, UE 120 may determine the number of resource elements (REs) to be allocated for uplink control information (UCI). The number of REs may be based on a β offset value from a set of β offset values ​​selected from a plurality of β offset value sets configured via signaling received at time t1. The set of β offset values ​​may be selected based on whether UCI is sent on a PUSCH associated with one TB or two TBs. At time t4, after determining the number of REs, UE 120 may send UCI on a PUSCH associated with one TB or two TBs.

[0075] As reference Figure 4A As discussed, UE 120 may receive signaling indicating multiple sets of beta offset values ​​associated with one TB and two TBs. Figure 4B 4 is a block diagram illustrating an example of a PUSCH having one TB 420 and a PUSCH having two TBs 440A and 440B. Figure 4BAs shown in the example of , DCI 424 can schedule a PUSCH with a single TB 420. In this example, UCI 426 can be sent on REs within the single TB 420. In some examples, the UCI 426 sent on the PUSCH with the single TB 420 can be associated with a first set of beta offset values ​​from a plurality of beta offset value sets indicated via downlink signaling. In some other examples, the UCI 426 sent on the PUSCH with the single TB 420 can be associated with a first set of beta offset values ​​430. Figure 4B As shown in the example of , the first set of beta offset value sets 430 includes a first set 432A of beta offset values, a second set 432B of beta offset values, a third set 432C of beta offset values, and a fourth set 432D of beta offset values. The first set 430 of beta offset values ​​is not limited to four sets of beta offset values; additional or fewer sets may be configured. As discussed, in some examples, each set 432A, 432B, 432C, and 432D of beta offset values ​​may be associated with a different code point, such that one of the sets 432A, 432B, 432C, and 432D of beta offset values ​​may be selected based on a code point indicated via downlink signaling (such as a DCI).

[0076] like Figure 4B As shown in the example of , DCI 444 may schedule a PUSCH with two TBs 440A and 440B. Figure 4B In the example of , UCI 426 is sent on REs within both TBs 440A and 440B. Figure 4B In other examples (not shown in FIG. 4 ), UCI 426 may be sent on an RE within one of the two TBs 440A and 440B. In some examples, UCI 426 sent on a PUSCH having two TBs 440A and 440B may be associated with a second set of β offset values ​​from a plurality of β offset value sets indicated via downlink signaling. The second set of β offset values ​​may be different from the first set of β offset values ​​associated with a PUSCH having a single TB 420. In some other examples, UCI 426 sent on a PUSCH having two TBs 440A and 440B may be associated with a second set of β offset values ​​446. Figure 4BAs shown in the example of , the second set of β offset value sets 446 includes a first set 448A of β offset values, a second set 448B of β offset values, a third set 448C of β offset values, and a fourth set 448D of β offset values. The second set 446 of β offset value sets is not limited to four sets of β offset values; additional or fewer sets may be configured. As discussed, in some examples, each set 448A, 448B, 448C, and 448D of β offset values ​​may be associated with a different code point, such that one of the sets 448A, 448B, 448C, and 448D of β offset values ​​may be selected based on a code point indicated via downlink signaling (such as a DCI). The second set 446 of β offset value sets associated with a PUSCH having two TBs 440A and 440B may be different from the first set 430 of β offset value sets associated with a PUSCH having one TB 420.

[0077] In some examples, a first UCI may be assigned to an RE within a first TB of a PUSCH having two TBs, and a second UCI may be multiplexed on an RE within a second TB of a PUSCH having two TBs. In some such examples, the REs assigned to the first UCI and the second UCI may be the same RE (e.g., corresponding REs on different TBs). In some implementations, the UE may select a set of β offset values ​​from a plurality of sets of β offset values ​​based on whether the two UCIs are multiplexed on the same REs of different TBs.

[0078] Figure 5A 5 is a timing diagram illustrating an example 500 of configuring multiple beta offset value sets associated with two TBs according to various aspects of the present disclosure. As shown in example 500, UE 120 may communicate with network node 510, such as reference Figure 1 and Figure 2 The base station 110 described or as referenced Figure 3 CU 310, DU 330 or RU 340 as described. Figure 5AAs shown in , at time t1, UE 120 may receive signaling, such as RRC signaling, indicating multiple beta offset value sets associated with two TBs. The two TBs may be associated with a single PUSCH. In some examples, a first UCI may be assigned to an RE within a first TB of the two TBs. In such examples, a second UCI may be multiplexed on a second RE within a second TB of the two TBs. In some such examples, the first RE may correspond to the second RE. In some specific implementations, the multiple beta offset value sets indicated via signaling at time t1 may include a first set of beta offset values ​​and a second set of beta offset values. In such specific implementations, the first set of beta offset values ​​may be associated with a first UCI transmission on a first TB of the two TBs, where other UCIs (e.g., second UCIs) are not multiplexed on a second RE of a second TB of the two TBs. Additionally, the second set of beta offset values ​​may be associated with a first UCI transmission on a first TB of the two TBs, where a second UCI is multiplexed on a second RE of a second TB of the two TBs. In addition, in such specific implementations, the signaling indicating multiple beta offset value sets may be a semi-static indication.

[0079] In some other implementations, the multiple beta offset value sets indicated via signaling at time t1 may include a first set of beta offset value sets and a second set of beta offset value sets. In such implementations, the first set of beta offset value sets may be associated with a first UCI transmission on a first TB of two TBs, where no other UCI (e.g., a second UCI) is multiplexed on a second RE of a second TB of the two TBs. Additionally, the second set of beta offset value sets may be associated with a first UCI transmission on a first TB of the two TBs, where a second UCI is multiplexed on a second RE of a second TB of the two TBs. In some examples, each beta offset value set in the first set of beta offset sets and the second set of beta offset sets may be associated with a different code point. In some such examples, the beta offset value set is selected from the first set of beta offset sets or the second set of beta offset sets based on a code point indicated via DCI (such as DCI scheduled for PUSCH transmission).

[0080] like Figure 5AAs shown in example 500, at time t2, the network node 510 may send a DCI or RRC message for scheduling a PUSCH transmission with two TBs. Additionally, at time t3, the UE 120 may determine the number of REs to be allocated for UCI transmitted via a PUSCH associated with the two TBs. The number of REs allocated for transmitting the UCI may be determined based on a β offset value from a set of β offset values ​​selected from a plurality of β offset value sets configured via signaling received at time t1. As discussed above, the set of β offset values ​​may be selected based on whether the second UCI and the first UCI are multiplexed on the same RE within two TBs associated with the same PUSCH. At time t4, after determining the number of REs, the UE 120 may transmit the first UCI on one of the two TBs of the PUSCH scheduled via the DCI at time t2. At ( Figure 5A In some examples (not shown in FIG), at time t4, UE 120 may also send a second UCI on another TB of the two TBs of the PUSCH. In this example, the first UCI and the second UCI may be multiplexed on the same REs of the two TBs.

[0081] As reference Figure 5A As discussed, UE 120 may receive signaling indicating multiple sets of beta offset values ​​associated with two TBs. Figure 5B is a block diagram illustrating an example of a PUSCH with two TBs according to various aspects of the present disclosure. Figure 5B As shown in the example of , a first DCI 524 may schedule a first PUSCH having two TBs 520A and 520B. In this example, a first UCI 526A may be sent on REs within the first TB 520A. In this example, the payload of the first UCI 526A may be HARQ feedback. Thus, the number of REs allocated to the first UCI 526A may be based on a HARQ feedback β offset value from a set of β offset values ​​selected from a plurality of β offset values ​​indicated via signaling (such as RRC signaling). Additionally, if Figure 5B As shown in , the second UCI 526B may be sent on REs within the second TB 530B associated with the second PUSCH scheduled via the second DCI 536. The second PUSCH may be associated with two TBs 530A and 530B. In this example, the payload of the second UCI 526B may be CSI part two. Therefore, the number of REs allocated to the second UCI 526B may be based on the CSI part two β offset value in the set of β offset values ​​selected from the plurality of β offset values.

[0082] exist Figure 5BIn the example of , the first UCI 526A and other UCIs are not multiplexed on the same RE of different TBs 520A and 520B associated with the same PUSCH. Therefore, the set of β offset values ​​selected from the plurality of sets of β offset values ​​may be a first set of β offset values ​​applied when two UCIs are not multiplexed on the same RE of different TBs associated with the same PUSCH. Alternatively, when the first UCI 526A and other UCIs are not multiplexed on the same RE of different TBs 520A and 520B associated with the same PUSCH, a first set of β offset value sets 530 may be configured for the first UCI 526A. Figure 5B As shown in the example of , the first set of beta offset value sets 530 includes a first set 532A of beta offset values, a second set 532B of beta offset values, a third set 532C of beta offset values, and a fourth set 532D of beta offset values. The first set 530 of beta offset values ​​is not limited to four sets of beta offset values; additional or fewer sets may be configured. As discussed, in some examples, each set 532A, 532B, 532C, and 532D of beta offset values ​​may be associated with a different code point, such that one of the sets 532A, 532B, 532C, and 532D of beta offset values ​​may be selected based on a code point indicated via downlink signaling (such as a DCI).

[0083] Additionally, if Figure 5B As shown in the example of , the third DCI 544 may schedule a third PUSCH having two TBs 540A and 540B. In this example, the third UCI 546A may be sent on REs within the first TB 540A. In this example, the payload of the third UCI 546A may be HARQ feedback. Thus, the number of REs allocated to the third UCI 546A may be based on a HARQ feedback β offset value from a set of β offset values ​​selected from a plurality of β offset values ​​indicated via signaling (such as RRC signaling). Additionally, if Figure 5B As shown in FIG. 5 , a fourth UCI 546B may be sent on REs within a second TB 540B associated with a third PUSCH scheduled via a third DCI 544. In this example, the payload of the fourth UCI 546B may be CSI part two. Thus, the number of REs allocated to the fourth UCI 546B may be based on a CSI part two β offset value in a set of β offset values ​​selected from a plurality of β offset values.

[0084] exist Figure 5BIn the example of , the third UCI 546A and the fourth UCI 546B are multiplexed on the same RE of different TBs 540A and 540B associated with the same PUSCH. Therefore, the set of β offset values ​​selected from the plurality of sets of β offset values ​​may be a second set of β offset values ​​applied when two UCIs are multiplexed on the same RE of different TBs associated with the same PUSCH. Alternatively, when the third UCI 546A and the fourth UCI 546B are multiplexed on the same RE of different TBs 540A and 540B associated with the same PUSCH, a second set of β offset values ​​550 may be configured for the third UCI 546A. Figure 5B As shown in the example of , the second set of β offset value sets 550 includes a first set 554A of β offset values, a second set 554B of β offset values, a third set 554C of β offset values, and a fourth set 554D of β offset values. The second set 550 of β offset value sets is not limited to four sets of β offset values; additional or fewer sets may be configured. As discussed, in some examples, each set 554A, 554B, 554C, and 554D of β offset values ​​may be associated with a different code point, such that one of the sets 554A, 554B, 554C, and 554D of β offset values ​​may be selected based on a code point indicated via downlink signaling (such as DCI). The first set 530 of β offset values ​​and the second set 550 of β offset values ​​may be configured via multiple sets of β offset values, which are indicated via signaling (such as RRC signaling).

[0085] Figure 6 6 is a flow chart illustrating an example process 600 performed, for example, by a UE, according to various aspects of the present disclosure. The example process 600 is an example of allocating REs for UCI based on a set of β offset values ​​selected from a plurality of sets of β offset values ​​associated with one TB and two TBs. The process 600 may be performed at a UE, such as a UE of reference Figure 1 , Figure 2 and Figure 3 UE 120 described. Figure 6As shown in , process 600 begins at box 602 by receiving signaling from a network node indicating multiple beta offset value sets associated with one TB and two TBs. At box 604, process 600 receives a DCI or RRC message from the network node that schedules a physical uplink shared channel (PUSCH) associated with one TB or two TBs. In some examples, the PUSCH may be a configuration grant (CG) PUSCH (CG-PUSCH). At box 606, process 600 sends UCI via a certain number of REs on the PUSCH associated with one TB or two TBs based on receiving the DCI or RRC message. In some examples, the number of REs may be determined based on a beta offset value from a beta offset value set in a plurality of beta offset value sets. In such examples, the beta offset value set may be selected from a plurality of beta offset value sets based on whether UCI is sent on a PUSCH associated with one TB or two TBs.

[0086] Figure 7 700 is a flow chart illustrating an example process 700 performed, for example, by a UE according to various aspects of the present disclosure. The example process 700 is an example of allocating REs for UCI based on a β offset value selected from a plurality of β offset value sets associated with two TBs. The process 700 may be performed at a UE, such as a UE of reference Figure 1 , Figure 2 and Figure 3 UE 120 described. Figure 7 As shown in , process 700 starts at box 702 by receiving signaling indicating multiple beta offset value sets associated with two TBs from a network node. At box 704, process 700 receives a DCI or RRC message from the network node that schedules a PUSCH associated with the two TBs. In some examples, the PUSCH can be a CG-PUSCH. At box 706, process 700 sends a first uplink UCI via a certain number of first REs on a PUSCH associated with a first TB of the two TBs based on receiving a DCI or RRC message. The number of first REs can be determined based on beta offset values ​​from a beta offset value set in a plurality of beta offset value sets. The beta offset value set can be selected based on whether a second UCI is multiplexed on a second RE within a second TB of the two TBs. The first RE may correspond to a second RE.

[0087] Specific implementation examples are described in the following numbered clauses:

[0088] Clause 1. A method for wireless communication at a user equipment (UE), comprising: receiving signaling indicating multiple β offset value sets associated with one transport block (TB) and two TBs from a network node; receiving downlink control information (DCI) or a radio resource control (RRC) message scheduling a physical uplink shared channel (PUSCH) associated with one TB or two TBs from the network node; and sending uplink control information (UCI) via a certain number of resource elements (REs) on the PUSCH associated with the one TB or the two TBs based on receiving the DCI or the RRC message, the number of REs being determined based on β offset values ​​from a set of β offset values ​​in the multiple β offset value sets, the set of β offset values ​​being selected from the multiple β offset value sets based on whether the UCI is sent on the PUSCH associated with the one TB or the two TBs.

[0089] Clause 2. The method of clause 1, wherein the signaling indicating the plurality of sets of beta offset values ​​is a semi-static indication.

[0090] Clause 3. A method according to any one of clauses 1 to 2, wherein: the multiple β offset value sets include a first set of β offset values ​​and a second set of β offset values; based on sending the UCI on the PUSCH associated with the one TB, the β offset value set corresponds to the first set of β offset values; and based on sending the UCI on the PUSCH associated with the two TBs, the β offset value set corresponds to the second set of β offset values.

[0091] Clause 4. A method according to Clause 1, wherein: the multiple β offset value sets include a first group of β offset value sets and a second group of β offset value sets; based on sending the UCI on the PUSCH associated with the one TB, the β offset value set corresponds to a β offset value set from the first group of β offset value sets; and based on sending the UCI on the PUSCH having the two TBs, the β offset value set corresponds to a β offset value set from the second group of β offset value sets.

[0092] Clause 5. A method according to clause 4, wherein: each set of beta offset values ​​in the first group of beta offset value sets and the second group of beta offset value sets is associated with a different code point; and the beta offset value sets correspond to code points indicated via the DCI.

[0093] Clause 6. A method according to any one of clauses 1 to 5, wherein: each of the multiple β offset value sets includes multiple β offset values; and each of the multiple β offset values ​​corresponds to one or both of a UCI type or a payload.

[0094] Clause 7. A method as described in any of clauses 1 to 6, wherein the signaling is RRC signaling.

[0095] Clause 8. A method as described in any of clauses 1 to 7, wherein the UCI comprises hybrid automatic repeat request (HARQ) feedback, channel state information (CSI) or configuration grant uplink control information (CG-UCI).

[0096] Clause 9. A method for performing wireless communications at a user equipment (UE), comprising: receiving signaling indicating multiple β offset value sets associated with two transport blocks (TBs) from a network node; receiving downlink control information (DCI) or a radio resource control (RRC) message scheduling a physical uplink shared channel (PUSCH) associated with the two TBs from the network node; and sending first uplink control information (UCI) via a certain number of first resource elements (REs) on the PUSCH associated with a first TB of the two TBs based on receiving the DCI or the RRC message, the number of first REs being determined based on β offset values ​​from a β offset value set in the multiple β offset value sets, the β offset value set being selected based on whether a second UCI is multiplexed on a second RE within a second TB of the two TBs, the first RE corresponding to the second RE.

[0097] Clause 10. The method of clause 9, wherein the signaling indicating the plurality of sets of beta offset values ​​is a semi-static indication.

[0098] Clause 11. A method according to any one of clauses 9 to 10, wherein: the multiple sets of β offset values ​​include a first set of β offset values ​​and a second set of β offset values; based on not multiplexing UCI on the second RE, the set of β offset values ​​corresponds to the first set of β offset values; and based on multiplexing the second UCI on the second RE, the set of β offset values ​​corresponds to the second set of β offset values.

[0099] Clause 12. A method according to Clause 9, wherein: the multiple β offset value sets include a first group of β offset value sets and a second group of β offset value sets; based on not multiplexing UCI on the second RE, the β offset value set corresponds to a β offset value set from the first group of β offset value sets; and based on multiplexing the second UCI on the second RE, the β offset value set corresponds to a β offset value set from the second group of β offset value sets.

[0100] Clause 13. A method according to clause 12, wherein: each respective set of beta offset values ​​in the first set of beta offset values ​​and the second set of beta offset values ​​is associated with a different code point; and the beta offset value sets correspond to code points indicated via the DCI.

[0101] Clause 14. A method according to any one of clauses 9 to 13, wherein: each of the multiple sets of β offset values ​​includes multiple β offset values; and each of the multiple β offset values ​​corresponds to one or both of a UCI type or a payload.

[0102] Clause 15. A method as described in any of clauses 9 to 14, wherein the signaling is RRC signaling.

[0103] Clause 16. A UE comprising a processor, a memory coupled to the processor, and instructions stored in the memory and operable when executed by the processor to cause the UE to perform any of clauses 1 to 8.

[0104] Clause 17. An apparatus configured for wireless communication, comprising at least one means for performing any of clauses 1-8.

[0105] Clause 18. A computer program comprising code for causing an apparatus to perform any one of clauses 1 to 8.

[0106] Clause 19. A UE comprising a processor, a memory coupled to the processor, and instructions stored in the memory and operable when executed by the processor to cause the UE to perform any of clauses 9 to 15.

[0107] Clause 20. An apparatus configured for wireless communication, comprising at least one means for performing any of clauses 9 to 15.

[0108] Clause 21. A computer program comprising code for causing an apparatus to perform any one of clauses 9 to 15.

[0109] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0110] As used, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used, a processor is implemented using hardware, firmware, and / or a combination of hardware and software.

[0111] Some aspects are described in conjunction with thresholds. As used, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0112] It will be apparent that the described systems and / or methods can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the aspects. Therefore, the operation and performance of these systems and / or methods are described without reference to specific software code, and it should be understood that software and hardware used to implement these systems and / or methods can be designed based at least in part on these descriptions.

[0113] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically set forth in the claims and / or is not disclosed in the specification. Although each dependent claim listed below may directly rely only on one claim, the disclosure of various aspects includes each dependent claim and each other claim combination in the claim set. The phrase "at least one" mentioned in the list of items refers to any combination of those items, including a single member. For example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc, and any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc, or any other sorting of a, b and c).

[0114] The elements, actions or instructions used should not be interpreted as critical or essential unless explicitly described as such. In addition, as used, the articles "one" and "an" are intended to include one or more items, and they can be used interchangeably with "one or more". In addition, as used, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related items and unrelated items, etc.), and can be used interchangeably with "one or more". If you want to refer to only one item, use the phrase "only one" or similar terms. In addition, as used, the terms "having" and the like are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise.

Claims

1. A method for wireless communication at a user equipment (UE), include: receiving signaling from a network node indicating a plurality of sets of beta offset values ​​associated with a transport block (TB) and two TBs; receiving, from the network node, a downlink control information (DCI) or a radio resource control (RRC) message scheduling a physical uplink shared channel (PUSCH) associated with one TB or two TBs; as well as Uplink control information (UCI) is sent via a certain number of resource elements (REs) on the PUSCH associated with the one TB or the two TBs based on receiving the DCI or the RRC message, the number of REs being determined based on a β offset value from a β offset value set in the multiple β offset value sets, the β offset value set being selected from the multiple β offset value sets based on whether the UCI is sent on the PUSCH associated with the one TB or the two TBs. 2 . The method of claim 1 , wherein the signaling indicating the plurality of beta offset value sets is a semi-static indication.

3. The method according to claim 2, in: The plurality of sets of beta offset values ​​include a first set of beta offset values ​​and a second set of beta offset values; The set of beta offset values ​​corresponds to the first set of beta offset values ​​based on sending the UCI on the PUSCH associated with the one TB; and The set of beta offset values ​​corresponds to the second set of beta offset values ​​based on sending the UCI on the PUSCH associated with the two TBs.

4. The method according to claim 1, in: The plurality of beta offset value sets include a first set of beta offset value sets and a second set of beta offset value sets; The set of beta offset values ​​corresponds to a set of beta offset values ​​from the first set of beta offset values ​​based on sending the UCI on the PUSCH associated with the one TB; and The set of beta offset values ​​corresponds to a set of beta offset values ​​from the second set of beta offset values ​​based on sending the UCI on the PUSCH having the two TBs.

5. The method according to claim 4, in: Each set of beta offset values ​​in the first set of beta offset values ​​and the second set of beta offset values ​​is associated with a different code point; and The set of beta offset values ​​corresponds to code points indicated via the DCI.

6. The method according to claim 1, in: Each beta offset value set in the plurality of beta offset value sets comprises a plurality of beta offset values; and Each beta offset value of the plurality of beta offset values ​​corresponds to one or both of a UCI type or a payload. The method according to claim 1 , wherein the signaling is RRC signaling.

8. The method of claim 1, wherein the UCI comprises hybrid automatic repeat request (HARQ) feedback, channel state information (CSI), or configuration grant uplink control information (CG-UCI).

9. An apparatus for wireless communication at a user equipment (UE), include: processor; and a memory coupled to the processor and storing instructions that, when executed by the processor, are operable to cause the apparatus to: receiving signaling from a network node indicating a plurality of sets of beta offset values ​​associated with a transport block (TB) and two TBs; receiving, from the network node, a downlink control information (DCI) or a radio resource control (RRC) message scheduling a physical uplink shared channel (PUSCH) associated with one TB or two TBs; as well as transmitting uplink control information (UCI) via a certain number of resource elements (REs) on the PUSCH associated with the one TB or the two TBs based on receiving the DCI or the RRC message, The number of REs is determined based on a β offset value from a set of β offset values ​​in the multiple β offset value sets, and the β offset value set is selected from the multiple β offset value sets based on whether the UCI is sent on the PUSCH associated with the one TB or the two TBs.

10. The apparatus of claim 9, wherein the signaling indicating the plurality of beta offset value sets is a semi-static indication.

11. The device according to claim 10, in: The plurality of sets of beta offset values ​​include a first set of beta offset values ​​and a second set of beta offset values; The set of beta offset values ​​corresponds to the first set of beta offset values ​​based on sending the UCI on the PUSCH associated with the one TB; and The set of beta offset values ​​corresponds to the second set of beta offset values ​​based on sending the UCI on the PUSCH associated with the two TBs.

12. The device according to claim 9, in: The plurality of beta offset value sets include a first set of beta offset value sets and a second set of beta offset value sets; The set of beta offset values ​​corresponds to a set of beta offset values ​​from the first set of beta offset values ​​based on sending the UCI on the PUSCH associated with the one TB; and The set of beta offset values ​​corresponds to a set of beta offset values ​​from the second set of beta offset values ​​based on sending the UCI on the PUSCH having the two TBs.

13. The device according to claim 12, in: Each set of beta offset values ​​in the first set of beta offset values ​​and the second set of beta offset values ​​is associated with a different code point; and The set of beta offset values ​​corresponds to code points indicated via the DCI.

14. The device according to claim 9, in: Each beta offset value set in the plurality of beta offset value sets comprises a plurality of beta offset values; and Each beta offset value of the plurality of beta offset values ​​corresponds to one or both of a UCI type or a payload.

15. The apparatus of claim 9, wherein the signaling is RRC signaling.

16. The apparatus of claim 9, wherein the UCI comprises hybrid automatic repeat request (HARQ) feedback, channel state information (CSI), or configuration grant uplink control information (CG-UCI).

17. A method for wireless communication at a user equipment (UE), include: receiving signaling from a network node indicating a plurality of sets of beta offset values ​​associated with two transport blocks (TBs); receiving, from the network node, a downlink control information (DCI) or a radio resource control (RRC) message scheduling a physical uplink shared channel (PUSCH) associated with two TBs; as well as Based on receiving the DCI or the RRC message, first uplink control information (UCI) is sent via a certain number of first resource elements (REs) on the PUSCH associated with the first TB of the two TBs, the number of first REs being determined based on a β offset value from a β offset value set in the multiple β offset value sets, the β offset value set being selected based on whether a second UCI is multiplexed on a second RE within a second TB of the two TBs, the first RE corresponding to the second RE.

18. The method of claim 17, wherein the signaling indicating the plurality of beta offset value sets is a semi-static indication.

19. The method according to claim 18, in: The plurality of sets of beta offset values ​​include a first set of beta offset values ​​and a second set of beta offset values; The set of beta offset values ​​corresponds to the first set of beta offset values ​​based on not multiplexing UCI on the second RE; and The set of beta offset values ​​corresponds to the second set of beta offset values ​​based on multiplexing the second UCI on the second RE.

20. The method according to claim 17, in: The plurality of beta offset value sets include a first set of beta offset value sets and a second set of beta offset value sets; The set of β offset values ​​corresponds to one set of β offset values ​​from the first set of β offset values ​​based on not multiplexing UCI on the second RE; and The set of β offset values ​​corresponds to one set of β offset values ​​from the second set of β offset values ​​based on multiplexing the second UCI on the second RE.

21. The method according to claim 20, in: Each respective set of beta offset values ​​in the first set of beta offset values ​​and the second set of beta offset values ​​is associated with a different code point; and The set of beta offset values ​​corresponds to code points indicated via the DCI.

22. The method according to claim 17, in: Each beta offset value set in the plurality of beta offset value sets comprises a plurality of beta offset values; and Each beta offset value of the plurality of beta offset values ​​corresponds to one or both of a UCI type or a payload.

23. The method of claim 17, wherein the signaling is RRC signaling.

24. An apparatus for wireless communication at a user equipment (UE), include: processor; and a memory coupled to the processor and storing instructions that, when executed by the processor, are operable to cause the apparatus to: receiving signaling from a network node indicating a plurality of sets of beta offset values ​​associated with two transport blocks (TBs); receiving, from the network node, a downlink control information (DCI) or a radio resource control (RRC) message scheduling a physical uplink shared channel (PUSCH) associated with two TBs; as well as Based on receiving the DCI or the RRC message, first uplink control information (UCI) is sent via a certain number of first resource elements (REs) on the PUSCH associated with the first TB of the two TBs, the number of first REs being determined based on a β offset value from a β offset value set in the multiple β offset value sets, the β offset value set being selected based on whether a second UCI is multiplexed on a second RE within a second TB of the two TBs, the first RE corresponding to the second RE.

25. The apparatus of claim 24, wherein the signaling indicating the plurality of sets of beta offset values ​​is a semi-static indication.

26. The device according to claim 25, in: The plurality of sets of beta offset values ​​include a first set of beta offset values ​​and a second set of beta offset values; The set of beta offset values ​​corresponds to the first set of beta offset values ​​based on not multiplexing UCI on the second RE; and The set of beta offset values ​​corresponds to the second set of beta offset values ​​based on multiplexing the second UCI on the second RE.

27. The device according to claim 24, in: The plurality of beta offset value sets include a first set of beta offset value sets and a second set of beta offset value sets; The set of β offset values ​​corresponds to one set of β offset values ​​from the first set of β offset values ​​based on not multiplexing UCI on the second RE; and The set of β offset values ​​corresponds to one set of β offset values ​​from the second set of β offset values ​​based on multiplexing the second UCI on the second RE.

28. The device according to claim 27, in: Each respective set of beta offset values ​​in the first set of beta offset values ​​and the second set of beta offset values ​​is associated with a different code point; and The set of beta offset values ​​corresponds to code points indicated via the DCI.

29. The device according to claim 24, in: Each beta offset value set in the plurality of beta offset value sets comprises a plurality of beta offset values; and Each beta offset value of the plurality of beta offset values ​​corresponds to one or both of a UCI type or a payload.

30. The apparatus of claim 24, wherein the signaling is RRC signaling.

Images