Uplink timing for a virtual user equipment

Abstract

Various aspects of the present disclosure relate to uplink timing for a virtual user equipment (VUE). The techniques discussed herein describe timeline aspects of cooperative UL communications when a group of user equipment (UEs) form a VUE from the network perspective. For example, the VUE indicates to a base station a physical uplink shared channel (PUSCH) preparation time capability that is larger than (slower than) a PUSCH preparation time capability of the various UEs in the VUE. This larger PUSCH preparation time is, for example, a time between two known PUSCH preparation times (e.g., between the defined PUSCH preparation time for PUSCH timing capability 1 and the defined PUSCH preparation time for PUSCH timing capability 2).

Description

Lenovo Ref. No. SMM920230169-WO-PCT 1 UPLINK TIMING FOR A VIRTUAL USER EQUIPMENT RELATED APPLICATION

[0001] This application claims priority to U.S. Patent Application Serial No. 63 / 622,210 filed January 18, 2024, entitled “UPLINK TIMING FOR A VIRTUAL USER EQUIPMENT,” the disclosure of which is incorporated by reference herein in its entirety. TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to uplink (UL) timing for multiple user equipment (UE). BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, which may be otherwise known as network equipment (NE), supporting wireless communications for one or multiple user communication devices, which may be otherwise known as UE, or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)). SUMMARY

[0004] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). By Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 2 way of another example, a list of at least one of B; or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on”. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0005] A first UE for wireless communication is described. The first UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first UE may be configured to, capable of, or operable to transmit an indication of a first physical uplink shared channel (PUSCH) preparation time different than a second PUSCH preparation time associated with a group of UEs, wherein the group of UEs comprises the first UE and at least one second UE, and wherein the group of UEs are part of a virtual UE (VUE); and communicate with the at least one second UE for transmission of data to a network equipment.

[0006] A processor (e.g., a standalone processor chipset, or a component of a first UE) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to transmit an indication of a first PUSCH preparation time different than a second PUSCH preparation time associated with a group of UEs, wherein the group of UEs comprises a first UE that includes the processor and at least one second UE, and wherein the group of UEs are part of a VUE; and communicate with the at least one second UE for transmission of data to a network equipment.

[0007] A method performed or performable by a first UE for wireless communication is described. The method may include transmitting an indication of a first PUSCH preparation time different than a second PUSCH preparation time associated with a group of UEs, wherein the group of UEs comprises the first UE and at least one second UE, and wherein the group of UEs are part of a VUE; and communicating with the at least one second UE for transmission of data to a network equipment. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 3

[0008] In some implementations of the first processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to communicate with the second UE via a device-to-device (D2D) link to transmit the data to the network equipment.

[0009] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to receive an indication of a radio network temporary identifier (RNTI) for the VUE; and monitor one or more physical downlink control channel (PDCCH) candidates associated with the RNTI of the VUE for downlink control information (DCI) scheduling a PUSCH transmission of the data.

[0010] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to receive, from the second UE, the data; and transmit, to the network equipment via one or more PUSCH transmissions, the data based at least in part on the first PUSCH preparation time.

[0011] In some implementations of the first UE, processor, and method described herein, the data comprises a first block of data and a second block of data associated with the first UE.

[0012] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to transmit, to the network equipment via a first PUSCH transmission, the first block of data; and transmit, to the second UE, the second block of data for transmission to the network equipment via a second PUSCH transmission.

[0013] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to transmit, to the second UE, the first block of data and the second block of data for transmission to the network equipment via a PUSCH transmission.

[0014] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to transmit, to the network equipment via a first PUSCH transmission, the first block of Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 4 data; determine whether a third PUSCH time associated with at least one third UE of the group of UEs is less than the second PUSCH preparation time; and transmit, to the third UE and in response to the third PUSCH preparation time being less than the second PUSCH preparation time, the second block of data for transmission to the network equipment via a second PUSCH transmission.

[0015] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to receive, from the second UE, an indication of presence of UL data in a buffer of the second UE.

[0016] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to transmit, to the network equipment, a buffer status report (BSR) associated with a buffer of the first UE that indicates a time window in which the first UE expects to store the UL data in the buffer.

[0017] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to determine an absence of the UL data in the buffer of the first UE after expiry of the time window or determine a failure to store the UL data in the buffer of the first UE within the time window; and transmit, to the network equipment in response to determining the absence of the UL in the buffer of the first UE after expiry of the time window or the failure to store the UL data in the buffer of the first UE within the time window, an indication that cancels the BSR.

[0018] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to determine that the UL data is expected to be in the buffer of the first UE by a predetermined time; and transmit the BSR in response to determining that the first UE expects to have the UL data in the buffer of the first UE by the predetermined time.

[0019] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to transmit the BSR in response to receipt of the UL data from the second UE. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 5

[0020] In some implementations of the first processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to transmit, to the network equipment, a BSR that indicates presence of UL data; and transmit, to the second UE, an indication of one or more resources of an UL grant for the second PUSCH transmission.

[0021] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to transmit the indication of the one or more resources of the UL grant using a first available resource after transmission of the BSR to the network equipment.

[0022] A first UE for wireless communication is described. The first UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first UE may be configured to, capable of, or operable to receive, from a second UE, a block of data if a first PUSCH preparation time associated with the first UE is less than a second PUSCH preparation time associated with the second UE, wherein the first UE and the second UE are part of a VUE; and transmit, to a network equipment via a first PUSCH transmission, the first block of data.

[0023] A processor (e.g., a standalone processor chipset, or a component of a first UE) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to receive, at a first UE that includes the processor and from a second UE, a block of data if a first PUSCH preparation time associated with the first UE is less than a second PUSCH preparation time associated with the second UE, wherein the first UE and the second UE are part of a VUE; and transmit, to a network equipment via a first PUSCH transmission, the first block of data.

[0024] A method performed or performable by a first UE for wireless communication is described. The method may include receiving, from a second UE, a block of data if a first PUSCH preparation time associated with the first UE is less than a second PUSCH preparation time associated with the second UE, wherein the first UE and the second UE are part of a VUE; and transmitting, to a network equipment via a first PUSCH transmission, the first block of data. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 6

[0025] In some implementations of the first processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to receive, from the second UE, the block of data via a D2D link.

[0026] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to receive, from the second UE, an indication of one or more resources of an UL grant to be used by the second UE; determine a set of resources based on the one or more resources of the UL grant; and transmit, to the network equipment, the first block of data using the determined set of resources.

[0027] In some implementations of the first UE, processor, and method described herein, the first UE, processor, and method may further be configured to, capable of, performed, performable, or operable to receive, from the second UE, an indication of one or more resources of an UL grant to be used by the first UE; and transmit, to the network equipment, the first block of data using the one or more of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0029] Figure 2 illustrates an example of a VUE in accordance with aspects of the present disclosure.

[0030] Figure 3 illustrates an example of a VUE in accordance with aspects of the present disclosure.

[0031] Figure 4 illustrates an example of PUSCH preparation time in accordance with aspects of the present disclosure.

[0032] Figure 5 illustrates an example of a VUE in accordance with aspects of the present disclosure.

[0033] Figure 6 illustrates an example of BSR and PUSCH transmission for a VUE in accordance with aspects of the present disclosure. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 7

[0034] Figure 7 illustrates an example of and associated PUSCH cancellation in accordance with aspects of the present disclosure.

[0035] Figure 8 illustrates an example of BSR and associated PUSCH transmission in accordance with aspects of the present disclosure.

[0036] Figure 9 illustrates an example of one UE assisting another UE in UL transmission in accordance with aspects of the present disclosure.

[0037] Figure 10 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0038] Figure 11 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0039] Figure 12 illustrates an example of a NE in accordance with aspects of the present disclosure.

[0040] Figure 13 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.

