Terminal, wireless communication method, base station, and system

Abstract

A terminal according to one aspect of this disclosure includes a receiver for receiving information indicating multiple transmission configuration indication (TCI) states and receiving downlink control information that indicates one or more TCI states from among the multiple TCI states and does not indicate scheduling of either of a physical downlink shared channel and a physical uplink shared channel, and a controller for applying the one or more TCI states to multiple types of signals. One aspect of this disclosure makes it possible to appropriately perform TCI state indication.

Description

Technical Field

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

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In a future wireless communication system (e.g., NR), a user terminal (terminal, user terminal, User Equipment (UE)) is considered to control transmission and reception processing based on information regarding Quasi-Co-Location (QCL) (QCL assumption / Transmission Configuration Indication (TCI) state / spatial relationship).

[0006] Applying a set / activated / instructed TCI state to multiple types of signals (channels / RSs) has been considered. However, there are cases where the method of indicating the TCI state is not clear. If the method of indicating the TCI state is not clear, it may lead to a decline in communication quality, a decline in throughput, etc.

[0007] Therefore, one object of the present disclosure is to provide a terminal and a wireless communication method that appropriately perform TCI state indication 、 base station and a system as one of the purposes.

Means for Solving the Problems

[0008] A terminal according to one aspect of the present disclosure includes a plurality of transmission configuration indication (TCI) states applicable to a plurality of types of uplink (UL) channels and reference signals (RSs) including Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Sounding Reference Signal (SRS) a transmitting unit that reports UE capabilities indicating support for one or more TCI state indications among the plurality of TCI states receives information indicating Record 1 the above TCI states without data scheduling First a receiving unit that receives downlink control information having, the transmitting unit the above FirstTransmit hybrid automatic repeat request acknowledgement (HARQ-ACK) information for downlink control information and , the First control unit that applies the one or more TCI states indicated by one or more TCI fields included in the downlink control information to the plurality of types of UL channels and RSs in a plurality of Component Carriers (CCs) further has and, a specific Radio Network Temporary Identifier (RNTI) used for Cyclic Redundancy Check (CRC) scrambling of the first downlink control information indicating the one or more TCI states is different from the C-RNTI used for CRC scrambling of a second downlink control information different from the first downlink control information .

Advantages of the Invention

[0009] According to one aspect of the present disclosure, appropriate TCI state indication can be performed.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

[0011] (TCI, Spatial Relationship, QCL) In NR, it is considered to control at least one of signal and channel (expressed as signal / channel) in a UE, such as reception processing (e.g., at least one of reception, demapping, demodulation, decoding), transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, encoding), based on a Transmission Configuration Indication state (TCI state).

[0012] The TCI state may represent what is applied to downlink signals / channels. What corresponds to the TCI state applied to uplink signals / channels may be expressed as a spatial relation.

[0013] The TCI state is information regarding the quasi - co - location (QCL) of signals / channels, and may also be referred to as spatial reception parameters, spatial relation information, etc. The TCI state may be set for the UE on a per - channel or per - signal basis.

[0014] QCL is an indicator showing the statistical properties of signals / channels. For example, when a certain signal / channel and another signal / channel are in a QCL relationship, it may mean that at least one of Doppler shift, Doppler spread, average delay, delay spread, spatial parameter (e.g., spatial Rx parameter) is the same (QCL with respect to at least one of these) among these different multiple signals / channels.

[0015] Note that the spatial reception parameter may correspond to the reception beam of the UE (e.g., reception analog beam), and the beam may be identified based on spatial QCL. The QCL (or at least one element of QCL) in the present disclosure may be read as sQCL (spatial QCL).

[0016] Multiple types (QCL types) of QCL may be defined. For example, four QCL types A - D may be provided with different parameters (or parameter sets) that can be assumed to be the same, and the parameters (which may also be called QCL parameters) are shown below: · QCL type A (QCL - A): Doppler shift, Doppler spread, average delay, and delay spread, · QCL type B (QCL - B): Doppler shift and Doppler spread, · QCL type C (QCL - C): Doppler shift and average delay, ·QCL type D (QCL-D): Spatial reception parameter.

[0017] For a UE to assume that a certain control resource set (Control Resource Set (CORESET)), channel, or reference signal is in a relationship of a specific QCL (e.g., QCL type D) with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

[0018] The UE may determine at least one of the transmission beam (Tx beam) and the reception beam (Rx beam) of the signal / channel based on the TCI state or QCL assumption of the signal / channel.

[0019] The TCI state may be, for example, information regarding the QCL between the target channel (in other words, the reference signal (Reference Signal (RS)) for the channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0020] The physical layer signaling may be, for example, downlink control information (Downlink Control Information (DCI)).

[0021] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a physical downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a physical downlink control channel (Physical Downlink Control Channel (PDCCH)), a physical uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and a physical uplink control channel (Physical Uplink Control Channel (PUCCH)).

[0022] In addition, the RS related to the channel and QCL may be, for example, at least one of a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a CSI-RS for tracking (also referred to as a Tracking Reference Signal (TRS)), and a reference signal for QCL detection (also referred to as a QRS).

[0023] The SSB is a signal block including at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). The SSB may be referred to as an SS / PBCH block.

[0024] The RS of QCL type X in the TCI state may mean an RS in a relationship of a certain channel / signal (DMRS thereof) and QCL type X, and this RS may also be referred to as the QCL source of QCL type X in the TCI state.

[0025] (Pathloss RS) Pathloss PL in the transmission power control of each of PUSCH, PUCCH, and SRS b,f,c (q d ) [dB] is the index q of a reference signal (RS, Pathloss Reference RS) for the downlink BWP associated with the active UL BWP b of the carrier f of the serving cell c d calculated by the UE using. In the present disclosure, the pathloss reference RS, pathloss (PL)-RS, index q dThe RS used for path loss calculation, the RS resource used for path loss calculation, may be read interchangeably with each other. In the present disclosure, calculate, estimate, measure, track, may be read interchangeably with each other.

[0026] When the path loss RS is updated by the MAC CE, it is being considered whether to change the existing mechanism of the higher layer filtered RSRP for path loss measurement.

[0027] When the path loss RS is updated by the MAC CE, path loss measurement based on L1-RSRP may be applied. At the available timing after the MAC CE for updating the path loss RS, the higher layer filtered RSRP may be used for path loss measurement, and L1-RSRP may be used for path loss measurement before the higher layer filtered RSRP is applied. At the available timing after the MAC CE for updating the path loss RS, the higher layer filtered RSRP may be used for path loss measurement, and the higher layer filtered RSRP of the previous path loss RS may be used before that timing. Similar to the operation of Rel.15, the higher layer filtered RSRP may be used for path loss measurement, and the UE may track all path loss RS candidates set by the RRC. The maximum number of path loss RSs that can be set by the RRC may depend on the UE capability. If the maximum number of path loss RSs that can be set by the RRC is X, path loss RS candidates less than or equal to X may be set by the RRC, and the path loss RS may be selected by the MAC CE from the set path loss RS candidates. The maximum number of path loss RSs that can be set by the RRC may be 4, 8, 16, 64, etc.

[0028] In the present disclosure, the higher layer filtered RSRP, the filtered RSRP, the layer 3 filtered RSRP, may be read interchangeably with each other.

[0029] (Default TCI state / Default spatial relation / Default PL-RS) In the RRC connected mode, when the TCI information in the DCI (upper layer parameter TCI-PresentInDCI) is set to "enabled", and when the TCI information in the DCI is not set, if the time offset between the reception of the DL DCI (DCI for scheduling the PDSCH) and the corresponding PDSCH (PDSCH scheduled by the DCI) is smaller than the threshold (timeDurationForQCL) (application condition, first condition), and if it is non-cross-carrier scheduling, the TCI state of the PDSCH (default TCI state) may be the TCI state of the lowest CORESET ID in the latest slot within the active DL BWP of the CC of the (specific UL signal). Otherwise, the TCI state of the PDSCH (default TCI state) may be the TCI state of the lowest TCI state ID of the PDSCH within the active DL BWP of the scheduled CC.

[0030] In Rel.15, individual MAC CEs for activation / deactivation of PUCCH spatial relation and for activation / deactivation of SRS spatial relation are required. The PUSCH spatial relation follows the SRS spatial relation.

[0031] In Rel.16, at least one of the MAC CEs for activation / deactivation of PUCCH spatial relation and for activation / deactivation of SRS spatial relation may not be used.

[0032] If in FR2, neither the spatial relation for PUCCH nor PL-RS is configured (application condition, second condition), the default assumptions for the spatial relation and PL-RS for PUCCH (default spatial relation and default PL-RS) are applied. If in FR2, neither the spatial relation for SRS (SRS resource for SRS, or SRS resource corresponding to SRI within DCI format 0_1 that schedules PUSCH) nor PL-RS is configured (application condition, second condition), the default assumptions for the spatial relation and PL-RS for PUSCH and SRS scheduled by DCI format 0_1 (default spatial relation and default PL-RS) are applied.

[0033] If a CORESET is configured within the active DL BWP on that CC (application condition), the default spatial relation and default PL-RS may be the TCI state or QCL assumption of the CORESET having the lowest CORESET ID within the active DL BWP. If no CORESET is configured within the active DL BWP on that CC, the default spatial relation and default PL-RS may be the active TCI state having the lowest ID of the PDSCH within the active DL BWP.

[0034] In Rel.15, the spatial relation of the PUSCH scheduled by DCI format 0_0 follows the spatial relation of the PUCCH resource having the lowest PUCCH resource ID among the active spatial relations of the PUCCH on the same CC. The network needs to update the PUCCH spatial relations on all SCell even if PUCCH is not transmitted on the SCell.

[0035] In Rel.16, no PUCCH configuration is required for PUSCH scheduled by DCI format 0_0. For PUSCH scheduled by DCI format 0_0, if there is no active PUCCH spatial relation or no PUCCH resource on the active UL BWP within that CC (application condition, second condition), the default spatial relation and default PL-RS are applied to that PUSCH.

[0036] The application conditions for the default spatial relation / default PL-RS for SRS may include that the default beam path loss activation information element for SRS (upper layer parameter enableDefaultBeamPlForSRS) is set to be effective. The application conditions for the default spatial relation / default PL-RS for PUCCH may include that the default beam path loss activation information element for PUCCH (upper layer parameter enableDefaultBeamPlForPUCCH) is set to be effective. The application conditions for the default spatial relation / default PL-RS for PUSCH scheduled by DCI format 0_0 may include that the default beam path loss activation information element for PUSCH scheduled by DCI format 0_0 (upper layer parameter enableDefaultBeamPlForPUSCH0_0) is set to be effective.

[0037] The above threshold may be referred to as the time duration for QCL, "timeDurationForQCL", "Threshold", "Threshold for offset between a DCI indicating a TCI state and a PDSCH scheduled by the DCI", "Threshold-Sched-Offset", schedule offset threshold, scheduling offset threshold, etc.

[0038] (Multi-TRP) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRP (MTRP)) perform DL transmission to a UE using one or more panels (multi-panel). Also, it is being considered that a UE performs UL transmission to one or more TRPs using one or more panels.

