Techniques for connected-state mobility in service-based wireless systems

Abstract

A method, system, and device for wireless communications are described. A user equipment (UE) may receive a measurement configuration including a trigger condition for performing a handover procedure in a service-based wireless system. The UE may send a message indicating satisfaction of the trigger condition to a source network entity, a mobility service provided by the service-based network, or both. After a handover decision is made 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 in the UE. The UE may then receive a handover command from the mobility service and perform the handover procedure to the target network entity.

Description

[Technical Field]

[0001] cross reference This patent application claims priority to U.S. Patent Application No. 17 / 948,044 by PURKAYASTHA et al., entitled "TECHNIQUES FOR CONNECTED STATE MOBILITY IN A SERVICE-BASED WIRELESS SYSTEM," filed September 19, 2022, which is assigned to the assignee of the present application and is expressly incorporated herein by reference in its entirety.

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

[0003] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasts, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems, sometimes referred to as New Radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM), etc. A wireless multiple-access communication system may include one or more base stations that each support wireless communication for communication devices, sometimes known as user equipment (UE).

[0004] In some wireless communication systems, a UE may perform handover procedures from one cell to another and / or from one network entity to another as the UE moves around within the system. However, in the context of service-based networks, such as Sixth Generation (6G) networks, performing handovers between network entities may disrupt ongoing communications between the UE and core network services to which the UE subscribes. Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for connected-state mobility in service-based wireless systems. Generally, aspects of the present disclosure are directed to signaling for handover procedures in service-based networks. In particular, aspects of the present disclosure are directed to signaling that enables a user equipment (UE) to perform a handover procedure from one network entity to another (e.g., 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. For example, the UE and / or a source network entity connected to the UE may identify trigger conditions for performing the handover procedure. Based on the trigger conditions, the 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. The mobility service may then 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) of the active core network services in the UE, and then send a handover command to the source network entity (for relay to the UE) so that the UE can perform a handover procedure from the source network entity to the target network entity.

[0006] A method for wireless communication in a UE is described that may include communicating with a first DU a set of service messages, the set of service messages being provided by a service-based network and associated with a set of core network services that are active in the UE, receiving, via the first DU, a measurement configuration from a core network mobility service of one of the set of core network services, the measurement configuration indicating one or more trigger conditions associated with a handover procedure in the UE, the measurement configuration indicating one or more trigger conditions associated with a handover procedure in the UE, transmitting a second message to the first DU for relay to the core network mobility service, the second message indicating satisfaction of the one of 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 that supports at least one core network service of the set of core network services that are active in the UE, and communicating with the second DU based on receiving the handover command.

[0007] An apparatus for wireless communication in a UE is described, which 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 communicate with a first DU a set of service messages, the set of service messages being provided by a service-based network and associated with a set of core network services that are active at the UE; receive, via the first DU, from a core network mobility service for one of the set of core network services, a measurement configuration indicating one or more trigger conditions associated with a handover procedure at the UE; send to the first DU for relay to the core network mobility service a second message indicating satisfaction of the one of the one or more trigger conditions; receive, based on the satisfaction of the trigger condition, from the core network mobility service via the first DU, a handover command indicating a second DU that supports at least one core network service of the set of core network services that is active at the UE; and communicate with the second DU based on receiving the handover command.

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

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

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

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, 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, and communicating with the second DU may be based on the cell identifier and the set of communication parameters.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for sending a service request to a network address associated with the core network mobility service to establish a service with the core network mobility service, and 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 may be based on the service context.

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

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

[0015] An apparatus for wireless communication in core network mobility services 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 receive, from a first DU in wireless communication with the UE, a message associated with satisfaction of a trigger condition for a handover procedure in the UE, select a second DU from a set of multiple candidate DUs based on the message based on the second DU being configured to support at least one core network service active in the UE from a set of multiple core network services of a service-based network, and transmit, to the first DU for relay to the UE, a handover command indicating the second DU based on the selection of the second DU and instructions for performing a handover procedure from the first DU to the second DU.

[0016] Another apparatus for wireless communication in core network mobility services is described, which may include: means for receiving, from a first DU in wireless communication with the UE, a message associated with satisfaction of a trigger condition for a handover procedure in the UE; means for selecting, based on the message, 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 that is active in the UE, among a set of multiple core network services of a service-based network; and means for transmitting, to the first DU for relay to the UE, a handover command indicating the second DU based on the selection of the second DU and instructions to perform a handover procedure from the first DU to the second DU.

[0017] A non-transitory computer-readable medium storing code for wireless communication in core network mobility services is described. The code may include instructions executable by a processor to receive, from a first DU in wireless communication with the UE, a message associated with satisfaction of a trigger condition for a handover procedure at the UE, select, based on the message, 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 that is active at the UE, from a set of multiple core network services of a service-based network, and transmit, to the first DU for relay to the UE, a handover command indicating the second DU based on the selection of the second DU, and instructions for performing a handover procedure from the first DU to the second DU.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, 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, and sending the handover command may be based on the ACK message.

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

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for receiving, via the ACK message, an indication of at least one core network service supported by the second DU, and sending the handover command may be based on receiving the indication of the at least one core network service.

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

[0022] 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 a set of multiple core network services.

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

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for receiving an indication of a set of multiple candidate DUs via a message, and selecting the second DU may be based on receiving the indication of the set of multiple candidate DUs.

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

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a second message from the second DU indicating completion of the handover procedure, and communicating with the UE via the second DU based on the second message.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for transmitting a measurement configuration indicating one or more trigger conditions, including the trigger condition, to the first DU for relay to the UE, and receiving the message may be based on the measurement configuration.

[0028] A method for wireless communication in a first DU is described. The method may include: communicating a set of service messages between a UE and a set of core network services of a service-based network that are active in the UE; sending a message associated with satisfaction of a trigger condition for a handover procedure in the UE to a core network mobility service of the set of core network services; receiving a handover command from the core network mobility service based on the message, the handover command indicating a second DU that supports at least one core network service of the set of core network services that are active in the UE; and sending the handover command to the UE, where the handover command includes instructions for the UE to perform a handover procedure from the first DU to the second DU.

[0029] 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 communicate a set of service messages between a UE and a set of core network services of a service-based network that are active at the UE, to send to a core network mobility service among the set of core network services a message associated with satisfaction of a trigger condition for a handover procedure at the UE, to receive from the core network mobility service based on the message a handover command indicating a second DU that supports at least one core network service among the set of core network services that are active at the UE, and to send the handover command to the UE, the handover command including instructions for the UE to perform a handover procedure from the first DU to the second DU.

[0030] Another apparatus for wireless communication in a first DU is described, which may include: means for communicating a set of service messages between a UE and a set of core network services of a service-based network that is active in the UE; means for sending a message associated with satisfaction of a trigger condition for a handover procedure in the UE to a core network mobility service of the set of core network services; means for receiving a handover command from the core network mobility service based on the message, the handover command indicating a second DU that supports at least one core network service of the set of core network services that is active in the UE; and means for sending the handover command to the UE, wherein the handover command includes instructions for the UE to perform a handover procedure from the first DU to the second DU.

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

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

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

[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for establishing a communication tunnel with a second DU based on the handover command, receiving a second message for the UE prior to completion of the handover procedure, and transmitting one or more packets to the second DU via the communication tunnel for relay to the UE based on receiving the second message.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting, via a 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 serving cells supported by the second DU, and receiving the handover command may be based on transmitting the indication of the set of multiple candidate DUs.

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

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

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

[0039] A method for wireless communication in a second DU is described that may include receiving, from a core network mobility service of a service-based network, a handover request associated with a handover procedure in a UE from a first DU to a second DU, 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 of a set of core network services that is active in 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.

[0040] An apparatus for wireless communication in 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 receive, from a core network mobility service of a service-based network, a handover request associated with a handover procedure in a UE from a first DU to a second DU, to 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 of a set of multiple core network services that is active in the UE and supported by the second DU, to communicate with the UE based on the handover request and the ACK message, and to send a second message to the core network mobility service indicating completion of the handover procedure based on communicating with the UE.

[0041] Another apparatus for wireless communication in a second DU is described that may include means for receiving a handover request associated with a handover procedure in a UE from a core network mobility service of a service-based network, from a first DU to a second DU, means 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 of a set of multiple core network services that is active in the UE and supported by the second DU, means for communicating with the UE based on the handover request and the ACK message, and means for sending a second message to the core network mobility service indicating completion of the handover procedure based on communicating with the UE.

[0042] 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, from a core network mobility service of a service-based network, a handover request associated with a handover procedure at a UE from a first DU to a second DU, 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 of a set of multiple core network services that is active at the UE and supported by the second DU, 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.

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

[0044] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, 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 prior to completion of the handover procedure; and transmitting one or more data packets associated with the second message to the UE based on receiving the one or more data packets via the communication tunnel.

[0045] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include an operation, feature, means, or instruction for transmitting a set of communication parameters for communication between the UE and the second DU to a core network mobility service via an ACK message, and communicating with the UE may be based on the set of communication parameters. [Brief explanation of the drawings]

[0046] [Figure 1] 1 illustrates an example of a wireless communication system that supports techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 2] 1 illustrates an example of a wireless communication system that supports techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 3]1 illustrates an example network architecture that supports techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 4] 1 illustrates an example of a wireless communication system that supports techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 5] 1 illustrates an example process flow supporting techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 6] 1 illustrates an example process flow supporting techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 7] 1 illustrates a block diagram of a device that supports techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 8] 1 illustrates a block diagram of a device that supports techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 9] 1 illustrates a block diagram of a communications manager that supports techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 10] 1 illustrates a diagram of a system including devices that support techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 11] 1 illustrates a block diagram of a device that supports techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 12] 1 illustrates a block diagram of a device that supports techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 13] 1 illustrates a block diagram of a communications manager that supports techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 14] 1 illustrates a diagram of a system including devices that support techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 15] 1 depicts a flowchart illustrating a method for supporting techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 16] 1 depicts a flowchart illustrating a method for supporting techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 17] 1 depicts a flowchart illustrating a method for supporting techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 18] 1 depicts a flowchart illustrating a method for supporting techniques for connected state mobility in a service-based wireless system, in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0047] Some wireless systems may exhibit a relatively vertical hierarchical architecture, including many “layers” of different devices that perform functions for the system. For example, a wireless system may include user equipment (UE), base stations / network entities, and numerous back-end (e.g., core network) devices associated with one or more functions for the system. Such a hierarchical structure may result in processing and other functions being performed in multiple devices (e.g., duplicated processing or capabilities across multiple back-end devices), thereby leading to wasted resources and excessive power consumption. Additionally, the back-end architecture of some wireless systems may be owned and maintained by a few operators, which may make it difficult for other parties / entities to integrate with the system and may complicate the system's ability to provide customized services and functionality to wireless devices.

[0048] In comparison, some wireless systems, such as 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 back-end components (e.g., in some systems) may be distributed across several core network services that may be hosted at different network addresses, such as in a cloud-based architecture. As a result, a UE in a service-based system may be able to establish and maintain connections with (e.g., “subscribe to”) different core network services or groups thereof on an a la carte basis, where each core network service provides or offers a distinct network function or service. For example, a service-based system may include mobility services, security services, privacy services, location services, etc. In this regard, each UE in a service-based system may be able to select which core network services it subscribes to based on the individualized characteristics or needs of the individual UE.

[0049] 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 such cases, a network entity of the RAN may interface with the service-based network and relay communications between the UE and the respective core network services. However, as the UE moves around within the network, the UE may perform handover procedures 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, performing a handover between network entities may disrupt ongoing communications between the UE and one or more core network services to which the UE subscribes.

[0050] Accordingly, aspects of the present disclosure are directed to signaling for handover procedures in service-based networks, such as 6G networks. In particular, aspects of the present disclosure are directed 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.

[0051] For example, the UE and / or a source DU connected to the UE may identify trigger conditions for performing a handover procedure. Based on the trigger conditions, the source DU or a mobility service (e.g., a core network mobility service that manages UE mobility within a network) may make a handover decision. The mobility service may then identify a target DU based on one or more active services in 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 in the UE. The mobility service may then send a handover command to the source DU (for relaying to the UE) so that the UE can perform the handover procedure from the source DU to the target DU. Following completion of the handover procedure, the source DU may relay communications between the UE and one or more supported core network services.

[0052] Aspects of the present disclosure are first described in the context of a wireless communication system. Additional aspects of the present disclosure are described in the context of example network architectures and example process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to techniques for connected state mobility in service-based wireless systems.

[0053] 1 illustrates an example wireless communication system 100 that supports techniques for capability indication for multiple services in a service-based wireless system in accordance with one or more aspects of the present disclosure. 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 network operating in accordance with 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 LTE-Advanced (LTE-A) network, an LTE-A Pro network), or other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

[0055] The 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. The UEs 115 may be devices of different types or with different capabilities. Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.

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

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

