Path switching

The enhancement of path switching procedures in 3GPP LTE and NR systems addresses the challenges of service continuity and handover failures by enabling informed decision-making based on target gNB capabilities and relay UE selection, ensuring effective inter-gNB path switching and service continuity.

WO2024237587A1PCT designated stage expired Publication Date: 2024-11-21LG ELECTRONICS INC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/006354
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-05-10
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current 3GPP LTE and New Radio (NR) systems face challenges in effectively supporting path switching, particularly in scenarios involving remote UE communication through a relay UE, where the candidate relay UE list may be included in handover failure messages, leading to issues with service continuity and path type determination during inter-gNB handovers.

Method used

The implementation enhances path switching procedures by allowing the target gNB to inform the source gNB about the success or failure of inter-gNB direct/indirect path switching, enabling the source gNB to determine a new target gNB and adjust the handover strategy, and introduces a candidate relay UE information list with criticality set to 'reject' to ensure proper path switching is performed.

Benefits of technology

This solution ensures service continuity by allowing the source gNB to adapt to target gNB capabilities and select appropriate relay UEs, preventing direct path switching when indirect paths are intended and ensuring proper handover execution, thereby improving the reliability of path switching operations in inter-gNB scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006354_21112024_PF_FP_ABST
    Figure KR2024006354_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A disclosure of the present disclosure provides a method of performing handover-related communication by a source base station. This method includes the steps of: receiving, from a UE, a report message including a measurement result related to at least one relay UE; determining a target path type for the UE; transmitting a handover request message to a first target base station; receiving a handover preparation failure message including a cause value from the first target base station; and re-determining a target path type of the UE.
Need to check novelty before this filing date? Find Prior Art

Description

Path switching

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR, meeting both urgent market needs and the longer-term requirements outlined by the ITU-R (ITU Radio communication sector) International Mobile Telecommunications (IMT)-2020 process. Furthermore, NR must be able to utilize any spectrum band, at least 13a and 13b0 GHz, that will remain available for wireless communications well into the future.

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). NR must be inherently forward-compatible.

[0005] In a situation where a Remote UE communicates with a network through a Relay UE, there is a problem that path switching is not effectively supported.

[0006] A list of candidate relay UEs may be included in the handover preparation failure message.

[0007] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0008] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0009] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0010] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0011] Figure 5 illustrates an example of the architecture of a UE-to-Network Relay.

[0012] Figure 6 illustrates the procedure involved in inter-gNB path switching from a direct path to an indirect path.

[0013] FIG. 7 illustrates a procedure related to inter-gNB path switching from an indirect path to an indirect path, according to one embodiment of the disclosure of the present specification.

[0014] Figures 8a and 8b illustrate procedures related to inter-gNB-CU switching from a direct path to an indirect path.

[0015] FIG. 9A and FIG. 9B illustrate a procedure when a target base station does not support inter-gNB path switching, according to one embodiment of the disclosure of the present specification.

[0016] FIG. 10A and FIG. 10B illustrate a procedure when a target base station cannot select a target relay UE from a candidate relay UE list, according to one embodiment of the disclosure of the present specification.

[0017] FIG. 11 illustrates a procedure for supporting service continuity for path switching from an indirect path to a direct path between inter-gNBs, according to one embodiment of the disclosure of the present specification.

[0018] FIG. 12 illustrates a procedure for supporting service continuity for path switching from a direct path to an indirect path between inter-gNBs, according to one embodiment of the disclosure of the present specification.

[0019] FIG. 13a and FIG. 13b illustrate a procedure for supporting service continuity in path switching from an inter-gNB indirect path to an indirect path, according to one embodiment of the disclosure of the present specification.

[0020] FIG. 14 is an example of a procedure for switching from an indirect path to a direct path according to one embodiment of the disclosure of the present specification.

[0021] FIG. 15 illustrates a procedure in which a direct path of a remote UE in RRC_CONNECTED state is switched to an indirect path according to one embodiment of the disclosure of the present specification.

[0022] FIG. 16 illustrates an example of a handover preparation procedure performed according to one embodiment of the disclosure of the present specification.

[0023] FIG. 17 illustrates an example of handover resource allocation according to one embodiment of the disclosure of the present specification.

[0024] FIG. 18A and FIG. 18B illustrate examples of a procedure for a source gNB to reselect a list of target cells and / or candidate relay UEs according to one embodiment of the disclosure of the present specification.

[0025] FIG. 19a and FIG. 19b illustrate an example of a procedure for a source gNB to re-determine path switching, according to an embodiment of the disclosure of the present specification.

[0026] FIG. 20 illustrates an example of a procedure according to one embodiment of the disclosure of the present specification.

[0027] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long-Term Evolution (LTE) is part of E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0028] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

[0029] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0030] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0031] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0032] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0033] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

[0034] Additionally, parentheses used herein may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0035] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0036] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0037] Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to the same or corresponding hardware blocks, software blocks, and / or functional blocks, unless otherwise indicated.

[0038] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0039] The 5G usage scenario shown in FIG. 1 is only an example, and the technical features of this specification can be applied to other 5G usage scenarios not shown in FIG. 1.

[0040] The three main requirement categories for 5G are (1) enhanced mobile broadband (eMBB), (2) massive machine type communication (mMTC), and (3) ultra-reliable and low latency communications (URLLC).

[0041] Referring to FIG. 1, a communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of a network of the communication system (1), but the implementation of the present disclosure is not limited to a 5G system and can be applied to future communication systems beyond the 5G system.

[0042] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

[0043] The wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0044] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving function, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

[0045] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). AI technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0046] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and a base station (200) and / or between base stations (200). Here, the wireless communication / connection can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D (Device-To-Device) communication), and base station-to-base station communication (150c) (e.g., relay, IAB (Integrated Access and Backhaul)). Through the wireless communication / connection (150a, 150b, 150c), the wireless devices (100a to 100f) and the base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of the various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present specification.

[0047] NR supports multiple numerologies, or subcarrier spacings (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0048] The NR frequency band can be defined by two types of frequency ranges (FR1 and FR2). The numerical values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range," and FR2 can mean the "above 6 GHz range," which can be called millimeter wave (mmW).

[0049] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0050] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 2 below. That is, FR1 may include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include unlicensed bands. Unlicensed bands may be used for various purposes, such as for communications for vehicles (e.g., autonomous driving).

[0051] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0052] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also Narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (Non-Bandwidth Limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PANs (Personal Area Networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0053] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0054] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

[0055] The first wireless device (100) may include at least one transceiver, such as a transceiver (106), at least one processing chip, such as a processing chip (101), and / or one or more antennas (108).

[0056] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0057] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0058] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

[0059] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). Each transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0060] The second wireless device (200) may include at least one transceiver, such as a transceiver (206), at least one processing chip, such as a processing chip (201), and / or one or more antennas (208).

[0061] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0062] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0063] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements code, instructions and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0064] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF unit. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0065] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Resource Control (RRC) layer, and a Service Data Adaptation Protocol (SDAP) layer). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs), one or more Service Data Units (SDUs), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0066] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a Memory Control Processor. One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer readable storage media and / or combinations thereof.One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0067] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0068] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0069] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0070] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0071] In the implementation of this specification, a UE can operate as a transmitter in the uplink and as a receiver in the downlink. In the implementation of this specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of this specification or to control a transceiver (106) to perform UE operations according to the implementation of this specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of this specification or to control a transceiver (206) to perform base station operations according to the implementation of this specification.

[0072] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0073] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0074] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0075] The UE (100) includes a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0076] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0077] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

[0078] A transceiver (106) is operably coupled to the processor (102) and transmits and / or receives a radio signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a radio frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a radio signal.

[0079] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0080] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0081] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

[0082] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0083] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0084] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0085] - AUSF (Authentication Server Function)

[0086] -AMF (Access and Mobility Management Function)

[0087] - DN (Data Network), for example, operator services, Internet access, or third-party services.

[0088] - USDF (Unstructured Data Storage Function)

[0089] - NEF (Network Exposure Function)

[0090] - I-NEF (Intermediate NEF)

[0091] - NRF (Network Repository Function)

[0092] - NSSF (Network Slice Selection Function)

[0093] - PCF (Policy Control Function)

[0094] - SMF (Session Management Function)

[0095] - UDM (Unified Data Management)

[0096] - UDR (Unified Data Repository)

[0097] - UPF (User Plane Function)

[0098] - UCMF (UE radio Capability Management Function)

[0099] - AF (Application Function)

[0100] - UE (User Equipment)

[0101] - (R)AN ((Radio) Access Network)

[0102] - 5G-EIR (5G-Equipment Identity Register)

[0103] - NWDAF (Network Data Analytics Function)

[0104] - CHF (CHarging Function)

[0105] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

[0106] - N3IWF (Non-3GPP InterWorking Function)

[0107] - TNGF (Trusted Non-3GPP Gateway Function)

[0108] - W-AGF (Wireline Access Gateway Function)

[0109] Figure 4 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0110] For clarity of the point-to-point diagram in Figure 4, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0111] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 4.

[0112] The 5G system architecture includes the following benchmarks:

[0113] - N1: Reference point between UE and AMF.

[0114] - N2: Reference point between (R)AN and AMF.

[0115] - N3: Reference point between (R)AN and UPF.

[0116] - N4: Reference point between SMF and UPF.

[0117] - N6: Reference point between UPF and data network.

[0118] - N9: Reference point between two UPFs.

[0119] The following benchmarks illustrate the interactions that exist between NF services in NF.

[0120] - N5: Reference point between PCF and AF.

[0121] - N7: Reference point between SMF and PCF.

[0122] - N8: Reference point between UDM and AMF.

[0123] - N10: Reference point between UDM and SMF.

[0124] - N11: Reference point between AMF and SMF.

[0125] - N12: Reference point between AMF and AUSF.

[0126] - N13: Reference point between UDM and AUSF.

[0127] - N14: Reference point between two AMFs.

[0128] - N15: Reference point between PCF and AMF for non-roaming scenarios, and reference point between PCF and AMF of visited network for roaming scenarios.

[0129] - N16: Reference point between two SMFs (in case of roaming, between the SMF of the visited network and the SMF of the home network)

[0130] - N22: Reference point between AMF and NSSF.

[0131] In some cases, two NFs may need to be interconnected to serve a UE.

[0132] < UE-to-Network Relay >

[0133] Figure 5 illustrates an example of the architecture of a UE-to-Network Relay.

[0134] Referring to FIG. 5, UE-to-Network Relay supports network connection of a remote UE.

[0135] The PC5 link is the interface between the UE and the UE-to-network relay. The Uu link is the interface between the UE-to-network relay and the base station.

[0136] If the UE has established a PC5 link with a UE-to-network relay, the UE is considered a remote UE.

[0137] A UE-to-Network Relay entity can provide network connectivity for remote UEs. UE-to-Network Relay can be used for both public safety services and commercial services (e.g., interactive services).

[0138] When a UE (e.g., a remote UE) successfully establishes a PC5 link to a UE-to-Network Relay, the UE (e.g., a remote UE) may be considered a Remote UE for that particular UE-to-Network Relay. The Remote UE may be located within NG-RAN coverage or outside NG-RAN coverage.

[0139] A UE-to-Network Relay can relay unicast traffic (UL and DL traffic) between a remote UE and the network. A UE-to-Network Relay must provide a general function capable of relaying all IP traffic.

[0140] For unicast traffic between Remote UEs and UE-to-Network Relays, one-to-one direct communication can be used.

