Method, device and system for scheduling downlink UE cooperative transmission

Abstract

Systems and methods for scheduling low layer transport block-based UE collaboration are provided. One or more PDCCHs are used to schedule downlink joint UE transmissions from a transmitter and involving a first UE (also referred to as a target UE) and a second UE (also referred to as a cooperative UE), or may also be referred to as UE cooperative (UC) transmissions. This may involve the transmission of a single PDCCH to the transmitter, or the transmission of a corresponding PDCCH to the transmitter and the second UE, respectively. The first UE receives the first TB based on the scheduling information in the PDCCH. The second UE receives a second TB as part of the joint / UC transmission. Various design schemes of downlink control information carrying scheduling information are provided.

Description

[0001] Cross-references to related applications

[0002] This application relates to and claims priority to U.S. Provisional Patent Application No. 63 / 520,012, filed August 16, 2023, entitled “METHOD, APPARATUS AND SYSTEM FOR SCHEDULING DOWNLINK UE COOPERATIONTRANSMISSION”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application generally relates to wireless communication, and more generally to a method, apparatus and system for scheduling cooperative transmission of user equipment (UE). Background Technology

[0004] In traditional wireless communication systems, each UE communicates independently with the base station. These systems can essentially be considered cell-centric. To improve direct communication between UEs, UE-to-UE communication has been researched and defined in the form of device-to-device (D2D) communication.

[0005] UE cooperation (UC) involves configuring a group of UEs to operate collaboratively to improve transmission and reception between the UE and the base station, as well as among the UEs themselves. Essentially, this can be viewed as a more UE-centric approach. UE cooperation can complement traditional cell-centric systems and improve the overall system performance and capacity. Summary of the Invention

[0006] Methods, apparatus, and systems for scheduling UE cooperation based on lower-layer transport blocks (PDCCHs) are provided. One or more PDCCHs are used to schedule UE cooperation (UC) transmissions involving a target UE and cooperating UEs. This may involve the transmission of a single PDCCH to the target UE, or the transmission of corresponding PDCCHs to the target UE and cooperating UEs separately. The target UE receives a first TB based on the scheduling information in the PDCCH. The cooperating UE receives a second TB as part of the UC transmission. Various design schemes for downlink control information carrying scheduling information are provided.

[0007] According to one aspect of the present disclosure, a method in a first user equipment (UE) is provided, the method comprising: receiving a first physical downlink control channel (PDCCH), the first PDCCH scheduling a downlink UE cooperation (UC) transmission for the first UE in a role of a target UE (TUE); receiving a first transport block (TB) based on the first PDCCH; receiving data from a second UE in a role of a cooperative UE (CUE) over an inter-UE connection.

[0008] In some implementations, receiving the first TB based on the first PDCCH comprises receiving the first TB from a network device.

[0009] In some implementations, receiving the first TB based on the first PDCCH comprises receiving the first TB from a third UE.

[0010] In some implementations, when the UC transmission is a TB duplicate UC transmission, the data is a duplicate of the first TB, or the data can be used to generate the first TB; when the UC transmission is a TB split UC transmission, the data is a second TB different from the first TB, or the data can be used to generate the second TB.

[0011] In some implementations, the first PDCCH comprises an indication of whether the UC transmission is a TB duplicate UC transmission or a TB split UC transmission.

[0012] In some implementations, the method further comprises receiving a higher layer signaling to indicate whether the UC transmission is a TB duplicate UC transmission or a TB split UC transmission.

[0013] In some implementations, the first PDCCH comprises scheduling information of only the first TB to indicate that a TB duplicate UC transmission is scheduled; or the first PDCCH comprises scheduling information of the first TB and a second TB to indicate that a TB split UC transmission is scheduled.

[0014] In some implementations, the first PDCCH comprises scheduling information of two TBs, in a case that the scheduling information of the two TBs is the same, a TB duplicate UC transmission is scheduled, and in a case that the scheduling information of the two TBs is different, a TB split UC transmission is scheduled.

[0015] In some implementations, the first PDCCH is scrambled using a first radio network temporary identifier (RNTI) to indicate the TB repetition UC transmission, and the first PDCCH is scrambled using a second RNTI to indicate the TB split UC transmission.

[0016] In some implementations, the method further includes receiving a second PDCCH, the second PDCCH scheduling a transmission of a normal downlink transmission to the first UE; wherein the first PDCCH is scrambled using a first radio network temporary identifier (RNTI) to indicate that the first PDCCH schedules the downlink UC transmission, and the second PDCCH is scrambled using a second RNTI to indicate that the second PDCCH schedules the normal downlink transmission to the first UE.

[0017] In some implementations, for the TB repetition UC transmission, the first PDCCH includes a new data indicator (NDI), the NDI indicating whether a new transmission or a retransmission is scheduled.

[0018] In some implementations, for the TB split UC transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI), the first NDI indicating whether a new transmission or a retransmission is scheduled for the transmission to the first UE, and the second NDI indicating whether a new transmission or a retransmission is scheduled for the transmission to the second UE in a CUE role.

[0019] According to another aspect of the present disclosure, there is provided an apparatus in a user equipment (UE), the apparatus comprising at least one processor coupled with a memory storing instructions that, when executed by the at least one processor, cause the UE to perform a method, the method comprising: receiving a first physical downlink control channel (PDCCH), the first PDCCH scheduling a downlink UE cooperation (UC) transmission for the UE in a target UE (TUE) role; receiving a first transport block (TB) based on the PDCCH; receiving data from a second UE in a cooperative UE (CUE) role over an inter-UE connection.

[0020] In some implementations, receiving a first transport block (TB) based on a first PDCCH includes receiving the first TB from a network device.

[0021] In some implementations, receiving a first transport block (TB) based on a first PDCCH includes receiving the first TB from a third UE.

[0022] In some implementations, when the UC transmission is a TB-repeated UC transmission, the data is a copy of the first TB, or the data can be used to generate the first TB; when the UC transmission is a TB-segmented UC transmission, the data is a second TB different from the first TB, or the data can be used to generate the second TB.

[0023] In some implementations, the first PDCCH includes an indication of whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0024] In some implementations, the apparatus of the method further includes receiving higher-layer signaling to indicate whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0025] In some implementations, the first PDCCH includes only the scheduling information of the first TB to indicate that the scheduled TB repeated UC transmission is being performed; the first PDCCH includes the scheduling information of the first TB and the second TB to indicate that the scheduled TB segmented UC transmission is being performed.

[0026] In some implementations, the first PDCCH includes scheduling information for two TBs. When the scheduling information for the two TBs is the same, the TB repeat UC transmission is scheduled. When the scheduling information for the two TBs is different, the TB segmented UC transmission is scheduled.

[0027] In some implementations, the first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the TB repeats the UC transmission, and the first PDCCH is scrambled with a second RNTI to indicate that the TB segments the UC transmission.

[0028] In some implementations, the apparatus of the method further includes: receiving a second PDCCH, the second PDCCH scheduling a normal downlink transmission to the first UE; the first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the first PDCCH schedules downlink UC transmission, and the second PDCCH is scrambled with a second RNTI to indicate that the second PDCCH schedules a normal downlink transmission to the first UE.

[0029] In some implementations, for TB repeated UC transmissions, the first PDCCH includes a new data indicator (NDI), which indicates whether a new transmission or a retransmission is scheduled.

[0030] In some implementations, for TB-segmented UC transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI). The first NDI indicates whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicates whether the transmission to the second UE, which is in the CUE role, is scheduled as a new transmission or a retransmission.

[0031] According to another aspect of this disclosure, a method in a network device is provided, the method comprising: transmitting a first physical downlink control channel (PDCCH), the first PDCCH scheduling downlink UE cooperation (UC) transmission for a first UE in the role of a target UE (TUE); transmitting a first TB to the first UE based on scheduling information in the PDCCH; and transmitting a second TB to a second UE in the role of a cooperative UE (CUE).

[0032] In some implementations, when the UC transmission is a TB-repeated UC transmission, the second TB is a copy of the first TB; when the UC transmission is a TB-segmented UC transmission, the second TB is different from the first TB.

[0033] In some implementations, the first PDCCH includes an indication of whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0034] In some implementations, the method further includes sending higher-layer signaling to indicate whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0035] In some implementations, the first PDCCH includes only the scheduling information of the first TB to indicate that the scheduled TB repeated UC transmission is being performed; the first PDCCH includes the scheduling information of the first TB and the second TB to indicate that the scheduled TB segmented UC transmission is being performed.

[0036] In some implementations, the first PDCCH includes scheduling information for two TBs. When the scheduling information for the two TBs is the same, the TB duplicate UC transmission is scheduled. When the scheduling information for the two TBs is different, the TB split UC transmission is scheduled.

[0037] In some implementations, the first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the TB repeats the UC transmission, and the first PDCCH is scrambled with a second RNTI to indicate that the TB segments the UC transmission.

[0038] In some implementations, the method further includes: sending a second PDCCH, the second PDCCH scheduling the transmission of normal downlink UE transmission; wherein the first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the first PDCCH schedules downlink UC transmission to the first UE, and the second PDCCH is scrambled with a second RNTI to indicate that the second PDCCH schedules normal downlink UE transmission to the first UE.

[0039] In some implementations, for TB repeated UC transmissions, the first PDCCH includes a new data indicator (NDI), which indicates whether a new transmission or a retransmission is scheduled.

[0040] In some implementations, for TB-segmented UC transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI). The first NDI indicates whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicates whether the transmission to the second UE, which is in the CUE role, is scheduled as a new transmission or a retransmission.

[0041] According to another aspect of this disclosure, an apparatus in a network device is provided, the apparatus including at least one processor coupled to a memory storing instructions, the instructions causing the network device to perform a method when executed by the at least one processor, the method comprising: transmitting a first physical downlink control channel (PDCCH), the first PDCCH scheduling downlink UE cooperation (UC) transmission for a first UE in the role of a target UE (TUE); transmitting a first transport block (TB) to the first UE based on the first PDCCH; and transmitting a second TB to a second UE in the role of a cooperative UE (CUE).

[0042] In some implementations, when the UC transmission is a repeat of the UC transmission in a transport block (TB), the second TB is a copy of the first TB; when the UC transmission is a segmented UC transmission in a transport block (TB), the second TB is different from the first TB.

[0043] In some implementations, the first PDCCH includes an indication of whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0044] In some implementations, the network device also includes sending higher-layer signaling to indicate whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0045] In some implementations, the first PDCCH includes only the scheduling information of the first TB to indicate that the scheduled TB repeated UC transmission is being performed; the first PDCCH includes the scheduling information of the first TB and the second TB to indicate that the scheduled TB segmented UC transmission is being performed.

[0046] In some implementations, the first PDCCH includes scheduling information for two TBs. When the scheduling information for the two TBs is the same, the TB duplicate UC transmission is scheduled. When the scheduling information for the two TBs is different, the TB split UC transmission is scheduled.

[0047] In some implementations, the first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the TB repeats the UC transmission, and the first PDCCH is scrambled with a second RNTI to indicate that the TB segments the UC transmission.

[0048] In some implementations, the network device further includes: sending a second PDCCH, the second PDCCH scheduling normal downlink UE transmissions; the first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the first PDCCH schedules downlink UC transmissions to the first UE, and the second PDCCH is scrambled with a second RNTI to indicate that the second PDCCH schedules normal downlink UE transmissions to the first UE.

[0049] In some implementations, for TB repeated UC transmissions, the first PDCCH includes a new data indicator (NDI), which indicates whether a new transmission or a retransmission is scheduled.

[0050] In some implementations, for TB-segmented UC transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI). The first NDI indicates whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicates whether the transmission to the second UE, which is in the CUE role, is scheduled as a new transmission or a retransmission.

[0051] According to another aspect of this disclosure, a method in a first UE involves: receiving a first PDCCH, the first PDCCH scheduling downlink joint UE transmissions from a transmitter for the first UE; receiving a first TB from the transmitter based on the first PDCCH; and receiving data from a second UE via an inter-UE connection.

[0052] In some implementations, the transmitter is a network device, and receiving the first TB based on the first PDCCH involves receiving the first TB from the network device.

[0053] In some implementations, the transmitter is a third UE, and receiving the first TB based on the first PDCCH involves receiving the first TB from the third UE.

[0054] In some implementations, when the combined UE transmission is a TB repeated combined UE transmission, the data is a copy of the first TB, or the data can be used to generate the first TB.

[0055] In some implementations, when the joint UE transmission is a TB-segmented joint UE transmission, the data is a second TB that is different from the first TB, or the data can be used to generate the second TB.

[0056] In some implementations, the first PDCCH includes an indication of whether the combined UE transmission is a TB repeated combined UE transmission or a TB segmented combined UE transmission.

[0057] In some implementations, the method also involves receiving higher-layer signaling to indicate whether the combined UE transmission is a TB repeated combined UE transmission or a TB segmented combined UE transmission.

[0058] In some implementations, the first PDCCH includes only the scheduling information of the first TB to indicate that the scheduled TB repeat joint UE transmission is being performed; or the first PDCCH includes the scheduling information of the first TB and the second TB to indicate that the scheduled TB segment joint UE transmission is being performed.

