Method and device for terminal-driven beam reporting considering cross-component carrier operation

Abstract

A method of a terminal may include the steps of: detecting at least one event; transmitting a first UL channel to a base station in a first CC when the at least one event is detected; receiving DCI for allocating a UL resource of a second CC for transmitting a beam report according to the at least one event from the base station on the basis of the first UL channel in the first CC or the second CC; and transmitting a second UL channel including the beam report by using the UL resource in the second CC, wherein the first UL channel may include multi-bit information, and the multi-bit information may include information related to cross-CC scheduling.

Description

Terminal-driven beam reporting method and device considering cross-component carrier operation

[0001] The present invention relates to a beam management method in a mobile communication system, and more particularly, to a UE-initiated / event-driven beam reporting method considering cross-component carrier operation and a device therefor.

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

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

[0004] Meanwhile, 3GPP (3 rd In Release-19 of the Generation Partnership Project, standardization of user equipment-initiated (UEI) / event-driven (ED) beam management is underway to resolve the problems of conventional network-driven beam management. Unlike conventional network-driven beam management, UE-initiated / event-driven beam management is a method in which UEs proactively perform beam management because they can recognize the current beam status and beam change trends relatively quickly compared to base stations. However, in UE-initiated / event-driven beam management, specific beam reporting operations that take cross-component carrier scheduling situations into account have not yet been defined.

[0005] The purpose of the present disclosure to solve the above problems is to provide a UE-initiated / event-driven beam reporting method and a device therefor that takes cross-component carrier operation into account.

[0006] According to embodiments of the present disclosure for achieving the above object, a method of a terminal may include: transmitting information related to cross-component carrier (CC) scheduling to a base station; detecting at least one event; transmitting a first uplink (UL) channel from a first CC to the base station when the at least one event is detected; receiving downlink control information (DCI) from the first CC or the second CC, which allocates UL resources of a second CC for transmitting a beam report according to the at least one event from the base station based on the first UL channel and the information related to the cross-CC scheduling; and transmitting a second UL channel including the beam report from the second CC using the UL resources.

[0007] The first CC and the second CC may be contiguous CCs within the same band (intra-band), non-contiguous CCs within the same band, or CCs of different bands (inter-band).

[0008] The information related to the above cross-CC scheduling may include information that the terminal requests cross-CC scheduling for the beam report to the base station or information on whether the terminal supports cross-CC scheduling.

[0009] The information related to the cross-CC scheduling may include at least one of information about a CC on which the second UL channel is to be transmitted, information about a reference signal (RS) corresponding to a new beam according to the at least one event, information about an RS corresponding to a current beam according to the at least one event, information about a band(s) of CCs, or information about a maximum number of CCs.

[0010] The first CC and the second CC are different from each other, and the current beam according to the at least one event and the new beam according to the at least one event may belong to the first CC.

[0011] The first CC and the second CC are different from each other, and the current beam according to the at least one event may belong to the first CC, and the new beam according to the at least one event may belong to the second CC.

[0012] The first CC and the second CC are identical, and the current beam according to the at least one event may belong to the first CC, and the new beam according to the at least one event may belong to the third CC.

[0013] The quality of the current beam according to at least one of the above events may be measured based on a quasi-co-location (QCL) reference signal for the indicated transmission configuration indication (TCI) state, or based on a quasi-co-located (QCL) synchronization signal block (SSB) for the indicated TCI state.

[0014] The quality of the current beam and the quality of the new beam according to at least one of the above events can be measured by reference signals of the same type.

[0015] According to embodiments of the present disclosure for achieving the above object, a method of a base station may include: receiving information related to cross-component carrier (CC) scheduling from a terminal; receiving a first uplink (UL) channel from a first CC from a terminal that detects at least one event; transmitting downlink control information (DCI) for allocating UL resources of a second CC for receiving a beam report according to the at least one event, from the first CC or the second CC to the terminal based on the first UL channel and the information related to the cross-CC scheduling; and receiving a second UL channel including the beam report from the second CC using the UL resources.

[0016] The first CC and the second CC may be contiguous CCs within the same band (intra-band), non-contiguous CCs within the same band, or CCs of different bands (inter-band).

[0017] The information related to the above cross-CC scheduling may include information that the terminal requests cross-CC scheduling for the beam report to the base station or information on whether the terminal supports cross-CC scheduling.

[0018] The information related to the cross-CC scheduling may include at least one of information about a CC on which the second UL channel is to be transmitted, information about a reference signal (RS) corresponding to a new beam according to the at least one event, information about an RS corresponding to a current beam according to the at least one event, information about a band(s) of CCs, or information about a maximum number of CCs.

[0019] The first CC and the second CC are different from each other, and the current beam according to the at least one event and the new beam according to the at least one event may belong to the first CC.

[0020] The first CC and the second CC are different from each other, and the current beam according to the at least one event may belong to the first CC, and the new beam according to the at least one event may belong to the second CC.

[0021] The first CC and the second CC are identical, and the current beam according to the at least one event may belong to the first CC, and the new beam according to the at least one event may belong to the third CC.

[0022] According to embodiments of the present disclosure for achieving the above object, a terminal may include at least one processor, and the at least one processor may cause the terminal to perform the steps of: transmitting information related to cross-component carrier (CC) scheduling to a base station; detecting at least one event; transmitting a first uplink (UL) channel on a first CC to the base station when the at least one event is detected; receiving downlink control information (DCI) from the first CC or the second CC, which allocates UL resources of a second CC for transmitting a beam report according to the at least one event from the base station based on the first UL channel and the information related to the cross-CC scheduling; and transmitting a second UL channel including the beam report on the second CC using the UL resources.

[0023] The information related to the above cross-CC scheduling may include information that the terminal requests cross-CC scheduling for the beam report to the base station or information on whether the terminal supports cross-CC scheduling.

[0024] The information related to the cross-CC scheduling may include at least one of information about a CC on which the second UL channel is to be transmitted, information about a reference signal (RS) corresponding to a new beam according to the at least one event, information about an RS corresponding to a current beam according to the at least one event, information about a band(s) of CCs, or information about a maximum number of CCs.

[0025] The first CC and the second CC are different from each other, and the current beam according to the at least one event and the new beam according to the at least one event may belong to the first CC, or the current beam according to the at least one event may belong to the first CC and the new beam according to the at least one event may belong to the second CC.

[0026] Using embodiments of the present disclosure, signaling for beam reporting operations between a terminal and a base station for performing terminal-driven / event-based beam management can be efficiently performed. In particular, applying cross-component carrier scheduling to beam reporting operations can improve the resource efficiency of a communication system and distribute the load among component carriers. Therefore, rapid and stable beam management can be enabled in the communication system, and the overall performance of the communication system can be improved.

[0027] Figure 1 is a conceptual diagram illustrating a first embodiment of a communication system.

[0028] Figure 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.

[0029] Figure 3 is a block diagram illustrating a first embodiment of communication nodes performing communication.

[0030] Figure 4a is a block diagram illustrating a first embodiment of a transmission path.

[0031] Figure 4b is a block diagram illustrating a first embodiment of a receiving path.

[0032] Figure 5 is a conceptual diagram illustrating a first embodiment of a system frame in a communication system.

[0033] Figure 6 is a conceptual diagram illustrating a first embodiment of a subframe in a communication system.

[0034] Figure 7 is a conceptual diagram illustrating a first embodiment of a slot in a communication system.

[0035] Figure 8 is a conceptual diagram illustrating a first embodiment of time-frequency resources in a communication system.

[0036] Figure 9 is a flowchart for explaining Mode A operation to which embodiments of the present invention are applied.

[0037] Figure 10 is a flowchart for explaining Mode B operation to which embodiments of the present invention are applied.

[0038] FIG. 11 is a flowchart for explaining a cross-CC beam reporting operation according to one embodiment of the present invention.

[0039] FIG. 12 is a flowchart for explaining a cross-CC beam reporting operation according to another embodiment of the present invention.

[0040] FIG. 13 is a flowchart illustrating a cross-CC beam reporting operation according to another embodiment of the present invention.

[0041] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.

[0042] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" may refer to a combination of multiple related items described herein or to any of multiple related items described herein.

[0043] 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 combinations of one or more 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 combinations of one or more of A and B.”

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

[0045] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0046] The terminology used in this disclosure is only used to describe specific embodiments and is not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

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

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

