Terminal, radio communication method, and base station

Abstract

To provide a terminal, a radio communication method, and a base station that appropriately determine a PUCCH resource, even when a plurality of DCIs correspond to the same serving cell / the same PDCCH monitoring opportunity.SOLUTION: A terminal has: a receiving section that receives downlink control information including information related to the transmission timing of an uplink control channel; and a control section that, when a plurality of pieces of downlink control information indicating the same time domain are received as the transmission timing of the uplink control channel, determines an uplink control channel resource on the basis of downlink control information with the last index, of the plurality of pieces of downlink control information. When the plurality of pieces of downlink control information correspond to the same downlink control channel monitoring opportunity of the same serving cell, the index of each downlink control information is determined on the basis of one or more parameters corresponding to each downlink control information.SELECTED DRAWING: Figure 5

Description

[Technical Field]

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

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

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

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

[0005] In existing wireless communication systems (e.g., Rel. 15 NR), a terminal (user terminal, User Equipment (UE)) is supported to feed back uplink control information (e.g., HARQ-ACK) using an uplink control channel (e.g., PUCCH). Also, a UE is supported to determine resources (e.g., PUCCH resources) to be used for PUCCH based on information related to an uplink control channel resource indication included in downlink control information (e.g., DCI).

[0006] When multiple DCIs indicate HARQ-ACK feedback in a certain time domain (e.g., slot / symbol), the UE determines the PUCCH resource based on a specific DCI (e.g., the last DCI) among the multiple DCIs, which may be determined based on an index assigned based on the serving cell index / PDCCH monitoring occasion.

[0007] On the other hand, in future wireless communication systems, it is conceivable that multiple DCIs will correspond to the same serving cell / same PDCCH monitoring opportunity. In such cases, how to determine the PUCCH resource becomes an issue.

[0008] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately determine PUCCH resources even when multiple DCIs correspond to the same serving cell / same PDCCH monitoring opportunity. [Means for solving the problem]

[0009] A terminal according to one aspect of the present disclosure has a receiving unit that receives downlink control information including information regarding the transmission timing of an uplink control channel, and a control unit that, when receiving a plurality of downlink control information indicating the same time domain as the transmission timing of the uplink control channel, determines an uplink control channel resource based on the downlink control information with the last index among the plurality of downlink control information, and when a plurality of downlink control information corresponds to the same downlink control channel monitoring opportunity of the same serving cell, the index of each downlink control information is determined based on one or more parameters corresponding to each downlink control information. [Effects of the Invention]

[0010] According to one aspect of the present disclosure, it is possible to appropriately determine PUCCH resources even when multiple DCIs correspond to the same serving cell / same PDCCH monitoring occasion. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of transmission of a HARQ-ACK for a PDSCH. [Figure 2] FIG. 2 is a diagram illustrating an example of configuration of PUCCH resource sets. [Figure 3] FIG. 3 is a diagram illustrating an example of PUCCH resources specified in DCI. [Figure 4] FIG. 4 is a diagram illustrating an example in which multiple DCIs correspond to the same PDCCH monitoring occasion of the same serving cell. [Figure 5] FIG. 5 is a diagram illustrating an example of DCI ordering control when multiple DCIs correspond to the same PDCCH monitoring occasion of the same serving cell. [Figure 6] FIG. 6 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] <Service (traffic type)> In future wireless communication systems (e.g., NR), traffic types (also referred to as types, services, service types, communication types, use cases, etc.) such as further advances in mobile broadband (e.g., enhanced Mobile Broadband (eMBB)), machine-type communications that enable multiple simultaneous connections (e.g., massive Machine Type Communications (mMTC), Internet of Things (IoT)), and highly reliable and low-latency communications (e.g., Ultra-Reliable and Low-Latency Communications (URLLC)) are expected. For example, URLLC requires lower latency and higher reliability than eMBB.

[0013] Traffic types may be identified at the physical layer based on at least one of the following: Logical channels with different priorities Modulation and Coding Scheme (MCS) table (MCS index table) Channel Quality Indication (CQI) table DCI format Used to scramble (mask) the Cyclic Redundancy Check (CRC) bits included (added) in the DCI (DCI format) (RNTI: System Information-Radio Network Temporary Identifier) RRC (Radio Resource Control) parameters A specific RNTI (e.g., RNTI for URLLC, MCS-C-RNTI, etc.) Search Space Predefined fields in the DCI (e.g., newly added fields or reused existing fields)

[0014] Specifically, the traffic type of HARQ-ACK (or PUCCH) for PDSCH may be determined based on at least one of the following: The MCS index table used to determine at least one of the modulation order, target code rate, and transport block size (TBS) of the PDSCH (for example, whether to use MCS index table 3). The RNTI used for CRC scrambling of the DCI used for scheduling the PDSCH (for example, whether CRC scrambling is performed using C-RNTI or MCS-C-RNTI) Priority set by upper layer signaling

[0015] The traffic type may be associated with communication requirements (requirements such as delay, error rate, etc.), data type (voice, data, etc.), and the like.

[0016] The difference between the requirements of URLLC and eMBB may be that the latency of URLLC is smaller than that of eMBB, or that the requirements of URLLC include a reliability requirement.

[0017] For example, the eMBB user (U) plane delay requirement may include a downlink U-plane delay of 4 ms and an uplink U-plane delay of 4 ms. On the other hand, the URLLC U-plane delay requirement may include a downlink U-plane delay of 0.5 ms and an uplink U-plane delay of 0.5 ms. Furthermore, the URLLC reliability requirement may include a 32-byte error rate of 10 ms for a 1 ms U-plane delay. -5 It may include that:

[0018] Additionally, enhanced Ultra Reliable and Low Latency Communications (eURLLC) is being studied to improve the reliability of traffic, mainly for unicast data. In the following, when there is no need to distinguish between URLLC and eURLLC, they will simply be referred to as URLLC.

[0019] <PUCCHリソース> In existing wireless communication systems (e.g., Rel. 15), the PUCCH resource to be used for transmitting HARQ-ACK for DL ​​transmission (e.g., PDSCH) is determined based on information notified by DCI and higher layer signaling. For example, the UE may determine the PUCCH resource to be used for transmitting HARQ-ACK using the following steps 1 to 3. Note that the order of steps 1 to 3 may be reversed.

[0020] [Step 1] In step 1, the UE or terminal (hereinafter also simply referred to as UE) determines the HARQ-ACK feedback timing (K1). K1 corresponds to the period (e.g., slot) from the reception of DL transmission (e.g., PDSCH) to the transmission of HARQ-ACK for that DL transmission. Information regarding the HARQ-ACK timing (K1) may be included in the DCI used for scheduling the PDSCH.

