Method and apparatus for configuring handover in wireless communication system
The method for continuous L1/L2-based handover in wireless communication systems addresses the challenge of handover efficiency by using Layer 1 measurement and signaling, improving data transmission and reducing delay, particularly in high-frequency bands.
Patent Information
- Application Number
- PCT/KR2024/003630
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-03-22
- Publication Date
- 2024-11-14
AI Technical Summary
Current wireless communication systems face challenges in efficiently performing handovers between cells, particularly in high-frequency bands, leading to increased path loss and reduced transmission distances, which affects the reliability and speed of data transmission.
A method and apparatus for continuous L1/L2-based handover in wireless communication systems, involving Layer 1 measurement of neighboring cells and Layer 1/L2 signaling for beam change, allowing for seamless data transmission and reception by changing to a better beam, thereby reducing delay and improving coverage.
This solution enables efficient handover operations with reduced delay and improved data transmission capabilities by using Layer 1-based beam measurement and signaling, enhancing the performance of wireless communication systems, especially in high-frequency bands.
Smart Images

Figure KR2024003630_14112024_PF_FP_ABST
Abstract
Description
Method and device for establishing handover in a wireless communication system
[0001] The present disclosure relates generally to a wireless communication system, and more particularly to a method and apparatus for transmitting a signal for L1 / L2 based handover in a wireless communication system.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.
[0008] Based on the discussion as described above, the present disclosure provides an apparatus and method for, in a wireless communication system, when a terminal is currently receiving service from a serving cell through a specific beam, measuring and reporting a beam belonging to another cell, and performing a cell change to the neighboring cell if the beam of the neighboring cell is better. In particular, a configuration method for performing Layer 1 measurement of a neighboring cell for continuous L1 / L2 (Layer1 / Layer2)-based handover (L1 / L2 triggered mobility, LTM) and a method for reporting or controlling a Layer 1 measurement value measured through L1 / L2 signaling are proposed.
[0009] According to various embodiments of the present disclosure, a method for processing a control signal in a wireless communication system may include the steps of receiving a first control signal transmitted from a base station, processing the received first control signal, and transmitting a second control signal generated based on the processing to the base station.
[0010] Through embodiments of the present disclosure, a device and method capable of effectively providing a service in a wireless communication system are provided.
[0011] Through embodiments of the present disclosure, a device and method are provided that can support continuous L1 / L2 signaling-based handover operations to neighboring cells through layer 1-based beam measurement, reduce delay time compared to existing procedures, and enable data transmission and reception after changing to a beam to another cell.
[0012] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.
[0013] FIG. 1 illustrates the structure of a wireless communication system according to one embodiment of the present disclosure.
[0014] FIG. 2 illustrates a wireless protocol structure of a wireless communication system according to one embodiment of the present disclosure.
[0015] FIG. 3 illustrates the structure of another wireless communication system according to one embodiment of the present disclosure.
[0016] FIG. 4 illustrates a scenario in which a terminal transmits and receives data through a beam of a transmission and reception point (TRP) of a neighboring cell that supports L1 / L2-based beam switching while maintaining a connection state with a serving cell, according to one embodiment of the present disclosure.
[0017] FIG. 5 illustrates a scenario in which a terminal transmits and receives data by changing a serving cell and beam to a TRP of a cell that supports L1 / L2-based beam changing, according to one embodiment of the present disclosure.
[0018] FIG. 6 illustrates a signal flow for supporting continuous L1 / L2 triggered mobility (LTM) operation according to one embodiment of the present disclosure.
[0019] FIG. 7 illustrates another L1 signal flow for supporting continuous L1 / L2 based handover (LTM) operation according to one embodiment of the present disclosure.
[0020] FIG. 8 illustrates an operation flow of a terminal for performing L1 / L2-based beam change and handover according to one embodiment of the present disclosure.
[0021] FIG. 9 illustrates an operation flow of a base station for performing L1 / L2-based beam change and handover according to one embodiment of the present disclosure.
[0022] FIG. 10 illustrates a discontinuous reception (DRX) operation for a terminal in a radio resource control (RRC) connection state according to one embodiment of the present disclosure.
[0023] FIG. 11 illustrates a method for setting channel state information (CSI) resources in a wireless communication system, according to one embodiment of the present disclosure.
[0024] FIG. 12 illustrates a method for setting up a CSI resource reporting method in a wireless communication system according to one embodiment of the present disclosure.
[0025] FIG. 13 illustrates a triggering state setting for CSI resource reporting in a wireless communication system according to one embodiment of the present disclosure.
[0026] FIG. 14 illustrates an L1 / L2 signaling method for supporting continuous L1 / L2 triggered mobility (LTM) operation according to one embodiment of the present disclosure.
[0027] FIG. 15 illustrates a method for transmitting L1 measurement reports for continuous LTM when DRX is set and applied, according to one embodiment of the present disclosure.
[0028] FIG. 16 illustrates a signal flow for semi-persistent L1 measurement reporting to support continuous L1 / L2 based handover (LTM) operation, according to one embodiment of the present disclosure.
[0029] FIG. 17 illustrates an operation of applying aperiodic L1 measurement reporting to support continuous L1 / L2 based handover (LTM) operation according to one embodiment of the present disclosure.
[0030] FIG. 18 illustrates another operation flow of a terminal for performing L1 / L2 based beam change and handover according to one embodiment of the present disclosure.
[0031] FIG. 19 illustrates another operation flow of a base station for performing L1 / L2 based beam change and handover according to one embodiment of the present disclosure.
[0032] FIG. 20 illustrates a functional configuration of a terminal according to one embodiment of the present disclosure.
[0033] FIG. 21 illustrates a functional configuration of a base station according to one embodiment of the present disclosure.
[0034] Hereinafter, the operating principles of the present invention will be described in detail with reference to the attached drawings. In the following description of the present invention, if a detailed description of a related known function or configuration is judged to unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present invention, and these may vary depending on the intention or custom of the user or operator. Therefore, the definitions should be made based on the contents throughout this specification. Terms used in the following description, such as terms for identifying connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information, are examples for the convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0035] For convenience of explanation, the present invention uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present invention is not limited to these terms and names and can be equally applied to systems conforming to other standards.
[0036] FIG. 1 illustrates the structure of a wireless communication system according to one embodiment of the present disclosure.
[0037] Referring to FIG. 1, a wireless access network of a next-generation mobile communication system may be composed of a next-generation base station (New Radio Node B, hereinafter referred to as NR NB) (110) and a New Radio Core Network (NR CN, or NG CN: Next Generation Core Network) (105). A user terminal (New Radio User Equipment, hereinafter referred to as NR UE or terminal) (115) may access an external network through the NR NB (110) and the NR CN (105).
[0038] In Fig. 1, the NR NB (110) may correspond to the eNB (Evolved Node B) of the existing LTE system. The NR NB is connected to the NR UE (user equipment) (115) via a wireless channel and can provide a service that is superior to the existing Node B. In the next-generation mobile communication system, all user traffic can be serviced through a shared channel. Therefore, the next-generation mobile communication system requires a device that collects status information such as the buffer status of UEs, the available transmission power status, and the channel status and performs scheduling, and the NR NB (110) can be in charge of this. One NR NB can typically control multiple cells. In order to implement ultra-high-speed data transmission compared to the existing LTE, it can have a bandwidth higher than the existing maximum, and by using Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology, beamforming technology can be additionally incorporated. In addition, an adaptive modulation and coding (AMC) method that determines a modulation scheme and a channel coding rate according to the channel status of the terminal may be applied. The NR CN (105) may perform functions such as mobility support, bearer setup, and QoS setup. The NR CN is a device that is responsible for various control functions as well as mobility management functions for the terminal, and may be connected to multiple base stations. In addition, the next-generation mobile communication system may also be interoperable with the existing LTE system, and the NR CN may be connected to the mobility management entity (MME) (125) through a network interface. The MME may be connected to an existing base station, eNB (130).
[0039] FIG. 2 illustrates a wireless protocol structure of a wireless communication system according to one embodiment of the present disclosure.
[0040] Referring to FIG. 2, the wireless protocol of the next-generation mobile communication system of each terminal or NR base station may include NR SDAP (service data adaptation protocol) (201, 245), NR PDCP (packet data convergence protocol) (205, 240), NR RLC (radio link control) (210, 235), and NR MAC (medium access control) (215, 230).
[0041] The main functions of NR SDAP (201, 245) may include some of the following functions:
[0042] - Transfer of user plane data
[0043] - Mapping function between QoS (quality of service) flow and data bearer for both DL and UL
[0044] - Marking function of QoS flow ID for both uplink and downlink (marking QoS flow ID in both DL and UL packets)
[0045] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).
[0046] For an SDAP layer device, a terminal can be configured by an RRC (radio resource control) message, for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device. When the SDAP header is configured, the terminal can be instructed to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink by a 1-bit indicator for reflecting the NAS (non-access stratum) QoS (NAS reflective QoS) and a 1-bit indicator for reflecting the AS (access stratum) QoS (AS reflective QoS) in the SDAP header. The SDAP header can include QoS flow ID (identifier) information indicating the QoS. The QoS information can be used for data processing priorities, scheduling information, etc. to support smooth service.
[0047] The main functions of NR PDCP (205, 240) may include some of the following functions:
[0048] - Header compression and decompression (ROHC (robust header compression) only)
[0049] - User data transfer function
[0050] - In-sequence delivery of upper layer PDUs (protocol data units)
[0051] - Out-of-sequence delivery of upper layer PDUs
[0052] - PDCP PDU reordering for reception
[0053] - Duplicate detection of lower layer SDUs (service data units)
[0054] - Retransmission function (Retransmission of PDCP SDUs)
[0055] - Encryption and decryption functions (Ciphering and deciphering)
[0056] - Timer-based SDU discard in uplink.
[0057] The reordering function of the NR PDCP device described above may refer to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number). The reordering function of the NR PDCP device may include a function of transmitting data to an upper layer in the reordered order, or may include a function of transmitting data directly without considering the order. Alternatively, the reordering function of the NR PDCP device may include a function of recording lost PDCP PDUs by reordering the order, a function of reporting a status of lost PDCP PDUs to the transmitting side, or a function of requesting retransmission of lost PDCP PDUs.
[0058] The main functions of NR RLC (210, 235) may include some of the following functions:
[0059] - Data transfer function (Transfer of upper layer PDUs)
[0060] - In-sequence delivery of upper layer PDUs
[0061] - Out-of-sequence delivery of upper layer PDUs
[0062] - ARQ function (Error Correction through ARQ (automatic repeat request))
[0063] - Concatenation, segmentation and reassembly of RLC SDUs
[0064] - Re-segmentation of RLC data PDUs
[0065] - Reordering of RLC data PDUs
[0066] - Duplicate detection function
[0067] - Protocol error detection
[0068] - RLC SDU discard function
[0069] - RLC re-establishment function
[0070] The in-sequence delivery function of the NR RLC device described above may refer to a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering multiple RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of reordering the received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number). The in-sequence delivery function of the NR RLC device may include a function of recording lost RLC PDUs by rearranging the order, a function of reporting a status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. Alternatively, the in-sequence delivery function of the NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or even if there is a lost RLC SDU, if a predetermined timer has expired, a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts, or even if there is a lost RLC SDU, a function to sequentially deliver to the upper layer all RLC SDUs received up to the present time when a predetermined timer has expired. In addition, the in-sequence delivery function of the NR RLC device may process the above-described RLC PDUs in the order they are received (e.g., in the order of arrival, regardless of the order of the sequence number) and deliver them to the PDCP device out of sequence (Out-of sequence delivery), or in the case of segments, it may receive segments that are stored in the buffer or will be received later, reconstruct them into a single complete RLC PDU, process them, and deliver them to the PDCP device.The NR RLC layer may not include a concatenation function, and the concatenation function may be performed in the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.
[0071] The out-of-sequence delivery function of the NR RLC device described above may refer to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order. The out-of-sequence delivery function of the NR RLC device may include the function of reassembling and delivering multiple RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, and may include the function of storing and arranging the RLC SN or PDCP SN of the received RLC PDUs to record any lost RLC PDUs.
[0072] NR MAC (215, 230) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.
[0073] - Mapping function (Mapping between logical channels and transport channels)
[0074] - Multiplexing / demultiplexing of MAC SDUs
[0075] - Scheduling information reporting function
[0076] - HARQ function (Error correction through HARQ (hybrid automatic repeat request))
[0077] - Priority handling between logical channels of one UE
[0078] - Priority handling between UEs by means of dynamic scheduling
[0079] - MBMS (multimedia broadcast multicast service) service identification function
[0080] - Transport format selection function
[0081] - Padding function
[0082] The NR PHY layer (220, 225) can perform an operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.
[0083] FIG. 3 illustrates the structure of another wireless communication system according to one embodiment of the present disclosure.
[0084] Referring to FIG. 3, a cell served by an NR gNB (305) operating on a beam basis may be composed of multiple Transmission Reception Points (TRPs) (310, 315, 320, 325, 330, 335, 340). The TRPs (310 to 340) represent blocks that separate some of the functions of transmitting and receiving physical signals from an existing NR base station (eNB), and may be composed of multiple antennas.
[0085] The NR gNB (305) can also be expressed as a CU (Central Unit), and the TRP can also be expressed as a DU (Distributed Unit). The functions of the NR gNB (305) and the TRP can be configured by separating each layer in the PDCP / RLC / MAC / PHY layers such as the protocol (345). That is, the TRP can perform the function of the corresponding layer with only the PHY layer (315, 325), or the TRP can perform the functions of the corresponding layers with only the PHY layer and the MAC layer (310, 335, 340), or the TRP can perform the functions of the corresponding layers with only the PHY layer, the MAC layer, and the RLC layer (320, 330).
[0086] In particular, the TRP (310-340) can use beamforming technology to transmit and receive data by generating narrow beams in multiple directions using multiple transmit / receive antennas. The user terminal (350) can connect to the NR gNB (305) and an external network through the TRP (310-340). The NR gNB (305) can collect and schedule status information such as buffer status, available transmit power status, and channel status of the terminals to provide services to the users, and can support connections between the terminals and the core network (CN) (particularly, the access and mobility management function (AMF) / session management function (SMF) (350)).
[0087] According to various embodiments of the present disclosure, the TRP is based on a structure (315, 325) that can perform the functions of the layer with only the PHY layer.
[0088] FIG. 4 illustrates a scenario in which a terminal transmits and receives data through a beam of a transmission and reception point (TRP) of a neighboring cell that supports L1 / L2-based beam switching while maintaining a connection state with a serving cell, according to one embodiment of the present disclosure. More specifically, referring to FIG. 4, as a scenario for inter-cell beam management, a scenario in which a terminal transmits and receives data through a beam of a TRP of a neighboring cell that supports L1 / L2-based beam switching while maintaining a connection state with a serving cell is illustrated.
[0089] Although this drawing describes a case where multiple cells (TRP1-Cell1, TRP2-Cell2) (410, 415) exist within one DU (Distributed unit) (405), it is also applicable to the case of inter-DU (e.g., each DU constitutes one TRP-Cell) according to various embodiments of the present disclosure. In addition, according to various embodiments of the present disclosure, although L1 / L2-based mobility (e.g., beam change and serving cell change) is supported, it goes without saying that a cell (TRP 2, Cell 2) that is not a serving cell may be expressed interchangeably as a neighbor cell, a non-serving cell, an additional cell with the PCI (physical cell ID) different from the serving cell, etc.
[0090] Referring to the existing terminal beam change procedure (445), the terminal (420) is transmitting and receiving data in a connected state through TRP 1 (410) of serving cell 1, and may be set to the optimal beam, transmission configuration indicator (TCI) state 1 (425, 430). At this stage, the terminal may receive configuration information for L3 channel measurement (radio resource management, RRM) for an additional cell (TRP 2-Cell 2) (415) having a different PCI from the serving cell through RRC configuration information from the serving cell (410), and may perform an L3 measurement operation (446) for the corresponding frequency and cell. Thereafter, the serving cell (TRP 1-Cell 1) (410) may instruct (447) a handover to the corresponding cell (TRP 2-Cell 2) (415) based on the reported measurement value. After the handover is completed, additional RRC configuration information may be transmitted (448) to the terminal (420) via TRP 2-Cell 2 (415). The additionally transmitted RRC configuration information may include UL (uplink) / DL (downlink) configuration information in the corresponding cell, L1 measurement-related settings (e.g., CSI-RS measurement and reporting), and in particular, TCI state configuration information for PDCCH (physical downlink control channel) and PDSCH (physical downlink shared channel) channels. The terminal may perform L1 measurement (449) according to the received configuration. The base station may update the TCI state through L1 / L2 signaling according to the measurement report (450). Here, TCI state 2 (440), which is an optimal beam, may be indicated. At this stage, the serving cell is Cell 1 before the handover, and Cell 2 may become the serving cell after the handover.That is, even after the handover, many procedures and time may be required until the optimal beam is indicated.
[0091] Unlike the existing terminal beam changing procedure (445) described above, an improved beam changing technique (455) according to various embodiments of the present disclosure is as follows. The terminal can receive, from the serving cell (410), a beam setting associated with an additional cell (TRP 2-Cell 2) (415) having a different PCI from the serving cell through RRC setting information (456). The beam setting associated with the additional cell (TRP 2-Cell 2) (415) having a different PCI from the serving cell (e.g., a part associating a TCI state corresponding to TRP2) can be applied by indicating a new cell ID (Physical cell ID, PCI) (e.g., additionalPCI-r17) as follows.
[0092]
[0093] In one embodiment, a unified TCI state framework may also be applied for inter-cell beam management. The unified TCI state framework is a framework that applies a common TCI state framework to uplink and downlink, and common and dedicated channels, and may be configured in either a joint UL / DL mode or a separate UL / DL mode.
[0094]
[0095] 1. Joint UL / DL mode: Set UL and DL to share the same TCI settings (in PDSCH-Config).
[0096]
[0097] 2. Separate UL / DL mode: UL and DL provide their own TCI configurations. The TCI state for DL follows the configuration in dl-OrJoint-TCIStateList-r17 (in PDSCH-Config), and the TCI state for UL follows ul-TCI-StateList-r17 (in BWP-UplinkDedicated).
[0098]
[0099] According to one embodiment, after the configuration for TRP 2-Cell 2 is provided in an RRC connection state to serving cell 1, the terminal may perform L1 measurement for TRP 2-Cell 2 according to the received configuration and report the result to the serving cell (Cell 1, 410) (457). If the serving cell determines that a change to a specific beam (TCI state 2) (435, 440) of TRP 2 (Cell 2) (415) is necessary rather than the serving cell beam (TCI state 1) (425, 430) based on the measurement result, the serving cell may trigger a beam change and instruct the terminal to change the beam through L1 / L2 signaling (458). The terminal can change the beam to a specific beam (TCI state 2) (440) of TRP 2 (Cell 2) (415) through the instruction, and perform physical channel configuration and upper layer configuration operations related to the configured beam. From this step, the terminal can remain connected to the serving cell (Cell 1) (410), but can perform data transmission and reception using the channel link of TRP 2 (Cell 2) (415) (e.g., PDCCH / PDSCH reception, PUCCH (physical uplink control channel) / PUSCH (physical uplink shared channel) transmission). That is, transmission and reception for the common control channel can be performed through the serving cell (Cell 1) (410). Afterwards, the terminal can perform L3 measurement operation according to the measurement settings set in the independent serving cell (459), receive a handover command message from the serving base station (Cell 1), and perform a serving cell change to Cell 2 (460). Through this technique (455), the terminal can perform data transmission and reception with a specific TRP 2 of Cell 2 that supports L1 / L2-based mobility while connected to the serving cell, and can continuously use the corresponding beam even after the handover.
[0100] Below, the RRC settings for the settings and operations related to L1 measurement and reporting in step (457) are specifically described. These contents can be fundamentally applied to the following embodiments of the present invention, and enhanced techniques may be added in future embodiments.
[0101] 1. L1 measurement settings (CSI-ResourceConfig, set in ServingCellConfig IE (information element) within the serving cell)
[0102] - CSI-RS (reference signal) / SSB (synchronization signal block) resources and resource pools requiring measurement (nzp (non-zero power)-CSI-RS, csi-IM (interference measurement), csi-SSB).
[0103] - Setting up CSI-RS / SSB resources that require measurement (aperiodic, semi-persistent) and triggering settings.
[0104] - When CSI-RS resources reference SSB resources, additional PCI information is provided to enable L1 measurements from neighboring cells (e.g., up to 7 neighboring cells (PCI) can be added from one serving cell).
[0105]
[0106]
[0107] 2. L1 report settings (set in ServingCellConfig IE within the serving cell)
[0108] - Report type: periodic report, semi-periodic report on PUCCH, semi-periodic report on PUSCH, aperiodic report on PUSCH (periodic, semi-persistent for PUCCH, semi-persistent for PUSCH, aperiodic)
[0109] - Report quantity
[0110] - Settings required for other reports
[0111] FIG. 5 illustrates a scenario in which a terminal transmits and receives data by changing a serving cell and beam to a TRP of a cell that supports L1 / L2-based beam switching, according to one embodiment of the present disclosure. Referring to FIG. 5 , a case is described in which multiple cells (TRP1-Cell1, TRP2-Cell2) (510, 515, 540, 545) exist within one DU (Distributed Unit) (505, 535), but according to various embodiments of the present disclosure, it is also applicable to an inter-DU case (e.g., each DU constitutes one TRP-Cell).
[0112] Unlike the existing terminal beam changing procedure (445, 455) described in FIG. 4, the improved beam changing technique (525, 575) according to various embodiments of the present disclosure is as follows.
[0113] 1. Example 1 (525): After performing inter-cell beam management (change) operation, L1 / L2 handover is performed.
[0114] 2. Example 2 (575): Immediate execution of L1 / L2 handover
[0115] First, to explain the overall operation of Embodiment 1, the terminal can receive common configuration information and dedicated configuration information for an additional cell (TRP 2-Cell 2) (515) having a different PCI from the serving cell (510) through RRC configuration information (526). For example, configuration information corresponding to ServingCellID or candidateCellID (cell ID associated with PCI), ServingCellConfigCommon, and ServingCellConfig can be provided in advance. The configuration information can be provided in the form of pre-configuration in the RRC configuration and can include configuration information for multiple cells. In addition, the configuration can include all configuration information (e.g., cell configuration, bearer configuration, security key configuration, etc.) applied when the terminal moves to the corresponding cell (e.g., handover). In addition, the configuration can include enhanced configuration by referring to the unified TCI state configuration described in step (456) of FIG. 4 and the configuration related to L1 measurement and report. In one embodiment, enhanced unified TCI state settings and L1 measurement and report settings for continuous LTM (L1 / L2 triggered mobility) may be transmitted to the terminal, which are described in detail below.
[0116] According to one embodiment, in an RRC connection state to serving cell 1, after the configuration for TRP 2-Cell 2 (515) is provided, the terminal may perform L1 measurement for the corresponding TRP 2-Cell 2 (515) according to the configuration received in step (527) and report the result to the serving cell (Cell 1) (510). If the serving cell determines that a change to a specific beam (TCI state 2) (540) of TRP 2 (Cell 2) (515) is required rather than the serving cell beam (TCI state 1) (525) based on the measurement result, the serving cell may trigger a beam change in step (528) and instruct the terminal to change the beam through L1 / L2 signaling. The terminal can perform beam change to TRP 2 (Cell 2) (515) through the instruction, and can perform data transmission and reception through the TRP 2 (Cell 2) (515). At this time, the serving cell change does not occur, and the terminal may still be RRC connected to the serving cell (Cell 1) (510). Afterwards, the terminal can still perform L1 measurement (529) for TRP 2-Cell 2 (515) and report the result to the serving cell (Cell 1) (510). The serving cell (Cell 1) (510) can instruct the terminal to perform a handover if the L1 measurement reported by the terminal satisfies the triggering condition for handover to TRP 2-Cell 2 (515) (the detailed operation is described in detail below). According to one embodiment, the instruction may be an L1 / L2 message. For example, MAC CE (control element) or DCI (downlink control information) may contain an indicator indicating a handover.
[0117] To explain the overall operation of Embodiment 2, the terminal can receive common configuration information and dedicated configuration information for an additional cell (TRP 2-Cell 2) (545) having a different PCI from the serving cell (540) through RRC configuration information (576). For example, ServingCellID or candidateCellID (cell ID associated with PCI) and configuration information corresponding to the candidate LTM cell may be provided in advance. The configuration information may be provided in the form of pre-configuration in the RRC configuration and may include configuration information for multiple cells. In addition, according to one embodiment, the configuration may include all configuration information (cell configuration, bearer configuration, security key configuration, etc.) applied when the terminal moves to the corresponding cell (e.g., handover). In addition, in the configuration, the unified TCI state configuration described in step (456) of FIG. 4 and the configuration related to L1 measurement and report may be modified and included to support continuous LTM. Hereinafter, L1 measurement and report and TCI state setting according to various embodiments of the present disclosure are specifically described.
[0118] After the configuration for TRP 2-Cell 2 (545) is provided in the RRC connection state to the serving cell 1, the terminal can perform L1 measurement for the corresponding TRP 2-Cell 2 (545) according to the configuration received in step (577) and report the result to the serving cell (Cell 1) (540). If the serving cell determines that a handover is necessary simultaneously with a beam change to a specific beam (TCI state 2) (570) of TRP 2 (Cell 2) (545) rather than the serving cell beam (TCI state 1) (545) based on the measurement result, the serving cell can trigger the beam change and handover in step (578) and instruct the terminal to perform the beam change and handover through L1 / L2 signaling. The terminal can perform a handover to TRP 2 (Cell 2) (515) simultaneously with a beam change through the instruction, and can perform data transmission and reception through the TRP 2 (Cell 2) (515). At this time, the terminal can apply the configuration information for the target cell where the handover is performed, which was previously set in step (576). Depending on whether uplink synchronization is required in the step, the terminal can perform random access, or random access to the target cell can be omitted. Detailed operations related to the above-described contents are described in detail below.
[0119] According to one embodiment, as described above, according to various embodiments of the present disclosure, unified TCI state configuration and L1 measurement and report configuration for LTM peripheral candidate cells for supporting continuous LTM are specifically described. As described in FIG. 4, in a conventional method, L1 measurement resource configuration for cells requiring measurement may be provided in CSI-ResourceConfig within ServingCellConfig IE in serving cell configuration. In particular, in order to indicate resources for peripheral cells, the PCI of a cell in which the corresponding L1 measurement resource is set may be indicated in servingAdditionalPCIList.
[0120] According to various embodiments of the present disclosure, in order to support subsequent LTM (L1 / L2 triggered mobility), a method for setting L1 measurement information for surrounding candidate cells for LTM and a setting method for a terminal to report the set L1 measurement information are specifically described. Hereinafter, a unified TCI state setting may be applied and set in the same manner to a location for setting L1 measurement resources according to various embodiments, but is not limited thereto and may of course be omitted and described.
[0121] 1. Issue 1: How to set up SSB-based L1 measurement resources for surrounding cells
[0122] - Method for configuring first L1 measurement resources: In addition to configuring a serving cell, L1 measurement resource configuration for LTM candidate cells may be provided as a separate, independent configuration. According to various embodiments of the present disclosure, L1 measurement resource configuration for LTM candidate cells may include the following IEs, but is not limited thereto, and may of course include various IEs.
[0123] Cell index indicating the LTM candidate cell (PCI or logical LTM candidate cell configuration index)
[0124] Setting up SMTC (SSB measurement timing configuration) for L1 measurement
[0125] Setting the time and frequency resources of L1 measurement resources
[0126] SCS (sub-carrrier spacing) of L1 measurement resources
[0127] In one embodiment, the ASN.1 below (e.g., ltm-L1-measConfig) may be referenced.
[0128]
[0129] - Method for setting up 2nd L1 measurement resources: L1 measurement resource settings for LTM candidate cells can be provided through L1 measurement settings (CSI-ResourceConfig) set in serving cell settings within reference cell settings.
[0130] In one embodiment, since the Reference cell configuration is configuration information commonly applied to multiple LTM candidate cells, if the L1 measurement resource configuration applied for continuous LTM operation is provided within a specific serving cell configuration of the Reference cell, the structure for setting the existing L1 measurement resources can be reused so that continuous LTM can be supported with less signaling overhead.
[0131] In one embodiment, if, after LTM execution, or if a change in L1 measurement resource configuration is required, the Reference cell configuration may be changed / modified through RRC reconfiguration.
[0132] The Reference Cell configuration may include the following configuration information, and may also list L1 measurement resources applicable to LTM candidate cells to facilitate the application of additional delta configurations. For example, the Reference Cell configuration may use the AddMod / Release structure to manage L1 measurement resources.
[0133] Cell index indicating the LTM candidate cell (PCI or logical LTM candidate cell configuration index)
[0134] Setting up SMTC (SSB measurement timing configuration) for L1 measurement
[0135] Setting the time and frequency resources of L1 measurement resources
[0136] SCS (sub-carrrier spacing) of L1 measurement resources
[0137] In one embodiment, the ASN.1 below may be referenced (e.g., configured by applying CSI-ResourceConfig within ServingCellConfig IE in lte-ReferenceConfiguration configuration).
[0138]
[0139]
[0140] 2. Issue 2: How to report SSB-based L1 measurement resources to neighboring cells
[0141] - Method for setting up a first L1 measurement report: A setting capable of reporting the configured L1 measurement resources described above within the current serving cell setting may be provided (for example, it may be provided through a serving cell setting that reports L1 measurement values for LTM candidate cells). According to one embodiment, in order to support reporting of L1 measurement values for candidate cells in successive LTMs and to provide L1 measurement reporting settings in the corresponding cell after LTM is performed once (for example, handover), the L1 measurement reporting settings may also be provided in LTM candidate cells through a serving cell setting.
[0142] In one embodiment, inter-node coordination may be required to share L1 measurement resources and reporting settings between the current serving cell and LTM candidate cells.
[0143] For example, in the L1 measurement report setting within the current serving cell, the L1 measurement report for the current LTM is provided, and after LTM is performed within each serving cell setting of the LTM candidate cells, the L1 measurement report setting that can be applied when the candidate cell becomes the serving cell can be transmitted to the terminal.
[0144] If changes to the L1 measurement reporting settings are required, the configuration of each LTM candidate cell can be updated through an RRC reset. For this purpose, inter-node coordination can be performed between the current serving cell and the LTM candidate cells.
[0145] - Method for setting up a second L1 measurement report: Within the current serving cell configuration, a setting capable of reporting the above-described set L1 measurement resources may be provided (for example, a setting capable of reporting L1 measurement resources may be provided within a serving cell configuration that reports L1 measurement values for LTM candidate cells). According to one embodiment, in order to support reporting of L1 measurement values for candidate cells in successive LTMs, after one LTM is performed (for example, a handover), an L1 measurement report setting may be provided within a serving cell configuration within a Reference cell configuration to provide the L1 measurement report setting in the corresponding cell.
[0146] In one embodiment, a procedure may be required to include L1 measurement reporting configuration within the reference cell configuration, through inter-node coordination to share L1 measurement resources and reporting configuration between the serving cell and LTM candidate cells.
[0147] For example, in the L1 measurement report setting within the current serving cell, an L1 measurement report for the current LTM can be provided, and after LTM is performed within each serving cell setting of LTM candidate cells, an L1 measurement report setting that can be applied when a specific LTM candidate cell becomes a serving cell can apply an L1 measurement report setting within a reference cell setting.
[0148] If changes to the L1 measurement reporting settings are required, each LTM reference cell configuration can be updated via an RRC reset. For this purpose, inter-node coordination can be performed between the current serving cell and the LTM candidate cells.
[0149] In the following embodiments, the entire operation to which the specific methods proposed in the present invention described above are applied is described with respect to a method for setting SSB-based L1 measurement resources for surrounding cells and a method for reporting L1 measurement resources.
[0150] FIG. 6 illustrates a signal flow for supporting continuous L1 / L2 triggered mobility (LTM) operation according to one embodiment of the present disclosure.
[0151] According to one embodiment, a terminal (601) in an RRC connection state can perform data transmission and reception with a source cell 1 (602). In step (610), the terminal can transmit layer 3 measurement values for the serving cell and neighboring cells to the source cell 1 (602) according to the configured layer 3 measurement and reporting. At this time, the actual measurement values can be transmitted to the CU (603) of the base station. This is because the base station CU (603) is responsible for RRC message processing and determines mobility.
[0152] In step (615), the base station CU (603) may generate a message (e.g., L1 / L2 config request message, HandoverPreparationInformation message, or a new message) requesting configuration information for L1 / L2-based handover to LTM candidate peripheral cells (604, 605) based on the measurement value report received from the terminal, and transmit the message through the F1 interface. Referring to FIG. 6, the candidate cell is illustrated in association with the DU, but is not limited thereto, and the candidate cell and the DU may be mapped 1:1, or multiple candidate cells may be included in one DU. According to one embodiment, the message requesting configuration information for L1 / L2-based handover may include an existing handover request message, a UE context request message, a UE context modification request message, etc., or may include a new F1 or Xn message. A message requesting configuration information for L1 / L2-based handover may request neighboring cells to be determined as candidate cells for L1 / L2-based handover, and at the same time, request RRC configuration information to be applied when L1 / L2-based handover is performed to the corresponding cell. In addition, the above-described message may include information requesting L1 measurement resource and reporting configuration for LTM candidate cells according to various embodiments of the present disclosure. The request for the L1 measurement resource and reporting configuration may be performed for each candidate cell. Referring to FIG. 6, step (615) is illustrated as a single procedure, but is not limited thereto, and the step may be performed as inter-node coordination through multiple procedures.
[0153] In one embodiment, although not shown in the drawing, the inter-node coordination procedure that can be performed for setting up L1 measurement resources and reporting at that stage is as follows.
[0154] Step 1: Receive L1 measurement resource settings from LTM candidate cells.
[0155] Step 2: The source base station CU (603) transmits the L1 measurement resource settings for continuous LTM support to each candidate cell by setting the L1 measurement resource for each collected candidate cell (e.g., the first L1 measurement resource setting method or the second L1 measurement resource setting method).
[0156] Step 3: The source base station CU (603) requests and receives L1 measurement report setup from LTM candidate cells.
[0157] Step 4: Transmit LTM-related settings to the terminal (e.g., including L1 resource reporting settings set according to the first L1 measurement resource reporting setting method).
[0158] In one embodiment, the source base station CU (603) may transmit the configuration information of the source cell and separate reference cell configuration information to the LTM candidate surrounding cells (604, 605). In one embodiment, the message transmitted by the source base station CU (603) may also include L1 measurement resource configuration for continuous LTM within the reference cell configuration information.
[0159] According to one embodiment, the reference cell configuration information that the source base station CU (603) transmits to each candidate cell (604, 605) may include configuration information that can be commonly applied to multiple target candidate cells (common configuration) to reduce signaling overhead that may occur when the target candidate cells provide configuration information for LTM. The common configuration information may include measurement configuration, bearer configuration, or, if the cells belong to the same CellGroup, configurations that are set at the CellGroup level (e.g., MAC-CellGroupConfig, RLC bearer configuration, SCell configuration, etc.). If the source base station CU (603) knows or has a procedure for knowing the configuration information for each candidate cell (604, 605), the reference cell configuration may be determined through a separate procedure for obtaining the reference cell configuration information through the procedure. The purpose of the source base station CU (603) transmitting the reference cell configuration to each candidate cell (604, 605) is to enable each candidate cell to transmit only the configuration information added based on the reference cell configuration to the source base station CU (603) so that a delta configuration (e.g., a method of configuring a complete configuration by applying a configuration added on top of the reference cell configuration or a method of configuring a complete configuration by overwriting the configuration in the target cell based on the reference cell configuration) can be applied. This can be transmitted as is to the terminal thereafter, and thus can have the effect of reducing the signaling of the RRC message transmitted to the terminal.
[0160] In one embodiment, furthermore, when the source base station CU (603) transmits the reference cell configuration to each of the candidate cells (604, 605), the candidate cell configuration may be provided as a complete RRC configuration, if it can be omitted. For example, the RRC configuration information (CellGroupConfig 1, ..., CellGroupConfig N) applied when an L1 / L2-based handover is performed may be transmitted at either a cell group level or an RRC message level. As described above, the message (615) requesting configuration information for an L1 / L2-based handover may be transmitted including both information and configuration for the reference cell, and may include at least one of an indicator instructing the candidate peripheral cells (604, 605) to transmit the reference cell configuration information or the configuration information for the L1 / L2-based handover by applying a delta configuration. The above-described indicator may be requested for each cell or may be requested commonly for all cells.
[0161] Candidate peripheral cells (604, 605) that have received a message requesting configuration information for L1 / L2-based handover in step (620) can generate configuration information of each candidate peripheral cell when L1 / L2-based handover is applied based on the configuration information of the transmitted reference cell, based on the delta configuration or without applying it.
[0162] In step (625), each candidate surrounding cell (604, 605) can store the configuration information for the generated L1 / L2-based handover in a configuration information response message for the L1 / L2-based handover (L1 / L2 config response message) and transmit it to the base station CU (603).
[0163] In step (630), the base station CU (603) may transmit the generated RRC message to the source cell (602) based on the configuration information received from each candidate cell, and the source cell (602) may transmit the received message to the terminal. The RRC message may include configuration information (Pre-Config1, ..., Pre-ConfigN) for surrounding candidate cells to which L1 / L2-based handover (LTM) is applied. The Pre-Config included in the RRC message may include information on the CellGroupConfig configuration received from the LTM candidate cells in step (625), the bearer configuration for the LTM candidate cells generated by the base station, and the Layer 3 (Layer 3, L3) measurement configuration.
[0164] In step (635), the terminal that receives the RRC message can decode and process the RRC message. The processing procedure performed by the terminal may include ASN.1 decoding and validity determination of the received message, and a method for storing or managing the configuration contents. In addition, the terminal can store the LTM configuration information for each candidate cell decoded in step (635) as complete configuration information in a buffer (e.g., memory) of the terminal, and simultaneously store and manage the received reference cell configuration information in the buffer (e.g., memory) of the terminal. According to one embodiment, the reference cell configuration information may be omitted from the RRC message (or the configuration information for each LTM candidate cell) of step (630). In this case, the terminal may recognize that there is no reference cell configuration information, and may determine and store the configuration information for the received LTM target candidate cells as complete configuration information. In this case, the reference cell configuration information may not be stored separately (e.g., may operate as empty). For example, the delta configuration may not be applied.
[0165] In step (640), the terminal can perform L1 (layer 1) measurement and reporting for each candidate surrounding cell, and at the same time, in step (645), the terminal can also perform L3 measurement and reporting according to the received settings.
[0166] In step (650), the source cell that receives the L1 measurement report can make a handover decision based on the corresponding measurement value and can instruct the terminal to perform L1 / L2 handover. In step (650), MAC CE and DCI including a handover indicator can be used for L1 / L2 signaling. The L1 measurement value transfer and handover decision for determining L1 / L2 handover in steps (640) and (650) can be performed by the source cell (DU) or the source base station CU. If the base station CU makes all decisions, the source cell can transfer the L1 measurement value received from the terminal to the base station CU and transfer L1 / L2 signaling to the terminal according to the handover decision instruction of the base station CU. However, when the source cell makes the final decision, the source cell may not transmit the received L1 measurement values to the base station, but may determine the handover on its own based on measurement value criteria (e.g., threshold values or measurement value ranges) for making handover decisions for each candidate neighboring cell received from the previous base station, and may transmit L1 / L2 signaling to the terminal accordingly.
[0167] When an L1 / L2 handover instruction is transmitted to the terminal at step (655), the terminal can initiate a handover procedure and start a timer for L1 / L2 handover. The timer may be a newly set timer for LTM, or an existing T304 timer may be reused.
[0168] In step (660), the terminal may apply settings for the target cell to which the L1 / L2 handover is applied. For example, the terminal may replace the current settings with the complete configuration information of the designated LTM target cell previously stored in the terminal. This may be one of the LTM candidate neighboring cell settings previously received in step (630) and may be a setting stored in the terminal.
[0169] In step (665), the terminal may perform random access if random access is required for the target cell according to the applied settings, or the random access procedure may be omitted if random access is not indicated or required (e.g., if uplink synchronization has already been performed or aligned).
[0170] In step (670), the terminal may perform a handover completion procedure with the target cell. This completion procedure may be a handover completion procedure for LTM. This procedure may vary depending on the method of indicating the handover completion. In addition, this procedure may be a process of transmitting an RRCReconfigurationComplete message when the target cell configuration is received at the RRC message level. However, if the cell-level or cell group-level configuration is received, this may be replaced with a new handover completion indication message (e.g., a new RRC message or MAC CE).
[0171] In addition, since this scenario considers application to intra-CU, the target cell (DU) (604) that receives the handover completion message in step (675) can forward the received message to the base station CU (603). At this time, the handover completion message received through the F1 interface can be forwarded as is, or the target cell (604) can reprocess the message based on the received information and forward it.
[0172] In step (680), the base station CU (603) may transmit information about the completion of the handover to the source cell (602) and instruct it to release the terminal context.
[0173] As illustrated in step (685), various embodiments of the present invention may support subsequent LTM operations. The subsequent LTM operations may include the UE continuously performing the LTM procedure, as long as the LTM configuration information (e.g., configuration for target candidate cells and reference cell configuration information, etc.) received in step (630) is stored in the UE as is, and the UE does not change / release / add the corresponding LTM configuration information through a separate RRC configuration. If it is necessary to update the reference cell configuration information, new RRC configuration information may be transmitted to the UE, allowing the subsequent LTM operation to be performed. For example, all or part of the procedures described in the above-described drawing may be triggered and performed again.
[0174] According to one embodiment, if the terminal is provided with reference cell configuration information in step (630), the terminal may store it in the terminal buffer and, if there is no update for a separate configuration, may use the configuration as reference cell configuration information even after performing LTM (step (650)) (for example, the terminal may apply the reference cell configuration and LTM candidate configuration values stored in successive LTMs). In addition, if the terminal is not provided with reference cell configuration information in step (630) in an RRC connected state, the terminal may empty and store the reference cell configuration or store configuration information for the corresponding source cell (PCell) from which the LTM configuration information was received as reference cell configuration information, depending on some of the terminal operation options described above.
[0175] FIG. 7 illustrates another L1 signal flow for supporting continuous L1 / L2 based handover (LTM) operation according to one embodiment of the present disclosure.
[0176] According to one embodiment, a terminal (701) in an RRC connection state can perform data transmission and reception with a source cell 1 (702). In step (710), the terminal can transmit layer 3 measurement values for the serving cell and neighboring cells to the source cell 1 (702) according to the configured layer 3 measurement and reporting. At this time, the actual measurement values can be transmitted to the CU (703) of the base station. This is because the base station CU (703) is responsible for RRC message processing and determines mobility.
[0177] In steps (712) and (715), the base station CU (703) may generate a message (e.g., L1 / L2 config request message or HandoverPreparationInformation message or a new message) requesting configuration information for L1 / L2-based handover to LTM candidate neighboring cells (704, 705) based on the measurement value report received from the terminal, and transmit the message through the F1 interface. Referring to FIG. 7, the candidate cell is illustrated in association with the DU, but is not limited thereto, and the candidate cell and the DU may be mapped 1:1, or multiple candidate cells may be included in one DU. According to one embodiment, the message requesting configuration information for L1 / L2-based handover may include an existing handover request message, a UE context request message, a UE context modification request message, etc., or may include a new F1 or Xn message. A message requesting configuration information for L1 / L2-based handover may request neighboring cells to be determined as candidate cells for L1 / L2-based handover, and at the same time, request RRC configuration information to be applied when L1 / L2-based handover is performed to the corresponding cell. In addition, the above-described message may include information requesting L1 measurement resource and reporting configuration for LTM candidate cells according to various embodiments of the present disclosure. The request for the L1 measurement resource and reporting configuration may be performed for each candidate cell. Referring to FIG. 7, steps 712 and 715 may appear to be the same procedure, but inter-node coordination may be performed as multiple procedures performed for different purposes for the second L1 measurement resource reporting method according to various embodiments of the present disclosure.For example, step (712) may be a procedure for sharing L1 measurement resources and including L1 measurement reports in reference cell settings, and step (715) may be a procedure for transmitting reference cell settings including the settings.
[0178] In one embodiment, although not shown in the drawing, the inter-node coordination procedure that can be performed for setting up L1 measurement resources and reporting at that stage is as follows.
[0179] Step 1: Receive L1 measurement resource settings from LTM candidate cells.
[0180] Step 2: The source base station CU (703) transmits L1 measurement resource settings for continuous LTM support to each candidate cell by setting L1 measurement resources for each collected candidate cell (e.g., the first L1 measurement resource setting method or the second L1 measurement resource setting method).
[0181] Step 3: The source base station CU (703) requests and receives L1 measurement report setup from LTM candidate cells (step 712).
[0182] Step 4: The source base station CU (703) requests LTM configuration information from LTM candidate cells (step (715)).
[0183] Step 5: Transmit LTM-related settings to the terminal (e.g., including L1 resource reporting settings set according to the second L1 measurement reporting setting method)
[0184] In one embodiment, the source base station CU (703) may transmit the configuration information of the source cell and separate reference cell configuration information to the LTM candidate neighboring cells (704, 705). In one embodiment, the message transmitted by the source base station CU (703) may include L1 measurement resource configuration for continuous LTM within the reference cell configuration information.
[0185] According to one embodiment, the reference cell configuration information that the source base station CU (703) transmits to each candidate cell (704, 705) may include configuration information that can be commonly applied to multiple target candidate cells (common configuration) to reduce signaling overhead that may occur when the target candidate cells provide configuration information for LTM. The common configuration information may include measurement configuration, bearer configuration, or, if the cells belong to the same CellGroup, configurations that are set at the CellGroup level (e.g., MAC-CellGroupConfig, RLC bearer configuration, SCell configuration, etc.). If the source base station CU (703) knows or has a procedure for knowing the configuration information for each candidate cell (704, 705), the reference cell configuration may be determined through a separate procedure for obtaining the reference cell configuration information. The purpose of the source base station CU (703) transmitting the reference cell configuration to each candidate cell (704, 705) is to enable each candidate cell to transmit only the configuration information added based on the reference cell configuration to the source base station CU (703) so that a delta configuration (e.g., a method of configuring a complete configuration by applying a configuration added on top of the reference cell configuration or a method of configuring a complete configuration by overwriting the configuration in the target cell based on the reference cell configuration) can be applied. This can be transmitted as is to the terminal thereafter, and thus can have the effect of reducing the signaling of the RRC message transmitted to the terminal.
[0186] In one embodiment, furthermore, when the source base station CU (703) transmits the reference cell configuration to each of the candidate cells (704, 705), the candidate cell configuration may be provided as a complete RRC configuration, if it can be omitted. For example, the RRC configuration information (CellGroupConfig 1, ..., CellGroupConfig N) applied when an L1 / L2-based handover is performed may be transmitted at either a cell group level or an RRC message level. As described above, the message (715) requesting configuration information for an L1 / L2-based handover may be transmitted including both information and configuration for the reference cell, and may include at least one of an indicator instructing the candidate peripheral cells (704, 705) to transmit the reference cell configuration information or the configuration information for the L1 / L2-based handover by applying a delta configuration. The above-described indicator may be requested for each cell or may be requested commonly for all cells.
[0187] Candidate peripheral cells (704, 705) that have received a message requesting configuration information for L1 / L2-based handover in step (720) can generate configuration information of each candidate peripheral cell when L1 / L2-based handover is applied based on the configuration information of the transmitted reference cell, based on the delta configuration or without applying it.
[0188] In step (725), each candidate surrounding cell (704, 705) can store the configuration information for the generated L1 / L2-based handover in an L1 / L2-based handover configuration information response message (L1 / L2 config response message) and transmit it to the base station CU (703).
[0189] In step (730), the base station CU (703) may transmit an RRC message generated based on the configuration information received from each candidate cell to the source cell (702), and the source cell (702) may transmit the received message to the terminal. The RRC message may include configuration information (Pre-Config1, ..., Pre-ConfigN) for surrounding candidate cells to which L1 / L2-based handover (LTM) is applied. The Pre-Config included in the RRC message may include information on the CellGroupConfig configuration received from the LTM candidate cells in step (725), the bearer configuration for the LTM candidate cells generated by the base station, and the Layer 3 (Layer 3, L3) measurement configuration.
[0190] In step (735), the terminal that receives the RRC message can decode and process the RRC message. The processing procedure performed by the terminal may include ASN.1 decoding and validity determination of the received message, and a method for storing or managing the configuration contents. In addition, the terminal may store the LTM configuration information for each candidate cell decoded in step (735) as complete configuration information in a buffer (e.g., memory) of the terminal, and simultaneously store and manage the received reference cell configuration information in the buffer (e.g., memory) of the terminal. According to one embodiment, the reference cell configuration information may be omitted from the RRC message (or the configuration information for each LTM candidate cell) of step (730). In this case, the terminal may recognize that there is no reference cell configuration information, and may determine and store the configuration information for the received LTM target candidate cells as complete configuration information. In this case, the reference cell configuration information may not be stored separately (e.g., may operate as empty). For example, the delta configuration may not be applied.
[0191] In step (740), the terminal can perform L1 (layer 1) measurement and reporting for each candidate surrounding cell, and at the same time, perform L3 measurement and reporting according to the settings received in step (745).
[0192] In step (750), the source cell that has received the L1 measurement report can make a handover decision based on the corresponding measurement value and can instruct the terminal to perform L1 / L2 handover. In step (750), MAC CE and DCI including a handover indicator can be used as L1 / L2 signaling. The L1 measurement value transfer and handover decision for determining the L1 / L2 handover in steps (740) and (750) can be performed by the source cell (DU) or the source base station CU. If the base station CU makes all decisions, the source cell can transfer the L1 measurement value received from the terminal to the base station CU and transfer L1 / L2 signaling to the terminal according to the handover decision instruction of the base station CU. However, when the source cell makes the final decision, the source cell may not transmit the received L1 measurement values to the base station, but may determine the handover on its own based on measurement value criteria (e.g., threshold values or measurement value ranges) for making handover decisions for each candidate neighboring cell received from the previous base station, and may transmit L1 / L2 signaling to the terminal accordingly.
[0193] When an L1 / L2 handover instruction is transmitted to the terminal at step (755), the terminal may initiate a handover procedure and start a timer for L1 / L2 handover. The timer may be a newly set timer for LTM, or may be a reused existing T304 timer.
[0194] In step (760), the terminal may apply settings for the target cell to which the L1 / L2 handover is applied. For example, the terminal may replace the current settings with the complete configuration information of the designated LTM target cell previously stored in the terminal. This may be one of the LTM candidate neighboring cell settings previously received in step (730) and may be a setting stored in the terminal.
[0195] In step (765), the terminal may perform random access if random access is required for the target cell according to the applied settings, and if random access is not indicated or required (e.g., if uplink synchronization has already been performed or aligned), the random access procedure may be omitted.
[0196] In step (770), the terminal may perform a handover completion procedure with the target cell. This completion procedure may be a handover completion procedure for LTM. This procedure may vary depending on the method of indicating the handover completion. In addition, this procedure may be a process of transmitting an RRCReconfigurationComplete message when the target cell configuration is received at the RRC message level. However, if the cell-level or cell group-level configuration is received, this may be replaced with a new handover completion indication message (e.g., a new RRC message or MAC CE).
[0197] Additionally, since this scenario considers application to intra-CU, the target cell (DU) (704) that receives the handover completion message in step (775) can forward the received message to the base station CU (703). At this time, the handover completion message received via the F1 interface can be forwarded as is, or the target cell (704) can reprocess the message based on the received information and forward it.
[0198] In step (780), the base station CU (703) may transmit information about the completion of the handover to the source cell (702) and instruct it to release the terminal context.
[0199] As illustrated in step (785), various embodiments of the present invention may support subsequent LTM operations. The subsequent LTM operations may include the UE continuously performing the LTM procedure, as long as the LTM configuration information (e.g., configuration for target candidate cells and reference cell configuration information, etc.) received in step (730) is stored in the UE as is, and the corresponding LTM configuration information is not changed / released / added through a separate RRC configuration. If it is necessary to update the reference cell configuration information, new RRC configuration information may be transmitted to the UE, allowing the subsequent LTM operation to be performed. For example, all or part of the procedures described in the above-described drawing may be triggered and performed again.
[0200] According to one embodiment, if the terminal is provided with reference cell configuration information in step (730), the terminal may store it in the terminal buffer and, if there is no update for a separate configuration, may use the configuration as reference cell configuration information even after performing LTM (step (750)) (for example, the terminal may apply the reference cell configuration and LTM candidate configuration values stored in successive LTMs). In addition, if the terminal is not provided with reference cell configuration information in step (730) in an RRC connected state, the terminal may empty and store the reference cell configuration or store configuration information for the corresponding source cell (PCell) from which the LTM configuration information was received as reference cell configuration information, depending on some of the terminal operation options described above.
[0201] FIG. 8 illustrates an operational flow of a terminal for performing L1 / L2-based beam switching and handover according to one embodiment of the present disclosure. In particular, the terminal operation according to various embodiments of the present disclosure may be characterized by a method for performing L1 measurements and reports according to L1 measurement resource and reporting settings for continuous LTM operation.
[0202] In step (805), the terminal in the connected state can receive configuration information related to the neighboring cell applied after L1 / L2-based movement is indicated through an RRC reconfiguration message from the serving cell. The specific configuration method and contents are described in FIGS. 6 and 7. In addition, referring to FIG. 8, although omitted and not illustrated before the RRC configuration information, the terminal may have received basic RRC configuration from the base station and may perform an operation of reporting layer 3 measurement values for neighboring cells. In particular, the configuration information for the LTM candidate cell applied after L1 / L2-based movement is indicated received in step (805) may be transmitted with a delta configuration applied based on the configuration for one reference cell. The terminal can know which reference cell is known in advance or indicated through the RRC configuration and which configuration information for the reference cell is indicated. Since the configuration for neighboring cells other than the reference cell is transmitted as a common reference cell configuration and as additional configurations thereto, signaling overhead can be reduced. In the configuration of the above-described steps, the terminal can receive configuration information related to resources and reports for L1 measurements on LTM candidate cells. For detailed configuration methods, refer to the first L1 measurement resource configuration method / second L1 measurement resource configuration method and the first L1 measurement report configuration method / second L1 measurement report configuration method described above.
[0203] In step (810), the terminal can decode the configuration for the received LTM candidate cells based on the configuration of the reference cell, and store and manage the complete configuration that is actually applied (for example, an operation of storing the configuration delta-configured based on the reference cell as a complete configuration by referring to the reference cell configuration) in a separate buffer and list. Alternatively, the terminal may store and manage the received RRC configuration as it is in the buffer, without decoding the received configuration based on the reference cell and storing and managing the configuration that is actually applied. As described above in FIG. 6, when the terminal receives a configuration in which the reference cell configuration is omitted, the terminal can recognize that there is no reference cell configuration information, and can determine and store the configuration information for the received LTM target candidate cells as complete configuration information. In this case, the terminal may not separately store the reference cell configuration information (for example, operate as empty). For example, the delta configuration may not be applied. The advantage of having the terminal decode the settings for surrounding cells based on the reference cell at this stage and store the settings to be actually applied may be that when an actual L1 / L2-based handover is instructed, the handover for the corresponding cell can be applied immediately, so there is no additional delay time.
[0204] In step (815), the terminal can perform L1 measurements associated with candidate neighboring cells while maintaining a connection with the serving cell, and report the measurement results to the serving cell according to a preset L1 measurement reporting setting. In addition, the terminal can measure neighboring cells independently of the operation according to the L3 measurement setting, and report the measurement results to the base station according to the L3 measurement reporting setting. The serving cell can determine whether to change the beam of the terminal and perform a handover based on the received measurement results.
[0205] In step (820), if the serving cell determines that a change to a specific beam of a neighboring cell is necessary rather than a specific beam of the serving cell, the serving cell may instruct a handover and beam change of the terminal through L1 / L2 signaling. Referring to FIG. 8, the L1 / L2 signaling may be a MAC CE and a DCI, and both information indicating a specific beam of a neighboring cell and a change of serving cell may be indicated in the MAC CE (for example, when the MAC CE indicates only one beam), or a plurality of specific beams of an LTM target cell may be indicated in the MAC CE, and then a handover may be indicated in which one of the plurality of beams of the neighboring cell activated by the MAC CE is selected in the transmitted DCI.
[0206] In step (825), the terminal can identify whether a handover is indicated from the MAC CE and DCI signaling received in step (815), and can perform an LTM handover operation. If the MAC CE and DCI indicate a handover (e.g., the MAC CE itself indicates a handover, or the MAC CE activates multiple beams and the DCI indicates a handover while indicating one of the beams), the terminal can perform a handover to a cell associated with the indicated TCI state.
[0207] If random access is successfully performed in step (830) and handover is successful, the terminal can also apply the settings for the corresponding LTM target cell that were stored in step (810).
[0208] In step (835), the terminal can maintain previously stored LTM setting information and reference cell setting information.
[0209] In step (840), the terminal can connect to the designated LTM target cell and transmit and receive data using the designated beam. The terminal can perform channel measurement reporting according to the LTM settings and continue to perform continuous LTM operations.
[0210] If the LTM handover fails in step (830), the terminal may fall back to the previous source cell and attempt to connect in step (845). To this end, the terminal must maintain configuration information for the source cell even if LTM is triggered. In addition, even after falling back to the source cell, the terminal may maintain LTM configuration information and reference cell configuration information for the LTM target cell. This may be to enable LTM to be triggered again according to the existing configuration. If the fallback to the source cell is not performed perfectly, the terminal may perform an RRC re-establishment procedure to reselect connectable cells. If the cell found through cell reselection is one of the LTM candidate cells, the terminal may attempt to connect by applying the RRC configuration preset for the cell.
[0211] In step (850), the terminal may generate a handover failure report message from the cell where the connection was performed (e.g., the source cell or the target cell) and transmit it to the base station. The handover failure report message may include a UEInformationResponse or another uplink RRC message. The terminal may also report this via a new MAC CE or uplink control information (UCI). The information included in the handover failure report message may include the following information.
[0212] - An indicator indicating that the handover failed due to LTM failure.
[0213] - Target cell information that failed when attempting LTM: LTM cell configuration index or actual cell index (Physical Cell Index, PCI) information.
[0214] In one embodiment, the source base station may be notified by a handover failure message report that the LTM attempt has failed and has fallen back to the corresponding cell. In addition, if the cell found through cell reselection after the RRC re-establishment procedure is a cell other than the LTM candidate cells, the terminal may maintain the LTM configuration information and reference cell configuration information stored in the corresponding cell in step (855). Alternatively, the terminal may release the stored LTM-related configuration information and reference cell configuration information. Alternatively, the base station may explicitly designate an action to the terminal through configuration.
[0215] FIG. 9 illustrates an operation flow of a base station for performing L1 / L2-based beam change and handover according to one embodiment of the present disclosure.
[0216] In step (905), the base station receives an L3 measurement value report from the terminal, and based on the terminal's measurement values for surrounding frequencies and cells, can identify whether the terminal requires handover and which cells are handover candidate cells.
[0217] In step (910), the base station may request configuration information for L1 / L2-based handover from neighboring cells and receive responses from the corresponding cells. In this step, the base station may transmit configuration information for the current source cell and reference cell configuration information to the neighboring cells. The base station may receive RRC configuration information to which delta configuration is applied based on the reference cell configuration information from neighboring cells and LTM candidate cells. In addition, in this step, inter-node coordination for L1 measurement resource and report configuration according to various embodiments of the present disclosure may be performed. The first L1 measurement resource configuration method / second L1 measurement resource configuration method and the first L1 measurement report configuration method / second L1 measurement report configuration method described above may be referenced. Although omitted in this drawing, configuration related to L3 measurement configuration and basic RRC configuration may be provided before this step.
[0218] In step (915), the base station may transmit to the connected terminal the RRC configuration message generated, including the neighboring cell configuration information and L1 measurement resource / reporting configuration information received in step (910). For example, the base station may transmit configuration information in neighboring cells applied after L1 / L2-based movement is indicated by an RRC reconfiguration message from the serving cell. Detailed configuration methods and contents are specifically described in FIGS. 6 and 7.
[0219] In step (920), the base station can receive a report on L1 and L3 measurement values from the terminal, and at this time, the L1 measurement value may be a neighboring cell (non-serving cell) that supports L1 / L2-based mobility. The serving cell can determine whether to change the beam of the terminal and whether to perform a handover based on the received measurement results. If the serving cell determines that a change to a specific beam of a neighboring cell is necessary rather than a specific beam of the serving cell, the serving cell can instruct an LTM handover of the terminal through L1 / L2 signaling in step (925). The L1 / L2 signaling may be MAC CE or DCI, and may include information instructing a change to a specific beam of a neighboring cell. In addition, an existing handover through an RRC message may also be performed and instructed independently in this step. This may be because the base station and the serving cell independently perform the determination of LTM and Layer 3 handover.
[0220] In step (935), if the base station receives a handover completion message from the terminal, it can confirm that the corresponding LTM operation has been successfully completed, and accordingly, it can notify the previous source cell of the handover completion and request the release of the terminal context. In addition, if the base station receives a handover failure report message including information that the handover has failed, the base station can receive a message notifying that the terminal has attempted to connect to the corresponding cell again after the handover failure. The handover failure report message may include a UEInformationResponse or another uplink RRC message. In addition, the base station can receive this through a new MAC CE or uplink control information (UCI). The information included in the handover failure report message may include the following information.
[0221] - An indicator indicating that the handover failed due to LTM failure.
[0222] - Target cell information that failed when attempting LTM: LTM cell configuration index or actual cell index (Physical Cell Index, PCI) information.
[0223] The source base station can report a handover failure message to indicate that the LTM attempt failed and fell back to that cell.
[0224] According to embodiments of the present disclosure, methods for triggering L1 measurement reporting with L1 / L2 signaling for continuous LTM operation are described in relation to the above-described L1 measurement reporting method, and specific signaling and overall operation for each method are described.
[0225] FIG. 10 illustrates a discontinuous reception (DRX) operation for a terminal in a radio resource control (RRC) connection state according to one embodiment of the present disclosure.
[0226] In one embodiment, DRX is defined even in the RRC connected state, and its operation method may differ from DRX in the IDLE state. As described above, for a terminal to continuously monitor the PDCCH to obtain scheduling information may result in significant power consumption.
[0227] According to one embodiment, a basic DRX operation may have a DRX cycle (1000) and monitor PDCCH only during the on-duration (1005) time. In a connected mode, the DRX cycle may be set to two values: long DRX and short DRX. In general, the long DRX cycle is applied, and if necessary, the base station may trigger a short DRX cycle using MAC CE. After a certain period of time, the terminal may change from the short DRX cycle to the long DRX cycle. Initial scheduling information of a specific terminal is provided only on a predetermined PDCCH. Therefore, the terminal may minimize power consumption by periodically monitoring only the predetermined PDCCH.
[0228] According to one embodiment, if scheduling information for a new packet is received (1010) via PDCCH during the on-duration (1005), the UE may start a DRX inactivity timer (1015). The UE may remain active during the DRX inactivity timer (e.g., the UE may continue to monitor the PDCCH). In addition, the UE may also start a HARQ round trip time (RTT) timer (1020). The HARQ RTT timer may be applied to prevent the UE from unnecessarily monitoring the PDCCH during the HARQ RTT time, and the UE does not need to perform PDCCH monitoring during the timer operation time. However, while the DRX inactivity timer and the HARQ RTT timer operate simultaneously, the UE may continue to monitor the PDCCH based on the DRX inactivity timer. When the HARQ RTT timer expires, a DRX retransmission timer (1025) may be started. While the DRX retransmission timer is running, the terminal can perform PDCCH monitoring. Typically, during the DRX retransmission timer operation time, scheduling information for HARQ retransmission can be received (1030). Upon receiving the scheduling information, the terminal can immediately stop the DRX retransmission timer and start the HARQ RTT timer again. The above-described operations can be continuously performed until the packet is successfully received (1035).
[0229] According to one embodiment, configuration information related to DRX operation in connected mode may be transmitted to the terminal via an RRCConnectionReconfiguration message. In LTE, the on-duration timer, DRX inactivity timer, and DRX retransmission timer may be defined by the number of PDCCH subframes. However, in NR, unlike in LTE, the timer value may be set to an actual time unit such as ms, symbol, or slot, rather than the number of subframes. This is because, unlike in LTE, in NR, the unit for PDCCH monitoring is not a subframe, depending on the sub-carrier spacing (SCS) set in the bandwidth part (BWP), and this is to specify the exact timing. After the timer starts, the timer may expire when the time interval for PDCCH monitoring has passed by the set number. In LTE FDD (frequency division duplex), all downlink subframes can belong to PDCCH subframes, and in TDD (time division duplex), downlink subframes and special subframes can correspond to PDCCH subframes. For example, in TDD, downlink subframes, uplink subframes, and special subframes can exist in the same frequency band. Among these, downlink subframes and special subframes can be considered PDCCH subframes. Similarly, in NR, the time interval for PDCCH monitoring can differ depending on FDD and TDD, and can be set in symbol or slot units rather than subframe units.
[0230] In one embodiment, the base station can configure two states, longDRX and shortDRX. The base station can utilize one of the two states described above, considering power preference indication information reported by the terminal, terminal mobility record information, or the characteristics of the configured data radio bearer (DRB). Transition between the two states can be performed based on whether a specific timer expires or a specific MAC CE is transmitted to the terminal.
[0231] According to various embodiments of the present disclosure, the overall structure related to setting and reporting related to channel state information (CSI) in a wireless communication system will be described. Basically, time / frequency resources for reporting CSI can be controlled by a base station. Parameters for CSI reporting can include a Channel Quality Indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indication (LI), a rank indication (RI), and L1-RSRP (reference signal received power). A terminal can receive N reporting settings (CSI-ReportConfig), M resource settings (CSI-ResourceConfig), and one ReportTriggerList, which is a list of trigger states, through an RRC message received from the base station. Here, N and M can be set to multiple constant values through RRC and can have different values. The above list may include CSI-ReportConfigs indicating Resource Set IDs corresponding to channels and interference, and may be used for the purpose of triggering reporting for those resource sets.
[0232] According to various embodiments of the present disclosure, methods for setting CSI resources (e.g., L1 measurement resources) and reporting methods are specifically described below with reference to FIGS. 11, 12, and 13 (herein, CSI measurement and L1 measurement are used interchangeably but may also be used with the same meaning). The overall operation described below can be applied to the continuous LTM proposed in the present invention, and the embodiments below are described focusing on the differences. For example, L1 measurement and reporting operations in LTM without separate description can follow the operations described in FIGS. 11, 12, and 13.
[0233] FIG. 11 illustrates a method for setting channel state information (CSI) resources in a wireless communication system, according to one embodiment of the present disclosure.
[0234] Referring to FIG. 11, the CSI resource configuration (1105) may include up to 16 CSI resource sets (1115, 1120, 1130, 1140) in each CSI-ResourceConfing (1110, 1125, 1135), and the configuration may be applied to a DL BWP configured with an RRC message. In addition, all CSI resource settings (CSI-ResourceConfing) may be linked to a CSI report setting configured with the same DL BWP.
[0235] CSI resource sets (1115, 1120, 1130, 1140) may include CSI-RS resources configured as NZP CSI-RS or CSI-IM, and may include SS (synchronization signal) / PBCH (physical broadcast channel) block resources for L1-RSRP (Layer 1 Reference Signal Reference Power) calculation. In addition, CSI-RS resources may be distinguished by ResourceConfigType in the time domain, and the type may be set to aperiodic (AP), periodic (P), or semi-persistent (SP). However, the number of CSI-RS resource sets for P / SP CSI resource setting is limited to one, and the periodicity and slot offset in the setting may follow the numerology of the corresponding DL BWP. In addition, the CSI resource setting may specify the channel and interference that require measurement. For example, the CSI resource setting can set CSI IM / NZP CSI-RS to be used for interference (1125, 1135) or the NZP CSI-RS resource (1110) can be set to be used for channel measurement.
[0236] FIG. 12 illustrates a method for setting up a CSI resource reporting method in a wireless communication system according to one embodiment of the present disclosure.
[0237] Referring to FIG. 12, as a CSI reporting method setting (1205) in the time domain, the report type can be set to Aperiodic, Semi-persistent, or Periodic for each CSI-ReportConfig (1210, 1230, 1245). In the case of P / SP CSI reporting, the set periodicity and slot offset can be applied to the numerology of the corresponding UL BWP, and in the case of Aperiodic, transmission resources can be directly indicated through DCI. In addition, the CSI resource reporting configuration can indicate whether the corresponding CSI report is CSI-related or L1-RSRP-related through ReportQuantity. ReportFreqConfiguration can indicate the reporting granularity in the frequency domain, and can indicate whether the CSI reporting band and PMI / CQI reporting are wideband or sub-band. In addition, timeRestrictionForChannelMeasurements, timeRestrictionForInterferenceMeasurements can be set for time domain CSI measurement restrictions, and codebook subset restriction can be provided in CodebookConfig. In addition, one CSI-ReportConfig (1210, 1230, 1245) can set a set of NZP CSI resources (1215, 1235, 1250) as mandatory, and optionally associate NZP interference (1225) and ZP interference (1220, 1240) with the CSI resource configuration setting. This may mean that CSI reporting includes CSI resources by default and can additionally report on interference resources.
[0238] As described above, the configuration for CSI reporting can be set to Aperiodic (using PUSCH), Periodic (using PUCCH), or Semi-persistent (using PUCCH and DCI-activated PUSCH). The associated CSI-RS resources can also be configured for transmission as AP / P / SP. [Table 1] below shows how CSI reporting is triggered for each CSI-RS resource.
[0239]
[0240] As described in [Table 1], a CSI-RS configuration may include a set of CSI resources set to one of P / SP / AP for each corresponding resource setting (CSI-ResourceConfig), and CSI resources having the same characteristics may be set in the set. A CSI resource setting (CSI-ResourceConfig) may be mapped to a specific CSI reporting configuration, and a transmission method of a CSI report may be set to one of P / SP / AP transmission. For a P CSI-RS resource, both P / SP / AP CSI reporting may be set, for an SP CSI resource, P / SP CSI reporting may be applied, and for an A CSI resource, only A CSI reporting may be applied.
[0241] In one embodiment, for P CSI reporting, reporting may be performed according to the period and offset values set in the corresponding CSI-ReportConfig of the RRC message. The above-described operation may be performed without a separate triggering signal.
[0242] According to one embodiment, SP CSI reporting may be divided into two types depending on the triggering method and the physical channel on which CSI reporting is performed. The first may be a method in which SP CSI reporting is triggered by the SP CSI reporting MAC CE, and SP CSI reporting is performed according to the CSI reporting settings indicated by the MAC CE. This may allow CSI to be reported semi-periodically through PUCCH, and this may be performed until deactivation is indicated through the SP CSI reporting MAC CE. The period and offset corresponding to SP CSI reporting may follow the values set in the CSI-ReportConfig RRC configuration. The second may be a method in which SP CSI reporting is activated through DCI. In this case, a list of report slots, periods, and offsets for CSI reporting may be set in the CSI-ReportConfig configuration through RRC, and whether to use a specific offset and period setting may be indicated in the DCI indicated by the csi-RNTI, and PUSCH CSI reporting may be triggered. A terminal receiving DCI can determine whether to activate or deactivate SP CSI reporting via PUSCH based on the instructions (activation / deactivation) included in the DCI. The method for determining the two SP CSI reports described above can be determined by the base station based on the channel status and the reporting method to be transmitted (e.g., Quantity). In the case of AP reporting, reportSlotOffsetList can be provided through the RRC configuration (CSI-ReportConfig), and a triggering state that maps the A CSI reporting configuration described above to CSI-AperiodicTriggerState can be set. The A CSI report can be triggered by the terminal receiving the CSI request field of the DCI.The CSI request field of the above-described DCI can be set to a maximum of 6 bits, and if the A CSI report setting set by RRC is greater than 2^(CSI request field)-1 of the DCI (for example, up to 63), an operation of reducing candidate triggering states through MAC CE may also be included. The triggering detailed operation for the A CSI report is described in detail below.
[0243] FIG. 13 illustrates a triggering state setting for CSI resource reporting in a wireless communication system according to one embodiment of the present disclosure.
[0244] In NR, a separate configuration for A CSI reporting is introduced, separate from the CSI reporting configuration provided by the RRC configuration by default. This is a method in which a list of triggering states for A CSI reporting is configured, and one or more corresponding A CSI reports are indicated via DCI. In one embodiment, a list of triggering states may be provided in aperiodicReportTrigger first via the RRC configuration. Each triggering state may be associated with one or more CSI-ReportConfigs, and each CSI-ReportConfig may be associated with one or more P / SP / AP CSI resource settings. If multiple A CSI resource sets are associated with a resource setting, and a subset of the A CSI resource sets is related to a triggering state, only the corresponding configuration may be indicated as a bitmap for this purpose.
[0245] According to one embodiment, in the triggering state (1305), the trigger state level may be set to a high level via RRC. The triggering state may be associated with up to 16 CSI-ReportConfig (Setting) (1310, 1315). The CSI-ReportConfig level may be associated with up to three CSI resource settings (1320, 1325, 1330), which may correspond to NZP CSI channels, ZP CSI interference, and NZP CSI interference, respectively. The CSI resource setting (1320, 1325, 1330) levels may indicate, in bitmap form, the CSI resource sets included in the corresponding resource settings. Additionally, the CSI resource set may indicate the CSI resources (1335, 1345, 1355) included in the resource set, and may provide a TCI-RS (transmission configuration indication reference signal) State ID that is quasi-co-located with the CSI resource. In addition, the CSI resource set may also provide an offset (1340, 1350, 1360) for the aperiodicReportTrigger. The offset may mean the offset at which the actual CSI resource set is transmitted from the DCI triggering.
[0246] For example, when an aperiodic triggering state is activated via DCI, reporting may be performed for the associated CSI resource set. In one embodiment, the reporting may be performed once.
[0247] FIG. 14 illustrates an L1 / L2 signaling method for supporting continuous L1 / L2-based handover (L1 / L2 triggered mobility, LTM) operations, according to one embodiment of the present disclosure. Specifically, FIG. 14 illustrates an example of a method for controlling measurement and reporting of L1 measurement resources for supporting continuous L1 / L2-based handover (LTM) operations through L1 / L2 signaling.
[0248] Referring to FIG. 14, among the L1 measurement and reporting methods described above in FIGS. 11, 12, and 13, operations requiring control by L1 (e.g., DCI) and L2 signaling (e.g., MAC CE) and specific methods for the corresponding signaling are specifically described. According to various embodiments of the present disclosure, the continuous LTM-related L1 measurement resource and reporting method may be applied to the first L1 measurement resource setting method / second L1 measurement resource setting method and the first L1 measurement report setting method / second L1 measurement report setting method described above.
[0249] For example, various embodiments of the present disclosure may be applied to L1 resource measurement and reporting in continuous LTM, such as the L1 measurement resource CSI resource reporting method described in FIG. 12 (e.g., CSI reporting triggering / activation for CSI-RS configuration in [Table 1]), and only the configuration method thereof may be different. In the case where the L1 measurement resources and reporting method in [Table 1] described above are applied as they are, the following method may be applied, particularly based on the L1 measurement reporting method.
[0250] 1. Set up and trigger periodic L1 measurement reporting (periodic CSI reporting) using RRC settings.
[0251] a. The terminal can perform the corresponding L1 measurement and periodic reporting immediately by applying the RRC settings.
[0252] 2. Set up semi-periodic (e.g., quasi-static) L1 measurement reporting (semi-persistent CSI reporting) via PUCCH set to RRC, and instruct MAC CE to enable / disable SP CSI reporting.
[0253] a. The terminal can perform SP CSI reporting as directed by the MAC CE from the time Xms has passed since the MAC CE was received.
[0254] b. The terminal may perform reporting periodically until deactivation is instructed by the MAC CE.
[0255] c. Detailed settings for SP CSI reporting (e.g., time frequency resources and period information) can be provided through RRC.
[0256] d. A new MAC CE structure (1410, 1420, 1430) may be introduced.
[0257] 3. Setting up semi-persistent CSI reporting via PUSCH set to RRC and triggering activation / deactivation of SP CSI reporting via DCI.
[0258] a. The terminal can perform SP CSI reporting as directed by the MAC CE from the time Xms has passed since the MAC CE was received.
[0259] b. The terminal may perform periodic reporting until the DCI indicates deactivation. For example, a new DCI field may be introduced to trigger L1 measurement reporting for continuous LTM, or an existing DCI field may be reused.
[0260] c. Detailed settings for SP CSI reporting (e.g., time frequency resources and period information) can be provided through RRC.
[0261] 4. Regarding the aperiodic L1 measurement report (aperiodic CSI reporting) set by RRC and the triggering state associated with it, the MAC CE indicates the activation / deactivation of AP CSI reporting, and the actual triggering is performed through DCI.
[0262] a. MAC CE may be required to enable / disable the Triggering state.
[0263] b. A new MAC CE structure (1440, 1450, 1460) may be required.
[0264] c. DCI can actually activate one of the triggering states enabled via MAC CE. For example, a new DCI field can be introduced to trigger L1 measurement reporting for continuous LTM, or an existing DCI field can be reused.
[0265] d. After receiving DCI, the terminal can perform one L1 measurement report according to the settings.
[0266] The two new MAC CEs described above are described in detail below.
[0267] 1) MAC CE of the semi-persistent CSI reporting on PUCCH for LTM that enables semi-periodic L1 measurement reporting to support continuous LTM.
[0268] a. 1-1 MAC CE design method (1410)
[0269] - Introduction of MAC CE using new LCID or eLCID
[0270] - Ref field: An indicator indicating whether a reporting setting that enables L1 measurement reporting in the MAC CE exists in the Reference cell configuration. For example, if this field is 1, it may indicate that an L1 measurement reporting setting exists in the Reference cell configuration, and if it is 0, it may indicate that an L1 measurement reporting setting exists in the serving cell indicated below, not in the Reference cell.
[0271] - Serving Cell Index: This can be interpreted differently depending on whether the Ref field indicates it. For example, if the Ref field is 1, it can mean the serving cell index within the Reference cell configuration, and if the Meaning / Ref field is 0, it can mean the current serving cell index.
[0272] - BWP Index: BWP for which L1 measurement reporting is actually set in the indicated serving cell.
[0273] - S i Field: An indicator indicating the enable / disable status of the semi-periodic L1 measurement report setting. For example, if the field is 1, it may indicate enable, and if it is 0, it may indicate disable. Also, according to one embodiment, referring to FIG. 14, S i Although the field size is shown as 4, it is not limited to this and the number (size) of fields can be changed depending on the number that can be set.
[0274] b. MAC CE Design Method 1-2 (1420)
[0275] - Introduction of MAC CE using new LCID (logical channel ID) or eLCID (enhanced LCID)
[0276] - SC field: An indicator indicating whether a reporting configuration that enables L1 measurement reporting in the MAC CE exists within the current serving cell. For example, if this field is 1, the candidate cell ID can be replaced with the current serving cell index, and if it is 0, it can indicate that the L1 measurement reporting configuration exists within the indicated candidate cell ID, not the current serving cell.
[0277] - Candidate cell index (candidate cell ID): This can be interpreted differently depending on whether the SC field indicates it. For example, if the SC field is 1, it can mean the current serving cell index, and if the SC field is 0, it can be used as an index indicating a candidate cell (can be used as a logical candidate cell ID or PCI, etc.).
[0278] - BWP Index: BWP for which L1 measurement reporting is actually set in the indicated serving cell.
[0279] - S i Field: An indicator indicating the enable / disable status of the semi-periodic L1 measurement report setting. For example, if the field is 1, it may indicate enable, and if it is 0, it may indicate disable. Also, according to one embodiment, referring to FIG. 14, S i Although the field size is shown as 4, it is not limited to this and the number (size) of fields can be changed depending on the number that can be set.
[0280] c. 1-3 MAC CE design method
[0281] - Introduction of MAC CE using new LCID or eLCID
[0282] - SC field: An indicator indicating whether a reporting configuration that enables L1 measurement reporting in the MAC CE exists within the current serving cell. For example, if this field is 1, the candidate cell ID can be replaced with the current serving cell index, and if it is 0, it can indicate that the L1 measurement reporting configuration exists within the indicated candidate cell ID, not the current serving cell.
[0283] - Ref field: An indicator indicating whether a reporting setting that enables L1 measurement reporting in MAC CE exists in the Reference cell configuration. If this field is 1, it may indicate that an L1 measurement reporting setting exists in the Reference cell configuration, and if it is 0, it may indicate that an L1 measurement reporting setting exists in the indicated serving cell, not the Reference cell.
[0284] - Candidate cell index (candidate cell ID): This can be interpreted differently depending on whether the SC field and Ref field indicate it. For example, if the SC field is 1, it can mean the current serving cell index. If the SC field is 0 and the Ref field is 1, the candidate cell index can be ignored (i.e., has no meaning). For example, the Reference cell can be used as a cell for which L1 measurement reporting is set. If the SC field is 0 and the Ref field is 0, it can be used as an index indicating a candidate cell (for example, it can be used as a logical candidate cell ID or PCI, etc.).
[0285] - Serving cell index set in candidate cell: Serving cell index for indicating multiple SCells within the set candidate cell or reference cell.
[0286] - BWP Index: BWP for which L1 measurement reporting is actually set in the indicated serving cell.
[0287] - S i Field: An indicator indicating the enable / disable status of the semi-periodic L1 measurement report setting. For example, if the field is 1, it may indicate enable, and if it is 0, it may indicate disable. Also, according to one embodiment, referring to FIG. 14, S i Although the field size is shown as 4, it is not limited to this and the number (size) of fields can be changed depending on the number that can be set.
[0288] 2) MAC CE of the triggering state activation / deactivation for aperiodic CSI reporting for LTM to support continuous LTM
[0289] a. 2-1 MAC CE Design Method (1440)
[0290] - Introduction of MAC CE using new LCID or eLCID
[0291] - Ref field: An indicator indicating whether a triggering state setting that activates L1 measurement reporting in the MAC CE exists within the Reference cell configuration. For example, if this field is 1, it may indicate that a triggering state setting that activates L1 measurement reporting exists within the Reference cell configuration, and if it is 0, it may indicate that a triggering state setting that activates L1 measurement reporting exists in the indicated serving cell, not the Reference cell.
[0292] - Serving Cell Index: This can be interpreted differently depending on whether the Ref field indicates it. For example, if the Ref field is 1, it can mean the serving cell index within the Reference cell configuration, and if the Ref field is 0, it can mean the current serving cell index.
[0293] - BWP Index: BWP for which L1 measurement reporting is actually set in the indicated serving cell.
[0294] - T i Field: A field indicating the status of the triggering state setting that activates the Aperiodic L1 measurement report. If the field is 1, it can indicate activation, and if it is 0, it can indicate deactivation. In addition, according to one embodiment, T can be set according to the settable number. i The size of the field can be changed.
[0295] b. 2-2 MAC CE design method (1450)
[0296] - Introduction of MAC CE using new LCID or eLCID
[0297] - SC field: An indicator indicating whether a triggering state setting that enables L1 measurement reporting in the MAC CE exists within the current serving cell. If this field is 1, the candidate cell ID can be replaced with the current serving cell index, and if it is 0, it can indicate that the L1 measurement reporting setting exists within the indicated candidate cell ID, not the current serving cell.
[0298] - Candidate cell index (candidate cell ID): This can be interpreted in different ways depending on whether the SC field indicates it. For example, if the SC field is 1, it can mean the current serving cell index, and if the SC field is 0, it can be used as an index indicating a candidate cell (for example, it can be used as a logical candidate cell ID or PCI, etc.).
[0299] - BWP Index: BWP for which L1 measurement reporting is actually set in the indicated serving cell.
[0300] - T i Field: A field indicating the status of the triggering state setting that activates the Aperiodic L1 measurement report. For example, if the field is 1, it may indicate activation, and if it is 0, it may indicate deactivation. Also, according to one embodiment, T may be set according to the configurable number. i The size of the field can be changed.
[0301] c. 2-3 MAC CE design method (1460)
[0302] - Introduction of MAC CE using new LCID or eLCID
[0303] - SC field: An indicator indicating whether a triggering state setting that enables L1 measurement reporting in the MAC CE exists within the current serving cell. For example, if this field is 1, the candidate cell ID can be replaced with the current serving cell index, and if it is 0, it can indicate that the L1 measurement reporting setting exists within the indicated candidate cell ID, not the current serving cell.
[0304] - Ref field: An indicator indicating whether a triggering state setting that activates L1 measurement reporting in the MAC CE exists in the Reference cell configuration. For example, if this field is 1, it may indicate that L1 measurement reporting settings exist in the Reference cell configuration, and if it is 0, it may indicate that L1 measurement reporting settings exist in the indicated serving cell, not the Reference cell.
[0305] - Candidate cell index (candidate cell ID): It can be interpreted differently depending on whether the SC field and Ref field indicate it: If the SC field is 1, it can mean the current serving cell index. If the SC field is 0 and the Ref field is 1, the candidate cell index can be ignored (i.e., has no meaning). For example, a cell with a reference cell set can be used. If the SC field is 0 and the Ref field is 0, it can be used as an index indicating a candidate cell (for example, it can be used as a logical candidate cell ID or PCI, etc.)
[0306] - BWP Index: BWP for which L1 measurement reporting is actually set in the indicated serving cell.
[0307] - T i Field: A field indicating the status of the triggering state setting that activates the Aperiodic L1 measurement report. If the field is 1, it can indicate activation, and if it is 0, it can indicate deactivation. In addition, according to one embodiment, T can be set according to the settable number. i The size of the field can be changed.
[0308] The following embodiments describe the overall operation of applying the specific methods proposed in the present invention described above, with respect to a method for configuring SSB-based L1 measurement resources for neighboring cells and a method for reporting L1 measurement resources. In particular, for continuous LTM operation according to various embodiments of the present disclosure described above, the present invention may include an operation for triggering L1 measurement reporting through L1 / L2 signaling.
[0309] FIG. 15 illustrates a method for transmitting L1 measurement reports for continuous LTM when DRX is set and applied, according to one embodiment of the present disclosure.
[0310] According to one embodiment, FIG. 15 assumes that a terminal in an RRC connected state has connected DRX (hereinafter referred to as C-DRX) configured. The operation of C-DRX is described in detail in FIG. 10, and based thereon, a method for transmitting an L1 measurement report according to embodiments of the present disclosure is defined.
[0311] According to one embodiment, a terminal for which C-DRX is set by default can perform PDCCH monitoring during the active time. For example, by monitoring the PDCCH during the set active time, if the terminal receives scheduling for DL transmission or scheduling for UL transmission, the terminal can start a DRX inactivity timer. The terminal can maintain an active state during the DRX inactivity timer. That is, the terminal can continue to perform PDCCH monitoring. In addition, the terminal can also start a HARQ RTT timer. The HARQ RTT timer can be applied to prevent the terminal from unnecessarily monitoring the PDCCH during the HARQ RTT time, and the terminal does not need to perform PDCCH monitoring during the timer operation time. However, while the DRX inactivity timer and the HARQ RTT timer operate simultaneously, the terminal can continue to monitor the PDCCH based on the DRX inactivity timer.
[0312] According to one embodiment, when the HARQ RTT timer expires, the DRX retransmission timer may be started. While the DRX retransmission timer is operating, the UE may perform PDCCH monitoring. Typically, during the DRX retransmission timer operation time, the UE may receive scheduling information for HARQ retransmission. Upon receiving scheduling information, the UE may immediately stop the DRX retransmission timer and start the HARQ RTT timer again. The UE may continuously perform the above-described series of operations until the packet is successfully received.
[0313] In one embodiment, since the terminal does not perform PDCCH monitoring outside of the DRX active time, UL / DL data transmission cannot be performed. Similarly, how to perform CSI reporting and SRS (sounding reference signal) transmission set to be transmitted outside of the active time is defined below. As described above, CSI reporting methods can be broadly categorized into the following four types.
[0314] 1. Periodic CSI Reporting (P CSI Reporting): Reporting at a set period and offset through the configured PUCCH resources.
[0315] 2. Quasi-periodic CSI reporting via PUCCH (SP CSI reporting): Indicate activation / deactivation of SP CSI reporting via MAC CE.
[0316] 3. Quasi-periodic CSI reporting via PUSCH (SP CSI reporting): Indicate activation / deactivation of SP CSI reporting via DCI.
[0317] 4. Non-periodic CSI reporting (AP CSI reporting): Instructs DCI to enable / disable AP CSI reporting.
[0318] In step (1510), the terminal receives the setting for P CSI reporting through RRC setting, and if measurement is performed for the corresponding CSI-RS (1520), if the reporting condition (e.g., periodic reporting or event triggering) is satisfied, the terminal can perform CSI reporting within the active time (1530). However, the terminal may not perform CSI reporting for CSI-RS transmitted after the active time even if the reporting condition is satisfied. Similarly, in the case of SRS, if periodic SRS transmission is set with an RRC message, the terminal can transmit the SRS within the set resource only for the active time (1530). The CSI-RS received by the terminal may be a resource that is transmitted periodically.
[0319] In step (1540), the terminal receives the setting for SP CSI reporting through RRC setting, and if the measurement for the corresponding CSI-RS is performed, if the reporting condition (e.g., periodic reporting or event triggering) is satisfied, the terminal can perform CSI reporting within the active time, or can perform CSI reporting even if it is not the active time. Since the base station can activate / deactivate the CSI reporting section through a MAC CE instruction (1550), it can be understood that if the SP CSI reporting is activated during the active time, the terminal must perform the corresponding CSI reporting until a deactivation signal is received (1560). The following methods are possible for the SP CSI reporting method.
[0320] 1. No SP CSI reporting is performed after DRX Active time.
[0321] 2. After the DRX Active time, among the SP CSI reports activated within the active time, SP CSI reports transmitted on PUCCH are not performed, but SP SCI reports transmitted on PUSCH are performed.
[0322] 3. After the DRX Active time, among the SP CSI reports activated within the active time, SP CSI reports transmitted on PUSCH are not performed, but SP SCI reports transmitted on PUCCH are performed.
[0323] 4. Perform all SP CSI reports activated within the active time even after the DRX Active time.
[0324] 5. SP CSI reporting activated within the DRX Active time stops CSI reporting when the active time ends and restarts SP CSI reporting again according to the settings when the next active time starts (for example, SP CSI reporting stops when a MAC CE indicating inactivity for the corresponding SP CSI reporting is received).
[0325] In step (1570), if the terminal receives the setting for AP CSI reporting through RRC setting and performs measurement for the corresponding AP CSI-RS, and if the reporting condition (e.g., periodic reporting or event triggering) is satisfied (DCI triggering) (1580) but resources for AP CSI reporting exist outside of the active time, the terminal may not perform AP CSI reporting when it is not the active time, or may perform AP CSI reporting (1590) even when it is not the active time. For example, the following method is possible.
[0326] 1. AP CSI reporting is not performed after DRX Active time.
[0327] 2. AP CSI reporting activated within the DRX Active time performs CSI reporting regardless of the active time, even after the active time ends.
[0328] FIG. 16 illustrates a signal flow for a semi-persistent L1 measurement report to support continuous L1 / L2 based handover (LTM) operation, according to one embodiment of the present disclosure. In one embodiment, FIG. 16 may include at least one step disclosed in the signal flow of FIG. 6 , but this is merely an example, and each step is not a required component, and various embodiments may consist of at least one of all steps, some steps, or a combination of some steps.
[0329] According to one embodiment, a terminal (1601) in an RRC connection state can perform data transmission and reception with a source cell 1 (1602). In step (1610), the terminal can transmit layer 3 measurement values for a serving cell and neighboring cells to the source cell 1 (1602) according to the configured layer 3 measurement and reporting. At this time, the actual measurement values can be transmitted to the CU (1603) of the base station. This is because the base station CU (1603) is responsible for RRC message processing and determines mobility.
[0330] In step (1615), the base station CU (1603) may generate a message (e.g., L1 / L2 config request message, HandoverPreparationInformation message, or a new message) requesting configuration information for L1 / L2-based handover to LTM candidate neighboring cells (1604, 1605) based on the measurement value report received from the terminal, and transmit the message through the F1 interface. Referring to FIG. 16, the candidate cell is illustrated in association with the DU, but is not limited thereto, and the candidate cell and the DU may be mapped 1:1, or multiple candidate cells may be included in one DU. According to one embodiment, the message requesting configuration information for L1 / L2-based handover may include an existing handover request message, a UE context request message, a UE context modification request message, etc., or may include a new F1 or Xn message. A message requesting configuration information for L1 / L2-based handover may request neighboring cells to be determined as candidate cells for L1 / L2-based handover, and at the same time, request RRC configuration information to be applied when L1 / L2-based handover is performed to the corresponding cell. In addition, the above-described message may include information requesting L1 measurement resource and reporting configuration for LTM candidate cells according to various embodiments of the present disclosure. The request for the L1 measurement resource and reporting configuration may be performed for each candidate cell. Referring to FIG. 16, step (1615) is illustrated as a single procedure, but is not limited thereto, and the step may be performed as inter-node coordination through multiple procedures.
[0331] In one embodiment, although not shown in the drawing, the inter-node coordination procedure that can be performed for setting up L1 measurement resources and reporting at that stage is as follows.
[0332] Step 1: Receive L1 measurement resource settings from LTM candidate cells.
[0333] Step 2: The source base station CU (1603) transmits the L1 measurement resource configuration for continuous LTM support to each candidate cell by configuring the L1 measurement resource for each collected candidate cell (e.g., the first L1 measurement resource configuration method or the second L1 measurement resource configuration method).
[0334] Step 3: The source base station CU (1603) requests and receives L1 measurement report setup from LTM candidate cells.
[0335] Step 4: Transmit LTM-related settings to the terminal (e.g., including L1 resource reporting settings set according to the first L1 measurement resource reporting setting method).
[0336] In one embodiment, the source base station CU (1603) may transmit the configuration information of the source cell and separate reference cell configuration information to the LTM candidate neighboring cells (1604, 1605). In one embodiment, the message transmitted by the source base station CU (1603) may include L1 measurement resource configuration for continuous LTM within the reference cell configuration information.
[0337] According to one embodiment, the reference cell configuration information that the source base station CU (1603) transmits to each of the candidate cells (1604, 1605) may include configuration information that can be commonly applied to multiple target candidate cells (common configuration) to reduce signaling overhead that may occur when the target candidate cells provide configuration information for LTM. The common configuration information may include measurement configuration, bearer configuration, or, if the cells belong to the same CellGroup, configurations that are set at the CellGroup level (e.g., MAC-CellGroupConfig, RLC bearer configuration, SCell configuration, etc.). If the source base station CU (1603) knows or has a procedure for knowing the configuration information for each of the candidate cells (1604, 1605), the reference cell configuration may be determined through a separate procedure for obtaining the reference cell configuration information. The purpose of the source base station CU (1603) transmitting the reference cell configuration to each candidate cell (1604, 1605) is to enable each candidate cell to transmit only the configuration information added based on the reference cell configuration to the source base station CU (1603) so that a delta configuration (e.g., a method of configuring a complete configuration by applying a configuration added on top of the reference cell configuration or a method of configuring a complete configuration by overwriting the configuration in the target cell based on the reference cell configuration) can be applied. This can be transmitted as is to the terminal thereafter, and thus can have the effect of reducing the signaling of the RRC message transmitted to the terminal.
[0338] In one embodiment, further, when the source base station CU (1603) transmits the reference cell configuration to each of the candidate cells (1604, 1605), the candidate cell configuration may be provided as a complete RRC configuration, if it can be omitted. For example, the RRC configuration information (CellGroupConfig 1, ..., CellGroupConfig N) applied when an L1 / L2-based handover is performed may be transmitted at either a cell group level or an RRC message level. As described above, the message (1615) requesting configuration information for an L1 / L2-based handover may be transmitted including both information and configuration for the reference cell, and may include at least one of an indicator instructing the candidate peripheral cells (1604, 1605) to transmit the reference cell configuration information or the configuration information for the L1 / L2-based handover by applying a delta configuration. The above-described indicator may be requested for each cell or may be requested commonly for all cells.
[0339] Candidate neighboring cells (1604, 1605) that have received a message requesting configuration information for L1 / L2-based handover in step (1620) can generate configuration information of each candidate neighboring cell when L1 / L2-based handover is applied based on the configuration information of the transmitted reference cell, based on or without applying the delta configuration.
[0340] In step (1625), each candidate surrounding cell (1604, 1605) can store the configuration information for the generated L1 / L2-based handover in an L1 / L2-based handover configuration information response message (L1 / L2 config response message) and transmit it to the base station CU (1603).
[0341] In step (1630), the base station CU (1603) may transmit an RRC message generated based on the configuration information received from each candidate cell to the source cell (1602), and the source cell (1602) may transmit the received message to the terminal. The RRC message may include configuration information (Pre-Config1, ..., Pre-ConfigN) for surrounding candidate cells to which L1 / L2-based handover (LTM) is applied. The Pre-Config included in the RRC message may include information on the CellGroupConfig configuration received from the LTM candidate cells in step (1625), the bearer configuration for the LTM candidate cells generated by the base station, and the Layer 3 (Layer 3, L3) measurement configuration.
[0342] In step (1635), the terminal that receives the RRC message can decode and process the RRC message. The processing procedure performed by the terminal may include ASN.1 decoding and validity determination of the received message, and a method for storing or managing the configuration contents. In addition, the terminal may store the LTM configuration information for each candidate cell decoded in step (1635) as complete configuration information in a buffer (e.g., memory) of the terminal, and simultaneously store and manage the received reference cell configuration information in the buffer (e.g., memory) of the terminal. According to one embodiment, the reference cell configuration information may be omitted from the RRC message (or the configuration information for each LTM candidate cell) of step (1630). In this case, the terminal may recognize that there is no reference cell configuration information, and may determine and store the configuration information for the received LTM target candidate cells as complete configuration information. In this case, the reference cell configuration information may not be stored separately (e.g., may operate as empty). For example, the delta configuration may not be applied. Additionally, L1 measurement resource and reporting configuration information for continuous LTM can be transmitted via the RRC message. Detailed configuration information is described in the above description of the present invention.
[0343] At step (1638), the base station may transmit a MAC CE that activates a semi-persistent L1 report to the terminal.
[0344] At step (1640), the terminal receives the MAC CE and can perform L1 (layer 1) measurement and reporting for each candidate surrounding cell, and can perform semi-persistent L1 measurement reporting according to the received settings.
[0345] At step (1643), the terminal may terminate the semi-persistent L1 measurement report if it receives a MAC CE that disables the semi-persistent L1 report.
[0346] At the same time, in step (1645), the terminal can also perform L3 measurement and reporting according to the received settings.
[0347] In step (1650), the source cell that received the L1 measurement report can make a handover decision based on the corresponding measurement value and can instruct the terminal to perform L1 / L2 handover. In step (1650), MAC CE and DCI including a handover indicator can be used for L1 / L2 signaling. The L1 measurement value transfer and handover decision for determining L1 / L2 handover in steps (1640) and (1650) can be performed by the source cell (DU) or the source base station CU. If the base station CU makes all decisions, the source cell can transfer the L1 measurement value received from the terminal to the base station CU and transfer L1 / L2 signaling to the terminal according to the handover decision instruction of the base station CU. However, when the source cell makes the final decision, the source cell may not transmit the received L1 measurement values to the base station, but may determine the handover on its own based on measurement value criteria (e.g., threshold values or measurement value ranges) for making handover decisions for each candidate neighboring cell received from the previous base station, and may transmit L1 / L2 signaling to the terminal accordingly.
[0348] When an L1 / L2 handover instruction is transmitted to the terminal at step (1655), the terminal may initiate a handover procedure and start a timer for L1 / L2 handover. The timer may be a newly set timer for LTM, or an existing T304 timer may be reused.
[0349] In step (1660), the terminal may apply settings for the target cell to which the L1 / L2 handover is applied. For example, the terminal may replace the current settings with the complete configuration information of the designated LTM target cell previously stored in the terminal. This may be one of the LTM candidate neighboring cell settings previously received in step (1630) and may be a setting stored in the terminal.
[0350] In step (1665), the terminal may perform random access if random access is required for the target cell according to the applied settings, or the random access procedure may be omitted if random access is not indicated or required (e.g., if uplink synchronization has already been performed or aligned).
[0351] At step (1670), the terminal may perform a handover completion procedure with the target cell. This completion procedure may be a handover completion procedure for LTM. This procedure may vary depending on the method of indicating the handover completion. In addition, this procedure may be a process of transmitting an RRCReconfigurationComplete message when the target cell configuration is received at the RRC message level. However, if the cell-level or cell group-level configuration is received, this may be replaced with a new handover completion indication message (e.g., a new RRC message or MAC CE).
[0352] Additionally, since this scenario considers application to intra-CU, the target cell (DU) (1604) that receives the handover completion message at step (1675) can forward the received message to the base station CU (1603). At this time, the handover completion message received via the F1 interface can be forwarded as is, or the target cell (1604) can reprocess the message based on the received information and forward it.
[0353] At step (1680), the base station CU (1603) may transmit information about the completion of the handover to the source cell (1602) and instruct it to release the terminal context.
[0354] As illustrated in step (1685), various embodiments of the present invention may support subsequent LTM operations. The subsequent LTM operations may include the UE continuously performing the LTM procedure, as long as the LTM configuration information (e.g., configuration for target candidate cells and reference cell configuration information, etc.) received in step (1630) is stored in the UE as is, and the UE does not change / release / add the corresponding LTM configuration information through a separate RRC configuration. If it is necessary to update the reference cell configuration information, new RRC configuration information may be transmitted to the UE, allowing the subsequent LTM operation to be performed. For example, all or part of the procedures described in the above-described drawing may be triggered and performed again.
[0355] According to one embodiment, if the terminal is provided with reference cell configuration information in step (1630), the terminal may store it in the terminal buffer and, if there is no update for a separate configuration, may use the configuration as reference cell configuration information even after performing LTM (step (1650)) (for example, the terminal may apply the reference cell configuration and LTM candidate configuration values stored in successive LTMs). In addition, if the terminal is not provided with reference cell configuration information in step (1630) in an RRC connected state, the terminal may empty and store the reference cell configuration or store configuration information for the corresponding source cell (PCell) from which the LTM configuration information was received as reference cell configuration information, depending on some of the terminal operation options described above.
[0356] FIG. 17 illustrates an operation of applying aperiodic L1 measurement reporting to support continuous L1 / L2-based handover (LTM) operations, according to one embodiment of the present disclosure. According to one embodiment, FIG. 17 may include at least one step disclosed in the signal flow of FIG. 6 or FIG. 16 , but this is merely an example, and each step is not a required component, and various embodiments may consist of at least one of all steps, some steps, or a combination of some steps.
[0357] According to one embodiment, a terminal (1701) in an RRC connection state can perform data transmission and reception with a source cell 1 (1702). In step (1710), the terminal can transmit layer 3 measurement values for a serving cell and neighboring cells to the source cell 1 (1702) according to the configured layer 3 measurement and reporting. At this time, the actual measurement values can be transmitted to the CU (1703) of the base station. This is because the base station CU (1703) is responsible for RRC message processing and determines mobility.
[0358] In step (1715), the base station CU (1703) may generate a message (e.g., L1 / L2 config request message, HandoverPreparationInformation message, or a new message) requesting configuration information for L1 / L2-based handover to LTM candidate neighboring cells (1704, 1705) based on the measurement value report received from the terminal, and transmit the message through the F1 interface. Referring to FIG. 17, the candidate cell is illustrated in association with the DU, but is not limited thereto, and the candidate cell and the DU may be mapped 1:1, or multiple candidate cells may be included in one DU. According to one embodiment, the message requesting configuration information for L1 / L2-based handover may include an existing handover request message, a UE context request message, a UE context modification request message, etc., or may include a new F1 or Xn message. A message requesting configuration information for L1 / L2-based handover may request neighboring cells to be determined as candidate cells for L1 / L2-based handover, and at the same time, request RRC configuration information to be applied when L1 / L2-based handover is performed to the corresponding cell. In addition, the above-described message may include information requesting L1 measurement resource and reporting configuration for LTM candidate cells according to various embodiments of the present disclosure. The request for the L1 measurement resource and reporting configuration may be performed for each candidate cell. Referring to FIG. 17, step (1715) is illustrated as a single procedure, but is not limited thereto, and the step may be performed as inter-node coordination through multiple procedures.
[0359] In one embodiment, although not shown in the drawing, the inter-node coordination procedure that can be performed for setting up L1 measurement resources and reporting at that stage is as follows.
[0360] Step 1: Receive L1 measurement resource settings from LTM candidate cells.
[0361] Step 2: The source base station CU (1703) transmits the L1 measurement resource configuration for continuous LTM support to each candidate cell by configuring the L1 measurement resource for each collected candidate cell (e.g., the first L1 measurement resource configuration method or the second L1 measurement resource configuration method).
[0362] Step 3: The source base station CU (1703) requests and receives L1 measurement report setup from LTM candidate cells.
[0363] Step 4: Transmit LTM-related settings to the terminal (e.g., including L1 resource reporting settings set according to the first L1 measurement resource reporting setting method).
[0364] In one embodiment, the source base station CU (1703) may transmit the configuration information of the source cell and separate reference cell configuration information to the LTM candidate neighboring cells (1704, 1705). In one embodiment, the message transmitted by the source base station CU (1703) may include L1 measurement resource configuration for continuous LTM within the reference cell configuration information.
[0365] According to one embodiment, the reference cell configuration information that the source base station CU (1703) transmits to each of the candidate cells (1704, 1705) may include configuration information that can be commonly applied to multiple target candidate cells to reduce signaling overhead that may occur when the target candidate cells provide configuration information for LTM. The common configuration information may include measurement configuration, bearer configuration, or, if the cells belong to the same CellGroup, configurations that are set at the CellGroup level (e.g., MAC-CellGroupConfig, RLC bearer configuration, SCell configuration, etc.). If the source base station CU (1703) knows or has a procedure for knowing the configuration information for each of the candidate cells (1704, 1705), the reference cell configuration may be determined through a separate procedure for obtaining the reference cell configuration information. The purpose of the source base station CU (1703) transmitting the reference cell configuration to each candidate cell (1704, 1705) is to enable each candidate cell to transmit only the configuration information added based on the reference cell configuration to the source base station CU (1703) so that a delta configuration (e.g., a method of configuring a complete configuration by applying a configuration added on top of the reference cell configuration or a method of configuring a complete configuration by overwriting the configuration in the target cell based on the reference cell configuration) can be applied. This can be transmitted as is to the terminal thereafter, and thus can have the effect of reducing the signaling of the RRC message transmitted to the terminal.
[0366] In one embodiment, furthermore, when the source base station CU (1703) transmits the reference cell configuration to each of the candidate cells (1704, 1705), if it can be omitted, the candidate cell configuration may be provided as a complete RRC configuration. For example, the RRC configuration information (CellGroupConfig 1, ..., CellGroupConfig N) applied when an L1 / L2-based handover is performed may be transmitted at either a cell group level or an RRC message level. As described above, the message (1715) requesting configuration information for an L1 / L2-based handover may be transmitted including both information and configuration for the reference cell, and may include at least one of an indicator instructing the candidate peripheral cells (1704, 1705) to transmit the reference cell configuration information or the configuration information for the L1 / L2-based handover by applying a delta configuration. The above-described indicator may be requested for each cell or may be requested commonly for all cells.
[0367] Candidate neighboring cells (1704, 1705) that have received a message requesting configuration information for L1 / L2-based handover in step (1720) can generate configuration information of each candidate neighboring cell when L1 / L2-based handover is applied based on the configuration information of the transmitted reference cell, based on or without applying the delta configuration.
[0368] In step (1725), each candidate surrounding cell (1704, 1705) can store the configuration information for the generated L1 / L2-based handover in an L1 / L2-based handover configuration information response message (L1 / L2 config response message) and transmit it to the base station CU (1703).
[0369] In step (1730), the base station CU (1703) may transmit an RRC message generated based on the configuration information received from each candidate cell to the source cell (1702), and the source cell (1702) may transmit the received message to the terminal. The RRC message may include configuration information (Pre-Config1, ..., Pre-ConfigN) for surrounding candidate cells to which L1 / L2-based handover (LTM) is applied. The Pre-Config included in the RRC message may include information on the CellGroupConfig configuration received from the LTM candidate cells in step (1725), the bearer configuration for the LTM candidate cells generated by the base station, and the Layer 3 (Layer 3, L3) measurement configuration.
[0370] In step (1735), the terminal that receives the RRC message can decode and process the RRC message. The processing procedure performed by the terminal may include ASN.1 decoding and validity determination of the received message, and a method for storing or managing the configuration contents. In addition, the terminal may store the LTM configuration information for each candidate cell decoded in step (1735) as complete configuration information in a buffer (e.g., memory) of the terminal, and simultaneously store and manage the received reference cell configuration information in the buffer (e.g., memory) of the terminal. According to one embodiment, the reference cell configuration information may be omitted from the RRC message (or the configuration information for each LTM candidate cell) of step (1730). In this case, the terminal may recognize that there is no reference cell configuration information, and may determine and store the configuration information for the received LTM target candidate cells as complete configuration information. In this case, the reference cell configuration information may not be stored separately (e.g., may operate as empty). For example, the delta configuration may not be applied. Additionally, L1 measurement resource and reporting configuration information for continuous LTM can be transmitted via the RRC message. Detailed configuration information is described in the above description of the present invention.
[0371] In step (1738), the base station may transmit a MAC CE that activates an aperiodic L1 report to the terminal and transmit a DCI that activates it.
[0372] At step (1740), the terminal receives MAC CE and DCI, and can perform L1 (layer 1) measurement and reporting for each candidate surrounding cell, and can perform aperiodic L1 measurement reporting according to the received settings.
[0373] At the same time, in step (1745), the terminal can also perform L3 measurement and reporting according to the received settings.
[0374] In step (1750), the source cell that has received the L1 measurement report can make a handover decision based on the measurement value and instruct the terminal to perform L1 / L2 handover. In step (1750), MAC CE and DCI including a handover indicator can be used for L1 / L2 signaling. The L1 measurement value transfer and handover decision for determining L1 / L2 handover in steps (1740) and (1750) can be performed by the source cell (DU) or the source base station CU. If the base station CU makes all decisions, the source cell can transfer the L1 measurement value received from the terminal to the base station CU and transfer L1 / L2 signaling to the terminal according to the handover decision instruction of the base station CU. However, when the source cell makes the final decision, the source cell may not transmit the received L1 measurement values to the base station, but may determine the handover on its own based on measurement value criteria (e.g., threshold values or measurement value ranges) for making handover decisions for each candidate neighboring cell received from the previous base station, and may transmit L1 / L2 signaling to the terminal accordingly.
[0375] When an L1 / L2 handover instruction is transmitted to the terminal at step (1755), the terminal may initiate a handover procedure and start a timer for L1 / L2 handover. The timer may be a newly set timer for LTM, or an existing T304 timer may be reused.
[0376] At step (1760), the terminal may apply settings for the target cell to which the L1 / L2 handover is applied. For example, the terminal may replace the current settings with the complete configuration information of the designated LTM target cell previously stored in the terminal. This may be one of the LTM candidate neighboring cell settings previously received at step (1730) and may be a setting stored in the terminal.
[0377] In step (1765), the terminal may perform random access if random access is required for the target cell according to the applied settings, and if random access is not indicated or required (e.g., if uplink synchronization has already been performed or aligned), the random access procedure may be omitted.
[0378] At step (1770), the terminal may perform a handover completion procedure with the target cell. This completion procedure may be a handover completion procedure for LTM. This procedure may vary depending on the method of indicating the handover completion. In addition, this procedure may be a process of transmitting an RRCReconfigurationComplete message when the target cell configuration is received at the RRC message level. However, if the cell-level or cell group-level configuration is received, this may be replaced with a new handover completion indication message (e.g., a new RRC message or MAC CE).
[0379] Additionally, since this scenario considers application to intra-CU, the target cell (DU) (1704) that receives the handover completion message at step (1775) can forward the received message to the base station CU (1703). At this time, the handover completion message received via the F1 interface can be forwarded as is, or the target cell (1704) can reprocess the message based on the received information and forward it.
[0380] At step (1780), the base station CU (1703) may transmit information about the completion of the handover to the source cell (1702) and instruct it to release the terminal context.
[0381] As illustrated in step (1785), various embodiments of the present invention may support subsequent LTM operations. The subsequent LTM operations may include the UE continuously performing the LTM procedure, as long as the LTM configuration information (e.g., configuration for target candidate cells and reference cell configuration information, etc.) received in step (1730) is stored in the UE as is, and the corresponding LTM configuration information is not changed / released / added through a separate RRC configuration. If it is necessary to update the reference cell configuration information, new RRC configuration information may be transmitted to the UE, allowing the subsequent LTM operation to be performed. For example, all or part of the procedures described in the above-described drawing may be triggered and performed again.
[0382] According to one embodiment, if the terminal is provided with reference cell configuration information in step (1730), the terminal may store it in the terminal buffer and, if there is no update for a separate configuration, may use the configuration as reference cell configuration information even after performing LTM (step (1750)) (for example, the terminal may apply the reference cell configuration and LTM candidate configuration values stored in successive LTMs). In addition, if the terminal is not provided with reference cell configuration information in step (1730) in an RRC connected state, the terminal may empty and store the reference cell configuration or store configuration information for the corresponding source cell (PCell) from which the LTM configuration information was received as reference cell configuration information, depending on some of the terminal operation options described above.
[0383] FIG. 18 illustrates another operational flow of a terminal for performing L1 / L2-based beam switching and handover according to one embodiment of the present disclosure. In particular, the terminal operation according to various embodiments of the present disclosure may be characterized by a method for performing L1 measurements and reports according to L1 measurement resource and reporting settings for continuous LTM operation.
[0384] In step (1805), the terminal in the connected state can receive configuration information related to the neighboring cell applied after L1 / L2-based movement is indicated from the serving cell via an RRC reconfiguration message. Specific configuration methods and contents are described in FIGS. 10 and 11. In addition, referring to FIG. 1n, although omitted and not illustrated before the RRC configuration information, the terminal may have received basic RRC configuration from the base station and may perform an operation of reporting layer 3 measurement values for neighboring cells. In particular, the configuration information for the LTM candidate cell applied after L1 / L2-based movement is indicated received in step (1805) may be transmitted with a delta configuration applied based on the configuration for one reference cell. The terminal can know which reference cell is known in advance or indicated via the RRC configuration and which configuration information for the reference cell is indicated. Since the configuration for neighboring cells other than the reference cell is transmitted as a common reference cell configuration and as additional configurations thereto, signaling overhead can be reduced. In the configuration of the above-described steps, the terminal can receive configuration information related to resources and reports for L1 measurements on LTM candidate cells. For detailed configuration methods, refer to the first L1 measurement resource configuration method / second L1 measurement resource configuration method and the first L1 measurement report configuration method / second L1 measurement report configuration method described above.
[0385] In step (1810), the terminal can decode the configuration for the received LTM candidate cells based on the configuration of the reference cell, and store and manage the complete configuration that is actually applied (for example, an operation of storing the configuration delta-configured based on the reference cell as a complete configuration by referring to the reference cell configuration) in a separate buffer and list. Alternatively, the terminal may store and manage the received RRC configuration as it is in the buffer, without decoding the received configuration based on the reference cell and storing and managing the configuration that is actually applied. As described above in FIG. 10, when the terminal receives a configuration in which the reference cell configuration is omitted, the terminal can recognize that there is no reference cell configuration information, and can determine and store the configuration information for the received LTM target candidate cells as complete configuration information. In this case, the terminal may not separately store the reference cell configuration information (for example, operate as empty). For example, the delta configuration may not be applied. The advantage of having the terminal decode the settings for surrounding cells based on the reference cell at this stage and store the settings to be actually applied may be that when an actual L1 / L2-based handover is instructed, the handover for the corresponding cell can be applied immediately, so there is no additional delay time.
[0386] At step (1815), the terminal can perform L1 measurement associated with candidate neighboring cells while maintaining a connection state with the serving cell, and can report the measurement results to the serving cell according to a preset L1 measurement reporting setting method. At this step, the base station can control L1 measurement resource reporting for LTM neighboring cells requiring measurement through RRC settings and L1 / L2 signaling. The terminal can perform L1 measurement resource reporting according to the settings and instructions of the base station. In addition, the terminal can measure neighboring cells according to the L3 measurement settings independently of the corresponding operation, and can report the measurement results to the base station according to the L3 measurement reporting settings. The serving cell can determine whether to change the beam of the terminal and perform a handover based on the received measurement results.
[0387] In step (1820), if the serving cell determines that a change to a specific beam of a neighboring cell is necessary rather than a specific beam of the serving cell, the serving cell may instruct a handover and beam change of the terminal through L1 / L2 signaling. Referring to FIG. 1n, the L1 / L2 signaling may be a MAC CE and a DCI, and both information indicating a specific beam of a neighboring cell and a change of serving cell may be indicated in the MAC CE (for example, when the MAC CE indicates only one beam), or a specific plurality of beams of an LTM target cell may be indicated in the MAC CE, and then a handover may be indicated in which one of the plurality of beams of the neighboring cell activated by the MAC CE is selected in the transmitted DCI.
[0388] In step (1825), the terminal can identify whether a handover is indicated from the MAC CE and DCI signaling received in step (1815), and can perform an LTM handover operation. If the MAC CE and DCI indicate a handover (e.g., the MAC CE itself indicates a handover or the MAC CE activates multiple beams and the DCI indicates a handover while indicating one of the beams), the terminal can perform a handover to a cell associated with the indicated TCI state.
[0389] If random access is successfully performed in step (1830) and handover is successful, the terminal can also apply the settings for the corresponding LTM target cell that were stored in step (1810).
[0390] In step (1835), the terminal can maintain previously stored LTM setting information and reference cell setting information.
[0391] In step (1840), the terminal can connect to the designated LTM target cell and transmit and receive data using the designated beam. The terminal can perform channel measurement reporting according to the LTM settings and continue to perform continuous LTM operations.
[0392] If the LTM handover fails in step (1830), the terminal may fall back to the previous source cell and attempt to connect in step (1845). To this end, the terminal must maintain configuration information for the source cell even if LTM is triggered. Furthermore, even after falling back to the source cell, the terminal may maintain LTM configuration information and reference cell configuration information for the LTM target cell. This may be to ensure that LTM can be triggered again according to the existing configuration. If the fallback to the source cell is not performed perfectly, the terminal may perform an RRC re-establishment procedure to reselect connectable cells. If the cell found through cell reselection is one of the LTM candidate cells, the terminal may attempt to connect by applying the preset RRC configuration for the cell.
[0393] In step (1850), the terminal may generate a handover failure report message from the cell where the connection was performed (e.g., the source cell or the target cell) and transmit it to the base station. The handover failure report message may include a UEInformationResponse or another uplink RRC message. The terminal may also report this via a new MAC CE or uplink control information (UCI). The information included in the handover failure report message may include the following information.
[0394] - An indicator indicating that the handover failed due to LTM failure.
[0395] - Target cell information that failed when attempting LTM: LTM cell configuration index or actual cell index (Physical Cell Index, PCI) information.
[0396] In one embodiment, the source base station may be notified by a handover failure message report that the LTM attempt has failed and has fallen back to the corresponding cell. In addition, if the cell found through cell reselection after the RRC re-establishment procedure is a cell other than the LTM candidate cells, the terminal may maintain the LTM configuration information and reference cell configuration information stored in the corresponding cell in step (1855). Alternatively, the terminal may release the stored LTM-related configuration information and reference cell configuration information. Alternatively, the base station may explicitly designate an action to the terminal through configuration.
[0397] FIG. 19 illustrates another operation flow of a base station for performing L1 / L2 based beam change and handover according to one embodiment of the present disclosure.
[0398] In step (1905), the base station receives an L3 measurement value report from the terminal, and based on the terminal's measurement values for surrounding frequencies and cells, can identify whether the terminal requires handover and which cells are handover candidate cells.
[0399] In step (1910), the base station may request configuration information for L1 / L2-based handover from neighboring cells and receive responses from the corresponding cells. In this step, the base station may transmit configuration information for the current source cell and reference cell configuration information to the neighboring cells. The base station may receive RRC configuration information to which delta configuration is applied based on the reference cell configuration information from neighboring cells and LTM candidate cells. In addition, in this step, inter-node coordination for L1 measurement resource and report configuration according to various embodiments of the present disclosure may be performed. The first L1 measurement resource configuration method / second L1 measurement resource configuration method and the first L1 measurement report configuration method / second L1 measurement report configuration method described above may be referenced. Although omitted in this drawing, configuration related to L3 measurement configuration and basic RRC configuration may be provided before this step.
[0400] In step (1915), the base station may transmit to the terminal in a connected state the RRC configuration message generated, including the neighboring cell configuration information and L1 measurement resource / reporting configuration information received in step (1910). For example, the base station may transmit configuration information in a neighboring cell that is applied after L1 / L2-based movement is indicated from the serving cell via an RRC reconfiguration message. Detailed configuration methods and contents are specifically described in FIGS. 10 and 11.
[0401] In step (1920), the base station can instruct L1 measurement reporting in various ways through RRC or L1 / L2 signaling, depending on the L1 measurement and reporting that the base station wants to configure and trigger. The base station can receive reports on L1 and L3 measurement values from the terminal, and at this time, the L1 measurement value can be a neighboring cell (non-serving cell) that supports L1 / L2-based mobility. The serving cell can determine whether to change the beam of the terminal and whether to perform a handover based on the received measurement results. If the serving cell determines that a change to a specific beam of a neighboring cell is necessary rather than a specific beam of the serving cell, the serving cell can instruct an LTM handover of the terminal through L1 / L2 signaling in step (1925). The L1 / L2 signaling can be MAC CE or DCI, and can include information instructing a change to a specific beam of a neighboring cell. In addition, an existing handover through an RRC message can also be performed and instructed independently in this step. This may be because the base station and serving cell independently perform LTM and Layer 3 handover decisions.
[0402] In step (1935), if the base station receives a handover completion message from the terminal, it can confirm that the corresponding LTM operation has been successfully completed, and accordingly, it can notify the previous source cell of the handover completion and request the release of the terminal context. In addition, if the base station receives a handover failure report message including information that the handover has failed, the base station can receive a message notifying that the terminal has attempted to connect to the corresponding cell again after the handover failure. The handover failure report message may include a UEInformationResponse or another uplink RRC message. In addition, the base station can receive this through a new MAC CE or uplink control information (UCI). The information included in the handover failure report message may include the following information.
[0403] - An indicator indicating that the handover failed due to LTM failure.
[0404] - Target cell information that failed when attempting LTM: LTM cell configuration index or actual cell index (Physical Cell Index, PCI) information.
[0405] The source base station can report a handover failure message to indicate that the LTM attempt failed and fell back to that cell.
[0406] FIG. 20 illustrates a functional configuration of a terminal according to one embodiment of the present disclosure.
[0407] Referring to FIG. 20, the terminal includes an RF (Radio Frequency) processing unit (2010), a baseband processing unit (2020), a storage unit (2030), and a control unit (2040).
[0408] The RF processing unit (2010) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (2010) up-converts the baseband signal provided from the baseband processing unit (2020) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (2010) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In the drawing, only one antenna is illustrated, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (2010) may include multiple RF chains. Furthermore, the RF processing unit (2010) may perform beamforming. For the above beamforming, the RF processing unit (2010) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO, and can receive multiple layers when performing the MIMO operation.
[0409] The baseband processing unit (2020) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (2020) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (2020) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (2010). For example, in the case of an orthogonal frequency division multiplexing (OFDM) method, when transmitting data, the baseband processing unit (2020) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit (2020) divides the baseband signal provided from the RF processing unit (2010) into OFDM symbol units, restores signals mapped to subcarriers through an FFT (fast Fourier transform) operation, and then restores the received bit string through demodulation and decoding.
[0410] The baseband processing unit (2020) and the RF processing unit (2010) transmit and receive signals as described above. Accordingly, the baseband processing unit (2020) and the RF processing unit (2010) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (2020) and the RF processing unit (2010) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (2020) and the RF processing unit (2010) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band, a millimeter wave (mm wave) (e.g., 60GHz) band.
[0411] The storage unit (2030) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (2030) can store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit (2030) provides the stored data at the request of the control unit (2040).
[0412] The control unit (2040) (processor or controller) controls the overall operations of the terminal. For example, the control unit (2040) transmits and receives signals through the baseband processing unit (2020) and the RF processing unit (2010). In addition, the control unit (2040) records and reads data in the storage unit (2040). For this purpose, the control unit (2040) may include at least one processor. For example, the control unit (2040) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.
[0413] FIG. 21 illustrates a functional configuration of a base station according to one embodiment of the present disclosure.
[0414] Referring to FIG. 21, the base station is configured to include an RF processing unit (2110), a baseband processing unit (2120), a backhaul communication unit (2130), a storage unit (2140), and a control unit (2150).
[0415] The RF processing unit (2110) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (2110) up-converts the baseband signal provided from the baseband processing unit (2120) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (2110) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is illustrated, but the first access node may have multiple antennas. In addition, the RF processing unit (2110) may include multiple RF chains. Furthermore, the RF processing unit (2110) may perform beamforming. For the above beamforming, the RF processing unit (2110) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.
[0416] The baseband processing unit (2120) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (2120) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (2120) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (2110). For example, in the case of OFDM, when transmitting data, the baseband processing unit (2120) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (2120) divides the baseband signal provided from the RF processing unit (2110) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (2120) and the RF processing unit (2110) transmit and receive signals as described above. Accordingly, the baseband processing unit (2120) and the RF processing unit (2110) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.
[0417] The backhaul communication unit (2130) provides an interface for communicating with other nodes within the network. That is, the backhaul communication unit (2130) converts a bit string transmitted from the main base station to other nodes, such as auxiliary base stations and core networks, into a physical signal, and converts a physical signal received from the other nodes into a bit string.
[0418] The storage unit (2140) stores data such as basic programs, application programs, and configuration information for the operation of the base station. In particular, the storage unit (2140) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (2140) can store information that serves as a basis for determining whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (2140) provides the stored data at the request of the control unit (2150).
[0419] The control unit (2150) (processor or controller) controls the overall operations of the base station. For example, the control unit (2150) transmits and receives signals through the baseband processing unit (2120) and the RF processing unit (2110) or through the backhaul communication unit (2130). In addition, the control unit (2150) records and reads data in the storage unit (2140). For this purpose, the control unit (950) may include at least one processor.
[0420] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0421] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.
[0422] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.
[0423] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.
[0424] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.
[0425] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.
Claims
1. In a wireless communication system, the CU (central unit) is Transceiver; and Including a controller coupled with the above transceiver, The above controller, Transmit a request message containing LTM (L1 / L2 triggered mobility) resource configuration information to the DU (distributed unit), and A CU configured to receive a response message including LTM reporting setting information from the above DU.
2. In claim 1, Resources included in the above LTM resource configuration information are CUs associated with SSB (SS (synchronization signal) / PBCH (physical broadcasting channel) block).
3. In claim 1, The above LTM report setting information is a CU generated based on the above LTM resource setting information.
4. In claim 1, The above request message is a CU including a UE context setup request message or a UE context modification request message.
5. In a wireless communication system, a DU (distributed unit) is Transceiver; and Including a controller coupled with the above transceiver, The above controller, Receive a request message including LTM (L1 / L2 triggered mobility) resource configuration information from a CU (central unit), and A DU configured to transmit a response message including LTM reporting setting information to the above CU.
6. In claim 5, Resources included in the above LTM resource configuration information are DUs associated with SSB (SS (synchronization signal) / PBCH (physical broadcasting channel) block).
7. In claim 5, The above LTM report setting information is DU generated based on the above LTM resource setting information.
8. In claim 5, The above request message is a DU including a UE context setup request message or a UE context modification request message.
9. A method performed by a CU (central unit) in a wireless communication system, A step of transmitting a request message including LTM (L1 / L2 triggered mobility) resource configuration information to a DU (distributed unit); and A method comprising the step of receiving a response message including LTM reporting setting information from the above DU.
10. In claim 9, The resources included in the above LTM resource configuration information are related to SSB (SS (synchronization signal) / PBCH (physical broadcasting channel) block).
11. In claim 9, The above LTM report setting information is a method generated based on the above LTM resource setting information.
12. In claim 9, A method wherein the above request message includes a UE context setup request message or a UE context modification request message.
13. A method performed by a DU (distributed unit) in a wireless communication system, A step of receiving a request message including LTM (L1 / L2 triggered mobility) resource configuration information from a CU (central unit); and A method comprising the step of transmitting a response message including LTM reporting setting information to the CU.
14. In claim 13, The resources included in the above LTM resource configuration information are related to SSB (SS (synchronization signal) / PBCH (physical broadcasting channel) block).
15. In claim 13, The above LTM report setting information is generated based on the above LTM resource setting information, and A method wherein the above request message includes a UE context setup request message or a UE context modification request message.
Citation Information
Patent Citations
Configuration enhancements for an intra-GNB-du intra‑frequency l1 / l2 inter cell change
WO2023012646A1
Method and apparatus for l1 / l2-based inter-cell mobility
WO2023075423A1
Cited By
Methods for measurement reporting via channel state information activation or deactivation
US12633988B2
Communication method and communication apparatus
WO2026189105A1
