Techniques for connected state mobility in service-based wireless systems

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a measurement configuration including a trigger condition for performing a handover procedure within a service-based wireless system. The UE may send a message indicating satisfaction of a trigger condition to a source network entity, a mobility service provided by the service-based network, or both. After a handover decision is performed by the source network entity, the mobility service, or both, the mobility service may select a target network entity for the handover procedure. The mobility service may select a target network entity that supports at least one active core network service at the UE. The UE may then receive a handover command from the mobility service and may perform a handover procedure to the target network entity.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 948,044, filed by PURKAYASTHA et al. on September 19, 2022, entitled “TECHNIQUESFOR CONNECTED STATE MOBILITY IN ASERVICE-BASED WIRELESS SYSTEM,” which is assigned to the assignee of this patent and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following relates to wireless communications, including techniques for connected state mobility in service-based wireless systems. Background Art

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

[0005] In some wireless communication systems, when a UE moves within the system, the UE may perform a handover procedure from one cell to another cell and / or from one network entity to another network entity. However, in the context of a service-based network such as a sixth generation (6G) network, the execution of a handover between network entities may interrupt ongoing communications between the UE and a core network service to which the UE is subscribed. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting technologies for connection state mobility in service-based wireless systems. In general, aspects of the present disclosure relate to signaling for a handover process in a service-based network. In particular, aspects of the present disclosure relate to signaling that enables a user equipment (UE) to perform a handover process from one network entity to another network entity (e.g., from one distributed unit (DU) to another distributed unit) in a manner that reduces or minimizes interruption to one or more active core network services at the UE. For example, a UE and / or a source network entity connected to the UE may identify a trigger condition for performing a handover process. Based on the trigger condition, a source network entity or a mobility service (e.g., a core network mobility service that manages UE mobility within a network) may make a handover decision. Subsequently, the mobility service may identify a target network entity based on one or more active core network services at the UE. For example, the mobility service may select a target network entity that supports all (or at least one) active core network services in the active core network services at the UE. The mobility service may then send a handover command to the source network entity (for relaying to the UE) so that the UE may perform a handover procedure from the source network entity to the target network entity.

[0007] A method for wireless communication at a UE is described. The method may include: transmitting a set of multiple service messages with a first DU, the set of multiple service messages being associated with a set of multiple core network services provided by a service-based network and active at the UE; receiving a measurement configuration from a core network mobility service in the set of multiple core network services and via the first DU, the measurement configuration indicating one or more trigger conditions associated with a handover process at the UE; sending a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition in the one or more trigger conditions; receiving a handover command from the core network mobility service via the first DU based on the satisfaction of the trigger condition, the handover command indicating a second DU supporting at least one core network service in the set of multiple core network services active at the UE; and communicating with the second DU based on receiving the handover command.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: transmit a set of multiple service messages with a first DU, the set of multiple service messages being associated with a set of multiple core network services provided by a service-based network and active at the UE; receive a measurement configuration from a core network mobility service in the set of multiple core network services and via the first DU, the measurement configuration indicating one or more trigger conditions associated with a handover process at the UE; send a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition in the one or more trigger conditions; receive a handover command from the core network mobility service via the first DU based on the satisfaction of the trigger condition, the handover command indicating a second DU supporting at least one core network service in the set of multiple core network services active at the UE; and communicate with the second DU based on receiving the handover command.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for transmitting a set of multiple service messages with a first DU, the set of multiple service messages being associated with a set of multiple core network services provided by a service-based network and active at the UE; a unit for receiving a measurement configuration from a core network mobility service in the set of multiple core network services and via the first DU, the measurement configuration indicating one or more trigger conditions associated with a handover process at the UE; a unit for sending a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition in the one or more trigger conditions; a unit for receiving a handover command from the core network mobility service via the first DU based on the satisfaction of the trigger condition, the handover command indicating a second DU supporting at least one core network service in the set of multiple core network services active at the UE; and a unit for communicating with the second DU based on receiving the handover command.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: transmit a set of multiple service messages with a first DU, the set of multiple service messages associated with a set of multiple core network services provided by a service-based network and active at the UE; receive a measurement configuration from a core network mobility service in the set of multiple core network services and via the first DU, the measurement configuration indicating one or more trigger conditions associated with a handover process at the UE; send a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition in the one or more trigger conditions; receive a handover command from the core network mobility service via the first DU based on the satisfaction of the trigger condition, the handover command indicating a second DU supporting at least one core network service in the set of multiple core network services active at the UE; and communicate with the second DU based on receiving the handover command.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for sending capability information associated with the UE to the first DU, the core network mobility service, an additional core network service in the set of the multiple core network services, or any combination thereof, wherein receiving the handover command may be based on the capability information.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for receiving, via the handover command, a cell identifier associated with a serving cell supported by the second DU and a set of communication parameters for communicating with the serving cell, wherein communication with the second DU may be based on the cell identifier and the set of communication parameters.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: sending a service request for establishing a service with the core network mobility service to a network address associated with the core network mobility service; and, based on the service request, receiving control signaling indicating a service context for communicating with the core network mobility service, wherein sending the second message, receiving the switching command, or both may be based on the service context.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing measurements on signals received from the first DU and one or more candidate DUs including the second DU, wherein the measurements may be performed according to the measurement configuration, and wherein sending the second message may be based on performing the measurements.

[0015] A method for wireless communication at a core network mobility service is described. The method may include: receiving a message associated with satisfaction of a trigger condition for a handover procedure at a UE from a first DU in wireless communication with the UE; based on the message, selecting the second DU from a set of multiple candidate DUs based on the second DU being configured to support at least one core network service active at the UE from a set of multiple core network services of a service-based network; and, based on selecting the second DU, sending a handover command to the first DU for relaying to the UE, the handover command indicating the second DU and instructions to perform a handover procedure from the first DU to the second DU.

[0016] An apparatus for wireless communication at a core network mobility service is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receiving a message associated with satisfaction of a trigger condition for a handover procedure at a UE from a first DU in wireless communication with the UE; based on the message, selecting the second DU from a set of multiple candidate DUs based on the second DU being configured to support at least one core network service active at the UE from a set of multiple core network services of a service-based network; and, based on selecting the second DU, sending a handover command to the first DU for relaying to the UE, the handover command indicating the second DU and instructions for performing a handover procedure from the first DU to the second DU.

[0017] Another apparatus for wireless communication at a core network mobility service is described. The apparatus may include: a unit for receiving a message associated with satisfaction of a trigger condition for a handover procedure at a UE from a first DU in wireless communication with the UE; a unit for selecting the second DU from a set of multiple candidate DUs based on the message and based on the second DU being configured to support at least one core network service active at the UE from a set of multiple core network services of a service-based network; and a unit for sending a handover command to the first DU for relaying to the UE based on selecting the second DU, the handover command indicating the second DU and instructions to perform a handover procedure from the first DU to the second DU.

[0018] A non-transitory computer-readable medium storing code for wireless communication at a core network mobility service is described. The code may include instructions executable by a processor to perform the following operations: receiving a message associated with satisfaction of a trigger condition for a handover procedure at a UE from a first DU in wireless communication with the UE; based on the message, selecting the second DU from a set of multiple candidate DUs based on the second DU being configured to support at least one core network service active at the UE from a set of multiple core network services of a service-based network; and, based on selecting the second DU, sending a handover command to the first DU for relaying to the UE, the handover command indicating the second DU and instructions for performing a handover procedure from the first DU to the second DU.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: sending a handover request to the second DU based on the message; and receiving an acknowledgment (ACK) message from the second DU based on the handover request, wherein sending the handover command may be based on the ACK message.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for sending, via the handover request, an indication of the set of multiple core network services that may be active at the UE, wherein the ACK message may be based on the set of multiple core network services that may be active at the UE.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for receiving, via the ACK message, an indication of the at least one core network service supported by the second DU, wherein sending the switching command may be based on receiving the indication of the at least one core network service.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for receiving capability information associated with the UE, wherein selecting the second DU from the set of the plurality of candidate DUs may be based on the capability information.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability information may be received from a core network capability service included within the set of the plurality of core network services.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: selecting the second DU from the set of multiple candidate DUs may be based on the mobility history of the UE, the traffic load associated with the second DU, or both.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for receiving an indication of the set of the multiple candidate DUs via the message, wherein selecting the second DU may be based on receiving the indication of the set of the multiple candidate DUs.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, selecting the second DU may include operations, features, units, or instructions for selecting a serving cell supported by the second DU, wherein the handover command includes a cell identifier associated with the selected serving cell.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: receiving a second message from the second DU indicating that the handover process is complete; and communicating with the UE via the second DU based on the second message.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for sending a measurement configuration to the first DU for relaying to the UE, the measurement configuration indicating one or more trigger conditions including the trigger condition, wherein receiving the message may be based on the measurement configuration.

[0029] A method for wireless communication at a first DU is described. The method may include: transmitting a set of multiple service messages between a UE and a set of multiple core network services active at the UE based on a service network; sending a message associated with satisfaction of a trigger condition for a handover procedure at the UE to a core network mobility service in the set of multiple core network services; receiving a handover command indicating a second DU based on the message from the core network mobility service, the second DU supporting at least one core network service in the set of multiple core network services active at the UE; and sending the handover command to the UE, the handover command including an instruction to the UE to perform a handover procedure from the first DU to the second DU.

[0030] An apparatus for wireless communication at a first DU is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: transmit a set of multiple service messages between a UE and a set of multiple core network services active at the UE of a service-based network; send a message associated with the satisfaction of a trigger condition for a handover process at the UE to a core network mobility service in the set of multiple core network services; receive a handover command indicating a second DU from the core network mobility service based on the message, the second DU supporting at least one core network service in the set of multiple core network services active at the UE; and send the handover command to the UE, the handover command including an instruction to perform a handover process from the first DU to the second DU on the UE.

[0031] Another apparatus for wireless communication at a first DU is described. The apparatus may include: a unit for transmitting a set of multiple service messages between a UE and a set of multiple core network services active at the UE of a service-based network; a unit for sending a message associated with satisfaction of a trigger condition for a handover procedure at the UE to a core network mobility service in the set of multiple core network services; a unit for receiving a handover command indicating a second DU based on the message from the core network mobility service, the second DU supporting at least one core network service in the set of multiple core network services active at the UE; and a unit for sending the handover command to the UE, the handover command including an instruction to the UE to perform a handover procedure from the first DU to the second DU.

[0032] A non-transitory computer-readable medium storing code for wireless communication at a first DU is described. The code may include instructions executable by a processor to: transmit a set of multiple service messages between a UE and a set of multiple core network services active at the UE of a service-based network; send a message associated with the satisfaction of a trigger condition for a handover procedure at the UE to a core network mobility service in the set of multiple core network services; receive a handover command indicating a second DU based on the message from the core network mobility service, the second DU supporting at least one core network service in the set of multiple core network services active at the UE; and send the handover command to the UE, the handover command including instructions to perform a handover procedure from the first DU to the second DU on the UE.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for sending capability information associated with the UE to the core network mobility service, an additional core network service in the set of multiple core network services, or both, wherein receiving the handover command may be based on the capability information.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for sending an indication of the set of multiple core network services that can be active at the UE to the core network mobility service, an additional core network service in the set of multiple core network services, or both, wherein receiving the handover command may be based on sending the indication of the set of multiple core network services that can be active at the UE.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: establishing a communication tunnel with the second DU based on the handover command; receiving a second message for the UE before the handover process is completed; and, based on receiving the second message, sending one or more packets to the second DU via the communication tunnel for relaying to the UE.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for sending, via the message, an indication of a set of multiple candidate DUs including the second DU and one or more cell identifiers associated with one or more service cells supported by the second DU, wherein receiving the handover command may be based on sending the indication of the set of multiple candidate DUs.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: receiving an indication of at least one core network service supported by the second DU via the handover command; and sending the indication of at least one core network service supported by the second DU to the UE via the handover command.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: receiving, from the core network mobility service, a measurement configuration indicating one or more trigger conditions including the trigger condition; and sending the measurement configuration to the UE, wherein sending the message associated with the satisfaction of the trigger state may be based on the measurement configuration.

[0039] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for receiving a measurement report, a second message indicating the trigger condition, or both from the UE based on the measurement configuration, wherein sending the message associated with the satisfaction of the trigger state may be based on receiving the measurement report, the second message indicating the trigger condition, or both.

[0040] A method for wireless communication at a second DU is described. The method may include: receiving a handover request associated with a handover procedure from a first DU to the second DU at a UE from a core network mobility service of a service-based network; sending an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service in a set of multiple core network services that is active at the UE and supported by the second DU; communicating with the UE based on the handover request and the ACK message; and sending a second message to the core network mobility service indicating completion of the handover procedure based on communicating with the UE.

[0041] An apparatus for wireless communication at a second DU is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receiving a handover request associated with a handover process from a first DU to the second DU at a UE from a core network mobility service of a service-based network; sending an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service in a set of multiple core network services that is active at the UE and supported by the second DU; communicating with the UE based on the handover request and the ACK information; and sending a second message indicating completion of the handover process to the core network mobility service based on communicating with the UE.

[0042] Another apparatus for wireless communication at a second DU is described. The apparatus may include: a unit for receiving a handover request associated with a handover procedure from a first DU to the second DU at a UE from a core network mobility service of a service-based network; a unit for sending an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service in a set of multiple core network services that is active at the UE and supported by the second DU; a unit for communicating with the UE based on the handover request and the ACK message; and a unit for sending a second message to the core network mobility service indicating completion of the handover procedure based on communicating with the UE.

[0043] A non-transitory computer-readable medium storing code for wireless communication at a second DU is described. The code may include instructions executable by a processor to: receive a handover request associated with a handover procedure from a first DU to the second DU at a UE from a core network mobility service of a service-based network; send an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service active at the UE and supported by the second DU in a set of multiple core network services; communicate with the UE based on the handover request and the ACK message; and send a second message to the core network mobility service indicating completion of the handover procedure based on communicating with the UE.

[0044] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for receiving, via the handover request, an indication of the set of the multiple core network services that may be active at the UE, wherein sending the ACK message may be based on the set of the multiple core network services that may be active at the UE.

[0045] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: establishing a communication tunnel with the first DU based on the handover request, the ACK message, or both; receiving one or more data packets associated with a second message for the UE from the first DU via the communication tunnel before the handover process is completed; and, based on receiving the one or more data packets via the communication tunnel, sending the one or more data packets associated with the second message to the UE.

[0046] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for sending a communication parameter set for communication between the UE and the second DU to the core network mobility service via the ACK message, wherein communication with the UE may be based on the communication parameter set. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 An example of a wireless communication system supporting techniques for connection state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0048] Figure 2An example of a wireless communication system supporting techniques for connection state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0049] Figure 3 An example of a network architecture supporting techniques for connection state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0050] Figure 4 An example of a wireless communication system supporting techniques for connection state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0051] Figure 5 An example of a process flow for supporting techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0052] Figure 6 An example of a process flow for supporting techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0053] Figure 7 and 8 A block diagram of a device supporting techniques for connection state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0054] Fig. 9 A block diagram of a communications manager supporting techniques for connected state mobility in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0055] Fig.10 A schematic diagram of a system including devices supporting techniques for connection state mobility in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0056] Fig.11 and 12 A block diagram of a device supporting techniques for connection state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0057] Fig.13 A block diagram of a communications manager supporting techniques for connected state mobility in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0058] Fig.14A schematic diagram of a system including devices supporting techniques for connection state mobility in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0059] Figures 15 to 18 A flow chart illustrating a method of supporting techniques for connection state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0060] Some wireless systems may exhibit a relatively vertical layered architecture that includes many "layers" of different devices that perform the functions of the system. For example, a wireless system may include user equipment (UE), base stations / network entities, and many back-end (e.g., core network) devices associated with one or more functions for the system. This layered structure may cause processing and other functions to be performed at multiple devices (e.g., duplicate processing or capabilities across multiple back-end devices), resulting in wasted resources and excessive power consumption. Additionally, the back-end architecture of some wireless systems may be owned and maintained by a small number of operators, which may make it difficult for other parties / entities to integrate with these systems and may complicate the ability of these systems to provide customized services and functions to wireless devices.

[0061] In contrast, some wireless systems (e.g., sixth generation (6G) systems) may exhibit a flatter service-based architecture, in which a radio access network (RAN) (e.g., a network entity) interfaces with a service-based network to connect UEs to core network services maintained at various network addresses within the service-based network. In the context of a service-based system, operations and functions that might otherwise be performed by a few centralized backend components (e.g., in some systems) may be distributed across multiple core network services that may be hosted at different network addresses, such as in a cloud-based architecture. Thus, a UE in a service-based system may be able to establish and maintain connections to different core network services or different groups of core network services on a à la carte basis (e.g., "subscribe" to different core network services or different groups of core network services), each of which offers or provides a respective network function or service. For example, a service-based system may include mobility services, security services, privacy services, location services, and the like. In this regard, each UE within a service-based system may be able to select which core network services the UE will subscribe to based on the individual characteristics or needs of the respective UE.

[0062] In the context of a service-based wireless system, a UE may subscribe to one or more core network services provided by a service-based network. In this case, a network entity of the RAN may interface with a service-based network and relay communications between the UE and the corresponding core network services. However, as the UE moves within the network, the UE may perform a handover procedure from one cell to another and / or from one network entity to another. In the context of a service-based network such as a 6G network, the execution of a handover between network entities may interrupt ongoing communications between the UE and one or more core network services to which the UE subscribes.

