Network coordination during path switching and multi-path scenarios

By using the network coordination method in a wireless communication system, using measurement reports and identifier sets to manage the connection between the UE and the network entity, the problem of low coordination efficiency in path switching and multi-path scenarios in the prior art is solved, and more efficient Network coordination and communication system flexibility.

CN119032589APending Publication Date: 2024-11-26QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034372.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-28
Filing Date
2023-04-14
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The prior art is difficult to effectively coordinate wireless communication systems in path switching and multi-path scenarios, resulting in low efficiency in connection switching and path addition and unable to meet the needs of complex network environments.

Method used

By introducing a network coordination method in the wireless communication system, the connection switching and path management between the UE and the network entity is realized using a set of measurement reports and identifiers, including sending request messages, confirmation messages and configuration messages, ensuring that the UE is in the second network entity allocation and connection establishment at the location.

Benefits of technology

It improves the efficiency of network coordination in path switching and multi-path scenarios, enhances the flexibility and reliability of the communication system, and adapts to changes in complex network environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032589A_ABST
    Figure CN119032589A_ABST
Patent Text Reader

Abstract

A method, system, and device are described for wireless communication supporting network coordination during path switching and multi-path scenarios. For example, a first network entity may receive, from a first user equipment (UE), a measurement report indicating communication degradation between the first UE and the first network entity. The first network entity may send a request message to a second network entity to switch a connection between the first UE and the first network entity to a connection between the first UE and the second network entity. The second network entity may send an acknowledgement to the first network entity based on the request. The first network entity may configure the first UE for a new connection, and the second network entity may configure a second UE for the new connection. The first UE may communicate with the second network entity via the second UE.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 731,539, filed by Krishnan et al. on April 28, 2022, entitled “NETWORK COORDINATION DURING PATH SWITCHING AND MULTI-PATH SCENARIOS,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following concerns wireless communications, including path switching and network coordination during multipath scenarios. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting path switching and network coordination during multipath scenarios. In general, the described technology provides a first network entity associated with a first central unit (CU) and communicating with a first UE to switch a connection between the first UE and the first network entity to a connection between the first UE and a second network entity associated with a second UE. For example, the first network entity may receive a first message including a measurement report indicating a degradation of communication between the first UE and the first network entity from the first UE. The first network entity may receive the measurement report and may send a second message (e.g., a request message) to the second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity. The second message may indicate a set of identifiers including a first identifier associated with the first UE and a second identifier associated with the second UE. The second network entity may receive the request and assign a third identifier to the first UE. In some cases, the second network entity may select the second UE from a set of UEs associated with the set of identifiers. The second network entity may send a third message (e.g., a confirmation message) indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE to the first network entity. In some cases, the second network entity may send a fourth message (e.g., a configuration message) to the second UE indicating a first identifier associated with the first UE and a third identifier associated with the first UE. In addition, the first network entity may send a fifth message (e.g., a configuration message) to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE. After configuring the first UE and the second UE, the second network entity may communicate with the first UE via the second UE.

[0006] A method for wireless communication at a first network entity is described. The method may include: receiving a first message from a first UE including a measurement report indicating a degradation of communication between the first UE and the first network entity; sending a second message to a second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving the measurement report indicating the degradation of communication, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU; and sending a third message to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, the allocation of the third identifier to the first UE being established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity.

[0007] An apparatus for wireless communication at a first network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive a first message including a measurement report indicating a degradation of communication between the first UE and the first network entity from a first UE; send a second message to a second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving the measurement report indicating the degradation of communication, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU; and send a third message to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity.

[0008] Another apparatus for wireless communication at a first network entity is described. The apparatus may include means for receiving a first message from a first UE including a measurement report indicating a degradation of communication between the first UE and the first network entity, means for sending a second message to a second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving the measurement report indicating the degradation of communication, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU, and means for sending a third message to the first UE indicating a third identifier associated with the first UE and the second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, the allocation of the third identifier to the first UE being established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a first network entity is described. The code may include instructions executable by a processor to perform the following operations: receiving a first message from a first UE including a measurement report indicating a degradation of communication between the first UE and the first network entity; sending a second message to a second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving the measurement report indicating the degradation of communication, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU; and sending a third message to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving, from the second network entity and in response to sending the second message, a fourth message confirming the second message, the fourth message indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the fourth message may include an operation, feature, component, or instruction for receiving an indication of side link control group resources associated with a relay connection between a first UE, a second UE, and a second network entity, wherein the third message includes an indication of the side link control group resources.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a first message including a measurement report may include operations, features, components, or instructions for receiving the first message from the first UE via a third UE, wherein switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity includes: switching a second relay connection between the first UE, the third UE, and the first network entity to a relay connection between the first UE, the second UE, and the second network entity.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a first message may include operations, features, components, or instructions for receiving an indication of a set of identifiers associated with a set of multiple UEs, wherein the set of multiple UEs may be associated with corresponding candidate relay connections between the first UE and the second network entity.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending a fourth identifier associated with the first UE to a second network entity, wherein the fourth identifier associated with the first UE may be based on updating the first identifier associated with the first UE.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first network entity includes a source network node for a handover operation, and the second network entity includes a target network node for the handover operation.

[0016] A method for wireless communication at a second network entity is described. The method may include: receiving a first message from a first network entity for switching a connection between a first UE and the first network entity to a connection between the first UE and the second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU; sending a second message to the first network entity indicating the first identifier associated with the first UE, the second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity; and communicating with the first UE via the second UE based on sending the second message.

[0017] An apparatus for wireless communication at a second network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to perform the following operations: receiving a first message from a first network entity for switching a connection between a first UE and the first network entity to a connection between the first UE and the second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU; sending a second message to the first network entity indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity; and communicating with the first UE via the second UE based on sending the second message.

[0018] Another apparatus for wireless communication at a second network entity is described. The apparatus may include: a component for receiving a first message from a first network entity for switching a connection between a first UE and the first network entity to a connection between the first UE and the second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU; a component for sending a second message to the first network entity indicating the first identifier associated with the first UE, the second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity; and a component for communicating with the first UE via the second UE based on sending the second message.

[0019] A non-transitory computer-readable medium storing code for wireless communication at a second network entity is described. The code may include instructions that can be executed by a processor to perform the following operations: receiving a first message from a first network entity for switching a connection between a first UE and the first network entity to a connection between the first UE and the second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU; sending a second message to the first network entity indicating the first identifier associated with the first UE, the second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity; and communicating with the first UE via the second UE based on sending the second message.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for selecting a second UE from a set of multiple UEs associated with a set of identifiers, wherein the set of multiple UEs may be associated with corresponding candidate relay connections between the first UE and the second network entity.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending a third message indicating a first identifier associated with the first UE and a third identifier associated with the first UE to the second UE, wherein establishing a relay connection between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity may be based on the third message.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving a request for a third identifier associated with the first UE from the second UE, wherein receiving the request may be based on the second UE being in an inactive mode or an idle mode.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for detecting an operating state of the second UE, wherein establishing a relay connection between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity may be based on the operating state of the second UE.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the operating state of the second UE may be associated with an active state, an inactive state, or an idle state.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving a fourth identifier associated with the first UE from the first network entity, wherein the fourth identifier associated with the first UE may be based on updating the first identifier associated with the first UE.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a second message may include operations, features, components, or instructions for sending an indication of side link control group resources associated with a relay connection between a first UE, a second UE, and a second network entity. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 An example of a wireless communication system supporting path switching and network coordination during multipath scenarios in accordance with one or more aspects of the present disclosure is illustrated.

[0028] Figure 2 An example of a wireless communication system supporting path switching and network coordination during multipath scenarios in accordance with one or more aspects of the present disclosure is illustrated.

[0029] Figure 3A , Figure 3B and Figure 3C Continuous examples of a path switching process supporting network coordination during path switching and multi-path scenarios in accordance with one or more aspects of the present disclosure are illustrated.

[0030] Figure 4 An example of a path addition process that supports network coordination during path switching and multipath scenarios according to one or more aspects of the present disclosure is illustrated.

[0031] Figure 5 and Figure 6 A block diagram of a device supporting path switching and network coordination during multipath scenarios according to one or more aspects of the present disclosure is shown.

[0032] Figure 7 A block diagram of a communication manager supporting path switching and network coordination during multipath scenarios is shown in accordance with one or more aspects of the present disclosure.

[0033] Figure 8 A diagram of a system including devices supporting path switching and network coordination during multipath scenarios according to one or more aspects of the present disclosure is shown.

[0034] Figures 9 to 12 A flow chart illustrating a method of supporting path switching and network coordination during multipath scenarios according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0035] Some wireless communication systems may support path switching. That is, a first network entity such as a source network entity may communicate with a first user equipment (UE) such as a remote UE via a direct path (e.g., without using a relay UE to relay communications between the first network entity and the first UE) or via an indirect path (e.g., using a relay UE to relay communications between the first network entity and the first UE). In some cases, the communication between the remote UE and the source network entity may be degraded, so that the source network entity may attempt to switch the connection between the remote UE and the source network entity to a connection between the first UE and a second network entity such as a target network entity (e.g., an inter-network entity path switch). In addition, the connection between the first UE and the second network entity may include a second UE, so that the second UE may relay communications between the first UE and the second network entity (e.g., a direct / indirect to indirect path switch). However, current technology may be insufficient for switching the connection between the remote UE and the source network entity to the connection between the first UE and the second network entity.

