Method and apparatus for transmitting or receiving various types of synchronization signal blocks in wireless communication system

Abstract

A method and an apparatus for transmitting or receiving various types of synchronization signal blocks in a wireless communication system are disclosed. The method according to one embodiment of the present disclosure may comprise steps in which a terminal: receives, from a network, information related to a second synchronization signal block; and receives, from the network, the second synchronization signal block on a second occasion and / or a first synchronization signal block on a first occasion on the basis of the information related to the second synchronization signal block. On the basis that the second occasion and the first occasion overlap, the first synchronization signal block can be transmitted on the overlapping occasion.

Description

Method and device for transmitting or receiving various types of synchronization signal blocks in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting or receiving various types of synchronization signal blocks in a wireless communication system.

[0002] The fifth generation (5G) wireless communication system, the successor to 4G LTE (long-term evolution), is a new, clean-slate mobile communication system characterized by high performance, low latency, and high availability. 5G NR (New Radio) can utilize all available spectrum resources, from low-frequency bands below 1 GHz, to intermediate-frequency bands between 1 GHz and 10 GHz, and to high-frequency (or millimeter wave) bands above 24 GHz. 6G wireless communication systems are being developed based on the underlying technologies of 5G wireless communication.

[0003] The 6G wireless communication system is being developed with the goals of (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free 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. Considering the requirements of the 6G system, such as a peak data rate of 1 Tbps per device, an end-to-end latency of 1 ms, a maximum spectrum efficiency of 100 bps / Hz, support for mobility of 1000 km / h, satellite integration, artificial intelligence (AI), autonomous vehicles, extended reality (XR), and haptic communication, various technologies are being researched.

[0004] The technical problem of the present disclosure is to provide a method and device for transmitting or receiving various types of synchronization signal blocks in a wireless communication system.

[0005] An additional technical problem of the present disclosure is to provide a method and device for managing or expecting simultaneous transmission of a type-1 synchronization signal block and a type-2 synchronization signal block in a wireless communication system.

[0006] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0007] A method according to one aspect of the present disclosure may include: receiving, by a terminal, information related to a second synchronization signal block from a network; and receiving, by the terminal, from the network, at least one of the second synchronization signal block on a second occasion or the first synchronization signal block on a first opportunity, based on the information related to the second synchronization signal block. Based on the overlap between the second opportunity and the first opportunity, the first synchronization signal block may be transmitted on the overlapped opportunity.

[0008] A method according to an additional aspect of the present disclosure may include: transmitting, by a network node, information related to a second synchronization signal block to a terminal; and transmitting, by the network node, at least one of the second synchronization signal block on a second occasion or the first synchronization signal block on a first opportunity to the terminal based on the information related to the second synchronization signal block. Based on the overlap between the second opportunity and the first opportunity, the first synchronization signal block may be transmitted on the overlapped opportunity.

[0009] A method according to an additional aspect of the present disclosure may include: receiving, by a terminal, information related to a second synchronization signal block from a network; and receiving, by the terminal, from the network, at least one of the second synchronization signal block on a second occasion or the first synchronization signal block on a first opportunity within a specific bandwidth portion (BWP) based on the information related to the second synchronization signal block. Based on whether the first synchronization signal block corresponds to a cell-defining (CD) synchronization signal block or is located on a synchronization raster, a frequency domain resource of the second opportunity may be different from a frequency domain resource of the first opportunity.

[0010] A method according to an additional aspect of the present disclosure may include: transmitting, by a network node, information related to a second synchronization signal block to a terminal; and transmitting, by the network node, one or more of the second synchronization signal block on a second occasion or the first synchronization signal block on a first opportunity within a specific bandwidth portion (BWP) based on the information related to the second synchronization signal block. Frequency domain resources of the second opportunity may be different from frequency domain resources of the first opportunity based on whether the first synchronization signal block corresponds to a cell-defining (CD) synchronization signal block or is located on a synchronization raster.

[0011] According to the present disclosure, a method and device for transmitting or receiving various types of synchronization signal blocks in a wireless communication system can be provided.

[0012] According to the present disclosure, a method and device for managing or expecting simultaneous transmission of a type-1 synchronization signal block and a type-2 synchronization signal block in a wireless communication system can be provided.

[0013] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0014] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

[0015] Figure 1 illustrates a flexible network topology to which some examples of the present disclosure may be applied.

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

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

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

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

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

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

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

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

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

[0025] FIG. 11 exemplarily illustrates a beam management procedure to which some examples of the present disclosure may be applied.

[0026] Figures 12 and 13 illustrate examples of NTN scenarios to which some examples of the present disclosure may be applied.

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

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

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

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

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

[0032] FIG. 19 illustrates examples of on-demand SIB1 operation to which some examples of the present disclosure may be applied.

[0033] FIG. 20 is a drawing for explaining an example of a method performed by a terminal according to the present disclosure.

[0034] FIG. 21 is a drawing illustrating an example of a method performed by a base station according to the present disclosure.

[0035] FIG. 22 is a diagram showing an example of transmission of various types of SSBs according to the present disclosure.

[0036] FIG. 23 is a diagram showing an example of transmission of various types of SSBs according to the present disclosure.

[0037] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

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

[0039] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0040] In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish 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 stated otherwise. Accordingly, within the scope of this disclosure, a first component in one embodiment 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.

[0041] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise.

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

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

[0044] 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.”

[0045] 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.”

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

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

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

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

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

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

[0052] In the present disclosure, "setting or defining" may be interpreted as being set to a device through predefined signaling (e.g., SIB (system information block), MAC, RRC) from a base station or network. In the present disclosure, "setting or defining" may be interpreted as being set to a device through separate signaling or being defined in advance without separate signaling.

[0053] In the present disclosure, transmitting or receiving a channel means transmitting or receiving information or a signal through the channel. For example, transmitting a control channel means transmitting control information or a signal through the control channel. Similarly, transmitting a data channel means transmitting data information or a signal through the data channel.

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

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

[0056] Network structure

[0057] Figure 1 illustrates a flexible network topology to which some examples of the present disclosure may be applied.

[0058] 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 integrated access backhaul (IAB) nodes, relays, and radio frequency (RF) repeaters, as illustrated 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, and in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that simply performs the functions of signal amplification and forwarding, or in the case of a network-controlled repeater, it may not only amplify and forward signals but also adjust its transmission and reception settings based on information provided by the network. For example, NTN nodes could be satellites or aircraft that provide NTN coverage that terrestrial networks struggle to provide. Beyond these examples, various intermediate points can be introduced to improve the network topology.

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

[0060] 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. For example, 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.

[0061] 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. 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), where 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.

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

[0063] In the present disclosure, there may be zero or more intermediate points between the base station and the terminal. If an intermediate point exists, it may correspond to an IAB node / relay / RF repeater / NTN node, or a node supporting other functions. The intermediate point may be a node with a fixed location or a node with an unfixed location.

[0064] Systems applicable to this disclosure

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

[0066] The communication system (100) applied 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).

[0067] 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 another IoT device (e.g., a sensor) or another wireless device (110a to 110f).

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

[0069] Device applicable to the present disclosure

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

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

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

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

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

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

[0076] 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. Additionally, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document via 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 user data, control information, wireless signals / channels, etc. processed by at least one processor (202) from a baseband signal to an RF band signal. For this purpose, at least one transceiver (206) may include an (analog) oscillator and / or filter.

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

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

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

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

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

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

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

[0084] 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. 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 backhaul communications, and a wired transceiver may not be included.

[0085] Communication procedures

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

[0087] FIG. 4 illustrates operations of a first node (110) (e.g., a terminal) and a second node (120) (e.g., a base station) transmitting and / or receiving data and operations performed prior thereto.

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

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

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

[0091] In step S107, the first node (110) and the second node (120) can perform signaling of control information. For example, the control information can 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 transmission channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) can perform at least one of signaling for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.

[0092] In step S109, the first node (110) and the second node (120) can transmit and / or receive data. For example, the terminal (110) and the base station (120) can process, transmit, and / or receive data based on signaling of control information. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on information bits. For example, when receiving data, the terminal (110) or the base station (120) 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.

[0093] 6G system core technologies

[0094] As core implementation technologies of the 6G system, technologies such as artificial intelligence (AI), THz (terahertz) communication, optical wireless technology, free space optics (FSO) backhaul network, massive MIMO (multiple input multiple output) 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.

[0095] artificial intelligence

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

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

[0098] Below, to explain AI (or AI / ML (machine learning)) in more detail, the terms can be defined as follows.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0113] An actor function (40) is a function that receives an output (16) from a model inference function (30) and triggers or performs a corresponding task / action. The actor function (40) can trigger tasks / actions for other entities (e.g., one or more terminals, one or more RAN nodes, one or more network nodes, etc.) or for itself.

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

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

[0116] - Training data: refers to a data set for learning a model.

[0117] - Validation data: This refers to a dataset used to validate a model that has already completed training. Validation data can typically be used to prevent overfitting of the training data set. It can also be used to select the best model among the various models learned during the training process. Therefore, validation can be considered a type of learning.

[0118] - Test data: This refers to the data set for final evaluation. This data is unrelated to learning.

[0119] For example, the training and validation data can be divided into an 8:2 or 7:3 ratio within the entire data set. Alternatively, the training data:validation data:test data can be divided into a 6:2:2 ratio within the entire data set.

[0120] The level of cooperation can be defined as follows depending on whether the base station and the terminal have capabilities for AI / ML functions, and variations due to combination of multiple levels or separation of any one level are also possible.

[0121] Category 0a: This category corresponds to a no-collaboration framework. In this case, AI / ML algorithms are purely implementation-based and may not require any changes to the wireless interface.

[0122] Category 0b: Frameworks that involve a wireless interface modified to fit efficient implementation-based AI / ML algorithms, but without collaboration.

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

[0124] Category 2: This applies to cases where joint ML tasks can be performed between terminals and base stations. This level requires exchange of AI / ML model commands or network nodes.

[0125] The functions exemplified in FIG. 5 above may be implemented in a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.), a network node, an OAM (operation administration maintenance) of a network operator, or a terminal.

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

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

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

[0129] For example, the AI ​​model training function may be performed by a network node (e.g., a core network node, an OAM of a network operator, etc.), and the AI ​​model inference function may be performed by a RAN node (e.g., a base station, a TRP, a CU of a base station, etc.).

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

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

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

[0133] For convenience of explanation, we assume that the AI ​​model is deployed / updated only to RAN node 1.

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

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

[0136] Step 6: If applicable, RAN node 1 may send model performance feedback to the network nodes.

[0137] Step 7: RAN node 1, RAN node 2, and the terminal (or 'RAN node 1 and the terminal', or 'RAN node 1 and RAN node 2') may perform actions based on the output data. For example, in the case of a load balancing operation, the terminal may move from RAN node 1 to RAN node 2.

[0138] Step 8: RAN node 1 and RAN node 2 can transmit feedback information to the network nodes.

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

[0140] For example, both AI model training functions and AI model inference functions can be performed by RAN nodes (e.g., base stations, TRPs, CUs of base stations, etc.).

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

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

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

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

[0145] Step 5: RAN node 1, RAN node 2, and the terminal (or 'RAN node 1 and the terminal', or 'RAN node 1 and RAN node 2') may perform actions based on the output data. For example, in the case of a load balancing operation, the terminal may move from RAN node 1 to RAN node 2.

[0146] Step 6: RAN node 2 may transmit feedback information to RAN node 1.

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

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

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

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

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

[0152] Step 4: Input data (e.g., inference data) for AI model inference can be received from the terminal and RAN node (and / or from another terminal).

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

