Discovery in service-based wireless system

Abstract

Methods, systems, and devices for wireless communication are described. The techniques relate to signaling between a user equipment (UE), a distributed unit, and a discovery service of a service-based network that provides service information about other core network services of the service-based network. The service information may enable the UE to establish and maintain connections with various core network services provided by the service-based network. The UE may indicate a requested capability for the core network service, and the discovery service may return service information indicating the core network service that matches the requested capability. The UE may request information about the particular core network service in a discovery request, and the discovery service may return information about the particular core network service. For example, the service information may include dependency information between core network services, service capabilities, or network locations associated with the core network services.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 948,051, entitled "DISCOVERY INASERVICE-BASED WIRELESS SYSTEM," filed by Griot et al. on September 19, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including discovery 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, broadcast, 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, such as 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 of communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting discovery in service-based wireless systems. For example, the described technology provides signaling and other mechanisms that enable a user equipment (UE) to establish a wireless connection in a service-based network (e.g., a 6G network). The technology relates to signaling between a UE, a distributed unit (DU) and a discovery service of a service-based network, which provides service information about other core network services of the service-based network. The service information enables the UE to establish and maintain a connection with various core network services provided by the service-based network. In some cases, the UE may indicate the capabilities requested for the core network service, and the discovery service may return service information indicating the core network service that matches the requested capabilities. In some cases, the UE may request information about a specific core network service in a discovery request, and the discovery service may return information about a specific core network service. For example, the service information may include dependency information between core network services, service capabilities, or a network location associated with a core network service.

[0006] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving control information from a DU, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network configured to interface with a radio access network (RAN) associated with the DU; sending a discovery request including the routing information to the DU in response to the control information; and receiving service information associated with the core network service set from the DU in response to the discovery request.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor so that the apparatus receives control information from a DU, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU; in response to the control information, sends a discovery request including the routing information to the DU; and receives service information from the DU in response to the discovery request, the service information being associated with the core network service set.

[0008] Another apparatus for wireless communication on a UE is described. The apparatus may include means for receiving control information from a DU, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network configured to interface with a RAN associated with the DU; means for sending a discovery request including the routing information to the DU in response to the control information; and means for receiving service information associated with the core network service set from the DU in response to the discovery request.

[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 receive control information from a DU, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network configured to interface with a RAN associated with the DU; in response to the control information, send a discovery request including the routing information to the DU; and in response to the discovery request, receive service information from the DU, the service information associated with the core network service set.

[0010] Some examples of the methods, apparatus and non-transitory computer-readable media described herein may also include the following operations, features, units or instructions: in response to service information indicating a core network service set, sending a service request indicating a core network service in the core network service set to the DU; in response to the service request, receiving second control information indicating a service context for communicating with the core network service from the DU; and transmitting a message with the core network service via the DU according to the service context.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the service information includes an indication of a dependency of a core network service on a second core network service, and the methods, apparatus, and non-transitory computer-readable media may also include the following operations, features, units, or instructions: sending a second service request to the DU based on the dependency, the second service request indicating a second core network service in the core network service set; receiving third control information from the DU in response to the second service request, the third control information indicating a second service context for communicating with the second core network service; and transmitting a second message to the second core network service via the DU and based on the second service context, wherein the transmitted message may be based on transmitting the second message.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a discovery request may include the following operations, features, units, or instructions: sending an indication of one or more requested service capabilities, wherein the service information includes a list of core network service subsets in a core network service set associated with the one or more requested service capabilities.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include the following operations, features, units, or instructions: in response to the service information, sending a service request indicating a selected core network service from a subset of core network services to the DU; in response to the service request, receiving second control information indicating a service context for communicating with the selected core network service from the DU; and transmitting a message with the selected core network service via the DU according to the service context.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a discovery request may include the following operations, features, units, or instructions: sending an indication of a subset of core network services in a core network service set, wherein, for each core network service in the core network service subset, service information includes one or more of core network service dependency information, service capabilities, network addresses, or network locations.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving service information may include the following operations, features, units, or instructions: receiving an indication of one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in a core network service set.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, routing information may be associated with a proxy service that may be configured to route the discovery request to the core network discovery service.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving control information may include the following operations, features, units, or instructions: receiving a system information block message including control information.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a discovery request may be sent to a DU for relaying to a network address associated with a core network discovery service, the network address being based on routing information.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each core network service in the set of core network services can be associated with a corresponding application programming interface in the plurality of sets of application programming interfaces.

[0020] A method for wireless communication at a DU is described. The method may include: sending control information to a UE, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network configured to interface with a RAN associated with the DU; transmitting a discovery request including the routing information received from the UE to the core network discovery service; and transmitting service information received from the core network discovery service in response to the discovery request to the UE, the service information being associated with the core network service set.

[0021] 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 executed by the processor so that the apparatus sends control information to a UE, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU; transmits a discovery request including the routing information received from the UE to the core network discovery service; and transmits service information received from the core network discovery service in response to the discovery request to the UE, the service information being associated with the core network service set.

[0022] Another apparatus for wireless communication at a DU is described. The apparatus may include: a unit for sending control information to a UE, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network configured to interface with a RAN associated with the DU; a unit for transmitting a discovery request to the core network discovery service, the discovery request including the routing information received from the UE; and a unit for transmitting service information received from the core network discovery service in response to the discovery request to the UE, the service information associated with the core network service set.

[0023] 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 send control information to a UE, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network configured to interface with a RAN associated with the DU; transmit a discovery request including the routing information received from the UE to the core network discovery service; and transmit service information received from the core network discovery service in response to the discovery request to the UE, the service information being associated with the core network service set.

[0024] Some examples of the methods, apparatus and non-transitory computer-readable media described herein may also include the following operations, features, units or instructions: receiving a service request indicating a core network service in the core network service set from a UE in response to service information indicating a core network service set; sending second control information indicating a service context for communication between the UE and the core network service to the UE in response to the service request; and transmitting a message received from the UE to the core network service according to the service context.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include the following operations, features, units, or instructions: receiving a second service request from a UE in response to service information, the second service request indicating a second core network service in the core network service set, wherein the service information includes an indication of a dependency of the core network service on the second core network service; sending third control information indicating a second service context for communication between the UE and the second core network service to the UE in response to the second service request; and transmitting a second message received from the UE to the second core network service based on the second service context, wherein the transmitted message may be based on transmitting the second message.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, transmitting a discovery request may include the following operations, features, units, or instructions: receiving an indication of one or more requested service capabilities from a UE, wherein the service information includes a list of core network service subsets in a core network service set associated with the one or more requested service capabilities.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include the following operations, features, units, or instructions: receiving, in response to the service information, a service request indicating a selected core network service in a subset of core network services from a UE; sending, in response to the service request, second control information indicating a service context for communication between the UE and the selected core network service to the UE; and transmitting a message received from the UE to the selected core network service according to the service context.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, transmitting a discovery request may include the following operations, features, units, or instructions: receiving an indication of a subset of core network services in a core network service set from a UE, wherein, for each core network service in the core network service subset, service information includes one or more of core network service dependency information, service capabilities, a network address, or a network location.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, transmitting service information may include the following operations, features, units, or instructions: sending an indication of one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in a core network service set to a UE.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, routing information may be associated with a proxy service, which may be configured to route discovery requests to a core network discovery service and route service information from the core network discovery service to the UE via the DU, and transmitting the discovery request to the core network discovery service includes sending the discovery request to the proxy service, and transmitting the service information includes receiving the service information via the proxy service.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending control information may include the following operations, features, units, or instructions: sending a system information block message including the control information.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each core network service in the set of core network services can be associated with a corresponding application programming interface in a plurality of sets of application programming interfaces.

[0033] A method for wireless communication at a core network discovery service is described. The method may include receiving a discovery request from a UE via a DU, the discovery request including routing information associated with a core network discovery service for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU, and in response to the discovery request, sending service information associated with the core network service set to the DU for relaying to the UE.

[0034] An apparatus for wireless communication at a core network discovery service is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor so that the apparatus receives a discovery request including routing information associated with a core network discovery service from a UE via a DU, the core network discovery service being for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU, and in response to the discovery request, sends service information associated with the core network service set to the DU for relaying to the UE.

[0035] Another apparatus for wirelessly communicating at a core network discovery service is described. The apparatus may include means for receiving a discovery request from a UE via a DU, the discovery request including routing information associated with a core network discovery service for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU, and means for sending service information associated with the core network service set to the DU for relaying to the UE in response to the discovery request.

[0036] A non-transitory computer-readable medium storing code for wireless communication at a core network discovery service is described. The code may include processor-executable instructions to receive, from a UE via a DU, a discovery request including routing information associated with a core network discovery service for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU, and in response to the discovery request, send service information associated with the core network service set to the DU for relaying to the UE.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a discovery request may include the following operations, features, units, or instructions: receiving an indication of one or more requested service capabilities, wherein the service information includes a list of core network service subsets in a core network service set associated with the one or more requested service capabilities.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a discovery request may include the following operations, features, units, or instructions: receiving an indication of a subset of core network services in a core network service set, wherein, for each core network service in the core network service subset, service information includes one or more of core network service dependency information, service capabilities, network addresses, or network locations.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending service information may include the following operations, features, units, or instructions: sending an indication of one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in a core network service set.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, routing information may be associated with a proxy service, which may be configured to route discovery requests to a core network discovery service and route service information to the UE via the DU, receiving the discovery request includes receiving the discovery request from the DU via the proxy service, and sending the service information to the DU includes sending the service information via the proxy service.

[0041] A method for wireless communication at a proxy service is described. The method may include: receiving a discovery request including routing information associated with the proxy service from a UE via a DU; sending the discovery request to a core network discovery service associated with a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU; receiving service information associated with the core network service set from the core network discovery service in response to the discovery request, and sending the service information to the DU for relaying to the UE.

[0042] An apparatus for wireless communication at a proxy service is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor so that the apparatus receives a discovery request including routing information associated with a proxy service from a UE via a DU, sends the discovery request to a core network discovery service associated with a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU, receives service information associated with the core network service set from the core network discovery service in response to the discovery request, and sends the service information to the DU for relaying to the UE.

[0043] Another apparatus for wireless communication at a proxy service is described. The apparatus may include means for receiving a discovery request including routing information associated with the proxy service from a UE via a DU; means for sending the discovery request to a core network discovery service associated with a core network service set provided by a service-based network configured to interface with a RAN associated with the DU; means for receiving service information associated with the core network service set from the core network discovery service in response to the discovery request; and means for sending the service information to the DU for relaying to the UE.

[0044] A non-transitory computer-readable medium storing code for wireless communication at a proxy service is described. The code may include instructions executable by a processor to receive a discovery request including routing information associated with a proxy service from a UE via a DU; send the discovery request to a core network discovery service associated with a core network service set provided by a service-based network configured to interface with a RAN associated with the DU; receive service information associated with the core network service set from the core network discovery service in response to the discovery request; and send the service information to the DU for relaying to the UE.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a discovery request may include the following operations, features, units, or instructions: receiving an indication of one or more requested service capabilities, wherein the service information includes a list of core network service subsets in a core network service set associated with the one or more requested service capabilities.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a discovery request may include the following operations, features, units, or instructions: receiving an indication of a subset of core network services in a core network service set, wherein, for each core network service in the core network service subset, service information includes one or more of core network service dependency information, service capabilities, network addresses, or network locations.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the service information includes one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in a core network service set. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

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

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

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

[0060] Fig.15 and Fig.16 A block diagram of a device supporting service-based discovery in a wireless system is shown in accordance with one or more aspects of the present disclosure.

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

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

[0063] Fig.19 and Fig. 20 A block diagram of a device supporting service-based discovery in a wireless system is shown in accordance with one or more aspects of the present disclosure.

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

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

[0066] Figure 23 to Figure 28 A flow chart illustrating a method of supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

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

[0068] In contrast, some wireless systems (e.g., sixth generation (6G) systems) may exhibit a flatter service-based architecture, in which a radio access network (RAN) (e.g., a network entity) interfaces with a service-based network to connect UEs to core network services maintained at various network addresses within the service-based network. In the context of a service-based system, operations and functions that might otherwise be performed by a few centralized backend components (e.g., in some systems) may be distributed across many core network services, which may be hosted at different network addresses, such as in a cloud-based architecture. Thus, a UE in a service-based system may 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, wherein each core network service offers or provides corresponding network functions or services. For example, a service-based system may include mobile 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.

[0069] Various aspects of the present disclosure relate to signaling and other mechanisms that enable a UE to establish a wireless connection in a service-based network. The described techniques relate to signaling between a UE, a distributed unit (DU), and a discovery service of a service-based network that provides service information about other core network services of the service-based network. The service information may enable the UE to establish and maintain connections to various core network services provided by the service-based network.

[0070] In some examples, the DU may send control information (e.g., via a system information block (SIB)) indicating routing information for a discovery service associated with a service-based network. The UE may send a discovery request to the DU, and the DU may route the discovery request to the discovery service based on the routing information included with the discovery request. The routing information may include a network address for the discovery service or a proxy address associated with a (e.g., for) proxy that routes information between the DU and the discovery service (and / or other core network services). The DU may route the discovery request to the discovery service (e.g., directly or indirectly via a proxy service) based on the routing information associated with the discovery service, and the discovery service may return service information for the core network service provided by the network. The DU may route the service information to the UE. In some cases, the discovery request may indicate the requested capabilities for the core network service, and the discovery service may return service information indicating services that match the requested capabilities. In some cases, the UE may request information about a specific core network service in the discovery request, and the discovery service may return information about a specific core network service. For example, the service information may include dependency information, service capabilities, or a network location associated with the core network service for the core network service.

[0071] Various aspects of the disclosure are initially described in the context of a wireless communication system. Various aspects of the disclosure are further illustrated and described with reference to flow diagrams, system diagrams, and flow charts related to discovery in a service-based wireless system.

[0072] Figure 1 An example of a wireless communication system 100 that supports discovery 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0103] 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, the 6G RAT may be associated with the service-based network 130, and the 5G RAT may be associated with the 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 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.

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

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

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

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

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

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

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

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

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

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

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

