Terminal and communication method

Abstract

To clarify the terminal operation when an always-on SSB (SS / PBCH Block) is not transmitted in communication with a base station that can transition to a power saving state.SOLUTION: A terminal includes a control unit that supports an SSB (SS / PBCH Block)-less SCell (Secondary Cell) and an on-demand SSB, and a communication unit that receives settings related to an always-on SSB, and when the communication unit receives the on-demand SSB, the control unit assumes that the settings related to the always-on SSB do not include the absolute position of the frequency of the always-on SSB.SELECTED DRAWING: Figure 14

Description

[Technical Field]

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

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1).

[0003] Furthermore, in Release 18 of 3GPP (registered trademark), network energy savings has become increasingly important in order to achieve environmental sustainability, carbon neutrality, SDGs (Sustainable Development Goals), reduced operating costs, etc., and methods for saving energy are being considered (e.g., Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V18.4.0 (2024-12) [Non-patent document 2] "New WID: Network energy savings for NR", RP-223540, 3GPP TSG RAN Meeting #98-e, December 2022 [Non-patent document 3] 3GPP TS 38.331 V18.4.0 (2024-12) [Non-patent document 4] 3GPP TS 38.211 V18.5.0 (2024-12) [Non-Patent Document 5] 3GPP TS 38.213 V18.5.0 (2024-12) [Non-patent document 6] 3GPP TS 38.321 V18.4.0 (2024-12) [Non-Patent Document 7] 3GPP TS 38.214 V18.5.0 (2024-12) Summary of the Invention [Problem to be solved by the invention]

[0005] To achieve carbon neutrality and the SDGs, it is becoming increasingly important to reduce base station power consumption, and the introduction of discontinuous transmission / reception (DTX / RX) in base stations is being considered. A function (on-demand SSB case #1) has been added to enable or disable on-demand SSB without transmitting always-on SSB (SS / PBCH block). Meanwhile, an SSB-less SCell function has been added to acquire SSB transmitted from a PCell (primary cell) or another cell without transmitting SSB in an SCell (secondary cell). However, when always-on SSB is not configured, it was unclear whether to apply the SSB-less SCell function or on-demand SSB case #1.

[0006] The present invention has been made in consideration of the above points, and aims to clarify the terminal operation when an always-on SSB (SS / PBCH Block) is not being transmitted in communication with a base station that can transition to a power saving state. [Means for solving the problem]

[0007] According to the disclosed technology, a terminal is provided that has a control unit that supports SSB (SS / PBCH block)-less SCell (Secondary Cell) and on-demand SSB, and a communication unit that receives settings related to always-on SSB, and when the communication unit receives the on-demand SSB, the control unit assumes that the settings related to the always-on SSB do not include the absolute position of the frequency of the always-on SSB. [Effects of the Invention]

[0008] According to the disclosed technology, it is possible to clarify the terminal operation when an always-on SSB (SS / PBCH Block) is not transmitted in communication with a base station that can transition to a power saving state. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 2] This is a diagram to explain CDRX in NR Release 15. [Figure 3] FIG. 1 is a diagram for explaining WUS in NR Release 16. [Figure 4] FIG. 2 is a diagram illustrating discontinuous reception at a base station according to a first embodiment of the present invention. [Figure 5] FIG. 2 is a diagram for explaining each parameter according to Example 1 of the embodiment of the present invention. [Figure 6] FIG. 10 is a diagram illustrating discontinuous transmission by a base station according to a fifth embodiment of the present invention. [Figure 7] FIG. 10 is a diagram for explaining each parameter according to Example 5 of the embodiment of the present invention. [Figure 8] FIG. 13 is a sequence diagram illustrating an example (1) of OSI transmission according to a ninth embodiment of the present invention. [Figure 9] FIG. 13 is a sequence diagram illustrating an example (2) of OSI transmission according to a ninth embodiment of the present invention. [Figure 10] FIG. 13 is a diagram illustrating an example of an on-demand SSB according to a ninth embodiment of the present invention. [Figure 11] FIG. 13 is a sequence diagram illustrating an example of an operation related to an on-demand SSB according to a ninth embodiment of the present invention. [Figure 12] FIG. 13 is a sequence diagram illustrating an example of a random access procedure according to a ninth embodiment of the present invention. [Figure 13] FIG. 13 is a diagram for explaining an example of an SSB according to Example 9 of an embodiment of the present invention. [Figure 14] 16 is a flowchart illustrating an example (1) of SSB adaptation according to a tenth embodiment of the present invention. [Figure 15] 16 is a flowchart illustrating an example (2) of SSB adaptation according to a tenth embodiment of the present invention. [Figure 16] 16 is a flowchart illustrating an example (3) of SSB adaptation according to a tenth embodiment of the present invention. [Figure 17] 16 is a flowchart illustrating an example (4) of SSB adaptation according to a tenth embodiment of the present invention. [Figure 18] FIG. 2 is a diagram illustrating an example of a functional configuration of a base station according to an embodiment of the present invention. [Figure 19] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal according to an embodiment of the present invention. [Figure 20] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station or a terminal according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described 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.

[0011] In operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. The existing technologies include, but are not limited to, existing NR or LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

[0012] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, 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-".

[0013] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0014] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a base station or a terminal are set.

[0015] (System Configuration) Fig. 1 is a diagram for explaining a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention 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.

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

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

[0018] 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 also be referred to as a UE, and the base station 10 may also be referred to as a gNB.

[0019] Next, we will discuss the status of discussions on base station power saving in NR Release 18. Base station and terminal methods for improving network energy savings from both the base station transmission and reception perspectives are being considered. For example, methods are being considered for base stations to more efficiently achieve dynamic and / or semi-static finer-granularity adaptation of transmission and / or reception using network energy saving techniques in one or more of the time, frequency, space, and power domains using potential support / feedback from terminals and potential assistance information.

[0020] Next, discontinuous reception (DRX) or connected mode discontinuous reception (CDRX) in a conventional terminal will be described.

[0021] 2 is a diagram for explaining CDRX in NR Release 15. In CDRX operation in NR Release 15, a terminal monitors the PDCCH during a DRX-on period.

[0022] 3 is a diagram illustrating WUS in NR Release 16. In NR Release 16, a PDCCH-based wake-up signal (WUS) can instruct one or more terminals whether the terminals should monitor the PDCCH within the next DRX-on period.

[0023] DCI format 2_6, in which the CRC (Cyclic Redundancy Check) is scrambled by the PS-RNTI (Power Saving - Radio Network Temporary Identifier), is used as a PDCCH-based WUS and is also called DCP (DCI with CRC scrambled by PS-RNTI).

[0024] The WUS monitoring opportunity is set by an offset from the On Period based on the terminal capabilities. If the WUS indicates "inactive" (i.e., the terminal is not transmitting or receiving data), the terminal can skip monitoring during the On Period and immediately transition to sleep mode. In addition, a default terminal behavior can be configured for when the PDCCH-based WUS is not detected, for example due to a detection error.

[0025] DCI format 2_6 includes one bit of activation instruction information indicating "active" or "inactive."

[0026] (Previous problems) Next, we will explain the problems that have been encountered so far. In order to achieve carbon neutrality and the SDGs, it is becoming increasingly important to reduce the power consumption of base stations. However, there has been a problem in that there has been no standardization of methods for reducing the power consumption of base stations.

[0027] (Outline 1 of this embodiment) Therefore, in this embodiment, an example will be described in which the power consumption of a base station is reduced from the viewpoint of the time domain. As specific examples, examples 1 to 4 will be described below.

[0028] Example 1 In this embodiment, the operation of a base station when it receives signals intermittently and definitions of related concepts will be described.

[0029] 4 is a diagram for explaining the discontinuous reception of a base station according to Example 1 of an embodiment of the present invention. The period during which the base station 10 disables / enables the receiving unit is introduced as a discontinuous reception (gNB CDRX) function by the base station (hereinafter referred to as base station discontinuous reception).

[0030] The concept of discontinuous reception of the base station 10 is similar to that of the terminal 20. The reception units and / or parameters to be disabled may be for each port, panel, beam, or carrier (or cell).

[0031] 5 is a diagram for explaining each parameter according to Example 1 of the embodiment of the present invention. The base station CDRX may be defined by a plurality of parameters listed below. The unit of the parameters may be a symbol, a slot, a subframe, a millisecond, a second, or the like. The unit may be different or the same for each parameter. drx-onDurationTimer: Duration at the start of a DRX cycle drx-SlotOffset: Delay before starting drx-onDurationTimer drx-InactivityTimer: the period during which the terminal 20 performs uplink transmission after an uplink reception opportunity drx-LongCycleStartOffset: The long DRX cycle (i.e., drx-LongCycle) and drx-StartOffset that define when the long DRX cycle and short DRX cycle start. drx-ShortCycle: Short DRX cycle drx-ShortCycleTimer: the period during which the base station 10 follows the short DRX cycle drx-RetransmissionTimerUL: Maximum period until a grant for uplink retransmission is received drx-HARQ-RTT-TimerUL: Minimum period until an uplink retransmission grant is expected

[0032] When base station discontinuous reception is enabled, the base station 10 may receive an uplink channel transmitted from the terminal 20 when the drx-onDurationTimer, drx-InactivityTimer or drx-RetransmissionTimerUL is running.

[0033] If discontinuous base station reception is enabled, the terminal 20 may act in one of the following options.

