Apparatus and method for requesting synchronization signal and physical broadcast channel block transmitted in on-demand manner in wireless communication system

Abstract

This disclosure relates to a method for requesting a synchronization signal / physical broadcast channel block (SSB) to be transmitted on demand in a wireless communication system, comprising the steps of: receiving configuration information related to the on-demand SSB; identifying resources for requesting the on-demand SSB based on the configuration information; and using the resources to transmit a request signal for the on-demand SSB, wherein the configuration information may include information related to at least one of a signaling method for requesting the on-demand SSB, resources for transmitting the request signal, and the structure of the request signal.

Description

Technical Field

[0001] The following description relates to wireless communication systems, and specifically to an apparatus and method for requesting a synchronization signal / physical broadcast channel block (SSB) for on-demand transmission in a wireless communication system. Background Technology

[0002] 5G mobile communication systems, as the successor to LTE, represent a new state of mobile communication characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, to mid-frequency bands between 1 GHz and 10 GHz, and to high-frequency bands above 24 GHz (such as millimeter waves). 6G systems are being developed based on the fundamental technologies of 5G mobile communication.

[0003] The 6G system aims to achieve: (i) extremely high data rates per device; (ii) a massive number of connected devices; (iii) global connectivity; (iv) ultra-low latency; (v) low-power, battery-free Internet of Things (IoT) devices; (vi) ultra-reliable connectivity; and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be summarized in four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity. Summary of the Invention

[0004] Technical issues

[0005] This disclosure relates to an apparatus and method for efficiently requesting synchronization signal / physical broadcast channel blocks (SSBs) to be transmitted on demand in a wireless communication system.

[0006] This disclosure relates to apparatus and methods for effectively supporting network power saving (NES) operation of base stations in wireless communication systems.

[0007] This disclosure relates to an apparatus and method for providing configuration information related to a signal used to request SSB transmission in a wireless communication system.

[0008] This disclosure relates to an apparatus and method for configuring the structure of a signal for requesting SSB transmission in a wireless communication system.

[0009] This disclosure relates to an apparatus and method for allocating resources for a signal configured in a wireless communication system to request the transmission of an SSB.

[0010] This disclosure relates to an apparatus and method for configuring resources for sending signals to request an SSB for each attribute of a wireless communication system.

[0011] This disclosure relates to an apparatus and method for selecting resources in a wireless communication system for transmitting a signal requesting a Service Serving (SSB) transmission.

[0012] This disclosure relates to an apparatus and method for triggering a request for an SSB in a wireless communication system.

[0013] This disclosure relates to an apparatus and method for requesting an SSB transmission in a SSB-less cell in a wireless communication system.

[0014] The technical objectives to be achieved in this disclosure are not limited to those mentioned above, and other technical tasks not mentioned can be considered by those skilled in the art of applying the technical configuration of this disclosure from the embodiments of this disclosure described below.

[0015] Technical solution

[0016] In one example of this disclosure, a method may include: receiving configuration information related to a downlink signal; identifying resources for requesting the downlink signal based on the configuration information; and sending a request signal for the downlink signal using the resources, wherein the configuration information includes information related to at least one of a signaling scheme for requesting the downlink signal, resources for sending the request signal, or the structure of the request signal, and wherein the downlink signal includes an on-demand synchronization signal / physical broadcast channel block (SSB).

[0017] In one example of this disclosure, a method may include: sending configuration information related to a downlink signal; receiving a request signal for the downlink signal using resources identified by the configuration information; and sending the downlink signal in response to the request signal, wherein the configuration information includes at least one of a signaling scheme for requesting the downlink signal, resources for sending the request signal, or a structure of the request signal, and wherein the downlink signal includes an on-demand synchronization signal / physical broadcast channel block (SSB).

[0018] In one example of this disclosure, an apparatus may include: a transceiver; and a processor connected to the transceiver, wherein the processor is configured to: receive configuration information related to an on-demand synchronization signal / physical broadcast channel block (SSB); identify resources for requesting the on-demand SSB based on the configuration information; and use the resources to transmit a request signal for the on-demand SSB, wherein the configuration information includes information related to at least one of a signaling scheme for requesting the on-demand SSB, resources for transmitting the request signal, or the structure of the request signal.

[0019] In one example of this disclosure, an apparatus may include: a transceiver; and a processor connected to the transceiver, wherein the processor is configured to: transmit configuration information related to an on-demand synchronization signal / physical broadcast channel block (SSB); receive a request signal for the on-demand SSB using resources identified by the configuration information; and transmit the on-demand SSB in response to the request signal, wherein the configuration information includes at least one of a signaling scheme for requesting the on-demand SSB, resources for transmitting the request signal, or a structure of the request signal.

[0020] In one example of this disclosure, a user equipment (UE) may include: at least one processor; and at least one computer memory connected to the at least one processor and storing instructions that, when executed by the at least one processor, direct operations including: receiving configuration information related to an on-demand synchronization signal / physical broadcast channel block (SSB); identifying resources for requesting the on-demand SSB based on the configuration information; and using the resources to transmit a request signal for the on-demand SSB, wherein the configuration information includes information related to at least one of a signaling scheme for requesting the on-demand SSB, resources for transmitting the request signal, or the structure of the request signal.

[0021] In one example of this disclosure, a non-transitory computer-readable medium stores at least one instruction executable by a processor, the at least one instruction causing a device to perform operations including: receiving configuration information related to an on-demand synchronization signal / physical broadcast channel block (SSB); identifying resources for requesting the on-demand SSB based on the configuration information; and using the resources to send a request signal for the on-demand SSB, wherein the configuration information includes information related to at least one of a signaling scheme for requesting the on-demand SSB, resources for sending the request signal, or the structure of the request signal.

[0022] The aspects described above in this disclosure are merely some of the preferred embodiments of this disclosure, and various embodiments reflecting the technical features of this disclosure can be derived and understood by those skilled in the art based on the detailed description of this disclosure below.

[0023] Beneficial effects

[0024] According to embodiments based on this disclosure, the following effects can be obtained.

[0025] According to this disclosure, requests for synchronization signal / physical broadcast channel blocks (SSBs) and the transmission operations of SSBs thereunder can be performed efficiently.

[0026] The effects obtainable from the embodiments of this disclosure are not limited to those described above, and those skilled in the art to which the technical features of this disclosure are applied can clearly deduce and understand other effects not explicitly described based on the embodiments of this disclosure described below. In other words, those skilled in the art can also deduce from the embodiments of this disclosure unintended effects resulting from implementing the configurations described in this disclosure. Attached Figure Description

[0027] Figure 1 The diagram illustrates an example of a flexible network topology that can be applied to this disclosure.

[0028] Figure 2 The diagram illustrates an example of the structure applicable to the wireless communication system disclosed herein.

[0029] Figure 3 The illustrations are examples of wireless devices applicable to this disclosure.

[0030] Figure 4 The diagram illustrates an example of a communication process applicable to the first and second nodes of this disclosure.

[0031] Figure 5 The illustration shows an example of a common functional architecture related to both function-based lifecycle management (LCM) and model-based LCM.

[0032] Figure 6 The illustration is an example of the operational process applicable to the artificial intelligence (AI) / machine learning (ML) model of this disclosure.

[0033] Figure 7 The illustrations are examples of electromagnetic spectrum applicable to this disclosure.

[0034] Figure 8 The illustration shows an example of the system information transmission process applicable to THz communication in this disclosure.

[0035] Figure 9 The illustration shows an example of a beam management process applicable to this disclosure.

[0036] Figure 10a The illustration is an example applicable to the general non-terrestrial network (NTN) scenario based on transparent payloads of this disclosure.

[0037] Figure 10b The illustration is an example applicable to the general NTN scenario based on regenerated payloads disclosed herein.

[0038] Figure 11a This diagram illustrates an example of the components of an orbital parameter ephemeris (OPE) format.

[0039] Figure 11bThe illustration shows an example of offsets in satellite-related links.

[0040] Figure 11c The illustration shows an example of timing advance (TA) values ​​in a satellite-related link.

[0041] Figure 12a and Figure 12b The illustrations are examples of sensing operations that can be applied to this disclosure.

[0042] Figure 13 The illustrations are examples of time / frequency resources applicable to sensing operations in this disclosure.

[0043] Figure 14 The illustrations are examples of processes applicable to sensing operations in this disclosure.

[0044] Figure 15 The illustration shows an example of the operation process of a base station that can be applied to the Network Energy Saving (NES) technology supported by this disclosure.

[0045] Figure 16 The illustration is an example of a process applicable to this disclosure for carrier aggregation (CA) operation using secondary cells (SCells) with asynchronous signal / physical broadcast channel blocks (SSBs).

[0046] Figures 17a to 17c The illustration shows an example of an on-demand system information transmission scheme applicable to this disclosure.

[0047] Figure 18 The illustration shows an example of a frequency band operated by a base station according to an embodiment of the present disclosure.

[0048] Figure 19 The illustration shows an example of a process for requesting an on-demand SSB in a wireless communication system according to an embodiment of the present disclosure.

[0049] Figure 20 The illustration shows an example of a process in a wireless communication system, according to an embodiment of the present disclosure, of transmitting a signal for requesting an on-demand SSB by using at least one of a plurality of resources.

[0050] Figure 21 The illustration shows an example of a process for requesting on-demand SSBs based on conditions in a wireless communication system, according to an embodiment of the present disclosure.

[0051] Figure 22 The illustration shows an example of a process for requesting SSB transmission for an SSB-less cell according to an embodiment of the present disclosure. Detailed Implementation

[0052] In this disclosure, "A or B" can mean "A only", "B only", or "both A and B". In other words, in this disclosure, "A or B" can be interpreted as "A and / or B". For example, in this disclosure, "A, B or C" can mean "A only", "B only", "C only", or "any combination of A, B, and C".

[0053] The forward slash ( / ) or comma used in this disclosure may mean "and / or". For example, "A / B" may mean "A and / or B". Accordingly, "A / B" may mean "A only", "B only", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0054] In this disclosure, "at least one of A and B" can mean "only A", "only B" or "both A and B". Furthermore, in this disclosure, the expression "at least one of A or B" or "at least one of A and / or B" can be interpreted as "at least one of A and B".

[0055] Furthermore, in this disclosure, "at least one of A, B and C" can 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" can mean "at least one of A, B and C".

[0056] Furthermore, the parentheses used in this disclosure can indicate "for example". Specifically, when expressed as "control information (ABC)", "ABC" can describe an example of "control information". For example, "control information" can also include DEF as another example. In other words, the "control information" of this disclosure is not limited to "ABC", and "ABC" can only describe an example of "control information". Moreover, even when expressed as "control information (i.e., ABC)", "ABC" can also describe an example of "control information".

[0057] Furthermore, the terms "first," "second," etc., used in this disclosure are only used to distinguish one component from another and are not used to limit these components, and unless otherwise specified, do not limit the order, importance, etc., of the components. Therefore, a first component in one embodiment of this disclosure may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0058] In the following description, “when…”, “if…”, or “in the case of…” can be replaced with “based on”.

[0059] In this disclosure, a technical feature described individually in a figure may be implemented individually or together.

[0060] In this disclosure, a terminal refers to a user-side device (UE, UE) or a consumer-side device, and may also be referred to as a first node that receives or transmits signals to a base station / second node / Integrated Access and Backhaul (IAB) node or Transmit-Receive Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to an intermediate point between a user-side endpoint or other endpoints. In communication between two points (including one-to-one, many-to-one, one-to-many, and many-to-many communication) not limited to endpoints, a terminal may correspond to a served node. A terminal may be a node with a fixed location or a node with a non-fixed location (i.e., a mobile node).

[0061] In this disclosure, a base station (BS) refers to a network-side device and may also be referred to as a second node, an IAB node, an x-NodeB (where x may be an abbreviation related to Radio Access Technology (RAT)), or a Transmit-Receive Point (TRP). A base station may correspond to a physical node or a logical node. A base station may correspond to an intermediate point between network-side endpoints or other endpoints. In communication between two points (including one-to-one, many-to-one, one-to-many, and many-to-many communication) not limited to endpoints, a base station may correspond to a serving node. A base station may be a node with a fixed location or a node with a variable location.

[0062] In this disclosure, higher-layer parameters can be configured, pre-configured, or predefined for the UE. For example, the base station can send higher-layer parameters to the UE. For example, the UE can send parameters such as capabilities to the base station as higher-layer parameters. For example, higher-layer parameters can be sent via Radio Resource Control (RRC) signaling or Medium Access Control (MAC) signaling.

[0063] In this disclosure, when information / status / parameters are "configured or pre-configured," it can be interpreted as the information / status / parameters being provided or pre-provided to the UE via predefined signaling (e.g., SIB, MAC, RRC) from the base station. In this disclosure, when information / status / parameters are "defined or pre-defined," it can be interpreted as the information / status / parameters being known or stored in advance by both the base station and the UE without the need for signaling between them.

[0064] The techniques described in this disclosure can be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA). CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / GSM Evolution Enhanced Data Rate (EDGE). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Evolved UTRA (E-UTRA), Long Term Evolution (LTE), or 5G New Radio (NR).

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

[0066] A. 6G network architecture

[0067] Figure 1 The diagram illustrates an example of a flexible network topology applicable to this disclosure.

[0068] To compensate for incomplete network coverage areas, a more flexible and resilient split radio access network (RAN) topology can be considered. For this purpose, applications such as... Figure 1 The diagram illustrates various nodes such as IAB nodes, repeaters, and RF repeaters, and NTN can also be integrated. For example, an IAB node can correspond to a node that provides wireless backhaul. For example, a repeater can refer to any intermediate point, and in the case of a UE acting as a side-link repeater, it can be collectively referred to as a UE-to-network (U2N) repeater and a UE-to-UE (U2U) repeater. For example, an RF repeater can correspond to a node that performs simple signal amplification and transfer, and in the case of a network-controlled repeater, it can not only perform signal amplification and transfer but also adjust the transmit and receive configurations based on information provided from the network. For example, an NTN node can correspond to a satellite or aircraft that provides NTN coverage that is difficult for terrestrial networks to provide. In addition to these examples, various other intermediate points can be introduced to improve the network topology.

[0069] Reference Figure 1 A split RAN can support dividing a base station into a centralized unit (CU) and one or more distributed units (DUs). CUs and DUs can correspond to logical units. A CU can be further divided into a control plane (CP) portion and one or more user plane (UP) portions. Faults in a CU-CP can affect not only CU-UPs but also DUs; therefore, various intermediate points can be introduced to compensate for this.

[0070] Intermediate nodes can correspond to either a UE or a base station based on their relative relationship with other nodes. For example, an IAB node may include a Mobile Terminal (MT) portion and a DU. The MT can connect the IAB node to a donor node. The DU of an IAB node can provide services to other UEs or connect to another IAB node to provide multi-hop radio backhaul to the UE. In other words, an IAB node can correspond to a base station in relation to user-side nodes, and to a UE in relation to network-side nodes.

[0071] In some examples of this disclosure, the description of the UE can be applied equally not only to the user-side endpoint but also to the intermediate point corresponding to the UE in relation to the network-side endpoint. Similarly, in some examples of this disclosure, the description of the base station can be applied equally not only to the network-side endpoint but also to the intermediate point corresponding to the base station in relation to the user-side endpoint. However, where no additional description is provided for the operation of three or more entities in most cases, the communication entities in this disclosure are briefly described by the terms UE and / or base station (or first node and / or second node), wherein the terms UE and / or base station (or first node and / or second node) are to be interpreted as including or replacing any endpoint or intermediate point depending on the relationship with other nodes.

[0072] In other words, in some examples of this disclosure, for the sake of brevity, the subjects of the operation may be referred to as a base station and / or a UE (or a first node and / or a second node). Furthermore, the terms base station and / or UE (or a first node and / or a second node) may be interpreted or replaced as follows: for example, the base station (or the first node) and the UE (or the second node) may correspond to a first endpoint and a second endpoint, respectively; they may correspond to an endpoint and an intermediate point, respectively; they may correspond to an intermediate point and an endpoint, respectively; or they may correspond to a first intermediate point and a second intermediate point, respectively.

