User equipment aggregation for downlink communications

Abstract

The present application relates to devices and components, including apparatus, systems, and methods for UE aggregation for downlink communications in a wireless network.

Description

BACKGROUND

[0001] The Third Generation Partnership Project (3GPP) Technical Specifications (TSs) define standards for New Radio (NR) wireless networks. These TSs describe aspects related to user plane and control plane signaling over the network. BRIEF DESCRIPTION OF DRAWINGS

[0002] Figure 1 A network environment is shown in accordance with some embodiments.

[0003] Figure 2 A message flow is shown in accordance with some embodiments.

[0004] Figure 3 A signaling diagram is shown in accordance with some embodiments.

[0005] Figure 4 Another signaling diagram is shown in accordance with some embodiments.

[0006] Figure 5 An operational flow / algorithmic structure is shown in accordance with some embodiments.

[0007] Figure 6 Another operational flow / algorithmic structure is shown in accordance with some embodiments.

[0008] Figure 7 Another operational flow / algorithmic structure is shown in accordance with some embodiments.

[0009] Figure 8 User equipment is shown in accordance with some embodiments.

[0010] Figure 9 A base station is shown in accordance with some embodiments. DETAILED DESCRIPTION

[0011] The following detailed description relates to the drawings. Like reference numerals can be used to identify like elements throughout the several figures. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, and techniques, in order to provide a thorough understanding of the various aspects of various implementations. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of various implementations can be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods can be omitted so as not to obscure the description of various implementations. For purposes of this document, the phrases “A and / or B” and “A or B” mean (A), (B), or (A and B).

[0012] The following is a glossary of terms that can be used in the present disclosure.

[0013] As used herein, the term“circuitry” refers to all of the hardware parts or includes hardware parts configured to provide the described functionality. The hardware parts can include electronic circuits, logic circuits, a processor (shared, dedicated, or group), or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (for example, a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable system-on-a-chip (SoC)), or a digital signal processor (DSP). In some embodiments, the circuitry can execute one or more software or firmware programs to provide at least some of the described functionality. The term“circuitry” can also refer to a combination of one or more hardware elements with the program code used to carry out the functionality of the program code, or a combination of circuitry used in electrical or electronic systems. In these embodiments, the combination of hardware elements and program code can be referred to as a particular type of circuitry.

[0014] As used herein, the term“processor circuitry” refers to, is part of, or includes circuitry capable of sequentially and automatically processing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term“processor circuitry” can refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes.

[0015] As used herein, the term“interface circuitry” refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term“interface circuitry” can refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, and a network interface card.

[0016] As used herein, the term“user equipment” or“UE” refers to a device with radio communication capabilities that can allow a user to access network resources in a communication network. The term“user equipment” or“UE” can be considered synonymous, and can be referred to as a client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Moreover, the term“user equipment” or“UE” can include any type of wireless / wired device or any computing device including a wireless communication interface.

[0017] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" can refer to various components of a computer that are communicatively coupled to each other. Further, the term "computer system" or "system" can refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or networking resources.

[0018] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database, and application or unit of work. A "hardware resource" can refer to a computing, storage, or network resource provided by a physical hardware element. A "virtualized resource" can refer to a computing, storage, or network resource provided by a virtualization infrastructure to an application, device, or system. The term "network resource" or "communication resource" can refer to a resource that is accessible by a computer device / system via a communication network. The term "system resource" can refer to any kind of shared entity that provides a service, and can include a computing resource or a network resource. A system resource can be viewed as a set of coherent functions, network data objects, or services that are accessible through a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0019] As used herein, the term "channel" refers to any tangible or intangible transmission medium that is used to convey data or data streams. The term "channel" can be synonymous with or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier wave," "radio frequency carrier wave," or any other similar term denoting a pathway or medium through which data is conveyed. Additionally, as used herein, the term "link" refers to a connection between two devices for transmitting and receiving information.

[0020] As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object, which can occur, for example, during execution of program code.

[0021] The term "connect" can mean that two or more elements have an established signaling relationship with each other over a communication channel, link, interface, or reference point at a common communication protocol layer.

[0022] As used herein, the term “network element” refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term “network element” can be considered synonymous with or otherwise be referred to as a networked computer, networked hardware, network equipment, network node, or virtualized network function.

[0023] The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual content of an information element, or a data element containing content. An information element can include one or more additional information elements.

[0024] Figure 1 A network environment 100 is shown in accordance with some embodiments. The network environment 100 can include user equipment (UE) 104 and 106 and base stations 108 of a radio access network (RAN). The base stations 108 can be next generation NodeBs (gNBs) to provide one or more 5G New Radio (NR) cells to provide NR user plane and control plane protocol terminations toward the UEs 104 / 106.

[0025] The UEs 104 / 106 can be an aggregated group that cooperate to improve uplink or downlink communications. For example, the UEs 104 / 106 can operate as a virtual UE that includes more platform resources than the UEs 104 / 106 operating individually. As such, UE aggregation can provide more transmission power, antenna / RF chains, antenna diversity, etc.

[0026] An aggregated UE can include a target UE and one or more assisting UEs. Uplink / downlink communications performed by the assisting UEs can be for the benefit of the target UE, which is the source or destination of the communicated information. For the embodiments described herein, the UE 104 can be considered the target UE and the UE 106 can be considered the assisting UE. However, these roles can be dynamic and can change over time. The target UE 104 and the assisting UE 106 can belong to the same user or can belong to different users. The target UE 104 is generally shown as a mobile phone and the assisting UE 106 is generally shown as a smart watch. These depictions are non-limiting. In other embodiments, other types of UEs can be used as target / assisting UEs.