[0058] In some examples, the network entity 105 may 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 may be provided over the service-based network 130 using one or more APIs. For example, one or more DU service APIs 175 may provide an interface for one or more services in the UE 115. The services in the UE 115 may correspond to one or more CN / RAN services 185 in the service platform 150. For example, a network service API 180 in the service-based network 130 may interface with a corresponding DU service API 175 in the DU 165, which in turn interfaces with a corresponding API in the UE 115 to provide service connectivity between the one or more UE 115 services and the corresponding CN / RAN services 185.

[0059] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., base transceiver station, radio base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation NodeB or giga-NodeB (any of which may be referred to as a gNB), 5G NB, next-generation eNB (ng-eNB), Home NodeB, Home eNodeB, 6G NB, or other suitable terminology). In some examples, the network entities 105 (e.g., base station 140) may be implemented in a converged (e.g., monolithic, standalone) base station architecture that may be configured to provide wireless access utilizing a service-based architecture within a single network entity 105 (e.g., a single RAN node such as base station 140 may include RU 170, DU 165, and DU API 175 for CN / RAN services 185). The RU 170 may also be called a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP).

[0060] Additionally, in some examples, one or more network entities 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., cloud RAN (C-RAN)). For example, the network entities 105 may include one or more of a central unit (CU), a DU 165, an RU 170, a RAN Intelligent Controller (RIC) (e.g., a near-real-time RIC (near-RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system, or any combination thereof. One or more components of the network entity 105 in a disaggregated 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 in a disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0061] The division of functions among components (e.g., CU, DU, and RU) is flexible and may support different functionality depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are implemented in the components. For example, a functional division of a protocol stack may be adopted between the CU and the DU 165 such that the CU can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU may 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 may host one or more service APIs for one or more CN / RAN services 185 via corresponding network service APIs 180 of the service-based network 130. The CU may be connected to one or more DUs 165 or RUs 170, which may host lower protocol layers such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, each of which may be at least partially controlled by the CU. Additionally or alternatively, functional division of the protocol stack may be employed between the DUs 165 and the 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 DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional division between the CU and the DU 165 or between the DU 165 and the RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of the CU, the DU 165, or the RU 170, while other functions of the protocol layer are performed by a different one of the CU, the DU 165, or the 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 the respective network entities 105 communicating via such communication link.

[0062] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., for service-based network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access links and backhaul links (e.g., backhaul communication link 120). An IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the associated IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antenna (e.g., of the RU 170) of the IAB node 104 used 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., the IAB node 104, the UE 115) in an access network (e.g., downstream) relay chain or configuration. In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate in accordance with the techniques described herein.

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

[0064] The UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, and a "device" may also be referred to as a unit, a station, a terminal, or a client, among other examples. The UE 115 may also include or 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, the 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 communications (MTC) device, among other examples, which may be implemented in various items such as an appliance, a vehicle, a meter, or the like.

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

[0066] The UE 115 and the network entity 105 may wirelessly communicate with each other over one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier used for the communication link 125 may include a portion (e.g., a bandwidth part (BWP)) of an RF spectrum band operated 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 may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation on the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and another device may refer to communication between the device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, when referring to a network entity 105, the terms "transmitting," "receiving," or "communicating" may refer to any portion of the network entity 105 (e.g., base station 140, CU, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or through one or more other network entities 105).

[0067] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition or control signaling to coordinate operation with other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and can be identified according to a channel raster for discovery by the UE 115. A carrier may be operated in a standalone mode, where initial acquisition and connection may be made by the UE 115 via the carrier, or the carrier may be operated in a non-standalone mode, where connection is anchored using a different carrier (e.g., of the same or different radio access technology).

[0068] The communication links 125 shown in the wireless communication system 100 may include, among other transmission configurations, 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. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry downlink and uplink communications (e.g., in TDD mode).

[0069] 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 carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of a carrier of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., the network entities 105, the UEs 115, or both) may have a hardware configuration that supports communication using a particular carrier bandwidth or may be configurable to support communication using one of the set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entities 105 or UEs 115 that support simultaneous communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, BWP) or all of the carrier bandwidth.

[0070] A signal waveform transmitted over a carrier may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., the time length of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely proportional. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively large number of resource elements (e.g., during a transmission duration) and a relatively high order of the modulation scheme may correspond to a relatively higher communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may further increase the data rate or data integrity for communications with UE 115.

[0071] One or more numerologies for a carrier may be supported, and the numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs with the same or different numerologies. 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 communication for the UE 115 may be limited to one or more active BWPs.

[0072] The time interval for the network entity 105 or the UE 115 is, for example, T s =1 / (Δf max N f) seconds, where Δf max may represent the supported subcarrier spacing, and N f may represent the supported discrete Fourier transform (DFT) sizes. The communication resource time intervals may be organized according to radio frames, each having a specified time length (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0073] Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain amount of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on the subcarrier spacing. Each slot may include a certain number of symbol periods (e.g., depending on the length of a cyclic prefix prepended to each symbol period). In some wireless communication systems 100, a slot may be further divided into multiple minislots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the frequency band of operation.

[0074] A subframe, slot, minislot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a 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., among bursts of shortened TTIs (sTTIs)).

[0075] Physical channels may be multiplexed for communication using carriers according to various techniques. Physical control channels and physical data channels may be multiplexed for signaling over downlink carriers using, for example, 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 the physical control channels may be defined by a set of symbol periods and may span the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search the 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 at 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 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 sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0076] 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 for communication 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) for distinguishing neighboring cells. In some examples, a cell may also refer to a coverage area 110 or a portion (e.g., a sector) of a coverage area 110 in which the logical communication entity operates. Such a cell may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area, depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include, among other things, a building, a subset of a building, or an outer space between or overlapping with the coverage area 110.

[0077] A macro cell generally covers a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 115 that subscribe to service with the network provider that supports the macro cell. Small cells may be associated with lower-power network entities 105 (e.g., lower-power base stations 140) compared to macro cells, and the small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as the macro cell. A small cell may provide unrestricted access to UEs 115 that subscribe to service with the network provider, or may provide restricted access to UEs 115 that have an association with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in their homes or offices). The network entity 105 may support one or more cells and may support communication via one or more cells using one or more component carriers.

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

[0079] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus may provide communication coverage for moving 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 a heterogeneous network, for example, where different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0080] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that enable devices to communicate with each other or with a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application program that uses or presents the information to a human who interacts with the application program. Some UEs 115 may be designed to collect information or enable 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, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.

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

[0082] In some examples, the UEs 115 may be configured to support direct communication 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 of a group conducting D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of the network entity 105, or in some cases, may not be able to or configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without the involvement of the network entity 105.

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

[0084] In some deployments, multiple RANs may be accessed by one or more UEs 115 or network entities 105, such as, for example, a 6G RAT and a 5G RAT. In some examples, the 6G RAT may be associated with a service-based network 130, and the 5G RAT may be associated with a 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 or interconnects to external networks. The control plane entity 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 forwarded through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to IP services 195 for one or more network operators.IP services 195 may include access to the Internet, intranet(s), IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0085] The wireless communication system 100 may operate using one or more frequency bands, which may range from 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz region is commonly known as the ultra-high frequency (UHF) region or decimeter band because wavelengths range in length from approximately 1 decimeter to 1 meter. Although UHF waves may be blocked or redirected by buildings and environmental features, sometimes referred to as clusters, the waves can penetrate structures sufficiently for a macrocell to provide service 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 shortwave (high frequency (HF)) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0086] The wireless communication system 100 may also operate using the super high frequency (SHF) region, also known as the centimeter band, which may range from 3 GHz to 30 GHz, or the extremely high frequency (EHF) region of the spectrum, also known as the millimeter band (e.g., from 30 GHz to 300 GHz). 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 170), where the EHF antennas on each device may be smaller and more closely spaced than UHF antennas. In some examples, such technology may facilitate the use of antenna arrays within the device. However, propagation of EHF transmissions may be subject to greater attenuation and over shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of bands across these frequency regions may vary by country or regulatory body.

[0087] The wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0088] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ 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 in one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be collocated in an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located in various geographic locations. The network entity 105 may include an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming of communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted through the antenna ports.

[0089] The network entity 105 or the UE 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques are sometimes referred to as spatial multiplexing. Multiple signals may be transmitted by a transmitting device via, for example, 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 techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0090] Beamforming, sometimes referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming may be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjusting signals communicated through antenna elements may include the transmitting or receiving device applying an amplitude offset, a phase offset, or both to signals carried through the antenna elements associated with the device. The adjustment associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device, or to some other orientation).

[0091] The network entity 105 or the UE 115 may use beam sweeping 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 a beamforming operation for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the network entity 105 along different directions. For example, the network entity 105 may transmit signals according to different beamforming weight sets associated with different directions of transmission. The transmissions along different beam directions may be used to identify beam directions (e.g., by a transmitting device such as the network entity 105 or by a receiving device such as the UE 115) for subsequent transmission or reception by the network entity 105.

[0092] Some signals, such as data signals associated with a particular receiving device, may be transmitted 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 a transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or otherwise acceptable signal quality.

[0093] In some examples, transmission by a device (e.g., by the network entity 105 or the UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a composite beam for transmission (e.g., from the network entity 105 to the UE 115). The 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 the system bandwidth or one or more subbands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)) that may or may not be precoded. The 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 transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170), the UE 115 may employ similar techniques to transmit a signal multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or to transmit a signal along a single direction (e.g., to transmit data to a receiving device).

[0094] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., network entity 105), such as a synchronization signal, a reference signal, a beam selection signal, or other control signals. For example, a receiving device may perform receiving 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 receive 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 receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receiving configurations or receiving directions. In some examples, a receiving device may 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 with 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 with multiple beam directions).

[0095] In some examples, the wireless communication system 100 may include a packet-based network operating using a cloud platform, such as service platform 150, that provides CN / RAN services 185. The CN / RAN services 185 may, in some examples, be hosted based on the deployment topology and capabilities for service parameters associated with each service. Providing CN / RAN services 185 enables 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, among others) from transport functions (e.g., data radio bearer (DRB) and logical channel (LC) management, data service configuration, among others). Service-based functionality (e.g., message brokers decoupling radio network procedures from network delivery mechanisms) may allow flexibility for some functions (e.g., Layer 2 (L2) functions) to be hosted somewhere in the cloud, allowing for enhanced scalability, resilience, elasticity, agility, reuse, visibility, automation, failover, or any combination thereof (e.g., each service across the RAN and core network may be scaled independently by increasing or decreasing resources allocated across functions independently). Furthermore, efficiency may be improved through providing real-time link management to the RAN edge, enabling adaptation in DU 165 for more efficient activation, deactivation, or selection of features based on UE state.

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

[0097] For example, the UE 115, a source DU 165 connected to the UE 165, a mobility service (e.g., a core network service that manages mobility for the UE 115 in a 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 UE 115 mobility in a network) may make a handover decision. The mobility service may then identify a target DU 165 based on one or more active services in 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 in the UE 115. The mobility service may then send a handover command to the source DU 165 (for relay to the UE 115) so that the UE 115 can perform a handover procedure from the source DU 165 to the target DU 165. Following completion of the handover procedure, the source DU 165 may relay communications between the UE 115 and one or more supported core network services.

[0098] Techniques described herein may enable a UE 115 to perform handover procedures between DUs 165 and / or network entities 105 of a service-based wireless system while reducing or minimizing disruption 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 handover procedures to a target DU / target network entity that supports at least some of the active core network services at the UE 115. Accordingly, aspects of the present disclosure may reduce interruptions to communications conducted using core network services, thereby reducing or preventing the need for the UE 115 to continually re-establish communications using core network services. In this regard, techniques described herein may reduce signaling associated with a UE 115 that subscribes to core network services, reducing interruptions and improving the overall user experience.

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

[0100] 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 with or interface with a RAN 210 of the wireless communication system 200, the RAN 210 including 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, 215-e). In some implementations, the service-based network 205 may include or be associated with a cloud platform, with each core network service 215 hosted at a respective network address within the cloud platform.

[0101] 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 that 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), and the communication links 220 may be configured to facilitate bidirectional communications between the network entity 105-a and each of the respective core network services 215 of the service-based network 205.

[0102] 2, the wireless communication system 200 may exhibit a service-based architecture in which entities of the RAN 210 (e.g., network entity 105-a) are configured to connect the UE 115-a to core network services 215 of the service-based network 205. In particular, the RAN 210 (e.g., network entity 105-a) may be configured to relay communications between the UE 115-a and various core network services 215 of the service-based network to enable the UE 115-a to establish and maintain a wireless connection with each core network service 215 for exchanging communications associated with various network functionalities supported by the respective core network service 215. In other words, the wireless communication system 200 may enable the UE 115-a to “subscribe” to each core network service 215 on an a la carte basis, depending 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 running on the UE 115, the mobility of the UE 115, etc.

