Techniques for service establishment 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 identify a set of core network services provided by a service-based network interfaced with a radio access network (RAN) associated with a network entity (e.g., via signaling from the network or based on a subscriber identity module (SIM)). Each of the respective core network services may be associated with a corresponding network address. The UE may send a service request to a network address associated with a core network service included within the set of provided core network services, and may receive a service context for communicating with the core network service in response to the service request. The UE may then communicate service messages with the core network service according to the received service context (via the network entity).

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 948,039, filed by Griot et al. on September 19, 2022, and entitled “TECHNIQUESFOR SERVICE ESTABLISHMENT IN ASERVICE-BASED WIRELESS SYSTEM”; the above application is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

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

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

[0005] In the context of a service-based wireless system, a random access network (RAN) may interface with a service-based network that offers or provides various core network services. Each respective core network service may be hosted or provided by a different operator or entity and may be associated with a different set of parameters for communicating with the respective core network service. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting technology for service establishment in a service-based wireless system. In general, aspects of the present disclosure relate to signaling and other mechanisms that enable a user equipment (UE) to establish a wireless connection in a service-based network such as a sixth generation (6G) network. In particular, aspects of the present disclosure can support signaling between a UE, a network entity (e.g., a distributed unit (DU)), and a core network service based on a service-based network architecture, which enables the UE to establish and maintain connections with different core network services provided by the network. For example, a UE can establish a connection with a network entity of a radio access network (RAN), and can receive control signaling indicating a core network service provided by a service-based network connected to the RAN with an interface. The control signaling can additionally indicate a network address for each of the provided core network services. The UE can then send a service request to the network address of the provided core network service (via a relay of the network entity), and receive a service context for communicating with the core network service (via a relay of the network entity). The UE can then communicate with the core network service based on the service context (via a relay of the network entity).

[0007] A method for wireless communication at a UE is described. The method may include identifying first control information indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with a DU, the first control information indicating a set of multiple network addresses associated with the set of multiple core network services, sending a service request indicating a first core network service in the set of multiple core network services based on the first control information, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address, receiving control signaling indicating a first service context for communicating with the first core network service based on the service request, and sending a first service message including first service data for the first core network service and the first network address according to the first service context.

[0008] 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 are executable by the processor to enable the device to identify first control information, the first control information indicating a set of multiple core network services provided by a service-based network configured to be interfaced with a RAN associated with a DU, the first control information indicating a set of multiple network addresses associated with the set of multiple core network services, send a service request indicating a first core network service in the set of multiple core network services based on the first control information, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address, receive control signaling indicating a first service context for communicating with the first core network service based on the service request, and send a first service message including first service data for the first core network service and the first network address according to the first service context.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include means for identifying first control information indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with a DU, the first control information indicating a set of multiple network addresses associated with the set of multiple core network services, means for sending a service request indicating a first core network service in the set of multiple core network services based on the first control information, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address, means for receiving control signaling indicating a first service context for communicating with the first core network service based on the service request, and means for sending a first service message including first service data for the first core network service and the first network address according to the first service context.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: identifying first control information indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with a DU, the first control information indicating a set of multiple network addresses associated with the set of multiple core network services, sending a service request indicating a first core network service in the set of multiple core network services based on the first control information, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address, receiving control signaling indicating a first service context for communicating with the first core network service based on the service request, and sending a first service message including first service data for the first core network service and the first network address according to the first service context.

[0011] 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 query for the set of the multiple core network services based on establishing a wireless connection between the UE and the DU, and receiving first control information in response to the query.

[0012] 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 network address associated with a core network discovery service provided by the service-based network from the DU, wherein the query can be sent to the core network discovery service based on the network address.

[0013] 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: sending capability information associated with the UE via the query, wherein the set of the plurality of core network services may be based on the capability information.

[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: receiving an indication of a second core network service from the set of multiple core network services via a first service context for communicating with the first core network service, sending a second service request indicating the second core network service, the second service request including a second network address associated with the second core network service, and receiving third control signaling indicating a second service context for communicating with the second core network service based on the second service request, wherein transmitting the first service message can be based on receiving the second service context.

[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: transmitting a second service message including second service data for the second core network service and the second network address according to the second service context, wherein transmitting the first service message can be based on transmitting the second service message.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second core network service includes a security service associated with the first core network service, and the second service context includes authentication information, a key agreement, or both.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the service request, the first service message, or both may be sent to the DU to be relayed to a first network address associated with the first core network service.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first service context includes a radio access network configuration for communicating with the DU as part of the first core network service.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving additional control signaling including the first control information via a wireless connection between the UE and the DU.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first control information may be identified based on a subscriber identity module (SIM) associated with the UE.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each core network service in the set of multiple core network services can be associated with a corresponding API in the set of multiple application programming interfaces (APIs).

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple core network services includes mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0023] A method for wireless communication at a DU is described. The method may include receiving a service request from a UE, the service request indicating a first core network service from a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, wherein the set of multiple core network services is associated with multiple network addresses, the service request includes a first network address associated with the first core network service, the set of multiple network addresses includes the first network address, sending the service request to the first network address, sending control signaling received from the first core network service to the UE based on the service request, the control signaling indicating a first service context for communication between the UE and the first core network service, and transmitting a first service message received from the UE to the first core network service according to the first service context, the first service message including first service data for the first core network service and the first network address.

[0024] An apparatus for wireless communication at a DU is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receive a service request from a UE, the service request indicating a first core network service from a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, wherein the set of multiple core network services is associated with multiple network addresses, the service request includes a first network address associated with the first core network service, the set of multiple network addresses includes the first network address, send the service request to the first network address, send control signaling received from the first core network service to the UE based on the service request, the control signaling indicating a first service context for communication between the UE and the first core network service, and transmit a first service message received from the UE to the first core network service according to the first service context, the first service message including first service data for the first core network service and the first network address.

[0025] Another apparatus for wireless communication at a DU is described. The apparatus may include means for receiving a service request from a UE, the service request indicating a first core network service from a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, wherein the set of multiple core network services is associated with multiple network addresses, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address, means for sending the service request to the first network address, means for sending control signaling received from the first core network service to the UE based on the service request, the control signaling indicating a first service context for communication between the UE and the first core network service, and means for transmitting a first service message received from the UE to the first core network service according to the first service context, the first service message including first service data for the first core network service and the first network address.

[0026] 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: receiving a service request from a UE, the service request indicating a first core network service from a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, wherein the set of multiple core network services is associated with multiple network addresses, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address, sending the service request to the first network address, sending control signaling received from the first core network service to the UE based on the service request, the control signaling indicating a first service context for communication between the UE and the first core network service, and transmitting a first service message received from the UE to the first core network service according to the first service context, the first service message including first service data for the first core network service and the first network address.

[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: sending a second control signaling to the UE indicating a set of multiple core network services provided by the service-based network, the second control signaling indicating a set of multiple network addresses associated with the set of multiple core network services, wherein receiving the service request can be based on sending the second control signaling.

[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: sending a query for the set of the multiple core network services, and receiving an indication of the set of the multiple core network services in response to the query, wherein sending the control signaling may be based on receiving the indication of the set of the multiple core network services.

[0029] 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 network address of a core network discovery service provided by the service-based network to the UE, wherein the query can be received from the UE based on the network address and sent to the core network discovery service.

[0030] 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 capability information associated with the UE via the query, wherein the set of the plurality of core network services may be based on the capability information.

[0031] 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 an indication of a second core network service in the set of the multiple core network services via a first service context for communicating with the first core network service, receiving a second service request indicating the second core network service from the UE, the second service request including a second network address associated with the second core network service, sending the second service request to the second network address, and sending second control signaling received from the second core network service to the UE based on the second service request, the second control signaling indicating a second service context for communication between the UE and the second core network service, wherein transmitting the first service message can be based on transmitting the second service context.

[0032] 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: transmitting a second service message received from the UE to the second core network service according to the second service context, the second service message including second service data for the second core network service and the second network address, wherein transmitting the first service message can be based on transmitting the second service message.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second core network service includes a security service associated with the first core network service, and the second service context includes authentication information, a key agreement, or both.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first service context includes a radio access network configuration for communicating with the UE as part of the first core network service.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each core network service in the set of multiple core network services can be associated with a corresponding API in the set of multiple APIs.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple core network services includes mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0037] A method for wireless communication at a first core network service is described. The method may include receiving a service request indicating the first core network service from a UE via a DU, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, sending first control signaling to the UE via the DU based on the service request, the first control signaling indicating a first service context for communicating with the first core network service, and receiving a first service message including first service data for the first core network service and the first network address according to the first service context.

[0038] An apparatus for wireless communication at a first core network service is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receiving a service request indicating the first core network service from a UE via a DU, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, sending first control signaling to the UE via the DU based on the service request, the first control signaling indicating a first service context for communicating with the first core network service, and receiving a first service message including first service data for the first core network service and the first network address according to the first service context.

[0039] Another apparatus for wireless communication at a first core network service is described. The apparatus may include means for receiving a service request indicating a first core network service from a UE via a DU, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, means for sending first control signaling to the UE via the DU based on the service request, the first control signaling indicating a first service context for communicating with the first core network service, and means for receiving a first service message including first service data for the first core network service and the first network address according to the first service context.

[0040] A non-transitory computer-readable medium storing code for wireless communication at a first core network service is described. The code may include instructions executable by a processor to perform the following operations: receiving a service request indicating the first core network service from a UE via a DU, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, sending first control signaling to the UE via the DU based on the service request, the first control signaling indicating a first service context for communicating with the first core network service, and receiving a first service message including first service data for the first core network service and the first network address according to the first service context.

[0041] 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 an indication of a second core network service in the set of multiple core network services via a first service context for communicating with the first core network service, wherein receiving the first service message can be based on the indication of the second core network service.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second core network service includes a security service associated with the first core network service.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first service context includes a radio access network configuration for communication between the UE and the DU as part of the first core network service.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each core network service in the set of multiple core network services can be associated with a corresponding API in the set of multiple APIs.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple core network services includes mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0046] A method of wirelessly communicating at a core network discovery service is described. The method may include receiving, via a DU, from a UE a query for a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, and sending first control signaling indicating the set of multiple core network services to the DU for relay to the UE, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services.

[0047] An apparatus for wireless communication at a core network discovery service is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receiving a query from a UE via a DU for a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, and sending first control signaling indicating the set of multiple core network services to the DU for relay to the UE, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services.

[0048] Another apparatus for wirelessly communicating at a core network discovery service is described. The apparatus may include means for receiving, via a DU, from a UE a query for a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, and means for sending first control signaling indicating the set of multiple core network services to the DU for relay to the UE, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services.

[0049] A non-transitory computer-readable medium storing code for wireless communication at a core network discovery service is described. The code may include instructions executable by a processor to: receive a query from a UE via a DU for a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, and send first control signaling indicating the set of multiple core network services to the DU for relay to the UE, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services.

[0050] 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 network address associated with the core network discovery service provided by the service-based network to the DU, wherein the query can be received based on the network address.

[0051] 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 capability information associated with the UE via the query, wherein the set of the plurality of core network services may be based on the capability information.

[0052] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each core network service in the set of multiple core network services can be associated with a corresponding API in the set of multiple APIs.

[0053] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the set of multiple core network services includes mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0060] Figure 8 A block diagram of a communications manager supporting techniques for service establishment in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

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

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

