Terminal and communication method

Abstract

A terminal has a control section that decides an UL transmission that triggers an on-demand SSB in an SCell, the SCell being a secondary cell, the SSB being a synchronization signal / physical broadcast channel block, the UL being an uplink; a transmission section that transmits the UL transmission to a base station; and a reception section that receives an SSB in the SCell, the control section deciding the UL transmission as a certain UL signal or a certain UL signaling.

Description

Technical Field

[0001] This invention relates to terminals and communication methods in wireless communication systems. Background Technology

[0002] In NR (New Radio) (also known as "5G"), which is the successor system to LTE (Long Term Evolution), technologies are being researched to meet the requirements of high-capacity systems, high-speed data transmission, low latency, simultaneous connection of multiple terminals, low cost, and power saving (e.g., Non-Patent Literature 1).

[0003] In addition, in 3GPP (registered trademark) version 18, in order to achieve environmental sustainability, carbon neutrality, SDGs (Sustainable Development Goals), and reduce operating costs, the importance of network energy savings has increased, and methods for energy saving are being studied (e.g., non-patent literature 2).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 38.300 V17.7.0 (2023-12)

[0007] Non-patent document 2: "New WID: Enhancements of network energy savings for NR", RP-234065, 3GPP TSG RAN Meeting #102, December 2023

[0008] Non-patent document 3: 3GPP TS 38.331 V17.7.0 (2023-12)

[0009] Non-patent document 4: 3GPP TS 38.321 V17.7.0 (2023-12)

[0010] Non-patent document 5: 3GPP TS 38.213 V17.8.0 (2023-12)

[0011] Non-patent document 6: 3GPP TS 38.133 V17.12.0 (2023-12) Summary of the Invention

[0012] The problem that the invention aims to solve

[0013] To achieve carbon neutrality and the SDGs, the importance of conserving base station power has increased, and the introduction of intermittent transmission and reception in base stations is being studied. To achieve efficient base station power-saving (energy saving, ES) states, on-demand transmission of synchronization signals needs to be introduced.

[0014] The present invention was made in view of the above-mentioned problems, and its object is to enable a base station that can migrate to a power-saving state to perform on-demand transmission of synchronization signals.

[0015] Methods for solving problems

[0016] According to the disclosed technology, a terminal is provided, comprising: a control unit that determines to trigger UL transmission for on-demand SSB in a SCell, wherein the SCell is a sub-cell, the SSB is a synchronization signal / physical broadcast channel block, and the UL is an uplink; a transmission unit that transmits the UL transmission to a base station; and a receiving unit that receives the SSB in the SCell, wherein the control unit determines the UL transmission as a certain UL signal or a certain UL signaling.

[0017] Invention Effects

[0018] According to publicly available technology, base stations that can migrate to a power-saving state can perform on-demand transmission of synchronization signals. Attached Figure Description

[0019] Figure 1 This is a diagram used to illustrate the wireless communication system involved in the embodiments of the present invention.

[0020] Figure 2 This is a diagram used to illustrate CDRX in NR version 15.

[0021] Figure 3 This is a diagram used to illustrate WUS in NR version 16.

[0022] Figure 4 This is a diagram illustrating the intermittent reception of a base station according to Embodiment 1 of the present invention.

[0023] Figure 5 This is a diagram illustrating the parameters involved in Embodiment 1 of the present invention.

[0024] Figure 6 This is a diagram illustrating the intermittent transmission of a base station according to Embodiment 5 of the present invention.

[0025] Figure 7 This is a diagram illustrating the parameters involved in Embodiment 5 of the present invention.

[0026] Figure 8 This is a diagram illustrating an example of an SSB according to Embodiment 9 of the present invention.

[0027] Figure 9 This is a diagram illustrating an example of on-demand delivery according to Embodiment 9 of the present invention.

[0028] Figure 10 This is a diagram illustrating an example of the functional structure of a base station according to an embodiment of the present invention.

[0029] Figure 11 This is a diagram illustrating an example of the functional structure of a terminal according to an embodiment of the present invention.

[0030] Figure 12 This is a diagram illustrating an example of the hardware structure of a base station or terminal according to an embodiment of the present invention.

[0031] Figure 13 This is a diagram illustrating an example of the structure of a vehicle according to an embodiment of the present invention. Detailed Implementation

[0032] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Furthermore, the embodiments described below are examples, and the application of the present invention is not limited to the embodiments described below.

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

[0034] Furthermore, in the embodiments of the present invention described below, the terms 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 systems are used. These are for ease of description, and the same signals and functions may also be referred to by other names. Additionally, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily explicitly written as "NR-".

[0035] In addition, in embodiments of the present invention, the duplex mode can be TDD (Time Division Duplex), FDD (Frequency Division Duplex), or other modes (e.g., Flexible Duplex).

[0036] Furthermore, in embodiments of the present invention, the "configure" wireless parameters can be pre-configured predetermined values, or wireless parameters notified from a base station or terminal.

[0037] (System Structure)

[0038] Figure 1 This is a diagram used to illustrate the wireless communication system involved in the embodiments of the present invention.

[0039] like Figure 1 As shown, the wireless communication system according to the embodiments of the present invention includes a base station 10 and a terminal 20. Figure 1The image shows one base station 10 and one terminal 20, but this is just an example; there could be multiple terminals.

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

[0041] Base station 10 sends synchronization signals and system information to terminal 20. Synchronization signals may be, for example, NR-PSS and NR-SSS. System information may be sent via NR-PBCH, also known as broadcast information. Synchronization signals and system information can also be referred to as SSB (SS / PBCH block). Figure 1 As shown, base station 10 sends control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of beamforming for signal transmission and reception. Furthermore, both base station 10 and terminal 20 can apply MIMO (Multiple Input Multiple Output) based communication to DL or UL. Additionally, base station 10 and terminal 20 can also communicate via CA (Carrier Aggregation) based secondary cells (SCell) and primary cells (PCell). Moreover, terminal 20 can also communicate via DC (Dual Connectivity) based primary cells of base station 10 and primary SCG cells of other base stations 10.

[0042] Terminal 20 is a communication device with wireless communication capabilities, such as a smartphone, mobile phone, tablet computer, wearable terminal, or M2M (Machine-to-Machine) communication module. Figure 1As shown, terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Additionally, terminal 20 receives various reference signals transmitted from base station 10 and performs propagation path quality measurements based on the reception results of these reference signals. Furthermore, terminal 20 can also be referred to as UE, and base station 10 as gNB.

[0043] Next, we will explain the current state of discussion regarding base station power saving in NR Release 18. From the perspectives of both the transmitting and receiving sides of the base station, methods for improving network power saving for both base stations and terminals are being investigated. For example, methods are being studied whereby the base station uses potential support / feedback from terminals, as well as potential auxiliary information, to achieve more efficient dynamic and / or semi-static and finer-grained adaptation of transmission and / or reception through one or more network power saving techniques in the time, frequency, spatial, and power domains.

[0044] Next, we will explain the Discontinuous Reception (DRX) or Connected Mode Discontinuous Reception (CDRX) in previous terminals.

[0045] Figure 2 This is a diagram used to illustrate CDRX in NR version 15. In the CDRX action of NR version 15, the terminal monitors the PDCCH during the DRX enable period.

[0046] Figure 3 This is a diagram used to illustrate WUS in NR version 16. In NR version 16, the PDCCH-based Wake Up Signal (WUS) can instruct more than one terminal whether the terminal should monitor the PDCCH during the next DRX activation period.

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

[0048] The monitoring opportunity of WUS is set according to the offset relative to the on period of terminal-based function activation. When WUS indicates "inactive" (i.e., when the terminal is not sending or receiving data), the terminal can skip the monitoring during the on period and immediately switch to sleep mode.

[0049] Additionally, for example, if a PDCCH-based WUS is not detected due to a detection error, a default terminal action can be set.

[0050] DCI format 2_6 contains a 1-bit startup indication message indicating whether the device is "activated" or "inactive".

[0051] (Previous issues)

[0052] Next, we will address some of the previous issues. To achieve carbon neutrality and the SDGs, the importance of conserving the power consumption of base stations has increased. However, in the past, there has been a problem that methods for conserving the power consumption of base stations have not been standardized.

[0053] (Summary of this implementation method 1)

[0054] Therefore, in this embodiment, an example of reducing the power consumption of the base station from a time-domain perspective will be described. Hereinafter, Examples 1 to 4 will be described as specific embodiments.

[0055] (Example 1)

[0056] In this embodiment, the definitions of actions and associated concepts in the case of intermittent base station reception are explained.

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

[0058] The concept of intermittent reception for base station 10 is the same as that for terminal 20. Invalid receiving units and / or parameters can also be configured on a per-port, per-panel, per-beam, or per-carrier (or per-cell) basis.

[0059] Figure 5 This diagram illustrates the parameters involved in Embodiment 1 of the present invention. The base station CDRX can be defined by several parameters listed below. Furthermore, the units of the parameters can be symbols, time slots, subframes, milliseconds, or seconds, etc. The units can be different or the same among the parameters.

[0060] • drx-onDurationTimer: The period at the start of the DRX cycle

[0061] • drx-SlotOffset: The delay before drx-onDurationTimer starts

[0062] • drx-InactivityTimer: During the uplink transmission period after the uplink receive opportunity, terminal 20 performs uplink transmission.

[0063] • drx-LongCycleStartOffset: Defines when the long DRX cycle and the short DRX cycle begin, the long DRX cycle (i.e., drx-LongCycle), and drx-StartOffset.

[0064] •drx-ShortCycle: Short DRX cycle

[0065] • drx-ShortCycleTimer: The period during which base station 10 follows a short DRX cycle.

[0066] ·drx-RetransmissionTimerUL: The maximum period until the uplink retransmission grant is received.

[0067] ·drx-HARQ-RTT-TimerUL: The minimum period until an uplink retransmission authorization is expected.

[0068] When intermittent reception of the base station is effective, the base station 10 can receive the uplink channel transmitted from the terminal 20 when executing drx-onDurationTimer, drx-InactivityTimer or drx-RetransmissionTimerUL.

[0069] When the base station intermittently receives data, terminal 20 may also perform any of the following actions.

[0070] <Option 1>

[0071] Terminal 20 can also perform actions that envision intermittent reception by the base station. Specifically, terminal 20 identifies the state of intermittent reception by the base station via RRC, MAC-CE, or DCI. In the case of DCI, terminal 20 envisions receiving DCI from base station 10 indicating the state of intermittent reception by the base station. Furthermore, details regarding DCI-based indications will be described later in Embodiment 3.

[0072] Terminal 20 can also transmit uplink channels during the execution of drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL when the base station intermittently receives data.

[0073] <Option 2>

[0074] Terminal 20 may also ignore intermittent reception from the base station. Specifically, terminal 20 performs uplink transmission as scheduled or set by base station 10, regardless of the state of intermittent reception from the base station.

[0075] Furthermore, base station 10 can perform scheduling or settings that take into account intermittent base station reception when it is effective, or it can perform scheduling or settings that are unrelated to intermittent base station reception. When scheduling or settings that take intermittent base station reception into account are performed, the intermittent base station reception function is achieved even if terminal 20 ignores intermittent base station reception. Conversely, if scheduling or settings that do not take intermittent base station reception into account are performed, and terminal 20 ignores intermittent base station reception, power consumption by terminal 20 is wasted due to the transmission of useless signals.

[0076] On the other hand, even when intermittent reception by the base station is ineffective, the base station 10 can still receive the uplink channel transmitted from the terminal 20 regardless of the intermittent reception parameters. That is, the base station 10 can also continuously receive the uplink channel from the terminal 20 while keeping the receiving unit on.

[0077] In the event of intermittent failure of base station reception, terminal 20 may also perform any of the following actions.

[0078] <Option 1>

[0079] Terminal 20 can also perform actions that envision intermittent reception by the base station. Specifically, terminal 20 identifies the state of intermittent reception by the base station via RRC, MAC-CE, or DCI. In the case of DCI, terminal 20 envisions receiving DCI from base station 10 indicating the state of intermittent reception by the base station. Furthermore, details regarding DCI-based indications will be described later in Embodiment 3.

[0080] In the event that the base station intermittent reception is invalid, the terminal 20 performs uplink transmission as scheduled or set by the base station 10, regardless of the state of the intermittent reception.

[0081] <Option 2>

[0082] Terminal 20 may also ignore intermittent reception from the base station. Specifically, terminal 20 performs uplink transmission as scheduled or set by base station 10, regardless of the state of intermittent reception from the base station.

[0083] In addition, base station 10 can also receive terminal assistance information to determine the values ​​of the above parameters during the wake-up / sleep period.

[0084] Terminal assistance information can be a periodic representation of terminal services. Base station 10 can receive terminal assistance information at higher layers. Base station 10 considers the terminal assistance information reported by terminal 20 to determine the value of parameters.

[0085] Terminal 20 can send terminal auxiliary information such as the period of terminal services to base station 10.

[0086] According to this embodiment, intermittent reception of base station 10 can be achieved.

[0087] (Example 2)

[0088] This embodiment illustrates an example of a method for triggering intermittent reception at a base station.

[0089] The activation / deactivation of intermittent base station reception can also be performed using any of the following options.

[0090] <Option 1>

[0091] Base station 10 can also enable / disable intermittent reception of the base station when the RRC parameter representing the enable / disable intermittent reception of the base station is set by terminal 20 or other network nodes (e.g., core network or other base stations).

[0092] <Option 2>

[0093] Base station 10 can also enable / disable intermittent reception when it receives a MAC CE command indicating the enable / disable of intermittent reception from terminal 20 or other network nodes (e.g., core network or other base stations).

[0094] <Option 3>

[0095] When receiving a UCI contained in a PUCCH or PUSCH from a terminal 20, the base station 10 may also enable / disable intermittent reception of the base station based on the enable / disable instruction for intermittent reception of the base station contained in the UCI.

[0096] The UCI containing the indication of the activation / deactivation of intermittent base station reception can also be a newly defined UCI type, different from the previous ones. Alternatively, the UCI can be the same UCI type as before, such as HARQ-ACK, CSI, SR, etc.

[0097] Terminal 20 can also send a PUCCH or PUSCH to base station 10 to perform intermittent reception of base station (i.e., activate / deactivate), thereby enabling / disabling intermittent reception of base station.

[0098] Terminal 20 can also receive a DCI (Distributed Information Code) from base station 10 indicating the state of intermittent reception at the base station, in order to identify whether the UCI-based indication has been correctly decoded by base station 10, and whether there is a common understanding between base station 10 and terminal 20 regarding the state of intermittent reception at the base station. Further details regarding the DCI will be described later in Embodiment 3.

[0099] <Option 4>

[0100] Base station 10 can also enable / disable intermittent reception under certain conditions. For example, base station 10 can enable intermittent reception if it does not receive uplink channel from terminal 20 for a certain period of time. This certain period of time can be a symbol, time slot, subframe, millisecond, second, etc.

