Terminal and communication method

By employing intermittent transmission and reception strategies with adaptive SSB operations, the patent addresses the challenge of conserving power in base stations, enhancing network energy efficiency and aligning with environmental sustainability goals.

WO2026239969A1PCT designated stage Publication Date: 2026-11-19NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/017092
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-12
Filing Date
2026-04-30
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing technologies have not effectively standardized methods for conserving power consumption in base stations, which is crucial for achieving carbon neutrality and Sustainable Development Goals (SDGs) in wireless communication systems.

Method used

Implementing intermittent transmission and reception mechanisms in base stations, including discontinuous reception (DRX) and cell DTX/DRX, with adaptive SSB (SS/PBCH block) operations, using DCI and RRC signaling to manage power-saving states.

Benefits of technology

Reduces power consumption in base stations by optimizing transmission and reception patterns, aligning with environmental sustainability goals and improving network energy efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026017092_19112026_PF_FP_ABST
    Figure JP2026017092_19112026_PF_FP_ABST
Patent Text Reader

Abstract

This terminal comprises: a reception unit that receives, from a base station, a notification relating to on-demand SSB (SS / PBCH block) transmission; and a control unit that, when a secondary cell to which the on-demand SSB is transmitted is activated, assumes that an always-on SSB is transmitted at a certain frequency granularity. The reception unit receives the on-demand SSB from the base station in the secondary cell and receives the always-on SSB from the base station at said frequency granularity.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal and Communication Method

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

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

[0003] Additionally, in Release 18 of 3GPP (registered trademark), in order to achieve environmental sustainability, carbon neutrality, SDGs (Sustainable Development Goals), operational cost reduction, and the like, network energy savings are gaining importance, and methods for achieving power saving are being studied (for example, Non-Patent Document 2).

[0004] 3GPP TS 38.300 V18.0.0 (2023-12) "New WID: Network energy savings for NR", RP-223540, 3GPP TSG RAN Meeting #98-e, December 2022 3GPP TS 38.331 V18.0.0 (2023-12) 3GPP TS 38.211 V18.1.0 (2023-12) 3GPP TS 38.213 V18.1.0 (2023-12) 3GPP TS 38.321 V18.0.0 (2023-12)

[0005] To achieve carbon neutrality and the SDGs, the importance of saving power consumption of base stations is increasing, and the introduction of intermittent transmission and reception in base stations is under consideration. In a cell that supports a power saving state (Energy saving, ES), when performing operations related to SSB (SS / PBCH block) adaptation, it is necessary to perform measurements and the like using the adapted SSB in consideration of the presence of always-on SSB.

[0006] The present invention has been made in view of the above points, and aims to appropriately perform operations related to SSB (SS / PBCH block) adaptation in communication with a base station capable of transitioning to a power-saving state.

[0007] According to the disclosed technology, a terminal is provided which includes a receiving unit that receives notifications from a base station regarding on-demand SSB (SS / PBCH block) transmission, and a control unit that assumes that always-on SSB is transmitted at a certain frequency granularity when the secondary cell on which the on-demand SSB is transmitted is activated, and the receiving unit receives the on-demand SSB from the base station in the secondary cell and receives the always-on SSB from the base station at the frequency granularity.

[0008] According to the disclosed technology, it is possible to properly perform operations related to SSB (SS / PBCH block) adaptation in communication with a base station capable of transitioning to a power-saving state.

[0009] This is a diagram illustrating a wireless communication system according to an embodiment of the present invention. This is a diagram illustrating CDRX in NR release 15. This is a diagram illustrating WUS in NR release 16. This is a diagram illustrating intermittent reception of a base station according to Embodiment 1 of the present invention. This is a diagram illustrating each parameter according to Embodiment 1 of the present invention. This is a diagram illustrating intermittent transmission of a base station according to Embodiment 5 of the present invention. This is a diagram illustrating each parameter according to Embodiment 5 of the present invention. This is a sequence diagram illustrating an example of OSI transmission (1) according to Embodiment 9 of the present invention. This is a sequence diagram illustrating an example of OSI transmission (2) according to Embodiment 9 of the present invention. This is a diagram illustrating an example of on-demand SSB according to Embodiment 9 of the present invention. This is a sequence diagram illustrating an example of operation related to on-demand SSB according to Embodiment 9 of the present invention. This is a sequence diagram illustrating an example of a random access procedure according to Embodiment 9 of the present invention. This is a diagram illustrating an example of SSB according to Embodiment 9 of the present invention. This is a flowchart illustrating an example of SSB adaptation (1) according to Embodiment 10 of the present invention. This is a flowchart illustrating an example of SSB adaptation (2) according to Embodiment 10 of the present invention. This is a diagram illustrating an example of the functional configuration of a base station according to an embodiment of the present invention. This figure shows an example of the functional configuration of a terminal according to an embodiment of the present invention. This figure shows an example of the hardware configuration of a base station or terminal according to an embodiment of the present invention.

[0010] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0011] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. Such existing technologies include, for example, existing NR or LTE, but are not limited to existing NR or LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (e.g., NR), unless otherwise specified.

[0012] Furthermore, in the embodiments of the present invention described below, terms 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), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated as "NR-".

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

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

[0015] (System Configuration) Figure 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. The wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple base stations 10 and terminals 20.

[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 the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. In addition, the TTI (Transmission Time Interval) in the time domain may be a slot, or the TTI may be a subframe.

[0017] The base station 10 transmits synchronization signals and system information to the terminal 20. The synchronization signals are, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, in NR-PBCH and is also called broadcast information. The synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 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 using 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. In addition, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using CA (Carrier Aggregation). Furthermore, terminal 20 may communicate via the primary cell of base station 10 and the primary secondary cell group cell (PSCell: Primary SCG Cell) of other base stations 10 using DC (Dual Connectivity).

[0018] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, 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. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurement based on the reception results of said reference signals. Terminal 20 may be referred to as UE and base station 10 as gNB.

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

[0020] Next, we will explain discontinuous reception (DRX) or connected mode DRX (CDRX) in conventional terminals.

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

[0022] Figure 3 is a diagram illustrating the WUS in NR Release 16. In NR Release 16, a PDCCH-based Wake Up Signal (WUS) can instruct one or more terminals whether to monitor the PDCCH during the next DRX-ON period.

[0023] DCI format 2_6, in which the CRC (Cyclic Redundancy Check) is scrambled by 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] WUS monitoring opportunities are set by an offset from the on-period based on terminal functionality. If the WUS indicates "inactive" (i.e., no data is being sent or received by the terminal), the terminal can skip monitoring during the on-period and immediately enter sleep mode. Additionally, a default terminal behavior can be set in case the PDCCH-based WUS is not detected, for example due to a detection error.

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

[0026] (Conventional Problems) Next, let's discuss conventional problems. In order to achieve carbon neutrality and the SDGs, it is becoming increasingly important to conserve the power consumption of base stations. However, conventionally, there has been a problem in that methods for conserving the power consumption of base stations have not been standardized.

[0027] (Summary of this embodiment 1) Therefore, this embodiment describes an example in which the power consumption of a base station is reduced from the perspective of the time domain. Hereinafter, specific embodiments will be described from Embodiment 1 to Embodiment 4.

[0028] (Example 1) This example describes the operation of the base station when it receives signals intermittently, and defines related concepts.

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

[0030] The concept of intermittent reception at base station 10 is the same as that of intermittent reception at terminal 20. The receiving units and / or parameters to be disabled may be per port, panel, beam, or carrier (or cell).