[0049] In an embodiment, even if a method (e.g., transmitting or receiving a signal) performed by a first communication node among communication nodes is described, a corresponding second communication node can perform a method (e.g., receiving or transmitting a signal) corresponding to the method performed by the first communication node. That is, if an operation of a UE (user equipment) is described, a corresponding base station can perform an operation corresponding to the operation of the UE. Conversely, if an operation of a base station is described, a corresponding UE can perform an operation corresponding to the operation of the base station.

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

[0051] 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 a transmission and reception operation of system information (e.g., a master information block (MIB), a system information block (SIB)) and / or an RRC message. MAC signaling may refer to a transmission and reception operation of a MAC control element (CE). PHY signaling may refer to a transmission and reception operation of control information (e.g., downlink control information (DCI), uplink control information (UCI), sidelink control information (SCI)).

[0052] In the present disclosure, “an operation (e.g., a transmission operation) is set” may mean that “setting information for the operation (e.g., an information element, a parameter)” and / or “information instructing the performance of the operation” is signaled. “An information element (e.g., a parameter) is set” may mean that the information element is signaled. In the present disclosure, “a signal and / or a channel” may mean a signal, a channel, or “a signal and a channel,” and a signal may be used to mean “a signal and / or a channel.”

[0053] The communication network to which the embodiment is applied is not limited to what is described below, and the embodiment may be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, the communication network may be used in the same sense as the communication system.

[0054] Figure 1 is a conceptual diagram illustrating a first embodiment of a communication system.

[0055] 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). In addition, the communication system (100) may further include a core network (e.g., a serving-gateway (S-GW), a packet data network (PDN)-gateway (P-GW), a mobility management entity (MME)). 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.

[0056] A plurality of communication nodes (110 to 130) can support a communication protocol (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.) specified in the 3GPP (3rd generation partnership project) standard. The plurality of communication nodes (110 to 130) may 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 plurality of communication nodes may have the following structure.

[0057] Figure 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.

[0058] Referring to FIG. 2, a communication node (200) may include at least one processor (210), a memory (220), and a transmission / reception device (230) that is connected to a network and performs communication. In addition, the communication node (200) may further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the communication node (200) may be connected by a bus (270) and communicate with each other.

[0059] The processor (210) can execute program commands stored in at least one of the memory (220) and the storage device (260). The processor (210) may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor in which the methods according to embodiments of the present disclosure are performed. Each of the memory (220) and the storage device (260) may be configured with at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be configured with at least one of a read-only memory (ROM) and a random access memory (RAM).

[0060] Referring again to FIG. 1, the communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) may form a macro cell. Each of the fourth base station (120-1) and the fifth base station (120-2) may form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) may be within the cell coverage of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) may be within the cell coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be within the cell coverage of the third base station (110-3). The first terminal (130-1) may be within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the cell coverage of the fifth base station (120-2).

[0061] Here, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as a NodeB (NB), an evolved NodeB (eNB), a gNB, an advanced base station (ABS), a high reliability-base station (HR-BS), a base transceiver station (BTS), a radio base station, a radio transceiver, an access point, an access node, a radio access station (RAS), a mobile multihop relay-base station (MMR-BS), a relay station (RS), an advanced relay station (ARS), a high reliability-relay station (HR-RS), a home NodeB (HNB), a home eNodeB (HeNB), a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmission and reception point (TRP), etc.

[0062] Each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as a user equipment (UE), terminal equipment (TE), advanced mobile station (AMS), high reliability-mobile station (HR-MS), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, on board unit (OBU), etc.

[0063] Meanwhile, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in a different frequency band or may operate in the same frequency band. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to each other via an ideal backhaul link or a non-ideal backhaul link, and may exchange information with each other via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to the core network via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit a signal received from the core network to the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), and can transmit a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) to the core network.

