Terminal and communication method

Abstract

To trigger an on-demand SSB (SS / PBCH Block) for CSI (Channel State Information) reporting transmitted by a base station capable of transitioning to a power saving state.SOLUTION: A terminal includes a receiving unit that receives settings related to 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 on the basis of a trigger of an aperiodic CSI (Channel State Information) report included in the settings related to measurement of the on-demand SSB, and the receiving unit further includes a transmission unit that receives the on-demand SSB from the base station and transmits a report of the aperiodic CSI on the basis of the measurement of the on-demand SSB to the base station.SELECTED DRAWING: Figure 14

Description

[Technical Field]

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

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

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

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

[0005] To achieve carbon neutrality and the SDGs, it is becoming increasingly important to reduce the power consumption of base stations, and the introduction of discontinuous transmission and reception at base stations is being considered. However, in cells that support energy saving (ES), for example, how on-demand SSBs (SS / PBCH Blocks) for CSI (Channel State Information) reporting are triggered has not been specified.

[0006] The present invention has been made in consideration 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. [Means for solving the problem]

[0007] According to the disclosed technology, there is provided a terminal having a receiver that receives settings related to measurement of an on-demand SSB (SS / PBCH Block) from a base station, and a controller that assumes that the on-demand SSB is triggered based on the triggering of an aperiodic CSI (Channel State Information) report included in the settings related to measurement of the on-demand SSB, wherein the receiver further has a transmitter that receives the on-demand SSB from the base station and transmits a report of the aperiodic CSI based on the measurement of the on-demand SSB to the base station. [Effects of the Invention]

[0008] According to the disclosed technology, it is possible to trigger an on-demand SSB (SS / PBCH Block) for reporting CSI (Channel State Information) transmitted from a base station that can transition to a power saving state. [Brief explanation of the drawings]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0085] The following capability information may be introduced:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0171] In addition, notification may be performed that the characteristics or period of an existing SSB or an always-on SSB in the SCell are changed or adapted.

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

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

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

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

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

[0177] Here, procedures and signaling methods are considered to support on-demand SSB SCell operation for UEs in connected mode configured with CA, for both intraband CA or interband CA.

[0178] For example, a triggering method may be specified, which may be selected from an existing signal, a UE uplink wake-up signal using a channel, a cell on / off indication via backhaul, and an SCell activation / deactivation signaling.

[0179] It should be noted that on-demand SSB transmission can 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 spectrum.

[0180] Regarding UE assumptions regarding SSB transmission on cells supporting on-demand SSB SCell operation, the following cases may be considered. Case #1: No always-on SSB on the cell. Case #2: Always-on SSBs are transmitted periodically on the cell.

[0181] It may also be specified whether always-on SSBs and on-demand SSBs 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 SSBs are transmitted periodically on the cell), only one or both of the following options for the UE to make L1 measurements based on on-demand SSBs may be considered:

[0182] Option 1: The CSI reporting configuration is associated with both on-demand SSB and always-on SSB. Option 2: The CSI reporting configuration is associated with one of always-on SSB and on-demand SSB.

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

[0184] For cells supporting on-demand SSB SCell operation and case #2 (ie, always-on SSBs are transmitted periodically on the cell), at least the following multiplexing cases may be considered:

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

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

[0187] On-demand SSB on a cell is not located on the synchronization raster. On-demand SSB on a cell is a non-cell defining cell (NCD-Cell). · May support OD-SSB for CD (cell defining)-SSB located on the synchronous raster.

[0188] Regarding the SSB adaptation mechanism in the time domain, the PCell (CONNECTED mode) of an NES-enabled UE may not support adaptation to CD-SSB on a synchronous raster, may support adaptation to SSBs that are not CD-SSBs, or may support adaptation to SSBs that are not on a synchronous raster.

[0189] Regarding the adaptation mechanism of SSB in the time domain, the adaptation of SSB configured for an SCell of an NES-enabled UE may be supported for the following cases: Adaptation to CD-SSB including UE impact compared to legacy operation where SSB is configured for SCells with a period greater than 20 ms. Adaptation for non-CD-SSB SSB on synchronous raster. Adaptation for SSB that is not on a synchronous raster and is not CD-SSB.

