Techniques for capability indication for multiple services 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 receive signaling from a network entity indicating a set of core network services provided by a service-based network interfaced with a radio access network (RAN) associated with the network entity. A capability service may obtain UE capabilities and provide related capabilities to one or more other core network services. The UE may send an updated UE capability to a capability service, which may provide an updated capability indication to one or more services that have subscribed to an indication of receiving the updated UE capability.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. patent application No. 17 / 948,072, filed by Gholmieh et al. on September 19, 2022, entitled “TECHNIQUES FOR CAPABILITY INDICATION TO MULTIPLE SERVICES IN A SERVICE-BASED WIRELESS SYSTEM,” which 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 capability indication for multiple services 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 can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (e.g., long term evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for a communication device (which may be referred to as a user equipment (UE)).

[0005] In the context of a service-based wireless system, a random access network (RAN) may interface with a service-based network that provides or supplies various core network services. Each respective core network service may be hosted or supplied 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 that support capability indication for multiple services in a service-based wireless system. According to various aspects of the present disclosure, signaling and other mechanisms are provided 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, various aspects of the present disclosure can support signaling between a UE, a network entity (e.g., a distributed unit (DU)), and a network service (e.g., a core network service, a radio access network (RAN) service, or both) of a service-based network architecture, which enables the UE to establish and maintain connections with different network services provided by the service-based network based on the UE capabilities.

[0007] For example, the UE may establish a connection with a network entity of the RAN and may receive control signaling indicating that a capability service is provided by a service-based network interfaced with the RAN. The UE may provide a capability indication indicating one or more UE capabilities to the capability service (e.g., frequency bands and frequency band combinations on which the UE can transmit and receive, capabilities provided by the manufacturer, compatibility between service capabilities and access layer capabilities, etc.). In some cases, one or more other services provided by the service-based network, one or more distributed units, or a combination thereof may request capability information for the UE from the capability service and provide one or more UE communication parameters based on the indication of the UE capabilities provided by the capability service. In some cases, one or more other services, one or more distributed units, or a combination thereof may request a subscription associated with the UE capabilities from the capability service, and the capability service may provide an indication of any updated UE capabilities in response to the subscription request.

[0008] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving first control information via a wireless connection between the UE and a distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmitting a capability service establishment request with the capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service; and receiving second control signaling indicating a first capability service context based on the UE certificate.

[0009] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receiving first control information via a wireless connection between the UE and a distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmitting a capability service establishment request with the capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service; and receiving second control signaling indicating a first capability service context based on the UE certificate.

[0010] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for receiving first control information via a wireless connection between the UE and a distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; a unit for transmitting a capability service establishment request with the capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service; and a unit for receiving second control signaling indicating a first capability service context based on the UE certificate.

[0011] 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: receive first control information via a wireless connection between the UE and a distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmit a capability service establishment request with the capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service; and receive second control signaling indicating a first capability service context based on the UE certificate.

[0012] 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: transmitting a capability indication with the capability service, the capability indication providing one or more UE capabilities associated with at least a first service of one or more services provided by the service-based network. 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: receiving a third control signaling, the third control signaling indicating a first service context for communicating with the first service based on the capability indication. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first service may be a radio access network service, a service associated with the distributed unit, a core network service, or a UE service.

[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: receiving a capability request from the capability service; and sending a capability response to the capability service via the distributed unit in response to the capability request. 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: transmitting a capability update with the capability service, the capability update being based on one or more changed UE capabilities associated with one or more services provided by the service-based network. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the capability update indicates a duration for the one or more changed UE capabilities.

[0014] 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: transmitting a capability indication with the capability service, the capability indication indicating one or more supported combinations of component carriers, one or more frequency bands used for communication between the UE and the distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the capability indication is used to indicate one or more combinations of compatible service capabilities and access stratum capabilities.

[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: receiving a first capability definition associated with a first service, the first capability definition being defined by the first service and being independent of one or more other capabilities associated with one or more services other than the first service, and wherein the one or more UE capabilities associated with the first service are based on the first capability definition. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more UE capabilities associated with at least the first service are based on one or more frequency bands used for communication with the distributed unit.

[0016] A method for wireless communication at a distributed unit is described. The method may include: transmitting first control information via a wireless connection between a UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE certificates for the capability service; and sending second control signaling to the UE indicating a first capability service context.

[0017] An apparatus for wireless communication at a distributed unit is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: transmitting first control information via a wireless connection between a UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE certificates for the capability service; and sending second control signaling indicating a first capability service context to the UE.

[0018] Another apparatus for wireless communication at a distributed unit is described. The apparatus may include: means for transmitting first control information via a wireless connection between a UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; means for transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE certificates for the capability service; and means for sending second control signaling to the UE indicating a first capability service context.

[0019] A non-transitory computer-readable medium storing code for wireless communication at a distributed unit is described. The code may include instructions executable by a processor to: transmit first control information via a wireless connection between a UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmit a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE certificates for the capability service; and send second control signaling indicating a first capability service context to the UE.

[0020] 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: communicating with the capability service to obtain at least a first UE capability for transmission via a wireless connection between the UE and the distributed unit; and sending one or more communication parameters for the wireless connection between the UE and the distributed unit to the UE, the one or more communication parameters being based on the first UE capability.

[0021] 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: obtaining a capability update from the capability service, the capability update being based on one or more changed UE capabilities transmitted to the capability service; and changing the one or more communication parameters for the wireless connection between the UE and the distributed unit based on the capability update. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the capability update indicates a duration for the one or more changed UE capabilities. 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: transmitting a capability subscription indication to the capability service, and wherein the first UE capability may be provided by the capability service in response to the capability subscription indication sent by the distributed unit to the capability service.

[0022] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the capability service indicates one or more supported combinations of frequency bands for communication between the UE and the distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the capability service indicates one or more combinations of compatible service capabilities and access stratum capabilities. 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: providing the capability service with one or more frequency bands for the wireless connection between the UE and the distributed unit, and wherein the UE capabilities are based on the one or more frequency bands.

[0023] A method for wireless communication at a capability service provided by a service-based network is described. The method may include: transmitting first control information with a UE, the first control information indicating that the capability service is provided by the service-based network; obtaining a capability indication message, the capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by the service-based network; and providing information related to the capabilities of the UE to at least the first service.

[0024] An apparatus for wireless communication at a capability service provided by a service-based network is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: transmit first control information with a UE, the first control information indicating that the capability service is provided by the service-based network; obtain a capability indication message, the capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by the service-based network; and provide information related to the capabilities of the UE to at least the first service.

[0025] Another apparatus for wireless communication at a capability service provided by a service-based network is described. The apparatus may include: means for transmitting first control information with a UE, the first control information indicating that the capability service is provided by the service-based network; means for obtaining a capability indication message, the capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by the service-based network; and means for providing information related to the capabilities of the UE to at least the first service.

[0026] A non-transitory computer-readable medium storing code for wireless communication at a capability service provided by a service-based network is described. The code may include instructions executable by a processor to: transmit first control information with a UE, the first control information indicating that the capability service is provided by the service-based network; obtain a capability indication message, the capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by the service-based network; and provide information related to the capabilities of the UE to at least the first service.

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the transmitting and obtaining may be performed via a distributed unit. 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: obtaining a capability subscription indication from at least the first service, and wherein the information related to the capability of the UE is provided in response to the capability subscription indication.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: obtaining a capability update from the UE, the capability update being based on one or more changed UE capabilities relative to a previous capability indication of the UE; and providing updated information related to the capabilities of the UE to at least the first service in response to the capability update from the UE. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability update indicates a duration for one or more changed UE capabilities.

[0029] In some examples of methods, apparatuses, and non-transitory computer-readable media described herein, the capability indication message indicates one or more supported combinations of frequency bands for communication between the UE and a distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof. In some examples of methods, apparatuses, and non-transitory computer-readable media described herein, the capability indication message indicates one or more combinations of compatible service capabilities and access stratum capabilities.

[0030] 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: obtaining a first capability definition associated with a first service, the first capability definition being independent of one or more other capabilities associated with one or more other services different from the first service, and wherein the one or more UE capabilities associated with the first service are based on the first capability definition. 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: obtaining, from a distributed unit, an indication of one or more frequency bands used for a wireless connection between the UE and the distributed unit; filtering the one or more UE capabilities based on the one or more frequency bands to identify at least a first UE capability associated with the one or more frequency bands; and providing the first UE capability to the distributed unit. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0038] Fig. 9 A diagram of a system including devices supporting techniques for capability indication for multiple services in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

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

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

[0041] Fig.13 A diagram of a system including devices supporting techniques for capability indication for multiple services in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0042] Figures 14 to 22 A flow chart illustrating a method of supporting techniques for capability indication for multiple services in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

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

[0044] In contrast, some wireless systems (such as sixth generation (6G) systems) may exhibit a flatter service-based architecture, in which a radio access network (RAN) (e.g., a network entity) interfaces with a service-based network to connect UEs to 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 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 (e.g., "subscribe") to different network services or groups thereof on an aà la carte basis, where each network service provides or supplies 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 within a service-based system may be able to select which network services the UE will subscribe to based on the personalized characteristics or needs of the respective UE.

[0045] In some wireless systems, the RAN can be connected to a service-based network that provides various network services, and can relay communications between the UE and the corresponding network services. In particular, the UE can subscribe to various network services provided by the service-based network. However, each corresponding network service can be hosted or provided by a different operator or entity, and can be associated with a different set of parameters for communicating with the corresponding network service, and such parameters can be used on one or more capabilities of the UE. In order to provide appropriate parameters for communicating with the UE, each network service can obtain relevant UE capabilities. According to various aspects discussed herein, the capability service of the service-based network can obtain UE capability information and provide relevant UE capabilities to other network services, one or more RAN network entities (e.g., one or more distributed units), or any combination thereof.

[0046] Thus, aspects of the present disclosure relate to signaling and other mechanisms that enable a UE to provide UE capabilities to services in a service-based network, such as 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 network service of a service-based network architecture, which enables the UE to provide an indication of the UE capabilities to a capability service, and the capability service may provide an indication of the UE capabilities to one or more other network services, one or more RAN network entities, or any combination thereof.

[0047] For example, a UE may establish a connection with a DU of a network entity and may receive control signaling indicating that the network provides a capability service. The UE may send a service request to the capability service (e.g., via a relay of the DU, or via different wireless or wired technologies) and may receive a capability service context for communicating with the capability service. The UE may transmit a UE capability indication to the capability service (e.g., via the DU) based on the capability service context. The capability service may receive the UE capability indication and provide information related to one or more UE capabilities to one or more other network services, one or more DUs, or any combination thereof. In some examples, one or more other network services (such as a first network service) may determine an associated service context based on the UE capability. Additionally or alternatively, one or more DUs may determine one or more communication parameters for the UE based on the UE capability.

[0048] In some aspects, the UE may provide updates to the UE capabilities to the capability service. For example, the UE may reduce the transmission power using one or more frequency bands for a period of time, or may suspend transmission (for example, based on the transmitted millimeter wave radiation from the UE approaching or satisfying a threshold for a period of time). In such a case, the UE may provide an updated UE capability indication to the capability service. In addition, in some cases, the UE may provide an indication of the duration associated with the updated capability indication. The capability service may then provide UE capability information to other network services, network entities, or both based on the updated capability indication from the UE. In some examples, one or more other services or network entities may request a subscription to the UE capabilities from the capability service, and the capability service may provide updates to the UE capabilities based on the subscription request.

[0049] Aspects of the disclosure are first described in the context of a wireless communication system. Additional aspects of the disclosure are described in the context of an example network architecture and an example process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to techniques for capability indication for multiple services in a service-based wireless system.

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

[0051] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices of different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, access points, or network devices, among other terms. 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), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area 110. 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).

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

