Multi-user packets for user equipment assisted retransmission

Abstract

A method for wireless communication is presented. The method may be performed by a user equipment (UE) and includes: receiving a multi-user physical (MUP) downlink shared channel (PDSCH) communication (MUPC) including a plurality of payloads. The method also includes: transmitting an acknowledgement (ACK) in response to decoding the MUPC; the method further includes: receiving a message requesting a retransmission of at least one of the plurality of payloads. The method further includes: transmitting the at least one payload in response to the message.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and, more particularly, to techniques and apparatus for user equipment (UE) assisted retransmission of multi-user packets. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, 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 a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless communication network may include several base stations (BS) that can support communication of several user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. Downlinks (or forward links) refer to the communication link from a BS to a UE, while uplinks (or reverse links) refer to the communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, and the like.

[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 to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by 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 to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. Summary of the invention

[0005] According to one aspect of the present disclosure, a method for performing wireless communications by a user equipment (UE) includes: receiving a multi-user physical (MUP) downlink shared channel (PDSCH) communication (MUPC) including multiple payloads. The method also includes: transmitting an acknowledgement (ACK) in response to decoding the MUPC. The method also includes: receiving a message requesting retransmission of at least one of the plurality of payloads. The method further includes: transmitting the at least one payload in response to the message.

[0006] In another aspect of the present disclosure, a method for performing wireless communication by a base station (BS) includes: transmitting a MUPC including a plurality of payloads to a plurality of UEs. The method also includes: receiving a negative acknowledgement (NACK) from a first UE among the plurality of UEs in response to the MUPC. The method also includes: receiving an ACK from a second UE among the plurality of UEs in response to the MUPC. The method further includes: transmitting a first message to the second UE requesting the second UE to retransmit at least one of the plurality of payloads in response to receiving the NACK from the first UE and receiving the ACK from the second UE.

[0007] In another aspect of the present disclosure, a UE for wireless communication includes a memory and at least one processor operatively coupled to the memory. The memory and the processor(s) are configured to receive a MUPC including a plurality of payloads. The UE is configured to transmit an ACK in response to decoding the MUPC. The UE is further configured to receive a message requesting retransmission of at least one of the plurality of payloads. The UE is further configured to transmit the at least one payload in response to the message.

[0008] In another aspect of the present disclosure, a base station (BS) for wireless communication includes a memory and at least one processor operatively coupled to the memory. The memory and the processor(s) are configured to transmit a MUPC including a plurality of payloads to a plurality of UEs. The BS is configured to receive a NACK from a first UE among the plurality of UEs in response to the MUPC. The BS is also configured to receive an ACK from a second UE among the plurality of UEs in response to the MUPC. The BS is further configured to transmit a first message to the second UE requesting the second UE to retransmit at least one of the plurality of payloads in response to receiving the NACK from the first UE and receiving the ACK from the second UE.

[0009] In another aspect of the present disclosure, a UE includes: means for receiving a MUPC including a plurality of payloads. The UE also includes: means for transmitting an ACK in response to decoding the MUPC. The UE also includes: means for receiving a message requesting retransmission of at least one of the plurality of payloads. The UE further includes: means for transmitting the at least one payload in response to the message.

[0010] In another aspect of the present disclosure, a BS includes: means for transmitting a MUPC including a plurality of payloads to a plurality of UEs. The BS also includes: means for receiving a NACK from a first UE among the plurality of UEs in response to the MUPC. The BS also includes: means for receiving an ACK from a second UE among the plurality of UEs in response to the MUPC. The BS further includes: means for transmitting a first message to a second UE requesting the second UE to retransmit at least one of the plurality of payloads in response to receiving the NACK from the first UE and receiving the ACK from the second UE.

[0011] In another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon is disclosed. The program code is executed by a UE and includes: program code for receiving a MUPC including a plurality of payloads. The UE also includes: program code for transmitting an ACK in response to decoding the MUPC. The UE also includes: program code for receiving a message requesting retransmission of at least one of the plurality of payloads. The UE further includes: program code for transmitting the at least one payload in response to the message.

[0012] In another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon is disclosed. The program code is executed by a BS and includes: program code for transmitting a MUPC including a plurality of payloads to a plurality of UEs. The BS also includes: program code for receiving a NACK from a first UE among the plurality of UEs in response to the MUPC. The BS also includes: program code for receiving an ACK from a second UE among the plurality of UEs in response to the MUPC. The BS further includes: program code for transmitting a first message to a second UE requesting the second UE to retransmit at least one of the plurality of payloads in response to receiving a NACK from the first UE and receiving an ACK from the second UE.

[0013] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following detailed description better understood. 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 implementing the same purpose as 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 accompanying drawings is provided for the purpose of illustration and description and is not intended to define limitations on the claims. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0017] Figure 3 is a diagram illustrating an example of a multi-user grouping design for new radio according to various aspects of the present disclosure.

[0018] Figure 4A and 4B is a diagram illustrating an example of UE-assisted full multi-user packet physical downlink shared channel communication retransmissions in accordance with various aspects of the present disclosure.

[0019] Figure 5 is a diagram illustrating an example of UE-assisted partial multi-user packet physical downlink shared channel communication retransmissions in accordance with various aspects of the present disclosure.

[0020] Figure 6 is a flow chart illustrating an example process, eg, performed by a UE, according to various aspects of the present disclosure.

[0021] Figure 7 is a flow chart illustrating an example process, eg, performed by a base station, in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION

[0022] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. Specifically, these aspects are provided to make the present disclosure thorough and complete, and it will fully convey the scope of the present disclosure to those skilled in the art. Based on this teaching, it should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure, whether it is independently or in combination with any other aspect of the present disclosure. For example, any number of aspects described can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using supplements or other other structures, functionality, or structures and functionality as the various aspects of the present disclosure described. It should be understood that any aspect of the present disclosure disclosed can be implemented by one or more elements of the claims.

[0023] 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0024] It should be noted that while various aspects may be described using terminology generally associated with 5G and later generation 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.

