Terminals, wireless communication methods, base stations and systems

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 studied.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

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

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

[0007] However, previous NR specifications have not adequately considered how UEs (Underground Users) should receive multicast downlink data. If multicast downlink data is not received properly, system performance may deteriorate, such as a decrease in throughput.

[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, wireless communication method, base station, and system for appropriately receiving multicast downlink data. [Means for solving the problem]

[0009] A terminal according to one aspect of this disclosure includes a receiving unit that receives upper-layer signaling indicating a search space and downlink control information (DCI) that schedules 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, wherein an ID corresponding to the search space is set, and the receiving unit uses a sequence corresponding to the ID to provide the DCI. When time domain resource assignment (TDRA) information for unicast and TDRA information for multicast are set, the control unit determines that the PDSCH is multicast, and determines the time resources of the PDSCH based on the multicast TDRA information. . [Effects of the Invention]

[0010] According to one aspect of this disclosure, multicast downlink data can be properly received. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 shows an example of the multicast PDSCH receiving procedure. [Figure 2] Figure 2 shows another example of the multicast PDSCH receiving procedure. [Figure 3] Figures 3A to 3C show an example of NACK-only feedback. [Figure 4] Figures 4A and 4B show examples of frequency resources used in multicast PDSCH. [Figure 5] Figure 5 shows an example of PUCCH resource settings according to Embodiment 1-3. [Figure 6] Figure 6 shows an example of PUCCH resource settings according to Embodiment 1-4. [Figure 7] Figure 7 shows an example of PUCCH resource settings related to setting method 1 in embodiment 1-6. [Figure 8] Figure 8 shows an example of PUCCH resource settings related to setting method 2 in embodiment 1-6. [Figure 9] Figures 9A and 9B show an example of PUCCH resource settings according to Embodiment 2-1. [Figure 10] Figures 10A and 10B show an example of a multicast PDSCH / unicast PDSCH determination method according to the fifth embodiment. [Figure 11] Figure 11 shows an example of a method for determining multicast PDSCH / unicast PDSCH according to embodiment 6-1. [Figure 12] Figure 12 shows an example of a method for determining multicast PDSCH / unicast PDSCH according to embodiment 6-2. [Figure 13] Figure 13 shows an example of PDSCH scheduling according to the sixth embodiment. [Figure 14] Figure 14 shows an example of PDCCH monitoring according to the seventh embodiment. [Figure 15]FIG. 15 is a diagram showing another example of PDCCH monitoring according to the seventh embodiment. [Figure 16] FIG. 16 is a diagram showing an example of the schematic configuration of a wireless communication system according to an embodiment. [Figure 17] FIG. 17 is a diagram showing an example of the configuration of a base station according to an embodiment. [Figure 18] FIG. 18 is a diagram showing an example of the configuration of a user terminal according to an embodiment. [Figure 19] FIG. 19 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment.

MODE FOR CARRYING OUT 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 PF1 are PFs used to transmit UCIs of up to 2 bits. For example, the UCI may be at least one of a delivery acknowledgment (HARQ-ACK, also known as an acknowledgment (ACK), or negative-acknowledgment (NACK)) and a scheduling request (SR). PF0 can be assigned to 1 or 2 symbols and is therefore also called a short PUCCH or a sequence-based short PUCCH. On the other hand, PF1 can be assigned to 4-14 symbols and is therefore also called a long PUCCH. 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, the UCI value, a slot number, and a symbol number. In PF1, multiple user terminals may be code-divided multiplexed (CDM) within the same physical resource block (PRB) by time-domain block diffusion using at least one of CS and time-domain (TD)-orthogonal cover code (OCC).

[0014] PF2-4 are PFs used for transmitting UCI (e.g., Channel State Information (CSI), or at least one of CSI, HARQ-ACK, and SR) exceeding 2 bits. PF2 can be assigned to 1 or 2 symbols and is therefore also called a short PUCCH, etc. PF3 and PF4, on the other hand, can be assigned to 4-14 symbols and are therefore also called long PUCCH, etc. PF4 may allow multiple user terminals to perform CDM using pre-DFT (Frequency Domain (FD)-OCC) block spread.

[0015] Intra-slot frequency hopping may be applied to PF1, PF3, and PF4. The length of PUCCH is N. symb Therefore, the length before frequency hopping (first hop) is floor(N symb It may also be / 2), and the length after frequency hopping (second hop) is ceil(N symb (2) is also acceptable.

[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 transmission on the uplink control channel is performed using upper-layer signaling and / or downlink control information (DCI). Here, the upper-layer signaling can be at least one of the following: RRC (Radio Resource Control) signaling, system information (e.g., at least one of RMSI: Remaining Minimum System Information, OSI: Other System Information, MIB: Master Information Block, SIB: System Information Block), or broadcast information (PBCH: Physical Broadcast Channel).

[0018] Furthermore, in NR, the number of symbols assigned to PUCCH (which may also be called PUCCH-assigned symbols, PUCCH symbols, etc.) can be determined by slot-specific, cell-specific, user terminal-specific, or a combination thereof. Since increasing the number of PUCCH symbols is expected to increase the communication distance (coverage), it is conceivable that the number of symbols will be increased for user terminals that are farther from the base station (e.g., eNB, gNB).

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

[0020] Furthermore, in environments with extremely high density and high traffic, such as geographically densely populated areas (e.g., stadiums), it is conceivable that multiple UEs may simultaneously receive the same signal / channel. In such cases, if multiple UEs are located in the same area and each UE receives the same signal / channel, each UE receiving the signal / channel via unicast may ensure communication reliability, but it is thought to reduce resource utilization efficiency.

[0021] A group scheduling mechanism is being considered to ensure that multicast / broadcast service (MBS) is received by multiple UEs.

[0022] For example, scheduling multicast PDSCH using one or more DCIs is being considered. In this case, the size of the DCI (payload size, overhead) may increase.

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

[0024] It is being considered that PTP transmission uses a UE-specific PDCCH to schedule a UE-specific PDSCH for multiple RRC-connected UEs (RRC_CONNECTED UEs), that 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 that the UE-specific PDSCH is scrambled using the same UE-specific RNTI.

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

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

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

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

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

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

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

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

[0033] HARQ-ACK resources for multicast PDSCH may overlap among multiple UEs. As shown in the example in Figure 3A, ACK resources may not overlap among multiple UEs, but NACK resources may overlap. As shown in the example in Figure 3B, if the base station does not receive a signal with the NACK resource (received power is below the threshold), it may determine that there is no UE that sent the NACK and not retransmit the PDSCH. As shown in the example in Figure 3C, if the base station receives a signal with the NACK resource (received power exceeds the threshold), it may determine that there is a UE that sent the NACK and retransmit the PDSCH.

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

[0035] [Option 2A] Common frequency resources are defined as MBS-specific BWPs. MBS-specific BWPs are associated with individual unicast BWPs and use the same neurology (subcarrier spacing (SCS) and cyclic prefix (CP)).

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

[0037] [Option 2B] A common frequency resource is defined as an MBS frequency region (region) with several consecutive PRBs. The MBS frequency region is set up within an individual unicast BWP.

[0038] As shown in the example in Figure 4B, multicast PDSCH resources may be included in the BWP for unicast.

[0039] For RRC-connected UEs receiving multicast, when group-common PDCCH scheduling is supported, the PUCCH resource configuration for HARQ-ACK feedback based on ACK / NACK may be selected from the following three options from the perspective of each UE. [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 setting is either option 1 or 2, depending on the configuration.

[0040] However, it is unclear how to determine the resources for multicast HARQ-ACK feedback. If these resources are unclear, it could lead to a decrease in throughput.

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

[0042] When PTM transmission method 1 is used and a UE receives a DCI that schedules a PDSCH, if that DCI is a group-common DCI with 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 with a CRC scrambled by a group-common RNTI, the UE can determine that the PDSCH is a unicast PDSCH.

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

[0044] However, the monitoring / reception methods for DCIs scheduling multicast PDSCHs and DCIs scheduling unicast PDSCHs are unclear. Lack of clear monitoring / reception methods could lead to decreased throughput, increased power consumption, and other problems.

[0045] Therefore, the inventors conceived of a DCI monitoring / receiving method for scheduling multicast PDSCH / unicast PDSCH.

[0046] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0047] In this disclosure, “A / B / C” and “at least one of A, B, and C” may be interpreted as mutually exclusive. In this disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be interpreted as mutually exclusive. In this disclosure, index, ID, indicator, and resource ID may be interpreted as mutually exclusive. In this disclosure, support, control, controllable, operate, and operable may be interpreted as mutually exclusive.

[0048] In this disclosure, configure, activate, update, indicate, enable, specify, and select may be interpreted as interchangeable.

[0049] In this disclosure, link, associate, correspond, and map may be interpreted as mutually exclusive. In this disclosure, allocate, assign, monitor, and map may be interpreted as mutually exclusive.

[0050] In this disclosure, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof. In this disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher-layer parameters, RRC information elements (IE), and RRC messages may be interpreted as one another.

[0051] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (PDUs). Broadcast information may also include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), or Other System Information (OSIs).

[0052] In this disclosure, MAC CE and activation / deactivation commands may be interpreted as interchangeable.

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

[0054] In this disclosure, multicast, groupcast, broadcast, and MBS may be interpreted interchangeably. In this disclosure, multicast PDSCH and PDSCH scrambled by a group common RNTI may be interpreted interchangeably.

[0055] In this disclosure, HARQ-ACK, HARQ-ACK information, HARQ, ACK / NACK, ACK, and NACK may be interpreted as mutually exclusive.

[0056] In this disclosure, the terms specific, dedicated, UE specific, and UE specific may be interpreted as interchangeable.

[0057] In this disclosure, common, shared, group-common, UE common, and UE shared may be interpreted as mutually exclusive.

[0058] In this disclosure, UE-specific DCI and DCI having CEC scrambled by UE-specific RNTI may be interpreted as mutually exclusive. UE-specific RNTI may be, for example, C-RNTI.

[0059] In this disclosure, UE Common DCI and DCI having CEC scrambled by UE Common RNTI may be interpreted as mutually exclusive. UE Common RNTI may be, for example, multicast-RNTI.

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

[0061] A PUCCH resource for transmitting UCI containing a multicast PDSCH HARQ-ACK may be configured for each common frequency resource by upper-layer signaling, or, as in Rel.16, it may be configured within the UL BWP PUCCH configuration (PUCCH-Config). If this PUCCH resource is configured within PUCCH-Config, it may be a Rel.15 / 16 PUCCH resource or a newly defined PUCCH resource for multicast PDSCH HARQ-ACK.

[0062] Either PTM transmission method 1 or 2 may be specified in the specification. Both PTM transmission methods 1 and 2 may be specified in the specification, and one of them may be configured by upper-layer signaling. If both PTM transmission methods 1 and 2 are specified in the specification, and the DCI that schedules the group common PDSCH (multicast PDSCH) is a group common DCI having a CRC scrambled by the group common RNTI, the UE may determine that PTM transmission method 1 is used. If the DCI is a UE-specific DCI having a CRC scrambled by the UE-specific RNTI, the UE may determine that PTM transmission method 2 is used.

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

[0064] The UE may receive the configuration of a PUCCH resource for sending HARQ-ACK information to the PDSCH and control the sending of HARQ-ACK information using that PUCCH resource.

[0065] The UE may receive a DCI scheduling a 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> A UE that has scheduled a multicast PDSCH by a UE-specific DCI may follow at least one of the following embodiments 1-1 to 1-6.

[0067] 《Aspect 1-1》 A UE that has scheduled a multicast PDSCH via its own DCI sends the multicast PDSCH HARQ-ACK using its own PUCCH resource.

[0068] The UE-specific PUCCH resource may conform to either resource A or B below.

[0069] [Resource A] The UE uses a PUCCH resource configured by upper-layer signaling to send a UCI containing the HARQ-ACK for multicast PDSCH. DCI does not necessarily need to be used to determine this PUCCH resource. In this case, the PUCCH resource indicator (PRI) field can be omitted from the DCI that schedules multicast PDSCH, reducing DCI overhead. By configuring resources through individual UE upper-layer signaling, orthogonal resources can be allocated between UEs.

[0070] [Resource B] Multiple PUCCH resources are configured by upper-layer signaling, and the UE selects (determines) from among the multiple PUCCH resources to send a UCI containing the multicast PDSCH's HARQ-ACK, based on the multicast PDSCH's scheduling DCI. In the example in Figure 1, the UE selects (determines) one set of PUCCH resources (from multiple PUCCH resource sets configured by upper-layer signaling) based on the number of bits (size) of the UCI containing the multicast PDSCH's HARQ-ACK, and then selects (determines) one PUCCH resource from the selected set of PUCCH resources based on the PRI field in the DCI that schedules the multicast PDSCH and the index of the first CCE of the PDCCH that detected the DCI that schedules the multicast PDSCH.

[0071] 《Aspect 1-2》 UEs that have scheduled a multicast PDSCH via a UE-specific DCI send the multicast PDSCH HARQ-ACK using the UE-common PUCCH resource.

[0072] The UE common PUCCH resource may conform to either resource A or B below.

[0073] [Resource A] The UE uses a UE common PUCCH resource configured by upper-layer signaling as the PUCCH resource for transmitting UCI containing the multicast PDSCH HARQ-ACK. In this case, the PUCCH resource used for transmission can be dynamically specified from among multiple UE common PUCCH resources. The PUCCH resource for transmitting the multicast PDSCH HARQ-ACK may also 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 common PUCCH resource based on upper-layer signaling and the DCI. In the example in Figure 2, multiple PUCCH resources for sending HARQ-ACKs for multicast PDSCHs 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 that schedules the multicast PDSCH and the index of the first CCE of the PDCCH that detected the DCI that schedules the multicast PDSCH. The configuration of multiple PUCCH resources for sending HARQ-ACKs for multicast PDSCHs may also be done using a mechanism for determining the PUCCH resource set. For example, the UE may select (determine) a PUCCH resource / PUCCH resource set according to the number of bits (size) of the UCI containing the multicast PDSCH's HARQ-ACK.

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

[0076] Whether the UE uses ACK / NACK feedback or NACK-only feedback for HARQ-ACK transmission of multicast PDSCH may depend on either option 1 or 2 below.

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

[0078] [Option 2] Whether the UE uses ACK / NACK feedback or NACK-only feedback for HARQ-ACK transmission of multicast PDSCH may be determined by the number of bits in the UCI. In the example in Figure 5, if multiple PUCCH resource sets are configured and the number of UCI bits is N0 or less, NACK-only feedback is used. If the number of UCI bits is greater than N0, ACK / NACK feedback (first PUCCH resource set, PUCCH resource set ID=0) is used. If the number of UCI bits is greater than N0 and less than or equal to N1, ACK / NACK feedback (second PUCCH resource set, PUCCH resource set ID=1) is used. If the number of UCI bits is greater than N1, ACK / NACK feedback (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 specified in the specification. NACK-only feedback may use PUCCH format 0.

[0079] 《Aspects 1-4》 One or more PUCCH resource sets for multicast PDSCH HARQ-ACK transmission are configured (by upper-layer signaling), and the UE selects (determines) which PUCCH resource set to use for transmitting the UCI, depending on the number of bits (size) of the UCI containing the HARQ-ACK.

[0080] Whether a UE uses a UE-specific PUCCH or a UE-common PUCCH for sending a multicast PDSCH HARQ-ACK may depend on either option 1 or 2 below.

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

[0082] [Option 2] Whether a UE uses a UE-specific PUCCH or a UE-common PUCCH for multicast PDSCH HARQ-ACK transmission may be determined by the number of bits in the UCI. In the example in Figure 6, if multiple PUCCH resource sets are configured and the number of UCI bits is N0 or less, a UE-common PUCCH is used. If the number of UCI bits is greater than N0, a UE-specific PUCCH (first PUCCH resource set, PUCCH resource set ID=0) is used. If the number of UCI bits is greater than N0 and less than or equal to N1, a UE-specific PUCCH (second PUCCH resource set, PUCCH resource set ID=1) is used. If the number of UCI bits is greater than N1, a UE-specific PUCCH (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 specified in the specification. The UE-common PUCCH may use PUCCH format 0.

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

[0084] The condition may be at least one of the following conditions: DCI Format / DCI Fields • PDCCH Monitoring Occasion / CORESET / Searchspace • Scramble CRC RNTI MAC CE

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

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

[0087] 《Aspects 1-6》 The configuration of PUCCH resources / resource sets using upper-layer signaling may follow either of the following configuration methods 1 or 2.

[0088] [Setup Method 1] UE-specific PUCCH resources / resource sets and UE-common PUCCH resources / resource sets are configured separately. In the example in Figure 7, UE-specific PUCCH resources / resource sets and UE-common PUCCH resources / resource sets are configured. The UE-specific PUCCH resources / resource sets may also be the PUCCH resources / resource sets for unicast PDSCH in Rel.15 / 16. Separately from the PUCCH resources / resource sets for unicast PDSCH, a PUCCH resource / resource set for multicast PDSCH may also be configured.

[0089] [Setup Method 2] UE-specific PUCCH resources / resource sets and UE-common PUCCH resources / resource sets are configured in common.

[0090] For each resource, a UE-specific PUCCH resource and a UE-common PUCCH resource may be configured separately. For a unicast PDSCH HARQ-ACK, the UE-specific PUCCH resource may be indicated by DCI (PRI field / index of the first CCE). For a multicast PDSCH HARQ-ACK, the UE-common PUCCH resource may be indicated by DCI (PRI field / index of the first CCE). In the example in Figure 8, multiple PUCCH resource sets are configured, and some of these PUCCH resource sets include a UE-specific PUCCH resource / UE-common PUCCH resource. A PUCCH resource set with a UCI bit count of N0 or less may include a UE-common PUCCH resource, while a PUCCH resource set with a UCI bit count greater than N0 or N1 may not include a UE-common PUCCH resource. Each PUCCH resource / resource set may also be a PUCCH resource / resource set for unicast PDSCH according to Rel.15 / 16. In addition to the PUCCH resource / resource set for unicast PDSCH, a separate PUCCH resource / resource set for multicast PDSCH may also be configured.

[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 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 a sequence based on a base sequence and a CS based on ACK or NACK over the PUCCH.

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

[0093] <Second Embodiment> A UE that has scheduled a multicast PDSCH by the UE Common DCI may follow at least one of the following embodiments 2-1 and 2-2.

[0094] 《Aspect 2-1》 UEs that have scheduled a multicast PDSCH via the UE Common DCI send the multicast PDSCH HARQ-ACK using the UE-specific PUCCH resource.

[0095] The UE-specific PUCCH resource may conform to either resource A or B below.

[0096] [Resource A] The UE uses a PUCCH resource configured by upper-layer signaling to send a UCI containing the HARQ-ACK for multicast PDSCH. DCI does not necessarily need to be used to determine this PUCCH resource. In this case, the PUCCH resource indicator (PRI) field can be omitted from the DCI that schedules multicast PDSCH, reducing DCI overhead. By configuring resources through individual UE upper-layer signaling, orthogonal resources can be allocated between UEs.

[0097] [Resource B] Multiple PUCCH resources are configured by upper-layer signaling, and the UE selects (determines) from among the multiple PUCCH resources to send a UCI containing the multicast PDSCH's HARQ-ACK, based on the multicast PDSCH's scheduling DCI. In the example in Figure 1, the UE selects (determines) one set of PUCCH resources (from multiple PUCCH resource sets configured by upper-layer signaling) based on the number of bits (size) of the UCI containing the multicast PDSCH's HARQ-ACK, and then selects (determines) one PUCCH resource from the selected set of PUCCH resources based on the PRI field in the DCI that schedules the multicast PDSCH and the index of the first CCE of the PDCCH that detected the DCI that schedules the multicast PDSCH.

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

[0099] [PRI Field 1] In the example in Figure 9A, the PRI field is expanded to specify a PRI (PRI0 to 3) for each UE (UE0 to 3) (UE-specific). UEs have their own PRI field set by upper-layer signaling and determine the PUCCH resource based on the set PRI field. UEs may ignore PRI fields that are not set (for other UEs).

[0100] [PRI Field 2] The PRI field is not expanded. 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 in Figure 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 PRI (PUCCH resource).

[0101] One UE can know the PUCCH resources of other UEs and may control channel conflicts based on the PUCCH resources of other UEs.

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

[0103] 《Appearance 2-2》 UEs that have scheduled a multicast PDSCH via UE Common DCI send the multicast PDSCH HARQ-ACK using the UE Common PUCCH resource.

[0104] The UE common PUCCH resource may conform to either resource A or B below.

[0105] [Resource A] The UE uses a PUCCH resource configured by upper-layer signaling to send a UCI containing the HARQ-ACK for multicast PDSCH. DCI does not necessarily need to be used to determine this PUCCH resource. In this case, the PUCCH resource indicator (PRI) field can be omitted from the DCI that schedules multicast PDSCH, reducing DCI overhead. By configuring resources through individual UE upper-layer signaling, orthogonal resources can be allocated between UEs.

[0106] [Resource B] Multiple PUCCH resources are configured by upper-layer signaling, and the UE selects (determines) from among the multiple PUCCH resources to send a UCI containing the multicast PDSCH's HARQ-ACK, based on the multicast PDSCH's scheduling DCI. In the example in Figure 2, the UE selects (determines) one set of PUCCH resources (from the multiple PUCCH resource sets configured by upper-layer signaling) based on the number of bits (size) of the UCI containing the multicast PDSCH's HARQ-ACK, and then selects (determines) one PUCCH resource from the selected set of PUCCH resources based on the PRI field in the DCI that schedules the multicast PDSCH and the index of the first CCE of the PDCCH that detected the DCI that schedules the multicast PDSCH.

[0107] According to this embodiment, when a multicast PDSCH is scheduled by the UE Common DCI, the UE can appropriately send HARQ-ACK information to that PDSCH.

[0108] <Third Embodiment> When the UE receives a unicast PDSCH and a multicast PDSCH, the UE may respond to the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH in either of the following embodiments 3-1 and 3-2.

[0109] 《Aspect 3-1》 The UE multiplexes (maps to a single channel) the HARQ-ACK from a unicast PDSCH and the HARQ-ACK from a multicast PDSCH on a single channel. The channel can be a PUCCH or a PUSCH.

[0110] The UE may generate HARQ-ACK bit sequences for unicast and multicast PDSCHs according to the HARQ-ACK counting method for PDSCHs for existing semi-static / dynamic HARQ-ACK codebooks (HARQ codebooks), and transmit the generated HARQ-ACK bit sequences on a single channel resource. In this case, the UE only needs to transmit on one channel, thus improving resource utilization efficiency. The total DAI / counter DAI may be aggregated (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 a unicast PDSCH and the HARQ-ACK of a multicast PDSCH are mapped may conform to either resource A or B below.

[0112] [Resource A] The UE sends HARQ-ACKs for both unicast and multicast PDSCH channels using the PUCCH / PUSCH resource for unicast PDSCH. Because this channel resource is UE-specific, it is easier to control.

[0113] The UE may multiplex the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH, and select (determine) the PUCCH resource set according to the number of UCI bits including the multiplexed HARQ-ACK. The UE may also select (determine) the 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 onto the HARQ-ACK of the unicast PDSCH).

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

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

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

[0117] [Resource B] The UE sends HARQ-ACKs for both unicast and multicast PDSCH channels in the PUCCH / PUSCH resource for multicast PDSCH. Because this channel resource is a separate resource, it is easy to control.

[0118] The UE may multiplex the HARQ-ACK of the unicast PDSCH and the HARQ-ACK of the multicast PDSCH, and select (determine) the PUCCH resource set according to the number of UCI bits including the multiplexed HARQ-ACK. The UE may also select (determine) the 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 selecting a PUCCH resource according to existing time / frequency DCI selection rules. Here, the UE does not need to distinguish between the scheduling DCI for unicast PDSCHs and the scheduling DCI for multicast PDSCHs.

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

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

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

[0123] When mapping (multiplexing) a unicast PDSCH HARQ-ACK and a multicast PDSCH HARQ-ACK to a single channel, the bits of the HARQ-ACK may be ordered according to at least one of the following: the type indicating the unicast or multicast PDSCH (the PDSCH cast type), the PDSCH slot index, and the PDSCH cell index. When the HARQ-ACK is ordered by the PDSCH cast type, the order may be unicast PDSCH HARQ-ACK followed by multicast PDSCH HARQ-ACK, or multicast PDSCH HARQ-ACK followed by unicast PDSCH HARQ-ACK. For each slot of the PDSCH, the bits of the HARQ-ACK may be ordered according to at least one of the PDSCH cast type and the PDSCH cell index.

[0124] 《Aspect 3-2》 The UE does not multiplex the HARQ-ACK of a unicast PDSCH and the HARQ-ACK of a multicast PDSCH on the same channel (they map them to different channels). 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 these HARQ-ACK bit sequences on separate channel resources. The UE may generate the HARQ-ACK bits for the multicast PDSCH according to the PDSCH HARQ-ACK counting method for existing semistatic / dynamic HARQ-ACK codebooks. In this case, the multicast PDSCH HARQ-ACK transmission does not affect the unicast PDSCH HARQ-ACK transmission. The total DAI / counter DAI may be calculated separately for the scheduling DCI of the unicast PDSCH and the scheduling DCI of the multicast PDSCH.

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

[0127] Within a given slot (or subslot), a UE may send only one of the following: a PUCCH carrying a HARQ-ACK for a unicast PDSCH, or a PUCCH carrying a HARQ-ACK for a multicast PDSCH. Within a given slot (or subslot), a UE instructed (by the PDSCH-to-HARQ feedback indicator field) to provide feedback for both unicast and multicast PDSCHs may drop either feedback. It may be specified that a UE does not expect to be instructed to provide feedback for both unicast and multicast PDSCHs within a given slot (or subslot).

[0128] The UE reports in its capability information that it supports the simultaneous / multiplexing / on one channel transmission of both multicast PDSCH HARQ-ACKs and unicast PDSCH HARQ-ACKs, and if simultaneous transmission of multicast PDSCH HARQ-ACKs and unicast PDSCH HARQ-ACKs occurs (occasions overlap), the UE may transmit both multicast PDSCH HARQ-ACKs and unicast PDSCH HARQ-ACKs. In this case, the UE may transmit multicast PDSCH HARQ-ACKs and unicast PDSCH HARQ-ACKs using time division multiplexing (TDM), or using embodiment 3-1.

[0129] The UE may distinguish / identify DCIs for multicast PDSCHs from DCIs for unicast PDSCHs (according to at least one of the fifth to ninth embodiments).

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

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

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

[0133] <Fifth Embodiment> In PTM transmission method 2, the UE determines whether a PDSCH 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] Dedicated resources for multicast PDSCHs and dedicated resources for unicast PDSCHs may be configured by upper-layer signaling. Whether a PDSCH is a unicast PDSCH or a multicast PDSCH may be determined by whether the scheduled PDSCH's resources correspond to dedicated resources for multicast PDSCHs or dedicated resources for unicast PDSCHs. Resources may be in the time domain, frequency domain, code domain (sequence / cyclic shift), or spatial domain. Frequency domain resources may be physical resource elements (PRE), physical resource blocks (PRB), BWP, or CC.

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

[0136] A unicast resource and a multicast resource may be contained within (enclosed by) the other. For example, a portion of a unicast resource may be cut out (a hole made) and that portion may be a multicast resource.

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

[0138] <Sixth Embodiment> In PTM transmission method 2, the UE determines whether a 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 a scheduled PDSCH is a unicast PDSCH or a multicast PDSCH based on at least one of the following embodiments 6-1 to 6-4.

[0140] 《Aspect 6-1》 A dedicated CORESET / search space (multicast-only CORESET / search space) is configured for the UE-specific DCI that schedules multicast PDSCH.

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

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

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

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

[0145] The DCI that schedules 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 that schedules multicast PDSCH may also be a new DCI format for multicast PDSCH. If a new DCI format is specified, the UE may only attempt blind detection if configured by upper-layer signaling.

[0146] By using a multicast-dedicated CORESET / search space, the resources used to monitor DCI can be limited, thereby reducing UE power consumption.

[0147] 《Appearance 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 only exist within an existing DCI format if its use is configured by higher-layer signaling.

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

[0149] 《Appearance 6-3》 A new RNTI specific to the UE may be defined. If the UE detects a DCI with a CRC scrambled by the new RNTI, it may determine that the DCI will schedule a multicast PDSCH. The UE may only attempt to detect a DCI with a CRC scrambled by the new RNTI if the multicast PDSCH scheduling (new RNTI) is configured by upper-layer signaling.

[0150] 《Appearance 6-4》 If certain special values ​​of certain special fields in an existing DCI format are decoded, the UE may consider (determine, confirm, validate) that the DCI is scheduling a multicast PDSCH. Otherwise, the UE may consider that the DCI is scheduling a unicast PDSCH. The existing DCI format may be at least one of the DCI formats 0_1, 0_2, 1_1, 1_2, and 2_3. The combination of special fields and special values ​​may be at least one of the following: • The values ​​in the frequency domain resource allocation field are set to all 0s or all 1s. • The values ​​in the Time Domain Resource Allocation field are set to either all 0s or all 1s. The values ​​in the frequency hopping flag field are set to either all 0s or all 1s. The value of the Modulation and Coding Scheme (MCS) field is set to either all 0s or all 1s. • The values ​​of the New Data Indicator (NDI) field are set to either all 0 or all 1. • The value of the redundancy version field is set to either all 0s or all 1s. • The value of the HARQ process number field is set to either all 0s or all 1s. • The values ​​in the Downlink Assignment Indicator (DAI) field are set to either all 0s or all 1s. The values ​​in the PUCCH Transmit Power Control (TPC) command field are set to either all 0 or all 1. The values ​​in the Transmit Power Control (TPC) command field for PUSCH are set to either all 0 or all 1. • The values ​​in the SRS resource indicator field are set to either all 0s or all 1s. The values ​​in the precoding information and layer count fields are set to either all 0 or all 1. The values ​​of the antenna port field are set to either all 0 or all 1. • The values ​​in the CSI request field are set to either all 0s or all 1s.

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

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

[0153] After the UE determines that the received DCI schedules a multicast PDSCH, it may use the values ​​of each instruction field within that DCI to obtain resource allocation information for the multicast PDSCH. Resource allocation information for unicast PDSCHs and resource allocation information for multicast PDSCHs may be set by upper-layer signaling. If resource allocation information for multicast PDSCHs is not set (provided), the UE may use the resource allocation information for unicast PDSCHs for multicast PDSCHs. 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 in Figure 13, if the UE determines that the UE-specific DCI will schedule a multicast PDSCH, it may determine the resources for the multicast PDSCH based on the configured multicast resource allocation information and the DCI. If the UE determines that the UE-specific DCI will schedule a unicast PDSCH, it may determine the resources for the unicast PDSCH based on the configured unicast resource allocation information and the DCI. One value in the field indicating resource allocation within the DCI may indicate different resources depending on whether the DCI is scheduling a multicast PDSCH or a unicast PDSCH.

[0155] Resources for multicast PDSCH may be called common frequency resources, or they may be resources that are commonly recognized among multiple UEs. The resource allocation method for multicast PDSCH may be to select / instruct resources from among the common frequency resources, rather than the existing resource allocation method of selecting / instructing resources from within the BWP.

[0156] In this case, compared to the fifth embodiment, the PDSCH is limited to multicast resources, allowing for flexible specification of PDSCH resources using a limited number of bits in the scheduling DCI (e.g., the FDMA field).

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

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

[0159] For example, the embodiment 6-1 may be applied to PTM transmission method 1, and the DCI for PTM transmission method 1 may be restricted to being detected in a multicast-only CORESET / search space. In this case, the UE can reduce the amount of processing required for blind detection / CRC checks of the DCI for PTM transmission method 1, and thus reduce the UE's power consumption.

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

[0161] In PTM transmission schemes 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-only 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-only CORESET / search space. By limiting blind detection of the new DCI format to the multicast-only CORESET / search space, UE power consumption can be reduced.

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

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

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

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

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

[0167] If the UE successfully receives / decodes the PDSCH (Unicast PDSCH / Multicast PDSCH), the UE may follow at least one of the following steps 1 through 3.

[0168] [Step 1] If the PDSCH is notified by upper-layer signaling to be a unicast PDSCH, and the UE successfully receives / decodes the PDSCH, the UE may send an ACK.

[0169] [Step 2] If the PDSCH is notified by upper-layer signaling to be a multicast PDSCH, and ACK / NACK feedback is set / instructed, and the UE successfully receives / decodes the PDSCH, the UE may send an ACK.

[0170] [Step 3] If the PDSCH is notified by upper-layer signaling that it is a multicast PDSCH, and NACK-only feedback is set / instructed, and the UE successfully receives / decodes the PDSCH, the UE does not need to send a HARQ-ACK.

[0171] The PUCCH resources used for sending ACKs may differ between unicast PDSCHs and multicast PDSCHs.

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

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

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

[0175] [UE operation] The UE may decode the TB in the scheduled PDSCH, read the higher-layer signaling contained in the TB (e.g., MAC subheader), and determine whether the TB is unicast or multicast. Depending on the result of this determination, the UE may perform HARQ-ACK feedback control. HARQ-ACK feedback control may include at least one of the following: creating a HARQ-ACK information bit sequence, determining a PUCCH resource, and sending a PUCCH.

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

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

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

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

[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 from the higher-layer signaling included in the TB (e.g., the MAC subheader). In this case, it may be specified that the UE is not notified whether the PDSCH is multicast or unicast from the higher-layer signaling included in the TB (e.g., the MAC subheader). This can reduce control overhead.

[0181] The UE may determine the data scrambling RNTI by blind decoding of the PDSCH, determine whether the PDSCH is multicast or unicast using higher-layer signaling included in the TB (e.g., MAC subheader), and verify whether the determined data scrambling RNTI is correct. In this case, 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> If a multicast PDSCH is configured by upper-layer signaling, the UE may determine (assume) that a DL assignment DCI with a CRC scrambled by C-RNTI will schedule the multicast PDSCH (the UE may specify that it does not assume that a unicast PDSCH will be scheduled). If a multicast PDSCH is configured by upper-layer signaling, the UE may determine (assume) that a specific DCI format will schedule 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] <Tenth Embodiment> A UE capability may be defined corresponding to at least one function (feature) in the first to ninth embodiments. If the UE reports this UE capability, the UE may perform the corresponding function. If the UE reports this UE capability and a higher-layer parameter corresponding to this function is set, the UE may perform the corresponding function. A higher-layer parameter (RRC information element) corresponding to this function may be defined. If this higher-layer parameter is set, the UE may perform the corresponding function.

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

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

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

[0189] UE capability may indicate whether or not it supports multicast-only CORESET / search spaces. UE capability may also indicate the maximum number (number supported) of multicast-only CORESET / search spaces.

[0190] UE capability may also indicate how HARQ-ACKs are sent to multicast PDSCHs (ACK / NACK feedback or NACK-only feedback).

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

[0192] UE capability may indicate whether it supports the transmission of both multicast PDSCH HARQ-ACKs and unicast PDSCH HARQ-ACKs (simultaneously / multiplexed / within a single channel).

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

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

[0195] Figure 16 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

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

[0197] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

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

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

[0200] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

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

[0203] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0204] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0205] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0206] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0207] The wireless access method may also be called a waveform. In 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, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, shared by each user terminal 20.

