Techniques for service status in service-based wireless system

Abstract

Methods, systems, and devices for wireless communication are described. In the context of a service-based wireless system, a user equipment (UE) may communicate with one or more core network services provided by a service-based network, where the respective core network services are in one of an active state, an inactive state, or an unconnected state at the UE. The UE may be configured to maintain a service context for communicating with a core network service in an active or inactive state at the UE, wherein signaling between the UE and each respective core network traffic may be used to activate or deactivate the respective core network service at the UE between the active and inactive states. By maintaining a service context for an inactive core network service, a UE can quickly and efficiently resume communication with a core network service according to a stored service context when activating the core network service.

Description

Cross-references

[0001] This patent application claims priority to U.S. patent application No. 17 / 948,041, filed by Gholmieh et al. on September 19, 2022, and entitled “TECHNIQUES FOR SERVICE STATES IN A SERVICE-BASED WIRELESS SYSTEM,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following relates to wireless communications, including techniques for service status in a service-based wireless system. Background Art

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

[0004] In the context of a service-based wireless system, different core network services provided by the service-based network may be in different activation or service states (e.g., active state, inactive state, unconnected state) at the UE. For example, a first core network service may be in an active state, while a second core network service may be in an inactive state. Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting technology for service status in a service-based wireless system. In general, various aspects of the present disclosure relate to signaling that can be used to selectively adjust the activation state (e.g., service state) of a core network service at a user equipment (UE). Specifically, various aspects of the present disclosure relate to signaling, configurations, and other mechanisms that enable a UE to subscribe to a core network service, exchange signaling indicating whether the corresponding core network service is in an active state or an inactive state, and maintain context information for both active and inactive core network services to facilitate rapid service reestablishment. In addition, various aspects of the present disclosure can enable network entities and the core network services themselves to maintain context information for performing communications associated with the corresponding core network services in order to facilitate efficient communications within a service-based wireless communication system.

[0006] A method of wireless communication at a UE is described. The method may include: transmitting a first service message with a first core network service provided by a service-based network via a distributed unit (DU), the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based on the first core network service being active at the UE; sending a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based on the second core network service being inactive at the UE; receiving a message indicating activation of the second core network service at the UE from the DU in response to the request; and transmitting a second service message with the second core network service via the DU according to the second service context based on the activation of the second core network service at the UE.

[0007] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor so that the device: transmits a first service message to a first core network service provided by a service-based network via a DU, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based on the first core network service being active at the UE; sends a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based on the second core network service being inactive at the UE; receives a message indicating activation of the second core network service at the UE from the DU in response to the request; and transmits a second service message to the second core network service via the DU according to the second service context based on the activation of the second core network service at the UE.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include a unit for transmitting a first service message to a first core network service provided by a service-based network via a DU, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based on the first core network service being active at the UE; a unit for sending a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based on the second core network service being inactive at the UE; a unit for receiving a message indicating activation of the second core network service at the UE from the DU in response to the request; and a unit for transmitting a second service message to the second core network service via the DU according to the second service context based on the activation of the second core network service at the UE.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: transmitting a first service message with a first core network service provided by a service-based network via a DU, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based on the first core network service being active at the UE; sending a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based on the second core network service being inactive at the UE; receiving a message indicating activation of the second core network service at the UE from the DU in response to the request; and transmitting a second service message with the second core network service via the DU according to the second service context based on the activation of the second core network service at the UE.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: based on the third core network service being in an unconnected state at the UE, sending a second request to the DU to establish a service with the third core network service; based on the second request, receiving a second message from the DU, the second message indicating a third service context for communicating with the third core network service; and based on converting the third core network service from the unconnected state to one of the active state or the inactive state at the UE, storing the third service context in a memory.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for transmitting, with the DU, a second message indicating deactivation of the first core network service at the UE, wherein the first service context may be maintained at the UE based on the deactivation.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the deactivation of the first core network service can be based on signaling from the first core network service, release of the wireless connection between the UE and the DU, radio link failure, failure of one or more messages sent from the UE to the first core network service, or any combination thereof.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: identifying that all core network services including the first core network service and the second core network service have been deactivated at the UE; and based on the identification, releasing the wireless connection with the DU.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending, via the request, a network address associated with the second core network service, a third service message associated with the second core network service, or both.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending a second request to the DU to activate a third core network service provided by the service-based network, the third core network service being associated with a third service context for communicating with the third core network service, wherein the third service context may be maintained at the UE based on the third core network service being in an inactive state at the UE; and receiving a second message from the DU indicating a failure in activation of the third core network service based on the second request.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: based on receiving the second message indicating that the activation of the third service context failed, deleting the third service context from a memory.

[0017] A method for wireless communication at a DU is described. The method may include: transmitting a first service message between a UE and a first core network service provided by a service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the DU based on the first core network service being in an active state at the UE; receiving a request to activate a second core network service provided by the service-based network at the UE from an inactive state to the active state, the second core network service being associated with a second service context for communicating with the second core network service; based on the request, sending a message to the UE indicating activation of the second core network service at the UE; and transmitting a second service message between the UE and the second core network service according to the second service context based on the activation of the second core network service at the UE.

[0018] A device for wireless communication at a DU is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor so that the device performs the following operations: transmitting a first service message between a UE and a first core network service provided by a service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the DU based on the first core network service being in an active state at the UE; receiving a request to activate a second core network service provided by the service-based network from an inactive state to an active state at the UE, the second core network service being associated with a second service context for communicating with the second core network service; based on the request, sending a message to the UE indicating activation of the second core network service at the UE; and based on the activation of the second core network service at the UE, transmitting a second service message between the UE and the second core network service according to the second service context.

[0019] Another apparatus for wireless communication at a DU is described. The apparatus may include a unit for transmitting a first service message between a UE and a first core network service provided by a service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the DU based on the first core network service being in an active state at the UE; a unit for receiving a request to activate a second core network service provided by the service-based network from an inactive state to an active state at the UE, the second core network service being associated with a second service context for communicating with the second core network service; a unit for sending a message indicating activation of the second core network service at the UE to the UE based on the request; and a unit for transmitting a second service message between the UE and the second core network service according to the second service context based on the activation of the second core network service at the UE.

[0020] A non-transitory computer-readable medium storing code for wireless communication at a DU is described. The code may include instructions executable by a processor to perform the following operations: transmitting a first service message between a UE and a first core network service provided by a service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the DU based on the first core network service being in an active state at the UE; receiving a request to activate a second core network service provided by the service-based network at the UE from an inactive state to the active state, the second core network service being associated with a second service context for communicating with the second core network service; based on the request, sending a message to the UE indicating activation of the second core network service at the UE; and transmitting a second service message between the UE and the second core network service according to the second service context based on the activation of the second core network service at the UE.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for transmitting, with the UE, the first core network service, or both, a second message indicating deactivation of the first core network service at the UE.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for reallocating a set of resources previously allocated for wireless communication between the UE and the first core network service to another UE, another core network service, or both, wherein the reallocation may be based on the second message indicating the deactivation of the first core network service.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the deactivation of the first core network service can be based on signaling from the first core network service, signaling from the UE, release of a wireless connection between the UE and the DU, a radio link failure, a failure of one or more messages sent from the UE to the first core network service, or any combination thereof.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: establishing a wireless connection with the UE based on a switching process from a second DU to the DU; and obtaining the first service context associated with the first core network service from the first core network service, another core network service, or both based on establishing the wireless connection, wherein transmitting the first service message may be based on obtaining the first service context.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: based on receiving the request, sending the request to the second core network service; and based on sending the request, receiving a confirmation of the activation of the second core network service from the second core network service, wherein sending the message indicating the activation of the second core network service may be based on the confirmation.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving, via the request, a network address associated with the second core network service, a third service message associated with the second core network service, or both, wherein sending the request to the second core network service may be based on receiving the network address, the third service message, or both.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a second request from the UE to activate a third core network service provided by the service-based network at the UE, the third core network service being associated with a third service context for communicating with the third core network service; and sending a second message to the UE indicating a failure in activation of the third core network service based on the second request.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: identifying that all core network services including the first core network service and the second core network service have been deactivated at the UE; and based on the identification, releasing the wireless connection with the UE.

[0029] A method for wireless communication at a core network service provided by a service-based network is described. The method may include: transmitting a first service message with a UE via a DU based on a first UE context for communicating with the UE, the first UE context being maintained at the core network service based on the core network service being active at the UE; receiving a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based on the message indicating the deactivation of the core network service at the UE; receiving a request to activate the core network service at the UE from the DU; and transmitting a second service message with the UE via the DU based on the first UE context and based on maintaining the first UE context in the memory and receiving the request to activate the core network service at the UE.

[0030] An apparatus for wireless communication at a core network service provided by a service-based network is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: transmitting a first service message with a UE via a DU based on a first UE context for communicating with the UE, the first UE context being maintained at the core network service based on the core network service being active at the UE; receiving a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based on the message indicating the deactivation of the core network service at the UE; receiving a request to activate the core network service at the UE from the DU; and transmitting a second service message with the UE via the DU based on the first UE context and based on maintaining the first UE context in the memory and receiving the request to activate the core network service at the UE.

[0031] Another apparatus for wireless communication at a core network service provided by a service-based network is described. The apparatus may include: a unit for transmitting a first service message with a UE via a DU based on a first UE context for communicating with the UE, the first UE context being maintained at the core network service based on the core network service being active at the UE; a unit for receiving a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based on the message indicating the deactivation of the core network service at the UE; a unit for receiving a request from the DU to activate the core network service at the UE; and a unit for transmitting a second service message with the UE via the DU based on the first UE context and based on maintaining the first UE context in the memory and receiving the request to activate the core network service at the UE.

[0032] A non-transitory computer-readable medium storing code for wireless communication at a core network service provided by a service-based network is described. The code may include instructions executable by a processor to: transmit a first service message with a UE via a DU based on a first UE context for communicating with the UE, the first UE context being maintained at the core network service based on the core network service being active at the UE; receive a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based on the message indicating the deactivation of the core network service at the UE; receive a request from the DU to activate the core network service at the UE; and transmit a second service message with the UE via the DU based on the first UE context and based on maintaining the first UE context in the memory and receiving the request to activate the core network service at the UE.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: based on the core network service being in an unconnected state at the second UE, receiving a second request from the DU to establish a service with the second UE; based on the second request, sending a second message to the DU indicating a first service context for communicating with the core network service; and based on sending the second message indicating the first service context, storing a second UE context associated with the second UE in a memory.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: based on a switching process from a second DU to the DU, receiving a second request for a first service context associated with wireless communication with the core network service from the DU, and based on the second request, sending the first service context associated with the core network service to the DU, wherein transmitting the first service message may be based on the first service context.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending a second message to the DU indicating deactivation of the core network service at the UE, wherein receiving the message indicating the deactivation may be based on the second message.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the deactivation of the first core network service can be based on signaling from the core network service, release of the wireless connection between the UE and the DU, radio link failure, failure of one or more messages sent from the UE to the core network service, or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 An example of a wireless communication system that supports techniques for service status in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0038] Figure 2 An example of a wireless communication system that supports techniques for service status in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0039] Figure 3 An example of a network architecture for techniques supporting service status in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0040] Figure 4 An example of a wireless communication system that supports techniques for service status in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0041] Figure 5 An example of activation state configuration of a technique for supporting service states in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0042] Figure 6An example of activation state configuration of a technique for supporting service states in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0043] Figure 7 An example of a process flow for a technique to support service status in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0044] Figure 8 and Fig. 9 A block diagram of a device is shown that supports techniques for service status in a service-based wireless system in accordance with one or more aspects of the present disclosure.

[0045] Fig.10 A block diagram of a communication manager is shown that supports techniques for service status in a service-based wireless system in accordance with one or more aspects of the present disclosure.

[0046] Fig.11 A diagram of a system including devices supporting techniques for service status in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0047] Fig.12 and Fig.13 A block diagram of a device supporting techniques for service status in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0048] Fig.14 A block diagram of a communication manager is shown that supports techniques for service status in a service-based wireless system in accordance with one or more aspects of the present disclosure.

[0049] Fig.15 A diagram of a system including devices supporting techniques for service status in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

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

[0051] Some wireless systems may exhibit a relatively vertical layered architecture that includes 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 several back-end (e.g., core network) devices associated with one or more functions of the system. Such a layered architecture may result in processing and other functions being performed at multiple devices (e.g., duplicated processing or capabilities across multiple back-end devices), resulting in wasted resources and excessive power consumption. In addition, the back-end architecture of some wireless systems may be owned and maintained by a small number of operators, which may make it difficult for other parties / entities to integrate with the system and may complicate the system's ability to provide customized services and functionality to wireless devices.

[0052] In contrast, 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) is connected to 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 would otherwise be performed by a few centralized backend components (e.g., in some systems) may be distributed across multiple core network services that may be hosted at different network addresses, such as in a cloud-based architecture. Thus, a UE in a service-based system is able to establish and maintain connections (e.g., "subscriptions") with different core network services or groups on an à la carte basis, where each core network service provides or provides a corresponding 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 within a service-based system may be able to select which core network services the UE will subscribe to based on the personalized characteristics or needs of the corresponding UE.

