Terminal, wireless communication method, base station and system

Abstract

A terminal according to an aspect of this disclosure comprises a receiver that receives downlink control information for scheduling physical downlink shared channel (PDSCH) and a controller that determines whether the PDSCH is multicast or unicast on the basis of at least one of upper layer signaling and the downlink control information. An aspect of this disclosure makes it possible to properly receive multicast downlink data.

Description

[Technical field]

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of achieving higher capacity and greater sophistication of 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, etc.) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [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]

[0005] In future wireless communication systems (e.g., NR), it is expected that multiple user terminals (User Equipment (UE)) will communicate in an ultra-high density and high traffic environment.

[0006] In NR, in such an environment, it is assumed that multiple UEs will receive downlink data using multicast.

[0007] However, in the NR specifications to date, the reception of multicast downlink data by UEs has not been sufficiently considered. If the reception of downlink data using multicast is not performed properly, there is a risk of degradation of system performance, such as a decrease in throughput.

[0008] Therefore, the present disclosure relates to a terminal and a wireless communication method for appropriately receiving multicast downlink data. 、 base station and systems One of the aims is to provide. [Means for solving the problem]

[0009] A terminal according to an embodiment of the present disclosure includes a receiver that receives higher layer signaling indicating a search space and receives downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) within the search space, and a controller that determines whether the PDSCH is multicast or unicast based on the search space and the DCI. The control unit determines a time resource of the PDSCH based on the TDRA information for multicast when the PDSCH is determined to be a multicast in a case where time domain resource assignment (TDRA) information for unicast and TDRA information for multicast are set. . Effect of the Invention

[0010] According to one aspect of the present disclosure, multicast downlink data can be properly received. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing an example of a procedure for receiving a multicast PDSCH. [Diagram 2] FIG. 2 is a diagram showing another example of a procedure for receiving a multicast PDSCH. [Diagram 3] 3A to 3C are diagrams illustrating an example of NACK-only feedback. [Figure 4] 4A and 4B are diagrams showing an example of frequency resources used for a multicast PDSCH. [Diagram 5] FIG. 5 is a diagram illustrating an example of PUCCH resource configuration according to aspects 1-3. [Figure 6] FIG. 6 is a diagram illustrating an example of PUCCH resource configuration according to aspects 1-4. [Figure 7] FIG. 7 is a diagram illustrating an example of PUCCH resource configuration according to configuration method 1 of aspect 1-6. [Figure 8] FIG. 8 is a diagram illustrating an example of PUCCH resource configuration according to configuration method 2 of example 1-6. [Figure 9] 9A and 9B are diagrams illustrating an example of PUCCH resource configuration according to aspect 2-1. [Figure 10] 10A and 10B are diagrams showing an example of a method for determining whether a PDSCH is a multicast PDSCH or a unicast PDSCH according to the fifth embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a method for determining whether a PDSCH is a multicast PDSCH or a unicast PDSCH according to aspect 6-1. [Figure 12] FIG. 12 is a diagram showing an example of a method for determining whether a PDSCH is a multicast PDSCH or a unicast PDSCH according to aspect 6-2. [Figure 13] FIG. 13 is a diagram showing an example of PDSCH scheduling according to the sixth embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of PDCCH monitoring according to the seventh embodiment. [Figure 15]FIG. 15 is a diagram showing another example of PDCCH monitoring according to the seventh embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 19] FIG. 19 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 PREFERRED EMBODIMENTS

[0012] (PUCCH format) In future wireless communication systems (e.g., Rel. 15 and later, 5G, NR, etc.), configurations (formats, also called PUCCH formats (PFs)) for uplink control channels (e.g., PUCCHs) used to transmit uplink control information (UCI) are under consideration. For example, in Rel. 15 NR, support for five types of PFs 0 to 4 is under consideration. Note that the names of the PFs shown below are merely examples, and different names may be used.

[0013] For example, PF0 and PF1 are PFs used for transmitting UCI of up to 2 bits. For example, UCI may be at least one of delivery acknowledgement information (also called hybrid automatic repeat reQuest-Acknowledgement (HARQ-ACK), acknowledgement (ACK) or negative-acknowledgement (NACK), etc.) and scheduling request (SR). PF0 can be assigned to 1 or 2 symbols, and is therefore also called short PUCCH or sequence-based short PUCCH, etc. On the other hand, PF1 can be assigned to 4 to 14 symbols, and is therefore also called long PUCCH, etc. PF0 may transmit a sequence obtained by cyclic shifting a base sequence using a cyclic shift based on at least one of an initial cyclic shift (CS) index, a UCI value, a slot number, and a symbol number. In PF1, multiple user terminals may be code division multiplexed (CDM) within the same physical resource block (PRB) by time domain block spreading using at least one of CS and time domain (TD)-orthogonal cover code (OCC).

[0014] PF2-4 are PFs used for transmitting UCI of more than 2 bits (e.g., Channel State Information (CSI) or at least one of CSI, HARQ-ACK, and SR). PF2 can be allocated to 1 or 2 symbols, and is therefore also called a short PUCCH, etc. Meanwhile, PF3 and PF4 can be allocated to 4-14 symbols, and are therefore also called long PUCCH, etc. In PF4, multiple user terminals may be CDM-multiplexed using (frequency domain (FD)-OCC) block spreading before DFT.

[0015] For PF1, PF3, and PF4, intra-slot frequency hopping may be applied. symb Then, the length before frequency hopping (first hop) is floor(N symb / 2), and the length after frequency hopping (second hop) is ceil(N symb / 2).

[0016] The waveforms of PF0, PF1, and PF2 may be Cyclic Prefix (CP)-Orthogonal Frequency Division Multiplexing (OFDM). The waveforms of PF3 and PF4 may be Discrete Fourier Transform (DFT)-spread(s)-OFDM.

[0017] The allocation of resources (e.g., PUCCH resources) used for transmitting the uplink control channel is performed using higher layer signaling and / or downlink control information (DCI). Here, the higher layer signaling may be at least one of RRC (Radio Resource Control) signaling, system information (e.g., at least one of RMSI: Remaining Minimum System Information, OSI: Other System Information, MIB: Master Information Block, and SIB: System Information Block), and broadcast information (PBCH: Physical Broadcast Channel).

[0018] In addition, in NR, the number of symbols assigned to PUCCH (which may be called PUCCH assigned symbols, PUCCH symbols, etc.) can be determined as slot-specific, cell-specific, or user terminal-specific, or a combination of these. Since it is expected that the communication distance (coverage) will increase as the number of PUCCH symbols increases, it is assumed that the number of symbols will be increased for user terminals located farther away from a base station (e.g., eNB, gNB).

[0019] (NR Multicast / Broadcast) In NR up to Rel.16, the transmission of at least one of a signal and a channel (hereinafter referred to as a signal / channel) from a network to a UE is basically unicast transmission. In this case, it is assumed that each UE receives the same downlink (DL) data signal / channel (e.g., a downlink shared channel (PDSCH)) transmitted from the network to multiple UEs using multiple reception opportunities (reception occasions) corresponding to multiple beams (or panels) of the network.

[0020] In addition, in an ultra-high density and high traffic environment where many UEs are geographically concentrated (e.g., stadiums, etc.), it is assumed that multiple UEs will receive the same signal / channel simultaneously. In such a case, if multiple UEs are present in the same area and each UE receives the same signal / channel by unicast, it is considered that the reliability of communication can be ensured, but the efficiency of resource utilization will decrease.

[0021] A group scheduling mechanism is being studied to enable multicast / broadcast services (MBS) to be received by multiple UEs.

[0022] For example, it is being considered to schedule a multicast PDSCH using one or more DCIs, which may increase the size of the DCI (payload size, overhead).

[0023] In a Point-to-Point (PTP) transmission (distribution method), a RAN node (e.g., a base station) transmits separate copies of an MBS data packet over the air to each individual UE. In a Point-to-Multipoint (PTM) transmission (distribution method), a RAN node (e.g., a base station) transmits a single copy of an MBS data packet over the air to a set of UEs.

[0024] It is considered that PTP transmission uses a UE-specific PDCCH to schedule UE-specific PDSCH for multiple RRC connected UEs (RRC_CONNECTED UEs), the UE-specific PDCCH has a cyclic redundancy check (CRC) scrambled with a UE-specific radio network temporary identifier (RNTI) (e.g., C-RNTI), and the UE-specific PDSCH is scrambled with the same UE-specific RNTI.

