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

Abstract

The present disclosure relates to a method for requesting a synchronization signal / physical broadcast channel block (SSB) transmitted in an on-demand manner in a wireless communication system, comprising the steps of: receiving configuration information related to an on-demand SSB; identifying, on the basis of the configuration information, a resource for requesting the on-demand SSB; and using the resource so as to transmit a request signal for the on-demand SSB, wherein the configuration information can include information related to at least one from among a signaling method for requesting the on-demand SSB, a resource for transmitting the request signal, and the structure of the request signal.

Description

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

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

[0002] The 5G mobile communications system, the successor to LTE (long-term evolution), is a new, clean-slate mobile communications system 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 (e.g., millimeter wave) above 24 GHz. 6G systems are being developed based on the underlying technologies of 5G mobile communications.

[0003] The 6G system aims to provide (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for 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 divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.

[0004] The present disclosure relates to a device and method for effectively requesting a synchronization signal / physical broadcast channel block (SSB) transmitted on-demand in a wireless communication system.

[0005] The present disclosure relates to a device and method for effectively supporting a network energy saving (NES) operation of a base station in a wireless communication system.

[0006] The present disclosure relates to a device and method for providing configuration information related to a signal for requesting transmission of SSB in a wireless communication system.

[0007] The present disclosure relates to a device and method for setting a structure of a signal for requesting transmission of SSB in a wireless communication system.

[0008] The present disclosure relates to a device and method for setting resources allocated for a signal requesting transmission of SSB in a wireless communication system.

[0009] The present disclosure relates to a device and method for setting resources for transmitting a signal for requesting transmission of SSB in a wireless communication system according to the properties of SSB.

[0010] The present disclosure relates to a device and method for selecting a resource for transmitting a signal for requesting transmission of SSB in a wireless communication system.

[0011] The present disclosure relates to a device and method for triggering a request for SSB in a wireless communication system.

[0012] The present disclosure relates to a device and method for requesting transmission of SSB in an SSB-less cell in a wireless communication system.

[0013] The technical objectives to be achieved in the present disclosure are not limited to those mentioned above, and other technical tasks not mentioned can be considered by a person having ordinary skill in the technical field to which the technical configuration of the present disclosure is applied from the embodiments of the present disclosure described below.

[0014] As an example of the present disclosure, a method includes the steps of receiving configuration information related to a downlink signal, identifying a resource for requesting the downlink signal based on the configuration information, and transmitting a request signal for the downlink signal using the resource, wherein the configuration information includes information related to at least one of a signaling method for requesting the downlink signal, a resource for transmitting the request signal, or a structure of the request signal, and wherein the downlink signal may include an on-demand SSB (synchronization signal / physical broadcast channel block).

[0015] As an example of the present disclosure, a method includes a step of transmitting configuration information related to a downlink signal, a step of receiving a request signal for the downlink signal using a resource identified based on the configuration information, and a step of transmitting the downlink signal in response to the request signal, wherein the configuration information includes information related to at least one of a signaling method for requesting the downlink signal, a resource for transmitting the request signal, or a structure of the request signal, and wherein the downlink signal may include an on-demand SSB (synchronization signal / physical broadcast channel block).

[0016] As an example of the present disclosure, a device includes a transceiver and a processor connected to the transceiver, wherein the processor is configured to receive configuration information related to an on-demand SSB (synchronization signal / physical broadcast channel block), identify a resource for requesting the on-demand SSB based on the configuration information, and transmit a request signal for the on-demand SSB using the resource, wherein the configuration information may include information related to at least one of a signaling method for requesting the on-demand SSB, a resource for transmitting the request signal, or a structure of the request signal.

[0017] As an example of the present disclosure, a device includes a transceiver and a processor connected to the transceiver, wherein the processor is configured to transmit configuration information related to an on-demand SSB (synchronization signal / physical broadcast channel block), receive a request signal for the on-demand SSB using a resource identified based on the configuration information, and transmit the on-demand SSB in response to the request signal, wherein the configuration information may include information related to at least one of a signaling method for requesting the on-demand SSB, a resource for transmitting the request signal, or a structure of the request signal.

[0018] As an example of the present disclosure, a terminal includes at least one processor, and at least one memory connected to the at least one processor and storing instructions that, when executed by the at least one processor, cause the terminal to perform operations, the operations including: receiving configuration information related to an on-demand SSB (synchronization signal / physical broadcast channel block), identifying a resource for requesting the on-demand SSB based on the configuration information, and transmitting a request signal for the on-demand SSB using the resource, wherein the configuration information may include information related to at least one of a signaling method for requesting the on-demand SSB, a resource for transmitting the request signal, or a structure of the request signal.

[0019] As an example of the present disclosure, a non-transitory computer-readable medium storing at least one program instruction, wherein the at least one program instruction, when executed by at least one processor, causes a terminal to perform operations, the operations including: receiving configuration information related to an on-demand SSB (synchronization signal / physical broadcast channel block), identifying a resource for requesting the on-demand SSB based on the configuration information, and transmitting a request signal for the on-demand SSB using the resource, wherein the configuration information may include information related to at least one of a signaling method for requesting the on-demand SSB, a resource for transmitting the request signal, or a structure of the request signal.

[0020] The above-described aspects of the present disclosure are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description of the present disclosure to be described below.

[0021] The following effects may be achieved by embodiments based on the present disclosure.

[0022] According to the present disclosure, a request for a synchronization signal / physical broadcast channel block (SSB) and a transmission operation of the SSB accordingly can be effectively performed.

[0023] The effects that can be obtained from the embodiments of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly derived and understood by those skilled in the art to which the technical configuration of the present disclosure is applied, from the description of the embodiments of the present disclosure below. In other words, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived from the embodiments of the present disclosure by those skilled in the art.

[0024] Figure 1 illustrates an example of a flexible network topology applicable to the present disclosure.

[0025] FIG. 2 illustrates an example of the structure of a wireless communication system applicable to the present disclosure.

[0026] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

[0027] FIG. 4 illustrates an example of a communication procedure between a first node and a second node applicable to the present disclosure.

[0028] Figure 5 illustrates an example of a general functional architecture related to both functionality-based life cycle management (LCM) and model-based LCM.

[0029] FIG. 6 illustrates an example of an operation procedure based on an artificial intelligence (AI) / machine learning (ML) model applicable to the present disclosure.

[0030] Figure 7 illustrates an example of an electromagnetic spectrum applicable to the present disclosure.

[0031] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication applicable to the present disclosure.

[0032] Figure 9 illustrates an example of a beam management procedure applicable to the present disclosure.

[0033] FIG. 10a illustrates an example of a general non-terrestrial network (NTN) scenario based on transparent payload applicable to the present disclosure.

[0034] Figure 10b illustrates an example of a general NTN scenario based on a replay payload applicable to the present disclosure.

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

[0036] Figure 11b shows examples of offsets in links associated with satellites.

[0037] Figure 11c illustrates examples of TA (timing advanced) values ​​in a link associated with a satellite.

[0038] Figures 12a and 12b illustrate examples of sensing operations applicable to the present disclosure.

[0039] FIG. 13 illustrates an example of time / frequency resources for sensing operations applicable to the present disclosure.

[0040] FIG. 14 illustrates an example of a procedure related to a sensing operation applicable to the present disclosure.

[0041] FIG. 15 illustrates an example of an operation procedure of a base station supporting network energy saving (NES) technology applicable to the present disclosure.

[0042] FIG. 16 illustrates an example of a procedure for a carrier aggregation (CA) operation using a synchronization signal / physical broadcast channel block (SSB)-less SCell (secondary cell) applicable to the present disclosure.

[0043] FIGS. 17A to 17C illustrate examples of on-demand system information transmission methods applicable to the present disclosure.

[0044] FIG. 18 illustrates examples of frequency bands operated by a base station according to one embodiment of the present disclosure.

[0045] FIG. 19 illustrates an example of a procedure for requesting on-demand SSB in a wireless communication system according to one embodiment of the present disclosure.

[0046] FIG. 20 illustrates an example of a procedure for transmitting a signal requesting on-demand SSB using at least one of a plurality of resources in a wireless communication system according to one embodiment of the present disclosure.

[0047] FIG. 21 illustrates an example of a procedure for requesting on-demand SSB according to conditions in a wireless communication system according to one embodiment of the present disclosure.

[0048] FIG. 22 illustrates an example of a procedure for requesting transmission of SSB for an SSB-less cell according to one embodiment of the present disclosure.

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

[0050] As used herein, a slash ( / ) or a comma may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B, or C."

[0051] In the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in the present disclosure, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0052] Additionally, in the present 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.”

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

[0054] Additionally, in the present disclosure, terms such as “first,” “second,” etc. are used only for the purpose of distinguishing one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically limited. Accordingly, a first component in one embodiment of the present 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.

[0055] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.

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

[0057] In the present disclosure, a terminal is a user equipment (UE) or a consumer-side device, and may also be referred to as a base station / second node / IAB (integrated access and backhaul) node / first node that receives / transmits signals from / to a Transmission-Reception Point (TRP). The terminal may correspond to a physical node or a logical node. The terminal may correspond to an endpoint on the user side, or may correspond to an intermediate point between other endpoints. In communication between two points that are not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), the terminal may correspond to a served node. A terminal may be a node with a fixed location, or a node with an unfixed location (or mobile).

[0058] In the present disclosure, a base station (BS) is a device on the network side, and may also be called a second node / IAB node / x-NodeB (x-NodeB, x may be an abbreviation related to a radio access technology (RAT)) / Transmission-Reception Point (TRP). A base station may correspond to a physical node or a logical node. A base station may correspond to an endpoint on the network side, or may correspond to an intermediate point between other endpoints. In communication between two points that are not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a base station may correspond to a serving node. A base station may be a node with a fixed location, or a node with an unfixed location.

[0059] In the present disclosure, higher layer parameters may be set for the terminal, preset, or predefined. For example, the base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capabilities to the base station as higher layer parameters. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0060] In the present disclosure, the information / state / parameter being “configured or pre-configured” can be interpreted as the information / state / parameter being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In the present disclosure, the information / state / parameter being “defined or pre-defined” can be interpreted as the information / state / parameter being known in advance or pre-stored at the base station and the terminal without signaling between the base station and the terminal.

[0061] The technology described in the present 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 with wireless technologies such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA can be implemented with wireless technologies such as global system for mobile communications (GSM) / general packet radio service (GPRS) / enhanced data rates for GSM evolution (EDGE). OFDMA can be implemented with wireless technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), long term evolution (LTE), and 5G NR.

[0062] The technology described in the present disclosure can be implemented with 6G wireless technology and applied to various 6G systems. For example, the 6G system can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (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.

[0063] A. 6G network architecture

[0064] Figure 1 illustrates an example of a flexible network topology applicable to the present disclosure.

[0065] To compensate for incomplete network coverage areas, a network topology that allows for more flexible and resilient split radio access networks (RANs) may be considered. For this purpose, various nodes, such as IAB nodes, relays, and RF repeaters, as illustrated in the example in Figure 1, may be applied, or a non-terrestrial network (NTN) may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, or in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that simply performs the function of signal amplification and forwarding, while a network-controlled repeater may not only amplify and forward signals but also adjust transmission and reception settings based on information provided by the network. For example, an NTN node may correspond to a satellite or aircraft that provides NTN coverage that terrestrial networks find difficult to provide. In addition to these examples, various intermediate points can be introduced to improve the network topology.

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

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

[0068] In some examples of the present disclosure, the description of a terminal may equally apply not only to a user-side endpoint, but also to an intermediate point corresponding to a terminal in a relative relationship with a network-side endpoint. Similarly, in some examples of the present disclosure, the description of a base station may equally apply not only to a network-side endpoint, but also to an intermediate point corresponding to a base station in a relative relationship with a user-side endpoint. However, in most cases where there is no additional description of the operations of three or more entities, the communicating entities in the present disclosure are briefly described as terminals and / or base stations (or first nodes and / or second nodes), and the terms terminal and / or base stations (or first nodes and / or second nodes) are interpreted to include / replace any endpoint or any intermediate point in relation to other nodes.

[0069] That is, in some examples of the present disclosure, for the sake of simplicity of explanation, the subjects of the operation may be referred to as a base station and / or a terminal (or a first node and / or a second node). In addition, the terms base station and / or terminal (or a first node and / or a second node) may also be interpreted / replaced as in the following examples: For example, the base station (or a first node) and the terminal (or a second node) may respectively correspond to a first endpoint and a second endpoint; may respectively correspond to an endpoint and an intermediate point; may respectively correspond to an intermediate point and an endpoint; or may respectively correspond to a first intermediate point and a second intermediate point.

[0070] In the present disclosure, there may be zero or more intermediate points between the base station and the terminal. If intermediate points exist, they may be IAB nodes / relays / RF repeaters / NTN (non-terrestrial network) nodes, or nodes supporting other functions. The intermediate points may be nodes with fixed locations or nodes with unfixed locations.

[0071] Systems applicable to this disclosure

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

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

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

[0075] Devices applicable to the present disclosure

[0076] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

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

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

[0079] Hereinafter, the hardware elements of the wireless device (200) will be described in more detail. Although not limited thereto, at least one protocol layer may be implemented by at least one processor (202). For example, at least one processor (202) may implement at least one layer (e.g., a functional layer 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 a message, 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) can generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this document, and provide the signal to at least one transceiver (206). At least one processor (202) can receive a signal (e.g., a baseband signal) from at least one transceiver (206) and obtain the PDU, SDU, message, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document.

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

[0081] At least one memory (204) can be connected to at least one processor (202) and can store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The at least one memory (204) can be configured as a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), a flash memory, a hard drive, a register, a cache memory, a computer readable storage medium and / or a combination thereof. The at least one memory (204) can be located internally and / or externally to the at least one processor (202). In addition, the at least one memory (204) can be connected to the at least one processor (202) via various technologies such as a wired or wireless connection.