[0073] In this disclosure, there may be no intermediate point between the base station and the UE, or there may be one or more intermediate points. When an intermediate point exists, it may correspond to an IAB node, repeater, RF repeater, non-terrestrial network (NTN) node, or a node supporting other functions. The intermediate point may be a node with a fixed location or a node with a variable location.

[0074] Systems applicable to this disclosure

[0075] Figure 2 The diagram illustrates an example of the structure of a wireless communication system applicable to this disclosure. Application of this disclosure... Figure 2 The communication system 100 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 radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR, 5G, 5G-A, 6G) and may be referred to as a communication / radio / 5G / 6G device. Not limited thereto, the wireless device 110 may include robots 110a, vehicles 110b-1 and 110b-2, extended reality (XR) devices 110c, handheld devices 110d, home appliances 110e, Internet of Things (IoT) devices 110f, and artificial intelligence (AI) devices / servers 110g. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, or vehicles capable of performing vehicle-to-vehicle communication, and vehicles 110b-1 and 110b-2 may include unmanned aerial vehicles (UAVs) such as drones. XR device 110c may include augmented reality (AR), virtual reality (VR), or mixed reality (MR) devices, and can be implemented in the form of a head-up display (HMD), a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, or a robot. Handheld device 110d may include a smartphone, a smart tablet, a wearable device (e.g., a smartwatch, smart glasses), or a computer (e.g., a laptop computer). Home appliance 110e may include a television, a refrigerator, or a washing machine. IoT device 110f may include sensors or smart meters. Wireless device 110 may correspond to a UE (or a first node) or an intermediate point. Network device 120 may correspond to a base station (or a second node) or another intermediate point. For example, network device 120 may also be implemented as wireless device 110, and a particular wireless device 120a may act as a network device 120 for another wireless device 110.

[0076] Wireless devices 110a to 110f can be connected to network 130 via network device 120. AI technology can be applied to wireless devices 110a to 110f, and wireless devices 110a to 110f can be connected to AI server 110g via network 130. 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. Wireless devices 110a to 110f can communicate with each other via network device 120 / network 130, but can also communicate directly without going through network device 120 / network 130 (e.g., via sidelink communication). For example, vehicles 110b-1 and 110b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) or vehicle-to-everything (V2X) communication). Furthermore, IoT device 110f (e.g., a sensor) can perform direct communication with another IoT device (e.g., another sensor) or with another wireless device 110a to 110f.

[0077] Wireless communication / connections 150a, 150b, and 150c can be established between wireless devices 110a to 110f and network device 120, as well as among network devices 120. Here, the wireless communication / connections can be established using 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, integrated access backhaul (IAB)). Through wireless communication / connections 150a, 150b, and 150c, wireless devices can send and receive wireless signals to and from each other, as well as between network devices. For example, wireless communication / connections 150a, 150b, and 150c can send and receive signals through various physical channels. Therefore, based on the various descriptions of this disclosure, at least a portion of various configuration information, various signal processing procedures (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation procedures can be executed for configuring the process of sending / receiving wireless signals.

[0078] Applicable apparatus of this disclosure

[0079] Figure 3 The illustration shows an example of a wireless device applicable to this disclosure.

[0080] Reference Figure 3 The wireless device 200 can transmit / receive radio signals through various wireless access technologies (e.g., LTE, LTE-A, pre-LTE-A, NR, 5G, 5G-A, 6G). The wireless device 200 may include at least one processor 202 and at least one memory 204, and further include at least one transceiver 206 and / or at least one antenna 208.

[0081] Processor 202 may be configured to control memory 204 and / or transceiver 206 and implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, processor 202 may generate a first information / signal by processing information in memory 204 and then transmit a radio signal including the first information / signal via transceiver 206. Additionally, processor 202 may receive a radio signal including a second information / signal via transceiver 206 and then store information obtained from the signal processing of the second information / signal in memory 204. Memory 204 may be connected to processor 202 and store various information associated with the operation of processor 202. For example, memory 204 may store software code including instructions for implementing some or all of the processes controlled by processor 202 or for implementing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology. Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via at least one antenna 208. Transceiver 206 may be a transmitter and / or a receiver. Transceiver 206 may be used interchangeably with a radio frequency (RF) unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0082] The hardware elements of the wireless device 200 will be described in further detail below. Although not limited thereto, at least one processor 202 may implement at least one protocol layer (e.g., functional layers such as Physical (PHY), Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), and Service Data Adaptation Protocol (SDAP)). At least one processor 202 may generate at least one Protocol Data Unit (PDU) and / or at least one Service Data Unit (SDU) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts 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 flowcharts disclosed in this document. At least one processor 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide such signals to at least one transceiver 206. At least one processor 202 may receive signals (e.g., baseband signals) from at least one transceiver 206 and obtain PDUs, SDUs, messages, control information, data, or information, in accordance with the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document.

[0083] 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. As an example, at least one 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, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be included in at least one processor 202, or may be stored in at least one memory 204 and executed by at least one processor 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or instruction sets.

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

[0085] At least one transceiver 206 can transmit user data, control information, and radio signals / channels mentioned in the methods and / or operation flowcharts of this document to at least one other device. At least one transceiver 206 can receive user data, control information, and radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document from at least one other device. For example, at least one transceiver 206 can be connected to at least one processor 202 to transmit and receive radio signals. For example, at least one processor 202 can control at least one transceiver 206 to transmit user data, control information, or radio signals to at least one other device. Additionally, at least one processor 202 can control at least one transceiver 206 to receive user data, control information, or radio signals from at least one other device. Furthermore, at least one transceiver 206 can be connected to at least one antenna 208, and at least one transceiver 206 can be configured to transmit and receive user data, control information, and radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document via at least one antenna 208. In this document, at least one antenna may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). At least one transceiver 206 can convert received radio signals / channels from RF band signals to baseband signals to facilitate processing of received user data, control information, and radio signals / channels using at least one processor 202. At least one transceiver 206 can convert user data, control information, and radio signals / channels processed using at least one processor 202 from baseband signals to RF band signals. For this purpose, at least one transceiver 206 may include (analog) oscillators and / or filters.

[0086] Reference Figure 3 The components of the described wireless device may be referred to by other terms in terms of their function. For example, processor 202 may be referred to as a control unit, transceiver 206 as a communication unit, and memory 204 as a storage unit. In some cases, "communication unit" may be used to mean at least a portion of processor 202 and transceiver 206.

[0087] Reference Figure 3 The described wireless device structure can be understood as at least a part of various device structures. For example, Figure 3 The structure of the wireless device shown in the diagram can be compared with that of the reference. Figure 2 At least a portion of the various devices described (e.g., robots 110a, vehicles 110b-1 and 110b-2, XR device 110c, handheld device 110d, home appliance 110e, IoT device 110f, and AI device / server 110g) correspond to each. Furthermore, according to various embodiments, in addition to Figure 3 In addition to the components shown in the diagram, the device may also include other components.

[0088] For example, the device can be a handheld device, such as a smartphone, smart tablet, wearable device (e.g., smartwatch, smart glasses), and handheld computer (e.g., laptop computer, etc.). In this case, the device may further include at least one of the following: a power supply unit that supplies power and includes wired / wireless charging circuitry, a battery, etc.; an interface unit that includes at least one port for connecting to 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 from the user.

[0089] For example, the device can be a mobile device, such as a mobile robot, vehicle, train, manned / unmanned aerial vehicle (AV), and ship. In this case, the device may further include at least one of the following: a drive unit, which includes at least one of the device's engine, electric motor, power transmission system, wheels, brakes, and steering mechanism; a power supply unit, which supplies power and includes wired / wireless charging circuitry, batteries, etc.; a sensor unit, which senses state information, environmental information, and user information of the device or its surroundings; an autopilot unit, which performs functions such as route maintenance, speed control, and destination setting; and a position measurement unit, which obtains the location information of the moving object through a Global Positioning System (GPS) and various sensors.

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

[0091] For example, the device may be a robot, which can be classified according to its purpose or field of use, such as industrial use, medical use, domestic use, military use, etc. In this case, the device may further include at least one of the following: a sensor unit that senses state information, environmental information, and user information of the device or its surroundings; and a drive unit that moves the robot joints and performs various other physical operations.

[0092] For example, the device can be an AI device such as a television, projector, smartphone, personal computer, laptop computer, digital broadcasting terminal, tablet PC, wearable device, set-top box (STB), radio, washing machine, refrigerator, digital signage, robot, and vehicle. In this case, the device may also include at least one of the following: an input unit that receives various types of data from the outside; an output unit that generates outputs associated with vision, 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 uses learning data to learn a model composed of an artificial neural network.

[0093] Figure 3 The structure of the wireless device illustrated can be understood as part of a UE (or first node), part of an intermediate point, or part of a base station (or second node). When Figure 3 When the illustrated device is a base station (or a second node), it may also include a wired transceiver for fronthaul and / or backhaul communication. However, when fronthaul and / or backhaul communication is based on wireless communication, it may use... Figure 3 At least one transceiver 206 shown in the figure performs forward and / or backhaul communication, and may not include a wired transceiver.

[0094] B. Communication process

[0095] Figure 4 The illustration is an example of a communication process applicable to a first node (e.g., a UE) and a second node (e.g., a base station) in this disclosure. Figure 1 The second node can support Dynamic Spectrum Sharing (DSS) and can provide connectivity not only to nodes implementing 6G technology but also to nodes implementing pre-6G wireless communication technologies (such as 5G and 4G). In other words, Figure 1 The first node can implement 6G technology, or it can implement pre-6G wireless communication technologies (such as 5G, 4G). In addition, the first node and / or the second node can support not only non-overlapping full-duplex mode, but also full-duplex mode.

[0096] exist Figure 4 For the sake of brevity, it is assumed that the first node and the second node are the UE and the base station, respectively, and the diagram illustrates the operations of UE440 and base station 420 in sending and / or receiving data, as well as the operations performed before them. Figure 1 The operation is not limited to the operation between the UE and the base station, and can be interpreted as the operation between the first node and the second node. Furthermore, although... Figure 1The diagram illustrates a direct wireless signal transmission / reception operation between UE 440 and base station 420. However, there may be one or more intermediate points between UE 440 and base station 420, and wireless signals can be transmitted and received through one or more intermediate points.

[0097] Reference Figure 4 In step 401, UE 440 and base station 420 perform synchronization. For example, UE 440 may perform an initial cell search operation. Specifically, UE 440 may detect at least one synchronization signal for base station connection transmitted by base station 420 according to predefined rules. Here, the synchronization signal may include multiple synchronization signals classified according to structure or purpose (e.g., a first synchronization signal (e.g., a primary synchronization signal), a second synchronization signal (e.g., a secondary synchronization signal), etc.). Through this operation, UE 440 can identify the boundaries of units (e.g., frames, subframes, time slots, and / or symbols) configuring radio signal transmission by base station 420, and can obtain information related to base station 420 (e.g., cell identifier).

[0098] In step 403, UE 440 obtains system information sent from base station 420. System information is information related to the attributes, characteristics, and / or capabilities of base station 420 that is necessary for the UE to access base station 420 and use services. It can be categorized according to content (e.g., whether it is necessary for access), transmission structure (e.g., which channel is used, whether it is provided on demand), etc. For example, system information can be divided into first system information (e.g., main information block (MIB), main system information) and second system information (e.g., system information block (SIB), secondary system information). If necessary, UE 440 may send a signal requesting system information before receiving it. However, the request and provision of system information can be performed after the random access procedure described below.

[0099] In step 405, UE 440 and base station 420 perform a random access procedure. UE 440 may send and / or receive at least one message for the random access procedure (e.g., random access preamble, random access response (RAR) message, etc.) based on channel information (e.g., channel location, channel structure, supported preamble structure, etc.) related to the random access procedure of base station 420 obtained through system information. For example, UE 440 may send a first message (e.g., preamble, MSG1), receive a second message (e.g., RAR message, MSG2) through the channel used for the random access procedure, send a third message (e.g., MSG3) to base station 420 including information related to UE 440 (e.g., identification information) using scheduling information included in the second message, and receive a fourth message (e.g., MSG4) for contention resolution and / or connection establishment. In another example, the first and third messages may be sent and received as a single message, or the second and fourth messages may be sent and received as a single message.

[0100] In step 407, UE 440 and base station 420 perform signaling interaction for control information. Here, control information can be defined in various layers, such as layers for controlling connections (e.g., Radio Resource Control (RRC) layer), layers for handling the mapping between logical channels and transport channels (e.g., Medium Access Control (MAC) layer), and layers for handling physical channels (e.g., Physical (PHY) layer). For example, UE 440 and base station 420 can execute at least one of the following signaling: signaling for establishing a connection, signaling for determining communication-related configurations, and signaling for indicating allocated resources.

[0101] In step 409, UE 440 and base station 420 transmit and / or receive data. In other words, UE 440 and base station 420 can process and transmit and / or receive data based on signaling of control information. For example, when transmitting data, UE 440 or base station 420 can perform at least one of channel coding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. Conversely, when receiving data, UE 440 or base station 420 can perform at least one of extracting signals from resources, waveform demodulation per antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0102] C.6G System Core Technology

[0103] As the core implementation technology of 6G systems, technologies such as artificial intelligence (AI), terahertz (THz) communication, optical wireless technology, free space light (FSO) backhaul network, massive MIMO technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cellless communication, wireless information and power transfer (WIET), integrated sensing and communication, integrated access and backhaul network, holographic beamforming, big data analysis, and large smart surfaces (LIS) can be adopted.

[0104] C-1. Artificial Intelligence

[0105] Introducing artificial intelligence (AI) into communications can simplify and enhance real-time data transmission. AI can determine how to perform complex tasks by using extensive analysis. In other words, AI can improve efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly by AI. AI can also play an important role in M2M, machine-to-human, and human-to-machine communications. Furthermore, AI can enable high-speed communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, smart structures, smart networks, smart devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0106] [Functional Framework]

[0107] The following describes the functional framework used for AI / ML operations.

[0108] To describe AI (or AI / ML) more specifically, the terminology can be defined as follows.

[0109] - Data Acquisition: Data collected from network nodes, management entities, or user units (UEs) to form the basis for AI model training, data analysis, and inference.

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

[0111] - AI / ML Training: Training AI models by learning functions and patterns that best represent the data and enable inference, either online or offline, to obtain the trained AI / ML model.

[0112] - AI / ML Inference: The process of predicting or deriving decisions based on collected data and the AI ​​model, using a trained AI model.

[0113] The lifecycle management (LCM) process for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updates, etc.) can be categorized into function-based LCM and model-based LCM. In function-based LCM, the AI / ML model may not be identifiable within the network, and the network can instruct the activation / deactivation / rollback / switching of AI / ML functions. In model identifier (ID)-based LCM, the AI / ML model can be identified within the network, and the network / UE can activate / deactivate / select / switch the AI / ML model using the model ID.

[0114] Figure 5 The illustration shows an example of a general functional architecture related to both function-based LCM and model-based LCM. Figure 5 Some functions or parts of the data / information / command flow (i.e., arrows) shown in the diagram may be omitted.

[0115] Reference Figure 5 The general functional framework can be configured to include data acquisition function 510, model training function 520, management function 530, inference function 540, and model storage function 550.

[0116] Data acquisition function 510 provides input data to model training function 520, management function 530, and inference function 540. Data acquisition function 510 can perform data preparation based on raw data, and can provide input data for processing through this data preparation. Examples of raw data may include received or measured data from the UE or other network entities, as well as inference results or outputs from AI / ML models. Data acquisition function 510 can be performed by a single entity (e.g., UE, network node, etc.) or by multiple entities.