[0063] Fig.12 A block diagram of a communications manager supporting techniques for service establishment in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

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

[0065] Figures 14 to 17 A flow chart illustrating a method of supporting techniques for service establishment in a service-based wireless system in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION

[0066] 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 many back-end (e.g., core network) devices associated with one or more functions for the system. This layered structure may cause processing and other functions to be performed at multiple devices (e.g., duplicate processing or capabilities across multiple back-end devices), resulting in wasted resources and excessive power consumption. Additionally, the back-end architecture of some wireless systems may be owned and maintained by a few operators, which may make it difficult for other parties / entities to integrate with these systems and may complicate the ability of these systems to provide customized services and functions to wireless devices.

[0067] In contrast, some wireless systems (e.g., sixth generation (6G) systems) may exhibit a flatter service-based architecture, in which a radio access network (RAN) (e.g., a network entity) interfaces with a service-based network to connect UEs to core network services maintained at various network addresses within the service-based network. In the context of a service-based system, operations and functions that might otherwise be performed by a few centralized backend components (e.g., in some systems) may be distributed across multiple core network services that may be hosted at different network addresses, such as in a cloud-based architecture. Thus, a UE in a service-based system may be able to establish and maintain connections to different core network services or groups thereof on a à la carte basis (e.g., "subscribe" to different core network services or groups thereof), each of which offers or provides respective network functions or services. 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 individual characteristics or needs of the respective UE.

[0068] In some wireless systems, the RAN may interface with a service-based network that provides various core network services and may relay communications between the UE and the corresponding core network services. In particular, the UE may subscribe to various core network services provided by the service-based network. However, each corresponding core network service may be hosted or provided by a different operator or entity and may be associated with a different set of parameters for communicating with the corresponding core network service. In other words, the communication parameters used to communicate with one core network service may not be used to communicate with another core network service.

[0069] Thus, aspects of the present disclosure relate to signaling and other mechanisms that enable a UE to establish a wireless connection in a service-based network (e.g., a 6G network). In particular, aspects of the present disclosure relate to signaling between a UE, a network entity (e.g., a distributed unit (DU)), and a core network service of a service-based network architecture that enables the UE to establish and maintain connections with different services provided by the network. Thus, the techniques described herein may enable a UE to obtain a service context for each corresponding core network service to which the UE subscribes, wherein the service context includes core network service-specific communication parameters for communicating with the corresponding core network service.

[0070] For example, the UE may establish a connection with the DU of the network entity and may receive control signaling indicating the core network services provided by the network and the network address of each core network service provided. The UE may then send a service request to the network address of the provided core network service (via the relay of the DU) and may receive a service context for communicating with the core network service (via the relay of the PDU). The UE may then communicate with the core network service (via the DU) based on the service context.

[0071] In some aspects, a UE may be able to request core network services provided by a network. For example, a UE may be able to query a discovery service (e.g., a core network discovery service) that is configured to provide a list of provided core network services that can be accessed by each querying UE. The core network services indicated to the UE as available may be based on the capabilities of each respective UE. Some core network services may include or depend on other network function services. For example, in order for a UE to subscribe to / communicate with a first core network service, the UE may also be required to subscribe to / communicate with a second core network service associated with the first core network service.

[0072] Aspects of the disclosure are initially described in the context of wireless communication systems. Additional aspects of the disclosure are described in the context of example network architectures and example process flows. Aspects of the disclosure are also illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams relating to techniques for service establishment in a service-based wireless system.

[0073] Figure 1An example of a wireless communication system 100 that supports techniques for service establishment 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.

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

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

[0076] 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 yet another aspect of the example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0077] In some examples, the network entities 105 can communicate with the service-based network 130, or communicate with each other, or communicate with 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 fronthaul communication link 168 (e.g., between the radio unit 170 and the distributed unit 165). The backhaul communication link 120 or the fronthaul communication link 168, or other communication 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.

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

[0079] One or more network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base station transceiver, a radio base station, an access point, a radio transceiver, a node B, an evolved node B (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 a CN / RAN service 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).

[0080] Additionally, in some examples, one or more network entities 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of 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 (non-RT 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 disaggregated RAN architecture may be implemented as virtual units (eg, virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0081] The functional division between components (e.g., CU, DU, and RU) is flexible and can support different functions, depending on which functions are performed at the component (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of 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 higher 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 the 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 at least partially controlled by the CU. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional division between the CU and DU 165 or between the DU 165 and the RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of the CU, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU, DU 165, or RU 170). The DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., an open fronthaul (FH) interface). In some examples, the fronthaul communication link 168 may be implemented according to interfaces (e.g., channels) between layers of a protocol stack supported by the various network entities 105 communicating via such a communication link.

[0082] 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., an IAB donor) may communicate with one or more additional network entities 105 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 a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., antennas of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (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.

[0083] Where the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the techniques for capability indication for multiple services in a service-based wireless system 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 additionally or alternatively 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).

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

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

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

[0087] 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 identified based on a channel grid for discovery by a UE 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be performed by a UE 115 via the carrier, or may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., with the same or different radio access technology).

[0088] The communication links 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 an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

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

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

[0091] One or more digital schemes for a carrier may be supported, and the digital schemes may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs having the same or different digital schemes. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP of 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.

[0092] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which 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).

[0093] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of a cyclic prefix added in front of each symbol period). In some wireless communication systems 100, a time slot may also be divided into a plurality of small 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 The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

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

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

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

[0097] 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 with a service subscription to a network provider that supports the macro cell. A small cell may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as compared to a macro cell. A small cell may provide unrestricted access to a UE 115 with a service subscription to a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a residence or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

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

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

[0100] 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 (e.g., 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 automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0101] 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 and key 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.

[0102] 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 be unable to receive transmissions from the network entity 105 or not configured to receive transmissions from the network entity 105 for other reasons. 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 can facilitate the scheduling of resources for D2D communication. In some other examples, D2D communication is performed between UEs 115 without involving the network entity 105.

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

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

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

[0106] The wireless communication system 100 may also operate using a super high frequency (SHF) region (also referred to as a centimeter band) that may be in the range of 3 GHz to 30 GHz 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 (e.g., base station 140, RU 170), and the EHF antennas of each device may be smaller and more closely spaced than the UHF antennas. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may suffer from even greater attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may differ according to the country or regulatory agency.

[0107] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use 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 network entities 105 and UE 115 can use carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on 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, as well as other examples.

[0108] 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 network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels that may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of rows and columns of antenna ports that the network entity 105 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.

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

[0110] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals transmitted via antenna elements of an antenna array so that some signals propagating 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 direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0111] 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 communications with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) to identify a beam direction for subsequent transmission or reception by the network entity 105.

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

[0113] In some examples, transmissions 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)), which 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 for sending signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by UE 115) or for sending signals along a single direction (e.g., for sending data to a receiving device).

[0114] 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, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the 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 along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

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

[0116] In some implementations, the wireless communication system 100 supports signaling and other mechanisms that enable the UE 115 to establish a wireless connection with a service-based network 130 (e.g., a 6G network). In particular, aspects of the present disclosure are directed to signaling between the UE 115, the network entity 105 (e.g., the DU 165), and the core network service (e.g., the CN / RAN service 185) of a service-based network architecture, which enables the UE 115 to establish and maintain connections with different core network services (e.g., the CN / RAN service 185) provided by the network. Therefore, the techniques described herein can enable the UE 115 to obtain a service context for each corresponding core network service to which the UE 115 subscribes, wherein the service context includes core network service-specific communication parameters for communicating with the corresponding core network service.

[0117] For example, a UE 115 of the wireless communication system 100 may establish a connection with a DU 165 of a network entity 105 and may receive control signaling indicating core network services (e.g., CN / RAN services 185) provided by the network, and a network address for each core network service provided. The UE 115 may then send a service request (via a relay of the DU 165) to the network address of the provided core network service and may receive a service context (via a relay of the DU 165) for communicating with the core network service. The UE 115 may then communicate with the core network service based on the service context (via the DU 165).

[0118] In some aspects, UE 115 may be able to request core network services provided by the network. For example, UE 115 may be able to query a discovery service (e.g., a core network discovery service) that is configured to provide a list of provided core network services that can be accessed by each querying UE 115. The core network services indicated as available to UE 115 may be based on the capabilities of each respective UE 115. Some core network services may include or depend on other network function services. For example, in order for UE 115 to subscribe to / communicate with a first core network service, UE 115 may also be required to subscribe to / communicate with a second core network service associated with the first core network service.

[0119] The techniques described herein may enable a UE 115 to establish and maintain a connection with (e.g., subscribe to) a core network service provided by a service-based network (e.g., within a 6G system). In particular, the techniques described herein may enable a UE 115 to obtain a service context for each respective core network service to which the UE 115 subscribes, wherein the service context includes core network service-specific parameters for communicating with the respective core network service. By enabling a UE 115 to subscribe to multiple different core network services, various aspects of the present disclosure may enable a UE 115 to establish a connection with a variety of core network services that may be provided by different operators or entities. Thus, the techniques described herein may enable a UE 115 to subscribe to different core network services on a per-order basis, based on the needs or requirements of individual UEs 115, thereby improving customization and the overall user experience at the UE 115. In addition, by enabling UE 115 to subscribe to specific core network services, the techniques described herein can enable UE 115 to avoid communicating with unnecessary or unwanted core network services, thereby reducing control signaling within the network, improving resource utilization, and reducing power consumption at UE 115.

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

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

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

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

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

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

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

[0127] 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).