[0025] It is being considered that PTM transmission method 1 uses a group-common PDCCH to schedule a group-common PDSCH for multiple RRC connected UEs in the same MBS group, the group-common PDCCH has a CRC scrambled with a group-common RNTI, and the group-common PDSCH is scrambled using the same group-common RNTI.

[0026] It is being considered that PTM transmission method 2 uses a UE-specific PDCCH to schedule a group-common PDSCH for multiple RRC connected UEs in the same MBS group, the UE-specific PDCCH has a CRC scrambled with a UE-specific RNTI (e.g., C-RNTI), and the group-common PDSCH is scrambled using the group-common RNTI.

[0027] Here, the UE-specific PDCCH / PDSCH can be identified by the target UE but cannot be identified by other UEs in the same MBS group, whereas the group-common PDCCH / PDSCH is transmitted in the same time / frequency resource and can be identified by all UEs in the same MBS group.

[0028] In addition, HARQ feedback is being considered to improve the reliability of MBS.

[0029] For an RRC connected UE receiving multicast, at least the PTM transmission scheme 1 may support at least one of the following feedback methods 1 and 2.

[0030] [Feedback method 1] HARQ-ACK feedback based on ACK / NACK for multicast (ACK / NACK based HARQ-ACK feedback, ACK / NACK based PUCCH, ACK / NACK transmission, ACK / NACK feedback) A UE that successfully decodes the PDSCH transmits an ACK, whereas a UE that fails to decode the PDSCH transmits a NACK.

[0031] [Feedback method 2] NACK-only based HARQ-ACK feedback for multicast (NACK-only based HARQ-ACK feedback, NACK-only based PUCCH, NACK-only transmission, NACK-only feedback) A UE that successfully decodes the PDSCH does not send an ACK, and a UE that fails to decode the PDSCH sends a NACK.

[0032] As in the example of Figure 1, the UE-specific (individual) DCI may schedule a UE-common PDSCH (multicast PDSCH) and a UE-specific (individual) PUCCH including a HARQ-ACK for the UE-common PDSCH. As in the example of Figure 2, the UE-common DCI may schedule a UE-common PDSCH (multicast PDSCH) and a UE-common PUCCH including a HARQ-ACK for the UE-common PDSCH.

[0033] HARQ-ACK resources for multicast PDSCH may overlap among multiple UEs. As in the example of FIG. 3A, ACK resources may not overlap among multiple UEs, but NACK resources may overlap. As in the example of FIG. 3B, when the base station does not receive a signal in the NACK resource (received power is equal to or less than a threshold), the base station may determine that a UE that transmitted a NACK does not exist, and may not retransmit the PDSCH. As in the example of FIG. 3C, when the base station receives a signal in the NACK resource (received power exceeds a threshold), the base station may determine that a UE that transmitted a NACK exists, and may retransmit the PDSCH.

[0034] For multicast for RRC connected UEs, the common frequency resources for group-common PDCCH / PDSCH are limited within the frequency resources of the dedicated unicast BWP to support simultaneous reception of unicast and multicast in the same slot. The following two options may be chosen for the common frequency resources for group-common PDCCH / PDSCH:

[0035] [Option 2A] The common frequency resources are defined as MBS-specific BWPs, which are associated with the dedicated unicast BWPs and use the same numerology (subcarrier spacing (SCS) and cyclic prefix (CP)).

[0036] As shown in the example of Figure 4A, a BWP for multicast (BWP1) and a BWP for unicast (BWP2) may be configured. BWP1 and 2 may not overlap in the frequency domain. If the UE does not receive BWP1 and 2 at the same time, the UE may switch the BWP used for reception (active DL BWP, BWP1 or 2) in the time domain.

[0037] [Option 2B] The common frequency resource is defined as an MBS frequency region having several consecutive PRBs, and the MBS frequency region is set within a dedicated unicast BWP.

[0038] As in the example of FIG. 4B, the multicast PDSCH resource may be included in the unicast BWP.

[0039] For RRC connected UEs receiving multicast, for HARQ-ACK feedback based on ACK / NACK when group common PDCCH scheduling is supported, the PUCCH resource configuration for HARQ-ACK feedback from a per UE perspective may be one of the following three options: [Option 1] The PUCCH resource configuration is shared with the PUCCH resource configuration for unicast HARQ-ACK feedback. [Option 2] The PUCCH resource configuration is separated from the PUCCH resource configuration for unicast HARQ-ACK feedback. [Option 3] The PUCCH resource configuration is option 1 or 2 based on the configuration.

[0040] However, it is not clear how to determine the resource for the HARQ-ACK feedback for multicast. If this resource is not clear, it may result in a decrease in throughput.

[0041] Therefore, the present inventors came up with a method for determining resources for multicast HARQ-ACK feedback.

[0042] When PTM transmission method 1 is used and a UE receives DCI scheduling a PDSCH, if the DCI is a group-common DCI having a CRC scrambled by a group-common RNTI, the UE can determine that the PDSCH is a multicast PDSCH, and if the DCI is not a group-common DCI having a CRC scrambled by a group-common RNTI, the UE can determine that the PDSCH is a unicast PDSCH.

[0043] When PTM transmission method 2 is used, a UE-specific DCI with a CRC scrambled by a UE-specific RNTI (eg, C-RNTI) schedules the multicast PDSCH.

[0044] However, the method of monitoring / receiving the DCI for scheduling the multicast PDSCH and the DCI for scheduling the unicast PDSCH is unclear. If the monitoring / reception method is unclear, it may result in a decrease in throughput, an increase in power consumption, and the like.

[0045] Therefore, the present inventors have conceived a method for monitoring / receiving DCI that schedules a multicast PDSCH / unicast PDSCH.

[0046] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0047] 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.

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

[0049] In this disclosure, link, associate, correspond, and map may be read as interchangeable. In this disclosure, allocate, assign, monitor, and map may be read as interchangeable.

[0050] 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 read as interchangeable.

[0051] The MAC signaling may be, 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.

[0052] In the present disclosure, MAC CE and activation / deactivation command may be read as interchangeable.

[0053] In this disclosure, UL channel, PUCCH, PUSCH, repetition, and transmission occasion may be read as interchangeable.

[0054] In the present disclosure, the terms "multicast," "groupcast," "broadcast," and "MBS" may be interchangeable. In the present disclosure, the terms "multicast PDSCH" and "PDSCH scrambled by a group-common RNTI" may be interchangeable.

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

[0056] In the present disclosure, specific, dedicated, UE specific, and UE individual may be read as interchangeable.

[0057] In the present disclosure, common, shared, group-common, UE common, and UE shared may be read as interchangeable.

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

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

[0060] (Wireless communication method) The UE may control / determine the PUCCH resources for transmitting UCI including HARQ-ACK for the multicast PDSCH.

[0061] The PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH may be configured for each common frequency resource by higher layer signaling, or may be configured in the PUCCH configuration (PUCCH-Config) of the UL BWP, as in Rel. 16. When this PUCCH resource is configured in the PUCCH-Config, this PUCCH resource may be a PUCCH resource of Rel. 15 / 16, or may be a newly defined PUCCH resource for HARQ-ACK of the multicast PDSCH.

[0062] One of PTM transmission schemes 1 and 2 may be specified in the specification. Both PTM transmission schemes 1 and 2 may be specified in the specification, and one may be set by higher layer signaling. If both PTM transmission schemes 1 and 2 are specified in the specification and a DCI that schedules a group-common PDSCH (multicast PDSCH) is a group-common DCI having a CRC scrambled by a group-common RNTI, the UE may determine that PTM transmission scheme 1 is used, and if the DCI is a UE-specific DCI having a CRC scrambled by a UE-specific RNTI, the UE may determine that PTM transmission scheme 2 is used.

[0063] In the PTM transmission method 1, the group-common DCI may be a new DCI format. The new DCI format may be DCI format 2_x. The UE may monitor the group-common DCI in the search space for multicast. The search space for multicast may be a type 3 PDCCH common search space (CSS), or the search space type (searchSpaceType) in the PDCCH configuration (PDCCH-Config) may be common.

[0064] The UE may receive a configuration of PUCCH resources for transmitting HARQ-ACK information for the PDSCH, and control the transmission of the HARQ-ACK information using the PUCCH resources.

[0065] The UE may receive the DCI scheduling the PDSCH and may determine, based on at least one of higher layer signaling and the DCI, whether the PDSCH is multicast or unicast.

[0066] <First embodiment> A UE scheduled for a multicast PDSCH by UE-specific DCI may follow at least one of the following aspects 1-1 to 1-6.

