Method and apparatus for UE-initiated beam management
The proposed UE-initiated/event-driven beam reporting method addresses the lack of cross-component carrier operation definitions in 3GPP standards by adjusting resource periods and CSI reports, ensuring reliable and efficient beam management in 5G and 6G networks.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- HYUNDAI MOTOR CO LTD
- Filing Date
- 2025-09-18
- Publication Date
- 2026-05-15
AI Technical Summary
Existing 3GPP standards for user equipment-initiated/event-driven beam management in 5G and 6G communication networks lack specific definitions for beam reporting behaviors considering cross-component carrier operation, leading to potential reporting failures and performance degradation due to mismatched resource periods and subcarrier spacings.
A method for UE-initiated/event-driven beam reporting that involves transmitting UL channels from different component carriers with varying subcarrier spacings, allowing for flexible and reliable reporting by adjusting resource periods based on the smallest or largest SCS, and configuring CSI reports accordingly.
Ensures reliable and efficient beam management and CSI report collection across different component carriers, preventing reporting failures and enhancing scalability for future network adaptations.
Smart Images

Figure KR2025014528_15052026_PF_FP_ABST
Abstract
Description
Terminal-led beam management method and device
[0001] The present invention relates to a beam management method in a mobile communication system, and more specifically, to a UE-initiated / event-driven beam reporting method considering cross-component carrier operation and an apparatus for the same.
[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, etc.).
[0004] Meanwhile, 3GPP (3 rd Release-19 of the generation partnership project is proceeding with standardization for user equipment-initiated (UEI) and event-driven (ED) beam management to address the issues of conventional network-driven beam management. Unlike conventional network-driven beam management, user equipment-initiated / event-driven beam management is a method in which the terminal, which can recognize the current beam status and beam change trends relatively faster than the base station, proactively performs beam management. However, in user equipment-initiated / event-driven beam management, specific beam reporting behaviors considering cross-component carrier scheduling situations have not yet been defined.
[0005] The purpose of the present disclosure to solve the above-mentioned problems is to provide a UE-initiated / event-driven beam reporting method considering cross-component carrier operation and an apparatus for the same.
[0006] A method of a terminal according to embodiments of the present disclosure for achieving the above objective comprises: detecting at least one event; transmitting a first uplink (UL) channel from a first component carrier (CC) to a base station when the at least one event is detected; and transmitting a second UL channel from a second CC to the base station using a preset UL resource, wherein the first CC and the second CC are different CCs, and the first CC and the second CC may have different subcarrier spacings (SCS).
[0007] The first CC and the second CC may be contiguous CCs within the same intra-band, non-contiguous CCs within the same band, or CCs of different inter-bands.
[0008] The method further includes the step of receiving a CSI (channel state information) report setting corresponding to the first UL channel from the base station, and the second CC can be set by the CSI report setting.
[0009] The resources of the first UL channel and the resources of the second channel can be set to have the same period.
[0010] The resources of the first UL channel and the resources of the second channel can be configured to have different cycles.
[0011] The resource period of the second UL channel can be set to be shorter or longer than the resource period of the first UL channel based on the difference between the different SCSs.
[0012] The resource period of the second UL channel can be set based on the smallest SCS or the largest SCS of the CCs that the second UL channel can set.
[0013] A method of a base station according to embodiments of the present disclosure for achieving the above objective comprises: receiving a first uplink (UL) channel in a first (component carrier, CC) from a terminal that has detected at least one event; and receiving a second UL channel from the terminal in a second CC, which includes a beam report according to the at least one event, using a preset UL resource, wherein the first CC and the second CC are different CCs, and the first CC and the second CC may have different subcarrier spacings (SCS).
[0014] The first CC and the second CC may be contiguous CCs within the same intra-band, non-contiguous CCs within the same band, or CCs of different inter-bands.
[0015] The above method further includes the step of transmitting a CSI (channel state information) reporting setting corresponding to the first UL channel to the terminal, and the second CC can be set by the CSI reporting setting.
[0016] The resources of the first UL channel and the resources of the second channel can be set to have the same period.
[0017] The resources of the first UL channel and the resources of the second channel can be configured to have different cycles.
[0018] The resource period of the second UL channel can be set to be shorter or longer than the resource period of the first UL channel based on the difference between the different SCSs.
[0019] The resource period of the second UL channel can be set based on the smallest SCS or the largest SCS of the CCs that the second UL channel can set.
[0020] A terminal according to embodiments of the present disclosure for achieving the above objective comprises at least one processor, wherein the at least one processor enables the terminal to perform: a step of detecting at least one event; a step of transmitting a first uplink (UL) channel from a first (component carrier, CC) to a base station when the at least one event is detected; and a step of transmitting a second UL channel from a second CC to the base station using a preset UL resource, wherein the first CC and the second CC are different CCs, and the first CC and the second CC may have different subcarrier spacings.
[0021] The above at least one processor further enables the terminal to perform the step of receiving a CSI (channel state information) report setting corresponding to the first UL channel from the base station, and the second CC can be set by the CSI report setting.
[0022] The resources of the first UL channel and the resources of the second channel can be set to have the same period.
[0023] The resources of the first UL channel and the resources of the second channel can be configured to have different cycles.
[0024] The resource period of the second UL channel can be set to be shorter or longer than the resource period of the first UL channel based on the difference between the different SCSs.
[0025] The resource period of the second UL channel can be set based on the smallest SCS or the largest SCS of the CCs that the second UL channel can set.
[0026] According to embodiments of the present disclosure, beam reporting can be transmitted reliably and flexibly even when the first UL channel and the second UL channel have different SCSs in a cross-CC and / or cross-PUCCH group environment. That is, the resource periods of the first UL channel and the second UL channel can be set identically or set to different periods, but adjusted according to the SCS difference or specific criteria (minimum / maximum value of SCS), thereby supporting various channel environments and CC / PUCCH group / CG configurations. Accordingly, the terminal can prevent reporting failures or performance degradation due to period mismatches, and the base station can perform efficient beam management and CSI report collection. Consequently, the present disclosure improves the reliability and efficiency of cross-CC beam reporting in 3GPP NR systems and provides scalability even when new modes or triggering conditions are added in the future.
[0027] FIG. 1 is a conceptual diagram illustrating a first embodiment of a communication system.
[0028] FIG. 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.
[0029] FIG. 3 is a block diagram illustrating a first embodiment of communication nodes performing communication.
[0030] FIG. 4a is a block diagram illustrating a first embodiment of a transmission path.
[0031] FIG. 4b is a block diagram illustrating a first embodiment of a receiving path.
[0032] FIG. 5 is a conceptual diagram illustrating a first embodiment of a system frame in a communication system.
[0033] FIG. 6 is a conceptual diagram illustrating a first embodiment of a subframe in a communication system.
[0034] FIG. 7 is a conceptual diagram illustrating a first embodiment of a slot in a communication system.
[0035] FIG. 8 is a conceptual diagram illustrating a first embodiment of a time-frequency resource in a communication system.
[0036] FIG. 9 is a flowchart for explaining Mode A operation to which embodiments of the present invention are applied.
[0037] FIG. 10 is a flowchart illustrating Mode B operation to which embodiments of the present invention are applied.
[0038] FIGS. 11a and FIGS. 11b are conceptual diagrams illustrating different environments for the first channel and second channel SCSs for beam reporting to which embodiments of the present invention are applied.
[0039] FIG. 12 is a flowchart illustrating a beam reporting method according to one embodiment of the present invention.
[0040] 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.
[0041] 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.
[0042] 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".
[0043] 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".
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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.
[0048] 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.
[0049] 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.
[0050] 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)).
[0051] 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."
[0052] 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."
[0053] FIG. 1 is a conceptual diagram illustrating a first embodiment of a communication system.
[0054] 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., an S-GW (serving-gateway), a P-GW (PDN (packet data network)-gateway), and an 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 AMF (access and mobility management function), a UPF (user plane function), an SMF (session management function), etc.
[0055] 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.
[0056] FIG. 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.
[0057] Referring to FIG. 2, the communication node (200) may include at least one processor (210), a memory (220), and a transceiver (230) that is connected to a network to perform communication. Additionally, 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) to communicate with one another.
[0058] The processor (210) can execute a program command stored in at least one of the memory (220) and the storage device (260). The processor (210) 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. Each of the memory (220) and the storage device (260) may be composed of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be composed of at least one of read-only memory (ROM) and random access memory (RAM).
[0059] 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 located 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 located 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 located within the cell coverage of the third base station (110-3). The first terminal (130-1) may be located within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be located within the cell coverage of the fifth base station (120-2).
[0060] Here, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as NB (NodeB), eNB (evolved NodeB), gNB, ABS (advanced base station), HR-BS (high reliability-base station), BTS (base transceiver station), radio base station, radio transceiver, access point, access node, RAS (radio access station), MMR-BS (mobile multihop relay-base station), RS (relay station), ARS (advanced relay station), HR-RS (high reliability-relay station), HNB (home NodeB), HeNB (home eNodeB), RSU (road side unit), RRH (radio remote head), TP (transmission point), TRP (transmission and reception point), etc.
[0061] Each of the multiple terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as UE (user equipment), TE (terminal equipment), AMS (advanced mobile station), HR-MS (high reliability-mobile station), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, OBU (on board unit), etc.
[0062] Meanwhile, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in different frequency bands or in the same frequency band. Each of the multiple 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 an ideal backhaul link or a non-ideal backhaul link. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to a core network via an ideal backhaul link or a non-ideal backhaul link. Each of the multiple 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.
[0063] In addition, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can support MIMO transmission (e.g., SU (single user)-MIMO, MU (multi user)-MIMO, massive MIMO, etc.), CoMP (coordinated multipoint) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, sidelink communication (e.g., D2D (device to device communication), ProSe (proximity services)), IoT (Internet of Things) 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 method, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) based on the SU-MIMO method. Alternatively, the second base station (110-2) can transmit a signal 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 a signal from the second base station (110-2) by the MU-MIMO method.
[0064] 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 method, 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) by the CoMP method. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive signals based on the CA method with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage area. 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 by controlling each of the second base station (110-2) and the third base station (110-3).
[0065] Meanwhile, communication nodes performing communication in a communication network may be configured as follows. The communication node shown in FIG. 3 may be a specific embodiment of the communication node shown in FIG. 2.
[0066] FIG. 3 is a block diagram illustrating a first embodiment of communication nodes performing communication.
[0067] 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).
[0068] 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.
[0069] 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).
[0070] 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).
[0071] 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 the 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 the 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.
[0072] 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 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 antennas (364a to 364t).
[0073] 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).
[0074] 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.
[0075] 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.
[0076] 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 (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 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.
[0077] 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) (LDPC) 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.
[0078] 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.
[0079] 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.
[0080] 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 N FFT 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 perform a decoding operation on the result of the demodulation operation to restore the data.
[0081] 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.
[0082] FIG. 5 is a conceptual diagram illustrating a first embodiment of a system frame in a communication system.
[0083] 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.
[0084] 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".
[0085] FIG. 6 is a conceptual diagram illustrating a first embodiment of a subframe in a communication system.
[0086] Referring to FIG. 6, one subframe may include n slots, where n is a natural number. Thus, one subframe may consist of one or more slots.
[0087] FIG. 7 is a conceptual diagram illustrating a first embodiment of a slot in a communication system.
[0088] 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.
[0089] 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 a first embodiment 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.
[0090] Subcarrier Spacing 15kHz 30kHz 60kHz 120kHz 240kHz 480kHz OFDM Symbol Length (μs) 66.733.316.78.34.22.1 CP Length (μs) 4.762.381.190.600.300.151 ms Number of OFDM Symbols within 142856112224448
[0091]
[0092] When the subcarrier spacing is 15 kHz (e.g., μ=0), the slot length may be 1 ms. In this case, one system frame may contain 10 slots. When the subcarrier spacing is 30 kHz (e.g., μ=1), the slot length may be 0.5 ms. In this case, one system frame may contain 20 slots.
[0093] When the subcarrier spacing is 60 kHz (e.g., μ=2), the slot length may be 0.25 ms. In this case, one system frame may contain 40 slots. When the subcarrier spacing is 120 kHz (e.g., μ=3), the slot length may be 0.125 ms. In this case, one system frame may contain 80 slots. When the subcarrier spacing is 240 kHz (e.g., μ=4), the slot length may be 0.0625 ms. In this case, one system frame may contain 160 slots.
[0094] The symbol can be set as a downlink (DL) symbol, a flexible (FL) symbol, or an uplink (UL) symbol. A slot consisting only of a DL symbol may be referred to as a "DL slot," a slot consisting only of an FL symbol may be referred to as an "FL slot," and a slot consisting only of a UL symbol may be referred to as an "UL slot."
[0095] The slot format can be semi-fixed by upper-layer signaling (e.g., RRC signaling). Information indicating the semi-fixed slot format may be included in system information, and the semi-fixed slot format can be set cell-specifically. Additionally, the semi-fixed slot format can be additionally set per terminal through terminal-specific upper-layer signaling (e.g., RRC signaling). The flexible symbols of the cell-specific slot format can be overridden as downlink symbols or uplink symbols by the terminal-specific upper-layer signaling. Furthermore, the slot format can be dynamically indicated by physical layer signaling (e.g., the SFI (slot format indicator) included in the DCI). The semi-fixed slot format can be overridden by the dynamically indicated slot format. For example, the semi-fixed flexible symbols can be overridden as downlink symbols or uplink symbols by the SFI.
[0096] The reference signal may be a CSI-RS (channel state information-reference signal), SRS (sounding reference signal), DM-RS (demodulation-reference signal), PT-RS (phase tracking-reference signal), etc. The channel may be a PBCH (physical broadcast channel), PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), PUCCH (physical uplink control channel), PUSCH (physical uplink shared channel), PSCCH (physical sidelink control channel), PSSCH (physical sidelink shared channel), etc. In the present disclosure, the control channel may mean PDCCH, PUCCH, or PSCCH, and the data channel may mean PDSCH, PUSCH, or PSSCH.
[0097] FIG. 8 is a conceptual diagram illustrating a first embodiment of a time-frequency resource in a communication system.
[0098] 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.
[0099] 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.
[0100] 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.
[0101] 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.
[0102] 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 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 symbol units. In the frequency domain, the size of the PDCCH occasion may be indicated in RB units (e.g., PRB (physical resource block) units or CRB (common resource block) units).
[0103] 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.
[0104] 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." One or more BWPs may be configured for a single terminal. 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).
[0105]
[0106] In accordance with the Work Item Description (WID) for 3GPP Rel-19 NR MIMO discussions, discussions are underway regarding improvements to intra-cell and inter-cell beam management. These improvements primarily target the FR2 band and single transmission / reception point (sTRP) scenarios, aiming to reduce overhead or latency while utilizing existing legacy CSI measurement and reporting configuration procedures.
[0107] To this end, UE-initiated (UEI) and event-driven (ED) beam management procedures are being discussed. The beam management methods defined up to Rel-18 consisted of network-based operations. That is, in network-driven 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, since the base station receives a measurement report from the terminal and issues instructions based on that report, the base station cannot identify the optimal beam until it receives the measurement report transmitted by the terminal.
[0108] If beam management operations are initiated at the terminal side, which can detect changes in the beam first, latency (e.g., the time required for a base station to instruct a terminal to report a measurement and to receive a measurement report from the terminal based on that instruction) and signal overhead (e.g., the overhead of the signal in which the network instructs the terminal to report a measurement) can be reduced compared to network-based beam management operations.
[0109]
[0110] Meanwhile, at 3GPP RAN 1 meetings (RAN #116 and RAN #116-bis), outlined beam reporting transmission procedures for UEI / ED beam reporting were approved.
[0111] First, the beam report transmission procedure is broadly divided into Mode A and Mode B, and an overview of the procedure for each mode is as follows.
[0112] First, Mode A is a method in which the base station dynamically schedules UCI (uplink control information) for beam reporting, and can be performed in the following three steps.
[0113] Step 1: The terminal may transmit a first UL channel requesting resources for a second UL channel to transmit a beam report. The first UL channel consists of a PUCCH (i.e., first PUCCH) containing one bit information or multi-bit information, and the PUCCH may follow the type of an existing SR (scheduling req terminal st) or a new UCI type.
[0114] Step 2: The terminal can detect a DCI format indicating a resource of the second UL channel. In this case, a new DCI format is not introduced.
[0115] Step 3: The terminal can transmit a beam report on the second UL channel. In this case, PUCCH, PUSCH, or both can be used as the second UL channel.
[0116] Mode A is a basic function of the terminal, and all terminals that support UEI / ED beam reporting must support this function.
[0117] Meanwhile, Mode B is a method of transmitting UCI from a pre-configured resource for a second UL channel, and can be performed in the following two steps.
[0118] Step 1: The terminal may transmit the first UL channel to notify that a beam report will be transmitted on the second UL channel. The first UL channel consists of a PUCCH (i.e., first PUCCH) containing one bit information or multi-bit information, and the PUCCH may follow the type of the existing SR (scheduling request terminal st) or the new UCI type.
[0119] Step 2: The terminal can transmit a beam report on the second UL channel. As with Mode A, PUCCH, PUSCH, or both can be used as the second UL channel.
[0120] In Mode B, the notification in Step 1 and the beam report in Step 2 are transmitted as separate report instances, and it is not determined whether the terminal receives confirmation information in response to each step in Mode A and Mode B.
[0121] In addition, cross-CC (component carrier) beam reporting can be supported in both Mode A and Mode B in the above procedures.
[0122]
[0123] Meanwhile, the following events are being discussed as triggering the aforementioned UEI / ED beam reporting.
[0124] -Event-1: The quality of the current beam (e.g., L1-RSRP, etc.) falls below a specific threshold.
[0125] -Event-2: The quality of at least one new beam is improved by a threshold amount compared to the current beam.
[0126] -Event-3: New beam quality exceeds a specific threshold.
[0127] -Event-4: Current beam quality drops below threshold 1, and at least one new beam quality rises above threshold 2.
[0128] -Event-5: The absolute difference between the quality of the current beam and the quality of at least one new beam becomes smaller than a specific threshold.
[0129] -Event-6: The current beam is not included in the top K (>1) beams among the beams configured for measurement and reporting.
[0130] -Event-7: The quality of at least one new beam (L1-RSRP, etc.) is improved by a specific threshold compared to the RS derived from the active TCI state with the Mth best quality.
[0131] -Event-8: The quality of M (>1) new beams (L1-RSRP, etc.) has improved by a specific threshold compared to the current beam.
[0132] -Event-9: The quality of at least one new beam (L1-RSRP, etc.) is improved by a specific threshold compared to the configured reference RS (SSB or CSI-RS possible).
[0133]
[0134] As described above, for UEI / ED beam reporting operations, a process of first transmitting information from the terminal to the base station (Step 1) is required in all modes. In the case of Mode A, where resources for beam reporting are not pre-allocated, the terminal may request resources for beam reporting from the base station. In the case of Mode B, where resources for beam reporting are pre-allocated, the terminal may notify the base station that it intends to use the pre-allocated resources for beam reporting. In Step 1, the terminal may transmit the relevant information to the base station via PUCCH, and the information may consist of 1-bit information or multi-bit information. If the information consists of 1 bit, it may simply be information requesting resources from the base station or information notifying the fact that pre-allocated resources are being used. On the other hand, if the information consists of multi-bit information, it may be used for various purposes in addition to information requesting resources or notifying the fact that pre-allocated resources are being used.
[0135]
[0136] FIG. 9 is a flowchart for explaining Mode A operation to which embodiments of the present invention are applied.
[0137] Referring to FIG. 9, the terminal can detect at least one event (S910). In this case, the terminal can detect at least one event among the previously described event(s) (e.g., Event-1 to Event-9). When at least one event is detected, the terminal requests resources for beam reporting through the first UL channel (i.e., first PUCCH) (S920), and the base station that received the first UL channel may indicate resources for the second UL channel to be used by the terminal to transmit the beam report through the DCI (S930). Subsequently, the terminal can transmit the second UL channel including the beam report using the said resources (S940).
[0138] FIG. 10 is a flowchart illustrating Mode B operation to which embodiments of the present invention are applied.
[0139] Referring to FIG. 10, the terminal can detect at least one event (S1010). In this case, the terminal can detect at least one event among the previously described event(s) (e.g., Event-1 to Event-9). When at least one event is detected, the terminal can notify the base station that it is transmitting the second UL channel(s) using a pre-configured resource through the first UL channel (i.e., first PUCCH) (S1020). Subsequently, the terminal can transmit the second UL channel(s), including a beam report, to the base station using the pre-configured resource (S1040).
[0140] In this case, the terminal may transmit the second UL channel(s) after receiving an acknowledgment 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) at a slot or symbol after a predetermined offset from the time point associated with the transmission of the first PUCCH (e.g., the slot or symbol in which the first PUCCH (e.g., the last symbol constituting the first PUCCH) was transmitted) without receiving an acknowledgment message for the first PUCCH from the base station. For example, if it is not confirmed that the first PUCCH was not normally received by the base station until the predetermined offset has elapsed from the time point associated with the transmission of the first PUCCH, the terminal may transmit the second UL channel(s) at a slot or symbol after a predetermined offset from the time point associated with the transmission of the first PUCCH. In this case, the offset may be set from the base station to the terminal in units of symbols, subslots, slots, subframes, or absolute time, or may be predefined in the technical specifications. Meanwhile, since there may be cases where the terminal does not receive the acknowledgment message even though the base station has transmitted the acknowledgment message, the base station may transmit the acknowledgment message one or more times.
[0141]
[0142] Meanwhile, the following approvals were decided at the 3GPP RAN 1 meeting.
[0143] At the RAN1 #118 meeting, regarding the UEI / ED beam reporting transmission procedure, it was decided that the following options are provided for resource mapping / configuration between the first UL channel (i.e., first PUCCH) and the second UL channel in Mode-B based on specific CSI reporting settings.
[0144] - Option-1 (1-to-1): For a CSI reporting setup for UEI / ED beam reporting, only one first UL channel (i.e., first PUCCH) resource and only one pre-configured second UL channel resource can be associated.
[0145] Specifically, Option-1A, in which the periodicity of the resource of the first UL channel and the pre-set periodicity of the resource of the second UL channel are set to be the same, and Option 1-B, in which there is no restriction between the periodicity of the resource of the first UL channel and the pre-set periodicity of the resource of the second UL channel, may be supported.
[0146] -Option-2 (One-to-Many): A CSI reporting setup for UEI / ED beam reporting may be associated with a resource of one first UL channel (i.e., first PUCCH) and one or more preset resource(s) of a second UL channel.
[0147] In addition, regarding the beam report transmission procedure for UEI / ED beam reporting, for Event-2, at least in Mode-B, the beam report must be transmitted on the second UL channel within the CC where the corresponding CSI reporting setting is configured. This applies to both cross-CC and same-CC beam reports, and may apply when the second UL channel is PUSCH.
[0148] In addition, at the RAN1 #118-bis meeting, regarding the cross-CC beam reporting transmission procedure for UEI / ED beam reporting, it was determined that for Event-2, the first UL channel and the second UL channel can be transmitted from the same CC or different CCs in both Mode-A and Mode-B.
[0149] In addition, in the beam report transmission procedure for UEI / ED beam reporting, when the beam report is transmitted via a preset Type-1 CG PUSCH, at least Option-3 of the following options must be supported for the second UL channel of Mode-B.
[0150] - Option-1: The same Type-1 CG PUSCH can transmit UL-SCH, other UCIs, and beam reports.
[0151] - Option-2: Type-1 CG PUSCH is assigned exclusively for beam report transmission.
[0152] Specifically, the PUSCH cannot transmit UL-SCH, nor can it transmit other UCIs.
[0153] - Option-3: Type-1 CG PUSCH is used for beam report transmission.
[0154] Specifically, the PUSCH cannot transmit UL-SCH, but other UCIs can.
[0155]
[0156] Meanwhile, as described above, since both modes (Mode A and Mode B) support cross-CC beam reporting, it is necessary to define specific procedures for cross-CC beam reporting operations.
[0157] As previously described, in the case of Mode-B, the terminal transmits a first UL channel (e.g., first PUCCH) to the base station and subsequently transmits a second UL channel using preset resources. In this case, to transmit the first UL channel and the second UL channel, there may be cases where the relationship between the resources of the first UL channel and the preset resources of the second UL channel (e.g., subcarrier spacing (SCS) and / or periodicity) must be considered. Additionally, as previously described, regarding Event-2 in the beam report transmission procedure for UEI / ED beam reporting, at least in the case of Mode-B, the beam report may be transmitted through a second UL channel within the CC indicated by the associated CSI report setting. The CC may be the same CC as the CC to which the first UL channel was transmitted or a different CC. Additionally, the second UL channel may be a PUCCH or a PUSCH.
[0158] In the following description, the two previously mentioned Modes are used as examples, but a similar method may be used even if other Modes are added later (i.e., if UEI / ED beam reporting modes that can be defined other than Mode-A or Mode-B are added). Furthermore, in the following description, Event-2 is used as an example for the condition for transmitting a beam report, but a similar method may be used even if other events are additionally used later (i.e., if triggering conditions that can be defined other than Event-2).
[0159] As previously described, in the cross-CC beam report transmission procedure for UEI / ED beam reporting, the first UL channel and the second UL channel may be transmitted from the same or different CCs. Additionally, the first UL channel and the second UL channel may belong to the same PUCCH group or different PUCCH groups. Additionally, the first UL channel and the second UL channel may belong to the same CG (cell group) or different CGs. In this case, if the second UL channel is a PUSCH, the second UL channel may be a type-1 CG (configured grant) PUSCH.
[0160] That is, in the case of Mode-B, a second UL channel may be transmitted using a preset resource after the transmission of the first UL channel. In this case, the second UL channel may be transmitted at a CC indicated by the CSI reporting setting corresponding to the first UL channel. The CC to which the second UL channel is transmitted may be the same CC as the CC to which the first UL channel was transmitted, or a different CC. If the second UL channel is transmitted at the same CC as the first UL channel or a different CC, the second UL channel may be a PUSCH, and the second UL channel (second PUSCH) and the first PUCCH may belong to the same CG or different CGs.
[0161] That is, the first UL channel and the second UL channel can be transmitted in the following environments.
[0162] (a) Same CC, same PUCCH group, same CG
[0163] (b) Different CCs, same PUCCH group, same CG
[0164] (c) Different CCs, same PUCCH group, different CGs
[0165] (d) Different CCs, different PUCCH groups, same CG
[0166] (e) Different CCs, different PUCCH groups, different CGs
[0167]
[0168] At this time, since the second UL channel is transmitted at the CC indicated by the CSI reporting setting corresponding to the first UL channel, it can be transmitted at the same frequency unless there is a change in other settings. However, there may be cases where the frequency differs depending on the specific environment.
[0169] FIGS. 11a and FIGS. 11b are conceptual diagrams illustrating different environments for the first channel and second channel SCSs for beam reporting to which embodiments of the present invention are applied.
[0170] In the case of Cross-CC (e.g., (b) to (e)), since the first UL channel and the second UL channel can be transmitted at different CCs, the second UL channel can have different numerologies (i.e., different SCSs) from the first UL channel. Referring to FIG. 11a, a case is illustrated in which the first UL channel is transmitted at CC 2 and the second UL channel is transmitted at CC n-1 in an environment where n CCs are aggregated. In this case, CC 2 and CC n-1 can have different SCSs.
[0171] In the case of a Cross-PUCCH group (e.g., (d), (e)), the CC to which the first UL channel is transmitted and the CC to which the second UL channel is transmitted may belong to different PUCCH groups, and the CC to which the first UL channel is transmitted and the CC to which the second UL channel is transmitted may have different numerologies (i.e., different SCSs). Referring to FIG. 11b, in an environment where n CCs are aggregated, CCs 1 to 3 may belong to PUCCH group 1 and CCs 4 to 9 may belong to PUCCH group 2. In this case, the first UL channel may be transmitted from CC 2 belonging to PUCCH group 1, and the second UL channel may be transmitted from CC n-1 belonging to PUCCH group 2, and CC 2 and CC n-1 may have different SCSs.
[0172] In this way, the resource cycle of the first UL channel and the resource cycle of the second channel (e.g., the number of slots or the number of subframes) may differ due to different SCSs.
[0173]
[0174] In the environment described above, at least one of the following methods may be applied. Meanwhile, in the following description, the statement that the resource period of the first UL channel and the resource period of the second UL channel can be set to be the same (or different) can be extended to mean that the transmission period of the first UL channel and the transmission period of the second UL channel can be set to be the same (or different).
[0175] (Method 1) The resource period of the second UL channel and the resource period of the first UL channel may be set differently. For example, the resource period of the second UL channel may be set shorter (or longer) than the resource period of the first UL channel. In this case, the period (1 / N times) may be set shorter by the difference in SCS (N times). As another example, the resource period of the second UL channel and the resource period of the first UL channel may be set to specific values. In this case, the resource period of the second UL channel may be set shorter (or longer) than the resource period of the first UL channel. As yet another example, the resource period of the second UL channel may be set based on the smallest settable SCS (or the largest settable SCS). If there are two or more CCs where the resource of the second UL channel can be set, the resource of the second UL channel may be set in the CC having the largest (or smallest) SCS.
[0176] (Method 2) It may not be permitted for the resource period of the second UL channel and the resource period of the first UL channel to be set differently. That is, only cases where the resource period of the second UL channel and the resource period of the first UL channel are the same may be permitted. For example, the second UL channel may be transmitted only to CCs that have the same SCS as the CC transmitted to the first UL channel. As another example, the transmission period of the second UL channel may be set based on the transmission period of the first UL channel (last transmitted) (or identical to the transmission period of the first UL channel).
[0177]
[0178] Meanwhile, an indicator (1 bit or 2 bits) indicating a Cross-CC (or same CC) and / or a cross PUCCH group (or same PUCCH group) may be used to set the resource cycle of the second UL channel and the resource cycle of the first UL channel. For example, the indicator may be included in the CSI reporting setting to indicate the application of at least one of the above-mentioned Method 1 or Method 2.
[0179] For example, the operations described above may be applied when the first UL channel and the second UL channel are transmitted in a cross-CC and / or cross-PUSCCH group manner. Alternatively, as a default operation, the resource period of the first UL channel and the preset resource period of the second UL channel may be considered to be the same. If the indicator described above is explicitly present, the resource period of the first UL channel and / or the resource period of the second UL channel may be adjusted as described above.
[0180] If the resource cycle of the first UL channel and the resource cycle of the second UL channel differ due to the above-described operation, the cycle may be maintained until a specific environment. For example, the transmission cycle may be maintained until a new first UL channel is transmitted. Alternatively, the cycle may be newly set in a specific environment. For example, the cycle may be reset after the second UL channel is transmitted.
[0181]
[0182] FIG. 12 is a flowchart illustrating a beam reporting method according to one embodiment of the present invention.
[0183] Referring to FIG. 12, the terminal may perform the step of detecting at least one event (S1210), and when at least one event is detected, may perform the step of transmitting a first UL channel to a base station from a first CC (i.e., CC #1) (S1220). Next, the terminal may perform the step of transmitting a second UL channel containing a beam report according to the at least one event from a second CC (i.e., CC #2) to the base station using a preset UL resource (S1230).
[0184] At this time, the first CC and the second CC are different CCs, and the first CC and the second CC may have different SCSs. Meanwhile, the first CC and the second CC may be contiguous CCs within the same intra-band, non-contiguous CCs within the same band, or CCs of different inter-bands.
[0185] Meanwhile, the terminal may additionally perform the step of receiving a CSI (channel state information) report setting corresponding to the first UL channel from the base station, and this step may generally be performed before the step of detecting an event (S1210). In FIG. 12, the step of receiving the CSI report setting is omitted for convenience. The second CC may be indicated by the CSI report setting.
[0186] If the first CC and the second CC have different SCSs, the resources of the first UL channel and the resources of the second channel may be set to have the same period. That is, the above-described (Method 2) may be applied. Alternatively, the resources of the first UL channel and the resources of the second channel may be set to have different periods. That is, the above-described (Method 1) may be applied.
[0187] When the above (Method 1) is applied, the resource period of the second UL channel may be set to be shorter or longer than the resource period of the first UL channel based on the difference between the different SCSs, or may be set based on the smallest SCS or the largest SCS of the CCs that the second UL channel can set.
[0188]
[0189] The information(s) or operation(s) described in this disclosure may be applied differently depending on the frequency range (FR). For example, in FR1, the resource period of the first UL channel and the resource period of the second UL channel may be set differently from each other, and in FR2, the resource period of the first UL channel and the resource period of the second UL channel may be set identically. As another example, in FR1, the resource period of the first UL channel and the resource period of the second UL channel may be set identically, and in FR1, the resource period of the first UL channel and the resource period of the second UL channel may be set differently from each other.
[0190] The information(s) or operation(s) described in this disclosure may be applied differently depending on the terminal's capability (UE capability). For example, in FR1, the resource period of the first UL channel and the resource period of the second UL channel may be allowed to be set differently from each other, and depending on the terminal's capability, the resource period of the first UL channel and the resource period of the second UL channel may be set to be the same, or the resource period of the first UL channel and the resource period of the second UL channel may be set differently from each other.
[0191] The information(s) described in this disclosure may apply 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.
[0192] 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.
[0193] The information(s) described above may be transmitted via MAC-CE signaling, UCI, and / or RRC signaling (and / or another channel).
[0194] In the present disclosure, the statement that a terminal-led / event-based beam management operation is performed can be interpreted to mean that the terminal transmits a signaling instructing a base station to perform a terminal-led / event-based beam management operation.
[0195] In the present disclosure, the term "terminal-led / event-based beam management operation is stopped" can be interpreted to mean that the terminal transmits a signaling to the base station indicating that it does not perform a terminal-led / event-based beam management operation, or performs an existing base station-led beam management operation.
[0196] The methods proposed in this disclosure may be applied to additionally defined event(s) in addition to the currently defined events. The methods proposed in this disclosure may be applied to intra-cell beam management and inter-cell beam management. The methods proposed in this disclosure may be similarly applied to multi-TRP (mTRP) operations.
[0197]
[0198] 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 any type of recording device 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, allowing the computer-readable program or code to be stored and executed in a distributed manner.
[0199] 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, etc.
[0200] 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 a 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 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 of the most important method steps may be performed by such a device.
[0201] 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. Generally, it is preferable that the methods be performed by some hardware device.
[0202] 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 a terminal for beam reporting, A step of detecting at least one event; When at least one of the above events is detected, the step of transmitting a first uplink (UL) channel from the first (component carrier, CC) to the base station; and The method includes the step of transmitting a second UL channel, which includes a beam report according to at least one event in the second CC, to the base station using a preset UL resource, and The first CC and the second CC are different CCs, and the first CC and the second CC have different SCS (subcarrier spacings). method.
2. In Claim 1, The first CC and the second CC are contiguous CCs within the same intra-band, non-contiguous CCs within the same band, or CCs of different inter-bands. method.
3. In Claim 1, The method further includes the step of receiving a CSI (channel state information) reporting setting corresponding to the first UL channel from the base station, wherein the second CC is set by the CSI reporting setting. method.
4. In Claim 1, The resources of the first UL channel and the resources of the second channel are set to have the same period, method.
5. In Claim 1, The resources of the first UL channel and the resources of the second channel are configured to have different periods, method.
6. In Claim 5, The resource period of the second UL channel is set to be shorter or longer than the resource period of the first UL channel based on the difference between the different SCSs, method.
7. In Claim 5, The resource period of the second UL channel is set based on the smallest SCS or the largest SCS of the CCs that the second UL channel can set, method.
8. In a method of a base station for beam reporting, A step of receiving a first uplink (UL) channel from a first (component carrier, CC) from a terminal that has detected at least one event; and The method includes the step of receiving a second UL channel from the terminal using a preset UL resource, the second UL channel including a beam report according to at least one event in the second CC. The first CC and the second CC are different CCs, and the first CC and the second CC have different SCS (subcarrier spacings). method.
9. In Claim 8, The first CC and the second CC are contiguous CCs within the same intra-band, non-contiguous CCs within the same band, or CCs of different inter-bands. method.
10. In Claim 8, The method further includes the step of transmitting a CSI (channel state information) reporting setting corresponding to the first UL channel to the terminal, wherein the second CC is set by the CSI reporting setting, method.
11. In Claim 8, The resources of the first UL channel and the resources of the second channel are set to have the same period, method.
12. In claim 8, The resources of the first UL channel and the resources of the second channel are configured to have different periods, method.
13. In Claim 12, The resource period of the second UL channel is set to be shorter or longer than the resource period of the first UL channel based on the difference between the different SCSs, method.
14. In Claim 12, The resource period of the second UL channel is set based on the smallest SCS or the largest SCS of the CCs that the second UL channel can set, method.
15. In a terminal comprising at least one processor, The above at least one processor is the terminal: A step of detecting at least one event; When at least one of the above events is detected, the step of transmitting a first uplink (UL) channel from the first (component carrier, CC) to the base station; and Performing the step of transmitting a second UL channel, which includes a beam report according to at least one event in the second CC, to the base station using a preset UL resource, and The first CC and the second CC are different CCs, and the first CC and the second CC have different SCS (subcarrier spacings). Terminal.
16. In Claim 15, The above at least one processor further enables the terminal to perform the step of receiving a CSI (channel state information) reporting setting corresponding to the first UL channel from the base station, and the second CC is set by the CSI reporting setting, Terminal.
17. In Claim 15, The resources of the first UL channel and the resources of the second channel are set to have the same period, Terminal.
18. In Claim 15, The resources of the first UL channel and the resources of the second channel are configured to have different periods, Terminal.
19. In Claim 18, The resource period of the second UL channel is set to be shorter or longer than the resource period of the first UL channel based on the difference between the different SCSs, Terminal.
20. In Claim 18, The resource period of the second UL channel is set based on the smallest SCS or the largest SCS of the CCs that the second UL channel can set, Terminal.