Addressability in Service-Based Wireless Systems

Abstract

A method, system, and device for wireless communications are described. An end-to-end routing layer may address packets between a user equipment (UE) and a core network service provided by a service-based network for each core network service. The UE may communicate with the core network service directly (e.g., based on a network address associated with the core network service) or indirectly (e.g., through a proxy service). The UE may select access stratum (AS) resources for transmitting uplink packet data units based on a target core network service. The UE may receive control signaling from a distributed unit, a system information block (SIB), or point-to-point signaling from the core network service indicating specific AS resources for each core network service. The UE may select a logical channel for transmitting uplink packet data units to a specific core network service based on the AS resources associated with each service.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS)

[0001] This patent application claims priority to U.S. patent application Ser. No. 17 / 948,060 by GRIOT et al., entitled "ADDRESSABILITY IN A SERVICE-BASED WIRELESS SYSTEM," filed Sep. 19, 2022, which is assigned to the assignee of the present specification and is expressly incorporated by reference in its entirety into this specification.

[0002] The following relates to wireless communications, including addressability in service-based wireless systems. [Background technology]

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

[0004] The described technology relates to improved methods, systems, devices, and apparatuses that support addressability in service-based wireless systems. For example, the described technology provides routing of information (e.g., packet data units) between a user equipment (UE) and core network services provided by a service-based network. An end-to-end routing layer may address packets between the UE and multiple core network services for each core network service. The UE may communicate with a core network service directly (e.g., based on a network address associated with the core network service) or indirectly (e.g., by routing communications through a proxy service). In both the direct and indirect cases, the UE may select access stratum (AS) resources (e.g., AS resource blocks) for transmitting uplink packet data units based on the target core network service. For example, the UE may receive control signaling from a distribution unit (DU), a system information block (SIB), or point-to-point signaling from a core network service indicating specific AS resources for each core network service. The UE may also select a logical channel for transmitting uplink packet data units to a particular core network service based on AS resources associated with each core network service.

[0005] A method of wireless communication in a UE is described. The method may include establishing communication with a set of core network services provided by a service-based network configured to interface with a Radio Access Network (RAN) associated with the DU, over a wireless connection between the UE and the DU, wherein each core network service of the set of core network services is associated with a respective addressing scheme, transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service, and transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service.

[0006] An apparatus for wireless communication in 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 establish communication with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, over a wireless connection between the UE and the DU, wherein each core network service of the set of core network services is associated with a respective addressing scheme, transmit a first packet data unit associated with a first core network service of the set of core network services over the wireless connection in accordance with a first addressing scheme associated with the first core network service, and transmit a second packet data unit associated with a second core network service of the set of core network services over the wireless connection in accordance with a second addressing scheme associated with the second core network service.

[0007] Another apparatus for wireless communication in a UE is described. The apparatus may include: means for establishing communication with a set of core network services provided by a service-based network configured to interface with a RAN associated with a DU, over a wireless connection between the UE and the DU, wherein each core network service of the set of core network services is associated with a respective addressing scheme; means for transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service; and means for transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service.

[0008] A non-transitory computer-readable medium storing code for wireless communication in a UE is described. The code may include instructions executable by a processor to establish communication with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, over a wireless connection between the UE and the DU, wherein each core network service of the set of core network services is associated with a respective addressing scheme, transmit a first packet data unit associated with a first core network service of the set of core network services over the wireless connection in accordance with a first addressing scheme associated with the first core network service, and transmit a second packet data unit associated with a second core network service of the set of core network services over the wireless connection in accordance with a second addressing scheme associated with the second core network service.

[0009]

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for determining first routing information associated with a first core network service and second routing information associated with a second core network service, wherein transmitting the first packet data unit according to the first addressing scheme includes adding a first header to the first packet data unit including the first routing information, and transmitting the second packet data unit according to the second addressing scheme includes adding a second header to the second packet data unit including the second routing information.

[0010]

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for determining a first AS resource associated with a first core network service and a second AS resource associated with a second core network service, wherein transmitting a first packet data unit according to a first addressing scheme includes transmitting the first packet data unit using the first AS resource, and transmitting a second packet data unit according to a second addressing scheme includes transmitting the second packet data unit using the second AS resource.

[0011]

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for determining, at the UE, a first logical channel associated with a first AS resource and a second logical channel associated with a second AS resource.

[0012]

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include an operation, feature, means, or instruction for receiving control information from the DU via a wireless connection, the control information indicating the first AS resource and the second AS resource.

[0013]

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving control information from the proxy service via a wireless connection indicating a first service identifier associated with a first core network service and a second service identifier associated with a second core network service, wherein transmitting the first packet data unit according to the first addressing scheme includes transmitting an indication of the first service identifier with the first packet data unit, and transmitting the second packet data unit according to the second addressing scheme includes transmitting an indication of the second service identifier with the second packet data unit.

[0014]

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving, along with control information, an indication of AS resources associated with the proxy service, wherein transmitting the first packet data unit according to the first addressing scheme includes transmitting the first packet data unit using the AS resources, and transmitting the second packet data unit according to the second addressing scheme includes transmitting the second packet data unit using the AS resources.

[0015]

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for determining, at a UE, a logical channel associated with an AS resource.

[0016]

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a third packet data unit via a wireless connection, determining that the third packet data unit may be associated with a first core network service based on first routing information included in a first header of the third packet data unit, and processing the third packet data unit in accordance with a first protocol associated with the first core network service.

[0017]

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving control information from a proxy service via a wireless connection indicating a first service identifier associated with a first core network service; receiving a third packet data unit via the wireless connection; determining that the third packet data unit may be associated with the first core network service based on the first service identifier being included in a first header of the third packet data unit; and processing the third packet data unit in accordance with a first protocol associated with the first core network service.

[0018]

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first core network service may be associated with a first application programming interface, and the second core network service may be associated with a second application programming interface.

[0019]

[0019] In some examples of the methods, devices, and non-transitory computer-readable media described in this specification, the first core network service and the second core network service each include one of a mobility service, a connection state management service, a security service, a paging service, a wireless access service, a data service, a capability management service, a location service, or a messaging service.

[0020] A method of wireless communication in a DU is described, which may include receiving from a UE a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service, and routing the first packet data unit to the first core network service based on the first addressing scheme, receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service, and routing the second packet data unit to the second core network service based on the second addressing scheme.

[0021] An apparatus for wireless communication in a DU is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive from the UE a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service, and route the first packet data unit to the first core network service based on the first addressing scheme, and to receive from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service, and route the second packet data unit to the second core network service based on the second addressing scheme.

[0022] Another apparatus for wireless communication in a DU is described, which may include: means for receiving from a UE a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service, means for routing the first packet data unit to the first core network service based on the first addressing scheme, means for receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service, and means for routing the second packet data unit to the second core network service based on the second addressing scheme.

[0023] A non-transitory computer-readable medium storing code for wireless communication in a DU is described. The code may include instructions executable by a processor to receive from a UE a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service, and route the first packet data unit to the first core network service based on the first addressing scheme, and receive from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service, and route the second packet data unit to the second core network service based on the second addressing scheme.

[0024]

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining, based on first routing information included in a first header of the first packet data unit, that a first core network service may be associated with the first packet data unit, and for determining, based on second routing information included in a second header of the second packet data unit, that a second core network service may be associated with the second packet data unit, wherein routing the first packet data unit to the first core network service based on the first addressing scheme includes routing the first packet data unit based on the first routing information, and routing the second packet data unit to the second core network service based on the second addressing scheme includes routing the second packet data unit based on the second routing information.

[0025]

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for determining that the UE may be authorized to communicate with the first core network service, and routing the first packet data unit to the first core network service may be based on the determination that the UE may be authorized to communicate with the first core network service.

[0026]

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for receiving control information indicating a set of network entities, including the UE, that are authorized to communicate with the first core network service, and the determination that the UE may be authorized to communicate with the first core network service may be based on the control information.

[0027]

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving from the UE a third packet data unit associated with a third core network service of the set of core network services, the third packet data unit being received according to a third addressing scheme associated with the third core network service; determining that the UE is not authorized to communicate with the third core network service; and refraining from routing the third packet data unit to the third core network service based on the determination that the UE is not authorized to communicate with the third core network service.

[0028]

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include an operation, feature, means, or instruction for receiving control information indicating a set of network entities, excluding the UE, that are authorized to communicate with the third core network service, and the determination that the UE is not authorized to communicate with the third core network service is based on the control information.

[0029]

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for receiving a third packet data unit from a first core network service, the third packet data unit including a first header indicating destination routing information, and transmitting the third packet data unit to the UE based on the destination routing information indicating the UE.

[0030]

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described in this specification may further include operations, features, means, or instructions for determining downlink resources for the third packet data unit based on the destination routing information and based on the first header further indicating source routing information, and transmitting the third packet data unit includes transmitting the third packet data unit using the downlink resources.

[0031]

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for routing the first packet data unit to a first core network service based on a first addressing scheme to include routing the first packet data unit to a proxy service, and for routing the second packet data unit to a second core network service based on a second addressing scheme to include routing the second packet data unit to the proxy service or to a second proxy service associated with the second core network service.

[0032]

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first core network service may be associated with a first application programming interface, and the second core network service may be associated with a second application programming interface.

[0033]

[0033] In some examples of the methods, devices, and non-transitory computer-readable media described in this specification, the first core network service and the second core network service each include one of a mobility service, a connection state management service, a security service, a paging service, a wireless access service, a data service, a capability management service, a location service, or a messaging service. [Brief explanation of the drawings]

[0034] [Figure 1] 1 illustrates an example of a wireless communication system that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 2]

[0035] 1 illustrates an example of a wireless communication system that supports addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 3]

[0036] 1 illustrates an example network architecture that supports addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 4]

[0037] 1 illustrates an example signaling diagram for supporting addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 5]

[0038] 1 illustrates an example signaling diagram for supporting addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 6]

[0039] 1 illustrates an example process flow for supporting addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 7]

[0040] 1 illustrates an example process flow for supporting addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 8]

[0041] 1 illustrates a block diagram of a device that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 9]1 illustrates a block diagram of a device that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 10]

[0042] 1 illustrates a block diagram of a communications manager that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 11]

[0043] 1 illustrates a diagram of a system including a device that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 12]

[0044] 1 illustrates a block diagram of a device that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 13] 1 illustrates a block diagram of a device that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 14]

[0045] 1 illustrates a block diagram of a communications manager that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 15]

[0046] 1 illustrates a diagram of a system including a device that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. [Figure 16]

[0047] 1 depicts a flowchart illustrating a method for supporting addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 17] 1 depicts a flowchart illustrating a method for supporting addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 18]1 depicts a flowchart illustrating a method for supporting addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. [Figure 19] 1 depicts a flowchart illustrating a method for supporting addressability in a service-based wireless system, in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0035]

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

[0036]

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

[0037]