[0025] In New Radio (NR), the performance of certain communication scenarios may be improved by using multi-user packets (MUPs), where data for multiple user equipments (UEs) may be multiplexed together in a single packet. For example, in scenarios where a small amount of data is communicated to multiple UEs (such as factory automation scenarios, industrial Internet of Things (IIoT) scenarios, broadcast or multicast scenarios, evolved Multimedia Broadcast Multicast Service (eMBMS) scenarios, single cell point-to-multipoint (SC-PTM) scenarios, etc.), performance may be improved by aggregating the data in a MUP rather than transmitting the data via multiple packets. For example, such aggregation or concatenation of data in a MUP may improve coding gain compared to transmission of multiple packets. Additionally or alternatively, downlink control overhead may be reduced because downlink information (DCI) may be transmitted for a MUP rather than for multiple packets for different UEs.

[0026] Various aspects of the present disclosure relate to UE-assisted retransmission of a MUP. According to some aspects, multiple UEs receive a MUP from a base station. Each UE may transmit an acknowledgement / negative acknowledgement (ACK / NACK) feedback in response to the received MUP. The base station may map the ACK / NACK feedback to the UEs. The base station may request one or more UEs associated with the ACK to retransmit at least a portion of the MUP. Various aspects of the present disclosure may save network resources and computing resources of the base station and / or the UE.

[0027] Figure 1 1 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 several 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, NR BS, B node, gNB, 5G B node (NB), access point, transmit receive point (TRP), and the like. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0028] 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., several kilometers in radius) 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 residence) 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,” “TRP,” “AP,” “B node,” “5G NB,” and “cell” may be used interchangeably.”

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

[0030] 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 send 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 in , a relay station 110d may communicate with a macro BS 110a and a 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.

[0031] 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 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 to 2 watts).

[0032] As an example, BSs 110 (shown as BSs 110a, BSs 110b, BSs 110c, and BSs 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) over other backhaul links (e.g., X2, etc.). UEs 120 (e.g., 120a, 120b, 120c) may communicate with core network 130 via communication links 135.

[0033] The core network 130 may be an evolved packet core (EPC), which may include at least one mobility 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 services.

[0034] 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 communication 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).

[0035] UEs 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. UEs may also be referred to as access terminals, terminals, mobile stations, subscriber units, stations, etc. A UE may 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, 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 vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0036] 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 having different network slices serve different applications or subscriptions, the UE 120 may improve its resource utilization in the wireless communication system 100 while also meeting the performance specifications of the individual applications of the UE 120. In some cases, the network slice used by the UE 120 may be determined by an AMF (AMF) associated with one or both of the base station 110 or the core network 130. Figure 1 In addition, the session management of the network slice can be performed by the session management function (SMF).

[0037] The BS 110 (e.g., BSs 110a, 110b, 110c, 110d) may include a MUP retransmission request module 138 for transmitting a message requesting MUP retransmission. For ease of explanation, only one BS 110a is shown as including the MUP retransmission request module 138. The MUP retransmission request module 138 may be a component of each BS 110. The MUP retransmission request module 138 may transmit a MUP physical downlink shared channel (PDSCH) communication (MUP-PDSCH) including a plurality of payloads to a plurality of UEs 120. The MUP retransmission request module 138 may receive a negative acknowledgement (NACK) from a first UE 120 among the plurality of UEs 120 in response to the MUP-PDSCH communication. The MUP retransmission request module 138 may also receive an acknowledgement (ACK) from a second UE 120 among the plurality of UEs 120 in response to the MUP-PDSCH communication. Additionally, the MUP retransmission request module 138 may transmit a first message to the second UE 120 requesting the second UE 120 to retransmit one or more payloads (eg, one or more payload portions) of the plurality of payloads in response to receiving a NACK from the first UE 120 and an ACK from the second UE 120.

[0038] UE 120 (e.g., UE 120a, 120b, 120c, 120d, 120e) may include a MUP retransmission module 140. For ease of explanation, only one UE 120d is shown as including the MUP retransmission module 140. The MUP retransmission module 140 may be a component of each UE 120. The MUP retransmission module 140 may be configured to receive a multi-user physical (MUP) downlink shared channel (PDSCH) communication including multiple payloads (e.g., multiple payload parts). The MUP retransmission module 140 may transmit an ACK in response to decoding the MUP-PDSCH communication. The MUP retransmission module 140 may receive a message requesting retransmission of at least one of the multiple payloads. In addition, the MUP retransmission module 140 may transmit (the payloads) in response to the message.

[0039] Some UEs may be considered as machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may 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 client equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120, such as a processor component, a memory component, and the like.

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

[0041] 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) protocol (e.g., which may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, etc.), mesh network, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110. For example, base station 110 may configure UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, media access control-control element (MAC-CE), or via system information (e.g., system information block (SIB)).

[0042] As indicated above, Figure 1 These are provided as examples only. Other examples may differ from those described herein. Figure 1 The content described.

[0043] Figure 2A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 One for each base station and one for each UE in the base station 110. 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.

[0044] 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 improves reliability of transmission. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., channel quality indicator (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., precoding) 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 respective output symbol stream (e.g., for OFDM, etc.) 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.

[0045] At UE 120, antennas 252a to 252r may receive downlink signals from 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. A 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. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a 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.

[0046] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from a controller / processor 280. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if 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, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide decoded data to the data sink 239 and provide 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.

[0047] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component(s) of the base station 110 may perform one or more techniques associated with MUP retransmission, as described in greater 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(s) may perform or direct e.g. Figure 6-7 The processes and / or operations of other processes as described. Memories 242 and 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.

[0048] In some aspects, UE 120 may include means for receiving a multi-user physical (MUP) downlink shared channel (PDSCH) communication (MUPC) including multiple payloads; transmitting an acknowledgement (ACK) in response to decoding the MUPC; receiving a message requesting retransmission of at least one of the multiple payloads; and transmitting the at least one payload in response to the message.

