Method and apparatus for performing uplink transmission and reception in wireless communication system

The method addresses uplink transmission and reception challenges in 6G systems by using SSB sets to detect beam and link failures, improving system reliability and performance.

WO2026101158A1PCT designated stage Publication Date: 2026-05-15LG ELECTRONICS INC
View PDF 5 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
LG ELECTRONICS INC
Filing Date
2025-11-03
Publication Date
2026-05-15

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in performing uplink transmission and reception, particularly in detecting beam failure and wireless link failure, especially in the context of emerging 6G systems with high data rates and low latency requirements.

Method used

The method involves receiving and transmitting synchronization signal block (SSB) sets to detect beam failure and wireless link failure, utilizing on-demand SSB transmission based on specific conditions.

Benefits of technology

Enables effective uplink transmission and reception in wireless communication systems, particularly in 6G networks, by accurately detecting beam and link failures, thereby enhancing system reliability and performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2025017839_15052026_PF_FP_ABST
    Figure KR2025017839_15052026_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed are a method and an apparatus for performing uplink transmission and reception in a wireless communication system. A method, according to one embodiment of the present disclosure, may comprise the steps of: receiving, by a terminal from a base station, first configuration information related to at least one of a first type synchronization signal block (SSB) set or a second type SSB set; and on the basis of the second type SSB set being activated and a condition related to the SSB set being satisfied, performing, by the terminal, link failure detection on the basis of the first type SSB set and the second type SSB set.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for performing uplink transmission and reception in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for performing uplink transmission and reception in a wireless communication system.

[0002] The 5th generation (5G) wireless communication system is a successor technology to 4G LTE (long term evolution) and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. In the case of 5G NR (New Radio), all available spectrum resources can be utilized, ranging from low-frequency bands below 1 GHz to intermediate frequency bands between 1 GHz and 10 GHz, and high-frequency (or millimeter wave) bands above 24 GHz. Based on the foundational technology of 5G wireless communication, 6G wireless communication systems are being developed.

[0003] 6G wireless communication systems are being developed with the goal of (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of 6G systems can be seen in four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity. Various technologies are being researched in consideration of the requirements for 6G systems, such as a peak data rate of 1 Tbps per device, an end-to-end (E2E) latency of 1ms, a maximum spectrum efficiency of 100 bps / Hz, support for mobility of 1000 km / h, satellite integration, artificial intelligence (AI), autonomous vehicles, extended reality (XR), and haptic communication.

[0004] The technical problem of the present disclosure is to provide a method and apparatus for performing uplink transmission and reception in a wireless communication system.

[0005] In addition, an additional technical objective of the present disclosure is to provide a method and apparatus for detecting beam failure and wireless link failure depending on whether on-demand synchronization signal block (SSB) transmission occurs.

[0006] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure belongs from the description below.

[0007] A method according to one embodiment of the present disclosure may include: receiving first setting information associated with at least one of a first type of synchronization signal block (SSB) set or a second type of SSB set from a base station by a terminal; and performing link failure detection by the terminal based on the first type of SSB set and the second type of SSB set, based on the second type of SSB set being activated and conditions associated with the SSB set being satisfied.

[0008] A method according to another embodiment of the present disclosure may include: a step of transmitting first configuration information associated with at least one of a first type of synchronization signal block (SSB) set or a second type of SSB set to a terminal by a base station; and a step of receiving information associated with link failure detection based on the first type of SSB set and the second type of SSB set from the terminal by the base station, based on the second type of SSB set being activated and conditions associated with the SSB set being satisfied.

[0009] By various embodiments of the present disclosure, a method and apparatus for performing uplink transmission and reception in a wireless communication system may be provided.

[0010] According to various embodiments of the present disclosure, a method and apparatus for detecting beam failure and wireless link failure depending on whether on-demand SSB transmission is performed may be provided.

[0011] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0012] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and explain the technical features of the present disclosure together with the detailed description.

[0013] FIG. 1 illustrates an exemplary flexible network topology to which some examples of the present disclosure may be applied.

[0014] FIG. 2 illustrates an exemplary communication system to which some examples of the present disclosure may be applied.

[0015] FIG. 3 illustrates an exemplary wireless device to which some examples of the present disclosure may be applied.

[0016] FIG. 4 illustrates an exemplary communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

[0017] FIG. 5 illustrates an exemplary functional framework for AI operations to which some examples of the present disclosure may be applied.

[0018] FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0019] FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0020] FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0021] FIG. 9 shows an electromagnetic spectrum to which some examples of the present disclosure may be applied.

[0022] FIG. 10 illustrates an exemplary system information transmission / reception procedure to which some examples of the present disclosure may be applied.

[0023] FIG. 11 illustrates an exemplary beam management procedure to which some examples of the present disclosure may be applied.

[0024] FIGS. 12 and FIGS. 13 show examples of NTN scenarios to which some examples of the present disclosure may be applied.

[0025] FIG. 14 shows examples of sensing operations to which some examples of the present disclosure may be applied.

[0026] FIG. 15 illustrates an example of a cell DTX / DRX operation to which some examples of the present disclosure may be applied.

[0027] FIG. 16 illustrates an example of a carrier aggregation (CA) operation including an SSB-free cell to which some examples of the present disclosure may be applied.

[0028] FIG. 17 illustrates an example of a conditional handover operation to which some examples of the present disclosure may be applied.

[0029] FIG. 18 illustrates an example of a procedure for CSI measurement and reporting to which some examples of the present disclosure may be applied.

[0030] FIG. 19 shows an example of an on-demand SIB1 transmission procedure to which some examples of the present disclosure may be applied.

[0031] FIG. 20 is a flowchart for explaining the operation of a terminal according to one embodiment of the present disclosure.

[0032] FIG. 21 is a flowchart for explaining the operation of a base station according to one embodiment of the present disclosure.

[0033] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiment in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will know that the present disclosure may be practiced without such specific details.

[0034] In some cases, to avoid obscuring the concept of the present disclosure, known structures and devices may be omitted or illustrated in the form of a block diagram focusing on the core functions of each structure and device.

[0035] In the present disclosure, when a component is described as being “connected,” “combined,” or “joined” with another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, in the present disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, actions, elements, components, and / or groups thereof.

[0036] In the present disclosure, terms such as "first," "second," etc. are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically stated otherwise. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment.

[0037] The terms used in this disclosure are for the description of specific embodiments and are not intended to limit the claims. As used in the description of embodiments and the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise.

[0038] In the present disclosure, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0039] A slash ( / ) or a comma used in the present disclosure may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0040] In the present disclosure, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in the present disclosure, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0041] Additionally, in the present disclosure, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Additionally, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0042] Additionally, parentheses used in the present disclosure may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be described as an example of "control information." In other words, the "control information" of the present disclosure is not limited to "PDCCH," and "PDCCH" may be described as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be described as an example of "control information."

[0043] In the following explanation, '...when, if, in case of' can be replaced with '...based on'.

[0044] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.

[0045] In the present disclosure, a terminal or user equipment (UE) may be a portable device and may be a first node that receives a signal from a base station / second node / integrated access backhaul (IAB) node.

[0046] In the present disclosure, the base station (BS, Base Station) may be a second node / IAB node / Transmission-Reception Point (TRP).

[0047] In the present disclosure, a higher layer parameter may be a parameter configured, pre-configured, or pre-defined for a terminal. For example, a base station or network may transmit the higher layer parameter to the terminal. For example, the higher layer parameter may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0048] In the present disclosure, "set or defined" may be interpreted as being set to a device through predefined signaling (e.g., System Information Block (SIB), MAC, RRC) from a base station or network. In the present disclosure, "set or defined" may be interpreted as being set to a device through separate signaling or being predefined without separate signaling.

[0049] In the present disclosure, transmitting or receiving a channel includes the meaning of transmitting or receiving information or a signal through said channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

[0050] The technology described in this disclosure can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications), GPRS (general packet radio service), and EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0051] The technology described in this disclosure can be implemented as 6G wireless technology and applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0052] Network structure

[0053] FIG. 1 illustrates an exemplary flexible network topology to which some examples of the present disclosure may be applied.

[0054] To compensate for incomplete areas of network coverage, a network topology in which the split radio access network (RAN) is configured more flexibly and resiliently may be considered. To this end, various nodes such as integrated access backhaul (IAB) nodes, relays, and radio frequency (RF) repeaters, as exemplified in Fig. 1, may be applied, and a non-terrestrial network (NTN) may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, and in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that performs simple signal amplification and forwarding functions, and in the case of a network-controlled repeater, it may adjust transmit / receive settings based on information provided by the network as well as signal amplification and forwarding. For example, NTN nodes can correspond to satellites or aircraft that provide NTN coverage that is difficult for terrestrial networks to provide. In addition to these examples, various intermediate points can be introduced to improve the network topology.

[0055] Referring to FIG. 1, a split RAN can support the division of a base station into one centralized unit (CU) and one or more distributed units (DU). The CU and DU may correspond to logical units. The CU may be further divided into a control plane (CP) portion and one or more user plane (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DU, various intermediate points may be introduced to compensate for this.

[0056] An intermediate point may correspond to a terminal or a base station depending on its relative relationship with other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a DU. The MT may connect the IAB node to a donor node. The DU of the IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to terminals. For example, an IAB node may correspond to a base station in its relative relationship with a user-side node and to a terminal in its relative relationship with a network-side node.

[0057] In some examples of the present disclosure, the description of a terminal may apply equally to an intermediate point corresponding to a terminal in relation to a network-side endpoint as well as to a user-side endpoint. Similarly, in some examples of the present disclosure, the description of a base station may apply equally to an intermediate point corresponding to a base station in relation to a user-side endpoint as well as to a network-side endpoint. In most cases where there is no additional description of the operation of three or more subjects, the communication subjects in the present disclosure are briefly described by the term terminal and / or base station (or first node and / or second node), wherein the term terminal and / or base station (or first node and / or second node) is interpreted to include or replace any endpoint or any intermediate point in relation to other nodes.

[0058] As such, in some examples of the present disclosure, for the sake of brevity of description, the subject of the operation may be referred to as a terminal and / or base station (or a first node and / or a second node). Additionally, the term terminal and / or base station (or a first node and / or a second node) may be interpreted or substituted as in the following examples: for example, the terminal (or first node) and the base station (or second node) may correspond to a first endpoint and a second endpoint, respectively; may correspond to an endpoint and an intermediate point, respectively; may correspond to an intermediate point and an endpoint, respectively; or may correspond to a first intermediate point and a second intermediate point, respectively.

[0059] In the present disclosure, there may be no intermediate points between the base station and the terminal, or there may be one or more. If intermediate points exist, the intermediate points may correspond to IAB nodes, relays, RF repeaters, NTN nodes, or nodes supporting other functions. The intermediate points may be nodes with a fixed location or nodes with an indefinite location.

[0060] Systems applicable to the present disclosure

[0061] FIG. 2 illustrates an exemplary communication system to which some examples of the present disclosure may be applied.

[0062] The communication system (100) to which the present disclosure applies includes a wireless device (110), a network device (120), and a network (130). Here, the wireless device (110) refers to a device that performs communication using wireless access technology (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G) and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device (110) may include a robot (110a), a vehicle (110b-1, 110b-2), an XR (extended reality) device (110c), a hand-held device (110d), a home appliance (110e), an IoT (Internet of Thing) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle (110b-1, 110b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (110c) includes an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.). The home appliance (110e) may include a TV, a refrigerator, a washing machine, etc. The IoT device (110f) may include a sensor, a smart meter, etc. The wireless device (110) may correspond to a terminal (or first node) or an intermediate point.The network device (120) may correspond to a base station (or a second node) or another intermediate point. For example, the network device (120) may also be implemented as a wireless device (110), and a specific wireless device (120a) may operate as a network device (120) to another wireless device (110).

[0063] Wireless devices (110a to 110f) can be connected to a network (130) through a network device (120). AI technology may be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) through the network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a 6G network. The wireless devices (110a to 110f) may communicate with each other through the network device (120) / network (130), but may also communicate directly (e.g., sidelink communication) without going through the network device (120) / network (130). For example, vehicles (110b-1, 110b-2) can communicate directly (e.g., V2V (vehicle to vehicle) / V2X (vehicle to everything) communication). Also, an IoT device (110f) (e.g., a sensor) can communicate directly with another IoT device (e.g., a sensor) or other wireless devices (110a to 110f).

[0064] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120) and between network devices (120). Here, wireless communication / connection can be established through various wireless access technologies such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between network devices (150c) (e.g., relay, IAB (integrated access backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and network devices / wireless devices, and network devices and network devices can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on the various descriptions of the present disclosure, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), a resource allocation process, etc.

[0065] Devices applicable to the present disclosure

[0066] FIG. 3 illustrates an exemplary wireless device to which some examples of the present disclosure may be applied.

[0067] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G). The wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and / or at least one antenna (208).