[0021] The network (e.g., a base station) may notify the UE of K1 using a predetermined field of DCI (or PDCCH) that schedules the PDSCH. For example, the bit value specified in the predetermined field of DCI may correspond to a predetermined value (e.g., {1, 2, 3, 4, 5, 6, 7, 8}). Alternatively, the bit value specified in the predetermined field of DCI may correspond to a value set by higher layer signaling.

[0022] When a UE receives DCI scheduling a PDSCH, the UE determines the timing of feeding back a HARQ-ACK for the PDSCH based on information included in the DCI (see Figure 1). In Figure 1, the UE receives a PDSCH scheduled in slot #n based on the DCI transmitted in the same slot. Furthermore, the UE transmits a HARQ-ACK using a PUCCH resource set for slot #n+1 based on information (here, K1=1) about the HARQ-ACK feedback timing included in the DCI.

[0023] [Step 2] In step 2, the UE determines the PUCCH resource set to be used in the slot in which the HARQ-ACK is transmitted.

[0024] One or more PUCCH resource sets are signaled (or configured) to a UE by higher layer signaling. A PUCCH resource set may include one or more PUCCH resources. For example, a base station may signal K (e.g., 1≦K≦4) PUCCH resource sets to a UE. Each PUCCH resource set may include M (e.g., 8≦M≦32, or 1≦M≦8) PUCCH resources.

[0025] The UE may determine a single PUCCH resource set from the configured K PUCCH resource sets based on the payload size of the UCI (UCI payload size), which may be the number of bits of the UCI excluding cyclic redundancy code (CRC) bits.

[0026] Figure 2 is a diagram showing an example of PUCCH resource allocation. In Figure 2, as an example, K=4, and four PUCCH resource sets #0-#3 are configured from the base station to the UE by higher layer signaling. Furthermore, each of the PUCCH resource sets #0-#3 includes M (e.g., 8≦M≦32) PUCCH resources #0-#M-1. Note that the number of PUCCH resources included in each PUCCH resource set may be the same or different.

[0027] In Fig. 2, each PUCCH resource configured in a UE may include a value of at least one of the following parameters (also referred to as a field or information, etc.): Note that a range of values ​​that each parameter can take may be defined for each PUCCH format. Symbol at which PUCCH allocation starts (start symbol) Number of symbols allocated to PUCCH within a slot (period allocated to PUCCH) Index of the resource block (PRB: Physical Resource Block) where PUCCH allocation starts Number of PRBs allocated to PUCCH Whether to enable frequency hopping for PUCCH - Second hop frequency resource and initial cyclic shift (CS) index when frequency hopping is enabled The index of the orthogonal spreading code (e.g., OCC: Orthogonal Cover Code) in the time domain, the length of the OCC used for block spreading before the Discrete Fourier Transform (DFT) (also called the OCC length, spreading factor, etc.) The OCC index used for block-wise spreading after DFT.

[0028] As shown in FIG. 2, when PUCCH resource sets #0 to #3 are configured for a UE, the UE selects one of the PUCCH resource sets based on the UCI payload size.

[0029] For example, if the UCI payload size is 1 or 2 bits, PUCCH resource set #0 is selected. If the UCI payload size is 3 bits or more and N2-1 bits or less, PUCCH resource set #1 is selected. If the UCI payload size is N2 bits or more and N3-1 bits or less, PUCCH resource set #2 is selected. Similarly, if the UCI payload size is N3 bits or more and N3-1 bits or less, PUCCH resource set #3 is selected.

[0030] In this way, the range of UCI payload sizes for which PUCCH resource set #i (i=0,...,K-1) is selected is N i N bits or more i+1 -1 bit or less (i.e., {N i ,…,N i+1 -1 bit).

[0031] Here, the starting positions (number of starting bits) N0 and N1 of the UCI payload size for PUCCH resource sets #0 and #1 may be 1 and 3, respectively. Thus, PUCCH resource set #0 is selected when transmitting UCI of 2 bits or less, and PUCCH resource set #0 may include PUCCH resources #0 to #M-1 for at least one of PF0 and PF1. On the other hand, one of PUCCH resource sets #1 to #3 is selected when transmitting UCI of more than 2 bits, and PUCCH resource sets #1 to #3 may each include PUCCH resources #0 to #M-1 for at least one of PF2, PF3, and PF4.

[0032] For i=2,…,K-1, the start position of the payload size of UCI for PUCCH resource set #i (N i The information indicating the start position (N i ) may be UE specific. For example, the starting position (N i ) may be set to a value in the range of 4 bits to 256 bits (e.g., a multiple of 4). For example, in FIG. 2, information indicating the start positions (N2, N3) of the UCI payload sizes for PUCCH resource sets #2 and #3 is notified to the UE by higher layer signaling (e.g., user-specific RRC signaling).

[0033] The maximum payload size of UCI for each PUCCH resource set is N K is given by -1. K may be explicitly signaled (configured) to the UE by higher layer signaling and / or DCI, or may be implicitly derived. For example, in Figure 2, N0 = 1 and N1 = 3 may be specified in the specification, and N2 and N3 may be signaled by higher layer signaling. Also, N4 may be specified in the specification (e.g., N4 = 1706).

[0034] In this way, the UE selects one PUCCH resource set from one or more PUCCH resource sets configured by higher layers based on the UCI payload size (e.g., HARQ-ACK bits if the UCI is HARQ-ACK).

[0035] [Step 3] In step 3, the UE determines one PUCCH resource from one or more PUCCH resources included in the PUCCH resource set.

[0036] For example, the UE may determine a PUCCH resource to be used for transmitting UCI from the M PUCCH resources included in the determined PUCCH resource set based on at least one of DCI and implicit information (also referred to as implicit indication information or implicit index, etc.).

[0037] In the case shown in Figure 2, the user terminal can determine a single PUCCH resource to use for transmitting UCI based on the value of a specified field in the DCI from among PUCCH resources #0 to #M-1 included in a PUCCH resource set selected based on the UCI payload size.

[0038] The number M of PUCCH resources in one PUCCH resource set may be configured in the user terminal by higher layer signaling (see FIG. 3). FIG. 3 shows a case where eight PUCCH resources are configured by higher layer signaling. Here, a case where the PUCCH resources in the PUCCH resource set are notified by a 3-bit field in the DCI is shown, but the number of bits is not limited to this.

[0039] There may be cases where the time domains (e.g., slots or symbols) of PUCCHs (e.g., PUCCHs for HARQ-ACK) indicated by multiple DCIs overlap. In such cases, the PUCCH resource is determined based on the PUCCH resource indication field (e.g., PRI field) in the last DCI (the last received PDCCH or PDCCH occasion). DCI may be read as DCI format.