[0041] Figure 14 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0042] UE cooperation can offer several benefits including traffic offload, capacity improvement, power saving, and distributed processing. One approach to UE cooperation can be for a network (e.g., a base station) to view (e.g., handle, manage) a group of cooperative UEs as one UE (referred to as a VUE), where the network views (e.g., handles, manages) sees a single device (e.g., UE) being served on user planes and control planes. Once the UEs form the VUE, the VUE registers with the network, and a connection (e.g., session, communication link) between the network (e.g., a base station, such as a next-generation NodeB (gNB)) and the VUE can leverage hardware, software, and computation power of the UEs (i.e., physical UEs) that formed the VUE.

[0043] For UL communication (e.g., UL transmission), timelines are defined for determining a PUSCH preparation time. For example, such timelines define a minimum time (e.g., duration) Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 8 between a downlink control information (DCI) an UL transmission and the first symbol of the UL transmission (e.g., a PUSCH transmission). If these timelines are not satisfied, the UE is not expected to transmit the UL transmission. Additionally, one or more UE operations, such as UL cancellation, may be performed when timing conditions defined based on these timelines are satisfied.

[0044] In a VUE, if at least a part (e.g., portion) of UL data from a first UE in the VUE is to be communicated to the network via a second UE in the VUE, extra signaling is performed to enable cooperation between the first UE and the second UE. Depending on communication protocols, such as when a BSR is triggered or how the first UE and the second UE coordinate resources for UL transmission, such cooperation may require additional time. This additional time can impact the PUSCH preparation time and, hence, the capability (e.g., PUSCH preparation time) indicated (e.g., communicated) to the network by the VUE.

[0045] The techniques described herein relate to timeline aspects of cooperative wireless communications (e.g., UL communications) when a group of UEs forms a VUE. In one or more implementations, the VUE indicates to the network (e.g., a base station) a PUSCH preparation time capability that is longer than (and slower / shorter than) a PUSCH preparation time capability of the various UEs in the VUE. This longer PUSCH preparation time may be, for example, a duration between two known PUSCH preparation times (e.g., between the PUSCH preparation time for PUSCH timing capability 1 and the PUSCH preparation time for PUSCH timing capability 2). This allows for additional time for the VUE to perform extra signaling to allow for cooperation between the first UE and the second UE for the UL communications. By selecting a time between two known PUSCH preparation times, latency for the UL communications is reduced compared to simply selecting a known slower / shorter PUSCH preparation time (e.g., the PUSCH preparation time for PUSCH timing capability 1).

[0046] Additionally or alternatively, the VUE may include a gateway UE (GUE) that couples (e.g., connects) the VUE to the network (e.g., a base station). In such implementations, UL data from UEs in the VUE are transmitted to the network by the GUE. The GUE can transmit a BSR to the network including an indication of a deadline by which the GUE expects to have data in the buffer of the GUE (e.g., data transmitted to by one or more other UEs in the VUE to the GUE and temporarily stored at the GUE). This allows the network to schedule UL communication (e.g., Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 9 resources) even if the data to be transmitted has yet been received by the GUE (e.g., buffered at the GUE), thereby reducing latency compared to scenarios where the GUE waits to send the BSR until the data is received and stored in the buffer of the GUE. Additionally or alternatively, whether two UEs in a VUE cooperate to transmit UL data to the network depends on various conditions. For example, a first UE in the VUE may transmit UL data to a second UE in the VUE for transmission to the network only if the second UE has the same or higher (e.g., faster, shorter) PUSCH preparation time capability as the first UE.

[0047] Aspects of the present disclosure are described in the context of a wireless communications system.

[0048] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a new radio (NR) network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0049] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next- generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 10 an NE 102 and a UE 104 may perform wireless (e.g., receive signaling, transmit signaling) over a Uu interface.

[0050] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non- terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0051] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of- Everything (IoE) device, or machine-type communication (MTC) device, among other examples.

[0052] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0053] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., S1, N2, N6, or other network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other indirectly (e.g., via the CN 106). In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 11 example of an access node controller (ANC). ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0054] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0055] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an S1, N2, N6, or other network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0056] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 12 frame structures (i.e., multiple frame NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0057] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., ^=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., ^=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., ^=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., ^=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., ^=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., ^=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0058] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0059] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., ^=0, ^=1, ^=2, ^=3, ^=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 13 relationship between the number of symbols the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., ^=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0060] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz – 7.125 GHz), FR2 (24.25 GHz – 52.6 GHz), FR3 (7.125 GHz – 24.25 GHz), FR4 (52.6 GHz – 114.25 GHz), FR4a or FR4-1 (52.6 GHz – 71 GHz), and FR5 (114.25 GHz – 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0061] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., ^=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., ^=1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., ^=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., ^=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., ^=3), which includes 120 kHz subcarrier spacing.

[0062] UE cooperation can offer several benefits including traffic offload, capacity improvement, power saving, and distributed processing. One approach to UE cooperation can be to view a group of cooperative UEs as one UE (referred to as virtual UE (VUE)) from the network perspective, where the network views (e.g., handles, manages) a single device being served on user and control planes. Once the UEs form the VUE, the VUE registers with the network, and the communication link between a next-generation NodeB (gNB) and the VUE can leverage hardware, software, and computation power of the physical UEs that formed the VUE. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 14

[0063] Figure 2 illustrates an example 200 a VUE in accordance with aspects of the present disclosure. In the example 200, a VUE 202 is formed by a set of UEs that cooperate, illustrated as UE1 204, UE2206, UE3208, and GUE 210. The GUE 210 connects or couples the VUE 202 to a network, such as via gNB 212. The VUE can include one or more GUEs, and one or more UEs in the VUE can have a direct connection to the gNB 212. UE1204, UE2206, and UE3208 can optionally communicate with one another via a device-to-device (D2D) link. A D2D link can be a wireless or wired link. As an example, UE1204 can be a smart-watch, UE2206 can be smart glasses, UE3208 can be a smart glove, and GUE 210 can be a smart phone.

[0064] Figure 3 illustrates an example 300 of a VUE in accordance with aspects of the present disclosure. In the example 300, a VUE 302 is formed by a set of UEs that cooperate, illustrated as UE1 304, UE2306, and UE3308. UEs associated with or part of the VUE 302 have a connection to the gNB 310, and data communication is between UE3308 (also referred to as a primary device or primary UE) and gNB 310, and UE1304 and UE2306 are assisting such communication. UE1304 and UE2306 may thus also be referred to as an assisting device or an assisting UE. UE1304, UE2 306, and UE3308 can communicate with one another via a D2D link. As an example, UE3308 can be a laptop, UE1304 can be a smartphone, and UE2306 can be a tablet.

[0065] Returning to Figure 1, for UL, timelines are defined such as for determining PUSCH preparation time (e.g., a minimum time between DCI scheduling UL transmission and the first symbol of the corresponding UL / PUSCH transmission; otherwise, the UE is not expected to transmit the UL transmission), and some UE operations (e.g., UL cancellation) are performed when timing conditions defined based on those timelines are satisfied.

[0066] In a VUE, if at least a part of UL data from a first UE in the VUE is to be communicated to the gNB via a second UE in the VUE, extra signaling is performed to allow for cooperation between the first UE and the second UE. Depending on communication protocols (e.g., when a BSR is triggered, or how the first and second UE coordinate resources for UL transmission) such cooperation may take additional time, which can impact PUSCH preparation time and hence the corresponding capability (e.g., PUSCH preparation time) indicated to the network by the VUE.

[0067] Figure 4 illustrates an example 400 of PUSCH preparation time in accordance with aspects of the present disclosure. In the example 400, time progresses from left to right. As Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 15 illustrated in the example 400, at 402 a gNB DCI scheduling a UE. At 404 a real UE (RUE), also referred to as a non-VUE or physical UE, sends UL data to the gNB a time gap 406 after the gNB sends the DCI at 402. At 408, a VUE sends UL data to the gNB at time gap 410 after the gNB sends the DCI at 402. The PUSCH preparation time (tg2) is larger for the VUE than that of the RUE (tg1).

