Addressability in service-based wireless system

Abstract

Methods, systems, and devices for wireless communication 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 on a per core network service basis. 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 layer (AS) resources on which an uplink packet data unit is to be transmitted based on a target core network service. The UE may receive control signaling from a distributed unit, a system information block (SIB), or peer-to-peer signaling from a core network service, the peer-to-peer signaling indicating a particular AS resource for each core network service. The UE may select a logical channel for transmitting uplink packet data units to a particular core network service based on AS resources associated with each service.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 948,060, entitled “ADDRESSABILITY IN A SERVICE-BASED WIRELESS SYSTEM,” filed by GRIOT et al. on September 19, 2022, which is assigned to the assignee of this application and the entire contents of which are expressly incorporated herein by reference. Technical Field

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

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

[0005] The described technology relates to improved methods, systems, devices and apparatus for supporting addressability in service-based wireless systems. For example, the described technology provides routing of information (e.g., packet data units) between user equipment (UE) and core network services provided by a service-based network. An end-to-end routing layer can address packets between UE and multiple core network services on a per-core network service basis. The UE can communicate with the core network service directly (e.g., based on a network address associated with the core network service) or indirectly (e.g., by proxy service routing communication). In both direct and indirect cases, the UE can select an access stratum (AS) resource (e.g., AS resource block) on which an uplink packet data unit is to be sent based on a target core network service. For example, the UE can receive control signaling from a distributed unit (DU), a system information block (SIB), or point-to-point signaling from a core network service indicating a specific AS resource for each core network service. The UE can also select a logical channel for sending an uplink packet data unit to a specific core network service based on the AS resource associated with each core network service.

[0006] A method for wireless communication at 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 via a wireless connection between the UE and the DU, each core network service in the set of core network services being associated with a corresponding addressing scheme; sending a first packet data unit associated with a first core network service in the set of core network services according to a first addressing scheme associated with the first core network service via the wireless connection; and sending a second packet data unit associated with a second core network service in the set of core network services according to a second addressing scheme associated with the second core network service via the wireless connection.

[0007] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to perform the following operations: 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 via a wireless connection between the UE and the DU, each core network service in the set of core network services being associated with a corresponding addressing scheme; send a first packet data unit associated with a first core network service in the set of core network services via the wireless connection according to a first addressing scheme associated with the first core network service; and send a second packet data unit associated with a second core network service in the set of core network services via the wireless connection according to a second addressing scheme associated with the second core network service in the set of core network services.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for 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 via a wireless connection between the UE and the DU, each core network service in the set of core network services being associated with a corresponding addressing scheme; a unit for sending a first packet data unit associated with a first core network service in the set of core network services according to a first addressing scheme associated with the first core network service via the wireless connection; and a unit for sending a second packet data unit associated with a second core network service in the set of core network services according to a second addressing scheme associated with the second core network service via the wireless connection.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: 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 via a wireless connection between the UE and the DU, each core network service in the set of core network services being associated with a corresponding addressing scheme; send a first packet data unit associated with a first core network service in the set of core network services via the wireless connection according to a first addressing scheme associated with the first core network service; and send a second packet data unit associated with a second core network service in the set of core network services via the wireless connection according to a second addressing scheme associated with the second core network service.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining first routing information associated with the first core network service and second routing information associated with the second core network service, wherein sending the first packet data unit according to the first addressing scheme includes: appending a first header including the first routing information to the first packet data unit, and wherein sending the second packet data unit according to the second addressing scheme includes: appending a second header including the second routing information to the second packet data unit.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining a first AS resource associated with the first core network service and a second AS resource associated with the second core network service, wherein sending the first packet data unit according to the first addressing scheme includes: sending the first packet data unit using the first AS resource, and wherein sending the second packet data unit according to the second addressing scheme includes: sending the second packet data unit using the second AS resource.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for 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.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving control information indicating the first AS resource and the second AS resource from the DU via the wireless connection.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving control information from a proxy service via the wireless connection, the 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, wherein sending the first packet data unit according to the first addressing scheme includes: sending an indication of the first service identifier together with the first packet data unit, and wherein sending the second packet data unit according to the second addressing scheme includes: sending an indication of the second service identifier together with the second packet data unit.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving an indication of an AS resource associated with the proxy service together with the control information, wherein sending the first packet data unit according to the first addressing scheme includes: sending the first packet data unit using the AS resource, and wherein sending the second packet data unit according to the second addressing scheme includes: sending the second packet data unit using the AS resource.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for determining, at the UE, a logical channel associated with the AS resources.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a third packet data unit via the wireless connection; determining that the third packet data unit can be associated with the 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 according to a first protocol associated with the first core network service.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving control information indicating a first service identifier associated with the first core network service from a proxy service via the wireless connection; receiving a third packet data unit via the wireless connection; determining that the third packet data unit can 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 according to a first protocol associated with the first core network service.

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

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first core network service and the second core network service each include one of: mobility service, connection state management service, security service, paging service, radio access service, data service, capability management service, location service, or messaging service.

[0021] A method for wireless communication at a DU is described. The method may include: receiving a first packet data unit associated with a first core network service in a set of core network services from a UE, the set of core network services being provided by a service-based network configured to interface with a RAN associated with the DU, wherein the first packet data unit is 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 a second packet data unit associated with a second core network service in the set of core network services from the UE, wherein the second packet data unit is 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.

