Terminal, wireless communication method, and base station

Abstract

One way of the terminal of the present disclosure has: a receiving unit that receives a MAC CE containing information related to activation of a transmission configuration indication (TCI) state of a physical shared channel; and a control unit that, in a case where one physical shared channel is scheduled by a plurality of downlink control channels that support application of different control resource set pool indexes, determines a TCI state corresponding to the physical shared channel based on a field related to the TCI state included in at least one of a plurality of downlink control information respectively transmitted by the plurality of downlink control channels.

Description

Technical Field

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. Background Technology

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of LTE (Third Generation Partnership Project (3GPP) Releases (Rel.) 8, 9).

[0003] The development of successor systems to LTE is also underway (e.g., also known as the 5th generation mobile communication system (5G), 5G+, the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention

[0007] The problem that the invention aims to solve

[0008] In future wireless communication systems (e.g., after Rel.17, after Beyond 5G / 6G), it is envisioned that one or more Transmission / Reception Points (TRPs) (multiple TRPs) will use one or more panels (multiple panels) to perform DL transmission (e.g., PDSCH transmission) to terminals (user terminals, user equipment (UE)).

[0009] In such cases, it is envisioned that repetition (e.g., repetition) be applied to a specific channel (e.g., PDCCH). For example, consider using multiple PDCCHs from multiple panels / TRPs that are repetitively transmitted (e.g., repetition) to control the scheduling of DL transmissions / UL transmissions (e.g., a PDSCH / PUSCH).

[0010] However, in existing systems (e.g., prior to Rel.16), there has been insufficient research on how to use repeatedly transmitted PDCCH / DCI from more than one TRP to control the scheduling of PDSCH / PUSCH.

[0011] Therefore, one of the objectives of this disclosure is to provide a terminal, wireless communication method, and base station that can communicate appropriately even when scheduling is performed using PDCCH / DCI that is repeatedly transmitted from more than one TRP.

[0012] Methods for solving problems

[0013] One aspect of this disclosure relates to a terminal comprising: a receiving unit that receives a MAC CE containing information related to the activation of a Transmission Setting Indication (TCI) state of a Physical Shared Channel; and a control unit that, when a Physical Shared Channel is scheduled through multiple downlink control channels supporting different control resource set pool indices, determines the TCI state corresponding to the Physical Shared Channel based on a field related to the TCI state contained in at least one of multiple downlink control messages transmitted through the multiple downlink control channels respectively.

[0014] The effects of the invention

[0015] According to one method of this disclosure, communication can be properly performed even when scheduling is carried out using PDCCH / DCI that is repeatedly sent from more than one TRP. Attached Figure Description

[0016] Figures 1A-1D This is a diagram illustrating an example of a multi-TRP scenario.

[0017] Figure 2 This is a diagram illustrating an example of repeatedly scheduling PDSCH via PDCCH.

[0018] Figure 3 This is a diagram illustrating an example of a MAC CE utilized during the activation of the TCI state.

[0019] Figure 4 It is a diagram used to illustrate the TCI states applied in the PDSCH that are repeatedly scheduled via PDCCH.

[0020] Figures 5A-5C This is a diagram illustrating an example of the MAC CE involved in the first approach.

[0021] Figures 6A-6C This is a diagram illustrating an example of the MAC CE involved in the second approach.

[0022] Figure 7A as well as Figure 7B This is a diagram illustrating an example of the mapping between TCI code points and TCI state IDs involved in the second method.

[0023] Figures 8A-8C This is a diagram illustrating an example of a MAC CE involved in the third approach.

[0024] Figure 9A as well as Figure 9B This is a diagram representing another example of the MAC CE involved in variation 1.

[0025] Figure 10 This is a diagram illustrating an example of the TCI state applied in the PDSCH involved in variation 2.

[0026] Figure 11 This is a diagram used to illustrate the scheduling offset between PDCCH and PDSCH.

[0027] Figure 12 This is a diagram used to illustrate the default TCI / QCL applied in the PDSCH involved in the fourth method.

[0028] Figure 13 This is a diagram used to illustrate the default TCI / QCL applied in the PDSCH involved in the fourth method.

[0029] Figure 14 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0030] Figure 15 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0031] Figure 16 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0032] Figure 17 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment. Detailed Implementation

[0033] (Multiple TRPs)

[0034] In NR, research is underway on using one or more Transmission / Reception Points (TRPs) (multiple TRPs) with one or more panels (multiple panels) to perform DL transmissions to the UE. Additionally, research is underway on UL transmissions from the UE to one or more TRPs.

[0035] Furthermore, multiple TRPs can correspond to the same cell identifier (cell Identifier(ID)) or different cell IDs. This cell ID can be either a physical cell ID or a virtual cell ID.

[0036] Figures 1A-1D This diagram illustrates an example of a multi-TRP scenario. In these examples, it is assumed that each TRP can transmit four different beams, but it is not limited to this.

[0037] Figure 1A This represents an example of a scenario where only one TRP (TRP1 in this example) transmits data to the UE in a multi-TRP configuration (also known as single-mode, single TRP, etc.). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

[0038] Figure 1B This is an example of a scenario where only one TRP (TRP1 in this example) in a multi-TRP system sends control signals to the UE, while the other TRPs send data signals (also known as single-master mode). The UE receives each PDSCH sent from the multi-TRP based on a downlink control information (DCI) message.

[0039] Figure 1C This illustrates an example of a scenario where multiple TRPs each send a portion of control signals to the UE, while simultaneously sending data signals (also known as master-slave mode). Alternatively, part 1 of the control signal (DCI) can be sent in TRP1, and part 2 of the control signal (DCI) can be sent in TRP2. Part 2 of the control signal can also depend on part 1. The UE receives each PDSCH sent from the multiple TRPs based on these parts of the DCI.

[0040] Figure 1D This illustrates an example of a scenario where multiple TRPs send different control signals to the UE, while simultaneously transmitting data signals (also known as a multi-master mode). Alternatively, a first control signal (DCI) can be sent in TRP1, and a second control signal (DCI) can be sent in TRP2. The UE receives the PDSCHs transmitted from these multiple TRPs based on these DCIs.

[0041] exist Figure 1B In cases where a single DCI is used to schedule multiple PDSCHs from multiple TRPs (also known as multiple PDSCHs), this DCI can also be called a single DCI (S-DCI, single PDCCH). Furthermore, in Figure 1D In the case of using multiple DCIs to schedule multiple PDSCHs from multiple TRPs separately, these multiple DCIs can also be called multiple DCIs (M-DCI, multiple PDCCH).

[0042] Different code words (CWs) and different layers can also be sent from each TRP of a multi-TRP system. As a method of multi-TRP transmission, non-coherent joint transmission (NCJT) is being studied.

[0043] In NCJT, for example, TRP1 performs modulation mapping on the first codeword and layer mapping, and transmits the first PDSCH using the first precoding on a first number of layers (e.g., 2 layers). Furthermore, TRP2 performs modulation mapping on the second codeword and layer mapping, and transmits the second PDSCH using the second precoding on a second number of layers (e.g., 2 layers).

[0044] Furthermore, multiple PDSCHs (multiple PDSCHs) of NCJT can also be defined as partially or completely overlapping in terms of at least one of the time and frequency domains. In other words, the time and frequency resources of the first PDSCH from the first TRP and the second PDSCH from the second TRP can also overlap.

[0045] It can also be conceived that these first PDSCHs and second PDSCHs are not in a quasi-co-located (QCL) relationship. The reception of multiple PDSCHs can also be replaced by the simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0046] Research is underway on supporting repetition of PDSCH (Transport Block (TB) or Codeword (CW)) across multiple TRPs in URLLC for multiple TRPs. Research is also underway on methods supporting repetition across multiple TRPs in the frequency domain, layer (spatial) domain, or time domain (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4). In scheme 1, multiple PDSCHs from multiple TRPs are spatially multiplexed (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency-division multiplexed (FDM). In scheme 2a, for multiple TRPs, the redundancy version (RV) is the same. In scheme 2b, for multiple TRPs, the RV can be the same or different. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time-division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted within a single time slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different time slots.

[0047] In such a multi-TRP scenario, more flexible transmission control can be implemented by utilizing high-quality channels.

[0048] NCJT using multiple TRPs / panels may require high-ranking operations. To support both ideal and non-ideal backhaul between multiple TRPs, a single DCI (single PDCCH, e.g.) can also be supported. Figure 1B ) and multiple DCI (multiple PDCCH, for example) Figure 1D Both of these. For both single DCI and multiple DCI, the maximum number of TRPs can also be 2.

[0049] For single PDCCH designs (primarily for ideal backhaul), TCI extensions are being investigated. Each TCI code point within the DCI can also correspond to one or two TCI states. The size of the fields associated with the TCI states can also be the same as in Rel.15.