[0068] Returning to Figure 1, in one or more implementations, timelines and protocols for cooperation between the first UE and the second UE in a VUE are defined to take care of processing network commands such as when the first UE is to indicate to the second UE which part of the allocated UL resources are to be used by the second UE, and / or to help the network perform efficient scheduling e.g., via BSR enhancements. Such enhancements can include BSR indicating the deadline it expects data (from the first UE) to arrive in a device buffer of a second UE, and to send a BSR cancellation indication in case the deadline cannot be honored (e.g., due to D2D-related transmission failures associated with the cooperative UL transmission).

[0069] This disclosure provides solutions for defining timelines and associated capabilities for different VUE configurations.

[0070] For example, the techniques discussed herein describe timeline aspects of cooperative UL communications when a group of UEs form a VUE from the network perspective. In one or more implementations, the VUE indicates to the gNB a PUSCH preparation time capability that is larger than (slower than) a PUSCH preparation time capability of the various UEs in the VUE. This larger PUSCH preparation time is, for example, a time between two known PUSCH preparation times (e.g., between the defined PUSCH preparation time for PUSCH timing capability 1 and the defined PUSCH preparation time for PUSCH timing capability 2). This allows for additional time for the VUE to perform extra signaling to allow for cooperation between the first UE and the second UE for the UL transmission. Using a time between two known PUSCH preparation times also reduces latency in the UL transmission that could result from simply selecting a known slower PUSCH preparation time (e.g., the defined PUSCH preparation time for PUSCH timing capability 1).

[0071] With respect to UE PUSCH preparation procedure time, if the first uplink symbol in the PUSCH allocation for a transport block, including the demodulation reference signal (DM-RS), as Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 16 defined by the slot offset K2and Koffset, if and the start S and length L of the PUSCH allocation indicated by 'Time domain resource assignment' of the scheduling DCI and including the effect of the timing advance, is no earlier than at symbol L2, where L2 is defined as the next uplink symbol with its cyclic prefix (CP) starting T= max (N + d + d )(2048 + 144) ⋅κ 2 −µproc , 2 ( 2 2,1 2 ⋅ T C +Text + T switch , d 2,2 )PUSCH, then the UE shall transmit the transport block. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, for the purpose of determining the last symbol of the PDCCH carrying the DCI scheduling the PUSCH, the PDCCH candidate that ends later in time is used.

[0072] N2 is based on µ of Table 1 and Table 2 for UE processing capability 1 and 2respectively, where µ corresponds to the one of (µDL, µUL) resulting with the largest Tproc,2, wherethe µDL corresponds to the subcarrier spacing of the downlink with which the PDCCH carrying the DCI scheduling the PUSCH was transmitted and µULcorresponds to the subcarrier spacing of the uplink channel with which the PUSCH is to be transmitted, and κ is defined in clause 4.1 of 3rd Generation Partnership Project (3GPP) technical specification (TS) 38.211.

[0073] For operation with shared spectrum channel access in FR1,Textis calculated according to3GPP TS 38.211, otherwiseText=0.

[0074] If the first symbol of the PUSCH allocation consists of DM-RS only, then d2,1= 0, otherwise d2,1= 1.

[0075] If the UE is configured with multiple active component carriers, the first uplink symbol in the PUSCH allocation further includes the effect of timing difference between component carriers as given in 3GPP TS 38.133.

[0076] If the scheduling DCI triggered a switch of bandwidth part (BWP), d2,2 equals to the switching time as defined in 3GPP TS 38.133, otherwise d2,2=0.

[0077] If a PUSCH of a larger priority index would overlap with physical uplink control channel (PUCCH) of a smaller priority index and the UE is not provided uci-MuxWithDiffPrio for Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 17 the primary PUCCH group or uci- for the secondary PUCCH group, d2for the PUSCH of a larger priority is set as reported by the UE; otherwise d2= 0.

[0078] For a UE that supports capability 2 on a given cell, the processing time according to UE processing capability 2 is applied if the high layer parameter processingType2Enabled in PUSCH- ServingCellConfig is configured for the cell and set to 'enable',

[0079] If the PUSCH indicated by the DCI is overlapping with one or more PUCCH channels, then the transport block is multiplexed following the procedure in clause 9.2.5 of 3GPP TS 38.213, otherwise the transport block is transmitted on the PUSCH indicated by the DCI.

[0080] If uplink switching gap is triggered as defined in clause 6.1.6, Tswitchequals to the switching gap duration and for the UE configured with higher layer parameter uplinkTxSwitchingOption set to 'dualUL' for uplink carrier aggregation µUL=min(µUL,carrier1, µUL,carrier2), otherwise Tswitch=0.

[0081] Otherwise the UE may ignore the scheduling DCI.

[0082] The value of Tproc , 2 is used both in the case of normal and extended cyclic prefix.Table preparation time for PUSCH timing capability 1 µPUSCH preparation time N2[symbols] 0 10 1 12 2 23 3 36 5 144 6 288 Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 18 Table 2: PUSCH preparation for PUSCH timing capability 2 µPUSCH preparation time N2[symbols] 0 5 1 5.5 2 11 for frequency range 1

[0083] According to 3GPP TS 38.300, UL BSRs are used to provide support for quality of service (QoS) aware packet scheduling. In NR, UL BSRs refer to the data that is buffered in for a group of logical channels (LCG) in the UE. The integrated access backhaul (IAB) node can send a Pre-emptive BSR based on UL grants it has provided to child nodes and / or UEs, or based on BSRs it has received from child nodes or UEs. The Pre-emptive BSR conveys the data expected rather than the data buffered.

[0084] A scheduling request (SR) can be transmitted (e.g., in a configured periodic SR resource) by the UE (e.g. when no resources are available to transmit the BSR).

[0085] In the discussions herein, it is assumed that once a VUE is formed, the VUE sends a message to a gNB indicating that the VUE is formed (e.g., by a random access channel (RACH) indicating a VUE identifier (VUE-ID)). The gNB sends a VUE capability inquiry to the VUE and receives corresponding capabilities that are applicable to the VUE from the UE (e.g., through a gate-way UE). These capabilities include, for example, a PUSCH preparation time.

[0086] If the gNB views (e.g., handles, manages) the VUE as a single UE, the gNB addresses all the internal UEs of the VUE with the same RNTI and accordingly, all such UEs get the same DCI from the network if they have a direct connection with the network (such as the VUE scenario of Figure 3).

[0087] The present disclosure concerns about UL timing aspects of VUE operation. The present disclosure discusses having at least one additional processing capability or time (that is not applicable to a real individual UE: e.g., something between N2 values currently specified for processing capability 1 and 2) applicable to the case of VUE operation: e.g., N2. Additionally, or alternatively, at least one additional Tproc,2value that is different than the one specified for individual real UEs (not VUEs) can be defined. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 19

[0088] The present disclosure discusses enhancements. For example, BSR (from VUE to gNB) is triggered when an internal UE’s data is expected to be in the buffer of the GUE not later than a certain time (e.g., a timeline is satisfied with respect to D2D communication). By way of another example, BSR for a UE indicates when the UE expects the data associated with the BSR to become available at the buffer of the UE.

[0089] The present disclosure discusses a D2D indication of content from a primary UE to an assisting UE.

[0090] The present disclosure discusses timelines for collaborative UL data transmission. Timeline and processing capability conditions are discussed to determine if an assisting UE can collaborate to transmit part of UL data of a primary UE to the network.

[0091] With respect to UE PUSCH preparation procedure time, for a RUE, a PUSCH transmission can start no earlier than Tproc,2from the end of the scheduling PDCCH (details below), where Tproc,2depends on a PUSCH preparation capability (‘N2’), and other parameters, namely d2,1, d2,2, d2, Text, Tswitch, etc.