[0103] Each core network service 215 may be associated with a distinct network address within the service-based network 205. In other words, each core network service 215 may be hosted in one or more components of the cloud-based network, and each core network service 215 component may be associated with a distinct network address. Each core network service 215 may be provided by a network provider, a third-party entity, etc., where each core network service 215 is configured to support a distinct service or functionality provided to a component of the wireless communication system 200 (e.g., UE 115-a, network entity 105-a).

[0104] Different services, functionalities, and core network functions that may be supported or provided by each core network service 215 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 to facilitate geographic movement of the 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 subscribing UEs 115 within the wireless communication system 200.

[0105] In some aspects, each core network service 215 may include a separate API configured to facilitate wireless communication with the network entity 105-a and the UE 115-a, such as the network service API 180 shown in FIG. 1. The API in each core network service 215 may include a routing API, a configuration API, or both. The routing API may be configured for service data unit communication between the UE 115-a and the respective core network service 215. In comparison, the configuration API may be configured to facilitate communication between the network entity 105-a and the respective core network service 215 to negotiate service requirements and service-specific behaviors.

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

[0107] The service-based wireless communications system 200 (e.g., a 6G network) shown in FIG. 2 may offer several differences and advantages compared to some other types of wireless systems, such as networks that instead exhibit a relatively more vertically hierarchical architecture that includes many “layers” of different devices that perform functions for the network. A more hierarchical structure may result in processing and other functions being performed in multiple devices (e.g., the network entity 105 and one or more back-end devices), thereby leading to inefficient use of resources and high power consumption. In addition, the back-end architecture of a network with a more vertically hierarchical 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 UEs 115 and other devices may be difficult to customize within such a system.

[0108] In comparison, the service-based wireless communications system 200 shown in Figure 2 exhibits a flatter, horizontal architecture that allows each function of the wireless communications system to be distributed across different components of the system (e.g., core network services 215). For example, such functions and protocols may be divided and distributed across a set of core network services 215, such that each core network service 215 may support or enable a subset of the capabilities and functionality of a conventional wireless communications system. In other words, a service-based architecture may allow functions and protocols to be divided into self-contained services (e.g., core network services 215) as compared to components that provide all-encompassing network functions and protocols (e.g., modularization of network services / functionality across multiple core network services 215).

[0109] In this regard, the wireless communications system 200 may represent an example of a cloud-native platform configured to host mergers of CORE and RAN services, which may simplify protocols and reduce duplication of processing operations across the CORE and RAN (e.g., redistribution of CORE and RAN 210 services). In other words, convergence of RAN 210 and CN functions may reduce repeated operations and functionality to serve one UE at different layers.

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

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

[0112] 3 illustrates an example of a network architecture 300 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports techniques for system information broadcasting in a service-based wireless system according to one or more aspects of the present disclosure. 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 the service-based network 130 or 205, that communicates with the DU 165-a via 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 backhaul communication link 120-a or indirectly with the 5G core 190-a via one or more disaggregated network entities 105 (e.g., a quasi-RT RIC 330-a via an E2 link, or a non-RT RIC 330-b associated with the SMO 335 (e.g., an SMO framework), or both). The CU 310 may communicate with one or more DUs 165-a via respective midhaul communication links 315 (e.g., F1 interfaces). The DUs 165-a may communicate with one or more RUs 170-a via respective fronthaul communication links 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with the UE 115-b via one or more communication links 125-a. In some implementations, the UE 115-b may be served by multiple RUs 170-a simultaneously.

[0113] Each of the network entities 105 (e.g., CU 310, DU 165-a, RU 170-a, non-RT RIC 330-a, quasi-RT RIC 330-b, SMO 335, Open Cloud (O-Cloud) 320, Open eNBs (O-eNBs) 325) of network architecture 300 may include one or more interfaces or may be coupled with one or more interfaces configured to receive or transmit signals (e.g., data, information) over a wired or wireless transmission medium. Each network entity 105, or an associated processor (e.g., controller) that provides instructions to the interfaces of the network entity 105, may be configured to communicate with one or more of the other network entities 105 over a transmission medium. For example, a network entity 105 may include a wired interface configured to receive or transmit signals to one or more of the other network entities 105 over 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 (such as an RF transceiver), configured to receive and / or transmit signals to one or more of the other network entities 105 via a wireless transmission medium.

[0114] In some examples, the CU 310 may host one or more upper layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 may be implemented to communicate with the DU 165-a, as needed, for network control and signaling.

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

[0116] In some examples, lower layer functionality may be hosted by one or more RUs 170-a. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node hosting RF processing functions, or lower PHY layer functions (such as performing fast Fourier transforms (FFTs), inverse FFTs (iFFTs), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division, such as a lower layer functional division. In such an architecture, an 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(s) 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

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

[0118] The non-RT RIC 330-b may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and RAN resources, artificial intelligence (AI) or machine learning (ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 330-a. The non-RT RIC 330-b may be coupled to or communicate with the quasi-RT RIC 330-a (e.g., via an A1 interface). The quasi-RT RIC 330-a may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and RAN resources through data collection and action via interfaces connecting one or more CUs 310, one or more DUs 165-a, or both, and the O-eNB 325 to the quasi-RT RIC 330-a (e.g., via an E2 interface).

[0119] In some examples, the non-RT RIC 330-b may receive parameters or external enrichment information from an external server to generate AI / ML models deployed to the quasi-RT RIC 330-b. Such information may be utilized by the quasi-RT RIC 330-a and may be received at the SMO 335 or the non-RT RIC 330-b from non-network data sources or from network functions. In some examples, the non-RT RIC 330-b or the quasi-RT RIC 330-a may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 330-b may employ AI / ML models to monitor long-term trends and patterns in performance and implement corrective actions through the SMO (e.g., reconfiguration via O1) or by generating RAN management policies (e.g., A1 policies).

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

[0121] 4 illustrates an example wireless communication system 400 that supports techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. In some examples, aspects of the wireless communication system 400 may implement 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 that enable the UE 115 to perform a handover procedure from one network entity 105 to another network entity 105 (or from one DU to another DU) in a manner that minimizes disruption to active core network services 405 at the UE 115, as described with respect to FIG. 1.

[0122] 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 examples of O-RAN entities that include multiple components, such as one or more DUs, as shown and described in FIG. 3. In this regard, the network entities 105-b, 105-c shown in FIG. 4 may additionally or alternatively be referred to as DUs or eDUs (e.g., first / source DU, second / target DU).

[0123] 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 the service-based network 205 shown in Figure 2. In some aspects, the service-based network including the core network services 405-a, 405-b may be configured to communicate with or interface with a RAN of the wireless communication system 400, the RAN including one or more network entities (e.g., the first network entity 105-b, the second network entity 105-c). In some implementations, the core network services 405-a, 405-b may be associated with or hosted by a cloud platform, with each core network service 405 hosted at a respective network address within the cloud platform.

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

[0125] 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 service 405 and 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 service 405 and vice versa. The network entity 105 may facilitate traffic routing between the respective devices directly, via other network entities 105, via a proxy, or any combination thereof.

[0126] In the context of a service-based wireless system, the UE 115-b may subscribe to various core network services 405 provided by the service-based network. However, as the UE 115-b moves around within the network, the UE 115-b may perform handover procedures 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, such as a 6G network, performing a handover between network entities 105 may disrupt ongoing communications between the UE 115-b and the core network services 405 to which the UE 115-b subscribes (e.g., may disrupt active core network services 405).

[0127] Accordingly, the wireless communication system 400 may support signaling for handover procedures in a service-based network. In particular, the wireless communication system 400 may support 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.

[0128] In some implementations, the service-based network may provide or support a mobility service (e.g., a core network mobility service) that controls and handles mobility and connectivity management for the UE 115 in the wireless communication system 400. For example, the first core network service 405-a may include a mobility service to which the UE 115 moving around within the network subscribes so that the mobility service can manage handover procedures and connectivity for the UE 115 as the UE 115 moves around within the network.

[0129] In some aspects, a mobility service (e.g., the first core network service 405-a) may maintain UE context information related to mobility when the UE 115-b is connected to a network. For example, the mobility service may maintain access and roaming restrictions (e.g., a mobility restriction list) that may include a list of public land mobile networks (PLMNs), radio access technologies (RATs) within each PLMN, and respective service areas that the UE 115-b can or cannot access. In some aspects, the mobility service may maintain or receive information from a UE subscription service to determine access and roaming restrictions for the 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.

[0130] 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 in the UE 115-b from the UE 115-b, the first network entity 105-b, and / or another core network service 405, such as a core network capability service. The capabilities that may be reported by the UE 115-b and / or maintained in 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).

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

[0132] The source network entity 105-b (e.g., a source eDU communicatively coupled to the UE 115-b) may be configured to obtain capabilities related to the UE (e.g., from the UE 115-b, a mobility service, a capability service, etc.) and determine an RLC layer configuration, a MAC layer configuration, and a PHY layer configuration for the UE 115-b when the UE 115-b operates in a serving cell supported by the first network entity 105-b.

[0133] In some aspects, both the UE 115-b and the source network entity 105-b may be aware of the connectivity state 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 connectivity state information for the UE 115-b. For example, the source network entity 105-b 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 were previously connected to the network entity 105-b.

[0134] For each UE 115 connected to the network (and / or for each UE 115 that subscribes to the mobility service), the mobility service may maintain information regarding the network entities 105 (e.g., DUs, eDUs) and the cell(s) supported by the network entity 105 that is serving the respective UE 115. In other words, for each UE 115 in the network (or for each UE 115 that subscribes to the mobility service), the mobility service may maintain historical mobility information associated with past and present network entities 105, DUs, serving cells, etc. to which the UE 115 is connected. The mobility service may also maintain (e.g., store) load information associated with the network entities or cells (e.g., the number of UEs 115 supported by each network entity 105 or serving cell), the traffic load associated with each such UE 115, etc. As described in further detail herein, such historical mobility information, load information, etc. may be used by a 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 is handed over.

[0135] It will be appreciated that the example is illustrative. Referring to the wireless communication system 400 shown in FIG. 4, the UE 115-b may communicate with a first network entity 105-b. For example, the UE 115-b may communicate service messages with one or more core network services 405 active in the 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 may relay service messages between the UE 115-b and the one or more core network services 405 active in the UE 115-b.

[0136] The UE 115-b may establish communication with a mobility service (e.g., the first core network service 405-a). In other words, the UE 115-b may subscribe to the mobility service such that the mobility service can manage mobility and connectivity management (e.g., manage handover procedures) for the UE 115-b within the wireless communication system 400. For example, the UE 115-b may send a service request to establish 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 may 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 may relay each communication between the UE 115-b and the mobility service. Furthermore, subsequent communications between the UE 115-b and the mobility service 605 may be conducted in accordance with the service context.

[0137] In some aspects, the UE 115-b may transmit capability information associated with the UE 115-b to a first network entity 105-b, a mobility service, an 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 serving cells that the UE 115-b can or cannot access, etc. Similarly, the first network entity 105-b, the second network entity 105-c, or both may transmit capability information to a mobility service, another core network service 405 (e.g., a core network capability service), or both. The capability information associated with the network entities 105 may include core network services supported by the respective network entity 105 (e.g., each eDU may provide information about the entire set of services / slices it supports).

[0138] If the UE 115-b and / or the network entity 105 transmit capability information to a capability service (e.g., a core network capability service), the mobility service 605 may be configured to retrieve the capability information from the capability service to facilitate handover procedures for the UE 115-b. As previously described herein, such capability information may be used by the mobility service 605 to select a target network entity 105 and / or a target cell for the UE 115-b.

[0139] In some implementations, the UE 115-b may be configured with a measurement configuration including one or more trigger conditions associated with performing a handover procedure at the UE 115-b. The measurement configuration may relate to mobility for both the source eDU (e.g., the first network entity 105-b) and the UE 115-b. As another example, the UE 115-b may be configured with a measurement configuration for cell-level (e.g., Layer 3 (L3)) measurements, and L3 reports may be sent to the first network entity 105-b and / or the mobility service. Furthermore, 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.

[0140] 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. Furthermore, 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, there may be two (or more) alternative approaches for inter-eDU handover, depending on whether the mobility service or the source eDU configures the measurement configuration, processes the measurement reports, and makes the handover decision. Two distinct approaches for inter-eDU handover are further shown and described with reference to FIGS. 5 and 6.

[0141] 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., for determining a handover procedure) and a configuration of uplink reference signals that the first network entity 105-b should measure for mobility purposes. In addition, the measurement configuration may indicate a measurement gap and a trigger condition (e.g., an event trigger) for reporting a measurement report when the trigger condition is met.

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

[0143] 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 a 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 fulfillment of a trigger condition for a handover procedure, the trigger condition being identified by the measurement configuration.

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

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

[0146] When 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 candidate target network entities 105. For example, the UE 115-b may measure reference signals received from multiple candidate target network entities 105 (e.g., the second network entity 105-c) and indicate one or more of the candidate target network entities 105 in a measurement report, and 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 trigger condition for handover) may indicate a list of core network services 405 currently active in the UE 115-b. Such information may enable the mobility service to make the handover decision and / or select a target network entity 105 / target DU / target cell for a potential handover procedure.

