Addressing the ambiguity of user equipment service location during mobility processes

Abstract

Methods, systems, and apparatus for conducting wireless communication are described. A first source network entity may obtain an indication from a user equipment (UE) regarding a lower-layer triggered mobility (LTM) procedure that has occurred, wherein the UE transfers a communication session from a second source network entity to the first source network entity. The first source network entity may output one or more access notifications to one or more candidate network entities and obtain one or more updated configuration indications from at least one of the one or more candidate network entities. The one or more updated configuration indications indicate updated LTM mobility procedure information at one or more of the one or more candidate network entities. In some examples, one or more candidate network entities, anchor network entities, or combinations thereof may obtain and output access notifications and updated configuration indications.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 19 / 044,261, filed February 3, 2025, entitled “RESOLVING AMBIGUITY OF USER EQUIPMENT SERVING LOCATION IN MOBILITY PROCEDURES,” which claims the benefit of U.S. Provisional Patent Application No. 63 / 569,679, filed March 25, 2024, entitled “RESOLVING AMBIGUITY OF USER EQUIPMENT SERVING LOCATION IN MOBILITY PROCEDURES,” which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including addressing the ambiguity of user equipment service locations during mobility processes. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can 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, LTE-A Advanced (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 technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0005] A UE can communicate with one or more network entities. A UE can transfer communication from one network entity to another via mobility procedures such as handover procedures. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting the resolution of ambiguity in the service location of a User Equipment (UE) during mobility processes. For example, the described technology provides a lower-layer triggered mobility (LTM) process between one or more network entities and the UE. The network entity may be a source network entity, a candidate network entity, an anchor network entity, etc.

[0007] A method performed by a first source network entity is described. The method may include: obtaining from a user equipment (UE) an indication that a lower-layer triggered mobility (LTM) procedure has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to the first source network entity; outputting one or more access notifications to one or more candidate network entities, at least in part based on the UE transferring the communication session; and obtaining one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0008] A first source network entity is described. The first source network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the first source network entity to: obtain from a UE an indication that an LTM procedure has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to the first source network entity; output one or more access notifications to one or more candidate network entities based on the UE transferring the communication session; and obtain one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0009] Another first source network entity is described. This first source network entity may include: components for one or more memories storing processor-executable code; components for one or more processors coupled to the one or more memories; and components for obtaining from a UE an indication of an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to the first source network entity; components for outputting one or more access notifications to one or more candidate network entities, at least in part based on the UE transferring the communication session; and components for obtaining one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0010] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to: obtain from a UE an indication of an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to the first source network entity; output one or more access notifications to one or more candidate network entities based on the UE transferring the communication session; and obtain one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0011] In some examples of the methods, first source network entities, and non-transitory computer-readable media described herein, outputting the one or more access notifications may include operations, features, components, or instructions for: outputting a first access notification to the second source network entity; and outputting one or more second access notifications to one or more other network entities, wherein the first access notification indicates that the communication session has been successfully delivered to the first source network entity, and wherein the one or more second access notifications indicate that the first source network entity may be a serving entity of the UE.

[0012] In some examples of the methods described herein, the first source network entity, and the nontransitory computer-readable medium, outputting the one or more access notifications may include operations, features, components, or instructions for outputting the first access notification to the second source network entity, wherein obtaining the one or more updated configuration indications may also be based on signaling sent from the second source network entity to one or more candidate network entities in response to the first access notification.

[0013] In some examples of the methods described herein, the first source network entity, and non-transitory computer-readable media, one or more reconfiguration messages are output to the UE based on the one or more updated configuration indications.

[0014] In some examples of the methods described herein, the first source network entity, and non-transitory computer-readable media, the one or more reconfiguration messages include Radio Resource Control (RRC) signaling.

[0015] The methods described herein, examples of first-source network entities, and non-transitory computer-readable media may also include operations, features, components, or instructions for obtaining the instruction from the UE, which may also be based on a previous mobility process in addition to a successful LTM process.

[0016] A method for wireless communication by a first source network entity is described. The method may include: obtaining from a UE an indication of an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to the first source network entity; outputting one or more access notifications to one or more candidate network entities based on the UE transferring the communication session; and obtaining one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0017] A first source network entity for wireless communication is described. The first source network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the first source network entity to: obtain from a UE an indication that an LTM procedure has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to the first source network entity; output one or more access notifications to one or more candidate network entities based on the UE transferring the communication session; and obtain one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0018] Another first source network entity for wireless communication is described. This first source network entity may include: components for obtaining an indication from a UE regarding an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to the first source network entity; components for outputting one or more access notifications to one or more candidate network entities based on the UE transferring the communication session; and components for obtaining one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0019] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: obtain from a UE an indication of an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to the first source network entity; output one or more access notifications to one or more candidate network entities based on the UE transferring the communication session; and obtain one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0020] In some examples of the methods, first source network entities, and non-transitory computer-readable media described herein, outputting the one or more access notifications may include operations, features, components, or instructions for: outputting a first access notification to the second source network entity; and outputting one or more second access notifications to one or more other network entities, wherein the first access notification indicates that the communication session has been successfully delivered to the first source network entity, and wherein the one or more second access notifications indicate that the first source network entity may be a serving entity of the UE.

[0021] In some examples of the methods described herein, the first source network entity, and the nontransitory computer-readable medium, outputting the one or more access notifications may include operations, features, components, or instructions for outputting the first access notification to the second source network entity, wherein obtaining the one or more updated configuration indications may also be based on signaling sent from the second source network entity to one or more candidate network entities in response to the first access notification.

[0022] The methods described herein, examples of first-source network entities, and non-transitory computer-readable media may also include operations, features, components, or instructions for outputting one or more reconfiguration messages to the UE based on the one or more updated configuration indications.

[0023] In some examples of the methods described herein, the first source network entity, and non-transitory computer-readable media, the one or more reconfiguration messages include radio RRCs.

[0024] The methods described herein, examples of first-source network entities, and non-transitory computer-readable media may also include operations, features, components, or instructions for obtaining the instruction from the UE, which may also be based on a previous mobility process in addition to a successful LTM process.

[0025] A method for wireless communication by a device is described. The method may include: obtaining from a UE an indication of an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to a first source network entity; outputting one or more access notifications to one or more candidate network entities, at least in part based on the UE transferring the communication session; and obtaining one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0026] An apparatus for wireless communication is described. The apparatus may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to enable the apparatus to: obtain from a UE an indication that an LTM procedure has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to a first source network entity; output one or more access notifications to one or more candidate network entities based on the UE transferring the communication session; and obtain one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0027] Another apparatus for wireless communication is described. The apparatus may include: components for obtaining from a UE an indication of an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to a first source network entity; components for outputting one or more access notifications to one or more candidate network entities, at least in part based on the UE transferring the communication session; and components for obtaining one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0028] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: obtain from a UE an indication of an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to a first source network entity; output one or more access notifications to one or more candidate network entities based on the UE transferring the communication session; and obtain one or more updated configuration indications from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0029] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, outputting the one or more access notifications may include operations, features, components, or instructions for: outputting a first access notification to the second source network entity; and outputting one or more second access notifications to one or more other network entities, wherein the first access notification indicates that the communication session has been successfully delivered to the first source network entity, and wherein the one or more second access notifications indicate that the first source network entity may be a serving entity of the UE.

[0030] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, outputting the one or more access notifications may include operations, features, components, or instructions for: outputting a first access notification to the second source network entity, wherein obtaining the one or more updated configuration indications may also be based on signaling sent from the second source network entity to one or more candidate network entities in response to the first access notification.

[0031] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, one or more reconfiguration messages are output to the UE based on the one or more updated configuration instructions.

[0032] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the one or more reconfiguration messages include radio RRCs.

[0033] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining the instruction from the UE, which may also be based on a previous mobility process in addition to a successful LTM process. Attached Figure Description

[0034] Figure 1 An example of a wireless communication system that supports resolving ambiguity in the service location of a user equipment (UE) during mobility processes is shown, according to one or more aspects of this disclosure.

[0035] Figure 2 An example of a wireless communication system that supports resolving ambiguity of UE service location during mobility processes is shown, according to one or more aspects of this disclosure.

[0036] Figure 3 An example flowchart of a process for resolving ambiguity in the UE service location during mobility procedures, according to one or more aspects of this disclosure, is shown.

[0037] Figure 4 An example flowchart of a process for resolving ambiguity in the UE service location during mobility procedures, according to one or more aspects of this disclosure, is shown.