[0101] Terminal 20 can also receive a DCI (Distributed Information Citation) from base station 10 indicating the state of intermittent reception at the base station, so as to obtain a common understanding of the state of intermittent reception between base station 10 and terminal 20. Further details regarding the DCI will be described later in Embodiment 3.

[0102] <Option 5>

[0103] Base station 10 can also enable / disable intermittent reception by combining the above options.

[0104] In addition, as a process to enable / disable intermittent reception of the base station, the base station 10 may also perform any of the following actions.

[0105] <Option 1>

[0106] Base station 10 can also immediately enable / disable base station intermittent reception when executing any of the above-mentioned options that trigger the activation / deactivation of base station intermittent reception.

[0107] <Option 2>

[0108] Base station 10 can also receive a timing indication for the activation / deactivation of intermittent base station reception, which can be a certain time interval or a specified moment from the date of receiving the indication. The unit for specifying the time interval or moment can be a symbol, time slot, subframe, millisecond, second, etc. That is, base station 10 can also activate / deactivate intermittent base station reception at a specified time when executing any of the above-mentioned options that trigger the activation / deactivation of intermittent base station reception.

[0109] <Option 3>

[0110] Base station 10 can also enable / disable intermittent reception based on newly introduced timers. The timers for enabling / disabling reception can be the same or different. The units for the timers can be symbols, time slots, subframes, milliseconds, seconds, etc. Base station 10 or other network nodes such as terminal 20 can set the timers via RRC, or specify the timers via MAC-CE or UCI / DCI.

[0111] That is, when any of the above-mentioned options for triggering the activation / deactivation of intermittent base station reception are executed, the timer is executed. When the timer expires, base station 10 can also activate / deactivate intermittent base station reception.

[0112] The advantages of a timer will be explained. There exists a situation where, even if intermittent reception by the base station is indicated as valid, the actual uplink transmission from terminal 20 occurs with a certain delay after the indication due to processing by terminal 20, etc. Even in such a case, by introducing a timer, intermittent reception by the base station can be made valid after a certain period of time, thus reducing the power consumption of base station 10.

[0113] Furthermore, there exists a situation where, even if the base station's intermittent reception is indicated as invalid, actual uplink transmissions from the terminal 20 continue for a period of time after the indication due to processing by the terminal 20. Even in such cases, by introducing a timer, the base station's intermittent reception can be invalidated after a certain period, thus improving the performance of the terminal 20.

[0114] According to this embodiment, it is possible to trigger intermittent reception of the base station, and to perform the activation / deactivation actions when the trigger is triggered.

[0115] (Example 3)

[0116] In this embodiment, an example of a terminal receiving an instruction related to intermittent reception by a base station via DCI is described.

[0117] In cases where the state of intermittent reception by the base station is recognized by terminal 20 and is commonly understood in both terminal 20 and base station 10, a mechanism for indicating the state of intermittent reception from base station 10 to terminal 20 needs to be considered. For timely indication, DCI-based indication is promising.

[0118] Furthermore, as is generally understood, when the base station is intermittently receiving data, the terminal 20 can stop uplink transmission, thus saving the power consumed by the terminal 20.

[0119] To indicate the intermittent reception status of the base station, a new RNTI can also be imported. For example, the new RNTI can be set to gNBCDRX-RNTI (GC-RNTI).

[0120] Alternatively, the import of DCI fields can be done using any of the following options.

[0121] <Option 1>

[0122] To indicate the intermittent reception status of the base station, a new DCI field can be imported. The imported DCI field can be 1 bit in size, with "1" indicating a valid state and "0" indicating an invalid state. Alternatively, it can be the other way around.

[0123] <Option 2>

[0124] Alternatively, the new DCI field can be omitted. That is, the intermittent reception status of the base station can also be represented by existing fields. For example, if the corresponding DCI format is scrambled by a new RNTI such as GC-RNTI, and the HPN and RV fields are all set to "0", the terminal 20 can identify the intermittent reception status of the base station as valid.

[0125] Alternatively, for example, if the corresponding DCI format is scrambled by a new RNTI such as GC-RNTI, and the HPN and RV fields are all set to "0", and the MCS field is all set to "1", the terminal 20 may identify the intermittent reception state of the base station as invalid.

[0126] Alternatively, the corresponding DCI format can be any of the following options.

[0127] <Option 1>

[0128] It could also be the DCI inherent to terminal 20.

[0129] <Option 1-1>

[0130] Base station 10 can also use a new DCI format, different from the past, to represent the state of intermittent reception of the base station.

[0131] <Options 1-2>

[0132] Base station 10 can also use the conventional DCI format 0_1, 0_2, 1_1, 1_2 or other DCI formats to represent the intermittent reception state of the base station.

[0133] <Option 2>

[0134] It can also be a common DCI for 20 terminals.

[0135] <Option 2-1>

[0136] Base station 10 can also use a new DCI format, different from the previous one, to represent the intermittent reception state of the base station. The aforementioned new DCI field can also be imported together with other new DCI fields used for power-saving technology of base station 10 through the new DCI format. Base station 10 can also scramble the new DCI format through the aforementioned new RNTI (GC-RNTI, etc.).

[0137] <Option 2-2>

[0138] Base station 10 can also use the conventional DCI format 2_6 or other common DCI formats to represent the intermittent reception state of the base station.

[0139] If we assume the use of DCI format 2_6, then previous DCI fields in the DCI format can also be reinterpreted to indicate the state of intermittent reception by the base station. For example, the "Wake-up indication" is reinterpreted. A "1" can be used to represent a valid state, and a "0" to represent an invalid state. The reverse is also possible.

[0140] To distinguish them, base station 10 can also replace PS-RNTI and scramble DCI format 2_6 using the new RNTI (GC-RNTI, etc.) mentioned above.

[0141] According to this embodiment, the terminal 20 identifies the intermittent reception state of the base station, which can be commonly understood by both the terminal 20 and the base station 10.

[0142] (Example 4)

[0143] In this embodiment, an example of mutually reporting capability information of base stations or terminals related to intermittent reception of base stations is described.

[0144] You can also import the following capability information.

[0145] Base station capability information representing the capabilities of base station 10 can also be imported. That is, base station 10 sends base station capability information to terminal 20 or other network nodes. Terminal 20 or other network nodes that receive the base station capability information can also infer the capabilities of base station 10 based on the received base station capability information.

[0146] Base station capability information can also include information indicating whether intermittent reception by the base station is supported. Additionally, base station capability information indicating whether intermittent reception by the base station is supported can also be imported.

[0147] Additionally, the following terminal capability information can also be imported. For example, terminal capability information indicating whether intermittent base station reception is supported can also be imported. Furthermore, terminal capability information indicating whether intermittent base station reception is supported can also be imported.

[0148] If terminal 20 has the terminal capability to identify the state of intermittent base station reception, it can also identify whether the intermittent base station reception function is effective or ineffective. For example, terminal 20 can also perform the operation of option 1 shown in embodiment 1. Alternatively, if terminal 20 does not have the terminal capability to identify the state of intermittent base station reception, it can also perform the operation of option 2 shown in embodiment 1.

[0149] Additionally, terminal capability information indicating whether DCI (Distributed Compatibility Index) is supported, representing the state of intermittent base station reception, can also be imported. Furthermore, terminal capability information indicating whether new terminal-specific / group-common DCI formats are supported can also be imported.

[0150] The dependency relationship between base station capability information and terminal capability information can be any of the following options.

[0151] <Option 1>

[0152] Alternatively, it can be configured such that, in order to utilize intermittent base station reception, both base station capability information and terminal capability information indicating support for intermittent base station reception need to be reported separately.

[0153] <Option 2>

[0154] Alternatively, it can be configured such that, in order to apply intermittent base station reception, only one of the base station capability information and terminal capability information indicating support for intermittent base station reception needs to be reported.

[0155] According to this embodiment, the base stations or terminals can report each other's capability information related to intermittent reception by the base station.

[0156] The terminal capabilities in the above embodiments can be limited to the case where terminal 20 is a feature-reduced terminal, or can be applied to the case where terminal 20 is not a feature-reduced terminal.

[0157] (Summary of this implementation method 2)

[0158] In addition, to reduce power consumption in base station 10, cell DTX / DRX is being studied. For example, the alignment of cell DTX / DRX with UE-DRX in RRC connection mode and information exchange between nodes related to cell DTX / DRX are being studied. Furthermore, cell DTX / DRX can be replaced by cell DTX and cell DRX, or it can be replaced by cell DTX or cell DRX.

[0159] Mechanisms for enabling or disabling the transceiver units of base station 10 are important for reducing power consumption in base station 10. Adaptive technologies for DL ​​transmission and UL reception are being investigated to reduce power consumption in base station 10.

[0160] Cell DTX / DRX is useful for enabling adaptive DL transmission and UL reception. However, the operational details of cell DTX / DRX are not clearly defined. Therefore, embodiments 5 to 8 will be described below as specific examples related to cell DTX / DRX.

[0161] (Example 5)

[0162] In Example 5, the definition of cell DTX / DRX is explained. Cell DRX can also be defined as in Examples 1-4 above. Whether to implement cell DRX can be determined by higher-layer parameters, and the period, start time slot, offset, and duration can be further set. In addition, whether cell DRX can be applied can also be determined based on the semi-static, dynamic, or flexible network status.

[0163] Cell DTX can also be defined as described below. Whether to perform cell DTX can be determined by higher-layer parameters, which can further set the period, start time slot, offset, and duration. Additionally, the application of cell DTX can also be determined based on semi-static, dynamic, or flexible network conditions.

[0164] <Option 1>

[0165] Figure 6 This is a diagram illustrating the intermittent transmission of a base station according to Embodiment 5 of the present invention. (See diagram below.) Figure 6 As shown, the period during which the base station 10 invalidates or enables its own transmission unit can also be imported as the cell DTX.

[0166] The invalidated transmission unit and / or parameters can be per port, per panel, per beam, per carrier, or per cell. Cell DTX can be defined by some or all of the parameters shown in 1)-6) below. The unit of this parameter can be a symbol, time slot, subframe, millisecond, or second, or other units. The units can be the same or different among these parameters.

[0167] 1) dtx-onDurationTimer: The period starting from the beginning of the DTX cycle.

[0168] 2) dtx-SlotOffset: The delay period before the start of dtx-onDurationTimer.

[0169] 3) dtx-InactivityTimer: The period that begins after the DL transmission opportunity (the opportunity for base station 10 to perform DL transmission and terminal 20 to receive DL transmission).

[0170] 4) dtx-LongCycleStartOffset: Defines the dtx-StartOffset for the start of the long DTX cycle (i.e., dtx-LongCycle) and the long and short DTX cycles.

[0171] 5) dtx-ShortCycle: Short DTX cycle. This can also be optional.

[0172] 6) dtx-ShortCycleTimer: The period during which base station 10 performs a short DTX cycle. Short DTX begins when DL reception occurs during long DTX. This can also be optional.

[0173] Figure 7 This is a diagram illustrating the parameters involved in Embodiment 5 of the present invention. For example... Figure 7 As shown, starting from the beginning of dtx-LongCycle, only dtx-onDurationTimer becomes active after dtx-SlotOffset. If a DL reception occurs within dtx-LonCycle, the active time ends after dtx-InactivityTimer from the point of DL reception, and dtx-ShortCycle begins. If a DL reception occurs within dtx-ShortCycleTimer, dtx-ShortCycle continues. If no DL reception occurs within dtx-ShortCycleTimer, dtx-LongCycle begins.

[0174] When cell DTX is activated, and dtx-onDurationTimer or dtx-InactivityTimer is active, base station 10 can also transmit DL channel or DL ​​signal. As an action of terminal 20, when cell DTX is activated, and dtx-onDurationTimer or dtx-InactivityTimer is active, terminal 20 can also receive DL channel or DL ​​signal. Terminal 20 can also be designed to receive DL channel or DL ​​signal when dtx-onDurationTimer or dtx-InactivityTimer is not active.

[0175] When the cell DTX is disabled, terminal 20 can also be expected to receive the DL channel or DL ​​signal as if notified or configured by base station 10.

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

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

[0178] (Example 6)

[0179] In Example 6, the settings for cell DTX / DRX will be explained.

[0180] <Option 1>

[0181] Joint configuration can also be performed. Cell DTX and cell DRX can also be jointly configured through common parameters. When common parameters (such as CellDTXDRX-Config) are set, cell DTX and DRX can be enabled. Terminal 20 can also appropriately perform the actions of Embodiment 5.

[0182] Public parameters may contain one or both of the information elements shown in 1) and 2) below.

[0183] 1) Parameters common to both DTX and DRX. Some parameters are common to both DTX and DRX. For example, parameters indicating the on-duration timer are common to both DTX and DRX. Similarly, parameters indicating the period are common to both DTX and DRX.

[0184] 2) Parameters separated in DTX and DRX. Some parameters can be set separately in DTX and DRX. For example, the parameter representing the slot offset can be set separately in DTX and DRX.

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

[0186] <Option 2>

[0187] Separate settings can also be performed. Cell DTX and cell DRX can also be set individually using separate parameters. Cell DTX can be enabled when DTX-oriented parameters (e.g., CellDTX-Config) are set. Cell DRX can be enabled when DRX-oriented parameters (e.g., CellDRX-Config) are set. DTX-oriented parameters can also include the parameters described in Example 5. DRX-oriented parameters can also include the parameters described in Example 1.

[0188] Option 2 provides greater flexibility in setting up either cell DTX or cell DRX.

[0189] (Example 7)

[0190] In Example 7, the activation or deactivation of cell DTX / DRX will be explained. When cell DTX and cell DRX are jointly configured (Option 1 of Example 6), cell DTX and cell DRX can also be activated or deactivated as follows.

[0191] <Option 1>

[0192] Cell DTX and cell DRX can also be enabled or disabled via RRC signaling. This can also be done by setting RRC parameters. For example, these RRC parameters can be common parameters from Example 6 (e.g., CellDTXDRX-Config).

[0193] <Option 2>

[0194] MAC-CE can also be used to enable or disable cell DTX and cell DRX. When terminal 20 receives MAC-CE, it can also enable or disable cell DTX and cell DRX.

[0195] <Option 3>

[0196] The DCI can also be used to enable or disable cell DTX and cell DRX. Terminal 20 can also dynamically notify the user that cell DTX and cell DRX have been enabled or disabled via DCI. The notification based on this DCI can be executed as shown in 1)-4) below.

[0197] 1) The DCI format can be either a UE-specific DCI format or a group-common DCI format.

[0198] 2) The DCI format can be an existing format (e.g., DCI format 1_1, 1_2, 2_0) or a newly defined one (e.g., 1_x, 2_x).

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

[0200] 4) DCI fields can be a combination of existing fields and / or new fields. For example, in the case of a combination of existing fields, as shown in Alt.1) and Alt.2) below, some fields can be used to enable or disable cell DTX and cell DRX.

[0201] Alt.1) When scrambled using an existing RNTI such as CS-RNTI, and for example, when all HPNs are set to "0", all RVs are set to "00", and all TDRAs are set to "1", terminal 20 can also dynamically enable cell DTX and cell DRX. Additionally, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all TDRAs are set to "1", terminal 20 can also dynamically disable cell DTX and cell DRX.