[0036] Similarly, some wireless communication systems may support path addition. That is, the remote UE may be connected to multiple network entities (such as a primary network entity and a secondary network entity) via multiple paths (which may be direct paths or indirect paths). In some cases, the communication between the remote UE and the primary network entity may be degraded, so that the primary network entity may configure a path (e.g., add a path) for the remote UE to communicate with the second network entity. For example, the primary network entity may configure the remote UE to communicate indirectly with the second node via a relay UE (e.g., indirect path addition). However, current technology may be insufficient for some path addition scenarios.

[0037] Thus, aspects of the present disclosure may support techniques for network coordination during path switching and multipath scenarios. For example, a first UE (e.g., a remote UE) may send a first message including a measurement report indicating a degradation of communications between the first UE and the first network entity to a first network entity (e.g., a source or primary network entity). In some cases, the measurement report may include an indication of one or more UEs including a second UE (e.g., a target UE) for relaying communications between the first UE and the second network entity. The first network entity may receive the first message and may send a request message (e.g., a handover or path addition request) to the second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity. The request message may include a set of identifiers including at least a first identifier associated with the first UE (e.g., a remote UE layer 2 (L2) identifier) ​​and a second identifier associated with the second UE (e.g., a target UE L2 identifier).

[0038] The second network entity may receive the request message and may assign a third identifier (e.g., a remote UE local identifier) ​​to the first UE. In some cases, the second network entity may select the second UE from a set of UEs associated with the set of identifiers. Additionally or alternatively, the second network entity may send a confirmation message indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE. In some cases, the second network entity may send a first configuration message indicating the first identifier associated with the first UE and the third identifier associated with the first UE to the second UE, so that the second UE can establish a connection with the first UE. In addition, the first network entity may send a second configuration message indicating the third identifier associated with the first UE and the second identifier associated with the second UE to the first UE, so that the first UE can establish a connection with the second UE. The second network entity may communicate with the first UE via the second UE based on the first configuration message and the second configuration message.

[0039] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are then described in the context of a path switching process and a path adding process. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to network coordination during path switching and multipath scenarios.

[0040] Figure 1 An example of a wireless communication system 100 that supports path switching and network coordination during multipath scenarios according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0041] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0042] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices such as Figure 1 Communicating with other UEs 115 or network entities 105 as shown.

[0043] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0044] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other on the backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0045] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0046] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0047] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165, such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), L2) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0048] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such a case, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0049] In the case where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support network coordination during path switching and multipath scenarios as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0050] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.

[0051] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, such as Figure 1 shown.

[0052] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate," when referring to the network entity 105, may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or via one or more other network entities 105).

[0053] The signal waveform transmitted by the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0054] The time interval of the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0055] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of codeword periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may also be divided into a plurality of mini time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0056] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmit time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0057] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0058] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, as well as other examples.

[0059] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have a service subscription with a network provider, or may provide restricted access to UEs 115 associated with a small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0060] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0061] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0062] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0063] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0064] In some systems, the D2D communication link 135 can be an example of a communication channel such as a sidelink communication channel between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure such as roadside units using vehicle-to-network (V2N) communications, or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0065] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0066] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is approximately 1 decimeter to 1 meter. UHF waves may be blocked or redirected by buildings and environmental features that may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0067] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as network entities 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands may be based on carrier aggregation configurations (e.g., LAA) in conjunction with component carriers operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0068] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0069] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0070] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0071] The wireless communication system 100 may support techniques for network coordination during path switching and multipath scenarios. For example, the first UE 115 may send a first message including a measurement report indicating that the communication between the first UE 115 and the first network entity 105 is degraded to the first network entity 105. The first network entity 105 may receive the first message and may send a request message to the second network entity 105 for switching the connection between the first UE 115 and the first network entity 105 to the connection between the first UE 115 and the second network entity 105. The request message may include a set of identifiers, including at least a first identifier associated with the first UE 115 and a second identifier associated with the second UE 115.

[0072] In addition, the second network entity 105 may send a confirmation message indicating a first identifier associated with the first UE 115, a second identifier associated with the second UE 115, and a third identifier associated with the first UE 115, the third identifier being assigned by the second network entity 105. The first network entity 105 may send a configuration message indicating the third identifier associated with the first UE 115 and the second identifier associated with the second UE 115 to the first UE 115, so that the first UE 115 may establish a connection with the second UE 115. Therefore, the second network entity 105 may communicate with the first UE 115 via the second UE 115.

[0073] Figure 2An example of a wireless communication system 200 that supports path switching and network coordination during multipath scenarios according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. For example, the wireless communication system 200 may include one or more network entities 105 (e.g., network entity 105-a and network entity 105-b) and one or more UEs 115 (e.g., UE 115-a and UE 115-b), which may be as described in reference to Figure 1 Examples of corresponding devices described. Figure 2 In the example of FIG. 1 , the network entity 105 may be a CU 160, a DU 165, a RU 170, a base station 140, an IAB node 104, or a Figure 1 Examples of one or more other network nodes are described. The network entity 105 - a and the network entity 105 - b may coordinate with each other during path switching and multipath scenarios.

[0074] Some wireless communication systems may support network entity path switching, such as intra-network entity path switching and inter-network entity path switching. For intra-network entity path switching, the network entity 105 may be associated with multiple DUs 165 (such as a first DU 165 and a second DU 165), and may switch connections (e.g., paths) between the first DU 165 and the second DU 165. The network entity 105 may communicate directly or indirectly with a UE 115 (such as a remote UE 115) via the first DU 165. For direct communication, the remote UE 115 may communicate directly with the first DU 165 (e.g., without using the second UE 115, such as a relay UE 115), and for indirect communication, the remote UE 115 may communicate with the first DU 165 via the relay UE 115. In some cases, the remote UE 115 may send a measurement report to the first DU 165 indicating that the communication between the UE 115 and the first DU 165 is degraded (e.g., the signal quality drops below a threshold), and the first DU 165 may switch the first connection between the remote UE 115 and the first DU 165 to a second connection between the remote UE 115 and the second DU 165. In some cases, the second connection between the remote UE 115 and the second DU 165 may be an indirect connection and may involve the relay UE 115 (which may be in a connected mode, an idle mode, or an inactive mode). For example, the first DU 165 may use the first connection to communicate with the remote UE 115 via the first relay UE 115, and may switch the first connection between the remote UE 115, the first relay UE 115, and the first DU 165 to a second connection between the remote UE 115, the second relay UE 115, and the second DU 165 (e.g., an indirect to indirect path switch within the network entity 105).

[0075] In another example, the first DU 165 may communicate directly with the remote UE 115 (e.g., without the first relay UE 115), and the first connection between the remote UE 115 and the first DU 165 may be switched to a second connection between the remote UE 115 and the second DU 165 (e.g., a direct to indirect path switch within the network entity 105). In some other cases, the second connection between the remote UE 115 and the second DU 165 may be direct. For example, the first DU 165 may communicate with the remote UE 115 via the first relay UE 115, and the first connection between the remote UE 115, the first relay UE 115, and the first DU 165 may be switched to a second connection between the remote UE 115 and the second DU 165 (e.g., an indirect to direct path switch within the network entity 105).

[0076] For an inter-network entity path switch, the first network entity 105 may switch a connection (e.g., a path) from the first network entity 105 to the second network entity 105, where each network entity 105 is associated with a CU 160 (e.g., the first network entity 105 is associated with the first CU 160 and the second network entity 105 may be associated with the second CU 160). In some cases, the first network entity 105 may communicate indirectly with the remote UE 115 via the relay UE 115, and may receive a measurement report from the remote UE 115 (e.g., via the relay UE 115) indicating that the communication between the remote UE 115 and the first network entity 105 is degraded. In this case, the first network entity 105 may switch the connection between the remote UE 115, the relay UE 115, and the first network entity 105 to the connection between the remote UE 115 and the second network entity (e.g., an indirect to direct path switch between network entities 105). However, current technologies may not provide additional inter-network entity 105 path switch scenarios.

[0077] Similarly, the wireless communication system 200 may support an intra-network entity 105 multipath scenario and an inter-network entity 105 multipath scenario. That is, one or more network entities 105 may establish one or more connections (e.g., directly or indirectly) with a remote UE 115, and may switch between the one or more connections, communicate via the one or more connections simultaneously, or both. For an intra-network entity 105 multipath scenario, a network entity 105 that communicates with a remote UE 115 using a first DU 165 may be associated with multiple DUs 165 (such as a first DU 165 and a second DU 165), and may configure an additional connection (e.g., path) between the remote UE 115 and the second DU 165. In this case, the network entity 105 may switch communication between a connection between the remote UE 115 and the first DU 165 and a connection between the remote UE 115 and the second DU 165, or may communicate via these connections simultaneously. In some cases, one or both of the connections between the remote UE 115 and the DU 165 may utilize one or more relay UEs 115 (e.g., the connections may be indirect), such that the one or more relay UEs 115 relay communications between the remote UE 115 and one or both of the DUs 165. In some other cases, neither connection between the remote UE 115 and the DU 165 may utilize a relay UE 115, such that the remote UE 115 communicates directly with the DU 165.