[0063] Thus, aspects of the present disclosure relate to signaling for a handover procedure in a service-based network such as a 6G network. In particular, aspects of the present disclosure relate to signaling that enables a UE to perform a handover procedure from one network entity to another network entity (or, from one distributed unit (DU) to another distributed unit) in a manner that reduces or minimizes disruption to one or more active core network services at the UE.

[0064] For example, the UE and / or a source network entity connected to the UE may identify a trigger condition for performing a handover procedure. Based on the trigger condition, the source DU or a mobility service (e.g., a core network mobility service that manages UE mobility within the network) may make a handover decision. Subsequently, the mobility service may identify a target DU based on one or more active core network services at the UE. For example, the mobility service may select a target DU that supports all (or at least one) of the active core network services at the UE. The mobility service may then send a handover command (for relaying to the UE) to the source DU so that the UE may perform a handover procedure from the source DU to the target DU. After completing the handover procedure, the source DU may relay communications between the UE and the supported one or more core network services.

[0065] Aspects of the disclosure are first described in the context of wireless communication systems. Additional aspects of the disclosure are described in the context of example network architectures and example process flows. Aspects of the disclosure are also illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow charts related to techniques for connection state mobility in service-based wireless systems.

[0066] Figure 1An example of a wireless communication system 100 supporting techniques for capability indication for multiple services in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a service-based network 130. In some examples, the wireless communication system 100 may implement aspects of a 6G network, a 5G network (e.g., a New Radio (NR) network), a 4G network (e.g., a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network), or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

[0070] In some examples, the network entities 105 can communicate with the service-based network 130 or with each other or both. For example, the network entities 105 can communicate with the service-based network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3 or other interface protocols). Similarly, the UE 115 can communicate with the service-based network 130 via one or more communication links 155. In some examples, the network entities 105 can communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the service-based network 130) via the backhaul communication links 120 (e.g., according to X2, Xn or other interface protocols). In some examples, the network entities 105 can communicate with each other via one or more communication links such as the fronthaul communication link 168 (e.g., between the radio unit 170 and the distributed unit 165). The backhaul communication link 120, the fronthaul communication link 168, or other communication links between the network entities 105 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof.

[0071] In some examples, the network entity 105 can communicate with a service platform 150 (e.g., a cloud platform) that provides one or more core network services (CN services), one or more radio access network services (RAN services), or any combination thereof (CN / RAN services 185). The CN / RAN services can be provided via the service-based network 130 using one or more APIs. For example, one or more DU service APIs 175 can provide an interface for one or more services at the UE 115. The services at the UE 115 can correspond to one or more CN / RAN services 185 at the service platform 150. For example, the network service API 180 at the service-based network 130 can interface with a corresponding DU service API 175 at the DU 165, which interfaces with a corresponding API at the UE 115 to provide service connectivity between the services of the one or more UEs 115 and the corresponding CN / RAN services 185.

[0072] One or more network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an access point, a radio transceiver, a Node B, an eNodeB (eNB), a next generation Node B or a giga-NodeB (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a home NodeB, a home eNodeB, a 6G NB, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, independent) base station architecture, which may be configured to utilize a service-based architecture and provide radio access within a single network entity 105 (e.g., a single RAN node such as a base station 140 may include a RU 170, a DU 165, and a DU API 175 for CN / RAN services 185). The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP).

[0073] Additionally, in some examples, one or more network entities 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture), which may be configured to utilize a protocol stack physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more central units (CUs), DUs 165, RUs 170, RAN intelligent controllers (RICs) 175 (e.g., near real-time RICs (near RT RICs), non-real-time RICs (non-RT RICs)), service management and orchestration (SMO) systems, or any combination thereof. One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as virtual units (eg, virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0074] The functional division between components (e.g., CU, DU, and RU) is flexible and can support different functions, depending on which functions are performed at the component (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of a protocol stack can be adopted between a CU and a DU 165, such that the CU can support one or more layers of a protocol stack and the DU 165 can support one or more different layers of a protocol stack. In some examples, the CU can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). In some examples, the CU can host one or more service APIs for one or more CN / RAN services 185 via a corresponding network service API 180 of a service-based network 130. The CU may be connected to one or more DUs 165 or RUs 170, and one or more DUs 165 or RUs 170 may host lower protocol layers, e.g., Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and each may be at least partially controlled by the CU. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU and DU 165, or the functional split between the DU 165 and the RU 170 may be within a protocol layer (e.g., certain functions of a protocol layer may be performed by one of the CU, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU, DU 165, or RU 170). The DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., an open fronthaul (FH) interface). In some examples, the fronthaul communication link 168 may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by a respective network entity 105 communicating via such a communication link.

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

[0076] In the case where the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the techniques for capability indication for multiple services in a service-based wireless system described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU, a RU 170, a RIC, a SMO).

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

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

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

[0080] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling, or control signaling to coordinate operations with respect to other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster used for discovery by a UE 115. A carrier may operate in a standalone mode, in which a UE 115 may perform initial acquisition and connection via a carrier, or in a non-standalone mode, in which a different carrier (e.g., the same or different radio access technology) is used to anchor the connection.

[0081] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in TDD mode).

[0082] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using portions (e.g., subbands, BWPs) or all of the carrier bandwidth.

[0083] The signal waveform transmitted via the carrier wave may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the subcarrier spacing are inversely proportional. The amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high amount of resource elements (e.g., within the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0084] One or more digital schemes for a carrier may be supported, and the digital scheme may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different digital schemes. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be limited to the one or more active BWPs.

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

[0086] 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, the frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a 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 number of symbol periods (e.g., depending on the length of a cyclic prefix added in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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., N f ) sampling period. The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

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

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

[0090] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 115 having a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as compared to the macro cell. A small cell may provide unrestricted access to a UE 115 having a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a residence or office). A network entity 105 may support one or more cells, and may also support communications via one or more cells using one or more component carriers.

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

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

[0093] Some UEs 115 (e.g., MTC or IoT devices) may be low-cost or low-complexity devices and may provide automated communications between machines (e.g., via machine-to-machine (M2M) communications). M2M communications or MTC may refer to data communications technology that allows devices to communicate with each other or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communications or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a human interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.

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

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

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

[0097] In some deployments, one or more UEs 115 or network entities 105 (such as, for example, 6G RAT and 5G RAT) may access multiple RANs. In some examples, the 6G RAT may be associated with the service-based network 130, and the 5G RAT may be associated with the 5G core 190. The 5G core 190 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The 5G core 190 may be an evolved packet core (EPC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets to or interconnects to an external network. The control plane entities may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the 5G core 190. User IP packets may be transferred through user plane entities, which may provide IP address allocation and other functions. The user plane entities may be connected to IP services 195 for one or more network operators. IP services 195 may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0098] The wireless communication system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band, due to the wavelength range from 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 may penetrate buildings sufficiently for macro cells to provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0099] The wireless communication system 100 may also operate in the ultra-high frequency (SHF) region of use (which may be in the range of 3 GHz to 30 GHz) (also referred to as the centimeter band) or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (e.g., base station 140, RU 105), and the EHF antennas of each device may be smaller and more closely spaced than the UHF antennas. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may suffer from even greater attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may differ depending on the country or regulatory agency.

[0100] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed radio frequency spectrum bands, devices (such as network entities 105 and UE 115) can use carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on carrier aggregation configurations of component carriers combined with operations using licensed bands (e.g., LAA). Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, as well as other examples.

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

[0102] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and increase spectrum efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. Multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) (for which multiple spatial layers are sent to the same receiving device) and multi-user MIMO (MU-MIMO) (for which multiple spatial layers are sent to multiple devices).

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

[0104] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device such as network entity 105, or by a receiving device such as UE 115) a beam direction for later transmission or reception by the network entity 105.

[0105] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on signals that have been sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 having the highest signal quality or otherwise acceptable signal quality.

[0106] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may generate a combined beam for transmission (e.g., from network entity 105 to UE 115) using a combination of digital precoding or beamforming. UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may be precoded or unprecoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may employ similar techniques to send signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by UE 115) or to send signals along a single direction (e.g., for sending data to a receiving device).

[0107] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) can perform receiving operations according to multiple receiving configurations (e.g., directional listening). For example, the receiving device can perform reception according to multiple receiving directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which can be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device can use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0108] In some examples, the wireless communication system 100 may include a packet-based network that operates using a cloud platform (e.g., a service platform 150 that provides CN / RAN services 185). In some examples, the CN / RAN services 185 may be hosted based on the capabilities of the deployment topology and service parameters associated with each service. Providing CN / RAN services 185 allows for separation of specific services (e.g., mobility, connection state management, security, paging, radio access services, quality of service (QoS) configuration and data services, UE capability management, location, messaging, etc.) from transport functions (e.g., data radio bearer (DRB) and logical channel (LC) management, data service configuration, etc.). Service-based functions (e.g., message brokers decouple radio network processes from network delivery mechanisms) can allow the flexibility to host some functions (e.g., Layer 2 (L2) functions) anywhere in the cloud, and can achieve enhanced scalability, resiliency, elasticity, agility, reuse, visibility, automation, failover, or any combination thereof (e.g., each service across the RAN and core networks can be independently scaled by independently increasing or decreasing resources allocated across functions). In addition, efficiency can be enhanced by providing real-time link management to the RAN edge and allowing adaptation at the DU 165 to more effectively activate, deactivate, or select features based on UE conditions.

[0109] In some implementations, the wireless communication system 100 supports signaling that enables efficient handover procedures in service-based networks (e.g., 6G networks). In particular, aspects of the present disclosure relate to signaling that enables a UE 115 to perform a handover procedure from one network entity 105 to another network entity (e.g., from one DU to another DU) in a manner that reduces or minimizes interruption to one or more active core network services (e.g., CN / RAN services 185) at the UE 115.

[0110] For example, the UE 115, the source DU 165 connected to the UE 165, the mobility service (e.g., a core network service that manages the mobility of the UE 115 within the network), or any combination thereof may identify a trigger condition for performing a handover procedure. Based on the trigger condition, the source DU 165 or the mobility service (e.g., a core network mobility service that manages the mobility of the UE 115 within the network) may make a handover decision. Subsequently, the mobility service may identify a target DU 165 based on one or more active core network services at the UE 115. For example, the mobility service may select a target DU 165 that supports all (or at least one) of the one or more active core network services at the UE 115. The mobility service may then send a handover command (for relaying to the UE 115) to the source DU 165 so that the UE 115 may perform a handover procedure from the source DU 165 to the target DU 165. After the handover procedure is completed, the source DU 165 may relay communications between the UE 115 and the supported one or more core network services.

[0111] The techniques described herein may enable a UE 115 to perform a handover procedure between DUs 165 and / or between network entities 105 of a service-based wireless system while reducing or minimizing interruption to one or more active core network services at the UE 115. In particular, aspects of the present disclosure support techniques that enable a UE 115 to perform a handover procedure to a target DU / target network entity that supports at least some of the active core network services at the UE 115. Thus, aspects of the present disclosure may reduce interruption to communications performed with core network services, thereby reducing or preventing the need for the UE 115 to continually reestablish communications with core network services. In this regard, the techniques described herein may reduce signaling associated with a UE 115 subscribing to core network services, reduce interruptions, and improve the overall user experience.

[0112] Figure 2 An example of a wireless communication system 200 that supports techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. Aspects of the wireless communication system 200 may implement aspects of the wireless communication system 100 or may be implemented by aspects of the wireless communication system 100. In some implementations, the wireless communication system 200 illustrates an example architecture of a service-based wireless communication system, such as with reference to Figure 1 6G network described.

[0113] The wireless communication system 200 may include one or more UEs 115 (e.g., UE 115-a), one or more network entities (e.g., network entity 105-a), and a service-based network 205. In some aspects, the service-based network 205 may be configured to communicate or interface with a RAN 210 of the wireless communication system 200, wherein the RAN 210 includes one or more network entities (e.g., network entity 105-a). The service-based network 205 may support or provide a set of core network services 215 (e.g., core network services 215-a, 215-b, 215-c, 215-d, 215-d, and 215-e). In some implementations, the service-based network 205 may include or be associated with a cloud platform, wherein the corresponding core network services 215 are hosted at corresponding network addresses in the cloud platform.

[0114] The UE 115-a may communicate with the network entity 105-a using one or more communication links 220, which may include an example of an access link (e.g., a Uu link). The communication link 220 may include a bidirectional link, which may include both uplink and downlink communications. Similarly, the network entity 105-a of the RAN 210 may be configured to communicate (e.g., interface) with the service-based network 205 via one or more communication links (e.g., communication link 225), wherein the communication link 215 may be configured to facilitate bidirectional communication between the network entity 105-a and each of the various core network services 215 of the service-based network 205.

[0115] like Figure 2 As shown, the wireless communication system 200 may present a service-based architecture in which entities of the RAN 210 (e.g., the network entity 105-a) are configured to connect the UE 115-a to the core network services 215 of the service-based network 205. In particular, the RAN 210 (e.g., the network entity 105-a) may be configured to relay communications between the UE 115-a and the various core network services 215 of the service-based network to enable the UE 115-a to establish and maintain wireless connections with the various core network services 215 in order to exchange communications associated with the various network functions supported by the corresponding core network services 215. In other words, the wireless communication system 200 may enable the UE 115-a to "subscribe" to the corresponding core network services 215 on a per-order basis, based on the needs or requirements of the UE 115-a. In this regard, different UEs 115 within the wireless communication system 200 may be able to subscribe to different subsets of the core network services 215 depending on the capabilities of the UE 115, the applications executed at the UE 115, the mobility of the UE 115, and so forth.

[0116] Each core network service 215 can be associated with a corresponding network address within the service-based network 205. In other words, each core network service 215 can be hosted at one or more components of the cloud-based network, where the components of each core network service 215 can be associated with a corresponding network address. The respective core network services 215 can be provided by a network provider, a third-party entity, etc., where each core network service 215 is configured to support a corresponding service or function provided to a component (e.g., UE 115-a, network entity 105-a) of the wireless communication system 200.

[0117] The different services, functions, and core network functions that each core network service 215 may support or provide may include, but are not limited to, mobility services, security services, privacy services, location services, etc. For example, a first core network service 215-a may include a core network mobility service that hosts information and provides signaling that facilitates geographic mobility of a UE 115-a throughout the wireless communication system. As another example, a second core network service 215-b may include a security service that provides security and encryption services to a subscribing UE 115 within the wireless communication system 200.

[0118] In some aspects, each core network service 215 may include a respective API configured to facilitate wireless communications with the network entity 105 - a and the UE 115 - a , e.g. Figure 1 . The APIs at the respective core network services 215 may include routing APIs, configuration APIs, or both. The routing APIs may be configured for service data unit communications between the UE 115-a and the respective core network services 215. In contrast, the configuration APIs may be configured to facilitate communications between the network entity 105-a and the respective core network services 215 to negotiate service requests and service-specific operations.

[0119] In some aspects, the network entity 105-a (e.g., eDU) can facilitate traffic routing (e.g., service data unit routing) from the UE 115-a to the core network service 215, and vice versa. The network entity 105-a can facilitate traffic routing between the corresponding devices directly, via other network entities 105-a, via a proxy, or any combination thereof. In addition, in some cases, the UE 115-a can be communicatively coupled to multiple network entities 105 (e.g., dual connectivity), where multiple network entities 105 facilitate traffic routing with the same or different sets of core network services 215. Additionally, the network entity 105-a can support service configurations or service contexts associated with communication parameters within the system, such as QoS flows, security, and UE 115 service contexts. In some aspects, the communication link 220 between the network entity 105-a and the UE 115-a can be associated with an access layer configuration that facilitates air service awareness. The access layer configuration can include logical channels, access layer security, access layer contexts, and the like. For example, access layer configuration can be associated with service-specific configuration (e.g., logical channels corresponding to QoS flows for each corresponding core network service 215) and service-agnostic configuration (e.g., parameters common to all core network services 215).

[0120] Compared with some other types of wireless systems, Figure 2 The service-based wireless communication system 200 (e.g., a 6G network) shown in FIG. 2 may exhibit some differences and advantages, for example, the network exhibits a relatively more vertical layered architecture that includes "layers" of multiple different devices that perform functions for the network. A more layered structure may result in processing and other functions being performed at multiple devices (e.g., the network entity 105 and one or more backend devices), resulting in inefficient use of resources and high power consumption. Additionally, the backend architecture of a network with a more vertical layered architecture may be owned and maintained by a few operators, which may make it difficult for other parties / entities to integrate with such a system, and the services provided to the UE 115 and other devices may be difficult to customize within such a system.

[0121] In contrast, Figure 2The service-based wireless communication system 200 shown in presents a flatter horizontal architecture that enables the corresponding functions of the wireless communication system to be distributed among different components of the system (e.g., core network services 215). For example, such functions and protocols can be divided and distributed across a collection of core network services 215, so that each core network service 215 can support or implement a small part of the capabilities and functions of a traditional wireless communication system. In other words, compared to components that provide all-encompassing network functions and protocols (e.g., modularization of network services / functions across multiple core network services 215), the service-based architecture can enable functions and protocols to be split into self-contained services (e.g., core network services 215).