[0202] Alt.2) When scrambled via a new RNTI, and for example, when all HPNs are set to "0" and all RVs are set to "00", terminal 20 can also dynamically enable cell DTX and cell DRX. Additionally, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", and all FDRAs are set to "1", terminal 20 can also dynamically disable cell DTX and cell DRX.

[0203] For example, with a new DCI field, the cell DTX and cell DRX can be enabled or disabled using this new DCI field. This new DCI field can also be called the "Cell DTX / DRX identifier". For example, when the cell DTX / DRX identifier is set to "1", the terminal 20 can dynamically enable the cell DTX and cell DRX. Alternatively, for example, when the cell DTX / DRX identifier is set to "0", the terminal 20 can dynamically disable the cell DTX and cell DRX. Furthermore, the DCI containing this new DCI field can also be scrambled using either an existing RNTI or a new RNTI.

[0204] In addition, when cell DTX and cell DRX are set separately (option 2 of embodiment 6), cell DTX and cell DRX can also be enabled or disabled as follows.

[0205] <Option 1>

[0206] Cell DTX or cell DRX can also be enabled or disabled via RRC signaling. This can also be done by setting RRC parameters. For example, these RRC parameters can be the separated parameters from Example 6 (e.g., CellDTX-Config, CellDRX-Config).

[0207] <Option 2>

[0208] MAC-CE can also be used to enable or disable cell DTX or cell DRX. When terminal 20 receives MAC-CE, it can also enable or disable cell DTX or cell DRX.

[0209] <Option 3>

[0210] Terminal 20 can also dynamically notify the cell DTX or cell DRX of being activated or deactivated via DCI. The notification based on this DCI can be executed as shown in 1)-4) below.

[0211] 1) The DCI format can be either a UE-specific DCI format or a group-common DCI format.

[0212] 2) The DCI format can be an existing format (e.g., DCI format 1_1, 1_2, 2_0) or a newly defined one (e.g., 1_x, 2_x).

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

[0214] 4) DCI fields can be combinations of existing fields and / or new fields. For example, different combinations of DCI fields can be used to enable or disable either the cell DTX or the cell DRX, respectively, in a manner that represents either the cell DTX or the cell DRX. For example, in the case of combinations of existing fields, as shown in Alt.1) and Alt.2) below, some fields can be used to enable or disable the cell DTX and the cell DRX.

[0215] Alt.1) When scrambling via an existing RNTI such as CS-RNTI, and for example, when all HPNs are set to "0", all RVs are set to "00", and all PRIs are set to "1", terminal 20 can also dynamically enable cell DTX. Additionally, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all PRIs are set to "1", terminal 20 can also dynamically disable cell DTX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", and all TDRAs are set to "1", terminal 20 can also dynamically enable cell DRX. Additionally, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all TDRAs are set to "1", the terminal 20 can also dynamically disable the cell DRX.

[0216] In addition, the PRI and TDRA fields can be added to indicate which of the CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX the valid or invalid DCI will be the object.

[0217] Alternatively, fields identical to those used above (such as TDRA) can be used, such as PRI and TDRA, to indicate which of the CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX is being considered as the object. When using different DCI formats, the DCI format can also indicate whether the cell DTX or cell DRX is being considered as the object. For example, DCI format 0_0 can enable or disable cell DRX, while DCI format 1_0 can enable or disable cell DTX.

[0218] Alt.2) When scrambled via a new RNTI, for example, when all HPNs are set to "0", all RVs are set to "00", and all PRIs are set to "1", terminal 20 can also dynamically enable cell DTX. For example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all PRIs are set to "1", terminal 20 can also dynamically disable cell DTX. For example, when all HPNs are set to "0", all RVs are set to "00", terminal 20 can also dynamically enable cell DRX. For example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", and all FDRAs are set to "1", terminal 20 can also dynamically disable cell DRX.

[0219] Furthermore, while PRI can be used as described above, it is also possible to omit the additional field to indicate which cell DTX or cell DRX is being considered as the object. When using different DCI formats, the DCI format can also indicate whether the cell DTX or cell DRX is being considered as the object. For example, DCI format 0_0 can enable or disable the cell DRX, while DCI format 1_0 can enable or disable the cell DTX.

[0220] For example, in the case of a new DCI field, the cell DTX or cell DRX can be enabled or disabled through this new DCI field. This new DCI field can also be called the "Cell DTX identifier" or the "Cell DRX identifier".

[0221] When cell DTX and cell DRX are notified separately using separate fields, for example, if the cell DTX identifier is set to "1", terminal 20 can also dynamically activate cell DTX. Alternatively, for example, if the cell DTX identifier is set to "0", terminal 20 can also dynamically deactivate cell DTX. Similarly, if the cell DRX identifier is set to "1", terminal 20 can also dynamically activate cell DRX. Alternatively, for example, if the cell DRX identifier is set to "0", terminal 20 can also dynamically deactivate cell DRX.

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

[0223] Furthermore, a DCI containing this new DCI field can also be scrambled using either an existing RNTI or a new RNTI.

[0224] The timing for the activation or deactivation of the application cell DTX or cell DRX notified via MAC-CE or DCI as described above can be either 1) or 2) as shown below.

[0225] 1) Terminal 20 can immediately activate or deactivate the cell DTX or cell DRX. When the activation or deactivation of the cell DTX or cell DRX is notified via MAC-CE or DCI, the cell DTX or cell DRX can be activated or deactivated immediately.

[0226] 2) Terminal 20 can activate or deactivate the cell DTX or cell DRX at the notified time. The timing of activating or deactivating the cell DTX or cell DRX can be specified as an interval or a specific moment from the time the activation or deactivation is notified, via RRC signaling, MAC-CE, or DCI. The unit of time can be a symbol, time slot, subframe, millisecond, or second, etc. When the activation or deactivation of the cell DTX or cell DRX is notified via MAC-CE or DCI, the cell DTX or cell DRX can be activated or deactivated at the pre-notified time.

[0227] (Example 8)

[0228] In Example 8, the associated operation of cell DTX / DRX and UE DRX is explained. When the time positions of cell DTX and UE DRX are not aligned, and DL transmission is not performed due to cell DTX, terminal 20 may be woken up to receive DL channel or DL ​​signal.

[0229] Therefore, the actions can also be performed as shown in options 1-5 below.

[0230] <Option 1>

[0231] If UE DRX (e.g., DRX-Config) is configured, terminal 20 may not need to configure cell DTX.

[0232] <Option 2>

[0233] If cell DTX is configured, terminal 20 may not need to configure UE DRX (e.g., DRX-Config). Furthermore, the parameters for cell DTX can be those described in Example 6.

[0234] <Option 3>

[0235] When a UE DRX (e.g., DRX-Config) is configured, terminal 20 may not need to configure a cell DTX whose time location is inconsistent with the UE DRX. When the time location of the cell DTX and the UE DRX is consistent, the cell DTX and UE DRX can also be configured jointly.

[0236] <Option 4>

[0237] When a cell DTX is configured, terminal 20 may not need to configure a UE DRX (e.g., DRX-Config) whose time location is inconsistent with the cell DTX. When the time locations of the cell DTX and UE DRX are consistent, the cell DTX and UE DRX can also be configured jointly.

[0238] <Option 5>

[0239] The cell DTX and UE DRX can be set for terminal 20 regardless of whether their time positions are consistent. Furthermore, if cell DTX is set in addition to UE DRX, the cell DTX parameters can be prioritized. Terminal 20 can also ignore UE DRX parameters. Terminal 20 can also operate as in Embodiment 5. Additionally, if cell DTX is set in addition to UE DRX, the parameters of both can be applied. Terminal 20 can also wake up at the activation time of both cell DTX and cell DRX.

[0240] The above-mentioned "the time position of the cell DTX and UE DRX is aligned" can also be defined as shown in option 1 or option 2 below.

[0241] <Option 1>

[0242] When the long cycle is the same in both the cell DTX and UE DRX, it can be defined as the time position of the cell DTX and UE DRX being consistent.

[0243] <Option 1-1>

[0244] Furthermore, when the long cycle is the same in both the cell DTX and UE DRX, it can be defined as the time position of the cell DTX and UE DRX being consistent, regardless of the activation time within the long cycle. That is, when the long cycle (e.g., dtx-LongCycle) of the cell DTX is the same as the long cycle (e.g., drx-LongCycle) of the UE DRX, it can be defined as the time position being consistent.

[0245] <Options 1-2>

[0246] When the long cycle is the same in both the cell DTX and UE DRX, the definition can be further based on the definition of the activation time within the long cycle being consistent between the cell DTX and UE DRX time positions. Similarly, when the on-period timer and slot offset (e.g., dtx-LongCycle, drx-LongCycle, dtx-onDurationTimer, drx-onDurationTimer, dtx-SlotOffset, drx-SlotOffset) are the same in both the cell DTX and UE DRX, this can also be defined as consistent between the cell DTX and UE DRX time positions. Furthermore, other parameters (e.g., dtx-InactivityTimer, drx-InactivityTimer, etc.) can be additionally considered to determine whether this definition is satisfied.

[0247] <Option 2>

[0248] When the short cycle, in addition to the long cycle, is also the same in both the cell DTX and UE DRX, it can also be defined as the cell DTX and UE DRX having the same time position. Option 2 can also be applied to situations that satisfy the conditions of Option 1-1 or Option 1-2.

[0249] <Option 2-1>

[0250] Furthermore, when the short cycle is the same in both cell DTX and UE DRX, it can be defined as the time position being consistent between cell DTX and UE DRX, regardless of the activation time within the short cycle. That is, when the short cycle (e.g., dtx-ShortCycle) of cell DTX is the same as the short cycle (e.g., drx-ShortCycle) of UE DRX, it can also be defined as the time position being consistent.

[0251] <Option 2-2>

[0252] When the short cycle is the same in both the cell DTX and UE DRX, the activation time within the short cycle can also be defined as the time position being consistent between the cell DTX and UE DRX. Similarly, when the short cycle timer and short cycle (e.g., dtx-ShortCycleTimer, drx-ShortCycleTimer, dtx-ShortCycle, drx-ShortCycle) are the same in both the cell DTX and UE DRX, it can also be defined as the time position being consistent between the cell DTX and UE DRX.

[0253] (Summary of this implementation method 3)

[0254] (Example 9)

[0255] To achieve Network Energy Savings (NES), research is underway to support on-demand transmission of SSBs in SCells for UEs with carrier aggregation configured in the connection mode. On-demand SSB transmission is performed by the UE at least for SCell time and frequency synchronization, L1 and L3 measurements, and SCell activation.

[0256] The addition and release of SCells are supported, for example, in Non-Patent Document 3. When a predetermined information element is set at a higher level, the SCell at a lower level is set to an active state.

[0257] Activation and deactivation of SCells are supported, for example, in Non-Patent Documents 4 and 5. When an SCell is activated via MAC-CE, SRS (Sounding Reference Signal) transmission, CSI reporting, PDCCH monitoring, and PUCCH transmission can be performed within that SCell. Furthermore, a timeline is defined from receiving the activation command to the execution of activation.

[0258] For example, if a SCell activation command is received in time slot n, then in time slot n+T HARQ +T activation_time +T CSI_Reporting Previously, a valid CSI report was sent to the activated SCell (see Non-Patent Literature 6).

[0259] Regarding T activation_time The value varies depending on the conditions of the SCell. For example, it can be any of the values ​​shown in 1)-5) below. Furthermore, regarding SMTC (SSB-based RRM Measurement Timing Configuration window), T SMTC_MAX T SMTC_SCell As determined in Table 1.

[0260] [Table 1]

[0261] 1) When the SCell is in FR1 and measurements have been completed beforehand (known cell), T SMTC_SCell +5ms (for cases where MeasCycleSCell is below 160ms), or T SMTC_MAX +T SMTC_SCell +5ms (for cases where MeasCycleSCell is 160ms or more). Furthermore, the 5ms detail could be 3ms for MAC decoding, leaving a 2ms margin.

[0262] 2) When the SCell is in FR1 and is an unknown cell, 2×T SMTC_MAX +2×T SMTC_SCell +5ms.

[0263] 3) When SCell is in FR2 and there is more than one active cell in this band, T SMTC_SCell +5ms.

[0264] 4) When the SCell is in FR2, and there are no active cells in this band, but it is a known cell, and when both SCell activation and TCI (Transmission Configuration Indication) status activation are received simultaneously, T MAC-CE,SCell +T FineTiming +2ms. When the SCell is in FR2, there are no active cells in this band, but they are known cells, and the SCell is activated after receiving a TCI state activation, max{T MAC-CE,SCell, T uncertainty}+T MAC-CE_TCI +T FineTiming +2ms.

[0265] 5) When the SCell is in FR2 and is an unknown cell, T MAC-CE,SCell +24×T SMTC_SCell +T L1-RSRP,measure +T uncertainty +T MAC-CE_TCI +T FineTiming +T CSI-RS_resource_configuration +2ms.

[0266] The definition of a Known cell is as follows. Under certain conditions, it can skip SSB detection in the target cell, thus shortening the time until activation is complete.

[0267] In FR1, a valid measurement report is sent during the max{measCycleSCell,DRX cycles} period before the SCell activation command is received, provided that the SSB used during that measurement can still detect the data. In the case of a known cell, only AGC (Auto Gain Control) settings are required; PSS / SSS detection and SSB index retrieval are not needed.

[0268] In FR2, a valid L3-RSRP measurement report is sent at the beam level during a period of 4 seconds (power level 1) or 3 seconds (power level 2-4) before the SCell activation command is received. The SCell activation command is received after the measurement report and before TCI activation, and the SSB used during the measurement is also capable of detecting certain conditions.

[0269] Figure 8This diagram illustrates an example of the SSB according to Embodiment 9 of the present invention. Compared to LTE, the SSB in NR offers wider bandwidth and fewer symbols, such as increasing from 6 RBs and 6 symbols to 20 RBs and 4 symbols. Furthermore, it provides greater flexibility, allowing for longer periods to be set, such as {5, 10, 20, 40, 80, 160} ms. Multiple candidate symbol positions can be set within a 5ms half-radio frame. For example, 4 can be set in the 0-3 GHz band, 8 in the 3-6 GHz band, and 64 in the 6-52.6 GHz band.

[0270] like Figure 8 As shown, transmitting towards the SSB enables beam scanning. The same cell ID is used across SSBs, but the SSB index is separate. The SSB index determines the time-domain location within a 5ms half-radio frame.

[0271] For example, operating as an SSB-less SCell, it can be performed within the FR1 intraband. When operating between FR1 bands, the SSB-less SCell can be quasi-co-located with the reference cell, or a TRS (Tracking RS) or A-TRS can be configured. The RTD can be shorter than the CP length converted from the SCS of the SSB-less SCell. The power difference between the SSB-less SCell's TRS or A-TRS and the reference cell's SSB can be below a predetermined value. Alternatively, the SSB-less SCell's RS and TRS or A-TRS can be QCL-A, and the TRS or A-TRS and the reference cell's SSB can be QCL-C.