[0040] To determine the last DCI (or DCI format), a DCI format index (eg, DCI format indexing) may be specified as follows: First, for the same PDCCH monitoring occasion index, the serving cell indexes are indexed in ascending order; Next, it is indexed in ascending order among the PDCCH monitoring occasion indices.

[0041] For DCI formats from different TRPs in a serving cell for the same PDCCH monitoring occasion, the DCI format from the first TRP is indexed before (prioritized to) the DCI format from the second TRP.

[0042] For example, assume that for an active DL BWP of a serving cell, a CORESET pool index is not set or a CORESET with a value of 0 is set for one or more first CORESETs, a CORESET pool index with a value of 1 is set for one or more second CORESETs, and an ACK / NACK feedback mode is set to joint (e.g., ackNackFeedbackMode=joint) for an active UL BWP. In such a case, a DCI format detected from PDCCH reception in the first CORESET may be assigned an index with priority over a DCI format detected from PDCCH reception in the second CORESET.

[0043] In Rel.16 / 17, from the viewpoint of multi-TRP, it is supported that up to two CORESET pool indices can be set with the value 0 or 1. From the viewpoint of PDSCH scheduling, a DCI format may schedule a PDSCH or may not schedule a PDSCH.

[0044] Regarding the DCI format for scheduling PDSCH, Rel.16 supports one DCI for scheduling one PDSCH. Rel.17 supports a single DCI for scheduling multiple PDSCHs for FR2-2, allowing up to eight PDSCHs to be scheduled by one DCI.

[0045] Regarding DCI formats that do not schedule PDSCH, Rel. 16 supports SPS release DCI (e.g., SPS release DCI), SCell dormancy indication DCI (e.g., SCell dormancy indication DCI), and type 3 HARQ-ACK codebook triggering DCI (e.g., type 3 HARQ-ACK CB triggering DCI).

[0046] In Rel. 17, additional DCI formats that do not schedule PDSCH are supported: Unified TCI indication DCI (e.g., Unified TCI indication DCI), DCI for one-shot HARQ-ACK retransmission (e.g., DCI for one-shot HARQ-ACK retransmission), and DCI for triggering enhanced type 3 HARQ-ACK codebook triggering (e.g., DCI for triggering enhanced type 3 HARQ-ACK CB).

[0047] From a multicast or unicast perspective, Rel. 17 supports multicast / broadcast DCI formats for scheduling PDSCH.

[0048] In Rel.15 / 16 / 17, PUCCH resource determination is based on the PUCCH resource indication (PRI) included in the DCI. When multiple DCI formats are considered for the same PDCCH monitoring occasion of the same serving cell associated with one PUCCH (e.g., a PUCCH used for HARQ-ACK transmission), the order of the multiple DCI formats (e.g., the indexing order of the DCI formats) is specified only if the DCI formats have different CORESET pool indices.

[0049] On the other hand, when multiple DCI formats correspond to the same PDCCH monitoring opportunity of the same serving cell associated with one PUCCH (e.g., a PUCCH used for HARQ-ACK transmission) (e.g., when multiple DCI formats correspond to the same CORESET pool index), the question arises as to how to order the multiple DCI formats (or the indexes of the multiple DCI formats).

[0050] 4 shows an example in which multiple DCIs indicate the same time domain (for example, slot or symbol) as the PUCCH transmission timing. Here, DCI#1, DCI#3, and DCI#4 of Cell#1 and DCI#2 of Cell#2 indicate the same slot as the PUCCH transmission timing.

[0051] In existing systems, a UE determines a PUCCH resource based on the last DCI. The last DCI is determined based on, for example, a cell index and a PDCCH monitoring opportunity. In the example shown in FIG. 4, DCI#3 and DCI#4 correspond to the same PDCCH monitoring opportunity of the same serving cell#1. In this case, the question arises as to how to determine the order of DCI#3 and DCI#4 (or which DCI is the last DCI).

[0052] If the ordering of DCIs is not determined appropriately, the last DCI (or the DCI with the last index) may not be determined appropriately, which may result in an inability to select PUCCH resources appropriately.

[0053] The inventors focused on the case where multiple DCIs (multiple DCIs specifying PUCCHs in the same time domain) correspond to the same PDCCH monitoring opportunity of the same serving cell, and studied methods for determining PUCCH resources, resulting in the concept of this embodiment.

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

[0055] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0056] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be interchangeable. In the present disclosure, terms such as support, control, controllable, operate, and operate may be interchangeable.

[0057] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0058] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination thereof.

[0059] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0060] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0061] In this disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0062] In this disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0063] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interchangeable. "Spatial relationship information" may be interchangeable with "set of spatial relationship information," "one or more pieces of spatial relationship information," etc. The TCI state and TCI may be interchangeable with each other.

[0064] (Wireless communication method) When a UE receives a plurality of pieces of downlink control information indicating the same time domain as the transmission timing of the uplink control channel, the UE may determine the uplink control channel resource based on the downlink control information with the last index among the plurality of pieces of downlink control information.When a plurality of pieces of downlink control information correspond to the same downlink control channel monitoring opportunity of the same serving cell, the index of each piece of downlink control information may be determined based on a predetermined condition (e.g., one or more parameters corresponding to each piece of downlink control information).

[0065] Regarding PUCCH resource determination for a PUCCH (e.g., HARQ-ACK PUCCH) associated with a DCI (or DCI format), if there are multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell to which the PUCCH is associated, the order of the DCI formats (or the order of indexing of the DCI formats) may be determined based on predetermined conditions.

[0066] The predetermined condition may be, for example, at least one of a CORESET pool index, whether to schedule a PDSCH (or DL-SCH), a start time (e.g., starting time) of a scheduled PDSCH for a DCI format that schedules a PDSCH, a DCI function (e.g., DCI function) for a DCI format that does not schedule a PDSCH, a unicast or multicast / broadcast DCI format, a CORESET index, and a PDCCH candidate index.

[0067] Regarding PUCCH resource determination for PUCCH associated with DCI formats, when there are multiple DCI formats for the same PDCCH monitoring occasion of the same serving cell, for example, at least one of Alt.1 to Alt.7 below may be applied.

[0068] Alt.1 to Alt.7 may be applied independently or in combination. The base station may instruct the UE by RRC / MAC CE / DCI which of Alt.1 to Alt.7 to apply.

[0069] In the following description, whether or not to schedule a PDSCH may be interpreted as whether or not to schedule a DL-SCH. Also, when the same CORESET pool index is present, the same CORESET pool index may be set, or the CORESET pool index may not be set.