[0128] Compared with some other types of wireless systems, Figure 2 The service-based wireless communication system 200 (e.g., a 6G network) shown in FIG. 2 may exhibit some differences and advantages, for example, the network exhibits a relatively more vertical layered architecture that includes "layers" of multiple different devices that perform functions for the network. A more layered structure may result in processing and other functions being performed at multiple devices (e.g., a 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 UE 115 and other devices may be difficult to customize within such a system.

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

[0130] 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 RAT (e.g., reallocation of core and RAN 210 services). In other words, the fusion of RAN 210 and CN functions may reduce duplication of operations and functions used to serve one UE at different layers.

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

[0132] In some implementations, as will be described in further detail herein, the wireless communication system 200 may support signaling that enables the UE 115-a to establish and maintain communications with a core network service 215 of a service-based network 205 (e.g., a 6G network). In particular, aspects of the present disclosure are directed to signaling that enables the UE 115-a to subscribe to core network services 215 on a per-order basis based on the needs or requirements of the UE 115-a.

[0133] Figure 3An example of a network architecture 300 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting techniques for service establishment in a service-based wireless system according to one or more aspects of the present disclosure is shown. The network architecture 300 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 300 may include a service-based network 305, which may be an example of a service-based network 130 or 205, and the service-based network 305 communicates with the DU 165-a via a link 120-b. In this example, the DU 165 may also communicate with one or more CUs 310, which may communicate directly with the 5G core 190-a via a backhaul communication link 120-a, or indirectly with the 5G core 190-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 330-a via an E2 link, or a non-RT RIC 330-b associated with a SMO 335 (e.g., an SMO framework), or both. The CU 310 may communicate with one or more DUs 165-a via corresponding mid-range communication links 315 (e.g., F1 interfaces). The DU 165-a may communicate with one or more RUs 170-a via corresponding front-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.

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

[0135] 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 communicate signals with other control functions hosted by CU 310. CU 310 may be configured to process user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some 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.

[0136] 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 interfaced with a service-based network 305, DU 165-a may host one or more APIs for one or more services of the service-based network 305 and one or more corresponding services at one or more UEs 115-b. In some examples, when interfaced with a CU 310, DU 165-a may at least partially host one or more of the following depending at least in part on a functional partitioning (e.g., a functional partitioning defined by the Third Generation Partnership Project (3GPP)): an RLC layer, a MAC layer, and one or more aspects of a PHY layer (e.g., a high PHY layer, such as modules 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 interfaces configured to communicate signals with other layers hosted by the DU 165 - a , or using control functions hosted by the CU 310 .

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

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

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

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

[0141] In some implementations, as will be described in further detail herein, the network architecture 300 may support signaling that enables the UE 115 to establish and maintain communications with core network services of a service-based network (e.g., a 6G network). In particular, aspects of the present disclosure relate to signaling between the UE 115, the DU 165, and the core network services that enables the UE 115 to subscribe to core network services on a per-order basis based on the needs or requirements of individual UEs 115.

[0142] Figure 4An example of a wireless communication system 400 that supports techniques for service establishment 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 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, or any combination thereof. In particular, the wireless communication system 400 may support signaling that enables the UE 115 to establish and maintain communication with a service-based network (e.g., such as regarding Figure 1 Communications of core network services of the 6G network described.

[0143] The wireless communication system 400 may include a UE 115-b, a network entity 105-b, a first core network service 405-a (e.g., a core network security service), a second core network service 405-b (e.g., a core network discovery service), 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 Figure 3 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.

[0144] 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 interface 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 or hosted by a cloud platform, wherein the corresponding core network service 405 is hosted at a corresponding network address in the cloud platform.

[0145] 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., interface with) 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 core network services 405-a. 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 .

[0146] 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 devices directly, via other network entities 105, via a proxy, or any combination thereof.

[0147] As previously mentioned, some traditional wireless systems (e.g., 4G / 5G communication systems) may exhibit a relatively vertical layered architecture, including many "layers" of different devices that perform functions specific to the system. For example, a traditional wireless system may include user equipment (UE), base stations / network entities, and many backend devices such as mobility management entities (MMEs), session management functions (SMFs), and access and mobility management functions (AMFs). When moving from 4G systems to 5G systems, the functional division of core / RAN remains largely unchanged. In particular, 3G and 4G systems introduced a core / RAN hierarchy based on device models and deployments to meet the performance and security requirements of accessibility to field devices, and the 5G system did not reconsider the division in its design for cloud deployments.

[0148] The layered structure of 5G communication systems often causes processing and other functions to be performed at multiple devices (e.g., repeated processing across MME, AMF and / or SMF), resulting in wasted resources and power consumption. In addition, the backend architecture of some traditional wireless systems may be owned and maintained by a few operators, making it difficult for other parties / entities to integrate within these systems and complicating the ability of these systems to provide customized services and functions to wireless devices.

[0149] In contrast, some wireless systems (e.g., 6G systems) may exhibit a flatter, service-based architecture in which the RAN (e.g., network entity 105) interfaces with a service-based network to connect UEs to core network services maintained at various network addresses within the service-based network. In the context of a service-based system, operations and functions performed by a few centralized backend components (e.g., AMF, MME, SMF) of some traditional systems may be distributed across multiple core network services (e.g., in a cloud architecture) that may be hosted at different network addresses. In other words, a 6G network may present a more cloud-native architecture in which network functions and protocols are divided into self-contained services (e.g., core network services 405) rather than all-encompassing network functions and network protocols.

[0150] Cloud-native platforms or architectures for 6G systems (e.g. Figure 2 The service-based network 205 shown in FIG. 4 can host the merging of core and RAN services while enabling each network function and protocol to be operated and managed by a self-contained core network service 405. The merging of core and RAN services can simplify protocols and reduce duplication of processing and operations across the core and RATs. New merged services can be hosted based on the deployment topology and capabilities of each corresponding core network service 405.

[0151] In other words, a service-based wireless system (e.g., a 6G system) can present a single cloud platform that is configured to host application, core, and RAN services (e.g., via multiple core network services 405). The wireless communication system 400 can extend the benefits associated with the service-based architecture of the service-based network 205 to the RAN, including the benefits of increased scalability, elasticity, flexibility, agility, reuse, visibility, automation, and failover. Additionally, the service-based architecture can enable each core network service across the RAN 210 and the core to scale independently by independently increasing or decreasing the resources allocated across the various core network services 215.

[0152] In addition, a service-based wireless system (e.g., wireless communication system 400) can reconsider the functional division of the core and RAN (e.g., core and TRAN based on converged services). In particular, the 6G network can reformat the assumptions made in the 3G / 4G functional hierarchy based on the requirements of the device-centric architecture in order to take full advantage of cloud deployment / platforms. By doing so, the cloud platform of the 6G system can achieve redistribution of core and RAN services, simplify protocols, and reduce functional duplication while maintaining QoS requirements for each corresponding core network service 405. For example, operations and protocols previously performed by AMF, CU, CP, DU, or any combination thereof in the context of a 4G / 5G system can now be performed by multiple core network services 405 of a service-based network, which can be hosted in a cloud platform. In some cases, a cloud architecture can enable applications to share a common platform and can enable all real-time link management to be moved to the edge of the RAN. For example, a cloud platform can implement adaptation at the DU to allow more efficient activation, deactivation, and selection of features based on UX requirements, and can decouple the configuration (e.g., RRC) and activation (e.g., MAC) of performance-sensitive features.

[0153] A service-based wireless system can implement modular protocols across services (e.g., across core network services 405). More specifically, a service-based wireless system can decompose monolithic protocols to implement cloud-native protocol designs for the core, RAN, and devices (e.g., UE). 3GPP defines protocols based on network-centric designs and limits innovation through releases. Monolithic protocols at the core (e.g., NAS) and RAN (e.g., RRC) may result in a single control plane protocol defined for all control plane (C-plane) functions, where feature updates affect multiple functions and the software of the device may be too difficult to upgrade. In contrast, a cloud-native device model can enable modular protocols to extend to the long tail of the vertical, where protocols can be dedicated to each core network service 405 and can be upgraded or modified individually. Such a cloud-native device model can enable the ability to adapt across different verticals and deployment types (e.g., cloud-native CI / CD protocol upgrades) and promote supplier diversity for each core network service 405.

[0154] The RAN-core C-plane protocol partitioning provided by the service-based wireless network can achieve vertical convergence of operations and protocols across the previous DU, DU, AMF and SMF structures to multiple core network services 405. For example, NAS protocols and functions previously performed by AMF (e.g., connection state (idle / connected) functions, CN paging, UE network capabilities, mobility, NAS security) can now be managed / provided by corresponding core network services 405 (e.g., paging services, capability services, mobility services, security services, etc.). Similarly, RRC protocols and functions previously performed by CU (e.g., AS security, mobility, UE radio capabilities, RAN paging, connection management, SRB / DRB management, etc.) can now be managed / provided by corresponding core network services 405 (e.g., connection services, SRB / DRB services, etc.), new eDU functions, or both. In addition, the RAN-core C-plane protocol partitioning can achieve horizontal partitioning (e.g., modularization) of different network operations and functions across multiple core network services 405.

[0155] Thus, a UE 115 in a service-based system can establish and maintain connections (e.g., "subscribe") to different core network services 405 on a per-order basis, each of which offers or provides a respective network function or service. For example, a service-based system may include mobility services, security services, privacy services, location services, etc. In this regard, each UE 115 in a service-based system may be able to select which core network services 405 the UE 115 will subscribe to based on the individual characteristics or needs of the respective UE 115.

[0156] The process for establishing a connection with the core network service 405 (e.g., subscribing to the core network service) may include several main stages: (1) RAN connection establishment, (2) system information acquisition, (3) service establishment, (4) service execution, and (5) service release. During the RAN connection establishment stage, the UE 115-b may establish a wireless connection with the RAN (e.g., establish a wireless connection with the network entity 105-b). During the system information acquisition stage, the RAN (e.g., the network entity 105-b) may acquire information or configuration associated with providing system information to the UE 115-b, and may subsequently provide the system information to the UE 115-b. In this regard, the UE 115-b may be configured to receive system information, system information services (e.g., core network system information services), or both from the network entity 105-b. The system information may include information used for communication with the network entity 105-b, communication with other core network services provided by the service-based network, and the like.

[0157] The service establishment phase may include several steps of sub-phases, including: (a) security establishment, (b) service discovery, and (c) service configuration. In some aspects, a security service (e.g., a first core network service 405-a) may be established as the first core network service 405 of the service group. That is, as part of the service establishment phase, UE 115-b may subscribe to a security service (e.g., a first core network service 405-a). Subsequently, during the service discovery sub-phase, UE 115-b may identify core network services 405 provided / available within the system. In some cases, the network entity 105-b may indicate which core network services 405 are provided or available. Additionally or alternatively, UE 115-b may query a discovery service (e.g., a second core network service 405-b) in order to perform service discovery. Finally, during service configuration, UE 115-b may send a service request to the provided core network service 405 (e.g., a third core network service 405c), and may receive a service context for communicating with the core network service 405. In some aspects, the service context may include service-specific parameters for communicating with the third core network service 405-c. The parameters for communicating with the second core network service 405-c that may be indicated via the service context may include: the type or format of signaling and information to be exchanged between the UE 115-b and the third core network service 405-c, resources for communication between the UE 115-b and the third core network service 405-c, HARQ processes for communication between the UE 115-b and the third core network service 405-c, associated or related core network services 405 required to execute the third core network service 405-c, and the like.

[0158] Subsequently, during a service activation phase, UE 115-b and third core network service 405-c may activate the service at UE 115-b (e.g., third core network service 405-c transitions to an active state at UE 115-b), and UE 115-b and third core network service 405-c may communicate with each other (via network entity 105-b) based on the service context. Finally, during a service deactivation phase, third core network service 405-c may transition to an inactive state at UE 115-c (e.g., there is no active communication between UE 115-b and third core network service 405-c).

[0159] Reference Figure 5 The various stages for subscribing to core network services 405 are further shown and described.

[0160] Figure 5An example of a process flow 500 for supporting techniques for service establishment 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 500 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, or any combination thereof. In particular, the process flow 500 illustrates signaling that enables a UE 115-c to subscribe to a core network service provided by a service-based network, as described with reference to FIG. Figure 1-4 and other aspects described.

[0161] Process flow 500 may include UE 115-c, network entity 105-c, core network service 505, security service 510 (e.g., additional core network service or core network security service), and discovery service 515 (e.g., additional core network service, or core network discovery service), which may be UE 115, network entity 105, core network device, and reference Figure 1-4 Other wireless devices described. In some aspects, the security service can store information associated with security operations and protocols and can facilitate security functions at the UE 115-c within the network. Similarly, the discovery service 515 can store information associated with the core network services 505 provided by the service-based network and can facilitate the subscription of the UE 115-c to the provided core network services 505.

[0162] In some aspects, core network services 505, security services 510, discovery services 515, or any combination thereof may be included in a service-based network (e.g., Figure 2 In this case, the service-based network including core network services 505, security services 510, and discovery services 515 can be configured to interface with (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-c. In this regard, Figure 5 The signaling shown in may include example signaling within a network with a service-based architecture, such as a 6G system.

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

[0164] At 520, the UE 115-c may establish services (e.g., establish a location connection) and perform communications with the network entity 105-c. In some aspects, the UE 115-c may perform communications with the network entity 105-c based on performance of a random access procedure with the network entity 105-c. At 520, the UE 115-c may not have established communications with any core network services 505 and, therefore, may not have any service context information for communicating with the respective core network services 505.

[0165] At 525, the UE 115-c may perform a security service establishment with a security service 510 (e.g., a core network security service). For example, the UE 115-c and the security service 510 may exchange information associated with authentication and key agreement between the respective devices. In some aspects, the UE 115-c may establish a connection with the security service 510 (e.g., subscribe to the security service 510) as the first core network service of a service group (e.g., a related or interdependent core network service group 505). Additionally, in some cases, the security service establishment may be performed on an existing subscription and the security setup process may be reused.

[0166] At 530, the UE 115-c and the security service 510 may perform security setup. The UE 115-c and the security service 510 may perform security setup at 530 based on performing the security establishment at 525. After performing the security setup at 530, the security service 510 may be active (e.g., in an active state) at the UE 115-c. In some aspects, the network entity 105-c may be configured to relay communications between the UE 115-c and the security service 510 in order to perform the security establishment and the security setup at 525 and 530.

[0167] At 535, the UE 115-c may send a query to the network entity 105-c, the discovery service 515, or both, for a set of core network services offered / provided by a service-based network configured to interface with a RAN including the network entity 105-c. In other words, the UE 115-c may perform optional service discovery to determine which core network services are available to the UE 115-c.

[0168] In some aspects, the UE 115-c may send the request based on communicating with the network entity 105-c at 520, establishing communication with the security service 510 at 525 and 530, or any combination thereof. For example, the network entity 105-c may relay the request from the UE 115-c to the discovery service 515. As another example, the UE 115-c may receive a network address for the discovery service 515 from the network entity 105-c and may send a query to the network address for the discovery service 515, where the network entity 105-c is configured to relay the query to the indicated network address.

[0169] In some aspects, the query may include information that enables the discovery service 515 to determine which core network services may be provided to (or accessible by) the UE 115-c. For example, in some cases, the query may include capability information associated with the UE 115-c, where the capability information may enable the discovery service 515 to determine which core network services the UE 115-c may access.

[0170] In some aspects, the UE 115-c may, based on determining that one or more core network services provided by the cellular network need to be established to have connectivity and access to the corresponding core network services, send a query for provided core network services at 535. Core network services that may be offered or provided by the wireless communication system may include, but are not limited to, mobility services, connection state management services, security services 510, paging services, radio access services, QoS configuration and data services, UE capability management services, location services, messaging services, and the like.

[0171] In additional or alternative implementations, information about available core network services 505 provided by the service-based network may be preconfigured at the UE 115-c. For example, in some implementations, a subscriber identity module (SIM) associated with the UE 115-c may be preconfigured with information associated with core network services 505 that are provided by the service-based network and / or accessible to the UE 115-c. In this case, the UE 115-c may be configured to identify the available core network services 505 without sending a query at 535 and / or receiving signaling indicating the available services at 540.

[0172] At 540, the UE 115-c may receive control signaling from the discovery service 515 (and via the network entity 105-c) indicating a set of core network services provided by the service-based network. For example, the control signaling may indicate the core network service 505 as a service provided by the service-based network and / or accessible by the UE 115-c. The UE 115-c may receive the control signaling at 540 in response to the request at 535. In some aspects, the control signaling may indicate a set of network addresses associated with the set of provided core network services, wherein each core network service corresponds to a respective network address. In addition, each core network service may be associated with a respective API that enables communication between the respective core network service and the UE 115-c / network entity 105-c.

[0173] In some cases, the available core network services indicated via the control signaling to 540 may be based on the capabilities or other parameters (e.g., geographic location) of the UE 115-c. For example, the indicated core network services may be based on the capability information of the UE 115-c indicated via the service discovery query at 535. In this example, the control signaling may indicate only those core network services with which the UE 115-c is able to communicate or subscribe, and may not indicate other core network services that are provided by the service-based network but that the UE 115-c is unable to access due to capabilities or other limitations (e.g., geographic location).

[0174] At 545, the UE 115-c may send a service request to the core network service 505, wherein the service request includes a first network address associated with the core network service (e.g., a request to establish a service context). In other words, the UE 115-c may send (and the network entity 105-c may relay) a service request to a network address corresponding to the core network service 505. In this regard, the UE 115-c may send the service request based on control signaling received at 540 indicating the core network service provided. In some aspects, the UE 115-c may send the service request as part of a service establishment procedure (e.g., a subscription procedure) between the UE 115-c and the core network service 505. In some aspects, the service request may include a request for AS security (e.g., at the MAC layer).

[0175] The service request may include a request for a radio access configuration associated with the service, and may trigger core network service-specific configuration at the RAN (e.g., network entity 105-c) and UE 115-c, as well as RAN reconfiguration between the RAN and UE 115-c. In addition, the service request may include or indicate various parameters or characteristics associated with the UE 115-c and / or the network entity 105-c, including QoS configuration, AS security request, etc. In this regard, the network entity 105-c may be configured to expose one or more APIs of the network entity 105-c to the core network service 505 in order to facilitate communication between the UE 115-c and the core network service 505.

[0176] The UE 115-c may send a service request to each core network service 505 available / provided to the UE 115-c based on a number of parameters or characteristics. The determination as to which core network services 505 the UE 115-c may subscribe to may be based on application / service layer requests, user preferences (e.g., applications executed / executable at the UE 115-c), configuration of the home operator, discovery of available services in the serving network, mobility of the UE 115-c, discovery of interdependencies between services (e.g., data services may require establishment of mobility services and security services), or any combination thereof.

[0177] In some aspects, the core network service 505 can determine whether the UE 115-c is authorized for the core network service 506 and / or whether it is able to perform communications for the corresponding core network service. In some cases, such a determination can be based on capability information indicated via the request, the geographic location of the UE 115-c, or based on the core network service 505 obtaining or requesting capability information / subscription information associated with the UE 115-c from another core network service, such as a capability service (e.g., a core network capability service) or a subscription service (e.g., a core network subscription service). Additionally or alternatively, the core network service 505 can determine whether the UE 115-c is authorized for the core network service 505 and / or whether it is able to perform communications for the corresponding core network service 505 based on whether the UE 115-c has previously established a security context with the security service 510 (e.g., as shown in 525 and 530).

[0178] In some implementations, the service request may trigger the core network service 505 to communicate (e.g., subscribe) with other core network services that may be associated (e.g., interdependent) with the core network service 505. For example, the service request at 545 may cause the core network service 505 to subscribe to other services, such as the security service 510, the mobility service, the capability service for managing UE context, or any combination thereof. The communication between the core network services may be further illustrated and described at 550 and 555 in the process flow 500.

[0179] At 550, the core network service 505 may send a security setup request to the security service 510. In some aspects, the service request may include a request for AS security (e.g., at the MAC layer). In particular, the core network service 505 may send the request at 550 based on receiving the service request from the UE 115-c at 545. In this regard, the core network service 505 may establish communication with the security service 510 (e.g., subscribe to the security service 510) so that the core network service 505 can provide corresponding services / network functions to the UE 115-c.

[0180] In other words, the core network service 505 and the security service 510 may be included in a service group of related or interdependent core network services, where the security service 510 is required for execution of the core network service 505. Additional security may be established with one or more other core network services in the service group as needed, and the additional security may be triggered by the service establishment (e.g., triggered by the service request at 545). In this regard, the core network service 505 may send a request to the security service 510 (and / or subscribe to other interdependent core network services) at 550 based on determining that the core network service 505 requires subscription information or other information associated with the UE 115-c from one or more other core network services. For example, where the core network service 505 includes a data service, the data service may obtain security context information from the security service 510 and may obtain mobility information of the UE 115-c from the mobility service.

[0181] At 555, the core network service 505 may receive a security context from the security service 510. The core network service 505 may receive the security context at 555 in response to the security setup request at 550. The security context may include information (e.g., communication parameters) for communication between the core network service 505 and the security service 510, for communication between the UE 115-c and the core network service 505 / or the security service 510, or both. Further, in some implementations, the UE 115-c may perform a security setup with the security service 510 based on the security context at 555. In this regard, in some cases, the UE 115-c may perform the security establishment and security setup at 525 and 530 based on the security service 510 providing the security context at 555 (e.g., after the security service 510 provides the security context at 555).

[0182] At 560, the network entity 105-c may receive control signaling indicating a service context (e.g., service configuration information) for communicating with the core network service 505. The network entity 105-c may send a response message to the core network service 505 and may send (e.g., relay) the control signaling / service context to the UE 115-c. The core network service 505 may send the control signaling indicating the service context based on receiving a service request at 545, sending a service setup request at 550, receiving a security context at 555, or any combination thereof. In some aspects, the control signaling indicating the service context may additionally or alternatively include a request for the network entity 105-c to establish a context with the core network service 505 (e.g., a service configuration request), and, if desired, may also indicate radio access requirements / parameters for the corresponding core network service 505.

[0183] In some aspects, the security context (e.g., the service configuration request) may include information associated with communications between the UE 115-c and the core network service 505, communications between the UE 115-c and the network entity 105-c, communications between the network entity 105-c and the core network service 505, or any combination thereof. In this regard, the service context may include service-specific parameters for communicating with the core network service 505, such as the type or format of signaling and information to be exchanged with the core network service 505, resources used for communications between respective devices (e.g., resources used for communications between the UE 115-c, the network entity 105-c, and the core network service 505), HARQ processes used for communications, associated or related (e.g., interdependent) core network services required for execution of the core network service 505, and the like. In this regard, the service context may include RAN configuration (e.g., RAN reconfiguration) for communications between the UE 115-c and the network entity 105-c as part of communications for the core network service 505, where the network entity 105-c locally configures the corresponding RAN configuration / radio resource configuration for the UE 115-c.

[0184] At 565, the UE 115-c may establish connections / communications with other related core network services. In particular, the UE 115-c may establish communications with other core network services based on the service context received at 560. In this way, the network entity 105-c may be configured to accumulate radio access configuration requests from multiple core network services 505 requested by the UE 115-c to determine one or more radio configurations for the UE 115-c based on the accumulation of those requests from different core network services 505.

[0185] In other words, where the service context indicates that the UE 115-c is also to subscribe to other core network services 505 associated with the core network service 505 (e.g., indicating interdependent core network services), the UE 115-c may establish services with the other indicated core network services, as shown at 545 through 560 in the process flow 500. In this case, security establishment may be configurable per core network service, including that the discovered service may require security, and wherein the security context may be shared between a group of interdependent core network services.

[0186] In some aspects, for each respective core network service 505 to which UE 115-c subscribes, the network entity 105-c may be configured to reply to a service context (e.g., a service configuration request) received from each core network service 505 with a service configuration response, wherein the service configuration response indicates (one or more) respective radio configurations associated with each respective core network service 505.

[0187] In some aspects, the UE 115-c may receive a service protocol response from each core network service 505 that the UE 115-c has requested service for. The service protocol response may indicate whether each respective service accepts or rejects the service request received from the UE 115-c. In addition, for the core network service 505 that accepts the service request from the UE 115-c, the service protocol response may indicate a service context (e.g., service configuration information) for communicating with the core network service 505, as shown at 560. In addition, the service configuration information included in the service protocol response may be based on a corresponding service request from the UE 115-c (e.g., the service request at 545), a resource configuration response received from the network entity 105-c, or both. In the event that the core network service 505 requires more information from the UE 115-c before being able to establish a service, the service protocol message from the core network service 505 may include a request for additional information associated with the service configuration / service context, wherein the additional requested information may be returned via one or more additional service protocol messages from the UE 115-c.

[0188] At 570, the UE 115-c may exchange service messages with the core network services 505 based on the service context. In particular, the network entity 105-c may relay service messages (e.g., service protocol data units) between the UE 115-c and the core network services 505. The service messages exchanged between the UE 115-c and the core network services 505 may include identifiers associated with the UE 115-c and the core network services 505, such as a UE ID, a network address of the core network services 505, etc. The UE 115-c may communicate with the core network services 505 at 570 based on receiving a list of available services at 540, sending a service request at 545, receiving a service context at 560, establishing communication with the relevant core network services 505, or any combination thereof.

[0189] Figure 6A block diagram 600 of a device 605 supporting techniques for establishing services in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0190] The receiver 610 may provide a unit for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technology for service establishment in a service-based wireless system). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna, or may utilize a group of multiple antennas.

[0191] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 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 establishment in a service-based wireless system). In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna, or may utilize a group of multiple antennas.

[0192] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of service establishment in a service-based wireless system as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

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

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

[0195] In some examples, the communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using the receiver 610, the transmitter 615, or both, or otherwise cooperate with the receiver 610, the transmitter 615, or both. For example, the communication manager 620 can receive information from the receiver 610, send information to the transmitter 615, or be integrated in conjunction with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations described herein.

[0196] According to an example as disclosed herein, the communication manager 620 may support wireless communication at the UE. For example, the communication manager 620 may be configured to or otherwise support a unit for receiving a first control signaling via a wireless connection between the UE and the distributed unit, the first control signaling indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services. The communication manager 620 may be configured to or otherwise support a unit for sending a service request indicating a first core network service in a set of multiple core network services based on the first control signaling, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address. The communication manager 620 may be configured to or otherwise support a unit for receiving a second control signaling indicating a first service context for communicating with the first core network service based on the service request. The communication manager 620 may be configured to or otherwise support a unit for sending a first service message including first service data and a first network address for the first core network service according to the first service context.

[0197] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor that controls or is otherwise coupled to the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques that enable the UE 115 to establish and maintain a connection with a core network service provided by a service-based network (e.g., within a 6G system) (e.g., subscribe to the core network service). In particular, the techniques described herein can enable the UE 115 to obtain a service context for each respective core network service to which the UE 115 subscribes, wherein the service context includes core network service-specific parameters for communicating with the respective core network service. By enabling the UE 115 to subscribe to multiple different core network services, various aspects of the present disclosure can enable the UE 115 to establish a connection with a variety of core network services that may be provided by different operators or entities. Therefore, the techniques described herein can enable the UE 115 to subscribe to different core network services on a per-order basis, based on the needs or requirements of each UE 115, thereby improving the customization and overall user experience at the UE 115. In addition, by enabling UE 115 to subscribe to specific core network services, the techniques described herein may enable UE 115 to avoid communicating with unnecessary or unwanted core network services, thereby reducing control signaling within the network, improving resource utilization, and reducing power consumption at UE 115.

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

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

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

[0201] The device 705 or its various components may be examples of units for performing various aspects of the technology of service establishment in a service-based wireless system as described herein. For example, the communication manager 720 may include a control signaling reception manager 725, a service request transmission manager 730, a service context manager 735, a service message communication manager 740, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use the receiver 710, the transmitter 715, or both, or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 720 may receive information from the receiver 710, send information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations described herein.

[0202] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. The control signaling reception manager 725 may be configured to or otherwise support a unit for receiving a first control signaling via a wireless connection between the UE and the distributed unit, the first control signaling indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services. The service request sending manager 730 may be configured to or otherwise support a unit for sending a service request indicating a first core network service in the set of multiple core network services based on the first control signaling, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address. The service context manager 735 may be configured to or otherwise support a unit for receiving a second control signaling indicating a first service context for communicating with the first core network service based on the service request. The service message communication manager 740 may be configured to or otherwise support means for sending a first service message including first service data and a first network address for a first core network service according to a first service context.

[0203] Figure 8 A block diagram 800 of a communication manager 820 supporting techniques for service establishment in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of units for performing various aspects of the techniques for service establishment in a service-based wireless system as described herein. For example, the communication manager 820 may include a control signaling reception manager 825, a service request transmission manager 830, a service context manager 835, a service message communication manager 840, a query transmission manager 845, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0204] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. The control signaling reception manager 825 may be configured to or otherwise support a unit for receiving a first control signaling via a wireless connection between the UE and the distributed unit, the first control signaling indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services. The service request sending manager 830 may be configured to or otherwise support a unit for sending a service request indicating a first core network service in the set of multiple core network services based on the first control signaling, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address. The service context manager 835 may be configured to or otherwise support a unit for receiving a second control signaling indicating a first service context for communicating with the first core network service based on the service request. The service message communication manager 840 may be configured to or otherwise support means for sending a first service message including first service data and a first network address for a first core network service according to a first service context.

[0205] In some examples, the query sending manager 845 can be configured as or otherwise support means for sending a query for a set of multiple core network services based on establishing a wireless connection between the UE and the distributed unit, wherein the first control signaling is received in response to the query.

[0206] In some examples, the control signaling reception manager 825 may be configured or otherwise support means for receiving, from a distributed unit, a network address associated with a core network discovery service provided by the service-based network, wherein a query is sent to the core network discovery service based on the network address.

[0207] In some examples, the query transmission manager 845 may be configured or otherwise support means for transmitting capability information associated with the UE via a query, wherein the set of multiple core network services is based on the capability information.

[0208] In some examples, the service context manager 835 may be configured as or otherwise support a unit for receiving an indication of a second core network service in a set of multiple core network services via a first service context for communicating with the first core network service. In some examples, the service request sending manager 830 may be configured as or otherwise support a unit for sending a second service request indicating a second core network service, the second service request including a second network address associated with the second core network service. In some examples, the service context manager 835 may be configured as or otherwise support a unit for receiving a third control signaling indicating a second service context for communicating with the second core network service based on the second service request, wherein transmitting the first service message is based on receiving the second service context.

[0209] In some examples, the service message communication manager 840 can be configured as or otherwise support a unit for transmitting a second service message including second service data and a second network address for a second core network service based on a second service context, wherein transmitting the first service message is based on transmitting the second service message.

[0210] In some examples, the second core network service includes a security service associated with the first core network service. In some examples, the second service context includes authentication information, a key agreement, or both.

[0211] In some examples, the service request, the first service message, or both are sent to a distributed unit for relaying to a first network address associated with a first core network service.

[0212] In some examples, the first service context includes a radio access network configuration for communicating with the distributed unit as part of the first core network service.

[0213] In some examples, each core network service in the set of multiple core network services is associated with a corresponding API in the set of multiple APIs.

[0214] In some examples, the set of multiple core network services includes mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0215] Fig. 9A schematic diagram of a system 900 including a technical device 905 supporting service establishment 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 a device 605, a device 705, or a UE 115 as described herein, or include components of a device 605, a device 705, or a UE 115 as described herein. The device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, and / or electrically) via one or more buses (e.g., a bus 945).

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