[0078] For the multi-path scenario among network entities 105, a network entity 105, such as a primary network entity 105, may communicate with a remote UE 115 via a first connection (e.g., a path), and may configure (e.g., add), release, or change a second connection between the remote UE 115 and a second network entity 105, such as a secondary network entity 105. For example, the remote UE 115 may communicate with the primary network entity 105 via a direct or indirect connection, and may also communicate with the secondary network entity 105 via a direct or indirect connection. In some cases, the primary network entity 105 (e.g., the primary network entity) may change the connection between the remote UE 115 and the primary network entity 105 (e.g., direct to indirect or indirect to direct) while refraining from changing the connection between the remote UE 115 and the secondary network entity 105 (e.g., the secondary network entity 105 remains direct or remains indirect). In some other cases, the primary network entity 105 may change the connection between the remote UE 115 and the secondary network entity 105 (e.g., direct to indirect or indirect to direct) while refraining from changing the connection between the remote UE 115 and the primary network entity 105 (e.g., the primary network entity 105 remains direct or remains indirect). In some other cases, the primary network entity 105 may change the connection between the remote UE 115 and the primary network entity 105 (e.g., direct to indirect or indirect to direct) while refraining from changing the connection between the remote UE 115 and the secondary network entity 105 (e.g., direct to indirect or indirect to direct).

[0079] In some other cases, the primary network entity 105 may release one or more connections of the remote UE 115. That is, the remote UE 115 may communicate with the primary network entity 105 via a first connection (e.g., directly or indirectly), and communicate with the secondary network entity 105 via a second connection (e.g., directly or indirectly). In addition, the primary network entity 105 may release the second connection with the second network entity 105. For example, the primary network entity 105 may communicate with the remote UE 115 via a direct connection or an indirect connection, and may release the direct connection between the remote UE 115 and the secondary network entity 105 (e.g., released by a direct path of the secondary network entity 105). In another example, the primary network entity 105 may communicate with the remote UE 115 via a direct connection or an indirect connection, and may release the indirect connection between the remote UE 115 and the secondary network entity 105 (e.g., released by an indirect path of the secondary network entity 105).

[0080] In some other cases, the primary network entity 105 may add a connection between the remote UE 115 and the secondary network entity 105. For example, the remote UE 115 may communicate with the primary network entity 105 via a first direct connection or a first indirect connection (e.g., using a relay UE 115), and the remote UE 115 may be configured (e.g., added) to communicate with the secondary network entity 105 via a second connection, where the second connection may be direct (e.g., added through a direct path of the secondary network entity 105) or indirect (e.g., added through an indirect path of the secondary network entity 105). However, some wireless communication technologies for connection addition (e.g., for configuring the remote UE 115 using a second connection between the remote UE 115 and the secondary network entity 105) may be improved.

[0081] The techniques described herein may support network coordination during path switching and multipath scenarios, particularly path switching between network entities and path addition between network entities. For example, a UE 115-a (e.g., a remote UE 115) may communicate with a network entity 105-a via a communication link 205 (e.g., a connection or path), which may be an example of a primary network entity 105 (e.g., a primary network entity) or a source network entity 105. In some cases, the UE 115-a may send a measurement report 220 to the network entity 105-a indicating a degradation of communication on the communication link 205. In addition, the measurement report 220 may include an indication of one or more UEs 115 (such as UE 115-b), which may be used to relay communications between the UE 115-a and a second network entity 105 (such as network entity 105-b), which may be an example of a target network entity 105 or a secondary network entity 105. For example, the measurement report 220 may include a set of identifiers associated with each UE 115 of the one or more UEs 115 (eg, target UE 115 L2 identifiers).

[0082] The network entity 105-a may receive the measurement report 220 and may send a message (such as a connection request 225) to the network entity 105-b for switching (e.g., or adding) the connection between the UE 115-a and the network entity 105-a to the connection between the UE 115-a and the network entity 105-b. The connection request 225 may include a first identifier associated with the UE 115-a (e.g., a remote UE 115L2 identifier) ​​and a set of identifiers associated with one or more UEs 115, such as a second identifier associated with the UE 115-b (e.g., a target UE 115L2 identifier).

[0083] The network entity 105-b may receive the connection request 225 and assign (e.g., generate) a third identifier associated with the UE 115-a (e.g., a remote UE 115 local identifier). Additionally or alternatively, the network entity 105-b may select the UE 115-b from the one or more UEs 115 indicated in the connection request 225. Alternatively, the connection request 225 may indicate the UE 115-b and the associated identifiers such that the network entity 105-b may refrain from performing the selection (e.g., the connection request 225 indicates a target UE 115, such as the UE 115-b). The network entity 105-b may send a connection confirmation 230 to the network entity 105-a based on receiving the connection request 225. In addition, the connection confirmation 230 may indicate a first identifier associated with the UE 115-a, a second identifier associated with the UE 115-b, and a third identifier associated with the UE 115-a.

[0084] The network entity 105-a may receive the connection confirmation 230 and send a configuration message 235-a to the UE 115-a indicating a third identifier associated with the UE 115-a and a second identifier associated with the UE 115-b. In some cases, the network entity 105-b may send a configuration message 235-b to the UE 115-b via the communication link 215 indicating a first identifier associated with the UE 115-a and a third identifier associated with the UE 115-a.

[0085] In addition, network entity 105-b may communicate with UE 115-a via UE 115-b (e.g., direct to indirect path switching or direct to direct and indirect path addition) based on configuration message 235. That is, UE 115-a may send uplink communications to UE 115-b via communication link 210, and UE 115-b may relay the uplink communications to network entity 105-b via communication link 215. Conversely, network entity 105-b may send downlink communications to UE 115-b via communication link 215, and UE 115-b may relay the downlink communications to UE 115-a via communication link 210.

[0086] In some cases, UE 115-a may simultaneously communicate with network entity 105-a via communication link 205 through communication link 210 and communication link 215, and communicate with network entity 105-b via UE 115-b. Alternatively, UE 115-a may refrain from communicating with network entity 105-a via communication link 205 through communication link 210 and communication link 215, while refraining from communicating with network entity 105-b via UE 115-b.

[0087] Additionally or alternatively, UE 115-a may communicate with network entity 105-a via relay UE 115 (e.g., indirectly connected). In such cases, network entity 105-a may switch the connection between UE 115-a, relay UE 115 (e.g., which is different from UE 115-b), and network entity 105-a to the connection between UE 115-a, UE 115-b, and network entity 105-b (e.g., indirect to indirect path switching or indirect to indirect and indirect path addition).

[0088] Figure 3A , Figure 3B and Figure 3C Each illustrates a portion of a path switching process 300 that supports network coordination during path switching and multipath scenarios according to one or more aspects of the present disclosure. In some examples, the path switching process 300 (e.g., path switching process 300-a, path switching process 300-b, and path switching process 300-c) can implement aspects of the wireless communication system 100 and the path switching process 300. For example, the path switching process 300 may include one or more network entities 105 (e.g., network entity 105-c and network entity 105-d) and one or more UEs 115 (e.g., UE 115-c and UE 115-d), which may be as described in reference Figure 1 The path switching process 300 may also include a user plane function (UPF) / access and mobility management (AMF) 302. Figure 3A , Figure 3B and Figure 3C In the example of FIG. 1 , the network entity 105 may be a CU 160, a DU 165, a RU 170, a base station 140, an IAB node 104, or a Figure 1 The network entity 105 - c and the network entity 105 - d may coordinate with each other during the path switching process 300 .

[0089] From the example path switching process 300-a Figure 3A Initially, at 304, the network entity 105-c CU-UP 160 may send first downlink data (e.g., user data) to the UE 115-c via the network entity 105-c DU 165, and at 306, the UE 115-c may send uplink data to the network entity 105-c CU-UP 160 via the network entity 105-c DU.

[0090] At 308, UE 115-c may send a measurement report to network entity 105-c DU 165. The measurement report may indicate that communication between UE 115-c and network entity 105-c is degraded. In some cases, the measurement report may include an indication of a set of identifiers associated with multiple UEs (including a second identifier associated with UE 115-d) (e.g., a target relay UE 115L2 identifier), where the multiple UEs are associated with corresponding candidate relay connections between UE 115-c and network entity 105-d. In some cases, the measurement report may include a single identifier associated with the candidate relay connection (e.g., an indication of one target relay UE 115). The measurement report may also include an indication of a first identifier associated with UE 115-c (e.g., a remote UE 115L2 identifier). In some cases, network entity 105-c may communicate with UE 115-c via relay UE 115.

[0091] At 310 , the network entity 105 - c DU 165 may perform a first messaging wherein the network entity 105 - c DU 165 communicates a measurement report to the network entity 105 - c CU-CP 160 .