[0272] Regarding SSB transmission within a SCell, the SSB can be omitted if not needed, and only the minimum required characteristics (period, location, etc.) can be transmitted if necessary. This can be necessary for SCell activation, L1 and / or L3 measurements of the SCell frequency, AGC, channel estimation, and time-frequency synchronization. It can also be performed outside of the aforementioned no-SSB operation scenarios and / or when the UE does not support no-SSB operation.

[0273] Figure 9This diagram illustrates an example of on-demand transmission according to Embodiment 9 of the present invention. In step S101, terminal 20 sends a signal to base station 10 requesting SSB transmission in SCell. This signal can be sent to PCell or SCell. In step S101, base station 10 performs SSB transmission in SCell. Base station 10 may also have PCell, SCell for which on-demand SSB transmission is applied, and other SCells.

[0274] The UE may transmit a predetermined UL signal containing predetermined parameters for triggering SSB transmission in the SCell, within predetermined associations and / or UL resources set by the BS. After such transmission, the UE may also perform predetermined actions related to SCell addition and / or SCell activation, or predetermined actions related to SSBs in the SCell. The above series of actions will be referred to below as "SSB triggering".

[0275] The SSB send trigger can be any one of the following 1)-6), or any combination thereof.

[0276] 1) Trigger SSB sending itself.

[0277] 2) Trigger the SSB transmission as shown below.

[0278] SSB transmission in a certain period X

[0279] • SSB transmissions with a period of X or more, less, longer, or shorter

[0280] • SSB transmissions with a period shorter than the currently transmitted, currently set, or most recently received SSB by the UE.

[0281] • SSB transmissions with a period longer than the currently transmitted, currently set, or most recently received SSB by the UE.

[0282] • Maintain SSB transmission in the current cycle

[0283] 3) Trigger the transmission of a certain SS burst or a SS burst within a certain period.

[0284] 4) Trigger the non-sending of a certain SS burst or an SS burst within a certain period.

[0285] 5) Trigger an SSB transmission at a certain opportunity.

[0286] 6) Trigger SSB transmissions when the number of SSBs sent is less than the number of SSBs sent by another SSB, the number of SSBs sent is more than the number of SSBs sent by another SSB, or the status quo is maintained.

[0287] 7) Triggering SSB transmissions where the number of SSBs sent is less than the number of SSBs sent within a certain SS burst, the number of SSBs sent is more than the number of SSBs sent within a certain SS burst, or the status quo is maintained.

[0288] 8) Trigger a certain SSB.

[0289] 9) Trigger an SSB within a certain SS burst.

[0290] 10) Trigger an SSB with a different index or position.

[0291] 11) Trigger an SSB index or an SSB with a different position within a certain SS burst.

[0292] 12) Trigger the SSB transmission of the application’s transmit beam or certain other RS ​​for a predetermined QCL relationship.

[0293] 13) Trigger the transmission of SSBs with a predetermined QCL relationship that are applied to each SSB with a different SSB index or location.

[0294] Action 1) can also determine whether to trigger UL transmission for on-demand SSB. By ensuring consistency in the identification of the signals that trigger UL transmission for on-demand SSB in the BS and UE, appropriate on-demand SSB-triggered UL transmission can be performed between the UE and BS.

[0295] Alt.1) The UE can perform SSB triggering by sending a predetermined UL signal, or it can determine the UL resources used for the UL signal based on the settings of the following parameters notified from the BS. Furthermore, SSB triggering and SSB transmission triggering can be interchanged.

[0296] The UE can trigger an SSB by sending a PRACH and / or SRS. The UE can obtain the PRACH resource associated with the transmission based on the parameters set for the PRACH, or it can refer to the PRACH resource predefined in the specification. The PRACH signal shown in 1) or 2) below can also be used for SSB triggering.

[0297] 1) To perform SSB triggering, the UE can send any PRACH signal. The UE can also use all PRACH signals for SSB triggering, waking up, or triggering the BS.

[0298] 2) The UE can send a predefined or set PRACH signal to trigger the SSB. The parameters of the PRACH signal can be one or more of the parameters shown below.

[0299] ·PRACH preamble format

[0300] Time resources

[0301] Frequency resources

[0302] ·Root sequence

[0303] • prach-ConfigurationIndex (Refer to Non-Patent Literature 3)

[0304] • Cyclic shift and restriction type (unrestricted, restricted set A, or restricted set B)

[0305] PRACH Opportunity Index

[0306] • The set of PRACH opportunities associated with a single index or a single mask index

[0307] • A PRACH opportunity index or a set of PRACH opportunity indices associated with one SSB

[0308] • Preamble index or preamble index associated with one SSB or one PRACH opportunity

[0309] • Mapping information between SSB and PRACH

[0310] • The threshold for RSRP in cells used to select wake-up cells or BS cells in ES state.

[0311] • Thresholds for determining PRACH parameters, mSSB for selecting cells in ES state, and RSRP in cells in ES state.

[0312] • Index during association

[0313] Msg1 of the random access procedure

[0314] Alt.2) The UE can perform SSB triggering by sending a pre-defined UL signaling, or it can determine the UL resources used for the UL signaling based on the settings of the following parameters notified from the BS.

[0315] Regarding the predetermined UL signaling, the UE can perform UL transmission triggered by SSB via UCI and / or MAC-CE and / or RRC signaling, or it can perform UL transmission triggered by SSB via UCI in the PHY layer, and / or by SSB via MAC-CE in the MAC entity, and / or by SSB via RRC signaling in the RRC.

[0316] When a UE triggers an SSB via UCI in the UCI or PHY layer, it can use PUCCH resources associated with the SSB trigger, predefined PUCCH resources for the SSB trigger in the specification, or PUCCH resources not associated with this purpose, depending on the parameters set by the BS.

[0317] The PUCCH resource can be determined based on pucch-ConfigCommon>pucch-ResourceCommon in the public signaling.

[0318] The parameters associated with SSB triggering (e.g., on-demandSsbTrigger) contained in the pucch-Config within the dedicated signaling can include the following settings.

[0319] • Set identifier

[0320] • Period and offset within the period, such as periodyoffset

[0321] • Associated PUCCH resource ID or PUCCH resource set ID, associated PUCCH format or PUCCH format list

[0322] The pre-defined UL signaling used by the UE in MAC-CE can be BSR (Buffer Status Report), and the pre-defined UL signaling used in MAC-CE in the MAC entity can also be BSR.

[0323] When the UE sets the predetermined UL signaling to RRC signaling, or sets the predetermined UL signaling to RRC signaling in RRC, it can also be the existing message described below.

[0324] Measurement report

[0325] ·DedicatedSIBRequest

[0326] Failure Information

[0327] ·RRCSystemInfoRequest

[0328] ·UEAssistanceInformation

[0329] ·UEInformationResponse

[0330] ·ULInformationTransfer

[0331] Regarding the parameters included in the predetermined UL signaling used for SSB triggering, the UE may include parameters representing any of the following information in the predetermined UL signaling for SSB triggering, or may select the information from a feature candidate or feature candidate list of on-demand SSBs set in advance by the BS or by the RRC, or may trigger on-demand SSBs or predetermined on-demand SSBs by referring to a part (e.g., row index) predefined in the specification (e.g., a table).

[0332] • Indicates that the SSB is triggered to send its own information.

[0333] • The parameters included in the predetermined UL signaling that trigger the on-demand transmission of the SSB can be the characteristics shown in 1)-16 below.

[0334] 1) SSB transmission in a certain period X.

[0335] 2) SSB transmissions with a period of X or more, less, longer or shorter.

[0336] 3) SSB transmission with a period shorter than the currently transmitted, currently set, or most recently received SSB by the UE.

[0337] 4) SSB transmission with a period longer than the currently transmitted, currently set, or most recently received SSB by the UE.

[0338] 5) Maintain SSB transmission in the current cycle.

[0339] 6) Trigger the transmission of a certain SS burst or an SS burst within a certain period.

[0340] 7) Trigger to prevent the sending of a certain SS burst or an SS burst within a certain period.

[0341] 8) Trigger an SSB transmission at a certain opportunity.

[0342] 9) Trigger SSB transmissions when the number of SSBs sent is less than the number of SSBs sent by another SSB, the number of SSBs sent by another SSB is more than the number of SSBs sent by another SSB, or the status quo is maintained.

[0343] 10) Triggering SSB transmissions where the number of SSBs sent is less than the number of SSBs sent within a certain SS burst, the number of SSBs sent is more than the number of SSBs sent within a certain SS burst, or the status quo is maintained.

[0344] 11) Trigger a certain SSB.

[0345] 12) Trigger an SSB within a certain SS burst.

[0346] 13) Trigger an SSB with a different index or position.

[0347] 14) Trigger an SSB index or an SSB with a different position within a certain SS burst.

[0348] 15) Trigger the SSB transmission of the application’s transmit beam or certain other RS ​​for a predetermined QCL relationship.

[0349] 16) Trigger the transmission of SSBs with a predetermined QCL relationship that are applied to each SSB with a different SSB index or location.

[0350] • The parameters included in the predetermined UL signaling that trigger the cell or frequency notification for on-demand transmission can be as shown in 1)-2).

[0351] 1) Cell ID or a list of cell IDs. Serving cell index or a list of serving cell indexes, and / or, PCI (Physical cell identity) or a list of PCIs, and / or, CGI (Cell Global Identity) or a list of CGIs, and / or, SCell ID or a list of SCell IDs.

[0352] 2) Frequency or frequency list. ARFCN-NR or ARFCN-NR list, and / or, SMTC or SMTC ID, and / or, measobject or measobject ID.

[0353] • The auxiliary information contained in the parameters of the predetermined UL signaling that triggers on-demand transmission of the cell or frequency can be as shown in 1)-7 below.

[0354] 1) Whether L1 and / or L3 have been measured during idle and / or connected periods.

[0355] 2) Has the basic information (SI) of the community been obtained?

[0356] 3) Is it a known cell, or is it an unknown cell?

[0357] 4) Whether DL and / or UL carrier aggregation is supported.

[0358] 5) What are the triggering conditions? For example, SCell time and frequency synchronization, L1 measurement in SCell, L3 measurement in SCell, CA appending, CA activation for dormancy recovery in channel estimation (QCL).

[0359] 6) L1 and / or L3 measurements in PCell and / or other SCells.

[0360] 7) Characteristic differences between the SCell and the PCell and / or other SCells. For example, the characteristic difference the UE can tolerate, and the characteristic difference it can maintain after a single measurement. This characteristic difference can be specified in the radio requirements or in the UE capabilities. This characteristic difference can be a power difference, a time difference, a propagation delay difference, a deviation from QCL type A, B, C, or D, and the time the UE can maintain this characteristic difference after a single measurement.

[0361] Alt.3) The UE may determine the UL signal and / or UL signaling and / or parameters contained in the UL signaling to be triggered by the SSB based on predetermined conditions and / or predetermined parameters set by the BS. For example, if the predetermined conditions described in Alt.4 are met, such as support for a certain UE capability, settings from the BS, or verbal instructions, the UE may perform any one of Alt.1, Alt.2, and Alt.3.

[0362] By using the above action 1), and by making the identification of the signal that triggers the UL transmission of the on-demand SSB in the BS and UE consistent, it is possible to perform appropriate on-demand SSB triggering UL transmission and reception between the UE and BS.

[0363] Action 2) can determine the cell and / or resource for triggering on-demand SSB UL transmission. By ensuring consistency in the identification of the cell or resource for triggering on-demand SSB UL transmission in the BS and UE, appropriate on-demand SSB-triggered UL transmission can be performed between the UE and BS.

[0364] Alt.1) The UE can trigger an SSB by sending a predetermined UL signal or UL signaling in the PCell. When dual connectivity is configured, the triggering can be limited to the case of triggering an on-demand SSB in the serving cell of the SCell belonging to the primary cell group, or it can also include the case of triggering an on-demand SSB in the serving cell of the SCell belonging to the secondary cell group.

[0365] Alt.2) The UE can trigger an SSB by sending a predetermined UL signal or UL signaling in the PSCell. This can be limited to the case where dual connectivity is configured, or to the case of triggering an on-demand SSB in the serving cell of the SCell belonging to the primary cell group, or it can also include the case of triggering an on-demand SSB in the serving cell of the SCell belonging to the secondary cell group.

[0366] Alt.3) The UE can trigger an SSB by sending a pre-defined UL signal or UL message in the SCell serving cell that triggers an on-demand SSB.

[0367] Alt.4) SSB triggering can be performed by sending a predetermined UL signal or UL message in a serving cell or SCell in a predetermined active state, or the serving cell for UL transmission can be determined from multiple serving cells in a predetermined state based on predetermined metrics. In the case of dual connectivity, the triggering can be limited to on-demand SSBs in serving cells of SCells belonging to the primary cell group, and may also include on-demand SSBs in serving cells of SCells belonging to the secondary cell group.

[0368] The serving cell or SCell with the predetermined activation status can be determined based on the predetermined conditions described below, or based on the settings from the BS notification, or based on any combination of the predetermined conditions described below and the settings from the BS notification (e.g., when the notification from the BS is X, condition Y is met, etc.).

[0369] The predetermined cell or SCell is the predetermined active state, which can refer to any of the following conditions being met, or any combination of the following conditions being met.

[0370] Is it PUCCH SCell or not PUCCH SCell?

[0371] • The TA (timing advance) group may be different from or the same as the PCell group.

[0372] • The TA group may be the same as or different from the cell or SCell that triggered the on-demand SSB.

[0373] • Notified from the BS as a neighboring cell (e.g., via SIB2 or SIB4 during idle time).

[0374] • During idle and / or connected periods, L1 and / or L3 may or may not have been measured. For example, a measurement report may be submitted to the BS at a predetermined event or X seconds prior. X may be determined based on the parameter measCycleSCell or DRX cycles.

[0375] • In SCell append state or SCell release state

[0376] • In SCell active state or in SCell deactivated state

[0377] • In SCell hibernation state or not in SCell hibernation state

[0378] • Is it a known cell, a non-known cell, or an unknown cell?

[0379] • The time and frequency synchronization information of the cell maintained by the UE has been lost.

[0380] • The quality information of the cell maintained by the UE (such as CSI, L1 measurement, L3 measurement) has been lost.

[0381] • No SSB and / or TRS received from the cell

[0382] • As set by the BS, and / or specified in the UE capabilities, and / or, before X seconds or Y periods, the cell did not receive or received Z seconds or Z periods of SSB and / or TRS and / or other signals or channels. This can also be limited to cases where reception was achieved with the desired quality.

[0383] The PCell is the pre-defined activation state, which can refer to any of the following conditions or any combination of the following conditions.

[0384] BSR is a pre-determined status.

[0385] • A BSR that was reported and completed X seconds ago or was decided within the UE is a pre-defined state.

[0386] MCS is a pre-defined value.

[0387] • The MCS that was notified X seconds ago is a pre-defined value.

[0388] The predetermined quality of the L3 measurement report is the predetermined quality.