[0050] (PDCCH / DCI repeated)

[0051] Following Rel.17, it is also envisioned that PDCCH repetition be applied to PDCCHs (or DCIs) transmitted from more than one TRP. For example, consider using multiple PDCCHs (or DCIs) transmitted from more than one TRP to schedule or transmit / receive instructions for more than one signal / channel.

[0052] The PDCCH / DCI that is repeatedly sent by the application can also be referred to as multiple PDCCH / multiple DCI. The repeated sending of PDCCH can also be replaced by repeated PDCCH, multiple sending of PDCCH, multiple PDCCH sending, or multiple PDCCH sending.

[0053] Multiple PDCCHs / multiple DCIs can also be sent from different TRPs. Different TRPs can also correspond to different CORESET pool indices (hereinafter also referred to as CORESET pool IDs).

[0054] The multiple PDCCH / DCI can also be multiplexed using time multiplexing (TDM), frequency multiplexing (FDM), and spatial multiplexing (SDM). For example, in the case of PDCCH repetition using time multiplexing (TDM PDCCH repetition), PDCCHs transmitted from different TRPs are allocated to different time domains.

[0055] Figure 2 This illustrates an example of scheduling a PDSCH (e.g., the same PDSCH) through repeated transmissions of the PDCCH. It shows the case where PDCCH #1 is used in the transmission of DCI #1 and corresponds to the first CORESET pool ID (here, #0). It also shows the case where PDCCH #2 is used in the transmission of DCI #2 and corresponds to the second CORESET pool ID (here, #1). Here, the case where the number of PDCCH repetitions (or repetition factor) is 2 is shown, but the number of repetitions can also be 3 or more.

[0056] The content of the DCI transmitted in each PDCCH (e.g., DCI payload / coded bits / CCE number) can also have the same structure. Furthermore, the encoding / rate matching of each DCI can be controlled based on each iteration.