[0031] Figure 5 is a diagram illustrating the parameters related to Embodiment 1 of the present invention. The base station CDRX may be defined by several parameters listed below. The units of the parameters may be symbols, slots, subframes, milliseconds, or seconds. The units may be different or the same among the parameters. ・drx-onDurationTimer: The period at the start of the DRX cycle ・drx-SlotOffset: The delay before starting drx-onDurationTimer ・drx-InactivityTimer: The period after an uplink reception opportunity during which terminal 20 performs an uplink transmission ・drx-LongCycleStartOffset: Defines when the long DRX cycle (i.e., drx-LongCycle) and short DRX cycle start. - drx-ShortCycle: Short DRX cycle - drx-ShortCycleTimer: Period during which base station 10 follows a short DRX cycle - drx-RetransmissionTimerUL: Maximum period until permission for uplink retransmission is received - drx-HARQ-RTT-TimerUL: Minimum period until permission for uplink retransmission is expected

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

[0033] If intermittent base station reception is enabled, terminal 20 may perform one of the following optional actions:

[0034] <Option 1> Terminal 20 may operate assuming intermittent reception from base stations. Specifically, terminal 20 identifies the status of intermittent reception from base stations using RRC, MAC-CE, or DCI. In the case of DCI, terminal 20 assumes that it receives a DCI from base station 10 indicating the status of intermittent reception from base stations. Details of the instructions using DCI will be described later in Example 3.

[0035] Terminal 20 may transmit an uplink channel while drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL is running, if intermittent reception from base stations is enabled.

[0036] <Option 2> Terminal 20 may ignore intermittent reception from the base station. Specifically, terminal 20 performs uplink transmission as scheduled or configured by base station 10, regardless of the status of intermittent reception from the base station.

[0037] Furthermore, if intermittent base station reception is enabled, base station 10 may perform a schedule or settings that take intermittent base station reception into consideration, or it may perform a schedule or settings regardless of intermittent base station reception. If a schedule or settings that take intermittent base station reception into consideration are performed, the function of intermittent base station reception will be realized even if terminal 20 ignores intermittent base station reception. Conversely, if a schedule or settings that take intermittent base station reception are not performed, and terminal 20 ignores intermittent base station reception, it will transmit unnecessary signals, resulting in wasted power consumption of terminal 20.

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

[0039] If intermittent base station reception is disabled, terminal 20 may perform one of the following optional actions.

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

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

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

[0043] Furthermore, the base station 10 may receive terminal assistance information in order to determine the values of the aforementioned parameters that define the wakeup / sleep period.

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

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

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

[0047] (Embodiment 2) This embodiment presents an example of a method for triggering base station discontinuous reception.

[0048] Activation / deactivation of base station discontinuous reception may be performed by any of the following options.

[0049] <Option 1> The base station 10 may enable or disable intermittent base station reception when an RRC parameter indicating the enablement or disablement of intermittent base station reception is set by the terminal 20 or other network node (e.g., the core network or other base stations).

[0050] <Option 2> When base station 10 receives a MAC-CE command indicating the enablement or disablement of intermittent base station reception from terminal 20 or other network nodes (e.g., the core network or other base stations), it may enable or disable intermittent base station reception.

[0051] <Option 3> When base station 10 receives a PUCCH or UCI included in PUSCH from terminal 20, it may enable / disable intermittent base station reception based on the instructions for enabling / disabling intermittent base station reception included in the UCI.

[0052] The UCI, which includes instructions for enabling / disabling intermittent base station reception, may be a newly defined UCI type that differs from conventional ones. Alternatively, the UCI may be a conventional UCI type such as HARQ-ACK, CSI, or SR.

[0053] Terminal 20 may enable or disable intermittent base station reception by sending a PUCCH or PUSCH to base station 10 to perform an instruction for intermittent base station reception (i.e., activation / deactivation).

[0054] Terminal 20 may receive a DCI from base station 10 indicating the status of intermittent base station reception in order to identify whether the instructions via UCI have been successfully decoded by base station 10 and whether there is a common understanding between base station 10 and terminal 20 regarding the status of intermittent base station reception. Details of the DCI will be described later in Example 3.

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

[0056] Terminal 20 may receive a DCI from base station 10 indicating the status of intermittent base station reception in order to obtain a common understanding of the status of intermittent base station reception between base station 10 and terminal 20. Details of the DCI will be described later in Example 3.

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

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

[0059] <Option 1> The base station 10 may immediately enable or disable intermittent base station reception when any of the options described above that trigger the enabling / disabling of intermittent base station reception are executed.

[0060] <Option 2> The base station 10 may receive instructions regarding the timing of enabling / disabling intermittent base station reception at a certain time interval or at a specified time after receiving the instruction. The unit of the time interval or specified time may be a symbol, slot, subframe, millisecond, second, etc. That is, the base station 10 may enable / disable intermittent base station reception at the specified time when any of the above-described options that trigger the enabling / disabling of intermittent base station reception are executed.

[0061] <Option 3> Base station 10 may enable / disable intermittent base station reception based on newly introduced timers. The enable / disable timers may be the same or different. The timer units may be symbols, slots, subframes, milliseconds, seconds, etc. Base station 10 or terminal 20 or other network nodes may set the timers using RRC or specify them using MAC-CE or UCI / DCI.

[0062] In other words, the timer is executed when any of the options that trigger the activation or deactivation of intermittent base station reception, as described above, is executed. When the timer expires, base station 10 may activate or deactivate intermittent base station reception.

[0063] Let me explain the advantages of the timer. Even if intermittent base station reception is instructed to be enabled, due to processing by terminal 20, actual uplink transmission from terminal 20 may occur after a certain delay following the instruction. In such cases, by introducing a timer, intermittent base station reception can be enabled after a certain period of time, thereby reducing the power consumption of base station 10.

[0064] Furthermore, even if intermittent base station reception is disabled, actual uplink transmissions from terminal 20 may continue for a while after the instruction due to processing by terminal 20. In such cases, by introducing a timer, intermittent base station reception can be disabled after a certain period of time, thereby improving the performance of terminal 20.

[0065] According to this embodiment, it is possible to trigger intermittent reception at base stations and to enable / disable the system when it is triggered.

[0066] (Example 3) This example describes a case in which a terminal receives instructions regarding intermittent reception from a base station via DCI.

[0067] If terminal 20 identifies the status of intermittent reception from the base station and this is commonly understood by both terminal 20 and base station 10, a mechanism should be considered to indicate the status of intermittent reception from base station 10 to terminal 20. For timely notification, DCI (Digital Communication Indication) is a promising option.

[0068] Furthermore, one advantage of having a shared understanding is that when intermittent reception from the base station is enabled, terminal 20 can stop uplink transmission, thus saving power consumption for terminal 20.

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

[0070] Furthermore, 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 intermittent base station reception. The introduced DCI field may have a bit size of 1 bit, with "1" indicating the enabled state and "0" indicating the disabled state. The reverse is also possible.

[0072] <Option 2> It is not necessary to introduce a new DCI field. That is, the status of intermittent base station 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 intermittent base station reception is enabled.

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

[0074] Furthermore, the corresponding DC Ie format may be one of the following options:

[0075] <Option 1> The DCI may be specific to terminal 20.

[0076] <Option 1-1> The base station 10 may use a new DCI format different from the conventional one to indicate the status of intermittent base station reception.

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

[0078] <Option 2> Terminal 20 may use a group-wide DCI.

[0079] <Option 2-1> The base station 10 may use a new DCI format different from the conventional one to indicate the status of intermittent base station reception. The aforementioned new DCI fields may be introduced in the new DCI format along with other new DCI fields for the power saving technology of the base station 10. The base station 10 may scramble the new DCI format with the aforementioned new RNTI (such as GC-RNTI).

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

[0081] Assuming that DCI format 2_6 is being used, the conventional DCI fields in the DCI format may be reinterpreted to indicate the status of intermittent base station reception. For example, the "Wake-up indication" may be used for reinterpretation. An active state may be indicated by "1" and an inactive state by "0," or vice versa.

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

[0083] According to this embodiment, the terminal 20 can identify the status of intermittent reception from the base station, and this can be commonly understood by both the terminal 20 and the base station 10.