[0068] The processor (202) controls the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or sequences of operation disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a second information / signal through the transceiver (206) and then store information obtained from the signal processing of the second information / signal in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequences of operations disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through at least one antenna (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with a radio frequency (RF) unit. In this disclosure, a wireless device may mean a communication modem / circuit / chip.

[0069] Hereinafter, hardware elements of the wireless device (200) will be described in more detail. Although not limited thereto, at least one protocol layer may be implemented by at least one processor (202). For example, at least one processor (202) may implement at least one layer (e.g., functional layers such as PHY (physical), MAC (media access control), RLC (radio link control), PDCP (packet data convergence protocol), RRC (radio resource control), and SDAP (service data adaptation protocol). At least one processor (202) may generate at least one PDU (Protocol Data Unit) and / or at least one SDU (service data unit) according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to at least one transceiver (206). At least one processor (202) may receive a signal (e.g., a baseband signal) from at least one transceiver (206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document.

[0070] At least one processor (202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. At least one processor (202) may be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application-specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be included in at least one processor (202) or stored in at least one memory (204) and driven by at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0071] At least one memory (204) may be connected to at least one processor (202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. At least one memory (204) may be composed of ROM (read-only memory), RAM (random access memory), EPROM (erasable programmable read-only memory), flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. At least one memory (204) may be located inside and / or outside of at least one processor (202). Additionally, at least one memory (204) may be connected to at least one processor (202) via various technologies, such as wired or wireless connections.

[0072] At least one transceiver (206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc. of this document to at least one other device. At least one transceiver (206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc. disclosed in this document from at least one other device. For example, at least one transceiver (206) may be connected to at least one processor (202) and may transmit and receive wireless signals. For example, at least one processor (202) may control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Additionally, at least one processor (202) may control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. Additionally, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document through at least one antenna (208). In this document, at least one antenna may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). At least one transceiver (206) may convert the received wireless signals / channels, etc., from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc., using at least one processor (202).At least one transceiver (206) can convert user data, control information, wireless signals / channels, etc. processed using at least one processor (202) from a baseband signal to an RF band signal. To this end, at least one transceiver (206) may include an (analog) oscillator and / or filter.

[0073] The components of the wireless device described with reference to FIG. 3 may be referred to by other terms in terms of their function. For example, the processor (202) may be referred to as the control unit, the transceiver (206) as the communication unit, and the memory (204) as the storage unit. In some cases, the communication unit may be used to mean at least a part of the processor (202) and the transceiver (206).

[0074] The structure of the wireless device described with reference to FIG. 3 can be understood as the structure of at least part of various devices. For example, the structure of the wireless device illustrated in FIG. 3 may be at least part of the various devices described with reference to FIG. 2 (e.g., robot (110a), vehicle (110b-1, 110b-2), XR device (110c), portable device (110d), home appliance (110e), IoT device (110f), AI device / server (110g)). Furthermore, according to various embodiments, the device may include other components in addition to the components illustrated in FIG. 3.

[0075] For example, the device may be a portable device such as a smartphone, smartpad, wearable device (e.g., smart watch, smart glasses), or portable computer (e.g., laptop, etc.). In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an interface unit that includes at least one port for connection with another device (e.g., an audio input / output port, a video input / output port), and an input / output unit for inputting and outputting video information / signals, audio information / signals, data, and / or information input by a user.

[0076] For example, the device may be a mobile device such as a mobile robot, vehicle, train, manned / unmanned aerial vehicle (AV), or ship. In this case, the device may further include at least one of a drive unit comprising at least one of an engine, motor, power train, wheel, brake, and steering device of the device; a power supply unit that supplies power and includes a wired / wireless charging circuit, battery, etc.; a sensor unit that senses state information, environmental information, and user information of the device or its surroundings; an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting; and a position measurement unit that acquires position information of the moving body through a GPS (global positioning system) and various sensors.

[0077] For example, the device may be an XR device such as an HMD, a HUD (head-up display) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an input / output unit that acquires control information, data, etc. from the outside and outputs a generated XR object, and a sensor unit that senses state information, environment information, and user information of the device or the surroundings of the device.

[0078] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc., depending on the purpose or field of use. In this case, the device may further include at least one of a sensor unit that senses state information, environmental information, and user information of the device or its surroundings, and a drive unit that performs various physical actions, such as moving robot joints.

[0079] For example, the device may be an AI device such as a TV, projector, smartphone, PC, laptop, digital broadcasting terminal, tablet PC, wearable device, set-top box (STB), radio, washing machine, refrigerator, digital signage, robot, vehicle, etc. In this case, the device may further include at least one of an input unit that acquires various types of data from the outside, an output unit that generates output related to sight, hearing, or touch, a sensor unit that senses state information, environmental information, and user information of the device or its surroundings, and a training unit that learns a model composed of an artificial neural network using training data.

[0080] The structure of the wireless device illustrated in FIG. 3 may be understood as part of a terminal (or first node), or part of an intermediate point, or part of a base station (or second node). If the device illustrated in FIG. 3 is a base station (or second node), the device may further include a wired transceiver for front haul and / or back haul communication. If the front haul and / or back haul communication is based on wireless communication, at least one transceiver (206) illustrated in FIG. 3 is used for front haul and / or back haul communication, and a wired transceiver may not be included.

[0081] Communication procedures

[0082] FIG. 4 illustrates an exemplary communication procedure between a first node and a second node to which some examples of the present disclosure may be applied.

[0083] FIG. 4 illustrates the operation of a first node (110) (e.g., a terminal) and a second node (120) (e.g., a base station) transmitting and / or receiving data, and the operation performed prior to this.

[0084] In step S101, the first node (110) and the second node (120) can perform synchronization. For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect at least one synchronization signal transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal may include a plurality of synchronization signals (e.g., a primary synchronization signal, a secondary synchronization signal) classified according to structure or use. Through this, the terminal (110) can identify the boundaries of the frame, subframe, slot, and / or symbol of the base station (120) and obtain information about the base station (120) (e.g., a cell identifier).

[0085] In step S103, the first node (110) can obtain system information transmitted from the second node (120). For example, the system information is information related to the attributes, characteristics, and / or capabilities of the base station (120) required to connect to the base station (120) and use the service, and can be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., the channel used, whether it is provided on-demand), etc., and can be classified, for example, into a master information block (MIB) and a system information block (SIB). If necessary, the terminal (110) may transmit a signal requesting system information prior to receiving the system information. Such request and provision of system information may be performed after a random access procedure described later.

[0086] In step S105, the first node (110) and the second node (120) can perform a random access procedure. For example, the terminal (110) can transmit and / or receive at least one message for a random access procedure (e.g., a random access preamble, a RAR (random access response) message, etc.) based on information related to the random access channel of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of a supported preamble, etc.). For example, the terminal (110) may transmit a preamble (e.g., message 1 (MSG1)) through a random access channel, receive a random access response (RAR) message (e.g., message 2 (MSG2)), transmit a message (e.g., message 3 (MSG3)) containing information related to the terminal (110) (e.g., identification information) to the base station (120) using scheduling information included in the RAR message, and receive a message (e.g., message 4 (MSG4)) for contention resolution and / or connection establishment. As another example, MSG1 and MSG3 may be transmitted and received as a single message (e.g., message A (MSG A), or MSG2 and MSG4 may be transmitted and received as a single message (e.g., message B (MSG B).

[0087] In step S107, the first node (110) and the second node (120) can perform signaling of control information. For example, the control information may be defined in various layers, such as a layer that controls the connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transmission channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and signaling to indicate allocated resources.

[0088] In step S109, the first node (110) and the second node (120) can transmit and / or receive data. For example, the terminal (110) and the base station (120) can process data based on the signaling of control information and transmit and / or receive data. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. For example, when receiving data, the terminal (110) or the base station (120) can perform at least one of extracting a signal from a resource, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0089] 6G System Core Technology

[0090] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, free space optics (FSO) backhaul network, multiple input multiple output (MIMO) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.

[0091] artificial intelligence

[0092] The introduction of AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in machine-to-machine (M2M), machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0093] FIG. 5 illustrates an exemplary functional framework for AI operations to which some examples of the present disclosure may be applied.

[0094] Below, to provide a more specific explanation of AI (or AI / ML (machine learning)), terms can be defined as follows.

[0095] - Data collection: Data collected from network nodes, management entities, or terminals, serving as a basis for AI model training, data analysis, and inference.

[0096] - AI model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.

[0097] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent data and acquire an AI / ML model trained for inference.

[0098] - AI / ML Inference: A process of making predictions or deriving decisions based on collected data and an AI model using a trained AI model.

[0099] Referring to FIG. 5, the data collection function (10) is a function that collects input data and provides processed input data to the model training function (20) and the model inference function (30).

[0100] Examples of input data may include measurements from terminals or other network entities, feedback from actors, and outputs from AI models.

[0101] The data collection function (10) performs data preparation based on input data and provides the input data processed through data preparation. Here, the data collection function (10) does not perform specific data preparation (e.g., data pre-processing and cleaning, forming and transformation) for each AI algorithm, and can perform data preparation common to AI algorithms.

[0102] After the data preparation process is performed, the data collection function (10) can provide training data (11) to the model training function (20) and provide inference data (12) to the model inference function (30). Here, the training data (11) corresponds to data required as input for the AI ​​model training function (20), and the inference data (12) corresponds to data required as input for the AI ​​model inference function (30).

[0103] The data collection function (10) may be performed by a single entity (e.g., terminal, RAN node, network node, etc.) but may also be performed by multiple entities. In this case, training data (11) and inference data (12) from multiple entities may be provided to the model training function (20) and the model inference function (30), respectively.

[0104] The model training function (20) may correspond to a function that performs AI model training, validation, and testing, which can generate model performance metrics as part of the AI ​​model testing procedure. If necessary, the model training function (20) may also be responsible for data preparation (e.g., data pre-processing and cleaning, formatting and transformation, etc.) based on training data (11) provided by the data collection function (10).

[0105] Here, model deployment / update (13) can be used to initially deploy a trained, validated, and tested AI model to the model inference function (30) or to provide an updated model to the model inference function (30).

[0106] The model inference function (30) may correspond to a function that provides an AI model inference output (16) (e.g., a prediction or a decision). The model inference function (30) may provide model performance feedback (14) to the model training function (20) where applicable. Additionally, the model inference function (30) may be responsible for data preparation (e.g., data pre-processing and cleaning, formatting and transformation, etc.) based on the inference data (12) provided by the data collection function (10) if necessary.

[0107] Here, output (16) refers to the inference output of an AI model generated by the model inference function (30), and the details of the inference output may vary depending on the use case.

[0108] Model performance feedback (14) can be used to monitor the performance of the AI ​​model if available, and this feedback may be omitted.

[0109] The actor function (40) is a function that receives an output (16) from the model inference function (30) and triggers or performs a corresponding operation / action. The actor function (40) can trigger an operation / action on another entity (e.g., one or more terminals, one or more RAN nodes, one or more network nodes, etc.) or on itself.

[0110] Feedback (15) can be used to derive training data (11) and inference data (12), or to monitor the performance of the AI ​​model, the impact on the network, etc.

[0111] Meanwhile, the definitions of training, validation, and testing in data sets used in AI / ML can be distinguished as follows.

[0112] - Training data: Refers to the dataset used to train a model.

[0113] - Validation data: This refers to a dataset used to validate a model that has already been trained. Validation data typically refers to a dataset used to prevent overfitting of the training dataset. Additionally, validation data can refer to a dataset used to select the best model among the various models trained during the learning process. Therefore, validation can be viewed as a type of training.

[0114] - Test data: Refers to the dataset for final evaluation. This data is unrelated to training.

[0115] For example, within the entire dataset, training data and validation data can be divided in a ratio of approximately 8:2 or 7:3. Alternatively, within the entire dataset, training data:validation data:test data can be divided in a ratio of 6:2:2.

[0116] Depending on whether the base station and the terminal possess the capability for AI / ML functions, the cooperation level can be defined as follows, and variations resulting from the combination of multiple levels below or the separation of any one level are also possible.

[0117] Category 0a: This corresponds to a no collaboration framework. In this case, the AI / ML algorithm is based on pure implementation and may not require changes to the wireless interface.

[0118] Category 0b: Corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but lacks cooperation.

[0119] Category 1: This applies to cases involving inter-node support to improve the AI / ML algorithms of each node. For example, it applies when a terminal receives support from a base station (for training, adaptation, etc.), and vice versa. At this level, model exchange between network nodes is not required.

[0120] Category 2: This applies to cases where joint ML operations between a terminal and a base station can be performed. This level requires AI / ML model commands or exchanges between network nodes.

[0121] The functions exemplified in Figure 5 above may be implemented at RAN nodes (e.g., base station, TRP, base station CU, etc.), network nodes, network operator's OAM (operation administration maintenance), or terminals.

[0122] Alternatively, two or more entities among a RAN, a network node, a network operator's OAM, or a terminal may cooperate to implement the functions exemplified in FIG. 5. For example, one entity may perform some of the functions of FIG. 5, and another entity may perform the remaining functions. As such, some of the functions exemplified in FIG. 5 are performed by a single entity (e.g., a terminal, a RAN node, a network node, etc.), the transmission / provision of data / information between each function may be omitted. For example, if the model training function (20) and the model inference function (30) are performed by the same entity, the transmission / provision of model distribution / update (13) and model performance feedback (14) may be omitted.

[0123] Alternatively, any one of the functions exemplified in FIG. 5 may be performed by two or more entities among the RAN, network node, network operator's OAM, or terminal in collaboration. This may be referred to as a split AI operation.

[0124] FIG. 6 illustrates an example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0125] For example, the AI ​​model training function can be performed by network nodes (e.g., core network nodes, network operator's OAM, etc.), and the AI ​​model inference function can be performed by RAN nodes (e.g., base station, TRP, base station's CU, etc.).

[0126] Step 1: RAN Node 1 and RAN Node 2 can transmit input data (e.g., training data) for training an AI model to a network node. Here, RAN Node 1 and RAN Node 2 can also transmit data collected from terminals to the network node (e.g., terminal measurements related to RSRP (reference signal received power), RSRQ (reference signal received quality), and SINR (signal to interference-plus-noise ratio) of the serving cell and neighboring cells, terminal location, speed, etc.).

[0127] Step 2: Network nodes can train AI models using the received training data.

[0128] Step 3: The network node can distribute / update the AI ​​model to RAN Node 1 and / or RAN Node 2. RAN Node 1 (and / or RAN Node 2) may also continue model training based on the received AI model.

[0129] For the sake of convenience of explanation, it is assumed that the AI ​​model was deployed / updated only to RAN Node 1.

[0130] Step 4: RAN Node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN Node 2.

[0131] Step 5: RAN Node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

[0132] Step 6: If applicable, RAN node 1 can send model performance feedback to network nodes.

[0133] Step 7: RAN Node 1, RAN Node 2, and the terminal (or 'RAN Node 1 and the terminal', or 'RAN Node 1 and RAN Node 2') can perform an action based on the output data. For example, in the case of a load balancing action, the terminal may move from RAN Node 1 to RAN Node 2.

[0134] Step 8: RAN Node 1 and RAN Node 2 can transmit feedback information to network nodes.

[0135] FIG. 7 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0136] For example, both AI model training and AI model inference functions can be performed by RAN nodes (e.g., base station, TRP, base station's CU, etc.).

[0137] Step 1: The terminal and RAN node 2 can transmit input data (e.g., training data) for training an AI model to RAN node 1.

[0138] Step 2: RAN Node 1 can train an AI model using the received training data.

[0139] Step 3: RAN Node 1 can receive input data (e.g., inference data) for AI model inference from the terminal and RAN Node 2.

[0140] Step 4: RAN Node 1 can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

[0141] Step 5: RAN Node 1, RAN Node 2, and the terminal (or 'RAN Node 1 and the terminal', or 'RAN Node 1 and RAN Node 2') can perform an action based on the output data. For example, in the case of a load balancing action, the terminal may move from RAN Node 1 to RAN Node 2.

[0142] Step 6: RAN Node 2 can send feedback information to RAN Node 1.

[0143] FIG. 8 illustrates another example of operations related to AI model training and AI model inference to which some examples of the present disclosure may be applied.

[0144] For example, the AI ​​model training function may be performed by a RAN node (e.g., base station, TRP, base station CU, etc.), and the AI ​​model inference function may be performed by a terminal.

[0145] Step 1: A terminal can transmit input data (e.g., training data) for training an AI model to a RAN node. Here, the RAN node can collect data (e.g., terminal measurements related to RSRP, RSRQ, SINR of the serving cell and neighboring cells, terminal location, velocity, etc.) from various terminals and / or other RAN nodes.

[0146] Step 2: The RAN node can train an AI model using the received training data.

[0147] Step 3: The RAN node can distribute / update the AI ​​model to the terminal. The terminal may also continue model training based on the received AI model.

[0148] Step 4: Input data (e.g., inference data) for AI model inference can be received from terminals and RAN nodes (and / or other terminals).

[0149] Step 5: The terminal can perform AI model inference using the received inference data to generate output data (e.g., prediction or decision).

[0150] Step 6: If applicable, the terminal can transmit model performance feedback to the RAN node.

[0151] Step 7: The terminal and the RAN node can perform actions based on the output data.

[0152] Step 8: The terminal can transmit feedback information to the RAN node.

[0153] THz communication

[0154] Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz–300 GHz band range (sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz–3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz–3 THz band is part of the broadband, it lies at the boundary of the broadband and immediately following the RF band. Therefore, this 300 GHz–3 THz band exhibits similarities to RF.

[0155] FIG. 9 shows an electromagnetic spectrum to which some examples of the present disclosure may be applied.

[0156] Key characteristics of THz communication include (i) widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array technologies that can overcome range limitations.

[0157] When transmitting system information (e.g., MIB) of a cell in the THz frequency band, it can be inefficient because, in the case of high frequency bands, beam sweeping must be performed more frequently to cover the entire area of ​​the cell as the beam width becomes narrower. In particular, transmitting system information using this method is even more inefficient when there are not many users in the cell.

[0158] FIG. 10 illustrates an exemplary system information transmission / reception procedure to which some examples of the present disclosure may be applied.

[0159] The example of FIG. 10 is applicable not only to THz communication environments but also to 6G communication environments where THz communication is not applied. In addition, the procedure exemplified in FIG. 10 can be combined with various embodiments of the present disclosure described below. For example, embodiments described below can be performed based on system information obtained by the procedure exemplified in FIG. 10.

[0160] In step S1010, the second node (120) (e.g., a base station) can transmit system information of cell #1 through cell #2. For example, the base station provides at least two cells, cell #1 uses a THz frequency band, and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one of a system frame number (SFN) generated at a higher layer, a PDCCH configuration for SIB1, cell barring, cell re-selection, and subcarrier spacing, and may include at least one of a synchronization signal / PBCH (physical broadcast channel) block index generated at a physical layer. To this end, as an example, cell #1 and cell #2 may have a secondary cell and primary cell relationship.

[0161] In step S1030, the first node (110) (e.g., a terminal) can acquire synchronization for cell #1. Synchronization can be acquired by detecting a synchronization signal. Generally, synchronization is acquired prior to receiving system information, but since the system information of cell #1 is received in cell #2, the acquisition of synchronization for cell #1 can be performed after receiving system information. For example, the terminal can acquire synchronization based on system information. Alternatively, the acquisition of synchronization may be performed prior to step S1010.

[0162] In step S1050, the first node (110) may transmit a signal to connect to cell #1. For example, the signal may include a random access preamble. The structure of such a signal and the resource for transmitting the signal (e.g., a channel) may be identified through system information. Subsequently, in step S1070, the first node (110) and the second node (120) may perform a connection procedure to cell #1 and perform communication.

[0163] The procedure described with reference to FIG. 10 may be performed when the first node (110) first connects to cell #1 of the second node (120). Alternatively, a similar procedure may be performed when the first node (110) handovers to cell #1 of the second node (120). However, in the case of a handover, the system information of cell #1 may be received from a cell of a different base station other than cell #2 of the second node (120).

[0164] Communication in the THz band is expected to experience severe path loss, and to overcome this, terminals and base stations may be required to use very sharp beams. The use of sharp beams implies that terminals and base stations must perform beam control in addition to beamforming, meaning that a very large number of beams are utilized. Consequently, aligning the transmit and receive beams between the base station and the terminal takes a very long time. Furthermore, if the beam alignment between the base station and the terminal is disrupted due to the movement of the terminal, time is frequently required to realign the beams, which may lead to link instability.

[0165] FIG. 11 illustrates an exemplary beam management procedure to which some examples of the present disclosure may be applied.

[0166] Figure 11 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but this procedure is not limited to a THz environment and can also be applied in a 6G communication environment where THz communication is not applied.

[0167] Here, the term "beam" can be interpreted as other terms having equivalent technical meanings capable of distinguishing beams, such as "spatial domain filter," "spatial domain transmit filter," "spatial domain receive filter," reference signal (RS) resources for distinguishing beams, and SSB index.

[0168] In step S1110, the second node (120) (e.g., base station) may set resources for beam management to the first node (110) (e.g., terminal). Here, the resources may include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station may utilize a beam search signal (BSS) that is transmitted spatially separated from the existing downlink signal / channel for beam search. Here, the BSS may be transmitted based on a dedicated port for beam search. The dedicated port may be a port different from the port used for transmitting the existing downlink signal / channel (e.g., SSB, PDSCH (physical downlink shared channel), etc.). BSS is a term defined for convenience of explanation, and the technical concept according to the present embodiment is not limited to the term BSS itself. For example, a signal transmitted based on a dedicated port defined / set for beam search may be included in the technical concept according to the present embodiment.

[0169] In step S1130, the second node (120) (e.g., a base station) transmits measurement signals using multiple transmission beams. For example, the measurement signals may include at least one of a reference signal and a synchronization signal. At this time, the measurement signals may be transmitted as many times as the number of beams requiring measurement, and may be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, or a true time delay (TTD).

[0170] In step S1050, the first node (110) (e.g., a terminal) may transmit a feedback signal to the second node (120) (e.g., a base station). The feedback signal may indicate at least one beam selected by the terminal. The terminal may select at least one preferred beam based on the measurement signals received in step S1030.

[0171] In step S1070, the first node (110) and the second node (120) can perform communication. For example, the second node (120) can perform transmission to the first node (110) using the receiving beam of the first node (110) selected in step S1050. If channel reciprocity is established, the transmission beam of the first node (110) can also be determined through steps S1030 and S1050, so the transmission operation from the first node (110) can also be performed using a beam that has a reciprocity relationship with the beam selected in step S1050. If channel reciprocity is not established, a procedure including the transmission of measurement signal(s) by the first node (110) and the transmission of feedback signal(s) by the second node (120) may be performed first to determine the transmission beam of the first node (110).

[0172] Non-terrestrial networks (NTN)

[0173] FIGS. 12 and FIGS. 13 show examples of NTN scenarios to which some examples of the present disclosure may be applied.

[0174] NTN can represent a network or network segment that uses RF (radio frequency) resources mounted on a satellite (or UAS (unmanned aerial system) platform).

[0175] Figure 12 shows an example of a typical scenario of an NTN based on a transparent payload, and Figure 13 shows an example of a typical scenario of an NTN based on a regenerative payload.

[0176] Referring to FIG. 12, the satellite (or UAS platform) can establish a service link with a terminal. The satellite (or UAS platform) can be connected to a gateway via a feeder link. The satellite can be connected to a data network via the gateway. A beam footprint may refer to an area where signals transmitted by the satellite can be received.

[0177] Referring to FIG. 13, a satellite (or UAS platform) can establish a service link with a terminal. The satellite (or UAS platform) connected to the terminal can be connected to another satellite (or UAS platform) via inter-satellite links (ISL). Another satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on a regenerated payload, the satellite can be connected to a data network via another satellite and a gateway. If no ISL exists between the satellite and another satellite, a feeder link between the satellite and the gateway may be required.

[0178] FIGS. 12 and 13 are merely examples of NTN scenarios, and NTN can be implemented based on various scenarios. For example, a satellite (or UAS platform) can implement a transparent or regenerative (with on-board processing) payload. For example, a satellite (or UAS platform) can generate multiple beams across a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) may vary depending on the on-board antenna diagram and the minimum elevation angle.

[0179] For example, the transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may not be altered.

[0180] For example, the regeneration payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, the regeneration payload may be substantially the same as carrying all or part of the base station functions on a satellite (or UAS platform).

[0181] Integrated Sensing and Communication (ISAC)

[0182] Wireless sensing is a technology that utilizes radio frequencies to determine the instantaneous linear velocity, angle, distance (or range) of an object, thereby obtaining information about the characteristics of the environment and / or objects within that environment. Since radio frequency sensing capabilities do not require connecting to objects via devices within a network, they can provide services for determining object locations without the need for devices. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection and recognition (e.g., vehicles, humans, animals, UAVs), as well as high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing may utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, such as sensing operations, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks to wireless communication and sensing networks.

[0183] FIG. 14 shows examples of sensing operations to which some examples of the present disclosure may be applied.

[0184] Specifically, FIG. 14(a) illustrates an example of monostatic sensing operation using a sensing receiver and a sensing transmitter located at the same position. FIG. 14(b) illustrates an example of bistatic sensing operation using a sensing receiver and a sensing transmitter located at separate positions. A sensing receiver receives a signal that is reflected or scattered by a sensing object from a sensing signal transmitted from a sensing transmitter, and can extract or acquire sensing data based on the received signal. A sensing result can be generated or determined through appropriate processing of this sensing data. The sensing result can be provided to a trusted third-party entity or service outside the 3GPP system via an entity or service within the 3GPP system.

[0185] Network Energy Saving (NES)

[0186] Energy conservation in base stations is considered important in wireless communication systems, including 3GPP, because it can contribute to building eco-friendly networks by reducing carbon emissions and lowering the operational expenditure (OPEX) of telecommunication operators. In particular, as the introduction of 5G communication requires high transmission rates, base stations must be equipped with a larger number of antennas and provide services through wider bandwidths and frequency bands. Consequently, according to recent studies, the energy cost of base stations has reached the level of 20% of total OPEX. For example, in 5G wireless communication systems, various technologies for reducing energy consumption are being discussed under the name NES (network energy savings).

[0187] With the application of NES technology, the base station can perform operations such as controlling on / off for a certain duration in the time axis, controlling transmission and reception resources for terminal-common or terminal-specific signals / channels, changing the amount of resources in the frequency axis, controlling transmission power, or turning on / off antenna ports, TRPs (transmission-reception points), etc. in the spatial domain.

[0188] For example, the base station can identify the NES solution(s) to be applied, perform signaling for the NES, and perform operations on the NES.

[0189] NES solution(s) may relate to the control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. Which NES solution(s) to apply may be adaptively selected based on the current situation (e.g., cell load level, characteristics of connected terminals, etc.) or may be predefined.

[0190] A base station that has identified the NES solution(s) performs signaling for the NES. The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information regarding the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of NES operation to at least one terminal. Additionally, the base station may receive capability information related to the NES from at least one terminal.

[0191] Based on signaled NES-related information, the base station can perform operations for the NES. For example, depending on system information, configuration information, and control information transmitted via signaling, the base station can turn the transmission and reception of specific signals on or off, turn elements of the spatial domain on or off, or adjust resources for the transmission and reception of measurement signals.

[0192] Examples of NES solutions that can be implemented through this procedure are as follows.

[0193] Intra-system energy saving: A RAN node may request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).

[0194] Inter-system energy saving: An NG-RAN node owning a capacity booster cell can autonomously switch the cell to an inactive state.

[0195] SSB-less cell: When no SSB or SMTC (SSB-based RRM (radio resource management) measurement timing configuration) setting is provided for a specific cell (e.g., secondary cell (SCell) or primary cell (PCell))(s), the terminal may obtain timing reference and automatic gain control (AGC) sources from other serving cells. In frequency range 1 (FR1) or FR2, the base station may establish intra-band carrier aggregation (CA) or inter-band CA that includes cells without SSB transmission, in which case SSB / SIB transmission may be triggered by the terminal's wake-up signal (WUS). Accordingly, the period of common channels / signals such as SSB is increased, so the base station may remain in a sleep state for a longer time.

[0196] Cell DTX (discontinuous transmission) / DRX (discontinuous reception): To reduce the downlink transmission / uplink reception activity time of a base station, periodic cell DTX / DRX patterns (e.g., active and inactive periods) may be set commonly for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern may be set and activated separately, and up to two cell DTX / DRX patterns may be set per MAC entity. When cell DTX is set and activated, at least one of monitoring for semi-persistent scheduling (SPS) opportunities or monitoring for PDCCH may be suspended during the cell DTX inactive period. When cell DRX is set and activated, at least one of transmission from configured grant (CG) resources or scheduling request (SR) transmission may be suspended during the cell DRX inactive period. Cell DTX / DRX can be enabled / disabled through RRC signaling or L1 (layer 1) group common signaling.

[0197] Parameters such as active duration and cycle may be set for Cell DTX / DRX. Active duration is the period during which a terminal waits to transmit an SR or CG after receiving a PDCCH or SPS opportunity, and cycle may specify the periodic repetition of active duration and inactive duration. When both Cell DTX and Cell DRX are set, parameters such as active duration and cycle may be common. If the base station recognizes an emergency call or public safety-related service (e.g., Multimedia Priority Service (MPS) or Mission Critical Service (MCS)), the network may release or disable the Cell DTX / DRX settings so as not to affect the service. Additionally, at least some overlap may be required between the active period of the terminal's connected mode DRX and the active period of the Cell DTX / DRX. For example, the period of the terminal's connected mode DRX may be a multiple of the Cell DTX / DRX period, or vice versa.

[0198] Conditional Handover (CHO): A CHO procedure performed in such a manner that the execution of a handover is determined by the terminal may be used while NES technology is applied (e.g., when a cell enables or disables the cell DTX / DRX). In this case, the terminal may use an NES-specific CHO event to execute a CHO for a candidate cell, and as an additional triggering condition for this, the reception of a DCI that enables CHO condition(s) set as an NES event indication may be applied.

[0199] Spatial and power domain adaptation: To support the base station for transceiver muting and / or transmit power adaptation, the terminal may be configured to report multiple CSI quantities in the CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset between a data channel (e.g., PDSCH) and CSI-RS. Depending on the application of the spatial and power domain adaptation solution, CSI configuration, measurement, and / or reporting behavior may be affected.

[0200] Cell DTX / DRX

[0201] To operate the base station in sleep mode for a relatively long period without frequent wake-ups, the base station's DTX / DRX was introduced for NES purposes. By configuring the cell DTX and setting the on-duration of the terminals' C-DRX within the active period of the cell DTX, the base station can reduce energy consumption by utilizing DTX transmission under low system load conditions.

[0202] FIG. 15 illustrates an example of a cell DTX / DRX operation to which some examples of the present disclosure may be applied.

[0203] The second node (120) (e.g., a base station) can transmit system information to the first node (110) (e.g., a terminal). Accordingly, the first node (110) can check information related to the cell DTX / DRX of the second node (120).

[0204] For example, system information may include MIB, SIB1, etc. In relation to NES technology, MIB may include information related to cell barring (e.g., cellBarred), and SIB1 may include information related to the cell barring state (e.g., cellBarredNES). For example, if cellBarred included in MIB is set to a value indicating that it is not barred (e.g., notBarred), the terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX. For example, if cellBarred included in the received MIB is set to a value indicating that the cell is barred (e.g., barred), a terminal that does not support NES cell DTX / DRX may determine that the cell is barred.

[0205] For example, if a terminal has the capability to support NES cell DTX / DRX, the terminal can check SIB1 to determine the cell blocking status. For example, if cellBarred in the MIB is set to barred and cellBarredNES is absent in SIB1, a terminal supporting NES cell DTX / DRX can treat the cell as blocked and perform cell-reselection to another cell. For example, if cellBarred in the MIB is set to barred and cellBarredNES is included in SIB1, a terminal supporting NES cell DTX / DRX can determine that the cell is not blocked.

[0206] In the example of FIG. 15, it is assumed that the terminal has the capability to support NES cell DTX / DRX, and that cellBarred in the MIB is set to notBarred or cellBarred in the MIB is set to barred, and cellBarredNES is included in SIB1. Accordingly, the terminal can perform a random access procedure to connect to the base station and then perform communication. For example, the base station can perform a cell DTX / DRX operation and transmit configuration information related to the cell DTX / DRX operation to the terminal. The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include at least one of, for example, an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). In addition, the configuration information may further include information for receiving and interpreting control information related to cell DRX / DRX (e.g., DCI-related information such as cellDTRX-RNTI included in physicalCellGroupConfig, size of DCI format 2_9, etc.).

