Terminal and communication method

Abstract

This terminal comprises: a reception unit that receives, from a base station, a setting related to measurement of an on-demand SS / PBCH block (SSB); and a control unit that assumes that the on-demand SSB is triggered on the basis of a trigger of an aperiodic channel state information (CSI) report included in the setting related to the measurement of the on-demand SSB. The reception unit receives the on-demand SSB from the base station. The terminal further comprises a transmission unit that transmits, to the base station, the aperiodic CSI report based on the measurement of the on-demand SSB.

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), which is a successor system to LTE (Long Term Evolution) (also referred to as "5G"), technologies that meet requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and power saving are being studied (for example, Non-Patent Document 1).

[0003] Also, in Release 18 of 3GPP (registered trademark), in order to achieve environmental sustainability, carbon neutrality, SDGs (Sustainable Development Goals), reduction of operating costs, etc., power saving in the network (Network energy savings) has become more important, and methods for power saving are being studied (for example, Non-Patent Document 2).

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

[0005] In order to achieve carbon neutrality and SDGs, the importance of saving power consumption of base stations has increased, and the introduction of intermittent transmission and reception in base stations is being studied. In a cell that supports a power-saving state (energy saving, ES), for example, how an on-demand SSB (SS / PBCH Block) for CSI (Channel State Information) reporting is triggered has not been defined.

[0006] The present invention has been made in view of the above points, and aims to trigger an on-demand SSB (SS / PBCH Block) for CSI (Channel State Information) reporting transmitted from a base station capable of transitioning to a power-saving state.

[0007] According to the disclosed technology, a terminal is provided having a receiving unit that receives settings related to the measurement of an on-demand SSB (SS / PBCH Block) from a base station, and a control unit that assumes that the on-demand SSB is triggered based on a trigger for a periodic CSI (Channel State Information) report included in the settings related to the measurement of the on-demand SSB, wherein the receiving unit further has a transmitting unit that receives the on-demand SSB from the base station and transmits the report of the periodic CSI based on the measurement of the on-demand SSB to the base station.

[0008] According to the disclosed technology, it is possible to trigger on-demand SSB (SS / PBCH Block) for CSI (Channel State Information) reporting transmitted from base stations capable of transitioning to a low-power 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 SIB1 according to Embodiment 10 of the present invention. This is a diagram illustrating an example of CSI setting according to Embodiment 10 of the present invention. This is a flowchart illustrating an example of on-demand SSB reception according to Embodiment 10 of the present invention. This is a flowchart illustrating an example of CSI reporting according to Embodiment 10 of the present invention. This is a diagram illustrating an example of on-demand SSB triggering 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 is a diagram illustrating 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. This figure shows an example of the configuration of a vehicle 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 of achieving a reduction in base station power consumption from the perspective of the time domain. Below, specific examples, from Example 1 to Example 4, will be described.

[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 operations assuming base station intermittent reception. Specifically, the terminal 20 identifies the status of base station intermittent reception by RRC, MAC-CE, or DCI. In the case of DCI, the terminal 20 assumes that it receives DCI indicating the status of base station intermittent reception from the base station 10. Details of the instruction by DCI will be described later in Example 3.

[0041] When base station intermittent reception is invalid, the terminal 20 executes uplink transmission as scheduled or set by the base station 10 regardless of the status of base station intermittent reception.

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

[0043] Further, the base station 10 may receive terminal assistance information to determine the value of the aforementioned parameter that defines the wake-up / 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 value of the parameter in consideration of the terminal assistance information reported by the terminal 20.

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

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

[0047] (Example 2) In this example, an example of a method for triggering base station intermittent reception is shown.

[0048] Activation / invalidation of base station intermittent 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 base station reception by combining 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 base station 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, terminal 20 can identify the status of intermittent reception from the base station, and this can be commonly understood by both terminal 20 and 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 / DRX 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 one 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 one 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 is set to all "00", and PRI is set to all "1", terminal 20 may dynamically enable cell DTX. Also, for example, when HPN is set to all "0", RV is set to all "00", MCS is set to all "1", FDRA is set to all "1", and PRI is set to all "1", terminal 20 may dynamically disable cell DTX. Also, for example, when HPN is set to all "0", RV is set to all "00", and TDRA is set to all "1", terminal 20 may dynamically enable cell DRX. Also, for example, when HPN is set to all "0", RV is set to all "00", MCS is set to all "1", FDRA is set to all "1", and TDRA is set to all "1", 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, assuming that a UE is available to another carrier (e.g., an anchor cell), 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] 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.

[0171] Furthermore, a notification may be issued in SCell indicating that the characteristics or period of an existing SSB or an always-on SSB are changed or adapted.

[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] (Example 10) 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 triggered by the UE. A cell that performs this on-demand SIB1 transmission operation will be called an NES cell. The UE acquires the settings (UL-WUS settings) related to UL transmission that triggers on-demand SIB1 in advance. Cell A, which mainly transmits SIB1 periodically or always on, notifies 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.

[0174] Figure 11 is a sequence diagram illustrating an example of operation related to the on-demand SIB1 according to Embodiment 10 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 settings 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] Here, procedures and signaling methods are considered to support on-demand SSB SCell operation for UEs in connection modes configured using CA, for both intraband CA and interband CA.

[0178] For example, a trigger method may be specified. This trigger method may be selected from existing signals, UE uplink wake-up signals using channels, cell on / off instructions via backhaul, or SCell activation / deactivation signaling.

