Terminal and communication method

Abstract

To clarify a method for applying a TCI state and a QCL type to a LP-WUS, and enable reception of the LP-WUS using the QCL relationship.SOLUTION: A base station comprises: a receiving section that receives, from a base station, a transmission configuration indication (TCI) state including a first quasi co-location (QCL) type; and a control section that applies, to a low power signal, at least part of characteristics related to a second QCL type different from the first QCL type.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a terminal and a communication method in a wireless communication system. [Background technology]

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) Release 19 (Rel-19) introduced the Low-Power Wake-Up Signal (LP-WUS). LP-WUS is a mechanism that uses a low-power, always-operable wake-up receiver (WUR) to determine the presence or absence of paging with minimal reception capabilities.

[0003] In 3GPP Rel-19, the application of a Transmission Configuration Indication (TCI) state (TCI state) using reference signals that have a Quasi Co-Location (QCL) relationship with SSB or CSI-RS when UE (User Equipment) receives LP-WUS is being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V18.5.0(2025-03) [Non-patent document 2] 3GPP TS 38.401 V18.5.0(2025-03) Summary of the Invention [Problem to be solved by the invention]

[0005] Previously, it was unclear how to configure the TCI state and QCL type applied to LP-WUS. As a result, there was a risk that the UE would not be able to properly receive LP-WUS depending on whether the unified TCI framework was available or the TCI state configuration. [Means for solving the problem]

[0006] The terminal in this embodiment includes a receiving unit that receives a TCI state including a first Quasi Co-Location (QCL) type from a base station, and a control unit that applies at least some of the characteristics associated with a second QCL type that is different from the first QCL type to a low-power signal. [Effects of the Invention]

[0007] According to this embodiment, the method of applying the TCI state and QCL type to the LP-WUS is clarified, and it becomes possible to receive the LP-WUS using the QCL relationship. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present invention. [Figure 2] FIG. 1 illustrates an example of a QCL type. [Figure 3] FIG. 10 is a diagram illustrating an example of the configuration of TCI and each parameter in the TCI state. [Figure 4] FIG. 1 is a diagram showing the relationship between a conventional Target RS and a Source RS and a QCL type. [Figure 5] FIG. 2 is a flowchart illustrating an example of an operation procedure of a UE in this embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of a relationship between a Target RS and a Source RS and a QCL type in the first embodiment. [Figure 7] FIG. 10 is a diagram illustrating an example of a definition of an operation related to an antenna port QCL in the first embodiment (Alt. 1-2). [Figure 8] FIG. 10 is a diagram illustrating an example of a relationship between a target RS and a source RS and a QCL type in the second embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of a definition of an operation related to an antenna port QCL in the second embodiment (Alt. 2-3). [Figure 10] FIG. 10 is a sequence diagram showing an example of an operation procedure of a wireless communication system according to the second embodiment (Alt. 2-4). [Figure 11] FIG. 10 is a diagram illustrating an example of definition of operations related to antenna port QCL in Example 2 of the second embodiment (Alt. 2-4). [Figure 12] FIG. 10 is a diagram illustrating an example of definition of operations related to antenna port QCL in Example 3 of the second embodiment (Alt. 2-4). [Figure 13] FIG. 10 is a sequence diagram showing an example of an operation procedure of a wireless communication system according to the second embodiment (Alt. 2-5). [Figure 14] FIG. 10 is a diagram illustrating an example of a definition of an operation related to an antenna port QCL in the third embodiment (Alt. 3-4). [Figure 15] FIG. 2 is a diagram illustrating an example of a functional configuration of a base station according to the present embodiment. [Figure 16] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal according to the present embodiment. [Figure 17] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station or a terminal according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] The present embodiment will be described below with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0010] In operation of the wireless communication system of the present embodiment, an existing technology may be used as appropriate. The existing technology is, for example, the existing LTE or the existing NR, but is not limited to the existing LTE or NR.

[0011] Furthermore, in the present embodiment described below, terms used in existing technologies, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0012] Furthermore, in this embodiment, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or other methods (for example, flexible duplex, etc.).

[0013] Furthermore, in this embodiment, "configuring" radio parameters etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a base station or a terminal are set.

[0014] (System Configuration) Fig. 1 is a diagram for explaining a wireless communication system in this embodiment. As shown in Fig. 1, the wireless communication system in this embodiment includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0015] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. Furthermore, a TTI (Transmission Time Interval) in the time domain may be a slot, or a TTI may be a subframe.

[0016] The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via the NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as an SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell) and a primary cell (PCell) using Carrier Aggregation (CA). Furthermore, the terminal 20 may perform communication via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0017] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in FIG. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals. The terminal 20 may be referred to as a UE 20, and the base station 10 may be referred to as a gNB 10.

[0018] The Low-Power Wake Up Signal is called LP-WUS or simply WUS, and the Low-Power Wake Up Receiver is called LP-WUR, WUR, or LR. The LR, a simple circuit that operates with lower power consumption than the Main Radio (MR) used in normal data communications, operates as a replacement for the MR, introducing a state called Ultra-Deep Sleep. The LR may have a function that triggers the power OFF of the MR or the power ON of the MR when it receives an LP-WUS signal.

[0019] The agreement on the scope of application of LP-WUS / WUR in 3GPP Rel-19 is shown below.

[0020] To specify a LP-WUS design that is commonly applicable to both RRC IDLE / INACTIVE and RRC CONNECTED modes, an LP-WUS is specified that is based on an OOK (OOK-1 and / or OOK-4) waveform, with an OFDM sequence overlaid on the OOK symbols as needed. At a minimum, duty cycle monitoring of the LP-WUS must be supported. In IDLE / INACTIVE operation, the same information must be delivered regardless of the type of LP-WUS, and the OFDM sequence may carry the information.

[0021] In RRC IDLE / INACTIVE mode, - Specifying the procedures and configurations for LP-WUS to indicate paging monitoring triggered by LP-WUS, including at least the configuration, subgrouping and entry / exit conditions for LP-WUS monitoring.