[0070] <Alt.1> The order of DCI formats may be determined taking into consideration the order of the CORESET pool index, whether scheduling PDSCH, or scheduled PDSCH starting time for DCI formats scheduling PDSCH, or DCI function for DCI formats not scheduling PDSCH (e.g., CORESET pool index > whether scheduling PDSCH > scheduled PDSCH starting time for DCI formats scheduling PDSCH, or DCI function for DCI formats not scheduling PDSCH).

[0071] [Example 1-0] If DCI formats in the same PDCCH monitoring occasion of the same serving cell have different CORESET pool indices, the DCI format with CORESET pool index 0 will precede (or be indexed with priority over) the DCI format with CORESET pool index 1.

[0072] [Example 1-1] If DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index, the order of the DCIs may be determined based on whether a PDSCH is scheduled or not. For example, a DCI format that schedules a PDSCH comes before (or is indexed with priority over) a DCI format that does not schedule a PDSCH.

[0073] 5 shows an example in which multiple DCIs indicate the same time domain (for example, slot or symbol) as the PUCCH transmission timing. Here, DCI#1, DCI#3, and DCI#4 of Cell#1 and DCI#2 of Cell#2 indicate the same slot as the PUCCH transmission timing.

[0074] In the example shown in Figure 5, DCI#3 and DCI#4 correspond to the same PDCCH monitoring opportunity of the same serving cell#1. If DCI#3 and DCI#4 have the same CORESET pool index (or correspond to the same CORESET pool index), the index may be determined based on whether DCI#3 and DCI#4 each schedule a PDSCH. For example, if DCI#3 schedules a PDSCH and DCI#4 does not schedule a PDSCH, DCI#3 may be indexed with priority over DCI#4.

[0075] Alternatively, if DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index, the DCI format that schedules the PDSCH is later (or is indexed later) than the DCI format that does not schedule the PDSCH.

[0076] Alternatively, if DCI formats in the same PDCCH monitoring occasion of the same serving cell have different CORESET pool indices, this may be an error case, and the UE may not assume / expect this case or may ignore this case.

[0077] [Example 1-2] When DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and each DCI format schedules a PDSCH, the order of the DCIs may be determined based on the start time (e.g., start symbol) of the scheduled PDSCH. For example, a DCI format that schedules a PDSCH with an earlier start time is placed before (or is indexed with priority over) a DCI format that schedules a PDSCH with a later start time. In other words, when multiple DCI formats each schedule a PDSCH, the order of DCIs that schedule PDSCHs with an earlier start time (e.g., first symbol) may be prioritized.

[0078] If DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and each DCI format schedules a PDSCH, this may be an error case. The UE may not assume / expect this case or may ignore this case.

[0079] [Example 1-3] When DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and each DCI format does not schedule a PDSCH, the order of the DCI formats (or the indexing order) may be determined based on the function of the DCI formats. For example, the order of the DCI formats may be determined based on any of the following:

[0080] For example, a DCI format for an SPS release (e.g., SPS release) may be prioritized over a DCI format for an SCell dormancy indication (e.g., SCell dormancy indication), or a DCI format for an SCell dormancy indication may be prioritized over a DCI format for an SPS release.

[0081] Alternatively, the DCI format for SPS release may be prioritized over a DCI format for HARQ-ACK retransmission trigger (e.g., triggering HARQ-ACK retransmission). Alternatively, the DCI format for HARQ-ACK retransmission trigger may be prioritized over the DCI format for SPS release.

[0082] Alternatively, the DCI format for SPS release may be prioritized over a DCI format for enhanced type 3 HARQ-ACK triggering without scheduling a PDSCH (for example, triggering enhanced type 3 HARQ-ACK without scheduling PDSCH). Alternatively, the DCI format for enhanced type 3 HARQ-ACK triggering without scheduling a PDSCH may be prioritized over the DCI format for SPS release.

[0083] Alternatively, the DCI format for SPS release may be prioritized over the DCI format for unified TCI state indication (e.g., unified TCI state indication), or the DCI format for unified TCI state indication may be prioritized over the DCI format for SPS release.

[0084] Alternatively, the DCI format for SCell dormancy instruction may be prioritized over the DCI format for triggering HARQ-ACK retransmission. Alternatively, the DCI format for triggering HARQ-ACK retransmission may be prioritized over the DCI format for SCell dormancy instruction.

[0085] Alternatively, the DCI format for SCell dormancy instruction may be prioritized over a DCI format for enhanced type 3 HARQ-ACK triggering that does not schedule a PDSCH. Alternatively, the DCI format for enhanced type 3 HARQ-ACK triggering that does not schedule a PDSCH may be prioritized over the DCI format for SCell dormancy instruction.

[0086] Alternatively, the DCI format for SCell dormancy indication may be prioritized over the DCI format for unified TCI state indication (e.g., unified TCI state indication). Alternatively, the DCI format for unified TCI state indication may be prioritized over the DCI format for SCell dormancy indication.

[0087] Alternatively, the DCI format for triggering HARQ-ACK retransmission may be prioritized over the DCI format for triggering HARQ-ACK of enhanced type 3 that does not schedule PDSCH, or the DCI format for triggering HARQ-ACK of enhanced type 3 that does not schedule PDSCH may be prioritized over the DCI format for triggering HARQ-ACK retransmission.

[0088] Alternatively, the DCI format for triggering HARQ-ACK retransmission may be prioritized over the DCI format for indicating the integrated TCI status. Alternatively, the DCI format for indicating the integrated TCI status may be prioritized over the DCI format for triggering HARQ-ACK retransmission.

[0089] Alternatively, the DCI format for enhanced type 3 HARQ-ACK triggering that does not schedule a PDSCH may be prioritized over the DCI format for indicating an integrated TCI status, or the DCI format for indicating an integrated TCI status may be prioritized over the DCI format for enhanced type 3 HARQ-ACK triggering that does not schedule a PDSCH.

[0090] If DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and each DCI format does not schedule a PDSCH, this may be an error case. The UE may not assume / expect this case or may ignore this case.

[0091] <Alt.2> The order of DCI formats may be determined taking into consideration the order of whether to schedule a PDSCH, the CORESET pool index, the scheduled PDSCH start time for DCI formats with the same CORESET pool index that schedule a PDSCH, or the DCI function for DCI formats with the same CORESET pool index that do not schedule a PDSCH (e.g., whether scheduling PDSCH > CORESET pool index > scheduled PDSCH starting time for DCI formats with same CORESET pool index scheduling PDSCH, or DCI function for DCI formats with same CORESET pool index not scheduling PDSCH).

[0092] [Example 2-1] If one of multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell schedules a PDSCH and the other DCI formats do not schedule a PDSCH, the order of the DCIs may be determined based on whether the PDSCH is scheduled or not. For example, a DCI format that schedules a PDSCH is placed before (or is indexed with priority over) a DCI format that does not schedule a PDSCH.

