Method and apparatus for performing UEBR in wireless communication system

Abstract

The present disclosure relates to a method and an apparatus for performing UE-initiated beam report (UEBR) in a wireless communication system, and an operation method of a terminal in a wireless communication system comprises the steps of: receiving, from a base station, at least one piece of configuration information including first configuration information; determining satisfaction of a first event configured by the first configuration information; triggering a UEBR operation on the basis of the satisfaction of the first event; determining an operation mode for the UEBR operation on the basis of the first configuration information; transmitting signaling by using a first physical uplink control channel (PUCCH) resource indicated by the first configuration information; and transmitting a beam report on the basis of the signaling, wherein the operation mode includes mode A or mode B, and the first configuration information is configured in association with the type of the first event and the first PUCCH resource.

Description

Method and apparatus for performing UEBR in a wireless communication system

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

[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 determining a mode for performing UEBR operation.

[0007] The present disclosure may provide a method and apparatus for determining resources for performing UEBR operations.

[0008] The present disclosure may provide a method and apparatus for determining an operation mode associated with an event of UEBR operation.

[0009] The present disclosure may provide a method and apparatus for setting events, modes, and resources for performing UEBR operations.

[0010] The present disclosure may provide a method and apparatus for setting priorities among modes for performing UEBR operations.

[0011] The present disclosure may provide a method and apparatus for setting resources for beam reporting.

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

[0013] According to one embodiment of the present disclosure, a method of operation of a terminal in a wireless communication system comprises: receiving at least one configuration information including first configuration information from a base station; determining satisfaction of a first event set by the first configuration information; triggering a UE-initiated beam report (UEBR) operation based on satisfaction of the first event; determining an operation mode for the UEBR operation based on the first configuration information; transmitting a signaling using a first physical uplink control channel (PUCCH) resource indicated by the first configuration information; and transmitting a beam report based on the signaling, wherein the operation mode includes mode A or mode B, and the first configuration information is set in association with the type of the first event and the first PUCCH resource.

[0014] According to one embodiment of the present disclosure, a method of operation of a base station in a wireless communication system comprises: transmitting at least one configuration information including first configuration information to a terminal; receiving a signaling from the terminal based on the first configuration information; and receiving a beam report based on the signaling, wherein the beam report is transmitted by the terminal based on an operation mode determined based on the first configuration information, the signaling is received using a first PUCCH resource indicated by the first configuration information, the operation mode includes mode A or mode B, and the first configuration information is set by association with the type of the first event and the first PUCCH resource.

[0015] According to one embodiment of the present disclosure, in a wireless communication system, a terminal 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 at least one configuration information from a base station that includes first configuration information; determining satisfaction of a first event set by the first configuration information; triggering a UEBR (UE initiated beam report) operation based on satisfaction of the first event; determining an operation mode for the UEBR operation based on the first configuration information; transmitting a signaling using a first PUCCH (physical uplink control channel) resource indicated by the first configuration information; and transmitting a beam report based on the signaling, wherein the operation mode includes mode A or mode B, and the first configuration information is set in association with the type of the first event and the first PUCCH resource.

[0016] According to one embodiment of the present disclosure, a base station 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: transmitting at least one configuration information including first configuration information to the terminal; receiving a signaling from the terminal based on the first configuration information; and receiving a beam report based on the signaling, wherein the beam report is transmitted by the terminal based on an operation mode determined based on the first configuration information, the signaling is received using a first PUCCH resource indicated by the first configuration information, the operation mode includes mode A or mode B, and the first configuration information is set in association with the type of the first event and the first PUCCH resource.

[0017] The proposed technology determines an operation mode associated with an event to perform a UEBR (user-initiated / event-driven beam report) and can efficiently report a beam using resources configured based on the determined operation mode.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0031] FIG. 13 illustrates a procedure for performing beam reporting based on a mode associated with an event according to one embodiment of the present disclosure.

[0032] FIG. 14 illustrates a resource utilization procedure for beam reporting according to a mode according to one embodiment of the present disclosure.

[0033] FIG. 15 illustrates a procedure for transmitting signaling using a configured resource according to one embodiment of the present disclosure.

[0034] FIG. 16 illustrates a mode change procedure based on a time window according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0083]

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

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

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

[0087] 014101114202214404314808414160165143203261464064

[0088]

[0089]

[0090]

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

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

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

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

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

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

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

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

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

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

[0101] ISAC (integrated sensing and communication) technology

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0127] 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 resources. 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. The information related to resources may include information related to PUCCH resources. For example, the PUCCH resources may include resources dedicated to UEBR operation. In other words, they may include PUCCH resources that are available in common for Mode A and Mode B. Alternatively, the PUCCH resources may include at least one of resources for Mode A or resources for Mode B. The information related to resources may further include information regarding PUCCH resources for Mode B.