[0039] Note that the plurality of TRPs may correspond to the same cell identifier (cell Identifier (ID)), or may correspond to different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0040] Multi-TRPs (e.g., TRP#1, #2) are connected by ideal / non-ideal backhaul, and information, data, etc. may be exchanged. Different codewords (Code Word (CW)) and different layers may be transmitted from each TRP of the multi-TRP. As a form of multi-TRP transmission, Non-Coherent Joint Transmission (NCJT) may be used.

[0041] In NCJT, for example, TRP#1 modulates and maps the first codeword, layer-maps it, and transmits the first PDSCH with the first number of layers (e.g., 2 layers) using the first precoding. Also, TRP#2 modulates and maps the second codeword, layer-maps it, and transmits the second PDSCH with the second number of layers (e.g., 2 layers) using the second precoding.

[0042] Note that the plurality of PDSCHs (multi-PDSCH) subject to NCJT may be defined to partially or completely overlap in at least one of the time and frequency domains. That is, the first PDSCH from the first TRP and the second PDSCH from the second TRP may overlap in at least one of the time and frequency resources.

[0043] These first PDSCH and second PDSCH may be assumed to be not quasi-co-located. Reception of multi-PDSCH may be interpreted as simultaneous reception of PDSCH that is not of a certain QCL type (e.g., QCL type D).

[0044] Multiple PDSCH from multiple TRPs (which may be referred to as multiple PDSCH) may be scheduled using one DCI (single DCI, single PDCCH) (single master mode, single-DCI based multi-TRP). Multiple PDSCH from multiple TRPs may be scheduled separately using multiple DCIs (multi-DCI, multiple PDCCH) (multi-master mode, multi-DCI based multi-TRP).

[0045] In URLLC for multi-TRP, it is being considered to support repetition of PDSCH (transport block (TB) or codeword (CW)) across multiple TRPs. Repetition schemes (URLLC schemes, e.g., scheme 1, 2a, 2b, 3, 4) across multiple TRPs in the frequency domain or layer (space) domain or time domain are being considered. In scheme 1, multi-PDSCH from multiple TRPs is space division multiplexing (SDM). In schemes 2a and 2b, PDSCH from multiple TRPs is frequency division multiplexing (FDM). In scheme 2a, the redundancy version (RV) for multiple TRPs is the same. In scheme 2b, the RV for multiple TRPs may be the same or different. In schemes 3 and 4, multi-PDSCH from multiple TRPs is time division multiplexing (TDM). In scheme 3, multi-PDSCH from multiple TRPs is transmitted within one slot. In scheme 4, multi-PDSCH from multiple TRPs is transmitted in different slots.

[0046] According to such a multi-TRP scenario, more flexible transmission control using a good-quality channel is possible.

[0047] To support multi-TRP transmission within a cell (intra-cell, having the same cell ID) and between cells (inter-cell, having different cell IDs) based on multiple PDCCHs, in the RRC configuration information for linking multiple pairs of PDCCH and PDSCH having multiple TRPs, one control resource set (CORESET) within the PDCCH configuration information (PDCCH-Config) may correspond to one TRP.

[0048] If at least one of the following Conditions 1 and 2 is satisfied, the UE may determine that it is a multi-TRP based on multi-DCI. In this case, the TRP may be rewritten to the CORESET pool index. [Condition 1] One CORESET pool index is set. [Condition 2] Two different values (e.g., 0 and 1) of the CORESET pool index are set.

[0049] If the following condition is satisfied, the UE may determine that it is a multi-TRP based on single-DCI. In this case, the two TRPs may be rewritten to two TCI states indicated by the MAC CE / DCI. [Condition] "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE" is used to indicate one or two TCI states for one code point of the TCI field in the DCI.

[0050] The common beam indication DCI may be a UE-specific DCI format (e.g., DL DCI format (e.g., 1_1, 1_2), UL DCI format (e.g., 0_1, 0_2)), or a UE-group common DCI format.

[0051] (Simultaneous beam update for multiple CCs) In Rel.16, one MAC CE can update the beam indices (TCI states) of multiple CCs.

[0052] The UE can have up to two applicable CC lists (e.g., applicable-CC-list) configured by RRC. When two applicable CC lists are configured, the two applicable CC lists may correspond to intra-band CA in FR1 and intra-band CA in FR2, respectively.

[0053] The MAC CE for activating the TCI state of PDCCH activates the TCI states associated with the same CORESET ID on all BWPs / CCs within the applicable CC list.

[0054] The MAC CE for activating the TCI state of PDSCH activates the TCI states on all BWPs / CCs within the applicable CC list.

[0055] The MAC CE for activating the spatial relation of A-SRS / SP-SRS activates the spatial relations associated with the same SRS resource ID on all BWPs / CCs within the applicable CC list.

[0056] For example, the UE configures an applicable CC list indicating CC#0, #1, #2, #3 and a list indicating 64 TCI states for the CORESET or PDSCH of each CC. When one TCI state of CC#0 is activated by a MAC CE, the corresponding TCI states are activated in CC#1, #2, and #3.

[0057] Such simultaneous beam updates are considered to be applicable only in the single TRP case.

[0058] For PDSCH, the UE may follow the following procedure A. [Procedure A] The UE receives an activation command to map up to 8 TCI states to the code points of the DCI field (TCI field) within one CC / DL BWP or within one set of CC / BWPs. If one set of TCI state IDs is activated for one set of CC / DL BWPs, where the applicable list of CCs is determined by the CCs indicated in the activation command, the same set of TCI states is applied to all DL BWPs within the indicated CCs. A set of TCI state IDs can only be activated for one set of CC / DL BWPs if the UE does not provide different values of the CORESET pool index (CORESETPoolIndex) within the CORESET information element (ControlResourceSet) and does not provide at least one TCI code point mapped to two TCI states.

[0059] For the PDCCH, the UE may follow the following procedure B. [Procedure B] If the UE provides a list of up to two cells for simultaneous TCI state activation by means of the simultaneous TCI update list (at least one of simultaneousTCI-UpdateList-r16 and simultaneousTCI-UpdateListSecond-r16), in a list determined from the serving cell index provided by the MAC CE command, for all configured DL BWPs of all configured cells within one list, the UE applies antenna port quasi co-location (QCL) provided by a TCI state having the same activated TCI state ID value for a CORESET having index p. The simultaneous TCI cell list can be provided for simultaneous TCI state activation only if the UE does not provide different values of the CORESET pool index (CORESETPoolIndex) within the CORESET information element (ControlResourceSet) and does not provide at least one TCI code point mapped to two TCI states.

[0060] For semi-persistent (SP) / aperiodic (AP)-SRS, the UE may be based on the following procedure C. [Procedure C] For a set of CC / BWP, when the spatial relation information (spatialRelationInfo) for the SP or AP-SRS resource set by the SRS resource information element (higher layer parameter SRS-Resource) is activated / updated by the MAC CE, where the applicable list of CCs is indicated by the simultaneous spatial update list (higher layer parameter simultaneousSpatial-UpdateList-r16 or simultaneousSpatial-UpdateListSecond-r16), for the SP or AP-SRS resources with the same SRS resource ID in all BWPs within the indicated CC, the spatial relation information is applied. Only if the UE does not provide multiple different values of the CORESET pool index (CORESETPoolIndex) within the CORESET information element (ControlResourceSet) and does not provide at least one TCI code point mapped to two TCI states, for a set of CC / BWP, the spatial relation information (spatialRelationInfo) for the SP or AP-SRS resource set by the SRS resource information element (higher layer parameter SRS-Resource) is activated / updated by the MAC CE.

[0061] The simultaneous TCI cell list (simultaneousTCI-CellList), the simultaneous TCI update list (at least one of simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16) is a list of serving cells for which the TCI relationship can be updated simultaneously using the MAC CE. simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16 do not contain the same serving cell.

[0062] The simultaneous spatial update list (at least one of the upper layer parameters simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16) is a list of serving cells whose spatial relationships can be updated simultaneously using a MAC CE. simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16 do not contain the same serving cell.

[0063] Here, the simultaneous TCI update list and the simultaneous spatial update list are set by RRC, the CORESET pool index of the CORESET is set by RRC, and the TCI code point mapped to the TCI state is indicated by a MAC CE.

[0064] (Unified / Common TCI Framework) According to the unified TCI framework, the UL and DL channels can be controlled by a common framework. Instead of defining the TCI state or spatial relationship for each channel as in Rel.15, the unified TCI framework may indicate a common beam (common TCI state) and apply it to all UL and DL channels, or apply the common beam for UL to all UL channels and the common beam for DL to all DL channels.

[0065] One common beam for both DL and UL, or a common beam for DL and a common beam for UL (two common beams in total) are being considered.

[0066] The UE may assume the same TCI state (joint TCI state, joint TCI pool, joint common TCI pool) for both UL and DL. The UE may assume different TCI states (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool) for each of UL and DL.

[0067] Based on beam management based on MAC CE (MAC CE level beam indication), the default beams for UL and DL may be aligned. The default TCI state of the PDSCH may be updated to match the default UL beam (spatial relationship).

[0068] Based on beam management based on DCI (DCI level beam indication), a common beam / unified TCI state may be indicated from the same TCI pool (joint common TCI pool, joint TCI pool, set) for both UL and DL. M (>1) TCI states may be activated by MAC CE. The UL / DL DCI may select one from the M active TCI states. The selected TCI state may be applied to the channels / RSs for both UL and DL.

[0069] The TCI pool (set) may be a plurality of TCI states set by RRC parameters, or among the plurality of TCI states set by RRC parameters, a plurality of TCI states (active TCI states, active TCI pool, set) activated by MAC CE. Each TCI state may be a QCL type A / D RS. The QCL type A / D RS may be set as SSB, CSI-RS, or SRS.

[0070] In the example of FIG. 1A, the RRC parameter (information element) sets a plurality of TCI states for both DL and UL. The MAC CE may activate a plurality of the set TCI states. The DCI may indicate one of the activated plurality of TCI states. The DCI may be UL / DL DCI. The indicated TCI state may be applied to at least one (or all) of the UL / DL channels / RSs. One DCI may indicate both UL TCI and DL TCI.

[0071] In the example of FIG. 1A, one point may be one TCI state applied to both UL and DL, or two TCI states applied to UL and DL respectively.

[0072] At least one of the plurality of TCI states set by the RRC parameter and the plurality of TCI states activated by the MAC CE may be called a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The plurality of TCI states activated by the MAC CE may be called an active TCI pool (active common TCI pool).

[0073] In the example of FIG. 1B, the RRC parameter sets a plurality of TCI states (joint common TCI pool) for both DL and UL. The MAC CE may activate a plurality of the set TCI states (active TCI pool). Separate active TCI pools for each of UL and DL may be set / activated.

[0074] A DL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state(s) may be applied to one or more (or all) DL channels / RSs. The DL channel may be a PDCCH / PDSCH / CSI-RS. The UE may determine the TCI state of each DL channel / RS using the Rel.16 TCI state operation (TCI framework). A UL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state(s) may be applied to one or more (or all) UL channels / RSs. The UL channel may be a PUSCH / SRS / PUCCH. Thus, different DCIs may separately indicate UL TCI and DL DCI.

[0075] The existing DCI format 1_2 / 1_2 may be used for indicating a common TCI state.

[0076] The common TCI framework may have separate TCI states for DL and UL.

[0077] The common TCI framework may have separate TCI states for DL and UL. It is not preferred to indicate a UL-only common TCI state using DCI format 1_1 / 1_2.

[0078] (SPS PDSCH) In NR, transmission and reception based on Semi-Persistent Scheduling (SPS) is utilized. In the present disclosure, SPS may be mutually read as Downlink (DL) SPS.

[0079] The UE may activate or deactivate (release) the SPS configuration based on the Physical Downlink Control Channel (PDCCH). The UE may receive the corresponding Physical Downlink Shared Channel (PDSCH) of the SPS based on the activated SPS configuration.

[0080] In the present disclosure, the PDCCH may be read as Downlink Control Information (DCI) transmitted using the PDCCH, simply DCI, etc. Also, in the present disclosure, SPS, SPS PDSCH, SPS configuration, SPS occasion, SPS reception, SPS PDSCH reception, SPS scheduling, etc. may be read as each other.

[0081] The DCI for activating or deactivating (releasing) the SPS configuration may be called activation DCI (or SPS assignment DCI), deactivation DCI, etc. The deactivation DCI may be called release DCI, simply release, etc.

[0082] The DCI may have Cyclic Redundancy Check (CRC) bits scrambled by a specific RNTI (for example, Configured Scheduling Radio Network Temporary Identifier (CS-RNTI)).

[0083] The DCI may be, for example, a DCI format for PUSCH scheduling (such as DCI format 0_0, 0_1, etc.), a DCI format for PDSCH scheduling (such as DCI format 1_0, 1_1, etc.). A DCI with a plurality of fields indicating a certain bit string may indicate an SPS activation DCI or an SPS release DCI.

[0084] The SPS configuration (which may also be referred to as configuration information related to SPS) may be set for the UE using upper layer signaling.

[0085] The configuration information related to SPS (for example, the "SPS-Config" information element of RRC) may include an index for identifying SPS (which may also be referred to as an SPS index, an SPS configuration index, etc.), information related to the resources of SPS (for example, the period of SPS), information related to the PUCCH resources for SPS, etc.

[0086] The UE may determine the length, start symbol, etc. of the SPS based on the time domain allocation field of the SPS activation DCI.

[0087] The SPS may be set in a special cell (SpCell) (for example, a primary cell (PCell) or a primary secondary cell (PSCell)), or may be set in a secondary cell (SCell).

[0088] In Rel.16 NR, the UE may be provided with a plurality of SPS configurations. In this case, the UE may activate / deactivate a plurality of SPS configurations by one activation / release DCI.

[0089] The DCI that separately instructs releases for each SPS setting is called a separate release DCI. The DCI that jointly instructs the releases of multiple SPS settings is called a joint release DCI.

[0090] In Rel.16 NR, the SPS settings (e.g., SPS-Config) notified by upper layer signaling may include at least one of the following: · Information indicating a period (e.g., periodicity), · Information indicating the number of HARQ processes (e.g., nrofHARQ-Processes), · Information regarding resources (e.g., PUCCH resources) for the uplink control channel (e.g., Physical Uplink Control Channel) used for transmitting HARQ-ACK (e.g., n1PUCCH-AN), · Table information (e.g., MCS table (mcs-Table)) used for determining the modulation and coding scheme (MCS), · Information indicating one of multiple DL SPS settings in one BWP (e.g., SPS setting index, sps-ConfigIndex, sps-ConfigIndex-r16), · Information regarding the offset used to generate the HARQ process ID (e.g., harq-ProcID-Offset, harq-ProcID-Offset-r16), · Information for calculating the period of the SPS PDSCH (e.g., periodicityExt, periodicityExt-r16), · Information indicating the HARQ-ACK codebook corresponding to the HARQ-ACK for the SPS PDSCH and the ACK for the SPS PDSCH release (e.g., harq-CodebookID, harq-CodebookID-r16), · Information indicating the number of repetitions of the SPS PDSCH (e.g., pdsch-AggregationFactor, pdsch-AggregationFactor-r16).

[0091] In addition, at least one of the SPS activation DCI and the release DCI may include at least one of the following information. · Information regarding the allocation of time domain resources (e.g., one or more symbols) (time domain resource assignment (TDRA)) · Information regarding the allocation of frequency domain resources (e.g., one or more Physical Resource Blocks (PRBs) (also referred to as Resource Blocks (RBs))) (frequency domain resource assignment (FDRA)) · Information regarding MCS (e.g., MCS index) · Information indicating the HARQ process (e.g., HARQ process number (HPN), HARQ process ID) · Information indicating the redundancy version (e.g., Redundancy Version (RV)) · Information regarding DL allocation (e.g., Downlink assignment index) · Information regarding PUCCH resources (e.g., PUCCH resource indicator) · Information regarding the timing for feedback (transmission) of HARQ-ACK (e.g., PDSCH-HARQ-ACK feedback timing indicator) · Information regarding the carrier (e.g., Carrier indicator (CI)) · Information regarding the Bandwidth Part (BWP) (e.g., Bandwidth part indicator (BI)) · New Data Indicator (NDI)

[0092] In the example of Figure 2, the UE receives SPS configuration by RRC signaling. The SPS configuration includes the period of the SPS PDSCH. The UE monitors the PDCCH. When the UE receives the activation DCI for configured scheduling (CS), it receives the PDSCH. The activation DCI has a CRC scrambled by the CS-RNTI. Thereafter, the UE receives the PDSCH without PDCCH according to the configured period. The UE may receive the activation DCI that overwrites the configured scheduling (CS).

[0093] If the UE receives a PDSCH without receiving the corresponding PDCCH, or if the UE receives a PDCCH that indicates the SPS PDSCH release, the UE generates one corresponding HARQ-ACK information bit. If the UE receives a PDCCH that indicates the SPS PDSCH release, the UE generates one corresponding HARQ-ACK information bit even if it does not receive the PDSCH.

[0094] The case of multiplexing the HARQ-ACK feedback for the SPS PDSCH and the HARQ-ACK feedback for the dynamic PDSCH on one PUCCH is being considered.

[0095] For the type 1 (semi-static) HARQ-ACK codebook, in cases where HARQ-ACK feedback for one or more SPS PDSCH receptions without the corresponding PDCCH is multiplexed with HARQ-ACK feedback for at least one of the dynamically scheduled PDSCH, SPS PDSCH release, or in cases where HARQ-ACK feedback for at least one SPS PDSCH release is multiplexed with HARQ-ACK feedback for the dynamically scheduled PDSCH, or in cases where only HARQ-ACK feedback for the SPS PDSCH is reported, it is considered to follow at least one of the following derivation methods 1-1 to 1-3.

[0096] [Derivation method 1-1] By reusing the mechanism of Rel.15 (based on the row index of the TDRA table and K1 indicated by the activation DCI), the HARQ-ACK bit position for SPS PDSCH reception is derived.

[0097] [Derivation method 1-2] By reusing the mechanism of Rel.15 (based on the row index of the TDRA table (value of the TDRA field) indicated by the activation DCI and the K1 (value of the PDSCH-to-HARQ feedback indicator field) indicated by the release DCI), the HARQ-ACK bit position for the SPS PDSCH release with a separate release DCI is derived.

[0098] [Derivation method 1-3] Based on the row index of the TDRA table indicated by the activation DCI for the SPS PDSCH with the lowest SPS setting index among the jointly released SPS settings, and the row index of the TDRA table and K1 indicated by the release DCI, the HARQ-ACK bit position for the SPS PDSCH release with a joint release DCI is derived.

[0099] Thus, for the Type 1 HARQ-ACK codebook, the HARQ-ACK bit positions for SPS PDSCH are based on the TDRA index and K1 in the activation DCI, and for SPS separate release DCI / SPS joint release DCI, the HARQ-ACK bit positions are based on the TDRA index in the activation DCI (for the lowest SPS configuration index) and K1 in the release, and this is being considered.

[0100] For the Type 2 (dynamic) HARQ-ACK codebook, it is being considered to follow at least one of the following derivation methods 2-1 to 2-3.

[0101] [Derivation method 2-1] By reusing the Rel.15 mechanism (based on the downlink assignment index (DAI) and K1 indicated by the release DCI), the HARQ-ACK bit order for SPS PDSCH release with separate release DCI / joint release DCI is derived.

[0102] [Derivation method 2-2] By reusing the Rel.15 mechanism (based on the DAI and K1 indicated by the activation DCI), the HARQ-ACK bit order for SPS PDSCH with the associated PDCCH is derived.

[0103] [Derivation method 2-3] In a case where HARQ-ACK feedback for one or more SPS PDSCH receptions without corresponding PDCCH is multiplexed with HARQ-ACK feedback for at least one of dynamically scheduled PDSCH and SPS PDSCH release, the HARQ-ACK bits for one or more SPS PDSCH receptions without corresponding PDCCH are added after the HARQ-ACK bits for at least one of dynamically scheduled PDSCH and SPS PDSCH release. The order of the added HARQ-ACK bits is, firstly, in ascending order of DL slots for each combination of {SPS configuration index, serving cell index} of SPS configuration index and serving cell index, secondly, in ascending order of SPS configuration index for each serving cell index, and thirdly, it may be in ascending order of serving cell index.

[0104] Thus, for type 2 HARQ-ACK codebook, the order of HARQ-ACK bits for SPS PDSCH is based on DAI and K1 in activation DCI. It is being considered that the order of HARQ-ACK bits for SPS separate release DCI / SPS joint release DCI is based on DAI and K1 in release DCI.

[0105] For scheduling activation, scheduling release, DL SPS assignment PDCCH, or configured UL grant type 2 PDCCH, the UE checks the following states 1 to 4. [State 1] The CRC of the corresponding DCI format is scrambled using the CS-RNTI provided by cs-RNTI. [State 2] The new data indicator field in the DCI format for the activated transport block is set to '0'. [State 3] If the DFI flag exists in the DCI format, the DFI flag field is set to '0'. [State 4] If the confirmation is for scheduling activation and there is a PDSCH-to-HARQ timing indicator field in the DCI format, the value of the PDSCH-to-HARQ timing indicator field is not applicable from dl-DataToUL-ACK.

[0106] If the UE provides a single configuration for UL grant type 2 PUSCH or SPS PDSCH and all fields of the DCI format are set according to the specification table (e.g., Figure 3A), the confirmation of the DCI format is achieved.

[0107] If the UE provides one or more configurations for UL grant type 2 PUSCH or SPS PDSCH, follow the following procedures 1 and 2.

[0108] [Procedure 1] If the UE provides Type2Configuredgrantconfig-ReleaseStateList or SPS-ReleaseStateList, the value of the HARQ process number field in the DCI format indicates the corresponding entry in the scheduling release of one or more UL grant type 2 PUSCH or SPS PDSCH configurations.

[0109] [Procedure 2] If the UE does not provide Type2Configuredgrantconfig-ReleaseStateList or SPS-ReleaseStateList, the value of the HARQ process number field in the DCI format indicates the release for the UL grant type 2 PUSCH or SPS PDSCH configuration corresponding to the same value provided by Configuredgrantconfig-index or SPSconfig-index.

[0110] If all fields in a DCI format are set according to the specification table (e.g., Figure 3B), the verification of that DCI format is achieved. If the verification is achieved, the UE regards the information in that DCI format as a valid activation or a valid release for DL SPS or configured UL grant type 2. If the verification is not achieved, the UE discards the information in that DCI format.

[0111] For SPS PDSCH release, special values of special fields (e.g., new data indicator (NDI), downlink feedback information (DFI), redundancy version (RV), modulation and coding scheme (MCS), frequency domain resource assignment (FDRA), HARQ process number (HPN)) (e.g., Figures 3A and 3B) are reused for SPS configuration index indication (verification).

[0112] The UE is assumed to provide HARQ-ACK information corresponding to the SPS PDSCH N symbols after the last symbol of the PDCCH that provides the SPS PDSCH release. If processingType2Enabled of PDSCH-ServingCellConfig is set to be valid for the serving cell having the PDCCH that provides the SPS PDSCH release, N = 5 for μ = 0, N = 5.5 for μ = 1, N = 11 for μ = 2; otherwise, N = 10 for μ = 0, N = 12 for μ = 1, N = 22 for μ = 2, N = 25 for μ = 3. Here, μ corresponds to the minimum SCS configuration between the SCS configuration of the PDCCH that provides the SPS PDSCH release and the SCS configuration of the PUCCH that carries the HARQ-ACK information corresponding to the SPS PDSCH release.

[0113] Thus, the HARQ-ACK for the SPS PDSCH release follows N symbols after the PDCCH.

[0114] (PUCCH Resource Determination) After RRC connection (when the UE is provided with an individual PUCCH resource configuration), the UE transmits HARQ-ACK information on the PUCCH.

[0115] The UE determines the HARQ-ACK feedback timing (K1). K1 corresponds to the period (e.g., slots) from the reception of the DL transmission (e.g., PDSCH) to the transmission of the HARQ-ACK for the DL transmission. Information regarding the HARQ-ACK timing (K1) may be included in the DCI used for the scheduling of the PDSCH.

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

[0117] When the UE receives the DCI that schedules the PDSCH, it determines the timing for feedback of the HARQ-ACK for the PDSCH based on the information included in the DCI.

[0118] The UE determines the PUCCH resource to be used for the transmission of the HARQ-ACK based on the following Steps 1 and 2 (Figure 4).

[0119] [Step 1] The UE determines the PUCCH resource set to be used in the slot for transmitting the HARQ-ACK.

[0120] For the UE, one or more PUCCH resource sets are notified (or configured) by upper layer signaling. A PUCCH resource set may include one or more PUCCH resources. For example, K (e.g., 1 ≤ K ≤ 4) PUCCH resource sets may be notified to the UE from the base station. Each PUCCH resource set may include M (e.g., 8 ≤ M ≤ 32, or 1 ≤ M ≤ 8) PUCCH resources.

[0121] 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). The UCI payload size may be the number of bits of the UCI excluding the cyclic redundancy check (CRC) bits.