[0207] Subsequently, the base station may transmit control information related to cell DTX / DRX to the terminal. The control information related to cell DTX / DRX may include DCI having a specified format (e.g., DCI format 2_9). When an operation for a serving cell according to at least one of cell DTX operation and cell DRX operation is configured by configuration information (e.g., cellDTXDRX-Config included in secvingcell-config), the terminal may identify a set of search spaces (e.g., Type3-PDCCH CSS set) for monitoring a PDCCH that transmits control information of the specified format during the active time through a higher-level parameter (e.g., SearchSpace included in PDCCH-Config), and obtain the location of information regarding the serving cell within the control information through a higher-level parameter (e.g., positionInDCI-cellDTRX included in SecvingCell-config). Then, the terminal may obtain the control information based on the identified set of search spaces and location.

[0208] Control information related to cell DTX / DRX may be used to indicate the activation or deactivation of cell DTX and / or cell DRX, and / or to provide NES-mode indicators (e.g., NES-specific CHO execution conditions, etc.), and may include, for example, at least one block including cell DTX / DRX indicators and NES-mode indicators. In this case, if the serving cell is set as a supplementary uplink (SUL) carrier, the instruction to activate or deactivate cell DRX by the cell DTX / DRX indicator may be applied to both the uplink (UL) carrier and the SUL carrier.