[0059] In some implementations, the first PDCCH includes scheduling information for two TBs. When the scheduling information for the two TBs is the same, the TB is repeated and the UE is transmitted together. When the scheduling information for the two TBs is different, the TB is split and the UE is transmitted together.

[0060] In some implementations, the first PDCCH is scrambled using the first RNTI to indicate that the TB repeats the joint UE transmission, and the first PDCCH is scrambled using the second RNTI to indicate that the TB divides the joint UE transmission.

[0061] In some implementations, the method also involves: receiving a second PDCCH, the second PDCCH scheduling a normal downlink transmission to the first UE, in which case the first PDCCH can be scrambled using a first RNTI to indicate that the first PDCCH schedules a downlink transmission to the joint UE, and the second PDCCH can be scrambled using a second RNTI to indicate that the second PDCCH schedules a normal downlink transmission to the first UE.

[0062] In some implementations, for TB repeated joint UE transmission, the first PDCCH includes NDI, which indicates whether a new transmission or a retransmission is scheduled.

[0063] In some implementations, for TB segmented joint UE transmission, the first PDCCH includes a first NDI and a second NDI. The first NDI indicates whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicates whether the transmission to the second UE is scheduled as a new transmission or a retransmission.

[0064] According to another aspect of this disclosure, an apparatus includes at least one processor coupled to a memory storing instructions, the instructions causing a UE to perform a method when executed by the at least one processor. The method relates to: receiving a first PDCCH, the first PDCCH scheduling downlink joint UE transmissions from a transmitter for the UE; receiving a first TB from the transmitter based on the first PDCCH; and receiving data from a second UE via an inter-UE connection.

[0065] In some implementations, the transmitter is a network device, and receiving the first TB based on the first PDCCH involves receiving the first TB from the network device.

[0066] In some implementations, the transmitter is a third UE, and receiving the first TB based on the first PDCCH involves receiving the first TB from the third UE.

[0067] In some implementations, when the combined UE transmission is a TB repeated combined UE transmission, the data is a copy of the first TB, or the data can be used to generate the first TB.

[0068] In some implementations, when the joint UE transmission is a TB-segmented joint UE transmission, the data is a second TB that is different from the first TB, or the data can be used to generate the second TB.

[0069] In some implementations, the first PDCCH includes an indication of whether the combined UE transmission is a TB repeated combined UE transmission or a TB segmented combined UE transmission.

[0070] In some implementations, the method also involves receiving higher-layer signaling to indicate whether the combined UE transmission is a TB repeated combined UE transmission or a TB segmented combined UE transmission.

[0071] In some implementations, the first PDCCH includes only the scheduling information of the first TB to indicate that the scheduled TB repeat joint UE transmission is being performed; or the first PDCCH includes the scheduling information of the first TB and the second TB to indicate that the scheduled TB segment joint UE transmission is being performed.

[0072] In some implementations, the first PDCCH includes scheduling information for two TBs. When the scheduling information for the two TBs is the same, the TB is repeated and the UE is transmitted together. When the scheduling information for the two TBs is different, the TB is split and the UE is transmitted together.

[0073] In some implementations, the first PDCCH is scrambled using the first RNTI to indicate that the TB repeats the joint UE transmission, and the first PDCCH is scrambled using the second RNTI to indicate that the TB divides the joint UE transmission.

[0074] In some implementations, the method also involves: receiving a second PDCCH, the second PDCCH scheduling a normal downlink transmission to the UE, in which case the first PDCCH can be scrambled using a first RNTI to indicate that the first PDCCH schedules a transmission to the UE, and the second PDCCH can be scrambled using a second RNTI to indicate that the second PDCCH schedules a normal downlink transmission to the UE.

[0075] In some implementations, for TB repeated joint UE transmission, the first PDCCH includes NDI, which indicates whether a new transmission or a retransmission is scheduled.

[0076] In some implementations, for TB segmented joint UE transmission, the first PDCCH includes a first NDI and a second NDI. The first NDI indicates whether the transmission to the UE is scheduled as a new transmission or a retransmission, and the second NDI indicates whether the transmission to the second UE is scheduled as a new transmission or a retransmission.

[0077] Another aspect of this disclosure relates to a method comprising: transmitting a first PDCCH, the first PDCCH scheduling downlink joint UE transmission from a transmitter for a first UE; transmitting a first TB of data from the transmitter to the first UE based on scheduling information in the first PDCCH; and transmitting a second TB of data from the transmitter to a second UE.

[0078] In some implementations, when the combined UE transmission is a TB repeated combined UE transmission, the second TB is a copy of the first TB.

[0079] In some implementations, when the combined UE transmission is a TB-segmented combined UE transmission, the second TB is different from the first TB.

[0080] In some implementations, the first PDCCH includes an indication of whether the combined UE transmission is a TB repeated combined UE transmission or a TB segmented combined UE transmission.

[0081] In some implementations, the method also involves sending higher-layer signaling to indicate whether the combined UE transmission is a TB repeated combined UE transmission or a TB segmented combined UE transmission.

[0082] In some implementations, the first PDCCH includes only the scheduling information of the first TB to indicate that the scheduled TB repeat joint UE transmission is being scheduled, or the first PDCCH includes the scheduling information of the first TB and the second TB to indicate that the scheduled TB segment joint UE transmission is being scheduled.

[0083] In some implementations, the first PDCCH includes scheduling information for two TBs. When the scheduling information for the two TBs is the same, the transmission of the duplicate TBs combined with the UE is scheduled. When the scheduling information for the two TBs is different, the transmission of the segmented TBs combined with the UE is scheduled.

[0084] In some implementations, the first PDCCH is scrambled using the first RNTI to indicate that the TB repeats the joint UE transmission, and the first PDCCH is scrambled using the second RNTI to indicate that the TB divides the joint UE transmission.

[0085] In some implementations, the method also involves: sending a second PDCCH, the second PDCCH scheduling the transmission of normal downlink UE transmission, in which case the first PDCCH can be scrambled using a first RNTI to indicate that the first PDCCH schedules joint UE transmission, and the second PDCCH can be scrambled using a second RNTI to indicate that the second PDCCH schedules normal UE transmission.

[0086] In some implementations, for TB repeated joint UE transmission, the first PDCCH includes NDI, which indicates whether a new transmission or a retransmission is scheduled.

[0087] In some implementations, for TB segmented joint UE transmission, the first PDCCH includes a first NDI and a second NDI. The first NDI indicates whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicates whether the transmission to the second UE is scheduled as a new transmission or a retransmission.

[0088] According to another aspect of this disclosure, an apparatus includes at least one processor coupled to a memory storing instructions, the instructions causing a transmitter to perform a method when executed by the at least one processor. The method may involve: transmitting a first PDCCH, the first PDCCH scheduling joint UE transmission from the transmitter for a first UE; transmitting a first TB of data from the transmitter to the first UE based on the first PDCCH; and transmitting a second TB of data to a second UE.

[0089] In some implementations, when the combined UE transmission is a TB repeated combined UE transmission, the second TB is a copy of the first TB.

[0090] In some implementations, when the combined UE transmission is a TB-segmented combined UE transmission, the second TB is different from the first TB.

[0091] In some implementations, the first PDCCH includes an indication of whether the combined UE transmission is a TB repeated combined UE transmission or a TB segmented combined UE transmission.

[0092] In some implementations, the method also involves sending higher-layer signaling to indicate whether the combined UE transmission is a TB repeated combined UE transmission or a TB segmented combined UE transmission.

[0093] In some implementations, the first PDCCH includes only the scheduling information of the first TB to indicate that the scheduled TB repeat joint UE transmission is being scheduled, or the first PDCCH includes the scheduling information of the first TB and the second TB to indicate that the scheduled TB segment joint UE transmission is being scheduled.

[0094] In some implementations, the first PDCCH includes scheduling information for two TBs. When the scheduling information for the two TBs is the same, the transmission of the duplicate TBs combined with the UE is scheduled. When the scheduling information for the two TBs is different, the transmission of the segmented TBs combined with the UE is scheduled.

[0095] In some implementations, the first PDCCH is scrambled using the first RNTI to indicate that the TB repeats the joint UE transmission, and the first PDCCH is scrambled using the second RNTI to indicate that the TB divides the joint UE transmission.

[0096] In some implementations, the method also involves: sending a second PDCCH, the second PDCCH scheduling the transmission of normal downlink UE transmission, in which case the first PDCCH can be scrambled using a first RNTI to indicate that the first PDCCH schedules joint UE transmission, and the second PDCCH can be scrambled using a second RNTI to indicate that the second PDCCH schedules normal downlink UE transmission.

[0097] In some implementations, for TB repeated joint UE transmission, the first PDCCH includes NDI, which indicates whether a new transmission or a retransmission is scheduled.

[0098] In some implementations, for TB segmented joint UE transmission, the first PDCCH includes a first NDI and a second NDI. The first NDI indicates whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicates whether the transmission to the second UE is scheduled as a new transmission or a retransmission.

[0099] According to one aspect of this disclosure, a communication system is provided, including means in a TUE as shown above and means in a network terminal as shown above. Additionally, the system includes at least one CUE.

[0100] The system can also be described as including a first UE or means for causing such a UE to perform a method, at least one second UE or means for causing such a UE to perform a method, and a transmitter or means for causing the transmitter to perform a method.

[0101] According to one aspect of this disclosure, a computer program including instructions is provided. When executed by a processor, the instructions cause the processor to implement the methods described in any of the foregoing aspects or implementations.

[0102] According to one aspect of this disclosure, a non-transitory computer-readable medium is provided that stores instructions which, when executed by a processor, cause the processor to implement the methods described in any of the foregoing aspects or implementations. Attached Figure Description

[0103] Embodiments of this disclosure are described below with reference to the accompanying drawings, in which:

[0104] Figure 1 This is a block diagram of a communication system.

[0105] Figure 2 This is a block diagram of a communication system.

[0106] Figure 3 A block diagram illustrating the basic component structure of a communication system, including electronic devices (EDs) and base stations.

[0107] Figure 4 This is a block diagram of a module that can be used to implement or perform one or more steps of the embodiments of this application.

[0108] Figure 5A , 5B Figure 5C illustrates a block diagram for joint scheduling for user equipment cooperation (UC).

[0109] Figure 6 This is a block diagram illustrating bit-level scrambling and physical downlink control channel (PDCCH) cyclic redundancy check (CRC) scrambling.

[0110] Figure 7 A block diagram illustrating two types of data transmission is provided.

[0111] Figure 8A To illustrate the first type of user equipment cooperation (UC) based on transport block (TB), this cooperation is referred to as segmented TB UC data transmission.

[0112] Figure 8B A block diagram is shown to illustrate a second type of TB-based UC, referred to as TB-repeated UC data transmission.

[0113] Figure 9A This is a block diagram illustrating the use of higher-level signaling to instruct TB to segment UC data transmission.

[0114] Figure 9B This is a block diagram illustrating the use of higher-level signaling to instruct TB to repeat UC data transmission.

[0115] Figure 10 A block diagram of an example of a common PDCCH carrying common downlink control information (DCI) for scheduling two transport blocks (2TB).

[0116] Figure 11 A block diagram showing examples of separate PDCCHs for target user equipment (TUE) and cooperative user equipment (CUE).

[0117] Figure 12 This is an example flowchart of a method performed by a UE that is used as a TUE, characterized by TB repetition.

[0118] Figure 13 This is an example flowchart of a method executed by a UE that is used as a TUE, characterized by TB segmentation.

[0119] Figure 14 This is an example flowchart of the method executed by the UE used as CUE.

[0120] Figure 15This is a block diagram illustrating data transmission between UEs using TB buffers and ring block buffers in the PHY layer of TUE and CUE.

[0121] Figure 16 This is a block diagram illustrating the hybrid automatic repeat request (HARQ) control at the TUE MAC layer.

[0122] Figure 17 This is a block diagram illustrating HARQ control in the CUE MAC layer.

[0123] Figure 18 A block diagram illustrating an example of data / signaling flow in a UC using the TB repetition method.

[0124] Figure 19 A block diagram illustrating an example of UC's data / signaling flow using the TB segmentation method.

[0125] Figure 20 This is a block diagram illustrating code block group (CBG) based retransmission for UC.

[0126] Figure 21 A block diagram illustrating HARQ configuration that supports both UC and non-UC data traffic is provided. Detailed Implementation

[0127] UE cooperation is a new topic in 3GPP. In Rel-18, UE cooperation is studied and specified under the themes of multipath support and UE aggregation. The main objective is to improve downlink (DL) throughput and reliability by increasing the number of transmission paths between the base station and the target UE (or destination UE).

[0128] 3GPP refers to the 3rd Generation Partnership Project.

[0129] In the systems studied in 3GPP Rel-18, data segmentation / repeating is performed at the Packet Data Control Protocol (PDCP) layer as part of the UE cooperation approach. This approach may not fully utilize dynamic channel variations.

[0130] Compared to PDCP layer data segmentation / duplication, UE cooperation (UC) at lower protocol layers can be used to further improve performance such as throughput and latency. For example, transport block (TB) based UC may be better suited to take advantage of dynamic channel variations and maximize performance. Systems and methods for scheduling TB-based UC are provided. In future generations of wireless communication (e.g., 5.5G or future networks), a large number of devices (mobile phones / devices, Internet of Things (IoT) devices, cooperative UEs (CUEs), industrial sensors / monitors, etc.) can be deployed.