[0122] In the example of FIG. 5, assume K = 4, and four PUCCH resource sets #0 - #3 are configured for the UE from the base station by upper layer signaling. Also assume that PUCCH resource sets #0 - #3 each include 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.

[0123] Each PUCCH resource configured for the UE may include the value of at least one of the following parameters (also referred to as fields or information, etc.). Note that for each parameter, a range of values that can be taken for each PUCCH format may be defined. · The symbol at which the allocation of the PUCCH starts (start symbol) · The number of symbols allocated to the PUCCH within a slot (the period allocated to the PUCCH) · The index of the resource block (physical resource block (PRB)) at which the allocation of the PUCCH starts · The number of PRBs allocated to the PUCCH ·Whether to enable frequency hopping for PUCCH ·Frequency resource of the second hop and index of the initial cyclic shift (CS) when frequency hopping is enabled ·Index of the orthogonal cover code (e.g., OCC: Orthogonal Cover Code) in the time domain, and the length of the OCC used for block spreading before discrete Fourier transform (DFT) (also referred to as OCC length, spreading rate, etc.) ·Index of the OCC used for block-wise spreading after DFT

[0124] When PUCCH resource sets #0 to #3 are configured for the UE as in this example, the UE selects one of the PUCCH resource sets based on the UCI payload size.

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

