Method and device for uplink transmission / reception in wireless communication system

Abstract

Disclosed are a method and a device for uplink transmission / reception in a wireless communication system. A method according to one embodiment of the present disclosure comprises the steps of: receiving, by a terminal, first information related to at least one common reference signal (RS) set for a plurality of events from a base station; monitoring, by the terminal, whether each of the plurality of events has occurred on the basis of the at least one common RS set; and transmitting, by the terminal, information related to a first event to the base station on the basis of the occurrence of the first event among the plurality of events, wherein a first condition related to the first event may be based on a first RS included in the at least one common RS set.

Description

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

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for performing uplink transmission and reception 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 performing uplink transmission and reception in a wireless communication system.

[0005] In addition, an additional technical challenge of the present disclosure is to provide a method and device for performing terminal-initiated / triggered or event-based channel state information reporting operations.

[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 will 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 embodiment of the present disclosure includes the steps of: receiving, by a terminal, first information related to at least one common reference signal (RS) set for a plurality of events from a base station; monitoring, by the terminal, whether each of the plurality of events has occurred based on the at least one common RS set; and transmitting, by the terminal, information related to the first event to the base station based on the occurrence of a first event among the plurality of events, wherein a first condition related to the first event may be based on a first RS included in the at least one common RS set.

[0008] According to another embodiment of the present disclosure, a method includes the steps of: transmitting, by a base station, first information related to at least one common reference signal (RS) set for a plurality of events to a terminal; and receiving, by the base station, information related to the first event from the terminal based on occurrence of a first event among the plurality of events, wherein occurrence of each of the plurality of events is monitored based on the at least one common RS set, and a first condition related to the first event may be based on a first RS included in the at least one common RS set.

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

[0010] Additionally, various embodiments of the present disclosure may provide methods and devices for performing terminal-initiated / triggered or event-based channel state information reporting operations.

[0011] Additionally, various embodiments of the present disclosure may reduce overhead associated with resources for reporting channel state information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0028] FIG. 16 is a flowchart illustrating a method for a terminal to perform a communication procedure according to one embodiment of the present disclosure.

[0029] FIG. 17 is a flowchart illustrating a method for a base station to perform a communication procedure according to one embodiment of the present disclosure.

[0030] FIG. 18 is a diagram for explaining a signaling procedure of a network side and a terminal according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0048] 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), and 5G NR.

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

[0050] Network structure

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

[0052] 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 function 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.

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

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

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

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

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

[0058] Systems applicable to this disclosure

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

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

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

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

[0063] Device applicable to the present disclosure

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0079] Communication procedures

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

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

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

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

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

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

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

[0087] 6G system core technologies

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

[0089] artificial intelligence

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0151] THz communication (terahertz communication)

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

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

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

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

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

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

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

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

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

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

[0162] 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 of the beams may be required, resulting in link instability.

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

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

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

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

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

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

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

[0170] non-terrestrial networks (NTN)

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

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

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

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

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

[0176] Figures 12 and 13 are only 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.

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

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

[0179] Integrated Sensing and Communication (ISAC)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0205] 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 (CSI-RS resource indicator), 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 through at least one of a physical uplink control channel (PUCCH) or a PUSCH.

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

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

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

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

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

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

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

[0213] Some or all of the examples of FIGS. 1 to 15 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.

[0214] Terminal-initiated / triggered reporting or event-based / triggered reporting

[0215] In describing the present disclosure, " / " means "and", "or", or "and / or" depending on the context. In addition, "beam" in the present disclosure may mean a source RS for a "spatial filter" or a "spatial relationship", and may be interpreted as a QCL (type-D) RS, a (DL / UL / joint) TCI state, or (in the case of uplink) a spatial relationship RS.

[0216] A basic wireless communication system supports various types of event-based or terminal-initiated / triggered transmissions. These event-based or terminal-initiated / triggered transmissions include RRC message-based transmissions or data (e.g., transport block (TB))-based transmissions. For example, if a radio link failure (RLF) event occurs during a radio link monitoring (RLM) process, the terminal may initiate an RRC re-establishment process based on an RRC message.

[0217] Additionally, event-based transmission may be supported at Layer-1 (L1) and / or Layer-2 (L2). For example, procedures for transmitting UL data (e.g., UL TB, UL-SCH, etc.) via scheduling request (SR), procedures for transmitting information related to beam failure recovery (BFR) in case of beam failure, etc. may be utilized.

[0218] Additionally, a procedure is being defined for performing beam reporting when a specific beam-related event (e.g., finding a new beam superior to the current beam) occurs in a next-generation wireless communication system.

[0219] One or more of the above-described information may be transmitted to the base station via an explicit or implicit method (e.g., transmitting a new beam index via PRACH (physical random access channel) resource selection information). In addition, one or more of the above-described information may be transmitted all at once or in parts via one or more UL resources. For example, based on the occurrence of a beam failure event, the terminal may transmit a beam failure recovery request (BFRQ) to the base station via a PUCCH, and may transmit new beam information to the base station via a BFR MAC control element (CE).