[0117] Here, training data 511 refers to the data required as input to the AI / ML model training function 520. Monitoring data 512 refers to the data required as input to the AI / ML model or AI / ML function management function 530. Inference data 513 refers to the data required as input to the AI / ML inference function 530.

[0118] The model training function 520 performs AI / ML model training, validation, and testing that can generate model performance metrics that can be used as part of the AI / ML model testing process. When necessary, the model training function 520 can perform data preparation (such as data preprocessing and cleaning, formatting, and transformation) based on the training data 511 transmitted from the data acquisition function 510.

[0119] Training / Updated Model 521: If model storage function 550 exists, it is used to transfer the AI / ML model that is being trained, validated, and tested to model storage function 550, or to transfer an updated version of the model to model storage function 550.

[0120] Management function 530 supervises the operation of AI / ML models or AI / ML functions. In addition, management function 530 can make decisions based on data received from data acquisition function 510 (i.e., monitoring data 512) and / or data received from inference function 540 (i.e., inference output 541) to ensure appropriate inference operations.

[0121] Management instruction 532 refers to the information required as input to management inference function 540. This information may include the selection / deactivation / switching of an AI / ML model or AI / ML-based function, and may also include fallback to non-AI / ML operations (i.e., operations independent of the inference process).

[0122] Model transfer / delivery request 533 can be used to request one or more models from model storage function 550.

[0123] Performance feedback / retraining request 531 refers to the information required as input to model training function 520 (e.g., for model retraining or model update purposes).

[0124] The inference function 540 uses the data provided by the data acquisition function 510 (i.e., inference data 513) as input to apply an AI / ML model or AI / ML function to provide output. The inference function 540 can perform data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) based on the inference data 513 transmitted by the data acquisition function 510. If necessary, the inference function 540 can also perform data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) based on the inference data 513 provided by the data acquisition function 510.

[0125] Inference output 541 is data used by management function 530 to monitor the performance of AI / ML models or AI / ML functions. Inference output 541 may include the inference output of the AI / ML model generated by inference function 540, and the details of the inference output may vary depending on the use case.

[0126] The model storage function 550 stores the trained / updated model that can be used to perform the inference function 540. Figure 5 The illustrated model storage function 550 can serve as a reference point for protocol termination, model transfer / transmission, and related processes where applicable. Furthermore, model storage function 550 is merely an example and is not intended to limit the actual storage location of AI / ML models; this function can be omitted.

[0127] Model transfer / delivery 551 is used to deliver AI / ML models to inference functions.

[0128] Based on the AI / ML capabilities of multiple nodes, the collaboration level can be defined as follows, and can be modified by combining multiple levels or separating any one level.

[0129] Level 0a) No collaborative framework: AI / ML algorithms are purely based on the implementation method and do not require any modification to the wireless interface.

[0130] Level 0b) This level corresponds to a non-cooperative framework, but involves a modified wireless interface that is adapted to an effectively implemented AI / ML algorithm.

[0131] Level 1 involves node-to-node assistance to improve the AI / ML algorithm on each node. For example, this applies when a particular node receives assistance from another node (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.

[0132] Level 2) enables joint AI / ML operations across multiple nodes. This level requires AI / ML model commands or exchanges between network nodes.

[0133] Figure 5 This is an attached diagram illustrating the overall functional framework of an AI / ML model, and Figure 5 The diagram shows that not all functions and / or all data / information / command signals can be executed within a specific node; perhaps only a portion of them can be executed.

[0134] AI / ML models can be classified as one-sided or two-sided models based on whether training and / or inference are performed within a single node or jointly / sequentially across multiple nodes.

[0135] A one-sided model can refer to an AI / ML model inference performed entirely by a single node (e.g., UE or network). Here, training of the AI / ML model can also be performed entirely by a single node. Training and inference of the AI / ML model can be performed by the same node, or they can be performed by different nodes.

[0136] Two-sided models refer to AI / ML models that perform joint inference across multiple nodes (e.g., UE and network). Joint inference means that inference is performed jointly across multiple nodes; for example, the first part of the inference can be performed by the first node, while the remaining part can be performed by the second node. Two-sided models can be classified into several types based on the training methods used to train AI / ML models.

[0137] - Type 1: AI / ML models can be trained on a single node. In this case, joint training can be performed. The trained model can then be distributed to other nodes or entities.

[0138] - Type 2: Joint training of AI / ML models can be performed at multiple nodes or entities (e.g., network and UE). Joint training can refer to model generation (e.g., CSI generation part) and model reconstruction (for CSI compression of sub-use cases) being trained on forward activation and backward gradients within the same loop. Under this type, joint training can include both synchronous training (i.e., performing model generation training and model reconstruction training simultaneously) and sequential training (i.e., performing model reconstruction training after model generation training).

[0139] - The third type: AI / ML models can be trained separately at multiple nodes (e.g., network and UE). Separate training can refer to starting training sequentially at one node and then continuing training at another node. In this case, when the first node executes the AI / ML model first and shares training data with the second node, the second node can use the shared training data to execute the AI / ML model. For example, the training of the CSI generation part can be performed by the UE, while the CSI reconstruction can be performed by the network.

[0140] In this disclosure described below, even if not specifically mentioned (i.e., not explicitly referenced as such as by / based on / for AI / ML models), the operations presented in this disclosure may be described or interpreted as being based on AI / ML models, such as Figure 6 As shown in the diagram. Figure 6 The illustration is an example of the operation process based on the AI / ML model applicable to this disclosure.

[0141] Furthermore, unless otherwise specifically defined in the description of this disclosure, an AI / ML model may correspond to a one-sided model in which inference is performed entirely by a single node, or to a two-sided model in which joint inference is performed across multiple nodes.

[0142] Step 1: In the description provided below, signaling (e.g., information / data / channel / signaling, etc.) between a specific node (e.g., UE, network, etc.) and another node, even if not explicitly mentioned, can be interpreted as the signaling or set of signaling used in Step 1 to perform operations based on the AI / ML model. For example, such signaling may correspond to... Figure 2The diagram illustrates training data used for AI / ML model training (i.e., generation and / or reconstruction), or inference data applied to AI / ML model inference, or corresponding feedback to the AI / ML model. Step 1 can be omitted if signaling between nodes is not required before operations based on the AI / ML model in this disclosure. When a one-sided model is used in this disclosure, the one-way / two-way signaling (sets) in this disclosure can correspond to the signaling in step 1. Furthermore, when a two-sided model is used in this disclosure, the one-way / two-way signaling in this disclosure can also correspond to the signaling in step 1, and repeated signaling operations can also correspond to the signaling in step 1.

[0143] For example, in AI / ML model-based beam management (BM), when the base station predicts (i.e., infers) a high-quality beam based on the AI / ML model, the base station can receive quality / strength information of multiple beams from the UE. Similarly, when the UE predicts (i.e., infers) a high-quality beam based on the AI / ML model, the UE can receive multiple beams from the base station.

[0144] Step 2: In the description of this disclosure provided below, an operation (e.g., computation, selection, prediction, etc.) performed at a specific node (e.g., UE, network, etc.) or a joint operation (e.g., computation, selection, prediction, etc.) performed at multiple nodes (e.g., UE, network, etc.), even if not explicitly mentioned, may correspond to the operation of Step 2 based on one or more functions within the AI / ML model functional framework. For example, this may correspond to... Figure 2 The diagram illustrates the training (i.e., generation and / or reconstruction) or inference of the AI / ML model. When using a one-sided model, the operation performed by a single node in this disclosure may correspond to the operation in step 2; furthermore, when using a two-sided model, the joint operation performed by multiple nodes in this disclosure may correspond to the operation in step 2.

[0145] For example, in a BM based on an AI / ML model, the base station can use the quality / strength information of multiple beams received from the UE as inference data and predict (i.e., infer) a high-quality beam based on the AI / ML model. Similarly, the UE can measure multiple beams received from the base station, use the measurement results as inference data, and predict (i.e., infer) a high-quality beam based on the AI / ML model.

[0146] Step 3: In the description provided below, the signaling (e.g., information / data / channel / signaling, etc.) between a specific node (e.g., UE, network, etc.) and another node, even if not explicitly mentioned, can be interpreted as the signaling or set of signaling in Step 3 generated based on the operational results of the AI / ML model. For example, this could correspond to... Figure 2The output obtained from AI / ML model inference is illustrated in the figure. If the operation results based on the AI / ML model in this disclosure do not require signaling between nodes, then step 3 can be omitted. When a one-sided model is used in this disclosure, the one-way / two-way signaling (sets) in this disclosure can correspond to the signaling in step 3. Furthermore, when a two-sided model is used in this disclosure, the one-way / two-way signaling in this disclosure can also correspond to the signaling in step 3, and repeated signaling operations can also correspond to the signaling in step 3.

[0147] For example, in a BM based on an AI / ML model, the base station can send one or more beams predicted by the AI / ML model as candidate beams to the UE, allowing the UE to determine the optimal beam. Furthermore, the UE can report one or more beams predicted by the AI / ML model as candidate beams to the base station, requesting the base station to send candidate beams for determining the optimal beam.

[0148] C-2.THz Communication

[0149] Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced massive MIMO technology. THz waves, also known as submillimeter-wave radiation, generally refer to the frequency band between 0.1 THz and 10 THz, corresponding to wavelengths of 0.03 mm to 3 mm. The frequency range of 100 GHz–300 GHz (sub-THz band) is considered the main part of the THz band for cellular communication. Adding sub-THz bands to the millimeter-wave band can increase the capacity of 6G cellular communication. Among the defined THz bands, the 300 GHz–3 THz range belongs to the far-infrared (IR) frequency region. The 300 GHz–3 THz range is part of the optical band, but it is located at its boundary, immediately following the RF band. Therefore, the 300 GHz–3 THz range exhibits similarities to the RF band. Figure 7 The illustration shows an example of the electromagnetic spectrum applicable to this disclosure. Figure 7 The implementation can be combined with various other implementations. Key characteristics of THz communication include (i) a wide range of available bandwidth supporting extremely high data transmission rates, and (ii) high path loss occurring in the high-frequency band (highly directional antennas are indispensable). The narrow beamwidth generated by highly directional antennas can reduce interference. The short wavelength of THz signals allows for the integration of a much larger number of antenna elements in devices and base stations operating in this band. This enables the use of advanced adaptive array techniques that overcome range limitations.

[0150] In the THz band, transmitting system information (i.e., information related to base station attributes, characteristics, and / or capabilities required for service use, such as MIB and SIB) can be inefficient because beamwidth is narrower in higher frequencies, requiring more frequent beam scans to cover the entire cell area. This inefficiency is even lower when the number of users within a cell is small. Therefore, alternative methods such as... Figure 8 The system information sending process is illustrated in the figure.

[0151] (System Information Receiving Method)

[0152] Figure 8 The illustration shows an example of a process for transmitting system information applicable to THz communication as described in this disclosure. Although this example is described with consideration of a THz scenario, it can also be applied to 6G communication environments that do not use THz. Furthermore, Figure 8 The illustrated process can be combined with various embodiments of this disclosure described below. For example, the embodiments described below can be based on... Figure 8 The system information obtained from the process illustrated is used for execution.

[0153] Reference Figure 8 In step 801, base station 820 transmits system information of cell #1 through cell #2. That is, base station 820 provides at least two cells, where cell #1 uses the 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 piece of information / status / parameter / configuration generated at each of the higher layers and the physical layer. For example, at least one piece of information / status / parameter / configuration generated at a higher layer may include at least one of SFN, SIB1 control information configuration (e.g., SIB1 PDCCH configuration), cell selection / entry related information (e.g., cell prohibition, cell reselection, etc.), and subcarrier spacing; at least one piece of information / status / parameter / configuration generated at the physical layer may include at least one of SFN, half-frame indicator, and SSB index. However, this is only an example; the system information may include information / status / parameter / configuration related to cell #1 and / or cell #2 generated at various types of physical layers and higher layers. Therefore, in one example, cell #1 and cell #2 may have a secondary cell and primary cell relationship.

[0154] In step 803, UE 810 obtains synchronization for cell #1. This synchronization can be obtained by detecting a synchronization signal. Normally, synchronization is obtained before receiving system information; however, since the system information for cell #1 is received via cell #2, synchronization acquisition for cell #1 can be performed after receiving the system information. For example, UE 810 can obtain synchronization based on the system information. But compared to... Figure 8In contrast, in another example, synchronous fetching can be performed before step 801.

[0155] In step 805, UE 810 transmits a signal for accessing cell #1. For example, this signal may include information for accessing cell #1 (e.g., a random access preamble). The structure of the signal and the resources (e.g., channels) used to transmit it can be determined through system information. Subsequently, in step 807, UE 810 and base station 820 perform the access procedure for cell #1 and initiate communication. In this step, operations corresponding to various embodiments described below can be performed.

[0156] Reference Figure 8 The described procedure can be performed when UE 810 initially accesses cell #1 of base station 820. Alternatively, a similar procedure can be performed when UE 810 is handed over to cell #1 of base station 820. However, in the case of handover, the system information of cell #1 can be received from a cell of another base station, rather than from cell #2 of base station 820.

[0157] Communication in the THz band is expected to encounter significant path loss. To overcome this problem, the UE and base station must use extremely narrow beams. The use of narrow beams means that the UE and base station must perform beam control during beamforming, and the number of beams used becomes very large. Therefore, beam alignment between the base station and UE for transmission and reception takes a considerable amount of time. Furthermore, when beam alignment between the base station and UE is disrupted due to UE movement or mobility, frequent beam realignment is required, which can cause link instability. Therefore, methods such as... Figure 9 The diagram illustrates the beam management process.

[0158] (Beam search process in THz communication environment)

[0159] Figure 9 The illustration shows an example of a beam management process applicable to this disclosure. Figure 9 An example of a beam search and / or selection process for THz communication is shown, but this disclosure is not limited to THz environments and can also be applied to 6G communication environments. Furthermore, Figure 9 The processes illustrated herein can be combined with various embodiments of this disclosure described below. Here, the term beam can be interpreted as “spatial (configuration) information,” “spatial domain filter,” “spatial domain transmit filter,” “spatial domain receive filter,” or other terms with equivalent technical meaning that can distinguish a beam (e.g., reference signal, synchronization block (SSB) index, transmit / receive point (TRP), panel, cell, transmit point (TP), base station, or control resource related information, such as control resource set (CORESET) related information).

[0160] Reference Figure 9 In step 901, base station 920 configures resources for beam management. Here, resources may include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, base station 920 may utilize a beam search signal (BSS) for beam searching, which is spatially separated from existing downlink signals / channels. Here, the BSS may be transmitted based on a specific port for beam searching. This specific port may be different from the port used to transmit existing downlink signals / channels (e.g., synchronization signals such as SSBs or data channels such as Physical Downlink Shared Channels). The term BSS is defined for ease of explanation, and the technical concept of this embodiment is not limited to the term BSS itself. That is, signals transmitted based on specific ports defined / configured for beam searching are all within the scope of the technical concept of this embodiment.

[0161] In step 903, base station 920 transmits measurement signals using multiple transmit beams. For example, the measurement signals may include at least one of a reference signal and a synchronization signal. In this case, the measurement signals may be transmitted for all beams that need to be measured, and a multi-beam transmission method may be employed, which can simultaneously form multiple beams to reduce scan time. Here, multi-beam transmission may be performed based on at least one of multiple panels, subarrays, and true time delay (TTD).

[0162] In step 905, UE 910 sends a feedback signal to base station 920. This feedback signal indicates at least one beam selected by UE 910. UE 910 can select at least one preferred beam based on the measurement signal received in step 903. In step 907, UE 910 and base station 920 communicate. At this time, UE 910 and base station 920 can perform communication using the beam selected in step 905. When channel reciprocity is established, the transmission beam of UE 910 can also be determined through steps 903 and 905; therefore, the transmission operation of UE 910 can be performed using the beam selected in step 905. If channel reciprocity is not established, a process including UE 910 transmitting a measurement signal and base station 920 transmitting a feedback signal can be pre-executed to determine the transmission beam of UE 910. In step 907, operations corresponding to various embodiments described below can be performed.