[0126] Thus, the range of UCI payload sizes for which PUCCH resource set #i (i = 0, …, K - 1) is selected is N i bits or more and N i+1 - 1 bits or less (i.e., {N i , …, N i+1 - 1} bits).

[0127] Here, the start positions (start bit numbers) N0 and N1 of the UCI payload sizes for PUCCH resource sets #0 and #1 may be 1 and 3, respectively. As a result, when transmitting UCI of 2 bits or less, PUCCH resource set #0 is selected, so PUCCH resource set #0 may include PUCCH resources #0 to #M-1 for at least one of PF0 and PF1. On the other hand, when transmitting UCI exceeding 2 bits, one of PUCCH resource sets #1 to #3 is selected, so PUCCH resource sets #1 to #3 may each include PUCCH resources #0 to #M-1 for at least one of PF2, PF3, and PF4.

[0128] When i = 2, …, K-1, information (start position information) indicating the start position (N i ) of the UCI payload size for PUCCH resource set #i may be notified (or set) to the UE using upper layer signaling. The start position (N i ) may be UE-specific. For example, the start position (N i ) may be set to a value in the range of 4 or more and 256 or less (for example, a multiple of 4). For example, 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 upper layer signaling (for example, user-specific RRC signaling), respectively.

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

[0130] In this way, the UE selects one PUCCH resource set from one or more PUCCH resource sets configured in the upper layer based on the UCI payload size (e.g., HARQ-ACK bits when the UCI is HARQ-ACK).

[0131] [Step 2] The UE determines one PUCCH resource from one or more PUCCH resources included in the PUCCH resource set.

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

[0133] The UE can determine a single PUCCH resource used for UCI transmission based on at least one of the field in the DCI (PUCCH resource indicator (PRI) field) and the CCE of the PDCCH carrying the DCI (the index of the first CCE corresponding to the PDCCH, the number of CCEs in the CORESET of the PDCCH) from among PUCCH resources #0 to #M-1 included in the PUCCH resource set selected based on the UCI payload size.

[0134] The number M of PUCCH resources in one PUCCH resource set may be configured for the UE by upper layer signaling. For example, when 8 or fewer PUCCH resources are configured by upper layer signaling, the PUCCH resources in the PUCCH resource set may be notified by a 3-bit field (PRI) in the DCI. The number of bits of this field is not limited to 3.

[0135] For PUCCH resource set 0 (the first PUCCH resource set, when M is greater than 8), the UE may determine one PUCCH resource within the PUCCH resource set based on the PRI (Δ PRI ) in the scheduling DCI, the index (n CCE,0 ) of the first CCE of the PDCCH carrying the DCI, and the number of CCEs (N CCE ) within the CORESET of the PDCCH.

[0136] For PUCCH resource sets 1 to 3 (the second to fourth PUCCH resource sets), the UE may determine one PUCCH resource within the PUCCH resource set based on the PRI.

[0137] (Analysis) In the common TCI framework, it is not clear which DCI / which DCI format is used for the indication of at least one TCI state (beam) in cases 1 to 3 below. Also, in the common TCI framework, it is not clear how to send HARQ-ACK for the beam indication DCI of at least one TCI state (beam) in cases 1 to 3 below. [Case 1] Common beam indication for both UL and DL (or, if a common beam indication for both UL and DL is set, or, the case of a common beam indication for both UL and DL) [Case 2] Beam indication for DL only for separate beam indications of UL and DL [Case 3] Beam indication for UL only for separate beam indications of UL and DL

[0138] If the TCI state is not properly indicated, there may be a risk of deterioration in communication quality, throughput degradation, etc.

[0139] Therefore, the inventors have conceived a method for indicating the TCI state.

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

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

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

[0143] In the present disclosure, MAC CE, activation / deactivation command may be read interchangeably.

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

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

[0146] In the present disclosure, beam, spatial domain filter, spatial setting, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI assumption, QCL assumption, QCL parameter, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS of QCL type D for TCI state / QCL assumption, RS of QCL type A for TCI state / QCL assumption, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, PL-RS may be read interchangeably with each other. In the present disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, source of DL-RS, SSB, CSI-RS, SRS may be read interchangeably with each other.

[0147] UL DCI, DCI for scheduling a UL channel (e.g., PUSCH), DCI format 0_x (x = 0, 1, 2,...) may be read interchangeably with each other. DL DCI, DCI for scheduling a DL channel (PDSCH), DCI format 1_x (x = 0, 1, 2,...) may be read interchangeably with each other.

[0148] In the present disclosure, HARQ-ACK information, ACK, and NACK may be read as each other.

[0149] In the present disclosure, link direction, downlink (DL), uplink (UL), and one of UL and DL may be read as each other.

[0150] In the present disclosure, pool, set, group, and list may be read as each other.

[0151] In the present disclosure, common beam, common TCI, common TCI state, unified TCI, unified TCI state, TCI state applicable to DL and UL, TCI state applied to multiple (multiple types of) channels / RSs, TCI state applicable to multiple types of channels / RSs, and PL-RS may be read as each other.

[0152] In the present disclosure, multiple TCI states set by RRC, multiple TCI states activated by MAC CE, pool, TCI state pool, active TCI state pool, common TCI state pool, joint TCI state pool, separate TCI state pool, common TCI state pool for UL, common TCI state pool for DL, common TCI state pool set / activated by RRC / MAC CE, and TCI state information may be read as each other.

[0153] In the present disclosure, beam, spatial domain filter, spatial setting, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI assumption, QCL assumption, QCL parameter, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS of QCL type D for TCI state / QCL assumption, RS of QCL type A for TCI state / QCL assumption, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, PL-RS may be read interchangeably with each other. In the present disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, source of DL-RS, SSB, CSI-RS, SRS may be read interchangeably with each other.

[0154] In the present disclosure, panel, Uplink (UL) transmission entity, point, TRP, spatial relationship, Control Resource Set (CORESET), PDSCH, codeword, base station, antenna port of a signal (for example, Demodulation Reference Signal (DMRS) port), antenna port group of a signal (for example, DMRS port group), group for multiplexing (for example, Code Division Multiplexing (CDM) group, reference signal group, CORESET group), CORESET pool, CORESET subset, CW, redundancy version (RV), layer (MIMO layer, transmission layer, spatial layer) may be read interchangeably with each other. Also, panel Identifier (ID) and panel may be read interchangeably with each other. In the present disclosure, TRP index, TRP ID, CORESET pool index, ordinal numbers (first, second) of TCI states in two TCI states, TRP may be read interchangeably with each other.

[0155] In the present disclosure, one of the two TCI states associated with one code point of a TRP, a transmission point, a panel, a DMRS port group, a CORESET pool, or a TCI field may be read as the other.