[0179] On-demand SSB transmission may be used by the UE for at least SCell time and frequency synchronization, L1 and L3 measurements, and SCell activation, and may be supported for FR1 and FR2 in non-shared spectra.

[0180] Regarding UE assumptions about SSB transmission on cells that support on-demand SSB SCell operation, the following cases may be considered: Case #1: There is no always-on SSB on the cell. Case #2: Always-on SSB is transmitted periodically on the cell.

[0181] Furthermore, it may be specified whether always-on SSB and on-demand SSB are not cell-defined SSBs when transmitted. Also, for cells that support on-demand SSB SCell operation, and for case #2 (i.e., always-on SSB is transmitted periodically on the cell), only one or both of the following options may be considered for the UE to perform L1 measurements based on on-demand SSB.

[0182] Option 1: CSI reporting settings are associated with both on-demand SSB and always-on SSB. Option 2: CSI reporting settings are associated with either always-on SSB or on-demand SSB.

[0183] Furthermore, it may be specified whether the OD-SSB and the always-on SSB have the same beam. It may also be specified whether the above parameters are set by reusing legacy RRC parameters or by reusing new RRC parameters.

[0184] For cells and case #2 (i.e., always-on SSB is periodically transmitted over the cell) that support on-demand SSB SCell operation, at least the following multiplexing cases may be considered.

[0185] Multiplexing Case #1: There is no time-domain overlap between always-on SSB and on-demand SSB. Multiplexing Case #2: Always-on SSB and on-demand SSB overlap in at least the time or frequency domain.

[0186] For cells that support on-demand SSB SCell operation, at least the following may be supported:

[0187] - On-demand SSBs on cells are not located on a synchronous raster. - On-demand SSBs on cells are non-cell-defining cell (NCD-Cell) SSBs. - OD-SSBs for CD (cell-defining)-SSBs located on a synchronous raster may be supported.

[0188] Regarding the SSB adaptation mechanism in the time domain, PCell (CONNECTED mode) of NES-compatible UE does not necessarily support CD-SSB adaptation on a synchronized raster. Adaptation to SSBs other than CD-SSB may be supported. Adaptation to SSBs not on a synchronized raster may also be supported.

[0189] Regarding the SSB adaptation mechanism in the time domain, the adaptation of an SSB set for a SCell of an NES-enabled UE may be supported in the following cases: • Adaptation to a CD-SSB that includes UE effects compared to legacy operation where the SSB is set for the SCell at a period greater than 20 milliseconds. • Adaptation to an SSB that is not a CD-SSB on a synchronous raster. • Adaptation to an SSB that is not a CD-SSB and is not on a synchronous raster.

[0190] Regarding the UE's assumptions about SSB transmission on a cell that supports on-demand SSB SCell operation, the following cases may be considered.

[0191] Case #1: There are no always-on SSBs on the cell. Case #2: Always-on SSBs are sent periodically on the cell. Case #3: When always-on SSBs and on-demand SSBs are sent, check whether they are cell-defined SSBs. Note that any of the above cases may apply.

[0192] For cells that support on-demand SSB SCell operation, at least the following may be supported for on-demand SSB via a higher layer, such as RRC signaling:

[0193] - On-demand SSB frequency - SSB position within on-demand SSB bursts using signaling similar to ssb-PositionsInBurst - Periodicity of on-demand SSB - Whether it is possible to set two or more on-demand SSB settings for a cell to UE. - Whether a new RRC is introduced or an existing RRC is reused.

[0194] For cells that support on-demand SSB SCell operation, RRC-based signaling may be supported to notify on-demand SSB transmission on the cell, at least when the RRC also configures SCell, activates SCell, and provides on-demand SSB configuration. RRC-based signaling may also be supported for other cases.

[0195] MAC CE-based signaling may be supported to demonstrate on-demand SSB transmission on cells for scenarios #2 and #2A. Deactivation and adaptation of on-demand SSB transmission may be considered separately.

[0196] For cells that support on-demand SSB SCell operation, multiple candidate values ​​can be set by the RRC for at least the following parameters, and applicable values ​​can be indicated by the MAC-CE for on-demand SSB transmission notification to the cell: • On-demand SSB periodicity • Other relevant parameters

[0197] For cells that support on-demand SSB SCell operation, the RRC supports providing at least the following parameters for on-demand SSB configuration, at least for case #1: • Subcarrier interval for on-demand SSB • Physical cell ID for on-demand SSB • Time domain position of on-demand SSB bursts, such as SFN offset and half-frame index • Downlink transmit power for on-demand SSB • The number N of on-demand SSB bursts to be transmitted after the on-demand SSB may be notified • It may be specified whether the above parameters are set by reusing legacy RRC parameters or by reusing new RRC parameters

[0198] CD (Cell defining)-SSB and NCD (Non cell defining)-SSB may be defined as follows (see Non-Patent Document 1).

[0199] When an SSB is associated with an RMSI, the SSB is called a cell-defined SSB (CD-SSB). PCell is always associated with a CD-SSB located on a synchronous raster. When an SSB is not associated with an RMSI, the SSB is called an NCD-SSB. If the active BWP does not contain a CD-SSB, the NCD-SSB can be used to perform RLM, BFD, and RRM measurements, and measurements for RA resource selection within the active DL-BWP. The UE may be configured with multiple SSBs, provided that each BWP consists of at most one SSB (CD-SSB or NCD-SSB).

[0200] The NCD-SSB of BWP may be defined as follows (see Non-Patent Document 3).