[0209] Subsequently, the terminal and the base station can communicate based on the cell DTX / DRX. Specifically, the base station can turn the transmission and reception of signals on or off according to the settings related to the cell DTX / DRX, and accordingly, the terminal can selectively monitor signals from the base station. During the DTX-OFF duration, the base station can enter sleep mode to reduce energy consumption. For example, the base station DTX cycle can be aligned with the terminal DRX cycle. The base station DTX-ON duration can fully cover the terminal's DRX-ON duration. Furthermore, for NES purposes, the base station can align transmissions on Xn (interface between base stations) / NG (interface between 5G RAN and 5G core network) with transmissions on Uu (interface between terminal and network). The DTX / DRX mechanism triggers the switching of reference signal resource set groups, and the base station may perform dormancy-like behavior of infrequently transmitting or not transmitting SSB, SIB, and CSI-RS to reduce energy consumption. Depending on the base station's configuration, the terminal may infrequently receive or not receive downlink signals / channels. Once the base station DTX / DRX operation is triggered, during the DTX / DRX OFF duration, the terminal may receive the corresponding CSI-RS, SSB, or PDCCH discontinuously.

[0210] SSB-less cell

[0211] FIG. 16 illustrates an example of a carrier aggregation (CA) operation including an SSB-free cell to which some examples of the present disclosure may be applied.

[0212] In the example of Fig. 16, it is assumed that the SSB-free cell is a SCell in CA, but the SSB-free cell may also be a PCell in CA.

[0213] A second node (120) (e.g., a base station) can transmit configuration information for a SCell to a first node (110) (e.g., a terminal). For example, the base station can transmit configuration information for CA to provide services to the terminal through CA operation. Here, the CA operation may be intra-band CA or inter-band CA. For example, the configuration information for a SCell may include information containing information for adding a SCell (e.g., sCellToAddModList), and specifically, may include a cell index, a physical cell identifier, information related to DL-UL settings, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Accordingly, the terminal can determine the settings for CA operation and perform communication using the base station's PCell and SCell.

[0214] For example, the terminal can verify that the SCell is an SSB-less SCell based on information related to the downlink frequency included in the configuration information, and can verify the relevant parameters. For example, the terminal can determine that the SCell is an SSB-less SCell by verifying the existence of a parameter indicating that it is an SSB-less SCell (e.g., SSBlessSCell), and can verify the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the example of FIG. 16, the reference cell may be a PCell. Therefore, the terminal can use the PCell as a timing reference and AGC source for communication in the SCell. For example, the reference of the SSB-less cell may be (another) cell, TRP, CORESET pool (control resource set pool), (additional) PCI (physical cell ID), etc.

[0215] Conditional Handover (CHO)

[0216] FIG. 17 illustrates an example of a conditional handover operation to which some examples of the present disclosure may be applied.

[0217] The order of the operations exemplified in Fig. 17 may vary depending on the case.

[0218] A second node (120) (e.g., a base station) may transmit configuration information for a CHO to a first node (110) (e.g., a terminal). The configuration information for a CHO may include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList) and information related to configuration for reporting (e.g., ReportConfigNR). For example, information related to configuration for reporting may include information related to events related to reporting, identifiers of events (e.g., condEventId), information indicating whether it is an NES-specific CHO event (e.g., nesEvent), etc. In the example of FIG. 17, it is assumed that event information indicating that it is an NES-specific CHO event is received.

[0219] The base station may transmit information to the terminal that enables NES-specific CHO execution conditions. The information that enables NES-specific CHO execution conditions may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information that enables NES-specific CHO execution conditions may be referred to as an NES-mode indicator, and may indicate that NES-specific CHO execution conditions are enabled, for example, as 1-bit information, if the relevant upper layer parameter (e.g., nesEvent) is set and the serving cell of the relevant block in the corresponding DCI is the primary cell.

[0220] Subsequently, the terminal may perform a measurement and transmit the measurement report to the base station. The base station may determine the CHO based on the measurement report and perform signaling for a handover request with the adjacent / neighboring base station(s) indicated by the measurement report. The base station may determine the adjacent base station(s) that have affirmed admission through signaling as candidate base station(s) and transmit information about the candidate base station(s) to the terminal. Accordingly, the terminal may evaluate the CHO execution conditions for the candidate base station(s). Based on the evaluation results, if a candidate cell satisfying the conditions is determined, the terminal may perform detachment from the previous / old cell and perform synchronization for the new cell.

[0221] For example, based on event information indicating that the event received by the terminal in the previous procedure is an NES-specific CHO event, and information enabling the NES-specific CHO execution condition, the terminal can determine whether the event is satisfied. For example, if an NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information indicating that the event is an NES-specific CHO event (e.g., nesEvent), the terminal can determine that the event associated with the corresponding measurement identifier (e.g., measId) is satisfied, and accordingly, determine that the CHO execution condition is satisfied.

[0222] Channel Status Information (CSI) Measurement and Reporting

[0223] FIG. 18 illustrates an example of a procedure for CSI measurement and reporting to which some examples of the present disclosure may be applied.

[0224] The second node (120) (e.g., base station) can transmit configuration information for CSI to the first node (110) (e.g., terminal). The configuration information for CSI may include information related to a reference signal (e.g., CSI-RS) resource or resource set for CSI (e.g., time-frequency resource information, sequence information, power information, etc.), information related to CSI reporting (e.g., quantity information, report type information, report resource information, codebook information, etc.), information related to CSI measurement, etc.

[0225] For example, to assist the base station with base station transceiver muting and / or transmit power adaptation, the terminal may be configured to report multiple CSI entries in a CSI report based on multiple sub-configs. For example, each sub-config may correspond to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset. In relation to CSI reporting, a higher-level parameter included in the configuration information (e.g., CSI-ReportConfig) may include a list of sub-configs, and each sub-config may be identified by an identifier (e.g., csi-ReportSubConfigID). For example, each sub-setting may correspond to a list of at least one CSI-RS resource, a subset of CSI-RS antenna ports, and / or power-related parameters of the CSI-RS resource(s) (e.g., power control offset related parameters (e.g., powerControlOffset) and / or power offset for PDSCH related to CSI-RS).

[0226] For example, an information element (IE) for a list of aperiodic trigger states for CSI may include a trigger list parameter for a CSI reporting sub-setting. This parameter may include a list of sub-setting ID(s) of N sub-setting(s) out of L configured sub-settings within a CSI reporting setting associated with a triggering state for an aperiodic CSI reporting on an uplink data channel (e.g., PUSCH (physical uplink shared channel)).