[0156] In the present disclosure, single TRP, single TRP system, single TRP transmission, and single PDSCH may be read as each other. In the present disclosure, multi-TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be read as each other. In the present disclosure, single DCI, single PDCCH, multi-TRP based on single DCI, and activation of two TCI states on at least one TCI code point may be read as each other.

[0157] In the present disclosure, single TRP, a channel using single TRP, a channel using one TCI state / spatial relation, non-activation of multi-TRP by RRC / DCI, non-activation of multiple TCI states / spatial relations by RRC / DCI, no setting of one CORESET pool index (CORESETPoolIndex) value for any CORESET, and no mapping of any code point of the TCI field to two TCI states may be read as each other.

[0158] In the present disclosure, multi-TRP, a channel using multi-TRP, a channel using multiple TCI states / spatial relations, activation of multi-TRP by RRC / DCI, activation of multiple TCI states / spatial relations by RRC / DCI, and at least one of multi-TRP based on single DCI and multi-TRP based on multi-DCI may be read as each other.

[0159] In the present disclosure, multi-TRP based on multi-DCI, multi-TRP based on multi-DCI, a CORESET pool index (CORESETPoolIndex) value of 1 being set for a CORESET, a CORESET pool index being set for one or more CORESETs, and different CORESET pool indices = 0 or 1 being set for a CORESET may be mutually interchangeable.

[0160] In the present disclosure, multi-TRP based on single-DCI, multi-TRP based on single-DCI, at least one code point of a TCI field being mapped to two TCI states, a CORESET pool index not being set for a CORESET, and the same CORESET pool index being set for all CORESETs may be mutually interchangeable.

[0161] In the present disclosure, TRP1 (first TRP) may correspond to a CORESET pool index = 0 or may correspond to a first TCI state among two TCI states corresponding to one code point of a TCI field. TRP2 (second TRP) may correspond to a CORESET pool index = 1 or may correspond to a second TCI state among two TCI states corresponding to one code point of a TCI field.

[0162] In the present disclosure, the CC list, the serving cell list, the CC list in the cell group configuration (CellGroupConfig), the applicable list, the simultaneous TCI update list / the second simultaneous TCI update list, simultaneousTCI-UpdateList1-r16 / simultaneousTCI-UpdateList2-r16, the simultaneous TCI cell list, simultaneousTCI-CellList, the simultaneous spatial update list / the second simultaneous spatial update list, simultaneousSpatial-UpdatedList1-r16 / simultaneousSpatial-UpdatedList2-r16, the set CC, the set list, the BWP / CC in the set list, all the BWP / CC in the set list, the CC indicated by the activation command, the indicated CC, the CC that received the MAC CE, the information indicating a plurality of cells for at least one update of the TCI state and the spatial relationship may be read interchangeably with each other.

[0163] (Wireless communication method) In the present disclosure, the joint beam indication, the common beam indication, the beam indication for UL and DL may be read interchangeably with each other.

[0164] In the present disclosure, the separate beam indication, the common beam indication for UL or DL, the beam indication for UL or DL, the UL beam indication, the DL beam indication may be read interchangeably with each other.

[0165] The UE may receive information (RRC information element / MAC CE) indicating a plurality of TCI states, and receive DCI (beam indication DCI, existing DCI format) indicating one scheduling of PDSCH and PUSCH and one or more of the plurality of TCI states.

[0166] The UE may receive information (RRC information element / MAC CE) indicating a plurality of TCI states, and receive a DCI (beam indication DCI, new DCI format) that indicates one or more of the plurality of TCI states and does not indicate scheduling of either PDSCH or PUSCH.

[0167] The UE may receive information (RRC information element / MAC CE) indicating a plurality of TCI states, and receive a DCI (beam indication DCI, new DCI format) that includes at least one field of one or more of the plurality of TCI states, a serving cell index, a HARQ timing indicator (PDSCH-to-HARQ_timing indicator), DAI, TDRA, and PRI.

[0168] The UE may apply the one or more TCI states to multiple types (UL / DL) of signals (channels / RSs).

[0169] <First Embodiment> In Case 1 / 2 / 3, at least one of a DCI (format / field) for common beam indication and HARQ-ACK information for the DCI may be defined (e.g., FIG. 6).

[0170] In Case 1 / 2, the existing TCI field in DCI format 1_1 / 1_2 may indicate a common beam. In Case 1, the existing TCI field in DCI format 1_1 / 1_2 may indicate a common beam for both UL and DL. In Case 2, the existing TCI field in DCI format 1_1 / 1_2 may indicate a common beam for DL only.

[0171] In case 1 / 2, the HARQ-ACK information (ACK / NACK) for the PDSCH scheduled by the beam indication DCI may be the ACK for the common beam indication. In case 1, the HARQ-ACK information for the PDSCH scheduled by the beam indication DCI may be the ACK for the common beam indication for both UL and DL. In case 2, the HARQ-ACK information for the PDSCH scheduled by the beam indication DCI may be the ACK for the common beam indication for DL only.

[0172] The DCI field / DCI format for the separate beam indication for UL only (case 3) may be any of the following options (Alt.) 1-1 to 1-3. [[Option 1-1]]New DCI format. A new DCI format for beam indication without data scheduling is beneficial. It is preferable not to increase the number of blind detections (BD), for example, the new DCI format has the same DCI payload as one of the existing DCI formats. [[Option 1-2]]New DCI field within DCI format 1_1 / 1_2. For beam indication for UL only, the base station may send a DL DCI including a DL grant and a TCI field for DL only. [[Option 1-3]]New DCI field or existing DCI field (e.g., SRI field) within DCI format 0_1 / 0_2.

[0173] The ACK for the separate beam indication for UL only (case 3) may follow any of the following options 2-1 to 2-3. [[Option 2-1]]The mechanism of HARQ for DCI reception (e.g., SPS PDSCH release (DCI / PDCCH)). If the UE receives a beam indication DCI, the UE may generate one HARQ-ACK information bit even if it does not receive the PDSCH (the PDSCH is not scheduled by the beam indication DCI). In this way, if the UE receives a beam indication DCI, in order to avoid a mismatch in the common TCI state between the base station and the UE, it is preferable for the UE to feedback an ACK. [[Option 2-2]]The HARQ-ACK information (ACK / NACK) of the PDSCH scheduled by that DCI. [[Option 2-3]]At least one of the following a, b, and c. a) PUSCH transmission. The PUSCH transmission is recognized as an ACK for the beam indication. b) ACK transmission for the UL grant DCI. The ACK transmission may be introduced. c) DCI reception corresponding to the ACK of the PUSCH.

[0174] The common beam indication may follow the following Aspect 1-1.

[0175] 《Aspect 1-1》 In Case 1 / 2, the TCI field in DCI format 1_1 / 1_2 may be used for the common beam indication. The operation when there is no transmitted DL data is not clear.

[0176] For the DL beam indication (Option 1-2 in Case 1 / 2 or Case 3), either of the following Options 1 and 2 may be applicable.

[0177] [Option 1] Beam indications without DL data are not assumed. The common beam may be indicated with a DL assignment. The UE may assume that the beam indication DCI (e.g., DCI format 1_1 / 1_2 or a new DCI format) always comes with DL data (DL assignment). If there is no DL data, the base station may schedule dummy DL data, and the UE may send HARQ-ACK information for the reception of that dummy DL data.

[0178] [Option 2] If there is no DL data, a common beam indication may be sent. The UE may receive a beam indication DCI (e.g., DCI format 1_1 / 1_2 or a new DCI format) without DL data (DL assignment). If there is no DL data, the base station may indicate only the beam indication information, and the UE may send HARQ-ACK information for the reception of that DCI (similar to SPS PDSCH release). This is more efficient than Option 1.

[0179] For UL beam indications (Options 1 - 3 in Case 3), either of the following Options 1 and 2 may apply.

[0180] [Option 1] Beam indications without UL data are not assumed. The common beam may be indicated with a UL grant. The UE may assume that the beam indication DCI (e.g., DCI format 1_1 / 1_2 or a new DCI format or UL DCI) always comes with UL data (UL grant). If there is no UL data, the base station may schedule dummy UL data, and the UE may send that dummy UL data.

[0181] [Option 2] If there is no UL data, a common beam indication may be transmitted. The UE may receive a beam indication DCI (e.g., DCI format 1_1 / 1_2 or a new DCI format or UL DCI) without UL data (UL assignment). If there is no UL data, the base station indicates only the beam indication information, and the UE may send HARQ-ACK information for the reception of that DCI (similar to the SPS PDSCH release). This is more efficient than Option 1.

[0182] According to this embodiment, a common beam indication for UL / DL can be appropriately performed.

[0183] <Second Embodiment> Option 1-1 of the first embodiment uses a new DCI format in Case 3. The new DCI format will be described later.

[0184] By reusing the existing TCI field in DCI format 1_1 / 1_2, Option 1 of the first embodiment may be used for DL beam indication and UL beam indication.

[0185] In the DL-only beam indication in the separate beam indications for DL and UL, if it is assumed that the common beam is applied only to the PDSCH, it is reasonable not to consider the case without DL data. However, in the scenario of a common beam for DL and UL, when the common beam is applied to the PDSCH and PUSCH, it cannot be said that it is reasonable not to consider the case without DL data (e.g., there is PUSCH data and the base station tries to update the common beam and there is no DL data). If a new DCI format is introduced for the UL-only beam indication in the separate beam indications for DL and UL, it is preferably used in other scenarios as well.

[0186] In Case 1 / 2 / 3, at least one of the DCI for the common beam indication and the HARQ-ACK information for that DCI may be defined (e.g., FIG. 7).

[0187] In case 1 / 2, an existing TCI field in at least one of DCI format 1_1 / 1_2 and the new DCI format may indicate a common beam. In case 1, an existing TCI field in at least one of DCI format 1_1 / 1_2 and the new DCI format may indicate a common beam for both UL and DL. In case 2, an existing TCI field in at least one of DCI format 1_1 / 1_2 and the new DCI format may indicate a common beam for DL only. In case 2, an existing TCI field in DCI format 1_1 / 1_2 may indicate a common beam for DL only.

[0188] In case 1 / 2, at least one of the HARQ-ACK information (ACK / NACK) for the PDSCH scheduled by the beam indication DCI and the HARQ mechanism for the reception of the new DCI format (e.g., a mechanism similar to SPS PDSCH release) may be an ACK for the common beam indication. In case 1, at least one of the HARQ-ACK information for the PDSCH scheduled by the beam indication DCI and the HARQ mechanism for the reception of the new DCI format (e.g., a mechanism similar to PDSCH SPS release) may be an ACK for the common beam indication for both UL and DL. In case 2, at least one of the HARQ-ACK information for the PDSCH scheduled by the beam indication DCI and the HARQ mechanism for the reception of the new DCI format (e.g., a mechanism similar to SPS PDSCH release) may be an ACK for the common beam indication for DL only. In case 2, the HARQ-ACK information for the PDSCH scheduled by the beam indication DCI may be an ACK for the common beam indication for DL only.