[0122] In this regard, the wireless communication system 200 may illustrate an example of a merged cloud-native platform configured to host core and RAN services, which may simplify protocols and reduce duplication of processing operations across the core and RAN (e.g., reallocation of core and RAN 210 services). In other words, the fusion of RAN 210 and CN functions may reduce duplication of operations and functions used to serve one UE at different layers.

[0123] The wireless communication system 200 can extend the benefits associated with the service-based architecture of the service-based network 205 to the RAN 210, including the benefits of increased scalability, resiliency, flexibility, agility, reuse, visibility, automation, and failover. Additionally, the service-based architecture can enable each core network service 215 to scale independently across the RAN 210 and the core by independently increasing or decreasing the resources allocated across each core network service 215.

[0124] In some implementations, as will be described in further detail herein, the wireless communication system 200 can support signaling for handover procedures in a service-based network 205 (e.g., a 6G network). In particular, aspects of the present disclosure relate to signaling that enables a UE 115-a to perform a handover procedure from one network entity 105 to another network entity (or from one DU to another DU) in a manner that minimizes disruption to active core network services 215 at the UE 115-a.

[0125] Figure 3An example of a network architecture 300 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting techniques for broadcasting system information in a service-based wireless system according to one or more aspects of the present disclosure is shown. The network architecture 300 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 300 may include a service-based network 305, which may be an example of a service-based network 130 or 205, and the service-based network 305 communicates with the DU 165-a via a link 120-b. In this example, the DU 165 may also communicate with one or more CUs 310, which may communicate directly with the 5G core 190-a via the backhaul communication link 120-a, or indirectly with the 5G core 190-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 330-a via an E2 link, or a non-RT RIC 330-b associated with a SMO 335 (e.g., an SMO framework), or both. The CU 310 may communicate with one or more DUs 165-a via corresponding mid-range communication links 315 (e.g., F1 interfaces). The DU 165-a may communicate with one or more RUs 170-a via corresponding front-haul communication links 168-a. The RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with a UE 115-b via one or more communication links 125-a. In some implementations, a UE 115 may be served by multiple RUs 170-a simultaneously.

[0126] Each network entity 105 (e.g., CU 310, DU 165-a, RU 170-a, non-RT RIC 330-a, near-RT RIC 330-b, SMO 335, open cloud (O-cloud) 320, open eNB (O-eNB) 325) of the network architecture 300 may include one or more interfaces, or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105, or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105, may be configured to communicate with one or more other network entities 105 via a transmission medium. For example, a network entity 105 may include a wired interface that is configured to receive or send signals to one or more other network entities 105 via a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive or send signals, or both, to one or more other network entities 105 via a wireless transmission medium.

[0127] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, and the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to process user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some implementations, CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (e.g., via an E1 interface when implemented in an O-RAN configuration). CU 310 may be implemented to communicate with DU 165-a when necessary for network control and signaling.