[0064] Additionally, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may support MIMO transmission (e.g., single user (SU)-MIMO, multi user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, sidelink communication (e.g., device to device communication (D2D), proximity services (ProSe)), Internet of Things (IoT) communication, dual connectivity (DC), etc. Here, each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) can perform an operation corresponding to the base station (110-1, 110-2, 110-3, 120-1, 120-2) and an operation supported by the base station (110-1, 110-2, 110-3, 120-1, 120-2). For example, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) based on the SU-MIMO scheme, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) by the SU-MIMO scheme. Alternatively, the second base station (110-2) can transmit signals to the fourth terminal (130-4) and the fifth terminal (130-5) based on the MU-MIMO method, and each of the fourth terminal (130-4) and the fifth terminal (130-5) can receive signals from the second base station (110-2) based on the MU-MIMO method.

[0065] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP scheme, and the fourth terminal (130-4) can receive a signal from the first base station (110-1), the second base station (110-2), and the third base station (110-3) based on the CoMP scheme. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive a signal with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage based on the CA scheme. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can control sidelink communication between the fourth terminal (130-4) and the fifth terminal (130-5), and each of the fourth terminal (130-4) and the fifth terminal (130-5) can perform sidelink communication under the control of the second base station (110-2) and the third base station (110-3), respectively.

[0066] Meanwhile, communication nodes performing communication in a communication network may be configured as follows. The communication node illustrated in Fig. 3 may be a specific embodiment of the communication node illustrated in Fig. 2.

[0067] Figure 3 is a block diagram illustrating a first embodiment of communication nodes performing communication.

[0068] Referring to FIG. 3, each of the first communication node (300a) and the second communication node (300b) may be a base station or a UE. The first communication node (300a) may transmit a signal to the second communication node (300b). The 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 the controller (316). The control information may include at least one of system information, RRC configuration information (e.g., information configured by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

[0069] The transmitting processor (311) may perform a processing operation on data (e.g., an encoding operation, a symbol mapping operation, etc.) to generate data symbol(s). The transmitting processor (311) may perform a processing operation on control information (e.g., an encoding operation, a symbol mapping operation, etc.) to generate control symbol(s). In addition, the transmitting processor (311) may generate synchronization / reference symbol(s) for a synchronization signal and / or a reference signal.

[0070] The Tx MIMO processor (312) may perform a spatial processing operation (e.g., a precoding operation) on data symbol(s), control symbol(s), and / or synchronization / reference symbol(s). The output (e.g., a symbol stream) of the Tx MIMO processor (312) may be provided to modulators (MODs) included in the transceivers (313a to 313t). The modulators (MODs) may perform a processing operation on the symbol stream to generate modulation symbols, and may perform an additional processing operation (e.g., an analog conversion operation, an amplification operation, a filtering operation, an upconversion operation) on the modulation symbols to generate signals. The signals generated by the modulators (MODs) of the transceivers (313a to 313t) may be transmitted via the antennas (314a to 314t).

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

[0072] Meanwhile, the second communication node (300b) can transmit a signal to the first communication node (300a). The transmitting processor (368) included in the second communication node (300b) can receive data (e.g., data units) from a data source (367) and perform a processing operation on the data to generate data symbol(s). The transmitting processor (368) can receive control information from the controller (366) and perform a processing operation on the control information to generate control symbol(s). In addition, the transmitting processor (368) can perform a processing operation on a reference signal to generate reference symbol(s).

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

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

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

[0076] FIG. 4a is a block diagram illustrating a first embodiment of a transmission path, and FIG. 4b is a block diagram illustrating a first embodiment of a reception path.

[0077] Referring to FIGS. 4A and 4B, a transmission path (410) may be implemented in a communication node that transmits a signal, and a reception path (420) may be implemented in 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 (512), 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 receiving 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 may be a natural number.

[0078] In the transmission path (410), information bits may be input to a channel coding and modulation block (411). The channel coding and modulation block (411) may perform a coding operation (e.g., a low-density parity check (LDPC) coding operation, a polar coding operation, etc.) and a modulation operation (e.g., a quadrature phase shift keying (QPSK), a quadrature amplitude modulation (QAM), etc.) on the information bits. The output of the channel coding and modulation block (411) may be a sequence of modulation symbols.

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

[0080] The CP addition block (415) can insert a CP into a 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 at the baseband before up-conversion.

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

[0082] In FIGS. 4A and 4B , Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. Each of the blocks (e.g., components) in FIGS. 4A and 4B may be implemented by at least one of hardware, software, or firmware. For example, some of the blocks in FIGS. 4A and 4B 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 , a block may be subdivided into multiple blocks, multiple blocks may be integrated into a single block, some blocks may be omitted, and blocks supporting other functions may be added.

[0083] Figure 5 is a conceptual diagram illustrating a first embodiment of a system frame in a communication system.

[0084] Referring to FIG. 5, time resources in a communication system can be divided into frame units. 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 (milliseconds). 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 the system frame after system frame #1023 can be #0.

[0085] A system frame may include two half frames. A half frame may be 5 ms long. 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 include 10 subframes. A subframe may be 1 ms long. The 10 subframes within a system frame may be referred to as "subframes #0-9."

[0086] Figure 6 is a conceptual diagram illustrating a first embodiment of a subframe in a communication system.

[0087] Referring to FIG. 6, one subframe may include n slots, where n may be a natural number. Accordingly, one subframe may be composed of one or more slots.

[0088] Figure 7 is a conceptual diagram illustrating a first embodiment of a slot in a communication system.

[0089] Referring to Figure 7, a single slot may include one or more symbols. A single slot illustrated in Figure 7 may include 14 symbols. The length of a slot may vary depending on the number and length of symbols contained in the slot. Alternatively, the length of a slot may vary depending on the numerology.

[0090] In a communication system, the numerology applied to physical signals and channels may be variable. The numerology may be variable to meet various technical requirements of the communication system. In a communication system applying CP (cyclic prefix)-based OFDM waveform technology, the numerology may include subcarrier spacing and CP length (or CP type). Table 1 may be a first embodiment of a method for configuring a numerology for a CP-OFDM-based communication system. At least some of the numerologies in Table 1 may be supported depending on the frequency band in which the communication system operates. In addition, the communication system may additionally support numerologies not listed in Table 1.

[0091] Subcarrier spacing 15kHz 30kHz 60kHz 120kHz 240kHz 480kHz OFDM symbol length (㎲) 66.733.316.78.34.22.1 CP length (㎲) 4.762.381.190.600.300.151 Number of OFDM symbols in ㎳ 142856112224448

[0092]

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

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

[0095] A symbol may be configured as a downlink (DL) symbol, a flexible (FL) symbol, or an uplink (UL) symbol. A slot consisting solely of DL symbols may be referred to as a "DL slot," a slot consisting solely of FL symbols may be referred to as an "FL slot," and a slot consisting solely of UL symbols may be referred to as a "UL slot."

[0096] The slot format can be semi-statically configured by higher layer signaling (e.g., RRC signaling). Information indicating the semi-static slot format can be included in the system information, and the semi-static slot format can be configured cell-specifically. In addition, the semi-static slot format can be additionally configured for each terminal through terminal-specific higher layer signaling (e.g., RRC signaling). The flexible symbol of the cell-specifically configured slot format can be overridden to a downlink symbol or an uplink symbol by terminal-specific higher layer signaling. In addition, the slot format can be dynamically indicated by physical layer signaling (e.g., a slot format indicator (SFI) included in DCI). The semi-statically configured slot format can be overridden by a dynamically indicated slot format. For example, the semi-statically configured flexible symbol can be overridden to a downlink symbol or an uplink symbol by the SFI.

[0097] The reference signal may be a channel state information-reference signal (CSI-RS), a sounding reference signal (SRS), a demodulation-reference signal (DM-RS), a phase tracking-reference signal (PT-RS), etc. The channel may be a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), etc. In the present disclosure, a control channel may mean a PDCCH, a PUCCH, or a PSCCH, and a data channel may mean a PDSCH, a PUSCH, or a PSSCH.

