Terminal, radio communication method, base station, and system

Abstract

To appropriately receive multi-cast downlink data.SOLUTION: A terminal includes: a receiving section that receives upper layer signaling indicating a search space and receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) in the search space; and a control section that on the basis of the search space and the DCI, determines whether the PDSCH is multi-cast or unicast. An ID corresponding to the search space is set and the receiving section uses a series corresponding to the ID for the DCI. Thereby, multi-cast downlink data can be received appropriately.SELECTED DRAWING: Figure 2

Description

Technical Field

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

Background Art

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was standardized for the purpose of further high-speed data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was standardized.

[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+(plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also being considered.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In a future wireless communication system (e.g., NR), it is assumed that a plurality of user terminals (User Equipment (UE)) communicate in an ultra-high density and high traffic environment.

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

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

[0008] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, a base station, and a system that can appropriately receive multicast downlink data.

Means for Solving the Problems

[0009] A terminal according to an aspect of the present disclosure includes a receiving unit that receives upper layer signaling indicating a search space and receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) within the search space, and a control unit that determines whether the PDSCH is multicast or unicast based on the search space and the DCI. An ID corresponding to the search space is set, and the receiving unit uses a sequence corresponding to the ID for the DCI.

Effects of the Invention

[0010] According to an aspect of the present disclosure, multicast downlink data can be appropriately received.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

DETAILED DESCRIPTION OF THE INVENTION

[0012] (PUCCH Format) In future wireless communication systems (e.g., after Rel. 15, 5G, NR, etc.), configurations (also referred to as formats, PUCCH formats (PF), etc.) for uplink control channels (e.g., PUCCH) used for transmitting uplink control information (UCI) are being studied. For example, in Rel. 15 NR, it is being studied to support five types of PF0 to 4. Note that the names of the PFs shown below are merely examples, and different names may be used.

[0013] For example, PF0 and 1 are PFs used for transmitting UCI of up to 2 bits. For example, UCI may be at least one of delivery confirmation information (also referred to as Hybrid Automatic Repeat reQuest-Acknowledgement (HARQ-ACK), acknowledgement (ACK) or negative-acknowledgement (NACK), etc.) and scheduling request (SR). Since PF0 can be assigned to 1 or 2 symbols, it is also called short PUCCH or sequence-based short PUCCH, etc. On the other hand, since PF1 can be assigned to 4 - 14 symbols, it is also called long PUCCH, etc. PF0 may transmit a sequence obtained by a cyclic shift of a base sequence, using a cyclic shift based on at least one of an initial cyclic shift (CS) index, a value of UCI, 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 block spreading in the time domain 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 (for example, Channel State Information (CSI), or at least one of CSI, HARQ-ACK, and SR). Since PF2 can be assigned to 1 or 2 symbols, it is also called short PUCCH, etc. On the other hand, since PF3 and 4 can be assigned to 4 - 14 symbols, they are also called long PUCCH, etc. In PF4, multiple user terminals may be CDM using block spreading of (frequency domain (FD)-OCC) before DFT.

[0015] Intra-slot frequency hopping may be applied to PF1, PF3, and PF4. Let the length of PUCCH be N symb Then, the length before frequency hopping (the first hop) may be floor(N symb / 2), and the length after frequency hopping (the second hop) may be 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 upper layer signaling and / or downlink control information (DCI). Here, the upper layer signaling may be, for example, at least one of Radio Resource Control (RRC) signaling, system information (e.g., at least one of Remaining Minimum System Information (RMSI), Other System Information (OSI), Master Information Block (MIB), System Information Block (SIB)), and broadcast information (Physical Broadcast Channel (PBCH)).

[0018] Also, in NR, the number of symbols allocated to PUCCH (which may also be referred to as PUCCH allocation symbols, PUCCH symbols, etc.) can be determined by any one of slot-specific, cell-specific, user equipment-specific, or a combination thereof. Since it is expected that the communication distance (coverage) increases as the number of PUCCH symbols increases, for example, an operation of increasing the number of symbols for user equipment farther from the base station (e.g., eNB, gNB) is assumed.

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

[0020] Also, in a situation of ultra-high density and high traffic, such as an environment where a large number of UEs are geographically concentrated (e.g., stadium, etc.), it is assumed that a plurality of UEs receive the same signal / channel simultaneously. In such a case, since a plurality of UEs exist in the same area and each UE receives the same signal / channel, although the communication reliability can be ensured when each UE receives the signal / channel by unicast, it is considered that the resource utilization efficiency is reduced.

[0021] A mechanism for group scheduling for the multicast / broadcast service (MBS) to be received by a plurality of UEs is being studied.

[0022] For example, scheduling the multicast PDSCH by one or more DCIs is being studied. In this case, there is a possibility that the size (payload size, overhead) of the DCI increases.

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

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

[0025] It is being considered that PTM transmission mode 1 uses a group-common PDCCH to schedule a group-common PDSCH for a plurality of RRC-connected UEs within the same MBS group, the group-common PDCCH has a CRC scrambled by 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 mode 2 uses a UE-specific PDCCH to schedule a group-common PDSCH for a plurality of RRC-connected UEs within the same MBS group, the UE-specific PDCCH has a CRC scrambled by a UE-specific RNTI (e.g., C-RNTI), and the group-common PDSCH is scrambled using a group-common RNTI.

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

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

[0029] For RRC-connected UEs that receive multicast, at least PTM transmission mode 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) UEs that successfully decode the PDSCH transmit ACK. UEs that fail to decode the PDSCH transmit NACK.

[0031] [Feedback method 2] HARQ-ACK feedback based only on NACK for multicast (NACK-only based HARQ-ACK feedback, NACK-only based PUCCH, NACK-only transmission, NACK-only feedback) UEs that successfully decode the PDSCH do not transmit ACK. UEs that fail to decode the PDSCH transmit NACK.

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

[0033] Among a plurality of UEs, HARQ-ACK resources for the multicast PDSCH may overlap. As in the example of FIG. 3A, among a plurality of UEs, ACK resources do not overlap, and NACK resources may overlap. As in the example of FIG. 3B, when the base station does not receive a signal (the received power is below the threshold) in the NACK resource, the base station may determine that there is no UE that transmitted a NACK and may not retransmit the PDSCH. As in the example of FIG. 3C, when the base station receives a signal (the received power exceeds the threshold) in the NACK resource, the base station may determine that there is a UE that transmitted a NACK and may retransmit the PDSCH.

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

