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

Abstract

Disclosed are a method and a device for performing uplink transmission and reception in a wireless communication system. The 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 uplink (UL) resource for a plurality of events from a base station; and transmitting, by the terminal, second information related to at least one event that has occurred within a first time window among the plurality of events to the base station on the basis of the at least one common UL resource, wherein the first time window may be based on at least one of a reception time point of the first information or third information related to the first time window.

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 comprises the steps of: receiving, by a terminal, first information related to at least one common uplink (UL) resource for a plurality of events from a base station; and transmitting, by the terminal, to the base station, second information related to at least one event occurring within a first time window among the plurality of events based on the at least one common UL resource, wherein the first time window may be based on at least one of a reception time of the first information or third information related to the first time window.

[0008] A method according to another embodiment of the present disclosure comprises the steps of: transmitting, by a base station, first information related to at least one common uplink (UL) resource for a plurality of events to a terminal; and receiving, by the base station, from the terminal, second information related to at least one event occurring within a first time window among the plurality of events based on the at least one common UL resource, wherein the first time window may be based on at least one of a reception time of the first information or third information related to the first time window.

[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 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 nodes 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., base station) can set resources for beam management to the first node (110) (e.g., terminal). Here, the resources can include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station can utilize a beam search signal (BSS) that is transmitted spatially separated from an existing downlink signal / channel for beam search. Here, the BSS can be transmitted based on a dedicated port for beam search. The dedicated port can 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 can 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 above-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 above-described settings, thereby enabling efficient use of system resources. That is, L1 / L2 event-based transmissions may be utilized.

[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] Additionally, if more than one event is triggered simultaneously, transmission resource overhead and power consumption of the terminal may increase, and the receiving burden of the related base station may increase.

[0228] In order to solve the above-described problems, an integrated transmission reporting / transmission method for multiple events is described below.

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

[0230] The terminal can receive first information related to at least one common uplink (UL) resource for multiple events from the base station (S1610).

[0231] For example, the first information may include at least one of the number of at least one common UL resource, the size of at least one common UL resource, or the type of at least one common UL resource. That is, a common UL resource may be set by the base station for a plurality of events, and the terminal may transmit information related to at least one of the plurality of events to the base station through the common UL resource.

[0232] Here, the first information may be included in configuration information related to event-based transmission. That is, the terminal may receive the first information from the base station through configuration information related to event-based transmission. For example, the configuration information may include at least one of the priorities of each of the plurality of events, conditions related to the plurality of events, type / identification information for each of the plurality of events, or transmission parameters for each of the plurality of events. In addition, the configuration information may be transmitted to the terminal via higher layer signaling (e.g., SIB, RRC, etc.).

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

[0234] For example, the terminal capability information may include at least one of the number of events that can be reported via at least one common UL resource, a reporting method for information about at least one event supported by the terminal, or a type of event capable of event-based transmission supported by the terminal.

[0235] The terminal may transmit second information related to at least one event occurring within a first time window among a plurality of events based on at least one common UL resource to the base station (S1620).

[0236] As an example of the present disclosure, the terminal may monitor the occurrence of each of a plurality of events during a first time window. Here, the first time window may be based on at least one of the reception time of the first information or third information related to the first time window.

[0237] For example, the third information may include at least one of the length of the first time window, the starting point of the first time window, or the period of the first time window. The third information may be transmitted to the terminal along with the first information through the same configuration information, but is not limited thereto. The third information may also be transmitted to the terminal through separate configuration information. Additionally, the starting point of the first time window may be determined based on the reception point of the first information, but may also be set by the third information.

[0238] As an example of the present disclosure, a terminal may monitor whether each of a plurality of events occurs during a first time window. Assume that at least one of the plurality of events occurs (or is triggered) within the first time window (or a condition of at least one event is satisfied). The terminal may transmit second information related to at least one event to a base station based on at least one common UL resource. That is, the terminal may transmit information about at least one event occurring during the first time window to the base station based on the common UL resource.

[0239] Here, the second information may include information related to the occurrence of at least one event, identification information for at least one event, or at least one performance indicator or parameter related to the occurrence of at least one event. Here, the types of performance indicators or / and parameters related to the occurrence of at least one event may be defined / set differently for each event.

[0240] For example, if the event is a beam failure event, the performance indicator may include a quality value (e.g., RSRP, RSRQ, etc.), and the type of parameter may include the type of cell in which the beam failure was detected (e.g., PCell / PSCell or secondary cell, etc.), identification information of the cell in which the beam failure was detected, etc. In other words, the performance indicator or / and the parameter may include information to be reported upon occurrence of the event.

[0241] As an example of the present disclosure, at least one common UL resource may include a first (common) UL resource and a second (common) UL resource. In this case, the terminal may transmit information related to the occurrence of at least one event and / or identification information for at least one event to the base station based on the first UL resource. In addition, the terminal may transmit performance figures or parameters related to the occurrence of at least one event to the base station based on the second UL resource.

[0242] Additionally or alternatively, assume that at least one event includes a first event and a second event. For example, if the priority of the first event is higher than that of the second event and the first and second events occur simultaneously, the terminal may drop the second information related to the second event.

[0243] At this time, the sum of the sizes of the second information associated with each of the first and second events may be greater than the size of the payload associated with at least one of the first UL resource or the second UL resource. That is, if the size of the information to be reported is greater than the payload of the first / second UL resource, the terminal may drop a specific event based on the priority of the event.

[0244] Here, the first event (e.g., an event with a higher priority) may include at least one of an event for a primary cell (PCell) or a primary secondary cell (PSCell), an event for a serving cell, or a beam failure event. And, the second event may include at least one of an event for a secondary cell (SCell), an event for a non-serving cell, or an event related to new beam discovery. However, this is only one embodiment, and the priority for each of the multiple events may be set by the base station.

[0245] And, at least one transmission parameter may be set / defined to be applied differently for each event. Here, the transmission parameter may include at least one of a repetition transmission method, uplink precoding or rank, transmission format, modulation and coding scheme (MCS), UL spatial filter, or UL power. Accordingly, the terminal may transmit the second information for each event to the base station using at least one transmission parameter applied to each event.

[0246] The method described in the example of FIG. 16 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 UL resource for a plurality of events from a base station through one or more transceivers (106). The one or more processors (102) may transmit second information related to at least one event occurring within a first time window among the plurality of events based on the at least one common UL resource to the base station through one or more transceivers (106).

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

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