[0082] At least one transceiver (206) can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or flowcharts of this document to at least one other device. At least one transceiver (206) can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or 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) and can transmit and receive wireless signals. For example, at least one processor (202) can control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Furthermore, at least one processor (202) can control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. In addition, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this document through at least one antenna (208). In this document, at least one antenna may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). At least one transceiver (206) may convert the received wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using at least one processor (202). At least one transceiver (206) may convert the processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using at least one processor (202).For this purpose, at least one transceiver (206) may include an (analog) oscillator and / or filter.

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

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

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

[0086] For example, the device may be a mobile device such as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, etc. In this case, the device may further include at least one of a driving unit including at least one of an engine, a motor, a power train, wheels, brakes, and a steering unit of the device, a power supply unit including a wired / wireless charging circuit, a battery, etc. that supplies power, a sensor unit that senses status information, environmental information, and user information of the device or its surroundings, an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting, and a position measurement unit that obtains location information of the mobile device through a global positioning system (GPS) and various sensors.

[0087] For example, the device may be an XR device such as an 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, a robot, etc. In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an input / output unit that obtains control information, data, etc. from the outside and outputs the generated XR object, and a sensor unit that senses status information, environmental information, and user information of the device or the surroundings of the device.

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

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

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

[0091] B. Communication Procedures

[0092] FIG. 4 illustrates an example of a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure. The second node of FIG. 1 supports dynamic spectrum sharing (DSS) to provide connectivity to both nodes implementing 6G technology and nodes implementing pre-6G wireless communication technologies (e.g., 5G, 4G). That is, the first node of FIG. 1 may implement 6G technology or pre-6G wireless communication technologies (e.g., 5G, 4G). In addition, the first node and / or the second node may support a full duplex mode as well as a non-overlapping full duplex mode.

[0093] In Fig. 4, for the sake of simplicity of explanation, the first node and the second node are assumed to be a terminal and a base station, respectively, and operations of transmitting and / or receiving data by the terminal (440) and the base station (420) and operations performed prior thereto are illustrated. However, the operations of Fig. 1 are not limited to operations between the terminal and the base station, and may be interpreted as operations between the first node and the second node. In addition, although Fig. 1 illustrates direct wireless signal transmission and reception operations between the terminal (440) and the base station (420), one or more intermediate points may exist between the terminal (440) and the base station (420), and wireless signals may be transmitted and received via one or more intermediate points.

[0094] Referring to FIG. 4, in step 401, the terminal (440) and the base station (420) perform synchronization. For example, the terminal (440) performs an initial cell search operation. Specifically, the terminal (440) can detect a synchronization signal for connection to at least one base station transmitted from the base station (420) according to a predefined rule. Here, the synchronization signal can include a plurality of 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, the terminal (440) can confirm the boundary of a unit (e.g., a frame, a subframe, a slot, and / or a symbol) constituting a wireless signal transmission of the base station (420) and obtain information (e.g., a cell identifier) ​​about the base station (420).

[0095] In step 403, the terminal (440) obtains system information transmitted from the base station (420). The system information is information related to the properties, characteristics, and / or capabilities of the base station (420) required to access the base station (420) and use the service, and may be classified according to the content (e.g., whether it is essential for access), transmission structure (e.g., channel used, whether provided on-demand), etc., and may be classified into, for example, first system information (e.g., master information block (MIB), primary system information), second system information (e.g., system information block (SIB), secondary system information), etc. If necessary, the terminal (440) may transmit a signal requesting system information before receiving the system information. However, the request and provision of the system information may be performed after the random access procedure described below.

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

[0097] In step 407, the terminal (440) and the base station (420) perform signaling of control information. Here, the control information may be defined in various layers, such as a layer that controls a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (440) and the base station (420) may perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.

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

[0099] C. 6G System Core Technologies

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

[0101] C-1. Artificial intelligence

[0102] Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0103] [Functional Framework]

[0104] The following describes a functional framework for AI / ML operations.

[0105] Below, to explain AI (or AI / ML) more specifically, the terms can be defined as follows.

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

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

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

[0109] - AI / ML Inference: The process of making predictions or inducing decisions based on collected data and the AI ​​model using a trained AI model.

[0110] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updates, etc.) can be divided into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identified by the network, and the network can direct the activation / deactivation / fallback / switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified by the network, and the network / terminal can activate / deactivate / select / switch AI / ML models based on the model ID.

[0111] Figure 5 illustrates an example of a general functional architecture relevant to both Functionality-based LCM and Model-based LCM. Some of the functions or some of the data / information / command flows (i.e., arrows) illustrated in Figure 5 may be omitted.

[0112] Referring to FIG. 5, a general functional framework can be configured to include a data collection function (510), a model training function (520), a management function (530), an inference function (540), and a model storage function (550).

[0113] The Data Collection function (510) is a function that provides input data to the Model Training function (520), Management function (530), and Inference function (540). The Data Collection function (510) can perform data preparation based on raw data and provide input data processed through data preparation. Examples of raw data may include received data / measurement data from terminals or other network entities, inference / output of AI / ML models, etc. The Data Collection function (510) may be performed by a single entity (e.g., a terminal, a network node, etc.) or may be performed by multiple entities.

[0114] Here, training data (511) refers to data required as input for the AI / ML Model Training function (520). Monitoring data (512) refers to data required as input for the AI / ML model or AI / ML function Management (530). Inference data (513) refers to data required as input for the AI / ML Inference function (530).

[0115] The Model Training function (520) performs AI / ML model training, validation, and testing, which can generate model performance metrics that can be used as part of the AI / ML model testing process. If necessary, the Model Training function (520) can perform data preparation (e.g., data pre-processing and cleaning, forming, and transformation) based on the Training Data (511) transmitted from the Data Collection function (510).

[0116] Trained / Updated Model (521): If there is a Model Storage function (550), it is used to pass a trained, validated and tested AI / ML model to the Model Storage function (550) or to pass an updated version of the model to the Model Storage function (550).

[0117] The Management function (530) is a function that supervises the operation of the AI / ML model or AI / ML function. In addition, the Management function (530) may perform decisions to ensure appropriate inference operations based on data received from the Data Collection function (510) (i.e., Monitoring Data (512)) and / or data received from the Inference function (540) (i.e., Inference Output (541)).

[0118] Management Instruction (532) is information required as input to manage the Inference function (540). The relevant information may include selection / (de)activation / switching of an AI / ML model or AI / ML-based function, and may also include fallback to non-AI / ML operations (i.e., not relying on the inference process).

[0119] A Model Transfer / Delivery Request (533) can be used to request model(s) from Model Storage (550).

[0120] A Performance Feedback / Retraining Request (531) refers to information required as input to the Model Training function (520) (e.g., for the purpose of (re)training or updating the model).

[0121] The Inference function (540) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data (i.e., Inference Data (513)) provided by the Data Collection (510) as input. Data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) may also be performed based on the Inference Data (513) delivered by the Data Collection (510). If necessary, the Inference function (540) may also perform data preparation (e.g., data preprocessing and cleaning, forming, and transformation) based on the Inference Data (513) provided by the Data Collection function (510).

[0122] Inference Output (541) is data used by the Management function (530) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (541) may also include the inference output of the AI / ML model generated by the Inference function (530), and the details of the inference output may vary depending on the use case.

[0123] The Model Storage function (550) stores a trained / updated model that can be used to perform the Inference function (540). The Model Storage function (550) illustrated in FIG. 5 can be used as a reference point (if any) when applicable to protocol termination, model transfer / delivery, and related processes. Furthermore, the Model Storage function (550) is merely an example and is not intended to limit the storage location of actual AI / ML models, and may be omitted.

[0124] Model Transfer / Delivery (551) is used to transfer AI / ML models to inference functions.

[0125] The level of cooperation can be defined as follows depending on the capability of AI / ML functions between multiple nodes, and variations due to combination of multiple levels or separation of any one level are also possible.

[0126] Cat 0a) No collaboration framework: AI / ML algorithms are purely implementation-based and do not require any changes to the wireless interface.

[0127] Cat 0b) This level corresponds to a framework with a modified wireless interface tailored to efficient implementation-based AI / ML algorithms, but without collaboration.

[0128] Category 1) involves inter-node support to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from another node (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.

[0129] Category 2) Joint AI / ML tasks can be performed across multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

[0130] FIG. 5 is a diagram illustrating an overall functional framework for an AI / ML model, and not all functions and / or all data / information / command signals illustrated in FIG. 5 may be performed within a specific node, but only some of them may be performed.

[0131] AI / ML models can be divided into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.

[0132] A one-side model can refer to an AI / ML model in which inference is performed entirely by a single node (e.g., a terminal or network). Here, AI / ML model training can also be performed entirely by a single node. AI / ML model training and inference can be performed by the same node, or they can be performed by separate nodes.

[0133] A two-side model can refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference refers to inference being performed jointly across multiple nodes. For example, the first part of the inference may be performed by a first node, and the remaining part by a second node. Two-side models can be categorized into several types depending on the training method of the AI / ML model, as follows:

[0134] - First type: 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 / objects.

[0135] - Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and terminals). Joint training can mean that model generation (e.g., CSI generation part) and model reconstruction (CSI compression by sub-use case) are trained in the same loop for forward activation and backward gradient. In this type, joint training can include both simultaneous training (i.e., model generation training and model reconstruction training are performed simultaneously) and sequential training (i.e., model reconstruction training is performed after model generation training).

[0136] - Third type: Separate training of AI / ML models can be performed on multiple nodes (e.g., networks and terminals). Separate training may mean that training begins sequentially on one node and continues on other nodes. In this case, the first node first performs the AI / ML model and shares the training data with the second node. The second node can then use the shared training data to perform the AI / ML model. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.

[0137] The operations described in the present invention described below can be described / interpreted based on the AI / ML model as shown in Fig. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for the AI / ML model). Fig. 6 illustrates an example of an operation procedure based on an AI / ML model applicable to the present disclosure.

[0138] Additionally, unless specifically limited in the description of the present invention, the AI / ML model may correspond to a one-side model in which inference is entirely performed by one node or a two-side model in which joint inference is performed by multiple nodes.

[0139] Step 1: In the description of the present invention described below, the signaling (e.g., information / data / channel / signal, etc.) or set of signaling between a specific node (e.g., terminal, network, etc.) and another node can be interpreted as the signaling or set of signaling of step 1 used to perform an operation based on an AI / ML model, even if there is no separate mention. For example, it can correspond to training data for training (i.e., generation and / or reconstruction) the AI / ML model of FIG. 2, or correspond to inference data used for inference of the AI / ML model, or correspond to feedback for the AI / ML model, etc. If signaling between nodes is not required prior to an operation based on an AI / ML model in the present invention, step 1 can be omitted. If a one-side model is used in the present invention, the unidirectional / bidirectional signaling (set) in the present invention can correspond to the signaling of step 1. In addition, when a two-side model is used in the present invention, unidirectional / bidirectional signaling in the present invention may correspond to one stage of signaling, and also repetitive signaling operations may correspond to one stage of signaling.

[0140] For example, in AI / ML model-based beam management (BM), if a base station predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from a terminal. Furthermore, if a terminal predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the terminal can receive multiple beams from the base station.

[0141] Step 2: In the description of the present invention described below, an operation (e.g., calculation, selection, prediction, etc.) in a specific node (e.g., terminal, network, etc.) or a joint operation (e.g., calculation, selection, prediction, etc.) in multiple nodes (e.g., terminal, network, etc.) may correspond to a step 2 operation based on one or more functions in the functional framework of the AI / ML model, even if not mentioned separately. For example, it may correspond to training (i.e., generation and / or reconstruction) of the AI / ML model in FIG. 2 or inference of the AI / ML model, etc. When a one-side model is used, an operation performed by a single node in the present invention may correspond to a step 2 operation, and also when a two-side model is used, a joint operation performed by multiple nodes in the present invention may correspond to a step 2 operation.

[0142] For example, in an AI / ML model-based BM, the base station can use quality / intensity information for multiple beams received from the terminal as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model. Furthermore, the terminal can measure multiple beams received from the base station and use the measurement results as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model.

[0143] Step 3: In the description of the present invention described below, the signaling (e.g., information / data / channel / signal, etc.) or set of signaling between a specific node (e.g., terminal, network, etc.) and another node can be interpreted as a three-stage signaling or set of signaling generated due to (as a result of) an operation based on an AI / ML model, even if not otherwise mentioned. For example, it can correspond to an output due to inference of the AI / ML model in FIG. 2. If signaling between nodes is not required as a result of an operation based on an AI / ML model in the present invention, Step 3 can be omitted. If a one-side model is used in the present invention, the one-way / two-way signaling (set) in the present invention can correspond to the three-stage signaling. In addition, if a two-side model is used in the present invention, the one-way / two-way signaling in the present invention can correspond to the three-stage signaling, and furthermore, a repetitive signaling operation can correspond to the three-stage signaling.

[0144] For example, in an AI / ML model-based BM, the base station can transmit to the terminal the beam(s) predicted based on the AI / ML model as candidates so that the terminal can determine the optimal beam. Furthermore, the terminal can report to the base station the beam(s) predicted based on the AI / ML model to request the base station to transmit the candidate beams as candidates for determining the optimal beam.

[0145] C-2. THz communication

