Method and apparatus for UEBR triggering in wireless communication system

Abstract

The present disclosure relates to a method and apparatus for UEBR triggering in a wireless communication system. According to an embodiment of the present disclosure, an operating method of a terminal in a wireless communication system comprises the steps of: receiving first configuration information for beam reporting; detecting an event on the basis of the first configuration information; increasing an event instance counter on the basis of detecting the event; triggering the beam reporting on the basis of the event instance counter reaching a preset value; and resetting the event instance counter on the basis of the event instance counter reaching the preset value.

Description

Method and device for UEBR triggering in a wireless communication system

[0001] The present disclosure relates to initial access in a wireless communication system, and more specifically, to a method and apparatus for triggering a UEBR (user initiated / event-driven beam report).

[0002] Communication networks (e.g., 5G communication networks, 6G communication networks, etc.) are being developed to provide communication services that are improved over existing communication networks (e.g., LTE (long term evolution), LTE-A (advanced), etc.). 5G communication networks (e.g., NR (new radio) communication networks) can support frequency bands above 6 GHz as well as frequency bands below 6 GHz. That is, 5G communication networks can support the FR1 band and / or FR2 band. 5G communication networks can support a wider variety of communication services and scenarios compared to LTE communication networks. For example, usage scenarios for 5G communication networks may include eMBB (enhanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication), mMTC (massive Machine Type Communication), etc.

[0003] 6G communication networks can support a wider variety of communication services and scenarios compared to 5G communication networks. 6G communication networks can meet the requirements for ultra-high performance, ultra-bandwidth, ultra-spatial, ultra-precision, ultra-intelligence, and / or ultra-reliability. 6G communication networks can support a wide range of frequency bands and can be applied to various usage scenarios (e.g., terrestrial communication, non-terrestrial communication, sidelink communication, sensing, etc.).

[0004] Meanwhile, the technology forming the background of the invention is written to enhance understanding of the background of the invention and may include content that is not prior art already known to a person with ordinary knowledge in the field to which this technology belongs.

[0005] The present disclosure may provide a method and apparatus for performing a user-initiated / event-driven beam report (UEBR) operation.

[0006] The present disclosure may provide a method and apparatus for triggering UEBR operation.

[0007] The present disclosure may provide a method and apparatus for counting event instances for triggering UEBR operation.

[0008] The present disclosure may provide a method and apparatus for resetting an event instance counter for triggering UEBR operation.

[0009] The present disclosure may provide a method and apparatus for setting event occurrence conditions to trigger UEBR operation.

[0010] The present disclosure may provide a method and apparatus for setting a time window, time offset, or timer for triggering a UEBR.

[0011] The present disclosure may provide a method and apparatus for retransmitting signaling for UEBR operation.

[0012] The present disclosure may provide a method and apparatus for selecting another resource when a resource conflict occurs in UEBR operation.

[0013] The present disclosure may provide a method and apparatus for notifying a base station of the occurrence of an event in UEBR operation.

[0014] The technical objectives to be achieved in this disclosure are not limited to those mentioned above, and other unmentioned technical problems may be considered by those skilled in the art to which the technical configuration of this disclosure applies, based on the embodiments of this disclosure described below.

[0015] According to one embodiment of the present disclosure, a method of operation of a terminal in a wireless communication system comprises: receiving first setting information for beam reporting; detecting an event based on the first setting information; increasing an event instance counter based on the detection of the event; triggering a beam report based on the event instance counter reaching a preset value; and resetting the event instance counter based on the event instance counter reaching the preset value.

[0016] According to one embodiment of the present disclosure, a method of operating a base station in a wireless communication system comprises: transmitting first setting information for beam reporting; and receiving the beam report based on the first setting information, wherein the beam report is transmitted based on the event instance counter based on the first setting information reaching a preset value, and the event instance counter is reset based on the event instance counter reaching a preset value.

[0017] According to one embodiment of the present disclosure, a terminal in a wireless communication system comprises: at least one transceiver; at least one processor; and at least one memory connected to the at least one processor to be operable and storing instructions that control the terminal to perform operations when executed by the processor, wherein the operations include: receiving first configuration information for beam reporting; detecting an event based on the first configuration information; increasing an event instance counter based on the detection of the event; triggering a beam report based on the event instance counter reaching a preset value; and resetting the event instance counter based on the event instance counter reaching the preset value.

[0018] In a wireless communication system, a base station comprises at least one transceiver; at least one processor; and at least one memory connected to the at least one processor to be operable and storing instructions that control the base station to perform operations when executed by the processor, wherein the operations include: transmitting first configuration information for beam reporting; and receiving the beam report based on the first configuration information, wherein the beam report is transmitted based on an event instance counter based on the first configuration information reaching a preset value, and the event instance counter is reset based on the event instance counter reaching a preset value.

[0019] The proposed technology can perform efficient beam reporting by resetting the event instance counter to trigger the UEBR (user-initiated / event-driven beam report).

[0020] The effects obtainable from the embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by a person skilled in the art to which the technical configuration of the present disclosure applies from the description of the embodiments of the present disclosure below. That is, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by a person skilled in the art from the embodiments of the present disclosure.

[0021] FIG. 1 illustrates a communication system according to an embodiment of the present disclosure.

[0022] FIG. 2 illustrates a block diagram of a communication node according to an embodiment of the present disclosure.

[0023] FIG. 3 illustrates a block diagram of devices performing communication according to one embodiment of the present disclosure.

[0024] FIGS. 4a and 4b illustrate block diagrams of a transmission path and a reception path of a communication node according to an embodiment of the present disclosure.

[0025] FIG. 5 illustrates an example of a system frame in a wireless communication system according to an embodiment of the present disclosure.

[0026] FIG. 6 illustrates an example of a subframe in a wireless communication system according to an embodiment of the present disclosure.

[0027] FIG. 7 illustrates an example of a slot in a wireless communication system according to an embodiment of the present disclosure.

[0028] FIG. 8 illustrates an example of a time-frequency resource in a wireless communication system according to an embodiment of the present disclosure.

[0029] FIG. 9 illustrates an example of a UEBR procedure in Mode A according to one embodiment of the present disclosure.

[0030] FIG. 10 illustrates an example of a UEBR procedure in Mode A according to one embodiment of the present disclosure.

[0031] FIG. 11 illustrates a terminal procedure of UEBR operation according to one embodiment of the present disclosure.

[0032] FIG. 12 illustrates a base station procedure of UEBR operation according to one embodiment of the present disclosure.

[0033] FIG. 13 illustrates an initialization procedure for an event instance count according to one embodiment of the present disclosure.

[0034] FIG. 14 illustrates a PUCCH retransmission procedure according to one embodiment of the present disclosure.

[0035] FIG. 15 illustrates a procedure for notifying whether an event is satisfied according to one embodiment of the present disclosure.

[0036] The present disclosure is capable of various modifications and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present disclosure to specific embodiments and should be understood to include all modifications, equivalents, and substitutions that fall within the spirit and scope of the present disclosure.

[0037] Terms such as "first," "second," etc., may be used to describe various components, but said components should not be limited by said terms. Such terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present disclosure, the first component may be named the second component, and similarly, the second component may be named the first component. The term "and / or" may mean a combination of a plurality of related described items or any of a plurality of related described items.

[0038] In the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B". Additionally, in the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B".

[0039] In the present disclosure, (re)transmission may mean "transmission," "retransmission," or "transmission and retransmission"; (re)setting may mean "setting," "resetting," or "setting and resetting"; (re)connection may mean "connection," "reconnection," or "connection and reconnection"; and (re)connection may mean "connection," "reconnection," or "connection and reconnection".

[0040] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0041] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit this disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, terms such as “comprising” or “having” are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0042] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which this disclosure pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure.

[0043] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. To facilitate overall understanding in describing the present disclosure, the same reference numerals are used for identical components in the drawings, and redundant descriptions of identical components are omitted. Operations according to combinations of embodiments, extensions of embodiments, and / or modifications of embodiments may be performed, as well as the embodiments explicitly described in the present disclosure. The performance of some operations may be omitted, and the order of operations may be changed.

[0044] In the embodiments, even when a method performed at a first communication node among the communication nodes (e.g., transmission or reception of a signal) is described, the corresponding second communication node may perform a method corresponding to the method performed at the first communication node (e.g., reception or transmission of a signal). That is, when the operation of a UE (user equipment) is described, the corresponding base station may perform an operation corresponding to the operation of the UE. Conversely, when the operation of a base station is described, the corresponding UE may perform an operation corresponding to the operation of the base station.

[0045] A base station may be referred to as Node B, evolved Node B, gNode B (next generation node B), gNB, device, apparatus, node, communication node, BTS (base transceiver station), RRH (radio remote head), TRP (transmission reception point), RU (radio unit), RSU (road side unit), radio transceiver, access point, access node, etc. A UE may be referred to as terminal, device, apparatus, node, communication node, end node, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, OBU (on-broad unit), etc.

[0046] In the present disclosure, signaling may be at least one of upper-layer signaling, MAC signaling, or PHY (physical) signaling. A message used for upper-layer signaling may be referred to as an "upper-layer message" or an "upper-layer signaling message." A message used for MAC signaling may be referred to as a "MAC message" or a "MAC signaling message." A message used for PHY signaling may be referred to as a "PHY message" or a "PHY signaling message." Upper-layer signaling may refer to the transmission and reception operations of system information (e.g., MIB (master information block), SIB (system information block)) and / or RRC messages. MAC signaling may refer to the transmission and reception operations of MAC CE (control element). PHY signaling may refer to the transmission and reception operations of control information (e.g., DCI (downlink control information), UCI (uplink control information), SCI (sidelink control information)).

[0047] In the present disclosure, "setting an operation (e.g., a transmission operation)" may mean that "setting information for said operation (e.g., an information element, a parameter)" and / or "information directing the performance of said operation" is signaled. "Setting an information element (e.g., a parameter)" may mean that said information element is signaled. In the present disclosure, "signal and / or channel" may mean a signal, a channel, or "signal and channel," and "signal" may be used to mean "signal and / or channel."

[0048] The communication networks to which the embodiments are applied are not limited to those described below, and the embodiments may be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, the term "communication network" may be used interchangeably with "communication system."

[0049] FIG. 1 illustrates a communication system according to an embodiment of the present disclosure.