[0092] At 312, network entity 105-c CU-CP 160 may send a handover request message to network entity 105-d CU-CP 160. In some cases, the handover request message may include a request to switch a connection between UE 115-c and network entity 105-c to a connection between UE 115-c and network entity 105-d based on receiving the measurement report. In addition, the handover request message may include a set of identifiers associated with multiple UEs (including a second identifier associated with UE 115-d and a first identifier associated with UE 115-c).

[0093] In some cases, the network entity 105-d DU 165 and the network entity 105-d CU-CP 160 may perform a first context modification (CM) procedure at 314. For example, the network entity 105-d may detect an operating state of the UE 115-d (e.g., an active mode, an inactive mode, or an idle mode) and may perform the first CM procedure based on the UE 115-d being in an active mode (e.g., an RRC_Connected state). In another example, the network entity 105-d may refrain from performing the first CM procedure based on the UE 115-d being in an inactive or idle mode (RRC_IDLE / INACTIVE state).

[0094] In some cases, at 316 , the network entity 105 - d CU-CP 160 may perform a second messaging (eg, downlink RRC messaging) to the network entity 105 - d DU 165 .

[0095] At 318, the network entity 105-d may select UE 115-d from the plurality of UEs indicated in the handover request message, and the network entity 105-d DU 165 may send a first configuration message (e.g., RRCReconfiguration) to UE 115-d indicating a first identifier associated with UE 115-c and a third identifier associated with UE 115-c (e.g., when UE 115-c is in active or connected mode) (e.g., a remote UE 115 local identifier), wherein the third identifier is assigned by the network entity 105-d. In some cases, the first configuration message may include an indication of a sidelink control group (SCG) resource set for communication between UE 115-c, UE 115-d, and network entity 105-d (e.g., as determined by network entity 105-d). Additionally or alternatively, the first configuration message may include an indication of a sidelink protocol (e.g., a sidelink relay adaptation protocol (SRAP), a UE 115-c bearer mapped to a PC5 radio link control (RLC) channel). In some cases, the network entity 105-d may send the first configuration message indicating a first identifier associated with the UE 115-c and a third identifier associated with the UE 115-c based on a request (e.g., using a supplemental user identification (SUI) procedure) from the UE 115-d requesting a third identifier (e.g., when the UE 115-d is in an inactive or idle mode).

[0096] At 320, UE 115-d may send a first configuration confirmation message (e.g., RRCReconfigurationComplete) to the network entity 105-d indicating that UE 115-d is configured to relay communications between UE 115-c and the network entity 105-d.

[0097] At 322, the network entity 105-d CU-CP 160 may send a setup request (e.g., a bearer context setup request) to the network entity 105-d CU-UP 160, and at 324, the network entity 105-d CU-UP 160 may send a setup response (e.g., a bearer context setup response) to the network entity 105-d CU-CP 160.

[0098] Continuing with the example of path switching process 300-b Figure 3B, at 326 , the network entity 105 - d CU-CP 160 and the network entity 105 - d DU 165 may perform a UE 115 - c context establishment procedure.

[0099] At 328, network entity 105-d CU-CP 160 may send a handover request confirmation message (e.g., a confirm handover request message) indicating a first identifier associated with UE 115-c and a third identifier associated with UE 115-d to network entity 105-c CU-CP 160. In some cases, the handover request confirmation message may include an indication of a set of SCG resources to be used for communications between UE 115-c, UE 115-d, and network entity 105-d.

[0100] At 330 , the network entity 105 - c CU-CP 160 and the network entity 105 - c DU 165 may perform a UE 115 - c context modification procedure.

[0101] At 332, the network entity 105-c DU 165 may send a second configuration message to the UE 115-c indicating a third identifier associated with the UE 115-c and a second identifier associated with the UE 115-d. In some cases, the second configuration message may include an indication of an SCG resource set for communication between the UE 115-c, the UE 115-d, and the network entity 105-d. Additionally or alternatively, the second configuration message may include an indication of a side link protocol (e.g., SS AP, UE 115-e bearer mapped to a PC5 RLC channel).

[0102] At 334 , the network entity 105 - c CU-CP 160 may send a CM request (e.g., a bearer CM request) to the network entity 105 - c CU-UP 160 , and at 336 , the network entity 105 - c CU-UP 160 may send a CM response (e.g., a bearer CM response) to the network entity 105 - c CU-CP 160 .

[0103] At 338 , the network entity 105 - c CU-CP 160 may perform a first state transfer (eg, a secondary node state transfer or an early state transfer) to the network entity 105 - d CU-CP 160 .

[0104] At 340 , the network entity 105 - d CU-CP 160 may send a CM request (e.g., a bearer CM request) to the network entity 105 - d CU-UP 160 , and at 342 , the network entity 105 - d CU-UP 160 may send a CM response (e.g., a bearer CM response) to the network entity 105 - d CU-CP 160 .

[0105] In some cases, at 344 , the AMF / UPF 402 may send data to the network entity 105 - c CU-CP 160 for forwarding to the network entity 105 - d CU-CP 160 , and at 346 , the network entity 105 - c CU-CP 160 may forward the data to the network entity 105 - d CU-CP 160 .

[0106] At 348, UE 115-c may send a second configuration confirmation message (e.g., RRCReconfigurationComplete) to network entity 105-d DU 165 indicating that UE 115-c is configured to relay communications to network entity 105-d via UE 115-d. In some cases, the second configuration confirmation message may include an indication that UE 115-c has successfully established sidelink communications with UE 115-d. In some cases, network entity 105-d DU 165 may forward an indication of the second configuration confirmation message to network entity 105-d CU-CP 160 (e.g., via a third message at 350). In addition, UE 115-c may connect with network entity 105-d via a random access procedure (e.g., a random access channel (RACH) procedure).

[0107] Continuing with the example of the path switching process 300-c Figure 3C At 352 , the network entity 105 - d CU-CP 160 may send a handover success message to the network entity 105 - c CU-CP 160 indicating that the handover process was successful.

[0108] At 354, the network entity 105-c CU-CP 160 and the network entity 105-c DU 165 may perform a UE 115-c context modification procedure.

[0109] At 356 , the network entity 105 - c CU-CP 160 may send a CM request (e.g., a bearer CM request) to the network entity 105 - c CU-UP 160 , and at 358 , the network entity 105 - c CU-UP 160 may send a CM response (e.g., a bearer CM response) to the network entity 105 - c CU-CP 160 .

[0110] At 360 , the network entity 105 - c CU-CP 160 may perform a second state transfer (eg, a secondary node state transfer) to the network entity 105 - d CU-CP 160 .

[0111] At 362 , the network entity 105 - d CU-CP 160 may send a CM request (e.g., a bearer CM request) to the network entity 105 - d CU-UP 160 , and at 364 , the network entity 105 - d CU-UP 160 may send a CM response (e.g., a bearer CM response) to the network entity 105 - d CU-CP 160 .

[0112] At 366 , the network entity 105 - d CU-UP 160 may perform a path switching procedure with the AMF / UPF 302 .

[0113] At 368, the AMF / UPF 302 may send an end marker packet to the network entity 105-c CU-UP 160, and at 370, the network entity 105-c CU-UP 160 may forward the end marker packet to the network entity 105-d CU-UP 160. Additionally, at 372, the AMF / UPF 302 may send an indication of a new path (e.g., a new connection established via the handover process) to the network entity 105-d CU-UP 160.

[0114] At 374, network entity 105-d CU-UP 160 may send second downlink data (e.g., user data) to UE 115-c via network entity 105-d DU 165 and UE 115-d. Additionally, at 376, UE 115-c may send second uplink data to network entity 105-d CU-UP 160 via UE 115-d and network entity 105-d DU 165.

[0115] At 378 , the network entity 105 - d CU-UP 160 may send a context release (eg, UE 115 - c context release) to the network entity 105 - c CU-CP 160 indicating that the network entity 105 - c may release the connection with the UE 115 - c .

[0116] At 380, the network entity 105-c CU-CP 160 may send a release command (e.g., a bearer context release command) to the network entity 105-c CU-UP 160, and at 382, ​​a context release procedure (e.g., a UE 115-c context release procedure) may be performed with the network entity 105-c DU 165. At 384, upon completion of the procedure, the network entity 105-c CU-UP 160 may send an indication of the completed procedure (e.g., bearer context release complete) to the network entity 105-d CU-CP 160.

[0117] Although communications between UE 115-c and network entity 105-c are initially described in the context of a direct communications link (e.g., UE 115-c communicates directly with network entity 105-c), it should be understood that UE 115-c may communicate with network entity 105-c via relay UE 115 (e.g., relay UE 115 relays uplink communications from UE 115-c to network entity 105-c and relays downlink communications from network entity 105-c to UE 115-c). That is, path switching process 300 may support network coordination for path switching scenarios associated with switching from an indirect communications path (e.g., UE 115-c communicates with network entity 105-c via an initial relay UE 115) to an indirect communications path (e.g., UE 115-c communicates with network entity 105-d via an initial UE 115-d).