[0209] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0210] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0212] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0213] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0214] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0215] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0216] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

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

[0218] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0219] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0220] (base station) Figure 17 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

[0221] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each part 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, control circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0224] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0225] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0226] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0227] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0228] The transmitting / receiving unit 120 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

[0230] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

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

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

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

[0234] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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 send 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] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

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

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

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

[0240] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0241] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0243] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0244] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0245] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0246] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0247] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0248] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.

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

[0250] Note that whether to apply the DFT process may also be based on the settings of transform precoding. For a certain channel (e.g., PUSCH), when transform precoding is enabled in the transceiver unit 220 (transmission processing unit 2211), the DFT process may be performed as the above-mentioned transmission processing to transmit the channel using the DFT-s-OFDM waveform; otherwise, the DFT process may not be performed as the above-mentioned transmission processing.

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

[0255] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0256] The transmitting / receiving unit 220 may receive the configuration of a physical uplink control channel (PUCCH) resource for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information to a multicast physical downlink shared channel (PDSCH). The control unit 110 may control the transmission of the HARQ-ACK information using the PUCCH resource (in the 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 aforementioned settings may be either terminal-specific settings or terminal-common settings (first and second embodiments).

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

[0260] The transmitting / receiving 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 (5th to 10th embodiments).

[0261] The downlink control information may also be terminal-specific downlink control information (5th and 6th embodiments).

[0262] The transmitting / receiving unit 220 may receive the multicast PDSCH settings. If the resources indicated by the downlink control information are included in the settings, the control unit 210 may determine that the PDSCH is multicast (Fifth Embodiment).

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

[0264] (Hardware configuration) The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0265] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0267] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0268] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

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