[0147] Once the handover decision is made, the mobility service may select a target network entity 105 to which the UE 115-b is to be handed over. For example, as shown in FIG. 4, the mobility service (e.g., a core network mobility service, or a first core network service 405-a) may select the second network entity 105-c as the target for the handover procedure for the UE 115-b. Furthermore, in some aspects, the mobility service may select a serving cell of the second network entity 105-c to which the UE 115-b is to be handed over.

[0148] The mobility service may select the target network entity 105-c and / or the target serving cell for the handover procedure based on several parameters or factors, including, but not limited to, capability information associated with the UE 115-b, the core network services 405 active at the UE 115-b (e.g., the core network services 405 supported by the target network entity 105), an indication of candidate target network entities 105 indicated via the handover request, the mobility history of the UE 115-b, the traffic load 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., the second network entity 105-c) that supports at least one core network service 405 currently active at the UE 115-b.

[0149] 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 based on selecting the second network entity 105-c as the target for the handover procedure. In some implementations, the handover request may indicate a set of core network services 405 that are active in the UE 115-b, access restriction information and roaming access restriction information associated with the UE 115-b, or both.

[0150] In some implementations, the second network entity 105-c may perform admission control to determine which of the active core network services 405 in the UE 115-b are supported by the second network entity 105-c (e.g., determine a list of accepted services from among the services 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 flow associated with the slice.

[0151] 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 in 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.

[0152] In some aspects, the second network entity 105-c may indicate a communication configuration for communication with the second network entity 105-c in the ACK message (e.g., for relay to the UE 115-b). For example, the target network entity 105-c may determine the target cell AS protocol layer configuration and configuration(s) related to the accepted core network service 405 and indicate such configuration to the mobility service. In such a 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).

[0153] In an alternative implementation, the second network entity 105-c may reject 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 in the UE 115-b, the second network entity 105-c may reject the handover request. In such a case, the mobility service may reselect a new target for the handover procedure and send a new handover request to the newly selected target.

[0154] The mobility service may then send a handover command to the first network entity 105-b and / or the UE 115-b (e.g., for relay to the UE 115-b) with instructions for the UE 115-b to perform a handover procedure 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 serving 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 that are active in the 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, etc.

[0155] 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 respective devices. In some aspects, the communication tunnel may be configured to relay data packets destined for the UE 115-b between the respective devices during a handover procedure. In other words, during handover, a direct forwarding from the source eDU to the target eDU may be performed over the established IP tunnel for the flow to which data forwarding applies.

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

[0157] The UE 115-b may establish communication with the second network entity 105-c. Based on receiving the handover command (e.g., according to information included in the handover command), the UE 115-b may establish communication with the second network entity 105-c. The second network entity 105-c may then send a message to the mobility service indicating completion of the handover procedure. For example, the target eDU (e.g., the second network entity 105-c) may indicate a target cell ID to the mobility service once the handover is complete. In some cases, the mobility service may provide notification of the completed handover procedure to other core network services 405 (e.g., other core network services 405 active in the UE 115-b). Additionally, upon completion of the handover, the target eDU may request the access gateway (e.g., the UPF) to switch the path to the target eDU.

[0158] The UE 115-b may communicate with the second network entity 105-c upon completion of the handover procedure. For example, the UE 115-b may communicate service messages with one or more core network services 405 active in the UE 115-b via the second network entity 105-c. In other words, the first network entity 105-b may relay service messages between the UE 115-b and one or more core network services 405 active in the UE 115-b.

[0159] Techniques described herein may enable the UE 115-b to perform handover procedures between DUs and / or 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 the UE 115-b to perform handover procedures 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. Accordingly, aspects of the present disclosure may reduce interruptions to communications conducted using the core network services 405, thereby preventing the UE 115-b from having to continually re-establish communications with the core network services 405. In this regard, techniques described herein may reduce signaling associated with the UE 115-b that subscribes to the core network services 405, reducing the interruptions and improving the overall user experience.

[0160] 5 illustrates an example process flow 500 that supports techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. In some examples, aspects of process flow 500 may implement or be implemented by aspects of wireless communication system 100, wireless communication system 200, network architecture 300, wireless communication system 400, or any combination thereof. In particular, process flow 500 illustrates signaling that enables UE 115-c to perform a handover procedure from one network entity 105 to another network entity 105 (or from one DU to another DU) in a manner that minimizes disruption to active core network services at UE 115-c, as described with reference to FIGS. 1-4, among other aspects.

[0161] The process flow 500 may include a UE 115-c, a first network entity 105-d (e.g., a source network entity 105-d), a second network entity 105-e (e.g., a target network entity 105-e), and a mobility service 505 (e.g., a core network service or a core network mobility service), which may be examples of the UE 115, network entities 105, core network services, and other wireless devices described with reference to Figures 1-4. In some aspects, the mobility service 505 may control and handle mobility and connectivity management for the UE 115 within a wireless communication system.

[0162] In some aspects, the mobility service 505 may be included within a set of services provided or offered by a service-based network, such as the service-based network 205 shown in Figure 2. In such cases, the service-based network including the mobility service 505 may be configured to interface (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, the signaling shown in Figure 5 may include example signaling within a network having a service-based architecture, such as a 6G system.

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

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

[0165] 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 can manage mobility and connectivity management (e.g., manage handover procedures) for the UE 115-c within the wireless communication system.

[0166] For example, the UE 115-c may send a service request to a network address associated with the mobility service 505 to establish a service with the mobility service 505, and may receive control signaling based on the service request indicating a service context for communicating with the mobility service 505. In this example, the first network entity 105-d may relay each communication between the UE 115-c and the mobility service. Further, subsequent communications between the UE 115-c and the mobility service 505 may be conducted in accordance with the service context.

[0167] At 520, the UE 115-c may transmit capability information associated with the UE 115-c to the first network entity 105-d, the mobility service 505, an additional core network service (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 serving cells that the UE 115-c may or may not have access to, etc.

[0168] If the 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 handover procedures 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.

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

[0170] 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., for determining a handover procedure) and a configuration of uplink reference signals that the first network entity 105-d should measure for mobility purposes. In addition, the measurement configuration may indicate a measurement gap and a trigger condition (e.g., an event trigger) for reporting a measurement report when the trigger condition is met.

[0171] 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) in accordance with 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, which may be identified by the measurement configuration.

[0172] 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) in accordance with a measurement configuration to facilitate a handover decision. Additionally, the first network entity 105-d may perform measurements on uplink reference signals received from the UE 115-c in accordance with a measurement configuration to facilitate a handover decision. In some aspects, the UE 115-c may identify a trigger condition for a handover procedure when the quality, strength, or performance of the reference signal from the first network entity 105-d does not meet a threshold, when the quality, strength, or performance of the reference signal from the second network entity 105-e meets an additional threshold, or both. Similarly, the first network entity 105-d may identify a trigger condition for a handover procedure when the quality, strength, or performance of the reference signal from the UE 115-c does not meet a threshold.

[0173] 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 the measurement configuration at 525, performing the measurements at 530, identifying satisfaction of a trigger condition based on the measurements, or any combination thereof.

[0174] In some aspects, the message indicating the trigger condition may additionally or alternatively indicate candidate target network entities 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., may indicate candidate network entities 105 exhibiting sufficient performance).

[0175] 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 in the UE 115-c via the message at 535. Such information may enable the mobility service 505 to make handover decisions and select a target network entity 105 / target DU / target cell for a potential handover procedure.

[0176] 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 the satisfaction of a trigger condition) from the UE 115-c and / or the first network entity 105-d to make a handover decision (e.g., determine whether to initiate a handover procedure at the UE 115-c).

[0177] If the mobility service 505 determines 545 to trigger a handover procedure, the mobility service 505 may select a target network entity 105 to which the UE 115-c is to be handed over. For example, as shown in FIG. 5, the mobility service 505 may select a second network entity 105-e as the target for the handover procedure for 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 over.

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

[0179] 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 that is currently active in the UE 115-c. Furthermore, if multiple candidate network entities 105 support one or more core network services that are active in the UE 115-c, the mobility service 505 may select the network entity 105 that supports the highest percentage of active core network services in the UE 115-c. As another example, if 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).

[0180] 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 for the handover procedure at 545. In some implementations, the handover request may indicate a set of core network services that are active at the UE 115-c.

[0181] In some implementations, the second network entity 105-e may perform admission control to determine which of the active core network services in the UE 115-c are supported by the second network entity 105-e (e.g., determine a list of accepted services from among the services 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-e can accept / support may be based on the QoS requirements of the flow associated with the slice.

[0182] At 555, the mobility service 505 may receive an ACK message from the second network entity 105-e. The mobility service 505 may receive an 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.

[0183] In some aspects, the second network entity 105-e may indicate a communication configuration for communication with the second network entity 105-e in the ACK message (e.g., for relay to the UE 115-c). For example, the target network entity 105-e may determine a target cell AS protocol layer configuration and a configuration related to the accepted core network service and indicate such configuration(s) to the mobility service 505. In such a 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).

[0184] 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 in the UE 115-c, the second network entity 105-e may reject the handover request. In such a case, the mobility service 505 may reselect a new target for the handover procedure and send a new handover request to the newly selected target.

[0185] 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 relay to the UE 115-c) 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 making 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.

[0186] 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 serving cell (e.g., a target cell) supported by the second network entity 105-e, communication parameters for communicating with the second network entity 105-e (e.g., communication configurations such as target cell AS protocol layer configurations), a list of core network services active in the UE 115-c and supported / accepted by the second network entity 105-e, new measurement configurations associated with the second network entity 105-e, etc.

[0187] 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 destined for the UE 115-c between the respective devices during the handover procedure. In other words, during the handover, a direct forwarding from the source eDU to the target eDU may be performed over the established IP tunnel for the flow to which the data forwarding applies.

[0188] For example, during (e.g., before completion of) the handover procedure, 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) the handover procedure.

[0189] 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 (e.g., according to information included in the handover command).

[0190] At 575, the second network entity 105-e may send a message to the mobility service 505 indicating completion of the handover procedure. For example, the target eDU (e.g., the second network entity 105-e) may indicate a target cell ID to the mobility service 505 once 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 in the UE 115-c). Additionally, upon handover completion, the target eDU may request the access gateway (e.g., the UPF) to switch the path to the target eDU.

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

[0192] 6 illustrates an example process flow 600 that supports techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. In some examples, aspects of process flow 600 may implement or be implemented by aspects of wireless communication system 100, wireless communication system 200, network architecture 300, wireless communication system 400, process flow 600, or any combination thereof. In particular, process flow 600 illustrates signaling that enables UE 115-d to perform a handover procedure from one network entity 105 to another network entity 105 (or from one DU to another DU) in a manner that minimizes disruption to active core network services at UE 115-d, as described with reference to FIGS. 1-5, among other aspects.

[0193] The process flow 600 may include a UE 115-d, a first network entity 105-f (e.g., a source network entity 105-f), a second network entity 105-g (e.g., a target network entity 105-g), and a mobility service 605 (e.g., a core network service or a core network mobility service), which may be examples of the UE 115, network entities 105, core network services, and other wireless devices described with reference to Figures 1-5. In some aspects, the mobility service 605 may control and handle mobility and connectivity management for the UE 115 within a wireless communication system.

[0194] In some aspects, the mobility service 605 may be included within a set of services provided or offered by a service-based network, such as the service-based network 205 shown in Figure 2. In such cases, the service-based network including the mobility service 605 may be configured to interface (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, the signaling shown in Figure 6 may include example signaling within a network having a service-based architecture, such as a 6G system.

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

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

[0197] 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 can manage mobility and connectivity management (e.g., manage handover procedures) for the UE 115-d within the wireless communication system.

[0198] For example, the UE 115-d may send a service request to a network address associated with the mobility service 605 to establish a service with the mobility service 605, and may receive control signaling based on the service request indicating a service context for communicating with the mobility service 605. In this example, the first network entity 105-f may relay each communication between the UE 115-d and the mobility service. Further, subsequent communications between the UE 115-d and the mobility service 605 may be conducted in accordance with the service context.

[0199] At 620, the UE 115-d may transmit capability information associated with the UE 115-d to the first network entity 105-f, the mobility service 605, an additional core network service (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 serving cells that the UE 115-d may or may not have access to, etc.

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

[0201] At 625, the UE 115-d may receive from the first network entity 105-f a measurement configuration indicating one or more trigger conditions associated with performing 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 relate to mobility for both the source eDU (e.g., the first network entity 105-f) and the UE 115-d.

[0202] In comparison to the process flow 500 shown in FIG. 5 , in which the mobility service 505 configures the measurement configuration and makes the handover decision, the source network entity 105-f shown in FIG. 6 may configure the measurement configuration and make the handover decision. In this case, the mobility service may forward access restriction information and roaming access restriction information to the source eDU and the target eDU. In some cases, allowing the source eDU to configure the measurement configuration and measurement reporting may enable the source eDU to frequently update measurement gaps. Furthermore, allowing the source eDU (e.g., the first network entity 105-f) to configure the measurement configuration may provide some efficiency due to the fact that the source eDU may have complete and up-to-date knowledge of the time-frequency resources consumed by data and control signaling.

[0203] 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 across the respective devices. For example, according to one hybrid scheme, the mobility service 605 may determine the event type and trigger conditions for a handover procedure, and 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 trigger conditions to the source eDU.

[0204] 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., for determining a handover procedure) 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 when the trigger condition is met.

[0205] 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) in accordance with the measurement configuration communicated 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, which may be identified by the measurement configuration.