[0163] C-3. Non-terrestrial Network (NTN)

[0164] NTN can refer to a network or network segment that uses radio frequency (RF) resources mounted on satellites (or unmanned aerial vehicle (UAS) platforms). The use of NTN services is considered to provide wireless communication services to areas requiring wider coverage or where terrestrial base stations are difficult to install. NTN services can be collectively referred to as wireless communication systems that provide services to a UE by installing base stations on non-terrestrial platforms such as satellites (e.g., geostationary, low Earth orbit, or medium Earth orbit satellites), aircraft, unmanned airships, or drones. The satellites described in this disclosure can move at high speeds relative to specific locations on Earth, and the satellite beams pointed towards Earth can correspond to the Earth region where the satellite can provide services to the user.

[0165] In one example of this disclosure, NTN scenarios can be categorized into stationary cell scenarios and moving cell scenarios based on the cell type supported by the satellite. A stationary cell scenario refers to a scenario where cells are permanently maintained within a specific location on the surface or maintained for a specific service duration based on satellite beamforming capabilities. A moving cell scenario refers to a scenario where cells on the surface continuously move without using satellite beamforming capabilities and by providing service through fixed beams.

[0166] In another example of this disclosure, based on the characteristics of the payload, NTN scenarios can be classified into typical NTN scenarios based on transparent payloads and typical NTN scenarios based on regenerative payloads. Figure 10a The illustration is applicable to a typical NTN scenario example based on transparent payloads in this disclosure. Figure 10b The illustration is applicable to a typical NTN scenario example based on regenerative payloads disclosed herein. Figure 10a or Figure 10b The implementation methods can be combined with various implementation methods of this disclosure. See also... Figure 10a The satellite (or UAS platform) can establish a service link with the UE. The satellite (or UAS platform) can connect to the NTN gateway via a feed link. The satellite can then connect to the data network through this gateway. The beam coverage area refers to the region where the signal transmitted by the satellite can be received. (See reference...) Figure 10b A satellite (or UAS platform) can establish a service link with the UE. A satellite (or UAS platform) connected to the UE can connect to another satellite (or another UAS platform) via an inter-satellite link (ISL). The other satellite (or another UAS platform) can connect to the gateway via a feed link. Based on regenerated payloads, a satellite can connect to the data network via another satellite and the gateway. When there is no inter-satellite link (ISL) between satellites, a feed link between the satellite and the gateway is required. Figure 10a and Figure 10bThis is merely an example of an NTN scenario; NTN can be implemented based on various types of scenarios. For example, a satellite (or UAS platform) can implement a transparent payload or a regenerative payload (with on-board processing). For example, a satellite (or UAS platform) can generate multiple beams within a specified service area based on its field of view. For example, the field of view of a satellite (or UAS platform) can vary depending on the onboard antenna pattern and minimum elevation angle. For example, a transparent payload can include RF filtering, frequency conversion, and signal amplification, so the waveform signal repeated by the payload can remain unchanged. For example, a regenerative payload can include RF filtering, frequency conversion, signal amplification, demodulation / decoding, switching and / or routing, and encoding / modulation. For example, the functionality of a regenerative payload is essentially equivalent to configuring all or part of the functions of a base station on a satellite (or UAS platform).

[0167] The following describes the processes used to maintain network service continuity and satellite coverage in wireless communication systems that utilize NTN elements (e.g., initial cell selection, mobility management in idle mode, and mobility management in connected mode).

[0168] - Initial cell selection process

[0169] After the UE is powered on, it can search for the first satellite-based NTN cell (or the satellite broadcasting the cell's signal). If the UE already possesses satellite orbit information (i.e., ephemeris data) and / or round-trip time (RTT) information, which can be used during cell access procedures (e.g., random access procedures), the UE can utilize this information to shorten the cell search process and reduce the time required for cell search. To this end, the UE needs to obtain (initial) system information, including satellite orbit (ephemeris) information, to identify the precise location of the cell. This (initial) system information can be configured / determined / generated based on the orbital plane information already held by the UE. For example, the UE can be provided in advance with satellite-level orbital parameters of all satellites that can provide services to it via its uSIM, including satellite IDs or indices. Subsequently, since the system information includes and broadcasts the satellite IDs of the serving satellites, the UE can use these satellite IDs to deduce the relevant orbital data (ephemeris data) and / or the location coordinates of the serving satellites stored in the uSIM. Furthermore, to assist in mobility management, the UE can obtain relevant information about neighboring satellites through system information and / or specific RRC signaling.

[0170] Here, the satellite orbit (ephemeris) information sent to the UE via system information and / or RRC signaling can be implemented / supported in the following two formats: i) Position-Velocity State Vector orbit format; and ii) Orbit Parameter (ephemeris) format. For example, the Position-Velocity State Vector orbit format can include 17 bytes or less (i.e., 132 bits). The field size for the position (x, y, z) (in meters) can be 78 bits, and the field size for the velocity (vx, vy, vz) (in meters per second) can be 54 bits.

[0171] The Orbit Parameter ephemeris format can be composed of 21 bytes or fewer bytes (e.g., 164 bits). Figure 11a Illustration of an example of the components of the Orbit Parameter ephemeris format. Figure 11a The components of the illustrated Orbit Parameter ephemeris format are as follows.

[0172] - Semi-major axis (half of the major axis of the satellite's elliptical orbit) "α" [m] (e.g., 33 bits)

[0173] - Eccentricity "e" (in the satellite's elliptical orbit, where 0 < e < 1) (e.g., 20 bits)

[0174] - Argument of perigee (the angle measured from the ascending node to the perigee (the point closest to the central body), thus determining the orientation of the ellipse in the orbital plane) "ω" [radians] (e.g., 28 bits)

[0175] - Longitude of the ascending node (the angle measured counterclockwise from a reference point (e.g., the vernal equinox of the solar system) to the ascending node (the point where the orbit crosses from below the reference plane to above it)) "Ω" [radians] (e.g., 28 bits)

[0176] - Inclination (the tilt of the ellipse relative to the reference plane, measured as the angle between the orbital plane and the reference plane at the ascending node) "i" [radians] (e.g., 27 bits)

[0177] - Mean anomaly (an angle that varies continuously with time, having mathematical convenience but not corresponding to a geometric angle) "M" = mean anomaly M(t0) [radians] at epoch time t0 [Julian day] (e.g., 28 bits)

[0178] - Mobility management in the idle mode

[0179] During idle mode, the UE's location can be identified at the tracking area level or at the tracking area cell level. Here, a tracking area is defined as a group of cells, and each cell can belong to a tracking area identified by a Tracking Area Code (TAC). The TAC can be sent via system information broadcast channel. Multiple cells can belong to the same tracking area, and the same TAC corresponding to that same tracking area can be broadcast. The UE's location can be known to the network when the UE is first powered on (i.e., during the registration process). The registration request message sent by the UE for the registration process can include the TAC of the cell where the UE is currently camped. When the UE moves and changes cells, it can determine the tracking area of ​​the new cell by decoding the system information of the new cell. The UE can move within the same tracking area without performing an update. When the UE enters a new cell with a different TAC, the UE can perform registration in the new cell and send a new TAC to update its location to the network. Therefore, the larger the tracking area becomes, the less signaling the UE sends to the network, thereby minimizing the UE's power consumption. When the network needs to locate a UE in idle mode (e.g., for call access), it can page the UE in all cells belonging to the tracking area (TAC) where the UE last registered. If the tracking area is very large and includes multiple cells, the network needs to page the UE in all cells to which the TAC belongs, increasing the number of paging messages. When this same pattern is applied to a satellite system where each satellite broadcasts a TAC, the tracking area can be scanned across regions on the ground as the satellite orbits the Earth. In this case, even a stationary UE needs to frequently perform registration updates, which affects the UE's battery life and increases uplink signaling. To solve this problem, the system can be designed so that the tracking area does not change its geographical location on Earth. The alternative tracking area moves with the satellite, which can switch its tracking area when entering a new geographical area, and the satellite-broadcast TAC can be updated to reflect the corresponding new geographical area. Simultaneously, when the UE detects a new TAC on the broadcast channel, it can perform a tracking area update process. Therefore, if the UE does not change its physical location on Earth, its tracking area can remain fixed.

[0180] - Mobility management in connected mode

[0181] While the UE is in connected mode, mobility management can be handled through handover. In terrestrial or NTN networks, handover can be triggered by the network based on signal quality measurements of the current cell and neighboring cells reported by the UE (i.e., measurement-based handover triggering). During handover, the service interruption time is defined as the time from when the UE stops transmitting and receiving with the source base station to when the UE resumes transmitting and receiving with the target base station. The interruption times for uplink and downlink can differ. In the downlink, the interruption time can be defined as the time from when the network sends a synchronized RRC reconfiguration message to when the target base station receives an RRC reconfiguration completion message. After sending the RRC reconfiguration message, the base station can no longer transmit data and can only resume communication after receiving the RRC reconfiguration completion message. In the uplink, the UE can theoretically continue transmitting data to the source base station before receiving the synchronized RRC reconfiguration message. In this case, the interruption time can be defined as the time from when the UE receives the synchronized RRC reconfiguration message to when the target base station receives the RRC reconfiguration completion message.

[0182] Because the propagation delay in satellite-based NTNs is much greater than that in terrestrial systems, additional latency may occur for mobility-related signals (e.g., measurement reports, handover (HO) command reception, HO requests / acknowledgments (when the target cell is served by another satellite)). Geostationary orbit (GEO) scenarios are characterized by significantly greater propagation delays than low Earth orbit (LEO) scenarios, but LEO scenarios require consideration of satellite movement. To avoid prolonged service interruptions, latency related to mobility-related signaling needs to be addressed in both scenarios. In addition to measurement-based handover as described above, the following handover triggering methods can also be used: handover triggering based on the UE's position relative to the satellite (or the distance between the UE and the satellite), handover triggering based on the target cell timing lead (TA), handover triggering based on deterministic satellite motion / local time, and handover triggering based on the source / target cell elevation angle. Additionally or alternatively, handover configuration and handover triggering conditions (e.g., UE / satellite position, or signal strength transmitted by the UE / satellite) can be provided to the UE in advance. For example, the UE can receive handover configuration and handover triggering conditions through information related to the new cell to which it will be handed over. Therefore, the UE can monitor the handover conditions and perform handover to the target cell when the conditions are met.

[0183] Furthermore, as mentioned above, since the round-trip time (RTT) of a wireless communication system using NTN elements is much greater than that of a terrestrial communication system, various offsets and TA values ​​can be configured / defined / indicated / signaled to achieve effective time and frequency synchronization. The following section describes the offsets (e.g., K_offset and k_mac), TA values, effective duration, and epoch time used for time / frequency synchronization in NTN-based wireless communication systems.

[0184] - K_offset and k_mac

[0185] Figure 11b The diagram illustrates an example of offsets in satellite-related links. Figure 11b In the diagram, K_offset represents the offset value corresponding to the RTT of the uplink time synchronization reference point (RP). Here, K_offset can correspond to the sum of the serving link RTT and the common TA (if indicated). Figure 11b In the diagram, k_mac represents the offset value corresponding to the RTT between the RP and the base station. For example, k_offset can be applied to at least one of the following: i) PUSCH transmission timing based on DCI and PUSCH scheduled by DCI, ii) PUSCH transmission timing based on Random Access Response (RAR), iii) PUSCH transmission timing based on configuration grant, iv) PUCCH transmission timing based on MsgB, and v) transmission timing of aperiodic SRS / CSI resources. For example, k_mac can be applied to UE actions and assumptions associated with the downlink configuration indicated by the MAC-CE command on the PDSCH. During beam fault recovery, for PRACH transmission in uplink slot n, the UE can monitor the corresponding PDCCH starting from downlink slot "n + k_mac + 4" within the corresponding RAR window.

[0186] Cell-specific K_offsets can be signaled via NTN-related system information (e.g., NTN-specific SIBs). The range of cell-specific K_offset values ​​(0 to 1023 milliseconds) can cover all scenarios. Differential UE-specific K_offsets can be signaled via MAC CE, and the corresponding differential UE-specific values ​​can range from 0 to 63 milliseconds. The total UE-specific K_offset value equals the cell-specific K_offset value minus the differential UE-specific K_offset value. The network can provide k_mac when downlink and uplink frame timings at the base station are misaligned. k_mac updates are not supported, and their value range is 1 to 512 milliseconds. When the UE does not receive a k_mac value from the network, the UE can assume k_mac = 0. In FR1, the reference SCS value for the K_offset unit can be 15 kHz.

[0187] - UE-specific TA and public TA

[0188] In NTN-based communication systems, the UE can calculate the TA based on its GNSS (Global Navigation Satellite System) capabilities (e.g., UE location) and higher-level parameters associated with satellite ephemeris transmitted from the base station. This TA is referred to as UE-specific. When no higher-level parameters associated with satellite ephemeris are received from the base station, the UE-specific TA can be set to 0. Therefore, the TA calculated based on common TA parameters (such as TACommon, TACommonDrift, and / or TACommonDriftVariation) sent by the base station as higher-level parameters is called the common TA. When the base station does not send common TA parameters, the common TA can be set to 0. Therefore, in an NTN-based communication system, the total TA value (T_TA) can be determined by... The calculation is as follows. Here, N_TA,offset represents the TA offset value provided to the UE for each serving cell, and N_TA represents the value derived based on the timing advance command.

[0189] Figure 11c The diagram illustrates an example of timing advance (TA) values ​​in a satellite-related link. Figure 11c As shown, the calculation of the UE-specific TA is used to compensate for the transmission delay on the serving link, while the calculation of the common TA is used to compensate for the transmission delay between the RP and the satellite.

[0190] - Effective duration and epoch time

[0191] The effective duration refers to the (maximum) time interval during which the UE can apply previously acquired auxiliary information (such as ephemeris of serving and / or neighboring satellites and common TA parameters) without needing to acquire new auxiliary information (from the epoch time). Configuration information related to the effective duration can be broadcast by the base station to each cell via system information related to the NTN (such as SIB19). For example, the effective duration range can include, but is not limited to, {5 seconds, 10 seconds, 15 seconds, 20 seconds, 25 seconds, 30 seconds, 35 seconds, 40 seconds, 45 seconds, 50 seconds, 55 seconds, 60 seconds, 120 seconds, 180 seconds, 240 seconds, 900 seconds}. The effective timer configured with the effective duration value can be (re)started at the epoch time of the auxiliary information. If new or additional auxiliary information is unavailable within the effective duration, the UE can assume that uplink synchronization has been lost.

[0192] The ephemeris and common TA parameters of the serving satellite can be signaled in the same SIB message and can share the same epoch time. When the epoch time is explicitly provided via SIB, the epoch time of the auxiliary information (i.e., satellite ephemeris and common TA parameters) corresponds to the start time of the DL subframe indicated by the SFN and subframe number signaled along with the auxiliary information. When the epoch time is not explicitly indicated via SIB, the epoch time of the auxiliary information can be implicitly assumed to be the end time of the SI window for transmitting NTN-specific system information (e.g., SIB19). When the epoch time is provided via dedicated signaling, the epoch time of the auxiliary information corresponds to the start time of the DL subframe and can be represented by the SFN and subframe number.

[0193] For the serving cell, when the epoch time is explicitly indicated by the SFN and subframe number, the UE can identify the corresponding frame as the frame corresponding to the next SFN after receiving the frame indicating the current SFN or epoch time. For neighboring cells, when the epoch time is explicitly indicated by the SFN and subframe number, the UE can identify the corresponding frame as the frame closest to receiving the frame indicating the epoch time.

[0194] C-4. Sensor and Communication Integration (ISAC)