[0084] (Example 4) This example describes an instance in which base stations or terminals report capability information to each other regarding intermittent reception between base stations.

[0085] The following capability information may be introduced.

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

[0087] Base station capability information may include information indicating whether or not intermittent base station reception is supported. Furthermore, base station capability information indicating whether or not DCI indications, which show the status of intermittent base station reception, are supported may also be introduced.

[0088] Furthermore, the following terminal capability information may be introduced. For example, terminal capability information indicating whether or not intermittent base station reception is supported may be introduced. Also, terminal capability information indicating whether or not the status of intermittent base station reception is supported may be introduced.

[0089] If terminal 20 has the capability to support identification of the status of intermittent base station reception, it may identify whether the intermittent base station reception function is enabled or disabled. For example, terminal 20 may perform the operation of option 1 shown in Embodiment 1. Alternatively, if terminal 20 does not have the capability to support identification of the status of intermittent base station reception, it may perform the operation of option 2 shown in Embodiment 1.

[0090] Furthermore, terminal capability information indicating whether or not it supports DCI instructions that show the status of intermittent base station reception may be introduced. Additionally, terminal capability information indicating whether or not it supports a new terminal-specific / group-common DCI format may be introduced.

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

[0092] <Option 1> In order to apply intermittent base station reception, it may be required that both base station capability information and terminal capability information indicating support for intermittent base station reception be reported.

[0093] <Option 2> To apply intermittent base station reception, it may be sufficient for either base station capability information or terminal capability information indicating support for intermittent base station reception to be reported.

[0094] According to this embodiment, base stations and terminals can report capability information regarding intermittent reception between base stations to each other.

[0095] The terminal capabilities described in each of the above embodiments may be limited to cases where terminal 20 is a function-reduced terminal, or they may be applicable even when terminal 20 is not a function-reduced terminal.

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

[0097] The mechanism for enabling or disabling the transmitting and receiving unit of the base station 10 is important for reducing power consumption in the base station 10. To reduce power consumption in the base station 10, the application of DL transmission and UL reception is being considered.

[0098] Cell DTX / DRX is useful for achieving DL transmission and UL reception adaptation. However, the detailed operation of Cell DTX / DRX was not clear. Therefore, Examples 5 to 8 will be described below as specific embodiments relating to Cell DTX / DRX.

[0099] (Example 5) Example 5 describes the definition of cell DTX / DRX. Cell DRX may be defined as in Examples 1 to 4 above. Whether or not to execute cell DRX is determined by upper-level layer parameters, and further, the period, start slot, offset and duration may be set. In addition, the applicability of cell DRX may be determined by a quasi-static, dynamic or flexible network state.

[0100] Cell DTX may be defined as described below. Whether or not to perform Cell DTX is determined by higher-layer parameters, which may further set the period, start slot, offset, and duration. The applicability of Cell DTX may also be determined by quasi-static, dynamic, or flexible network conditions.

[0101] <Option 1> Figure 6 is a diagram illustrating intermittent transmission by a base station according to Embodiment 5 of the present invention. As shown in Figure 6, the period during which the base station 10 disables or enables its own transmission unit may be introduced as cell DTX.

[0102] The transmitting 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 shown in 1)-6) below. The units of such parameters may be symbols, slots, subframes, milliseconds, or seconds, or other units. The units may be the same or different among such parameters.

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

[0104] Figure 7 is a diagram illustrating the parameters related to Embodiment 5 of the present invention. As shown in Figure 7, the active time is from the beginning of dtx-LongCycle, after dtx-SlotOffset, for the duration of dtx-onDurationTimer. If DL reception occurs during dtx-LongCycle, the active time ends after dtx-InactivityTimer from the time of DL reception, 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, base station 10 may transmit DL channels or DL ​​signals while dtx-onDurationTimer or dtx-InactivityTimer is operating. As for the operation of terminal 20, when cell DTX is enabled, terminal 20 may receive DL channels or DL ​​signals while dtx-onDurationTimer or dtx-InactivityTimer is operating. Terminal 20 may be assumed to receive DL channels or DL ​​signals when dtx-onDurationTimer or dtx-InactivityTimer is not operating.

[0106] When cell DTX is disabled, terminal 20 may assume that it will receive DL channels or DL ​​signals as notified to or configured to base station 10.

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

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

[0109] (Example 6) Example 6 describes the settings for Cell DTX / DRX.

[0110] <Option 1> Joint configuration may be performed. Cell DTX and Cell DRX may be configured jointly using common parameters. If common parameters (e.g., CellDTXDRX-Config) are configured, Cell DTX and DRX may be enabled. Terminal 20 may appropriately perform the operation of Embodiment 5.

[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, the parameter indicating the on-duration timer may be common to DTX and DRX. For example, the parameter indicating the cycle may be common to DTX and DRX.

[0113] 2) Parameters separated in DTX and DRX. Some parameters may be set individually in DTX and DRX. For example, the parameter indicating the slot offset may be set individually in DTX and DRX.

[0114] Option 1 can reduce the overhead of RRC signaling.

[0115] <Option 2> Separate configuration may be performed. Cell DTX and Cell DRX may be configured individually by separate parameters. If parameters for DTX (e.g., CellDTX-Config) are set, Cell DTX may be enabled. If parameters for DRX (e.g., CellDRX-Config) are set, Cell DRX may be enabled. The parameters for DTX may include the parameters described in Example 5. The parameters for DRX may include the parameters described in Example 1.

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

[0117] (Example 7) Example 7 describes the activation or deactivation of cell DTX / DRX. When cell DTX and cell DRX are set together (Option 1 of Example 6), cell DTX and cell DRX may be activated or deactivated as follows.

[0118] <Option 1> Cell DTX and Cell DRX may be enabled or disabled by RRC signaling. If RRC parameters are set, Cell DTX and Cell DRX may be enabled or disabled. For example, the RRC parameters may be the common parameters in Example 6 (e.g., CellDTXDRX-Config).

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

[0120] <Option 3> Cell DTX and Cell DRX may be enabled or disabled by DCI. Terminal 20 may be dynamically notified by DCI that Cell DTX and Cell DRX have been enabled or disabled. Such notification by 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 (e.g., DCI format 1_1, 1_2, 2_0) or a new format may be defined (e.g., 1_x, 2_x).

[0123] 3) RNTI may be an existing RNTI (e.g., 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 they are 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, HPN is set to all "0", RV to all "00", and TDRA to all "1", terminal 20 may dynamically enable cell DTX and cell DRX. Also, for example, when HPN is set to all "0", RV to all "00", MCS to all "1", FDRA to all "1", and TDRA to all "1", terminal 20 may dynamically disable cell DTX and cell DRX.

[0126] Alt. 2) When scrambling is performed with a new RNTI, and for example, HPN is set to all "0" and RV is set to all "00", terminal 20 may dynamically enable cell DTX and cell DRX. Also, for example, when 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", terminal 20 may dynamically disable cell DTX and cell DRX.

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

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

[0129] <Option 1> Cell DTX or Cell DRX may be enabled or disabled by RRC signaling. If RRC parameters are set, Cell DTX or Cell DRX may be enabled or disabled. For example, the RRC parameters may be the separated parameters in Example 6 (e.g., CellDTX-Config, CellDRX-Config).

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

[0131] <Option 3> Terminal 20 may be dynamically notified by DCI that cell DTX or cell DRX has been enabled or disabled. Such 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 (e.g., DCI format 1_1, 1_2, 2_0) or a new format may be defined (e.g., 1_x, 2_x).

