Terminal, wireless communication method and base station

Abstract

A terminal according to one embodiment of the present disclosure comprises: a reception unit for receiving information that pertains to a schedule; a transmission unit for transmitting, to other terminals, information that pertains to partial uplink (UL) data into which UL data is divided on the basis of at least one of transport block units, code word units, code block units and bit units; and a control unit for exercising control on the basis of information that pertains to the schedule so as to perform the transmission of the UL data in cooperation with the other terminals.

Description

[Technical Field]

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system. [Background technology]

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was specified with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered.

[0004] Existing systems (e.g., LTE systems) support MIMO (Multi-Input Multi-Output) systems as a wireless communication technology that transmits and receives data using multiple antennas to improve data rates (spectral efficiency). In a MIMO system, multiple transmit / receive antennas are provided on the transmitter and receiver, and different transmit information sequences are transmitted simultaneously from different transmit antennas.

[0005] Furthermore, in MIMO systems, there are specified single user MIMO (SU-MIMO (Single User MIMO)), in which transmission information sequences simultaneously transmitted from different transmitting antennas are all from the same user, and multi user MIMO (MU-MIMO (Multiple User MIMO)), in which transmission information sequences are from different users. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0007] In future wireless communication systems (for example, NR), it is being considered to extend the MIMO system to perform communication.

[0008] For example, it is assumed that UL transmission from a certain terminal will be performed using antennas / antenna ports of multiple terminals including the terminal (UE cooperative MIMO).

[0009] However, there has been insufficient consideration on how to control communications using multiple UE antennas / antenna ports.

[0010] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control communication even when communication is performed using antennas / antenna ports of multiple UEs. [Means for solving the problem]

[0011] A terminal according to one aspect of the present disclosure includes: a receiver for receiving information regarding a schedule of uplink (UL) data; and a receiver for receiving some UL data divided based on at least one of a transport block unit, a code word unit, a code block unit, and a bit unit from the UL data. and information regarding some of the UL data a control unit that controls transmission of the UL data scheduled based on information relating to the schedule in cooperation with the other terminals by transmitting to a base station a portion of the UL data that is not transmitted from the other terminals, Some The information about the UL data includes control information and channel state information about the UL data. and the transmitting unit transmits information about the part of UL data and the part of UL data to the other terminal using at least one of a channel used for device-to-device communication and a channel for a side link. It is characterized by: [Effects of the Invention]

[0012] According to one aspect of the present disclosure, even when communication is performed using antennas / antenna ports of a plurality of UEs, communication can be appropriately controlled. [Brief explanation of the drawings]

[0013] [Figure 1] 1A and 1B are diagrams illustrating an example of MU-MIMO and UE collaborative MIMO. [Figure 2] FIG. 2 is a diagram illustrating an example of antenna ports for UE collaborative MIMO. [Figure 3] FIG. 3 is a diagram illustrating an example of a synchronization signal in UE cooperative MIMO according to the first embodiment. [Figure 4] 4A and 4B are diagrams illustrating an example of communication control in UE cooperative MIMO according to the second embodiment. [Figure 5] FIG. 5 is a diagram illustrating another example of communication control in UE cooperative MIMO according to the second embodiment. [Figure 6]FIG. 6 is a diagram illustrating an example of resource allocation in UE cooperative MIMO according to the third embodiment. [Figure 7] 7A and 7B are diagrams illustrating an example of communication control in UE cooperative MIMO according to the fourth embodiment. [Figure 8] 8A and 8B are diagrams showing another example of communication control in UE cooperative MIMO according to the fourth embodiment. [Figure 9] 9A and 9B are diagrams showing another example of communication control in UE cooperative MIMO according to the fourth embodiment. [Figure 10] 10A and 10B are diagrams illustrating an example of DCI used for UE cooperative MIMO according to the fourth embodiment. [Figure 11] FIG. 11 is a diagram illustrating another example of communication control in UE cooperative MIMO according to the fourth embodiment. [Figure 12] FIG. 12 is a diagram illustrating another example of communication control in UE cooperative MIMO according to the fourth embodiment. [Figure 13] 13A and 13B are diagrams illustrating an example of control of information sharing between UEs in UE cooperative MIMO according to the fifth embodiment. [Figure 14] FIG. 14 is a diagram illustrating another example of control of information sharing between UEs in UE cooperative MIMO according to the fifth embodiment. [Figure 15] FIG. 15 is a diagram illustrating another example of control of information sharing between UEs in UE cooperative MIMO according to the fifth embodiment. [Figure 16] 16A and 16B are diagrams illustrating another example of control of information sharing between UEs in UE cooperative MIMO according to the fifth embodiment. [Figure 17] 17A and 17B are diagrams illustrating another example of control of information sharing between UEs in UE cooperative MIMO according to the fifth embodiment. [Figure 18] 18A and 18B are diagrams showing an example of SRS transmission in UE cooperative MIMO according to the sixth embodiment. [Figure 19]FIG. 19 is a diagram illustrating an example of SRS transmission and PUSCH transmission in UE cooperative MIMO according to the sixth embodiment. [Figure 20] FIG. 20 is a diagram showing another example of SRS transmission and PUSCH transmission in UE cooperative MIMO according to the sixth embodiment. [Figure 21] FIG. 21 is a diagram showing another example of SRS transmission and PUSCH transmission in UE cooperative MIMO according to the sixth embodiment. [Figure 22] FIG. 22 is a diagram showing another example of SRS transmission and PUSCH transmission in UE cooperative MIMO according to the sixth embodiment. [Figure 23] FIG. 23 is a diagram illustrating an example of retransmission control in UE cooperative MIMO according to the seventh embodiment. [Figure 24] FIG. 24 is a diagram illustrating another example of retransmission control in UE cooperative MIMO according to the seventh embodiment. [Figure 25] FIG. 25 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 26] FIG. 26 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 27] FIG. 27 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 28] FIG. 28 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] (MIMO extension) In future wireless communication systems, increasing the number of terminal antennas / antenna ports (hereinafter referred to as antenna ports) is being considered to improve communication throughput. However, increasing the number of antenna ports in a UE requires distance between the antenna ports, so the increase in the number of antenna ports is limited by factors such as the size of the UE.

[0015] When increasing the number of antenna ports per UE is limited, it is expected that UE cooperative MIMO (e.g., UE corporative MIMO), Tx / Rx diversity, or multi-user MIMO (MU-MIMO enhancement) will be used to improve UE throughput / cell capacity.

[0016] When UE cooperative MIMO is applied, even if there is an upper limit on the number of antenna ports due to constraints such as UE size, it is possible to increase the apparent number of antenna ports by using antenna ports of multiple UEs. It is also specified that spatial correlation is reduced by using antenna ports in different positions (or different antenna port numbers 9). UE cooperative MIMO may also be interpreted as UE collaborative MIMO, UE corporative MIMO, UE-to-UE cooperative transmission, UE-to-UE cooperative reception, UE-to-UE cooperative reception, etc.

[0017] When four antenna ports (or four ranks / four layers) are used in communications between a base station and multiple UEs, MU-MIMO is equivalent to SU-MIMO with a rank of two per UE (see Figure 1A). In contrast, UE cooperative MIMO is equivalent to SU-MIMO with a rank of four (or a virtual four-port antenna) (see Figure 1B).

[0018] For example, in UE cooperative MIMO (e.g., FIG. 1B), rank 4 data (e.g., DL data / DL-SCH) for UE#1 may be transmitted to UE#1-UE#2, and the data may be transferred from UE#2 to UE#1. This allows UE#1 to receive data equivalent to four antenna ports even if it has only two antenna ports.

[0019] Alternatively, in UE cooperative MIMO (e.g., FIG. 1B), data for UE#1 (e.g., UL data / UL-SCH) may be transmitted from UE#1-UE#2. This allows UE#1 to transmit data equivalent to four antenna ports (virtual four-port antennas) even if it has only two antenna ports.

[0020] In this way, it is assumed that UL transmission / DL reception of a certain terminal will be performed using the antennas / antenna ports of multiple terminals including the terminal itself (UE cooperative MIMO). This will enable communication using more antenna ports than the number of antenna ports supported by the terminal itself (see Figure 2). Figure 2 shows an example of communication using four antenna ports (virtual four antenna ports) by cooperation between UEs each having two antenna ports.