[0034] <Option 1> The terminal 20 may perform an operation assuming discontinuous reception at the base station. Specifically, the terminal 20 identifies the status of discontinuous reception at the base station by RRC, MAC-CE, or DCI. In the case of DCI, it is assumed that the terminal 20 receives DCI indicating the status of discontinuous reception at the base station from the base station 10. Details of the instruction by DCI will be described later in a third embodiment.

[0035] When the base station discontinuous reception is enabled, the terminal 20 may transmit the uplink channel during the execution of the drx-onDurationTimer, the drx-InactivityTimer, or the drx-RetransmissionTimerUL.

[0036] <Option 2> The terminal 20 may ignore the DBR, specifically, the terminal 20 performs uplink transmissions as scheduled or configured by the base station 10, regardless of the status of the DBR.

[0037] When the base station 10 is enabled for discontinuous base station reception, the base station 10 may perform scheduling or settings that take discontinuous base station reception into consideration, or may perform scheduling or settings regardless of discontinuous base station reception. When scheduling or settings that take discontinuous base station reception into consideration are performed, the discontinuous base station reception function is realized even if the terminal 20 ignores discontinuous base station reception. Conversely, when scheduling or settings that take discontinuous base station reception into consideration are not performed, if the terminal 20 ignores discontinuous base station reception, unnecessary signal transmission occurs, resulting in wasted power consumption by the terminal 20.

[0038] On the other hand, if the base station discontinuous reception is disabled, the base station 10 may receive the uplink channel transmitted from the terminal 20 regardless of the base station discontinuous reception parameter. That is, the base station 10 may keep the receiving unit turned on and continuously receive the uplink channel from the terminal 20.

[0039] If discontinuous base station reception is disabled, the terminal 20 may act in one of the following options.

[0040] <Option 1> The terminal 20 may perform an operation assuming discontinuous reception at the base station. Specifically, the terminal 20 identifies the status of discontinuous reception at the base station by RRC, MAC-CE, or DCI. In the case of DCI, it is assumed that the terminal 20 receives DCI indicating the status of discontinuous reception at the base station from the base station 10. Details of the instruction by DCI will be described later in a third embodiment.

[0041] If discontinuous base station reception is disabled, the terminal 20 performs uplink transmissions as scheduled or configured by the base station 10, regardless of the status of discontinuous base station reception.

[0042] <Option 2> The terminal 20 may ignore the DBR, specifically, the terminal 20 performs uplink transmissions as scheduled or configured by the base station 10, regardless of the status of the DBR.

[0043] The base station 10 may also receive terminal assistance information in order to determine the values ​​of the aforementioned parameters that define the wake-up / sleep periods.

[0044] The terminal assistance information may be a period of terminal traffic. The base station 10 may receive the terminal assistance information at a higher layer. The base station 10 determines the value of the parameter by taking into account the terminal assistance information reported by the terminal 20.

[0045] The terminal 20 may transmit terminal assistance information, such as the period of terminal traffic, to the base station 10.

[0046] According to this embodiment, the base station 10 can achieve discontinuous reception.

[0047] Example 2 In this embodiment, an example of a method for triggering discontinuous reception from a base station will be described.

[0048] Enabling / disabling the base station discontinuous reception may be done by one of the following options:

[0049] <Option 1> The base station 10 may enable / disable the base station discontinuous reception when an RRC parameter indicating the enable / disable of the base station discontinuous reception is set by the terminal 20 or another network node (e.g., a core network or another base station, etc.).

[0050] <Option 2> The base station 10 may enable / disable the base station discontinuous reception when it receives a MAC-CE command indicating the enable / disablement of the base station discontinuous reception from the terminal 20 or another network node (e.g., a core network or another base station, etc.).

[0051] <Option 3> When receiving UCI included in the PUCCH or PUSCH from the terminal 20, the base station 10 may enable / disable the discontinuous reception at the base station based on the instruction to enable / disable the discontinuous reception at the base station included in the UCI.

[0052] The UCI including the instruction to enable / disable the base station discontinuous reception may be a UCI of a newly defined UCI type different from the conventional UCI, or the UCI may be a UCI of the same conventional type as the conventional UCI, such as HARQ-ACK, CSI, or SR.

[0053] The terminal 20 may transmit a PUCCH or PUSCH to the base station 10 to carry out an instruction (ie, activation / deactivation) of the discontinuous reception at the base station, thereby enabling / disabling the discontinuous reception at the base station.

[0054] The terminal 20 may receive DCI indicating the status of the discontinuous reception at the base station from the base station 10, in order to determine whether the instruction by the UCI has been successfully decoded by the base station 10 and whether there is a common understanding of the status of the discontinuous reception at the base station between the base station 10 and the terminal 20. Details of the DCI will be described later in a third embodiment.

[0055] <Option 4> The base station 10 may enable / disable the base station discontinuous reception when certain conditions are met. For example, the base station 10 may enable the base station discontinuous reception when the base station 10 does not receive an uplink channel from the terminal 20 for a certain period of time. The certain period of time may be a symbol, a slot, a subframe, a millisecond, a second, or the like.

[0056] The terminal 20 may receive DCI indicating the status of discontinuous reception at the base station from the base station 10, in order to obtain a common understanding of the status of discontinuous reception at the base station between the base station 10 and the terminal 20. Details of the DCI will be described later in a third embodiment.

[0057] <Option 5> The base station 10 may enable / disable the base station discontinuous reception by a combination of the above options.

[0058] Furthermore, the base station 10 may perform one of the following optional operations as a procedure for enabling / disabling the base station discontinuous reception.

[0059] <Option 1> The base station 10 may immediately enable / disable the discontinuous reception at the base station when any of the options that trigger the enable / disable of the discontinuous reception at the base station described above is executed.

[0060] <Option 2> The base station 10 may receive an instruction on the timing of enabling / disabling the base station discontinuous reception at a fixed time interval after receiving the instruction, or at a specified time. The time interval or time may be specified in units of symbols, slots, subframes, milliseconds, seconds, etc. In other words, the base station 10 may enable / disable the base station discontinuous reception at a specified time when one of the above-mentioned options that trigger the enabling / disabling of the base station discontinuous reception is executed.

[0061] <Option 3> The base station 10 may enable / disable the base station discontinuous reception based on a newly introduced timer. The enable / disable timers may be the same or different. The timer unit may be symbols, slots, subframes, milliseconds, seconds, etc. The base station 10, the terminal 20, or another network node may set the timer in RRC or specify it in MAC-CE or UCI / DCI.

[0062] That is, when any of the options that trigger the enabling / disabling of the base station discontinuous reception described above is executed, the timer is executed, and when the timer expires, the base station 10 may enable / disable the base station discontinuous reception.

[0063] The advantages of the timer are as follows: Even if an instruction to enable discontinuous reception at the base station is given, there may be cases where actual uplink transmission from the terminal 20 occurs with a certain delay after the instruction, due to processing by the terminal 20, etc. Even in such cases, by introducing a timer, discontinuous reception at the base station can be enabled after a certain time, thereby reducing the power consumption of the base station 10.

[0064] Furthermore, even if an instruction to disable discontinuous reception at the base station is given, there may be cases where actual uplink transmission from the terminal 20 continues to occur for a while after the instruction due to processing by the terminal 20. Even in such cases, by introducing a timer, the discontinuous reception at the base station can be disabled after a certain period of time, thereby improving the performance of the terminal 20.

[0065] According to this embodiment, it is possible to realize a trigger for base station discontinuous reception, and also to realize an operation for enabling / disabling the reception when the trigger is established.

[0066] Example 3 In this embodiment, an example will be described in which a terminal receives an instruction regarding discontinuous reception at a base station via DCI.

[0067] If the terminal 20 identifies the status of discontinuous reception at the base station and the terminal 20 and the base station 10 have a common understanding of the status, it is necessary to consider a mechanism for the base station 10 to indicate the status of discontinuous reception at the base station to the terminal 20. For timely indication, an indication by DCI is promising.

[0068] It should be noted that the advantage of having a common understanding is that when base station discontinuous reception is enabled, the terminal 20 can stop uplink transmission, thereby saving power consumption of the terminal 20.

[0069] A new RNTI may be introduced to indicate the status of the base station discontinuous reception. The new RNTI may be, for example, the gNB CDRX-RNTI (GC-RNTI).

[0070] Also, the introduction of the DCI field may be one of the following options:

[0071] <Option 1> A new DCI field may be introduced to indicate the status of the base station discontinuous reception. The bit size of the introduced DCI field may be 1 bit, with a "1" indicating a valid state and a "0" indicating an invalid state. The reverse may also be possible.

[0072] <Option 2> A new DCI field does not need to be introduced. That is, the status of the base station discontinuous reception may be indicated by an existing field. For example, if the corresponding DCI format is scrambled with a new RNTI such as GC-RNTI and the HPN and RV fields are all set to "0", the terminal 20 may identify that the status of the base station discontinuous reception is enabled.

[0073] Also, for example, if the corresponding DCI format is scrambled with a new RNTI such as GC-RNTI, the HPN and RV fields are set to all "0", and the MCS field is set to all "1", the terminal 20 may identify that the base station discontinuous reception status is disabled.

[0074] Also, the corresponding DCI format may be one of the following options:

[0075] <Option 1> It may be a DCI specific to the terminal 20.

[0076] <Option 1-1> The base station 10 may indicate the status of the base station discontinuous reception using a new DCI format that is different from the conventional format.

[0077] <Option 1-2> The base station 10 may indicate the status of base station discontinuous reception using conventional DCI formats 0_1, 0_2, 1_1, 1_2 or other DCI formats.