[0050] Referring to FIG. 1, the communication system (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Additionally, the communication system (100) may further include a core network (e.g., S-GW (serving-gateway), P-GW (PDN (packet data network)-gateway), MME (mobility management entity)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.

[0051] Multiple communication nodes (110 to 130) can support communication protocols defined in 3GPP (3rd generation partnership project) standards (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.). Multiple communication nodes (110 to 130) can support CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA technology, NOMA (non-orthogonal multiple access) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi-carrier) technology, SDMA (space division multiple access) technology, etc. Each of the multiple communication nodes may have the following structure.

[0052] FIG. 2 illustrates a block diagram of a communication node according to an embodiment of the present disclosure. The structure exemplified in FIG. 2 may be understood as the structure of at least part of a communication node, base station, satellite, or core network entity. The communication node (200) exemplified in FIG. 2 may be a mobile terminal such as a smartphone, tablet PC, or wearable device, but is not limited thereto.

[0053] Referring to FIG. 2, the wireless device (200) may include at least one control unit (210), at least one memory (220), at least one power supply unit (230), at least one transceiver unit (240), at least one input unit (250), at least one output unit (260) and / or at least one antenna (270).

[0054] The control unit (210) can control the memory (220) and / or the transmission / reception unit (240) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this disclosure. The memory (220) may be connected to the control unit (210) and may store various information related to the operation of the control unit (210). For example, the memory (220) may store software code including instructions for performing some or all of the controls controlled by the control unit (210) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this disclosure. The configuration of the memory is not limited in a particular way. For example, it may be configured as at least one of read-only memory (ROM) and random access memory (RAM).

[0055] At least one control unit (210) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The descriptions, functions, procedures, proposals, methods, and / or flowcharts of operations disclosed in this disclosure may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions. Here, the firmware or software may execute other programs stored in memory (220), such as an OS. The control unit (210) may be implemented to support differently weighted beamforming or directional routing operations to effectively control the outgoing signal from at least one antenna (270) to a desired direction.

[0056] Additionally, at least one control unit (210) may be coupled with a backhaul or network interface. The wireless device (200) may communicate with other wireless devices through the backhaul or network interface. The control unit (210) may include at least one processor. The processor may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the methods according to embodiments of the present disclosure are performed.

[0057] At least one transceiver (240) may be connected to a control unit (210) and may transmit and / or receive a wireless signal through at least one antenna (270). The transceiver (240) may include a transmitter and / or a receiver. At least one transceiver (240) may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or operation flowcharts of the present disclosure to at least one other device. For example, at least one transceiver (240) may be connected to at least one control unit (210) and may transmit and receive wireless signals. Additionally, at least one control unit (210) may control at least one transceiver (240) to transmit user data, control information, or wireless signals to at least one other device. At least one transmitter (240) may receive a signal transmitted by another wireless device from at least one antenna (270). Additionally, at least one transceiver (24) can down-convert or up-convert the received signal to generate a baseband signal. At least one antenna (270) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0058] The input unit (250) can acquire information such as user input, video, and audio, and may include various input means such as various mechanical / electronic input means, cameras, and microphones. The output unit (260) is intended to provide information to a user by generating output related to sight, hearing, or touch, and may include a display, speaker, vibration module, etc. The wireless device (200) supplies power through the power unit (230), and the power unit (230) may include a wired / wireless charging circuit, battery, etc.

[0059] A more detailed example of the structure of the control unit (210) and / or the transceiver unit (240) is shown in FIG. 3. FIG. 3 illustrates a block diagram of devices performing communication according to an embodiment of the present disclosure. FIG. 3 illustrates the structure of a first communication node (300a) and a second communication node (300b) that transmit and / or receive a signal. In FIG. 3, each of the first communication node (300a) and the second communication node (300b) may be a base station or a UE.