[0190] Regarding UE assumptions regarding SSB transmissions on cells supporting on-demand SSB SCell operation, the following cases may be considered.

[0191] Case #1: No always-on SSB on the cell. Case #2: Always-on SSBs are transmitted periodically on the cell. Case #3: Always-on SSB and on-demand SSB are not cell-defined SSBs when transmitted. Any of the above cases may be applied.

[0192] For cells supporting on-demand SSB SCell operation, at least the following may be supported for on-demand SSB via higher layers, e.g., RRC signaling:

[0193] On-demand SSB frequencies SSB positions within an on-demand SSB burst by using signaling similar to ssb-PositionsInBurst On-demand SSB periodicity ·Whether it is possible to configure more than one on-demand SSB configuration for a cell to a 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 indicate on-demand SSB transmissions on the cell, at least if this RRC also configures the SCell, activates the 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 indicate on-demand SSB transmission on a cell for scenarios #2 and #2A, although deactivation and adaptation of on-demand SSB transmission may be considered separately.

[0196] For cells supporting on-demand SSB SCell operation, multiple candidate values ​​can be configured by RRC for at least the following parameters, and the applicable value can be indicated by MAC-CE for on-demand SSB transmission notification for the cell: On-demand SSB periodicity Other related parameters

[0197] For cells that support on-demand SSB SCell operation, support providing at least the following parameters for on-demand SSB configuration by RRC, at least for case #1: On-demand SSB subcarrier spacing Physical Cell ID for on-demand SSB Time domain location of on-demand SSB bursts, such as SFN offset and half-frame index On-demand SSB downlink transmit power The number N of on-demand SSB bursts to be sent after the on-demand SSB may be signaled. 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). A PCell is always associated with a CD-SSB located on the synchronization raster. When an SSB is not associated with an RMSI, the SSB is called an NCD-SSB. If an active BWP does not include a CD-SSB, the NCD-SSB can be used to perform RLM, BFD, and RRM measurements, and measurements for RA resource selection within an active DL-BWP. A 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] The fields in the MIB associated with the CD-SSB and NCD-SSB in the same cell are set to the same value, e.g., they may be set to the information element BWP-DownlinkDedicated-nonCellDefiningSSB. When set, a UE operating in this BWP will use this SSB for purposes for which it would otherwise use the serving cell's CD-SSB (e.g., obtaining synchronization, measurements, RLM, BFD, beam management). Furthermore, other parts of the BWP configuration that refer to an SSB (e.g., "SSB" configured in the QCL-Info IE, "ssb-Index" configured in the 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) apart from the attribute values ​​set in the NonCellDefiningSSB-r17 IE. In the MIB related to this NCD-SSB, the systemFrameNumber field indicates the frame boundary and frame number of the NCD-SSB. The subCarrierSpacingCommon and dmrs-TypeA-Position may be set.

[0202] Fig. 12 is a diagram illustrating an example of CSI configuration according to a tenth embodiment of the present invention. Periodic CSI (P (periodic)-CSI) reporting, aperiodic (AP (aperiodic)-CSI) CSI reporting, and semi-persistent CSI (SP (semi-persistent)-CSI) reporting may be configured by the information elements illustrated in Fig. 12.

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

[0204] CSI-IM is set to the same time slot as AP-CSI-RS for efficient CSI measurement, and the aperiodic trigger offset of 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] The AP-CSI-RS and AP-CSI are both triggered by the DCI, and the AP-CSI-RS for channel measurements is transmitted in an offset slot relative to the DCI that triggers the AP-CSI.

[0207] The information element NZP-CSI-RS-ResourceSet-aperiodicTriggeringOffset INTEGER(0.6) (see 3GPP TSE101666) may set the following offset: offset X between the slot containing the DCI triggering the aperiodic NZP CSI-RS resource set and the slot where the CSI-RS resource set is transmitted, where the value 0 corresponds to 0 slot, the value 1 corresponds to 1 slot, the value 2 corresponds to 2 slots, the value 3 corresponds to 3 slots, the value 4 corresponds to 4 slots, the value 5 corresponds to 16 slots and the value 6 corresponds to 24 slots.

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