[0035] [Option 2A] The common frequency resources are defined as an MBS-specific BWP. The MBS-specific BWP is associated with the individual unicast BWP and uses the same numerology (subcarrier spacing (SCS) and cyclic prefix (CP)).

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

[0037] [Option 2B] The common frequency resource is defined as an MBS frequency region having several consecutive PRBs. The MBS frequency region is configured within an individual 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 the perspective of each UE may be one selected from 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 multicast HARQ-ACK feedback. If this resource is not clear, there is a risk of throughput degradation and the like.

[0041] Therefore, the inventors of the present invention conceived a method for determining resources for multicast HARQ-ACK feedback.

[0042] When PTM transmission mode 1 is used and a UE receives a DCI that schedules 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. 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 mode 2 is used, a UE-specific DCI having a CRC scrambled by a UE-specific RNTI (e.g., C-RNTI) schedules a multicast PDSCH.

[0044] However, the monitoring / receiving method for the DCI that schedules a multicast PDSCH and the DCI that schedules a unicast PDSCH is not clear. If the monitoring / receiving method is not clear, there is a risk of causing a throughput decrease, an increase in power consumption, etc.

[0045] Therefore, the inventors of the present invention conceived a method for monitoring / receiving the 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. The wireless communication methods according to the respective embodiments may be applied individually or in combination.

[0047] In the present disclosure, "A / B / C", "at least one of A, B, and C" may be read interchangeably with each other. In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, band may be read interchangeably with each other. In the present disclosure, index, ID, indicator, resource ID may be read interchangeably with each other. In the present disclosure, support, control, be able to control, operate, be able to operate may be read interchangeably with each other.

[0048] In the present disclosure, configure, activate, update, indicate, enable, specify, select may be read interchangeably with each other.

[0049] In the present disclosure, link, associate, correspond, map may be read interchangeably with each other. In the present disclosure, allocate, assign, monitor, map may be read interchangeably with each other.

[0050] In the present disclosure, the upper layer signaling may be any one of, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameter, upper layer, upper layer parameter, RRC information element (IE), RRC message may be read interchangeably with each other.

[0051] MAC signaling may use, for example, a MAC control element (MAC CE), a MAC Protocol Data Unit (PDU), etc. 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, the MAC CE and the activation / deactivation command may be read interchangeably with each other.

[0053] In the present disclosure, the UL channel, PUCCH, PUSCH, repetition, transmission occasion may be read interchangeably with each other.

[0054] In the present disclosure, multicast, groupcast, broadcast, MBS may be read interchangeably with each other. In the present disclosure, the multicast PDSCH and the PDSCH scrambled by a group common RNTI may be read interchangeably with each other.

[0055] In the present disclosure, HARQ-ACK, HARQ-ACK information, HARQ, ACK / NACK, ACK, NACK may be read interchangeably with each other.

[0056] In the present disclosure, specific, dedicated, UE-specific, UE-dedicated may be read interchangeably with each other.

[0057] In the present disclosure, common, shared, group-common, UE-common, UE-shared may be read interchangeably with each other.

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

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

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

[0061] The PUCCH resource for transmitting UCI including HARQ-ACK of a multicast PDSCH may be set for each common frequency resource by upper layer signaling, or may be set within the PUCCH configuration (PUCCH-Config) of the UL BWP, similar to Rel. 16. When this PUCCH resource is set within 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 a multicast PDSCH.

[0062] One of PTM transmission methods 1 and 2 may be specified in the specification. Both of PTM transmission methods 1 and 2 may be specified in the specification, and one of them may be set by upper layer signaling. When both of PTM transmission methods 1 and 2 are specified in the specification and the DCI for scheduling the 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 method 1 is used, and when the DCI is a UE-specific DCI having a CRC scrambled by a UE-specific RNTI, the UE may determine that PTM transmission method 2 is used.

[0063] In PTM transmission mode 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 within the multicast search space. The multicast search space may be type 3 PDCCH common search space (CSS), or the search space type within the PDCCH configuration (PDCCH-Config) may be common.

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

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

[0066] <First Embodiment> The UE scheduled to transmit the multicast PDSCH by the UE-specific DCI may follow at least one of the following aspects 1-1 to 1-6.

[0067] 《Aspect 1-1》 The UE scheduled to transmit the multicast PDSCH by the UE-specific DCI transmits the HARQ-ACK of the multicast PDSCH using the UE-specific PUCCH resource.

[0068] The UE-specific PUCCH resource may follow either of the following resources A and B.

[0069] [Resource A] The UE uses the PUCCH resource configured by upper layer signaling as the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH. It is not necessary to use DCI for the determination of this PUCCH resource. In this case, the PUCCH resource indicator (PRI) field can be omitted from the DCI for scheduling the multicast PDSCH, and the overhead of the DCI can be reduced. By configuring through UE-specific upper layer signaling, orthogonal resources can be allocated among UEs.

[0070] [Resource B] Multiple PUCCH resources are configured by upper layer signaling, and the UE selects (determines) the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH from among the multiple 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 among multiple PUCCH resource sets configured by upper layer signaling) based on the number of bits (size) of the 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 that detected the DCI for scheduling the multicast PDSCH.

[0071] 《Aspect 1-2》 The UE scheduled to transmit the multicast PDSCH by UE-specific DCI transmits the HARQ-ACK of the multicast PDSCH using the UE-common PUCCH resource.

[0072] The UE-common PUCCH resource may follow either of the following Resource A and Resource B.

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

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

[0075] 《Aspect 1-3》 One or more PUCCH resource sets for HARQ-ACK transmission of the multicast PDSCH are configured (by upper layer signaling), and the UE selects (determines) the PUCCH resource set used for transmitting the UCI according to the number of bits (size) of the UCI including the HARQ-ACK.