[0201] Fields in the MIB associated with CD-SSB and NCD-SSB within the same cell are set to the same value. For example, this may be set in the information element BWP-DownlinkDedicated-nonCellDefiningSSB. If set, the UE operating on that BWP will use that SSB for purposes that the serving cell's CD-SSB would have used if it were not set (e.g., obtaining synchronization, measurement, RLM, BFD, and beam management). Furthermore, other parts of the BWP configuration that refer to an SSB (e.g., "SSB" configured in QCL-Info IE, "ssb-Index" configured in RadioLinkMonitoringRS, CFRA-SSB-Resource, PRACH-ResourceDedicatedBFR) implicitly refer to this NCD-SSB. The NCD-SSB has the same values ​​for the corresponding CD-SSB attributes (e.g., ssb-PositionsInBurst, PCI, ssb-PBCH-BlockPower) as the attribute values ​​set in NonCellDefiningSSB-r17 IE. In the MIB associated with this NCD-SSB, the systemFrameNumber field indicates the frame boundary and frame number of the NCD-SSB. subCarrierSpacingCommon and dmrs-Type A-Position may also be set.

[0202] Figure 12 is a diagram illustrating an example of CSI settings according to Embodiment 10 of the present invention. Periodic CSI (P-CSI) reporting, aperiodic (AP-CSI) reporting, and semi-persistent CSI (SP-CSI) reporting may be set up using the information elements shown in Figure 12.

[0203] AP-CSI-RS and AP-CSI are triggered together by DCI. AP-CSI-RS for channel measurement is transmitted in a slot offset from the DCI that triggers AP-CSI. For NZP-CSI-RS-ResourceSet-aperiodicTriggeringOffset INTEGER(0.6), the offset X is between the slot containing the DCI that triggers the aperiodic NZP CSI-RS resource set and the slot to which the CSI-RS resource set is transmitted, where a value of 0 corresponds to slot 0, a value of 1 corresponds to slot 1, a value of 2 corresponds to slot 2, a value of 3 corresponds to slot 3, a value of 4 corresponds to slot 4, a value of 5 corresponds to slot 16, and a value of 6 corresponds to slot 24.

[0204] The CSI-IM is set to the same time slot as the AP-CSI-RS for efficient CSI measurement. The aperiodic trigger offset of the CSI-IM follows the offset of the associated NZP CSI-RS for channel measurement.

[0205] SP-CSI-RS and SP-CSI are triggered separately (SP-CSI-RS can also be used for AP-CSI). SP-CSI-RS / CSI-IM are activated / deactivated by MAC CE. SP-CSI on PUCCH is activated / deactivated by MAC CE. SP-CSI on PUSCH is activated / deactivated by DCI.

[0206] AP-CSI-RS and AP-CSI are both triggered by DCI. AP-CSI-RS for channel measurement is transmitted in a slot offset from the DCI that triggers AP-CSI.

[0207] The information element NZP-CSI-RS-ResourceSet-aperiodicTriggeringOffset INTEGER(0.6) (see Non-Patent Document 3) may set the following offset: an offset X between a slot containing a DCI that triggers a set of aperiodic NZP CSI-RS resources and a slot to which the CSI-RS resource set is transmitted, where a value of 0 corresponds to slot 0, a value of 1 corresponds to slot 1, a value of 2 corresponds to slot 2, a value of 3 corresponds to slot 3, a value of 4 corresponds to slot 4, a value of 5 corresponds to slot 16, and a value of 6 corresponds to slot 24.

[0208] The CSI-IM is positioned in the same time slot as the AP-CSI-RS for efficient CSI measurement. The non-periodic trigger offset of the CSI-IM follows the offset of the associated NZP CSI-RS for channel measurement (see Non-Patent Document 7).

[0209] Here, with respect to on-demand SSB, if on-demand SSB can be transmitted at a different frequency compared to existing always-on SSB, it may be specified how the frequency information for on-demand SSB is notified. The association between on-demand SSB and BWP may be specified. The configuration of on-demand SSB and always-on SSB, as well as the corresponding UE capabilities, may be specified.

[0210] Therefore, the following operations 1-4 may be performed: Operation 1: On-demand SSB frequency information. Operation 2: UE assumptions regarding BWP association for on-demand SSB transmission. Operation 3: On-demand SSB configuration and limitations. Operation 4: UE capabilities.

[0211] Figure 13 is a flowchart illustrating an example of on-demand SSB reception according to Embodiment 10 of the present invention. In step S401, the UE receives settings for receiving on-demand SSB from the base station. In step S402, the UE receives on-demand SSB based on these settings.

[0212] The following explains Operation 1: On-Demand SSB frequency information.

[0213] The frequency information for on-demand SSB may include the information shown in 1)-3) below.

[0214] 1) Bandwidth portion (BWP) information. Notifies that on-demand SSB will be applied to the BWP. For example, this may be notified by BWP-Id. 2) Measurement target information. Indicates the SSB within the measurement target to which on-demand SSB will be applied. For example, this may be notified by measObjectId. 3) Frequency point information. The absolute frequency position of the on-demand SSB may be notified by either the ARFCN value or the GSCN value. For example, this may be notified by absoluteFrequencySSB / ssbFrequency / ARFCN-ValueNR / dl-CarrierFreq / GSCN value.

[0215] On-demand SSB frequency information may be set or notified as shown in 1) or 2) below.