[0249] The base station may transmit first information related to at least one common UL resource for multiple events to the terminal (S1710). That is, the base station may configure the common UL resource for the terminal, which is used for transmission procedures related to each of the multiple events. 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.

[0250] The base station may transmit configuration information to the terminal, including at least one of the first information, third information related to the time window, the priority of each of the plurality of events, conditions related to the plurality of events, the type of each of the plurality of events, and / or transmission parameters for each of the plurality of events. However, this is merely an example, and each piece of information may be transmitted to the terminal using different configuration information.

[0251] The base station can receive second information related to at least one event occurring within a first time window among a plurality of events based on at least one common UL resource from the terminal (S1720).

[0252] That is, the base station can receive information about events that occurred / triggered within the first time window from the terminal through a common UL resource.

[0253] The method described in the example of FIG. 17 can be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 can transmit first information related to at least one common UL resource for a plurality of events to a terminal via one or more transceivers (206). The one or more processors (202) can receive, from the terminal via one or more transceivers (206), second information related to at least one event occurring within a first time window among the plurality of events based on at least one common UL resource.

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

[0255] Below, a detailed description is given of an integrated transmission / reporting method for multiple event(s). In describing the present disclosure, the first resource and the second resource may be replaced with the first UL resource and the second UL resource, or the first UL resource and the second UL resource may be replaced with the first resource and the second resource.

[0256] Example 1

[0257] Embodiment 1 relates to a method / procedure in which a base station sets / defines / instructs UL resource(s) (e.g., first resource and / or second resource) related to event transmission to a terminal, and all or part of the UL resource(s) are common / same resources for multiple events.

[0258] When one or more events occur at a specific (reference) point in time or within a certain period of time (e.g., observation / detection window) based on a specific (reference) point in time, a terminal for which UL resource(s) related to event transmission are configured / defined / indicated may perform a transmission operation based on the UL resource(s) configured for one or more events. Here, the specific (reference) point in time may include a point in time related to an event detection / trigger / transmission instance.

[0259] As an example of the present disclosure, when multiple events to which common / same UL resource(s) are applied occur at a (reference) point in time or for a certain period of time, the terminal may transmit information related to the multiple events (e.g., report information according to the occurrence of multiple events, etc.) to the base station through the UL resource(s).

[0260] Embodiment 1 relates to a method for suppressing transmission burden on a terminal and increased overhead of UL resources by sharing UL resources associated with transmission for multiple events. Accordingly, a reference point or / and duration / window for determining event transmission applicable to a common event can be defined / set / indicated.

[0261] For example, whether an event occurs / transmits (e.g., reporting information based on the occurrence of an event) can be determined only in certain slots, such as by setting / defining whether an event occurs / transmits. Another example is whether an event occurs / transmits every N slots, such as by setting / defining whether an event occurs / transmits. Another example is whether an event occurs / transmits within slots corresponding to a specific DL slot index, such as a TDD system.

[0262] In describing the present disclosure, a reference point in time may collectively refer to a point in time for determining whether an event has occurred or whether UL transmission related to the event has occurred. For example, if the reference point in time is a point in time for determining whether UL transmission related to the event has occurred, the point in time for occurrence (determination) of the event may be different from the point in time for determining whether UL transmission has occurred. For example, a reference / decision time slot may be set in slot #n (a cycle is 4 slots), event #1 may be detected in slot #n, event #2 may be detected in slot #n-1, and event #3 may be detected in slot #n-1. At this time, in the reference / decision time slot, the terminal may determine whether events #1, #2, and #3 have occurred.

[0263] As another example, a time window related to event detection / transmission (e.g., an event observation / detection / trigger window) may be set / defined for the terminal. For example, the terminal may transmit information related to event(s) occurring during the time window to the base station at once.

[0264] When the above-described method(s) are applied, if multiple events occur at a specific reference point or during a specific time / window, the terminal may transmit common / shared UL resources for the corresponding event(s) to the base station. Here, the terminal transmitting common / shared UL resources to the base station may mean that the terminal transmits / reports information regarding the occurrence of the corresponding event(s) to the base station based on the common / shared UL resources. Accordingly, event-based transmission can be performed efficiently.

[0265] Additionally or alternatively, a reference point in time or time window may not be separately established / defined. Whether an event occurs or / and whether an event-related transmission occurs may be determined based on the time at which a UL resource (e.g., a first resource) related to event transmission is established or a time defined / established in relation to the UL resource (e.g., an SR-related cycle / time when the first resource is an SR resource). In other words, the time at which the UL resource is established / transmitted or / and a time defined / established in relation to the UL resource may serve as the aforementioned "reference point in time."

[0266] For example, whether an event occurs and / or whether an event-related transmission occurs can be determined based on slots in which UL resources are configured. For example, a time period from the nth UL resource transmission / configuration time point or later to the n+1th UL resource transmission / configuration time point or earlier can be configured / defined as a time window for determining whether an event occurs / transmits. If at least one event(s) occurs within the time window, the terminal can transmit information related to at least one event(s) to the base station in the next resource (e.g., the n+1th UL resource or the n+1+Mth UL resource). Here, M can be a configured / defined positive integer and can be based on a terminal processing time.

[0267] For example, UL resources (e.g., PUCCH, PUSCH, PRACH, etc.) related to event transmission may be resources preset by the base station for the terminal so that information related to the event occurrence can be transmitted to the base station when the event occurs. For example, UL resources related to event transmission may include at least one of a PUCCH resource (pre-configured) for SR / BFRQ, a PUCCH / PUSCH resource (pre-configured) for event-based beam reporting, and a PRACH / PUCCH resource configured by system information.

[0268] Additionally or alternatively, the base station may (dynamically) allocate UL resources to the terminal for reporting information related to the occurrence of an event at the terminal. The UL resources may include dynamic grant PUSCH resources, etc. For example, the base station may configure one or more UL resources for the terminal.

[0269] Below are examples of configuration / operation for UL resources for event-based transmission. At least one of the examples described below may be applied.

[0270] Example 1 - A method of configuring with a preset first UL resource and a preset second UL resource.

[0271] For example, a first UL resource may include a channel / resource for reporting an event occurrence or for pre-announcement of transmission / reporting from a second resource. The second resource may include a channel / resource for reporting, requesting, or / and transmitting an event (e.g., via UCI, MAC-CE, or / and TB).