[0049] In some aspects, BS110 may include a device for the following operations: transmitting a MUPC including multiple payloads to multiple UEs; receiving a negative acknowledgement (NACK) from a first UE among the multiple UEs in response to the MUPC; receiving an ACK from a second UE among the multiple UEs in response to the MUPC; and transmitting a first message to the second UE requesting the second UE to retransmit at least one of the multiple payloads in response to receiving the NACK from the first UE and receiving an ACK from the second UE.

[0050] As indicated above, Figure 2 These are provided as examples only. Other examples may differ from those described herein. Figure 2 The content described.

[0051] In New Radio (NR), the performance of certain communication scenarios may be improved by using multi-user packets (MUPs), where data for multiple UEs 120 are multiplexed together in the payload of a single packet. For example, in scenarios where a small amount of data is communicated to multiple UEs 120 (such as factory automation scenarios, industrial Internet of Things (IIoT) scenarios, broadcast or multicast scenarios, evolved multimedia broadcast multicast service (eMBMS) scenarios, single cell point-to-multipoint (SC-PTM) scenarios, etc.), performance may be improved by aggregating the data in MUPs. Aggregation of data in MUPs may improve coding gain and / or reduce downlink control overhead.

[0052] Various aspects of the present disclosure relate to UE-assisted retransmission of MUPs. According to some aspects, multiple UEs 120 receive MUPs from a base station 110. Each UE 120 may transmit ACK / NACK feedback in response to the received MUP. The base station may map the ACK / NACK feedback to the UE 120. In addition, the base station 110 may request one or more UEs 120 associated with the ACK to retransmit at least a portion of the MUP. Various aspects of the present disclosure may save network resources and computing resources of the base station 110 and / or the UE 120.

[0053] Figure 3 3 is a diagram illustrating an example 300 of a MUP design for NR in accordance with various aspects of the present disclosure. In some cases, MUP is referred to as multi-user physical downlink shared channel (PDSCH) communication (MUPC). MUPC may also be referred to as MUP-PDSCH communication.

[0054] like Figure 3 As shown in , MUPC may include multiple subheaders. The multiple subheaders together form a MUPC header 305. The subheader may include a UE ID that identifies a specific UE 120, such as a cellular cell radio network temporary identifier (C-RNTI). Different subheaders may include different UE IDs that identify different UEs 120. For example, a first subheader (e.g., shown as subheader A) may identify a first UE 120 (e.g., shown as UE A), a second subheader (e.g., shown as subheader B) may identify a second UE 120 (e.g., shown as UE B), and a third subheader (e.g., shown as subheader C) may identify a third UE 120 (e.g., shown as UE C). Aspects of the present disclosure are not limited to MUPCs of three UEs. MUPC may aggregate data of any number of UEs (e.g., two or more UEs).

[0055] In addition, the MUPC may include a payload 310 aggregated from a plurality of payload parts (e.g., payload part a, payload part b, and payload part c) corresponding to a plurality of UEs 120 (e.g., UE A, UE B, and UE C). Each payload part may be referred to as a transport block (TB). Different payload parts may carry data intended for different UEs 120. In one example, a first UE 120 (e.g., UE A) may identify a subheader including a UE identifier of the first UE. The first UE 120 may then identify a payload part (e.g., payload part A) corresponding to the identified subheader. In addition, the first UE 120 may obtain data included in the identified payload part. In this way, data for a plurality of UEs 120 may be carried in a single MUPC.

[0056] In some aspects, such as Figure 3 As shown in , a subheader may include a length field indicating the length (e.g., size, number of bits, number of bytes, etc.) of the corresponding payload portion. Additionally or alternatively, a subheader may include a field indicating whether the subheader is the last subheader (shown as a "last SH indicator"). One or more of these fields may identify the end of the subheader and the beginning of the payload portion. UE 120 may identify the beginning of the payload portion intended for UE 120 based on the beginning of the payload portion and the sum of all lengths indicated in the subheaders that appear before the subheader identifying UE 120. UE 120 may use the length indicated in the subheader identifying UE 120 to identify the end of the payload portion intended for UE 120.

[0057] As further shown, the subheader may include an acknowledgment or negative acknowledgment (ACK / NACK) resource indicator (ARI). The ARI may (e.g., by itself or in combination with other information) identify a physical uplink control channel (PUCCH) resource in which the UE 120 identified in the subheader will transmit ACK / NACK feedback for the MUPC (e.g., a payload portion of the MUPC corresponding to the UE 120). The base station 110 may configure the ARI included in different subheaders to indicate different PUCCH resources so that different UEs 120 transmit ACK / NACK feedback for the MUPC in different PUCC resources (e.g., different time resources, different symbols, different time slots, different subframes, different frequency resources, different resource blocks, etc.). In this way, the base station 110 may map the ACK / NACK feedback to the UE 120 based on the PUCCH resource in which the ACK / NACK feedback is received.

[0058] In some aspects, the header 305 of the MUPC and the payload 310 of the MUPC may be included in the PDSCH payload. Additionally or alternatively, the header (e.g., all subheaders) of the MUPC may be included in the physical layer header (e.g., rather than the media access control (MAC) header), thereby allowing the header to be processed faster by the UE 120 and reducing latency. In some aspects, each of the subheaders may be the same size as each other. Additionally or alternatively, the header may be a fixed or preconfigured size across multiple MUPCs. Thus, the subheader may include one or more reserved bits (e.g., padding bits) to achieve such alignment and reduce complexity. Alternatively, different subheaders included in the header may have different sizes. Additionally or alternatively, different headers included in different MUPCs may have different sizes. In this way, the MUPC may be flexibly configured (e.g., depending on the number of UEs 120 to which the MUPC is intended).

[0059] As indicated by reference numeral 315, in some aspects, the MUPC may have a first format in which the subheaders are grouped contiguously at the beginning of the MUPC. Additionally or alternatively, if the MUPC is transmitted using multiple code blocks, the subheader may be included in the first code block of the MUPC (e.g., an initial code block or the first code block in time). In this way, the subheader may appear closer in time to a demodulation reference signal (DMRS), which may improve the reliability of reception of the subheader. In addition, reducing the time between the subheader and the DMRS may reduce the amount of data to be processed by the UE 120 because the UE 120 may process the subheader to determine whether there is a payload portion for the UE 120. As indicated by reference numeral 320, in some aspects, the MUPC may have a second format in which each subheader is located immediately before a corresponding payload portion corresponding to the subheader.