[0389] • The predetermined quality of L3 measurement reports that were completed X seconds ago or were measured within the UE is the predetermined quality.

[0390] Whether the pre-defined serving cell is in the pre-defined active state can be determined based on the UE implementation.

[0391] When a predetermined timer expires or is started, the serving cell can be determined to be in the predetermined active state. For example, when a predetermined timer managed on a UE-by-UE and / or serving cell-by-serving cell and / or cell group-by-cell-associated or unassociated basis is in progress, it can be determined that on-demand SSBs in the serving cell cannot be triggered. The predetermined timer can be started or reset after a UL transmission triggering an on-demand SSB is made in the UE or serving cell, or it can be started or reset from the timer of receiving the on-demand SSB. Different timer values ​​can also be managed in the UE and BS. The timer value can be predefined in the specification, set by the BS, or an identifier set by the BS from a predefined list, or multiple lists can be set by the BS.

[0392] The serving cell and the PCell being in the predetermined active state can refer to any of the following conditions being met, or any combination of the following conditions being met.

[0393] · It is inside the belt

[0394] ·It is a space

[0395] • A band field has a predetermined correlation, such as being closer to a predetermined value than a predetermined value. For example, regarding band fields n_X and n_Y, it could also be X < Y ± 5.

[0396] • Within the frequency range

[0397] • It is between frequencies

[0398] • The frequency has a certain predetermined correlation, for example, the frequency is closer to a predetermined value.

[0399] • FR (Frequency Range) may be the same or different, for example, FR1 and FR2.

[0400] • The following conditions 1)-4) are met or not met: 1) The SSB-less SCell has a TRS or A-TRS that is quasi-co-located with the reference cell. 2) The RTD is shorter than the CP length calculated from the SCS of the SSB-less SCell. 3) The power difference between the TRS or A-TRS of the SSB-less SCell and the reference cell is below a predetermined value. 4) The RS and TRS or A-TRS of the SSB-less SCell are QCL type A, and the TRS or A-TRS and the SSB of the reference cell are QCL type C.

[0401] Alt.5) The UE can determine the actions of Alt.1)-Alt.4) based on predetermined conditions and / or predetermined parameters set by the BS. For example, if the support of a certain UE capability, the settings from the BS, and the predetermined conditions described in action 2)Alt.4) are met, the UE can perform any of the actions in Alt.1)-Alt.3). When there are multiple UL transmission cells or UL resource candidates for triggering on-demand SSB, the UE can randomly select a candidate for SSB triggering from the candidates, or select a cell and / or resource for SSB triggering based on the priority set by the BS, or select a cell and / or resource for performing UL transmission for SSB triggering based on the predetermined metrics described in Alt.1)-Alt.4).

[0402] By using the above action 2), and by ensuring consistency in the identification of the cell or resource for triggering UL transmission of on-demand SSB in the BS and UE, appropriate on-demand SSB triggering UL transmission can be performed between the UE and BS.

[0403] Action 3) When on-demand SSB is triggered, the cell from which the SSB is transmitted can be determined. By ensuring consistency in the identification of the cell that triggers the on-demand SSB in the BS and UE, appropriate on-demand SSB transmission can be performed between the UE and the BS, and appropriate reception and subsequent SSB-related procedures can be performed in the UE.

[0404] Alt.1) The UE can perform a predetermined action after the SSB is triggered based on the frequency, cell and / or characteristics (such as period, opportunity, etc.) of an on-demand SSB set by the BS.

[0405] 1-1) The UE can obtain from the BS, via public signaling, whether it can trigger an on-demand SSB in the SCell, the frequency or cell capable of executing an on-demand SSB in the SCell, and / or, the predetermined parameters required for SSB triggering. The UE can obtain from the BS, via public signaling in the PCell, whether it can trigger an on-demand SSB in the SCell, the frequency or cell capable of executing an on-demand SSB in the SCell, and / or, the predetermined parameters required for SSB triggering.

[0406] 1-2) The UE can obtain from the BS whether it can trigger an on-demand SSB in the SCell, and / or the frequency or cell capable of executing an on-demand SSB in the SCell, via dedicated signaling. The UE can obtain from the BS whether it can trigger an on-demand SSB in the SCell, and / or the frequency or cell capable of executing an on-demand SSB in the SCell, via dedicated signaling in the PCell.

[0407] In addition, the parameter list described below can be set to allow only a single entity to be set or to allow only a single entity to be set.

[0408] Alt.2) The UE can determine the frequency or cell for transmitting on-demand SSBs, and / or the characteristics (e.g., period, opportunity) related to SSBs, based on multiple frequencies or cells for transmitting on-demand SSBs set by the BS, and / or the SSB-related characteristics (e.g., period, opportunity), and the SSB triggering caused by the transmission of UL signals by UEs that are associated with candidates in multiple lists. The UE can then perform a predetermined action.

[0409] 2-1) The UE can obtain from the BS, via public signaling, the list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and the predetermined parameters for the UL signal required to trigger an SSB associated with that list. The UE can obtain from the BS, via public signaling in the PCell, the list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and the predetermined parameters for the UL signal required to trigger an SSB associated with that list. The UE can obtain from the BS, via public signaling in the serving cell that sends on-demand SSBs, the list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and the predetermined parameters for the UL signal required to trigger an SSB associated with that list. The UE can obtain from the BS, via public signaling in the predetermined serving cell, the predetermined parameters for the UL signal required to trigger an SSB associated with that list.

[0410] This public signaling can be either setting whether the action can be performed in the MIB or SIB1 within the PCell, or it can be setting whether the action can be performed in the MIB or SIB1 within the SCell. Within the PCell, it can also notify only UEs that support the action that they can camp on the cell sending the on-demand SSB. The UE can also consider this notification when performing cell selection during the cell selection process.

[0411] This public signaling can be signaling that notifies via new parameters set in existing SIB-X (2,3,4,…,2X). In SIB2 or SIB4, which notifies whether the SSB of that frequency corresponds to UE-triggered on-demand SSB transmission, or a list of frequencies or cells (PCIs) that can perform the action, it can notify whether the SSB of that frequency corresponds to UE-triggered on-demand SSB transmission.

[0412] The public signaling can be based on the newly defined SIB-Y, or it can be signaling notified by new parameters set in the SIB-Y.

[0413] 2-2) The UE can obtain from the BS, via dedicated signaling, the list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and the predetermined parameters of the UL signal required to trigger an SSB associated with that list. The UE can obtain from the BS, via dedicated signaling in the PCell, the list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and the predetermined parameters of the UL signal required to trigger an SSB associated with that list.

[0414] The dedicated signaling can be signaling notified by parameters set by RRCReconfiguration in PCell, or it can be signaling that is enabled or disabled by MAC-CE and / or DCI from any of the multiple configuration lists set in RRC.

[0415] Regarding the parameters set through RRCReconfiguration, as for their association with existing SCell appended parameters, the SSB can be set via sCellToAddModList>sCellConfig under RRCReconfiguration, or it can be left unset. The UE can assume that the SSB is set via sCellToAddModList>sCellConfig under RRCReconfiguration, or it can assume that it is left unset.

[0416] When new SSB triggering parameters are set through RRCReconfiguration, the UE can ignore the existing SSB transmission parameters of the SCell mentioned above, or it can choose not to perform SSB reception set through the existing SSB transmission parameters of the SCell.

[0417] Regarding parameters set via RRCReconfiguration, the UE can implicitly determine that an SSB trigger is valid even if the parameter is not set, or implicitly determine that an SSB trigger is valid even if a subordinate parameter of the parameter is not set. The UE can also implicitly determine that an SSB trigger is valid only if the parameter is not set and if predetermined conditions related to SSB-less SCell operation are not met.

[0418] Regarding the parameters set via RRCReconfiguration, the UE can assume a predetermined relationship between the parameters involved in the triggering of a new SSB and the transmission of an existing SSB in the SCell. For example, it can be assumed that these SSBs have the same SCS and frequency (e.g., arfcn).

[0419] As for the order of parameter settings involved in adding to an existing SCell, the UE can perform the predetermined settings related to SSB triggering before, after, or simultaneously with the settings of parameters related to SSB triggering of the existing SCell.

[0420] Regarding the parameters set via RRCReconfiguration, as a method for setting predetermined parameters related to SSB triggering (under which parameter the on-demand SSB feature is set), the UE can obtain predetermined information related to the SSB of the SCell that can perform SSB triggering from the RRC parameters or their subordinate parameters set below. The BS can set this predetermined information in the RRC parameters or their subordinate parameters set below.

[0421] ·sCellAddModList>sCellConfig (subordinate parameters)

[0422] >smtc

[0423] >sCellConfigCommon>servingCellConfigCommon> (subordinate parameters)

[0424] >>ssb-PositionsInBurst

[0425] >>ssb-PeriodicityServingCell

[0426] >>ss-PBCH-BlockPower

[0427] >sCellConfigDedicated(subordinate parameters)

[0428] • Parameters involved in L3 and / or L1 measurements. For example, measObjectNR >ssbFrequency >ssbSubcarrierSpacing >smtc1 >smtc2 >freqBandIndicatorNR >measCycleSCell Regarding the parameters set via RRCReconfiguration, the predetermined information related to the SSB of the SCell that can be triggered by SSB can be obtained from the RRC parameters set below, or it may include any of the following contents.

[0429] • Cell ID or cell ID list: Serving cell index, serving cell index list, PCI, PCI list, CGI, part or all of the CGI list.

[0430] • Frequency or frequency list, ARFCN-NR, ARFCN-NR list.

[0431] • Trigger the UL resource of the on-demand SSB in the SCell.

[0432] • Trigger UL resources for on-demand SSBs in SCells associated with cells or frequencies.

[0433] • Synchronization information and synchronization auxiliary information of the serving cell, such as whether the PCell and / or other SCells are synchronized with the SCell triggering the on-demand SSB in time and / or frequency, the value of the time and / or frequency deviation, and whether the value of the time and / or frequency deviation is below a predetermined value; power information or power auxiliary information, such as whether the power between the SSB and / or TRS in the PCell and / or other SCells and the SCell triggering the on-demand SSB is the same, whether the power difference is below a predetermined value, and the value of the power difference; QCL information, such as QCL types A, B, C, and / or D, the reference signal and QCL type of the PCell and / or other SCells that can be assumed; reference signal information, such as the TRS resources of the SCell triggering the on-demand SSB, the serving cell index of the PCell and / or other SCells that can reference time, frequency, and / or QCL, etc.

[0434] • Synchronization information and synchronization auxiliary information of the serving cell associated with the cell or frequency, such as whether the PCell and / or other SCells are synchronized with the SCell triggering the on-demand SSB in time and / or frequency, the value of the time and / or frequency deviation, and whether the value of the time and / or frequency deviation is below a predetermined value; power information or power auxiliary information, such as whether the power between the SSB and / or TRS in the PCell and / or other SCells and the SCell triggering the on-demand SSB is the same, whether the power difference is below a predetermined value, and the value of the power difference; QCL information, such as QCL types A, B, C, and / or D, the reference signal and QCL type of the PCell and / or other SCells that can be assumed; reference signal information, such as the TRS resources of the SCell triggering the on-demand SSB, the serving cell index of the PCell and / or other SCells that can reference time, frequency, and / or QCL, etc.

[0435] • Synchronization information and synchronization auxiliary information of the serving cell for on-demand SSB in the SCell, such as whether the PCell and / or other SCells have synchronized with the SCell triggering the on-demand SSB in time and / or frequency, the value of the time and / or frequency deviation, and whether the value of the time and / or frequency deviation is below a predetermined value; power information or power auxiliary information, such as whether the power of the SSB and / or TRS in the PCell and / or other SCells and the SCell triggering the on-demand SSB is the same, whether the power difference is below a predetermined value, and the value of the power difference; QCL information, such as QCL types A, B, C, and / or D, the reference signal and QCL type of the PCell and / or other SCells that can be assumed; reference signal information, such as the TRS resources of the SCell triggering the on-demand SSB, and the serving cell index of the PCell and / or other SCells that can reference time, frequency, and / or QCL, etc.

[0436] • Provide SCell feature candidates for on-demand SSBs. Period or a list of periods, such as {10, 20, 40, 80, 160, 320, 640} ms. Time-domain actions, such as aperiodic, semi-persistent (SP), periodic, etc. Other configurable characteristics can be specified based on the time-domain action, or different other characteristics can be set. For example, the period can be set only in the case of periodicity or SP, or the number of SS bursts can be set only in the case of aperiodicity. Within a given SS burst (a given opportunity), Y bitmaps can be used to notify the transmission of SSBs in 1, 2, 3, ..., N SS bursts, triggering M-period SSB transmissions, or triggering X-ms SSB transmissions after triggering. SS bursts can be transmitted with bits set to 0 or 1, or multiple SS bursts can be transmitted. Regarding the bitmap, each bit can represent one or a predetermined number of SS bursts. The number of SSB transmissions or the number of SSB transmissions within a given SS burst. Triggering a specific SSB, or triggering a specific SSB within a specific SS burst, or triggering an SSB within a specific SS burst with a different index or position. This includes SSB transmissions that have a predetermined QCL relationship with the application's transmit beam or certain other RSs, or SSB transmissions that have a predetermined QCL relationship with the transmit beam or certain other RSs applied to SSBs with different indexes or positions.

[0437] • Perform SCell characteristic candidate configuration for on-demand SSBs associated with a cell or frequency. Period or period list, such as {10, 20, 40, 80, 160, 320, 640} ms. Time-domain action, such as aperiodic, semi-persistent (SP), periodic, etc. Other configurable characteristics can be specified based on the time-domain action, or different other characteristics can be set. For example, the period can be set only in the case of periodicity or SP, or the number of SS bursts can be set only in the case of aperiodicity. In a given SS burst (a given opportunity), Y bitmaps can be used to notify the transmission of SSBs in 1, 2, 3, ..., N SS bursts, triggering M-period SSB transmissions, triggering X-ms SSB transmissions, transmitting SS bursts with bits set to 0 or 1, or transmitting multiple SS bursts. Regarding the bitmap, each bit can represent one or a predetermined number of SS bursts. The number of SSB transmissions or the number of SSB transmissions within a given SS burst. Triggering a specific SSB, or triggering a specific SSB within a specific SS burst, or triggering an SSB within a specific SS burst with a different index or position. This includes SSB transmissions that have a predetermined QCL relationship with the application's transmit beam or certain other RSs, or SSB transmissions that have a predetermined QCL relationship with the transmit beam or certain other RSs applied to SSBs with different indexes or positions.

[0438] Regarding the parameters set via RRCReconfiguration, the predetermined information related to the predetermined UL signal associated with the SSB of the SCell that can be triggered by SSB can be obtained from the RRC parameters set below, and may also include any of the following contents.

[0439] ·PRACH preamble format

[0440] Time resources

[0441] Frequency resources

[0442] ·Root sequence

[0443] • prach-ConfigurationIndex (Refer to Non-Patent Literature 3)

[0444] • Cyclic shift and restriction type (unrestricted, restricted set A, or restricted set B)

