Terminal and communication method

Abstract

This terminal comprises: a control unit that executes beam failure detection using an SS / PBCH block (SSB) transmitted on demand; and a transmission unit that transmits a beam failure recovery request to a base station. The control unit determines, on the basis of an SSB index of the SSB transmitted on demand, whether or not to execute the beam failure detection using the SSB transmitted on demand.

Description

Terminal and communication method

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

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that satisfy the requirements of 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 (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).

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

[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 the energy saving state (ES), it was unclear how to configure beam failure detection and beam failure recovery using on-demand transmitted SSB (SS / PBCH Block).

[0006] The present invention has been made in consideration of the above points, and aims to perform beam failure detection using SSB (SS / PBCH Block) transmitted on demand in a base station that can transition to a power saving state.

[0007] According to the disclosed technology, a terminal is provided which has a control unit that performs beam failure detection using an SSB (SS / PBCH Block) transmitted on demand, and a transmission unit that transmits a beam failure recovery request to a base station, and the control unit determines whether to perform beam failure detection using the SSB transmitted on demand based on the SSB index of the SSB transmitted on demand.

[0008] According to the disclosed technology, a base station capable of transitioning to a power saving state can perform beam failure detection using SSBs (SS / PBCH Blocks) transmitted on demand.

[0009] FIG. 1 is a diagram for explaining a wireless communication system according to an embodiment of the present invention. FIG. 1 is a diagram for explaining CDRX in NR Release 15. FIG. 1 is a diagram for explaining WUS in NR Release 16. FIG. 1 is a diagram for explaining discontinuous reception of a base station according to Example 1 of an embodiment of the present invention. FIG. 2 is a diagram for explaining each parameter according to Example 1 of an embodiment of the present invention. FIG. 3 is a diagram for explaining discontinuous transmission of a base station according to Example 5 of an embodiment of the present invention. FIG. 4 is a diagram for explaining each parameter according to Example 5 of an embodiment of the present invention. FIG. 5 is a sequence diagram for explaining example (1) of OSI transmission according to Example 9 of an embodiment of the present invention. FIG. 6 is a sequence diagram for explaining example (2) of OSI transmission according to Example 9 of an embodiment of the present invention. FIG. 7 is a diagram for explaining example (1) of on-demand SSB according to Example 9 of an embodiment of the present invention. FIG. 8 is a diagram for explaining example (2) of on-demand SSB according to Example 9 of an embodiment of the present invention. FIG. 9 is a diagram for explaining example (3) of on-demand SSB according to Example 9 of an embodiment of the present invention. FIG. 10 is a diagram for explaining example (1) of QCL according to Example 10 of an embodiment of the present invention. FIG. 11 is a diagram for explaining example (2) of QCL according to Example 10 of an embodiment of the present invention. FIG. 10 is a diagram for explaining a QCL example (4) according to Example 10 of an embodiment of the present invention. FIG. 11 is a diagram for explaining a QCL example (5) according to Example 10 of an embodiment of the present invention. FIG. 12 is a diagram for explaining a QCL example (6) according to Example 10 of an embodiment of the present invention. FIG. 13 is a diagram for explaining a BFD example (1) according to Example 11 of an embodiment of the present invention. FIG. 14 is a diagram for explaining a BFD example (2) according to Example 11 of an embodiment of the present invention. FIG. 15 is a diagram for explaining a CSI report example (1) according to Example 12 of an embodiment of the present invention. FIG. 16 is a diagram for explaining a CSI report example (2) according to Example 12 of an embodiment of the present invention. FIG. 17 is a diagram for explaining a CSI report example (3) according to Example 12 of an embodiment of the present invention. FIG. 18 is a diagram for explaining a CSI report example (4) according to Example 12 of an embodiment of the present invention.FIG. 10 is a diagram for explaining an example (5) of a CSI report according to Example 12 of an embodiment of the present invention. FIG. 11 is a diagram for explaining an example (6) of a CSI report according to Example 12 of an embodiment of the present invention. FIG. 12 is a diagram for explaining an example (7) of a CSI report according to Example 12 of an embodiment of the present invention. FIG. 13 is a diagram for explaining an example (8) of a CSI report according to Example 12 of an embodiment of the present invention. FIG. 14 is a diagram for explaining an example (9) of a CSI report according to Example 12 of an embodiment of the present invention. FIG. 15 is a diagram for explaining an example (10) of a CSI report according to Example 12 of an embodiment of the present 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 the operation of the wireless communication system according to the embodiment of the present invention, existing technology may be used as appropriate. The existing technology is, for example, the existing NR or LTE, but is not limited to the existing NR or LTE. In addition, 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] In addition, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. In addition, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily stated as "NR-".

[0013] Furthermore, in the embodiment of the present invention, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (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 transmission time interval (TTI) in the time domain may be a slot, or 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 NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may also be referred to as 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 the DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). 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 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, the status of discussions on base station power saving in NR Release 18 will be described. Techniques for base stations and terminals to improve network energy saving from both the base station's transmission and reception perspectives are being considered. For example, methods are being considered for a base station to more efficiently realize 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 and potential assistance information from terminals.

[0020] Next, discontinuous reception (DRX) or connected mode DRX (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, the terminal monitors the PDCCH during the DRX on period.

[0022] 3 is a diagram for explaining WUS in NR Release 16. In NR Release 16, a PDCCH-based wake-up signal (WUS: Wake Up Signal) 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-duration 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-duration 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 indication information indicating "active" or "inactive."

[0026] (Problems with the past) Next, we will explain the problems with the past. 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 the past in that there is no standardized method for reducing the power consumption of base stations.

[0027] (Outline 1 of the Present Embodiment) In the present embodiment, an example of achieving a reduction in power consumption of a base station from the viewpoint of the time domain will be described. Specific examples will be described below, including Examples 1 to 4.

[0028] (First embodiment) In this embodiment, the operation of a base station when it receives intermittently and the definition 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] FIG. 5 is a diagram illustrating each parameter according to Example 1 of the embodiment of the present invention. The base station CDRX may be defined by a number of parameters listed below. The units of the parameters may be symbols, slots, subframes, milliseconds, or seconds, etc. The units may be different or the same for each parameter. drx-onDurationTimer: Period at the start of the DRX cycle drx-SlotOffset: Delay before starting drx-onDurationTimer drx-InactivityTimer: Period during which the terminal 20 performs uplink transmission after an uplink reception opportunity drx-LongCycleStartOffset: 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: Period during which the base station 10 follows the short DRX cycle; drx-RetransmissionTimerUL: Maximum period until a grant for an uplink retransmission is received; drx-HARQ-RTT-TimerUL: Minimum period until a grant for an uplink retransmission 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 drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL is executed.