[0195] Radio sensing is a technology that uses the instantaneous flux velocity, angle, and distance (range) of an object identified by radio frequency identification (RFI) to obtain information related to environmental characteristics and / or the characteristics of objects within that environment. Because RF sensing does not require connecting objects to devices via a network, it can provide object localization services without the need for dedicated equipment. The ability to obtain range, velocity, and angle information from RF signals enables a variety of novel functions, such as object detection, object recognition (e.g., vehicles, humans, animals, drones), high-precision positioning, tracking, and activity recognition. Radio sensing services can provide information to various industries (e.g., drones, smart homes, connected vehicles, factories, railways, public safety, etc.) to support applications such as intrusion detection, assisted driving and navigation, trajectory tracking, collision avoidance, traffic management, and health or traffic monitoring. In some cases, radio sensing can employ non-3GPP sensors (e.g., radar, cameras) to additionally support 3GPP-based sensing. For example, the operation of a radio sensing service, i.e., sensing operation, can depend on the transmission, reflection, and scattering of radio sensing signals. Therefore, radio sensing can provide an opportunity to upgrade existing communication systems from communication networks to radio communication and sensing networks.

[0196] Figure 12a and Figure 12b The illustration is applicable to the sensing operation example of this disclosure. Figure 12a and Figure 12b The embodiments shown can be combined with various embodiments of this disclosure. Specifically, Figure 12a The illustration shows an example of sensing using a sensor receiver and sensor transmitter located in the same location (e.g., monostatic sensing). Figure 12b The illustration shows an example of sensing using separate sensor receivers and sensor transmitters (e.g., bistatic sensing).

[0197] For example, in a wireless communication system based on a 6G network according to this disclosure, referring to Figure 12a The sensing transmitter and sensing receiver can be configured to be included in a single base station (i.e., the same base station) or a single UE (i.e., the same UE). Conversely, refer to Figure 12b The sensing transmitter and sensing receiver can be configured to be included in different base stations, different UEs, or separately in the UE and the base station.

[0198] Based on whether the sensing transmitter and sensing receiver are included in the base station or the UE, the following six sensing modes can be defined: - Mode 1: A mode in which the sensing transmitter and sensing receiver are included in a single base station (e.g., a base station-based sensing mode in a monobase mode). - Mode 2: A mode in which the sensing transmitter is included in a first base station and the sensing receiver is included in a second base station different from the first base station (e.g., a base station-based sensing mode in a bistatic mode). - Mode 3: A mode in which the sensing transmitter is included in the base station and the sensing receiver is included in the UE (e.g., base station to UE sensing mode). - Mode 4: A mode in which the sensing transmitter is included in the UE and the sensing receiver is included in the base station (e.g., UE-to-base station sensing mode). - Mode 5: A mode in which the sensing transmitter and sensing receiver are included in a single UE (e.g., a UE-based sensing mode in monobase mode). - Mode 6: A mode in which the sensing transmitter is included in a first UE and the sensing receiver is included in a second UE that is different from the first UE (e.g., a UE-based sensing mode in a bipolar mode). In the 6G network-based wireless communication system according to this disclosure, one or more of the above six sensing modes can be used independently or in combination.

[0199] Combination Figure 12a and Figure 12b The illustrated sensing operation involves a sensing transmitter that can transmit sensing signals for sensing one or more objects (and / or their surrounding environment). For example, this sensing signal may correspond to a radio frequency signal defined as transmittable by a base station or UE in a 6G-based wireless communication system according to this disclosure. A sensing receiver can receive signals scattered or reflected by one or more objects (and / or their surrounding environment) from the sensing signals transmitted by the sensing transmitter. At the sensing receiver, sensing data can be derived from the scattered / reflected signals, and sensing results can be generated or obtained through processing the sensing data. Here, the sensing results may include characteristic information (e.g., position, distance, velocity, angle, etc.) of one or more objects (and / or their surrounding environment). The sensing results generated or obtained in this manner can be used for radio sensing services (e.g., object and / or environment detection or tracking) provided by the 6G-based wireless communication system according to this disclosure, or can be provided / disclosed to a trusted third party.

[0200] Additionally, although Figure 12a and Figure 12b The sensing operation described in the text is a representative example of operation in a wireless communication system based on a 6G network, but it can also be extended and applied to situations using UEs / base stations / signals based on previous generations (such as 4G, 5G, etc.).

[0201] Furthermore, regarding the radio sensing described in this disclosure, in a 6G network-based wireless communication system according to this disclosure, the time-frequency resources for sensing operations and the time-frequency resources for general communication (e.g., uplink / downlink / sidelink-based communication) can be scheduled / configured separately.

[0202] Figure 13 The illustration is an example of a time-frequency resource applicable to the sensing operation of this disclosure. Figure 13 The implementation methods can be combined with various implementation methods of this disclosure.

[0203] Reference Figure 13 For the above sensing operations (e.g., based on) Figure 12a and Figure 12b The time-frequency resources (hereinafter referred to as sensing resources) for sensing operations can be configured / allocated separately from the time-frequency resources (hereinafter referred to as communication resources) used for general communication.

[0204] For example, such as Figure 13 As illustrated, sensing resources can be configured or allocated in the time domain on a per-symbol basis and / or in the frequency domain on a per-resource-block basis. Resources other than those configured or allocated as sensing resources can be used as general communication resources. That is, for the operation of the base station / UE, sensing and communication resources can be configured or allocated based on time-division multiplexing (TDM) and / or frequency-division multiplexing (FDM) schemes. Additionally or alternatively, with Figure 13 Unlike the example shown, sensing resources can be configured or allocated in the time domain based on other units (such as time slots, frames, or absolute time such as milliseconds or microseconds) and / or in the frequency domain based on other units (such as subcarriers, carriers, or absolute frequencies such as megahertz or gigahertz).

[0205] Additionally or alternatively, the configuration / allocation / scheduling of the general communication resources described in this disclosure may need to consider the relationship between such resources and the aforementioned sensing resources. For example, when configuring or allocating general communication resources according to embodiments of this disclosure, these resources may be configured / allocated to perform rate matching or puncturing operations on resource areas corresponding to sensing resources. For example, when scheduling general communication resources according to embodiments of this disclosure, these resources may be scheduled so that they do not overlap with resource areas corresponding to sensing resources. In embodiments of this disclosure, if the resource areas corresponding to general communication resources and sensing resources are configured / allocated / scheduled to overlap, one or both operations may be abandoned, skipped, or postponed based on priority or predefined rules. That is, in embodiments of this disclosure, resources related to general communication (e.g., signal / channel path resources related to data / control based on uplink / downlink / sidelink) are preferably configured / allocated / scheduled to not overlap with the aforementioned sensing resources.

[0206] Additionally, various channel modeling methods can be applied to the radio sensing described in this disclosure. Channel modeling related to sensing can refer to constructing paths for transmitting and / or receiving sensing signals and / or scattered / reflected signals, a process that takes into account the object to be sensed and / or its environment. Since channel modeling can be relevant to the performance and requirements of sensing in a wireless communication system, it can be an important aspect of verifying the feasibility of sensing functionality.

[0207] Sensing-related channels can be categorized into channels between the object (e.g., the target of interest) and the sensing transmitter / receiver, and channels between the object's environment and the sensing transmitter / receiver. Sensing-related channel modeling can be classified based on the sensing mode (e.g., the six modes mentioned above), whether the target of interest is an object or the environment, and / or the sensing scenario. For example, channel modeling for targets in a base station / UE-based monostatic sensing mode, channel modeling for targets in a base station / UE-based bistatic sensing mode, channel modeling for the environment in a base station / UE-based monostatic sensing mode, and channel modeling for the environment in a base station / UE-based bistatic sensing mode can be differentiated and configured respectively. For example, when classifying multiple sensing scenarios, channel modeling can be divided into channel modeling for detection, localization, and tracking scenarios, channel modeling for action recognition, and channel modeling for imaging or environment reconstruction scenarios. Additionally, sensing-related channel modeling can be based on statistical channel modeling techniques and / or deterministic channel modeling techniques. For example, sensing modeling in the 6G network-based wireless communication system of this disclosure can be based on stochastic geometric channel modeling techniques and / or hybrid channel modeling techniques including ray tracing channel modeling. Here, stochastic geometric channel models can be based on various statistical properties of channel conditions. Furthermore, hybrid channel models can be based on both ray tracing and stochastic techniques. In the case of a hybrid approach, channel modeling for objects requiring high accuracy and consistency (e.g., targets of interest) can be performed using ray tracing techniques, while channel modeling for the environment can be performed using stochastic techniques.

[0208] Figure 14 The illustrations are applicable to process examples related to sensing operations in this disclosure. Figure 14 The implementation methods can be combined with various implementation methods of this disclosure.

[0209] For example, in the 6G-based wireless communication system of this disclosure, when the UE participates in sensing operations, the base station may need to identify the UE's capabilities related to the sensing operations. To this end, the UE can be configured to report capability information to the base station, indicating whether it supports sensing operations. Alternatively or additionally, if the UE is predefined by the specification as supporting sensing operations, this process can be omitted. Furthermore, when only the base station participates in the sensing operations, the base station can be configured to report capability information indicating whether it supports sensing operations to the entity that configures or controls its sensing operations (e.g., a higher-level network entity above the base station).

[0210] For example, the base station can interact with the UE via signaling to exchange configuration information related to sensing operations. For instance, the base station can configure or instruct the UE on sensing operation modes (e.g., based on the six modes mentioned above), the entity performing the sensing operation (e.g., a sensing transmitter, a sensing receiver), and the resources for the sensing operation (e.g., [missing information]). Figure 13 This includes information related to the sensing resources shown, the target of the sensing results (e.g., the type of radio sensing service based on a 6G network or a trusted third party), and the channel modeling of the sensing (e.g., the channel between the base station / UE and the object / environment). For example, the base station may be configured / instructed to have such information from a network entity at a higher level / layer than the base station.

[0211] For example, a base station and / or UE can perform sensing operations based on configuration / instruction information. For instance, a base station and / or UE acting as a sensing transmitter and / or sensing receiver can perform the following processes: transmitting sensing signals, receiving scattered / reflected signals, deriving sensing data, obtaining sensing results by processing the sensing data, and providing the sensing results, as described above. Figure 12a and Figure 12b As illustrated. In one example, in the operation of the base station / UE described in this disclosure, sensing results provided through sensing operations may also be utilized.

[0212] D. Network Energy Saving (NES)

[0213] In wireless communication systems, including 3GPP, energy efficiency at base stations is receiving significant attention because it can help build environmentally friendly networks by reducing carbon emissions and lowering the operating expenses (OPEX) of telecom operators. Specifically, the introduction of 5G communications requires higher transmission rates, necessitating base stations with a greater number of antennas and providing services through wider bandwidth and frequency bands. As a result, according to recent research, the energy cost of base stations has reached approximately 20% of total OPEX. Accordingly, 5G systems have adopted various energy-saving technologies known as Network Energy Saving (NES), and standardization efforts for these technologies are expected to continue. Specifically, the recently released Release 18 discusses the following technologies.

[0214] -----------------------------

[0215] 1. If feasible through RAN4 research, specify SSB-less SCell operation for inter-band CA of FR1 and co-located cells, whereby the UE measures SSBs transmitted on the PCell or another SCell for SCell time / frequency synchronization (including downlink AGC) and L1 / L3 measurements, including potential enhancements to the SCell activation process if necessary [RAN4, RAN2].

[0216] 2. Specify enhancements to the cell DTX / DRX mechanism, including alignment of cell DTX / DRX with UEDRX in RRC_CONNECTED mode, and inter-node information exchange regarding cell DTX / DRX [RAN2, RAN1, RAN3].

[0217] Note: Due to the DTX / DRX of the cell, there are no changes for SSB transmission.

[0218] Note: The above enhancements should be avoided in order to prevent them from affecting IDLE / INACTIVE UEs.

[0219] 3. Specify the following techniques in the spatial and power domains.

[0220] • Specify necessary enhancements to CSI and beam management related processes (including measurement and reporting), as well as signaling, to achieve efficient adaptation of spatial elements (e.g., antenna ports, active transceiver chains) [RAN1, RAN2].

[0221] • Specify the necessary enhancements to CSI-related processes (including measurement and reporting), as well as signaling, to achieve effective adaptation of power offset values ​​between PDSCH and CSI-RS [RAN1, RAN2].

[0222] Note: The above objectives apply only to specific channels / signals of the UE.

[0223] Note: When considering the total number and requirements of CSI reports, traditional UE CSI / CSI-RS capabilities apply.

[0224] 4. If necessary, specify mechanisms to prevent legacy UEs from camping on cells using Rel-18 NES technology [RAN2]

[0225] 5. Specify enhanced CHO procedure [RAN2] when the source / target cell is in NES mode.

[0226] 6. Designated inter-node beam activation and enhancements to paging restrictions within limited areas [RAN3]

[0227] 7. If necessary, specify the corresponding RRM / RF core requirements [RAN4] for the above features.

[0228] ----------------------------------

[0229] Based on the application of NES technology, the base station can perform the following operations: control the opening / closing of antenna ports and transmit / receive points (TRPs) for a specific duration on the time axis, adjust the transmit / receive resources for UE common or UE specific signals / channels, change the amount of frequency domain resources, adjust the transmit power, or open / close antenna ports and transmit / receive points (TRPs) in the spatial domain. Figure 15 This diagram illustrates an example of the operation process of a base station supporting NES technology. (Refer to...) Figure 15 The base station identifies the NES solution to be applied. The NES solution can be related to signal transmission / reception control (e.g., enabling / disabling), beam operation, handover procedures, channel measurement, and reporting. Which NES solutions to apply can be adaptively selected based on current conditions (e.g., cell load level, characteristics of connected UEs), or can be predefined. The base station that identifies the NES solution executes signaling for the NES. The specific signaling procedure can vary depending on the identified NES solution. For example, the base station can send public information about the NES solution, or send configuration information required for NES operation to at least one UE. Furthermore, the base station can receive NES-related capability information from at least one UE. Afterward, the base station executes operations for the NES. In this case, the base station can execute operations for the NES based on earlier executed signaling. That is, based on system information, configuration information, and control information transmitted via signaling, the base station can enable / disable specific signal transmission / reception, enable / disable spatial domain elements, or adjust resources used for signal transmission / reception measurement.

[0230] NES technology can be implemented through a process such as that shown in Figure 12. An example of an NES solution that can be implemented through a process such as that shown in Figure 12 is as follows.

[0231] • In-system energy-saving solutions: RAN nodes can request neighboring RAN nodes to switch at least one SSB beam to their inactive cells, or can use a limited set of beams to perform paging on inactive UEs (e.g., stationary UEs).

[0232] • Inter-system energy-saving solution: NG-RAN nodes with capacity-enhanced cells can autonomously switch the cell to an inactive state.

[0233] • SSB-less SCell Solution: When no SSB or SSB-based RRM Measurement Timing Configuration (SMTC) is provided for the SCell, the UE can obtain timing references and AGC sources from another serving cell. In FR1 or FR2, the base station can be configured with co-band CA or inter-band CA for SCells that do not transmit SSBs. In this case, SSB / SIB transmission can be triggered by the UE's wake-up signal (WUS). Accordingly, due to the increased periodicity of common channels / signals such as SSBs, the base station can remain in a dormant state for a longer period.

[0234] • Cell DTX / DRX Solution: To reduce the downlink transmit / uplink receive activation time of the base station, a periodic cell DTX / DRX mode (e.g., active and inactive periods) can be jointly configured for UEs in cells with this characteristic. Here, the cell DTX mode and cell DRX mode can be configured and activated separately, and each MAC entity can configure a maximum of two cell DTX / DRX modes. When cell DTX is configured and activated, at least one of monitoring for SPS opportunities or PDCCH can be suspended during the cell DTX inactive period. When cell DRX is configured and activated, at least one of transmitting on configuration grant (CG) resources or scheduling request (SR) transmission can be suspended during the cell DRX inactive period. Cell DTX / DRX can be activated / deactivated via RRC signaling or L1 group common signaling.