[0220] In describing the present disclosure, information (e.g., SR, BFRQ, new beam information, etc.) transmitted to the network via an event-based and / or terminal-initiated / triggered transmission method of a terminal is referred to as "event information." The event information may be implicitly transmitted by a specific (connected) UL signal. For example, SR or / and BFRQ may be transmitted to a base station depending on whether a specific preset SR PUCCH resource is transmitted. In addition, the event information may be transmitted to the base station via UCI and / or MAC CE.

[0221] Additionally, in describing the present disclosure, the conditions that trigger the transmission of event information are referred to as "event triggering conditions." Whether standardized event triggering conditions are applied may be determined based on the nature / type of the event transmission and the effect resulting from such transmission. As another example, event triggering conditions (e.g., event conditions such as SR) may not be standardized.

[0222] Next-generation wireless communication systems may support various event-based L1 / L2 transmission techniques to achieve low latency and / or low overhead. For example, event-based L1 / L2 transmission techniques could be utilized not only for BFR and SR, but also for CSI reporting. Furthermore, beam reporting for various events and L1 / L2 event-based transmission procedures related to RLF could be supported.

[0223] In addition, in the next-generation wireless communication system, communication links can be more efficiently optimized according to the circumstances of each terminal, and for this purpose, AI / ML operations on the terminal side can be utilized. That is, rather than the terminal relying on the settings / instructions of the base station, a request / report for the system settings preferred by the terminal (e.g., RS-related settings, CSI feedback-related settings, UL MIMO / port-related settings, etc.) and / or the base station's operations (e.g., transmission of specific DL RS(s), UL RS trigger, resource allocation, etc.) can be transmitted / performed. Based on the request / report, the communication link (e.g., DL / UL / SL) for the terminal can be operated more efficiently.

[0224] For example, the terminal may request / report specific beam RS related settings (e.g., preferred beam(s), repeated beam transmission, number of beams, transmission cycle, etc.) and / or beam RS transmission to the base station in terms of beam management. As another example, for DL / UL CSI measurement, the terminal may request / report settings related to DL RS (e.g., CSI-RS) or UL RS (e.g., SRS) and / or DL / UL codebook related settings to the base station. As another example, the terminal may request / report DL / UL control channel / signal related settings (e.g., HARQ, CORESET, PUCCH, UCI, DCI, etc.) to the base station.

[0225] The base station may initiate / trigger requests / reports related to the base station settings / operations of the terminals described above. However, if changes to the described settings are required and / or base station operations are required, the terminal may perform reports / transmissions (e.g., event-based transmission procedures) related to the described settings, thereby enabling efficient use of system resources.

[0226] As described above, supporting various event-based transmissions or terminal-initiated / triggered transmission reporting can reduce system resource overhead, as transmission / reporting procedures can be performed only when relevant conditions are met (or when necessary). However, monitoring more than one event can increase the implementation burden on the terminal.

[0227] In particular, since the triggering conditions of many events (e.g., BFD, RLM, event-based CSI feedback, DL RS configuration / transmission (change) request / report, CSI feedback configuration (change) request / report, etc.) can be defined / configured based on the DL RS reception of the terminal, the overhead for monitoring the triggering conditions of the terminal events may increase. From the base station's perspective, the overhead for transmitting various event-related RS and configuration / instruction information may also increase.

[0228] That is, to support various event-based transmissions, the computational burden (e.g., counters / timers) and memory burden associated with DL RS measurement and monitoring at the terminal may increase. At the base station, the overhead for various event-related DL RS transmissions and / or configuration / instruction may also increase.

[0229] In the following, we describe a method for reducing the complexity and overhead of multiple event-based transmissions based on common / related elements per event to solve the above-described problems.

[0230] FIG. 16 is a flowchart illustrating a method performed by a terminal according to one embodiment of the present disclosure.

[0231] The terminal can receive first configuration information related to at least one common reference signal (RS) set for multiple events from the base station (S1610).

[0232] For example, a terminal may receive first configuration information related to at least one RS set for monitoring trigger conditions for each of multiple events. At least one RS set is commonly used across multiple events, and thus may be represented as at least one common RS set. Furthermore, in FIGS. 16 and 17 , the RS set may also be represented as an M-RS set.

[0233] For example, a first condition related to a first event among multiple events may be based on a first RS included in at least one common RS set. That is, a first condition related to the first event may be configured based on the first RS, and the terminal may perform a measurement operation or the like for the first RS to monitor whether the first condition is satisfied (e.g., whether the first event occurs).

[0234] Here, the terminal may receive first configuration information from the base station via upper layer signaling (e.g., SIB, RRC message, etc.). For example, the first configuration information may include the number, configuration, type, and / or beam / TCI status information associated with at least one common RS set.

[0235] Before or after step S1610, the terminal may transmit terminal capability information (related to multiple events) to the base station. The first information may be configured based on the terminal capability information, but is not limited thereto.

[0236] For example, the terminal capability information may include at least one of the maximum number of common RS sets supported by the terminal, the maximum number of RSs within the common RS set supported by the terminal, the maximum number of types of common event instances supported by the terminal, or information on the types of events supported by the terminal.