[0134] 3) RNTI may be an existing RNTI (e.g., 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, different sets of DCI fields may be used to enable or disable a cell DTX or a cell DRX, respectively, so that each set indicates either a cell DTX or a cell DRX. For example, if they are a set of existing fields, several fields may be used to enable or disable a cell DTX and a 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, HPN is set to all "0", RV to all "00", and PRI to all "1", terminal 20 may dynamically enable cell DTX. Also, for example, when HPN is set to all "0", RV to all "00", MCS to all "1", FDRA to all "1", and PRI to all "1", terminal 20 may dynamically disable cell DTX. Also, for example, when HPN is set to all "0", RV to all "00", and TDRA to all "1", terminal 20 may dynamically enable cell DRX. Also, for example, when HPN is set to all "0", RV to all "00", MCS to all "1", FDRA to all "1", and TDRA to all "1", terminal 20 may dynamically disable cell DRX.

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

[0138] Furthermore, the same fields used as described above, such as PRI and TDRA (for example, TDRA), may be used to indicate whether CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX are targeted. When different DCI formats are used, the DCI format may indicate whether cell DTX or cell DRX are targeted. 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 with a new RNTI, for example, if HPN is all set to "0", RV is all set to "00", and PRI is all set to "1", terminal 20 may dynamically enable cell DTX. For example, if HPN is all set to "0", RV is all set to "00", MCS is all set to "1", FDRA is all set to "1", and PRI is all set to "1", terminal 20 may dynamically disable cell DTX. For example, if HPN is all set to "0" and RV is all set to "00", terminal 20 may dynamically enable cell DRX. For example, if HPN is all set to "0", RV is all set to "00", MCS is all set to "1", and FDRA is all set to "1", terminal 20 may dynamically disable cell DRX.

[0140] For example, although PRI is used as described above, additional fields are not required to indicate whether to target cell DTX or cell DRX. When different DCI formats are used, the DCI format may indicate whether to target 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.

[0141] For example, if it is a new DCI field, the new DCI field may enable or disable cell DTX or cell DRX. 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", terminal 20 may dynamically enable cell DTX. Also, for example, if the cell DTX identifier is set to "0", terminal 20 may dynamically disable cell DTX. For example, if the cell DRX identifier is set to "1", terminal 20 may dynamically enable cell DRX. Also, for example, if the cell DRX identifier is set to "0", terminal 20 may dynamically disable cell DRX.

[0143] Furthermore, the new DCI field may be called the "Cell DTX DRX identifier". When Cell DTX and Cell DRX are notified together in a common field, for example, if the Cell DTX DRX identifier is set to "01", terminal 20 may dynamically enable Cell DTX or dynamically disable Cell DRX. For example, if the Cell DTX DRX identifier is set to "10", terminal 20 may dynamically enable Cell DRX or dynamically disable Cell DTX. For example, if the Cell DTX DRX identifier is set to "11", terminal 20 may dynamically enable Cell DTX and Cell DRX. For example, if the Cell DTX DRX identifier is set to "00", 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] Furthermore, 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 activation or deactivation of cell DTX or cell DRX as notified by MAC-CE or DCI, as described above, may be either 1) or 2) below.

[0146] 1) Terminal 20 may be immediately enabled or disabled. When MAC-CE or DCI notifies the activation or deactivation of cell DTX or cell DRX, cell DTX or cell DRX may be immediately enabled or disabled.

[0147] 2) Terminal 20 may be enabled or disabled at the notified time. The timing of enabling or disabling 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 the enabling or disabling is notified. The unit of time may be a symbol, slot, subframe, millisecond, or second, etc. When the enabling or disabling of cell DTX or cell DRX is notified via MAC-CE or DCI, cell DTX or cell DRX may be enabled or disabled at the previously notified time.

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

[0149] Therefore, it may operate as shown in Options 1-5 below.

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

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

[0152] <Option 3> If UE DRX is configured (for example, DRX-Config), terminal 20 does not need to assume that a cell DTX is configured whose time position does not match that of UE DRX. If the time positions of cell DTX and UE DRX match, cell DTX and UE DRX may be configured jointly.

[0153] <Option 4> If cell DTX is set, terminal 20 does not need to assume that UE DRX (e.g., DRX-Config) is set if its time position does not match that of cell DTX. If the time positions of cell DTX and UE DRX match, cell DTX and UE DRX may be set jointly.

[0154] <Option 5> Cell DTX and UE DRX may be set on terminal 20 regardless of whether the time positions of cell DTX and UE DRX are aligned or not. Also, if cell DTX is set in addition to UE DRX, the parameters of cell DTX may take precedence. Terminal 20 may ignore the parameters of UE DRX. Terminal 20 may operate as in Example 5. Also, if cell DTX is set in addition to UE DRX, the parameters of both may be applied. Terminal 20 may wake up during the active time of both cell DTX and cell DRX.

[0155] The above statement, "The time positions of cell DTX and UE DRX are aligned," may be defined as in 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, if the long cycles are the same for cell DTX and UE DRX, the time positions of cell DTX and UE DRX may be defined as being aligned regardless of the active time within the long cycle. That is, if the long cycle of cell DTX (e.g., dtx-LongCycle) and the long cycle of UE DRX (e.g., drx-LongCycle) are the same, the time positions may be defined as being 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 time positions of cell DTX and UE DRX are aligned, depending on the active time within the long cycle. If the on-period timers and slot offsets (e.g., dtx-LongCycle, drx-LongCycle, dtx-onDurationTimer, drx-onDurationTimer, dtx-SlotOffset, drx-SlotOffset) in the long cycle are the same for cell DTX and UE DRX, it may be defined that the time positions of cell DTX and UE DRX are aligned. Furthermore, other parameters (e.g., dtx-InactivityTimer, drx-InactivityTimer, etc.) may be additionally considered to determine whether the above definition is satisfied.

[0159] <Option 2> If, in addition to the long cycle, the short cycle is the same for cell DTX and UE DRX, then the time positions of cell DTX and UE DRX may be defined as being 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 cycles are the same for cell DTX and UE DRX, the time positions of cell DTX and UE DRX may be defined as being aligned regardless of the active time within the short cycle. That is, 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, the time positions may be defined as being aligned.

[0161] <Option 2-2> If the short cycle is the same for cell DTX and UE DRX, 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, it may be defined that the time positions of cell DTX and UE DRX are aligned.

[0162] (Summary of this embodiment 3) (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, transmitting on-demand S1B1 or SSB to idle UEs, and transmitting on-demand SSB and other DL signals to connected UEs in SCell is being considered. Note that SSB may be replaced with an SS / PBCH block. Note that " / " may be replaced with "and / or", "and", or "or".

[0164] The methods described in 1)-3) below have been considered to trigger on-demand SSB and / or SIB1 transmission.

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

[0166] Furthermore, operation without SSB and / or SIB1 may be performed in multi-carrier scenarios. For example, when it is assumed that the UE has the availability of other carriers (e.g., anchor cells), SSB and / or SIB1 may be absent in non-anchor NES cells for idle or inactive UEs.

[0167] The choice between on-demand SSB and / or SIB1 transmission and transmission without SSB and / or SIB1 may be determined based on the advantages in the target scenario. Optimization of common signal and / or channel transmission is also being considered.

[0168] Figure 8 is a sequence diagram illustrating an example (1) of OSI (On-demand system information) transmission according to Embodiment 9 of the present invention. Figure 8 is an example of an MSG1 (Message 1 in Random Access Procedure) based SIB request, and CFRA (Contention Free Random Access) may be assumed. In step S101, terminal 20 transmits a system information request indicating a specific SIB type to base station 10 by using pre-allocated PRACH resources and a preamble in MSG1. In step S102, base station 10 transmits MSG2 to terminal 20 in response. In step S103, base station 10 transmits the requested system information to terminal 20.

[0169] Figure 9 is a sequence diagram illustrating an example (2) of OSI transmission according to Embodiment 9 of the present invention. Figure 9 is an example of an MSG3 (Message 3 in Random Access Procedure) based SIB request, and CBRA (Contention Based Random Access) may also be assumed. In step S201, terminal 20 transmits MSG1 to base station 10. In step S202, base station 10 transmits MSG2 to terminal 20. In step S203, terminal 20 transmits MSG3 to base station 10, which contains information indicating a system information request. In step S204, base station 10 transmits MSG4 to terminal 20. In step S205, base station 10 transmits the requested system information to terminal 20.