[0038] Figure 5 An example flowchart of a process for resolving ambiguity in the UE service location during mobility procedures, according to one or more aspects of this disclosure, is shown.

[0039] Figure 6 An example flowchart of a process for resolving ambiguity in the UE service location during mobility procedures, according to one or more aspects of this disclosure, is shown.

[0040] Figure 7 An example flowchart of a process for resolving ambiguity in the UE service location during mobility procedures, according to one or more aspects of this disclosure, is shown.

[0041] Figure 8 and Figure 9 A block diagram of an apparatus for resolving ambiguity of UE service location during mobility processes, according to one or more aspects of this disclosure, is shown.

[0042] Figure 10 A block diagram of a mobility communication manager supporting the resolution of ambiguity in the UE service location during mobility processes, according to one or more aspects of this disclosure, is shown.

[0043] Figure 11 A diagram is shown of a system including an apparatus for supporting the resolution of ambiguity in the UE's service location during mobility processes, according to one or more aspects of this disclosure.

[0044] Figures 12 to 14 A flowchart illustrating a method for resolving ambiguity in the UE service location during mobility processes, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0045] A User Equipment (UE) can move from the coverage area of ​​one network entity or cell to the coverage area of ​​another network entity or cell. To continue communication with the network, the UE can connect to a new network entity (e.g., source, destination, serving). Various procedures, such as conditional handover procedures or lower-layer triggered mobility (LTM) procedures, can be used to transfer a communication session from one network entity to another. Multiple candidate network entities can be configured to serve the UE, while in some examples, one network entity may serve as the current source or serving network entity. In some examples, candidate cells may have outdated configuration information regarding when a candidate cell or network entity was first configured for a mobility procedure. For example, a UE may be configured to complete a conditional handover from a first source network entity to a second network entity, and a third network entity may have outdated configuration information. If the UE's conditional handover has not yet been triggered, and the UE's source network entity has not changed, the third network entity may send a message to the first source network entity indicating that the conditional handover configuration at the third network entity is outdated. If the UE has been triggered to be handed over to the second network entity, the first network entity may send a cancellation message to the third network entity, indicating that the outdated conditional handover configuration is no longer relevant and that the second network entity is the source network entity. In such an example, after the conditional handover process, changes to the source network entity used for the UE are used to update the third network entity.

[0046] Another mobility procedure is LTM (Local Time Management), in which the UE may not release stored LTM configuration information of a network entity unless explicitly instructed to do so. LTM can be implemented at lower layers (such as Layer 1 and Layer 2). During LTM, the source network entity can notify the UE of any configuration updates for candidate cells. However, if a third network entity has outdated configuration information for the UE, the third network entity may not be able to update information about which network entity is the UE's current source network entity and may not be able to notify the source network entity of any updates. In such examples, there is ambiguity regarding the third network entity with outdated configuration information or any candidate network entity.

[0047] The techniques described herein provide signaling between network entities configured for the LTM procedure to communicate updated cell handover information and configuration. The UE can receive an LTM configuration from a source network entity, instructing the UE to transfer its communication session from the source network entity to a new source network entity. As part of the LTM procedure, the UE can contact the new source network entity. After a successful LTM, the network entity can communicate the updated configuration information, and the source network entity can reconfigure the UE.

[0048] In the first example, a new source network entity may notify a previous source network entity, other candidate network entities, or both of a successful LTM. In some examples, the previous source network entity may forward the notification to candidate network entities. In the second example, a candidate network entity with outdated information may output an updated configuration indication to one or more other candidate network entities without receiving any updates. For example, the candidate network entity may output a broadcast message or may query to identify the source network entity. In the third example, a network entity may be designated as an anchor and forward the updated configuration indication. For example, the anchor network entity may receive an update from a candidate network entity and forward that update to the source network entity or all candidate network entities. In some examples, the anchor network entity may query to identify the source network entity before forwarding any updates. Such techniques address the ambiguity regarding UE location information used in the LTM procedure.

[0049] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated by process flowcharts, apparatus diagrams, system diagrams, and flowcharts relating to resolving ambiguities in the UE serving location during mobility processes, and are described with reference to these process flowcharts, apparatus diagrams, system diagrams, and flowcharts.

[0050] Figure 1An example of a wireless communication system 100 supporting the resolution of ambiguity regarding the UE's serving location during mobility processes is illustrated, according to one or more aspects of this disclosure. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 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 under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0051] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0052] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are shown below. Figure 1 As shown, the UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including the UE 115 or network entity 105).

[0053] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or 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, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

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

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

[0056] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize a protocol stack physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and 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, network entity 105 may include one or more of the following: a Central Unit (CU) (such as CU 160), a Distributed Unit (DU) (such as DU 165), a Radio Unit (RU) (such as RU 170), a RAN Intelligent Controller (RIC) (such as RIC 175) (e.g., a near real-time RIC (near RTRIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system (such as SMO system 180), or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0057] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) can connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both can 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 can each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split may be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0058] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can 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 in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support 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 cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0059] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include one or more of CU 160, DU 165, and RU 170, in which case CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with core network 130 via an interface (which may be part of a backhaul link) and may communicate with other CUs (e.g., including CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be another part of a backhaul link).

[0060] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay UE transmissions through other IAB nodes 104). Additionally or alternatively, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104, depending on the AN's relay chain or configuration. The IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB nodes (e.g., IAB node 104) to receive signaling from parent IAB nodes (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB nodes to send signaling notifications to child IAB nodes or UE 115.

[0061] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 with a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT of IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or DU 165 of IAB node 104.

[0062] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

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

[0064] The UE 115 described herein may be able to communicate with various types of devices, such as the UE 115 which may sometimes operate as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

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

[0066] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and 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 decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0067] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0068] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be 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 symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

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

[0070] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can 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 set may include a public search space set configured to transmit control information to UE115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

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

[0072] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and can allow unrestricted access for UE 115 that has a service subscription with a network provider supporting the macro cell. Small cells may be associated with network entities 105 that operate at lower power relative to macro cells (e.g., base station 140 operating at lower power), and small cells may operate using the same or different (e.g., licensed or unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or may provide restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0073] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0074] In some examples, network entity 105 (e.g., base station 140, RU 170) can be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) can overlap, but coverage areas 110 (e.g., different coverage areas) can be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies can be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 support communication in coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0075] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, 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 prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0076] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as 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 performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, where each UE 115 sends to one or more UEs within the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0077] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can 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), 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), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0078] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0079] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0080] 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 techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation 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, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include 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 transmitted via the antenna ports.

[0081] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a particular orientation of the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., for the antenna array of the transmitting or receiving device or for some other orientation).

[0082] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0083] The techniques described herein provide signaling between network entities 105 configured for the LTM procedure to communicate updated cell handover information and configuration. UE 115 may receive an LTM configuration from a source network entity 105 instructing UE 115 to transfer a communication session from the source network entity to a new source network entity 105. As part of the LTM procedure, UE 115 may contact the new source network entity 105. After a successful LTM, network entity 105 may communicate updated configuration information, and source network entity 105 may reconfigure UE 115. For example, the new source network entity 105 may communicate changes to the source network entity 105 to one or more candidate network entities 105, one or more candidate network entities 105 may indicate configuration information updates to one or more other candidate network entities 105, anchor network entity 105 may forward information between candidate network entities 105, or a combination thereof.

[0084] Figure 2An example of a wireless communication system 200 supporting the resolution of ambiguity regarding the UE's serving location during mobility procedures, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 describes communication between a candidate network entity 220 and a UE 115-a. The candidate network entity 220 may include network entity 105-a, network entity 105-b, and network entity 105-c, which may be as described in reference... Figure 1 An example of network entity 105 as described. UE 115-a can be as shown in the reference. Figure 1 An example of UE 115 as described.

[0085] As described herein, candidate network entities 220 may include more than the number described (e.g., there may be 4, 5, 6, etc.) network entities 105. The labels “candidate,” “source,” and “anchor,” as well as other descriptors, of network entities 105 are used to clarify functionality and are not restrictive. For example, any candidate network entity in candidate network entity 220 may be a source network entity.

[0086] Candidate network entity 220 may communicate with UE 115-a via communication link 205 (e.g., communication link 205-a, communication link 205-b). In some examples, network entity 105-a may communicate with UE 115-a via communication link 205-a, and network entity 105-b may communicate with UE 115-a via communication link 205-b. UE 115-a may stop communication with network entity 105-a and begin communication with network entity 105-b (e.g., a communication session). Movement or transfer at 210 may be an example of a mobility procedure (such as an LTM procedure).