[0060] In some aspects, DCI ( Figure 3 120 ) may schedule and / or activate MUPC. The DCI may be transmitted on a downlink control channel, such as a physical downlink control channel (PDCCH). The DCI may include a group radio network temporary identifier (RNTI) assigned to a group of UEs 120. The UEs 120 included in the group may determine, based on the group RNTI, that the DCI includes information about the UEs 120. For example, the DCI may be descrambled based on the group RNTI. Thus, the DCI may include a group RNTI (e.g., a group-specific RNTI) for the group of UEs 120, and the MUPC subheader may include a UE-specific RNTI. Accordingly, each UE 120 configured with the group RNTI may decode the PDSCH (e.g., the header 305 and payload 310 of the MUPC). As described above, by parsing the header 305, the UE 120 may determine whether it is addressed and identify the corresponding payload portion (e.g., TB).

[0061] In some aspects, the DCI may include scheduling information and / or control information for the MUPC, which may indicate a PDSCH resource carrying the MUPC, a modulation and coding scheme (MCS) for the MUPC, etc. Additionally or alternatively, the MUPC may be pre-scheduled using semi-persistent scheduling (SPS) (e.g., where the scheduling information may be indicated in a radio resource control (RRC) message), and the UE 120 may activate and / or deactivate monitoring the MUPC based at least in part on the DCI. In some aspects, the DCI may be the same format, size, etc. as a unicast DCI, thereby reducing complexity.

[0062] In one configuration, a UE 120 configured to monitor the group RNTI may decode data for other UEs 120 in the MUPC while attempting to decode its own data. In some cases, a UE 120 may not be served by a particular MUPC. However, the UE 120 does not know whether it is served by a particular MUPC until the UE 120 decodes the header 305. In some aspects, the DCI piggyback design may separate the header 305 of the MUP-PDSCH from the payload. That is, the header 305 may be encoded separately from the payload 310. Radio resource control (RRC) signaling may configure the UE 120 to decode the payload 310.

[0063] Figure 4A 4 is a diagram illustrating an example 400 of a UE-assisted full MUPC retransmission according to various aspects of the present disclosure. Figure 4A As shown in , a first UE 120 (eg, shown as UE0), a second UE 120 (eg, shown as UE1) and a third UE 120 (eg, shown as UE2) may be configured as a mutual assistance group. Additionally, the first, second and third UEs 120 may be configured with a group RNTI.

[0064] In one example, in a first time period (T1), base station 110 (e.g., gNB) may be combined with Figure 3 The first DCI 402 for the MUPC 315 is transmitted in a similar manner as described. The first DCI 412 may correspond to the group RNTI, such that each UE 120 configured with the group RNTI may receive and decode the first DCI 422.

[0065] Each UE 120 configured with the group RNTI may determine or attempt to determine whether the subheader of the MUPC 315 includes the UE-ID of the UE 120. Additionally, each UE 120 configured with the group RNTI may attempt to identify or decode the payload portion corresponding to the subheader including the UE-ID. Such an attempt may succeed, or may fail, and the UE 120 may selectively transmit ACK / NACK feedback based on whether the attempt succeeded or failed.

[0066] exist Figure 4AIn the example of , the first, second, and third UEs 120 belong to the same group and are configured with the same group RNTI. In a second time period (T2), the base station 110 transmits the MUPC 315 to the first, second, and third UEs 120. Additionally, in the second time period (T2), the first, second, and third UEs 120 attempt to decode the MUPC 315 based on the first DCI 402. In the current example, the payload 310 of the MUPC 315 includes a first payload portion (e.g., shown as a TB to UE0), a second payload portion (e.g., shown as a TB to UE1), and a third payload portion (e.g., shown as a TB to UE2). Each payload portion of the payload 310 may correspond to a different UE 120 configured with a group RNTI. For example, the first payload portion (e.g., a TB to UE0) corresponds to the first UE (e.g., UE0).

[0067] As described above, during the second time period (T2), each UE 120 may receive and attempt to decode MUPC 315. As described, by parsing header 305, UE 120 may identify a portion of payload 310 designated for itself. Figure 4A In the example of FIG. 4 , the first UE 120 fails to decode or receive the MUPC 315. Therefore, the first UE 120 transmits a NACK 410 to the base station 110 in a third time period (T3). In addition, the second and third UEs 120 successfully receive and decode the MUPC 315. Therefore, each of the second UE 120 and the third UE 120 transmits an ACK 412 to the base station 110 (T3).

[0068] In one configuration, the UE 120 may identify a PUCCH resource for acknowledging receipt of the payload portion (e.g., ACK / NACK) based on a UE-specific ARI included in a subheader identifying the UE 120 in the MUPC 315. The PUCCH resource may also be identified based on a common ARI included in the first DCI 402. For example, the UE 120 may determine the PUCCH resource as a function of the common ARI and the UE-specific ARI.

[0069] In one configuration, during time period T3, each UE 120 transmits an ACK 412 if it has decoded the entire payload 310 (e.g., each payload portion) of the MUPC 315, rather than decoding only the payload portion designated for the UE 120. For example, to transmit the ACK 412, the second UE 120 may be designated to successfully decode the payload portion designated for the first UE 120 (e.g., TB for UE0), the payload portion designated for the second UE 120 (e.g., TB for UE1), and the payload portion designated for the third UE 120 (e.g., TB for UE2).

[0070] In another configuration, there may not be a payload portion specified for UE 120. In this configuration, header 305 may still include a subheader for UE 120. UE 120 may decode the subheader to determine that there is no payload portion specified for UE 120. In this configuration, UE 120 that does not have a specified payload portion may be referred to as an assist-only UE. Additionally, in this configuration, if the assist-only UE 120 has successfully decoded each payload portion of payload 310, then the assist-only UE 120 transmits ACK 412.