[0076] Whether the UE uses ACK / NACK feedback or NACK-only feedback for HARQ-ACK transmission of the 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 HARQ-ACK transmission of the multicast PDSCH may be determined / set / stipulated regardless of the number of bits of the UCI. The UE may not need to switch whether to use ACK / NACK feedback or NACK-only feedback for 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 the multicast PDSCH may be determined according to the number of bits of the UCI. In the example of Figure 5, when multiple PUCCH resource sets are configured and the number of UCI bits is less than or equal to N0 bits, NACK-only feedback is used. When the number of UCI bits is more than N0 bits, ACK / NACK feedback (the first PUCCH resource set, PUCCH resource set ID = 0) is used. When the number of UCI bits is more than N0 and less than or equal to N1 bits, ACK / NACK feedback (the second PUCCH resource set, PUCCH resource set ID = 1) is used. When the number of UCI bits is more than N1 bits, ACK / NACK feedback (the third PUCCH resource set, PUCCH resource set ID = 2) may be used. N0 may be 2. N1 may be set by upper layer signaling or may be a value stipulated in the specification. The NACK-only feedback may use PUCCH format 0.

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

[0080] Whether the UE uses the UE-specific PUCCH or the UE-common PUCCH for transmitting HARQ-ACK for the multicast PDSCH may follow either of the following Option 1 and Option 2.

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

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

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

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

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

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

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

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

[0089] [Setting method 2] The UE-specific PUCCH resource / resource set and the UE-common PUCCH resource / resource set are set commonly.

[0090] For each resource, the UE-specific PUCCH resource and the UE-common PUCCH may be set separately. For the HARQ-ACK of the unicast PDSCH, the UE-specific PUCCH resource may be indicated by DCI (PRI field / index of the first CCE). For the HARQ-ACK of the multicast PDSCH, the 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 set, and a part of the plurality of PUCCH resource sets includes the UE-specific PUCCH resource / UE-common PUCCH resource. The PUCCH resource set when the number of UCI bits is N0 or less may include the UE-common PUCCH resource, and the PUCCH resource set when the number of UCI bits is greater than N0 or N1 may not include the UE-common PUCCH resource. Each PUCCH resource / resource set may be the PUCCH resource / resource set for the unicast PDSCH in Rel.15 / 16. Separately from the PUCCH resource / resource set for the unicast PDSCH, a PUCCH resource / resource set for the multicast PDSCH may be set.

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

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

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

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

[0095] The UE-specific PUCCH resource may follow either of the following Resources A and B.

[0096] [Resource A] The UE uses the PUCCH resource set configured by upper layer signaling as the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH. DCI may not be used for the determination of this PUCCH resource. In this case, the PUCCH resource indicator (PRI) field can be omitted from the DCI that schedules the multicast PDSCH, reducing the DCI overhead. By configuring through UE-specific upper layer signaling, orthogonal resources can be allocated among UEs.

[0097] [Resource B] Multiple PUCCH resource sets are configured by upper layer signaling, and the UE selects (determines) the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH from among the multiple PUCCH resource sets 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 multiple PUCCH resource sets configured by upper layer signaling) based on the number of bits (size) of the 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 that schedules the multicast PDSCH and the index of the first CCE of the PDCCH that detects the DCI that schedules the multicast PDSCH.

[0098] The PRI may follow either of the following PRI fields 1 and 2.

[0099] [PRI Field 1] In the example of FIG. 9A, the PRI field is extended to indicate a PRI (PRI0 to 3) for each UE (UE-specifically) from UE0 to UE3. The UE sets the PRI field for its own UE by upper layer signaling and determines the PUCCH resource based on the set PRI field. The UE may ignore the un-set (for other UEs) PRI field.

[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 upper layer signaling, and the UE determines the PUCCH resource using its own UE's PRI (PUCCH resource).

[0101] The UE may be able to know the PUCCH resources of other UEs and control channel collisions based on the PUCCH resources of other UEs.

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

[0103] 《Aspect 2-2》 The UE for which the multicast PDSCH is scheduled by the UE common DCI transmits the HARQ-ACK of the multicast PDSCH using the UE common PUCCH resource.

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

[0105] [Resource A] The UE uses the PUCCH resource set by upper layer signaling as the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH. DCI may not be used for the determination of this PUCCH resource. In this case, the PUCCH resource indicator (PRI) field can be omitted in the DCI for scheduling the multicast PDSCH, and the overhead of the DCI can be reduced. By setting through UE individual upper layer signaling, orthogonal resources can be allocated among UEs.

[0106] [Resource B] Multiple PUCCH resources are set by upper layer signaling, and the UE selects (determines) the PUCCH resource for transmitting UCI including HARQ-ACK of the multicast PDSCH from among the multiple 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 multiple PUCCH resource sets set by upper layer signaling) based on the number of bits (size) of the 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 that detected the DCI for scheduling the multicast PDSCH.

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

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

[0109] 《Mode 3-1》 The UE multiplexes (maps to one channel) the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH on one channel. The channel may be the PUCCH or the PUSCH.

[0110] The UE generates the HARQ-ACK bit sequences of the unicast PDSCH and the multicast PDSCH according to the counting method of the HARQ-ACK of the PDSCH for the existing semi-static / dynamic HARQ-ACK codebook (HARQ codebook), and may transmit the generated HARQ-ACK bit sequences in one channel resource. In this case, since the UE can perform one-channel transmission, the resource utilization efficiency can be improved. The total DAI / counter DAI may be counted across the scheduling DCI of the unicast PDSCH and the scheduling DCI of the multicast PDSCH.

[0111] The channel resource to which the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH are mapped may follow either of the following Resources A and B.

[0112] [Resource A] The UE transmits the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH in the PUCCH / PUSCH resource for the unicast PDSCH. Since this channel resource is a UE-specific resource, the control becomes easier.

[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 to the HARQ-ACK of the unicast PDSCH).

[0114] The UE may obtain DCI (PRI field / index of the first CCE) required for the selection of PUCCH resources according to the existing selection rules of DCI in the time / frequency direction. Here, the UE may not 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 numbered in ascending order of the serving cell index for the same PDCCH monitoring occasion, and may be the last DCI format among the DCI formats numbered in ascending order of the PDCCH monitoring occasion index.

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

[0117] [Resource B] The UE transmits the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH in the PUCCH / PUSCH resources for the multicast PDSCH. Since this channel resource is an individual resource, control becomes easier.

[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 multiplexing the HARQ-ACK of the unicast PDSCH with the HARQ-ACK of the unicast PDSCH).

[0119] The UE may obtain the DCI (PRI field / index of the first CCE) required for the selection of the PUCCH resource according to the existing selection rule of the time / frequency direction DCI. Here, the UE may not 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 numbered in ascending order of the serving cell index for the same PDCCH monitoring occasion, and may be the last DCI format among the DCI formats numbered in ascending order of the PDCCH monitoring occasion index.

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