[0057] Each PDCCH that is repeatedly transmitted (e.g., PDCCH #1, PDCCH #2) can also be referred to as a PDCCH candidate. Each PDCCH candidate is explicitly associated (or linked), and the UE can also know the links (or associated PDCCH candidates) of the PDCCH candidates before performing decoding processing.

[0058] For PDCCH repetitions, the association (or linking) of multiple (e.g., two) search space sets can also be configured via higher-level signaling / MAC CE. Two search space sets can also correspond to separate CORESETs for each repetition. A CORESET used for PDCCH repetitions can also be equivalent to two CORESETs associated with two linked search space sets.

[0059] In a PDCCH iteration, two PDCCH candidates from two search spaces can also be linked with the same aggregation level (AL) and the same candidate index. The two linked search space sets can also consist of the same number of candidates for each AL. In other words, two linked PDCCH candidates used in a PDCCH iteration can also be two PDCCH candidates with the same aggregation level (AL) and the same index in the two linked search space sets.

[0060] (TCI state activation based on MAC CE)

[0061] In existing systems (e.g., prior to Rel. 16), with a CORESET pool ID set, the activation of the PDSCH's TCI state is performed per CORESET pool ID (e.g., TRP). In other words, the MAC CE used in the notification of TCI state activation is associated with the CORESET pool ID (e.g., TRP) (see [reference]). Figure 3 ).

[0062] exist Figure 3 In the MAC CE shown, we assume that the CORESET pool ID is set to 1. In this case, the mapping between the activated TCI state and the code points of the TCI state field contained in the DCI specified by the MAC CE can also be applied in the PDSCH scheduled in a way that makes the CORESET pool ID 1.

[0063] exist Figure 3In the MAC CE shown, we assume that the CORESET pool ID is set to 1. In this case, the mapping of the activated TCI state to the code points of the TCI state field in the DCI represented by the MAC CE can also be applied in the PDSCH scheduled in a way that makes the CORESET pool ID 1.

[0064] exist Figure 3 In the MAC CE shown, we assume the case where the CORESET pool ID is set to 0. In this case, the mapping of the activated TCI state to the code points of the TCI state field in the DCI represented by the MAC CE can also be applied in the PDSCH scheduled in a way that makes the CORESET pool ID 0.

[0065] Thus, in the existing system, a list of TCI states is set for each CORESET pool ID (here, two TCI state lists).

[0066] like Figure 4 As shown, it is also assumed that two linked PDCCH candidates (e.g., PDCCH#1 and PDCCH#2) that are reused by PDCCH are sent separately using two CORESETs with different CORESET pool IDs. For example, it is also envisioned that PDCCH#1 corresponds to the first CORESET pool ID and PDCCH#2 corresponds to the second CORESET pool ID.

[0067] Thus, in the case of PDSCH being scheduled through multiple PDSCHs (e.g., linked PDSCH candidates) corresponding to different CORESET pool IDs during repeated PDSCH transmissions, how to control the TCI state applied to PDSCH becomes a problem.

[0068] For example, how the UE envisions / interprets the mapping between the code points of the DCI's TCI status field and the activated TCI status becomes a problem. Or, how the UE determines / decides the TCI status applied to the PDSCH based on the code points of the DCI's TCI status field becomes a problem.

[0069] Alternatively, when the offset between a repeatedly sent PDCCH (e.g., multiple PDCCHs with different CORESET pool IDs) and a PDSCH scheduled through those multiple PDCCHs is smaller than a specific value, how to control the TCI state / QCL (e.g., default TCI state / default QCL) applied to the PDSCH becomes a problem.

[0070] Therefore, the inventors of the present invention studied control methods for situations where shared channels (e.g., PDCCH / PUSCH) are scheduled through repeatedly transmitted PDCCHs (or multiple PDCCHs / DCIs), and conceived of this embodiment.

[0071] In one aspect of this disclosure, when a physical shared channel (e.g., PDSCH / PUSCH) is scheduled across multiple PDCCH / DCIs of applications supporting different CORESET pool IDs, the UE determines the TCI state corresponding to the physical shared channel based on a field (TCI state field) associated with at least one of the multiple DCIs.

[0072] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Each method (or the structure / wireless communication method shown in each method) can be applied individually or in combination.

[0073] In this disclosure, "A / B" and "at least one of A and B" can be substituted for each other. In this disclosure, "A / B / C" and "at least one of A, B, and C" can also be substituted for each other. In this disclosure, cell, serving cell, CC, carrier, BWP, DLBWP, UL BWP, active DL BWP, active UL BWP, and band domain can also be substituted for each other. In this disclosure, index, ID, indicator, and resource ID can also be substituted for each other. In this disclosure, support, control, able to control, operate, and able to operate can also be substituted for each other.

[0074] In this disclosure, configure, activate, update, indicate, enable, specify, and select can be used interchangeably.

[0075] In this disclosure, higher-layer signaling may be any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc. In this disclosure, RRC, RRC signaling, RRC parameters, higher layers, higher-layer parameters, RRC information elements (IEs), and RRC messages may also be used interchangeably.

[0076] MAC signaling can also use MAC Control Element (MAC CE) or MAC Protocol Data Unit (PDU). Broadcast information can also be Master Information Block (MIB), System Information Block (SIB), Remaining Minimum System Information (RMSI), or Other System Information (OSI).

[0077] In this disclosure, MAC CE and activation / deactivation commands can be used interchangeably.

[0078] In this disclosure, pool, set, group, list, and candidate can be used interchangeably.

[0079] In this disclosure, DMRS, DMRS port, and antenna port can be interchanged.

[0080] In this disclosure, special cell, SpCell, PCell, and PSCell can be used interchangeably.

[0081] In this disclosure, beam, spatial domain filter, spatial settings, TCI state, TCI design, QCL design, QCL parameters, quasi-co-addressable, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoder, DL precoder, DL-RS, RS of QCL type D in TCI state / QCL design, RS of QCL type A in TCI state / QCL design, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoder, UL precoder, and PL-RS can also be interchanged. In this 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, and SRS can also be interchanged.

[0082] In this disclosure, the TRP ID, TRP association ID, CORESET pool ID, the position of one of the two TCI states corresponding to a code point in a field within the DCI (ordinal number, first TCI state, or second TCI state), and TRP can also be interchanged.

[0083] In this disclosure, the TRP, transmit point, panel, DMRS port group, CORESET pool, and one of the two TCI states associated with a code point in the TCI field can also be interchanged.

[0084] In the following description, examples will be given of DCI content (e.g., DCI payload / coded bits / CCE number) that is transmitted through each PDCCH in repeated PDCCH transmissions. For example, the code points of the TCI field of the DCI transmitted through the first PDCCH and the code points of the TCI field of the DCI transmitted through the second PDCCH can be set to the same value. However, this embodiment is not limited to this and can also be applied when the code points of the DCI are different.

[0085] (First method)

[0086] In the first approach, where a physical shared channel is supported by multiple PDCCHs (or PDCCH candidates) corresponding to different CORESET pool IDs, the UE determines the TCI status for the PDSCH by referring to a PDCCH candidate (or CORESET pool ID). Alternatively, the UE determines the TCI status of the PDSCH based on the MAC CE corresponding to a specific CORESET pool ID.

[0087] In this disclosure (or other embodiments), PDCCH (or PDCCH candidate) may also be replaced with DCI (or DCI candidate). Furthermore, in this disclosure (or other embodiments), PDSCH is cited as an example of a physical shared channel, but the same principle applies to PUSCH.

[0088] The UE can also receive information related to the activation / deactivation of TCI states. Information related to the activation of TCI states can also be received via MAC CE. MAC CE can also be used in existing systems (e.g., Rel.16) for notifications of TCI state activation for PDSCH (e.g., TCI State Activation / Deactivation for UE-specific PDSCH MACCE).

[0089] Figure 5A , Figure 5B This illustrates an example of a MAC CE being utilized in a notification of activation in the TCI state. Figure 5A This shows the case where the specified CORESET pool ID = 0. Additionally, Figure 5A The diagram shows the activation of TCI states #0, #10, #12, and #13. However, the activated TCI states are just one example and are not limited to this.

[0090] Figure 5B This shows the case where the specified CORESET pool ID = 1. Additionally, Figure 5B The diagram shows the activation of TCI states #1, #3, #4, and #5. However, the activated TCI states are just one example and are not limited to this.

[0091] In two CORESETs with different CORESET pool IDs, consider the case where a PDSCH is scheduled through an associated (or linked) PDCCH candidate (see [reference]). Figure 5C ). Figure 5C This illustrates the case where a PDSCH is scheduled via PDCCH#1 / DCI#1 (corresponding to CORESET pool ID#0) and PDCCH#2 / DCI#2 (corresponding to CORESET pool ID#1). Here, the case where the code point of the TCI status field of the DCI for each PDCCH is specified as 0 (e.g., "000"). The code point of the TCI status field included in the DCI can also be referred to as the TCI code point.

[0092] When mapping the TCI state activated by MAC CE to the TCI code point in the DCI for this PDSCH, it can also be referenced to one (or a specific) PDCCH candidate among multiple PDCCH candidates. One of the multiple PDCCH candidates (also referred to as the reference PDCCH candidate or reference PDCCH) can also be applied to at least one of the following options 1-1 to 1-6.

[0093] <Option 1-1>

[0094] It can also be referenced to the PDCCH candidate corresponding to the first CORESET pool index (e.g., #0) or the first CORESET pool ID. The referenced first CORESET pool ID can also refer to the TCI state of the PDSCH selected to be associated with the first CORESET pool index.

[0095] The UE can also receive information related to the activated TCI state corresponding to each CORESET pool ID (e.g., Figure 5A , Figure 5BIn the case of a MAC CE, the TCI state activated by the MAC CE corresponding to the first CORESET pool index (#0) is applied. In other words, the UE can also be envisioned as the TCI state activated by the MAC CE corresponding to the first CORESET pool index (#0) being mapped to the TCI code point of the DCI.

[0096] For example, it could also be via the MAC CE corresponding to the first CORESET pool index (#0) (see reference). Figure 6A The TCI state #0 that is indicated to be activated is mapped to TCI code point "000", and the TCI state #10 is mapped to TCI code point "001".

[0097] <Options 1-2>

[0098] When designated as 0 (“000”) as a TCI code point, the UE may also apply TCI state #0 to the PDSCH. It may also be referenced to the PDSCH candidate corresponding to the second CORESET pool index (e.g., #1) or the second CORESET pool ID.

[0099] The UE can also receive information related to the activated TCI state corresponding to each CORESET pool ID (e.g., Figure 5A , Figure 5B In the case of a MAC CE, the TCI state activated by the MAC CE corresponding to the second CORESET pool index (#1) is applied. In other words, the UE can also be envisioned as the TCI state activated by the MAC CE corresponding to the second CORESET pool index (#1) being mapped to a TCI code point.

[0100] For example, it could also be via the MAC CE corresponding to the second CORESET pool index (#1) (see reference). Figure 6B The TCI state #1 that is indicated to be active is mapped to TCI code point "000", and the TCI state #3 is mapped to TCI code point "001". For example, the UE can also apply TCI state #1 to the PDSCH when it is designated as 0 ("000") as a TCI code point.

[0101] <Options 1-3>

[0102] It can also be referenced to the first PDCCH candidate among multiple PDCCH candidates (or multiple PDCCH monitoring occasions) (or the PDCCH candidate of the first PDCCH monitoring occasion). The first can refer to either the earliest one sent in the time domain (or the first one received by the UE) or the one with the smallest index of the monitoring occasion.

[0103] Alternatively, it can be referenced to the last PDCCH candidate among multiple PDCCH candidates (or multiple PDCCH monitoring times) (or the PDCCH candidate of the last PDCCH monitoring time). "Last" can refer to either the latest one sent in the time domain (or the last one received by the UE) or the one with the largest index of the monitoring time.

[0104] The UE can also determine the TCI state of the PDSCH using a MAC CE that specifies the CORESET pool ID corresponding to the first (or last) PDCCH candidate. For example, the UE can also envision that the TCI state activated by this MAC CE is mapped to the TCI code point contained in the DCI.

[0105] <Options 1-4>

[0106] Alternatively, the PDCCH candidate of the CORESET with the lowest CORESET ID can be referenced. Or, the PDCCH candidate of the CORESET with the highest CORESET ID can be referenced.

[0107] The UE can also determine the TCI state of the PDSCH using a MAC CE that specifies the CORESET pool ID set to the lowest (or highest) indexed CORESET. For example, the UE can also envision that the TCI state activated by this MAC CE is mapped to the TCI code point contained in the DCI.

[0108] <Options 1-5>

[0109] Alternatively, the PDCCH candidate of the CORESET with the lowest search space set ID can be referenced. Or, the PDCCH candidate of the CORESET with the highest search space set ID can also be referenced.

[0110] The UE can also determine the TCI state of the PDSCH by using the MAC CE that specifies the CORESET pool ID corresponding to the lowest (or highest) search space set in the index. For example, the UE can also envision that the TCI state activated by this MAC CE is mapped to the TCI code points contained in the DCI.

[0111] <Options 1-6>

[0112] The method for determining the PDCCH candidates can also be set by the base station to the UE. For example, multiple options from options 1-1 to 1-5 can be supported, and which option to apply can be set / indicated quasi-statically or dynamically via higher-layer signaling / MAC CE / DCI.

[0113] In the above options, one of the linked PDCCH candidates being referenced can also refer to the mapping between TCI code points contained in the DCI and the activated TCI state, where the CORESET pool ID is set to the same CORESET pool ID as the reference PDCCH candidate, and the TCI state activation MAC CE is applied.

[0114] Alternatively, the rules for determining the reference used for TCI status indication can be the same as those for determining the reference used for timing offset / HARQ codebook / DAI / PUCCH resources. Or, the rules for determining the reference used for TCI status indication can be different from those for determining the reference used for timing offset / HARQ codebook / DAI / PUCCH resources.

[0115] Thus, in the first approach, a mapping is performed between the TCI state activated by referencing one (or a specific) PDCCH candidate among multiple PDCCH candidates and the TCI code point. Therefore, even when scheduling a single PDSCH is supported by multiple PDCCHs corresponding to different CORESET pool IDs, the TCI state used for the PDSCH can be appropriately determined.

[0116] (Second method)

[0117] In the second approach, where a physical shared channel is supported by multiple PDCCHs (or PDCCH candidates) corresponding to different CORESET pool IDs, the UE considers the MAC CE corresponding to each CORESET pool ID to determine the TCI status.

[0118] The UE can also use new rules, different from those in the existing system, to interpret the mapping between the TCI state activated by MAC CE and the TCI code point of DCI for PDSCH that has been repeatedly scheduled through PDCCH with two different CORESET pool IDs.

[0119] For example, the UE can also be envisioned as having both a TCI state activated by a MAC CE corresponding to a first CORESET pool ID and a TCI state activated by a MAC CE corresponding to a second CORESET pool ID mapped to TCI code points.

[0120] The UE can also receive information related to the activation / deactivation of TCI states. Information related to the activation of TCI states can also be received via MAC CE. MAC CE can also be used in existing systems (e.g., Rel.16) for notifications of TCI state activation for PDSCH (e.g., TCI State Activation / Deactivation for UE-specific PDSCH MACCE).

[0121] Figure 6A , Figure 6B This illustrates an example of a MAC CE being utilized in a notification of activation in the TCI state. Figure 6A This shows the case where CORESET pool ID #0 is specified. Additionally, Figure 6A The diagram shows the activated TCI states #0, #10, #12, and #13. However, the activated TCI states are just one example and are not limited to this.

[0122] Figure 6B This shows the case where CORESET pool ID #1 is specified. Additionally, Figure 6B The diagram shows the activated TCI states #1, #3, #4, and #5. However, the activated TCI states are just one example and are not limited to this.

[0123] In two CORESETs with different CORESET pool IDs, consider the case where a PDSCH is scheduled by associating (or linking) PDCCH candidates (see [reference]). Figure 6C ). Figure 6C This illustrates the case where a PDSCH is scheduled via PDCCH#1 / DCI#1 (corresponding to CORESET pool ID#0) and PDCCH#2 / DCI#2 (corresponding to CORESET pool ID#1).

[0124] When mapping the TCI state activated by the MAC CE to the TCI code point in the DCI for this PDSCH, it is also possible to disregard the multiple MAC CEs corresponding to different CORESET pool IDs. As a mapping rule, at least one of the following options 2-1 to 2-2 can also be applied.

[0125] <Option 2-1>

[0126] TCI code points can also be mapped to the TCI states that were initially activated in order of CORESET pool ID, and mapped to the same CORESET pool ID in order of TCI state ID.

[0127] For example, the first to (x+1)th TCI states of a MAC CE with the first CORESET pool ID (#0) set to '1' can also be mapped to TCI code point values ​​0 to x. The first to yth TCI states of a MAC CE with the second CORESET pool ID (#1) set to '1' can also be mapped to TCI code point values ​​x+1 to x+y.

[0128] exist Figure 6A , Figure 6B In the case shown, TCI states #0, #10, #12, and #13 activated by the MAC CE corresponding to the first CORESET pool ID are mapped to TCI code points 0, 1, 2, and 3 respectively (see reference). Figure 7A The TCI states #1, #3, #4, and #5 activated by the MAC CE corresponding to the second CORESET pool ID are mapped to TCI code points 4, 5, 6, and 7, respectively.

[0129] Figure 7A The diagram illustrates the case where the number of TCI states activated by the MAC CE corresponding to the first CORESET pool ID is the same as the number of TCI states activated by the MAC CE corresponding to the second CORESET pool ID, but is not limited to this.

[0130] <Option 2-2>

[0131] TCI code points can also be mapped to TCI states that have been activated in order of TCI state ID.

[0132] For example, the TCI status field of the MAC CE with the first CORESET pool ID (#0) set to '1' and the TCI status field of the MAC CE with the second CORESET pool ID (#1) set to '1' can also be mapped to TCI code point values ​​0~x.

[0133] exist Figure 6A , Figure 6B In the case shown, TCI states #0, #10, #12, and #13 activated by the MAC CE corresponding to the first CORESET pool ID, and TCI states #1, #3, #4, and #5 activated by the MAC CE corresponding to the second CORESET pool ID, are mapped to TCI code points 0-7 respectively in the order of TCI state ID (see reference). Figure 7B ).

[0134] Figure 7BThe diagram illustrates the case where the number of TCI states activated by the MAC CE corresponding to the first CORESET pool ID is the same as the number of TCI states activated by the MAC CE corresponding to the second CORESET pool ID, but is not limited to this.

[0135] In option 2-1 / option 2-2, the size of the TCI status field can also be set to 3 bits. In this case, the maximum total number of TCI states activated by MAC CE for the first CORESET pool ID and the second CORESET pool ID can also be 8.

[0136] The size of the TCI status field can also be larger than 3 bits (e.g., 4 bits). In this case, the maximum number of TCI states activated by the MAC CE corresponding to each CORESET pool ID can also be 8.

[0137] Alternatively, the maximum total number of TCI states activated by the MAC CE for the first CORESET pool ID and the second CORESET pool ID is set to 8, and a maximum of 4 activated TCI states for each CORESET pool ID can also be selected based on the MAC CE. For example, if the number of activated TCI states in the MAC CE for the first CORESET pool ID #0 / #1 is greater than 4, the first (or last) 4 TCI states with the TCI state field set to 1 can also be mapped to the TCI code points of the DCI.

[0138] In the case of PDSCH scheduled via a non-linked PDCCH, the eight activated TCI states based on MAC CE can also be applied according to the rules of the existing system that map TCI code points to the DCI.

[0139] Thus, in the second approach, the TCI states activated by the MAC CE with different CORESET pool IDs are mapped to TCI code points. Therefore, the activated TCI states corresponding to different CORESET pool IDs can be specified via DCI, allowing for flexible setting of the TCI states applied to the PDSCH.

[0140] (Third method)

[0141] In the third approach, when a physical shared channel is supported by multiple PDCCHs (or PDCCH candidates) corresponding to different CORESET pool IDs, the UE considers the MAC CE (or MAC CE that does not contain the CORESET pool ID field) that does not correspond to the CORESET pool ID to determine the TCI status.

[0142] The UE can also apply the TCI state activated by the new MAC CE for PDSCH that has been repeatedly scheduled through PDCCH with two different CORESET pool IDs. The new MAC CE can also be defined / set separately from the existing system's MAC CE (e.g., the MAC CE with the CORESET pool ID field).

[0143] For example, the new MAC CE could also be a structure that does not include a field specifying the CORESET pool ID. The UE could also envision that, for a PDSCH that has been repeatedly scheduled via a PDCCH with two different CORESET pool IDs, the TCI state activated by the new MAC CE is mapped to a TCI code point.

[0144] The UE can also receive information related to the activation / deactivation of TCI states. Information related to the activation of TCI states can also be received via a MAC CE. The UE can also envision both MAC CEs used in existing systems (e.g., Rel. 16) for notifications of TCI state activation for PDSCH (e.g., TCI States Activation / Deactivation for UE-specific PDSCH MAC CE) and new MAC CEs. New MAC CEs (e.g., Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE) can also be applied only under specific conditions (e.g., if set via higher-layer signaling).

[0145] Figure 8A , Figure 8B This illustrates an example of a MAC CE being utilized in a notification of TCI state activation. Figure 8A The MAC CE displays a field containing the notification CORESET pool ID. Additionally, the first or second CORESET pool ID can also be set through this field.

[0146] Figure 8B This illustrates an example of the new MAC CE. In the new MAC CE, it's also possible to have a structure that doesn't include a field for notifying the CORESET pool ID. Furthermore, Figure 8BThe diagram shows the activated TCI states #6, #8, #10, and #11. However, the activated TCI states are just one example and are not limited to this.

[0147] In two CORESETs with different CORESET pool indices, consider the case where a PDSCH is scheduled by associating (or linking) PDCCH candidates (see [reference]). Figure 8C ). Figure 8C This illustrates the case where a PDSCH is scheduled via PDCCH#1 / DCI#1 (corresponding to CORESET pool index #0) and PDCCH#2 / DCI#2 (corresponding to CORESET pool index #1). Here, the case where the TCI code point of each PDCCH's DCI is specified as 0 (e.g., "000").

[0148] In this situation, the UE can also consider using a new MAC CE (see reference). Figure 8B The TCI state activated by the UE controls the reception of the PDSCH. For example, the UE can also be envisioned as having the TCI state activated by the new MAC CE mapped to the TCI code point of the DCI.

[0149] exist Figure 8B In the scenario shown, the UE can also be designed such that TCI states #6, #8, #10, #11... activated by the new MAC CE are mapped to TCI code points respectively. For example, it is also possible that TCI state #6 is mapped to TCI code point 0, TCI state #6 is mapped to TCI code point 0, TCI states #8, #10, #11... are mapped to TCI code points 1, 2, 3... respectively, and TCI state #6 is mapped to TCI code point 0.

[0150] When designated as 0 (“000”) as a TCI code point, the UE can also apply TCI status #6 to the PDSCH.

[0151] PDSCHs scheduled through PDCHs that do not repeat (or do not have links with other PDCCH candidates / CORESET / search space sets) or PDSCHs scheduled through multiple PDCCH candidates with the same CORESET pool index applied can also be applied. Figure 8A The MAC CE shown in the image.

[0152] Thus, the TCI state activation MAC CE (or the new MAC CE) extended from Rel.16 can also be configured to be selectively applied to PDSCHs scheduled through two linked PDCCH candidates in two CORESETs with different CORESET pool IDs.

[0153] In the third approach, when a single PDSCH is scheduled using multiple PDCCHs corresponding to different CORESET pool IDs, the activation of the TCI state (or the mapping between the activated TCI state and TCI code points) can be achieved using a new MAC CE. The TCI state applied to the PDSCH can be flexibly configured.

[0154] <Change 1>

[0155] The new MAC CE can also be utilized in the activation of the TCI state of the PDSCH that is repeatedly scheduled by linking PDCCH candidates in two CORESETs with different CORESET pool IDs and the activation of the TCI state corresponding to a specific CORESET pool ID.

[0156] Specific fields in MAC CE (e.g., the X field) can also represent PDCCH repetitions with CORESET pool ID = 0 ("00"), CORESET pool ID = 1 ("01"), or PDCCH repetitions with different CORESET pool IDs (e.g., PDCCH repetition with CORESET pool ID = 0 and CORESET pool ID = 1) ("10") (see reference) Figure 9A In this case, the UE may also envision only the new MAC CE, without envisioning the existing MAC CE for TCI state activation.

[0157] Figure 9A The diagram shows the activated TCI states #6, #8, #10, and #11. However, the activated TCI states are just one example and are not limited to this.

[0158] Imagine a scenario where a PDSCH is scheduled through two linked PDCCH candidates within two CORESETs with different CORESET pool IDs (see reference). Figure 9B In this case, the TCI state activated by the MAC CE with the X field set to have PDCCH repetition with CORESETPoolID=0 and CORESETPoolID=1 can also be mapped to the TCI code point of the DCI.

[0159] exist Figure 9BIn the scenario shown, the UE can also envision that the TCI states #6, #8, #10, #11... activated via the new MAC CE are mapped to TCI code points 0, 1, 2, 3... respectively. Here, since the code point used as the TCI state field is notified as 0, the UE can apply TCI state #6 in the PDSCH.

[0160] Consider the scenario where a PDSCH is scheduled via a PDCH without repetition (or without links to other PDSCH candidates) or via multiple PDSCH candidates with the same CORESET pool index applied. When the PDCCH corresponds to CORESET pool ID = 0, the TCI state activated by setting a new MAC CE with CORESET pool ID = 0 in the X field can also be mapped to the TCI code point in the DCI. Alternatively, when the PDCCH corresponds to CORESET pool ID = 1, the TCI state activated by setting a new MAC CE with CORESET pool ID = 1 in the X field can be mapped to the TCI code point in the DCI.

[0161] <Change 2>

[0162] The TCI state can also be set for both single-TRP PDSCH (e.g., TCI state for PDSCH for S-TRP) and multi-DCI-based multi-TRP PDSCH (e.g., TCI state for PDSCH or M-DCI M-TRP). In this case, the TCI state for single-TRP PDSCH can also be selected for PDSCHs scheduled by associating with different CORESET pool IDs (e.g., linked PDCCHs, recurring PDCCHs). Figure 10 ).

[0163] (Fourth method)

[0164] In the fourth approach, during the repetition of the PDCCH, if the offset (also known as the scheduling offset) between the PDCCH / DCI and the PDSCH scheduled through the PDCCH / DCI is smaller than a specific value (e.g., timeDurationForQCL), the TCI state / QCL assumption applied to the PDSCH is explained.

[0165] In existing systems (e.g., Rel.16), when the offset between PDCCH / DCI and PDSCH is smaller than a specific value (e.g., timeDurationForQCL), and CORESETs are configured with different CORESET pool IDs, a specific QCL can also be applied to PDSCH if a specific higher-level parameter is set. This specific higher-level parameter can also be a higher-level parameter that sets the default TCI state per CORESET pool index (e.g., enableDefaultTCIStatePerCoresetPoolIndex-r16).

[0166] For example, for a PDSCH scheduled via a PDCCH with CORESET pool ID = 0, the QCL of the CORESET with the smallest CORESET ID in the CORESET with CORESET pool ID = 0 in the latest slot (e.g., the latest slot) can also be used as the default QCL for the PDSCH. The latest slot can also be the most recent slot in which a CORESET (e.g., the CORESET corresponding to CORESET pool ID #0) has been monitored. In other words, the default TCI state / QCL for the PDSCH with CORESET pool ID = 0 can also be determined based on the smallest CORESET ID associated with CORESET pool ID = 0 in the latest monitoring slot.

[0167] For example, for a PDSCH scheduled via a PDCCH with CORESET pool ID = 1, the QCL of the CORESET with the smallest CORESET ID among the CORESETs with CORESET pool ID = 1 in the latest slot (e.g., the latest slot) can also be used as the default QCL for the PDSCH. The latest slot can also be the most recent slot in which a CORESET (e.g., the CORESET corresponding to CORESET pool ID #1) has been monitored. In other words, the default TCI state / QCL for the PDSCH with CORESET pool ID = 1 can also be determined based on the smallest CORESET ID associated with CORESET pool ID = 1 in the latest monitoring slot.

[0168] Thus, in the existing system, when the high-level parameters that set the default TCI state per CORESET pool index are less than a specific value, the default QCL applied to the PDSCH is determined by considering the CORESET pool ID corresponding to that DCI (or PDCCH). In other words, the default QCL applied to the PDSCH is determined based on the CORESET pool ID corresponding to the PDCCH / DCI that schedules the PDSCH.

[0169] On the other hand, it is also envisioned that multiple PDCCH candidates that are repeatedly used (e.g., linked PDCCH candidates) are sent through two CORESETs with different CORESET pool IDs (see [reference]). Figure 11 ).

[0170] Figure 11 This illustrates an example of scheduling a PDSCH (e.g., the same PDSCH) through repeated transmissions of the PDCCH. It shows the case where PDCCH#1 / DCI#1 corresponds to the first CORESET pool ID (here, #0), and PDCCH#2 / DCI#2 corresponds to the second CORESET pool ID (here, #1). Here, the case where the number of PDCCH repetitions (or repetition factor) is 2 is shown, but the number of repetitions can also be 3 or more.

[0171] Figure 11 In cases where the scheduling offset between at least one (or all) of the repeatedly transmitted PDCCH / DCI and the PDSCH is smaller than a specific value (e.g., timeDurationForQCL), the question arises as to how to determine the default QCL (or default beam) to be applied to the PDSCH.

[0172] In this embodiment, if the scheduling offset between at least one (or all) of the repeatedly transmitted PDCCH / DCI and the PDSCH is smaller than a specific value, at least one of Alt.4-1 to Alt.4-3 below can also be applied. The following description can also be applied to either the case where the offset between at least one of the repeatedly transmitted PDCCH / DCI and the PDSCH is smaller than a specific value (scheduling offset assumption #1) or the case where the offset between multiple PDCCH / DCI and the PDSCH is smaller than a specific value (scheduling offset assumption #2).

[0173] Alt.4-1 controls that, if the scheduling offset between at least one (or all) of the repeatedly transmitted PDCCH / DCI and the PDSCH is smaller than a specific value, the default TCI state for each CORESET pool ID will not be set. Alt.4-2 / 4-3 controls that, if the scheduling offset between at least one (or all) of the repeatedly transmitted PDCCH / DCI and the PDSCH is smaller than a specific value, the default TCI state for each CORESET pool ID will be set.

[0174] <Alt.4-1>

[0175] In cases where the UE is configured with multiple (e.g., two) PDCCH candidates (e.g., linked PDCCH candidates) that are repeatedly used in two CORESETs with different CORESET pool IDs, it is also not advisable to set specific high-level parameters (e.g., enableDefaultTCIStatePerCoresetPoolIndex-r16) for setting the default TCI state per CORESET pool index (see reference). Figure 12 In other words, when multiple linked PDCCH candidates that are repeatedly used by PDCCH are sent through two CORESETs with different CORESET pool IDs, the UE can also be assumed to be indexed by each CORESET pool without being set to a default TCI state.

[0176] Without setting specific higher-layer parameters, and with the offset between the reception of PDCCH / DCI and the reception of the corresponding PDSCH being smaller than a specific value, the UE may also use the QCL of the CORESET with the smallest CORESET ID in the latest slot (e.g., the latest slot) of the CORESET that has been monitored as the default QCL of the PDSCH, regardless of the CORESET pool ID (or, without considering the CORESET pool ID).

[0177] In other words, the default TCI state / QCL of PDSCH can also be determined based on the smallest CORESET ID in the monitoring slot of the latest CORESET, without considering the CORESET pool ID.

[0178] Alternatively, the UE can also operate in an existing system (e.g., Rel.16) without having specific high-level parameters set (e.g., enableDefaultTCIStatePerCoresetPoolIndex-r16).

[0179] The UE may also assume that the DM-RS ports of the PDSCH of a serving cell are quasi-co-located with the RS(s) with respect to the QCL parameter(s) used for the PDCCH quasi-co-location indication of the CORESET associated with a monitored search space with the lowest controlResourceSetId in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE.

[0180] <Alt.4-2>

[0181] The UE can also be configured with multiple (e.g., two) PDCCH candidates (e.g., linked PDCCH candidates) that are repeatedly used in two CORESETs with different CORESET pool IDs, and the setting of specific higher-level parameters for the default TCI state per CORESET pool index is supported (see [reference]). Figure 13 In other words, when multiple PDCCH candidates that are repeatedly used are sent through two CORESETs with different CORESET pool IDs, the UE can also be envisioned to support the setting of the default TCI state per CORESET pool index.

[0182] A specific high-level parameter that sets the default TCI state for each CORESET pool index can be, for example, enableDefaultTCIStatePerCoresetPoolIndex-r16, or a new high-level parameter.

[0183] Imagine a scenario where specific higher-layer parameters are set and the offset between the received PDCCH / DCI and the corresponding received PDSCH is smaller than a specific value (see reference). Figure 13 In this case, the UE can also determine the default QCL / default beam in two CORESETs with different CORESET pool IDs, for the PDSCH scheduled through the linked PDCCH candidates, by referring to one (or a specific) PDCCH candidate among the linked PDCCH candidates.

[0184] One of the multiple PDCCH candidates (also referred to as the reference PDCCH candidate or reference PDCCH) may also be subject to at least one of the following options 4-2-1 to 4-2-6.

[0185] [Option 4-2-1]

[0186] It can also be referenced to the PDCCH candidate corresponding to the first CORESET pool index (e.g., #0) or the first CORESET pool ID. The referenced first CORESET pool ID can also refer to the TCI state / QCL assumption of the smallest CORESET ID associated with CORESET pool ID = 0 in the latest time slot.

[0187] The UE can also envision that, for a PDSCH scheduled through repeated PDCCHs, the QCL of the CORESET with the smallest CORESET ID in the CORESET pool ID=0 in the latest slot (e.g., the latest slot) is the default QCL of the PDSCH. The latest slot can also be the most recent slot in which the CORESET (e.g., the CORESET corresponding to CORESET pool ID #0) has been monitored.

[0188] [Option 4-2-2]

[0189] It can also be referenced to the PDCCH candidate corresponding to the second CORESET pool index (e.g., #1) or the second CORESET pool ID. The referenced second CORESET pool ID can also refer to the TCI state / QCL assumption of the smallest CORESET ID associated with CORESET pool ID=1 in the latest time slot.

[0190] The UE can also envision that, for a PDSCH scheduled through repeated PDCCHs, the QCL of the CORESET with the smallest CORESET ID in the CORESET pool ID=1 in the latest slot (e.g., the latest slot) is the default QCL of the PDSCH. The latest slot can also be the most recent slot in which a CORESET (e.g., the CORESET corresponding to CORESET pool ID#1) has been monitored.

[0191] [Option 4-2-3]

[0192] It can also be referenced to the first PDCCH candidate among multiple PDCCH candidates (or multiple PDCCH monitoring times) (or the PDCCH candidate of the first PDCCH monitoring time). The first can refer to either the earliest one sent in the time domain (or the first one received by the UE) or the one with the smallest index of the monitoring time.

[0193] Alternatively, it can be referenced to the last PDCCH candidate among multiple PDCCH candidates (or multiple PDCCH monitoring times) (or the PDCCH candidate of the last PDCCH monitoring time). "Last" can refer to either the latest one sent in the time domain (or the last one received by the UE) or the one with the largest index of the monitoring time.

[0194] Consider the case where the CORESET pool ID corresponding to the first PDCCH candidate (or the last PDCCH candidate) is 0. In this case, the UE can also assume that for PDSCH scheduled through repeated PDCCHs, the QCL of the CORESET with the smallest CORESET ID in the CORESET with CORESET pool ID = 0 in the latest slot (e.g., the latest slot) is the default QCL of the PDSCH.

[0195] Consider the case where the CORESET pool ID corresponding to the first (or last) PDCCH candidate is 1. In this case, the UE can also assume that, for a PDSCH scheduled through repeated PDCCHs, the QCL of the CORESET with the smallest CORESET ID in the CORESET with CORESET pool ID = 1 in the latest slot (e.g., the latest slot) is the default QCL of the PDSCH.

[0196] [Option 4-2-4]

[0197] Alternatively, the PDCCH candidate of the CORESET with the lowest CORESET ID can be referenced. Or, the PDCCH candidate of the CORESET with the highest CORESET ID can be referenced.

[0198] Consider the case where the PDCCH candidate for the CORESET with the lowest (or highest) CORESET ID corresponds to CORESET pool ID = 0. In this case, the UE can also assume that, for a PDSCH scheduled through repeated PDCCHs, the QCL of the CORESET with the smallest CORESET ID among the CORESETs with CORESET pool ID = 0 in the latest slot (e.g., the latest slot) is the default QCL of the PDSCH.

[0199] Consider the case where the PDCCH candidate for the CORESET with the lowest (or highest) CORESET ID corresponds to CORESET pool ID = 1. In this case, the UE can also assume that, for PDSCHs scheduled via repeated PDCCHs, the QCL of the CORESET with the smallest CORESET ID among the CORESETs with CORESET pool ID = 1 in the latest slot (e.g., the latest slot) is the default QCL of the PDSCH.

[0200] [Options 4-2-5]

[0201] Alternatively, the PDCCH candidate of the CORESET with the lowest search space set ID can be referenced. Or, the PDCCH candidate of the CORESET with the highest search space set ID can also be referenced.

[0202] Consider the case where the CORESET pool ID corresponding to the PDCCH candidate of the CORESET with the lowest (or highest) search space set ID is 0. In this case, the UE can also envision that, for a PDSCH scheduled through repeated PDCCHs, the QCL of the CORESET with the smallest CORESET ID in the CORESET with CORESET pool ID = 0 in the latest slot (e.g., the latest slot) is the default QCL of the PDSCH.

[0203] Consider the case where the CORESET pool ID = 1 corresponds to the PDCCH candidate of the CORESET with the lowest (or highest) search space set ID. In this case, the UE can also envision that, for a PDSCH scheduled through repeated PDCCHs, the QCL of the CORESET with the smallest CORESET ID in the CORESET pool ID = 1 in the latest slot (e.g., the latest slot) is the default QCL of the PDSCH.

[0204] [Option 4-2-6]

[0205] The method for determining the PDCCH candidate can also be set by the base station to the UE. For example, multiple options from options 4-2-1 to 4-2-5 can be supported, and which option to apply can be set / indicated quasi-statically or dynamically via higher-layer signaling / MAC CE / DCI.

[0206] In the above options, setting the default QCL by referencing one of the linked PDCCH candidates can also mean considering the CORESET pool ID corresponding to the referenced PDCCH candidate, and determining the QCL of the CORESET with the smallest CORESET ID among the CORESETs of that CORESET pool ID in the latest slot (e.g., the latest slot) as the default QCL of the PDSCH.

[0207] Specifically, the UE may also assume that, in the latest time slot monitored by the UE, one or more CORESETs associated with the same CORESET pool ID as the "reference PDCCH candidate" between two linked PDCCH candidates scheduling the PDSCH within the active BWP of the serving cell, the QCL parameter used in the PDCCH quasi-co-location indication of the CORESET associated with the smallest CORESET ID among the CORESETs with the same CORESET pool ID as the "reference PDCCH candidate" between the two linked PDCCH candidates scheduling the PDSCH, the DM-RS ports of the PDSCH scheduled by two linked PDCCH candidates associated with different CORESET pool IDs are quasi-co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with the serving cell. a monitoredsearch space with the lowest controlResourceSetId among CORESETs, which are configured with the same value of CORESETPoolIndex as the “reference PDCCHcandidate” between the two linked PDCCH candidates scheduling that PDSCH,in the latest slot in which one or more CORESETs associated with the same value of CORESETPoolIndex as the “reference PDCCH candidate” between the two linkedPDCCH candidates scheduling that PDSCH within the active BWP of the servingcell are monitored by the UE.). ,

[0208] The rules for determining the reference used for TCI status indication can be the same as those for determining the reference used for timing offset / HARQ codebook / DAI / PUCCH resources. Alternatively, the rules for determining the reference used for TCI status indication can be different from those for determining the reference used for timing offset / HARQ codebook / DAI / PUCCH resources.

[0209] <Alt.4-3>

[0210] The UE can also be configured with multiple (e.g., two) PDCCH candidates (e.g., linked PDCCH candidates) that are repeatedly used in two CORESETs with different CORESET pool IDs, and the setting of specific higher-level parameters for the default TCI state per CORESET pool index is supported (see [reference]). Figure 13 In other words, when multiple PDCCH candidates that are repeatedly used are sent through two CORESETs with different CORESET pool IDs, the UE can also be envisioned as supporting the setting of a default TCI state indexed by each CORESET pool.

[0211] A specific high-level parameter sets the default TCI state for each CORESET pool index; for example, it could be either enableDefaultTCIStatePerCoresetPoolIndex-r16 or a new high-level parameter.

[0212] Imagine a scenario where specific higher-layer parameters are set and the offset between the received PDCCH / DCI and the corresponding received PDSCH is smaller than a specific value (see reference). Figure 13In this case, the UE can also determine the QCL / default beam based on the CORESET with the smallest ID among the CORESETs that are set to PDCCH reusable and linked to other CORESETs with different CORESET pool IDs (or, apply the TCI state / QCL corresponding to that CORESET as the default QCL / default beam).

[0213] For example, consider a scenario where a PDSCH is scheduled via PDCCH#1 / DCI#1 corresponding to CORESET pool ID=0 and PDCCH#2 / DCI#2 corresponding to CORESET pool ID=1. The UE can also apply the TCI state / QCL corresponding to the CORESET with the smallest ID among the CORESETs corresponding to PDCCH#1 and PDCCH#2 as the default QCL / default beam for the PDSCH.

[0214] Specifically, the UE may also assume that, in the latest time slot monitored by the UE, among the CORESETs linked to other CORESETs with different CORESET pool IDs that are repeatedly used with the PDCCH within the active BWP of the serving cell, the CORESET with the smallest CORESET ID (e.g., lowest controlResourceSetID) associated with the monitored search space, the QCL parameter used in the PDCCH quasi-co-location indication (e.g., PDCCH quasi co-location indication) of the CORESET with the smallest CORESET ID (e.g., lowest controlResourceSetID) associated with the monitored search space, is quasi-co-located with the RS(s) of the PDSCH scheduled by two linked PDCCH candidates associated with different CORESET pool IDs. co-location indication of theCORESET associated with a monitored search space with the lowestcontrolResourceSetId among CORESETs, which are configured with linkage withanother CORESET with different CORESETPoolID for PDCCH repetition,in the latest slot in which one or more CORESETs configured with linkage withanother CORESET with different CORESETPoolID for PDCCH repetition that within the active BWP of the serving cell are monitored by the UE.). ,

[0215] Alternatively, if specific higher-layer parameters are set and the offset between the received PDCCH / DCI and the corresponding received PDSCH is smaller than a specific value, the UE may also utilize the QCL of the CORESET with the smallest CORESET ID in the latest slot (e.g., the latest slot) that has been monitored for CORESET as the default QCL for PDSCH. The latest slot can also be the most recent slot that has been monitored for CORESET (e.g., the CORESET corresponding to CORESET pool ID #0 / #1).

[0216] For example, imagine at least one of the PDCCH / DCIs that are repeatedly sent (e.g., Figure 13 This applies when the offset between PDCCH#2 and PDSCH is less than a specific value (while the offset between PDCCH#1 and PDSCH is greater than a specific value). In such cases, the UE can also determine the default TCI state / QCL for PDSCH based on the TCI state / QCL corresponding to PDCCH#1 (CORESET pool ID=0). For example, the TCI state / QCL corresponding to PDCCH#1 (CORESET pool ID=0) can also be used as the default TCI state / QCL.

[0217] (UE capability information)

[0218] In the first to fourth methods described above, the following UE capabilities can also be set. Additionally, the following UE capabilities can be replaced with parameters (e.g., higher-layer parameters) set to the UE from the network (e.g., base station).

[0219] It can also be defined as UE capability information that is repeatedly associated with whether or not multiple TRPs (e.g., M-TRP) are supported by the PDCCH.

[0220] It can also be defined as UE capability information related to whether or not it supports PDCCH repetition of multiple TRPs that utilize PDCCH candidates linked by two CORESETs with different CORESET pool IDs.

[0221] It can also be defined to determine whether UE capability information related to the default QCL / default beam is supported for PDSCHs that have been repeatedly scheduled through PDCCHs in two CORESETs with different CORESET pool IDs, provided that the scheduling offset is smaller than a specific value (e.g., timeDurationForQCL).

[0222] Methods one through four can also be configured to be applied in a UE that supports / reports at least one of the aforementioned UE capabilities. Alternatively, methods one through four can also be configured to be applied in a UE for which corresponding higher-layer parameters have been set from the network.

[0223] (Wireless communication system)

[0224] The structure of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0225] Figure 14 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) as standardized by the Third Generation Partnership Project (3GPP).

[0226] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

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

[0228] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0229] The wireless communication system 1 may also include: a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. User terminals 20 may also be located within at least one cell. The configuration and number of cells and user terminals 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0230] User terminal 20 may also be connected to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0231] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these; for example, FR1 can also correspond to a frequency band higher than FR2.

[0232] In addition, user terminal 20 can also communicate in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0233] Multiple base stations 10 can also be connected via wired (e.g., fiber optic cable based on the Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

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

[0235] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0236] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0237] Wireless access methods can also be referred to as waveforms. In addition, in wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be applied in the wireless access methods of UL and DL.

[0238] In the wireless communication system 1, the downlink channel can also be a shared downlink channel (Physical Downlink Shared Channel (PDSCH)), a broadcast channel (Physical Broadcast Channel (PBCH)), or a downlink control channel (Physical Downlink Control Channel (PDCCH)) shared by each user terminal 20.

[0239] In addition, in the wireless communication system 1, the uplink channel can also be an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), an uplink control channel (Physical Uplink Control Channel (PUCCH)), or a random access channel (Physical Random Access Channel (PRACH)) shared by each user terminal 20.

[0240] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and high-level control information can also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) can be transmitted via PBCH.

[0241] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0242] Additionally, the DCI for scheduling PDSCH can also be called DL allocation, DL DCI, etc., and the DCI for scheduling PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can also be replaced with DL data, and PUSCH can also be replaced with UL data.

[0243] In PDCCH detection, a Control Resource Set (CORESET) and a search space can be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0244] A search space can also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", and "CORESET setting" disclosed herein can be used interchangeably.

[0245] Uplink control information (UCI) can also be transmitted via PUCCH, including at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat reQuest ACK knowledgement (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). Random access preambles used for establishing a connection with the cell can also be transmitted via PRACH.

[0246] Additionally, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, it may be described without "physical" at the beginning of various channels.

[0247] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, as DL-RS, cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS) can also be transmitted.

[0248] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0249] Furthermore, in wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0250] (Base station)