[0128] DU 165-a may correspond to a logical unit including one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, when connected to a service-based network 305 with an interface, DU 165-a may host one or more services for the service-based network 305 and one or more corresponding services at one or more UEs 115-b. One or more APIs. In some examples, when connected to a CU 310 with an interface, DU 165-a may at least partially host one or more of the following, depending at least in part on a functional partition (e.g., a functional partition defined by the Third Generation Partnership Project (3GPP)): an RLC layer, a MAC layer, and one or more aspects of a PHY layer (e.g., a high PHY layer, such as a module for FEC encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, DU 165 may further host one or more low PHY layers. Each layer may be implemented with an interface configured to communicate signals with other layers hosted by DU 165-a or with a control function hosted by CU 310.

[0129] In some examples, lower layer functions may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional partitioning (e.g., lower layer functional partitioning). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-b. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and the CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0130] SMO 335 can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, SMO 335 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., O1 interface). For virtualized network entities 105, SMO335 can be configured to interact with a cloud computing platform (e.g., O-cloud 320) via a cloud computing platform interface (e.g., O2 interface) to perform network entity lifecycle management (e.g., instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 310, DU 165-a, RU 170-a, and near-RT RIC 330-a. In some implementations, SMO335 can communicate with components configured according to 4G RAN (e.g., via O1 interface). Additionally or alternatively, in some implementations, SMO 335 can communicate directly with one or more RU 170-a via the O1 interface. The SMO 335 may also include a non-RT RIC 330 - b configured to support the functionality of the SMO 335 .

[0131] The non-RT RIC 330-b can be configured to include logical functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 330-a. The non-RT RIC 330-b can be coupled to or communicate with the near-RT RIC 330-a (e.g., via an A1 interface). The near-RT RIC 330-a can be configured to include logical functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 165-a, or both, and the O-eNB 325 with the near-RT RIC 330-a.

[0132] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 330-b, the non-RT RIC 330-b may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 330-a and may be received from a non-network data source or from a network function at the SMO 335 or the non-RT RIC 330-b. In some examples, the non-RT RIC 330-b or the near-RT RIC 330-a may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 330-b may monitor long-term trends and patterns of performance and perform corrective actions using an AI or ML model through the SMO 335 (e.g., via reconfiguration of O1) or via generation of a RAN management policy (e.g., an A1 policy).

[0133] In some implementations, as will be described in further detail herein, the network architecture 300 can support signaling for handover procedures in a service-based wireless system. In particular, aspects of the present disclosure relate to signaling that enables a UE 115 to perform a handover procedure from one network entity 105 to another network entity (or from one DU 165 to another DU) in a manner that minimizes disruption to active core network services at the UE 115.

[0134] Figure 4An example of a wireless communication system 400 that supports techniques for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. In some examples, aspects of the wireless communication system 400 may implement aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, or any combination thereof, or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, or any combination thereof. In particular, the wireless communication system 400 may support signaling, configuration, and other mechanisms, such as for Figure 1 As described, these signaling, configuration, and other mechanisms enable the UE 115 to perform a handover procedure from one network entity 105 to another (or from one DU to another) in a manner that minimizes disruption to active core network services 405 at the UE 115.

[0135] The wireless communication system 400 may include a UE 115-b, a first network entity 105-b (e.g., a source network entity 105-b), a second network entity 105-c (e.g., a target network entity 105-c), a first core network service 405-a, and a second core network service 405-b. In some implementations, the network entities 105-b, 105-c may include an example of an O-RAN entity, which includes multiple components, such as Figure 3 In this regard, Figure 4 The network entities 105 - b , 105 - c shown in FIG. 1 may additionally or alternatively be referred to as DU or eDU (eg, first / source DU, second / target DU).

[0136] The first core network service 405 - a and the second core network service 405 - b may be associated with a service-based network, such as Figure 2 . In some aspects, the service-based network including core network services 405-a, 405-b can be configured to communicate or interface with a RAN of the wireless communication system 400, wherein the RAN includes one or more network entities (e.g., a first network entity 105-b, a second network entity 105-c). In some implementations, the core network services 405-a, 405-b can be associated with a cloud platform or hosted by a cloud platform, wherein the corresponding core network services 405 are hosted at corresponding network addresses in the cloud platform.

[0137] The UE 115-b may communicate with each network entity 105 using a communication link 410 (e.g., a first communication link 410-a, a second communication link 410-b), which may be an example of an NR, LTE, or 6G link between the UE 115-b and each network entity 105. In some cases, the communication link 410 may include an example of an access link (e.g., a Uu link), which may include a bidirectional link that implements both uplink and downlink communications. Similarly, the network entity 105 of the RAN may be configured to communicate with a core network service 405 of a service-based network via communication links 415-a, 415-b (e.g., interfaced with the core network service 405), wherein the communication link 415 may be configured to facilitate bidirectional communication between each network entity 105 and each of the core network services 405. In some aspects, each core network service 405 - a , 405 - b may include a respective API configured to facilitate wireless communications with the network entity 105 and the UE 115 - b , e.g. Figure 1 The web service API 180 shown in .

[0138] In some aspects, the network entity 105 (e.g., DU, eDU) may facilitate traffic routing (e.g., service data unit routing) from the UE 115-b to the core network services 405, or vice versa. In other words, the network entity 105 may be configured to relay communications (e.g., service messages) from the UE 115-b to the core network services 405, or vice versa. The network entity 105 may facilitate traffic routing between devices directly, via other network entities 105, via a proxy, or any combination thereof.

[0139] In the context of a service-based wireless system, a UE 115-b may subscribe to various core network services 405 provided by the service-based network. However, as the UE 115-b moves within the network, the UE 115-b may perform a handover procedure from one cell to another and / or from one network entity 105 to another (e.g., a handover from a first network entity 105-b to a second network entity 105-c). In the context of a service-based network (e.g., a 6G network), the performance of a handover between network entities 105 may interrupt ongoing communications between the UE 115-b and the core network services 405 to which the UE 115-b is subscribed (e.g., interrupting the active core network services 405).

[0140] Thus, the wireless communication system 400 may support signaling for a handover procedure in a service-based network. In particular, the wireless communication system 400 may support the signaling that enables the UE 115-b to perform a handover procedure from a first network entity 105-b (e.g., a source DU) to a second network entity 105-c (e.g., a target DU) in a manner that minimizes disruption to active core network services 405 at the UE 115-a.

[0141] In some implementations, the service-based network may provide or support mobility services (e.g., core network mobility services) that control and handle mobility and connectivity management of the UE 115 within the wireless communication system 400. For example, the first core network service 405-a may include a mobility service, wherein a UE 115 that moves around within the network subscribes to the mobility service so that the mobility service can manage handover procedures and connectivity of the UE 115 as the UE 115 moves around within the network.

[0142] In some aspects, when UE 115-b is connected to the network, a mobility service (e.g., a first core network service 405-a) may maintain UE context information related to mobility. For example, the mobility service may maintain access and roaming restrictions (e.g., a mobility restriction list), which may include a list of: a list of public land mobile networks (PLMNs), radio access technologies (RATs) within each PLMN, and corresponding service areas that UE 115-b can or cannot access. In some aspects, the mobility service may maintain a UE subscription service or receive information from a UE subscription service to determine access and roaming restrictions for UE 115-b. In this regard, network elements such as eDUs, mobility services (e.g., core network mobility services), capability services (e.g., core network capability services), and UE subscription services (e.g., core network subscription services) may be provided by a service-based network and / or implemented in a cloud platform.

[0143] In some aspects, to facilitate mobility and handover of the UE 115-b within the network, the mobility service may store or retrieve capability information associated with mobility at the UE 115-b from the UE 115-b, the first network entity 105-b, and / or another core network service 405 (e.g., a core network capability service). Capabilities that may be reported by the UE 115-b and / or maintained at the core network service 405 (e.g., the mobility service and / or the capability service) may include radio access capabilities related to mobility (e.g., capabilities for each supported RAT).

[0144] In some aspects, the mobility service and the source network entity 105-b may use a subscription notification mechanism to obtain access and roaming restrictions and UE radio access capabilities related to mobility and access stratum (AS) protocol layer configuration from the UE subscription and capability service. For example, a capability service (e.g., core network service 405) may maintain UE radio access capabilities related to AS protocol layer configuration, and the mobility service may retrieve UE capabilities from the capability service (e.g., by subscribing to, notifying, or querying the capability service).

[0145] The source network entity 105-b (e.g., a source eDU communicatively coupled to UE 115-b) can be configured to, when UE115-b is operating in a service cell supported by the first network entity 105-b, obtain UE-related capabilities (e.g., obtained from UE115-b, mobility services, capability services, etc.) and determine the RLC, MAC, and PHY layer configurations for UE 115-b.

[0146] In some aspects, both the UE 115-b and the source network entity 105-b may be aware of the connection status of the UE 115-b (e.g., whether the UE is connected to the network (eDU)). That is, the UE 115-b and the source network entity 105-b may be configured to maintain connection status information of the UE 115-b. For example, the source network entity 105 may maintain a list of all UEs 115 that are currently connected to the network entity 105-b, and may additionally maintain a list of all UEs 115 that have previously been connected to the network entity 105-b.

[0147] For each UE 115 connected to the network (and / or for each UE subscribed to the mobility service), the mobility service may maintain information about the network entity 105 (e.g., DU, eDU) and the cell(s) supported by the network entity 105 serving the respective UE 115. In other words, for each UE 115 in the network (or for each UE 115 subscribed to the mobility service), the mobility service may maintain historical mobility information associated with past and current network entities 105, DUs, serving cells, etc. to which the UE 115 has been connected. The mobility service may also maintain (e.g., store) load information associated with the network entities or cells (e.g., the amount of UEs 115 supported by each network entity 105 or serving cell), traffic load associated with each such UE 115, etc. As will be described in further detail herein, such historical mobility information, load information, etc. may be used by the mobility service (e.g., the first core network service 405-a) to select a target cell / DU / network entity 105 to which the UE 115-b will be handed over.

[0148] Examples may prove illustrative. Figure 4 In the wireless communication system 400 shown in FIG. 4 , UE 115-b can perform communication with a first network entity 105-b. For example, UE 115-b can transmit service messages with one or more core network services 405 active at UE 115-b via the first network entity 105-b, where the core network services 405 are provided by a service-based network. In other words, the first network entity 105-b can relay service messages between UE 115-b and one or more core network services 405 active at UE 115-b.

[0149] UE 115-b can establish communication with a mobility service (e.g., a first core network service 405-a). In other words, UE 115-b can subscribe to the mobility service so that the mobility service can manage the mobility and connection management (e.g., managing the switching process) of UE 115-b within the wireless communication system 400. For example, UE 115-b can send a service request for establishing a service with the mobility service to a network address associated with the mobility service (e.g., the first core network service 405-a), and can receive control signaling indicating a service context for communicating with the mobility service based on the service request. The service context may include various communication parameters for communicating with the mobility service. In this example, the first network entity 105-b can relay each communication between UE 115-b and the mobility service. In addition, subsequent communications between UE 115-b and the mobility service 605 can be performed based on the service context.

[0150] In some aspects, the UE 115-b may send capability information associated with the UE 115-b to the first network entity 105-b, the mobility service, the additional core network service 405 (e.g., a core network capability service), or any combination thereof. The capability information may include: supported RATs, capabilities related to AS protocol layer configuration, PLMNs and / or service cells that the UE 115-b can or cannot access, and the like. Similarly, the first network entity 105-b, the second network entity 105-c, or both may send capability information to the mobility service, another core network service 405 (e.g., a core network capability service), or both. The capability information associated with the network entity 105 may include the core network services supported by each network entity 105 (e.g., each eDU may provide information about the entire set of services / slices it supports).

[0151] In the event that UE 115-b and / or network entity 105 sends capability information to a capability service (e.g., a core network capability service), mobility service 605 may be configured to retrieve capability information from the capability service in order to facilitate a handover procedure for UE 115-b. As previously described herein, mobility service 605 may use such capability information to select a target network entity 105 and / or target cell for UE 115-b.

[0152] In some implementations, UE 115-b may be configured with a measurement configuration that includes one or more trigger conditions associated with execution of a handover procedure at UE 115-b. The measurement configuration may be related to the mobility of both the source eDU (e.g., the first network entity 105-b) and the UE 115-b. As another example, UE 115-b may be configured with a measurement configuration for cell-level (e.g., layer 3 (L3)) measurements, where L3 reports may be sent to the first network entity 105-b and / or the mobility service. In addition, the first network entity 105-b and / or the mobility service may make a handover decision based on the received cell-level (e.g., L3) measurement reports.

[0153] In some aspects, the measurement configuration may be configured by the first network entity 105-b, the mobility service (e.g., the first core network service 405-a), or both. In addition, the handover decision for the UE 115-b may be made by the first network entity 105-b, the mobility service (e.g., the first core network service 405-a), or both. In other words, depending on whether the mobility service or the source eDU configures the measurement configuration, processes the measurement report, and makes the handover decision, there may be two (or more) alternative methods for inter-eDU handover. Reference will be made to Figure 5 and Figure 6 Two separate methods for inter-eDU switching are further shown and described.

[0154] In some aspects, the measurement configuration may include or indicate: a configuration of downlink reference signals that the UE 115-b should measure for mobility purposes (e.g., to determine a handover process), and a configuration of uplink reference signals that the first network entity 105-b should measure for mobility purposes. Additionally, the measurement configuration may indicate: a measurement gap, and a trigger condition (e.g., an event trigger) for reporting a measurement report if the trigger condition is met.

[0155] In the case where the mobility service configures the measurement configuration, the mobility service (e.g., core network mobility service or first core network service 405-a) may be configured to determine and configure the measurement configuration using stored UE context information (e.g., UE 115-b capability information, access and mobility restrictions, etc.). In some cases, the measurement configuration (e.g., measurement report) may take the form of a subscription notification mechanism, in which subscriptions to the mobility service and mobility-related reporting events are defined, and the source eDU or UE 115-b notifies the mobility service if a trigger condition for handover is met.

[0156] In some aspects, the UE 115-b, the first network entity 105-b, or both may perform measurements on a signal (e.g., a reference signal) in accordance with the measurement configuration. In particular, the UE 115-b and / or the first network entity 105-b may perform measurements on a received reference signal to identify satisfaction of a trigger condition for a handover procedure, where the trigger condition may be identified by the measurement configuration.

[0157] UE 115-b may send a measurement report to first network entity 105-b and / or mobility service. UE 115-b may send the measurement report according to the received measurement configuration. For example, UE 115-b may send the measurement report according to a defined period or frequency, based on satisfaction of a trigger condition, or both. In some cases, the measurement report may indicate satisfaction of a trigger condition for performing a handover procedure.

[0158] Subsequently, the first network entity 105-b, the mobility service, or both may perform a handover decision. In particular, the first network entity 105-b and / or the mobility service may be configured to receive and process measurements or event reports (e.g., event reports indicating satisfaction of a triggering condition) from the UE 115-b in order to make a handover decision (e.g., determine whether to initiate a handover procedure at the UE 115-b).

[0159] In the event that the network entity 105-b makes a handover decision, the first network entity 105-b may send a handover request to the mobility service. The handover request message may indicate the candidate target network entity 105. For example, the UE 115-b may measure reference signals received from a plurality of candidate target network entities 105 (e.g., the second network entity 105-c) and may indicate one or more of the candidate target network entities 105 in a measurement report, wherein the first network entity 105-b relays the indication of the candidate target network entities 105 via the handover request message. The handover request message (or other message indicating satisfaction of a triggering condition for a handover) may indicate a list of core network services 405 that are currently active at the UE 115-b. Such information may enable the mobility service to perform a handover decision and / or select a target network entity 105 / target DU / target cell for a potential handover procedure.

[0160] Once the handover decision is made, the mobility service may select a target network entity 105 to which the UE 115-b will be handed over. Figure 4 As shown, a mobility service (e.g., a core network mobility service or a first core network service 405-a) may select a second network entity 105-c as a target for a handover procedure at UE 115-b. In addition, in some aspects, the mobility service may select a serving cell of the second network entity 105-c to which UE 115-b will be handed off.

[0161] The mobility service may select a target network entity 105-c and / or a target serving cell for the handover procedure based on a number of parameters or factors, including, but not limited to, capability information associated with the UE 115-b, active core network services 405 at the UE 115-b (e.g., core network services supported by the target network entity 105), an indication of a candidate target network entity 105 indicated via the handover request, a mobility history of the UE 115-b, traffic loads associated with the candidate network entities 105 and / or the target serving cell, or any combination thereof. For example, the mobility service may select a target network entity 105 (e.g., a second network entity 105-c) that supports at least one core network service 405 currently active at the UE 115-b.

[0162] In some aspects, the mobility service may send a handover request to the second network entity 105-c. The mobility service may send the handover request based on selecting the second network entity 105-c as a target for the handover procedure. In some implementations, the handover request may indicate a set of core network services 405 active at the UE 115-b, access and roaming access restriction information associated with the UE 115-b, or both.

[0163] In some implementations, the second network entity 105-c may perform admission control to determine which of the active core network services 405 at the UE 115-b are supported by the second network entity 105-c (e.g., determining a list of acceptable services from those indicated in the handover request). For example, in the case of a slice, the list of active core network services 405 that the second network entity 105-c can accept / support may be based on the QoS requirements of the flows associated with the slice.

[0164] The mobility service may receive an acknowledgement (ACK) message from the second network entity 105-c based on (e.g., in response to) the handover request. In some implementations, the ACK message may indicate one or more active core network services 405 at the UE 115-b that are supported and / or accepted by the second network entity 105-c. In other words, the ACK message may indicate a list of accepted / supported core network services 405.

[0165] In some aspects, the second network entity 105-c may indicate in the ACK message a communication configuration for communicating with the second network entity 105-c (e.g., for relaying to the UE 115-b). For example, the target network entity 105-c may determine the target cell AS protocol layer configuration and the configuration(s) associated with the accepted core network service 405, and indicate such configuration to the mobility service. In this case, the mobility service may determine a measurement configuration for the target network entity 105-c and / or the target cell for mobility purposes (e.g., a new measurement configuration for the target cell).

[0166] In an alternative implementation, the second network entity 105-c may deny the handover request (e.g., send a NACK message). For example, if the second network entity 105-c does not support any core network services 405 currently active at the UE 115-b, the second network entity 105-c may deny the handover request. In this case, the mobility service may reselect a new target for the handover process and send a new handover request to the newly selected target.

[0167] Subsequently, the mobility service may send to the first network entity 105-b and / or UE 115-b: a handover command (e.g., for relaying to UE 115-b), together with instructions for UE 115-b to perform a handover process from the first network entity 105-b to the second network entity 105-c. The handover command may include various information associated with the second network entity 105-c, including, but not limited to: an identifier associated with the second network entity 105-c and / or a service cell (e.g., a target cell) supported by the second network entity 105-c, communication parameters for communicating with the second network entity 105-c (e.g., communication configuration, such as a target cell AS protocol layer configuration), a list of core network services 405 active at UE 115-b and supported / accepted by the second network entity 105-c, a new measurement configuration associated with the second network entity 105-c, and the like.

[0168] In some aspects, the first network entity 105-b and the second network entity 105-c may establish a communication tunnel (e.g., an IP tunnel) between the devices. In some aspects, the communication tunnel may be configured to relay data packets intended for the UE 115-b between the devices during the execution of the handover procedure. In other words, during the handover execution, for flows to which data forwarding is applied, direct forwarding from the source eDU to the target eDU may be performed over the established IP tunnel.

[0169] For example, during execution of the handover process (e.g., before completion), the first network entity 105-b may receive a message from the core network service 405 and may relay one or more packets associated with the second network entity 105-c via the communication tunnel based on (e.g., in response to) receiving the message, so that the second network entity 105-c can relay the data packets to the UE 115-b after (or during) execution of the handover process.

[0170] UE 115-b may establish communication with a second network entity 105-c. UE 115-b may establish communication with a second network entity 105-c based on receiving a handover command (e.g., based on information included in the handover command). Subsequently, the second network entity 105-c may send a message to the mobility service indicating that the handover process is complete. For example, the target eDU (e.g., the second network entity 105-c) may indicate the target cell ID to the mobility service when the handover is complete. In some cases, the mobility service may provide notification of the completed handover process to other core network services 405 (e.g., other core network services 405 active at UE 115-b). Additionally, when the handover is complete, the target eDU may request an access gateway (e.g., UPF) to switch the path to the target eDU.

[0171] UE 115-b may perform communication with the second network entity 105-c upon completion of the handover process. For example, UE 115-b may transmit service messages with one or more core network services 405 active at UE 115-b via the second network entity 105-c. In other words, the first network entity 105-b may relay service messages between UE 115-b and one or more core network services 405 active at UE 115-b.

[0172] The techniques described herein may enable a UE 115-b to perform a handover procedure between DUs and / or between network entities 105 of a service-based wireless system while minimizing disruption to active core network services 405 at the UE 115-c. In particular, aspects of the present disclosure support techniques that enable a UE 115-b to perform a handover procedure to a target DU / target network entity 105 that supports at least some of the active core network services 405 at the UE 115-b. Thus, aspects of the present disclosure may reduce disruption to communications performed with the core network services 405, thereby reducing or preventing the need for the UE 115-b to continually reestablish communications with the core network services 405. In this regard, the techniques described herein may reduce signaling associated with a UE 115-b subscribing to core network services 405, reduce disruptions, and improve the overall user experience.

[0173] Figure 5 An example of a process flow 500 for supporting techniques for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. In some examples, aspects of the process flow 500 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, or any combination thereof. In particular, the process flow 500 illustrates signaling, as described with reference to FIG. Figure 1-4 As described in other aspects, the signaling enables UE 115-c to perform a switching process from one network entity 105 to another network entity (or from one DU to another DU) in a manner that minimizes disruption to active core network services at UE 115-c.

[0174] Process flow 500 may include UE 115-c, first network entity 105-d (e.g., source network entity 105-d), second network entity 105-e (e.g., target network entity 105-e), and mobility service 505 (e.g., core network service or core network mobility service), which may be UE 115, network entity 105, core network service, and reference Figure 1-4 In some aspects, the mobility service 505 can control and handle mobility and connection management of the UE 115 within the wireless communication system.

[0175] In some aspects, the mobility service 505 may be included in a service-based network (e.g., Figure 2 In this case, the service-based network including the mobility service 505 can be configured to interface with (e.g., communicate with) a RAN including network entities 105-d, 105-e (e.g., DU, eDU) to facilitate communication between the service-based network and the UE 115-c. In this regard, Figure 5 The signaling shown in may include example signaling within a network having a service-based architecture (e.g., a 6G system).

[0176] In some examples, the operations shown in process flow 500 can be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. The following alternative examples can be implemented in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0177] At 510, UE 115-c may perform communications with first network entity 105-d. For example, UE 115-c may communicate service messages with one or more core network services active at UE 115-c via first network entity 105-d, where the core network services are provided by a service-based network. In other words, first network entity 105-d may relay service messages between UE 115-c and one or more core network services active at UE 115-c.

[0178] At 515, the UE 115-c may establish communication with a mobility service 505 (e.g., a core network mobility service). In other words, the UE 115-c may subscribe to the mobility service 505 so that the mobility service 505 may manage mobility and connection management (e.g., manage handover procedures) of the UE 115-c within the wireless communication system.

[0179] For example, the UE 115-c may send a service request for establishing a service with the mobility service 505 to a network address associated with the mobility service 505, and may receive control signaling indicating a service context for communicating with the mobility service 505 based on the service request. In this example, the first network entity 105-d may relay various communications between the UE 115-c and the mobility service. In addition, subsequent communications between the UE 115-c and the mobility service 505 may be performed based on the service context.

[0180] At 520, the UE 115-c may send capability information associated with the UE 115-c to the first network entity 105-d, the mobility service 505, the additional core network service (e.g., the core network capability service), or any combination thereof. The capability information may include supported RATs, capabilities related to AS protocol layer configuration, PLMNs, and / or serving cells that the UE 115-c can or cannot access, and the like.

[0181] In the event that UE 115-c sends capability information to a capability service (e.g., a core network capability service), the mobility service 505 may be configured to retrieve the capability information from the capability service to facilitate a handover procedure for the UE 115-c. As previously described herein, such capability information may be used by the mobility service 505 to select a target network entity 105 and / or a target cell for the UE 115-c.

[0182] At 525, the UE 115-c may receive a measurement configuration from the mobility service 505 (and via the first network entity 105-d) indicating one or more trigger conditions associated with the execution of a handover procedure at the UE 115-c. The measurement configuration may be related to the mobility of both the source eDU (e.g., the first network entity 105-d) and the UE 115-c.

[0183] In some aspects, the measurement configuration may include or indicate: a configuration of downlink reference signals that the UE 115-c should measure for mobility purposes (e.g., to determine a handover process), and a configuration of uplink reference signals that the first network entity 105-d should measure for mobility purposes. Additionally, the measurement configuration may indicate: a measurement gap, and a trigger condition (e.g., an event trigger) for reporting a measurement report if the trigger condition is met.

[0184] At 530, the UE 115-c, the first network entity 105-d, or both may perform measurements on a signal (e.g., a reference signal) according to the measurement configuration received at 525. In particular, the UE 115-c and / or the first network entity 105-d may perform measurements on the received reference signal to identify satisfaction of a trigger condition for a handover procedure, where the trigger condition may be identified by the measurement configuration.

[0185] For example, the UE 115-c may perform measurements on reference signals received from the first network entity 105-d and other potential target network entities 105 (e.g., the second network entity 105-e) according to the measurement configuration to facilitate the handover determination. In addition, the first network entity 105-d may perform measurements on uplink reference signals received from the UE 115-c according to the measurement configuration to facilitate the handover determination. In some aspects, if the quality, strength, or performance of the reference signal from the first network entity 105-d fails to meet a threshold, or if the quality, strength, or performance of the reference signal from the second network entity 105-e meets an additional threshold, or both, the UE 115-c may identify a trigger condition for a handover procedure. Similarly, if the quality, strength, or performance of the reference signal from the UE 115-c fails to meet a threshold, the first network entity 105-d may identify a trigger condition for a handover procedure.

[0186] At 535, the UE 115-c, the first network entity 105-d, or both may send a message to the mobility service 505 indicating satisfaction of a trigger condition for performing a handover procedure. In this regard, the UE 115-c and / or the first network entity 105-d may send the message at 535 based on receiving a measurement configuration at 525, performing measurements at 530, identifying satisfaction of a trigger condition based on the measurements, or any combination thereof.

[0187] In some aspects, the message indicating the triggering condition may additionally or alternatively indicate the candidate target network entity 105. For example, the UE 115-c may measure reference signals received from multiple candidate target network entities 105 (e.g., the second network entity 105-e) and may indicate one or more of the candidate target network entities 105 in the message / event report (e.g., indicating the candidate network entities 105 that exhibited sufficient performance).

[0188] Additionally or alternatively, the UE 115-c and / or the first network entity 105-d may indicate a list of core network services currently active at the UE 115-c via the message at 535. Such information may enable the mobility service 505 to perform a handover decision and select a target network entity 105 / target DU / target cell for a potential handover procedure.

[0189] At 540, the mobility service 505 may perform a handover decision. In particular, the mobility service 505 may be configured to receive and process measurements or event reports (e.g., event reports indicating satisfaction of a triggering condition) from the UE 115-c and / or the first network entity 105-d in order to make a handover decision (e.g., determine whether to initiate a handover procedure at the UE 115-c).

[0190] At 545, if the mobility service 505 determines that a handover procedure is triggered, the mobility service 505 may select a target network entity 105 to which the UE 115-c will be handed over. Figure 5 As shown, the mobility service 505 may select the second network entity 105-e as a target for a handover procedure at the UE 115-c. Additionally, in some aspects, the mobility service 505 may select a serving cell of the second network entity 105-e to which the UE 115-c is to be handed off.

[0191] The mobility service 505 can select a target network entity 105-e and / or a target serving cell for the switching process based on multiple parameters or factors, including but not limited to: capability information associated with the UE 115-c received at 520, active core network services at the UE 115-c (e.g., core network services supported by the target network entity 105), an indication of the candidate target network entity 105 indicated in the event report / measurement report at 535, the mobility history of the UE 115-c, the traffic load associated with the candidate network entity 105 and / or the target serving cell, or any combination thereof.

[0192] For example, the mobility service 505 may select a target network entity 105 (e.g., a second network entity 105-e) that supports at least one core network service currently active at the UE 115-c. In addition, in the event that multiple candidate network entities 105 support one or more core network services active at the UE 115-c, the mobility service 505 may select the network entity 105 that supports the highest proportion of active core network services at the UE 115-c. As another example, in the event that the message indicating the trigger condition at 535 indicates a set of candidate network entities 105, the mobility service 505 may select one of the candidate network entities 105 (and the serving cell supported by the selected network entity 105).

[0193] At 550, the mobility service 505 may send a handover request to the second network entity 105-e (e.g., the selected target network entity 105-e). The mobility service 505 may send the handover request at 550 based on selecting the second network entity 105-e as the target of the handover procedure at 545. In some implementations, the handover request may indicate a set of core network services active at the UE 115-c.

[0194] In some implementations, the second network entity 105-e may perform admission control to determine which of the active core network services at the UE 115-c are supported by the second network entity 105-e (e.g., determining a list of acceptable services from those indicated in the handover request). For example, in the case of slices, the list of active core network services that the second network entity 105-e can accept / support may be based on the QoS requirements of the flows associated with the slice.

[0195] At 555, the mobility service 505 may receive an ACK message from the second network entity 105-e. The mobility service 505 may receive the ACK message from the second network entity 105-e based on (e.g., in response to) the handover request at 550. In some implementations, the ACK message may indicate one or more active core network services at the UE 115-c that are supported and / or accepted by the second network entity 105-e. In other words, the ACK message may indicate a list of accepted / supported core network services.

[0196] In some aspects, the second network entity 105-e may indicate in the ACK message a communication configuration for communicating with the second network entity 105-e (e.g., for relaying to the UE 115-c). For example, the target network entity 105-e may determine a target cell AS protocol layer configuration and configuration(s) related to the accepted core network service and indicate these configurations to the mobility service 505. In this case, the mobility service 505 may determine a measurement configuration for the target network entity 105-e and / or the target cell for mobility purposes (e.g., a new measurement configuration for the target cell as shown and described at 525).

[0197] In an alternative implementation, the second network entity 105-e may reject the handover request (e.g., send a NACK message). For example, if the second network entity 105-e does not support any core network services currently active at the UE 115-c, the second network entity 105-e may reject the handover request. In this case, the mobility service 505 may reselect a new target for the handover process and send a new handover request to the newly selected target.

[0198] At 560, the mobility service 505 may send a handover command to the first network entity 105-d and / or the UE 115-c (e.g., for relaying to the UE 115-c), along with instructions for the UE 115-c to perform a handover procedure from the first network entity 105-d to the second network entity 105-e. The mobility service 505 may send the handover command based on performing a handover decision at 540, selecting a target cell / network entity 105-e at 545, sending a handover request at 550, receiving an ACK message at 555, or any combination thereof.

[0199] The handover command may include various information associated with the second network entity 105-e, including but not limited to: an identifier associated with the second network entity 105-e and / or a service cell supported by the second network entity 105-e (e.g., a target cell), communication parameters for communicating with the second network entity 105-e (e.g., communication configuration, such as a target cell AS protocol layer configuration), a list of core network services active at the UE 115-c and supported / accepted by the second network entity 105-e, a new measurement configuration associated with the second network entity 105-e, and the like.

[0200] At 565, the first network entity 105-d and the second network entity 105-e may establish a communication tunnel (e.g., an IP tunnel) between the respective devices. In some aspects, the communication tunnel may be configured to relay data packets intended for the UE 115-c between the respective devices during the execution of the handover procedure. In other words, during the handover execution, for flows to which data forwarding is applied, direct forwarding from the source eDU to the target eDU may be performed over the established IP tunnel.

[0201] For example, during execution of a handover process (e.g., before completion), the first network entity 105-d may receive a message from a core network service and may relay one or more packets associated with the message to the second network entity 105-e via a communication tunnel, so that the second network entity 105-e may relay the data packets to the UE 115-c after (or during) execution of the handover process.

[0202] At 570, the UE 115-c may establish communication with the second network entity 105-e. The UE 115-c may establish communication with the second network entity 105-e based on receiving the handover command (eg, based on information included in the handover command).

[0203] At 575, the second network entity 105-e may send a message to the mobility service 505 indicating that the handover procedure is complete. For example, the target eDU (e.g., the second network entity 105-e) may indicate the target cell ID to the mobility service 505 when the handover is complete. In some cases, the mobility service 505 may provide notification of the completed handover procedure to other core network services (e.g., other core network services active at the UE 115-c). Additionally, when the handover is complete, the target eDU may request an access gateway (e.g., UPF) to switch the path to the target eDU.

[0204] At 580, UE 115-c may perform communications with second network entity 105-e. For example, UE 115-c may transmit service messages with one or more core network services active at UE 115-c via second network entity 105-e. In other words, first network entity 105-d may relay service messages between UE 115-c and one or more core network services active at UE 115-c. UE 115-c may communicate with second network entity 105-e (and active core network services) at 580 based on receiving a handover command at 560, establishing communications at 570, sending a confirmation of the handover process at 575, or any combination thereof.

[0205] Figure 6An example of a process flow 600 for supporting techniques for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. In some examples, aspects of the process flow 600 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, the process flow 600, or any combination thereof. In particular, the process flow 600 illustrates signaling, as described with reference to FIG. Figure 1-5 As described in other aspects, the signaling enables UE 115-d to perform a switching process from one network entity 105 to another network entity (or from one DU to another DU) in a manner that minimizes disruption to active core network services at UE 115-d.

[0206] Process flow 600 may include UE 115-d, first network entity 105-f (e.g., source network entity 105-f), second network entity 105-g (e.g., target network entity 105-g), and mobility service 605 (e.g., core network service or core network mobility service), which may be UE 115, network entity 105, core network service, and reference Figure 1-5 In some aspects, the mobility services 605 may control and handle mobility and connection management of the UE 115 within the wireless communication system.

[0207] In some aspects, the mobility service 605 may be included in a service-based network (e.g., Figure 2 In this case, the service-based network including the mobility service 605 can be configured to interface with (e.g., communicate with) a RAN including network entities 105-f, 105-g (e.g., DU, eDU) to facilitate communication between the service-based network and the UE 115-d. In this regard, Figure 6 The signaling shown in may include example signaling within a network having a service-based architecture (e.g., a 6G system).

[0208] In some examples, the operations shown in process flow 600 can be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. The following alternative examples can be implemented in which some of the steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0209] At 610, UE 115-d may perform communications with first network entity 105-f. For example, UE 115-d may communicate service messages with one or more core network services active at UE 115-d via first network entity 105-f, where the core network services are provided by a service-based network. In other words, first network entity 105-f may relay service messages between UE 115-d and one or more core network services active at UE 115-d.

[0210] At 615, the UE 115-d may establish communication with a mobility service 605 (e.g., a core network mobility service). In other words, the UE 115-d may subscribe to the mobility service 605 so that the mobility service 605 may manage mobility and connection management (e.g., manage handover procedures) of the UE 115-d within the wireless communication system.

[0211] For example, the UE 115-d may send a service request for establishing a service with the mobility service 605 to a network address associated with the mobility service 605, and may receive control signaling indicating a service context for communicating with the mobility service 605 based on the service request. In this example, the first network entity 105-f may relay various communications between the UE 115-d and the mobility service. In addition, subsequent communications between the UE 115-d and the mobility service 605 may be performed based on the service context.

[0212] At 620, the UE 115-d may send capability information associated with the UE 115-d to the first network entity 105-f, the mobility service 605, the additional core network service (e.g., the core network capability service), or any combination thereof. The capability information may include supported RATs, capabilities related to AS protocol layer configuration, PLMNs, and / or serving cells that the UE 115-d can or cannot access, and the like.

[0213] In the event that UE 115-d sends capability information to a capability service (e.g., a core network capability service), mobility service 605 may be configured to retrieve capability information from the capability service to facilitate a handover procedure for UE 115-d. As previously described herein, such capability information may be used by mobility service 605 to select a target network entity 105 and / or a target cell for UE 115-d.

[0214] At 625, the UE 115-d may receive a measurement configuration from the first network entity 105-f, the measurement configuration indicating one or more trigger conditions associated with the execution of a handover procedure at the UE 115-d. In other words, the first network entity 105-f may configure the measurement configuration. The measurement configuration may be related to the mobility of both the source eDU (e.g., the first network entity 105-f) and the UE 115-d.

[0215] and Figure 5 Compared to the process flow 500 shown in FIG. 5 , in the process flow 500 , the mobility service 505 configures the measurement configuration and performs the handover decision, while Figure 6 The source network entity 105-f shown may configure the measurement configuration and make the handover decision. In this case, the mobility service may forward access and roaming access restriction information to the source eDU and the target eDU. In some cases, enabling the source eDU to configure the measurement configuration and measurement reporting may enable the source eDU to frequently update the measurement gaps. In addition, enabling the source eDU (e.g., the first network entity 105-f) to configure the measurement configuration may provide some efficiencies because the source eDU may have complete and up-to-date knowledge of the time-frequency resources consumed by data and control signaling.

[0216] In additional or alternative implementations, the source eDU and the mobility service 605 may implement various hybrid schemes in which measurement configurations and other information associated with mobility are split between various devices. For example, according to one hybrid scheme, the mobility service 605 may determine an event type and triggering conditions for a handover procedure, wherein the source eDU (e.g., the first network entity 105-f) may configure the actual measurement configuration (e.g., measurement objects, frequencies to be measured), measurement reports, and associated measurement gap configurations. In this example, the mobility service may indicate information about the event type and triggering conditions to the source eDU.

[0217] In some aspects, the measurement configuration may include or indicate: a configuration of downlink reference signals that the UE 115-d should measure for mobility purposes (e.g., to determine a handover process), and a configuration of uplink reference signals that the first network entity 105-f should measure for mobility purposes. Additionally, the measurement configuration may indicate: a measurement gap, and a trigger condition (e.g., an event trigger) for reporting a measurement report if the trigger condition is met.

[0218] At 630, the UE 115-d, the first network entity 105-f, or both may perform measurements on a signal (e.g., a reference signal) according to the measurement configuration transmitted at 625. In particular, the UE 115-d and / or the first network entity 105-f may perform measurements on the received reference signal to identify satisfaction of a trigger condition for a handover procedure, where the trigger condition may be identified by the measurement configuration.

[0219] At 635, the UE 115-d may send a measurement report to the first network entity 105-f. The UE 115-d may send the measurement report according to the measurement configuration received at 625. For example, the UE 115-d may send the measurement report according to a defined period or frequency, based on satisfaction of a trigger condition, or both.

[0220] At 640, the first network entity 105-f may perform a handover decision. In particular, the first network entity 105-f may be configured to receive and process measurements or event reports (e.g., event reports indicating satisfaction of a triggering condition) from the UE 115-d in order to make a handover decision (e.g., determine whether to initiate a handover procedure at the UE 115-d).

[0221] At 645, if the first network entity 105-f determines to trigger a handover procedure, the first network entity 105-f may send a handover request message to the mobility service 605. In this regard, the first network entity 105-f may send the handover request based on sending a measurement configuration at 625, performing measurements at 630, receiving a measurement report at 635, identifying satisfaction of a trigger condition, performing a handover decision at 640, or any combination thereof.

[0222] In some aspects, the handover request message may additionally or alternatively indicate the candidate target network entities 105. For example, the UE 115-d may measure reference signals received from a plurality of candidate target network entities 105 (e.g., the second network entity 105-g), and may indicate one or more of the candidate target network entities 105 in a measurement report, wherein the first network entity 105-f relays the indication of the candidate target network entities 105 via the handover request message. In additional or alternative implementations, the UE 115-d may indicate a target cell associated with the target eDU in the handover request.

[0223] Additionally or alternatively, the first network entity 105-f may indicate a list of core network services currently active at the UE 115-d via the handover request message at 645. Such information may enable the mobility service 605 to perform a handover decision and select a target network entity 105 / target DU / target cell for a potential handover procedure.

[0224] At 650, the mobility service 605 may select a target network entity 105 to which the UE 115-d will be handed off. Figure 6 As shown, the mobility service 605 may select the second network entity 105-g as a target for a handover procedure at the UE 115-d. Additionally, in some aspects, the mobility service 605 may select a serving cell of the second network entity 105-g to which the UE 115-d will be handed over.

[0225] The mobility service 605 may select a target network entity 105-g and / or a target serving cell for the handover procedure based on a number of parameters or factors, including, but not limited to, capability information associated with the UE 115-d received at 620, active core network services at the UE 115-d (e.g., core network services supported by the target network entity 105), an indication of a candidate target network entity 105 indicated in the handover request at 645, a mobility history of the UE 115-d, traffic loads associated with the candidate network entities 105 and / or the target serving cell, or any combination thereof. For example, the mobility service 605 may select a target network entity 105 (e.g., a second network entity 105-g) that supports at least one core network service currently active at the UE 115-d.

[0226] At 655, the mobility service 605 may send a handover request to the second network entity 105-g (e.g., the selected target network entity 105-g). The mobility service 605 may send the handover request at 655 based on selecting the second network entity 105-g as a target for the handover procedure at 650. In some implementations, the handover request may indicate a set of core network services active at the UE 115-d, access and roaming access restriction information associated with the UE 115-d, or both.

[0227] In some implementations, the second network entity 105-g may perform admission control to determine which of the active core network services at the UE 115-d are supported by the second network entity 105-g (e.g., determining a list of acceptable services from those indicated in the handover request). For example, in the case of a slice, the list of active core network services that the second network entity 105-g may accept / support may be based on the QoS requirements of the flows associated with the slice.

[0228] At 660, the mobility service 605 may receive an ACK message from the second network entity 105-g. The mobility service 605 may receive the ACK message from the second network entity 105-g based on the handover request at 655 (e.g., in response to the handover request). In some implementations, the ACK message may indicate one or more active core network services at the UE 115-d that are supported and / or accepted by the second network entity 105-g. In other words, the ACK message may indicate a list of accepted / supported core network services.

[0229] In some aspects, the second network entity 105-g may indicate in the ACK message a communication configuration for communicating with the second network entity 105-g (e.g., for relaying to the UE 115-d). For example, the target network entity 105-g may determine a target cell AS protocol layer configuration and configuration(s) related to the accepted core network service and indicate these configurations to the mobility service 605. In this case, the target network entity 105-g may determine a measurement configuration for the target network entity 105-g and / or the target cell for mobility purposes (e.g., a new measurement configuration for the target cell) and may indicate the measurement configuration to the mobility service 605 (for relaying to the UE 115-d).

[0230] In an alternative implementation, the second network entity 105-g may deny the handover request (e.g., send a NACK message). For example, if the second network entity 105-g does not support any core network services currently active at the UE 115-d, the second network entity 105-g may deny the handover request. In this case, the mobility service 605 may reselect a new target for the handover process and send a new handover request to the newly selected target.

[0231] At 665, the mobility service 605 may send a handover command to the first network entity 105-f and / or the UE 115-d (e.g., for relaying to the UE 115-d), along with instructions for the UE 115-d to perform a handover procedure from the first network entity 105-f to the second network entity 105-g. The mobility service 605 may send the handover command based on performing a handover decision at 640, selecting a target cell / network entity 105-g at 650, sending a handover request at 655, receiving an ACK message at 660, or any combination thereof.

[0232] The handover command may include various information associated with the second network entity 105-g, including, but not limited to: an identifier associated with the second network entity 105-g and / or a service cell supported by the second network entity 105-g (e.g., a target cell), communication parameters for communicating with the second network entity 105-g (e.g., communication configuration, such as a target cell AS protocol layer configuration), a list of core network services active at the UE 115-d and supported / accepted by the second network entity 105-g, a new measurement configuration associated with the second network entity 105-g, and the like.

[0233] At 670, the first network entity 105-f and the second network entity 105-g may establish a communication tunnel (e.g., an IP tunnel) between the respective devices. In some aspects, the communication tunnel may be configured to relay data packets intended for the UE 115-d between the respective devices during the execution of the handover procedure. In other words, during the handover execution, for flows to which data forwarding is applied, direct forwarding from the source eDU to the target eDU may be performed over the established IP tunnel.

[0234] For example, during execution of a handover process (e.g., before completion), the first network entity 105-f may receive a message from a core network service and may relay one or more packets associated with the message to the second network entity 105-g via a communication tunnel, so that the second network entity 105-g may relay data packets to the UE 115-d after (or during) execution of the handover process.

[0235] At 675, UE 115-d may establish communication with second network entity 105-g. UE 115-d may establish communication with second network entity 105-g based on receiving the handover command (eg, based on information included in the handover command).

[0236] At 680, the second network entity 105-g may send a message to the mobility service 605 indicating that the handover procedure is complete. For example, the target eDU (e.g., the second network entity 105-g) may indicate the target cell ID to the mobility service 605 when the handover is complete. In some cases, the mobility service 605 may provide notification of the completed handover procedure to other core network services (e.g., other core network services active at the UE 115-d). Additionally, when the handover is complete, the target eDU may request an access gateway (e.g., UPF) to switch the path to the target eDU.

[0237] At 685, UE 115-d may perform communications with second network entity 105-g. For example, UE 115-d may transmit service messages with one or more core network services active at UE 115-d via second network entity 105-g. In other words, first network entity 105-f may relay service messages between UE 115-d and one or more core network services active at UE 115-d. UE 115-d may communicate with second network entity 105-g (and active core network services) at 685 based on receiving a handover command at 665, establishing communications at 675, sending a confirmation of the handover process at 680, or any combination thereof.

[0238] Figure 7 A block diagram 700 of a device 705 supporting techniques for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of a UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0239] The receiver 710 may provide a unit for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies for connection state mobility in service-based wireless systems). The information may be delivered to other components of the device 705. The receiver 710 may utilize a single antenna, or may utilize a group of multiple antennas.