[0050] Aspects of the present disclosure relate to routing information between a UE and core network services provided by a service-based network. An end-to-end routing layer may address packets between a UE and multiple core network services for each core network service. A UE may communicate with a core network service directly (e.g., based on a network address associated with the core network service) or indirectly (e.g., by routing communications through a proxy service). In direct communication, for uplink communication, the UE may send a packet data unit including routing information for the core network service to the core network service via a distribution unit (DU). In indirect communication, the UE may send a packet data unit including a service identifier for the core network service to the proxy service via the DU, and the proxy service may route the packet data unit to the core network service based on the service identifier. In both the direct and indirect cases, the UE may select access stratum (AS) resources (e.g., AS resource blocks) for transmitting uplink packet data units based on the target core network service. For example, the UE may receive control signaling from the DU, a system information block (SIB), or point-to-point signaling from the core network service indicating specific AS resources for each core network service. The UE may also select a logical channel for transmitting uplink packet data units to a specific core network service based on the AS resources associated with each core network service.

[0038]

[0051] In the case of direct downlink communication, the DU may route the packet data unit from the core network service to the UE based on the destination address included in the header of the packet data unit and a local UE context (e.g., a UE identifier) ​​created by the DU. In the case of indirect downlink transmission, the DU may receive a downlink packet data unit including the destination address and the service identifier from the proxy service. The UE may identify a source core network service for the downlink packet data unit based on source information in the header of the packet data unit (e.g., a network address in direct communication or a service identifier in indirect communication), and the UE may process the packet data unit using a service protocol corresponding to the identified source core network service.

[0039]

[0052] Aspects of the present disclosure are initially described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to signaling diagrams, process flows, apparatus diagrams, system diagrams, and flowcharts related to addressability in a service-based wireless system.

[0040]

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

[0041]

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

[0042]

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

[0043]

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

[0044]

[0057] In some examples, the network entities 105 may communicate with the service-based network 130, with each other, or both. For example, the network entities 105 may communicate with the service-based network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols), either directly (e.g., directly between the network entities 105), or indirectly (e.g., via the service-based network 130). In some examples, the network entities 105 may communicate with each other via one or more communication links, such as a fronthaul communication link 168 (e.g., between the radio units 170 and the DUs 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, among other examples, one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), or various combinations thereof.

[0045]

[0058] In some examples, the network entity 105 may communicate with a service platform 150 (e.g., a cloud platform) that provides one or more core network services (CN services), one or more RAN services, or any combination thereof (CN / RAN services 185). The CN / RAN services may be provided over the service-based network 130 using one or more application programming interfaces (APIs). For example, one or more DU service APIs 175 may provide an interface for one or more services in the UE 115. The services in the UE 115 may correspond to one or more CN / RAN services 185 in the service platform 150. For example, a network service API 180 in the service-based network 130 may interface with a corresponding DU service API 175 in the DU 165, which interfaces with a corresponding API in the UE 115 to provide service connectivity between the one or more UE 115 services and the corresponding CN / RAN services 185. In some cases, a common API framework may be defined for both the CN / RAN services 185 and the UE 115. The CN / RAN services 185 may be restricted to be available only to the UE 115 or only to other network services based on permissions.

[0046]

[0059] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a Next Generation NodeB or Giga NodeB (any of which may be referred to as a gNB), a 5G NB, a Next Generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, a 6G NB, or other suitable terminology). In some examples, the network entities 105 (e.g., the base stations 140) may be implemented in a centralized (e.g., monolithic, standalone) 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 the base station 140 may include an RU 170, a DU 165, and a DU API 175 for CN / RAN services 185). The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit / receive point (TRP).

[0047]

[0060] Furthermore, in some examples, one or more network entities 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, the network entities 105 may include one or more of a central unit (CU), a DU 165, an RU 170, a RAN intelligent controller (RIC) (e.g., a near-real-time RIC (near-RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof. One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as a virtual unit (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0048]

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

[0049]

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

[0050]

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

[0051]

[0064] The UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or any other suitable terminology, and a “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. The UE 115 may also include or be referred to as a personal electronic device, such as a mobile phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, and may be implemented in various items such as an appliance, a vehicle, a meter, etc., among other examples.

[0052]

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

[0053]

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

[0054]

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

[0055]

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

[0056]

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

[0057]

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

[0058]

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

[0059]

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

[0060]

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

[0061]

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

[0062]

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

[0063]

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

[0064]

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

[0065]

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

[0066]

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

[0067]

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

[0068]

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

[0069]

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

[0070]

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

[0071]

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

[0072]

[0085] The wireless communication system 100 may operate using one or more frequency bands, which may range from 300 megahertz (MHz) to 300 gigahertz (GHz). The 300 MHz to 3 GHz region is commonly known as the ultra-high frequency (UHF) region or decimeter band because wavelengths range in length from approximately 1 decimeter to 1 meter. Although UHF waves may be blocked or redirected by buildings and environmental features, sometimes referred to as clusters, the waves may penetrate structures sufficiently for a macrocell to provide service to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to communications using lower frequency and longer waves in the shortwave (high frequency (HF)) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0073]

[0086] The wireless communications system 100 may also operate using the super high frequency (SHF) region, also known as the centimeter band, which may range from 3 GHz to 30 GHz, or the extremely high frequency (EHF) region of the spectrum, also known as the millimeter band (e.g., 30 GHz to 300 GHz). In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (e.g., base station 140, RU 170), where the EHF antennas on each device may be smaller and more closely spaced than UHF antennas. In some embodiments, such technology may facilitate the use of antenna arrays within the device. However, propagation of EHF transmissions may be more highly attenuated and over shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency ranges, and the designated use of bands across these frequency ranges may vary by country or regulatory body.

[0074]

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

[0075]

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

[0076]

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

[0077]

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

[0078]

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

[0079]

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

[0080]

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

[0081]

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

[0082]

[0095] In some examples, the wireless communication system 100 may include a packet-based network operating using a cloud platform, such as the service platform 150, that provides CN / RAN services 185. The CN / RAN services 185 may, in some examples, be hosted based on the deployment topology and capabilities for service parameters associated with each service. Providing the CN / RAN services 185 enables the separation of specific services (e.g., mobility, connection state management, security, paging, radio access services, quality of service (QoS) configuration and data services, UE capability management, location, messaging, among others) from transport functions (e.g., data radio bearer (DRB) and logical channel (LC) management, data service configuration, among others). Service-based functionality (e.g., message brokers decoupling radio network procedures from network distribution mechanisms) may allow the flexibility of some functions (e.g., Layer 2 (L2) functions) to be hosted 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 scaled independently by increasing or decreasing resources allocated independently across functions). Additionally, efficiency can be increased by providing real-time link management at the RAN edge and enabling adaptation at the DU 165 for more efficient activation, deactivation, or selection of features based on UE state.

[0083]

[0096] 2 illustrates an example wireless communication system 200 supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. Aspects of wireless communication system 200 may implement or be implemented by aspects of wireless communication system 100. In some implementations, wireless communication system 200 illustrates an example architecture of a service-based wireless communication system, such as the system described with reference to FIG.

[0084]

[0097] The wireless communication system 200 may include one or more UEs 115 (e.g., UEs 115-a), one or more network entities (e.g., network entity 105-a), and a service-based network 205. In some aspects, the service-based network 205 may be configured to communicate with or interface with a RAN 210 of the wireless communication system 200, the RAN 210 including one or more network entities (e.g., network entity 105-a). The service-based network 205 may support or provide a set of core network services 215 (e.g., a first core network service 215-a, a second core network service 215-b, a third core network service 215-c, a fourth core network service 215-d, and a fifth core network service 215-e). In some implementations, the service-based network 205 may include or be associated with a cloud platform, with each core network service 215 hosted at a respective network address within the cloud platform.

[0085]

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

[0086]

[0099] 2, the wireless communication system 200 may exhibit a service-based architecture in which entities of the RAN 210 (e.g., network entity 105-a) are configured to connect the UE 115-a to core network services 215 of the service-based network 205. In particular, the RAN 210 (e.g., network entity 105-a) may be configured to relay communications between the UE 115-a and various core network services 215 of the service-based network 205, enabling the UE 115-a to establish and maintain a wireless connection with each core network service 215 and to exchange communications associated with various network functions supported by each core network service 215. In other words, the wireless communication system 200 may enable the UE 115-a to “subscribe” to each core network service 215 on an a la carte basis according to the wants or requirements of the UE 115-a. In this regard, different UEs 115 within the wireless communication system 200 may be able to subscribe to different subsets of the core network services 215 depending on the capabilities of the UE 115, the applications running on the UE 115, the mobility of the UE 115, etc.

[0087]

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

[0088]

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

[0089]

[0102] The service-based network 205 may provide subscription services and policy services (e.g., one core network service 215 may be a subscription service and another core network service 215 may be a policy service). The subscription and / or policy services may be provided for other core network services to receive relevant information (e.g., network subscription or operator policy information) about a given UE (e.g., UE 115-a). If UE 115-a is authorized, the subscription and / or policy services may provide network subscription or policy information to UE 115-a, or UE 115-a may request to create or modify network subscription or policy information.

[0090]

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

[0091]

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

[0092]

[0105] The service-based wireless communications system 200 shown in FIG. 2 may exhibit several differences and advantages over some other types of wireless systems, such as networks that instead exhibit a relatively more vertically hierarchical architecture that includes many “tiers” of different devices that perform functions for the network. A more hierarchical structure may result in processing and other functions being performed in multiple devices (e.g., the network entity 105 and one or more back-end devices), thereby leading to inefficient use of resources and high power consumption. Additionally, the back-end architecture of a network with a more vertically hierarchical architecture may be owned and maintained by only a few operators, which may make it difficult for other parties / entities to integrate with such a system, and the services provided to UEs 115 and other devices may be difficult to customize within such a system.

[0093]

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

[0094]

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

[0095]

[0108] The wireless communications system 200 may 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, agility, reuse, visibility, automation, and failover. Additionally, the service-based architecture may enable each core network service 215 across the RAN 210 and the CN to scale independently by increasing or decreasing the resources allocated across each core network service 215 independently.

[0096]

[0109] The core network services 215 and the UE 115-a may share a common discovery framework for discovery of the core network services 215 provided by the service-based network 205. Discovery of and access to the core network services 215 may be independent. The UE 115-a may discover or access the services directly (e.g., using a respective network address associated with the given core network service 215) or indirectly (e.g., via a proxy that routes communications to the given core network service 215).

[0097]

[0110] The end-to-end routing layer may address packets between the UE 115-a and the core network service 215 on a core network service-by-core network service basis. For example, the UE 115-a may determine one or more core network services 215 with which to communicate via the network entity 105-a to which the UE 115-a is connected. The UE 115-a may determine routing information for the services. The UE 115-a may communicate with the core network service 215 directly (e.g., based on a network address (e.g., an IP address, a Transmission Control Protocol (TCP) port, or a Hypertext Transfer Protocol (HTTP) port) associated with the core network service 215) or indirectly (e.g., by routing the communication through a proxy service). In a direct communication, in the case of an uplink communication, the UE 115-a may send a packet data unit including routing information for the core network service 215 to the core network service 215 via the network entity 105-a. In indirect communication, the UE 115-a may send a packet data unit including a service identifier for the core network service 215 to a proxy service via the network entity 105-a, and the proxy service may route the packet data unit to the core network service 215 based on the service identifier. For example, the proxy service may be the core network service 215. In both the direct and indirect cases, the UE 115-a may select AS resources (e.g., AS resource blocks) for transmitting the uplink packet data unit based on the target core network service. For example, the UE 115-a may receive control signaling, a signaling information block (SIB), or point-to-point signaling from the core network service indicating specific AS resources for each core network service from the network entity 105-a. The UE 115-a may also select a logical channel for transmitting the uplink packet data unit to a specific core network service based on the AS resources associated with each core network service.