[0067] <<Aspect 1-1>> A UE that is scheduled for a multicast PDSCH by the UE-specific DCI transmits a HARQ-ACK for the multicast PDSCH using a UE-specific PUCCH resource.

[0068] The UE specific PUCCH resource may be according to any of the following resources A and B.

[0069] [Resource A] The UE uses the PUCCH resource set by higher layer signaling as the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH. DCI may not be used to determine this PUCCH resource. In this case, the PUCCH resource indicator (PRI) field can be omitted in the DCI that schedules the multicast PDSCH, and the overhead of the DCI can be reduced. By setting by UE-specific higher layer signaling, orthogonal resources can be assigned between UEs.

[0070] [Resource B] A plurality of PUCCH resources are configured by higher layer signaling, and the UE selects (determines) a PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH from among the plurality of PUCCH resources based on the scheduling DCI of the multicast PDSCH. In the example of Fig. 1, the UE selects (determines) one PUCCH resource set (from the plurality of PUCCH resource sets configured by higher layer signaling) based on the number of bits (size) of UCI including HARQ-ACK of the multicast PDSCH, and selects (determines) one PUCCH resource from the selected PUCCH resource set based on the PRI field in the DCI for scheduling the multicast PDSCH and the index of the first CCE of the PDCCH in which the DCI for scheduling the multicast PDSCH is detected.

[0071] <<Aspect 1-2>> A UE that is scheduled for a multicast PDSCH by the UE-specific DCI transmits a HARQ-ACK for the multicast PDSCH using a UE common PUCCH resource.

[0072] The UE common PUCCH resource may be according to either of the following resources A and B.

[0073] [Resource A] The UE uses the UE common PUCCH resource set by higher layer signaling as the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH. In this case, the PUCCH resource used for transmission among a plurality of UE common PUCCH resources can be dynamically indicated. The PUCCH resource for transmitting HARQ-ACK of the multicast PDSCH may be set by higher layer signaling. The HARQ-ACK feedback using this PUCCH resource may be NACK-only feedback.

[0074] [Resource B] The UE determines a UE common PUCCH resource based on higher layer signaling and DCI. In the example of FIG. 2, multiple PUCCH resources for HARQ-ACK transmission of a multicast PDSCH are configured by higher layer signaling, and the UE selects (determines) one PUCCH resource from the multiple PUCCH resources configured based on the PRI field in the DCI that schedules the multicast PDSCH and the index of the first CCE of the PDCCH in which the DCI that schedules the multicast PDSCH is detected. The configuration of multiple PUCCH resources for HARQ-ACK transmission of a multicast PDSCH may use a mechanism for determining a PUCCH resource set. For example, the UE may select (determine) a PUCCH resource / PUCCH resource set according to the number of bits (size) of UCI including HARQ-ACK of the multicast PDSCH.

[0075] <<Aspect 1-3>> One or more PUCCH resource sets for transmitting the HARQ-ACK of the multicast PDSCH are configured (by higher layer signaling), and the UE selects (determines) the PUCCH resource set to be used for transmitting the UCI including the HARQ-ACK depending on the number of bits (size) of the UCI.

[0076] Whether the UE uses ACK / NACK feedback or NACK-only feedback for HARQ-ACK transmission of multicast PDSCH may follow either of the following options 1 and 2.

[0077] [Option 1] Whether the UE uses ACK / NACK feedback or NACK-only feedback for the HARQ-ACK transmission of the multicast PDSCH may be determined / configured / specified regardless of the number of UCI bits. The UE does not need to switch between using ACK / NACK feedback or NACK-only feedback for the HARQ-ACK transmission of the multicast PDSCH.

[0078] [Option 2] Whether the UE uses ACK / NACK feedback or NACK-only feedback for HARQ-ACK transmission of multicast PDSCH may be determined depending on the number of UCI bits. In the example of FIG. 5, when multiple PUCCH resource sets are configured and the number of UCI bits is equal to or less than N0 bits, NACK-only feedback is used, and when the number of UCI bits is more than N0 bits, ACK / NACK feedback (first PUCCH resource set, PUCCH resource set ID=0) is used. When the number of UCI bits is greater than N0 and equal to or less than N1 bits, ACK / NACK feedback (second PUCCH resource set, PUCCH resource set ID=1) is used, and when the number of UCI bits is greater than N1 bits, ACK / NACK feedback (third PUCCH resource set, PUCCH resource set ID=2) may be used. N0 may be 2. N1 may be configured by higher layer signaling or may be a value specified in the specification. PUCCH format 0 may be used for NACK-only feedback.

[0079] <<Aspect 1-4>> One or more PUCCH resource sets for transmitting the HARQ-ACK of the multicast PDSCH are configured (by higher layer signaling), and the UE selects (determines) the PUCCH resource set to be used for transmitting the UCI including the HARQ-ACK depending on the number of bits (size) of the UCI.

[0080] The UE may use either a UE-specific PUCCH or a UE-common PUCCH for transmitting a HARQ-ACK for a multicast PDSCH according to either of the following options 1 and 2.

[0081] [Option 1] Whether the UE uses a UE-specific PUCCH or a UE-common PUCCH for transmitting the HARQ-ACK of the multicast PDSCH may be determined / configured / specified regardless of the number of UCI bits. The UE does not need to switch between using the UE-specific PUCCH or the UE-common PUCCH for transmitting the HARQ-ACK of the multicast PDSCH.

[0082] [Option 2] Whether the UE uses a UE-specific PUCCH or a UE-common PUCCH for transmitting HARQ-ACK of a multicast PDSCH may be determined according to the number of UCI bits. In the example of FIG. 6, when a plurality of PUCCH resource sets are configured and the number of UCI bits is equal to or less than N0 bits, the UE-common PUCCH is used, and when the number of UCI bits is more than N0 bits, the UE-specific PUCCH (first PUCCH resource set, PUCCH resource set ID=0) is used. When the number of UCI bits is greater than N0 and equal to or less than N1 bits, the UE-specific PUCCH (second PUCCH resource set, PUCCH resource set ID=1) is used, and when the number of UCI bits is greater than N1 bits, the UE-specific PUCCH (third PUCCH resource set, PUCCH resource set ID=2) may be used. N0 may be 2. N1 may be configured by higher layer signaling or may be a value specified in the specification. The UE-common PUCCH may use PUCCH format 0.

[0083] Aspects 1-5 One or more PUCCH resource sets for transmitting HARQ-ACK of the multicast PDSCH are configured (by higher layer signaling), and the UE selects (determines) the PUCCH resource set to be used for transmitting the UCI depending on the conditions.

[0084] The condition may be at least one of the following conditions: DCI format / DCI field PDCCH monitoring occasion / CORESET / search space RNTI with scrambling CRC ·MAC CE

[0085] The UE may determine whether to use ACK / NACK feedback or NACK-only feedback for HARQ-ACK transmission of the multicast PDSCH according to this condition.

[0086] The UE may determine whether to use a UE-specific PUCCH or a UE-common PUCCH for transmitting HARQ-ACK for a multicast PDSCH according to this condition.

[0087] Aspects 1-6 The configuration of the PUCCH resource / resource set by higher layer signaling may follow either of the following configuration methods 1 and 2.

[0088] [Setting method 1] A UE-specific PUCCH resource / resource set and a UE common PUCCH resource / resource set are configured separately. In the example of Fig. 7, a UE-specific PUCCH resource / resource set and a UE common PUCCH resource / resource set are configured. The UE-specific PUCCH resource / resource set may be a PUCCH resource / resource set for unicast PDSCH of Rel.15 / 16. A PUCCH resource / resource set for multicast PDSCH may be configured separately from the PUCCH resource / resource set for unicast PDSCH.

[0089] [Setting method 2] A UE-specific PUCCH resource / resource set and a UE-common PUCCH resource / resource set are commonly configured.

[0090] A UE-specific PUCCH resource and a UE-common PUCCH may be configured separately for each resource. For a HARQ-ACK of a unicast PDSCH, a UE-specific PUCCH resource may be indicated by DCI (PRI field / index of the first CCE). For a HARQ-ACK of a multicast PDSCH, a UE-common PUCCH resource may be indicated by DCI (PRI field / index of the first CCE). In the example of FIG. 8, a plurality of PUCCH resource sets are configured, and a portion of the plurality of PUCCH resource sets includes a UE-specific PUCCH resource / a UE-common PUCCH resource. A PUCCH resource set in a case where the number of UCI bits is equal to or less than N0 or N1 may include a UE-common PUCCH resource, and a PUCCH resource set in a case where the number of UCI bits is greater than N0 or N1 may not include a UE-common PUCCH resource. Each PUCCH resource / resource set may be a PUCCH resource / resource set for a unicast PDSCH of Rel.15 / 16. A PUCCH resource / resource set for a multicast PDSCH may be configured separately from a PUCCH resource / resource set for a unicast PDSCH.