[0128] In step S1103, the terminal determines an operation mode based on whether an event is satisfied. Whether an event is satisfied may be determined based on information regarding the event. The operation mode may be determined when the event is satisfied. Alternatively, the operation mode may be determined in advance even if the event is not satisfied. The operation mode may be determined based on information regarding the event or configuration information. For example, if the event is satisfied, the terminal may determine a mode associated with the type of satisfied event as the operation mode. As another example, if the event is satisfied, the terminal may determine a mode configured as enable as the operation mode. As yet another example, the terminal may determine a mode indicated in the configuration information received in step S1101 as the operation mode. In addition to the examples described above, the terminal may determine an operation mode based on the embodiments to be described below.

[0129] In step S1105, the terminal performs a UEBR operation based on the operation mode. Here, the UEBR operation may include the operation illustrated in FIG. 9 or FIG. 10. In other words, the UEBR operation may include at least one of beam reporting, signaling for performing beam reporting, or receiving DCI for resource allocation. The UEBR operation may be performed based on configuration information. For example, if Mode A is determined as the operation mode in step S1103, the terminal may request resources for beam reporting from the base station based on information regarding resources included in the configuration information. As another example, if Mode B is determined as the operation mode in step S1103, the terminal may notify the base station to perform beam reporting based on information regarding resources included in the configuration information. If the operation mode is Mode A, the terminal may perform beam reporting based on resources allocated by the DCI. If the operation mode is Mode B, the terminal may perform beam reporting using resources configured by the configuration information.

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

[0131] Referring to FIG. 12, in step S1201, the base station transmits configuration information to the terminal. The configuration information may be transmitted 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 resources. 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. The information related to resources may include information related to PUCCH resources. For example, the PUCCH resources may include resources dedicated to UEBR operation. In other words, they may include PUCCH resources that are available in common for Mode A and Mode B. Alternatively, the PUCCH resources may include at least one of resources for Mode A or resources for Mode B. The information related to resources may further include information regarding PUCCH resources for Mode B.

[0132] In step S1203, 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.

[0133] In step S1205, 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.

[0134] Detailed embodiments for performing UBER operations are described below. The embodiments described below may be performed as part of the aforementioned procedures. For example, each embodiment, such as Embodiment #1, may be performed as part of the operation of receiving the configuration information of FIGS. 11 and FIGS. 12. Each embodiment may be performed alone, or alternatively, in combination with other embodiments or other methods.

[0135] Example #1

[0136] The following embodiment describes a case where PUCCH resources for UEBR are configured by separating them according to Mode. Additionally, it is assumed that a single event is set and operated for the UE. In this case, when the corresponding event is satisfied, UEBR operation may be triggered.

[0137] When both UEBR Modes are configured for the UE, the UE cannot determine which mode to use to perform UEBR, so an operational method is required to perform UEBR in a specific mode. Below, two methods for performing UEIBR in a specific mode are described.

[0138] Method #1

[0139] The gNB can be configured and operated to allow the UE to enable only one UEBR mode for UEBR operation. In this case, changing the UEBR mode is possible through at least one of RRC reconfiguration or lower-level signaling (e.g., MAC-CE or DCI). For example, a change in the UEBR mode may be indicated by a combination of such signalings.

[0140] For example, UEBR Mode change instruction information may be indicated based on at least one of the release of RRC configuration information for existing UEBR Mode configuration information or the RRC configuration for the new UEBR Mode.

[0141] As another example, a simple mode change may be instructed based on a combination of at least one of RRC, MAC-CE, or DCI. In this case, the terminal may stop using the existing mode and perform operations for the new UEBR mode.

[0142] As another example, the use of a specific UEBR Mode may be instructed based on a combination of at least one of RRC, MAC-CE, or DCI. In this case, the terminal may perform UEBR operations in the instructed UEBR Mode. Here, any uninstructed UEBR Mode may be disabled.

[0143] Method #2

[0144] Method #1 exemplifies a method for instructing and changing the use of a single UEBR Mode. However, if both UEBR modes are enabled so that the UE can use them, or if the UE is operated to always have both UEBR modes available, UEBR operation is triggered when a configured event is satisfied, and the UE can perform UEBR operation in one of the two modes. Here, the following methods may be used to operate a specific mode.

[0145] Method #2-1: A terminal may perform UEBR by using the earliest PUCCH among the UEBR-dedicated PUCCHs available after a specific time offset from the time when the UEBR operation is triggered. Here, the PUCCH is a resource configured for a specific UEBR operation, and a specific UEBR Mode operation can be performed through the PUCCH. The specific time offset may be a time unit such as a symbol or a slot. The time offset setting may be 0 or a value greater than 0. The time offset value may be configured by including the corresponding values ​​when configuring information for the UEBR operation. That is, it may be configured as at least one or more combinations of upper-layer signaling (e.g., RRC signaling) or lower-layer signaling (e.g., MAC-CE, DCI signaling).