[0217] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of simultaneously sending or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem to modulate a packet, provide the modulated packet to one or more antennas 925 for transmission, and demodulate the packet received from the one or more antennas 925. The transceiver 915 or the transceiver 915 and the one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

[0218] The memory 930 may include a random access memory (RAM) or a read-only memory (ROM). The memory 930 may store a computer-readable, computer-executable code 935 including instructions, which, when executed by the processor 940, enables the device 905 to perform various functions described herein. The code 935 may be stored in a non-temporary computer-readable medium such as a system memory or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940, but may enable the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among others, the memory 930 may include a basic I / O system (BIOS), which may control basic hardware or software operations (such as interactions with peripheral components or devices).

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

[0220] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured to or otherwise support a unit for receiving a first control signaling via a wireless connection between the UE and the distributed unit, the first control signaling indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services. The communication manager 920 may be configured to or otherwise support a unit for sending a service request indicating a first core network service in a set of multiple core network services based on the first control signaling, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address. The communication manager 920 may be configured to or otherwise support a unit for receiving a second control signaling indicating a first service context for communicating with the first core network service based on the service request. The communication manager 920 may be configured to or otherwise support a unit for sending a first service message including first service data and a first network address for the first core network service according to the first service context.

[0221] By including or configuring the communication manager 920 according to the examples described herein, the device 905 can support technologies that enable the UE 115 to establish and maintain a connection with a core network service provided by a service-based network (e.g., within a 6G system) (e.g., subscribe to the core network service). In particular, the techniques described herein can enable the UE 115 to obtain a service context for each corresponding core network service to which the UE 115 subscribes, wherein the service context includes core network service-specific parameters for communicating with the corresponding core network service. By enabling the UE 115 to subscribe to multiple different core network services, various aspects of the present disclosure can enable the UE 115 to establish a connection with a variety of core network services that can be provided by different operators or entities. Therefore, the techniques described herein can enable the UE 115 to subscribe to different core network services on a single basis according to the needs or requirements of each UE 115, thereby improving the customization and overall user experience at the UE 115. In addition, by enabling UE 115 to subscribe to specific core network services, the techniques described herein may enable UE 115 to avoid communicating with unnecessary or unwanted core network services, thereby reducing control signaling within the network, improving resource utilization, and reducing power consumption at UE 115.