[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 operate 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 Example 3.

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

[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 DBR status.

[0037] Note that when discontinuous base station reception is enabled, 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, i.e., 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 operate 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 Example 3.

[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 DBR status.

[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] (Embodiment 2) In this embodiment, an example of a method for triggering discontinuous reception at a base station is shown.

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

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

[0051] <Option 3> When the base station 10 receives UCI included in the PUCCH or PUSCH from the terminal 20, the base station 10 may enable / disable the base station discontinuous reception based on an instruction to enable / disable the base station discontinuous reception 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. Also, the UCI may be a UCI of the same 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 execute an instruction (i.e., activation / deactivation) of discontinuous reception at the base station, thereby enabling / disabling 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 Example 3.

[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 it 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 Example 3.

[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 above-described options that trigger the enablement / disablement of the discontinuous reception at the base station is executed.

[0060] <Option 2> The base station 10 may receive an instruction on the timing of enabling / disabling the discontinuous reception at the base station 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 discontinuous reception at the base station at a specified time when one of the above-mentioned options that triggers the enabling / disabling of the discontinuous reception at the base station 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 configure 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 discontinuous base station reception described above is executed, the timer is executed, and when the timer expires, the base station 10 may enable / disable the discontinuous base station reception.

[0063] The advantages of the timer are as follows: Even if the base station discontinuous reception is instructed to be enabled, there are 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, the base station discontinuous reception can be enabled after a certain time, thereby reducing the power consumption of the base station 10.

[0064] Furthermore, even if the discontinuous reception from the base station is instructed to be disabled, actual uplink transmission from the terminal 20 may continue 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 from 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] Third Embodiment In this embodiment, an example will be described in which a terminal receives an instruction regarding discontinuous reception at a base station by 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 indicating the status of discontinuous reception at the base station from the base station 10 to the terminal 20. For timely indication, 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 valid state indicated by "1" and an invalid state indicated by "0". 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 a 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 a GC-RNTI, the HPN and RV fields are all set to "0", and the MCS field is all set to "1", the terminal 20 may identify that the status of base station discontinuous reception is disabled.

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

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

[0076] <Option 1-1> The base station 10 may indicate the status of 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 the 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 technology 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 base station discontinuous reception using the conventional DCI format 2_6 or another group-common 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 an 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 GC-RNTI) described above instead of the PS-RNTI.

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

[0084] Fourth Embodiment 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] When the terminal 20 has a terminal capability that supports identifying the status of the discontinuous reception from the base station, the terminal 20 may identify whether the discontinuous reception from the base station function is enabled or disabled. For example, the terminal 20 may perform the operation of Option 1 described in the first embodiment. Furthermore, when the terminal 20 does not have a terminal capability that supports identifying the status of the discontinuous reception from the base station, the terminal 20 may perform the operation of Option 2 described in the first embodiment.

[0090] In addition, 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. In addition, 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, it may be necessary to report both the base station capability information and the terminal capability information indicating that the base station discontinuous reception is supported.

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

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

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

[0096] (Outline 2 of the present embodiment) Furthermore, 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 in the base station 10. To reduce the power consumption in the base station 10, 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 of 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 based on 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> Fig. 6 is a diagram for explaining discontinuous transmission of a base station according to Example 5 of an 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: A period from the beginning of the DTX cycle. 2) dtx-SlotOffset: A delay period before starting 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: dtx-StartOffset that defines the long DTX cycle (i.e., dtx-LongCycle) and the start of the long and short DTX cycles. 5) dtx-ShortCycle: A short DTX cycle. This 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] 7 is a diagram for explaining each parameter according to Example 5 of an embodiment of the present invention. As shown in FIG. 7, from the beginning of dtx-LongCycle, the active time is dtx-onDurationTimer after dtx-SlotOffset. If DL reception occurs during drx-LonCycle, 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 assume to receive DL channels or DL ​​signals as notified 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 UL signal may be any of PRACH, PUCCH, PUSCH, CG-PUSCH, SRS, PT-RS, and DM-RS.

[0109] Sixth Embodiment In a 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 using common parameters. When the common parameters (e.g., CellDTXDRX-Config) are configured, cell DTX and DRX may be enabled. The terminal 20 may appropriately perform the operation of Example 5.

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

[0112] 1) Parameters common to DTX and DRX. Some parameters may be common to DTX and DRX. For example, 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 using 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 Example 5. The parameters for DRX may include the parameters described in Example 1.

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

[0117] Example 7 In Example 7, 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> Cell DTX and cell DRX may be enabled or disabled by RRC signaling. When an RRC parameter is configured, 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 Example 6.

[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> Cell DTX and cell DRX may be enabled or disabled by DCI. The terminal 20 may be dynamically notified by DCI that cell DTX and cell DRX have been enabled or disabled. The notification by DCI may be performed as shown in 1) to 4) below.

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

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

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

[0124] 4) The DCI fields may be a set of existing fields and / or a new set of 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 a 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, 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 DTX and cell DRX.

[0126] Alt. 2) When scrambling 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> Cell DTX or cell DRX may be enabled or disabled by RRC signaling. When an RRC parameter is configured, 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 Example 6.

[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 a DCI that cell DTX or cell DRX has been enabled or disabled. The notification by the DCI may be performed as shown in 1) to 4) below.

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

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

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

[0135] 4) The DCI fields may be a set of existing fields and / or a new set of 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 a CS-RNTI, and, for example, when the HPN is set to all "0", the RV is set to all "00", and the PRI is set to all "1", the terminal 20 may dynamically enable cell DTX. Also, for example, when the HPN is set to all "0", the RV is set to all "00", the MCS is set to all "1", the FDRA is set to all "1", and the PRI is set to all "1", the terminal 20 may dynamically disable cell DTX. Also, for example, when the HPN is set to all "0", the RV is set to all "00", and the TDRA is set to all "1", the terminal 20 may dynamically enable cell DRX. Also, for example, when the HPN is set to all "0", the RV is set to all "00", the MCS is set to all "1", the FDRA is set to all "1", and the TDRA is set to all "1", the terminal 20 may dynamically disable cell DRX.