[0122] As a method for transmitting HARQ-ACK for the multicast PDSCH, when NACK-only feedback is specified / set, the HARQ-ACK information to be transmitted may be calculated by the logical operation of the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH. The HARQ-ACK information bit of 0 may represent NACK, and the HARQ-ACK information bit of 1 may represent 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), since the logical operation result is 0, the UE may transmit NACK by NACK-only feedback.

[0123] When mapping (multiplexing) the HARQ-ACK for the unicast PDSCH and the HARQ-ACK for the multicast PDSCH to one channel, the bits of the HARQ-ACK may be ordered according to at least one of the type indicating the unicast PDSCH or the multicast PDSCH (cast type of the PDSCH), the slot index of the PDSCH, and the cell index of the PDSCH. When the HARQ-ACK is ordered by the cast type of the PDSCH, it may be in the order of the HARQ-ACK of the unicast PDSCH, the HARQ-ACK of the multicast PDSCH, or in the order of 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 (map to different channels) the HARQ-ACK for the unicast PDSCH and the HARQ-ACK for the multicast PDSCH in one channel. Each channel may be a PUCCH or a PUSCH.

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

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

[0127] Within a certain slot (or sub-slot), the UE may transmit only one of the PUCCH carrying the HARQ-ACK for the unicast PDSCH and the PUCCH carrying the HARQ-ACK for the multicast PDSCH. Within a certain slot (or sub-slot), a UE instructed to perform feedback for both the unicast PDSCH and the multicast PDSCH (by the PDSCH-to-HARQ feedback indicator field) may drop either feedback. It may be specified that the UE does not assume that it will be instructed to perform feedback for both the unicast PDSCH and the multicast PDSCH within a certain slot (or sub-slot).

[0128] The UE reports by UE capability information that it supports the transmission of both (simultaneous / multiplexed / within one channel) the HARQ-ACK for the multicast PDSCH and the HARQ-ACK for the unicast PDSCH, and if simultaneous transmission occurs (the occasions overlap) between the HARQ-ACK for the multicast PDSCH and the HARQ-ACK for the unicast PDSCH, the UE may transmit both the HARQ-ACK for the multicast PDSCH and the HARQ-ACK for the unicast PDSCH. In this case, the UE may transmit the HARQ-ACK for the multicast PDSCH and the HARQ-ACK for the unicast PDSCH by time division multiplexing (TDM), or may transmit using Mode 3-1.

[0129] The UE may distinguish / discriminate between the DCI for multicast PDSCH and the DCI for unicast PDSCH (and may be in accordance with at least one of the fifth to ninth embodiments).

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