[0021] However, there has been insufficient consideration on how to control communications (eg, UL transmission processing / DL reception processing) using antenna ports of multiple UEs.

[0022] For example, the problem is how to synchronize between UEs (e.g., carrier frequency / phase / transmission timing). Another problem is how to share data / control information between UEs. Another problem is how to control scheduling / retransmission when transmitting using UE cooperative MIMO. Another problem is how to set the beam / TCI state / spatial relationship applied (or corresponding / associated) to each antenna port. Another problem is how to control retransmission when using UE cooperative MIMO.

[0023] Therefore, the present inventors have studied UE operations / base station operations that can solve at least one of the above problems and have come up with the idea for this embodiment.

[0024] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. The wireless communication methods (or UE operations / base station operations) according to the embodiments may be applied independently or in combination.

[0025] In the present disclosure, "A / B" and "at least one of A and B" may be read as interchangeable. Similarly, in the present disclosure, "A / B / C" and "at least one of A, B, and C" may be read as interchangeable. In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be read as interchangeable. In the present disclosure, index, ID, indicator, and resource ID may be read as interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be read as interchangeable.

[0026] In the present disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be read interchangeably.

[0027] In the present disclosure, the terms use, determine, apply, and select may be read interchangeably.

[0028] In this disclosure, the terms link, associate, correspond, and map may be read interchangeably. In this disclosure, the terms allocate, assign, monitor, and map may be read interchangeably.

[0029] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher layer parameters, RRC information elements (IEs), and RRC messages may be interchangeable.

[0030] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0031] In the present disclosure, acknowledgement information, HARQ-ACK, HARQ-ACK / NACK, HARQ-ACK information, HARQ, ACK / NACK, ACK, NACK, NACK only, and UCI may be interpreted as interchangeable.

[0032] In the present disclosure, specific, dedicated, UE-specific, and UE-individual may be read interchangeably.

[0033] In the present disclosure, common, shared, group-common, UE common, and UE shared may be read interchangeably.

[0034] In the present disclosure, a UE-specific DCI and a DCI having a CRC scrambled by a UE-specific RNTI may be interchangeable. The UE-specific RNTI may be, for example, a C-RNTI.

[0035] In the present disclosure, a UE common DCI and a DCI having a CRC scrambled by a UE common RNTI may be interchangeable. The UE common RNTI may be, for example, a multicast-RNTI.