[0272] For example, if the transmission capacity associated with an event is variable (e.g., the CSI and PMI payload size including PMI is dependent on the reported rank), a third resource, etc. may be dynamically configured / allocated to the terminal (by terminal request / report). In this case, the terminal may perform reporting, requesting, and / or transmission associated with the event across the second resource and / or the third resource. The second resource-based transmission may be performed after the first resource-based transmission or after the base station receives an acknowledgement / ACK message for the first resource (or the first resource-based transmission).

[0273] Example 2 - A method of configuring a preset first UL resource and a non-preset second UL resource.

[0274] For example, the first resource may include a channel / resource for reporting an event occurrence or requesting a scheduling for the second resource. For example, the first resource may include a UL resource for requesting a scheduling. The second resource may include a channel / resource for reporting, requesting, or / and transmitting an event (e.g., via UCI, MAC-CE, or / and TB). For example, the second resource may include a UL resource (e.g., a dynamic grant PUSCH resource) that the base station dynamically schedules for the terminal after receiving the first resource of the terminal.

[0275] Example 3 - A method of configuring with one preset UL resource (e.g., PUCCH, SPS PUSCH, etc.)

[0276] The terminal can perform event-based transmission based on preset UL resources when an event occurs. The base station can monitor preset UL resources for event-based transmission.

[0277] When Example 1 is applied to the operations according to the above-described example(s), the following operations can be performed.

[0278] How Example 1 is applied to Example 1 (Example 1-1)

[0279] As an example of the present disclosure, a common first resource may be set for multiple events, and a second resource may not be set in common for multiple events.

[0280] The terminal may transmit to the base station information regarding which event(s) have occurred via the first resource (e.g., the ID of the occurred event(s) or a bitmap related to information regarding the occurred event(s). Additionally or alternatively, the terminal may report to the base station information regarding which of the configured second resources (for each event) to perform transmission via (e.g., a resource indicator). Additionally or alternatively, the terminal may request the base station to allocate a new third resource (if the transmission capacity for the event(s) is insufficient with the preset second resources).

[0281] For example, if at least one event occurs, the terminal may report information related to at least one event to the base station based on a second resource set for at least one event.

[0282] How Example 1 is applied to Example 1 (Example 1-2)

[0283] In one embodiment of the present disclosure, a common second resource may be set for multiple event(s), and the first resource may not be set in common for multiple events.

[0284] The terminal may transmit information about an event that has occurred to the base station through a first resource configured / defined for each event. For example, SR resources, PUCCH resources, etc. may be configured for each event, and the terminal may transmit information about at least one event(s) that has occurred to the base station based on the first resource configured / defined for at least one event.

[0285] For example, after transmission based on the first resource(s) is performed, the base station may instruct the terminal to transmit information about one or more events that occurred through a second resource that is commonly configured for the event(s). The terminal receiving the instruction may perform transmission for the one or more events that occurred based on the second resource (commonly configured / defined for each event).

[0286] Additionally, the instruction message transmitted by the base station to the terminal may include information on which event(s) (among the event(s) reported by the terminal to have occurred and / or the configured event(s)) to perform transmission for through the second resource. For example, the instruction message may include an ID of the event(s) to be transmitted based on the second resource, a report / configuration ID, and / or an ID for the first resource(s). That is, the terminal may identify the event(s) to be reported through the second resource through the ID of the event(s), the report / configuration ID, and / or the ID for the first resource(s) included in the instruction message.

[0287] In another example of the present disclosure, the process of the base station instructing the terminal to transmit to the second resource may be omitted. For example, after performing transmission for the first resource(s) (for each event), the terminal may report information related to one or more event(s) to the base station based on a common second resource for one or more event(s).

[0288] Additionally or alternatively, in order to prepare for the case where at least one of the first resource(s) is not normally transmitted to the base station, the terminal may transmit information about the occurred event(s) (e.g., event ID, report ID, etc.) and / or information related to the amount (or range) of information about the event(s) to the base station via the second resource.

[0289] Additionally or alternatively, two resources may be configured / defined for each event, as well as a common second resource for multiple events. For example, if only one event is triggered (via the first resource), the terminal may perform a reporting operation based on the second resource configured for that event (e.g., the second resource configured for the first event among the second resources configured for each event). In another example, if multiple events are triggered, the terminal may perform a reporting operation based on the second resource configured commonly for each event.

[0290] How Example 1 is applied to Example 1 (Example 1-3)

[0291] A common first resource and a common second resource may be set for multiple events. The terminal may transmit information about which events have occurred (e.g., an ID for the occurred event(s) and / or a bitmap associated with the occurred event(s)) to the base station through the common first resource set for the multiple events. The terminal may report information related to the occurred event(s) to the base station based on the common second resource set for the multiple events.

[0292] Additionally, the information reported via the first resource may include i) information about the payload size to be transmitted via the second resource and / or ii) parameters related to the transmission method for the information to be transmitted via the first resource and / or the second resource.

[0293] For example, information about the payload size to be transmitted via the second resource may include information related to the TB size, UCI payload size, etc., such as a butter status report. In addition, parameters related to the transmission method may include a modulation / coding scheme (MCS), precoding, rank, antenna port, beam (e.g., spatial filter), UL power, TPR, UL TCI, sequence, symbol interval, RB size, etc.

[0294] If the parameters related to the above transmission method are variable, the terminal may report / transmit (together) parameters related to the transmission method preferred or applicable to the base station. For example, the terminal may transmit parameters related to the transmission method preferred or applicable to the base station based on the first resource. However, if the transmission method to be applied to the second resource is set / fixed, the transmission operation of the parameters related to the terminal's preferred or applicable transmission method may be omitted.

[0295] For example, if i) information about a payload size to be transmitted via a second resource and / or ii) parameters related to a transmission method for information to be transmitted via the first resource and / or the second resource are reported to the base station via the first resource, the terminal may perform a transmission operation based on the second resource according to the payload size and / or the transmission method. As another example, after a transmission operation based on the first resource is performed, the base station may separately instruct the terminal (via an acknowledgement / ACK message) about the payload size and / or the transmission method related to the transmission operation based on the second resource.

[0296] For example, after a first resource-based transmission, the base station may instruct or trigger the terminal to transmit based on a second resource, which is commonly set for each of the multiple events, through separate signaling (e.g., an instruction message, an acknowledgement / ACK message, etc.). As another example, the terminal may perform a second resource-based transmission at a predefined / set time after the first resource-based transmission without signaling from the base station.