[0146] Method #2-2: The terminal may prioritize the use of PUCCH for Mode B operation after a specific time offset from the time when the UEBR operation is triggered. In other words, PUCCH for Mode B operation may have a high priority. Here, if there is no PUCCH dedicated to Mode B within a specific time window relative to the time of UEBR triggering, or if there is no PUCCH resource for Mode B within a specific time window after the transmission of PUCCH dedicated to Mode B, the terminal may request UL resource allocation through PUCCH dedicated to Mode A and perform the UEBR operation. That is, the terminal may switch to Mode A and perform the UEBR.

[0147] The above specific time offset may be configured in time units such as symbol, slot, etc., and the time offset setting may be set to 0 or a value greater than 0.

[0148] For convenience of explanation, a specific time window based on the triggering time of the above UEBR may be referred to as time window #1, and a specific time window after the PUCCH transmission for Mode B only may be referred to as time window #2. Time window #1 and #2 may be set to a value of 0 or greater than 0, and may be composed of the same value or different values.

[0149] At least one of the above time offset, time window #1, and time window #2 may be included in the configuration information for UEBR operation. In other words, the base station may configure at least one value of the time offset, time window #1, or time window #2 in the configuration information. That is, it may be configured as at least one or more combinations of upper-layer signaling such as RRC or lower-layer signaling such as MAC-CE and DCI.

[0150] Method #2-3: The terminal may prioritize the use of a PUCCH for Mode A operation after a specific time offset from the time when the UEBR operation is triggered. In other words, the PUCCH for Mode A operation may have a higher priority. Here, if there is no PUCCH dedicated to Mode A within a specific time window relative to the time of UEBR triggering, or if a DCI is not received within a specific time window after the transmission of a PUCCH dedicated to Mode A, the terminal may notify the use of a CG (configured grant)-PUSCH associated with the PUCCH via a PUCCH dedicated to Mode B and perform the UEBR operation. That is, the terminal may perform UEBR by changing the UBER mode to Mode B.

[0151] The above specific time offset may be a time unit such as a symbol or slot, and the time offset setting may be set to 0 or a value greater than 0.

[0152] For convenience of explanation, a specific time window based on the triggering point of the above UEBR may be referred to as time window #3, and a specific time window after the PUCCH transmission for Mode A only may be referred to as time window #4. Time windows #3 and #4 may be composed of 0 or a value greater than 0, and may be composed of the same value or different values.

[0153] At least one of the above time offset, time window #1, and time window #2 may be included in the configuration information for UEBR operation. In other words, the base station may configure at least one value of the time offset, time window #1, or time window #2 in the configuration information. That is, it may be configured as a combination of at least one or more of upper layer layers such as RRC or lower layer layers such as MAC-CE and DCI.

[0154] Method #2-4: Depending on the event that triggered the UEBR operation, the type and size of the beam information that the UE must transmit to the gNB through UEBR execution can be determined. In other words, beam reporting can be performed based on which event triggers the UEBR operation. Therefore, a specific UEBR Mode can be configured and operated to be executed based on that event, or based on the type and size of the beam information transmitted by that event.

[0155] Method #2-4-1: If beam-related information transmitted by a configured event includes information about a beam that can replace the current beam, the terminal may use the earliest PUCCH resource after a specific time offset from the UEBR triggering point. In this case, the PUCCH is a resource configured for a specific UEBR operation and can perform operations based on the UEBR Mode configured on the PUCCH.

[0156] Method #2-4-2: When the size of beam-related information transmitted by a configured event is larger than a specific size, the terminal can perform an operation based on a UEBR Mode that enables the use of a 2nd UL channel to transmit all of the beam information after a specific time offset from the UEBR triggering point.

[0157] In the case of Mode B, since CG-PUSCH is used, the size of the beam information that can be transmitted is fixed. Therefore, if the size of the beam information is smaller than the size of the data that can be transmitted through the CG-PUSCH allocated for Mode B, Mode B operation is performed. If the size of the beam information is larger than the size of the data that can be transmitted through the CG-PUSCH allocated for Mode B, a 2nd UL channel capable of transmitting all the beam information is allocated through Mode A operation, allowing for UEBR operation to be performed. Therefore, if a Mode capable of transmitting all the corresponding beam information is determined after a specific time offset following the UEBR triggering point, UEBR operation can be performed through the earliest PUCCH among the PUCCHs dedicated to that Mode.

[0158] Contrary to the operation of the above example, if the resource allocated to the CG-PUSCH assigned to the 2nd UL channel of Mode B is sufficiently large, the terminal can perform Mode A operation if the size of the beam information is below a certain size. That is, UEBR operation can be performed by allocating a PUSCH that occupies a small resource to the 2nd UL channel. If the size of the beam information is greater than a certain size, the terminal can perform Mode B operation. That is, beam information can be transmitted using the pre-configured CG-PUSCH as the 2nd UL channel. In this case as well, if a Mode is determined that can transmit all the corresponding beam information after a specific time offset from the UEBR triggering point, UEBR operation can be performed through the earliest PUCCH among the PUCCHs dedicated to that Mode.