[0022] An apparatus for wireless communication at a DU is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receiving a first packet data unit associated with a first core network service in a set of core network services from a UE, the set of core network services being provided by a service-based network configured to interface with a RAN associated with the DU, wherein the first packet data unit is 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 a second packet data unit associated with a second core network service in the set of core network services from the UE, wherein the second packet data unit is 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.

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

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

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining that the first core network service can be associated with the first packet data unit based on first routing information included in a first header of the first packet data unit, and determining that the second core network service can be associated with the second packet data unit based on second routing information included in a second header of 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 wherein 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.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining that the UE can be authorized to communicate with the first core network service, wherein routing the first packet data unit to the first core network service can be based on the determination that the UE can be authorized to communicate with the first core network service.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving control information indicating a set of network entities authorized to communicate with the first core network service, wherein the set of network entities includes the UE, and wherein the determination that the UE can be authorized to communicate with the first core network service can be based on the control information.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a third packet data unit associated with a third core network service in the set of core network services from the UE, wherein the third packet data unit may be received according to a third addressing scheme associated with the third core network service; determining that the UE may not be authorized to communicate with the third core network service; and avoiding routing the third packet data unit to the third core network service based on the determination that the UE may not be authorized to communicate with the third core network service.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving control information indicating a set of network entities authorized to communicate with the third core network service, the set of network entities excluding the UE, and wherein the determination that the UE may not be authorized to communicate with the third core network service may be based on the control information.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a third packet data unit including a first header indicating destination routing information from the first core network service; and sending the third packet data unit to the UE based on the destination routing information indicating the UE.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining downlink resources for the third packet data unit based on the destination routing information and based on the first header also indicating source routing information, wherein sending the third packet data unit includes: using the downlink resources to send the third packet data unit.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: 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.

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

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first core network service and the second core network service each include one of: mobility service, connection state management service, security service, paging service, radio access service, data service, capability management service, location service, or messaging service. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0038] Figure 4 An example of a signaling diagram supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

[0039] Figure 5 An example of a signaling diagram supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown.

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

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

[0042] Figure 8 and 9 A block diagram of a device supporting addressability in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0043] Fig.10 A block diagram of a communications manager supporting addressability in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0044] Fig.11 A diagram of a system including a device supporting addressability in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0045] Fig.12 and 13 A block diagram of a device supporting addressability in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0046] Fig.14A block diagram of a communications manager supporting addressability in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

[0047] Fig.15 A diagram of a system including a device supporting addressability in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure.

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

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

[0050] In contrast, some wireless systems (such as sixth generation (6G) systems) may exhibit a flatter service-based architecture, in which a radio access network (RAN) (e.g., a network entity) interfaces with a service-based network to connect UEs to core network services maintained at various network addresses within the service-based network. In the context of a service-based system, operations and functions that might otherwise be performed by a few centralized backend components (e.g., in some systems) may be distributed across multiple core network services that may be hosted at different network addresses, such as in a cloud-based architecture. Thus, a UE in a service-based system is able to establish and maintain connections with different core network services or groups thereof (e.g., "subscribe" to different core network services or groups thereof) on an a la carte basis, where each core network service supplies or provides a corresponding network function or service. For example, a service-based system may include mobility services, security services, privacy services, location services, etc. In this regard, each UE within a service-based system is able to select which core network services the UE will subscribe to based on the personalized characteristics or needs of the corresponding UE.

[0051] Aspects of the present disclosure relate to routing of information between a UE and a core network service provided by a service-based network. An end-to-end routing layer may address packets between a UE and multiple core network services on a per-core network service basis. 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., by routing communications through a proxy service). In direct communications, for uplink communications, the UE may send a packet data unit including routing information for the core network service to the core network service via a distributed unit (DU). In indirect communications, 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 direct and indirect cases, the UE may select an access stratum (AS) resource (e.g., an AS resource block) on which an uplink packet data unit is to be sent based on a 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 sending uplink packet data units to a particular core network service based on the AS resources associated with each core network service.

[0052] For 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 the local UE context (e.g., UE identifier) ​​created by the DU. For indirect downlink transmission, the DU may receive a downlink packet data unit including a destination address and a service identifier from the proxy service. The UE may identify the source core network service used in the downlink packet data unit based on the source information in the header of the packet data unit (e.g., the network address in direct communication or the 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.

[0053] Aspects of the present disclosure are first 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, device diagrams, system diagrams, and flow charts relating to addressability in a service-based wireless system.

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

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

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

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

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

[0059] 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 via 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 at the UE 115. The services at the UE 115 may correspond to one or more CN / RAN services 185 at the service platform 150. For example, the network service API 180 at the service-based network 130 may interface with a corresponding DU service API 175 at the DU 165, which interfaces with a corresponding API at the UE 115 to provide service connectivity between 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. Based on authorization, the CN / RAN services 185 may be restricted to be available only to the UE 115 or only to other network services.

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

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

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

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

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

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

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

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

[0068] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling to coordinate operations for other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel grid for discovery by a UE 115. A carrier may operate in a standalone mode, in which case a UE 115 may perform initial acquisition and connection via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0087] The wireless communication system 100 may also operate using a super high frequency (SHF) region that may be in the range of from 3 GHz to 30 GHz (also referred to as a centimeter band) or an extremely high frequency (EHF) region (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band) using a spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and a network entity (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and more closely spaced than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may suffer from even greater attenuation and shorter distances than SHF or UHF transmissions. The technology disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may differ according to the country or regulatory agency.

[0088] The wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating using unlicensed RF spectrum bands, devices (such as network entities 105 and UE 115) can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on a carrier aggregation configuration of component carriers in combination with operations using licensed bands (e.g., LAA). Operations using unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, as well as other examples.

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

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

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

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

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

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

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

[0096] In some examples, the wireless communication system 100 may include a packet-based network that operates using a cloud platform, such as a service platform 150 that provides CN / RAN services 185. In some examples, the CN / RAN services 185 may be hosted based on a deployment topology and capabilities for service parameters associated with each service. Providing the CN / RAN services 185 allows for separation of specific services (e.g., mobility, connection state management, security, paging, radio access services, quality of service (QoS) configuration and data services, UE capability management, location, messaging, etc.) from transport functions (e.g., data radio bearer (DRB) and logical channel (LC) management, data service configuration, etc.). Service-based functions (e.g., message brokers decouple radio network processes from network delivery mechanisms) may allow flexibility for 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 independently scaled by independently increasing or decreasing resources allocated across each function). Furthermore, efficiency may be enhanced by providing real-time link management to the RAN edge and allowing adaptation at the DU 165 to more efficiently activate, deactivate, or select features based on UE conditions.

[0097] Figure 2 An example of a wireless communication system that supports addressability in a service-based wireless system according to one or more aspects of the present disclosure is shown. Aspects of the wireless communication system 200 may implement aspects of the wireless communication system 100 or be implemented by aspects of the wireless communication system 100. In some implementations, the wireless communication system 200 illustrates a service-based wireless communication system (such as referring to Figure 1 An example architecture of the system described herein.

[0098] The wireless communication system 200 may include one or more UEs 115 (e.g., UE 115-a), one or more network entities (e.g., network entity 105-a), and a service-based network 205. In some aspects, the service-based network 205 may be configured to communicate or interface with a RAN 210 of the wireless communication system 200, wherein the RAN 210 includes one or more network entities (e.g., network entity 105-a). The service-based network 205 may support or provide a set of core network services 215 (e.g., 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 a cloud platform or be associated with a cloud platform, wherein the corresponding core network service 215 is hosted at a corresponding network address in the cloud platform.

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

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

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

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

[0103] The service-based network 205 may provide subscription 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). 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) related to a given UE (e.g., UE 115-a). If UE 115-a is authorized, the subscription and / or policy service 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.

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

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

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

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