[0216] 1) These may be set as RRC parameters. For example, on-demand SSB based on RRC, MAC-CE, or DCI triggers may be set. For example, in the case of MAC-CE based on-demand SSB transmission, multiple candidate values ​​may be set by RRC, and the applicable candidates may be notified by MAC-CE. Frequency information, such as ARFCN-ValueNR, may be included as a parameter for each of the candidate values.

[0217] 2) Notification may be given by triggering signaling. For example, on-demand SSB based on RRC, MAC-CE, or DCI triggers may be given. For example, in the case of MAC-CE based on-demand SSB transmission, frequency information, e.g., BWP-Id, may be given in the MAC-CE signaling for on-demand SSB triggering. According to the frequency information, e.g., BWP-Id, the UE may determine the BWP to which on-demand SSB is applied.

[0218] The following describes Operation 2: UE's assumptions regarding BWP association for on-demand SSB transmission.

[0219] After receiving RRC, MAC-CE, or DCI-based signaling to trigger an on-demand SSB transmission, the UE may perform the following actions:

[0220] Alt. 1: If frequency information is not set or indicated, the UE may assume that on-demand SSB was triggered or associated with the following:

[0221] Alt. 1-1: BWP with initial BWP, active BWP, and minimum BWP-ID. Alt. 1-2: BWP that triggers on-demand SSB when the UE receives RRC, MAC-CE, or DCI signaling. Alt. 1-3: All configured BWPs.

[0222] Alt. 2: If BWP information (e.g., BWP-Id) is set or specified, the UE assumes that the on-demand SSB will be triggered or associated with the specified BWP.

[0223] Example #1: If there is a legacy SSB associated with BWP (e.g., always-on SSB), the on-demand SSB will be triggered at the same frequency point as the legacy SSB.

[0224] Example #2: If there is a legacy NCD-SSB associated with BWP (e.g., always-on SSB), the on-demand SSB will be triggered at the same frequency point as the legacy NCD-SSB.

[0225] Example #3: If there is no NCD-SSB associated with the BWP, i.e., if the BWP is associated with the CD-SSB of the serving cell, the UE may assume the following:

[0226] Alt. 2-1: On-demand SSB is triggered at the same frequency point as the CD-SSB of the serving cell.

[0227] Alt. 2-2: If frequency point information for on-demand SSB is available, the UE assumes that on-demand SSB is triggered, transmitted, and associated with the BWP at the frequency point.

[0228] Alt. 2-3: If frequency point information for on-demand SSB is unavailable, the UE assumes that on-demand SSB will be triggered and transmitted at a specific frequency point of the BWP, for example, the nth ARFCN-ValueNR or GSCN value of the BWP (where n is a pre-configured or predefined integer).

[0229] Alt. 2-4: If frequency point information for on-demand SSB is unavailable, the UE assumes that on-demand SSB will not be triggered, transmitted, or ignored.

[0230] Alt. 3: When frequency point information (e.g., ARFCN-ValueNR) or measurement object information (e.g., measObjectId) is set or instructed, the terminal assumes that on-demand SSB has been triggered or associated with that frequency point.

[0231] For example, if there is a legacy SSB (e.g., always-on SSB) at a frequency point or related to the object being measured, the on-demand SSB will be triggered at the same frequency point as the original SSB.

[0232] For example, if there is no legacy SSB (e.g., always-on SSB) at a frequency point, the UE assumes that on-demand SSB is triggered and transmitted at the frequency point. The UE assumes that the triggered on-demand SSB is associated with a BWP that covers the frequency range of the on-demand SSB.

[0233] Alt. 4: When BWP information (e.g., BWP-Id) and frequency point information (e.g., ARFCN-ValueNR) are set or specified, the UE assumes that the on-demand SSB is triggered at the frequency point and associated with the BWP. For example, if there is no NCD-SSB associated with the BWP, the BWP is associated with the on-demand SSB. For example, if there is an NCD-SSB associated with the BWP, and the frequency point of the NCD-SSB is the same as the frequency point of the on-demand SSB, the UE assumes that the on-demand SSB is triggered and transmitted at the frequency point.

[0234] For example, if there is an NCD-SSB associated with BWP, and the frequency point of the NCD-SSB is different from the frequency point of the on-demand SSB, the UE may anticipate the following behaviors: • The on-demand SSB is not triggered, transmitted, or ignored. • The on-demand SSB is triggered, transmitted, or ignored, and the on-demand SSB is not associated with BWP. • The on-demand SSB is triggered, transmitted, or ignored, and the on-demand SSB is associated with BWP. The original NCD-SSB is not associated with BWP. • The on-demand SSB is triggered, transmitted, or ignored, and the on-demand SSB is associated with BWP. The original NCD-SSB is still associated with BWP.

[0235] For the above Alt. 1–Alt. 4, which triggers and sends on-demand SSB, one of the following can be assumed:

[0236] Option 1: Some parameters of the on-demand SSB can be referenced from the legacy or associated SSB (e.g., frequency point, PCI, ssb-PBCH-BlockPower, subcarrier spacing), and other parameters of the on-demand SSB can follow the on-demand SSB settings (e.g., periodicity, offset).

[0237] Option 2: All parameters of the on-demand SSB can follow the on-demand SSB settings (e.g., periodicity, offset).

[0238] In the above case, the legacy SSB associated with BWP may be CD-SSB only, NCD-SSB only, or either CD-SSB or NCD-SSB.

[0239] The following describes operation 3: On-Demand SSB settings and limitations.