[0206] The UE 115-d may send a measurement report to the first network entity 105-f at 635. 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 periodicity or frequency, based on the satisfaction of a trigger condition, or both.

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

[0208] If the first network entity 105-f determines to trigger a handover procedure at 645, 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 a fulfillment of a trigger condition, performing a handover decision at 640, or any combination thereof.

[0209] In some aspects, the handover request message may additionally or alternatively indicate candidate target network entities 105. For example, the UE 115-d may measure reference signals received from multiple candidate target network entities 105 (e.g., the second network entity 105-g) and indicate one or more of the candidate target network entities 105 in a measurement report, with the first network entity 105-f relaying an 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.

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

[0211] At 650, the mobility service 605 may select a target network entity 105 to which the UE 115-d is to be handed over. For example, as shown in FIG. 6, the mobility service 605 may select a second network entity 105-g as the target for the handover procedure for 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 is to be handed over.

[0212] The mobility service 605 may select the target network entity 105-g and / or the target serving cell for the handover procedure based on several parameters or factors, including, but not limited to, the capability information associated with the UE 115-d received at 620, the core network services active at the UE 115-d (e.g., core network services supported by the target network entity 105), the indication of candidate target network entities 105 indicated in the handover request at 645, the mobility history of the UE 115-d, the traffic load 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.

[0213] 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) at 655. The mobility service 605 may send the handover request at 655 based on selecting the second network entity 105-g as the target for the handover procedure at 650. In some implementations, the handover request may indicate a set of core network services that are active at the UE 115-d, access restriction information and roaming access restriction information associated with the UE 115-d, or both.

[0214] In some implementations, the second network entity 105-g may perform admission control to determine which of the active core network services in the UE 115-d are supported by the second network entity 105-g (e.g., determine a list of accepted services from among the services 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 can accept / support may be based on the QoS requirements of the flow associated with the slice.

[0215] At 660, the mobility service 605 may receive an ACK message from the second network entity 105-g. The mobility service 605 may receive an ACK message from the second network entity 105-g based on (e.g., in response to) the handover request at 655. In some implementations, the ACK message may indicate one or more active core network services in 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.

[0216] In some aspects, the second network entity 105-g may indicate a communication configuration for communication with the second network entity 105-g in the ACK message (e.g., for relay to the UE 115-d). For example, the target network entity 105-g may determine a target cell AS protocol layer configuration and a configuration related to the accepted core network service and indicate such configuration to the mobility service 605. In such a 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 indicate the measurement configuration to the mobility service 605 (for relay to the UE 115-d).

[0217] In an alternative implementation, the second network entity 105-g may reject 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 in the UE 115-d, the second network entity 105-g may reject the handover request. In such a case, the mobility service 605 may reselect a new target for the handover procedure and send a new handover request to the newly selected target.

[0218] 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 relay to the UE 115-d) 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 making 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.

[0219] 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 serving cell (e.g., a target cell) supported by the second network entity 105-g, communication parameters for communicating with the second network entity 105-g (e.g., communication configurations such as target cell AS protocol layer configurations), a list of core network services active in the UE 115-d and supported / accepted by the second network entity 105-g, new measurement configurations associated with the second network entity 105-g, etc.

[0220] 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 destined for the UE 115-d between the respective devices during the handover procedure. In other words, during the handover, a direct forwarding from the source eDU to the target eDU may be performed over the established IP tunnel for the flow to which the data forwarding applies.

[0221] For example, during (e.g., before completion of) the handover procedure, 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 the data packets to the UE 115-d after (or during) the handover procedure.

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

[0223] At 680, the second network entity 105-g may send a message to the mobility service 605 indicating completion of the handover procedure. For example, the target eDU (e.g., the second network entity 105-g) may indicate a target cell ID to the mobility service 605 once 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 in the UE 115-d). Additionally, upon handover completion, the target eDU may request the access gateway (e.g., the UPF) to switch the route to the target eDU.

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

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

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

[0227] 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 traffic channels (e.g., control channels, data channels, traffic channels related to techniques for connected state mobility in service-based wireless systems). In some examples, the transmitter 715 may be collocated with the receiver 710 within a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.

[0228] The communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be examples of means for implementing various aspects of the techniques for connected state mobility in service-based wireless systems described herein. For example, the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.

[0229] In some examples, the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in this disclosure. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0230] Additionally or alternatively, in some examples, the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). When implemented in code executed by a processor, the functionality of the communications 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 a means for performing the functions described in this disclosure).

[0231] In some examples, communications manager 720 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with receiver 710, transmitter 715, or both. For example, communications manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both, to acquire information, output information, or perform various other operations described herein.

[0232] The communications manager 720 may support wireless communications in the UE according to examples disclosed herein. For example, the communications manager 720 may be configured as or otherwise support a means for communicating with a first DU a set of service messages associated with a set of core network services provided by a service-based network and active in the UE. The communications manager 720 may be configured as or otherwise support a means for receiving, from a core network mobility service of one of the set of core network services, via the first DU, a measurement configuration indicating one or more trigger conditions associated with a handover procedure in the UE. The communications manager 720 may be configured as or otherwise support a means for transmitting, to the first DU for relay to the core network mobility service, a second message indicating satisfaction of one of the one or more trigger conditions. The communications manager 720 may be configured or otherwise support a means for receiving a handover command from the core network mobility service via the first DU based on fulfillment of a trigger condition, the handover command indicating a second DU that supports at least one core network service of the set of core network services active in the UE. The communications manager 720 may be configured or otherwise support a means for communicating with the second DU based on receiving the handover command.

[0233] By including or configuring the communications manager 720 in accordance with examples described herein, the device 705 (e.g., a processor controlling or otherwise coupled to the receiver 710, the transmitter 715, the communications manager 720, or a combination thereof) may support techniques that enable the UE 115 to perform handover procedures between DUs 165 and / or network entities 105 of a services-based wireless system while minimizing disruption to active core network services at the UE 115. In particular, aspects of the present disclosure support techniques that enable the UE 115 to perform handover procedures to a target DU / target network entity that supports at least some of the active core network services at the UE 115. Accordingly, aspects of the present disclosure may reduce interruptions to communications conducted using core network services, thereby preventing the UE 115 from having to continually re-establish communications using core network services. In this regard, the techniques described herein may reduce signaling associated with a UE 115 that has subscribed to core network services, reducing interruptions and improving the overall user experience.

[0234] 8 shows a block diagram 800 of a device 805 supporting techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 805 may be an example of an aspect of the device 705 or UE 115 described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

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

[0236] 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 traffic channels (e.g., control channels, data channels, traffic channels related to techniques for connected state mobility in service-based wireless systems). In some examples, the transmitter 815 may be collocated with the receiver 810 within a transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.

[0237] Device 805, or its various components, may be an example of a means for implementing various aspects of the techniques for connected state mobility in service-based wireless systems described herein. For example, communications manager 820 may include a service message communications manager 825, a measurement configuration manager 830, a handover command reception manager 835, or any combination thereof. Communications manager 820 may be an example of an aspect of communications manager 720 described herein. In some examples, communications manager 820, or its various components, may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with receiver 810, transmitter 815, or both. For example, communications manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both, to acquire information, output information, or perform various other operations described herein.

[0238] The communications manager 820 may support wireless communications in the UE according to examples disclosed herein. The service message communications manager 825 may be configured as or may otherwise support a means for communicating a set of service messages with the first DU, the set of service messages being provided by the service-based network and associated with a set of core network services active in the UE. The measurement configuration manager 830 may be configured as or may otherwise support a means for receiving, via the first DU, a measurement configuration from a core network mobility service of one of the set of core network services, the measurement configuration indicating one or more trigger conditions associated with a handover procedure in the UE. The measurement configuration manager 830 may be configured as or may otherwise support a means for transmitting, to the first DU for relay to the core network mobility service, a second message indicating satisfaction of one of the one or more trigger conditions. The handover command reception manager 835 may be configured as or may otherwise support a means for receiving a handover command from the core network mobility service via the first DU based on fulfillment of a trigger condition, the handover command indicating a second DU that supports at least one core network service of the set of core network services active in the UE. The service message communication manager 825 may be configured as or may otherwise support a means for communicating with the second DU based on receiving the handover command.

[0239] 9 illustrates a block diagram 900 of a communications manager 920 supporting techniques for connected-state mobility in service-based wireless systems in accordance with one or more aspects of the present disclosure. Communications manager 920 may be an example of aspects of communications manager 720, communications manager 820, or both, as described herein. Communications manager 920, or its various components, may be an example of a means for implementing various aspects of the techniques for connected-state mobility in service-based wireless systems, as described herein. For example, communications manager 920 may include a service message communications 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 directly or indirectly with one another (e.g., via one or more buses).

[0240] The communications manager 920 may support wireless communications in the UE according to examples disclosed herein. The service message communications manager 925 may be configured as or may otherwise support a means for communicating with the first DU a set of service messages, the set of service messages being provided by the service-based network and associated with a set of core network services active in the UE. The measurement configuration manager 930 may be configured as or may otherwise support a means for receiving, via the first DU, a measurement configuration from a core network mobility service of one of the set of core network services, the measurement configuration indicating one or more trigger conditions associated with a handover procedure in the UE. In some examples, the measurement configuration manager 930 may be configured as or may otherwise support a means for transmitting, to the first DU for relay to the core network mobility service, a second message indicating satisfaction of one of the one or more trigger conditions. The handover command reception manager 935 may be configured or otherwise support a means for receiving a handover command from the core network mobility service via the first DU based on satisfaction of a trigger condition, the handover command indicating a second DU that supports at least one core network service of the set of core network services active in the UE. In some examples, the service message communication manager 925 may be configured or otherwise support a means for communicating with the second DU based on receiving the handover command.

[0241] In some examples, the capability information manager 940 may be configured as or otherwise support a means for transmitting capability information associated with the UE to the first DU, a core network mobility service, an additional core network service of a set of multiple core network services, or any combination thereof, and receiving the handover command is based on the capability information.

[0242] In some examples, the handover command reception manager 935 may be configured as or otherwise support a means for receiving, via a 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, and communicating with the second DU is based on the cell identifier and the set of communication parameters.

[0243] In some examples, the service request sending manager 945 may be configured as or may otherwise support a means for sending a service request to establish a service with a 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 as or may otherwise support a means for 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 is based on the service context.

[0244] In some examples, the measurement configuration manager 930 may be configured as or otherwise support a means for performing measurements on signals received from one or more candidate DUs, including the first DU and the second DU, the measurements being performed in accordance with the measurement configuration, and transmitting the second message being based on performing the measurements.

[0245] 10 shows a diagram of a system 1000 including a device 1005 supporting techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein, or may 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 communication, including components for transmitting and receiving communications, such as a communications manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, code 1035, and a processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1045).

[0246] The I / O controller 1010 may manage input and output signals for the device 1005. The I / O controller 1010 may also manage peripheral devices not integrated with the device 1005. In some cases, the I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1010 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1010 may be implemented as part of a processor, such as the processor 1040. In some cases, a user may interact with the device 1005 through the I / O controller 1010 or through a hardware component controlled by the I / O controller 1010 .

[0247] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have two or more antennas 1025 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, wired links, or wireless links described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for modulating packets, providing the received packets to one or more antennas 1025 for transmission, and demodulating packets received from the one or more antennas 1025. The transceiver 1015, or the transceiver 1015 and one or more antennas 1025, may be an example of the transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination or component thereof described herein.

[0248] The memory 1030 may include random access memory (RAM) and 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 on a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, the code 1035 may not be directly executable by the processor 1040, but may instead cause a computer to perform (e.g., when compiled or executed) the functions described herein. In some cases, the memory 1030 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0249] The processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, 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 cases, the 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 the processor 1040. The processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks supporting techniques for connected state mobility in service-based wireless systems). For example, the device 1005 or a component of the device 1005 may include the processor 1040 and the memory 1030 coupled to or associated with the processor 1040, and the processor 1040 and the memory 1030 may be configured to perform various functions described herein.