[0222] In some examples, the communication manager 920 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 920 can be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions executable by the processor 940 to cause the device 905 to perform various aspects of the technology for establishing services in a service-based wireless system using services as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0223] Fig.10 A block diagram 1000 of a device 1005 supporting techniques for service establishment in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a network entity 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

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

[0225] The transmitter 1015 may provide a means for outputting (e.g., sending, providing, transmitting, sending) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1015 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1015 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 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0226] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of service establishment in a service-based wireless system as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

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

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

[0229] In some examples, the communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using the receiver 1010, the transmitter 1015, or both, or otherwise cooperate with the receiver 610, the transmitter 615, or both. For example, the communication manager 1020 can receive information from the receiver 1010, send information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations described herein.

[0230] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at the distributed unit. For example, the communication manager 1020 may be configured to or otherwise support a unit for sending a first control signaling to a UE, the first control signaling indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services. The communication manager 1020 may be configured to or otherwise support a unit for receiving a service request indicating a first core network service in a set of multiple core network services from the UE based on the first control signaling, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address. The communication manager 1020 may be configured to or otherwise support a unit for sending a service request to the first network address. The communication manager 1020 may be configured to or otherwise support a unit for sending a second control signaling received from the first core network service to the UE based on the service request, the second control signaling indicating a first service context for communication between the UE and the first core network service. The communication manager 1020 may be configured to or otherwise support means for transmitting a first service message received from the UE to a first core network service according to a first service context, the first service message including first service data and a first network address for the first core network service.