[0098]

[0111] In the case of direct downlink communication, the network entity 105-a may route the packet data unit from the core network service to the UE 115-a based on the destination address included in the header of the packet data unit and a local UE 115-a context (e.g., a UE 115-a identifier) ​​created by the network entity 105-a. In the case of indirect downlink transmission, the network entity 105-a may receive the downlink packet data unit including the destination address and the service identifier from the proxy service. The UE 115-a may identify a source core network service 215 for the downlink packet data unit based on the source information in the header of the packet data unit (e.g., a network address in direct communication or a service identifier in indirect communication), and the UE 115-a may process the packet data unit using a service protocol corresponding to the identified source core network service 215.

[0099]

[0112] 3 illustrates an example network architecture 300 supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure. The network architecture 300 may represent an example for implementing one or more aspects of the wireless communication system 100. The network architecture 300 may include a service-based network 305, which may be an example of the service-based network 130 or 205, communicating with the DU 165-a via link 120-b. In this example, the DU 165 may also communicate with one or more CUs 310, which may communicate directly with the 5G core 190-a via backhaul communication link 120-a or indirectly with the 5G core 190-a through one or more disaggregated network entities 105 (e.g., a quasi-RT RIC 330-a via an E2 link, or a non-RT RIC 330-b associated with the SMO 335 (e.g., an SMO framework), or both). The CU 310 may communicate with one or more DUs 165-a via respective midhaul communication links 315 (e.g., F1 interfaces). The DUs 165-a may communicate with one or more RUs 170-a via respective fronthaul communication links 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with the UE 115-b via one or more communication links 125-a. In some implementations, the UE 115-b may be served by multiple RUs 170-a simultaneously.

[0100]

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

[0101]

[0114] In some examples, the 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 with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some examples, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 may be implemented to communicate with the DU 165-a, as needed, for network control and signaling.

[0102]

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

[0103]

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

[0104]

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

[0105]

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

[0106]

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

[0107]

[0120] 4 illustrates an example signaling diagram 400 supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. Aspects of signaling diagram 400 may implement or be implemented by aspects of wireless communication system 100 or wireless communication system 200. For example, the signaling diagram includes UE 115-c, DU 165-b, and core network service 215-f, which may be examples of corresponding devices described herein.

[0108]

[0121] Example 405-a illustrates an example of direct uplink packet transport between the UE 115-c and the core network service 215-f. Example 405-b illustrates an example of direct downlink packet transport between the UE 115-c and the core network service 215-f. The UE 115-c may communicate with the DU 165-b using communication link 220-a, which may be an example of a communication link 220 described herein. Similarly, the DU 165-b may be configured to communicate (e.g., interface) with the core network service 215-f via communication link 225-a, which may be an example of a communication link 225 described herein.

[0109]

[0122] The UE 115-c may discover routing information (e.g., a uniform resource identifier (URI), a network address (e.g., an IP address), or a port (e.g., a TCP port or an HTTP port)) for the core network service 215-f, for example, via discovery information received from the network via the DU 165-b. The UE 115-c may send the packet data unit 410 to the core network service 215-f via the end-to-end routing layer 425-a and the service protocol layer 430-a. The service protocol layer 430-a may be transparent to the DU 165-b and may be specific to the core network service 215-f (e.g., each core network service 215 may be associated with a respective service protocol layer for communicating with the UE 115-c). The core network service 215-f may send the packet data unit 415 to the UE 115-c via the end-to-end routing layer 425-b and the service protocol layer 430-b.

[0110]

[0123] For example, when transmitting the packet data unit 410, the UE 115-c may generate the packet data unit 410 (e.g., including data in the service protocol layer 430-a). The UE 115-c may label the packet data unit 410 with a service address (e.g., an IP address) for the core network service 215-f. For example, the routing layer 425-a may include a UE address (e.g., a UE identifier or an IP address associated with the UE 115-c) and the service address. For example, the UE 115-c may add a header including routing information to the packet data unit 410. The UE 115-c may bind the packet data unit 410 to AS resources for the communication link 220-a based on the core network service 215-f. For example, the UE 115-c may select AS resources for transmission of the packet data unit 410 via the AS layer 420-a. For example, the UE 115-c may select AS resources based on a configuration received from the DU 165-b indicating AS resources associated with the core network service 215-f. In some examples, the SIB may indicate a configuration indicating an association between the AS resources and a particular core network service. In some examples, the UE 115-c may select AS resources based on dedicated signaling from the core network service 215-f. The UE 115-c may also select a logical channel for transmitting the packet data unit 410 based on the AS resources. In some examples, the UE 115-c may add a link-level (e.g., MAC or radio link control (RLC)) header (or multiple headers) to the packet data unit 410 based on a local configuration received from the DU 165-b.

[0111]

[0124] The DU 165-b may route the packet data unit 410 to the core network service 215-f via the communication link 225-a based on the service address. The routing of the packet data unit 410 in the DU 165-b may be transparent to the DU 165-b. In some cases, the routing layer may include the UE address and the service address. The DU 165-b may determine how to route the packet data unit 410 to the core network service 215-f by processing the routing layer 425-a (e.g., a routing header). In some cases, the DU 165-b may determine whether the UE 115-c is authorized to communicate with the core network service 215-f based on, for example, the core network service 215-f configuring the DU 165-b with authorization information for the UE 115-c (via a configuration API). In some examples, the DU 165-b may determine whether the UE 115-c is authorized to communicate with the core network service 215-f based on querying the second core network service for authorization information (e.g., security services or subscription services). If the UE 115-c is authorized to communicate with the core network service 215-f, the DU 165-b may route the packet data unit 410 to the core network service 215-f. If the UE 115-c is not authorized to communicate with the core network service 215-f, the DU 165-b may refrain from routing the packet data unit 410 to the core network service 215-f. In some examples, the DU 165-b may notify the UE 115-c that the UE 115-c is not authorized to communicate with the core network service 215-f.

[0112]

[0125] For the downlink, the core network service 215-f may label (e.g., via a header) the packet data unit 415 with a service label (e.g., a label indicating the core network service 215-f or indicating an IP address associated with the core network service 215-f) and a UE address (e.g., an IP address associated with the UE 115-c). The service protocol layer 430-b may include the data for transmission to the UE 115-c.

[0113]

[0126] The DU 165-b may route the packet data unit 415 to the UE 115-c based on the service label. The routing of the packet data unit 415 in the DU 165-b may be transparent to the DU 165-b. The DU 165-b may bind the packet data unit 415 to AS resources for the communication link 220-a based on the UE 115-c and / or the core network service 215-f. The DU 165-b may receive the packet data unit 415 including a routing layer 425-b (e.g., a header) that includes the service label and the UE address. For example, the routing layer 425-b may include source (core network service 215-f) and destination (UE 115-c) routing addresses (e.g., IP address, TCP port, or HTTP port). The DU 165-b may determine a local identifier for the UE 115-c based on the destination address and a local UE context created by the DU 165-b for communication between the DU 165-b and the UE 115-c. The DU 165-b may determine a local downlink resource configuration (e.g., AS resource) and communication requirements (e.g., quality of service, delay budget, error rate, etc.) based on the routing information in the routing layer 425-b. For example, the DU 165-b may select AS resources for transmission of the packet data unit 415 via the AS layer 420-b. The DU 165-b may schedule transmission of the packet data unit 415 based on the resource configuration and requirements and transmit the packet data unit 415. The packet data unit 415 transmitted from the DU 165-b to the UE 115-c may include local access header(s) (e.g., a MAC or RLC header) in addition to the packet data unit 415 received from the core network service 215-f.

[0114]

[0127] Upon receipt, the UE 115-c may determine source information for the packet data unit 415 based on source information from a routing header (e.g., routing layer 425-b), which indicates which core network service transmitted the packet data unit 415. The UE 115-c may process the packet data unit using a service protocol corresponding to the core network service 215-f.

[0115]

[0128] 5 illustrates an example signaling diagram 500 supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. Aspects of signaling diagram 500 may implement or be implemented by aspects of wireless communication system 100 or wireless communication system 200. For example, the signaling diagram includes UE 115-d, DU 165-c, and core network service 215-g, which may be examples of corresponding devices as described herein.

[0116]

[0129] Example 505-a illustrates an example of indirect-direct uplink packet transport between UE 115-d and core network service 215-g. Example 505-b illustrates an example of indirect downlink packet transport between UE 115-d and core network service 215-g. For example, in signaling diagram 500, UE 115-d and core network service 215-g may communicate via proxy service 510. UE 115-d can communicate with DU 165-c using communication link 220-b, which may be an example of a communication link described herein. Similarly, DU 165-c may be configured to communicate (e.g., interface) with proxy service 510 via communication link 225-b, which may be an example of a communication link 225 described herein. Proxy service 510 may communicate with core network service 215-f via communication link 525, which may be, for example, a network link (e.g., an IP link). The use of the proxy service 510 may hide the core network service topology from the UE 115-d.

[0117]

[0130] The UE 115-d may discover routing information for the core network service 215-g (e.g., a service identifier for the core network service 215-g). For example, the UE 115-d may establish a proxy session with the proxy service 510. The proxy service 510 may map the local service identifier to routing information for the core network service 215-g (e.g., a uniform resource identifier (URI), a network address (e.g., an IP address), or a port (e.g., a TCP port or an HTTP port)). The proxy service may provide the service identifier to the UE 115-d. In some cases, the proxy service 510 may provide service discovery (e.g., discovery of different core network services and capabilities of the core network services) to the UE 115-d. The proxy service 510 may or may not be co-located with the DU 165-c.

[0118]

[0131] The UE 115-d may send the packet data unit 410-a to the core network service 215-g via the proxy service 510. The service protocol layer 430-c may be transparent to the DU 165-c and may be specific to the core network service 215-g (e.g., each core network service 215 may be associated with a respective service protocol layer for communication with the UE 115-d). The core network service 215-g may send the packet data unit 415-a to the UE 115-d via the proxy service 510.

[0119]

[0132] For example, when transmitting a packet data unit 410-a, the UE 115-d may generate the packet data unit 410-a (e.g., including data in the service protocol layer 430-c). The UE 115-d may label the packet data unit 410-aa with a service identifier for the core network service 215-g. For example, the proxy layer 515-a may include a UE address (e.g., a UE identifier or an IP address associated with the UE 115-d) and / or the service identifier. For example, the UE 115-d may add a header including routing information to the packet data unit 410-a. The UE 115-d may bind the packet data unit 410-a to AS resources for the communication link 220-a based on the core network service 215-g. For example, the UE 115-d may select AS resources for transmission of the packet data unit 410-a via the AS layer 420-c. For example, the UE 115-d may select AS resources based on a configuration received from the DU 165-c indicating AS resources associated with the core network service 215-g. In some examples, the SIB may indicate a configuration indicating an association between the AS resources and a particular core network service. In some examples, the UE 115-d may select AS resources based on dedicated signaling from the core network service 215-g (e.g., via the proxy service 510). The UE 115-d may also select a logical channel for transmitting the packet data unit 410-a based on the AS resources. In some examples, the UE 115-d may add a link-level (e.g., MAC or RLC) header (or multiple headers) to the packet data unit 410-a based on a local configuration received from the DU 165-c.