[0209] For on-demand SSBs, the specification may specify how frequency information for on-demand SSBs is notified if they can be transmitted at a different frequency than the existing always-on SSBs. The specification may also specify the association between on-demand SSBs and BWPs. The specification may also specify the configuration of on-demand SSBs and always-on SSBs and the corresponding UE capabilities.

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

[0211] 13 is a flowchart illustrating an example of on-demand SSB reception according to a tenth embodiment of the present invention. In step S401, the UE receives a setting for receiving on-demand SSBs from the base station. In step S402, the UE receives on-demand SSBs based on the setting.

[0212] Operation 1: Frequency information for on-demand SSB will be explained below.

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

[0214] 1) Bandwidth Part (BWP) information. This indicates that on-demand SSB is applied to the BWP. For example, this may be indicated by the BWP-Id. 2) Measurement object information. Indicates the SSB within the measurement object to which the on-demand SSB applies. For example, it may be notified by measObjectId. 3) Frequency Point Information. The absolute frequency location of the on-demand SSB may be reported using either the ARFCN value or the GSCN value. For example, absoluteFrequencySSB / ssbFrequency / ARFCN-ValueNR / dl-CarrierFreq / GSCN value.

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

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

[0217] 2) It may be notified by triggering signaling. For example, an on-demand SSB based on an RRC, MAC-CE, or DCI trigger may be signaled. For example, in the case of a MAC-CE-based on-demand SSB transmission, frequency information, such as a BWP-Id, may be signaled in the MAC-CE signaling for on-demand SSB triggering. According to the frequency information, such as a BWP-Id, the UE may determine the BWP to which the on-demand SSB applies.

[0218] Action 2: UE assumption regarding BWP association for on-demand SSB transmission is described below.

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

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

[0221] Alt.1-1: Initial BWP, active BWP, BWP with minimum BWP-ID. Alt. 1-2: BWP in which the UE receives RRC, MAC-CE or DCI signaling to trigger an on-demand SSB. Alt.1-3: All configured BWPs.

[0222] Alt. 2: If BWP information (eg, BWP-Id) is set or indicated, the UE assumes that an on-demand SSB is triggered or associated with the indicated BWP.

[0223] Example #1: If there is a legacy SSB (eg, an always-on SSB) associated with the BWP, 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 (eg, always-on SSB) associated with the BWP, the on-demand SSB is 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 serving cell's CD-SSB.

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

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

[0229] Alt. 2-4: In the absence of frequency point information for an on-demand SSB, the UE assumes that an on-demand SSB is not 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 indicated, the terminal assumes that an on-demand SSB is triggered or associated with the frequency point.

[0231] For example, if there is a legacy SSB (eg, an always-on SSB) at the frequency point or associated with the measurement target, 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 an 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: If BWP information (e.g., BWP-Id) and frequency point information (e.g., ARFCN-ValueNR) are set or indicated, 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 an 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 the BWP and the frequency point of the NCD-SSB is different from the frequency point of the on-demand SSB, the UE may assume the following behavior. On-demand SSBs are not triggered, transmitted or ignored. On-demand SSBs can be triggered, transmitted or ignored, and on-demand SSBs are not associated with a BWP. On-demand SSBs are triggered, transmitted or ignored. On-demand SSBs are associated with a BWP. The original NCD-SSB is not associated with a BWP. The on-demand SSB is triggered, transmitted or ignored, and the on-demand SSB is associated with the BWP. The original NCD-SSB is still associated with the BWP.

[0235] For the above Alt.1-Alt.4 where on-demand SSBs are triggered and transmitted, one of the following can be assumed:

[0236] Option 1: Some of the 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 configuration (e.g., periodicity, offset).

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

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

[0239] Operation 3: On-demand SSB setting and restrictions will be explained below.

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

[0241] Action 3-1: Always-on SSB and on-demand SSB restrictions The UE expects or assumes that on-demand SSBs and always-on SSBs may or may not be transmitted at the same frequency point. The UE expects or assumes that the frequency points of the on-demand SSB and the always-on SSB associated with the same BWP should be the same or can be different. For example, if no on-demand SSBs are configured, each BWP is configured with at most one SSB. For example, each BWP is 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 is 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] Action 3-2: Limiting the number of candidate parameter sets for on-demand SSB One candidate parameter set may include the following parameters for on-demand SSB: periodicity, offset, frequent frequency information, PCI, ssb-PBCH-BlockPower, subcarrier spacing, and / or ssb-PositionsInBurst. Alt.1-1: The number of candidate parameter sets per on-demand SSB or frequency point of 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] Action 3-3: Limiting the number of on-demand SSB settings Configured On-Demand SSB means that the number of frequency points for 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 on-demand SSBs configured per serving cell is not greater than n6. Alt.2-3: The number of on-demand SSBs configured per terminal is not greater than n7.