[0227] For example, an IE for a CSI reporting configuration may include a parameter for a list of CSI reporting sub-configuration ID(s) to be added, modified, or released. A list of port subset indicators and non-zero power (NZP) CSI-RS resources may not be configured simultaneously in the same CSI reporting configuration.

[0228] For example, IE for CSI reporting sub-settings may include port-subset indicator parameters, NZP CSI-RS resource list parameters, and power offset parameters.

[0229] The port-subset indicator parameter may indicate the number of ports of NZP CSI-RS resources indicated in the NZP CSI-RS resource list (the value being equal to the number of ports of the corresponding NZP CSI-RS resources) and a (sub)set of CSI-RS antenna ports used for CSI calculation of the sub-configuration. Each bit in the bit string of the port-subset indicator corresponds to an antenna port, and if any bit is set to 1, the corresponding port may be enabled for CSI calculation corresponding to the sub-configuration, and if any bit is set to 0, the corresponding port may not be enabled for CSI calculation corresponding to the sub-configuration.

[0230] The NZP CSI-RS resource list parameter may indicate a list of NZP CSI-RS resources for a sub-setting that is a (sub)set of NZP CSI-RS resource(s) of a set of CSI-RS resources for channel measurements connected to the sub-setting of the CSI reporting setting. Values ​​0, 1, 2, ... may mean the first, second, third, ... NZP CSI-RS resources of the set of CSI-RS resources.

[0231] When the power offset parameter is set for an NZP CSI-RS resource, it may indicate that a power offset between the PDSCH RE (resource element) and the NZP CSI-RS RE is applied by the difference between the value of the power offset parameter and the value of the power control offset parameter.

[0232] When a configuration for CSI includes multiple sub-configurations, the terminal may determine CSI-RS resources, CSI-RS port mapping, power offset, codebook type, report items, etc., by considering the sub-configurations when interpreting the configuration information for CSI. When configuration information related to CSI reporting that includes sub-configurations (e.g., CSI-ReportConfig) is provided to the terminal, the terminal may not expect that a higher-level parameter related to a report item (e.g., reportQuantity) is set to 'cri-RSRP', 'cri-SINR', 'cri-SINR-Index', 'cri-RSRP-Index', 'none', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', 'ssb-Index-SINR-Index', or 'tdcp' (where CRI corresponds to the CSI-RS resource index and tdcp corresponds to time domain channel properties). Additionally, if the type of CSI report is set to semi-persistent CSI report or aperioditic CSI report, the base station may activate / trigger only some of the sub-settings configured for the terminal via MAC-CE (control element) or DCI (downlink control information). For example, the trigger state of the aperioditic CSI report may be set as needed, and the activation of the semi-persistent CSI report may be controlled by an activation command.

[0233] For example, regarding the setting of a report quantity, the terminal may determine CSI-RS port index(s) for each CSI-RS resource based on information related to a port-subset per sub-setting (hereinafter referred to as 'port-subset indicator'). The port-subset indicator may include a bitmap for specifying some of the antenna ports for the corresponding CSI-RS resource. Thus, the terminal may identify at least one antenna port for the corresponding sub-setting based on the positions of bits set to a positive value (e.g., 1) in the port-subset indicator.

[0234] For example, regarding the settings for a report quantity, the terminal can determine the codebook type based on the existence of sub-settings. Specifically, if sub-settings are configured for a CSI report, the terminal may exclude the configuration of at least one codebook type. For example, if the terminal's capability supports it, the corresponding at least one codebook type may be configured.

[0235] For example, regarding the settings for report quantities, a power offset value and an NZP CSI-RS resource set may be set for each sub-setting. For example, depending on whether a power offset value and an NZP CSI-RS resource set are set for each sub-setting, the interpretation of the NZP CSI-RS resource set for each sub-setting may vary.

[0236] In determining the CQI (channel quality indicator), a higher-level parameter related to the time limit for channel measurements (e.g., timeRestrictionForChannelMeasurements) may be set. In this case, the terminal can derive a channel estimate to determine the CSI based on the most recent CSI reference resource. For example, if Cell DTX for the base station is enabled, the Cell DTX activation time may be considered to determine the CSI reference resource.

[0237] The CSI is derived based on the CSI reference resource. The CSI reference resource is defined as a group of downlink physical resource blocks corresponding to the bands related to the CSI derived in the frequency domain, and is defined as a single downlink slot determined in the time domain based on upper-layer parameters and subcarrier spacing. The terminal may transmit the CSI report no later than the CSI reference resource after receiving the CSI-RS. For example, if sub-configurations are configured for the CSI report, the CSI reference resource may be considered for each sub-configuration.

[0238] When configured to report at least one of the CQI index, PMI (precoding matrix index), and RI (rank indicator), in a CSI reference resource, the terminal may assume specific values ​​for the symbol location and number occupied in control signaling, the number of PDSCH and DMRS (demodulation reference signal) symbols, the subcarrier spacing of the BWP (bandwidth part), the bandwidth for CQI reporting, the CP (cyclic prefix) length and subcarrier spacing of the reference resource, and the RV (redundancy version), for the purpose of deriving at least one of the CQI index, PMI, and RI. In this case, if sub-settings are configured for CSI reporting, assumptions regarding the antenna port, EPRE (energy per resource element), etc., may be determined based on the sub-settings.

[0239] Based on the configuration as described above, the base station may transmit at least one CSI-RS to the terminal. Based on the configuration as described above, the terminal may receive at least one CSI-RS and perform a measurement thereon. For example, at least one CSI-RS may be transmitted through a CSI-RS resource or resource set configured by the configuration information.

[0240] When the terminal is configured for DRX (discontinuous reception), the terminal may perform measurements as follows. For example, if the terminal is configured to monitor power saving-related control information (e.g., DCI format 2_6) and, in a situation where the DRX-related timer (e.g., drx-onDurationTimer) is not started by the upper layer parameter (e.g., ps-TransmitOtherPeriodicCSI), and is configured to report CSI using a reporting configuration type set to periodic reporting and a reporting item set to an item other than cri-RSRP and ssb-index-RSRP, the most recent CSI measurement opportunity occurs during the time indicated by drx-onDurationTimer in the DRX-related configuration information (e.g., DRX-Config), in addition to the DRX active time or the DRX active time for the CSI to be reported. As another example, if the terminal is configured to monitor power saving-related control information (e.g., DCI format 2_6) and, under conditions where drx-onDurationTimer is not initiated by a higher-level parameter (e.g., ps-TransmitPeriodicL1-RSRP), is configured to report L1-RSRP using a report setting type configured for periodic reporting and a report item configured for cri-RSRP, the most recent CSI measurement opportunity occurs during the time indicated by drx-onDurationTimer within the DRX-related setting information (e.g., DRX-Config), excluding the DRX active time or the DRX active time for the CSI to be reported. Additionally, the most recent CSI measurement opportunity occurs within the DRX active time for the CSI to be reported.

[0241] The base station may perform cell DTX and / or cell DRX operations. In this case, during the non-active period of the cell DTX, the terminal configured as the cell DTX may not expect to receive periodic CSI-RS and semi-static CSI-RS, which are configured in the CSI reporting configuration associated with a reporting item including at least RI. When the cell DTX is activated for the serving cell, the most recent CSI measurement opportunity of the semi-static CSI-RS resource or periodic CSI-RS resource may occur within the active periods of the cell DTX for CSI reporting, which are configured by the configuration information (e.g., CSI-ReportConfig) associated with the CSI reporting associated with a reporting item including at least RI.

[0242] A terminal that has received at least one CSI-RS can determine the CSI. For example, the terminal can perform a CSI calculation. The terminal can perform a CSI calculation based on CSI processing criteria. The terminal can indicate the number of supported concurrent CSI calculations, for example, the number of concurrently run CSI processing units (CPUs), which is the NCPU. The terminal can determine the number of CPUs for the corresponding CSI report based on at least one of the NCPU, the number of CPUs for each CSI report, the number of currently occupied CPUs, and the settings of the report item. For example, for configuration information related to CSI reporting (e.g., CSI-ReportConfig) containing a report item parameter (e.g., reportQuantity) that is not set to 'none', the CPU(s) may be occupied for at least one OFDM (orthogonal frequency division multiplexing) symbol, wherein the number of at least one symbol may be determined based on the CSI-RS resource or CSI-IM (interference measurement) resource associated with the sub-configurations.

[0243] If configuration information related to CSI reporting (e.g., CSI-ReportConfig) includes multiple sub-configurations, the number of CPUs occupied by CSI reporting may be determined based on the number of CSI-RS resources corresponding to the sub-configurations. For example, the number of CSI-RS resources may be determined based on the number of times the configuration information related to CSI reporting (e.g., CSI-ReportConfig) is referred or the number of sub-configurations referencing the CSI-RS resources.

[0244] A terminal that has determined the CSI may transmit a CSI report to a base station. The terminal may transmit CSI(s) for at least one sub-configuration according to a report item parameter (e.g., reportQuantity) configured for configuration information related to the CSI report (e.g., CSI-ReportConfig). For example, the CSI report may include at least one of PMI, CQI, RI, CRI, SSBRI (SSB resource index), LI (layer indicator), and RSRP. In this case, the CSI report may include a Part 1 CSI report and a Part 2 CSI report. Additionally, the CSI report may be transmitted via at least one of a PUCCH (physical uplink control channel) or a PUSCH.

[0245] When a terminal multiplexes CSI reports containing Part 2 CSI reports to a PUCCH resource, the terminal determines the number of physical resource blocks (PRBs) or Part 2 CSI reports for the PUCCH resource and the PUCCH resource, assuming that each CSI report or each CSI sub-report included in the CSI report indicates Rank 1 or a Rank combination {1, 1}. When a higher-level parameter related to the CSI report mode (e.g., csi-ReportMode) is set to 'Mode2', the terminal determines the number of PRBs or Part 2 CSI reports for the PUCCH resource and the PUCCH resource, assuming that each CRI of the CSI report is associated with a resource pair.

[0246] If a CSI report in PUSCH contains two parts, the terminal may omit part of the Part 2 CSI. The omission of the Part 2 CSI follows the priority order. Except where the corresponding CSI report contains at least one CSI sub-report including Part 2 that corresponds to a sub-configuration from a list of sub-configurations provided by a higher-level parameter (e.g., csi-ReportSubConfigList) included in the information related to the CSI report (e.g., CSI-ReportConfig), if the terminal omits Part 2 CSI information for a specific priority level, the terminal must exclude all information for that priority level.

[0247] For report configurations related to information (e.g., CSI-ReportConfig) containing a list of sub-configurations for a CSI report, the following processing is possible. For a corresponding CSI report containing at least one CSI sub-report, the omission of Part 2 CSI is performed at the sub-configuration level within the same priority level. Here, the sub-configuration having a lower index value has a higher priority.

[0248] If a CSI report consists of two parts, the terminal may omit part of the Part 2 CSI. The omission of the Part 2 CSI follows the priority order. For a given CSI report containing at least one CSI sub-report, the omission of the Part 2 CSI may be applied according to the CSI reporting procedure using PUSCH, for a report configuration related to information (e.g., CSI-ReportConfig) containing a list of sub-configurations related to the CSI report. The Part 2 CSI may be omitted starting from the lowest priority level up to a Part 2 CSI code rate that is less than or equal to the code rate set by the upper-level parameter (e.g., maxCodeRate).

[0249] Additionally, if a CQI request (or CSI request) field within a DCI triggers CSI report(s) in a PUSCH, the first uplink symbol carrying the CSI report(s) may not precede a symbol specified after a certain interval from the last symbol of the PDCCH carrying the DCI. Accordingly, the CSI calculation time may be guaranteed. For example, if multiple sub-configurations are configured for a CSI report, the starting position of the aforementioned interval may be determined based on all triggered sub-configurations.

[0250] CSI is transmitted via PUCCH or PUSCH and can be represented as a bit sequence of a fixed size. When CSI is transmitted via PUCCH, if a parameter (e.g., csi-ReportSubConfig) specifying sub-configuration settings for the CSI report is configured, the mapping order of CSI fields for each CSI sub-report can be applied according to a predefined rule.

[0251] When a CSI is transmitted via PUSCH, if a parameter (e.g., csi-ReportSubConfig) that specifies settings per sub-configuration for the CSI report is configured, the mapping order of CSI fields for each CSI sub-report can be applied according to a predefined rule.

[0252] Some or all of the examples of FIGS. 1 to 18 described above may be combined with some or all of the examples of the present disclosure described below, and such combined examples are included within the scope of the present disclosure.

[0253] On-demand SSB transmission and reception procedure

[0254] In basic communication systems, base stations were defined to periodically and continuously transmit SSBs for purposes such as time / frequency synchronization and / or radio resource management (RRM). In other words, base stations were defined to transmit SSBs even when there was no data to transmit or receive, which led to the problem of unnecessary energy consumption.

[0255] Accordingly, energy consumption can be reduced by the base station transmitting an SSB to a terminal on a specific cell according to the on-demand SSB procedure, and not transmitting an SSB to a terminal from a specific cell when the on-demand SSB procedure is not applied. That is, the base station's energy consumption can be reduced by performing SSB transmission only when the on-demand SSB procedure is applied or involved.

[0256] The on-demand SSB process can be triggered based on at least one of the operations described below:

[0257] 1) An operation in which a terminal transmits a request for SSB transmission to a base station via an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS, etc.),