[0120]

[0133] The DU 165-c may route the packet data unit 410-a to the proxy service 510 via the communication link 225-a. The routing of the packet data unit 410-a in the DU 165-c may be transparent to the DU 165-c. In some cases, the proxy layer 515-a may include the UE address and the service identifier. In some cases, the DU 165-c may determine whether the UE 115-d is authorized to communicate with the core network service 215-g, for example, based on the core network service 215-g configuring the DU 165-c with authorization information for the UE 115-d (via a configuration API via the proxy service 510). In some examples, the DU 165-c may determine whether the UE 115-d is authorized to communicate with the core network service 215-g based on querying a second core network service for authorization information (e.g., a security service or a subscription service). If the UE 115-d is authorized to communicate with the core network service 215-g, the DU 165-c may route the packet data unit 410-a to the proxy service 510 for routing to the core network service 215-g. If the UE 115-d is not authorized to communicate with the core network service 215-g, the DU 165-c may refrain from routing the packet data unit 410-a to the proxy service 510. In some examples, the DU 165-c may notify the UE 115-d that the UE 115-d is not authorized to communicate with the core network service 215-g.

[0121]

[0134] The proxy service 510 may route the packet data unit 410-a to the core network service 215-g based on the service identifier in the proxy layer 515-a. For example, the proxy service 510 may map the service identifier to a network address (e.g., a URI, an IP address, or a port (e.g., a TCP port or an HTTP port)) for the core network service 215-g. The routing layer 520-a of the packet data unit 410-a routed from the proxy service 510 to the core network service 215-g may include source proxy address information and a destination service address (e.g., a network address for the core network service 215-g).

[0122]

[0135] For the downlink, the core network service 215-g may label (e.g., via a header) the packet data unit 415-a with a service address (e.g., a label indicating the core network service 215-g or an IP address associated with the core network service 215-g) and a proxy address (e.g., a network address of the proxy). The routing layer 520-b may include the service address and the proxy address. The service protocol layer 430-d may include data for transmission to the UE 115-d.

[0123]

[0136] The proxy service 510 may route the packet data unit 415-a to the DU 165-c based on the routing layer 520-b (e.g., based on the service address and the proxy address). The packet data unit sent from the proxy service 510 to the DU 165-c may include the proxy layer 515-b containing the service identifier. For example, the proxy service 510 may map the service address in the routing layer 520-b to a service identifier for the core network service 215-g.

[0124]

[0137] The DU 165-c may route the packet data unit 415-a to the UE 115-d based on the service identifier in the proxy layer 515-b. The routing of the packet data unit 415-a in the DU 165-c may be transparent to the DU 165-c. The DU 165-c may bind the packet data unit 415-a to AS resources for the communication link 220-a based on the UE 115-d and / or the core network service 215-g. The DU 165-c may receive the packet data unit 415-a including the proxy layer 515-b (e.g., a header) that includes the identifier. The DU 165-c may determine a local identifier for the UE 115-d based on the service identifier and a local UE context created by the DU 165-c for communication between the DU 165-c and the UE 115-d. The DU 165-c may determine local downlink resource configurations (e.g., AS resources) and communication requirements (e.g., quality of service, delay budget, error rate, etc.) based on the routing information in the routing layer 425-b. For example, the DU 165-c may select AS resources for transmission of the packet data unit 415-a via the AS layer 420-d. The DU 165-c may schedule transmission of the packet data unit 415-a based on the resource configurations and requirements and transmit the packet data unit 415-a. The packet data unit 415-a transmitted from the DU 165-c to the UE 115-d may include local access header(s) (e.g., a MAC or RLC header) in addition to the packet data unit 415-a received from the proxy service.

[0125]

[0138] Upon receipt, the UE 115-d may determine source information for the packet data unit 415-a based on a service identifier in the proxy layer 515-b, which indicates which core network service transmitted the packet data unit 415-a. The UE 115-d may process the packet data unit using a service protocol corresponding to the core network service 215-g.

[0126]

[0139] 6 illustrates an example process flow 600 for supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. The process flow 600 may include a UE 115-e, which may be an example of a UE 115 described herein. The process flow 600 may include a DU 165-d, which may be an example of a DU 165 described herein. The process flow 600 may include a first core network service 215-h and a second core network service 215-i, which may be examples of core network services 215 described herein. In the following description of process flow 600, operations between UE 115-e, DU 165-d, first core network service 215-h, and second core network service 215-i may be transmitted in an order different from the example order shown, or operations performed by UE 115-e, DU 165-d, first core network service 215-h, and second core network service 215-i may be performed in a different order or at a different time. Some operations may also be omitted from process flow 600, and other operations may be added to process flow 600.

[0127]

[0140] At 605, the UE 115-e may establish communication with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU 165-d, wherein each core network service of the set of core network services is associated with a respective addressing scheme, via a wireless connection between the UE 115-e and the DU 165-d. The set of core network services includes a first core network service 215-h and a second core network service 215-i.

[0128]

[0141] At 610, the UE 115-e may transmit a first packet data unit associated with the first core network service 215-h over a wireless connection in accordance with a first addressing scheme associated with the first core network service 215-h.

[0129]

[0142] At 615, the DU 165-d may route the first packet data unit to the first core network service 215-h based on the first addressing scheme.

[0130]

[0143] At 620, the UE 115-e may transmit, via the wireless connection, a second packet data unit associated with the second core network service 215-i according to a second addressing scheme associated with the second core network service 215-i.

[0131]

[0144] At 625, the DU 165-d may route the second packet data unit to the second core network service 215-i based on the second addressing scheme.

[0132]

[0145] In some examples, the UE 115-e may determine first routing information associated with the first core network service 215-h and second routing information associated with the second core network service 215-i. Transmitting the first packet data unit according to the first addressing scheme at 610 may include attaching a first header to the first packet data unit including the first routing information, and transmitting the second packet data unit according to the second addressing scheme at 620 may include attaching a second header to the second packet data unit including the second routing information.

[0133]

[0146] In some examples, the UE 115-e may determine a first AS resource associated with the first core network service 215-h and a second AS resource associated with the second core network service 215-i. Transmitting the first packet data unit according to the first addressing scheme at 610 may include transmitting the first packet data unit using the first AS resource, and transmitting the second packet data unit according to the second addressing scheme at 620 may include transmitting the second packet data unit using the second AS resource. In some cases, the UE 115-e may determine a first logical channel associated with the first AS resource and a second logical channel associated with the second AS resource. In some examples, the UE 115-e may receive control information from the DU 165-d indicating the first AS resource and the second AS resource.

[0134]

[0147] In some cases, the DU 165-d may determine that a first core network service 215-h is associated with the first packet data unit based on first routing information included in a first header of the first packet data unit, and may determine that a second core network service 215-i is associated with the second packet data unit based on second routing information included in a second header of the second packet data unit. At 615, routing the first packet data unit to the first core network service based on the first addressing scheme may include routing the first packet data unit based on the first routing information, and at 625, routing the second packet data unit to the second core network service based on the second addressing scheme may include routing the second packet data unit based on the second routing information.

[0135]

[0148] In some cases, the DU 165-d may determine that the UE 115-e is authorized to communicate with the first core network service 215-h, and routing the first packet data unit to the first core network service 215-h is based on the determination that the UE 115-e is authorized to communicate with the first core network service 215-h. In some cases, the DU 165-d may receive control information indicating a set of network entities, including the UE 115-e, that are authorized to communicate with the first core network service 215-h. The determination that the UE 115-e is authorized to communicate with the first core network service 215-h may be based on the control information.

[0136]

[0149] In some cases, the DU 165-d may receive from the UE 115-e a third packet data unit associated with a third core network service, the third packet data unit being received according to a third addressing scheme associated with the third core network service. The DU 165-d may determine that the UE 115-e is not authorized to communicate with the third core network service. The DU 165-d may refrain from routing the third packet data unit to the third core network service based on the determination that the UE 115-e is not authorized to communicate with the third core network service. In some cases, the DU 165-d may receive control information indicating a set of network entities, excluding the UE 115-e, that are authorized to communicate with the third core network service. The determination that the UE 115-e is not authorized to communicate with the third core network service may be based on the control information.

[0137]

[0150] At 630, the DU 165-d may receive a third packet data unit from the first core network service 215-h, the third packet data unit including a header indicating destination routing information.

[0138]

[0151] At 635, the DU 165-d may transmit the third packet data unit to the UE 115-e based on the destination routing information indicating the UE 115-e as the destination. In some cases, the DU 165-d may determine downlink resources for the third packet data unit based on the destination routing information and based on a header further indicating source routing information, and transmitting the third packet data unit includes transmitting the third packet data unit using the downlink resources.

[0139]

[0152] At 640, the UE 115-e may determine, based on the routing information, that the third packet data unit is associated with the first core network service 215-h and may process the third packet data unit according to a protocol associated with the first core network service 215-h.

[0140]

[0153] In some cases, the first core network service 215-h is associated with a first API and the second core network service 215-i is associated with a second API.

[0141]

[0154] 7 illustrates an example process flow 700 for supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. The process flow 700 may include a UE 115-f, which may be an example of a UE 115 described herein. The process flow 700 may include a DU 165-e, which may be an example of a DU 165 described herein. The process flow 700 may include a proxy service 510-a, which may be an example of a proxy service 510 described herein. The process flow 700 may include a first core network service 215-j and a second core network service 215-k, which may be examples of core network services 215 described herein. In the following description of process flow 700, the operations between UE 115-f, DU 165-e, proxy service 510-a, first core network service 215-j, and second core network service 215-k may be transmitted in an order different from the example order shown, or the operations performed by UE 115-f, DU 165-e, proxy service 510-a, first core network service 215-j, and second core network service 215-k may be performed in a different order or at different times. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

[0142]

[0155] At 705, the UE 115-f may establish communication with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU 165-e via a wireless connection between the UE 115-f and the DU 165-e and via the proxy service 510-a. The set of core network services includes a first core network service 215-j and a second core network service 215-k. At 705, the UE 115-f may receive control information from the proxy service 510-a indicating a first service identifier associated with the first core network service 215-j and a second service identifier associated with the second core network service 215-k.

[0143]

[0156] At 710, the UE 115-f may transmit a first packet data unit associated with the first core network service 215-j over the wireless connection in accordance with a first addressing scheme associated with the first core network service 215-j. Transmitting the first packet data unit in accordance with the first addressing scheme includes transmitting an indication of a first service identifier associated with the first core network service 215-j with the first packet data unit.

[0144]

[0157] At 715, the DU 165-e may route the first packet data unit to the proxy service 510-a based on the first addressing scheme.

[0145]