[0053] As described herein, a node (which may be referred to as a network node) or a wireless node of the wireless communication system 100 may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of the example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of the example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of the example, the first 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, a 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.

[0054] In some examples, the network entities 105 can communicate with the service-based network 130, or communicate with each other, or both. For example, the network entities 105 can communicate with the service-based network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). Similarly, the UE 115 can communicate with the service-based network 130 via one or more communication links 155. In some examples, the network entities 105 can communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the service-based network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 can communicate with each other via one or more communication links such as the fronthaul communication link 168 (e.g., between the radio unit 170 and the distributed unit 165). The backhaul communication link 120 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.

[0055] 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 185 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 one or more UE 115 services and the corresponding CN / RAN services 185.

[0056] One or more of the 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 (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 evolved node B, 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 that 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).

[0057] Additionally, in some examples, one or more network entities 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed across 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 the following: 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 disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located at 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)).

[0058] The functional split between components (e.g., CU, DU, and RU) is flexible and can support different functionalities, 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 upper layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality 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 the one or more DUs 165 or RUs 170 may host lower protocol layer functionality and signaling, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer), and may each be at least partially controlled by the CU. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU and DU 165 or between the DU 165 and the RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU, DU 165, or RU 170). The DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., an open fronthaul (FH) interface). In some examples, the fronthaul communication link 168 may be implemented according to an interface (e.g., a channel) between layers of a protocol stack supported by a corresponding network entity 105 communicating via such a communication link.

[0059] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for wireless 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 donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by 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., the same antennas of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration of an access network (e.g., downstream). In such cases, 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.

[0060] 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 described herein for capability indication for multiple services in a service-based wireless system. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU, a RU 170, a RIC, a SMO).

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

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

[0063] 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 having a defined physical layer structure for supporting 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 may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating operations for the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. According to the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used with both frequency division duplex (FDD) component carriers 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 communicating with another device (e.g., directly or via one or more other network entities 105).

[0064] 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 operate in a standalone mode, in which case a UE 115 may perform initial acquisition and connection via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0065] 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 configurations of transmissions. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

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

[0067] 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 one symbol period (e.g., the duration of one modulation symbol) and one 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.

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

[0069] The 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 time intervals for the network entity 105 or the UE 115 may be expressed as multiples of a supported discrete Fourier transform (DFT) size). The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

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

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

[0072] Physical channels may be multiplexed according to various techniques to communicate using carriers. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search 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 at 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 coding 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 .

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

[0074] 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 the 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 105105 may support one or more cells, and may also support communication via one or more cells using one or more component carriers.

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

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

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

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

[0079] 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 of 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 aspects of such D2D communication configured by the network entity 105 (e.g., scheduled by the network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105 or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, groups of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

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

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

[0082] 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, because the wavelengths 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 be sufficient to penetrate the structure for macro cells to provide service to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communications using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0083] The wireless communication system 100 may also operate using a super high frequency (SHF) region that may be in the range of from 3 GHz to 30 GHz (also referred to as a centimeter band) or an extremely high frequency (EHF) region (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band) using a spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and a network entity (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and more closely spaced than the UHF antenna. 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 shorter distances than SHF or UHF transmissions. The technology disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may differ according to countries or regulatory agencies.

[0084] The wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ licensed 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 employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on a carrier aggregation configuration of component carriers in combination with operations using licensed bands (e.g., LAA). Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, as well as other examples.

[0085] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which may be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operations or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (e.g., 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.

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

[0087] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to form 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 can be achieved by combining signals transmitted via antenna elements of an antenna array so that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals transmitted via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of the antenna elements may be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0088] 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. The network entity 105 may send some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times 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.

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

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

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

[0092] In some examples, the wireless communication system 100 may include a packet-based network that operates using a cloud platform, such as 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 the 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) may allow for the flexibility of hosting some functions (e.g., layer 2 (L2) functions) anywhere in the cloud, and may enable enhanced scalability, resilience, elasticity, agility, reuse, visibility, automation, failover, or any combination thereof (e.g., each service across the RAN and core network may be independently scalable by independently increasing or decreasing resources allocated across the functions). Furthermore, efficiency may be enhanced by providing real-time link management to the RAN edge and allowing adaptation at the DU 165 to more efficiently activate, deactivate, or select features based on UE conditions.

[0093] 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, various aspects of the present disclosure relate 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 the service-based network architecture, which enables the UE 115 to establish and maintain connections with different network entities 105, different core network services (e.g., the CN / RAN service 185) provided by the network, or any combination thereof based on the capabilities of the UE transmitted via the capability service at the service-based network 130. Therefore, the techniques described herein can enable the UE 115 to obtain a capability service context for a capability service and provide a UE 115 capability indication to the capability service. The capability service can receive the UE 115 capability indication and provide an indication of the UE capability to one or more other services, one or more network entities 105, or any combination thereof. The indication of UE 115 capabilities may be used by one or more other services or one or more network entities 105 to determine various communication parameters.

[0094] 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 a capability service provided by the network (e.g., as part of a CN / RAN service 185). In some cases, the UE 115 may also receive a network address of the provided network service. The UE 115 may then send (via a relay of the DU 165) a capability service request to the network address of the capability service and may receive (via a relay of the DU 165) a capability service context for communicating with the capability service. The UE 115 may then provide the UE 115 capability indication to the capability service, and the capability service may manage capability information for multiple UEs 115 and provide related capabilities to one or more other services or network entities 105. Thus, rather than each service having to individually request an indication of capabilities from the UE 115, the capability service may obtain the UE 115 capabilities and provide related information to other services or entities.

[0095] In some aspects, UE 115 may be able to provide capability updates to a capability service. For example, the capabilities of UE 115 may change from a previous UE 115 capability indication (e.g., due to RF transmission limitations at UE 115, thermal conditions at UE 115, power state at UE 115, etc.), and an updated capability indication may be provided to the capability service. In some examples, UE 115 may also provide a time period during which the updated capabilities are values ​​(e.g., a time period during which the RF transmission limitations will change to allow UE 115 to transmit using one or more frequency bands associated with the RF transmission limitations). The capability service may receive the updated capability indication and provide the associated UE 115 capabilities to other services or network entities 105 accordingly. In some examples, one or more other services or network entities 105 may provide a subscription request to the capability service and may be notified of the updated capabilities based on the updated capability indication received at the capability service.

[0096] The techniques described herein may enable a UE 115 to efficiently establish and maintain connections (e.g., subscriptions) to core network services provided by a service-based network (e.g., within a 6G system) based on the capabilities of the UE 115. In particular, the techniques described herein may enable a UE 115 to provide a capability indication to a capability service, wherein the capability service may coordinate with other CN / RAN services 105, with other network entities 105, or any combination thereof, to provide communications using parameters according to the capabilities of the UE 115. By enabling a UE 115 to provide a capability indication to a capability service, various aspects of the present disclosure may enable a UE 115 to establish connections with various core network or RAN services that may be provided by different operators or entities without providing a separate capability indication for each service. 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 the respective UE 115, thereby improving customization and the overall user experience at the UE 115. In addition, by enabling UE 115 to provide capability indications to capability services, the techniques described herein may enable UE 115 to avoid transmitting unnecessary or unwanted capability indications to multiple different core network services, thereby reducing control signaling within the network, improving resource utilization, and reducing power consumption at UE 115.

[0097] Figure 2 An example of a wireless communication system that supports techniques for capability indication for multiple services 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 or be implemented by aspects of the wireless communication system 100. In some implementations, the wireless communication system 200 illustrates a service-based wireless communication system (such as a wireless communication system based on a wireless communication system). Figure 1 An example architecture of a 6G network described herein.

[0098] 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 a cloud platform or be associated with a cloud platform, wherein the corresponding core network services 215 are hosted at corresponding network addresses in the cloud platform.

[0099] 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., dock) with the service-based network 205 via one or more communication links (e.g., communication link 225), wherein the communication link 225 may be configured to facilitate bidirectional communication between the network entity 105-a and the corresponding core network service 215 of the service-based network 205.