[0118] Figure 4 An example of a path adding process 400 for supporting network coordination during path switching and multipath scenarios according to one or more aspects of the present disclosure is illustrated. In some examples, the path adding process 400 can implement aspects of the wireless communication system 100, the wireless communication system 200, and the path switching process 300. For example, the path switching process 400 may include one or more network entities 105 (e.g., network entity 105-e and network entity 105-f) and one or more UEs 115 (e.g., UE 115-e and UE 115-f), which may be as described in reference to Figure 1 In addition, the path adding process 400 may include UPF 402 and AMF 404. Figure 4 In the example of FIG. 1 , the network entity 105 may be a CU 160, a DU 165, a RU 170, a base station 140, an IAB node 104, or a Figure 1 The network entity 105 - e and the network entity 105 - f may coordinate with each other during the path adding process 400 .

[0119] At 406, the network entity 105-e may send a measurement report to the network entity 105-e. The measurement report may indicate that the communication between the UE 115-e and the network entity 105-e is degraded. In some cases, the measurement report may include an indication of a set of identifiers associated with multiple UEs (e.g., target relay UE 115L2 identifiers), the set of identifiers including a second identifier associated with the UE 115-f, wherein the multiple UEs are associated with corresponding candidate relay connections between the UE 115-e and the network entity 105-f. In some cases, the measurement report may include n single identifiers associated with the candidate relay connection (e.g., an indication of one target relay UE 115). The measurement report may also include an indication of a first identifier associated with the UE 115-e (e.g., a remote UE 115L2 identifier). In some aspects, the network entity 105-e may communicate with the UE 115-e via the relay UE 115.

[0120] At 408, UE 115-e may send a secondary node (SN) (e.g., secondary network entity 105) add request. In some cases, the SN add request may include a request to switch a connection between UE 115-e and network entity 105-e to a connection between UE 115-e and network entity 105-f based on receiving the measurement report. In some other cases, the SN add request may include a request to configure (e.g., add) a connection between UE 115-e and network entity 105-f based on receiving the measurement report. In addition, the SN add request may include a set of identifiers associated with multiple UEs, including a second identifier associated with UE 115-f and a first identifier associated with UE 115-e.

[0121] At 410, the network entity 105-f may select a target UE 115, such as UE 115-f, from the plurality of UEs associated with the set of identifiers, and may generate (e.g., allocate) a third identifier (e.g., a remote UE 115 local identifier) ​​to the UE 115-e. In some cases, the SN add request may include an indication of a single target UE 115, and the network entity 105-f may select the single target UE 115. In some cases, the network entity 105-f may determine a set of SCG resources for communication between the UE 115-e, the UE 115-f, and the network entity 105-f.

[0122] At 412, the network entity 105-f may send an SN add request confirmation (e.g., a confirmation request message) indicating a first identifier associated with the UE 115-e and a third identifier associated with the UE 115-e. In some cases, the SN add request confirmation may include an indication of an SCG resource set for communication between the UE 115-e, the UE 115-f, and the network entity 105-f. Additionally or alternatively, the SN add request confirmation may include an indication of a side link protocol (e.g., SRAP, UE 115-e bearer mapped to PC5 RLC channel).

[0123] At 414, the network entity 105-f may send a first configuration message (e.g., RRCReconfiguration) to the UE 115-f indicating a first identifier associated with the UE 115-e and a third identifier associated with the UE 115-e (e.g., when the UE 115-f is in an active mode or a connected mode). In some cases, the first configuration message may include an indication of an SCG resource set for communication between the UE 115-e, the UE 115-f, and the network entity 105-f. Additionally or alternatively, the first configuration message may include an indication of a side link protocol (e.g., SRAP, UE 115-e bearer mapped to a PC5 RLC channel). In some cases, the network entity 105-f may send the first configuration message indicating the first identifier associated with the UE 115-e and the third identifier associated with the UE 115-e based on a request from the UE 115-f for the third identifier (e.g., when the UE 115-f is in an inactive or idle mode). For example, the network entity 105-f may detect that the UE 115-f is in an inactive mode (e.g., an operational state of the UE 115-f) and may monitor for a request from the UE 115-f. In this manner, the UE 115-f may send the request (e.g., via the SUI), and the network entity 105-f may send a first configuration message based on receiving the request.

[0124] At 416, UE 115-f may send a first configuration confirmation message (e.g., RRCReconfigurationComplete) to network entity 105-f indicating that UE 115-f is configured to relay communications between UE 115-e and network entity 105-f. At 418, network entity 105-e may send an address indication (e.g., an Xn-U address) to network entity 105-f.

[0125] At 420, the network entity 105-e may send a second configuration message to the UE 115-e indicating a third identifier associated with the UE 115-e and a second identifier associated with the UE 115-f. In some cases, the second configuration message may include an indication of an SCG resource set for communication between the UE 115-e, the UE 115-f, and the network entity 105-f. Additionally or alternatively, the second configuration message may include an indication of a side link protocol (e.g., SRAP, UE 115-e bearer mapped to a PC5 RLC channel).

[0126] At 422, UE 115-e and UE 115-f may establish a sidelink communication link (e.g., a PC5 connection). At 424, UE 115-e may send a second configuration confirmation message (e.g., RRCReconfigurationComplete) to network entity 105-e indicating that UE 115-e is configured to relay communications to network entity 105-f via UE 115-f. In some cases, the second configuration confirmation message may include an indication that UE 115-e has successfully established sidelink communications with UE 115-f. In some cases, network entity 105-e may forward an indication of the second configuration confirmation message to network entity 105-f.

[0127] At 426, network entity 105-e may send a state transfer (e.g., an SN state transfer) to network entity 105-f. In some cases, at 428, UPF 402 may send data to network entity 105-e for forwarding to network entity 105-f, and at 430, network entity 105-e may forward the data to network entity 105-f.

[0128] In some cases, at 432, the network entity 105, UPF 402, and AMF 404 may perform a path update procedure, for example, when the network entity 105 updates a first identifier associated with the UE 115-e (e.g., the network entity 105-e may update the first identifier).

[0129] In this case, at 434, the network entity 105-e may send a protocol data unit (PDU) session modification message to the AMF 404, and at 436, the AMF 404 may send a bearer modification to the UPF 402.

[0130] At 438, UPF 402 may send the end marker packet to network entity 105-e, and at 440, network entity 105-e may forward the end marker packet to network entity 105-f. In some cases, the end marker packet may include a fourth identifier associated with UE 115-e, wherein the fourth identifier is based on the updated first identifier (e.g., the updated remote UE 115L2 identifier).

[0131] At 442, the AMF 404 may send a PDU session modification determination to the network entity 105-e indicating that the PDU session modification was successful.

[0132] Although described in the context of indirect communication path addition, it should be understood that the techniques described herein may also be applied to indirect communication path modification. For example, a remote UE 115-e may communicate with a network entity 105-f via a first direct connection, and the network entity 105-e may configure the UE 115-e to switch the path from the first direct connection to a second indirect connection between the UE 115-e and the network entity 105-f. In another example, a remote UE 115-e may communicate with the network entity 105-f via a first indirect connection associated with a first relay UE 115, and the network entity 105-e may configure the UE 115-e to switch the path from the first indirect connection to a second indirect connection between the UE 115-e and the network entity 105-f associated with a second relay UE 115. That is, the network entity 105-e may configure the UE 115-e to switch communications with the network entity 105-f from the first relay UE 115 to the second relay UE 115. Additionally or alternatively, although described in the context of indirect communication path addition, it should be understood that the techniques described herein may be applied to any inter-network entity 105 multipath scenario.

[0133] Figure 5 A block diagram 500 of a device 505 supporting path switching and network coordination during multipath scenarios according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the network entity 105 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0134] The receiver 510 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 505. In some examples, the receiver 510 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 510 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0135] The transmitter 515 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 505. For example, the transmitter 515 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 515 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 515 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 515 and the receiver 510 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0136] The communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of network coordination during path switching and multipath scenarios as described herein. For example, the communication manager 520, the receiver 510, the transmitter 515, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0137] In some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described herein. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0138] Additionally or alternatively, in some examples, the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0139] In some examples, communication manager 520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated with receiver 510, transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0140] The communication manager 520 may support wireless communication at the first network entity according to the examples disclosed herein. For example, the communication manager 520 may be configured to or otherwise support a component for receiving a first message from a first UE, the first message including a measurement report indicating a degradation of communication between the first UE and the first network entity. The communication manager 520 may be configured to or otherwise support a component for sending a second message to a second network entity, the second message being used to switch a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving a measurement report indicating degradation of communication, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The communication manager 520 may be configured to or otherwise support means for sending a third message to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established based on a relay connection between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity.

[0141] Additionally or alternatively, the communication manager 520 may support wireless communication at the second network entity according to the examples disclosed herein. For example, the communication manager 520 may be configured to or otherwise support a component for receiving a first message from the first network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The communication manager 520 may be configured to or otherwise support a component for sending a second message to the first network entity indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity, as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity. The communication manager 520 may be configured or otherwise support means for communicating with the first UE via the second UE based on sending the second message.