[0235] For cell DTX / DRX, parameters such as activation duration and period can be configured. The activation duration is the period during which the UE waits to receive a PDCCH or SPS opportunity, and waits to send an SR or CG. The period specifies the periodic repetition of the activation and inactivation durations. When both cell DTX and cell DRX are configured, parameters such as activation duration and period are common. If the base station detects an emergency call or public safety-related service (e.g., MPS or MCS), the network can release or deactivate the cell DTX / DRX configuration to avoid affecting the corresponding service. Furthermore, the activation duration of the UE's connection mode DRX needs to at least partially overlap with the activation duration of the cell DTX / DRX. For example, the UE's connection mode DRX period can be a multiple of the cell DTX / DRX period, and vice versa.

[0236] • Conditional Handover (CHO) Solution: During the application of NES technology (e.g., when a cell is activated or deactivated via DTX / DRX), a CHO procedure is used, determined by the UE, to perform the handover. In this case, the UE can use an NES-specific CHO event to perform a CHO to a candidate cell, and as an additional triggering condition, the reception of the DCI can be applied to activate the CHO condition indicated by the NES event.

[0237] • Spatial Domain and Power Domain Adaptation Solution: To support transceiver mutating and / or transmit power adaptation for gNBs, the UE can be configured to report multiple CSI entries in a CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation mode (e.g., a subset of available spatial elements) and / or a power offset between the data channel (e.g., PDSCH) and the CSI-RS. With the application of the spatial domain and power domain adaptation solution, CSI configuration, measurement, and / or reporting operations may be affected.

[0238] SSB-less SCell

[0239] Figure 16 The diagram illustrates an example of a CA operation using an SSB-less SCell applicable to this disclosure. Reference Figure 16The base station sends configuration information for the SCell to the UE. Specifically, the base station sends configuration information for CA (Card Access Control) to the UE to provide services via CA operation. Here, CA operation can be in-band CA or inter-band CA. For example, the configuration information for the SCell may include information for adding the SCell (e.g., sCellToAddModList), and may specifically include the cell index, physical cell identifier, information related to DL-UL configuration, information related to BWP (Browser Protection Device), information related to cell DTX / DRX (Digital Transmission Module), and information related to downlink frequency (e.g., FrequencyInfoDL). Subsequently, the UE determines the configuration for CA operation and can perform communication using the base station's PCell and SCell. At this time, the UE can check whether the SCell is an SSB-free SCell based on the downlink frequency-related information included in the configuration information, and can check related parameters. For example, a UE can determine that an SCell is an SSB-free SCell by checking the presence of a parameter indicating an SSB-free SCell (e.g., SSBlessSCell), and can check the timing reference and AGC source for the SCell based on information related to a reference cell (e.g., referenceCell). In the case of Figure D03, the reference cell can be a PCell. Therefore, the UE can use the PCell as a timing reference and AGC source for communication within the SCell.

[0240] In 3GPP New Radio (NR) Release 19, a work item titled "Enhancements for Network Power Efficiency in NR" has been additionally approved. Specifically, enhancements to the following methods are being considered in 3GPP NR Release 19.

[0241] -------------------------------

[0242] The objectives of a research project (SI), a core component work project (WI), or a test component work project

[0243] The goals of WI are as follows: 1. For both in-band CA and inter-band CA, specify the procedures and signaling methods for supporting on-demand SSB SCell operation for UEs configured with carrier aggregation (CA) in connection mode. [RAN1 / 2 / 3 / 4] • Specify the triggering method (select from UE uplink wake-up signal using existing signal / channel, cell enable / disable indication via backhaul, and SCell activation / deactivation signaling). • Note 1: On-demand SSB transmission can be used by the UE for minimum SCell time-frequency synchronization, L1 / L3 measurement and SCell activation, and is supported in FR1 and FR2 in non-shared spectrum.

[0244] 2. Research the procedures and signaling methods for on-demand SIB1 supporting idle / inactive mode UEs, as follows: [RAN1 / 2 / 3]

[0245] • Triggering method using the uplink wake-up signal of an existing signal / channel

[0246] • Provide wake-up signal configuration to the UE

[0247] Note: This objective does not discuss modifications to the SSB.

[0248] • If necessary, at least gNB inter-information exchange should be performed for the configuration of the wake-up signal.

[0249] Standardized work checkpoints on RAN#105

[0250] 3. Specify the adaptation for common signal / channel transmission. [RAN1 / 2 / 3 / 4]

[0251] • SSB's adaptation in the time domain, such as periodic adaptation

[0252] • PRACH time-domain adaptation

[0253] • Spatial adaptation of PRACH, such as studying non-uniform PRACH resources per SSB, and designating them if they are deemed beneficial.

[0254] - This study was conducted only in the second quarter of 2024.

[0255] • Adjustment of paging timing, including time-domain restrictions on paging timing.

[0256] Note: Paging delay must not be increased.

[0257] Note: Unless a significant benefit is observed, there must be no negative impact on the traditional UE.

[0258] 4. Specify the corresponding key requirements for the above characteristics. [RAN4]

[0259] ---------------------------------

[0260] SSB on demand

[0261] Based on the aforementioned objective 1, a method can be discussed: the base station transmits SSBs on a specific cell through an on-demand SSB procedure, and does not transmit SSBs in that cell when there is no on-demand SSB procedure, thereby reducing energy consumption. In traditional NR systems, because SSBs must be transmitted periodically and continuously for purposes such as time / frequency synchronization or RRM measurements, it is difficult to reduce energy consumption even when the base station has no data to receive or transmit. Therefore, the base station can reduce energy consumption by not performing SSB transmission and only performing SSB transmission when accompanied by an on-demand SSB procedure. The on-demand SSB procedure can be triggered by one of the following methods: 1) The UE requests the base station to send an SSB by sending uplink signals / channels (such as PRACH, PUCCH, PUSCH, SRS, etc. in an NR system). 2) Base station (or TRP) #1 requests base station (or TRP) #2 to send SSB via base station interface (e.g., Xn interface in NR system) or backhaul signaling. 3) Send a signal to notify whether an SSB is being sent for the corresponding SCell via SCell activation / deactivation signaling. Considering coexistence with traditional NR UEs, version 19 restricts on-demand SSB operation to connected mode UEs and SCells. However, in future versions or next-generation communication systems, on-demand SSB operation (for SSB transmission on PCells) can be defined to consider inactive or idle mode UEs or initial access UEs. Furthermore, carrier aggregation (CA) including SCells can be applied to both in-band CA and inter-band CA. SSBs on SCells transmitted via the on-demand SSB procedure can be used for at least time / frequency synchronization, L1 / L3 measurements, and SCell activation functions.

[0262] SIB1 sent on demand

[0263] Based on objective 2 in Table E-1 above, a method can be discussed: the base station transmits SIB1 for a specific cell via an on-demand SIB1 procedure, and does not transmit SIB1 for that cell when there is no on-demand SIB1 procedure, thereby reducing energy consumption. In traditional NR systems, since SIB1, which contains system information and random access information for UEs accessing the cell for initial access or idle mode, must be provided periodically and continuously, it is difficult to reduce energy consumption even if the base station has no data to receive or transmit. Therefore, the base station can reduce energy consumption by not performing SIB1 transmission, but only performing SIB1 transmission when accompanied by an on-demand SIB1 procedure. The on-demand SIB1 procedure can be triggered by the UE sending uplink signals / channels (e.g., PRACH in NR systems) to send SIB1. Specific scenarios can be considered, but are not limited to, the following: 1) Scenario 1: such as Figure 17aAs shown, a UE that receives an SSB (and / or other downlink signal / channel) from cell #1 and identifies that no SIB1 has been transmitted on cell #1 can send a signal requesting SIB1 (referred to as a Wake-up Signal (WUS) in this disclosure for convenience) based on information provided in the SSB (and / or other downlink signal / channel) and / or predefined information, thereby triggering the transmission of SIB1. The base station receiving the WUS can respond by transmitting a specific downlink signal / channel on cell #1, and / or transmitting SIB1 on cell #1 without transmitting a downlink signal / channel.

[0264] 2) Scenario 2: such as Figure 17b As shown, a UE that receives an SSB (and / or other downlink signal / channel, such as SIB1) from cell #1 and identifies that SIB1 has not been transmitted on cell #2 may attempt to camp on cell #2. Based on the information provided in the received SSB (and / or other downlink signal / channel, such as SIB1) and / or predefined information, the UE transmits a request for SIB1 signal (i.e., WUS) on cell #1 to trigger SIB1 transmission on cell #2. The base station receiving the WUS may respond by transmitting a specific downlink signal / channel (on cell #1 or cell #2), and / or transmitting SIB1 of cell #2 on cell #1 or cell #2 without transmitting a downlink signal / channel.

[0265] 3) Scenario 3: such as Figure 17c As shown, a UE that receives an SSB (and / or other downlink signal / channel, such as SIB1) from cell #1 and identifies that SIB1 has not been transmitted on cell #2 may attempt to camp on cell #2. Based on the information provided in the received SSB (and / or other downlink signal / channel, such as SIB1) and / or predefined information, the UE transmits a request for SIB1 signal (i.e., WUS) on cell #2 to trigger the transmission of SIB1 on cell #2. The base station that receives the WUS may respond by transmitting a specific downlink signal / channel (on cell #1 or cell #2), and / or transmitting the SIB1 of cell #2 on cell #1 or cell #2 without transmitting a downlink signal / channel.

[0266] Specific embodiments of this disclosure

[0267] This disclosure relates to a technique for operating synchronization signal / physical broadcast channel block (SSB) and system information on an on-demand basis in a wireless communication system. Specifically, this disclosure proposes a technique for providing SSB and / or system information on a request basis in a cell or frequency band where the transmission of SSBs (e.g., synchronization signals, MIBs) and / or system information (e.g., MIBs, SIBs) is temporarily suspended for NES operation. Specifically, this disclosure proposes on-demand signaling for requesting SSBs and the conditions for executing said on-demand signaling. In this disclosure, " / " means "and," "or," or "and / or" depending on the context.

[0268] For NES purposes, the base station can operate various techniques, such as controlling the UE to turn on / off for a specific duration on the time axis, adjusting transmit and receive resources for UE-common or UE-specific signals / channels, changing the amount of frequency domain resources, adjusting transmit power, or turning antenna ports (APs) and transmit / receive points (TRPs) on / off in the spatial domain. In this disclosure, the techniques listed above are referred to as "NES techniques" or "NES_tech," and the state of applying at least one NES_tech is referred to as "NES mode" or "NES state." The base station can indicate to the UE the NES_tech applied for each NES_tech or each group of NES_techs [Scheme 1], or it can pre-configure the NES_tech or NES_tech group corresponding to each code point of a specific indicator [Scheme 2]. Here, the specific indicator can be indicated by DCI or MAC CE, or it can be configured by higher-layer signaling.

[0269] In Scheme 1, when at least one NES_tech is applied to the UE, the corresponding state can be defined as an NES mode or an NES state. Furthermore, depending on the specific NES_tech applied, this state can be considered as a different NES mode or a different NES state. An NES mode or NES state can be used as a concept indicating whether at least one NES technology is applied, or, in addition, as a concept indicating the applied NES technology. When an NES mode or NES state further indicates the applied NES technology, different NES modes or different NES states can include different combinations of NES_tech. In Scheme 2, for example, when using a 1-bit indicator, "0" can indicate that the corresponding NES_tech is not applied, and "1" can indicate that at least one NES_tech is applied. In this case, when the indicator indicates "1", the corresponding state can be defined as an NES mode or an NES state. In another example, when using a 2-bit indicator, "00" can indicate the absence of a corresponding NES_tech, "01" can indicate the application of at least one NES_tech_A, "10" can indicate the application of at least one NES_tech_B, and "11" can indicate the application of at least one NES_tech_C. In this case, when the indicator indicates a code point other than "00", the corresponding state can be defined as NES mode or NES state. Furthermore, the UE can determine NES state #1 when it detects "01", NES state #2 when it detects "10", and NES state #3 when it detects "11". Therefore, it is possible to distinguish whether the state is an NES state and / or which type of NES state for each code point.

[0270] For NES purposes, base stations can enable / disable specific spatial elements (e.g., antenna ports, active transmit / receive links, panels, or TRPs) or adjust the power values ​​of downlink signals / channels. To dynamically apply multiple NES technologies in the spatial and power domains, base stations can configure a CSI report (e.g., CSI-ReportConfig) to associate CSI-RS resources or resource sets with different antenna ports, or they can associate multiple power offsets (e.g., the powerControlOffset parameter representing the power offset between PDSCH and CSI-RS, the powerControlOffsetSS parameter representing the power offset between SSS and CSI-RS, etc.).

[0271] Specifically, at least one of the following CSI frameworks can be introduced.

[0272] - Framework #1: In CSI-ReportConfig, multiple CSI-RS resource sets are associated with a Channel Measurement Resource (CMR) or an Interference Measurement Resource (IMR). Here, the CMR can be configured via the resourcesForChannelMeasurement parameter, and the IMR can be configured via the csi-IM-ResourcesForInterference parameter or the nzp-CSI-RS-ResourcesForInterference parameter. For example, for CMR, associating CSI-RS resource set #1 and CSI-RS resource set #2, the CSI-RS resource belonging to CSI-RS resource set #1 can be configured with 16 antenna ports (APs), and the CSI-RS resource belonging to CSI-RS resource set #2 can be configured with 8 APs.

[0273] - Framework #2: When configuring a CSI-RS resource set associated with a CMR or an IMR in CSI-ReportConfig, at least one CSI-RS resource with different attributes (such as the number of APs and / or power offset) can be configured within that CSI-RS resource set. For example, for CSI-RS resource set #1 configured as CMR, CSI-RS resource 1 belonging to CSI-RS resource set #1 can be configured with 16 APs, and CSI-RS resource #2 belonging to the same resource set can be configured with 8 APs. As another example, for CSI-RS resource set #1 configured as CMR, CSI-RS resource 1 belonging to CSI-RS resource set #1 can be configured with power offset #1, and CSI-RS resource #2 belonging to the same resource set can be configured with power offset #2.

[0274] - Framework #3: When configuring a CSI-RS resource set associated with a CMR or IMR in CSI-ReportConfig, multiple AP numbers and / or multiple power offset values ​​can be configured for some or all of the CSI-RS resources in that resource set. For example, for CSI-RS resource set #1 configured as a CMR, CSI-RS resource 1 belonging to CSI-RS resource set #1 can be configured with up to 16 APs, and can be configured to use at least one of these APs for CSI reporting. Alternatively, CSI-RS resource #2 belonging to the same CSI-RS resource set #1 can be configured with multiple power offset values, and can be configured to use all or part of the power offsets for CSI reporting.

[0275] For the CSI framework described above, a CSI reporting methodology can be defined using at least one of the following options.

[0276] - Option #1: Considering multiple AP quantity values ​​and / or multiple power offset values ​​configured in a single CSI report, all CSI values ​​can be included in a single CSI report. Alternatively, considering multiple AP quantity values ​​and / or multiple power offset values ​​determined by base station configuration / instructions, CSI values ​​can be included in a single CSI report. In this case, the AP quantity values ​​and / or power offset values ​​configured / instructed by the base station can be a subset of the AP quantity values ​​and / or power offset values ​​configured in the CSI report.

[0277] - Option #2: Even if multiple AP quantity values ​​and / or multiple power offset values ​​are configured in a single CSI report, the CSI that considers a single AP quantity value and / or a single power offset value determined by the base station configuration / instruction can be included in a single CSI report.

[0278] - Option #3: Even if multiple AP quantity values ​​and / or multiple power offset values ​​are configured in a single CSI report, the CSI of some AP quantity values ​​and / or some power offset values ​​can be included in a single CSI report after the UE makes a judgment / decision / selection based on the base station's pre-configured or predefined criteria.

[0279] In the configuration of CSI reports (e.g., CSI-ReportConfig), more than 1 L sub-configurations can be configured, and each sub-configuration can correspond to either spatial domain adaptive mode or power domain adaptive mode.