[0141] An example of path switching is described with reference to FIGS. 6 and 7.

[0142] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0143] Figure 6 illustrates the procedure involved in inter-gNB path switching from a direct path to an indirect path.

[0144] An example of inter-gNB direct to indirect path switching is described. In the example of Fig. 6, at step 0, the Remote UE communicates with the source gNB via a direct path that performs direct communication. According to the example of Fig. 6, the path through which the UE communicates can be changed from a direct path between the Remote UE and the source gNB to an indirect path through which the Remote UE communicates with the target gNB via a relay UE.

[0145] For service continuity of Layer 2 (L2) UE to Network (U2N) Remote UE, the following procedures may be supported. When the L2 U2N Remote UE is in RRC_CONNECTED state with respect to another gNB, the procedure according to the example of Fig. 6 is used when switching from a direct path to an indirect path via an L2 U2N Relay UE.

[0146] For reference, the Remote UE described below can be used as a term with the same meaning as U2N Remote UE.

[0147] 0. Remote UE can exchange uplink (UL) data and / or downlink (DL) data with Source gNB.

[0148] 1. After measuring / discovering candidate L2 U2N relay UEs, L2 U2N remote UE reports measurements and Uu measurements for one or more candidate L2 U2N relay UEs to the source gNB:

[0149] - The L2 U2N Remote UE filters the appropriate L2 U2N Relay UEs based on the relay selection criteria before reporting. The L2 U2N remote UE should only report L2 U2N relay UE candidates that meet the upper layer criteria;

[0150] - The report includes at least the L2 U2N relay UE ID, the serving cell ID of the L2 U2N relay UE, and sidelink measurement quantity information. SD-RSRP is used as the sidelink measurement quantity.

[0151] 2. The source gNB decides to trigger a path switch of the L2 U2N remote UE to an indirect path of the target gNB based on the measurement report and Radio Resource Management (RRM) information.

[0152] 3. To enable the target side to prepare for a path switch, the source gNB sends a HANDOVER REQUEST message to the target gNB. The handover request message includes a list of candidate target relay UE IDs belonging to a cell and the remote UE L2 ID.

[0153] 4. The target gNB can perform admission control.

[0154] 5. The Target gNB selects one Target Relay UE from the list of candidate Relay UEs provided by the Source gNB. To configure the relay, including the local ID and L2 ID of the L2 U2N Remote UE, Uu Relay RLC channel configuration for relaying, PC5 Relay RLC channel configuration, and bearer mapping configuration, the Target gNB sends an RRCReconfiguration message to the L2 U2N Relay UE.

[0155] 6. The target gNB sends a HANDOVER REQUEST ACKNOWLEDGE message containing new RRC settings for the L2 U2N remote UE to the source gNB.

[0156] 7. The source gNB sends an RRCReconfiguration message to the L2 U2N Remote UE. The RRCReconfiguration message contains at least the L2 U2N Relay UE ID, the Remote UE's local ID, the PC5 Relay RLC channel configuration for relay traffic, and the associated Uu end-to-end radio bearer(s). After receiving the RRCReconfiguration message from the source gNB, the L2 U2N remote UE stops user plane and control plane transmissions over the direct path.

[0157] 8. The source gNB sends the SN STATUS TRANSFER message to the target gNB. It conveys the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status (i.e., in case of RLC AM) of the DRB of the L2 U2N Remote UE for which PDCP status preservation is applied.

[0158] 9. The L2 U2N remote UE establishes a PC5 connection with the L2 U2N relay UE.

[0159] 10. The L2 U2N remote UE sends an RRCReconfigurationComplete message to the target gNB through the L2 U2N relay UE.

[0160] 11. The data path is switched from a direct path to an indirect path via a target L2 U2N relay UE between the L2 U2N remote UE and the target gNB.

[0161] 12. The target gNB sends a UE context release message to the source gNB to indicate the success of the path switching.

[0162] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0163] FIG. 7 illustrates a procedure related to inter-gNB path switching from an indirect path to an indirect path, according to one embodiment of the disclosure of the present specification.

[0164] An example of inter-gNB indirect to indirect path switching is described. In the example of Fig. 7, at step 0, a remote UE communicates with a source gNB based on an indirect path via a source relay UE. According to the example of Fig. 7, the path through which the remote UE communicates can be changed from an indirect path with the source gNB via the source relay UE to an indirect path with the target gNB via the target relay UE.

[0165] For service continuity between gNBs of L2 U2N Remote UEs connected to an indirect path, a procedure for switching to another indirect path via a target L2 U2N Relay UE in RRC_CONNECTED state to another gNB may be used.

[0166] 1. After measuring / discovering candidate L2 U2N relay UEs, L2 U2N remote UE reports measurements and Uu measurements for one or more candidate L2 U2N relay UEs to the source gNB:

[0167] - The L2 U2N Remote UE filters the appropriate L2 U2N Relay UEs based on the relay selection criteria before reporting. The L2 U2N remote UE should only report L2 U2N relay UE candidates that meet the upper layer criteria;

[0168] - The report includes at least the L2 U2N relay UE ID, the serving cell ID of the L2 U2N relay UE, and sidelink measurement quantity information. SD-RSRP is used as the sidelink measurement quantity.

[0169] 2. The source gNB decides to trigger the L2 U2N remote UE to switch to an indirect path to another gNB.

[0170] 3. To prepare for a path switch on the target side, the source gNB sends a HANDOVER REQUEST message to the target gNB. The handover request message includes the remote UE L2 ID and a list of candidate target relay UE IDs belonging to a cell.

[0171] 4. The target gNB can perform admission control.

[0172] 5. The Target gNB selects one Target Relay UE from the list of candidate Relay UEs provided by the Source gNB. The Target gNB sends an RRCReconfiguration message to the L2 U2N Relay UE for relay configuration, which includes the Local ID and L2 ID of the L2 U2N Remote UE, Uu Relay RLC channel and PC5 Relay RLC channel configuration for relay, and bearer mapping configuration.

[0173] 6. The target gNB sends a HANDOVER REQUEST ACKNOWLEDGE message containing new RRC settings for the L2 U2N Remote UE to the source gNB.

[0174] 7. The source gNB sends an RRCReconfiguration message to the L2 U2N Remote UE. The RRCReconfiguration message may include at least the target L2 U2N Relay UE ID, the local ID of the Remote UE, the PC5 Relay RLC channel configuration for relay traffic, and the associated end-to-end Uu radio bearer. After receiving the RRCReconfiguration message from the source gNB, the L2 U2N remote UE stops user plane and control plane transmissions via the (source) indirect path.

[0175] 8. It can be performed in the same manner as step 8 of Fig. 6.

[0176] 9. The L2 U2N remote UE establishes a PC5 connection to the target L2 U2N relay UE.

[0177] 10. The L2 U2N remote UE sends an RRCReconfigurationComplete message to the target gNB through the target L2 U2N relay UE.

[0178] 11. The data path is switched to an indirect path between the L2 U2N remote UE and the target gNB via the target L2 U2N relay UE.

[0179] 12. The target gNB sends a UE CONTEXT RELEASE message to the source gNB to notify the successful path switching.

[0180] 13. The source gNB sends an RRCReconfiguration message to the source L2 U2N Relay UE to re-establish the connection between the source L2 U2N Relay UE and the source gNB. The RRCReconfiguration message to the source L2 U2N Relay UE can be sent at any time after step 7, depending on the source gNB implementation (e.g., to de-establish Uu Relay RLC channels and PC5 Relay RLC channels for relay, and to establish bearer mapping related to L2 U2N Remote UE).

[0181] 14. The AS layer of the L2 U2N Relay UE or L2 U2N Remote UE may indicate to upper layers to release the PC5 unicast link after receiving the RRCReconfiguration message from the source gNB. The timing of the link release depends on the UE implementation.

[0182] With reference to the examples of FIGS. 8a and 8b, inter-gNB-CU switching from a direct path to an indirect path is described.

[0183] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0184] Figures 8a and 8b illustrate procedures related to inter-gNB-CU switching from a direct path to an indirect path.

[0185] An example of a procedure for switching from a UE direct path to an indirect path and performing a gNB-CU change in a U2N remote is described.

[0186] 1. Uu measurement setup and measurement reporting signaling are performed between the U2N Remote UE and the source gNB-CU to evaluate both relay link measurements and Uu link measurements. After the U2N Remote UE measures / discovers candidate U2N relay UEs, it can report Uu measurement results to one or more candidate U2N relay UEs.

[0187] 2. The source gNB-CU decides to switch the direct path of the U2N remote UE to an indirect path with one of the candidate U2N relay UEs served by the same target cell in another gNB.

[0188] 3. The source gNB-CU sends a HANDOVER REQUEST message to the target gNB-CU. The handover request message may include a list of candidate U2N relay UEs.

[0189] 4. The target gNB-CU decides to accept an indirect path switch to the target U2N relay UE among the candidate U2N relay UEs.

[0190] 5. If the target U2N relay UE is in RRC_CONNECTED state, reconfiguration to the target U2N relay UE is performed among the target U2N relay UE, the target gNB-DU, and the target gNB-CU. The target gNB-CU assigns a local ID to the U2N Remote UE. The target gNB-CU sends an RRCReconfiguration message to the target U2N relay UE. If the target U2N relay UE is in RRC_IDLE / INACTIVE state, this step is skipped, and configuration for the target U2N relay UE is performed in step 15.

[0191] 6. The target gNB-CU sends a UE CONTEXT SETUP REQUEST message (e.g., including at least the path switch configuration) to the target gNB-DU for the U2N Remote UE.

[0192] 7. The target gNB-DU responds to the gNB-CU with a target UE CONTEXT SETUP RESPONSE message.

[0193] 8. The target gNB-CU responds to the source gNB-CU by sending a handover request acknowledgement message containing an RRCReconfiguration message. The contents of the RRCReconfiguration message may include at least the path switch configuration, PC5 RLC channel configuration for relay traffic, bearer mapping, and the associated radio bearer.

[0194] 9. To transmit a handover command to the U2N Remote UE and instruct the U2N Remote UE to stop transmitting data, the source gNB-CU transmits a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU.

[0195] 10. The source gNB-DU sends an RRCReconfiguration message to the U2N Remote UE. After receiving the RRCReconfiguration message from the source gNB, the U2N Remote UE stops transmitting UP and CP over Uu.

[0196] 11. The source gNB-DU sends a UE CONTEXT MODIFICATION RESPONSE message to the source gNB-CU.

[0197] 12. The source gNB-CU sends the SN STATUS TRANSFER message to the target gNB-CU.

[0198] 13. Data forwarding can be performed from a source gNB-CU to a target gNB-CU.

[0199] 14. The U2N remote UE establishes a PC5 connection with the target U2N relay UE.

[0200] 15. The U2N Remote UE completes the path switching procedure by sending an RRCReconfigurationComplete message to the target gNB-DU via the target U2N Relay UE. If the target U2N Relay UE is in RRC_IDLE / INACTIVE state when the RRCReconfigurationComplete message is received, upon receiving the RRCReconfigurationComplete message, the RRC setup / resume procedure for the target U2N Relay UE is triggered first, causing it to enter the RRC_CONNECTED state.

[0201] 17. A path switching procedure is performed to switch the DL data path to the target gNB-CU and establish an NG-C interface instance toward the target gNB-CU.

[0202] 18. The target gNB-CU sends a UE CONTEXT RELEASE message to the source gNB-CU.