[0071] exist Figure 4A In the example of FIG. 1 , based on the NACK 410 received from the first UE 120, the base station 110 determines that the first UE failed to receive or decode the MUPC 315. Additionally, based on the ACKs 412 received from the second and third UEs 120, the base station 110 determines that the second and third UEs 120 successfully received and decoded the MUPC 315. Therefore, the second and third UEs 120 have successfully received and decoded the payload portion of the first UE 120.

[0072] In response to the ACK 412 from the second and third UEs 120 and the NACK 410 from the first UE 120, in a fourth time period (T4), the base station 110 transmits a message requesting retransmission of the MUPC 315 to the second and / or third UEs 120. In one configuration, the message is a second DCI 404 associated with the group RNTI. The second DCI 404 may include a field to trigger retransmission. The field may be an added field or a diverted field. Downlink channel communication (such as PDSCH) is not associated with the second DCI 404.

[0073] The retransmission may be a full retransmission, in which the entire MUPC 315 is retransmitted. Alternatively, the retransmission may be a partial retransmission, in which only a portion of the MUPC is retransmitted. The hybrid automatic repeat request (HARQ) process ID and NDI included in the second DCI 404 may indicate whether the retransmission is full or partial. That is, the HARQ process ID and NDI may identify one or more payload portions for the retransmission. In addition, the second DCI identifies one or more resources for the retransmission. In one configuration, a time domain resource assignment (TDRA) or a frequency domain resource assignment (FDRA) in the second DCI 404 may be used for the retransmission.

[0074] As mentioned above, in Figure 4A In the fourth time period (T4), the base station 110 transmits the second DCI 404 to the first, second and third UEs 120. As described, Figure 4A is an example of a complete retransmission. Therefore, the format of the second DCI 404 matches the format of the first DCI 402. For example, the HARQ process ID and NDI of the second DCI 404 match the HARQ process ID and NDI of the first DCI 402.

[0075] In one configuration, if the slot offset (K0) is greater than zero (eg, the PDSCH and PDCCH are in different slots), the UE 120 that successfully decoded the initial MUPC performs a retransmission in response to receiving the second DCI 404 .

[0076] exist Figure 4A In the example of , the second and / or third UE 120 receives the second DCI 404 and determines that both the HARQ process ID and the NDI of the second DCI 404 match the HARQ process ID and the NDI of the first DCI 402. As a result, the second UE and / or the third UE 120 determines that the second DCI 404 is an assisted retransmission grant for a full retransmission. Figure 4A In the example of , for the second and third UEs 120, K0 is greater than zero.

[0077] In response to receiving the second DCI 404, the second and / or third UE 120 may retransmit the MUPC 315 at a fifth time period (T5). The second and / or third UE 120 is not specified to change the MUPC 315 so that the first UE 120 may soft combine the retransmitted MUPC 315. However, this comes at a cost to the second and third UEs because both the second and third payload portions are retransmitted to each of the UEs 120. In this example, none of the UEs 120 in the group RNTI has a use for the second or third payload portion.

[0078] The second and / or third UE 120 may retransmit the MUPC 315 via the one or more resources indicated in the second DCI 404. In addition, the second and / or third UE 120 may re-encode the MUPC 315 and rate match the re-encoded MUPC 315 to the one or more indicated resources. The redundancy version identifier (RVID) used to retransmit the MUPC 315 matches the RVID of the first DCI 402.

[0079] As described, the second and third UEs 120 may each retransmit MUPC 315. In some examples, the second UE 120 may receive MUPC 315 retransmissions from the third UE 120, and vice versa. In such examples, the second and third UEs 120 refrain from transmitting ACK 412 or NACK 410 for MUPC 315 retransmissions.

[0080] The retransmissions from the second and / or third UE 120 may follow the PDSCH waveform in a system frame number (SFN) manner.

[0081] exist Figure 4A In the example of , in the fifth time period (T5), the first UE 120 receives the second DCI 404 and regards the second DCI 404 as a retransmission grant for itself. The first UE 120 may combine the retransmitted MUPC 315 with the initial MUPC 315 based on a log likelihood ratio (LLR) method. That is, the first UE 120 may apply soft combining to the retransmitted MUPC 315 and the initial MUPC 315. From the perspective of the first UE 120, the source of the MUPC 315 retransmission is transparent.

[0082] In one configuration, the first UE 120 transmits an ACK 412 or NACK 410 in response to the MUPC retransmission to the base station 110. The second DCI 404 may provide an uplink grant for transmitting the ACK 412 or NACK 410 at a sixth time period (T6). In some aspects, multiple MUPC 315 retransmissions may be performed by one or more UEs 120 that successfully decoded the initial transmission of the MUPC 315.

[0083] Figure 4A is an example of macro diversity. Figure 4A In addition or alternatively to the aspects described in , the second and / or third UE 120 may detect the NACK 410 transmitted by the first UE 120. The retransmission of the MUPC 315 may be triggered in response to detecting the NACK 410 transmitted by the first UE 120.

[0084] Figure 4B4 is a diagram illustrating another example 450 of UE-assisted full MUPC retransmission according to various aspects of the present disclosure. Figure 4B As shown in FIG. 1 , in time period T1, base station 110 may transmit first DCI 402 to first UE 120, second UE 120, and third UE 120, as shown in FIG. Figure 4A Additionally, as described in Figure 4A As described in , during time period T2, the base station 110 may transmit MUPC 315 to the first, second and third UEs 120.

[0085] exist Figure 4B In the example of FIG. 4 , in time period T3, the first and third UEs 120 transmit NACK 410 in response to MUPC 315 (e.g., initial MUPC 315 transmission). Additionally, in time period T3, the second UE 120 transmits ACK 412 in response to the initial MUPC 315 transmission. In response to the ACK 412 from the second UE 120 and the NACK 410 from the first UE 120 and the third UE 120, in time period T4, the BS 110 transmits a second DCI 404 to the first, second, and third UEs 120.