[0142] By including or configuring a communication manager 520 according to examples as described herein, the device 505 (e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communication manager 520, or a combination thereof) may support techniques for network coordination during path switching and multipath scenarios, which may result in reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other advantages.

[0143] Figure 6 A block diagram 600 of a device 605 supporting path switching and network coordination during multipath scenarios according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or the network entity 105 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0144] The receiver 610 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 605. In some examples, the receiver 610 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 610 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0145] The transmitter 615 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 605. For example, the transmitter 615 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 615 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 615 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 615 and the receiver 610 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0146] Device 605 or its various components can be examples of components for performing various aspects of network coordination during path switching and multipath scenarios as described herein. For example, communication manager 620 may include reporting component 625, connection request component 630, connection switching component 635, connection confirmation component 640, or any combination thereof. Communication manager 620 can be an example of various aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components can be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or integrate with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0147] The communication manager 620 may support wireless communication at the first network entity according to the examples disclosed herein. The reporting component 625 may be configured to or otherwise support a component for receiving a first message including a measurement report indicating a degradation of communication between the first UE and the first network entity from the first UE. The connection request component 630 may be configured to or otherwise support a component for sending a second message to the second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving a measurement report indicating a degradation of communication, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The connection switching component 635 may be configured to or otherwise support means for sending a third message to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established based on a relay connection between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity.

[0148] Additionally or alternatively, the communication manager 620 may support wireless communication at the second network entity according to the examples disclosed herein. The connection request component 630 may be configured to or otherwise support a means for receiving a first message from the first network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The connection confirmation component 640 may be configured to or otherwise support a means for sending a second message to the first network entity indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity, as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity. The connection switching component 635 may be configured to or otherwise support means for communicating with the first UE via the second UE based on sending the second message.

[0149] Figure 7 A block diagram 700 of a communication manager 720 supporting network coordination during path switching and multipath scenarios according to one or more aspects of the present disclosure is shown. The communication manager 720 can be an example of aspects of the communication manager 520, the communication manager 620, or both as described herein. The communication manager 720 or its various components can be examples of components for performing various aspects of network coordination during path switching and multipath scenarios as described herein. For example, the communication manager 720 can include a reporting component 725, a connection request component 730, a connection switching component 735, a connection confirmation component 740, an identifier component 745, a relay selection component 750, a detection component 755, a resource component 760, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0150] The communication manager 720 may support wireless communication at the first network entity according to the examples disclosed herein. The reporting component 725 may be configured to or otherwise support a component for receiving a first message including a measurement report indicating a degradation of communication between the first UE and the first network entity from the first UE. The connection request component 730 may be configured to or otherwise support a component for sending a second message to the second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving a measurement report indicating a degradation of communication, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The connection switching component 735 may be configured to or otherwise support means for sending a third message to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established based on a relay connection between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity.

[0151] In some examples, the connection confirmation component 740 may be configured to or otherwise support a component for receiving a fourth message confirming the second message from the second network entity and in response to sending the second message, the fourth message indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE.

[0152] In some examples, to support receiving a fourth message, resource component 760 may be configured as or support a component for receiving an indication of side link control group resources associated with a relay connection between the first UE, the second UE, and the second network entity, wherein the third message includes an indication of the side link control group resources.

[0153] In some examples, to support receiving a first message including a measurement report, the connection switching component 735 may be configured to or otherwise support a component for receiving a first message from the first UE via a third UE, wherein switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity includes: switching the second relay connection between the first UE, the third UE and the first network entity to the relay connection between the first UE, the second UE and the second network entity.

[0154] In some examples, to support receiving the first message, the identifier component 745 may be configured as or otherwise support means for receiving an indication of a set of identifiers associated with a set of multiple UEs, where the set of multiple UEs are associated with respective candidate relay connections between the first UE and the second network entity.

[0155] In some examples, identifier component 745 may be configured to or otherwise support means for sending a fourth identifier associated with the first UE to a second network entity, wherein the fourth identifier associated with the first UE is based on updating a first identifier associated with the first UE.

[0156] In some examples, the first network entity comprises a source network node for a handover operation, and the second network entity comprises a target network node for the handover operation.

[0157] Additionally or alternatively, the communication manager 720 may support wireless communication at the second network entity according to the examples disclosed herein. In some examples, the connection request component 730 may be configured to or otherwise support a means for receiving a first message from the first network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The connection confirmation component 740 may be configured to or otherwise support a means for sending a second message to the first network entity indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity. In some examples, connection switching component 735 may be configured or otherwise support means for communicating with the first UE via the second UE based on sending the second message.

[0158] In some examples, relay selection component 750 may be configured to or otherwise support means for selecting a second UE from a set of multiple UEs associated with a set of identifiers, wherein the set of multiple UEs are associated with corresponding candidate relay connections between the first UE and the second network entity.

[0159] In some examples, the connection switching component 735 may be configured to or otherwise support a component for sending a third message to a second UE indicating a first identifier associated with the first UE and a third identifier associated with the first UE, wherein a relay connection is established between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on the third message.

[0160] In some examples, identifier component 745 may be configured to or otherwise support means for receiving a request for a third identifier associated with the first UE from the second UE, where receiving the request is based on the second UE being in an inactive mode or an idle mode.

[0161] In some examples, detection component 755 may be configured as or otherwise support means for detecting an operating state of the second UE, wherein a relay connection is established between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on the operating state of the second UE.

[0162] In some examples, the operating state of the second UE is associated with an active mode, an inactive mode, or an idle mode.

[0163] In some examples, identifier component 745 may be configured or otherwise support means for receiving a fourth identifier associated with the first UE from the first network entity, wherein the fourth identifier associated with the first UE is based on updating a first identifier associated with the first UE.

[0164] In some examples, to support sending the second message, resource component 760 may be configured as or otherwise support means for sending an indication of sidelink control group resources associated with the relay connection between the first UE, the second UE, and the second network entity.

[0165] Figure 8 A diagram of a system 800 including a device 805 supporting network coordination during path switching and multipath scenarios according to one or more aspects of the present disclosure is shown. The device 805 can be an example of a device 505, a device 605, or a network entity 105 as described herein, or include components thereof. The device 805 can communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 805 may include components that support output and acquisition of communications, such as a communication manager 820, a transceiver 810, an antenna 815, a memory 825, a code 830, and a processor 835. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 840).

[0166] The transceiver 810 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 810 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 810 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 805 may include one or more antennas 815, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 810 may also include a modem for: modulating a signal, providing the modulated signal for transmission (e.g., through one or more antennas 815, through a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 815, from a wired receiver) and demodulating the signal. The transceiver 810 or transceiver 810 and one or more antennas 815 or wired interfaces (where applicable) may be examples of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communications via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0167] The memory 825 may include RAM and ROM. The memory 825 may store computer-readable, computer-executable code 830 including instructions that, when executed by the processor 835, cause the device 805 to perform various functions described herein. The code 830 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 830 may not be directly executable by the processor 835, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, the memory 825 may also include a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0168] The processor 835 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 835 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 835. The processor 835 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 825) to enable the device 805 to perform various functions (e.g., functions or tasks that support network coordination during path switching and multipath scenarios). For example, the device 805 or a component of the device 805 may include a processor 835 and a memory 825 coupled to the processor 835, and the processor 835 and the memory 825 are configured to perform various functions described herein. The processor 835 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions for performing functions of the device 805 (e.g., by executing code 830).

[0169] In some examples, bus 840 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 840 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 805, or communications performed between different components of device 805 that may be co-located or located in different locations (e.g., where device 805 may refer to a system in which one or more of communication manager 820, transceiver 810, memory 825, code 830, and processor 835 may be located in one of the different components or divided between the different components).

[0170] In some examples, the communication manager 820 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 820 may manage the delivery of data communications for client devices such as one or more UEs 115. In some examples, the communication manager 820 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UE 115 in collaboration with the other network entities 105. In some examples, the communication manager 820 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0171] The communication manager 820 may support wireless communication at the first network entity according to the examples disclosed herein. For example, the communication manager 820 may be configured to or otherwise support a component for receiving a first message including a measurement report indicating communication degradation between the first UE and the first network entity from the first UE. The communication manager 820 may be configured to or otherwise support a component for sending a second message to the second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving a measurement report indicating communication degradation, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The communication manager 820 may be configured to or otherwise support a component for sending a third message to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established based on a relay connection between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity.

[0172] Additionally or alternatively, the communication manager 820 may support wireless communication at the second network entity according to the examples disclosed herein. For example, the communication manager 820 may be configured to or otherwise support a component for receiving a first message from the first network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The communication manager 820 may be configured to or otherwise support a component for sending a second message to the first network entity indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity, as part of switching the connection between the first UE and the first network entity to a connection between the first UE and the second network entity. The communication manager 820 may be configured or otherwise support means for communicating with the first UE via the second UE based on sending the second message.

[0173] By including or configuring a communications manager 820 according to examples as described herein, the device 805 may support techniques for network coordination during path switching and multipath scenarios, which may result in improved communications reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient utilization of communications resources, improved coordination between devices, longer battery life, and improved utilization of processing power, among other advantages.