[0053] In some wireless systems, the RAN may be connected to a service-based network that provides various core network services, and may relay communications between the UE and the corresponding core network services. In this case, the UE may "subscribe" to different core network services, each of which may be in a different activation state (e.g., active state, inactive state, unconnected state) at the UE. For example, at the UE, the first core network service may be in an active state, the second core network service may be in an inactive state, and the third core network service may be in an unconnected state. The UE is able to actively perform communications with the core network services in an active state. In contrast, the UE may not be able to perform communications with the core network services in an inactive or unconnected state. However, some traditional, non-service-based wireless communication systems do not provide any signaling or other mechanisms that enable core network services to be individually activated and deactivated at the UE.

[0054] Therefore, various aspects of the present disclosure relate to signaling that can be used to selectively adjust the activation state (e.g., service state) of a core network service at a UE. In particular, various aspects of the present disclosure relate to signaling, configuration, and other mechanisms that enable a UE to subscribe to a core network service, exchange signaling indicating whether the corresponding core network service is in an active state or an inactive state, and maintain context information for both active core network services and inactive core network services to facilitate rapid service reestablishment. In addition, various aspects of the present disclosure can enable network entities and the core network services themselves to maintain context information for performing communications associated with the corresponding core network services in order to facilitate efficient communications within a service-based wireless communication system.

[0055] As used herein, the term "context information" may be used to refer to information maintained at a device (e.g., UE, network entity, core network service) that enables the corresponding device to communicate with other devices. Context information may include identifiers associated with other devices, communication parameters (e.g., type / format of communication), feedback procedures between devices, resources used for communication between devices, and the like. Context information may include "service context" information and "UE context" information. "Service context" information may include information stored / maintained by the UE and / or network entity for communicating with the core network service. "UE context" information may include information stored / maintained by the core network service and / or network entity for communicating with the UE (e.g., UE context may enable the core network service to communicate with the UE via a relay provided by the DU).

[0056] For example, the UE may subscribe to a first core network service and a second core network service, wherein the first core network service is in an active state at the UE and the second core network service is in an inactive state at the UE. The UE may maintain (e.g., store in a memory) a first service context for the first core network service and a second service context for the second core network service based on the respective active and inactive states of the corresponding core network services at the UE. In this regard, the UE may communicate with the first core network service based on the first service context. Subsequently, the UE may send or receive communications to activate the second core network service at the UE. When the second core network service is activated to an active state, the UE may communicate with the second core network service based on the second service context.

[0057] Context information (e.g., service context, UE context) used to perform core network services for active and inactive core network services can be stored in one or more locations on the corresponding device to facilitate rapid service re-establishment. For example, when the core network service is active at the UE, the context information used to perform the service can be maintained in three locations: (1) the UE, (2) a serving network entity (e.g., a distributed unit (DU)), and (3) the core network service itself. In contrast, when the core network service is inactive, the context information used to perform the core network service can be maintained in two locations: (1) the UE and (2) the core network service. Maintaining context information for an inactive core network service can enable the UE and the corresponding core network service to quickly re-establish communication.

[0058] Relevant 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 an example network architecture, an example activation state configuration, and an example process flow. Various aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to service states in a service-based wireless communication system.

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

[0060] Base stations 105 may be dispersed throughout a geographic area to form a wireless communication system 100 and may include devices of different forms or with different capabilities. In various examples, network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, an access point, or a network device, among others. In some examples, network entity 105 and UE 115 may communicate wirelessly via one or more communication links 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographic area over which base station 105 and UE 115 may support transmission of signals according to one or more radio access technologies.

[0061] 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 forms or with different capabilities. Figure 1 Some example UEs 115 are shown in FIG. Figure 1 As shown, the UE 115 described herein is capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105 .

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

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

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

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

[0066] In addition, in some examples, one or more network entities 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture), which may be configured to utilize a protocol stack 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 initiated by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of a central unit (CU), a DU 165, a RU 170, a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near RT-RIC), a non-real-time RIC), a service management and orchestration (SMO) system, or any combination thereof. One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (eg, virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

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

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

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

[0071] like Figure 1 As shown, the UE 115 described herein is capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as base stations 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc.

[0072] UE 115 and network entity 105 can use resources associated with one or more carriers to communicate with each other wirelessly via one or more communication links 125 (e.g., access links). The term "carrier" can refer to a set of RF spectrum resources with a defined physical layer structure to support communication link 125. For example, a carrier for communication link 125 may include a portion of an RF spectrum band (e.g., bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel can carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating operations for the carrier, user data, or other signaling. The wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. According to the carrier aggregation configuration, UE 115 can be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, when referring to the network entity 105, the terms "sending," "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 via one or more other network entities 105).

[0073] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling, or control signaling to coordinate operations for other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel grid to be discovered by a UE 115. A carrier may be operated in a standalone mode, where initial acquisition and connection may be performed by a UE 115 via the carrier, or may be operated in a non-standalone mode, where a connection is anchored using a different carrier (e.g., with the same or different radio access technology).

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

[0075] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers 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., base stations 105, UEs 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion of the bandwidth (e.g., subband, BWP) or the entire bandwidth of the carrier bandwidth.

[0076] The signal waveform transmitted via the carrier wave may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource unit may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high 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 layers may increase the data rate or data integrity used for communication with UE 115.

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

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

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

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

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

[0082] 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., via a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the base station 105, such a cell may range from a smaller area (e.g., a building, a subset of a building) to a larger area. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping geographic coverage areas 110, and the like.

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

[0084] 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 for different types of devices.

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

[0086] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automatic communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automatic 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 charging.

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

[0088] In some examples, the UE 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 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), and the network entity 105 may support various aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105, or may not be able 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 other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications are performed between UEs 115 without involving the network entity 105.

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

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

[0091] The wireless communication system 100 can operate using one or more frequency bands, which can range from 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features, but these waves can penetrate buildings sufficiently for macro cells to provide service to UEs 115 located indoors. Communications using UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmissions using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0092] The wireless communication system 100 may also operate using a super high frequency (SHF) region (which may be in the range of from 3 GHz to 30 GHz, also referred to as a centimeter band), or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also referred to as a millimeter band. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105, and the EHF antennas of the corresponding devices 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, the propagation of EHF transmissions may be affected by greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be used across transmissions using one or more different frequency regions, and the designated use of frequency bands spanning these frequency regions may vary by country or regulatory agency.

[0093] The wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can 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). When operating using unlicensed RF spectrum bands, devices such as base stations 105 and UEs 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on a carrier aggregation configuration combined with component carriers operating using licensed bands (e.g., LAA). Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

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

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

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

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

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

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

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

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

[0102] In some implementations, the wireless communication system 100 supports signaling and other mechanisms that can be used to selectively adjust the activation state of a core network service (e.g., CN / RAN service 185) at a UE 115. In particular, aspects of the present disclosure relate to signaling, configuration, and other mechanisms that enable a UE 115 to subscribe to a core network service (e.g., CN / RAN service 185) of a service-based network 130, exchange signaling indicating whether the corresponding core network service is active or inactive, and maintain context information for active and inactive core network services to facilitate rapid service reestablishment. In addition, aspects of the present disclosure can enable a network entity 105 (e.g., DU 165) and the core network service itself to maintain context information for performing communications associated with the corresponding core network service, so as to facilitate efficient communications within a service-based wireless communication system.

[0103] For example, a UE 115 of a wireless communication system 100 may subscribe to a first core network service and a second core network service, wherein the first core network service is in an active state at the UE 115, and the second core network service is in an inactive state at the UE 115. The UE 115 may maintain (e.g., store in a memory) a first service context for the first core network service and a second service context for the second core network service based on the corresponding core network services that are respectively in an active state and an inactive state at the UE 115. In this regard, the UE 115 may communicate with the first core network service based on the first service context. Subsequently, the UE 115 may send or receive a communication to activate the second core network service at the UE 115. When the second core network service is activated to an active state, the UE 115 may communicate with the second core network service based on the second service context.

[0104] Context information (e.g., service context, UE context) used to perform core network services for active and inactive core network services may be stored or maintained in one or more locations on the respective devices to facilitate rapid service reestablishment. For example, when the core network service is active at UE 115, context information used to perform the service may be maintained in three locations: (1) UE 115, (2) serving network entity 105 (e.g., DU 165), and (3) the core network service itself. In contrast, when the core network service is inactive, context information used to perform the core network service may be maintained in two locations: (1) UE 115 and (2) the core network service. Maintaining context information for inactive core network services may enable UE 115 and the respective core network services to quickly reestablish communications.

[0105] The techniques described herein may enable a UE 115 to subscribe to different core network services on an a la carte basis, and activate and deactivate the corresponding core network services, according to the needs or requirements of the corresponding UE 115. In this regard, aspects of the present disclosure enable different core network services to be maintained at the UE 115 in different activation states according to the needs or requirements of the corresponding UE 115, and enable the core network services to be activated or deactivated independently of each other. Therefore, the techniques described herein may enable the UE 115 to activate only those core network services that are required or desired, thereby reducing control signaling within the network and reducing power consumption at the UE 115. In addition, aspects of the present disclosure enable a wireless device to maintain (e.g., store) context information for executing the corresponding core network service based on the activation state of each corresponding core network service at the UE 115. In this regard, by enabling the wireless device to maintain context information for active and inactive core network services, the techniques described herein may facilitate fast and efficient service reconstruction when activating core network services, thereby reducing control signaling for activating core network services and improving the overall user experience.

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

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

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

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

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

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

[0112] In some aspects, each core network service 215 may include a respective API configured to facilitate wireless communications with the network entity 105 - a and the UE 115 - a , e.g. Figure 1 . The API at the corresponding 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 corresponding core network service 215. In contrast, the configuration API may be configured to facilitate communication between the network entity 105-a and the corresponding core network service 215 to negotiate service requirements and service specific operations.

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

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

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

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

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

[0118] In some implementations, as will be described in further detail herein, the wireless communication system 200 may support signaling that may be used to selectively adjust the activation state of core network services 215 at the UE 115. Specifically, aspects of the present disclosure relate to signaling that enables a UE 115-a to subscribe to core network services 215 of a service-based network 205, exchange signaling indicating whether the corresponding core network services 215 are in an active state or an inactive state, and maintain context information for active and inactive core network services 215 to facilitate rapid service reestablishment.

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

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

[0121] In some examples, CU 310 may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function may be implemented using an interface configured to transmit signals to other control functions hosted by CU 310. CU 310 may be configured to process user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some examples, 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 unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. CU 310 may be implemented to communicate with DU 165-a as needed for network control and signaling.

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

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

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

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

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

[0127] In some implementations, as will be described in further detail herein, the network architecture 300 can support signaling that can be used to selectively adjust the activation state of core network services at the UE 115. In particular, aspects of the present disclosure relate to signaling that enables the UE 115-a to subscribe to core network services of a service-based network, exchange signaling indicating whether the corresponding core network services are active or inactive, and maintain context information for active and inactive core network services to facilitate rapid service reestablishment.

[0128] Figure 4 An example of a wireless communication system 400 supporting techniques for service status in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. In some examples, aspects of the wireless communication system 400 can 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 can support signaling that enables the UE 115 to subscribe to core network services 415, exchange signaling indicating whether the corresponding core network services 415 are in an active state or an inactive state, and maintain context information for active and inactive core network services 415 to facilitate rapid service reestablishment, such as regarding Figure 1 as described.

[0129] The wireless communication system 400 may include a UE 115-b, a network entity 105-b, a first core network service 405-a, a second core network service 405-b, and a third core network service 405-c. In some implementations, the network entity 105-b may include an example of an O-RAN entity, which includes multiple components, such as one or more DUs, such as Figure 3shown and described. In this regard, Figure 4 The network entity 105 - b shown in FIG. 1 may additionally or alternatively be referred to as a DU or an eDU.

[0130] Core network services 405 may be associated with a service-based network, such as Figure 2 4. In some aspects, the service-based network including the core network service 405 can be configured to communicate or connect with a RAN of the wireless communication system 400, wherein the RAN includes one or more network entities (e.g., the network entity 105-b). In some implementations, the core network service 405 can be associated with a cloud platform or hosted by a cloud platform, wherein the corresponding core network service 405 is hosted at a corresponding network address in the cloud platform.

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

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

[0133] As previously described, the RAN may be connected to a service-based network that provides various core network services 405, and may relay communications between the UE 115 and the corresponding core network services 405. In this case, the UE 115 may "subscribe" to different core network services 405, wherein each corresponding core network service 405 may be in a different activation state (e.g., active state, inactive state, unconnected state) at the UE 115. The UE may be able to actively perform communications with the core network service 405 in an active state, but may not be able to perform communications with the core network service 405 in an inactive or unconnected state. However, some conventional, non-service-based wireless communication systems do not provide any signaling or other mechanisms that enable the core network services 405 to be individually activated and deactivated at the UE 115.