[0244] Action 3-4: Limiting the number of triggered / transmitted on-demand SSBs Triggered on-demand SSB refers to the number of frequency points at which on-demand SSBs are transmitted, where always-on SSBs may or may not be transmitted. Alt.3-1: The number of on-demand SSBs triggered or transmitted per BWP is not greater than n8. Alt.3-2: The number of on-demand SSBs triggered or transmitted 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] Action 3-5: Restrictions on SSB, including either on-demand SSB or always-on SSB The number of SSBs means the following: Option 1: The number of always-on SSB frequency points plus the number of on-demand SSB frequency points. Option 2: The number of frequency points for always-on SSB plus the number of frequency points for on-demand SSB. If always-on SSB and on-demand SSB are transmitted within one 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] Regarding n1, n2, and so on above n1, n2,...>=1 are integers and can be set or predefined.

[0247] Below, we will explain Action 4: UE Capability. Note that the always-on SSB may be a legacy SSB.

[0248] Abilities related to Movement 3-1: Ability to support on-demand SSB transmission for initial BWP -On-demand SSB transmission must be supported 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 in the initial BWP Ability to support on-demand SSB and always-on SSB transmitted at the same frequency points as each of the other BWPs Ability to support on-demand SSB and always-on SSB transmitted at different frequency points for each of the other BWPs

[0249] Abilities related to Actions 3-2 / 3-3 / 3-4 / 3-5: Ability to support number of candidate parameter sets for frequency points, BWP, on-demand SSB per serving cell or UE Ability to support BWP, number of SSB frequency points on demand per 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 BWP, number of SSBs per serving cell or UE

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

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

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

[0253] Operation 5: Relationship between the triggering method for on-demand SSB and the triggering method for CSI reporting will be described below.

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

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

[0256] Alt. 2: There are constraints between the triggering methods for on-demand SSB and 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, the UE assumes that on-demand SSBs requested by P-CSI, SP-CSI on PUSCH, SP-CSI, and A-CSI on PUCCH are triggered by RRC trigger or activation signaling.

[0258] Alt. 2-2: On-demand SSBs triggered or activated by the MAC-CE can be used, measured, or configured for SP-CSI on the PUSCH, SP-CSI on the PUCCH, and A-CSI reporting. Note that on-demand SSBs function like quasi-persistent SSBs and may not be suitable for P-CSI reporting. For example, P-CSI cannot be derived for periods when on-demand SSBs are not transmitted. Regarding the on-demand SSBs for CSI reporting described above, they may overlap or not overlap with on-demand SSB opportunities with always-on SSB opportunities. For example, among on-demand SSBs triggered or activated by the MAC-CE, SSB opportunities 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. Regarding the on-demand SSBs for CSI reporting described above, they may overlap or not overlap with on-demand SSB opportunities with always-on SSB opportunities. For example, among on-demand SSBs triggered or activated by DCI, SSB opportunities 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 different DCI or DCI fields. If an on-demand SSB is configured for A-CSI reporting, triggering of A-CSI can trigger the on-demand SSB.

[0260] Below, we will explain operation 6: On-demand SSB is triggered by A-CSI triggering.

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

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

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

[0264] Alt.2: Activated by the CSI request field of the DCI when on-demand SSB is configured, used or measured for a CSI that corresponds to one or more of the CSI triggering states included in the CSI-AperiodicTriggerStateList.

[0265] Alt.3: If an on-demand SSB is configured, used or measured for a CSI that corresponds to one or more of the CSI trigger states included in the CSI-AperiodicTriggerStateList, there is no SSB that is always on in the BWP for CSI reporting that is activated by the CSI request field of the DCI.