[0087] UE 115-a can transfer or move communication from one network entity 105 to another. The procedures for transferring communication include conditional handover and LTM. Conditional handover can have various constraints, such as constraints on mobility between cells within the same network entity 105 (e.g., intra-gNB constraints, where a gNB may include a CU and one or more DUs), and constraints on the measurement of handover for specific resources. Improving mobility between network entities 105 (e.g., cells) can be advantageous, including supporting inter-gNB or inter-CU mobility procedures.

[0088] In some conditional handover applications, UE 115-a may communicate with or be served by network entity 105-a, and may be configured using network entities 105-b and 105-c as conditional handover candidates. In some examples, each network entity 105-a may include one or more cells, such that UE 115-a may be served by a first cell of network entity 105-a.

[0089] Mobility configuration information (such as conditional handover information) for UE 115-a can be used to configure each network entity 105. The mobility configuration information can indicate that each network entity 105 is a candidate network entity among candidate network entities 220. In some examples, the configuration information may become outdated or inaccurate. For example, UE 115-a may be configured to perform a conditional handover procedure to move communication from source network entity 105-a to network entity 105-b, which could be a new source network entity 105. In some examples, mobility configuration information for candidate network entities (such as network entity 105-c) may become outdated. If the mobility configuration information for network entity 105-c becomes outdated during conditional handover, network entity 105-c may follow the steps of notifying the source network entity 105-a of the update.

[0090] In the first scenario, if the conditional handover process has not yet been triggered, network entity 105-c may send (e.g., transmit) a notification to network entity 105-a (which is the source network entity 105-a). In another scenario, if the conditional handover has been triggered, network entity 105-b is the serving cell, and network entity 105-c has not yet been updated to the change. In such an example, UE 115-a may delete all conditional handover configurations of all candidate network entities 220, and network entity 105-a that has participated in the conditional handover process may instruct network entity 105-c to remove (e.g., cancel, delete) the configuration information. In such an example, network entity 105 has the updated configuration information, or is notified when the information is outdated.

[0091] Another handover process could be an LTM process. For example, candidate network entity 220 could be configured as a candidate for an LTM process for UE 115-a. Network entity 105-a could be a source network entity communicating with UE 115-a. UE 115-a could be configured to perform an LTM process to transfer communication between candidate network entities 220, such as from network entity 105-a to network entity 105-b.

[0092] In some examples, the configuration of network entity 105-c may become outdated. To inform UE 115-a of its outdated configuration, UE 115-a may receive RRC signaling from the source network entity 105-a currently serving UE 115-a. In some examples, network entity 105-c may not have the updated serving location of UE 115-a, and therefore may not be able to notify network entity 105-a to inform UE 115-a of the outdated configuration.

[0093] The techniques described herein provide signaling and procedures for LTM candidate network entity 220 to convey indications of outdated configurations and resolve ambiguities in UE location information (e.g., which network entity is serving the UE at a given time). Such techniques reduce overhead signaling and latency.

[0094] In some examples, to resolve ambiguity regarding the UE's service location for LTM applications, candidate network entities 220 may be notified of a change in the service location of UE 115-a (e.g., UE 115-a is transferred from network entity 105-a to network entity 105-b). In some examples, any candidate network entity 220 with outdated configuration information may notify all other candidate network entities 220, regardless of the location of UE 115-a. In some examples, network entity 105 may be configured as an anchor network entity and may receive and forward notifications of outdated configurations among candidate network entities 220. Reference Figure 3 ‍‍– Figure 7 The signaling and technology are further described.

[0095] Figure 3 An example of a process flowchart 300 supporting the resolution of ambiguity regarding the UE's service location during mobility operations, according to one or more aspects of this disclosure, is shown. Process flowchart 300 describes the notification of updated LTM configuration information between network entities 105. UE 115-b can communicate with candidate network entities such as network entity A (e.g., network entity 105-d), network entity B (e.g., network entity 105-e), network entity C (e.g., network entity 105-f), and network entity D (e.g., network entity 105-g)). Network entity 105-a can be as described in reference... Figure 1 or Figure 2 An example of network entity 105 is described. UE 115-b can be as follows (refer to...) Figure 1 or Figure 2 Examples of UE 115 and UE 115-a are described below. In the following description of process flowchart 300, operations may be performed in different orders or at different times. Some operations may be omitted, and others may be added. Some aspects of some operations may be performed by one or more other wireless devices.

[0096] Network entity A, network entity B, network entity C, and network entity D can be examples of candidate network entities configured for the LTM process. Candidate network entities can be identified as source network entities. For example, see reference... Figure 3As described, network entity A can be the source network entity A relative to UE 115-b. UE 115-b can perform an LTM procedure to move communication from source network entity A (e.g., the original source) to a new source, such as network entity B. Network entities C and D can be candidate network entities configured for LTM procedures with UE 115-b. In some examples, such as reference... Figure 3 As described, network entities C and D may not be selected as source network entities for UE 115-b.

[0097] To resolve the ambiguity of UE 115-b's location, the new source network entity B may send (e.g., output) one or more access notifications after the LTM procedure. In some examples, the new source network entity B may send access notifications to network entities A, C, and D. In some examples, the new source network entity B may send access notifications to the original source network entity A, and network entity A may forward the access notifications to candidate network entities C and D. In some examples, before successfully transferring communication from the original source network entity A to the new source network entity B in the LTM procedure, UE 115-b may attempt an LTM procedure with a different candidate network entity (such as network entity C) and cause the LTM procedure to fail (e.g., as described with reference to steps 310–320).

[0098] At point 305, network entity A can be configured as the originating source network entity A for communicating with UE 115-b. Originating source network entity A can send LTM configuration to UE 115-b. The LTM configuration information can instruct UE 115-b to perform an LTM procedure to transfer a communication session from one network entity to another, such as from network entity A to network entity B or from network entity A to network entity C.

[0099] At 310, in some examples, UE 115-b may attempt to send an uplink message to network entity C. For example, the LTM configuration may have instructed UE 115-b to deliver the message to network entity C. The attempted uplink message may fail.

[0100] At 315-a and 315-b, a message failure could result in a radio link failure at both UE 115-b and network entity C. In such an example, at 320, UE 115-b could complete a network entity reselection. Although the radio link failure is provided as an example, an unsuccessful attempt to pass communication to network entity C can be an example of any type of mobility process other than a successful LTM delivery procedure.

[0101] At 325, UE 115-b may send an uplink message (e.g., an indication) to network entity B (e.g., the first source network entity). The uplink message may be an indication from UE 115-b regarding an LTM procedure that has occurred, wherein the LTM procedure includes UE 115-b transferring a communication session from the original source network entity A (e.g., the second source network entity) to a new source network entity B.

[0102] In some examples, network entity B may receive uplink messages or indications from UE 115-b based on a previous mobility procedure other than a successful LTM procedure. The previous mobility procedure may include a Layer 3 mobility procedure with a radio link failure or an LTM procedure. For example, uplink messages may be received in response to a radio link failure and network entity reselection (e.g., as described with reference to steps 3103–20). In some examples, there may be no procedure prior to the LTM procedure, such as when the LTM configuration indicates to UE 115-b that it is moving to a new source network entity B and that procedure is successful.

[0103] At 330, the new source network entity B may indicate (e.g., send, output) an access notification (e.g., a first access notification) to the original source network entity A. The access notification may indicate that communication with UE 115-b has been successfully delivered to the new source network entity B.

[0104] At point 335, the original source network entity A or the new source network entity B may send access notifications to candidate network entities C and D. In some examples, at point 335-a, network entity B sends access notifications (e.g., one or more second access notifications) to network entities C and D. Access notifications to candidate network entities C and D may indicate that network entity B is a new source (e.g., serving) network entity for UE 115-b. Access notifications to candidate network entities C and D may be transmitted simultaneously with access notifications to network entity A. Network entity B may send access notifications to network entities A, network entities C and D, or both, based on receiving an uplink message conveying a communication session for UE 115-b.

[0105] In some examples, at 335-b, an access notification indicating that network entity B is the source network entity can be indirectly conveyed to candidate network entities C and D. For example, the original network entity A may send or forward the access notification to network entities C and D based on receiving the access notification from network entity B, rather than the new source network entity B sending the access notification. In such examples, network entity A acts as an intermediary by forwarding the access notification from network entity B to network entities C and D, and network entity A can be an example of an anchor network entity.