[0251] Figure 15 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0252] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may also possess other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0253] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0254] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0255] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 may be composed of a transmitter / receiver, RF circuitry, baseband circuitry, filters, phase shifters, measurement circuitry, transmitting / receiving circuitry, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0256] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be configured as a transmitting unit and a receiving unit. The transmitting unit can also be configured as a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be configured as a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0257] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

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

[0259] The transmitting and receiving unit 120 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

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

[0261] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing, Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0262] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0263] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, demodulate baseband signals, etc., for the wireless frequency band signals received by the transmitting and receiving antenna 130.

[0264] The transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data.

[0265] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also 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 can also be output to the control unit 110.

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

[0267] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0268] The transmit / receive unit 120 may also transmit a MAC CE containing information related to the activation of the Transmission Setting Indication (TCI) state of the Physical Shared Channel. The control unit 110 may also, in the case where a Physical Shared Channel is scheduled through multiple downlink control channels supporting different control resource set pool indices, indicate the TCI state corresponding to the Physical Shared Channel using a field related to the TCI state contained in at least one of multiple downlink control messages transmitted separately through the multiple downlink control channels.

[0269] The transmit / receive unit 120 can also transmit a physical shared channel to the terminal, which is scheduled through multiple downlink control channels supporting different control resource set pool indices. The control unit 110 can also determine, if the offset between at least one of the multiple downlink control channels and the physical shared channel is less than a specific value, that the physical shared channel is received in the terminal based on a default TCI state set according to each control resource set pool index or a default TCI state set without association with a control resource set pool index.