[0131] 5.5G refers to the 5.5th generation. More generally, a number followed by a "G" indicates the generation of a wireless communication system.

[0132] UE collaboration can be used to meet requirements such as low power consumption, long battery life, limited capabilities, and enhanced capabilities / coverage. More specifically, data originating from / to a device (source device / target device) can be sent / received by a group of collaborating devices.

[0133] Connections between UEs used for UC purposes may not necessarily be specified by 3GPP and can be achieved through non-3GPP connections that include wired or wireless connections.

[0134] Joint scheduling can be used to facilitate UC transmission / reception. For uplink transmissions, joint scheduling can include scheduling information for multiple packets (or identical duplicate packets) initiated by the source device (SUE) to be sent from multiple cooperating devices (CUEs) and the source device itself to the network in the uplink or to another device via a side link. For downlink transmissions, joint scheduling can include scheduling information for multiple packets (or identical duplicate packets) to be sent directly from the source device or network (e.g., gNB) to the destination device (TUE) and to multiple cooperating devices, where the packets are destined for the destination device.

[0135] In either case, the scheduling information for each data packet may include one or more parameters, such as resource allocation (RA), modulation and coding scheme (MCS), HARQID, redundancy version (RV), etc. Joint scheduling can work in conjunction with independent scheduling (per UC transmission or per non-UC transmission).

[0136] The scenarios described here typically focus on downlink UC transmission and reception, but the methods provided can be applied to uplink, sidelink, and downlink transmissions. Therefore, for example, as...Figure 5A The data transmissions shown can be uplink or downlink. Uplink data transmission can be carried in the Physical Uplink Shared Channel (PUSCH), while downlink data transmission can be carried in the Physical Downlink Shared Channel (PDSCH) of the 3GPP New Radio (NR) standard (also known as the 5G standard). Most of the mechanisms provided in this document are applicable to both uplink and downlink unless explicitly stated otherwise.

[0137] For example, for downlink UC transmission, joint scheduling can include scheduling information for transmitting multiple data packets (or identical duplicate data packets) from a source next-generation (or 5G) base station (gNB) (or source network equipment) to corresponding devices including a destination device (or destination / target UE, or target UE, TUE)) and cooperating devices. The cooperating devices can relay the data packets to the TUE.

[0138] refer to Figure 1 As a non-limiting illustrative example, a simplified schematic diagram of a communication system is provided. Communication system 100 includes a radio access network 120. Radio access network 120 may be a next-generation radio access network or a traditional (e.g., 5G, 4G, 3G, or 2G) radio access network. One or more electric devices (EDs) 110a to 110j (collectively referred to as 110) may be interconnected with each other or connected to one or more network nodes (170a, 170b, collectively referred to as 170) in radio access network 120. Core network 130 may be part of the communication system and may depend on or be independent of the radio access technology used in communication system 100. Furthermore, communication system 100 includes a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0139] Figure 2An example communication system 100 is illustrated. Generally, communication system 100 enables multiple wireless or wired components to transmit data and other content. The purpose of communication system 100 may be to provide content such as voice, data, video, and / or text via broadcast, multicast, and unicast. Communication system 100 can operate by sharing resources (e.g., carrier spectrum bandwidth) among its constituent components. Communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. Communication system 100 can provide a wide variety of communication services and applications (such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery, and mobility). Communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can form a heterogeneous network that can be considered as comprising multiple layers. Compared to traditional communication networks, heterogeneous networks can achieve better overall performance through efficient multi-link joint operation between terrestrial and non-terrestrial networks, more flexible function sharing, and faster physical layer link switching.

[0140] Terrestrial and non-terrestrial communication systems can be considered as subsystems of a communication system. In the example shown, communication system 100 includes electronic devices (EDs) 110a to 110d (collectively referred to as ED 110), radio access networks (RANs) 120a and 120b, a non-terrestrial communication network 120c, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. RANs 120a and 120b include corresponding base stations (BSs) 170a and 170b, which are generally referred to as terrestrial transmit / receive points (TRPs) 170a and 170b. The non-terrestrial communication network 120c includes access nodes 120c, which are generally referred to as non-terrestrial transmit and receive points (NT-TRPs) 172.

[0141] Any ED 110 can also be alternatively or additionally configured to connect, access, or communicate with any other T-TRP 170a and 170b, NT-TRP 172, Internet 150, core network 130, PSTN 140, other network 160, or any combination thereof. In some examples, ED 110a can communicate uplink and / or downlink with T-TRP 170a via interface 190a. In some examples, ED 110a, 110b, and 110d can also communicate directly with each other via one or more sidelink air interfaces 190b. In some examples, ED 110d can communicate uplink and / or downlink with NT-TRP 172 via interface 190c.

[0142] Air interfaces 190a and 190b can use similar communication technologies, such as any suitable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA). Air interfaces 190a and 190b can utilize other high-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.

[0143] The air interface 190c enables communication between the ED 110d and one or more NT-TRP 172s via a wireless link or simply via a link. In some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection for multicast transmission between a group of EDs and one or more NT-TRPs.

[0144] RANs 120a and 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 120b and / or core network 130 can communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by core network 130, and may or may not use the same radio access technology as RANs 120a, RAN 120b, or both. Core network 130 can also serve as a gateway access between (i) RANs 120a and 120b or EDs 110a, 110b, and 110c, or both RANs and EDs, and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Additionally, some or all of EDs 110a, 110b, and 110c may include the ability to communicate with different wireless networks via different radio links using different radio technologies and / or protocols. Instead of wireless communication (or other methods), ED 110a, 110b, and 110c can communicate with service providers or exchanges (not shown) via wired communication channels and with the Internet 150. PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a network of computers and subnets (intranets) or both, and incorporate protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating under various wireless access technologies and may incorporate multiple transceivers required to support such operation.

[0145] Figure 3Another example of the ED 110 and base stations 170a, 170b, and / or 170c is shown. The ED 110 is used to connect people, objects, machines, etc. The ED 110 can be widely used in various scenarios, such as cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, and mobility, etc.

[0146] Each ED 110 represents any suitable end-user equipment used for wireless operation and may include (or be referred to as) devices such as user equipment / device (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics device, smart book, vehicle, automobile, truck, bus, train, or IoT device, industrial equipment, or devices within the aforementioned equipment (e.g., communication module, modem, or chip). Future generations of ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs and will be referred to hereinafter as T-TRP 170. Also... Figure 3 As shown, NT-TRP is referred to below as NT-TRP 172. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically enabled (i.e., established, activated, or enabled), disabled (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connectivity availability and connectivity necessity.

[0147] ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown in the figure. One, some, or all of the antennas may alternatively be panels. The transmitter 201 and receiver 203 may, for example, be integrated as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver is also used to demodulate data or other content received through at least one antenna 204. Each transceiver includes any suitable structure to generate signals for wireless or wired transmission and / or process signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure to transmit and / or receive wireless or wired signals.

[0148] ED 110 may also include at least one memory 208. Memory 208 stores instructions and data used, generated, or acquired by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein, which are executed by processing unit 210. Each memory 208 includes any suitable volatile and / or non-volatile storage and retrieval device. Any suitable type of memory can be used, such as random-access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, and on-processor cache, etc.

[0149] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., connected to...). Figure 1 (Wired interface of Internet 150 in the network). Input / output devices support interaction with users or other devices on the network. Each input / output device includes any suitable structure for providing or receiving information from the user, such as a speaker, microphone, keypad, keyboard, display, or touchscreen, including network interface communication.

[0150] ED 110 also includes a processor 210 for performing various operations, including operations related to preparing for uplink transmissions to NT-TRP 172 and / or T-TRP 170, operations related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170, and operations related to processing lateral link transmissions to and from another ED 110. Processing operations related to preparing for uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. According to an embodiment, receiver 203 may receive downlink transmissions, possibly using receive beamforming, and processor 210 may extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). Examples of signaling may be reference signals transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction indications (e.g., beam angle information (BAI)) received from T-TRP 170. In some embodiments, processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and obtaining system information. In some embodiments, processor 210 may perform channel estimation, for example, using reference signals received from NT-TRP 172 and / or T-TRP 170.

[0151] Although not shown, processor 210 may be part of transmitter 201 and / or receiver 203. Although not shown, memory 208 may be part of processor 210.

[0152] The processor 210 and the processing components of the transmitter 201 and receiver 203 may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 208). Alternatively, some or all of the processing components of the processor 210 and the transmitter 201 and receiver 203 may be implemented using special-purpose circuitry such as a field-programmable gate array (FPGA), a graphics processing unit (GPU), or an application-specific integrated circuit (ASIC).

[0153] In some implementations, the T-TRP 170 may have other names, such as base station, basetransceiver station (BTS), wireless base station, network node, network device, network end device, transmit / receive node, NodeB, evolved NodeB (eNodeB or eNB), home eNodeB, next-generation NodeB (gNB), transmission point (TP), site controller, access point (AP) or wireless router, relay station, remote radio head, ground node, ground network device or ground base station, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distribution unit (DU), location node, etc. The T-TRP 170 can be a macro BS, micro BS, relay node, host node, or a combination thereof. T-TRP 170 may refer to the aforementioned equipment or a device within the aforementioned equipment (e.g., a communication module, modem, or chip).

[0154] In some implementations, the various parts of T-TRP 170 can be distributed. For example, some modules of T-TRP 170 may be located remotely from the device housing the antenna of T-TRP 170 and may be coupled to the device housing the antenna via a communication link sometimes referred to as a fronthaul (not shown), such as a Common Public Radio Interface (CPRI). Therefore, in some embodiments, the term T-TRP 170 may also refer to network-side modules performing processing operations such as ED 110 location determination, resource allocation (scheduling), message generation, and encoding / decoding, which are not necessarily part of the device housing the antenna of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs that operate together, for example, through coordinated multicast transmissions to serve ED 110.

[0155] T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figure. One, some, or all of the antennas may alternatively be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. T-TRP 170 also includes a processor 260 for performing various operations, including operations related to: preparing a transmission for downlink transmission to ED 110, processing uplink transmissions received from ED 110, preparing a transmission for backhaul transmission to NT-TRP 172, and processing transmissions received from NT-TRP 172 via backhaul. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via backhaul may include operations such as receive beamforming, demodulation, and decoding of received symbols. Processor 260 can also perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating the contents of synchronization signal blocks (SSBs), generating system information, etc. In some embodiments, processor 260 also generates beam direction indications, such as BAI, which can be scheduled for transmission by scheduler 253. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110, determining the deployment location of NT-TRP 172, etc. In some embodiments, processor 260 can generate signaling, for example, to configure one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252. Note that the term "signaling" as used herein may also be referred to as control signaling. Dynamic signaling can be transmitted in control channels such as the physical downlink control channel (PDCCH), while static or semi-static higher-layer signaling can be included in data packets transmitted in data channels such as the physical downlink shared channel (PDSCH).

[0156] Scheduler 253 may be coupled to processor 260. Scheduler 253 may be included within or operate separately from T-TRP 170, and may schedule uplink, downlink, and / or backhaul transmissions, including issuing scheduling grants and / or configuring schedule-free (“configuration grants”) resources. T-TRP 170 also includes memory 258 for storing information and data. Memory 258 stores instructions and data used, generated, or acquired by T-TRP 170. For example, memory 258 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein, which are executed by processor 260.

[0157] Although not shown, processor 260 may form part of transmitter 252 and / or receiver 254. Furthermore, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may form part of processor 260.

[0158] The processor 260, scheduler 253, and processing components of transmitter 252 and receiver 254 may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processor 260, scheduler 253, and processing components of transmitter 252 and receiver 254 may be implemented using dedicated circuitry such as FPGA, GPU, or ASIC.

[0159] Although the NT-TRP 172 is shown as a drone only as an example, the NT-TRP 172 can be implemented in any suitable non-terrestrial form. Furthermore, in some implementations, the NT-TRP 172 may have other names, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is shown in the figure. One, some, or all of the antennas may alternatively be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 also includes a processor 276 for performing various operations, including operations related to: preparing transmissions for downlink transmission to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmission to T-TRP 170, and processing transmissions received from T-TRP 170 via backhaul. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via backhaul may include operations such as receive beamforming, demodulation, and decoding of received symbols. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, for example, to configure one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-level functions such as medium access control (MAC) or radio link control (RLC) layer functions. Since this is only an example, NT-TRP 172 may more generally implement higher-level functions in addition to physical layer processing.

[0160] The NT-TRP 172 also includes a memory 278 for storing information and data. Although not shown, a processor 276 may form part of the transmitter 272 and / or receiver 274. Although not shown, the memory 278 may form part of the processor 276.

[0161] The processor 276 and the processing components of the transmitter 272 and receiver 274 may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 278). Alternatively, some or all of the processing components of the processor 276 and the transmitter 272 and receiver 274 may be implemented using dedicated circuitry such as a programmed FPGA, GPU, or ASIC. In some embodiments, the NT-TRP 172 may actually be multiple NT-TRPs that operate together, for example, through coordinated multicast transmissions, to serve ED 110.