[0237] The terminal can monitor whether each of a plurality of events occurs based on at least one common RS set (S1620).

[0238] As described above, the first (trigger) condition associated with the first event may be defined / set based on the first RS included in at least one common RS set. The second condition associated with the second event among the multiple events may be defined / set based on the common RS set and the RS set associated with the second event.

[0239] For example, the terminal may receive second configuration information from the base station, including a set of RSs related to a second event. The second condition related to the second event may be based on a first RS included in the common RS set and a second RS included in the set of RSs related to the second event. That is, the terminal may monitor whether the second event occurs based on the RS(es) included in the common RS set and the RS(es) included in the set of RSs related to the second event.

[0240] Additionally or alternatively, the terminal may receive from the base station third configuration information including at least one of i) information related to a common performance metric for at least one common RS set or ii) information related to a common filter for at least one common RS set.

[0241] For example, information related to a common performance metric for at least one common RS set may include at least one of a threshold related to the common performance metric or a type of the common performance metric (e.g., RSRP, virtual BLER, RSRQ, PMI, CQI, RI, etc.). And information related to a common filter may include at least one of a (common) measurement window, a (common) filter type, or a (common) filter coefficient.

[0242] Accordingly, the terminal may obtain a common performance figure value through at least one common RS set and / or utilize a common filter, and may perform monitoring of each of a plurality of events based on the obtained common performance figure value and / or common filter.

[0243] For example, assume that at least one common RS set includes a first common RS set and a second common RS set. The terminal can monitor the occurrence of each of multiple events based on the values ​​of common performance indicators based on the first common RS set (e.g., common performance indicator values ​​obtained from RSs included in the first common RS set) and the values ​​of common performance indicators based on the second common RS set.

[0244] Additionally or alternatively, the terminal may receive third configuration information related to at least one common event instance for at least one common RS set from the base station. For example, the third configuration information may include the type, counter, and / or timer of the common event instance for at least one common RS set. That is, a common event instance and / or a counter / timer related to the instance may be applied to each common RS set.

[0245] For example, the terminal may monitor the occurrence of each of a plurality of events based on a counter associated with at least one common event instance. For example, the terminal may measure a first RS included in at least one common RS set to identify whether a common event instance occurs. The terminal may increment the corresponding counter value as a common event instance based on the first RS occurs. The terminal may determine whether monitoring conditions for the plurality of events are met based on the counter value associated with the common event instance.

[0246] Here, the at least one common event instance may include at least one of: i) a beam failure event instance for a serving beam or a transmission configuration indicator (TCI), ii) a beam failure instance for a non-serving beam or TCI, or iii) an event instance associated with a new beam. As an example, the terminal may monitor whether a first event occurs based on a counter associated with each of two or more common event instances among the at least one common event instance.

[0247] Based on the occurrence of a first event among multiple events, the terminal may transmit information related to the first event to the base station (S1630). Here, the information related to the first event may include at least one of information related to the occurrence of the first event or performance indicators related to the occurrence of the first event. However, this is merely an example, and the terminal may transmit report information related to the first event to the base station.

[0248] Additionally or alternatively, the condition of the third event among the plurality of events may include a condition related to the occurrence of the first event. That is, at least one of the (trigger) conditions of the third event may be the occurrence of the first event.

[0249] For example, assume that the third event is a new beam reporting event following a beam failure. The third event may occur / trigger upon the occurrence / trigger of a first event (e.g., a serving beam failure event and / or a new beam discovery event).

[0250] In describing the present disclosure, each configuration information may be received from a base station via higher-layer signaling (e.g., SIB, RRC message, etc.). For example, at least one of each configuration information (e.g., first configuration information, second configuration information, third configuration information, etc.) may be transmitted to a terminal via the same higher-layer signaling, but is not limited thereto.

[0251] The method described in the example of FIG. 15 may be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) of FIG. 1 may receive first information related to at least one common RS set for a plurality of events from a base station through one or more transceivers (106). The one or more processors (102) may monitor whether each of the plurality of events occurs based on the at least one common RS set. Based on the occurrence of a first event among the plurality of events, the one or more processors (102) may receive second information related to the first event from the base station through one or more transceivers (106).

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

[0253] FIG. 17 is a flowchart illustrating a method performed by a base station according to one embodiment of the present disclosure.

[0254] The base station may transmit first configuration information related to at least one common RS set for multiple events to the terminal (S1710). That is, the base station may configure an RS set that is commonly applied to multiple events for the terminal. At this time, the base station may configure the first configuration information based on terminal capability information received from the terminal, but is not limited thereto.

[0255] As described with reference to FIG. 16, the base station can transmit at least one of the first configuration information, the second configuration information, or the third configuration information to the terminal via upper layer signaling. The configuration and related operations of each configuration information have been described with reference to FIG. 16, so any redundant description will be omitted.

[0256] Based on the occurrence of a first event among multiple events, the base station can receive information related to the first event from the terminal (S1720).