[0092] In one or more implementations, for a VUE, once an internal UE (e.g., referred to as UE1 in Figure 2) has UL data (destined for a gNB), for a D2D resource allocation mode1-like resource allocation scheme (where network or GUE assigns D2D communication resources), UE1 sends a side-link or D2D BSR (referred to as D-BSR) to a GUE, where D-BSR indicates to the GUE presence of UL data at a buffer of UE1.

[0093] The GUE schedules data transmission (referred to as side-link transmission ‘S1’) from UE1 to GUE (e.g., via D2D transmission). This scheduling is done via a sidelink control information (SCI). SCI transmission triggers a BSR (from GUE to gNB)

[0094] The GUE sends a corresponding BSR to gNB (e.g., as illustrated in Figures 6 and 8). The GUE does the BSR transmission if the GUE has received D-BSR, or scheduled ‘S1’ to be transmitted or received by at most ‘t1’ time units (e.g., symbols or slots) from the time the SCI is sent, or scheduled ‘S1’ to be transmitted or received by at most ‘t2’ time units (e.g., symbols or slots) from the time the BSR is supposed to be sent. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 20

[0095] If the GUE has sent the BSR to as BSR1) and has not yet received S1 (e.g., an absence of data in the buffer of the GUE) within ‘t4’ time units (e.g., in case S1 could not be correctly decoded and a re-transmission is needed from UE1 to GUE), the GUE sends a notification to the gNB to cancel the previously indicated BSR (e.g., as illustrated in Figure 7). The notification can be a BSR and a specific buffer size value for the corresponding logical channel group (LCG) can indicate such BSR cancellation. This notification is sent to the gNB if the GUE has not yet received a scheduling DCI in response to BSR1 or has received the scheduling DCI with the time gap between the notification and the to be cancelled transmission is larger than ‘t5’ (hence, sending such indication to the gNB becomes useful as gNB will have sufficient time to re-allocate the UL resources to another UE). The gNB sends a DCI (referred to as dci_p) to the GUE scheduling an UL transmission (referred to as ‘U1’).

[0096] The VUE or GUE is not expected to transmit U1 earlier than Tproc,2_vuefrom dci_p.

[0097] Figure 5 illustrates an example 500 of a VUE in accordance with aspects of the present disclosure. In the example 500, a VUE 502 is formed by a set of UEs that cooperate, including a UE1 504 and a GUE 506. Although two UEs are illustrated in the example 500, it is to be appreciated that the VUE 502 can include any number of UEs. The example 500 illustrates that the UE1 504 sends UL data to the gNB 508 via the GUE 506. In the example 500, the timing order is i1<i2<i3.

[0098] Figure 6 illustrates an example 600 of BSR and PUSCH transmission for a VUE in accordance with aspects of the present disclosure. In the example 600, time progresses from left to right. As illustrated in the example 600, at 602 UE1 sends a sidelink BSR (SL-BSR) to the GUE. At 604, the GUE sends SCI scheduling UE1. At 606, the GUE sends a BSR (BSR(S1)) to the gNB. At 608, the gNB sends DCI_p scheduling the GUE. At 610, the UE1 sends data S1 to the GUE. At 612, the GUE sends data U1(S1) to the gNB. A first time gap 614 is illustrated between the GUE sending SCI scheduling UE1 at 604 and the UE sending data S1 to the GUE at 610. A second time gap 616 is also illustrated between the GUE sending BSR(S1) to the gNB at 606 and the UE sending data S1 to the GUE at 610. A third time gap 618 is also illustrated between the gNB sending DCI_p scheduling the GUE at 608 and the GUE sending data U1(S1) to the gNB at 612. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 21

[0099] In one or more implementations, time gap at 614 is less than t1. Additionally or alternatively, the second time gap at 616 is less than t2. It should be noted that BSR indicating presence of data S1 at UE1 is sent at 606 before the GUE receives the data S1 at 610. The gNB schedules the GUE or VUE for the UL transmission, where the third time gap 618 is not smaller than Tproc,2_vue.

[0100] Figure 7 illustrates an example 700 of BSR and associated PUSCH cancellation in accordance with aspects of the present disclosure. In the example 700, time progresses from left to right. As illustrated in the example 700, at 702 the GUE sends BSR(S1) to the gNB. At 704 the gNB sends DCI scheduling PUSCH (S1) transmission by the GUE. At 706 the sends BSR(S1) cancellation to the gNB and cancels the scheduled PUSCH. At 708 the GUE was supposed to send PUSCH(S1) to the gNB but does not due to the BSR(S1) cancellation. A first time gap 710 between the GUE sending the BSR(S1) to the gNB at 702 and the GUE sending BSR(S1) cancellation to the gNB and canceling the scheduled PUSCH at 706 is illustrated. A second time gap 712 between the GUE sending BSR(S1) cancellation to the gNB and canceling the scheduled PUSCH at 706 and the GUE supposed to send PUSCH(S1) to the gNB at 708 is also illustrated.

[0101] In the example 700, BSR and associated PUSCH are canceled if the first time gap 710 between the BSR transmission and the cancellation is larger than ‘t4’, and the second time gap 712 between the cancellation and / or the cancelled PUSCH is larger than ‘t5’.

[0102] In one or more implementations, the GUE or VUE indicates to the gNB whether the data for which the BSR is being sent is available at the GUE or VUE at the time the BSR is being sent or constructed.

[0103] Additionally or alternatively, the GUE or VUE indicates when the GUE or VUE expects the associated data being available at its buffer. For instance, the GUE or VUE indicates in the BSR to the network that it expects the data associated with the BSR becomes available at the GUE or VUE buffer in 2 time-units (e.g., slots). The VUE, GUE, or network determines Tproc,2_vueaccording to Tproc,2and the indicated time in the BSR.

[0104] In one or more implementations, Tproc,2_vueis longer than ‘Tproc,2’ determined by the network based on GUE capability reporting. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 22

[0105] The VUE or GUE may report which can determineTproc,2_vue. For example,the VUE or GUE can report ‘N2-2’ for a subcarrier spacing (SCS) µ, where N2-2(µ)>N2(µ) for a processing capability (PUSCH timing capability). Additionally or alternatively, a new PUSCH timing capability is defined that is applicable to VUE configurations.

[0106] Tproc,2_vueis determined based on a PUSCH timing capability, where the PUSCH timing capability is determined based on adding a δ>0 to the reported GUE’s PUSCH timing capability, where δ(µ) is reported or measured by the VUE or fixed in the specifications or configured.

[0107] In one or more implementations, the VUE updates the value of N2-2 / Tproc,2_vuebased on virtual group updates.

[0108] The changes in the group can trigger such N2-2 / Tproc,2_vueupdate. For example, if a UE (e.g., at the edge of the VUE or having the worst D2D link quality according to a measure (such as link length)) in the VUE leaves the VUE, and removal of that UE lets the GUE receive a D2D signaling significantly faster (e.g., by couple of symbols of a reference SCS) from any other internal UE, then N2-2 / Tproc,2_vuecan be updated (e.g., reduced). Additionally or alternatively, if a UE is added to the VUE, and the added UE has a significantly worse D2D link compared to the other D2D links, then N2-2 / Tproc,2_vuecan be updated (e.g., increased).

[0109] Such an update can be communicated with the gNB via a medium access control control element (MAC-CE), radio resource control (RRC), or physical layer signaling (such as an uplink control information (UCI)). In one or more implementations the update triggers a new VUE capability inquiry from the gNB or network, where the VUE or GUE can now send the updated capability information to the network.

[0110] In one or more implementations, the Pre-emptive BSR framework can be re-used for this purpose for BSR transmission by the VUE (with some of the suggested changes above; e.g., timeline aspects, triggering conditions, BSR cancellation indication, etc.).