[0091] The PUCCH resource may include an initial CS index. In the ACK / NACK feedback, the UE may determine a CS for NACK based on an index obtained by adding a first offset (e.g., 0) to the initial CS index, and may determine a CS for ACK based on an index obtained by adding a second offset (e.g., 6) to the initial CS index. In the NACK-only feedback, the UE may determine a CS based on an index obtained by adding a first offset (e.g., 0) to the initial CS index. The UE may transmit a sequence based on a base sequence and a CS based on an ACK or NACK on the PUCCH.

[0092] According to this embodiment, when a multicast PDSCH is scheduled by a UE-specific DCI, the UE can properly transmit HARQ-ACK information for that PDSCH.

[0093] <Second embodiment> A UE scheduled for a multicast PDSCH by the UE common DCI may follow at least one of the following aspects 2-1 and 2-2.

[0094] <<Aspect 2-1>> A UE that is scheduled for a multicast PDSCH by the UE common DCI transmits a HARQ-ACK for the multicast PDSCH using a UE-specific PUCCH resource.

[0095] The UE specific PUCCH resource may be according to any of the following resources A and B.

[0096] [Resource A] The UE uses the PUCCH resource set by higher layer signaling as the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH. DCI may not be used to determine this PUCCH resource. In this case, the PUCCH resource indicator (PRI) field can be omitted in the DCI that schedules the multicast PDSCH, and the overhead of the DCI can be reduced. By setting by UE-specific higher layer signaling, orthogonal resources can be assigned between UEs.

[0097] [Resource B] A plurality of PUCCH resources are configured by higher layer signaling, and the UE selects (determines) a PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH from among the plurality of PUCCH resources based on the scheduling DCI of the multicast PDSCH. In the example of Fig. 1, the UE selects (determines) one PUCCH resource set (from the plurality of PUCCH resource sets configured by higher layer signaling) based on the number of bits (size) of UCI including HARQ-ACK of the multicast PDSCH, and selects (determines) one PUCCH resource from the selected PUCCH resource set based on the PRI field in the DCI for scheduling the multicast PDSCH and the index of the first CCE of the PDCCH in which the DCI for scheduling the multicast PDSCH is detected.

[0098] The PRI may follow either PRI fields 1 and 2 below.

[0099] [PRI field 1] In the example of Figure 9A, the PRI field is extended to indicate a PRI (PRI0 to 3) for each UE (UE0 to 3) (UE-specific). The UE is configured with the PRI field for its own UE by higher layer signaling, and determines the PUCCH resource based on the configured PRI field. The UE may ignore the PRI field that is not configured (for other UEs).

[0100] [PRI field 2] The PRI field is not extended. The PRI field in DCI format 1_1 may be 3 bits. The PRI field in DCI format 1_2 may be 1 to 3 bits. In the example of Fig. 9B, the association (mapping) between the value of the PRI field and the PRI (PUCCH resource) for each UE is set by higher layer signaling, and the UE determines the PUCCH resource using the PRI (PUCCH resource) for its own UE.

[0101] A UE may know the PUCCH resources of other UEs, and may control channel collisions based on the PUCCH resources of other UEs.

[0102] The index of the CCE for determining the PUCCH resource set #0 (first PUCCH resource set) may be the same as that of Rel. 15. The index of the CCE may be common between UEs. In order for a common DCI to indicate a different PUCCH resource for each UE, the UE may determine the PUCCH resource by adding an offset to the CCE index. The offset may be set for each UE (individually for each UE) by higher layer signaling, or may be determined by a function based on the UE-ID / C-RNTI.

[0103] "Aspect 2-2" A UE that is scheduled for a multicast PDSCH by the UE common DCI transmits a HARQ-ACK for the multicast PDSCH using a UE common PUCCH resource.

[0104] The UE common PUCCH resource may be according to either of the following resources A and B.

[0105] [Resource A] The UE uses the PUCCH resource set by higher layer signaling as the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH. DCI may not be used to determine this PUCCH resource. In this case, the PUCCH resource indicator (PRI) field can be omitted in the DCI that schedules the multicast PDSCH, and the overhead of the DCI can be reduced. By setting by UE-specific higher layer signaling, orthogonal resources can be assigned between UEs.

[0106] [Resource B] A plurality of PUCCH resources are configured by higher layer signaling, and the UE selects (determines) a PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH from among the plurality of PUCCH resources based on the scheduling DCI of the multicast PDSCH. In the example of Fig. 2, the UE selects (determines) one PUCCH resource set (from the plurality of PUCCH resource sets configured by higher layer signaling) based on the number of bits (size) of UCI including HARQ-ACK of the multicast PDSCH, and selects (determines) one PUCCH resource from the selected PUCCH resource set based on the PRI field in the DCI for scheduling the multicast PDSCH and the index of the first CCE of the PDCCH in which the DCI for scheduling the multicast PDSCH is detected.

[0107] According to this embodiment, when a multicast PDSCH is scheduled by the UE common DCI, the UE can properly transmit HARQ-ACK information for the PDSCH.

[0108] <Third embodiment> When the UE receives a unicast PDSCH and a multicast PDSCH, the UE may follow either of the following aspects 3-1 and 3-2 for the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH.

[0109] <<Aspect 3-1>> The UE multiplexes the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH in one channel (maps them to one channel). The channel may be a PUCCH or a PUSCH.

[0110] The UE may generate HARQ-ACK bit sequences for unicast PDSCH and multicast PDSCH according to a method for counting HARQ-ACK of PDSCH for an existing semi-static / dynamic HARQ-ACK codebook (HARQ codebook), and transmit the generated HARQ-ACK bit sequence in one channel resource. In this case, the UE only needs one channel transmission, so that the resource utilization efficiency can be improved. The total DAI / counter DAI may be added up (counted) over the scheduling DCI of the unicast PDSCH and the scheduling DCI of the multicast PDSCH.

[0111] The channel resources to which the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH are mapped may be in accordance with either of the following resources A and B.

[0112] [Resource A] The UE transmits the HARQ-ACK for the unicast PDSCH and the HARQ-ACK for the multicast PDSCH in the PUCCH / PUSCH resource for the unicast PDSCH. This channel resource is a UE-specific resource, which makes it easy to control.

[0113] The UE may multiplex the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH, and select (determine) a PUCCH resource set according to the number of UCI bits including the multiplexed HARQ-ACK. The UE may select (determine) a PUCCH resource set according to the number of UCI bits of the HARQ-ACK of the unicast PDSCH (the number of UCI bits before multiplexing the HARQ-ACK of the multicast PDSCH into the HARQ-ACK of the unicast PDSCH).

[0114] The UE may obtain the DCI (PRI field / first CCE index) required for PUCCH resource selection according to the existing time / frequency DCI selection rules. Here, the UE does not need to distinguish between the scheduling DCI of the unicast PDSCH and the scheduling DCI of the multicast PDSCH.

[0115] For example, the selection rule may be the last DCI format among DCI formats numbered in ascending order of serving cell index for the same PDCCH monitoring occasion and numbered in ascending order of PDCCH monitoring occasion index.

[0116] The UE may obtain (PRI field / first CCE index) required for selecting a PUCCH resource for each of the unicast PDSCH scheduling DCI and the multicast PDSCH scheduling DCI according to the existing time / frequency direction DCI selection rule. Here, the UE may not distinguish between the unicast PDSCH scheduling DCI and the multicast PDSCH scheduling DCI. The UE may obtain (PRI field / first CCE index) required for selecting a PUCCH resource for the unicast PDSCH scheduling DCI according to the existing time / frequency direction DCI selection rule.

[0117] [Resource B] The UE transmits the HARQ-ACK for the unicast PDSCH and the HARQ-ACK for the multicast PDSCH in the PUCCH / PUSCH resource for the multicast PDSCH. This channel resource is an individual resource, which makes it easy to control.