[0240] Note that the number of SSBs may also mean the number of frequency points (e.g., ARFCN values) on which the SSB is transmitted. One SSB means an SSB transmitted at one frequency point. In the above case, an SSB transmitted at one frequency point may be an always-on SSB only, an on-demand SSB only, either an always-on SSB or an on-demand SSB, or both an always-on SSB and an on-demand SSB.

[0241] Operation 3-1: Restrictions on Always-On SSB and On-Demand SSB The UE expects or assumes that on-demand SSB and always-on SSB will be transmitted or not transmitted at the same frequency point. The UE expects or assumes that the frequency points of on-demand SSB and always-on SSB associated with the same BWP should be the same or may be different. For example, if no on-demand SSB is configured, each BWP will be configured with at most one SSB. For example, each BWP will be configured with at most one always-on SSB and one additional on-demand SSB at the same frequency point as the always-on SSB. For example, each BWP will be configured with at most one always-on SSB and one additional on-demand SSB at a different frequency point compared to the always-on SSB.

[0242] Operation 3-2: Limitation on the number of candidate parameter sets for On-Demand SSB A single candidate parameter set may include parameters for periodicity, offset, high-frequency information, PCI, ssb-PBCH-BlockPower, subcarrier spacing, and / or ssb-PositionsInBurst for On-Demand SSB. Alt. 1-1: The number of candidate parameter sets per frequency point for On-Demand SSB or On-Demand SSB is not greater than n1. Alt. 1-2: The number of candidate parameter sets per BWP is not greater than n2. Alt. 1-3: The number of candidate parameter sets per serving cell is not greater than n3. Alt. 1-4: The number of candidate parameter sets per UE is not greater than n4.

[0243] Operation 3-3: Limitation on the number of configured On-Demand SSBs A configured On-Demand SSB means that the number of frequency points for the On-Demand SSB is configured regardless of whether it is triggered or not. Alt. 2-1: The number of configured On-Demand SSBs per BWP is not greater than n5. Alt. 2-2: The number of configured On-Demand SSBs per serving cell is not greater than n6. Alt. 2-3: The number of configured On-Demand SSBs per terminal is not greater than n7.

[0244] Operation 3-4: Limitation on the number of triggered / transmitted on-demand SSBs. Triggered on-demand SSBs refer to the number of frequency points on which on-demand SSBs are transmitted. These frequency points may or may not transmit always-on SSBs. Alt. 3-1: The number of triggered or transmitted on-demand SSBs per BWP is not greater than n8. Alt. 3-2: The number of triggered or transmitted on-demand SSBs per serving cell is not greater than n9. Alt. 3-3: The number of triggered or transmitted on-demand SSBs per UE is not greater than n10.

[0245] Operation 3-5: Restrictions on SSBs including either on-demand SSB or always-on SSB The number of SSBs means the following: Option 1: The sum of the number of always-on SSB frequency points and the number of on-demand SSB frequency points. Option 2: The sum of the number of always-on SSB frequency points and the number of on-demand SSB frequency points. If both always-on SSB and on-demand SSB are transmitted within the same frequency point, they are counted only once. Alt. 4-1: The number of SSBs per BWP is n11 or less. Alt. 4-2: The number of SSBs per serving cell is not greater than n12. Alt. 4-3: The number of SSBs per UE is not greater than n13.

[0246] For n1, n2, ... above, n1, n2, ... >= 1 are integers and are either configurable or predefined.

[0247] The following explains Operation 4: UE Capabilities. Note that always-on SSB can be legacy SSB.

[0248] Capabilities related to Operation 3-1: • Ability to support on-demand SSB transmission for the initial BWP. • Ability to support on-demand SSB transmission for both the initial BWP and other BWPs (BWPs other than the initial BWP). • Ability to support on-demand SSB and always-on SSB transmitted at the same frequency point of the initial BWP. • Ability to support on-demand SSB and always-on SSB transmitted at different frequency points of the initial BWP. • Ability to support on-demand SSB and always-on SSB transmitted at the same frequency point of each of the other BWPs. • Ability to support on-demand SSB and always-on SSB transmitted at different frequency points of each of the other BWPs.

[0249] Capabilities related to operations 3-2 / 3-3 / 3-4 / 3-5: • Ability to support the number of candidate parameter sets for on-demand SSB per frequency point, BWP, serving cell, or UE • Ability to support the number of frequency points for on-demand SSB per BWP, serving cell, or UE • Ability to support the number of triggered or transmitted on-demand SSBs per BWP, serving cell, or UE • Ability to support the number of SSBs per BWP, serving cell, or UE

[0250] Here, the on-demand SSB is supported to support either P / SP / A-CSI reporting. The relationship or limitations between the triggering method for the on-demand SSB and the triggering method for the CSI reporting may be specified. Details of the on-demand SSB with A-CSI triggering may be specified. A (aperiodic)-CSI may be replaceable with AP-CSI.

[0251] Therefore, the following operations 5-7 may be performed. Operation 5: Relationship between the triggering method for on-demand SSB and the triggering method for CSI reporting. Operation 6: On-demand SSB is triggered by A-CSI triggering. Operation 7: UE capability

[0252] Figure 14 is a flowchart illustrating an example of a CSI report according to Embodiment 10 of the present invention. In step S501, the UE receives settings from the base station for measuring on-demand SSB. In step S502, the UE measures on-demand SSB based on the settings and generates a CSI report. The UE may trigger on-demand SSB based on the settings. In step S503, the UE transmits the CSI report to the base station.