[0231] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1020 may support wireless communications at a first core network service. For example, the communication manager 1020 may be configured to or otherwise support a unit for receiving a service request indicating a first core network service from a UE via a distributed unit, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit. The communication manager 1020 may be configured to or otherwise support a unit for sending a first control signaling indicating a first service context for communicating with the first core network service to the UE via a distributed unit based on the service request. The communication manager 1020 may be configured to or otherwise support a unit for receiving a first service message including first service data and a first network address for the first core network service according to the first service context.

[0232] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at a core network discovery service. For example, the communication manager 1020 may be configured as or otherwise support a unit for receiving, from a UE via a distributed unit, a query for a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit. The communication manager 1020 may be configured as or otherwise support a unit for sending to the distributed unit a first control signaling indicating a set of multiple core network services for relaying to the UE, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services.

[0233] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof or otherwise coupled thereto) can support techniques that enable the UE 115 to establish and maintain a connection with a core network service provided by a service-based network (e.g., within a 6G system) (e.g., subscribe to the core network service). In particular, the techniques described herein can enable the UE 115 to obtain a service context for each respective core network service to which the UE 115 subscribes, wherein the service context includes core network service-specific parameters for communicating with the respective core network service. By enabling the UE 115 to subscribe to multiple different core network services, various aspects of the present disclosure can enable the UE 115 to establish a connection with a variety of core network services that may be provided by different operators or entities. Therefore, the techniques described herein can enable the UE 115 to subscribe to different core network services on a per-order basis, based on the needs or requirements of the respective UE 115, thereby improving the customization and overall user experience at the UE 115. In addition, by enabling UE 115 to subscribe to specific core network services, the techniques described herein may enable UE 115 to avoid communicating with unnecessary or unwanted core network services, thereby reducing control signaling within the network, improving resource utilization, and reducing power consumption at UE 115.

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

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

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

[0237] The device 1105 or its various components may be examples of units for performing various aspects of the technology for service establishment in a service-based wireless system as described herein. For example, the communication manager 1120 may include a control signaling transmission manager 1125, a service request communication manager 1130, a service context manager 1135, a service message communication manager 1140, a query communication manager 1145, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to use the receiver 1110, the transmitter 1115, or both, or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations described herein.

[0238] According to an example as disclosed herein, the communication manager 1120 may support wireless communication at a distributed unit. The control signaling sending manager 1125 may be configured to or otherwise support a unit for sending to a UE a first control signaling indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services. The service request communication manager 1130 may be configured to or otherwise support a unit for receiving from a UE a service request indicating a first core network service in a set of multiple core network services based on the first control signaling, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address. The service request communication manager 1130 may be configured to or otherwise support a unit for sending a service request to the first network address. The service context manager 1135 may be configured to or otherwise support a unit for sending to the UE a second control signaling received from the first core network service based on the service request, the second control signaling indicating a first service context for communication between the UE and the first core network service. The service message communication manager 1140 may be configured to or otherwise support means for transmitting a first service message received from a UE to a first core network service according to a first service context, the first service message including first service data and a first network address for the first core network service.

[0239] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at a first core network service. The service request communication manager 1130 may be configured as or otherwise support a unit for receiving a service request indicating a first core network service from a UE via a distributed unit, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit. The service context manager 1135 may be configured as or otherwise support a unit for sending a first control signaling indicating a first service context for communicating with the first core network service to the UE via a distributed unit based on the service request. The service message communication manager 1140 may be configured as or otherwise support a unit for receiving a first service message including first service data and a first network address for the first core network service according to the first service context.

[0240] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at a core network discovery service. The query communication manager 1145 may be configured as or otherwise support a unit for receiving, via a distributed unit, a query for a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit from the UE. The control signaling sending manager 1125 may be configured as or otherwise support a unit for sending to the distributed unit a first control signaling indicating the set of multiple core network services for relaying to the UE, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services.

[0241] Fig.12 A block diagram 1200 of a communication manager 1220 supporting technology for service establishment in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of units for performing various aspects of the technology for service establishment in a service-based wireless system as described herein. For example, the communication manager 1220 may include a control signaling manager 1225, a service request communication manager 1230, a service context manager 1235, a service message communication manager 1240, a query communication manager 1245, 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 communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0242] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a distributed unit. The control signaling sending manager 1225 may be configured as or otherwise support a unit for sending to a UE a first control signaling indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services. The service request communication manager 1230 may be configured as or otherwise support a unit for receiving from a UE a service request indicating a first core network service in a set of multiple core network services based on the first control signaling, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address. In some examples, the service request communication manager 1230 may be configured as or otherwise support a unit for sending a service request to the first network address. The service context manager 1235 may be configured as or otherwise support a unit for sending to the UE a second control signaling received from the first core network service based on the service request, the second control signaling indicating a first service context for communication between the UE and the first core network service. The service message communication manager 1240 may be configured as or otherwise support means for communicating a first service message received from the UE to a first core network service according to a first service context, the first service message including first service data and a first network address for the first core network service.

[0243] In some examples, query communication manager 1245 can be configured as or otherwise support means for sending a query for a set of multiple core network services. In some examples, query communication manager 1245 can be configured as or otherwise support means for receiving an indication of the set of multiple core network services in response to the query, wherein sending the first control signaling is based on receiving the indication of the set of multiple core network services.

[0244] In some examples, the query communication manager 1245 can be configured as or otherwise support a unit for sending a network address associated with a core network discovery service provided by a service-based network to a UE, wherein the query is received from the UE and sent to the core network discovery service based on the network address.

[0245] In some examples, query communication manager 1245 may be configured or otherwise support means for sending capability information associated with the UE via a query, wherein a set of multiple core network services is based on the capability information.

[0246] In some examples, the service context manager 1235 may be configured as or otherwise support a unit for sending an indication of a second core network service in a set of multiple core network services via a first service context for communicating with the first core network service. In some examples, the service request communication manager 1230 may be configured as or otherwise support a unit for receiving a second service request indicating a second core network service from a UE, the second service request including a second network address associated with the second core network service. In some examples, the service request communication manager 1230 may be configured as or otherwise support a unit for sending a second service request to a second network address. In some examples, the service context manager 1235 may be configured as or otherwise support a unit for sending a third control signaling received from a second core network service to the UE based on the second service request, the third control signaling indicating a second service context for communication between the UE and the second core network service, wherein transmitting the first service message is based on sending the second service context.

[0247] In some examples, the service message communication manager 1240 can be configured as or otherwise support a unit for transmitting a second service message received from the UE to a second core network service based on a second service context, the second service information including second service data and a second network address for the second core network service, wherein transmitting the first service message is based on transmitting the second service message.

[0248] In some examples, the second core network service includes a security service associated with the first core network service. In some examples, the second service context includes authentication information, a key agreement, or both.

[0249] In some examples, the first service context includes a radio access network configuration for communicating with the UE as part of a first core network service.

[0250] In some examples, each core network service in the set of multiple core network services is associated with a corresponding API in the set of multiple APIs.

[0251] In some examples, the set of multiple core network services includes mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0252] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communications at a first core network service. In some examples, the service request communication manager 1230 may be configured as or otherwise support a unit for receiving a service request indicating a first core network service from a UE via a distributed unit, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit. In some examples, the service context manager 1235 may be configured as or otherwise support a unit for sending a first control signaling indicating a first service context for communicating with the first core network service to the UE via a distributed unit based on the service request. In some examples, the service message communication manager 1240 may be configured as or otherwise support a unit for receiving a first service message including first service data and a first network address for a first core network service according to the first service context.

[0253] In some examples, the service context manager 1235 can be configured as or otherwise support a unit for sending an indication of a second core network service from a set of multiple core network services via a first service context for communicating with a first core network service, wherein receiving the first service message is based on the indication of the second core network service.

[0254] In some examples, the second core network service includes a security service associated with the first core network service.

[0255] In some examples, the first service context includes a radio access network configuration for communications between the UE and the distributed unit as part of a first core network service.

[0256] In some examples, each core network service in the set of multiple core network services is associated with a corresponding API in the set of multiple APIs.

[0257] In some examples, the set of multiple core network services includes mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0258] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communications at a core network discovery service. The query communication manager 1245 may be configured as or otherwise support a unit for receiving, via a distributed unit, a query from a UE for a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit. In some examples, the control signaling sending manager 1225 may be configured as or otherwise support a unit for sending to the distributed unit a first control signaling for relaying to the UE, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services.

[0259] In some examples, control signaling manager 1225 may be configured or otherwise support a unit that sends a network address associated with a core network discovery service provided by a service-based network to a distributed unit, wherein the query is received based on the network address.

[0260] In some examples, query communications manager 1245 may be configured or otherwise support means for receiving capability information associated with the UE via a query, wherein the set of multiple core network services is based on the capability information.

[0261] In some examples, each core network service in the set of multiple core network services is associated with a corresponding API in the set of multiple APIs.

[0262] In some examples, the set of multiple core network services includes mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0263] Fig.13A schematic diagram of a system 1300 including a device 1305 supporting technology for service establishment 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 a device 1005, a device 1105, or a network entity 105 as described herein, or include components of a device 1005, a device 1105, or a network entity 105 as described herein. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communicating through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0264] As described herein, the transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of sending or receiving wireless transmissions (e.g., simultaneously). The transceiver 1310 may also include a modem for modulating signals, providing modulated signals for transmission (e.g., via one or more antennas 1315, via a wired transmitter), receiving modulated signals (e.g., from one or more antennas 1311, from a wired receiver), and demodulating signals. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1311 configured to support various sending or output operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or 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 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335, or memory 1325, or both) may be included in a chip or chip component installed in the device 1305. The transceiver 1310 or transceiver 1310 and one or more antennas 1315 or wired interfaces (where applicable) may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be used to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, mid-haul communication link, fronthaul communication link 168).

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

[0266] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some examples, the processor 1335 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 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) so that the device 1305 performs various functions (e.g., functions or tasks that support the technology for service establishment in a service-based wireless system). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform various functions described herein. The processor 1335 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 1330) to perform the functions of the device 1305. Processor 1335 can be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (e.g., in memory 1325). In some implementations, processor 1335 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 1305). For example, a processing system of device 1305 can refer to a system including various other components or subcomponents of device 1305 (e.g., processor 1335, transceiver 1310, communication manager 1320, or other components or combinations of components of device 1305). The processing system of device 1305 can be connected to other components of device 1305 with an interface, 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 1305 can include a processing system and an interface to output information, or obtain information, or perform these two operations. The interface may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information. In some implementations, the first interface may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1305 can send information output from the chip or modem. In some implementations, the second interface may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1305 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0267] In some examples, bus 1340 can support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 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 1305, or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 can refer to a system where one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 can be located in one of the different components or divided between the different components).

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