[0108] In this regard, the wireless communication system 200 may illustrate an example of a cloud-native platform configured to host a merge 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 fusion of RAN 210 and CN functions may reduce duplicated operations and functions for serving one UE at different layers.

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

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

[0111] The end-to-end routing layer may address packets between the UE 115-a and the core network services 215 on a per 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. UE 115-a may communicate with core network service 215 directly (e.g., based on a network address associated with core network service 215 (e.g., an IP address, a transmission control protocol (TCP) port, or a hypertext transfer protocol (HTTP) port)) or indirectly (e.g., by routing the communication through a proxy service). In direct communication, for uplink communication, UE 115-a may send a packet data unit to core network service 215 via network entity 105-a, the packet data unit including routing information for core network service 215. In indirect communication, UE 115-a may send a packet data unit including a service identifier for core network service 215 to the proxy service via network entity 105-a, and the proxy service may route the packet data unit to core network service 215 based on the service identifier. For example, the proxy service may be core network service 215. In both direct and indirect cases, UE 115-a may select an AS resource (e.g., an AS resource block) on which to send the uplink packet data unit based on the target core network service. For example, UE 115-a may select an AS resource (e.g., an AS resource block) on which to send the uplink packet data unit based on the target core network service. 115-a can receive control signaling, SIB, or point-to-point signaling from the core network service from the network entity 105-a (the point-to-point signaling indicates the specific AS resources used for each core network service). UE 115-a can also select a logical channel for sending uplink packet data units to a specific core network service based on the AS resources associated with each core network service.