[0106] At 340, network entity C may have or otherwise identify configuration updates. For example, network entity C may have outdated configuration information related to the LTM procedure used for UE 115-b.

[0107] At point 345, network entity C can indicate to the new source network entity B via an updated configuration instruction that the LTM configuration information at network entity C is outdated. Network entity B can receive the updated configuration instruction based on an access notification (from network entity A or B) sent to network entity C. Since the access notification informs network entity C that network entity B is the source network entity, network entity C indicates any configuration changes to the new source network entity B, rather than any configuration changes to the original source network entity A. The access notification removes ambiguity regarding the location of UE 115-b and enables network entity C to send updated configuration information to the current source network entity B.

[0108] At 350, network entity B can send reconfiguration messages, such as RRC reconfiguration messages, to UE 115-b based on the updated configuration indicated by network entity C.

[0109] At 355, similar to network entity C, network entity D may have configuration updates that identify outdated configuration information or otherwise.

[0110] At point 360, network entity D can indicate to the new source network entity B via an updated configuration instruction that the configuration information at network entity D is outdated. Network entity B can receive the updated configuration instruction based on an access notification.

[0111] At 365, network entity B can send configurations, such as RRC reconfiguration messages, to UE 115-b based on the updated configuration indicated by network entity D.

[0112] Figure 4 An example of a process flowchart 400 supporting the resolution of ambiguity regarding the UE's serving location during a mobility process, according to one or more aspects of this disclosure, is shown. Process flowchart 400 describes the communication of an updated configuration for the LTM process. UE 115-c can communicate with candidate network entities such as network entity A (e.g., network entity 105-d), network entity B (e.g., network entity 105-e), network entity C (e.g., network entity 105-f), and network entity D (e.g., network entity 105-g)). Network entity 105 can be as described in reference... Figures 1 to 3 Examples of network entity 105 described in any of the above. UE 115-c can be as shown in the reference. Figures 1 to 3Examples of any UE in UE 115 as described in any of the above. In the following description of process flowchart 400, operations may be performed in different orders or at different times. Some operations may be omitted, and others may be added. Some aspects of some operations may be performed by one or more other wireless devices.

[0113] Network entities A, B, C, and D can be configured for the LTM procedure of UE 115-c. In some examples, each network entity can receive (e.g., receive) an indication of configuration indicating that each network entity is a candidate network entity among one or more candidate network entities configured for the LTM procedure of UE 115-c. For example, network entity C (e.g., the first network entity) can receive an indication of configuration indicating that network entity C is a candidate network entity among candidate network entities. UE 115-c can transfer communication from network entity A to network entity B according to the LTM procedure. When a configuration update exists (e.g., outdated configuration information), candidate network entities C and D can send messages to other network entities.

[0114] At 405, network entity A can be the original source network entity A communicating with UE 115-b. The original source network entity A can send LTM configuration to UE 115-c. The LTM configuration information can instruct UE 115-c to move the communication session from one network entity to another, such as from network entity A to network entity B.

[0115] At 410, UE 115-b can send an uplink message to network entity B. The uplink message can be an indication from UE 115-c that an LTM procedure has occurred, where the LTM procedure includes UE 115-c transferring a communication session from network entity A to network entity B.

[0116] At point 415, the new source network entity B may indicate (e.g., send, output) an access notification (e.g., a first access notification) to the original source network entity A. The access notification may indicate that communication was successfully delivered to the new source network entity B.

[0117] At 420, network entity C can update the LTM process information associated with a previously configured LTM process. For example, the network entity may have outdated configuration information.

[0118] At 425, network entity C may output one or more updated configuration indications to at least one of one or more candidate network entities based on updated LTM procedure information. For example, network entity C may send updated configuration indications to network entities A, B, and D, indicating that network entity C has outdated configuration information. In some examples, the updated configuration indications may be broadcast to other network entities. In such examples, network entity C does not direct notifications to source network entity B because the LTM procedure has been completed and network entity C has not yet been updated to the location change of UE 115-c.

[0119] At 430, network entity B may send a reconfiguration message, such as an RRC reconfiguration message, to UE 115-c based on the updated configuration indicated by network entity C. Network entity B sends the reconfiguration based on the source network entity used for UE 115-c.

[0120] At position 435, similar to network entity C, network entity D can be a candidate network entity. Network entity D can update the LTM process information associated with a previously configured LTM process. For example, the network entity may have outdated configuration information.

[0121] At 440, network entity D can output one or more updated configuration indications to at least one of the candidate network entities based on updated LTM process information. For example, network entity D can send updated configuration indications to network entities A, B, and C, indicating that network entity D has outdated configuration information. In some examples, the updated configuration indications can be broadcast to other network entities.

[0122] At 445, network entity B can send a reconfiguration message, such as an RRC reconfiguration message, to UE 115-c based on the updated configuration indicated by network entity D.

[0123] Figure 5 An example of a process flowchart 500 supporting the resolution of ambiguity regarding the UE's service location during a mobility process, according to one or more aspects of this disclosure, is shown. Process flowchart 500 describes the communication of an updated configuration for the LTM process. UE 115-d can communicate with candidate network entities such as network entity A (e.g., network entity 105-d), network entity B (e.g., network entity 105-e), network entity C (e.g., network entity 105-f), and network entity D (e.g., network entity 105-g)). Network entity 105 can be as described in reference... Figures 1 to 4 Examples of network entity 105 described in any of the above. UE 115-d can be as shown in the reference. Figures 1 to 4Examples of UE 115 described in any of the above. In the following description of process flowchart 500, operations may be performed in different orders or at different times. Some operations may be omitted, and others may be added. Some aspects of some operations may be performed by one or more other wireless devices.

[0124] Network entities A, B, C, and D can be configured for the LTM procedure of UE 115-d. In some examples, each network entity can receive (e.g., receive) an indication of configuration indicating that each network entity is a candidate network entity among one or more candidate network entities configured for the LTM procedure of UE 115-d. For example, network entity C (e.g., the first network entity) can receive an indication of configuration indicating that network entity C is a candidate network entity among candidate network entities.

[0125] For reference Figure 5 As described, UE 115-d can complete the LTM procedure and transfer the communication session from network entity A to network entity B. Network entity C, without receiving notification of the LTM procedure, can perform a configuration update and query other network entities to locate the source network entity. Network entity C can receive an affirmative response from network entity B indicating that network entity B is the source network entity. The network entity can then send an updated configuration indication to the source network entity B. By querying before sending the updated configuration indication, network entity C only notifies the source network entity B, which can then reconfigure UE 115-d.

[0126] At 505, network entity A can be the original source network entity A communicating with UE 115-b. The original source network entity A can send LTM configuration to UE 115-c. The LTM configuration information can instruct UE 115-c to move the communication session from one network entity to another, such as from network entity A to network entity B.

[0127] At position 510, UE 115-b can send an uplink message to network entity B. The uplink message can be an indication from the UE that an LTM procedure has occurred, where the LTM procedure involves the UE transferring a communication session from network entity A to network entity B.

[0128] At point 515, the new source network entity B may indicate (e.g., send, output) an access notification (e.g., a first access notification) to the original source network entity A. The access notification may indicate that communication was successfully delivered to the new source network entity B.

[0129] At point 520, network entity C can update the LTM process information associated with a previously configured LTM process. For example, network entity C may have outdated configuration information.

[0130] At 525, network entity C may output (e.g., send) a query to one or more candidate network entities (e.g., network entities A, B, and D), the query including a request for an indication of whether the receiving network entity is the source network entity for UE 115-d.

[0131] At points 530, 535, and 540, network entity C can obtain (e.g., receive) response messages from network entities A, B, and D. The response messages can indicate whether the receiving network entity is the source network entity. For example, at point 530, network entity A can provide a negative response indicating that network entity A is not a source network entity. At point 535, network entity D can provide a negative response indicating that network entity D is not a source network entity. At point 540, network entity B can provide a positive response indicating that network entity B is a source network entity.

[0132] At 545, network entity C may output an updated configuration indication (e.g., a unicast message) to source network entity B based on a response message indicating that source network entity B is the source network entity for UE 115-d.

[0133] At 550, network entity B may send a reconfiguration message, such as an RRC reconfiguration message, to UE 115-d based on the updated configuration indicated by network entity C. Network entity B sends the reconfiguration based on the source network entity used for UE 115-d.