[0162] T-TRP 170, NT-TRP 172 and / or ED 110 may include other components, but these components have been omitted for clarity.

[0163] One or more steps of the method provided in this article can be derived from... Figure 4 The corresponding unit or module is executed. Figure 4 The diagram illustrates units or modules within a device, such as ED 110, T-TRP 170, or NT-TRP 172. For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by artificial intelligence (AI) or machine learning (ML) modules. The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of these units or modules may be integrated circuits, such as a programmed FPGA, GPU, or ASIC. It should be understood that where these modules are implemented using software executed by a processor, for example, these modules may be retrieved by the processor, in whole or in part, individually or together, for processing, in single or multiple instances, and these modules themselves may include instructions for further deployment and instantiation.

[0164] Further details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0165] Methods, apparatus, and systems for scheduling low-layer downlink UC data transmission (e.g., transport block (TB) based downlink UC transmission) are provided. While the description focuses on TB-based downlink UC transmission, the method can be applied to other low-layer UC transmissions, such as UC implemented / achieved in the MAC and PHY layers. The provided methods, apparatus, and systems can solve / mitigate one or more of the following:

[0166] How to distinguish between normal data transmission and UC data transmission PDCCH;

[0167] How to distinguish between DL TB segmented or TB repeated UC transmission PDCCH;

[0168] The DCI design for DL ​​UC transmission includes the design of the new data indicator (NDI);

[0169] The corresponding UE (TUE and CUE) behavior of UC transmission based on TB, including information sharing on the link between UEs;

[0170] HARQ operation control;

[0171] HARQ processing based on CBG;

[0172] HARQ process configuration for UC traffic and non-UC traffic.

[0173] The difference between scheduling UE's own traffic and UC traffic

[0174] In this implementation, a system and method are provided for distinguishing between scheduling UE’s own downlink traffic (or non-UC traffic) and downlink UC traffic, as well as for distinguishing between scheduling different types of UC traffic.