[0158] At 720, the proxy service 510-a may route the first packet data unit to the first core network service 215-j based on a first service identifier associated with the first core network service 215-j (e.g., based on mapping the first service identifier to a network address associated with the first core network service).

[0146]

[0159] At 725, the UE 115-f may transmit, over the wireless connection, a second packet data unit associated with the second core network service 215-k in accordance with a second addressing scheme associated with the second core network service 215-k. Transmitting the second packet data unit in accordance with the second addressing scheme includes transmitting, with the second packet data unit, an indication of a second service identifier associated with the second core network service 215-k.

[0147]

[0160] At 730, the DU 165-e may route the second packet data unit to the proxy service 510-a based on the second addressing scheme.

[0148]

[0161] At 735, the proxy service 510-a may route the second packet data unit to the second core network service 215-k based on a second service identifier associated with the second core network service 215-k (e.g., based on mapping the second service identifier to a network address associated with the second core network service).

[0149]

[0162] In some examples, the UE 115-f may receive, along with the control information, an indication of AS resources associated with the proxy service 510-a at 705. Transmitting the first packet data unit according to the first addressing scheme at 710 may include transmitting the first packet data unit using the AS resources, and transmitting the second packet data unit according to the second addressing scheme at 725 may include transmitting the second packet data unit using the AS resources. The UE 115-f may determine a logical channel associated with the AS resources.

[0150]

[0163] At 740, the first core network service 215-j may send a third packet data unit (e.g., the header may include source and destination information) to the proxy service 510-a, indicating the UE 115-f as the destination and the first core network service 215-j as the source.

[0151]

[0164] At 745, based on the source and destination information, the proxy service 510-a can route the third packet data unit to the DU 165-e, and the DU 165-e can receive the third packet data unit. The third packet data unit may include a header indicating a service identifier associated with the first core network service 215-j and a destination (e.g., the UE 115-f). For example, the proxy service may map a network address associated with the first core network service 215-j to a service identifier for the first core network service 215-j.

[0152]

[0165] At 750, the DU 165-e may transmit a third packet data unit to the UE 115-f based on the service identifier.

[0153]

[0166] At 755, the UE 115-f may determine that the third packet data unit is associated with the first core network service 215-j based on the first service identifier being included in the header of the third packet data unit. The UE 115-f may process the third packet data unit according to a protocol associated with the first core network service 215-j.

[0154]

[0167] In some cases, the first core network service 215-j is associated with a first API and the second core network service 215-k is associated with a second API.

[0155]

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

[0156]

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

[0157]

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

[0158]

[0171] The communications manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for implementing various aspects of addressability in the service-based wireless system described herein. For example, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.

[0159]

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

[0160]

[0173] Additionally or alternatively, in some examples, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communications management software or firmware). If implemented in code executed by a processor, the functionality of the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., that may be configured as or otherwise support a means for performing the functions described in this disclosure).

[0161]

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

[0162]

[0175] The communications manager 820 may support wireless communications in a UE in accordance with examples disclosed herein. For example, the communications manager 820 may be configured as or otherwise support a means for establishing, over a wireless connection between the UE and the DU, communications with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, where each core network service of the set of core network services is associated with a respective addressing scheme. The communications manager 820 may be configured as or otherwise support a means for transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service. The communications manager 820 may be configured as or otherwise support a means for transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service.

[0163]

[0176] By including or configuring a communications manager 820 according to the examples described herein, the device 805 (e.g., a processor controlling or otherwise coupled to the receiver 810, the transmitter 815, the communications manager 820, or a combination thereof) can support techniques for reduced processing, reduced power consumption, and more efficient utilization of communications resources.

[0164]

[0177] 9 shows a block diagram 900 of a device 905 that supports addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 905 may be an example of an aspect of the device 805 or UE 115 described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0165]

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

[0166]

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

[0167]

[0180] Device 905, or its various components, may be an example of a means for implementing various aspects of addressability in a service-based wireless system described herein. For example, communications manager 920 may include a service-based network communications manager 925, an uplink addressing scheme manager 930, or any combination thereof. Communications manager 920 may be an example of an aspect of communications manager 820 described herein. In some examples, communications manager 920, or its various components, may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with receiver 910, transmitter 915, or both. For example, communications manager 920 may receive information from receiver 910 and transmit information to transmitter 915, or may be integrated in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations described herein.

[0168]

[0181] The communications manager 920 may support wireless communications in the UE in accordance with examples disclosed herein. The service-based network communications manager 925 may be configured as or otherwise support a means for establishing communications with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, over a wireless connection between the UE and the DU, where each core network service of the set of core network services is associated with a respective addressing scheme. The uplink addressing scheme manager 930 may be configured as or otherwise support a means for transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service. The uplink addressing scheme manager 930 may be configured as or otherwise support a means for transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service.

[0169]

[0182] 10 illustrates a block diagram 1000 of a communications manager 1020 supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. The communications manager 1020 may be an example of aspects of communications manager 820, communications manager 920, or both, described herein. The communications manager 1020, or its various components, may be an example of a means for implementing various aspects of addressability in a service-based wireless system described herein. For example, the communications manager 1020 may include a service-based network communications manager 1025, an uplink addressing scheme manager 1030, an uplink routing information manager 1035, an AS resource manager 1040, a service identifier manager 1045, a downlink packet manager 1050, a downlink source manager 1055, a core network service protocol manager 1060, a logical channel manager 1065, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0170]

[0183] The communications manager 1020 may support wireless communications in the UE in accordance with examples disclosed herein. The service-based network communications manager 1025 may be configured as or otherwise support a means for establishing communications with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, over a wireless connection between the UE and the DU, where each core network service of the set of core network services is associated with a respective addressing scheme. The uplink addressing scheme manager 1030 may be configured as or otherwise support a means for transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service. In some examples, the uplink addressing scheme manager 1030 may be configured as or otherwise support a means for transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service.

[0171]

[0184] In some examples, the uplink routing information manager 1035 may be configured with or otherwise support a means for determining first routing information associated with a first core network service and second routing information associated with a second core network service, wherein transmitting the first packet data unit according to the first addressing scheme includes attaching a first header to the first packet data unit including the first routing information, and transmitting the second packet data unit according to the second addressing scheme includes attaching a second header to the second packet data unit including the second routing information.

[0172]

[0185] In some examples, the AS resource manager 1040 may be configured as or otherwise support a means for determining first AS resources associated with a first core network service and second AS resources associated with a second core network service, wherein transmitting the first packet data unit according to the first addressing scheme includes transmitting the first packet data unit using the first AS resources, and transmitting the second packet data unit according to the second addressing scheme includes transmitting the second packet data unit using the second AS resources.

[0173]

[0186] In some examples, the logical channel manager 1065 may be configured as or otherwise support a means for determining, at a UE, a first logical channel associated with a first AS resource and a second logical channel associated with a second AS resource.

[0174]

[0187] In some examples, the AS resource manager 1040 may be configured as or otherwise support a means for receiving control information indicating the first AS resource and the second AS resource from the DU over a wireless connection.

[0175]

[0188] In some examples, the service identifier manager 1045 may be configured as or otherwise support a means for receiving, via a wireless connection, control information from a proxy service indicating a first service identifier associated with a first core network service and a second service identifier associated with a second core network service, wherein transmitting the first packet data unit according to the first addressing scheme includes transmitting an indication of the first service identifier with the first packet data unit, and transmitting the second packet data unit according to the second addressing scheme includes transmitting an indication of the second service identifier with the second packet data unit.

[0176]

[0189] In some examples, the AS resource manager 1040 may be configured as or otherwise support a means for receiving, along with the control information, an indication of AS resources associated with the proxy service, and wherein transmitting the first packet data unit according to the first addressing scheme includes transmitting the first packet data unit using the AS resources, and transmitting the second packet data unit according to the second addressing scheme includes transmitting the second packet data unit using the AS resources.

[0177]

[0190] In some examples, the logical channel manager 1065 may be configured or may otherwise support a means for determining, at a UE, the logical channels associated with AS resources.

[0178]

[0191] In some examples, the downlink packet manager 1050 may be configured or otherwise support a means for receiving the third packet data unit over a wireless connection. In some examples, the downlink source manager 1055 may be configured or otherwise support a means for determining that the third packet data unit is associated with a first core network service based on first routing information included in a first header of the third packet data unit. In some examples, the core network service protocol manager 1060 may be configured or otherwise support a means for processing the third packet data unit in accordance with a first protocol associated with the first core network service.

[0179]

[0192] In some examples, the service identifier manager 1045 may be configured or otherwise support a means for receiving control information indicating a first service identifier associated with the first core network service from the proxy service over a wireless connection. In some examples, the downlink packet manager 1050 may be configured or otherwise support a means for receiving a third packet data unit over a wireless connection. In some examples, the downlink source manager 1055 may be configured or otherwise support a means for determining that the third packet data unit is associated with the first core network service based on a first service identifier included in a first header of the third packet data unit. In some examples, the core network service protocol manager 1060 may be configured or otherwise support a means for processing the third packet data unit in accordance with a first protocol associated with the first core network service.

[0180]

[0193] In some examples, the first core network service is associated with a first API and the second core network service is associated with a second API.

[0181]

[0194] In some examples, the first core network service and the second core network service each include one of a mobility service, a connection state management service, a security service, a paging service, a wireless access service, a data service, a capability management service, a location service, or a messaging service.

[0182]

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

[0183]

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

[0184]

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

[0185]

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

[0186]

[0199] The processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting addressability in a service-based wireless system). For example, the device 1105 or a component of the device 1105 may include the processor 1140 and the memory 1130 coupled to or to the processor 1140, where the processor 1140 and the memory 1130 are configured to perform various functions described herein.

[0187]

[0200] The communications manager 1120 may support wireless communications in a UE in accordance with examples disclosed herein. For example, the communications manager 1120 may be configured as or otherwise support a means for establishing, over a wireless connection between a UE and a DU, communications with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, where each core network service of the set of core network services is associated with a respective addressing scheme. The communications manager 1120 may be configured as or otherwise support a means for transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service. The communications manager 1120 may be configured as or otherwise support a means for transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service.

[0188]

[0201] By including or configuring a communications manager 1120 in accordance with examples described herein, the device 1105 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient use of communications resources, improved coordination between devices, and improved utilization of processing power.

[0189]

[0202] In some examples, communications manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with transceiver 1115, one or more antennas 1125, or any combination thereof. Although communications manager 1120 is shown as a separate component, in some examples, one or more functions described with reference to communications manager 1120 may be supported or implemented by processor 1140, memory 1130, code 1135, or any combination thereof. For example, code 1135 may include instructions executable by processor 1140 to cause device 1105 to implement various aspects of addressability in a services-based wireless system as described herein, or processor 1140 and memory 1130 may be otherwise configured to perform or support such operations.

[0190]

[0203] 12 shows a block diagram 1200 of a device 1205 supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of an aspect of the DU 165 described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0191]

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

[0192]

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

[0193]

[0206] The communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof or components thereof may be examples of means for implementing various aspects of addressability in the service-based wireless system described herein. For example, the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.

[0194]

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

[0195]

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

[0196]

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

[0197]