[0137] In addition, 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 fields as those used above, such as PRI and TDRA (e.g., 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 with a new RNTI, for example, when the HPN is set to all "0", the RV is set to all "00", and the PRI is set to all "1", the terminal 20 may dynamically enable cell DTX. For example, when the HPN is set to all "0", the RV is set to all "00", the MCS is set to all "1", the FDRA is set to all "1", and the PRI is set to all "1", the terminal 20 may dynamically disable cell DTX. For example, when the HPN is set to all "0" and the RV is set to all "00", the terminal 20 may dynamically enable cell DRX. For example, when the HPN is set to all "0", the RV is set to all "00", the MCS is set to all "1", and the FDRA is set to all "1", the terminal 20 may dynamically disable cell DRX.

[0140] Note that, for example, although PRI is used as described above, an additional field may not be used to indicate whether cell DTX or cell DRX is targeted. When different DCI formats are used, the DCI format may signal whether cell DTX or cell DRX is targeted. 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 the cell DTX and the 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 the cell DTX. Also, for example, if the cell DTX identifier is set to "0", the terminal 20 may dynamically disable the cell DTX. For example, if the cell DRX identifier is set to "1", the terminal 20 may dynamically enable the cell DRX. Also, for example, if the cell DRX identifier is set to "0", the terminal 20 may dynamically disable the 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 enabling or disabling of cell DTX or cell DRX notified by MAC-CE or DCI described above 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 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, a slot, a subframe, a millisecond, a second, or the like. When the activation or deactivation of the cell DTX or cell DRX is notified by MAC-CE or DCI, the terminal 20 may activate or deactivate the cell DTX or cell DRX at the notified time in advance.

[0148] Example 8 In Example 8, a related operation between 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, it may operate as shown in Option 1 to Option 5 below.

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

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

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

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

[0154] <Option 5> Cell DTX and UE DRX may be configured in the terminal 20 regardless of whether the time positions of the cell DTX and the UE DRX are aligned or not. Furthermore, when the cell DTX is configured in addition to the UE DRX, the parameters of the cell DTX may take priority. The terminal 20 may ignore the parameters of the UE DRX. The terminal 20 may operate as in Example 5. Furthermore, when the cell DTX is configured in addition to the UE DRX, both parameters may be applied. The terminal 20 may wake up during the active times of both the cell DTX and the 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, the cell DTX and UE DRX may be defined as being aligned in time.

[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 the cell DTX and the UE DRX, the cell DTX and the UE DRX may be further defined as being 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 the cell DTX and the UE DRX, the cell DTX and the UE DRX may be defined as being time-aligned. Furthermore, other parameters (e.g., dtx-InactivityTimer, drx-InactivityTimer, etc.) may be additionally considered to determine whether this definition is met.

[0159] <Option 2> In addition to the long cycle, if the short cycle is the same for the cell DTX and the UE DRX, it may be defined that the cell DTX and the 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, when the short cycle is the same for cell DTX and UE DRX, the time positions of cell DTX and UE DRX may be defined as being aligned regardless of the active time within the short cycle. In other words, when the short cycle of cell DTX (e.g., dtx-ShortCycle) and the short cycle of UE DRX (e.g., drx-ShortCycle) are the same, the time positions may be defined as being aligned.

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

[0162] (Outline 3 of the present 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 for idle UEs and on-demand SSB and other DL signals transmission for connected UEs in the SCell are being considered. Note that SSB may be replaced with SS / PBCH block. Note that " / " may be replaced with "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) Triggering based on a backhaul signal indicating cell ON or OFF; 3) Triggering based on SCell activation or deactivation signaling.

[0166] Also, SSB and / or SIB1-less operation may be performed in multi-carrier scenarios, e.g., no SSB and / or no 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-assigned 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 showing an example (1) 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 immediately before the on-demand SSB is actually transmitted by MAC-CE or the like.

[0171] As shown in Fig. 10, for the operation related to on-demand SSB, Scenario #2 considers the operation when the SCell is set to an inactive state. Scenario #2A considers the operation when an SCell activation command is received. Scenario #3A considers the operation from 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.

[0172] Information related to the on-demand SSB may be notified at the timing when the SCell activation command of Scenario #2A is received. The on-demand SSB transmitted during SCell activation may be used for SCell activation.

[0173] 11 is a diagram showing an example (2) of on-demand SSB according to Example 9 of the embodiment of the present invention. As shown in FIG. 11, always-on SSB may not be transmitted, and only on-demand SSB may be transmitted.

[0174] 12 is a diagram showing an example (3) of on-demand SSB according to Example 9 of the embodiment of the present invention. As shown in FIG. 12, an always-on SSB may be transmitted, and an on-demand SSB may also be transmitted. In the example of FIG. 12, the always-on SSB corresponds to SSB index {a, b, c, d}, and the on-demand SSB corresponds to SSB index {a, b, c, d}.

[0175] 13 is a diagram showing an example (4) of on-demand SSB according to Example 9 of the embodiment of the present invention. As shown in FIG. 13, an always-on SSB may be transmitted, and an on-demand SSB may also be transmitted. In the example of FIG. 12, the always-on SSB corresponds to SSB index {a, b}, and the on-demand SSB corresponds to SSB index {c, d}.

[0176] (Example 10) As shown in Table 1, four types of QCLs have been defined (see Non-Patent Document 4).

[0177]

[0178] The QCL type is used to communicate large-scale property and beam information.

[0179] 14 is a diagram illustrating an example (1) of a QCL according to a tenth embodiment of the present invention. As shown in FIG. 14, a TCI (Transmission Configuration Indication) indicates that a CSI-RS, a PDSCH-DMRS, or a PDCCH-DMRS refers to large-scale characteristics of one or two reference signals (SSB index or NZP-CSI-RS-Resource). For example, a target and a source of the QCL may be set by the TCI notified from the base station to the terminal.

[0180] Table 2 shows possible QCL target and source combinations.

[0181]

[0182] As shown in Table 2, SSB is normally used for QCL type D for CSI-RS TRS (Tracking RS) / BM (Beam Management) / CSI and PDSCH / PDCCH-DMRS. SSB is also used for QCL type C for CSI-RS TRS / BM. SSB is also used for QCL type A for PDSCH / PDCCH-DMRS.

[0183] Here, if on-demand or adaptive SSB can be configured as a QCL source, restrictions may apply when SSB is configured as a QCL source. UE behavior when on-demand SSB can be configured as a QCL source may be determined.

[0184] Operation 1) Restriction on TCI setting considering on-demand SSB

[0185] Whether or not the on-demand SSB can be configured as the QCL source in the TCI state may be determined based on one or more or a combination of the following. Note that in this embodiment, the configuration may be performed by the base station via signaling to the terminal. The terminal may receive information related to the configuration from the base station and perform the configuration.

[0186] Alt. 1-1: An SSB index configured for on-demand SSB may not be configured as a QCL source (applicable at least to the case of FIG. 11). Alt. 1-2: An SSB index not configured for always-on SSB may not be configured as a QCL source (applicable at least to the case of FIG. 11). For example, among SSB indexes configured for on-demand SSB, an SSB index not configured as always-on SSB may not be configured as a QCL source. Alt. 1-3: An SSB index not configured for on-demand SSB may be configured as a QCL source (applicable at least to the cases of FIGS. 12 and 13). Alt. 1-4: An SSB index configured for always-on SSB may be configured as a QCL source (applicable at least to FIGS. 12 and 13). For example, among SSB indexes configured for on-demand SSB, an SSB index configured as always-on SSB may be configured as a QCL source. Alt. 1-5: An SSB index configured as always-on SSB may be configured as a QCL source without being configured as on-demand SSB (applicable at least to the case of FIG. 13). Alt. 1-6: An SSB index configured as either always-on SSB or on-demand SSB may be configured as a QCL source.

[0187] When on-demand SSB can be configured as a QCL source, one or more or a combination of the following may be considered:

[0188] Alt. 2-1: An SSB index configured as an on-demand SSB may be configured only as QCL-Type 2 with QCL-Type D. Alt. 2-2: An SSB index configured as an on-demand SSB may be configured only as QCL-Type 1 with QCL-Type A and / or QCL-Type C. Alt. 2-3: An SSB index configured as an on-demand SSB may be configured only as a QCL source for some or all of the CSI-RS TRS, CSI-RS BM, CSI-RS CSI, PDCCH-DMRS, and PDSCH-DMRS.

[0189] Operation 2) QCL UE Behavior and Assumptions

[0190] Action 2-1) For an SSB index included in an on-demand SSB and configured as a QCL source for one RS, if condition X is met, the UE may assume QCL relationship Y.

[0191] Condition X can be one, more, or a combination of the following: Alt. 1-1: No SSB is triggered or transmitted. Alt. 1-2: The time interval from the last transmitted SSB to the RS targeted by the QCL is greater than T1. The most recently transmitted SSB may be any of the following SSBs: a triggered on-demand SSB, an on-demand SSB, or an always-on SSB. Alt. 1-3: The number of SSB samples for which the time interval from the SSB to the RS targeted by the QCL is less than T2 is less than N. The number of SSB samples may be counted only for SSBs within on-demand SSBs, or for both on-demand SSBs and always-on SSBs.

[0192] T1, T2 and N may be configured by system information, RRC signaling, MAC-CE and / or DCI.

[0193] T1 and T2 may be the number of symbols, slots, subframes, radio frames, and / or SSB periods or durations, and N is an integer, where N=0, 1, 2, . . .

[0194] 15 is a diagram for explaining an example (2) of QCL according to Example 10 of the embodiment of the present invention. FIG. 15 shows an example of Alt. 1-2.

[0195] 16 is a diagram for explaining an example (3) of QCL according to Example 10 of the embodiment of the present invention. FIG. 16 shows an example of Alt. 1-3.

[0196] The QCL relationship Y may be one, more or a combination of the following:

[0197] Alt. 2-1: The UE may assume that the SSB and the target RS are not QCL with any QCL type, i.e., not QCL at all.

[0198] Alt. 2-2: If configured, the UE may assume that the SSB and target RS are QCLs only for some or all of Type A, Type B, Type C, and Type D. Figure 17 is a diagram for explaining a QCL example (4) according to Example 10 of the present invention. For example, if only the SSB and RS are QCLs for QCL Type A, the UE may assume that the SSB and RS are QCLs, as shown in Figure 17. The UE may assume that QCL-Type 1 (QCL Type A) is still valid, or that the non-QCLed QCL-Type 2 (QCL Type D) is invalid.

[0199] Alt. 2-3: When an SSB and a target RS are configured, the UE may assume that the QCL is valid only for some or all of the Doppler spread, Doppler shift, mean gain, mean delay, delay spread, and spatial reception parameters. Figure 18 is a diagram for explaining a QCL example (5) according to Example 10 of the present invention. For example, when the SSB and RS are QCL only for the mean delay and Doppler shift, in Figure 18, the UE may assume that the SSB and RS are partially valid for qcl-Type 1 (QCL Type A) for the mean delay and Doppler shift, and that qcl-Type 2 (QCL Type D) is invalid.

[0200] Alt. 2-4: The UE may assume that the other SSB and the target RS are QCL for some or all of Type A, Type B, Type C, Doppler spread, Doppler shift, average delay, and delay spread. The other SSB may be assumed not to be QCL with the RS for Type D, spatial reception parameters, and average gain. The above other SSB may be an SSB within the always-on SSBs, an SSB with the lowest index within the always-on SSBs, or the most recently transmitted SSB.

[0201] 19 is a diagram illustrating an example (6) of a QCL according to Example 10 of the embodiment of the present invention. As shown in Fig. 19, in the past, when it was assumed that the target RS and SSB#d were in QCL, if SSB#d was not triggered, it was also possible to assume that the target RS and SSB#a were in QCL.

[0202] Operation 2-2) Other behaviors of the UE

[0203] If there is no always-on SSB and / or only an on-demand SSB for an SSB index included in an on-demand SSB and configured as a QCL source for one target RS (e.g., the case of Figure 11), the UE may assume that the SSB and the target RS are not QCL or that the QCL relationship is invalid.

[0204] For an SSB index included in an on-demand SSB and configured as a QCL source for one target RS, if both an always-on SSB and an on-demand SSB exist for the SSB index (e.g., the case of Figure 12), the UE may measure or refer to only the on-demand SSB, only the always-on SSB, or either the on-demand SSB or the always-on SSB for the QCL relationship.

[0205] The UE may assume that the always-on SSB and the on-demand SSB with the same SSB index are QCL.

[0206] The above operations 1) and 2) may be effective during SSB adaptation. For example, in the above operations 1) and 2), on-demand SSB may be replaced with adapted SSB.

[0207] Example 11 A Beam Failure Recovery (BFR) mechanism is used to recover from a beam failure.

[0208] For beam failure detection, SSB-based beam failure detection can be based on CD (Cell Defining)-SSB and NCD (Non Cell Defining)-SSB (see Non-Patent Document 1). The same procedure is applied to PCell and SCell.

[0209] For beam failure recovery, after beam failure is detected on the PCell, the UE triggers BFR by initiating a random access procedure on the PCell, and after beam failure is detected on the SCell, the UE triggers BFR by transmitting a BFR MAC-CE for this SCell.

[0210] The reference signals used for beam failure detection are PDCCH-DMRS and periodic CSI-RS and / or SSB, which are QCL. BLER (Block Error Rate) is referenced as a condition for beam failure. The default value of RLM (Radio Link Monitoring) is used as the threshold. Periodic CSI-RS and / or SSB are used as new candidate beams. L1-RSRP is used to determine new candidate beams. The threshold for SSB is set by RRC signaling, and the threshold for CSI-RS is derived from the threshold for SSB.

[0211] The condition for requesting beam failure recovery is to continuously detect beam failure and identify a new candidate beam. A non-contention-based PRACH is used to transmit the beam failure recovery request. Each PRACH resource is associated with a new candidate beam. The gNB's response is transmitted via the PDCCH of the C-RNTI. The response is transmitted using the new candidate beam determined by the UE. The BFR Control Resource Set (CORESET) is monitored for the gNB's response for beam recovery. The search space is mapped one-to-one to the BFR CORESET.

[0212] Here, when detecting beam failure, if an on-demand SSB such as that shown in Figure 11 or Figure 13 is configured for beam failure detection and the on-demand SSB is not triggered, it is necessary to determine how the UE will detect beam failure.

[0213] When beam failure recovery occurs, an on-demand SSB such as that shown in Figure 11 or Figure 13 is configured as a candidate RS for new beam determination, and if the on-demand SSB is not triggered, it is necessary to determine how the UE will identify a new RS.

[0214] Therefore, the following operations may be performed: Operation 1) Enhancement of beam failure detection (BFD) taking on-demand SSB into consideration Operation 1-1) Restriction on configuration of on-demand SSB as RS for BFD Operation 1-2) Behavior related to beam failure detection when on-demand SSB is configured as RS for BFD Operation 2) Enhancement of beam failure recovery (BFR) taking on-demand SSB into consideration Operation 2-1) Restriction on configuration of on-demand SSB as RS for BFR Operation 2-2) Enhancement of behavior related to new candidate beam identification for BFR

[0215] Operation 1) Enhanced beam failure detection (BFD) to account for on-demand SSB

[0216] Operation 1-1) Restrictions on setting on-demand SSB as RS for BFD

[0217] Regarding whether an on-demand SSB can be configured as an RS for beam failure detection, one or more of the following may be considered:

[0218] Alt. 1-1: An SSB index set as an on-demand SSB may not be set or considered as an RS for beam failure detection. For example, an SSB transmitted on-demand as shown in FIG. 11 or FIG. 13 may not be set as an RS for beam failure detection.

[0219] Alt. 1-2: An SSB index that is not configured as an always-on SSB may not be configured as an RS for beam obstruction detection or may not be considered. For example, an SSB index that is configured as an on-demand SSB but is not configured as an always-on SSB may not be configured as an RS for beam obstruction detection.

[0220] Alt. 1-3: SSB indices that are not configured as on-demand SSBs may be configured or considered as RSs for beam failure detection.

[0221] Alt. 1-4: An SSB index configured as an always-on SSB may be configured or considered as an RS for beam obstruction detection. For example, an SSB index configured as an on-demand SSB and also configured as an always-on SSB may be configured as an RS for beam obstruction detection.

[0222] Alt. 1-5: SSB indexes configured as always-on SSB and not configured as on-demand SSB may be configured as RS for beam failure detection.

[0223] Alt. 1-6: SSB indexes configured as either always-on SSB or on-demand SSB may be configured or considered as RS for beam failure detection.

[0224] For example, the UE may determine that the SS / PBCH blocks configured by higher layer parameters as on-demand SSBs are q０ , q ０，０ or q ０，１ (see Non-Patent Document 5).

[0225] Operation 1-2) Behavior related to beam obstruction detection when on-demand SSB is configured as RS for BFD

[0226] In legacy, if beam failure is detected on all RSs (radio link quality on each RS is worse than a threshold), the UE provides notifications to higher layers with a periodicity determined by max{shortest period of RS for BFD, 2 ms}.

[0227] Action 1-2-1) In case of on-demand SSB for BFD and SSB index configured as RS, the UE may assume the following:

[0228] Alt. 1-1: On-demand SSB may always be transmitted without any trigger. Considering UE measurement requirements, on-demand SSB may always be transmitted.