[0240] The transmitter 715 may provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for connection state mobility in a service-based wireless system). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.

[0241] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of connection state mobility in a service-based wireless system as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0242] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, a discrete gate or transistor logic device, discrete hardware components, or any combination thereof, which are configured as a unit for performing the functions described in the present disclosure or otherwise supporting the unit. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

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

[0244] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, acquire, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, send information to the transmitter 715, or integrate in combination with the receiver 710, the transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0245] According to an example as disclosed herein, the communication manager 720 may support wireless communication at the UE. For example, the communication manager 720 may be configured to or otherwise support a unit for the following operations: transmitting a set of multiple service messages with a first DU, the set of multiple service messages being associated with a set of multiple core network services provided by a service-based network and active at the UE. The communication manager 720 may be configured to or otherwise support a unit for the following operations: receiving a measurement configuration from a core network mobility service in the set of multiple core network services and via the first DU, the measurement configuration indicating one or more trigger conditions associated with a handover process at the UE. The communication manager 720 may be configured to or otherwise support a unit for the following operations: sending a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition in one or more trigger conditions. The communication manager 720 may be configured to or otherwise support a unit for the following operations: receiving a handover command from the core network mobility service via the first DU based on satisfaction of the trigger condition, the handover command indicating a second DU supporting at least one core network service in the set of multiple core network services active at the UE. The communication manager 720 may be configured or otherwise support means for communicating with the second DU based on receiving the handover command.

[0246] By including or configuring the communication manager 720 according to the examples described herein, the device 705 (e.g., a processor controlling the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof or otherwise coupled thereto) can support techniques that enable the UE 115 to perform a handover procedure between DUs 165 and / or between network entities 105 in a service-based wireless system while minimizing interruption of active core network services at the UE 115. In particular, aspects of the present disclosure support techniques that enable the UE 115 to perform a handover procedure to a target DU / target network entity that supports at least some of the active core network services at the UE 115. Therefore, aspects of the present disclosure can reduce interruption of communications performed with core network services, thereby avoiding the need for the UE 115 to continuously reestablish communications with the core network services. In this regard, the techniques described herein can reduce signaling associated with the UE 115 subscribing to core network services, reduce interruptions, and improve the overall user experience.

[0247] Figure 8 A block diagram 800 of a device 805 supporting techniques for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0248] The receiver 810 may provide a unit for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies for connected state mobility in service-based wireless systems). The information may be delivered to other components of the device 805. The receiver 810 may utilize a single antenna or a group of multiple antennas.