[0027] The UEs 104 / 106 and the base stations 108 can communicate over the air interface using the OFDM / OFDMA technologies or some other technologies as defined by 3GPP TSs, such as those that define the Fifth Generation (5G) NR system standards. In some embodiments, the target UE 104 can communicate with the base station 108 over a Uu interface and can also communicate with the assisting UE 106 over a sidelink (SL) interface. The sidelink interface can be any type of wired or wireless interface. For example, the sidelink interface can be an interface of a wireless personal area network technology, a wireless local area network technology, or a wireless wide area network technology.

[0028] In some embodiments, the assisting UE 106 can be camped on a cell provided by the base station 108. In these embodiments, the assisting UE 106 can also communicate with the base station 108 over a Uu interface. In other embodiments, the assisting UE 106 can not be camped on a cell provided by the base station 108 and can therefore be hidden with respect to the base station 108. In these embodiments, the assisting UE 106 can not be able to communicate with the base station 108 over an established Uu interface, but can still be configured to receive information from or transmit information to the base station 108, as will be described.

[0029] Figure 2 A message flow 200 is shown in accordance with some embodiments. The message flow 200 can be performed in the case where the assisting UE is hidden with respect to the base station 108. However, similar concepts can also be used in the case where the assisting UE is camped on a cell provided by the base station 108.

[0030] The target UE 104 can identify one or more assisting UEs, including the assisting UE 106, with which it forms a UE aggregation. The target UE 104 can use various criteria to identify the assisting UEs. The criteria can include UEs belonging to a common user. The criteria can additionally / alternatively include UEs that are within a predetermined range from the target UE 104 or have a predetermined sidelink quality with the target UE 104. The criteria can additionally / alternatively include UEs that have declared their ability to assist. The declaration can be through a physical sidelink shared channel (PSSCH) transmission, a sidelink synchronization signal block (S-SSB) transmission, etc. The criteria can additionally / alternatively include UEs that are relatively stationary with respect to the target UE 104. For example, the target UE 104 can select them as assisting UEs only if the UEs are expected to be within a predetermined proximity for a predetermined period of time. Thus, it can be desirable for the assisting UEs to have a relatively low mobility with respect to the target UE 104. The criteria can additionally / alternatively include UEs that have sufficient processing capability. The processing capability can be, for example, a transmission power, an uplink / downlink processing power, a predetermined number of transmit antennas or receive antennas, etc. In some embodiments, the target UE 104 can not select assisting UEs that have a lower processing capability than the target UE 104 itself. However, in some embodiments, assisting UEs that have a lower processing capability than the target UE 104 can still be selected by the target UE 104 and be able to contribute by, for example, improving spatial receive diversity.

[0031] At 204, the target UE 104 can transmit configuration information to the assisting UE 106. The configuration information can be information sufficient to enable the assisting UE 106 to decode downlink communications (e.g., downlink control information (DCI), physical downlink shared channel (PDSCH) transmissions, etc.) from the base station 108 to the target UE 104. The configuration information can include a radio network temporary identity (RNTI), an indication of a configured / activated bandwidth part (BWP) on which the target UE 104 is operating, a physical downlink control channel (PDCCH) configuration, a PDSCH configuration, an expected time to receive the downlink communications from the base station 108, etc.

[0032] The PDCCH configuration can include control resource and search space information sufficient to allow the assisting UE to identify and correctly decode PDCCH transmissions. The PDSCH configuration can include demodulation reference signal (DMRS) information (e.g., a number of DMRS symbols in a slot, a DMRS format, etc.) and other information that allows the assisting UE 106 to identify and correctly decode PDSCH transmissions.

[0033] In some embodiments, the expected time of receiving a downlink communication from the base station 108 can be the time at which the target UE 104 expects to receive the downlink communication. In cases where the target UE 104 and the assisting UE 106 are in close proximity, the assisting UE 106 can use the same expected reception time as the target UE 104. When the target UE 104 and the assisting UE 106 are communicating over a relatively large distance, the assisting UE 106 can use the expected timing at which the target UE 104 is to receive the downlink communication and the relative positioning information of the target UE 104 and the assisting UE 106 to determine the time at which the assisting UE 106 is expected to receive the downlink communication.

[0034] At 208, the target UE 104 can transmit a trigger request message to the base station 108 to request activation of the aggregation mode. In some embodiments, the trigger request message can be an uplink control information (UCI) transmitted in a physical uplink control channel (PUCCH) transmission, an extended hybrid automatic repeat request (HARQ)-acknowledgement (ACK) transmission, a special scheduling request (SR), or a special physical random access channel (PRACH) transmission.

[0035] In some embodiments, the trigger request can be transmitted in response to the target UE 104 not successfully decoding an initial PDSCH transmission from the base station 108. In some embodiments, rather than sending a one-bit HARQ-ACK to indicate that the PDSCH transmission was not successfully received, the target UE 104 can send a two-bit HARQ-ACK, where the first bit corresponds to the acknowledgement / negative-acknowledgement bit of a typical HARQ-ACK transmission and the second bit indicates whether the target UE 104 requests to enter the aggregation mode.

[0036] In some embodiments, the trigger request message can only include an indication of a request to enter (or exit) the aggregation mode. In other embodiments, the trigger request message can additionally / alternatively include a desired time to process all PDSCH transmissions, including those received directly from the base station 108 and those received from the assisting UE. In other embodiments, the trigger request message can additionally / alternatively include a HARQ-ACK for the PDSCH transmission (as described above).

[0037] In some embodiments, the trigger request message can additionally / alternatively include information that facilitates retransmission of the PDSCH to facilitate reception of the PDSCH transmission by both the target UE 104 and the assisting UE 106. For example, the target UE 104 can provide a transmission configuration indication identity (TCI) to the base station 108 to configure a downlink transmission with desired characteristics.