[0229] Alt. 1-2: If on-demand SSB is configured for BFD, it may be considered a trigger for on-demand SSB. Based on this configuration, on-demand SSB transmission may be enabled.

[0230] Alt. 1-3: For on-demand SSB, additional signaling is required, triggered by RRC signaling, MAC-CE, and DCI. For example, RRC signaling is appropriate for configuring on-demand SSB as an RS for BFD.

[0231] Operation 1-2-2) When the SSB index set as an on-demand SSB is set for BFD, the following operation may be performed.

[0232] Alt. 2-1: The UE may not use SSB for beam failure detection. For example, if beam failure on all RSs other than SSB is detected, the UE may notify higher layers.

[0233] Alt. 2-2: The UE may not use on-demand SSB opportunities for beam failure detection. For example, in the case of on-demand SSB shown in FIG. 12, only always-on SSB opportunities may be used for beam failure detection. For example, in the case of on-demand SSB shown in FIG. 11, no SSB opportunities are used for beam failure detection. In this case, the UE may or may not report a beam failure notification to higher layers.

[0234] Alt. 2-3: The UE may use SSB for beam obstruction detection either on always-on SSB opportunities or on triggered or transmitted on-demand SSB opportunities.

[0235] Alt. 2-3-1: The UE may not use SSB for beam failure detection if on-demand SSB is not triggered or transmitted.

[0236] Alt. 2-3-2: The UE may use always-on SSB for beam obstruction detection if on-demand SSB is not triggered or transmitted.

[0237] Alt. 2-3-3: If an on-demand SSB is not triggered or transmitted, no notification of beam failure may be provided to higher layers.

[0238] Alt. 2-4: The UE may not provide notification of beam failure to higher layers.

[0239] For example, in non-DRX mode, the UE's physical layer may notify higher layers when the radio link quality for all corresponding resource configurations other than the SS / PBCH block configured by higher layers as on-demand SSB transmission is worse than a threshold (see non-patent document 5).

[0240] For example, in non-DRX mode, the UE's physical layer may notify higher layers when the radio link quality for all corresponding resource configurations other than SS / PBCH blocks configured as on-demand SSB transmission by higher layers and not triggered is worse than a threshold (see non-patent document 5).

[0241] Action 1-2-3) The periodicity (P) for providing BFD notification to higher layers may be determined based on the following formula:

[0242] Alt. 3-1: max {shortest period of RS configured for BFD, shortest period of RS configured for BFD including on-demand SSB, 2 ms}.

[0243] Alt. 3-2: max {shortest period of RS configured for BFD, shortest period of RS configured for BFD including triggered and transmitted on-demand SSB, 2 ms}. Fig. 20 is a diagram for explaining a BFD example (1) according to an eleventh embodiment of the present invention. Fig. 21 is a diagram for explaining a BFD example (2) according to an eleventh embodiment of the present invention. For example, as shown in Fig. 20, for SSB index {a}, if on-demand SSB is triggered, P = max {t, 2 ms}, and if on-demand SSB is not triggered, P = max {2t, 2 ms}. For example, as shown in Fig. 21, for SSB index {a}, P = max {t, 2 ms}.

[0244] Alt. 3-3: max{shortest period of RS configured for BFD, shortest period of RS configured for BFD not including on-demand SSB, 2 ms}. For example, as shown in Figure 20, if on-demand SSB is triggered, P may be max{2t, 2 ms} for SSB index {a}.

[0245] Alt. 3-4: max {minimum period of RS configured for BFD, minimum period of RS configured for BFD that does not include on-demand SSB configured for BFD and not transmitted or triggered, 2 ms}.

[0246] Operation 2) Enhanced Beam Failure Recovery (BFR) considering on-demand SSB

[0247] Operation 2-1) Restrictions on Configuring On-Demand SSB as an RS for BFR

[0248] Whether or not an on-demand SSB can be configured as an RS for beam failure recovery may be determined based on one or more of the following:

[0249] Alt. 1-1: An SSB index configured as on-demand SSB may not be configured as an RS for BFR. Alt. 1-2: An SSB index not configured as always-on SSB may not be configured as an RS for BFR. For example, an SSB index configured as on-demand SSB and not configured as always-on SSB may not be configured as an RS for BFR. Alt. 1-3: An SSB index not configured as on-demand SSB may be configured as an RS for BFR. Alt. 1-4: An SSB index configured as always-on SSB may be configured as an RS for BFR. For example, an SSB index configured as on-demand SSB and also configured as always-on SSB may be configured as an RS for BFR. Alt. 1-5: An SSB index that is configured as an always-on SSB and not configured as an on-demand SSB may be set as an RS for BFR. Alt. 1-6: An SSB index that is configured as an always-on SSB or on-demand SSB may be set as an RS for BFR.

[0250] For example, the UE may determine that the SS / PBCH blocks configured as on-demand SSB transmissions by higher layer parameters are １ , q １，０ or q １，１ (see Non-Patent Document 5).

[0251] Operation 2-2) Strengthening of operations related to determining new candidate beams

[0252] In legacy, for an SCell, if beam failure is detected, the UE notifies higher layers whether there is at least one RS with a corresponding L1-RSRP measurement value that is above the threshold and provides the RS index.

[0253] Action 2-2-1) For an SSB index configured as an on-demand SSB and configured as a candidate beam for BFR, the UE may operate as follows:

[0254] Alt. 2-1: The SSB may not be used, measured, or reported as a candidate beam or RS for BFR.

[0255] Alt. 2-2: When the SSB is triggered or transmitted, the SSB may be used, measured, or reported as a candidate beam or RS for BFR.

[0256] Alt. 2-3: If there is at least one candidate RS or beam other than the on-demand SSB with a corresponding metric equal to or greater than the threshold, the UE may notify higher layers of the beam failure and one or more of the RS or beam indexes other than the on-demand SSB with a corresponding metric equal to or greater than the BFR threshold.

[0257] Alt. 2-4: In case of only on-demand SSBs (without other RSs) with corresponding metrics above the threshold, the UE may notify higher layers of beam failure and may further perform the following actions: Alt. 2-4-1: The UE may notify higher layers of one or more on-demand SSBs for BFR. Alt. 2-4-1: The UE may notify higher layers of no candidate beams or RSs for BFR.

[0258] For example, the UE may notify the upper layer of at least one CSI-RS configuration index or whether there are any SS / PBCH blocks other than the SS / PBCH blocks configured as on-demand SSB transmission by the upper layer (see non-patent document 5).

[0259] Action 2-2-2) In case of on-demand SSB for BFD and SSB index configured as RS, the UE may operate as follows.

[0260] Alt. 3-1: On-demand SSB may be transmitted without any trigger. Considering UE measurement requirements, on-demand SSB may be transmitted at any time.

[0261] Alt. 3-2: A beam failure recovery request (BFRQ) in which an on-demand SSB is included as a candidate beam or RS for BFR may be considered a trigger for the on-demand SSB. For example, when such a BFRQ is transmitted, the UE may assume that the on-demand SSB is triggered, transmitted, or always transmitted.

[0262] Alt. 3-3: An UL grant in the same HARQ process as a BFRQ transmission in which an on-demand SSB is included as a candidate beam or RS for BFR may be considered a trigger for the on-demand SSB or a response to the trigger. If there are no candidate beams or RSs for BFR indicated in the BFRQ, the UE may assume that all on-demand SSBs or all on-demand SSBs configured as RSs for BFR are triggered or transmitted. When the UE receives an UL grant, it may assume that the triggered on-demand SSB is always transmitted or transmitted within a window.