[0189] The DCI field / DCI format for separate beam indication (case 3) for UL only may be any of the following options 1-1 to 1-3. [[Option 1-1]]A new DCI format. A new DCI format for beam indication without data scheduling is beneficial. It is preferable that the number of blind detections (BD) is not increased, for example, the new DCI format has the same DCI payload as one of the existing DCI formats. [[Option 1-2]]A new DCI field within DCI format 1_1 / 1_2. For UL-only beam indication, the base station may send a DL DCI including a DL grant and a DL-only TCI field. [[Option 1-3]]A new DCI field or an existing DCI field (e.g., SRI field) within DCI format 0_1 / 0_2.

[0190] The ACK for separate beam indication (case 3) for UL only may follow any of the following options 2-1 to 2-3. [[Option 2-1]]The HARQ mechanism for DCI reception (e.g., SPS PDSCH release (DCI / PDCCH)). If the UE receives a beam indication DCI, the UE may generate one HARQ-ACK information bit even if the UE does not receive a PDSCH (the PDSCH is not scheduled by the beam indication DCI). Thus, if the UE receives a beam indication DCI, it is preferable for the UE to feedback an ACK to avoid a common TCI state mismatch between the base station and the UE. [[Option 2-2]]The HARQ-ACK information (ACK / NACK) of the PDSCH scheduled by that DCI. [[Option 2-3]]At least one of the following a, b, and c. a) PUSCH transmission. The PUSCH transmission is recognized as an ACK for the beam indication. b) ACK transmission for the UL grant DCI. The ACK transmission may be introduced. c) Reception of DCI corresponding to the ACK of PUSCH.

[0191] If a new DCI format is introduced, the common UL / DL beam indication and the DL-only separate UL / DL beam indication are useful. Whether the UE monitors the new DCI format in addition to the TCI state of DCI format 1_1 / 1_2 may depend on the upper layer configuration. The new DCI format may be a beam (TCI) indication without (UL / DL) data scheduling.

[0192] If a new DCI format for beam indication is configured, the UE may only be required to monitor the new DCI format.

[0193] If the number of blind detections does not increase for the new DCI format (for example, if the new DCI format has the same DCI size as one of the existing DCI formats), since there is no disadvantage in monitoring the new DCI format, the UE may always monitor the new DCI format for cases 1 / 2 / 3.

[0194] If the number of blind detections increases for the new DCI format (for example, if the new DCI format has a different DCI size from one of the existing DCI formats), since monitoring the new DCI format increases the complexity of the UE, it is preferable that it can be set whether the new DCI format is used for the common beam indication.

[0195] If the UE is configured to monitor a new DCI format, at least one of the existing TCI fields of DCI format 1_1 / 1_2 and the new DCI format may indicate a common beam, or the UE may assume that only the new DCI format indicates a common beam, and at least one of the HARQ-ACK information (ACK / NACK) of the PDSCH scheduled by the beam-indicating DCI and the HARQ mechanism for DCI reception (e.g., SPS PDSCH release) may be an ACK for the common beam indication.

[0196] If the UE is not configured to monitor a new DCI format, the existing TCI field of DCI format 1_1 / 1_2 may indicate a common beam, and the HARQ-ACK information (ACK / NACK) of the PDSCH scheduled by the beam-indicating DCI may be an ACK for the common beam indication.

[0197] Whether the UE supports the reception of the new DCI format may depend on the UE capabilities.

[0198] <<Modification Example>> DL assignment DCI (DCI format 1_1 / 1_2) that does not perform DL data scheduling may be allowed. The UE may transmit HARQ-ACK information indicating successful reception (ACK) of the beam-indicating DCI (DCI format 1_1 / 1_2) in the same manner as the HARQ-ACK information for the SPS PDSCH release (described in the "SPS PDSCH" above).

[0199] For example, as shown in FIG. 8, the beam-indicating DCI may perform DL data (PDSCH) scheduling or may not perform DL data scheduling.

[0200] The DCI (joint beam indication, case 1) that indicates a common beam for both UL and DL is the DL assignment DCI (DCI format 1_1 / 1_2), and PDSCH scheduling may be performed. The ACK (successful reception of beam indication) for this beam indication may be the HARQ-ACK (ACK / NACK) for that PDSCH.

[0201] The DCI (separate beam indication, case 2) that indicates a common beam for DL only is the DL assignment DCI (DCI format 1_1 / 1_2), and PDSCH scheduling may be performed. The ACK (successful reception of beam indication) for this beam indication may be the HARQ-ACK (ACK / NACK) for that PDSCH.

[0202] The DCI (joint beam indication, case 1) that indicates a common beam for both UL and DL may be a new DCI format that does not perform PDSCH scheduling. The ACK (successful reception of beam indication) for this beam indication may be the HARQ-ACK information directly transmitted for that DCI, similar to the HARQ-ACK information for SPS PDSCH release.

[0203] The DCI (separate beam indication, case 2) that indicates a common beam for DL only may be a new DCI format that does not perform PDSCH scheduling. The ACK (successful reception of beam indication) for this beam indication may be the HARQ-ACK information directly transmitted for that DCI, similar to the HARQ-ACK information for SPS PDSCH release.

[0204] For the common beam for UL only, the DCI field / DCI format for DCI (separate beam indication, case 3) may be any of the aforementioned options 1-1 to 1-3. For example, this DCI may be a new DCI format that does not perform PDSCH scheduling (option 1-1). The ACK for this beam indication may follow any of the aforementioned options 2-1 to 2-3. For example, this ACK (successful reception of the beam indication) may be HARQ-ACK information directly transmitted for that DCI, similar to the HARQ-ACK information for SPS PDSCH release (option 2-1).

[0205] According to this embodiment, the common beam indication for UL / DL can be appropriately performed.

[0206] <The Third Embodiment> In case 1 / 2 / 3, the new DCI format indicates the beam.

[0207] In case 1 / 3, the new DCI format may have one TCI field (for example, for DL beam only or for common beam of UL and DL).

[0208] In case 2, the new DCI format may have another one TCI field (for example, for UL beam of separate beam indication only).

[0209] When the UE assumes case 2 in addition to case 1 / 3, two TCI fields, one for DL only / common use and one for UL only, may be assumed.

[0210] In the case of indicating a common beam for multiple CCs (multi-CC case), at least one of the following options 1 and 2 may be applied.

[0211] [Option 1] One or two TCI fields within the new DCI format are applied to the CCs within the CC list configured by RRC.

[0212] [Option 2] The new DCI field includes an indication for multiple CCs. The DCI may include one or two TCI fields for each CC. The DCI may or may not be accompanied by a serving cell index. If the DCI is accompanied by a serving cell index, a common beam for different CCs may be indicated by the DCI. If the DCI is not accompanied by a serving cell index, different positions of one or two TCI fields may correspond to different serving cells in ascending order within the CC list. In this case, a special value may be set for the one or two TCI fields for the CCs for which the common beam is not updated.

[0213] The new DCI field may be a DCI dedicated to beam indication (without scheduling / triggering of UL / DL data, SRS, CSI-RS, CSI reporting). The new DCI field may have fields for at least one of UL / DL data, SRS, CSI-RS, CSI reporting, scheduling / triggering. It may not be a DCI dedicated to beam indication.

[0214] The new DCI format may follow at least one of the following Aspects 3-1 to 3-2.

[0215] 《Aspect 3-1》 For the new DCI format, the number of blind detections does not increase. The new DCI format may have the same DCI size as one of the existing DCI formats.

[0216] The new DCI format may be designed to have the same payload size as 1 of the existing DCI formats for UE-specific DCI. As a result, the number of blind detections may not increase.

[0217] For example, if a new DCI format has the same payload size as DCI format 1_1 and a search space set is configured for monitoring these two DCI formats, the number of blind detections is the same as the case where a search space set is configured for monitoring only DCI format 1_1.

[0218] In this case, if a C-RNTI is used for two DCI formats, the problem is how the UE distinguishes between these two DCI formats having the same payload size.

[0219] How the UE distinguishes the new DCI format may follow at least one of the following distinguishing methods A and B.

[0220] [Distinguishing Method A] An RNTI (new RNTI, for example, beam indication RNTI) used for CRC scrambling of the new DCI format may be configured. If the UE is configured to monitor the new DCI format, the UE may attempt blind detection of the new DCI format having a CRC scrambled by the new RNTI.

[0221] In the example of FIG. 9, the payload size of the new DCI format for beam indication is equal to the payload size of the existing DCI format. The RNTI (for example, beam indication RNTI) that scrambles the CRC of the new DCI format is different from the RNTI (for example, C-RNTI) that scrambles the CRC of the existing DCI format.

[0222] [Distinguishing Method B] If a new DCI format / new DCI field is configured, a new DCI field for indicating an existing DCI format or the new DCI format is inserted into the existing DCI format. If the UE is configured to monitor a new DCI format and the UE is indicated of the new DCI format by the new DCI field, a common beam may be indicated by the new DCI format. The RNTI that scrambles the CRC of the new DCI format may be the same as the RNTI (e.g., C-RNTI) that scrambles the CRC of the existing DCI format, or may be a different RNTI (e.g., a new RNTI, a beam indication RNTI).

[0223] In the example of FIG. 10, the payload size of the new DCI format for beam indication is equal to the payload size of the existing DCI format. Each of the existing DCI format and the new DCI format has an indicator field. The value of the indicator field in the existing DCI format is 0. The value of the indicator field in the new DCI format is 1.

[0224] 《Aspect 3-2》 For the new DCI format, the number of blind detections increases. The new DCI format may have a DCI size different from one of the existing DCI formats.

[0225] If the UE is configured to monitor a new DCI format, the UE may attempt blind detection of the new DCI format having a CRC scrambled by an existing RNTI (e.g., C-RNTI) using the (configured / specified in the specification) payload size of the new DCI format.

[0226] The payload size (number of bits) of the new DCI format may be settable according to the upper layer configuration. Any of the payload sizes of the new DCI format may be different from any of the payload sizes of the existing DCI format. In this case, a new RNTI may not be necessary. If the payload size of the new DCI format is the same as any of the payload sizes of the existing DCI format, a new RNTI for distinguishing the DCI format may be required.

[0227] In the example of FIG. 11, the payload size of the new DCI format for beam indication is different from the payload size of the existing DCI format. The RNTI that scrambles the CRC of the new DCI format may be the same as the RNTI (e.g., C-RNTI) that scrambles the CRC of the existing DCI format, or may be a different RNTI (e.g., a new RNTI, which may be a beam indication RNTI).

[0228] The payload size (number of bits) of the new DCI format may be settable / scalable for at least one of the following states 1 and 2. [State 1] Whether the TCI field is for DL only / common to UL and DL, or for UL only. [State 2] Whether one DCI indicates one set of TCI states (for UL and DL) for a single TRP, or one DCI indicates multiple sets of TCI states (for UL and DL) for a multi-TRP.

[0229] According to this embodiment, the UE can appropriately receive a common beam indication by the new DCI format.

[0230] <Fourth Embodiment> In the third embodiment, when a new DCI format having the same payload size as an existing DCI format is transmitted without including DL assignment, it is not clear which DCI fields are required in addition to the TCI field in order to enable HARQ-ACK feedback.