[0111] With respect to SR-related aspects, for SR from GUE to gNB, in one or more implementations once an internal UE (e.g., UE1 in Figure 2) has UL data (destined for the gNB), for D2D resource allocation mode1-like (network or GUE-involved resource allocation (RA)), the internal UE sends a side-link or D2D BSR (referred to as D-BSR) to a GUE. The GUE schedules Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 23 data transmission (referred to as side-link ‘S1’) from the internal UE to the GUE (e.g., via D2D). This scheduling is done via a SCI and the SCI transmission triggers a BSR (from the GUE to the gNB).

[0112] The GUE sends a corresponding SR to the gNB. The GUE does the SR transmission if the GUE has received D-BSR, received ‘S1’, or scheduled ‘S1’ to be transmitted or received by at most ‘t1’ time units (e.g., symbols or slots) from the time the SCI is sent, or scheduled ‘S1’ to be transmitted or received by at most ‘t2’ time units (e.g., symbols or slots) from the time the BSR is sent.

[0113] If the GUE has sent the SR (referred to as SR1) and has not yet received S1 within ‘t4’ time units (e.g., in case S1 could not be correctly decoded and a re-transmission is needed from the internal UE to the GUE), the GUE sends a notification to the gNB to cancel the previously indicated SR1. The notification can be another SR (e.g., using the same SR configuration associated with the same logical channel (LCH) or LCG) indicating SR1 cancellation (such that the gNB knows which SR is cancelled). Such notification is sent to the gNB if the GUE has not yet received a scheduling DCI in response to SR1 or has received the scheduling DCI not ‘t5’ time units before sending the notification.

[0114] The gNB sends a DCI (referred to as dci1) to the GUE scheduling an UL transmission (referred to as ‘U1’). The VUE or GUE is not expected to transmit U1 earlier than Tproc,2_vuefrom dci_p.

[0115] Figure 8 illustrates an example 800 of BSR and associated PUSCH transmission in accordance with aspects of the present disclosure. In the example 800, time progresses from left to right. The example 800 illustrates a timeline for BSR and PUSCH transmission for VUE in case of SR transmissions prior to PUSCH transmission. As illustrated in the example 800, at 802 UE1 sends a sidelink scheduling request (SL-SR) to the GUE. At 804 the GUE sends SCI scheduling UE1. At 806 UE1 sends an SL-BSR to the GUE. At 808 the GUE sends SR(S1) to the gNB. At 810 the gNB sends DCI scheduling the GUE. At 812 the GUE sends BSR(S1) to the gNB. At 814, the gNB sends dci_p to the scheduling GUE. At 816, UE1 sends S1 to the GUE. At 818 the GUE sends U1(S1) to the gNB. A time gap 820 between the gNB sending dci_p to the scheduling GUE ant the GUE sending UE(S1) to the gNB is also illustrated. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 24

[0116] With respect to resource allocation related aspects, for resource-allocation mode 2, the transmission is as follow. In one or more implementations, for a VUE, once an internal UE (e.g., UE1 in Figure 2) has UL data (destined for the gNB), for D2D resource allocation mode2-like (UE1 selecting a D2D resource to communicate with the GUE), UE1 sends ‘S1’ to a GUE. The GUE, sends a corresponding SR or BSR to the gNB (e.g., as shown in Figure 6 and Figure 8). The GUE does the SR or BSR transmission. The gNB sends a DCI (referred to as dci1) to the GUE scheduling an UL transmission (referred to as ‘U1’). The VUE or GUE is not expected to transmit U1 earlier than Tproc,2from dci_p.

[0117] In case ‘S1’ takes more than one transmission slot, UE1 can indicate in a D-BSR to the GUE how much or for how long UE1 expects to transmit ‘S1’.

[0118] With respect to VUE configuration-related aspects, in one or more implementations multiple internal UEs can (a) receive a DCI from the network, and (b) transmit a PUSCH to the network (e.g., as illustrated in Figure 9).

[0119] In one or more implementations, a first UE of a VUE sends a BSR to the network. The first UE shares some part of its data (e.g., data of a particular LCG / LCH or a transport block (TB)) with a second UE of the VUE. The first UE and the second UE receive an UL DCI scheduling a PUSCH transmission. The first UE indicates to the second UE via a first indication (e.g., via SCI) in what part of the allocated resources indicated in the UL DCI (referred to as a second part of the resources) the second UE is to transmit in. The SCI can indicate that the SCI is applicable to the data that is going to be collaboratively transmitted by the second UE. The first UE transmits to the gNB in a first part of the resources, and the second UE transmits to the gNB in the second part of the resources.

[0120] In one or more implementations, the first indication is sent after reception of the UL DCI. The first indication is sent not earlier than ‘T’ time units after reception of the UL DCI; where ‘T’ is a UE capability, e.g., depending on Tproc,2. The second part of the resources includes resources that occur after (in time domain) the first part of the resources (the second part of resources may occur at least a particular time from the first symbol of the first part of resources). This gives the second UE more time to process the SCI and figure out when to transmit Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 25

[0121] Additionally or alternatively, the is sent before reception of the UL DCI; otherwise the second UE is not expected to cooperate in collaborative transmission of UL data of the first UE. This approach offers lower latency as the second UE does not need to wait to receive the SCI after the reception of the UL DCI. The first indication indicates what percentage of the to be allocated resources provided by the UL DCI is to be used by the second UE. The first indication is sent in the first available SL (D2D) resource after the transmission of the BSR, or in a SL resource prior to transmission of BSR.

[0122] Additionally or alternatively, the second UE only cooperates with the first UE when both UEs have the same processing capability (e.g., in terms of ‘N2’ for PUSCH preparation time), or the second UE is more processing capable (has a higher capability, e.g., in terms of less number of ‘N2’ symbols).

[0123] Figure 9 illustrates an example 900 of one UE assisting another UE in UL transmission in accordance with aspects of the present disclosure. In the example 900, a VUE 902 is formed by a set of UEs that cooperate, including a UE1904 and a UE2906, each of which can transmit a PUSCH to the gNB 908. Although two UEs are illustrated in the example 900, it is to be appreciated that the VUE 902 can include any number of UEs.

[0124] The example 900 illustrates that UE2906 assists UE1904 in UL transmission to the gNB 908. The UE1904 shares UL data (D) with the UE2906 at time ‘t1’, and the UE1904 sends a control command (c) to the UE2906 at time ‘t2’>’t1’ indicating which part of allocated resources (or to be allocated resources) to be used for transmission by the UE2906.

[0125] Accordingly, additional processing capability or time applicable to the case of VUE operation: e.g., N2 is discussed herein.

[0126] BSR enhancements are also discussed herein, including BSR (from VUE to gNB) is triggered when an internal UE’s data is expected to be in a GUE’s buffer not later than a certain time (a timeline is satisfied with respect to D2D communication). The BSR indicates when the UE expects the data associated with the BSR to become available at its buffer is also discussed herein.

[0127] The D2D indication content from a primary UE to an assisting UE is also discussed herein. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 26

[0128] Timelines and capability conditions collaborative UL data transmission are also discussed herein.

[0129] Timeline aspects of cooperative UL communications when a group of UEs form a VUE from the network perspective is discussed herein. Timelines and capability conditions enabling collaborative UL data transmission are discussed, BSR triggering and content enhancements to enable UL transmission by an assisting UE are discussed, and D2D control information content from a primary UE to an assisting UE to allow cooperative communication are also discussed.

[0130] A VUE can indicate a lower capability in terms of PUSCH preparation time than that of the primary UE having or originating UL data. However, this approach might lead to additional latency (even 100% latency increase), whereas with the techniques discussed herein the VUE can indicate a slightly lower capability instead of processing capability 1.

[0131] A GUE can send BSR on behalf of the primary UE once the GUE has received the data of the primary UE. While this approach works, it leads to additional latency compared to the techniques discussed herein, where the BSR is sent by the GUE prior to reception of data from the primary UE, if certain timelines are satisfied.