[0146] Data rates can be increased by increasing bandwidth. This can be achieved by utilizing sub-THz communications with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key portion of the THz band for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While the 300 GHz to 3 THz band is part of the optical band, it lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF. Figure 7 illustrates an example of the electromagnetic spectrum applicable to the present disclosure. The embodiment of FIG. 7 can be combined with various other embodiments. Key characteristics of THz communications include (i) widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (which necessitates highly directional antennas). The narrow beamwidth generated by highly directional antennas reduces interference. The small wavelength of THz signals allows for a significantly larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.

[0147] Transmitting system information (i.e., information related to the properties, characteristics, and / or capabilities of a BS required to use a service, such as MIB, SIB, etc.) in the THz frequency band may be inefficient because, as the beam width becomes narrower in high frequency bands, more beam sweeps must be performed to cover the entire area of ​​the cell. In particular, transmitting system information in this manner is even more inefficient when there are not many users in the cell. Accordingly, a system information transmission procedure such as that illustrated in FIG. 8 may be used.

[0148] (How to receive system information)

[0149] Figure 8 illustrates an example procedure for transmitting system information for THz communication applicable to the present disclosure. While this example was developed with THz in mind, it is also applicable to 6G communication environments where THz is not applicable. Furthermore, the procedure illustrated in Figure 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below can be performed based on system information acquired through the procedure illustrated in Figure 8.

[0150] Referring to FIG. 8, in step 801, the base station (820) transmits system information of cell #1 through cell #2. That is, the base station (820) provides at least two cells, cell #1 uses a THz frequency band, and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one information / state / parameter / setting generated in each of a higher layer and a physical layer. For example, the at least one information / state / parameter / setting generated in the higher layer may include at least one of SFN, control information setting for SIB1 (e.g., PDCCH configuration for SIB1, etc.), information related to cell selection / entry (e.g., cell barring, cell re-selection, etc.), and subcarrier spacing, and the at least one information / state / parameter / setting generated in the physical layer may include at least one of SFN, half frame indicator, and SSB index. However, this is merely an example, and system information may include information / status / parameters / settings related to Cell #1 / Cell #2 generated from various types of physical layers / upper layers. For this purpose, as an example, Cell #1 and Cell #2 may have a relationship as a secondary cell and a primary cell.

[0151] In step 803, UE (810) acquires synchronization for cell #1. Synchronization can be acquired by detecting a synchronization signal. Typically, synchronization is acquired before receiving system information. However, since system information for cell #1 is received from cell #2, synchronization acquisition for cell #1 can be performed after receiving the system information. For example, UE (810) can acquire synchronization based on system information. However, unlike FIG. 8, in another example, synchronization acquisition can be performed before step 801.

[0152] In step 805, the UE (810) transmits a signal for accessing cell #1. For example, the signal may include information for accessing cell #1 (e.g., a random access preamble, etc.). The structure of the signal and the resources for transmitting the signal (e.g., a channel) may be identified through system information. Thereafter, in step 807, the UE (810) and the base station (820) perform an access procedure for cell #1 and communicate. In this step, operations according to various embodiments described below may be performed.

[0153] The procedure described with reference to FIG. 8 may be performed when the UE (801) first connects to cell #1 of the base station (820). Alternatively, a similar procedure may be performed when the UE (801) hands over to cell #1 of the base station (820). However, in the case of handover, the system information of cell #1 may be received from a cell of a base station other than cell #2 of the base station (520).

[0154] Communications in the THz band are expected to experience extremely severe path loss, and to overcome this, terminals and base stations must use extremely sharp beams. The use of sharp beams means that terminals and base stations must perform beam control in addition to beamforming, and the number of beams used increases significantly. Consequently, it takes a very long time to align the transmit and receive beams between the base station and terminals. Furthermore, if the beam alignment between the base station and terminals is misaligned due to the movement or movement of the terminals, frequent re-alignment of the beams is required, which can lead to link instability. Accordingly, a beam management procedure, as illustrated in FIG. 9 below, may be used.

[0155] (Beam search procedure in THz communication environment)

[0156] FIG. 9 illustrates an example of a beam management procedure applicable to the present disclosure. FIG. 9 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but is not limited to a THz environment, and the present disclosure is applicable to a 6G communication environment. In addition, the procedure illustrated in FIG. 9 can be combined with various embodiments of the present disclosure described below. Here, the beam can be interpreted as 'spatial (setting) information', 'spatial domain filter', 'spatial domain transmit filter', 'spatial domain receive filter', or / and a term having an equivalent technical meaning that can distinguish the beam (e.g., Reference signal, SSB (Synchronization Signal Block) Index, TRP (transmission reception point), panel, cell, TP (transmission point), base station, control resource related information (e.g., CORESET (control resource set) related information, etc.).

[0157] Referring to FIG. 9, in step 901, the base station (920) configures resources for beam management. Here, the resources may include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station (920) may utilize a beam search signal (BSS) that is transmitted spatially separated from an existing downlink signal / channel for beam search. Here, the BSS may be transmitted based on a dedicated port for beam search. The dedicated port may be a different port from a port for transmitting an existing downlink signal / channel (e.g., a synchronization signal (e.g., SSB, etc.), a data channel (e.g., PDSCH, etc.)). BSS is a term defined for convenience of explanation, and the technical concept according to the present embodiment is not limited to the term BSS itself. That is, a signal transmitted based on a dedicated port defined / configured for beam search may be included in the technical concept according to the present embodiment.

[0158] In step 903, the base station (920) transmits measurement signals using a plurality of transmission beams. For example, the measurement signals may include at least one of a reference signal and a synchronization signal. At this time, the measurement signals may be transmitted as many times as the number of beams that require measurement, and may be transmitted in a multi-beam transmission method that forms a plurality of beams simultaneously to reduce the sweeping time. Here, the multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).

[0159] In step 905, the UE (910) transmits a feedback signal to the base station (920). The feedback signal indicates at least one beam selected by the UE (910). The UE (910) may select at least one preferred beam based on the measurement signals received in step 903. In step 907, the UE (910) and the base station (920) perform communication. At this time, the UE (910) and the base station (920) may perform communication using the beam selected in step 905. If channel reciprocity is established, the transmission beam of the UE (910) may also be determined through steps 903 and 905, and thus, the transmission operation of the UE (910) may also be performed using the beam selected in step 905. If channel reciprocity is not established, a procedure including transmitting measurement signals of the UE (910) and transmitting feedback signals of the base station (920) may be performed to determine the transmission beam of the UE (910). In step 907, operations according to various embodiments described below may be performed.

[0160] C-3. Non-terrestrial networks (NTN)

[0161] NTN can refer to a network or network segment that uses RF (radio frequency) resources mounted on a satellite (or unmanned aerial system (UAS) platform). The use of NTN services has been considered to secure wider coverage or to provide wireless communication services in locations where it is difficult to install wireless communication base stations. NTN services can collectively refer to a wireless communication system that provides terminals by installing base stations on satellites (e.g., geostationary-orbit, low-Earth orbit, medium-geometry satellites, etc.), airplanes, unmanned airships, drones, etc. rather than on the ground. The satellite described in the present disclosure can move at high speed from a specific location on the Earth, and the satellite beam directed toward the Earth can correspond to an area on the Earth where the satellite can provide services to users.

[0162] As an example of the present disclosure, NTN scenarios can be divided into Earth-fixed cell scenarios and Earth-moving cell scenarios depending on the type of cell supported by the satellite. The Earth-fixed cell scenario refers to a scenario in which a cell is maintained permanently or for a specific service period within a specific location on the Earth's surface based on the satellite's beam steering function. The Earth-moving cell scenario refers to a scenario in which a cell within the Earth's surface continuously moves as the satellite's beam steering function is not utilized and a fixed beam is used for service.

[0163] As another example of the present disclosure, the NTN scenario can be divided into a typical NTN scenario based on a transparent payload and a typical NTN scenario based on a regenerative payload, depending on the characteristics of the payload. Fig. 10a illustrates an example of a typical NTN scenario based on a transparent payload applicable to the present disclosure. Fig. 10b illustrates an example of a typical NTN scenario based on a regenerative payload applicable to the present disclosure. The embodiments of Fig. 10a or Fig. 10b can be combined with various embodiments of the present disclosure. Referring to Fig. 10a, a satellite (or UAS platform) can create a service link with a UE. The satellite (or UAS platform) can be connected to an (NTN) gateway via a feeder link. The satellite can be connected to a data network via the gateway. A beam footprint can refer to an area where a signal transmitted by a satellite can be received. Referring to Figure 10b, a satellite (or UAS platform) can establish a service link with a UE. A satellite (or UAS platform) connected to a UE can be connected to another satellite (or UAS platform) via an inter-satellite link (ISL). The other satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on the replay payload, a satellite can be connected to a data network through another satellite and the gateway. If an ISL does not exist between a satellite and another satellite, a feeder link between the satellite and the gateway may be required. Figures 10a and (b) are merely examples of NTN scenarios, and NTN can be implemented based on various scenarios.For example, a satellite (or UAS platform) may implement a transparent or regenerative (with onboard processing) payload. For example, a satellite (or UAS platform) may generate multiple beams over a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) may vary depending on the onboard antenna diagram and minimum elevation angle. For example, a transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may not be altered. For example, a regenerative payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, a regenerative payload may be substantially equivalent to equipping the satellite (or UAS platform) with all or part of the base station functionality.

[0164] Below, we describe procedures (e.g., initial cell selection, mobility management in idle mode, and mobility management in connected mode) for maintaining network service continuity and satellite coverage in a wireless communication system utilizing NTN elements.

[0165] - Initial cell selection procedure

[0166] Upon power-on, the terminal can search for the first satellite-based NTN cell (or the satellite broadcasting the cell). At this time, if the terminal has satellite orbit information (i.e., ephemeris data) and / or round-to-trip (RTT) information that can be used when performing a cell entry procedure (e.g., a random access procedure), the terminal can use such information to shorten the cell search procedure and the time required for cell search. To this end, the terminal may require (initial) system information including satellite ephemeris information to identify the exact location of the cell, and the (initial) system information may be set / determined / generated based on orbital plane information already possessed by the terminal. For example, satellite-level orbit parameters for all satellites capable of providing services to the terminal through the terminal uSIM, including satellite IDs or indices, may be provided in advance. Afterwards, the satellite ID of the service satellite is broadcast as part of the system information, allowing the terminal to derive ephemeris data and / or location coordinates of the service satellite stored in the uSIM. Additionally, to assist mobility handling, the terminal can obtain information about neighboring satellites through system information and / or dedicated RRC signaling.

[0167] Here, the satellite ephemeris information transmitted to the terminal via system information and / or RRC signaling can be implemented / supported in i) a position and velocity state vector orbit format and ii) an orbital parameter ephemeris format. For example, the position and velocity state vector orbit format can be configured with 17 bytes or less (e.g., 132 bits). The field size for position (x, y, z)(m) can be 78 bits, and the field size for velocity (vx, vy, vz)(m / s) can be 54 bits.

[0168] The orbital parameter ephemeris format can be composed of 21 bytes or less (e.g., 164 bits). Fig. 11a illustrates an example of the components of the orbital parameter ephemeris format. The components of the orbital parameter ephemeris format illustrated in Fig. 11a are as follows.

[0169] - Semi-major axis (half the major axis of an elliptical satellite orbit) "α" [m] (e.g. 33 bits)

[0170] - Eccentricity "e" (in an elliptical satellite orbit, 0 <e<1)(예: 20 비트)

[0171] - Argument of periapsis (the angle from the orbital periapsis, the point where an object is closest to the central body when orbiting, to the ascending node, which determines the direction of the ellipse in the orbital plane) "ω" (e.g. 28 bits) [rad]

[0172] - Longitude of ascending node (the angle measured counterclockwise from a reference point (e.g., the vernal equinox in the solar system) to the ascending node (the point where the orbit passes above the reference plane)) "Ω" (e.g., 28 bits) [rad]

[0173] - (orbital) inclination (the degree of tilt of the ellipse with respect to the reference plane, measured as the angle between the orbital plane and the reference plane at the ascending node) "i" (e.g. 27 bits) [rad]

[0174] - Mean anomaly (mathematically convenient angle that changes continuously over time, but does not correspond to a geometric angle) "M0" = M(t0) (e.g. 28 bits) [rad] at epoch t0 [JD]

[0175] - Mobility management in idle mode

[0176] During idle mode, the location of a terminal can be identified at the tracking area level / unit. Here, a tracking area is defined as a set of cells, and each cell can belong to a tracking area identified by a tracking area code (TAC). The TAC can be transmitted via system information on a broadcast channel. Multiple cells can belong to the same tracking area, and the same TAC corresponding to the same tracking area can be broadcast. The location of a terminal can be announced to the network when the terminal is first powered on (i.e., when performing a registration procedure). The registration request message transmitted by the terminal for the registration procedure can include the TAC of the cell in which the terminal is currently camping. When the terminal changes cells as it moves, the tracking area of ​​the corresponding cell can be determined by decoding the system information of the changed cell. The terminal can move within the same tracking area without performing an update. When a terminal enters a new cell using a different TAC, the terminal can register in the new cell and transmit a new TAC to update the network about its location. Consequently, a larger tracking area can reduce signaling from the terminal to the network, minimizing terminal power consumption. When the network needs to reach a terminal in idle mode (e.g., during an incoming call), the network can page the terminal in all cells within the last tracking area in which the terminal registered. If the tracking area is very large and contains many cells, the network may page the terminal in all cells within the TAC, resulting in an increased number of pages. If the same model is used for a satellite system, with each satellite broadcasting a TAC, the tracking area can sweep the ground as the satellite orbits the Earth.In this case, even stationary terminals must frequently perform registration updates, which can impact terminal battery life and increase uplink signal throughput. To address this, the system can be designed so that the tracking area does not change its geographic location on Earth. Instead, the tracking area can change as the satellite moves, entering a new geographic area and updating the TAC broadcast by the satellite to reflect the new geographic area. Simultaneously, the terminal can perform a tracking area update procedure if it detects a new TAC on the broadcast channel. Accordingly, if the terminal's physical location on Earth does not change, the tracking area can remain fixed.