[0131] <Fourth Embodiment> In at least one of the first to third embodiments, the method for determining the PUCCH resource (e.g., the method for determining the PRI) may be applied to the determination of the TPC command for PUCCH (the TPC command field for the scheduled PPUCCH) / HARQ timing (the 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 the PTM transmission mode 2, the UE determines whether the PDSCH scheduled by the DCI is a unicast PDSCH or a multicast PDSCH (whether the DCI schedules a unicast PDSCH or a multicast PDSCH) based on the resource allocation of the PDSCH scheduled by the DCI.

[0134] The multicast PDSCH dedicated resource and the unicast PDSCH dedicated resource may be set by upper layer signaling. Whether the scheduled PDSCH resource corresponds to the multicast PDSCH dedicated resource or the unicast PDSCH dedicated resource, it may be determined whether the PDSCH is a unicast PDSCH or a multicast PDSCH. The resource may be in the 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 FIGS. 10A and 10B, the frequency domain resource for the multicast PDSCH and the frequency domain resource for the unicast PDSCH are set. In the example of FIG. 10A, if the frequency domain resource of the PDSCH scheduled by the UE-specific DCI is within the frequency domain resource for the multicast PDSCH, the UE determines that the PDSCH is a multicast PDSCH. In the example of FIG. 10B, if the frequency domain resource of the PDSCH scheduled by the UE-specific DCI is within the frequency domain resource for the unicast PDSCH, the UE determines that the PDSCH is a unicast PDSCH.

[0136] One of the unicast resource and the multicast resource may be included in the other (may be surrounded). For example, a part within the unicast resource may be cut out (perforated), and that part may be the multicast resource.

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

[0138] <Sixth Embodiment> In PTM transmission mode 2, the UE determines whether the PDSCH is a unicast PDSCH or a multicast PDSCH (whether the DCI schedules a unicast PDSCH or a multicast PDSCH) based on the reception / detection result of the DCI that schedules the 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 UE-specific DCI dedicated CORESET / search space for scheduling multicast PDSCH (multicast dedicated CORESET / search space) is configured.

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

[0142] In the example of FIG. 11, a multicast dedicated CORESET / search space and a unicast dedicated CORESET / search space are configured. When the UE detects a DCI within the multicast dedicated CORESET, it determines that this DCI schedules a multicast PDSCH. The multicast dedicated CORESET / search space and the unicast dedicated CORESET / search space may or may not overlap.

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

[0144] If the time / frequency resources of the multicast dedicated CORESET / search space overlap with the time / frequency resources of other CORESET / search spaces, it is conceivable that the UE cannot determine to which CORESET / search space the detected DCI belongs. To avoid this, the base station may set different sequence IDs for each CORESET / search space and use different sequences for the DMRS of the PDCCH corresponding to each CORESET / search space. Thereby, even when the time / frequency resources of the multicast dedicated CORESET / search space overlap with the time / frequency resources of other CORESET / search spaces, the UE can determine to which CORESET / search space the detected DCI belongs.

[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, an increase in the number of blind detections can be prevented. The DCI for scheduling the multicast PDSCH may be a new DCI format for the multicast PDSCH. When a new DCI format is defined, the UE may attempt blind detection only when set by upper layer signaling.

[0146] By using a multicast - dedicated CORESET / search space, the resources for monitoring DCI can be restricted, and the UE power consumption can be suppressed.

[0147] 《Aspect 6 - 2》 A new field may be defined within an existing DCI format. The new field may indicate whether the PDSCH scheduled by that 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 exist within the existing DCI format only when the use of the new field is set by upper - layer signaling.

[0148] In the example of FIG. 12, the existing DCI format includes an existing field and a new field. When the value of the new field is 0, it indicates that this DCI schedules a unicast PDSCH, and when the value of the new field is 1, it indicates that this DCI schedules a multicast PDSCH.

[0149] 《Aspect 6 - 3》 A new UE - specific RNTI may be defined. When the UE detects a DCI having 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 having a CRC scrambled by the new RNTI only when the scheduling of the multicast PDSCH (new RNTI) is set by upper - layer signaling.

[0150] 《Aspect 6 - 4》 If some special values of some special fields in the existing DCI format are decoded, the UE may consider (determine, confirm, validate) that the DCI schedules a multicast PDSCH. Otherwise, the UE may consider 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 the special field and the special value may be at least one of the following. · The value of the frequency domain resource allocation field is set to all 0s or all 1s. · The value of the time domain resource allocation field is set to all 0s or all 1s. · The value of the frequency hopping flag field is set to all 0s or all 1s. · 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 0s or all 1s. · The value of the redundancy version field is set to all 0s or all 1s. · 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 transmission power control (TPC) command field for PUCCH is set to all 0s or all 1s. · The value of the transmission 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 0s or all 1s. · The value of the precoding information and layer number field is set to all 0s or all 1s. · The value of the antenna port field is set to all 0s or all 1s. · 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 determining that the received DCI schedules a multicast PDSCH, the UE may obtain resource allocation information for the multicast PDSCH using the value of each indication field in that DCI. Resource allocation information for the unicast PDSCH and resource allocation information for the multicast PDSCH may be set by higher layer signaling. If the resource allocation information for the multicast PDSCH is not set (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, when the UE determines that the UE-specific DCI schedules the multicast PDSCH, the UE may determine the resources of the multicast PDSCH based on the configured resource allocation information for multicast and the DCI. When the UE determines that the UE-specific DCI schedules the unicast PDSCH, the UE may determine the resources of the unicast PDSCH based on the configured resource allocation information for unicast and the DCI. One value of the field indicating the resource allocation in the DCI may indicate different resources depending on whether the DCI schedules the multicast PDSCH or the unicast PDSCH.

[0155] The resources for the multicast PDSCH may be referred to as common frequency resources or may be resources that are commonly recognized among multiple UEs. The resource allocation method for the multicast PDSCH may select / indicate resources from among the common frequency resources, rather than using the existing resource allocation method of selecting / indicating resources from within the BWP.

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

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

[0158] <The Seventh Embodiment> In the fifth and sixth embodiments, the operations mainly when the PTM transmission method 2 is used have been described, but the fifth and sixth embodiments may be applied when the PTM transmission method 1 is used.

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

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

[0161] In PTM transmission method 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 the sequence ID set for the multicast-dedicated CORESET / search space. By limiting the blind detection of the new DCI format within the multicast-dedicated CORESET / search space, the UE power consumption can be suppressed.

[0162] In the example of FIG. 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 within the multicast-only CORESET / search space. The UE does not perform blind detection of a new DCI format within the unicast-only CORESET / search space (it does not assume receiving a new DCI format within the unicast-only CORESET / search space).

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

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

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

[0166] If the UE fails to receive / decrypt the PDSCH (unicast PDSCH / multicast PDSCH), it may send a NACK. The PUCCH resources for sending NACK may be common for both the unicast PDSCH and the multicast PDSCH.

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

[0168] [Procedure 1] It is notified by upper layer signaling that the PDSCH is a unicast PDSCH. If the UE successfully receives / decodes the PDSCH, the UE may send an ACK.

[0169] [Procedure 2] It is notified by upper layer signaling that the PDSCH is a multicast PDSCH and ACK / NACK feedback is configured / indicated. If the UE successfully receives / decodes the PDSCH, the UE may send an ACK.

[0170] [Procedure 3] It is notified by upper layer signaling that the PDSCH is a multicast PDSCH and NACK-only feedback is configured / indicated. If the UE successfully receives / decodes the PDSCH, the UE may not send a HARQ-ACK.

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

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

[0173] Until the decoding of the TB in the received PDSCH is successful, the UE cannot recognize whether the PDSCH is a unicast PDSCH or a multicast PDSCH. In PDSCH demodulation / decoding, the physical (PHY) layer may not need to distinguish between unicast PDSCH and multicast PDSCH.

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

[0175] [UE Operation] The UE may decode the TB in the scheduled PDSCH, read the upper layer signaling (e.g., MAC sub-header) 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 the creation of HARQ-ACK information bit series, the determination of PUCCH resources, and PUCCH transmission.

[0176] The UE may perform this UE operation only when set by upper layer signaling. The UE may perform this UE operation only for the PDSCH 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 the PDSCH scheduled by DCI having a CRC scrambled by a specific RNTI. The specific RNTI may be, for example, C-RNTI.

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

[0178] For the multicast PDSCH and the 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 mode 2) is 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 perform decoding (blind decoding) of 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 was used (whether the PDSCH is multicast or unicast) by performing error determination for each TB / code word (CW) / code block group (CBG).

[0180] Thus, 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 upper layer signaling (e.g., MAC sub-header) included in the TB. In this case, it may be specified that the UE is not notified by the upper layer signaling (e.g., MAC sub-header) included in the TB whether the PDSCH is multicast or unicast. In this case, the control overhead can be suppressed.

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

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

[0183] <Ninth Embodiment> When the multicast PDSCH is set by upper layer signaling, the UE may determine (assume) that the DL assignment DCI having the CRC scrambled by the C-RNTI schedules the multicast PDSCH (it may be specified that the UE does not assume that the unicast PDSCH is scheduled). When the multicast PDSCH is set by upper 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 appropriately determine whether the PDSCH is a unicast PDSCH or a multicast PDSCH.

[0185] <Embodiment 10> UE capabilities corresponding to at least one function (feature) in the first to ninth embodiments may be defined. When the UE reports this UE capability, the UE may perform the corresponding function. When the UE reports this UE capability and the upper layer parameters corresponding to this function are set, the UE may perform the corresponding function. Upper layer parameters (RRC information elements) corresponding to this function may be defined. When this upper layer parameter is set, the UE may perform the corresponding function.

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

[0187] The UE capability may indicate whether the UE supports PTM transmission mode 1.

[0188] The UE capability may indicate whether the UE supports PTM transmission mode 2.

[0189] The UE capability may indicate whether the UE supports a multicast dedicated CORESET / search space. The UE capability may indicate the maximum number (the number supported) of multicast dedicated CORESET / search spaces.

[0190] The UE capability may indicate the transmission method of HARQ-ACK for the multicast PDSCH (ACK / NACK feedback or NACK-only feedback).

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

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

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

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

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

[0196] In addition, the wireless communication system 1 may support dual connectivity (multi-RAT dual connectivity (MR-DC)) between a plurality of Radio Access Technologies (RATs). 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 base station (eNB) of LTE (E-UTRA) is the Master Node (MN), and the base station (gNB) of NR is the Secondary Node (SN). In NE-DC, the base station (gNB) of NR is the MN, and the base station (eNB) of LTE (E-UTRA) is the SN.

[0198] The radio communication system 1 may support dual connectivity between a plurality of base stations within the same RAT (for example, dual connectivity where both the MN and the SN are base stations (gNBs) of NR (NR-NR Dual Connectivity (NN-DC))).

[0199] The radio communication system 1 may include a base station 11 that forms a relatively wide-coverage macro cell C1, and a base station 12 (12a - 12c) disposed within the macro cell C1 and forming a small cell C2 that is narrower than the macro cell C1. The user terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and the user terminal 20 are not limited to the mode shown in the figure. Hereinafter, when the base stations 11 and 12 are not distinguished, they are collectively referred to as the base station 10.

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

[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)). Macro cell C1 may be included in FR1, and 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 higher than 24 GHz (above-24 GHz). Note that the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these. For example, FR1 may correspond to a frequency band higher than FR2.

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

[0203] The plurality of base stations 10 may be connected by wire (e.g., an optical fiber compliant with Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, the base station 11 corresponding to the upper-level 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 via another base station 10 or directly. The core network 30 may include at least one of, for example, Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0205] The user terminal 20 may be a terminal corresponding to at least one of communication systems such as LTE, LTE-A, 5G, etc.

[0206] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access method 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 wireless access method may be referred to as a waveform. Note that in the wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

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

[0210] User data, upper layer control information, System Information Block (SIB), etc. are transmitted by PDSCH. User data, upper layer control information, etc. may be transmitted by PUSCH. Also, Master Information Block (MIB) may be transmitted by PBCH.

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

[0212] Note that the DCI for scheduling PDSCH may be called DL assignment, DL DCI, etc., and the DCI for scheduling PUSCH may be called UL grant, UL DCI, etc. Note that PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0213] For PDCCH detection, a control resource set (CORESET) and a search space may be used. A CORESET corresponds to the resources for searching for DCI. A search space corresponds to the search area and search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the 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 referred to as a search space set. Note that the "search space", "search space set", "search space configuration", "search space set configuration", "CORESET", "CORESET configuration", etc. in the present disclosure may be read interchangeably with each other.