[0100] like Figure 2 As shown, the wireless communication system 200 may present a service-based architecture in which entities of the RAN 210 (e.g., the network entity 105-a) are configured to connect the UE 115-a to the core network services 215 of the service-based network 205. In particular, the RAN 210 (e.g., the network entity 105-a) may be configured to relay communications between the UE 115-a and various core network services 215 of the service-based network to enable the UE 115-a to establish and maintain a wireless connection 215 with the corresponding core network service in order to exchange communications associated with various network functions supported by the corresponding core network service 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 based on the capabilities of the UE 115, the applications executed at the UE 115, the mobility of the UE 115, etc.

[0101] 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 a cloud-based network, wherein the components of each core network service 215 can be associated with a corresponding network address. The corresponding core network service 215 can be provided by a network provider, a third-party entity, etc., wherein 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.

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

[0103] In some aspects, each core network service 215 may include a corresponding API configured to facilitate wireless communications with the network entity 105-a and the UE 115-a, such as Figure 1 . The API at the corresponding core network service 215 may include a routing API, a configuration API, or both. The routing API may be configured for service data unit communication between the UE 115-a and the corresponding core network service 215. In contrast, the configuration API may be configured to facilitate communication between the network entity 105-a and the corresponding core network service 215 to negotiate service requirements and service specific operations.

[0104] 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 respective 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), wherein the multiple network entities 105 facilitate traffic routing with the same or different groups 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, and the like. For example, access layer configuration may be associated with service specific configuration (eg, logical channels corresponding to QoS flows for each respective core network service 215) and service agnostic configuration (eg, parameters common to all core network services 215).

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

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

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

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

[0109] 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 (such as a 6G network) based on the capabilities of the UE 115-a. In particular, aspects of the present disclosure relate to signaling that enables the UE 115-a to provide capability indications to a capability service that manages indicating the UE 115-a capabilities to multiple different core network services 215 and network entities 105.

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

[0111] 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, the network entity 105 may include a wired interface that is configured to receive or send signals to one or more of the other network entities 105 via a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive or send signals, or both, to one or more other network entities 105 via a wireless transmission medium.

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

[0113] 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 docking with a service-based network 305, DU165-a may host one or more APIs for one or more services of the service-based network 305 and one or more corresponding services at one or more UEs 115-b. In some examples, when docking with CU 310, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., a high PHY layer, such as a module for FEC encoding and decoding, scrambling, modulation, and demodulation, etc.), which depends at least in part on the functional split, such as the functional split defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to transmit signals to other layers hosted by DU 165-a, or implemented using a control function hosted by CU 310.

[0114] 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 splitting (such as lower layer functional splitting). In such an architecture, 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 RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable DU 165-a and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0116] The non-RT RIC 330-b can be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 330-a. The non-RT RIC 330-b can be coupled to or communicate with the near-RT RIC 330-a (e.g., via an A1 interface). The near-RT RIC 330-a can be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions through 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.

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

[0118] 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, such as 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 provide UE capabilities to a capability service that manages indicating capabilities to a plurality of different core network services and network entities.

[0119] Figure 4 An example of a wireless communication system 400 that supports techniques for capability indication for multiple services in a service-based wireless system in accordance with one or more aspects of the present disclosure 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 communications with core network services of a service-based network (such as a 6G network), such as with respect to Figure 1 Described.

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

[0121] Core network services 410 can be used with service-based networks such as Figure 2 4) is associated with the service-based network 205 shown in FIG. In some aspects, the service-based network including the core network service 410 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 410 can be associated with a cloud platform or hosted by a cloud platform, wherein the corresponding core network service 410 is hosted at a corresponding network address in the cloud platform.

[0122] The UE 115-b may communicate with the network entity 105-b using a communication link 415, 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 415 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 (e.g., interface with) a capability service 405 and a core network service 410 of a service-based network via communication links 420-a, 420-b, 420-c, and 420-d, where the communication link 420 may be configured to facilitate bidirectional communication with the network entity 105-b. In some aspects, the capability service 405 and each core network service 410 may include corresponding APIs 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 .

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

[0124] As mentioned previously herein, some legacy wireless systems (e.g., 4G / 5G communication systems) may exhibit a relatively vertical layered architecture that includes many different "layers" of devices that perform functions for the system. For example, a legacy wireless system may include a UE, a base station / network entity, and many backend devices, such as a mobility management entity (MME), a session management function (SMF), and an access and mobility management function (AMF). When moving from a 4G system to a 5G system, the CORE / RAN functional split remains largely unchanged. In particular, 3G and 4G systems introduced a CORE / RAN hierarchy based on device models and deployments to meet performance and security requirements for accessibility of field devices, and as part of the design, the 5G system did not reconsider the split for cloud deployments.

[0125] The layered structure of 5G communication systems often results in processing and other functions being performed on 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 the system and complicating the system's ability to provide customized services and functions to wireless devices.

[0126] In contrast, some wireless systems (such as 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 several centralized backend components (e.g., AMF, MME, SMF) of some traditional systems may be distributed across multiple core network services, which may be hosted at different network addresses, such as in a cloud architecture. In other words, a 6G network may exhibit a more cloud-native architecture in which network functions and protocols are split into self-contained services (e.g., capability services 405 and core network services 410) rather than all-encompassing network functions and network protocols.

[0127] 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 the corresponding network functions and protocols to be operated and managed by self-contained capability services 405 and core network services 410. The merging of CORE and RAN services can simplify protocols and reduce duplication of processing and operations across CORE and RAT. New merged services can be hosted based on the deployment topology and capabilities of each corresponding service.

[0128] 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 capability services 405 and multiple core network services 410). 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, resilience, elasticity, flexibility, reuse, visibility, automation, and failover. In addition, the service-based architecture can enable each service across the RAN and CORE to scale independently by independently increasing or decreasing the resources allocated across the corresponding services.