[0038] At 212, the base station 108 can transmit the scheduling DCI and the scheduled PDSCH. The DCI / PDSCH can be transmitted to the target UE 104, but also intended to be received by the assisting UE 106. For example, the base station 108 can transmit the DCI / PDSCH based on the TCI provided by the target UE 104. In another example, the base station 108 can transmit the DCI / PDSCH with a spatial beam that is wider than the spatial beam used for the initial transmission. The wider spatial beam can facilitate reception by both the target UE 104 and the assisting UE 106. In another example, the base station 108 can transmit multiple DCI / PDSCHs, where each DCI / PDSCH is intended for a different UE in the aggregated UE. These DCI / PDSCHs can be transmitted with different spatial beams or a common spatial beam. The multiple PDSCH transmission can include the same transport block directed to the target UE 104.

[0039] At 216, the target UE 104 can transmit a forwarding request message to the assisting UE 106. The forwarding request message can request the assisting UE 106 to transmit (retransmit) any transport block that the assisting UE 106 is able to decode correctly.

[0040] In some embodiments, the forwarding request message can be a message transmitted on the sidelink (e.g., a PSCCH transmission). In other embodiments, if the assisting UE 106 is able to decode the PUCCH from the target UE 104, the forwarding request message can be a NACK transmission on the PUCCH. For example, the trigger request transmitted at 208 can be used to indicate that the target UE 104 did not successfully receive the initial PDSCH transmission and request the assisting UE 106 to transmit (retransmit) the transport block that was decoded successfully.

[0041] At 220, the assisting UE 106 can forward the transport block to the UE. This can be based on the forwarding request message. The transport block can be forwarded on a preconfigured sidelink resource or the same resource indicated by the base station 108 for the initial transmission. The assisting UE 106 can transmit the transport block in the form of a Uu transmission (e.g., PUSCH) or a sidelink transmission (e.g., PSSCH). For example, the transport block can be transmitted to the target UE 104 on an uplink symbol. Various embodiments can consider modulation and coding scheme (MCS) and interference management aspects in the forwarding of the transport block.

[0042] In some embodiments, the assisting UE 106 can automatically retransmit the transport block to the target UE 104, as opposed to having a specific request to retransmit the transport block (at 216 or 208). For example, after receiving the configuration information at 204, the assisting UE 106 can begin forwarding the successfully decoded transport block to the target UE 104 based on a preconfigured timeline after decoding the PDSCH transmission. The target UE 104 can forward the successfully decoded transport block on the preconfigured time / frequency resources.

[0043] At 224, the UE 104 can HARQ-ACK based on the retransmitted PDSCH transmission. In the case that the UE 104 does not successfully decode the retransmitted PDSCH as received directly from the base station 108, it can defer transmission of the HARQ-ACK until it has received and processed the transport block from the assisting UE 106.

[0044] Figure 3 A signaling diagram 300 is shown in accordance with some embodiments.

[0045] The signaling diagram 300 shows a PDCCH 304 that can be received by the target UE 104. The PDCCH 304 can schedule a PDSCH 308 to be received by the target UE 104. In some embodiments, the target UE 104 can be operating in an aggregated mode and can not successfully receive the PDSCH 308 directly from the base station 108. Accordingly, the target UE 104 can communicate with the aggregating UE at 312 to receive the transmitted (retransmitted) PDSCH.

[0046] The PDCCH 304 can be associated with a PUCCH 316 designated for transmitting a HARQ-ACK corresponding to the reception of the PDSCH 308. For example, the PDCCH 304 can indicate the time of the PUCCH 316 by providing a K1 value. However, if at the indicated time, the target UE 104 is still communicating with the aggregating UE at 312 to attempt to properly receive the PDSCH, the target UE 104 can not yet be ready to transmit the HARQ-ACK in the PUCCH 316. Accordingly, various embodiments describe procedures that can defer the transmission of the HARQ-ACK.

[0047] In a first option, the target UE 104 can transmit a special NACK (e.g., 00, instead of 0) on the PUCCH resource 316 to indicate that the target UE 104 is not ready to send the real HARQ-ACK information. A second PUCCH resource (PUCCH 320) offset by Toffset from the PUCCH 316 can then be triggered. The value of Toffset can be pre-configured or dynamically configured by the network and can be known to the target UE 104. If the target UE 104 is still not ready to send the real HARQ-ACK information in the PUCCH 320, it can again send a special NACK, and the deferral procedure can repeat.

[0048] In a second option, the target UE 104 can transmit a special NACK on the PUCCH 316 to indicate a desired offset to the PUCCH 320. In some embodiments, the special NACK can provide an indication of the likelihood of one or more pre-configured offsets to be used.

[0049] As noted above, in some of the embodiments, both the target UE 104 and the assisting UE 106 can be pre-camped on a cell provided by the base station 108. In these embodiments, the base station can provide a more active role in establishing UE aggregation and communicating with the assisting UE. For example, the assisting UE can be selected by the target UE 104, as described above. However, the target UE 104 can then transmit a suggestion to the base station 108 of the UEs to include as assisting UEs. In other embodiments, the base station 108 can select the UEs to include as assisting UEs. This can allow UEs that are not already involved in the established communication with each other to participate in UE aggregation.

[0050] For downlink transmissions, the base station 108 can multicast a transport block to the aggregated UEs (e.g., the target UE 104 and the assisting UE 106). This can be accomplished in a variety of ways.

[0051] In some embodiments, the aggregated UEs can have a common identity. For example, the aggregated UEs can all be associated with a group RNTI (G-RNTI). The base station 108 can then transmit a DCI with cyclic redundancy check (CRC) bits scrambled with the G-RNTI. The aggregated UEs can decode the DCI to determine that they are involved in the aggregation and can identify the PDSCH transmission scheduled by the DCI.

[0052] In some embodiments, information about the aggregated UEs can be signaled with a group common DCI (GC-DCI). For example, the GC-DCI can include a list of UE identities corresponding to the aggregated UEs, the first UE identity in the list of identities can identify the target UE 104 to which the PDSCH scheduled by the GC-DCI is to be transmitted. The remaining identities in the list can correspond to the helper UEs. Thus, by receiving the GC-DCI, each of the aggregated UEs will be aware of the destination of the transport block and the role the UE is to play in the aggregation (e.g., as a helper or target).