[0249] The transmitter 815 may provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies for connection state mobility in service-based wireless systems). In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0250] The device 805 or its various components may be examples of units for performing various aspects of the technology for connection state mobility in a service-based wireless system as described herein. For example, the communication manager 820 may include a service message communication manager 825, a measurement configuration manager 830, a handover command reception manager 835, or any combination thereof. The communication manager 820 may be an example of various aspects of the communication manager 720 as described herein. In some examples, the communication manager 820 or its various components may be configured to perform various operations (e.g., receive, monitor, send) using the receiver 810, the transmitter 815, or both or in other ways in cooperation with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 may receive information from the receiver 810, send information to the transmitter 815, or integrate with the receiver 810, the transmitter 815, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0251] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. For example, the service message communication manager 825 may be configured to or otherwise support a unit for the following operations: transmitting a set of multiple service messages with a first DU, the set of multiple service messages being associated with a set of multiple core network services provided by a service-based network and active at the UE. The measurement configuration manager 830 may be configured to or otherwise support a unit for the following operations: receiving a measurement configuration from a core network mobility service in a set of multiple core network services and via the first DU, the measurement configuration indicating one or more trigger conditions associated with a handover process at the UE. The measurement configuration manager 830 may be configured to or otherwise support a unit for the following operations: sending a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition in one or more trigger conditions. The handover command reception manager 835 may be configured to or otherwise support a unit for the following operations: receiving a handover command from the core network mobility service via the first DU based on satisfaction of the trigger condition, the handover command indicating a second DU supporting at least one core network service in a set of multiple core network services active at the UE. The service message communication manager 825 may be configured or otherwise support means for communicating with the second DU based on receiving the handover command.

[0252] Fig. 9A block diagram 900 of a communication manager 920 supporting techniques for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The device 920 or its various components may be examples of units for performing various aspects of the techniques for connection state mobility in a service-based wireless system as described herein. For example, the communication manager 920 may include a service message communication manager 925, a measurement configuration manager 930, a handover command reception manager 935, a capability information manager 940, a service request transmission manager 945, a control signaling reception manager 950, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0253] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the service message communication manager 925 may be configured to or otherwise support a unit for the following operations: transmitting a set of multiple service messages with a first DU, the set of multiple service messages being associated with a set of multiple core network services provided by a service-based network and active at the UE. The measurement configuration manager 930 may be configured to or otherwise support a unit for the following operations: receiving a measurement configuration from a core network mobility service in a set of multiple core network services and via the first DU, the measurement configuration indicating one or more trigger conditions associated with a handover process at the UE. In some examples, the measurement configuration manager 930 may be configured to or otherwise support a unit for the following operations: sending a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition in one or more trigger conditions. The handover command reception manager 935 may be configured to or otherwise support a unit for the following operations: receiving a handover command from the core network mobility service via the first DU based on satisfaction of the trigger condition, the handover command indicating a second DU supporting at least one core network service in a set of multiple core network services active at the UE. In some examples, the service message communication manager 925 may be configured or otherwise support means for communicating with the second DU based on receiving the handover command.

[0254] In some examples, the capability information manager 940 can be configured as or otherwise support a unit for performing the following operations: sending capability information associated with the UE to a first DU, a core network mobility service, an additional core network service from a set of multiple core network services, or any combination thereof, wherein receiving a handover command is based on the capability information.

[0255] In some examples, the handover command receiving manager 935 can be configured as or otherwise support a unit for the following operations: receiving a cell identifier associated with a service cell supported by the second DU and a set of communication parameters for communicating with the service cell via a handover command, wherein the communication with the second DU is based on the cell identifier and the set of communication parameters.

[0256] In some examples, the service request sending manager 945 may be configured to or otherwise support a unit for the following operations: sending a service request for establishing a service with the core network mobility service to a network address associated with the core network mobility service. In some examples, the control signaling receiving manager 950 may be configured to or otherwise support a unit for the following operations: receiving control signaling indicating a service context for communicating with the core network mobility service based on the service request, wherein sending the second message, receiving the handover command, or both are based on the service context.

[0257] In some examples, the measurement configuration manager 930 can be configured as or otherwise support a unit for performing measurements on signals received from a first DU and one or more candidate DUs including a second DU, wherein the measurements are performed according to the measurement configuration, and wherein sending the second message is based on performing the measurements.

[0258] Fig.10 A schematic diagram of a system 1000 including a device 1005 supporting technology for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein or include components thereof. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

[0259] I / O controller 1010 can manage input and output signals for device 1005. I / O controller 1010 can also manage peripheral devices that are not integrated into device 1005. In some cases, I / O controller 1010 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 can utilize a computer such as a , or another known operating system. Additionally or alternatively, I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1010 may be implemented as part of a processor, such as processor 1040. In some cases, a user may interact with device 1005 via I / O controller 1010 or via hardware components controlled by I / O controller 1010.

[0260] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which can simultaneously send or receive multiple wireless transmissions. The transceiver 1015 can communicate bidirectionally via one or more antennas 1025, wired or wireless links as described herein. For example, the transceiver 1015 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1025 for transmission, and demodulating packets received from one or more antennas 1025. The transceiver 1015 or the transceiver 1015 and one or more antennas 1025 can be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or components thereof as described herein.

[0261] The memory 1030 may include a random access memory (RAM) or a read-only memory (ROM). The memory 1030 may store computer-readable, computer-executable code 1035, which includes instructions that, when executed by the processor 1040, cause the device 1005 to perform various functions described herein. The code 1035 may be stored in a non-transitory computer-readable medium (such as a system memory or another type of memory). In some cases, the code 1035 may not be directly executable by the processor 1040, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition to this, the memory 1030 may also contain a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0262] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a GPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some examples, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks that support technologies for connection state mobility in a service-based wireless system). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform various functions described herein.

[0263] According to an example as disclosed herein, the communication manager 1020 may support wireless communication at a UE. For example, the communication manager 1020 may be configured to or otherwise support a unit for the following operations: transmitting a set of multiple service messages with a first DU, the set of multiple service messages being associated with a set of multiple core network services provided by a service-based network and active at the UE. The communication manager 1020 may be configured to or otherwise support a unit for the following operations: receiving a measurement configuration from a core network mobility service in the set of multiple core network services and via the first DU, the measurement configuration indicating one or more trigger conditions associated with a handover process at the UE. The communication manager 1020 may be configured to or otherwise support a unit for the following operations: sending a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition in one or more trigger conditions. The communication manager 1020 may be configured to or otherwise support a unit for the following operations: receiving a handover command from the core network mobility service via the first DU based on satisfaction of the trigger condition, the handover command indicating a second DU supporting at least one core network service in the set of multiple core network services active at the UE. The communication manager 1020 may be configured or otherwise support means for communicating with the second DU based on receiving the handover command.

[0264] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 can support techniques that enable the UE 115 to perform a handover procedure between DUs 165 and / or between network entities 105 in a service-based wireless system while minimizing interruption of active core network services at the UE 115. In particular, aspects of the present disclosure support techniques that enable the UE 115 to perform a handover procedure to a target DU / target network entity that supports at least some of the active core network services at the UE 115. Therefore, aspects of the present disclosure can reduce interruption of communications performed with core network services, thereby avoiding the need for the UE 115 to continuously reestablish communications with the core network services. In this regard, the techniques described herein can reduce signaling associated with the UE 115 subscribing to core network services, reduce interruptions, and improve the overall user experience.

[0265] In some examples, the communication manager 1020 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 can be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 can include instructions executable by the processor 1040 to cause the device 1005 to perform various aspects of the techniques for using connected state mobility in a service-based wireless system as described herein, or the processor 1040 and the memory 1030 can be otherwise configured to perform or support such operations.

[0266] Fig.11 A block diagram 1100 of a device 1105 supporting techniques for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of a base station 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0267] The receiver 1110 may provide a unit 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 the device 1105. In some examples, the receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0268] The transmitter 1115 may provide a means for outputting (e.g., sending, providing, transmitting, sending) information generated by other components of the device 1105. For example, the transmitter 1115 may output 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). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0269] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of connection state mobility in a service-based wireless system as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0270] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which are configured as or otherwise support means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

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

[0272] In some examples, communication manager 1120 can be configured to perform various operations (e.g., receive, acquire, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 can receive information from receiver 1110, send information to transmitter 1115, or integrate in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0273] According to an example as disclosed herein, the communication manager 1120 may support wireless communications at a core network mobility service. For example, the communication manager 1120 may be configured to or otherwise support a unit for the following operations: receiving a message associated with the satisfaction of a trigger condition for a handover process at the UE from a first DU configured to wirelessly communicate with the UE. The communication manager 1120 may be configured to or otherwise support a unit for the following operations: based on the message, based on the second DU being configured to support at least one core network service active at the UE in a set of multiple core network services of a service-based network, the second DU is selected from a set of multiple candidate DUs. The communication manager 1120 may be configured to or otherwise support a unit for the following operations: based on selecting the second DU, a handover command is sent to the first DU for relaying to the UE, the handover command indicating the second DU and an instruction to perform a handover process from the first DU to the second DU.

[0274] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1120 may support wireless communication at the first DU. For example, the communication manager 1120 may be configured to or otherwise support a unit for the following operations: a set of multiple service messages is transmitted between the UE and a set of multiple core network services active at the UE of a service-based network. The communication manager 1120 may be configured to or otherwise support a unit for the following operations: a message associated with the satisfaction of a trigger condition for a handover process at the UE is sent to a core network mobility service in the set of multiple core network services. The communication manager 1120 may be configured to or otherwise support a unit for the following operations: a handover command indicating a second DU is received from the core network mobility service based on the message, and the second DU supports at least one core network service in the set of multiple core network services active at the UE. The communication manager 1120 may be configured to or otherwise support a unit for the following operations: a handover command is sent to the UE, and the handover command includes an instruction to the UE to perform a handover process from the first DU to the second DU.

[0275] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1120 may support wireless communication at the second DU. For example, the communication manager 1120 may be configured to or otherwise support a unit for the following operations: receiving a handover request associated with a handover process from a first DU to a second DU at a UE from a core network mobility service of a service-based network. The communication manager 1120 may be configured to or otherwise support a unit for the following operations: sending an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service active at the UE and supported by the second DU in a set of multiple core network services. The communication manager 1120 may be configured to or otherwise support a unit for the following operations: communicating with the UE based on the handover request and the ACK message. The communication manager 1120 may be configured to or otherwise support a unit for the following operations: sending a second message indicating the completion of the handover process to the core network mobility service based on communicating with the UE.

[0276] By including or configuring the communication manager 1120 according to the examples described herein, the device 1105 (e.g., a processor controlling the receiver 1110, the transmitter 1115, the communication manager 1120, or a combination thereof or otherwise coupled thereto) can support techniques that enable the UE 115 to perform a handover procedure between DUs 165 and / or between network entities 105 in a service-based wireless system while minimizing interruption of active core network services at the UE 115. In particular, aspects of the present disclosure support techniques that enable the UE 115 to perform a handover procedure to a target DU / target network entity that supports at least some of the active core network services at the UE 115. Therefore, aspects of the present disclosure can reduce interruption of communications performed with core network services, thereby avoiding the need for the UE 115 to continuously reestablish communications with the core network services. In this regard, the techniques described herein can reduce signaling associated with the UE 115 subscribing to core network services, reduce interruptions, and improve the overall user experience.

[0277] Fig.12 A block diagram 1200 of a device 1205 supporting techniques for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0278] The receiver 1210 may provide a means 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 transmitted to other components of the device 1205. In some examples, the receiver 1210 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0279] The transmitter 1215 may provide a means for outputting (e.g., sending, providing, transmitting, sending) information generated by other components of the device 1205. For example, the transmitter 1215 may output 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). In some examples, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0280] The device 1205 or its various components may be examples of units for performing various aspects of the technology for connection state mobility in a service-based wireless system as described herein. For example, the communication manager 1220 may include a handover process manager 1225, a target cell selection manager 1230, a handover command transmission manager 1235, a service message relay manager 1240, a handover command reception manager 1245, a handover request transmission manager 1250, a handover request reception manager 1255, an ACK message transmission manager 1260, a UE communication manager 1265, or any combination thereof. The communication manager 1220 may be an example of various aspects of the communication manager 1120 as described herein. In some examples, the communication manager 1220 or its various components may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 1210, the transmitter 1215, or both. For example, the communications manager 1220 may receive information from the receiver 1210, send information to the transmitter 1215, or integrate with the receiver 1210, the transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0281] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at a core network mobility service. The handover process manager 1225 may be configured as or otherwise support a unit for the following operations: receiving a message associated with the satisfaction of a trigger condition for a handover process at the UE from a first DU configured to wirelessly communicate with the UE. The target cell selection manager 1230 may be configured as or otherwise support a unit for the following operations: based on the message, based on the second DU being configured to support at least one core network service active at the UE in a set of multiple core network services of a service-based network, the second DU is selected from a set of multiple candidate DUs. The handover command sending manager 1235 may be configured as or otherwise support a unit for the following operations: based on selecting the second DU, sending a handover command to the first DU for relaying to the UE, the handover command indicating the second DU and instructions for performing a handover process from the first DU to the second DU.

[0282] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1220 may support wireless communication at the first DU. The service message relay manager 1240 may be configured as or otherwise support a unit for the following operations: transmitting a set of multiple service messages between the UE and a set of multiple core network services active at the UE based on the service network. The handover process manager 1225 may be configured as or otherwise support a unit for the following operations: sending a message associated with the satisfaction of a trigger condition for a handover process at the UE to a core network mobility service in the set of multiple core network services. The handover command reception manager 1245 may be configured as or otherwise support a unit for the following operations: receiving a handover command indicating a second DU from the core network mobility service based on the message, the second DU supporting at least one core network service in the set of multiple core network services active at the UE. The handover request transmission manager 1250 may be configured as or otherwise support a unit for the following operations: sending a handover command to the UE, the handover command including an instruction to the UE to perform a handover process from the first DU to the second DU.

[0283] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1220 may support wireless communication at the second DU. The handover request reception manager 1255 may be configured to or otherwise support a unit for the following operations: receiving a handover request associated with a handover process from the first DU to the second DU at the UE from a core network mobility service of a service-based network. The ACK message sending manager 1260 may be configured to or otherwise support a unit for the following operations: sending an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service active at the UE and supported by the second DU in a set of multiple core network services. The UE communication manager 1265 may be configured to or otherwise support a unit for the following operations: communicating with the UE based on the handover request and the ACK message. The handover process manager 1225 may be configured to or otherwise support a unit for the following operations: sending a second message indicating the completion of the handover process to the core network mobility service based on communicating with the UE.

[0284] Fig.13A block diagram 1300 of a communication manager 1320 supporting a technology for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of units for performing various aspects of the technology for connection state mobility in a service-based wireless system as described herein. For example, the communication manager 1320 may include a handover process manager 1325, a target cell selection manager 1330, a handover command transmission manager 1335, a service message relay manager 1340, a handover instruction reception manager 1345, a handover request transmission manager 1350, a handover request reception manager 1355, an ACK message transmission manager 1360, a UE communication manager 1365, an ACK message reception manager 1370, a capability information reception manager 1375, a capability information transmission manager 1380, a communication tunnel manager 1385, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0285] According to the examples disclosed herein, the communication manager 1320 may support wireless communications at a core network mobility service. The handover process manager 1325 may be configured to or otherwise support a unit for the following operations: receiving a message associated with the satisfaction of a trigger condition for a handover process at the UE from a first DU configured to wirelessly communicate with the UE. The target cell selection manager 1330 may be configured to or otherwise support a unit for the following operations: based on the message, based on the second DU being configured to support at least one core network service active at the UE in a set of multiple core network services of a service-based network, the second DU is selected from a set of multiple candidate DUs. The handover command sending manager 1335 may be configured to or otherwise support a unit for the following operations: based on selecting the second DU, sending a handover command to the first DU for relaying to the UE, the handover command indicating the second DU and instructions for performing a handover process from the first DU to the second DU.

[0286] In some examples, the handover request sending manager 1350 can be configured or otherwise support a unit for the following operations: sending a handover request to the second DU based on the message. In some examples, the ACK message receiving manager 1370 can be configured or otherwise support a unit for the following operations: receiving an ACK message from the second DU based on the handover request, wherein sending the handover command is based on the ACK message.

[0287] In some examples, the handover command sending manager 1335 can be configured as or otherwise support a unit for performing the following operations: sending an indication of a set of multiple core network services active at the UE via a handover request, wherein the ACK message is based on the set of multiple core network services active at the UE.

[0288] In some examples, the ACK message reception manager 1370 can be configured as or otherwise support a unit for performing the following operations: receiving an indication of at least one core network service supported by the second DU via an ACK message, wherein sending the switching command is based on receiving the indication of the at least one core network service.

[0289] In some examples, capability information reception manager 1375 may be configured or otherwise support means for receiving capability information associated with the UE, wherein selecting a second DU from a set of multiple candidate DUs is based on the capability information.

[0290] In some examples, the capability information is received from a core network capability service included within a set of multiple core network services.

[0291] In some examples, selecting the second DU from the set of multiple candidate DUs is based on the UE's mobility history, the traffic load associated with the second DU, or both.

[0292] In some examples, the handover process manager 1325 may be configured as or otherwise support means for receiving an indication of a set of multiple candidate DUs via the message, wherein selecting the second DU is based on receiving the indication of the set of multiple candidate DUs.

[0293] In some examples, to support selection of the second DU, the target cell selection manager 1330 may be configured or otherwise support means for selecting a serving cell supported by the second DU, wherein the handover command includes a cell identifier associated with the selected serving cell.

[0294] In some examples, the handover process manager 1325 may be configured or otherwise support means for: receiving a second message from the second DU indicating completion of the handover process. In some examples, the UE communication manager 1365 may be configured or otherwise support means for: communicating with the UE via the second DU based on the second message.