[0118] The UE may multiplex the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH, and select (determine) a PUCCH resource set according to the number of UCI bits including the multiplexed HARQ-ACK. The UE may select (determine) a PUCCH resource set according to the number of UCI bits of the HARQ-ACK of the multicast PDSCH (the number of UCI bits before the HARQ-ACK of the unicast PDSCH is multiplexed with the HARQ-ACK of the unicast PDSCH).

[0119] The UE may obtain the DCI (PRI field / first CCE index) required for PUCCH resource selection according to the existing time / frequency DCI selection rules. Here, the UE does not need to distinguish between the scheduling DCI of the unicast PDSCH and the scheduling DCI of the multicast PDSCH.

[0120] For example, the selection rule may be the last DCI format among DCI formats numbered in ascending order of serving cell index for the same PDCCH monitoring occasion and numbered in ascending order of PDCCH monitoring occasion index.

[0121] The UE may obtain (PRI field / first CCE index) required for selecting a PUCCH resource for each of the unicast PDSCH scheduling DCI and the multicast PDSCH scheduling DCI according to the existing time / frequency direction DCI selection rules. Here, the UE may not distinguish between the unicast PDSCH scheduling DCI and the multicast PDSCH scheduling DCI. The UE may obtain (PRI field / first CCE index) required for selecting a PUCCH resource for the multicast PDSCH scheduling DCI according to the existing time / frequency direction DCI selection rules.

[0122] When NACK-only feedback is specified / configured as the HARQ-ACK transmission method for the multicast PDSCH, the HARQ-ACK information to be transmitted may be calculated by a logical operation of the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH. A HARQ-ACK information bit of 0 may represent a NACK, and a HARQ-ACK information bit of 1 may represent an ACK. The logical operation may be an AND operation. For example, when the HARQ-ACK information bit of the multicast PDSCH is 1 (ACK) and the HARQ-ACK information bit of the unicast PDSCH is 0 (NACK), the logical operation result is 0, so the UE may transmit a NACK by NACK-only feedback.

[0123] When the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH are mapped (multiplexed) to one channel, the bits of the HARQ-ACK may be ordered according to at least one of the type (cast type of the PDSCH) indicating the unicast PDSCH or the multicast PDSCH, the slot index of the PDSCH, and the cell index of the PDSCH. When the HARQ-ACK is ordered according to the cast type of the PDSCH, the order may be the HARQ-ACK of the unicast PDSCH, the HARQ-ACK of the multicast PDSCH, or the HARQ-ACK of the multicast PDSCH, the HARQ-ACK of the unicast PDSCH. For each slot of the PDSCH, the bits of the HARQ-ACK may be ordered according to at least one of the cast type of the PDSCH and the cell index of the PDSCH.

[0124] "Aspect 3-2" The UE does not multiplex the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH in one channel (maps them to different channels). Each channel may be a PUCCH or a PUSCH.

[0125] The UE may generate HARQ-ACK bit sequences for unicast PDSCH and multicast PDSCH separately, and transmit the HARQ-ACK bit sequences in different channel resources. The UE may generate HARQ-ACK bits for multicast PDSCH according to the counting method of HARQ-ACK for PDSCH for existing semi-static / dynamic HARQ-ACK codebook. In this case, HARQ-ACK transmission for multicast PDSCH does not affect HARQ-ACK transmission for unicast PDSCH. The total DAI / counter DAI may be counted separately for scheduling DCI for unicast PDSCH and scheduling DCI for multicast PDSCH.

[0126] If simultaneous transmission of a HARQ-ACK for a multicast PDSCH and a HARQ-ACK for a unicast PDSCH occurs (occasions overlap), the UE may prioritize the HARQ-ACK transmission for the unicast PDSCH (may drop the HARQ-ACK transmission for the multicast PDSCH), or may prioritize the HARQ-ACK transmission for the multicast PDSCH (may drop the HARQ-ACK transmission for the unicast PDSCH).

[0127] In a slot (or sub-slot), a UE may transmit only one of the PUCCH carrying HARQ-ACK for unicast PDSCH and the PUCCH carrying HARQ-ACK for multicast PDSCH. A UE that is instructed (by the PDSCH-to-HARQ feedback indicator field) to provide feedback for both unicast PDSCH and multicast PDSCH in a slot (or sub-slot) may drop either feedback. It may be specified that a UE does not expect to be instructed to provide feedback for both unicast PDSCH and multicast PDSCH in a slot (or sub-slot).

[0128] When the UE reports by the UE capability information that it supports both (simultaneous / multiplexed / within one channel) transmission of the HARQ-ACK of the multicast PDSCH and the HARQ-ACK of the unicast PDSCH, and simultaneous transmission of the HARQ-ACK of the multicast PDSCH and the HARQ-ACK of the unicast PDSCH occurs (occasion overlaps), the UE may transmit both the HARQ-ACK of the multicast PDSCH and the HARQ-ACK of the unicast PDSCH. In this case, the UE may transmit the HARQ-ACK of the multicast PDSCH and the HARQ-ACK of the unicast PDSCH by time division multiplexing (TDM) or may transmit them using aspect 3-1.

[0129] The UE may distinguish / identify between DCI for multicast PDSCH and DCI for unicast PDSCH (may follow at least one of the fifth to ninth embodiments).

[0130] According to this embodiment, the UE can properly transmit HARQ-ACK information for unicast PDSCH and multicast PDSCH.

[0131] <Fourth embodiment> In at least one of the first to third embodiments, a method for determining a PUCCH resource (e.g., a method for determining a PRI) may be applied to determining a TPC command for PUCCH (a scheduled TPC command field for PUCCH) / HARQ timing (a PDSCH-to-HARQ_feedback timing indicator field).

[0132] According to this embodiment, the UE can appropriately determine the TPC command / HARQ timing for PUCCH.

[0133] <Fifth embodiment> In PTM transmission method 2, the UE determines whether the PDSCH is a unicast PDSCH or a multicast PDSCH based on the resource allocation of the PDSCH scheduled by the DCI (whether the DCI schedules a unicast PDSCH or a multicast PDSCH).

[0134] A multicast PDSCH dedicated resource and a unicast PDSCH dedicated resource may be configured by higher layer signaling. Whether a scheduled PDSCH resource corresponds to a multicast PDSCH dedicated resource or a unicast PDSCH dedicated resource may determine whether the PDSCH is a unicast PDSCH or a multicast PDSCH. The resource may be a time domain / frequency domain / code domain (sequence / cyclic shift) / spatial domain. The frequency domain resource may be a physical resource element (PRE) / physical resource block (PRB) / BWP / CC.

[0135] In the examples of Figures 10A and 10B, a frequency domain resource for a multicast PDSCH and a frequency domain resource for a unicast PDSCH are configured. In the example of Figure 10A, if the frequency domain resource of a PDSCH scheduled by a UE-specific DCI is within the frequency domain resource for a multicast PDSCH, the UE determines that the PDSCH is a multicast PDSCH. In the example of Figure 10B, if the frequency domain resource of a PDSCH scheduled by a UE-specific DCI is within the frequency domain resource for a unicast PDSCH, the UE determines that the PDSCH is a unicast PDSCH.

[0136] A unicast resource or a multicast resource may be contained (surrounded) by the other. For example, a portion of the unicast resource may be hollowed out (punched) and the portion may be the multicast resource.

[0137] According to this embodiment, the UE can properly determine whether the PDSCH scheduled by the DCI is a unicast PDSCH or a multicast PDSCH.

[0138] Sixth embodiment In PTM transmission method 2, the UE determines, based on the reception / detection result of DCI that schedules a PDSCH, whether the PDSCH is a unicast PDSCH or a multicast PDSCH (whether the DCI schedules a unicast PDSCH or a multicast PDSCH).

[0139] The UE may determine whether the scheduled PDSCH is a unicast PDSCH or a multicast PDSCH based on at least one of the following aspects 6-1 to 6-4.

[0140] <<Aspect 6-1>> A CORESET / search space dedicated to UE-specific DCI for scheduling multicast PDSCH (multicast dedicated CORESET / search space) is configured.

[0141] If the UE detects DCI in a multicast-only CORESET / search space, it may determine that this DCI schedules a multicast PDSCH, and if the UE detects DCI in any other CORESET / search space, it may determine that this DCI is the same as Rel.15 / 16 (this DCI does not schedule a multicast PDSCH).

[0142] In the example of Figure 11, a multicast-only CORESET / search space and a unicast-only CORESET / search space are configured. If the UE detects DCI in the multicast-only CORESET, it determines that the DCI schedules a multicast PDSCH. The multicast-only CORESET / search space and the unicast-only CORESET / search space may or may not overlap.