[0263] Actions 1) and 2) may work for adapted or adapted SSB. For example, "on-demand SSB" in actions 1) and 2) may be replaced with "adapted or adapted SSB."

[0264] (Example 12) Fig. 22 is a diagram for explaining an example (1) of a CSI report according to Example 12 of an embodiment of the present invention. The UE is configured with information as shown in Fig. 22 for measurement and reporting. The report configuration (CSI-ReportConfig) notifies the UE how to perform reporting. The resource configuration (CSI-ResourceConfig) notifies the CSI-RS / SSB resource set used for CSI / L1-RSRP measurement.

[0265] 23 is a diagram illustrating an example (2) of a CSI report according to Example 12 of the present invention. As shown in Fig. 23, the RRC sets multiple semiPersistentOnPUCCHs in a reporting configuration (CSI-ReportConfig), and the MAC-CE enables or disables or activates or deactivates one or multiple reporting configurations (see Non-Patent Documents 3 and 4).

[0266] MAC-CE Field S ０ corresponds to a reporting configuration including PUCCH resources for reporting SP-CSI in the notified BWP, and the reporting configuration has the smallest CSI-ReportConfigId in the list whose type is set to semiPersistentOnPUCCH.

[0267] MAC-CE Field S ｉ When the value of the field S of the MAC-CE is set to 1, the corresponding SP-CSI reporting setting is enabled or activated. ｉ When set to a value of 0, the corresponding SP-CSI reporting setting is disabled or deactivated.

[0268] 24 is a diagram illustrating an example (3) of a CSI report according to Example 12 of the present invention. As shown in FIG. 24, the RRC configures up to 64 CSI-SemiPersistentOnPUSCH-TriggerStates, and the DCI triggers one CSI-SemiPersistentOnPUSCH-TriggerState. One CSI-SemiPersistentOnPUSCH-TriggerState corresponds to one CSI reporting configuration.

[0269] Fig. 25 is a diagram illustrating an example (4) of a CSI report according to a twelfth embodiment of the present invention. As shown in Fig. 25, the RRC sets a maximum of 128 CSI-AperiodicTriggerState, the MAC-CE downselects the range to a maximum of 63, and the DCI triggers one. One CSI-AperiodicTriggerState corresponds to a maximum of 16 CSI-AssociatedReportConfigInfo, i.e., a maximum of 16 CSIs. One CSI-AssociatedReportConfigInfo corresponds to one CSI reporting configuration.

[0270] The fields T0 / T1 / ... of the MAC-CE correspond to the first / second / ... CSI-AperiodicTriggerState of the CSI-AperiodicTriggerStateList. If Ti is 1, it is mapped to a DCI codepoint; otherwise, it is not mapped to a DCI codepoint. A maximum of 63 CSI-AperiodicTriggerStates are mapped to DCI codepoints.

[0271] L1 measurements based on on-demand SSB, periodic, semi-persistent, and / or aperiodic L1 measurement reporting based on the existing CSI framework may be supported. Since on-demand SSB is transmitted only when triggered, periodic, semi-persistent, and / or aperiodic CSI reporting may be supported based on on-demand SSB.

[0272] Operation) Enhanced on-demand SSB triggering and transmission for CSI reporting

[0273] For an SSB index included in the on-demand SSB configuration, which is configured as an on-demand SSB configured as shown in Figure 11, Figure 12 or Figure 13, an on-demand SSB, or an SSB configured as a constant transmission as shown in Figure 11 or Figure 13, and which is configured as a measurement resource in the CSI report configuration, the UE may assume one or more of the following regarding the triggering and transmission of the on-demand SSB:

[0274] Alt. 1: CSI reporting configuration implies triggering of on-demand SSB. CSI reporting configuration, e.g., RRC configuration / reconfiguration with periodic CSI reporting, can trigger on-demand SSB, e.g., no other signaling is required for on-demand SSB triggering / transmission.

[0275] Alt. 1-1: On-demand SSB configured with CSI reporting configuration may be always transmitted or triggered. On-demand SSB may be triggered or transmitted from time, slot, or symbol n+n1 when the UE receives or transmits an RRC configuration or reconfiguration using the CSI reporting configuration at time, slot, or symbol n, where n1 = 0, 1, 2, .... On-demand SSB may stop transmitting from time, slot, or symbol m+n2 when the UE receives or transmits an RRC release using the CSI reporting configuration at time, slot, or symbol m, where n2 = 0, 1, 2, ....

[0276] Alt. 1-2: On-demand SSBs configured in the CSI reporting configuration may be automatically transmitted or triggered periodically.

[0277] Alt. 1-2-1: On-demand SSB may be transmitted in one, multiple, or M SSB opportunities (M >= 1). An SSB opportunity may include at least the CSI reference resource of the SSB for CSI reporting. If more than one SSB opportunity is transmitted, consecutive SSB opportunities before the CSI reference resource may be transmitted.

[0278] Alt. 1-2-2: On-demand SSB may be transmitted within a window. The window may include at least the CSI reference resource of the SSB for the CSI report. If the CSI report is for slot n, the window starts at time, slot, or symbol n-N-T-1, has duration T, and ends at time, slot, or symbol n-N, where N may be the time, slot, or symbol offset between the CSI reference resource and the CSI report. For example, as defined in Non-Patent Document 4, N=n ＣＳＩ＿ｒｅｆ +TA.

[0279] The above N, M, T, n1 and n2 may be determined by one or more of the following:

[0280] Predefined value in specification. Signaled by system information, RRC signaling MAC-CE and / or DCI. Determined by UE capabilities.

[0281] 26 is a diagram illustrating an example (5) of a CSI report according to Example 12 of the present invention. Fig. 26 shows an example of Alt. 1-1. As shown in Fig. 26, the CSI reporting configuration may constantly trigger an on-demand SSB, or the CSI report may be performed based on the on-demand SSB.

[0282] 27 is a diagram illustrating an example (6) of a CSI report according to Example 12 of the present invention. Fig. 27 shows an example of Alt. 1-2-2. As shown in Fig. 27, an on-demand SSB may be periodically triggered, or CSI measurement related to the on-demand SSB (index c) may be performed for T slots from slot n-N-T-1 to slot n-N, and CSI reporting may be performed.

[0283] Alt. 2: Activation of CSI reporting may mean triggering of on-demand SSB. For example, CSI activation signaling by MAC-CE or DCI for semi-persistent or aperiodic CSI reporting may be able to trigger on-demand SSB. For example, no other signaling for on-demand SSB triggering or transmission may be required.

[0284] Alt. 2-1: On-demand SSBs configured in the CSI reporting configuration may be constantly transmitted or triggered, for example, for semi-persistent CSI. On-demand SSBs configured in the CSI reporting configuration may be activated, transmitted, deactivated, or stopped from transmitting.

[0285] Alt. 2-1-1: When a UE receives activation or deactivation signaling by MAC-CE or DCI at time, slot, or symbol n, an on-demand SSB may be activated at time, slot, or symbol n+n1 (the first time, slot, or symbol thereafter).

[0286] For example, an on-demand SSB may be activated for semi-persistent CSI on PUCCH or semi-persistent CSI on PUSCH. n1 may be the same or different for the activation and deactivation procedures.

[0287] Alt. 2-1-2: When the UE receives activation or deactivation signaling by the MAC-CE at time, slot, or symbol n, the on-demand SSB may be activated at time / slot / symbol n+n2 (the first time, slot, or symbol thereafter).

[0288] For example, an on-demand SSB may be activated for semi-persistent CSI on the PUCCH. n2 may be the same or different for the activation and deactivation procedures.