[0231] The new DCI format for common beam indication can follow the HARQ-ACK procedure for SPS PDSCH. However, considering some differences between the new DCI format and the SPS PDSCH release, it is conceivable to introduce some extensions.

[0232] As described in the above-mentioned "SPS PDSCH", for the type 1 HARQ-ACK codebook, the HARQ-ACK information for the separate release DCI / joint release DCI of SPS PDSCH is related to the TDRA index in the activation DCI (for the lowest SPS configuration index) (example in Fig. 12A). However, there is no activation DCI for the new DCI format for common beam indication. Also, in the new DCI format, it is not clear which fields are required to facilitate the HARQ-ACK procedure.

[0233] For the type 1 HARQ-ACK codebook, when the HARQ-ACK feedback for the new DCI format and the HARQ-ACK feedback for the dynamically scheduled PDSCH are multiplexed (mapped) on one PUCCH, the HARQ-ACK bit position for the new DCI format may be derived based on the row index of the TDRA table and the K1 value. The HARQ-ACK procedure may be the same as that for the SPS PDSCH release by using these two values.

[0234] The K1 (PDSCH-to-HARQ_feedback timing indicator) value may be indicated by the new DCI format (example in Fig. 12B).

[0235] The row index of the TDRA table may be determined by at least one of the following Options 1 to 3. [Option 1] The row index of the TDRA table is indicated within the new DCI format (TDRA field) (example in Figure 12B). [Option 2] The row index of the TDRA table is set by RRC. [Option 3] The default value of the row index of the TDRA table is defined by the specification. For example, the default value may be the lowest or highest index / row index / code point.

[0236] In Option 1, the new DCI format includes a TDRA field. In Option 2 or 3, the new DCI format may not include a TDRA field.

[0237] According to this embodiment, when using the type 1 HARQ-ACK codebook, the UE can appropriately report HARQ-ACK information for the new DCI format.

[0238] <Fifth Embodiment> As described in the foregoing "SPS PDSCH", for the type 2 HARQ-ACK codebook, the HARQ-ACK information for the release DCI of the SPS PDSCH is related to DAI and K1 within the activation DCI / release DCI (example in Figure 13A).

[0239] For the type 2 HARQ-ACK codebook, when the HARQ-ACK feedback for a new DCI format and the HARQ-ACK feedback for a dynamically scheduled PDSCH are multiplexed (mapped) onto one PUCCH, the HARQ-ACK bit order for the new DCI format may be derived based on the DAI and K1 values indicated within the new DCI format (example in Figure 13B). The HARQ-ACK procedure may be similar to the SPS PDSCH release by using these two values.

[0240] For the type 2 HARQ-ACK codebook, the new DCI format may include a DAI field and a K1 (PDSCH-to-HARQ_feedback timing indicator) field.

[0241] According to this embodiment, when using the type 2 HARQ-ACK codebook, the UE can appropriately report the HARQ-ACK information for the new DCI format.

[0242] <Sixth Embodiment> It is assumed that the UE provides HARQ-ACK information X symbols after the last symbol of the PDCCH that provides the common beam indication, in response to the new DCI format for the common beam indication (example in Figure 14). X may be the same as N for the SPS PDSCH release. As a UE capability different from the SPS PDSCH release, the value of X may be reported. A value of X different from the value of N for the SPS PDSCH release may be applied to the new DCI format.

[0243] According to this embodiment, the UE can appropriately report the HARQ-ACK information for the new DCI format.

[0244] <Seventh Embodiment> The new DCI format includes a PUCCH resource indicator (PRI) field. The UE may determine the PUCCH resources for transmitting HARQ-ACK information for the new DCI format according to the aforementioned "PUCCH resource determination".

[0245] At least one of the PRI in the new DCI format, the index of the first CCE corresponding to the PDCCH carrying the new DCI format, and the number of CCEs in the CORESET of the PDCCH may be used to indicate the PUCCH resources carrying HARQ-ACK for the new DCI format for beam indication.

[0246] After RRC connection (when the UE is provided with individual PUCCH resource settings), the UE may follow the following Steps 1 and 2 (or may follow the aforementioned "PUCCH resource determination") for transmitting HARQ-ACK information for the new DCI format.

[0247] [Step 1] The UE determines one PUCCH resource set from a plurality of configured PUCCH resource sets based on the HARQ-ACK payload.

[0248] [Step 2] The UE determines one PUCCH resource from a plurality of configured PUCCH resources within the selected PUCCH resource set.

[0249] For PUCCH resource set 0 (the first PUCCH resource set, when M is more than 8), the UE may determine one PUCCH resource within the PUCCH resource set based on the PRI, the index of the first CCE, and the number of CCEs.

[0250] For PUCCH resource sets 1 to 3 (the second to fourth PUCCH resource sets), the UE may determine one PUCCH resource within the PUCCH resource set based on the PRI.

[0251] According to this embodiment, the UE can appropriately determine a PUCCH resource for transmitting HARQ-ACK information for a new DCI format.

[0252] <Eighth Embodiment> The new DCI format for common beam indication in at least one of the first to seventh embodiments may include at least one of the following fields. · One or two TCI states. Or, one or two TCI states for each serving cell (CC). · Serving cell (CC) index. · K1 (PDSCH-to-HARQ_feedback timing indicator). · DAI. · TDRA. · PRI.

[0253] According to this embodiment, the UE can appropriately report HARQ-ACK information for a new DCI format.

[0254] <Ninth Embodiment> Higher layer parameters (RRC information elements) / UE capabilities corresponding to at least one function (feature) in the first to eighth embodiments may be defined. The UE capability may indicate that it supports this function.

[0255] A UE with higher layer parameters corresponding to that function set may perform that function. It may be defined that "a UE without higher layer parameters corresponding to that function does not perform that function".

[0256] A UE that reports a UE capability indicating that it supports that function may perform that function. It may be defined that "a UE that does not report a UE capability indicating that it supports that function does not perform that function".

[0257] If the UE reports UE capabilities indicating that it supports the function and the upper layer parameters corresponding to the function are set, the UE may perform the function. It may be specified that "if the UE does not report UE capabilities indicating that it supports the function or the upper layer parameters corresponding to the function are not set, the UE shall not perform the function".

[0258] The function may be a common beam indication / separate beam indication.

[0259] The UE capabilities may indicate the number (maximum number) of TCI states set by RRC for common beam indication that the UE supports. The TCI state may include at least one of the TCI state for common beam indication, the UL TCI state for separate beam indication, and the DL TCI state for separate beam indication.

[0260] The UE capabilities may indicate the number (maximum number) of active TCI states for common beam indication that the UE supports. The TCI state may include at least one of the TCI state for common beam indication, the UL TCI state for separate beam indication, and the DL TCI state for separate beam indication.

[0261] The UE capabilities may indicate whether different (separate) active TCI state pools for UL and DL are supported or whether a joint / same TCI pool for UL and DL is supported.

[0262] The UE capabilities may indicate whether the UE supports receiving a new DCI format (second embodiment).

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

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

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

[0266] Further, the wireless communication system 1 may support dual connectivity (multi-RAT dual connectivity (MR-DC)) between a plurality of Radio Access Technologies (RATs). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

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

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

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

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

[0271] 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 higher than 24 GHz (above-24 GHz). Note that the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.

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

[0273] The plurality of base stations 10 may be connected by wire (e.g., an optical fiber compliant with Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, the base station 11 corresponding to the upper-level station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

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

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

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

[0277] The wireless access method may be referred to as a waveform. Note that in the wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the wireless access methods of the UL and the DL.

[0278] In the wireless communication system 1, as downlink channels, a physical downlink shared channel (PDSCH) shared by each user terminal 20, a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc. may be used.

[0279] Also, in the wireless communication system 1, as uplink channels, a physical uplink shared channel (PUSCH) shared by each user terminal 20, a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc. may be used.

[0280] The PDSCH is used to transmit user data, upper layer control information, System Information Block (SIB), etc. The PUSCH may be used to transmit user data, upper layer control information, etc. Also, the PBCH may be used to transmit the Master Information Block (MIB).

[0281] The PDCCH may be used to transmit lower layer control information. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.

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

[0283] For the detection of the PDCCH, a control resource set (COntrol REsource SET (CORESET)) and a search space may be used. The CORESET corresponds to the resource for searching for DCI. The search space corresponds to the search area and search method for PDCCH candidates (PDCCH candidates). One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0284] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the "search space", "search space set", "search space configuration", "search space set configuration", "CORESET", "CORESET configuration", etc. in the present disclosure may be read interchangeably with each other.

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

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

[0287] In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), etc. may be transmitted.

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

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

[0290] (Base station) FIG. 16 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transmission / reception unit 120, a transmission / reception antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140 may be provided.

[0291] In this example, the functional blocks of the characteristic parts in 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. A part of the processing of each unit described below may be omitted.

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

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

[0294] The transmission / reception unit 120 may include a baseband unit 121, a Radio Frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmission / reception unit 120 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

[0295] The transmitting and receiving unit 120 may be configured as an integrated transmitting and 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.

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

[0297] The transmitting and receiving unit 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

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

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

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

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

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

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

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

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

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

[0307] The transmission / reception unit 120 may transmit information indicating a plurality of transmission configuration indication (TCI) states, and may transmit downlink control information indicating one of the one or more TCI states among the plurality of TCI states and scheduling of one of the physical downlink shared channel and the physical uplink shared channel. The control unit 110 may apply the one or more TCI states to a plurality of types of signals.

[0308] It may transmit information indicating a plurality of transmission configuration indication (TCI) states, indicate one or more of the plurality of TCI states, and transmit downlink control information that does not indicate scheduling of either a physical downlink shared channel or a physical uplink shared channel. The control unit 110 may apply the one or more TCI states to a plurality of types of signals.

[0309] It may transmit information indicating a plurality of transmission configuration indication (TCI) states, indicate one or more of the plurality of TCI states, and transmit downlink control information that does not indicate scheduling of either a physical downlink shared channel or a physical uplink shared channel. The control unit 110 controls reception of hybrid automatic repeat request acknowledgement (HARQ-ACK) information for the downlink control information, and the control unit 110 may apply the one or more TCI states to a plurality of types of signals.

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

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

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

[0313] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission, 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.

[0314] 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 composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc. described based on the common understanding in the technical field related to the present disclosure.

[0315] The transceiver unit 220 may be configured as an integrated transceiver unit or may be composed of a transmitter unit and a receiver unit. The transmitter unit may be composed of the transmission processing unit 2211 and the RF unit 222. The receiver unit may be composed of the reception processing unit 2212, the RF unit 222, and the measurement unit 223.

[0316] The transceiver antenna 230 may be composed of an antenna described based on the common understanding in the technical field related to the present disclosure, such as an array antenna.

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

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

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

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

[0321] Note that whether to apply DFT processing may be based on the setting of transform precoding. For a certain channel (e.g., PUSCH), when transform precoding is enabled, the transmission / reception unit 220 (transmission processing unit 2211) may perform DFT processing as the above transmission processing to transmit the channel using the DFT-s-OFDM waveform, or if not, it may not perform DFT processing as the above transmission processing.

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

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