[0297] Here, the signaling of the base station may include information about the event(s) for which transmission is to be performed via the second resource (e.g., an ID for the first resource(s), an event ID, a report / configuration ID, etc.). That is, the signaling of the base station may include information about which event(s) (among the event(s) reported by the terminal to have occurred or among the configured event(s)) to perform transmission for.

[0298] How Example 1 is applied to Example 2

[0299] A common first resource may be set for multiple events. The terminal may transmit information about which events have occurred (e.g., an ID for the event(s) that have occurred and / or a bitmap associated with the event(s) that have occurred) to the base station through the common first resource set for the multiple events. The terminal may report information related to the event(s) that have occurred to the base station based on the common second resource set for the multiple events or on a second resource individually set for each event.

[0300] As with Examples 1-3 described above, the terminal may report to the base station, via the first resource, i) information about the payload size to be transmitted via the second resource and / or ii) parameters related to the transmission method for information to be transmitted via the first resource and / or the second resource.

[0301] A base station can allocate a second resource to a terminal (e.g., a transmission method based on the second resource) through a first resource-based transmission. The terminal can transmit an event(s) generated through the allocated second resource.

[0302] For example, a message for second resource allocation transmitted from a base station to a terminal may include information about events for which related reporting is to be performed through the second resource (e.g., an ID for the first resource(s), an event ID, a report / configuration ID, etc.) (among event(s) reported by the terminal to have occurred or event(s) configured). The terminal may identify event(s) for which related information is to be reported through the second resource through the ID for the first resource(s), the event ID, and the report / configuration ID.

[0303] For example, multiple secondary resources may be allocated for each of multiple event(s) (e.g., via one UL DCL / grant per secondary resource / event or separate UL DCI / grants, etc.). In this case, information for allocating secondary resources may include information about the event(s) to be transmitted via the corresponding secondary resource, and information about the event(s) to be transmitted for each secondary resource (e.g., mapping information, indicators for the secondary resource, etc.). For example, information for allocating secondary resources may include mapping / bitmaps for mapping / indicating related event(s) for each secondary resource (e.g., events for which information is to be reported for each secondary resource, etc.).

[0304] How Example 1 is applied to Example 3

[0305] A common UL resource may be configured for multiple event(s). The terminal may determine whether multiple related event(s) occur for each transmission opportunity of the UL resource. As described above, the terminal may monitor the occurrence of at least one event(s) based on a reference point in time and / or a time interval. If one or more event(s) occur, the terminal may transmit information related to one or more event(s) for each transmission opportunity. If no event occurs, the terminal may not perform event-based transmission.

[0306] For example, information related to one or more event(s) transmitted by a terminal may include information (e.g., event ID, report / configuration ID, etc.) indicating which event(s) among multiple event(s) sharing the UL resource the information relates to. For example, information related to one or more event(s) may be included in a message (e.g., UCI, MAC-CE, etc.) transmitted via the UL resource, or may be included in a separate message. For example, the message may include a header for the message / transmission, and may be encoded separately. For example, two-part UCI encoding may be applied, and information related to one or more event(s) may be included on the first part UCI.

[0307] Additionally or alternatively, information related to one or more event(s) may be transmitted and received via different types / message formats. For example, an event ID (e.g., identifying information for an event occurring / reporting) may be transmitted and received via UCI, and information about the event (e.g., reporting information following the occurrence of the event, etc.) may be transmitted and received via MAC-CE.

[0308] Additionally or alternatively, the ID (combination) of each event may be mapped to a signature / sequence associated with the UL resource, and the base station may detect the corresponding signature / sequence to determine which event(s) the transmission is for.

[0309] As an example of the present disclosure, if the above-described examples 1 / 2 are applied, the terminal may only report the occurrence of an event(s) via the first resource and may not perform transmission via the second resource. To achieve this, the terminal may report or notify the base station via the first resource whether transmission based on the second resource is being performed.

[0310] For example, if information about each event(s) is encoded separately, as in Example 3, the terminal may transmit identification information (e.g., ID) of the event(s) to the base station (via the first part UCI). At this time, the presence or absence of subsequent information (e.g., the second part UCI) may also be included on the first part UCI (or the corresponding identification information).

[0311] As an example of the present disclosure, some / all of the event(s) reported through the first resource may be canceled before the reporting time of the second resource. For example, assume that a beam / link failure event has occurred and the terminal reports information related to the beam / failure event to the base station based on the first resource. In this case, there may be a case where the beam / link quality is restored before the reporting operation based on the second resource. To prevent such a situation, the terminal may report / transmit information related to the maintenance or cancellation status of the event(s) reported based on the first resource (e.g., IDs related to the generated / canceled event(s)) to the base station through the second resource.

[0312] As an example of the present disclosure, when Example 1 is applied, multiple candidates for the second resource may be configured on the same / different component carriers (CCs). The terminal may perform a transmission operation for one or more event(s) occurring through a specific one of the candidates for the second resource (depending on the amount of information to be transmitted, link quality, and / or the received TRP / cell / CC, etc.).

[0313] The selection of a candidate for a second resource may be determined based on predefined rules or may be performed by the terminal. In another example, at least one candidate for a second resource may be selected based on a predefined rule, and (if multiple event(s) are selected based on the rule), the terminal may select one or more of the candidates for at least one second resource.

[0314] For example, if an event occurs where the quality of a specific beam / TRP / cell / CC degrades (below a certain level), a rule can be defined / configured that the terminal performs event-based transmission through a secondary resource set for a different beam / TRP / cell / CC than the corresponding beam / TRP / cell / CC. As another example, if an event occurs where (the quality of the current beam / TRP / cell / CC degrades below a certain level) and a beam / TRP / cell / CC with a quality that is superior to the current beam / TRP / cell / CC by a certain level or higher is found, a rule can be defined / configured that the terminal performs secondary resource-based transmission to the new beam / TRP / cell / CC. As an example, if a serving beam failure event occurs in the PCell, the terminal can perform a reporting operation for the event through at least one of the candidates for the secondary resource of another CC (e.g., PSCell or SCell) (set in a different band / frequency range than the PCell).