[0210] The communications manager 1220 may support wireless communications at the DU in accordance with examples disclosed herein. For example, the communications manager 1220 may be configured as or otherwise support a means for receiving from the UE a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service. The communications manager 1220 may be configured as or otherwise support a means for routing the first packet data unit to the first core network service based on the first addressing scheme. The communications manager 1220 may be configured as or otherwise support a means for receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service. The communications manager 1220 may be configured with or may otherwise support a means for routing the second packet data unit to a second core network service based on a second addressing scheme.

[0198]

[0211] By including or configuring a communications manager 1220 according to the examples described herein, the device 1205 (e.g., a processor controlling or otherwise coupled to the receiver 1210, the transmitter 1215, the communications manager 1220, or a combination thereof) can support techniques for reduced processing, reduced power consumption, and more efficient utilization of communications resources.

[0199]

[0212] 13 shows a block diagram 1300 of a device 1305 supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of an aspect of the device 1205 or DU 165 described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0200]

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

[0201]

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

[0202]

[0215] The device 1305, or its various components, may be an example of a means for implementing various aspects of addressability in a service-based wireless system described herein. For example, the communications manager 1320 may include an uplink addressing scheme manager 1325, a core network service routing manager 1330, or any combination thereof. The communications manager 1320 may be an example of an aspect of the communications manager 1220 described herein. In some examples, the communications manager 1320, or its various components, may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with the receiver 1310, the transmitter 1315, or both. For example, the communications manager 1320 may receive information from the receiver 1310 and transmit information to the transmitter 1315, or may be integrated in combination with the receiver 1310, the transmitter 1315, or both to acquire information, output information, or perform various other operations described herein.

[0203]

[0216] The communications manager 1320 may support wireless communications at the DU according to examples disclosed herein. The uplink addressing scheme manager 1325 may be configured as or otherwise support a means for receiving from the UE a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service. The core network service routing manager 1330 may be configured as or otherwise support a means for routing the first packet data unit to the first core network service based on the first addressing scheme. The uplink addressing scheme manager 1325 may be configured as or otherwise support a means for receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service. The core network service routing manager 1330 may be configured with or may otherwise support a means for routing the second packet data unit to the second core network service based on the second addressing scheme.

[0204]

[0217] 14 shows a block diagram 1400 of a communications manager 1420 supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. The communications manager 1420 may be an example of aspects of the communications manager 1220, the communications manager 1320, or both, described herein. The communications manager 1420, or its various components, may be an example of a means for implementing various aspects of addressability in a service-based wireless system described herein. For example, the communications manager 1420 may include an uplink addressing scheme manager 1425, a core network service routing manager 1430, an uplink routing information manager 1435, a UE authorization manager 1440, a downlink packet manager 1445, a UE routing manager 1450, a downlink resource manager 1455, or any combination thereof. Each of these components may communicate directly or indirectly with one another (e.g., via one or more buses).

[0205]

[0218] The communications manager 1420 may support wireless communications at the DU in accordance with examples disclosed herein. The uplink addressing scheme manager 1425 may be configured as or otherwise support a means for receiving from the UE a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service. The core network service routing manager 1430 may be configured as or otherwise support a means for routing the first packet data unit to the first core network service based on the first addressing scheme. In some examples, the uplink addressing scheme manager 1425 may be configured as or otherwise support a means for receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service. In some examples, the core network service routing manager 1430 may be configured as or otherwise support a means for routing the second packet data unit to the second core network service based on the second addressing scheme.

[0206]

[0219] In some examples, the uplink routing information manager 1435 may be configured as or otherwise support a means for determining, based on first routing information included in a first header of the first packet data unit, that a first core network service is associated with the first packet data unit, and for determining, based on second routing information included in a second header of the second packet data unit, that a second core network service is associated with the second packet data unit, wherein routing the first packet data unit to the first core network service based on the first addressing scheme includes routing the first packet data unit based on the first routing information, and routing the second packet data unit to the second core network service based on the second addressing scheme includes routing the second packet data unit based on the second routing information.

[0207]

[0220] In some examples, the UE authorization manager 1440 may be configured as or otherwise support a means for determining that the UE is authorized to communicate with the first core network service, and routing the first packet data unit to the first core network service is based on the determination that the UE is authorized to communicate with the first core network service.

[0208]

[0221] In some examples, the UE authorization manager 1440 may be configured as or otherwise support a means for receiving control information indicating a set of network entities, including the UE, that are authorized to communicate with the first core network service, and the determination that the UE is authorized to communicate with the first core network service is based on the control information.

[0209]

[0222] In some examples, the uplink addressing scheme manager 1425 may be configured or otherwise support a means for receiving from the UE a third packet data unit associated with a third core network service of the set of core network services, the third packet data unit being received according to a third addressing scheme associated with the third core network service. In some examples, the UE authorization manager 1440 may be configured or otherwise support a means for determining that the UE is not authorized to communicate with the third core network service. In some examples, the uplink addressing scheme manager 1425 may be configured or otherwise support a means for refraining from routing the third packet data unit to the third core network service based on a determination that the UE is not authorized to communicate with the third core network service.

[0210]

[0223] In some examples, the UE authorization manager 1440 may be configured as or otherwise support a means for receiving control information indicating a set of network entities, excluding the UE, that are authorized to communicate with the third core network service, and the determination that the UE is not authorized to communicate with the third core network service is based on the control information.

[0211]

[0224] In some examples, the downlink packet manager 1445 may be configured or otherwise support receiving, from the first core network service, a third packet data unit including a first header indicating destination routing information. In some examples, the UE routing manager 1450 may be configured or otherwise support transmitting, to the UE, the third packet data unit based on the destination routing information indicating the UE.

[0212]

[0225] In some examples, the downlink resource manager 1455 may be configured as or otherwise support a means for determining downlink resources for the third packet data unit based on the destination routing information and based on the first header further indicating the source routing information, and wherein transmitting the third packet data unit includes transmitting the third packet data unit using the downlink resources.

[0213]

[0226] In some examples, routing the first packet data unit to the first core network service based on the first addressing scheme includes routing the first packet data unit to a proxy service. In some examples, routing the second packet data unit to the second core network service based on the second addressing scheme includes routing the second packet data unit to the proxy service or to a second proxy service associated with the second core network service.

[0214]

[0227] In some examples, the first core network service is associated with a first API and the second core network service is associated with a second API.

[0215]

[0228] In some examples, the first core network service and the second core network service each include one of a mobility service, a connection state management service, a security service, a paging service, a wireless access service, a data service, a capability management service, a location service, or a messaging service.

[0216]

[0229] 15 shows a diagram of a system 1500 including a device 1505 supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure. The device 1505 may be an example of or include components of the device 1205, device 1305, or DU 165 described herein. The device 1505 may include components for two-way voice and data communication, including components for transmitting and receiving communications, such as a communications manager 1520, a transceiver 1510, an antenna 1515, memory 1525, code 1530, and a processor 1535. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1540).

[0217]

[0230] The transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1510 may include a wired transceiver and may bidirectionally communicate with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may bidirectionally communicate with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of transmitting or receiving (e.g., simultaneously) wireless transmissions. The transceiver 1510 may also include a modem for modulating signals, providing the modulated signals for transmission (e.g., by one or more antennas 1515, by a wired transmitter), receiving the modulated signals (e.g., from one or more antennas 1515 or from a wired receiver), and demodulating the signals. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled with one or more antennas 1515 configured to support various receive or acquisition operations, or one or more interfaces coupled with one or more antennas 1515 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1510 may include, or be configured to couple with, one or more processors or memory components operable to perform or support an operation based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and one or more antennas 1515, or the transceiver 1510 and one or more antennas 1515 and one or more processor or memory components (e.g., the processor 1535, or the memory 1525, or both) may be included in a chip or chip assembly installed in the device 1505.The transceiver 1510, or the transceiver 1510 and one or more antennas 1515 or wired interface, where applicable, may be an example of the transmitter 1215, the transmitter 1315, the receiver 1210, the receiver 1310, or any combination or component thereof described herein. In some examples, the transceiver may be operable to support communication over one or more communication links (e.g., the communication link 125, the backhaul communication link 120, the fronthaul communication link 168).

[0218]

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

[0219]

[0232] The processor 1535 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1535. The processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1525) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting addressability in a service-based wireless system). For example, the device 1505 or a component of the device 1505 may include the processor 1535 and the memory 1525 coupled to the processor 1535, where the processor 1535 and the memory 1525 are configured to perform various functions described herein. Processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functionality (e.g., by executing code 1530) to perform the functionality of device 1505. Processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored within device 1505 (e.g., in memory 1525). In some implementations, processor 1535 may be a component of a processing system. A processing system may generally refer to a system or set of machines or components that receives inputs, processes the inputs, and generates a set of outputs (e.g., that may be passed to other systems or components of device 1505).For example, the processing system of device 1505 may refer to a system that includes various other components or subcomponents of device 1505, such as processor 1535, or transceiver 1510, or communications manager 1520, or other components or combinations of components of device 1505. The processing system of device 1505 may interface with other components of device 1505 and may process information (e.g., input or signals) received from other components or output information to other components. For example, a chip or modem of device 1505 may include a processing system and an interface for outputting information, an interface for acquiring information, or both. The interfaces may be implemented as or may otherwise include a first interface configured to output information and a second interface configured to acquire information. In some implementations, the first interface may refer to an interface between the processing system and a transmitter of the chip or modem, whereby device 1505 may transmit information output from the chip or modem. In some implementations, the second interface may refer to an interface between a processing system and a receiver of a chip or modem, whereby the device 1505 can receive information or signal input, which information can pass to the processing system. Those skilled in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0220]

[0233] In some examples, bus 1540 may support communications within (e.g., within) protocol layers of a protocol stack. In some examples, bus 1540 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications conducted within a component of device 1505 or between different components of device 1505, which may be collocated or located in different locations (e.g., device 1505 may refer to a system in which one or more of communications manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 may be located in one of or split among different components).

[0221]

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

[0222]

[0235] The communications manager 1520 may support wireless communications at the DU in accordance with examples disclosed herein. For example, the communications manager 1520 may be configured as or otherwise support a means for receiving from the UE a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service. The communications manager 1520 may be configured as or otherwise support a means for routing the first packet data unit to the first core network service based on the first addressing scheme. The communications manager 1520 may be configured as or otherwise support a means for receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service. The communications manager 1520 may be configured with or may otherwise support a means for routing the second packet data unit to a second core network service based on a second addressing scheme.

[0223]

[0236] By including or configuring a communications manager 1520 in accordance with examples described herein, the device 1505 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient use of communications resources, improved coordination between devices, and improved utilization of processing power.

[0224]

[0237] In some examples, communications manager 1520 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or otherwise cooperating with transceiver 1510, one or more antennas 1515 (e.g., if applicable), or any combination thereof. Although communications manager 1520 is shown as a separate component, in some examples, one or more functions described with reference to communications manager 1520 may be supported or implemented by processor 1535, memory 1525, code 1530, transceiver 1510, or any combination thereof. For example, code 1530 may include instructions executable by processor 1535 to cause device 1505 to implement various aspects of addressability in a services-based wireless system as described herein, or processor 1535 and memory 1525 may otherwise be configured to perform or support such operations.