[0159] At least one of the setting values ​​for the time offset value or the beam information size in Method #2-4 may be included and set when configuring information for UEBR operation. In other words, at least one of the setting values ​​for the time offset value or the beam information size may be included in the configuration information for UEBR operation. That is, the information for Method #2-4 may be configured as at least one or more combinations of upper-layer signaling such as RRC or lower-layer signaling such as MAC-CE and DCI.

[0160] In this embodiment, for operation such as methods #1 and #2, at least one of identification information for a UEBR mode or identification information for a UEBR configuration information may be included and operated within the configuration information for a UEBR that includes configuration information for a PUCCH resource. That is, specific ID information may be included in the configuration information to enable differentiation of UEBR modes and differentiation of each UEBR configuration information. In addition, the identification information for the UEBR mode and the identification information for the UEBR configuration information may be operated in association with CG-PUSCH configuration information that can be used as a 2nd UL channel.

[0161] In the present embodiment, regarding enable / disable instruction information for UEBR operations or UEBR modes, firstPUCCHResourceConfig-ModeA-UEBR or firstPUCCHResourceConfig-ModeB-UEBR, which are configuration information for the 1st PUCCH resource, may include enable / disable instruction information for the corresponding mode. As another example, enable / disable instruction information for each mode may be included in the RRC configuration information for the UEBR, in addition to the configuration information for each PUCCH resource mentioned above. As yet another example, at least one of the configuration information for each PUCCH resource may be operated by including a single instruction to use a specific mode.

[0162] In this embodiment, the methods can be applied and operated during UEBR operation in a simple modified, extended, or combined manner.

[0163] Example #2

[0164] This embodiment is an example in which the settings for the PUCCH resource for the UEBR are not distinguished by mode when a single event is configured and operated for the UE. When both UEBR modes are enabled so that the UE can use them, or when the UEBR is operated so that the two UEBR modes can always be used, the UEBR operation is triggered at the time when the configured event is satisfied, and the UE can perform the UEBR operation in one of the two modes by using a specific PUCCH resource. Here, at least one of the following methods may be used to operate in a specific UEBR Mode, and the following methods may include the selection of the PUCCH to be used for the UEBR.

[0165] Method #3

[0166] The terminal uses the earliest PUCCH resource after a specific time offset following the UEBR triggering point, and the UEBR mode applied to use the said PUCCH resource may be determined and operated in at least one of the following methods or a combination thereof.

[0167] Method #3-1: The terminal may perform UEBR based on the priority of a specific UEBR Mode. For example, if Mode A is set to a higher priority than Mode B, the terminal may perform Mode A operations using the earliest PUCCH after a specific time offset from the UEBR triggering point in Method #3. Conversely, if Mode B is set to a higher priority than Mode A, the terminal may perform Mode B operations using the selected PUCCH.

[0168] Method #3-2: The terminal may be configured to perform a specific mode based on the delay time value from the UEBR triggering point to the PUCCH transmission. For example, the terminal may perform Mode A if the delay time is less than or equal to a specific value, and Mode B if it is greater than or equal to a specific value. In Method #3, if the delay time to the earliest PUCCH resource after a specific time offset following the UEBR triggering point is less than or equal to a set specific value, the terminal may perform UEBR operations in Mode A using that PUCCH. If the delay time is greater than the set specific value, the terminal may perform UEBR operations in Mode B. This example can also be applied in the opposite case. That is, the terminal may be operated to perform Mode B if the delay time is less than or equal to a specific value, and Mode A if it is greater than or equal to a specific value.

[0169] Method #3-3: Based on an event that triggered the UEBR operation, the type and size of beam information that the UE must transmit to the gNB through UEBR execution can be determined. Accordingly, the terminal can be configured to perform a specific UEBR Mode depending on the event, or the type and size of beam information transmitted based on the event.

[0170] For example, if beam-related information transmitted by a configured event includes information about a beam that can replace the current beam, the terminal can be operated to use the fastest PUCCH resource after a specific time offset from the UEBR triggering point, and to perform Mode B operation through that PUCCH for UEBR operations with relatively short latency. Conversely, if Mode A operation can be performed faster than Mode B, the terminal can be operated to perform Mode A operation. In other words, the terminal can operate in a mode that can be performed relatively quickly by utilizing the fastest PUCCH resource after the time offset has elapsed.

[0171] As another example, if the size of beam-related information transmitted by a configured event is larger than a specific size, the terminal may be operated to execute a UEBR Mode that uses the earliest PUCCH resource after a specific time offset from the UEBR triggering point, while enabling the use of a 2nd UL channel capable of transmitting all the beam information. In the case of Mode B, since CG-PUSCH is used, the size of the beam information that can be transmitted is fixed. Therefore, if the size of the beam information is larger than the size of the data that can be transmitted through the CG-PUSCH allocated for Mode B, the terminal can execute UEBR by allocating a PUCCH capable of transmitting all the beam information through the execution of Mode A operation. Conversely, if the size of the beam information to be transmitted is smaller than the size of the data that can be transmitted through the CG-PUSCH allocated for Mode B, the terminal executes Mode B operation, and accordingly, the entire beam information can be transmitted.