[0132] In one or more implementations, the VUE indicates a second PUSCH preparation time capability (PPTC2 / N2_2) that is larger (slower) than a first PUSCH preparation time capability(PPTC1 / N2_1), where all UEs of the VUE have PPTC1, and PPTC2>PPTC1 (N2_2>N2_1).

[0133] Additionally or alternatively, a GUE indicates to a gNB a BSR including an indication indicating a deadline by which it expects to have data in its buffer. This deadline may be, for example, expiry of a time window in which the GUE expects to have data in its buffer.

[0134] Additionally or alternatively, a second UE of the VUE cooperates with a first UE in transmission of the first UE’s UL data to a gNB only if the second UE has the same or higher (faster) PUSCH preparation time capability.

[0135] Figure 10 illustrates an example of a UE 1000 in accordance with aspects of the present disclosure. The UE 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008. The processor 1002, the memory 1004, the controller 1006, or the transceiver Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 27 1008, or various combinations thereof or thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0136] The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0137] The processor 1002 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1002 may be configured to operate the memory 1004. In some other implementations, the memory 1004 may be integrated into the processor 1002. The processor 1002 may be configured to execute computer-readable instructions stored in the memory 1004 to cause the UE 1000 to perform various functions of the present disclosure.

[0138] The memory 1004 may include volatile or non-volatile memory. The memory 1004 may store computer-readable, computer-executable code including instructions when executed by the processor 1002 cause the UE 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 1004 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0139] In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to cause the UE 1000 to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004). For example, the processor 1002 may support wireless communication at the UE 1000 in accordance with examples as disclosed herein. The UE 1000 may be a first UE configured to or Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 28 operable to support a means for transmitting an of a first PUSCH preparation time different than a second PUSCH preparation time associated with a group of UEs, where the group of UEs comprises the first UE and at least one second UE, and where the group of UEs are part of a VUE; and communicating with the at least one second UE for transmission of data to a network equipment.

[0140] Additionally, the UE 1000 may be configured to support any one or combination of communicating with the second UE via a D2D link to transmit the data to the network equipment; receiving an indication of a RNTI for the VUE; and monitoring one or more PDCCH candidates associated with the RNTI of the VUE for DCI scheduling the transmission of the data; transmitting, to the network equipment via one or more PUSCH transmissions, the data based at least in part on the first PUSCH preparation time; where the data comprises a first block of data and a second block of data associated with the first UE; transmitting, to the network equipment via a first PUSCH transmission, the first block of data; and transmitting, to the second UE, the second block of data for transmission to the network equipment via a second PUSCH transmission; transmitting, to the second UE, the first block of data and the second block of data for transmission to the network equipment via a PUSCH transmission; transmitting, to the network equipment via a first PUSCH transmission, the first block of data; determining whether a third PUSCH preparation time associated with at least one third UE of the group of UEs is less than the second PUSCH preparation time; and transmitting, to the third UE and in response to the third PUSCH preparation time being less than the second PUSCH preparation time, the second block of data for transmission to the network equipment via a second PUSCH transmission; receiving, from the second UE, an indication of presence of UL data in a buffer of the second UE; transmitting, to the network equipment, a BSR associated with a buffer of the first UE that indicates a time window in which the first UE expects to store the UL data in the buffer; determining an absence of the UL data in the buffer of the first UE after expiry of the time window or determine a failure to store the UL data in the buffer of the first UE within the time window; and transmitting, to the network equipment in response to determining the absence of the UL in the buffer of the first UE after expiry of the time window or the failure to store the UL data in the buffer of the first UE within the time window, an indication that cancels the BSR; determining that the UL data is expected to be in the buffer of the first UE by a predetermined time; and transmitting the BSR in response to determining that the first Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 29 UE expects to have the UL data in the buffer first UE by the predetermined time; transmitting the BSR in response receipt of the UL data from the second UE; transmitting, to the network equipment, a BSR that indicates presence of UL data; and transmitting, to the second UE, an indication of one or more resources of an UL grant for the second PUSCH transmission; transmitting the indication of the one or more resources of the UL grant using a first available resource after transmission of the BSR to the network equipment.

[0141] Additionally, or alternatively, the UE 1000 may be a first UE and support at least one memory (e.g., the memory 1004) and at least one processor (e.g., the processor 1002) coupled with the at least one memory and configured to cause the UE to: transmit an indication of a first PUSCH preparation time different than a second PUSCH preparation time associated with a group of UEs, where the group of UEs comprises the first UE and at least one second UE, and where the group of UEs are part of a VUE; and communicate with the at least one second UE for transmission of data to the network equipment.

[0142] Additionally, the UE 1000 may be configured to support any one or combination of the at least one processor is configured to communicate with the second UE via a D2D link to transmit the data to the network equipment; receive an indication of a RNTI for the VUE; and monitor one or more physical PDCCH candidates associated with the RNTI of the VUE for DCI scheduling the transmission of the data; receive an indication of the data; and transmit, to the network equipment via one or more PUSCH transmissions, the data based at least in part on the first PUSCH preparation time; where the data comprises a first block of data and a second block of data associated with the first UE; transmit, to the network equipment via a first PUSCH transmission, the first block of data; and transmit, to the second UE, the second block of data for transmission to the network equipment via a second PUSCH transmission; transmit, to the second UE, the first block of data and the second block of data for transmission to the network equipment via a PUSCH transmission; transmit, to the network equipment via a first PUSCH transmission, the first block of data; determine whether a third PUSCH preparation time associated with at least one third UE of the group of UEs is less than the second PUSCH preparation time; and transmit, to the third UE and in response to the third PUSCH preparation time being less than the second PUSCH preparation time, the second block of data for transmission to the network equipment via a second PUSCH transmission; receive, from the second UE, an indication of presence of UL data in a buffer of the Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 30 second UE; transmit, to the network BSR associated with a buffer of the first UE that indicates a time window in which the first UE expects to store the UL data in the buffer; determine an absence of the UL data in the buffer of the first UE after expiry of the time window or determine a failure to store the UL data in the buffer of the first UE within the time window; and transmit, to the network equipment in response to determining the absence of the UL in the buffer of the first UE after expiry of the time window or the failure to store the UL data in the buffer of the first UE within the time window, an indication that cancels the BSR; determine that the UL data is expected to be in the buffer of the first UE by a predetermined time; and transmit the BSR in response to determining that the first UE expects to have the UL data in the buffer of the first UE by the predetermined time; transmit the BSR in response to receipt of the UL data from the second UE; transmit, to the network equipment, a BSR that indicates presence of UL data; and transmit, to the second UE, an indication of one or more resources of an UL grant for the second PUSCH transmission; transmit the indication of the one or more resources of the UL grant using a first available resource after transmission of the BSR to the network equipment.

[0143] In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to cause the UE 1000 to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004). For example, the processor 1002 may support wireless communication at the UE 1000 in accordance with examples as disclosed herein. The UE 1000 may be a first UE configured to or operable to support a means for receiving, from a second UE, a block of data if a first PUSCH preparation time associated with the first UE is less than a second PUSCH preparation time associated with the second UE, where the first UE and the second UE are part of a VUE; and transmitting, to a network equipment via a first PUSCH transmission, the first block of data.

[0144] Additionally, the UE 1000 may be configured to support any one or combination of receiving, from the second UE, the block of data via a D2D link; receiving, from the second UE, an indication of one or more resources of an UL grant to be used by the second UE; determining a set of resources based on the one or more resources of the UL grant; and transmitting, to the network equipment, the first block of data using the one or more resources; receiving, from the second UE, an indication of one or more resources of an UL grant to be used by the first UE; and transmitting, to the network equipment, the first block of data using the one or more of resources. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 31