[0177] - Mobility management in connected mode

[0178] While the UE is in connected mode, mobility management procedures can be handled by handover. For terrestrial / NTN networks, handovers can be triggered by the network (i.e., measurement handover triggering) based on measurements reported by the UE regarding the current cell and neighboring cell signal quality. Within the handover procedure, service interruption time is defined as the time from when the UE ceases transmitting and receiving with the source base station to when it resumes transmitting and receiving with the target base station. The interruption time may vary for uplink and downlink. For downlink, the interruption time can be defined as the time from when the network transmits a synchronized RRC reconfiguration message to when the target base station receives an RRC reconfiguration complete message. After transmitting the RRC reconfiguration message, the base station cannot send any more data and can resume communication after receiving the RRC reconfiguration complete message. For uplink, the UE can potentially continue transmitting data to the source base station until a synchronized RRC reconfiguration message is received. And, the downtime can be defined as the time from the time the terminal receives a synchronized RRC reset message to the time the target base station receives an RRC reset complete message.

[0179] The propagation delay of satellite-based NTN is much larger than that of terrestrial systems, which may incur additional latency for mobility signals such as measurement reports, handover (HO) command reception, and HO requests / ACKs (if the target cell originates from a different satellite). The geostationary Earth orbit (GEO) scenario is characterized by much larger propagation delays than the low Earth orbiting (LEO) scenario, but the latter must take satellite movement into account. To avoid extended service interruptions, the latency associated with mobility signals must be addressed in both cases. In addition to the measurement-triggered handover described above, other handover triggering methods may be utilized, such as handover triggering based on the position of the UE and the satellite (or the distance between the UE and the satellite), handover triggering based on the timing advance (TA) of the target cell, handover triggering based on deterministic satellite movement / local time, and handover triggering based on the elevation angle of the source / target cells. Additionally or alternatively, the terminal may be provided with handover settings and triggering conditions (e.g., terminal / satellite location, signal strength transmitted by the terminal / satellite, etc.) in advance. For example, the terminal may receive handover settings and triggering conditions through information about a new cell that will be the handover target. Accordingly, the terminal can monitor handover conditions and, if the conditions are met, perform a handover to the target cell.

[0180] Meanwhile, as described above, wireless communication systems utilizing NTN elements have significantly larger RTT values ​​compared to terrestrial communication systems. Therefore, various types of offsets and TA values ​​can be set / defined / indicated / signaled for efficient time / frequency synchronization. Below, offsets (e.g., K_offset and k_mac), TA values, validity duration, and epoch time for time / frequency synchronization in NTN-based wireless communication systems are described.

[0181] - K_offset and k_mac

[0182] Figure 11b illustrates examples of offsets in a satellite-related link. K_offset illustrated in Figure 11b is an offset value indicating the RTT of an uplink time synchronization reference point (RP). Here, K_offset may correspond to the sum of the service link RTT and the common TA (if indicated). k_mac illustrated in Figure 11b is an offset value indicating the RTT between the RP and the base station. For example, K_offset may be applied to i) DCI and PUSCH transmission timing scheduled by the DCI, ii) random access response (RAR) and PUSCH transmission timing based on the RAR, iii) PUSCH transmission timing based on a configured grant, iv) PUCCH transmission timing according to MsgB, v) aperiodic SRS / CSI resource transmission timing, etc. For example, k_mac may be applied to terminal actions and assumptions regarding a downlink configuration indicated by a MAC-CE command in a PDSCH. In the beam failure recovery procedure, for PRACH transmission in uplink slot n, the terminal may monitor the corresponding PDCCH starting from downlink slot "n+k_mac+4" within the corresponding RAR window.

[0183] The cell-specific K_offset can be signaled via NTN-related system information (e.g., NTN-specific SIB). A range of cell-specific K_offset values ​​(0 to 1023 ms) can be used to cover all scenarios. A differential UE-specific K_offset can be signaled via MAC CE, and the differential UE-specific value range is 0 to 63 ms. The total UE-specific K_offset value is equal to the cell-specific K_offset value minus the differential UE-specific K_offset value. k_mac can be provided by the network when the downlink and uplink frame timings are not aligned at the base station. k_mac updates are not supported, and the value range can be 1 to 512 ms. If the UE does not receive a k_mac value from the network, the UE can assume k_mac to be 0. The reference SCS value for the units of K_offset in FR1 can be 15 kHz.

[0184] - UE-specific TA and common TA

[0185] In an NTN-based communication system, a terminal can calculate TA based on the terminal's global navigation satellite system (GNSS) capability (e.g., terminal position) and upper layer parameters related to satellite orbit (ephemeris) transmitted from a base station, and this is called terminal-specific TA ( ) is named. If the upper layer parameters related to the satellite orbit are not received from the base station, the terminal-specific TA can be set to 0. Then, the TA calculated based on the common TA parameters (e.g., TACommon, TACommonDrift, and / or TACommonDriftVariation), which are upper layer parameters transmitted from the base station, is called the common TA ( ) is named. If the common TA parameter is not transmitted from the base station, the common TA can be set to 0. Accordingly, the total TA value (T_TA) in the NTN-based communication system is It can be calculated as follows. N_TA,offset means the TA offset value provided to the terminal for each serving cell, and N_TA means the value derived based on the timing advance command.

[0186] Figure 11c illustrates examples of timing advanced (TA) values ​​for a satellite-related link. As illustrated in Figure 11c, a terminal-specific TA is calculated to compensate for transmission delay for the service link, and a common TA is calculated to compensate for transmission delay between the RP and the satellite.

[0187] - Valid interval and epoch time

[0188] The validity period refers to the (maximum) time period during which the terminal can apply the previously acquired assistance information (from the epoch time) without acquiring new assistance information (e.g., serving and / or neighboring satellite orbits (ephemeris) and common TA parameters, etc.). The configuration information related to the validity period can be broadcast from the base station via the NTN-related system information (e.g., SIB19) for each cell. For example, the validity period length range can be configured as, but is not limited to, {5s, 10s, 15s, 20s, 25s, 30s, 35s, 40s, 45s, 50s, 55s, 60s, 120s, 180s, 240s, 900s}. The validity timer with the set validity period value can be (re)started at the epoch time of the assistance information. If no new or additional support information is available within that validity period, the terminal may assume that uplink synchronization is lost.

[0189] The serving satellite ephemeris and common TA parameters are signaled in the same SIB message and may have the same epoch time. If the epoch time is explicitly provided via SIB, the epoch time of the assistance information (i.e., the satellite ephemeris and common TA parameters) is the start time of the DL subframe indicated by the SFN and the subframe number signaled together with the assistance information. If the epoch time is not explicitly indicated via SIB, the epoch time of the assistance information may be implicitly known as the end of the SI window in which NTN-specific system information (e.g., SIB19) is transmitted. If the epoch time is provided via dedicated signaling, the epoch time of the assistance information is the start time of the DL subframe and may be indicated by the SFN and the subframe number.

[0190] For a serving cell, if the epoch time is explicitly indicated by the SFN and subframe number, the UE may consider the frame as the current SFN or the next SFN after the frame in which the message indicating the epoch time was received. For a neighboring cell, if the epoch time is explicitly indicated by the SFN and subframe number, the UE may consider the frame as the frame closest to the frame in which the message indicating the epoch time was received.

[0191] C-4. Integrated Sensing and Communication (ISAC)

[0192] Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Because radio frequency sensing does not require a networked device to connect to the object, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of wireless sensing services, i.e., sensing operations, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing offers an opportunity to enhance existing communication systems from a communications network to a wireless communication and sensing network.

[0193] FIGS. 12A and 12B illustrate examples of sensing operations applicable to the present disclosure. The embodiments of FIGS. 12A and 12B can be combined with various embodiments of the present disclosure. Specifically, FIG. 12A illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and FIG. 12B illustrates an example of sensing using separate sensing receivers and sensing transmitters (e.g., bistatic sensing).

[0194] For example, in a wireless communication system based on a 6G network of the present disclosure, referring to FIG. 12a, the sensing transmitter and the sensing receiver may be configured to be included in a single base station (i.e., the same base station) or a single terminal (i.e., the same terminal). Alternatively, referring to FIG. 12b, the sensing transmitter and the sensing receiver may be configured to be included in different base stations, different terminals, or each terminal and base station.

[0195] In this regard, the following six types of sensing modes can be defined based on whether the sensing transmitter and sensing receiver are included in the base station or the terminal, respectively.

[0196] - Mode 1: A mode in which the sensing transmitter and sensing receiver are contained in a single base station (e.g., base station-based sensing mode in monostatic mode).

[0197] - Second mode: 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., base station-based sensing mode in bistatic mode).

[0198] - Mode 3: A mode in which the sensing transmitter is included in the base station and the sensing receiver is included in the terminal (e.g., base station-terminal sensing mode).

[0199] - Mode 4: A mode in which the sensing transmitter is included in the terminal and the sensing receiver is included in the base station (e.g., terminal-base station sensing mode).

[0200] - Mode 5: A mode in which the sensing transmitter and sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode).

[0201] - 6th mode: A mode in which the sensing transmitter is included in a first terminal and the sensing receiver is included in a second terminal different from the first terminal (e.g., terminal-based sensing mode in bistatic mode).

[0202] In a wireless communication system based on the 6G network of the present disclosure, one or more of the six types of sensing modes described above may be utilized independently / in combination.

[0203] With respect to the sensing operation in FIGS. 12A and 12B , the sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or an environment around the objects). For example, the sensing signal may correspond to a radio (frequency) signal defined to be transmittable by a base station / terminal in a wireless communication system based on a 6G network of the present disclosure. The sensing receiver may receive a signal scattered / reflected by one or more objects (and / or an environment around the objects) from the sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signals, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing results may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment around the objects). The sensing results generated / obtained in this way may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided in a wireless communication system based on the 6G network of the present disclosure, or may be provided / disclosed to a trusted third party.

[0204] Additionally, the sensing operations in FIGS. 12A and 12B are described as a representative example of operations in a wireless communication system based on a 6G network, but can be extended and applied to cases where terminals / base stations / signals based on networks of previous generations (e.g., 4G, 5G, etc.) are utilized.

[0205] Additionally, with respect to the wireless sensing described in the present disclosure, in a wireless communication system based on a 6G network of the present disclosure, time / frequency resources for sensing operations and time / frequency resources for general communications (e.g., UL / DL / sidelink-based communications, etc.) may be scheduled / configured separately.

[0206] FIG. 13 illustrates an example of time / frequency resources for sensing operations applicable to the present disclosure. The embodiment of FIG. 13 may be combined with various embodiments of the present disclosure.

[0207] Referring to FIG. 13, time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 12a and FIG. 12b) can be set / allocated separately from time / frequency resources (hereinafter, communication resources) for general communication.

[0208] For example, as illustrated in FIG. 13, sensing resources can be set / allocated in units of symbols in the time domain and / or resource blocks in the frequency domain. Resources other than those for which the sensing resources are set / allocated can be utilized as resources for general communication. That is, sensing resources and communication resources can be set / allocated based on the time-division multiplexing (TDM) method and / or the frequency-division multiplexing (FDM) method in terms of the operation of the base station / terminal. Additionally or alternatively, unlike what is illustrated in FIG. 13, sensing resources can also be set / allocated based on other units in the time domain (e.g., slots, frames, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarriers, carriers, absolute frequencies (MHz, GHz), etc.).

[0209] Additionally or alternatively, in connection with the setting / allocation / scheduling of resources for general communication as described in the present disclosure, the relationship between the resources and the aforementioned sensing resources may need to be considered. For example, when setting / allocating resources for general communication according to the embodiment(s) of the present disclosure, the resources may be set / allocated to rate-match or puncture the resource region corresponding to the sensing resource. For example, when scheduling resources for general communication according to the embodiment(s) of the present disclosure, the resources may be scheduled so as not to overlap with the resource region corresponding to the sensing resource. If the resources for general communication according to the embodiment(s) of the present disclosure and the resource region corresponding to the sensing resource are set / allocated / scheduled to overlap, one or both operations may be dropped, skipped, or postponed based on priorities, predefined rules, etc. That is, in the embodiment(s) of the present disclosure, it may be desirable that resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) are set / allocated / scheduled so as not to overlap with the aforementioned sensing resources.

[0210] Additionally, various channel modeling methods may be applied to the wireless sensing described in the present disclosure. Channel modeling related to sensing may refer to configuring a path for transmitting and receiving sensing signals and / or scattered / reflected signals, taking into account the object being sensed and / or the environment in which the object resides. Channel modeling may be related to the performance / requirements of sensing in a wireless communication system, and thus may be an important factor in validating the sensing function.