[0112] For 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 the local UE 115-a context (e.g., the UE 115-a identifier) ​​created by the network entity 105-a. For indirect downlink transmission, the network entity 105-a may receive a downlink packet data unit including the destination address and the service identifier from the proxy service. The UE 115-a may identify the source core network service 215 used in the downlink packet data unit based on the source information in the header of the packet data unit (e.g., the network address in direct communication or the 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.

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

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

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

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

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

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

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

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

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

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

[0123] 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 core network service 215-f, for example, via discovery information received from the network through DU 165-b. UE 115-c may send packet data units 410 to core network service 215-f via end-to-end routing layer 425-a and service protocol layer 430-a. Service protocol layer 430-a may be transparent to DU 165-b and may be specific to core network service 215-f (e.g., each core network service 215 may be associated with a corresponding service protocol layer for communication with UE 115-c). Core network service 215-f may send packet data units 415 to UE 115-c via end-to-end routing layer 425-b and service protocol layer 430-b.

[0124] For example, when sending a packet data unit 410, the UE 115-c may generate a packet data unit (e.g., including data within the service protocol layer 430-a). The UE 115-c may mark 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 a 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 bundle the packet data unit 410 to an AS resource for the communication link 220-a based on the core network service 215-f. For example, the UE 115-c may select an AS resource for transmitting the packet data unit 410 via the AS layer 420-a. For example, the UE 115-c may select an AS resource based on a configuration received from the DU 165-b indicating an AS resource associated with the core network service 215-f. In some examples, the SIB may indicate a configuration indicating an association between an AS resource and a particular core network service. In some examples, the UE 115-c may select an AS resource based on dedicated signaling from the core network service 215-f. The UE 115-c may also select a logical channel for transmitting a packet data unit 410 based on the AS resource. In some examples, the UE 115-c may add one (or more) link level (e.g., MAC or radio link control (RLC)) headers to the packet data unit 410 based on a local configuration received from the DU 165-b.

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

[0126] For the downlink, the core network service 215-f may tag the packet data unit 415 (e.g., via a header) with a service tag (e.g., a tag indicating the core network service 215-f or 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 data for transmission to the UE 115-c.

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

[0128] Upon reception, 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 sent 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.

[0129] Figure 5 An example of a signaling diagram 500 for supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure is shown. Aspects of the signaling diagram 500 may implement or be implemented by aspects of the wireless communication system 100 or the wireless communication system 200. For example, the signaling diagram includes a UE 115-d, a DU 165-c, and a core network service 215-g, which may be examples of corresponding devices described herein.

[0130] Example 505-a illustrates an example of an indirect direct uplink packet transmission between UE 115-d and core network service 215-g. Example 505-b illustrates an example of an indirect downlink packet transmission 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 can communicate via proxy service 510. UE 115-d can communicate with DU 165-c using communication link 220-b, which can be an example of communication link 220 as described herein. Similarly, DU 165-c can be configured to communicate (e.g., dock) with proxy service 510 via communication link 225-b, which can be an example of communication link 225 as described herein. Proxy service 510 can communicate with core network service 215-f via communication link 525, which can be, for example, a network link (e.g., an IP link). Using the proxy service 510 may hide the core network service topology from the UE 115 - d .

[0131] UE 115-d may discover routing information for core network service 215-g (e.g., a service identifier for core network service 215). For example, UE 115-d may establish a proxy session with proxy service 510. Proxy service 510 may map a local service identifier to routing information for 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 UE 115-d. In some cases, proxy service 510 may provide service discovery (e.g., discovery of different core network services and capabilities of the core network services) to UE 115-d. Proxy service 510 may or may not be co-located with DU 165-c.

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

[0133] For example, when sending a packet data unit 410-a, the UE 115-d may generate a packet data unit 410-a (e.g., including data within a service protocol layer 430-c). The UE 115-d may mark 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 a 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 bundle the packet data unit 410-a to an AS resource for the communication link 220-a based on the core network service 215-g. For example, the UE 115-d may select an AS resource for transmitting the packet data unit 410-a via the AS layer 420-c. For example, UE 115-d may select AS resources based on a configuration of AS resources associated with core network service 215-g received from DU 165-c. In some examples, the SIB may indicate a configuration indicating an association between an AS resource and a specific core network service. In some examples, UE 115-d may select AS resources based on dedicated signaling from core network service 215-g (e.g., via proxy service 510). UE 115-d may also select a logical channel for transmitting packet data unit 410-a based on AS resources. In some examples, UE 115-d may add one (or more) link level (e.g., MAC or RLC) headers to packet data unit 410-a based on a local configuration received from DU 165-c.

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

[0135] 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 the source proxy address information and the destination service address (e.g., the network address for the core network service 215-g).

[0136] For the downlink, the core network service 215-g may tag the packet data unit 415-a (e.g., via a header) 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.

[0137] 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, which includes the service identifier. For example, the proxy service 510 may map the service address in the routing layer 520-b to the service identifier for the core network service 215-g.

[0138] DU 165-c may route packet data unit 415-a to UE 115-d based on the service identifier in proxy layer 515-b. Routing of packet data unit 415-a at DU 165-c may be transparent to DU 165-c. DU 165-c may bundle packet data unit 415-a to AS resources for communication link 220-a based on UE 115-d and / or core network services 215-g. DU 165-c may receive packet data unit 415-a including proxy layer 515-b (e.g., header) including identifier. DU 165-c may determine a local identifier for UE 115-d based on the service identifier and a local UE context created by DU 165-c for communication between DU 165-c and UE 115-d. The DU 165-c may determine the local downlink resource configuration (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 transmitting the packet data unit 415-a via the AS layer 420-d. The DU 165-c may schedule the transmission of the packet data unit 415-a based on the resource configuration and requirements and send the packet data unit 415-a. The packet data unit 415-a sent from the DU 165-c to the UE 115-d may include the packet data unit 415-a received from the proxy service plus a local access header (e.g., a MAC or RLC header).

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

[0140] Figure 6An example of a process flow 600 for supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure is shown. The process flow 600 may include a UE 115-e, which may be an example of a UE 115 as described herein. The process flow 600 may include a DU 165-d, which may be an example of a DU 165 as 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 as described herein. In the following description of the process flow 600, operations between the UE 115-e, the DU 165-d, the first core network service 215-h, and the second core network service 215-i may be sent in a different order than the example order shown, and operations performed by the UE 115-e, the DU 165-d, the first core network service 215-h, and the 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 the process flow 600 , and other operations may be added to the process flow 600 .

[0141] At 605, 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 DU 165-d via a wireless connection between UE 115-e and DU 165-d, each core network service in the set of core network services being associated with a corresponding addressing scheme. The set of core network services includes a first core network service 215-h and a second core network service 215-i.

[0142] At 610, the UE 115-e may send, via a wireless connection, a first packet data unit associated with the first core network service 215-h according to a first addressing scheme associated with the first core network service 215-h.

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

[0144] At 620 , the UE 115 - e may send, via the wireless connection, a second packet data unit associated with the second core network service 215 - i in accordance with a second addressing scheme associated with the second core network service 215 - i .

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

[0146] In some examples, UE 115-e can 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. Sending the first packet data unit according to the first addressing scheme at 610 can include: appending a first header including the first routing information to the first packet data unit, and sending the second packet data unit according to the second addressing scheme at 620 can include: appending a second header including the second routing information to the second packet data unit.

[0147] 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. Sending the first packet data unit according to the first addressing scheme at 610 may include sending the first packet data unit using the first AS resource, and sending the second packet data unit according to the second addressing scheme at 620 may include sending 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 indicating the first AS resource and the second AS resource from the DU 165-d.

[0148] In some cases, DU 165-d may determine that 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 determine that 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. Routing the first packet data unit to the first core network service based on the first addressing scheme at 615 may include 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 at 625 may include routing the second packet data unit based on the second routing information.

[0149] In some cases, DU 165-d may determine that UE 115-e is authorized to communicate with 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 UE 115-e is authorized to communicate with first core network service 215-h. In some cases, DU 165-d may receive control information indicating a set of network entities authorized to communicate with first core network service 215-h, wherein the set of network entities includes UE 115-e. The determination that UE 115-e is authorized to communicate with first core network service 215-h may be based on the control information.

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

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

[0152] At 635, DU 165-d may send a third packet data unit to UE 115-e based on the destination routing information indicating UE 115-e as the destination. In some cases, DU 165-d may determine downlink resources for the third packet data unit based on the destination routing information and based on the report also indicating source routing information, wherein sending the third packet data unit includes: using the downlink resources to send the third packet data unit.

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

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

[0155] Figure 7 An example of a process flow 700 for supporting addressability in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. The process flow 700 may include a UE 115-f, which may be an example of a UE 115 as described herein. The process flow 700 may include a DU 165-e, which may be an example of a DU 165 as described herein. The process flow 700 may include a proxy service 510-a, which may be an example of a proxy service 510 as 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 as described herein. In the following description of process flow 700, 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 sent in a different order than the example order shown, and 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 a different time. Some operations may also be omitted from process flow 700, and other operations may be added to process flow 700.

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

[0157] At 710, the UE 115-f may send, via a wireless connection, a first packet data unit associated with the first core network service 215-j according to a first addressing scheme associated with the first core network service 215-j. Sending the first packet data unit according to the first addressing scheme includes sending, with the first packet data unit, an indication of a first service identifier associated with the first core network service 215-j.

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

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

[0160] At 725, the UE 115-f may send, via the wireless connection, a second packet data unit associated with the second core network service 215-k according to a second addressing scheme associated with the second core network service 215-k. Sending the second packet data unit according to the second addressing scheme includes sending, with the second packet data unit, an indication of a second service identifier associated with the second core network service 215-k.

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

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

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

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

[0165] Based on the source information and the destination information, at 745, the proxy service 510-a may route to the DU 165-e, and the DU 165-e may 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., 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.

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

[0167] At 755, 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. UE 115-f may process the third packet data unit according to a protocol associated with the first core network service 215-j.

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

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

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

[0171] 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 related to addressability in a service-based wireless system, data channels, information channels). In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

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

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

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

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

[0176] According to the examples disclosed herein, the communication manager 820 can support wireless communication at the UE. For example, the communication manager 820 can be configured to or otherwise support a unit for 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 via a wireless connection between the UE and the DU, each core network service in the set of core network services being associated with a corresponding addressing scheme. The communication manager 820 can be configured to or otherwise support a unit for sending a first packet data unit associated with a first core network service in the set of core network services according to a first addressing scheme associated with a first core network service in the set of core network services via a wireless connection. The communication manager 820 can be configured to or otherwise support a unit for sending a second packet data unit associated with a second core network service in the set of core network services according to a second addressing scheme associated with a second core network service in the set of core network services via a wireless connection.

[0177] By including or configuring the communication manager 820 according to examples as described herein, the device 805 (e.g., a processor for controlling the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof, or otherwise coupled to the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources.

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

[0179] 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 related to addressability in a service-based wireless system, data channels, information channels). The information may be communicated to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

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

[0181] The device 905 or its various components may be examples of units for performing various aspects of addressability in a service-based wireless system as described herein. For example, the communication manager 920 may include a service-based network communication manager 925, an uplink addressing scheme manager 930, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using the receiver 910, the transmitter 915, or both or otherwise cooperate with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0182] According to the examples disclosed herein, the communication manager 920 can support wireless communication at the UE. The service-based network communication manager 925 can be configured to or otherwise support a unit for 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 via a wireless connection between the UE and the DU, each core network service in the core network service set being associated with a corresponding addressing scheme. The uplink addressing scheme manager 930 can be configured to or otherwise support a unit for sending a first packet data unit associated with a first core network service in the core network service set according to a first addressing scheme associated with a first core network service in the core network service set via a wireless connection. The uplink addressing scheme manager 930 can be configured to or otherwise support a unit for sending a second packet data unit associated with a second core network service in the core network service set according to a second addressing scheme associated with a second core network service in the core network service set via a wireless connection.

[0183] Fig.10 A block diagram 1000 of a communication manager 1020 supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of units for performing various aspects of addressability in a service-based wireless system as described herein. For example, the communication manager 1020 may include a service-based network communication 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 with each other directly or indirectly (e.g., via one or more buses).

[0184] According to the examples disclosed herein, the communication manager 1020 can support wireless communication at the UE. The service-based network communication manager 1025 can be configured to or otherwise support a unit for 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 via a wireless connection between the UE and the DU, each core network service in the set of core network services being associated with a corresponding addressing scheme. The uplink addressing scheme manager 1030 can be configured to or otherwise support a unit for sending a first packet data unit associated with a first core network service in the set of core network services according to a first addressing scheme associated with a first core network service in the set of core network services via a wireless connection. In some examples, the uplink addressing scheme manager 1030 can be configured to or otherwise support a unit for sending a second packet data unit associated with a second core network service in the set of core network services according to a second addressing scheme associated with a second core network service in the set of core network services via a wireless connection.

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

[0186] In some examples, the AS resource manager 1040 can be configured as or otherwise support a unit 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 sending a first packet data unit according to a first addressing scheme includes: sending the first packet data unit using the first AS resource, and wherein sending a second packet data unit according to a second addressing scheme includes: sending the second packet data unit using the second AS resource.

[0187] In some examples, the logical channel manager 1065 may be configured or otherwise support 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.

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

[0189] In some examples, the service identifier manager 1045 can be configured as or otherwise support a unit for receiving control information from a proxy service via a wireless connection, the control information 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 sending a first packet data unit according to a first addressing scheme includes: sending an indication of the first service identifier together with the first packet data unit, and wherein sending a second packet data unit according to a second addressing scheme includes: sending an indication of the second service identifier together with the second packet data unit.

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

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

[0192] In some examples, downlink packet manager 1050 may be configured to or otherwise support means for receiving a third packet data unit via a wireless connection. In some examples, downlink source manager 1055 may be configured to or otherwise support 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, core network service protocol manager 1060 may be configured to or otherwise support means for processing the third packet data unit according to a first protocol associated with the first core network service.

[0193] In some examples, the service identifier manager 1045 may be configured as or otherwise support means for receiving control information indicating a first service identifier associated with a first core network service from a proxy service via a wireless connection. In some examples, the downlink packet manager 1050 may be configured as or otherwise support means for receiving a third packet data unit via a wireless connection. In some examples, the downlink source manager 1055 may be configured as or otherwise support means for 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. In some examples, the core network service protocol manager 1060 may be configured as or otherwise support means for processing the third packet data unit according to a first protocol associated with the first core network service.

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

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

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

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

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

[0199] 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, which includes 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 cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition, the memory 1130 may also contain a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

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

[0201] According to the examples disclosed herein, the communication manager 1120 can support wireless communication at the UE. For example, the communication manager 1120 can be configured to or otherwise support a unit for 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 via a wireless connection between the UE and the DU, each core network service in the set of core network services being associated with a corresponding addressing scheme. The communication manager 1120 can be configured to or otherwise support a unit for sending a first packet data unit associated with a first core network service in the set of core network services according to a first addressing scheme associated with a first core network service in the set of core network services via a wireless connection. The communication manager 1120 can be configured to or otherwise support a unit for sending a second packet data unit associated with a second core network service in the set of core network services according to a second addressing scheme associated with a second core network service in the set of core network services via a wireless connection.

[0202] By including or configuring the communication manager 1120 according to examples as described herein, the device 1105 can support techniques for improving communication reliability, reducing latency, improving user experience related to reduced processing, reducing power consumption, more efficiently utilizing communication resources, improving coordination between devices, and improving utilization of processing capabilities.

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

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

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

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

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

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

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

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

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

[0212] By including or configuring the communication manager 1220 according to the examples described herein, the device 1205 (e.g., a processor for controlling or otherwise coupling the receiver 1210, the transmitter 1215, the communication manager 1220, or a combination thereof) can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources.

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

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

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

[0216] Device 1305 or its various components may be examples of units for performing various aspects of addressability in a service-based wireless system as described herein. For example, communication manager 1320 may include uplink addressing scheme manager 1325, core network service routing manager 1330, or any combination thereof. Communication manager 1320 may be an example of various aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using receiver 1310, transmitter 1315, or both or otherwise in cooperation with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 may receive information from receiver 1310, send information to transmitter 1315, or integrate with receiver 1310, transmitter 1315, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0217] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at the DU. The uplink addressing scheme manager 1325 may be configured to or otherwise support a unit for receiving a first packet data unit associated with a first core network service in a core network service set from a UE, the core network service set being provided by a service-based network configured to interface with a RAN associated with the DU, wherein the first packet data unit is received according to a first addressing scheme associated with the first core network service. The core network service routing manager 1330 may be configured to or otherwise support a unit 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 to or otherwise support a unit for receiving a second packet data unit associated with a second core network service in a core network service set from a UE, wherein the second packet data unit is received according to a second addressing scheme associated with the second core network service. The core network service routing manager 1330 may be configured to or otherwise support a unit for routing the second packet data unit to the second core network service based on the second addressing scheme.