[0257] The method described in the example of FIG. 17 may be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 may transmit first configuration information related to at least one common RS set for a plurality of events to a terminal via one or more transceivers (206). Based on the occurrence of a first event among the plurality of events, one or more processors (202) may receive information related to the first event from the terminal via one or more transceivers (206).

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

[0259] Below, we describe embodiments that reduce the complexity and overhead associated with event-based transmission by setting / defining common / related information for multiple events. Specifically, we describe integrated configuration / operation / computation methods for multiple stages for multiple events.

[0260] Example 1

[0261] Example 1 relates to a method for setting up a common monitoring (M)-RS set for multiple events (e.g., level 1).

[0262] Specifically, the base station can configure / instruct the terminal to configure a common M-RS set for multiple event-based transmissions. For example, the base station can transmit configuration information related to the common M-RS set for multiple events to the terminal. The trigger condition for each event can be configured based on some or all RSs of the common M-RS set.

[0263] In one embodiment of the present disclosure, a common M-RS set #1 for multiple events can be configured for serving beam / TRP / TCI / QCL RS(s). For example, DL RSs corresponding to instantaneously indicated TCI states (e.g., TCI states indicated by DCI / MAC CE, etc.) can be configured / indicated for M-RS set #1. And, M-RS set #1 can be used as a monitoring RS set for multiple event(s). For example, M-RS set #1 can be used for monitoring triggering conditions of each of RLM, BFD, and / or other beam-related events.

[0264] As another example of the present disclosure, M-RS set #1 and M-RS set #2 (corresponding to different TRP / beam / TRP) may be configured for a terminal. For example, M-RS set #1 (for a serving beam / TRP / cell) and M-RS set #2 (for a non-serving beam / TRP / cell) may be configured for the terminal, and event trigger conditions may be configured / defined based on two M-RS sets or one M-RS set for each of a plurality of events. That is, an association / mapping relationship between each of a plurality of events and M-RS sets may be configured / defined. As an example, an association / mapping relationship between an event and an M-RS set may be configured as follows:

[0265] - Event #1: (For BFD related events) M-RS Set #1;

[0266] - Event #2: (For events related to RLM) M-RS Set #1;

[0267] - Event #3: (For new beam discovery event) M-RS Set #1 and M-RS Set #2; and

[0268] - Event #4: (For events related to m-TRP BFD) M-RS Set #1 and M-RS Set #2.

[0269] As an example of the present disclosure, an M-RS set may include one or more (DL) RSs. When multiple RSs are included in an M-RS set, multiple events that set the same M-RS set as a monitoring RS may apply / use all RS(s) included in the M-RS set as monitoring RSs.

[0270] As another example, the M-RS(s) for a specific event may only include some of the RSs included in the M-RS set. In this case, an indicator for the RS(s) to be actually applied in the M-RS set(s) associated with each event may be set / indicated (via a higher layer message, DCI, or MAC-CE). For example, the indicator may consist of a value "n" for the nth RS in the M-RS set, or a bitmap of the M-RS set.

[0271] As an example of the present disclosure, a performance metric (e.g., a metric that serves as a reference for determining whether a condition is met for each event) may be separately set / regulated for each event. For example, a hypothetical block error rate (BLER) may be used as a performance metric for events related to RLM / BFD. L1-RSRP / L1-SINR may be used as a performance metric for events related to beams. L1-RSRP may be used as a performance metric for events related to new candidate beams.

[0272] As described above, if different, distinct performance metrics are used for each event, the terminal implementation burden and memory requirements for instantaneous measurements can be reduced through a common M-RS set.

[0273] Example 2

[0274] Embodiment 2 relates to a method (e.g., Level 2) of setting / designating common M-RS (set)(s) for multiple event-based transmission(s), and defining / setting common performance metrics and / or common filtering (e.g., measurement window, filter type, filter coefficients, etc.) for the M-RS (set)(s).

[0275] In one embodiment of the present disclosure, a common M-RS (set), a performance measure for the M-RS (set) (e.g., virtual BLER, RSRP, RSRQ, PMI, CQI, RI, etc.), and / or a common filter for the performance measure may be set for the terminal for each event. When the terminal obtains a specific measure based on the performance measure and / or filtering set / defined for a specific M-RS (set), the specific measure can be applied to each different event, thereby reducing the implementation complexity and memory requirements of the terminal.

[0276] Additionally or alternatively, performance metrics and / or filters may be commonly applied to the M-RS (set), but common performance metrics and / or filters may be set for different M-RS (sets). The methods according to each of Embodiments 2 and 1 may be applied, and common performance metrics and / or filters may be set for the M-RS sets.

[0277] For example, performance metrics and / or filters that are commonly applicable to M-RS set #1 (for serving beam / TRP / cell) may be set / specified, and performance metrics and / or filters that are commonly applicable to M-RS set #2 (for non-serving beam / TRP / cell) may be set / specified.

[0278] The terminal may support multiple types of events based on the output values ​​of performance metrics for each M-RS set. For example, event(s) for M-RS set #1, event(s) for M-RS set #2, and event(s) for M-RS sets #1 and #2 may be supported for each M-RS set, with common performance metrics values ​​(for each M-RS set).