[0203] 19. To release the UE context of the U2N remote UE from the source gNB-DU, the source gNB-CU may initiate an F1 UE context release procedure.

[0204] In the prior art, path switching in an inter-gNB situation and indirect-to-indirect path switching were not considered. During the handover process, the source gNB determines in advance whether the target gNB should use the direct path or the indirect path for the remote UE. If the source gNB determines that the indirect path should be used, the source gNB can transmit a HANDOVER REQUEST message to the target gNB. In this case, the HANDOVER REQUEST message includes a list of candidate relay UEs that can be used as indirect paths. The target gNB can select a target relay UE based on the candidate relay UE list received from the source gNB and establish an indirect path to service the remote UE.

[0205] However, if the target gNB does not support inter-gNB direct / indirect-to-indirect path switching, there is a problem that it ignores the candidate relay UE list sent by the source gNB and applies legacy handover. That is, instead of establishing an indirect path with a specific relay UE among the relay UEs included in the candidate relay UE list, the target gNB can connect the remote UE and the target gNB through the target Uu cell included in the HANDOVER REQUEST message. In this situation, switching to the direct path is applied, not switching to the indirect path determined by the source gNB. In this situation, the target gNB ignores the target path type determined by the source gNB, and the source gNB does not know that the target gNB has decided to switch to the direct path.

[0206] Furthermore, even if the target gNB supports inter-gNB direct / indirect-to-indirect path switching, there may be a situation where no suitable relay UE is available to service the remote UE in the candidate relay UE list sent by the source gNB. In this situation, even if the target gNB aborts the handover procedure, the source gNB cannot determine the reason for the abort. This may lead to the source gNB re-requesting a handover for the same path type to the target gNB.

[0207] In other words, path switching of remote UEs may occur during the handover process. However, specific operations related to path switching and indirect-to-indirect path switching in inter-gNB situations where the gNB changes have not been considered in the past.

[0208] For example, a HANDOVER REQUEST message transmitted by a source base station (e.g., gNB) to a target base station (e.g., gNB) may include an IE containing a candidate relay UE list that can be used as an indirect path. Conventionally, the criticality of this IE is defined as "ignore." The target base station may not support inter-gNB direct / indirect-to-indirect path switching. In this case, the conventional approach has the problem that the target base station may ignore the candidate relay UE list transmitted by the source base station and perform a handover.

[0209] In addition, according to the prior art, there is a problem in that if the target base station cannot find a relay UE to service the remote UE within the candidate relay UE list, the target base station stops the handover without notifying the source base station.

[0210] As shown in the example below, service continuity needs to be provided through path switching between different gNBs for L2 U2N remote UEs.

[0211] For example, a mechanism needs to be specified to improve service continuity for single-hop Layer-2 UE-to-network relays for the following scenarios:

[0212] A. Inter-gNB indirect-to-direct path switching (i.e., switching from "remote UE <-> relay UE A <-> gNB X" to "remote UE <-> gNB Y")

[0213] B. Inter-gNB direct-to-indirect path switching (i.e., switching from "remote UE <-> gNB X" to "remote UE <-> relay UE A <-> gNB Y")

[0214] C. Intra-gNB indirect-to-indirect path switching (i.e., switching from "remote UE <-> relay UE A <-> gNB X" to "remote UE <-> relay UE B <-> gNB X")

[0215] D. Inter-gNB indirect-to-indirect path switching (i.e., switching from "remote UE<-> relay UE A<-> gNB X" to "remote UE<-> relay UE B<-> gNB Y")

[0216] According to the prior art, service continuity for L2 U2N remote UEs can only be provided in an intra-gNB situation. That is, only direct-to-indirect path switching or indirect-to-direct path switching can be provided in an intra-gNB situation.

[0217] Therefore, there is a problem that path switching and indirect-to-indirect path switching cannot be performed in an inter-gNB situation in the past. According to various examples disclosed in the present specification, path switching and indirect-to-indirect path switching in an inter-gNB situation can be supported.

[0218] Based on the handover process, the remote UE may be served by the target gNB. In this case, during the handover process, the source gNB may predetermine whether the target gNB will use a direct path or an indirect path for the remote UE.

[0219] For example, the source gNB may determine that an indirect path should be used from the target gNB. In this case, the source gNB may send a HANDOVER REQUEST message to the target gNB. The source gNB may include a list of candidate relay UEs that can be used as the indirect path in the HANDOVER REQUEST message. The target gNB may select the target relay UE from the list of candidate relay UEs received from the source gNB. Based on the target relay UE, the target gNB configures an indirect path to serve the corresponding remote UE.

[0220] However, the target gNB may not support inter-gNB direct / indirect-to-indirect path switching. In this case, according to the prior art, the target gNB may ignore the candidate relay UE list transmitted by the source gNB and apply a legacy handover. In this case, the target gNB may not establish an indirect path with one of the relay UEs in the candidate relay UE list, and the remote UE and the target gNB may be directly connected through the target Uu cell included in the HANDOVER REQUEST message. In this case, there is a problem that switching to the direct path is applied instead of switching to the indirect path determined by the source gNB. In other words, there is a problem that the target gNB violates the target path type determined by the source gNB. However, there is a problem that the source gNB is unaware that the target gNB has decided to switch to the direct path.

[0221] Even if the target gNB supports inter-gNB direct / indirect-to-indirect path switching, there are cases where it cannot select an appropriate relay UE. For example, the target gNB may not have a suitable relay UE within the candidate relay UE list sent by the source gNB to service the remote UE. In this situation, the target gNB may abort the handover procedure. However, the source gNB cannot know why the target gNB aborted the handover procedure. As a result, the source gNB may request the same type of handover again from the target gNB.

[0222] Accordingly, various examples of the disclosure herein aim to address the various problems described above. The disclosure herein enables the target gNB to inform the source gNB of whether path switching has been successfully performed and / or the reason for the handover being aborted. For example, the target gNB can clearly inform the source gNB that inter-gNB direct / indirect-to-indirect path switching has not been performed properly. Based on this, a method for the source gNB to determine a new target is described.

[0223] Various examples of the disclosure of this specification provide methods for a target gNB to notify a source gNB that inter-gNB direct / indirect-to-indirect path switching is not properly performed during a handover process. For example, the target gNB may receive a HANDOVER REQUEST message from the source gNB, which includes a list of candidate relay UEs. If the target gNB does not support inter-gNB direct / indirect-to-indirect path switching, the target gNB may abort the ongoing handover procedure. In this case, the target gNB may notify the source gNB that it does not support inter-gNB direct / indirect-to-indirect path switching by transmitting a new cause value or indication.

[0224] The target gNB may receive a HANDOVER REQUEST message from the source gNB, including a list of candidate relay UEs. In this case, the target gNB may not be able to select a suitable relay UE within the list that can service the remote UE. In this case, the target gNB may abort the ongoing handover procedure and notify the source gNB of the failure to select a suitable relay UE by sending a new cause value or indication.

[0225] Newly defined service operations may be used for some or all of the service operations between Core NFs according to various examples of the disclosure in this specification. In addition, newly defined NG messages may be used for some or all of the NG messages between AMF and NG-RAN according to various examples of the disclosure in this specification. In addition, newly defined RRC messages may be used for some or all of the RRC messages between NG-RAN and UE according to various examples of the disclosure in this specification.

[0226] In the procedures according to the various examples of the disclosure of this specification, certain steps may be performed concurrently / in parallel or may be performed in a reversed order.

[0227] The names of indication or parameter information according to various examples of the disclosure of this specification are examples and may be interpreted as other names for the proposed procedure / purpose / method.

[0228] Referring to examples of FIGS. 9a and 9b, a procedure will be described when a target base station (e.g., Target NG-RAN, target gNB, etc.) does not support inter-gNB path switching for a remote UE.

[0229] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0230] FIG. 9A and FIG. 9B illustrate a procedure when a target base station does not support inter-gNB path switching, according to one embodiment of the disclosure of the present specification.

[0231] For reference, in the various examples of the disclosure of this specification, target base station, target gNB, and target NG-RAN may all be used as terms with the same meaning.

[0232] Figures 9a and 9b illustrate examples of how the target gNB notifies the source gNB of a case where the target gNB itself does not understand / perform the IE related to Rel-18 inter-gNB path switching for remote UE, or where the target gNB understands the IE but does not support it. By quickly notifying the source gNB of this fact, the target gNB enables the source gNB to select a new target gNB.

[0233] Step 0: The remote UE receives DL data and transmits UL data based on a direct path through the source gNB.

[0234] Step 1: The remote UE can receive the measurement configuration from the source gNB. Based on the measurement configuration, the remote UE can perform measurement / discover operations on the surrounding relay UE. The remote UE reports the measurement / discover results to the source gNB. For example, the remote UE can send a report message containing the measurement / discover results to the source gNB. The result may include the L2 U2N Relay UE ID, serving cell ID, and sidelink measurement results of the candidate relay UE located nearby.

[0235] Step 2: Based on the measurement result received from the remote UE in Step 1, the source gNB may decide to handover the remote UE to the target gNB #1. The source gNB may determine the target path type. For example, the source gNB may decide whether to have the remote UE use a direct path through the Uu cell of the target gNB #1 or an indirect path through a relay UE located within the cell of the target gNB #1. The examples in FIGS. 9A and 9B illustrate an example in which the source gNB decides to service the remote UE through the indirect path from the target gNB #1.

[0236] NOTE: The order in which the source gNB determines the target gNB, target cell, and target path type is up to the gNB implementation.

[0237] Step 3: The source gNB can send a handover request message to the target gNB #1. For example, based on the measurement result received from the remote UE in Step 1, the source gNB can determine a list of candidate relay UEs that can be utilized as an indirect path from the target gNB #1. The source gNB sends a HANDOVER REQUEST message containing the list of candidate relay UEs to the target gNB #1. The source gNB can set the criticality of the IE containing the list of candidate relay UEs in the HANDOVER REQUEST message to reject.

[0238] Step 4: The source gNB sets the criticality of the IE containing the list of candidate relay UEs in the HANDOVER REQUEST message to reject. Target gNB #1 does not have the capability to understand / perform the IE. Accordingly, target gNB #1 aborts the handover procedure for the remote UE and notifies the source gNB of this abort by sending a HANDOVER PREPARATION FAILURE message. At this time, target gNB #1 may include a cause value or indication in the HANDOVER PREPARATION FAILURE message indicating that it cannot understand / perform the IE containing the list of candidate relay UEs.

[0239] NOTE: While the target gNB may understand the IE containing the list of candidate relay UEs in the HANDOVER REQUEST message, it may not be able to perform a handover to the target relay UE in the candidate relay UE list because it does not support inter-gNB path switching for remote UEs. In this case, the target gNB may still send the cause value or indication defined above to the source gNB.

[0240] NOTE: To avoid interruption of the handover procedure, an operation may be performed to exchange whether or not inter-gNB path switching for remote UE can be supported between gNBs using the Xn Setup procedure, Xn Configuration update procedure, etc. In this case, if the source gNB decides to switch to an indirect path, only gNBs that support inter-gNB path switching for remote UE can be considered when selecting the target gNB.

[0241] Step 5: The source gNB may receive a cause value or indication indicating that it cannot understand / perform the IE containing the list of candidate relay UEs in Step 4. The source gNB may determine that handover to Target gNB #1 is not possible and may select a new target gNB. Therefore, the source gNB may perform one or more of target gNB selection, target cell selection, and target path type selection (e.g., Step 2) again. The source gNB may decide to switch paths to the new gNB's direct path or indirect path.