[0129] In addition, a service-based wireless system (such as the wireless communication system 400) can restructure the functional split for CORE and RAN (e.g., CORE and RAN 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 the cloud deployment / platform. 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 the QoS requirements of each corresponding core network service 410. For example, operations and protocols previously performed by the AMF, CU, CP, DU, or any combination thereof in the context of a 4G / 5G system can now be performed by the capability service 405 and multiple core network services 410 of a service-based network, which can be hosted in a cloud platform. In some cases, the 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, the cloud platform can implement adaptation at the DU to allow more efficient activation, deactivation, and selection of features based on UX requirements, and can enable the configuration (e.g., RRC) and activation (e.g., MAC) of performance-sensitive features to be decoupled.

[0130] A service-based wireless system can implement modular protocols across services (e.g., across core network services 410). More specifically, a service-based wireless system can decompose monolithic protocols to implement cloud-native protocol designs for CORE, RAN, and devices (e.g., UE). 3GPP defines protocols based on network-centric designs and limits innovation through releases. Monolithic protocols at 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 where 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 a vertical long tail, where protocols can be specialized for each core network service 410 and can be upgraded or modified individually. Such a cloud-native device model can enable adaptability across different verticals and deployment types (e.g., cloud-native CI / CD protocol upgrades) and promote supplier diversity for each core network service 410.

[0131] The RAN-CORE C-plane protocol split provided by the service-based wireless network can realize the vertical convergence of operations and protocols across the previous DU, DU, AMF and SMF structures into capability services 405 and multiple core network services 410. 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 410 (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 410 (e.g., connection services, SRB / DRB services, etc.), new eDU functions, or both. In addition, the RAN-CORE C-plane protocol split can realize the horizontal splitting (e.g., modularization) of different network operations and functions across capability services 405 and multiple core network services 410.

[0132] Thus, a UE 115 in a service-based system can establish and maintain connections (e.g., "subscribe") to capability services 405 and different core network services 410 on a per-order basis, wherein the capability services 405 and each core network service provision or provide corresponding 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 115 within the service-based system can select which core network services 410 the UE 115 will subscribe to based on the individual characteristics or needs of the corresponding UE 115.

[0133] The process for establishing a connection with the core network service 410 (e.g., subscribing to the core network service 410) 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 from the network entity 105-b, a system information service (e.g., a core network system information service), or both. 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.

[0134] 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 410-a) may be established as the first core network service 410 of the service group. That is, as part of the service establishment phase, the UE 115-b may subscribe to the security service (e.g., the first core network service 410-a). Subsequently, during the service discovery sub-phase, the UE 115-b may identify the capability services 405 and the core network services 410 provided / available within the system. In some cases, the network entity 105-b may indicate which core network services 410 (including the capability services 405) are provided or available. Additionally or alternatively, the UE 115-b may query a discovery service (e.g., a second core network service 410-b) in order to perform service discovery. Finally, during service configuration, the UE 115 - b may send a service request to a provided core network service 410 (eg, the third core network service 410 - c ) and may receive a service context 410 for communicating with the core network service.

[0135] In some aspects, UE 115-b may send a capability service request to capability service 405, and capability service 405 may provide capability service context to UE 115-b (e.g., via APIs running at capability service 405, network entity 105-b, and UE 115-b). Parameters for communicating with capability service 405 that may be indicated via capability service context may include the type or format of signaling and information to be exchanged between UE 115-b and capability service 405, resources used for communication between UE 115-b and capability service 405, HARQ processes used for communication between UE 115-b and capability service 405, associated or related core network services 410 required for performance of capability service 405, and the like. Subsequently, during a service activation phase, UE 115-b and capability service 405 may activate the capability service at UE 115-b (e.g., capability service 405 transitions to an active state at UE 115-b), and UE 115-b and capability service 405 may communicate with each other (via network entity 105-b) based on the service context. Finally, during a service deactivation phase, capability service 405 may transition to an inactive state at UE 115-c (e.g., there is no active communication between UE 115-b and capability service 405). Although this example discusses techniques related to capability service 405 and UE 115-b, similar techniques may be used for other core network services 410.

[0136] In some examples, when the capability service 405 is active, the UE 115-b may provide capability indications of one or more capabilities of the UE 115-b to the capability service 405. In a service-based wireless system, the UE may need to transmit multiple capabilities related to multiple services, including one or more access stratum (AS) related services and one or more non-access stratum (NAS) services. According to various aspects, instead of the UE 115-b having to allocate its capabilities individually to multiple services 410, a capability service 405 is provided, and the capability service 405 is common to all services 410 (for example, the capability service 405 is a service for other core network services 410). In some examples, the capability service may provide processes for querying, updating, and saving UE 115-b capabilities. In addition, the capability service 405 may communicate with other core network services 410, for example via a link 425 between the core network service 410 and the capability service 405. In some examples, capability service 405 may store UE 115-b capabilities and, in response to a query from another service 410 or from network entity 105, may provide an indication of the capabilities of UE 115-b. In some examples, capability service 405 may provide subscription and capability change notifications to other core network services 410.

[0137] Furthermore, in some examples, the capabilities service 405 may provide filtering of a complete list of UE 115-b capabilities based on the capabilities of the query service (e.g., an eDU may be interested in a subset of frequency bands deployed locally at the eDU, and the capabilities service 405 may provide UE 115-b capabilities related to the subset of frequency bands). In some examples, the capabilities service 405 may trigger a capabilities query of the UE 115-b to obtain more details of the UE 115-b capabilities (e.g., frequency band combination details). Additionally or alternatively, a capability update may be triggered by the UE 115-b (e.g., a temporary reduction in capability due to RF emission limitations, thermal constraints, power constraints, etc.). In some examples, the capability service 405 may also store capabilities provided by the manufacturer of the UE 115-b (e.g., UE radio capability signaling optimization, RACS, capabilities), may report UE 115-b capabilities based on the service or entity requesting the information (e.g., adapting capabilities to an eDU query for frequency bands supported by the eDU), may manage multiple types of capabilities (e.g., AS capabilities, service-related capabilities), may provide indications of compatibility between service capabilities and AS capabilities, or any combination thereof. In some aspects, one or more core network services 410 may also define their own independent capability requirements, which may be different from the capabilities of other services, and the UE 115-b may subscribe to services based on the UE 115-b capabilities satisfying the defined capability requirements.

[0138] Figure 5 An example of a process flow 500 is shown for supporting techniques for capability indication for multiple services in a service-based wireless system in accordance with one or more aspects of the present disclosure. In some examples, aspects of the process flow 500 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, or any combination thereof. In particular, the process flow 500 illustrates signaling that enables a UE 115-c to subscribe to a capability service 505, which enables the UE 115-c to communicate capabilities between the UE 115-c, the network entity 105-c, and one or more other services 510 provided by the service-based network, as described with reference to FIG. Figure 1-4 and other aspects described.

[0139] The process flow 500 may include the UE 115-c, the network entity 105-c, the capability service 505, and one or more other core network services 510 (e.g., core network security services, discovery services, mobility services, etc.), which may be referenced. Figure 1-4Examples of UE 115, network entities 105, core network services, and other wireless devices are described. In some aspects, capability service 505 may store information associated with UE 115-c capabilities (as well as capabilities of one or more other UEs) and may facilitate indication of capabilities of UE 115-c within the network.

[0140] In some aspects, capability services 505, other services 510, or any combination thereof may be included in a service-based network such as Figure 2 In such a case, the service-based network including the capability service 505 and one or more other services 510 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.

[0141] 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 additional steps may be added.

[0142] At 515, 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 515, the UE 115-c may not have established communications with any core network services and, therefore, may not have any service context information for communicating with the corresponding core network services.

[0143] At 520, the UE 115-c may receive capability service information from the capability service 505 (e.g., via the network entity 105-c). In some aspects, the capability service information may be received as part of a discovery process (e.g., provided by a discovery service of other network services 510) that communicates a set of core network services provided / provisioned by a service-based network configured to interface with a RAN including the network entity 105-c. The core network services that may be provisioned or provided by the wireless communication system may include, but are not limited to, mobility services, connection state management services, capability services 505, paging services, radio access services, QoS configuration and data services, location services, messaging services, and the like. In addition, each core network service may be associated with a corresponding API that enables communication between the corresponding core network service and the UE 115-c / network entity 105-c.

[0144] At 525, the UE 115-c may send a capability service request to establish communications with the capability service 505. For example, the network entity 105-c may relay the request from the UE 115-c to the capability service 505. As another example, the UE 115-c may receive a network address for the capability service 505 from the network entity 105-c and may send a query to the network address 505 for the capability service, where the network entity 105-c is configured to relay the query to the indicated network address.

[0145] At 530, the network entity 105-c may receive control signaling indicating a service context (e.g., service configuration information) for communicating with the capability service 505. The network entity 105-c may send a response message to the capability service 505 and may send (e.g., relay) the control signaling / service context to the UE 115-c. 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 capability service 505 (e.g., a service configuration request) and, if desired, may indicate radio access requirements / parameters for the capability service 505.

[0146] At 535, the UE 115-c may send a capability indication to the capability service 505 (e.g., via the network entity 105-c). In some aspects, the capability indication may include information that enables the capability service 505 to determine which core network services may be provided to the UE 115-c (or accessible by the UE 115-c). In some aspects, the capability service 505 may determine whether the UE 115-c is capable of performing communications for other core network services 510. In some cases, such a determination may be based on the capability information provided in the capability indication. Although in Figure 5 In the example of , the capability indication is shown as being relayed by the network entity 105 - c , but communication with the service may occur over other wireless technologies such as Bluetooth or Wi-Fi, or may occur over a wired network (e.g., Ethernet or a USB port).

[0147] At 540, the network entity 105-c may send a capability request to the capability service 505 to obtain an indication of the capabilities of the UE 115-c. Additionally, at 545, one or more of the other services 510 may send a capability request to the capability service to obtain an indication of the capabilities of the UE 115-c. At 550, the capability service 505 may provide a capability notification to the network entity 105-c indicating the capabilities of the UE 115-c associated with the network entity 105-c (e.g., supported frequency band combinations for the set of frequency bands indicated by the capability request of the network entity 105-c). Additionally, at 555, the capability service 505 may provide a capability notification to one or more other services 510 indicating the capabilities of the UE 115-c associated with one or more other services 520.

[0148] exist Figure 5 In the example shown, at 560, the network entity 105-c may send one or more communication parameters (e.g., DU communication parameters) to the UE 115-c, which may include one or more wireless parameters for communication between the UE 115-c and the network entity 105-c (e.g., based on the frequency band combination indicated in the UE capabilities). Additionally or alternatively, at 565, one or more other services 510 may transmit to the UE 115-c (e.g., via the network entity 105-c) a service context for associated communications between the UE 115-c and the service 510, wherein the one or more communication parameters are based on the UE 115-c capabilities provided by the capability service 505.

[0149] In some aspects, as indicated at 570 and 575, the network entity 105-c, the one or more other services 510, or both may provide a subscription request to the capabilities service 505. For example, the one or more other services 510 may use a first set of communication parameters when the UE 115-c is capable of communicating using a first combination of frequency bands, and may use a second set of communication parameters when the UE 115-c is capable of communicating using a second combination of frequency bands. In such a case, the one or more other services 510 may provide a subscription request to the capabilities service 505 in order to be notified of changes in the capabilities of the UE 115-c.

[0150] In some examples, as indicated at 580, the UE 115-c may provide an updated capability indication to the capability service 505. For example, the UE 115-c may communicate using a first set of frequency bands having associated RF emission limits for a period of time, and based on satisfying the RF emission limits, the UE 115-c may stop using the first set of frequency bands within a time window that brings the UE 115-c back within the RF emission limits. Based on different available frequency bands, the UE 115-c may send an updated capability indication. In this example, the capability service 505 may obtain an updated capability indication (e.g., via the network entity 105-c) and, at 585 and 590, provide an updated capability notification to one or both of the network entity 105-c and the other services 510 that have provided a subscription request. In some examples, based on the updated UE 115-c capabilities, the network entity 105-c may provide updated DU communication parameters to the UE 115-c (e.g., based on the updated UE 115-c capabilities for communication using a different frequency band) at 595. Additionally or alternatively, at 597, one or more other services 510 may provide updated service context to the UE 115-c based on the updated capabilities.

[0151] Figure 6 A block diagram 600 of a device 605 supporting techniques for capability indication for multiple 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 communicate with each other (e.g., via one or more buses).

[0152] The receiver 610 may provide a means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for capability indication for multiple services in a service-based wireless system). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0153] 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 techniques for capability indication for multiple services 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 a collection of multiple antennas.

[0154] 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 the techniques for capability indication for multiple services 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.

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

[0156] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations 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 or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

[0157] In some examples, the communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating 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 integrate with the receiver 610, the transmitter 615, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0158] According to examples as disclosed herein, the communication manager 620 may support wireless communications at the UE. For example, the communication manager 620 may be configured to or otherwise support a unit for receiving first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that the capability service is provided by a service-based network configured to interface with the UE via the distributed unit. The communication manager 620 may be configured to or otherwise support a unit for transmitting a capability service establishment request with the capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service. The communication manager 620 may be configured to or otherwise support a unit for receiving a second control signaling indicating a first capability service context based on the UE certificate.

[0159] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, 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 such as within a 6G system based on UE capabilities (e.g., subscribe to a core network service). In particular, the techniques described herein can enable the UE 115 to obtain a service context for a capability service and provide UE capabilities to the capability service. The capability service can provide UE capabilities to other entities and services. By enabling UE 115 capability indications via the capability service, various aspects of the present disclosure can enable the UE 115 to establish connections with various core network services provided by different operators or entities with efficiency and relatively low overhead. Therefore, the techniques described herein can enable the UE 115 to subscribe to different core network services on a per-order basis according to the needs or requirements of the corresponding UE 115 and services, thereby improving the customization and overall user experience at the UE 115. Furthermore, the techniques described herein may enable the 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 the UE 115 .

[0160] Figure 7A block diagram 700 of a device 705 supporting techniques for capability indication for multiple 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 communicate with each other (e.g., via one or more buses).

[0161] The receiver 710 may provide a means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for capability indication for multiple services in a service-based wireless system). The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

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