[0134] Thus, the wireless communication system 400 can support signaling that can be used to selectively adjust the activation state (e.g., service state) of the core network services 405 at the UE 115-b. In particular, aspects of the present disclosure relate to signaling, configuration, and other mechanisms that enable the UE 115-b to subscribe to the core network services 405, exchange signaling indicating whether the corresponding core network services 405 are active or inactive, and maintain context information for active and inactive core network services to facilitate rapid service reestablishment.

[0135] In other words, aspects of the present disclosure relate to techniques for service establishment, wherein RAN context information may be exchanged as a service. In some implementations, the activation state of each respective core network service 405 may be independently adjusted for each respective core network service 405 (e.g., the activation state of each service). In some aspects, the wireless communication system 400 may support signaling and other mechanisms that enable a wireless device to: obtain and / or adjust the activation state of a core network service 405, and obtain, store, and maintain AS context information that may be used to perform communications associated with the respective core network service 405.

[0136] In some aspects, the UE 115-b may be configured to operate in different RAN or eDU states. The term "RAN / eDU state" for the UE 115-e may be used to refer to the state of the UE 115-b relative to the network entity 105-b or the RAN (e.g., whether the UE 115-b is connected to the RAN). For example, the UE 115-b may be configured to operate in one of an idle RAN state (e.g., an eDU idle state), a connected RAN state (e.g., an eDU connected or eDU active state), or an inactive RAN state (e.g., an eDU inactive state). In the eDU idle state, the UE 115-b may not have a wireless connection with the network entity 105-b (e.g., no RAN connection). In contrast, in the eDU active / connected state, the UE 115-b may have an active wireless connection with the network entity 105-b that enables wireless communication between the respective devices (e.g., an active RAN connection with the network entity 105-b). Finally, in the eDU inactive state, UE 115-b may have eDU context information for communicating with network entity 105-b via communication link 410, but may not have ongoing communications with network entity 105-b. While in the eDU inactive state, network entity 105 (and / or UE 115-b) may maintain the last UE-RAN connection configuration.

[0137] In addition, aspects of the present disclosure may enable the core network services 405 to be maintained in different activation states (e.g., service states) at the UE 115-b. The terms "activation state" or "service state" associated with the core network services 405 may be used to refer to the state of the UE 115-b relative to each respective core network service 405, as compared to the RAN / eDU state of the UE 115-e (which refers to the communication between the UE 115-b and the RAN). Each respective core network service 405 provided by the service-based network may be in one of an active state, an inactive state, or an unconnected state (e.g., an unregistered state) at each UE 115 of the wireless communication system 400. The activation state may be maintained independently at each core network service 405.

[0138] For example, Figure 4As shown, the first core network service 405-a can be in an active state at UE 115-b, the second core network service 405-b can be in an inactive state at UE 115-b, and the third core network service 405-c can be in an unconnected state at UE 115-b. In addition, each core network service 405 can be in a different state at different UEs 115. For example, the first core network service 405-a can be in an inactive or unconnected state at another UE 115, and the second core network service 405-b can be in an active or unconnected state at another UE 115.

[0139] In some aspects, different core network services 405 may be maintained (e.g., activated, deactivated) at UE 115-b based on the requirements or expectations of UE 115-b (e.g., which applications UE 115-b is currently executing). In some aspects, each core network service 405 provided by the service-based network may initially start in an unconnected state at UE 115-b until UE 115-b subscribes to the corresponding core network service 405, at which time the corresponding core network service 405 may transition to one of an active or inactive state. In some aspects, UE 115-b may be configured to perform communications with a core network service 405 in an active state. In contrast, UE 115-b may not be able to perform communications with a core network service 405 in an inactive or unconnected state. In some aspects, the activation state of each corresponding core network service 405 at UE 115-b may change independently of each other (e.g., a second core network service 405-b may be activated without affecting the activation state of other core network services 405).

[0140] As will be further described herein, the UE 115-b, the network entity 105-b, the core network service 405, or any combination thereof may be configured to maintain (or not maintain) context information (e.g., service context, UE context) associated with execution of the core network service 405 based on the activation state of each respective core network service 405.

[0141] As used herein, the term "context information" may be used to refer to information maintained at a device (e.g., UE 115, network entity 105, core network service 405) that enables the corresponding device to communicate with other devices. The context information may include identifiers associated with other devices (e.g., network addresses), communication parameters (e.g., type / format of communication), feedback procedures between devices, resources used for communication between devices, etc. The context information may include "service context" information, which may include information stored / maintained by UE 115 and / or network entity 105 for communicating with core network service 405, and "UE context" information, which may include information stored / maintained by core network service 405 and / or network entity 105 for communicating with UE 115 (e.g., UE context may enable core network service to communicate with UE 115 via a relay provided by DU).

[0142] For example, based on the first core network service 405-a being active at the UE 115-b, context information for the first core network service 405-a may be maintained at the UE 115-b, the network entity 105-b, and the first core network service 405-a. While active, the first core network service 405-a may know or identify the serving network entity 105-b (e.g., serving DU) for the UE 115-b (e.g., due to active exchange of communications).

[0143] As another example, based on the second core network service 405-b being in an inactive state at the UE 115-b, context information for the second core network service 405-b may be maintained at the UE 115-b and the second core network service 405-b. Compared to the first core network service 405-a, the network entity 105-b may not be configured to maintain context information for the second core network service 405-b because, based on the second core network service 405-b being in an inactive state, there is no ongoing communication between the UE 115-b and the second core network service 405-b. When in an inactive state, the second core network service 405-b may not be aware of or identify the serving network entity 105-b / serving DU for the UE 115-b (e.g., because there is no active communication being exchanged). Finally, based on the third core network service 405 - c being in an unconnected state at the UE 115 - b , the context information may not be maintained at any of the UE 115 - b , the network entity 105 - b , or the third core network service 405 - c .

[0144] Different communications or operations enabled by different combinations of RAN / eDU states and core network service 405 activation states are shown in Table 1 below: Table 1: eDU status / activation status summary

[0145] In some aspects, UE 115-b may obtain information from a subscription service (e.g., a core network subscription service) or a discovery service (e.g., a core network discovery service) associated with other core network services 405 provided by core network services 405 (e.g., the subscription / discovery service may indicate which core network services 405 are accessible to UE 115-b). After obtaining the information from the subscription / discovery service, UE 115-b may subscribe to additional core network services 405. In some aspects, each core network service 405 may be associated with a security service or a certain security level.

[0146] In some aspects, a core network service 405 may be related or interdependent with other core network services 405 within a "group" or "cluster" of core network services 405 (e.g., UE 115-b is expected to subscribe to a second core network service 405-b in order to communicate with a first core network service 405-a). In this regard, the activation states of the core network services 405 within a group or cluster may exhibit interdependencies with each other. In some cases, multiple network operators (e.g., mobile virtual network operators, MVNOs) may share the same core network service 405 / connectivity service, or be associated with a core network service 405 / connectivity service. In addition, because each core network service 405 may operate independently of one another, a single operator is able to host or provide new core network services 405 without affecting other core network services 405 within the network.

[0147] In some aspects, the UE 115-b, the network entity 105-b, and / or the respective core network services 405 may be configured to exchange signaling that selectively adjusts the activation state of each respective core network service 405 at the UE 115-b. For example, the UE 115-b may be configured to send a message to the second core network service 405-b (via the network entity 105-b) that includes instructions for activating the second core network service 405-b at the UE 115-b.

[0148] UE 115-b may maintain core network services 405 in an active state when the corresponding core network services 405 are being used (e.g., communicating with) and when UE 115-b is connected to network entity 105-b (e.g., eDU active / connected state). Similarly, core network services 405 may be configured to establish services / contexts with UE 115-b and determine whether / when the corresponding core network services 405 are active at UE 115-b. In some aspects, UE 115-b may determine the need or desire to communicate with additional core network services 405 for which UE 115-b has established a context and which are currently inactive. For example, UE 115-b may determine the desire to exchange communications with a second core network service 405-b that is in an inactive state. In this example, UE 115-b may send an activation request to network entity 105b-, where the activation request indicates a second core network service 405-b (and / or additional core network services 405) to be activated at UE 115-b. In this example, network entity 105-b may relay the activation request to the corresponding core network service 405.

[0149] In some aspects, the activation request may indicate routing information (e.g., a network address) for each core network service 405 to be activated, and may optionally include additional service protocol messages 405 to be delivered to the newly activated core network services. In some cases, the UE 115-b may receive a confirmation message from the network entity 105-b indicating which core network services 405 were successfully (or unsuccessfully) activated. The UE 115-b may then transition each of the confirmed core network services 405 to an active state at the UE 115-b. In some aspects, the network entity 105-b may receive a request from the UE 115-b and / or the activated core network services 405 to keep the corresponding core network services in an active state, and for the network entity 105-b to maintain context information (e.g., service context, UE context) for executing the corresponding core network services 405.

[0150] The core network services 405 active at the UE 115-b may be configured to maintain a context (e.g., service context, UE context) with the network entity 105-b to which the UE 115-b is connected. The context information (e.g., UE context) maintained at the core network services 405 may include information associated with how communications to the UE 115-b and / or the network entity 105-b are addressed (e.g., cell ID, UE ID), service-related configuration information associated with the network entity 105-b, etc. In the event that the UE 115-b performs a handover to a new network entity 105-b, the core network services 405 may be configured to re-establish a context with the new network entity 105-b.

[0151] For each requested core network service 405 that is not successfully activated, the UE 115-b may receive (e.g., from the network entity 105-b) a reason for the activation failure (e.g., a reason code). The reason for the activation failure may be indicated via direct local signaling, via one or more service protocol messages, or both. In the event of an activation failure, the UE 115-b may remove or discard context information (e.g., service context) for the failed core network service 405 based on the failure cause. In some aspects, the UE 115-b may attempt to reestablish a context with the core network service 405 (e.g., reactivate or resubscribe) based on the activation failure, or establish a context with another core network service 405.

[0152] In some aspects, UE 115-b, network entity 105-b and / or core network services 405 may determine when one or more core network services 405 become inactive (e.g., deactivated, or otherwise transitioned to an inactive state) at UE 115-b based on explicit signaling from UE 115-b and / or core network services 405, based on UE 115-b being disconnected from network entity 105-b or other RAN node, based on local protocol errors (e.g., messages sent to core network services 405 repeatedly fail), or any combination thereof. For example, where a first core network service 405-a has performed its purpose, the first core network service 405-a and / or UE 115-b may send signaling at UE 115-b indicating deactivation of the first core network service 405-a. In addition, when UE 115-b disconnects from network entity 105-b (e.g., when UE 115-b enters an eDU idle or inactive state), all activated core network services 405 may be deactivated (e.g., transitioned to an inactive state).

[0153] In addition, if the UE 115-b determines that there are no active core network services 405 at the UE 115-b, or determines that the UE 115-b does not need / expect to communicate with any core network services 405 at that time or in the near future, the UE 115-b can be configured to send a request to the network entity 105-b to release the RAN connection with the UE 115-b. If there are any core network services 405 active at the UE 115-b, the request can include further signaling for the activated core network services 405, indicating that the UE 115-b is disconnecting and deactivating the core network services 405 at the UE 115-b. Similarly, in some aspects, the network entity 105-b can be configured to determine that there are no active core network services 405 at the UE 115-b, and therefore can initiate the release of the RAN connection with the UE 115-b. In this case, the network entity 105-b can determine that there is no active core network service 405 based on explicit signaling from the UE 115-b and / or a previously activated core network service 405, based on a release request received from the UE 115-b, due to a radio link failure, or any combination thereof.

[0154] In the event that the core network service 405 is deactivated at the UE 115-b (e.g., transitions to an inactive state at the UE 115-b), the core network service 405 may be configured to maintain (e.g., store in a memory) a UE context for communicating with the UE 115-b. However, the core network service 405 in the inactive state may not maintain up-to-date information associated with which network entity 105 the UE 115-b is connected. In this regard, the core network service 405 may release / discard the network entity 105-b identity and related information, or maintain information associated with the “last connected network entity 105-b / DU” in the event that the UE 115-b reconnects to the same network entity 105-b or the core network service 405 is activated while the UE 115-b is connected to the same network entity 105-b.

[0155] You can refer to Figure 5 and Figure 6 Maintenance (eg, storage) of context information (eg, service context, UE context) for communications between the UE 115 - b , the network entity 105 - b , and the core network services 405 is further illustrated and described.

[0156] Figure 5An example of an activation state configuration 500 that supports techniques for service states in a service-based wireless system according to one or more aspects of the present disclosure is shown. In some examples, aspects of the activation state configuration 500 can implement aspects of or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, or any combination thereof. In particular, the activation state configuration 500 illustrates a situation where context information (e.g., service context, UE context) for a core network service is maintained at different wireless devices based on the corresponding activation state of the core network service, as shown in reference Figure 1-4 and other aspects described.