[0170] Under the existing specifications, SIB1 (System information block 1), which is transmitted periodically and always on, is being considered for specification extension to enable on-demand transmission via UE trigger. Cells that perform this on-demand SIB1 transmission operation will be called NES cells. The UE will acquire in advance the settings (UL-WUS settings) related to UL transmission that triggers on-demand SIB1. Cell A, which mainly transmits SIB1 periodically or always on, will notify the UE of the UL-WUS settings. After camp-on to the NES cell, the WUS settings may also be notified from the NES cell.

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

[0172] As shown in Figure 10, regarding the operation related to on-demand SSB, Scenario #2 considers the operation when SCell is set to an inactive state. Scenario #2A considers the operation when an SCell activation command is received. Scenario #3A considers the operation from the time the SCell activation command is received until SCell activation is completed. Scenario #3B considers the operation when SCell activation is completed, or after SCell activation is completed.

[0173] Furthermore, the case where SCell is configured with an on-demand SSB as shown in Figure 10 and SCell activation is performed may be referred to as Case #1. Alternatively, the case where SCell is configured with a legacy SSB, i.e., an always-on SSB, and SCell activation is performed may be referred to as Case #2.

[0174] Figure 11 is a sequence diagram illustrating an example of operation relating to an on-demand SSB according to Embodiment 9 of the present invention. In step S301, the UE completes cell selection or cell re-selection and camps on to cell A. In step S302, the UE receives the WUS configuration from cell A via SIB-X or individual RRC signaling.

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

[0176] In step S307, the NES cell sends 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 to the NES cell.

[0177] Figure 12 is a sequence diagram illustrating an example of a random access procedure according to Embodiment 9 of the present invention. In step S401, the UE performs PSS detection. The UE performs time and frequency synchronization and obtains a portion of the physical cell ID. In step S402, the UE performs SSS detection. The UE obtains a portion of the physical cell ID. In step S403, the UE performs PBCH-DMRS detection. The UE detects the SSB index or a portion of the SSB index within a 5ms half-frame. In step S404, the UE receives the PBCH. The UE obtains the SFN, the wireless frame timing of the SSB index, settings necessary for obtaining the RMSI, and information indicating whether or not camp-on to the cell is possible. Steps S401 to S404 correspond to the operation of receiving the SS / PBCH block.

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

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

[0180] In step S410, Msg3 is sent via PUSCH. The UE sends an RRC setup request including the UE-ID. In step S411, the UE receives Msg4-PDCCH, and in step S412, it 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 sends HARQ-ACK corresponding to Msg4 via PUCCH.

[0181] Table 1 shows examples of masks for existing PRACH resources (see Non-Patent Document 6).

[0182]

[0183] Under the existing specifications, the PRACH resource basically uses the mask shown in Table 1 when multiple ROs exist for the same SSB. The mask can only be applied if the value of ssb-perRACH-Occasion is an integer greater than 1. Therefore, it cannot be applied in cases other than the above, for example, when only a single RO is assigned to a certain SSB. Furthermore, the allowed indexes are configured to enable the resources indicated in the table and disable or mute the others.

[0184] Figure 13 is a diagram illustrating an example of SSB according to Embodiment 9 of the present invention. Compared to LTE, SSB in NR has a wider bandwidth and fewer symbols, from 6RB6 symbols to 20RB4 symbols. In addition, flexibility is improved, and longer period settings are possible than before, such as {5, 10, 20, 40, 80, 160} ms. Multiple candidate symbol positions can be set within a 5 ms half-wireless 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] As shown in Figure 13, transmit beam sweeping is possible for SSB transmission. The same cell ID is used between SSBs, and the SSB index is unique. The SSB index determines the time domain position within a 5ms half-radio frame.

[0186] Note that "existing SSB" may mean any of the following 1)-4), or any combination of the following 1)-4).

[0187] 1) SSBs configured in RRC signaling up to release 18. 2) SSBs configured in servingCellConfigCommon, which is set in SIB1 or RRCReconfiguration. 3) Cell-defined SSBs (CD SSB) or non-cell-defined SSBs (NCD SSB). SSBs configured as NCD-SSBs in RRC signaling. 4) SSBs placed on a sync raster or SSBs placed elsewhere. 5) SSBs configured in servingCellConfig under SCell configuration.

[0188] Note that "on-demand SSB" may mean any of the following 1)-13), or any combination of the following 1)-13). For example, it may mean an SSB triggered by any of the following 1)-13), or an SSB triggered by any combination of the following 1)-13), or it may mean 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".

[0189] 1) An SSB that is notified with settings different from the existing SSB mentioned above. 2) Triggering SSB transmission itself. Turning SSB transmission on or off. 3) Triggering SSB transmission at a certain period X, SSB transmission at a period greater than or equal to a certain period X or less than or equal to a certain period X or longer than or shorter than a certain period X, SSB transmission with a shorter period than the currently transmitted or currently set or most recently received SSB by the UE, SSB transmission with a longer period than the currently transmitted or currently set or most recently received SSB by the UE, or maintaining SSB transmission at the current period. Changing the SSB period. 4) Triggering / not transmitting a certain SS burst (triggering SSB transmission at a certain occasion). It may also trigger the transmission / not transmitting of multiple SSB bursts. 5) Triggering / not transmitting an SS burst within a certain period (triggering SSB transmission at a certain occasion). You may trigger the transmission / non-transmission of multiple SSB bursts. 6) A certain number of SSB transmissions / fewer SSB transmissions / more SSB transmissions / maintaining the current SSB transmission. Changing the SSB position or SSB index. 7) A certain number of SSB transmissions within an SSB burst / fewer SSB transmissions / more SSB transmissions / maintaining the current SSB transmission. Changing the SSB position or SSB index. 8) Triggering a certain SSB. 9) A certain SSB index / triggering an SSB with a different position. 10) A certain SSB within a certain SSB burst. 11) A certain SSB index / triggering an SSB with a different position within a certain SSB burst. 12) A transmitting beam / triggering an SSB transmission that has a predetermined QCL (Quasi Co Location) relationship with another RS. 13) Triggering an SSB transmission that has a predetermined QCL relationship with a transmit beam used for each SSB with a different SSB index / position, or with another RS.

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

[0191] The conditions that are met or that a predetermined setting is notified in steps S501 and S601 described later may be any of the following 1)-10), or any combination thereof.

[0192] 1) If existing SSB or always-on SSB is set or being transmitted.

[0193] 2) When a resource from which on-demand SSB is transmitted or can be transmitted is configured or notified via RRC signaling, semi-statically via RRC signaling, or dynamically via MAC-CE or DCI.

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

[0195] 4) When set as TDD, FDD, SUL, Unlicensed, SL, mTRP, DC, FR (Frequency Range) 2 or FR1, or when not set.

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

[0197] 6) The transmission characteristics of the on-demand SSB are predetermined, for example, periodic, quasi-sustaining, 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.

[0198] 7) When there is a predetermined relationship between on-demand SSB and existing SSB or always-on SSB. For example, when they have the same FR, frequency, or BWP.

[0199] 8) When there is a predetermined relationship between the cell to which the on-demand SSB is transmitted, configured or notified, and (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., the conditions for SSB-less SCell) is met, when other predetermined time-frequency resources are the same, or when other predetermined time-frequency resources are different.

[0200] 9) When the SCell to which the on-demand SSB is sent, configured, or notified is in a predetermined state. For example, SCell activated, SCell deactivated, SCell dormancy, SCell activation procedure in progress, deactivation procedure in progress, BWP enabled, or BWP deactivated.