[0022] - For synchronization and / or serving cell RRM, the LP-WUR is assigned an LP-SS with a periodicity of Y [ms]. The LP-SS is based on OOK-1 and / or OOK-4 waveforms, with or without an OFDM sequence overlay. The choice of whether or not to overlay the OFDM sequence will be further determined within this work item (WI). For LP-WURs that can receive existing PSS / SSS, the existing PSS / SSS can be used instead of the LP-SS for synchronization and RRM.

[0023] - Specify further relaxation of UE MR RRM for both serving and neighbor cell measurements and offloading of UE serving cell RRM measurements from MR to LP-WUR, including the necessary conditions.

[0024] In RRC CONNECTED mode, it specifies the procedure to enable UE MR PDCCH monitoring triggered by LP-WUS, including the procedure to enable and disable LP-WUS monitoring. In CONNECTED mode, UE MR ultra-deep sleep is not considered, and UE RRM / RLM / BFD / CSI measurements are performed by MR.

[0025] The target coverage of LP-WUS and LP-SS is the PUSCH coverage of message 3. Optimization of LP-WUS signal design for idle / inactive mode takes priority over optimization for connected mode.

[0026] Furthermore, 3GPP Rel-19 is considering the possibility of LP-WUS being quasi-co-located (QCL) with existing NR signals / channels / TCI states of CORESET during LP-WUS monitoring in RRC CONNECTED mode. It is being considered whether these existing NR configurations can be QCL sources for LP-WUS.

[0027] The following agreement was reached at the 3GPP RAN1#120bis meeting in April 2025. Specifically, Rel-19 allows UEs to support LP-WUS even if they do not support the unified TCI framework in Rel-17. In such cases, the following two methods are being considered for configuring the LP-WUS TCI state: "RRC provides the UE with a CORESET ID, and the UE derives the LP-WUS TCI state based on this," or "RRC configures K TCI states for LP-WUS, and a new MAC-CE activates one of them."

[0028] On the other hand, Rel-19 also supports cases where a UE supports both the Rel-17 unified TCI framework and LP-WUS. When the Rel-17 unified TCI framework is configured by RRC, LP-WUS is transmitted according to the TCI state indicated by MAC-CE or DCI, just like other downlink channels / signals (no change to the DCI format is required). When the unified TCI framework is not configured, the application of either "a method in which RRC provides a CORESET ID" or "a method in which RRC configures K TCI states and activates them in MAC-CE" is being considered.

[0029] Furthermore, it was agreed that for monitoring LP-WUS in RRC CONNECTED mode, one or both of SSB (Synchronization Signal Block) and / or CSI-RS (Channel State Information Reference Signal) can be used as quasi-co-location (QCL) sources for LP-WUS, with Type C and Type D being used as QCL types depending on the applicable circumstances.

[0030] Here, QCL and TCI will be explained.

[0031] QCL is an index that indicates that multiple signals or channels are quasi-colocated, i.e., that certain large-scale properties can be assumed to match. Signals in a QCL relationship can be assumed to match at least one of the following: Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters.

[0032] In the 3GPP standard, four types of QCLs are specified to define the relationship between QCLs, as shown in Figure 2.

[0033] - QCL-Type A: Doppler shift, Doppler spread, mean delay, delay spread - QCL-Type B: Doppler shift, Doppler spread - QCL-Type C: Doppler shift, mean delay - QCL-Type D: Spatial Rx parameters They are used to estimate or set spatial or temporal reception conditions for a particular physical channel or reference signal.

[0034] The TCI is an indicator that indicates that a CSI-RS (Channel State Information Reference Signal) or a DMRS (Demodulation Reference Signal) of a PDSCH / PDCCH is configured with reference to the large-scale characteristics (QCL) of one or two specific reference signals (SSB index or NZP-CSI-RS resource). That is, the QCL relationship with a specific RS is indicated to a terminal via the TCI, and the terminal can perform beam selection and reception operations based on the indicated QCL relationship.

[0035] 3 is a diagram showing an example of the TCI configuration and each parameter in the TCI state. The TCI state (TCI-State) describes the spatial reception setting based on the QCL relationship and is set for each signal or channel. The TCI state is also called spatial relation information including spatial reception parameters and beam information, and is set in the UE via an RRC signal or MAC control information.

[0036] FIG. 4 is a diagram showing Source RSs (source reference signals) and QCL types having QCL relationships when the Target RS (target reference signal) is a PDCCH / PDSCH DMRS in 3GPP Rel-15 / Rel-17. The Target RS is a signal to which a QCL is applied. The Source RS is a signal that serves as a basis for assuming the radio characteristics of the Target RS in the QCL. Index #0 in FIG. 4 specifies that the UE receives the PDCCH / PDSCH DMRS assuming that the radio characteristics of the PDCCH / PDSCH DMRS, which is the Target RS, match the radio characteristics of the SSB, which is the Source RS. The radio characteristics of the SSB that are assumed to match are QCL-Type A, and include the Doppler shift, Doppler spread, average delay, and delay spread.

[0037] The combinations of QCL type and RS type allowed in Rel-15 are any of the indexes #0-3 in Figure 4. The combinations of QCL type and RS type allowed in Rel-17 are any of the indexes #0-2 in Figure 4. The setting corresponding to index #0 in Figure 4 is not applicable to the TCI state only if the TCI state is not configured.

[0038] As shown in Fig. 4, Rel-15 / Rel-17 stipulate that a UE must assume that only QCL-Type A is supported for the PDCCH / PDSCH DMRS, which is a Target RS. On the other hand, 3GPP has agreed that QCL-Type C is supported for the LP-WUS, which is a Target RS.

[0039] In the past, it was unclear how the UE should assume the TCI state for the LP-WUS, so the UE may not be able to properly receive the LP-WUS using the QCL.

[0040] According to this embodiment, it is specified how the UE should assume the TCI state for the LP-WUS, and the UE can receive the LP-WUS appropriately using the QCL relationship.