[0036] In the following description, a case where two UEs (UE#1 and UE#2) perform cooperative transmission is shown, but the number of UEs performing cooperative transmission may be three or more. In the following description, a case where each UE includes two antenna ports is shown, but the number of antenna ports included in each UE is not limited to this. UE#1 and UE#2 may include the same number of antenna ports, or may include different numbers of antenna ports. In the following description, cooperative transmission in UL is taken as an example, but is not limited to this. A similar mechanism may also be applied when multiple UEs transmit DL data cooperatively.

[0037] (First embodiment) The UE may perform control to perform synchronization between UEs / antenna ports based on a predetermined synchronization signal.

[0038] When a UE performing UE cooperative transmission receives a predetermined synchronization signal, it may control synchronization with other UEs / synchronization with the antenna ports of other UEs based on the predetermined synchronization signal. In the present disclosure, a UE performing UE cooperative transmission may be interpreted as a UE in which predetermined higher layer parameters (e.g., parameters for UE cooperative MIMO) are set, or a UE that supports UE cooperative transmission.

[0039] The predetermined synchronization signal may be transmitted / set periodically or aperiodically. The predetermined synchronization signal may be transmitted in a resource or an occasion (see FIG. 3). The resource may be interpreted as a transmission resource, a reception resource, or a measurement resource. The occasion may be interpreted as a transmission occasion, a reception occasion, or a measurement occasion.

[0040] The resources / occasions of the synchronization signal may be notified / configured to the UE by the base station using higher layer signaling, etc. The UE may control reception of the predetermined synchronization signal based on the resources / occasions notified from the base station. The predetermined synchronization signal may always be transmitted on the configured resources / occasions, or may be transmitted on some of the multiple configured resources / occasions (or resource candidate / occasion candidate).

[0041] When the UE receives the synchronization signal, the UE may be controlled to perform synchronization (time / frequency synchronization) after a predetermined time has elapsed. The predetermined time may be defined in the specifications, may be notified / configured to the UE by the base station through higher layer signaling, or may be determined based on the reported UE capability information.

[0042] The UE may control synchronization using multiple synchronization signals, or may control synchronization using a single synchronization signal. For example, when multiple synchronization signals are used, the UE may control synchronization by applying an averaging process to reception results of multiple synchronization signals received in the past. When a single synchronization signal is used, the UE may control synchronization each time it receives a synchronization signal.

[0043] The predetermined synchronization signal may be transmitted from a network (e.g., a base station). Alternatively, the predetermined synchronization signal may be transmitted from another UE / an antenna port of another UE. The other UE may be a cooperating UE or a paired UE when cooperative transmission / cooperative reception is performed between UEs / antenna ports.

[0044] The synchronization signal may be a channel / signal (e.g., SSB / TRS / CSI-RS) of an existing system (e.g., Rel. 16 or earlier), or a new channel / signal. The synchronization signal used for synchronization between a base station and a UE and the synchronization signal used for synchronization among multiple UEs may be set in common or separately.

[0045] When a UE receives / detects a synchronization signal in a resource / occasion used for transmitting the synchronization signal, the UE may use the received / detected synchronization signal to determine the timing of cooperative transmission / cooperative reception between UEs / antenna ports.

[0046] The resource / occasion of the synchronization signal may be a resource / occasion for synchronization between the base station and the UE, or may be a resource / occasion for synchronization between UE and UE (between antenna ports). Alternatively, both the resource / occasion for synchronization between the base station and the UE and the resource / occasion for synchronization between UE and UE (between antenna ports) may be configured.

[0047] In this way, by using a synchronization signal to synchronize a UE (or an antenna port of a UE) with another UE (or an antenna port of another UE), UE cooperative MIMO can be appropriately controlled.

[0048] (Second embodiment) The UE may control the sharing of predetermined information with other UEs that employ UE cooperative MIMO. The predetermined information may be at least one of transmission data, control information, and channel state information. The transmission data may be interpreted as transmission data information, UL data, DL data, UL-SCH, or DL-SCH.

[0049] In the following explanation, we will use an example of transmitting transmission data (or PUSCH / UL data / UL-SCH) in UE cooperative MIMO, but the same can be applied to cooperative transmission of other UL signals / UL channels (e.g., uplink control information / PUCCH).

[0050] 4A and 4B show an example of a case where a first UE (UE#1) and a second UE (UE#2) perform cooperative UL transmission. In FIG. 4A, UE#1 uses antenna ports #0 and #1, and UE#2 uses antenna ports #2 and #3, and transmits using a virtual four-port antenna. Note that the number of antenna ports of each UE (two each in this case), the number of ranks / layers used for cooperative transmission (four in this case), and the number of UEs performing cooperative transmission (two in this case) are not limited to these.

[0051] 4B, the base station transmits information regarding an UL transmission instruction to the UE. In the present disclosure, the information regarding an UL transmission instruction may be interpreted as information regarding scheduling of UL transmission, information regarding triggering of UL transmission, an UL grant, or a DL assignment (in the case of cooperative reception in DL).

[0052] Here, a case is shown in which UE#1's transmission data (e.g., a portion of the transmission data) is also transmitted from UE#2. In this case, information regarding UE#1's transmission data may be reported / notified / transferred / shared (hereinafter also referred to as "transferred / information shared") to UE#2. In other words, information regarding UE#1's transmission data is shared between UE#1 and UE#2.

[0053] The transmission data of UE#1 may be interpreted as UL data / UL-SCH corresponding to UE#1 or UL data / UL-SCH for UE#1. Note that UL data / UL-SCH may be interpreted as UL control information / UCI.

[0054] Information sharing between UE#1 and UE#2 may be performed by transmitting / notifying predetermined information from UE#1 to UE#2. Existing communication methods such as unlicensed bands (or shared spectrum), Wi-Fi, Bluetooth (registered trademark), etc. may be applied to the information sharing. For example, in FIG. 4B, UE#1 may transfer / share predetermined information with UE#2 using a higher layer. In other words, higher layer signaling may be used in communication between UEs.

[0055] Alternatively, information may be shared between UE#1 and UE#2 as a periodic report configured by the base station. Alternatively, information may be shared between UE#1 and UE#2 as an aperiodic report triggered by the base station. Alternatively, information may be shared between UE#1 and UE#2 autonomously. Alternatively, each UE may be configured to instruct / command other UEs to report or share specific information.

[0056] Alternatively, based on specifications supported by D2D (e.g., physical layer specifications / RAN1 specifications), information may be shared between UEs using a channel for D2D, and coordinated transmission may be performed between multiple UEs using the shared information.

[0057] 4B shows a case where UE#1's transmission data (e.g., a portion of the transmission data) is transmitted from UE#2, but this is not limiting. UE#2's transmission data (e.g., a portion of the transmission data) may be transmitted from UE#1. In this case, UE#2 may share / provide information to UE#1 (see FIG. 5).

[0058] 5 shows a case where information relating to UE#1's transmission data (e.g., a portion of the transmission data) is transferred from UE#1 to UE#2, and information relating to UE#2's transmission data (e.g., a portion of the transmission data) is transferred from UE#2 to UE#1. The method for transferring transmission data from UE#2 to UE#1 may be controlled in the same way as the method for transferring transmission data from UE#1 to UE#2.

[0059] In this way, by performing cooperative transmission among multiple UEs after information sharing among them based on instructions from the base station, cooperative transmission can be appropriately controlled.

[0060] (Third embodiment) When transmission / reception is performed using UE collaborative MIMO, certain parameters / configurations may be controlled to be shared between UEs / antenna ports. In this case, some parameters / configurations (e.g., a first parameter / configuration) may be commonly set between UEs / antenna ports, while other parameters / configurations (e.g., a second parameter / configuration) may be separately (e.g., differently) set between UEs / antenna ports.

[0061] The predetermined parameter / configuration may be at least one of a demodulation reference signal setting (e.g., DMRS setting or DMRS configuration), the number of layers / ranks (e.g., the number of MIMO layers / MIMO ranks), transmission signal resources, and DMRS resources.

[0062] The DMRS configuration may be at least one of a DMRS symbol number in the time direction, whether or not an additional DMRS is inserted, and a DMRS type in the frequency direction (for example, type 1 or type 2).

[0063] The transmission signal resource (or resource) may be at least one of time, frequency, CDM / orthogonal code, sequence number, and cyclic shift number. The DMRS resource may be at least one of time, frequency, CDM / orthogonal code, sequence number, cyclic shift number, comb index (e.g., comb index), and CDM group index (e.g., CDM group index). Information regarding the transmission signal resource / DMRS resource may be dynamically notified to the UE by the base station using DCI when instructing (or scheduling) a transmission.

[0064] A network (e.g., a base station) may use higher layer / physical layer control information (e.g., DCI) to set predetermined parameters / configurations to a predetermined UE. The predetermined UE may be a plurality of UEs that perform coordinated transmission, or may be a portion of the UEs that perform coordinated transmission (e.g., UEs corresponding to data to be transmitted (or UEs that are the source of data transmission)). The predetermined parameters / configurations may be set separately (e.g., for coordinated transmission) from normal transmission (e.g., UE-to-base station transmission).

[0065] When predetermined parameters / configurations are configured by higher layer / physical layer control information (e.g., DCI), the UE may assume that the same contents are configured in the UE / antenna port (e.g., paired UE / antenna port) that performs coordinated transmission. Alternatively, the UE may assume that the same contents are configured for some parameters / configurations and different contents are configured for other parameters / configurations.

[0066] Alternatively, when a predetermined parameter / configuration is set, the UE may notify / instruct the paired UE / antenna port of the same (or different) content. The notification to the paired UE / antenna port may be performed using the method used for information sharing between UEs in the second aspect.

[0067] For example, the DMRS symbol number etc. may be set to the same value among multiple UEs (e.g., between UE#1 and UE#2), and the DMRS Comb index / CDM group index etc. may be set to different values ​​(e.g., different values) among multiple UEs. Transmission signal resources may be set to overlap with each other among multiple UEs, or may be set to different values ​​(e.g., different values) among multiple UEs.

[0068] 6 is a diagram showing an example of resource configuration / resource allocation for UE#1 and UE#2 that transmit cooperatively. Here, a case is shown in which UE#1 transmits using antenna ports #0 and #1, and UE#2 transmits using antenna ports #2 and #3. Also shown is a case in which the same content is configured as the first parameter / configuration (here, DMRS symbols) for UE#1 and UE#2, and different content is configured as the second parameter / configuration (here, Comb index). Note that the content of the first parameter / configuration and the second parameter / configuration is not limited to this.

[0069] Also, while Figure 6 shows a case where the transmission signal resources of UE#1 and UE#2 overlap, this is not limited to this, and the transmission signal resources of UE#1 and UE#2 may not overlap (or may overlap partially).

[0070] In this way, by setting some parameters in common and other parameters separately for multiple UEs that perform UE cooperative MIMO, it becomes possible to appropriately control UE cooperative MIMO transmission.

[0071] (Fourth embodiment) When transmission / reception is performed using UE cooperative MIMO, the base station uses a predetermined DCI to transmit information about a schedule to at least one UE among multiple UEs that perform cooperative transmission.

[0072] The information about the schedule may include at least one of frequency resources, time resources, transmission timing, and reception timing to be used for transmission / reception. Also, the information about the schedule may be interpreted as information about an UL transmission instruction or information about a DL reception instruction.

[0073] Transmission of information related to the schedule may be controlled based on at least one of the following aspects 4-1 to 4-3. Which of aspects 4-1 to 4-3 to apply may be defined in the specifications, or may be switched and set using higher layer signaling / DCI, etc. The aspects that can be set may be limited based on the capability information of the UE (or capability information reported from the UE).

[0074] <Aspect 4-1> The DCI used for UL transmission instruction / scheduling may be a UE-specific DCI. That is, each UE may be scheduled with its own DCI (see FIG. 7A). The UE uses the schedule information addressed to itself to transmit data in cooperation with other UEs (e.g., UL coordinated MIMO transmission).

[0075] In Figure 7A, the base station transmits schedule information to UE #1 and UE #2. Here, the base station may transmit information about the schedule to UE #1 using DCI corresponding to UE #1 (e.g., UE #1-specific DCI). The base station may also transmit information about the schedule to UE #2 using DCI corresponding to UE #2 (e.g., UE #2-specific DCI).

[0076] UE#1 notifies UE#2 of information such as transmission data (information sharing). For example, UE#1 may transfer / share information to UE#2 regarding transmission data to be transmitted using UE#2 (or the antenna port of UE#2).

[0077] UE#1 / UE#2 transmit cooperatively based on information about the schedule received from the base station. Here, a case is shown in which UL data corresponding to UE#1 is transmitted from UE#1 (or the antenna port of UE#1) and UE#2 (or the antenna port of UE#2). Note that the information to be transmitted cooperatively is not limited to UL data (or UL-SCH) and may be UL control information (e.g., UCI).

[0078] In this way, by notifying each UE of schedule-related information using UE-specific DCI, it is possible to flexibly control the schedule for each UE.

[0079] Variations 7A shows a case where UE#1 notifies UE#2 of information such as transmission data (information sharing), but this is not limited to this. UE#2 may also notify UE#1 of information such as transmission data (information sharing) (see FIG. 7B).

[0080] 7B shows a case where the base station notifies UE#1 of first schedule information and notifies UE#2 of second schedule information. Schedule information #1 and #2 may include at least one of (e.g., both) information on resources used for transmitting information notified from UE#1 to UE#2 (e.g., information share 1) and information on resources used for transmitting information notified from UE#2 to UE#1 (e.g., information share 2).

[0081] <Aspect 4-2> The DCI used for UL transmission instruction / schedule may be transmitted to only some of the UEs among multiple UEs. In other words, information about the schedule may be notified to only some of the UEs by UE-specific DCI (see FIG. 8A). The information about the schedule may include information about the schedule for other terminals in addition to information about the schedule for the UE to which the DCI is transmitted.

[0082] In Fig. 8A, the base station transmits schedule information to UE #1. Here, the base station may transmit information regarding the schedule to UE #1 using DCI CRC-scrambled with the RNTI (e.g., C-RNTI) corresponding to UE #1. The DCI may include information regarding scheduling for UE #1 and information regarding scheduling for UE #2.

[0083] UE#1 may notify UE#2 of information related to UE#2's schedule as part of information sharing between UEs. UE#2 may transmit UL data (e.g., UL data notified from UE#1) using inter-UE cooperative MIMO based on the acquired scheduling information. Note that the information to be cooperatively transmitted is not limited to UL data (or UL-SCH) and may also be UL control information (e.g., UCI).

[0084] In this way, by notifying information about the schedule using DCI only to some UEs, it is possible to suppress an increase in the number of DCIs to be transmitted.

[0085] Variations 8A shows a case where UE#1 notifies UE#2 of information such as transmission data (information sharing), but this is not limited to this. Information such as transmission data may also be notified (information sharing) from UE#2 to UE#1 (see FIG. 8B).

[0086] In Figure 8B, the schedule information notified to UE#1 by the base station may include at least one (e.g., both) of information regarding resources used to transmit information notified from UE#1 to UE#2 (e.g., information share 1) and information regarding resources used to transmit information notified from UE#2 to UE#1 (e.g., information share 2).

[0087] <Aspect 4-3> The DCI used for the UL transmission instruction / schedule may be a DCI common to multiple UEs (e.g., a group-common DCI). That is, information related to the schedule may be notified to multiple UEs (e.g., UE#1 and UE#2) by the group-common DCI (see FIG. 9A).

[0088] 9A, the base station transmits schedule information to UE#1 and UE#2. Here, the base station may transmit information about the schedule to multiple UEs (e.g., a pair of UE#1 and UE#2) using DCI CRC-scrambled with a common RNTI. The DCI may include information about scheduling for UE#1 and information about scheduling for UE#2.

[0089] Each UE may obtain information related to scheduling addressed to the UE from the group common DCI. A common RNTI for multiple UEs may be notified / configured to the UE from the base station by higher layer signaling or the like.

[0090] UE#1 notifies UE#2 of information such as transmission data (information sharing). For example, UE#1 may transfer / share information to UE#2 regarding transmission data to be transmitted using UE#2 (or the antenna port of UE#2).

[0091] UE#1 / UE#2 transmit cooperatively based on information about the schedule received from the base station. Here, a case is shown in which UL data corresponding to UE#1 is transmitted from UE#1 (or the antenna port of UE#1) and UE#2 (or the antenna port of UE#2). Note that the information to be transmitted cooperatively is not limited to UL data (or UL-SCH) and may be UL control information (e.g., UCI).

[0092] In this way, by notifying information about the schedule using DCI that is common to multiple UEs, it becomes unnecessary to transmit DCI separately to each UE.

[0093] Variations 9A shows a case where UE#1 notifies UE#2 of information such as transmission data (information sharing), but this is not limited to this. UE#2 may also notify UE#1 of information such as transmission data (information sharing) (see FIG. 9B).

[0094] In Figure 9B, the schedule information notified to UE#1 and UE#2 by the base station may include at least one (e.g., both) of information regarding resources used to transmit information notified from UE#1 to UE#2 (e.g., information share 1) and information regarding resources used to transmit information notified from UE#2 to UE#1 (e.g., information share 2).

[0095] In aspect 4-1, each UE may assume that scheduling (for example, resource control) of UL data (or UL-SCH) or PUSCH transmitted by the UE is performed based on DCI addressed to the UE.

[0096] In example 4-2 / example 4-3, UE#1 may receive control information addressed to UE#2. In this case, one DCI can be used to transmit control information addressed to each UE.

[0097] When a control signal addressed to each UE (here, UE#1 and UE#2) is transmitted using one DCI, a separate DCI field may be set for each UE in the DCI (option 4-1). Alternatively, a DCI field common to all UEs may be set in the DCI, and a different value may be transmitted for each UE (option 4-2).

[0098] Option 4-1 In one DCI, an individual DCI field may be defined for each UE (see FIG. 10A). FIG. 10A shows a case where a TPMI field is set for each UE in DCI. For example, in an existing DCI field, the TPMI field may be extended to set a field that can indicate a different TPMI for each UE.

[0099] The DCI field for each UE may be only a predetermined DCI field (or a predetermined type). For a field for which an individual DCI field for each UE is not set, a common value may be assumed between UEs (or may be commonly applied between UEs).

[0100] The DCI field that is individually set for each UE may be a field related to at least one of a precoder for UL MIMO, a rank indication, a UL beam indication (e.g., TPMI / SRI), and a TPC command (e.g., a TPC command for PUSCH).

[0101] Alternatively, when the DMRS Comb index (or CDM group index) is indicated in the DCI, a field related to the DMRS Comb index (or CDM group index) may be set individually for each UE.

[0102] Alternatively, when different resource indications are supported between UEs, the fields related to time resources / frequency resources may be set individually for each UE.

[0103] The DCI field that is set to be the same / common for each UE may be a DCI format indicator field, a timing indicator field, or the like.

[0104] Option 4-2 A different value may be notified for each UE in a DCI field that is common to the UEs (see FIG. 10B). For example, information on the codepoint of each DCI (or each bit value of the DCI field) may be configured for each UE by higher layer signaling or the like.

[0105] 10B shows a case where a TPMI field corresponding to UE#1 and UE#2 is set in common in the DCI, and the correspondence between the code point of the TMPI field and the TMPI index is set separately for each UE. This makes it possible to specify a different TPMI index for each UE using the common TPMI field.

[0106] <DCIフォーマット> A predetermined DCI format may be defined for UL transmission (e.g., PUSCH transmission) coordinated between UEs. Alternatively, a predetermined DCI format may be defined for resource allocation / scheduling used for signal transmission (e.g., information sharing) between UEs. The predetermined DCI format may be configured by, for example, replacing bits in an existing DCI format.

[0107] For example, a predetermined DCI format may include at least one of a field used for coordinated UL transmission (e.g., PUSCH transmission) and a field indicating resources used for UE-to-UE signaling (e.g., information sharing between UEs).

[0108] The base station may use a predetermined DCI format to indicate at least one (e.g., both) of a schedule for PUSCH transmission (e.g., UL coordinated PUSCH transmission) and conditions / schedules for UE-to-UE signal transmission in UE-to-UE communication (e.g., resource allocation, etc.) (see FIG. 11).

[0109] The field used for PUSCH transmission (e.g., UE cooperative PUSCH transmission) may be a field related to at least one of a precoder for UL MIMO, a rank indication, a UL beam indication (e.g., TPMI / SRI), and a TPC command (e.g., a TPC command for PUSCH).

[0110] Alternatively, if the DMRS Comb index (or CDM group index) is indicated in the DCI, the field related to the DMRS Comb index (or CDM group index) may be set.

[0111] Alternatively, if different resource indications are supported between UEs, a field related to time resource / frequency resource may be set.

[0112] The field indicating the resources used for UE-to-UE signaling may be a field related to time resources / frequency resources or a field related to TPC commands. The field related to time resources / frequency resources may be set when different resource indications are supported between UEs. The field related to TPC commands may be set when closed-loop TPC (e.g., CL-TPC) is used for UE-to-UE signaling.

[0113] A predetermined DCI (or a predetermined PDCCH) indicating at least one of inter-UE coordinated PUSCH transmission and resource allocation / schedule for inter-UE signal transmission may be configured to be received / detected in a predetermined control resource set / search space. The predetermined control resource set / search space may be interpreted as at least one of a predetermined time resource, a predetermined frequency resource, and a predetermined subcarrier spacing.

[0114] The UE may attempt to detect (e.g., blindly detect) DCI indicating UE collaborative PUSCH transmission in a given control resource set / search space, and may be controlled not to detect DCI (or PDCCH) corresponding to UE collaborative PUSCH transmission in other control resource sets / search spaces.

[0115] Alternatively, a given DCI (or a given PDCCH) may be configured to be received / detected in any control resource set / search space.

[0116] The UE may attempt to detect (e.g., blindly detect) DCI indicating UE collaborative PUSCH transmission in the configured control resource set / search space. The UE may determine whether a UE collaborative PUSCH is scheduled based on whether a predetermined DCI (or a predetermined PDCCH) is CRC-scrambled with the RNTI for UE collaborative PUSCH transmission. Alternatively, the UE may determine whether a UE collaborative PUSCH is scheduled based on a predetermined field of the DCI.

[0117] <Use multiple DCIs> In the fourth embodiment, a case has been shown in which the following operations 1 and 2 are performed using one DCI (or PDCCH). Action 1: Scheduling UE cooperative PUSCH and allocating inter-UE signaling resources Operation 2: Scheduling PUSCH (e.g., PUSCH resources) of UE#1 and scheduling PUSCH of UE#2

[0118] The fourth embodiment is not limited to this, and DCI / PDCCH may be transmitted multiple times (for example, twice). Part of the information (for example, information related to the schedule) may be transmitted in the first DCI, and the remaining information may be transmitted in the second DCI. This reduces the number of DCI bits per transmission, and can reduce the coding rate and improve the error rate.

[0119] For example, UE shared information may be transmitted using a first DCI, and UE-specific information may be transmitted using a second DCI (see FIG. 12).

[0120] The first DCI may be CRC-scrambled with an RNTI corresponding to a predetermined group common. The first DCI may include information on at least one of the resources, monitoring occasions, search spaces, and control resource sets of the second DCI / PDCCH. In this case, the number of times the second DCI is detected can be reduced.

[0121] The first DCI may include a DCI field common to UEs. For example, the first DCI may include a field specifying a parameter commonly configured between UEs. The field may be, for example, at least one of a PUSCH timing indication (e.g., timing indicator) field, a PUSCH time / frequency resource indication field, and an inter-UE signaling resource indication field.

[0122] The second DCI may be CRC-scrambled with a UE-specific RNTI. The second DCI may include a UE-specific DCI field. For example, the second DCI may include a field specifying a parameter to be configured individually for the UE. The field may be at least one of a UL MIMO precoder / rank indication field, a UL beam indication (TPMI / SRI) field, a DMRS comb index (or CDM group index) field, and a TPC command field.

[0123] 12 shows a case where the first DCI is group-common and the second DCI is UE-specific, but this is not limiting. Both the first DCI and the second DCI may be UE-specific. Furthermore, the first DCI and the second DCI may be transmitted in the same slot / same CC / same BWP, or in different slots / different CCs / different BWPs.

[0124] The first DCI / second DCI may include a DAI field (e.g., counter DAI / total DAI). The counter DAI indicates a count value of DCI (or PDCCH), and the total DAI indicates the total number of DCI (or PDCCH). This allows the UE to determine whether it has failed to detect the first DCI / second DCI based on the counter DAI / total DAI included in each DCI, even if it fails to receive one of the DCIs.

[0125] When reception of the first DCI and the second DCI (or two-step DCI) is configured / specified, if the UE receives only the first DCI (e.g., a group common DCI) or the second DCI (e.g., a UE-specific DCI), the UE may detect a reception error in either DCI.

[0126] If the first DCI and the second DCI include an HARQ process ID field, the UE may assume that the first DCI and the second DCI that include the same HARQ process ID correspond to each other. If the UE is unable to receive either the first DCI or the second DCI for the same HARQ process ID (e.g., within a predetermined time period), the UE may detect an error in either DCI.

[0127] The order of transmission / reception of the first DCI and the second DCI may be specified. For example, the second DCI may be transmitted / received after the first DCI. This can simplify the DCI error detection operation in the UE.

[0128] If an error occurs in any of the DCIs, the UE may perform control so as not to perform UE-to-UE communication / UE coordinated PUSCH transmission. If the base station does not receive a PUSCH transmission (UE coordinated PUSCH transmission) transmitted from the UE, the base station may determine that the UE has failed to detect the first DCI / second DCI, and may perform retransmission of the DCI.

[0129] Alternatively, if an error occurs in a predetermined DCI, the UE may be controlled not to perform UE-to-UE communication / UE cooperative PUSCH transmission. For example, if the UE fails to detect the first DCI and receives the second DCI, the UE may be controlled to perform UE-to-UE communication but not to perform UE cooperative PUSCH transmission. Furthermore, if the UE receives the first DCI but fails to detect the second DCI, the UE may be controlled not to perform both UE-to-UE communication and UE cooperative PUSCH transmission. This makes it possible to appropriately use the DCI that was correctly received.

[0130] (Fifth embodiment) When UL transmission is performed using UE cooperative MIMO, the UE may control data / control information including physical layer transmission data to be reported / notified / transferred / information shared (hereinafter also referred to as transfer / information sharing) to other UEs based on a predetermined unit / predetermined unit.

[0131] A UE may divide UL data to be transmitted by itself into predetermined units (see FIG. 13A) and transfer / share information with other UEs (see FIG. 13B). The predetermined unit may be at least one of a transport block (TB), a code word (CW), a code block (CB), and a bit unit. Although FIGS. 13A and 13B show a case where the data is divided into CB units, this is not limiting.

[0132] The UE may divide part of the TB / CW / CB of the UL data it transmits into data to be transmitted on its own UL-SCH and data to be transferred / shared with other UEs. By dividing the data into TB / CW / CB units, error detection / retransmission can be performed appropriately.

[0133] For example, when UL data is divided into CB units, even if an error occurs in the UL data (CB) transmitted from one UE, it is possible to retransmit only the erroneous CB. On the other hand, when UL data is divided into bit units, if some CBs are erroneous, control may be exercised so that all CBs are retransmitted.

[0134] The distinction between UL data transmitted by the own terminal (e.g., UE#1) and UL data transmitted by another UE (e.g., UE#2) (e.g., the boundary for dividing the UL data) may be set by a higher layer, etc., or may be determined based on a predetermined rule.

[0135] The setting by the higher layer may be based on the number of TB / CW / CB, the number of UL-SCH bits for each UE, or the coding rate of UL-SCH for each UE.

[0136] The predetermined rule may be to equalize the number of bits of the UL-SCH of a plurality of UEs (for example, UE#1 and UE#2). Based on the predetermined rule, the UE may divide the data corresponding to its own terminal (for example, the data transmitted from the antenna port of its own terminal to the base station) and the data corresponding to other terminals (for example, the data transmitted from the antenna port of other terminals to the base station). Among the divided data (for example, TB / CW / CB / bits), the UE may use the first half for its own terminal and the second half for other terminals.

[0137] <Inter-UE Information Sharing> When a UE (for example, UE#1) transfers / share information to another UE (for example, UE#2), it may utilize the mechanisms of communication systems other than 3GPP. For example, UE#1 may use a radio RAN (for example, WiFi), short-range data communication (for example, Bluetooth) to control the transmission of predetermined information to UE#2 (see Figure 14). A UE's notification of predetermined information by using the mechanisms of other communication systems may be equivalent to the transmission of physical layer information that the UE transfers to the upper layer for the purpose of inter-UE communication. UE#2 may be controlled to transmit the physical layer information received from the upper layer on the UL-SCH.

[0138] In Figure 14, UE#1 transmits CB#2 of the UL data (for example, CB#1 + CB#2) to UE#2 by using the upper layer. And it shows the case where UE#1 transmits CB#1 as UL data (for example, on the UL-SCH of UE#1), and UE#2 transmits CB#2 as UL data (for example, on the UL-SCH of UE#2).

[0139] Alternatively, when a UE (for example, UE#1) transfers / share information to another UE (for example, UE#2), it may utilize the inter-UE transmission / reception method of the physical layer. For example, UE#1 may use at least one of the D2D channel and the sidelink to control the transmission of predetermined information to UE#2 (see Figure 15).

[0140] 15 shows a case where UE#1 transmits CB#2 of UL data (e.g., CB#1+CB#2) to UE#2 using D2D / sidelink. UE#1 transmits CB#1 as UL data (e.g., on the UL-SCH of UE#1), and UE#2 transmits CB#2 as UL data (e.g., on the UL-SCH of UE#2).

[0141] When a physical layer inter-UE transmission / reception scheme is used, the base station may control the schedule. When D2D / sidelink is applied to inter-UE information sharing, at least one of a configuration in which resources are autonomously selected among multiple UEs to control transmission (aspect 5-1) and a configuration in which a base station selects / schedules transmission resources among multiple UEs to control transmission (aspect 5-2) may be applied.

[0142] <Aspect 5-1> When UEs autonomously select resources to control transmission, the base station may configure a resource pool for each UE using higher layer signaling. UEs may autonomously select resources based on the resource pool to transmit to other UEs (see FIGS. 16A and 16B).

[0143] 16A and 16B, UE#1 transmits some UL data (e.g., CB#2) of UL data (e.g., CB#1+CB#2) to UE#2 using resources included in a resource pool preset by a higher layer. UE#1 transmits CB#1 as UL data (e.g., on UL-SCH of UE#1), and UE#2 transmits CB#2 as UL data (e.g., on UL-SCH of UE#2). The base station may simultaneously schedule UL data for each UE and schedule coordinated transmission between UEs.

[0144] FIG. 16B shows a case where UE-specific DCI is transmitted to each UE (example 4-1), but the methods shown in example 4-2 / example 4-3 may also be applied.

[0145] When a UE for which a resource pool has been set by a higher layer transmits a signal in UE-to-UE communication, the UE selects a resource from the resource pool and transmits the signal to another terminal using the selected resource. In this case, the UE may autonomously perform carrier sensing or the like to determine the status of the resource pool (e.g., whether it is available or not), or may determine the status of the resource pool based on information notified / broadcast / instructed by the base station.

[0146] The resource pool may be selected randomly by the UE based on a random number or the like, or may be selected based on a predetermined rule. A receiving UE (e.g., UE #2) may receive / measure resources (or resource pools) configured by a higher layer and receive a signal addressed to the receiving UE. To determine whether a signal is addressed to the receiving UE, for example, the UE may determine whether a CRC inserted in the data can be solved based on the ID (or C-RNTI) of the receiving UE (e.g., CRC check).

[0147] Alternatively, UEs may not use a resource pool for information sharing between UEs. In this case, UEs may be controlled to transmit if resources are available, such as CSMA / CA (Carrier Sense Multiple Access / Collision Avoidance) for Wi-Fi or LBT (Listen Before Talk) for NRU (NR Unlicensed). The receiving side may decode the received signal and determine whether it is addressed to the receiving device based on information such as the MAC header.

[0148] <Aspect 5-2> When the base station selects resources for UE-to-UE transmission, the base station may instruct / schedule each UE on the resources to be used for UE-to-UE transmission. The UE may control the UE-to-UE transmission using the resources scheduled by the base station (see FIGS. 17A and 17B).

[0149] A data transfer source UE (here, UE#1) that has been allocated resources by the base station uses the allocated resources to divide physical layer data (TB / CW / CB) and transmits a portion of the data (here, CB#2) to another UE#2. A data transfer destination UE (here, UE#2) that has been allocated resources by the base station may measure / receive the allocated resources, receive the divided physical layer data (TB / CW / CB), and transmit it to the base station using the UL-SCH of UE2.

[0150] 17A and 17B, UE#1 transmits some UL data (e.g., CB#2) of UL data (e.g., CB#1+CB#2) to UE#2 using resources scheduled by the base station. UE#1 transmits CB#1 as UL data (e.g., on UL-SCH of UE#1), and UE#2 transmits CB#2 as UL data (e.g., on UL-SCH of UE#2). The base station may simultaneously schedule UL data for each UE and schedule coordinated transmission between UEs.

[0151] FIG. 17B shows a case where UE-specific DCI is transmitted to each UE (example 4-1), but the methods shown in example 4-2 / example 4-3 may also be applied.

[0152] (Sixth embodiment) When UE-cooperative MIMO is used for communication, the base station may determine channel information between each UE and the base station based on an UL signal transmitted from the UE. The UL signal may be a predetermined reference signal (e.g., SRS) or another signal.

[0153] The base station may instruct / configure / trigger each UE to transmit an UL signal / RS (hereinafter also referred to as SRS) before scheduling each UE (e.g., scheduling UE cooperative MIMO transmission / scheduling UE-to-UE signal transmission).The base station may determine the TPMI / SRI of each UE based on the received SRS.

[0154] In transmitting SRS, the SRS (here, SRS#1 and SRS#2) transmitted from each UE (e.g., UE#1 and UE#2) may use different SRS resources (see FIG. 18A). The base station may set different SRS resources for UE#1 and UE#2 using higher layer signaling, etc.

[0155] In this case, the SRS transmission timing (e.g., timing advance) may differ between UEs. If the transmission timing of the SRS transmitted from each UE differs, the base station may adjust the timing advance based on the SRS reception result. The UE may be controlled by the base station regarding the timing advance when transmitting the SRS.

[0156] When the timing advance is adjusted based on the SRS, the UE may receive a timing advance command (TA command in MAC CE) included in the MAC CE transmitted on the PDSCH after transmitting the SRS. When the UE receives the timing advance command, the UE may adjust the timing advance (or the UL transmission timing) based on the received information.

[0157] Alternatively, when transmitting SRS, the SRS (here, SRS#1 and SRS#2) transmitted from each UE (e.g., UE#1 and UE#2) may use the same / common SRS resource (see FIG. 18B). The base station may configure a common SRS resource for UE#1 and UE#2 using higher layer signaling, etc. Each UE transmits SRS in cooperation using one SRS resource.

[0158] In this case, it is necessary to align the SRS transmission timing (timing advance) between UEs. Therefore, the timing advance may be controlled to be adjusted based on UL transmission (e.g., PRACH / SRS / PUSCH / PUCCH, etc.) before SRS transmission.

[0159] The correspondence relationship between antenna ports may be the same during SRS transmission and PUSCH transmission (for example, during UE coordinated PUSCH transmission) (see FIG. 19). For example, a configuration may be adopted in which antenna ports are not swapped across UEs during SRS transmission and PUSCH transmission. Alternatively, a configuration may be adopted in which the UL beam (for example, SRI / spatial relationship) does not change during SRS transmission and PUSCH transmission.

[0160] The UE may assume that the beams (e.g., spatial relationship / TCI state / quasi-co-location) of each antenna port during PUSCH transmission are the same as those during the most recent SRS transmission. Figure 19 shows a case where the antenna ports (#0, #1) and spatial relationship (#1) corresponding to UE #1 during SRS transmission are the same as the antenna ports (#0, #1) and spatial relationship (#1) corresponding to UE #1 during PUSCH transmission. Similarly, it shows a case where the antenna ports (#2, #3) and spatial relationship (#2) corresponding to UE #2 during SRS transmission are the same as the antenna ports (#2, #3) and spatial relationship (#2) corresponding to UE #2 during PUSCH transmission.

[0161] FIG. 19 shows an example of PUSCH transmission, but the same mechanism / rule may also be applied to transmission of other UL signals / UL channels (for example, PUCCH) transmitted in cooperation between UEs.

[0162] When one or more UEs (e.g., UEs performing UE cooperative MIMO) transmit UL signals / UL channels, multiple beams (e.g., TCI states, spatial relationships, or quasi-co-location (QCL)) may be configured for one UL signal / UL channel (or resources of one UL signal / UL channel). The UL signal / UL channel may be interpreted as at least one of SRS, PUSCH, and PUCCH.

[0163] In this case, between SRS / PUSCH / PUCCH channels (or between signals and channels), the same antenna port may be mapped to the same physical antenna port (see FIG. 20). Also, between SRS / PUSCH / PUCCH channels (or between signals and channels), the same antenna port may be configured to correspond to the same beam (for example, TCI state, spatial relationship, or quasi-co-location).

[0164] In Fig. 20, the number of the antenna port for SRS transmission is the same as the number of the antenna port for PUSCH transmission. Furthermore, the same beam (e.g., TCI state, spatial relationship, or quasi-co-location) may be configured between antenna ports with the same number for SRS transmission and PUSCH transmission. Furthermore, multiple TCI states (e.g., TCI state #1 and TCI state #2) may be configured for a common SRS resource (e.g., SRS resource #1).

[0165] The phase may be continuous (coherent) between antenna ports #0 and #1, continuous (coherent) between antenna ports #2 and #3, and not continuous (coherent) between antenna ports #0-#1 and antenna ports #2-#3.

[0166] Also, it may be possible to set a separate (e.g., different) TCI state / spatial relationship / QCL for each antenna port (see FIG. 21). FIG. 21 shows a case where TCI state #1 and TCI state #2 are set for a common SRS resource (e.g., SRS resource #1). In this case, the TCI state may be mapped to each antenna port based on a predetermined rule. Here, a case is shown where a TCI state ID with a smaller index is mapped / associated with an antenna port number with a smaller number.

[0167] Specifically, TCI state #1 is set for antenna ports #0 and #1 of SRS resource #1, and TCI state #2 is set for antenna ports #2 and #3 of SRS resource #1. Also shown is a case where the same association between antenna ports and TCI states is maintained even for transmission of different UL signals / UL channels (e.g., PUSCH transmission). Specifically, TCI state #1 is set for antenna ports #0 and #1 of PUSCH resource #1, and TCI state #2 is set for antenna ports #2 and #3 of PUSCH resource #1.

[0168] <Variations> Although Fig. 21 shows a case where multiple beams (e.g., spatial relationships / TCI states / quasi-co-locations) are set for one UL signal / UL channel, this is not limiting. One beam (e.g., spatial relationships / TCI states / quasi-co-locations) may be set for each UL signal / UL channel (see Fig. 22). In other words, it may be possible to set separate (e.g., different) TCI states / spatial relationships / QCLs for each resource.

[0169] Figure 22 shows a case where TCI state #1 is set for SRS resource #1 (or antenna ports #0 and #1 corresponding to SRS resource #1), and TCI state #2 is set for SRS resource #2 (or antenna ports #2 and #3 corresponding to SRS resource #2).

[0170] Furthermore, the same association between antenna ports and TCI states may be used for transmission of different UL signals / UL channels (e.g., PUSCH transmission). For example, TCI state #1 may be set for PUSCH resource #1 (or antenna ports #0 and #1 corresponding to PUSCH resource #1), and TCI state #2 may be set for PUSCH resource #2 (or antenna ports #2 and #3 corresponding to PUSCH resource #2).

[0171] (Seventh embodiment) When communication is performed using UE cooperative MIMO, if a transmission error occurs (for example, if an error is detected in the base station) in data transmitted by each UE (for example, in units of TB / CW / CB), a predetermined retransmission control may be performed. The base station may instruct the UE to retransmit based on a CRC check or an error detection code.

[0172] For example, the UE may perform retransmission control based on at least one of example 7-1 and example 7-2. In the following description, a case where transmission data (or UL data) is divided in units of CB is taken as an example, but is not limited to this.

[0173] <Aspect 7-1> Regardless of which UL data (or which UE transmitted the UL data) is erroneous, the UE that transmitted the data (e.g., UE#1) may be controlled to retransmit the UL data (see FIG. 23). FIG. 23 shows a case where, of the UL data (e.g., CB#1+CB#2) of UE#1, CB#1 is transmitted from UE#1 (or the antenna port of UE#1) and CB#2 is transmitted from UE#2 (or the antenna port of UE#2).

[0174] If at least one of CB#1 and CB#2 is transmitted in error, UE#1 may control the CB to be retransmitted from UE#1. In this case, UE#1 may control the CB to be retransmitted only if it is erroneous, or may control the CB to be retransmitted including the CB that is not erroneous.

[0175] The resources used for retransmission may be resources (e.g., retransmission resources) different from the resources scheduled for UL data transmission. The retransmission resources may be defined in a specification or may be configured from the base station to the UE by higher layer signaling, etc. When the UE receives information regarding a retransmission instruction (or information regarding an error) from the base station, the UE may transmit a PUSCH for retransmission using a predetermined resource.

[0176] If an error is detected in at least one of CB#1 transmitted from UE#1 and CB#2 transmitted from UE#2, the base station may notify UE#1 (or UE#1 and UE#2) of information regarding a retransmission instruction. In this case, it is sufficient to control UE#1 to perform retransmission.

[0177] In this way, by controlling the UE (UE#1) that is the source of transmission or data transfer to perform retransmission, even if an error is detected in a CB that is not being transferred to other UEs, new UE-to-UE transfer for retransmission is not required.

[0178] <Aspect 7-2> The UE to perform retransmission may be determined / selected based on which UL data (or which UE transmitted the UL data) is erroneous.

[0179] Option A A UE (or a UE that missed a transmission) that is notified by the base station of an instruction to retransmit the CB sent at the time of the initial transmission (or that the CB is incorrect) may be controlled to retransmit the CB.

[0180] The base station may schedule PUSCH resources for transmitting retransmission data to the UE. The UE may transmit UL data instructed by the base station to be retransmitted using the scheduled resources. Note that the UE may perform control so as to retransmit only erroneous CBs, or may perform control so as to retransmit CBs including non-erroneous CBs.

[0181] The resources used for retransmission may be resources (e.g., retransmission resources) different from the resources scheduled for UL data transmission. The retransmission resources may be defined in a specification or may be configured from the base station to the UE by higher layer signaling, etc. When the UE receives information regarding a retransmission instruction (or information regarding an error) from the base station, the UE may transmit a PUSCH for retransmission using a predetermined resource.

[0182] The base station may notify the UE that transmitted the UL data of a retransmission instruction for the UL data. For example, if an error is detected in CB#1 transmitted from UE#1, the base station may notify UE#1 of information regarding the retransmission instruction. Also, if an error is detected in CB#2 transmitted from UE#2, the base station may notify UE#2 of information regarding the retransmission instruction. In this way, by having the UE that transmitted the UL data in error retransmit the data, new inter-UE transfer for the retransmission is unnecessary.

[0183] If an error is detected in one of the CBs (e.g., CB#2 transmitted from UE#2), the base station may notify both UEs (e.g., UE#1 and UE#2) of information regarding a retransmission command. In this case, retransmission may be performed only from UE#2, or retransmission may be performed from both UE#1 and UE#2.

[0184] Option B A UE (or a UE that missed a transmission) that is notified by the base station of an instruction to retransmit the CB sent during the initial transmission (or that the CB is incorrect) may be controlled not to retransmit the CB (so that another UE will send the incorrect CB).

[0185] For example, if an error is detected in CB#1 transmitted from UE#1, control may be performed so that CB#1 is retransmitted from UE#2 (see FIG. 24). In this case, UE#1 may transfer / share information about CB#1 to UE#2, and UE#2 may transmit CB#1 to the base station. The base station may notify UE#1 of information regarding a retransmission instruction, or may notify both UE#1 and UE#2 of information regarding a retransmission instruction. The transfer control from UE#1 to UE#2 may be applied to the above-mentioned embodiments (for example, the fifth embodiment).

[0186] If an error is detected in CB#2 transmitted from UE#2, control may be performed so that UE#1 retransmits CB#2. In this case, UE#1 knows the information about CB#2, so UE-to-UE transfer is not required. The base station may notify UE#1 of information regarding the retransmission instruction, or may notify both UE#1 and UE#2 of information regarding the retransmission instruction.

[0187] In this way, by performing retransmission from a UE other than the UE that made the mistake in transmission, retransmission can be performed from a UE in a better communication environment.

[0188] If an error is detected in the CBs from both UEs, control may be performed so that a specific UE (for example, UE #1) retransmits the CBs, or so that each UE retransmits the CBs.

[0189] (supplement) The above embodiment may be applied only to UEs that report support by UE capability signaling (for example, UE capability signaling). Also, in the above embodiment, a configuration is shown in which part of the data of UE#1 is also transmitted from UE#2, but based on this configuration, whether data transfer from UE#2 to U##1 (or whether bidirectional data transfer) is possible may be reported by another UE capability signaling.

[0190] The above embodiment may be configured to be applied when configured by a base station using a higher layer control signal, etc. In the above embodiment, UE#1 and UE#2 may be interpreted as a first UE and a second UE, a master UE and a slave UE, or a primary UE and a secondary UE.

[0191] (wireless communication system) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0192] 25 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0193] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0194] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0195] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0196] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0197] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0198] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be a frequency band higher than FR2.

[0199] Furthermore, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

[0200] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 interface, or the like) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0201] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0202] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0203] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0204] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0205] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0206] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

[0207] The PDSCH transmits user data, higher layer control information, System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit Master Information Block (MIB).

[0208] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0209] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

[0210] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0211] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

[0212] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0213] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0214] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted as DL-RS.

[0215] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

[0216] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0217] (base station) 26 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0218] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0219] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0220] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0221] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0222] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0223] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0224] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0225] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0226] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0227] The transceiver 120 (transmission processor 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0228] The transmitting / receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna .

[0229] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna .

[0230] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0231] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0232] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0233] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0234] The transceiver 120 may transmit information about the schedule to at least one of the multiple terminals. The control unit 110 may control reception of UL data transmitted in a coordinated manner from the multiple terminals based on the information about the schedule.

[0235] The transceiver 120 may transmit information about the schedule to at least one of the multiple terminals by using terminal-specific downlink control information or group-common downlink control information. The control unit 110 may control reception of UL data transmitted in a coordinated manner from the multiple terminals based on the information about the schedule.

[0236] The transceiver 120 may receive UL data transmitted in a coordinated manner from a plurality of terminals based on information regarding a schedule for transmission to at least one of the terminals. The control unit 110 may set resources or a resource pool to be used for transmitting information regarding a portion of UL data divided based on at least one of transport block units, codeword units, code block units, and bit units.

[0237] The transceiver 120 may receive sounding reference signals from multiple terminals. The controller 110 may control the reception of UL transmissions transmitted in coordination from multiple terminals based on information related to the schedule. The antenna port used for transmitting the sounding reference signal may be associated with the antenna port used for UL transmission.

[0238] (user terminal) 27 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0239] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0240] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0241] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.

[0242] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured from a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0243] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0244] The transmitting / receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0245] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0246] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0247] The transceiver 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0248] The transceiver 220 (transmission processor 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0249] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