[0060] Referring to FIG. 3, the first communication node (300a) and the second communication node (300b) may each be a base station or a UE. The first communication node (300a) may transmit a signal to the second communication node (300b). A transmission processor (311) included in the first communication node (300a) may receive data (e.g., a data unit) from a data source (310). The transmission processor (311) may receive control information from a controller (316). The control information may include at least one of system information, RRC setting information (e.g., information set by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

[0061] The transmitting processor (311) can generate data symbol(s) by performing processing operations on data (e.g., encoding operations, symbol mapping operations, etc.). The transmitting processor (311) can generate control symbol(s) by performing processing operations on control information (e.g., encoding operations, symbol mapping operations, etc.). Additionally, the transmitting processor (311) can generate synchronization / reference symbol(s) for synchronization signals and / or reference signals.

[0062] The Tx MIMO processor (312) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or synchronization / reference symbol(s). The output of the Tx MIMO processor (312) (e.g., a symbol stream) can be provided to modulators (MODs) included in transceivers (313a to 313t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulated symbols and perform additional processing operations on the modulated symbols (e.g., analog conversion operations, amplification operations, filtering operations, up-conversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (313a to 313t) can be transmitted through antennas (314a to 314t).

[0063] Signals transmitted by the first communication node (300a) can be received at the antennas (364a to 364r) of the second communication node (300b). Signals received at the antennas (364a to 364r) can be provided to demodulators (DEMODs) included in the transceivers (363a to 363r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering, amplification, down-conversion, digital conversion). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (362) can perform MIMO detection operations on the symbols. The receiving processor (361) can perform processing operations on the symbols (e.g., deinterleaving, decoding). The output of the receiving processor (361) can be provided to the data sink (360) and the controller (366). For example, data can be provided to the data sink (360), and control information can be provided to the controller (366).

[0064] Meanwhile, the second communication node (300b) can transmit a signal to the first communication node (300a). The transmission processor (368) included in the second communication node (300b) can receive data (e.g., a data unit) from a data source (367) and can generate data symbol(s) by performing a processing operation on the data. The transmission processor (368) can receive control information from a controller (366) and can generate control symbol(s) by performing a processing operation on the control information. Additionally, the transmission processor (368) can generate reference symbol(s) by performing a processing operation on a reference signal.

[0065] The Tx MIMO processor (369) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or reference symbol(s). The output of the Tx MIMO processor (369) (e.g., a symbol stream) can be provided to modulators (MODs) included in the transceivers (363a to 363t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulated symbols and perform additional processing operations on the modulated symbols (e.g., analog conversion operations, amplification operations, filtering operations, up-conversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (363a to 363t) can be transmitted through the antennas (364a to 364t).

[0066] Signals transmitted by the second communication node (300b) can be received at the antennas (314a to 314r) of the first communication node (300a). Signals received at the antennas (314a to 314r) can be provided to demodulators (DEMODs) included in the transceivers (313a to 313r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering operation, amplification operation, down-conversion operation, digital conversion operation). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (320) can perform MIMO detection operations on the symbols. The receiving processor (319) can perform processing operations on the symbols (e.g., deinterleaving operation, decoding operation). The output of the receiving processor (319) can be provided to the data sink (318) and the controller (316). For example, data can be provided to the data sink (318), and control information can be provided to the controller (316).

[0067] The memories (315 and 365) may store data, control information, and / or program code. The scheduler (317) may perform scheduling operations for communication. The processors (311, 312, 319, 361, 368, 369) and controllers (316, 366) shown in FIG. 3 may be the processor (210) shown in FIG. 2 and may be used to perform the methods described in this disclosure.

[0068] FIGS. 4a and 4b illustrate block diagrams of a transmission path and a reception path of a communication node according to an embodiment of the present disclosure.

[0069] Referring to FIGS. 4a and 4b, a transmission path (410) may be implemented at a communication node that transmits a signal, and a reception path (420) may be implemented at a communication node that receives a signal. The transmission path (410) may include a channel coding and modulation block (411), an S-to-P (serial-to-parallel) block (412), an N IFFT (Inverse Fast Fourier Transform) block (413), a P-to-S (parallel-to-serial) block (414), a CP (cyclic prefix) addition block (415), and an UC (up-converter) (UC) (416). The reception path (420) may include a DC (down-converter) (421), a CP removal block (422), an S-to-P block (423), an N FFT block (424), a P-to-S block (425), and a channel decoding and demodulation block (426). Here, N can be a natural number.

[0070] Information bits in the transmission path (410) can be input to the channel coding and modulation block (411). The channel coding and modulation block (411) can perform coding operations (e.g., LDPC (low-density parity check) coding operations, polar coding operations, etc.) and modulation operations (e.g., QPSK (Quadrature Phase Shift Keying), QAM (Quadrature Amplitude Modulation), etc.) on the information bits. The output of the channel coding and modulation block (411) may be a sequence of modulation symbols.

[0071] The S-to-P block (412) can convert modulated symbols in the frequency domain into parallel symbol streams to generate N parallel symbol streams. N can be the IFFT size or the FFT size. The N IFFT block (413) can generate signals in the time domain by performing an IFFT operation on the N parallel symbol streams. The P-to-S block (414) can convert the output of the N IFFT block (413) (e.g., parallel signals) into a serial signal to generate a serial signal.

[0072] The CP addition block (415) can insert CP into the signal. The UC (416) can up-convert the frequency of the output of the CP addition block (415) to an RF (radio frequency) frequency. Additionally, the output of the CP addition block (415) can be filtered in the baseband before up-conversion.

[0073] A signal transmitted from the transmission path (410) can be input to the reception path (420). The operation in the reception path (420) may be the inverse operation of the operation in the transmission path (410). The DC (421) may down-convert the frequency of the received signal to a baseband frequency. The CP removal block (422) may remove CP from the signal. The output of the CP removal block (422) may be a serial signal. The S-to-P block (423) may convert the serial signal into parallel signals. The NFFT block (424) may generate N parallel signals by performing an FFT algorithm. The P-to-S block (425) may convert the parallel signals into a sequence of modulation symbols. The channel decoding and demodulation block (426) may perform a demodulation operation on the modulation symbols and restore data by performing a decoding operation on the result of the demodulation operation.

[0074] In FIGS. 4a and 4b, Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. In FIGS. 4a and 4b, each of the blocks (e.g., components) may be implemented by at least one of hardware, software, or firmware. For example, in FIGS. 4a and 4b, some blocks may be implemented by software, and the remaining blocks may be implemented by hardware or a "combination of hardware and software." In FIGS. 4a and 4b, one block may be subdivided into multiple blocks, multiple blocks may be integrated into one block, some blocks may be omitted, and blocks supporting other functions may be added.

[0075] FIG. 5 illustrates an example of a system frame in a wireless communication system according to an embodiment of the present disclosure.

[0076] Referring to FIG. 5, time resources in a communication system can be divided into frames. For example, system frames can be set consecutively in the time domain of the communication system. The length of a system frame can be 10 ms (millisecond). The system frame number (SFN) can be set from #0 to #1023. In this case, 1024 system frames can be repeated in the time domain of the communication system. For example, the SFN of a system frame after system frame #1023 can be #0.

[0077] A single system frame may contain two half frames. The length of a single half frame may be 5ms. A half frame located at the beginning of the system frame may be referred to as "Half Frame #0", and a half frame located at the end of the system frame may be referred to as "Half Frame #1". A system frame may contain 10 subframes. The length of a single subframe may be 1ms. Within a single system frame, the 10 subframes may be referred to as "Subframe #0-9".

[0078] FIG. 6 illustrates an example of a subframe in a wireless communication system according to an embodiment of the present disclosure.

[0079] Referring to FIG. 6, one subframe may contain n slots, where n is a natural number. Thus, one subframe may consist of one or more slots.

[0080] FIG. 7 illustrates an example of a slot in a wireless communication system according to an embodiment of the present disclosure.

[0081] Referring to FIG. 7, a slot may contain one or more symbols. A slot illustrated in FIG. 7 may contain 14 symbols. The length of the slot may vary depending on the number of symbols included in the slot and the length of the symbols. Alternatively, the length of the slot may vary depending on the numerology.

[0082] Numerals applied to physical signals and channels in a communication system may be variable. Numerals may be variable to meet various technical requirements of the communication system. In a communication system where CP (cyclic prefix) based OFDM waveform technology is applied, numerals may include subcarrier spacing and CP length (or CP type). Table 1 may be an example of a method for configuring numerals for a CP-OFDM based communication system. Depending on the frequency band in which the communication system operates, at least some of the numerals in Table 1 may be supported. Additionally, numerals not listed in Table 1 may be further supported in the communication system.

[0083] Subcarrier spacing 15kHz 30kHz 60kHz 120kHz 240kHz 480kHz OFDM symbol length [ ]66.733.316.78.34.22.1CP Length [ ] 4.762.381.190.600.300.151ms OFDM symbol count 142856112224448

[0084]

[0085] When the subcarrier spacing is 15 kHz (e.g., (=0), the slot length can be 1ms. In this case, one system frame can contain 10 slots. When the subcarrier spacing is 30kHz (e.g., =1), the length of the slot can be 0.5ms. In this case, one system frame can contain 20 slots.

[0086] When the subcarrier spacing is 60 kHz (for example, (=2), the slot length can be 0.25ms. In this case, one system frame can contain 40 slots. When the subcarrier spacing is 120kHz (e.g., =3), the slot length can be 0.125ms. In this case, one system frame can contain 80 slots. When the subcarrier spacing is 240kHz (e.g., =4), the length of the slot can be 0.0625ms. In this case, one system frame can contain 160 slots.

[0087] These frame structures can be configured in various ways. For example, the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe in the numeral can be configured as shown in Table 2 below.

[0088] 014101114202214404314808414160165143203261464064

[0089]

[0090] This frame structure is not limited to a specific method. Therefore, unlike Table 2 above, other numerals may be configured or additional numerals may be supported.

[0091] FIG. 8 illustrates an example of a time-frequency resource in a wireless communication system according to an embodiment of the present disclosure.

[0092] Referring to FIG. 8, a resource consisting of one symbol (e.g., an OFDM symbol) in the time domain and one subcarrier in the frequency domain can be defined as a "RE (resource element)." A resource consisting of one OFDM symbol in the time domain and K subcarriers in the frequency domain can be defined as a "REG (resource element group)." A REG can include K REs. A REG can be used as the basic unit of resource allocation in the frequency domain. K can be a natural number. For example, K can be 12. N can be a natural number. In the slot illustrated in FIG. 7, N can be 14. N OFDM symbols can be used as the basic unit of resource allocation in the time domain.

[0093] In the present disclosure, RB may mean a common RB (CRB). Alternatively, RB may mean a PRB or a virtual RB (VRB). In a communication system, a CRB may mean an RB that constitutes a set of consecutive RBs (e.g., a common RB grid) based on a reference frequency (e.g., point A). A carrier and / or bandwidth portion may be placed on the common RB grid. That is, the carrier and / or bandwidth portion may be composed of CRB(s). An RB or CRB constituting the bandwidth portion may be referred to as a PRB, and within the bandwidth portion, a CRB index may be appropriately converted to a PRB index.

[0094] Downlink data may be transmitted via PDSCH. A base station may transmit configuration information of the PDSCH (e.g., scheduling information) to a terminal via PDCCH. A terminal may obtain the configuration information of the PDSCH by receiving the PDCCH (e.g., downlink control information (DCI)). For example, the configuration information of the PDSCH may include a modulation coding scheme (MCS) used for transmitting and receiving the PDSCH, time resource information of the PDSCH, frequency resource information of the PDSCH, feedback resource information for the PDSCH, etc. PDSCH may refer to a radio resource where downlink data is transmitted and received. Alternatively, PDSCH may refer to the downlink data itself. PDCCH may refer to a radio resource where downlink control information (e.g., DCI) is transmitted and received. Alternatively, PDCCH may refer to the downlink control information itself.

[0095] The terminal may perform a monitoring operation for the PDCCH to receive the PDSCH transmitted from the base station. The base station may notify the terminal of configuration information for the monitoring operation of the PDCCH using a higher-layer message (e.g., a radio resource control (RRC) message). The configuration information for the monitoring operation of the PDCCH may include CORESET (control resource set) information and search space information.

[0096] CORESET information may include PDCCH DMRS (demodulation reference signal) information, PDCCH precoding information, PDCCH occasion information, etc. The PDCCH DMRS may be a DMRS used to demodulate the PDCCH. A PDCCH occasion may be an area where the PDCCH can exist. That is, a PDCCH occasion may be an area where the DCI can be transmitted. A PDCCH occasion may be referred to as a PDCCH candidate. PDCCH occasion information may include time resource information and frequency resource information of the PDCCH occasion. In the time domain, the length of the PDCCH occasion may be indicated in units of symbols. In the frequency domain, the size of the PDCCH occasion may be indicated in units of RBs (e.g., units of physical resource block (PRB) or common resource block (CRB)).

[0097] The search space information may include a CORESET ID (identifier) ​​associated with the search space, the period of PDCCH monitoring, and / or an offset. The period and offset of PDCCH monitoring may each be specified in slot units. Additionally, the search space information may further include the index of the symbol where the PDCCH monitoring operation begins.

[0098] A base station may configure a Bandwidth Part (BWP) for downlink communication. BWPs may be configured differently for each terminal. The base station may notify the terminal of the BWP configuration information using upper-layer signaling. Upper-layer signaling may refer to "transmission operations of system information" and / or "transmission operations of Radio Resource Control (RRC) messages." The number of BWPs configured for a single terminal may be one or more. The terminal may receive BWP configuration information from the base station and identify the BWP(s) configured by the base station based on the BWP configuration information. If multiple BWPs are configured for downlink communication, the base station may activate one or more of the multiple BWPs. The base station may transmit the configuration information of the activated BWP(s) to the terminal using at least one of upper-layer signaling, a Medium Access Control (MAC) Control Element (CE), or a DCI. The base station may perform downlink communication using the activated BWP(s). The terminal can identify the activated BWP(s) by receiving configuration information of the activated BWP(s) from the base station, and can perform a downlink reception operation on the activated BWP(s).

[0099] The structure of the resources for communication described with reference to FIGS. 5 through 8 is described as an example. A wireless communication system according to an embodiment of the present disclosure may adopt a different frame structure, a different slot structure, and / or a different symbol structure, and may use resource units with names other than frame, slot, and / or symbol. Here, a difference in structure may be understood as a difference in the numerator applied to the resource unit or a difference in the hierarchical structure. In addition, although described on the premise of an OFDM waveform, it is also possible to use waveforms other than OFDM.

[0100] ISAC (integrated sensing and communication) technology

[0101] ISAC is a technology that can simultaneously achieve maximum spectrum efficiency and reduce hardware costs by combining sensing and communication functions to be realized on a single integrated platform. ISAC is attracting attention as one of the key element technologies of 6G systems.

[0102] The ISAC system is divided into stages based on the level of integration between sensing and communication functions. In the initial integration stage, both functions share the same physical location (site), but frequency resources and hardware can be operated independently. In subsequent advanced integration stages, sensing and communication share the same frequency band and hardware platform, which can significantly improve the efficiency of system resource utilization and the level of integration. This resource-sharing structure is implemented by integrating sensing functions into existing communication infrastructure without the need for additional equipment, thereby enabling real-time environmental awareness and data collection. Consequently, various benefits are expected, including minimized redundant resource usage, reduced operating costs, decreased system complexity, and improved service quality.

[0103] The ultimate technical goal of ISAC is the reuse of waveforms and signals. In the waveform reuse phase, simultaneous data communication and environmental sensing are possible without additional spectrum resources by utilizing the same waveform for both communication and sensing. In the signal reuse phase, transmitted signals intended for communication are reused for sensing purposes, thereby minimizing system overhead and energy consumption while maximizing resource efficiency.

[0104] In particular, 6G systems are closely integrated with ISAC technology in the following aspects. First, regarding the enhancement of spatial precision, 6G aims to provide sub-centimeter positional accuracy through high-resolution sensing capabilities utilizing the mmWave / THz band, which is one of ISAC's core competencies. In terms of intelligent network operations, ISAC-based environmental awareness information is utilized for network resource allocation, link adaptation, and beamforming control, enabling intelligent autonomous network operations. Regarding service convergence, the simultaneous provision of sensing and communication is essential for major 6G application services such as autonomous driving, digital twins, and extended reality (XR), and ISAC can provide the key means to achieve this. In terms of energy and cost efficiency, 6G places emphasis on sustainability and efficiency, and ISAC's signal and hardware reuse structure directly meets these requirements. In conclusion, ISAC is establishing itself as a core technology for achieving functional scalability and infrastructure efficiency in 6G systems; accordingly, active theoretical and experimental research is underway in academia as well as in the industry for commercialization. ISAC technology is expected to serve as the foundation for realizing intelligent networks that combine communication and environmental awareness in the 6G era.

[0105] Various use cases for ISAC technology are being discussed. ISAC technology is recognized as having high potential for application, particularly in Unmanned Aerial Vehicles (UAVs) and industrial automation environments. Representative examples include drone tracking and positioning, real-time positioning of autonomous mobile robots, collision avoidance, and environmental monitoring for autonomous driving. These use cases require high-precision localization and dynamic object detection, demonstrating the potential to efficiently integrate sensing functions onto existing communication infrastructure through ISAC technology.

[0106] Furthermore, the application of ISAC technology in areas of daily life and public services, such as healthcare, transportation, and consumer services, is discussed. In the healthcare sector, contactless sleep monitoring, health monitoring, and sensing-assisted accessibility services are included. In the transportation sector, use cases applicable to V2X-based Intelligent Transportation Systems (ITS), such as surrounding object detection, intersection monitoring, blind spot detection, and parking space detection, are discussed. In addition, services aimed at enhancing next-generation consumer experiences, such as gesture recognition-based interaction, sports movement monitoring, and XR-based immersive streaming, are also mentioned.

[0107] Finally, environmental monitoring and security are also discussed as application areas for ISAC technology. Representative applications include real-time environmental detection based on smart cities, such as rainfall detection and urban flood monitoring, as well as intrusion detection systems in smart homes and public infrastructure. In particular, intrusion detection near critical infrastructure, such as power grids, and pedestrian and animal intrusion detection on highways demonstrate the feasibility of utilizing ISAC to ensure public safety. Furthermore, advanced application methods, such as sensor group formation that configures multiple sensor nodes to perform joint detection functions, are also being discussed.

[0108] The various sensing methods described above can be applied to devices such as base stations and terminals. Devices that perform transmission and reception operations for sensing may be base stations or terminals, and accordingly, a total of six sensing modes can be defined as follows.

[0109] [Mode #1] TRP monostatic: The same base station (or transmission point) acts as both the transmitter and receiver for sensing.

[0110] [Mode #2) UE monostatic: The same terminal acts as both the transmitter and receiver for sensing.

[0111] [Mode #3] TRP-TRP bistatic: Different base stations or transmission points each perform the roles of transmitter and receiver for sensing.

[0112] [Mode #4] UE-UE bistatic: Different terminals each perform the roles of transmitter and receiver for sensing.

[0113] [Mode #5] TRP-UE bistatic: The base station acts as the transmitter for sensing, and the terminal acts as the receiver for sensing.

[0114] [Mode #6] UE-TRP bistatic: The terminal acts as the transmitter for sensing and the base station acts as the receiver for sensing.

[0115] In the following, procedures for performing conditional beam reporting operations are described. Conditional beam reporting operations may be referred to as UEBR (UE-initiated / event driven beam reporting), UE_BR, or UEIBR operations. In the following description, the base station may be referred to as gNB, eNB, NB, network, or NW. The terminal may be referred to as UE.

[0116] In the present disclosure, the operation of performing beam reporting when the UE satisfies a triggering condition set by the gNB may be referred to as UE-initiated / event-driven beam reporting (UEBR). Here, the triggering condition of the UEBR may be referred to as an event. The UEBR operation may be performed based on the method illustrated in FIGS. 9 and 10.

[0117] FIG. 9 illustrates an example of a UEBR procedure in Mode A according to one embodiment of the present disclosure. FIG. 10 illustrates an example of a UEBR procedure in Mode A according to one embodiment of the present disclosure. In other words, in the present disclosure, the method of FIG. 9 may be expressed or referred to as Mode A, and the method of FIG. 10 may be expressed or referred to as Mode B.

[0118] For UEBR operation, the gNB can configure specific events, which are triggering conditions for UEBR, to the terminal using at least one or more combinations of higher layer signaling such as RRC (radio resource control) and SIB (system information block) or low layer signaling such as MAC-CE and DCI. Additionally, these events may be configured by association with at least one of a specific reference signal (RS) that the UE must measure for UEBR execution or a specific PUCCH resource to be used for the 1st PUCCH in UEBR operation. In the case of Mode B, the PUCCH resource configuration information may be configured by association with a predefined specific PUCCH resource to be used as the 2nd uplink (UL) channel. That is, the CSI resource / reporting configuration information required for UEBR may be configured based on or associated with configuration information that includes at least one of a specific RS set, event, PUCCH resource, or predefined PUSCH resource (e.g., for Mode B).

[0119] For convenience of explanation, the PUCCH resource configuration RRC parameter for the UEBR is referred to as firstPUCCHResourceConfig-UEBR in this disclosure. The RRC parameter may include configuration information regarding the PUCCH resources used for the UEBR. Additionally, it may include all or part of the event configuration information for the UEBR, or be associated with the event configuration information. In the case of Mode B, the firstPUCCHResourceConfig-UEBR may include all or part of the PUCCH resource information, or be associated with such information. Furthermore, the firstPUCCHResourceConfig-UEBR may be configured in association with RS configuration information and CSI resource / report configuration information for the UEBR. The aforementioned configuration information can be set by the gNB using at least one or more combinations of upper-layer signaling such as RRC and SIB, or lower-layer signaling such as MAC-CE and DCI, prior to the time of the 1st PUCCH transmission as shown in FIGS. 9 and 10. Subsequently, when the set event is satisfied, the UEBR operation is triggered.

[0120] In the Mode A method of Fig. 9, the 1st PUCCH (e.g., Signaling A1 in Fig. 9) is a PUCCH requesting the allocation of a 2nd UL channel for UE-BR execution. Subsequently, the gNB can allocate a UL channel to be used for UEBR via the DCI (e.g., Signaling A2 in Fig. 9). The UE performs UEBR using the corresponding 2nd UL channel (e.g., Signaling A3 in Fig. 9). In other words, the UE 2 ndBeam reporting can be performed through a UL channel. Herein, the 2nd UL channel may include at least one of PUCCH or PUSCH. In the following, the operation of transmitting or receiving a signal, information, data, or report using a channel such as PUCCH or PUSCH, or the operation of the channel being transmitted or received, may be understood as the operation of transmitting or receiving a signal, information, data, or report using or on the resources allocated for the channel such as PUCCH or PUSCH.

[0121] In the Mode B method of Fig. 10, the 1st PUCCH (e.g., signaling B1 in Fig. 10) is transmitted to notify the gNB that the UE intends to use the allocated or defined 2nd UL channel for UEBR execution. Subsequently, UEBR is executed using the allocated or defined 2nd UL channel (e.g., signaling B2 in Fig. 10). In other words, the terminal 2 nd Beam reporting can be performed through the UL channel. Here, the 2nd UL channel may include at least one of PUCCH or PUSCH.

[0122] For convenience of explanation, PUSCH is described below as an example of a 2nd UL channel. However, the contents of the present disclosure may be applied in a simple, modified, extended, or combined form even when the 2nd UL channel is PUCCH.

[0123] PUCCH resources for the UEBR can be configured and operated as dedicated resources, separate from PUCCH resources based on existing resource allocation methods. Here, firstPUCCHResourceConfig-UEBR may be operated as dedicated PUCCH configuration information for Mode A and Mode B, or as a single PUCCH configuration information without distinction between modes. If dedicated PUCCH resources are configured for each mode of the UEBR, for the sake of convenience of explanation, the PUCCH configuration information for Mode A may be referred to as firstPUCCHResourceConfig-ModeA-UEBR, and the PUCCH configuration information for Mode B may be referred to as firstPUCCHResourceConfig-ModeB-UEBR.

[0124]

[0125] In the following, procedures for performing UBER operations are described. These operations may be performed in combination with the embodiments described below. Alternatively, some or all of the operations may be replaced by the embodiments described below.

[0126]

[0127] FIG. 11 illustrates a terminal procedure of UEBR operation according to one embodiment of the present disclosure. FIG. 11 illustrates a procedure performed by a terminal.

[0128] Referring to FIG. 11, in step S1101, the terminal receives configuration information from the base station. The configuration information may be received by at least one of RRC signaling, MAC CE, or DCI. The configuration information may include information about a reference signal, information about an event, and information related to a resource. Here, the reference signal may include CSI-RS. The information about the event may include the type of event or a threshold value based on the type of event. For example, the type of event may include at least one of Event #1, Event #2, or Event #3.

[0129] In step S1103, the terminal counts event instances. In other words, the terminal increments the counter of event instances. Here, the counter of event instances may be incremented when an event occurs. For example, if Event 1 is defined as the current beam quality being lower than a threshold, the event instance may be incremented whenever the measured beam quality is lower than the threshold. For example, the terminal may count event instances for each of at least one configured event. Here, the operation of increasing or decreasing the count of event instances may be referred to as event instance counting or the operation of the event instance counter. Event instances may be measured and counted during a time interval, a time window, or the time during which a timer operates.

[0130] In step S1105, the terminal resets the event instance counter. For example, the terminal may return the event instance count to 0 or a preset value. The reset may be performed upon the satisfaction of a condition. For example, the event instance count may be reset based on a change in a setting related to the beam. As another example, the event instance count may be reset when the event instance count reaches a preset value. If the condition is not satisfied, step S1105 may not be performed.

[0131] In step S1107, the terminal performs a UEBR operation based on an event instance counter. For example, the terminal may perform a UEBR operation when the count of event instances reaches a predefined value. The UEBR operation may be referred to as an operation for beam reporting. The operation for beam reporting may include an operation based on a UEBR mode. For example, the operation for beam reporting may include at least one of an operation based on Mode A or an operation based on Mode B. The terminal may perform beam reporting based on resources set by configuration information or resources allocated based on DCI.

[0132]

[0133]

[0134] FIG. 12 illustrates a base station procedure of UEBR operation according to one embodiment of the present disclosure. FIG. 12 illustrates a procedure performed by a base station.

[0135] Referring to FIG. 12, in step S1201, the base station transmits first configuration information to the terminal. The first configuration information may be transmitted by at least one of RRC signaling, MAC CE, or DCI. The first configuration information may include information about a reference signal, information about an event, and information related to a resource. Here, the reference signal may include CSI-RS. The information about the event may include the type of event or a threshold value based on the type of event. For example, the type of event may include at least one of Event 1, Event 2, or Event 7. Here, each of Event 1, Event 2, or Event 7 may include one of Event #1, Event #2, or Event #3, which will be described below.

[0136] In step S1203, the base station transmits second configuration information to the terminal. The second configuration information may be transmitted via at least one of RRC signaling, MAC CE, or DCI. The second configuration information may include at least one of information regarding an event or information regarding a reference signal. The information regarding an event or the information regarding a reference signal included in the second configuration information may differ from the first configuration information. In other words, the base station may use the second configuration information to reset the terminal or change the settings. The second configuration information may be referred to as a reset message.

[0137] In step S1205, the base station receives signaling according to the operation mode. Here, the signaling according to the operation mode may include a resource request message for beam reporting based on Mode A or a beam reporting notification based on Mode B. The signaling according to the operation mode may be received via PUCCH. Here, the PUCCH resource for signaling may be a resource indicated by information related to the resource included in the configuration information. The PUCCH resource may include a resource for Mode A, a resource for Mode B, or a dedicated resource for UEBR operation common to the modes. If a resource request message based on Mode A is received, the base station may allocate a resource for beam reporting to the terminal. Terminal allocation may be performed using DCI. For example, the base station may transmit a DCI indicating a resource for beam reporting to the terminal.

[0138] In step S1207, the base station receives a beam report. The beam report may be received based on resources allocated by the base station using DCI or resources pre-configured by the base station using configuration information. In other words, the beam report may be received based on the terminal's operating mode. For example, if a resource request message based on Mode A is received, the base station may receive a beam report based on resources allocated using DCI. As another example, if a resource request message based on Mode B is received, the base station may receive a beam report based on resources pre-configured using configuration information.

[0139]

[0140] In the procedure of FIGS. 11 and 12, some steps may be omitted or repeated. For example, step S1203 may be omitted. In other words, the base station may not change or reset the already set information. As another example, the base station may change or reset the set information repeatedly.

[0141]

[0142] Detailed embodiments for performing UBER operations are described below. For example, the following embodiments may include an operation for a terminal to reset an event instance counter. That is, the following embodiments may include conditions for resetting an event instance counter. The embodiments described below may be performed as part of the aforementioned procedure. Each embodiment may be performed alone, or alternatively, in combination with other embodiments or other methods.

[0143]

[0144] Example #1

[0145] Event satisfaction is determined when instances satisfying the configured event occur a certain number of times or more; in this case, the event is considered to have occurred, and UEBR triggering is performed. In other words, UEBR may be triggered if the number of instances satisfying the configured event exceeds a set value. Here, when the counting of instances satisfying the event is referred to as event instance counting, the following methods may be applied to manage the initialization and reset of the event instance counting.

[0146] For convenience of explanation in the present invention, three examples of events that can be set for UEBR are defined as follows. The event names below are examples only, and the events described below may be referred to or set by other names.

[0147] Event #1: When the current beam quality is worse than a specific threshold

[0148] Event #2: When there is at least one new beam with better beam quality than the beam currently in use

[0149] Event #3: If there is at least one new beam with a better beam quality than the reference signal (RS) associated with the Kth best quality TCI state among the activated TCI states

[0150] In addition, for Event #1, the event may be deemed satisfied if the quality measurements for the RSs associated with the current beam's TCI state are measured to be worse than a specific threshold M or more times.

[0151] For Event #2, satisfaction is determined by measuring instances where the quality of each new beam is measured to be better than the currently used beam; if at least one new beam is measured to be better than the current beam M times or more, the terminal determines that the event is satisfied and triggers the UEBR. For Event #3, satisfaction is determined by measuring that the quality of the new beam is measured to be better than the beam transmitting the RS associated with the Kth best quality TCI state among the activated TCI states M times or more, the terminal determines that the event is satisfied and triggers the UEBR.

[0152] The setting value M for the above events #1, #2, or #3 may be set to be the same or different and operated. For convenience of explanation, the present invention is described based on a common variable named M.

[0153] Furthermore, the M value set for a single event may be updated based on specific conditions. Additionally, the M value set for a single event by the gNB may be changed to a different value. Furthermore, multiple M values ​​may be set for a single event, and a specific M value may subsequently be indicated by the gNB. The settings for the above M values ​​may be included in UEBR-related configuration information. The above M values ​​may be set and changed using one or more combinations of upper-layer signaling such as RRC or lower-layer signaling such as MAC-CE and DCI.

[0154]

[0155] Method #1: Depending on the configured event, the condition for initializing event instance counting and the target of the event instance counting to be initialized may change.

[0156] In the case of Event #1, if the number of times the quality of the current beam is measured and found to be lower than a specific threshold satisfies M, the UE can reset the event instance count for all beams. In other words, if the beam quality is measured to be lower than the threshold M times, the beam's event instance count can be reset. That is, when resetting the event instance count, the value of M for the current beam can be initialized to 0.

[0157] In the case of Events #2 and #3, if a new beam occurs where the event instance count satisfies M, the UE may reset the event instance count for all beams. That is, when the event instance count is reset, the event instance count for all beams may be reset to 0. The above-mentioned "all beams" may include all beams subject to measurement, excluding the beam currently in use. An event instance can be counted for each beam. In other words, an event instance counter can operate for each beam. If the event instance counter of one of the beams reaches a predefined value, an event may be triggered.

[0158]

[0159] Method #2: Event instance counting can be initialized based on the triggering time of the UEBR or subsequent actions. For example, the UE can initialize event instance counting after the UEBR is triggered, that is, at the moment a specific time window or timer for the 1st PUCCH transmission starts. The moment a specific time window or timer starts can be the time when the UEBR is triggered.

[0160] In contrast, the UE may reset the event instance count after the UEBR is triggered, after the 1st PUCCH transfer is completed within a specific time window, or after the 1st PUCCH transfer is completed before a specific timer expires. The specific time window or the timer may be the time when the UEBR is triggered.

[0161] In contrast, after the UEBR is triggered, that is, when a specific time window for the 1st PUCCH transmission or a specific timer expires, the UE can initialize the event instance counting. The moment the specific time window or timer starts can be the point at which the UEBR is triggered.

[0162] In contrast, if the UEBR operation is completed via a 2nd UL channel transmission after the UEBR is triggered, the UE can initialize the event instance counting.

[0163] In contrast, in Mode A operation, after the UEBR is triggered and the 1st PUCCH transmission is completed, upon receiving a DCI containing 2nd UL channel allocation information, the UE can initialize the event instance counting.

[0164] In the above examples, a specific time window or a specific timer is a value used to set the time offset value for which the 1st PUCCH must be transmitted within a specific time after UEBR triggering.

[0165] Alternatively, after the UEBR is triggered, i.e., after the 1st PUCCH transmission, when a specific time window or timer for the 2nd UL channel transmission is operated, if the 2nd UL channel transmission is interrupted or fails within that time offset, or if that specific time window or specific timer expires, the UE may reset the event instance counting.

[0166] In this method, the specific time window size or the expiration, value, or length of a specific timer can be set to a value equal to or greater than 0. Additionally, these values ​​can be included when setting information for UEBR operation. That is, they can be set to one or more combinations of upper-level signaling such as RRC or lower-level signaling such as MAC-CE and DCI.

[0167] In the present embodiment and subsequent inventions, the UEBR triggering time can be set / determined in the following manner and the UEBR operation can be operated.

[0168]

[0169] UEBR Triggering Point Example #1

[0170] The UEBR triggering point may be the point at which a specific event is satisfied M times. That is, the position / index of the symbol of the RS (i.e., the reference signal transmitted for beam measurement) measured at the time when the specific event is satisfied for the Mth time, or a specific symbol position / index after one or more symbol time offsets relative to that symbol position, may be used as the UEBR triggering point.

[0171] In contrast, the start or end symbol position of a slot or subframe containing the RS symbol measured at the time when a specific event is satisfied for the Mth time can be operated as the UEBR triggering point.

[0172] In contrast, the start symbol of the next slot or subframe containing the RS symbol measured at the time when a specific event is satisfied for the Mth time may be operated as the UEBR triggering point.

[0173] UEBR Triggering Time Example #2

[0174] The UEBR triggering point can be the position / index of a symbol that has completed all quality measurements for the RS set for beam quality measurement, or a specific symbol position / index after one or more symbol time offsets relative to that symbol position.

[0175] Alternatively, the UEBR triggering point may be the start or end symbol position of a slot or subframe containing the symbol that has completed all quality measurements for the RS set for beam quality measurement.

[0176] Alternatively, the UEBR triggering point may be the starting symbol of the slot or subframe following the slot or subframe containing the symbol that has completed all quality measurements for the RS set for beam quality measurement.

[0177] UEBR Triggering Time Example #3

[0178] The gNB sets a time window for measuring whether a specific event is satisfied and can trigger the UEBR if the event is satisfied M or more times within that time window. In this case, the position / index of the symbol where the time window ends, or a specific symbol position / index after one or more symbol time offsets relative to that symbol position, can be used as the UEBR triggering point.

[0179] Alternatively, the start or end symbol position of a slot or subframe containing the symbol at which the corresponding time window ends can be used as the UEBR triggering point.

[0180] Alternatively, the start symbol of the slot or subframe following the slot or subframe containing the symbol at which the corresponding time window ends can be used as the UEBR triggering point.

[0181]

[0182] Method #3: When the TCI state pool setting value is reset by the RRC or when the TCI state list is enabled or disabled by the MAC-CE, the UE may initialize event instance counting. In this case, the RRC or MAC-CE containing the change in the TCI state setting may include indicator information instructing the initialization of event instance counting. For example, a specific bit field instructing the initialization of event instance counting may be defined and operated within the RRC or MAC-CE to transmit such indicator information.

[0183] In the above operation, configuration changes to TCI states by RRC or MAC-CE may not indicate a change to the currently used beam, but include a change in configuration information for beams associated with the TCI state. Therefore, since applying a specific beam change after UEBR operation is possible via the TCI state indication, the event instance counting value may be initialized to eliminate ambiguity regarding beam application between the gNB and the UE.

[0184] Method #3 can be operated to be applied only to specific events. For example, in cases like Event #3 where the terminal operates based on RS associated with TCI states for beams other than the current beam to determine whether the event is satisfied, the event instance counting value may be initialized to eliminate synchronization errors or ambiguities between the RS measurement operations associated with the existing TCI states for the changed TCI states and the UEBR when the settings for the TCI states are changed.

[0185]

[0186] Method #4: If the current beam changes during the measurement period for event satisfaction, the UE can reset the event instance count.

[0187] In other words, when performing a beam change operation, the beam change can be performed using one or more combinations of RRC, MAC-CE, and DCI. Additionally, a beam change instruction for PDSCH or PUSCH can be given via an indicator that specifies the TCI state of the DCI. In this case, the UE can initialize the event instance counting.

[0188] For example, in events configured as Event #1 and #2, if event satisfaction is determined based on the quality of the current beam, ambiguity may arise if the currently used beam changes to a new one while the satisfaction measurement is being performed based on the current beam. Therefore, to eliminate this ambiguity, the event instance counting can be reset when a beam change operation occurs.

[0189] In the case of Method #4, since the quality of the current beam is included as an event condition, as in Events #1 and #2, the corresponding event instance counting initialization method is applied, but this method may not be applied to Event #3.

[0190] In addition to the examples of configured events mentioned above, the proposed operational methods for various event instance counting can be applied to various event configurations in simple, modified, extended, or combined forms. Furthermore, different initialization methods for event instance counting can be configured and operated for each event.

[0191] The above methods #2, #3, and #4 are methods that reset the event instance count to 0 for the beams currently in use or beams being measured when initializing event instance counting. Here, in order to give priority to the event targeted for initialization in each method, the event instance count can be set and operated as a value greater than 0. In this case, it is possible for the event to operate as having priority for UEBR operation compared to other events. In other words, weights can be assigned to the event instance count.

[0192]

[0193] Example #2

[0194] This embodiment is an example in which the settings for PUCCH resources for UEBR are configured separately by mode. Additionally, it is assumed that a single event is configured and operated for the UE. In this case, when the corresponding event is satisfied, UEBR operation may be triggered. In situations where, after UEBR triggering, the 1st PUCCH for UEBR is not within a specific time window, or where the 1st PUCCH cannot be transmitted due to a conflict with another UL channel, the transmission and retransmission of the 1st PUCCH can be performed in the following manner.

[0195]

[0196] Method #5: Method #5 is an example of a case where a specific UEBR mode operation is configured and operated during UEBR operation. That is, it is a case where a specific UEBR mode operation is configured and operated at or prior to the time when the UEBR is triggered, and when the UEBR is triggered, a 1st PUCCH transmission can be performed using the PUCCH resources already allocated for that mode operation. For the sake of convenience of explanation, it is assumed that the UEBR Mode A operation is configured.

[0197] In the above operation, the 1st PUCCH transmission may be performed using the earliest PUCCH among the PUCCH resources for UEBR Mode A available after the UEBR triggering time. At this time, the PUCCH resources available for UEBR Mode A are dedicated PUCCH resources configured for Mode A. Additionally, the PUCCH resources available for the 1st PUCCH may be limited to PUCCH resources allocated after a specific time offset relative to the UEBR triggering time.

[0198] If the UE is unable to perform the 1st PUCCH transmission using the earliest available PUCCH resource for the above Mode A, such as due to a conflict with another UL channel transmission, the UE may perform the 1st PUCCH transmission using the earliest available PUCCH resource for another Mode A that is available within a specific time window A based on the UEBR triggering time or before a specific timer A started based on the UEBR triggering time expires. Subsequently, the UEBR Mode A operation may continue.

[0199] Method #5-1: If PUCCH resources for UEBR Mode A are not available within a specific time window A, or if a 1st PUCCH transmission using PUCCH resources for UEBR Mode A cannot be performed within a specific time window A due to reasons such as a conflict with other UL channel transmissions, or if PUCCH resources allocated for UEBR Mode B operation are available within a time window B, or if a specific timer B has not yet expired, a PUCCH retransmission operation through UEBR mode switching may be performed. Here, the size of time window A or the duration of timer A may be set shorter than the size of time window B or the duration of timer B.

[0200] In the examples above, the specific time window or specific timer is a value used to set the time offset value that the 1st PUCCH must transmit within a specific timeframe relative to the UEBR triggering point, and it can be operated in one of two ways. Additionally, the specific time window size or the specific timer's duration can be set to a value equal to or greater than zero. Furthermore, these values ​​can be included when configuring information for UEBR operation. That is, they can be configured as one or more combinations of upper-layer signaling such as RRC or lower-layer signaling such as MAC-CE or DCI. In the examples above, Time Window A and Time Window B are designated to distinguish the time window values ​​set for UEBR Mode A and Mode B. Similarly, Timer A and Timer B are designated to distinguish the timer values ​​set for UEBR Mode A and Mode B. In other words, the same or different time window sizes or timer duration values ​​can be set and operated for each mode. In this case, the time window and timer can be operated based on the time when the UEBR is triggered, or other reference points can be set. In other words, the time window and timer can start from the time the UEBR is triggered or at any other time.

[0201] Within a given time window or timer for each Mode, a 1st PUCCH retransmission for the same Mode operation may be performed, and the maximum number of retransmissions within that period may be limited. Based on the example of Method #5, a specific number of PUCCH retransmissions for Mode A operation may be performed before Time Window A or Timer A expires, and thereafter, a specific number of PUCCH retransmissions for Mode B operation may be performed before Time Window B or Timer B expires.

[0202] The specific time offset mentioned above may be a value set considering the processing time of the UE. This time offset may be a time unit such as a symbol or a slot, and may be set to a value equal to or greater than 0. The above time offset value and the maximum number of retransmissions may be included when configuring information for UEBR operation. That is, it may be set as one or more combinations of upper-layer signaling such as RRC or lower-layer signaling such as MAC-CE and DCI.

[0203] Method #5 is an example where Mode A is set, but the same method can be applied even when Mode B is set. Here, the operation of the above example can be simply applied when the setting value for Time Window A or Timer A is greater than the setting value for Time Window B or Timer B.

[0204] As another method, if a common time window or timer is applied instead of applying a time window or timer for each mode, the following operation is possible.

[0205] Method #5-2: Time Window C or Timer C refers to the valid period during which PUCCH retransmission is allowed in the UEBR Mode configured for UEBR operation. When such period expires, the system may operate as a period during which retransmission is allowed through other UEBR Mode operations from that point until Time Window D or Timer D expires.

[0206] In this example, since UEBR Mode A is configured, PUCCH retransmission for Mode A may be allowed until the expiration of time window C or timer C. If a limit on the maximum number of retransmissions is set, the 1st PUCCH retransmission for Mode A may be performed within that timeframe without exceeding the maximum number of retransmissions. If the PUCCH resource for the 1st PUCCH transmission for Mode A is not available within time window C, or if the 1st PUCCH transmission using the PUCCH resource for UEBR Mode A cannot be performed within a specific time window C due to reasons such as a conflict with other UL channel transmissions, or if the PUCCH resource allocated for UEBR Mode B operation is available within time window D, or if a specific timer D has not yet expired, the 1st PUCCH transmission operation for Mode B operation may be performed through UEBR mode switching.

[0207] In this case, the size of Time Window C or the expiration date of Timer C must be set to be shorter than the size of Time Window D or the expiration date of Timer D. Additionally, Time Windows C, D, or Timers C, D can be set based on the UEBR triggering point. Alternatively, Time Window D or Timer D can be set based on the expiration point of Time Window C or Timer C.

[0208] Although Method #5-2 is an example where Mode A is set, the same method can be applied to an example where Mode B is set.

[0209]

[0210] Method #6: Method #6 is an example of a case where a specific UEBR Mode operation is not configured during UEBR operation. Since each PUCCH resource is exclusively allocated for each UEBR mode, the decision to use a specific PUCCH resource may consequently mean the execution of a specific UEBR mode operation.

[0211] The terminal attempts transmission using the earliest PUCCH resource within a specific time window based on the triggering time of the UEBR, and a UEBR Mode operation corresponding to that PUCCH resource can be performed. Here, the earliest PUCCH resource may be a resource located at least after a specific time offset from the UEBR triggering time.

[0212] If the 1st PUCCH transmission through the selected PUCCH resource cannot be performed due to issues such as a conflict with other UL channel transmissions, a retransmission may be attempted using the next earliest PUCCH resource within a set time window. Here, a UEBR mode operation corresponding to the PUCCH resource may be performed. The retransmission operation may be attempted up to a maximum number of times within the time window.

[0213] In the above embodiment, a specific time window set based on the triggering point of the UEBR can be defined and operated by a specific timer set based on the triggering point of the UEBR. The set size and range of the specific time window can be applied identically to the start and expiration periods of the specific timer.

[0214] The specific time offset mentioned above may be a value set considering the processing time of the UE. This time offset may be a time unit such as a symbol or a slot, and may be set to a value equal to or greater than 0. The above time offset value and the maximum number of retransmissions may be included when configuring information for UEBR operation. That is, it may be set as one or more combinations of upper-layer signaling such as RRC or lower-layer signaling such as MAC-CE and DCI.

[0215] A specific time window or a specific timer is a value used to set the time offset value within which the 1st PUCCH must be transmitted relative to the UEBR triggering point, and it can be operated in one of the two ways. Additionally, the specific time window size or the specific timer duration can be set to a value equal to or greater than zero. Furthermore, these values ​​can be included when configuring information for UEBR operation. That is, they can be configured as one or more combinations of upper-layer signaling such as RRC or lower-layer signaling such as MAC-CE and DCI.

[0216] #Method 6-1: In the operation of the above Method #6, different time windows may be set for the PUCCH resources allocated to each mode. For example, a short time window A may be set for Mode A, and a long time window B may be set for Mode B. In such cases, transmission and retransmission are possible via the earliest PUCCH within the time window A related to Mode A, and the UEBR mode that can be operated at that time is the UEBR Mode corresponding to the PUCCH resource used for the 1st PUCCH transmission. That is, it is a period in which both Mode A and Mode B operations are possible.

[0217] After time window A set for Mode A, 1st PUCCH transmission or retransmission is possible using PUCCH resources dedicated to Mode B within time window B set for Mode B. In other words, this section is a section where only UEBR operation by Mode B is possible.

[0218] In this method, time windows A and B can be set based on the UEBR triggering time. In contrast, time window B can be set based on the expiration time of time window A. In other words, time window B can include a time window starting from the expiration time of time window A.

[0219] The time window configured and operated in this method can be defined and operated by a specific timer that starts and expires in the same form as the time window start and end points.

[0220] This example of the method is for the case where the time window of Mode A is shorter than that of Mode B, but it is possible to set it to the opposite case and operate the transmission or retransmission for the 1st PUCCH in the same way. In other words, the time window of Mode A can be shorter than the time window of Mode B.

[0221] The size of the time window or the expiration date of a specific timer can be set to a value equal to or greater than 0. Additionally, these values ​​can be included when configuring information for UEBR operation. That is, these values ​​can be configured using one or more combinations of upper-level signaling such as RRC or lower-level signaling such as MAC-CE and DCI.

[0222]

[0223] Method #7: Method #7 is an example of how a specific UEBR mode operation can be prioritized in the operation of the UEBR. A counter can be set and operated for priority setting for each mode. Based on the counter value, the operation can be operated to prioritize the operation to a specific mode and perform transmission and retransmission. Prioritizing the operation to a specific mode may mean performing a 1st PUCCH transmission through the PUCCH resource associated with that mode.

[0224] As an example of the above operation method, a counter can be set for each UEBR operation mode to count the number of successful attempts. Additionally, when the UEBR is triggered, the terminal can prioritize the execution of the mode with the higher value of the corresponding counter.

[0225] In the above operation method, the counter value may be decreased by -1 when the execution of the corresponding UEBR operation mode fails. As another example, the counter values ​​may be initialized when the UEBR configuration information is reconfigured. As yet another example, the counter value may be initialized when it becomes above or below a specific value. As yet another example, if one counter is initialized, both counters may be initialized.

[0226] In the above operation method, a single counter may be used instead of a counter for each mode. When Mode A operation is successful, the counter value may be increased by 1, and when Mode B operation is successful, the counter value may be decreased by -1. In this case, the initial value of the counter may be set to a non-zero value. Additionally, the initialization of the single counter may be performed when the UEBR configuration information is reset. Alternatively, it may be initialized when the counter value becomes greater than or less than a specific value. If one counter is initialized, both counters may be initialized.

[0227] An example operation based on the two counters above can be used as a counter for the number of times the UEBR operation failed. In this case, the mode with the smaller counter value can be executed first.

[0228] The above examples can be applied and operated in simple modified, expanded, or combined forms.

[0229]

[0230] Example #3

[0231] This embodiment is an example in which the PUCCH resource for the UEBR is configured as a common dedicated resource for UEBR operation without distinction by mode. Additionally, it is assumed that a single event is configured and operated for the UE. In this case, when the corresponding event is satisfied, the UEBR operation may be triggered. In situations such as when the 1st PUCCH for the UEBR is not within a specific time window after UEBR triggering, or when the 1st PUCCH cannot be transmitted due to a conflict with another UL channel, the transmission and retransmission of the 1st PUCCH may be performed in the following manner.

[0232] When gNB is configured and operated so that the terminal operates in one specific mode among two UEBR modes, it can be applied and operated in the same manner as Method #5, a variation or extension thereof, or a combination with other methods proposed in the present invention.

[0233]

[0234] Method #8: When both UEBR modes are configured and allowed to be used, the terminal can perform a 1st PUCCH transmission through the PUCCH resource at an earlier point in time within a configured specific time window.

[0235] In the above operation, the 1st PUCCH may use the earliest PUCCH among the PUCCH resources exclusive to UEBR that are available after the UEBR triggering time. Additionally, the PUCCH resources available for the 1st PUCCH may be limited to PUCCH resources allocated after a specific time offset relative to the UEBR triggering time.

[0236] If the UE is unable to perform a 1st PUCCH transmission using the earliest available PUCCH resource for the above UEBR, such as due to a conflict with another UL channel transmission, the UE may perform a 1st PUCCH retransmission using the earliest available PUCCH resource within a specific time window based on the UEBR triggering time or before a specific timer starting from the UEBR triggering time expires.

[0237] The determination of the UEBR mode during the above 1st PUCCH transmission or retransmission can be determined and operated in the following manner.

[0238] Method #8-1: A method in which the determination of the UEBR mode is performed at the time of PUCCH transmission, and the specific time window setting for the 1st PUCCH transmission for each UEBR mode operation can be operated differently.

[0239] For example, a time window A for limiting 1st PUCCH transmission in Mode A and a time window B for limiting 1st PUCCH transmission in Mode B can be configured. Here, let us assume that both time windows A and B are configured based on the UEBR triggering time, and that the expiration period of time window A is set shorter than that of time window B. In this case, within time window A, 1st PUCCH transmissions and retransmissions are sent to the 1st PUCCH for Mode A operation, and subsequently, after the expiration of time window A, within time window B, 1st PUCCH transmissions and retransmissions can be sent to the 1st PUCCH for Mode B operation. In this method, time window B can be configured and operated based on the expiration time of time window A.

[0240] Method #8-1 is an example where the expiration period of Time Window A is set shorter than that of Time Window B, so the retransmission of the Mode A operation is performed first. However, the opposite example is also possible.

[0241] Additionally, within a given time window for each mode, retransmission of the 1st PUCCH for the same mode operation is possible, and the maximum number of retransmissions within that period may be limited. That is, a specific number of PUCCH retransmissions for Mode A operation are possible before time window A expires, and thereafter, a specific number of PUCCH retransmissions for Mode B operation are possible before time window B expires.

[0242] Method #8-2: UEBR mode can be determined after confirming whether DCI is received for Mode A operation following the time of PUCCH transmission. A time window may be set and operated as a time limit for receiving DCI after the 1st PUCCH transmission, and this may be referred to as the DCI time window for convenience of explanation. In this case, if a DCI that allocates the 2nd UL channel resource of Mode A is received within the DCI time window after the 1st PUCCH transmission, the terminal may operate in Mode A.

[0243] If it is not received, the terminal can change its operation to Mode B to perform UEBR operation, and can perform UBER Mode B using the CG-PUSCH that is earliest after the DCI time window end among the CG-PUSCHs associated with the previously transmitted 1st PUCCH.

[0244] As another example of retransmission through a change in Mode B operation, the terminal may consider the previously transmitted 1st PUCCH as dropped and perform a 1st PUCCH retransmission operation for Mode B operation. In this case, the PUCCH resource for the 1st PUCCH transmission may be the UEBR-dedicated PUCCH available at the earliest time after the DCI time window expires. Subsequently, 1st PUCCH retransmission for Mode B may be performed until a specific time window. This specific time window refers to the time window during which 1st PUCCH retransmission for Mode B is permitted, and this time window may be defined and operated based on the UEBR triggering time or the DCI time window expiration time.

[0245] Method #8-3: In the case of Method #8-2, 1st PUCCH retransmission is not performed within the DCI time window. However, a time window for performing the 1st PUCCH retransmission operation of Mode A can be set and operated within the DCI time window. For convenience of explanation, this is referred to as modeA-time-window. modeA-time-window can be set and operated with a value equal to or smaller than the DCI time window. After UEBR triggering, the 1st PUCCH is transmitted, and if DCI reception is not received within the modeA-time-window, the terminal can perform the 1st PUCCH transmission again. The retransmission operation of the 1st PUCCH expecting the corresponding Mode A operation may only be possible within the DCI time window. Subsequent operations can be operated in the same manner as Method #8-2.

[0246]

[0247] The specific time offset mentioned above may be a value set considering the processing time of the UE. This time offset may be a time unit such as a symbol or a slot, and the time offset setting may be set to a value equal to or greater than 0. The above time offset value and the maximum number of retransmissions may be included when setting information for UEBR operation. That is, it may be set as one or more combinations of upper-layer signaling such as RRC or lower-layer signaling such as MAC-CE and DCI.

[0248] In the above methods, a specific time window set based on the triggering point of the UEBR can be defined and operated by a specific timer set based on the triggering point of the UEBR. The set size and range of the specific time window can be applied identically to the start and expiration periods of the specific timer.

[0249] The above specific time window size can be set to a value equal to or greater than 0. Additionally, these values ​​may be included when setting information for UEBR operation. That is, it can be set to one or more combinations of upper-level signaling such as RRC or lower-level signaling such as MAC-CE and DCI.

[0250]

[0251] Example #4

[0252] Since the 1st PUCCH resources for UEBR operation are pre-configured, development is required regarding the usage method of the corresponding PUCCH if an event is not satisfied. For example, if the 1st PUCCH is not used and no transmission is made when an event is not satisfied, a situation may arise where the gNB cannot determine whether the PUCCH is decoding-undecodable or if the event has not been satisfied. Therefore, if the 1st PUCCH is to be used for transmitting specific information even when an event is not satisfied, the following operational method is possible.

[0253] If an event is not satisfied through the pre-configured UEBR 1st PUCCH, the terminal can perform a 1st PUCCH transmission to indicate that a specific event has not been satisfied through the PUCCH.

[0254] When 1 bit information is transmitted through the existing 1st PUCCH, this bit is used to indicate whether there is a request for 2nd UL channel resource allocation in Mode A, and to indicate whether there is a pre-configured 2nd UL channel resource in use in Mode B.

[0255] However, when an operation is applied to perform a 1st PUCCH transmission indicating that an event has not been satisfied, and 1 bit information is transmitted through the above 1st PUCCH, the PUCCH in Mode A may be used to indicate either a request for allocation of a 2nd UL channel resource or information indicating that a set event has not been satisfied. Additionally, the PUCCH in Mode B may be used to indicate either the use of a pre-configured 2nd UL channel resource or information indicating that a set event has not been satisfied. Here, the information indicating that an event has not been satisfied may consequently include information indicating no request for a 2nd UL resource or that a pre-configured 2nd UL channel is not being used.

[0256] In the above operation, indicating that an event is not satisfied may be an operation indicating that an event associated with the corresponding 1st PUCCH resource is not satisfied. If multiple events are associated with a single 1st PUCCH resource, for a 1-bit information transmission PUCCH, the PUCCH in Mode A may be used to indicate one of the following: a request for 2nd UL channel resource allocation or information indicating that none of the configured events are satisfied. Additionally, in Mode B, the PUCCH may be used to indicate one of the following: usage of a pre-configured 2nd UL channel resource or information indicating that none of the configured events are satisfied.

[0257] In the above operation, if a PUCCH resource capable of transmitting more than 1 bit of information is applied and used as the 1st PUCCH, information indicating whether a specific event or specific events is satisfied can be included in the 1st PUCCH and transmitted to the gNB.

[0258] When the gNB recognizes that a specific event or specific events are not satisfied upon receiving the 1st PUCCH, the gNB may instruct the use of a specific UEBR mode, change configuration information for the UEBR mode, change event settings, or instruct the allocation or modification of UL resources for UEBR operation, namely PUCCH / CG-PUSCH resources, by using one or more combinations of upper-level signaling such as RRC, DCI, or MAC-CE.

[0259]

[0260] Example #5

[0261] When the gNB sets multiple events for multiple UEBRs for the UE, and the 1st PUCCH is capable of multi-bit transmission to indicate whether the event is satisfied, the following methods can be operated.

[0262]

[0263] Method #9: In the case where there are a total of two configured events, Event #1 and Event #2, if PUCCH is capable of transmitting 2 bits of information, as shown in Table 3, each bit can indicate whether each event is satisfied and to perform the UEBR operation associated with that event. In other words, whether an event is satisfied can be indicated through PUCCH.

[0264] bits instruction information transmitted via 1st PUCCH 00 Events #1 and #2 are not satisfied. 10 Event #1 is satisfied. 01 Event #2 is satisfied. 11 Events #1 and #2 are both satisfied.

[0265] If '00' is transmitted via the 1st PUCCH, the PUCCH may indicate that neither Event #1 nor Event #2 is satisfied. If '01' is transmitted via the 1st PUCCH, the PUCCH may indicate that Event #1 is not satisfied and Event #2 is satisfied. If '10' is transmitted via the 1st PUCCH, the PUCCH may indicate that Event #1 is satisfied and Event #2 is not satisfied. If '11' is transmitted via the 1st PUCCH, the PUCCH may indicate that both Event #1 and Event #2 are satisfied. For a specific satisfied event, in Mode A, the terminal may request the gNB to allocate the 2nd UL channel for the UEBR operation corresponding to the event. In Mode B, the terminal may transmit a notification to the gNB regarding the use of the previously allocated CG-PUSCH for the UEBR operation corresponding to the event.

[0266] If both events are satisfied, the terminal may execute only the UEBR for the event with the higher priority among the two events. Alternatively, the terminal may multiplex beam information corresponding to the two UEBRs and transmit it to the gNB through the 2nd UL channel.

[0267] The above embodiment is an example in which the method of Embodiment #4 is applied as an example of transmitting 0 even when an event is not satisfied. In a method where 1st PUCCH transmission is not performed when an event is not satisfied, if both Event #1 and Event #2 are not satisfied, the terminal may be operated to transmit nothing, such as '00', through 1st PUCCH. If only one of the two events is not satisfied, the terminal may be operated to transmit including 0, such as '01' or '10', in the same manner as the above example operation to indicate the satisfied event. For example, the satisfied event may be indicated based on the position of the bit with a value of 1.

[0268]

[0269] Method #10: When there are a total of two configured events, Event #1 and Event #2, and PUCCH is capable of transmitting 2 bits of information, the combination of each bit as shown in Tables 4 and 5 can indicate whether a specific event is satisfied and the execution of a UEBR operation associated with that event.

[0270] Bits instruction information transmitted via 1st PUCCH: 00 Event #1 satisfied. 10 Event #2 satisfied. 01 Event #1 and #2 both satisfied. 11 Neither satisfied.

[0271]

[0272] In the case of the example in Table 4, instructions identical to those in Table 3 are possible. However, unlike the example in Table 3, where each bit corresponds to a single event, the codepoint for each bit combination is mapped to the instruction information and operated. In contrast, the example in Table 4 can be operated in such a way that if both of the two events configured in the same way as Method #9 are not satisfied, the '11' instruction information is transmitted, but transmission to the 1st PUCCH is not performed. In this case, the '11' codepoint in Table 4 can be left empty as reserved.

[0273] Table 4 is an example of a case where two events are set. If three events are set, the satisfaction of the events can be indicated as shown in Table 5.

[0274] Bits instruction information transmitted via 1st PUCCH: 00 Event #1 satisfied. 10 Event #2 satisfied. 01 Event #3 satisfied. 11 None satisfied.

[0275]

[0276] Of the four code points formed by a combination of 2 bits, three indicate that each event is satisfied, and the remaining code point '11' can indicate that none of the events are satisfied. Alternatively, the example in Table 5 can be operated in such a way that transmission to the 1st PUCCH is not performed instead of transmitting the '11' indication information when all three set events are not satisfied. In this case, the '11' code point in Table 3 can be left empty as a reserve.

[0277]

[0278] bits instruction information transmitted via 1st PUCCH 000 Event #1 satisfied only. 001 Event #2 satisfied only. 010 Event #3 satisfied only. 011 Event #1, #2 satisfied only. 100 Event #1, #3 satisfied only. 101 Event #2, #3 satisfied only. 110 Event #1, #2, #3 all satisfied. 111 Event #1, #2, #3 all unsatisfied.

[0279]

[0280] Table 6 is an example of the operation method for the three configured events when three bits can be transmitted via PUCCH. Each of the eight code points can be operated by mapping to instruction information for each case satisfying one or more events. It can also be operated by including information indicating that none of the configured events are satisfied. Alternatively, the example in Table 6 allows for an operation where transmission to the 1st PUCCH is not performed instead of transmitting the '11' instruction information when none of the three configured events are satisfied. In this case, the '111' code point in Table 6 can be left empty as a reserve.

[0281] For a specific event satisfied in the above methods, in Mode A, a request for allocation of the 2nd UL channel for UEBR operation corresponding to the event may be made to the gNB, and in Mode B, a notification regarding the use of the previously allocated CG-PUSCH for UEBR operation corresponding to the event may be sent to the gNB.

[0282] If two or more events are satisfied, the terminal may execute only the UEBR for the event with the highest priority among the multiple events. Alternatively, beam information corresponding to multiple UEBRs may be multiplexed and transmitted to the gNB through the 2nd UL channel.

[0283] The above methods can be applied in simple, modified, extended, and combined forms to various operating environments where two or more multi-bit transmission PUCCHs and two or more events are configured and operated.

[0284] All embodiments and detailed methods in the present invention can be applied in simple, modified, extended, or combined forms in an operating environment for UEBR.

[0285]

[0286] FIG. 13 illustrates an initialization procedure for an event instance count according to one embodiment of the present disclosure. The procedure of FIG. 13 may be performed by a terminal. The procedure of FIG. 13 may be part of the procedure illustrated in FIG. 11.

[0287] Referring to FIG. 13, in step S1301, the terminal receives configuration information containing information about an event. The configuration information may include information indicating the type of event. For example, the type of event may include at least one of Event 1 (e.g., Event #1 of Example #1), Event 2 (e.g., Event #2 of Example #1), or Event 7 (e.g., Event #3 of Example #1). The information about the event may further include information about at least one of a time interval, a time window, or a timer for event detection.

[0288] In step S1303, the terminal detects an event. The detection of the event may be performed based on the type of event set. For example, if Event 1 is set, the terminal may detect when the quality of the measured beam is lower than a threshold. When the event is detected, the terminal may increment the event instance counter. The increment of the event instance counter may be performed based on a time window, a time interval, or a timer. For example, if the timer has not started, the terminal may increment the event instance counter from 0 to 1 when the event is detected. If the timer has started, the terminal may increment the event instance counter by 1 when the event is detected.

[0289] In step S1305, the terminal may receive information for changing the settings. For example, the terminal may receive RRC signaling or MAC-CE for changing the settings. For example, the information for changing the settings may receive information for changing the beam or information for changing the TCI state. Here, the information for changing the beam may include information indicating the beam to be changed. The information for changing the TCI state may include information indicating the TCI state to be changed. The information for changing the TCI state may include a TCI state pool or a TCI state list. Changing the settings may be referred to as updating the settings.

[0290] In step S1307, the terminal may reset the event instance counter. The event instance counter may be reset based on a change in the configuration. For example, the event instance counter may be reset based on a change in the TCI state. As another example, the event instance counter may be reset based on a change in the beam. As yet another example, the event instance counter may be reset based on the event instance counter reaching a defined value.

[0291] In step S1309, the terminal may initiate a UEBR operation. The initiation of a UEBR operation may be referred to as UEBR triggering. A UEBR operation may be initiated based on the detection of an event. For example, a UEBR operation may be performed based on an event instance counter reaching a predefined value.

[0292]

[0293] FIG. 14 illustrates a PUCCH retransmission procedure according to one embodiment of the present disclosure. The procedure of FIG. 14 can be performed by a terminal.

[0294] Referring to FIG. 14, in step S1401, the terminal determines UEBR triggering. UEBR triggering may be determined based on whether an event is satisfied. For example, an event may be satisfied when an event instance counter reaches a predefined value. When UEBR triggering is determined, the terminal may determine a UEBR mode. For example, the UEBR mode may be associated with the satisfied event.

[0295] In step S1403, the terminal attempts to transmit a signal via the PUCCH. Here, 'transmission via the PUCCH' may refer to the transmission of a signal using the resources allocated to the PUCCH. The resources allocated to the PUCCH may be referred to as PUCCH resources. PUCCH resources may be associated with UEBR modes. For example, the PUCCH resources for Mode A and the PUCCH resources for Mode B may be different. As another example, the PUCCH resources for Mode A and the PUCCH resources for Mode B may be the same resource.

[0296] In step S1405, the terminal attempts retransmission if the PUCCH resource is unavailable. For example, the case where the PUCCH resource is unavailable may include the case where there is no available PUCCH resource based on the UEBR mode within a set time window. Retransmission may be attempted up to a maximum retransmission limit. The maximum retransmission limit may include at least one of the number of retransmissions or the retransmission period. Retransmission may be performed based on a mode different from the UEBR mode determined in step S1401.

[0297]

[0298] FIG. 15 illustrates a procedure for notifying whether an event is satisfied according to one embodiment of the present disclosure. The procedure of FIG. 15 may be performed by a terminal.

[0299] Referring to FIG. 15, in step S1501, the terminal receives configuration information including information regarding PUCCH resources. The information regarding PUCCH resources may include information regarding PUCCH resources associated with a UEBR mode or information regarding PUCCH resources for UEBR operation. In other words, the PUCCH resources may include resources different depending on the UEBR mode and may include resources common to the UEBR modes.

[0300] In step S1503, the terminal generates a message to notify whether an event has been satisfied. The message to notify whether an event has been satisfied may be transmitted via a PUCCH resource. The message to notify whether an event has been satisfied may be 1 bit, 2 bits, or 3 bits. The message to notify whether an event has been satisfied may indicate whether each of at least one set event has been satisfied.

[0301] In step S1505, the terminal notifies the base station whether the event has been satisfied. The terminal may transmit a message to notify whether the event has been satisfied. Here, the message may be transmitted via a PUCCH resource. Alternatively, the terminal may not transmit a message via a PUCCH resource. In this case, the terminal’s action of not transmitting a message via a PUCCH resource may signify an action of notifying that the event has not been satisfied. In other words, the terminal may inform the base station that the event has not been satisfied by not transmitting a message.

[0302]

[0303] The operation of the method according to the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes all types of recording devices in which information that can be read by a computer system is stored. Additionally, a computer-readable recording medium may be distributed across networked computer systems, and a computer-readable program or code may be stored and executed in a distributed manner.

[0304] In addition, computer-readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions may include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter.

[0305] Some aspects of the present disclosure have been described in the context of a device, but may also be described according to a corresponding method, wherein a block or device corresponds to a method step or feature of a method step. Similarly, aspects described in the context of a method may also be described according to a corresponding block or item or feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one of the most important method steps may be performed by such a device.

[0306] A programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described in this disclosure. A field-programmable gate array may operate with a microprocessor to perform one of the methods described in this disclosure. In general, it is preferable that the methods be performed by some hardware device.

[0307] Although the present disclosure has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the following claims.

Claims

In a method of operation of a terminal in a wireless communication system, A step of receiving first setting information for beam reporting; A step of detecting an event based on the above-mentioned first setting information; A step of increasing an event instance counter based on the detection of the above event; A step of triggering a beam report based on the event instance counter reaching a preset value; and A method comprising the step of resetting the event instance counter based on the event instance counter reaching the preset value. In Article 1, A step of receiving information indicating a change in the current beam; and A method further comprising the step of resetting the event instance counter based on receiving information indicating a change in the current beam. In Article 1, A step of receiving second setting information for changing the first setting information; and A method further comprising the step of resetting the event instance counter based on the reception of the second setting information. In Paragraph 3, The above second setting information is, A method comprising at least one of information related to a beam, information instructing or setting a change in an activated TCI state, information instructing or setting a change in a setting for a TCI state pool, or information instructing or setting a change in a TCI state list instructed by activation or deactivation based on said TCI state pool. In Article 1, A method further comprising the step of starting a timer or time window based on the detection of the above event. In Article 5, A method further comprising the step of resetting the event instance counter based on the expiration of the timer or time window. In Article 5, A method in which information regarding the timer or time window is included in the first setting information. In Article 7, A method in which information regarding the timer or time window includes the size of the timer or the length of the time window. In Article 1, The above first setting information includes information related to the type of event, and The type of the above event is a method that indicates the conditions under which the above event occurs. In Article 9, The above event is, If the current beam quality is worse than the first threshold; If there is at least one new beam having better beam quality than the beam currently in use; or If, among the activated TCI states, there exists at least one new beam having a better beam quality than the reference signal (RS) associated with the Kth best quality TCI state A method comprising at least one of the following. In Article 1, The above event instance counter includes a counter for each of the plurality of beams, and A method in which the beam report is triggered based on one of the counters for each of the plurality of beams reaching the preset value. In Article 1, The above first setting information includes information regarding resources for the beam report, and The resource for the above beam report is associated with the mode for the above beam report, and The above-mentioned mode for beam reporting includes at least one of Mode A or Mode B, wherein The above Mode A is a mode in which triggering of beam reporting or resource allocation for beam reporting is directed via DCI, and The above Mode B is a method in which signaling regarding beam reporting is performed through periodic PUCCH resources and beam reporting is performed through pre-configured UL resources. In a method of operating a base station in a wireless communication system, A step of transmitting first setting information for beam reporting; and Based on the first setting information above, the method includes the step of receiving the beam report, The above beam report is transmitted based on the event instance counter based on the above first setting information reaching a preset value, and A method in which the above event instance counter is reset based on the event instance counter reaching a preset value. In Article 13, The method further includes the step of transmitting information indicating a change in the current beam, A method in which the above event instance counter is reset based on the transmission of information indicating a change in the current beam. In Article 13, A step of transmitting second setting information for changing the first setting information; and A method in which the above event instance counter is reset based on the transmission of the above second setting information. In Article 15, The above second setting information is, A method comprising at least one of information related to a beam, information instructing or setting a change in an activated TCI state, information instructing or setting a change in a setting for a TCI state pool, or information instructing or setting a change in a TCI state list instructed by activation or deactivation based on said TCI state pool. In Article 13, The above first setting information includes information related to the type of event, and The above event is, If the current beam quality is worse than the first threshold; If there is at least one new beam having better beam quality than the beam currently in use; or If, among the activated TCI states, there exists at least one new beam having a better beam quality than the reference signal (RS) associated with the Kth best quality TCI state A method comprising at least one of the following. In Article 13, The above event instance counter includes a counter for each of the plurality of beams, and A method in which the beam report is triggered based on one of the counters for each of the plurality of beams reaching the preset value. In a terminal of a wireless communication system, At least one transmitter / receiver; At least one processor; and It includes at least one memory connected to the above-mentioned at least one processor to enable operation and storing instructions that control the terminal to perform operations when executed by the processor, and The above operations are, A step of receiving first setting information for beam reporting; A step of detecting an event based on the above-mentioned first setting information; A step of increasing an event instance counter based on the detection of the above event; A step of triggering a beam report based on the event instance counter reaching a preset value; and A terminal comprising the step of resetting the event instance counter based on the event instance counter reaching the preset value. In a base station of a wireless communication system, At least one transmitter / receiver; At least one processor; and It includes at least one memory connected to operately with the above-mentioned at least one processor and storing instructions that control the base station to perform operations when executed by the processor, and The above operations are, A step of transmitting first setting information for beam reporting; and Based on the first setting information above, the method includes the step of receiving the beam report, The above beam report is transmitted based on the event instance counter based on the above first setting information reaching a preset value, and The above event instance counter is a base station that is reset based on the event instance counter reaching a preset value.

Images