[0078] <Option 2> The DCI may be common to a group of terminals 20.

[0079] <Option 2-1> The base station 10 may indicate the status of the base station discontinuous reception using a new DCI format different from the conventional one. The above-mentioned new DCI field may be introduced in the new DCI format together with other new DCI fields for the power saving technique of the base station 10. The base station 10 may scramble the new DCI format with the above-mentioned new RNTI (e.g., GC-RNTI).

[0080] <Option 2-2> The base station 10 may indicate the status of the base station discontinuous reception using the conventional DCI format 2_6 or another group-wide DCI format.

[0081] Assuming that DCI format 2_6 is used, the conventional DCI fields of the DCI format may be reinterpreted to indicate the status of the base station discontinuous reception. For example, the "wake-up indication" may be reinterpreted. A valid state may be indicated by "1" and a invalid state by "0", or vice versa.

[0082] For differentiation, the base station 10 may scramble the DCI format 2_6 with the new RNTI (such as the GC-RNTI) described above instead of the PS-RNTI.

[0083] According to this embodiment, the terminal 20 can identify the status of the base station discontinuous reception, and the terminal 20 and the base station 10 can understand it in common.

[0084] Example 4 In this embodiment, an example will be described in which base stations and terminals mutually report capability information relating to base station discontinuous reception.

[0085] The following capability information may be introduced:

[0086] Base station capability information indicating the capabilities of the base station 10 may be introduced. That is, the base station 10 transmits the base station capability information to the terminal 20 or other network nodes. The terminal 20 or other network nodes that receive the base station capability information may assume the capabilities of the base station 10 based on the received base station capability information.

[0087] The base station capability information may include information indicating whether the base station supports discontinuous reception. Also, the base station capability information may be introduced to indicate whether a DCI indication indicating the status of discontinuous reception is supported.

[0088] The following terminal capability information may also be introduced. For example, terminal capability information indicating whether or not the base station discontinuous reception is supported may be introduced. Furthermore, terminal capability information indicating whether or not the base station discontinuous reception status identification may be introduced.

[0089] If the terminal 20 has a terminal capability that supports identifying the status of the base station discontinuous reception, the terminal 20 may identify whether the base station discontinuous reception function is enabled or disabled. For example, the terminal 20 may perform the operation of option 1 described in the first embodiment. Furthermore, if the terminal 20 does not have a terminal capability that supports identifying the status of the base station discontinuous reception, the terminal 20 may perform the operation of option 2 described in the first embodiment.

[0090] Also, terminal capability information indicating whether or not a DCI indication indicating the status of discontinuous reception at a base station is supported may be introduced. Also, terminal capability information indicating whether or not a new terminal-specific / group-common DCI format is supported may be introduced.

[0091] The dependency between the base station capability information and the terminal capability information may be one of the following options:

[0092] <Option 1> To apply the base station discontinuous reception, both the base station capability information and the terminal capability information indicating that the base station discontinuous reception is supported may need to be reported.

[0093] <Option 2> To apply the base station discontinuous reception, it may be sufficient to report only either the base station capability information or the terminal capability information indicating that the base station discontinuous reception is supported.

[0094] According to this embodiment, the base station and the terminal can mutually report capability information regarding the base station discontinuous reception.

[0095] The terminal capabilities in the above-described embodiments may be limited to cases where the terminal 20 is a reduced-function terminal, or may be applied to cases where the terminal 20 is not a reduced-function terminal.

[0096] (Outline 2 of this embodiment) Also, cell DTX (Discontinuous Transmission) / DRX (Discontinuous Reception) is being considered to reduce power consumption in the base station 10. For example, alignment of cell DTX / DRX with UE-DRX in RRC connected mode, information exchange between nodes regarding cell DTX / DRX, etc. are being considered. Note that cell DTX / DRX may be replaced with cell DTX and cell DRX, or may be replaced with cell DTX or cell DRX.

[0097] The mechanism for enabling or disabling the transceiver units of the base station 10 is important to reduce the power consumption of the base station 10. To reduce the power consumption of the base station 10, the adaptation of DL transmission and UL reception has been considered.

[0098] Cell DTX / DRX is useful for achieving adaptation of DL transmission and UL reception. However, the details of the operation of cell DTX / DRX have not been clear. Therefore, hereinafter, examples 5 to 8 will be described as specific examples related to cell DTX / DRX.

[0099] Example 5 In Example 5, a definition of cell DTX / DRX will be described. Cell DRX may be defined as in Examples 1 to 4 above. Whether cell DRX is performed is determined by higher layer parameters, and a period, a start slot, an offset, and a duration may be set. Furthermore, whether cell DRX is applicable may be determined by a semi-static, dynamic, or flexible network state.

[0100] Cell DTX may be defined as described below. Whether cell DTX is performed is determined by higher layer parameters, and the period, start slot, offset, and duration may be configured. Furthermore, whether cell DTX is applicable may be determined by semi-static, dynamic, or flexible network conditions.

[0101] <Option 1> 6 is a diagram for explaining the discontinuous transmission of a base station according to a fifth embodiment of the present invention. As shown in FIG. 6, a period during which the base station 10 disables or enables its own transmission unit may be introduced as cell DTX.

[0102] The transmission units and / or parameters to be disabled may be per port, per panel, per beam, per carrier, or per cell. Cell DTX may be defined by some or all of the parameters listed in 1)-6) below. The units of the parameters may be symbols, slots, subframes, milliseconds, seconds, etc., or other units. The units of the parameters may be the same or different.

[0103] 1) dtx-onDurationTimer: Duration from the beginning of the DTX cycle. 2) dtx-SlotOffset: The delay period before starting the dtx-onDurationTimer. 3) dtx-InactivityTimer: A period that starts after a DL transmission opportunity (an opportunity for the base station 10 to perform DL transmission and for the terminal 20 to receive DL transmission). 4) dtx-LongCycleStartOffset: The dtx-StartOffset that defines the long DTX cycle (i.e., dtx-LongCycle) and the start of the long and short DTX cycles. 5) dtx-ShortCycle: Short DTX cycle. May be optional. 6) dtx-ShortCycleTimer: A period during which the base station 10 performs a short DTX cycle. When DL reception occurs during long DTX, short DTX is started. This may be optional.

[0104] FIG. 7 is a diagram for explaining each parameter according to Example 5 of the embodiment of the present invention. As shown in FIG. 7, the active time is dtx-onDurationTimer after dtx-SlotOffset from the beginning of dtx-LongCycle. If DL reception occurs during drx-LongCycle, the active time ends after dtx-InactivityTimer from the point at which DL reception occurred, and dtx-ShortCycle starts. If DL reception occurs during dtx-ShortCycleTimer, dtx-ShortCycle continues. If DL reception does not occur during dtx-ShortCycleTimer, dtx-LongCycle starts.

[0105] When cell DTX is enabled, the base station 10 may transmit a DL channel or a DL signal while the dtx-onDurationTimer or the dtx-InactivityTimer is running. As an operation of the terminal 20, when cell DTX is enabled, the terminal 20 may receive a DL channel or a DL signal while the dtx-onDurationTimer or the dtx-InactivityTimer is running. The terminal 20 may assume that it receives a DL channel or a DL signal when the dtx-onDurationTimer or the dtx-InactivityTimer is not running.

[0106] When cell DTX is disabled, the terminal 20 may expect to receive DL channels or DL ​​signals as signaled or configured by the base station 10 .

[0107] The DL channel or DL ​​signal may be any of PDCCH, PDSCH, SPS (Semi Persistent Scheduling)-PDSCH, CSI-RS (Channel State Information - Reference Signal), PT-RS (Phase Tracking - Reference Signal), and DM-RS (Demodulation - Reference Signal).

[0108] The UL channel or signal may be any of the PRACH, PUCCH, PUSCH, CG-PUSCH, SRS, PT-RS, and DM-RS.

[0109] Example 6 In the sixth embodiment, the setting of cell DTX / DRX will be described.

[0110] <Option 1> Joint configuration may be performed. Cell DTX and cell DRX may be jointly configured by a common parameter. When the common parameter (e.g., CellDTXDRX-Config) is configured, cell DTX and DRX may be enabled. The terminal 20 may appropriately perform the operation of the fifth embodiment.

[0111] The common parameters may include either or both of the information elements 1) and 2) shown below.

[0112] 1) Parameters common to DTX and DRX. Some parameters may be common to DTX and DRX. For example, a parameter indicating an on-duration timer may be common to DTX and DRX. For example, a parameter indicating a cycle may be common to DTX and DRX.

[0113] 2) Parameters separated for DTX and DRX: Some parameters may be set separately for DTX and DRX. For example, a parameter indicating a slot offset may be set separately for DTX and DRX.

[0114] Option 1 allows for a reduction in RRC signaling overhead.

[0115] <Option 2> Separate configurations may be performed. Cell DTX and cell DRX may be configured individually by separate parameters. When a parameter for DTX (e.g., CellDTX-Config) is configured, cell DTX may be enabled. When a parameter for DRX (e.g., CellDRX-Config) is configured, cell DRX may be enabled. The parameters for DTX may include the parameters described in the fifth embodiment. The parameters for DRX may include the parameters described in the first embodiment.

[0116] Option 2 provides more flexibility in configuration when enabling either Cell DTX or Cell DRX.

[0117] Example 7 In Example 7, the enabling or disabling of cell DTX / DRX is described. When cell DTX and cell DRX are jointly configured (option 1 in Example 6), cell DTX and cell DRX may be enabled or disabled as follows:

[0118] <Option 1> The cell DTX and cell DRX may be enabled or disabled by RRC signaling. When an RRC parameter is configured, the cell DTX and cell DRX may be enabled or disabled. For example, the RRC parameter may be the common parameter (e.g., CellDTXDRX-Config) in the sixth embodiment.

[0119] <Option 2> Cell DTX and cell DRX may be enabled or disabled by MAC-CE. When the terminal 20 receives MAC-CE, cell DTX and cell DRX may be enabled or disabled.

[0120] <Option 3> The cell DTX and cell DRX may be enabled or disabled by the DCI. The terminal 20 may be dynamically notified by the DCI that the cell DTX and cell DRX have been enabled or disabled. The notification by the DCI may be performed as shown in 1)-4) below.

[0121] 1) The DCI format may be a UE-specific DCI format or a group-common DCI format.

[0122] 2) The DCI format may be an existing format (for example, DCI formats 1_1, 1_2, 2_0) or may be a newly defined format (for example, 1_x, 2_x).

[0123] 3) The RNTI may be an existing RNTI (for example, C-RNTI, SFI-RNTI), or a new RNTI may be defined.

[0124] 4) The DCI fields may be a set of existing fields and / or new fields. For example, if it is a set of existing fields, some fields may be used to enable or disable cell DTX and cell DRX, as shown in Alt. 1) and Alt. 2) below.

[0125] Alt. 1) When scrambling is performed by an existing RNTI such as CS-RNTI, and, for example, when HPN is set to all "0", RV is set to all "00", and TDRA is set to all "1", the terminal 20 may dynamically enable cell DTX and cell DRX. Also, when HPN is set to all "0", RV is set to all "00", MCS is set to all "1", FDRA is set to all "1", and TDRA is set to all "1", the terminal 20 may dynamically disable cell DTX and cell DRX.

[0126] Alt. 2) When scrambling is performed with a new RNTI and, for example, when HPN is set to all "0"s and RV is set to all "00", the terminal 20 may dynamically enable cell DTX and cell DRX. Also, when, for example, HPN is set to all "0", RV is set to all "00", MCS is set to all "1", and FDRA is set to all "1", the terminal 20 may dynamically disable cell DTX and cell DRX.

[0127] For example, in the case of a new DCI field, cell DTX and cell DRX may be enabled or disabled by the new DCI field. The new DCI field may be referred to as a "cell DTX DRX identifier." For example, if the cell DTX DRX identifier is set to "1," the terminal 20 may dynamically enable cell DTX and cell DRX. Also, for example, if the cell DTX DRX identifier is set to "0," the terminal 20 may dynamically disable cell DTX and cell DRX. Note that the DCI including the new DCI field may be scrambled with either an existing RNTI or a new RNTI.

[0128] Also, when cell DTX and cell DRX are configured separately (option 2 in Example 6), cell DTX and cell DRX may be enabled or disabled as follows.

[0129] <Option 1> The cell DTX or cell DRX may be enabled or disabled by RRC signaling. When an RRC parameter is configured, the cell DTX or cell DRX may be enabled or disabled. For example, the RRC parameter may be the separate parameter (e.g., CellDTX-Config, CellDRX-Config) in the sixth embodiment.

[0130] <Option 2> Cell DTX or cell DRX may be enabled or disabled by MAC-CE. When the terminal 20 receives MAC-CE, cell DTX or cell DRX may be enabled or disabled.

[0131] <Option 3> The terminal 20 may be dynamically notified by DCI that cell DTX or cell DRX has been enabled or disabled. The notification by DCI may be performed as shown in 1)-4) below.

[0132] 1) The DCI format may be a UE-specific DCI format or a group-common DCI format.

[0133] 2) The DCI format may be an existing format (for example, DCI formats 1_1, 1_2, 2_0) or may be a newly defined format (for example, 1_x, 2_x).

[0134] 3) The RNTI may be an existing RNTI (for example, C-RNTI, SFI-RNTI), or a new RNTI may be defined.

[0135] 4) The DCI fields may be a set of existing fields and / or new fields. For example, a different set of DCI fields may be used to enable or disable cell DTX or cell DRX, respectively, to indicate either cell DTX or cell DRX. For example, in the case of an existing set of fields, some fields may be used to enable or disable cell DTX and cell DRX, as shown in Alt. 1) and Alt. 2) below.

[0136] Alt. 1) When scrambling is performed by an existing RNTI such as CS-RNTI, and, for example, when HPN is set to all "0", RV is set to all "00", and PRI is set to all "1", the terminal 20 may dynamically enable cell DTX. Also, for example, when HPN is set to all "0", RV is set to all "00", MCS is set to all "1", FDRA is set to all "1", and PRI is set to all "1", the terminal 20 may dynamically disable cell DTX. Also, for example, when HPN is set to all "0", RV is set to all "00", and TDRA is set to all "1", the terminal 20 may dynamically enable cell DRX. Also, for example, when HPN is set to all "0", RV is set to all "00", MCS is set to all "1", FDRA is set to all "1", and TDRA is set to all "1", the terminal 20 may dynamically disable cell DRX.

[0137] Note that the PRI and TDRA fields may additionally be used to indicate whether the DCI to be enabled or disabled is for CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX.

[0138] Note that the same field (e.g., TDRA) as the fields used as described above, such as PRI and TDRA, may be used to indicate whether the target is CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX. When different DCI formats are used, the DCI format may indicate whether the target is cell DTX or cell DRX. For example, DCI format 0_0 may enable or disable cell DRX, and DCI format 1_0 may enable or disable cell DTX.

[0139] Alt. 2) When scrambling is performed with a new RNTI, for example, if HPN is set to all "0", RV is set to all "00", and PRI is set to all "1", the terminal 20 may dynamically enable cell DTX. For example, if HPN is set to all "0", RV is set to all "00", MCS is set to all "1", FDRA is set to all "1", and PRI is set to all "1", the terminal 20 may dynamically disable cell DTX. For example, if HPN is set to all "0" and RV is set to all "00", the terminal 20 may dynamically enable cell DRX. For example, if HPN is set to all "0", RV is set to all "00", MCS is set to all "1", and FDRA is set to all "1", the terminal 20 may dynamically disable cell DRX.

[0140] Note that, for example, PRI is used as described above, but an additional field may not be used to indicate whether cell DTX or cell DRX is intended. When different DCI formats are used, the DCI format may indicate whether cell DTX or cell DRX is intended. For example, DCI format 0_0 may enable or disable cell DRX, and DCI format 1_0 may enable or disable cell DTX.

[0141] For example, in the case of a new DCI field, the new DCI field may enable or disable cell DTX or cell DRX, and the new DCI field may be called a "cell DTX identifier" or a "cell DRX identifier."

[0142] When cell DTX and cell DRX are notified separately in separate fields, for example, if the cell DTX identifier is set to "1", the terminal 20 may dynamically enable cell DTX. Also, for example, if the cell DTX identifier is set to "0", the terminal 20 may dynamically disable cell DTX. For example, if the cell DRX identifier is set to "1", the terminal 20 may dynamically enable cell DRX. Also, for example, if the cell DRX identifier is set to "0", the terminal 20 may dynamically disable cell DRX.

[0143] Furthermore, this new DCI field may be referred to as a "cell DTX DRX identifier." When cell DTX and cell DRX are jointly notified in a common field, for example, if the cell DTX DRX identifier is set to "01," the terminal 20 may dynamically enable cell DTX or dynamically disable cell DRX. For example, if the cell DTX DRX identifier is set to "10," the terminal 20 may dynamically enable cell DRX or dynamically disable cell DTX. For example, if the cell DTX DRX identifier is set to "11," the terminal 20 may dynamically enable cell DTX and cell DRX. For example, if the cell DTX DRX identifier is set to "00," the terminal 20 may dynamically enable cell DTX and cell DRX. The bit mapping of cell DTX and cell DRX described above may be reversed.

[0144] It should be noted that the DCI including the new DCI field may be scrambled with either the existing RNTI or the new RNTI.

[0145] The timing for applying the above-mentioned enabling or disabling of cell DTX or cell DRX notified by MAC-CE or DCI may be 1) or 2) shown below.

[0146] 1) The terminal 20 may immediately activate or deactivate the cell DTX or cell DRX. When activation or deactivation of the cell DTX or cell DRX is notified by the MAC-CE or DCI, the terminal 20 may immediately activate or deactivate the cell DTX or cell DRX.

[0147] 2) The terminal 20 may activate or deactivate the cell DTX or cell DRX at the notified time. The time to activate or deactivate the cell DTX or cell DRX may be notified via RRC signaling, MAC-CE, or DCI as an interval or a certain time from the time when the activation or deactivation is notified. The unit of time may be a symbol, slot, subframe, millisecond, second, or the like. When the activation or deactivation of cell DTX or cell DRX is notified by MAC-CE or DCI, the cell DTX or cell DRX may be activated or deactivated at the notified time in advance.

[0148] Example 8 In Example 8, the related operation of cell DTX / DRX and UE DRX will be described. If the time positions of cell DTX and UE DRX are not aligned, the terminal 20 may wake up to receive a DL channel or DL ​​signal when no DL transmission is being performed due to cell DTX.

[0149] Therefore, you may operate as shown in Option 1-Option 5 below.

[0150] <Option 1> If UE DRX is configured (for example, DRX-Config), the terminal 20 may not assume that cell DTX is configured.