[0242] In FIG. 9a and FIG. 9b, it is assumed that the Source gNB has decided in Step 5 to serve the remote UE through an indirect path from Target gNB #2.

[0243] NOTE: Step 5 may be performed even if the target gNB can understand the IE containing the list of candidate relay UEs in the HANDOVER REQUEST message, but cannot perform a handover to a target relay UE in the candidate relay UE list because it does not support inter-gNB path switching for remote UEs. For example, the source gNB may perform Step 5 based on the cause value or indication received in Step 4.

[0244] Step 6: The Source gNB can send a HANDOVER REQUEST message containing a list of candidate relay UEs to the Target gNB #2. For example, the Source gNB can determine a list of candidate relay UEs that can be used as an indirect path to the Target gNB #2 based on the measurement results received from the remote UE in Step 1. The Source gNB forwards the HANDOVER REQUEST message containing the list of candidate relay UEs to the Target gNB #2.

[0245] Step 7: Target gNB #2 can select a target relay UE. Target gNB #2 can support inter-gNB path switching for remote UEs. Target gNB #2 can understand / process the IE containing the list of candidate relay UEs in the HANDOVER REQUEST message. Therefore, Target gNB #2 can select a relay UE from the list of candidate relay UEs received in Step 6 to assist in DL / UL data transmission for the remote UE.

[0246] Step 8: Target gNB #2 can transmit the information required for the relay UE selected in Step 7 to serve the remote UE to the selected relay UE through the RRC Reconfiguration procedure.

[0247] Step 9: Target gNB #2 may send a HANDOVER REQUEST ACK message to the source gNB. For example, the HANDOVER REQUEST ACK message may be sent to the source gNB, including an RRC Reconfiguration message containing information necessary for the Remote UE to access Target gNB #2 via the relay UE selected in Step 7.

[0248] Step 10: The source gNB forwards the RRC Reconfiguration message received in Step 9 to the remote UE.

[0249] Step 11: Source gNB sends SN STATUS TRANSFER message to Target gNB #2.

[0250] Step 12: The remote UE establishes a PC5 connection with the relay UE based on the RRC Reconfiguration message received in Step 10.

[0251] Step 13: The Remote UE generates an RRC Reconfiguration Complete message in response to the RRC Reconfiguration message received in Step 10. The Remote UE can complete the handover procedure by forwarding the RRC Reconfiguration Complete message to Target gNB #2 via the relay UE.

[0252] Step 14: DL / UL data is exchanged through the relay UE located within the cell of Target gNB #2.

[0253] Referring to examples of FIGS. 10a and 10b, a procedure is described when the target NG-RAN cannot select a target relay UE from a list of candidate relay UEs to support the remote UE.

[0254] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0255] FIG. 10A and FIG. 10B illustrate a procedure when a target base station cannot select a target relay UE from a candidate relay UE list, according to one embodiment of the disclosure of the present specification.

[0256] The target gNB of FIGS. 10A and 10B can support Rel-18 inter-gNB path switching for remote UEs. The examples of FIGS. 10A and 10B illustrate a case where the target gNB cannot select a target relay UE capable of servicing the remote UE from the candidate relay UE list sent by the source gNB. The target gNB can quickly notify the source gNB that it cannot select a target relay UE. Accordingly, the source gNB can determine a new target gNB, target cell, target path type, or candidate relay UE list.

[0257] Below, the differences between FIGS. 10a and 10b and FIGS. 9a and 9b are explained with reference to examples of FIGS. 10a and 10b.

[0258] Step 0~1: Performed in the same manner as steps 0~1 of Figs. 9a and 9b.

[0259] Step 2: Based on the measurement result received from the remote UE in Step 1, the source gNB may decide to handover the remote UE to the target gNB #1. The source gNB may determine the target path type. For example, the source gNB may decide whether to have the remote UE use a direct path through the Uu cell of the target gNB #1 or an indirect path through a relay UE located within the cell of the target gNB #1. The examples in FIGS. 10A and 10B illustrate an example in which the source gNB decides to service the remote UE through the indirect path from the target gNB #1.

[0260] NOTE: The order in which the source gNB determines the target gNB, target cell, and target path type is up to the gNB implementation.

[0261] Step 3: It is performed in the same manner as step 3 of Figs. 9a and 9b.

[0262] Step 4: Target gNB #1 can select a target relay UE. Target gNB #1 supports inter-gNB path switching for remote UEs. Target gNB #1 can understand / execute the IE containing the list of candidate relay UEs in the HANDOVER REQUEST message. Therefore, Target gNB #1 can perform the operation of selecting a relay UE to assist in DL / UL data transmission for the remote UE from the list of candidate relay UEs received in Step 3. However, Target gNB #1 may fail to select a target relay from the list of candidate relay UEs if the RRC state of the candidate relay UE is RRC_IDLE / RRC_INACTIVE, if the load of each candidate relay UE is severe enough to make it difficult to service the remote UE, or if the Uu link quality between the candidate relay UE and target gNB #1 is poor.

[0263] Step 5: If Target gNB#1 fails to select a target relay in Step 4, Target gNB#1 may abort the handover procedure for the remote UE. Target gNB#1 may notify the source gNB that the handover procedure has been aborted by sending a HANDOVER PREPARATION FAILURE message to the source gNB. In this case, Target gNB#1 may include a cause value or indication in the HANDOVER PREPARATION FAILURE message that it failed to select a target relay based on the list of candidate relay UEs. Alternatively, Target gNB#1 may include a cause value or indication in the HANDOVER PREPARATION FAILURE message that all relay UEs in the candidate relay UE list are not suitable to serve the remote UE from the perspective of Target gNB#1.

[0264] Step 6: Based on the cause value or indication received in Step 5, the source gNB may perform one or more of target gNB selection, target cell selection, and target path type selection (e.g., Step 2), which may result in one or more of the following:

[0265] (a) The source gNB may determine a new target gNB when it recognizes that handover to Target gNB #1 is impossible. For example, there may be cases such as i) when direct path switching to Target gNB #1 is impossible (e.g., when no Uu cell belonging to Target gNB #1 provides adequate radio quality, or when the Uu cell belonging to Target gNB #1 cannot be determined as the target because the cell does not support S-NSSAI for the remote UE, etc.), ii) when it is difficult to establish a new list other than the candidate relay UE list established / determined in Step 3 for indirect path switching to Target gNB #1. In this case, the source gNB may determine a new target gNB when it recognizes that handover to Target gNB #1 is impossible.

[0266] (b) The source gNB can still perform a handover to the target gNB #1, but can decide to perform a direct path switching. For example, it is difficult to set up a new list other than the candidate relay UE list set / determined in Step 3 for indirect path switching to the target gNB #1. However, there may be a cell among the Uu cells belonging to the target gNB #1 that is suitable for serving the remote UE. In this case, the source gNB can determine that cell as the target cell and notify the target gNB #1 of the direct path switching (i.e., legacy handover).

[0267] (c) The source gNB may maintain the handover and indirect path switching decisions to Target gNB #1, but may select a new target cell and / or candidate relay UE list. For example, the source gNB may configure / determine a new list other than the candidate relay UE list configured / determined in Step 3. For example, the source gNB may determine that serving the Remote UE through a Relay UE belonging to the list is better than serving it through a Uu cell belonging to the target gNB #1 or a Uu cell or candidate relay UE belonging to another neighboring gNB. This may be the case, for example, when the radio quality of the PC5 link between the Remote UE and the Candidate relay UE is better, or when connecting via a direct path through the Uu cell, the radio quality of the Uu link is poor, etc. The source gNB may maintain the handover and indirect path switching decisions to Target gNB #1, but may select a new target cell and / or candidate relay UE list.

[0268] Alternatively, if a HANDOVER PREPARATION FAILURE message is received from Target gNB#1 as in Step 5, it is also possible to immediately execute (a), (b), or (c) by the source gNB implementation or operator's pre-configuration.

[0269] In the examples of FIGS. 10a and 10b, it is assumed that the Source gNB has decided in Step 6 to serve the remote UE through an indirect path from Target gNB #2.

[0270] Step 7: The Source gNB can send a HANDOVER REQUEST message containing a list of candidate relay UEs to the Target gNB #2. For example, the Source gNB can determine a list of candidate relay UEs that can be used as an indirect path to the Target gNB #2 based on the measurement results received from the remote UE in Step 1. The Source gNB forwards the HANDOVER REQUEST message containing the list of candidate relay UEs to the Target gNB #2.

[0271] NOTE: Depending on the result of Step 6, the HANDOVER REQUEST message may be delivered to Target gNB #1 instead of Target gNB #2.

[0272] Step 8: Target gNB #2 can select a target relay UE. Target gNB #2 can support inter-gNB path switching for remote UEs. Target gNB #2 can understand / process the IE containing the list of candidate relay UEs in the HANDOVER REQUEST message. Therefore, Target gNB #2 can select a relay UE from the list of candidate relay UEs received in Step 7 to assist in DL / UL data transmission for the remote UE.

[0273] Step 9: Target gNB #2 can transmit the information required for the relay UE selected in Step 8 to serve the remote UE to the selected relay UE through the RRC Reconfiguration procedure.

[0274] Step 10: Target gNB #2 may send a HANDOVER REQUEST ACK message to the source gNB. For example, the HANDOVER REQUEST ACK message may be sent to the source gNB, including an RRC Reconfiguration message containing information necessary for the Remote UE to access Target gNB #2 via the relay UE selected in Step 8.

[0275] Step 11: The source gNB forwards the RRC Reconfiguration message received in Step 10 to the remote UE.

[0276] Step 12: Source gNB sends SN STATUS TRANSFER message to Target gNB #2.

[0277] Step 13: The remote UE establishes a PC5 connection with the relay UE based on the RRC Reconfiguration message received in Step 11.

[0278] Step 14: The Remote UE generates an RRC Reconfiguration Complete message in response to the RRC Reconfiguration message received in Step 11. The Remote UE can complete the handover procedure by forwarding the RRC Reconfiguration Complete message to Target gNB #2 via the relay UE.

[0279] Step 15: Can be performed in the same manner as step 14 of the examples of FIGS. 9a and 9b.

[0280] In the examples of FIGS. 9A and 9B and 10A and 10B above, operations based on inter-gNB direct-to-indirect path switching are described. However, these are merely examples, and the scope of the disclosure of this specification is not limited to inter-gNB direct-to-indirect path switching. Various examples disclosed in this specification are also applicable to inter-gNB indirect-to-indirect path switching situations.

[0281] Below, examples to which various examples of the disclosure of this specification are applied are described.

[0282] In the prior art, a list of candidate relay UEs was introduced via XnAP and NGAP. However, it was not specified whether the list of candidate relay UEs was an ordered list. Furthermore, considering gNBs that do not support service continuity for U2N relay, the significance of this new IE (i.e., the list of candidate relay UEs) requires further discussion. Furthermore, the overall path switching procedure between gNBs should be further reflected.

[0283] Describes details about the candidate relay UE list.

[0284] In the prior art, it is not determined whether the list of candidate relay UEs is a sorted list based on the measurement reports of remote UEs for the candidate relay UEs. If the source gNB provides measurement information of the remote UEs to the target gNB, the target gNB may make a better decision based on its full knowledge of the relay UEs (e.g., the PC5 measurement results of the candidate relay UEs of the source gNB, the Uu measurement results of the candidate relay UEs, and the current RRC state and load state of the candidate relay UEs). However, we will not discuss further whether the source gNB provides the measurement results for the list of candidate relay UEs to the target gNB.