[0270] (User terminal)

[0271] Figure 16 This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided as one or more.

[0272] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also possess other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0273] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

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

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

[0276] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0277] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0278] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

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

[0280] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate the bit string to be transmitted.

[0281] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0282] Furthermore, whether or not to apply DFT processing can be based on the transform precoding settings. For a certain channel (e.g., PUSCH), if transform precoding is activated, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

[0283] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0284] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0285] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data.

[0286] The transmitting / receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can also perform RRM measurements, CSI measurements, etc., based on the received signal. The measurement unit 223 can also 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 can also be output to the control unit 210.

[0287] In addition, the transmitting unit and receiving unit of the user terminal 20 in this disclosure can also be configured by at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0288] The transmit / receive unit 220 can also receive a MAC CE containing information related to the activation of the Transmit Setting Indication (TCI) status of the Physical Shared Channel.

[0289] The control unit 210 can also determine the TCI state corresponding to the physical shared channel based on a field related to the TCI state contained in at least one of the multiple downlink control messages transmitted through the multiple downlink control channels respectively, when a physical shared channel is scheduled through multiple downlink control channels that support different control resource set pool indexes.

[0290] The code points contained in the fields associated with the TCI status can also be associated with a TCI status activated by a MAC CE corresponding to a specific control resource set pool index. Alternatively, the code points contained in the fields associated with the TCI status can also be associated with a TCI status activated by a MAC CE corresponding to a first control resource set pool index and a TCI status activated by a MAC CE corresponding to a second control resource set pool index. Alternatively, the code points contained in the fields associated with the TCI status can also be associated with a TCI status activated by a MAC CE that does not contain information related to a control resource set pool index.