[0250] The transmitting / receiving unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna 230.

[0251] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0252] The transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0253] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0254] The transmitting section and receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0255] The transceiver 220 may receive information regarding a schedule. The transceiver 220 may transmit information regarding at least a portion of the UL data to another terminal. The transceiver 220 may receive a synchronization signal used for synchronization with another terminal. The control unit 110 may control the transmission of the UL data in cooperation with another terminal based on the information regarding the schedule. The UL data may be transmitted using a rank or a number of layers greater than the number of antenna ports supported by at least one of the terminal and the other terminal. In the cooperative transmission of UL data, at least a portion of parameters may be set in common for a first demodulation reference signal corresponding to first UL data transmitted by the terminal and a second demodulation reference signal corresponding to second UL data transmitted by the other terminal.

[0256] The transceiver 220 may receive information about the schedule through terminal-specific downlink control information or group common downlink control information. The control unit 110 may control the transmission of UL data in cooperation with other terminals based on the information about the schedule. The terminal-specific downlink control information may include information about the schedule for the terminal and other terminals. The terminal-specific downlink control information or group common downlink control information may include at least one of first parameter information used for transmitting information about at least a portion of the UL data and second parameter information used for transmitting the UL data. The transceiver 220 may receive the first parameter information used for transmitting information about at least a portion of the UL data and the second parameter information used for transmitting the UL data using different downlink control information.