[0250] The communications manager 1020 may support wireless communications in the UE according to examples disclosed herein. For example, the communications manager 1020 may be configured as or otherwise support a means for communicating with a first DU a set of service messages associated with a set of core network services provided by a service-based network and active in the UE. The communications manager 1020 may be configured as or otherwise support a means for receiving, from a core network mobility service of one of the set of core network services, via the first DU, a measurement configuration indicating one or more trigger conditions associated with a handover procedure in the UE. The communications manager 1020 may be configured as or otherwise support a means for transmitting, to the first DU for relay to the core network mobility service, a second message indicating satisfaction of one of the one or more trigger conditions. The communications manager 1020 may be configured or otherwise support a means for receiving a handover command from the core network mobility service via the first DU based on fulfillment of a trigger condition, the handover command indicating a second DU that supports at least one core network service of the set of core network services active in the UE. The communications manager 1020 may be configured or otherwise support a means for communicating with the second DU based on receiving the handover command.

[0251] By including or configuring the communications manager 1020 according to examples described herein, the device 1005 may support techniques that enable the UE 115 to perform handover procedures between DUs 165 and / or network entities 105 of a service-based wireless system while minimizing disruption to active core network services at the UE 115. In particular, aspects of the present disclosure support techniques that enable the UE 115 to perform handover procedures to a target DU / target network entity that supports at least some of the active core network services at the UE 115. Accordingly, aspects of the present disclosure may reduce interruptions to communications conducted using core network services, thereby preventing the UE 115 from having to continually re-establish communications using core network services. In this regard, the techniques described herein may reduce signaling associated with a UE 115 that subscribes to core network services, reducing interruptions and improving the overall user experience.

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

[0253] 11 shows a block diagram 1100 of a device 1105 supporting techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of an aspect of a network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. The device 1105 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0254] The receiver 1110 may provide a means for obtaining (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 protocol stacks). The information may be passed to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0255] The transmitter 1115 may provide a means for outputting (e.g., transmitting, providing, conveying, 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 protocol stacks). In some examples, the transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by transmitting 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 within a transceiver, which may include or be coupled to a modem.

[0256] The communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be examples of means for implementing various aspects of the techniques for connected state mobility in service-based wireless systems described herein. For example, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.

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

[0258] Additionally or alternatively, in some examples, the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). When implemented in code executed by a processor, the functionality of the communications 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., that may be configured as or otherwise support a means for performing the functions described in this disclosure).

[0259] In some examples, communications manager 1120 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communications manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in combination with receiver 1110, transmitter 1115, or both, to acquire information, output information, or perform various other operations described herein.

[0260] The communications manager 1120 may support wireless communications in core network mobility services according to examples disclosed herein. For example, the communications manager 1120 may be configured as, or may otherwise support, a means for receiving, from a first DU configured to communicate with the UE, a message associated with fulfillment of a trigger condition for a handover procedure in the UE. The communications manager 1120 may be configured as, or may otherwise support, a means for selecting, based on the message, 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 in the UE from a set of multiple core network services of the service-based network. The communications manager 1120 may be configured as, or may otherwise support, a means for transmitting, to the first DU for relay to the UE, a handover command indicating the second DU and an instruction to perform a handover procedure from the first DU to the second DU based on the selection of the second DU.

[0261] Additionally or alternatively, the communications manager 1120 may support wireless communications at the first DU according to examples disclosed herein. For example, the communications manager 1120 may be configured as, or may otherwise support, a means for communicating a set of service messages between the UE and a set of core network services of a service-based network that are active at the UE. The communications manager 1120 may be configured as, or may otherwise support, a means for transmitting a message associated with fulfillment of a trigger condition for a handover procedure at the UE to a core network mobility service of the set of core network services. The communications manager 1120 may be configured as, or may otherwise support, a means for receiving, based on the message, a handover command from the core network mobility service indicating a second DU that supports at least one core network service of the set of core network services that are active at the UE. The communications manager 1120 may be configured as, or may otherwise support, a means for transmitting a handover command to the UE, the handover command including instructions for the UE to perform a handover procedure from the first DU to the second DU.

[0262] Additionally or alternatively, the communications manager 1120 may support wireless communications at the second DU according to embodiments disclosed herein. For example, the communications manager 1120 may be configured as, or otherwise support, a means for receiving a handover request associated with a handover procedure at the UE from a core network mobility service of the service-based network from a first DU to a second DU. The communications manager 1120 may be configured as, or otherwise support, a means 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 of a set of core network services that is active at the UE and supported by the second DU. The communications manager 1120 may be configured as, or otherwise support, a means for communicating with the UE based on the handover request and the ACK message. The communications manager 1120 may be configured as, or otherwise support, a means for sending a second message to the core network mobility service indicating completion of the handover procedure based on communicating with the UE.

[0263] By including or configuring the communications manager 1120 in accordance with examples described herein, the device 1105 (e.g., a processor controlling or otherwise coupled to the receiver 1110, the transmitter 1115, the communications manager 1120, or a combination thereof) may support techniques that enable the UE 115 to perform handover procedures between DUs 165 and / or network entities 105 of a services-based wireless system while minimizing disruption to active core network services at the UE 115. In particular, aspects of the present disclosure support techniques that enable the UE 115 to perform handover procedures 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 interruptions to communications conducted using core network services, thereby preventing the UE 115 from having to continually re-establish communications using core network services. In this regard, the techniques described herein may reduce signaling associated with a UE 115 that has subscribed to core network services, reducing interruptions and improving the overall user experience.

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

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

[0266] The transmitter 1215 may provide a means for outputting (e.g., transmitting, providing, conveying, 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 protocol stacks). In some examples, the transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by transmitting 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 within a transceiver, which may include or be coupled to a modem.

[0267] Device 1205, or various components thereof, may be an example of a means for implementing various aspects of the techniques for connected-state mobility in service-based wireless systems described herein. For example, communications manager 1220 may include a handover procedure 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 communications manager 1265, or any combination thereof. Communications manager 1220 may be an example of an aspect of communications manager 1120 described herein. In some examples, communications manager 1220, or various components thereof, may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, the communications manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both, to obtain information, output information, or perform various other operations described herein.

[0268] The communications manager 1220 may support wireless communications in core network mobility services according to examples disclosed herein. The handover procedure manager 1225 may be configured as, or may otherwise support, a means for receiving, from a first DU configured to communicate with the UE, a message associated with fulfillment of a trigger condition for a handover procedure in the UE. The target cell selection manager 1230 may be configured as, or may otherwise support, a means for selecting, based on the message, 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 in the UE from a set of multiple core network services of the service-based network. The handover command transmission manager 1235 may be configured as, or may otherwise support, a means for transmitting, to the first DU for relay to the UE, a handover command indicating the second DU and an instruction to perform a handover procedure from the first DU to the second DU based on the selection of the second DU.

[0269] Additionally or alternatively, the communications manager 1220 may support wireless communications at the first DU according to examples disclosed herein. The service message relay manager 1240 may be configured as, or may otherwise support, a means for communicating a set of service messages between the UE and a set of core network services of the service-based network that are active at the UE. The handover procedure manager 1225 may be configured as, or may otherwise support, a means for sending, to a core network mobility service of the set of core network services, a message associated with fulfillment of a trigger condition for a handover procedure at the UE. The handover command reception manager 1245 may be configured as, or may otherwise support, a means for receiving, based on the message, from the core network mobility service, a handover command indicating a second DU that supports at least one core network service of the set of core network services that are active at the UE. The handover request transmission manager 1250 may be configured as or may otherwise support a means for transmitting a handover command to the UE, the handover command including instructions for the UE to perform a handover procedure from a first DU to a second DU.

[0270] Additionally or alternatively, the communications manager 1220 may support wireless communications at the second DU according to embodiments disclosed herein. The handover request reception manager 1255 may be configured as, or may otherwise support, a means for receiving a handover request associated with a handover procedure at the UE from a core network mobility service of the service-based network, from the first DU to the second DU. The ACK message transmission manager 1260 may be configured as, or may otherwise support, a means for transmitting an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service of a set of core network services that is active at the UE and supported by the second DU. The UE communications manager 1265 may be configured as, or may otherwise support, a means for communicating with the UE based on the handover request and the ACK message. The handover procedure manager 1225 may be configured as, or may otherwise support, a means for transmitting a second message to the core network mobility service indicating completion of the handover procedure based on communicating with the UE.

[0271] 13 shows a block diagram 1300 of a communications manager 1320 supporting techniques for connected state mobility in service-based wireless systems in accordance with one or more aspects of the present disclosure. Communications manager 1320 may be an example of aspects of communications manager 1120, communications manager 1220, or both, as described herein. Communications manager 1320, or various components thereof, may be an example of a means for implementing various aspects of the techniques for connected state mobility in service-based wireless systems described herein. For example, communications manager 1320 may include a handover procedure manager 1325, a target cell selection manager 1330, a handover command transmission manager 1335, a service message relay manager 1340, a handover command reception manager 1345, a handover request transmission manager 1350, a handover request reception manager 1355, an ACK message transmission manager 1360, a UE communications manager 1365, an ACK message reception manager 1370, a capability information reception manager 1375, a capability information transmission manager 1380, a communications tunnel manager 1385, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0272] The communications manager 1320 may support wireless communications in core network mobility services according to examples disclosed herein. The handover procedure manager 1325 may be configured as, or may otherwise support, a means for receiving, from a first DU configured to communicate with the UE, a message associated with fulfillment of a trigger condition for a handover procedure in the UE. The target cell selection manager 1330 may be configured as, or may otherwise support, a means for selecting, based on the message, 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 in the UE from a set of multiple core network services of the service-based network. The handover command transmission manager 1335 may be configured as, or may otherwise support, a means for transmitting, to the first DU for relay to the UE, a handover command indicating the second DU and an instruction to perform a handover procedure from the first DU to the second DU based on the selection of the second DU.

[0273] In some examples, the handover request sending manager 1350 may be configured as or may otherwise support a means for sending a handover request to the second DU based on the message. In some examples, the ACK message receiving manager 1370 may be configured as or may otherwise support a means for receiving an ACK message from the second DU based on the handover request, and the sending of the handover command is based on the ACK message.

[0274] In some examples, the handover command transmission manager 1335 may be configured as or otherwise support a means for transmitting an indication of the set of core network services that are active in the UE via the handover request, and the ACK message is based on the set of core network services that are active in the UE.

[0275] In some examples, the ACK message reception manager 1370 may be configured as or otherwise support a means for receiving, via the ACK message, an indication of at least one core network service supported by the second DU, and sending the handover command is based on receiving the indication of the at least one core network service.

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

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

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

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

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

[0281] In some examples, the handover procedure manager 1325 may be configured or otherwise support a means for receiving a second message from the second DU indicating completion of the handover procedure, and in some examples, the UE communications manager 1365 may be configured or otherwise support a means for communicating with the UE via the second DU based on the second message.

[0282] In some examples, the handover procedure manager 1325 may be configured as or otherwise support a means for transmitting a measurement configuration indicating one or more trigger conditions, including the trigger condition, to the first DU for relay to the UE, and receiving the message is based on the measurement configuration.

[0283] Additionally or alternatively, the communications manager 1320 may support wireless communications at the first DU according to examples disclosed herein. The service message relay manager 1340 may be configured as, or may otherwise support, a means for communicating a set of service messages between the UE and a set of core network services of the service-based network that are active at the UE. In some examples, the handover procedure manager 1325 may be configured as, or may otherwise support, a means for sending a message associated with satisfaction of a trigger condition for a handover procedure at the UE to a core network mobility service of the set of core network services. The handover command reception manager 1345 may be configured as, or may otherwise support, a means for receiving, based on the message, a handover command from the core network mobility service indicating a second DU that supports at least one core network service of the set of core network services that are active at the UE. The handover request transmission manager 1350 may be configured as or otherwise support a means for transmitting a handover command to the UE, the handover command including instructions for the UE to perform a handover procedure from a first DU to a second DU.

[0284] In some examples, the capability information transmission manager 1380 may be configured as or otherwise support a means for transmitting capability information associated with the UE to a core network mobility service, an additional core network service of a set of multiple core network services, or both, and receiving a handover command is based on the capability information.

[0285] In some examples, the handover procedure manager 1325 may be configured as or otherwise support a means for sending an indication of the set of core network services that are active in the UE to the core network mobility service, an additional core network service of the set of core network services, or both, and receiving the handover command is based on having sent the indication of the set of core network services that are active in the UE.

[0286] In some examples, the communication tunnel manager 1385 may be configured as or may otherwise support a 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 as or may otherwise support a means for receiving a second message for the UE prior to completion of the handover procedure. In some examples, the service message relay manager 1340 may be configured as or may otherwise support a means for transmitting one or more packets associated with the second message to the second DU via the communication tunnel for relay to the UE.

[0287] In some examples, the handover procedure manager 1325 may be configured as or otherwise support a means for transmitting, via a 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 serving cells supported by the second DU, and receiving the handover command is based on having transmitted the indication of the set of multiple candidate DUs.