[0315] For example, the base station may set each of the second resources for the terminal according to the number of events that have occurred and / or the range of the amount of information, and the terminal may perform a reporting / transmission operation based on the second resource corresponding to / set for the number and / or amount of information (range) of events transmitted through the first resource.

[0316] Additionally or alternatively, the terminal may transmit information to the base station for selecting a specific second resource (among a plurality of second resource candidates) via the first resource.

[0317] As another example, if example 1 / 2 applies and the transmission timing of the second resource is variable, the terminal may report / transmit information related to the (preferred) transmission timing for the second resource to the base station via the first resource.

[0318] As an example of the present disclosure, the configuration (e.g., time / frequency location, format, transmission method, cycle, etc.) for UL resources to be used for multiple event(s) may be common. In this case, the configuration format of information reported for each event may differ. For example, the base station may configure (SPS) PUSCH resources to the terminal as resources for event transmission. When a specific event occurs, the terminal may transmit a MAC-CE containing information related to the specific event to the base station via the PUSCH resources. When another event occurs, the terminal may transmit a UCI containing information related to another event to the base station via the PUSCH resources.

[0319] That is, even if UL resources are shared, the composition / format (e.g., MAC-CE or UCI, etc.) of the information / packet / message transmitted through the resource may be defined / set differently for each event. As another example, when the same event occurs, information related to the same event may be reported to the base station through MAC-CE and UCI information, taking into account addition / multiplexing with other event information. That is, MAC-CE and UCI-based reporting formats may be supported for the same event. In this case, information about the message composition / format (e.g., a 1-bit indicator for MAC-CE or DCI) may be included in the reporting information (e.g., information transmitted through the first resource in Examples 1 / 2 or / and separately encoded information in Example 3, etc.).

[0320] As an example of the present disclosure, transmission properties for events may differ. For example, reporting information from a terminal for configuring beam / precoding of a base station, such as beam / CSI reporting, may be set / defined / instructed / triggered, and information (e.g., request information) requesting transmission of a specific RS for AI / ML-related operations, etc. may be set / defined / instructed / triggered. For example, when request information is transmitted to a base station, there may be an action following the request information from the base station, and the action needs to be consistent / aligned with the request from the terminal. Accordingly, the request information and the report information may differ.

[0321] Additionally, transmission properties for each event may vary depending on the importance / impact of the event, the actions involved in the event (e.g., transmission / reception actions such as CSI data, DL / UL control, etc.), and the application / use case for the event (e.g., AI / ML, sidelink IAB, IoT, etc.).

[0322] Accordingly, one or more types / types of event(s) or event-related transmissions may be defined, and one or more types / types may be used in the signaling procedure.

[0323] For example, the reporting information of the terminal (e.g., information reported via the first resource in examples 1 / 2 and / or separately encoded information in example 3) may include information on the type / kind(s) of the occurred event(s). As another example, when the base station configures an event-common UL resource for the terminal, the base station may designate an event type / kind for the corresponding UL resource to the terminal. As another example, when triggering / activating / deactivating an action / transmission related to a specific event, the terminal may be configured / instructed / defined to operate on an event type / kind basis.

[0324] As an example of the present disclosure, the transmission beam / precoder for UL resource(s) may be directed / configured by the base station. In this case, separate rules may be established / defined for specific event(s).

[0325] For example, if an event related to a degradation of link quality of a serving beam / link / TRP (e.g., an event in which the link quality value is detected to be lower than a reference value) occurs, the success probability of UL transmission (e.g., a reporting procedure related to the event) may be low when the UL transmission is performed through the serving beam / link / TRP. To prevent such a situation, a default beam / link / TRP may be separately set / defined, and the terminal may perform a reporting procedure related to the event through the default beam / link / TRP. For example, the default beam / link / TRP may include the most recently accessed SSB, the beam / TRP for receiving system information, the PRACH transmission beam / TRP, etc.

[0326] Additionally or alternatively, power control parameters to be used by the terminal may also be separately configured / defined. That is, transmission methods / parameters (e.g., beam (or spatial filter), UL TCI, TRP, power) to be applied to common UL resources may be configured / defined differently for each event(s) that occur.

[0327] As an example of the present disclosure, assume that multiple events corresponding to different transmission methods / parameters occur. In this case, if a default beam / TRP / link, etc. is set / defined to be applied to at least one of the multiple events, the terminal may perform a reporting operation for the multiple event(s) based on the default beam / TRP / link. As another example, the terminal may perform a reporting operation for the multiple event(s) based on the transmission method / parameter corresponding to an event with a higher priority among the multiple events.

[0328] When the examples described above are applied, the amount of information to be transmitted through the event-based reporting procedure may vary depending on the event(s) that occurred. To resolve this payload size ambiguity issue, in Examples 1 / 2, information related to the payload size and / or ID information related to the event(s) may be transmitted and received or reported between the terminal and the base station through the first resource. As another example, in Example 3, information related to the payload size and / or ID information related to the event(s) that occurred may be transmitted and received between the terminal and the base station through a separate header message (e.g., a header for MAC-CE, etc.) or individually encoded UCI bits (e.g., the first part UCI of a two-part UCI).

[0329] Additionally or alternatively, when transmissions for multiple events are performed over the same UL resource, some of the information about the event(s) may be omitted (depending on the maximum payload size of the configured resource and / or according to configured / defined rules). For example, some of the information about each event may be omitted and / or transmissions for specific event(s) may be omitted (depending on predefined / configured priorities).

[0330] Example 1-1

[0331] In one embodiment of the present disclosure, when transmission for multiple events is performed through the same UL resource, some of the information for some events may be omitted (according to a pre-configured / defined omission method), and / or transmission operations for some event(s) may be omitted (according to a pre-configured / defined event priority / dropping rule or / and a terminal's selection).

[0332] As an example of the present disclosure, when a terminal performs event-based CSI reporting, reporting operations for some or all of the PMI-related information with a large payload size may be omitted. Additionally or alternatively, when a terminal performs event-based CSI reporting, configuration values ​​related to the codebook (e.g., CSI codebook type and / or granularity, etc.) may be changed.

[0333] Additionally or alternatively, when an event-based beam reporting procedure is performed, some of the reported beams (e.g., resource IDs) and / or quality values ​​(e.g., L1-RSRP / SINR) of the corresponding beams may be omitted. For example, only N beam quality values ​​with the best quality value (e.g., N=1) may be omitted, and the remaining beam IDs and / or quality values ​​may be omitted. Similarly, when an event-based reporting procedure related to mobility / radio resource management (RRM) / multi-TRP is performed, IDs / quality values, etc. for some cells / TRPs with low quality values ​​(e.g., RSRP) may be omitted.

[0334] Additionally or alternatively, when a beam failure (BF) / RLF event occurs, i) some of the new beam-related information and / or ii) beam information for some CC(s) (e.g., SCell(s)) may be omitted.