[0218] Fig.14 A block diagram 1400 of a communication manager 1420 supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of units for performing various aspects of addressability in a service-based wireless system as described herein. For example, the communication 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 with each other directly or indirectly (e.g., via one or more buses).

[0219] According to the examples disclosed herein, the communication manager 1420 may support wireless communications at the DU. The uplink addressing scheme manager 1425 may be configured to or otherwise support a unit for receiving a first packet data unit associated with a first core network service in a core network service set from a UE, the core network service set being provided by a service-based network configured to interface with a RAN associated with the DU, wherein the first packet data unit is received according to a first addressing scheme associated with the first core network service. The core network service routing manager 1430 may be configured to or otherwise support a unit 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 to or otherwise support a unit for receiving a second packet data unit associated with a second core network service in a core network service set from a UE, wherein the second packet data unit is received according to a second addressing scheme associated with the second core network service. In some examples, core network service routing manager 1430 may be configured or otherwise support means for routing the second packet data unit to the second core network service based on the second addressing scheme.

[0220] In some examples, the uplink routing information manager 1435 can be configured to or otherwise support determining that a first core network service is associated with a first packet data unit based on first routing information included in a first header of the first packet data unit, and determining that a second core network service is associated with a second packet data unit based on second routing information included in a second header of 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 wherein 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.