[0258] 2) An operation in which Base Station #1 (or TRP #1) requests SSB transmission to Base Station #2 (or TRP #2) via an inter-base station interface (e.g., Xn interface, etc.) or backhaul signaling, etc.

[0259] 3) An operation in which the base station signals whether to transmit an SSB for the corresponding SCell by transmitting SCell enable / disable signaling to the terminal.

[0260] The on-demand SSB operation (on PCell or / and SCell) and related information described below may apply not only to terminals in connected mode but also to terminals in inactive (or idle) mode or terminals performing initial connection. That is, the on-demand SSB operation (on PCell or / and SCell) may apply not only to terminals of basic wireless communication systems but also to terminals of next-generation communication systems.

[0261] Additionally, the on-demand SSB operation applied to the CA (carrier aggregation) containing the SCell may also be applied to intra-band CA or inter-band CAD. The SSB on the SCell transmitted through the on-demand SSB process may be used for at least time / frequency synchronization, L1 / L3 measurements, and SCell activation procedures.

[0262] On-demand system information (e.g., SIB1) or SSB transmission procedure

[0263] In basic wireless communication systems, for a terminal in initial access or idle mode to connect to a cell, the terminal was defined to always periodically transmit system information (e.g., SIB1), which includes system information and random access information, to the terminal. In other words, the base station was defined to transmit system information even when there was no data to transmit or receive, which resulted in the problem of unnecessary energy consumption.

[0264] Accordingly, the base station can reduce energy consumption by transmitting the SIB1 for a specific cell to the terminal through the on-demand SIB1 process and not transmitting the SIB1 for a specific cell to the terminal when the on-demand SIB1 procedure is not applied.

[0265] As an example of the present disclosure, the terminal may trigger the base station's SIB1 transmission by transmitting an uplink signal / channel (e.g., PRACH, etc.) to the base station, and at least one of the scenarios described below may be applied.

[0266] Scenario 1: As illustrated in FIG. 19(a), the terminal may recognize that SIB1 is not being transmitted in Cell #1 by receiving an SSB (and / or other downlink signaling channel) from the base station in Cell #1. The transmission of SIB1 may be triggered by the terminal transmitting a signal requesting SIB1 to the base station based on information provided via the SSB (and / or other downlink signaling channel) and / or predetermined information. For the purposes of describing this disclosure, the signal requesting SIB1 may be collectively referred to as a WUS (wake-up signal), but is not limited thereto. Upon receiving the WUS, the base station may transmit a specific DL signal / channel (e.g., an ACK signal) on Cell #1 to the terminal in response to the WUS. Additionally or alternatively, the base station may transmit SIB1 on Cell #1 to the terminal (without a specific DL signal / channel) in response to the WUS.

[0267] Scenario #2: As illustrated in FIG. 19(b), the terminal may recognize that SIB1 is not being transmitted in Cell #2 by receiving an SSB (and / or other downlink signaling channel such as SIB1) from the base station in Cell #1. The terminal may attempt camp-on in Cell #2. The terminal may trigger the transmission of SIB1 for Cell #2 by transmitting a signal (e.g., WUS) requesting SIB1 from Cell #1 to the base station based on information provided via the received SSB (and / or other downlink signaling / channel such as SIB1) and / or predetermined information. Upon receiving the WUS, the base station may transmit a specific DL signaling / channel (in Cell #1 or Cell #2) to the terminal in response to the WUS. Additionally, or alternatively, the base station may transmit SIB1 for Cell #2 (without a specific DL signaling / channel) to the terminal in response to the WUS in Cell #1 or Cell #2.

[0268] Scenario #3: As illustrated in FIG. 19(c), the terminal may recognize that SIB1 is not being transmitted in Cell #2 by receiving an SSB (and / or other downlink signaling channel such as SIB1) from the base station in Cell #1. The terminal may attempt camp-on in Cell #2. Transmission of SIB1 for Cell #2 may be triggered by the terminal transmitting a signal (e.g., WUS) requesting SIB1 on Cell #2 to the base station based on information provided through the received SSB (and / or other downlink signaling / channel such as SIB1) and / or predetermined information. Upon receiving the WUS, the base station may transmit a specific DL signaling / channel (in Cell #1 or Cell #2) to the terminal in response to the WUS. Additionally, or alternatively, the base station may transmit SIB1 for Cell #2 to the terminal on Cell #1 or Cell #2 (without a specific DL signaling / channel) in response to the WUS.

[0269] As another example, base stations can reduce energy consumption by controlling common signal / channel transmissions such as SSB, PRACH, and paging. While completely stopping (or turning off) SSB transmission can significantly reduce the base station's energy consumption, the absence of SSB, which performs functions such as time / frequency synchronization or RRM measurement, may compromise stable operation for the corresponding cell from the terminal's perspective.

[0270] Accordingly, energy saving effects of the base station can be achieved by changing the transmission pattern of the SSB (e.g., transmission period, period per SSB candidate index(s), SSB candidate index(s) transmitted within one transmission period, transmission power, etc.) depending on the situation.

[0271] For example, in the case of contention-based random access, since it is unknown when a terminal will transmit PRACH, the base station may consume a lot of energy by always attempting to receive from the configured PRACH resources. Accordingly, the energy of the base station can be saved by applying methods to control the amount of PRACH resources (for example, a method to control the cycle of PRACH resources, a method to control the amount of resources by pre-configuring PRACH resource set #1 and set #2 and transmitting instructions to activate one or both sets, or a method to provide a corresponding amount of PRACH resources (non)uniformly) for each SSB index.

[0272] In the case of paging, paging frames and / or paging opportunities (POs) are distributed along the time axis within a DRX cycle (or paging cycle), and terminals can attempt to receive paging at specific PFs / POs derived from their ID-based formulas. However, from the perspective of the base station, if it is intended to transmit paging to multiple terminals simultaneously, it may be frequently activated to transmit paging. Accordingly, methods may be applied to place PFs and / or POs for paging reception as close to the time axis as possible, or to place them using different frequency axis resources within the same time period.

[0273] Network Energy Saving (NES)

[0274] Energy conservation in base stations is considered important in wireless communication systems because it contributes to building eco-friendly networks by reducing carbon emissions and lowering the operational expenditures (OPEX) of telecommunications operators. In particular, as the introduction of next-generation wireless communication demands high transmission rates, base stations must be equipped with a greater number of antennas and provide services through wider bandwidths and frequency bands.

[0275] As a result, the energy costs of base stations increase excessively, so base stations need to apply energy-saving methods.

[0276] In the improved wireless communication system, SSB-free SCell operation for inter-band CA of FR 1 and co-located cells, cell DTX / DRX and terminal DRX alignment operation in RRC_connected mode, and information exchange between nodes of cell DTX / DRX can be performed.

[0277] In addition, spatial and power domain technologies that enable efficient adaptation of spatial elements, efficient adaptation of power offset values ​​between PDSCH and CSI-RS, methods to prevent camping by legacy terminals in cells with NES technology, conditional handover (CHO) methods, inter-node beam activation methods that limit paging in restricted areas, and radio resource management (RRM) / RF methods may be applied.

[0278] From the perspective of a base station operating multiple frequency bands, even when the number of serviced terminals is small or the traffic load is relatively low, the amount of energy consumed by periodically transmitting SSB and / or system information can be large.

[0279] In the description of the present disclosure, the frequency band may be applied as a band, carrier, serving cell, or BWP, etc.

[0280] As an example of the present disclosure, an action in which a terminal requests a necessary situation from a base station (e.g., an on-demand based action) may be applied. As an example, a method of instructing / setting / defining a request for an on-demand SSB transmission, and the start and end of an on-demand SSB transmission may be applied.

[0281] An always-on (AO) SSB refers to an SSB that continues to transmit until the base station sets it to OFF. The terminal can perform synchronization and measurement operations for the corresponding cell through the AO SSB. Additionally, the terminal can find information about the CORESET for receiving SIBs through the AO SSB. If the SSB is a CD (cell defining)-SSB, the terminal can determine the location of the CORESET based on the SSB. If the SSB is an NCD (non-cell defining)-SSB, the terminal can measure the state of synchronization and received signals based on the SSB.

[0282] Additionally, the AO-SSB may not be present in a specific cell or may not be configured. In this case, the terminal may instead use the AO-SSB of a reference cell or a special cell, which is another co-located cell, and the AO-SSB may always be transmitted and received in multiple beam directions at specific intervals.

[0283] On-demand SSB refers to an SSB that is transmitted only for a certain period of time when requested by a base station or / and a terminal. On-demand SSB transmission can be requested by a base station or / and a terminal when needed via L1 signaling (e.g., DCI, etc.), L2 signaling (e.g., MAC CE, etc.), or L3 signaling (or RRC signaling, etc.). Unlike AO SSB, On-demand SSB does not perform continuous transmission with a single triggering, so methods related to the completion of On-demand SSB transmission may be applied.

[0284] Activation or / and triggering of transmission of on-demand SSB can be performed / interpreted from the perspective of a base station, and activation or / and triggering of reception of on-demand SSB can be performed / interpreted from the perspective of a terminal.

[0285] In a basic wireless communication system, for each BWP of each serving cell, the terminal may be provided with a set of periodic CSI-RS resource setting indices q_0 by "failureDetectionResourcesToAddModList" and a set of periodic CSI-RS resource setting indices and / or SS / PBCH block indices q_1 by "candidateBeamRSList" or "candidateBeamRSListExt" or "candidateBeamRSSCellList" for measuring wireless link quality in the BWP of the corresponding serving cell. Instead of sets q_0 and q_1, for each BWP of each serving cell, the terminal may be provided with two sets of periodic CSI-RS resource setting indices, q_0,0 and q_0,1, respectively, by "failureDetectionSet1" and "failureDetectionSet2" which can be enabled by MAC CE, and two sets of periodic CSI-RS resource setting indices and / or SS / PBCH block indices, q_1,0 and q_1,1, respectively, by "candidateBeamRS-List" and "candidateBeamRS-List2". Set q_0,0 may be associated with set q_1,0 and set q_0,1 may be associated with set q_1,1. For each BWP of each serving cell, a set of periodic CSI-RS resource setting indices q_0 by "failureDetectionResourcesToAddModList" and a set of periodic CSI-RS resource setting indices and / or SS / PBCH block indices q_1 by "candidateBeamRSList" or "candidateBeamRSListExt" or "candidateBeamRSSCellList" may be provided to the terminal.Instead of sets q_0 and q_1, for each BWP of each serving cell, the terminal may be provided with two sets of periodic CSI-RS resource setting indices, q_0,0 and q_0,1, respectively, by "failureDetectionSet1" and "failureDetectionSet2" which can be enabled by MAC CE, and two sets of periodic CSI-RS resource setting indices and / or SS / PBCH block indices, q_1,0 and q_1,1, respectively, by "candidateBeamRS-List" and "candidateBeamRS-List2". Set q_0,0 may be associated with set q_1,0, and set q_0,1 may be associated with set q_1,1.

[0286] When the operation of the basic wireless communication system described above is applied, a method to detect beam failure and radio link failure is not provided when the on-demand SSB is not transmitted or is disabled in a specific cell where the on-demand SSB is provided. In particular, in a cell where the AO SSB is not configured, when the on-demand SSB is not transmitted or is disabled, a problem occurs in which the terminal cannot perform beam failure detection (BFD) and radio link monitoring (RLM).

[0287] Below, we will explain the methods for detecting beam failures and wireless link failures based on whether on-demand SSB transmission is enabled.

[0288] FIG. 20 is a flowchart for explaining a method performed by a terminal according to one embodiment of the present disclosure.

[0289] The terminal can receive first setting information associated with at least one of a first type of synchronization signal block (SSB) set or a second type of SSB set from a base station (S2010).

[0290] In describing the present disclosure, each of the first type of SSB set and the second type of SSB set may include at least one SSB. Furthermore, the first type of SSB set may include at least one always-on (AO) SSB, and the second type of SSB set may include at least one on-demand SSB. That is, the first type of SSB set may be replaced / represented by AO SSB(s), and the second type of SSB set may be replaced / represented by on-demand SSB(s). However, this is merely one embodiment, and the first type of SSB set and the second type of SSB set may be determined according to at least one of the options described below.

[0291] For example, the first configuration information may be transmitted from a base station to a terminal via upper layer signaling (e.g., system blocks, RRC messages, etc.). The first configuration information may include information for configuring each of the first type of SSB set and / or the second type of SSB set. For example, the first configuration information may include the number, use, type, etc. of (SSB) resources included in each of the first type of SSB set and / or the second type of SSB set.

[0292] For example, the use of at least one SSB included in the second type of SSB set may be set to link failure detection (or / and link monitoring, etc.). In this case, the use of at least one SSB may be set by the first setting information, but is not limited thereto and may be set by other setting information.

[0293] In addition, link failure detection may include beam failure or / and wireless link failure. That is, the terminal may perform beam failure detection or / and wireless link monitoring based on a first type of SSB set and / or a second type of SSB set.

[0294] Based on the second type of SSB set being activated and conditions related to the SSB set being satisfied, the terminal can perform link failure detection based on the first type of SSB set and the second type of SSB set (S2020).

[0295] In one example of the present disclosure, a terminal may receive control information (or control signal) (e.g., DCI, MAC CE, RRC message, etc.) from a base station for activating a second type of SSB set. In one example, the terminal may transmit a request signal / information requesting the activation of a second type of SSB set to the base station. The terminal may receive control information (or control signal) from the base station for activating a second type of SSB set corresponding to the request signal / information. Accordingly, a second type of SSB set may be activated / transmitted on a cell where a first type of SSB set is transmitted / configured.

[0296] In one example of the present disclosure, a condition related to an SSB set may include a condition regarding whether a first type of SSB set and a second type of SSB set are located in the same bandwidth part (BWP). Satisfying such a condition means that the first type of SSB set and the second type of SSB set are located in the same BWP.

[0297] Additionally or alternatively, conditions related to the SSB set may include i) a condition regarding whether the power of the first type of SSB set and the second type of SSB set is the same, or ii) a condition regarding whether the power difference between the first type of SSB set and the second type of SSB set is less than or equal to a first threshold. Meeting such conditions may mean i) the power of the first type of SSB set and the second type of SSB set is the same and / or ii) the power difference between the first type of SSB set and the second type of SSB set is less than or equal to the first threshold.