[0253] The following explains Operation 5: the relationship between the trigger method for on-demand SSB and the trigger method for CSI reporting.

[0254] For on-demand SSB configured for CSI reporting, the UE may assume one or more of the following:

[0255] Alt. 1: There are no restrictions between the triggering method for on-demand SSB and the triggering method for CSI reporting. For example, on-demand SSB triggered or activated by RRC, MAC-CE, or DCI signaling may be used for P, SP, or A-CSI reporting.

[0256] Alt. 2: There are constraints between the triggering method for on-demand SSB and the triggering method for CSI reporting.

[0257] Alt. 2-1: On-demand SSBs triggered or activated by RRC can be used, measured, or configured for P-CSI, SP-CSI on PUSCH, SP-CSI on PUCCH, and A-CSI reporting. For example, UE assumes that on-demand SSBs required for P-CSI, SP-CSI on PUSCH, SP-CSI on PUCCH, and A-CSI are triggered by RRC triggering or activation signaling.

[0258] Alt. 2-2: On-demand SSBs triggered or activated by MAC-CE can be used, measured, or configured for SP-CSI on PUSCH, SP-CSI on PUCCH, and A-CSI reporting. Note that on-demand SSBs may function like quasi-persistent SSBs and may not be suitable for P-CSI reporting. P-CSI cannot be derived during periods when on-demand SSBs are not transmitted. For on-demand SSBs for the above-mentioned CSI reporting, they may overlap or not overlap with on-demand SSB opportunities that have always-on SSB opportunities. For example, on-demand SSBs triggered or activated by MAC-CE that overlap or not overlap with always-on SSB opportunities may not be used, measured, or configured for P-CSI reporting.

[0259] Alt. 2-3: On-demand SSBs triggered or activated by DCI can be used, measured, or configured for A-CSI reporting. Note that on-demand SSBs can function like aperiodic SSBs. For on-demand SSBs for CSI reporting as described above, they may overlap or not overlap with on-demand SSB opportunities that have always-on SSB opportunities. For example, on-demand SSBs triggered or activated by DCI that overlap or not overlap with always-on SSB opportunities may not be used, measured, or configured for P-CSI or SP-CSI reporting. On-demand SSBs and A-CSI reporting can be triggered by the same or separate DCI or DCI field. If an on-demand SSB is configured for A-CSI reporting, triggering A-CSI can trigger the on-demand SSB.

[0260] The following describes operation 6: On-demand SSB is triggered by A-CSI triggering.

[0261] When an A-CSI is triggered by a DCI, the associated on-demand SSB configured for the corresponding trigger or activated CSI may be triggered or activated as appropriate. For example, additional triggering of the on-demand SSB may not be required. Whether or not a UE supports on-demand SSBs triggered by A-CSI triggering can be configured (for example, by the RRC).

[0262] Operation 6-1: If one or more of the following conditions are met, A-CSI triggering can trigger on-demand SSB transmission.

[0263] Alt. 1: When on-demand SSB is set up, used, or measured for A-CSI reporting.

[0264] Alt. 2: When an on-demand SSB is set, used, or measured for a CSI that corresponds to one or more of the CSI triggering states included in the CSI-AperiodicTriggerStateList, it is activated by the DCI's CSI request field.

[0265] Alt. 3: When an on-demand SSB is set, used, or measured for a CSI that matches one or more of the CSI trigger states included in the CSI-AperiodicTriggerStateList, it is activated by the DCI's CSI request field, and there is never an SSB that is always on in the BWP for CSI reporting.

[0266] Alt. 4: When an on-demand SSB is set, used, or measured for a CSI corresponding to one or more CSI trigger states included in the CSI-AperiodicTriggerStateList, it is activated by the DCI's CSI Requests field, and in the BWP for CSI reporting, an SSB index is set for one or more CSI measurements only with the on-demand SSB (i.e., if SSB is always on in the BWP, there is no such SSB index for CSI measurements).

[0267] Alt. 5: If parameters related to resource configuration for on-demand SSB are notified based on the CSI report, the UE measures the on-demand SSB according to the notification. For example, if the on-demand SSB should be measured according to the notification, the on-demand SSB is triggered.

[0268] Operation 6-2: For SSB indexes (multiple indices) of on-demand SSB transmissions activated as in Operation 6-1, one or more of the following may be considered:

[0269] Alt. 1-1: The terminal assumes that all SSB indices configured for on-demand SSB will be sent.

[0270] Alt. 1-2: The terminal assumes that only SSB indices used for CSI measurement configured in on-demand SSB will be transmitted. For example, SSB indices not used for CSI measurement will not be triggered or transmitted.

[0271] Alt. 1-3: If an always-on SSB exists, the terminal assumes that only SSB indices set for on-demand SSB, which are not transmitted via the always-on SSB and are used for CSI measurement, will be transmitted. For example, SSB indices that are not included in the always-on SSB and are not used for CSI measurement will not be triggered or transmitted.

[0272] Operation 6-3: For the transmission time of an activated on-demand SSB transmission as in Operation 6-1, one or more of the following factors may be considered:

[0273] Alt. 2-1: The UE assumes on-demand SSB transmitted by the RRC configuration.

[0274] Alt. 2-2: If there are candidate on-demand SSB opportunities that can be sent in or after the A-CSI report, the A-CSI before the A-CSI report, or in the Z slot's reference resource slot, the UE assumes that the SSB opportunities will be sent or not. The above Z slot is determined by the CSI computation time and the UE's capacity. For example, the UE assumes that no remaining on-demand SSB opportunities will be sent after the A-CSI report.