[0221] In some examples, UE authorization manager 1440 can be configured as or otherwise support a unit for determining that the UE is authorized to communicate with a 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.

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

[0223] In some examples, uplink addressing scheme manager 1425 may be configured to or otherwise support a unit for receiving, from a UE, a third packet data unit associated with a third core network service in a set of core network services, wherein the third packet data unit is received according to a third addressing scheme associated with the third core network service. In some examples, UE authorization manager 1440 may be configured to or otherwise support a unit for determining that the UE is not authorized to communicate with the third core network service. In some examples, uplink addressing scheme manager 1425 may be configured to or otherwise support a unit for avoiding 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.

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

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

[0226] In some examples, the downlink resource manager 1455 can be configured to or otherwise support a unit for determining downlink resources for a third packet data unit based on destination routing information and based on the first header also indicating source routing information, wherein sending the third packet data unit includes: using the downlink resources to send the third packet data unit.

[0227] In some examples, routing a first packet data unit to a first core network service based on a first addressing scheme includes routing the first packet data unit to a proxy service. In some examples, routing a second packet data unit to a second core network service based on a 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.

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

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

[0230] Fig.15 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 is shown. The device 1505 may be an example of or include components of a device 1205, a device 1305, or a DU 165 as described herein. The device 1505 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a 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).

[0231] 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 communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515 that are capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1510 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., via one or more antennas 1515, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1515, from a wired receiver), and for demodulating a signal. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various sending or output operations, or a combination thereof. In some implementations, the transceiver 1510 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or are operable 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 processors or memory components (e.g., processor 1535, or memory 1525, or both) may be included in a chip or chip component installed in the device 1505. The transceiver 1510, or the transceiver 1510 and one or more antennas 1515 or a wired interface (where applicable) may be an example of a transmitter 1215, a transmitter 1315, a receiver 1210, a receiver 1310, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, fronthaul communication link 168).

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

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

[0234] In some examples, bus 1540 may support communications of protocol layers of a protocol stack (e.g., within a protocol layer 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 performed within components of device 1505, or communications performed between different components of device 1505 that may be co-located or located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 may be located in one component of different components or divided between different components).

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

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

[0237] By including or configuring the communication manager 1520 according to the examples described herein, the device 1505 can support techniques for improving communication reliability, reducing latency, improving user experience related to reduced processing, reducing power consumption, more efficiently utilizing communication resources, improving coordination between devices, and improving utilization of processing capabilities.

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

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

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

[0241] At 1610, the method may include sending, via a wireless connection, a first packet data unit associated with a first core network service in a set of core network services according to a first addressing scheme associated with the first core network service. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Fig.10 The described uplink addressing scheme manager 1030 is executed.

[0242] At 1615, the method may include sending, via the wireless connection, a second packet data unit associated with a second core network service in the set of core network services according to a second addressing scheme associated with the second core network service. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described with reference to Fig.10 The described uplink addressing scheme manager 1030 is executed.

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

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

[0245] At 1710, the method may include sending, via a wireless connection, a first packet data unit associated with a first core network service in a set of core network services according to a first addressing scheme associated with the first core network service. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Fig.10 The described uplink addressing scheme manager 1030 is executed.

[0246] At 1715, the method may include sending, via the wireless connection, a second packet data unit associated with a second core network service in the set of core network services according to a second addressing scheme associated with the second core network service. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Fig.10 The described uplink addressing scheme manager 1030 is executed.

[0247] At 1720, the method may include receiving a third packet data unit via the wireless connection. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described with reference to Fig.10 The described downlink packet manager 1050 is executed.

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

[0249] At 1730, the method may include processing the third packet data unit according to the first protocol associated with the first core network service. The operations of 1730 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1730 may be performed as described with reference to Fig.10 The core network service protocol manager 1060 described above is executed.

[0250] Fig.18 A flow chart illustrating a method 1800 for supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a DU or components thereof as described herein. For example, the operations of the method 1800 may be implemented by a DU or components thereof as described herein. Figures 1 to 7 12 to 15. In some examples, the DU may execute an instruction set to control the functional units of the DU to perform the described functions. Additionally or alternatively, the DU may use dedicated hardware to perform various aspects of the described functions.

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

[0252] At 1810, the method may include routing a first packet data unit to a first core network service based on a first addressing scheme. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described with reference to Fig.14 The core network services routing manager 1430 described is executed.

[0253] At 1815, the method may include: receiving, from the UE, a second packet data unit associated with a second core network service in the set of core network services, wherein the second packet data unit is received according to a second addressing scheme associated with the second core network service. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Fig.14 The described uplink addressing scheme manager 1425 is executed.