[0134] Figure 6 An example of a process flowchart 600 supporting the resolution of ambiguity regarding the UE's serving location during a mobility process, according to one or more aspects of this disclosure, is shown. Process flowchart 600 describes an updated configuration for the LTM process forwarded via anchor network entity 605. UE 115-c may communicate with candidate network entities such as network entity A (e.g., network entity 105-d), network entity B (e.g., network entity 105-e), network entity C (e.g., network entity 105-f), and network entity D (e.g., network entity 105-g)). In some examples, anchor network entity 605-a may be referred to as a candidate network entity. Network entity 105 and anchor network entity 605 may be as described in reference... Figures 1 to 5 An example of network entity 105 as described. UE115-e can be as shown in the reference. Figure 2 The UE 115-a described or as referenced Figures 1 to 5An example of UE 115 is described below. In the following description of process flowchart 600, operations may be performed in different orders or at different times. Some operations may be omitted, and others may be added. Some aspects of some operations may be performed by one or more other wireless devices.

[0135] For reference Figure 6 As described, UE 115-e can complete the LTM procedure to switch from the original source network entity A to a new source network entity B. Network entity B can notify both network entity A and anchor network entity 605 of the successful LTM procedure. Network entities C and D may not be updated and can send their own corresponding configuration updates to anchor network entity 605. The anchor network entity can then forward the updated configuration instructions to source network entity B, multiple network entities within the network entity group, or all candidate network entities.

[0136] Network entities A, B, C, and D may receive a configuration indication indicating that each network entity is a candidate network entity configured for the LTM procedure of UE 115-e. Anchor network entity 605 may receive (obtain) a configuration indication (e.g., a first indication) indicating that anchor network entity 605 is a communication anchor for one or more candidate network entities A, B, C, and D configured for the LTM procedure.

[0137] At 610, network entity A can be the original source network entity A communicating with UE 115-e. The original source network entity A can send LTM configuration to UE 115-e. The LTM configuration information can instruct UE 115-e to move the communication session from one network entity to another, such as from network entity A to network entity B.

[0138] At 615, UE 115-e can send an uplink message to network entity B. The uplink message can be an indication from UE 115-e that an LTM procedure has occurred, wherein the LTM procedure includes UE 115-e transferring a communication session from network entity A (e.g., a second source network entity) to network entity B.

[0139] At 620, the new source network entity B may indicate (e.g., send, output) an access notification (e.g., a first access notification) to the original source network entity A, anchor network entity 605, or both. The access notification may indicate that communication was successfully delivered to the new source network entity B.

[0140] At point 625, network entity C can update the LTM process information associated with a previously configured LTM process. For example, network entity C may have outdated configuration information.

[0141] At 630, network entity C can output (e.g., send) an updated configuration instruction to anchor network entity 605 based on anchor network entity 605 being configured as anchor network entity 605.

[0142] At 635, anchor network entity 605 may forward (e.g., output) one or more updated configuration indications to one or more candidate network entities A, B, C, and D. Anchor network entity 605 may forward the updated configuration indications based on an access notification from network entity B, an updated configuration indication from network entity C, or both. For example, anchor network entity 605 may forward the updated configuration indications only to source network entity B. In some examples, anchor network entity 605 may forward or broadcast the updated configuration indications to all or a combination of candidate network entities A, B, C, and D.

[0143] At 640, network entity B may send a reconfiguration message, such as an RRC reconfiguration message, to UE 115-e based on the updated configuration indicated by network entity C. Network entity B sends the reconfiguration based on the source network entity used for UE 115-e.

[0144] At point 645, network entity D can update the LTM process information associated with a previously configured LTM process. For example, network entity D may have outdated configuration information.

[0145] At 650, network entity D can output (e.g., send) an updated configuration instruction to anchor network entity 605 based on anchor network entity 605 being configured as anchor network entity 605.

[0146] At point 655, anchor network entity 605 may forward (e.g., output) one or more updated configuration indications to one or more candidate network entities A, B, C, and D. Anchor network entity 605 may forward the updated configuration indications based on an access notification from network entity B, an updated configuration indication from network entity D, an updated configuration indication from network entity C, or a combination thereof. For example, anchor network entity 605 may forward the updated configuration indications only to source network entity B. In some examples, anchor network entity 605 may forward or broadcast the updated configuration indications to all or a combination of candidate network entities A, B, C, and D.

[0147] At 660, network entity B may send a reconfiguration message, such as an RRC reconfiguration message, to UE115-e based on the updated configuration indicated by anchor network entity 605.

[0148] Figure 7An example of a process flowchart 700 supporting the resolution of ambiguity regarding the UE's serving location during a mobility process is shown, according to one or more aspects of this disclosure. Process flowchart 700 describes an updated configuration for the LTM process forwarded via anchor network entity 705 based on a query from anchor network entity 705. UE 115-e may communicate with candidate network entities such as network entity A (e.g., network entity 105-d), network entity B (e.g., network entity 105-e), network entity C (e.g., network entity 105-f), and network entity D (e.g., network entity 105-g)). In some examples, anchor network entity 705 may be referred to as a candidate network entity.

[0149] Network entity 105 and anchor network entity 705 can be as referenced. Figures 1 to 6 An example of network entity 105 described. Anchor network entity 705 can be as shown in the reference. Figure 6 An example of anchor network entity 605 as described. UE 115-f can be as shown in the reference. Figures 1 to 6 An example of UE 115 is described below. In the following description of process flowchart 700, operations may be performed in different orders or at different times. Some operations may be omitted, and others may be added. Some aspects of some operations may be performed by one or more other wireless devices.

[0150] For reference Figure 7 As described, UE 115-f can complete the LTM procedure to switch from the original source network entity A to a new source network entity B. Network entity B can notify both network entity A and anchor network entity 705 of the successful LTM procedure. Network entities C and D may not be updated. Network entity C can send a configuration update to anchor network entity 705. Anchor network entity 705 can then query candidate network entities to identify source network entity B and forward the updated configuration instruction to source network entity B.

[0151] Network entities A, B, C, and D may receive a configuration indication indicating that each network entity is a candidate network entity configured for the LTM procedure of UE 115-f. Anchor network entity 705 may receive (obtain) a configuration indication (e.g., a first indication) indicating that anchor network entity 705 is a communication anchor for one or more candidate network entities A, B, C, and D configured for the LTM procedure.

[0152] At 710, network entity A can be the original source network entity A communicating with UE 115-f. The original source network entity A can send LTM configuration to UE 115-f. The LTM configuration information can instruct UE 115-f to move the communication session from one network entity to another, such as from network entity A to network entity B.

[0153] At 715, UE 115-f can send an uplink message to network entity B. The uplink message can be an indication from UE 115-f that an LTM procedure has occurred, where the LTM procedure involves UE 115-f transferring a communication session from network entity A to a new source network entity B.

[0154] At 720, the new source network entity B may indicate (e.g., send, output) an access notification (e.g., a first access notification) to the original source network entity A, the anchor network entity 705, or both. The access notification may indicate that communication was successfully delivered to the new source network entity B.

[0155] At point 725, network entity C can update the LTM process information associated with a previously configured LTM process. For example, network entity C may have outdated configuration information.

[0156] At 730, network entity C can output (e.g., send) an updated configuration instruction to anchor network entity 705 based on anchor network entity 705 being configured as anchor network entity 705.

[0157] At 735, anchor network entity 705 may output (e.g., send) a query to one or more candidate network entities (e.g., network entities A, B, C, and D), the query including a request for an indication of whether the receiving network entity is the source network entity for UE 115-e.

[0158] At points 740, 745, 750, and 755, anchor network entity 705 can obtain (e.g., receive) response messages from network entities A, B, C, and D. The response messages can indicate whether the receiving network entity is a source network entity. For example, at 740, network entity A can provide a negative response indicating that network entity A is not a source network entity. At 745, network entity B can provide a positive response indicating that network entity B is a source network entity. At 750, network entity C can provide a negative response indicating that network entity C is not a source network entity. In some examples, because network entity C sends an updated configuration indication that is outdated, which may implicitly or explicitly indicate that network entity C is not a source network entity, network entity C may not respond to the query. At 755, network entity D can provide a negative response indicating that network entity D is not a source network entity.

[0159] At 760, anchor network entity 705 may output an updated configuration indication (e.g., unicast message) to source network entity B based on a response message indicating that source network entity B is the source network entity for UE 115-f.