[0086] The second UE 120 identifies the second DCI 404 as a retransmission request and combines it with Figure 4A MUPC 315 is retransmitted in a similar manner as described above. Additionally, each of the first and third UEs 120 receives the second DCI 404 and regards the second DCI 404 as a retransmission grant to itself. In time period T5, the first and third UEs 120 transmit the second DCI 404 in conjunction with the first DCI 404. Figure 4A The MUPC 315 retransmission is received from the second UE 120 in a similar manner as described.

[0087] As described, the retransmission may be a partial retransmission (eg, a selective retransmission). Figure 5 is a diagram illustrating an example 500 of UE-assisted partial MUPC retransmission in accordance with various aspects of the present disclosure. Figure 5 As shown in FIG. 1 , in time period T1, base station 110 may be combined with Figure 4A The first DCI 402 is transmitted to the first UE 120, the second UE 120, and the third UE 120 in a similar manner as described above. Figure 4A In a similar manner as described, during time period T2, base station 110 may transmit MUPC 315 to first, second, and third UEs 120.

[0088] exist Figure 5In the example of FIG. 1 , during time period T3, the first UE 120 transmits NACK 510 in response to the initial MUPC 315 transmission. Additionally, during time period T3, the second and third UEs 120 transmit ACK 512 in response to the initial MUPC 315 transmission. In response to the ACK 512 from the second and third UEs 120 and the NACK 410 from the first UE 120, the BS 110 initiates a selective retransmission procedure.

[0089] exist Figure 5 In the example of , for the selective retransmission procedure, BS 110 identifies the one or more payload portions that are not received by one or more UEs 120. In this example, the first UE 120 does not receive the first payload portion (e.g., TB for UE0). In response, BS 110 transmits a message requesting the second and / or third UE 120 to retransmit only the portion of MUPC 315 corresponding to the first payload portion (e.g., the first payload portion and the corresponding subheader).

[0090] In one configuration, during time period T4, the BS transmits a second DCI 502 to the second and / or third UE 120 because the second and third UEs transmit ACK 510 in response to the initial MUPC 315. The second DCI 502 may be associated with the group RNTI of the first, second, and third UEs 120. The content of the second DCI associates the second DCI 502 with the initial transmission grant (e.g., the first DCI 402, as shown in FIG. 4 ). Figure 4A In other words, the content of the second DCI 502 identifies the second DCI 502 as a partial retransmission request. In one configuration, the HARQ process ID and NDI of the second DCI 502 identify a specific payload portion (e.g., a specific TB) for retransmission. Additionally or alternatively, a separate bit field of the second DCI 502 may identify a specific payload portion (e.g., a specific TB) for retransmission.

[0091] like Figure 5 As shown in FIG. 5 , in time period T5, the second and / or third UE 120 may retransmit the payload portion (e.g., the first payload portion) identified in the second DCI 502 via the resources identified in the third DCI 504. These resources may include RVID, modulation and coding scheme (MCS), etc. The partial retransmissions from the second and / or third UE 120 may follow the PDSCH waveform in a system frame number (SFN) manner.

[0092] In one configuration, such as Figure 5As shown in FIG, at time period T4, BS 110 transmits third DCI 504 to first UE 120 because first UE 110 transmits NACK 512 in response to initial MUPC 315 transmission. The NDI of third DCI 504 may be flipped or the HARQ process ID of third DCI 504 may be different from the HARQ process ID of first DCI 402. First UE 120 may view third DCI 504 as a grant for a new transmission, which is received based on information in third DCI 504.

[0093] exist Figure 5 In the example of , in time period T5, the first UE 120 receives retransmissions from the second and / or third UE 120. Since the second DCI 502 requests one or more specific payload parts, the first UE 120 may not perform soft combining on the retransmitted payload parts and the initial payload parts. From the perspective of the first UE 120, the source of the retransmitted payload parts is transparent. In time period T6, the first UE 120 may transmit an ACK 510 or a NACK 512 to the BS 110 in response to receiving the retransmitted payload parts.

[0094] As indicated above, Figure 3 , 4A , 4B and 5 are provided as examples. Other examples may differ from those regarding Figure 3 , 4A , 4B and 5 described.

[0095] Figure 6 6 is a diagram illustrating an example process 600 performed, for example, by a UE according to various aspects of the present disclosure. The example process 600 is performed by a UE (user equipment) such as Figure 1 ) or by one of the UEs 120 described in Figure 1 The process 600 may include:

[0096] Figure 6 is a diagram illustrating an example process 600 performed, for example, by a UE, in accordance with various aspects of the present disclosure. The example process 600 is an example of multi-user packets for user equipment assisted retransmission.

[0097] like Figure 6As shown in , in some aspects, process 600 may include: receiving a multi-user physical (MUP) downlink shared channel (PDSCH) communication (MUPC) including multiple payloads (block 602). For example, a UE (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, memory 282, etc.) may receive a multi-user physical (MUP) downlink shared channel (PDSCH) communication (MUPC).

[0098] like Figure 6 As shown in , in some aspects, process 600 may include transmitting an acknowledgment (ACK) in response to decoding the MUPC (block 604). For example, the UE (e.g., using antenna 252, MOD 254, TX MIMO processor 266, transmit processor 264, controller / processor 280, memory 282, etc.) may transmit an acknowledgment (ACK).

[0099] like Figure 6 As shown in , in some aspects, process 600 may include receiving a message requesting retransmission of at least one of the plurality of payloads (block 606). For example, the UE (e.g., using antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, memory 282, etc.) may receive the message requesting retransmission.

[0100] like Figure 6 As shown in , in some aspects, process 600 may include transmitting the at least one payload in response to the message (block 608). For example, the UE (e.g., using antenna 252, MOD 254, TX MIMO processor 266, transmit processor 264, controller / processor 280, memory 282, etc.) may transmit the at least one payload.

[0101] Figure 7 700 is a diagram illustrating an example process 700 performed, for example, by a BS, according to various aspects of the present disclosure. The example process 700 is performed by a BS, such as Figure 1 BS110 as described in Figure 1 An example of wireless communication performed by the MUP retransmission request module 138 described in the embodiment of the present invention. Process 700 includes