[0298] Additionally or alternatively, conditions related to the SSB set may include conditions regarding whether the center frequencies of the first type of SSB set and the second type of SSB set, respectively, are the same. Meeting such conditions may mean that the center frequencies of the first type of SSB set and the second type of SSB set, respectively, are the same.

[0299] Additionally or alternatively, conditions related to the SSB set may include i) a condition regarding whether the period of each of the first type of SSB set and the second type of SSB set is below a second threshold, or ii) a condition regarding whether the time resource index to which the first type of SSB set and the second type of SSB set are transmitted is the same. Meeting such conditions may mean i) the period of each of the first type of SSB set and the second type of SSB set is below the second threshold, and / or ii) the time resource index to which the first type of SSB set and the second type of SSB set are transmitted is the same.

[0300] For example, if a second type of SSB set is activated and at least one or all of the conditions associated with the SSB set described above are satisfied, the terminal can perform link failure detection based on the first type of SSB set and the second type of SSB set. That is, based on the second type of SSB set being activated and at least one of the conditions associated with the SSB set described above being satisfied, the terminal can perform link failure detection based on both the first type of SSB set and the second type of SSB set. For example, the terminal can perform link failure detection by measuring the first type of SSB set transmitted periodically and the second type of SSB set transmitted by a request / instruction.

[0301] As an example of the present disclosure, a terminal may perform link failure detection based on a first type of SSB set, provided that a second type of SSB set is activated and conditions related to the SSB set (e.g., at least one of the conditions described above) are not satisfied. That is, if all of the conditions described above are not satisfied, or if at least one of the conditions is not satisfied, the terminal may perform link failure detection using only the first type of SSB set. However, the terminal is not limited thereto, and may perform link failure detection using both the first type of SSB set and the second type of SSB set even if the conditions are not satisfied.

[0302] As described above, the activation or deactivation of the second type of SSB set may be directed or set by control information transmitted by the base station. For example, the terminal may receive instruction information (e.g., DCI, MAC CE, RRC message) for deactivating the second type of SSB set, and accordingly, the second type of SSB set may be deactivated.

[0303] Additionally or alternatively, the second type of SSB set may be deactivated based on the expiration of the timer associated with the second type of SSB set or the end of the duration associated with the second type of SSB set.

[0304] The method described in the example of FIG. 20 can be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) of FIG. 1 may receive first configuration information related to at least one of a first type of SSB set or a second type of SSB set from a base station through one or more transceivers (106). Based on the second type of SSB set being activated and conditions related to the SSB set being satisfied, one or more processors (102) may perform link failure detection based on the first type of SSB set and the second type of SSB set.

[0305] Furthermore, one or more memories (104) of the first device (100) may store instructions for performing the method described in the example of FIG. 20 or the examples described below when executed by one or more processors (102).

[0306] FIG. 21 is a flowchart for explaining a method performed by a base station according to one embodiment of the present disclosure.

[0307] The base station can transmit first setting information associated with at least one of a first type of SSB set or a second type of SSB set to a terminal (S2110).

[0308] That is, the base station may transmit first configuration information to a terminal for configuring a first type of SSB set and / or a second type of SSB set. The first configuration information may include the number, use, type, etc. of (SSB) resources included in each of the first type of SSB set and / or the second type of SSB set.

[0309] Based on the second type of SSB set being activated and conditions related to the SSB set being satisfied, the base station can receive link failure detection information based on the first type of SSB set and the second type of SSB set from the terminal (S2120).

[0310] Specifically, based on the activation of the second type of SSB set and the satisfaction of at least one of the above-described conditions related to the SSB set, a link failure detection operation based on the first type of SSB set and the second type of SSB set may be performed by the terminal. Additionally, the base station may receive information related to the link failure detection based on the first type of SSB set and the second type of SSB set (e.g., report information related to said detection) from the terminal.

[0311] For example, information related to link failure detection may include measurement / monitoring report information based on a first type of SSB set and a second type of SSB set, beam failure or wireless link failure indication information, information for recovering from a beam failure or wireless link failure, etc.

[0312] The method described in the example of FIG. 21 can be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 can transmit first setting information related to at least one of a first type SSB set or a second type SSB set to a terminal via one or more transceivers (206). Based on the second type SSB set being activated and conditions related to the SSB set being satisfied, one or more processors (202) can receive link failure detection information based on the first type SSB set and the second type SSB set from the terminal via one or more transceivers (206).

[0313] Furthermore, one or more memories (204) of the second device (200) may store instructions for performing the method described in the example of FIG. 10 or the examples described below when executed by one or more processors (202).

[0314] Below, we will specifically explain the methods for detecting beam failures and wireless link failures based on whether on-demand SSB transmission is enabled.

[0315] In describing the present disclosure, at least one of three options for setting two types of SSB may be applied. That is, two types of SSB according to at least one of the options described below may be applied to each embodiment(s).

[0316] Option 1

[0317] Option 1 relates to an SSB on a first cell (e.g., an on-demand SSB) in which transmission is initiated by a directive from a base station or a request from a terminal.

[0318] - Type 1 SSB (or AO SSB): This may refer to an SSB that is periodically transmitted over a first cell or a second cell. If the period, etc., for the SSB is determined / defined / set, the SSB may be transmitted continuously (without on, off, or activation / deactivation) at that period. If the Type 1 SSB is an SSB transmitted over the first cell, the first cell may be a timing reference cell. If the Type 1 SSB is an SSB transmitted over the second cell, the second cell may have an intra-band or inter-band carrier aggregation (CA) relationship with the first cell. For example, (in an inter-band CA environment) the second cell may be set as a timing reference cell for the first cell, or (in an intra-band CA environment) the second cell may be determined / defined as a timing reference cell for the first cell (e.g., a specific cell within the same timing advance group, PCell, or PSCell (primary secondary cell)). In addition, only the following Type 2 SSB can be transmitted on the first cell without Type 1 SSB.

[0319] - Type 2 SSB (or, On-Demand SSB): This may refer to an SSB in which transmission on the first cell is enabled through instructions from the base station (by RRC, MAC-CE, DCI, etc.). Alternatively, Type 2 SSB may refer to an SSB in which transmission is enabled by a request from a terminal.

[0320] For example, for the activated SSB (e.g., Type 2 SSB), deactivation of the SSB may be explicitly instructed via RRC / MAC-CE / DCI, etc. As another example, after a transmission count or transmission interval is set / instructed in the RRC / MAC-CE / DCI instructing the activation of the SSB, the transmission of the SSB may be deactivated once that transmission count or transmission interval has elapsed. As yet another example, a previously set / defined transmission count or transmission interval may be set / defined, and the SSB may be deactivated once that transmission count or transmission interval has elapsed after activation. As yet another example, (if the first cell is a SCell) the SSB may be deactivated when the activation of the first cell is completed (or when a CSI report for the first cell is successfully performed). As yet another example, (if the first cell is a SCell) the SSB may be deactivated when the first cell is deactivated. As another example, (if the first cell is a PCell) the corresponding SSB may be disabled after a handover is performed. As yet another example, the corresponding SSB may be disabled at the request of the terminal.

[0321] Option 2

[0322] According to this option, one or more SSB settings are configured, and an SSB corresponding to one of the SSB settings may be transmitted by a base station instruction or a request from a terminal. At this time, at least the SSB periodicity values ​​may differ between different SSB settings, and adaptation to the SSB periodicity may be performed by changing the activated SSB setting.

[0323] - Type 1 SSB: This may refer to a reference configuration among the SSB configurations set by the base station, or an SSB configuration with the largest SSB period value set. An SSB corresponding to the reference configuration may be called a Type 1 SSB. For example, if an SSB configuration corresponding to a Type 2 SSB is not activated, an SSB configuration corresponding to a Type 1 SSB may be activated. If an SSB configuration corresponding to a Type 2 SSB (or an SSB configuration not corresponding to a Type 1 SSB) is activated, an SSB configuration corresponding to a Type 1 SSB may be deactivated.

[0324] Additionally or alternatively, if an SSB opportunity (hereinafter referred to as "reference SSB opportunity(s)") configured based on a specific (reference) setting among the SSB settings configured by the base station is a subset of SSB opportunity(s) configured based on another setting (hereinafter referred to as "extended SSB opportunity(s)"), said reference SSB opportunity(s) may be defined as a Type 1 SSB (regardless of the actual activated SSB setting). In this case, a Type 2 SSB may be defined as the remaining SSB opportunity(s) among said extended SSB opportunity(s) (included in the actual activated setting), excluding the reference SSB opportunity(s).

[0325] - Type 2 SSB: In addition to the SSB setting corresponding to Type 1 SSB, one or more SSB setting(s) for Type 2 SSB may be set for the terminal. When the SSB setting corresponding to Type 2 SSB is activated, all SSBs belonging to the activated SSB setting may be defined as Type 2 SSBs. As another example, if an SSB setting(s) configured based on a specific (reference) setting among the configured SSB setting(s) (hereinafter, "reference SSB opportunity(s)") becomes a subset of SSB opportunity(s) configured based on another setting (hereinafter, "extended SSB opportunity(s)"), the reference SSB opportunity(s) may be defined as Type 1 SSBs (regardless of the actual activated SSB setting). In this case, Type 2 SSBs may be defined as the remaining SSB opportunity(s) among the extended SSB opportunity(s) (included in the actual activated setting), excluding the reference SSB opportunity(s).

[0326] For example, at least one of the corresponding SSB setting(s) may be activated by an instruction from the base station (by RRC, MAC-CE, or DCI) or by a request from the terminal. For example, the deactivation of the SSB may be explicitly instructed via RRC, MAC-CE, DCI, etc. for the corresponding activated SSB setting. As another example, the number of transmissions or the transmission interval may be set / instructed by the RRC, MAC-CE, or DCI instructing the SSB activation, and the corresponding SSB may be deactivated after the number of transmissions or the transmission interval has elapsed. As yet another example, if a pre-set / defined number of transmissions or the transmission interval exists, the corresponding SSB may be deactivated after the number of transmissions or the transmission interval has elapsed following SSB activation. As yet another example, (if the first cell is a SCell) the corresponding SSB may be deactivated when the activation for the first cell is completed (or when a CSI report for the first cell is successfully reported). As another example, (if the first cell is SCell) if the first cell is deactivated, the corresponding SSB may be deactivated. As another example, (if the first cell is PCell) the SSB may be deactivated after a handover is performed. As yet another example, the SSB may be deactivated by a request from the terminal.

[0327] Option 3

[0328] According to this option, one or more SSB setting(s) are configured for the terminal, and an SSB corresponding to one of the SSB setting(s) may be transmitted by base station instruction or a request from the terminal. At this time, there exists an SSB (e.g., Type 1 SSB) that is continuously and periodically transmitted regardless of the (de)activation of the SSB setting(s), and an additional SSB setting to be transmitted to that SSB may be (de)activated. At least the SSB period value or SSB time pattern may differ between different SSB settings. Adaptation to the SSB period may be performed by changing the activated SSB setting.

[0329] - Type 1 SSB: This may mean an SSB corresponding to the default SSB setting, and continuous periodic transmission may be guaranteed regardless of the (de)activation of the SSB setting(s) corresponding to Type 2 SSB.

[0330] - Type 2 SSB: One or more SSB setting(s) for Type 2 SSB may be configured for the terminal. For example, at least one of the one or more SSB setting(s) may be activated by an instruction from the base station (by RRC, MAC-CE, or DCI) or by a request from the terminal. For example, the deactivation of the SSB may be explicitly instructed via RRC, MAC-CE, DCI, etc. for the activated SSB setting. As another example, the number of transmissions or transmission intervals may be configured / instructed by RRC, MAC-CE, or DCI instructing SSB activation, and the SSB may be deactivated after the number of transmissions or transmission intervals have elapsed. As yet another example, there is a pre-configured / defined number of transmissions or transmission intervals, and the SSB may be deactivated after the number of transmissions or transmission intervals have elapsed following SSB activation. As another example, (if the first cell is a SCell) the corresponding SSB may be disabled when activation for the first cell is completed (or when a CSI report for the first cell is successfully reported). As another example, (if the first cell is a SCell) the corresponding SSB may be disabled when the first cell is disabled. As another example, (if the first cell is a PCell) the SSB may be disabled after a handover is performed. As yet another example, the SSB may be disabled by a request from the terminal.

[0331] As with the options described above, Type 2 SSB may mean an SSB that cannot assume continuous and periodic transmission.

[0332] Example 1

[0333] Example 1 relates to a BFD method based on whether a Type 1 SSB and / or a Type 2 SSB is set / transmitted / enabled. The terminal may perform a BFD operation according to at least one of the detailed embodiments described below.