[0163] The device 705 or its various components may be examples of units for performing various aspects of the technology for capability indication for multiple services in a service-based wireless system as described herein. For example, the communication manager 720 may include a control signaling manager 725, a capability service manager 730, a service context manager 735, 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 perform various operations (e.g., receive, obtain, monitor, output, send) using the receiver 710, the transmitter 715, or both or in other ways in cooperation with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 may receive information from the receiver 710, send information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0164] According to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. The control signaling manager 725 may be configured as or otherwise support a unit for receiving first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that the capability service is provided by a service-based network configured to interface with the UE via the distributed unit. The capability service manager 730 may be configured as or otherwise support a unit for transmitting a capability service establishment request with the capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service. The service context manager 735 may be configured as or otherwise support a unit for receiving a second control signaling indicating a first capability service context based on the UE certificate.

[0165] Figure 8 A block diagram 800 of a communication manager 820 supporting techniques for capability indication for multiple services 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 capability indication for multiple services in a service-based wireless system as described herein. For example, the communication manager 820 may include a control signaling manager 825, a capability service manager 830, a service context manager 835, a capability indication manager 840, a capability update manager 845, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0166] According to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. The control signaling manager 825 may be configured as or otherwise support a unit for receiving first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that the capability service is provided by a service-based network configured to interface with the UE via the distributed unit. The capability service manager 830 may be configured as or otherwise support a unit for transmitting a capability service establishment request with the capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service. The service context manager 835 may be configured as or otherwise support a unit for receiving a second control signaling indicating a first capability service context based on the UE certificate.

[0167] In some examples, the capability service may be configured to provide information related to the capabilities of the UE to one or more core network services provided by a service-based network that are different from the capability service. In some examples, the capability indication manager 840 may be configured as or otherwise support a unit for transmitting a capability indication with the capability service, the capability indication providing one or more UE capabilities associated with at least a first service of one or more services provided by the service-based network. In some examples, the service context manager 835 may be configured as or otherwise support a unit for receiving a third control signaling, the third control signaling indicating a first service context for communicating with the first service based on the capability indication. In some examples, the first service is a radio access network service, a service associated with a distributed unit, a core network service, or a UE service.

[0168] In some examples, capability indication manager 840 may be configured or otherwise support means for receiving capability requests from capability services. In some examples, capability indication manager 840 may be configured or otherwise support means for sending capability responses to capability services via distributed units in response to capability requests.

[0169] In some examples, the capability update manager 845 can be configured as or otherwise support means for communicating a capability update with a capability service, the capability update being based on one or more changed UE capabilities associated with one or more services provided by the service-based network. In some examples, the capability update indicates a duration for the one or more changed UE capabilities.

[0170] In some examples, the capability indication manager 840 can be configured to or otherwise support a unit for transmitting a capability indication with a capability service, the capability indication being used to indicate one or more supported combinations of component carriers, one or more frequency bands for communication between the UE and the distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof. In some examples, the capability indication is used to indicate one or more combinations of compatible service capabilities and access stratum capabilities.

[0171] In some examples, the capability service manager 830 can be configured to or otherwise support a unit for receiving a first capability definition associated with a first service, the first capability definition being defined by the first service and being independent of one or more other capabilities associated with one or more services other than the first service, and wherein the one or more UE capabilities associated with the first service are based on the first capability definition. In some examples, the one or more UE capabilities associated with at least the first service are based on one or more frequency bands used for communication with the distributed unit.

[0172] Fig. 9 A diagram of a system 900 including a device 905 supporting techniques for capability indication for multiple services 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 thereof. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. 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, electrically) via one or more buses (e.g., a bus 945).

[0173] 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 , 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.

[0174] 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 can simultaneously send or receive multiple wireless transmissions. The transceiver 915 can communicate bidirectionally via one or more antennas 925, wired or wireless links as described herein. For example, the transceiver 915 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 925 for transmission, and demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 can be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

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

[0176] 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 cases, 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) so that the device 905 performs various functions (e.g., functions or tasks that support technology for capability indications for multiple services 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 various functions described herein.

[0177] According to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. For example, the communication manager 920 may be configured to or otherwise support a unit for receiving first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that the capability service is provided by a service-based network configured to interface with the UE via the distributed unit. The communication manager 920 may be configured to or otherwise support a unit for transmitting a capability service establishment request with the capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service. The communication manager 920 may be configured to or otherwise support a unit for receiving a second control signaling indicating a first capability service context based on the UE certificate.

[0178] 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 connections with core network services provided by a service-based network such as within a 6G system (e.g., subscribe to core network services) based on UE capabilities. In particular, the techniques described herein can enable the UE 115 to obtain the service context of the capability service and provide the UE capabilities to the capability service. The capability service can provide UE capabilities to other entities and services. By enabling the UE 115 capability indication via the capability service, various aspects of the present disclosure can enable the UE 115 to establish connections with various core network services that can be provided by different operators or entities with efficiency and relatively low overhead. 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 the corresponding UE 115 and services, thereby improving the customization and overall user experience at the UE 115. In addition, the techniques described herein can enable the 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 the UE 115.

[0179] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or in cooperation with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may 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 techniques for capability indication for multiple services in a service-based wireless system as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0180] Fig.10 A block diagram 1000 of a device 1005 supporting techniques for capability indication for multiple services 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 105 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 communicate with each other (e.g., via one or more buses).

[0181] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information such as user data associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), 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.

[0182] The transmitter 1015 may provide a means for outputting (e.g., sending, providing, transmitting, emitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information such as user data associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), 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.

[0183] 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 the techniques for capability indication for multiple services 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.

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

[0185] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations 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 functions of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

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

[0187] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a distributed unit. For example, the communication manager 1020 may be configured to or otherwise support a unit for transmitting first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit, and the capability service is configured to provide information related to the capabilities of the UE to one or more services provided by the service-based network that are different from the capability service. The communication manager 1020 may be configured to or otherwise support a unit for transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE certificates for the capability service. The communication manager 1020 may be configured to or otherwise support a unit for sending a second control signaling indicating a first capability service context to the UE.

[0188] Additionally or alternatively, according to examples as disclosed herein, the communications manager 1020 may support wireless communications at a capability service provided by a service-based network. For example, the communications manager 1020 may be configured to or otherwise support a unit for transmitting first control information with the UE, the first control information indicating that the capability service is provided by the service-based network. The communications manager 1020 may be configured to or otherwise support a unit for obtaining a capability indication message, the capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by the service-based network. The communications manager 1020 may be configured to or otherwise support a unit for providing information related to the capabilities of the UE to at least the first service.

[0189] 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 such as within a 6G system based on UE capabilities (e.g., subscribe to a core network service). In particular, the techniques described herein can enable the UE 115 to obtain a service context for a capability service and provide UE capabilities to the capability service. The capability service can provide UE capabilities to other entities and services. By enabling UE 115 capability indications via capability services, various aspects of the present disclosure can enable the UE 115 to establish connections with various core network services that can be provided by different operators or entities with efficiency and relatively low overhead. Therefore, the techniques described herein can enable the UE 115 to subscribe to different core network services on a per-order basis according to the needs or requirements of the corresponding UE 115 and services, thereby improving the customization and overall user experience at the UE 115. Furthermore, the techniques described herein may enable the 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 the UE 115 .

[0190] Fig.11 A block diagram 1100 of a device 1105 supporting techniques for capability indication for multiple services 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 communicate with each other (e.g., via one or more buses).

[0191] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information such as user data associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), 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 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.

[0192] The transmitter 1115 may provide a means for outputting (e.g., sending, providing, transmitting, emitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information such as user data associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), 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 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 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0193] The device 1105 or its various components may be examples of units for performing various aspects of the technology for capability indication of multiple services in a service-based wireless system as described herein. For example, the communication manager 1120 may include a control signaling manager 1125, a capability service manager 1130, a service context manager 1135, a capability indication manager 1140, 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 perform various operations (e.g., receive, obtain, monitor, output, send) using the receiver 1110, the transmitter 1115, or both or in other ways in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communication manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or integrate with the receiver 1110, the transmitter 1115, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0194] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at the distributed unit. The control signaling manager 1125 may be configured as or otherwise support a unit for transmitting first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that the capability service is provided by a service-based network configured to interface with the UE via the distributed unit. The capability service manager 1130 may be configured as or otherwise support a unit for transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE certificates for the capability service. The service context manager 1135 may be configured as or otherwise support a unit for sending a second control signaling indicating a first capability service context to the UE.

[0195] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1120 may support wireless communications at a capability service provided by a service-based network. The control signaling manager 1125 may be configured as or otherwise support a unit for transmitting first control information with the UE, the first control information indicating that the capability service is provided by the service-based network. The capability indication manager 1140 may be configured as or otherwise support a unit for obtaining a capability indication message, the capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by the service-based network. The capability service manager 1130 may be configured as or otherwise support a unit for providing information related to the capabilities of the UE to at least the first service.

[0196] Fig.12 A block diagram 1200 of a communication manager 1220 supporting techniques for capability indication for multiple services 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 techniques for capability indication for multiple services in a service-based wireless system as described herein. For example, the communication manager 1220 may include a control signaling manager 1225, a capability service manager 1230, a service context manager 1235, a capability indication manager 1240, a wireless connection manager 1245, a capability subscription manager 1250, a capability update manager 1255, a capability definition manager 1260, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses), which can include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0197] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at the distributed unit. The control signaling manager 1225 may be configured as or otherwise support a unit for transmitting first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that the capability service is provided by a service-based network configured to interface with the UE via the distributed unit. The capability service manager 1230 may be configured as or otherwise support a unit for transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE certificates for the capability service. The service context manager 1235 may be configured as or otherwise support a unit for sending a second control signaling indicating a first capability service context to the UE.

[0198] In some examples, the capability service can be configured to provide information related to the capabilities of the UE to one or more services provided by the service-based network other than the capability service. In some examples, the capability service manager 1230 can be configured as or otherwise support means for communicating with the capability service to obtain at least a first UE capability for transmission via a wireless connection between the UE and the distributed unit. In some examples, the wireless connection manager 1245 can be configured as or otherwise support means for sending one or more communication parameters for a wireless connection between the UE and the distributed unit to the UE, the one or more communication parameters being based on the first UE capability.