[0335] Additionally or alternatively, when an event occurs that changes the terminal's preferred system settings or / and requests the operation of a characteristic base station, information of a type with low importance or reliability among the types of information related to the event (e.g., information with low reliability, information with a value related to performance improvement due to the setting change below a reference value, etc.) may be (prioritized) omitted.

[0336] Additionally or alternatively, when specific event(s) occur, the terminal may transmit ID information for the specific event(s) to the base station with priority over other information / content related to the event (e.g., CRI / L1-RSRP, RI / PMI / CQI, TDCP (time domain channel property), etc.). That is, (when the payload size is insufficient), the terminal may transmit only ID information for the event that occurred with priority to the base station, and the transmission operation of the remaining information may be omitted.

[0337] As an example of the present disclosure, a terminal may perform a reporting operation after dropping specific event(s) based on priorities / correlation between events. For example, interrelated events (e.g., events with a correlation greater than a certain value) may be configured for the terminal together. If the events occur simultaneously / together, the terminal may report only information on the most significant event(s) among them to the base station.

[0338] For example, assume that a terminal has a beam failure event, a new beam discovery event, and an RLF event configured. If the quality of the serving beam degrades (e.g., the quality value of the serving beam falls below a predefined value), one or more of the beam failure event, new beam discovery event, and RLF event may occur simultaneously. The severity and importance of the RLF event, beam failure event, and new beam discovery event may increase in that order.

[0339] Specifically, assume that the quality value of the serving beam is less than or equal to X1. Since the quality value of the candidate beam may be X2, which is greater than "X1 + threshold", the probability of a new beam discovery event occurring may be high. If there is only one serving beam and the beam quality is continuously poor for a certain period of time (T1) (e.g., below a certain value), the probability of a beam failure event occurring may be high. If the serving beam quality value is continuously poor for a certain period of time (T2) (e.g., T2 > T1), the probability of an RLF event occurring may be high.

[0340] Therefore, in the example described above, if two or more events occur together, the terminal can be set / defined to report to the base station only information related to the event with higher importance / priority among the two or more events.

[0341] As an example of the present disclosure, if some event(s) are dropped (e.g., if reporting operations related to some event(s) are dropped, etc.), the terminal may be defined / configured to report information / IDs regarding the dropped event(s) to the base station. The terminal may (subsequently) transmit ID(s) associated with the event(s) requiring event-related transmission to the base station.

[0342] At this time, the terminal can report the required payload size information for the dropped event(s) to the base station, and the base station can perform subsequent UL resource scheduling based on the reported information. For example, in Example 2 and / or Example 3, the terminal can report all indicator(s) for the event(s) generated through the first resource to the base station. At this time, dropping / omitting can be performed in the second resource according to the set / allocated payload size. Similarly, in Example 3, the indicator(s) for the generated event(s) can be reported from the terminal to the base station through separately encoded information / message, etc. for the dropped event(s).

[0343] As an example of the present disclosure, the inter-event drop rule may be predefined or configured for the terminal by the base station. For example, the inter-event drop rule may be defined / configured / used in one of the following ways:

[0344] - The priority of events for PCell / PSCell is higher than that of events for SCell;

[0345] - The priority of events for the serving cell / TRP beam is higher than the priority of events for the non-serving cell / TRP / beam;

[0346] - The priority of a beam failure event is higher than that of other beam-related events (e.g., a new beam found event);

[0347] - Drop event-related IDs (e.g., event ID, report ID, configuration ID, etc.) in high / low order;

[0348] - Drop events in order of occurrence, either fast or slow;

[0349] - Prioritize dropping information with a high required payload size (interval);

[0350] - High priority in the order of wireless link-related information, beam-related information, and CSI-related information;

[0351] - Priority is determined based on the event type / type (e.g., events of the same type / type have the same priority, and priorities are determined based on rules between different types / types (e.g., the lower the type ID, the higher the priority of the corresponding event / information)); and

[0352] - Priority is determined based on the presence and / or amount of information to be transmitted in addition to the event-related ID (e.g., procedures related to events where only the ID is transmitted are performed with priority, and / or information for events with a small amount of information is transmitted with priority).