[0201] 10) When the on-demand SSB is associated with or used for a predetermined purpose. For example, such predetermined purpose may be SCell activation, L1 measurement, L3 measurement, SCell beam fault recovery, power control, SCell time synchronization, SCell frequency synchronization, recovery from hibernation for channel estimation (QCL), or known cell transition.

[0202] Furthermore, for all of items 1) through 10) above, it may be limited to cases where X or more, X or less, or X equal predetermined conditions or settings are met. X may be set by RRC signaling, different pre-defined values ​​may be defined by SCS, or it may be reported by UE capability.

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

[0204] (Example 10) For SCells that transmit on-demand SSB, they are classified into Case #1 and Case #2 depending on whether or not they transmit always-on SSB. In Case #1 and Case #2, UE capabilities are defined individually, as are the feasibility of L1 / L3 measurement using on-demand SSB and the notification scheme for activation or deactivation of on-demand SSB.

[0205] In SCell, which operates on-demand SSB, case #2, where SSB is always on, is being considered. However, the definition of "always on SSB" and "being transmitted" is unclear. Furthermore, if always on SSB is defined and transmitted on a per-BWP basis, the presence or absence of always on SSB, i.e., case #1 or case #2, may change depending on the operation related to a given BWP, potentially affecting the operation of the UE using SSB.

[0206] Therefore, it may be specified which scenarios or scopes require the presence of SSB or always-on SSB. Furthermore, constraints may be placed on scenario transitions or BWP transitions.

[0207] Figure 14 is a flowchart illustrating an example (1) of SSB adaptation according to Embodiment 10 of the present invention. In step S501, a predetermined condition is met or a predetermined setting is notified to the UE. In step S502, the UE may assume that always-on SSB is transmitted or set at a predetermined frequency granularity in a predetermined state of the CA or SCell, or it may assume that on-demand SSB is set, transmitted or notified only in the frequency range in which always-on SSB is transmitted or set.

[0208] The specified state of CA or SCell described above may be any combination or any case described below.

[0209] - The state in which SCell is activated, the state in which SCell is deactivated, the state in which SCell is suspended, during the activation procedure, during the deactivation procedure, and the state from the receipt of the SCell activation or deactivation command until the completion of activation or deactivation as defined in existing non-patent literature 5. - Activated BWP, deactivated BWP, suspended BWP.

[0210] Furthermore, this operation may be performed if at least one [S]Cell that is configured, notified, or transmitted for on-demand SSB is in the above state, or if on-demand SSB is transmitted for X [or more / less than / equal to] [S]Cells (where X is configured in the RRC signaling, is a predefined value that differs depending on the SCS, or is reported in the UE capability), and the predetermined unit or granularity of the number (the range in which the number is counted) may be 1 UE, the number notified within a single signaling, the cell group unit, or the FR unit.

[0211] The above-mentioned predetermined frequency granularity may be any of the following: - A predetermined identical BWP, for example, a BWP set as follows: - initialDownlinkBWP - firstActiveDownlinkBWP - defaultDownlinkBWP - initialDownlinkBWP-RedCap - may be newly defined as initialDownlinkBWP-OdSSB - BWP-DownlinkCommon - BWP-DownlinkDedicated - BWP notified by RRC / DCI (bwp switch) - BWP set as a dormant BWP - BWP whose SCS or numerology is different from any of the above BWPs - BWP which does not include CD-SSB and the overall CORESET#0

[0212] Furthermore, the case where always-on SSB is limited to each BWP (e.g., NCD-SSB), or to each cell (e.g., CD-SSB), and different predetermined frequency granularities may be assumed in each case.

[0213] The above-mentioned predetermined frequency granularity or range in which always-on SSB is transmitted or set may be any of the following: - A predetermined identical cell group. - It may overlap (be the same) at the subcarrier, resource element, RB, PRB, RBG (Resource block group), BWP, carrier, band, or FR level, or there may be two or more X transmits and receives within a predetermined frequency range. The UE may set the above overlap level or overlap range in the RRC, or report the overlap level / overlap range that can be handled in the capacity, and different overlap ranges may be defined / set between different cells / frequencies / bands.

[0214] A UE, or for example a UE supporting the on-demand SCell operation in case #2, may assume that, for an configured but deactivated SCell, if on-demand SSB is configured per BWP, the always-on SSB is transmitted within the same BWP-ID, and if on-demand SSB is configured per cell, both the always-on SSB and the on-demand SSB fall within the frequency range of the initial downlink BWP, and that the value set as the on-demand SSB frequency is within or the same range as the always-on SSB.

[0215] A UE, or for example a UE supporting the on-demand SCell operation in Case #2, may assume that, for firstActiveDownlinkBWP-Id / defaultDownlinkBWP-Id in a configured and activated SCell, if on-demand SSB is configured in BWP, always-on SSB will be transmitted within the same BWP-ID, or if on-demand SSB is configured per cell, both always-on SSB and on-demand SSB will fall within the frequency range of the BWP.

[0216] A UE, or a UE supporting, for example, the on-demand SCell operation in Case #2, may assume that in all scenarios / any CA state, an always-on SSB exists on the same BWP as the on-demand SSB. For BWPs where an always-on SSB exists, all BWPs configured in RRC (Initial downlink BWP, firstActiveDownlinkBWP / defaultDownlinkBWP) must be within the same range, or may be limited to BWPs configured in RRC but activated (i.e., BWPs configured in RRC but not used or deactivated are not included), or may be limited to BWPs configured in RRC but activated and the initial downlink BWP.

[0217] Figure 15 is a flowchart illustrating an example (2) of SSB adaptation according to Embodiment 10 of the present invention. In step S601, a predetermined condition is met or a predetermined setting is notified to the UE. In step S602, the UE does not have to assume that a predetermined state of CA, SCell, or BWP related to the presence or absence of always-on SSB transmission at a predetermined frequency granularity will be changed, that a notification will be received, or that a setting will be made, or if such notification or setting is received, the UE may perform other predetermined handling operations.

[0218] Receiving a notification or setting a change in the specified state of the above CA, SCell, or BWP may be any combination or any case described below.

[0219] Any of the following actions may occur regarding BWP transitions: • BWP switching that changes SCS or numerology • Changing to a BWP other than the one set in RRC as initialDownlinkBWP • Changing to a BWP other than the one set in RRC as firstActiveDownlinkBWP • BWP notified as a BWP switch by RRC or DCI • BWP set as a dormant BWP, or notification to change to that BWP • A BWP inactivity timer is set, and the BWP change is performed by that timer

[0220] The following actions may also occur regarding the transition of the CA scenario: Notifications that trigger scenario #2>2A, 2A>3A, 3A>3B, 3B>2. For example, receiving an SCell activation or deactivation command, the SCell deactivation timer expiring, and after the above event, during the delay period defined in Non-Patent Document 5, 4.3 Timing for secondary cell activation / deactivation.

[0221] According to Non-Patent Document 6, Scenario #2 refers to the period when SCell is configured to a UE but before the UE receives the SCell activation command. Scenario #2A refers to the period when the UE receives the SCell activation command. Scenario #3A refers to the period after the UE receives the SCell activation command until SCell activation is completed. Scenario #3B refers to the period when SCell activation is completed and SCell is activated, or after SCell activation is completed and SCell is activated.

[0222] The other specified handling actions mentioned above may be any combination of the following:

[0223] - The report will show different feasibility and / or switching delay for each case than those reported in the existing BWP switching (Type 1 / Type 2). The UE does not need to anticipate that the NW will configure or notify it of operations that exceed its capabilities. Existing UE capabilities include, for example, bwp-SameNumerology, bwp-DiffNumerology, bwp-SwitchingDelay, and bwp-WithoutRestriction.

[0224] - The capabilities of On-Demand SSB Case #1 (a case where there is no always-on SSB) may be referenced, and the UE may assume that the NW will configure or notify based on those capabilities. The UE does not have to assume that the NW will configure or notify of any operations that exceed those capabilities.