[0257] The transceiver 220 may transmit information about some UL data, which is obtained by dividing the UL data based on at least one of transport block units, codeword units, code block units, and bit units, to other terminals. The control unit 110 may control the transmission of UL data in cooperation with other terminals based on information about the schedule. The transceiver 220 may transmit information about some UL data to other terminals using a higher layer. The transceiver 220 may transmit information about some UL data to other terminals using a channel used for device-to-device communication (D2D) and a channel for sidelink. The transceiver 220 may transmit information about some UL data using any resource included in a resource pool or a scheduled resource.

[0258] The transceiver 220 may transmit a sounding reference signal. The transceiver 220 may receive information related to a schedule. The control unit 110 may control UL transmission in cooperation with other terminals based on the information related to the schedule. An antenna port used for transmitting the sounding reference signal may be associated with an antenna port used for UL transmission. At least one of a different pseudo-colocation, a different transmission configuration index, and a different spatial relationship may be set for each antenna port number. At least one of the same pseudo-colocation, the same transmission configuration index, and the same spatial relationship may be set for the same antenna port number in sounding reference signal transmission and UL transmission.

[0259] When retransmitting UL transmission transmitted in cooperation with other terminals, the control unit 110 may control so that retransmission is performed from a predetermined terminal.

[0260] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0261] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.