[0285] However, even if the source gNB does not provide the measurement results of the remote UE to the target gNB, the ordered list of candidate relay UEs specified by the source gNB can still help the target gNB determine the target relay selection. Typically, the target gNB selects a target relay from the candidate relay list of the source gNB based on several criteria, such as the signal strength of the Uu link (e.g., the link between the remote UE and the target gNB), the current RRC state of the candidate relay UE, and the load status. If the candidate relay UEs in the list have similar aspects (e.g., similar Uu link signal strength and identical RRC states), the target gNB can consider the order provided by the source gNB when making the final decision. If the source gNB orders the candidate relay UEs based on the PC5 measurement results of the remote UE, the target gNB can assume that it can select the candidate relay UE with the best signal strength of the PC5 link (e.g., the link between the remote UE and the relay UE). Therefore, it may be advantageous to provide the target gNB with an ordered list of candidate relay UEs.

[0286] First example of the proposal: The list of candidate relay UEs may be an ordered list based on measurement reports of remote UEs for the candidate relay UEs.

[0287] A Candidate Relay UE Information List IE may be introduced in the XnAP Handover Request message. According to the prior art, the criticality of this new IE (i.e., the Candidate Relay UE Information List IE) is "ignore".

[0288] Therefore, if the source gNB sends this candidate relay UE information list IE to a target gNB that does not support service continuity for U2N relay, the target gNB ignores this IE. In this case, even if the source gNB decides to perform path switching from the direct path to the indirect path or from the indirect path to the indirect path, there is a problem that the target gNB performs a handover to the direct cell, not the target relay UE. Since the decision result related to target relay selection (e.g., the selected relay UE ID) is not included in the XnAP HANDOVER REQUEST ACKNOWLEDGE message, there is a problem that the source gNB cannot recognize the handover to the direct cell.

[0289] Therefore, to avoid such issues, the disclosure of this specification proposes to set the criticality of the Candidate Relay UE Information List IE to "reject". Similar to the XnAP case, the criticality of the Candidate Relay UE Information List IE in the Source NG-RAN Node-Target NG-RAN Node Transparent Container IE is set to "reject".

[0290] Second example of the proposal: The importance of the Candidate Relay UE Information List IE included in the XnAP Handover Request message is set to "Reject". The importance of the Candidate Relay UE Information List IE included in the Transparent Container IE via NGAP from the source NG-RAN node to the target NG-RAN node is set to "Reject".

[0291] Hereinafter, a procedure for supporting service continuity will be described with reference to examples of FIGS. 11 to 13a and 13b.

[0292] Describes the overall procedure for supporting L2 U2N service continuity.

[0293] For the inter-gNB path switch cases (ie, Scenario A, B and D), RAN3 can capture the overall procedures to support the Rel-18 service continuity for L2 U2N relay in TS 38.300 based on the initial version of a running CR to TS 38.300 in RAN2.

[0294] For network-to-network path switching cases (i.e., Scenarios A, B, and D), the entire process for supporting service continuity can be reflected. Here, Scenarios A through D are the same as those described above:

[0295] A. Inter-gNB indirect-to-direct path switching (i.e., switching from "remote UE <-> relay UE A <-> gNB X" to "remote UE <-> gNB Y")

[0296] B. Inter-gNB direct-to-indirect path switching (i.e., switching from "remote UE <-> gNB X" to "remote UE <-> relay UE A <-> gNB Y")

[0297] C. Intra-gNB indirect-to-indirect path switching (i.e., switching from "remote UE <-> relay UE A <-> gNB X" to "remote UE <-> relay UE B <-> gNB X")

[0298] D. Inter-gNB indirect-to-indirect path switching (i.e., switching from "remote UE<-> relay UE A<-> gNB X" to "remote UE<-> relay UE B<-> gNB Y")

[0299] Third example of proposal: The entire procedure for inter-network path switching (i.e. scenarios A, B and D) could be reflected in TS 38.300.

[0300] If the U2N Remote UE switches from an indirect path to a direct path with an inter-gNB change (i.e., Scenario A), it is believed that there will be no significant F1 impact. In this case, a procedure similar to the example in Figure 11 can be performed.

[0301] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0302] FIG. 11 illustrates a procedure for supporting service continuity for path switching from an indirect path to a direct path between inter-gNBs, according to one embodiment of the disclosure of the present specification.

[0303] The Remote UE performs indirect path-based communication with the source gNB via the source relay UE.

[0304] 1. Uu measurement setup and measurement report signaling are performed. For example, a remote UE performs measurements on a target gNB and then reports them to the source gNB.

[0305] 2. The source gNB decides to switch the communication path of the L2 U2N remote mode UE to the direct cell of the target gNB.

[0306] 3. The source gNB sends a handover request message to the target gNB to deliver a transparent RRC container containing the information required to prepare the handover on the target side.

[0307] 4. The target gNB prepares for a handover to L1 / L2 and sends a HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which includes a transparent container to be transmitted to the UE as an RRC message to perform the handover.

[0308] 5. The source gNB triggers a Uu handover by sending an RRCReconfiguration message to the L2 U2N Remote UE. After receiving the RRCReconfiguration message containing the path switching configuration, the L2 U2N Remote UE stops transmitting User Plane (UP) and Control Plane (CP) data through the L2 U2N Relay UE.

[0309] 6. The source gNB sends the SN STATUS TRANSFER message to the target gNB.

[0310] 7. The remote UE can perform a Random Access (RA) procedure for the target gNB.

[0311] 8. The remote UE sends an RRCReconfigurationComplete message to the target gNB.

[0312] 9. The relay UE and source gNB perform RRC reconfiguration.

[0313] 10. Remote UE disconnects PC5.

[0314] 11. Remote UE and target gNB exchange DL and UL data through a direct path.

[0315] Example 4 of the proposal: The entire procedure of Fig. 11 can be applied as a criterion to support transition from an indirect path to a direct path.

[0316] For a U2N remote UE, when switching to an inter-gNB indirect path (e.g., from a direct path to an indirect path, or from an indirect path to an indirect path) (i.e., scenarios B and D), the target gNB establishes an indirect path via the target relay UE. The transition from a direct path to an indirect path with a gNB-DU change can be reused together with the Xn handover procedure. In this scenario, based on the information received from the source gNB-CU, the target gNB-CU assigns a remote UE local ID. The overall procedure for a U2N remote UE to switch from a direct path to an indirect path can be described as an example in Fig. 12.

[0317] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0318] FIG. 12 illustrates a procedure for supporting service continuity for path switching from a direct path to an indirect path between inter-gNBs, according to one embodiment of the disclosure of the present specification.

[0319] The Remote UE performs direct path-based communication with the source gNB.

[0320] 1. Uu measurement setup and measurement reporting signaling are performed between the U2N Remote UE and the source gNB-CU to evaluate both relay link measurements and Uu link measurements. After the U2N Remote UE measures / discovers candidate U2N relay UEs, it can report Uu measurement results to one or more candidate U2N relay UEs.

[0321] 2. The source gNB decides to switch the communication path of the L2 U2N remote UE to an indirect path with one of the candidate target U2N relay UEs served in the same target cell under the target gNB.

[0322] NOTE: The candidate U2N relay UE IDs in the list may be sorted based on, for example, the measurement report of the U2N remote UE for the candidate U2N relay UE.

[0323] 4. If possible, the target gNB makes the final decision to switch the indirect path to the target U2N relay UE among the candidate target relay UEs. The target gNB assigns a local ID to the U2N remote UE. Then, the target gNB sends an RRCReconfiguration message to the target L2 U2N Relay UE, which includes at least the local ID and L2 ID of the L2 U2N Remote UE, the Uu and PC5 Relay RLC channel configuration for relay, and the bearer mapping settings.

[0324] 5. The target gNB sends a handover request acknowledgement message containing an RRCReconfiguration message to the source gNB. The content of the RRCReconfiguration message may include at least the path switch configuration, PC5 RLC channel configuration for relay traffic, bearer mapping, and the associated radio bearer.

[0325] 6. The Source gNB can send an RRCReconfiguration message to the Remote UE.

[0326] 7. The source gNB sends the SN STATUS TRANSFER message to the target gNB.

[0327] 8. Remote UE can establish a PC5 connection with Relay UE.

[0328] 9. The Remote UE sends an RRCReconfiguration Complete message to the Target gNB.

[0329] 10. The Remote UE can exchange DL data and UL data with the Target gNB based on an indirect path through the Relay UE.

[0330] Example 5 of the proposal: As an example of criteria to support transition from a direct route to an indirect route, the entire procedure of Fig. 12 can be applied.

[0331] According to the inter-gNB direct-to-indirect path switching procedure of FIG. 12, the inter-gNB indirect-to-indirect path switching procedure can be described as follows.

[0332] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0333] FIG. 13a and FIG. 13b illustrate a procedure for supporting service continuity in path switching from an inter-gNB indirect path to an indirect path, according to one embodiment of the disclosure of the present specification.

[0334] The Remote UE performs indirect path-based communication with the source gNB via the source relay UE.

[0335] 1. Uu measurement setup and measurement reporting signaling are performed between the U2N Remote UE and the source gNB-CU to evaluate both relay link measurements and Uu link measurements. After the U2N Remote UE measures / discovers candidate U2N relay UEs, it can report Uu measurement results to one or more candidate U2N relay UEs.

[0336] 2. The source gNB decides to switch the indirect path of the L2 U2N remote UE to one of the candidate target U2N relay UEs served in the same target cell under the target gNB.

[0337] 3. The source gNB sends a HANDOVER REQUEST message to the target gNB. The handover request message may include additional information about the list of candidate target U2N relay UEs.

[0338] NOTE: The candidate U2N relay UE IDs in the list may be sorted based on, for example, the measurement report of the U2N remote UE for the candidate U2N relay UE.

[0339] 4. If possible, the target gNB finally decides to switch the indirect path to the target U2N relay UE among the candidate target relay UEs. Then, the target gNB sends an RRCReconfiguration message to the target L2 U2N Relay UE, which includes at least the local ID and L2 ID of the L2 U2N Remote UE, the Uu and PC5 Relay RLC channel configuration for the relay, and the bearer mapping configuration.

[0340] 5. The target gNB sends a handover request acknowledgement message containing an RRCReconfiguration message to the source gNB. The contents of the RRCReconfiguration message may include at least path switch configuration, PC5 RLC channel configuration for relay traffic, bearer mapping, and associated radio bearers.

[0341] 6. The Source gNB can send an RRCReconfiguration message to the Remote UE.

[0342] 7. The source gNB sends the SN STATUS TRANSFER message to the target gNB.

[0343] 8. The Remote UE can establish a PC5 connection with the target Relay UE.

[0344] 9. The Remote UE sends an RRCReconfiguration Complete message to the Target gNB.

[0345] 10. The target gNB sends a UE CONTEXT RELEASE message to the source gNB.

[0346] 11. The relay UE and source gNB perform RRC reconfiguration.

[0347] 12. Remote UE disconnects PC5.

[0348] 13. Remote UE and target gNB exchange DL data and UL data through an indirect path via the target relay UE.

[0349] Example 6 of the proposal: The entire procedure of FIGS. 13a and 13b can be used as an example to support switching from an indirect path to an indirect path.