[0093] If any of multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell schedules a PDSCH and the other DCI formats do not schedule a PDSCH, the DCI format that schedules a PDSCH comes after (or is indexed after) the DCI format that does not schedule a PDSCH.

[0094] Alternatively, if one of multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell schedules a PDSCH and the other DCI formats do not schedule a PDSCH, this may be an error case, and the UE may not assume / expect this case or may ignore this case.

[0095] [Example 2-2] If multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell schedule a PDSCH (or do not schedule a PDSCH) and the multiple DCI formats have different CORESET pool indices, the order of the DCIs may be determined based on the CORESET pool index. For example, a DCI format with CORESET pool index 0 precedes (or is indexed with priority over) a DCI format with CORESET pool index 1.

[0096] Alternatively, if multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell schedule a PDSCH (or do not schedule a PDSCH) and the multiple DCI formats have different CORESET pool indices, this may be an error case, and the UE may not assume / expect this case or may ignore it.

[0097] [Example 2-3] When multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell schedule PDSCHs and the multiple DCI formats have the same CORESET pool index, the order of the DCIs may be determined based on the start times of the scheduled PDSCHs. For example, a DCI format that schedules a PDSCH with an earlier start time is placed before (or indexed with priority over) a DCI format that schedules a PDSCH with a later start time. In other words, when multiple DCI formats each schedule a PDSCH, the order of the DCI that schedules a PDSCH with an earlier start time (e.g., first symbol) may be prioritized.

[0098] Alternatively, if multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell schedule PDSCH and the multiple DCI formats have the same CORESET pool index, this may be an error case, and the UE may not assume / expect this case or may ignore it.

[0099] [Example 2-4] When multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell do not schedule a PDSCH and the multiple DCI formats have the same CORESET pool index, the order of the DCI formats (or the indexing order) may be determined based on the function of the DCI formats. For example, the order of the DCI formats may be determined based on any of the criteria shown in Examples 1-3 above.

[0100] Alternatively, if multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell do not schedule a PDSCH and the multiple DCI formats have the same CORESET pool index, this may be an error case, and the UE may not assume / expect this case or may ignore it.

[0101] <Alt.3> The order of DCI formats may be determined taking into consideration the order of the CORESET pool index, the unicast or multicast / broadcast DCI format, whether scheduling PDSCH or the scheduled PDSCH starting time, or the DCI function for unicast DCI formats not scheduling PDSCH (e.g., CORESET pool index > unicast or multicast / broadcast DCI format > whether scheduling PDSCH > scheduled PDSCH starting time, or DCI function for unicast DCI formats not scheduling PDSCH).

[0102] Alt.3 may be considered as a variation of Alt.1, for example, in Alt.1, unicast DCI or multicast / broadcast DCI may be additionally considered.

[0103] [Example 3-1] If DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and there is a unicast DCI format and a multicast / broadcast DCI format, the unicast DCI format will come before (or be indexed with priority to) the multicast / broadcast DCI format.

[0104] Alternatively, if DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and there is a unicast DCI format and a multicast / broadcast DCI format, the unicast DCI format comes after (or is indexed after) the multicast / broadcast DCI format.

[0105] Alternatively, if the DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and there is a unicast DCI format and a multicast / broadcast DCI format, this may be an error case. The UE may not assume / expect this case or may ignore this case.

[0106] [Example 3-2] When DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and each DCI format is a unicast DCI format, examples 1-1 / 1-2 / 1-3 in Alt. 1 may be applied.

[0107] [Example 3-3] When DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and each DCI format is a multicast / broadcast DCI format, the order of the DCIs may be determined based on the start time of the scheduled PDSCH. For example, a DCI format that schedules a PDSCH with an earlier start time is placed before (or indexed with priority over) a DCI format that schedules a PDSCH with a later start time. In other words, when multiple DCI formats each schedule a PDSCH, the order of DCIs that schedule PDSCHs with an earlier start time (e.g., first symbol) may be prioritized.

[0108] Alternatively, if DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and each DCI format is a multicast / broadcast DCI format, this may be an error case. The UE may not assume / expect this case or may ignore this case.

[0109] <Alt.4> The order of DCI formats may be determined taking into consideration the order of unicast or multicast / broadcast DCI format, CORESET pool index, whether scheduling PDSCH, scheduled PDSCH starting time, or DCI function for unicast DCI formats not scheduling PDSCH (e.g., unicast or multicast / broadcast DCI format > CORESET pool index > whether scheduling PDSCH > scheduled PDSCH starting time, or DCI function for unicast DCI formats not scheduling PDSCH).

[0110] Alt.4 may be considered as a variation of Alt.1 / Alt.2. For example, in Alt.1 / Alt.2, unicast DCI or multicast / broadcast DCI may be additionally considered.

[0111] [Example 4-1] If one of multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell is a unicast DCI format and the other DCI format is a multicast / broadcast DCI format, the unicast DCI format comes before (or is indexed with priority to) the multicast / broadcast DCI format.

[0112] Alternatively, if one of multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell is a unicast DCI format and the other DCI format is a multicast / broadcast DCI format, the unicast DCI format comes after (or is indexed after) the multicast / broadcast DCI format.

[0113] Alternatively, if one of the multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell is a unicast DCI format and the other DCI formats are multicast / broadcast DCI formats, this may be an error case, and the UE may not assume / expect this case or may ignore this case.

[0114] [Example 4-2] When there are multiple unicast DCI formats in the same PDCCH monitoring occasion of the same serving cell, examples 1-0 / 1-1 / 1-2 / 1-3 in Alt. 1 may be applied.

[0115] [Example 4-3] When there are multiple multicast / broadcast DCI formats for the same PDCCH monitoring occasion of the same serving cell, a DCI format that schedules a PDSCH with an earlier start time is placed before (or is indexed with priority to) a DCI format that schedules a PDSCH with a later start time. In other words, when multiple DCI formats each schedule a PDSCH, the order of DCIs that schedule PDSCHs with an earlier start time (e.g., first symbol) may be prioritized.

[0116] Alternatively, the presence of multiple multicast / broadcast DCI formats in the same PDCCH monitoring occasion of the same serving cell may be an error case, and the UE may not assume / expect this case or may ignore this case.

[0117] <Alt.5> The order of DCI formats may be determined taking into consideration the order of the CORESET pool index, CORESET index, and PDCCH candidate index (for example, CORESET pool index > CORESET index > PDCCH candidate index).

[0118] [Example 5-0] If DCI formats in the same PDCCH monitoring occasion of the same serving cell have different CORESET pool indices, the DCI format with CORESET pool index 0 will precede (or be indexed with priority over) the DCI format with CORESET pool index 1.