[0145] Additionally, or alternatively, the may be a first UE and support at least one memory (e.g., the memory 1004) and at least one processor (e.g., the processor 1002) coupled with the at least one memory and configured to cause the UE to: receive, from a second UE, a block of data if a first PUSCH preparation time associated with the first UE is less than a second PUSCH preparation time associated with the second UE, where the first UE and the second UE are part of a VUE; and transmit, to a network equipment via a first PUSCH transmission, the first block of data.

[0146] Additionally, the UE 1000 may be configured to support any one or combination of the at least one processor is configured to receive, from the second UE, the block of data via a D2D link; receive, from the second UE, an indication of one or more resources of an UL grant to be used by the second UE; determine a set of resources based on the one or more resources of the UL grant; and transmit, to the network equipment, the first block of data using the determined set of resources; receive, from the second UE, an indication of one or more resources of an UL grant to be used by the first UE; and transmit, to the network equipment, the first block of data using the one or more of resources.

[0147] The controller 1006 may manage input and output signals for the UE 1000. The controller 1006 may also manage peripherals not integrated into the UE 1000. In some implementations, the controller 1006 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1006 may be implemented as part of the processor 1002.

[0148] In some implementations, the UE 1000 may include at least one transceiver 1008. In some other implementations, the UE 1000 may have more than one transceiver 1008. The transceiver 1008 may represent a wireless transceiver. The transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.

[0149] A receiver chain 1010 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1010 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 1010 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1010 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 32 transmission of the signal. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0150] A transmitter chain 1012 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1012 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase- shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1012 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1012 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0151] Figure 11 illustrates an example of a processor 1100 in accordance with aspects of the present disclosure. The processor 1100 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1100 may include a controller 1102 configured to perform various operations in accordance with examples as described herein. The processor 1100 may optionally include at least one memory 1104, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 1100 may optionally include one or more arithmetic-logic units (ALUs) 1106. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0152] The processor 1100 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1100) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others). Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 33

[0153] The controller 1102 may be to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. For example, the controller 1102 may operate as a control unit of the processor 1100, generating control signals that manage the operation of various components of the processor 1100. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0154] The controller 1102 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1104 and determine subsequent instruction(s) to be executed to cause the processor 1100 to support various operations in accordance with examples as described herein. The controller 1102 may be configured to track memory addresses of instructions associated with the memory 1104. The controller 1102 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1102 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1100 to cause the processor 1100 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1102 may be configured to manage flow of data within the processor 1100. The controller 1102 may be configured to control transfer of data between registers, ALUs 1106, and other functional units of the processor 1100.

[0155] The memory 1104 may include one or more caches (e.g., memory local to or included in the processor 1100 or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1104 may reside within or on a processor chipset (e.g., local to the processor 1100). In some other implementations, the memory 1104 may reside external to the processor chipset (e.g., remote to the processor 1100).

[0156] The memory 1104 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1100, cause the processor 1100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1102 and / or the processor 1100 may be configured to execute computer-readable instructions stored in the memory 1104 to cause Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 34 the processor 1100 to perform various example, the processor 1100 and / or the controller 1102 may be coupled with or to the memory 1104, the processor 1100, and the controller 1102, and may be configured to perform various functions described herein. In some examples, the processor 1100 may include multiple processors and the memory 1104 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0157] The one or more ALUs 1106 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1106 may reside within or on a processor chipset (e.g., the processor 1100). In some other implementations, the one or more ALUs 1106 may reside external to the processor chipset (e.g., the processor 1100). One or more ALUs 1106 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1106 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1106 may be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1106 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 1106 to handle conditional operations, comparisons, and bitwise operations.

[0158] The processor 1100 may support wireless communication in accordance with examples as disclosed herein. The processor 1100 may be configured to or operable to support at least one controller (e.g., the controller 1102) coupled with at least one memory (e.g., the memory 1104) and configured to cause the processor to: transmit an indication of a first PUSCH preparation time different than a second PUSCH preparation time associated with a group of UEs, where the group of UEs comprises a first UE that includes the processor and at least one second UE, and where the group of UEs are part of a VUE; and communicate with the at least one second UE for transmission of data to a network equipment.

[0159] Additionally, the processor 1100 may be configured to or operable to support any one or combination of the at least one controller is configured to cause the processor to communicate with the second UE via a D2D link to transmit the data to the network equipment; receive an indication Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 35 of a RNTI for the VUE; and monitor one or PDCCH candidates associated with the RNTI of the VUE for DCI scheduling the transmission of the data; receive, from the second UE, the data; and transmit, to the network equipment via one or more PUSCH transmissions, the data based at least in part on the first PUSCH preparation time; where the data comprises a first block of data and a second block of data associated with the first UE; transmit, to the network equipment via a first PUSCH transmission, the first block of data; and transmit, to the second UE, the second block of data for transmission to the network equipment via a second PUSCH transmission; transmit, to the second UE, the first block of data and the second block of data for transmission to the network equipment via a PUSCH transmission; transmit, to the network equipment via a first PUSCH transmission, the first block of data; determine whether a third PUSCH preparation time associated with at least one third UE of the group of UEs is less than the second PUSCH preparation time; and transmit, to the third UE and in response to the third PUSCH preparation time being less than the second PUSCH preparation time, the second block of data for transmission to the network equipment via a second PUSCH transmission; receive, from the second UE, an indication of presence of UL data in a buffer of the second UE; transmit, to the network equipment, a BSR associated with a buffer of the first UE that indicates a time window in which the first UE expects to store the UL data in the buffer; determine an absence of the UL data in the buffer of the first UE after expiry of the time window or determine a failure to store the UL data in the buffer of the first UE within the time window; and transmit, to the network equipment in response to determining the absence of the UL in the buffer of the first UE after expiry of the time window or the failure to store the UL data in the buffer of the first UE within the time window, an indication that cancels the BSR; determine that the UL data is expected to be in the buffer of the first UE by a particular predetermined time; and transmit the BSR in response to determining that the first UE expects to have the UL data in the buffer of the first UE by the predetermined time; transmit the BSR in response receipt of the UL data from the second UE; transmit, to the network equipment, a BSR that indicates presence of UL data; and transmit, to the second UE, an indication of one or more resources of an UL grant for the second PUSCH transmission; transmit the indication of the one or more resources of the UL grant using a first available resource after transmission of the BSR to the network equipment. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 36

[0160] The processor 1100 may support communication in accordance with examples as disclosed herein. The processor 1100 may be configured to or operable to support at least one controller (e.g., the controller 1102) coupled with at least one memory (e.g., the memory 1104) and configured to cause the processor to: receive, at a first UE that includes the processor and from a second UE, a block of data if a first PUSCH preparation time associated with the first UE is less than a second PUSCH preparation time associated with the second UE, where the first UE and the second UE are part of a VUE; and transmit, to a network equipment via a first PUSCH transmission, the first block of data.

[0161] Additionally, the processor 1100 may be configured to or operable to support any one or combination of the at least one controller is configured to cause the processor to receive, from the second UE, the block of data via a D2D link; receive, from the second UE, an indication of one or more resources of an UL grant to be used by the second UE; determine a set of resources based on the one or more resources of the UL grant; and transmit, to the network equipment, the first block of data using the one or more resources; receive, from the second UE, an indication of one or more resources of an UL grant to be used by the first UE; and transmit, to the network equipment, the first block of data using the one or more of resources.

[0162] Figure 12 illustrates an example of a NE 1200 in accordance with aspects of the present disclosure. The NE 1200 may include a processor 1202, a memory 1204, a controller 1206, and a transceiver 1208. The processor 1202, the memory 1204, the controller 1206, or the transceiver 1208, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0163] The processor 1202, the memory 1204, the controller 1206, or the transceiver 1208, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 37

[0164] The processor 1202 may include an hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1202 may be configured to operate the memory 1204. In some other implementations, the memory 1204 may be integrated into the processor 1202. The processor 1202 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the NE 1200 to perform various functions of the present disclosure.