[0053] In some embodiments, the PUCCH resources for HARQ-ACK from each of the aggregated UEs can be RRC mapped to the aggregated UEs. The mapping can be relative to the ordering of the list of identities in the GC-DCI. For example, the UEs can receive RRC configuration information that maps the target UE to a first PUCCH resource, the first helper UE to a second PUCCH resource, the second helper UE to a third PUCCH resource, and so on. When the UEs receive the GC-DCI that schedules the PDSCH transmission, the receiving UEs can be aware of which PUCCH resource to use for HARQ-ACK feedback based on their position in the list of identities. Upon receiving the HARQ-ACK feedback, the base station 108 can be aware of which UEs successfully received the PDSCH transmission based on the PUCCH resources used to transmit the HARQ-ACK feedback.

[0054] In some embodiments, the DCI can only indicate one PUCCH resource that can be used by the helper UEs to transmit HARQ-ACK.

[0055] In some embodiments, different DCIs / PDSCHs (including the same transport block) can be transmitted to different aggregated UEs. This option can be associated with a relatively high overhead, but can also provide some additional flexibility / reliability.

[0056] Figure 4 A signaling diagram 400 is shown in accordance with some embodiments. The signaling diagram 400 can be used in embodiments in which the helper UEs 106 are camped on a cell provided by the base station 108.

[0057] After establishing the UE aggregation and activating the aggregation mode, the base station 108 can transmit a DCI / PDSCH 404 to both the target UE 104 and the assisting UE 106. If the target UE 104 does not successfully receive the PDSCH transmission, it can transmit a NACK at 408. Upon receiving the NACK (or not receiving the expected ACK), the base station 108 can then transmit a retransmission request 412 to the assisting UE 106. The retransmission request 412 can include a specific HARQ-ID associated with the transport block to be forwarded to the target UE 104. The assisting UE 106 can then transmit (retransmit) the transport block (received from the PDSCH transmitted at 404) to the target UE 104 at 416.

[0058] In some embodiments, the base station 108 can schedule resources (in terms of time and frequency) that can be used by the assisting UE 106 to transmit (retransmit) the transport block to the target UE 104. This can be similar to a Mode 1 sidelink resource allocation.

[0059] In some embodiments, the base station 108 can include an indication of a timeline for the assisting UE 106 to transmit (retransmit) the transport block at 416 in the retransmission request 412. The frequency domain resources for transmitting (retransmitting) the transport block at 416 can be the same resources that the assisting UE 106 originally received the transport block in the PDSCH 404 on.

[0060] In some embodiments, the assisting UE 106 can transmit (retransmit) the transport block to the target UE 104 without further indication, similar to the discussion above Figure 2

[0061] Figure 5 An operational flow / algorithmic structure 500 is provided in accordance with some embodiments. The operational flow / algorithmic structure 500 can be performed / implemented by a UE, such as, for example, the target UE 104 or the UE 700, or a component thereof (e.g., the processor 704).

[0062] The operational flow / algorithmic structure 500 can include identifying an assisting UE at 504. The assisting UE can be identified as included in a UE aggregation group that includes the target UE. The aggregation group can be used to facilitate downlink communications to the target UE. In some embodiments, the assisting UE can be identified by a proximity to the target UE, a capability of the assisting UE, a signal connection with the assisting UE, a tenancy status of the UEs (e.g., both the assisting UE and the target UE correspond to the same user), and the like.

[0063] ​The operational flow / algorithm structure 500 may also include transmitting information to the assisting UE to enable reception of downlink communications at 508. The information may be configuration information, such as an RNTI, a portion of bandwidth configured for the target UE, a PDCCH / PDSCH configuration for the target UE, or a time at which the target UE expects to receive downlink communications.

[0064] In some embodiments, the target UE may also transmit information to the assisting UE to facilitate transmission of downlink communications from the assisting UE to the target UE. For example, the target UE may provide an indication of pre-configured resources (in terms of time and frequency) that the assisting UE may use to transmit information to the target UE.

[0065] The operational flow / algorithm structure 500 may also include receiving a downlink communication from the base station via the assisting UE at 512. In some embodiments, the receipt of the downlink communication from the assisting UE may be in response to transmitting a specific request to the assisting UE via a sidelink control channel or transmitting a negative acknowledgement to the base station in an uplink control channel.

[0066] Figure 6 An operational flow / algorithm structure 600 according to some embodiments is provided. The operational flow / algorithm structure 600 may be performed or implemented by a base station, such as base station 108 or base station 900, or a component thereof (eg, processor 904).

[0067] The operational flow / algorithm structure 600 may include receiving a request to enter aggregation mode at 604. In some embodiments, the request may be part of HARQ feedback from a target UE that did not successfully receive a PDSCH transmission. In other embodiments, the request may be part of a scheduling request, a PRACH transmission, or UCI.

[0068] The operational flow / algorithm structure 600 may also include, at 608, generating a downlink transmission to the target UE to be received by the target UE and the assisting UE. In some embodiments, the base station may use downlink parameters recommended for use by the target UE. In some embodiments, the downlink transmission may include DCI / PDSCH transmissions directed separately to the target UE and the assisting UE. The PDSCH transmission may include the same transport block to be sent to the target UE.

[0069] The operational flow / algorithm structure 600 may also include transmitting a downlink transmission at 612. In some embodiments, the base station may transmit the downlink transmission using a beam that is wider than the beam used in the non-aggregated mode. In other embodiments, the base station may use different beams for different aggregated UEs.

[0070] Figure 7An operational flow / algorithmic structure 700 is provided in accordance with some embodiments. The operational flow / algorithmic structure 700 can be performed / implemented by a UE, such as, for example, target UE 104, assisting UE 106, or UE 800, or a component thereof, such as, for example, processor 804.