[0199] In some examples, capability update manager 1255 can be configured as or otherwise support means for obtaining a capability update from a capability service, the capability update being based at least in part on one or more changed UE capabilities communicated to the capability service. In some examples, wireless connection manager 1245 can be configured as or otherwise support means for changing one or more communication parameters for a wireless connection between the UE and the distributed unit based on the capability update. In some examples, the capability update indicates a duration for the one or more changed UE capabilities.

[0200] In some examples, the capability subscription manager 1250 may be configured as or otherwise support a unit for transmitting a capability subscription indication to a capability service, and wherein the first UE capability is provided by the capability service in response to the capability subscription indication sent by the distributed unit to the capability service. In some examples, the capability service indicates one or more supported combinations of frequency bands for communication between the UE and the distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof. In some examples, the capability service indicates one or more combinations of compatible service capabilities and access stratum capabilities.

[0201] In some examples, the wireless connection manager 1245 can be configured as or otherwise support a unit for providing one or more frequency bands for wireless connections between the UE and the distributed unit to the capability service, and wherein the UE capabilities are based on the one or more frequency bands.

[0202] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communications at a capability service provided by a service-based network. In some examples, the control signaling manager 1225 may be configured as or otherwise support a unit for transmitting first control information to the UE, the first control information indicating that the capability service is provided by the service-based network. The capability indication manager 1240 may be configured as or otherwise support a unit for obtaining a capability indication message, the capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by the service-based network. In some examples, the capability service manager 1230 may be configured as or otherwise support a unit for providing information related to the capabilities of the UE to at least the first service. In some examples, the communication and obtaining are performed via a distributed unit.

[0203] In some examples, capability subscription manager 1250 may be configured as or otherwise support means for obtaining a capability subscription indication from at least a first service, and wherein information related to the capabilities of the UE is provided in response to the capability subscription indication.

[0204] In some examples, capability update manager 1255 can be configured as or otherwise support means for obtaining a capability update from the UE, the capability update being based at least in part on one or more changed UE capabilities relative to a previous capability indication of the UE. In some examples, capability update manager 1255 can be configured as or otherwise support means for providing updated information related to the capabilities of the UE to at least a first service in response to the capability update from the UE. In some examples, the capability update indicates a duration for the one or more changed UE capabilities.

[0205] In some examples, the capability indication message indicates one or more supported combinations of frequency bands for communication between the UE and the distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof. In some examples, the capability indication message indicates one or more combinations of compatible service capabilities and access stratum capabilities.

[0206] In some examples, the capability definition manager 1260 can be configured as or otherwise support a unit for obtaining a first capability definition associated with a first service, the first capability definition being independent of one or more other capabilities associated with one or more other services different from the first service, and wherein the one or more UE capabilities associated with the first service are based on the first capability definition.

[0207] In some examples, capability service manager 1230 may be configured as or otherwise support means for obtaining, from a distributed unit, an indication of one or more frequency bands for a wireless connection between the UE and the distributed unit. In some examples, capability service manager 1230 may be configured as or otherwise support means for filtering one or more UE capabilities based on the one or more frequency bands to identify at least a first UE capability associated with the one or more frequency bands. In some examples, capability service manager 1230 may be configured as or otherwise support means for providing the first UE capability to the distributed unit.

[0208] Fig.13 A diagram of a system 1300 including a device 1305 supporting technology for capability indication for multiple services 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 thereof. 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).

[0209] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. 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 that are capable of sending or receiving wireless transmissions (e.g., concurrently). 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 1315, 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 1315 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 the transceiver 1310 and one or more antennas 1315 or a wired interface (where applicable) may be an example of a transmitter 1015, a transmitter 1115, a receiver 1010, a receiver 1110, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, mid-range communication link, fronthaul communication link 168).

[0210] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330, which includes instructions that, when executed by processor 1335, cause 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, in addition to this, memory 1325 may also contain BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0211] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 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) to cause the device 1305 to perform various functions (e.g., functions or tasks that support technology for capability indications for multiple services 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 the various functions described herein. Processor 1335 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that can host functions (e.g., by executing code 1330) to perform functions of 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., within 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 the inputs to produce a set of outputs (which can be delivered 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, such as processor 1335, or transceiver 1310, or communication manager 1320, or other components or combinations of components of device 1305. The processing system of device 1305 can be docked with other components of device 1305, and can process information (such as input or signal) received from other components or output information to other components. For example, the chip or modem of device 1305 may include a processing system and an interface to output information, or obtain information, or both. 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 the processing system of the chip or modem and a transmitter, so that device 1305 can send information output from the chip or modem. In some implementations, the second interface may refer to an interface between the processing system of the chip or modem and a receiver, so that 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.

[0212] In some examples, bus 1340 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 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 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

[0213] In some examples, the communication manager 1320 can manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 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 the UE 115 in cooperation with the other network entities 105. In some examples, the communication manager 1320 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0214] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at the distributed unit. For example, the communication manager 1320 may be configured to or otherwise support a unit for transmitting first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that the capability service is provided by a service-based network configured to interface with the UE via the distributed unit. The communication manager 1320 may be configured to or otherwise support a unit for transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE certificates for the capability service. The communication manager 1320 may be configured to or otherwise support a unit for sending a second control signaling indicating a first capability service context to the UE.

[0215] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 may support wireless communications at a capability service provided by a service-based network. For example, the communication manager 1320 may be configured to or otherwise support a unit for transmitting first control information with the UE, the first control information indicating that the capability service is provided by the service-based network. The communication manager 1320 may be configured to or otherwise support a unit for obtaining a capability indication message, the capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by the service-based network. The communication manager 1320 may be configured to or otherwise support a unit for providing information related to the capabilities of the UE to at least the first service.

[0216] 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 connections with core network services provided by a service-based network such as within a 6G system (e.g., subscribe to core network services) based on UE capabilities. In particular, the techniques described herein can enable the UE 115 to obtain the service context of the capability service and provide the UE capabilities to the capability service. The capability service can provide UE capabilities to other entities and services. By enabling the UE 115 capability indication via the capability service, various aspects of the present disclosure can enable the UE 115 to establish connections with various core network services that can be provided by different operators or entities with efficiency and relatively low overhead. 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 the corresponding UE 115 and the service, thereby improving the customization and overall user experience at the UE 115. In addition, the techniques described herein can enable the 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 the UE 115.

[0217] In some examples, the communication manager 1320 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or in cooperation with the transceiver 1310, one or more antennas 1315 (e.g., when applicable), 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 can 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 capability indication for multiple services in a service-based wireless system as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0218] Fig.14 A flow chart illustrating a method 1400 for supporting a technique for capability indication for multiple services 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 may be performed. In some examples, the UE may execute an instruction set to control the functional units 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.

[0219] At 1405, the method may include: receiving first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit. The operations of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described with reference to Figure 8 The capability service may be configured to provide information related to the capabilities of the UE to one or more core network services provided by the service-based network other than the capability service.

[0220] At 1410, the method may include: transmitting a capability service establishment request with a capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service. 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 as described with reference to Figure 8 The described capabilities are performed by the service manager 830.

[0221] At 1415, the method may include receiving a second control signaling indicating a first capability service context based on the UE certificate. The operations of 1415 may be performed according to examples 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.

[0222] Fig.15 A flow chart illustrating a method 1500 for supporting a technique for capability indication for multiple services 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 UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described with reference to Figures 1 to 9 The UE 115 described herein may be performed. In some examples, the UE may execute an instruction set to control the functional units 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.

[0223] At 1505, the method may include: receiving first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit, and the capability service is configured to provide information related to the capability of the UE to one or more core network services provided by the service-based network that are different from the capability service. The operation of 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1505 may be performed as described with reference to Figure 8 The control signaling manager 825 described above is executed.

[0224] At 1510, the method may include: transmitting a capability service establishment request with a capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described with reference to Figure 8 The described capabilities are performed by the service manager 830.

[0225] At 1515, the method may include receiving a second control signaling indicating a first capability service context based on the UE certificate. 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 Figure 8 The service context manager 835 described above is executed.

[0226] At 1520, the method may include: transmitting a capability indication with a capability service, the capability indication providing one or more UE capabilities associated with at least a first service of one or more services provided by the service-based network. 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 Figure 8 The described capabilities instruct manager 840 to perform.

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

[0228] Fig.16 A flow chart illustrating a method 1600 for supporting a technique for capability indication for multiple services in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described with reference to Figures 1 to 9 The UE 115 described herein may be performed. In some examples, the UE may execute an instruction set to control the functional units 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.

[0229] At 1605, the method may include: receiving first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit, and the capability service is configured to provide information related to the capability of the UE to one or more core network services provided by the service-based network that are different from the capability service. The operation of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1605 may be performed as described with reference to Figure 8 The control signaling manager 825 described above is executed.

[0230] At 1610, the method may include: transmitting a capability service establishment request with a capability service based on the first control information, the capability service establishment request providing one or more UE certificates for the capability service. 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 Figure 8 The described capabilities are performed by the service manager 830.

[0231] At 1615, the method may include receiving a second control signaling indicating a first capability service context based on the UE certificate. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described with reference to Figure 8 The service context manager 835 described above is executed.

[0232] At 1620, the method may include receiving a capability request from a capability service. The operations of 1620 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1620 may be described by referring to Figure 8 The described capabilities instruct manager 840 to perform.

[0233] At 1625, the method may include: in response to the capability request, sending a capability response to the capability service via the distributed unit. The operations of 1625 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1625 may be described by referring to Figure 8 The described capabilities instruct manager 840 to perform.

[0234] At 1630, the method may include: communicating a capability update with the capability service, the capability update being based at least in part on one or more changed UE capabilities associated with one or more services provided by the service-based network. The operations of 1630 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1630 may be performed as described with reference to Figure 8 The described capability update manager 845 is executed.

[0235] Fig.17 A flow chart illustrating a method 1700 for supporting a technique for capability indication for multiple services 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 an instruction set to control the functional units 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.

[0236] At 1705, the method may include transmitting, via a wireless connection between the UE and the distributed unit, first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Fig.12The capability service may be configured to provide information related to the UE's capabilities to one or more core network services provided by the service-based network that are different from the capability service.