[0262] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 28 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0263] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0264] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0265] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0266] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0267] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

[0268] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

[0269] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as a secondary storage device.

[0270] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0271] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0272] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0273] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0274] (Variation) Note that terms explained in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0275] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0276] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

[0277] A slot may be composed of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol), and may be a time unit based on numerology.

[0278] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0279] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0280] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0281] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

[0282] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0283] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0284] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0285] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0286] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0287] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0288] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0289] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0290] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0291] The BWP may include an UL BWP (a BWP for UL) and a DL BWP (a BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0292] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0293] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0294] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0295] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0296] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0297] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0298] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0299] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0300] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0301] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0302] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0303] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0304] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0305] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0306] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

[0307] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0308] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0309] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0310] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0311] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, or the mobile object itself. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0312] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as uplink channel and downlink channel may be read as sidelink channel.

[0313] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0314] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0315] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the specific order presented.

[0316] Each aspect / embodiment described in the present disclosure may be related to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use 802.20, Ultra-Wide Band (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on and extend these systems. Furthermore, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0317] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0318] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0319] The term "determining," as used in this disclosure, may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0320] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0321] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0322] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

[0323] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0324] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0325] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0326] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0327] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0328] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0329] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. a receiver for receiving information regarding a schedule of uplink (UL) data; a transmitting unit configured to transmit, to another terminal, some UL data divided based on at least one of a transport block unit, a code word unit, a code block unit, and a bit unit, and information regarding the some UL data; a control unit that controls transmission of the UL data scheduled based on information related to the schedule in cooperation with the other terminals by transmitting to a base station a portion of the UL data that is not transmitted from the other terminals, The information regarding the part of UL data is information including control information and channel state information regarding the UL data, The terminal is characterized in that the transmitting unit transmits information regarding the part of the UL data and the part of the UL data to the other terminal using at least one of a channel used for device-to-device communication and a channel for a side link.