[0172] Contrary to the operation of the above example, if the resource allocation for the CG-PUSCH allocated to the 2nd UL channel of Mode B is sufficiently large, if the size of the beam information is less than or equal to a specific size, the terminal performs Mode A operation to allocate a PUSCH occupying a small resource to the 2nd UL channel and performs UEBR operation, and if the size of the beam information is greater than or equal to a specific size, the terminal performs Mode B operation to use the pre-configured CG-PUSCH as the 2nd UL channel to transmit beam information.

[0173] Method #4

[0174] If a DCI for UEBR Mode A operation is received within a specific time window after the 1st PUCCH transmission for UEBR, and a UEBR triggering state is indicated using the CSI request field of the DCI, the terminal can perform Mode A operation. For convenience of explanation, the time window for receiving the DCI is referred to as the UEBR-DCI-time-window.

[0175] If a DCI for UEBR Mode A operation is not received within the UEBR-DCI-time-window, the terminal may perform a Mode B operation. In the above operation, the format of the DCI for UEBR Mode A operation may include at least one of DCI 0_1, 0_2, or 0_3. In the above operation, the 1st PUCCH for the UEBR may indicate a request for the allocation of a 2nd UL channel for Mode A operation, or a notification on the 2nd UL channel, such as a pre-configured CG-PUSCH for Mode B operation. In other words, the terminal 1 st via PUCCH or 1 stThe resources of the PUCCH can be used to request the base station to allocate resources for beam reporting or to notify its use. That is, the PUCCH can be used to inform the gNB that a UEBR operation has been triggered and started, and subsequently, the gNB can make a decision regarding a specific UEBR Mode operation. That is, the gNB can decide whether to transmit the DCI for a Mode A operation. If the terminal performs a Mode A operation, the gNB can transmit the DCI within the UEBR-DCI-time-window. If the terminal decides to perform a Mode B operation, the gNB may not transmit the DCI. If a Mode B operation is decided, the terminal can perform the UEBR using the earliest CG-PUSCH among the CG-PUSCHs allocated for UEBR Mode B after the UEBR-DCI-time-window.

[0176] Method #4-1: In the operation of Method #4, the following method may be additionally applied to Method #4 to support fast UEBR operation. If there is a CG-PUSCH associated with the 1st PUCCH within the UEBR-DCI-time-window after the 1st PUCCH has been transmitted, the terminal may perform Mode B operation. If there is no CG-PUSCH associated with the 1st PUCCH, the terminal may operate based on the existing Method #4.

[0177] In the above operation, if there is a CG-PUSCH associated with the 1st PUCCH within the UEBR-DCI-time-window after the 1st PUCCH transmission, the gNB may not transmit the DCI for Mode A. Nevertheless, if the UE receives the DCI for Mode A, it may ignore the DCI and perform the Mode B operation.

[0178] Method #5

[0179] The terminal uses the earliest PUCCH resource after a specific time offset following the UEBR triggering point, and the base station may configure the PUCCH resource configured for UEBR to operate in a specific UEBR Mode through at least one of upper-layer signaling such as RRC, and lower-layer signaling such as MAC-CE and DCI. In this case, the configuration method for the specific Mode for UEBR operation may be operated in cell-specific, UE-specific, BWP-specific, or CC-specific forms.

[0180] The methods in this embodiment may be applied and operated during UEBR operation in a simple modified, extended, or combined manner. In this embodiment, at least one of the time offset value, the priority by mode in Method #3-1, the configuration value for the delay time from the UEBR triggering time to the PUCCH transmission time in Method #3-2, the configuration value for the beam information size in Method #3-3, or the UEBR-DCI-time-window may be included in the information for UEBR operation. That is, it may be configured based on one or more combinations of upper-layer signaling such as RRC or lower-layer signaling such as MAC-CE and DCI.

[0181] In this embodiment, regarding enable / disable instruction information for UEBR operations or UEBR modes, firstPUCCHResourceConfig, which is configuration information for the 1st PUCCH resource, may include enable / disable instruction information for each UEBR mode. Alternatively, enable / disable instruction information for each mode may be included in the RRC configuration information for the UEBR other than the configuration information for each PUCCH resource mentioned above.

[0182] Example #3

[0183] In this embodiment, it is assumed that one or more events are configured and operated for the UE. In this case, when a specific event among the multiple events is satisfied and the UEBR is triggered, a specific UEBR mode may be executed at that time, and the specific method is as follows.

[0184] Method #6

[0185] The gNB can configure the use of a specific UEBR Mode for each event. Therefore, in a situation where multiple events are configured and operated, if a specific event is satisfied, the UEBR Mode associated with that event may be executed. In this case, to execute the UEBR Mode triggered after a specific time offset from the time the UEBR is triggered, the terminal may initiate the UEBR operation via the earliest available PUCCH.