[0151] <Option 2> When cell DTX is configured, terminal 20 does not need to assume that UE DRX (for example, DRX-Config) is configured. Note that the parameters of cell DTX may be the parameters described in the sixth embodiment.

[0152] <Option 3> When UE DRX is configured (e.g., DRX-Config), the terminal 20 does not need to assume that cell DTX that is not time-aligned with UE DRX is configured. If cell DTX and UE DRX are time-aligned, cell DTX and UE DRX may be configured jointly.

[0153] <Option 4> When cell DTX is configured, terminal 20 does not need to assume that UE DRX (e.g., DRX-Config) that is not time-aligned with cell DTX is configured. When cell DTX and UE DRX are time-aligned, cell DTX and UE DRX may be configured jointly.

[0154] <Option 5> Regardless of whether the time positions of cell DTX and UE DRX are aligned or not, cell DTX and UE DRX may be configured in the terminal 20. Furthermore, when cell DTX is configured in addition to UE DRX, the parameters of cell DTX may take priority. The terminal 20 may ignore the parameters of UE DRX. The terminal 20 may operate as in the fifth embodiment. Furthermore, when cell DTX is configured in addition to UE DRX, the parameters of both may be applied. The terminal 20 may wake up during the active times of both cell DTX and cell DRX.

[0155] The above "cell DTX and UE DRX are time aligned" may be defined as option 1 or option 2 shown below.

[0156] <Option 1> If the long cycle is the same for cell DTX and UE DRX, it may be defined that the time positions of cell DTX and UE DRX are aligned.

[0157] <Option 1-1> Furthermore, when the long cycle is the same for cell DTX and UE DRX, it may be defined that the time positions of cell DTX and UE DRX are aligned regardless of the active time within the long cycle. In other words, when the long cycle of cell DTX (e.g., dtx-LongCycle) and the long cycle of UE DRX (e.g., drx-LongCycle) are the same, it may be defined that the time positions are aligned.

[0158] <Option 1-2> If the long cycle is the same for cell DTX and UE DRX, it may be further defined that the cell DTX and UE DRX are time-aligned depending on the active time within the long cycle. If the on-duration timers and slot offsets in the long cycle (e.g., dtx-LongCycle, drx-LongCycle, dtx-onDurationTimer, drx-onDurationTimer, dtx-SlotOffset, drx-SlotOffset) are the same for cell DTX and UE DRX, it may be defined that the cell DTX and UE DRX are time-aligned. Furthermore, other parameters (e.g., dtx-InactivityTimer, drx-InactivityTimer, etc.) may be additionally considered to determine whether this definition is met.

[0159] <Option 2> In addition to the long cycle, if the short cycle is the same for cell DTX and UE DRX, it may be defined that the cell DTX and UE DRX are time-aligned. Option 2 may be applied when the conditions of Option 1-1 or Option 1-2 are met.

[0160] <Option 2-1> Furthermore, if the short cycle is the same for cell DTX and UE DRX, it may be defined that the time positions of cell DTX and UE DRX are aligned regardless of the active time within the short cycle. In other words, if the short cycle of cell DTX (e.g., dtx-ShortCycle) and the short cycle of UE DRX (e.g., drx-ShortCycle) are the same, it may be defined that the time positions are aligned.

[0161] <Option 2-2> If the short cycle is the same for cell DTX and UE DRX, then it may be further defined that the time positions of cell DTX and UE DRX are aligned depending on the active time within the short cycle. If the short cycle timers and short cycles (e.g., dtx-ShortCycleTimer, drx-ShortCycleTimer, dtx-ShortCycle, drx-ShortCycle) are the same for cell DTX and UE DRX, then it may be defined that the time positions of cell DTX and UE DRX are aligned.

[0162] (Outline 3 of this embodiment) Example 9 Here, the following technologies are being considered for network energy saving (NES).

[0163] On-demand SSB and / or SIB1 transmission is being considered. For example, on-demand S1B1 or SSB transmission to idle UEs, and on-demand SSB and other DL signals transmission to connected UEs in SCells are being considered. Note that SSB may be replaced with SS / PBCH block. Note that " / " may be replaced with either "and / or", "and", or "or".

[0164] To trigger on-demand SSB and / or SIB1 transmission, the following methods 1)-3) are being considered.

[0165] 1) Triggering based on the UE's UL-WUS (Wake-up signal), which may be used for non-CA cases, for example, and may be an existing signal or a new signal. 2) Trigger based on a backhaul signal indicating cell ON or OFF. 3) Trigger based on SCell activation or deactivation signaling.

[0166] Also, operation without SSB and / or SIB1 may be performed in a multi-carrier scenario, for example, without SSB and / or SIB1 in a non-anchor NES cell for an idle or inactive UE, assuming that other carriers (e.g., anchor cells) are available for the UE to use.

[0167] The decision to use on-demand SSB and / or SIB1 transmission versus no SSB and / or SIB1 may be based on the benefits in the target scenario, and optimization of the transmission of common signals and / or channels is considered.

[0168] 8 is a sequence diagram illustrating an example (1) of OSI (On-demand system information) transmission according to a ninth embodiment of the present invention. FIG. 8 illustrates an example of an SIB request based on MSG1 (message 1 in a random access procedure), and CFRA (Contention Free Random Access) may be assumed. In step S101, the terminal 20 transmits a system information request indicating a specific SIB type to the base station 10 by using a pre-allocated PRACH resource and a preamble for MSG1. In step S102, the base station 10 transmits MSG2 to the terminal 20 as a response. In step S103, the base station 10 transmits the requested system information to the terminal 20.

[0169] 9 is a sequence diagram for explaining an example (2) of OSI transmission according to Example 9 of the embodiment of the present invention. FIG. 9 shows an example of an SIB request based on MSG3 (message 3 in the random access procedure), and CBRA (Contention-based Random Access) may be assumed. In step S201, the terminal 20 transmits MSG1 to the base station 10. In step S202, the base station 10 transmits MSG2 to the terminal 20. In step S203, the terminal 20 transmits MSG3 to the base station 10, the MSG3 including information indicating a system information request. In step S204, the base station 10 transmits MSG4 to the terminal 20. In step S205, the base station 10 transmits the requested system information to the terminal 20.

[0170] In the existing specifications, a specification extension is being considered that will enable on-demand transmission of SIB1 (System Information Block 1), which is transmitted periodically and always on, triggered by the UE. A cell that operates on-demand SIB1 transmission is called an NES cell. The UE acquires in advance the configuration related to UL transmission (UL-WUS configuration) that triggers on-demand SIB1. The UE notifies the UL-WUS configuration mainly in cell A, which transmits SIB1 periodically or always on. After camping on the NES cell, the WUS configuration can also be notified from the NES cell.

[0171] 10 is a diagram illustrating an example of an on-demand SSB according to a ninth embodiment of the present invention. The on-demand SSB can be notified or transmitted in various procedures during carrier aggregation. It is assumed that basic information of the on-demand SSB is set by RRC signaling, and then an activation command is notified by MAC-CE or the like immediately before the on-demand SSB is actually transmitted.

[0172] As shown in Fig. 10, for operations related to on-demand SSB, Scenario #2 considers the operation when the SCell is set to a deactivated state. Scenario #2A considers the operation when an SCell activation command is received. Scenario #3A considers the operation from receiving the SCell activation command until SCell activation is completed. Scenario #3B considers the operation when SCell activation is completed or after SCell activation is completed.

[0173] Note that the case where an on-demand SSB is configured for the SCell and SCell activation is performed may be referred to as case #1, as shown in Fig. 10. Also, the case where a legacy SSB, i.e., an always-on SSB, is configured for the SCell and SCell activation is performed may be referred to as case #2.

[0174] 11 is a sequence diagram for explaining an example of an operation related to an on-demand SSB according to Example 9 of the embodiment of the present invention. In step S301, the UE completes cell selection or cell reselection and camps on cell A. In step S302, the UE receives a WUS configuration from cell A via SIB-X or dedicated RRC signaling.

[0175] In step S303, the UE triggers, for example, cell reselection. In step S304, a condition for requesting an on-demand SIB is met in the NES cell. In step S305, the UE transmits a UL-WUS (PRACH / msg1) requesting on-demand SIB1 to the NES cell. In step S306, the NES cell transmits a UL-WUS response (RAR / msg2) to the UE via the PDCCH and PDSCH.

[0176] In step S307, the NES cell transmits the on-demand SIB1 to the UE via the PDCCH and PDSCH. In step S308, the UE performs, for example, cell reselection. In step S309, the UE camps on the NES cell.

[0177] FIG. 12 is a sequence diagram illustrating an example of a random access procedure according to Example 9 of the present invention. In step S401, the UE performs PSS detection. The UE performs time and frequency synchronization and acquires a portion of the physical cell ID. In step S402, the UE performs SSS detection. The UE acquires a portion of the physical cell ID. In step S403, the UE performs PBCH-DMRS detection. The UE detects an SSB index or a portion of an SSB index within a 5 ms half frame. In step S404, the UE receives the PBCH. The UE acquires the SFN, the radio frame timing of the SSB index, settings required for acquiring RMSI, and information indicating whether camping on the cell is possible. Steps S401 to S404 correspond to operations for receiving SS / PBCH blocks.

[0178] In step S405, the UE receives the PDCCH, and in step S406, the UE receives the SIB1-PDSCH. The UE acquires information related to cell configuration and initial access, including PRACH configuration.