[0174] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 810, one or more antennas 815 (e.g., where applicable), or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by the processor 835, the memory 825, the code 830, the transceiver 810, or any combination thereof. For example, the code 830 may include instructions that are executable by the processor 835 to cause the device 805 to perform various aspects of network coordination during path switching and multipath scenarios as described herein, or the processor 835 and the memory 825 may be otherwise configured to perform or support such operations.

[0175] Fig. 9 A flow chart illustrating a method 900 for supporting network coordination during path switching and multipath scenarios according to one or more aspects of the present disclosure is shown. The operations of the method 900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 900 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 8 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0176] At 905, the method may include: receiving from the first UE a first message including a measurement report indicating that communication between the first UE and the first network entity is degraded. The operations of 905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed as described in reference to Figure 7 The described reporting component 725 is executed.

[0177] At 910, the method may include: sending a second message to a second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving a measurement report indicating communication degradation, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The operations of 910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed as described in reference to Figure 7 The described connection request component 730 is executed.

[0178] At 915, the method may include: sending a third message to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an assignment of the first UE at the second network entity, and the assignment of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of switching a connection between the first UE and the first network entity and a connection between the first UE and the second network entity. The operations of 915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 915 may be performed as described in reference to Figure 7 The described connection switching component 735 is performed.

[0179] Fig.10 A flow chart illustrating a method 1000 for supporting network coordination during path switching and multipath scenarios according to one or more aspects of the present disclosure is shown. The operations of the method 1000 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1000 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 8 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0180] At 1005, the method may include: receiving from the first UE a first message including a measurement report indicating that communication between the first UE and the first network entity is degraded. The operations of 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed as described in reference to Figure 7 The described reporting component 725 is executed.

[0181] At 1010, the method may include: sending a second message to a second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based on receiving a measurement report indicating communication degradation, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The operations of 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed as described in reference to Figure 7 The described connection request component 730 is executed.

[0182] At 1015, the method may include: receiving, from the second network entity and in response to sending the second message, a fourth message confirming the second message, the fourth message indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE. The operations of 1015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed as described in reference to Figure 7 The described connection confirmation component 740 is executed.

[0183] At 1020, the method may include: sending a third message to the first UE indicating a third identifier associated with the first UE and a second identifier associated with the second UE, wherein the third identifier associated with the first UE is based on an assignment of the first UE at the second network entity, and the assignment of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of handing over a connection between the first UE and the first network entity and a connection between the first UE and the second network entity. The operations of 1020 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1020 may be performed as described in reference to Figure 7 The described connection switching component 735 is performed.

[0184] Fig.11 A flow chart illustrating a method 1100 for supporting network coordination during path switching and multipath scenarios according to one or more aspects of the present disclosure is shown. The operations of the method 1100 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1100 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 8 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0185] At 1105, the method may include: receiving, from a first network entity, a first message for switching a connection between a first UE and the first network entity to a connection between the first UE and a second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The operations of 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed as described in reference to Figure 7 The described connection request component 730 is executed.

[0186] At 1110, the method may include: sending a second message to the first network entity indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an assignment of the first UE at the second network entity, and the assignment of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of handing over a connection between the first UE and the first network entity and a connection between the first UE and the second network entity. The operations of 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed as described with reference to Figure 7 The described connection confirmation component 740 is executed.

[0187] At 1115, the method may include communicating with the first UE via the second UE based on sending the second message. The operations of 1115 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1115 may be performed as described in reference Figure 7 The described connection switching component 735 is performed.

[0188] Fig.12 A flow chart illustrating a method 1200 for supporting network coordination during path switching and multipath scenarios according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 8 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0189] At 1205, the method may include: receiving, from a first network entity, a first message for switching a connection between a first UE and the first network entity to a connection between the first UE and a second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first CU and the second network entity is associated with a second CU different from the first CU. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Figure 7 The described connection request component 730 is executed.

[0190] At 1210, the method may include: selecting a second UE from a set of multiple UEs associated with a set of identifiers, wherein the set of multiple UEs is associated with respective candidate relay connections between the first UE and the second network entity. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference Figure 7 The relay selection component 750 is described to perform.

[0191] At 1215, the method may include: sending a second message to the first network entity indicating a first identifier associated with the first UE, a second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based on an assignment of the first UE at the second network entity, and the assignment of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of handing over a connection between the first UE and the first network entity and a connection between the first UE and the second network entity. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Figure 7 The described connection confirmation component 740 is executed.

[0192] At 1220, the method may include communicating with the first UE via the second UE based on sending the second message. The operations of 1220 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1220 may be performed as described in reference to Figure 7 The described connection switching component 735 is performed.

[0193] The following provides an overview of various aspects of the disclosure:

[0194] Aspect 1: A method for wireless communication at a first network entity, the method comprising: receiving a first message from a first UE including a measurement report indicating a degradation of communication between the first UE and the first network entity; sending a second message to a second network entity for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity based at least in part on receiving the measurement report indicating the degradation of communication, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first central unit and the second network entity is associated with a second central unit different from the first central unit; and sending a third message to the first UE indicating a third identifier associated with the first UE and the second identifier associated with the second UE, wherein the third identifier associated with the first UE is based at least in part on an allocation of the first UE at the second network entity, the allocation of the third identifier to the first UE being established according to a relay connection between the first UE, the second UE and the second network entity as part of switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity.

[0195] Aspect 2: According to the method described in Aspect 1, the method further includes: receiving a fourth message confirming the second message from the second network entity and in response to sending the second message, the fourth message indicating the first identifier associated with the first UE, the second identifier associated with the second UE, and the third identifier associated with the first UE.

[0196] Aspect 3: A method according to Aspect 2, wherein receiving the fourth message includes: receiving an indication of side link control group resources associated with the relay connection between the first UE, the second UE and the second network entity, wherein the third message includes the indication of the side link control group resources.

[0197] Aspect 4: A method according to any one of Aspects 1 to 3, wherein receiving the first message including the measurement report includes: receiving the first message from the first UE via a third UE, wherein switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity includes: switching the second relay connection between the first UE, the third UE and the first network entity to the relay connection between the first UE, the second UE and the second network entity.

[0198] Aspect 5: A method according to any one of Aspects 1 to 4, wherein receiving the first message includes: receiving an indication of a set of identifiers associated with multiple UEs, wherein the multiple UEs are associated with corresponding candidate relay connections between the first UE and the second network entity.

[0199] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method further includes: sending a fourth identifier associated with the first UE to the second network entity, wherein the fourth identifier associated with the first UE is at least partially based on updating the first identifier associated with the first UE.

[0200] Aspect 7: The method according to any one of aspects 1 to 6, wherein the first network entity comprises a source network node for a handover operation, and the second network entity comprises a target network node for the handover operation.

[0201] Aspect 8: A method for wireless communication at a second network entity, the method comprising: receiving a first message from a first network entity for switching a connection between a first UE and the first network entity to a connection between the first UE and the second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first central unit and the second network entity is associated with a second central unit different from the first central unit; sending a second message to the first network entity indicating the first identifier associated with the first UE, the second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is at least partially based on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE and the second network entity as part of switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity; and communicating with the first UE via the second UE based at least in part on sending the second message.

[0202] Aspect 9: According to the method according to aspect 8, the method further comprises: selecting the second UE from a plurality of UEs associated with the set of identifiers, wherein the plurality of UEs are associated with corresponding candidate relay connections between the first UE and the second network entity.

[0203] Aspect 10: According to any one of Aspects 8 to 9, the method further includes: sending a third message to the second UE indicating the first identifier associated with the first UE and the third identifier associated with the first UE, wherein establishing the relay connection between the first UE, the second UE and the second network entity as part of switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity is at least partially based on the third message.

[0204] Aspect 11: According to the method according to aspect 10, the method further includes: receiving a request for the third identifier associated with the first UE from the second UE, wherein receiving the request is at least partly based on the second UE being in an inactive mode or an idle mode.

[0205] Aspect 12: According to any one of Aspects 8 to 11, the method further includes: detecting an operating state of the second UE, wherein establishing the relay connection between the first UE, the second UE and the second network entity as part of switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity is at least partially based on the operating state of the second UE.

[0206] Aspect 13: The method according to aspect 12, wherein the operating state of the second UE is associated with an active mode, an inactive mode, or an idle mode.

[0207] Aspect 14: According to any one of Aspects 8 to 13, the method further includes: receiving a fourth identifier associated with the first UE from the first network entity, wherein the fourth identifier associated with the first UE is at least partially based on updating the first identifier associated with the first UE.

[0208] Aspect 15: A method according to any one of Aspects 8 to 14, wherein sending the second message comprises: sending an indication of sidelink control group resources associated with the relay connection between the first UE, the second UE and the second network entity.

[0209] Aspect 16: An apparatus for wireless communication at a first network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 7.

[0210] Aspect 17: An apparatus for wireless communication at a first network entity, the apparatus comprising: at least one means for performing the method according to any one of aspects 1 to 7.

[0211] Aspect 18: A non-transitory computer-readable medium storing code for wireless communication at a first network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 7.