2. The terminal according to claim 1 , wherein the transmitting unit transmits the information about the part of UL data and the part of UL data using any resource included in a resource pool or a scheduled resource.

3. receiving information regarding a schedule of uplink (UL) data; transmitting, to another terminal, some UL data divided based on at least one of a transport block unit, a code word unit, a code block unit, and a bit unit, and information regarding the some UL data; transmitting a portion of the UL data that is not transmitted from the other terminals to a base station, thereby controlling the transmission of the UL data scheduled based on information related to the schedule in cooperation with the other terminals; transmitting information about the part of UL data and the part of UL data to the other terminal using at least one of a channel used for device-to-device communication and a channel for a side link; The wireless communication method for a terminal, wherein the information regarding the part of UL data includes control information and channel state information regarding the UL data.

4. a transmitter for transmitting information regarding a schedule of uplink (UL) data to a first terminal; a control unit that sets resources or a resource pool to be used for transmitting some UL data divided based on at least one of a transport block unit, a code word unit, a code block unit, and a bit unit of the UL data and information related to the some UL data; a receiving unit that receives, from the first terminal, a portion of the UL data that is not transmitted from a second terminal, and thereby receives the UL data that is scheduled according to information about the schedule that is transmitted in cooperation from the first terminal and the second terminal; The information regarding the part of UL data is information including control information and channel state information regarding the UL data, A base station characterized in that information regarding the portion of UL data and transmission of the portion of UL data are transmitted to the second terminal using at least one of a channel used for device-to-device communication and a channel for a side link.

Images