[0350] Below, an example of switching from an indirect path to a direct path is described.

[0351] For service continuity of L2 U2N relay, when L2 U2N remote UE switches to direct path, the procedure according to the example of Figure 14 is used:

[0352] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0353] FIG. 14 is an example of a procedure for switching from an indirect path to a direct path according to one embodiment of the disclosure of the present specification.

[0354] Figure 14 shows an example of a procedure for switching an indirect path of an L2 U2N remote UE to a direct path based on a direct Uu cell.

[0355] 0. The remote UE exchanges UL data and DL data with the gNB based on an indirect path through the relay UE.

[0356] 1. To evaluate both relay link measurements and Uu link measurements, Uu measurement configuration and measurement reporting signaling procedures are performed. If the configured measurement reporting criteria are met, the L2 U2N remote UE reports the measurement results. The sidelink relay measurement report may include at least the source L2 ID of the L2 U2N relay UE, the serving cell ID (i.e., NCGI / NCI), and the sidelink measurement quantity results. The quantity of the sidelink measurement may be the SL-RSRP of the serving L2 U2N relay UE, and if SL-RSRP is not available, SD-RSRP is used.

[0357] 2. The gNB decides to switch the indirect path of the L2 U2N remote UE to a direct Uu path.

[0358] 3. The gNB sends an RRCReconfiguration message to the L2 U2N Remote UE. After receiving the RRCReconfiguration message containing the path switching configuration, the L2 U2N Remote UE stops transmitting UP and CP through the L2 U2N Relay UE.

[0359] 4. L2 U2N remote UE synchronizes with gNB and performs random access.

[0360] 5. The UE (i.e., the L2 U2N Remote UE in the previous step) sends an RRCReconfigurationComplete message to the gNB via the direct path, using the settings provided in the RRCReconfiguration message. From this step onwards, the UE (i.e., the L2 U2N remote UE in the previous step) uses the RRC connection to the gNB via the direct path.

[0361] 6. The gNB sends an RRCReconfiguration message to the L2 U2N Relay UE to re-establish the connection between the L2 U2N Relay UE and the gNB. The RRCReconfiguration message to the L2 U2N Relay UE may be sent at any time after step 3, depending on the gNB implementation (e.g., to release the Uu and PC5 Relay RLC channels for relay, or to set up bearer mapping associated with the L2 U2N Remote UE).

[0362] 7. The AS layer of the L2 U2N Relay UE or L2 U2N Remote UE can release the PC5-RRC connection and instruct the upper layer to release the PC5 unicast link after receiving the RRCReconfiguration message from the gNB. The timing of the link release depends on the UE implementation.

[0363] 8. The data path between the UE (i.e., the former L2 U2N Remote UE) and the gNB switches from an indirect path to a direct path. If configured by the gNB, PDCP re-establishment or PDCP data recovery on the uplink is performed by the UE (i.e., the former L2 U2N Remote UE) to ensure lossless transmission during the path switch.

[0364] NOTE: Step 8 can be performed at any time after Step 4. Step 8 is independent of Steps 6 and 7.

[0365] When the indirect path of the L2 U2N remote UE is switched to a direct path, the procedure described in the example of Fig. 11 can be used for service continuity of the L2 U2N relay between inter-gNBs.

[0366] Below, we describe path switching from a direct path to an indirect path.

[0367] The gNB may select an L2 U2N relay UE in any RRC state (e.g., RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED) as the target L2 U2N relay UE to switch the path of the remote UE from a direct path to an indirect path.

[0368] For service continuity of L2 U2N remote UE, when the direct path of L2 U2N remote UE is switched to an indirect path through L2 U2N relay UE in RRC_CONNECTED, the procedure according to the example of Figure 15 is used:

[0369] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0370] FIG. 15 illustrates a procedure in which a direct path of a remote UE in RRC_CONNECTED state is switched to an indirect path according to one embodiment of the disclosure of the present specification.

[0371] Figure 15 shows an example of a procedure in which a direct path of an L2 U2N remote UE in RRC_CONNECTED state is switched to an indirect path via an L2 U2N relay UE.

[0372] 1. After measuring / discovering candidate L2 U2N relay UEs, L2 U2N remote UE reports measurements and Uu measurements for one or more candidate L2 U2N relay UEs:

[0373] - L2 U2N Remote UE filters appropriate L2 U2N Relay UEs based on relay selection criteria before reporting. L2 U2N Remote UE reports only L2 U2N Relay UE candidates that meet higher layer criteria;

[0374] - The report includes at least the L2 U2N relay UE ID, the serving cell ID of the L2 U2N relay UE, and sidelink measurement quantity information. SD-RSRP is used as the sidelink measurement quantity.

[0375] 2. The gNB decides to switch the direct path of the L2 U2N Remote UE to an indirect path via the target L2 U2N Relay UE. Then, the gNB sends an RRCReconfiguration message to the target L2 U2N Relay UE, which includes at least the local ID and L2 ID of the L2 U2N Remote UE, Uu and PC5 Relay RLC channel settings for relay, and bearer mapping settings.

[0376] 3. The gNB sends an RRCReconfiguration message to the L2 U2N Remote UE. The RRCRecfiguration message contains at least the L2 U2N Relay UE ID, the Remote UE's local ID, the PC5 Relay RLC channel configuration for relay traffic, and the associated end-to-end radio bearer(s). After receiving the RRCReconfiguration message from the gNB, the L2 U2N Remote UE stops UP and CP transmissions over the direct path.

[0377] 4. The L2 U2N remote UE establishes a PC5 RRC connection with the target L2 U2N relay UE.

[0378] 5. The L2 U2N remote UE sends the RRCRecfigurationComplete message to the gNB through the L2 U2N relay UE and completes the path switching procedure.

[0379] 6. The data path is switched from a direct path to an indirect path between the L2 U2N remote UE and the gNB.

[0380] When the L2 U2N Relay UE selected for switching from the direct path to the indirect path is in RRC_IDLE or RRC_INACTIVE state, after receiving the path switching command, the L2 U2N Remote UE establishes a PC5 link with the L2 U2N Relay UE. The L2 U2N Remote UE triggers the L2 U2N Relay UE to enter the RRC_CONNECTED state by sending an RRCReconfigurationComplete message through the L2 U2N Relay UE.

[0381] For reference, the procedure for switching the L2 U2N Remote UE to an indirect path according to the example of FIG. 15 can also be applied when the L2 U2N Relay UE selected for the path switching from the direct path to the indirect path is in RRC_IDLE or RRC_INACTIVE state. In this case, the same operation can be performed except that after the L2 U2N Relay UE becomes RRC_CONNECTED state between steps 4 and 5, the gNB transmits an RRCRecfiguration message to the L2 U2N Relay UE.

[0382] When the path of an L2 U2N Remote UE in RRC_CONNECTED state is switched from a direct path to an indirect path via an L2 U2N Relay UE, the procedure described in the example of FIG. 12 above is used for service continuity between inter-gNBs.

[0383] For path switching from indirect path to indirect path, the following description applies. For service continuity of L2 U2N Remote UE between inter-gNBs, when the indirect path of L2 U2N Remote UE switches from RRC_CONNECTED to intet-gNB indirect path via L2 U2N Relay UE, the procedure described in the examples of FIGS. 13a and 13b above is used.

[0384] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0385] FIG. 16 illustrates an example of a handover preparation procedure performed according to one embodiment of the disclosure of the present specification.

[0386] Figure 16 illustrates an example of a handover preparation procedure. According to the example of Figure 16, a source NG-RAN node may transmit a handover request message to a target NG-RAN node. If the handover request is successful, the target NG-RAN node may transmit a handover request acknowledgement message to the source NG-RAN node.

[0387] The source NG-RAN node initiates the procedure by sending a HANDOVER REQUEST message to the target NG-RAN node. When the source NG-RAN node sends the handover request message, the source NG-RAN node sends a T XnRELOCprep You can start the timer.

[0388] If the Candidate Relay UE Info List IE is included in the HANDOVER REQUEST message, the target NG-RAN node shall, if supported, use it to configure the path switch to indirect path as specified in TS 38.300 [9].

[0389] If the Candidate Relay UE Information List IE is included in the handover request message, and if the target NG-RAN node supports the Candidate Relay UE Information List IE, the target NG-RAN node can set up path switching to an indirect path based on the Candidate Relay UE Information List IE.

[0390] Below, we describe the HANDOVER REQUEST message transmitted from a source NG-RAN node to a target NG-RAN node. The HANDOVER REQUEST message is transmitted from the source NG-RAN node to the target NG-RAN node to request resource preparation for a handover. The HANDOVER REQUEST message may include, for example, an Information Element (IE) such as the example in Table 3.

[0391] IE / Group Name Presence Range IE type and reference Semantics description Criticality Assigned Criticality 5G ProSe PC5 QoS Parameters O9.2.3.160 of TS 38.423 V17.3.0 This IE applies only if the UE is authorized for 5G ProSe services. YES Ignore Candidate Relay UE Info List O9.2.3.x of TS 38.423 V17.3.0 (x can be, for example, 188) YES Reject

[0392] According to the example in Table 3, the handover request message may include a Candidate Relay UE Info List. As suggested in various examples of the disclosure of this specification, the criticality of the Candidate Relay UE Info List may be set to reject. Note that the Candidate Relay UE Info List is included in the 5G ProSe PC5 QoS Parameters, and the 5G ProSe PC5 QoS Parameters may also be included in the handover request message.

[0393] The Candidate Relay UE Info List contains the IDs of candidate relay UEs when the source NG-RAN decides to switch the UE to an indirect path from the target NG-RAN. Table 4 below provides an example of the Candidate Relay UE Info List.

[0394] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCandidate Relay UE Info Item1.. <maxnoofcandidaterelayues>>Candidate Relay UE IDMBIT STRING(SIZE(24)) Contains the SL-SourceIdentity for the candidate relay UE.

[0395] For example, a handover request message may include UEContextInfoHORequest ID information. UEContextInfoHORequest may include UEHistoryInformation ID information. UEHistoryInformation may include NoPDUSessionIndication ID information. NoPDUSessionIndication may include TimeSynchronizationAssistanceInformation UD information. TimeSynchronizationAssistanceInformation may include FiveGProSePC5QoSParameters ID information. FiveGProSePC5QoSParameters may include CandidateRelayUEInfoList ID information. The importance of CandidateRelayUEInfoList may be assigned as reject.

[0396] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0397] FIG. 17 illustrates an example of handover resource allocation according to one embodiment of the disclosure of the present specification.

[0398] According to FIG. 17, the AMF can send a handover request message to the target NG-RAN node. The target NG-RAN node can send a handover request acknowledge message to the AMF. The AMF can initiate the handover resource allocation procedure by sending the handover request message to the target NG-RAN node.

[0399] The Candidate Relay UE Information List IE may be included in the Source NG-RAN Node to Target NG-RAN Node Transparent Container IE within the Handover Request message. In this case, if the target NG-RAN node supports the Candidate Relay UE Information List IE, the target NG-RAN node may configure a path switch to an indirect path based on the Candidate Relay UE Information List IE.

[0400] Below, we describe an example of a Transparent Container transmitted from a source NG-RAN node to a target NG-RAN node. This IE is generated by the source NG-RAN node and transmitted to the target NG-RAN node. In the case of an inter-system handover to 5G, the IE is transmitted from an external handover source to the target NG-RAN node. This IE is transparent to the 5GC.