[0225] - The settings, notifications, transmissions, or operations may be ignored, dropped, considered valid or invalid resources, not transmitted or received, not performed, not performed any predetermined operations using the SSB, not performed any predetermined operations using other channels, signals, or PHY layer control information, or responded with a predetermined UL signaling (e.g., HARQ-NACK, RRCReconfigurationfailure), which may include content or parameters indicating reconfiguration, retransmission or failure, reconfiguration resources, retransmission resources, or failure resources.

[0226] The specified period may be any of the following, or it may be determined based on the specified parameters set by BS.

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

[0228] The units in the time direction may be symbols, slots, wireless frames, system frames, sub-milliseconds, milliseconds, or seconds.

[0229] The predetermined time window is defined by parameters and / or specifications set by the BS and / or determined according to the UE capability, or it may be after a certain delay (application delay, processing delay).

[0230] The predetermined time window is defined by parameters and / or specifications set by BS, and / or determined according to UE capability, and / or varies depending on SCS, and / or varies depending on the UE's Timing Advanced value, and / or may be a time window from a reference point, or from a reference point and / or after a certain delay (application delay, processing delay).

[0231] UE may take a minimum value (using a smaller value) or a maximum value (using a larger value) from a predetermined value to determine a predetermined period. The predetermined value may be 1 symbol / 1 slot / 1 millisecond, or it may be a value determined below.

[0232] A value determined by parameters and / or specifications set by the BS and / or determined by the UE's capability and / or differing by the SCS.

[0233] The specified cell in BS may be any of the following: SpCell, PCell, PSCell during DC, active SCell, or Cell that satisfies the specified conditions.

[0234] UE can be in any of the following states: idle, inactive, or RRCconnected, and different actions may be performed depending on the UE state.

[0235] A UE may correspond to and / or report predetermined functions / operations within a predetermined UE capability. The predetermined UE capability may be set at any of the following granularities: UE, FR1, FR2, FR2-1, FR2-2, SCS, band, band combination, feature combination, and / or FSPC unit; or UE, Cell, TDD, FDD unit.

[0236] The specified settings / notifications may be any of the following:

[0237] Configuration / notification may be performed via RRC, MAC-CE, or DCI, and a parameter list configured / notified via RRC, MAC-CE, or DCI may be associated with an identifier (index), and the identifier may be notified to the UE by another notification (MAC-CE, DCI), allowing the UE to determine which parameter lists are activated / applied / used (deactivated, not applied, used).

[0238] Identifiers may be implicitly associated by the order of the list set in the RRC, or they may be associated by explicitly assigning a number.

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

[0240] UE may have multiple parameter lists set, modified, and released by RRC as "AddModlist" and / or "releaselist".

[0241] Settings / notifications may be made via SI / SIB RRC messages, or via individual UE RRC messages (e.g., RRCReconfiguration) for UEs that are connected via RRC.

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

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

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

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

[0246] The setting / notification may be a predetermined DCI format scrambled with X-RNTI, and X-RNTI may be NES-RNTI, SI-RNTI, or not limited to these, and may also be a new DCI format and / or RNTI.

[0247] For all parameters, the UE may perform default values / actions when not set / notified by the BS, and the default actions may be as follows:

[0248] - Do not perform any action - Repeat the previous action - Perform RRC Release / Perform RRC Re-establishment - Send a specified notification to BS - Send a specified notification to the upper layer of UE

[0249] The default value may be as follows:

[0250] - Always 0 / 1 - The value used immediately before - The value set / notified immediately before - A value (pre-)defined by the specifications - A parameter value from another setting / notification - A predetermined timer value

[0251] The term "deactivation" may be replaced with any term indicating invalidation, or with any term indicating update, adaptation, or modification. The RRC parameters may be referenced to Non-Patent Document 3 as appropriate.

[0252] Furthermore, for all UE actions #A, the UE may perform a default action #B if a particular action #A could not be performed.

[0253] The choice of which of the above embodiments to use may be determined by upper-layer parameters, reported from terminal 20 to base station 10 as UE capability, specified by specifications, reported from terminal 20 to base station 10 as UE capability and also determined by upper-layer parameters, or notified by DCI. A base station WUS (Wake up signal) may be used for cell DTX in addition to cell DRX.

[0254] Furthermore, a UE capability indicating whether or not to support cell DTX and cell DRX may be defined. A UE capability indicating whether or not to support dynamic activation or deactivation of cell DTX and cell DRX may be defined. A UE capability indicating whether or not to support cell DTX and cell DRX accompanied by UE DRX or CDRX may be defined.

[0255] Note that Cell DTX / DRX may be replaced with Cell DTX and / or Cell DRX. Activate / Deactivate may be replaced with activate and / or deactivate, activate and / or deactivate, etc.

[0256] The above-described operation allows for L3 / L1 measurements and SCell-related operations to be performed between the BS and UE using appropriate on-demand SSB or adapted SSB, and enables the transmission of on-demand SSB or adapted SSB to be started or stopped at the appropriate timing, eliminating the need for the UE to perform unnecessary operations related to those SSBs.

[0257] In other words, a technology is provided that appropriately performs operations related to SSB (SS / PBCH block) adaptation in communication with a base station capable of transitioning to a power-saving state.

[0258] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processing and operations described above will be explained. The base station 10, network node 30, and terminal 20 include the functions to perform the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each be equipped with only some of the functions in the embodiments.

[0259] <Base Station 10 and Network Node 30> Figure 16 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 16, 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 Figure 16 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated by function.

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

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

[0262] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The contents of the setting information include, for example, information related to the operation described in the embodiment.

[0263] The control unit 140 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0264] <Terminal 20> Figure 17 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 17, 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 Figure 17 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

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

[0266] As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.

[0267] (Hardware Configuration) The block diagrams (Figures 16 and 17) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired, wireless, etc.). A functional block may be realized by combining the above one device or the above multiple devices with software.

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

[0269] In this disclosure, any two terms selected from the set of terms such as circuit, device, unit, module, chip, and means may be used interchangeably. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figures, or it may be configured to omit some of the devices.

[0270] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication by the communication device 1004, or to control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.

[0271] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the baseband signal processing unit, call processing unit, etc., may be implemented by the processor 1001. Although only one processor 1001 is shown in the diagram, there may be multiple processors.

[0272] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line, or provided to the computer device via the communication device 1004, for example.

[0273] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (for example, a processor 1001).

[0274] The memory 1002 is a computer-readable recording medium and may be composed of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), or at least a combination of these. The memory 1002 may also be called a register, cache, main memory, etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing a wireless communication method according to one embodiment of the present disclosure.

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

[0276] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, or communication module, for example. The communication device 1004 may include a high-frequency switch, duplexer, filter, frequency synthesizer, or a combination of at least two of these. For example, a transmit / receive antenna, amplifier section, transmit / receive section, or transmission path interface may be implemented by the communication device 1004. The transmit / receive section may be implemented in a physically or logically separated manner, consisting of a transmit section and a receive section.