[0154] Step 6: If applicable, the terminal may send model performance feedback to the RAN node.

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

[0156] Step 8: The terminal may transmit feedback information to the RAN node.

[0157] THz communication (terahertz communication)

[0158] Data transmission 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 (the sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase 6G cellular capacity. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band 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.

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

[0160] Key characteristics of THz communications include (i) the widely available bandwidth to support very high data rates, and (ii) the high path loss at high frequencies (which necessitates highly directional antennas). The narrow beamwidths generated by highly directional antennas reduce 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.

[0161] Transmitting system information (e.g., MIB) in a cell in the THz frequency band can be inefficient because the beam width in high-frequency bands narrows, requiring more beam sweeps to cover the entire cell area. This method is particularly inefficient when there are only a few users within the cell.

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

[0163] The example of Fig. 10 is applicable not only to THz communication environments but also to 6G communication environments where THz communication is not applicable. Furthermore, the procedure illustrated in Fig. 10 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 Fig. 10.

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

[0165] At step S1030, the first node (110) (e.g., terminal) can acquire synchronization for cell #1. Synchronization can be acquired by detecting a synchronization signal. Typically, synchronization is acquired before receiving system information, but since the 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, the terminal can acquire synchronization based on the system information. Alternatively, synchronization acquisition can be performed before step S1010.

[0166] At step S1050, the first node (110) may transmit a signal for accessing cell #1. For example, the signal may include a random access preamble. The structure of this signal and the resources (e.g., channels) for transmitting the signal may be identified through system information. Thereafter, at step S1070, the first node (110) and the second node (120) may perform an access procedure for cell #1 and communicate.

[0167] The procedure described with reference to FIG. 10 may be performed when the first node (110) initially connects to cell #1 of the second node (120). Alternatively, a similar procedure may be performed when the first node (110) hands over to cell #1 of the second node (120). 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 second node (120).

[0168] Communications in the THz band are expected to experience extremely severe path loss, and to overcome this, terminals and base stations may be required to use very 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 movement or movement of the terminals, frequent re-alignment is required, which can lead to link instability.

[0169] FIG. 11 exemplarily illustrates a beam management procedure to which some examples of the present disclosure may be applied.

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

[0171] Here, beam may be interpreted as other terms having equivalent technical meanings that can distinguish beams, such as 'spatial domain filter', 'spatial domain transmit filter', 'spatial domain receive filter', reference signal (RS) resource that distinguishes beams, SSB index, etc.

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

[0173] In step S1130, the second node (120) (e.g., base station) 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 also be transmitted in a multi-beam transmission method that forms a plurality of beams simultaneously to reduce 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).

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

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

[0176] non-terrestrial networks (NTN)

[0177] Figures 12 and 13 illustrate examples of NTN scenarios to which some examples of the present disclosure may be applied.

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

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

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

[0181] Referring to Figure 13, a satellite (or UAS platform) can establish a service link with a terminal. A satellite (or UAS platform) connected to a terminal 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 regenerated payload, the satellite can be connected to a data network through another satellite and the gateway. If an ISL does not exist between the satellite and another satellite, a feeder link between the satellite and the gateway may be required.

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

[0183] For example, a transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may remain unchanged.

[0184] 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 mounting all or part of a base station function on a satellite (or UAS platform).

[0185] Integrated Sensing and Communication (ISAC)

[0186] Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (or range) of an object, and thus obtain 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, such as 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.

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

[0188] Specifically, Fig. 14(a) shows an example of a monostatic sensing operation using a sensing receiver and a sensing transmitter located in the same location. Fig. 14(b) shows an example of a bistatic sensing operation using a sensing receiver and a sensing transmitter located in separate locations. A sensing signal transmitted from a sensing transmitter is reflected / scattered by a sensing object, and the sensing receiver can receive the signal, and extract / obtain sensing data based on the received signal. A sensing result can be generated / determined through appropriate processing of the sensing data. The sensing result can be provided to a trusted third-party entity / service outside the 3GPP system through an entity / service within the 3GPP system.

[0189] Network Energy Saving (NES)

[0190] 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 providers. In particular, the introduction of 5G communications will require higher transmission rates, necessitating base stations to be equipped with more antennas and provide services over wider bandwidths and frequency bands. Consequently, recent studies have shown that base station energy costs have reached as high as 20% of total OPEX. For example, various technologies for reducing energy consumption in 5G wireless communication systems are being discussed under the term "network energy savings" (NES).

[0191] Depending on the application of NES technology, the base station can perform operations such as controlling on / off for a certain time duration in the time domain, controlling transmission / reception resources for terminal-common or terminal-specific signals / channels, changing the amount of frequency domain resources, controlling transmission power, or turning on / off an antenna port, transmission-reception point (TRP), etc. in the spatial domain.

[0192] For example, a base station may identify the NES solution(s) to be applied, perform signaling to the NES, and perform actions on the NES.

[0193] NES solution(s) may be related to control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement, and reporting. The NES solution(s) to be applied may be adaptively selected or predefined based on current conditions (e.g., cell load level, characteristics of connected terminals, etc.).

[0194] A base station that has identified 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 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.

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

[0196] Examples of NES solutions that can be implemented using these procedures include:

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

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

[0199] SSB-less cells: If SSB or SSB-based RRM (radio resource management) measurement timing configuration (SMTC) configuration is not provided for a specific cell (e.g., secondary cell (SCell) or primary cell (PCell)), the UE may obtain timing reference and automatic gain control (AGC) source from another serving cell. In frequency range 1 (FR1) or FR2, the base station may configure intra-band carrier aggregation (CA) or inter-band CA including cells without SSB transmission, in which case SSB / SIB transmission may be triggered by a wake up signal (WUS) of the UE. Accordingly, since the period of common channels / signals such as SSB is increased, the base station may stay in sleep state for a longer time.

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