[0254] At 1820, the method may include routing the second packet data unit to the second core network service based on the second addressing scheme. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Fig.14 The core network services routing manager 1430 described is executed.

[0255] Fig.19 A flow chart illustrating a method 1900 for supporting addressability in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a DU or components thereof as described herein. For example, the operations of the method 1900 may be implemented by a DU or components thereof as described herein. Figures 1 to 7 12 to 15. In some examples, the DU may execute an instruction set to control the functional units of the DU to perform the described functions. Additionally or alternatively, the DU may use dedicated hardware to perform various aspects of the described functions.

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

[0257] At 1910, the method may include routing a first packet data unit to a first core network service based on a first addressing scheme. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described with reference to Fig.14 The core network services routing manager 1430 described is executed.

[0258] At 1915, the method may include: receiving, from the UE, a second packet data unit associated with a second core network service in the set of core network services, wherein the second packet data unit is received according to a second addressing scheme associated with the second core network service. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described with reference to Fig.14 The described uplink addressing scheme manager 1425 is executed.

[0259] At 1920, the method may include routing the second packet data unit to the second core network service based on the second addressing scheme. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described with reference to Fig.14 The core network services routing manager 1430 described is executed.

[0260] At 1925, the method may include: receiving, from the first core network service, a third packet data unit including a first header indicating destination routing information. The operations of 1925 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1925 may be performed as described with reference to Fig.14 The described downlink packet manager 1445 is executed.

[0261] At 1930, the method may include: instructing the UE to send a third packet data unit to the UE based on the destination routing information. The operations of 1930 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1930 may be performed as described with reference to Fig.14 The UE routing manager 1450 described above is executed.

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

[0263] Aspect 1: A method for wireless communication at a UE, comprising: 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 via a wireless connection between the UE and the DU, each core network service in the core network service set being associated with a corresponding addressing scheme; sending a first packet data unit associated with a first core network service in the core network service set according to a first addressing scheme associated with the first core network service in the core network service set via the wireless connection; and sending a second packet data unit associated with a second core network service in the core network service set according to a second addressing scheme associated with the second core network service in the core network service set via the wireless connection.

[0264] Aspect 2: The method according to Aspect 1 also includes: determining first routing information associated with the first core network service and second routing information associated with the second core network service, wherein sending the first packet data unit according to the first addressing scheme includes: attaching a first header including the first routing information to the first packet data unit, and wherein sending the second packet data unit according to the second addressing scheme includes: attaching a second header including the second routing information to the second packet data unit.

[0265] Aspect 3: The method according to any one of Aspects 1 to 2 further includes: determining a first AS resource associated with the first core network service and a second AS resource associated with the second core network service, wherein sending the first packet data unit according to the first addressing scheme includes: sending the first packet data unit using the first AS resource, and wherein sending the second packet data unit according to the second addressing scheme includes: sending the second packet data unit using the second AS resource.

[0266] Aspect 4: The method according to aspect 3 further includes: 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.

[0267] Aspect 5: The method according to any one of aspects 3 to 4, further comprising: receiving control information indicating the first AS resource and the second AS resource from the DU via the wireless connection.

[0268] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: receiving control information from a proxy service via the wireless connection, the 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, wherein sending the first packet data unit according to the first addressing scheme includes: sending an indication of the first service identifier together with the first packet data unit, and wherein sending the second packet data unit according to the second addressing scheme includes: sending an indication of the second service identifier together with the second packet data unit.

[0269] Aspect 7: The method according to Aspect 6 further includes: receiving an indication of AS resources associated with the proxy service together with the control information, wherein sending the first packet data unit according to the first addressing scheme includes: sending the first packet data unit using the AS resources, and wherein sending the second packet data unit according to the second addressing scheme includes: sending the second packet data unit using the AS resources.

[0270] Aspect 8: The method according to aspect 7 further includes: determining, at the UE, a logical channel associated with the AS resource.

[0271] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: 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 first routing information 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.

[0272] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: receiving control information indicating a first service identifier associated with the first core network service from a proxy service via the wireless connection; 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 the 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.

[0273] Aspect 11: The method according to any one 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.

[0274] 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 the following: mobility service, connection state management service, security service, paging service, radio access service, data service, capability management service, location service, or messaging service.

[0275] Aspect 13: A method for wireless communication at a DU, comprising: receiving a first packet data unit associated with a first core network service in a core network service set from a UE, the core network service set being provided by a service-based network configured to interface with a RAN associated with the DU, wherein the first packet data unit is 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 a second packet data unit associated with a second core network service in the core network service set from the UE, wherein the second packet data unit is 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.

[0276] Aspect 14: The method according to Aspect 13 further includes: determining that the first core network service is associated with the first packet data unit based on first routing information included in the first header of the first packet data unit, and determining that the second core network service is associated with the second packet data unit based on second routing information included in the second header of 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 wherein 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.

[0277] Aspect 15: The method according to any one of Aspects 13 to 14 further includes: 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.

[0278] Aspect 16: The method according to Aspect 15 further includes: receiving control information indicating a set of network entities authorized to communicate with the first core network service, wherein the set of network entities includes the UE, and wherein the determination that the UE is authorized to communicate with the first core network service is based on the control information.

[0279] Aspect 17: The method according to any one of Aspects 13 to 16 further includes: receiving a third packet data unit associated with a third core network service in the core network service set from the UE, wherein the third packet data unit is 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 avoiding 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.

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

[0281] Aspect 19: The method according to any one of Aspects 13 to 18 further includes: receiving a third packet data unit including a first header indicating destination routing information from the first core network service; and sending the third packet data unit to the UE based on the destination routing information indicating the UE.

[0282] Aspect 20: The method according to Aspect 19 further includes: determining downlink resources for the third packet data unit based on the destination routing information and based on the first header also indicating source routing information, wherein sending the third packet data unit includes: using the downlink resources to send the third packet data unit.

[0283] Aspect 21: A method according to any one 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.

[0284] Aspect 22: The method according to any one 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.

[0285] Aspect 23: A method according to any one of Aspects 13 to 22, wherein the first core network service and the second core network service each include one of the following: mobility service, connection state management service, security service, paging service, radio access service, data service, capability management service, location service, or messaging service.

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

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

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

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