[0186] Operation Example #1: When dedicated PUCCH resources are configured and operated for each Mode, among the dedicated PUCCHs allocated for the UEBR Mode associated with the event, the UEBR operation may be initiated through the PUCCH that is earliest after a specific time offset from the time the UEBR is triggered.

[0187] Operation Example #2: If dedicated PUCCH resources are not configured for each Mode, but instead a dedicated PUCCH resource for UEBR is configured for common use across all Modes, the UEBR Mode operation associated with the event can be performed by using the PUCCH from the dedicated UEBR resources that is earliest after a specific time offset from the time when the UEBR is triggered.

[0188] The corresponding time offset value can be configured by including these values ​​when setting information for UEBR operation. That is, it 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.

[0189] This method determines the execution of a specific UEBR Mode associated with a given event when that specific event is satisfied and triggered among multiple events. If UEBR is operated via a single event, or if the gNB configures the use of a specific event among multiple events, the specific UEBR Mode associated with that event may be configured and operated. In other words, the use of a specific UEBR Mode may be directed or enabled based on the configuration or activation of a specific event for UEBR.

[0190] In this method, some or all of the configuration information for each UEBR Mode associated with each event, or for events associated with the configuration information for each UEBR mode and operation, may be included in the information configured for UEBR operation. Additionally, such configurations may be made using one or more combinations of upper-layer signaling, such as RRC, or lower-layer signaling, such as MAC-CE and DCI. Furthermore, the configuration relationship between events and UEBR Modes may be operated by changing it to one or more combinations of upper-layer signaling, such as RRC, or lower-layer signaling, such as MAC-CE and DCI.

[0191] Method #6-1: In the case where dedicated PUCCH resources are configured and operated for each Mode as in Operation Example #1 of Method #6, among the dedicated PUCCHs allocated for the UEBR Mode associated with the event, the UEBR operation may be initiated through the PUCCH that is earliest after a specific time offset from the time the UEBR is triggered. Here, if there is no PUCCH dedicated to the corresponding UEBR Mode within a specific time window relative to the time of the UEBR triggering, the UEBR may be executed through another PUCCH dedicated to a UEBR Mode. That is, if there is no PUCCH dedicated to Mode B, UEBR Mode A may be executed through a PUCCH dedicated to Mode A. Conversely, if there is no PUCCH dedicated to Mode A, UEBR Mode B may be executed through a PUCCH dedicated to Mode B.

[0192] Method #7

[0193] Method #6 is a method that limits the UEBR Mode associated with each event to a single specific Mode. In contrast, instead of specifying a single UEBR Mode associated with each event, a priority is configured between two UEBR Modes, and operation can be performed based on this.

[0194] For example, assuming that dedicated PUCCH resources are configured and operated for each Mode, Mode A is set to a higher priority than Mode B in the UEBR Mode configuration for a specific event. At the time the UEBR is triggered, the terminal can initiate UEBR operations using the earliest available PUCCH for Mode A execution after a specific time offset. If, within a specific time window relative to the UEBR triggering time, there are no available PUCCHs for Mode A execution but there are available PUCCHs for Mode B execution, the terminal can perform Mode B operations. The same operation method is possible even when the priority for the modes is reversed. While this example illustrates a case where different UEBR Mode priorities are set for each event, such priority settings can be operated in cell-specific, UE-specific, BWP-specific, or CC-specific forms.

[0195] For convenience of explanation, specific time windows based on the triggering time of the above UEBR may be set to 0 or a value greater than 0. The above time window values ​​may be included in information for UEBR operation. That is, they may be set to one or more combinations of upper-level signaling such as RRC or lower-level signaling such as MAC-CE and DCI.

[0196] The methods in this embodiment can be applied and operated during UEBR operation in a simple modified, extended, or combined manner.

[0197] Each embodiment and the detailed methods in the embodiments described in this disclosure may be applied and operated during UEBR operation in a simple modified, extended, or combined manner.

[0198] FIG. 13 illustrates a procedure for performing beam reporting based on a mode associated with an event 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 of FIG. 11. Here, the expression 'associated' may mean that information about an event, information about a mode, or information about a resource is included in a single configuration information. For example, if information about a first event, a first mode, and a first resource is included in the first configuration information, the first mode may be referred to as a mode associated with at least one of the first event or the first resource.

[0199] Referring to FIG. 13, in step S1301, the terminal receives configuration information related to events and modes from a base station. The configuration information may include information about events and information about modes. Here, information about events may be associated with information about modes. For example, a specific event or a specific type of event indicated by information about events may be associated with a mode indicated by information about modes.

[0200] In step S1303, the terminal determines an operation mode associated with an event. For example, if an event is satisfied, the terminal may determine a mode associated with the satisfied event as an operation mode. In this case, the terminal may use a resource associated with the satisfied event or the mode associated with the event. For example, a PUCCH resource may be associated with the mode or the event.