[0280] Here, the spatial domain adaptive mode can correspond to a specific number of APs or an AP on / off mode, or it can correspond to a specific CSI-RS power value (for example, since disabling some antenna elements corresponding to an AP will affect the CSI-RS power value, it can be the CSI-RS power value determined by the powerControlOffsetSS parameter, which represents the power offset between SSS and CSI-RS). For example, in the case of application framework #2, A1 APs or P1 power values ​​are configured for CSI-RS index #n1 belonging to a certain resource set, and A2 APs or P2 power values ​​are configured for CSI-RS index #n2 belonging to the same resource set. In this case, sub-configuration index #s1 is associated with CSI-RS index #n1, and sub-configuration index #s2 is associated with CSI-RS index #n2, so that different spatial domain adaptive modes can be configured for each sub-configuration. In the case of application framework #3, when CSI-RS index #n1 belonging to a certain resource set is configured with A1 APs (or P1 / P2 power values), sub-configuration index #s1 is associated with A1 APs (or P1 power values ​​or delta values ​​from P1 power values), and sub-configuration index #s2 is associated with A2 APs (or P2 power values ​​or delta values ​​from P1 power values) that are less than A1 of those configured with CSI-RS index #n1, so that different spatial domain adaptive modes can be configured for each sub-configuration.

[0281] Furthermore, a power domain adaptive mode can refer to a change in the power offset value (e.g., a power offset value determined by the powerControlOffset parameter, which represents the power offset between PDSCH and CSI-RS, or the powerControlOffsetSS parameter, which represents the power offset between SSS and CSI-RS). For example, in the case of application framework #2, a power value P1 is configured for CSI-RS index #n1 belonging to a certain resource set, and a power value P2 is configured for CSI-RS index #n2 belonging to the same resource set. In this case, sub-configuration index #s1 is associated with CSI-RS index #n1, and sub-configuration index #s2 is associated with CSI-RS index #n2, thereby allowing different power domain adaptive modes to be configured for each sub-configuration.

[0282] Furthermore, in the case of application framework #3, power values ​​P1 and P2 can be configured for CSI-RS index #n1 belonging to a certain resource set. In this case, sub-configuration index #s1 is associated with the P1 power value, and sub-configuration index #s2 is associated with the P2 power value or a delta value from the P1 power value, thereby enabling different power domain adaptive modes to be configured for each sub-configuration.

[0283] By using one of the above options #1 / 2 / 3, the UE can send a CSI report to the base station, which includes CSIs corresponding to N of the L sub-configurations (where N is between 1 and L).

[0284] According to TS 38.214, in a CSI reporting configuration, at least one sub-configuration can be configured, and in each sub-configuration, one or a combination of the following configurations can be configured.

[0285] - A list of IDs for one or more CSI Reference Signal (CSI-RS) resources

[0286] - Antenna port subset indication configured as a bitmap

[0287] - Additional power offset delta between the PDSCH and CSI-RS configured in the CSI-RS resource configuration and the EPRE offset.

[0288] In this disclosure, for ease of description, a CSI reporting configuration including a sub-configuration in which a list of IDs of at least one CSI-RS resource is configured is referred to as Type 2 Spatial Domain (SD) Adaptive; a CSI reporting configuration including a sub-configuration in which an antenna port subset indication configured as a bitmap is configured is referred to as Type 1 Spatial Domain Adaptive; and a CSI reporting configuration including a sub-configuration in which an additional power offset increment value is configured is referred to as Power Domain (PD) Adaptive. For a sub-configuration belonging to a CSI reporting configuration, a list of IDs of at least one CSI-RS resource and / or a power offset increment value can be configured, and this is referred to as Type 2 Spatial Domain + Power Domain Adaptive. Additionally, for a sub-configuration belonging to a CSI reporting configuration, an antenna port subset indication configured as a bitmap and / or a power offset increment value can be configured, and this is referred to as Type 1 Spatial Domain + Power Domain Adaptive. In the case of Type 1 Spatial Domain or Power Domain or Type 1 Spatial Domain + Power Domain Adaptive, each CSI-RS resource can be associated with each of all sub-configurations configured in a CSI reporting configuration. In the Type 2 spatial domain adaptive configuration, each CSI-RS resource can be associated with only a single sub-configuration among multiple sub-configurations in a single CSI reporting configuration. In the Type 2 spatial domain + power domain adaptive configuration, the list #1 of CSI-RS resources configured in one sub-configuration and the list #2 of CSI-RS resources configured in another sub-configuration within the same CSI reporting configuration can be identical to each other or can be disjoint.

[0289] Simultaneously, when L sub-configurations are configured in a CSI reporting configuration, the UE can report the CSI corresponding to each of the L sub-configurations to the base station via a single PUSCH / PUCCH. Of these L sub-configurations, only N (L or fewer and 1 or more) sub-configurations can be activated or triggered via MAC-CE or DCI, and in this case, the UE can report the CSI corresponding to each of the N sub-configurations to the base station via a single PUSCH / PUCCH. Specifically, for a CSI reporting configuration that configures semi-persistent (SP) CSI reporting on the PUCCH, N of the L sub-configurations configured via MAC-CE can be activated. Additionally, for a CSI reporting configuration that configures SP CSI reporting or aperiodic (A)-CSI reporting on the PUSCH, N of the L sub-configurations configured via DCI can be triggered.

[0290] From the perspective of a base station operating multiple frequency bands, periodically transmitting SSB and / or system information may lead to unnecessary energy consumption when the number of UEs being served is small or the service load is relatively low. In this disclosure, frequency band can be replaced by waveband, carrier, serving cell, or bandwidth portion (BWP).

[0291] For example, as in Figure 18 It can operate on three frequency bands. Figure 18 The illustration shows an example of a frequency band operated by a base station according to an embodiment of the present disclosure. Reference Figure 18 When a base station operates in three frequency bands, it can periodically transmit SSBs (e.g., legacy SSBs) in some bands (e.g., F1), transmit simplified or improved simplified SSBs (S-SSBs) in the remaining bands (e.g., F2), or not transmit SSBs and S-SSBs in another band (e.g., F3). That is, F2 and F3 can be understood as SSB-free bands. This allows the base station to promote energy saving. When a UE operates in F2 or F3, the UE can request the base station to transmit SSBs in the corresponding band. SSBs transmitted according to the UE's request can be called on-demand SSBs, and the corresponding SSBs can be legacy SSBs or simplified or improved S-SSBs. Here, cells such as F2 or F3 that are allowed not to transmit SSBs can be called SSB-free cells. From the UE's perspective, an SSB-free cell can be any of PCell / PSCell / SCell.