[0041] In this embodiment, "the UE assumes..." means, for example, that the UE handles the information according to a specific value or condition in accordance with a prerequisite operation defined in the specification. That is, the operation "the UE assumes..." means that the UE performs the assumed processing required to maintain operational consistency based on the 3GPP standard, even when a certain configuration does not explicitly exist.

[0042] In this embodiment, the LP-WUS is an example of a low-power signal.

[0043] FIG. 5 is a flowchart showing an example of an operation procedure of the UE 20 in this embodiment.

[0044] In step S101, the UE 20 supports LP-WUS and / or LP-WUS is configured for the UE 20.

[0045] In step S102, it is determined whether a unified TCI framework is configured for the UE. The unified TCI framework is a method introduced in 3GPP Rel-17 for unifying the management of TCI stats that can be commonly applied to each physical channel of the downlink and uplink. In the unified TCI framework, multiple TCI states are configured for the UE 20 in advance, and the TCI state to be applied at any given time (hereinafter referred to as the indicated TCI state) from among these TCI states is indicated by the MAC CE or DCI. The unified TCI framework may also be referred to as the R17 unified TCI framework.

[0046] If the result of step S102 is No, then in step S103, a QCL type is assumed for the LP-WUS based on the first embodiment.

[0047] If the answer is Yes in step S102, in step S104, a QCL type is assumed for the LP-WUS based on the second embodiment.

[0048] Each embodiment and the operation examples included in each embodiment may be performed independently or in any combination.

[0049] (First embodiment) According to the first embodiment, if the UE 20 supports the LP-WUS but does not support the R17 unified TCI framework, the UE 20 may assume the following QCL types for the LP-WUS that is the Target RS:

[0050] If UE 20 supports LP-WUS, it may be the case that LP-WUS is configured for UE 20, or the case that UE 20 supports LP-WUS and LP-WUS is configured for UE 20.

[0051] If the UE 20 does not support the R17 unified TCI framework, it may be that the R17 unified TCI framework is not configured for the UE 20, or that the UE 20 does not support the R17 unified TCI framework and the R17 unified TCI framework is not configured for the UE 20.

[0052] (Alt.1-1) The UE 20 may assume that any combination of Source RS and QCL type is applied to the LP-WUS. For example, the following combinations, where SSB or CSI-RS is the Source RS and QCL-Type C or QCL-Type D is the QCL type, may be configured in the TCI State:

[0053] qcl-Type1 {type C with SSB} and qcl-Type2 {type D with SSB} qcl-Type1 {type C with CSI-RS} and qcl-Type2 {type D with SSB} qcl-Type1 {type C with SSB} and qcl-Type2 {type D with CSI-RS} qcl-Type1 {type C with CSI-RS} and qcl-Type2 {type D with CSI-RS} In the above, for example, {type C with SSB} indicates that the QCL type applied to the LP-WUS is QCL-Type C and the Source RS is SSB. For example, qcl-Type1 {type C with SSB} indicates that the combination of QCL-Type C and SSB is qcl-Type1.

[0054] In the above, qcl-Type2, which indicates a combination of QCL-Type D and Source RS, may be set arbitrarily if applicable.

[0055] In the above, the CSI-RS may be a CSI-RS used for BM (Beam Management), TRS (Tracking Reference Signal), or CSI (Channel State Information).

[0056] In this embodiment, the BM, TRS, and CSI are examples of types of CSI. In this embodiment, the CSI-RS used for the BM, TRS, and CSI are denoted as CSI-RS BM, CSI-RS TRS, and CSI-RS CSI, respectively.

[0057] (Alt.1-2) The UE 20 may assume that restricted combinations of Source RSs and QCL types are applied to the LP-WUS that is the Target RS. For example, as shown in Fig. 6, certain restrictions may be added to the RS type, CSI-RS type, QCL type, and RS combinations between qcl-Type1 and qcl-Type2 that are applied to the LP-WUS that is the Target RS.

[0058] As shown in FIG. 6, the qcl-type1 applied to the LP-WUS that is the Target RS may be QCL-Type C regardless of the type of the Source RS#1.

[0059] As shown in FIG. 6, for example, CSI-RS type may be set to CSI-RS BM, CSI-RS TRS, or CSI-RS CSI.

[0060] In Fig. 6, the setting corresponding to index #0 may be a setting for the TCI state, or may not be a setting for the TCI state. Even if the TCI state is not set or instructed for the UE 20, the UE 20 may operate assuming a QCL relationship in a specific case or scenario (e.g., default reception setting or when receiving LP-WUS). In other words, even if the TCI state is not set, the UE 20 may perform channel estimation, etc. based on the QCL assumption (implicit setting).

[0061] In FIG. 6, the settings corresponding to indexes #1-#3 may be TCI state settings that are set or instructed to the UE 20.

[0062] The CSI-RS BM may be a CSI-RS resource in the NZP-CSI-RS-ResourceSet configured in the higher layer parameter "repetition".

[0063] The CSI-RS TRS may be a CSI-RS resource in the NZP-CSI-RS-ResourceSet configured in the higher layer parameter "trs-Info".

[0064] The CSI-RS CSI may be a CSI-RS resource in the NZP-CSI-RS-ResourceSet that is not configured in either the higher layer parameter "repetition" or "trs-Info".

[0065] The antenna port QCL for Alt.1-2 may be defined in a standard (for example, the 3GPP standard) as in the example of FIG.

[0066] If LP-WUS monitoring is configured for the UE and dl-OrJointTCI-StateList is not configured, the UE shall assume that the TCI state for LP-WUS indicates one of the following QCL types:

[0067] - 'typeC' applied to the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured in the higher layer parameter trs-Info and, if applicable, 'typeD' applied to the same CSI-RS resources or - 'typeC' applied to CSI-RS resources in the NZP-CSI-RS-ResourceSet configured in the higher layer parameter trs-Info and, if applicable, 'typeD' applied to CSI-RS resources in another NZP-CSI-RS-ResourceSet configured in the higher layer parameter repetition, or - 'typeC' applied to CSI-RS resources in the NZP-CSI-RS-ResourceSet that are not configured in either trs-Info or repetition, and 'typeD' applied to the same CSI-RS resources, if applicable. "dl-OrJointTCI-StateList" is a parameter set in UE 20 by RRC (Radio Resource Control) signaling, and is a list of TCI states including either a downlink-specific TCI state (DL TCI state) or a TCI state common to downlink and uplink (Joint TCI state), or both. "dl-OrJointTCI-StateList" complies with the unified TCI framework introduced in Rel-17, and a specific TCI state (so-called indicated TCI state) from among the TCI states included in this list is dynamically applied to UE 20 by instructions using MAC CE or DCI.

[0068] (Second embodiment) According to the second embodiment, if the UE 20 supports LP-WUS and supports the R17 unified TCI framework, the UE 20 may assume the following QCL types for the LP-WUS that is the Target RS:

[0069] If UE 20 supports LP-WUS, it may be the case that LP-WUS is configured for UE 20, or the case that UE 20 supports LP-WUS and LP-WUS is configured for UE 20.

[0070] If the UE 20 supports the R17 unified TCI framework, it may be the case that the R17 unified TCI framework is configured for the UE 20, or the case that the UE 20 supports the R17 unified TCI framework and the R17 unified TCI framework is configured for the UE 20.

[0071] (Alt.2-1) As in Alt.1-1 above, the UE 20 may assume that any combination of Source RS and QCL type is applied to the LP-WUS. For example, the following combinations, in which SSB or CSI-RS is the Source RS and QCL-Type C or QCL-Type D is the QCL type, may be configured in the TCI State. Each embodiment in Alt.1-1 may also be applied to Alt.2-1.

[0072] qcl-Type1 {type C with SSB} and qcl-Type2 {type D with SSB} qcl-Type1 {type C with CSI-RS} and qcl-Type2 {type D with SSB} qcl-Type1 {type C with SSB} and qcl-Type2 {type D with CSI-RS} qcl-Type1 {type C with CSI-RS} and qcl-Type2 {type D with CSI-RS}

[0073] (Alt.2-2) As in Alt.1-2 above, the UE 20 may assume that a combination of a restricted Source RS and a QCL type is applied to the LP-WUS that is the Target RS. Each embodiment in Alt.2-1 may also be applied to Alt.2-1.

[0074] (Alt.2-3) Previously, when the R17 unified TCI framework was configured in the UE 20, QCL-type A was not supported as a QCL type. According to Alt. 2-3, support for QCL-type A is enabled as an exception in the R17 unified TCI framework.

[0075] A UE 20 configured with both the LP-WUS and the R17 unified TCI framework may assume that QCL-type A is applied to the LP-WUS that is the Target RS. As shown in Fig. 8, when both the LP-WUS and the R17 unified TCI framework are configured for the UE 20, the qcl-type 1 applied to the LP-WUS that is the Target RS may be QCL-Type A regardless of the type of Source RS#1.

[0076] As shown in FIG. 8, for example, CSI-RS type may be set to CSI-RS BM, CSI-RS TRS, or CSI-RS CSI.

[0077] In Fig. 8, the setting corresponding to index #0 may be a setting for the TCI state, or may not be a setting for the TCI state. Even if the TCI state is not set or instructed for the UE 20, the UE 20 may operate assuming a QCL relationship in a specific case or scenario (e.g., default reception setting or when receiving LP-WUS). In other words, even if the TCI state is not set, the UE 20 may perform channel estimation, etc. based on the QCL assumption (implicit setting).

[0078] In FIG. 8, the settings corresponding to indexes #1-#3 may be TCI state settings that are set or instructed to the UE 20.

[0079] The CSI-RS BM may be a CSI-RS resource in the NZP-CSI-RS-ResourceSet configured in the higher layer parameter "repetition".

[0080] The CSI-RS TRS may be a CSI-RS resource in the NZP-CSI-RS-ResourceSet configured in the higher layer parameter "trs-Info".

[0081] The CSI-RS CSI may be a CSI-RS resource in the NZP-CSI-RS-ResourceSet that is not configured in either the higher layer parameter "repetition" or "trs-Info".

[0082] The antenna port QCL for Alt.2-3 may be defined in a standard (for example, the 3GPP standard) as shown in the example of FIG.

[0083] If LP-WUS monitoring and dl-OrJointTCI-StateList are configured for the UE, the UE shall assume that the indicated TCI state for LP-WUS indicates one of the following QCL types: The indicated TCI state is the TCI state dynamically specified by the MAC CE and / or DCI to apply to a specific physical channel or signal from among multiple TCI states preconfigured by the unified TCI framework.

[0084] - 'typeC' applied to the CSI-RS resources in the NZP-CSI-RS-ResourceSet configured in the higher layer parameter trs-Info and, if applicable, 'typeD' applied to the same CSI-RS resources or 'type C' applied to CSI-RS resources in the NZP-CSI-RS-ResourceSet configured in the upper layer parameter trs-Info and, if applicable, 'type D' applied to CSI-RS resources in another NZP-CSI-RS-ResourceSet configured in the upper layer parameter repetition (Alt.2-4) When the indicated TCI state sets QCL-typeA, UE 20 may assume that QCL-typeC (or characteristics related to QCL-typeC, e.g., mean delay, Doppler shift) of the Source RS is applied to the Target RS, LP-WUS.

[0085] 10 is a sequence diagram showing an example of an operation procedure of a wireless communication system in the second embodiment (Alt. 2-4). In step S201, the gNB 10 transmits an indicated TCI state in which QCL-type A is set to the UE 20. In step S202, the UE 20 assumes that QCL-type C or at least some of the characteristics related to QCL-type C are applied to the LP-WUS that is the Target RS. Note that transmitting or receiving a TCI state may mean transmitting or receiving information related to the TCI state (for example, information that explicitly or implicitly indicates the TCI state).