[0115] Figure 2 An example of a wireless communication system that supports discovery 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 a wireless communication system 100). Figure 1 An example architecture of the system described herein.

[0116] 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, and a third core network service 215-c). 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.

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

[0118] like Figure 2 As shown, the wireless communication system 200 may present a service-based architecture in which entities of the RAN 210 (e.g., the network entity 105-a) are configured to connect the UE 115-a to the core network services 215 of the service-based network 205. In particular, the RAN 210 (e.g., the network entity 105-a) may be configured to relay communications between the UE 115-a and 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.

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

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

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

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

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

[0124] 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 excessive 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.

[0125] In contrast, Figure 2The 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).

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

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

[0128] 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 the core network 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).

[0129] For example, a discovery service 230 associated with the service-based network 205 may provide service information about other core network services 215 of the service-based network 205. The service information may enable the UE 115-a to establish and maintain connections with various core network services 215 provided by the service-based network 205.

[0130] In some examples, the network entity 105-a may send control information (e.g., via a SIB) indicating routing information for the discovery service 230. The UE 115-a may send a discovery request to the network entity 105-a, and the network entity 105-a may route the discovery request to the discovery service 230 based on the routing information included with the discovery request. The routing information may include a network address for the discovery service or a proxy address associated with a proxy service 235 that routes information between the network entity 105-a and the discovery service 230 (and / or other core network services 215) (e.g., for the proxy service 235). The network entity 105-a may route the discovery request to the discovery service 230 based on the routing information associated with the discovery service 230 (e.g., directly or indirectly via the proxy service 235).

[0131] The discovery service 230 may return service information of the core network services 215 provided by the service-based network. The network entity 105-a may route the service information to the UE 115-a. In some cases, the discovery request may indicate the requested capabilities of the core network services 215, and the discovery service 230 may return service information indicating the core network services 215 that match the requested capabilities. In some cases, the UE 115-a may request information about a specific core network service 215 in the discovery request, and the discovery service 230 may return information about the specific core network service 215. For example, the service information may include dependency information of the core network service 215, service capabilities of the core network service 215, or a network location associated with the core network service 215.

[0132] Figure 3An example of a network architecture 300 supporting discovery 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., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via respective fronthaul communication links 168-a. The RU 170-a may be associated with respective coverage areas 110-a and may communicate with the UE 115-b via one or more communication links 125-a. In some implementations, the UE 115-b may be served simultaneously by multiple RUs 170-a.

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

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

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

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

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

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

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

[0140] Figure 4 An example of a process flow 400 for supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The process flow 400 may include a UE 115-c, which may be an example of a UE 115 described herein. The process flow 400 may include a DU 165-b, which may be an example of a DU 165 described herein. In the following description of the process flow 400, operations between the UE 115-c and the DU 165-b may be sent in an order different from the example order shown, or operations performed by the UE 115-c and the DU 165 may be performed in a different order or at different times. Certain operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400.

[0141] Process flow 400 illustrates an example of a broadcast-based discovery mode. At 405, DU 165-b may broadcast a SIB indicating a set of core network services provided by a service-based network. The SIB may indicate routing information (e.g., a network address) for the core network service and service information associated with the core network service. In some cases, each core network service in the set of core network services is associated with a corresponding API in a set of multiple APIs.