[0288] In some examples, the handover command reception manager 1345 may be configured as or may otherwise support a means for receiving, via a handover command, an indication of at least one core network service supported by the second DU. In some examples, the handover command transmission manager 1335 may be configured as or may otherwise support a means for transmitting, via a handover command, to the UE, an indication of at least one core network service supported by the second DU.

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

[0290] In some examples, the handover procedure manager 1325 may be configured with or otherwise support a means for receiving a measurement report, a second message indicating a trigger condition, or both, from the UE based on the measurement configuration, and wherein sending the message associated with satisfaction of the trigger condition is based on receiving the measurement report, the second message indicating the trigger condition, or both.

[0291] Additionally or alternatively, the communications manager 1320 may support wireless communications at the second DU according to embodiments disclosed herein. The handover request reception manager 1355 may be configured as, or may otherwise support, a means for receiving a handover request associated with a handover procedure at the UE from a core network mobility service of the service-based network, from the first DU to the second DU. The ACK message transmission manager 1360 may be configured as, or may otherwise support, a means for transmitting an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service of a set of core network services that is active at the UE and supported by the second DU. The UE communications manager 1365 may be configured as, or may otherwise support, a means for communicating with the UE based on the handover request and the ACK message. In some examples, the handover procedure manager 1325 may be configured as, or may otherwise support, a means for transmitting a second message to the core network mobility service indicating completion of the handover procedure based on communicating with the UE.

[0292] In some examples, the handover request reception manager 1355 may be configured as or otherwise support a means for receiving, via the handover request, an indication of a set of core network services that are active in the UE, and sending the ACK message is based on the set of core network services that are active in the UE.

[0293] In some examples, the communication tunnel manager 1385 may be configured as or may otherwise support a means for establishing 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 as or may otherwise support a means for receiving, from the first DU via the communication tunnel, one or more data packets associated with a second message for the UE prior to completion of the handover procedure. In some examples, the service message relay manager 1340 may be configured as or may otherwise support a means for transmitting, to the UE, one or more data packets associated with the second message based on receiving the one or more data packets via the communication tunnel.

[0294] In some examples, the ACK message transmission manager 1360 may be configured as or otherwise support a means for transmitting a set of communication parameters for communication between the UE and the second DU to the core network mobility service via an ACK message, and communicating with the UE is based on the set of communication parameters.

[0295] 14 shows a diagram of a system 1400 including a device 1405 supporting techniques for connected state mobility in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 as described herein, or may 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 via one or more wired interfaces, one or more wireless interfaces, or a combination thereof. The device 1405 may include components supporting outputting and obtaining communications, such as a communications manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, code 1430, and a processor 1435. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

[0296] 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 that may be capable of transmitting or receiving (e.g., simultaneously) wireless transmissions. The transceiver 1410 may also include a modem for modulating signals, providing the modulated signals for transmission (e.g., by one or more antennas 1415 or by a wired transmitter), receiving the modulated signals (e.g., from one or more antennas 1415 or from a wired receiver), and demodulating the signals. In some implementations, the transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled with one or more antennas 1415 configured to support various receive or acquisition operations, or one or more interfaces coupled with one or more antennas 1415 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1410 may include or be configured to couple to one or more processors or memory components 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., the processor 1435, or the memory 1425, or both) may be included on a chip or chip assembly installed in the device 1405.In some examples, the transceiver may be operable to support communication over one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link, fronthaul communication link 168).

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

[0298] The 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the 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 the processor 1435. The processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to cause the device 1405 to perform various functions (e.g., functions or tasks supporting techniques for connected state mobility in service-based wireless systems). For example, the device 1405 or a component of the device 1405 may include the processor 1435 and the memory 1425 coupled to the processor 1435, where the processor 1435 and the memory 1425 are configured to perform various functions described herein. Processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functionality (e.g., by executing code 1430) to perform the functionality of device 1405. Processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored on device 1405 (e.g., in memory 1425). In some implementations, processor 1435 may be a component of a processing system. A processing system may generally refer to a system or set of machines or components that receives inputs, processes the inputs, and generates a set of outputs (e.g., that may be passed to other systems or components of device 1405).For example, the processing system of device 1405 may refer to a system that includes various other components or subcomponents of device 1405, such as processor 1435, or transceiver 1410, or communications manager 1420, or other components or combinations of components of device 1405. The processing system of device 1405 may interface with other components of device 1405 and may process information (e.g., input or signals) received from other components or output information to other components. For example, a chip or modem of device 1405 may include a processing system and one or more interfaces for outputting information, acquiring 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 acquire information, or the same interface configured to output information and acquire information, among other implementations. In some implementations, the one or more interfaces refer to an interface between the processing system and a transmitter of the chip or modem, such that device 1405 may transmit information output from the chip or modem. Additionally or alternatively, in some implementations, the one or more interfaces refer to an interface between a processing system and a receiver of a chip or modem, such that the device 1405 obtains information or signal input, and that information can be passed to the processing system. Those skilled in the art will readily recognize that the first interface can also obtain information or signal input, and the second interface can also output information or signal output.

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

[0300] In some examples, the communications manager 1420 may manage aspects of communications with the core network (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1420 may manage the forwarding of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1420 may manage communications with other network entities 105 and may include a controller or scheduler for cooperating with the other network entities 105 to control communications with the UEs 115. In some examples, the communications manager 1420 may support an X2 interface within LTE / LTE-A wireless communications network technologies to provide communications between network entities 105.

[0301] The communications manager 1420 may support wireless communications in core network mobility services according to examples disclosed herein. For example, the communications manager 1420 may be configured as, or may otherwise support, a means for receiving, from a first DU configured to communicate with the UE, a message associated with fulfillment of a trigger condition for a handover procedure in the UE. The communications manager 1420 may be configured as, or may otherwise support, a means for selecting, based on the message, 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 in the UE from a set of multiple core network services of the service-based network. The communications manager 1420 may be configured as, or may otherwise support, a means for transmitting, to the first DU for relay to the UE, a handover command indicating the second DU and an instruction to perform a handover procedure from the first DU to the second DU based on the selection of the second DU.

[0302] Additionally or alternatively, the communications manager 1420 may support wireless communications at the first DU according to examples disclosed herein. For example, the communications manager 1420 may be configured as, or may otherwise support, a means for communicating a set of service messages between the UE and a set of core network services of a service-based network that are active at the UE. The communications manager 1420 may be configured as, or may otherwise support, a means for transmitting a message associated with satisfaction of a trigger condition for a handover procedure at the UE to a core network mobility service of the set of core network services. The communications manager 1420 may be configured as, or may otherwise support, a means for receiving, based on the message, a handover command from the core network mobility service indicating a second DU that supports at least one core network service of the set of core network services that are active at the UE. The communications manager 1420 may be configured as, or may otherwise support, a means for transmitting a handover command to the UE, the handover command including instructions for the UE to perform a handover procedure from the first DU to the second DU.

[0303] Additionally or alternatively, the communications manager 1420 may support wireless communications at the second DU according to embodiments disclosed herein. For example, the communications manager 1420 may be configured as, or otherwise support, a means for receiving a handover request associated with a handover procedure at the UE from a core network mobility service of the service-based network, from the first DU to the second DU. The communications manager 1420 may be configured as, or otherwise support, a means for transmitting an ACK message to the core network mobility service based on the handover request, the ACK message indicating at least one core network service of a set of core network services that is active at the UE and supported by the second DU. The communications manager 1420 may be configured as, or otherwise support, a means for communicating with the UE based on the handover request and the ACK message. The communications manager 1420 may be configured as, or otherwise support, a means for transmitting a second message to the core network mobility service indicating completion of the handover procedure based on communicating with the UE.

[0304] By including or configuring the communications manager 1420 according to examples described herein, the device 1405 may support techniques that enable the UE 115 to perform handover procedures between DUs 165 and / or network entities 105 of a service-based wireless system while minimizing disruption to active core network services at the UE 115. In particular, aspects of the present disclosure support techniques that enable the UE 115 to perform handover procedures to a target DU / target network entity that supports at least some of the active core network services at the UE 115. Accordingly, aspects of the present disclosure may reduce interruptions to communications conducted using core network services, thereby preventing the UE 115 from having to continually re-establish communications using core network services. In this regard, the techniques described herein may reduce signaling associated with a UE 115 that subscribes to core network services, reducing interruptions and improving the overall user experience.

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

[0306] FIG. 15 illustrates a flowchart of a method 1500 supporting techniques for connected state mobility in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1500 may be performed by a UE 115 as described with reference to FIGS. 1-10. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functionality. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functionality.

[0307] At 1505, the method may include communicating with the first DU a set of service messages associated with a set of core network services provided by the service-based network and active at the UE. The operations of 1505 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a service message communication manager 925 as described with reference to FIG. 9.

[0308] At 1510, the method may include receiving, via the first DU, from one core network mobility service of the set of core network services, a measurement configuration indicating one or more trigger conditions associated with a handover procedure at the UE. The operations of 1510 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a measurement configuration manager 930 as described with reference to FIG. 9.

[0309] At 1515, the method may include transmitting a second message to the first DU for relay to the core network mobility service, the second message indicating satisfaction of one of the one or more trigger conditions. The operations of 1515 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed by a measurement configuration manager 930 as described with reference to FIG. 9.

[0310] At 1520, the method may include receiving, based on satisfaction of the trigger condition, a handover command from the core network mobility service via the first DU, the handover command indicating a second DU that supports at least one core network service of the set of core network services active at the UE. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be performed by a handover command reception manager 935 as described with reference to FIG. 9.

[0311] At 1525, the method may include communicating with the second DU based on receiving the handover command. The operations of 1525 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1525 may be performed by a service message communication manager 925 as described with reference to FIG. 9.

[0312] FIG. 16 illustrates a flowchart of a method 1600 supporting techniques for connected-state mobility in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1600 may be implemented by a network entity or components thereof as described herein. For example, the operations of method 1600 may be performed by a network entity as described with reference to FIGS. 1-6 and 11-14. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functionality. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functionality.

[0313] At 1605, the method may include receiving, from a first DU configured to communicate with the UE, a message associated with satisfaction of a trigger condition for a handover procedure in the UE. The operations of 1605 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a handover procedure manager 1325 as described with reference to FIG. 13.

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

[0315] At 1615, the method may include transmitting, to the first DU for relay to the UE, a handover command indicating the second DU based on the selection of the second DU and instructions to perform a handover procedure from the first DU to the second DU. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed by a handover command transmission manager 1335 as described with reference to FIG. 13.

[0316] FIG. 17 illustrates a flowchart of a method 1700 supporting techniques for connected-state mobility in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1700 may be implemented by a network entity or components thereof as described herein. For example, the operations of method 1700 may be performed by a network entity such as those described with reference to FIGS. 1-6 and 11-14. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functionality. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functionality.

[0317] At 1705, the method may include communicating a set of service messages between the UE and a set of core network services of the service-based network that are active at the UE. The operations of 1705 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a service message relay manager 1340 as described with reference to FIG. 13.

[0318] At 1710, the method may include transmitting, to a core network mobility service of the set of core network services, a message associated with satisfaction of a trigger condition for a handover procedure at the UE. The operations of 1710 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a handover procedure manager 1325 as described with reference to FIG. 13.

[0319] At 1715, the method may include receiving, based on the message, from the core network mobility service, a handover command indicating a second DU that supports at least one core network service of the set of core network services that are active in the UE. The operation of 1715 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1715 may be performed by the handover command reception manager 1345 as described with reference to FIG. 13.

[0320] At 1720, the method may include transmitting a handover command to the UE, the handover command including instructions for the UE to perform a handover procedure from the first DU to the second DU. The operations of 1720 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1720 may be performed by a handover request transmission manager 1350 as described with reference to FIG. 13.

[0321] FIG. 18 illustrates a flowchart of a method 1800 supporting techniques for connected-state mobility in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1800 may be implemented by a network entity or components thereof as described herein. For example, the operations of method 1800 may be performed by a network entity such as those described with reference to FIGS. 1-6 and 11-14. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functionality. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functionality.

[0322] At 1805, the method may include receiving, from a core network mobility service of the service-based network, a handover request associated with a handover procedure in the UE from a first DU to a second DU. The operations of 1805 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a handover request receive manager 1355 as described with reference to FIG. 13.

[0323] At 1810, the method may include transmitting an ACK message to a core network mobility service based on the handover request, the ACK message indicating at least one core network service of the set of 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 disclosed herein. In some examples, aspects of the operations of 1810 may be performed by an ACK message transmission manager 1360 as described with reference to FIG. 13.

[0324] At 1815, the method may include communicating with the UE based on the handover request and ACK message. The operations of 1815 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1815 may be performed by the UE communications manager 1365 as described with reference to FIG. 13.

[0325] At 1820, the method may include, based on communicating with the UE, sending a second message to the core network mobility service indicating completion of the handover procedure. The operation of 1820 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 1820 may be performed by the handover procedure manager 1325 as described with reference to FIG. 13.

[0326] The following provides a summary of aspects of the present disclosure.

[0327] Aspect 1: A method for wireless communication in a UE, the method comprising: communicating a plurality of service messages with a first DU, the plurality of service messages being provided by a service-based network and associated with a plurality of core network services that are active in the UE; receiving, via the first DU, from a core network mobility service of the plurality of core network services, a measurement configuration indicating one or more trigger conditions associated with a handover procedure in the UE; transmitting a second message to the first DU for relay to the core network mobility service, the second message indicating satisfaction of one of the one or more trigger conditions; receiving, at least in part, a handover command from the core network mobility service via the first DU based at least in part on the satisfaction of the trigger condition, the handover command indicating a second DU that supports at least one core network service of the plurality of core network services that are active in the UE; and communicating with the second DU based at least in part on receiving the handover command.

[0328] Aspect 2: The method of aspect 1, further comprising: transmitting capability information associated with the UE to the first DU, a core network mobility service, an additional core network service among the plurality of core network services, or any combination thereof; and receiving the handover command is based at least in part on the capability information.

[0329] Aspect 3: The method of aspect 1 or 2, further comprising receiving, via a 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 communicating with the second DU is based at least in part on the cell identifier and the set of communication parameters.

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

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

[0332] Aspect 6: A method for wireless communication in core network mobility services, the method including: receiving, from a first DU in wireless communication with a UE, a message associated with satisfaction of a trigger condition for a handover procedure in the UE; selecting, based at least in part on the message, a second DU from a plurality of candidate DUs based at least in part on the second DU being configured to support at least one core network service, the core network service being active in the UE, of a plurality of core network services of a service-based network; and transmitting, to the first DU for relay to the UE, a handover command indicating the second DU based at least in part on the selection of the second DU, and instructions to perform a handover procedure from the first DU to the second DU.

[0333] Aspect 7: The method of aspect 6, further including: sending a handover request to a 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 handover request, wherein sending the handover command is based at least in part on the ACK message.

[0334] Aspect 8: The method of aspect 7, further comprising: sending an indication of a plurality of core network services that are active in the UE via the handover request, wherein the ACK message is based at least in part on the plurality of core network services that are active in the UE.

[0335] Aspect 9: The method of aspect 7 or 8, further comprising: receiving, via the ACK message, an indication of at least one core network service supported by the second DU; and sending the handover command is based at least in part on receiving the indication of the at least one core network service.

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

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

[0338] Aspect 12: The method of any 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.

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

[0340] Aspect 14: The method of any of aspects 6 to 13, wherein selecting the second DU includes selecting a serving cell supported by the second DU, and the handover command includes a cell identifier associated with the selected serving cell.

[0341] Aspect 15: The method of any of aspects 6 to 14, further including: receiving a second message from the second DU indicating completion of the handover procedure; and communicating with the UE via the second DU based at least in part on the second message.

[0342] Aspect 16: The method of any of aspects 6 to 15, further comprising: transmitting a measurement configuration indicating one or more trigger conditions, including the trigger condition, to the first DU for relay to the UE, wherein receiving the message is based at least in part on the measurement configuration.

[0343] Aspect 17: A method for wireless communication in a first DU, the method comprising: communicating a plurality of service messages between a UE and a plurality of core network services of a service-based network that are active in the UE; sending a message associated with satisfaction of a trigger condition for a handover procedure in the UE to a core network mobility service among the plurality of core network services; receiving a handover command from the core network mobility service based at least in part on the message, the handover command indicating a second DU that supports at least one core network service among the plurality of core network services that are active in the UE; and sending the handover command to the UE, the handover command including instructions for the UE to perform a handover procedure from the first DU to the second DU.

[0344] Aspect 18: The method of aspect 17, further comprising: transmitting capability information associated with the UE to a core network mobility service, an additional core network service among the plurality of core network services, or both; and receiving the handover command is based at least in part on the capability information.

[0345] Aspect 19: The method of aspect 17 or 18, further comprising: sending an indication of the plurality of core network services that are active in the UE to a core network mobility service, an additional core network service among the plurality of core network services, or both, wherein receiving the handover command is based at least in part on sending the indication of the plurality of core network services that are active in the UE.

[0346] Aspect 20: The method of any of aspects 17-19, further including: establishing a communication tunnel with a second DU based at least in part on the handover command; receiving a second message for the UE prior to completion of the handover procedure; and transmitting one or more packets to the second DU via the communication tunnel for relay to the UE based at least in part on receiving the second message.

[0347] Aspect 21: The method of any of aspects 17 to 20, further comprising: transmitting, via a message, an indication of a plurality of candidate DUs, including the second DU, and one or more cell identifiers associated with one or more serving cells supported by the second DU; and receiving the handover command is based at least in part on transmitting the indication of the plurality of candidate DUs.

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

[0349] Aspect 23: The method of any of aspects 17 to 22, further comprising: receiving, from a core network mobility service, a measurement configuration indicating one or more trigger conditions, including the trigger condition; and transmitting the measurement configuration to the UE, wherein transmitting the message associated with satisfaction of the trigger condition is based at least in part on the measurement configuration.

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

[0351] Aspect 25: A method for wireless communication in a second DU, the method comprising: receiving, from a core network mobility service of a service-based network, a handover request associated with a handover procedure in a UE from a first DU to a second DU; sending an ACK message to the core network mobility service based at least in part on the handover request, the ACK message indicating at least one core network service among a plurality of core network services that is active in the UE and supported by the second DU; communicating with the UE based at least in part 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 at least in part on communicating with the UE.

[0352] Aspect 26: The method of aspect 25, further comprising receiving, via the handover request, an indication of a plurality of core network services that are active in the UE, wherein sending the ACK message is based at least in part on the plurality of core network services that are active in the UE.

[0353] Aspect 27: The method of aspect 25 or 26, further including: establishing a communication tunnel with the first DU based at least in part 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 prior to completion of the handover procedure; and transmitting one or more data packets associated with the second message to the UE based at least in part on receiving the one or more data packets via the communication tunnel.

[0354] Aspect 28: The method of any of aspects 25 to 27, further comprising: transmitting a set of communication parameters for communication between the UE and the second DU to a core network mobility service via an ACK message, wherein communicating with the UE is based at least in part on the set of communication parameters.

[0355] Aspect 29: An apparatus for wireless communication in a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform a method described in any of aspects 1 to 5.

[0356] Aspect 30: An apparatus for wireless communication in a UE, comprising: at least one means for performing the method of any of aspects 1-5.

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

[0358] Aspect 32: An apparatus for wireless communication in core network mobility services, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform a method described in any of aspects 6-16.

[0359] Aspect 33: An apparatus for wireless communication in core network mobility services, the apparatus comprising at least one means for performing the method described in any of aspects 6-16.

[0360] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication in core network mobility services, the code including instructions executable by a processor for performing a method as described in any of aspects 6-16.

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

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

[0363] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication in a first DU, the code including instructions executable by a processor for performing a method described in any of aspects 17 to 24.

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

[0365] Example 39: An apparatus for wireless communication in a second DU, comprising at least one means for performing the method of any of Examples 25 to 28.

[0366] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication in a second DU, the code including instructions executable by a processor for performing a method described in any of aspects 25 to 28.

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

[0368] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described as examples, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used throughout much of the description, the techniques described herein may be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR. 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.

[0369] The information and signals described herein may be represented using any of a wide variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0370] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an 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 alternatively, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0371] 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 on or transmitted using one or more instructions or code on 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, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that portions of the functions are performed at different physical locations.