[0086] When a TCI state is configured based on a Source RS having a QCL-Type A relationship, when the TCI state is instructed and applied to the UE 20, the UE 20 may assume that the QCL-Type C characteristics of the Source RS are applied to the LP-WUS, which is the Target RS. The characteristics specified by QCL-Type A are "Doppler shift, Doppler spread, mean delay, and delay spread." The UE 20 may only apply the specific "mean delay and Doppler shift" specified by QCL-Type C.

[0087] When a TCI state is configured based on a Source RS having a QCL-Type A relationship, when that TCI state is instructed and applied to UE 20, UE 20 may assume that QCL-type A of the Source RS applies to RSs / channels other than LP-WUS.

[0088] As an example 1 of Alt. 2-4, when a TCI state configured based on qcl-Type1 {type A with CSI-RS TRS} and qcl-Type2 {type D with CSI-RS TRS} is instructed and applied to UE 20 by the unified TCI framework, UE 20 may assume the following:

[0089] - For the LP-WUS, a TCI state configured based on qcl-Type1 {type C with CSI-RS TRS} and qcl-Type2 {type D with CSI-RS TRS} is applied, i.e., the UE 20 assumes that the QCL type applied to the LP-WUS is replaced from QCL-Type A to QCL-Type C.

[0090] - For RS / channels other than LP-WUS, qcl-Type1 {type A with CSI-RS TRS} and qcl-Type2 {type D with CSI-RS TRS} are applied.

[0091] As an example 2 of Alt. 2-4, if the TCI state is not set in the target BWP (Bandwidth Part) / CC (Component Carrier) where the LP-WUS is set / transmitted or the TCI state is applied, the UE 20 may apply the TCI state from the reference BWP of the reference CC.

[0092] The reference BWP / CC for the LP-WUS may be determined by reusing the conventional (existing) setting (for example, the setting by the conventional (existing) parameter "unifiedTCI-StateRef").

[0093] The reference BWP / CC for the LP-WUS may be determined based on instructions from individual configuration by the gNB 10 (e.g., configuration by the new parameter "unifiedTCI-StateRef-LPWUS").

[0094] The UE 20 may apply the TCI state from the reference CC of the reference BWP indicated by "unifiedTCI-StateRef-LPWUS" for the LP-WUS. The UE 20 may apply the TCI state from the reference CC of the reference BWP indicated by "unifiedTCI-StateRef" for RSs / channels other than the LP-WUS.

[0095] The antenna port QCL for Example 2 of Alt. 2-4 may be defined in a standard (for example, the 3GPP standard) as in the example of FIG.

[0096] If there is no TCI-State or TCI-UL-State setting in the BWP in the CC and LP-WUS monitoring is not configured for the UE, the UE may apply the TCI-State or TCI-UL-State setting in the referenced BWP of the referenced CC set by unifiedTCI-StateRef.

[0097] If there is no TCI-State or TCI-UL-State setting in the BWP within the CC and LP-WUS monitoring is configured for the UE, the UE can apply the TCI-State or TCI-UL-State setting in the reference BWP of the reference CC set by unifiedTCI-StateRef-LPWUS to the LP-WUS, and can apply the TCI-State or TCI-UL-State setting in the reference BWP of the reference CC set by unifiedTCI-StateRef to RSs and channels other than the LP-WUS.

[0098] As an example 3 of Alternative 2-4, if the BWP / CC ID of the QCL source is not set, the QCL Source RS may be an RS with the same RS ID in the target BWP / CC. The UE 20 may derive QCL-TypeA / TypeC / TypeD from the same RS ID in the target BWP / CC.

[0099] The antenna port QCL for Example 3 of Alt. 2-4 may be defined in a standard (for example, the 3GPP standard) as in the example of FIG.

[0100] If the bwp-id or cell for a Source RS of QCL-Type A / Type D is not configured in the QCL-Info of the TCI state, and LP-WUS monitoring is not configured for the UE, the UE shall assume that the Source RS of QCL-Type A / Type D is configured within the CC / downlink BWP (DL BWP) to which the TCI state applies.

[0101] If the bwp-id or cell for a Source RS of QCL-Type A / Type C / Type D is not configured in the QCL-Info of the TCI state and LP-WUS monitoring is configured for the UE, the UE shall assume that the Source RS of QCL-Type A / Type C / Type D is configured within the CC / DL BWP to which the TCI state applies.

[0102] (Alt.2-5) If a TCI state including QCL-typeA is indicated or configured for the UE 20, the UE 20 may assume that the TCI state or QCL type including QCL-typeA is not valid.

[0103] When a TCI state including QCL-type A is instructed or configured for UE 20, UE 20 may assume that the TCI state or QCL type including QCL-type A does not apply or does not apply to the LP-WSU that is the Target RS.

[0104] 13 is a sequence diagram showing an example of an operation procedure of a wireless communication system in the second embodiment (Alt. 2-5). In step S211, the gNB 10 transmits a TCI state including QCL-type A to the UE 20. In step S212, the UE 20 assumes that the TCI state including QCL-type A is not applied to the LP-WUS, which is the Target RS.

[0105] In Alt. 2-5, if the TCI state or QCL type is not applied, the UE 20 may assume the QCL relationship for LP-WUS in the third embodiment described later.

[0106] For example, for UE 20, if a TCI state configured based on qcl-Type1 {type A with CSI-RS TRS} and qcl-Type2 {type D with CSI-RS TRS} is indicated and applied by the unified TCI framework, UE 20 may consider the following options:

[0107] Option 1: qcl-Type1 is not applied to LP-WUS, and qcl-Type2 is applied to LP-WUS.

[0108] Option 1a: qcl-Type1 is not applied to the LP-WUS and other RSs / channels, and qcl-Type2 is applied to the LP-WUS and other RSs / channels.

[0109] Option 2: The entire TCI state, including qcl-Type1 and qcl-Type2, is not applied to LP-WUS.