[0142] For example, the service information may include: service type (e.g., mobility, security, paging, registration, data service, short message service (SMS), location service, data service); specific type of service information (e.g., certain capabilities of core network services); information about how to enable core network services (e.g., routing information / network addresses (e.g., IP addresses, TCP ports, or HTTP ports associated with each core network service); dependencies on other core network services (e.g., data services may depend on security and / or registration services); or whether further discovery information is available (e.g., routing information of the discovery service 230, which may provide additional information about the set of core network services).

[0143] At 410, the UE 115-c may select one or more core network services from the core network service set indicated by the SIB. For example, the UE 115-c may automatically select one or more core network services based on the capabilities required by the UE 115-c, the preferences of the UE 115-c, and the service information indicated by the SIB. In some cases, the UE 115-c may automatically select additional core network services that the selected core network service depends on (e.g., based on the service information). In some cases, the user may manually select a service. For example, the UE 115-c may display a list of available core network services based on the service information. The order in which the core network services are displayed and the display of the service information may be determined based on a configuration received from the user (e.g., user preferences or based on a home network).

[0144] At 415, UE 115-c may connect with the selected core network service via DU 165-b. For example, UE 115-c may send a service request to DU 165-b indicating a core network service in the core network service set. DU 165-b may transmit the service request to the indicated core network service. DU 165-b may send control information to UE 115-c indicating a service context for communication between UE 115-c and the indicated core network service. UE 115-c may then transmit a message with the indicated core network service via DU 165-b based on the service context.

[0145] Figure 5 An example of a process flow 500 for supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The process flow 500 may include a UE 115-d, which may be an example of a UE 115 described herein. The process flow 500 may include a DU 165-c, which may be an example of a DU 165 described herein. The process flow 500 may include a discovery service 230-a, which may be an example of a discovery service 230 described herein. In the following description of the process flow 500, operations between the UE 115-d, the DU 165-c, and the discovery service 230-a may be sent in an order different from the example order shown, or operations performed by the UE 115-d, the DU 165-c, and the discovery service 230-a may be performed in a different order or at a different time. Certain operations may also be omitted from the process flow 500, and other operations may be added to the process flow 500.

[0146] Process flow 500 illustrates an example of a query-based direct discovery mode. At 505, UE 115-d may receive control information from DU 165-c indicating routing information for a discovery service 230-a for a set of core network services provided by a service-based network configured to interface with a RAN associated with DU 165-c. For example, UE 115-d may receive control information via a SIB broadcast of DU 165-c that announces information for discovery service 230-a (e.g., routing information (e.g., an IP address, TCP port, or HTTP port associated with discovery service 230-a)). In some cases, each core network service in the set of core network services is associated with a corresponding API in a set of multiple APIs.

[0147] At 510 , the UE 115 - d may select the discovery service 230 - a based on the control information.

[0148] At 515, UE 115-d may send a discovery request including routing information for discovery service 230-a to DU 165-c. DU 165-c may transmit the discovery request to discovery service 230-a based on the routing information. For example, the discovery request may be sent to DU 165-c for relaying to a network address associated with discovery service 230-a, where the network address is based on the routing information.

[0149] At 520, the discovery service 230-a may transmit a discovery response to the DU 165-c in response to the discovery request, wherein the discovery response includes service information associated with the core network service set. The DU 165-c may send the service information to the UE 115-d.

[0150] For example, the service information may include a list of core network services and, for each of the core network services, including: service type (e.g., mobility, security, paging, registration, data service, SMS, location service, data service); information about a specific type of service (e.g., certain capabilities of the service); information about how to enable the core network service (e.g., routing information / network address (e.g., IP address, TCP port, or HTTP port)); network location (e.g., edge of the network); dependencies on other core network services (e.g., data services may depend on security and / or registration services); and whether further discovery information can be obtained via discovery service 230-a.

[0151] At 525, UE 115-d may select one or more core network services from the core network service set based on the service information. For example, UE 115-d may automatically select one or more core network services based on the capabilities required by UE 115-d, preferences of UE 115-d, and service information. In some cases, UE 115-d may automatically select additional core network services that the selected core network service depends on (e.g., based on service information). In some cases, the user may manually select a service. For example, UE 115-d may display a list of available core network services based on service information. The order of displayed core network services and the display of service information may be determined based on a configuration received from the user (e.g., user preferences or based on a home network).

[0152] At 530, UE 115-d may connect with the selected core network service via DU 165-c. For example, UE 115-d may send a service request to DU 165-c indicating a core network service in a core network service set. DU 165-c may transmit the service request to the indicated core network service. DU 165-c may send control information to UE 115-d indicating a service context for communication between UE 115-d and the indicated core network service. UE 115-d may then transmit a message with the indicated core network service via DU 165-c based on the service context.

[0153] In some cases, the control information at 505 may indicate a set of core network services, as well as an indication that routing information for the discovery service 230-a and more information about the core network services may be obtained from the discovery service 230-a. The UE 115-d may select the discovery service 230-a at 510 and send a discovery request at 515 based on the control information indicating the set of core network services. For example, the UE 115-d may select a particular core network service from the set of core network services for which the UE 115-d may request additional service information. In some cases, the UE 115-d may select a particular core network service for which to request information based on a preferred service capability or a preferred service location (e.g., network edge).

[0154] In some cases, the UE 115-d may indicate a preferred or requested service capability or network location in the discovery request at 515. The discovery service 230-a may provide a list of core network services associated with the preferred or requested service capability or network location in the discovery response at 520. The UE 115-d may select a core network service to connect to from the list of core network services at 525.

[0155] Figure 6 An example of a process flow 600 for supporting discovery 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 described herein. The process flow 600 may include a DU 165-d, which may be an example of a DU 165 described herein. The process flow 500 may include a proxy service 235-a, which may be an example of a proxy service 235 described herein. The process flow 600 may include a discovery service 230-b, which may be an example of a discovery service 230 described herein. In the following description of the process flow 600, operations between the UE 115-e, the DU 165-d, the proxy service 235-a, and the discovery service 230-b may be sent in an order different from the example order shown, or the operations performed by the UE 115-e, the DU 165-d, the proxy service 235-a, and the discovery service 230-b may be performed in a different order or at a different time. Certain operations may also be omitted from process flow 600 , and other operations may be added to process flow 600 .

[0156] Process flow 600 illustrates an example of an indirect discovery mode based on a query. At 605, UE 115-e may receive control information from DU 165-d indicating routing information associated with (e.g., for) a proxy service 235-a, which is configured to route communications between UE 115-e and discovery service 230-b for a set of core network services provided by a service-based network configured to be docked with a RAN associated with DU165-d. In some cases, proxy service 235-a may be configured to route communications between UE 115-e and a set of core network services. Using a proxy service may hide the topology of a service-based network from UE 115-e. UE 115-e may receive control information via a SIB broadcasted by DU 165-d, which announces proxy information for proxy service 235-a. In some cases, each core network service in a set of core network services is associated with a corresponding API in a set of multiple APIs.

[0157] At 610 , the UE 115 - e may select the proxy service 235 - a based on the control information.

[0158] At 615, the UE 115-e may send a discovery request including routing information for the proxy service 235-a to the DU 165-d. The DU 165-d may transmit the discovery request to the proxy service 235-a based on the routing information.

[0159] At 620 , the proxy service 235 - a may send a discovery request to the discovery service 230 - b , for example, based on the network address of the discovery service 230 - b known to the proxy service 235 - a.

[0160] At 625 , the discovery service 230 - b may transmit a discovery response to the proxy service 235 - a in response to the discovery request, the discovery response including service information associated with the core network service set.

[0161] At 630, the proxy service 235-a may send a service response including the service information to the DU 165-d. The DU 165-d may send the service information to the UE 115-e.

[0162] For example, the service information may include a list of core network services, and for each core network service in the core network services, including: service type (e.g., mobility, security, paging, registration, data service, SMS, location service, data service); specific type of service information (e.g., certain capabilities of the service); information about how to enable the core network service (e.g., proxy / routing information / network address (e.g., IP address, TCP port, or HTTP port)); network location (e.g., network edge); dependencies on other core network services (e.g., data services may depend on security and / or registration services); and whether further discovery information can be obtained via discovery service 230-b.

[0163] At 635, the UE 115-e may select one or more core network services from the core network service set based on the service information. For example, the UE 115-e may automatically select one or more core network services based on the capabilities required by the UE 115-e, the preferences of the UE 115-e, and the service information. In some cases, the UE 115-e may automatically select additional core network services that the selected core network service depends on (e.g., based on the service information). In some cases, the user may manually select a service. For example, the UE 115-e may display a list of available core network services based on the service information. The order of the displayed core network services and the display of the service information may be determined based on a configuration received from the user (e.g., user preferences or based on a home network).

[0164] At 640, UE 115-e may connect to the selected core network service via DU 165-d. For example, UE 115-e may send a service request to DU 165-d, the service request indicating a core network service in the core network service set. DU 165-d may transmit the service request to the indicated core network service. DU 165-d may send control information indicating a service context for communication between UE 115-e and the indicated core network service to UE 115-e. Then, UE 115-e may transmit a message to the indicated core network service via DU 165-d according to the service context. In some cases, UE 115-e may communicate with the core network service via DU 165-d and proxy service 235-a (e.g., the proxy service may route the communication between UE 115-e and the selected core network service based on the service identifier associated with the core network service). For example, the network address associated with the core network service and the topology of the service-based network may be hidden from UE 115-e.

[0165] In some cases, the control information at 605 may indicate a set of core network services and an indication that routing information for the discovery service 230-b and more information about the core network services may be obtained from the discovery service 230-b. The UE 115-e may select the proxy service 235-a at 610 and send a discovery request at 615 based on the control information indicating the set of core network services. For example, the UE 115-e may select a specific core network service from the set of core network services for which the UE 115-e may request additional service information. In some cases, the UE 115-e may select a specific service to request information about based on a preferred service capability or a preferred service location (e.g., network edge).

[0166] In some cases, the UE 115-e may indicate a preferred or requested service capability or network location in the discovery request at 615. The discovery service 230-b may provide a list of core network services associated with the preferred or requested service capability or network location in the discovery response at 625. The UE 115-e may select a core network service to connect to from the list of core network services at 635.

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

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

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

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

[0171] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit system). The hardware can include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which are configured as or otherwise support units 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 functions described herein (e.g., by the processor executing instructions stored in the memory).

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

[0173] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, acquire, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, send information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to acquire information, output information, or perform other various operations described herein.

[0174] The communication manager 720 may support wireless communications at the UE according to the examples disclosed herein. For example, the communication manager 720 may be configured as or otherwise support a unit for receiving control information from the DU, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU. The communication manager 720 may be configured as or otherwise support a unit for sending a discovery request including routing information to the DU in response to the control information. The communication manager 720 may be configured as or otherwise support a unit for receiving service information associated with a core network service set from the DU in response to the discovery request.

[0175] By including or configuring a communications manager 720 according to the examples described herein, a device 705 (e.g., a processor controlling or otherwise coupled to a receiver 710, a transmitter 715, a communications manager 720, or a combination thereof) may support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communications resources.

[0176] Figure 8 A block diagram 800 of a device 805 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. As described herein, the device 805 can be an example aspect of the device 705 or the UE 115. 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).

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

[0178] 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 (e.g., packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to discovery in a service-based wireless system). In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.

[0179] Device 805 or its various components may be examples of units for performing various aspects of discovery in a service-based wireless system as described herein. For example, communication manager 820 may include discovery service manager 825, discovery request manager 830, service information manager 835, or any combination thereof. As described herein, communication manager 820 may be an example of various aspects of communication manager 720. In some examples, communication manager 820 or its various components may be configured to use or otherwise cooperate with receiver 810, transmitter 815, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 820 may receive information from receiver 810, send information to transmitter 815, or be integrated with receiver 810, transmitter 815, or both to obtain information, output information, or perform various other operations described herein.

[0180] The communication manager 820 may support wireless communication at the UE according to the examples described herein. The discovery service manager 825 may be configured as or otherwise support a unit for receiving control information from the DU, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU. The discovery request manager 830 may be configured as or otherwise support a unit for sending a discovery request including routing information to the DU in response to the control information. The service information manager 835 may be configured as or otherwise support a unit for receiving service information associated with a core network service set from the DU in response to the discovery request.

[0181] Fig. 9 A block diagram 900 of a communication manager 920 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both, as described herein. The communication manager 920 or its various components may be examples of units for performing various aspects of discovery in a service-based wireless system as described herein. For example, the communication manager 920 may include a discovery service manager 925, a discovery request manager 930, a service information manager 935, a service request manager 940, a service context manager 945, a core network service manager 950, a request capability manager 955, a SIB manager 960, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0182] The communication manager 920 may support wireless communications at the UE according to the examples disclosed herein. The discovery service manager 925 may be configured as or otherwise support a unit for receiving control information from the DU, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU. The discovery request manager 930 may be configured as or otherwise support a unit for sending a discovery request including routing information to the DU in response to the control information. The service information manager 935 may be configured as or otherwise support a unit for receiving service information associated with a core network service set from the DU in response to the discovery request.

[0183] In some examples, the service request manager 940 may be configured or otherwise support a unit for sending a service request indicating a core network service in the core network service set to the DU in response to service information indicating the core network service set. In some examples, the service context manager 945 may be configured or otherwise support a unit for receiving a second control information from the DU in response to the service request, the second control information indicating a service context for communicating with the core network service. In some examples, the core network service manager 950 may be configured or otherwise support a unit for transmitting a message with the core network service via the DU according to the service context.

[0184] In some examples, the service information includes an indication of a dependency of the core network service on a second core network service, and the service request manager 940 may be configured as or otherwise supports a unit for sending a second service request indicating a second core network service in the core network service set to the DU based on the dependency. In some examples, the service information includes an indication of a dependency of the core network service on the second core network service, and the service context manager 945 may be configured as or otherwise supports a unit for receiving third control information from the DU in response to the second service request, the third control information indicating a second service context for communicating with the second core network service. In some examples, the service information includes an indication of the dependency of the core network service on the second core network service, and the core network service manager 950 may be configured as or otherwise supports a unit for transmitting a second message with the second core network service via the DU based on the second service context, wherein the communication message is based on transmitting the second message.

[0185] In some examples, to support sending a discovery request, the request capability manager 955 may be configured as or otherwise support a unit for sending an indication of one or more requested service capabilities, wherein the service information includes a list of core network service subsets in a core network service set associated with the one or more requested service capabilities.