[0175] Downlink UC data transmission refers to the cooperative reception of data from the network (e.g., from a base station) by the target UE (TUE) and one or more CUEs. Note that the described method also applies to cooperative data transmission from the UE to the TUE and one or more CUEs. (See also...) Figure 5A Describe the difference between normal UE traffic (i.e., UE's own traffic) and UC traffic. Figure 5A The diagram shows gNB 500 and three UEs 502, 504, and 506. Any UE can receive its own data from gNB 500 without UC cooperation. Additionally, one or more UEs can act as CUEs to assist another UE acting as a TUE in data reception. Figure 5AIn the example, specifically in a UC data transmission example, UEs 504 and 506 are acting as CUEs to assist UE 502, which is acting as a TUE, in data reception. There is an inter-UE connection 501 between UE 502 and UE 504, and another inter-UE connection 503 between UE 502 and UE 506. As mentioned above, these links may or may not be standardized by 3GPP. The transmission of scheduling signal 508 from gNB 500 to UEs 502, 504, and 506 is also shown, with the aim of scheduling normal downlink UE data transmission and downlink UC data transmission 510.

[0176] This document describes embodiments primarily with reference to UC data transmission, in which a SUE or target UE (TUE) collaborates with (one or more) CUEs to transmit data from the SUE (and / or to the TUE). UC is a form of joint transmission by multiple UEs (e.g., SUE and one or more CUEs), and "joint UE transmission" or "joint transmission" may also be used to refer to the collaborative transmission of data as disclosed herein. SUE, TUE, and CUE refer to UEs and UE behaviors that may vary depending on whether the UE is used as or implements a SUE, TUE, or CUE (or in other words, is in a SUE, TUE, or CUE role). For example, features disclosed herein in the context of an SUE, TUE, or CUE, or a UE in a SUE, TUE, or CUE role, generally apply to UEs configured or operable to collaborate in joint data transmission.

[0177] Figure 5B Another example is shown, indicating that the network end can include multiple TRPs (Transmission Receive Points) 550, 552, instead of network entities such as gNB.

[0178] Figure 5C Another example is shown where another UE 560 sends data to / receives data from a group of UEs (TUE / SUE and multiple CUEs) in a UC manner. In this case, the air interface between such another UE and the group of UEs can be a sidelink interface. For example, the control signals used for scheduling can be in the format of sidelink control information (SCI) and carried in the physical sidelink control channel (PSCCH) / physical sidelink shared channel (PSSCH). Data can be carried in the PSSCH.

[0179] Transmissions to / from different TUEs / SUEs can be on the same or different frequency bands as those to / from CUEs. For example, in Figure 5A In this context, transmissions to / from TUE / SUE (downlink / side link) may be on the same or different frequency bands as those to / from CUE#1 or CUE#2. Transmissions to / from CUE#1 (downlink / side link) may be on the same or different frequency bands as those to / from CUE#2.

[0180] for Figure 5A , 5B In any implementation of 5C, the scheduling signal includes a distinction between two types of data transmission, enabling the UE receiving the scheduling signal to know whether the data transmission is a normal downlink UE data transmission, rather than a downlink UC data transmission.

[0181] For example, when PDCCH scheduling is used to schedule these two types of data transmission, PDCCH scheduling includes the distinction between the two types of data transmission. Note that in this disclosure, the PDCCH that schedules UC transmissions or normal UE transmissions can also be described as: downlink control information (e.g., DCI) transmitted in the PDCCH that schedules UC transmissions or normal UE transmissions.

[0182] In some embodiments, a radio network temporary identifier (RNTI) is used for this purpose. Depending on whether the scheduled transmission is normal downlink UE data transmission or downlink UC data transmission, different RNTIs can be used to scramble the contents of the PDCCH. In a specific example, the PDCCH for scheduling normal downlink UE data transmission to the UE is scrambled using the normal UE RNTI, for example, the receiving UE's regular C-RNTI, while the PDCCH for scheduling UC data transmission is scrambled using the new UE RNTI. More generally, different RNTIs known to both the transmitter and receiver can be used for both purposes.

[0183] This new UE RNTI (or UC RNTI) can be used to apply one or both of bit-level scrambling and PDCCH cyclic redundancy check (CRC) scrambling. Figure 6 An example is shown in [the image]. Figure 6In the example shown, at the transmitter, a set of DCI bits 602 and generated CRC bits 604 are illustrated. This is scrambled using RNTI 606, one of two RNTIs that distinguish normal UE data transmission from UC transmission. In the example shown, this is referred to as the "new RNTI" or UC RNTI to indicate UC transmission. In another application, encoder 608 is shown, which generates an encoded bitstream including CRC, which undergoes bit-level scrambling at bit scrambling using the new RNTI at 612 in bit scrambler 610.

[0184] In some embodiments, a common PDCCH is used to schedule UC data transmissions to both the TUE and CUE. In this case, a new common RNTI can be configured and used to scramble the common PDCCH. Both the TUE and CUE receive and process the common PDCCH. In some embodiments, corresponding independent PDCCHs are used to schedule UC data transmissions to both the TUE and each CUE. In this case, the TUE and CUE each receive and process their respective independent PDCCHs. In this case, separate new RNTIs can be configured for the TUE and each CUE respectively and used to scramble the PDCCHs of the TUE and each CUE for appropriate reception by the TUE and CUE.

[0185] Differences between scheduling different types of TB-based downlink UC traffic

[0186] Reference Figure 7 Further illustrating an example of TB-based downlink UC data transmission, the figure shows a gNB 700, a first UE 702 acting as a TUE, and a second UE 704 acting as a CUE to assist the TUE in receiving data from the gNB 700. UE 702 has a MAC layer 710 and a PHY layer 712. UE 704 has corresponding layers 714 and 716, and the gNB 700 has corresponding layers 718 and 720. At 722, the TB for receiving normal UE data as the first UE 702 is indicated, showing TB 722 received by PHY 712 for processing by MAC 710. At 724, the TB for receiving normal UE data as the second UE 704 is indicated, showing TB 724 received by PHY 716 for processing by MAC 714. Finally, the TBs used for UC transmission include TB 726, which is received by PHY 712 for processing by MAC 710, and TB 728, which is received by PHY 716 for transmission to TUE 702 for processing by TUE's MAC 710.

[0187] In the context of the illustrated example of combined transmission, combined transmission is used for data originating from a transmitter, source, or source device, which is... Figure 7 gNB 700 in the context of gNB 700, but may include or include as follows: Figure 5B TRP as an example is shown in the text. Figure 5C The image shows another UE as an example. For example, such data can also be referred to as data originating from a transmitter, source, or source device. For example, joint transmission can be described as joint transmission for such data, joint transmission of such data, joint transmission from a transmitter, source, or source device, or joint transmission for a UE, or more generally joint transmission for a receiver, target, target device, or destination device. These are merely examples; other terms may be used to describe joint transmission.

[0188] UC data transmission can take the form of split UC data transmission or repeated UC transmission. When split UC data transmission is used, TUE and CUE receive different data from TUE, while when repeated UC transmission is used, TUE and CUE receive the same data from TUE. In a specific example, data duplication / split occurs at the TB level, and an example is provided in [example missing]. Figure 8A and 8B As shown in the figures, these diagrams illustrate two types of TB-based UC. Figure 8A This illustrates segmented TB downlink UC data transmission. In this scenario, for the UC transmission, the first TB 800 is sent to and received by TUE 702, and the second distinct TB 802 is sent to and received by CUE 704, and then transmitted to the TUE. In this case, the two distinct TBs are sent by the gNB, one to the TUE and one to the CUE. Each TB is managed by an independent Hybrid Automatic Repeat Request (HARQ) process.

[0189] Figure 8B The diagram illustrates TB repeating downlink UC data transmission. In this case, for the UC transmission, the first TB 810 is sent to and received by TUE 702, TB 812 is sent to and received by CUE, and then transmitted to TUE. In this case, the same TB is repeated and sent by the gNB or simply broadcast to both TUE and CUE. The two TBs (or broadcast TBs) sent to TUE and CUE are managed by a single (identical) HARQ process because the TBs contain the same data.

[0190] In the detailed examples described in this article, it is assumed that a UC transmission involves multiple UEs collaboratively receiving data from a network device such as a gNB. However, a UC transmission can also involve multiple UEs collaboratively receiving data from another UE (the source UE).

[0191] In the detailed examples described herein, TB-based UC transmission (TB duplication or TB segmentation) is used. Other types of data duplication and segmentation can also be employed (e.g., data duplication or segmentation may not occur at the TB level, but rather in other units / formats / packets), and mechanisms similar to those described herein for scheduling UEs, UE behavior, signal / data streams, etc., can be used.

[0192] Different alternatives exist for distinguishing between these segmented and repeated TB-based UC transmissions. In some embodiments, different RNTIs are used for PDCCH scrambling to differentiate between segmented TB transmissions and repeated TB transmissions. For example, the PDCCH for scheduling segmented TB transmissions can be scrambled using a first new UE RNTI-1. Both or either bit-level scrambling based on UE RNTI-1 and PDCCH CRC scrambling can be applied. The PDCCH for scheduling repeated TB transmissions can be scrambled using a second new UE RNTI-2. Both or either bit-level scrambling based on UE RNTI-2 and PDCCH CRC scrambling can be applied.

[0193] For a TUE, both RNTI-1 and RNTI-2 can be used to distinguish between TB-segmented UC transmissions and TB-repeated UC transmissions. When a TUE receives a PDCCH scrambled with RNTI-1, the TUE knows the transmission is a TB-segmented transmission, and therefore the TUE receives a different TB from the CUE. When a TUE receives a PDCCH scrambled with RNTI-2, the TUE knows the transmission is a TB-repeated transmission, and therefore the TUE receives the same TB from the CUE. When a UE acting as a TUE receives normal traffic, it can use its normal RNTI for this purpose; if the same UE can also be used as a CUE to help another TUE receive UC transmissions, a third RNTI can be allocated to that UE for scrambling the corresponding PDCCH.

[0194] For a UE used as a CUE, only one additional RNTI is used for UC transmission because it may not be necessary to distinguish between TB-segmented UC transmissions or TB-repeated UC transmissions; instead, the CUE simply receives the TB from the gNB and transmits it to the TUE, and this may be a duplicate or different TB compared to the TB sent to the TUE itself.

[0195] In some embodiments, a single new RNTI is used instead of both the new RNTI-1 and RNTI-2 of the TUE, wherein the distinction between TB segmented UC transmissions and TB repeated UC transmissions is achieved, for example, by other means configured by higher-layer signaling.

[0196] New RNTIs, which can be configured identically or differently for both TUE and CUE, can be referred to as UC-RNTIs.

[0197] If a common DCI is used to schedule DL UC data transmissions for both TUE and CUE, two new common RNTIs (such as group RNTIs) can be configured and used to scramble the common PDCCH, one for scheduling TB-segmented downlink UC transmissions and the other for scheduling TB-segmented downlink UC transmissions. If a separate DCI is used to schedule UC transmissions for TUE and CUE respectively, separate sets of new RNTIs can be configured for TUE and CUE respectively and used to scramble the PDCCHs of TUE and CUE to schedule TB-segmented UC transmissions or TB-repeated UC transmissions respectively. Such new RNTIs can also be used to determine the location of the PDCCH for scheduling UC traffic transmitted in the corresponding control resource set (CORESET).

[0198] In some embodiments, higher-layer signaling is used to configure TB-repeated downlink UC data transmission and TB-segmented downlink UC data transmission. For example, radio resource control (RRC) signals or medium access control (MAC) control entity (CE) signals can be used. In some embodiments, the higher-layer configuration is only sent to the TUE because the CUE may not need to distinguish between TB-segmented UC transmission and TB-repeated UC transmission. Figure 9A An example is shown where higher-layer signaling 900 is used to instruct TB to segment downlink UC data transmission. Figure 9B An example is shown where higher-layer signaling 902 is used to instruct TB to repeat downlink UC data transmission.

[0199] The above discussion covered public and independent PDCCHs. The actual scheduling information is contained within the DCI transmitted using such public or independent PDCCHs. Several alternatives for scheduling DCI content for UC transmissions are provided.

[0200] In the first alternative, if TB-repeated UC transmission is configured, the DCI for TUE is expected to include scheduling information for a single TB; otherwise, if TB-split UC transmission is configured, the DCI for TUE will include scheduling information for two TBs. The scheduling information for the first TB is used by TUE for receiving the first TB. The scheduling information for the second TB is used by CUE for receiving the second TB, which is then transmitted to TUE.

[0201] In the second alternative, the DCI to TUE includes only one TB of scheduling information, and if TB segmentation is configured, a second TB with the same size as the first TB will be expected to be received by CUE and transmitted to TUE.

[0202] In the third alternative, the DCI to TUE always includes scheduling information for both TBs, and if TB duplication is configured, the second TB has the same size as the first TB, and TUE expects to receive the duplicated TB from CUE. Otherwise, if TB splitting is configured, the second TB may have a different size compared to the first TB. TUE then expects to receive two different TBs, one received by TUE from the network / SUE and the other from CUE.

[0203] In the fourth alternative, the DCI to TUE includes only one TB of scheduling information, and if TB segmentation is configured, a second TB with the same size as the first TB will be expected to be received by CUE and transmitted to TUE.

[0204] In some implementations, one of the two types of TB-based UC transmissions (split and repeat) is implicitly indicated in the DCI to TUE.

[0205] In the first example of this method, if the DCI sent to TUE includes scheduling for a single TB (or a single codeword (CW), where the TB is typically encoded into a CW), this is used to imply / indicate that the TB is a duplicate UC transmission, and the same TB will be repeated and sent to both TUE and CUE. In this case, the scheduling portion of the second TB can be padded with padding bits or zeros for easy detection. On the other hand, if the DCI sent to TUE includes scheduling information for two TBs, this is used to imply / indicate that the TB is a split UC transmission, and in this case, the different TBs are expected to be unicast to TUE and CUE respectively. In this case, the DCI size is fixed regardless of whether the scheduled TB is a split UC transmission or a duplicate UC transmission.

[0206] In some implementations, the TB size is derived from the allocated time-frequency resources and the corresponding MCS indicated for each TB.

[0207] The UE can implicitly determine whether it is TB repeated UC data traffic or TB segmented UC data traffic by detecting whether the DCI includes scheduling information of one TB or two TBs.

[0208] In the second example of this method, if the DCI sent to TUE includes scheduling for two TBs and such scheduling information is identical (e.g., the MCS, HARQ ID, and RV are the same for each TB), this is used to imply / indicate that the TBs are duplicated for UC transmission, and the same TBs will be repeated and sent to both TUE and CUE respectively, or a single TB will be broadcast to both TUE and CUE. On the other hand, if the DCI sent to TUE includes scheduling information for two TBs and such scheduling information is different (e.g., the MCS, HARQ ID, and RV are different for each TB), this is used to imply / indicate that the TBs are split for UC transmission, in which case different TBs will be prepared and sent to TUE and CUE respectively. The UE can implicitly determine whether the TBs are duplicated for UC transmission or split for UC transmission by detecting the scheduling information of the two TBs and determining whether the scheduling information is identical or different.

[0209] In either case, the DCI size can be based on scheduling two TB transmissions, so the DCI size is fixed regardless of whether a TB-split UC transmission or a TB-repeated UC transmission is scheduled. Similarly, the TB size can be derived from the allocated time-frequency (TF) resources and the MCS indicated for each TB.

[0210] Detailed DCI design options for TB-based UC transmission

[0211] In the first alternative, the same DCI (common DCI) including scheduling information for both TUE and CUE can be used. The common PDCCH carrying this DCI (or the PSCCH / PSSCH carrying the SCI on a side link from another transmitting UE) can be transmitted from shared / identical resources (e.g., a shared control resource set (CORESET) with a shared / identical search space) or independent resources (e.g., an independent CORESET and an independent search space) configured separately for TUE and CUE. In this case, the same new RNTI (different from the traditional C-RNTI) can be configured and used to scramble the CRC of the common DCI.

[0212] In some implementations, the common DCI carried by the common PDCCH includes a common set of time-frequency resources used for TUE and CUE transmissions. This implies overlapping transmissions to TUE and CUE on the same time-frequency resources.

[0213] The public DCI may include one or more HARQ process numbers (HARQ IDs) and corresponding redundant versions (RVs) (one HARQ ID and / or one RV per TB). For TB duplication, one HARQ process is used, thus indicating one HARQ ID and one or more RVs for the same TB sent to different UEs (TUE or CUE). For TB segmentation, more than one HARQ process is used, one HARQ process per TB. Therefore, more than one HARQ ID and its corresponding RV are indicated in the public DCI, one HARQ ID and its corresponding RV per TB. Alternatively, a first HARQ ID may be indicated, while other HARQ IDs may be derived from the first HARQ ID, for example, second HARQ ID = first HARQ ID + offset. In a specific example of this method, second HARQ ID = first HARQ ID + 1, third HARQ ID = first HARQ ID + 2, and so on.

[0214] A public DCI can include one or more NDIs, one NDI per TB, to indicate whether it is a new transmission or a retransmission.

[0215] For data duplication, an NDI is used. If the NDI is flipped, the new data is sent to both TUE and CUE. If the NDI is not flipped, the same old TB is retransmitted for both TUE and CUE.

[0216] For data segmentation, two NDIs can be specified (more generally, one NDI for TUE and one NDI for each CUE). In this case, the NDI for TUE indicates whether the TB sent to TUE is a new transmission or a retransmission, and the NDI for each CUE indicates whether the TB sent to CUE is a new transmission or a retransmission. In this way, new transmissions and retransmissions to TUE and CUE can be scheduled independently.

[0217] In some implementations, DCI includes demodulation reference symbol (DMRS) indications for two TBs (or two CWs), with one DMRS indication for each UE.

[0218] In this implementation, the TUE will use one or two TBs of scheduling information to expect to receive data either by itself or through the CUE. The CUE will use only one TB (e.g., the second TB) of scheduling information to receive data.

[0219] Figure 10An example of a public PDCCH carrying a public DCI 1000 for scheduling 2 TB (maximum, e.g., maximum 2 CW) transmissions is shown. A DCI format similar to DCI format 1-1 in NR can be used. The public DCI 1000 includes public scheduling information 1002 (which may include resource allocation, etc.) suitable for scheduling two TBs to avoid duplication, scheduling information 1004 specific to the first TB (including one or more of, for example, MCS, HARQ ID, RV, NDI), and scheduling information 1006 specific to the second TB.

[0220] If a TB repetition is scheduled, in addition to the common scheduling information 1002, the DCI also includes scheduling information 1004 specific to the first TB, while scheduling information (or part / field) 1006 specific to the second TB is padded with padding bits or zeros. If a TB split is scheduled, it includes scheduling information 1004 and 1006 for both TBs.

[0221] In this case, data duplication or data splitting can be implicitly sent to TUE by scheduling information that includes only one TB (e.g., the first TB) or by scheduling information that includes both the first TB and the second TB.

[0222] If TUE detects that the DCI includes only one TB of scheduling information, TUE uses this information to infer that UC traffic of the TB repetition type was scheduled; otherwise, if TUE detects that the DCI includes two TBs of scheduling information, TUE uses this information to infer that UC traffic of the TB segmentation type was scheduled.

[0223] The size of each TB can be derived from the allocated TF resources and the corresponding MCS indicated for each TB. TUE and CUE will receive their respective UC transmissions on the same TF resources scheduled by the common DCI in the common scheduling information field. Additionally, for TB-segmented UC transmissions, TUE will receive a portion of its UC transmission (e.g., the first TB) based on scheduling information specific to the first TB, and CUE will receive a portion of its UC transmission (e.g., the second TB) based on scheduling information specific to the second TB. For TB-segmented UC transmissions, the two TBs sent to TUE and CUE respectively can have different TB sizes.

[0224] When the CUE receives the second TB, it needs to pass the decoded TB or some intermediate data obtained during decoding to the destination TUE. If a non-3GPP inter-UE link is used, the transmission scheduling of the second TB from the CUE to the TUE is not specified. However, if a 3GPP-defined interface is used for the inter-UE link, resources can be configured on the inter-UE link to send the second TB received by the CUE to the TUE. For example, if a PC5 link is used to carry the second TB from the CUE to the TUE, a configured grant (CG) can be used to configure resources on the inter-UE link; therefore, this scheduling information for the inter-UE link does not need to be carried by the public DCI.

[0225] In some embodiments, separate PDCCHs for TUE and CUE are used, which can be sent from separate CORESETs configured for TUE or CUE respectively. Figure 11 An example is shown in the image. Figure 11 A first DCI (transmitted on the first PDCCH) 1100 for TUE is shown. This DCI includes other scheduling information 1102 common to the first TB and the second TB, scheduling information 1104 specific to the first TB, and scheduling information 1106 specific to the second TB. A second DCI 1110 (transmitted on the second PDCCH) for CUE is also shown, which includes scheduling information 1114 specific to the TB sent to CUE for subsequent transmission to TUE, and some other scheduling information 1112.

[0226] The TUE's PDCCH can include scheduling information for two TBs and is used to schedule UC transmissions from the gNB to the TUE. This PDCCH is also used to prepare TBs for receiving UC data traffic received by the CUE, following the same principles as those mentioned for public PDCCHs.

[0227] For TB-level splits, alternative methods can be used to indicate the size of the second TB. More specifically, a scheduling field specific to the second TB can be reused to directly carry the size of the second TB, or it can carry other relevant information that can be used to deduce the size of the second TB. For example, such as... Figure 10 The specific fields shown, carrying the MCS, HARQ ID, and RV for the second TB, can be used to carry the size of the second TB or other relevant information that can be used to deduce the size of the second TB.

[0228] Similar to the public PDCCH scenario, if a non-3GPP inter-UE link is used, the scheduling of the second TB from CUE to TUE is not specified. However, if the 3GPP-defined interface is used for the inter-UE link, some resources can be configured on the inter-UE link to send the second TB from CUE to TUE. For example, if the PC5 link is used to carry the second TB from CUE to TUE, a configured grant (CG) can be used to configure some resources on the inter-UE link; therefore, this scheduling information for the inter-UE link does not need to be carried to TUE or CUE by the PDCCH.

[0229] In some embodiments, the CUE's PDCCH includes a TB of scheduling information and is used to schedule UC data traffic to the CUE.

[0230] In some embodiments, the HARQ ID is consistent across the corresponding PDCCH (or DCI) of the TUE and CUE. For example, if data is duplicated, the same HARQ ID can be used in both the TUE's and CUE's PDCCHs. Different RVs can be used for transmissions to the TUE and CUE. If data is segmented, for a TB sent from the gNB to the CUE (and transmitted to the TUE), the same HARQ ID can be used in both the TUE's and CUE's PDCCHs. Therefore, the HARQ ID for a TB sent to the CUE (and transmitted to the TUE) is consistent across the TUE, CUE, and gNB.

[0231] The HARQ ID and RV received / decoded by the CUE can be transmitted to the TUE. If there are some differences between the HARQ ID and / or RV received by the TUE and the HARQ ID and / or RV received by the CUE, the TUE can ignore them during the joint HARQ combination.

[0232] In some embodiments, the NDI in the corresponding PDCCH (or DCI) of TUE and CUE should be consistent. For example, if data is duplicated, the NDI can be flipped together in the PDCCH of TUE and CUE respectively, so that both TUE and CUE are expected to receive the new TB (data).

[0233] In some embodiments, the TB size derived from the corresponding PDCCH (or DCI) of the TUE and CUE should be consistent with the TB decoded by the CUE. If the TB size obtained by the TUE from its PDCCH differs from the TB size decoded by the CUE, the TB may be discarded. Alternatively, if the TB decoded by the CUE is considered valid (or successful) by passing the CRC test, the TB size obtained by the TUE from the PDCCH is ignored.

[0234] If the NDI in the TUE's DCI flips, it means that new data is expected, and the TB passed from the CUE indicates that it is an old TB, the TUE can skip the HARQ combination of the received data from the CUE.

[0235] If the NDI in the TUE's DCI is not flipped, it means the old data is being retransmitted, while the TB transmitted from the CUE indicates that it is a new TB, and the TUE can skip the HARQ combination of the received data from the CUE.

[0236] UE behavior based on TB-based UC transmission

[0237] In this embodiment, different UE methods or behaviors are provided to implement TB-based UC transmission / reception. Functions will be described separately for TUE and CUE. Of course, a given UE can be used to act as a TUE for some transmissions and / or as a CUE for other transmissions.

[0238] Figure 12 This is an example flowchart of a method performed by a UE acting as a TUE, characterized by TB repetition. The method begins in box 1200 with receiving and decoding the PDCCH of scheduled downlink UC data traffic with TB repetition. If it is new data (NDI flip), the path is yes (box 1202), meaning it is a new TB. At box 1206, the TUE will attempt to decode the received data. Otherwise, it is retransmitted data (no (box 1202)), and the TUE will attempt to combine the received data with the data in its HARQ soft buffer (stored from previous transmissions) and decode it at box 1204. If decoding is successful (yes (box 1208)), the TUE will send an ACK to the gNB for the TB at box 1218. If decoding fails (no (box 1208)), the TUE will check if decoding of the same TB at the CUE was successful; if yes (yes (box 1210)), the TUE will receive the decoded TB from the CUE at box 1212 and send an ACK to the gNB at box 1218. If both TUE and CUE fail to decode TB (No path box 1210), TUE can obtain the received data from CUE, combine it with the data in TUE's HARQ soft buffer, and decode the combined data at 1214. If this decoding is successful (Yes path box 1216), TUE will send an ACK to gNB at 1218. Otherwise, TUE will send a NACK to gNB at 1220. It should be noted that the order of using individual decoding and joint decoding operations depends on the implementation.

[0239] Figure 13This is an example flowchart of a method performed by a UE acting as a TUE, characterized by TB segmentation. The method begins in block 1300 with receiving and decoding the PDCCH of scheduled downlink UC data traffic with TB segmentation (similar to scheduling 2 CWs for 2 TBs). If the NDI of the first TB is flipped (path 1302), the TUE will attempt to decode the received data at 1308. If successful, (path 1312) the TUE will send an ACK for the first TB to the gNB at 1318; otherwise, (path 1312) the TUE will send a NACK for the first TB to the gNB at 1320. If the NDI of the first TB is not flipped (path 1302), the TUE will attempt to decode the combined data (current data and previously received data) at 1306. If successful, (path 1312) the TUE will send an ACK for the first TB to the gNB at 1318; otherwise, (path 1312) the TUE will send a NACK for the first TB to the gNB at 1320.

[0240] The TUE also checks the instruction from the CUE regarding decoding the second TB. If the instruction is successfully decoded (path box 1304), the TUE will receive the decoded second TB from the CUE at box 1310 and send an ACK for the second TB to the gNB at box 1316; otherwise, the TUE will send a NACK for the second TB to the gNB at box 1314. If the second TB is not successfully decoded by the CUE (path box 1304), the TUE will send a NACK to the gNB at box 1314.

[0241] As mentioned earlier, UE-to-UE connectivity can be specified by 3GPP or not. For example, this connectivity can be a wired or wireless connection based on specifications outside of 3GPP, such as WiFi, Bluetooth, Ethernet, etc.

[0242] Figure 14This is an example flowchart of a method performed by the UE acting as the CUE. The method begins in box 1400 with receiving and decoding the PDCCH for CUE-scheduled downlink UC data traffic. If the NDI is flipped (path box 1402), the CUE will attempt to decode the received data at 1406. If successful, (path box 1408), the CUE will send the decoded TB and ACK to the TUE via the inter-UE link at 1410. Otherwise, if decoding fails, the CUE will send a NACK to the TUE via the inter-UE link at 1412. If the NDI of the TB is not flipped (path box 1402), the CUE will attempt to decode the combined data (current data and previously received data) at 1404. If successful, (path box 1408), the CUE will send the decoded TB and ACK to the TUE at 1410. Otherwise, if decoding fails, the CUE will send a NACK to the TUE at 1412. Optionally, if decoding fails (No path box 1408), CUE also sends the received data (possibly in the form of soft symbols decoded from TB) along with the corresponding HARQ ID, RV and NDI information to TUE at 1412.

[0243] Including the aforementioned Figure 7 The same reference numerals in the attached figures Figure 15 TB buffers 1500 and 1502 are also shown. These buffers are used by the TUE and CUE to store TB data and exchange such data between these buffers via inter-UE links. HARQ buffers 1504 and 1506 in PHY layers 712 and 716 can be conventional HARQ soft buffers in the TUE and CUE, respectively, used to store channel-decoded data in the PHY layer.

[0244] For downlink UC transmissions, with the destination UE being TUE, the HARQ entity managing the UC transmission can be configured at the MAC layer of TUE. Various alternatives for HARQ control of UC transmissions at CUE are described below.

[0245] In the first alternative, such as Figure 16 As shown, it illustrates the relationship with Figure 7 and 15 Using the same reference numerals, HARQ control for the CUE is performed in the HARQ entity configured in the TUE MAC layer 710. In this case, HARQ information decoded from the CUE's DCI, such as HARQID, RV, and NDI, is passed to the TUE MAC layer 710, and at 1600, the HARQ transmission decision is sent from the TUE MAC layer 710 to the CUE's PHY layer 716 for HARQ transmission. This is similar to conventional behavior and may result in more latency because HARQ control needs to be exchanged between the TUE and CUE.

[0246] In the second alternative, such as Figure 17 As shown, it also shows the same as Figure 7 and 15 Using the same reference numerals, HARQ control for the CUE is accomplished with the assistance of MAC layer 714 in the CUE. In this case, certain HARQ entity functions for UC transmission are configured and implemented in the CUE's MAC layer 714. HARQ information decoded from the DCI at the CUE can be passed to the CUE's MAC layer 714 at 1700, and the CUE's MAC layer 714 can make decisions regarding HARQ operation. Because HARQ control is performed in the CUE, this alternative approach results in lower latency.

[0247] For example, if the HARQ information decoded from the DCI indicates a retransmission of an earlier transmission, the CUE's MAC layer can instruct its PHY to combine the received data with data from the earlier transmission stored in the HARQ soft buffer and attempt to decode them together. Otherwise, if the HARQ information, such as NDI, indicates that it is a new TB, the CUE's MAC layer can instruct its PHY layer to decode the received data into a new TB. If decoding (after the first transmission or retransmission) is successful, the CUE sends an ACK indication and the decoded TB to the TUE; otherwise, the CUE sends a NACK indication to the TUE, and optionally, the CUE sends a HARQ soft message to the TUE.

[0248] Typically, the UE-to-UE interface can carry one or more of the following information between the TUE and CUE to facilitate data transmission between the UC:

[0249] Decoded TB from CUE;

[0250] Intermediate soft information (undecoded information bits) from the received data from CUE is used by TUE for combination;

[0251] HARQ information, such as HARQ ID, RV, NDI, etc.;

[0252] ACK / NACK information for TB after decoding from CUE.

[0253] The interface between UEs may or may not be 3GPP-defined. However, the information carried through this interface can be specified / configured along with necessary information such as the information sharing window / timing / period and the information sharing process.

[0254] Figure 18An example of the signal / data flow for the TB repetition process between gNB 1800, TUE 1802, and CUE 1804 is shown. This example begins with the transmission of the PDCCH at 1806 and 1808. This is followed by the transmission of the PDSCH at 1810 and 1812. For the PDSCH transmission 1810 to TUE 1802, at 1814, if the NDI is toggled, TUE 1802 decodes the received data; otherwise, TUE 1802 decodes the HARQ combined data. For the PDSCH transmission 1812 to CUE 1804, at 1816, if the NDI is toggled, CUE 1804 decodes the received data; otherwise, CUE 1804 decodes the HARQ combined data. At 1820, if CUE 1804 successfully decodes the received data, CUE 1804 sends a successful decoding indication and the decoded TB to TUE 1802; otherwise, it sends HARQ soft information to TUE 1802. At 1822, if necessary, TUE 1802 decodes the combined HARQ data from both TUE 1802 and CUE 1804. If successful, at 1824, TUE 1802 sends a HARQ-ACK feedback (ACK or NACK) of the TB to gNB 1800.

[0255] Figure 19 An example of the signal / data flow for the TB segmentation process between gNB 1900, TUE 1902, and CUE 1904 is shown. This example begins with PDCCH transmissions at 1906 and 1908, followed by PDSCH transmissions at 1910 and 1912. For PDSCH transmission 1910 to TUE 1902, at 1914, if the NDI is flipped for the first TB, TUE 1902 decodes the received data; otherwise, TUE 1902 decodes the HARQ combined data for the first TB. For PDSCH transmission 1912 to CUE 1904, at 1916, if the NDI is flipped for the second TB, CUE 1904 decodes the received data; otherwise, CUE 1904 decodes the HARQ combined data for the second TB. At 1918, if CUE 1904 successfully decodes the received data for the second TB, CUE 1904 sends the successfully decoded second TB to TUE 1902. At 1920, TUE 1902 sends HARQ-ACK feedback (ACK or NACK) for the first TB and the second TB to gNB 1900.

[0256] For UC's code block group (CBG) based retransmission

[0257] In some embodiments, to handle large TB sizes, HARQ based on code block groups (CBGs) is used to improve efficiency and reduce latency. This approach divides the TB into multiple CBGs. Each CBG comprises multiple code blocks (CBs).

[0258] exist Figure 20 An example is shown, illustrating that a TB can be divided into multiple CBGs. Each CBG can include multiple code blocks (CBs). TUE or CUE can attempt to decode each CB. If all CBs in a CBG are correctly decoded, an ACK is generated; otherwise, a NACK is generated for the CBG.

[0259] For CBG-based HARQ processes, ACK / NACK are generated in the PHY layer, thus eliminating the need for information exchange with the MAC layer. This also reduces latency. TUE and CUE perform their own CBG-based HARQ until all CBGs in the TB have been successfully decoded. CUE then transmits the TB and the ACK indication of the decoded TB to TUE.

[0260] To expedite the HARQ process when TBs are repeated (receiving the same TB at both TUE and CUE), some ACK / NACK information based on CBGs can be exchanged between TUE and CUE. For example, TUE (or CUE) can pass its ACK / NACK information for each CBG to other UEs, so other UEs (TUE or CUE) may not need to retransmit the CBG. When all CBGs are correctly received or combined at either TUE or CUE, an ACK can be indicated for the entire TB, and CUE can pass the correctly decoded CBG to TUE for generating the entire TB (using CBGs decoded from both TUE and CUE).

[0261] In some embodiments, since both CUE-based transmissions (non-UC transmissions) and UC transmissions may require HARQ soft buffers (resource types) to support HARQ operations, the HARQ soft buffers can be segmented to accommodate UC traffic and CUE-based traffic, such as... Figure 21 As shown, it illustrates a HARQ buffer 2102 for CUE traffic and a HARQ buffer 2100 for UC traffic. For example, if a total of M HARQ processes can be supported with the corresponding HARQ buffers allocated, N1 HARQ processes can be configured for UC traffic, and N2 HARQ processes can be configured for CUE traffic. Such configuration can be achieved, for example, using higher-layer signals such as RRC or MAC CE.

[0262] The HARQ processes used for UC traffic and CUE traffic can be configured differently. In one example, for UC traffic, HARQ processes are numbered from 1 to N1, and for CUE traffic, HARQ processes are numbered from 1 to N2. .

[0263] In another example, for UC traffic, the HARQ process is numbered from 1 to N1, and for CUE traffic itself, the HARQ process is numbered from N1+1 to N1+1. Number them.

[0264] The HARQ soft buffer here can refer to either the UL or DL ​​HARQ buffer.

[0265] For uplink, the HARQ soft buffer can refer to a circular buffer (or a rate-matched buffer after channel coding), which stores different RV versions of the channel-coded TB.

[0266] For downlink, the HARQ soft buffer can refer to a buffer used to store received data (raw transmission or retransmission) before channel decoding.

[0267] For UC data traffic, a HARQ entity can be configured in the common MAC used for UC (which can be located in TUE or another UE).

[0268] In some implementations, for cases where TB is repeated, the number of HARQ processes for CUE and TUE is configured to be the same (i.e., TUE and CUE are configured with the same number of HARQ processes), or a set of HARQ processes can be configured for both TUE and CUE.

[0269] For TB segmentation, the number of HARQ processes for CUE and TUE can be configured differently (i.e., TUE and CUE can be configured with different numbers of HARQ processes). The number of HARQ processes configured for TUE or CUE may depend on the amount of UC traffic being transmitted. For example, if more UC traffic is being transmitted from gNB to TUE, more HARQ processes can be configured for TUE.

[0270] The configuration of the number of HARQ processes can be sent to the UE and then passed to the CUE, or it can be sent to the TUE / CUE separately.

[0271] The UE behavior and data / signaling flow for receiving TB-based downlink UC data traffic (including TUE and SUE) have been provided and described in a clear and concise manner. Additionally, several other aspects are provided, including CBG-based HARQ procedures to support UC data traffic, and HARQ procedure configuration to support both UC and non-UC data traffic.

[0272] This document discloses various embodiments by way of example.

[0273] These embodiments include, for example, a method in a first UE. This method may involve: receiving a first PDCCH that schedules downlink joint UE transmissions from a transmitter for the first UE; receiving a first TB from the transmitter based on the first PDCCH; and receiving data from a second UE via an inter-UE connection. For example, from the perspective of a transmitter such as a network device, the method may involve sending a first PDCCH that schedules joint UE transmissions, sending a first TB of data to the first UE based on scheduling information in the first PDCCH, and sending a second TB of data to the second UE.

[0274] The apparatus embodiments disclosed herein include an apparatus having at least one processor coupled to a memory storing instructions. These instructions, when executed by the at least one processor, can cause a UE or a transmitter to perform a method. In the context of causing the UE to perform a method, the method may include: receiving a first PDCCH that schedules downlink joint UE transmissions from the transmitter for the UE; receiving a first TB from the transmitter based on the first PDCCH; and receiving data from a second UE via an inter-UE connection. In the context of causing the transmitter to perform a method, the method may involve: transmitting a first PDCCH that schedules joint UE transmissions from the transmitter for the first UE; transmitting a first TB of data from the transmitter to the first UE based on the first PDCCH from the first UE; and transmitting a second TB of data from the transmitter to the second UE.

[0275] In these examples, the receiving UE that receives the first PDCCH, the first TB, and the data received from the second UE can be referred to herein as the first UE, TUE, or a UE in the TUE role, and the second UE in these examples can be referred to herein as the CUE or a UE in the CUE role. The joint UE transmission in these examples can be referred to herein as a UC transmission. The transmitter in these examples can be a network device, such as a gNB, or another UE. When a UE acts as a transmitter, that UE can be referred to as the transmitting UE, the third UE, the SUE, or a UE in the SUE role.

[0276] These and other features described herein should be interpreted accordingly. For example, any feature disclosed herein in the context of a TUE or a UE in the TUE role generally applies to the UE to which the TB data is to be received. Such a UE is the first UE or receiving UE in the above example. Features disclosed herein in the context of a SUE or a UE in the SUE role may generally apply to the UE from which the TB data to be transmitted originates, or even more generally to the transmitter from which the TB data to be transmitted originates. In the above example, the transmitting UE is referred to as the third UE, and in some embodiments, the transmitter is a network device.

[0277] Similarly, features disclosed herein in the context of a CUE or a UE in a CUE role are generally more applicable to a UE to which a second TB of data originating from a transmitter is sent. This UE is the second UE in the example above. For instance, features disclosed herein in the context of network, network end, or gNB features are generally more applicable to network devices.

[0278] It should be noted that different embodiments can be implemented individually or in combination. Although combinations of features are shown in the illustrated embodiments, not all features need to be combined to achieve the benefits of the various embodiments of this disclosure. In other words, a method, apparatus, or system designed according to embodiments of this disclosure does not necessarily include all features (including steps) shown in any of the figures or all portions schematically shown in the figures. Furthermore, selected features of one exemplary embodiment may be combined with selected features of other exemplary embodiments.

[0279] Based on the above guidance, many modifications and variations of this disclosure can be made. Therefore, it should be understood that, within the scope of the appended claims, this disclosure may be practiced in ways other than those specifically described herein.

[0280] For example, this disclosure includes the following examples and other examples.

[0281] According to Example 1, a method in a first user equipment (UE) involves: receiving a first physical downlink control channel (PDCCH), the first PDCCH scheduling downlink UE cooperation (UC) transmission for a first UE in the role of a target UE (TUE); receiving a first transport block (TB) based on the first PDCCH; and receiving data from a second UE in the role of a cooperative UE (CUE) via an inter-UE connection.

[0282] Example 2 relates to the method of Example 1, wherein receiving the first TB based on the first PDCCH relates to receiving the first TB from a network device.

[0283] Example 3 relates to the method of Example 1, wherein receiving the first TB based on the first PDCCH includes receiving the first TB from the third UE.

[0284] Example 4 relates to the method of Example 1, wherein: when the UC transmission is a TB-repeated UC transmission, the data is a copy of the first TB, or the data can be used to generate the first TB; when the UC transmission is a TB-segmented UC transmission, the data is a second TB different from the first TB, or the data can be used to generate the second TB.

[0285] Example 5 relates to the method of Example 4, wherein: the first PDCCH includes an indication of whether the UC transmission is a TB repeated UC transmission or a TB split UC transmission.

[0286] Example 6 relates to the method of Example 4, and further includes: receiving higher-layer signaling to indicate whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0287] Example 7 relates to the method of Example 4, wherein: the first PDCCH includes only the scheduling information of the first TB to indicate that the scheduled TB repeated UC transmission is scheduled; or the first PDCCH includes the scheduling information of the first TB and the second TB to indicate that the scheduled TB segmented UC transmission is scheduled.