[0266] Alt. 4: When an on-demand SSB is configured, used, or measured for a CSI corresponding to one or more CSI trigger states included in the CSI-AperiodicTriggerStateList, activated by the CSI request field of the DCI, in the BWP for CSI reporting, one or more SSB indices for CSI measurement are configured only for the on-demand SSB (i.e., in the case of an always-on SSB in the BWP, there is no such SSB index for CSI measurement).

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

[0268] Action 6-2: For the SSB index(ies) of an on-demand SSB transmission activated as in action 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 are transmitted.

[0270] Alt.1-2: The terminal assumes that only the SSB index used for CSI measurement configured for on-demand SSB is transmitted. For example, SSB indices that are not used for CSI measurements are not triggered or transmitted.

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

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

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

[0274] Alternative 2-2: If there are candidate on-demand SSB opportunities that can be transmitted in or after the A-CSI report, the A-CSI before the A-CSI report, or Z slots of reference resources, the UE assumes that the SSB opportunity will or will not be transmitted. The above Z slots are determined by the CSI calculation time and UE capabilities. For example, after the A-CSI report, the UE assumes that the remaining on-demand SSB opportunities will not be transmitted.

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

[0276] Alt.3-1: A triggered on-demand SSB can only be used for CSI measurements for activated CSI reporting that configures the on-demand SSB as a CSI measurement resource.

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

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

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

[0280] 15 is a diagram illustrating an example of an on-demand SSB trigger according to a tenth embodiment of the present invention. FIG. 15 illustrates an example of Alternative 2-2 of Operation 6-3. As shown in FIG. 15, the UE assumes that after A-CSI reporting, no remaining on-demand SSB opportunities will be transmitted. The on-demand SSB is configured for A-CSI, and may also be triggered by DCI that triggers A-CSI.

[0281] Below, we will explain Operation 7: UE Capability. Note that the always-on SSB may be a legacy SSB.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0306] The default value may be:

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

[0308] For every UE action #A, the UE may perform a default action #B in case the UE is unable to perform the action #A.

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

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

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

[0312] According to the above-described embodiment, the UE can determine the band in which the on-demand SSB is transmitted, the UE can determine the BWP associated with the on-demand SSB, and the UE can receive the on-demand SSB triggered by the AP-CSI and perform AP-CSI reporting.

[0313] That is, a technique is provided for triggering 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.

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

[0315] <Base station 10> Fig. 16 is a diagram showing an example of the functional configuration of a base station. As shown in Fig. 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 Fig. 16 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention. The transmitting unit 110 and the receiving unit 120 may be called a communication unit.

[0316] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of a higher layer from the received signal. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, DL data, etc. to the terminal 20. The transmitter 110 also transmits the setting information, etc., described in the embodiments.

[0317] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads out the information from the storage device as needed. The control unit 140 performs, for example, overall control of the base station 10, including control related to signal transmission and reception. Note that the functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120. Furthermore, the transmitting unit 110 and the receiving unit 120 may be called a transmitter and a receiver, respectively.

[0318] <Terminal 20> Fig. 17 is a diagram showing an example of the functional configuration of a terminal. As shown in Fig. 17, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 17 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be called a communication unit.

[0319] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The transmitter 210 also transmits HARQ-ACK, and the receiver 220 receives the setting information and the like described in the embodiments.

[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 out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The control unit 240 performs overall control of the terminal 20, including control related to signal transmission and reception. Note that the functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220. The transmitting unit 210 and the receiving unit 220 may also be called a transmitter and a receiver, respectively.

[0321] The terminal or base station of this embodiment may be configured as a terminal or base station shown in each of the following items. Also, the following communication method may be implemented.

[0322] <Configuration of this embodiment> (Section 1) A receiver that receives settings related to on-demand SSB (SS / PBCH Block) measurement from a base station; A control unit that assumes that the on-demand SSB is triggered based on a trigger of an aperiodic CSI (Channel State Information) report included in the configuration related to the measurement of the on-demand SSB; The receiver receives the on-demand SSB from the base station; The terminal further comprises a transmitter configured to transmit a report of the aperiodic CSI based on the measurement of the on-demand SSB to the base station. (Section 2) The terminal of claim 1, wherein the control unit assumes that the on-demand SSB is triggered based on the triggering of the aperiodic CSI report by RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, or DCI (Downlink Control Information). (Section 3) The terminal according to claim 1, wherein the control unit assumes that the on-demand SSB is triggered based on the triggering of the aperiodic CSI report if the on-demand SSB is configured for the aperiodic CSI report in the configuration related to the measurement of the on-demand SSB. (Section 4) The terminal of claim 1, wherein the control unit assumes that an SSB index that is not transmitted in an always-on SSB is used for the on-demand SSB. (Section 5) 2. The terminal according to claim 1, wherein the control unit does not assume that an on-demand SSB will be transmitted after the aperiodic CSI report is transmitted to the base station. (Section 6) receiving configuration for on-demand SSB (SS / PBCH Block) measurements from a base station; A procedure for assuming that the on-demand SSB is triggered based on a trigger of an aperiodic CSI (Channel State Information) report included in the configuration 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 on-demand SSB measurement to the base station.

[0323] Any of the above configurations provides a technique for triggering 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. According to paragraphs 2 to 5, a UE can receive an on-demand SSB triggered by AP-CSI and perform AP-CSI reporting.

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

[0325] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0326] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 18 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above 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 description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

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