[0237] At 1710, the method may include transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE credentials for the capability service. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Fig.12 The described capabilities are performed by the service manager 1230.

[0238] At 1715, the method may include: sending a second control signaling indicating the first capability service context to the UE. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Fig.12 The service context manager 1235 described is executed.

[0239] Fig.18 A flow chart illustrating a method 1800 for supporting a technique for capability indication for multiple services in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 10 to 13. In some examples, the network entity may execute an instruction set to control the functional units 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.

[0240] At 1805, the method may include: transmitting first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit, and the capability service is configured to provide information related to the capability of the UE to one or more core network services provided by the service-based network that are different from the capability service. The operation of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1805 may be performed as described with reference to Fig.12 The control signaling manager 1225 described above is executed.

[0241] At 1810, the method may include transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE credentials for the capability service. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described with reference to Fig.12 The described capabilities are performed by the service manager 1230.

[0242] At 1815, the method may include: sending a second control signaling indicating the first capability service context to the UE. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Fig.12 The service context manager 1235 described is executed.

[0243] At 1820, the method may include communicating with a capability service to obtain at least a first UE capability for transmission via a wireless connection between the UE and the distributed unit. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Fig.12 The described capabilities are performed by the service manager 1230.

[0244] At 1825, the method may include: sending one or more communication parameters for a wireless connection between the UE and the distributed unit to the UE, the one or more communication parameters being based on the first UE capabilities. The operations of 1825 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1825 may be performed as described with reference to Fig.12 The wireless connection manager 1245 described above is executed.

[0245] At 1830, the method may include obtaining a capability update from a capability service, the capability update being based at least in part on one or more changed UE capabilities transmitted to the capability service. The operations of 1830 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1830 may be performed as described with reference to Fig.12 The described capability update manager 1255 is executed.

[0246] At 1835, the method may include: changing one or more communication parameters for a wireless connection between the UE and the distributed unit based on the capability update. The operations of 1835 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1835 may be performed as described with reference to Fig.12 The wireless connection manager 1245 described above is executed.

[0247] Fig.19A flow chart illustrating a method 1900 for supporting a technique for capability indication for multiple services in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1900 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 an instruction set to control the functional units 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.

[0248] At 1905, the method may include: transmitting first control information via a wireless connection between the UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit, and the capability service is configured to provide information related to the capability of the UE to one or more core network services provided by the service-based network that are different from the capability service. The operation of 1905 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1905 may be performed as described with reference to Fig.12 The control signaling manager 1225 described above is executed.

[0249] At 1910, the method may include transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE credentials for the capability service. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described with reference to Fig.12 The described capabilities are performed by the service manager 1230.

[0250] At 1915, the method may include: sending a second control signaling indicating the first capability service context to the UE. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described with reference to Fig.12 The service context manager 1235 described is executed.

[0251] At 1920, the method may include transmitting a capability subscription indication to a capability service, and wherein the first UE capability is provided by the capability service in response to the capability subscription indication sent by the distributed unit to the capability service. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described with reference to Fig.12 The described capability subscription manager 1250 is executed.

[0252] Fig. 20A flow chart illustrating a method 2000 for supporting a technique for capability indication for multiple services in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2000 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 an instruction set to control the functional units 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.

[0253] At 2005, the method may include: transmitting first control information with the UE, the first control information indicating that the capability service is provided by the service-based network. The operations of 2005 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described with reference to Fig.12 The control signaling manager 1225 described above is executed.

[0254] At 2010, the method may include obtaining a capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by a service-based network. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described with reference to Fig.12 The described capabilities instruct manager 1240 to execute.

[0255] At 2015, the method may include: providing information related to the capabilities of the UE to at least the first service. The operations of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed as described with reference to Fig.12 The described capabilities are performed by the service manager 1230.

[0256] Fig.21 A flow chart illustrating a method 2100 for supporting a technique for capability indication for multiple services in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2100 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 an instruction set to control the functional units 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.

[0257] At 2105, the method may include: transmitting first control information with the UE, the first control information indicating that the capability service is provided by the service-based network. The operations of 2105 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described with reference to Fig.12 The control signaling manager 1225 described above is executed.

[0258] At 2110, the method may include obtaining a capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by a service-based network. The operations of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described with reference to Fig.12 The described capabilities instruct manager 1240 to execute.

[0259] At 2115, the method may include providing information related to the capabilities of the UE to at least the first service. The operations of 2115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed as described with reference to Fig.12 The described capabilities are performed by the service manager 1230.

[0260] At 2120, the method may include obtaining a capability subscription indication from at least the first service, and wherein the information related to the capabilities of the UE is provided in response to the capability subscription indication. The operations of 2120 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed as described with reference to Fig.12 The described capability subscription manager 1250 is executed.

[0261] At 2125, the method may include obtaining a capability update from the UE, the capability update being based at least in part on one or more changed UE capabilities relative to a previous capability indication of the UE. The operations of 2125 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2125 may be performed as described with reference to Fig.12 The described capability update manager 1255 is executed.

[0262] At 2130, the method may include: in response to the capability update from the UE, providing updated information related to the capabilities of the UE to at least the first service. The operations of 2130 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2130 may be performed as described with reference to Fig.12 The described capability update manager 1255 is executed.

[0263] Fig. 22A flow chart illustrating a method 2200 for supporting techniques for capability indication for multiple services in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 2200 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2200 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 an instruction set to control the functional units 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.

[0264] At 2205, the method may include obtaining a first capability definition associated with a first service, the first capability definition being independent of one or more other capabilities associated with one or more other services different from the first service, and wherein one or more UE capabilities associated with the first service are based on the first capability definition. The operations of 2205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2205 may be performed as described with reference to Fig.12 The capability definition manager 1260 described is executed.

[0265] At 2210, the method may include: transmitting first control information with the UE, the first control information indicating that the capability service is provided by the service-based network. The operations of 2210 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2210 may be performed as described in reference to Fig.12 The control signaling manager 1225 described above is executed.

[0266] At 2215, the method may include obtaining a capability indication message indicating one or more UE capabilities associated with at least a first service in a set of multiple services provided by the service-based network. The operations of 2215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2215 may be performed as described with reference to Fig.12 The described capabilities instruct manager 1240 to execute.

[0267] At 2220, the method may include providing information related to the capabilities of the UE to at least the first service. The operations of 2220 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2220 may be performed as described with reference to Fig.12 The described capabilities are performed by the service manager 1230.

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

[0269] Aspect 1: A method for wireless communication at a UE, comprising: receiving first control information via a wireless connection between the UE and a distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmitting a capability service establishment request with the capability service based at least in part on the first control information, the capability service establishment request providing one or more UE certificates for the capability service; and receiving second control signaling indicating a first capability service context based at least in part on the UE certificate.

[0270] Aspect 2: The method according to aspect 1 also includes: transmitting a capability indication with the capability service, the capability indication providing one or more UE capabilities associated with at least a first service of one or more services provided by the service-based network.

[0271] Aspect 3: The method according to aspect 2 further includes: receiving third control signaling, the third control signaling indicating a first service context for communicating with the first service based at least in part on the capability indication.

[0272] Aspect 4: The method according to any one of aspects 2 to 3, wherein the first service is a radio access network service, a service associated with the distributed unit, a core network service, or a UE service.

[0273] Aspect 5: The method according to any one of Aspects 1 to 4, further comprising: receiving a capability request from the capability service; and sending a capability response to the capability service via the distributed unit in response to the capability request.

[0274] Aspect 6: The method according to aspect 5 further includes: transmitting a capability update with the capability service, the capability update being based at least in part on one or more changed UE capabilities associated with one or more services provided by the service-based network.

[0275] Aspect 7: The method according to aspect 6, wherein the capability update indicates a duration for the one or more changed UE capabilities.

[0276] Aspect 8: The method according to any one of Aspects 1 to 7 also includes: transmitting a capability indication together with the capability service, wherein the capability indication is used to indicate one or more supported combinations of component carriers, one or more frequency bands used for communication between the UE and the distributed unit, one or more manufacturer-related capabilities of the UE, one or more access layer capabilities of the UE, one or more service capabilities of the UE, or any combination thereof.

[0277] Aspect 9: The method according to aspect 8, wherein the capability indication is used to indicate one or more combinations of compatible service capabilities and access layer capabilities.

[0278] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: receiving a first capability definition associated with a first service, the first capability definition being defined by the first service and being independent of one or more other capabilities associated with one or more services other than the first service, and wherein the one or more UE capabilities associated with the first service are at least partially based on the first capability definition.

[0279] Aspect 11: The method according to any one of aspects 1 to 10, wherein one or more UE capabilities associated with at least the first service are based at least in part on one or more frequency bands used for communication with the distributed unit.

[0280] Aspect 12: A method for wireless communication at a distributed unit, comprising: transmitting first control information via a wireless connection between a UE and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE certificates for the capability service; and sending a second control signaling indicating a first capability service context to the UE.

[0281] Aspect 13: The method according to Aspect 12 also includes: communicating with the capability service to obtain at least a first UE capability for transmission via a wireless connection between the UE and the distributed unit; and sending one or more communication parameters for the wireless connection between the UE and the distributed unit to the UE, wherein the one or more communication parameters are at least partially based on the first UE capability.

[0282] Aspect 14: The method according to Aspect 13 also includes: obtaining a capability update from the capability service, the capability update being at least partially based on one or more changed UE capabilities transmitted to the capability service; and changing the one or more communication parameters used for the wireless connection between the UE and the distributed unit based at least partially on the capability update.

[0283] Aspect 15: The method according to aspect 14, wherein the capability update indicates a duration for the one or more changed UE capabilities.

[0284] Aspect 16: The method according to any one of Aspects 12 to 15 further includes: transmitting a capability subscription indication to the capability service, and wherein the first UE capability is provided by the capability service in response to the capability subscription indication sent by the distributed unit to the capability service.

[0285] Aspect 17: A method according to any one of Aspects 12 to 16, wherein the capability service indicates one or more supported combinations of frequency bands used for communication between the UE and the distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof.