[0401] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityNGAP IE Support Information Request List0..1YESignore>NGAP IE Support Information Request Item1.. <maxnoofiesupportinfo>->>NGAP Protocol IE-IdM9.3.1.239-Candidate Relay UE Information List0..1YESreject>Candidate Relay UE Information Item1.. <maxnoofcandidaterelayues>->>Candidate Relay UE IDMBIT STRING (SIZE(24)) Contains the SL-SourceIdentity for the candidate relay UE.-

[0402] According to the example of Table 5, the Source NG-RAN Node to Target NG-RAN Node Transparent Container may include a Candidate Relay UE Info List. As suggested in various examples of the disclosure of this specification, the criticality of the Candidate Relay UE Info List may be set to reject. The Candidate Relay UE Info List may include a Candidate Relay UE information item and a Candidate Relay UE ID.

[0403] Note that SourceNGRANNode-ToTargetNGRANNode-TransparentContainer can contain an NGAPIESupportInformationRequestList, which can in turn contain a CandidateRelayUEInformationList.

[0404] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0405] FIG. 18A and FIG. 18B illustrate examples of a procedure for a source gNB to reselect a list of target cells and / or candidate relay UEs according to one embodiment of the disclosure of the present specification.

[0406] Figures 18a and 18b illustrate examples where the target gNB can support inter-gNB path switching for remote UEs, but cannot select a target relay UE capable of servicing the remote UE from the candidate relay UE list sent by the source gNB. In such cases, the target gNB can quickly inform the source gNB that it cannot select a target relay UE. The target gNB allows the source gNB to determine a new target gNB, target cell, target path type, or candidate relay UE list.

[0407] Step 0: Remote UE is transmitting DL / UL data through Source gNB.

[0408] Step 1~2: Can be performed in the same manner as steps 1~2 of FIG. 9a and FIG. 9b.

[0409] NOTE: The order in which the source gNB determines the target gNB, target cell, and target path type is up to the gNB implementation.

[0410] Step 3: It can be performed in the same manner as step 3 of FIG. 9a and FIG. 9b.

[0411] Step 4: Since the target gNB #1 can support Rel-18 inter-gNB path switching for remote UEs, it can understand / execute the IE containing the list of candidate relay UEs in the HANDOVER REQUEST message. Therefore, the target gNB #1 wants to select a relay UE to assist in DL / UL data transmission for the remote UE from the list of candidate relay UEs received in Step 3. However, the selection of the target relay from the list of candidate relay UEs may fail due to the following reasons: the RRC state of the candidate relay UE is RRC_IDLE / RRC_INACTIVE, the load of each candidate relay UE is so severe that it is difficult to service the remote UE, or the Uu link quality between the candidate relay UE and the target gNB #1 is poor.

[0412] Step 5: If Target gNB#1 fails to select a target relay in Step 4, Target gNB#1 may abort the handover procedure for the remote UE. Target gNB#1 may notify the source gNB that the handover procedure has been aborted by sending a HANDOVER PREPARATION FAILURE message to the source gNB. In this case, Target gNB#1 may include a cause value or indication in the HANDOVER PREPARATION FAILURE message that it failed to select a target relay based on the list of candidate relay UEs. Alternatively, Target gNB#1 may include a cause value or indication in the HANDOVER PREPARATION FAILURE message that all relay UEs in the candidate relay UE list are not suitable to serve the remote UE from the perspective of Target gNB#1.

[0413] Step 6: Based on the cause value or indication received in Step 5, the source gNB may perform one or more of target gNB selection, target cell selection, and target path type selection (e.g., Step 2), which may result in one or more of the following:

[0414] (a) The source gNB may determine a new target gNB when it recognizes that handover to Target gNB #1 is impossible. For example, there may be cases such as i) when direct path switching to Target gNB #1 is impossible (e.g., when no Uu cell belonging to Target gNB #1 provides adequate radio quality, or when the Uu cell belonging to Target gNB #1 cannot be determined as the target because the cell does not support S-NSSAI for the remote UE, etc.), ii) when it is difficult to establish a new list other than the candidate relay UE list established / determined in Step 3 for indirect path switching to Target gNB #1. In this case, the source gNB may determine a new target gNB when it recognizes that handover to Target gNB #1 is impossible.

[0415] (b) The source gNB can still perform a handover to the target gNB #1, but can decide to perform a direct path switching. For example, it is difficult to set up a new list other than the candidate relay UE list set / determined in Step 3 for indirect path switching to the target gNB #1. However, there may be a cell among the Uu cells belonging to the target gNB #1 that is suitable for serving the remote UE. In this case, the source gNB can determine that cell as the target cell and notify the target gNB #1 of the direct path switching (i.e., legacy handover).

[0416] (c) The source gNB may maintain the handover and indirect path switching decisions to Target gNB #1, but may select a new target cell and / or candidate relay UE list. For example, the source gNB may configure / determine a new list other than the candidate relay UE list configured / determined in Step 3. For example, the source gNB may determine that serving the Remote UE through a Relay UE belonging to the list is better than serving it through a Uu cell belonging to the target gNB #1 or a Uu cell or candidate relay UE belonging to another neighboring gNB. This may be the case, for example, when the radio quality of the PC5 link between the Remote UE and the Candidate relay UE is better, or when connecting via a direct path through the Uu cell, the radio quality of the Uu link is poor, etc. The source gNB may maintain the handover and indirect path switching decisions to Target gNB #1, but may select a new target cell and / or candidate relay UE list.

[0417] Alternatively, if a HANDOVER PREPARATION FAILURE message is received from Target gNB#1 as in Step 5, it is also possible to immediately execute (a), (b), or (c) by the source gNB implementation or operator's pre-configuration.

[0418] In the examples of FIGS. 18a and 18b, it is assumed that the Source gNB, in Step 6, re-determines that the remote UE is to be served via an indirect path from Target gNB #1. Furthermore, it is assumed that the Source gNB sets / determines a value different from the list of candidate relay UEs included in Step 3 and / or a value different from the Target cell, and includes the set / determined value in the HANDOVER REQUEST message.

[0419] Step 7: The Source gNB may re-determine a list of candidate relay UEs that can be used as an indirect path to Target gNB #1 based on the measurement result received from the remote UE in Step 1 and / or the candidate relay UE list determined / configured in Step 3. The Source gNB transmits a HANDOVER REQUEST message containing the list of candidate relay UEs to Target gNB #1.

[0420] Step 8: Target gNB #1 finally selects a relay UE that will assist in transmitting DL / UL data to the remote UE from the list of candidate relay UEs received in Step 7.

[0421] Step 9: Target gNB #1 transmits the information required for the relay UE selected in Step 8 to serve the remote UE through the RRC Reconfiguration procedure.

[0422] Step 10: Target gNB#1 sends a HANDOVER REQUEST ACK message to the source gNB, including an RRC Reconfiguration message containing information required for the Remote UE to access Target gNB#1, through the relay UE finally selected in Step 8.

[0423] Step 11: The source gNB transmits the RRC Reconfiguration message received in Step 10 to the remote UE.

[0424] Step 12: The Source gNB sends the SN STATUS TRANSFER message to Target gNB #1.

[0425] Step 13: The remote UE establishes a PC5 connection with the relay UE based on the RRC Reconfiguration message received in Step 11.

[0426] Step 14: The Remote UE can complete the Handover procedure by generating an RRC Reconfiguration Complete message in response to the RRC Reconfiguration message received in Step 11 and sending it to Target gNB #1 via the relay UE.

[0427] Step 15: From now on, DL / UL data is exchanged through the relay UE located within the cell of Target gNB #1.

[0428] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0429] FIG. 19a and FIG. 19b illustrate an example of a procedure for a source gNB to re-determine path switching, according to an embodiment of the disclosure of the present specification.

[0430] According to the examples of FIGS. 19A and 19B, the target gNB can support inter-gNB path switching for remote UEs. FIGS. 19A and 19B illustrate an example in which the target gNB cannot select a target relay UE capable of servicing the remote UE from the candidate relay UE list transmitted by the source gNB. In this case, an example is described in which the target gNB quickly informs the source gNB of this fact so that a new target gNB, target cell, target path type, or candidate relay UE list can be determined.

[0431] Step 0~5: The same operations as steps 0 to 5 of FIGS. 18a and 18b are performed.

[0432] Step 6: Based on the cause value or indication received in Step 5, the source gNB may perform one or more of target gNB selection, target cell selection, and target path type selection (e.g., Step 2), which may result in one or more of the following:

[0433] (a) The source gNB may determine a new target gNB when it recognizes that handover to Target gNB #1 is impossible. For example, there may be cases such as i) when direct path switching to Target gNB #1 is impossible (e.g., when no Uu cell belonging to Target gNB #1 provides adequate radio quality, or when the Uu cell belonging to Target gNB #1 cannot be determined as the target because the cell does not support S-NSSAI for the remote UE, etc.), ii) when it is difficult to establish a new list other than the candidate relay UE list established / determined in Step 3 for indirect path switching to Target gNB #1. In this case, the source gNB may determine a new target gNB when it recognizes that handover to Target gNB #1 is impossible.

[0434] (b) The source gNB can still perform a handover to the target gNB #1, but can decide to perform a direct path switching. For example, it is difficult to set up a new list other than the candidate relay UE list set / determined in Step 3 for indirect path switching to the target gNB #1. However, there may be a cell among the Uu cells belonging to the target gNB #1 that is suitable for serving the remote UE. In this case, the source gNB can determine that cell as the target cell and notify the target gNB #1 of the direct path switching (i.e., legacy handover).

[0435] (c) The source gNB may maintain the handover and indirect path switching decisions to Target gNB #1, but may select a new target cell and / or candidate relay UE list. For example, the source gNB may configure / determine a new list other than the candidate relay UE list configured / determined in Step 3. For example, the source gNB may determine that serving the Remote UE through a Relay UE belonging to the list is better than serving it through a Uu cell belonging to the target gNB #1 or a Uu cell or candidate relay UE belonging to another neighboring gNB. This may be the case, for example, when the radio quality of the PC5 link between the Remote UE and the Candidate relay UE is better, or when connecting via a direct path through the Uu cell, the radio quality of the Uu link is poor, etc. The source gNB may maintain the handover and indirect path switching decisions to Target gNB #1, but may select a new target cell and / or candidate relay UE list.

[0436] Alternatively, if a HANDOVER PREPARATION FAILURE message is received from Target gNB#1 as in Step 5, it is also possible to immediately execute (a), (b), or (c) by the source gNB implementation or operator's pre-configuration.

[0437] In the examples of Figures 19a and 19b, it is assumed that in Step 6, the Source gNB has determined that the Target gNB #1 will serve the remote UE via a direct path, rather than an indirect path. The Source gNB may also decide to handover to a direct path (i.e., a target Uu cell) belonging to another nearby gNB other than the Target gNB #1. In this case, Steps 7 to 13 may be performed for a gNB other than the Target gNB #1.

[0438] Step 7: The Source gNB can determine the target Uu cell that can be utilized in the direct path of Target gNB #1 based on the measurement result received from the remote UE in Step 1. The Source gNB sends a HANDOVER REQUEST message containing information about the target Uu cell to Target gNB #1.

[0439] Step 8: Target gNB #1 decides whether to accept / approve the handover for the Remote UE to the target Uu cell received in Step 7. Target gNB #1 may accept the handover for the UE to the target Uu cell. In this case, Target gNB #1 may include an RRC Reconfiguration message containing the information required for the Remote UE to access Target gNB #1 in the HANDOVER REQUEST ACK message. Target gNB #1 transmits the HANDOVER REQUEST ACK message to the source gNB.