[0071] The operational flow / algorithmic structure 700 can include, at 704, processing a scheduled PDSCH transmission and a DCI that includes a list of UE identities. The DCI can be a GC-DCI or a DCI with a CRC scrambled by a group RNTI. In some embodiments, the list of UE identities can be stored locally, and the DCI can only provide an index to the list.

[0072] The operational flow / algorithmic structure 700 can also include, at 708, determining a target UE based on the list. For example, the first identity in the list can correspond to the target UE. The remaining identities in the list can correspond to assisting UEs. The UE performing the operational flow / algorithmic structure 700 can determine where its identity is located in the list. Based on the location, the UE can determine its role and the identity of the target UE.

[0073] The operational flow / algorithmic structure 700 can also include, at 712, transmitting or receiving the PDSCH transmission to the UE.

[0074] In the case where the identity of the UE is the first in the list, the UE can determine that it is the target UE. It can attempt to receive the scheduled PDSCH transmission directly from the base station. If the reception is not successful, the target UE can receive the PDSCH transmission from one or more of the assisting UEs identified from the list. The assisting UEs can transmit the PDSCH as described elsewhere herein.

[0075] In the case where the identity of the UE is not the first in the list, the UE can determine that it is an assisting UE. It can attempt to receive the scheduled PDSCH transmission from the base station and automatically forward to the target UE or wait for an indication (from the base station or the target UE) to transmit the PDSCH transmission.

[0076] Figure 8 A UE 800 is shown in accordance with some embodiments. The UE 800 can be similar to, and substantially interchangeable with, target UE 104 or assisting UE 106.

[0077] The UE 800 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, or an actuator), a video surveillance / monitoring device (e.g., a camera or a video camera), a wearable device (e.g., a smart watch), or an Internet of Things device.

[0078] The UE 800 can include a processor 804, RF interface circuitry 808, memory / storage 812, user interface 816, sensors 820, drive circuitry 822, power management integrated circuit (PMIC) 824, antenna structure 826, and battery 828. The components of the UE 800 can be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic components, hardware, software, firmware, or a combination thereof. Figure 8 The block diagram of FIG. 8 is intended to show a high-level view of certain ones of the components of the UE 800. However, some of the components shown can be omitted in some implementations, additional components can be present, and different arrangements of the components shown can occur in other implementations.

[0079] The components of the UE 800 can be coupled through one or more interconnects 832, which can represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, or optical connection that allows the various circuit components (on common or different chips or chip sets) to interact.

[0080] The processor 804 can include processor circuitry, such as baseband processor circuitry (BB) 804A, central processor unit circuitry (CPU) 804B, and graphics processor unit circuitry (GPU) 804C. The processor 804 can include any type of circuit or processor circuitry that executes or otherwise operates computer executable instructions, such as program code, software modules, or functional processes from the memory / storage 812, to cause the UE 800 to perform operations as described herein.

[0081] In some embodiments, the baseband processor circuitry 804A can access a communication protocol stack 836 in the memory / storage 812 to communicate over a 3GPP-compatible network. Generally, the baseband processor circuitry 804A can access the communication protocol stack 836 to perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and NAS layer. In some embodiments, PHY layer operations can additionally / alternatively be performed by components of the RF interface circuitry 808.

[0082] The baseband processor circuitry 804A can generate or process baseband signals or waveforms carrying the information in a 3GPP-compatible network. In some embodiments, waveforms for NR can be based on Cyclic Prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Spread OFDM (DFT-S-OFDM) in the uplink.

[0083] The memory / storage 812 can include one or more non-transitory computer-readable media storing instructions (e.g., the communication protocol stack 836) executable by one or more of the processors 804 to cause the UE 800 to perform various operations described herein. The memory / storage 812 includes any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state memory devices, etc. In some embodiments, some of the memory / storage 812 can be on the processor 804 itself, such as load- store buffers, cache memory, and / or the like. In some embodiments, some of the memory / storage 812 can be external to the processor 804, such as one or more memory / storage devices on a motherboard of the UE 800.

[0084] The RF interface circuitry 808 can include transceiver circuitry and radio frequency front module(s) (RFEM(s)) that allow the UE 800 to communicate with other devices over a radio access network. The RF interface circuitry 808 can include various elements arranged in transmit or receive paths. These elements can include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0085] In the receive path, the RFEM can receive a radiated signal from the air interface via antenna structure 826 and proceed to filter and amplify the signal (with a low-noise amplifier). The signal can be provided to a receiver of the transceiver which down-converts the RF signal into a baseband signal that is provided to the baseband processor of the processor 804.

[0086] In the transmit path, a transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 826.

[0087] In various embodiments, the RF interface circuitry 808 can be configured to transmit / receive signals in a manner compatible with NR and sidelink access technologies.

[0088] Antenna 826 can include antenna elements to convert electrical signals into radio waves for transmission through the air and to convert received radio waves into electrical signals. The antenna elements can be arranged into one or more antenna panels. Antenna 826 can have an antenna panel that is omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input multiple-output communication. Antenna 826 can include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, or phased array antennas. Antenna 826 can have one or more panels designed for a particular frequency band, including bands in FR1 or FR2.