[0269] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at the distributed unit. For example, the communication manager 1320 may be configured to or otherwise support a unit for sending a first control signaling to a UE, the first control signaling indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services. The communication manager 1320 may be configured to or otherwise support a unit for receiving a service request indicating a first core network service in a set of multiple core network services from the UE based on the first control signaling, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address. The communication manager 1320 may be configured to or otherwise support a unit for sending a service request to the first network address. The communication manager 1320 may be configured to or otherwise support a unit for sending a second control signaling received from the first core network service to the UE based on the service request, the second control signaling indicating a first service context for communication between the UE and the first core network service. The communication manager 1320 may be configured to or otherwise support means for transmitting a first service message received from the UE to a first core network service according to a first service context, the first service message including first service data and a first network address for the first core network service.

[0270] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 may support wireless communications at a first core network service. For example, the communication manager 1320 may be configured to or otherwise support a unit for receiving a service request indicating a first core network service from a UE via a distributed unit, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit. The communication manager 1320 may be configured to or otherwise support a unit for sending a first control signaling indicating a first service context for communicating with the first core network service to the UE via the distributed unit based on the service request. The communication manager 1320 may be configured to or otherwise support a unit for receiving a first service message including first service data and a first network address for the first core network service according to the first service context.

[0271] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 may support wireless communications at a core network discovery service. For example, the communication manager 1320 may be configured as or otherwise support a unit for receiving, via a distributed unit, from a UE a query for a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit. The communication manager 1320 may be configured as or otherwise support a unit for sending to the distributed unit a first control signaling for relaying to the UE, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services.

[0272] By including or configuring the communication manager 1320 according to the examples described herein, the device 1305 can support technologies that enable the UE 115 to establish and maintain a connection with a core network service provided by a service-based network (e.g., within a 6G system) (e.g., subscribe to the core network service). In particular, the techniques described herein can enable the UE 115 to obtain a service context for each corresponding core network service to which the UE 115 subscribes, wherein the service context includes core network service-specific parameters for communicating with the corresponding core network service. By enabling the UE 115 to subscribe to multiple different core network services, various aspects of the present disclosure can enable the UE 115 to establish a connection with a variety of core network services that can be provided by different operators or entities. Therefore, the techniques described herein can enable the UE 115 to subscribe to different core network services on a single basis according to the needs or requirements of each UE 115, thereby improving the customization and overall user experience at the UE 115. In addition, by enabling UE 115 to subscribe to specific core network services, the techniques described herein may enable UE 115 to avoid communicating with unnecessary or unwanted core network services, thereby reducing control signaling within the network, improving resource utilization, and reducing power consumption at UE 115.

[0273] In some examples, the communication manager 1320 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof, or otherwise cooperate with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 1320 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1335, the memory 1325, the code 1330, the transceiver 1310, or any combination thereof. For example, the code 1330 may include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of the techniques for establishing services in a service-based wireless system using services as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0274] Fig.14 A flow chart illustrating a method 1400 for supporting technology for service establishment in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described with reference to Figures 1 to 9 The 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.

[0275] At 1405, the method may include identifying first control information indicating a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with a distributed unit, the first control information indicating a set of multiple network addresses associated with the set of multiple core network services. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described with reference to Figure 8 The control signaling reception manager 825 described above is executed.

[0276] At 1410, the method may include sending a service request indicating a first core network service in a set of multiple core network services based on the first control information, the service request including a first network address associated with the first core network service, the set of multiple network addresses including the first network address. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by the service request sending manager 830 as described in reference 8.

[0277] At 1415, the method may include receiving control signaling based on the service request, the control signaling indicating a first service context for communicating with the first core network service. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described with reference to Figure 8 The service context manager 835 described above is executed.

[0278] At 1420, the method may include sending a first service message according to the first service context, the first service message including first service data and a first network address for a first core network service. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described with reference to Figure 8 The described service message communication manager 840 is executed.

[0279] Fig.15 A flow chart illustrating a method 1500 for supporting technology for service establishment in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 11 The network entity described in 10 to 13 performs. In some examples, the network entity can 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 can use dedicated hardware to perform various aspects of the described functions.

[0280] At 1505, the method may include receiving a service request from a UE, the service request indicating a first core network service from a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with a distributed unit, wherein the multiple core network services are associated with multiple core network services, the service request including a first network address associated with the first core network service, and the set of multiple network addresses including the first network address. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a service request communication manager 1230 as described in reference 12.

[0281] At 1510, the method may include sending a service request to a first network address. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a service request communication manager 1230 as described in reference 12.

[0282] At 1515, the method may include sending, based on the service request, second control signaling received from the first core network service to the UE, the second control signaling indicating a first service context for communication between the UE and the first core network service. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Fig.12 The service context manager 1235 described is executed.

[0283] At 1520, the method may include transmitting a first service message received from the UE to the first core network service according to the first service context, the first service message including first service data and a first network address for the first core network service. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described with reference to Fig.12 The described service message communication manager 1240 is executed.

[0284] Fig.16 A flow chart illustrating a method 1600 for supporting technology for service establishment 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 network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 10 to 13. 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.

[0285] At 1605, the method may include receiving, via the distributed unit, from the UE a service request indicating a first core network service, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit. 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 by the service request communication manager 1230 as described in reference 12.

[0286] At 1610, the method may include sending, via a distributed unit, first control signaling to the UE, the first control signaling indicating a first service context for communicating with a first core network service based on a service request. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Fig.12The service context manager 1235 described is executed.

[0287] At 1615, the method may include receiving a first service message according to the first service context, the first service message including first service data and a first network address for a first core network service. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described with reference to Fig.12 The described service message communication manager 1240 is executed.

[0288] Fig.17 A flow chart illustrating a method 1700 for supporting technology for service establishment 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 a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 10 to 13. 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.

[0289] At 1705, the method may include receiving, via the distributed unit, from the UE a query for a set of multiple core network services provided by a service-based network configured to interface with a RAN associated with the distributed unit. 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.12 The query communication manager 1245 described is executed.

[0290] At 1710, the method may include sending a first control signaling to a distributed unit for relaying to a UE, the first control signaling indicating a set of multiple core network services, the first control signaling indicating a set of multiple network addresses associated with the set of multiple core network services. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Fig.12 The control signaling described is sent to the manager 1225 for execution.

[0291] A summary of some aspects of the disclosure is provided below.

[0292] Aspect 1: A method for wireless communication at a UE, comprising: identifying first control information, the first control information indicating a plurality of core network services provided by a service-based network configured to be interfaced with a RAN associated with a DU, the first control information indicating a plurality of network addresses associated with the plurality of core network services; sending a service request indicating a first core network service among the plurality of core network services based at least in part on the first control information, the service request including a first network address associated with the first core network service, the plurality of network addresses including the first network address; receiving control signaling indicating a first service context for communicating with the first core network service based at least in part on the service request; and sending a first service message including first service data for the first core network service and the first network address based on the first service context.

[0293] Aspect 2: The method according to aspect 1 also includes: sending a query for the multiple core network services based at least in part on establishing a wireless connection between the UE and the DU; and receiving the first control information in response to the query.

[0294] Aspect 3: The method according to aspect 2 also includes: receiving a network address associated with a core network discovery service provided by the service-based network from the DU, wherein the query is sent to the core network discovery service based at least in part on the network address.

[0295] Aspect 4: The method according to any one of aspects 2 to 3 further includes: sending capability information associated with the UE via the query, wherein the plurality of core network services are based at least in part on the capability information.

[0296] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: receiving an indication of a second core network service among the multiple core network services via the first service context used to communicate with the first core network service; sending a second service request indicating the second core network service, the second service request including a second network address associated with the second core network service; and receiving third control signaling indicating a second service context for communicating with the second core network service based at least in part on the second service request, wherein transmitting the first service message is based at least in part on receiving the second service context.

[0297] Aspect 6: The method according to Aspect 5 further includes: transmitting a second service message based on the second service context, the second service message including second service data for the second core network service and the second network address, wherein transmitting the first service message is at least partially based on transmitting the second service message.

[0298] Aspect 7: The method according to any one of Aspects 5 to 6, wherein the second core network service includes a security service associated with the first core network service, and the second service context includes authentication information, a key agreement, or both.

[0299] Aspect 8: The method according to any one of aspects 1 to 7, wherein the service request, the first service message, or both are sent to the DU to be relayed to the first network address associated with the first core network service.

[0300] Aspect 9: The method according to any one of aspects 1 to 8, wherein the first service context includes a radio access network configuration for communicating with the DU as part of the first core network service.

[0301] Aspect 10: The method according to any one of aspects 1 to 9 further includes: receiving additional control signaling including the first control information via a wireless connection between the UE and the DU.

[0302] Aspect 11: The method according to any one of aspects 1 to 10, wherein the first control information is identified based at least in part on a SIM associated with the UE.

[0303] Aspect 12: The method according to any one of Aspects 1 to 11, wherein each of the plurality of core network services is associated with a corresponding API of the plurality of APIs.

[0304] Aspect 13: A method according to any one of Aspects 1 to 12, wherein the multiple core network services include mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0305] Aspect 14: A method for performing wireless communication at a DU, comprising: receiving a service request from a UE, the service request indicating a first core network service among multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU, wherein the multiple core network services are associated with multiple network addresses, the service request including a first network address associated with the first core network service, the multiple network addresses including the first network address; sending the service request to the first network address; sending control signaling received from the first core network service to the UE based at least in part on the service request, the control signaling indicating a first service context for communication between the UE and the first core network service; and transmitting a first service message received from the UE to the first core network service according to the first service context, the first service message including first service data and a first network address for the first core network service.

[0306] Aspect 15: The method according to Aspect 14 further includes: sending a second control signaling to the UE indicating the multiple core network services provided by the service-based network, the second control signaling indicating the multiple network addresses associated with the multiple core network services, wherein receiving the service request is at least partially based on sending the second control signaling.

[0307] Aspect 16: The method according to any one of Aspects 14 to 15 further includes: sending a query for the multiple core network services; and receiving an indication of the multiple core network services in response to the query, wherein sending the control signaling is at least partially based on receiving the indication of the multiple core network services.

[0308] Aspect 17: The method according to Aspect 16 also includes: sending a network address associated with a core network discovery service provided by the service-based network to the UE, wherein the query is received from the UE and is sent to the core network discovery service based at least in part on the network address.

[0309] Aspect 18: The method according to any one of aspects 16 to 17 further comprises: sending capability information associated with the UE via the query, wherein the plurality of core network services are based at least in part on the capability information.

[0310] Aspect 19: The method according to any one of Aspects 14 to 18 also includes: sending an indication of a second core network service among the multiple core network services via the first service context used to communicate with the first core network service; receiving a second service request indicating the second core network service from a UE, the second service request including a second network address associated with the second core network service; sending the second service request to the second network address; and sending second control signaling received from the second core network service to the UE based at least in part on the second service request, the second control signaling indicating a second service context for communication between the UE and the second core network service, wherein transmitting the first service message is at least in part based on sending the second service context.

[0311] Aspect 20: The method according to Aspect 19 also includes: transmitting a second service message received from the UE to the second core network service according to the second service context, the second service message including second service data for the second core network service and the second network address, wherein transmitting the first service message is at least partially based on transmitting the second service message.

[0312] Aspect 21: The method according to any one of Aspects 19 to 20, wherein the second core network service includes a security service associated with the first core network service, and the second service context includes authentication information, a key agreement, or both.

[0313] Aspect 22: The method according to any one of aspects 14 to 21, wherein the first service context includes a radio access network configuration for communicating with the UE as part of the first core network service.