[0201] In step S1305, the terminal may perform UEBR operations based on the determined operation mode. For example, if the operation mode is determined to be Mode A, the terminal may request resource allocation for beam reporting via PUCCH resources. As another example, if the operation mode is determined to be Mode B, the terminal may notify to perform beam reporting via PUCCH resources.

[0202] FIG. 14 illustrates a resource utilization procedure for beam reporting according to a mode according to one embodiment of the present disclosure. The procedure of FIG. 14 may be performed by a terminal. The procedure of FIG. 14 may be part of the procedure of FIG. 11. The procedure of FIG. 14 may be performed in combination with the procedure of FIG. 13.

[0203] Referring to FIG. 14, in step S1401, the terminal receives configuration information related to resources and modes from a base station. The configuration information may include information regarding resources and information regarding modes. For example, information regarding resources may be associated with information regarding modes. Information regarding modes may include information indicating an operating mode. Information regarding resources may include at least one of information regarding PUCCH resources or information regarding PUSCH resources. The content of information regarding resources may be changed based on information regarding modes. For example, if information regarding modes indicates Mode A as the operating mode, information regarding resources may include information regarding PUCCH resources. As another example, if information regarding modes indicates Mode B as the operating mode, information regarding resources may include information regarding PUCCH resources and information regarding PUSCH resources. As yet another example, information regarding resources may indicate resources related to Mode A and resources related to Mode B, and the terminal may use at least some of the indicated resources according to the operating mode.

[0204] In step S1403, the terminal can determine an operation mode. The operation mode may be a mode indicated by the configuration information. Alternatively, the operation mode may be determined as one of the modes indicated by the configuration information. For example, the operation mode may be determined as a mode associated with an event in which a condition is satisfied, among the modes indicated by the configuration information.

[0205] In step S1405, the terminal transmits signaling via PUCCH based on the operation mode and configuration information. For example, the terminal may transmit signaling using a resource indicated by information regarding the resource. For example, if the operation mode is Mode A, the terminal may transmit signaling using a PUCCH resource associated with Mode A. If the operation mode is Mode B, the terminal may transmit signaling using a PUCCH resource associated with Mode B. Alternatively, the PUCCH resources associated with Mode A and Mode B may be the same, and the terminal may transmit signaling using a PUCCH resource regardless of the operation mode.

[0206] In step S1407, the terminal may transmit a beam report based on the operation mode. If the operation mode is Mode A, the terminal may transmit a beam report through a resource allocated based on the signaling transmitted in step S1405. If the operation mode is Mode B, the terminal may transmit a beam report through a resource indicated by the configuration information. For example, the terminal may transmit a beam report using a PUSCH resource indicated by the configuration information. Here, the PUSCH resource indicated by the configuration information may be referred to as a PUSCH resource pre-configured by the configuration information or a PUSCH resource pre-defined by the configuration information.

[0207] FIG. 15 illustrates a procedure for transmitting signaling using a configured resource according to one embodiment of the present disclosure. The procedure of FIG. 15 can be performed by a terminal.

[0208] Referring to FIG. 15, in step S1501, the terminal determines an operation mode. The operation mode may be determined based on an event. Alternatively, the operation mode may be determined based on configuration information received from a base station. The operation mode may be Mode A or Mode B.

[0209] In step S1503, the terminal may determine a resource for signaling based on an operation mode. For example, the terminal may determine a PUCCH resource associated with the mode determined as the operation mode. Among the PUCCH resources, the terminal may determine the earliest PUCCH resource after a time offset has elapsed from the triggering point as the resource for signaling. Here, the time offset may be 0 or a value greater than that. Alternatively, the time offset may not be set. In this case, the terminal may determine the earliest PUCCH resource from the triggering point as the resource for signaling. The earliest PUCCH resource may be referred to as the earliest PUCCH occasion.

[0210] In step S1505, the terminal transmits a signaling using the determined resources. Here, the signaling may be generated based on the operation mode. For example, if the operation mode is Mode A, the signaling may be for requesting resource allocation. As another example, if the operation mode is Mode B, the signaling may be for notifying that a beam report will be performed.

[0211] FIG. 16 illustrates a mode change procedure based on a time window according to one embodiment of the present disclosure. The procedure of FIG. 16 can be performed by a terminal.

[0212] Referring to FIG. 16, in step S1601, the terminal receives configuration information. The configuration information may include information regarding a time window.

[0213] In step S1603, the terminal determines an operation mode. The operation mode may be determined as a mode associated with an event. Alternatively, the operation mode may be determined based on configuration information.

[0214] In step S1605, the terminal determines a resource for signaling within a time window. The terminal may determine a resource associated with an operation mode among the resources within the time window as a resource for signaling. If there is no resource associated with an operation mode among the resources within the time window, the terminal may perform step S1607.

[0215] In step S1607, the terminal changes the operation mode. The operation mode may be changed to a mode in which an associated resource exists among the resources within the time window.