[0165] The memory 1204 may include volatile or non-volatile memory. The memory 1204 may store computer-readable, computer-executable code including instructions when executed by the processor 1202 cause the NE 1200 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 1204 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0166] In some implementations, the processor 1202 and the memory 1204 coupled with the processor 1202 may be configured to cause the NE 1200 to perform one or more of the functions described herein (e.g., executing, by the processor 1202, instructions stored in the memory 1204). For example, the processor 1202 may support wireless communication at the NE 1200 in accordance with examples as disclosed herein.

[0167] The controller 1206 may manage input and output signals for the NE 1200. The controller 1206 may also manage peripherals not integrated into the NE 1200. In some implementations, the controller 1206 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1206 may be implemented as part of the processor 1202.

[0168] In some implementations, the NE 1200 may include at least one transceiver 1208. In some other implementations, the NE 1200 may have more than one transceiver 1208. The transceiver 1208 may represent a wireless transceiver. The transceiver 1208 may include one or more receiver chains 1210, one or more transmitter chains 1212, or a combination thereof. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 38

[0169] A receiver chain 1210 may be to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1210 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 1210 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1210 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1210 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0170] A transmitter chain 1212 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1212 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase- shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1212 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1212 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0171] Figure 13 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0172] At 1302, the method may include transmitting an indication of a first PUSCH preparation time different than a second PUSCH preparation time associated with a group of UEs, wherein the group of UEs comprises the first UE and at least one second UE, and wherein the group of UEs are part of a VUE. The operations of 1302 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by a UE as described with reference to Figure 10. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 39

[0173] At 1304, the method may include with the at least one second UE via a device-to-device link for transmission of data to a network equipment. The operations of 1304 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1304 may be performed by a UE as described with reference to Figure 10.

[0174] Figure 14 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0175] At 1402, the method may include receiving, from a second UE, a block of data if a first PUSCH preparation time associated with the first UE is less than a second PUSCH preparation time associated with the second UE, wherein the first UE and the second UE are part of a VUE. The operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a UE as described with reference to Figure 10.

[0176] At 1404, the method may include transmitting, to a network equipment via a first PUSCH transmission, the first block of data. The operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a UE as described with reference to Figure 10.

[0177] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0178] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0179] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 40 the examples and designs described herein but be accorded the broadest scope consistent with the principles and novel features disclosed herein. Attorney Ref. No. SMM920230169-WO-PCT

Claims

Lenovo Ref. No. SMM920230169-WO-PCT 41 What is claimed is:

1. A first user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first UE to: transmit an indication of a first physical uplink shared channel (PUSCH) preparation time different than a second PUSCH preparation time associated with a group of UEs, wherein the group of UEs comprises the first UE and at least one second UE, and wherein the group of UEs are part of a virtual UE (VUE); and communicate with the at least one second UE for transmission of data to a network equipment.

2. The first UE of claim 1, wherein the at least one processor is configured to cause the first UE to: communicate with the second UE via a device-to-device (D2D) link to transmit the data to the network equipment.

3. The first UE of claim 1, wherein the at least one processor is configured to cause the first UE to: receive an indication of a radio network temporary identifier (RNTI) for the VUE; and monitor one or more physical downlink control channel (PDCCH) candidates associated with the RNTI of the VUE for downlink control information (DCI) scheduling the transmission of the data.

4. The first UE of claim 1, wherein the at least one processor is configured to cause the first UE to: receive, from the second UE, the data; and transmit, to the network equipment via one or more PUSCH transmissions, the data based at least in part on the first PUSCH preparation time. Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 42 5. The first UE of claim 1, wherein the a first block of data and a second block of data associated with the first UE.

6. The first UE of claim 5, wherein the at least one processor is configured to cause the first UE to: transmit, to the network equipment via a first PUSCH transmission, the first block of data; and transmit, to the second UE, the second block of data for transmission to the network equipment via a second PUSCH transmission.

7. The first UE of claim 5, wherein the at least one processor is configured to cause the first UE to: transmit, to the second UE, the first block of data and the second block of data for transmission to the network equipment via a PUSCH transmission.

8. The first UE of claim 5, wherein the at least one processor is configured to cause the first UE to: transmit, to the network equipment via a first PUSCH transmission, the first block of data; determine whether a third PUSCH preparation time associated with at least one third UE of the group of UEs is less than the second PUSCH preparation time; and transmit, to the third UE and in response to the third PUSCH preparation time being less than the second PUSCH preparation time, the second block of data for transmission to the network equipment via a second PUSCH transmission.

9. The first UE of claim 1, wherein the at least one processor is configured to cause the first UE to: receive, from the second UE, an indication of presence of uplink (UL) data in a buffer of the second UE.

10. The first UE of claim 9, wherein the at least one processor is configured to cause the first UE to: Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 43 transmit, to the network equipment, a status report (BSR) associated with a buffer of the first UE that indicates a time window in which the first UE expects to store the UL data in the buffer.

11. The first UE of claim 10, wherein the at least one processor is configured to cause the first UE to: determine an absence of the UL data in the buffer of the first UE after expiry of the time window or determine a failure to store the UL data in the buffer of the first UE within the time window; and transmit, to the network equipment in response to determining the absence of the UL in the buffer of the first UE after expiry of the time window or the failure to store the UL data in the buffer of the first UE within the time window, an indication that cancels the BSR.

12. The first UE of claim 10, wherein the at least one processor is configured to cause the first UE to: determine that the UL data is expected to be in the buffer of the first UE by a predetermined time; and transmit the BSR in response to determining that the first UE expects to have the UL data in the buffer of the first UE by the predetermined time.

13. The first UE of claim 10, wherein the at least one processor is configured to cause the first UE to: transmit the BSR in response to receipt of the UL data from the second UE.

14. The first UE of claim 6, wherein the at least one processor is configured to cause the first UE to: transmit, to the network equipment, a buffer status report (BSR) that indicates presence of UL data; and transmit, to the second UE, an indication of one or more resources of an uplink (UL) grant for the second PUSCH transmission.

15. The first UE of claim 14, wherein the at least one processor is configured to cause the first UE to: Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 44 transmit the indication of the one or resources of the UL grant using a first available resource after transmission of the BSR to the network equipment.

16. A first user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first UE to: receive, from a second UE, a block of data if a first physical uplink shared channel (PUSCH) preparation time associated with the first UE is less than a second PUSCH preparation time associated with the second UE, wherein the first UE and the second UE are part of a virtual UE (VUE); and transmit, to a network equipment via a first PUSCH transmission, the first block of data.

17. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: transmit an indication of a first physical uplink shared channel (PUSCH) preparation time different than a second PUSCH preparation time associated with a group of UEs, wherein the group of UEs comprises a first user equipment (UE) that includes the processor and at least one second UE, and wherein the group of UEs are part of a virtual UE (VUE); and communicate with the at least one second UE for transmission of data to a network equipment.

18. The processor of claim 17, wherein the at least one controller is configured to cause the processor to: communicate with the second UE via a device-to-device (D2D) link to transmit the data to the network equipment.

19. The processor of claim 17, wherein the at least one controller is configured to cause the processor to: receive an indication of a radio network temporary identifier (RNTI) for the VUE; and Attorney Ref. No. SMM920230169-WO-PCTLenovo Ref. No. SMM920230169-WO-PCT 45 monitor one or more physical downlink channel (PDCCH) candidates associated with the RNTI of the VUE for downlink control information (DCI) scheduling the transmission of the data.

20. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, at a first user equipment (UE) that includes the processor and from a second UE, a block of data if a first physical uplink shared channel (PUSCH) preparation time associated with the first UE is less than a second PUSCH preparation time associated with the second UE, wherein the first UE and the second UE are part of a virtual UE (VUE); and transmit, to a network equipment via a first PUSCH transmission, the first block of data. Attorney Ref. No. SMM920230169-WO-PCT

Images