[0089] User interface circuitry 816 includes various input / output (I / O) devices that allow a user to interact with UE 800. User interface circuitry 816 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for entering information into the UE 800, including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphone, scanner, headset, and / or the like. Output device circuitry includes any physical or virtual means for displaying information, or for otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry can include any number or combination of audio or visual displays, including one or more simple visual outputs / indicators (e.g., binary status indicators (such as light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touchscreens (e.g., liquid crystal displays (LCD), LED displays, quantum dot displays, and projectors), the output of which is generated or produced by the operation of the UE 800.

[0090] The sensors 820 can include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information about the detected events (sensor data) to some other a device, module, or subsystem. Examples of such sensors include: an inertial measurement unit comprising an accelerometer, a gyroscope, or a magnetometer; a microelectromechanical system or nanoelectromechanical system comprising a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravimeter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; and a microphone or other similar audio capture device.

[0091] The drive circuits 822 can include software and hardware elements that are arranged to control particular devices that are embedded in, attached to, or otherwise coupled to the UE 800. The drive circuits 822 can include individual drivers to allow other components to interact with or control various input / output (I / O) devices that can be present within, or connected to, the UE 800. For example, the drive circuits 822 can include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, a sensor driver to fetch sensor readings of sensor circuitry 820 and control and allow access to the sensor circuitry 820, a driver to fetch actuator positions of electromechanical components or control and allow access to electromechanical components, a camera driver to control and allow access to an embedded image capture device, an audio driver to control and allow access to one or more audio devices.

[0092] The PMIC 824 can manage power for the various components of the UE 800. In particular, with respect to the processor 804, the PMIC 824 can control a power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

[0093] The battery 828 can power the UE 800, although in some examples the UE 800 can be deployed in a fixed location, and can have a power supply coupled to an electrical grid. The battery 828 can be a lithium ion battery; a metal-air battery, such as a zinc-air battery; an aluminum-air battery; a lithium-air battery; and the like. In some implementations, such as in vehicle-based applications, the battery 828 can be a typical lead-acid automotive battery.

[0094] Figure 9 A base station 900 is shown in accordance with some embodiments. The base station 900 can be similar to the base station 108, and substantially interchangeable therewith.

[0095] The base station 900 can include a processor 904, RF interface circuitry 908 (if implemented as a base station), core network (CN) interface circuitry 912, memory / storage circuitry 916, and antenna structure 926 (if implemented as a base station).

[0096] The components of the base station 900 can be coupled with various other components over one or more interconnects 928.

[0097] The processor 904, RF interface circuitry 908, memory / storage circuitry 916 (including communication protocol stack 910), antenna structure 926, and interconnects 928 can be similar to those described above in reference to Figure 8 Like-named components have been described above in reference to the

[0098] The CN interface circuitry 912 can provide connectivity to a core network (e.g., a 5thGeneration Core Network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols or some other suitable protocol). Network connectivity can be provided to / from the base station 900 via a fiber or wireless backhaul. The CN interface circuitry 912 can include one or more specialized processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 912 can include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0099] In some embodiments, the base station 900 can be coupled with a transmission-reception point (TRP) using the antenna structure 926, CN interface circuitry, or other interface circuitry.

[0100] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a way to minimize risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0101] For one or more embodiments, at least one of the components shown in one or more of the preceding figures can be configured to perform one or more operations, techniques, processes, or methods as described in the following example section. For example, the baseband circuitry described above in connection with one or more of the preceding figures can be configured to operate in accordance with one or more of the following examples. For another example, circuitry associated with a UE, base station, or network element described above in connection with one or more of the preceding figures can be configured to operate in accordance with one or more of the examples shown in the following example section.

[0102] Example

[0103] In the following section, additional example embodiments are provided.

[0104] Example 1 includes a method of operating a target user equipment (UE), the method comprising: identifying an assisting UE; transmitting information to the assisting UE to enable the assisting UE to receive a downlink communication from a base station to the target UE; and receiving the downlink communication from the base station via the assisting UE.

[0105] Example 2 includes the method of example 1 or some other example herein, wherein the information comprises: one or more radio network temporary identifiers (RNTIs), a bandwidth part configured for the target UE; a physical downlink control channel (PDCCH) configuration for the target UE; a PDSCH configuration for the target UE; or an expected time of receiving the downlink communication.

[0106] Example 3 includes the method of example 1 or some other example herein, wherein identifying the assisting UE comprises: determining that the assisting UE and the target UE are associated with a same user; determining that the assisting UE is within a predefined range from the target UE; determining that the assisting UE has provided an indication that it is capable of assisting; determining an expected proximity of the assisting UE to the target UE; or determining that the assisting UE has sufficient capability to assist.

[0107] Example 4 includes the method of example 1 or some other example herein, the method further comprising: transmitting a request to enter an aggregated mode to the base station, wherein the request is an uplink control information, an extended hybrid automatic repeat request acknowledgement (HARQ-ACK), a scheduling request, or a physical random access channel transmission.

[0108] Example 5 includes the method of example 4 or some other example herein, wherein transmitting the request comprises: transmitting an indication of a time needed to process a physical downlink shared channel transmission and provide an acknowledgement.

[0109] Example 6 includes the method of example 4 or some other example herein, wherein transmitting the request comprises: transmitting an indication of a transmission configuration indication identity requested for the downlink communication.

[0110] Example 7 includes the method of example 1 or some other example herein, the method further comprising: transmitting a request for the downlink communication to the assisting UE, wherein the request is transmitted as a sidelink control information on a physical sidelink control channel or as a negative acknowledgement information on a physical uplink control channel.

[0111] Example 8 includes the method of example 1 or some other example herein, the method further comprising: transmitting an indication to the assisting UE of a preconfigured resource to be used to transmit the downlink communication to the target UE.

[0112] Example 9 includes the method of Example 1 or some other example herein, wherein the downlink communication is a physical downlink shared channel (PDSCH) transmission, and the method further comprises: receiving a physical downlink control channel (PDCCH) transmission scheduling the PDSCH transmission; receiving, from the secondary UE, the PDSCH transmission; generating hybrid automatic repeat request (HARQ) acknowledgement (ACK) information related to receiving the PDSCH transmission; transmitting, in a first physical uplink control channel (PUCCH) resource allocated for the HARQ-ACK information, an indication that the HARQ-ACK information is not ready in time to be transmitted in the first PUCCH resource; and transmitting the HARQ-ACK information in a second PUCCH resource allocated for the HARQ-ACK information after the first PUCCH resource.

[0113] Example 10 includes the method of Example 9 or some other example herein, wherein the indication provides an offset between the first PUCCH resource and the second PUCCH resource.