[0179] In step S407, the UE transmits Msg1 via PRACH. Msg1 is the first transmission signal in the initial access procedure. In step S408, the UE receives PDCCH, and in step S409, receives Msg2-PDSCH (RAR, Random Access Response). The UE acquires the TA, TC-RNTI, and scheduling information (RAR UL grant) of Msg3.

[0180] In step S410, Msg3 is transmitted via PUSCH. The UE transmits an RRC setup request including the UE-ID. In step S411, the UE receives Msg4-PDCCH, and in step S412, receives Msg4-PDSCH. The UE performs collision resolution. If collision resolution is successful, TC-RNTI is used as C-RNTI. In step S413, the UE transmits HARQ-ACK corresponding to Msg4 via PUCCH.

[0181] Table 1 shows an example of a mask for existing PRACH resources (see Non-Patent Document 6).

[0182] [Table 1]

[0183] In the existing specifications, the PRACH resource mask shown in Table 1 is used when there are multiple ROs for the same SSB. The mask can only be applied when the value of ssb-perRACH-Occasion is an integer greater than 1. Therefore, it cannot be applied in cases other than the above, such as when only a single RO is assigned to a certain SSB. In addition, the permitted indexes are used to enable the resources indicated in the table, and disable or mute the others.

[0184] 13 is a diagram illustrating an example of an SSB according to Example 9 of the present invention. Compared to LTE, the SSB in NR has a wider bandwidth and a reduced number of symbols, from 6RB6 symbols to 20RB4 symbols. Furthermore, it has improved flexibility and allows for longer periods to be set, such as {5, 10, 20, 40, 80, 160} ms. Multiple candidate symbol positions can be set within a 5-ms half radio frame. For example, 4 can be set in the 0-3 GHz band, 8 in the 3-6 GHz band, and 64 in the 6-52.6 GHz band.

[0185] Transmit beam sweeping is possible for SSB transmissions, as shown in Figure 13. The same cell ID is used across SSBs, but the SSB index is distinct. The SSB index determines the time domain position within the 5 ms half radio frame.

[0186] Example 10

[0187] The existing SSB may mean any of the following 1)-4), or any combination of 1)-4).

[0188] 1) SSB configured by RRC signaling up to Release 18. 2) SSB set in servingCellConfigCommon set in SIB1 or RRCReconfiguration. 3) Cell-Defining SSB (CD SSB) or non-cell-defining SSB (NCD SSB): An SSB configured as an NCD-SSB by RRC signaling. 4) SSBs located on a sync raster or SSBs located other than on a sync raster. 5) SSB configured in servingCellConfig under SCell configuration

[0189] Note that on-demand SSB may mean any of 1)-13) below, or any combination of 1)-13) below. For example, it may mean an SSB triggered by any of 1)-13) below, or an SSB triggered by any combination of 1)-13) below, or it may be an adaptation of an existing and / or new SSB, or it may be interpreted as an adaptation of an on-demand SSB. Note that " / " may be replaced with "and / or," "and," or "or."

[0190] 1) SSBs that are notified with settings different from the existing SSBs listed above. 2) Triggering the SSB transmission itself: SSB transmission is turned on or off. 3) Triggering SSB transmission at a certain period X, SSB transmission at a period greater than or less than X, or longer or shorter than X, SSB transmission with a shorter period than the SSB currently being transmitted, currently set, or most recently received by the UE, SSB transmission with a longer period than the SSB currently being transmitted, currently set, or most recently received by the UE, or maintaining SSB transmission at the current period. Changing the SSB period. 4) Triggering the transmission / not transmitting of a certain SS burst (triggering SSB transmission at a certain opportunity). It may also be possible to trigger the transmission / not transmitting of multiple SSB bursts. 5) Triggering the transmission / not transmitting of an SS burst within a certain period (triggering SSB transmission at a certain opportunity). Triggering the transmission / not transmitting of multiple SSB bursts may be possible. 6) Maintain a certain number of SSB transmissions / fewer SSB transmissions / more SSB transmissions / current SSB transmissions. Change the SSB position or SSB index. 7) Maintain the number of SSB transmissions in an SS burst / fewer SSB transmissions / more SSB transmissions / current SSB transmissions. Change the SSB position or SSB index. 8) Triggering a certain SSB. 9) Triggering different SSBs at a certain SSB index / position. 10) Triggering on a certain SSB within a certain SS burst. 11) Triggering different SSBs at a certain SSB index / position within a certain SS burst. 12) Transmit beam / triggering SSB transmission that has a predetermined QCL (Quasi Co Location) relationship with some other RS. 13) Triggering SSB transmissions with different SSB indices / positions and transmit beams / predetermined QCL relationships with some other RS ​​for each SSB.

[0191] The on-demand SSB may be replaced by an on-demand SIB1, or may be a CORESET (Control Resource Set) that is transmitted on-demand / triggered by the UE and associated with the Type0-PDCCH CSS set to which the UE belongs.

[0192] In steps S501, S601, S701, and S801 described below, the predetermined conditions being satisfied or the predetermined settings being notified may be any of 1) to 10) shown below, or any combination thereof.

[0193] 1) When an existing SSB or always-on SSB is configured or being transmitted.

[0194] 2) When the resources on which on-demand SSBs are transmitted or can be transmitted are configured or notified by RRC signaling, semi-statically by RRC signaling, or dynamically by MAC-CE or DCI.

[0195] 3) When an existing SSB, always-on SSB, or on-demand SSB is received.

[0196] 4) If configured as TDD, FDD, SUL, unlicensed, SL, mTRP, DC, FR (Frequency Range) 2 or FR1, or if not configured.

[0197] 5) When the transmission, configuration, cell or frequency of the on-demand SSB is a cell in the MCG, a cell in the SCG, a PCell, a SCell, a PSCell, a PUCCH-SCell, a known cell, an unknown cell, or satisfies or does not satisfy the side condition.

[0198] 6) The transmission characteristics of the on-demand SSB are predetermined characteristics, for example, periodic, quasi-persistent or aperiodic transmission, X SSB bursts are transmitted, the period is less than or equal to X, or the period is greater than or equal to X.

[0199] 7) When there is a specific relationship between the on-demand SSB and the existing or always-on SSB, for example, when they are the same FR, frequency, or BWP.

[0200] 8) When there is a predetermined relationship between the cell to which the on-demand SSB is transmitted, configured, or notified and the (S)pCell. For example, when they are the same cell or different cells. For example, when the SCS is different, when the SCS is the same, when the TA group is the same, when the TA group is different, when the cell group is the same, when the cell group is different, when the FR is the same, when the FR is different, when a predetermined relationship (e.g., conditions for SSB-less SCell) is satisfied, when other predetermined time-frequency related resources are the same, or when other predetermined time-frequency related resources are different.

[0201] 9) When the SCell for which an on-demand SSB is transmitted, configured or signaled is in a predetermined state, such as activated, deactivated, dormant, in SCell activation procedure, in deactivation procedure, BWP activated, or BWP deactivated.

[0202] 10) When the on-demand SSB is associated with or used for a predetermined application, for example, the predetermined application may be SCell activation, L1 measurement, L3 measurement, SCell beam failure recovery, power control, SCell time synchronization, SCell frequency synchronization, return from dormancy for channel estimation (QCL), or known cell transition.

[0203] Note that for all of the above 1) to 10), the condition may be limited to the case where a predetermined condition or setting is satisfied that is greater than, less than, or equal to X. X may be set by RRC signaling, or a different predefined value may be specified by the SCS, or may be reported in the UE capabilities.

[0204] For example, it may mean that X1 on-demand SSB configurations are made under the same conditions or settings, or that X2 different conditions are met from the predetermined conditions described above, or a combination thereof.

[0205] An SSB-less SCell function has been added that performs time-frequency synchronization of a certain SCell based on SSBs transmitted from a PCell or another cell without transmitting SSBs in the SCell. When absoluteFrequencySSB is not configured in the RRC parameter servingCellConfigCommon, this function is activated and the UE uses a reference cell for synchronization (see Non-Patent Document 3).

[0206] Also, as in On-Demand SSB Case #1 shown in Figure 10, a function has been added to turn on or off On-Demand SSB without transmitting an Always-On SSB. As in On-Demand SSB Case #2 shown in Figure 10, a function has been added to transmit an Always-On SSB and additionally turn on or off On-Demand SSB. Note that in On-Demand SSB Case #1, absoluteFrequencySSB in servingCellConfigCommon is not set, and absoluteFrequencySSB in od-ssb config is referenced.

[0207] Here, when always-on SSB is not configured, it is unclear whether to apply the SSB-less SCell function or the on-demand SSB case #1.

[0208] FIG. 14 is a flowchart illustrating an example (1) of SSB adaptation according to a tenth example of an embodiment of the present invention. A UE that supports SSB-less SCell and on-demand SSB case #1 may execute the flowchart of FIG. 14. In step S501, a predetermined condition is met or a predetermined setting is notified. In step S502, the UE assumes a predetermined constraint on the setting related to whether or not to transmit an always-on SSB. For example, the setting related to whether or not to transmit an always-on SSB may be the absolute frequency position of the SSB (absoluteFrequencySSB).

[0209] Note that a UE that supports an SSB-less SCell may be a UE that reports any combination of the following UE capabilities. Parameters related to Intra-band SSB-less SCell scellWithoutSSB csi-RS-MeasSCellWithoutSSB Parameters related to Inter-band SSB-less SCell (may be applicable only to UEs that have reported certain parameters below, for example, only referenceBand1). scellWithoutSSB-InterBandCA-r18 CHOICE { supportOfSingleGroup ENUMERATED {referenceBand, scellWithoutSSB, both}, supportOfMultipleGroups ENUMERATED {referenceBand1, scellWithoutSSB1, referenceBand2, scellWithoutSSB2}

[0210] Note that a UE that supports on-demand SSB case #1 may be a UE that has reported its UE capability for on-demand SSB.

[0211] The predetermined constraint in step S502 may be any one of the following 1) to 4) or any combination thereof.