[0186] In some examples, the service request manager 940 may be configured as or otherwise support a unit for sending a service request indicating a selected core network service in the subset of core network services to the DU in response to the service information. In some examples, the service context manager 945 may be configured as or otherwise support a unit for receiving second control information indicating a service context for communicating with the selected core network service from the DU in response to the service request. In some examples, the core network service manager 950 may be configured as or otherwise support a unit for transmitting a message with the selected core network service via the DU according to the service context.

[0187] In some examples, to support sending a discovery request, the service request manager 940 may be configured as or otherwise support a unit for sending an indication of a subset of core network services in a core network service set, wherein, for each core network service in the core network service subset, the service information includes one or more of core network service dependency information, service capabilities, a network address, or a network location.

[0188] In some examples, to support receiving service information, the service information manager 935 may be configured as or otherwise support a unit for receiving indications of one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in a core network service set.

[0189] In some examples, the routing information is associated with a proxy service that is configured to route the discovery request to the core network discovery service.

[0190] In some examples, to support receiving control information, SIB manager 960 may be configured or otherwise support means for receiving system information block messages containing control information.

[0191] In some examples, a discovery request is sent to the DU for relaying to a network address associated with a core network discovery service, the network address being based on routing information.

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

[0193] Fig.10 A schematic diagram of a system 1000 including a device 1005 that supports discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1005 may be or include an example of a component of the device 705, device 805, or UE 115 described herein. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be coupled in electronic communication or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1045).

[0194] The I / O controller 1010 can manage input and output signals of the device 1005. The I / O controller 1010 can also manage peripheral devices that are not integrated into the device 1005. In some cases, the I / O controller 1010 can represent a physical connection to an external peripheral device or a port to an external peripheral device. In some cases, the I / O controller 1010 can utilize an operating system, for example, Or other known operating systems. Additionally, or alternatively, the I / O controller 1010 can represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 1010 can be implemented as part of a processor (e.g., processor 1040). In some cases, a user can interact with device 1005 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0195] In some cases, the device 1005 may include an antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025 and may be able to send or receive multiple wireless transmissions simultaneously. The transceiver 1015 can communicate bidirectionally via one or more antennas 1025, a wired link, or a wireless link, as described herein. For example, the transceiver 1015 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem to modulate packets, provide the modulated packets to one or more antennas 1025 for transmission, and demodulate packets received from one or more antennas 1025. The transceiver 1015 or the transceiver 1015 and the one or more antennas 1025 can be examples of the transmitter 715, the transmitter 815, the receiver 710, the receiver 810, or any combination or component thereof, as described herein.

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

[0197] The processor 1040 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 1040 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 1040. The processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) so that the device 1005 performs various functions (e.g., functions or tasks that support discovery in a service-based wireless system). For example, the device 1005 or a component of the device 1005 may include a processor 1040 and a memory 1030 coupled to the processor 1040 or a memory 1030 coupled to the processor 1040, and the processor 1040 and the memory 1030 are configured to perform the various functions described herein.

[0198] The communication manager 1020 may support wireless communication at the UE according to the examples disclosed herein. For example, the communication manager 1020 may be configured to or otherwise support a unit for receiving control information from the DU, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU. The communication manager 1020 may be configured to or otherwise support a unit for sending a discovery request including routing information to the DU in response to the control information. The communication manager 1020 may be configured to or otherwise support a unit for receiving service information associated with a core network service set from the DU in response to the discovery request.

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

[0200] In some examples, the communication manager 1020 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 can be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 can include instructions executable by the processor 1040 to cause the device 1005 to perform various aspects of discovery in a service-based wireless system as described herein, or the processor 1040 and the memory 1030 can be configured in other ways to perform or support such operations.

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

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

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

[0204] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or various components thereof may be examples of units for performing various aspects of discovery in a service-based wireless system as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or components thereof may support methods for performing one or more functions described herein.

[0205] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which are configured as or otherwise support 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 functions described herein (e.g., by the processor executing instructions stored in the memory).

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

[0207] In some examples, the communication manager 1120 can be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receive, acquire, monitor, output, send). For example, the communication manager 1120 can receive information from the receiver 1110, send information to the transmitter 1115, or combine with the receiver 1110, the transmitter 1115, or both to acquire information, output information, or perform various other operations described herein.

[0208] The communication manager 1120 may support wireless communication at the DU according to the examples disclosed herein. For example, the communication manager 1120 may be configured to or otherwise support a unit for sending control information to the UE, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU. The communication manager 1120 may be configured to or otherwise support a unit for transmitting a discovery request including routing information received from the UE to the core network discovery service. The communication manager 1120 may be configured to or otherwise support a unit for transmitting service information received from the core network discovery service in response to the discovery request to the UE, the service information being associated with the core network service set.

[0209] By including or configuring the communication manager 1120 according to the examples described herein, the device 1105 (e.g., a processor controlling or otherwise coupled to the receiver 1110, the transmitter 1115, the communication manager 1120, or a combination thereof) can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources.

[0210] Fig.12 A block diagram 1200 of a device 1205 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1205 can be an example of aspects of the device 1105 or 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).

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

[0212] The transmitter 1215 may provide a means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 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.

[0213] Device 1205 or its various components may be examples of units for performing various aspects of discovery in a service-based wireless system as described herein. For example, communication manager 1220 may include discovery service manager 1225, discovery request manager 1230, service information manager 1235, or any combination thereof. Communication manager 1220 may be an example of various aspects of communication manager 1120, as described herein. In some examples, communication manager 1220 or its various components may be configured to use or otherwise cooperate with receiver 1210, transmitter 1215, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 1220 may receive information from receiver 1210, send information to transmitter 1215, or combine with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0214] The communication manager 1220 may support wireless communication at the DU according to examples as disclosed herein. The discovery service manager 1225 may be configured as or otherwise support a unit for sending control information to the UE, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network configured to interface with a RAN associated with the DU. The discovery request manager 1230 may be configured as or otherwise support a unit for transmitting a discovery request to the core network discovery service, the discovery request including routing information received from the UE. The service information manager 1235 may be configured as or otherwise support a unit for transmitting service information received from the core network discovery service in response to the discovery request to the UE, the service information being associated with the core network service set.

[0215] Fig.13 A block diagram 1300 of a communication manager 1320 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be the communication manager 1120, the communication manager 1220, or both, as described herein. The communication manager 1320 or its various components may be examples of units for performing various aspects of discovery in a service-based wireless system as described herein. For example, the communication manager 1320 may include a discovery service manager 1325, a discovery request manager 1330, a service information manager 1335, a service request manager 1340, a service context manager 1345, a core network service manager 1350, a request capability manager 1355, a SIB manager 1360, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0216] The communication manager 1320 may support wireless communication at the DU according to the examples disclosed herein. The discovery service manager 1325 may be configured as or otherwise support a unit for sending control information to the UE, the control information indicating routing information associated with a core network discovery service for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU. The discovery request manager 1330 may be configured as or otherwise support a unit for transmitting a discovery request to the core network discovery service, the discovery request including routing information received from the UE. The service information manager 1335 may be configured as or otherwise support a unit for transmitting service information received from the core network discovery service in response to the discovery request to the UE, the service information being associated with the core network service set.

[0217] In some examples, the service request manager 1340 may be configured as or otherwise support a unit for receiving a service request indicating a core network service in a core network service set from a UE in response to service information indicating the core network service set. In some examples, the service context manager 1345 may be configured as or otherwise support a unit for sending to the UE, in response to the service request, second control information indicating a service context for communication between the UE and the core network service. In some examples, the core network service manager 1350 may be configured as or otherwise support a unit for transmitting a message received from the UE to the core network service according to the service context.

[0218] In some examples, the service request manager 1340 may be configured as or otherwise support a unit for receiving a second service request from the UE in response to service information, the second service request indicating a second core network service in the core network service set, wherein the service information includes an indication of a dependency of the core network service on the second core network service. In some examples, the service context manager 1345 may be configured as or otherwise support a unit for sending to the UE, in response to the second service request, third control information indicating a second service context for communication between the UE and the second core network service. In some examples, the core network service manager 1350 may be configured as or otherwise support a unit for transmitting a second message received from the UE to the second core network service based on the second service context, wherein the transmitted message is based on transmitting the second message.

[0219] In some examples, to support transmitting discovery requests, request capability manager 1355 may be configured as or otherwise support a unit for receiving indications of one or more requested service capabilities from a UE, wherein the service information includes a list of core network service subsets of a core network service set associated with the one or more requested service capabilities.

[0220] In some examples, service request manager 1340 may be configured as or otherwise support a unit for receiving a service request from a UE in response to service information, the service request indicating a selected core network service in a subset of core network services. In some examples, service context manager 1345 may be configured as or otherwise support a unit for sending second control information to the UE in response to the service request, the second control information indicating a service context for communication between the UE and the selected core network service. In some examples, core network service manager 1350 may be configured as or otherwise support a unit for transmitting a message received from the UE to the selected core network service according to the service context.

[0221] In some examples, to support transmitting discovery requests, the service request manager 1340 may be configured as or otherwise support a unit for receiving an indication of a core network service subset in a core network service set from a UE, wherein, for each core network service in the core network service subset, the service information includes one or more of core network service dependency information, service capabilities, a network address, or a network location.

[0222] In some examples, to support transmission of service information, the service information manager 1335 may be configured as or otherwise support a unit for sending to a UE an indication of one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in a core network service set.

[0223] In some examples, the routing information is associated with a proxy service that is configured to route discovery requests to a core network discovery service and to route service information from the core network discovery service to the UE via the DU, and transmitting the discovery request to the core network discovery service includes sending the discovery request to the proxy service, and transmitting the service information includes receiving the service information via the proxy service.

[0224] In some examples, to support sending control information, SIB manager 1360 may be configured or otherwise support means for sending a system information block message including control information.

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

[0226] Fig.14 A schematic diagram of a system 1400 including a device 1405 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1405 may be a component of or include an example of a device 1105, a device 1205, or a DU 165 as described herein. The device 1405 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. 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 1440).

[0227] The transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415, which may be able to send or receive wireless transmissions (e.g., concurrently). The transceiver 1410 may also include a modem for modulating a signal to provide a modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter), to receive a modulated signal (e.g., from one or more antennas 1415, from a wired receiver), and demodulate the signal. In some implementations, the transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various sending or output operations, or a combination thereof. In some implementations, the transceiver 1410 may include or be configured to be coupled to one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1410, or the transceiver 1410 and one or more antennas 1415, or the transceiver 1410 and one or more antennas 1415 and one or more processors or memory components (e.g., processor 1435, or memory 1425, or both) may be included in a chip or chip component installed in the device 1405. The transceiver 1410, or the transceiver 1410 and one or more antennas 1415 or a wired interface (where applicable) can be an example of a transmitter 1115, a transmitter 1215, a receiver 1110, a receiver 1210, or any combination thereof or components thereof, as described herein. In some examples, the transceiver can be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, fronthaul communication link 168).

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