[0114] Example 11 includes a method of operating a base station, the method comprising: receiving, from a target user equipment (UE), a request to enter an aggregated mode with a secondary UE; generating, for the target UE, a downlink transmission to be received by the target UE and the secondary UE; and transmitting the downlink transmission.

[0115] Example 12 includes the method of Example 11 or some other example herein, wherein the request comprises: uplink control information, extended hybrid automatic repeat request acknowledgement (HARQ-ACK), a scheduling request, or a physical random access channel transmission.

[0116] Example 13 includes the method of Example 11 or some other example herein, wherein transmitting the downlink transmission comprises: transmitting the downlink transmission with a beam in the aggregated mode that is wider than a beam in a non-aggregated mode.

[0117] Example 14 includes the method of Example 11 or some other example herein, wherein the downlink transmission comprises: a first physical downlink control information and a first physical downlink shared channel (PDSCH) transmission transmitted to the target UE; and a second downlink control information and a second PDSCH transmission transmitted to the secondary UE, wherein the first PDSCH transmission and the second PDSCH transmission comprise a common transport block for the target UE.

[0118] Example 15 includes a method of operating a user equipment (UE), the method comprising: processing a downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) transmission and includes a list of a plurality of UE identities that respectively correspond to a plurality of UEs within a downlink aggregation group to which the PDSCH transmission is transmitted; and determining a target UE of the plurality of UEs based on an order of the list.

[0119] Example 16 includes the method of Example 15 or some other example herein, further comprising: transmitting the PDSCH transmission to the UE. The PDSCH transmission (which can or can not be based on a specific request for the PDSCH transmission from the target UE) can be transmitted on preconfigured time or frequency domain resources of a PSSCH or a PUSCH.

[0120] Example 17 includes the method of Example 15 or some other example herein, wherein the UE is the target UE, the plurality of UEs includes an assisting UE, and the method further comprises: receiving the PDSCH transmission from the assisting UE.

[0121] Example 18 includes the method of Example 15 or some other example herein, wherein the DCI includes a group common DCI or includes cyclic redundancy check bits scrambled with a group radio network temporary identity.

[0122] Example 19 includes the method of Example 15 or some other example herein, further comprising: identifying a physical uplink control channel (PUCCH) resource based on the list of the plurality of UEs; and transmitting hybrid automatic repeat request (HARQ) acknowledgement (ACK) information corresponding to the PDSCH transmission in the PUCCH resource.

[0123] Example 20 includes a method of operating a base station, the method comprising: transmitting a transport block to a target user equipment (UE) in a downlink transmission to the target UE and an assisting UE; determining that the target UE did not successfully receive the transport block; and transmitting a request to the assisting UE to transmit the transport block to the target UE.

[0124] Example 21 includes the method of Example 20 or some other example herein, wherein the request includes a hybrid automatic repeat request (HARQ) identity associated with the transport block.

[0125] Example 22 includes the method of Example 20 or some other example herein, wherein determining that the transport block was not successfully received includes: receiving a negative acknowledgement from the target UE; or not receiving an expected positive acknowledgement from the target UE.

[0126] Example 23 includes the method of example 20 or some other example herein, further comprising transmitting an indication of resources to be used by the assisting UE to transmit transport blocks to the target UE.

[0127] Example 24 can include an apparatus comprising means for performing one or more elements of a method described in or related to any of examples 1-23, or any other method or process described herein.

[0128] Example 25 can include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-23, or any other method or process described herein.

[0129] Example 26 can include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-23, or any other method or process described herein.

[0130] Example 27 can include a method, technique, or process as described in or related to any of examples 1-23, or portions or parts thereof.

[0131] Example 28 can include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process as described in or related to any of examples 1-23, or portions thereof.

[0132] Example 29 can include a signal as described in or related to any of examples 1-23, or portions or parts thereof.

[0133] Example 30 can include a datagram, information element, packet, frame, segment, PDU, or message as described in or related to any of examples 1-23, or portions or parts thereof, or otherwise described in the present disclosure.

[0134] Example 31 can include a signal encoded with data as described in or related to any of examples 1-23, or portions or parts thereof, or otherwise described in the present disclosure.

[0135] Example 32 can include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described in or related to any of examples 1-23, or portions or parts thereof, or otherwise described in the present disclosure.

[0136] Example 33 can include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform a method, technique, or process as described in or related to any of examples 1-23, or portions thereof.

[0137] Example 34 can include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to perform a method, technique, or process as described in or related to any of examples 1-23, or portions thereof.

[0138] Example 35 can include a signal in a wireless network as shown and described herein.

[0139] Example 36 can include a method of communicating in a wireless network as shown and described herein.

[0140] Example 37 can include a system for providing wireless communication as shown and described herein.

[0141] Example 38 can include an apparatus for providing wireless communication as shown and described herein.

[0142] Any of the above examples can be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides functionality and / or technical features to enable one to achieve or enhance the advantages thereof, but the particular arrangements shown are not intended to be limiting. Numerous variations and modifications can be possible based on the teachings described herein, and such variations and modifications are encompassed within the scope of the disclosure. Accordingly, the disclosure is not limited to that described above but is only limited as defined by the claims.

[0143] While the forgoing implementations have been described in some detail for purposes of clarity and the specific embodiments have been explained above, it will be apparent to those skilled in the art that various adaptations and modifications of the aforementioned implementations can be accomplished with respect to those implementations. Accordingly, the disclosure is intended to be illustrated by the foregoing description, but is not limited to the exact forms described above. Rather, it is the following claims, including all equivalents thereof, that are intended to embrace all adaptations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a target user equipment (UE): identify an assisting UE; transmit, to the assisting UE, information to enable the assisting UE to receive a downlink communication from a base station to the target UE; transmit, to the base station, a request to enter an aggregated mode, wherein the request includes an indication of a time required to process and provide an acknowledgment of physical downlink shared channel transmissions received directly from the base station and from the assisting UE; and receive, from the base station via the assisting UE, the downlink communication.