[0445] PRACH Opportunity Index

[0446] • The set of PRACH opportunities associated with a single index or a single mask index

[0447] • A PRACH opportunity index or a set of PRACH opportunity indices associated with one SSB

[0448] • Preamble index or preamble index associated with one SSB or one PRACH opportunity

[0449] • Mapping information between SSB and PRACH

[0450] • The threshold for RSRP in cells used to select wake-up cells or BS cells in ES state.

[0451] • Thresholds for determining PRACH parameters, mSSB for selecting cells in ES state, and RSRP in cells in ES state.

[0452] • Index during association

[0453] Msg1 of the random access procedure

[0454] Alt.3) The UE can determine the frequency or cell for transmitting on-demand SSBs and / or the characteristics (e.g., period, opportunity) related to the SSBs based on multiple lists of on-demand SSB transmission frequencies or cells set by the BS, and / or the characteristics (e.g., period, opportunity) related to the SSBs, and the parameters (ID and / or ID list) included in the UE's UL signaling. The UE can then perform a predetermined action. Furthermore, the UE can determine the frequency or cell for transmitting on-demand SSBs and / or the characteristics (e.g., period, opportunity) related to the SSBs based on multiple lists set by the BS, and / or the parameters (ID and / or ID list) related to the SSBs, and the UE can then perform a predetermined action. Additionally, the UL signaling that triggers on-demand SSBs can include the parameters described in Action 1) Alt.2).

[0455] 3-1) The UE can obtain from the BS, via public signaling, the list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and the predetermined parameters for the UL signal required to trigger an SSB associated with that list. The UE can obtain from the BS, via public signaling in the PCell, the list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and the predetermined parameters for the UL signal required to trigger an SSB associated with that list. The UE can obtain from the BS, via public signaling in the serving cell that sends on-demand SSBs, the list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and the predetermined parameters for the UL signal required to trigger an SSB associated with that list. The UE can obtain from the BS, via public signaling in the predetermined serving cell, the predetermined parameters for the UL signal required to trigger an SSB associated with that list.

[0456] This public signaling can be either setting whether the action can be performed in the MIB or SIB1 within the PCell, or it can be setting whether the action can be performed in the MIB or SIB1 within the SCell. Within the PCell, it can also notify only UEs that support the action that they can camp on the cell sending the on-demand SSB. The UE can also consider this notification when performing cell selection during the cell selection process.

[0457] This public signaling can be signaling that notifies via new parameters set in existing SIB-X (2,3,4,…,2X). In SIB2 or SIB4, which notifies whether the SSB of that frequency corresponds to UE-triggered on-demand SSB transmission, or a list of frequencies or cells (PCIs) that can perform the action, it can notify whether the SSB of that frequency corresponds to UE-triggered on-demand SSB transmission.

[0458] The public signaling can be based on the newly defined SIB-Y, or it can be signaling notified by new parameters set in the SIB-Y.

[0459] 3-2) The UE can obtain from the BS, via dedicated signaling, a list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and predetermined parameters for the UL signals required to trigger an SSB associated with that list. The UE can also obtain from the BS, via dedicated signaling in the PCell, a list of frequencies or cells in the SCell that can perform on-demand SSB triggering, and predetermined parameters for the UL signals required to trigger an SSB associated with that list.

[0460] The dedicated signaling can be signaling notified by parameters set by RRCReconfiguration in PCell, or it can be signaling that is enabled or disabled by MAC-CE and / or DCI from any of the multiple configuration lists set in RRC.

[0461] Regarding the parameters set through RRCReconfiguration, as for their association with existing SCell appended parameters, the SSB can be set via sCellToAddModList>sCellConfig under RRCReconfiguration, or it can be left unset. The UE can assume that the SSB is set via sCellToAddModList>sCellConfig under RRCReconfiguration, or it can assume that it is left unset.

[0462] When new SSB triggering parameters are set through RRCReconfiguration, the UE can ignore the existing SSB transmission parameters of the SCell mentioned above, or it can choose not to perform SSB reception set through the existing SSB transmission parameters of the SCell.

[0463] Regarding parameters set via RRCReconfiguration, the UE can implicitly determine that an SSB trigger is valid even if the parameter is not set, or implicitly determine that an SSB trigger is valid even if a subordinate parameter of the parameter is not set. The UE can also implicitly determine that an SSB trigger is valid only if the parameter is not set and if predetermined conditions related to SSB-less SCell operation are not met.

[0464] Regarding the parameters set via RRCReconfiguration, the UE can assume a predetermined relationship between the parameters involved in the triggering of a new SSB and the transmission of an existing SSB in the SCell. For example, it can be assumed that these SSBs have the same SCS and frequency (e.g., arfcn).

[0465] As for the order of parameter settings involved in adding to an existing SCell, the UE can perform the predetermined settings related to SSB triggering before, after, or simultaneously with the settings of parameters related to SSB triggering of the existing SCell.

[0466] Regarding the parameters set via RRCReconfiguration, as a method for setting predetermined parameters related to SSB triggering (under which parameter the on-demand SSB feature is set), the UE can obtain predetermined information related to the SSB of the SCell that can perform SSB triggering from the RRC parameters or their subordinate parameters set below. The BS can set this predetermined information in the RRC parameters or their subordinate parameters set below.

[0467] ·sCellAddModList>sCellConfig (subordinate parameters)

[0468] >smtc

[0469] >sCellConfigCommon>servingCellConfigCommon> (subordinate parameters)

[0470] >>ssb-PositionsInBurst

[0471] >>ssb-PeriodicityServingCell

[0472] >>ss-PBCH-BlockPower

[0473] >sCellConfigDedicated(subordinate parameters)

[0474] • Parameters involved in L3 and / or L1 measurements. For example, measObjectNR >ssbFrequency >ssbSubcarrierSpacing >smtc1 >smtc2 >freqBandIndicatorNR >measCycleSCell Regarding the parameters set via RRCReconfiguration, the predetermined information related to the SSB of the SCell that can be triggered by SSB can be obtained from the RRC parameters set below, or it may include any of the following contents.

[0475] • Cell ID or cell ID list: Serving cell index, serving cell index list, PCI, PCI list, CGI, part or all of the CGI list.

[0476] • Frequency or frequency list, ARFCN-NR, ARFCN-NR list.

[0477] • Trigger the UL resource of the on-demand SSB in the SCell.

[0478] • Trigger UL resources for on-demand SSBs in SCells associated with cells or frequencies.

[0479] • Synchronization information and synchronization auxiliary information of the serving cell, such as whether the PCell and / or other SCells are synchronized with the SCell triggering the on-demand SSB in time and / or frequency, the value of the time and / or frequency deviation, and whether the value of the time and / or frequency deviation is below a predetermined value; power information or power auxiliary information, such as whether the power between the SSB and / or TRS in the PCell and / or other SCells and the SCell triggering the on-demand SSB is the same, whether the power difference is below a predetermined value, and the value of the power difference; QCL information, such as QCL types A, B, C, and / or D, the reference signal and QCL type of the PCell and / or other SCells that can be assumed; reference signal information, such as the TRS resources of the SCell triggering the on-demand SSB, the serving cell index of the PCell and / or other SCells that can reference time, frequency, and / or QCL, etc.

[0480] • Synchronization information and synchronization auxiliary information of the serving cell associated with the cell or frequency, such as whether the PCell and / or other SCells are synchronized with the SCell triggering the on-demand SSB in time and / or frequency, the value of the time and / or frequency deviation, and whether the value of the time and / or frequency deviation is below a predetermined value; power information or power auxiliary information, such as whether the power between the SSB and / or TRS in the PCell and / or other SCells and the SCell triggering the on-demand SSB is the same, whether the power difference is below a predetermined value, and the value of the power difference; QCL information, such as QCL types A, B, C, and / or D, the reference signal and QCL type of the PCell and / or other SCells that can be assumed; reference signal information, such as the TRS resources of the SCell triggering the on-demand SSB, the serving cell index of the PCell and / or other SCells that can reference time, frequency, and / or QCL, etc.

[0481] • Synchronization information and synchronization auxiliary information of the serving cell for on-demand SSB in the SCell, such as whether the PCell and / or other SCells have synchronized with the SCell triggering the on-demand SSB in time and / or frequency, the value of the time and / or frequency deviation, and whether the value of the time and / or frequency deviation is below a predetermined value; power information or power auxiliary information, such as whether the power of the SSB and / or TRS in the PCell and / or other SCells and the SCell triggering the on-demand SSB is the same, whether the power difference is below a predetermined value, and the value of the power difference; QCL information, such as QCL types A, B, C, and / or D, the reference signal and QCL type of the PCell and / or other SCells that can be assumed; reference signal information, such as the TRS resources of the SCell triggering the on-demand SSB, and the serving cell index of the PCell and / or other SCells that can reference time, frequency, and / or QCL, etc.

[0482] • Provide SCell feature candidates for on-demand SSBs. Period or a list of periods, such as {10, 20, 40, 80, 160, 320, 640} ms. Time-domain actions, such as aperiodic, semi-persistent (SP), periodic, etc. Other configurable characteristics can be specified based on the time-domain action, or different other characteristics can be set. For example, the period can be set only in the case of periodicity or SP, or the number of SS bursts can be set only in the case of aperiodicity. Within a given SS burst (a given opportunity), Y bitmaps can be used to notify the transmission of SSBs in 1, 2, 3, ..., N SS bursts, triggering M-period SSB transmissions, or triggering X-ms SSB transmissions after triggering. SS bursts can be transmitted with bits set to 0 or 1, or multiple SS bursts can be transmitted. Regarding the bitmap, each bit can represent one or a predetermined number of SS bursts. The number of SSB transmissions or the number of SSB transmissions within a given SS burst. Triggering a specific SSB, or triggering a specific SSB within a specific SS burst, or triggering an SSB within a specific SS burst with a different index or position. This includes SSB transmissions that have a predetermined QCL relationship with the application's transmit beam or certain other RSs, or SSB transmissions that have a predetermined QCL relationship with the transmit beam or certain other RSs applied to SSBs with different indexes or positions.

[0483] • Perform SCell characteristic candidate configuration for on-demand SSBs associated with a cell or frequency. Period or period list, such as {10, 20, 40, 80, 160, 320, 640} ms. Time-domain action, such as aperiodic, semi-persistent (SP), periodic, etc. Other configurable characteristics can be specified based on the time-domain action, or different other characteristics can be set. For example, the period can be set only in the case of periodicity or SP, or the number of SS bursts can be set only in the case of aperiodicity. In a given SS burst (a given opportunity), Y bitmaps can be used to notify the transmission of SSBs in 1, 2, 3, ..., N SS bursts, triggering M-period SSB transmissions, triggering X-ms SSB transmissions, transmitting SS bursts with bits set to 0 or 1, or transmitting multiple SS bursts. Regarding the bitmap, each bit can represent one or a predetermined number of SS bursts. The number of SSB transmissions or the number of SSB transmissions within a given SS burst. Triggering a specific SSB, or triggering a specific SSB within a specific SS burst, or triggering an SSB within a specific SS burst with a different index or position. This includes SSB transmissions that have a predetermined QCL relationship with the application's transmit beam or certain other RSs, or SSB transmissions that have a predetermined QCL relationship with the transmit beam or certain other RSs applied to SSBs with different indexes or positions.

[0484] Regarding the parameters set via RRCReconfiguration, the predetermined information related to the predetermined UL signal associated with the SSB of the SCell that can be triggered by SSB can be obtained from the RRC parameters set below, and may also include any of the following contents.

[0485] ·PRACH preamble format

[0486] Time resources

[0487] Frequency resources

[0488] ·Root sequence

[0489] • prach-ConfigurationIndex (Refer to Non-Patent Literature 3)

[0490] • Cyclic shift and restriction type (unrestricted, restricted set A, or restricted set B)

[0491] PRACH Opportunity Index

[0492] • The set of PRACH opportunities associated with a single index or a single mask index

[0493] • A PRACH opportunity index or a set of PRACH opportunity indices associated with one SSB

[0494] • Preamble index or preamble index associated with one SSB or one PRACH opportunity

[0495] • Mapping information between SSB and PRACH

[0496] • The threshold for RSRP in cells used to select wake-up cells or BS cells in ES state.

[0497] • Thresholds for determining PRACH parameters, mSSB for selecting cells in ES state, and RSRP in cells in ES state.

[0498] • Index during association

[0499] Msg1 of the random access procedure

[0500] Alt.4) The UE may determine the actions of Alt.1)-Alt.3) based on predetermined conditions and / or predetermined parameters set by the BS. For example, if the support of a certain UE capability, the settings from the BS, and the predetermined conditions described in action 2)Alt.4) are met, the UE may execute any one of the actions of Alt.1)-Alt.3).

[0501] By using the above action 3), and by making the identification of the cell that triggers on-demand SSB consistent in the BS and UE, it is possible to perform appropriate on-demand SSB transmission between the UE and the BS, and to perform appropriate reception and subsequent procedures related to SSB in the UE.

[0502] Action 4) The UE can determine the conditions required to trigger the on-demand SSB.

[0503] Option 1) The UE may decide whether to perform UL transmission triggered by SSB transmission in the SCell based on predetermined parameters set and / or notified by the BS, or may perform a determination action to perform UL transmission triggered by SSB transmission in the SCell (i.e., may decide whether it can be performed).

[0504] The details of the predetermined parameters set and / or notified by the BS are the same as those in Alt.1 and Alt.2 of Action 3. Furthermore, the feasibility of UL transmission triggered by SSB transmission in the SCell can also be set in relation to any of the elements described below. An SSB for period X can be triggered in carrier #X or cell #X using PRACH. The details of the triggering method (e.g., PRACH or ULMAC CE) can be the same as those in Action 1). The details of the SSB characteristics can be the same as those in Alt.2) 2-2 of Action 2).

[0505] Furthermore, the permission to "perform UL transmission triggered by SSB transmission in SCell" can be set on a per-carrier and / or serving cell basis for transmitting on-demand SSBs. The carrier / cell for this setting / notification can be any of the following.

[0506] • The carrier and / or serving cell that transmits the on-demand SSB

[0507] • PCell and / or the same carrier as PCell

[0508] • Carriers and / or serving cells that meet predetermined conditions

[0509] The details of the predetermined conditions can be the same as those described in action 2) Alt.4).

[0510] Option 2) If the UE supports and / or reports predetermined action parameters related to on-demand SSB, and / or predetermined actions or parameters related to performing SSB-triggered UL transmission in the predetermined UE capabilities, it may perform a determination action to perform SSB-triggered UL transmission in the SCell, or it may perform a determination action to perform SSB-triggered UL transmission in the SCell (i.e., it may also determine whether it can be performed). This predetermined UE capability can be set at any granularity as described below.

[0511] UE, FR1, FR2, FR2-1, FR2-2, SCS, band domain, band domain combination, feature combination, FSPC (per featureset per component carrier) unit, UE, cell, each TDD, each FDD.