[0289] Alt. 2-2: On-demand SSB configured in the CSI reporting configuration may be automatically and periodically transmitted or triggered within the activation period, for example, for semi-persistent CSI. Details may be similar to Alt. 1-2-1 and Alt. 1-2-2.

[0290] Alt. 2-3: The on-demand SSB configured in the CSI reporting configuration may be triggered once, for example, alone with aperiodic CSI reporting. When the UE receives activation or deactivation signaling by DCI at time, slot, or symbol n, the on-demand SSB may be activated at time, slot, or symbol n+n3 (the first time, slot, or symbol thereafter). For example, the on-demand SSB may be activated due to semi-persistent CSI or aperiodic CSI on the PUSCH.

[0291] For n1, n2, n3 = 0, 1, 2, ... above, they may be determined by one or more of the following:

[0292] Predefined value in specification. Signaled by system information, RRC signaling MAC-CE and / or DCI. Determined by UE capabilities.

[0293] FIG. 28 is a diagram illustrating an example (7) of a CSI report according to Example 12 of an embodiment of the present invention. FIG. 28 shows an example of Alt2-1-2. As shown in FIG. 28, an on-demand SSB may be activated after a time gap n2 from a HARQ-ACK for MAC-CE that activates semi-persistent CSI reported on the PUCCH. Furthermore, the semi-persistent CSI or the on-demand SSB may be deactivated after a time gap n2 from a HARQ-ACK for MAC-CE that deactivates semi-persistent CSI reported on the PUCCH.

[0294] Alt. 3: CSI reporting may also mean triggering of on-demand SSB. In the case of [periodic / semi-persistent on PUSCH / semi-persistent on PUCCH / aperiodic] CSI reporting, at least the CSI reference resource of the SSB should be triggered / transmitted for CSI derivation, e.g., no other signaling is required for on-demand SSB triggering / transmission. Details are the same as in Alt. 1-2-1 and Alt. 1-2-2.

[0295] Alt. 4: On-demand SSB configured in the reporting configuration is explicitly triggered by other signaling.

[0296] Alt. 4-1: Triggering or transmission of on-demand SSB may be bundled with CSI configuration, activation, deactivation, and CSI reporting. The gNB may explicitly trigger on-demand SSB using additional trigger signaling. The trigger signaling enables on-demand SSB to be triggered / transmitted to support CSI configuration, activation, deactivation, and CSI reporting. The UE may assume that at least the CSI reference resource of the SSB should be triggered or transmitted for CSI derivation.

[0297] Alt. 4-2: It may be assumed that there is no on-demand SSB triggering or transmission bundled with CSI configuration, activation, deactivation, or CSI reporting. In some cases, SSB may not be used for CSI derivation.

[0298] Alt. 5: Configurable and combinations of the above alternatives and subalterns.

[0299] Actions 1) and 2) may work for adapted or adapted SSB. For example, "on-demand SSB" in actions 1) and 2) may be replaced with "adapted or adapted SSB."

[0300] (Example 13) L1 measurement based on on-demand SSB, periodic, persistent, and aperiodic L1 measurement reporting based on the existing CSI framework may be supported. The configuration and measurement related to on-demand SSB for CSI reporting may be determined. For example, the CSI reporting configuration for on-demand SSB may be enhanced. Furthermore, for example, the measurement and reporting based on on-demand SSB may be enhanced.

[0301] Action 1) Enhancement of CSI reporting settings for on-demand SSB

[0302] Operation 1-1) Resource setting configuration restrictions

[0303] For an SSB index configured as an on-demand SSB as shown in Figure 11, Figure 12 or Figure 13, an SSB index configured as an on-demand SSB and an SSB transmission that is not always transmitted as shown in Figure 11 or Figure 13, or an SSB index included in an on-demand SSB configuration, the UE may assume one or more of the following:

[0304] Alt. 1-1: The SSB index cannot be used or configured for CSI measurement or reporting.

[0305] Alt. 1-2: The SSB index cannot be set by the configuration included in resourcesForChannelMeasurement for CSI measurement or reporting.

[0306] Alt. 1-3: The SSB index cannot be configured by the csi-SSB-ResourceList in the CSI-SSB-ResourceSet for CSI measurement or reporting.

[0307] Alt. 1-4: The SSB index can be used or set for CSI measurement or reporting.

[0308] Action 1-2) Report volume configuration limit

[0309] For an SSB index configured as an on-demand SSB as shown in Figure 11, Figure 12 or Figure 13, an SSB index configured as an on-demand SSB and an SSB transmission that is not always transmitted as shown in Figure 11 or Figure 13, or an SSB index included in an on-demand SSB configuration, the UE may assume one or more of the following:

[0310] Alt. 2-1: The SSB index may or may not be configured for L1-RSRP (Reference Signal Received Power) or L1-SINR (Signal-to-Interference-plus-Noise Ratio) measurements.

[0311] Alt. 2-2: When the SSB index is configured as a measurement resource of the CSI reporting configuration, the CSI reporting configuration may or may not be configured with the following report quantity:

[0312] ・ssb-Index-RSRP ・ssb-Index-RSRP-Index ・ssb-Index-SINR ・ssb-Index-SINRIndex

[0313] Action 1-3) Restrictions on CSI trigger or activation settings

[0314] For an SSB index configured as an on-demand SSB as shown in Figure 11, Figure 12 or Figure 13, an SSB index set as an on-demand SSB and an SSB transmission that is not always transmitted as shown in Figure 11 or Figure 13, or an SSB index included in an on-demand SSB configuration, the reporting configuration may or may not be set to only one or more of the following reporting configuration types.

[0315] Periodic CSI reporting, Semi-persistent CSI reporting on PUCCH, Semi-persistent CSI reporting on PUSCH, and Aperiodic CSI reporting.

[0316] Action 1-3) Any combination of the above actions 1-1), 1-2), and 1-3) may be performed.

[0317] Operation 2) Enhanced CSI Measurement and Reporting Based on On-Demand SSB

[0318] Operation 2-1) For an SSB index configured as an on-demand SSB as shown in Figure 11, Figure 12 or Figure 13, an SSB index set as an on-demand SSB and an SSB transmission that is not always transmitted as shown in Figure 11 or Figure 13, or an SSB index included in an on-demand SSB configuration, when the SSB index is configured as a measurement resource in a CSI reporting configuration, the UE may assume one or more of the CSI measurements and reports based on the on-demand SSB as shown below.

[0319] Alt. 1: The UE may derive a CSI report based only on the always-on SSB. For an SSB index configured as a measurement resource, if the SSB is transmitted as both an on-demand SSB and an always-on SSB (see FIG. 12), the UE may perform measurements only on the always-on SSB to derive a CSI report. For an SSB index configured as a measurement resource, if the SSB is transmitted only as an on-demand SSB (see FIG. 11), i.e., if there is no always-on SSB to derive a CSI report, the UE may perform Alt. 1-1-1 or Alt. 1-1-2 below.

[0320] Alt. 1-1-1: The UE does not update the CSI, i.e., the UE may report the previously measured CSI.

[0321] Alt. 1-1-2: The UE may drop or ignore the report, i.e., the UE does not report the CSI.

[0322] Alt. 2: The UE may derive a CSI report based on always-on SSB and / or on-demand SSB. If an SSB is transmitted as both an on-demand SSB and an always-on SSB for an SSB index configured as a measurement resource (see FIG. 12), the UE may measure the always-on SSB, the on-demand SSB, or both, and derive a CSI report. If an SSB is transmitted only as an on-demand SSB for an SSB index configured as a measurement resource (see FIG. 11), the UE may measure on the on-demand SSB and derive a CSI report.