[0212] 1) Constraints on the reference cell (ReferenceCell), for example, may be as follows: ·referenceCell-r18 may or may not be set. A new parameter (e.g., referenceCell-r19) is set to indicate the time-frequency reference when on-demand SSB is configured / can be transmitted / is being transmitted.

[0213] 2) Restrictions on whether or not there is always-on SSB, for example, the following may be possible: Absolute Frequency SSB must not be set A new parameter (e.g., ssblessSCellapplicationOD-SSBcase1) is set as a binary or Boolean to indicate whether an SSB-less SCell is valid in cases where an on-demand SSB is configured, can be transmitted, or is being transmitted. · Whether absoluteFrequencySSB is set or not may be ignored as to whether SSB-less SCell is in operation or not.

[0214] 3) In addition to the existing RRC parameter conditional presence SSBlessSCell, the following conditions may be specified in a predetermined parameter, e.g., a reference cell, taking into account the case where an on-demand SSB is configured, can be transmitted, or is being transmitted: ·scelllessSCellOd-ssb ·scelllessSCellOd-ssbCase1

[0215] 4) The smtc included in the SCellConfig is absent or not absent.

[0216] Table 2 shows examples of conditions for conditionally set RRC parameters.

[0217] [Table 2]

[0218] As shown in Table 2, the existence condition SSBlessSCell exists as an option when the interband SSBless Scell ​​is configured and absoluteFrequencySSB is absent.

[0219] For a UE that supports on-demand SSB Case #1, or an SSB-less SCell and on-demand SSB Case #1, if an RRC parameter (e.g., a reference cell) whose conditional presence is SSBlessSCell is configured or not configured in the cell, the UE may interpret the parameter as Optionally present, Need S or Absent, Need R.

[0220] Note that Need S may refer to a field whose presence specifies the behavior of the UE, and Need R may refer to a parameter that is retained and releases its current value when an absent field is received.

[0221] Fig. 15 is a flowchart for explaining an example (2) of SSB adaptation according to a tenth embodiment of the present invention. A UE that supports an SSB-less SCell and on-demand SSB case #1 may execute the flowchart of Fig. 15. In step S601, a predetermined condition is satisfied or a predetermined configuration is notified. In step S602, the UE performs predetermined handling for the configuration or notification related to the SSB-less SCell and / or on-demand SSB.

[0222] The predetermined handling operation in step S602 may be any one of the following 1) to 3) or any combination thereof.

[0223] 1) On-demand SSB configuration or transmission notification (activation, deactivation, adaptation), transmission, reception and / or operation may be ignored, dropped, considered as a valid or invalid resource, no transmission or reception operation may be performed, predetermined operations using the SSB may not be performed, predetermined operations using other channels, signals or PHY layer control information may not be performed, predetermined UL signaling (e.g., HARQ-NACK, RRCReconfigurationfailure) may be responded to, and the signaling may include content or parameters indicating reconfiguration, retransmission or failure, or the resource of reconfiguration, retransmission or failure.

[0224] 2) The settings of a use case may be changed or released. For example, the following may be performed: Cell DTX deactivation or activation, UE DRX deactivation or activation. · Perform or stop measurements or monitoring related to the associated SCell beam failure recovery. ·Semi-persistent CSI reporting, release of associated measurement objects (L3 measurements), SCell release. Release of associated periodic CSI reporting (L1 measurements). Release or deactivation of associated semi-persistent CSI reporting (L1 measurement). Release or deactivation of associated aperiodic CSI reporting (L1 measurements). · Suspend operation in a specified SCell or SSB, do not transmit / drop CSI reports on PUCCH or PUSCH, do not perform normal SCell operation as defined in Non-Patent Document 5 in the SCell. Performs mapping from the associated PRACH SSB to the RO (RACH Occasion). Performs PRACH validation.

[0225] 3) Additional processing delays may be assumed for the predetermined timing at which on-demand SSB transmission of the advertised characteristics is initiated.

[0226] Fig. 16 is a flowchart for explaining an example (3) of SSB adaptation according to Example 10 of the embodiment of the present invention. A UE that supports SSB-less SCell and on-demand SSB case #1 may execute the flowchart of Fig. 16. In step S701, a predetermined condition is met or a predetermined setting is notified. In step S702, the UE may or may not execute a predetermined operation related to SSB-less SCell operation and / or on-demand SSB operation. The predetermined operation may be any one of the following 1) to 6) or any combination thereof.

[0227] 1) Always perform on-demand SSB operation without performing SSB-less SCell operation. 2) Always perform SSB-less SCell operation without performing on-demand SSB operation. 3) Both SSB-less SCell and on-demand SSB operation is performed. 4) When on-demand SSB is activated, on-demand SSB operation is performed, and otherwise (after on-demand SSB is deactivated) SSB-less SCell operation is performed. 5) Whether to perform any of the above 1) to 4) may be configured by the RRC, may be reported in the UE capabilities, or may be determined based on the UE implementation. 6) The operation of 1) to 4) above may be performed differently depending on the SSB use or different cases described below. For example, During SCell deactivation, SSB-less SCell operation (time and frequency synchronization is performed by referencing the reference cell) is performed. During SCell activation, on-demand SSB operation (time-frequency synchronization is performed with reference to on-demand SSB) is performed.

[0228] The SSB-less SCell operation and / or on-demand SSB operation may be any combination of the following:

[0229] In any case of the SCell activation state, SCell deactivation state, SCell dormancy state, during the SCell activation procedure, during the SCell deactivation procedure, from receiving the SCell activation or SCell deactivation command until the completion of activation / deactivation as defined in existing non-patent document 5, the SSB of the reference cell or on-demand SSB is used to perform SCell activation, L1 measurement, L3 measurement, SCell beam failure recovery, SCell power control, time synchronization, frequency synchronization, return from dormancy for channel estimation, and transition to a known cell.

[0230] It may be assumed that the RRC parameters that are set to perform the above operations are not set, or those parameters that are set may be ignored.

[0231] FIG. 17 is a flowchart illustrating an example (4) of SSB adaptation according to a tenth example of an embodiment of the present invention. A UE supporting an SSB-less SCell and an on-demand SSB case #1 may execute the flowchart of FIG. 16. In step S801, a predetermined condition is met or a predetermined configuration is notified. In step S802, the UE assumes a predetermined operation regarding whether an on-demand SSB can be configured or used as a reference cell for another SSB-less SCell. The predetermined operation may be any one of the following or any combination thereof:

[0232] 1) In on-demand SSB case #1, the on-demand SSB (SCell #2) may or may not be configurable as a reference cell for the SSB-less SCell (SCell #1). If configurable, it may be configured using existing parameters (referenceCell-r18) or new parameters.

[0233] 2) In on-demand SSB case #2, the on-demand SSB (SCell #2) may or may not be configurable as a reference cell for the SSB-less SCell (SCell #1). If configurable, it may be configured using existing parameters (referenceCell-r18) or new parameters.

[0234] The above SCell#2 may be limited to the SCell on which the activated on-demand SSB is being transmitted.

[0235] It should be noted that the behavior of siblings in embodiments of the present invention may be limited to the following cases or any combination of the following cases:

[0236] On-Demand SSB Case #1 On-Demand SSB Case #2 When both always-on and on-demand SSBs are associated with a given use case, e.g., SCell activation, L1 measurements for CSI reporting, L3 measurements, SCell beam failure recovery, power control On-demand SSB activation / adaptation with MAC-CE Initial notification (when no on-demand SSB has been sent and this is the first notification of an on-demand SSB transmission), subsequent or adaptation notification (when an on-demand SSB has already been sent and this notification overrides the on-demand SSB transmission). On-demand SSB activation or adaptation via RRC Initial notification (when no on-demand SSB has been sent and this is the first notification of an on-demand SSB transmission), subsequent or adaptation notification (when an on-demand SSB has already been sent and this notification overrides the on-demand SSB transmission). On-demand SSB deactivation by MAC-CE via explicit signaling (on-demand SSB configured or signaled as deactivation method) On-demand SSB deactivation by implicit counter or timer (on-demand SSB configured or advertised as deactivation method) SCell SSB adaptation The always-on SSB may be limited to the case where it is per BWP (for example, NCD-SSB) or per cell (for example, CD-SSB). Any combination of the following cases is acceptable, or any case is acceptable.

[0237] SCell activation state, SCell deactivation state, SCell dormant state, during SCell activation procedure, during SCell deactivation procedure, from receiving an SCell activation or SCell deactivation command to activation / deactivation completion as defined in existing non-patent document 5.

[0238] The predetermined period may be any of the following, or may be determined based on a predetermined parameter set by the BS.

[0239] The predetermined period may be a period of a predetermined time width from a predetermined reference point, which may be a predetermined DL / UL signal transmission / reception time and / or a reference time (SFN (System Frame Number), slot number, symbol number) set by the BS.

[0240] The unit in the time direction may be a symbol, a slot, a radio frame, a system frame, a sub-millisecond, a millisecond, or a second.

[0241] The predetermined time period may be a time window pre-defined by parameters and / or specifications set by the BS and / or determined according to the UE capabilities, or after a certain delay (application delay, processing delay).