[0212] Aspect 19: An apparatus for performing wireless communications at a second network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 8 to 15.

[0213] Aspect 20: An apparatus for wireless communication at a second network entity, the apparatus comprising at least one means for performing the method according to any one of aspects 8 to 15.

[0214] Aspect 21: A non-transitory computer-readable medium storing code for wireless communication at a second network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 8 to 15.

[0215] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0216] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0217] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0218] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0219] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0220] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transmitted from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0221] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0222] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0223] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label, or other subsequent reference labels.

[0224] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described technology. However, these technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0225] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a first network entity, the method comprising: receiving, from a first user equipment (UE), a first message including a measurement report indicating a degradation of communications between the first UE and the first network entity; sending, based at least in part on receiving the measurement report indicating the degradation of communications, to a second network entity a second message for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with a second UE, wherein the first network entity is associated with a first central unit and the second network entity is associated with a second central unit different from the first central unit; and sending a third message to the first UE indicating a third identifier associated with the first UE and the second identifier associated with the second UE, wherein the third identifier associated with the first UE is based at least in part on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of handing over the connection between the first UE and the first network entity to the connection between the first UE and the second network entity.

2. The method according to claim 1, further comprising: A fourth message confirming the second message is received from the second network entity and in response to sending the second message, the fourth message indicating the first identifier associated with the first UE, the second identifier associated with the second UE, and the third identifier associated with the first UE.

3. The method of claim 2, wherein receiving the fourth message comprises: receiving an indication of sidelink control set resources associated with the relay connection between the first UE, the second UE, and the second network entity, wherein the third message includes the indication of the sidelink control set resources.

4. The method of claim 1 , wherein receiving the first message including the measurement report comprises: The first message is received from the first UE via the third UE, wherein the connection between the first UE and the first network entity is switched to the connection between the first UE and the second network entity, including: switching the second relay connection between the first UE, the third UE and the first network entity to the relay connection between the first UE, the second UE and the second network entity.

5. The method of claim 1 , wherein receiving the first message comprises: An indication of the set of identifiers associated with a plurality of UEs is received, wherein the plurality of UEs are associated with respective candidate relay connections between the first UE and the second network entity.

6. The method according to claim 1, further comprising: A fourth identifier associated with the first UE is sent to the second network entity, wherein the fourth identifier associated with the first UE is based at least in part on updating the first identifier associated with the first UE.

7. The method of claim 1, wherein the first network entity comprises a source network node for a handover operation, and the second network entity comprises a target network node for the handover operation.

8. A method for wireless communication at a second network entity, the method comprising: receiving, from a first network entity, a first message for switching a connection between a first UE and the first network entity to a connection between the first UE and a second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first central unit and the second network entity is associated with a second central unit different from the first central unit; sending a second message to the first network entity indicating the first identifier associated with the first UE, the second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based at least in part on an assignment of the first UE at the second network entity, the assignment of the third identifier to the first UE being established according to a relay connection between the first UE, the second UE, and the second network entity as part of handing over the connection between the first UE and the first network entity to the connection between the first UE and the second network entity; as well as Communicating with the first UE via the second UE based at least in part on sending the second message.

9. The method according to claim 8, further comprising: The second UE is selected from a plurality of UEs associated with the set of identifiers, wherein the plurality of UEs are associated with respective candidate relay connections between the first UE and the second network entity.

10. The method according to claim 8, further comprising: and sending a third message to the second UE indicating the first identifier associated with the first UE and the third identifier associated with the first UE, wherein establishing the relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity is based at least in part on the third message.

11. The method according to claim 10, further comprising: A request is received from the second UE for the third identifier associated with the first UE, wherein receiving the request is based at least in part on the second UE being in an inactive mode or an idle mode.

12. The method according to claim 8, further comprising: detecting an operational state of the second UE, wherein establishing the relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity is based at least in part on the operational state of the second UE.

13. The method of claim 12, wherein the operating state of the second UE is associated with an active mode, an inactive mode, or an idle mode.

14. The method according to claim 8, further comprising: A fourth identifier associated with the first UE is received from the first network entity, wherein the fourth identifier associated with the first UE is based at least in part on updating the first identifier associated with the first UE.

15. The method of claim 8, wherein sending the second message comprises: Sending an indication of sidelink control group resources associated with the relay connection between the first UE, the second UE, and the second network entity.

16. An apparatus for wireless communication at a first network entity, the apparatus comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from a first user equipment (UE), a first message including a measurement report indicating a degradation of communications between the first UE and the first network entity; sending, based at least in part on receiving the measurement report indicating the degradation of communications, to a second network entity a second message for switching a connection between the first UE and the first network entity to a connection between the first UE and the second network entity, the second message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with a second UE, wherein the first network entity is associated with a first central unit and the second network entity is associated with a second central unit different from the first central unit; and sending a third message to the first UE indicating a third identifier associated with the first UE and the second identifier associated with the second UE, wherein the third identifier associated with the first UE is based at least in part on an allocation of the first UE at the second network entity, and the allocation of the third identifier to the first UE is established according to a relay connection between the first UE, the second UE, and the second network entity as part of handing over the connection between the first UE and the first network entity to the connection between the first UE and the second network entity.

17. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: A fourth message confirming the second message is received from the second network entity and in response to sending the second message, the fourth message indicating the first identifier associated with the first UE, the second identifier associated with the second UE, and the third identifier associated with the first UE.

18. The apparatus of claim 17, wherein the instructions to receive the fourth message are executable by the processor to cause the apparatus to: receiving an indication of sidelink control set resources associated with the relay connection between the first UE, the second UE, and the second network entity, wherein the third message includes the indication of the sidelink control set resources.

19. The apparatus of claim 16, wherein the instructions to receive the first message including the measurement report are executable by the processor to cause the apparatus to: receiving the first message from the first UE via a third UE, wherein switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity comprises: The second relay connection between the first UE, the third UE and the first network entity is handed over to the relay connection between the first UE, the second UE and the second network entity.

20. The apparatus of claim 16, wherein the instructions to receive the first message are executable by the processor to cause the apparatus to: An indication of the set of identifiers associated with a plurality of UEs is received, wherein the plurality of UEs are associated with respective candidate relay connections between the first UE and the second network entity.

21. The apparatus of claim 16, wherein the instructions are further executable by the processor to cause the apparatus to: A fourth identifier associated with the first UE is sent to the second network entity, wherein the fourth identifier associated with the first UE is based at least in part on updating the first identifier associated with the first UE.

22. The apparatus of claim 16, wherein the first network entity comprises a source network node for a handover operation, and the second network entity comprises a target network node for the handover operation.

23. An apparatus for wireless communication at a second network entity, the apparatus comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from a first network entity, a first message for switching a connection between a first UE and the first network entity to a connection between the first UE and a second network entity, the first message indicating a set of identifiers including at least a first identifier associated with the first UE and a second identifier associated with the second UE, wherein the first network entity is associated with a first central unit and the second network entity is associated with a second central unit different from the first central unit; sending a second message to the first network entity indicating the first identifier associated with the first UE, the second identifier associated with the second UE, and a third identifier associated with the first UE, wherein the third identifier associated with the first UE is based at least in part on an assignment of the first UE at the second network entity, the assignment of the third identifier to the first UE being established according to a relay connection between the first UE, the second UE, and the second network entity as part of handing over the connection between the first UE and the first network entity to the connection between the first UE and the second network entity; as well as Communicating with the first UE via the second UE based at least in part on sending the second message.

24. The apparatus of claim 23, wherein the instructions are further executable by the processor to cause the apparatus to: The second UE is selected from a plurality of UEs associated with the set of identifiers, wherein the plurality of UEs are associated with respective candidate relay connections between the first UE and the second network entity.

25. The apparatus of claim 23, wherein the instructions are further executable by the processor to cause the apparatus to: and sending a third message to the second UE indicating the first identifier associated with the first UE and the third identifier associated with the first UE, wherein establishing the relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity is based at least in part on the third message.

26. The apparatus of claim 25, wherein the instructions are further executable by the processor to cause the apparatus to: A request is received from the second UE for the third identifier associated with the first UE, wherein receiving the request is based at least in part on the second UE being in an inactive mode or an idle mode.

27. The apparatus of claim 23, wherein the instructions are further executable by the processor to cause the apparatus to: detecting an operational state of the second UE, wherein establishing the relay connection between the first UE, the second UE, and the second network entity as part of switching the connection between the first UE and the first network entity to the connection between the first UE and the second network entity is based at least in part on the operational state of the second UE.

28. The apparatus of claim 27, wherein the operating state of the second UE is associated with an active mode, an inactive mode, or an idle mode.

29. The apparatus of claim 23, wherein the instructions are further executable by the processor to cause the apparatus to: A fourth identifier associated with the first UE is received from the first network entity, wherein the fourth identifier associated with the first UE is based at least in part on updating the first identifier associated with the first UE.

30. The apparatus of claim 23, wherein the instructions to send the second message are executable by the processor to cause the apparatus to: Sending an indication of sidelink control group resources associated with the relay connection between the first UE, the second UE, and the second network entity.