[0512] Furthermore, the ability to support UL transmission triggered by SSB transmission in a SCell can be configured in conjunction with any of the following elements. For example, using PRACH, regarding SSB of period X, UL triggering for SCell activation can be supported in carrier #X or cell #X.

[0513] • Triggering methods include PRACH transmission or UL MAC-CE, and the details are the same as for action 1).

[0514] • The relationship between the carrier or cell transmitted by the on-demand SSB and the carrier or cell triggered by the transmission UL meets predetermined conditions. The details of the predetermined conditions are the same as those described in action 2) Alt.4).

[0515] The characteristics of SSB are detailed in the same way as Alt.2)2-2 of action 2).

[0516] • The purpose of on-demand SSB transmission and / or the actions following transmission are detailed in the same way as action 5) described later.

[0517] Option 3) Under any predetermined condition (or any combination of conditions), the UE may perform a UL transmission triggered by SSB transmission in the SCell, or it may perform a determination action to decide whether or not to perform UL transmission triggered by SSB transmission in the SCell. This predetermined condition may be the same as action 2) Alt.4) involved in the PCell and / or serving cell. For example, in a cell X, if the UL transmission suppression timer expires and the quality of the serving cell is XX, UL transmission triggered by on-demand SSB transmission can be performed in that serving cell.

[0518] Option 4) The UE may determine the actions of Options 1)-3) based on predetermined conditions and / or predetermined parameters set by the BS. For example, if the support of a certain UE capability, the settings from the BS, and the predetermined conditions described in Action 2) Alt.4) are met, the UE may perform any of the actions in Options 1)-3).

[0519] Through the above action 4), the identification of the conditions for triggering on-demand SSB in BS and UE is consistent, thereby enabling the BS to perform appropriate UL signal reception, resource management, and on-demand SSB transmission.

[0520] Action 5) After the on-demand SSB is triggered, the action and execution process envisioned by the UE can be determined.

[0521] Furthermore, the process envisioned by the UE after UL triggering can vary depending on the UE's capabilities, the triggering conditions for UL triggering, or parameters pre-set by the BS. This process can also be applied to BS-triggered on-demand SSB transmission, in addition to UE-triggered on-demand SSB transmission.

[0522] In addition, the scheduled period can be any of the following, or it can be determined based on parameters set by the BS.

[0523] • The period defined by the time window set by the BS, or the period from the reference point to a certain delay (application delay, processing delay).

[0524] • During the time window specified in the specification, or the period from the reference point to a certain delay.

[0525] • The time window period determined by the UE's capabilities, or the period from the reference point to a certain delay.

[0526] • The time window period varies depending on the SCS set by the BS, or the period from the reference point to a certain delay.

[0527] • The time window period, or the period from the reference point to a certain delay, varies depending on the SCS specified in the specification.

[0528] • The time window period varies depending on the SCS determined by the UE's capabilities, or the period from the reference point to a certain delay.

[0529] • The time window period from the reference point set by the BS, or the period from the reference point to a certain delay.

[0530] • The time window period from the reference point specified in the specification, or the period from the reference point to a certain delay.

[0531] • The time window period starting from a reference point determined based on UE capabilities, or the period from the reference point to a certain delay.

[0532] Furthermore, "starting from the reference point" can refer to the time after the transmission of the UL signal for SSB triggering, and / or, the time after receiving the predetermined notification related to the SSB triggering notified by the BS, and / or, the time after the UE sends a predetermined UL response to the notification from the BS, and / or, the reference time (SFN, slot number, symbol number) set by the BS.

[0533] Option 1) The UE may envision sending an SSB from the BS at a predetermined period after performing a UL transmission triggered by an SSB transmission in the SCell. Alternatively, the UE may envision sending an SSB from the BS at a predetermined period within a predetermined timeframe after performing a UL transmission triggered by an SSB transmission in the SCell. This predetermined period may be determined by the UE in advance based on parameters set by the BS, or by referring to predetermined parameters notified by the BS during on-demand SSB transmission, or by being determined based on the UL transmission triggered by the UE.

[0534] Option 2) The UE may envision sending a predetermined number of SSBs from the BS after performing a UL transmission triggered by an SSB transmission in the SCell. Alternatively, the UE may envision sending a predetermined number of SSBs from the BS within a predetermined period after performing a UL transmission triggered by an SSB transmission in the SCell. This predetermined number of SSBs may be determined by the UE in advance based on parameters set by the BS, or by referring to predetermined parameters notified by the BS during on-demand SSB transmission, or by being determined based on the UL transmission triggered by the UE.

[0535] Alternatively, the predetermined number of times can also be the number of SSB transmissions determined based on any of the following factors.

[0536] The predetermined number of occurrences can be determined based on time-domain actions, such as aperiodic, SP, or periodic. Other configurable characteristics can be specified based on time-domain actions, or different other characteristics can be set. For example, the period can be set only in the case of periodic or SP, or the number of SS bursts can be set only in the case of aperiodicity.

[0537] • In a given SS burst (a given opportunity), after triggering, Y bitmaps can be used to notify the transmission of SSBs in 1, 2, 3, ..., N SS bursts, the transmission of SSBs in M ​​cycles, or the transmission of SSBs in X ms. The SS burst can be transmitted with bits set to 0 or 1, or multiple SS bursts can be transmitted. Regarding the bitmap, each bit can represent one or a predetermined number of SS bursts. The number of SSBs transmitted or the number of SSBs transmitted within an SS burst. Triggering an SSB, or triggering an SSB within an SS burst, or triggering an SSB with a different index or position than the SSB within an SS burst. SSB transmissions that have a predetermined QCL relationship with the applied transmit beam or certain other RS, or SSB transmissions that have a predetermined QCL relationship with the transmit beam or certain other RS ​​applied to SSBs with different indices or positions.

[0538] Option 3) After performing a UL transmission triggered by an SSB transmission in the SCell, the UE may use an SSB transmitted from the BS to perform predetermined actions related to the SSB, and / or predetermined actions related to the SCell, and / or predetermined actions related to L1 and / or L3 measurements. Additionally, after performing a UL transmission triggered by an SSB transmission in the SCell, the UE may, during a predetermined period, use an SSB transmitted from the BS to perform predetermined actions related to the SSB, and / or predetermined actions related to the SCell, and / or predetermined actions related to L1 and / or L3 measurements.

[0539] The scheduled action related to the SSB can be any of the following.

[0540] • Attempt to receive SSB

[0541] • Obtain the SSB's DMRS and / or PBCH and / or associated SIB1

[0542] • Time and / or frequency synchronization

[0543] ·AGC

[0544] • Channel estimation (QCL relation can also be used)

[0545] The scheduled action related to SCell can be any of the following, or a scheduled action that satisfies the wireless requirements and / or RRM requirements associated with any of the actions.

[0546] • Adding or releasing SCell

[0547] • Activate or deactivate SCell

[0548] The predetermined action related to L1 and / or L3 measurement can be any of the following, or it can be a predetermined action that satisfies the wireless requirements and / or RRM requirements related to any of the actions.

[0549] •CSI measurement

[0550] • L3 measurement (RSRP, RSRQ, or SINR)

[0551] • Idle L3 measurements (RSRP, RSRQ, or SINR)

[0552] • L3 measurement during connection (RSRP, RSRQ, or SINR)

[0553] • L3 measurements (RSRP, RSRQ, or SINR) for CSI-RS and / or SSB

[0554] • Idle L3 measurements (RSRP, RSRQ, or SINR) for CSI-RS and / or SSB

[0555] • L3 measurements (RSRP, RSRQ, or SINR) when connected to CSI-RS and / or SSB

[0556] Option 4) The UE may receive predetermined signaling or parameters related to the SSB from the BS. These predetermined signaling or parameters may be any of the following, and the UE may also determine or execute subsequent actions based on such predetermined notification (e.g., predetermined reception actions related to on-demand SSBs and / or subsequent predetermined actions related to the SCell and / or predetermined UL transmission actions). Additionally, the UE may receive predetermined signaling or parameters related to the SSB from the BS in the PCell or in the serving cell or predetermined serving cell that transmits on-demand SSBs. These predetermined notifications may be any of the following, and the UE may also determine or execute subsequent actions based on such predetermined notifications (e.g., predetermined reception actions related to on-demand SSBs and / or subsequent predetermined actions related to the SCell and / or predetermined UL transmission actions).

[0557] The pre-defined signaling can be any of the following, but is not limited to the following.

[0558] • RRC signaling RRCReconfiguration. This can also be a parameter of action 3) Alt.2) 2-2. It can also be a new signaling message sent with the on-demand SSB.

[0559] • SCell activation command or quick SCell activation command in RRC or MAC-CE. It can also be a new signaling sent with on-demand SSB.

[0560] • A predetermined DCI format scrambled via X-RNTI. X-RNTI can be NES-RNTI, SI-RNTI, or not limited to these, and can also be a new DCI format and / or RNTI that informs the SSB to send on demand.

[0561] Short messages in RRC

[0562] The predefined parameters can be any of the following, but are not limited to the following.

[0563] • Parameters related to the reference point or start point and / or duration and / or time width of sending on-demand SSBs

[0564] • Action 3) Alt.2) 2-2 The parameters or cell involved in the characteristic candidates of the SCell performing on-demand SSB transmission, and / or the frequency-related parameters involved in the characteristic candidates of the SCell performing on-demand SSB transmission.

[0565] Option 5) The UE may perform a scheduled UL transmission, execute the scheduled action of Option 4) above, or, if it fails to receive the scheduled notification of the on-demand SSB itself and / or the on-demand SSB transmission from the BS, execute the scheduled action of re-triggering the on-demand SSB. Alternatively, after receiving the scheduled notification of the on-demand SSB itself and / or the on-demand SSB transmission from the BS, the UE may perform a scheduled UL transmission, execute the scheduled action of Option 4) above, or, if it fails to receive the scheduled notification of the on-demand SSB itself and / or the on-demand SSB transmission from the BS, execute the scheduled action of re-triggering the on-demand SSB.

[0566] The scheduled UL transmission can be any of the following signaling, not limited to the following.

[0567] • It can be an L3 measurement report, or it can be new signaling related to on-demand SSB transmission.

[0568] • This could be an L3 measurement report in RRC, or new signaling related to on-demand SSB transmission.

[0569] • This could be new signaling related to on-demand SSB transmission.

[0570] • This can be new signaling related to on-demand SSB transmission in the MAC entity or MAC layer.

[0571] • It can be UCI (HARQ-ACK / NACK, CSI report, SR), SRS, PRACH, or a new UCI related to on-demand SSB transmission, and is not limited to these.

[0572] • It can be a UCI (HARQ-ACK / NACK, CSI report, SR), SRS, or PRACH in the PHY layer, or a new UCI related to on-demand SSB transmission, and is not limited to these.

[0573] The pre-defined action that triggers the on-demand SSB again can be any of the following, but is not limited to the following.

[0574] • The action described in action 1) can be performed again.

[0575] • UL transmission can be performed by increasing a predetermined counter value (e.g., by increasing parameters included in the UL signaling, or by using other resources by increasing the identifier associated with the UL signal). The UE can also have the UL resources used for re-execution and / or the Xth trigger independently set by the BS.

[0576] • You can also change the power ramping, MCS changes, repetition, repetition count, and standard UL resource quantity to perform UL transmission.

[0577] The predetermined parameters can be any of the following, but are not limited to the following.

[0578] • Parameters related to the reference point or start point and / or duration or time width of sending on-demand SSBs.

[0579] • Parameters related to the reference point or start point and / or duration or time width of the retransmission or transmission of the on-demand SSB, which are different from the initial transmission.

[0580] • Action 3) Alt.2) 2-2, the characteristic candidate of the SCell for transmitting on-demand SSB, the characteristic candidate of the SCell for transmitting on-demand SSB associated with the cell or frequency, or the characteristic candidate of the SCell for transmitting on-demand SSB that is retransmitted or different from the initial transmission, or the characteristic candidate of the SCell for transmitting on-demand SSB associated with the cell or frequency that is retransmitted or different from the initial transmission.

[0581] Through the above action 5), the procedures involved in on-demand SSB (such as SSB reception, SCell appending, SCell activation, L1 or L3 measurement of SSB) can be appropriately executed in the BS and UE after on-demand SSB triggering or SSB transmission.

[0582] Furthermore, the usage of any of the above embodiments can be set via higher-layer parameters, reported from terminal 20 to base station 10 as a UE capability, specified by a standard, reported from terminal 20 to base station 10 as a UE capability and set via higher-layer parameters, or notified via DCI. The base station-oriented WUS (Wake-up signal) can be used for cell DTX in addition to cell DRX.

[0583] In addition, UE capabilities indicating whether cell DTX and cell DRX are supported can be defined. UE capabilities indicating whether dynamic activation or deactivation of cell DTX and cell DRX can also be defined. UE capabilities indicating whether cell DTX and cell DRX accompanied by UE DRX or CDRX can also be defined.

[0584] In addition, cell DTX / DRX can also be replaced with cell DTX and / or cell DRX. Activation / deactivation can also be replaced with activation and / or deactivation, activation and / or deactivation, etc.

[0585] According to the above embodiments, in order to implement NES, it is possible to import on-demand transmission of SSBs triggered by the UE in the secondary cell.

[0586] That is, providing a technology that allows base stations to migrate to a power-saving state to perform on-demand transmission of synchronization signals.

[0587] (Device structure)

[0588] Next, an example of the functional structure of the base station 10 and the terminal 20 performing the processes and actions described above will be explained. The base station 10 and the terminal 20 include the functions of performing the embodiments described above. However, the base station 10 and the terminal 20 may each possess only the functions of any one of the proposed embodiments.

[0589] <Base Station 10>

[0590] Figure 10 This is a diagram illustrating an example of the functional structure of a base station. (For example...) Figure 10 As shown, the base station 10 includes a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. Figure 10 The functional structure shown is only one example. The functional divisions and names of the functional units can be arbitrary, as long as they can perform the actions involved in the embodiments of the present invention. The transmitting unit 110 and the receiving unit 120 can also be referred to as communication units.

[0591] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and wirelessly transmitting the signal. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining, for example, higher-level information from the received signals. Furthermore, the transmitting unit 110 has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, DL data, etc., to the terminal 20. Additionally, the transmitting unit 110 transmits setting information, etc., as described in the embodiment.

[0592] The setting unit 130 stores preset setting information and various setting information sent to the terminal 20 in a storage device, and reads it 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. Alternatively, the signal transmission-related functions of the control unit 140 may be included in the transmitting unit 110, and the signal reception-related functions of the control unit 140 may be included in the receiving unit 120. Furthermore, the transmitting unit 110 and the receiving unit 120 may be referred to as a transmitter and a receiver, respectively.

[0593] Terminal 20

[0594] Figure 11 This is a diagram illustrating an example of the functional structure of a terminal. (For example...) Figure 11 As shown, the terminal 20 includes a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. Figure 11 The functional structure shown is only one example. The functional distinctions and names of the functional units can be arbitrary, as long as they can perform the actions involved in the embodiments of the present invention. The transmitting unit 210 and the receiving unit 220 can also be referred to as communication units.