[0353] As an example of the present disclosure, when multiple drop rules are applied, the multiple drop rules may be applied sequentially. For example, when determining the priority of each event(s) according to a specific rule (e.g., Rule #1), assume that the priorities of the multiple events are the same. In this case, another rule (e.g., Rule #2) may be applied to determine the priorities of the multiple events.

[0354] According to the above-described rules, the terminal may prioritize reporting information for high-priority events and drop information for event(s) exceeding the maximum payload. Furthermore, the terminal may prioritize reporting high-priority information and then use the remaining payload to compose or / and omit lower-priority information. As another example, the terminal may selectively compose information that can be transmitted within the given payload size among lower-priority information.

[0355] The above-described event-to-event priorities can be used / applied to drop / omit information related to events, as well as to determine the order of information organization (e.g., placing higher priority information in front), and to determine the location of related physical layer signals (e.g., placing higher priority information near / adjacent to DMRS).

[0356] For example, when a terminal reports multiple pieces of event information with different event trigger conditions together to a base station, each piece of event information may be configured in a defined / configured order (according to a priority order among the predefined / configured event information). In this case, it may be defined / regulated that all or part of event information (with low priority and / or large information content) is omitted (if the size of the UL payload / resource allocated to the terminal is insufficient to transmit the entire information). Additionally, it may be regulated / regulated that some event information is configured with only specific information (with a smaller information content).

[0357] In addition to the drop rules described above, the terminal can determine whether to select / drop specific event(s) among events with the same priority. Alternatively, the drop rules may not apply, and the terminal may selectively report information about the event(s) (after determining their importance). In this case, IDs (e.g., event IDs, report IDs, etc.) associated with the currently reported event(s) and / or event(s) excluded from the current report (e.g., those with additional information to report) may be included in the event report information transmitted by the terminal. Accordingly, the base station can identify event drop / omission situations.

[0358] In cases where common UL resources for event(s) are set / allocated for the terminal, as well as cases where separate UL resources are set for the event(s), the method(s) according to embodiment 1-1 can be utilized for multiplexing / dropping between event information / resources.

[0359] For example, if UL resource #1 for event #1 and UL resource #2 for event #2 are set to overlapping symbols or the same slot, and both event #1 and event #2 occur, multiplexing rules (e.g., transmitting both pieces of information using only one of the two UL resources) and / or dropping rules (e.g., performing only one of the two event-based transmissions) for the two event information can be defined.

[0360] When these multiplexing / drop rules are applied, some event(s) and / or some information about the event(s) may be omitted through multiple methods(s) according to Example 1-1. That is, the terminal may multiplex or drop each piece of information according to the methods described above.

[0361] For example, when resources overlap / conflict as described above, the terminal can decide which event(s) to transmit information about first based on priority rules (e.g., a rule that considers an event that occurred first as an event with a higher priority, and applies a different rule if the occurrence times are the same, etc.).

[0362] Example 1-2

[0363] In one embodiment of the present disclosure, when UL resources (some of which) are commonly set for multiple event(s), the transmission method (e.g., repetition / method, UL precoding / rank, transmission format, MCS, UL beam / panel, UL power, etc.) of the corresponding UL resources may be applied differently depending on which event(s) occur. To this end, the UL resource transmission method to be applied depending on the event(s) may be configured / regulated. Additionally, the terminal may be configured / regulated to transmit using other UL resources together with or separately from the UL resources, depending on the event (e.g., specific circumstances of the event).

[0364] Specifically, when Example 1 is applied, there may be differences in reliability, output, etc. of UL transmission required for each event that shares UL resources. For example, among various event-based transmissions related to beams, when the quality of a serving beam (e.g., indicated TCI) is degraded, the UL transmission reliability may be lower than when the quality of a non-serving beam is degraded. This is because, when the UL transmission is transmitted in the direction of the serving beam (e.g., when a joint DL / UL TCI is set / indicated), the quality of the serving beam may be degraded.

[0365] In addition, when CA(carrier aggregation) / DC(dual connectivity) is applied, if the beam quality of PCell / PSCell is degraded, the UL transmission reliability may be lower than if the beam quality of SCell is degraded. Since PUCCH / PRACH is not transmitted for SCell UL in NR system, event-related resources (e.g., primary resource, secondary resource) are more likely to be set to PCell / PScell, so the DL beam quality of PCell / PScell ​​may have a greater impact on the reliability of event transmission-related UL resources than the DL beam quality of SCell.

[0366] In addition, the DL beam / link quality for a cell / TRP for which event-related UL resources are configured may have a greater impact on the reliability of event-related UL transmission than the DL beam / link quality for a cell / TRP for which no UL resources are configured. Here, a cell may be a unit using a physical cell ID or a CC. Whether a specific UL resource is associated with a specific cell / TRP may be distinguished through the cell / TRP ID, but is not limited thereto. Whether a specific UL resource is associated with a specific cell / TRP may be distinguished by a TCI, a QCL RS, a spatial relationship / filter RS, or a resource unit (e.g., a CORESET full index) that receives a PDCCH.

[0367] In case of low reliability of UL transmission (e.g., degradation of serving beam quality for PCell / PSCell, degradation of quality for serving TRP / cell, etc.), it may be stipulated / defined to use / apply a UL resource transmission method with higher reliability (e.g., application of (larger) time domain (TD) / frequency domain (FD) / spatial domain (SD) repetition, application of lower rank (e.g., rank 1), application of lower MCS, feature precoding scheme, (semi-)open loop UL, precoding cycling, etc.), specific beam / panel (e.g., non-failed beam, UL beam for different TRP / cell, multi-beam / panel based repeated transmission or simultaneous transmission), etc.).

[0368] Below, we will describe a procedure for a case where UL resources (some of which are set in common for multiple event(s)) and the transmission method of the UL resources differs depending on which event(s) occur.

[0369] As described above, when certain event(s) corresponding to low reliability of UL transmission occur (e.g., serving beam quality degradation for PCell / PSCell, quality degradation for serving TRP / cell, etc.), at least one of the methods described below can be configured / defined for UL resource transmission commonly configured / allocated for the event:

[0370] - A method of repeatedly transmitting the same information based on TD / SD / FD by increasing the number of repetitions;

[0371] - How to perform UL transmission with non-serving beams / cells / TRPs of good / excellent quality;

[0372] - A method of performing UL transmission by applying a preset / defined (lower) MCS / rank;

[0373] - How to apply specific UL precoding (e.g., spatial diversity, (semi-)open loop UL, precoding cycling);

[0374] - Method of applying multi-TRP / panel / beam simultaneous transmission (e.g., SFN STxMP);

[0375] - How to use a specific transmission / channel format (e.g., sequence detection / modulation); and

[0376] - How to apply UL power boosting.

[0377] However, this is only one example, and other methods may be applied to transmit UL resources commonly set / allocated for events.

[0378] Additionally, when Example 1 is applied, both a method of transmitting the second resource after the base station's response (e.g., confirmation / ACK) to the first resource and a method of applying the second resource even without a response may be applied. In the event that an event(s) corresponding to a case where the reliability of UL transmission is low occurs, a method of transmitting the second resource after the base station's response may be defined / configured to be (mandatory) applied.

[0379] Additionally, the terminal may perform (event-based) transmission operations using separate UL resources instead of, or in addition to, the configured / allocated resources. For example, to achieve higher UL quality, the terminal may be configured / defined to transmit (specific) PRACH resources instead of, or in addition to, the configured / allocated UL resources. Here, the PRACH resources may be non-contention-free PRACH resources or contention-based PRACH resources.

[0380] For example, when using both configured / allocated UL resources and additionally configured / defined resources, the UE can sequentially transmit both resources within adjacent time periods. Furthermore, the UE can first transmit the configured / allocated UL resources, and then, if there is no response from the base station for a certain period of time, transmit the additionally configured / defined resources. For example, the UE can first transmit UCI over PUCCH, and then, if there is no response, perform PRACH-based transmission.