[0102] Figure 7 is a diagram illustrating an example process 700, performed, for example, by a base station, in accordance with various aspects of the present disclosure. The example process 700 is an example of multi-user packets for user equipment assisted retransmission.

[0103] like Figure 7As shown in FIG. 7 , in some aspects, process 700 may include transmitting a multi-user physical (MUP) downlink shared channel (PDSCH) communication (MUPC) including multiple payloads to multiple UEs (block 702). For example, a base station (e.g., using antenna 234, MOD 232, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.) may transmit a multi-user physical (MUP) downlink shared channel (PDSCH) communication (MUPC).

[0104] like Figure 7 As shown in , in some aspects, process 700 may include: receiving a negative acknowledgement (NACK) from a first UE of the plurality of UEs in response to the MUPC (block 704). For example, a base station (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, etc.) may receive a negative acknowledgement (NACK) from a first UE of the plurality of UEs in response to the MUPC.

[0105] like Figure 7 As shown in , in some aspects, process 700 may include: receiving an acknowledgment (ACK) from a second UE in the plurality of UEs in response to the MUPC (block 706). For example, a base station (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, etc.) may receive an acknowledgment (ACK) from a second UE in the plurality of UEs in response to the MUPC.

[0106] like Figure 7 As shown in , in some aspects, process 700 may include: in response to receiving a NACK from the first UE and receiving an ACK from the second UE, transmitting a first message to the second UE requesting the second UE to retransmit at least one of the plurality of payloads (block 708). For example, a base station (e.g., using antenna 234, MOD 232, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.) may transmit the first message requesting the second UE to retransmit at least one of the plurality of payloads.

[0107] 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 by practice of the various aspects.

[0108] As used herein, 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 with hardware, firmware, and / or a combination of hardware and software.

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

[0110] 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. Thus, the operation and behavior of these systems and / or methods are described without reference to specific software code - it is understood that software and hardware can be designed to implement these systems and / or methods based at least in part on the description herein.

[0111] Although specific feature combinations are described 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 not specifically described in the claims and / or not disclosed in the specification. Although each dependent claim listed below can be directly subordinate to only one claim, the disclosure of various aspects includes that each dependent claim is combined with each other claim in this group of claims. The phrase quoting "at least one of" a column of items refers to any combination of these items, including a single member. As an 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 (for example, aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other sorting of a, b and c).

[0112] The elements, actions or instructions used should not be interpreted as critical or necessary unless explicitly described as such. Moreover, as used, the articles "one" and "a" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items (e.g., related items, non-related items, combinations of related and non-related items, etc.), and can be used interchangeably with "one or more". In the case of intending to have only one item, the phrase "only one" or similar language is used. Moreover, as used herein, the terms "having", "containing", "including", etc. are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated.

Claims

1. A method for performing wireless communication by a user equipment (UE), comprising: receiving a multi-user physical (MUP) downlink shared channel (PDSCH) communication (MUPC) including multiple payloads; transmitting an acknowledgment (ACK) in response to decoding the MUPC; receiving a message requesting retransmission of at least one of the plurality of payloads, wherein the message includes group radio network temporary identifier (RNTI) downlink control information (DCI); transmitting the at least one payload in response to the message; and Resources for the retransmission are determined based on a time domain resource assignment (TDRA) or a frequency domain resource assignment (FDRA) in the group RNTIDCI.

2. The method of claim 1, wherein the group RNTIDCI includes a field for triggering the retransmission.

3. The method of claim 1, wherein the group RNTIDCI is not associated with a data channel.

4. The method of claim 1, further comprising: Whether to perform a full retransmission of the plurality of payloads or a partial retransmission of a subset of the plurality of payloads is determined based on a hybrid automatic repeat request (HARQ) process ID and a new data indicator (NDI) of the group RNTIDCI.

5. The method of claim 1, wherein: The MUPC further includes a plurality of subheaders corresponding to a plurality of UEs; Each of the plurality of subheaders includes a UE identifier for identifying a UE among the plurality of UEs and a length field for indicating a length of a corresponding payload among the plurality of payloads; and Each of the plurality of payloads corresponds to a different UE among the plurality of UEs.

6. The method of claim 1, further comprising: The multiple retransmissions of the at least one payload are performed in response to receiving a plurality of messages requesting the retransmissions.

7. The method of claim 1, further comprising: receiving retransmissions of the plurality of payloads; as well as Transmitting an ACK or negative acknowledgement is refrained from in response to receiving the retransmission.

8. A method for performing wireless communication by a base station (BS), comprising: transmitting multi-user physical (MUP) downlink shared channel (PDSCH) communications (MUPC) including multiple payloads to multiple UEs; receiving a negative acknowledgement (NACK) from a first UE of the plurality of UEs in response to the MUPC; receiving an acknowledgment (ACK) from a second UE of the plurality of UEs in response to the MUPC; as well as In response to receiving a NACK from the first UE and an ACK from the second UE, a first message is transmitted to the second UE requesting the second UE to retransmit at least one of the multiple payloads, wherein the first message includes group radio network temporary identifier (RNTI) downlink control information (DCI), and wherein the DCI uses a time domain resource assignment (TDRA) or a frequency domain resource assignment (FDRA) in the group RNTI DCI to identify resources for the retransmission.

9. The method of claim 8, further comprising: transmitting the first message to the first UE, the first message scheduling the first UE to receive a complete retransmission of the plurality of payloads, wherein: The first message requests the second UE to perform the complete retransmission including the plurality of payloads to each of the plurality of UEs, and The first message is transmitted to the first UE in response to receiving a NACK from the first UE.

10. The method of claim 8, wherein the first message schedules an uplink time slot for the first UE to transmit an ACK or a NACK for the retransmission.

11. The method of claim 8, further comprising: receiving an ACK from a third UE of the plurality of UEs in response to the MUPC; as well as The first message requesting the third UE to perform a complete retransmission is transmitted to the third UE in response to receiving an ACK from the third UE.