[0334] Example 1-1

[0335] Example 1-1 relates to a case where, for a cell in which a Type 1 SSB is set / transmitted, the Type 1 SSB is set for BFD use by the "failureDetectionResourcesToAddModList" parameter (e.g., a parameter related to a reference signal / resource for detecting BFD and / or RLF (radio link failure)). That is, the terminal may receive a parameter related to a reference signal / resource for detecting BFD and / or RLF (e.g., an RRC message, etc.) from the base station, and Example 1-1 relates to a case where the Type 1 SSB is set for BFD use by the said parameter.

[0336] As an example of the present disclosure, when a type 2 SSB is transmitted to or activated in the cell, the terminal can perform BFD by utilizing both the type 1 SSB and the type 2 SSB.

[0337] Additionally or alternatively, if a Type 2 SSB is transmitted to or activated in the cell, the terminal may perform BFD using both a Type 1 SSB and a Type 2 SSB if at least one of the conditions described below is satisfied. If the conditions described below are not satisfied, the terminal may perform BFD using only the Type 1 SSB and not use the Type 2 SSB for BFD execution. The conditions related to BFD execution are as follows:

[0338] - When the center frequencies of Type 1 SSB and Type 2 SSB are set / determined to be the same (or, when the difference in center frequencies between the two SSBs is less than or equal to a specific value);

[0339] - When the configured / determined downlink transmit power (or EPRE (energy per resource element)) values ​​of the Type 1 SSB and Type 2 SSB are the same (or when the difference in transmit power between the two SSBs is less than or equal to a specific value);

[0340] - If the difference between the periododicity of a Type 1 SSB and the periododicity of a Type 2 SSB is less than or equal to a predefined value (e.g., if the periododicity of a Type 1 SSB is 80 ms and the periododicity of a Type 2 SSB is 5 ms, only the Type 1 SSB is used as the BFD);

[0341] - If the half-frame index where the Type 1 SSB is transmitted and the half-frame index where the Type 2 SSB is transmitted are the same; and

[0342] - When both TYPE 1 SSB and TYPE 2 SSB belong to the same (active DL) BWP.

[0343] Examples 1-2

[0344] Example 1-1 relates to a case where, for a cell in which a Type 1 SSB is not set, a Type 2 SSB is set for BFD purposes by the "failureDetectionResourcesToAddModList" parameter, etc.

[0345] In one example of the present disclosure, when a Type 2 SSB is transmitted to or activated in the cell, the terminal may perform BFD based on the Type 2 SSB. In this case, the activation of the Type 2 SSB may be enabled by a MAC CE / DCI instruction or an RRC message.

[0346] In one example of the present disclosure, when a Type 2 SSB is terminated from transmission or disabled in the cell, the terminal determines an RS set q0 or q as described below. 0,0 and q 0,1 BFD can be performed according to:

[0347] - (where q0 is provided by "failureDetectionResourcesToAddModList" of a Type 2 SSB that is disabled for the BWP of the serving cell and / or is not currently transmitting) the terminal may determine set q0 to include periodic CSI-RS resource setting indices having the same value as the RS index of the RS set indicated by the TCI status for each CORESET it uses for PDCCH monitoring;

[0348] - (q corresponding to a Type 2 SSB for TRP 1 that is disabled for the serving cell's BWP and / or is not currently transmitting, when the terminal is set to MTRP) 0,0 and q corresponding to Type 2 SSB for TRP 2 0,1 (If provided,) the terminal includes, for the first CORESET and second CORESET used for PDCCH monitoring, periodic CSI-RS resource setting indices having the same value as the RS index of the RS set indicated by the TCI status, respectively, q 0,0 and q 0,1 A set can be determined. At this time, the terminal may be provided with "coresetPoolIndex" values ​​0 and 1 for the first CORESET and the second CORESET, respectively, or may not be provided with a "coresetPoolIndex" value for the first CORESET and may be provided with a "coresetPoolIndex" value 1 for the second CORESET.

[0349] - In this case, the deactivation of the Type 2 SSB may result in the termination or deactivation of the transmission of the SSB in accordance with MAC CE, DCI instructions, or RRC messages. Additionally or alternatively, the transmission of the SSB may be terminated or deactivated when the Type 2 SSB-related timer expires or the Type 2 SSB transmission duration ends. Additionally or alternatively, the transmission of the SSB may be deactivated when the Type 2 SSB transmission is terminated under specific conditions.

[0350] Example 2

[0351] Example 2 relates to an RLM method based on whether Type 1 / 2 SSB is set / transmitted / enabled. The terminal may perform an RLM operation according to at least one of the detailed embodiments described below.

[0352] Example 2-1

[0353] Example 2-1 relates to a case where, for a cell in which a Type 1 SSB is set / transmitted, the Type 1 SSB is set for RLM purposes by a "RadioLinkMonitoringRS" parameter (e.g., a parameter for setting an RS for wireless link monitoring). That is, the terminal can receive a parameter related to a reference signal / resource for RLM (e.g., an RRC message, etc.) from the base station, and Example 2-1 relates to a case where the Type 1 SSB is set for RLM purposes by said parameter.

[0354] As an example of the present disclosure, when a Type 2 SSB is transmitted to or activated in the cell, the terminal can perform RLM by utilizing both the Type 1 SSB and the Type 2 SSB.

[0355] Additionally or alternatively, if a Type 2 SSB is transmitted to or activated in the cell, the terminal may perform RLM using both a Type 1 SSB and a Type 2 SSB if at least one of the conditions described below is satisfied. If the conditions described below are not satisfied, the terminal may perform RLM using only the Type 1 SSB and not use the Type 2 SSB for RLM execution. The conditions related to RLM execution are as follows:

[0356] - When the center frequencies of Type 1 SSB and Type 2 SSB are set / determined to be the same (or, when the difference in center frequencies between the two SSBs is less than or equal to a specific value);

[0357] - When the configured / determined downlink transmission power (or EPRE) values ​​of Type 1 SSB and Type 2 SSB are identical (or when the difference in transmission power between the two SSBs is less than or equal to a specific value);

[0358] - If the difference between the SSB period of Type 1 SSB and the SSB period of Type 2 SSB is less than or equal to a predefined value (e.g., if the period of Type 1 SSB is 80 ms and the period of Type 2 SSB is 5 ms, only Type 1 SSB is used as the RLM);

[0359] - If the half-frame index where the Type 1 SSB is transmitted and the half-frame index where the Type 2 SSB is transmitted are the same; and

[0360] - When both TYPE 1 SSB and TYPE 2 SSB belong to the same (active DL) BWP.

[0361] Example 2-2

[0362] Example 2-2 relates to a case where a Type 2 SSB is set for RLM purposes by the "RadioLinkMonitoringRS" parameter, etc., for a cell (e.g., PCell, PSCell, or SCell) in which a Type 1 SSB is not separately set.

[0363] In one example of the present disclosure, when a Type 2 SSB is transmitted to or activated in the cell, the terminal may perform RLM based on the Type 2 SSB. In this case, the activation of the Type 2 SSB may be enabled by a MAC CE, DCI, or RRC message.

[0364] In one example of the present disclosure, when a type 2 SSB is terminated from transmission or deactivated in the cell, the terminal may perform an RLM according to an RS set determined according to the method described below:

[0365] - (When the terminal is provided with a "RadioLinkMonitoringRS" of a Type 2 SSB that is disabled or not currently transmitting) and the terminal is provided with a PDCCH received TCI status including one or more CSI-RS:

[0366] -- If the terminal contains only one RS in the active TCI state for PDCCH reception, the RS provided in the active TCI state for PDCCH reception can be used for wireless link monitoring;

[0367] -- If two RSs are included in the active TCI state for PDCCH reception, the terminal may expect that one RS is configured with qcl-Type set to 'typeD' and that the terminal uses the RS configured with qcl-Type set to 'typeD' for wireless link monitoring; the terminal may not expect that both RSs are configured with qcl-Type set to 'typeD';

[0368] -- The terminal does not need to use a non-periodic or semi-permanent RS for wireless link monitoring;

[0369] -- When "Lmax = 4", the terminal can select N RLM RS provided for active TCI status for PDCCH reception in the CORESET associated with the search space set in order starting from the shortest monitoring period; if there are two or more CORESETs associated with the search space set having the same monitoring period, the terminal can determine the order of the CORESETs starting from the highest CORESET index.

[0370] -- If a Type 2 SSB “RadioLinkMonitoringRS” is provided to the terminal and the said SSB is disabled or not currently transmitting, the terminal may not expect to use N RLM “RadioLinkMonitoringRS” or higher for wireless link monitoring.

[0371] According to various embodiments of the present disclosure, even when both Type 1 SSB and Type 2 SSB are not transmitted, the terminal can efficiently detect BFD and RLF for the cell.

[0372] Methods, embodiments, or descriptions for implementing the method proposed in this disclosure may each be applied separately, or one or more methods (or embodiments or descriptions) may be applied in combination.

[0373] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.

[0374] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential features of the present disclosure. Accordingly, the detailed description set forth above should not be interpreted restrictively in all respects and should be considered exemplary. The scope of the present disclosure shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.

[0375] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that enable operations according to the methods of various embodiments to be executed on a device or computer, and a non-transitory computer-readable medium on which such software or instructions, etc. are stored and executable on a device or computer. Instructions that may be used to program a processing system to perform the features described in the present disclosure may be stored on or within a storage medium or a computer-readable storage medium, and the features described in the present disclosure may be implemented using a computer program product comprising such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and may include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remotely from the processor(s). Memory or alternatively, non-volatile memory device(s) within memory comprises a non-transient computer-readable storage medium. The features described in this disclosure may be stored in any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of a processing system and allow the processing system to interact with other mechanisms utilizing results according to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0376] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally or generally, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the device (100, 200) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology may create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0377] Although the method proposed in this disclosure has been described with an example applied to 3GPP LTE / LTE-A and 5G systems, it can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

1. A step of receiving first setting information associated with at least one of a first type synchronization signal block (SSB) set or a second type SSB set from a base station by a terminal; and A method comprising the step of performing link failure detection by the terminal based on the first type of SSB set and the second type of SSB set, based on the second type of SSB set being activated and conditions related to the SSB set being satisfied.

2. In Paragraph 1, The above link failure includes a beam failure or a wireless link failure, a method.

3. In Paragraph 1, A method in which link failure detection is performed by the terminal based on the first type of SSB set, based on the second type of SSB set being activated and the condition associated with the SSB set not being satisfied.

4. In Paragraph 1, A method in which the conditions related to the above SSB set include a condition regarding whether the first type of SSB set and the second type of SSB set are located in the same bandwidth part (BWP).

5. In Paragraph 1, A method comprising a condition related to the above SSB set, i) a condition related to whether the power of the first type SSB set and the second type SSB set is the same, or ii) a condition related to whether the power difference between the first type SSB set and the second type SSB set is less than or equal to a first threshold value.

6. In Paragraph 1, The condition related to the above SSB set is a condition and method regarding whether the center frequency of each of the first type SSB set and the second type SSB set is the same.

7. In Paragraph 1, A method comprising a condition related to the above SSB set, i) a condition related to whether the period of each of the first type SSB set and the second type SSB set is below a second threshold, or ii) a condition related to whether the time resource index to which the first type SSB set and the second type SSB set are transmitted is the same.

8. In Paragraph 1, The above-mentioned first type SSB set includes at least one always-on (AO) SSB, and A method in which the above-mentioned second type of SSB set comprises at least one on-demand SSB.

9. In Paragraph 1, A method in which the use of at least one SSB included in the above-mentioned second type of SSB set is set to the above-mentioned link failure detection.

10. In Paragraph 1, A method in which the activation or deactivation of the above-mentioned second type of SSB set is directed or set by control information transmitted by the base station.

11. In Paragraph 1, A method in which the second type of SSB set is deactivated based on the expiration of a timer associated with the second type of SSB set or the end of a duration associated with the second type of SSB set.

12. One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: Receiving first setting information associated with at least one of a first type synchronization signal block (SSB) set or a second type SSB set from a base station through the one or more transceivers; and A terminal configured to perform link failure detection based on the first type of SSB set and the second type of SSB set, based on the second type of SSB set being activated and conditions related to the SSB set being satisfied.

13. A step of transmitting first configuration information associated with at least one of a first type synchronization signal block (SSB) set or a second type SSB set to a terminal by a base station; and A method comprising the step of receiving information related to link failure detection based on the first type of SSB set and the second type of SSB set from the terminal by the base station, based on the second type of SSB set being activated and conditions related to the SSB set being satisfied.

14. In a base station, the above base station is: One or more transceivers; and It includes one or more processors connected to the above one or more transmitters and receivers, and The above one or more processors are: Transmitting first setting information associated with at least one of a first type synchronization signal block (SSB) set or a second type SSB set to a terminal through the one or more transceivers; and A base station configured to receive information related to link failure detection based on the first type of SSB set and the second type of SSB set from the terminal through the one or more transceivers, based on the second type of SSB set being activated and conditions related to the SSB set being satisfied.

15. In a processing device configured to control a terminal, the processing device comprises: One or more processors; and A processing device comprising one or more computer memories that are operably connected to one or more processors and store instructions for performing a method according to any one of claims 1 to 11 based on execution by one or more processors.

16. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium in which one or more of the above instructions are executed by one or more processors to control the device to perform a method according to any one of claims 1 to 11.