[0160] At 765, network entity B may send a reconfiguration message, such as an RRC reconfiguration message, to UE115-f based on the updated configuration indicated by anchor network entity 705. Network entity B sends the reconfiguration based on the source network entity used for UE115-f.

[0161] Figure 8 A block diagram 800 of an apparatus 805 supporting the resolution of ambiguity regarding the UE's service location during mobility operations, according to one or more aspects of this disclosure, is shown. Apparatus 805 may be an example of aspects of network entity 105 as described herein. Apparatus 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Apparatus 805, or one or more components of apparatus 805 (e.g., receiver 810, transmitter 815, communication manager 820), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0162] Receiver 810 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 805. In some examples, receiver 810 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 810 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0163] Transmitter 815 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 805. For example, transmitter 815 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, transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 815 and receiver 810 may be co-located in a transceiver, which may include or be coupled to a modem.

[0164] The communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be examples of components used to perform various aspects of resolving ambiguity in the UE's service location during mobility processes as described herein. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0165] In some examples, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0166] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., referred to as processor executable code) (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0167] In some examples, the communication manager 820 may be configured to use a receiver 810, a transmitter 815, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0168] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for obtaining an indication from a UE regarding an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to a first source network entity. The communication manager 820 may be capable of, configured to, or operable to support components for outputting one or more access notifications to one or more candidate network entities based on the UE transferring the communication session. The communication manager 820 may be capable of, configured to, or operable to support components for obtaining one or more updated configuration indications from at least one of one or more candidate network entities based on one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0169] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for obtaining a first indication of configuration, the first indication indicating that a first network entity is one of one or more candidate network entities configured for an LTM procedure of the UE. The communication manager 820 may be capable of, configured to, or operable to support components for updating LTM procedure information associated with the LTM procedure. The communication manager 820 may be capable of, configured to, or operable to support components for outputting one or more updated configuration indications to at least one of the one or more candidate network entities based on the updated LTM procedure information.

[0170] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for obtaining a first indication of configuration, wherein the first indication of configuration indicates that the anchor network entity is a communication anchor for one or more candidate network entities configured for the LTM procedure of the UE. The communication manager 820 may be capable of, configured to, or operable to support components for obtaining one or more updated configuration indications from at least one of the one or more candidate network entities based on the first indication of configuration indicating that the anchor network entity is configured as a communication anchor. The communication manager 820 may be capable of, configured to, or operable to support components for forwarding one or more updated configuration indications to one or more candidate network entities, at least in part based on obtaining one or more updated configuration indications from at least one candidate network entity.

[0171] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for resolving ambiguity in UE location, which can achieve various advantages such as reduced processing, reduced power consumption, more efficient use of communication resources, etc.

[0172] Figure 9A block diagram 900 of an apparatus 905 supporting the resolution of ambiguity regarding the UE's service location during mobility operations, according to one or more aspects of this disclosure, is shown. Apparatus 905 may be an example of aspects of apparatus 805 or network entity 105 as described herein. Apparatus 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Apparatus 905, or one or more components of apparatus 905 (e.g., receiver 910, transmitter 915, communication manager 920), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0173] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0174] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 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, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0175] Device 905 or its various components may be examples of parts used to perform various aspects of resolving ambiguity in the UE's serving location during mobility processes as described herein. For example, communication manager 920 may include UE indication acquisition component 925, access notification output component 930, updated configuration indication acquisition component 935, configuration acquisition component 940, process information update component 945, updated configuration indication output component 950, updated configuration indication forwarding component 955, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or integrate with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0176] The communication manager 920 may support wireless communication according to examples disclosed herein. The UE indication acquisition component 925 is capable of, configured to, or operable to support components for obtaining an indication from the UE regarding an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to a first source network entity. The access notification output component 930 is capable of, configured to, or operable to support components for outputting one or more access notifications to one or more candidate network entities based on the UE transferring a communication session. The updated configuration indication acquisition component 935 is capable of, configured to, or operable to support components for obtaining one or more updated configuration indications from at least one of the one or more candidate network entities based on one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0177] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. The configuration acquisition component 940 is capable of, configured to, or operable to support components for obtaining a first indication of configuration, which indicates that a first network entity is one of one or more candidate network entities configured for the LTM procedure of the UE. The procedure information update component 945 is capable of, configured to, or operable to support components for updating LTM procedure information associated with the LTM procedure. The updated configuration indication output component 950 is capable of, configured to, or operable to support components for outputting one or more updated configuration indications to at least one of the one or more candidate network entities based on the updated LTM procedure information.

[0178] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. The configuration acquisition component 940 is capable of, configured to, or operable to support components for acquiring a first indication of configuration, wherein the first indication of configuration indicates that the anchor network entity is a communication anchor for one or more candidate network entities configured for the LTM procedure of the UE. The updated configuration indication acquisition component 935 is capable of, configured to, or operable to support components for acquiring one or more updated configuration indications from at least one of the one or more candidate network entities based on the first indication of configuration indicating that the anchor network entity is configured as a communication anchor. The updated configuration indication forwarding component 955 is capable of, configured to, or operable to support components for forwarding one or more updated configuration indications to one or more candidate network entities based on obtaining one or more updated configuration indications from at least one candidate network entity.

[0179] Figure 10A block diagram 1000 of a communication manager 1020 supporting the resolution of ambiguity in the UE service location during mobility processes, according to one or more aspects of this disclosure, is shown. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of parts for performing various aspects of resolving ambiguity in the UE service location during mobility processes as described herein. For example, the communication manager 1020 may include a UE indication acquisition component 1025, an access notification output component 1030, an updated configuration indication acquisition component 1035, a configuration acquisition component 1040, a process information update component 1045, an updated configuration indication output component 1050, an updated configuration indication forwarding component 1055, a query output component 1060, a response message acquisition component 1065, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components or virtualization components associated with network entity 105, between devices, components or virtualization components associated with network entity 105), or any combination thereof.

[0180] Communication manager 1020 may support wireless communication according to examples disclosed herein. UE indication acquisition component 1025 is capable of, configured to, or operable to support components for obtaining an indication from the UE regarding an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to a first source network entity. Access notification output component 1030 is capable of, configured to, or operable to support components for outputting one or more access notifications to one or more candidate network entities based on the UE transferring a communication session. Updated configuration indication acquisition component 1035 is capable of, configured to, or operable to support components for obtaining one or more updated configuration indications from at least one of one or more candidate network entities based on one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0181] In some examples, to support the output of one or more access notifications, the access notification output component 1030 is capable of, configured to, or operable to support components for outputting a first access notification to a second source network entity. In some examples, to support the output of one or more access notifications, the access notification output component 1030 is capable of, configured to, or operable to support components for outputting one or more second access notifications to one or more other network entities, wherein the first access notification indicates that a communication session has been successfully delivered to a first source network entity, and wherein one or more second access notifications indicate that the first source network entity is a serving entity of the UE.

[0182] In some examples, in order to support the output of one or more access notifications, the access notification output component 1030 is capable of being configured or operable to support components for outputting a first access notification to a second source network entity, wherein obtaining one or more updated configuration indications is also based on signaling sent from the second source network entity to one or more candidate network entities in response to the first access notification.

[0183] In some examples, the indication obtained from the UE is also based on a previous mobility procedure in addition to a successful LTM procedure.

[0184] Additionally or alternatively, the communication manager 1020 may support wireless communication according to examples disclosed herein. The configuration acquisition component 1040 is capable of, configured to, or operable to support components for obtaining a first indication of configuration, which indicates that a first network entity is one of one or more candidate network entities configured for the LTM procedure of the UE. The procedure information update component 1045 is capable of, configured to, or operable to support components for updating LTM procedure information associated with the LTM procedure. The updated configuration indication output component 1050 is capable of, configured to, or operable to support components for outputting one or more updated configuration indications to at least one of the one or more candidate network entities based on the updated LTM procedure information.

[0185] In some examples, in order to support the output of one or more updated configuration indications, the updated configuration indication output component 1050 is capable of being configured or operated to support components for broadcasting one or more updated configuration indications to one or more candidate network entities.

[0186] In some examples, query output component 1060 is capable of, configured to, or operable to support components for outputting queries to one or more candidate network entities, the queries including requests for indications regarding whether a receiving candidate network entity among the one or more candidate network entities is a source network entity for the UE. In some examples, response message acquisition component 1065 is capable of, configured to, or operable to support components for obtaining one or more response messages from one or more candidate network entities, wherein the one or more response messages indicate whether a receiving candidate network entity is a source network entity. In some examples, updated configuration indication output component 1050 is capable of, configured to, or operable to support components for outputting one or more updated configuration indications to a source network entity based on one or more response messages.