[0143] The group-common DCI of the PTM transmission method 1 may use a multicast-dedicated CORESET / search space or a group-common DCI-dedicated CORESET / search space. Considering beam operation, in receiving the UE-specific DCI, the UE assumes a set TCI state. In receiving the group-common DCI received by multiple UEs, multiple monitoring occasions corresponding to multiple TCI states are set, and the UE needs to select a monitoring occasion corresponding to its own TCI state. Therefore, a search space for the UE-specific DCI and a search space for the group-common DCI may be set separately.

[0144] When the time / frequency resources of a multicast-dedicated CORESET / search space overlap with the time / frequency resources of other CORESETs / search spaces, the UE may not be able to determine which CORESET / search space the detected DCI belongs to. To avoid this, the base station may set a different sequence ID for each CORESET / search space and use a different sequence for the DMRS of the PDCCH corresponding to each CORESET / search space. This allows the UE to determine which CORESET / search space the detected DCI belongs to, even if the time / frequency resources of a multicast-dedicated CORESET / search space overlap with the time / frequency resources of other CORESETs / search spaces.

[0145] The DCI for scheduling the multicast PDSCH may be a DL assignment DCI such as DCI format 1_1 / 1_2. In this case, it is possible to prevent an increase in the number of blind detections. The DCI for scheduling the multicast PDSCH may be a new DCI format for the multicast PDSCH. If a new DCI format is specified, the UE may attempt blind detection only when configured by higher layer signaling.

[0146] By using a multicast-only CORESET / search space, the resources for monitoring DCI can be limited, reducing UE power consumption.

[0147] Aspect 6-2 A new field may be defined in an existing DCI format. The new field may indicate whether a PDSCH scheduled by the DCI format is a multicast PDSCH or a unicast PDSCH. The existing DCI format may be DCI format 1_1 / 1_2. The new field may be present in the existing DCI format only if the use of the new field is configured by higher layer signaling.

[0148] In the example of Figure 12, the existing DCI format includes an existing field and a new field, where a value of 0 in the new field indicates that this DCI schedules a unicast PDSCH, and a value of 1 in the new field indicates that this DCI schedules a multicast PDSCH.

[0149] Aspect 6-3 A UE-specific new RNTI may be defined. If the UE detects a DCI with a CRC scrambled by the new RNTI, the UE may determine that the DCI schedules a multicast PDSCH. The UE may attempt to detect a DCI with a CRC scrambled by the new RNTI only if the scheduling of the multicast PDSCH (new RNTI) is configured by higher layer signaling.

[0150] Aspect 6-4 If some special values ​​of some special fields in an existing DCI format are decoded, the UE may determine (validate) that the DCI schedules a multicast PDSCH. Otherwise, the UE may determine that the DCI schedules a unicast PDSCH. The existing DCI format may be at least one of DCI formats 0_1, 0_2, 1_1, 1_2, and 2_3. The combination of special fields and special values ​​may be at least one of the following: The value of the Frequency Domain Resource Allocation field is set to all 0's or all 1's. · The value of the time domain resource allocation field is set to all 0's or all 1's. The value of the frequency hopping flag field is set to all 0's or all 1's. The value of the modulation and coding scheme (MCS) field is set to all 0s or all 1s. · The value of the New Data Indicator (NDI) field is set to all 0's or all 1's. The value of the redundancy version field is set to all 0's or all 1's. The value of the HARQ process number field is set to all 0s or all 1s. The value of the Downlink Allocation Indicator (DAI) field is set to all 0s or all 1s. · The value of the transmit power control (TPC) command field for PUCCH is set to all 0's or all 1's. The value of the transmit power control (TPC) command field for PUSCH is set to all 0s or all 1s. · The value of the SRS resource indicator field is set to all 0's or all 1's. The values ​​of the precoding information and number of layers fields are set to all 0s or all 1s. The value of the Antenna Ports field is set to all 0's or all 1's. The value of the CSI request field is set to all 0s or all 1s.

[0151] In any of aspects 6-1 to 6-4, at least one of the one or more DCI fields (special DCI field) or a DCI field set by a higher layer may indicate that this DCI schedules a multicast PDSCH.

[0152] In any of aspects 6-1 to 6-4, the number of bits (size) of the DCI that schedules the multicast PDSCH may be the same as or different from the number of bits of the DCI that schedules the unicast PDSCH.

[0153] After the UE determines that the received DCI schedules a multicast PDSCH, the UE may obtain resource allocation information for the multicast PDSCH using the values ​​of each indication field in the DCI. Resource allocation information for the unicast PDSCH and resource allocation information for the multicast PDSCH may be configured by higher layer signaling. If resource allocation information for the multicast PDSCH is not configured (provided), the UE may use the resource allocation information for the unicast PDSCH for the multicast PDSCH. The resource allocation information may include frequency domain resource assignment (FDRA) / time domain resource assignment (TDRA) / DMRS information (CDM group index).

[0154] In the example of Fig. 13, if the UE determines that the UE-specific DCI schedules a multicast PDSCH, the UE may determine a resource for the multicast PDSCH based on the configured resource allocation information for multicast and the DCI. If the UE determines that the UE-specific DCI schedules a unicast PDSCH, the UE may determine a resource for the unicast PDSCH based on the configured resource allocation information for unicast and the DCI. One value of a field indicating resource allocation in the DCI may indicate different resources depending on whether the DCI schedules a multicast PDSCH or a unicast PDSCH.

[0155] The resource for the multicast PDSCH may be called a common frequency resource, or may be a resource commonly recognized among multiple UEs. The resource allocation method for the multicast PDSCH may select / indicate a resource from the common frequency resource, instead of the existing resource allocation method of selecting / indicating a resource from within the BWP.

[0156] In this case, compared to the fifth embodiment, since the PDSCH is limited to resources for multicast, the PDSCH resources can be flexibly specified using a limited number of bits (for example, an FDMA field) in the scheduling DCI.

[0157] According to this embodiment, the UE can properly determine whether the PDSCH scheduled by the DCI is a unicast PDSCH or a multicast PDSCH.

[0158] <Seventh embodiment> In the fifth and sixth embodiments, the operation when the PTM transmission method 2 is used has been mainly described, but the fifth and sixth embodiments may also be applied when the PTM transmission method 1 is used.

[0159] For example, the example 6-1 may be applied to the PTM transmission method 1, and the DCI for the PTM transmission method 1 may be restricted when it is detected in a multicast-dedicated CORESET / search space. In this case, the UE can reduce the amount of processing for blind detection / CRC check of the DCI for the PTM transmission method 1, and the UE power consumption can be reduced.

[0160] In the example of Fig. 14, a multicast-only CORESET / search space and a unicast-only CORESET / search space are set. The UE performs a CRC check using a group-common RNTI based on the PTM transmission method 1 only for DCI detected in the multicast-only CORESET / search space. The UE does not perform a CRC check using a group-common RNTI based on the PTM transmission method 1 for DCI detected in the unicast-only CORESET / search space (it is not assumed that a multicast PDSCH is scheduled by this DCI).

[0161] In PTM transmission mode 1 / 2, a new DCI format for multicast PDSCH scheduling may be defined. The UE may attempt blind detection of the new DCI format only within the multicast dedicated CORESET / search space. The DMRS sequence used for blind detection of the new DCI format may correspond to a sequence ID configured for the multicast dedicated CORESET / search space. By limiting the blind detection of the new DCI format to the multicast dedicated CORESET / search space, UE power consumption can be reduced.

[0162] In the example of Figure 15, a multicast-only CORESET / search space and a unicast-only CORESET / search space are configured. The UE performs blind detection of a new DCI format in the multicast-only CORESET / search space. The UE does not perform blind detection of a new DCI format in the unicast-only CORESET / search space (does not assume to receive a new DCI format in the unicast-only CORESET / search space).

[0163] According to this embodiment, the UE can properly determine whether the PDSCH scheduled by the DCI is a unicast PDSCH or a multicast PDSCH.

[0164] <Eighth embodiment> In the PTM transmission method 2, the UE determines whether the PDSCH is a unicast PDSCH or a multicast PDSCH based on higher layer signaling. The higher layer signaling may be, for example, MAC CE.

[0165] A common resource allocation configuration may be used for the unicast PDSCH and the multicast PDSCH.

[0166] The UE may transmit a NACK if it fails to receive / decode a PDSCH (unicast PDSCH / multicast PDSCH). The PUCCH resource for transmitting the NACK may be common to the unicast PDSCH and the multicast PDSCH.