[0225]

[0238] FIG. 16 shows a flowchart illustrating a method 1600 for supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1600 may be performed by the UE 115 described with reference to FIGS. 1-11. In some examples, the UE may execute a set of instructions that control functional elements of the UE to perform the described functionality. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functionality.

[0226]

[0239] At 1605, the method may include establishing communication with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, wherein each core network service of the set of core network services is associated with a respective addressing scheme, via a wireless connection between the UE and the DU. The operations of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed by the service-based network communications manager 1025 described with reference to FIG. 10.

[0227]

[0240] At 1610, the method may include transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service. The operations of 1610 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed by the uplink addressing scheme manager 1030 described with reference to FIG. 10.

[0228]

[0241] At 1615, the method may include transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service. The operations of 1615 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed by the uplink addressing scheme manager 1030 described with reference to FIG. 10.

[0229]

[0242] FIG. 17 shows a flowchart illustrating a method 1700 for supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1700 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1700 may be performed by the UE 115 described with reference to FIGS. 1-11. In some examples, the UE may execute a set of instructions that control functional elements of the UE to perform the described functionality. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functionality.

[0230]

[0243] At 1705, the method may include establishing communication with a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, wherein each core network service of the set of core network services is associated with a respective addressing scheme, via a wireless connection between the UE and the DU. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed by the service-based network communications manager 1025 described with reference to FIG. 10.

[0231]

[0244] At 1710, the method may include transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service. The operations of 1710 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed by the uplink addressing scheme manager 1030 described with reference to FIG. 10.

[0232]

[0245] At 1715, the method may include transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service. The operations of 1715 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed by the uplink addressing scheme manager 1030 described with reference to FIG. 10.

[0233]

[0246] At 1720, the method may include receiving, via the wireless connection, a third packet data unit. The operations of 1720 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1720 may be performed by the downlink packet manager 1050 described with reference to FIG. 10.

[0234]

[0247] At 1725, the method may include determining that the third packet data unit is associated with the first core network service based on the first routing information included in the first header of the third packet data unit. The operations of 1725 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1725 may be performed by the downlink source manager 1055 described with reference to FIG. 10.

[0235]

[0248] At 1730, the method may include processing the third packet data unit according to a first protocol associated with the first core network service. The operations of 1730 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1730 may be performed by the core network services protocol manager 1060 described with reference to FIG. 10.

[0236]

[0249] FIG. 18 shows a flowchart illustrating a method 1800 for supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1800 may be implemented by a DU or components thereof as described herein. For example, the operations of method 1800 may be performed by a DU as described with reference to FIGS. 1-7 and 12-15. In some examples, the DU may execute a set of instructions that control functional elements of the DU to perform the described functions. Additionally or alternatively, the DU may implement aspects of the described functions using dedicated hardware.

[0237]

[0250] At 1805, the method may include receiving, from the UE, a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed by the uplink addressing scheme manager 1425 described with reference to FIG. 14.

[0238]

[0251] At 1810, the method may include routing the first packet data unit to a first core network service based on the first addressing scheme. The operations of 1810 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed by the core network service routing manager 1430 described with reference to FIG. 14.

[0239]

[0252] At 1815, the method may include receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service. The operations of 1815 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1815 may be performed by the uplink addressing scheme manager 1425 described with reference to FIG. 14.

[0240]

[0253] At 1820, the method may include routing the second packet data unit to a second core network service based on the second addressing scheme. The operations of 1820 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1820 may be performed by the core network service routing manager 1430 described with reference to FIG. 14.

[0241]

[0254] FIG. 19 shows a flowchart illustrating a method 1900 for supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure. The operations of method 1900 may be implemented by a DU or components thereof as described herein. For example, the operations of method 1900 may be performed by a DU as described with reference to FIGS. 1-7 and 12-15. In some examples, the DU may execute a set of instructions that control functional elements of the DU to perform the described functions. Additionally or alternatively, the DU may use dedicated hardware to implement aspects of the described functions.

[0242]

[0255] At 1905, the method may include receiving, from the UE, a first packet data unit associated with a first core network service among a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service. The operations of 1905 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1905 may be performed by the uplink addressing scheme manager 1425 described with reference to FIG. 14.

[0243]

[0256] At 1910, the method may include routing the first packet data unit to a first core network service based on the first addressing scheme. The operations of 1910 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1910 may be performed by the core network service routing manager 1430 described with reference to FIG. 14.

[0244]

[0257] At 1915, the method may include receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service. The operations of 1915 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1915 may be performed by the uplink addressing scheme manager 1425 described with reference to FIG. 14.

[0245]

[0258] At 1920, the method may include routing the second packet data unit to a second core network service based on the second addressing scheme. The operations of 1920 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1920 may be performed by the core network service routing manager 1430 described with reference to FIG. 14.

[0246]

[0259] At 1925, the method may include receiving a third packet data unit from the first core network service, the third packet data unit including the first header indicating destination routing information. The operations of 1925 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1925 may be performed by the downlink packet manager 1445 described with reference to FIG. 14.

[0247]

[0260] At 1930, the method may include transmitting the third packet data unit to the UE based on the destination routing information indicating the UE. The operations of 1930 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operations of 1930 may be performed by the UE routing manager 1450 described with reference to FIG. 14.

[0248]

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

[0249]

[0262] Aspect 1: A method for wireless communication in a UE, the method including: establishing communication with a set of core network services provided by a service-based network configured to interface with a RAN associated with a DU, over a wireless connection between the UE and a DU, wherein each core network service of the set of core network services is associated with a respective addressing scheme; transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service; and transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service.

[0250]

[0263] Aspect 2: The method of aspect 1, further comprising determining first routing information associated with a first core network service and second routing information associated with a second core network service, wherein transmitting the first packet data unit according to the first addressing scheme comprises adding a first header to the first packet data unit including the first routing information, and transmitting the second packet data unit according to the second addressing scheme comprises adding a second header to the second packet data unit including the second routing information.

[0251]

[0264] Aspect 3: The method of aspect 1 or 2, further comprising determining a first AS resource associated with a first core network service and a second AS resource associated with a second core network service, wherein transmitting a first packet data unit according to a first addressing scheme comprises transmitting the first packet data unit using the first AS resource, and transmitting a second packet data unit according to a second addressing scheme comprises transmitting the second packet data unit using the second AS resource.

[0252]

[0265] Aspect 4: The method of aspect 3, further comprising determining, at the UE, a first logical channel associated with the first AS resource and a second logical channel associated with the second AS resource.

[0253]

[0266] Example 5: The method of example 3 or example 4, further comprising receiving control information from the DU over the wireless connection, the control information indicating the first AS resource and the second AS resource.

[0254]

[0267] Aspect 6: A method as described in any of Aspects 1 to 5, further comprising receiving control information from a proxy service via a wireless connection indicating a first service identifier associated with a first core network service and a second service identifier associated with a second core network service, wherein transmitting the first packet data unit according to the first addressing scheme comprises transmitting an indication of the first service identifier with the first packet data unit, and transmitting the second packet data unit according to the second addressing scheme comprises transmitting an indication of the second service identifier with the second packet data unit.

[0255]

[0268] Aspect 7: The method of aspect 6, further comprising receiving, along with the control information, an indication of AS resources associated with the proxy service, wherein transmitting the first packet data unit according to the first addressing scheme comprises transmitting the first packet data unit using the AS resources, and transmitting the second packet data unit according to the second addressing scheme comprises transmitting the second packet data unit using the AS resources.

[0256]

[0269] Example 8: The method of example 7, further comprising determining, at the UE, a logical channel associated with the AS resource.

[0257]

[0270] Aspect 9: The method of any of Aspects 1 to 8, further including: receiving a third packet data unit via a wireless connection; determining that the third packet data unit is associated with a first core network service based on first routing information included in a first header of the third packet data unit; and processing the third packet data unit in accordance with a first protocol associated with the first core network service.

[0258]

[0271] Aspect 10: A method according to any one of aspects 1 to 9, further comprising: receiving control information from a proxy service via a wireless connection indicating a first service identifier associated with a first core network service; receiving a third packet data unit via the wireless connection; determining that the third packet data unit is associated with the first core network service based on the first service identifier being included in a first header of the third packet data unit; and processing the third packet data unit according to a first protocol associated with the first core network service.

[0259]

[0272] Aspect 11: The method of any of Aspects 1 to 10, wherein the first core network service is associated with a first application programming interface, and the second core network service is associated with a second application programming interface.

[0260]

[0273] Aspect 12: A method according to any one of aspects 1 to 11, wherein the first core network service and the second core network service each include one of a mobility service, a connection state management service, a security service, a paging service, a wireless access service, a data service, a capability management service, a location service, or a messaging service.

[0261]

[0274] Aspect 13: A method for wireless communication in a DU, the method including: receiving from a UE a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU, the first packet data unit being received according to a first addressing scheme associated with the first core network service; routing the first packet data unit to the first core network service based on the first addressing scheme; receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service; and routing the second packet data unit to the second core network service based on the second addressing scheme.

[0262]

[0275] Aspect 14: The method of aspect 13, further comprising: determining, based on first routing information included in a first header of the first packet data unit, that a first core network service is associated with the first packet data unit; and determining, based on second routing information included in a second header of the second packet data unit, that a second core network service is associated with the second packet data unit. The method of aspect 13, further comprising: determining, based on first routing information included in a first header of the first packet data unit, that a second core network service is associated with the second packet data unit. wherein: routing the first packet data unit to the first core network service based on the first addressing scheme includes routing the first packet data unit based on the first routing information; and routing the second packet data unit to the second core network service based on the second addressing scheme includes routing the second packet data unit based on the second routing information.

[0263]

[0276] Aspect 15: The method of aspect 13 or 14, further comprising determining that the UE is authorized to communicate with the first core network service, wherein routing the first packet data unit to the first core network service is based on a determination that the UE is authorized to communicate with the first core network service.

[0264]

[0277] Aspect 16: The method of aspect 15, further comprising receiving control information indicating a set of network entities, including the UE, that are authorized to communicate with the first core network service, wherein the determination that the UE is authorized to communicate with the first core network service is based on the control information.

[0265]

[0278] Aspect 17: The method of any of Aspects 13 to 16, further including: receiving, from the UE, a third packet data unit associated with a third core network service of the set of core network services, the third packet data unit being received according to a third addressing scheme associated with the third core network service; determining that the UE is not authorized to communicate with the third core network service; and refraining from routing the third packet data unit to the third core network service based on the determination that the UE is not authorized to communicate with the third core network service.

[0266]

[0279] Aspect 18: The method of aspect 17, further comprising receiving control information indicating a set of network entities, excluding the UE, that are authorized to communicate with the third core network service, wherein the determination that the UE is not authorized to communicate with the third core network service is based on the control information.

[0267]

[0280] Aspect 19: The method of any of aspects 13 to 18, further comprising: receiving a third packet data unit from a first core network service, the third packet data unit including a first header indicating destination routing information; and transmitting the third packet data unit to the UE based on the destination routing information indicating the UE.