[0119] [Example 5-1] When DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index, the ordering (or indexing order) of the DCI formats may be determined based on the CORESET index. For example, a DCI format corresponding to a CORESET with a smaller CORESET index is placed before (or indexed with priority to) a DCI format corresponding to a CORESET with a larger CORESET index.

[0120] Alternatively, if DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index, the DCI format corresponding to a CORESET with a smaller CORESET index will be later (or will be indexed later) than the DCI format corresponding to a CORESET with a larger CORESET index.

[0121] Alternatively, if the DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index, this may be an error case, and the UE may not assume / expect this case or may ignore this case.

[0122] [Example 5-2] When DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and the same CORESET index, the ordering (or indexing order) of the DCI formats may be determined based on the PDCCH candidate index. For example, a DCI format corresponding to a PDCCH candidate with a smaller PDCCH candidate index is placed before (or indexed with priority to) a DCI format corresponding to a PDCCH candidate with a larger PDCCH candidate index.

[0123] Alternatively, if DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and have the same CORESET index, the DCI format corresponding to a PDCCH candidate with a smaller PDCCH candidate index will be later (or will be indexed later) than the DCI format corresponding to a PDCCH candidate with a larger PDCCH candidate index.

[0124] Alternatively, if the DCI formats in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and the same CORESET index, this may be an error case, and the UE may not assume / expect this case or may ignore this case.

[0125] <Alt.6> In Alt.1 / 2 / 3 / 4, the DCI function (for example, DCI function) for the DCI format / unicast DCI format that does not schedule PDSCH may be replaced with the order of CORESET index, PDCCH candidate for the DCI format / unicast DCI format that does not schedule PDSCH (CORESET index > PDCCH candidate index for DCI (unicast DCI) formats not scheduling PDSCH). The DCI format may be read as the unicast DCI format.

[0126] [Example 6-1] When DCI formats (or unicast DCI formats) in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and each DCI format does not schedule a PDSCH, the ordering (or indexing order) of the DCI formats may be determined based on the CORESET index. For example, a DCI format corresponding to a CORESET with a smaller CORESET index is placed before (or is preferentially indexed with) a DCI format corresponding to a CORESET with a larger CORESET index.

[0127] Alternatively, if DCI formats (or unicast DCI formats) in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index and each DCI format does not schedule a PDSCH, the DCI format corresponding to a CORESET with a smaller CORESET index will be later (or will be indexed later) than the DCI format corresponding to a CORESET with a larger CORESET index.

[0128] [Example 6-2] When multiple DCI formats (or unicast DCI formats) in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index, each DCI format does not schedule a PDSCH, and each DCI format corresponds to the same CORESET index, the ordering (or indexing order) of the DCI formats may be determined based on the PDCCH candidate index. For example, a DCI format corresponding to a PDCCH candidate with a smaller PDCCH candidate index is placed before (or is indexed with priority to) a DCI format corresponding to a PDCCH candidate with a larger PDCCH candidate index.

[0129] Alternatively, a DCI format corresponding to a PDCCH candidate with a smaller PDCCH candidate index comes after (or is indexed after) a DCI format corresponding to a PDCCH candidate with a larger PDCCH candidate index.

[0130] Alternatively, it may be an error case if multiple DCI formats (or unicast DCI formats) in the same PDCCH monitoring occasion of the same serving cell have the same CORESET pool index, each DCI format does not schedule a PDSCH, and each DCI format corresponds to the same CORESET index. The UE may not assume / expect this case or may ignore this case.

[0131] <Alt.7> In Alt. 1 / 2 / 3 / 4 / 6, the condition for scheduling a PDSCH (for example, whether scheduling PDSCH) may be whether scheduling a single PDSCH or scheduling multiple PDSCHs (for example, whether scheduling single PDSCH or scheduling multiple PDSCHs).

[0132] For example, any of the following standards may be applied to Alt.1 / 2 / 3 / 4 / 6: Note that the DCI format may be interpreted as a unicast DCI format.

[0133] A DCI format that schedules a PDSCH has priority (or is indexed with priority) over a DCI format that does not schedule a PDSCH, or alternatively, a DCI format that does not schedule a PDSCH may have priority over a DCI format that schedules a PDSCH.

[0134] A DCI format for scheduling a single PDSCH has priority (or is indexed with priority) over a DCI format for scheduling multiple PDSCHs, or a DCI format for scheduling multiple PDSCHs may have priority over a DCI format for scheduling a single PDSCH.

[0135] A DCI format that schedules a larger number of PDSCHs may be prioritized (or indexed with a higher priority) over a DCI format that schedules a smaller number of PDSCHs, or alternatively, a DCI format that schedules a smaller number of PDSCHs may be prioritized over a DCI format that schedules a larger number of PDSCHs.

[0136] A DCI format that schedules a PDSCH with an earlier start time (e.g., start symbol) has priority (or is indexed with priority) over a DCI format that schedules a PDSCH with a later start time. Alternatively, a DCI format that schedules a PDSCH with a later start time may have priority over a DCI format that schedules a PDSCH with an earlier start time. When there are multiple PDSCHs to determine the start time (e.g., when a DCI schedules multiple PDSCHs), the reference PDSCH may be the first scheduled valid PDSCH or the last scheduled valid PDSCH.

[0137] <Variation 1> In Alt.1 to Alt.7, the criteria / parameters to be applied may be changed based on the set ACK / NACK feedback mode (e.g., ackNackFeedbackMode). The ACK / NACK feedback mode may be set to the UE by the base station through higher layer signaling.

[0138] For example, when the ACK / NACK feedback mode (e.g., ackNackFeedbackMode) is set to separate (e.g., separate), the HARQ-ACK codebooks for the two TRPs are configured separately, so the CORESET pool index criterion does not need to be applied in Alt.1 to Alt.7.

[0139] When the ACK / NACK feedback mode (e.g., ackNackFeedbackMode) is set to joint (e.g., joint), the CORESET pool index criteria may be applied in Alt.1 to Alt.7 to commonly control HARQ-ACK feedback between different CORESET pool indices (e.g., commonly apply counter DAI / total DAI).

[0140] Having the same CORESET pool index (eg, with the same CORESET pool index) may be either of the following two cases: Each with a CORESET pool index value of 0 (e.g., each with CORESET pool index value 0), i.e., no CORESET pool index is provided or a CORESET pool index with a value of 0 is provided - Each has a CORESET pool index value of 1.

[0141] <Variation 2> In Alt.1 to Alt.7, in the case of an error, any of the following may be applied: In the following, the DCI format may be read as the unicast DCI format.