[0215] Uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (e.g., may be referred to as Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR) may be transmitted by PUCCH. A random access preamble for connection establishment with the cell may be transmitted by PRACH.

[0216] Note that in the present disclosure, the downlink, uplink, etc. may be expressed without adding "link". Also, the "Physical" may be omitted at the beginning of various channels.

[0217] In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (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 (Primary Synchronization Signal (PSS)) and a secondary synchronization signal (Secondary Synchronization Signal (SSS)). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, an SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0219] Also, in the wireless communication system 1, as the uplink reference signal (Uplink Reference Signal (UL-RS)), a sounding reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may be transmitted. Note that DMRS may also be called a UE-specific reference signal.

[0220] (Base station) FIG. 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 transmission / reception unit 120, a transmission / reception antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140 may be provided.

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

[0222] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

[0223] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission / reception, measurement, etc., using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140. The control unit 110 may generate data, control information, a sequence, etc., to be transmitted as a signal, and transfer it to the transmission / reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of a communication channel, state management of the base station 10, management of radio resources, etc.

[0224] The transmission / reception 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 transmission / reception unit 120 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

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

[0226] The transmission / reception antenna 130 can be composed of an antenna described based on the common knowledge in the technical field related to the present disclosure, such as an array antenna.

[0227] The transmission / reception unit 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, etc. The transmission / reception unit 120 may receive the above-described uplink channel, uplink reference signal, etc.

[0228] The transmission / reception unit 120 may form at least one of a transmission beam and a reception beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

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

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

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

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

[0233] The transceiver unit 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 on the acquired baseband signal, and acquire user data, etc.

[0234] The transmission / reception unit 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) with devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0236] Note that the transmission unit and reception unit of the base station 10 in the present disclosure may be configured by at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140.

[0237] The transmission / reception unit 120 may transmit settings of physical uplink control channel (PUCCH) resources for the transmission of hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information for the multicast physical downlink shared channel (PDSCH). The control unit 110 may control the reception of the HARQ-ACK information using the PUCCH resources.

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

[0239] (User Equipment) FIG. 18 is a diagram showing an example of the configuration of a user equipment according to an embodiment. The user equipment 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230. Note that one or more of the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may be provided.

[0240] Note that in this example, the functional blocks of the characteristic portions in the present embodiment are mainly shown, and the user equipment 20 may be assumed to have other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

[0241] The control unit 210 controls the entire user equipment 20. The control unit 210 may be composed of a controller, a control circuit, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