[0291] The transmitting and receiving unit 220 can also receive multiple downlink control channels for applications that support different control resource set pool indices.

[0292] The control unit 210 can also control the reception of the physical shared channel based on a default TCI state set according to each control resource set pool index or a default TCI state set without association with a control resource set pool index, when the offset between at least one of the multiple downlink control channels and the physical shared channel scheduled through the multiple downlink control channels is smaller than a specific value.

[0293] Control unit 210 may also determine the quasi-co-addressability of the physical shared channel based on a specific control resource set monitored in the most recent time slot of the monitored control resource set. Alternatively, control unit 210 may also determine the quasi-co-addressability of the physical shared channel based on a specific control resource set corresponding to a control resource pool index of a specific downlink control channel among multiple downlink control channels. Alternatively, control unit 210 may also determine the quasi-co-addressability of the physical shared channel based on a specific control resource set corresponding to at least one of the multiple downlink control channels.

[0294] (Hardware structure)

[0295] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining one or more of the aforementioned devices with software.

[0296] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. As described above, the implementation method is not particularly limited.

[0297] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 17 This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0298] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0299] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0300] The functions of the base station 10 and the user terminal 20 are implemented, for example, by reading specific software (programs) into 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 device 1003.

[0301] The processor 1001, for example, enables the operating system to operate and control the computer as a whole. The processor 1001 may also be configured as a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0302] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operating in the processor 1001; similar implementations can be made for other functional blocks.