[0372] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one location to another. Non-transitory storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. A disk may reproduce data magnetically, and a disc may reproduce data optically using a laser. Combinations of the above are also included within the scope of computer-readable media.

[0373] As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, 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). Also, the phrase "based on" as used herein should not be construed as referring to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" is to be interpreted the same as the phrase "based at least in part on."

[0374] The terms "determine" or "determining" encompass various actions, and thus "determining" can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database, or other data structure), ascertaining, etc. "Determining" can also include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. "Determining" can also include resolving, obtaining, selecting, choosing, establishing, and other similar acts.

[0375] In the accompanying figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes between the similar components. If only a first reference label is used herein, the description is applicable to any of the similar components having the same first reference label, regardless of a second reference label, or other subsequent reference label.

[0376] The descriptions set forth herein with reference to the accompanying drawings describe exemplary configurations and do not necessarily represent all examples that may be implemented or fall within the scope of the claims. As used herein, the term "example" means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0377] The description herein is provided to enable any person skilled in the art to make or use the disclosure. Various modifications of the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication in core network mobility services, Receiving a message from a first distributed unit configured to communicate with a user device (UE) associated with the fulfillment of a trigger condition for a handover procedure in the UE, Based at least in part on the aforementioned message, and at least in part on the fact that the second distributed unit is configured to support at least one core network service among a plurality of core network services of a service-based network that is active in the UE, the second distributed unit is selected from a plurality of candidate distributed units, To relay to the UE, the first distributed unit is to transmit a handover command indicating the second distributed unit, and an instruction to perform the handover procedure from the first distributed unit to the second distributed unit, at least partially based on the selection of the second distributed unit. Methods that include...

2. Sending a handover request to the second distributed unit based at least in part on the aforementioned message, Based at least partially on the handover request, an acknowledgment message is received from the second distributed unit, It further includes, Sending the aforementioned handover command is at least partially based on the aforementioned acknowledgment message, The method further includes transmitting instructions for the plurality of core network services that are active in the UE via the handover request, wherein the acknowledgment message is at least partially based on the plurality of core network services that are active in the UE, and / or The method according to claim 1, further comprising receiving instructions for the at least one core network service supported by the second distributed unit via the acknowledgment message, wherein sending the handover command is at least partially based on receiving the instructions for the at least one core network service.

3. Further includes receiving capability information associated with the UE, The method according to claim 1, wherein the selection of the second distributed unit from the plurality of candidate distributed units is at least in part based on the capability information, the capability information is received from core network capability services included in the plurality of core network services.

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

5. The further includes receiving instructions for the plurality of candidate distribution units via the message, The method according to claim 1, wherein the selection of the second distribution unit is at least in part based on receiving the instructions for the plurality of candidate distribution units.

6. Selecting the second distributed unit means This includes selecting a serving cell to be supported by the second distributed unit, The method according to claim 1, wherein the handover command includes a cell identifier associated with the selected serving cell.

7. Receiving a second message from the second distributed unit indicating the completion of the handover procedure, Communicating with the UE via the second distributed unit based at least in part on the second message, The method according to claim 1, further comprising:

8. The further includes transmitting a measurement configuration indicating one or more trigger conditions, including the trigger condition, to the first distributed unit for relaying to the UE, The method according to claim 1, wherein receiving the aforementioned message is at least partially based on the measurement configuration.

9. A method for wireless communication in a first distributed unit, The communication of multiple service messages between a user device (UE) and multiple core network services of a service-based network that are active in the UE, Sending a message to the core network mobility service among the multiple core network services associated with the fulfillment of the trigger condition for the handover procedure in the UE, Based at least in part on the aforementioned message, a handover command is received from the core network mobility service indicating a second distributed unit that supports at least one of the multiple core network services active in the UE, Sending the handover command to the UE, wherein the handover command includes instructions for the UE to perform the handover procedure from the first distributed unit to the second distributed unit, Methods that include...

10. The method of claim 9, further comprising transmitting capability information associated with the UE to the core network mobility service, an additional core network service among the plurality of core network services, or both, wherein receiving the handover command is at least partially based on the capability information.

11. Further includes transmitting instructions for the multiple core network services that are active in the UE to the core network mobility service, an additional core network service among the multiple core network services, or both. The method according to claim 9, wherein receiving the handover command is at least in part based on transmitting the instructions for the multiple core network services that are active in the UE.

12. Based at least partially on the handover command, establish a communication tunnel with the second distributed unit, Receiving a second message for the UE before the completion of the handover procedure, Based at least in part on having received the second message, one or more packets are transmitted to the second distributed unit via the communication tunnel for relaying to the UE, The method according to claim 9, further comprising:

13. The transmission via the message includes instructions for a plurality of candidate distributed units, including the second distributed unit, and one or more cell identifiers associated with one or more serving cells supported by the second distributed unit. The method according to claim 9, wherein receiving the handover command is at least in part based on having transmitted the instructions for the plurality of candidate distribution units.

14. The handover command receives instructions for the at least one core network service supported by the second distributed unit, The handover command transmits the instructions for the at least one core network service supported by the second distributed unit to the UE, The method according to claim 9, further comprising:

15. Receiving a measurement configuration from the core network mobility service that includes one or more trigger conditions, including the trigger condition, The measurement configuration is transmitted to the UE, The transmission of the message associated with the satisfaction of the trigger condition is at least partially based on the measurement configuration, The method further includes receiving a measurement report, a second message indicating the trigger condition, or both, from the UE, at least in part, based on the measurement configuration. The method according to claim 9, wherein transmitting the message associated with the satisfaction of the trigger condition is at least in part based on receiving the measurement report, the second message indicating the trigger condition, or both.

Images