[0211] Channels related to sensing can be divided into channels between objects (e.g., targets of interest) and sensing transmitters / receivers, and channels between the environment to which the object belongs and sensing transmitters / receivers. In this regard, channel modeling related to sensing can be divided based on sensing mode (e.g., the six types of modes described above), whether there is an object / environment, and / or sensing scenarios. For example, channel modeling for a target in a base station / terminal-based monostatic sensing mode, channel modeling for a target in a base station / terminal-based bistatic sensing mode, channel modeling for the environment in a base station / terminal-based monostatic sensing mode, and channel modeling for the environment in a base station / terminal-based bistatic sensing mode can be configured and optimized differently. For example, when various sensing scenarios are classified, channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios can be divided, etc. Additionally, channel modeling related to sensing may be based on statistical channel modeling techniques and / or deterministic channel modeling techniques. For example, modeling for sensing in a wireless communication system based on a 6G network of the present disclosure may be based on stochastic geometric channel modeling techniques and / or a hybrid with ray tracing channel modeling technique. Here, the stochastic geometric channel model may be based on various statistical characteristics of the channel state. Furthermore, the hybrid channel model may be based on both ray tracing techniques and stochastic techniques.In a hybrid approach, channels for objects requiring high accuracy and consistency (e.g., targets of interest) can be modeled using ray tracing techniques, while channels for the environment can be modeled using probabilistic techniques.

[0212] FIG. 14 illustrates an example of a procedure related to a sensing operation applicable to the present disclosure. The embodiment of FIG. 14 may be combined with various embodiments of the present disclosure.

[0213] For example, in a wireless communication system based on a 6G network of the present disclosure, in the case of a sensing operation in which a terminal participates, the base station may need to verify the capability of the terminal for the sensing operation. In this regard, the terminal may be configured to report capability information regarding whether it supports the sensing operation to the base station. Additionally or alternatively, if the terminal is predefined in the standard to support the sensing operation, the procedure may be omitted. In addition, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information regarding whether it supports the sensing operation to an entity that configures / controls its sensing operation (e.g., a network entity at a higher level / layer of the base station).

[0214] For example, the base station can perform signaling with the terminal to exchange configuration information related to the sensing operation. For example, the base station can configure / instruct the terminal information about the mode of the sensing operation (e.g., based on the six types of modes described above), the subject of the sensing operation (e.g., sensing transmitter, sensing receiver), the resource of the sensing operation (e.g., sensing resource as in FIG. 13), the target of utilizing the sensing result (e.g., type of wireless sensing service based on 6G network, trusted third party), channel modeling for sensing (e.g., channel between the base station / terminal and object / environment), etc. For example, the base station can also configure / instruct such information from a network entity at an upper level / layer of the base station.

[0215] For example, the base station and / or the terminal may perform a sensing operation based on the set / instructed information. For example, the base station and / or the terminal may, as a sensing transmitter and / or a sensing receiver, perform procedures such as transmitting a sensing signal, receiving a scattered / reflected signal, deriving sensing data, obtaining a sensing result through processing the sensing data, and providing the sensing result, as in FIGS. 12A and 12B described above. As an example, in the operation of the base station / terminal described in the present disclosure, a sensing result provided through a sensing operation may be utilized.

[0216] D. NES (network energy saving)

[0217] Energy conservation at base stations is a key consideration in wireless communication systems, including 3GPP, as it can contribute to building eco-friendly networks by reducing carbon emissions and reducing operational expenditures (OPEX) for telecommunications companies. In particular, the introduction of 5G communications will require higher transmission rates, necessitating base stations to be equipped with more antennas and provide services across wider bandwidths and frequency bands. Consequently, recent studies have shown that base station energy costs have reached as high as 20% of total OPEX. Accordingly, 5G systems are adopting various technologies to reduce energy consumption, known as network energy savings (NES), and the standardization of related technologies is expected to continue. Specifically, the following techniques were discussed in the recent Rel-18.

[0218] -----------------------------------------------------------------------

[0219] 1. If deemed feasible by RAN4 studies, specify SSB-less SCell operation for interband CA for FR1 and co-located cells, where the UE measures SSB 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 procedure if required. [RAN4, RAN2]]

[0220] 2. Embody improvements to the cell DTX / DRX mechanism, including inter-node information exchange for cell DTX / DRX and alignment of cell DTX / DRX and UE DRX in RRC_CONNECTED mode. [RAN2, RAN1, RAN3]

[0221] ·Note: No changes to SSB transmission due to cell DTX / DRX.

[0222] ·Note: The above improvements should avoid any impact on IDLE / INACTIVE UEs.

[0223] 3. Implement the following technologies in the space and power domains:

[0224] · To enable efficient adaptation of spatial elements (e.g., antenna ports, active transceiver chains), specify necessary improvements to CSI and beam management-related procedures, including measurement and reporting, and signaling. [RAN1, RAN2]

[0225] · To enable efficient adaptation of power offset values ​​between PDSCH and CSI-RS, necessary improvements to CSI-related procedures, including measurement, reporting, and signaling, are specified. [RAN1, RAN2]

[0226] · Note: The above goals are only applicable to UE specific channels / signals.

[0227] · Note: Given the total number and requirements of CSI reports, conventional UE CSI / CSI-RS capabilities apply.

[0228] 4. If necessary, specify a mechanism to prevent camping of legacy UEs in cells adopting Rel-18 NES technology. [RAN2]

[0229] 5. Implement improvements to the CHO procedure when the source / target cell is in NES mode. [RAN2]

[0230] 6. Improvements to limit paging in limited areas and specify inter-node beam activation [RAN3].

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

[0232] -----------------------------------------------------------------------

[0233] According to the application of NES technology, the base station can perform operations such as controlling on / off for a certain duration in the time domain, controlling transmission / reception resources for UE-common or UE-specific signals / channels, changing the amount of frequency domain resources, controlling transmission power, or turning on / off antenna ports, transmission-reception points (TRPs), etc. in the spatial domain. Fig. 15 illustrates an example of an operation procedure of a base station supporting the NES technology applicable to the present disclosure. Referring to Fig. 15, the base station identifies NES solution(s) to be applied. The NES solution(s) may be related to control of signal transmission / reception (e.g., on / off), beam operation, handover procedure, channel measurement and reporting, etc. Which NES solution(s) to apply can be adaptively selected or predefined depending on the current situation (e.g., cell load level, characteristics of connected terminals, etc.). The base station, having identified the NES solution(s), performs signaling for the NES. The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information about the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of the NES operation to at least one terminal. In addition, the base station may receive capability information related to the NES from at least one terminal. Thereafter, the base station performs operations for the NES. At this time, the base station may perform operations for the NES based on the previously performed signaling. That is, based on the system information, configuration information, and control information transmitted through the signaling, the base station may turn on / off the transmission / reception of a specific signal, turn on / off elements in the spatial domain, or adjust resources for the transmission / reception of a measurement signal.

[0234] Through a procedure similar to that in Fig. 12, NES technology can be implemented. Examples of NES solutions that can be implemented through a procedure similar to that in Fig. 12 are as follows.

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

[0236] · Inter-system energy saving solution: NG-RAN nodes that own capacity booster cells can autonomously transition those cells to an inactive state.

[0237] · SSB-less SCell solution: If SSB or SMTC (SSB-based RRM measurement timing configuration) configuration is not provided for the SCell, the UE can obtain the timing reference and AGC source from another serving cell. In FR1 or FR2, the base station can configure intra-band CA or inter-band CA including the SCell without SSB transmission, in which case the SSB / SIB transmission can be triggered by the WUS (wake-up signal) of the UE. Accordingly, since the period of common channels / signals such as SSB increases, the base station can stay in the sleep state for a longer time.

[0238] · Cell DTX / DRX (discontinuous transmission / discontinuous reception) solution: In order to reduce the downlink transmission / uplink reception activity time of a base station, a periodic cell DTX / DRX pattern (e.g., active and inactive periods) can be commonly set for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern can be separately set and activated, and up to two cell DTX / DRX patterns can be set per MAC entity. When cell DTX is set and activated, at least one of monitoring for SPS opportunities or monitoring PDCCH can be stopped during the cell DTX inactivity period. When cell DRX is set and activated, at least one of transmission on CG resources or SR transmission can be stopped during the cell DRX inactivity period. Cell DTX / DRX can be activated / deactivated via RRC signaling or L1 group common signaling.

[0239] · Parameters such as active duration and cycle may be configured for cell DTX / DRX. The active duration is the period during which the UE receives a PDCCH or SPS opportunity and waits to transmit SR or CG, and the cycle specifies the periodic repetition of the active duration and the inactive duration. When both cell DTX and cell DRX are configured, parameters such as active duration and cycle are common. If the base station recognizes an emergency call or a public safety-related service (e.g., MPS or MCS), the network may release or deactivate the cell DTX / DRX configuration so as not to affect the service. In addition, at least some overlap is required between the active duration of the connected mode DRX of the UE and the active duration of the cell DTX / DRX. For example, the connected mode DRX cycle of the UE may be a multiple of the cell DTX / DRX cycle, or vice versa.

[0240] · Conditional handover (CHO) solution: A CHO procedure is used when the UE determines whether to execute a handover while NES technology is applied (e.g., when the cell activates or deactivates cell DTX / DRX). In this case, the UE can use an NES-specific CHO event to initiate CHO to a candidate cell, and the reception of a DCI activating the CHO condition(s) set by the NES event indication can be applied as an additional triggering condition for this.

[0241] · Spatial and Power Domain Adaptation Solution: To support gNBs for transceiver muting and / or transmit power adaptation, a UE may 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 pattern (e.g., a subset of available spatial elements) and / or a power offset between a data channel (e.g., PDSCH) and CSI-RS. Depending on the application of the spatial and power domain adaptation solution, the CSI configuration, measurement, and / or reporting behavior may be affected.

[0242] SCell without SSB

[0243] FIG. 16 illustrates an example of a procedure for a CA operation using an SSB-less SCell applicable to the present disclosure. Referring to FIG. 16, a base station transmits configuration information for an SCell to a terminal. That is, the base station transmits configuration information for CA to provide a service to the terminal through a CA operation. Here, the CA operation may be an intra-band CA or an inter-band CA. For example, the configuration information for an SCell may include information including information for adding an SCell (e.g., sCellToAddModList), and specifically, may include a cell index, a physical cell identifier, information related to DL-UL configuration, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Then, the terminal can determine the configuration for the CA operation and perform communication using the PCell and SCell of the base station. At this time, the terminal can confirm that the SCell is an SSB-less SCell based on the information related to the downlink frequency included in the configuration information, and check the related parameters. For example, the UE can determine that the SCell is an SSB-less SCell by checking for the presence of a parameter indicating that the SCell is an SSB-less SCell (e.g., SSBlessSCell), and can determine the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the case of Figure D03, the reference cell may be the PCell. Therefore, the UE can use the PCell as a timing reference and AGC source for communications on the SCell.

[0244]

[0245] In 3GPP NR release 19, a work item titled “Enhancements of network energy savings for NR” was additionally approved. Specifically, the following enhancement techniques are being considered in 3GPP NR release 19:

[0246] -----------------------------------------------------------------------

[0247] Objectives of SI (study item) or core part WI (work item) or test part WI

[0248] The goals of WI are:

[0249] 1. Specify procedures and signaling methods to support on-demand SSB SCell operation for both in-band and inter-band CA for UEs in connection mode set to CA. [RAN1 / 2 / 3 / 4]

[0250] · Specify the triggering method(s). (Select from UE uplink wake-up signaling using existing signals / channels, cell on / off indication via backhaul, and Scell ​​activation / deactivation signaling.)

[0251] · Note 1: On-demand SSB transmission can be used by the UE for minimum SCell time / frequency synchronization, L1 / L3 measurements, and SCell activation, and is supported for FR1 and FR2 in unshared spectrum.

[0252] 2. Study the procedures and signaling method(s) to support on-demand SIB1 for UEs in idle / inactive mode, as follows: [RAN1 / 2 / 3]

[0253] · Triggering method by uplink wake-up signal using existing signal / channel.

[0254] · Provide wake-up signal settings to the UE

[0255] - Note: Modification of SSB is not discussed in this goal.

[0256] · If necessary, exchange information between gNBs at least for setting up wake-up signals.

[0257] · Checkpoints for normative work in RAN#105

[0258] 3. Implement adaptation of common signal / channel transmission [RAN1 / 2 / 3 / 4]

[0259] · Adaptation of SSB in the time domain, e.g. periodic adaptation

[0260] · PRACH adaptation in the time domain

[0261] · Study adaptation of PRACH in the spatial domain, e.g., non-uniform PRACH resources per SSB, and implement if found to be beneficial.

[0262] - This study will be conducted only in the second quarter of 2024.

[0263] · Coordination of paging opportunities, including limiting paging opportunities in the time domain.

[0264] - Note: Paging delay time should not increase.

[0265] - Note: There should be no negative impact on existing UEs unless significant benefits are achieved.

[0266] 4. For the above features, specify the corresponding core requirements. [RAN4]

[0267] -----------------------------------------------------------------------

[0268] On-demand SSB

[0269] Through the aforementioned objective 1, a method can be discussed to reduce energy consumption by having the base station transmit SSB on a specific cell through the on-demand SSB process and not transmit SSB on the cell when the on-demand SSB process is not available. In the existing NR system, SSB must be transmitted periodically and constantly for purposes such as time / frequency synchronization or RRM measurement, making it difficult to reduce energy consumption even when the base station has no data to receive or send. Considering this, the base station can reduce base station energy consumption by not performing SSB transmission until the on-demand SSB process is involved and then performing SSB transmission. The on-demand SSB process can be triggered using one of the following methods:

[0270] 1) The terminal requests SSB transmission from the base station by transmitting an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS in the NR system).

[0271] 2) Requesting SSB transmission from base station (or TRP) #1 to base station (or TRP) #2 through an interface between base stations (e.g., Xn interface in NR system) or backhaul signaling.

[0272] 3) Signaling whether SSB transmission is possible for the corresponding Scell ​​through Scell ​​activation / deactivation signaling.