[0229] Processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, ASIC, CPU, FPGA, microcontroller, programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) so that device 1405 performs various functions (e.g., functions or tasks supporting discovery in a service-based wireless system). For example, device 1405 or a component of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435, and processor 1435 and memory 1425 are configured to perform various functions described herein. Processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (e.g., an operating system, a virtual machine, or a container instance)), which may host functions (e.g., by executing code 1430) to perform functions of device 1405. The processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1405 (e.g., within the memory 1425). In some implementations, the processor 1435 may be a component of a processing system. A processing system may 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 may be passed to, for example, other systems or components of the device 1405). For example, the processing system of the device 1405 may refer to a system (e.g., the processor 1435, or the transceiver 1410, or the communication manager 1420, or other components or combinations of components of the device 1405) including various other components or subcomponents of the device 1405. The processing system of the device 1405 may interface with other components of the device 1405 and may process information (e.g., input or signal) received from other components or output information to other components. For example, a chip or modem of the device 1405 may include a processing system and an interface to output information, or obtain information, or both. The interface may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information. In some implementations, the first interface may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1405 can send information output from the chip or modem. In some implementations, the second interface may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1405 can obtain information or signal input, and the information can be passed to the processing system.A person having ordinary skill in the art will readily recognize that the first interface may also acquire information or signal input, and the second interface may also output information or signal output.

[0230] In some examples, bus 1440 may support communications of protocol layers of a protocol stack (e.g., within a protocol layer of a protocol stack). In some examples, bus 1440 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 1405, or communications performed between different components of device 1405 that may be co-located or located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one component of different components or divided between different components).

[0231] In some examples, the communication manager 1420 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 1420 can manage the transmission of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1420 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 1420 can support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0232] The communication manager 1420 may support wireless communications at the DU according to the examples disclosed herein. For example, the communication manager 1420 may be configured as or otherwise support a unit for sending control information indicating routing information associated with a core network discovery service to the UE, the core network discovery service being used for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU. The communication manager 1420 may be configured as or otherwise support a unit for communicating a discovery request including routing information received from the UE to the core network discovery service. The communication manager 1420 may be configured as or otherwise support a unit for transmitting service information received from the core network discovery service in response to the discovery request to the UE, the service information being associated with the core network service set.

[0233] By including or configuring the communication manager 1420 according to the examples described herein, the device 1405 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.

[0234] In some examples, the communication manager 1420 can be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. Although the communication manager 1420 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 can be supported or performed by the processor 1435, the memory 1425, the code 1430, the transceiver 1410, or any combination thereof. For example, the code 1430 may include instructions executable by the processor 1435 to cause the device 1405 to perform various aspects of discovery in a service-based wireless system as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0235] Fig.15 A block diagram 1500 of a device 1500 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. Device 1505 can be an example of various aspects of a discovery service 230 (e.g., a core network discovery service), as described herein. Device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. Device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

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

[0239] In some examples, the communication manager 1520, the receiver 1510, the transmitter 1515, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit system). 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, or a unit configured to or otherwise support 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 functions described herein (e.g., by executing instructions stored in the memory by the processor).

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

[0241] In some examples, communication manager 1520 can be configured to use or otherwise cooperate with receiver 1510, transmitter 1515, or both to perform various operations (e.g., receive, acquire, monitor, output, send). For example, communication manager 1520 can receive information from receiver 1510, send information to transmitter 1515, or integrate with receiver 1510, transmitter 1515, or both in combination to acquire information, output information, or perform various other operations described herein.

[0242] The communication manager 1520 may support wireless communications at a core network discovery service according to examples disclosed herein. For example, the communication manager 1520 may be configured to or otherwise support a unit for receiving a discovery request including routing information associated with a core network discovery service from a UE via a DU, the core network discovery service being used for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU. The communication manager 1520 may be configured to or otherwise support a unit for sending service information associated with a core network service set to the DU in response to the discovery request for relaying to the UE.

[0243] By including or configuring the communication manager 1520 according to the examples described herein, the device 1505 (e.g., a processor controlling or otherwise coupled to the receiver 1510, the transmitter 1515, the communication manager 1520, or a combination thereof) can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communication resources.

[0244] Fig.16 A block diagram 1600 of a device 1605 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1605 can be an example of aspects of the device 1505 or a discovery service 230 (e.g., a core network discovery service), as described herein. The device 1605 may include a receiver 1610, a transmitter 1615, and a communication manager 1620. The device 1605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0247] Device 1605, or various components thereof, may be examples of units for performing various aspects of discovery in a service-based wireless system as described herein. For example, communication manager 1620 may include discovery request manager 1625, service information manager 1630, or any combination thereof. Communication manager 1620 may be an example of various aspects of communication manager 1520 as described herein. In some examples, communication manager 1620 or various components thereof may be configured to use or otherwise cooperate with receiver 1610, transmitter 1615, or both to perform various operations (e.g., receive, acquire, monitor, output, send). For example, communication manager 1620 may receive information from receiver 1610, send information to transmitter 1615, or be integrated with receiver 1610, transmitter 1615, or both in combination to acquire information, output information, or perform various other operations as described herein.

[0248] The communication manager 1620 may support wireless communication at a core network discovery service according to examples as disclosed herein. The discovery request manager 1625 may be configured as or otherwise support a unit for receiving a discovery request from a UE via a DU, the discovery request including routing information associated with a core network discovery service for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU. The service information manager 1630 may be configured as or otherwise support a unit for sending service information associated with a core network service set to the DU in response to the discovery request for relaying to the UE.

[0249] Fig.17A block diagram 1700 of a communication manager 1720 supporting discovery in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure. The communication manager 1720 may be an example of aspects of the communication manager 1520, the communication manager 1620, or both, as described herein. The communication manager 1720 or its various components may be examples of units for performing various aspects of discovery in a service-based wireless system, as described herein. For example, the communication manager 1720 may include a discovery request manager 1725, a service information manager 1730, a service capability manager 1735, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0250] The communication manager 1720 may support wireless communication at a core network discovery service according to examples as disclosed herein. The discovery request manager 1725 may be configured as or otherwise support a unit for receiving a discovery request from a UE via a DU, the discovery request including routing information associated with a core network discovery service for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU. The service information manager 1730 may be configured as or otherwise support a unit for sending service information associated with a core network service set to the DU in response to the discovery request for relaying to the UE.

[0251] In some examples, to support receiving discovery requests, service capability manager 1735 may be configured as or otherwise support a unit for receiving indications of one or more requested service capabilities, wherein the service information includes a list of core network service subsets of a core network service set associated with the one or more requested service capabilities.

[0252] In some examples, to support receiving discovery requests, the discovery request manager 1725 can be configured as or otherwise support a unit for receiving indications of a subset of core network services of a core network service set, wherein, for each core network service in the subset of core network services, service information includes one or more core network service dependency information, service capabilities, network addresses, or network locations.

[0253] In some examples, to support sending service information, service information manager 1730 may be configured as or otherwise support a unit for sending indications of one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in a core network service set.

[0254] In some examples, the routing information is associated with a proxy service (e.g., for a proxy service) that is configured to route the discovery request to the core network discovery service and route the service information to the UE via the DU. In some examples, receiving the discovery request includes receiving the discovery request from the DU via the proxy service. In some examples, sending the service information to the DU includes sending the service information via the proxy service.

[0255] Fig.18 A schematic diagram of a system 1800 including a device 1805 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. Device 1805 may be an example or component of device 1505, device 1605, or discovery service 230 (e.g., core network discovery service) as described herein. Device 1805 may include components for two-way voice and data communications, including components for sending and receiving communications (e.g., communication manager 1820, I / O controller 1810, antenna 1815, code 1830, memory 1835, processor 1840, and transceiver 1845). These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1825) in an electronic communication manner or otherwise.

[0256] I / O controller 1810 can manage input and output signals of device 1805. I / O controller 1810 can also manage peripheral devices that are not integrated into device 1805. In some cases, I / O controller 1810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1810 can utilize a computer such as a Or other known operating systems. Additionally, or alternatively, I / O controller 1810 can represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1810 can be implemented as part of a processor (e.g., processor 1840). In some cases, a user can interact with device 1805 via I / O controller 1810 or via hardware components controlled by I / O controller 1810.

[0257] Memory 1835 may include RAM and ROM. Memory 1835 may store computer-readable, computer-executable code 1830, including instructions that, when executed by processor 1840, cause device 1805 to perform various functions described herein. Code 1830 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, code 1830 may not be directly executed by processor 1840, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1835 may include BIOS and other components that may control basic hardware or software operations (e.g., interactions with peripheral device components or devices).

[0258] Processor 1840 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, processor 1840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1840. Processor 1840 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1835) so that device 1805 performs various functions (e.g., functions or tasks supporting discovery in a service-based wireless system). For example, device 1805 or a component of device 1805 may include processor 1840 and memory 1835 coupled to processor 1840 or coupled to processor 1840, and processor 1840 and memory 1835 are configured to perform various functions described herein.

[0259] In some cases, the device 1805 may include a single antenna 1815. However, in some other cases, the device 1805 may have more than one antenna 1815, which may send or receive multiple wireless transmissions in parallel. The transceiver 1845 may communicate bidirectionally via one or more antennas 1815, a wired link, or a wireless link, as described herein. For example, the transceiver 1845 may represent a wireless transceiver set and may communicate bidirectionally with another wireless transceiver. The transceiver 1845 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1815 for transmission, and demodulating packets received from one or more antennas 1815. The transceiver 1845, or the transceiver 1845 and the one or more antennas 1815, may be an example of a transmitter 1515, a transmitter 1615, a receiver 1510, a receiver 1610, or any combination thereof or components thereof, as described herein.

[0260] The communication manager 1820 may support wireless communications at a core network discovery service according to examples disclosed herein. For example, the communication manager 1820 may be configured to or otherwise support a unit for receiving a discovery request including routing information associated with a core network discovery service from a UE via a DU, the core network discovery service being for a core network service set provided by a service-based network configured to interface with a RAN associated with the DU. The communication manager 1820 may be configured to or otherwise support a unit for sending service information associated with the core network service set to the DU in response to the discovery request for relaying to the UE.

[0261] By including or configuring the communication manager 1820 according to the examples described herein, the device 1805 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 processing power utilization.