[0187] Additionally or alternatively, the communication manager 1020 may support wireless communication according to examples disclosed herein. In some examples, the configuration acquisition component 1040 is capable of, configured to, or operable to support components for acquiring a first indication of configuration, wherein the first indication of configuration indicates an anchor network entity as a communication anchor for one or more candidate network entities configured for the LTM procedure of the UE. In some examples, the updated configuration indication acquisition component 1035 is capable of, configured to, or operable to support components for acquiring one or more updated configuration indications from at least one of the one or more candidate network entities based on the first indication of configuration indicating that the anchor network entity is configured as a communication anchor. The updated configuration indication forwarding component 1055 is capable of, configured to, or operable to support components for forwarding one or more updated configuration indications to one or more candidate network entities based on acquiring one or more updated configuration indications from at least one candidate network entity.

[0188] In some examples, in order to support the forwarding of one or more updated configuration indications, the updated configuration indication forwarding component 1055 is capable of being configured or operable to support components for forwarding one or more updated configuration indications to a source network entity, wherein the source network entity is one of one or more candidate network entities.

[0189] In some examples, in order to support the forwarding of one or more updated configuration indications, the updated configuration indication forwarding component 1055 is capable of being configured or operated to support components for broadcasting one or more updated configuration indications to one or more candidate network entities.

[0190] In some examples, query output component 1060 is capable of, configured to, or operable to support components for outputting queries to one or more candidate network entities, the queries including requests for indications regarding whether a receiving candidate network entity among the one or more candidate network entities is a source network entity for the UE. In some examples, response message acquisition component 1065 is capable of, configured to, or operable to support components for obtaining one or more response messages from one or more candidate network entities, wherein the one or more response messages indicate whether a receiving candidate network entity is a source network entity. In some examples, updated configuration indication output component 1050 is capable of, configured to, or operable to support components for outputting one or more updated configuration indications to a source network entity based on one or more response messages.

[0191] Figure 11 A diagram of a system 1100 including device 1105 supporting the resolution of ambiguity in UE service location during mobility operations, according to one or more aspects of this disclosure. Device 1105 may be an example of device 805, device 905, or network entity 105 as described herein, or may include components thereof. Device 1105 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1105 may include components supporting output and acquisition of communication, such as a communication manager 1120, a transceiver 1110, one or more antennas 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).

[0192] Transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, device 1105 may include one or more antennas 1115 that may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1110 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1115, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1110 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1110, or transceiver 1110 and one or more antennas 1115, or transceiver 1110 and one or more antennas 1115 and one or more processors or one or more memory components (e.g., at least one processor 1135, at least one memory 1125, or both) may be included in a chip or chip assembly mounted in device 1105. In some examples, transceiver 1110 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0193] At least one memory 1125 may include RAM, ROM, or any combination thereof. At least one memory 1125 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1130. Code 1130 may include instructions that, when executed by one or more of the at least one processor 1135, cause the device 1105 to perform the various functions described herein. Code 1130 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1130 may not be directly executable by one of the at least one processor 1135, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1125 may include a BIOS, etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0194] At least one processor 1135 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1135 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1135. At least one processor 1135 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1125) to cause device 1105 to perform various functions (e.g., functions or tasks that support resolving ambiguities in the UE's service location during mobility processes). For example, device 1105 or components thereof may include at least one processor 1135 and at least one memory 1125 coupled to one or more processors in at least one processor 1135, the at least one processor 1135 and the at least one memory 1125 being configured to perform the various functions described herein. At least one processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1130) to perform the functions of device 1105. At least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1105 (such as within one or more memories of at least one memory 1125).

[0195] In some examples, at least one processor 1135 may include multiple processors, and at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1135 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1135) and memory circuitry (which may include at least one memory 1125)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1135 or a processing system including at least one processor 1135 may be configured, configured to, or operable to cause device 1105 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1125 or otherwise.

[0196] In some examples, bus 1140 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1140 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1105, or communication performed between different components of device 1105 that are co-addressable or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, at least one memory 1125, code 1130 and at least one processor 1135 may be located in one component of different components or partitioned between different components).

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

[0198] The communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for obtaining an indication from a UE regarding an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to a first source network entity. The communication manager 1120 may be capable of, configured to, or operable to support components for outputting one or more access notifications to one or more candidate network entities based on the UE transferring the communication session. The communication manager 1120 may be capable of, configured to, or operable to support components for obtaining one or more updated configuration indications from at least one of one or more candidate network entities based on one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0199] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for obtaining a first indication of configuration, the first indication indicating that a first network entity is one of one or more candidate network entities configured for an LTM procedure of the UE. The communication manager 1120 may be capable of, configured to, or operable to support components for updating LTM procedure information associated with the LTM procedure. The communication manager 1120 may be capable of, configured to, or operable to support components for outputting one or more updated configuration indications to at least one of the one or more candidate network entities based on the updated LTM procedure information.

[0200] Additionally or alternatively, the communication manager 1120 may support wireless communication according to examples disclosed herein. For example, the communication manager 1120 may be capable of, configured to, or operable to support components for obtaining a first indication of configuration, wherein the first indication of configuration indicates that the anchor network entity is a communication anchor for one or more candidate network entities configured for the LTM procedure of the UE. The communication manager 1120 may be capable of, configured to, or operable to support components for obtaining one or more updated configuration indications from at least one of the one or more candidate network entities based on the first indication of configuration indicating that the anchor network entity is configured as a communication anchor. The communication manager 1120 may be capable of, configured to, or operable to support components for forwarding one or more updated configuration indications to one or more candidate network entities, at least in part based on obtaining one or more updated configuration indications from at least one candidate network entity.

[0201] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 can support techniques for resolving ambiguity in UE location, which can achieve various benefits such as improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, longer battery life, improved utilization of processing power, etc.

[0202] In some examples, the communication manager 1120 may be configured to use or otherwise cooperate with transceiver 1110, one or more antennas 1115 (e.g., where applicable) or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by transceiver 1110, one or more processors in at least one processor 1135, one or more memories in at least one memory 1125, code 1130, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1135, at least one memory 1125, code 1130, or any combination thereof). For example, code 1130 may include instructions that can be executed by one or more processors of at least one processor 1135 to cause device 1105 to perform various aspects of resolving ambiguity of UE service location in the mobility process as described herein, or at least one processor 1135 and at least one memory 1125 may be otherwise configured to perform or support such operations individually or jointly.

[0203] Figure 12 A flowchart illustrating a method 1200 for resolving ambiguity regarding the UE's serving location during a mobility process, according to one or more aspects of this disclosure, is shown. Operation of method 1200 may be implemented by a network entity or its components as described herein. For example, operation of method 1200 may be implemented by, as referenced... Figures 1 to 11 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions 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 aspects of the described functions.

[0204] At 1205, the method may include: obtaining from the UE an indication that an LTM procedure has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to a first source network entity. The operation of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1205 may be provided by reference to [reference needed]. Figure 10The described UE instructs to obtain component 1025 to perform.

[0205] At 1210, the method may include: outputting one or more access notifications to one or more candidate network entities based on a UE-transmitted communication session. The operation of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be derived from references... Figure 10 The described access notification output component 1030 is used to execute this.

[0206] At 1215, the method may include: obtaining one or more updated configuration indications from at least one candidate network entity among one or more candidate network entities based on one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM process information at one or more candidate network entities among the one or more candidate network entities. The operation of 1215 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1215 may be provided by reference to [reference]. Figure 10 The described updated configuration instructions are obtained from component 1035 for execution.

[0207] Figure 13 A flowchart illustrating a method 1300 for resolving ambiguity regarding the UE's serving location during a mobility process, according to one or more aspects of this disclosure, is shown. Operation of method 1300 may be implemented by a network entity or its components as described herein. For example, operation of method 1300 may be implemented by, as referenced... Figures 1 to 11 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions 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 aspects of the described functions.

[0208] At 1305, the method may include: obtaining a first indication of a configuration, the first indication of the configuration indicating that a first network entity is a candidate network entity among one or more candidate network entities configured for the LTM procedure of the UE. The operation of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to... Figure 10 The described configuration is used to obtain component 1040 for execution.

[0209] At 1310, the method may include: updating LTM process information associated with the LTM process. The operation of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be derived from references... Figure 10 The process information update component 1045 is used to perform the described process.