[0270] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0271] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0272] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.

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

[0274] Communication device 1004 is hardware (a transceiver 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 be configured to 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 duplex (FDD) and time division duplex (TDD). For example, the above-described transceiver unit 120 (220), transceiver antenna 130 (230), etc. may be implemented by communication device 1004. The transceiver 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 (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) for receiving an external input. Output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) for performing an output to the external. Note that input device 1005 and output device 1006 may have an integrated configuration (e.g., a touch panel).

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

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

[0278] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

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

[0280] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

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

[0282] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

[0283] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0284] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0285] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0286] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0287] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

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

[0289] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0291] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0292] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

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

[0294] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0295] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0296] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0297] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

[0299] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0301] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

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

[0303] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0304] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0305] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

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

[0307] Software should be broadly interpreted 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, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

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

[0309] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0310] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "quasi-co-location (QCL)," "transmission configuration indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

[0311] In this disclosure, terms such as "Base Station (BS)", "wireless 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", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0312] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

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

[0314] A mobile station may also be called 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 appropriate term.

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

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

[0317] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

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

[0319] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0320] Each aspect / embodiment described in this disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may be applied to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that extend these. It may also be applied in combination with multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0321] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0322] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may 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 actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0324] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0325] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0326] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

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

[0328] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0329] In this 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, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0330] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0331] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0332] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0333] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. A receiving unit that receives upper-layer signaling indicating a search space and receives downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) within the search space, The system includes 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 aforementioned search space is set. The receiving unit uses the sequence corresponding to the ID for the DCI, The control unit is a terminal that, when time domain resource assignment (TDRA) information for unicast and TDRA information for multicast are set, determines that the PDSCH is multicast, and determines the time resources of the PDSCH based on the multicast TDRA information.