[0262] In some examples, the communication manager 1820 can be configured to use or otherwise cooperate with the transceiver 1845, one or more antennas 1815, or any combination thereof to perform various operations (e.g., receive, monitor, transmit). Although the communication manager 1820 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1820 can be supported or performed by the processor 1840, the memory 1835, the code 1830, or any combination thereof. For example, the code 1830 may include instructions executable by the processor 1840 to cause the device 1805 to perform various aspects of discovery in a service-based wireless system as described herein, or the processor 1840 and the memory 1835 may be otherwise configured to perform or support such operations.

[0263] Fig.19 A block diagram 1900 of a device 1905 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1905 can be an example of aspects of the proxy service 235 as described herein. The device 1905 can include a receiver 1910, a transmitter 1915, and a communication manager 1920. The device 1905 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

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

[0265] The transmitter 1915 may provide for transmitting signals generated by other components of the device 1905. For example, the transmitter 1915 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 discovery in a service-based wireless system). In some examples, the transmitter 1915 may be co-located with the receiver 1910 in a transceiver module. The transmitter 1915 may utilize a single antenna or a set of multiple antennas.

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

[0267] In some examples, the communication manager 1920, the receiver 1910, the transmitter 1915, 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).

[0268] Additionally or alternatively, in some examples, the communication manager 1920, the receiver 1910, the transmitter 1915, 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 1920, the receiver 1910, the transmitter 1915, 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., a unit configured or otherwise supported to perform the functions described in the present disclosure).

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

[0270] The communication manager 1920 may support wireless communication at the proxy service according to the examples disclosed herein. For example, the communication manager 1920 may be configured to or otherwise support a unit for receiving a discovery request including routing information associated with the proxy service from the UE via the DU. The communication manager 1920 may be configured to or otherwise support a unit for sending a discovery request to a core network discovery service associated with a core network service set, the core network service set being provided by a service-based network configured to interface with a RAN associated with the DU. The communication manager 1920 may be configured to or otherwise support a unit for receiving service information associated with the core network service set from the core network discovery service in response to the discovery request. The communication manager 1920 may be configured to or otherwise support a unit for sending service information to the DU for relaying to the UE.

[0271] By including or configuring a communications manager 1920 according to the examples described herein, a device 1905 (e.g., a processor controlling or otherwise coupled to a receiver 1910, a transmitter 1915, a communications manager 1920, or a combination thereof) can support techniques for reducing processing, reducing power consumption, and more efficiently utilizing communications resources.

[0272] Fig. 20A block diagram 2000 of a device 2005 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 2005 can be an example of aspects of the device 1905 or the proxy service 235 as described herein. The device 2005 can include a receiver 2010, a transmitter 2015, and a communication manager 2020. The device 2005 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

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

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

[0275] Device 2005 or its various components may be examples of units for performing various aspects of discovery in a service-based wireless system as described herein. For example, communication manager 2020 may include discovery request manager 2025, service information manager 2030, or any combination thereof. Communication manager 2020 may be an example of aspects of communication manager 1920 as described herein. In some examples, communication manager 2020 or its various components may be configured to use or otherwise cooperate with receiver 2010, transmitter 2015, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, communication manager 2020 may receive information from receiver 2010, send information to transmitter 2015, or integrate with receiver 2010, transmitter 2015, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0276] The communication manager 2020 may support wireless communication at the proxy service according to the examples disclosed herein. The discovery request manager 2025 may be configured to or otherwise support a unit for receiving a discovery request from the UE via the DU, the discovery request including routing information associated with the proxy service. The discovery request manager 2025 may be configured to or otherwise support a unit for sending a discovery request to a core network discovery service, the core network discovery service being associated with a core network service set, the core network service set being provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU. The service information manager 2030 may be configured to or otherwise support a unit for receiving service information associated with the core network service set from the core network discovery service in response to the discovery request. The service information manager 2030 may be configured to or otherwise support a unit for sending service information to the DU for relaying to the UE.

[0277] Fig.21 A block diagram 2100 of a communication manager 2120 supporting discovery in a service-based wireless system is shown in accordance with one or more aspects of the present disclosure. The communication manager 2120 may be an example of the communication manager 1920, the communication manager 2020, or aspects of both, as described herein. The communication manager 2120 or its various components may be examples of units for performing various aspects of discovery in a service-based wireless system, as described herein. For example, the communication manager 2120 may include a discovery request manager 2125, a service information manager 2130, a service capability manager 2135, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0278] The communication manager 2120 may support wireless communication at the proxy service according to the examples disclosed herein. The discovery request manager 2125 may be configured to or otherwise support a unit for receiving a discovery request including routing information associated with the proxy service from the UE via the DU. In some examples, the discovery request manager 2125 may be configured to or otherwise support a unit for sending a discovery request to a core network discovery service associated with a core network service set, the core network service set being provided by a service-based network configured to dock with a RAN associated with the DU. The service information manager 2130 may be configured to or otherwise support a unit for receiving service information associated with the core network service set from the core network discovery service in response to the discovery request. In some examples, the service information manager 2130 may be configured to or otherwise support a unit for sending service information to the DU for relaying to the UE.

[0279] In some examples, to support receiving discovery requests, the service capability manager 2135 can be configured as or otherwise support a unit for receiving indications of one or more requested service capabilities, wherein the service information includes a list of core network service subsets of a core network service set associated with the one or more requested service capabilities.

[0280] In some examples, to support receiving discovery requests, the service information manager 2130 may be configured as or otherwise support a unit for receiving indications of a core network service subset of a core network service set, wherein, for each core network service in the core network service subset, the service information includes one or more of core network service dependency information, service functionality, a network address, or a network location.

[0281] In some examples, the service information includes one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in the core network service set.

[0282] Fig. 22 A schematic diagram of a system 2200 including a device 2205 supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 2205 may be an example of or include components of the device 1905, the device 2005, or the proxy service 235 as described herein. The device 2205 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 2220, an I / O controller 2210, an antenna 2215, code 2230, a memory 2235, a processor 2240, and a transceiver 2245. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) in an electronic communication manner or otherwise via one or more buses (e.g., bus 2225).

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

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

[0285] The processor 2240 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 2240 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 2240. The processor 2240 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 2235) so that the device 2205 performs various functions (e.g., functions or tasks supporting discovery in a service-based wireless system). For example, the device 2205 or a component of the device 2205 may include a processor 2240 and a memory 2235 coupled to or coupled to the processor 2240, and the processor 2240 and the memory 2235 are configured to perform the various functions described herein.

[0286] In some cases, the device 2205 may include a single antenna 2215. However, in some other cases, the device 2205 may have more than one antenna 2215, which may send or receive multiple wireless transmissions in parallel. The transceiver 2245 may communicate bidirectionally via one or more antennas 2215, a wired link, or a wireless link, as described herein. For example, the transceiver 2245 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 2245 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 2215 for transmission, and demodulating packets received from one or more antennas 2215. The transceiver 2245, or the transceiver 2245 and the one or more antennas 2215, may be an example of a transmitter 1915, a transmitter 2015, a receiver 1910, a receiver 2010, or any combination thereof or components thereof, as described herein.

[0287] The communication manager 2220 may support wireless communication at the proxy service according to the examples disclosed herein. For example, the communication manager 2220 may be configured to or otherwise support a unit for receiving a discovery request including routing information associated with the proxy service from the UE via the DU. The communication manager 2220 may be configured to or otherwise support a unit for sending a discovery request to a core network discovery service associated with a core network service set, the core network service being provided by a service-based network configured to interface with a RAN associated with the DU. The communication manager 2220 may be configured to or otherwise support a unit for receiving service information associated with the core network service set from the core network discovery service in response to the discovery request. The communication manager 2220 may be configured to or otherwise support a unit for sending service information to the DU for relaying to the UE.

[0288] By including or configuring the communication manager 2220 according to the examples described herein, the device 2205 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.

[0289] In some examples, the communication manager 2220 can be configured to use or otherwise cooperate with the transceiver 2245, one or more antennas 2215, or any combination thereof to perform various operations (e.g., receive, monitor, transmit). Although the communication manager 2220 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 2220 can be supported or performed by the processor 2240, the memory 2235, the code 2230, or any combination thereof. For example, the code 2230 may include instructions executable by the processor 2240 to cause the device 2205 to perform various aspects of discovery in a service-based wireless system as described herein, or the processor 2240 and the memory 2235 may be otherwise configured to perform or support such operations.

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

[0291] At 2305, the method may include receiving control information from the DU, the control information indicating routing information related to a core network discovery service for a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU. The operations of 2305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2305 may be performed by the discovery service manager 925, as described in reference to Fig. 9 described.

[0292] At 2310, the method may include sending a discovery request including routing information to the DU in response to the control information. The operations of 2310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2310 may be performed by the discovery request manager 930, as described in reference to Fig. 9 described.

[0293] At 2315, the method may include receiving service information associated with the core network service set from the DU in response to the discovery request. The operations of 2315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2315 may be performed by the service information manager 935, as described in reference to Fig. 9 described.

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

[0295] At 2405, the method may include receiving control information from the DU, the control information indicating routing information associated with a core network discovery service for a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU. The operations of 2405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2405 may be performed by the discovery service manager 925, as described in reference to Fig. 9 as described.

[0296] At 2410, the method may include, in response to the control information, sending a discovery request including routing information to the DU. The operations of 2410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2410 may be performed by the discovery request manager 930, as described in reference to Fig. 9 described.

[0297] At 2415, the method may include receiving service information associated with the core network service set from the DU in response to the discovery request. The operations of 2415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2415 may be performed by the service information manager 935, as described in reference to Fig. 9 described.

[0298] At 2420, the method may include sending a service request indicating a core network service in the core network service set to the DU in response to the service information indicating the core network service set. The operations of 2420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2420 may be performed by the service request manager 940, as described in reference to Fig. 9 described.

[0299] At 2425, the method may include receiving second control information from the DU in response to the service request, the second control information indicating a service context for communicating with the core network service. The operations of 2425 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2425 may be performed by the service context manager 945, as described in reference to Fig. 9 described.

[0300] At 2430, the method may include transmitting a message to the core network service via the DU according to the service context. The operations of 2430 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 2430 may be performed by the core network service manager 950, as described in reference to Fig. 9 described.

[0301] Fig.25 A flow chart illustrating a method 2500 for supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 2500 may be implemented by a DU or a component thereof, as described herein. For example, the operations of the method 2500 may be implemented by reference to Figures 1 to 6 and Figures 11 to 14 The DU performs the described functions. In some examples, the DU may execute a set of instructions to control the functional elements 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.

[0302] At 2505, the method may include sending control information to the UE, the control information indicating routing information associated with a core network discovery service for a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU. The operations of 2505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2505 may be performed by the discovery service manager 1325, as described in reference to Fig.13 described.