[0279] For example, if MTRP related CSI / beam reporting events related to both M-RS sets #1 and #2 are set for a terminal, MTRP CSI / beam reporting may be supported based on the quality value obtained for TRP #1 in M-RS set #1 and the quality value obtained for TRP #2 in M-RS set #2.

[0280] As another example of the present disclosure, for event-based beam reporting associated with new beam discovery associated with both M-RS sets #1 and #2, the event-based transmission operation may be supported by a comparison between the quality value obtained for M-RS set #1 for the serving beam (e.g., indicated TCI state) and the quality value obtained for M-RS set #2 corresponding to the new candidate beam(s).

[0281] Additionally or alternatively, thresholds related to the quality values ​​of M-RSs may also be commonly set / defined for the event(s). For example, if the case where the quality value of M-RS (set) #n is less than (or / and greater than) the threshold is expressed as En, triggering conditions for multiple different events are set / defined based on En, so that the terminal can more easily perform monitoring operations for the triggering conditions for each event.

[0282] As an example of the present disclosure, if the triggering condition of a specific event is defined / determined by the L1 / L2 measurements of the specific event, there may be a problem that event-based transmission is performed unnecessarily due to poor measurement accuracy. To compensate for this, the conditions for event-based transmission related to most L1 / L2 measurements may be based on whether the event occurs more than N times within a certain period of time or whether the event occurs N times consecutively. In other words, the conditions for event-based transmission related to L1 / L2 measurements may operate based on a counter (and / or a timer).

[0283] In describing the present disclosure, when event-related counters are utilized, a single event occurrence is expressed as an "event instance." For example, to trigger a beam failure (BF) event in BFR, a beam failure instance may be determined based on a counter and a timer. For example, a beam failure instance may occur when a virtual BLER measured based on BFD RS(s) at the terminal physical layer exceeds a certain threshold.

[0284] Assuming that event-based transmission is triggered when an event instance occurs N times consecutively and / or over a certain period of time, a terminal configured for multiple event-based transmissions can determine the event instance for each event. That is, the terminal can determine whether each event has occurred based on an independent counter / timer.

[0285] Example 3

[0286] Embodiment 3 relates to a method (e.g., level 3) in which common M-RS (sets) are set / specified for multiple event-based transmission(s), and a common event instance is set / defined for each M-RS (set)(s).

[0287] As an example of the present disclosure, if M-RS set #1 is associated with a serving beam / TRP / TCI, event instance #1 may be defined / set as follows:

[0288] - Event Instance #1: Failure event instance for serving beam / TRP / TCI (e.g., instance where L1-RSRP of DL RS (e.g., (first) indicated TCI state) corresponding to serving beam / TRP / TCI is lower than threshold)

[0289] Multiple types of events can be supported (for S(single)-TRP operation) based on the above event instance #1:

[0290] - (Serving TRP) Pre-warning of BF event: Event instance #1 occurs N1 times while timer #A is running;

[0291] - (Serving TRP) BF Event: Event instance #1 occurs N2 times while timer #B is running; and

[0292] - RLM Event: Event instance #1 occurs N3 times while timer #C is running.

[0293] As an example of the present disclosure, a specific type of event may be determined based on a combination of multiple event instances. As an example, assume that the following event instances are defined / determined:

[0294] - Event Instance #2: Failure event instance for non-serving beam / TRP / TCI (e.g., an instance where L1-RSRP of DL RS (e.g., 2nd indicated TCI state) corresponding to non-serving beam / TRP / TCI is lower than threshold); and

[0295] - Event instance #3: An event instance related to a new beam discovery (e.g., 1) at least one of the RSs included in the M-RS set has a beam quality value greater than or equal to a threshold (e.g., RSRP) or / and 2) an instance where the beam quality value of at least one of the RSs included in the M-RS set is higher than the beam quality value of the serving beam (e.g., M-RS set #1) by a certain value or more).

[0296] Here, various events can be supported through combinations of multiple event instances, as in the examples described below:

[0297] - Event-based MTRP beam reporting: Counters / timers for event instance #1 and event instance #2 can operate independently, and the terminal can trigger reporting of beam-related information by determining whether TRP #1 and TRP #2 are BF;

[0298] - BF event related to new beam information: If event instance #1 and event instance #3 occur together (e.g., for a certain period of time and / or a certain number of times), the terminal may transmit BF related information and information about the new beam together to the base station; and

[0299] - New beam discovery event: If event instance #3 occurs (e.g., for a certain period of time and / or more than a certain number of times), but event instance #1 does not occur (e.g., for a certain period of time and / or more than a certain number of times), the terminal may perform a beam reporting procedure. That is, the terminal may perform a beam reporting procedure to transmit new candidate beam information to the base station even though BF has not occurred.

[0300] Additionally or alternatively, Embodiment 3 can be applied in conjunction with Embodiments 1 and 2. For example, event instances can be defined to be categorized into several types based on the operational relationships of the M-RS (set)(s). For example, event instance types can be defined as follows:

[0301] - Event Instance Type #1: If the performance numerical value of RS(s) of a single M-RS set is above / below a predefined / set threshold, the counter value related to the event instance is increased;

[0302] - Event instance type #2: If the performance numerical value of the RS(s) of the second M-RS set is higher (above a certain threshold) than the performance numerical value of the RS(s) of the first M-RS set, the counter value related to the event instance increases; and

[0303] - Event Instance Type #3: If the performance figures of RS(s) of a single M-RS set fluctuate beyond a certain value, the counter value related to the event instance increases.

[0304] The above event instance type #1 may be applied to event(s) regarding (beam / link) failure for a specific TRP / cell / CC / BWP. The above event instance type #2 may be applied to events related to performance comparison between TRPs / cells / CCs / BWPs. The above event instance type #3 may be applied to event-based CSI reporting procedures, etc.

[0305] However, this is only one embodiment, and other event instance types may be defined in addition to the above-described event instance types. Here, the instance types may be defined in an event-agnostic manner, such as through M-RS sets and / or thresholds, which may allow for the addition / extension of new events.

[0306] When Example 3 is applied, event instances can be comprehensively judged and operated for multiple types of events, thereby reducing the implementation complexity of the terminal. That is, according to Example 3, not only event instances but also related counters / timers can be set / defined commonly for the events.

[0307] Example 4

[0308] Embodiment 4 relates to a method (e.g., Level 4) for setting / defining whether a specific event among multiple event-based transmission(s) occurs is determined based on whether other event(s) occur.

[0309] That is, the method according to Example 4 can reduce the terminal implementation complexity of multiple event-based transmissions by integrating not only event instances but also related counters / timers for each event. An example of the method according to Example 4 is as follows:

[0310] - If a BF event occurs N times (e.g., over a certain period of time and / or consecutively), and beam recovery does not occur for a certain period of time after the BF event occurs, or the base station does not respond to the related BF report for a certain number of times / time after the BF event occurs, the terminal / base station determines that an RLF event has occurred;

[0311] - If a TRP #1 beam failure event and a TRP #2 beam failure event occur within a certain time period or simultaneously, the terminal determines that a CC / BWP / terminal-specific beam failure event has occurred; and

[0312] - If a serving beam failure event and a new beam discovery event occur within a certain time or at the same time, a new beam information reporting event and a BF event may be triggered.

[0313] Example 4 relates to a method for reducing the implementation burden on a terminal by integrating triggering conditions or event definitions at the event level. When Example 4 is applied, even if event triggering conditions or event definitions are not integrated, the triggering conditions for a specific event may have dependencies depending on the occurrence of other events or events.

[0314] For example, event-based CSI reporting can be configured / defined to trigger only when no serving beam / TRP failure occurs. As another example, event-based transmission for TRP #A can be configured / defined to trigger only when no beam / TRP failure event occurs for TRP #A. This dependency can allow for a hierarchy structure between events and / or priorities in event detection / report transmission. Accordingly, implementation complexity can be reduced by having the terminal perform procedures based on high-priority events. For example, when a high-priority event occurs, measurement values / counters / timers, etc. related to lower-priority events (or / and dependent sub-events) can be reset / flashed.

[0315] Multiple methods according to the above-described embodiments (e.g., Embodiments 1, 2, 3, and 4) may be applied / used together. For example, when the methods according to Embodiments 1 and 2 are applied together, a common performance index / filter for a common M-RS set may be utilized.

[0316] As another example, triggering conditions may be configured so that an event-based transmission procedure is determined to be a multi-step transmission procedure. In this case, at least one of the embodiments described above may be applied only to a specific step, or a method according to the embodiments described above may be applied to each step. For example, if a specific event trigger condition is defined in two steps, a method according to Embodiment 2 or Embodiment 3 may be applied as the first step. For example, the terminal may initially determine whether an event has occurred based on a common performance indicator or event instance for multiple events. If the first-step event condition is satisfied, the terminal may determine whether a second-step event trigger condition, which is configured / defined with individual performance indicators / event instances for each event, is satisfied. Accordingly, the terminal may determine whether to perform the final event-based transmission.

[0317] In addition to the embodiments described above, various combinations of multi-step event triggering conditions can be configured / defined, and the method(s) of the present disclosure can be applied only to specific step(s).

[0318] When the method(s) according to each of the above-described embodiments (e.g., at least one of Embodiment 1, Embodiment 2, Embodiment 3, and Embodiment 4) is applied, a mapping relationship between event(s) and M-RS (set)(s) can be established / defined. Through this, M-RS (set)(s) shared by at least one event(s) can be defined / established (by the base station), and an M-RS (set) corresponding to each event can be established / defined.

[0319] Even if different events share the same M-RS (set), the actions for those events may differ. These actions may include whether to release RRC, different types of reporting content, and different reporting / transmission mechanisms (e.g., PRACH-based or PUCCH-based transmission / reporting mechanisms). Examples of configurations for beam-related event(s) are as follows:

[0320] - M-RS set#1 for PCell_TRP#1_BFR / RLM / BM_event(s) #1;

[0321] - M-RS set#2 for PCell_TRP#2_BFR / RLM / BM_event(s) #2;

[0322] - M-RS set #3 for SCell_TRP#1_BFR / BM_Event(s) #1;

[0323] - M-RS set #4 for SCell_TRP#2_BFR / BM_event(s) #2; and

[0324] - BM_Event(s) #5 associated with both M-RS Set #1 and M-RS Set #2 (e.g., PCell MTRP BM).

[0325] Application of at least one of the above-described methods may reduce terminal implementation complexity (e.g., memory requirements, computational load, etc.). Accordingly, the terminal capability value required when applying the above-described method(s) may be less than the sum of the capability requirements for each event.

[0326] For example, when at least one of Embodiment 1, Embodiment 2, Embodiment 3, or Embodiment 4 is applied, the terminal may transmit terminal capability information including the maximum number of M-RS sets and / or the maximum number of M-RSs across the M-RS sets to the base station. The terminal capability reported by the terminal may be applied to multiple event(s).

[0327] As an example of the present disclosure, when the method according to Embodiment 3 is applied, the terminal may transmit / report terminal capability information including the maximum number of event instances (and / or types) (that can be operated simultaneously) to the base station. Additionally, when at least one of the above-described methods is applied, the terminal may transmit terminal capabilities related to event-based transmission (e.g., the total number of events (e.g., events supported by the terminal and / or that can be operated simultaneously), the total number of timers / counters, the total number of activated RS resources / ports, the total number of processing units (e.g., CSI processing units), etc.) to the base station. In addition, some of the terminal capabilities related to event-based transmission may be shared by multiple events. For example, a specific value (e.g., a value added to the capability-related information) may not be applied to multiple event(s).

[0328] As an example of the present disclosure, terminal capability values ​​related to events A and B to which embodiment 4 applies may be set / defined to the same value (compared to when only event A or event B is set).

[0329] The above-described method can be similarly applied not only to terminal capabilities but also to base station configuration and / or terminal operation. For example, the terminal may not expect to be set more than X events (according to the CPU occupancy rules in NR). For example, if embodiment 4 is applied to events A and B, even if events A and B are set at the same time, the value of X may be counted as only one. From the perspective of CPU occupancy rules, even if events A and B are set at the same time, they may be counted as occupying only one CPU.

[0330] FIG. 18 is a diagram for explaining a signaling procedure of a network side and a terminal according to one embodiment of the present disclosure.

[0331] FIG. 18 illustrates an example of signaling between a network side and a terminal (UE) in an M-TRP situation to which any of the examples of the present disclosure described above (e.g., a combination of one or more of Embodiments 1, 2, 3, 4, or / and their detailed embodiments) may be applied.

[0332] Here, the UE / network side is exemplary and can be replaced with various devices as described with reference to FIG. 3. FIG. 18 is provided for convenience of explanation and does not limit the scope of the present disclosure. Furthermore, some of the steps shown in FIG. 18 may be omitted depending on the situation and / or settings. Furthermore, in the operation of the network side / UE of FIG. 18, the aforementioned uplink transmission / reception operations, M-TRP-related operations, etc. may be referenced or utilized.

[0333] In the following description, the network side may be a single base station including multiple TRPs, or a single cell including multiple TRPs. Alternatively, the network side may include multiple remote radio heads (RRHs) / remote radio units (RRUs).

[0334] For example, ideal / non-ideal backhauls can be established between TRP 1 and TRP 2, which constitute the network side. Furthermore, while the following description is based on multiple TRPs, it can be equally extended to transmissions through multiple panels / cells, and can also be extended to transmissions through multiple RRHs / RRUs, etc.

[0335] In addition, although the following description is based on "TRP", as described above, "TRP" can be replaced and applied with expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pico cell, etc.), transmission point (TP), base station (gNB, etc.). As described above, TRP can be distinguished according to information about CORESET group (or CORESET pool) (e.g., CORESET index, ID).

[0336] For example, if a single terminal is configured to transmit and receive with multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for the single terminal. The configuration of such CORESET groups (or CORESET pools) can be performed via higher-layer signaling (e.g., RRC signaling).

[0337] Additionally, a base station may be a general term for an object that transmits and receives data with a terminal. For example, the base station may be a concept that includes one or more Transmission Points (TPs), one or more Transmission and Reception Points (TRPs), etc. Furthermore, the TPs and / or TRPs may include a panel of the base station, a transmission and reception unit, etc.

[0338] The terminal can receive one or more event-based transmission-related configuration information from the base station (S110).

[0339] For example, one or more event-based transmission-related configuration information may include event-related configuration information (e.g., criteria, thresholds, etc.), report information configuration information, UL channel resource information for reporting / transmission (e.g., PUCCH / PUSCH resources, etc.), etc. Additionally or alternatively, one or more event-based transmission-related configuration information may include various configuration information related to Embodiment 1, Embodiment 2, Embodiment 3, and / or Embodiment 4.