[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 transmission / reception 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 transmission / reception unit 220 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

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

[0245] The transmission / reception antenna 230 can be composed of an antenna described based on the common understanding in the technical field related to the present disclosure, such as an array antenna.

[0246] The transmission / reception unit 220 may receive the above-described downlink channel, synchronization signal, downlink reference signal, etc. The transmission / reception unit 220 may transmit the above-described uplink channel, uplink reference signal, etc.

[0247] The transmission / reception unit 220 may form at least one of a transmission beam and a reception beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

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

[0249] The transmission / reception unit 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, digital-to-analog conversion, etc. on the bit string to be transmitted, and output a baseband signal.

[0250] Whether to apply the DFT process may be based on the settings of transform precoding. The transceiver unit 220 (transmission processing unit 2211) may perform the DFT process as the above-mentioned transmission processing in order to transmit a certain channel (for example, PUSCH) using the DFT-s-OFDM waveform when transform precoding is enabled for that channel, or may not perform the DFT process as the above-mentioned transmission processing if not.

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

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

[0253] The transceiver unit 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 unit 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 (for example, RSRP), reception quality (for example, RSRQ, SINR, SNR), signal strength (for example, RSSI), propagation path information (for example, CSI), etc. The measurement results may be output to the control unit 210.

[0255] Note that the transmission unit and reception unit of the user terminal 20 in the present disclosure may be configured by at least one of a transmission / reception unit 220 and a transmission / reception antenna 230.

[0256] The transmission / reception unit 220 may receive a setting of a physical uplink control channel (PUCCH) resource for transmission of hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information for a multicast physical downlink shared channel (PDSCH). The control unit 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 setting may be either a terminal-specific setting or a terminal-common setting (First and Second Embodiments).

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

[0260] The transmission / reception unit 220 may receive downlink control information for scheduling a physical downlink shared channel (PDSCH). The control unit 210 may determine whether the PDSCH is multicast or unicast based on at least one of upper 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 transceiver unit 220 may receive the configuration of the multicast PDSCH. When the resource indicated by the downlink control information is included in the configuration, the control unit 210 may determine that the PDSCH is a multicast (Fifth Embodiment).

[0263] When the downlink control information satisfies the condition, the control unit 210 may determine that the PDSCH is a multicast (Sixth Embodiment).

[0264] (Hardware Configuration) Note that the block diagrams used in the description of the above embodiments show blocks of functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly (e.g., using wired, wireless, etc.) connected and realized using these multiple devices. The functional block may be realized by combining software with the above one device or the above multiple devices.

[0265] Here, functions include, but are not limited to, judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, regarded as, notification (broadcasting), notification (notifying), communication (communicating), forwarding, configuration (configuring), reconfiguration (reconfiguring), allocation (allocating, mapping), assignment (assigning), etc. For example, a functional block (component) that functions as transmission may be referred to as a transmission unit, a transmitter, etc. In any case, as described above, the realization method 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 the processing of the wireless communication method of the present disclosure. FIG. 19 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may physically be 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, and the like.

[0267] In the present disclosure, words such as device, circuit, device, section, unit, etc. can be read interchangeably with each other. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without including some devices.

[0268] For example, although only one processor 1001 is shown, there may be a plurality of processors. Also, the processing may be executed by one processor, or the processing may be executed by two or more processors simultaneously, sequentially, or using other methods. Note that 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 causing the processor 1001 to load a predetermined software (program) onto hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of reading and writing data in the memory 1002 and the storage 1003.

[0270] Processor 1001 controls the entire computer by operating, for example, an operating system. Processor 1001 may be constituted by a Central Processing Unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, at least a part of the above-described control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by processor 1001.

[0271] Further, processor 1001 reads a program (program code), software module, data, etc. from at least one of storage 1003 and communication device 1004 into memory 1002, and executes various processes according to these. As the program, a program for causing a computer to execute at least a part of the operations described in the above embodiments is used. For example, control unit 110 (210) may be realized by a control program stored in memory 1002 and operating in processor 1001, and the same may apply to other functional blocks.

[0272] Memory 1002 is a computer-readable recording medium, and may be constituted by, for example, at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other appropriate storage media. Memory 1002 may be referred to as a register, cache, main memory (main storage device), etc. Memory 1002 can store a program (program code), software module, etc. executable for implementing the wireless communication method according to an embodiment of the present disclosure.

[0273] Storage 1003 is a computer-readable recording medium and may be composed of, for example, at least one of a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (such as a compact disc (Compact Disc ROM (CD-ROM), etc.), a digital versatile disc, a Blu-ray (registered trademark) disc), a removable disk, a hard disk drive, a smart card, a flash memory device (such as a card, a stick, a key drive), a magnetic stripe, a database, a server, and other appropriate storage media. Storage 1003 may be referred to as an auxiliary storage device.

[0274] Communication device 1004 is hardware (a transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. Communication device 1004 may include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to implement at least one of frequency-division duplexing (Frequency Division Duplex (FDD)) and time-division duplexing (Time Division Duplex (TDD)). For example, the above-described transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be implemented by communication device 1004. The transmission / reception unit 120 (220) may be physically or logically separated and implemented as a transmission unit 120a (220a) and a reception unit 120b (220b).

[0275] Input device 1005 is an input device (such as a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives external input. Output device 1006 is an output device (such as a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs external output. Note that input device 1005 and output device 1006 may have an integrated configuration (such as a touch panel).

[0276] Also, 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 for each device.

[0277] Also, 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), and a Field Programmable Gate Array (FPGA), 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 hardware components.

[0278] (Modification example) In addition, for the terms described in this disclosure and the terms necessary for understanding this disclosure, they may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be read interchangeably with each other. Also, a signal may be a message. A reference signal may also be abbreviated as RS and may be called a Pilot, a pilot signal, etc. depending on the applicable standard. Also, a Component Carrier (CC) may be called a cell, a frequency carrier, a carrier frequency, etc.

[0279] The wireless frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting the wireless frame may be called a subframe. Further, the subframe may be composed of one or more slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) independent of numerology.

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

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

[0282] The slot may include a plurality of mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. Also, the mini-slot may be called a sub-slot. The mini-slot may be composed of a smaller number of symbols than the slot. The PDSCH (or PUSCH) transmitted in a time unit larger than the mini-slot may be called PDSCH (PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the mini-slot may be called PDSCH (PUSCH) mapping type B.

[0283] The radio frame, sub-frame, slot, mini-slot, and symbol all represent time units when transmitting signals. Different names corresponding to each of them may be used. Note that the time units such as frames, sub-frames, slots, mini-slots, and symbols in this disclosure may be read interchangeably with each other.

[0284] For example, one sub-frame may be called a TTI, or a plurality of consecutive sub-frames may be called a TTI, or one slot or one mini-slot may be called a TTI. That is, at least one of the sub-frame and the TTI may be the sub-frame (1 ms) in the existing LTE, or 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, a mini-slot, etc. instead of a sub-frame.

[0285] Here, the TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) to each user terminal in TTI units. Note that the definition of the TTI is not limited to this.

[0286] The TTI may be a transmission time unit such as a channel-coded data packet (transport block), code block, codeword, etc., or may be a processing unit such as scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (e.g., number of symbols) in which a transport block, code block, codeword, etc. are actually mapped may be shorter than the TTI.

[0287] Note that when one slot or one mini-slot is called a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) may be the minimum time unit of scheduling. Also, the number of slots (number of mini-slots) constituting the minimum time unit of the 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), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, mini-slot, sub-slot, slot, etc.