[0288] Example 8 relates to the method of Example 4, wherein: the first PDCCH includes scheduling information for two TBs; when the scheduling information for the two TBs is the same, the TB duplicate UC transmission is scheduled; when the scheduling information for the two TBs is different, the TB segmented UC transmission is scheduled.

[0289] Example 9 relates to the method of Example 4, wherein: the first PDCCH is scrambled with a first radionetwork temporary identifier (RNTI) to indicate that the TB repeats the UC transmission, and the first PDCCH is scrambled with a second RNTI to indicate that the TB segments the UC transmission.

[0290] Example 10 relates to the method of any one of Examples 1 to 8, and further includes: receiving a second PDCCH, the second PDCCH scheduling a normal downlink transmission to the first UE; wherein the first PDCCH is scrambled with a first radionetwork temporary identifier (RNTI) to indicate that the first PDCCH schedules a downlink UC transmission, and the second PDCCH is scrambled with a second RNTI to indicate that the second PDCCH schedules a normal downlink transmission to the first UE.

[0291] Example 11 relates to the method of any of Examples 4 to 9, wherein: for TB repeated UC transmissions, the first PDCCH includes a new data indicator (NDI) that indicates whether the scheduled transmission is a new transmission or a retransmission.

[0292] Example 12 relates to the method of any one of Examples 4 to 9, wherein: for TB-segmented UC transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI), the first NDI indicating whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicating whether the transmission to the second UE in the CUE role is scheduled as a new transmission or a retransmission.