[0303] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to one embodiment of the present disclosure.

[0304] Storage device 1003 may also be a computer-readable recording medium, such as a flexible disc, floppy disk, optical disk (e.g., compact disc ROM, CD-ROM), digital multifunction disk, Blu-ray disc, removable disk, hard disk, smart card, flash memory device (e.g., card, stick, key drive), stripe, database, server, or other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0305] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

[0306] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

[0307] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communication of information. The bus 1007 can be a single bus or different buses can be used between the devices.

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

[0309] (Modified example)

[0310] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Additionally, a signal may also be a message. A reference signal may also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0311] A radio frame can also be composed of one or more periods (frames) in the time domain. Each period (frame) that constitutes the radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0312] Here, the parameter set can also refer to communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0313] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). In addition, a time slot can also be a time unit based on a set of parameters.

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

[0315] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols used in this disclosure can be used interchangeably.

[0316] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, a time slot or a mini-time slot can also be called a TTI. That is to say, at least one of a subframe and a TTI can be a subframe in the existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a time slot, mini-time slot, etc.

[0317] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0318] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to the transmission block, code block, codeword, etc. can be shorter than the TTI.

[0319] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0320] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in 3GPP Rel.8-12), standard TTI, long TTI, normal subframe, standard subframe, long subframe, time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, mini time slot, sub-time slot, time slot, etc.