[0142] The UE may not expect / assume multiple DCI formats that do not schedule a PDSCH (e.g., multiple DCI formats having the same CORESET pool index) in the same PDCCH monitoring occasion of the same serving cell. The multiple DCI formats may be DCI formats that indicate the same slot for corresponding HARQ-ACK transmission. The DCI format that does not schedule a PDSCH may be interpreted as at least one of a DCI format for an SPS release indication, a DCI format for an SCell dormancy indication, a DCI format for a type 3 HARQ-ACK codebook trigger, a DCI format for an integrated TCI indication, a DCI format for a one-shot HARQ-ACK retransmission trigger, and a DCI format for an extended type 3 HARQ-ACK codebook.

[0143] When there are multiple DCI formats for the same PDCCH monitoring occasion of the same serving cell, the UE does not need to expect / assume that one DCI format (or unicast DCI format) is a DCI format that does not schedule the PDSCH and the other DCI formats (or unicast / multicast / broadcast DCI formats) are DCI formats that schedule the PDSCH. The multiple DCI formats may be DCI formats that indicate the same slot for corresponding HARQ-ACK transmission. The DCI format that does not schedule the PDSCH may be interpreted as at least one of a DCI format for SPS release indication, a DCI format for SCell dormancy indication, a DCI format for type 3 HARQ-ACK codebook trigger, a DCI format for aggregate TCI indication, a DCI format for one-shot HARQ-ACK retransmission trigger, and a DCI format for extended type 3 HARQ-ACK codebook.

[0144] The UE may not expect / assume that multiple DCI formats (corresponding to the same CORESET pool index) each schedule more than one PDSCH when they are in the same PDCCH monitoring occasion for the same serving cell, and the multiple DCI formats may be DCI formats that indicate the same slot for corresponding HARQ-ACK transmission.

[0145] When multiple DCI formats (multiple DCI formats corresponding to the same CORESET pool index) are in the same PDCCH monitoring occasion of the same serving cell, the UE may not assume that there is one DCI format (or unicast DCI format) that schedules multiple PDSCHs and another DCI format (or unicast / multicast / broadcast DCI format) that schedules one PDSCH. The multiple DCI formats may be DCI formats that indicate the same slot for corresponding HARQ-ACK transmission.

[0146] When multiple DCI formats (multiple DCI formats corresponding to the same CORESET pool index) are present in the same PDCCH monitoring opportunity for the same serving cell, the UE does not need to expect / assume that one DCI format schedules multiple PDSCHs and another DCI format does not schedule a PDSCH. The multiple DCI formats may indicate the same slot for corresponding HARQ-ACK transmission. The DCI format that does not schedule a PDSCH may be interpreted as at least one of a DCI format for SPS release indication, a DCI format for SCell dormancy indication, a DCI format for type 3 HARQ-ACK codebook trigger, a DCI format for aggregate TCI indication, a DCI format for one-shot HARQ-ACK retransmission trigger, and a DCI format for extended type 3 HARQ-ACK codebook.

[0147] The UE may not expect / assume that one DCI format is a unicast DCI format and another DCI format is a multicast / broadcast DCI format when there are multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell, and the multiple DCI formats may be DCI formats that indicate the same slot for corresponding HARQ-ACK transmission.

[0148] When there are multiple DCI formats in the same PDCCH monitoring occasion of the same serving cell, the UE may not expect / assume that the multiple DCI formats are multicast / broadcast DCI formats, and the multiple DCI formats may indicate the same slot for corresponding HARQ-ACK transmission.

[0149] The UE may not expect / assume that multiple DCI formats have the same CORESET index when there are multiple DCI formats (multiple DCI formats with the same CORESET pool index) in the same PDCCH monitoring occasion of the same serving cell, and the multiple DCI formats may be DCI formats that indicate the same slot for corresponding HARQ-ACK transmission.

[0150] The UE may not expect / assume that multiple DCI formats correspond to the same CORESET index and PDCCH candidate index when there are multiple DCI formats (multiple DCI formats with the same CORESET pool index) in the same PDCCH monitoring occasion of the same serving cell, and the multiple DCI formats may be DCI formats that indicate the same slot for corresponding HARQ-ACK transmission.

[0151] <Supplementary information> [Notifying information to UE] In the above-described embodiments, notification of any information (from a network (NW) (e.g., a base station (BS))) to a UE (in other words, reception of any information from a BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0152] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0153] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0154] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0155] [Information notification from UE] In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0156] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID in the MAC subheader that is not defined in existing standards.

[0157] If the notification is performed by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0158] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0159] [Application of each embodiment] At least one of the above-described embodiments may be applied when a specific condition is met, which may be specified in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0160] At least one of the above embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0161] The specific UE capabilities may indicate at least one of the following: Supporting specific processing / operations / control / information for at least one of the above embodiments; Supporting multiple DCI formats that do not schedule PDSCH, have the same CORESET pool index, and indicate the same slot for corresponding HARQ-ACK transmissions in the same PDCCH monitoring occasion of the same serving cell; Supporting multiple DCI formats, including one DCI format (or unicast DCI format) that does not schedule PDSCH and another DCI format (or unicast / multicast / broadcast DCI format) that schedules PDSCH, when multiple DCI formats are in the same PDCCH monitoring occasion of the same serving cell, and indicating the same slot for corresponding HARQ-ACK transmission; Supporting multiple DCI formats (DCI formats with the same CORESET pool index) in the same PDCCH monitoring occasion of the same serving cell, each scheduling more than one PDSCH and indicating the same slot for the corresponding HARQ-ACK transmission; Supporting multiple DCI formats (DCI formats with the same CORESET pool index) in the same PDCCH monitoring occasion of the same serving cell, including one DCI format (or unicast DCI format) that schedules more than one PDSCH and another DCI format (or unicast / multicast / broadcast DCI format) that schedules a single PDSCH and indicates the same slot for corresponding HARQ-ACK transmission; Supporting multiple DCI formats (DCI formats with the same CORESET pool index) in the same PDCCH monitoring occasion of the same serving cell, including one DCI format (or unicast DCI format) that schedules more than one PDSCH and another DCI format (or unicast DCI format) that does not schedule a PDSCH, and indicating the same slot for corresponding HARQ-ACK transmission; Supporting unicast DCI format and multicast / broadcast DCI format, which indicate the same slot for corresponding HARQ-ACK transmission in the same PDCCH monitoring occasion of the same serving cell; Supporting multiple multicast / broadcast DCI formats that indicate the same slot for corresponding HARQ-ACK transmissions in the same PDCCH monitoring occasion for the same serving cell; Supporting multiple DCI formats (multiple DCI formats with the same CORESET pool index) in the same PDCCH monitoring occasion of the same serving cell, with the same CORESET index and indicating the same slot for corresponding HARQ-ACK transmission; Supporting multiple DCI formats (multiple DCI formats with the same CORESET pool index) in the same PDCCH monitoring occasion of the same serving cell, which have the same PDCCH candidate index and the same CORESET index and indicate the same slot for corresponding HARQ-ACK transmission;