[0293] According to Example 13, an apparatus in user equipment (UE) includes at least one processor coupled to a memory storing instructions, which, when executed by the at least one processor, cause the UE to perform a method relating to: receiving a first physical downlink control channel (PDCCH) that schedules downlink UE cooperation (UC) transmissions for a UE in the role of a target UE (TUE); receiving a first transport block (TB) based on the PDCCH; and receiving data from a second UE in the role of a cooperative UE (CUE) via an inter-UE connection.

[0294] Example 14 relates to the apparatus of Example 13, wherein receiving a first transport block (TB) based on a first PDCCH includes receiving the first TB from a network device.

[0295] Example 15 relates to the apparatus of Example 13, wherein receiving a first transport block (TB) based on a first PDCCH includes receiving the first TB from a third UE.

[0296] Example 16 relates to the apparatus of Example 13, wherein: when the UC transmission is a TB-repeated UC transmission, the data is a copy of the first TB, or the data can be used to generate the first TB; when the UC transmission is a TB-segmented UC transmission, the data is a second TB different from the first TB, or the data can be used to generate the second TB.

[0297] Example 17 relates to the apparatus of Example 16, wherein: the first PDCCH includes an indication of whether the UC transmission is a TB repeated UC transmission or a TB split UC transmission.

[0298] Example 18 relates to the apparatus of Example 16, and the method further includes: receiving higher-layer signaling to indicate whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0299] Example 19 relates to the apparatus of Example 16, wherein: the first PDCCH includes only scheduling information for the first TB to indicate that the scheduled TB repeated UC transmission; the first PDCCH includes scheduling information for the first TB and the second TB to indicate that the scheduled TB segmented UC transmission.

[0300] Example 20 relates to the apparatus of Example 16, wherein: the first PDCCH includes scheduling information for two TBs, and when the scheduling information for the two TBs is the same, a TB-repeated UC transmission is scheduled, and when the scheduling information for the two TBs is different, a TB-segmented UC transmission is scheduled.

[0301] Example 21 relates to the apparatus of Example 16, wherein: the first PDCCH is scrambled with a first radionetwork temporary identifier (RNTI) to indicate TB repeated UC transmission, and the first PDCCH is scrambled with a second RNTI to indicate TB segmented UC transmission.

[0302] Example 22 relates to an apparatus of any one of Examples 13 to 20, the method further comprising: receiving a second PDCCH, the second PDCCH scheduling a normal downlink transmission to a first UE; the first PDCCH being scrambled with a first radionetwork temporary identifier (RNTI) to indicate that the first PDCCH is scheduling a downlink UC transmission, and the second PDCCH being scrambled with a second RNTI to indicate that the second PDCCH is scheduling a normal downlink transmission to the first UE.

[0303] Example 23 relates to an apparatus of any of Examples 16 to 21, wherein: for a TB repeated UC transmission, the first PDCCH includes a new data indicator (NDI) that indicates whether a new transmission or a retransmission is scheduled.

[0304] Example 24 relates to an apparatus of any one of Examples 16 to 21, wherein: for TB-segmented UC transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI), the first NDI indicating whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicating whether the transmission to the second UE in the CUE role is scheduled as a new transmission or a retransmission.

[0305] According to Example 25, a method in a network device involves: transmitting a first physical downlink control channel (PDCCH), the first PDCCH scheduling downlink UE cooperation (UC) transmissions for a first UE in the role of a target UE (TUE); transmitting a first TB to the first UE based on scheduling information in the PDCCH; and transmitting a second TB to a second UE in the role of a cooperative UE (CUE).

[0306] Example 26 relates to the method of Example 25, wherein: when the UC transmission is a TB-repeated UC transmission, the second TB is a copy of the first TB; when the UC transmission is a TB-segmented UC transmission, the second TB is different from the first TB.

[0307] Example 27 relates to the method of Example 26, wherein: the first PDCCH includes an indication of whether the UC transmission is a TB repeated UC transmission or a TB split UC transmission.

[0308] Example 28 relates to the method of Example 26, and further includes: sending higher-layer signaling to indicate whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0309] Example 29 relates to the method of Example 26, wherein: the first PDCCH includes only scheduling information for the first TB to indicate that the scheduled TB repeated UC transmission is a TB repeated UC transmission; the first PDCCH includes scheduling information for the first TB and the second TB to indicate that the scheduled TB segmented UC transmission is a TB segmented UC transmission.

[0310] Example 30 relates to the method of Example 26, wherein: the first PDCCH includes scheduling information for two TBs, and when the scheduling information for the two TBs is the same, the TB duplicate UC transmission is scheduled, and when the scheduling information for the two TBs is different, the TB split UC transmission is scheduled.

[0311] Example 31 relates to the method of Example 26, wherein: the first PDCCH is scrambled with a first radionetwork temporary identifier (RNTI) to indicate that the TB repeats the UC transmission, and the first PDCCH is scrambled with a second RNTI to indicate that the TB segments the UC transmission.

[0312] Example 32 relates to the method of any one of Examples 26 to 31, further comprising: sending a second PDCCH, the second PDCCH scheduling a normal downlink UE transmission; the first PDCCH being scrambled with a first radio network temporary identifier (RNTI) to indicate that the first PDCCH is scheduling a downlink UC transmission to the first UE, and the second PDCCH being scrambled with a second RNTI to indicate that the second PDCCH is scheduling a normal downlink UE transmission to the first UE.

[0313] Example 33 relates to the method of any of Examples 26 to 31, wherein: for a TB repeated UC transmission, the first PDCCH includes a new data indicator (NDI) that indicates whether a new transmission or a retransmission is scheduled.

[0314] Example 34 relates to a method of any one of Examples 26 to 31, wherein: for TB-segmented UC transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI), the first NDI indicating whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicating whether the transmission to the second UE in the CUE role is scheduled as a new transmission or a retransmission.

[0315] According to Example 35, an apparatus in a network device includes at least one processor coupled to a memory storing instructions, the instructions causing the network device to perform a method when executed by the at least one processor, the method comprising: transmitting a first physical downlink control channel (PDCCH), the first PDCCH scheduling downlink UE cooperation (UC) transmission for a first UE in the role of a target UE (TUE); transmitting a first transport block (TB) to the first UE based on the first PDCCH; and transmitting a second TB to a second UE in the role of a cooperative UE (CUE).

[0316] Example 36 relates to the apparatus of Example 35, wherein: when the UC transmission is a repeating UC transmission of a transport block (TB), the second TB is a copy of the first TB; when the UC transmission is a segmented UC transmission of a transport block (TB), the second TB is different from the first TB.

[0317] Example 37 relates to the apparatus of Example 36, wherein: the first PDCCH includes an indication of whether the UC transmission is a TB repeated UC transmission or a TB split UC transmission.

[0318] Example 38 relates to the apparatus of Example 36 and further includes: sending higher-layer signaling to indicate whether the UC transmission is a TB repeated UC transmission or a TB segmented UC transmission.

[0319] Example 39 relates to the apparatus of Example 36, wherein: the first PDCCH includes only scheduling information for the first TB to indicate that the scheduled TB repeated UC transmission; the first PDCCH includes scheduling information for the first TB and the second TB to indicate that the scheduled TB segmented UC transmission.