[0268]

[0281] Aspect 20: The method of aspect 19, further comprising determining downlink resources for a third packet data unit based on the destination routing information and based on the first header further indicating source routing information, wherein transmitting the third packet data unit comprises transmitting the third packet data unit using the downlink resources.

[0269]

[0282] Aspect 21: A method according to any of aspects 13 to 20, wherein routing the first packet data unit to the first core network service based on the first addressing scheme includes routing the first packet data unit to a proxy service, and routing the second packet data unit to the second core network service based on the second addressing scheme includes routing the second packet data unit to the proxy service or to a second proxy service associated with the second core network service.

[0270]

[0283] Aspect 22: The method of any of Aspects 13 to 21, wherein the first core network service is associated with a first application programming interface, and the second core network service is associated with a second application programming interface.

[0271]

[0284] Aspect 23: The method of any of aspects 13 to 22, wherein the first core network service and the second core network service each include one of a mobility service, a connection state management service, a security service, a paging service, a wireless access service, a data service, a capability management service, a location service, or a messaging service.

[0272]

[0285] Aspect 24: An apparatus for wireless communication in a UE, the apparatus including: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions executable by the processor to cause the apparatus to perform a method described in any one of aspects 1 to 12.

[0273]

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

[0274]

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

[0275]

[0288] Aspect 27: An apparatus for wireless communication in a DU, the apparatus including: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions executable by the processor to cause the apparatus to perform a method described in any one of aspects 13 to 23.

[0276]

[0289] Example 28: An apparatus for wireless communication in a DU, comprising: at least one means for performing the method according to any one of Examples 13 to 23.

[0277]

[0290] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication in a DU, the code including instructions executable by a processor to perform a method described in any of aspects 13 to 23.

[0278]

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

[0279]

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

[0280]

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

[0281]

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

[0282]

[0295] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored on or transmitted using one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0283]

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

[0284]

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

[0285]

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

[0286]

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

[0287]

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

[0288]

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

Claims

1. 1. A method of wireless communication in a user equipment (UE), comprising: establishing, via a wireless connection between the UE and the distributed unit, communication with a set of core network services provided by a service-based network configured to interface with a radio access network (RAN) associated with the distributed unit, wherein each core network service of the set of core network services is associated with a respective addressing scheme; transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service; transmitting, over the wireless connection, a second packet data unit associated with a second core network service of the set of core network services in accordance with a second addressing scheme associated with the second core network service; A method comprising:

2. 2. The method of claim 1, further comprising determining first routing information associated with the first core network service and second routing information associated with the second core network service, wherein transmitting the first packet data unit according to the first addressing scheme comprises adding a first header to the first packet data unit including the first routing information, and transmitting the second packet data unit according to the second addressing scheme comprises adding a second header to the second packet data unit including the second routing information.

3. 2. The method of claim 1, further comprising determining first access stratum resources associated with the first core network service and second access stratum resources associated with the second core network service, wherein transmitting the first packet data unit according to the first addressing scheme comprises transmitting the first packet data unit using the first access stratum resources, and transmitting the second packet data unit according to the second addressing scheme comprises transmitting the second packet data unit using the second access stratum resources.

4. 4. The method of claim 3, further comprising determining, at the UE, a first logical channel associated with the first access stratum resource and a second logical channel associated with the second access stratum resource.

5. The method of claim 3 , further comprising receiving control information from the distributed unit over the wireless connection indicating the first access stratum resource and the second access stratum resource.

6. 2. The method of claim 1, further comprising receiving control information from a proxy service over the wireless connection indicating a first service identifier associated with the first core network service and a second service identifier associated with the second core network service, wherein transmitting the first packet data unit according to the first addressing scheme comprises transmitting an indication of the first service identifier with the first packet data unit, and transmitting the second packet data unit according to the second addressing scheme comprises transmitting an indication of the second service identifier with the second packet data unit.

7. 7. The method of claim 6, further comprising receiving, along with the control information, an indication of access stratum resources associated with the proxy service, wherein transmitting the first packet data unit according to the first addressing scheme comprises transmitting the first packet data unit using the access stratum resources, and transmitting the second packet data unit according to the second addressing scheme comprises transmitting the second packet data unit using the access stratum resources.

8. receiving a third packet data unit over the wireless connection; and determining, based on first routing information included in a first header of the third packet data unit, that the third packet data unit is associated with the first core network service; processing the third packet data unit according to a first protocol associated with the first core network service; The method of claim 1 further comprising:

9. receiving control information from a proxy service over the wireless connection indicating a first service identifier associated with the first core network service; receiving a third packet data unit over the wireless connection; and determining that the third packet data unit is associated with the first core network service based on the first service identifier being included in a first header of the third packet data unit; and processing the third packet data unit according to a first protocol associated with the first core network service; The method of claim 1 further comprising:

10. The method of claim 1 , wherein the first core network service is associated with a first application programming interface and the second core network service is associated with a second application programming interface.

11. 2. The method of claim 1, wherein the first core network service and the second core network service each include one of a mobility service, a connection state management service, a security service, a paging service, a wireless access service, a data service, a capability management service, a location service, or a messaging service.

12. 1. A method for wireless communication in distributed units, comprising: receiving, from a user equipment (UE), a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a radio access network (RAN) associated with the distributed unit, the first packet data unit being received according to a first addressing scheme associated with the first core network service; Routing the first packet data unit to a first core network service based on the first addressing scheme; receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service; routing the second packet data unit to the second core network service based on the second addressing scheme; A method comprising:

13. 13. The method of claim 12, further comprising: determining, based on first routing information included in a first header of the first packet data unit, that the first core network service is associated with the first packet data unit; and determining, based on second routing information included in a second header of the second packet data unit, that the second core network service is associated with the second packet data unit.

14. The method of claim 12, further comprising: determining, based on first routing information included in a first header of the first packet data unit, that the first core network service is associated with the first packet data unit; and determining, based on second routing information included in a second header of the second packet data unit, that the second core network service is associated with the second packet data unit.

14. 13. The method of claim 12, further comprising determining that the UE is authorized to communicate with the first core network service, wherein routing the first packet data unit to the first core network service is based on the determination that the UE is authorized to communicate with the first core network service.

15. 15. The method of claim 14, further comprising receiving control information indicating a set of network entities, including the UE, that are authorized to communicate with the first core network service, wherein the determination that the UE is authorized to communicate with the first core network service is based on the control information.

16. receiving from the UE a third packet data unit associated with a third core network service of the set of core network services, the third packet data unit being received according to a third addressing scheme associated with the third core network service; determining that the UE is not authorized to communicate with the third core network service; refraining from routing the third packet data unit to the third core network service based on the determination that the UE is not authorized to communicate with the third core network service; The method of claim 12 further comprising:

17. 17. The method of claim 16, further comprising receiving control information indicating a set of network entities, excluding the UE, that are authorized to communicate with the third core network service, wherein the determination that the UE is not authorized to communicate with the third core network service is based on the control information.

18. receiving a third packet data unit from the first core network service, the third packet data unit including a first header indicating destination routing information; transmitting the third packet data unit to the UE based on the destination routing information indicating the UE; The method of claim 12 further comprising:

19. 20. The method of claim 18, further comprising determining downlink resources for the third packet data unit based on the destination routing information and based on the first header further indicating source routing information, wherein transmitting the third packet data unit comprises transmitting the third packet data unit using the downlink resources.

20. Routing the first packet data unit to the first core network service based on the first addressing scheme includes routing the first packet data unit to a proxy service; routing the second packet data unit to the second core network service based on the second addressing scheme includes routing the second packet data unit to the proxy service or to a second proxy service associated with the second core network service. The method of claim 12.

21. The method of claim 12 , wherein the first core network service is associated with a first application programming interface and the second core network service is associated with a second application programming interface.

22. 13. The method of claim 12, wherein the first core network service and the second core network service each include one of a mobility service, a connection state management service, a security service, a paging service, a radio access service, a data service, a capability management service, a location service, or a messaging service.

23. 1. An apparatus for wireless communication in a user equipment (UE), comprising: a processor; a memory coupled to the processor; and wherein the memory includes: establishing, via a wireless connection between the UE and the distributed unit, communication with a set of core network services provided by a service-based network configured to interface with a radio access network (RAN) associated with the distributed unit, wherein each core network service of the set of core network services is associated with a respective addressing scheme; transmitting, over the wireless connection, a first packet data unit associated with a first core network service of the set of core network services in accordance with a first addressing scheme associated with the first core network service; causing a second packet data unit associated with a second core network service of the set of core network services to be transmitted over the wireless connection in accordance with a second addressing scheme associated with the second core network service; and instructions executable by the processor to: Device.

24. The instructions cause the device to:

24. The apparatus of claim 23, further executable by the processor to determine first access stratum resources associated with the first core network service and second access stratum resources associated with the second core network service, wherein transmitting the first packet data unit according to the first addressing scheme comprises transmitting the first packet data unit using the first access stratum resources, and transmitting the second packet data unit according to the second addressing scheme comprises transmitting the second packet data unit using the second access stratum resources.

25. The instructions cause the device to:

25. The apparatus of claim 24, further executable by the processor to receive control information from the distributed unit over the wireless connection, the control information indicating the first access stratum resource and the second access stratum resource.

26. The instructions cause the device to:

24. The apparatus of claim 23, further executable by the processor to cause control information indicating a first service identifier associated with the first core network service and a second service identifier associated with the second core network service to be received from a proxy service over the wireless connection, wherein transmitting the first packet data unit according to the first addressing scheme includes transmitting an indication of the first service identifier with the first packet data unit, and transmitting the second packet data unit according to the second addressing scheme includes transmitting an indication of the second service identifier with the second packet data unit.

27. 1. An apparatus for wireless communication in distributed units, comprising: a processor; a memory coupled to the processor; and wherein the memory includes: receiving, from a user equipment (UE), a first packet data unit associated with a first core network service of a set of core network services provided by a service-based network configured to interface with a radio access network (RAN) associated with the distributed unit, the first packet data unit being received according to a first addressing scheme associated with the first core network service; routing the first packet data unit to the first core network service based on the first addressing scheme; receiving from the UE a second packet data unit associated with a second core network service of the set of core network services, the second packet data unit being received according to a second addressing scheme associated with the second core network service; routing the second packet data unit to the second core network service based on the second addressing scheme; and instructions executable by the processor to: Device.

28. The instructions cause the device to:

28. The apparatus of claim 27, further executable by the processor to determine that the UE is authorized to communicate with the first core network service, and routing the first packet data unit to the first core network service is based on the determination that the UE is authorized to communicate with the first core network service.

29. The instructions cause the device to:

29. The apparatus of claim 28, further executable by the processor to receive control information indicating a set of network entities, including the UE, that are authorized to communicate with the first core network service, wherein the determination that the UE is authorized to communicate with the first core network service is based on the control information.

30. Routing the first packet data unit to the first core network service based on the first addressing scheme includes routing the first packet data unit to a proxy service; routing the second packet data unit to the second core network service based on the second addressing scheme includes routing the second packet data unit to the proxy service or to a second proxy service associated with the second core network service.

28. The method of claim 27.

Images