2. The one or more computer-readable media of claim 1, wherein the information comprises: one or more radio network temporary identifiers (RNTIs) configured for the target UE; a physical downlink control channel (PDCCH) configuration for the target UE; a PDSCH configuration for the target UE; or an expected time to receive the downlink communication.

3. The one or more computer-readable media of claim 1, wherein to identify the assisting UE, the target UE is to: determine that the assisting UE and the target UE are associated with a same user; determine that the assisting UE is within a predefined range from the target UE; determine that the assisting UE has provided an indication that the assisting UE is capable of assisting; determine an expected proximity of the assisting UE to the target UE; or determine that the assisting UE has sufficient capability to assist.

4. The one or more computer-readable media of claim 1, wherein the request is an uplink control information, an extended hybrid automatic repeat request-acknowledgment (HARQ-ACK), a scheduling request, or a physical random access channel transmission.

5. The one or more computer-readable media of claim 1, wherein to transmit the request, the target UE is to: transmit an indication of a transmission configuration indication identity requested for the downlink communication.

6. The one or more computer-readable media of any of claims 1-5, wherein the request is a first request, and the instructions, when executed, further cause the target UE to: transmit, to the assisting UE, a second request for the downlink communication, wherein the second request is transmitted as sidelink control information on a physical sidelink control channel or as negative acknowledgement information on a physical uplink control channel.

7. The one or more computer-readable media of any of claims 1-5, wherein the instructions, when executed, further cause the target UE to: transmit, to the assisting UE, an indication of preconfigured resources to be used to transmit the downlink communication to the target UE.

8. The one or more computer-readable media of any of claims 1-5, wherein the downlink communication is a physical downlink shared channel (PDSCH) transmission, and the instructions, when executed, further cause the target UE to: receive a physical downlink control channel (PDCCH) transmission scheduling the PDSCH transmission; receive, from the assisting UE, the PDSCH transmission; generating hybrid automatic repeat request acknowledgement, HARQ-ACK, information related to the PDSCH transmission; transmitting, in a first physical uplink control channel, PUCCH, resource allocated for the HARQ-ACK information, an indication that the HARQ-ACK information is not ready in time to be transmitted in the first PUCCH resource; and transmitting the HARQ-ACK information in a second PUCCH resource allocated for the HARQ-ACK information after the first PUCCH resource.

9. The one or more computer-readable media of claim 8, wherein the indication provides an offset between the first PUCCH resource and the second PUCCH resource.

10. An apparatus for employment in a base station, the apparatus comprising: receiving circuitry to receive, from a target user equipment, UE, a request to enter an aggregated mode with a secondary UE, wherein the request includes an indication of a time required to process and provide an acknowledgement of physical downlink shared channel transmissions received directly from the base station and from the secondary UE; processing circuitry to generate, for the target UE, a downlink transmission to be received by the target UE and the secondary UE; and transmitting circuitry to transmit the downlink transmission.

11. The apparatus of claim 10, wherein the request comprises: uplink control information, extended hybrid automatic repeat request acknowledgement, HARQ-ACK, scheduling request, or physical random access channel transmission.

12. The apparatus of claim 10 or 11, wherein the transmitting circuitry is to transmit the downlink transmission using beams in the aggregated mode that are wider than beams in a non-aggregated mode.

13. The apparatus of claim 10 or 11, wherein the downlink transmission includes: first downlink control information and a first physical downlink shared channel, PDSCH, transmission to the target UE; and second downlink control information and a second PDSCH transmission to the secondary UE, wherein the first PDSCH transmission and the second PDSCH transmission include a common transport block for the target UE.

14. A method of operating a user equipment, UE, the method comprising: processing a downlink control information, DCI, that schedules a physical downlink shared channel, PDSCH, transmission and includes a list of multiple UE identities that respectively correspond to multiple UEs within a downlink aggregation group to which the PDSCH transmission is sent; determining a target UE of the multiple UEs based on an order of the list; identifying a physical uplink control channel, PUCCH, resource based on the list of the multiple UEs; and transmitting, in the PUCCH resource, hybrid automatic repeat request acknowledgement, HARQ-ACK, information corresponding to the PDSCH transmission.

15. The method of claim 14, further comprising: transmitting the PDSCH transmission to the target UE on a physical sidelink shared channel or a physical uplink shared channel. ​ ​ 16. The method of claim 15, wherein transmitting the PDSCH transmission is not based on a specific request from the target UE for the PDSCH transmission, and is transmitted on preconfigured time or frequency domain resources.

17. The method of any one of claims 14-16, wherein the UE is the target UE, the plurality of UEs includes a helper UE, and the method further comprises: receiving the PDSCH transmission from the helper UE.

18. The method of any one of claims 14-16, wherein the DCI includes group common DCI or includes cyclic redundancy check bits scrambled with a group radio network temporary identity.

19. A method of operating a base station, the method comprising: receiving a request from a target user equipment (UE) to enter an aggregated mode with a helper UE, wherein the request includes an indication of a time required to process and provide an acknowledgement of physical downlink shared channel transmissions received directly from the base station and from the helper UE; transmitting a transport block to the target UE in a downlink transmission to the target UE and the helper UE; determining that the target UE did not successfully receive the transport block; and transmitting a request to the helper UE to transmit the transport block to the target UE.

20. The method of claim 19, wherein the request to transmit the transport block to the target UE includes a hybrid automatic repeat request (HARQ) identification associated with the transport block.

21. The method of claim 19, wherein determining that the transport block was not successfully received includes: receiving a negative acknowledgement from the target UE; or not receiving an expected positive acknowledgement from the target UE.

22. The method of claim 19, further comprising: transmitting an indication of resources to be used by the helper UE to transmit the transport block to the target UE.

Images