[0440] Step 9: The source gNB forwards the RRC Reconfiguration message received in Step 8 to the remote UE.

[0441] Step 10: The Source gNB sends an SN STATUS TRANSFER message to the Target gNB #1.

[0442] Step 11: The remote UE initiates a random access procedure toward the target gNB#1 based on the RRC Reconfiguration message received in Step 9.

[0443] Step 12: The Remote UE can complete the Handover procedure by generating an RRC Reconfiguration Complete message in response to the RRC Reconfiguration message received in Step 9 and forwarding it to Target gNB #1 via the direct path.

[0444] Step 13: From now on, DL / UL data is exchanged through the Uu cell of Target gNB #1.

[0445] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0446] FIG. 20 illustrates an example of a procedure according to one embodiment of the disclosure of the present specification.

[0447] For reference, the procedure illustrated in FIG. 20 is merely an example, and the scope of the disclosure of this specification is not limited by the example in FIG. 20.

[0448] For example, with respect to the example of FIG. 20, the operations described in the examples of FIGS. 1 to 19A and 19B may also be applied. For example, even if operations, contents, etc. are not directly described in the examples of FIGS. 19A and 19B, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0449] In the example of FIG. 20, the UE may refer to the Remote UE in the examples of FIGS. 6 to 19A and 19B. The source base station may be the source gNB or source NG-RAN node of FIGS. 6 to 19A and 19B. The target base station may be the target gNB or target NG-RAN node of FIGS. 6 to 19A and 19B.

[0450] In step (S2001), the UE may transmit a measurement report message to the source base station. For example, the source base station may receive a report message from the UE that includes measurement results related to one or more relay UEs.

[0451] The measurement report message may include the ID of the relay UE, the serving cell ID, and sidelink measurement results for the one or more relay UEs.

[0452] Before step (S2002) is performed, the source base station may determine a target path type for the UE based on the measurement results. The target path type may be an indirect path or a direct path. If the source base station determines that the target path type is an indirect path, the source base station may generate a candidate relay UE information list IE. For example, the source base station may determine the candidate relay UE information list IE including one or more candidate relay UEs that can be used as an indirect path for the UE from the first target base station based on the measurement results.

[0453] In step (S2002), the source base station may transmit a handover request message to the target base station. The handover request message may include a candidate relay UE information list information element (IE). The importance of this IE may be assigned to reject, meaning that the target base station cannot ignore this IE.

[0454] If the target base station supports the IE, the target relay UE may be selected based on the candidate relay UE information list IE. The target base station may select the target relay UE based on at least one of a Radio Resource Control (RRC) status of the one or more candidate relay UEs, a load of the one or more candidate relay UEs, and / or a link quality between the one or more candidate relay UEs and the target base station. Based on a failure to select the target relay UE from among the one or more candidate relay UEs included in the candidate relay UE information list IE, the target base station may perform step (S2003).

[0455] In step (S2003), the target base station may transmit a handover preparation failure message to the source base station. The handover preparation failure message may include a cause value. The cause value may indicate that the IE is not supported by the first target base station, or that the first target base station has failed to select a target relay UE from among one or more candidate relay UEs included in the IE.

[0456] After step (S2003) is performed, the source base station may re-determine the target path type of the UE. For example, the source base station may perform one or more of the following operations: selecting a target base station, selecting a target cell, and selecting a path type between an indirect path and a direct path.

[0457] For example, the source base station may determine the second target base station as the target base station. In another example, the source base station may maintain the target base station but change the target path type from a direct path to an indirect path, or change the target path type from an indirect path to a direct path. In another example, the source base station may maintain the target base station and the target path type, but newly select the target cell and / or the candidate relay UE information list IE.

[0458] The operations of the drawings based on the various examples described above may be performed individually or together with the operations of other drawings.

[0459] According to one embodiment of the disclosure of the present specification, during a handover process, a target gNB may notify a source gNB that inter-gNB direct / indirect-to-indirect path switching has not been properly performed. For example, the source gNB may notify the target gNB by including a candidate relay UE list in a HANDOVER REQUEST message. For example, if the target gNB does not support inter-gNB direct-to-indirect path switching and / or indirect-to-indirect path switching, or if the target gNB cannot select an appropriate target relay UE from the candidate relay UE list received from the source gNB, the target gNB may transmit a cause value or indication to the source gNB to notify this. Based on the cause value or indication received from the target gNB, the source gNB may perform a handover procedure targeting a new target (e.g., gNB, cell, path type, candidate relay UE list).

[0460] This specification may have various effects.

[0461] For example, according to the disclosure of this specification, if the target gNB does not support inter-gNB path switching for remote, the source gNB can quickly select another gNB. The source gNB can handover the UE and continue to provide services through the new gNB. Alternatively, the target gNB may not be able to select an appropriate target relay UE from the candidate relay UE list sent by the source gNB. In this case, the target gNB notifies the source gNB of this fact, so that the source gNB can quickly make a new decision on the handover target (e.g., gNB, cell, path type, candidate relay UE list). Through this, the source gNB can handover the UE to the newly determined target and continue to provide services to the UE through the new gNB.

[0462] For example, according to various examples of the disclosure of the present specification, path switching can be effectively supported during a handover process of a UE. For example, the target gNB may not support inter-gNB path switching for remote. Or, the target gNB may fail to select an appropriate relay UE from a list of candidate relay UEs. In such cases, the source gNB can quickly perform a new determination of the handover target (e.g., gNB, cell, path type, candidate relay UE list). Accordingly, the source gNB can perform a handover for the UE based on the newly determined target and continue to provide services to the UE through the new node.

[0463] The effects that can be achieved through the specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0464] For reference, the operation of the terminal (e.g., UE, remote UE, relay UE, etc.) described in this specification can be implemented by the devices of FIGS. 1 to 3 described above. For example, the terminal (e.g., UE, remote UE, relay UE, etc.) can be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal (e.g., UE, remote UE, relay UE, etc.) described in this specification can be processed by one or more processors (102 or 202). The operation of the terminal described in this specification can be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a terminal (e.g., UE) described in the disclosure of this specification.

[0465] In addition, commands for performing operations of a terminal (e.g., UE, remote UE, relay UE, etc.) described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform operations of a terminal (e.g., UE, remote UE, relay UE, etc.) described in the disclosure of this specification.

[0466] For reference, the operations of a network node (e.g., AMF, SMF, UPF, PCF, NEF, UDM, DN, etc.) or a base station (e.g., NG-RAN, gNB, source base station, target base station, source NG-RAN, target NG-RAN, source gNB, target gNB, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network node or base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operations of a network node or base station described in this specification may be processed by one or more processors (102 or 202). The operations of a terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

[0467] Additionally, the instructions for performing the operations of the network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories (104 or 204). In addition, the instructions recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the network node or base station described in the disclosure of this specification.

[0468] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to these specific embodiments, and may be modified, changed, or improved in various forms within the scope of the spirit and claims of this specification.

[0469] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0470] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.< / maxnoofcandidaterelayues> < / maxnoofiesupportinfo> < / maxnoofcandidaterelayues>

Claims

1. In a method for a source base station to perform communication related to handover, A step of receiving a report message including measurement results related to one or more relay UEs from a User Equipment (UE); A step of determining a target path type for the UE based on the measurement results; A step of transmitting a handover request message to the first target base station, The above handover request message includes a candidate relay UE information list Information Element (IE), and The criticality of the above IE is assigned as reject; A step of receiving a handover preparation failure message including a cause value from the first target base station; and comprising a step of re-determining the target path type of the UE; A method characterized in that the cause value indicates that the IE is not supported by the first target base station, or that the first target base station failed to select a target relay UE from among one or more candidate relay UEs included in the IE.

2. In paragraph 1, A method characterized in that the measurement report message includes an ID of a relay UE, a serving cell ID, and sidelink measurement results for the one or more relay UEs.

3. In paragraph 1 or 2, A method further comprising the step of determining, based on the measurement results, the candidate relay UE information list IE that can be used as an indirect path for the UE from the first target base station.

4. In any one of paragraphs 1 to 3, The step of re-determining the target path type is: A method characterized by performing at least one of the following steps: selecting a target base station, selecting a target cell, and selecting a path type among an indirect path and a direct path.

5. In any one of paragraphs 1 to 4, A method characterized in that the target path type is a direct path between the first target base station and the UE or an indirect path communicating with the first target base station via a relay UE.

6. In any one of paragraphs 1 to 5, The step of re-determining the target path type is: A method comprising the step of selecting a second target base station as a target base station.

7. In any one of paragraphs 1 to 5, The step of re-determining the target path type is: A method comprising the step of maintaining the first target base station as a target base station, but changing the target path type from a direct path to an indirect path or changing the target path from an indirect path to a direct path.

8. In any one of paragraphs 1 to 5, The step of re-determining the target path type is: A method comprising the step of maintaining the first target base station as a target base station and maintaining the target path type, while newly selecting a target cell and / or a candidate relay UE information list UE.

9. In a source base station performing communication related to handover, the source base station: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A source base station, wherein the operation performed based on the command being executed by the one or more processors is a method according to any one of claims 1 to 8.

10. As an apparatus in mobile communication, at least one processor; and At least one memory storing instructions and being operably electrically connected to the at least one processor, A processor wherein the operation performed based on the instruction being executed by the at least one processor is a method according to any one of claims 1 to 8.

11. A non-transitory computer-readable storage medium that records commands, The above instructions, when executed by one or more processors, cause the one or more processors to: A CRM that performs a method according to any one of claims 1 to 8.

12. As a method for a target base station to perform communication, A step of receiving a handover request message requesting handover of User Equipment (UE) from a source base station, The above handover request message includes a candidate relay UE information list Information Element (IE), and The criticality of the above IE is assigned as reject; comprising the step of transmitting a handover preparation failure message including a cause value to the source base station, A method characterized in that the cause value indicates that the target base station does not support the IE, or that selection of a target relay UE from among one or more candidate relay UEs included in the candidate relay UE information list IE has failed.

13. In paragraph 12, A method characterized in that the above candidate relay UE information list IE is determined by the source base station based on specific results related to one or more relay UEs received from the UE.

14. In paragraph 12 or 13, A method further comprising the step of selecting a target relay UE based on the candidate relay UE information list IE, if the target base station supports the IE.

15. In paragraph 14, A method characterized in that the handover preparation failure message is transmitted based on a failure to select a target relay UE from among one or more candidate relay UEs included in the candidate relay UE information list IE.

16. In paragraph 14, A method characterized in that the step of selecting the target relay UE is performed based on at least one of a Radio Resource Control (RRC) status of the one or more candidate relay UEs, a load of the one or more candidate relay UEs, and / or a link quality between the one or more candidate relay UEs and the target base station.

17. In a target base station performing communication related to handover, the target base station: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A target base station, wherein the operation performed based on the command being executed by the one or more processors is a method according to any one of claims 12 to 16.

Citation Information

Patent Citations

  • Handover method, network device, user equipment and communication system

    EP4175360A1

  • Method and Arrangement in a Telecommunication System

    US20130070663A1

  • Enhancement to multiple handover preparation

    US20140023045A1

  • Security framework for msg3 and msg4 in early data transmission

    US20190208411A1

  • User equipment (UE)-triggered handover with early preparation in mobile networks

    US20220116839A1