[0167] If the UE successfully receives / decodes the PDSCH (unicast PDSCH / multicast PDSCH), the UE may follow at least one of steps 1 to 3 below.

[0168] [Step 1] If higher layer signaling indicates that the PDSCH is a unicast PDSCH and the UE successfully receives / decodes the PDSCH, the UE may send an ACK.

[0169] [Step 2] If higher layer signaling indicates that the PDSCH is a multicast PDSCH, ACK / NACK feedback is configured / indicated, and the UE successfully receives / decodes the PDSCH, the UE may send an ACK.

[0170] [Step 3] If higher layer signaling indicates that the PDSCH is a multicast PDSCH, NACK-only feedback is configured / indicated, and the UE successfully receives / decodes the PDSCH, the UE does not need to send a HARQ-ACK.

[0171] The PUCCH resources for ACK transmission may be different between unicast PDSCH and multicast PDSCH.

[0172] The MAC subheader may indicate whether the PDSCH is a unicast PDSCH or a multicast PDSCH. The transport block (TB) may correspond to a MAC protocol data unit (PDU). The MAC PDU may include one or more MAC sub-PDUs. The MAC sub-PDU may be one MAC subheader, one MAC subheader and one MAC service data unit (SDU), one MAC subheader and one MAC CE, or one MAC subheader and padding.

[0173] Until the TB in the received PDSCH is successfully decoded, the UE cannot know whether the PDSCH is a unicast PDSCH or a multicast PDSCH. In demodulating / decoding the PDSCH, the physical (PHY) layer does not need to distinguish between a unicast PDSCH and a multicast PDSCH.

[0174] Whether the PDSCH is a unicast or multicast PDSCH may affect the following UE behavior (HARQ-ACK feedback control).

[0175] [UE Actions] The UE may decode the TB in the scheduled PDSCH, read the higher layer signaling (e.g., MAC subheader) included in the TB, and determine whether the TB is unicast or multicast. The UE may perform HARQ-ACK feedback control according to the determination result. The HARQ-ACK feedback control may include at least one of generating a HARQ-ACK information bit sequence, determining a PUCCH resource, and transmitting a PUCCH.

[0176] The UE may perform this UE operation only if configured by higher layer signaling. The UE may perform this UE operation only for PDSCHs scheduled by a specific DCI format. The specific DCI format may be, for example, an existing DCI format (such as DCI format 1_1 / 1_2) or a new DCI format for multicast PDSCH scheduling. The UE may perform this UE operation only for PDSCHs scheduled by a DCI with a CRC scrambled by a specific RNTI. The specific RNTI may be, for example, a C-RNTI.

[0177] The data scrambling RNTI of the multicast PDSCH (PTM transmission method 2) may be a group-common RNTI. The data scrambling RNTI of the unicast PDSCH may also be a group-common RNTI. Although the data scrambling RNTI of the existing unicast PDSCH is C-RNTI, the UE needs to decode the PDSCH using a specific RNTI before TB decoding, so in this embodiment, the UE uses a data scrambling RNTI that is common to both the multicast PDSCH and the unicast PDSCH.

[0178] For a multicast PDSCH and a unicast PDSCH, the data scrambling RNTI may be the RNTI used for CRC scrambling of the corresponding scheduling DCI.

[0179] The data scrambling RNTI of the multicast PDSCH (PTM transmission method 2) may be a group-common RNTI, and the data scrambling RNTI of the unicast PDSCH may be the RNTI (e.g., C-RNTI) used for CRC scrambling of the corresponding scheduling DCI. The UE may decode (blind decode) the PDSCH using each of the data scrambling RNTI of the multicast PDSCH and the data scrambling RNTI of the unicast PDSCH, and determine which data scrambling RNTI has been used (whether the PDSCH is multicast or unicast) by performing error detection for each TB / code word (CW) / code block group (CBG).

[0180] In this way, when the UE determines the data scrambling RNTI by blind decoding of the PDSCH, it is not necessary to determine whether the PDSCH is multicast or unicast by the higher layer signaling (e.g., MAC subheader) included in the TB. In this case, it may be specified that the UE is not notified of whether the PDSCH is multicast or unicast by the higher layer signaling (e.g., MAC subheader) included in the TB. In this case, it is possible to suppress the control overhead.

[0181] The UE may determine the data scrambling RNTI by blind decoding of the PDSCH, determine whether the PDSCH is multicast or unicast by the higher layer signaling (e.g., MAC subheader) included in the TB, and check whether the determined data scrambling RNTI is correct. In this case, reliability can be improved.

[0182] According to this embodiment, the UE can properly determine whether the PDSCH is a unicast PDSCH or a multicast PDSCH.

[0183] <Ninth embodiment> If a multicast PDSCH is configured by higher layer signaling, the UE may determine (assume) that a DL assignment DCI with a C-RNTI-scrambled CRC schedules the multicast PDSCH (the UE may be specified not to assume that a unicast PDSCH is scheduled). If a multicast PDSCH is configured by higher layer signaling, the UE may determine (assume) that a specific DCI format schedules the multicast PDSCH. The specific DCI format may be, for example, an existing DCI format (such as DCI format 1_1 / 1_2) or a new DCI format for multicast PDSCH scheduling.

[0184] According to this embodiment, the UE can properly determine whether the PDSCH is a unicast PDSCH or a multicast PDSCH.

[0185] <Tenth embodiment> A UE capability corresponding to at least one function (feature) in the first to ninth embodiments may be defined. If the UE reports this UE capability, the UE may perform the corresponding function. If the UE reports this UE capability and a higher layer parameter corresponding to this function is configured, the UE may perform the corresponding function. A higher layer parameter (RRC information element) corresponding to this function may be defined. If the higher layer parameter is configured, the UE may perform the corresponding function.

[0186] The UE capability may indicate whether the UE supports this feature.

[0187] The UE capability may indicate whether or not it supports PTM transmission method 1.

[0188] The UE capability may indicate whether or not it supports PTM transmission scheme 2.

[0189] The UE capabilities may indicate whether it supports multicast dedicated CORESETs / search spaces. The UE capabilities may indicate the maximum number of multicast dedicated CORESETs / search spaces (number supported).

[0190] The UE capability may indicate how to transmit the HARQ-ACK for the multicast PDSCH (ACK / NACK feedback or NACK-only feedback).

[0191] The UE capability may indicate the scheduling method (UE-specific DCI or UE common DCI) for the multicast PDSCH.

[0192] The UE capabilities may indicate whether it supports transmission of both (simultaneous / multiplexed / in one channel) HARQ-ACK for multicast PDSCH and HARQ-ACK for unicast PDSCH.

[0193] According to this embodiment, the UE can achieve the above functions while maintaining compatibility with existing specifications.

[0194] (Wireless communication systems) A 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 of these methods.

[0195] 16 is a diagram showing 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), 5th generation mobile communication system New Radio (5G NR), or the like, which are specified by the Third Generation Partnership Project (3GPP).

[0196] Furthermore, the wireless communication system 1 may support dual connectivity between a plurality of 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)), and the like.

[0197] 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.

[0198] The wireless communication system 1 may support dual connectivity between multiple base stations in 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))).

[0199] 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 arranged in the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1. A user terminal 20 may be located in at least one of the cells. The arrangement and number of each cell and user terminal 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 a base station 10.

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

[0201] 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 correspond to a frequency band higher than FR2.

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

[0203] The multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., 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.

[0204] 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 at least one of, for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

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

[0206] In the wireless communication system 1, a wireless access scheme based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and the uplink (UL), 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), etc. may be used.

[0207] The radio access scheme may be called a waveform. 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.

[0208] 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 a downlink channel.

[0209] In addition, 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.

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

[0211] 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 of at least one of the PDSCH and the PUSCH.

[0212] In addition, DCI for scheduling PDSCH may be called DL assignment, DL DCI, etc., and DCI for scheduling PUSCH may be called UL grant, UL DCI, etc. In addition, PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

[0213] 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 multiple search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0214] 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," and "CORESET setting" in the present disclosure may be read as interchangeable terms.

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

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

[0217] 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, as the DL-RS, 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.

[0218] 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 the DMRS for the PBCH) may be called an SS / PBCH block, an SS Block (SSB), or the like. In addition, the SS, SSB, and the like may also be called a reference signal.

[0219] 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 be called a user equipment specific reference signal (UE-specific reference signal).

[0220] (base station) 17 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 one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