[0381] In addition, when an event(s) corresponding to a case where the reliability of UL transmission is low occurs, signaling (e.g., ACK for UCI / MAC-CE, etc.) related to whether the base station has normally received the event transmission of the terminal may be defined. The terminal may be configured / defined to retransmit the event-based transmission if the signaling of the base station is not normally received (by a promised time or a certain time). The event-based retransmission method described above may be applied only to some event(s) with high importance (or priority). For example, the events to which the event-based retransmission method is applied may be predefined or configured by the base station.

[0382] The transmission method described in Example 1-2 may be configured / defined for each event, or defined for each event type / group. When multiple events corresponding to different transmission methods occur, the terminal may perform a UL transmission operation to which a transmission method / configuration value with higher reliability is applied (e.g., higher power, larger repetition count, lower rank / MCS, transmission with more TRPs / panels / beams).

[0383] When the above-described methods of the present disclosure are applied, the terminal may transmit capability information related to multiple event-based transmissions to the base station. For example, the capability information transmitted by the terminal to the base station may include information on event(s) for which event-based transmission is possible (e.g., indicators), information on the number of events that can be simultaneously supported / transmitted (via common UL resources), information related to multiplexing / dropping / omitting for event transmission when multiple events occur, information related to Embodiment 1-2 for UL resources (e.g., information on a transmission method supported by the terminal, etc.), etc. Here, the information related to multiplexing / dropping / omitting for event transmission may include a function / method related to event transmission supported by the terminal (e.g., multiplexing, dropping and / or omitting techniques, etc.).

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

[0385] FIG. 18 illustrates an example of signaling between a network side and a terminal (UE) in an M-TRP situation to which the examples of the present disclosure described above (e.g., one or more combinations of Embodiment 1, Embodiment 1-1, Embodiment 1-2, or / and detailed embodiments thereof) can be applied.

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

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

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

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

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

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

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

[0393] 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 1-1, and / or Embodiment 1-2.

[0394] Prior to step S110, the terminal may transmit terminal capability information (e.g., capability information related to event-based transmission supported by the terminal) to the base station. For example, capability information related to event-based transmission supported by the terminal may include the total number of event types / timers / counters supported by the terminal, the transmission method applied to each of the multiple events supported by the terminal, etc.

[0395] 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 1-1, and / or Embodiment 1-2) of the present disclosure may be applied.

[0396] 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, etc.) (S125). UL transmission (e.g., event transmission procedure) may perform various detailed procedures (e.g., first resource-based transmission, network response to first resource-based transmission, second resource-based transmission) according to various embodiments of the present disclosure (e.g., Example 1, Example 2, Example 3, etc.). At this time, at least one of the various embodiments of the present disclosure (e.g., Example 1, Example 1-1, and / or Example 1-2) may be applied.

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

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

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

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

[0401] 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 information related to at least one common uplink (UL) resource for multiple events from a base station; and A step of transmitting, by the terminal to the base station, second information related to at least one event occurring within a first time window among the plurality of events based on at least one common UL resource, A method wherein the first time window is based on at least one of a time point of reception of the first information or third information related to the first time window.

2. In paragraph 1, The starting point of the first time window is determined based on the reception point of the first information or the third information, A method wherein the third information comprises at least one of the length of the first time window, the starting point of the first time window, or the period of the first time window.

3. In paragraph 1, A method wherein the first information includes at least one of the number of the at least one common UL resource, the size of the at least one common UL resource, or the type of the at least one common UL resource.

4. In paragraph 1, A method wherein the second information includes at least one of information related to whether the at least one event has occurred, identification information for the at least one event, or performance figures or parameters related to the occurrence of the at least one event.

5. In paragraph 1, The at least one common UL resource includes a first UL resource and a second UL resource, Based on the first UL resource, information related to whether at least one event has occurred and identification information for the at least one event are transmitted to the base station, A method in which, based on the second UL resource, performance figures or parameters related to the occurrence of at least one event are transmitted to the base station.

6. In paragraph 1, wherein said at least one event comprises a first event and a second event, A method in which the priority of the first event is greater than the priority of the second event and the first event and the second event occur simultaneously, and second information related to the second event is dropped by the terminal.

7. In paragraph 6, The first event includes at least one of an event for a primary cell (PCell) or a primary secondary cell (PSCell), an event for a serving cell, or a beam failure event, A method wherein the second event comprises at least one of an event for a secondary cell (SCell), an event for a non-serving cell, or an event related to new beam discovery.

8. In paragraph 6, A method wherein the sum of the sizes of the second information associated with each of the first event and the second event is greater than the size of the payload associated with at least one of the first UL resource or the second UL resource.

9. In paragraph 1, Terminal capability information related to event-based transmission is transmitted by the terminal to the base station, A method wherein the terminal capability information includes at least one of the number of events that can be reported through the at least one common UL resource, a reporting method for information about the at least one event supported by the terminal, or a type of event capable of event-based transmission supported by the terminal.

10. In paragraph 1, At least one of the above event-specific transmission parameters is applied differently, A method wherein the transmission parameters include at least one of a repetition transmission method, uplink precoding or rank, transmission format, modulation and coding scheme (MCS), UL spatial filter, or UL power.

11. In paragraph 1, Setting information related to event-based transmission including the above first information is transmitted from the base station to the terminal, A method wherein the above setting information includes at least one of a priority of each of the plurality of events, a condition related to each of the plurality of events, a type of each of the plurality of events, or a transmission parameter for each of the plurality of events.

12. In paragraph 1, A method in which the occurrence of each of the plurality of events is monitored by the terminal during the first time window.

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 uplink (UL) resource for multiple events from a base station through the one or more transceivers; and Based on the at least one common UL resource, second information related to at least one event occurring within a first time window among the plurality of events is set to be transmitted to the base station through the one or more transceivers, The terminal wherein the first time window is based on at least one of the time of receiving the first information or third information related to the first time window.

14. A step of transmitting first information related to at least one common uplink (UL) resource for multiple events to a terminal by a base station; and A step of receiving, by the base station, from the terminal second information related to at least one event occurring within a first time window among the plurality of events based on at least one common UL resource, A method wherein the first time window is based on at least one of a time point of reception of the first information or third information related to the first time window.

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 uplink (UL) resource for multiple events to a terminal via the one or more transceivers; and Based on the at least one common UL resource, second information related to at least one event occurring within a first time window among the plurality of events is set to be received from the terminal through the one or more transceivers, A base station wherein the first time window is based on at least one of the reception time of the first information or third information related to the first time window.

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