[0295] In some examples, the handover process manager 1325 can be configured as or otherwise support a unit for performing the following operations: sending a measurement configuration to the first DU for relaying to the UE, the measurement configuration indicating one or more trigger conditions including the trigger conditions, wherein the received message is based on the measurement configuration.

[0296] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1320 may support wireless communication at the first DU. The service message relay manager 1340 may be configured to or otherwise support a unit for the following operations: transmitting a set of multiple service messages between the UE and a set of multiple core network services active at the UE based on the service network. In some examples, the handover process manager 1325 may be configured to or otherwise support a unit for the following operations: sending a message associated with the satisfaction of a trigger condition for a handover process at the UE to a core network mobility service in the set of multiple core network services. The handover command reception manager 1345 may be configured to or otherwise support a unit for the following operations: receiving a handover command indicating a second DU from the core network mobility service based on the message, the second DU supporting at least one core network service in the set of multiple core network services active at the UE. The handover request transmission manager 1350 may be configured to or otherwise support a unit for the following operations: sending a handover command to the UE, the handover command including an instruction to the UE to perform a handover process from the first DU to the second DU.

[0297] In some examples, the capability information sending manager 1380 can be configured as or otherwise support a unit for performing the following operations: sending capability information associated with the UE to a core network mobility service, an additional core network service in a set of multiple core network services, or both, wherein receiving a handover command is based on the capability information.

[0298] In some examples, the handover process manager 1325 can be configured as or otherwise support a unit for performing the following operations: sending an indication of a set of multiple core network services that can be active at the UE to a core network mobility service, an additional core network service in the set of multiple core network services, or both, wherein receiving the handover command is based on sending the indication of the set of multiple core network services that can be active at the UE.

[0299] In some examples, the communication tunnel manager 1385 may be configured or otherwise support means for establishing a communication tunnel with the second DU based on the handover command. In some examples, the service message relay manager 1340 may be configured or otherwise support means for receiving a second message for the UE before the handover process is completed. In some examples, the service message relay manager 1340 may be configured or otherwise support means for sending one or more packets to the second DU via the communication tunnel for relaying to the UE based on receiving the second message.

[0300] In some examples, the switching process manager 1325 can be configured as or otherwise support a unit for performing the following operations: sending, via the message, an indication of a set of multiple candidate DUs including a second DU and one or more cell identifiers associated with one or more service cells supported by the second DU, wherein receiving the switching command is based on sending the indication of the set of multiple candidate DUs.

[0301] In some examples, the handover command receiving manager 1345 may be configured as or otherwise support a unit for the following operations: receiving an indication of at least one core network service supported by the second DU via a handover command. In some examples, the handover command sending manager 1335 may be configured as or otherwise support a unit for the following operations: sending an indication of at least one core network service supported by the second DU to the UE via a handover command.

[0302] In some examples, the handover process manager 1325 may be configured as or otherwise support means for: receiving, from a core network mobility service, a measurement configuration indicating one or more trigger conditions including the trigger condition. In some examples, the handover process manager 1325 may be configured as or otherwise support means for: sending the measurement configuration to the UE, wherein sending the message associated with the satisfaction of the trigger state may be based on the measurement configuration.

[0303] In some examples, the switching process manager 1325 can be configured as or otherwise support a unit for performing the following operations: receiving a measurement report, a second message indicating a trigger condition, or both from the UE based on the measurement configuration, wherein sending a message associated with satisfaction of the trigger state is based on receiving the measurement report, the second message indicating the trigger condition, or both.

[0304] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1320 may support wireless communication at the second DU. The handover request reception manager 1355 may be configured to or otherwise support a unit for the following operations: receiving a handover request associated with a handover process from a first DU to a second DU at a UE from a core network mobility service of a service-based network. The ACK message sending manager 1360 may be configured to or otherwise support a unit for the following operations: sending an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service active at the UE and supported by the second DU in a set of multiple core network services. The UE communication manager 1365 may be configured to or otherwise support a unit for the following operations: communicating with the UE based on the handover request and the ACK message. In some examples, the handover process manager 1325 may be configured to or otherwise support a unit for the following operations: sending a second message indicating the completion of the handover process to the core network mobility service based on communicating with the UE.

[0305] In some examples, the handover request receiving manager 1355 can be configured as or otherwise support a unit for performing the following operations: receiving an indication of a set of multiple core network services active at the UE via a handover request, wherein sending an ACK message is based on the set of multiple core network services active at the UE.

[0306] In some examples, the communication tunnel manager 1385 may be configured or otherwise support a unit for the following operations: establish a communication tunnel with the first DU based on the handover request, the ACK message, or both. In some examples, the service message relay manager 1340 may be configured or otherwise support a unit for the following operations: receive one or more data packets associated with the second message for the UE from the first DU via the communication tunnel before the handover process is completed. In some examples, the service message relay manager 1340 may be configured or otherwise support a unit for the following operations: based on receiving the one or more data packets via the communication tunnel, send one or more data packets associated with the second message to the UE.

[0307] In some examples, the ACK message sending manager 1360 can be configured as or otherwise support a unit for the following operations: sending a communication parameter set for communication between the UE and the second DU to the core network mobility service via an ACK message, wherein communication with the UE is based on the communication parameter set.

[0308] Fig.14A schematic diagram of a system 1400 including a device 1405 supporting technologies for connection state mobility in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 as described herein or include components thereof. The device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1405 may include components that support output and acquisition of communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

[0309] The transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415, which may be able to (e.g., concurrently) send or receive wireless transmissions. The transceiver 1410 may also include a modem to modulate a signal to provide a modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter), receive a modulated signal (e.g., from one or more antennas 1415, from a wired receiver), and demodulate a signal. In some implementations, the transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receiving or acquiring operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1410 may include or be configured to be coupled to one or more 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 implementations, the transceiver 1410, or the transceiver 1410 and one or more antennas 1415, or the transceiver 1410 and one or more antennas 1415 and one or more processors or memory components (e.g., processor 1435, or memory 1425, or both) may be included in a chip or chip component installed in the device 1405. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link, fronthaul communication link 168).

[0310] Memory 1425 may include RAM and ROM. Memory 1425 may store computer-readable, computer-executable code 1430, which includes instructions that, when executed by processor 1435, cause device 1405 to perform various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, code 1430 may not be directly executable by processor 1435, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition to this, memory 1425 may also contain BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0311] Processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some examples, processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to cause device 1405 to perform various functions (e.g., functions or tasks that support technologies for connection state mobility in a service-based wireless system). For example, device 1405 or a component of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435, and processor 1435 and memory 1425 are configured to perform various functions described herein. Processor 1435 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software, such as an operating system, a virtual machine, or a container instance), which can host functions (e.g., by executing code 1430) to perform functions of device 1405. Processor 1435 can be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (e.g., in memory 1425). In some implementations, processor 1435 can be a component of a processing system. A processing system can generally refer to a system or a series of machines or components that receive inputs and process the inputs to produce an output set (which can be passed to other systems or components of, for example, device 1405). For example, a processing system of device 1405 can refer to a system including various other components or subcomponents of device 1405, such as a processor 1435, or a transceiver 1410, or a communication manager 1420, or a combination of other components or components of device 1405. The processing system of device 1405 can be docked with other components of device 1405, and can process information (such as input or signal) received from other components, and output the information to other components. For example, the chip or modem of device 1405 may include a processing system and one or more interfaces for outputting information, or obtaining information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or configured to input information and obtain the same interface of information, as well as other implementations. In some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, so that device 1405 can send information output from the chip or modem.Additionally or alternatively, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1405 can receive information or signal input and can pass information to the processing system. A person of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0312] In some examples, bus 1440 may support communications within a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1440 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1405, or communications performed between different components of device 1405, which may be co-located or located in different locations (e.g., where device 1405 may refer to a system in which one or more communication managers 1420, transceivers 1410, memory 1425, code 1430, and processor 1435 may be located in one of different components or divided into different components).

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

[0314] According to an example as disclosed herein, the communication manager 1420 may support wireless communications at a core network mobility service. For example, the communication manager 1420 may be configured to or otherwise support a unit for the following operations: receiving a message associated with the satisfaction of a trigger condition for a handover process at the UE from a first DU configured to wirelessly communicate with the UE. The communication manager 1420 may be configured to or otherwise support a unit for the following operations: based on the message, based on the second DU being configured to support at least one core network service active at the UE in a set of multiple core network services of a service-based network, the second DU is selected from a set of multiple candidate DUs. The communication manager 1420 may be configured to or otherwise support a unit for the following operations: based on selecting the second DU, a handover command is sent to the first DU for relaying to the UE, the handover command indicating the second DU and an instruction to perform a handover process from the first DU to the second DU.

[0315] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1420 may support wireless communication at the first DU. For example, the communication manager 1420 may be configured to or otherwise support a unit for the following operations: a set of multiple service messages is transmitted between the UE and a set of multiple core network services active at the UE of a service-based network. The communication manager 1420 may be configured to or otherwise support a unit for the following operations: a message associated with the satisfaction of a trigger condition for a handover process at the UE is sent to a core network mobility service in the set of multiple core network services. The communication manager 1420 may be configured to or otherwise support a unit for the following operations: a handover command indicating a second DU is received from the core network mobility service based on the message, and the second DU supports at least one core network service in the set of multiple core network services active at the UE. The communication manager 1420 may be configured to or otherwise support a unit for the following operations: a handover command is sent to the UE, and the handover command includes an instruction to the UE to perform a handover process from the first DU to the second DU.

[0316] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1420 may support wireless communication at the second DU. For example, the communication manager 1420 may be configured to or otherwise support a unit for the following operations: receiving a handover request associated with a handover process from a first DU to a second DU at a UE from a core network mobility service of a service-based network. The communication manager 1420 may be configured to or otherwise support a unit for the following operations: sending an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service active at the UE and supported by the second DU in a set of multiple core network services. The communication manager 1420 may be configured to or otherwise support a unit for the following operations: communicating with the UE based on the handover request and the ACK message. The communication manager 1420 may be configured to or otherwise support a unit for the following operations: sending a second message indicating the completion of the handover process to the core network mobility service based on communicating with the UE.

[0317] By including or configuring the communication manager 1420 according to the examples described herein, the device 1405 can support techniques that enable the UE 115 to perform a handover procedure between DUs 165 and / or between network entities 105 in a service-based wireless system while minimizing interruption of active core network services at the UE 115. In particular, aspects of the present disclosure support techniques that enable the UE 115 to perform a handover procedure to a target DU / target network entity that supports at least some of the active core network services at the UE 115. Therefore, aspects of the present disclosure can reduce interruption of communications performed with core network services, thereby avoiding the need for the UE 115 to continuously reestablish communications with the core network services. In this regard, the techniques described herein can reduce signaling associated with a UE 115 subscribing to core network services, reduce interruptions, and improve the overall user experience.

[0318] In some examples, the communication manager 1420 may be configured to perform (where applicable) various operations (e.g., receive, acquire, monitor, output, transmit) using or otherwise in cooperation with the transceiver 1410, one or more antennas 1415, or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, the processor 1435, the memory 1425, the code 1430, or any combination thereof. For example, the code 1430 may include instructions executable by the processor 1435 to cause the device 1405 to perform various aspects of the techniques for using connected state mobility in a service-based wireless system as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0319] Fig.15 A flow chart illustrating a method 1500 for supporting connection state mobility for a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described functions may be performed by the UE 115. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0320] At 1505, the method may include: transmitting a set of multiple service messages with the first DU, the set of multiple service messages being associated with a set of multiple core network services provided by the service-based network and active at the UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described with reference to Fig. 9 The described service message communication manager 925 is executed.

[0321] At 1510, the method may include: receiving a measurement configuration from a core network mobility service in a set of multiple core network services and via a first DU, the measurement configuration indicating one or more trigger conditions associated with a handover process at the UE. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described with reference to Fig. 9 The measurement configuration manager 930 described above is executed.

[0322] At 1515, the method may include: sending a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition in one or more trigger conditions. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Fig. 9 The measurement configuration manager 930 described above is executed.

[0323] At 1520, the method may include: receiving a handover command from a core network mobility service via a first DU based on satisfaction of a trigger condition, the handover command indicating a second DU supporting at least one core network service from a set of multiple core network services active at the UE. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described with reference to Fig. 9 The described switching command is received by the manager 935 for execution.

[0324] At 1525, the method may include: communicating with the second DU based on receiving the handover instruction. The operations of 1525 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described with reference to Fig. 9 The described service message communication manager 925 is executed.

[0325] Fig.16 A flow chart illustrating a method 1600 for supporting connection state mobility for a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 6 11 to 14 are performed by the network entity described. In some examples, the network entity can execute an instruction set to control the functional units of the network entity to perform the described functions. Additionally or alternatively, the network entity can use dedicated hardware to perform various aspects of the described functions.

[0326] At 1605, the method may include: receiving a message associated with satisfaction of a trigger condition for a handover procedure at the UE from a first DU configured to wirelessly communicate with the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described with reference to Fig.13 The described switching process manager 1325 is executed.

[0327] At 1610, the method may include: based on the message, selecting a second DU from a set of multiple candidate DUs based on the second DU being configured to support at least one core network service active at the UE in a set of multiple core network services of a service-based network. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Fig.13 The target cell selection manager 1330 described above is executed.

[0328] At 1615, the method may include: based on selecting the second DU, sending a handover command to the first DU for relaying to the UE, the handover command indicating the second DU and instructions for performing a handover process from the first DU to the second DU. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described with reference to Fig.13 The described switching command is sent to manager 1335 for execution.

[0329] Fig.17 A flow chart illustrating a method 1700 for supporting connection state mobility for a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 6 11 to 14 are performed by the network entity described. In some examples, the network entity can execute an instruction set to control the functional units of the network entity to perform the described functions. Additionally or alternatively, the network entity can use dedicated hardware to perform various aspects of the described functions.

[0330] At 1705, the method may include transmitting a set of multiple service messages between the UE and a set of multiple core network services active at the UE of the service-based network. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Fig.13 The described service message relay manager 1340 is executed.

[0331] At 1710, the method may include sending a message associated with satisfaction of a trigger condition for a handover procedure at the UE to a core network mobility service in a set of multiple core network services. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Fig.13 The described switching process manager 1325 is executed.

[0332] At 1715, the method may include: receiving a handover command from a core network mobility service indicating a second DU based on the message, the second DU supporting at least one core network service from a set of multiple core network services active at the UE. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Fig.13 The described switching command is received by the manager 1345 for execution.

[0333] At 1720, the method may include: sending a handover command to the UE, the handover command including an instruction to perform a handover procedure from the first DU to the second DU on the UE. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed by a handover request sending manager 1350 as described in reference 13.

[0334] Fig.18 A flow chart illustrating a method 1800 for supporting connection state mobility for a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 6 11 to 14 are performed by the network entity described. In some examples, the network entity can execute an instruction set to control the functional units of the network entity to perform the described functions. Additionally or alternatively, the network entity can use dedicated hardware to perform various aspects of the described functions.

[0335] At 1805, the method may include: receiving, from a core network mobility service of a service-based network, a handover request associated with a handover procedure from a first DU to a second DU at a UE. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described with reference to Fig.13 The described switching request reception manager 1355 is executed.

[0336] At 1810, the method may include: sending an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service in the set of multiple core network services that is active at the UE and supported by the second DU. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described with reference to Fig.13 The ACK message described is sent by manager 1360 to perform.

[0337] At 1815, the method may include: communicating with the UE based on the handover request and the ACK message. The operations of 1815 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Fig.13 The described UE communication manager 1365 is executed.

[0338] At 1820, the method may include: sending a second message to the core network mobility service indicating completion of the handover process based on communicating with the UE. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Fig.13 The described switching process manager 1325 is executed.

[0339] The following provides an overview of some aspects of the disclosure:

[0340] Aspect 1: A method for wireless communication at a UE, comprising: transmitting multiple service messages with a first DU, the multiple service messages being associated with multiple core network services provided by a service-based network and active at the UE; receiving a measurement configuration from a core network mobility service among the multiple core network services and via the first DU, the measurement configuration indicating one or more trigger conditions associated with a switching process at the UE; sending a second message to the first DU for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition among the one or more trigger conditions; receiving a switching command from the core network mobility service via the first DU based at least in part on the satisfaction of the trigger condition, the switching command indicating a second DU supporting at least one core network service among the multiple core network services active at the UE; and communicating with the second DU based at least in part on receiving the switching command.

[0341] Aspect 2: The method of Aspect 1 further includes: sending capability information associated with the UE to the first DU, the core network mobility service, an additional core network service among the multiple core network services, or any combination thereof, wherein receiving the switching command is at least partially based on the capability information.

[0342] Aspect 3: The method of any one of Aspects 1 to 2 further includes: receiving, via the switching command, a cell identifier associated with a service cell supported by the second DU and a set of communication parameters for communicating with the service cell, wherein the communication with the second DU is at least partially based on the cell identifier and the set of communication parameters.

[0343] Aspect 4: The method of any one of Aspects 1 to 3 further includes: sending a service request for establishing a service with the core network mobility service to a network address associated with the core network mobility service; and, based at least in part on the service request, receiving control signaling indicating a service context for communicating with the core network mobility service, wherein sending the second message, receiving the switching command, or both is based at least in part on the service context.

[0344] Aspect 5: The method of any one of Aspects 1 to 4 further includes: performing measurements on signals received from the first DU and one or more candidate DUs including the second DU, wherein the measurements are performed according to the measurement configuration, and wherein sending the second message is at least partially based on performing the measurements.