[0162] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0163] Furthermore, the specific UE capability may be a capability that is applied across all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (for example, Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0164] In addition, at least one of the above-described embodiments may be applied when the UE configures / activates / triggeres specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) by higher layer signaling / physical layer signaling.

[0165] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, Rel. 15 / 16 behavior.

[0166] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. [Appendix 1] A terminal comprising: a receiving unit that receives downlink control information including information regarding the transmission timing of an uplink control channel; and a control unit that, when receiving a plurality of pieces of downlink control information indicating the same time domain as the transmission timing of the uplink control channel, determines an uplink control channel resource based on the downlink control information with the last index among the plurality of pieces of downlink control information, wherein, when a plurality of pieces of downlink control information correspond to the same downlink control channel monitoring opportunity of the same serving cell, the index of each piece of downlink control information is determined based on one or more parameters corresponding to each piece of downlink control information. [Appendix 2] The terminal described in Supplementary Note 1, wherein the one or more parameters corresponding to the downlink control state are at least one of a control resource set pool index corresponding to each of the downlink control information, whether each of the downlink control information schedules a downlink shared channel, and a start time of the downlink shared channel scheduled by each of the downlink control information. [Appendix 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein, when the downlink control information does not schedule a downlink shared channel, an index of the downlink control information is determined based on a function of the downlink control information. [Appendix 4] 4. The terminal according to claim 1, wherein the one or more parameters corresponding to the downlink control state are at least one of a control resource set index and a downlink control channel candidate index corresponding to each of the downlink control information.

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

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

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

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

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

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

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

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

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

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

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

[0178] The core network 30 may include network functions (NFs) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and an Operation, Administration and Maintenance (Management) (OAM). Note that a single network node may provide multiple functions. Furthermore, communication with an external network (e.g., the Internet) may be performed via the DN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0211] The transmitting / receiving unit 120 may transmit downlink control information including information relating to the transmission timing of the uplink control channel.

[0212] When transmitting a plurality of pieces of downlink control information indicating the same time region as the transmission timing of the uplink control channel, the control unit 110 may perform control so as to indicate the uplink control channel resource using the downlink control information with the last index among the plurality of pieces of downlink control information.When a plurality of pieces of downlink control information correspond to the same downlink control channel monitoring opportunity of the same serving cell, the index of each piece of downlink control information may be determined based on one or more parameters corresponding to each piece of downlink control information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0230] The transceiver 220 may receive downlink control information including information relating to the transmission timing of the uplink control channel.

[0231] When the control unit 210 receives a plurality of pieces of downlink control information instructing the same time region as the transmission timing of the uplink control channel, the control unit 210 may determine the uplink control channel resource based on the downlink control information with the last index among the plurality of pieces of downlink control information.When a plurality of pieces of downlink control information corresponds to the same downlink control channel monitoring opportunity of the same serving cell, the control unit 210 may determine the index of each piece of downlink control information based on a predetermined condition (for example, one or more parameters corresponding to each piece of downlink control information).

[0232] The predetermined condition (e.g., one or more parameters corresponding to the downlink control state) may be at least one of a control resource set pool index corresponding to each downlink control information, whether each downlink control information schedules a downlink shared channel, and the start time of the downlink shared channel scheduled by each downlink control information.

[0233] If each piece of downlink control information does not schedule a downlink shared channel, the index of each piece of downlink control information may be determined based on the function of each piece of downlink control information.

[0234] The predetermined condition (for example, one or more parameters corresponding to a downlink control state) may be at least one of a control resource set index and a downlink control channel candidate index corresponding to each piece of downlink control information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0284] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

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

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

[0287] 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. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0288] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

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

[0290] 10 is a diagram showing an example of a vehicle according to an embodiment. A vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0291] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

[0292] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0293] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0294] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0295] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0296] The driving assistance system unit 64 is configured with various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), Artificial Intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0297] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0298] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the above-mentioned base station 10 or user terminal 20. Furthermore, the communication module 60 may be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (or may function as at least one of the base station 10 and user terminal 20).

[0299] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

[0300] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0301] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0319] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with the prefix "i-th" (i is any integer) (for example, "highest" may be interchangeable as "i-th highest").

[0320] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

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

Claims

1. a receiving unit for receiving downlink control information including information regarding the transmission timing of an uplink control channel; a control unit that, when receiving a plurality of pieces of downlink control information instructing the same time domain as the transmission timing of the uplink control channel, determines an uplink control channel resource based on the downlink control information having the last index among the plurality of pieces of downlink control information; A terminal in which, when a plurality of pieces of downlink control information correspond to the same downlink control channel monitoring opportunity of the same serving cell, an index of each piece of downlink control information is determined based on one or more parameters corresponding to each piece of downlink control information.

2. 2. The terminal according to claim 1, wherein the one or more parameters corresponding to the downlink control state are at least one of a control resource set pool index corresponding to each of the downlink control information, whether each of the downlink control information schedules a downlink shared channel, and a start time of the downlink shared channel scheduled by each of the downlink control information.

3. The terminal according to claim 1 , wherein, when the downlink control information does not schedule a downlink shared channel, an index of the downlink control information is determined based on a function of the downlink control information.

4. The terminal according to claim 1 , wherein the one or more parameters corresponding to the downlink control state are at least one of a control resource set index and a downlink control channel candidate index corresponding to each of the downlink control information.

5. receiving downlink control information including information regarding transmission timing of an uplink control channel; When a plurality of pieces of downlink control information instructing the same time domain as the transmission timing of the uplink control channel are received, determining an uplink control channel resource based on the downlink control information having the last index among the plurality of pieces of downlink control information, A wireless communication method for a terminal, in which when multiple pieces of downlink control information correspond to the same downlink control channel monitoring opportunity of the same serving cell, an index of each piece of downlink control information is determined based on one or more parameters corresponding to each piece of downlink control information.

6. a transmitter for transmitting downlink control information including information relating to the transmission timing of an uplink control channel; a control unit that, when transmitting a plurality of downlink control information pieces each indicating the same time domain as the transmission timing of the uplink control channel, controls to indicate an uplink control channel resource by using downlink control information piece having a last index among the plurality of downlink control information pieces; A base station, in which when a plurality of pieces of downlink control information correspond to the same downlink control channel monitoring opportunity of the same serving cell, an index of each piece of downlink control information is determined based on one or more parameters corresponding to each piece of downlink control information.

Images