[0110] Option 2a: The entire TCI state including qcl-Type1 and qcl-Type2 is not applied to LP-WUS and other RS / channels.

[0111] (Third embodiment) In the third embodiment, another example of UE assumption regarding QCL will be described. The third embodiment may be performed independently or in combination with the first or second embodiment.

[0112] (Alt.3-1) The UE 20 may assume that the QCL of the LP-WUS follows the QCL assumption of the CORESET ID. One or more CORESET IDs may be indicated to the UE 20, and the UE 20 may derive the active TCI state of the LP-WUS based on the one or more CORESET IDs.

[0113] (Alt.3-2) The UE 20 may assume that the QCL of the LP-WUS is indicated based on the respective indicated TCI state / activated TCI state, and the UE 20 may be instructed to use one TCI state for the LP-WUS.

[0114] (Alt.3-3) The UE 20 may assume that the LP-WUS is QCL'd with the SSB that the UE 20 identified during the initial access procedure.

[0115] The UE 20 may assume one or more of the above Alt.3-1 to Alt.3-3 in one or more of the following cases:

[0116] Case 1: The TCI state (including the unified TCI state) is not valid, does not apply, or does not apply to the LP-WUS (e.g., Alt. 2-5 in the second embodiment). Case 2: The TCI state to be applied includes a QCL type (e.g., QCL-typeA) that is not supported for LP-WUS. Case 3: The TCI state is set before the indicated or activated TCI state is applied. Case 4: After the UE 20 receives an initial upper layer configuration including multiple TCI states, but before the indicated TCI state or activated TCI state is applied from the received TCI state. Case 5: After the UE 20 receives an upper layer configuration including multiple available TCI states as part of a reconfiguration with sync procedure, but before the indicated TCI state or activated TCI state is applied from the received TCI state. The QCL relationship applied in the third embodiment may be at least one of QCL-TypeA, QCL-TypeB, QCL-TypeC, or QCL-TypeD.

[0117] The UE 20 may assume that one or more of Alt.3-1 to Alt.3-3 above are used when the R17 unified TCI framework is supported and / or configured.

[0118] The UE 20 may assume that one or more of Alt.3-1 to Alt.3-3 above are used even when the R17 unified TCI framework is not supported and / or configured.

[0119] The antenna port QCL for Alt.3-3 may be defined in a standard (for example, the 3GPP standard) as shown in the example of FIG.

[0120] CR Version 1 (based on the initial access procedure) For a UE configured for LP-WUS monitoring, after the UE receives an initial high-layer parameter configuration of dl-OrJointTCI-StateList in which multiple TCI-States are available as the indicated TCI state, and before the indicated TCI state from the configured TCI-State is applied, the UE shall assume that the LP-WUS to which the indicated TCI state applies is QCL'd with the SS / PBCH block identified by the UE during the initial access procedure.

[0121] CR Version 2 (based on the initial access procedure, with QCL type designation) For a UE configured for LP-WUS monitoring, after the UE receives an initial high layer parameter configuration of dl-OrJointTCI-StateList in which multiple TCI-States are available as the indicated TCI state, and before the indicated TCI state from the configured TCI-State is applied, the UE shall assume that the LP-WUS to which the indicated TCI state applies is QCL'd with the SS / PBCH block identified by the UE during the initial access procedure with qcl-Type set to "type C", if applicable, or with qcl-Type set to "type D", if applicable.

[0122] CR Version 1 (based on Reconfiguration with sync) For a UE configured for LP-WUS monitoring, after the UE receives, as part of the Reconfiguration with sync procedure described in TS 38.331, a higher layer configuration in dl-OrJointTCI-StateList where multiple TCI-States are available as the indicated TCI state, but before the indicated TCI state from the configured TCI-State is applied, the UE shall assume that the LP-WUS to which the indicated TCI state applies is QCL'd with the SS / PBCH block or CSI-RS resource identified by the UE during the random access procedure initiated by the Reconfiguration with sync procedure.

[0123] CR Version 2 (based on Reconfiguration with sync, with QCL type specification) For a UE configured for LP-WUS monitoring, after the UE receives, as part of the Reconfiguration with sync procedure described in TS 38.331, a higher layer configuration in dl-OrJointTCI-StateList where multiple TCI-States are available as the indicated TCI state, but before the indicated TCI state from the configured TCI-State is applied, the UE shall assume that the LP-WUS to which the indicated TCI state applies is QCL'd with the SS / PBCH block or CSI-RS resource identified by the UE during the random access procedure initiated by the Reconfiguration with sync procedure, with qcl-Type set to "type C", as applicable, or with qcl-Type set to "type D", as applicable.

[0124] In this embodiment, the UE 20 may report the capability information (UE capability) of the UE to the network (e.g., the gNB 10). The capability information may include, for example, at least one of the following:

[0125] - Capabilities related to each of the above-mentioned embodiments (information indicating that each embodiment is supported) - Capabilities related to each option or combination of options in each embodiment - Capabilities related to each Alt. or combination of Alt. in each embodiment The UE 20 may report the above capability information in frequency units, which may include at least one of UE units, FR1, FR2, FR2-1, FR2-2, FR3, subcarrier spacing (SCS), frequency band, BC, FC, or FSPC units.

[0126] The UE 20 may report the above capability information on a cell-by-cell basis, which may include at least one of a UE-by-UE, a cell-by-cell, or a TDD or FDD-by-cell basis.

[0127] In this embodiment, the UE 20 may receive the following types of information from the network (e.g., gNB 10):

[0128] - Information via higher layer signaling (e.g., RRC messages / LPP messages) - MAC CE The MAC CE may be a MAC CE having a new LCID in the subheader, or may be a MAC CE that is an extension of an existing MAC CE (for example, a MAC CE in which a new octet is introduced).