[0098] Figure 8 is a conceptual diagram illustrating a first embodiment of time-frequency resources in a communication system.

[0099] 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 may be defined as a "RE (resource element)". Resources consisting of one OFDM symbol in the time domain and K subcarriers in the frequency domain may be defined as a "REG (resource element group)". A REG may include K REs. A REG may be used as a basic unit for resource allocation in the frequency domain. K may be a natural number. For example, K may be 12. N may be a natural number. In the slot illustrated in FIG. 7, N may be 14. N OFDM symbols may be used as a basic unit for resource allocation in the time domain.

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

[0101] Downlink data can be transmitted via the PDSCH. The base station can transmit PDSCH configuration information (e.g., scheduling information) to the terminal via the PDCCH. The terminal can obtain the PDSCH configuration information by receiving the PDCCH (e.g., downlink control information (DCI)). For example, the PDSCH configuration information can include the MCS (modulation coding scheme) 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. The PDSCH can refer to a radio resource through which downlink data is transmitted and received. Alternatively, the PDSCH can refer to the downlink data itself. The PDCCH can refer to a radio resource through which downlink control information (e.g., DCI) is transmitted and received. Alternatively, the PDCCH can refer to the downlink control information itself.

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

[0103] 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. The PDCCH occasion may be a region where the PDCCH can exist. That is, the PDCCH occasion may be a region where DCI can be transmitted. The PDCCH occasion may be referred to as a PDCCH candidate. The 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 symbol units. In the frequency domain, the size of the PDCCH occasion may be indicated in RB units (e.g., in PRB (physical resource block) units or CRB (common resource block) units).

[0104] The search space information may include a coreset identifier (ID) associated with the search space, a period of PDCCH monitoring, and / or an offset. The period and offset of PDCCH monitoring may each be indicated on a slot-by-slot basis. In addition, the search space information may further include an index of the symbol at which the PDCCH monitoring operation begins.

[0105] A base station can configure a bandwidth part (BWP) for downlink communication. The BWP can be configured differently for each terminal. The base station can inform the terminal of the BWP configuration information using higher layer signaling. The higher layer signaling can mean "transmission operation of system information" and / or "transmission operation of RRC (radio resource control) message." The number of BWPs configured for one terminal can be one or more. The terminal can receive BWP configuration information from the base station and check the BWP(s) configured by the base station based on the BWP configuration information. When multiple BWPs are configured for downlink communication, the base station can activate one or more BWPs among the multiple BWPs. The base station can transmit the configuration information of the activated BWP(s) to the terminal using at least one of higher layer signaling, a medium access control (MAC) control element (CE), or DCI. The base station can 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 perform a downlink reception operation in the activated BWP(s).

[0106]

[0107] Discussions are underway to improve intra-cell and inter-cell beam management, based on the work item description (WID) for 3GPP Rel-19 NR MIMO discussions. These improvements primarily target FR2 bands and single transmission / reception point (sTRP) scenarios, leveraging existing legacy CSI measurement and reporting configuration procedures while reducing overhead and latency.

[0108] To this end, UE-initiated (UEI) / event-driven (ED) beam management procedures are being discussed. The beam management methods defined up to Rel-18 were network-based. In other words, in network-initiated beam management, the network (i.e., the base station) can instruct the terminal to switch to a specific beam for DL ​​reception or UL transmission. In this case, the base station receives a measurement report from the terminal and issues an instruction based on the measurement report, so the base station cannot determine the optimal beam until it receives the measurement report transmitted by the terminal.

[0109] If beam management operations are initiated from the terminal side, which can first detect beam changes, delay time (e.g., time required for a base station to instruct a terminal to perform a measurement report and for a terminal to receive a measurement report based on the instruction) and signal overhead (e.g., overhead of a signal from a network to instruct a terminal to perform a measurement report) can be reduced compared to network-based beam management operations.

[0110]