2. The steps include receiving upper-layer signaling indicating a search space and receiving downlink control information (DCI) that schedules a physical downlink sharing channel (PDSCH) within the search space, A step of determining whether the PDSCH is multicast or unicast based on the search space and the DCI, When time domain resource assignment (TDRA) information for unicast and TDRA information for multicast are set, and it is determined that the PDSCH is multicast, the process includes the step of determining the time resources of the PDSCH based on the multicast TDRA information. An ID corresponding to the aforementioned search space is set. A wireless communication method for a terminal, wherein a series corresponding to the ID is used for the DCI.

3. A transmitting unit that transmits upper-layer signaling indicating a search space for multicast, and upper-layer signaling indicating a search space for unicast, It includes a control unit that determines the transmission of either a multicast physical downlink shared channel (PDSCH) or a unicast PDSCH, The control unit controls the transmission of downlink control information (DCI) for scheduling the PDSCH within the search space corresponding to the PDSCH. An ID corresponding to the aforementioned search space is set. For the DCI, the series corresponding to the ID is used. The control unit, when setting time domain resource assignment (TDRA) information for unicast and TDRA information for multicast, instructs the time resources of the PDSCH based on the multicast TDRA information when the PDSCH is multicast, is a base station.

4. A system including terminals and base stations, The aforementioned terminal is A receiving unit that receives upper-layer signaling indicating a search space and receives downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) within the search space, The system includes 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 aforementioned search space is set. The receiving unit uses the sequence corresponding to the ID for the DCI, When time domain resource assignment (TDRA) information for unicast and TDRA information for multicast are set, and the control unit determines that the PDSCH is multicast, it determines the time resources of the PDSCH based on the multicast TDRA information. The aforementioned base station is A transmission unit that transmits the aforementioned upper layer signaling, It has a control unit that determines the transmission of the PDSCH, The control unit of the base station is a system for controlling the transmission of the DCI.

Images