[0275] Operation 6-4: Regardless of whether the on-demand SSB triggered as in Operation 6-1 can be used for other purposes, the UE assumes one or more of the following:

[0276] Alt. 3-1: Triggered on-demand SSB can only be used for CSI measurements for activated CSI reporting, setting the on-demand SSB as the CSI measurement resource.

[0277] Alt. 3-2: Triggered on-demand SSBs may or may not be used for CSI measurements against other CSIs corresponding to CSI triggering states included in the activated CSI-AperiodicTriggerStateList. For example, they may be used for measurements against other triggered A-CSI reports within the same activated CSI-AperiodicTriggerStateList.

[0278] Alt. 3-3: Triggered on-demand SSB cannot be used for other CSI measurements set or activated for UE. For example, it can be used for measurements for other set P-CSI reports, activated SP or A-CSI reports.

[0279] Alt. 3-4: Triggered on-demand SSB can be used for L3 measurements set for the UE.

[0280] Figure 15 is a diagram illustrating an example of an on-demand SSB trigger according to Embodiment 10 of the present invention. Figure 15 shows an example of Alt. 2-2 of Operation 6-3. As shown in Figure 15, the UE assumes that no remaining on-demand SSB opportunities are sent after the A-CSI report. The on-demand SSB may be set up for the A-CSI and may also be triggered by the DCI that triggers the A-CSI.

[0281] The following explains Operation 7: UE Capabilities. Note that always-on SSB can be legacy SSB.

[0282] - Ability to support on-demand SSB triggered by A-CSI triggering. - Ability to support on-demand SSB triggered together with A-CSI when on-demand is configured for A-CSI. - Ability to support using on-demand SSB triggered by A-CSI trigger for measurements of other CSIs activated in the same trigger state list (CSI-AperiodicTriggerStateList). - The ability to support on-demand SSB triggered by A-CSI triggering is used for measurements of other CSIs for P-CSI, SP-CSI, SP-CSI on PUCCH, or A-CSI reporting. - The ability to support on-demand SSB triggered by A-CSI triggering is used for L3 measurements.

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

[0284] 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, slot number, symbol number) set from the time of transmission / reception of a predetermined DL / UL signal and / or from BS.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0304] 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:

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

[0306] The default value may be as follows:

[0307] - 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

[0308] For all UE actions #A, the UE may perform a default action #B if an action #A could not be performed.

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

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

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

[0312] In the embodiments described above, the UE can determine the bandwidth on which the on-demand SSB is transmitted. The UE can also determine the BWP associated with the on-demand SSB. Furthermore, the UE can receive the on-demand SSB triggered by AP-CSI and perform AP-CSI reporting.

[0313] In other words, a technology is provided to trigger on-demand SSB (SS / PBCH Block) for CSI (Channel State Information) reporting transmitted from base stations capable of transitioning to a power-saving state.

[0314] (Device Configuration) Next, an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above will be explained. The base station 10 and terminal 20 include functions to perform the embodiments described above. However, the base station 10 and terminal 20 may each be equipped with only one of the proposed functions from the embodiments.

[0315] <Base Station 10> Figure 16 is a diagram showing an example of the functional configuration of a base station. 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. Any functional classification and name of the functional unit may be used as long as it can perform the operations according to the embodiment of the present invention. The transmitting unit 110 and the receiving unit 120 may be called the communication unit.

[0316] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. 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 of a higher layer. The transmitting unit 110 also has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, DL data, etc. to the terminal 20. The transmitting unit 110 also transmits setting information, etc., as described in the embodiment.

[0317] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 in a storage device and reads it from the storage device as needed. The control unit 140 performs control of the entire base station 10, including control related to signal transmission and reception. 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. The transmission unit 110 and the reception unit 120 may also be called the transmitter and receiver, respectively.

[0318] <Terminal 20> Figure 17 is a diagram showing an example of the functional configuration of a terminal. As shown in Figure 17, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 17 is merely an example. Any functional classification and name of the functional unit may be used as long as it can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be called the communication unit.

[0319] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The transmitting unit 210 also transmits HARQ-ACK, and the receiving unit 220 receives the setting information and the like as described in the embodiment.

[0320] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-set setting information. The control unit 240 controls the entire terminal 20, including control related to signal transmission and reception. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220. The transmission unit 210 and the reception unit 220 may also be called the transmitter and receiver, respectively.

[0321] The terminal or base station of this embodiment may be configured as one of the terminals or base stations described in the following sections. Furthermore, the following communication methods may be implemented.

[0322] <Configuration relating to this embodiment> (1) A terminal comprising: a receiving unit that receives settings relating to the measurement of an on-demand SSB (SS / PBCH Block) from a base station; and a control unit that assumes that the on-demand SSB is triggered based on a trigger for an aperiodic CSI (Channel State Information) report included in the settings relating to the measurement of the on-demand SSB, wherein the receiving unit further comprises a transmitting unit that receives the on-demand SSB from the base station and transmits the aperiodic CSI report based on the measurement of the on-demand SSB to the base station. (2) The terminal according to paragraph 1, wherein the control unit assumes that the on-demand SSB is triggered based on a trigger for an aperiodic CSI report by RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, or DCI (Downlink Control Information). (3) The terminal according to paragraph 1, wherein the control unit assumes that the on-demand SSB is triggered based on the trigger for the aperiodic CSI report when the on-demand SSB is set for the aperiodic CSI report in the settings relating to the measurement of the on-demand SSB. (4) The terminal according to paragraph 1, wherein the control unit assumes that an SSB index that is not transmitted by always-on SSB is used for the on-demand SSB. (5) The terminal according to paragraph 1, wherein the control unit does not assume that the on-demand SSB is transmitted after the time the aperiodic CSI report is transmitted to the base station. (Clause 6) A communication method in which a terminal performs the following steps: receiving settings related to the measurement of an on-demand SSB (SS / PBCH Block) from a base station; assuming that the on-demand SSB is triggered based on a trigger for an aperiodic CSI (Channel State Information) report included in the settings related to the measurement of the on-demand SSB; receiving the on-demand SSB from the base station; and transmitting the aperiodic CSI report based on the measurement of the on-demand SSB to the base station.

