Method and device for performing handover without random access for moving integrated access and backhaul system in next-generation mobile communication system
The method enables efficient handover of mobile IAB nodes by initiating an F1 setup with a target CU, allowing for handover without random access, thus addressing the challenge of network stability and service continuity in next-generation mobile communication systems.
Patent Information
- Application Number
- PCT/KR2024/006458
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-14
AI Technical Summary
Current mobile communication systems face challenges in efficiently performing handover operations without random access, particularly when a mobile Integrated Access and Backhaul (IAB) node moves, which can disrupt network stability and service continuity.
The method involves a mobile IAB node initiating an F1 setup with a target central unit (CU) through a distributed unit (DU), allowing for handover without random access by activating cells and transmitting information related to these cells to the source CU, enabling seamless handover operations.
This approach ensures efficient handover of mobile IAB nodes without the need for random access, enhancing network stability and service continuity by optimizing the handover process in next-generation mobile communication systems.
Smart Images

Figure KR2024006458_14112024_PF_FP_ABST
Abstract
Description
Method and device for performing handover without random access for moving an access backhaul combination system in a next-generation mobile communication system
[0001] The present invention relates to the operation of a terminal in a mobile communication system. Specifically, the present invention relates to a handover technique that can be performed without a random access channel (RACH) of a terminal when a mobile IAB (mIAB) node moves.
[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] As mobile communication systems have developed, they have become capable of providing a variety of services, and thus, methods for effectively providing these services are required.
[0009] The purpose of the present invention is to enable a terminal to efficiently perform handover without performing random access when moving a mobile IAB (mIAB) node.
[0010] In order to solve the above problem, a method performed by a mobile integrated access and backhaul (IAB) node in a wireless communication system according to an embodiment of the present disclosure may include the steps of: initiating, by a target logical distributed unit (DU), an F1 setup with a target central unit (CU); serving, by the target logical DU, a terminal based on at least one cell activated by the target logical DU based on the F1 setup; and transmitting, by a source logical DU, information related to at least one cell activated by the target logical DU to a source CU.
[0011] In another embodiment of the present disclosure, a wireless communication system, a mobile integrated access and backhaul (IAB) node may include a control unit configured to control a transceiver and a target logical distributed unit (DU) to initiate an F1 setup with a target central unit (CU), to control the target logical DU to serve a terminal based on the F1 setup, and to control the source logical DU to transmit information related to the at least one cell activated by the target logical DU to the source CU through the transceiver.
[0012] According to an embodiment of the present invention, when a mobile IAB (mIAB) node moves, a terminal can efficiently perform handover without performing random access.
[0013] Figure 1 is a diagram illustrating the structure of a typical LTE system.
[0014] Figure 2 is a diagram showing the wireless protocol structure of a typical LTE system.
[0015] FIG. 3 is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
[0016] FIG. 4 is a diagram illustrating a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
[0017] FIG. 5 is a block diagram illustrating the internal structure of a terminal according to an embodiment of the present disclosure.
[0018] FIG. 6 is a block diagram showing the configuration of a base station according to an embodiment of the present disclosure.
[0019] FIG. 7 is a sequence diagram specifically describing handover of a mobile termination (MT) and migration of a DU of a mobile Integrated access and backhaul (mIAB) node according to an embodiment of the present disclosure.
[0020] FIG. 8 is a flowchart illustrating a method of a base station according to an embodiment of the present disclosure.
[0021] The operating principles of the present invention will be described in detail below with reference to the attached drawings. In the following description of the present invention, detailed descriptions of known functions or components will be omitted if they are deemed to unnecessarily obscure the gist of the invention. Furthermore, the terms described below are defined based on their functions in the present invention and may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the overall content of this specification.
[0022] The terms used in the following description to identify 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 provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.
[0023] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which the embodiments of the present disclosure may be applied, and 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure. It will be appreciated that each block of the processing flow diagrams and combinations of the flow diagrams can be executed by computer program instructions.
[0024] These computer program instructions may be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, so that the instructions executed by the processor of the computer or other programmable data processing apparatus create means for performing the functions described in the flowchart block(s). These computer program instructions may also be stored in a computer-available or computer-readable memory that can be directed to a computer or other programmable data processing apparatus to implement functions in a particular manner, so that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes instruction means for performing the functions described in the flowchart block(s). The computer program instructions may also be installed on a computer or other programmable data processing apparatus, so that a series of operational steps are performed on the computer or other programmable data processing apparatus to create a computer-implemented process, so that the instructions executing on the computer or other programmable data processing apparatus can provide steps for performing the functions described in the flowchart block(s).
[0025] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the corresponding function. In this case, the term '~unit' used in the present embodiment means software or a hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the '~unit' may perform certain roles. However, the '~unit' is not limited to software or hardware. The '~unit' may be configured to be on an addressable storage medium and may be configured to execute one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to reproduce one or more CPUs within a device or a secure multimedia card. Also, in an embodiment, the '~ unit' may include one or more processors.
[0026] For convenience of explanation, the present invention uses terms and names defined in the 5GS and NR standards, which are standards defined by the 3rd Generation Partnership Project (3GPP) among the existing communication standards. However, the present invention is not limited to the above terms and names and can be equally applied to wireless communication networks that follow other standards. For example, the present invention can be applied to the 3GPP 5GS / NR (5th generation mobile communication standard).
[0027] Figure 1 is a diagram illustrating the structure of a typical LTE system.
[0028] Referring to FIG. 1, as illustrated, a wireless access network of an LTE system may be composed of next-generation base stations (Evolved Node Bs, hereinafter referred to as ENBs, Node Bs or base stations) (1-05, 1-10, 1-15, 1-20), a mobility management entity (MME) (1-25) and an S-GW (1-30, Serving-Gateway). A user equipment (UE or terminal) (1-35) may access an external network through the ENBs (1-05 to 1-20) and the S-GW (1-30).
[0029] In Fig. 1, ENBs (1-05 to 1-20) may correspond to existing Node Bs of a UMTS system. ENBs are connected to UEs (1-35) via a wireless channel and may perform more complex roles than existing Node Bs. In an LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, can be serviced through a shared channel. Therefore, a device that collects status information such as the buffer status of UEs, available transmission power status, and channel status and performs scheduling is required, and ENBs (1-05 to 1-20) may be responsible for this. One ENB can typically control multiple cells. For example, to achieve a transmission rate of 100 Mbps, an LTE system may use, for example, Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology in a 20 MHz bandwidth. Additionally, an adaptive modulation and coding (AMC) method can be applied, which determines the modulation scheme and channel coding rate according to the channel condition of the terminal. The S-GW (1-30) is a device that provides a data bearer and can create or remove a data bearer according to the control of the MME (1-25). The MME is a device that is responsible for various control functions as well as mobility management functions for the terminal and can be connected to multiple base stations.
[0030] Figure 2 is a diagram showing the wireless protocol structure of an existing LTE system.
[0031] Referring to Figure 2, the wireless protocol of the LTE system may be composed of Packet Data Convergence Protocol (PDCP) (2-05, 2-40), Radio Link Control (RLC) (2-10, 2-35), and Medium Access Control (MAC) (2-15, 2-30) in the terminal and ENB, respectively. PDCP may be responsible for operations such as IP header compression / decompression. The main functions of PDCP can be summarized as follows.
[0032] - Header compression and decompression (ROHC only)
[0033] - User data transfer function
[0034] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM
[0035] - Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)
[0036] - Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)
[0037] - Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)
[0038] - Encryption and decryption functions (Ciphering and deciphering)
[0039] - Timer-based SDU discard in uplink.
[0040] Radio Link Control (RLC) (2-10, 2-35) can perform ARQ operations, etc. by reconfiguring PDCP packet data units (PDUs) to an appropriate size. The main functions of RLC can be summarized as follows.
[0041] - Data transfer function (Transfer of upper layer PDUs)
[0042] - ARQ function (Error Correction through ARQ (only for AM data transfer))
[0043] - Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer)
[0044] - Re-segmentation of RLC data PDUs (only for AM data transfer)
[0045] - Reordering of RLC data PDUs (only for UM and AM data transfer)
[0046] - Duplicate detection (only for UM and AM data transfer)
[0047] - Error detection function (Protocol error detection (only for AM data transfer))
[0048] - RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))
[0049] - RLC re-establishment function
[0050] MAC (2-15, 2-30) connects to multiple RLC layer devices configured in a single terminal and can perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC can be summarized as follows.
[0051] - Mapping function (Mapping between logical channels and transport channels)
[0052] - Multiplexing and demultiplexing function (Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels)
[0053] - Scheduling information reporting function
[0054] - HARQ function (Error correction through HARQ)
[0055] - Priority handling between logical channels of one UE
[0056] - Priority handling between UEs by means of dynamic scheduling
[0057] - MBMS service identification function
[0058] - Transport format selection function
[0059] - Padding function
[0060] The physical layer (2-20, 2-25) can perform the 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.
[0061] Figure 3 is a diagram illustrating the structure of a next-generation mobile communication system.
[0062] Referring to FIG. 3, a wireless access network of a next-generation mobile communication system (hereinafter referred to as NR or 5g) may be composed of a next-generation base station (New Radio Node B, hereinafter referred to as NR gNB or NR base station) (3-10) and a next-generation radio core network (New Radio Core Network, NR CN) (3-05). A next-generation radio user equipment (New Radio User Equipment, NR UE or terminal) (3-15) may access an external network through the NR gNB (3-10) and the NR CN (3-05).
[0063] In Fig. 3, the NR gNB (3-10) may correspond to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (3-15) via a wireless channel and can provide superior services than the existing Node B. In the next-generation mobile communication system, all user traffic can be serviced through a shared channel. Therefore, a device that collects status information such as the buffer status of the UEs, the available transmission power status, and the channel status and performs scheduling is required, and the NR NB (3-10) may be responsible for the scheduling. One NR gNB may control multiple cells. In the next-generation mobile communication system, in order to implement ultra-high-speed data transmission compared to the general LTE, a bandwidth exceeding the general maximum bandwidth may be applied. In addition, beamforming technology may be additionally grafted using Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology. 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. NR CN (3-05) can perform functions such as mobility support, bearer setup, and QoS setup. NR CN is a device that is responsible for various control functions as well as mobility management functions for the terminal and can be connected to multiple base stations. In addition, the next-generation mobile communication system can also be linked with the LTE system, and NR CN can be connected to MME (3-25) through a network interface. MME can be connected to eNB (3-30), which is an LTE base station.
[0064] Figure 4 is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which the present invention can be applied.
[0065] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system consists of NR Service Data Adaptation Protocol (SDAP) (4-01, 4-45), NR PDCP (4-05, 4-40), NR RLC (4-10, 4-35), NR MAC (4-15, 4-30), and NR PHY (4-20, 4-25) in the terminal and NR base station, respectively.
[0066] Key features of NR SDAP (4-01, 4-45) may include some of the following:
[0067] - Transfer of user plane data
[0068] - Mapping function between QoS flow and data bearer for both DL and UL
[0069] - QoS flow ID marking function for uplink and downlink (marking QoS flow ID in both DL and UL packets)
[0070] - Ability to map relective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).
[0071] For an SDAP layer device, a terminal can be configured by a Radio Resource Control (RRC) message for each PDCP layer device, per bearer, or per 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 instruct the terminal to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink by using a 1-bit indicator for reflecting the Non-Access Stratum (NAS) Quality of Service (QoS) in the SDAP header (NAS reflective QoS) and a 1-bit indicator for reflecting the Access Stratum (AS) QoS in the SDAP header. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.
[0072] The main functions of NR PDCP (4-05, 4-40) may include some of the following functions:
[0073] - Header compression and decompression (ROHC only)
[0074] - User data transfer function
[0075] - In-sequence delivery of upper layer PDUs
[0076] - Out-of-sequence delivery of upper layer PDUs
[0077] - PDCP PDU reordering for reception
[0078] - Duplicate detection of lower layer SDUs
[0079] - Retransmission function (Retransmission of PDCP SDUs)
[0080] - Encryption and decryption functions (Ciphering and deciphering)
[0081] - Timer-based SDU discard in uplink.
[0082] In the above, the reordering function of the NR PDCP device may refer to a function of reordering PDCP PDUs received from a lower layer in order based on a 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 a function of transmitting data directly without considering the order, 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, and a function of requesting retransmission of lost PDCP PDUs.
[0083] The main features of NR RLC(4-10, 4-35) may include some of the following:
[0084] - Data transfer function (Transfer of upper layer PDUs)
[0085] - In-sequence delivery of upper layer PDUs
[0086] - Out-of-sequence delivery of upper layer PDUs
[0087] - ARQ function (Error Correction through ARQ)
[0088] - Concatenation, segmentation and reassembly of RLC SDUs
[0089] - Re-segmentation of RLC data PDUs
[0090] - Reordering of RLC data PDUs
[0091] - Duplicate detection function
[0092] - Protocol error detection
[0093] - RLC SDU discard function
[0094] - RLC re-establishment function
[0095] In the above, the in-sequence delivery function of the NR RLC device may refer to the function of sequentially delivering RLC SDUs received from the lower layer to the upper layer. If a single RLC SDU is originally received divided into multiple RLC SDUs, the in-sequence delivery function of the NR RLC device may include the function of reassembling and delivering them.
[0096] The in-sequence delivery function of the NR RLC device may include a function to reorder received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), a function to record lost RLC PDUs by reordering them, a function to report status of lost RLC PDUs to the transmitter, and a function to request retransmission of lost RLC PDUs.
[0097] The in-sequence delivery function of the NR RLC device may include a function to sequentially deliver only the RLC SDUs up to the lost RLC SDU to the upper layer when there is a lost RLC SDU.
[0098] The in-sequence delivery function of the NR RLC device may include a function to deliver to the upper layer in sequence all RLC SDUs received before a predetermined timer starts if there are lost RLC SDUs and a predetermined timer has expired.
[0099] The in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received so far to the upper layer in order if a predetermined timer has expired, even if there are lost RLC SDUs.
[0100] An NR RLC device can process RLC PDUs in the order they are received and deliver them to an NR PDCP device, regardless of the order of the sequence number (out-of-sequence delivery).
[0101] When an NR RLC device receives a segment, it can receive segments that are stored in a buffer or will be received later, reconstruct them into a complete RLC PDU, and then transmit them to the NR PDCP device.
[0102] The NR RLC layer may not include concatenation functionality, and the functionality may be performed by the NR MAC layer or replaced by the multiplexing functionality of the NR MAC layer.
[0103] In the above, the out-of-sequence delivery function of the NR RLC device may mean 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 the RLC SDUs when an original RLC SDU is received fragmented into multiple RLC SDUs. The out-of-sequence delivery function of the NR RLC device may include the function of storing the RLC SN or PDCP SN of the received RLC PDUs and arranging the order to record the lost RLC PDUs.
[0104] NR MAC (4-15, 4-30) 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.
[0105] - Mapping function (Mapping between logical channels and transport channels)
[0106] - Multiplexing / demultiplexing of MAC SDUs
[0107] - Scheduling information reporting function
[0108] - HARQ function (Error correction through HARQ)
[0109] - Priority handling between logical channels of one UE
[0110] - Priority handling between UEs by means of dynamic scheduling
[0111] - MBMS service identification function
[0112] - Transport format selection function
[0113] - Padding function
[0114] The NR PHY layer (4-20, 4-25) can perform operations such as 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.
[0115] Figure 5 is a block diagram showing the structure of a terminal according to one embodiment of the present invention.
[0116] Referring to the above drawing, the terminal includes an RF (Radio Frequency) processing unit (5-10), a baseband processing unit (5-20), a storage unit (5-30), and a control unit (5-40).
[0117] The RF processing unit (5-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (5-10) up-converts the baseband signal provided from the baseband processing unit (5-20) 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 (5-10) 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 shown, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (5-10) may include multiple RF chains. Furthermore, the RF processing unit (5-10) may perform beamforming. For the above beamforming, the RF processing unit (5-10) 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 receive multiple layers when performing the MIMO operation.
[0118] The baseband processing unit (5-20) above 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 (5-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (5-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (5-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (5-20) 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 (5-20) divides the baseband signal provided from the RF processing unit (5-10) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform), and then restores the received bit string through demodulation and decoding.
[0119] The baseband processing unit (5-20) and the RF processing unit (5-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (5-20) and the RF processing unit (5-10) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (5-20) and the RF processing unit (5-10) 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 (5-20) and the RF processing unit (5-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include 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 and a millimeter wave (mm wave) (e.g., 60GHz) band.
[0120] The storage unit (5-30) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (5-30) can store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit (5-30) provides the stored data at the request of the control unit (5-40).
[0121] The above control unit (5-40) controls the overall operations of the terminal. For example, the control unit (5-40) transmits and receives signals through the baseband processing unit (5-20) and the RF processing unit (5-10). In addition, the control unit (5-40) records and reads data in the storage unit (5-40). For this purpose, the control unit (5-40) may include at least one processor. For example, the control unit (5-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.
[0122] According to one embodiment of the present disclosure, the control unit (5-40) can receive a HO command message from a source donor CU. For example, when the source donor CU transmits a HO request including a RACH-less HO indication to the target donor CU, and the target donor CU transmits a HO request response to the source donor CU, the control unit (5-40) receives the HO command message from the source donor CU. In addition, the control unit (5-40) can control to perform a handover according to the RACH-less HO configuration information.
[0123] Figure 6 is a block diagram showing the configuration of a base station according to one embodiment of the present invention.
[0124] As shown in the above drawing, the base station is configured to include an RF processing unit (6-10), a baseband processing unit (6-20), a backhaul communication unit (6-30), a storage unit (6-40), and a control unit (6-50).
[0125] The RF processing unit (6-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (6-10) up-converts the baseband signal provided from the baseband processing unit (6-20) 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 (6-10) 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 shown, but the first access node may have multiple antennas. In addition, the RF processing unit (6-10) may include multiple RF chains. Furthermore, the RF processing unit (6-10) may perform beamforming. For the beamforming, the RF processing unit (6-10) may adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The above RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.
[0126] The baseband processing unit (6-20) above 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 (6-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (6-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (6-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (6-20) 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 (6-20) divides the baseband signal provided from the RF processing unit (6-10) 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 (6-20) and the RF processing unit (6-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (6-20) and the RF processing unit (6-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.
[0127] The above backhaul communication unit (6-30) provides an interface for communicating with other nodes within the network. The above backhaul communication unit (6-30) 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.
[0128] The storage unit (6-40) stores data such as basic programs, application programs, and configuration information for the operation of the main base station. In particular, the storage unit (6-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (6-40) can store information that serves as a judgment criterion for whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (6-40) provides the stored data at the request of the control unit (6-50).
[0129] The control unit (6-50) controls the overall operations of the base station. For example, the control unit (6-50) transmits and receives signals through the baseband processing unit (6-20) and the RF processing unit (6-10) or through the backhaul communication unit (6-30). In addition, the control unit (6-50) records and reads data in the storage unit (6-40). For this purpose, the control unit (6-50) may include at least one processor.
[0130] According to one embodiment, the base station of FIG. 6 may be a base station including a source donor CU. The control unit (6-50) of the base station may determine the handover of the MT. When the HO is completed, the control unit (6-50) may control to receive a HO success message including information from the target donor CU. At this time, the information may include at least one of NCGI of CU2 (target gNB), PCI of target cell (under CU2), PLMN ID of target cell under CU2, and mIAB node ID and / or MT ID (an ID that can be uniquely distinguished among gNBs).
[0131] The above control unit (6-50) can determine the migration of the DU based on the above information. In addition, the control unit (6-50) can determine the RACH-less HO of the terminal. At this time, the control unit (6-50) can control to transmit an HO request message including a RACH-less HO indication to the target donor CU and receive an HO request response message from the target donor CU.
[0132] FIG. 7 is a sequence diagram specifically describing handover of a mobile termination (MT) and migration of a DU of a mobile Integrated access and backhaul (mIAB) node according to one embodiment of the present disclosure.
[0133] The mIAB node may be composed of a DU (711) and a MT (712). The mIAB node may be connected to CU1 (720) as a donor CU through an initial connection process. Furthermore, the mIAB node may serve a terminal (700) via CU1 (720). At this time, the donor CU of the DU (711) may also be CU1 (720). Accordingly, traffic generated from the terminal (700) or control plane / user plane traffic generated in the core to be transmitted to the terminal (700) may be transmitted via CU1 (720). Furthermore, CU1 (720) may be an F1 termination anchor of the DU (711). Accordingly, F1 traffic between the DU (711) and CU1 (720) may be transmitted in step S701.
[0134] Due to the movement of mIAB, MT (712) can perform handover with CU2 (730) as the CU of the target cell first. At this time, CU1 (720), which is the serving node CU of MT (712), can decide to handover with CU2 (730) as the target cell. In step S702, CU1 (720) can decide to handover MT (712).
[0135] At step S703, CU1 (720) may transmit a handover request message to CU2 (730). And at S704, CU2 (730) may transmit a handover response message to CU1 (720).
[0136] For example, CU1 (720) can prepare HO by sending an HORequest message to CU2 (730). CU2 (730) can include target cell configuration information for MT (712) of the mIAB in an HOReqACK message and transmit it to CU1 (720).
[0137] In step S705, CU1 (720) may transmit an RRC reset message including a handover command (HO command) to MT (712). For example, CU1 (720) may transmit configuration information in the target cell, for example, the HO command, to MT (712) through the source cell.
[0138] In step S706, MT (712) can perform a RACH procedure with CU2 (730). For example, MT (712) that has received the HO command can receive UL grant and TA through random access (RA) preamble transmission and RA response (RAR) reception.
[0139] And in step S707, MT (712) may transmit an RRCReconfigurationComplete message to CU2 (730). For example, MT (712) may transmit an RRCReconfigurationComplete message to the target cell.
[0140] In step S708, CU2 (730) can transmit a HO success message or a separate Xn message to CU1 (720). Specifically, CU2 (730) that has received the RRCReconfigurationComplete message can transmit a HO success message to CU1 (720), which is a source CU. At this time, the CU ID of the target cell or the ID of the gNB that successfully performed the handover of the mIAB MT (712) can be transmitted to CU1 (720), which is a donor CU of the mIAB DU, through the HO success message or a separate X2 message. At this time, the transmitted information can specifically be at least one of the following.
[0141] - NCGI of CU2 (target gNB)
[0142] - PCI of target cell (under CU2)
[0143] -PLMN ID of target cell under CU2
[0144] - mIAB node ID and / or MT ID (ID that can be uniquely distinguished among gNBs)
[0145] In step S709, CU1 (720) may determine migration of DU (711). For example, at some point, based on the above information, CU1 (720) (e.g., source donor CU of co-located DU (711)) may determine DU migration to CU2 (730).
[0146] If the migration of DU (711) is determined, CU1 (720) can instruct DU (711) to setup F1 interface with CU2 (730) through CU2 (730). Specifically, in step S710, CU1 (720) can transmit an Xn message requesting F1 setup to CU2 (730). In step S711, CU2 (730) can transmit an F1 setup request message including CU2 information to DU (711). And in step S712, DU (711) can perform F1 setup procedure to CU2 (730) through IP / TNL address.
[0147] In step S713, DU (711) can perform F1 setup and configuration with CU2 (730), and perform logical DU2 setup and configuration. For example, DU (711) that received the above instruction can set up CU2 (730) and F1. Thereafter, CU2 (730) and DU (711) can exchange setup / modification of a CU2 specific cell of a logical DU, for example, a target logical DU cell, through F1. As a result, the target logical DU cell can operate. At this time, CU1 (720) can obtain information on cells that the target logical DU can activate or is scheduled to activate due to CU2 (730). The information on the cells can include at least one of information such as NR CGI, PCI, and ARFCN. In addition, information on the beam configuration of each activated cell, for example, how many beams it consists of and whether operation is possible in each new cell with the same settings as the beams configured and operated in the existing source cell, can also be obtained. The process of obtaining the above information can be performed by having CU1 request DU with an F1 message after DU obtains information on the activated cell of the target cell from CU2, or by having DU obtain information from CU2 and then transmit it to CU1 with an F1 message.
[0148] Additionally, after the DU obtains the negotiated information with the CU2, it can transmit to the CU1, in the same manner as above, whether a specific terminal is capable of RACH-less HO, whether the same beam can be used in the source cell and target cell in case of RACH-less HO, or the beam index and related information of the beam that can be used in the target cell.
[0149] After the target logical DU cell is configured and operated or at the time mentioned above, the information can be given from CU2 (730) to CU1 (720).
[0150] Through the above information, CU1 can determine whether RACH-less HO should be performed or can be performed for a specific terminal.
[0151] The current state may be one in which both the source logical DU cell and the target logical DU cell are configured and operating independently. In addition, accordingly, DU (711) is connected to both CU1 (720) and CU2 (730).
[0152] In this situation, the UEs may also need to perform HO from the source logical DU cell to the target logical DU cell as the DU cell changes. In this case, the node that determines whether to perform RACH-less HO of the UE may be the serving gNB of the access UE or the source donor CU of the collocated DU. In Fig. 7, it is the same as CU1 (720), but in an environment where the migration and HO of the MT (712) and the DU (711) are performed independently, the two nodes may be separated.
[0153] Issue 1: RACH-less HO determination.
[0154] In step S714, CU1 (720) may determine RACH-less HO for the terminal. The CU1 (720) may determine RACH-less HO and determine a target cell and target node of the RACH-less HO.
[0155] In step S715, CU1 (720) may transmit a HO request message including a RACH-less HO indication to CU2 (730). And in step S718, CU2 (730) may transmit a HO request response message to CU1 (720).
[0156] For example, the CU1 (720) can transmit the information to a target node (e.g., CU2 (730)). At this time, the target node can be a target donor node at the time of migration of the collocated DU / or a CU of the target donor node (e.g., CU2 (730)).
[0157] At this time, when CU1 (720) transmits the rach-less HO information to CU2 (730), the Xn message may be used. As an example, the HORequest message may be used. The conditions / or time points at which the message may be transmitted may include at least one of the following:
[0158] ● During mIAB DU's migration procedure; and / or
[0159] ● (in detail) after mIAB DU's F1 setup with target donor completed and / or F1 configuration was completed; and / or
[0160] ● logical DU2 (logical target DU)'s configuration from target donor CU was completed; and / or
[0161] ● the target cell of access UE or logical DU2 's cell was configured with the target donor of DU and / or turned on.; or
[0162] ● after mIAB DU's migration completed
[0163] At this time, the information that can be conveyed in the HORequest message may include at least one of the following:
[0164] ● The following information may be included per UE:
[0165] RACH-less HO indication which means:
[0166] ● RACH-less HO preference; and / or
[0167] it means the sender node wants / prefers RACH-less HO to this UE,
[0168] In this case, the target node may or may not accept RACH-less HO. If not, it may return admission control for general RACH-based HO and configuration information in the target cell to the sender node.
[0169] ● RACH-less HO request
[0170] It means request for the target node to reserve RACH-less HO resources
[0171] In this case, the target node may or may not accept the RACH-less HO. If it does not accept it, it may send an HORequest NACK message to the sender node.
[0172] mIAB served indication (indicator that the terminal is being served by a mobile IAB node)
[0173] ● with mIAB node ID (NCGI and / or DU ID) which can be recognized among the CU nodes
[0174] mIAB indication means this UE is under serving of mIAB node
[0175] ● logical DU identity connected to the DU's source donor CU and / or
[0176] ● logical DU identity connected to the DU’s target donor CU
[0177] (All information related to RACH-less HO) Feasibility of RACH-less HO
[0178] ● feasibility of RACH-less HO itself (collective meaning) and / or
[0179] Assuming that it knows the frequency and beam formation information of the source cell, as well as the frequency and beam configuration information to be used for the cells to be activated as target cells, the source CU can comprehensively convey a judgment (Yes or No) on whether RACH-less HO is feasible. However, this is still only an estimate from the source node, and the final decision can be made by the target node.
[0180] ● indication / request of whether source cell and target cell (can) have the same frequency (range / or part) :
[0181] reason: When migrating the above mIAB DU, the access UE cannot transmit measurement information about the corresponding cell to the serving base station because the target cell is not yet turned on (normal operation state) unlike the general handover preparation operation. However, CU1 can know which cell will be activated as the target logical DU cell from the target donor CU through F1. Based on the above information, if there is a cell with the same frequency among the cells to be activated as the target cell, it may mean that the same cell is requested as the target cell as the RACH-less HO target cell of the UE. Since already transmitting node of this message might know the activated cells by the target donor of DU (via F1 signaling from mIAB DU to the source donor of DU after F1 setup completion),
[0182] ● indication on whether source cell and target cell can have the common beam configuration to be used; or
[0183] It may indicate whether or not the beam to be used in the target cell for RACH-less HO of the above terminal can apply the same settings for beam forming as the beam to be used in the current source cell.
[0184] ● request on same beam configuration / status to be used in the target cell as the source cell
[0185] An indicator requesting that the beam to be used in the target cell for RACH-less HO of the above terminal be the same beam as the beam currently being used by the source.
[0186] information on the beam used in the source cell (this can be in another RRC container not HOpreparationInformation, or another Xn info field)
[0187] ● currently used beam information such as
[0188] Cell frequency information (NR AFRCN and / or PCI information)
[0189] TCI state info configured in RRC for each DL BWP and UL BWP
[0190] TCI state info indicated by MAC CE or DCI for DL and UL both
[0191] TCI state info indicated for the purpose of each physical channel PDSCH, PDCCH, PUCCH, PUSCH
[0192] ● Reason: legacy RRC INM HOPrepration only has the static info, ie, RRC initiated TCI state information per BWP per cells, at least MAC CE / DCI indicated beam info is not known by the target CU.
[0193] The above information may be transmitted as information for a specific terminal, such as an HORequest or HORequestACK message, which is currently an Xn message. In another embodiment, the information required for the HO preparation may be stored for multiple terminals (or terminals in all connection modes), rather than one terminal, and transmitted by the transmitting node to the target node. In this case, some of the per-UE information may be included in a common field. For example, the mIAB served indication may be included in the common field. In addition, the RACH-less HO indication may also be included in the common field, or may be included for each terminal.
[0194] ● Msg to be used
[0195] Per UE case: HOReq / HOReqACK msg
[0196] Bulk HO preparation case: new Xn msg which include all the target UE's context for HO request (refer the legacy HOReq msg contents)
[0197] ● Additionally, mIAB served indication above can be included in common part
[0198] ● Additionally, RACH-less HO indication and feasibility above can be included in common part; or
[0199] Per UE in that msg.
[0200] Issue 2: Signaling between target donor CU and target logical DU
[0201] The target donor CU (e.g., CU2 (730)) that receives the HORequest message may transmit an RRC inter-node message Handover preparation information to the target logical DU. The HORequest message is included in the HORequest message. Additionally, the target donor CU may transmit a RACH-less HO indication or request indicator and / or all or part of the information received in the HORequest to the target logical DU. For example, all or part of the information, e.g., RRC INM HO preparation information and RACH-less HO indication / request indicator and / or the information received in the HORequest, may be transmitted in an F1 message (e.g., UEContextSetupRequest message). (e.g., S716)
[0202] The target logical DU that receives the above information can perform at least one of the following:
[0203] ● Target logical DU can evaluate whether to reuse the same beam as in the source cell with above information.
[0204] ● Target logical DU can evaluate whether rach-less HO is possible in PHY, MAC configuration perspective
[0205] ● If beam to be reused is valid, target logical DU generate either
[0206] ● Indication to reuse the source cell beam
[0207] ● Explicit beam information as TCI state ID used at the source cell. And this beam can be immediately used without MAC CE / DCI dynamic indication.
[0208] ● Target logical DU generate the L1, L2 configuration including phy, MAC parameters to be used at the target cell, and include this to the RRC CellGroupConfig field or Pcell's serving cell configuration, further include the following RACH-less HO configurations:
[0209] ● UL grant information
[0210] ● Beam information to be used
[0211] ● BWP configuration for UL and / or DL transmission via beam at the target cell
[0212] ● TA configuration
[0213] ● 상기 정보들은 후술하는 issue 3에서 HO command 메시지에 포함되는 정보들과 동일할 수 있다.
[0214] ● This information about cell group configuration / or Pcell's serving cell configuration is sent back to the target donor CU via an F1 message. In this case, the F1 message may be a UEContextSetupResponse message (e.g., S717).
[0215] Issue 3: target donor operation
[0216] The operation of the target donor node that receives the cell group configuration or Pcell's serving cell configuration including RACH-less Handover configuration from the target logical DU is as follows.
[0217] When the target donor node receives the above message, the target donor node can admit RACH-less HO to the terminal only if the message includes a RACH-less HO indicator. Then, the target donor node can transmit configuration information in the target cell, for example, a handover command, to the source node and / or to the terminal.
[0218] The information contained in the handover command to be transmitted may include at least one of the following:
[0219] Rach-less HO configuration info (this can be in the field specific field like rachskip-NR in reconfigurationWithSync field)
[0220] ● The above RACH-less HO setting may include an indicator indicating which terminal the RACH-less HO is for. This indicator may indicate whether the setting is for a terminal receiving a service from a mobile IAB node, a terminal receiving an NTN service, or an LTM (L1 / 2 triggered mobility) terminal.
[0221] ● As UL grant information, the following is possible:
[0222] Time / frequency resource information, which also associated with the periodicity and duration
[0223] For example, it can be a type 1 CG or a type 2 radio resource (format).
[0224] For each of the above UL grant resources, information is associated with the TCI state ID of a specific beam information source cell, the SSB (or CSI-RS) ID transmitted from the source cell, and / or the ID of the beam on which the SSB (or CSI-RS) is transmitted. If the terminal uses a specific beam according to the above information, the terminal can use the UL grant resource associated with the beam for UL transmission. Or, conversely, if the terminal selects to use a specific resource among the above UL grants, the terminal can use the associated beam for UL transmission.
[0225] ● Beam information to be used for UL transmission / DL reception at the target cell
[0226] Beam information for UL transmission, which is associated with the resource for UL grant information above.
[0227] For UL / DL, there can be indicator to use the same beam (or same beam configuration / status) used at the source cell; or
[0228] Explicit beam information to be used at the target cell,
[0229] Beams to be used. A subset of TCI state ID is indicated by RRC and / or MAC CE and / or DCI for any purposes. (Here, the purpose can be information about the physical channel on which the beam is used. For example, purposes such as PDCCH reception, PDSCH reception, PUSCH transmission, and PUCCH transmission can be considered for specifying the beam.)
[0230] This can be further indicated using the source cell's beam indication or target cell's beam indication.
[0231] And beam is transmitting the reference signal such as SSB or CSI-RS, of this reference signal's resource configuration on time / frequency and resource ID can be indicated together with the beam TCI state ID. That is, for the purpose of specifying the beam used, it can refer to a beam that transmits and / or receives a specific SSB or CSI-RS.
[0232] ● BWP configuration for UL and / or DL transmission via beam at the target cell
[0233] Can be indicated via source cell's BWP ID, or can be indicated in conjunction with the UL grant resource and BWP.
[0234] ● TA configuration
[0235] Indication to Reuse legacy TA value. Here, legacy TA values can be indicated as one of the following:
[0236] Current Pcell TA
[0237] TAG ID: TA for that TAG to be reused
[0238] Specific offset for the current TA: A specific offset value can be added or reduced for the legacy TA value.
[0239] if there are some discrete position to be seated, and that information is already known by the network (donor CU)
[0240] As another example, if separate TA configuration information is not provided in the RACH-less HO configuration information, the terminal can use the TA value of the current Pcell as is.
[0241] Issue 4: Signals to and operation of the terminal
[0242] For example, in step S719, the terminal (700) that receives the HO command from the source cell (e.g., CU1 (720)) through the source donor node can perform handover according to the given RACH-less HO configuration information.
[0243] If a RACH-less HO configuration info indicator or configuration information exists in the HO command, the terminal (700) can perform RACH-less HO by applying the configuration information included in the corresponding field.
[0244] At this time, if UL grant information exists, a TB including an RRCReconfigurationcomplete message can be transmitted through the corresponding UL grant.
[0245] Additionally, if beam information is given, if a beam reuse indicator is given in the serving cell, the terminal (700) can use the beam in the serving cell used at the time of receiving the HO command for UL transmission and / or DL reception in the target cell. Alternatively, if there is explicit beam information about the beam used in the target cell, the terminal (700) can perform UL / DL transmission / reception operations using the corresponding beam.
[0246] Likewise, when the terminal (700) performs UL / DL transmission / reception using the beam, if BWP information associated with each beam is given, the terminal can operate the beam on the BWP.
[0247] Additionally, if TA information is given, the terminal (700) can transmit the first UL message by applying the corresponding TA value.
[0248] HO can be considered complete when the terminal transmits an RRCReconfigurationComplete message using the RACH-less HO configuration and / or receives a MAC CE regarding contention resolution from the target cell after transmission.
[0249] Meanwhile, FIG. 8 is a flowchart illustrating a method of a base station according to an embodiment of the present disclosure. According to an embodiment of the present disclosure, the base station disclosed in FIG. 8 may be a base station including a source donor CU. For example, the operation of FIG. 8 may be an operation performed by the source donor CU of the base station. In step S800, the base station may determine a handover of the MT.
[0250] In step S810, after the HO is completed, the base station may receive a HO success message including information from the target donor CU. At this time, the information may include at least one of NCGI of CU2 (target gNB), PCI of target cell (under CU2), PLMN ID of target cell under CU2, and mIAB node ID and / or MT ID (an ID that can be uniquely distinguished among gNBs).
[0251] In step S820, the base station can determine the migration of the DU based on the above information. Based on the determination, when an F1 setup request message is transmitted from the DU of the base station to the target base station corresponding to the target donor CU, the F1 setup procedure can be performed. CU1 (the base station) can determine the possibility of RACH-less HO for the terminal by utilizing the cell information of the target logical DU configured from CU2 (i.e., the target donor CU of DU migration) from the mIAB DU.
[0252] And in step S830, the base station can determine whether the terminal will attempt RACH-less HO. At this time, the base station can transmit a HO request message including a RACH-less HO indication to the target donor CU and receive a HO request response message from the target donor CU.
[0253] The methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.
[0254] 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 the embodiments described in the claims or specification of the present invention.
[0255] 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 device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.
[0256] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), 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 invention 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 invention.
[0257] In the specific embodiments of the present invention described above, components included in the invention are expressed in the singular or plural form 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 invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.
[0258] While the detailed description of the present invention has described specific embodiments, it is clear that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.
Claims
1. A method performed by a mobile integrated access and backhaul (IAB) node in a wireless communication system, A step of initiating F1 setup with a target central unit (CU) by a target logical distributed unit (DU); A step of serving a terminal based on at least one cell activated by the target logical DU based on the F1 setup; and A method comprising: transmitting, by a source logical DU, information related to at least one cell activated by the target logical DU to a source CU; 2. In paragraph 1, A method characterized in that handover for the terminal is determined by the source CU that has received information related to at least one cell activated by the target logical DU.
3. In paragraph 1, A method characterized in that, by the target logical DU, a list including information related to at least one cell activated by the target logical DU is received from the target CU, and the at least one cell is activated based on the list.
4. In paragraph 2, Handover for the above terminal is: A method characterized in that it is performed from a cell corresponding to the source logical DU to a cell corresponding to the target logical DU.
5. In paragraph 1, The above serving steps are, A method characterized by being based on the completion of the F1 setup between the target logical DU and the target CU.
6. In paragraph 1, The above mobile IAB node, A method characterized by comprising the source logical DU, the target logical DU, and a mobile termination (MT).
7. In paragraph 1, Further comprising: a step of receiving information related to at least one cell activated by the target logical DU from the target CU by the source logical DU; A method characterized in that information related to at least one cell activated by the target logical DU is transmitted to the source CU by the source logical DU based on information related to at least one cell activated by the target logical DU received from the target CU.
8. In a mobile integrated access and backhaul (IAB) node in a wireless communication system, Transmitter and receiver; and Controlling the initiation of F1 setup with target central unit (CU) by target logical distributed unit (DU), Based on the above F1 setup, the terminal is controlled to be served based on at least one cell activated by the target logical DU, A mobile IAB node comprising a control unit for controlling transmission of information related to at least one cell activated by the target logical DU to the source CU through the transceiver unit by the source logical DU; 9. In paragraph 8, A mobile IAB node characterized in that handover for the terminal is determined by the source CU that has received information related to at least one cell activated by the target logical DU.
10. In paragraph 8, A mobile IAB node characterized in that it receives, by the target logical DU, a list including information related to at least one cell activated by the target logical DU from the target CU, and activates the at least one cell based on the list.
11. In paragraph 9, Handover for the above terminal is: A mobile IAB node characterized in that it is performed from a cell corresponding to the source logical DU to a cell corresponding to the target logical DU.
12. In paragraph 8, The serving of the above terminal is, A mobile IAB node characterized in that it is performed based on the completion of the F1 setup between the target logical DU and the target CU.
13. In paragraph 8, The above mobile IAB node, A mobile IAB node characterized by comprising the source logical DU, the target logical DU, and a mobile termination (MT).
14. In paragraph 8, The above control unit, A mobile IAB node characterized by controlling the transmission / reception unit to receive, from the target CU by the source logical DU, information related to at least one cell activated by the target logical DU.
15. In paragraph 14, A mobile IAB node characterized in that information related to at least one cell activated by the target logical DU is transmitted to the source CU by the source logical DU based on information related to at least one cell activated by the target logical DU received from the target CU.
Citation Information
Patent Citations
Associating IAB mt to IAB du at handover-target gnb
EP3780738A1
User equipment and base station involved in a handover
EP3799470A1
Communication control method
EP4178246A1
IAB-node handover in inter-CU migration, recursive f1 and RRC signaling aspects
WO2021262077A1
Wireless telecommunications system and method
WO2023011996A1