12. The method of claim 8, further comprising: receiving a NACK from a third UE of the plurality of UEs in response to the MUPC; The first message is transmitted in response to a NACK from the third UE, the first message scheduling the first UE to receive a full retransmission of the plurality of payloads.

13. The method of claim 8, further comprising: transmitting a second message to the first UE, the second message scheduling the first UE to receive a partial retransmission of a subset of the plurality of payloads, wherein: The first message requests the second UE to perform the partial retransmission of the subset comprising the plurality of payloads, and The second message is transmitted to the second UE in response to receiving a NACK.

14. The method of claim 8, wherein: The MUPC further includes a plurality of subheaders corresponding to the plurality of UEs; Each of the plurality of subheaders includes a UE identifier for identifying a UE among the plurality of UEs and a length field for indicating a length of a corresponding payload among the plurality of payloads; and Each of the plurality of payloads corresponds to a different UE among the plurality of UEs.

15. The method of claim 8, wherein: The ACK indicates that the second UE decoded the plurality of payloads, and The NACK indicates that the first UE failed to decode at least one of the plurality of payloads.

16. The method of claim 8, wherein the group RNTIDCI includes a field for triggering the retransmission.

17. A user equipment (UE) for wireless communication, comprising: Memory, and at least one processor operatively coupled to the memory, the memory and the at least one processor being configured to: receiving a multi-user physical (MUP) downlink shared channel (PDSCH) communication (MUPC) including multiple payloads; transmitting an acknowledgment (ACK) in response to decoding the MUPC; receiving a message requesting retransmission of at least one of the plurality of payloads, wherein the message includes group radio network temporary identifier (RNTI) downlink control information (DCI); transmitting the at least one payload in response to the message; and Resources for the retransmission are determined based on a time domain resource assignment (TDRA) or a frequency domain resource assignment (FDRA) in the group RNTIDCI.

18. The UE of claim 17, wherein the group RNTIDCI includes a field for triggering the retransmission.

19. The UE of claim 17, wherein the group RNTIDCI is not associated with a data channel.

20. The UE of claim 17, wherein the at least one processor is further configured to determine whether to perform a full retransmission of the multiple payloads or a partial retransmission of a subset of the multiple payloads based on a hybrid automatic repeat request (HARQ) process ID and a new data indicator (NDI) of the group RNTIDCI.

21. The UE of claim 17, wherein: The MUPC further includes a plurality of subheaders further configured to correspond to a plurality of UEs; Each of the plurality of subheaders comprises a UE identifier further configured to identify a UE of the plurality of UEs and a length field to indicate a length corresponding to a payload of the plurality of payloads; and Each payload of the plurality of payloads is further configured to correspond to a different UE of the plurality of UEs.

22. The UE of claim 17, wherein the at least one processor is further configured to perform multiple retransmissions of the at least one payload in response to receiving a plurality of messages further configured to request the retransmissions.

23. The UE of claim 17, wherein the at least one processor is further configured to: receiving retransmissions of the plurality of payloads; and Transmitting an ACK or negative acknowledgement is refrained from in response to receiving the retransmission.

24. A base station (BS) for wireless communication, comprising: Memory, and at least one processor operatively coupled to the memory, the memory and the at least one processor being configured to: transmitting multi-user physical (MUP) downlink shared channel (PDSCH) communications (MUPC) including multiple payloads to multiple UEs; receiving a negative acknowledgement (NACK) from a first UE of the plurality of UEs in response to the MUPC; receiving an acknowledgment (ACK) from a second UE of the plurality of UEs in response to the MUPC; as well as In response to receiving a NACK from the first UE and an ACK from the second UE, a first message is transmitted to the second UE requesting the second UE to retransmit at least one of the multiple payloads, wherein the first message includes group radio network temporary identifier (RNTI) downlink control information (DCI), and wherein the DCI uses a time domain resource assignment (TDRA) or a frequency domain resource assignment (FDRA) in the group RNTI DCI to identify resources for the retransmission.

25. The base station of claim 24, wherein the at least one processor is further configured to transmit the first message to the first UE, the first message being further configured to schedule the first UE to receive full retransmissions of the plurality of payloads, wherein: The first message requests the second UE to perform the complete retransmission including the plurality of payloads to each of the plurality of UEs, and The first message is transmitted to the first UE in response to receiving a NACK from the first UE.

26. The base station of claim 24, wherein the first message schedules an uplink time slot for the first UE to transmit an ACK or a NACK for the retransmission.

27. The base station of claim 24, wherein the at least one processor is further configured to: receiving an ACK from a third UE of the plurality of UEs in response to the MUPC; and The first message requesting the third UE to perform a complete retransmission is transmitted to the third UE in response to receiving an ACK from the third UE.

28. The base station of claim 24, wherein the at least one processor is further configured to: receiving a NACK from a third UE of the plurality of UEs in response to the MUPC; The first message is transmitted in response to a NACK from the third UE, the first message scheduling the first UE to receive a full retransmission of the plurality of payloads.

29. The base station of claim 24, wherein the at least one processor is further configured to transmit a second message to the first UE, the second message further configured to schedule the first UE to receive a partial retransmission of a subset of the plurality of payloads, wherein: The first message requests the second UE to perform a partial retransmission of the subset including the plurality of payloads, and The second message is transmitted to the second UE, wherein the response is further configured to receive a NACK.

30. The base station of claim 24, wherein: The MUPC further includes a plurality of subheaders further configured to correspond to the plurality of UEs; Each subheader of the plurality of subheaders comprises a UE identifier further configured to identify a UE of the plurality of UEs and a length field configured to indicate a length of a corresponding payload of the plurality of payloads; and Each of the plurality of payloads is configured to correspond to a different UE among the plurality of UEs.

31. The base station of claim 24, wherein: The ACK indicates that the second UE decoded the plurality of payloads, and The NACK indicates that the first UE failed to decode at least one of the plurality of payloads.

32. The base station of claim 24, wherein the group RNTIDCI includes a field for triggering the retransmission.

Images