[0323] Any of the above configurations provides a technique for triggering on-demand SSB (SS / PBCH Block) for CSI (Channel State Information) reporting transmitted from a base station capable of transitioning to a power-saving state. According to paragraphs 2 to 5, the UE can receive the on-demand SSB triggered by AP-CSI and perform AP-CSI reporting.

[0324] (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 any combination of at least one of hardware and software. 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 or wireless connections). A functional block may be realized by combining the one device or the multiple devices with software.

[0325] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0326] For example, the base station 10, terminal 20, 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 the base station 10 and terminal 20 according to one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0327] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0328] 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 storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003.

[0329] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0330] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 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 140 of the base station 10 shown in Figure 16 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 17 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, 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 also be transmitted from the network via a telecommunications line.

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

[0332] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0333] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

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

[0335] Furthermore, each device, such as the processor 1001 and the storage device 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.

[0336] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), 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.

[0337] Figure 19 shows an example of the configuration of vehicle 2001. As shown in Figure 19, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0338] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0339] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0340] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front and rear wheel rotation speed signals acquired by rotation speed sensor 2022, front and rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0341] The Information Services Unit 2012 consists of various devices for providing various types of information, such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0342] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0343] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0344] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0345] The communication module 2013 transmits current signals from current sensors input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits, via wireless communication, the following signals input to the electronic control unit 2010: front and rear wheel rotation speed signals acquired by the rotation speed sensor 2022, front and rear wheel air pressure signals acquired by the air pressure sensor 2023, vehicle speed signals acquired by the vehicle speed sensor 2024, acceleration signals acquired by the acceleration sensor 2025, accelerator pedal depression amount signals acquired by the accelerator pedal sensor 2029, brake pedal depression amount signals acquired by the brake pedal sensor 2026, shift lever operation signals acquired by the shift lever sensor 2027, and detection signals for detecting obstacles, vehicles, pedestrians, etc., acquired by the object detection sensor 2028.

[0346] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0347] (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.

[0348] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information 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 combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0349] Each aspect / embodiment described in this disclosure refers to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0350] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0351] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0352] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0353] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0354] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0355] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0356] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

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

[0358] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0359] The terms “system” and “network” as used in this disclosure are interchangeable.

[0360] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0361] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0362] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0363] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0364] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0365] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0366] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0367] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0368] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0369] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0370] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0371] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0372] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

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

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

[0375] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0376] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0377] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

[0379] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B.

[0380] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0381] For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0382] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this.

[0383] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0384] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0385] A TTI with a time length of 1 ms may be called a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, a slot, etc.

[0386] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0388] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0389] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0390] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0391] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a particular neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0392] A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a terminal 20 within a single carrier.

[0393] At least one of the configured BWPs may be active, and terminal 20 does not need to be expected to send or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0394] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

[0396] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0397] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is X") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0398] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0399] This international patent application claims priority based on Japanese Patent Application No. 2024-197769, filed on 12 November 2024, and the entire contents of Japanese Patent Application No. 2024-197769 are incorporated herein by reference.

[0400] 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

A receiving unit that receives settings related to on-demand SSB (SS / PBCH Block) measurement from the base station, The system includes a control unit that assumes the on-demand SSB is triggered based on the trigger of a non-periodic CSI (Channel State Information) report included in the settings for measuring the on-demand SSB, The receiving unit receives the on-demand SSB from the base station, A terminal further comprising a transmitting unit that transmits a report of the non-periodic CSI based on the measurement of the on-demand SSB to the base station. 　 The terminal according to claim 1, wherein the control unit assumes that the on-demand SSB is triggered based on the trigger of the non-periodic CSI report by RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, or DCI (Downlink Control Information). 　 The terminal according to claim 1, wherein the control unit assumes that if the on-demand SSB is set for the non-periodic CSI report in the settings relating to the measurement of the on-demand SSB, the on-demand SSB is triggered based on the trigger for the non-periodic CSI report. 　 The terminal according to claim 1, wherein the control unit assumes that an SSB index that is not transmitted in always-on SSB is used for the on-demand SSB. 　 The terminal according to claim 1, wherein the control unit does not assume that on-demand SSB will be transmitted after the time the non-periodic CSI report is transmitted to the base station. 　 The procedure for receiving settings related to on-demand SSB (SS / PBCH Block) measurement from the base station, A procedure for assuming that the on-demand SSB is triggered based on the trigger of the non-periodic CSI (Channel State Information) report included in the settings for measuring the on-demand SSB, The procedure for receiving the on-demand SSB from the base station, A communication method in which a terminal performs the following steps: transmitting a report of the non-periodic CSI based on the measurement of the on-demand SSB to the base station.

Images