[0129] - DCI The DCI field may be an existing DCI field or a newly introduced DCI field. The DCI may be a DCI in which the CRC is scrambled with the existing RNTI or a newly introduced RNTI. The DCI format may be an existing DCI format or a newly introduced DCI format. A combination of these may be applied to the DCI.

[0130] In this embodiment, the UE 20 may receive information from the network periodically, semi-persistently (triggered by UE or gNB instruction) or aperiodically (triggered by UE or gNB instruction).

[0131] According to the above embodiment, it is possible to clarify the method of applying the TCI state and QCL type to the LP-WUS, and it is possible to receive the LP-WUS using the QCL relationship.

[0132] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station (gNB 10) 10 and the terminal (UE 20) 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0133] <Base station (gNB)> Fig. 15 is a diagram showing an example of the functional configuration of the base station 10 in this embodiment. As shown in Fig. 15, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 15 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations in this embodiment. The transmitting unit 110 and the receiving unit 120 may be collectively referred to as a communication unit.

[0134] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitter 110 also transmits setting information, instructions, notifications, etc. related to a low-power wake-up signal to the terminal 20. The transmitter 110 also transmits notifications related to switching of monitoring operations to the terminal. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

[0135] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information on the operations explained in the embodiments.

[0136] The control unit 140 controls the settings, instructions, and notifications related to the operations described in the embodiments. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0137] <Device (UE)> Fig. 16 is a diagram showing an example of the functional configuration of the terminal 20 in this embodiment. As shown in Fig. 16, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 16 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations in this embodiment. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.

[0138] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitter 210 also transmits capability information in a low-power wake-up signal to the base station 10. The receiver 220 wirelessly receives various signals and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The receiver 220 also receives paging notification information and setting information, instructions, and notifications related to the low-power wake-up signal from the base station 10. For example, the receiver 220 receives a low-power wake-up signal from the base station 10. The setting unit 230 stores various setting information received by the receiver 220 from the base station 10. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information on the operations described in the embodiments.

[0139] As described in the embodiments, the control unit 240 controls settings, instructions, and notifications related to the operations described in the embodiments. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

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

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

[0142] In the present disclosure, the term "apparatus" may be interchangeable with any two terms selected from a set of terms such as circuit, device, unit, module, chip, means, etc. The hardware configurations of the base station 10 and the terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0143] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, memory 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls the reading, writing, or both reading and writing of data in the memory 1002 and storage 1003.

[0144] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, a baseband signal processing unit, a call processing unit, etc. may be realized by the processor 1001. Although only one processor 1001 is shown in the figure, there may be multiple processors.

[0145] The processor 1001 also reads programs (program codes), software modules, data, etc. from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 401 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by a single processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line, or may be provided to the computer via the communication device 1004, for example.

[0146] The present disclosure also provides a computer program product including a computer program, which may implement the steps of the methods described in the above embodiments when the computer program is executed by a computer (e.g., the processor 1001).

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

[0148] Storage 1003 is a computer-readable recording medium, and may be, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, or a combination of at least two of these. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, memory 1002, storage 1003, or a database, server, or other appropriate medium including both memory 1002 and storage 1003.

[0149] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, or a combination of at least two of these. For example, a transmitting / receiving antenna, an amplifier unit, a transmitting / receiving unit, or a transmission path interface may be realized by the communication device 1004. The transmitting / receiving unit may be implemented as a transmitting unit and a receiving unit that are physically or logically separated.

[0150] The input device 1005 is an input device that accepts input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to the outside (for example, a display, a speaker, an LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

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

[0153] <Additional notes> (Additional note 1) a receiver for receiving a TCI state including a first QCL type from a base station; a controller that applies, to low-power signals, at least some of the characteristics associated with a second QCL type that is different from the first QCL type.

[0154] (Additional note 2) The terminal according to claim 1, wherein the control unit applies the first QCL type to signals other than the low-power signal.

[0155] (Additional note 3) the first QCL type is QCL type A; The terminal described in Supplementary Item 1, wherein the second QCL type is QCL Type C.

[0156] (Additional note 4) The terminal supports the integrated TCI framework, The terminal described in Supplementary Claim 1, wherein the TCI state is an indicated TCI state.

[0157] (Additional note 5) The terminal according to Supplementary Claim 1, wherein the control unit applies the TCI state set in the reference BWP or the reference component carrier to the low power signal when the TCI state is not set in the target BWP or the target component carrier.

[0158] (Additional note 6) A communication method performed by a terminal, comprising: receiving a TCI state from a base station, the TCI state including a first QCL type; and applying to the low-power signal at least some of the characteristics associated with a second QCL type that is different from the first QCL type.

[0159] Any of the above configurations clarifies how to apply the TCI state and QCL type to the LP-WUS, and enables reception of the LP-WUS using the QCL relationship.

[0160] (Supplementary explanation of the embodiment) Although the present embodiment has been described above, the disclosed invention is not limited to such an embodiment, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0161] The aspects / embodiments described in the present disclosure may be categorized as Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G-Advanced (5G-A), 6th generation mobile communication system (6G), xth generation mobile communication system (x is, for example, an integer or a decimal number)), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (O-RAN), Wideband Code Division Multiple Access (W-CDMA) (registered trademark), Global System for Mobile communications (GSM) (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) Engineers) 802.11, IEEE802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x=n it is called Wi-Fi4, when x=ac it is called Wi-Fi5, when x=ax it is called Wi-Fi6 or Wi-Fi6E, when x=be it is Wi-Fi7, and when x=bn it is called Wi-Fi8, etc. Wi-Fi is a registered trademark.), IEEE802.16 (WiMAX (registered trademark), IEEE802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), network virtualization technology (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Furthermore, each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Furthermore, "based on" naturally refers not only to a system that uses the technology, but also to a system that uses an extension or modification of the technology.

[0162] In the present disclosure, any two terms selected from a set of terms such as "base station (BS)", "radio base station", "fixed station (fixed station)", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point (AP)", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "radio unit (RU)", "remote unit (RU)", "control unit (CU)", "distributed unit (DU)", "remote radio head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "high altitude platform station (HAPS)", "airborne platform", "panel", "cell", "radio access network (RAN)", and "network" may be used interchangeably.

[0163] Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, or a super cell. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0164] In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE 20)", "Device", "Module" and "Terminal" may be used interchangeably.