[0345] Aspect 6: A method for wireless communication at a core network mobility service, comprising: receiving a message associated with the satisfaction of a trigger condition for a switching process at a UE from a first DU in wireless communication with the UE; selecting the second DU from a plurality of candidate DUs based at least in part on the message and at least in part on the second DU being configured to support at least one core network service active at the UE among a plurality of core network services of a service-based network; and, based at least in part on the selection of the second DU, sending a switching command to the first DU for relaying to the UE, the switching command indicating the second DU and instructions for performing a switching process from the first DU to the second DU.

[0346] Aspect 7: The method of Aspect 6 further includes: sending a switching request to the second DU based at least in part on the message; and receiving an ACK message from the second DU based at least in part on the switching request, wherein sending the switching command is based at least in part on the ACK message.

[0347] Aspect 8: The method of Aspect 7 further comprises: sending an indication of the multiple core network services active at the UE via the handover request, wherein the ACK message is at least partially based on the multiple core network services active at the UE.

[0348] Aspect 9: The method of any one of Aspects 7 to 8 further includes: receiving an indication of the at least one core network service supported by the second DU via the ACK message, wherein sending the switching command is at least partially based on receiving the indication of the at least one core network service.

[0349] Aspect 10: The method of any one of Aspects 6 to 9, further comprising: receiving capability information associated with the UE, wherein selecting the second DU from the plurality of candidate DUs is based at least in part on the capability information.

[0350] Aspect 11: The method of Aspect 10, wherein the capability information is received from a core network capability service included in the plurality of core network services.

[0351] Aspect 12: The method of any one of Aspects 6 to 11, wherein selecting the second DU from the plurality of candidate DUs is based at least in part on a mobility history of the UE, a traffic load associated with the second DU, or both.

[0352] Aspect 13: The method of any one of Aspects 6 to 12, further comprising: receiving an indication of the plurality of candidate DUs via the message, wherein selecting the second DU is based at least in part on receiving the indication of the plurality of candidate DUs.

[0353] Aspect 14: The method of any one of Aspects 6 to 13, wherein selecting the second DU further comprises: selecting a serving cell supported by the second DU, wherein the handover command comprises a cell identifier associated with the selected serving cell.

[0354] Aspect 15: The method of any one of Aspects 6 to 14, further comprising: receiving a second message from the second DU indicating that the switching process is completed; and, communicating with the UE via the second DU at least in part based on the second message.

[0355] Aspect 16: The method of any one of Aspects 6 to 15 further includes: sending a measurement configuration to the first DU for relaying to the UE, the measurement configuration indicating one or more trigger conditions including the trigger condition, wherein receiving the message is at least partially based on the measurement configuration.

[0356] Aspect 17: A method for wireless communication at a first DU, comprising: transmitting multiple service messages between a UE and multiple core network services active at the UE based on a service network; sending a message associated with the satisfaction of a trigger condition for a switching process at the UE to a core network mobility service among the multiple core network services; receiving a switching command indicating a second DU from the core network mobility service based at least in part on the message, the second DU supporting at least one core network service among the multiple core network services active at the UE; and sending the switching command to the UE, the switching command including an instruction to the UE to perform a switching process from the first DU to the second DU.

[0357] Aspect 18: The method of Aspect 17 further includes: sending capability information associated with the UE to the core network mobility service, an additional core network service among the multiple core network services, or both, wherein receiving the switching command is at least partially based on the capability information.

[0358] Aspect 19: The method of any one of Aspects 17 to 18 further comprises: sending an indication of the multiple core network services active at the UE to the core network mobility service, an additional core network service among the multiple core network services, or both, wherein receiving the switching command is at least partially based on sending the indication of the multiple core network services active at the UE.

[0359] Aspect 20: The method of any one of Aspects 17 to 19 further includes: establishing a communication tunnel with the second DU based at least in part on the switching command; receiving a second message for the UE before the switching process is completed; and, based at least in part on receiving the second message, sending one or more packets to the second DU via the communication tunnel for relaying to the UE.

[0360] Aspect 21: The method of any one of Aspects 17 to 20 further includes: sending, via the message, an indication of multiple candidate DUs including the second DU and one or more cell identifiers associated with one or more service cells supported by the second DU, wherein receiving the switching command is at least partially based on sending the indication of the multiple candidate DUs.

[0361] Aspect 22: The method of any one of Aspects 17 to 21 further includes: receiving an indication of the at least one core network service supported by the second DU via the switching command; and sending the indication of the at least one core network service supported by the second DU to the UE via the switching command.

[0362] Aspect 23: The method of any one of Aspects 17 to 22 further includes: receiving a measurement configuration indicating one or more trigger conditions including the trigger condition from the core network mobility service; and sending the measurement configuration to the UE, wherein sending the message associated with the satisfaction of the trigger state is at least partially based on the measurement configuration.

[0363] Aspect 24: The method of Aspect 23 further includes: receiving a measurement report, a second message indicating the trigger condition, or both from the UE based at least in part on the measurement configuration, wherein sending the message associated with the satisfaction of the trigger state is based at least in part on receiving the measurement report, the second message indicating the trigger condition, or both.

[0364] Aspect 25: A method for wireless communication at a second DU, comprising: receiving a switching request associated with a switching process from a first DU to the second DU at a UE from a core network mobility service of a service-based network; sending an ACK message to the core network mobility service based at least in part on the switching request, the ACK message indicating at least one core network service among a plurality of core network services that is active at the UE and supported by the second DU; communicating with the UE based at least in part on the switching request and the ACK message; and, based at least in part on communicating with the UE, sending a second message to the core network mobility service indicating completion of the switching process.

[0365] Aspect 26: The method of Aspect 25 further includes: receiving an indication of the multiple core network services active at the UE via the handover request, wherein sending the ACK message is at least partially based on the multiple core network services active at the UE.

[0366] Aspect 27: The method of any one of Aspects 25 to 26 further includes: establishing a communication tunnel with the first DU based at least in part on the switching request, the ACK message, or both; receiving one or more data packets associated with a second message for the UE from the first DU via the communication tunnel before the switching process is completed; and, based at least in part on receiving the one or more data packets via the communication tunnel, sending the one or more data packets associated with the second message to the UE.

[0367] Aspect 28: The method of any one of Aspects 25 to 27 further includes: sending a communication parameter set for communication between the UE and the second DU to the core network mobility service via the ACK message, wherein communication with the UE is at least partially based on the communication parameter set.

[0368] Aspect 29: An apparatus for performing wireless communications at a UE, comprising: a processor; a memory coupled to the processor; and instructions, the instructions being stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of Aspects 1 to 5.

[0369] Aspect 30: An apparatus for wireless communication at a UE, comprising at least one unit for performing the method of any one of aspects 1 to 5.

[0370] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method of any one of aspects 1 to 5.

[0371] Aspect 32: An apparatus for wireless communication at a core network mobility service, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of Aspects 6 to 16.

[0372] Aspect 33: An apparatus for wireless communication at a core network mobility service, comprising at least one unit for performing the method of any one of aspects 6 to 16.

[0373] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a core network mobility service, the code comprising instructions executable by a processor to perform the method of any one of aspects 6 to 16.

[0374] Aspect 35: An apparatus for wireless communication at a first DU, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of Aspects 17 to 24.

[0375] Aspect 36: An apparatus for wireless communication at a first DU, comprising at least one unit for performing the method of any one of aspects 17 to 24.

[0376] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication at a first DU, the code comprising instructions executable by a processor to perform the method of any one of aspects 17 to 24.

[0377] Aspect 38: An apparatus for wireless communication at a second DU, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of Aspects 25 to 28.

[0378] Aspect 39: An apparatus for wireless communication at a second DU, comprising at least one unit for performing the method of any one of Aspects 25 to 28.

[0379] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication at a second DU, the code comprising instructions executable by a processor to perform the method of any one of aspects 25 to 28.

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

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

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

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

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

[0385] Computer readable medium includes non-temporary computer storage medium and communication medium, wherein communication medium includes any medium that is convenient to transmit computer program from one position to another position.Non-temporary storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-temporary computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used for carrying or storing desired program code unit in the form of instruction or data structure and can be accessed by general or special-purpose computer or general or special-purpose processor any other non-temporary medium.In addition, any connection is appropriately referred to as computer readable medium.For example, if software is to send from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can copy data magnetically, while optical disks use lasers to copy data optically. Combinations of the above are also included within the scope of computer-readable media.

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

[0387] The term "determine" or "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, querying (e.g., querying in a table, database, or other data structure), ascertaining, etc. In addition, "determining" may also include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. In addition, "determining" may also include solving, obtaining, selecting, choosing, establishing, and other similar actions.

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

[0389] The description set forth herein in conjunction with the accompanying drawings describes exemplary configurations and does not represent all examples that can be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." For the purpose of providing an understanding of the described techniques, the detailed description includes specific details. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

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

Claims

1. A method for wireless communication at a user equipment (UE), comprising: communicating with a first distributed unit a plurality of service messages associated with a plurality of core network services provided by a service-based network and active at the UE; receiving, from a core network mobility service of the plurality of core network services and via the first distributed unit, a measurement configuration indicating one or more triggering conditions associated with a handover procedure at the UE; sending a second message to the first distributed unit for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition of the one or more trigger conditions; receiving, based at least in part on the satisfaction of the trigger condition, a handover command from the core network mobility service via the first distributed unit, the handover command instructing a second distributed unit supporting at least one core network service of the plurality of core network services active at the UE; as well as Communicating with the second distributed unit based at least in part on receiving the switch command.

2. The method according to claim 1, further comprising: Sending capability information associated with the UE to the first distributed unit, the core network mobility service, an additional core network service among the plurality of core network services, or any combination thereof, wherein receiving the handover command is based at least in part on the capability information.

3. The method according to claim 1, further comprising: A cell identifier associated with a serving cell supported by the second distributed unit and a set of communication parameters for communicating with the serving cell are received via the handover command, wherein communicating with the second distributed unit is based at least in part on the cell identifier and the set of communication parameters.

4. The method according to claim 1, further comprising: sending a service request for establishing service with the core network mobility service to a network address associated with the core network mobility service; as well as Based at least in part on the service request, control signaling is received indicating a service context for communicating with the core network mobility service, wherein sending the second message, receiving the handover command, or both is based at least in part on the service context.

5. The method according to claim 1, further comprising: Performing measurements on signals received from the first distributed unit and one or more candidate distributed units including the second distributed unit, wherein the measurements are performed according to the measurement configuration, and wherein sending the second message is based at least in part on performing the measurements.

6. A method for wireless communication at a core network mobility service, comprising: receiving, from a first distributed unit configured to wirelessly communicate with a user equipment (UE), a message associated with satisfaction of a triggering condition for a handover procedure at the UE; selecting the second distributed unit from a plurality of candidate distributed units based at least in part on the message and at least in part on the second distributed unit being configured to support at least one core network service of a plurality of core network services of a service-based network that is active at the UE; as well as Based at least in part on selecting the second distributed unit, a handover command is sent to the first distributed unit for relaying to the UE, the handover command indicating the second distributed unit and instructions to perform a handover procedure from the first distributed unit to the second distributed unit.

7. The method according to claim 6, further comprising: Based at least in part on the message, sending a handover request to the second distributed unit; as well as Based at least in part on the handover request, receiving a confirmation message from the second distributed unit, wherein sending the handover command is based at least in part on the confirmation message.

8. The method according to claim 7, further comprising: An indication of the plurality of core network services active at the UE is sent via the handover request, wherein the confirmation message is based at least in part on the plurality of core network services active at the UE.

9. The method according to claim 7, further comprising: An indication of the at least one core network service supported by the second distributed unit is received via the confirmation message, wherein sending the handover command is based at least in part on receiving the indication of the at least one core network service.

10. The method according to claim 6, further comprising: Capability information associated with the UE is received, wherein selecting the second distributed unit from the plurality of candidate distributed units is based at least in part on the capability information.

11. The method according to claim 10, wherein: The capability information is received from a core network capability service included within the plurality of core network services.

12. The method according to claim 6, wherein: Selecting the second distributed unit from the plurality of candidate distributed units is based at least in part on a mobility history of the UE, a traffic load associated with the second distributed unit, or both.

13. The method according to claim 6, further comprising: An indication of the plurality of candidate distributed units is received via the message, wherein selecting the second distributed unit is based at least in part on receiving the indication of the plurality of candidate distributed units.

14. The method according to claim 6, wherein: Selecting the second distributed unit includes: A serving cell supported by the second distributed unit is selected, wherein the handover command includes a cell identifier associated with the selected serving cell.

15. The method according to claim 6, further comprising: receiving, from the second distributed unit, a second message indicating completion of the handover process; as well as Based at least in part on the second message, communicating with the UE via the second distributed unit.

16. The method according to claim 6, further comprising: A measurement configuration is sent to the first distributed unit for relaying to the UE, the measurement configuration indicating one or more trigger conditions including the trigger condition, wherein receiving the message is based at least in part on the measurement configuration.

17. A method for wireless communication at a first distributed unit, comprising: transmitting a plurality of service messages between a user equipment (UE) and a plurality of core network services of a service-based network active at the UE; sending, to a core network mobility service of the plurality of core network services, a message associated with satisfaction of a triggering condition for a handover procedure at the UE; receiving, based at least in part on the message, from the core network mobility service a handover command indicative of a second distributed unit supporting at least one core network service of a plurality of core network services active at the UE; as well as The handover command is sent to the UE, where the handover command includes an instruction to execute a handover process from the first distributed unit to the second distributed unit on the UE.

18. The method according to claim 17, further comprising: Capability information associated with the UE is sent to the core network mobility service, an additional core network service of the plurality of core network services, or both, wherein receiving the handover command is based at least in part on the capability information.

19. The method according to claim 17, further comprising: and sending, to the core network mobility service, an additional one of the multiple core network services, or both, an indication of the multiple core network services active at the UE, wherein receiving the handover command is based at least in part on sending the indication of the multiple core network services active at the UE.

20. The method of claim 17, further comprising: establishing a communication tunnel with the second distributed unit based at least in part on the handover command; Before the handover process is completed, receiving a second message for the UE; as well as Based at least in part on receiving the second message, one or more packets are sent to the second distributed unit via the communication tunnel for relaying to the UE.

21. The method of claim 17, further comprising: An indication of a plurality of candidate distributed units including the second distributed unit and one or more cell identifiers associated with one or more service cells supported by the second distributed unit are sent via the message, wherein receiving the handover command is based at least in part on sending the indication of the plurality of candidate distributed units.

22. The method of claim 17, further comprising: receiving, via the handover command, an indication of the at least one core network service supported by the second distributed unit; as well as The indication of the at least one core network service supported by the second distributed unit is sent to the UE via the handover command.

23. The method of claim 17, further comprising: receiving, from the core network mobility service, a measurement configuration indicating one or more triggering conditions including the triggering condition; as well as The measurement configuration is sent to the UE, wherein sending the message associated with the satisfying of the triggering condition is based at least in part on the measurement configuration.

24. The method according to claim 23, further comprising: Based at least in part on the measurement configuration, a measurement report, a second message indicating the trigger condition, or both are received from the UE, wherein sending the message associated with the satisfaction of the trigger state is based at least in part on receiving the measurement report, the second message indicating the trigger condition, or both.

25. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; as well as The instructions stored in the memory are executable by the processor to cause the device to perform the following operations: communicating with a first distributed unit a plurality of service messages associated with a plurality of core network services provided by a service-based network and active at the UE; receiving, from a core network mobility service of the plurality of core network services and via the first distributed unit, a measurement configuration indicating one or more triggering conditions associated with a handover procedure at the UE; sending a second message to the first distributed unit for relaying to the core network mobility service, the second message indicating satisfaction of a trigger condition of the one or more trigger conditions; receiving, based at least in part on the satisfaction of the trigger condition, a handover command from the core network mobility service via the first distributed unit, the handover command instructing a second distributed unit supporting at least one core network service of the plurality of core network services active at the UE; as well as Communicating with the second distributed unit based at least in part on receiving the switch command.

26. The method according to claim 25, wherein: The instructions can be further executed by the processor to cause the device to perform the following operations: Sending capability information associated with the UE to the first distributed unit, the core network mobility service, an additional core network service among the plurality of core network services, or any combination thereof, wherein receiving the handover command is based at least in part on the capability information.

27. The method according to claim 25, wherein: The instructions can be further executed by the processor to cause the device to perform the following operations: A cell identifier associated with a serving cell supported by the second distributed unit and a set of communication parameters for communicating with the serving cell are received via the handover command, wherein communicating with the second distributed unit is based at least in part on the cell identifier and the set of communication parameters.

28. The method according to claim 25, wherein: The instructions can be further executed by the processor to cause the device to perform the following operations: sending a service request for establishing service with the core network mobility service to a network address associated with the core network mobility service; and Based at least in part on the service request, control signaling is received indicating a service context for communicating with the core network mobility service, wherein sending the second message, receiving the handover command, or both is based at least in part on the service context.

29. The method according to claim 25, wherein: The instructions can be further executed by the processor to cause the device to perform the following operations: Performing measurements on signals received from the first distributed unit and one or more candidate distributed units including the second distributed unit, wherein the measurements are performed according to the measurement configuration, and wherein sending the second message is based at least in part on performing the measurements.

Images