[0157] Figure 5 Activation state configuration 500 in FIG. 1 shows different configurations 505-a, 505-b, and 505-c, each of which includes UE 115-c, eDU 510 (e.g., network entity 105), a first core network service 515-a and a second core network service 515-b, which can be examples of UE 115, network entity 105, and core network services as described herein. In particular, each configuration 505 shows that context information for the corresponding core network service 515 can be stored based on the RAN / eDU state of UE 115c and based on the activation state of the corresponding core network service 515.

[0158] For example, referring to the first configuration 505-a, the UE 115-c may operate in an idle state (e.g., eDU idle). As such, the UE 115-c may not have any RAN connection with the eDU 510, and each of the core network services 515 may be in an unconnected state. Therefore, the UE 115-c may not have any context information (e.g., service context) for communicating with the core network services 515, and the core network services 505 may not have any context information (e.g., UE context) for communicating with the UE 115-c.

[0159] Referring now to the second configuration 505-b, the UE 115-b may be operating in a connected state (e.g., eDU active or eDU connected state) and may therefore have an active connection with the eDU 5150. In this example, the first core network service 515-a may be in an active state, while the second core network service 515-b may be in an unconnected state. Therefore, as described with reference to the first configuration, based on the second core network service 515-b being in an unconnected state at the UE 115-c, neither the UE 115-c nor the second core network service 515-b may have any context information (e.g., service context, UE context) for communicating with each other. In contrast, because the first core network service 515-a is in an active state, the service context 520-a associated with the first core network service 515-a may be maintained (e.g., stored) at the UE 115-c and the eDU 510. Additionally, the core network service 515 - a may maintain a UE context 525 associated with communications with the UE 115 - c based on the first core network service 515 - a being active at the UE 115 - c .

[0160] Referring now to the third configuration 505-c, the UE 115-b may be operating in a connected state (e.g., an eDU active or eDU connected state) and may therefore have an active connection with the eDU 5150. In this example, both the first core network service 515-a and the second core network service 515-b may be in an active state. Therefore, both the UE 115-c and the eDU 510 may maintain a first service context 520-a and a second service context 520b associated with the first core network service 515-a and the second core network service 515-b, respectively. In addition, both core network services 515 may maintain a UE context 525 associated with communications with the UE 115-c based on the respective core network services 515 being in an active state at the UE 115-c.

[0161] Although the UE context 525 stored at the first core network service 515-a and the second core network service 515-b are shown and described as including the same UE context 525, this is for illustration purposes only. In particular, each respective core network service 515 can maintain a service-specific UE context 525 for communicating with the UE 115-c. In addition, the UE context 525 can include information associated with the network eDU 510 (e.g., identifier, network address) that facilitates communication between the UE 115-c and the respective core network service 515.

[0162] Figure 6An example of an activation state configuration 600 that supports techniques for service states in a service-based wireless system according to one or more aspects of the present disclosure is shown. In some examples, aspects of the activation state configuration 600 can implement aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, the activation state configuration 500, or any combination thereof, or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, the activation state configuration 500, or any combination thereof. In particular, the activation state configuration 600 illustrates a case where context information (e.g., service context, UE context) for a core network service is maintained at different wireless devices based on the corresponding activation states of the core network service, as described in reference to FIG. Figure 1-5 and other aspects described.

[0163] Figure 6 Activation state configuration 500 in FIG. 5 shows different configurations 605-a, 605-b, and 605-c, each of which includes a UE 115-d, one or more eDUs 610 (e.g., network entity 105), a first core network service 615-a, and a second core network service 615-b, which can be examples of UE 115, network entity 105, and core network services as described herein. In particular, each configuration 605 shows a situation where context information for a corresponding core network service 615 can be stored based on the RAN / eDU state of UE 115-d and based on the activation state of the corresponding core network service 615.

[0164] For example, referring to the first configuration 605-a, the UE 115-d may operate in an inactive state (e.g., the eDU is inactive). In this way, the UE 115-d may not have any RAN connection with the eDU 610. In this example, each of the core network services 615 may be in an inactive state at the UE 115-c. Therefore, the UE 115-d may maintain a first service context 620-a associated with the first core network service 615-a and a second service context 620-b associated with the second core network service 615-b based on the corresponding core network service 615 being in an inactive state. Similarly, the two core network services 615 may maintain a UE context 625 associated with communication with the same UE 115-d based on the respective core network services 615 being in an inactive state at the UE 115-d. In some aspects, maintaining service context 620 and UE context 625 information at UE 115-d and core network service 615, respectively, can enable the respective devices to quickly and efficiently reestablish communications with each other when the respective core network service 615 is subsequently activated at UE 115-d.

[0165] Referring now to the second configuration 605-b, the UE 115-b may be operating in a connected state (e.g., an eDU active or eDU connected state) and may therefore have an active connection with the eDU 6150. In this example, the first core network service 615-a may be in an active state. Thus, because the first core network service 615-a is in an active state, a service context 620-a associated with the first core network service 615a may be maintained (e.g., stored) at the UE 115-d and the eDU 610. In addition, based on the first core network service 615-a being active at the UE 115-d, the first core network service 615-a may maintain a UE context 625 associated with communications with the same UE 115-d. In contrast, the second core network service 615-b may be in an inactive state. Thus, because the second core network service 615-b is in an inactive state, a service context 620-a associated with the second core network service 615-b may be maintained (e.g., stored) at the UE 115-d (rather than the eDU 610). In addition, the second core network service 615-b may maintain a UE context 625 associated with communications with the UE 115-d based on the second core network service 615-b being in an inactive state at the UE 115-d.

[0166] Referring now to the third configuration 605-c, the UE 115-b may be operating in a connected state (e.g., eDU active or eDU connected state) with the first eDU 610-a and the second eDU 610-b, and may thus have an active connection with the respective eDUs 610. In this regard, the third configuration 605-c may illustrate an example of a dual connectivity scenario. Additionally or alternatively, the first eDU 610-a may be an example of a primary cell (PCell) and the second eDU 610b may be an example of a secondary cell (SCell).

[0167] Continuing to refer to the third configuration, both the first core network service 615-a and the second core network service 615-b can be in an active state. Therefore, UE 115-d can maintain a first service context 620-a and a second service context 620-b associated with the first core network service 615-a and the second core network service 615-b, respectively. In addition, the first eDU 610-a can maintain a first service context 620-a associated with the first core network service 615-a, and the second eDU 610-a can maintain a second service context 620-b associated with the second core network service 615-b. In addition, the two core network services 615 can maintain a UE context 625 associated with communication with the same UE 115-d based on the corresponding core network service 615-d being active at UE 115-d. In particular, the UE context 625 maintained at the first core network service 615-a may include information for communicating with the first eDU 610-a, and the second UE context 625 maintained at the second core network service 615-b may include information for communicating with the second eDU 610-b.

[0168] Although the UE context 625 stored at the first core network service 615-a and the second core network service 615-b are shown and described as including the same UE context 625, this is for illustration purposes only. In particular, each respective core network service 615 may maintain a service-specific UE context 625 for communicating with the UE 115-d. In addition, the UE context 625 may include information associated with the network eDU 610 (e.g., identifier, network address) that facilitates communication between the UE 115-c and the respective core network service 615. In this regard, the UE context 625 stored and maintained by the first core network service 615-a may be different from the UE context 625 stored and maintained by the second core network service 615 because the respective UE context 625 is associated with communication with the UE 115-d performed via different eDUs 610.

[0169] Figure 7An example of a process flow 700 for supporting techniques for service states in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. In some examples, aspects of the process flow 700 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, the activation state configuration 500, the activation state setting 600, or any combination thereof. In particular, the process flow 700 illustrates signaling that enables the UE 115 to subscribe to a core network service 705, exchange signaling indicating whether the corresponding core network service 705 is in an active state or an inactive state, and maintain context information for active and inactive core network services 415 to facilitate rapid service reestablishment, as described in reference to FIG. Figure 1-6 as described.

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

[0171] The process flow 700 may include a UE 115-e, a network entity 105-c, a first core network service 705-a, a second core network service 705-b, and a third core network service 705-c, which may be reference Figure 1-6 Examples of UE 115, network entity 105, core network services, and other wireless devices are described.