[0210] At 1315, the method may include: outputting one or more updated configuration indications to at least one of one or more candidate network entities based on updated LTM process information. The operation of 1315 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1315 may be derived from references... Figure 10 The described updated configuration instructs output component 1050 to execute.

[0211] Figure 14 A flowchart illustrating a method 1400 for resolving ambiguity regarding the UE's serving location during a mobility process, according to one or more aspects of this disclosure, is shown. Operation of method 1400 may be implemented by a network entity or its components as described herein. For example, operation of method 1400 may be implemented by, as referenced... Figures 1 to 11 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0212] At 1405, the method may include: obtaining a first indication of a configuration, the first indication of which indicates that the anchor network entity is a communication anchor of one or more candidate network entities configured for the LTM procedure of the UE. Operation of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to... Figure 10 The described configuration is used to obtain component 1040 for execution.

[0213] At 1410, the method may include: instructing an anchor network entity to be configured as a communication anchor based on a first indication of configuration to obtain one or more updated configuration indications from at least one of one or more candidate network entities. The operation of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference]. Figure 10 The described updated configuration instructions are obtained from component 1035 for execution.

[0214] At 1415, the method may include: forwarding one or more updated configuration indications to one or more candidate network entities based on obtaining one or more updated configuration indications from at least one candidate network entity. The operation of 1415 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1415 may be provided by reference to [reference needed]. Figure 10 The described updated configuration instructs forwarding component 1055 to perform this action.

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

[0216] Aspect 1: A method for wireless communication at a first source network entity, the method comprising: obtaining from a UE an indication of an LTM procedure that has occurred, wherein the LTM procedure includes the UE transferring a communication session from a second source network entity to the first source network entity; outputting one or more access notifications to one or more candidate network entities at least in part based on the UE transferring the communication session; and obtaining one or more updated configuration indications from at least one of the one or more candidate network entities at least in part based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated LTM procedure information at one or more of the one or more candidate network entities.

[0217] Aspect 2: According to the method of aspect 1, outputting the one or more access notifications includes: outputting a first access notification to the second source network entity; and outputting one or more second access notifications to one or more other network entities, wherein the first access notification indicates that the communication session was successfully delivered to the first source network entity, and wherein the one or more second access notifications indicate that the first source network entity is the serving entity of the UE.

[0218] Aspect 3: The method according to any one of Aspects 1 to 2, wherein outputting the one or more access notifications comprises: outputting a first access notification to the second source network entity, wherein obtaining the one or more updated configuration indications is also based at least in part on signaling sent from the second source network entity to one or more candidate network entities among the one or more candidate network entities in response to the first access notification.

[0219] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: outputting one or more reconfiguration messages to the UE at least in part based on the one or more updated configuration indications.

[0220] Aspect 5: According to the method of aspect 4, the one or more reconfiguration messages include radio resource control signaling.

[0221] Aspect 6: The method according to any one of Aspects 1 to 5, wherein obtaining the indication from the UE is also based at least in part on a previous mobility process in addition to a successful LTM process.

[0222] Aspect 7: A first source network entity for wireless communication, the first source network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first source network entity to perform a method according to any one of Aspects 1 to 7.

[0223] Aspect 8: A first source network entity for wireless communication, the first source network entity comprising at least one component for performing the method according to any one of aspects 1 to 6.

[0224] Aspect 9: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to any one of Aspects 1 to 6.

[0225] It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0226] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0228] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A 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 working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0229] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0230] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0231] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0232] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “the component” in a claim may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” may refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0233] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0234] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0235] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0236] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this 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 first source network entity, the first source network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, said one or more processors coupled to said one or more memories and capable of operating individually or jointly to execute said code to enable the first source network entity: Obtain an indication from the user equipment (UE) that a lower-layer triggered mobility procedure has occurred, wherein the lower-layer triggered mobility procedure includes the UE transferring a communication session from a second source network entity to a first source network entity; At least in part, based on the communication session transmitted by the UE, one or more access notifications are output to one or more candidate network entities; as well as At least in part, one or more updated configuration indications are obtained from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated lower-layer triggered mobility process information at one or more of the one or more candidate network entities.

2. The first source network entity according to claim 1, wherein, In order to output the one or more access notifications, the one or more processors can operate individually or jointly to execute the code to cause the first source network entity: Output the first access notification to the second source network entity; as well as Output one or more second access notifications to one or more other network entities, wherein the first access notification indicates that the communication session was successfully delivered to the first source network entity, and wherein the one or more second access notifications indicate that the first source network entity is the service entity of the UE.

3. The first source network entity according to claim 1, wherein, In order to output the one or more access notifications, the one or more processors can operate individually or jointly to execute the code to cause the first source network entity: A first access notification is output to the second source network entity, wherein obtaining the one or more updated configuration indications is at least in part based on signaling sent from the second source network entity to one or more candidate network entities among the one or more candidate network entities in response to the first access notification.

4. The first source network entity of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first source network entity to: One or more reconfiguration messages are output to the UE, at least in part, based on the one or more updated configuration indications.

5. The first source network entity of claim 4, wherein the one or more reconfiguration messages include radio resource control signaling.

6. The first source network entity of claim 1, wherein obtaining the indication from the UE is also based at least in part on a previous mobility process other than a successful lower-layer triggered mobility process.

7. A method for wireless communication at a first source network entity, the method comprising: Obtain an indication from the user equipment (UE) that a lower-layer triggered mobility procedure has occurred, wherein the lower-layer triggered mobility procedure includes the UE transferring a communication session from a second source network entity to a first source network entity; At least in part, based on the communication session transmitted by the UE, one or more access notifications are output to one or more candidate network entities; as well as At least in part, one or more updated configuration indications are obtained from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated lower-layer triggered mobility process information at one or more of the one or more candidate network entities.

8. The method of claim 7, wherein outputting the one or more access notifications comprises: Output the first access notification to the second source network entity; as well as Output one or more second access notifications to one or more other network entities, wherein the first access notification indicates that the communication session was successfully delivered to the first source network entity, and wherein the one or more second access notifications indicate that the first source network entity is the service entity of the UE.

9. The method of claim 7, wherein outputting the one or more access notifications comprises: A first access notification is output to the second source network entity, wherein obtaining the one or more updated configuration indications is at least in part based on signaling sent from the second source network entity to one or more candidate network entities among the one or more candidate network entities in response to the first access notification.

10. The method according to claim 7, further comprising: One or more reconfiguration messages are output to the UE, at least in part, based on the one or more updated configuration indications.

11. The method of claim 10, wherein the one or more reconfiguration messages include radio resource control signaling.

12. The method of claim 7, wherein obtaining the indication from the UE is also based at least in part on a previous mobility process other than a successful lower-layer triggered mobility process.

13. A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to: Obtain an indication from the user equipment (UE) that a lower-layer triggered mobility procedure has occurred, wherein the lower-layer triggered mobility procedure includes the UE transferring a communication session from a second source network entity to a first source network entity; At least in part, based on the communication session transmitted by the UE, one or more access notifications are output to one or more candidate network entities; as well as At least in part, one or more updated configuration indications are obtained from at least one of the one or more candidate network entities based on the one or more access notifications, wherein the one or more updated configuration indications indicate updated lower-layer triggered mobility process information at one or more of the one or more candidate network entities.

14. The non-transitory computer-readable medium of claim 13, wherein the instructions for outputting the one or more access notifications are executable by the one or more processors to: Output a first access notification to the second source network entity; and Output one or more second access notifications to one or more other network entities, wherein the first access notification indicates that the communication session was successfully delivered to the first source network entity, and wherein the one or more second access notifications indicate that the first source network entity is the service entity of the UE.

15. The non-transitory computer-readable medium of claim 13, wherein the instructions for outputting the one or more access notifications are executable by the one or more processors to: A first access notification is output to the second source network entity, wherein obtaining the one or more updated configuration indications is at least in part based on signaling sent from the second source network entity to one or more candidate network entities among the one or more candidate network entities in response to the first access notification.

16. The non-transitory computer-readable medium of claim 13, wherein the instructions are further executable by the one or more processors to: One or more reconfiguration messages are output to the UE, at least in part, based on the one or more updated configuration indications.

17. The non-transitory computer-readable medium of claim 16, wherein the one or more reconfiguration messages include radio resource control signaling.

18. The non-transitory computer-readable medium of claim 13, wherein obtaining the indication from the UE is also based at least in part on a previous mobility process other than a successful lower-layer triggered mobility process.

Images