[0340] Prior to step S110, the terminal may transmit terminal capability information (e.g., capability information related to event-based transmission supported by the terminal, etc.) to the base station. For example, capability information related to event-based transmission supported by the terminal may include the maximum number of M-RS sets supported by the terminal and / or the maximum number of RSs within the M-RS set, the total number of event types / timers / counters supported by the terminal, etc.

[0341] The base station can transmit an RS to the terminal based on the above-described configuration information (S115). The base station can monitor whether an event has occurred based on the RS transmitted by the terminal (S120). At this time, the occurrence of a specific event may be determined regardless of whether the RS has been received. In the event monitoring process (S120), at least one of the embodiments described above (e.g., Embodiment 1, Embodiment 2, Embodiment 3, and / or Embodiment 4) of the present disclosure may be applied.

[0342] When a specific type of event occurs, the terminal may perform UL transmission (e.g., transmission of information related to the specific type of event) (S125). The procedures and / or parameters related to UL transmission may be based on the embodiments described above in the present disclosure.

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

[0344] 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 thereof. 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.

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

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

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

Claims

1. A step of receiving, by a terminal, first configuration information related to at least one common reference signal (RS) set for multiple events from a base station; A step of monitoring, by the terminal, whether each of the plurality of events occurs based on at least one common RS set; and A step of transmitting information related to the first event to the base station by the terminal based on the occurrence of a first event among the plurality of events, A method wherein a first condition associated with the first event is based on a first RS included in the at least one common RS set.

2. In paragraph 1, A second condition related to a second event among the plurality of events is based on a second RS included in the set of RSs related to the first RS and the second event, A method in which second configuration information including an RS set related to the second event is transmitted from the base station to the terminal.

3. In paragraph 1, A method in which third configuration information including at least one of i) information related to a common performance metric for at least one common RS set or ii) information related to a common filter for at least one common RS set is transmitted from the base station to the terminal.

4. In paragraph 3, The at least one common RS set includes a first common RS set and a second common RS set, A method in which the occurrence of each of the plurality of events is monitored by the terminal through the values ​​of the common performance figures based on the first common RS set and the values ​​of the common performance figures based on the second common RS set.

5. In paragraph 3, A method wherein information related to a common performance measure for at least one common RS set comprises at least one of a threshold value related to the common performance measure or a type of the common performance measure.

6. In paragraph 3, A method wherein information related to the common filter comprises at least one of a measurement window, a filter type, or a filter coefficient.

7. In paragraph 1, Third configuration information related to at least one common event instance for at least one common RS set is transmitted from the base station to the terminal, A method in which the occurrence of each of the plurality of events is monitored by the terminal based on a counter associated with at least one common event instance.

8. In paragraph 7, A method according to claim 1, wherein the at least one common event instance comprises at least one of: i) a beam failure event instance for a serving beam or a transmission configuration indicator (TCI), ii) a beam failure event instance for a non-serving beam or TCI, or iii) an event instance associated with a new beam.

9. In paragraph 7, A method wherein the occurrence of the first event is monitored based on a counter associated with each of two or more common event instances among the at least one common event instance.

10. In paragraph 1, A method in which terminal capability information including at least one of the maximum number of common RS sets supported by the terminal, the maximum number of RSs within the common RS set supported by the terminal, or the maximum number of types of common event instances supported by the terminal is transmitted from the terminal to the base station.

11. In paragraph 1, A method wherein the information related to the first event includes at least one of information related to whether the first event occurred or a performance indicator related to the occurrence of the first event.

12. In paragraph 1, A method wherein the condition of the third event among the plurality of events includes a condition related to whether the first event occurs.

13. 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 first information related to at least one common reference signal (RS) set for a plurality of events from a base station through the one or more transceivers; Monitor whether each of the plurality of events occurs based on at least one common RS set; and Based on the occurrence of a first event among the plurality of events, information related to the first event is set to be transmitted to the base station through the one or more transceivers, A first condition related to the first event is a terminal based on a first RS included in the at least one common RS set.

14. A step of transmitting first information related to at least one common reference signal (RS) set for multiple events to a terminal by a base station; and A step of receiving information related to the first event from the terminal by the base station based on the occurrence of a first event among the plurality of events, The occurrence of each of the plurality of events is monitored based on at least one common RS set, A method wherein a first condition associated with the first event is based on a first RS included in the at least one common RS set.

15. In the base station, the base station: one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting first information related to at least one common reference signal (RS) set for multiple events to a terminal via the one or more transceivers; and Based on the occurrence of a first event among the above multiple events, information related to the first event is set to be received from the terminal through the one or more transceivers, The occurrence of each of the plurality of events is monitored based on at least one common RS set, A base station, wherein the first condition associated with the first event is based on a first RS included in the at least one common RS set.

16. In a processing device configured to control a terminal, the processing device: 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 that, when executed by said one or more processors, perform a method according to any one of claims 1 to 12.

17. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein the one or more commands are executed by one or more processors to control a device to perform a method according to any one of claims 1 to 12.

Images