[0172] In some aspects, core network services 705 may be included in a network consisting of a service-based network (e.g. Figure 2 In this case, the service-based network including the core network services 705 can be configured to connect to (e.g., communicate with) a RAN including a network entity 105-c (e.g., DU, eDU) to facilitate communication between the service-based network and the UE 115-e. In this regard, Figure 7 The signaling shown in may include example signaling within a network having a service-based architecture such as a 6G system.

[0173] In some aspects, the corresponding core network services 705 may be in different activation states at the UE 115-e. Figure 7 As shown, the first core network service 705-a can be in an active state at the UE 115-e, the second core network service 705-b can be in an inactive state at the UE 115-e, and the third core network service 705-c can be in an unconnected state at the UE 115-e.

[0174] As shown and described herein, context information (e.g., service context 520, 620, UE context 525, 625) can be stored and maintained at the corresponding components (e.g., UE 115-e, network entity 105-c, core network service 705) based on the activation state of the corresponding core network service 705. For example, based on the first core network service 705-a being active at UE 115-c, the service context associated with the first core network service 705-a can be maintained at UE 115-e and network entity 105-c. In addition, the first core network service 705-a can maintain the UE context associated with UE 115-e based on the first core network service 705-a being active at UE 115-e. In contrast, UE 115-e (but not network entity 105-c) can maintain the service context associated with the second core network service 705-b based on the second core network service 705-b being inactive at UE 115-c. In addition, the second core network service 705-b can maintain the UE context associated with the UE 115-e based on the second core network service 705-b being active at the UE 115-e. Finally, based on the third core network service 705-c being in an unconnected state at the UE 115-e, the UE 115-e, the network entity 105-c, or the third core network service 705-c may not maintain context information (e.g., service context, UE context) associated with the third core network service 705-c.

[0175] At 710, UE 115-e may exchange service messages with the first core network service 705-a via a relay provided by the network entity 105-c and based on a service context used to communicate with the first core network service 705-a. In this regard, the network entity 105-c may relay service messages (e.g., service protocol data units) between the UE 115-e and the first core network service 705 based on the service context associated with the first core network service 705-a. In addition, the first core network service 705-a may transmit service messages with the UE 115-e (via the network entity 105-c) based on the UE context associated with the UE 115-e. As previously noted herein, context information (e.g., service context, UE context) associated with the first core network service 705-a may be stored at the UE 115-e, the network entity 105-c, or the first core network service 705-a based on the first core network service 705-a being active at the UE 115-e.

[0176] In some aspects, service messages exchanged between the UE 115-e and the first core network service 705-a may include identifiers associated with the UE 115-e and the first core network server 705-a, such as a UE ID, a network address of the first core network host 705-a, and the like.

[0177] At 715, UE 115-e may send a request (e.g., an activation request) to activate second core network service 705-b at UE 115-e via network entity 105-c. The activation request may include routing information (e.g., a network address) associated with second core network service 705-b. Additionally or alternatively, the request may include a service message (e.g., a service data protocol unit) to be delivered to second core network service 705-b.

[0178] In some aspects, the second core network service 705-b can be associated with a second service context, which can be maintained at the UE 115-e based on the second core network service 705-b being inactive at the UE 115-e. In addition, the second core network service 705-b can be configured to maintain the UE context based on the second core network service 705-b being inactive at the UE 115-e.

[0179] At 720, UE 115-e may receive a response message from second core network service 705-b (e.g., via network entity 105-c). In some aspects, the response message may indicate whether second core network service 705-b has been successfully activated (e.g., whether second core network service 705-b accepted the activation).

[0180] In the event that the second core network service 705-b is not successfully activated, the response message may indicate the reason for the activation failure (e.g., a reason code). In some aspects, in the event of an activation failure, the UE 115-e may remove or discard context information (e.g., service context) associated with the second core network service 705-b and the failed core network service 405 based on the failure cause. Additionally or alternatively, the UE 115-b may attempt to re-establish a context with the second core network service 705-b (e.g., send a new activation request) or establish a context with another core network service 705 based on the activation failure.

[0181] Conversely, if the activation of the second core network service 705-b is successful, the UE 115-e may transition the second core network service 705-b to an active state at the UE 115-e. In addition, the network entity 105-c may acquire and maintain context information (e.g., service context) associated with the second core network service 705-b based on the activation of the second core network service 705-b.

[0182] In some aspects, the network entity 105-c can receive a request from the UE 115-e and / or the activated core network service 705 (e.g., the first core network service 705-a, the second core network service 705-b) to keep the corresponding core network service 405 in an active state, and for the network entity 105-b to maintain context information (e.g., service context, UE context) for executing the corresponding core network service 705.

[0183] At 725, the UE 115-e may exchange service messages with the second core network service 705-b via a relay provided by the network entity 105-c and based on a service context for communicating with the second core network service 705-b. In this regard, the network entity 105-c may relay service messages (e.g., service protocol data units) between the UE 115-e and the second core network service 705-b based on the service context associated with the second core network service 705-b. In addition, the second core network service 705-b may transmit service messages with the UE 115-e (via the network entity 105-c) based on the UE context associated with the UE 115-e.

[0184] In some aspects, based on transmitting the activation request at 715, transmitting the response message at 720, activating the second core network service 705-b at the UE 115-e, or any combination thereof, the UE 115-e and the second core network service 705-b may communicate with each other at 725. As previously noted herein, context information (e.g., service context, UE context) associated with the second core network service 705-b may be stored at the UE 115-e, the network entity 105-c, and the second core network service 705-b based on the second core network service 705-b being transitioned to an active state at the UE 115-e.

[0185] In some aspects, service messages exchanged between the UE 115-e and the second core network service 705-b may include identifiers associated with the UE 115-e and the second core network service 705-b, such as a UE ID, a network address of the second core network service 705-b, and the like.

[0186] At 730, UE 115-c may send (via network entity 105-c) a request (e.g., a service request) to establish a service with a third core network service 705-c based on the third core network service 705-c being in an unconnected state at UE 115-e. In some aspects, the service request may include a network address associated with the third core network service 705-c. In other words, UE 115-e may request to establish a service context with the third core network service 705-c. In some aspects, UE 115-e may send the service request as part of a service establishment process (e.g., a subscription process) between UE 115-e and the third core network service 705-c.

[0187] At 735, the UE 115-e may receive a response message from the third core network service 705-c (e.g., via the network entity 105-c). In some aspects, the response message may indicate whether the third core network service 705-c has been successfully activated (e.g., whether the third core network service 705-c accepts the activation).

[0188] As previously noted herein, in the event that the third core network service 705-c is not successfully activated, the response message may indicate the reason for the activation failure (e.g., a reason code). In some aspects, in this case, the UE 115-b may attempt to re-establish a context with the third core network service 705-c (e.g., send a new activation request) based on the activation failure, or establish a context with another core network service 705.

[0189] Conversely, in the event that activation of the third core network service 705-c is successful, the response message from the third core network service 705-c may indicate a third service context for communicating with the third core network service 705-c. In addition, the network entity 105-c may acquire and maintain context information (e.g., a third service context) associated with the third core network service 705-c based on activation of the third core network service 705-c, and the third core network service 705-c may acquire and maintain a UE context associated with the UE 115-e based on activation of the third core network service 705-c.

[0190] At 740, the UE 115-e may store (and subsequently maintain) in memory a third service context associated with communications with the third core network service 705-c. As previously noted herein, based on the third core network service 705-c being in an unconnected state, the UE 115-e may not have stored any context information associated with the third core network service 705-c. Thus, the UE 115-e may store the third service context based on activating the third core network service 705-c at the UE 115-e.

[0191] At 745, the UE 115-e may exchange service messages with the third core network service 705-c via a relay provided by the network entity 105-c and based on the third service context stored at 740 for communicating with the third core network service 705-c. In this regard, the network entity 105-c may relay service messages (e.g., service protocol data units) between the UE 115-e and the third core network service 705-c based on the third service context associated with the third core network service 705-c. In addition, the third core network service 705-c may transmit service messages with the UE 115-e (via the network entity 105-c) based on the UE context associated with the UE 115-e (the third core network service 705-c may store and maintain the UE context based on activation of the third core network service 705-c). As previously noted herein, service messages exchanged between UE 115-e and the third core network service 705-c may include identifiers associated with UE 115-e and the third core network service 705-c, such as a UE ID, a network address of the third core network service 705-c, and the like.

[0192] At 750 , the UE 115 - e , the network entity 105 - c , the first core network service 705 - a , or any combination thereof may exchange signaling indicating deactivation of the first core network service 705 - a at the UE 115 - e .

[0193] As previously noted herein, deactivation of the core network service 705 can be based on (e.g., triggered by) a variety of different events or parameters. For example, deactivation of the first core network service 705-a can be based on explicit signaling from the first core network service 705-a and / or the UE 115-e (e.g., when the first core network service 705-a has performed its purpose), release of the wireless connection between the UE 115-e and the network entity 105-c, a radio link failure, a failure of one or more messages sent from the UE 115-e to the first core network service 705-a (or vice versa), or any combination thereof.

[0194] In some aspects, the first core network service 705-a may be deactivated (e.g., transitioned to an inactive state) at the UE 115-e based on the signaling at 750. In some implementations, the UE 115-e may maintain a first service context associated with the first core network service 705-a even after the first core network service 705-a is deactivated at the UE 115-e. Similarly, the first core network service 705-a may maintain a UE context for communicating with the UE 115-e even after the first core network service 705-a is deactivated at the UE 115-e.

[0195] At 755, the network entity 105-c may reallocate resources previously associated with (e.g., allocated to) communications between the UE 115-e and the first core network service 705-a. In particular, the network entity 105-c may reallocate resources based on the deactivation of the first core network service 705-a at 750. The network entity 105-c may reallocate resources to another core network service 705, another UE 115, or any combination thereof.

[0196] At 760, the UE 115-e, the network entity 105-c, or both may determine that all core network services 705 have been deactivated at the UE 115-e (e.g., the UE 115-e does not have any active core network services 705-c). In some aspects, the UE 115-e, the network entity 105-c, or both may determine that all core network services 705 have been deactivated based on explicit signaling to deactivate previously activated core network services 705, based on the UE 115-e being disconnected from the network entity 105-c, based on local protocol errors (e.g., messages sent to the core network services 705 repeatedly fail), or any combination thereof.

[0197] At 765, the UE 115-e, the network entity 105-c, or both may release the wireless connection between the respective devices (e.g., the UE 115-e is disconnected from the RAN). In some aspects, the UE 115-e and / or the network entity 105-c may release the connection at 765 based on determining at 760 that all core network services 705 have been deactivated at the UE 115-e.

[0198] For example, if the UE 115-e determines that there are no active core network services 705 at the UE 115-e, or determines that the UE 115-e does not need / expect to communicate with any core network services 705 at that time or in the near future, the UE 115-e may be configured to send a request to the network entity 105-c to release the RAN connection with the UE 115-e. Similarly, in some aspects, the network entity 105-c may be configured to determine that there are no active core network services 705 at the UE 115-c, and may therefore initiate the release of the RAN connection with the UE 115-e.

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

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

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

[0202] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing corresponding aspects of the techniques for service status in a service-based wireless network. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more functions described herein.

[0203] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations, or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include the following that are configured as or otherwise support units for performing the functions described in the present disclosure: 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. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0204] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, 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 means for performing the functionality described in the present disclosure).

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

[0206] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. For example, the communication manager 820 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message with a first core network service provided by a service-based network via a DU, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based on the first core network service being in an active state at the UE. The communication manager 820 may be configured to or otherwise support a unit for performing the following operations: sending a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based on the second core network service being in an inactive state at the UE. The communication manager 820 may be configured to or otherwise support a unit for performing the following operations: receiving a message indicating activation of the second core network service at the UE from the DU in response to the request. The communication manager 820 may be configured as or otherwise support means for communicating a second service message with the second core network service via a DU based on the activation of the second core network service at the UE according to the second service context.

[0207] By including or configuring the communication manager 820 according to examples as described herein, the device 805 (e.g., a processor controlling or otherwise coupled to the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) may support techniques that enable the UE 115 to subscribe to different core network services on an a la carte basis and to activate and deactivate the respective core network services according to the needs or requirements of the respective UE 115. In this regard, aspects of the present disclosure enable different core network services to be maintained at the UE 115 in different activation states according to the needs or requirements of the respective UE 115, and enable the core network services to be activated or deactivated independently of each other. Thus, the techniques described herein may enable the UE 115 to activate only those core network services that are needed or desired, thereby reducing control signaling within the network and reducing power consumption at the UE 115. Furthermore, aspects of the present disclosure enable the wireless device to maintain (e.g., store) context information for performing corresponding core network services based on the activation state of each corresponding core network service at the UE 115. In this regard, by enabling the wireless device to maintain context information for active and inactive core network services, the techniques described herein may facilitate fast and efficient service reestablishment when activating core network services, thereby reducing control signaling for activating core network services and improving the overall user experience.

[0208] Fig. 9 A block diagram 900 of a device 905 supporting techniques for service status in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0209] The receiver 910 may provide a means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technology for service status in a service-based wireless network). The information may be delivered to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.

[0210] The transmitter 915 may provide a means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technology for service status in service-based wireless networks). In some examples, the transmitter 915 may be collocated with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.

[0211] The device 905 or its various components may be examples of units for performing the corresponding aspects of the technology for service status in a service-based wireless system as described herein. For example, the communication manager 920 may include a service message communication manager 925, a request sending manager 930, an activation state manager 935, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its corresponding components may be configured to use the receiver 910, the transmitter 915, or both or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0212] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. The service message communication manager 925 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message with a first core network service provided by a service-based network via a DU, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based on the first core network service being in an active state at the UE. The request sending manager 930 may be configured to or otherwise support a unit for performing the following operations: sending a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based on the second core network service being in an inactive state at the UE. The activation state manager 935 may be configured to or otherwise support a unit for performing the following operations: receiving a message indicating activation of the second core network service at the UE from the DU in response to the request. The service message communication manager 925 may be configured as or otherwise support means for communicating a second service message with the second core network service via a DU based on the activation of the second core network service at the UE according to the second service context.

[0213] Fig.10 A block diagram 1000 of a communication manager 1020 supporting technology for service status in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of units for performing corresponding aspects of the technology for service status in a service-based wireless system as described herein. For example, the communication manager 1020 may include a service message communication manager 1025, a request sending manager 1030, an activation state manager 1035, a service context manager 1040, a wireless connection manager 1045, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0214] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at the UE. The service message communication manager 1025 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message with a first core network service provided by a service-based network via a DU, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based on the first core network service being in an active state at the UE. The request transmission manager 1030 may be configured to or otherwise support a unit for performing the following operations: sending a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based on the second core network service being in an inactive state at the UE. The activation state manager 1035 may be configured to or otherwise support a unit for performing the following operations: receiving a message indicating activation of the second core network service at the UE from the DU in response to the request. In some examples, the service message communication manager 1025 may be configured as or otherwise support a unit for transmitting a second service message with the second core network service via a DU based on the activation of the second core network service at the UE according to the second service context.

[0215] In some examples, the request sending manager 1030 may be configured as or otherwise support a unit for performing the following operations: based on the third core network service being in an unconnected state at the UE, sending a second request to the DU to establish a service with the third core network service. In some examples, the service context manager 1040 may be configured as or otherwise support a unit for performing the following operations: based on the second request, receiving a second message from the DU, the second message indicating a third service context for communicating with the third core network service; in some examples, the service context manager 1040 may be configured as or otherwise support a unit for performing the following operations: based on converting the third core network service from the unconnected state to one of the active state or the inactive state at the UE, storing the third service context in a memory.

[0216] In some examples, the activation state manager 1035 can be configured as or otherwise support a unit for performing the following operations: transmitting a second message with the DU indicating deactivation of the first core network service at the UE, wherein the first service context is maintained at the UE at least in part based on the deactivation.

[0217] In some examples, the deactivation of the first core network service is based on signaling from the first core network service, release of a wireless connection between the UE and the DU, a radio link failure, failure of one or more messages sent from the UE to the first core network service, or any combination thereof.

[0218] In some examples, the activation state manager 1035 may be configured as or otherwise support a unit for performing the following operations: identifying that all core network services including the first core network service and the second core network service have been deactivated at the UE. In some examples, the wireless connection manager 1045 may be configured as or otherwise support a unit for performing the following operations: based on the identification, releasing the wireless connection with the DU.

[0219] In some examples, the request sending manager 1030 can be configured as or otherwise support a unit for performing the following operations: sending a network address associated with the second core network service, a third service message associated with the second core network service, or both via the request.

[0220] In some examples, the request sending manager 1030 may be configured as or otherwise support a unit for performing the following operations: sending a second request to the DU to activate a third core network service provided by the service-based network, the third core network service being associated with a third service context for communicating with the third core network service, wherein the third service context is maintained at the UE based on the third core network service being in an inactive state at the UE. In some examples, the activation state manager 1035 may be configured as or otherwise support a unit for performing the following operations: based on the second request, receiving a second message from the DU indicating that activation of the third core network service has failed.

[0221] In some examples, the service context manager 1040 may be configured or otherwise support means for deleting the third service context from memory based on receiving the second message indicating that the activation of the third service context failed.

[0222] Fig.11A diagram of a system 1100 including a device 1105 supporting technology for service status in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a UE 115 as described herein, or include a component of the device 805, the device 905, or the UE 115. The device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, a code 1135, and a processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1145).

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

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

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

[0226] The processor 1140 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 1140 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 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks that support technology for service status in a service-based wireless network). For example, the device 1105 or a component of the device 1105 may include a processor 1140 and a memory 1130 coupled to the processor 1140, and the processor 1140 and the memory 1130 are configured to perform various functions described herein.