[0320] Example 40 relates to the apparatus of Example 36, wherein: the first PDCCH includes scheduling information for two TBs, and when the scheduling information for the two TBs is the same, a TB duplicate UC transmission is scheduled, and when the scheduling information for the two TBs is different, a split TB UC transmission is scheduled.

[0321] Example 41 relates to the apparatus of Example 36, wherein: the first PDCCH is scrambled with a first radionetwork temporary identifier (RNTI) to indicate TB repeated UC transmission, and the first PDCCH is scrambled with a second RNTI to indicate TB segmented UC transmission.

[0322] Example 42 relates to an apparatus of any one of Examples 35 to 41, further comprising: transmitting a second PDCCH, the second PDCCH scheduling a normal downlink UE transmission; the first PDCCH being scrambled with a first radio network temporary identifier (RNTI) to indicate that the first PDCCH is scheduling a downlink UC transmission to the first UE, and the second PDCCH being scrambled with a second RNTI to indicate that the second PDCCH is scheduling a normal downlink UE transmission to the first UE.

[0323] Example 43 relates to an apparatus of any of Examples 36 to 41, wherein: for a TB repeated UC transmission, the first PDCCH includes a new data indicator (NDI) that indicates whether a new transmission or a retransmission is scheduled.

[0324] Example 44 relates to an apparatus of any one of Examples 36 to 41, wherein: for TB-segmented UC transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI), the first NDI indicating whether the transmission to the first UE is scheduled as a new transmission or a retransmission, and the second NDI indicating whether the transmission to the second UE in the CUE role is scheduled as a new transmission or a retransmission.

Claims

1. A method characterized by, Comprising: receiving a first physical downlink control channel (PDCCH) scheduling a downlink joint UE transmission from a transmitter for a first UE; receiving a first transport block (TB) from the transmitter based on the first PDCCH; receiving data from a second UE through an inter-UE connection.

2. The method of claim 1, wherein: the transmitter is a network device, and receiving the first TB based on the first PDCCH comprises receiving the first TB from the network device.

3. The method of claim 1, wherein: the transmitter is a third UE, and receiving the first TB based on the first PDCCH comprises receiving the first TB from the third UE.

4. The method of any one of claims 1-3, wherein: when the joint UE transmission is a TB repetition joint UE transmission, the data is a copy of the first TB, or the data can be used to generate the first TB; or when the joint UE transmission is a TB split joint UE transmission, the data is a second TB different from the first TB, or the data can be used to generate the second TB.

5. The method of claim 4, wherein: the first PDCCH comprises an indication of whether the joint UE transmission is the TB repetition joint UE transmission or the TB split joint UE transmission.

6. The method of claim 4, wherein, Further comprising: receiving higher layer signaling to indicate whether the joint UE transmission is the TB repetition joint UE transmission or the TB split joint UE transmission.

7. The method of claim 4, wherein: the first PDCCH comprises only scheduling information of the first TB to indicate that the TB repetition joint UE transmission is scheduled; or the first PDCCH comprises scheduling information of the first TB and the second TB to indicate that the TB split joint UE transmission is scheduled.

8. The method of claim 4, wherein: the first PDCCH comprises scheduling information of two TBs, and in a case that the scheduling information of the two TBs is the same, the TB repetition joint UE transmission is scheduled, and in a case that the scheduling information of the two TBs is different, the TB split joint UE transmission is scheduled.

9. The method of claim 4, wherein, the first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate the TB repetition joint UE transmission, and the first PDCCH is scrambled with a second RNTI to indicate the TB split joint UE transmission.

10. The method according to any one of claims 1 to 8, characterized in that, Further comprising: receiving a second PDCCH scheduling transmission of a normal downlink transmission to the first UE; wherein the first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the first PDCCH schedules the downlink joint UE transmission, and the second PDCCH is scrambled with a second RNTI to indicate that the second PDCCH schedules the normal downlink transmission to the first UE.

11. The method of any of claims 4-9, wherein: for the TB repetition joint UE transmission, the first PDCCH includes a new data indicator (NDI) indicating whether a new transmission or a retransmission is scheduled.

12. The method of any of claims 4-9, wherein: for the TB split joint UE transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI), the first NDI indicating whether a new transmission or a retransmission is scheduled for transmission to the first UE, and the second NDI indicating whether a new transmission or a retransmission is scheduled for transmission to the second UE.

13. An apparatus, comprising: at least one processor coupled with a memory storing instructions that, when executed by the at least one processor, cause a user equipment (UE) to perform a method comprising: receiving a first physical downlink control channel (PDCCH) scheduling a downlink joint UE transmission from a transmitter for the UE; receiving a first transport block (TB) from the transmitter based on the first PDCCH; receiving data from a second UE over an inter-UE connection.

14. The apparatus of claim 13, wherein: the transmitter is a network device, and receiving the first transport block (TB) based on the first PDCCH comprises receiving the first TB from the network device.

15. The apparatus of claim 13, wherein: the transmitter is a third UE, and receiving the first transport block (TB) based on the first PDCCH comprises receiving the first TB from the third UE.

16. The apparatus of any of claims 13-15, wherein: when the joint UE transmission is a TB repetition joint UE transmission, the data is a copy of the first TB or the data can be used to generate the first TB; or when the joint UE transmission is a TB split joint UE transmission, the data is a second TB different from the first TB or the data can be used to generate the second TB.

17. The apparatus of claim 16, wherein: the first PDCCH includes an indication of whether the joint UE transmission is the TB repetition joint UE transmission or the TB split joint UE transmission.

18. The apparatus of claim 16, wherein, the method further comprises: receiving higher layer signaling to indicate whether the joint UE transmission is the TB repetition joint UE transmission or the TB split joint UE transmission.

19. The apparatus of claim 16, wherein: the first PDCCH includes scheduling information for only the first TB to indicate that the TB repetition joint UE transmission is scheduled; or the first PDCCH includes scheduling information for both the first TB and the second TB to indicate that the TB split joint UE transmission is scheduled.

20. The apparatus of claim 16, wherein: The first PDCCH includes scheduling information of two TBs, in a case that the scheduling information of the two TBs is the same, scheduling is the TB repetition joint UE transmission, in a case that the scheduling information of the two TBs is different, scheduling is the TB split joint UE transmission.

21. The apparatus of claim 16, wherein, The first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate the TB repetition joint UE transmission, the first PDCCH is scrambled with a second RNTI to indicate the TB split joint UE transmission.

22. The apparatus of any one of claims 13-20, wherein, The method further includes: receiving a second PDCCH, the second PDCCH scheduling transmission of normal downlink transmission to the UE; wherein the first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the first PDCCH schedules the downlink joint UE transmission, the second PDCCH is scrambled with a second RNTI to indicate that the second PDCCH schedules the normal downlink transmission to the UE.

23. The apparatus of any of claims 16-21, wherein: for the TB repetition joint UE transmission, the first PDCCH includes a new data indicator (NDI) indicating whether scheduling is a new transmission or a retransmission.

24. The apparatus of any of claims 16-21, wherein: for the TB split joint UE transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI), the first NDI indicating whether scheduling of transmission to the UE is a new transmission or a retransmission, the second NDI indicating whether scheduling of transmission to the second UE is a new transmission or a retransmission.

25. A method, comprising: including: transmitting a first physical downlink control channel (PDCCH), the first PDCCH scheduling a downlink joint user equipment (UE) transmission from a transmitter for a first UE; transmitting a first TB of data from the transmitter to the first UE based on scheduling information in the first PDCCH; transmitting a second TB of data from the transmitter to a second UE.

26. The method of claim 25, wherein: when the joint UE transmission is a TB repetition joint UE transmission, the second TB is a copy of the first TB; or when the joint UE transmission is a TB split joint UE transmission, the second TB is different from the first TB.

27. The method of claim 26, wherein: the first PDCCH includes an indication of whether the joint UE transmission is the TB repetition joint UE transmission or the TB split joint UE transmission.

28. The method of claim 26, wherein, further including: transmitting higher layer signaling to indicate whether the joint UE transmission is the TB repetition joint UE transmission or the TB split joint UE transmission.

29. The method of claim 26, wherein: the first PDCCH includes scheduling information of only the first TB to indicate that scheduling is the TB repetition joint UE transmission; or the first PDCCH includes scheduling information of two TBs, in a case that the scheduling information of the two TBs is the same, scheduling is the TB repetition joint UE transmission, in a case that the scheduling information of the two TBs is different, scheduling is the TB split joint UE transmission. The first PDCCH includes scheduling information of the first TB and the second TB to indicate that the TB splitting joint UE transmission is scheduled.

30. The method of claim 26, wherein: The first PDCCH includes scheduling information of two TBs, in a case that the scheduling information of the two TBs is the same, the TB repetition joint UE transmission is scheduled, in a case that the scheduling information of the two TBs is different, the TB splitting joint UE transmission is scheduled.

31. The method of claim 26, wherein, The first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate the TB repetition joint UE transmission, the first PDCCH is scrambled with a second RNTI to indicate the TB splitting joint UE transmission.

32. The method of any one of claims 26-30, wherein, Further comprising: transmitting a second PDCCH, the second PDCCH scheduling a transmission of a normal downlink UE transmission; The first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the first PDCCH schedules the downlink joint UE transmission to the first UE, the second PDCCH is scrambled with a second RNTI to indicate that the second PDCCH schedules the normal downlink UE transmission to the first UE.

33. The method of any of claims 26-32, wherein: For the TB repetition joint UE transmission, the first PDCCH includes a new data indicator (NDI) indicating whether a new transmission or a retransmission is scheduled.

34. The method of any of claims 26-32, wherein: For the TB splitting joint UE transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI), the first NDI indicating whether a new transmission or a retransmission is scheduled for a transmission to the first UE, the second NDI indicating whether a new transmission or a retransmission is scheduled for a transmission to the second UE.

35. An apparatus comprising: An apparatus comprising at least one processor coupled with a memory storing instructions that, when executed by the at least one processor, cause a transmitter to perform a method comprising: transmitting a first physical downlink control channel (PDCCH), the first PDCCH scheduling a downlink joint user equipment (UE) transmission from the transmitter for a first UE; transmitting, from the transmitter to the first UE, a first transport block (TB) of data based on the first PDCCH; transmitting, from the transmitter to a second UE, a second TB of data.

36. The apparatus of claim 35, wherein: when the joint UE transmission is a transport block (TB) repetition joint UE transmission, the second TB is a copy of the first TB; or when the joint UE transmission is a transport block (TB) splitting joint UE transmission, the second TB is different from the first TB.

37. The apparatus of claim 36, wherein: The first PDCCH includes an indication of whether the joint UE transmission is the TB repetition joint UE transmission or the TB split joint UE transmission.

38. The device of claim 36, wherein, Further comprising: transmitting high layer signaling to indicate whether the joint UE transmission is the TB repetition joint UE transmission or the TB split joint UE transmission.

39. The apparatus of claim 36, wherein: The first PDCCH includes scheduling information of only the first TB to indicate that a TB repetition joint UE transmission is scheduled; or The first PDCCH includes scheduling information of both the first TB and the second TB to indicate that a TB split joint UE transmission is scheduled.

40. The apparatus of claim 36, wherein: The first PDCCH includes scheduling information of two TBs, and in a case that the scheduling information of the two TBs is the same, a TB repetition joint UE transmission is scheduled, and in a case that the scheduling information of the two TBs is different, a TB split joint UE transmission is scheduled.

41. The device of claim 36, wherein, The first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate the TB repetition joint UE transmission, and the first PDCCH is scrambled with a second RNTI to indicate the TB split joint UE transmission.

42. The apparatus of any one of claims 35-40, wherein, Further comprising: transmitting a second PDCCH, the second PDCCH scheduling transmission of a normal downlink UE transmission; The first PDCCH is scrambled with a first radio network temporary identifier (RNTI) to indicate that the first PDCCH schedules the downlink joint UE transmission to the first UE, and the second PDCCH is scrambled with a second RNTI to indicate that the second PDCCH schedules the normal downlink UE transmission to the first UE.

43. The apparatus of any of claims 36 to 41, wherein: For the TB repetition joint UE transmission, the first PDCCH includes a new data indicator (NDI) indicating whether a new transmission or a retransmission is scheduled.

44. The apparatus of any of claims 36 to 41, wherein: For the TB split joint UE transmission, the first PDCCH includes a first new data indicator (NDI) and a second new data indicator (NDI), the first NDI indicating whether a new transmission or a retransmission is scheduled for transmission to the first UE, and the second NDI indicating whether a new transmission or a retransmission is scheduled for transmission to the second UE.

45. A non-transitory computer readable medium, characterized in that, instructions that, when executed by an apparatus, cause the apparatus to perform the method of any of claims 1 to 12 or 25 to 34.

46. A communication system, characterized by comprise the apparatus of any of claims 13 to 24 and the apparatus of any of claims 35 to 44.

47. A computer program product, characterised in that, instructions that, when executed, cause an apparatus to perform the method of any of claims 1 to 12 or 25 to 34.

48. An apparatus comprising: comprise: one or more processors; a memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1-12 or 25-34.

Images