[0273] Considering coexistence with existing NR terminals, Release 19 is limited to on-demand SSB operation for connected mode terminals and SCells. However, in future releases or next-generation communication systems, on-demand SSB operation (for SSB transmission on PCell) considering inactive or idle mode terminals or initially connected terminals may be defined. In addition, carrier aggregation (CA) including the SCell can be applied to both intra-band CA and inter-band CA, and the SSB on the SCell transmitted through the on-demand SSB process can be utilized for at least functionality such as time / frequency synchronization, L1 / L3 measurement, and SCell activation.

[0274] On-demand SIB1 transmission

[0275] Objective 2 in Table E-1 above can discuss a method of reducing energy consumption by having the base station transmit SIB1 for a specific cell through the on-demand SIB1 process and not transmit SIB1 for the cell when there is no on-demand SIB1 process. In the existing NR system, SIB1 containing system information, random access information, etc. for initial access or idle mode terminals to access a cell must always be periodically provided, making it difficult to reduce energy consumption even when the base station has no data to receive or send. Considering this, the base station can reduce base station energy consumption by not performing SIB1 transmission until the on-demand SIB1 process is accompanied and then performing SIB1 transmission. The on-demand SIB1 process can trigger SIB1 transmission of the base station when the terminal transmits an uplink signal / channel (e.g., PRACH in the NR system). Specifically, the following scenarios can be considered, but may not be limited to the following scenarios.

[0276] 1) Scenario 1: As shown in FIG. 17a, a terminal that receives an SSB (and / or other downlink signal / channel) from a cell#1 and recognizes that SIB1 is not transmitted on the cell#1 can trigger SIB1 transmission by transmitting a signal requesting SIB1 (for convenience, the signal is referred to as a WUS (wake-up signal) in the present invention) based on information provided in the SSB (and / or other downlink signal / channel) and / or predetermined information. The base station that receives the WUS can transmit a specific DL signal / channel on cell#1 in response thereto, and can transmit SIB1 on cell#1 (or without transmitting the DL signal / channel).

[0277] 2) Scenario 2: As in Fig. 17b, a terminal may attempt to camp on cell#2 when it receives an SSB (and / or other downlink signal / channel such as SIB1) from a cell#1 and recognizes that SIB1 is not transmitted on the corresponding cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal (i.e., WUS) requesting SIB1 on cell#1 based on information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. The base station receiving the WUS may transmit a specific DL signal / channel (on cell#1 or cell#2) in response thereto, and may transmit SIB1 for cell#2 on cell#1 or cell#2 (or without transmitting the DL signal / channel).

[0278] 3) Scenario 3: As in Fig. 17c, a terminal may attempt to camp on cell#2 when it receives an SSB (and / or other downlink signal / channel such as SIB1) from a cell#1 and recognizes that SIB1 is not transmitted on the corresponding cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal (i.e., WUS) requesting SIB1 on cell#2 based on information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. The base station receiving the WUS may transmit a specific DL signal / channel (on cell#1 or cell#2) in response thereto, and may transmit SIB1 for cell#2 on cell#1 or cell#2 (or without transmitting the DL signal / channel).

[0279]

[0280] Specific embodiments of the present disclosure

[0281] The present disclosure relates to a technology for operating SSB (synchronization signal / physical broadcast channel block) and system information in an on-demand manner in a wireless communication system. Specifically, the present disclosure proposes a technology for providing SSB and / or system information based on a request in a cell or frequency band where transmission of SSB (e.g., synchronization signal, MIB) and / or system information (e.g., MIB, SIB) has been temporarily suspended for NES operation. Specifically, the present disclosure proposes on-demand signaling for requesting SSB and conditions for performing the on-demand signaling. Hereinafter, in the present disclosure, ' / ' means 'and', 'or', or 'and / or' depending on the context.

[0282]

[0283] The base station can operate technologies such as controlling the on / off of the UE for a certain period of time in the time axis for the purpose of NES, controlling the transmission / reception resources for UE-common or UE-specific signals / channels, changing the amount of frequency-axis resources, controlling the transmission power, or turning on / off the antenna port (AP), TRP, etc. in the spatial domain. In the present disclosure, the listed technologies are referred to as 'NES technologies' or 'NES_tech', and the state in which at least one of the NES_techs is applied is referred to as 'NES mode' or 'NES state'. The base station can inform the terminal of which NES_tech(s) is applied for each NES_tech or NES_tech group [Approach 1], or can preset the corresponding NES_tech or NES_tech group(s) for each code-point of a specific indicator [Approach 2]. Here, specific indicators may be indicated by DCI or MAC CE, etc., or may be set by higher layer signaling.

[0284] For Approach 1, if at least one NES_tech is applied to the terminal, the state can be defined as an NES mode or NES state, and further, can be treated as a different NES mode or different NES state depending on which NES_tech is applied. The NES mode or NES state can be used as a concept to indicate whether at least one NES technology is applied, or further to indicate which NES technology(s) are applied. If the NES mode or NES state further indicates which NES technology(s) are applied, different NES modes or different NES states can include different combinations of NES_tech. For Approach 2, for example, if a 1-bit indicator is used, '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, if '1' is indicated through the indicator, the state can be defined as an NES mode or NES state. As another example, when a 2-bit indicator is used, '00' can indicate that there is no corresponding NES_tech, '01' can indicate that at least one NES_tech_A is applied, '10' can indicate that at least one NES_tech_B is applied, and '11' can indicate that at least one NES_tech_C is applied. In this case, if a code-point other than '00' is indicated through the indicator, the state can be defined as an NES mode or NES state. Furthermore, the terminal can determine NES state #1 when '01' is identified, NES state #2 when '10' is identified, and NES state #3 when '11' is identified. Accordingly, whether it is an NES state and / or which NES state it is can be distinguished for each code-point.

[0285] For NES purposes, the base station can turn on / off certain spatial elements (e.g., APs, active transmit / receive chains, panels or TRPs) or adjust the power value for the downlink signal / channel. To dynamically apply various NES techniques in the spatial and power domains, the base station can associate CSI-RS resources or resource sets with different APs for a single CSI report setting (e.g., CSI-ReportConfig) or associate multiple power offsets (e.g., powerControlOffset parameter, which is a power offset value between PDSCH and CSI-RS, powerControlOffsetSS parameter, which is a power offset value between SSS and CSI-RS, etc.).

[0286] Specifically, at least one of the following CSI frameworks may be introduced:

[0287] - Framework #1: Multiple CSI-RS resource sets are linked for one CMR (channel measurement resource) or one IMR (interference measurement resource) in CSI-ReportConfig. Here, the CMR can be set by the resourcesForChannelMeasurement parameter, and the IMR can be set by the csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference parameter. For example, for CMR, CSI-RS resource set #1 and CSI-RS resource set #2 are linked, and the CSI-RS resources belonging to CSI-RS resource set #1 can be configured with 16 APs (antenna ports, APs), and the CSI-RS resources belonging to CSI-RS resource set #2 can be configured with 8 APs.

[0288] - Framework #2: When a CSI-RS resource set linked to a CMR or an IMR in CSI-ReportConfig is configured, at least one CSI-RS resource(s) with different properties such as the number of APs and / or power offsets within the CSI-RS resource set are configured. For example, for a CSI-RS resource set #1 configured as CMR, CSI-RS resource #1 belonging to the CSI-RS resource set #1 may be configured with 16 APs, and CSI-RS resource #2 belonging to the same set may be configured with 8 APs. For example, for a CSI-RS resource set #1 configured as CMR, CSI-RS resource #1 belonging to the CSI-RS resource set #1 may be configured with the power offset #1 value, and CSI-RS resource #2 belonging to the same set may be configured with the power offset #2 value.

[0289] - Framework #3: When a CSI-RS resource set linked to a CMR or an IMR is configured in CSI-ReportConfig, some or all CSI-RS resource(s) within the set can be configured with multiple AP numbers and / or power offset values. For example, for a CSI-RS resource set #1 configured with a CMR, CSI-RS resource #1 belonging to the CSI-RS resource set #1 can be configured with up to 16 APs, and CSI reporting utilizing at least one AP among them can be configured. Alternatively, CSI-RS resource #2 belonging to the same CSI-RS resource set #1 can be configured with multiple power offset values, and CSI reporting utilizing all or part of the power offsets can be configured.

[0290] For the CSI frameworks described above, the CSI reporting method can be defined through at least one of the following options.

[0291] - Option #1: CSIs that consider multiple AP count values ​​and / or multiple power offset values ​​set in a single CSI report may all be included in a single CSI report. Alternatively, CSIs that consider multiple AP count values ​​and / or multiple power offset values ​​determined through the configuration / instruction of the base station may be included in a single CSI report. In this case, the AP count values ​​and / or power offset values ​​set / instructed through the base station may be some of the AP count values ​​and / or power offset values ​​set in the corresponding CSI report.

[0292] - Option #2: Even if multiple AP count values ​​and / or multiple power offset values ​​are set in one CSI report, CSI(s) considering a single AP count value and / or a single power offset value can be included in one CSI report through the base station's configuration / instruction.

[0293] - Option #3: Even if multiple AP count values ​​and / or multiple power offset values ​​are set in one CSI report, CSI(s) that consider some AP count values ​​and / or some power offset values ​​may be included in one CSI report through judgment / decision / selection of the terminal based on criteria set in advance by the base station or defined in advance.

[0294] Within a configuration for CSI reporting (e.g., CSI-ReportConfig), one or more L sub-configurations can be configured, and each sub-configuration can correspond to either a spatial domain adaptation pattern or a power domain adaptation pattern.

[0295] Here, the spatial domain adaptation pattern may correspond to a specific number of APs or an AP on / off pattern, or may correspond to a specific CSI-RS power value (e.g., the CSI-RS power value determined by the powerControlOffsetSS parameter, which is a power offset value between SSS and CSI-RS, because the turning off of some antenna elements corresponding to one AP may affect the CSI-RS power value). For example, when applying framework #2, the number of APs A1 or the power value P1 may be set for the CSI-RS index #n1 belonging to the resource set, and the number of APs A2 or the power value P2 may be set for the CSI-RS index #n2 belonging to the same resource set. In this case, the sub-configuration index #s1 is set to be linked with the CSI-RS index #n1, and the sub-configuration index #s2 is set to be linked with the CSI-RS index #n2, so that the spatial domain adaptation pattern can be set differently for each sub-configuration. When applying the Framework #3 method, when the number of A1 APs (or P1 / P2 power values) is set for the CSI-RS index #n1 belonging to the resource set, the number of A1 APs (or P1 power values ​​or delta values ​​from the P1 power values) is linked to the sub-configuration index #s1, and the number of A2 APs (or P2 power values ​​or delta values ​​from the P1 power values) that is less than the number of A1 APs that constitute the CSI-RS index #n1 is linked to the sub-configuration index #s2, so that the spatial domain adaptation pattern can be set differently for each sub-configuration.

[0296] In addition, the power domain adaptation pattern may mean that the power offset value (e.g., the power offset value determined by the powerControlOffset parameter, which is the power offset value between PDSCH and CSI-RS, the powerControlOffsetSS parameter, which is the power offset value between SSS and CSI-RS, etc.) is changed. For example, when applying framework #2, the P1 power value may be set for the CSI-RS index #n1 belonging to the resource set, and the P2 power value may be set for the CSI-RS index #n2 belonging to the same resource set. In this case, the sub-configuration index #s1 may be linked to the CSI-RS index #n1, and the sub-configuration index #s2 may be linked to the CSI-RS index #n2, so that the power domain adaptation pattern may be set differently for each sub-configuration.

[0297] In addition, when applying framework #3, the P1 power value and the P2 power value can be set for the CSI-RS index #n1 belonging to the resource set. In this case, the sub-configuration index #s1 is set to be linked to the P1 power value, and the sub-configuration index #s2 is set to be linked to the P2 power value or the delta value from the P1 power value, so that the power domain adaptation pattern can be set differently for each sub-configuration.

[0298] By utilizing one of the aforementioned options #1 / 2 / 3, the terminal may feed back to the base station a CSI report including CSI(s) corresponding to N sub-configurations, which are 1 to L, among L sub-configurations.

[0299]

[0300] According to the TS 38.214 standard document, at least one sub-configuration can be configured within a CSI reporting configuration, and within each sub-configuration, one or a combination of the following configurations can be configured:

[0301] - A list of IDs of one or more CSI-RS resource(s).

[0302] - Antenna port subset indication consisting of a bitmap

[0303] - Additional power offset delta from the EPRE offset between PDSCH and CSI-RS set within the CSI-RS resource configuration.

[0304] In the present disclosure, for convenience of description, a CSI reporting configuration including a sub-configuration in which an ID list of at least one CSI-RS resource(s) is set is referred to as Type 2 spatial domain (SD) adaptation, a CSI reporting configuration including a sub-configuration in which an antenna port subset indication configured as a bitmap is set is referred to as Type 1 spatial domain adaptation, and a CSI reporting configuration including a sub-configuration in which an additional power offset delta value is set is referred to as Power Domain (PD) adaptation. An ID list of at least one CSI-RS resource(s) and / or a power offset delta value may be set for sub-configuration(s) belonging to one CSI reporting configuration, which is referred to as Type 2 spatial domain+power domain adaptation. Additionally, an antenna port subset indication and / or a power offset delta value configured as a bitmap may be set for sub-configuration(s) belonging to one CSI reporting configuration, which is referred to as Type 1 spatial domain+power domain adaptation. For Type 1 spatial domain or power domain or Type 1 spatial domain+power domain adaptation, each CSI-RS resource can be associated with each of all sub-configurations configured within one CSI reporting configuration. For Type 2 spatial domain adaptation, each CSI-RS resource can be associated with only a single sub-configuration among multiple sub-configurations within one CSI reporting configuration. For Type 2 spatial domain+power domain adaptation, the list #1 of CSI-RS resource(s) configured in a sub-configuration within the same CSI reporting configuration and the list #2 of CSI-RS resource(s) configured in another sub-configuration may be the same or disjoint.