[0324] The transmission / reception unit 220 (reception processing unit 2212) may perform 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 on the acquired baseband signal, and may acquire user data and the like.

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

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

[0327] The transmission / reception unit 220 may receive information indicating a plurality of transmission configuration indication (TCI) states, and receive downlink control information indicating one or more of the TCI states among the plurality of TCI states and scheduling of one of the physical downlink shared channel and the physical uplink shared channel. The control unit 210 may apply the one or more TCI states to a plurality of types of signals (first embodiment).

[0328] The downlink control information may indicate scheduling of the physical downlink shared channel. The plurality of types of signals may include downlink signals and uplink signals.

[0329] The downlink control information may indicate scheduling of the physical downlink shared channel. Each of the plurality of types of signals may be a downlink signal.

[0330] The downlink control information may indicate the scheduling of the physical uplink shared channel. Each of the plurality of types of signals may be an uplink signal.

[0331] The transceiver unit 220 may receive information indicating a plurality of transmission configuration indication (TCI) states, indicate one or more TCI states among the plurality of TCI states, and receive downlink control information that does not indicate the scheduling of either the physical downlink shared channel or the physical uplink shared channel. The control unit 210 may apply the one or more TCI states to a plurality of types of signals (Second Embodiment, Third Embodiment).

[0332] The control unit 210 may report hybrid automatic repeat request acknowledgement (HARQ-ACK) information for the downlink control information.

[0333] The payload size of the format of the downlink control information may be equal to the payload size of a downlink control information format different from the format.

[0334] The radio network temporary identifier (RNTI) that scrambles the cyclic redundancy check (CRC) of the downlink control information may be different from the RNTI that scrambles the CRC of a downlink control information format different from the format of the downlink control information.

[0335] The transmission / reception unit 220 may receive information indicating a plurality of transmission configuration indication (TCI) states, and receive downlink control information including at least one field of one or more of the plurality of TCI states, a serving cell index, a HARQ timing indicator, a downlink assignment index, a time domain resource allocation, and a physical uplink control channel resource indicator. The control unit 210 may apply the one or more TCI states to a plurality of types of signals.

[0336] The control unit 210 may report hybrid automatic repeat request acknowledgement (HARQ-ACK) information for the downlink control information.

[0337] When the control unit 210 maps the HARQ-ACK information and the second HARQ-ACK information for the dynamically scheduled physical downlink shared channel to one physical uplink control channel, it may determine the bit position of the HARQ-ACK information based on at least one of the HARQ timing indicator, the downlink assignment index, and the time domain resource allocation.

[0338] The control unit 210 may apply the one or more TCI states to a plurality of types of signals after a certain number of symbols from the last symbol of the downlink control information.

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

[0340] Here, functions include, but are not limited to, judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, regarded as, notification (broadcasting), notification (notifying), communication (communicating), forwarding, configuration (configuring), reconfiguration (reconfiguring), allocation (allocating, mapping), assignment (assigning), etc. For example, a functional block (component) that functions to transmit may be referred to as a transmitting unit, a transmitter, etc. In any case, as described above, the realization method is not particularly limited.

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

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

[0343] For example, although only one processor 1001 is illustrated, there may be a plurality of processors. Also, the processing may be executed by one processor, or the processing may be executed by two or more processors simultaneously, sequentially, or using other methods. Note that the processor 1001 may be implemented by one or more chips.

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

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

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

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

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

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

[0350] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives an external input. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs an output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (e.g., a touch panel).

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

[0352] In addition, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), and a Field Programmable Gate Array (FPGA), and some or all of the functional blocks may be implemented using the hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

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

[0354] The radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting the radio frame may be called a subframe. Further, the subframe may be composed of one or more slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) that does not depend on numerology.

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

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

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

[0358] A radio frame, sub-frame, slot, mini-slot, and symbol all represent time units for signal transmission. A radio frame, sub-frame, slot, mini-slot, and symbol may each be used with another corresponding name. Note that the time units such as frames, sub-frames, slots, mini-slots, and symbols in this disclosure may be read interchangeably with each other.

[0359] For example, one sub-frame may be called a TTI, or a plurality of consecutive sub-frames may be called a TTI, or one slot or one mini-slot may be called a TTI. That is, at least one of the sub-frame and the TTI may be a sub-frame (1 ms) in the existing LTE, or a period shorter than 1 ms (for example, 1 - 13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc. instead of a sub-frame.

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

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

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

[0363] A TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini-slot, a sub-slot, a slot, etc.

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

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

[0366] Also, an RB may include one or a plurality of symbols in the time domain, and may have a length of one slot, one mini-slot, one subframe, or one TTI. One TTI, one subframe, etc. may each be constituted by one or a plurality of resource blocks.

[0367] Note that one or more RBs may be referred to as Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0368] Also, a resource block may be composed of one or more Resource Elements (REs). For example, 1 RE may be a radio resource region of 1 sub-carrier and 1 symbol.

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

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

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

[0372] Note that the structures such as the above-described radio frames, sub-frames, slots, mini-slots, and symbols are merely examples. For example, the number of sub-frames included in a radio frame, the number of slots per sub-frame or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of sub-carriers included in an RB, and the number of symbols, symbol length, Cyclic Prefix (CP) length, etc. within a TTI can be variously changed.

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

[0374] The names used for parameters, etc. in the present disclosure are not limiting names in any way. Furthermore, mathematical formulas, etc. using these parameters may be different from those explicitly disclosed in the present disclosure. Since various channels (such as PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, the various names assigned to these various channels and information elements are not limiting names in any way.

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

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

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

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

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

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

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

[0382] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether called software, firmware, middleware, microcode, a hardware description language, or by some other name.

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

[0384] The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may mean the devices (e.g., base stations) included in the network.

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

[0386] In the present disclosure, terms such as "Base Station (BS)", "radio base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. The base station may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0387] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each of the smaller areas can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of a base station and a base station subsystem that provides communication services in this coverage.

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

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

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

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

[0392] Similarly, the user terminal in the present disclosure may be replaced by a base station. In this case, the functions of the user terminal 20 described above may be configured as functions of the base station 10.

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

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

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

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

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

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

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

[0400] Also, "determining" may be considered to be "resolving", "selecting", "choosing", "establishing", "comparing", etc. That is, "determining" may be considered to be making any kind of operation.

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

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

[0403] As used in this disclosure, the terms "connected" and "coupled", or any variations thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements 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 "accessed".

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

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

[0406] In the present disclosure, when terms such as "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

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

[0408] As described above, the invention according to the present disclosure has been described in detail. However, it is obvious to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and changed forms without departing from the spirit and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for illustrative purposes and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A transmitting unit that reports a UE capability indicating support for an indication of one or more transmission configuration indication (TCI) states among a plurality of types of uplink (UL) channels and reference signals (RS) applicable to a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), and a Sounding Reference Signal (SRS); A receiving unit that receives information indicating the plurality of TCI states and receives first downlink control information without data scheduling indicating the one or more TCI states; The transmitting unit transmits hybrid automatic repeat request acknowledgement (HARQ-ACK) information for the first downlink control information; The apparatus further includes a control unit that applies the one or more TCI states indicated by one or more TCI fields included in the first downlink control information to the plurality of types of UL channels and RSs in a plurality of Component Carriers (CCs); A terminal, wherein a specific Radio Network Temporary Identifier (RNTI) used for Cyclic Redundancy Check (CRC) scrambling of the first downlink control information indicating the one or more TCI states is different from a C-RNTI used for CRC scrambling of second downlink control information different from the first downlink control information.

2. The terminal according to claim 1, wherein the plurality of CCs are included in a CC list set by Radio Resource Control (RRC).

3. The terminal according to claim 1, wherein the first downlink control information includes a Physical Uplink Control Channel (PUCCH) resource indicator (PRI) field for indicating a PUCCH resource for transmitting the Hybrid Automatic Repeat reQuest acknowledgement (HARQ-ACK) information.

4. Reporting a UE capability indicating support for indicating one or more of a plurality of transmission configuration indication (TCI) states applicable to a plurality of types of uplink (UL) channels and reference signals (RS) including a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), and a Sounding Reference Signal (SRS); Receiving information indicating the plurality of TCI states and receiving first downlink control information without data scheduling indicating the one or more TCI states; Transmitting hybrid automatic repeat request acknowledgement (HARQ-ACK) information for the first downlink control information; Applying the one or more TCI states indicated by one or more TCI fields included in the first downlink control information to the plurality of types of UL channels and RSs in a plurality of Component Carriers (CCs), comprising: A radio communication method of a terminal, wherein a specific Radio Network Temporary Identifier (RNTI) used for Cyclic Redundancy Check (CRC) scrambling of the first downlink control information indicating the one or more TCI states is different from a Cell Radio Network Temporary Identifier (C-RNTI) used for CRC scrambling of a second downlink control information different from the first downlink control information.

5. A receiving unit that receives a UE capability indicating support for an indication of one or more transmission configuration indication (TCI) states among a plurality of types of uplink (UL) channels and reference signals (RS) applicable to Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Sounding Reference Signal (SRS). A transmitting unit that transmits information indicating the plurality of TCI states and transmits first downlink control information without data scheduling indicating the one or more TCI states. The receiving unit receives hybrid automatic repeat request acknowledgement (HARQ-ACK) information for the first downlink control information. The apparatus further includes a control unit that applies the one or more TCI states indicated by one or more TCI fields included in the first downlink control information to the plurality of types of UL channels and RS in a plurality of Component Carriers (CC). A base station, wherein a specific Radio Network Temporary Identifier (RNTI) used for Cyclic Redundancy Check (CRC) scrambling of the first downlink control information indicating the one or more TCI states is different from a C-RNTI used for CRC scrambling of second downlink control information different from the first downlink control information. Claim 6 A system having a terminal and a base station. The terminal includes a transmitting unit that reports UE capabilities indicating support for one or more of a plurality of transmission configuration indication (TCI) states applicable to a plurality of types of uplink (UL) channels and reference signals (RS) including Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Sounding Reference Signal (SRS). a receiving unit that receives information indicating the plurality of TCI states and receives first downlink control information without data scheduling, indicating one or more of the plurality of TCI states; The transmitting unit transmits hybrid automatic repeat request acknowledgement (HARQ-ACK) information for the first downlink control information. The apparatus further includes a control unit that applies the one or more TCI states indicated by one or more TCI fields included in the first downlink control information to a plurality of types of UL channels and RSs in a plurality of Component Carriers (CCs). The base station includes a transmitting unit that transmits information indicating the plurality of TCI states and transmits the first downlink control information. a receiving unit that receives the UE capabilities and receives the HARQ-ACK information. a control unit that applies the one or more TCI states indicated by the one or more TCI fields to the plurality of types of UL channels and RSs. A specific Radio Network Temporary Identifier (RNTI) used for Cyclic Redundancy Check (CRC) scrambling of the first downlink control information indicating the one or more TCI states is different from a C-RNTI used for CRC scrambling of second downlink control information different from the first downlink control information.

Images