[0329] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0330] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 16 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 17 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

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

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

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

[0334] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, 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 may be configured using different buses between each device.

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

[0337] Fig. 19 shows an example configuration of a vehicle 2001. As shown in Fig. 19, the 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0338] The drive unit 2002 is configured, for example, by 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 operated by the user.

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

[0340] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0341] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001.

[0342] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0343] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are 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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, or the like.

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

[0346] The communication module 2013 receives various information (traffic information, traffic signal information, inter-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the external devices 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, axle 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

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

[0348] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0349] Each aspect / embodiment described in the present disclosure may be any of the following: LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 (x is, for example, an integer or decimal number)), 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 The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G).

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

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

[0352] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0353] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0354] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0355] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0356] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0358] Note that terms explained 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0359] As used in this disclosure, the terms "system" and "network" are used interchangeably.

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

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

[0362] In this disclosure, terms such as "base station (BS)," "radio 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. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0364] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. 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 some other suitable terminology.

[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, or the mobile body itself. 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 also include devices that do not necessarily move during communication operations. 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, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0368] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

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

[0370] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

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

[0372] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

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

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

[0375] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0376] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed 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] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

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

[0380] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[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. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0383] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0384] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0385] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0386] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0388] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0389] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

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

[0391] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0392] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set for the terminal 20 within one carrier.

[0393] At least one of the configured BWPs may be active, and the terminal 20 may not expect to transmit or receive a predetermined signal / channel outside the active BWP. Note that the terms "cell," "carrier," and the like in this disclosure may be read as "BWP."

[0394] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

[0396] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0397] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0398] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0399] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM 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 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. a receiving unit that receives settings related to on-demand SSB (SS / PBCH Block) measurement from a base station; A control unit that assumes that the on-demand SSB is triggered based on a trigger of an aperiodic CSI (Channel State Information) report included in the configuration related to the measurement of the on-demand SSB, The receiving unit receives the on-demand SSB from the base station, The terminal further comprises a transmitter configured to transmit the aperiodic CSI report based on the on-demand SSB measurement to the base station.

2. The terminal according to claim 1, wherein the control unit assumes that the on-demand SSB is triggered based on a trigger of the aperiodic CSI report by RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, or DCI (Downlink Control Information).

3. The terminal according to claim 1, wherein the control unit assumes that the on-demand SSB is triggered based on the triggering of the aperiodic CSI report if the on-demand SSB is configured for the aperiodic CSI report in the configuration related to the measurement of the on-demand SSB.

4. The terminal according to claim 1 , wherein the control unit assumes that an SSB index that is not transmitted in an always-on SSB is used for the on-demand SSB.

5. The terminal according to claim 1 , wherein the control unit does not assume that an on-demand SSB will be transmitted after the aperiodic CSI report is transmitted to the base station.

6. receiving configuration for on-demand SSB (SS / PBCH Block) measurements from a base station; A procedure for assuming that the on-demand SSB is triggered based on a trigger of an aperiodic CSI (Channel State Information) report included in the configuration related to the measurement of the on-demand SSB; receiving the on-demand SSB from the base station; and transmitting a report of the aperiodic CSI based on the measurement of the on-demand SSB to the base station.

Images