[0314] Aspect 23: The method according to any one of aspects 14 to 22, wherein each of the plurality of core network services is associated with a corresponding API of the plurality of APIs.

[0315] Aspect 24: A method according to any one of Aspects 14 to 23, wherein the multiple core network services include mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0316] Aspect 25: A method for performing wireless communications at a first core network service, comprising: receiving a service request indicating the first core network service from a UE via a DU, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a plurality of core network services provided by a service-based network configured to be interfaced with a RAN associated with the DU; sending first control signaling to the UE via the DU based at least in part on the service request, the first control signaling indicating a first service context for communicating with the first core network service; and receiving a first service message based on the first service context, the first service message including first service data and a first network address for the first core network service.

[0317] Aspect 26: The method according to Aspect 25 further includes: sending an indication of a second core network service among the multiple core network services via the first service context used to communicate with the first core network service, wherein receiving the first service message is at least partially based on the indication of the second core network service.

[0318] Aspect 27: The method according to Aspect 26, wherein the second core network service includes a security service associated with the first core network service.

[0319] Aspect 28: The method according to any one of aspects 25 to 27, wherein the first service context includes a radio access network configuration for communication between the UE and the DU as part of the first core network service.

[0320] Aspect 29: The method according to any one of aspects 25 to 28, wherein each of the plurality of core network services is associated with a corresponding API of the plurality of APIs.

[0321] Aspect 30: A method according to any one of Aspects 25 to 29, wherein the multiple core network services include mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0322] Aspect 31: A method for wireless communication at a core network discovery service, comprising: receiving, via a DU, from a UE a query for multiple core network services provided by a service-based network configured to interface with a RAN associated with the DU; and sending first control signaling indicating the multiple core network services to the DU for relaying to the UE, the first control signaling indicating multiple network addresses associated with the multiple core network services.

[0323] Aspect 32: The method according to aspect 31 further includes: sending a network address associated with the core network discovery service provided by the service-based network to the DU, wherein the query is received based at least in part on the network address.

[0324] Aspect 33: The method according to any one of aspects 31 to 32 further includes: receiving capability information associated with the UE via the query, wherein the plurality of core network services are based at least in part on the capability information.

[0325] Aspect 34: The method according to any one of aspects 31 to 33, wherein each of the plurality of core network services is associated with a corresponding API of the plurality of APIs.

[0326] Aspect 35: A method according to any one of Aspects 31 to 34, wherein the multiple core network services include mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0327] Aspect 36: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of Aspects 1 to 13.

[0328] Aspect 37: 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 13.

[0329] Aspect 38: 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 13.

[0330] Aspect 39: 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 the method of any one of aspects 14 to 24.

[0331] Aspect 40: An apparatus for wireless communication at a DU, comprising at least one unit for performing the method according to any one of aspects 14 to 24.

[0332] Aspect 41: 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 14 to 24.

[0333] Aspect 42: An apparatus for wireless communication at a first core network service, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 25 to 30.

[0334] Aspect 43: An apparatus for wireless communication at a first core network service, comprising at least one unit for performing the method according to any of aspects 25 to 30.

[0335] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication at a first core network service, the code comprising instructions executable by a processor to perform the method according to any one of aspects 25 to 30.

[0336] Aspect 45: An apparatus for wireless communication at a core network discovery location, 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 31 to 35.

[0337] Aspect 46: An apparatus for wireless communication at a core network discovery, comprising at least one unit for performing the method according to any of aspects 31 to 35.

[0338] Aspect 47: A non-transitory computer-readable medium storing code for wireless communication at a core network discovery, the code comprising instructions executable by a processor to perform the method according to any one of aspects 31 to 35.

[0339] 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.

[0340] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may be applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applied 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.

[0341] 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, light fields or optical particles, or any combination thereof.

[0342] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed by 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).

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

[0344] Computer-readable medium includes non-transitory computer storage medium and communication medium, including any medium that helps to transfer 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 any other non-transitory medium that 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 sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0345] As used herein, including in the claims, "or" when 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, 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".

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

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

[0348] 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." Specific embodiments include specific details for providing an understanding of the technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

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

Claims

1. A method for wireless communication at a user equipment (UE), comprising: identifying first control information indicating a plurality of core network services provided by a service-based network configured to interface with a radio access network (RAN) associated with a distributed unit, the first control information indicating a plurality of network addresses associated with the plurality of core network services; sending, based at least in part on the first control information, a service request indicative of a first core network service among the plurality of core network services, the service request comprising a first network address associated with the first core network service, the plurality of network addresses including the first network address; receiving control signaling indicating a first service context for communicating with the first core network service based at least in part on the service request; as well as A first service message including first service data for the first core network service and the first network address is sent according to the first service context.

2. The method according to claim 1, further comprising: sending a query for the plurality of core network services based at least in part on establishing a wireless connection between the UE and the distributed unit; as well as The first control information is received in response to the query.

3. The method according to claim 2, further comprising: A network address associated with a core network discovery service provided by the service-based network is received from the distributed unit, wherein the query is sent to the core network discovery service based at least in part on the network address.

4. The method according to claim 2, further comprising: Capability information associated with the UE is sent via the query, wherein the plurality of core network services are based at least in part on the capability information.

5. The method according to claim 1, further comprising: receiving, via the first service context for communicating with the first core network service, an indication of a second core network service of the plurality of core network services; sending a second service request indicating the second core network service, the second service request comprising a second network address associated with the second core network service; as well as Third control signaling indicating a second service context for communicating with the second core network service is received based at least in part on the second service request, wherein transmitting the first service message is based at least in part on receiving the second service context.

6. The method according to claim 5, further comprising: A second service message is transmitted according to the second service context, the second service message comprising second service data for the second core network service and the second network address, wherein transmitting the first service message is based at least in part on transmitting the second service message.

7. The method according to claim 5, wherein: The second core network service includes a security service associated with the first core network service, wherein the second service context includes authentication information, a key agreement, or both.

8. The method according to claim 1, wherein: The service request, the first service message, or both are sent to the distributed unit for relaying to the first network address associated with the first core network service.

9. The method according to claim 1, wherein: The first service context includes a radio access network configuration for communicating with the distributed unit as part of the first core network service.

10. The method according to claim 1, further comprising: Additional control signaling including the first control information is received via a wireless connection between the UE and the distributed unit.

11. The method according to claim 1, wherein: The first control information is identified based at least in part on a subscriber identity module associated with the UE.

12. The method according to claim 1, wherein: Each of the plurality of core network services is associated with a corresponding application programming interface of the plurality of application programming interfaces.

13. The method according to claim 1, wherein: The plurality of core network services include mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

14. A method for wireless communication at a distributed unit, comprising: receiving a service request from a user equipment (UE), the service request indicating a first core network service of a plurality of core network services provided by a service-based network configured to interface with a radio access network (RAN) associated with the distributed unit, wherein the plurality of core network services are associated with a plurality of network addresses, the service request including a first network address associated with the first core network service, the plurality of network addresses including the first network address; sending the service request to the first network address; sending, based at least in part on the service request, control signaling received from the first core network service to the UE, the control signaling indicating a first service context for communication between the UE and the first core network service; and A first service message received from the UE is transmitted to the first core network service according to the first service context, the first service message including first service data for the first core network service and the first network address.

15. The method according to claim 14, further comprising: sending, to the UE, second control signaling indicating the plurality of core network services provided by the service-based network, the second control signaling indicating the plurality of network addresses associated with the plurality of core network services, wherein receiving the service request is based at least in part on sending the second control signaling.

16. The method according to claim 14, further comprising: sending a query for the plurality of core network services; as well as An indication of the plurality of core network services is received in response to the query, wherein sending the control signaling is based at least in part on receiving the indication of the plurality of core network services.

17. The method according to claim 16, further comprising: A network address associated with a core network discovery service provided by the services-based network is sent to the UE, wherein the query is received from the UE and sent to the core network discovery service based at least in part on the network address.

18. The method according to claim 16, further comprising: Capability information associated with the UE is sent via the query, wherein the plurality of core network services are based at least in part on the capability information.

19. The method according to claim 14, further comprising: sending an indication of a second core network service of the plurality of core network services via the first service context for communicating with the first core network service; receiving, from the UE, a second service request indicating the second core network service, the second service request comprising a second network address associated with the second core network service; sending the second service request to the second network address; as well as Sending, to the UE, second control signaling received from the second core network service based at least in part on the second service request, the second control signaling indicating a second service context for communication between the UE and the second core network service, wherein transmitting the first service message is based at least in part on sending the second service context.

20. The method according to claim 19, further comprising: A second service message received from the UE is transmitted to the second core network service according to the second service context, the second service message comprising second service data for the second core network service and the second network address, wherein transmitting the first service message is at least partially based on transmitting the second service message.

21. The method according to claim 19, wherein: The second core network service includes a security service associated with the first core network service, wherein the second service context includes authentication information, a key agreement, or both.

22. The method according to claim 14, wherein: The first service context includes a radio access network configuration for communicating with the UE as part of the first core network service.

23. The method according to claim 14, wherein: Each of the plurality of core network services is associated with a corresponding application programming interface of the plurality of application programming interfaces.

24. The method according to claim 14, wherein: The plurality of core network services include mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

25. A method for wireless communication at a first core network service, comprising: receiving, via a distributed unit, from a user equipment (UE), a service request indicating the first core network service, the service request including a first network address associated with the first core network service, wherein the first core network service is included in a plurality of core network services provided by a service-based network configured to interface with a radio access network (RAN) associated with the distributed unit, Based at least in part on the service request, sending, via the distributed unit, first control signaling to the UE, the first control signaling indicating a first service context for communicating with the first core network service; and A first service message including first service data for the first core network service and the first network address is received according to the first service context.

26. The method according to claim 25, further comprising: An indication of a second core network service among the plurality of core network services is sent via the first service context used to communicate with the first core network service, wherein receiving the first service message is based at least in part on the indication of the second core network service.

27. The method according to claim 26, wherein: The second core network service includes a security service associated with the first core network service.

28. The method according to claim 25, wherein: The first service context includes a radio access network configuration for communication between the UE and the distributed unit as part of the first core network service.

29. The method according to claim 25, wherein: Each of the plurality of core network services is associated with a corresponding application programming interface of the plurality of application programming interfaces.

30. The method of claim 25, wherein: The plurality of core network services include mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

31. A method for wireless communication at a core network discovery service, comprising: receiving, from a user equipment (UE) via a distributed unit, a query for a plurality of core network services provided by a service-based network configured to interface with a radio access network (RAN) associated with the distributed unit; as well as First control signaling indicating the plurality of core network services is sent to the distributed unit for relaying to a user equipment (UE), the first control signaling indicating a plurality of network addresses associated with the plurality of core network services.

32. The method of claim 31 further comprising: A network address associated with the core network discovery service provided by the service-based network is sent to the distributed unit, wherein the query is received based at least in part on the network address.

33. The method of claim 31 , further comprising: Capability information associated with the UE is received via the query, wherein the plurality of core network services is based at least in part on the capability information.

34. The method of claim 31, wherein: Each of the plurality of core network services is associated with a corresponding application programming interface of the plurality of application programming interfaces.

35. The method of claim 31, wherein: The plurality of core network services include mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

Images