[0216] In step S1609, the terminal performs UEBR operations based on the operation mode. Based on the operation mode, the terminal can perform signaling using PUCCH resources and beam reporting using PUSCH resources.

[0217] The procedures of FIGS. 12 through 16 described above may be performed in combination. In this case, the configuration information may include multiple configuration information containing different information. In other words, the base station may transmit different configuration information to the terminal multiple times. Alternatively, the base station may change the configuration information or transmit additionally using an RRC reset message.

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

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

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

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

[0222] 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

1. In a method of operation of a terminal in a wireless communication system, A step of receiving at least one configuration information including first configuration information from a base station; A step of determining the satisfaction of a first event set by the first configuration information above; A step of triggering a UEBR (UE initiated beam report) operation based on the satisfaction of the above first event; A step of determining an operation mode for the UEBR operation based on the first configuration information above; A step of transmitting signaling using a first PUCCH (physical uplink control channel) resource indicated by the first configuration information; and Based on the above signaling, the method includes the step of transmitting a beam report, The above operation mode includes mode A or mode B, and A method in which the above first configuration information is set by association with the type of the above first event and the above first PUCCH resource.

2. In Paragraph 1, A method in which the content of the above signaling is determined based on the above operation mode.

3. In Paragraph 2, The above signaling includes information requesting resources for beam reporting when the above operation mode is mode A, and A method including information notifying that a beam report is scheduled to be performed when the above operation mode is mode B.

4. In Paragraph 1, A method further comprising the step of receiving downlink control information (DCI) containing information about resources for beam reporting from a base station when the above operating mode is mode A.

5. In Paragraph 4, The above beam report is, When the above operation mode is mode A, it is transmitted based on the resource indicated by the DCI, and A method in which, when the above operation mode is mode B, a PUSCH resource indicated by the first configuration information is transmitted.

6. In Paragraph 1, Each of the above at least one configuration information includes at least one of information about an event, information about a UEBR mode, information about a resource, information about a reference signal, information about a time offset, or information about a time window, and A method in which information about the above event, information about the above UEBR mode, and information about the above resource are associated.

7. In Paragraph 6, A method in which information regarding the above event includes information indicating the type of the event.

8. In Paragraph 6, Information regarding the above resources includes information regarding PUCCH resources.

9. In Paragraph 6, Information regarding the above resources includes a method for including information regarding PUSCH resources.

10. In Paragraph 1, The above signaling is transmitted at the earliest PUCCH opportunity (occasion) at a time when a time offset from the triggering time has elapsed among the first PUCCH resources.

11. In a method of operation of a base station in a wireless communication system, A step of transmitting at least one configuration information including a first configuration information to a terminal; Based on the first configuration information above, a step of receiving signaling from the terminal; and Based on the above signaling, the method includes the step of receiving a beam report, The above beam report is transmitted by the terminal based on an operation mode determined based on the first configuration information, and The above signaling is received using a first PUCCH resource indicated by the first configuration information, and The above operation mode includes mode A or mode B, and A method in which the above first configuration information is set by association with the type of the first event and the above first PUCCH resource.

12. In Paragraph 11, A method in which the content of the above signaling is determined based on the above operation mode.

13. In Paragraph 12, The above signaling includes information requesting resources for beam reporting when the above operation mode is mode A, and A method including information notifying that a beam report is scheduled to be performed when the above operation mode is mode B.

14. In Paragraph 11, A method further comprising the step of transmitting DCI (Downlink control information) for allocating resources for beam reporting when the above operating mode is mode A.

15. In Paragraph 11, A method in which, when the above operating mode is mode B, the beam report is received using a PUSCH resource indicated by the above configuration information.

16. In Paragraph 11, Each of the above-mentioned at least one configuration information includes at least one of information about an event, information about a UEBR (UE initiated beam report) mode, information about a resource, information about a reference signal, information about a time offset, or information about a time window. A method in which information about the above event, information about the above UEBR mode, and information about the above resource are associated.

17. 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 at least one configuration information including first configuration information from a base station; A step of determining the satisfaction of a first event set by the first configuration information above; A step of triggering a UEBR (UE initiated beam report) operation based on the satisfaction of the above first event; A step of determining an operation mode for the UEBR operation based on the first configuration information above; A step of transmitting signaling using a first PUCCH (physical uplink control channel) resource indicated by the first configuration information; and Based on the above signaling, the method includes the step of transmitting a beam report, The above operation mode includes mode A or mode B, and The above first configuration information is configured by association with the type of the first event and the first PUCCH resource, a terminal.

18. 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 at least one configuration information including a first configuration information to a terminal; Based on the first configuration information above, a step of receiving signaling from the terminal; and Based on the above signaling, the method includes the step of receiving a beam report, The above beam report is transmitted by the terminal based on an operation mode determined based on the first configuration information, and The above signaling is received using a first PUCCH resource indicated by the first configuration information, and The above operation mode includes mode A or mode B, and The above first configuration information is a base station configured in association with the type of the above first event and the above first PUCCH resource.

Images