[0227] According to the examples disclosed herein, the communication manager 1120 may support wireless communication at the UE. For example, the communication manager 1120 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message with a first core network service provided by a service-based network via a DU, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based on the first core network service being active at the UE. The communication manager 1120 may be configured to or otherwise support a unit for performing the following operations: sending a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based on the second core network service being inactive at the UE. The communication manager 1120 may be configured to or otherwise support a unit for performing the following operations: receiving a message indicating activation of the second core network service at the UE from the DU in response to the request. The communication manager 1120 may be configured as or otherwise support means for communicating a second service message with the second core network service via a DU based on the activation of the second core network service at the UE according to the second service context.

[0228] By including or configuring the communication manager 1120 according to the examples as described herein, the device 1105 can support technologies that enable the UE 115 to subscribe to different core network services on an a la carte basis and activate and deactivate the corresponding core network services according to the needs or requirements of the corresponding UE 115. In this regard, various aspects of the present disclosure enable different core network services to be maintained in different activation states at the UE 115 according to the needs or requirements of the corresponding UE 115, and enable the core network services to be activated or deactivated independently of each other. Therefore, the techniques described herein can enable the UE 115 to activate only those core network services that are needed or desired, thereby reducing control signaling within the network and reducing power consumption at the UE 115. In addition, various aspects of the present disclosure enable the wireless device to maintain (e.g., store) context information for performing corresponding core network services based on the activation state of each corresponding core network service at the UE 115. In this regard, by enabling wireless devices to maintain context information for active and inactive core network services, the techniques described herein may facilitate fast and efficient service reestablishment when core network services are activated, thereby reducing control signaling used to activate core network services and improving the overall user experience.

[0229] In some examples, the communication manager 1120 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 can be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 can include instructions executable by the processor 1140 to cause the device 1105 to perform corresponding aspects of the techniques for service status in a service-based wireless network as described herein, or the processor 1140 and the memory 1130 can be otherwise configured to perform or support such operations.

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

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

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

[0233] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or various components thereof, may be examples of units for performing corresponding aspects of the techniques for service status in a service-based wireless network. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0234] In some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include the following that is configured as or otherwise supports means for performing the functions described in the present disclosure: 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. In some examples, a processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

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

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

[0237] According to an example as disclosed herein, the communication manager 1220 may support wireless communication at a DU. The communication manager 1220 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message between a UE and a first core network service provided by a service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the DU based on the first core network service being in an active state at the UE. The communication manager 1220 may be configured to or otherwise support a unit for performing the following operations: receiving a request to activate a second core network service provided by the service-based network at the UE from an inactive state to an active state, the second core network service being associated with a second service context for communicating with the second core network service. The communication manager 1220 may be configured to or otherwise support a unit for performing the following operations: based on the request, sending a message to the UE indicating activation of the second core network service at the UE. The communication manager 1220 may be configured as or otherwise support means for transmitting a second service message between the UE and the second core network service according to the second service context based on activation of the second core network service at the UE.

[0238] Additionally or alternatively, the communication manager 1220 may support wireless communications at a core network service provided by a service-based network according to an example as disclosed herein. For example, the communication manager 1220 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message with a UE via a DU according to a first UE context for communicating with the UE, the first UE context being maintained at the core network service based on the core network service being active at the UE. The communication manager 1220 may be configured to or otherwise support a unit for performing the following operations: receiving a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based on the message indicating the deactivation of the core network service at the UE. The communication manager 1220 may be configured to or otherwise support a unit for performing the following operations: receiving a request from the DU to activate the core network service at the UE. The communication manager 1220 may be configured as or otherwise support means for transmitting a second service message with the UE via the DU based on the first UE context and based on maintaining the first UE context in a memory and receiving a request to activate the core network service at the UE.

[0239] By including or configuring the communication manager 1220 according to examples as described herein, the device 1205 (e.g., a processor controlling or otherwise coupled to the receiver 1210, the transmitter 1215, the communication manager 1220, or a combination thereof) may support techniques that enable a UE 115 to subscribe to different core network services on an a la carte basis and to activate and deactivate the respective core network services according to the needs or requirements of the respective UE 115. In this regard, aspects of the present disclosure enable different core network services to be maintained at the UE 115 in different activation states according to the needs or requirements of the respective UE 115, and enable the core network services to be activated or deactivated independently of each other. Thus, the techniques described herein may enable the UE 115 to activate only those core network services that are needed or desired, thereby reducing control signaling within the network and reducing power consumption at the UE 115. Furthermore, aspects of the present disclosure enable the wireless device to maintain (e.g., store) context information for performing corresponding core network services based on the activation state of each corresponding core network service at the UE 115. In this regard, by enabling the wireless device to maintain context information for active and inactive core network services, the techniques described herein may facilitate fast and efficient service reestablishment when activating core network services, thereby reducing control signaling for activating core network services and improving the overall user experience.

[0240] Fig.13 A block diagram 1300 of a device 1305 supporting techniques for service status in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the device 1205 or UE 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0241] Receiver 1310 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 a protocol stack). The information may be passed to other components of device 1305. In some examples, receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

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

[0243] Device 1305 or its various components may be examples of units for performing corresponding aspects of the technology for service status in a service-based wireless system as described herein. For example, communication manager 1320 may include service message communication manager 1325, request reception manager 1330, activation state manager 1335, or any combination thereof. Communication manager 1320 may be an example of various aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its corresponding components may be configured to perform various operations (e.g., receive, acquire, monitor, output, send) using receiver 1310, transmitter 1315, or both or otherwise in cooperation with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 may receive information from receiver 1310, send information to transmitter 1315, or integrate with receiver 1310, transmitter 1315, or both in combination to obtain information, output information, or perform various other operations described herein.

[0244] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at the DU. The service message communication manager 1325 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message between the UE and a first core network service provided by the service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the DU based on the first core network service being in an active state at the UE. The request reception manager 1330 may be configured to or otherwise support a unit for performing the following operations: receiving a request to activate a second core network service provided by the service-based network from an inactive state to an active state at the UE, the second core network service being associated with a second service context for communicating with the second core network service. The activation state manager 1335 may be configured to or otherwise support a unit for performing the following operations: based on the request, sending a message to the UE indicating activation of the second core network service at the UE. The service message communication manager 1325 may be configured as or otherwise support means for transmitting a second service message between the UE and the second core network service according to the second service context based on activation of the second core network service at the UE.

[0245] Additionally or alternatively, the communication manager 1320 may support wireless communications at a core network service provided by a service-based network according to an example as disclosed herein. The service message communication manager 1325 may be configured as or otherwise support a unit for performing the following operations: transmitting a first service message with a UE via a DU according to a first UE context for communicating with the UE, the first UE context being maintained at the core network service based on the core network service being active at the UE. The activation state manager 1335 may be configured as or otherwise support a unit for performing the following operations: receiving a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based on the message indicating the deactivation of the core network service at the UE. The request reception manager 1330 may be configured as or otherwise support a unit for performing the following operations: receiving a request from the DU to activate the core network service at the UE. The service message communication manager 1325 may be configured as or otherwise support a unit for transmitting a second service message with the UE via the DU based on the first UE context and based on maintaining the first UE context in a memory and receiving a request to activate the core network service at the UE.

[0246] Fig.14 A block diagram 1400 of a communication manager 1420 supporting techniques for service status in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of devices for performing corresponding aspects of the techniques for service status in a service-based wireless system as described herein. For example, the communication manager 1420 may include a service message communication manager 1425, a request reception manager 1430, an activation state manager 1435, a wireless connection manager 1440, a service context manager 1445, a request transmission manager 1450, a UE context manager 1455, a resource allocation manager 1460, 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 virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0247] According to the examples disclosed herein, the communication manager 1420 may support wireless communication at the DU. The service message communication manager 1425 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message between the UE and a first core network service provided by the service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the DU based on the first core network service being in an active state at the UE. The request reception manager 1430 may be configured to or otherwise support a unit for performing the following operations: receiving a request to activate a second core network service provided by the service-based network from an inactive state to an active state at the UE, the second core network service being associated with a second service context for communicating with the second core network service. The activation state manager 1435 may be configured to or otherwise support a unit for performing the following operations: based on the request, sending a message to the UE indicating activation of the second core network service at the UE. In some examples, the service message communication manager 1425 may be configured as or otherwise support a unit for transmitting a second service message between the UE and the second core network service according to the second service context based on activation of the second core network service at the UE.

[0248] In some examples, activation state manager 1435 may be configured or otherwise support means for communicating a second message to the UE, the first core network service, or both, the second message indicating deactivation of the first core network service at the UE.

[0249] In some examples, resource allocation manager 1460 can be configured to or otherwise support a unit for reallocating a set of resources previously allocated for wireless communication between a UE and a first core network service to another UE, another core network service, or both, wherein the reallocation is based on the second message indicating deactivation of the first core network service.

[0250] In some examples, the deactivation of the first core network service is based on signaling from the first core network service, signaling from the UE, release of a wireless connection between the UE and the DU, a radio link failure, failure of one or more messages sent from the UE to the first core network service, or any combination thereof.

[0251] In some examples, the wireless connection manager 1440 may be configured as or otherwise support a unit for performing the following operations: based on a handover process from a second DU to the DU, establishing a wireless connection with the UE. In some examples, the service context manager 1445 may be configured as or otherwise support a unit for performing the following operations: based on establishing the wireless connection, obtaining the first service context associated with the first core network service from the first core network service, another core network service, or both, wherein transmitting the first service message is based on obtaining the first service context.

[0252] In some examples, request sending manager 1450 may be configured or otherwise support means for performing the following operations: based on receiving the request, sending the request to the second core network service. In some examples, activation state manager 1435 may be configured or otherwise support means for performing the following operations: based on sending the request, receiving a confirmation of the activation of the second core network service from the second core network service, wherein sending the message indicating the activation of the second core network service is based on the confirmation.

[0253] In some examples, the request receiving manager 1430 can be configured as or otherwise support a unit for performing the following operations: receiving, via the request, a network address associated with the second core network service, a third service message associated with the second core network service, or both, wherein sending the request to the second core network service is based on receiving the network address, the third service message, or both.

[0254] In some examples, the request reception manager 1430 may be configured to or otherwise support a unit for performing the following operations: receiving from the UE a second request to activate a third core network service provided by the service-based network at the UE, the third core network service being associated with a third service context for communicating with the third core network service. In some examples, the activation state manager 1435 may be configured to or otherwise support a unit for performing the following operations: based on the second request, sending to the UE a second message indicating that activation of the third core network service has failed.

[0255] In some examples, the activation state manager 1435 may be configured to or otherwise support a unit for performing the following operations: identifying that all core network services including the first core network service and the second core network service have been deactivated at the UE. In some examples, the wireless connection manager 1440 may be configured to or otherwise support a unit for performing the following operations: based on the identification, releasing the wireless connection with the UE.

[0256] Additionally or alternatively, the communication manager 1420 may support wireless communications at a core network service provided by a service-based network according to an example as disclosed herein. In some examples, the service message communication manager 1425 may be configured as or otherwise support a unit for performing the following operations: transmitting a first service message to a UE via a DU according to a first UE context for communicating with the UE, the first UE context being maintained at the core network service based on the core network service being active at the UE. In some examples, the activation state manager 1435 may be configured as or otherwise support a unit for performing the following operations: receiving a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based on the message indicating the deactivation of the core network service at the UE. In some examples, the request reception manager 1430 may be configured as or otherwise support a unit for performing the following operations: receiving a request from the DU to activate the core network service at the UE. In some examples, the service message communication manager 1425 can be configured as or otherwise support a unit for performing the following operations: transmitting a second service message to the UE via the DU based on the first UE context and based on maintaining the first UE context in a memory and receiving a request to activate the core network service at the UE.

[0257] In some examples, the request reception manager 1430 may be configured or otherwise support a unit for performing the following operations: based on the core network service being in an unconnected state at the second UE, receiving from the DU a second request to establish a service with the second UE. In some examples, the service context manager 1445 may be configured or otherwise support a unit for performing the following operations: based on the second request, sending to the DU a second message indicating a first service context for communicating with the core network service. In some examples, the UE context manager 1445 may be configured or otherwise support a unit for performing the following operations: based on sending the second message indicating the first service context, storing in a memory a second UE context associated with the second UE.

[0258] In some examples, the request reception manager 1430 may be configured as or otherwise support a unit for performing the following operations: based on a handover process from a second DU to the DU, receiving a second request for a first service context associated with wireless communication with the core network service from the DU. In some examples, the service message communication manager 1425 may be configured as or otherwise support a unit for performing the following operations: based on the second request, sending the first service context associated with the core network service to the DU, wherein transmitting the first service message may be based on the first service context.

[0259] In some examples, the activation state manager 1435 can be configured as or otherwise support a unit for performing the following operations: sending a second message to the DU indicating deactivation of the core network service at the UE, wherein receiving the message indicating the deactivation is based on the second message.