[0289] Note that a long TTI (e.g., normal TTI, subframe, etc.) may be read as a TTI having a time length exceeding 1 ms, or a short TTI (e.g., shortened TTI, etc.) may be read as a TTI having a TTI length less than that of the long TTI and a TTI length of 1 ms or more.

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

[0291] Also, an RB may include one or more symbols in the time domain, and may have a length of 1 slot, 1 mini-slot, 1 subframe, or 1 TTI. 1 TTI, 1 subframe, etc. may each be composed of one or more resource blocks.

[0292] Note that one or more RBs may be referred to as physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc.

[0293] Also, a resource block may be composed of one or more resource elements (REs). For example, 1 RE may be a radio resource area of 1 subcarrier and 1 symbol.

[0294] A bandwidth part (BWP) (which may also be called a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (RBs) for a certain numerology in a certain carrier. Here, the common RB may be specified by the index of the RB based on the common reference point of the carrier. A PRB is defined in a certain BWP and may be numbered within that BWP.

[0295] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). For a UE, one or more BWPs may be configured within one carrier.

[0296] At least one of the configured BWPs may be active, and the UE may not be assumed to transmit and receive a predetermined signal / channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

[0297] Note that the structures such as the radio frame, subframe, slot, mini-slot, and symbol described above 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 mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of sub-carriers included in an RB, and the number of symbols, symbol length, cyclic prefix (CP) length, etc. within a TTI can be changed in various ways.

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

[0299] The names used for parameters, etc. in the present disclosure are not limiting names in any way. Furthermore, the mathematical formulas using these parameters, etc. may be different from those explicitly disclosed in the present disclosure. Since various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, the various names assigned to these various channels and information elements are not limiting names 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, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0301] Also, information, signals, etc. may be output from at least one of the upper layer to the lower layer and from the lower layer to the upper layer. Information, signals, etc. may be input and output via a plurality of network nodes.

[0302] The input and output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information, signals, etc. may be overwritten, updated, or appended. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.

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

[0304] Note that physical layer signaling may also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Also, RRC signaling may also be referred to as an RRC message, and for example, it may be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. Further, MAC signaling may be notified, for example, using a MAC Control Element (CE).

[0305] Also, the notification of predetermined information (for example, the notification of "being X") is not limited to explicit notification and may be performed implicitly (for example, by not performing the notification of the predetermined information or by the notification of another piece of information).

[0306] The determination may be made based on a value represented by 1 bit (0 or 1), a boolean value represented by true or false, or a numerical comparison (for example, comparison with a predetermined value).

[0307] Software should be interpreted 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, execution threads, procedures, functions, etc., regardless of whether it is called software, firmware, middleware, microcode, a hardware description language, or another name.

[0308] Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, when software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, optical fiber cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technologies (such as infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of the transmission medium.

[0309] The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may mean the devices (such as base stations) included in the network.

[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", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", "panel", etc. may be used interchangeably.

[0311] In the present 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. The base station may also be referred to by terms such as macro cell, small cell, femto cell, 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 divided into multiple smaller areas, and each of the smaller areas can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services in this coverage.

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

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

[0315] At least one of the base station and the mobile station may be referred to as a transmission device, a reception device, a wireless communication device, etc. Note that 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.), a moving body that moves unmanned (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanoid or unmanned). Note that at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0316] Also, the base station in the present disclosure may be read as a user terminal. For example, for a configuration in which communication between the base station and the user terminal is replaced with communication between a plurality of user terminals (which may be referred to as, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.), each aspect / embodiment of the present disclosure may be applied. In this case, the functions of the above-described base station 10 may be configured to be functions of the user terminal 20. Also, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (e.g., "sidelink"). For example, the uplink channel, the downlink channel, etc. may be read as the sidelink channel.

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

[0318] In the present disclosure, operations assumed to be performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (for example, Mobility Management Entity (MME), Serving-Gateway (S-GW), etc., but not limited thereto), or a combination thereof.

[0319] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched and used during execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be rearranged as long as there is no contradiction. For example, for the methods described in the present disclosure, the elements of various steps are presented using an exemplary order and are not limited to the specific order presented.

[0320] Each aspect / embodiment described in the present disclosure may be applicable to systems using 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) (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 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable wireless communication methods, and next-generation systems extended based on these. Also, multiple systems may be combined (for example, a combination of LTE or LTE-A and 5G) and applied.

[0321] The description "based on" used in the present disclosure does not mean "only based on" unless otherwise specified. In other words, the description "based on" means both "only based on" and "at least based on".

[0322] Any reference to an element using terms such as "first", "second", etc. used in this disclosure does not generally limit the quantity or order of those elements. These terms can be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not mean that only two elements can be employed or that the first element must precede the second element in any way.

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

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

[0325] Also, "determining" may be considered to be "resolving", "selecting", "choosing", "establishing", "comparing", etc. That is, "determining" may be considered to be "determining" some operation.

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

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

[0328] As used in the present disclosure, the terms "connected" and "coupled", or any variations thereof, mean 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 "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "accessed".

[0329] In the present disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and also, as some non-limiting and non-exhaustive examples, using electromagnetic energy having wavelengths in the radio frequency region, microwave region, optical (both visible and invisible) region, etc.

[0330] In the present disclosure, the term "A and B are different" may mean that "A and B are different from each other". Note that the term may also mean that "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] In the present disclosure, when terms such as "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0332] In the present disclosure, for example, when articles are added by translation, such as a, an and the in English, the present disclosure may include that the nouns following these articles are in the plural form.

[0333] As described above, the invention according to the present disclosure has been described in detail. However, it is obvious to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and changed 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 for illustrative purposes and does not impose 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, An ID corresponding to the search space is set, The receiving unit is a terminal that uses a sequence corresponding to the ID for the DCI.

2. The terminal according to claim 1, wherein 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, the control unit determines the time resource of the PDSCH based on the TDRA information for multicast.

3. 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; An ID corresponding to the search space is set, A wireless communication method for a terminal, in which a sequence corresponding to the ID is used for the DCI.

4. 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, An ID corresponding to the search space is set, A base station, wherein a sequence corresponding to the ID is used for the DCI.

5. 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, An ID corresponding to the search space is set, The receiving unit uses a sequence corresponding to the ID for the DCI, 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