[0303] At 2510, the method may include transmitting a discovery request including routing information received from the UE to a core network discovery service. The operations of 2510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2510 may be performed by a discovery request manager 1330, as described in reference to Fig.13 described.

[0304] At 2515, the method may include transmitting to the UE service information received from the core network discovery service in response to the discovery request, the service information being associated with the core network service set. The operations of 2515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2515 may be performed by the service information manager 1335, as described in reference to Fig.13 described.

[0305] Fig.26 A flow chart illustrating a method 2600 for supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 2600 may be implemented by a DU or a component thereof, as described herein. For example, the operations of the method 2600 may be performed by a DU, as described in reference to Figures 1 to 6 and Figures 11 to 14 In some examples, the DU may execute a set of instructions to control the functional elements 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.

[0306] At 2605, the method may include sending control information to the UE, the control information indicating routing information associated with a core network discovery service for a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU. The operations of 2605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2605 may be performed by the discovery service manager 1325, as described in reference to Fig.13 described.

[0307] At 2610, the method may include transmitting a discovery request including routing information received from the UE to a core network discovery service. The operations of 2610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2610 may be performed by a discovery request manager 1330, as described in reference to Fig.13 described.

[0308] At 2615, the method may include transmitting to the UE service information received from the core network discovery service in response to the discovery request, the service information being associated with the core network service set. The operations of 2615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2615 may be performed by the service information manager 1335, as described in reference to Fig.13 described.

[0309] At 2620, the method may include, in response to service information indicating the core network service set, receiving from the UE a service request indicating a core network service in the core network service set. The operations of 2620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2620 may be performed by the service request manager 1340, as described in reference to Fig.13 described.

[0310] At 2625, the method may include sending second control information to the UE in response to the service request, the second control information indicating a service context for communication between the UE and the core network service. The operations of 2625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2625 may be performed by the service context manager 1345, as described in reference to Fig.13 described.

[0311] At 2630, the method may include transmitting the message received from the UE to the core network service according to the service context. The operations of 2630 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2630 may be performed by the core network service manager 1350, as described in reference to Fig.13 described.

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

[0313] At 2705, the method may include receiving, from the UE via the DU, a discovery request including routing information associated with a core network discovery service for a set of core network services provided by a service-based network configured to interface with a RAN associated with the DU. The operations of 2705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2705 may be performed by a discovery request manager 1725, as described in reference to Fig.17 described.

[0314] At 2710, the method may include sending service information associated with the core network service set to the DU in response to the discovery request for relaying to the UE. The operations of 2710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2710 may be performed by a service information manager 1730, as described in reference to Fig.17 described.

[0315] Fig.28 A flow chart illustrating a method 2800 for supporting discovery in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 2800 may be implemented by a proxy service or a component thereof, as described herein. For example, the operations of the method 2800 may be implemented by reference to Figures 1 to 6 and Figures 19 to 22 In some examples, the proxy service may execute an instruction set to control the functional elements of the proxy service to perform the described functions. Additionally or alternatively, the proxy service may use dedicated hardware to perform various aspects of the described functions.

[0316] At 2805, the method may include receiving a discovery request including routing information associated with the proxy service from the UE via the DU. The operations of 2805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2805 may be performed by the discovery request manager 2125, as described in reference to Fig.21 described.

[0317] At 2810, the method may include sending a discovery request to a core network discovery service associated with a core network discovery service set, the core network service set provided by a service-based network configured to interface with a RAN associated with the DU. The operations of 2810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2810 may be performed by a discovery request manager 2125, as described in reference to Fig.21 described.

[0318] At 2815, the method may include receiving service information associated with the core network service set from the core network discovery service in response to the discovery request. The operations of 2815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2815 may be performed by the service information manager 2130, as described in reference to Fig.21 described.

[0319] At 2820, the method may include sending the service information to the DU for relaying to the UE. The operations of 2820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2820 may be performed by the service information manager 2130, as described in reference to Fig.21 described.

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

[0321] Aspect 112: A method for wireless communication at a UE, comprising: receiving control information from a DU, the control information indicating routing information associated with a core network discovery service, the core network discovery service being used for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU; in response to the control information, sending a discovery request including the routing information to the DU; and in response to the discovery request, receiving service information associated with the core network service set from the DU.

[0322] Aspect 234: The method according to Aspect 1 also includes: in response to service information indicating a core network service set, sending a service request indicating a core network service in the core network service set to the DU; in response to the service request, receiving second control information indicating a service context for communicating with the core network service from the DU; and transmitting a message with the core network service via the DU based on the service context.

[0323] Aspect 356: A method according to Aspect 2, wherein the service information includes an indication of the dependency of the core network service on a second core network service, the method further comprising: sending a second service request to the DU based on the dependency, the second service request indicating the second core network service in the core network service set; receiving third control information from the DU in response to the second service request, the third control information indicating a second service context for communicating with the second core network service; and transmitting a second message to the second core network service via the DU and based on the second service context, wherein the transmitted message is based on transmitting the second message.

[0324] Aspect 478: A method according to any one of Aspects 1 to 3, wherein sending a discovery request includes: sending an indication of one or more requested service capabilities, wherein the service information includes a list of core network service subsets in a core network service set associated with the one or more requested service capabilities.

[0325] Aspect 5910: The method according to Aspect 4 further includes: sending a service request indicating a selected core network service from a subset of core network services to the DU in response to the service information; receiving second control information indicating a service context for communicating with the selected core network service from the DU in response to the service request; and transmitting a message to the selected core network service via the DU based on the service context.

[0326] Aspect 61112: A method according to any one of Aspects 1 to 5, wherein the control information indicates a core network service set, and wherein sending a discovery request includes: sending an indication of a subset of core network services in the core network service set, wherein, for each core network service in the core network service subset, the service information includes one or more of core network service dependency information, service capabilities, network address, or network location.

[0327] Aspect 71314: A method according to any one of Aspects 1 to 6, wherein receiving service information includes: receiving one or more indications of core network service dependency information, service capabilities or network locations associated with one or more core network services in a core network service set.

[0328] Aspect 81516: A method according to any one of aspects 1 to 7, wherein the routing information is associated with a proxy service configured to route the discovery request to the core network discovery service.

[0329] Aspect 91718: A method according to any one of aspects 1 to 8, wherein receiving control information includes: receiving a SIB message including control information.

[0330] Aspect 10: The method according to any one of aspects 1 to 9, wherein the discovery request is sent to the DU to be relayed to a network address associated with a core network discovery service, the network address being based on routing information.

[0331] Aspect 11: The method according to any one of aspects 1 to 10, wherein each core network service in the core network service set is associated with a corresponding application programming interface in the plurality of application programming interfaces.

[0332] Aspect 12: A method for wireless communication at a DU, comprising: sending control information to a UE, the control information indicating routing information associated with a core network discovery service, the core network discovery service being used for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU; transmitting a discovery request including routing information received from the UE to the core network discovery service; and transmitting service information received from the core network discovery service in response to the discovery request to the UE, the service information being associated with the core network service set.

[0333] Aspect 13: The method according to Aspect 12 also includes: receiving a service request indicating a core network service in the core network service set from a UE in response to service information indicating a core network service set; sending second control information indicating a service context for communication between the UE and the core network service to the UE in response to the service request; and transmitting a message received from the UE to the core network service according to the service context.

[0334] Aspect 14: The method according to Aspect 13 further includes: receiving a second service request from the UE in response to service information, the second service request indicating a second core network service in the core network service set, wherein the service information includes an indication of the dependency of the core network service on the second core network service; sending third control information indicating a second service context for communication between the UE and the second core network service to the UE in response to the second service request; and transmitting a second message received from the UE to the second core network service based on the second service context, wherein the transmitted message is based on transmitting the second message.

[0335] Aspect 15: A method according to any one of Aspects 12 to 14, wherein transmitting a discovery request includes: receiving an indication of one or more requested service capabilities from a UE, wherein the service information includes a list of core network service subsets in a core network service set associated with the one or more requested service capabilities.

[0336] Aspect 16: The method according to Aspect 15 also includes: receiving a service request from a UE in response to service information, the service request indicating a selected core network service in a core network service subset; sending second control information to the UE in response to the service request, the second control information indicating a service context for communication between the UE and the selected core network service; and transmitting a message received from the UE to the selected core network service according to the service context.

[0337] Aspect 17: A method according to any one of Aspects 12 to 16, wherein the control information indicates a core network service set, and wherein transmitting a discovery request further comprises: receiving an indication of a core network service subset of the core network service set from a UE, wherein, for each core network service in the core network service subset, the service information includes one or more of core network service dependency information, service capabilities, network address, or network location.

[0338] Aspect 18: A method according to any one of Aspects 12 to 17, wherein transmitting service information includes: sending an indication of one or more of core network service dependency information, service capabilities or network locations associated with one or more core network services in a core network service set to the UE.

[0339] Aspect 19: A method according to any one of Aspects 12 to 18, wherein the routing information is associated with a proxy service, the proxy service is configured to route the discovery request to the core network discovery service, and route the service information from the core network discovery service to the UE via the DU, and transmitting the discovery request to the core network discovery service includes: sending the discovery request to the proxy service, and transmitting the service information includes: receiving the service information via the proxy service.

[0340] Aspect 20: The method according to any one of aspects 12 to 19, wherein sending the control information comprises: sending a SIB message including the control information.

[0341] Aspect 21: The method according to any one of aspects 12 to 20, wherein each core network service in the core network service set is associated with a corresponding application programming interface in the plurality of application programming interfaces.

[0342] Aspect 22: A method for wireless communication at a core network discovery service, comprising: receiving a discovery request from a UE via a DU, the discovery request including routing information associated with a core network discovery service, the core network discovery service being used for a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU; and in response to the discovery request, sending service information associated with the core network service set to the DU for relay to the UE.

[0343] Aspect 23: A method according to Aspect 22, wherein receiving a discovery request includes: receiving an indication of one or more requested service capabilities, wherein the service information includes a list of core network service subsets in a core network service set associated with the one or more requested service capabilities.

[0344] Aspect 24: A method according to any one of Aspects 22 to 23, wherein receiving a discovery request includes: receiving an indication of a core network service subset in a core network service set, wherein, for each core network service in the core network service subset, service information includes one or more of core network service dependency information, service capabilities, network addresses, or network locations.

[0345] Aspect 25: A method according to any one of Aspects 22 to 24, wherein sending service information comprises: sending an indication of one or more of core network service dependency information, service capabilities or network locations associated with one or more core network services in a core network service set.

[0346] Aspect 26: A method according to any one of Aspects 22 to 25, wherein the routing information is associated with a proxy service, the proxy service is configured to route the discovery request to the core network discovery service and route the service information to the UE via the DU, receiving the discovery request includes: receiving the discovery request from the DU via the proxy service, and sending the service information to the DU includes: sending the service information via the proxy service.