[0286] Aspect 18: The method according to any one of aspects 12 to 17, wherein the capability service indicates one or more combinations of compatible service capabilities and access layer capabilities.

[0287] Aspect 19: The method according to any one of Aspects 12 to 18 further includes: providing one or more frequency bands for the wireless connection between the UE and the distributed unit to the capability service, and wherein the UE capabilities are at least partially based on the one or more frequency bands.

[0288] Aspect 20: A method for wireless communication at a capability service provided by a service-based network, comprising: transmitting first control information to a UE, the first control information indicating that the capability service is provided by the service-based network; obtaining a capability indication message, the capability indication message indicating one or more UE capabilities associated with at least a first service among multiple services provided by the service-based network; and providing information related to the capabilities of the UE to at least the first service.

[0289] Aspect 21: The method according to aspect 20, wherein the transmitting and obtaining are performed via a distributed unit.

[0290] Aspect 22: The method according to any one of Aspects 20 to 21 further includes: obtaining a capability subscription indication from at least the first service, and wherein the information related to the capability of the UE is provided in response to the capability subscription indication.

[0291] Aspect 23: The method according to any one of Aspects 20 to 22 further includes: obtaining a capability update from the UE, the capability update being at least partially based on one or more changed UE capabilities relative to previous capability indications of the UE; and in response to the capability update from the UE, providing updated information related to the capabilities of the UE to at least the first service.

[0292] Aspect 24: The method according to aspect 23, wherein the capability update indicates a duration for one or more changed UE capabilities.

[0293] Aspect 25: A method according to any one of Aspects 20 to 24, wherein the capability indication message indicates one or more supported combinations of frequency bands for communication between the UE and a distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof.

[0294] Aspect 26: The method according to any one of Aspects 20 to 25, wherein the capability indication message indicates one or more combinations of compatible service capabilities and access layer capabilities.

[0295] Aspect 27: The method according to any one of Aspects 20 to 26 further includes: obtaining a first capability definition associated with a first service, the first capability definition being independent of one or more other capabilities associated with one or more other services different from the first service, and wherein the one or more UE capabilities associated with the first service are at least partially based on the first capability definition.

[0296] Aspect 28: The method according to any one of Aspects 20 to 27 further includes: obtaining, from a distributed unit, an indication of one or more frequency bands used for a wireless connection between the UE and the distributed unit; filtering the one or more UE capabilities based at least in part on the one or more frequency bands to identify at least a first UE capability associated with the one or more frequency bands; and providing the first UE capability to the distributed unit.

[0297] Aspect 29: 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 a method according to any one of Aspects 1 to 11.

[0298] Aspect 30: 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 11.

[0299] Aspect 31: 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 11.

[0300] Aspect 32: An apparatus for wireless communication at a distributed unit, 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 12 to 19.

[0301] Aspect 33: An apparatus for wireless communication at a distributed unit, comprising at least one unit for performing the method according to any one of aspects 12 to 19.

[0302] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a distributed unit, the code comprising instructions executable by a processor to perform the method according to any one of aspects 12 to 19.

[0303] Aspect 35: An apparatus for wireless communication at a capability service provided by a service-based network, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 20 to 28.

[0304] Aspect 36: An apparatus for wireless communication at a capability service provided by a service-based network, comprising at least one means for performing the method according to any one of aspects 20 to 28.

[0305] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication at a capability service provided by a service-based network, the code comprising instructions executable by a processor to perform the method according to any one of aspects 20 to 28.

[0306] 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 other implementations are possible. Furthermore, aspects from two or more methods may be combined.

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

[0308] 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 description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

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

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

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

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

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

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

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

[0316] To enable those skilled in the art to implement or use the present disclosure, the description herein is provided. It will be apparent to those skilled in the art that various modifications to the present disclosure will be apparent, 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: receiving, via a wireless connection between the UE and a distributed unit, first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmitting, based at least in part on the first control information, a capability service setup request with the capability service, the capability service setup request providing one or more UE credentials for the capability service; as well as Second control signaling is received indicating a first capability service context based at least in part on the UE credentials.

2. The method according to claim 1, further comprising: A capability indication is communicated with the capability service, the capability indication providing one or more UE capabilities associated with at least a first service of one or more services provided by the service-based network.

3. The method according to claim 2, further comprising: Third control signaling is received, the third control signaling indicating a first service context for communicating with the first service based at least in part on the capability indication.

4. The method according to claim 2, wherein: The first service is a radio access network service, a service associated with the distributed unit, a core network service, or a UE service.

5. The method according to claim 1, further comprising: receiving a capability request from the capability service; as well as In response to the capability request, a capability response is sent to the capability service via the distributed unit.

6. The method according to claim 5, further comprising: A capability update is communicated with the capability service, the capability update being based at least in part on one or more changed UE capabilities associated with one or more services provided by the service-based network.

7. The method according to claim 6, wherein: The capability update indicates a duration for the one or more changed UE capabilities.

8. The method according to claim 1, further comprising: A capability indication is transmitted together with the capability service, wherein the capability indication is used to indicate one or more supported combinations of component carriers, one or more frequency bands used for communication between the UE and the distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof.

9. The method according to claim 8, wherein: The capability indication is used to indicate one or more combinations of compatible service capabilities and access layer capabilities.

10. The method according to claim 1, further comprising: Receive a first capability definition associated with a first service, wherein the first capability definition is defined by the first service and is independent of one or more other capabilities associated with one or more services other than the first service, and wherein the one or more UE capabilities associated with the first service are at least partially based on the first capability definition.

11. The method according to claim 1, wherein: One or more UE capabilities associated with at least a first service are based at least in part on one or more frequency bands used for communications with the distributed unit.

12. A method for wireless communication at a distributed unit, comprising: transmitting first control information via a wireless connection between a user equipment (UE) and the distributed unit, the first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit; transmitting a capability service establishment request between the UE and the capability service, the capability service establishment request providing one or more UE credentials for the capability service; as well as Sending second control signaling indicating a first capability service context to the UE.

13. The method according to claim 12, further comprising: communicating with the capability service to obtain at least first UE capabilities for transmission via a wireless connection between the UE and the distributed unit; as well as One or more communication parameters for the wireless connection between the UE and the distributed unit are sent to the UE, the one or more communication parameters being based at least in part on the first UE capabilities.

14. The method according to claim 13, further comprising: obtaining a capability update from the capability service, the capability update being based at least in part on one or more changed UE capabilities communicated to the capability service; as well as The one or more communication parameters for the wireless connection between the UE and the distributed unit are changed based at least in part on the capability update.

15. The method according to claim 14, wherein: The capability update indicates a duration for the one or more changed UE capabilities.

16. The method according to claim 12, further comprising: A capability subscription indication is transmitted to the capability service, and wherein the first UE capability is provided by the capability service in response to the capability subscription indication sent by the distributed unit to the capability service.

17. The method according to claim 12, wherein: The capability service indicates one or more supported combinations of frequency bands for communication between the UE and the distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof.

18. The method according to claim 12, wherein: The capability service indicates one or more combinations of compatible service capabilities and access layer capabilities.

19. The method according to claim 12, further comprising: One or more frequency bands for the wireless connection between the UE and the distributed unit are provided to the capability service, and wherein UE capabilities are based at least in part on the one or more frequency bands.

20. A method for wireless communication at a capability service provided by a service-based network, comprising: transmitting first control information to a user equipment (UE), the first control information indicating that the capability service is provided by the service-based network; obtaining a capability indication message indicating one or more UE capabilities associated with at least a first service of a plurality of services provided by the service-based network; as well as Information related to the capabilities of the UE is provided to at least the first service.

21. The method according to claim 20, wherein: The transmitting and obtaining are performed via distributed units.

22. The method according to claim 20, further comprising: A capability subscription indication is obtained from at least the first service, and wherein the information related to the capabilities of the UE is provided in response to the capability subscription indication.

23. The method according to claim 20, further comprising: obtaining a capability update from the UE, the capability update being based at least in part on one or more changed UE capabilities relative to a previous capability indication of the UE; as well as In response to the capability update from the UE, updated information related to the capabilities of the UE is provided to at least the first service.

24. The method according to claim 23, wherein: The capability update indicates a duration for one or more changed UE capabilities.

25. The method according to claim 20, wherein: The capability indication message indicates one or more supported combinations of frequency bands for communication between the UE and a distributed unit, one or more manufacturer-related capabilities of the UE, one or more access stratum capabilities of the UE, one or more service capabilities of the UE, or any combination thereof.

26. The method of claim 20, wherein: The capability indication message indicates one or more combinations of compatible service capabilities and access layer capabilities.

27. The method of claim 20, further comprising: Obtain a first capability definition associated with the first service, the first capability definition being independent of one or more other capabilities associated with one or more other services different from the first service, and wherein the one or more UE capabilities associated with the first service are based at least in part on the first capability definition.

28. The method of claim 20, further comprising: obtaining, from a distributed unit, an indication of one or more frequency bands to be used for a wireless connection between the UE and the distributed unit; filtering the one or more UE capabilities based at least in part on the one or more frequency bands to identify at least a first UE capability associated with the one or more frequency bands; as well as The first UE capabilities are provided to the distributed unit.

29. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; as well as Instructions, which are stored in the memory and can be executed by the processor to cause the device to perform the following operations: receiving, via a wireless connection between the UE and a distributed unit, first control information indicating that a capability service is provided by a service-based network configured to interface with the UE via the distributed unit, and the capability service is configured to provide information related to the capability of the UE to one or more core network services provided by the service-based network that are different from the capability service; transmitting, based at least in part on the first control information, a capability service setup request with the capability service, the capability service setup request providing one or more UE credentials for the capability service; as well as Second control signaling is received indicating a first capability service context based at least in part on the UE credentials.

30. The device according to claim 29, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: communicating with the capability service a capability indication providing one or more UE capabilities associated with at least a first service of the one or more services provided by the service-based network; as well as Third control signaling is received, the third control signaling indicating a first service context for communicating with the first service based at least in part on the capability indication.

Images