[0277] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0279] Furthermore, the base station 10 and terminal 20 may be configured with hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or a combination of at least two of these, and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0280] <Configuration relating to this embodiment> (1) A terminal comprising: a receiving unit that receives notifications from a base station regarding on-demand SSB (SS / PBCH block) transmission; and a control unit that assumes that always-on SSB is transmitted at a certain frequency granularity when the secondary cell on which the on-demand SSB is transmitted is activated, wherein the receiving unit is a terminal that receives the on-demand SSB from the base station in the secondary cell and receives the always-on SSB from the base station at the frequency granularity. (2) The terminal according to paragraph 1, wherein the receiving unit receives the always-on SSB in the initial downlink BWP (Bandwidth Part). (3) The terminal according to paragraph 1, wherein the receiving unit receives the on-demand SSB in a secondary cell that is in the same cell group as the always-on SSB. (Clause 4) The terminal according to Clause 1, wherein the receiving unit receives a notification from the base station that the Bandwidth Part (BWP) on which the always-on SSB is transmitted is changed, and the control unit ignores the notification that the BWP is changed. (Clause 5) The terminal according to Clause 1, wherein the receiving unit receives a notification from the base station that the secondary cell is activated, and the control unit ignores the notification that the secondary cell is activated. (Clause 6) A communication method in which a terminal performs the following steps: receiving a notification from a base station regarding on-demand SSB (SS / PBCH block) transmission; assuming that if the secondary cell on which the on-demand SSB is transmitted is activated, the always-on SSB is transmitted at a certain frequency granularity; and receiving the on-demand SSB from the base station in the secondary cell and receiving the always-on SSB from the base station at the frequency granularity.

[0281] In any of the above configurations, operations related to SSB (SS / PBCH block) adaptation in communication with a base station capable of transitioning to a power-saving state can be properly executed. Furthermore, according to paragraphs 2 to 5, L3 / L1 measurement and SCell operations using appropriate on-demand SSB or adapted SSB can be performed between the BS and UE, and the transmission of on-demand SSB or adapted SSB can be started or stopped at the appropriate timing, and the UE does not have to perform unnecessary operations related to those SSBs.

[0282] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but 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, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0283] Each aspect / embodiment described in this disclosure is an LTE (Long Term Evolution), LTE-A (LTE-Advanced), IMT-Advanced (International Mobile Telecommunications-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), NX (New radio access), FX (Future generation radio access), O-RAN (Open Radio Access Network), W-CDMA (Wideband Code Division Multiple Access) (registered trademark), GSM (Global System for Mobile communications) (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Technology) Engineers) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is also called Wi-Fi 4, x=ac is Wi-Fi 5, x=ax is Wi-Fi 6 or Wi-Fi 6E, x=be is Wi-Fi 7, x=bn is Wi-Fi 8, etc. Note that Wi-Fi is a registered trademark.This may be applied to systems based on technologies such as IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, network virtualization technologies (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 this disclosure may be applied to systems based on a combination of at least two of these technologies. Of course, "based on" means not only systems that utilize the technology, but also systems that utilize extensions or modifications of the technology.

[0284] In this disclosure, any two terms selected from the set of terms such as "Base Station (BS)", "Radio Base 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", "Ground 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.

[0285] Each cell contained within a base station may be referred to as a macrocell, small cell, femtocell, picocell, serving cell, or supercell, among other terms. In this disclosure, any two terms selected from the set of terms such as “cell,” “sector,” “cell group,” “carrier,” “component carrier,” “cluster,” “bandwidth part (BWP),” and “carrier bandwidth” may be used interchangeably.

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

[0287] The terminal may be called 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 appropriate term.

[0288] Each base station and terminal may consist of one or more devices. Devices that constitute at least a part of each base station and terminal may be called transmitting devices, receiving devices, communication devices, etc. Furthermore, the devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, and IoT (Internet of Things) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the possibility of the moving object being in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0289] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations 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), V2X (Vehicle-to-Everything), etc.) or communication over a non-terrestrial network (NTN). In this case, the terminal 20 may have at least some of the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (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 interpreted as a sidelink channel.

[0290] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).

[0291] Furthermore, the term "terminal" in this disclosure may be interpreted as "base station." In this case, the base station 10 may be configured to have the same functions as the terminal 20 described above.

[0292] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or at least two combinations thereof. Physical layer signaling may also be called L1 (Layer 1) control information. MAC signaling may be called, for example, a MAC control element (CE) or a MAC PDU (Protocol Data Unit). RRC signaling may also be called an RRC message or an information element (IE) within the RRC message. The RRC message may be a message used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement reporting, or notification of terminal capability, or it may be an information element within the message. Furthermore, the notification of information may be explicit or implicit. An explicit notification of information is the notification of the information itself, while an implicit notification of information may be the notification of information other than the information in question, or the fulfillment of certain conditions which constitutes notification of the information in question.Furthermore, notification of information may include not only notification between the same layer of different devices (e.g., between lower layers or upper layers of base station 10 and terminal 20), but also notification between different layers within the same or different devices (e.g., between lower and upper layers within base station 10 or terminal 20). Also, notification of information from one device to another may be carried out via one or more devices. With respect to any information described in this disclosure (e.g., variables, constants, parameters, settings), information indicating / specifying (or relating to) the value of such arbitrary information may be notified from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal), even if not specifically stated in the embodiments described above.

[0293] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0294] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, or DU). It is clear that various operations performed for communication with terminals in a RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. A network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) or 5GC (5G Core Network), and provides one or more network functions (NFs).

[0295] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" and "the terminal setting a predetermined action based on the configuration information."

[0296] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during execution.

[0297] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.

[0298] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0299] Radio resources can be defined by a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.

[0300] For example, resources in the time domain may be defined by one or more time units. These one or more time units include, for example, radio frames, subframes, slots, symbols, transmission time intervals (TTI), or at least two combinations thereof, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that do depend on numerology, or both. Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and radio frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. Note that a certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. The time units described above may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as being interchangeable with other time units.

[0301] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.

[0302] Resources in the frequency domain may be defined, for example, by one or more frequency units. Such 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 names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or a variable number that changes depending on the neurology. For example, an RB consists 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 the neurology, for example, 12, but is not limited to this. Similarly, a BWP may consist of, for example, one or more consecutive RBs within a carrier bandwidth, but is not limited to this. For terminal 20, one or more BWPs may be set within one carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as another frequency unit.

[0303] Furthermore, resources in both the time domain and the frequency domain may be defined, for example, by one or more time / frequency units composed of time units and frequency units. Such time / frequency units are, but are not limited to, resource elements (REs) consisting of one symbol and one subcarrier, resource element groups (REGs) consisting of a predetermined number of REs, and control resource sets (CORESETs) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0304] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units. Such spatial units include, but are not limited to, beams, MIMO (Multi Input Multi Output) layers, antenna ports, or at least two combinations thereof.

[0305] Furthermore, resources in the code domain may be defined, for example, by one or more code units. Such code units may be, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.

[0306] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0307] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0308] This international patent application claims priority based on Japanese Patent Application No. 2025-080053, filed on 12 May 2025, and the entire contents of Japanese Patent Application No. 2025-080053 are incorporated herein by reference.

[0309] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A terminal comprising: a receiving unit that receives notifications from a base station regarding on-demand SSB (SS / PBCH block) transmission; and a control unit that assumes that always-on SSB is transmitted at a certain frequency granularity when the secondary cell on which the on-demand SSB is transmitted is activated, wherein the receiving unit receives the on-demand SSB from the base station in the secondary cell and receives the always-on SSB from the base station at the frequency granularity.

2. The terminal according to claim 1, wherein the receiving unit receives the always-on SSB in the initial downlink BWP (Bandwidth Part).

3. The terminal according to claim 1, wherein the receiving unit receives the on-demand SSB in a secondary cell that is in the same cell group as the always-on SSB.

4. The terminal according to claim 1, wherein the receiving unit receives a notification from the base station that the Bandwidth Part (BWP) on which the always-on SSB is transmitted is changed, and the control unit ignores the notification that the BWP is changed.

5. The terminal according to claim 1, wherein the receiving unit receives a notification from the base station that the secondary cell is activated, and the control unit ignores the notification that the secondary cell is activated.

6. A communication method in which a terminal performs the following steps: receiving a notification from a base station regarding on-demand SSB (SS / PBCH block) transmission; assuming that always-on SSB is transmitted at a certain frequency granularity when the secondary cell on which the on-demand SSB is transmitted is activated; and receiving the on-demand SSB from the base station in the secondary cell and receiving the always-on SSB from the base station at the frequency granularity.