[0321] In addition, long TTIs (e.g., normal TTIs, subframes, etc.) can be replaced with TTIs with a duration of more than 1ms, and short TTIs (e.g., shortened TTIs, etc.) can be replaced with TTIs with a duration of less than long TTIs but more than 1ms.

[0322] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0323] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0324] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0325] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0326] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0327] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0328] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive on a specific channel / signal outside of the active BWP. Furthermore, terms such as "cell" and "carrier" in this disclosure can be replaced with "BWP".

[0329] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0330] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0331] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0332] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0333] Furthermore, information, signals, etc., can be output in at least one of the following directions: from higher level (upper layer) to lower level (lower layer), and from lower layer to higher level. Information, signals, etc., can also be input and output via multiple network nodes.

[0334] Input and output information and signals can be stored in a specific location (such as memory) or managed using management tables. Input and output information and signals can be overwritten, updated, or appended. Output information and signals can also be deleted. Input information and signals can also be sent to other devices.

[0335] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher 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.

[0336] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0337] Furthermore, notification of specific information (e.g., a notification that “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0338] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0339] Whether it is called software, firmware, middleware, microcode, hardware description language, or any other name, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, program, subprogram, software module, application, software application, software package, routine, subroutine, object, executable file, execution thread, process, function, etc.

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

[0341] The terms “system” and “network” as used in this disclosure are used interchangeably. “Network” may also refer to devices included in a network (e.g., a base station).

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

[0343] In this disclosure, the terms "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access Point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell Group", "Carrier", and "Component Carrier" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0344] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its coverage area can be divided into several smaller areas, each of which can provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0345] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0346] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0347] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. This mobile body can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and the mobile station also includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0348] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, various methods / implementations of this disclosure can also be applied to a structure where the communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., it can also be referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can also be replaced with terms corresponding to inter-terminal communication (e.g., "side"). For example, uplink channel, downlink channel, etc. can also be replaced with side channel.

[0349] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0350] In this disclosure, operations are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. Clearly, in a network comprising one or more network nodes having a base station, various operations for communication with a terminal can be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0351] The various methods / implementations described in this disclosure can be used individually, in combination, or switched as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, with respect to the methods described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0352] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future generation radio access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi, a registered trademark), IEEE 802.16 (WiMAX, a registered trademark), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from them. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, or a combination with 5G, etc.) for application.

[0353] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise specified. In other words, the word "based on" means both "based on only" and "based on at least".

[0354] Any reference to an element using the terms "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These terms may be used in this disclosure as a convenient way to distinguish between two or more elements. Therefore, references to the first and second elements do not imply that only two elements are permitted, or that the first element must take precedence over the second element in some form.

[0355] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database, or other data structure), and ascertaining.

[0356] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0357] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". In other words, "judgment (decision)" can also refer to certain actions as situations where a "judgment (decision)" is made.

[0358] In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0359] As used in this disclosure, the terms "connected," "coupled," or all variations thereof, mean any direct or indirect connection or combination between two or more elements, and can include cases where there is one or more intermediate elements between two mutually "connected" or "coupled" elements. The combination or connection between elements can be physical, logical, or a combination thereof. For example, "connected" can also be replaced with "access."

[0360] In this disclosure, when connecting two elements, it is possible to consider using more than one wire, cable, printed electrical connection, etc., and as several non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region, to "connect" or "combine" them with each other.

[0361] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other". Additionally, the term can also mean "A and B are different from C respectively". Terms such as "separate" and "combined" can also be interpreted as "different".

[0362] In this disclosure, the terms “include,” “including,” and variations thereof, as used, mean inclusiveness, similar to the term “comprising.” Furthermore, the term “or” as used in this disclosure does not mean XOR.

[0363] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0364] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions are not limited to the embodiments described herein. The inventions disclosed herein can be implemented as modifications and variations without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description in this disclosure is for illustrative purposes only and is not intended to limit the inventions disclosed herein.

Claims

1. A terminal, comprising: The receiving unit receives a MACCE containing information related to the activation of the Physical Shared Channel Transmission Configuration Indicator (TCI) state; and The control unit, when a physical shared channel is scheduled through multiple downlink control channels supporting different control resource set pool indices, determines the TCI state corresponding to the physical shared channel based on a field related to the TCI state contained in at least one of multiple downlink control messages transmitted through the multiple downlink control channels respectively.

2. The terminal as described in claim 1, wherein, The code points contained in the fields associated with the TCI state are associated with the TCI state activated by the MAC CE corresponding to a specific control resource set pool index.

3. The terminal as described in claim 1, wherein, The code points contained in the fields associated with the TCI state are associated with the TCI state activated by the MAC CE corresponding to the first control resource set pool index and the TCI state activated by the MAC CE corresponding to the second control resource set pool index.

4. The terminal as described in claim 1, wherein, The code points contained in the fields associated with the TCI state are associated with the TCI state activated by a MAC CE that does not contain information related to the control resource set pool index.

5. A wireless communication method for a terminal, comprising: The steps of receiving a MAC CE containing information related to the activation of the Transmission Configuration Indicator (TCI) state of the Physical Shared Channel; and In the case where a physical shared channel is scheduled through multiple downlink control channels supporting different control resource set pool indexes, the step of determining the TCI state corresponding to the physical shared channel is based on a field related to the TCI state contained in at least one of the multiple downlink control messages transmitted through the multiple downlink control channels respectively.

6. A base station, comprising: The transmitting unit transmits a MACCE containing information related to the activation of the Physical Shared Channel Transmission Configuration Indicator (TCI) state; and The control unit, when a physical shared channel is scheduled through multiple downlink control channels supporting different control resource set pool indices, indicates the TCI state corresponding to the physical shared channel by using a field related to the TCI state included in at least one of the multiple downlink control messages transmitted through the multiple downlink control channels respectively.

Images