[0260] In some examples, the deactivation of the first core network service is based on signaling from the core network service, release of a wireless connection between the UE and the DU, a radio link failure, failure of one or more messages sent from the UE to the core network service, or any combination thereof.

[0261] Fig.15 A schematic diagram of a system 1500 including a device 1505 supporting technology for service status in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1505 may be an example of a device 1205, a device 1305, or a network entity 105 as described herein or a component including these devices. The device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1505 may include components that support output and acquisition of communications, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, a code 1530, and a processor 1535. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1540).

[0262] As described herein, the transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of sending or receiving wireless transmissions (e.g., simultaneously). The transceiver 1510 may also include a modem for modulating a signal, providing a modulated signal for transmission (e.g., via one or more antennas 1515, via a wired transmitter), receiving a modulated signal (e.g., from one or more antennas 1515, from a wired receiver), and demodulating a signal. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receiving or acquiring operations, or one or more interfaces coupled to one or more antennas 1510 configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1510 may include one or more processors or memory components, or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and one or more antennas 1515, or the transceiver 1520 and one or more antennas 1515 and one or more processors or memory components (e.g., processor 1535, or memory 1525, or both) may be included in a chip or chip assembly installed in the device 1505. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, mid-range communication link, fronthaul communication link 168).

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

[0264] The processor 1535 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1535 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 1535. The processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1525) so that the device 1505 performs various functions (e.g., functions or tasks that support the technology for the service state in a service-based wireless system). For example, the device 1505 or a component of the device 1505 may include a processor 1535 and a memory 1525 coupled to the processor 1535, and the processor 1535 and the memory 1525 are configured to perform various functions described herein. The processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions (e.g., by executing code 1530) to perform the functions of the device 1505. Processor 1535 can be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1505 (e.g., in memory 1525). In some implementations, processor 1535 can be a component of a processing system. A processing system can generally refer to a system or a series of machines or components that receive inputs and process inputs to generate an output set (which can be passed to, for example, other systems or components of device 1505). For example, a processing system of device 1505 can refer to a system including various other components or subcomponents of device 1505, such as processor 1535, transceiver 1510, communication manager 1520, or other components or combinations of components of device 1505. A processing system of device 1505 can be connected to other components of device 1505, and can process information (e.g., input or signal) received from other components, or output information to other components. For example, a chip or modem of device 1505 can include a processing system and one or more interfaces to output information, or obtain information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to input information and obtain information, as well as other implementations. In some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter so that the device 1505 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may be an interface between a processing system and a receiver, such as a chip or modem, so that the device 1505 can obtain information or signal input, and the information can be passed to the processing system. Those skilled in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0265] In some examples, bus 1540 can support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1540 can support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which can include communications performed within components of device 1505, or between different components of device 1505 that may be co-located or located in different locations (e.g., where device 1505 can refer to a system in which one or more of communication manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 can be located in one of the different components or divided between the different components).

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

[0267] According to the examples disclosed herein, the communication manager 1520 may support wireless communication at the DU. For example, the communication manager 1520 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message between a UE and a first core network service provided by a service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the DU based on the first core network service being in an active state at the UE. The communication manager 1520 may be configured to or otherwise support a unit for performing the following operations: receiving a request to activate a second core network service provided by the service-based network from an inactive state to an active state at the UE, the second core network service being associated with a second service context for communicating with the second core network service. The communication manager 1520 may be configured to or otherwise support a unit for performing the following operations: based on the request, sending a message to the UE indicating activation of the second core network service at the UE. The communication manager 1520 may be configured as or otherwise support means for transmitting a second service message between the UE and the second core network service according to the second service context based on activation of the second core network service at the UE.

[0268] Additionally or alternatively, the communication manager 1520 may support wireless communications at a core network service provided by a service-based network according to an example as disclosed herein. For example, the communication manager 1520 may be configured to or otherwise support a unit for performing the following operations: transmitting a first service message with a UE via a DU according to a first UE context for communicating with the UE, the first UE context being maintained at the core network service based on the core network service being active at the UE. The communication manager 1520 may be configured to or otherwise support a unit for performing the following operations: receiving a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based on the message indicating the deactivation of the core network service at the UE. The communication manager 1520 may be configured to or otherwise support a unit for performing the following operations: receiving a request from the DU to activate the core network service at the UE. The communication manager 1520 may be configured as or otherwise support means for transmitting a second service message with the UE via the DU based on the first UE context and based on maintaining the first UE context in a memory and receiving a request to activate the core network service at the UE.

[0269] By including or configuring the communication manager 1520 according to the examples as described herein, the device 1505 can support technologies that enable the UE 115 to subscribe to different core network services on an a la carte basis and activate and deactivate the corresponding core network services according to the needs or requirements of the corresponding UE 115. In this regard, various aspects of the present disclosure enable different core network services to be maintained at the UE 115 in different activation states according to the needs or requirements of the corresponding UE 115, and enable the core network services to be activated or deactivated independently of each other. Therefore, the techniques described herein can enable the UE 115 to activate only those core network services that are needed or desired, thereby reducing control signaling within the network and reducing power consumption at the UE 115. In addition, various aspects of the present disclosure enable the wireless device to maintain (e.g., store) context information for performing the corresponding core network business based on the activation state of each corresponding core network service at the UE 115. In this regard, by enabling wireless devices to maintain context information for active and inactive core network services, the techniques described herein may facilitate fast and efficient service reestablishment when core network services are activated, thereby reducing control signaling used to activate core network services and improving the overall user experience.

[0270] In some examples, the communication manager 1520 can be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) using the transceiver 1510, one or more antennas 1515, or any combination thereof, or in cooperation with the transceiver 1415, one or more antennas 1425, or any combination thereof. Although the communication manager 1520 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 can be supported or performed by the transceiver 1510, the processor 1535, the memory 1525, the code 1530, or any combination thereof. For example, the code 1530 can include instructions executable by the processor 1535 to cause the device 1505 to perform corresponding aspects of the technology for service status in a service-based wireless network, or the processor 1535 and the memory 1525 can be otherwise configured to perform or support such operations.

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

[0272] At 1605, the method may include: transmitting, via the DU, a first service message with a first core network service provided by a service-based network, the first service message being transmitted based on a first service context for communicating with the first core network service, the first service context being maintained at the UE based on the first core network service being active at the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described with reference to Fig.10 The described service message communication manager 1025 is executed.

[0273] At 1610, the method may include: sending a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based on the second core network service being in an inactive state at the UE. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a request sending manager 1030 as described in reference 10.

[0274] At 1615, the method may include: receiving a message from the DU indicating activation of the second core network service at the UE in response to the request. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be described with reference to Fig.10 The described activation state manager 1035 is executed.

[0275] At 1620, the method may include: transmitting a second service message with the second core network service via the DU based on the activation of the second core network service at the UE according to the second service context. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described with reference to Fig.10 The described service message communication manager 1025 is executed.

[0276] Fig.17A flow chart illustrating a method 1700 for supporting technology for service status in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or component thereof as described herein. Figures 1 to 7 as well as Figures 12 to 15 The network entity described herein performs. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0277] At 1705, the method may include: transmitting a first service message between the UE and a first core network service provided by a service-based network, the first service message being transmitted based on a first service context for communicating with the first core network service, the first service context being maintained at the DU based on the first core network service being active at the UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Fig.14 The described service message communication manager 1425 is executed.

[0278] At 1710, the method may include: receiving a request to activate a second core network service provided by the service-based network from an inactive state to the active state at the UE, the second core network service being associated with a second service context for communicating with the second core network service. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a request sending manager 1430 as described in reference 14.

[0279] At 1715, the method may include: based on the request, sending a message to the UE indicating activation of the second core network service at the UE. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be described with reference to Fig.14 The described activation state manager 1435 is executed.

[0280] At 1720, the method may include: based on the activation of the second core network service at the UE, transmitting a second service message between the UE and the second core network service according to the second service context. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described with reference to Fig.14 The described service message communication manager 1425 is executed.

[0281] Fig.18 A flow chart illustrating a method 1800 for supporting technology for service status in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or component thereof as described herein. Figures 1 to 7 and Figures 12 to 15 The network entity described herein performs. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0282] At 1805, the method may include: transmitting, via the DU, a first service message to the UE based on a first UE context for communicating with the UE, the first UE context being maintained at the core network service based on the core network service being active at the UE. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described with reference to Fig.14 The described service message communication manager 1425 is executed.

[0283] At 1810, the method may include: receiving a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based on the message indicating the deactivation of the core network service at the UE. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by reference to Fig.14 The described activation state manager 1435 is executed.

[0284] At 1815, the method may include: receiving a request from the DU to activate the core network service at the UE. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a request reception manager 1430 as described in reference 14.

[0285] At 1820, the method may include: transmitting a second service message with the UE via the DU based on the first UE context and based on maintaining the first UE context in a memory and receiving a request to activate the core network service at the UE. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Fig.14 The described service message communication manager 1425 is executed.

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

[0287] Aspect 1. A method for wireless communication at a UE, comprising: transmitting a first service message to a first core network service provided by a service-based network via a DU, the first service message being transmitted based on a first service context for communicating with the first core network service, the first service context being maintained at the UE at least partially based on the first core network service being in an active state at the UE; sending a request to the DU to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE at least partially based on the second core network service being in an inactive state at the UE; receiving a message indicating activation of the second core network service at the UE from the DU in response to the request; and transmitting a second service message to the second core network service via the DU based on the second service context, at least partially based on the activation of the second core network service at the UE.

[0288] Aspect 2: The method according to Aspect 1 also includes: sending a second request to the DU to establish a service with the third core network service based at least in part on the third core network service being in an unconnected state at the UE; receiving a second message from the DU based at least in part on the second request, the second message indicating a third service context for communicating with the third core network service; and storing the third service context in a memory based at least in part on converting the third core network service from the unconnected state to one of the active state or the inactive state at the UE.

[0289] Aspect 3: The method according to any one of Aspects 1 to 2 also includes: transmitting a second message with the DU indicating deactivation of the first core network service at the UE, wherein the first service context is maintained at the UE at least partially based on the deactivation.

[0290] Aspect 4: A method according to Aspect 3, wherein the deactivation of the first core network service is at least partially based on signaling from the first core network service, release of the wireless connection between the UE and the DU, radio link failure, failure of one or more messages sent from the UE to the first core network service, or any combination thereof.

[0291] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: identifying that all core network services including the first core network service and the second core network service have been deactivated at the UE; and releasing the wireless connection with the DU based at least in part on the identification.

[0292] Aspect 6: The method according to any one of aspects 1 to 5 further includes: sending, via the request, a network address associated with the second core network service, a third service message associated with the second core network service, or both.

[0293] Aspect 7: The method according to any one of Aspects 1 to 6 further includes: sending a second request to the DU to activate a third core network service provided by the service-based network, the third core network service being associated with a third service context for communicating with the third core network service, wherein the third service context is maintained at the UE at least in part based on the third core network service being in an inactive state at the UE; and receiving a second message from the DU indicating a failure in activation of the third core network service based at least in part on the second request.

[0294] Aspect 8: The method according to aspect 7 further includes: deleting the third service context from the memory based at least in part on receiving the second message indicating the activation failure of the third core network context.

[0295] Aspect 9: A method for wireless communication at a DU, comprising: transmitting a first service message between a UE and a first core network service provided by a service-based network, the first service message being transmitted based on a first service context for communicating with the first core network service, the first service context being maintained at the DU based at least in part on the first core network service being in an active state at the UE; receiving a request to activate a second core network service provided by the service-based network from an inactive state to an active state at the UE, the second core network service being associated with a second service context for communicating with the second core network service; sending a message indicating activation of the second core network service at the UE based at least in part on the request; and transmitting a second service message between the UE and the second core network service based on the second service context based at least in part on the activation of the second core network service at the UE.

[0296] Aspect 10: The method according to aspect 9 further includes: transmitting a second message indicating deactivation of the first core network service at the UE with the UE, the first core network service, or both.

[0297] Aspect 11: The method according to Aspect 10 also includes: reallocating a resource set previously allocated for wireless communication between the UE and the first core network service to another UE, another core network service, or both, wherein the reallocation is at least partially based on the second message indicating the deactivation of the first core network service.

[0298] Aspect 12: A method according to any one of Aspects 10 to 11, wherein the deactivation of the first core network service is at least partially based on signaling from the first core network service, signaling from the UE, release of the wireless connection between the UE and the DU, radio link failure, failure of one or more messages sent from the UE to the first core network service, or any combination thereof.

[0299] Aspect 13: The method according to any one of Aspects 9 to 12 also includes: establishing a wireless connection with the UE based at least in part on a switching process from a second DU to the DU; and obtaining the first service context associated with the first core network service from the first core network service, another core network service, or both based at least in part on establishing the wireless connection, wherein transmitting the first service message is based at least in part on obtaining the first service context.

[0300] Aspect 14: The method according to any one of Aspects 9 to 13 further includes: sending the request to the second core network service based at least in part on receiving the request; and receiving confirmation of the activation of the second core network service from the second core network service based at least in part on sending the request, wherein sending the message indicating the activation of the second core network service is based at least in part on the confirmation.