[0305] Meanwhile, if L sub-configurations are configured within a CSI reporting configuration, the UE can report CSIs corresponding to each of the L sub-configurations to the base station via a PUSCH / PUCCH. Among the L sub-configurations, only N (L or more and 1 or more) sub-configurations(es) can be activated or triggered via MAC-CE or DCI, in which case the UE can report CSIs corresponding to each of the N sub-configurations to the base station via a PUSCH / PUCCH. Specifically, for a CSI reporting configuration in which semi-persistent CSI reporting on PUCCH (SP CSI reporting on PUCCH) is configured, N sub-configurations(es) among the L sub-configurations configured via MAC-CE can be activated. Additionally, for a CSI reporting configuration in which SP CSI reporting on PUSCH or A(aperiodic)-CSI reporting is configured, N sub-configurations out of L sub-configurations configured via DCI may be triggered.

[0306]

[0307] From the perspective of a base station operating multiple frequency bands, if the number of terminals served is small or the traffic load is relatively low, periodically transmitting SSB and / or system information may result in unnecessary energy consumption. In the present disclosure, the frequency band may be replaced with a band, a carrier, a serving cell, or a bandwidth part (BWP).

[0308] For example, three frequency bands may be operated as shown in FIG. 18. FIG. 18 illustrates examples of frequency bands operated by a base station according to an embodiment of the present disclosure. Referring to FIG. 18, when a base station operates three frequency bands, the base station may periodically transmit SSB (e.g., legacy SSB) in some frequency bands (e.g., F1), transmit simplified or modified S-SSB (simplified-SSB) in the remaining frequency bands (e.g., F2), or not transmit SSB and S-SSB in other frequency bands (e.g., F3). That is, F2 and F3 may be understood as non-SSB frequency bands. Through this, the base station can save energy. A terminal operating in F2 or F3 can request SSB transmission from the base station in the corresponding frequency band. An SSB transmitted upon a request from a terminal may be referred to as an on-demand SSB, and the SSB may be a legacy SSB, or a simplified or modified S-SSB. Here, a cell that does not allow SSB transmission, such as F2 or F3, may be referred to as an SSB-less cell. From the terminal's perspective, an SSB-less cell may be any one of PCell, PSCell, or SCell.

[0309]

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