[0242] The predetermined time interval may be pre-defined by parameters and / or specifications set by the BS and / or may depend on the UE capabilities and / or may vary depending on the SCS and / or may vary depending on the Timing Advanced value of the UE and / or may be within a time window from a reference point, or after a certain delay (application delay, processing delay) from a reference point.

[0243] The UE may determine the predetermined period by taking the minimum (using a small value) or maximum (using a large value) of a predetermined value, which may be 1 symbol / 1 slot / 1 millisecond or a value determined as follows:

[0244] A parameter set by the BS and / or pre-defined in the specification and / or determined according to the UE's capability and / or a value that varies depending on the SCS.

[0245] The predetermined cell of the BS may be any of an SpCell, a Pcell, a PSCell during DC, an active SCell, and a cell that satisfies a predetermined condition.

[0246] The UE may be in an idle, inactive, or RRC connected state, and different operations may be performed depending on the UE state.

[0247] A UE may support and / or report certain functions / operations in a certain UE capability. The certain UE capability may be configured at any of the following granularities: UE, FR1, FR2, FR2-1, FR2-2, SCS, band, band combination, feature combination, and / or FSPC unit; UE, Cell, TDD, FDD unit.

[0248] The predetermined setting / notification may be any of the following.

[0249] The configuration / notification may be performed by RRC, MAC-CE, or DCI, and the parameter list configured / notified by RRC, MAC CE, or DCI may be associated with an identifier (index), and the UE may determine the parameter list to be activated / applied / used (deactivation, not applied, used) by notifying the UE of the identifier by another notification (MAC CE, DCI).

[0250] The identifiers may be associated implicitly by the order of a list configured in the RRC, or may be associated by explicitly configuring a certain number.

[0251] The UE may respond to any of the signals with a response signal (NACK, ACK, feedback, retransmission request).

[0252] The UE may configure, modify and release multiple parameter lists via RRC using "AddModlist" and / or "releaselist".

[0253] The configuration / notification may be performed by an SI / SIB RRC message, or may be a UE-specific RRC message (for example, RRCReconfiguration) for a UE in an RRC connection.

[0254] Dedicated RRC configuration / RRC release / RRC setup may be configured / notified.

[0255] Dedicated RRC configuration / RRC release / RRC setup for SS / PBCH / SIB1 / SIBX / one or more cells / bands / carriers may be configured / notified.

[0256] SS / PBCH / SIB1 / SIBX / dedicated RRC configuration / RRC release / RRC setup of one or more cells / bands / carriers may be configured / notified.

[0257] SS / PBCH / SIB1 / SIBX of one / multiple cells / bands / carriers / dedicated RRC configuration / RRC release / RRC setup of one / multiple cells / bands / carriers may be configured / notified.

[0258] The configuration / notification may be a predetermined DCI format scrambled with X-RNTI, which may be, but is not limited to, NES-RNTI, SI-RNTI, or a new DCI format and / or RNTI.

[0259] For all parameters, the UE may take default values / actions when not configured / notified by the BS, and the default actions may be as follows:

[0260] No action Repeat the previous action Perform RRC Release / RRC Re-establishment Sends the required notifications to BS Sends predetermined notifications to upper layers of the UE

[0261] The default value may be:

[0262] Always 0 / 1 Last used value -Last-time set / notified value - (pre-)defined values ​​in the specification - Different setting / notification parameter values -predetermined timer value

[0263] Note that "deactivation" may be replaced with any term indicating invalidation, or any term indicating update, adaptation, or change. Note that for the RRC parameters, Non-Patent Document 3 may be referred to as appropriate.

[0264] For all UE actions #A, the UE may perform a default action #B in the event that a certain action #A cannot be performed.

[0265] Which of the above embodiments is to be used may be set by higher layer parameters, may be reported from the terminal 20 to the base station 10 as UE capabilities, may be defined by specifications, may be reported from the terminal 20 to the base station 10 as UE capabilities and set by higher layer parameters, or may be notified by DCI. A WUS (Wake up signal) for the base station may be used for cell DTX in addition to cell DRX.

[0266] In addition, a UE capability may be defined indicating whether cell DTX and cell DRX are supported, a UE capability may be defined indicating whether dynamic enabling or disabling of cell DTX and cell DRX is supported, and a UE capability may be defined indicating whether cell DTX and cell DRX with UE DRX or CDRX are supported.

[0267] Note that cell DTX / DRX may be replaced with cell DTX and / or cell DRX. Validation / invalidation may be replaced with validation and / or invalidation, activation and / or deactivation, etc.

[0268] The above-described operation allows the BS and UE to agree on the SSB to be referenced when the parameter absoluteFrequencySSB is not set, enabling appropriate time-frequency synchronization, AGC, and measurement-related operations to be performed.

[0269] That is, a technique is provided that clarifies the terminal operation when an always-on SSB (SS / PBCH Block) is not transmitted in communication with a base station that can transition to a power saving state.

[0270] (Device configuration) Next, a description will be given of examples of functional configurations of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0271] <Base Station 10 and Network Node 30> FIG. 18 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in FIG. 18, 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. 18 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0272] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30, and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30, and acquiring, for example, information of a higher layer from the received signal. A communication unit including the transmitter 110 and the receiver 120 may be configured.

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

[0274] 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 related to the operations described in the embodiments.

[0275] The control unit 140 controls 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.

[0276] <Terminal 20> Fig. 19 is a diagram showing an example of the functional configuration of terminal 20 in the embodiment of the present invention. As shown in Fig. 19, 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. 19 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.

[0277] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The transmitter 210 also transmits capability information related to the low-power wake-up signal to the base station 10. The receiver 220 receives various signals wirelessly 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 configuration 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 configuration information received by the receiver 220 from the base station 10. The setting unit 230 also stores pre-configured configuration information. The content of the configuration information is, for example, information related to the operations described in the embodiments.

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

[0279] (Hardware configuration) The block diagrams (FIGS. 18 and 19) 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.

[0280] 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. 20 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.

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

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

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

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

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

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

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

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

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

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

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

[0292] <Configuration of this embodiment> (Section 1) a control unit that supports SSB (SS / PBCH block)-less SCell (Secondary Cell) and on-demand SSB; a communication unit for receiving settings related to always-on SSB; A terminal in which, when the communication unit receives an on-demand SSB, the control unit assumes that the settings related to the always-on SSB do not include the absolute position of the frequency of the always-on SSB. (Section 2) The terminal according to claim 1, wherein the control unit assumes that a reference cell is always set in the settings related to the always-on SSB. (Section 3) The communication unit receives a setting related to an SSB-less SCell or an on-demand SSB, The terminal according to claim 1, wherein the control unit ignores settings related to the SSB-less SCell or on-demand SSB. (Section 4) The terminal according to claim 1, wherein the control unit performs on-demand SSB operation while the on-demand SSB is activated, and performs SSB-less SCell operation while the on-demand SSB is deactivated. (Section 5) The terminal according to claim 1, wherein the control unit sets a cell from which an on-demand SSB is transmitted as a reference cell for an SSB-less SCell. (Section 6) Procedures for supporting SSB (SS / PBCH block)-less SCell (Secondary Cell) and on-demand SSB; receiving the Always-On SSB configuration; and a procedure in which, when an on-demand SSB is received, the terminal assumes that the settings relating to the always-on SSB do not include the absolute frequency position of the always-on SSB.

[0293] Any of the above configurations provides a technique for clarifying the terminal operation when an always-on SSB (SS / PBCH Block) is not transmitted in communication with a base station that can transition to a power saving state. Furthermore, according to paragraphs 2 to 5, the BS and UE agree on the SSB to refer to when the parameter absoluteFrequencySSB is not set, allowing appropriate time-frequency synchronization, AGC, and measurement-related operations to be performed.

[0294] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, 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; two or more items may be combined as needed, and items described in one item may apply to items 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 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0307] 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 "a terminal is configured to ..." or "configure UE to ..." may include the operation of "a base station transmits configuration information regarding the configuration of the terminal" and the operation of "a terminal configures a predetermined operation based on the configuration information."

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

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

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

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

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

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

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

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

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

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

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

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

[0320] 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 30 network nodes 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device

Claims

1. A control unit that supports an SSB (SS / PBCH block)-less SCell (Secondary Cell) and on-demand SSB; a communication unit for receiving settings related to always-on SSB; A terminal in which, when the communication unit receives an on-demand SSB, the control unit assumes that the settings related to the always-on SSB do not include an absolute position of the frequency of the always-on SSB.

2. The terminal according to claim 1 , wherein the control unit assumes that a reference cell is always set in the always-on SSB setting.

3. The communication unit receives a setting related to an SSB-less SCell or an on-demand SSB, The terminal according to claim 1 , wherein the control unit ignores the setting related to the SSB-less SCell or on-demand SSB.

4. The terminal according to claim 1 , wherein the control unit performs an on-demand SSB operation while the on-demand SSB is being activated, and performs an SSB-less SCell operation while the on-demand SSB is being deactivated.

5. The terminal according to claim 1 , wherein the control unit sets a cell to which an on-demand SSB is transmitted as a reference cell for an SSB-less SCell.

6. Procedures for supporting SSB (SS / PBCH block)-less SCell (Secondary Cell) and on-demand SSB; receiving a configuration for always-on SSB; and a procedure for assuming, when receiving an on-demand SSB, that the settings relating to the always-on SSB do not include an absolute position of the frequency of the always-on SSB.

Images