[0221] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the base station 10 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0222] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured with 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.

[0223] 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 transmission and reception unit 120, the transmission and reception antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transmission and reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0224] 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.

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

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

[0227] 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.

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

[0229] 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.

[0230] The transceiver 120 (transmission processing unit 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.

[0231] The transceiver unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna .

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

[0233] 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.

[0234] 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.

[0235] 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) for the user terminal 20, control plane data, etc.

[0236] 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.

[0237] The transceiver 120 may transmit a configuration of a physical uplink control channel (PUCCH) resource for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information for a multicast physical downlink shared channel (PDSCH). The controller 110 may control reception of the HARQ-ACK information using the PUCCH resource.

[0238] The transceiver 120 may transmit at least one of higher layer signaling and downlink control information for scheduling a physical downlink shared channel (PDSCH) based on whether the PDSCH is multicast or unicast. The controller 110 may control reception of the PDSCH.

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

[0240] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the user terminal 20 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0241] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured with 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.

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

[0243] The transmitting / receiving 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 transmitting / receiving unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting / receiving circuit, and the like, which are described based on common understanding in the technical field related to the present disclosure.

[0244] 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.

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

[0246] 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.

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

[0248] The transceiver unit 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.

[0249] The transceiver 220 (transmission processing unit 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 sequence to be transmitted, and output a baseband signal.

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

[0251] The transceiver unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna 230.

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

[0253] 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, and acquire user data, etc.

[0254] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, 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.

[0255] In addition, the transmitting section and the 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.

[0256] The transceiver 220 may receive a configuration of a physical uplink control channel (PUCCH) resource for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information for a multicast physical downlink shared channel (PDSCH). The controller 110 may control the transmission of the HARQ-ACK information using the PUCCH resource (first to fourth embodiments).

[0257] The multicast PDSCH may be scheduled by either terminal-specific downlink control information or terminal-common downlink control information (first and second embodiments).

[0258] The settings may be either terminal-specific settings or terminal-common settings (first and second embodiments).

[0259] The control unit 210 may control transmission of the HARQ-ACK information in either the same channel as the second HARQ-ACK information for a unicast PDSCH or a channel different from the second HARQ-ACK information (third embodiment).

[0260] The transceiver 220 may receive downlink control information that schedules a physical downlink shared channel (PDSCH). The controller 210 may determine whether the PDSCH is multicast or unicast based on at least one of higher layer signaling and the downlink control information (fifth to tenth embodiments).

[0261] The downlink control information may be terminal-specific downlink control information (Fifth and Sixth Embodiments).

[0262] The transmission / reception unit 220 may receive a configuration of a multicast PDSCH. If the configuration includes a resource indicated by the downlink control information, the control unit 210 may determine that the PDSCH is multicast (a fifth embodiment).

[0263] If the downlink control information satisfies a condition, the control unit 210 may determine that the PDSCH is multicast (sixth embodiment).

[0264] (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. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

[0265] 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, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission may be called a transmitting unit, a transmitter, and the like. In either case, as described above, the method of realization is not particularly limited.

[0266] For example, a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 19 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. The above-mentioned 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.

[0267] In this disclosure, the terms "apparatus," "circuit," "device," "section," "unit," and the like can 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.

[0268] For example, although only one processor 1001 is shown, there may be multiple processors. Also, the processes may be performed by one processor, or the processes may be performed by two or more processors simultaneously, sequentially, or in other manners. Also, the processor 1001 may be implemented by one or more chips.

[0269] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations, controls communications via a communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and the storage 1003.

[0270] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with 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.

[0271] Moreover, the processor 1001 reads out 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 according to the programs. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and the other functional blocks may be realized in a similar manner.

[0272] 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 ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), and other suitable storage media. The memory 1002 may be called a register, a cache, a main memory (primary storage device), and the like. The memory 1002 can store a program (program code), a software module, and the like that is executable to implement a wireless communication method according to an embodiment of the present disclosure.

[0273] 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 disk (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), 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 an auxiliary storage device.

[0274] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order 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.

[0275] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0276] In addition, 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.

[0277] 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), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized using the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0278] (Modification) In addition, the terms explained in this disclosure and the terms necessary for understanding this 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 read as mutually interchangeable. A signal may also be a message. A reference signal may also be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applied standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, etc.

[0279] 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.

[0280] Here, the numerology may be a communication parameter applied to at least one of the 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), a 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.

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

[0282] A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed 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.

[0283] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. A different name may be used for 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 read as interchangeable with each other.

[0284] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the 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.

[0285] Here, TTI refers to, for example, the minimum 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. Note that the definition of TTI is not limited to this.

[0286] 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) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

[0287] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

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

[0289] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 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.

[0290] 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 the numerology, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0291] 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. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

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

[0293] 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.

[0294] 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 numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0295] The BWP may include a 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.

[0296] 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 replaced with "BWP".

[0297] The above-mentioned structures of radio frames, subframes, slots, minislots, and symbols 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, and other configurations can be changed in various ways.

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

[0299] The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the formulas 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 limiting in any way.

[0300] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the 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.

[0301] 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.

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

[0303] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the 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.

[0304] 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. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified, for example, by using a MAC Control Element (CE).

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

[0306] The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or by comparing numerical values ​​(e.g., with a predetermined value).

[0307] 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.

[0308] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the 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, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0310] In this 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," and the like may be used interchangeably.

[0311] 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. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

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

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

[0314] 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.

[0315] 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 moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (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 include a device that does not necessarily move during communication operation. 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.

[0316] Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect / embodiment 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 a plurality of 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, an uplink channel, a downlink channel, etc. may be read as a sidelink channel.

[0317] Similarly, the user terminal in the present disclosure may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0318] In the present disclosure, an operation performed by a base station may be performed by its upper node in some cases. It is clear that in a network including one or more network nodes having base stations, various operations performed for communication with terminals 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.

[0319] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be reordered 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 particular order presented.

[0320] Each aspect / embodiment described in the present disclosure may be implemented using any of a wide variety of standards, including 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 using 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other appropriate wireless communication methods, next-generation systems that are based on these, etc. Also, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0321] 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."

[0322] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure 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 precede the second element in some way.

[0323] 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, and the like.

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

[0325] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. That is, "determination" may be considered to be "deciding" to perform some action.

[0326] Additionally, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," etc.

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

[0328] 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 the elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0329] 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, and the like, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, and the like, as some non-limiting and non-exhaustive examples.

[0330] 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."

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

[0332] In this disclosure, where articles have been 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.

[0333] 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 as modified and altered forms without departing from the spirit and scope of the invention defined based on the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the invention according to the present disclosure.

Claims

1. a receiving unit for receiving higher layer signaling indicating a search space and receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) within the search space; A control unit that determines whether the PDSCH is multicast or unicast based on the search space and the DCI, The control unit is a terminal that determines the time resource of the PDSCH based on the TDRA information for multicast when time domain resource assignment (TDRA) information for unicast and TDRA information for multicast are set and it is determined that the PDSCH is multicast.

2. receiving higher layer signaling indicating a search space and receiving downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) within the search space; determining whether the PDSCH is multicast or unicast based on the search space and the DCI; When time domain resource assignment (TDRA) information for unicast and TDRA information for multicast are set, if it is determined that the PDSCH is multicast, a step of determining a time resource of the PDSCH based on the TDRA information for multicast.

3. a transmission unit that transmits higher layer signaling indicating a search space for multicast and higher layer signaling indicating a search space for unicast; a control unit that determines transmission of one of a multicast physical downlink shared channel (PDSCH) and a unicast PDSCH; The control unit controls transmission of downlink control information (DCI) that schedules the PDSCH within a search space corresponding to the PDSCH, A base station, in which, when time domain resource assignment (TDRA) information for unicast and TDRA information for multicast are set, and when it is determined that the PDSCH is multicast, a time resource of the PDSCH is determined based on the TDRA information for multicast.

4. A system including a terminal and a base station, The terminal includes: a receiving unit for receiving higher layer signaling indicating a search space and receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) within the search space; A control unit that determines whether the PDSCH is multicast or unicast based on the search space and the DCI, When time domain resource assignment (TDRA) information for unicast and TDRA information for multicast are set, if it is determined that the PDSCH is multicast, the control unit determines a time resource of the PDSCH based on the TDRA information for multicast; The base station, A transmitter for transmitting the higher layer signaling; A control unit that determines transmission of the PDSCH, The control unit of the base station is a system that controls the transmission of the DCI.

Images