[0311] (Example #1-1) Method for transmitting a signal to request on-demand SSB

[0312] FIG. 19 illustrates an example of a procedure for requesting on-demand SSB in a wireless communication system according to one embodiment of the present disclosure. FIG. 19 illustrates a method performed by a terminal.

[0313] Referring to FIG. 19, in step S1901, the terminal receives configuration information related to on-demand SSB. The configuration information may include various parameters related to on-demand SSB. For example, the configuration information may include at least one of information related to a cell supporting on-demand SSB, information related to the structure of on-demand SSB, and information related to a request for on-demand SSB. Here, the configuration information may be received from the Pcell of the terminal. That is, the terminal may perform synchronization signal detection, random access procedure, connection establishment procedure, etc. for the Pcell, and receive configuration information related to on-demand SSB of the Pcell or another cell.

[0314] In step S1903, the terminal checks resources for requesting on-demand SSB. The terminal can check resources for requesting on-demand SSB based on configuration information related to on-demand SSB. That is, according to one embodiment, the configuration information is information related to the request for on-demand SSB and may include information related to resources (e.g., channels, etc.) for transmitting a signal for requesting on-demand SSB. Furthermore, the configuration information may include information related to at least one of a signaling method and a signal structure for requesting on-demand SSB. In other words, resources for transmitting a signal for requesting on-demand SSB are set by the configuration information and may be indicated by at least one of a time-frequency position, an index of a resource or channel, and an offset.

[0315] In step S1905, the terminal transmits a request signal for on-demand SSB. In other words, the terminal can request transmission of on-demand SSB by transmitting the request signal through the identified resource. In one embodiment, the terminal can generate and transmit the request signal based on at least one parameter set by the configuration information.

[0316] As described with reference to FIG. 19, a signal and / or channel for requesting on-demand SSB may be configured. At this time, various pre-defined uplink signals and / or channels may be used, or a unique uplink signal and / or channel may be used. According to various embodiments, the base station may configure the terminal to use which of the following uplink signals and / or channels to request on-demand SSB, and the terminal may request on-demand SSB through a specific uplink signal and / or channel based on the configuration from the base station. For convenience of explanation, the present disclosure refers to the uplink signal and / or channel transmitted by the terminal for requesting on-demand SSB as 'UL_SSB'.

[0317] (Example #1-1-1) PRACH: For requesting on-demand SSB, at least one RO (RACH occasion) may be separately configured. Alternatively, for requesting on-demand SSB, some PPRACH preamble index(es) within a specific RO may be configured for requesting on-demand SSB.

[0318] (Example #1-1-2) SR (scheduling request) PUCCH / PRACH: When transmitting an SR corresponding to an SSB-less cell (e.g., an SR transmitted on PUCCH or PRACH), the UE may always be regarded as requesting on-demand SSB. That is, transmission of an SR corresponding to an SSB-less cell may be interpreted as a request for on-demand SSB. Alternatively, SR resources for requesting on-demand SSB may be configured separately from SR resources that do not request on-demand SSB. Here, the SR resources may include separate time / frequency resources and / or sequence resources.

[0319] (Example #1-1-3) SRS: SRS resources for requesting on-demand SSB can be separately set. Here, the SRS resources can include separate time / frequency resources and / or sequence resources.

[0320] (Example #1-1-4) PUCCH: On-demand SSB request information can be transmitted periodically or aperiodically via a periodic or semi-persistent PUCCH. Here, the SSB request information includes information for notifying that the terminal requests transmission of on-demand SSB.

[0321] (Example #1-1-5) PUSCH: On-demand SSB request information can be transmitted periodically or aperiodically via PUSCH scheduled through UL grant or semi-static PUSCH (e.g., CG (configured grant) PUSCH or semi-static CSI-reporting on PUSCH, etc.).

[0322] (Example #1-1-6) Resources for UL_SSB may be set up on a cell without SSB. Alternatively, resources for UL_SSB may be set up on a cell other than the cell without SSB (e.g., PCell / PSCell / SCell / non-serving cell, etc.).

[0323] The above-described on-demand SSB request procedure based on uplink signals may be implemented in a limited manner for specific cells. In one embodiment, a terminal may transmit a request signal to request on-demand SSB for a Pcell.

[0324]

[0325] (Example #1-2) A method for requesting on-demand SSB by selectively using one resource among multiple resources.

[0326] One or more UL_SSB resources may be configured for a terminal. At this time, the terminal may select a UL_SSB resource according to the following conditions. Here, the UL_SSB resource(s) may be distinguished by time / frequency / sequence resources in the same uplink signal and / or channel, may be distinguished by the type of uplink signal and / or channel, or may be distinguished by the cell corresponding to the UL_SSB resource.

[0327] FIG. 20 illustrates an example of a procedure for transmitting a signal requesting on-demand SSB using at least one of a plurality of resources in a wireless communication system according to an embodiment of the present disclosure. FIG. 20 illustrates a method performed by a terminal.

[0328] Referring to FIG. 20, at step S2001, the terminal selects a resource for requesting on-demand SSB. That is, multiple resources for requesting on-demand SSB are set or allocated to the terminal, and the terminal selects one of the multiple resources. At this time, the terminal selects a resource based on the properties of the on-demand SSB it wishes to request. Here, the properties of the on-demand SSB may be related to at least one of the SSB itself, the resource carrying the SSB, the SSB transmission method, the cell providing the SSB, and the SSB structure.

[0329] In step S2003, the terminal transmits a request signal based on the selected resource. In other words, the terminal transmits a signal requesting on-demand SSB using resources corresponding to the attributes of the on-demand SSB to be requested. Here, the resource may include at least one of time resources, frequency resources, and sequence resources.

[0330] As described with reference to FIG. 20, a request signal for requesting on-demand SSB may be transmitted via one selected resource among multiple resources. Specific examples of the multiple resources are as follows.

[0331] (Example #1-2-1) Setting different UL_SSB resources by SSB index or index group: Here, the SSB index may be an index corresponding to an SSB to be transmitted on an SSB-less cell or an index corresponding to an SSB to be transmitted on a reference cell. In the present disclosure, a reference cell means a cell that is set to be interworked for at least one of timing sync and / or automatic gain control (AGC) setting of an SSB-less cell, uplink power control (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.), and may include cells other than an SSB-less cell (e.g., PCell / PSCell / SCell / non-serving cell, etc.). For example, different UL_SSB resources may be set for each SSB index or SSB index group corresponding to an SSB to be transmitted on a non-SSB cell or an SSB to be transmitted on a reference cell, and UL_SSB resource #1 corresponding to SSB index group #0 or SSB index #0 may be set in advance, and UL_SSB resource #2 corresponding to SSB index group #1 or SSB index #1 may be set in advance. If a terminal requests SSB index #1 or SSB index group #1, the terminal may transmit a signal using UL_SSB resource #2.

[0332] In one embodiment, in cases where it is unclear whether a terminal requests a specific SSB index or group of indexes, a separate UL_SSB resource may be set up to request all SSB indices. In this case, the terminal can request transmission for all SSB indices by performing uplink transmission through the UL_SSB resource.

[0333] (Example #1-2-2) Different UL_SSB resources are set according to the transmission duration, periodicity and / or SSB pattern of the SSB that the terminal requests: The transmission duration may mean the period from when on-demand SSB starts to when it ends on an SSB-free cell. For example, when on-demand SSB is transmitted P times with a period of X msec from slot #n on an SSB-free cell, and then SSB is no longer transmitted due to on-demand SSB being turned off from slot #n+k, the absolute time or P value corresponding to k slot(s) or k slot(s) may be defined as the period. The SSB period may mean the transmission time interval or the minimum transmission time interval between SSBs or SSB candidates having the same index. In addition, when multiple SSB patterns (e.g., legacy SSB and simplified SSB) are pre-configured / defined, different UL_SSB resources may be configured for each SSB pattern. For example, when UL_SSB resource #1 corresponding to SSB transmission section #1 and UL_SSB resource #2 corresponding to SSB transmission section #2 are separately configured, the UE may select UL_SSB resource #2 according to the required SSB transmission section and perform uplink transmission using the selected UL_SSB resource #2. Accordingly, the UE may assume that on-demand SSB may be transmitted during SSB transmission section #2.

[0334] (Example #1-2-3) When there is more than one reference cell corresponding to a SSB-less cell, setting different or identical UL_SSB resources for each reference cell: When multiple reference cells corresponding to a specific SSB-less cell are set, different UL_SSB resources may be set for each reference cell. For example, when a PCell and another SCell are set as reference cells for a SSB-less cell, UL_SSB resource #1 corresponding to the PCell and UL_SSB resource #2 corresponding to the other SCell may be set, and when a terminal requests an SSB linked with the PCell on the SSB-less cell, uplink transmission may be performed through UL_SSB resource #1.

[0335] (Example #1-2-4) When UL_SSB resources corresponding to one or more SSB-less cells are set for a common cell, different UL-SSB resources are set for each SSB-less cell or group of SSB-less cells: For example, when a terminal uses three serving cells through CA (carrier aggregation), both SCell#0 and SCell#1 operate as SSB-less cells, and both UL_SSB resources for requesting SSB on SCell#0 and UL_SSB resources for requesting SSB on SCell#1 can be set on the PCell.

[0336] At this time, Opt-1) UL_SSB resource for requesting SSB on SCell#0 and UL_SSB resource for requesting SSB on SCell#1 may be set identically, or Opt-2) UL_SSB resource for requesting SSB on SCell#0 and UL_SSB resource for requesting SSB on SCell#1 may be set differently. In case of Opt-1, the UE can request transmission of on-demand SSB for both SCells by performing uplink transmission through the common UL_SSB resource. In case of Opt-2, the UE can request transmission of on-demand SSB for a specific SCell by performing uplink transmission on one of the different UL_SSB resources.

[0337] (Example #1-2-5) Different UL_SSB resources are set depending on whether the SSB requested by the UE is a non-cell defining-SSB (NCD-SSB) or a cell defining-SSB (CD-SSB): NCD-SSB refers to an SSB that does not provide CORESET index 0 and type0-PDCCH CSS set information through PBCH information, and CD-SSB refers to an SSB that provides CORESET index 0 and type0-PDCCH CSS set information through PBCH information. According to one embodiment, UL_SSB resource #1 corresponding to NCD-SSB and UL_SSB resource #2 corresponding to CD-SSB may be set separately, and if the UE performs uplink transmission through UL_SSB resource #1, the UE may expect that NCD-SSB can be transmitted in the corresponding SSB-less cell. On the other hand, if the terminal performs uplink transmission via UL_SSB resource #2, the terminal can expect that CD-SSB can be transmitted in the corresponding SSB-less cell.

[0338]

[0339] [Example #2] Conditions for triggering an on-demand SSB request from a terminal

[0340] FIG. 21 illustrates an example of a procedure for requesting on-demand SSB according to conditions in a wireless communication system according to one embodiment of the present disclosure. FIG. 21 illustrates a method performed by a terminal.

[0341] Referring to FIG. 21, at step S2101, the terminal determines that the conditions for requesting on-demand SSB are satisfied. According to various embodiments, the conditions for requesting on-demand SSB may be predefined or set by the base station.

[0342] In step S2103, the terminal transmits a request signal for on-demand SSB. In other words, based on determining that a condition is satisfied, the terminal may request transmission of on-demand SSB by transmitting a request signal. In one embodiment, the terminal may transmit the request signal through a resource determined based on the condition for which satisfaction has been confirmed. The condition may be defined based on at least one of the timing or channel quality of a signal transmitted in a non-SSB cell.

[0343] As described with reference to FIG. 21, a terminal may request on-demand SSB using UL_SSB resources when certain conditions are met. According to various embodiments, a terminal may request on-demand SSB transmission if one or more of the following conditions are met. Various embodiments of the conditions for requesting on-demand SSB are described below.

[0344] (Example #2-1) When uplink data to be transmitted or downlink data to be received by the terminal occurs through a non-SSB cell: When transmitting SR as uplink data is generated, the terminal may perform an on-demand SSB request simultaneously with the SR resource as in [Example #1] described above. Alternatively, the terminal may request an on-demand SSB using a separate UL_SSB resource after transmitting the SR.

[0345] (Example #2-2) When it is determined that the reception timing or downlink reception synchronization (DL RX synchronization) is out of sync by a certain threshold (e.g. X ns or Y time samples) during downlink reception through a SSB-less cell, or when the transmission and reception success probability for initial transmission or retransmission is below a certain threshold: Here, the value of the threshold used for judgment may be defined in advance in the specification or may be set by the base station.

[0346] (Example #2-3) When the sensitivity of a signal received through a non-SSB cell and / or a reference cell, etc. satisfies a specific condition: The signal received through a non-SSB cell and / or a reference cell, etc. may include an SSB index and / or CSI-RS resource transmitted on the reference cell, or may include a CSI-RS transmitted on the non-SSB cell. The signal used to measure the sensitivity (hereinafter referred to as the “measurement signal”) may be defined in advance or set by the base station.

[0347] According to one embodiment, the measurement signal may include a signal set / indicated as a reference signal of a downlink / uplink signal and / or QCL / TCI / spatial relation information of a channel received or transmitted on a SSB-less cell. Here, the sensitivity of the signal may be understood as a result value of an L1 and / or L3 measurement corresponding to the signal (e.g., beam management-related measurements such as L1-RSRP, L1-SINR, and / or RRM measurements such as RSRP, RSRQ, RSSI, etc.). When the reception sensitivity decreases below / below a certain threshold (hereinafter, 'Event 1'), the range of change in the reception sensitivity is above / exceeds a certain threshold (hereinafter, 'Event 2'), or when such events (e.g., Event 1 and / or Event 2) occur more than a certain threshold, it may be determined that a certain condition is satisfied. Here, the threshold may be defined in advance or may be set by the base station.

[0348] Additionally, when counting the number of times an event has occurred, the terminal can count how many times the event has occurred within a given sliding time window or time window. Here, the value of the sliding time window or time window can be defined in advance or set by the base station.

[0349] At this time, if an event occurs again within a certain period (duration) from the time of event occurrence, the terminal can increase the count value. Conversely, if an event occurs again after a certain period has elapsed, the terminal can reset the count value. Here, the period value can be predefined or set by the base station.

[0350] Depending on the information that the terminal satisfies which triggering condition to request on-demand SSB, the behavior of the base station may vary. Considering this, the UL_SSB resource may be set differently, as in [Example #1] described above, depending on the triggering condition. For example, when downlink reception is performed through a non-SSB cell, UL_SSB resource #1 corresponding to a condition (hereinafter referred to as 'Condition #1') in which it is determined that the reception timing or downlink reception synchronization is deviated by a certain threshold (e.g., X ns or Y time samples) or more may be set, and UL_SSB resource #2 corresponding to a condition (hereinafter referred to as 'Condition #2') in which the reception sensitivity of a specific SSB index received on the reference cell is below a certain threshold may be set. When on-demand SSB is requested due to Condition #2, the terminal may attempt uplink transmission through UL_SSB resource #2.

[0351]

[0352] FIG. 22 illustrates an example of a procedure for requesting SSB transmission for an SSB-less cell according to one embodiment of the present disclosure. FIG. 22 illustrates signal exchange between a terminal (2210) and a base station (2220).

[0353] Referring to FIG. 22, in step S2201, the base station (2220) can configure an SSB-less cell and configure an on-demand SSB signal for requesting SSB on the cell as in the aforementioned [Example #1]. In step S2203, the terminal (2210) determines whether the triggering condition proposed in the aforementioned [Example #2] is satisfied. If the condition is satisfied, in step S2205, the terminal (2210) can select and transmit one of the signalings for requesting the configured on-demand SSB. After receiving the on-demand SSB signaling, in step S2207, the base station (2220) can transmit the corresponding SSB.

[0354]

[0355] When a base station operates on multiple frequency bands, it may periodically transmit SSB and / or system information on a specific frequency band for the purpose of NES, and may not periodically transmit the corresponding signal and / or channel on the remaining frequency bands. To support such operation of the base station and stable communication of the terminal on the corresponding frequency band, the present disclosure proposes an on-demand SSB operation procedure, specifically, signaling and triggering conditions for requesting on-demand SSB.

[0356] In the various embodiments described above, an on-demand SSB may be transmitted in an SSB-less cell at the request of a terminal or at the judgment of a base station. In this case, even a cell supporting on-demand SSB may transmit an always-on SSB (hereinafter referred to as a "default SSB") that is different from the on-demand SSB. In this case, the base station may transmit the default SSB in the cell and additionally transmit the on-demand SSB at the request of the terminal or at the judgment of the base station. In other words, an SSB-less cell refers to a cell from the perspective of on-demand SSB, and if there is a state in which an on-demand SSB is not transmitted at a specific point in time even when the default SSB is transmitted, the cell may be referred to as an SSB-less cell.

[0357] Accordingly, the embodiments applied to the aforementioned non-SSB cell can be similarly applied to a cell that transmits a default SSB and supports on-demand SSB. In this case, in the various embodiments described above, the reference cell and the non-SSB cell can be understood as a single cell that supports on-demand SSB, and the signal of the reference cell can be replaced with the default SSB of the cell that supports on-demand SSB.

[0358]

[0359] The proposed methods described above can be implemented independently, but they can also be implemented as a combination (or merge) of some of the proposed methods. Rules can be defined so that the base station notifies the terminal of the applicability of the proposed methods (or information about the rules of the proposed methods) through a predefined signal (e.g., a physical layer signal or a higher layer signal).

[0360] The present disclosure may be embodied in other specific forms without departing from the technical ideas and essential features described herein. Therefore, the above detailed description should not be construed as limiting in all respects but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are intended to be included within the scope of the present disclosure. Furthermore, claims that are not explicitly cited in the claims may be combined to form an embodiment or incorporated into a new claim through a post-filing amendment.

[0361] Embodiments of the present disclosure can be applied to various wireless access systems. Examples of various wireless access systems include the 3rd Generation Partnership Project (3GPP) or 3GPP2 systems.

[0362] The embodiments of the present disclosure can be applied not only to the various wireless access systems described above, but also to all technical fields that utilize these various wireless access systems. Furthermore, the proposed method can also be applied to mmWave and THz communication systems utilizing ultra-high frequency bands.

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

Claims

1. In the method, A step of receiving configuration information related to a downlink signal; A step of checking a resource for requesting the downlink signal based on the above setting information; and A step of transmitting a request signal for the downlink signal using the above resource, The above configuration information includes information related to at least one of a signaling method for requesting the downlink signal, a resource for transmitting the request signal, or a structure of the request signal. A method wherein the above downlink signal includes an on-demand SSB (synchronization signal / physical broadcast channel block).

2. In claim 1, A method in which the above resource comprises one of a random access channel occasion (RO) set for a request of the on-demand SSB, an uplink channel for a scheduling request (SR), a sounding reference signal (SRS), a physical uplink control channel (PUCCH), or a physical uplink shared channel (PUSCH).

3. In claim 1, A method wherein the above resources include resources on a cell transmitting the on-demand SSB.

4. In claim 1, The steps to verify the above resources are: A step of selecting one of a plurality of resources set by the above setting information, The above multiple resources are distinguished by at least one of time resources, frequency resources, or sequence resources.

5. In claim 4, A method in which one of the above multiple resources is selected based on the properties of the on-demand SSB to be requested.

6. In claim 4, A method in which the plurality of resources include one of: a plurality of different resources according to an SSB index or an SSB index group; a plurality of different resources according to an SSB transmission duration; a plurality of different resources according to an SSB transmission periodicity; a plurality of different resources according to an SSB pattern; a plurality of different resources according to a ref-cell; a plurality of resources corresponding to cells supporting a plurality of on-demand SSBs; or a plurality of different resources according to whether a non-cell defining-SSB (NCD-SSB) is present.

7. In claim 1, A method further comprising the step of determining satisfaction of a triggering condition for a request for the above on-demand SSB.

8. In claim 7, The triggering condition is a method including at least one of: a reception timing that is deviated by a threshold or more when receiving downlink through a cell supporting the on-demand SSB; a downlink reception synchronization (DL RX synchronization) that is deviated by a threshold or more; a transmission and reception success probability for initial transmission or retransmission that is lower than a threshold; a sensitivity of a signal received through the cell supporting the on-demand SSB that satisfies a set condition; or a sensitivity of a signal received through a reference cell that satisfies a set condition.

9. In claim 7, A method in which satisfaction of the above triggering condition is determined based on whether the set event is detected more than the threshold.

10. In claim 7, A method in which the above request signal is transmitted through a resource corresponding to the above triggering condition.

11. In the method, A step of transmitting configuration information related to a downlink signal; A step of receiving a request signal for the downlink signal using a resource identified based on the above setting information; and A step of transmitting the downlink signal in response to the request signal is included, The above configuration information includes information related to at least one of a signaling method for requesting the downlink signal, a resource for transmitting the request signal, or a structure of the request signal. A method wherein the above downlink signal includes an on-demand SSB (synchronization signal / physical broadcast channel block).

12. In claim 11, A method in which the above resource comprises one of a random access channel occasion (RO) set for a request of the on-demand SSB, an uplink channel for a scheduling request (SR), a sounding reference signal (SRS), a physical uplink control channel (PUCCH), or a physical uplink shared channel (PUSCH).

13. In claim 11, A method wherein the above resources include resources on a cell transmitting the on-demand SSB.

14. In claim 11, The above resource includes one of a plurality of resources set by the above setting information, The above multiple resources are distinguished by at least one of time resources, frequency resources, or sequence resources.

15. In claim 14, A method in which one of the above multiple resources is selected based on the properties of the on-demand SSB to be requested.

16. In claim 14, A method in which the plurality of resources include one of: a plurality of different resources according to an SSB index or an SSB index group; a plurality of different resources according to an SSB transmission duration; a plurality of different resources according to an SSB transmission periodicity; a plurality of different resources according to an SSB pattern; a plurality of different resources according to a ref-cell; a plurality of resources corresponding to cells supporting a plurality of on-demand SSBs; or a plurality of different resources according to whether a non-cell defining-SSB (NCD-SSB) is present.

17. In claim 11, A method in which the above request signal is received in response to satisfaction of a triggering condition for a request of the on-demand SSB.

18. In claim 17, The triggering condition is a method including at least one of: a reception timing that is deviated by a threshold or more when receiving downlink through a cell supporting the on-demand SSB; a downlink reception synchronization (DL RX synchronization) that is deviated by a threshold or more; a transmission and reception success probability for initial transmission or retransmission that is lower than a threshold; a sensitivity of a signal received through the cell supporting the on-demand SSB that satisfies a set condition; or a sensitivity of a signal received through a reference cell that satisfies a set condition.

19. In claim 17, A method in which satisfaction of the above triggering condition is determined based on whether the set event is detected more than the threshold.

20. In claim 17, A method in which the above request signal is received through a resource corresponding to the above triggering condition.

21. In the device, Transmitter and receiver; and A processor connected to the above transmitter and receiver is included, The above processor, Receive configuration information related to on-demand SSB (synchronization signal / physical broadcast channel block), Based on the above setting information, check the resources for the request of the on-demand SSB, configured to transmit a request signal for the on-demand SSB using the above resources, A device wherein the above configuration information includes information related to at least one of a signaling method for requesting the on-demand SSB, a resource for transmitting the request signal, or a structure of the request signal.

22. In the device, Transmitter and receiver; and A processor connected to the above transmitter and receiver is included, The above processor, Transmits configuration information related to on-demand SSB (synchronization signal / physical broadcast channel block), Receive a request signal for the on-demand SSB using a resource identified based on the above setting information, configured to transmit the on-demand SSB in response to the request signal; A device wherein the above configuration information includes information related to at least one of a signaling method for requesting the on-demand SSB, a resource for transmitting the request signal, or a structure of the request signal.

23. At the terminal, At least one processor; At least one memory connected to the at least one processor and storing instructions that cause the terminal to perform operations when executed by the at least one processor, The above actions are, A step of receiving configuration information related to an on-demand SSB (synchronization signal / physical broadcast channel block); A step of checking resources for a request of the on-demand SSB based on the above setting information; and A step of transmitting a request signal for the on-demand SSB using the above resources, A terminal including information related to at least one of a signaling method for requesting the on-demand SSB, a resource for transmitting the request signal, or a structure of the request signal.

24. In a non-transitory computer-readable medium storing at least one program instruction, wherein said at least one program instruction, when executed by at least one processor, causes the terminal to perform operations; The above actions are, A step of receiving configuration information related to an on-demand SSB (synchronization signal / physical broadcast channel block); A step of checking resources for a request of the on-demand SSB based on the above setting information; and A step of transmitting a request signal for the on-demand SSB using the above resources, A computer-readable medium including information related to at least one of a signaling method for requesting the on-demand SSB, a resource for transmitting the request signal, or a structure of the request signal.

Images