[0347] Aspect 27: A method for wireless communication at a proxy service, comprising: receiving a discovery request including routing information associated with the proxy service from a UE via a DU; sending the discovery request to a core network discovery service associated with a core network service set provided by a service-based network, the service-based network being configured to interface with a RAN associated with the DU; receiving service information associated with the core network service set from the core network discovery service in response to the discovery request; and sending the service information to the DU for relaying to the UE.

[0348] Aspect 28: A method according to Aspect 27, wherein receiving a discovery request includes: receiving an indication of one or more requested service capabilities, wherein the service information includes a list of core network service subsets in a core network service set associated with the one or more requested service capabilities.

[0349] Aspect 29: A method according to any one of Aspects 27 to 28, wherein receiving a discovery request includes: receiving an indication of a core network service subset in a core network service set, wherein, for each core network service in the core network service subset, service information includes one or more of core network service dependency information, service capabilities, network addresses, or network locations.

[0350] Aspect 30: The method according to any one of Aspects 27 to 29, wherein the service information includes one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in the core network service set.

[0351] Aspect 31: An apparatus for performing 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, so that the apparatus performs the method described in any one of Aspects 1 to 11.

[0352] Aspect 32: An apparatus for performing wireless communication at a UE, comprising at least one unit for executing the method described in any one of aspects 1 to 11.

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

[0354] Aspect 34: 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, so that the apparatus performs the method described in any one of aspects 12 to 21.

[0355] Aspect 35: An apparatus for wireless communication at a DU, comprising at least one method for performing any one of aspects 12 to 21.

[0356] Aspect 36: 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 of any one of aspects 12 to 21.

[0357] Aspect 37: An apparatus for wireless communication at a core network discovery service, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor, so that the apparatus performs the method described in any one of Aspects 22 to 26.

[0358] Aspect 38: An apparatus for wireless communication at a core network discovery service, comprising at least one unit for performing the method of any one of Aspects 22 to 26.

[0359] Aspect 39: A non-transitory computer-readable medium storing code for wireless communication at a core network discovery service, the code comprising instructions executable by a processor to perform the method of any one of aspects 22 to 26.

[0360] Aspect 40: An apparatus for wireless communication at a proxy service, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor, so that the apparatus performs the method described in any one of Aspects 27 to 30.

[0361] Aspect 41: An apparatus for wireless communication at a proxy service, comprising at least one unit for executing the method of any one of Aspects 27 to 30.

[0362] Aspect 42: A non-transitory computer-readable medium storing code for wireless communication at a proxy service, the code comprising instructions executable by a processor to perform the method of any one of aspects 27 to 30.

[0363] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. In addition, aspects of two or more methods may be combined in a method.

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

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

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

[0367] 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 these instructions or codes. 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 in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

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

[0369] 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 referring 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."

[0370] The terms "determine" or "determining" encompass a 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), determining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Furthermore, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other similar actions.

[0371] In the 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 that distinguishes between the 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, regardless of the second reference numeral or other subsequent reference numerals.

[0372] 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 "as an example, instance, or illustration" and is not "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, these technologies 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.

[0373] The description herein is provided to enable one of ordinary skill in the art to make 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 should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving control information from a distributed unit, the control information indicating routing information associated with a core network discovery service for 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; In response to the control information, sending a discovery request including the routing information to the distributed unit; as well as In response to the discovery request, service information associated with the core network service set is received from the distributed unit.

2. The method according to claim 1, further comprising: In response to the service information indicating the core network service set, sending a service request indicating a core network service in the core network service set to the distributed unit; receiving, in response to the service request, from the distributed unit, second control information indicating a service context for communicating with the core network service; as well as Messages are transmitted via the distributed unit and the core network service according to the service context.

3. The method according to claim 2, wherein: The service information includes an indication of the dependency of the core network service on a second core network service, the method further comprising: Based on the dependency, sending a second service request to the distributed unit, the second service request indicating the second core network service in the core network service set; receiving, in response to the second service request, from the distributed unit, third control information indicating a second service context for communicating with the second core network service; and According to the second service context, a second message is transmitted via the distributed unit and the second core network service, wherein transmitting the message is based on transmitting the second message.

4. The method according to claim 1, wherein: Sending the discovery request includes: An indication of one or more requested service capabilities is sent, wherein the service information includes a list of a core network service subset of the core network service set associated with the one or more requested service capabilities.

5. The method according to claim 4, further comprising: sending, in response to the service information, to the distributed unit a service request indicating a selected core network service from the subset of core network services; receiving second control information from the distributed unit in response to the service request, the second control information indicating a service context for communicating with the selected core network service; as well as Messages are communicated with the selected core network service via the distributed unit according to the service context.

6. The method according to claim 1, wherein: The control information indicates the core network service set, and wherein sending the discovery request comprises: An indication of a core network service subset of the core network service set is sent, wherein, for each core network service in the core network service subset, the service information includes one or more of core network service dependency information, service capabilities, network address, or network location.

7. The method according to claim 1, wherein: Receiving the service information includes: An indication of one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in the set of core network services is received.

8. The method according to claim 1, wherein: The routing information is associated with a proxy service, and the proxy service is configured to route the discovery request to the core network discovery service.

9. The method according to claim 1, wherein: Receiving the control information includes: A system information block message including the control information is received.

10. The method according to claim 1, wherein: The discovery request is sent to the distributed unit for relaying to a network address associated with the core network discovery service, the network address being based on the routing information.

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

12. A method for wireless communication at a distributed unit, comprising: sending control information to a user equipment (UE), the control information indicating routing information associated with a core network discovery service for 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; transmitting, to the core network discovery service, a discovery request including routing information received from the UE; as well as Service information received from the core network discovery service in response to the discovery request is transmitted to the UE, the service information being associated with the core network service set.

13. The method according to claim 12, further comprising: receiving, in response to the service information indicating the core network service set, from the UE a service request indicating a core network service of the core network service set; In response to the service request, sending to the UE second control information indicating a service context for communication between the UE and the core network service; as well as A message received from the UE is delivered to the core network service according to the service context.

14. The method according to claim 13, further comprising: receiving, in response to the service information, from the UE a second service request indicating a second core network service in the set of core network services, wherein the service information includes an indication of a dependency of the core network service on the second core network service; sending, in response to the second service request, third control information to the UE indicating a second service context for communication between the UE and the second core network service; and According to the second service context, a second message received from the UE is transmitted to the second core network service, wherein transmitting the message is based on transmitting the second message.

15. The method according to claim 12, wherein: Transmitting the discovery request includes: An indication of one or more requested service capabilities is received from the UE, wherein the service information includes a list of core network service subsets of the core network service set associated with the one or more requested service capabilities.

16. The method according to claim 15, further comprising: receiving, in response to the service information, from the UE a service request indicating a selected core network service of the subset of core network services; In response to the service request, sending to the UE second control information indicating a service context for communication between the UE and the selected core network service; as well as A message received from the UE is delivered to the selected core network service according to the service context.

17. The method according to claim 12, wherein: The control information indicates the set of core network services, and wherein transmitting the discovery request further comprises: An indication of a core network service subset of the core network service set is received from the UE, wherein, for each core network service in the core network service subset, the service information includes one or more of core network service dependency information, service capabilities, network address, or network location.

18. The method according to claim 12, wherein: Transmitting the service information includes: An indication of one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in the core network service set is sent to the UE.

19. The method according to claim 12, wherein: The routing information is associated with a proxy service, the proxy service is configured to route the discovery request to the core network discovery service, and route the service information from the core network discovery service to the UE via the distributed unit, and transmitting the discovery request to the core network discovery service includes: sending the discovery request to the proxy service, and transmitting the service information includes: receiving the service information via the proxy service.

20. The method according to claim 12, wherein: Sending the control information includes: A system information block message including the control information is sent.

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

22. A method for wireless communication over a core network discovery service, comprising: receiving, via a distributed unit, a discovery request from a user equipment (UE), the discovery request including routing information associated with the core network discovery service for 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; as well as In response to the discovery request, service information associated with the core network service set is sent to the distributed unit for relaying to the UE.

23. The method according to claim 22, wherein: Receiving the discovery request includes: An indication of one or more requested service capabilities is received, wherein the service information includes a list of a subset of core network services in the set of core network services associated with the one or more requested service capabilities.

24. The method according to claim 22, wherein: Receiving the discovery request includes: An indication of a subset of core network services in the set of core network services is received, wherein, for each core network service in the subset of core network services, the service information includes one or more of core network service dependency information, service capabilities, a network address, or a network location.

25. The method according to claim 22, wherein: Sending the service information includes: An indication of one or more of core network service dependency information, service capabilities, or network locations associated with one or more core network services in the set of core network services is sent.

26. The method of claim 22, wherein: The routing information is associated with a proxy service, the proxy service is configured to route the discovery request to the core network discovery service, and to route the service information to the UE via the distributed unit, wherein receiving the discovery request comprises: receiving the discovery request from the distributed unit via the proxy service, and wherein sending the service information to the distributed unit comprises: sending the service information via the proxy service.

27. 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: receiving control information from a distributed unit, the control information indicating routing information associated with a core network discovery service for 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; In response to the control information, sending a discovery request including the routing information to the distributed unit; and In response to the discovery request, service information associated with the core network service set is received from the distributed unit.

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: In response to the service information indicating the core network service set, sending a service request indicating a core network service in the core network service set to the distributed unit; receiving, in response to the service request, from the distributed unit, second control information indicating a service context for communicating with the core network service; as well as Messages are transmitted via the distributed unit and the core network service according to the service context.

29. The device according to claim 28, wherein The service information includes an indication of a dependency of the core network service on a second core network service, and wherein the instructions are further executable by the processor to cause the apparatus to perform the following operations: Based on the dependency, sending a second service request to the distributed unit, the second service request indicating the second core network service in the core network service set; receiving, in response to the second service request, from the distributed unit, third control information indicating a second service context for communicating with the second core network service; and and transmitting a second message via the distributed unit and the second core network service according to the second service context, wherein the instructions are executable by the processor to cause the device to transmit the message based on transmitting the second message.

30. The device according to claim 27, wherein: In order to send the discovery request, the instructions may be executed by the processor to cause the device to perform the following operations: sending an indication of one or more requested service capabilities, wherein the service information comprises a list of core network service subsets of the core network service set associated with the one or more requested service capabilities; sending, in response to the service information, to the distributed unit a service request indicating a selected core network service from the subset of core network services; receiving second control information from the distributed unit in response to the service request, the second control information indicating a service context for communicating with the selected core network service; and Messages are communicated with the selected core network service via the distributed unit according to the service context.

Images