[0323] Alt. 3: The UE can derive CSI reports based only on on-demand SSBs. If there are no on-demand SSBs to derive CSI reports, Alt. 1-1-1 or Alt. 1-1-2 above can be used.

[0324] Alt. 4: A configurable combination of the above Alts may be set.

[0325] Operation 2-2) For an SSB index configured as an on-demand SSB as shown in Figure 11, Figure 12 or Figure 13, an SSB index set as an on-demand SSB and an SSB transmission that is not always transmitted as shown in Figure 11 or Figure 13, or an SSB index included in an on-demand SSB configuration, when the SSB index is configured as a measurement resource in a CSI reporting configuration, the UE may assume one or more of the CSI measurements and reports based on the on-demand SSB as shown below.

[0326] Alt. 1: The UE may require at least one SSB opportunity with the same SSB index that is not later than the CSI reference resource. For example, the SSB opportunity may be either an always-on SSB or an on-demand SSB.

[0327] Alt. 2: The UE may require at least one SSB opportunity transmitted as an on-demand SSB not later than the CSI reference resource. For example, the SSB opportunity may be only an on-demand SSB.

[0328] For example, for a CSI report where reportQuantity is set to ssb-Index-RSRP, ssb-Index-SINR, ssb-Index-RSRP-Index or ssb-Index-SINR-Index and at least one of the SSB indices for channel measurement of the CSI report is configured as an on-demand SSB, after the on-demand SSB is triggered, the UE may report the CSI report only after receiving at least one SSB that is not later than the CSI reference resource, otherwise the report may be dropped (see non-patent document 4).

[0329] Actions 1) and 2) may work for adapted or adapted SSB. For example, "on-demand SSB" in actions 1) and 2) may be replaced with "adapted or adapted SSB."

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

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

[0332] Note that cell DTX / DRX may be replaced with cell DTX and / or cell DRX. Activation / deactivation may be replaced with activation and / or deactivation, activation and / or deactivation, etc.

[0333] The above-described embodiments allow beam failure detection and recovery to be performed using on-demand SSB.

[0334] That is, a technology is provided for performing beam failure detection using SSB (SS / PBCH Block) transmitted on demand in a base station that can transition to a power saving state.

[0335] (Device Configuration) Next, a functional configuration example of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. 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 proposed functions of any of the embodiments.

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

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

[0338] 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. The transmitting unit 110 and the receiving unit 120 may also be called a transmitter and a receiver, respectively.

[0339] <Terminal 20> Fig. 30 is a diagram showing an example of the functional configuration of a terminal. As shown in Fig. 30, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 30 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.

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

[0341] 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 function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function 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.

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

[0343] <Configuration of this embodiment> (Item 1) A terminal including: a control unit that performs beam failure detection using an SSB (SS / PBCH Block) transmitted on demand; and a transmission unit that transmits a beam failure recovery request to a base station, wherein the control unit determines whether to perform beam failure detection using the SSB transmitted on demand based on an SSB index of the SSB transmitted on demand. (Item 2) The terminal according to item 1, wherein the control unit does not perform beam failure detection based on the SSB transmitted on demand if the SSB index of the SSB transmitted on demand is an SSB index that is not set for SSBs that are always transmitted. (Item 3) The terminal according to item 1, wherein the control unit performs beam failure detection based on the SSB transmitted on demand if the SSB index of the SSB transmitted on demand is an SSB index that is set for SSBs that are always transmitted. (Item 4) The terminal according to item 1, wherein the control unit assumes that the SSB transmitted on demand has been triggered if the SSB transmitted on demand is set for beam failure detection. (Clause 5) The terminal according to clause 1, wherein the control unit determines whether to perform beam failure recovery using the SSB transmitted on demand based on an SSB index of the SSB transmitted on demand. (Clause 6) A communications method in which a terminal executes the following procedures: performing beam failure detection using an SSB (SS / PBCH Block) transmitted on demand; transmitting a beam failure recovery request to a base station; and determining whether to perform beam failure detection using the SSB transmitted on demand based on an SSB index of the SSB transmitted on demand.

[0344] Any of the above configurations provides a technique for performing beam fault detection using on-demand transmitted SSBs (SS / PBCH Blocks) in a base station that can transition to a power saving state. According to paragraphs 2 to 5, beam fault detection and beam fault recovery can be performed using on-demand SSBs.

[0345] (Hardware Configuration) The block diagrams (FIGS. 29 and 30) 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 directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0346] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, 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.

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

[0348] In the following description, the term "apparatus" can be interpreted 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.

[0349] Each function in the base station 10 and the terminal 20 is realized by loading specified 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.

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

[0351] 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. 29 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. 30 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 also be transmitted from a network via a telecommunications line.

[0352] 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 read-only memory (EPROM), an electrically erasable programmable read-only memory (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.

[0353] 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 (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0354] 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, a communication module, etc. 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.

[0355] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

[0357] Furthermore, the base station 10 and the 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, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0358] Fig. 32 shows an example configuration of a vehicle 2001. As shown in Fig. 32, 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.

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

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

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

[0362] 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 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

[0363] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

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

[0366] 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 detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

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

[0368] (Supplementary Notes on the Embodiments) 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; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to 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 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, but such devices may be realized by 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, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

[0370] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: 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 a 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 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable 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 LTE and / or LTE-A with 5G).

[0371] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged 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.

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

[0373] The information, signals, etc. 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.

[0374] 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 transmitted to another device.

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

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

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

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

[0379] Note that terms described 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.

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

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

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

[0383] In the present 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. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0384] 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 partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

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

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

[0387] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may 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.

[0388] 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 multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). 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.

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

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

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

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

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

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

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

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

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

[0398] Numerology may be communication parameters that apply to the transmission and / or 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, specific windowing operations performed by the transceiver in the time domain, etc.

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

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

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

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

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

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

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

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

[0407] 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 greater than or equal to 1 ms.

[0408] A resource block (RB) is a resource allocation unit in the time domain and the 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 the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

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

[0410] 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, etc.

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

[0412] 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 BWP and numbered within the BWP.

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

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

[0415] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to 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.

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

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

[0418] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

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

[0420] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Tire 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 system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A terminal having a control unit that performs beam failure detection using an SSB (SS / PBCH Block) transmitted on demand, and a transmission unit that transmits a beam failure recovery request to a base station, wherein the control unit determines whether to perform beam failure detection using the SSB transmitted on demand based on the SSB index of the SSB transmitted on demand.

2. The terminal of claim 1, wherein the control unit does not perform beam interference detection based on the SSB transmitted on demand if the SSB index of the SSB transmitted on demand is an SSB index that is not set for SSBs transmitted at all times.

3. The terminal according to claim 1, wherein the control unit performs beam failure detection based on the SSB transmitted on demand when the SSB index of the SSB transmitted on demand is an SSB index set for an SSB transmitted at all times.

4. The terminal according to claim 1, wherein the control unit assumes that the SSB transmitted on demand has been triggered if the SSB transmitted on demand is configured for beam obstruction detection.

5. The terminal according to claim 1, wherein the control unit determines whether to perform beam failure recovery using the SSB transmitted on demand based on an SSB index of the SSB transmitted on demand.

6. A communication method in which a terminal performs the following steps: performing beam failure detection using an SSB (SS / PBCH Block) transmitted on demand; transmitting a beam failure recovery request to a base station; and determining whether to perform beam failure detection using the SSB transmitted on demand based on the SSB index of the SSB transmitted on demand.

Images