[0301] Aspect 15: The method according to Aspect 14 further includes: receiving, via the request, a network address associated with the second core network service, a third service message associated with the second core network service, or both, wherein sending the request to the second core network service is at least partially based on receiving the network address, the third service message, or both.

[0302] Aspect 16: The method according to any one of Aspects 9 to 15 further includes: receiving a second request from the UE to activate a third core network service provided by the service-based network at the UE, the third core network service being associated with a third service context for communicating with the third core network service; and sending a second message to the UE indicating a failure in activation of the third core network service based at least in part on the second request.

[0303] Aspect 17: The method according to any one of Aspects 9 to 16 also includes: identifying that all core network services including the first core network service and the second core network service have been deactivated at the UE; and releasing the wireless connection with the UE at least partially based on the identification.

[0304] Aspect 18: A method for wireless communication at a core network service provided by a service-based network, comprising: transmitting a first service message to a UE via a DU based on a first UE context used for communicating with the UE, the first UE context being maintained at the core network service based at least in part on the core network service being active at the UE; receiving a message from the DU indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based at least in part on the message indicating the deactivation of the core network service at the UE; receiving a request to activate the core network service at the UE from the DU; and transmitting a second service message to the UE via the DU based on the first UE context and at least in part on maintaining the first UE context in the memory and receiving the request to activate the core network service at the UE.

[0305] Aspect 19: The method according to Aspect 18 also includes: receiving a second request from the DU to establish a service with the second UE based at least in part on the core network service being in an unconnected state at the second UE; sending a second message to the DU indicating a first service context for communicating with the core network service based at least in part on the second request; and storing a second UE context associated with the second UE in a memory based at least in part on sending the second message indicating the first service context.

[0306] Aspect 20: The method according to any one of Aspects 18 to 19 further includes: receiving a second request for a first service context associated with wireless communication with the core network service from the DU at least partially based on a switching process from a second DU to the DU; and sending the first service context associated with the core network service to the DU at least partially based on the second request, wherein transmitting the first service message is at least partially based on the first service context.

[0307] Aspect 21: The method according to any one of Aspects 18 to 20 further includes: sending a second message to the DU indicating deactivation of the core network service at the UE, wherein receiving the message indicating the deactivation is at least partially based on the second message.

[0308] Aspect 22: A method according to any one of Aspects 18 to 21, wherein the deactivation of the core network service is at least partially based on signaling from the core network service, release of the wireless connection between the UE and the DU, radio link failure, failure of one or more messages sent from the UE to the core network service, or any combination thereof.

[0309] Aspect 23: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions, which are stored in the memory and can be executed by the processor to enable the apparatus to perform a method according to any one of Aspects 1 to 8.

[0310] Aspect 24: An apparatus for wireless communication at a UE, comprising at least one unit for performing the method according to any one of aspects 1 to 8.

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

[0312] Aspect 26: An apparatus for wireless communication at a DU, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 9 to 17.

[0313] Aspect 27: An apparatus for wireless communication at a DU, comprising at least one unit for performing the method according to any one of aspects 9 to 17.

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

[0315] Aspect 29. An apparatus for wireless communication at a core network service provided by a service-based network, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any of Aspects 18 to 22.

[0316] Aspect 30: An apparatus for wireless communication at a core network service provided by a service-based network, comprising at least one means for performing the method according to any of aspects 18 to 22.

[0317] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a core network service provided by a service-based network, the code comprising instructions executable by a processor to perform the method according to any of aspects 18 to 22.

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

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

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

[0321] The various illustrative blocks and components described in conjunction 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 in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).

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

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

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

[0325] The terms "determine" or "determining" encompass a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), ascertaining, etc. Additionally, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Also, "determining" may include solving, obtaining, selecting, choosing, establishing, and other such similar actions.

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

[0327] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." For the purpose of providing an understanding of the described techniques, the detailed description includes specific details. 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.

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

Claims

1. A method for wireless communication at a user equipment (UE): transmitting, via a distributed unit, a first service message with a first core network service provided by a service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based at least in part on the first core network service being active at the UE; sending, to the distributed unit, a request to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based at least in part on the second core network service being inactive at the UE; receiving, from the distributed unit in response to the request, a message indicating activation of the second core network service at the UE; and Based at least in part on the activation of the second core network service at the UE, a second service message is communicated with the second core network service via a distributed unit according to the second service context.

2. The method according to claim 1, further comprising: Based at least in part on a third core network service being in an unconnected state at the UE, sending to the distributed unit a second request to establish service with the third core network service; receiving, based at least in part on the second request, from the distributed unit a second message indicating a third service context for communicating with the third core network service; as well as Based at least in part on transitioning the third core network service from the unconnected state to one of the active state or the inactive state at the UE, storing the third service context in a memory.

3. The method according to claim 1, further comprising: A second message is communicated with the distributed unit indicating deactivation of the first core network service at the UE, wherein the first service context is maintained at the UE based at least in part on the deactivation.

4. The method according to claim 3, wherein: The deactivation of the first core network service is based at least in part on signaling from the first core network service, release of a wireless connection between the UE and the distributed unit, a radio link failure, a failure of one or more messages sent from the UE to the first core network service, or any combination thereof.

5. The method according to claim 1, further comprising: identifying that all core network services including the first core network service and the second core network service have been deactivated at the UE; as well as Based at least in part on the identification, a wireless connection with the distributed unit is released.

6. The method according to claim 1, further comprising: Via the request, a network address associated with the second core network service, a third service message associated with the second core network service, or both are sent.

7. The method according to claim 1, further comprising: sending, to the distributed unit, a second request to activate a third core network service provided by the service-based network, the third core network service being associated with a third service context for communicating with the third core network service, wherein the third service context is maintained at the UE based at least in part on the third core network service being inactive at the UE; and Based at least in part on the second request, a second message is received from the distributed unit indicating that activation of the third core network service has failed.

8. The method according to claim 7, further comprising: Based at least in part on receiving the second message indicating that the activation of the third core network context has failed, deleting the third service context from memory.

9. A method for wireless communication at a distributed unit, comprising: transmitting a first service message between a user equipment (UE) and a first core network service provided by a service-based network, the first service message being transmitted based on a first service context for communicating with the first core network service, the first service context being maintained at the distributed unit based at least in part on the first core network service being active at the UE; receiving a request to activate, at the UE, from an inactive state to the active state, a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service; Based at least in part on the request, sending a message to the UE indicating activation of the second core network service at the UE; as well as Based at least in part on the activation of the second core network service at the UE, a second service message is communicated between the UE and the second core network service according to the second service context.

10. The method according to claim 9, further comprising: A second message indicating deactivation of the first core network service at the UE is transmitted with the UE, the first core network service, or both.

11. The method according to claim 10, further comprising: Reallocating a set of resources previously allocated for wireless communication between the UE and the first core network service to another UE, another core network service, or both, wherein the reallocation is based at least in part on the second message indicating the deactivation of the first core network service.

12. The method according to claim 10, wherein: The deactivation of the first core network service is based at least in part on signaling from the first core network service, signaling from the UE, release of a wireless connection between the UE and the distributed unit, a radio link failure, a failure of one or more messages sent from the UE to the first core network service, or any combination thereof.

13. The method according to claim 9, further comprising: establishing a wireless connection with the UE based at least in part on a handover process from a second distributed unit to the distributed unit; as well as Based at least in part on establishing the wireless connection, obtaining the first service context associated with the first core network service from the first core network service, another core network service, or both, wherein transmitting the first service message is based at least in part on obtaining the first service context.

14. The method according to claim 9, further comprising: Based at least in part on receiving the request, sending the request to the second core network service; as well as Based at least in part on sending the request, receiving, from the second core network service, a confirmation of the activation of the second core network service, wherein sending the message indicating the activation of the second core network service is based at least in part on the confirmation.

15. The method according to claim 14, further comprising: Via the request, a network address associated with the second core network service, a third service message associated with the second core network service, or both are received, wherein sending the request to the second core network service is at least partially based on receiving the network address, the third service message, or both.

16. The method according to claim 9, further comprising: receiving, from the UE, a second request to activate a third core network service provided at the UE by the service-based network, the third core network service being associated with a third service context for communicating with the third core network service; as well as Based at least in part on the second request, a second message is sent to the UE indicating that activation of the third core network service has failed.

17. The method according to claim 9, further comprising: identifying that all core network services including the first core network service and the second core network service have been deactivated at the UE; as well as Based at least in part on the identification, a radio connection with the UE is released.

18. A method for wireless communication at a core network service provided by a service-based network, comprising: transmitting, via a distributed unit, a first service message with a user equipment (UE) according to a first UE context for communicating with the UE, the first UE context being maintained at the core network service based at least in part on the core network service being active at the UE; receiving a message from the distributed unit indicating deactivation of the core network service at the UE, wherein the first UE context is maintained in a memory based at least in part on the message indicating the deactivation of the core network service at the UE; receiving, from the distributed unit, a request to activate the core network service at the UE; and A second service message is communicated with the UE via the distributed unit according to the first UE context and based at least in part on maintaining the first UE context in a memory and receiving the request to activate the core network service at the UE.

19. The method according to claim 18, further comprising: receiving, from the distributed unit, a second request to establish a service with the second UE based at least in part on the core network service being in an unconnected state at the second UE; Based at least in part on the second request, sending, to the distributed unit, a second message indicating a first service context for communicating with the core network service; as well as Based at least in part on sending the second message indicating the first service context, storing in a memory a second UE context associated with the second UE.

20. The method of claim 18, further comprising: receiving, from the distributed unit, a second request for a first service context associated with wireless communications with the core network service based at least in part on a handoff procedure from a second distributed unit to the distributed unit; as well as Based at least in part on the second request, the first service context associated with the core network service is sent to the distributed unit, wherein transmitting the first service message is based at least in part on the first service context.

21. The method of claim 18, further comprising: A second message is sent to the distributed unit indicating deactivation of the core network service at the UE, wherein receiving the message indicating the deactivation is based at least in part on the second message.

22. The method according to claim 18, wherein: The deactivation of the core network service is based at least in part on signaling from the core network service, release of a wireless connection between the UE and the distributed unit, a radio link failure, a failure of one or more messages sent from the UE to the core network service, or any combination thereof.

23. An apparatus for wireless communication at a user equipment (UE): processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: transmitting, via a distributed unit, a first service message with a first core network service provided by a service-based network, the first service message being transmitted according to a first service context for communicating with the first core network service, the first service context being maintained at the UE based at least in part on the first core network service being active at the UE; sending, to the distributed unit, a request to activate a second core network service provided by the service-based network, the second core network service being associated with a second service context for communicating with the second core network service, wherein the second service context is maintained at the UE based at least in part on the second core network service being inactive at the UE; receiving, from the distributed unit in response to the request, a message indicating activation of the second core network service at the UE; and Based at least in part on the activation of the second core network service at the UE, a second service message is communicated with the second core network service via a distributed unit according to the second service context.

24. The device according to claim 23, wherein: The instructions are also executable by the processor to cause the device to: Based at least in part on a third core network service being in an unconnected state at the UE, sending to the distributed unit a second request to establish service with the third core network service; receiving, based at least in part on the second request, from the distributed unit a second message indicating a third service context for communicating with the third core network service; as well as Based at least in part on transitioning the third core network service from the unconnected state to one of the active state or the inactive state at the UE, storing the third service context in a memory.

25. The device according to claim 23, wherein: The instructions are also executable by the processor to cause the device to: A second message is communicated with the distributed unit indicating deactivation of the first core network service at the UE, wherein the first service context is maintained at the UE based at least in part on the deactivation.

26. The device according to claim 25, wherein The deactivation of the first core network service is based at least in part on signaling from the first core network service, release of a wireless connection between the UE and the distributed unit, a radio link failure, a failure of one or more messages sent from the UE to the first core network service, or any combination thereof.

27. The device according to claim 23, wherein: The instructions are also executable by the processor to cause the device to: identifying that all core network services including the first core network service and the second core network service have been deactivated at the UE; as well as Based at least in part on the identification, a wireless connection with the distributed unit is released.

28. The device according to claim 23, wherein: The instructions are also executable by the processor to cause the device to: Via the request, a network address associated with the second core network service, a third service message associated with the second core network service, or both are sent.

29. The device according to claim 23, wherein: The instructions are also executable by the processor to cause the device to: sending, to the distributed unit, a second request to activate a third core network service provided by the service-based network, the third core network service being associated with a third service context for communicating with the third core network service, wherein the third service context is maintained at the UE based at least in part on the third core network service being inactive at the UE; and Based at least in part on the second request, a second message is received from the distributed unit indicating that activation of the third core network service has failed.

30. The device according to claim 29, wherein: The instructions are also executable by the processor to cause the device to: Based at least in part on receiving the second message indicating that the activation of the third core network context has failed, deleting the third service context from memory.

Images