[0111] Meanwhile, at the 3GPP RAN 1 meetings (RAN #116 and RAN #116-bis), outline beam report transmission procedures for UEI / ED beam reporting were approved.

[0112] First, the beam report transmission procedure is largely divided into Mode A and Mode B, and the outline of the procedure for each mode is as follows.

[0113] First, Mode A is a method of dynamically scheduling uplink control information (UCI) for beam reporting by the base station, and can be performed in the following three steps.

[0114] Step 1: The terminal may transmit the first UL channel requesting resources for the second UL channel for transmitting the beam report. The first UL channel consists of a PUCCH (i.e., the first PUCCH) containing single-bit information or multi-bit information, and the PUCCH may follow the existing SR (scheduling request terminal st) type or a new UCI type.

[0115] Step 2: The terminal can detect the DCI format indicating the resources of the second UL channel. In this case, no new DCI format is introduced.

[0116] Step 3: The terminal can transmit a beam report on a second UL channel. In this case, the second UL channel can be PUCCH, PUSCH, or both.

[0117] Mode A is a basic function of the terminal, and all terminals that support UEI / ED beam reporting must support this function.

[0118] Meanwhile, Mode B is a method of transmitting UCI on pre-configured resources for the second UL channel, and can be performed in the following two-step operation.

[0119] Step 1: The UE may transmit a first UL channel notifying that a beam report will be transmitted on a second UL channel. The first UL channel may consist of a PUCCH (i.e., the first PUCCH) containing single-bit information or multi-bit information, and the PUCCH may follow the existing SR (scheduling request terminal st) type or a new UCI type.

[0120] Step 2: The terminal can transmit a beam report on a second UL channel. As in Mode A, the second UL channel can be PUCCH, PUSCH, or both.

[0121] In Mode B, notifications in step 1 and beam reports in step 2 are transmitted as separate reporting instances, and it is not determined whether the terminal receives confirmation information in response to each step in Modes A and B.

[0122] Additionally, cross-CC (component carrier) beam reporting can be supported in both Mode A and Mode B in the above procedures.

[0123]

[0124] Meanwhile, the following events are being discussed as events that trigger the above-described UEI / ED beam report.

[0125] -Event-1: The quality of the current beam (e.g. L1-RSRP, etc.) falls below a certain threshold.

[0126] -Event-2: The quality of at least one new beam is improved by a threshold amount compared to the current beam.

[0127] -Event-3: The quality of the new beam exceeds a certain threshold.

[0128] -Event-4: The quality of the current beam becomes lower than threshold 1, and the quality of at least one new beam becomes higher than threshold 2.

[0129] -Event-5: The absolute value of the difference between the quality of the current beam and the quality of at least one new beam becomes less than a certain threshold.

[0130] -Event-6: The current beam is not included in the top K(>1) beams configured for measurement and reporting.

[0131] -Event-7a: The quality of at least one new beam (e.g. L1-RSRP) improves by a certain threshold compared to the quality derived from the lowest quality RS among the active TCI states.

[0132] -Event-7b: The quality of at least one new beam (e.g. L1-RSRP) improves by a certain threshold compared to the quality derived from the highest quality RS among the active TCI states.

[0133] -Event-8: The quality of M(>1) new beams (e.g. L1-RSRP) is improved by a certain threshold compared to the current beam.

[0134] -Event-9: The quality of at least one new beam (e.g. L1-RSRP) is improved by a certain threshold compared to the configured reference RS (possibly SSB or CSI-RS).

[0135]

[0136] As described above, for UEI / ED beam reporting operation, a process of transmitting information from the terminal to the base station (Step 1) is required in all modes. In Mode A, where resources for beam reporting are not pre-allocated, the terminal can request resources for beam reporting from the base station. In Mode B, where resources for beam reporting are pre-allocated, the terminal can notify the base station that it will use the pre-allocated resources for beam reporting. In Step 1, the terminal can transmit the information to the base station via the PUCCH, and the information can be composed of 1-bit information or multi-bit information. If the information is composed of 1 bit, the information can be simply information requesting resources from the base station or information notifying that pre-allocated resources will be used. On the other hand, if the information is composed of multi-bit information, the information can be utilized for various purposes in addition to information requesting resources or information notifying that pre-allocated resources will be used.

[0137]

[0138] Figure 9 is a flowchart for explaining Mode A operation to which embodiments of the present invention are applied.

[0139] Referring to FIG. 9, a terminal may detect at least one event (S910). In this case, the terminal may detect at least one event among the previously described event(s) (e.g., Event-1 to Event-9). If at least one event is detected, the terminal requests resources for beam reporting through a first UL channel (i.e., first PUCCH) (S920), and a base station that receives the first UL channel may indicate resources of a second UL channel to be used by the terminal to transmit the beam report through DCI (S930). Thereafter, the terminal may transmit the second UL channel including the beam report by utilizing the corresponding resources (S940).

[0140] Figure 10 is a flowchart for explaining Mode B operation to which embodiments of the present invention are applied.

[0141] Referring to FIG. 10, a terminal may detect at least one event (S1010). In this case, the terminal may detect at least one event among the previously described event(s) (e.g., Event-1 to Event-9). If at least one event is detected, the terminal may notify the base station that it will transmit second UL channel(s) using preset resources via the first UL channel (i.e., the first PUCCH) (S1020). Thereafter, the terminal may transmit the second UL channel(s) including a beam report to the base station using the preset resources (S1040).

[0142] In this case, the terminal may transmit the second UL channel(s) after receiving an acknowledgement message (e.g., an ACK (acknowledgement) message or a notification message consisting of a 1-bit indicator) (i.e., S1330 of FIG. 13) indicating that the first PUCCH has been received from the base station. Alternatively, the terminal may transmit the second UL channel(s) in a slot or symbol after a predetermined offset from a time point associated with transmission of the first PUCCH (e.g., a slot or symbol in which the first PUCCH (e.g., the last symbol constituting the first PUCCH) is transmitted) without receiving an acknowledgement message for the first PUCCH from the base station. For example, if it is not confirmed that the first PUCCH has not been normally received by the base station until the predetermined offset has elapsed from the time point associated with transmission of the first PUCCH, the terminal may transmit the second UL channel(s) in a slot or symbol after a predetermined offset from the time point associated with transmission of the first PUCCH. In this case, the offset may be set from the base station to the terminal in symbol, subslot, slot, subframe, or absolute time units, or may be predefined in the technical specifications. Meanwhile, since there may be cases where the terminal does not receive the acknowledgement message even though the base station has transmitted the acknowledgement message, the base station may transmit the acknowledgement message more than once.

[0143]

[0144] Meanwhile, as described above, since both modes (Mode A, Mode B) support cross-CC beam reporting, definition of specific procedures for cross-CC beam reporting operation is required.

[0145] First, there may be a case where the first UL channel (i.e., the first PUCCH) and the second UL channel are transmitted on the same component carrier (CC), and the second UL channel includes reports on the beam(s) of the CC. That is, no cross-CC beam reporting (or cross-carrier scheduling) occurs. In this case, there may be no need to transmit CC-related information from the terminal to the network (or from the network to the terminal).

[0146] On the other hand, if the CC through which the first UL channel is transmitted and the CC through which the second UL channel is transmitted are different, the terminal can operate as follows.

[0147]

[0148] Case 1: When a terminal transmits the first PUCCH on (a specific) CC (e.g., CC #1) and transmits the second UL channel for CC #1 on another CC (e.g., CC #2).

[0149] FIG. 11 is a flowchart for explaining a cross-CC beam reporting operation according to one embodiment of the present invention.

[0150] Referring to FIG. 11, the first UL channel (S1110) and the second UL channel (S1130) are transmitted through different CCs, and the CC of the current beam according to the detected event and the CC of the new beam according to the detected event may be the same. That is, information about a new beam existing in the same CC as the CC of the current beam (e.g., CC #1) (e.g., beam quality information (e.g., L1-RSRP, etc.)) may be transmitted through another CC (e.g., CC #2). This situation may occur when the quality of the current beam is degraded and a specific event (e.g., Event-2) condition is satisfied. That is, when it is difficult to transmit the second UL channel in CC #1, the second UL channel (and / or the DCI of step 2) may be transmitted in CC #2. Meanwhile, in FIG. 11, the DCI (S1120) transmitted by the base station receiving the first UL channel to schedule support of the second UL channel is illustrated as being transmitted through CC #1, but the DCI may also be transmitted through CC #2.

[0151] At this time, CC #1 and CC #2 may be contiguous CCs within the same band (intra-band).

[0152] At this time, CC #1 and CC #2 may be non-contiguous CCs within the same band (intra-band).

[0153] At this time, CC #1 and CC #2 may be CCs of different bands (inter-band).

[0154] At this time, CC #1 and CC #2 may belong to different FRs (frequency ranges). For example, CC #1 may belong to FR2, and CC #2 may belong to FR1.

[0155] To this end, if the first UL channel in the above process includes multi-bit information, the multi-bit information may be transmitted including various information (including a resource request of the second UL channel for transmitting a beam report). That is, when various event(s) described above and / or event(s) to be additionally defined later are detected, the terminal may transmit at least one of the following information to the base station via the first UL channel. For example, the first UL channel may include information regarding whether a cross-CC operation is performed (information requesting a cross-CC operation or information regarding whether a cross-CC operation is supported). Additionally or alternatively, the first UL channel may include at least one of information about a CC (e.g., an ID of a CC (cell) on which the second UL channel is to be transmitted), information about a reference signal (RS) ID, information about an RS (e.g., an SSB or CSI-RS) for a new beam (or current beam), information about band(s) (intra-band or inter-band) of CCs, or information about a maximum number of CCs. Meanwhile, the information may be transmitted from the terminal to the base station through various signaling methods other than the first UL channel. For example, the information may be transmitted from the terminal to the base station through an RRC signaling message.

[0156] The above information or some of the above information may be transmitted from the base station to the terminal via DCI (based on information of the first PUCCH) in the case of Mode A. Alternatively, some of the above information may be transmitted from the base station to the terminal via DCI and some of the above information may be transmitted from the base station to the terminal via MAC-CE signaling and / or RRC signaling.

[0157] Alternatively, the above information or some of the above information may be transmitted via MAC-CE signaling and / or RRC signaling in both Mode A and Mode B.

[0158]

[0159] Case 2: When the terminal transmits the first PUCCH on (a specific) CC (e.g., CC #1) and transmits the second UL channel for CC #2 on another CC (e.g., CC #2).

[0160] FIG. 12 is a flowchart for explaining a cross-CC beam reporting operation according to another embodiment of the present invention.

[0161] Referring to FIG. 12, the first UL channel (S1210) and the second UL channel (S1230) are transmitted through different CCs, and the CC of the current beam according to the detected event and the CC of the new beam according to the detected event may be different. That is, information about the current beam existing in CC #1 and the new beam existing in CC #2 (e.g., beam quality information (e.g., L1-RSRP, etc.)) may be transmitted through CC #2. This situation may occur in a newly defined event that includes a CC condition in addition to the events described above. That is, when it is difficult to transmit the second UL channel in CC #1, the second UL channel (and / or the DCI of step 2) may be transmitted in CC #2. Meanwhile, in FIG. 12, the DCI (S1220) transmitted by the base station receiving the first UL channel to schedule support of the second UL channel is illustrated as being transmitted through CC #1, but the DCI may also be transmitted through CC #2.

[0162] At this time, CC #1 and CC #2 may be contiguous CCs within the same band (intra-band).

[0163] At this time, CC #1 and CC #2 may be non-contiguous CCs within the same band (intra-band).

[0164] At this time, CC #1 and CC #2 may be CCs of different bands (inter-band).

[0165] At this time, CC #1 and CC #2 may belong to different FRs (frequency ranges). For example, CC #1 may belong to FR2, and CC #2 may belong to FR1.

[0166] To this end, if the first UL channel in the above process includes multi-bit information, the multi-bit information may be transmitted including various information (including a resource request of the second UL channel for transmitting a beam report). That is, when various event(s) described above and / or event(s) to be additionally defined later are detected, the terminal may transmit at least one of the following information to the base station via the first UL channel. For example, the first UL channel may include information regarding whether a cross-CC operation is performed (information requesting a cross-CC operation or information regarding whether a cross-CC operation is supported). Additionally or alternatively, the first UL channel may include at least one of information about a CC (e.g., an ID of a CC (cell) on which the second UL channel is to be transmitted), information about a reference signal (RS) ID, information about an RS (e.g., an SSB or CSI-RS) for a new beam (or current beam), information about band(s) (intra-band or inter-band) of CCs, or information about a maximum number of CCs. Meanwhile, the information may be transmitted from the terminal to the base station through various signaling methods other than the first UL channel. For example, the information may be transmitted from the terminal to the base station through an RRC signaling message.

[0167] The above information or some of the above information may be transmitted from the base station to the terminal via DCI (based on information of the first PUCCH) in the case of Mode A. Alternatively, some of the above information may be transmitted from the base station to the terminal via DCI and some of the above information may be transmitted from the base station to the terminal via MAC-CE signaling and / or RRC signaling.

[0168] Alternatively, the above information or some of the above information may be transmitted via MAC-CE signaling and / or RRC signaling in both Mode A and Mode B.

[0169]

[0170] Case 3: When the terminal transmits the first PUCCH on (a specific) CC (e.g., CC #1) and transmits the second UL channel for another CC (e.g., CC #2) on CC #1.

[0171] FIG. 13 is a flowchart illustrating a cross-CC beam reporting operation according to another embodiment of the present invention.

[0172] Referring to FIG. 13, the first UL channel and the second UL channel are transmitted through the same CC, and the CC of the current beam according to the detected event and the CC of the new beam according to the detected event may be different. That is, information about the quality (e.g., L1-RSRP, etc.) of the new beam in a CC different from the CC of the current beam (e.g., CC #1) may be transmitted in CC #1. This situation may occur in a newly defined event that includes a CC condition in addition to the events described above.

[0173] At this time, CC #1 and CC #2 may be contiguous CCs within the same band (intra-band).

[0174] At this time, CC #1 and CC #2 may be non-contiguous CCs within the same band (intra-band).

[0175] At this time, CC #1 and CC #2 may be CCs of different bands (inter-band).

[0176] At this time, CC #1 and CC #2 may belong to different FRs (frequency ranges). For example, CC #1 may belong to FR2, and CC #2 may belong to FR1.

[0177] To this end, if the first UL channel in the above process includes multi-bit information, the multi-bit information may be transmitted including various information (including a resource request of the second UL channel for transmitting a beam report). That is, when various event(s) described above and / or event(s) to be additionally defined later are detected, the terminal may transmit at least one of the following information to the base station via the first UL channel. For example, the first UL channel may include information regarding whether a cross-CC operation is performed (information requesting a cross-CC operation or information regarding whether a cross-CC operation is supported). Additionally or alternatively, the first UL channel may include at least one of information about a CC (e.g., an ID of a CC (cell) on which the second UL channel is to be transmitted), information about a reference signal (RS) ID, information about an RS (e.g., an SSB or CSI-RS) for a new beam (or current beam), information about band(s) (intra-band or inter-band) of CCs, or information about a maximum number of CCs. Meanwhile, the information may be transmitted from the terminal to the base station through various signaling methods other than the first UL channel. For example, the information may be transmitted from the terminal to the base station through an RRC signaling message.

[0178] The above information or some of the above information may be transmitted from the base station to the terminal via DCI (based on information of the first PUCCH) in the case of Mode A. Alternatively, some of the above information may be transmitted from the base station to the terminal via DCI and some of the above information may be transmitted from the base station to the terminal via MAC-CE signaling and / or RRC signaling.

[0179] Alternatively, the above information or some of the above information may be transmitted via MAC-CE signaling and / or RRC signaling in both Mode A and Mode B.

[0180]

[0181] Although the above embodiments assume two CCs, the above embodiments can be applied equally or similarly to two or more CCs.

[0182] Information about CCs described in the present disclosure (e.g., ID of a CC (cell) on which the second UL channel is to be transmitted), information about a reference signal (RS) ID, information about RS (e.g., SSB or CSI-RS, etc.) for a new beam (or current beam), information about band(s) (intra-band or inter-band) of CCs, or information about the maximum number of CCs, etc., may be transmitted by default regardless of whether cross-CC operation is supported, or may be optionally transmitted depending on a specific condition (e.g., whether cross-CC operation is supported).

[0183] With respect to the measurement of the RS defining the current beam of a specific event (e.g., Event-2) described in the present disclosure, the following schemes may be supported in certain cases. For example, the RS for the current beam may be a QCL RS for an indicated TCI state. In this case, the RS for the current beam may be a periodic CSI-RS configured for (UE-driven) beam management (Scheme 1). As another example, the RS for the current beam may be an SSB QCLed to the QCL RS for the indicated TCI state (Scheme 2). The activation (or operation) of one of the two schemes may be selected by the base station (NW). The selection of one of the two schemes may be performed either explicitly by signaling an RRC parameter or implicitly. For example, if the RS of the new beam is a CSI-RS, Scheme 1 may be activated, otherwise Scheme 2 may be activated. Alternatively, method 1 (or method 2) may operate as a baseline, and whether method 2 (or method 1) is additionally applied may be determined by RRC parameters. In addition, when method 1 or method 2 is activated, it may be ensured that the RS of the current beam and the RS of the new beam have the same RS type.

[0184]

[0185] The information(s) described in this disclosure may be applied not only to Mode A and Mode B described in this disclosure, but also to Mode(s) to be defined later. The information(s) described in this disclosure may be applied differently depending on the Mode.

[0186] The first PUCCH described above may have an SR type or a new UCI type, or may have an SR type, a BSR type, or another format.

[0187] The information(s) described above may be transmitted via MAC-CE signaling, UCI, and / or RRC signaling (and / or another channel).

[0188] In the present disclosure, performing a terminal-driven / event-based beam management operation can be extended to mean that the terminal transmits signaling to the base station instructing it to perform a terminal-driven / event-based beam management operation.

[0189] In the present disclosure, the term "terminal-driven / event-based beam management operation being stopped" can be extended to mean that the terminal transmits signaling to the base station indicating that it does not perform the terminal-driven / event-based beam management operation, or that it performs the existing base station-driven beam management operation.

[0190] The methods proposed in this disclosure can be applied to additionally defined events in addition to the currently defined events. The methods proposed in this disclosure can be applied to intra-cell beam management and inter-cell beam management. The methods proposed in this disclosure can also be similarly applied to multi-TRP (mTRP) operations.

[0191]

[0192] The operations 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 any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0193] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.

[0194] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described as a corresponding block or item or a 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 or more of the most significant method steps may be performed by such a device.

[0195] 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 the present disclosure. The field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described in the present disclosure. In general, the methods are preferably performed by some hardware device.

[0196] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.

Claims

1. In the terminal method, A step of transmitting information related to cross-component carrier (CC) scheduling to a base station; A step of detecting at least one event; When at least one event is detected, transmitting a first uplink (UL) channel from a first CC to the base station; A step of receiving downlink control information (DCI) for allocating UL resources of a second CC for transmitting a beam report according to the at least one event from the base station based on the information related to the first UL channel and the cross-CC scheduling, from the first CC or the second CC; and A step of transmitting a second UL channel including the beam report in the second CC using the UL resource, method.

2. In claim 1, The first CC and the second CC are contiguous CCs within the same band (intra-band), non-contiguous CCs within the same band, or CCs of different bands (inter-band). method.

3. In claim 1, The information related to the cross-CC scheduling includes information that the terminal requests cross-CC scheduling for the beam report to the base station or information on whether the terminal supports cross-CC scheduling. method.

4. In claim 1, The information related to the cross-CC scheduling includes at least one of information about a CC on which the second UL channel is to be transmitted, information about a reference signal (RS) corresponding to a new beam according to the at least one event, information about an RS corresponding to a current beam according to the at least one event, information about band(s) of CCs, or information about a maximum number of CCs. method.

5. In claim 1, The first CC and the second CC are different from each other, and the current beam according to the at least one event and the new beam according to the at least one event belong to the first CC. method.

6. In claim 1, The first CC and the second CC are different from each other, and the current beam according to the at least one event belongs to the first CC, and the new beam according to the at least one event belongs to the second CC. method.

7. In claim 1, The first CC and the second CC are identical, and the current beam according to the at least one event belongs to the first CC, and the new beam according to the at least one event belongs to the third CC. method.

8. In claim 1, The quality of the current beam according to at least one event is measured based on a quasi-co-location (QCL) reference signal for the indicated transmission configuration indication (TCI) state, or based on a QCL reference signal QCL (quasi-co-located) synchronization signal block (SSB) for the indicated TCI state. method.

9. In claim 1, The quality of the current beam and the quality of the new beam according to at least one of the above events are measured by reference signals of the same type. method.

10. In the method of the base station, A step of receiving information related to cross-component carrier (CC) scheduling from a terminal; A step of receiving a first uplink (UL) channel in a first CC from a terminal that detects at least one event; A step of transmitting downlink control information (DCI) for allocating UL resources of a second CC for receiving a beam report according to the at least one event, based on the information related to the first UL channel and the cross-CC scheduling, from the first CC or the second CC to the terminal; and A step of receiving a second UL channel including the beam report from the second CC using the UL resource, method.

11. In claim 10, The first CC and the second CC are contiguous CCs within the same band (intra-band), non-contiguous CCs within the same band, or CCs of different bands (inter-band). method.

12. In claim 10, The information related to the cross-CC scheduling includes information that the terminal requests cross-CC scheduling for the beam report to the base station or information on whether the terminal supports cross-CC scheduling. method.

13. In claim 10, The information related to the cross-CC scheduling includes at least one of information about a CC on which the second UL channel is to be transmitted, information about a reference signal (RS) corresponding to a new beam according to the at least one event, information about an RS corresponding to a current beam according to the at least one event, information about band(s) of CCs, or information about a maximum number of CCs. method.

14. In claim 10, The first CC and the second CC are different from each other, and the current beam according to the at least one event and the new beam according to the at least one event belong to the first CC. method.

15. In claim 10, The first CC and the second CC are different from each other, and the current beam according to the at least one event belongs to the first CC, and the new beam according to the at least one event belongs to the second CC. method.

16. In claim 9, The first CC and the second CC are identical, and the current beam according to the at least one event belongs to the first CC, and the new beam according to the at least one event belongs to the third CC. method.

17. In a terminal including at least one processor, At least one processor of the terminal: A step of transmitting information related to cross-component carrier (CC) scheduling to a base station; A step of detecting at least one event; When at least one event is detected, transmitting a first uplink (UL) channel from a first CC to the base station; A step of receiving downlink control information (DCI) for allocating UL resources of a second CC for transmitting a beam report according to the at least one event from the base station based on the information related to the first UL channel and the cross-CC scheduling, from the first CC or the second CC; and Performing a step of transmitting a second UL channel including the beam report on the second CC using the above UL resource, Terminal.

18. In claim 17, The information related to the cross-CC scheduling includes information that the terminal requests cross-CC scheduling for the beam report to the base station or information on whether the terminal supports cross-CC scheduling. Terminal.

19. In claim 18, The information related to the cross-CC scheduling includes at least one of information about a CC on which the second UL channel is to be transmitted, information about a reference signal (RS) corresponding to a new beam according to the at least one event, information about an RS corresponding to a current beam according to the at least one event, information about band(s) of CCs, or information about a maximum number of CCs. Terminal.

20. In claim 17, The first CC and the second CC are different from each other, and the current beam according to the at least one event and the new beam according to the at least one event belong to the first CC, or the current beam according to the at least one event belongs to the first CC and the new beam according to the at least one event belongs to the second CC. Terminal.

Images