[0201] Parameters such as active duration and cycle may be configured for cell DTX / DRX. Active duration is the period during which the UE receives a PDCCH or SPS opportunity and waits to transmit SR or CG, and cycle may specify the periodic repetition of the active duration and inactive duration. When both cell DTX and cell DRX are configured, parameters such as active duration and cycle may be common. If the base station recognizes an emergency call or a public safety-related service (e.g., multimedia priority service (MPS) or mission critical service (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 may be required between the active period of the connected mode DRX of the UE and the active period 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.

[0202] Conditional handover (CHO): A CHO procedure performed in a manner in which the execution of a handover is determined by the UE may be used while NES technology is applied (e.g., when the cell activates or deactivates cell DTX / DRX). In this case, the UE may use an NES-specific CHO event to initiate CHO to a candidate cell, and reception of a DCI activating the CHO condition(s) set by the NES event indication may be applied as an additional triggering condition for this.

[0203] Spatial and Power Domain Adaptation: To support the base station for transceiver muting and / or transmit power adaptation, the UE may be configured to report multiple CSI quantities 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.

[0204] Cell DTX / DRX

[0205] To enable base stations to operate in sleep mode for relatively long periods of time without frequent wake-ups, base station DTX / DRX has been introduced for NES purposes. The base station can reduce energy consumption by utilizing DTX transmission under low system load conditions by configuring cell DTX and setting the on-duration of terminals' C-DRX within the active period of the cell DTX.

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

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

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

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

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

[0211] Thereafter, the base station can transmit control information related to cell DTX / DRX to the terminal. The control information related to cell DTX / DRX can include DCI having a designated format (e.g., DCI format 2_9). If an operation for a serving cell according to at least one of a cell DTX operation and a cell DRX operation is configured by configuration information (e.g., cellDTXDRX-Config included in servingcell-config), the terminal can check a set of search spaces (e.g., a Type3-PDCCH CSS set) for monitoring a PDCCH conveying control information of a designated format during an active time through a higher layer parameter (e.g., SearchSpace included in PDCCH-Config), and can obtain a location of information about the serving cell within the control information through a higher layer parameter (e.g., positionInDCI-cellDTRX included in ServingCell-config). Then, the terminal can obtain control information based on the identified set of search spaces and the location.

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

[0213] After that, the terminal and the base station can perform communication based on the cell DTX / DRX. Specifically, the base station can turn on / off the transmission and reception of signals according to the settings related to the cell DTX / DRX, so that the terminal can selectively monitor the signal from the base station. During the DTX-OFF duration, the base station can enter a sleep mode to reduce energy consumption. For example, the base station DTX cycle can be aligned with the cycle of the terminal DRX. The base station DTX-ON duration can completely cover the DRX-ON duration of the terminal. Furthermore, the base station can align the transmission on Xn (base station-to-base station interface) / NG (interface between 5G RAN and 5G core network) and the transmission on Uu (interface between terminal and network) for NES purposes. The DTX / DRX mechanism triggers switching of reference signal resource sets, and the base station can perform a dormancy-like behavior of rarely or not transmitting SSB, SIB, and CSI-RS to reduce energy consumption. The terminal can rarely or not receive downlink signals / channels depending on the configuration of the base station. Once the base station DTX / DRX operation is triggered, the terminal can discontinuously receive the corresponding CSI-RS, SSB, or PDCCH during the DTX / DRX OFF duration.

[0214] SSB-less cells

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

[0216] In the example of Figure 16, it is assumed that the SSB-less cell is an SCell in the CA, but the SSB-less cell may also be a PCell in the CA.

[0217] A second node (120) (e.g., a base station) can transmit configuration information for an SCell to a first node (110) (e.g., a terminal). For example, the base station can transmit 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 (e.g., sCellToAddModList) including information for adding an SCell, 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. Accordingly, the terminal can determine the configuration for the CA operation and perform communication using the PCell and SCell of the base station.

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

[0219] Conditional Handover (CHO)

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

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

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

[0223] A base station may transmit information for enabling an NES-specific CHO execution condition to a terminal. The information for enabling the NES-specific CHO execution condition may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information for enabling the NES-specific CHO execution condition may be referred to as an NES-mode indicator, and may be, for example, 1-bit information that indicates enabling the NES-specific CHO execution condition when a related upper layer parameter (e.g., nesEvent) is set and a serving cell of a related block in the DCI is a primary cell.

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

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

[0226] Channel State Information (CSI) Measurement and Reporting

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

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

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

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

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

[0232] For example, an IE for a CSI reporting sub-configuration may include a port-subset indicator parameter, an NZP CSI-RS resource list parameter, and a power offset parameter.

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

[0234] The NZP CSI-RS resource list parameter may indicate a list of NZP CSI-RS resources for a sub-configuration, which is a (sub)set of NZP CSI-RS resource(s) of a CSI-RS resource set for channel measurements associated with the sub-configuration of the CSI reporting configuration. The values ​​0, 1, 2, ... may mean the first, second, third, ... NZP CSI-RS resources of the CSI-RS resource set.

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

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

[0237] For example, with respect to the configuration of a report quantity, the terminal may determine the CSI-RS port index(es) for each CSI-RS resource based on information related to a port subset per sub-configuration (hereinafter referred to as a "port subset indicator"). The port subset indicator may include a bitmap for specifying some of the antenna ports for the corresponding CSI-RS resource. Accordingly, the terminal may identify at least one antenna port for the corresponding sub-configuration based on the positions of bits set to positive values ​​(e.g., 1) in the port subset indicator.

[0238] For example, with respect to the configuration of report items (report quantity), the terminal may determine the codebook type based on the presence or absence of sub-configurations. Specifically, if sub-configurations are configured for CSI reporting, the terminal may exclude the configuration of at least one codebook type. For example, if the terminal's capabilities support it, at least one codebook type may be configured.

[0239] For example, in relation to the configuration of the report quantity, a power offset value and an NZP CSI-RS resource set may be configured for each sub-configuration. For example, depending on whether a power offset value is configured for each sub-configuration and whether an NZP CSI-RS resource set is configured, the interpretation of the NZP CSI-RS resource set for each sub-configuration may vary.

[0240] When determining the channel quality indicator (CQI), a higher-layer parameter related to time restrictions for channel measurements (e.g., timeRestrictionForChannelMeasurements) may be configured. In this case, the terminal can derive a channel estimate for determining CSI based on the most recent CSI reference resource. For example, if cell DTX is activated for the base station, the cell DTX activation time, etc., may be considered to determine the CSI reference resource, etc.

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

[0242] When at least one of a CQI index, a precoding matrix index (PMI), and a rank indicator (RI) is set to be reported, in the CSI reference resource, the terminal may assume specific values ​​for the symbol positions and number occupied by control signaling, the number of PDSCH and demodulation reference signal (DMRS) symbols, the subcarrier spacing of the bandwidth part (BWP), the bandwidth for CQI reporting, the length and subcarrier spacing of the cyclic prefix (CP) of the reference resource, and the redundancy version (RV), for the purpose of deriving at least one of the CQI index, PMI, and RI. At this time, when sub-configurations are set for the CSI reporting, assumptions about the antenna port, EPRE (energy per resource element), etc. may be determined based on the sub-configurations.

[0243] Based on the aforementioned configuration, the base station can transmit at least one CSI-RS to the terminal. Based on the aforementioned configuration, the terminal can receive at least one CSI-RS and perform measurement on it. For example, the at least one CSI-RS can be transmitted via a CSI-RS resource or resource set configured by the configuration information.

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

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

[0246] A terminal that receives at least one CSI-RS can determine CSI. For example, the terminal can perform CSI calculations. The terminal can perform CSI calculations based on CSI processing criteria. The terminal can indicate the number of supported concurrent CSI calculations, for example, the number of CSI processing units (CPUs) that can be performed simultaneously, called NCPUs. The terminal can determine the number of CPUs for a given CSI report based on at least one of the NCPUs, the number of CPUs for each CSI report, the number of CPUs currently occupied, and the settings of the report items. For example, for configuration information (e.g., CSI-ReportConfig) related to CSI reporting that includes a report item parameter (e.g., reportQuantity) that is not set to 'none', the CPU(s) may be occupied for at least one orthogonal frequency division multiplexing (OFDM) symbol, wherein the number of at least one symbol may be determined based on CSI-RS resources or CSI-IM (interference measurement) resources associated with the sub-configurations.

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

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

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

[0250] When a CSI report on PUSCH includes two parts, the UE may omit some of the Part 2 CSI. The omission of Part 2 CSI is in priority order. When omitting Part 2 CSI information for a particular priority level, the UE shall exclude all information for that priority level, except when the corresponding CSI report includes at least one CSI sub-report including Part 2, which corresponds to a sub-configuration from a list of sub-configurations provided by a higher layer parameter (e.g., csi-ReportSubConfigList) included in information related to the CSI report (e.g., CSI-ReportConfig).

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

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

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

[0254] CSI is transmitted via PUCCH or PUSCH and can be expressed as a bit string of a fixed size. When CSI is transmitted via PUCCH, if a parameter (e.g., csi-ReportSubConfig) indicating sub-configuration-specific settings for CSI reports is configured, the mapping order of CSI fields for each CSI sub-report can be applied according to predefined rules.

[0255] When CSI is transmitted via PUSCH, if a parameter indicating sub-configuration-specific configuration for CSI reporting (e.g., csi-ReportSubConfig) is set, for each CSI sub-report, the mapping order of CSI fields can be applied according to a predefined rule.

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

[0257] Improved NES

[0258] For enhancement of NES technology, on-demand SSB, on-demand SIB1, and adaptation of common signal / channel transmissions are being discussed.

[0259] Below we describe on-demand SSB.

[0260] On-demand SSB is a NES scheme that transmits SSB when triggered in a specific cell and does not transmit SSB when not triggered. Existing NR systems require periodic, constant transmission of SSB for purposes such as time / frequency synchronization and RRM measurement, making it difficult to reduce energy consumption even when the base station has no data to receive or send. Considering this, energy consumption at the base station can be reduced by not performing SSB transmission at all and only performing SSB transmission when the on-demand SSB process is performed.

[0261] These on-demand SSB processes can be triggered by one or more of the following examples:

[0262] - The terminal requests SSB transmission from the base station by transmitting an uplink signal / channel (e.g., PRACH (physical random access channel), PUCCH, PUSCH, SRS (sounding reference signal) in the 5G NR system, and may be a signal / channel with a different name in the 6G system).

[0263] - The first base station (or TRP) requests SSB transmission from the second base station (or TRP) through an interface between base stations (e.g., Xn interface in 5G NR system, interface with different name in 6G system) or backhaul signaling, etc.

[0264] - Signaling whether SSB transmission of the corresponding SCell is possible through SCell activation / deactivation signaling.

[0265] Considering coexistence with existing NR terminals, on-demand SSB operation may be limited to connected mode terminals and SCells. In subsequent releases or next-generation communication systems, on-demand SSB operation considering inactive or idle mode terminals or initially connected terminals (e.g., on-demand SSB support on PCell) may be defined. In addition, carrier aggregation (CA) including SCells applicable to on-demand SSB may be applied to both intra-band CA and inter-band CA. SSB on SCells transmitted through on-demand SSB may be utilized at least for time / frequency synchronization, L1 / L3 measurements, SCell activation, etc.

[0266] Below, we describe On-Demand SIB1.

[0267] On-demand SIB1 corresponds to a NES scheme that transmits SIB1 when triggered on a specific cell and does not transmit SIB1 when not triggered. In the existing NR system, in order to support access to a cell by an initial access terminal or an idle mode terminal, it is required to periodically and always transmit SIB1 containing system information, random access information, etc., so it was difficult to reduce energy consumption even when the base station had no data to receive or send. By having the base station not perform SIB1 transmission and perform SIB1 transmission only when the on-demand SIB1 process is performed, the energy consumption of the base station can be reduced.

[0268] This on-demand SIB1 process may include the terminal transmitting an uplink signal / channel (e.g., PRACH in a 5G NR system, or a signal / channel with a different name in a 6G system) that triggers the base station's SIB1 transmission.

[0269] FIG. 19 illustrates examples of on-demand SIB1 operations to which some examples of the present disclosure may be applied. FIG. 19 merely illustrates examples, and on-demand SIB1 operations are not limited to the examples of FIG. 19.

[0270] In (a) of FIG. 19, the terminal may receive an SSB (and / or other downlink signal / channel) from the first cell (cell#1) and recognize that SIB1 is not transmitted on the corresponding cell#1. The terminal may trigger SIB1 transmission on cell#1 by transmitting a signal requesting SIB1 (e.g., a wake-up signal (WUS)) based on information provided in the SSB (and / or other downlink signal / channel) and / or predetermined information. For example, the base station that received the WUS may transmit a specific DL signal / channel (e.g., ACK) on cell#1 in response thereto and transmit SIB1 on cell#1. Alternatively, the base station may transmit SIB1 on cell#1 without transmitting a specific DL signal / channel (e.g., ACK).

[0271] In (b) of FIG. 19, the terminal may receive an SSB (and / or other downlink signal / channel such as SIB1) from the first cell (cell#1) and recognize that SIB1 is not transmitted from the second cell (cell#2). The terminal may attempt to camp on cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal (e.g., WUS) requesting SIB1 on cell#1 based on information provided in the SSB (and / or other downlink signal / channel such as SIB1) received from cell#1 and / or predetermined information. For example, the base station receiving the WUS may transmit a specific DL signal / channel (e.g., ACK) on cell#1 (or on cell#2) in response thereto, and transmit SIB1 for cell#2 on cell#1 (or on cell#2). Alternatively, the base station may transmit SIB1 for cell#2 on cell#1 (or on cell#2) without transmitting a specific DL signal / channel (e.g., ACK).

[0272] In (c) of FIG. 19, the terminal may receive an SSB (and / or other downlink signal / channel such as SIB1) from the first cell (cell#1) and recognize that SIB1 is not transmitted from the second cell (cell#2). The terminal may attempt to camp on cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal (e.g., WUS) requesting SIB1 on cell#2 based on information provided in the SSB (and / or other downlink signal / channel such as SIB1) received from cell#1 and / or predetermined information. For example, the base station receiving the WUS may transmit a specific DL signal / channel (e.g., ACK) on cell#2 (or on cell#1) in response thereto, and transmit SIB1 for cell#2 on cell#2 (or on cell#1). Alternatively, the base station may transmit SIB1 for cell#2 on cell#2 (or on cell#1) without transmitting a specific DL signal / channel (e.g., ACK).

[0273] Below we describe the adaptation of common signal / channel transmission.

[0274] Base stations can apply NES schemes that control the transmission of common signals / channels such as SSB, PRACH, and paging. Energy consumption can be reduced more significantly when SSB is not transmitted completely but is transmitted as needed. However, if SSB that supports time / frequency synchronization or RRM measurement is not transmitted completely, stable operation of terminals for the corresponding cell may not be guaranteed. Considering this, energy saving effects of the base station can be achieved by controlling / changing the SSB transmission pattern (e.g., transmission period, period by SSB candidate index(es), SSB candidate index(es) transmitted within one transmission period, transmission power, etc.) according to the situation.

[0275] In the case of PRACH resources, in the case of contention-based random access, since the base station does not know when the terminal will transmit the PRACH, it is required to always attempt reception within the PRACH resources set for the terminal, which may increase network energy consumption. Considering this, a method for controlling the amount of PRACH resources can be applied. For example, the period of the PRACH resources can be adjusted to be longer so that the base station attempts PRACH reception less frequently. For example, the number of PRACH resources can be adjusted to be smaller, such as a method of pre-configuring PRACH resource sets #1 and #2 and activating only one of the two sets or activating both sets. For example, the amount of RACH resources corresponding to each SSB index can be provided uniformly or non-uniformly.

[0276] In the case of paging, it is defined that paging frames (PF) and / or paging occasions (PO) are distributed on the time axis within a DRX cycle (or paging cycle), and the terminal attempts to receive paging at a specific PF / PO derived from a formula based on its own identification information. If the base station wants to transmit paging to multiple terminals simultaneously, it may need to frequently transmit paging messages according to various terminal identification information values. As a method for reducing the base station energy consumption due to this, a method such as arranging the PF and / or PO as close as possible on the time axis or arranging them on distinct frequency resources within the same time resource can be applied.

[0277] Types of synchronization signals

[0278] The examples of the present disclosure assume two types of synchronization signals and explain them. While the term "SSB" is used as an example of a synchronization signal in the following description, the scope of the present disclosure is not limited by that term, and other units with different names that include synchronization signals may replace "SSB."

[0279] For example, assuming on-demand SSB on a specific cell where transmission is initiated by a base station instruction or a terminal request, Type-1 SSB and Type-2 SSB can be distinguished as follows.

[0280] Type-1 SSB may refer to an SSB transmitted periodically on a first cell or on a second cell. If a period, etc. for the SSB is determined / defined / set, the SSB may be continuously transmitted according to the period. Continuous transmission may include transmission without distinction between on and off periods for SSB transmission, or without activation or deactivation. If Type-1 SSB refers to an SSB transmitted on a first cell, the first cell may correspond to a timing reference cell. If Type-1 SSB refers to an SSB transmitted on a second cell, the second cell may be in an intra-band CA or inter-band CA relationship with the first cell. For example, (especially in an inter-band CA environment) the second cell may be set as a timing reference cell for the first cell, or (in an intra-band CA environment) the second cell may be determined / defined as a timing reference cell for the first cell (e.g., a specific cell within the same timing advance group or a PCell or PSCell (primary secondary cell, i.e., a primary cell within a secondary cell group (SCG)). Also, only Type-2 SSBs may be transmitted on a specific cell without Type-1 SSBs.

[0281] Type-2 SSB may refer to an SSB in which transmission on a specific cell is activated through a configuration / instruction of the base station (via RRC / MAC-CE / DCI, etc.) or upon a request of the terminal. For an activated SSB, SSB deactivation may be explicitly configured / instructed via RRC / MAC-CE / DCI, etc. Alternatively, for an SSB in which the number of transmissions or transmission intervals are configured / instructed in the RRC / MAC-CE / DCI instructing SSB activation, the SSB may be deactivated when the corresponding number of transmissions or transmission intervals have expired. Alternatively, if there is a pre-configured / defined number of transmissions or transmission intervals, the SSB may be deactivated when the corresponding number of transmissions or transmission intervals have expired after SSB activation. Alternatively, (if a specific cell is an SCell) the SSB may be deactivated when activation for the specific cell is completed (or when CSI reporting for the specific cell is successfully completed). Alternatively, SSB may be deactivated when the specific cell is deactivated (if the specific cell is an SCell). Alternatively, SSB may be deactivated after a handover from the specific cell to another cell (if the specific cell is a PCell). Alternatively, SSB may be deactivated at the request of the UE.

[0282] As another example, it can be assumed that one or more SSB configurations are configured among different SSB configurations with at least different SSB cycle values, and an SSB corresponding to one of the SSB configurations is transmitted at the base station's instruction or the terminal's request. In this case, adaptation to the SSB cycle can be performed by varying the activated SSB configuration. In this case, Type-1 SSB and Type-2 SSB can be distinguished as follows.

[0283] Type-1 SSB may refer to a reference SSB setting among the configured SSB setting(s). For example, the reference SSB setting may correspond to the SSB setting having the largest SSB period value. For example, if an SSB setting corresponding to a Type-2 SSB is not activated, an SSB setting corresponding to a Type-1 SSB may be activated. Alternatively, if an SSB setting corresponding to a Type-2 SSB is activated, an SSB setting corresponding to a Type-1 SSB may be deactivated. Alternatively, if SSB opportunities specified based on a particular SSB setting (e.g., the reference SSB setting) among the configured SSB settings are a subset of SSB opportunities specified based on other SSB settings (e.g., "extended SSB opportunities"), the reference SSB opportunities may be defined as a Type-1 SSB (regardless of the actual activated SSB setting). In this case, Type-2 SSB can be defined as the remaining SSB opportunities (excluding the reference SSB opportunities) among the extended SSB opportunities (included in the actual activated SSB configuration).

[0284] For Type-2 SSB, in addition to the SSB configuration corresponding to Type-1 SSB, one or more SSB configurations for Type-2 SSB can be configured. When an SSB configuration corresponding to Type-2 SSB is activated, all SSBs belonging to the activated SSB configuration can be defined as Type-2 SSBs. Alternatively, if SSB opportunities configured based on a specific SSB configuration (e.g., a reference SSB configuration) among the configured SSB configurations (hereinafter, referred to as "reference SSB opportunities" for convenience) are a subset of SSB opportunities configured based on other configurations (hereinafter, referred to as "extended SSB opportunities" for convenience), the reference SSB opportunities can be defined as Type-1 SSBs (regardless of the actual activated SSB configuration), in which case Type-2 SSBs can be defined as the remaining SSB opportunities among the extended SSB opportunities (in the actual activated configuration) excluding the reference SSB opportunities. One or more SSB configurations may be activated by a configuration / instruction (via RRC / MAC-CE / DCI) of the base station or by a request of the terminal. For an activated SSB configuration, SSB deactivation may be explicitly configured / instructed via RRC / MAC-CE / DCI, etc. Alternatively, for an SSB activated by configuring / instructing the number of transmissions or transmission intervals in the RRC / MAC-CE / DCI instructing the activation of the SSB configuration, when the corresponding number of transmissions or transmission intervals expire, the SSB may be deactivated. Alternatively, if there is a pre-configured / defined number of transmissions or transmission intervals, the SSB may be deactivated when the corresponding number of transmissions or transmission intervals expire after the SSB is activated. Alternatively, (if a specific cell is an SCell) the SSB may be deactivated when activation for the specific cell is completed (or CSI reporting for the specific cell is successfully completed). Alternatively, (if a specific cell is an SCell) the SSB may be deactivated when the specific cell is deactivated.Alternatively, SSB may be deactivated after a handover from a specific cell to another cell (if the specific cell is a PCell). Alternatively, SSB may be deactivated at the request of the terminal.

[0285] As another example, it can be assumed that one or more SSB configurations are configured and an SSB corresponding to one of the SSB configuration(s) is transmitted at the instruction of the base station or upon the request of the terminal. In this case, there is an SSB (e.g., Type-1 SSB) that continues to be transmitted periodically regardless of the activation / deactivation of the corresponding SSB configuration(s), and an SSB configuration to be transmitted in addition to this SSB can be activated / deactivated. At least the SSB period value or SSB time pattern can be different between different SSB configurations. In this case, adaptation to the SSB period can be performed by varying the activated SSB configuration. In this case, Type-1 SSB and Type-2 SSB can be distinguished as follows.

[0286] Type-1 SSB may mean an SSB corresponding to the default SSB setting, and continuous periodic transmission may be guaranteed for Type-1 SSB regardless of the activation / deactivation of the SSB setting(s) corresponding to Type-2 SSB.

[0287] One or more SSB configurations for Type-2 SSB can be configured. One of the one or more SSB configurations can be activated by a configuration / instruction from a base station (via RRC / MAC-CE / DCI) or a request from a terminal. For an activated SSB configuration, SSB deactivation can be explicitly configured / instructed via RRC / MAC-CE / DCI, etc. Alternatively, for an SSB activated by configuring / instructing the number of transmissions or transmission intervals in the RRC / MAC-CE / DCI indicating the activation of the SSB configuration, when the number of transmissions or transmission intervals has expired, the SSB can be deactivated. Alternatively, if there is a pre-configured / defined number of transmissions or transmission intervals, the SSB can be deactivated when the number of transmissions or transmission intervals has expired after the SSB is activated. Alternatively, the SSB can be deactivated when activation for the specific cell is completed (or when CSI reporting for the specific cell is successfully completed) (if the specific cell is an SCell). Alternatively, SSB may be deactivated when the specific cell is deactivated (if the specific cell is an SCell). Alternatively, SSB may be deactivated after a handover from the specific cell to another cell (if the specific cell is a PCell). Alternatively, SSB may be deactivated at the request of the UE.

[0288] In the various examples described above, Type-1 SSB may correspond to an SSB that can assume continuous periodic transmission, and Type-2 SSB may correspond to an SSB that cannot assume continuous periodic transmission. In some of the examples described below, the always-on SSB may correspond to or be replaced by the Type-1 SSB described above, and the on-demand SSB may correspond to or be replaced by the Type-2 SSB described above.

[0289] Transmission and reception of various types of synchronization signal blocks

[0290] If the NES cell transmitting the Type-1 SSB (or Legacy SSB or Always-On (AO) SSB) is a candidate SCell that is not activated for the UE or a neighboring cell of the UE's serving cell, the Type-2 SSB (or On-Demand (OD) SSB) may not need to be transmitted in that NES cell. In contrast, the Type-1 SSB (or AO SSB) may correspond to an SSB that is transmitted periodically in all neighboring cells that may become SCells in the future, or in a serving cell that is activated, at the time of activation completion and continuously thereafter. That is, the Type-2 SSB (or OD SSB) may correspond to an SSB that is transmitted according to a specific cycle when triggered by the base station or the UE at a specific time, or when a specific scenario / event occurs at a specific time. Therefore, a case may arise where the Type-1 (or AO) SSB and the Type-2 (or OD) SSB collide.

[0291] The present disclosure describes various examples in which Type-1 (or AO) SSB and Type-2 (or OD) SSB are transmitted together, and in which different types of SSB are transmitted / received, with or without overlapping in frequency domain resources and / or time domain resources. These examples may correspond to a method for preventing or resolving the deterioration of energy saving performance of a NES base station and the deterioration of interference reduction performance for adjacent cells, assuming that in the specific scenario described above with respect to Type-2 (or OD) SSB transmission, both different types of SSB are transmitted.

[0292] In the present disclosure, it is generally assumed that the transmission of OD SSB and AO SSB is transmitted in the form of SSB burst. For example, one SSB burst transmission may correspond to a method of transmitting (e.g., sweeping) SSBs of one or more indices (e.g., SSB#0 to SSB#x) once within a predetermined time interval (e.g., 5 ms, which is half of a 10 ms frame). Different SSB indices may correspond to different beam directions, and the same SSB index may correspond to the same beam direction (or be quasi-co-located (QCL)). That is, an SSB burst may correspond to a set of one or more SSB beams within a predetermined time interval (e.g., 5 ms), which may be referred to as an SSB group in the examples below. For example, in the sub-6 GHz band, up to 8 beams can be included in one SSB burst, and for frequency range 2 (FR2) or millimeter wave (mmwave), up to 64 beams can be included in one SSB burst. Which beam / SSB among the beam IDs or SSB indices within one SSB burst / group is transmitted can be set / indicated in bitmap form by information about the SSB time domain position (e.g., SSB PositionInBurst parameter) signaled via SIB or RRC (re)configuration. In addition, the 5 ms period during which all SSBs / beams within one SSB burst are transmitted once within the cell (i.e., swept) can correspond to the first 5 ms or the last 5 ms of a 10 ms period. The terminal can blindly detect whether an SSB burst is within the first 5 ms or the last 5 ms of a 10 ms frame (i.e., the half-frame index) without any instruction from the base station.

[0293] In this disclosure, it can be assumed that when transmission of an OD SSB is triggered in an SCell added / activated mainly through carrier aggregation (CA), there may be a conflict between the resources for transmitting an AO SSB that was already being transmitted in the SCell and the resources for transmitting an OD SSB. Typically, a cell may transmit SSBs from both the SCell and the PCell depending on the UE's situation, and a difference in transmission timing (e.g., an offset) may be provided between the two SSBs. The SSB cycle of a typical cell may be fixed once set or may not change significantly. In the case of an NES cell, the cycle of an SSB that is always transmitted (e.g., an AO SSB) may be set relatively long to save energy. In the case of an SCell that always transmits SSBs at a constant cycle, transmission of an SSB with a relatively short cycle may be required during the measurement or activation process in an NES situation. In this assumption, an SSB with a long cycle that is always transmitted may correspond to an AO SSB, and an SSB whose transmission is triggered for a specific purpose may correspond to an OD SSB.

[0294] In the case of OD SSB, the network can trigger it for the terminal when necessary during a specific configuration or signaling process, or the terminal can trigger it for the base station when necessary. In addition, although one OD SSB may appear to be triggered from the perspective of one terminal, multiple OD SSBs may be triggered from the perspective of the network. Therefore, in the present disclosure, it can be assumed that an AO SSB and one or more OD SSBs are configured for a specific scenario (Sn, n=0, 1, 2, 3 in the table below). Alternatively, depending on the situation, the network may configure multiple AO SSBs that have different cycles or include cell-defining (CD) SSBs and non-cell-defining (NCD) SSBs. For example, a CD SSB may correspond to an SSB that is located on a synchronization raster and includes information such as cell identification information and SIB1, which can be utilized for cell detection and initial access. For example, NCD SSB is not located in the synchronization raster and does not contain cell identification information and SIB1, etc., so it may correspond to an SSB that is used for time synchronization, wireless link measurement, beam failure detection, etc., but cannot be utilized for cell detection and initial access.

[0295] The four scenarios in which NES cells operate as SCells are distinguished, as shown in the table below, and additional scenarios may be defined. The SSB cycle may be set differently for each scenario.

[0296] Scenario Index Description S0 State of neighboring cell before SCell is added by RRC S1 State in which SCell is added by RRC and deactivated S2 State in which SCell activation is in progress by SCell activation command through MAC CE S3 State in which SCell activation process is completed (i.e., activated)

[0297] FIG. 22 is a diagram showing an example of transmission of various types of SSBs according to the present disclosure.

[0298] As described above, SSB transmission of a NES cell can be distinguished into Type-1 SSB (or AO SSB) and Type-2 SSB (or OD SSB). In the S0 scenario, since the neighboring cell is not recognized as a serving cell by the UE, it can be assumed that there is no operation for OD SSB. After receiving a configuration from the network to add a specific cell as an SCell by RRC, the UE can recognize the specific cell as a serving cell. Therefore, when a cell is a neighboring cell before being recognized as a serving cell or is additionally configured as an SCell, only long-period Type-1 SSB (or AO SSB) can be seen by the UE from the cell.

[0299] If a cell is completely co-located or QCL'd with the PCell or another specific reference cell / BWP / carrier, there may be no SSB transmission at all in the S0 scenario. That is, no Type-1 SSB (or AO SSB) may be transmitted from the cell. In this case, depending on the terminal capabilities, the cell in S0 state may operate as an SSB-less cell.

[0300] Type-2 SSB (or OD SSB) can be triggered / transmitted in the remaining scenarios S1, S2, and S3, other than the S0 scenario. In this case, if there is a Type-1 SSB (or AO SSB) that is always transmitted according to a specific cycle in the S0 scenario and the S1, S2, and S3 scenarios, it is necessary to define the transmission method of different types of SSB.

[0301] In the example of FIG. 22, Type-2 SSB (or OD SSB) can be triggered by L3 (layer 3 or RRC) / L2 (layer 2 or MAC CE) / L1 (layer 1 or DCI) signaling. Type-2 SSB can be transmitted periodically after a predetermined time from the triggering signaling time. For example, the period of Type-2 SSB can be shorter than the period of Type-1 SSB. In this way, if Type-1 SSB and Type-2 SSB do not overlap, they can be transmitted together at different times. In NES cells, if SSB is transmitted too frequently in this way, problems may arise in terms of energy saving or reducing interference with neighboring cells. Therefore, a method capable of efficiently transmitting various types of SSB is required, and various examples of the present disclosure for this purpose will be described below.

[0302] In the present disclosure, triggering or instructions related to the transmission of Type-2 (or OD) SSB may be used with the same meaning. In the present disclosure, activation / triggering for the transmission of Type-2 (or OD) SSB corresponds to the description from the base station perspective, and this can be understood as activation / triggering for the reception of Type-2 (or OD) SSB from the terminal perspective.

[0303] FIG. 20 is a drawing for explaining an example of a method performed by a terminal according to the present disclosure.

[0304] In step S2010, information related to the second synchronization signal block can be received from the network.

[0305] In some examples, the information related to the second synchronization signal block may include one or more of configuration information for the second synchronization signal block and / or information indicating transmission of the second synchronization signal block.

[0306] In step S2020, the terminal may receive a second synchronization signal block on a second occasion and / or a first synchronization signal block on a first opportunity from the network based on information related to the second synchronization signal block.

[0307] In some examples, the second synchronization signal block may be the aforementioned Type-2 SSB or On-Demand (OD) SSB, and the first synchronization signal block may be the aforementioned Type-1 SSB, Legacy SSB, or Always-On (AO) SSB.

[0308] In some examples, the second opportunity may correspond to one of the candidate resources on which the second synchronization signal block is transmitted, and the first opportunity may correspond to one of the candidate resources on which the first synchronization signal block is transmitted.

[0309] In some examples, when the second opportunity and the first opportunity overlap, the first synchronization signal block may be transmitted / received on the overlapped opportunity. For example, only the first synchronization signal block may be transmitted / received without the second synchronization signal block (or the second synchronization signal block may be dropped) on the overlapped opportunity. For example, in the overlapped opportunity, the time domain resources of the second opportunity and the time domain resources of the first opportunity may be the same, and the frequency domain resources of the second opportunity and the frequency domain resources of the first opportunity may be the same.

[0310] In some examples, the second synchronization signal block may be included in a second group (or a second synchronization signal block burst) and the first synchronization signal block may be included in a first group (or a first synchronization signal block burst). For example, one or more indices for one or more synchronization signal blocks including the second synchronization signal block in the second group / burst may be a subset of one or more indices for one or more synchronization signal blocks including the first synchronization signal block in the first group / burst.

[0311] In some examples, in overlapping opportunities, the index of the second synchronization signal block and the index of the first synchronization signal block may be the same index. For example, synchronization signal blocks of the same index in the second group / burst and the first group / burst (i.e., the synchronization signal block corresponding to the second index in the second group / burst and the synchronization signal block corresponding to the second index in the first group / burst) may correspond to the same beam direction or be quasi-co-located (QCL).

[0312] In some examples, if the second opportunity and the first opportunity do not overlap, the second synchronization signal block may be transmitted / received on the second opportunity, and the first synchronization signal block may be transmitted / received on the first opportunity.

[0313] In some examples, the second synchronization signal block and the first synchronization signal block may be transmitted / received within the same BWP.

[0314] For example, if the first synchronization signal block corresponds to a cell-defining (CD) synchronization signal block or is located on a synchronization raster, the frequency domain resources of the second opportunity and the frequency domain resources of the first opportunity within the same BWP may be different.

[0315] For example, if the first synchronization signal block corresponds to a non-cell-defining (NCD) synchronization signal block or is not located on the synchronization raster, the frequency domain resources of the second opportunity and the frequency domain resources of the first opportunity within the same BWP may be the same. Furthermore, if the time domain resources of the second opportunity and the time domain resources of the first opportunity are also the same, the second opportunity and the first opportunity may overlap. In the overlapped opportunity, the first synchronization signal block (only) may be transmitted / received (without the second synchronization signal block, or the second synchronization signal block is dropped).

[0316] In some examples, the second synchronization signal block may correspond to an NCD synchronization signal block or may not be located on the synchronization raster.

[0317] The method described in the example of FIG. 20 may be performed by the wireless device (200) of FIG. 3 corresponding to the first node (110) of FIG. 2 described above. For example, one or more processors (202) of the wireless device (200) of FIG. 3 may be configured to receive information related to a second synchronization signal block from a network via one or more transceivers (206), and, based on the information related to the second synchronization signal block, receive a second synchronization signal block on a second opportunity and / or a first synchronization signal block on a first opportunity from the network via one or more transceivers (206). Furthermore, one or more memories (204) of the wireless device (200) may store instructions for performing the method described in the example of FIG. 20 or the examples described below when executed by one or more processors (202).

[0318] FIG. 21 is a drawing illustrating an example of a method performed by a base station according to the present disclosure.

[0319] In step S2110, the base station can transmit information related to the second synchronization signal block to the terminal.

[0320] In step S2120, the base station may transmit a second synchronization signal block on a second opportunity and / or a first synchronization signal block on a first opportunity to the terminal based on information related to the second synchronization signal block.

[0321] Specific features related to the second and first synchronization signal blocks, whether the second and first opportunities overlap, the index within the group of synchronization signal blocks, and the frequency positions of the second and first synchronization signal blocks (or the second and first opportunities) within one BWP are the same as those described with reference to the example of FIG. 20, and therefore, redundant descriptions are omitted.

[0322] The method described in the example of FIG. 21 may be performed by the wireless device (200) of FIG. 3 corresponding to the second node (120) of FIG. 2 described above. For example, one or more processors (202) of the wireless device (200) of FIG. 3 may be configured to transmit information related to a second synchronization signal block to a terminal via one or more transceivers (206), and, based on the information related to the second synchronization signal block, transmit a second synchronization signal block on a second opportunity and / or a second synchronization signal block on a second opportunity to the terminal via one or more transceivers (206). Furthermore, one or more memories (204) of the wireless device (200) may store commands for performing the method described in the example of FIG. 21 or the examples described below when executed by one or more processors (202).

[0323] Hereinafter, various examples of the present disclosure for transmitting or receiving various types of synchronization signal blocks (or SSBs) will be described. In the examples below, the terms always-on SSB (or AO SSB) and on-demand SSB (or OD SSB) are primarily used for description, but these correspond to representative examples of the aforementioned Type-1 SSB and Type-2 SSB, and the scope is not limited by the names of the terms.

[0324] In the following description, the dropping of an SSB may mean that the network or base station does not transmit the SSB, or the network or base station transmits the SSB but the terminal does not receive the SSB, does not perform measurement / reporting, etc. based on the SSB, or expects the network / base station not to transmit the SSB.

[0325] Example 1

[0326] This embodiment is about a method of dropping one for transmission of different types of SSB.

[0327] Even if the transmission times of AO SSB and OD SSB do not overlap, as in the example of Fig. 22, one of the two can be dropped and the other can be transmitted.

[0328] Example 1-1

[0329] Depending on the state of the cell (e.g., the setting / activation state of the cell corresponding to the aforementioned scenario index Sn (n=0, 1, 2, 3)), the OD SSB or the AO SSB can be dropped.

[0330] For example, AO SSB can be dropped at Sn, and OD SSB can be dropped at Sn+1. Alternatively, OD SSB can be dropped at Sn, and AO SSB can be dropped at Sn+1. Which type of SSB is dropped in which state / scenario can be preset by separate signaling. For example, information about which type of SSB is dropped in which state / scenario can be preset / indicated via L1 DCI, L2 MAC CE, and / or L3 RRC message. Alternatively, which type of SSB is dropped in which state / scenario can be preset without separate signaling.

[0331] Example 1-2

[0332] A specific point in time can be set / defined as the reference point when the state of the corresponding cell changes (e.g., the boundary between Sn and Sn+1) or when the OD SSB is triggered. After this specific point in time, a specific timer can be started / operated after the first SSB transmission. While the timer is running (i.e., before the timer expires or during a window corresponding to the timer length), the AO SSB or the OD SSB can be dropped.

[0333] For example, a specific timer may be triggered if the first SSB transmitted after the aforementioned specific time point is an AO SSB. Alternatively, a specific timer may be triggered if the first SSB transmitted after the aforementioned specific time point is an OD SSB. The type of the first SSB transmitted that corresponds to the condition for the specific timer to be triggered may be preset.

[0334] As another example, if multiple OD SSBs are transmittable, after the base station transmits a particular OD SSB, other OD SSBs may be dropped during a particular timer operation (or during a window of a particular length).

[0335] Example 1-3

[0336] Based on the AO SSB transmission point, OD SSB can be dropped within a time interval of a predetermined duration before and after the point.

[0337] For example, if the instance point in time at which the AO SSB is transmitted (starts) corresponds to a time position of 320 ms and the length of the given duration is 10 ms, the OD SSB may be dropped within the interval from the 310 ms point to the 330 ms point.

[0338] The length of these durations may be preset / indicated by separate signaling, or may be predefined without separate signaling.

[0339] Example 1-4

[0340] If a transmission of an AO SSB is performed after the first transmission of an OD SSB while a particular cell state is maintained (e.g., during a time interval where the scenario index does not change), then the OD SSB transmission after that AO SSB transmission may be dropped (during that scenario).

[0341] In a specific Sn scenario, if OD SSB is transmitted first and then AO SSB transmission is performed (according to the original period), there may be a situation where AO SSB is not transmitted several times (due to the difference in the period of OD SSB and AO SSB). In S1 or S2 scenario, the terminal may require more SSBs for measurement or time / frequency synchronization during the period where AO SSB transmission is not performed. Therefore, in order to solve the problem of only a few transmissions including OD SSB and AO SSB during the period corresponding to a specific scenario, if OD SSB is triggered and first OD SSB is transmitted and then AO SSB transmission is performed, the second and subsequent OD SSB transmissions may be dropped.

[0342] As an additional example, it can be set / defined how many AO SSB transmissions are transmitted after OD SSB triggering before the OD SSB is dropped. Here, the number of AO SSB transmissions before OD SSB drop can be preset.

[0343] As an additional example, if the operation of dropping all transmissions of OD SSBs after transmission of AO SSBs is applied to the case where transmission of AO SSBs is performed after transmission / reception of one OD SSB, then all subsequent OD SSBs can be dropped after transmission / reception of one OD SSB.

[0344] In the examples described above and below, if an AO SSB set as a CD SSB (or an AO SSB not set as an NCD SSB) is transmitted on a synchronization raster, the AO SSB may not be dropped. Alternatively, dropping according to the examples described above may be applied to an AO SSB set as an NCD SSB.

[0345] In the examples described above and below, in the examples where drops are applied to some of the AO SSB and one or more OD SSBs, the drop is described as being applied on a per-SSB burst basis (e.g., when one SSB burst includes multiple SSB indices that are swept in multiple beam directions, the drop is applied on a per-SSB ID / index or beam direction basis), but the drop may also be applied on a per-SSB ID / index or beam direction basis. The drop to which SSB ID / index or beam direction is applied can be set / controlled through L3 / L2 / L1 signaling.

[0346] Example 2

[0347] This embodiment relates to a method for transmitting SSB in a case where AO SSB and OD SSB overlap in the time domain.

[0348] In the examples of Embodiment 1, it is assumed that when AO SSB and OD SSB with different periods are transmitted together, the opportunity (or time-frequency resource) for transmitting the AO SSB and the opportunity (or time-frequency resource) for transmitting the OD SSB are set so as not to overlap in the time domain (example of FIG. 22). In Embodiment 2, it is assumed that when AO SSB and OD SSB with different periods are transmitted together, the opportunity of the AO SSB and the opportunity of the OD SSB are set so as to overlap to some extent in the time domain. For example, the period of the AO SSB and the period of the OD SSB may be a multiple of each other, and the transmission time of the AO SSB and the transmission time of the OD SSB may be set so as not to be misaligned (or to overlap) as in the example of FIG. 22.

[0349] FIG. 23 is a diagram showing an example of transmission of various types of SSBs according to the present disclosure.

[0350] FIG. 23(a) illustrates a case where OD SSB opportunities and AO SSB opportunities are transmitted at the same frequency domain resource locations, and their periods are in a multiple relationship, so that some of the opportunities have the same time domain resource locations. Accordingly, for example, some of the AO SSB opportunities located in the time domain at intervals of X periods (e.g., the second AO SSB opportunity and the third AO SSB opportunity) and some of the OD SSB opportunities located in the time domain at intervals of Y (= X / 4) periods (e.g., the first OD SSB opportunity and the fifth OD SSB opportunity) may overlap with each other. For example, a method may be applied in which only the period parameter is changed while keeping other parameters the same in the OD SSB configuration / signaling compared to the AO SSB configuration / signaling.

[0351] Figure 23(a) illustrates a case where OD SSB opportunities and AO SSB opportunities are transmitted at different frequency domain resource locations, and their periods are in a multiple relationship, so that the time domain resource locations of some of the opportunities(s) are the same.

[0352] In the example of Fig. 23, the fact that the OD SSB opportunities and the AO SSB opportunities are located in the same frequency domain resource can be expressed as the center frequency of the OD SSB and the center frequency of the AO SSB being the same within the same BWP. Alternatively, the fact that the OD SSB opportunities and the AO SSB opportunities are located in different frequency domain resources can be expressed as the center frequency of the OD SSB and the center frequency of the AO SSB being different within the same BWP.

[0353] Example 2-1

[0354] As in the example of Fig. 23(a), either the AO SSB or the OD SSB can be transmitted at an opportunity where the AO SSB and the OD SSB overlap in the time domain and frequency domain.

[0355] For example, in a cell where AO SSB is being transmitted periodically, it is allowed for AO SSB opportunities and OD SSB opportunities to overlap in the time and / or frequency domain, and if they overlap in the time and / or frequency domain, AO SSB can be transmitted in the overlapped opportunity. This is to take into account that other terminals within the cell (e.g., terminals for which OD SSB is not triggered) require AO SSB.

[0356] Alternatively, if the AO SSB opportunity and the OD SSB opportunity overlap in the time and frequency domain, the OD SSB may be transmitted in the overlapping opportunity. This is because the service for a specific terminal may be more important than that for another terminal during the activation process of the corresponding cell.

[0357] Whether AO SSB or OD SSB will be transmitted in an overlapping opportunity can also be configured via L3 / L2 / L1 signaling.

[0358] Example 2-2

[0359] As in the example of Fig. 23(b), when the AO SSB opportunity and the OD SSB opportunity do not overlap in the frequency domain, both the AO SSB and the OD SSB may be transmitted, or either the AO SSB or the OD SSB may be transmitted.

[0360] For example, if the center frequency locations of AO SSB opportunities and OD SSB opportunities are different within the same BWP, both AO SSBs and OD SSBs corresponding to the same time domain resource can be transmitted.

[0361] Alternatively, if the center frequency locations of AO SSB opportunities and OD SSB opportunities are different within the same BWP, the AO SSB may be transmitted among the AO SSB and OD SSB corresponding to the same time domain resource. This is to take into account that other terminals within the cell (e.g., terminals for which OD SSB is not triggered) require AO SSB.

[0362] Alternatively, if the center frequency locations of AO SSB opportunities and OD SSB opportunities are different within the same BWP, the OD SSB may be transmitted among the AO SSBs and OD SSBs corresponding to the same time domain resources. This is because services for certain terminals may be more important than those for other terminals during the activation process of the corresponding cell.

[0363] If the time domain resources of the AO SSB opportunity and the OD SSB opportunity are the same / overlapping but the frequency domain resources are different, whether both the AO SSB and the OD SSB are transmitted, the AO SSB is transmitted, or the OD SSB is transmitted can be configured through L3 / L2 / L1 signaling.

[0364] For terminals subject to bandwidth limitations (e.g., reduced capability terminals), OD SSB may always be transmitted.

[0365] Example 2-3

[0366] In an example where a drop is applied to some of the AO SSBs and one or more OD SSBs, the drop may be applied on a per-SSB burst basis (e.g., a whole number of SSB indices if one SSB burst includes multiple SSB indices that are swept in multiple beam directions), but the drop may also be applied on a per-SSB ID / index or beam direction basis.

[0367] For example, the drop determination may be applied only to the SSB index / ID or beam direction corresponding to the overlapping opportunity of AO SSB and OD SSB. In the above-described embodiments, if only one of the AO SSB or OD SSB is transmitted in an overlapping opportunity in the time and / or frequency domain, the other one may be dropped. In this case, the drop determination may be applied per SSB index / ID corresponding to the overlapping opportunity, not per SSB burst (or per set or group of SSB indices / IDs).

[0368] In the example of Fig. 23, the 1st, 2nd, and 3rd opportunities of type-1 (AO) SSB are illustrated and can be assumed to correspond to AO SSB indices #a1, #a2, and #a3, respectively. The 1st, 2nd, 3rd, 4th, and 5th opportunities of type-2 (OD) SSB are illustrated and can be assumed to correspond to OD SSB indices #o1, #o2, #o3, #o4, and #o5, respectively. In addition, the 2nd AO SSB opportunity and the 3rd AO SSB opportunity overlap with the 1st OD SSB opportunity and the 5th OD SSB opportunity at least in the time domain. If an AO SSB is dropped in an overlapping opportunity, the AO SSB index #a1 may be transmitted and the AO SSB indices #a2 and #a3 may be dropped. If OD SSB is dropped in an overlapping opportunity, OD SSB indices #o1 and #o5 are dropped, and OD SSB indices #o2, #o3, and #o4 can be transmitted.

[0369] Example 2-4

[0370] If the half-frame index of the AO SSB (indicating either the first half-frame or the second half-frame) and the half-frame index of the OD SSB are the same within the same 10ms frame, only one of the AO SSB or OD SSB may be transmitted in the SSB burst unit and the other may be dropped.

[0371] For example, it may be preset or predefined which type of SSB is transmitted (or dropped).

[0372] For example, in cases where both AO SSB and OD SSB can be transmitted within the same cell or within the same BWP, whether AO SSB or OD SSB drop is applied per SSB burst may be applied depending on whether the half-frame index is the same. Whether to apply it per cell or per BWP may be preset or predefined.

[0373] For example, if both AO SSB and OD SSB are transmittable within one BWP (or within one cell), then within a particular half-frame (5 ms period) that includes both AO SSB and OD SSB opportunities, all OD SSB burst (or AO SSB burst) transmissions within that half-frame may be dropped.

[0374] Example 2-5

[0375] Even if the half-frame indexes of the AO SSB (indicating either the first half-frame or the second half-frame) and the half-frame indexes of the OD SSB are different and do not overlap in the time domain within the same 10ms frame, only one of the AO SSB or the OD SSB may be transmitted and the other may be dropped in an SSB burst unit. That is, if both the half-frame indices of the AO SSB and the OD SSB are the same or different (or regardless of the half-frame indices) and are included in the same frame, either one of them may be dropped.

[0376] For example, it may be preset or predefined which type of SSB is transmitted (or dropped).

[0377] For example, if both AO SSB and OD SSB can be transmitted within the same cell or within the same BWP, whether AO SSB or OD SSB drop is applied per SSB burst within the same frame can be applied. Whether to apply it per cell or per BWP can be preset or predefined.

[0378] For example, if both AO SSB and OD SSB are transmittable within a single cell (or within a single BWP), then within a particular frame (10 ms period) that includes both AO SSB and OD SSB opportunities, all OD SSB burst (or AO SSB burst) transmissions within any one half-frame within that frame may be dropped.

[0379] Example 3

[0380] In this embodiment, examples are described in which the number of transmissions of OD SSB is based on the transmission cycle of AO SSB.

[0381] In general, an OD SSB may correspond to an SSB that is temporarily transmitted for measurement or synchronization with a serving cell (e.g., (SCell)) of a terminal in a specific situation. The transmission period of an AO SSB transmitted from an existing cell (or SCell) may be longer than the transmission period of an OD SSB. For example, due to the transmission characteristics of SSB, the transmission period of an AO SSB may correspond to a multiple of the transmission period of an OD SSB. In this case, it may be appropriate for an OD SSB to be transmitted only a certain number of times rather than permanently after being triggered. Taking this into consideration, the number of transmissions of an OD SSB may be set / defined based on the AO SSB period.

[0382] For example, it can be assumed that the transmission period of AO SSB is 160ms and the transmission period of OD SSB is 40ms. In this case, the number of transmissions of OD SSB can be set / defined as 4 times so as to be less than or equal to one cycle of AO SSB. Alternatively, the number of transmissions of OD SSB can be set / defined as a number corresponding to X (X=1, 2, 3, ...) cycles of AO SSB.

[0383] For example, the X value for deriving the number of transmissions of OD SSB, or the parameter directly indicating the number of transmissions of OD SSB, can be set / instructed to the terminal through L1 / L2 / L3 signaling.

[0384] Example 4

[0385] In this embodiment, examples are described for cases where the AO SSB and OD SSB are CD SSB or NCD SSB.

[0386] SSB can be distinguished into CD SSB and NCD SSB. CD SSB can be said to be an SSB in which all information required for SIB acquisition of the corresponding cell (e.g., configuration information for CORESET#0 and type0-PDCCH CSS (common search space) set for SIB1 acquisition) is provided to the UE through MIB (or PBCH payload within SSB). NCD SSB can be said to be an SSB in which only the information required for simultaneous channel reception or measurement such as SFN, PSS, or SSB is provided to the UE through MIB (or PBCH payload within SSB) without including the information required for SIB acquisition.

[0387] In this disclosure, we consider OD SSB transmission for various scenarios, and provide examples of cases where OD SSB is transmitted as CD SSB or as NCD SSB.

[0388] Additionally, NCD SSB can be distinguished into two types of NCD SSB.

[0389] Type-1 NCD SSB may be applied, for example, to cells that operate only as SCells. For example, Type-1 NCD SSB may correspond to an SSB that does not provide the necessary settings for UE SIB1 acquisition and / or an SSB that is not transmitted on a synchronization raster.

[0390] Type-2 NCD SSB may correspond to an NCD SSB defined from Release 17 onwards. For example, a Type-2 NCD SSB may have a longer period than a CD SSB and may correspond to an SSB used only for synchronization or measurement of a certain BWP.

[0391] Type-2 NCD-SSB can be established via a dedicated RRC message for NCD SSB establishment (e.g., NonCellDefiningSSB information element as shown in the table below).

[0392] NonCellDefiningSSB information element-- ASN1START-- TAG-NONCELLDEFININGSSB-STARTNonCellDefiningSSB-r17 ::= SEQUENCE {absoluteFrequencySSB-r17 ARFCN-ValueNR,ssb-Periodicity-r17 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1} OPTIONAL, -- Need Sssb-TimeOffset-r17 ENUMERATED { ms5, ms10, ms15, ms20, ms40, ms80, spare2, spare1} OPTIONAL, -- Need S...}-- TAG-NONCELLDEFININGSSB-STOP-- ASN1STOP

[0393] Type-1 NCD-SSB is set up similarly to the setup for a typical CD SSB, but with the k SSB For the parameter value called , it may correspond to NCD SSB when a specific value or a predefined specific range of values ​​is given. For example, if the terminal determines that there is no information about CORESET for Type0-PDCCH CSS set in the SSB detected, and k for FR1 SSB If the value is 24 or more and 29 or less, or k for FR2 SSB If the value is 12 or more and 13 or less, the corresponding SSB can be determined as an NCD SSB. Alternatively, if the terminal determines that there is no information about the CORESET for the Type0-PDCCH CSS set in the SSB detected, k for FR1 SSB The value of is 31, or k for FR2 SSB If the value is 15, the SSB can be determined as NCD SSB.

[0394] Below are various examples of whether AO SSB and OD SSB correspond to CD SSB or NCD SSB (Type-1 or Type-2).

[0395] Example 4-1

[0396] AO SSB can be primarily configured / defined as CD SSB. AO SSB corresponding to CD SSB may always contain CORESET-related information for receiving SIB (e.g. SIB1).

[0397] Alternatively, for AO SSB in NES cell, it may be set / defined as NCD SSB.

[0398] Assuming that the transmission period applicable to the AO SSB corresponding to the CD SSB is A, the transmission period applicable to the AO SSB corresponding to the NCD SSB can be set / defined as a scaled value such as A / N or A*N.

[0399] For example, if an AO SSB exists, it can be used as a CD SSB or as a NCD SSB. It can also be configured in the terminal whether the AO SSB is used as a CD SSB or as a NCD SSB.

[0400] For a single BWP, multiple NCD SSBs may be configured simultaneously. Alternatively, for a single cell, multiple NCD SSBs may be configured simultaneously. Alternatively, for a single BWP in a single cell, multiple NCD SSBs may be configured simultaneously.

[0401] Example 4-2

[0402] OD SSB can be used as NCD SSB. In case of OD SSB, configuration information for receiving SIB (e.g., SIB1) may not be provided, and it may not be used as CD SSB because it is transmitted only a certain number of times during a short duration and is used for synchronization or measurement.

[0403] For example, for a cell supporting OD SSB SCell operation, the OD SSB on that cell may not be located in the synchronization raster, and / or the OD SSB on that cell may correspond to an NCD SSB.

[0404] For example, the OD SSB can be set / defined as the aforementioned Type-1 NCD SSB.

[0405] Alternatively, the OD SSB may be configured / defined as the Type-2 NCD SSB described above. For example, the transmission period of the NCD SSB may be configured to be smaller than the transmission period of the CD SSB (exceptionally for NES cells), and a new parameter may be added for this (e.g., a new parameter may be added to the information element of Table 2). In addition, the value of the time offset for the OD SSB may always be set to 0. Accordingly, the AO SSB opportunity and the OD SSB opportunity may be identical (or overlap) at least in the time domain.

[0406] Additionally, according to the present disclosure, it may be permissible for a CD SSB and a NCD SSB to operate simultaneously within the same BWP. If an AO SSB corresponds to a CD SSB and an OD SSB corresponds to a NCD SSB, the AO SSB (CD SSB) and the OD SSB (NCD SSB) may be located together within a single BWP.

[0407] For example, in terms of frequency location (or center frequency) between an AO SSB and an OD SSB, if the AO SSB corresponds to a CD SSB on the synchronization raster, the frequency location of the OD SSB may be different from the frequency location of the AO SSB. For example, the OD SSB may not be located on the synchronization raster, or may correspond to a CD SSB. These AO SSB and OD SSB may be located within the same BWP. The terminal is not required to measure both the AO SSB and the OD SSB, and may measure / use only one of them.

[0408] Additionally or alternatively, a new RRC message for configuring a NES NCD SSB (or OD SSB) may be defined to configure / provide the UE with parameters that are distinct from the existing RRC message (e.g., the NonCellDefiningSSB information element in Table 2). For example, the new RRC message may include only a parameter for a period, so that a scaled period based on the period of the CD SSB (or AO SSB) is applied to the NCD SSB (or OD SSB). Additionally or alternatively, the values ​​of the parameters for the relative frequency position (e.g., frequency offset) and / or relative time position (e.g., time offset) with respect to the NCD SSB (or OD SSB) based on the frequency position and / or time position of the AO SSB configured / defined as the CD SSB may be restricted to correspond to 0, or the values ​​of the frequency offset and / or time offset may be defined / applied as 0 without a separate parameter.

[0409] Alternatively, an OD SSB corresponding to a NCD SSB can be set / defined if an AO SSB does not exist (in the corresponding BWP or in the corresponding cell). Alternatively, an OD SSB corresponding to a NCD SSB can be set / defined if an AO SSB exists (in the corresponding BWP or in the corresponding cell).

[0410] Example 5

[0411] Existing SSB transmissions can be swept by SSB index / ID (or beam direction). In the present disclosure, unless it is explicitly stated that SSB transmission is temporary or unidirectional (i.e., transmission by SSB index / ID), it can mean transmission once in all directions (i.e., transmission by SSB burst or SSB group) from the perspective of beam management in which cell service is performed. Multiple transmissions in the same direction can also be included in SSB transmission.

[0412] Similar to the omnidirectional sweeping of AO SSB transmission in the present disclosure, omnidirectional sweeping may also be performed for OD SSB without any special restrictions.

[0413] Alternatively, the present disclosure may define that sweeping is performed for the OD SSB in a direction corresponding only to some directions of the AO SSB. For example, assuming that the number of SSB indices / IDs included in the AO SSB burst / group is at most M, the number of SSB indices / IDs included in the OD SSB burst / group may be less than M. For example, the SSB indices / ID(s) included in the OD SSB burst / group may correspond to some of the SSB indices / ID(s) included in the AO SSB burst / group. Here, the same SSB indices / IDs in the AO SSB and the OD SSB may mean the same beam direction, or may mean that the AO SSB and the OD SSB are QCLed. For example, only some of the SSB indices / ID(s) of the AO SSB may be used in the OD SSB transmission, and the rest may not be used. Accordingly, the number of times transmitted in a sweeping manner in one OD SSB burst (i.e., the number of SSB indices / IDs or the number of beam directions) may be less than the number of times transmitted in a sweeping manner in one AO ​​SSB burst (i.e., the number of SSB indices / IDs or the number of beam directions).

[0414] Additionally or alternatively, in terms of the number of bursts transmitted repeatedly within one period of SSB transmission (or the number of bursts included in a burst set), the number of bursts transmitted within one period of OD SSB may be set to be less than the number of bursts transmitted within one period of AO SSB. Furthermore, with respect to the number of SSB indices / IDs / beams transmitted within each burst, the number of SSB indices / IDs / beams within one OD SSB burst may be set / defined to be less than (or as a part of) the number of SSB indices / IDs / beams within one AO ​​SSB burst.

[0415] For example, the SSB index / ID / beam(s) within an OD SSB burst may be the same as the SSB index / ID / beam(s) within an AO SSB burst, or the SSB index / ID / beam(s) within an OD SSB burst may correspond to a subset of the SSB index / ID / beam(s) within an AO SSB burst.

[0416] In the examples below, the SSB index / ID / beam direction within an SSB burst or SSB group is collectively referred to as the SSB index.

[0417] Example 5-1

[0418] Information about the group of SSB indexes applicable to OD SSB can be provided to the terminal. For example, one or more lists of groups of SSB indexes can be configured, and one of the groups can be configured / instructed to the terminal. Information about these SSB index groups can be provided to the terminal via L1 / L2 / L3 signaling.

[0419] For example, if up to 8 SSB indices are defined, and a group including some of the indices (e.g., SSB indices 1, 3, 5, 7) is set up and the group is signaled / instructed to the terminal, the terminal can (repeatedly) transmit only the SSBs corresponding to the SSB indices 1, 3, 5, 7 within one cycle when transmitting OD SSB.

[0420] If an SSB group containing multiple SSB indices in the same direction is set / defined for AO SSB, only one SSB index in the corresponding direction can be included in the SSB group for OD SSB.

[0421] An SSB index can be commonly applied to both AO SSB bursts / groups and OD SSB bursts / groups. That is, regardless of the type of SSB burst / group to which the SSB index belongs, the same SSB index can correspond to the same SSB beam direction (or QCL relationship), and further, the information provided via the SSB can also be the same. In addition, although the SSB index for AO SSB and the SSB index for OD SSB are commonly defined, the transmission period and time / frequency offset may be set / defined to differ between the transmission of the SSB index for AO SSB and the transmission of the SSB index for OD SSB.

[0422] For example, SSBs having the same SSB index in AO SSB and OD SSB can be QCLed (with respect to Doppler spread, Doppler shift, average gain, average delay, delay spread, spatial reception parameters, etc.). For example, if the frequency locations or center frequencies of AO SSB and OD SSB are the same, it can be assumed that SSBs of the same SSB index are QCLed. When a signal / channel is set to be QCLed with a specific SSB index, the signal / channel can be QCLed by the same QCL parameters as the corresponding SSB index in AO SSB and OD SSB.

[0423] Example 5-2

[0424] The examples in which the AO SSB and OD SSB are transmitted together or only one of them is transmitted in the above examples can also be applied between multiple OD SSBs. For example, to determine whether both OD SSB#1 and OD SSB#2 are transmitted or only one of them is transmitted, the AO SSB in the above examples can be replaced with the OD SSB#1 that is triggered first, and the OD SSB in the above examples can be replaced with the OD SSB#2 that is triggered later, and the transmit / drop decision can be applied.

[0425] For example, if OD SSB#1 triggered at time T1 and OD SSB#2 triggered at time T2 are transmitted simultaneously (or have overlapping opportunities in the time domain) (with different periods applied), OD SSB#1 triggered first may be dropped.

[0426] Example 5-3

[0427] OD SSB can be set on a per BWP / cell basis.

[0428] If there is no configuration for OD SSB in a particular BWP / cell, OD SSB may not be indicated / activated / triggered in that BWP / cell.

[0429] Additionally, if there is no configuration of OD SSB within the BWP / cell, measurement / reporting based on OD SSB may not be configured / triggered / activated. If there is an AO SSB within the BWP / cell, measurement / reporting based on OD SSB may be performed based on AO SSB instead of OD SSB in response to configuration / trigger / activation of measurement / reporting based on OD SSB. In this way, whether OD SSB is used instead of AO SSB when OD SSB is not configured can be predefined or preconfigured.

[0430] For example, the transmit period for OD SSB can be used as the period and offset (periodicityAndOffset) parameter included in the SMTC settings for measurements, but if OD SSB is not set, the transmit period of AO SSB can be used.

[0431] For example, when OD SSB is transmitted in units of BWP, the BWP may reference an active BWP (e.g., the first active downlink BWP (firstactivedownlinkBWP) or default BWP (defaultBWP) or BWP corresponding to BWP ID 0 at the time when the SCell activation command is provided) after the SCell is activated. That is, transmission and measurement of OD SSB can be performed in units of active BWP.

[0432] Alternatively, when SCell is inactive and there is no active BWP, transmission (indication / activation / trigger) and measurement / reporting may be considered based on the OD SSB in firstactivedownlinkBWP or defaultBWP or initial BWP. If there is no configuration / indication (activation / trigger) for OD SSB in that BWP, the BWP with the transmitting OD SSB may be found in ascending or descending order starting from the lowest or highest BWP ID, and measurement / reporting may be performed on that BWP if necessary.

[0433] For example, if SCell is disabled and firstactivedownlinkBWP is not set, or if firstactivedownlinkBWP is set but no OD SSB is set within that BWP, the OD SSB may not be triggered / activated / instructed. Or, if firstactivedownlinkBWP is not set, or if firstactivedownlinkBWP is set but no OD SSB is set, the OD SSB of defaultBWP may be used.

[0434] For example, if OD SSB is not configured within defaultBWP in SCell disabled state, OD SSB may not be triggered / enabled / instructed.

[0435] For example, firstactivedownlinBWP can have one or more OD SSBs configured.

[0436] Example 5-4

[0437] A disable / deactivate command for the OD SSB being transmitted can be indicated via MAC CE. The bit field indicating OD SSB disable / deactivation can be signaled together with SCell index information.

[0438] For example, if the value of one bit field included in the MAC CE is 1, it may indicate disabling / deactivating the OD SSB being transmitted, and if the value is 0, it may indicate maintaining the current state (i.e., continuing to transmit the OD SSB).

[0439] Example 5-5

[0440] Triggering / activation / disabling / deactivation of OD SSB can be controlled / instructed via MAC CE. For example, triggering / activation / disabling / deactivation of OD SSB can be instructed via MAC CE for active BWP or firstActivedownlinkBWP.

[0441] Example 5-6

[0442] Disabling / deactivating OD SSB being transmitted can be set / indicated via L3 RRC signaling. For example, parameters corresponding to disabling / deactivating OD SSB can be defined.

[0443] For example, if the parameter is included in the L3 RRC information element, disablement / deactivation of the OD SSB being transmitted may be set / indicated, and if the parameter is not included in the L3 RRC information element, maintain status quo (i.e., continue transmitting the OD SSB) may be set / indicated.

[0444] Alternatively, when the value of the corresponding parameter is set to a first value, the disable / deactivation of the OD SSB being transmitted may be set / instructed, and when the value of the corresponding parameter is set to a second value, the maintenance of the current state (i.e., continued transmission of the OD SSB) may be set / instructed.

[0445] Example 5-7

[0446] Disabling / deactivating of OD SSB being transmitted can be set / indicated via L1 DCI. For example, a 1-bit field corresponding to disabling / deactivating OD SSB can be added to the DCI.

[0447] For example, if the value of the corresponding field in the DCI is set to a first value, disable / deactivate of the OD SSB being transmitted may be set / indicated, and if the value of the corresponding field is set to a second value, maintain the current state (i.e., continue transmitting the OD SSB) may be set / indicated.

[0448] Example 5-8

[0449] When OD SSB is configured via RRC signaling, the time offset parameter among the parameters related to OD SSB transmission may be set to a time domain difference value referenced to the AO SSB transmission time within the same BWP / cell. For example, the unit of the offset may correspond to ms, slot, slot group, symbol, symbol group, etc.

[0450] Alternatively, if AO SSB is not set / defined within the BWP / cell, even if the value of the time offset parameter for OD SSB is set to a specific value, the value may not be applied and a value of 0 may be applied (or the time offset may be considered as 0).

[0451] For example, for a cell supporting OD SSB SCell operation, the time domain location of the OD SSB may be provided by RRC. For this purpose, a parameter indicating an offset for the SFN and a parameter indicating a half-frame index may be provided, and if these parameters are not included, the UE may assume / apply the value as 0. In addition, as described above, a parameter for the time offset between the AO SSB and the OD SSB may be provided.

[0452] Example 5-9

[0453] For L1 measurements in SCell disabled state, measurements / reporting may be restricted to those defined for LTM (L1 / L2 triggered mobility) that were recently introduced (e.g. introduced in Release 18) rather than the older (e.g. defined in Release 15) measurement / reporting methods.

[0454] When configuring LTM-related measurements / reporting, the SCell index parameter or a specific parameter may be included. This parameter may indicate to the UE that LTM-related operations may be performed only when the SCell is deactivated. This parameter may also be used to turn on / off LTM, which is already configured for the cell, while the SCell is deactivated or activated. For example, if LTM-related operations are turned off when the SCell is activated, this may indicate that LTM-related measurements / reporting performed in the SCell deactivated state will not be performed.

[0455] According to the various examples of the present disclosure described above, by defining a clear operation for coexistence of AO SSB and OD SSB, or priority / drop between AO SSB and OD SSB, it is possible to efficiently provide synchronization / measurement via OD SSB in the time interval required by the terminal while saving network energy and reducing interference.

[0456] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0457] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics of the present disclosure. Therefore, the above detailed description should not be construed as limiting in any respect, 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 scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

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

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

[0460] The method proposed in this disclosure is explained with a focus on examples applied to 3GPP LTE / LTE-A, 5G, and 6G systems, but can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A, 5G, and 6G systems.

Claims

1. A step of receiving information related to the second synchronization signal block from the network by the terminal; and A step of receiving, by the terminal, from the network at least one of the second synchronization signal block on a second occasion or the first synchronization signal block on a first opportunity, based on information related to the second synchronization signal block, A method in which the first synchronization signal block is transmitted on the overlapped opportunity based on the overlap between the second opportunity and the first opportunity.

2. In paragraph 1, A method wherein the second synchronization signal block is included in a second group, and the first synchronization signal block is included in a first group.

3. In paragraph 2, One or more indices for one or more synchronization signal blocks including the second synchronization signal block within the second group, A method, wherein the method is a subset of one or more indices for one or more synchronization signal blocks including the first synchronization signal block within the first group.

4. In paragraph 1, In the above overlapping opportunities, the index of the second synchronization signal block and the index of the first synchronization signal block are the same.

5. In paragraph 1, A method in which synchronization signal blocks of the same index in the second group and the first group correspond to the same beam direction or are quasi co-located (QCL).

6. In paragraph 1, A method wherein the second synchronization signal block is transmitted on the second opportunity and the first synchronization signal block is transmitted on the first opportunity based on the second opportunity and the first opportunity do not overlap.

7. In paragraph 1, A method wherein the second synchronization signal block and the first synchronization signal block are transmitted within the same bandwidth portion (BWP).

8. In paragraph 7, Based on the fact that the first synchronization signal block corresponds to a CD (cell-defining) synchronization signal block or is located on a synchronization raster, The frequency domain resources of the second opportunity and the frequency domain resources of the first opportunity are different, method.

9. In paragraph 7, Based on the above first synchronization signal block being a non-cell-defining (NCD) synchronization signal block or not being located on the synchronization raster, The frequency domain resources of the second opportunity and the frequency domain resources of the first opportunity are the same.

10. In paragraph 9, A method wherein the second opportunity and the first opportunity overlap based on the time domain resources of the second opportunity being identical to each other, and the first synchronization signal block is transmitted without the second synchronization signal block on the overlapped opportunity.

11. In paragraph 1, The method wherein the second synchronization signal block corresponds to an NCD synchronization signal block or is not located on the synchronization raster.

12. In paragraph 1, The second opportunity corresponds to one of the candidate resources to which the second synchronization signal block is transmitted, The method wherein the first opportunity corresponds to one of the candidate resources to which the first synchronization signal block is transmitted.

13. In paragraph 1, In the above overlapping opportunities, the time domain resources of the second opportunity and the time domain resources of the first opportunity are the same, and the frequency domain resources of the second opportunity and the frequency domain resources of the first opportunity are the same.

14. In paragraph 1, A method wherein the information related to the second synchronization signal block includes at least one of setting information for the second synchronization signal block or information indicating transmission of the second synchronization signal block.

15. In paragraph 1, The above second synchronization signal block is an on-demand SSB (synchronization signal / PBCH (physical broadcast channel) block), A method wherein the first synchronization signal block is a legacy SSB or an always-on SSB.

16. One or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receiving information related to the second synchronization signal block from the network via the one or more transceivers; and Based on information related to the second synchronization signal block, one or more of the second synchronization signal block on a second occasion or the first synchronization signal block on a first opportunity is set to be received from the network through the one or more transceivers, A terminal in which the first synchronization signal block is transmitted on the overlapped opportunity based on the overlapping of the second opportunity and the first opportunity.

17. A step of transmitting information related to the second synchronization signal block to the terminal by the network node; and A step of transmitting, by the network node, to the terminal at least one of the second synchronization signal block on a second occasion or the first synchronization signal block on a first opportunity based on information related to the second synchronization signal block, A method in which the first synchronization signal block is transmitted on the overlapped opportunity based on the overlap between the second opportunity and the first opportunity.

18. One or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting information related to the second synchronization signal block to the terminal via one or more transceivers; and Based on information related to the second synchronization signal block, one or more of the second synchronization signal block on a second opportunity or the first synchronization signal block on a first opportunity is set to be transmitted to the terminal through the one or more transceivers, A base station, wherein the first synchronization signal block is transmitted on the overlapped opportunity based on the overlapping of the second opportunity and the first opportunity.

19. One or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions for performing a method according to any one of claims 1 to 15 based on execution by said one or more processors.

20. One or more non-transitory computer-readable media storing one or more instructions that are executed by one or more processors to control the performance of a method according to any one of claims 1 to 15.

Images