[0595] The transmitting unit 210 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains higher-layer signals from the received physical layer signals. Additionally, the transmitting unit 210 transmits HARQ-ACK, and the receiving unit 220 receives setting information, etc., as described in the embodiment.

[0596] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220 in a storage device and reads it from the storage device as needed. In addition, the setting unit 230 also stores pre-set setting information. The control unit 240 performs overall control of the terminal 20, including control related to signal transmission and reception. Alternatively, the signal transmission-related functional units of the control unit 240 can be included in the transmitting unit 210, and the signal reception-related functional units of the control unit 240 can be included in the receiving unit 220. Alternatively, the transmitting unit 210 and the receiving unit 220 can be referred to as a transmitter and a receiver, respectively.

[0597] The terminal or base station in this embodiment can be configured as shown in the following descriptions. Alternatively, the following communication methods can also be implemented.

[0598] <Structures related to this embodiment>

[0599] (Item 1)

[0600] A terminal includes: a control unit that determines to trigger a UL transmission for an on-demand SSB in a SCell, wherein the SCell is a sub-cell, the SSB is a synchronization signal / physical broadcast channel block, and the UL is an uplink; a transmission unit that transmits the UL transmission to a base station; and a receiving unit that receives an SSB in the SCell, wherein the control unit determines the UL transmission as a certain UL signal or a certain UL signaling.

[0601] (Item 2)

[0602] According to the terminal described in item 1, the control unit will send the PRACH, which is a Physical Random Access Channel, to the UL by applying a pre-determined parameter PRACH.

[0603] (Item 3)

[0604] According to the terminal described in item 1, the control unit determines whether the UL transmission is UCI, MAC signaling, or RRC signaling, wherein UCI is uplink control information, MAC is medium access control, and RRC is radio resource control.

[0605] (Item 4)

[0606] According to the terminal described in item 1, the control unit determines the resources for sending the UL signaling as a UCI based on parameters notified from the base station.

[0607] (Item 5)

[0608] According to the terminal described in item 1, the control unit includes information representing the characteristics of the SSB in the UL signaling.

[0609] (Item 6)

[0610] A communication method wherein a terminal performs the following process: determining to trigger a UL transmission for an on-demand SSB in a SCell, wherein the SCell is a secondary cell, the SSB is a synchronization signal / physical broadcast channel block, and the UL is an uplink; transmitting the UL transmission to a base station; receiving an SSB in the SCell; and determining the UL transmission as a UL signal or a UL signaling.

[0611] According to any of the above structures, a technique is provided for base stations to perform on-demand transmission of synchronization signals while migrating to a power-saving state. According to items 2 through 5, in order to implement NES, on-demand transmission of SSBs triggered by the UE in the secondary cell can be introduced.

[0612] (Hardware structure)

[0613] The block diagrams used in the description of the above embodiments ( Figure 10 and Figure 11 The diagram illustrates blocks organized by function. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software within one or more of the aforementioned devices.

[0614] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, the functional block (structural part) that performs the sending function is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0615] For example, in one embodiment of this disclosure, the base station 10, terminal 20, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 12 This diagram illustrates an example of the hardware structure of a base station 10 and a terminal 20 according to an embodiment of this disclosure. The base station 10 and the terminal 20 can be configured as a computer device that physically includes a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007, etc.

[0616] Furthermore, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of base station 10 and terminal 20 can be configured to include one or more of the devices shown in the figures, or it can be configured to not include any of them.

[0617] The functions of base station 10 and terminal 20 are implemented by reading predetermined software (program) into hardware such as processor 1001 and storage device 1002, so that processor 1001 performs calculations and controls the communication of communication device 1004 or controls at least one of reading and writing data in storage device 1002 and auxiliary storage device 1003.

[0618] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the control unit 140 and control unit 240 described above can also be implemented using the processor 1001.

[0619] Additionally, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage devices 1003 and communication devices 1004, and performs various processes accordingly. As a program, a program is used that causes the computer to perform at least a portion of the actions described in the above embodiments. For example, Figure 10 The control unit 140 of the base station 10 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Alternatively, for example, Figure 11 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Although it has been described that the various processes described above are executed by one processor 1001, the various processes described above can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by one or more chips. In addition, the program can also be sent from the network via a telecommunications line.

[0620] Storage device 1002 is a computer-readable recording medium, and may be composed of at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Storage device 1002 may also be referred to as a register, cache, main memory (main storage device), etc. Storage device 1002 can store programs (program code), software modules, etc., that are executable for implementing the communication method according to one embodiment of this disclosure.

[0621] The auxiliary storage device 1003 is a computer-readable recording medium, such as at least one of the following: CD-ROM (CompactDisc ROM) or other optical discs, hard disks, floppy disks, magneto-optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs), smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. The aforementioned storage medium may, for example, be a database, server, or other suitable media that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0622] Communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. Communication device 1004 may, for example, be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, transceiver antennas, amplifiers, transceiver units, transmission path interfaces, etc., can also be implemented using communication device 1004. The transceiver unit may also be physically or logically separated into a transmitting unit and a receiving unit.

[0623] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Furthermore, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0624] Furthermore, the processor 1001 and storage device 1002, among other devices, are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses used between devices.

[0625] Furthermore, the base station 10 and the terminal 20 can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or a FPGA (Field Programmable Gate Array), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0626] Figure 13 An example of the structure of vehicle 2001 is shown. For example... Figure 13 As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gearshift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. The various forms / implementations described in this disclosure can also be applied to communication devices mounted on the vehicle 2001, for example, to the communication module 2013.

[0627] The drive unit 2002 may be composed, for example, an engine, a motor, or a hybrid power system of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a steering wheel) 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.

[0628] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O port) 2033. Signals from various sensors 2021 to 2029 of the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

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

[0630] The Information Service Unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, which provide various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices via communication modules 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0631] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.

[0632] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 2001 via the communication port. For example, the communication module 2013 can send and receive data with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear shift lever 2006, front wheel 2007, rear wheel 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, memory (ROM, RAM) 2032, and sensors 2021 to 2029 in the vehicle 2001 via the communication port 2033.

[0633] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

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

[0635] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 of the vehicle 2001. Furthermore, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gearshift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, and sensors 2021-2029 of the vehicle 2001 based on the information stored in the memory 2032.

[0636] (Supplement to the implementation method)

[0637] The embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments. Those skilled in the art should understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these values ​​are merely examples, and any appropriate values ​​may be used. The distinctions between items in the above description are not essential to the present invention. Items described in two or more items may be combined as needed, and items described in one item may be applied to items described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. Multiple functional units may be operated by a single physical component, or a single functional unit may be operated by multiple physical components. Regarding the processing described in the embodiments, the order of processing may be interchanged unless there is a contradiction. For ease of explanation, a functional block diagram is used to illustrate the base station 10 and terminal 20, but such a device may also be implemented by hardware, software, or a combination thereof. The software operating according to the embodiments of the present invention via the processor of the base station 10 and the software operating according to the embodiments of the present invention via the processor of the terminal 20 may also 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 and other suitable storage media, respectively.

[0638] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, information notification may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Additionally, RRC signaling may be referred to as an RRC message, for example, it may also be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0639] The various forms / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The system may include at least one of 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), other suitable systems, and next-generation systems based on these systems that have been extended, modified, created, or specified. Additionally, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).

[0640] The processing procedures, timing, and flow of the various forms / implementations described in this specification may be rearranged in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order for the methods described in this disclosure, but are not limited to the specific order indicated.

[0641] In this specification, certain actions performed by base station 10 may sometimes also be performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having base station 10, it is obvious that various actions performed to communicate with terminal 20 can be performed by at least one of base station 10 and other network nodes besides base station 10 (e.g., considering MME or S-GW, but not limited to these). The above example illustrates the case where there is one other network node besides base station 10, but other network nodes can also be a combination of multiple other network nodes (e.g., MME and S-GW).

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

[0643] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0644] The determination in this disclosure can be made by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value).

[0645] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0646] In addition, software, commands, information, etc., can be sent and received via a transmission medium. For example, when software is sent from a webpage, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0647] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description as a whole can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0648] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.

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

[0650] Furthermore, the information, parameters, etc., described in this disclosure can be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources can be indicated using indexes.

[0651] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, therefore the various names assigned to these channels and information elements are non-limiting in any respect.

[0652] In this disclosure, the terms "base station (BS)," "wireless 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" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0653] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0654] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" are used interchangeably.

[0655] For mobile stations, those skilled in the art sometimes also use the following terms: 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, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0656] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Furthermore, at least one of the base station and mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). In addition, at least one of the base station and mobile station also includes devices that do not necessarily move during communication. For example, at least one of the base station and mobile station can be an IoT (Internet of Things) device such as a sensor.

[0657] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, the communication between the base station and the user terminal can be replaced by communication between multiple terminals 20 (e.g., D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.), and various forms / implementations of this disclosure can also be applied. In this case, the terminal 20 can also be configured to have the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to inter-terminal communication (e.g., "side"). For example, uplink channel, downlink channel, etc., can also be replaced with side channel.

[0658] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, the base station can also be configured to have the functions of the aforementioned user terminal.

[0659] As used in this disclosure, terms such as "determining" and "determining" sometimes encompass a variety of actions. For example, "determining" or "determining" may include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" or "determining." Furthermore, "determining" or "determining" may include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory), which are considered as actions of "determining" or "determining." Additionally, "determining" or "determining" may include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" or "determining." That is, "judgment" and "decision" can include matters that are considered as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0660] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.

[0661] The reference signal can be simply called RS (Reference Signal), or, depending on the standard applied, pilot.

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

[0663] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to the first and second elements do not imply that only two elements can be taken, or that the first element must precede the second element in any form.

[0664] Alternatively, the term "unit" in the structure of the above devices can be replaced with "section," "circuit," "equipment," etc.

[0665] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.

[0666] A wireless frame can consist of one or more frames in the time domain. Each frame in the time domain can be called a subframe. A subframe can also consist of one or more time slots in the time domain. A subframe can be a fixed duration (e.g., 1 ms) independent of the parameter set (numerology).

[0667] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.

[0668] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.

[0669] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Additionally, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type (type) A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type (type) B.

[0670] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can each be referred to by other corresponding names.

[0671] For example, a subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is to say, at least one of a subframe and a TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., symbols 1-13), or a period longer than 1ms. Furthermore, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0672] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each terminal 20) in units of TTI. However, the definition of TTI is not limited to this.

[0673] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than the TTI.

[0674] Furthermore, when one time slot or one mini time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini time slot) can become the minimum time unit for scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit for scheduling can also be controlled.

[0675] A TTI with a duration of 1ms can also be called a normal TTI (TTI in LTE Rel.8-12), a long TTI, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot.

[0676] Furthermore, for long TTIs (e.g., normal TTIs, subframes, etc.), they can be replaced with TTIs with a duration of more than 1ms. For short TTIs (e.g., shortened TTIs, etc.), they can be replaced with TTIs with a duration of less than long TTIs but more than 1ms.

[0677] A resource block (RB) is a unit of resource allocation in the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0678] In addition, the time domain of an RB can contain one or more symbols, which can be a time slot, a mini time slot, a subframe, or a TTI in length. A TTI, a subframe, etc., can each be composed of one or more resource blocks.

[0679] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB Pair, RB Pair, etc.

[0680] In addition, a resource block can consist of one or more resource elements (REs). For example, one RE can be a radio resource area consisting of one subcarrier and one symbol.

[0681] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can also represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0682] A BWP can include a UL BWP and a DL BWP. Terminal 20 can also be configured with one or more BWPs within a single carrier.

[0683] At least one of the configured BWPs can be active, and terminal 20 does not intend to transmit or receive predetermined signals / channels outside of the active BWP. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."

[0684] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other structures can be varied in many ways.

[0685] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure may also include cases where the noun following these articles is in a plural form.

[0686] In this disclosure, the phrase "A and B are different" can mean "A and B are not the same." Furthermore, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0687] The various forms / implementations described in this disclosure can be used individually, in combination, or switched during execution. Furthermore, the notification of predetermined information (e.g., a "Yes X" notification) is not limited to being explicit, but can also be implicit (e.g., not notifying the predetermined information).

[0688] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0689] Label Explanation

[0690] 10 base stations

[0691] 110 Dispatch Department

[0692] 120 Receiving Department

[0693] 130 Setting Department

[0694] 140 Control Department

[0695] 20 terminals

[0696] 210 Sending Department

[0697] 220 Receiving Department

[0698] 230 Setting Department

[0699] 240 Control Department

[0700] 1001 processor

[0701] 1002 Storage device

[0702] 1003 Auxiliary storage device

[0703] 1004 Communication device

[0704] 1005 Input Device

[0705] 1006 Output Device

[0706] Vehicle 2001

[0707] 2002 Drive Unit

[0708] 2003 Steering Unit

[0709] 2004 Accelerator Pedal

[0710] 2005 Brake Pedal

[0711] 2006 gearshift lever

[0712] 2007 front wheel

[0713] 2008 rear wheel

[0714] 2009 axle

[0715] 2010 Electronic Control Department

[0716] 2012 Information Service Department

[0717] 2013 Communication Module

[0718] 2021 Current Sensor

[0719] 2022 Speed ​​Sensor

[0720] 2023 Barometric Pressure Sensor

[0721] 2024 vehicle speed sensor

[0722] 2025 Accelerometer

[0723] 2026 Brake Pedal Sensor

[0724] 2027 Gearshift sensor

[0725] 2028 Object Detection Sensor

[0726] 2029 Accelerator Pedal Sensor

[0727] 2030 Driver Assistance Systems Department

[0728] 2031 microprocessor

[0729] 2032 Memory (ROM, RAM)

[0730] 2033 Communication Port (IO Port)

Claims

1. A terminal having: The control unit determines to trigger UL transmission for on-demand SSBs in the SCell, where the SCell is a sub-cell, the SSB is a synchronization signal / physical broadcast channel block, and the UL is an uplink; The transmitting unit transmits the UL signal to the base station; and The receiving unit, which receives SSB in the SCell, The control unit determines whether the UL transmission is a UL signal or a UL message.

2. The terminal according to claim 1, wherein, The control unit will use a pre-determined PRACH (Physical Random Access Channel) to send data to the UL.

3. The terminal according to claim 1, wherein, The control unit will determine whether the UL is sent as UCI, MAC signaling, or RRC signaling. UCI is uplink control information, MAC is medium access control, and RRC is radio resource control.

4. The terminal according to claim 1, wherein, The control unit determines the resources to send the UL signaling as a UCI based on parameters notified from the base station.

5. The terminal according to claim 1, wherein, The control unit includes information representing the characteristics of the SSB in the UL signaling.

6. A communication method, wherein, The following process is executed by the terminal: The decision is made to trigger UL transmission for the on-demand SSB in the SCell, where the SCell is a sub-cell, the SSB is a synchronization signal / physical broadcast channel block, and the UL is an uplink; The UL transmission is sent to the base station; Receive SSB in the SCell; and The UL transmission is determined to be either a UL signal or a UL message.

Images