[0290] Aspect 28: An apparatus for wireless communication at a DU, comprising at least one unit for performing the method according to any one of aspects 13 to 23.

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for wireless communication at a user equipment (UE), comprising: establishing, via a wireless connection between the UE and the distributed unit, communications 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, each core network service in the set of core network services being associated with a corresponding addressing scheme; transmitting, via the wireless connection, a first packet data unit associated with a first core network service in the set of core network services according to a first addressing scheme associated with the first core network service; as well as A second packet data unit associated with a second core network service in the set of core network services is sent via the wireless connection according to a second addressing scheme associated with the second core network service.

2. The method according to claim 1, further comprising: Determine first routing information associated with the first core network service and second routing information associated with the second core network service, wherein sending the first packet data unit according to the first addressing scheme includes: appending a first header including the first routing information to the first packet data unit, and wherein sending the second packet data unit according to the second addressing scheme includes: appending a second header including the second routing information to the second packet data unit.

3. The method according to claim 1, further comprising: Determine a first access layer resource associated with the first core network service and a second access layer resource associated with the second core network service, wherein sending the first packet data unit according to the first addressing scheme includes: sending the first packet data unit using the first access layer resource, and wherein sending the second packet data unit according to the second addressing scheme includes: sending the second packet data unit using the second access layer resource.

4. The method according to claim 3, further comprising: A first logical channel associated with the first access stratum resources and a second logical channel associated with the second access stratum resources are determined at the UE.

5. The method according to claim 3, further comprising: Control information indicative of the first access stratum resources and the second access stratum resources is received from the distributed unit via the wireless connection.

6. The method according to claim 1, further comprising: receiving control information from a proxy service via the wireless connection, the 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, wherein sending the first packet data unit according to the first addressing scheme comprises sending an indication of the first service identifier together with the first packet data unit, and wherein sending the second packet data unit according to the second addressing scheme comprises sending an indication of the second service identifier together with the second packet data unit.

7. The method according to claim 6, further comprising: An indication of access stratum resources associated with the proxy service is received together with the control information, wherein sending the first packet data unit according to the first addressing scheme includes sending the first packet data unit using the access stratum resources, and wherein sending the second packet data unit according to the second addressing scheme includes sending the second packet data unit using the access stratum resources.

8. The method according to claim 1, further comprising: receiving a third packet data unit via the wireless connection; 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; as well as The third packet data unit is processed according to a first protocol associated with the first core network service.

9. The method according to claim 1, further comprising: receiving, from a proxy service via the wireless connection, control information indicating a first service identifier associated with the 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; as well as The third packet data unit is processed according to a first protocol associated with the first core network service.

10. The method according to 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. The method according to 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 radio access service, a data service, a capability management service, a location service, or a messaging service.

12. A method for wireless communication at a distributed unit, comprising: receiving, from a user equipment (UE), a first packet data unit associated with a first core network service in 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 the first packet data unit is 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 in the set of core network services, wherein the second packet data unit is received according to a second addressing scheme associated with the second core network service; and The second packet data unit is routed to the second core network service based on the second addressing scheme.

13. The method according to claim 12, further comprising: The first core network service is determined to be associated with the first packet data unit based on first routing information included in a first header of the first packet data unit, and the second core network service is determined to be associated with the second packet data unit based on second routing information included in a second header of 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 wherein 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.

14. The method according to claim 12, further comprising: A determination is made 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. The method according to claim 14, further comprising: Receiving control information indicating a set of network entities authorized to communicate with the first core network service, wherein the set of network entities includes the UE, and wherein the determination that the UE is authorized to communicate with the first core network service is based on the control information.

16. The method according to claim 12, further comprising: receiving, from the UE, a third packet data unit associated with a third core network service in the set of core network services, wherein the third packet data unit is 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 Routing the third packet data unit to the third core network service is avoided based on the determination that the UE is not authorized to communicate with the third core network service.

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

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

19. The method according to 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 also indicating source routing information, wherein sending the third packet data unit includes sending the third packet data unit using the downlink resources.

20. The method of claim 12, 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.

21. The method according to 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. The method according to claim 12, wherein: The first core network service and the second core network service each include one of the following: mobility service, connection state management service, security service, paging service, radio access service, data service, capability management service, location service, or messaging service.

23. An apparatus for wireless communication at a user equipment (UE), comprising: processor; as well as A memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to perform the following operations: establishing, via a wireless connection between the UE and the distributed unit, communications 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, each core network service in the set of core network services being associated with a corresponding addressing scheme; transmitting, via the wireless connection, a first packet data unit associated with a first core network service in the set of core network services in accordance with a first addressing scheme associated with the first core network service; and A second packet data unit associated with a second core network service in the set of core network services is sent via the wireless connection according to a second addressing scheme associated with the second core network service.

24. The device according to claim 23, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: Determine a first access layer resource associated with the first core network service and a second access layer resource associated with the second core network service, wherein sending the first packet data unit according to the first addressing scheme includes: sending the first packet data unit using the first access layer resource, and wherein sending the second packet data unit according to the second addressing scheme includes: sending the second packet data unit using the second access layer resource.

25. The device according to claim 24, wherein: The instructions may also be executed by the processor to cause the device to perform the following operations: Control information indicative of the first access stratum resources and the second access stratum resources is received from the distributed unit via the wireless connection.

26. The device according to claim 23, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: receiving control information from a proxy service via the wireless connection, the 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, wherein sending the first packet data unit according to the first addressing scheme comprises sending an indication of the first service identifier together with the first packet data unit, and wherein sending the second packet data unit according to the second addressing scheme comprises sending an indication of the second service identifier together with the second packet data unit.

27. An apparatus for wireless communication at a distributed unit, comprising: processor; as well as A memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to perform the following operations: receiving, from a user equipment (UE), a first packet data unit associated with a first core network service in 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 the first packet data unit is 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 in the set of core network services, wherein the second packet data unit is received according to a second addressing scheme associated with the second core network service; and The second packet data unit is routed to the second core network service based on the second addressing scheme.

28. The device according to claim 27, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: A determination is made 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.

29. The device according to claim 28, wherein The instructions may also be executed by the processor to cause the device to perform the following operations: Receiving control information indicating a set of network entities authorized to communicate with the first core network service, wherein the set of network entities includes the UE, and wherein the determination that the UE is authorized to communicate with the first core network service is based on the control information.

30. The apparatus of claim 27, 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.

Images