[0165] A terminal may be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other suitable terminology.

[0166] The base station and the terminal may each be composed of one or more devices. The devices constituting at least a portion of the base station and the terminal may be called a transmitting device, a receiving device, a communication device, etc. Note that the devices constituting at least a portion of the base station and the terminal may be, for example, an object itself, such as a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, an excavator, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a handcar, a rickshaw, a ship and other watercraft, an airplane, a rocket, an unmanned aerial vehicle, a stratospheric base station (e.g., a High Altitude Platform Station (HAPS)), an artificial satellite (e.g., a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a Geostationary Earth Orbit (GEO) satellite), a drone (registered trademark), a multicopter, a quadcopter, a balloon, or an Internet of Things (IoT) device (e.g., a smart meter, a sensor), or may include, but are not limited to, an object or device mounted on the object. Furthermore, the object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is in a stationary state where it is not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").

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

[0168] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the earth (for example, in the atmosphere or outer space).

[0169] In addition, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 10 may be configured to have the functions of the terminal 20 described above.

[0170] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination of at least two of these. Note that the physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU), for example. Furthermore, the RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC message may be, for example, a message used for controlling an RRC connection (for example, setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a measurement report, or notification of a terminal's capabilities, or may be an information element within the message. Furthermore, notification of information may be explicit or implicit. Note that explicit notification of certain information means notification of the certain information itself, and implicit notification of certain information may mean notification of information other than the certain information, or may mean that the certain information is considered to have been notified when a certain condition is satisfied.Furthermore, notification of information may include not only notification between the same layers of different devices (e.g., between a lower layer or an upper layer of the base station 10 and the terminal 20) but also notification between different layers in the same or different devices (e.g., between a lower layer and an upper layer in the base station 10 or the terminal 20). Furthermore, notification of information from one device to another device may be performed via one or more devices. Regarding any information (e.g., a variable, a constant, a parameter, a setting) described in the present disclosure, even if not specifically stated in the above embodiments, information indicating / specifying (or related to) the any information (value) may be notified from any first device (e.g., a terminal / base station) to any second device (e.g., a base station / terminal).

[0171] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0172] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node or by some of its upper nodes (e.g., CU, RU, or DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) and 5GC (5G Core Network), and provides one or more network functions (NF: Network Functions), but is not limited to this.

[0173] Furthermore, in the present disclosure, the operation of "a terminal receives information from a base station" accompanies the operation of "the base station transmits the information to the terminal," "the base station generates the information," or both. Similarly, the operation of "a terminal transmits information to a base station" accompanies the operation of "the base station receives the information from the terminal." Furthermore, the operation of "the terminal is configured to ..." or "configure UE 20 to ..." may include the operation of "the base station transmits configuration information regarding the configuration of the terminal" and the operation of "the terminal configures a predetermined operation based on the configuration information."

[0174] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation.

[0175] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.

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

[0177] The radio resource may be defined by a combination of resource units in one or more domains, such as the time domain, the frequency domain, the spatial domain, the code domain, and the power domain.

[0178] For example, resources in the time domain may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. The time unit may be a fixed-length time unit independent of numerology, a variable-length time unit dependent on numerology, or both. Examples of fixed-length time units include, but are not limited to, a subframe consisting of one or more slots and a radio frame including multiple subframes. Examples of variable-length time units include, but are not limited to, a symbol and a slot including a fixed number of symbols. A certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, a minislot consisting of fewer symbols than the number of symbols constituting a slot. The above-described time units may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in the present disclosure may be read as another time unit.

[0179] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time, for example.

[0180] Resources in the frequency domain may be defined, for example, by one or more frequency units. The one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the terminology of the frequency units is not limited to these. The number of subcarriers included in a frequency unit may be a fixed number regardless of numerology, or may be a variable number that changes depending on numerology. For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. A BWP may be composed of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. One or more BWPs may be configured within one carrier for terminal 20, and at least one of the BWPs may be activated. Any frequency unit in the present disclosure may be interchangeable with another frequency unit.

[0181] Furthermore, resources in both the time domain and the frequency domain may be defined by one or more time / frequency units each consisting of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) consisting of one symbol and one subcarrier, a resource element group (REG) consisting of a predetermined number of REs, or a control resource set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0182] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units, including, but not limited to, a beam, a layer of MIMO (Multi-Input Multi-Output), an antenna port, or a combination of at least two of these.

[0183] Furthermore, the resources in the code domain may be defined by one or more code units, such as, but not limited to, a cyclic shift (CS), an orthogonal cover code (OCC), or a combination thereof.

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

[0185] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc. [Explanation of symbols]

[0186] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device

Claims

1. a receiving unit that receives a Transmission Configuration Indication (TCI) status including a first Quasi Co-Location (QCL) type from a base station; a controller that applies, to low-power signals, at least some of the characteristics associated with a second QCL type that is different from the first QCL type.

2. The terminal according to claim 1 , wherein the control unit applies the first QCL type to signals other than the low-power signal.

3. the first QCL type is QCL type A; The terminal of claim 1 , wherein the second QCL type is QCL Type C.

4. The terminal supports the integrated TCI framework, The terminal according to claim 1 , wherein the TCI state is an indicated TCI state.

5. The terminal according to claim 1, wherein the control unit applies the TCI state set in a reference BWP or a reference component carrier when a TCI state is not set in a target BWP (Bandwidth Part) or a target component carrier for the low power signal.

6. A communication method performed by a terminal, comprising: receiving a Transmission Configuration Indication (TCI) status from a base station, the TCI status including a first Quasi Co Location (QCL) type; and applying to the low-power signal at least some of the characteristics associated with a second QCL type that is different from the first QCL type.

Images