[0292] [Example #1] Signaling method for requesting on-demand SSB

[0293] (Example #1-1) Method for sending a signal to request an on-demand SSB

[0294] Figure 19 An example of a process for requesting an on-demand SSB in a wireless communication system according to embodiments of the present disclosure is shown. Figure 19 This example demonstrates a method executed by the UE.

[0295] refer to Figure 19 In step S1901, the UE receives configuration information related to on-demand SSB. This configuration information may include various parameters related to on-demand SSB. For example, the configuration information may include at least one of the following: information related to the cell supporting on-demand SSB, information related to the on-demand SSB structure, or information related to requesting on-demand SSB. Here, the configuration information can be received from the UE's PCell. That is, the UE can perform synchronization signal detection, random access procedures, connection establishment procedures, etc., for the PCell, and can receive configuration information related to on-demand SSB for the PCell or another cell.

[0296] In step S1903, the UE identifies the resources used to request an on-demand SSB. The UE may identify the resources used to request an on-demand SSB based on configuration information related to the on-demand SSB. That is, according to one embodiment, the configuration information may include information related to the resources (e.g., channels, etc.) used to transmit the signal requesting the on-demand SSB, as information related to the requesting the on-demand SSB. Furthermore, the configuration information may include information related to at least one of the structure of the signaling scheme or signal used to request the on-demand SSB. In other words, the resources used to transmit the signal requesting the on-demand SSB are configured by the configuration information and can be indicated by at least one of time-frequency location, resource or channel index, or offset.

[0297] In step S1905, the UE sends a request signal for on-demand SSB. In other words, the UE can request the transmission of on-demand SSB by sending a request signal through the identified resource. At this time, according to one embodiment, the UE can generate and send the request signal based on at least one parameter configured by configuration information.

[0298] For reference Figure 19 The signal and / or channel used to request an on-demand SSB can be configured. Various predefined uplink signals and / or channels can be used, or dedicated uplink signals and / or channels can be used. According to various embodiments, the base station can configure the UE to use which of the following uplink signals and / or channels to request an on-demand SSB, and the UE can request an on-demand SSB via a specific uplink signal and / or channel based on the configuration from the corresponding base station. For ease of description, in this disclosure, the uplink signal and / or channel sent by the UE to request an on-demand SSB is referred to as "UL_SSB".

[0299] (Example #1-1-1) PRACH: For on-demand SSB requests, at least one RACH timing (RO) can be configured individually. Alternatively, for on-demand SSB requests, some PRRACH leading indices within a specific RO can be configured for the on-demand SSB request.

[0300] (Example #1-1-2) Scheduling Request (SR) PUCCH / PRACH: When a UE transmits an SR corresponding to a cell without an SSB (e.g., an SR transmitted on the PUCCH or PRACH), it can be considered to always request an on-demand SSB. That is, the transmission of an SR corresponding to a cell without an SSB can be interpreted as a request for an on-demand SSB. Alternatively, the SR resources used to request an on-demand SSB can be configured separately from the SR resources used not to request an on-demand SSB. Here, SR resources may include separate time / frequency resources and / or sequence resources.

[0301] (Example #1-1-3) SRS: SRS resources for requesting on-demand SSBs can be configured separately. Here, SRS resources may include separate time / frequency resources and / or sequence resources.

[0302] (Example #1-1-4) PUCCH: On-demand SSB request information can be transmitted periodically or non-periodically via periodic or semi-persistent PUCCH. Here, the SSB request information includes information indicating to the UE that it requests the transmission of on-demand SSB.

[0303] (Example #1-1-5) PUSCH: On-demand SSB request information can be sent periodically or non-periodically via a PUSCH or a semi-persistent PUSCH scheduled via UL license (e.g., configuration license (CG) PUSCH or semi-persistent CSI reports on PUSCH).

[0304] (Example #1-1-6) Resources for UL_SSB can be configured on SSB-free cells. Alternatively, resources for UL_SSB can be configured on cells other than the corresponding SSB-free cells (e.g., PCell / PSCell / SCell / non-serving cells, etc.).

[0305] The above-described request process for on-demand SSBs based on uplink signals can be performed in a limited manner for a specific cell. According to an embodiment, the UE can send a request signal to request an on-demand SSB for the PCell.

[0306] (Examples #1-2) A method for requesting on-demand SSB by selectively using one resource from multiple resources.

[0307] One or more UL_SSB resources can be configured for a UE. The UE can then select a UL_SSB resource based on the following criteria: UL_SSB resources can be distinguished by time / frequency / sequence resources in the same uplink signal and / or channel, by the type of uplink signal and / or channel, or by the cell corresponding to the UL_SSB resource.

[0308] Figure 20 An example is shown of a process in a wireless communication system, according to an embodiment of the present disclosure, for transmitting a signal for requesting an on-demand SSB by using at least one of a plurality of resources. Figure 20 This example demonstrates a method executed by the UE.

[0309] refer to Figure 20 In step S2001, the UE selects a resource for requesting an on-demand SSB. That is, multiple resources are configured or allocated for the UE to request an on-demand SSB, and the UE selects one of these resources. At this time, the UE selects the resource based on the attributes of the on-demand SSB to be requested. Here, the attributes of the on-demand SSB can be related to at least one of the following: the SSB itself, the resource carrying the SSB, the SSB transmission scheme, the cell providing the SSB, or the SSB structure.

[0310] In step S2003, the UE sends a request signal based on the selected resource. In other words, the UE sends a signal to request the on-demand SSB by using a resource corresponding to the attribute of the requested on-demand SSB. Here, the resource may include at least one of time-domain resources, frequency-domain resources, or sequence resources.

[0311] For reference Figure 20 In the described embodiment, the request signal for requesting an on-demand SSB can be sent through one of a plurality of resources. Specific embodiments using multiple resources are as follows.

[0312] (Example #1-2-1) Configure different UL_SSB resources for each SSB index or group of indexes: Here, the SSB index may be an index corresponding to an SSB to be transmitted on an SSB-free cell, or it may be an index corresponding to an SSB to be transmitted on a reference cell. In this disclosure, a reference cell means a cell configured to be associated with at least one of the following: timing synchronization and / or automatic gain control (AGC) settings, UL power control, path loss estimation, beam management-related measurements (e.g., L1-RSRP, L1-SINR, etc.) and / or RRM measurements (e.g., RSRP, RSRQ, RSSI, etc.) of an SSB-free cell, and may include cells other than SSB-free cells (e.g., PCell / PSCell / SCell / non-serving cells, etc.). As an example, different UL_SSB resources can be configured for each SSB index or SSB index group corresponding to an SSB to be transmitted on an SSB-free cell or an SSB to be transmitted on a reference cell. UL_SSB resource #1 corresponding to SSB index group #0 or SSB index #0 can be pre-configured, and UL_SSB resource #2 corresponding to SSB index group #1 or SSB index #1 can be pre-configured. If the UE requests SSB index #1 or SSB index group #1, the UE can transmit a signal using UL_SSB resource #2.

[0313] According to an embodiment, in preparation for situations where it is unclear whether the UE is requesting a specific SSB index or group of indexes, a separate UL_SSB resource can be configured for requesting all SSB indexes. In this case, the UE can request transmissions for all SSB indexes by performing uplink transmissions through the corresponding UL_SSB resource.

[0314] (Example #1-2-2) Configure different UL_SSB resources based on the transmission duration, periodicity, and / or SSB mode of the SSB requested by the UE: Transmission duration can refer to the duration from when the on-demand SSB starts on an SSB-free cell until when the on-demand SSB ends. As an example, when on-demand SSBs are transmitted P times periodically at X milliseconds starting from slot #n on an SSB-free cell, and then the on-demand SSBs are turned off starting from slot #n+k so that no more SSBs are transmitted, the k slots, the absolute time corresponding to the k slots, or the value P can be defined as the duration. SSB periodicity can refer to the transmission time interval or minimum transmission time interval between SSBs or SSB candidates with the same index. In addition, when multiple SSB modes are pre-configured / defined (e.g., legacy SSBs and simplified SSBs), different UL_SSB resources can be configured for each SSB mode. As an example, when UL_SSB resource #1 corresponding to SSB transmission duration #1 and UL_SSB resource #2 corresponding to SSB transmission duration #2 are configured respectively, the UE can select UL_SSB resource #2 according to the required SSB transmission duration and can perform uplink transmission by using the selected UL_SSB resource #2. Therefore, the UE can assume that on-demand SSBs can be transmitted during SSB transmission duration #2.

[0315] (Example #1-2-3) When one or more reference cells exist corresponding to a cell without an SSB, different or the same UL_SSB resources are configured for each reference cell: When multiple reference cells are configured corresponding to a specific cell without an SSB, different UL_SSB resources can be configured for each reference cell. As an example, when a PCell and another SCell are configured as reference cells for a cell without an SSB, UL_SSB resource #1 corresponding to the PCell and UL_SSB resource #2 corresponding to the other SCell can be configured, and when the UE intends to request to be linked to the SSB of the PCell on a cell without an SSB, the UE can perform uplink transmission through UL_SSB resource #1.

[0316] (Example #1-2-4) When configuring UL_SSB resources corresponding to one or more SSB-free cells for a public cell, different UL_SSB resources are configured for each SSB-free cell or each group of SSB-free cells: As an example, when a UE uses three serving cells via carrier aggregation (CA), SCell#0 and SCell#1 operate as SSB-free cells, and the UL_SSB resources used to request an SSB on SCell#0 and the UL_SSB resources used to request an SSB on SCell#1 can both be configured on PCell.

[0317] In this case, Option-1) allows the UL_SSB resource used to request an SSB on SCell #0 and the UL_SSB resource used to request an SSB on SCell #1 to be configured identically, or Option-2) allows the UL_SSB resource used to request an SSB on SCell #0 and the UL_SSB resource used to request an SSB on SCell #1 to be configured differently. In Option-1, uplink transmission is performed using a common UL_SSB resource, allowing the UE to request on-demand SSB transmissions for both SCells. In Option-2, uplink transmission is performed using one of the different UL_SSB resources, allowing the UE to request on-demand SSB transmissions for a specific SCell.

[0318] (Example #1-2-5) Different UL_SSB resources are configured based on whether the SSB requested by the UE is a Non-Cell Defined-SSB (NCD-SSB) or a Cell Defined-SSB (CD-SSB): NCD-SSB refers to an SSB that does not provide CORESET index 0 and type 0-PDCCH CSS set information through PBCH information, while CD-SSB refers to an SSB that provides CORESET index 0 and type 0-PDCCH CSS set information through PBCH information. According to the embodiment, UL_SSB resource #1 corresponding to NCD-SSB and UL_SSB resource #2 corresponding to CD-SSB can be configured respectively. If the UE performs uplink transmission through UL_SSB resource #1, the UE can expect to be able to send NCD-SSB in the corresponding SSB-free cell. On the other hand, if the UE performs uplink transmission through UL_SSB resource #2, the UE may expect to be able to send CD-SSB in the corresponding SSB-free cell.

[0319] [Example #2] Conditions for UE to trigger a request for on-demand SSB

[0320] Figure 21 The illustration shows an example of a process for requesting on-demand SSBs based on conditions in a wireless communication system, according to an embodiment of the present disclosure. Figure 21 This example demonstrates a method executed by the UE.

[0321] refer to Figure 21 In step S2101, the UE determines that the conditions for requesting an on-demand SSB are met. According to various embodiments, the conditions for requesting an on-demand SSB can be predefined or configured by the base station.

[0322] In step S2103, the UE sends a request signal for on-demand SSB. In other words, based on the determination that certain conditions are met, the UE can request on-demand SSB transmission by sending a request signal. At this time, according to an embodiment, the UE can send the request signal based on resources determined according to conditions identified as met. The conditions can be defined based on at least one of the timing of the signal transmitted in an SSB-free cell or the channel quality.

[0323] For reference Figure 21 The described embodiments allow the UE to request an on-demand SSB using the UL_SSB resource when certain conditions are met. According to various embodiments, the UE can request the transmission of an on-demand SSB when one or more of the following conditions are met. Various embodiments of the conditions for requesting an on-demand SSB are described below.

[0324] (Example #2-1) When uplink data to be sent by the UE or downlink data to be received by the UE occurs through a cell without an SSB: Specifically, when the UE sends an SR due to uplink data occurrence, the UE can perform an on-demand SSB request simultaneously with the SR resource, as described in [Example #1] above. Alternatively, after the SR transmission, the UE can request an on-demand SSB using a separate UL_SSB resource.

[0325] (Example #2-2) When it is determined that the receive timing or DL ​​RX synchronization is misaligned by a certain threshold (e.g., X nanoseconds or Y time samples) during downlink reception via a cell without SSB, or when the probability of successful transmission and reception for initial transmission or retransmission is less than or equal to a certain threshold: Here, the value of the threshold used for determination can be predefined in the specification or can be configured from the base station.

[0326] (Examples #2-3) When the reception quality of the signal received through an SSB-free cell and / or a reference cell meets specific conditions: the signal received through an SSB-free cell and / or a reference cell may include SSB indexes and / or CSI-RS resources transmitted on the reference cell, or may include CSI-RS transmitted on the SSB-free cell. Which signal is used to measure reception quality (hereinafter referred to as the "measurement signal") can be predefined or configured by the base station.

[0327] According to an embodiment, the measurement signal may include a reference signal configured or indicated as QCL, TCI, or spatial relation information of any downlink / uplink signal and / or channel received or transmitted on an SSB-free cell. Here, the received quality of the signal can be understood as the result value of L1 and / or L3 measurements corresponding to the signal (e.g., beam management-related measurements such as L1-RSRP or L1-SINR, and / or RRM measurements such as RSRP, RSRQ, or RSSI). A specific condition can be determined to be met when the received quality degrades to less than or equal to / less than a specific threshold (hereinafter referred to as "Event 1"), when the amount of change in received quality becomes greater than or equal to / greater than the specific threshold (hereinafter referred to as "Event 2"), or when such events (e.g., Event 1 and / or Event 2) occur exceeding the specific threshold. Here, the threshold may be predefined or may be configured by the base station.

[0328] Furthermore, in counting the occurrences of a specific event, the UE can count how many times the corresponding event occurred within a given sliding time window or time window. Here, the value of the sliding time window or time window can be predefined or configured by the base station.

[0329] In this case, when the event recurs within a specific duration from the time the event occurred, the UE can increment the count. Conversely, when the event recurs after the specific duration has elapsed, the UE can reset the count. Here, the duration value can be predefined or configured by the base station.

[0330] The base station's behavior can vary depending on which triggering condition the UE is required to request on-demand SSB information. With this in mind, the UL_SSB resource can be configured differently depending on the triggering condition, as described in [Example #1] above. As an example, when performing downlink reception through an SSB-free cell, UL_SSB resource #1 can be configured corresponding to a condition (hereinafter referred to as "Condition #1") in which the reception timing or downlink reception synchronization is determined to be misaligned greater than or equal to a specific threshold (e.g., X nanoseconds or Y time samples), and UL_SSB resource #2 can be configured corresponding to a condition (hereinafter referred to as "Condition #2") in which the reception quality of a specific SSB index received on the reference cell becomes less than or equal to a specific threshold. When on-demand SSB is requested due to Condition #2, the UE can attempt uplink transmission through UL_SSB resource #2.

[0331] Figure 22 The illustration shows an example of a process for requesting SSB transmission for an SSB-less cell according to an embodiment of the present disclosure. Figure 22 The example illustrates the signal exchange between UE 2210 and base station 2220.

[0332] refer to Figure 22 In step S2201, base station 2220 configures a cell without an SSB and can configure an on-demand SSB signal for requesting an SSB on the corresponding cell, as described in [Example #1] above. In step S2203, UE 2210 determines whether the triggering condition proposed in [Example #2] above is met. When the condition is met, in step S2205, UE 2210 can select and send one of the signaling messages for requesting the configured on-demand SSB. After receiving the on-demand SSB signaling message, in step S2207, base station 2220 can send the corresponding SSB.

[0333] When a base station operates multiple frequency bands, for NES purposes, the base station may periodically transmit SSB and / or system information in a specific frequency band, and may not periodically transmit corresponding signals and / or channels in the remaining frequency bands. To support such operations by the base station and to support stable communication of the UE in the corresponding frequency band, this disclosure proposes an on-demand SSB operation procedure, specifically signaling and triggering conditions for requesting on-demand SSBs.

[0334] In the various embodiments described above, in an SSB-less cell, on-demand SSBs can be transmitted based on a UE request or a base station determination. In this case, even in cells supporting on-demand SSBs, an SSB that is always enabled and different from the on-demand SSB (hereinafter referred to as the "default SSB") can be transmitted. In this situation, the base station can transmit the default SSB in the corresponding cell and can additionally transmit on-demand SSBs based on a UE request or a base station determination. That is, an SSB-less cell refers to the corresponding cell from the perspective of on-demand SSBs, and even when the default SSB is transmitted, if there exists a state where on-demand SSBs are not transmitted at a specific point in time, the corresponding cell can also be called an SSB-less cell.

[0335] Therefore, the above embodiments applied to SSB-free cells can also be similarly applied to cells that transmit a default SSB and support on-demand SSB. In this case, in the various embodiments described above, the reference cell and the SSB-free cell can be understood as a cell that supports on-demand SSB, and the signal of the reference cell can be replaced by the default SSB signal of the cell that supports on-demand SSB.

[0336] The proposed methods described above can be implemented independently, but can also be implemented in combination (or merging) of some of the proposed methods. Information regarding whether to apply the proposed methods (or information regarding the rules for applying the proposed methods) can be defined by rules, enabling the base station to notify the UE via predefined signals (e.g., physical layer signals or higher layer signals).

[0337] This disclosure may be implemented in other specific forms without departing from the technical concept and essential characteristics described herein. Therefore, the detailed description above should not be construed as restrictive in any respect, but rather as illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of this disclosure are included within its scope. Furthermore, claims that are not expressly referenced in the claims may be combined to form an embodiment, or may be incorporated as a new claim after filing.

[0338] Industrial applicability

[0339] The embodiments disclosed herein can be applied to various wireless access systems. Examples of various wireless access systems include 3GPP (3rd Generation Partnership Project) systems or 3GPP2 systems.

[0340] The embodiments disclosed herein can be applied not only to the various wireless access systems described above, but also to all technical fields in which these wireless access systems are applied. Furthermore, the proposed method can be applied to mmWave and THz communication systems using ultra-high frequency bands.

[0341] Additionally, embodiments of this disclosure can be applied to various applications such as autonomous vehicles and drones.

Claims

1. A method comprising: Receive configuration information related to downlink signals; The configuration information is used to identify the resources used to request the downlink signal; as well as Use the resources to send a request signal for the downlink signal. The configuration information includes information related to at least one of the following: a signaling scheme for requesting the downlink signal, resources for sending the request signal, or the structure of the request signal. The downlink signals include the on-demand synchronization signal / physical broadcast channel block (SSB).

2. The method according to claim 1, in, The resources include at least one of the following: a random access channel timing (RO) configured for requesting the on-demand SSB, an uplink channel for scheduling requests (SR), a sounding reference signal (SRS), a physical uplink control channel (PUCCH), or a physical uplink shared channel (PUSCH).

3. The method according to claim 1, in, The resources include those on the cell that transmits the on-demand SSB.

4. The method according to claim 1, in, The steps for identifying the resource include: Select one of the multiple resources configured using the configuration information. The multiple resources are distinguished by at least one of time-domain resources, frequency-domain resources, or sequence resources.

5. The method according to claim 4, in, One of the plurality of resources is selected based on the attributes of the requested on-demand SSB.

6. The method according to claim 4, in, The multiple resources include at least one of the following: multiple resources that differ according to an SSB index or a group of SSB indexes; multiple resources that differ according to the transmission duration of an SSB; multiple resources that differ according to the transmission periodicity of an SSB; multiple resources that differ according to an SSB mode; multiple resources that differ according to a reference cell; multiple resources that correspond to a cell that supports multiple on-demand SSBs; or multiple resources that differ according to whether an SSB is a non-cell definition-SSB (NCD-SSB).

7. The method of claim 1, further comprising: Determine whether the triggering conditions for requesting the On-Demand SSB are met.

8. The method according to claim 7, in, The triggering conditions include at least one of the following: when receiving downlink data through a cell supporting the on-demand SSB, the receive timing is misaligned by a threshold greater than or equal to a threshold; downlink receive (DL RX) synchronization is misaligned by a threshold greater than or equal to a threshold; the probability of successful transmission and reception for initial transmission or retransmission is less than or equal to a threshold; the sensitivity of the signal received through the cell supporting the on-demand SSB meets the configured conditions; or the sensitivity of the signal received through a reference cell meets the configured conditions.

9. The method according to claim 7, in, Whether the triggering condition is met is determined based on whether the detected configured event exceeds the threshold.

10. The method according to claim 7, in, The request signal is sent using the resource corresponding to the triggering condition.

11. A method comprising: Send configuration information related to downlink signals; Use the resources identified by the configuration information to receive request signals for the downlink signals; as well as In response to the request signal, the downlink signal is sent. The configuration information includes at least one of the following: a signaling scheme for requesting the downlink signal, resources for sending the request signal, or the structure of the request signal. The downlink signals include the on-demand synchronization signal / physical broadcast channel block (SSB).

12. The method according to claim 11, in, The resources include at least one of the following: a random access channel timing (RO) configured for requesting the on-demand SSB, an uplink channel for scheduling requests (SR), a sounding reference signal (SRS), a physical uplink control channel (PUCCH), or a physical uplink shared channel (PUSCH).

13. The method according to claim 11, in, The resources include those on the cell that transmits the on-demand SSB.

14. The method according to claim 11, in, The resource includes one of a plurality of resources configured through the configuration information, and The multiple resources are distinguished by at least one of time-domain resources, frequency-domain resources, or sequence resources.

15. The method according to claim 14, in, One of the plurality of resources is selected based on the attributes of the requested on-demand SSB.

16. The method according to claim 14, in, The multiple resources include at least one of the following: multiple resources that differ according to an SSB index or a group of SSB indexes; multiple resources that differ according to the transmission duration of an SSB; multiple resources that differ according to the transmission periodicity of an SSB; multiple resources that differ according to an SSB mode; multiple resources that differ according to a reference cell; multiple resources that correspond to a cell that supports multiple on-demand SSBs; or multiple resources that differ according to whether an SSB is a non-cell definition-SSB (NCD-SSB).

17. The method according to claim 11, in, The request signal is received in response to whether the triggering condition for requesting the On-Demand SSB is met.

18. The method according to claim 17, in, The triggering conditions include at least one of the following: when receiving downlink data through a cell supporting the on-demand SSB, the receive timing is misaligned by a threshold greater than or equal to a threshold; downlink receive (DL RX) synchronization is misaligned by a threshold greater than or equal to a threshold; the probability of successful transmission and reception for initial transmission or retransmission is less than or equal to a threshold; the sensitivity of the signal received through the cell supporting the on-demand SSB meets the configured conditions; or the sensitivity of the signal received through a reference cell meets the configured conditions.

19. The method according to claim 17, in, Whether the triggering condition is met is determined based on whether the detected configured event exceeds the threshold.

20. The method according to claim 17, in, The request signal is received through the resource corresponding to the triggering condition.

21. An apparatus comprising: transceiver; as well as The processor is connected to the transceiver. The processor is configured as follows: Receive configuration information related to the on-demand synchronization signal / physical broadcast channel block (SSB); The configuration information is used to identify the resources used to request the on-demand SSB; and Use the resources to send a request signal for the on-demand SSB. The configuration information includes information related to at least one of the signaling scheme for requesting the on-demand SSB, the resource for sending the request signal, or the structure of the request signal.

22. An apparatus comprising: transceiver; as well as The processor is connected to the transceiver. The processor is configured as follows: Send configuration information related to the on-demand synchronization signal / physical broadcast channel block (SSB); Use the resources identified by the configuration information to receive request signals for the on-demand SSB; and In response to the request signal, the on-demand SSB is sent. The configuration information includes at least one of the following: a signaling scheme for requesting the on-demand SSB, a resource for sending the request signal, or a structure for the request signal.

23. A user equipment (UE), comprising: At least one processor; as well as At least one computer memory, connected to the at least one processor and storing instructions that, when executed by the at least one processor, direct operations including: Receive configuration information related to the on-demand synchronization signal / physical broadcast channel block (SSB); The configuration information is used to identify the resources used to request the on-demand SSB; and Use the resources to send a request signal for the on-demand SSB. The configuration information includes information related to at least one of the signaling scheme for requesting the on-demand SSB, the resource for sending the request signal, or the structure of the request signal.

24. A non-transitory computer-readable medium storing at least one instruction executable by a processor, the at least one instruction causing a device to perform an operation, the operation comprising: Receive configuration information related to the on-demand synchronization signal / physical broadcast channel block (SSB); The configuration information is used to identify the resources used to request the on-demand SSB; as well as Use the resources to send a request signal for the on-demand SSB. The configuration information includes information related to at least one of the signaling scheme for requesting the on-demand SSB, the resource for sending the request signal, or the structure of the request signal.

Images