Service group in service-based wireless system

Abstract

Methods, systems, and devices for wireless communication are described. In a service-based network, a core network service group may share user equipment (UE) credentials or network subscriptions. Signaling between the UE and the service-based network (e.g., via a distributed unit) enables the UE to establish a service context for communicating with multiple core network services in the same service group. A UE may receive control signaling from a network indicating a service group provided by a service-based network. The control signaling may indicate services included in each service group and how to access the service group. The UE may send an access request to the network indicating the selected service group, and in response, the network may indicate a service context for communicating with a service included in the service group. The UE may access different services in the service group using the same service context.

Description

Cross-references

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

[0002] The following relates to wireless communications, including service groups in a service-based wireless system. Background Art

[0003] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems, such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems, fifth generation (5G) systems that may be referred to as new radio (NR) systems, and sixth generation (6G) systems. These systems may use technologies 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 communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0004] The described technology relates to improved methods, systems, devices and apparatuses for supporting service groups in a service-based wireless system. For example, the described technology provides an indication of a service group in a service-based network and communication with the service group. In a service-based network, a set of core network services (e.g., a service group) can share a user equipment (UE) certificate or network subscription (e.g., can be accessed via the same UE certificate or network subscription). For example, a single network operator can provide multiple service groups associated with multiple UE certificates, or multiple operators can provide multiple service groups, each service group associated with a respective certificate. The UE can establish a wireless connection with the service group in the service-based network. Signaling between the UE and the service-based network (e.g., via a distributed unit (DU)) enables the UE to establish a service context for communicating with multiple core network services in the same service group. For example, the service context can be a security context (e.g., authentication information or key agreement) or a network subscription. For example, the UE can establish a connection with the service-based network via the DU, and receive control signaling from the service-based network via the DU indicating a set of multiple service groups provided by the network. The control signaling may indicate the core network services included in each service group and how to access the service group (e.g., certificates or network subscriptions for accessing the service group). The UE may send an access request indicating the selected service group to the network, and in response, the network may indicate a service context for communicating with the core network services included in the service group. For example, the service context may be a primary security context from which the security context for each core network service in the service group may be derived. Thus, the UE may use the same service context to access different core network services in the service group.

[0005] A method for wireless communication at a UE is described. The method may include: identifying first control information indicating a set of multiple service groups provided by a service-based network configured to connect a radio access network (RAN) associated with a DU, wherein the first control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group; sending an access request in response to the first control information, the access request indicating a first service group in the set of multiple service groups and a corresponding network certificate for the first service group; receiving second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services of the first service group; and transmitting a message with a core network service in the corresponding set of core network services of the first service group according to the service context.

[0006] A device for wireless communication at a UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor so that the device: identifies first control information, the first control information indicating a set of multiple service groups provided by a service-based network configured to connect a radio access network (RAN) associated with a DU, wherein the first control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group; sends an access request in response to the first control information, the access request indicating a first service group in the multiple service groups and a corresponding network certificate for the first service group; receives second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services of the first service group; and transmits a message to a core network service in a corresponding set of core network services of the first service group according to the service context.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for identifying first control information indicating a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with a DU, wherein the first control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group; a unit for sending an access request in response to the first control information, the access request indicating a first service group in the multiple service groups and a corresponding network certificate for the first service group; a unit for receiving second control information in response to the access request, the second control information indicating a service context for communicating with the corresponding set of core network services of the first service group; and a unit for transmitting a message to a core network service in the corresponding set of core network services of the first service group according to the service context.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: identifying first control information indicating a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with a DU, wherein the first control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group; sending an access request in response to the first control information, the access request indicating a first service group in the multiple service groups and a corresponding network certificate for the first service group; receiving second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services of the first service group; and transmitting a message with a core network service in the corresponding set of core network services of the first service group according to the service context.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the service context includes a primary security context associated with a first service group and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, units, or instructions for performing the following operations: based on the primary security context, determining a corresponding security context for each core network service included in the first service group.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, transmitting a message in accordance with a service context may include operations, features, elements, or instructions for performing the following operations: transmitting the message in accordance with a determined corresponding security context for a core network service.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the master security context includes authentication information, key agreement, or both.

[0012] Some examples of methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for transmitting a second message with a second core network service in the corresponding set of core network services according to the service context.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, based on transmitting the message with the core network service, the core network service may be configured to invoke a second core network service included in the first service group.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the core network service includes a data service and the second core network service includes a mobile service.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending a second access request in response to first control information, the second access request indicating a second service group in a set of multiple service groups and a corresponding network certificate for the second service group; receiving third control information in response to the second access request, the third control information indicating a second service context for communicating with a corresponding core network service set of the second service group, and transmitting a second message to a second core network service of the corresponding core network service set included in the second service group based on the second service context.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second core network service may be configured to invoke a third core network service included in the first service group based on transmitting the second message with the second core network service.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the core network service includes a data service and the third core network service includes a mobile service.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying first control information may include operations, features, units, or instructions for performing the following operations: determining that the first service group does not communicate with the second service group, wherein sending the second access request can be based on determining that the first service group does not communicate with the second service group.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying the first control information may include operations, features, units, or instructions for performing the following operations: identifying whether each service group in the set of the multiple service groups is capable of communicating with one or more other service groups in the set of the multiple service groups.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying first control information can include operations, features, units, or instructions for performing the following operations: identifying a corresponding network subscription associated with each service group in the set of the multiple service groups, wherein sending the access request can be based on the corresponding network subscription associated with the first service group.

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

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

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

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

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying first control information may include operations, features, means, or instructions for performing the following operations: receiving the first control information via a wireless connection between the UE and the DU.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying first control information may include operations, features, means, or instructions for accessing the first control information from local storage at the UE.

[0027] A method for wireless communication at a DU is described. The method may include receiving an access request from a UE, the access request indicating a first service group in a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein each service group in the set of multiple service groups includes a corresponding core network service set, wherein each service group in the set of multiple service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request also indicates the corresponding network certificate for the first service group; sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding core network service set of the first service group; and transmitting a message received from the UE according to the service context to a core network service in the corresponding core network service set of the first service group.

[0028] An apparatus for wireless communication at a DU is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receiving an access request from a UE, the access request indicating a first service group in a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein each service group in the set of multiple service groups includes a corresponding core network service set, wherein each service group in the set of multiple service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request also indicates the corresponding network certificate for the first service group, sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding core network service set of the first service group, and transmitting a message received from the UE according to the service context to a core network service in the corresponding core network service set of the first service group.

[0029] Another apparatus for wireless communication at a DU is described. The apparatus may include means for receiving an access request from a UE, the access request indicating a first service group in a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein each service group in the set of multiple service groups includes a corresponding core network service set, wherein each service group in the set of multiple service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request also indicates the corresponding network certificate for the first service group; means for sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding core network service set of the first service group, and means for transmitting a message received from the UE according to the service context to a core network service in the corresponding core network service set of the first service group.

[0030] A non-transitory computer-readable medium storing code for wireless communication at a DU is described. The instructions may be executable by a processor to cause the processor to perform the following operations: receiving an access request from a UE, the access request indicating a first service group in a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein each service group in the set of multiple service groups includes a corresponding core network service set, wherein each service group in the set of multiple service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request also indicates the corresponding network certificate for the first service group, sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding core network service set of the first service group, and transmitting a message received from the UE according to the service context to a core network service in the corresponding core network service set of the first service group.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a service context includes a primary security context associated with a first service group and a respective security context for each core network service included in the first service group may be based on the primary security context.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the master security context includes authentication information, key agreement, or both.

[0033] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, transmitting a message in accordance with a service context may include operations, features, means, or instructions for transmitting a message in accordance with a corresponding security context for a core network service.

[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: transmitting a second message received from the UE according to the service context to a second core network service in the corresponding core network service set.

[0035] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the core network service may be configured to, based on transmitting the message with the core network service, invoke a second core network service included in the first service group.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the core network service includes a data service and the second core network service includes a mobile service.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a second access request from a UE, the second access request indicating a second service group in a set of multiple service groups and a corresponding network certificate for the second service group; sending second control information to the UE and in response to the second access request, the second control information indicating a second service context for communicating with a corresponding set of core network services of the second service group, and transmitting a second message received from the UE according to the second service context to a second core network service in the corresponding set of core network services included in the second service group.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second core network service may be configured to invoke a third core network service included in the first service group based on a second message transmitted to the second core network service.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second core network service includes a data service and the third core network service includes a mobile service.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first service group does not communicate with the second service group.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending second control information indicating a set of multiple service groups to the UE, wherein the second control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second control information may include an operation, feature, unit, or instruction for performing the following operations: sending an indication of whether each service group in a set of multiple service groups is able to communicate with one or more other service groups in the set of multiple service groups.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second control information can include operations, features, units, or instructions for performing the following operations: sending an indication of a corresponding network subscription associated with each service group in a set of multiple service groups, wherein receiving the access request can be based on the corresponding network subscription associated with the first service group.

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

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

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

[0047] Figure 1 An example of a wireless communication system supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0048] Figure 2 An example of a wireless communication system supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown.

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

[0050] Figure 4 An example of a wireless communication system supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0051] Figure 5 An example of a system diagram for supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0052] Figure 6 An example of a process flow for supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0053] Figure 7 and Figure 8 A block diagram of a device supporting a service group in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0054] Fig. 9 A block diagram of a communication manager supporting service groups in a service-based wireless system is shown according to one or more aspects of the present disclosure.

[0055] Fig.10 A diagram of a system including devices supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0056] Fig.11 and Fig.12 A block diagram of a device supporting a service group in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0057] Fig.13 A block diagram of a communication manager supporting service groups in a service-based wireless system is shown according to one or more aspects of the present disclosure.

[0058] Fig.14 A diagram of a system including devices supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown.

[0059] Figures 15 to 18 A flow chart illustrating a method for supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

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

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

[0062] In some examples, groups of core network services (e.g., service groups) can share UE certificates or network subscriptions (e.g., can be accessed via the same UE certificates or network subscriptions). For example, a single network operator can provide multiple service groups associated with multiple UE certificates, or multiple operators can provide multiple service groups, each associated with a respective certificate. Conversely, in some systems, the entire operator system can be grouped, and slices can be used to support one type of service at the Internet Protocol (IP) layer. Additionally or alternatively, in some systems, the network services provided by slices can be defined above Layer 2 (e.g., in Radio Link Control (RLC)).

[0063] In some examples described herein, each service group may include a set of multiple core network services. The UE may establish a wireless connection with a service group in a service-based network. Signaling between the UE and the service-based network (e.g., via a distributed unit (DU)) enables the UE to establish a service context for communicating with multiple core network services in the same service group. For example, the service context may be a security context (e.g., authentication information or key agreement) or a network subscription.

[0064] For example, the UE may establish a connection with a service-based network through the DU, and receive control signaling from the service-based network through the DU, the control signaling indicating a set of multiple service groups provided by the service-based network. The control signaling may indicate the core network services included in each service group and how to access the service group (e.g., a certificate or network subscription for accessing the service group). The UE may send an access request indicating the selected service group to the network, and in response, the network may indicate a service context for communicating with the core network services included in the service group. For example, the service context may be a primary security context from which the security context of each core network service in the service group may be derived. Thus, the UE may use the same service context to access different core network services in the service group. Core network services within a group depend on other core network services in the group (e.g., data services may depend on mobile services). Therefore, a communication with a core network service may involve communicating with other services in the same group (e.g., automatically).

[0065] Aspects of the disclosure are initially described in the context of wireless communication systems. Aspects of the disclosure are also illustrated and described by and with reference to system diagrams, process flows, apparatus diagrams, and flowcharts relating to service groups in a service-based wireless system.

[0066] Figure 1 An example of a wireless system 100 supporting service groups 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-aPro network), or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

[0068] 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 may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, such as Figure 1 shown.

[0069] 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 any other 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 this 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 this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, with reference to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosures that UE 115, network entity 105, apparatus, device, computing system, etc. are nodes. For example, disclosures that UE 115 is configured to receive information from network entity 105 also disclose that the first node is configured to receive information from the second node.

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

[0071] 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 radio access network services (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 the one or more UE 115 services and the corresponding CN / RAN services 185. In some cases, a common API framework may be defined for both the CN / RAN services 185 and the UE 115. Based on the authorization, CN / RAN services 185 may be restricted to be available only to UE 115 or only to other network services.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0111] 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 the corresponding core network service 215 of the service-based network 205.

[0112] 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 215 with the corresponding core network service in order to exchange communications associated with various network functions supported by the corresponding core network service 215. In other words, the wireless communication system 200 may enable the UE 115-a to "subscribe" to the corresponding core network service 215 on a per-order basis, based on the needs or requirements of the UE 115-a. In this regard, different UEs 115 within the wireless communication system 200 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.

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

[0114] 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 may include a core network mobility service that hosts information and provides signaling that facilitates the geographic mobility of the UE 115-a throughout the wireless communication system. As another example, the second core network service 215-b may include a security service that provides security and encryption services to subscribing UEs 115 within the wireless communication system 200.

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

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

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

[0118] Compared to some other types of wireless systems, such as networks that instead exhibit a relatively more vertical layered architecture that includes multiple "layers" of different devices that perform the functions of the network, Figure 2 The service-based wireless communication system 200 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.

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

[0120] In this regard, the wireless communication system 200 may illustrate an example of a merged cloud-native platform configured to host CN and RAN services, which may simplify protocols and reduce duplication of processing operations between CN and RAN (e.g., reallocation of CN and RAN 210 services). In other words, the fusion of RAN 210 and CN functions may reduce duplication of operations and functions at different layers to serve one UE.

[0121] 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 scale independently by independently increasing or decreasing the resources allocated across the corresponding core network service 215.

[0122] 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 the given core network service).

[0123] As described herein, a group of core network services 215 may share a certificate or network subscription for a given UE 115-a. For example, a service group may be a group of independently addressable core network services 215. In some cases, a service group may provide services as services, meaning that the service group may present a unified interface to other core network services 215 or service groups. For example, a single network operator may provide multiple service groups associated with multiple UE certificates, or multiple operators may provide multiple service groups, each associated with a respective certificate. Each service group may include a set of multiple core network services 215. A UE 115-a may establish a wireless connection with a service group in a service-based network 205. A UE 115-a may establish a service context for communicating with multiple core network services 215 in the same service group. For example, a service context may be a security context (e.g., authentication information or key agreement) or a network subscription.

[0124] For example, the UE 115-a may establish a connection with the service-based network 205 via the network entity 105-a. In some cases, the UE 115-a may receive control signaling from the service-based network 205 via the network entity 105-a, the control signaling indicating a set of multiple service groups provided by the service-based network 205. The control signaling may indicate the services included in each service group and how to access the service group (e.g., a certificate or network subscription for accessing the service group). In some cases, a set of multiple service groups provided by the service-based network may be pre-configured, and the UE 115-a may identify a pre-configured set of service groups, for example, by accessing a memory location storing an identification of the pre-configured set of service groups. For example, the pre-configuration of the set of service groups may be stored in a universal user identity module (USIM) of the UE 115-a. The UE 115-a may send an access request indicating the selected service group to the network, and in response, the network may indicate a service context for communicating with the services included in the service group. For example, the service context may be a master security context from which the security context of each core network service in the service group may be derived. Thus, the UE 115-a may use the same service context to access different core network services in the service group.

[0125] Figure 3An example of a network architecture 300 for supporting service groups 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 a 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 a corresponding mid-range communication link 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.

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

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

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

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

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

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

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

[0133] Figure 4 An example of a wireless communication system 400 supporting service groups for a service-based wireless system according to one or more aspects of the present disclosure is shown. Aspects of the wireless communication system 400 may implement or be implemented by aspects of the wireless communication system 100 or the wireless communication system 200. In some implementations, the wireless communication system 400 illustrates an exemplary service-based wireless communication system, such as with reference to Figure 1 and Figure 2 Describe the system.

[0134] The wireless communication system 400 may include one or more UEs 115 (e.g., UE 115-c), one or more DUs 165-b (e.g., located at the network entity 105), and a service-based network 205-a. In some aspects, the service-based network 205-a may be configured to communicate or interface with the DUs 165-b. The service-based network 205-a may support or provide a set of service groups 405 (e.g., a first service group 405-a and a second service group 405-b), and each service group 405 may include a set of core network services (e.g., reference Figure 2 4. The core network services 215 described herein may include the core network services 215 described herein. For example, the first service group 405-a may include application services 410-a, subscription services 415-a, connectivity services 420-a, mobile services 425-a, and data services 430-a, and the second service group 405-b may include application services 410-b, subscription services 415-b, connectivity services 420-b, mobile services 425-b, and data services 430-b. In some examples, as described herein, the service-based network 205-a may include or be associated with a cloud platform, wherein the respective core network services 215 are hosted at respective network addresses in the cloud platform.

[0135] UE 115-c may communicate with DU 165-b using one or more communication links 220-a, which may include an example of an access link (e.g., a Uu link). Communication link 220-a may include a bidirectional link, which may include both uplink communication and downlink communication. Similarly, DU 165-b may be configured to communicate (e.g., an interface) with a service-based network 205-a via one or more communication links (e.g., communication link 225-a), wherein communication link 225-a may be configured to facilitate bidirectional communication between DU 165-b and each of the various core network services (e.g., application service 410-a, subscription service 415-a, connection service 420-a, mobile service 425-a, data service 430-a, application service 410-b, subscription service 415-b, connection service 420-b, mobile service 425-b, and data service 430-b). In particular, DU 165-b can be configured to relay communications between UE 115-c and various core network services of the service-based network 205-a to enable UE 115a to establish and maintain wireless connection services with the various core network services in order to exchange communications associated with various network functions supported by the corresponding core network services.

[0136] A service group 405 may be a set of independently addressable core network services. In some cases, a service group 405 may provide services as services, which means that the service group may present a unified interface to other core network services of the service group. For example, a first service group 405-a may provide a unified interface to a second service group 405-b or an application service 410-b, a subscription service 415-b, a connection service 420-b, a mobile service 425-b, or a data service 430-b. It may be common to mark or address core network services within a service group 405. The security of a group of services may be common. In some cases, security in service group to service group communications may be common between core network services in a service group. In some cases, a mobile service 425-a in a service group (e.g., a first service group 405-a) may provide mobility as a service for another service group (e.g., a second service group 405-b, for example, if the second service group 405-b does not include a mobile service).

[0137] Each core network service within a given service group 405 can share the same UE context 435. For example, core network services within a first service group 405-a (e.g., application services 410-a, subscription services 415-a, connection services 420-a, mobile services 425-a, and data services 430-a) can share a first UE context 435-a, and core network services within a second service group 405-b (e.g., application services 410-a, subscription services 415-a, connection services 420-a, mobile services 425-a, and data services 430-b) can share a second UE context 435-b. Within a given service group 405, the security context established for the included core network services can be based on the same UE certificate or network subscription. In some cases, a service group may be located behind a proxy. For example, DU 165-b can route communications to a proxy service, which can then route communications to a target service group, rather than DU 165-b routing communications to a network address associated with a core network service.

[0138] The service groups can be isolated from each other (e.g., communication isolation). For example, the first service group 405-a can be isolated from the second service group 405-b. In some cases, the service groups 405 can exchange communications. For example, the mobile service 425-a can provide mobile services for the second service group 405-b (e.g., if the second service group 405-b does not include mobile services). Different service groups can be operated by the same or different network operators. In some cases, the first UE context 435-a and the second UE context 435-b can be associated with the same UE certificate. In some cases, the first UE context 435-a and the second UE context 435-b can be associated with different UE certificates.

[0139] The service-based network 205-a can provide control information 440 to the UE 115-c via the DU 165-b regarding which core network services are included within the service group 405. In other words, the service-based network 205-a can provide information about core network services that the UE 115-c can invoke or establish service contexts using a common set of UE contexts derived from the same network subscription and / or certificates. In some cases, the UE context 435 may include, for example, a security context, which means that core network services within the same service group can derive a security context with the UE 115-c based on a common primary security context. In some cases, the UE context 435 may include, for example, a policy context, which means that the service policy for each core network service can be derived from a common policy set and the same network subscription information.

[0140] The core network services may call or subscribe to other core network services in the same service group 405. For example, a data service 430-a within a first service group may subscribe to a mobile service 425-a to transfer data services between DUs 165 or RAN nodes (e.g., network entity 105) when UE 115-c changes location. The control information 440 may also indicate operator information (e.g., a public land mobile network identifier or a non-public network identifier) ​​for each service group 405. The control information 440 may also indicate whether different service groups 405 are isolated from each other (e.g., whether core network services within a service group 405 communicate with core network services in other service groups 405).

[0141] Based on the control information 440, the UE 115-c may determine to access a set of core network services within the same service group 405 based on a need at the UE 115-c (e.g., data connectivity for a particular application or data flow, location services, or a particular mobility). The UE 115-c may determine which network subscription or certificate to use to access the service group 405 based on the control information 440. The UE 115-c may send an access request 445 to the service-based network 205-a via the DU 165-b, the access request 445 indicating a selected service group 405 among the indicated service groups 405. For example, the access request 445 may indicate a first service group 405-a and a network subscription or certificate associated with the first service group 405-a.

[0142] In response to the access request 445, the service-based network 205-a may provide control information 450 to the UE 115-c via the DU 165-b, the control information 450 indicating a service context for communicating with the set of core network services of the first service group 405-a. Thus, when accessing any core network service in the first service group 405-a, the UE may use a service context (e.g., UE or core network service identity) that points to a common network subscription or certificate of the first service group 405-a. In some cases, the service context may be a primary security context, and the UE 115-c may derive the security context for any specific service in the first service group from the primary security context.

[0143] After establishing communication with the first service group 405-a (e.g., after establishing a service context), the UE 115-c may determine to communicate with the core network services included in the second service group 405-b. The UE 115-c may determine to establish a second UE context 435-b on the same radio access (e.g., via the same RAN), and determine to establish a new primary security context with the second service group 405-b. The UE 115-c may also determine whether to use the same network subscription of the second service group 405-b as the first service group 405-a. The UE 115-c may also determine whether a specific core network service may be reused from the first service group 405-a based on the control information 440 indicating whether the first service group 405-a and the second service group 405-b are isolated. For example, when two service groups are activated for the UE 115-c, the UE 115-c may reuse the mobile service 425-a for the core network services in the second service group 405-b. The UE 115-c may establish a service context with the second service group 405-b independently of the service context established for the first service group (eg, by sending a second access request indicating the second service group 405-b and appropriate credentials).

[0144] Figure 5 An example of a system diagram 500 for supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown. The system diagram shows a first example system 505-a corresponding to a first example service group use case, a second example system 505-b corresponding to a second example service group use case, and a third example system 505-c corresponding to a third example service group use case. Aspects of the system diagram 500 may be implemented or implemented by aspects of the wireless communication system 100, the wireless communication system 200, or the wireless communication system 400.

[0145] In the first example system 505-a, a single network operator can provide core network services 215 through different service groups 405, which can be isolated. For example, the first service group 405-c can include core network services 215-f and core network services 215-g, and the first service group 405-c can be isolated from the second service group 405-d, which can include core network services 215-h and core network services 215-i. Therefore, a single network operator can provide isolated core network services. A single network operator can provide an independent set of core network services (e.g., service groups 405) to a subscriber UE 115-d. UE 115-d can use the same UE certificate to access the first service group 405-c and the second service group 405-d. UE 115-d can access the first service group 405-c and the second service group 405-d via DU 165-c.

[0146] In the second example system 505-b, UE 115-e can use different UE certificates to access different groups of core network services provided by the same network operator. For example, the second example system 505-b can show multiple user identity modules (SIMs) in the same access situation. The first group of UE certificates can be associated with the first core network service 215-j and the second core network service 215-k provided by the network operator. The second group of UE certificates can be associated with the third core network service 215-l and the fourth core network service 215-m provided by the network operator. Therefore, the first core network service 215-j and the second core network service 215-k can correspond to the first service group, and the third core network service 215-l and the fourth core network service 215-m can correspond to the second service group. The first service group and the second service group may be isolated or not isolated. UE115e can access the first service group and the second service group via DU 165-d.

[0147] In the third example system 505-c, UE 115-f can use different UE certificates to access different groups of core network services provided by different network operators. The first group of UE certificates can be associated with the first core network service 215-n and the second core network service 215-o provided by the first network operator. The second group of UE certificates can be associated with the third core network service 215-p and the fourth core network service 215-q provided by the second network operator. Therefore, the first core network service 215-n and the second core network service 215-o can correspond to the first service group, and the third core network service 215-p and the fourth core network service 215-q can correspond to the second service group. The first service group and the second service group may be isolated or not isolated. UE 115-f can access the first service group and the second service group via DU 165-e. Therefore, the same DU165-e can provide access to multiple network operators (for example, the third example system 505-c shows a RAN sharing system). For example, the first network operator may be an enterprise network, while the second network operator may be a public network, and the UE 115 - f may access both using the same DU 165 - e.

[0148] Figure 6 An example of a process flow 600 for supporting a service group 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-g, which may be an example of a UE 115 as described herein. The process flow 600 may include a DU 165-f, which may be an example of a DU 165 as described herein. The process flow 600 may include a core network service 215-r, which may be an example of a core network service 215 as described herein. In the following description of the process flow 600, operations between the UE 115-g, the DU 165-f, and the core network service 215-r may be sent in an order different from the example order shown, or the operations performed by the UE 115-g, the DU 165-f, and the core network service 215-r may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 600, and other operations may also be added to the process flow 600.

[0149] At 605, DU 165-f may be sent via a wireless connection between UE 115-g and DU 165-f and UE 115-g may receive first control information indicating a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with DU 165-f. The first control information indicates, for each service group in the set of the multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group. In some cases, instead of receiving the first control information from DU 165-f, UE 115-g may identify the first control information based on a preconfiguration stored in a memory at UE 115-g, indicating a set of multiple service groups provided by a service-based network. For example, the preconfiguration of the set of service groups may be stored in a universal user identity module (USIM) of UE 115-a. For example, for each service group in the set of the multiple service groups, the preconfiguration may indicate a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group.

[0150] At 610 , in response to the first control information, the UE 115 - g may send, and the DU 165 - f may receive, an access request indicating a first service group in a set of multiple service groups and a corresponding network certificate for the first service group.

[0151] At 615 , in response to the access request, the DU 165 - f may send, and the UE 115 - g may receive, second control information indicating a service context for communicating with a corresponding set of core network services of the first service group.

[0152] At 620 , the DU 165 - f may transmit the message received from the UE according to the service context to the core network service 215 - r of the corresponding core network service set for the first service group.

[0153] In some cases, the service context may be a primary context associated with the first service group, and the UE 115-g may determine, based on the primary security context, a respective security context for each core network service included in the first service group. In some cases, transmitting the message in accordance with the service context includes transmitting the message in accordance with the determined respective security context for the core network service. In some cases, the primary security context may be authentication information, key agreement, or both.

[0154] In some cases, the DU 165 - f may transmit a second message received from the UE 115 - g according to the service context to a second core network service in the corresponding set of core network services.

[0155] In some cases, the core network service is configured to invoke a second core network service included in the first service group based on a message transmitted to the core network service. In some cases, the core network service may be a data service and the second core network service may be a mobile service.

[0156] In some cases, DU 165-f may receive a second access request from UE 115-g and in response to the first control information, the second access request indicating a second service group in the set of multiple service groups and a corresponding network certificate for the second service group. DU 165-f may send third control information to UE 115-g and in response to the second access request, the third control information indicating a second service context for communicating with a corresponding set of core network services of the second service group. DU 165-f may transmit a second message received from UE 115-g according to the second service context to a second core network service in the corresponding set of core network services included in the second service group. In some cases, the second core network service is configured to invoke a third core network service included in the first service group based on the second message transmitted to the second core network service. In some cases, the second core network service may be a data service, and the third core network service may be a mobile service. In some cases, sending the first control information may include sending an indication that the first service group does not communicate with the second service group.

[0157] In some cases, sending the first control information may include sending an indication of whether each service group in the set of multiple service groups is able to communicate with one or more other service groups in the set of multiple service groups.

[0158] In some cases, sending the first control information may include sending an indication of a respective network subscription associated with each service group in a set of a plurality of service groups, wherein receiving the access request is based on the respective network subscription associated with the first service group.

[0159] In some cases, the service context includes a radio access network configuration for communicating with the UE 115-g as part of using core network services.

[0160] In some cases, each core network service in a respective set of core network services is associated with a respective API in a set of multiple APIs.

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

[0162] In some cases, the access request, message, or both are sent to the DU 165-f for relaying to a network address associated with the core network service 215-r.

[0163] Figure 7 A block diagram 700 of a device supporting a service group 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 a base station 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0166] 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 using a service group 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 of the functions described herein.

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

[0168] 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 using code executed by a processor (e.g., implemented as communication management software or firmware). If implemented using code executed by a processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting units for performing the functions described in the present disclosure).

[0169] 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 integrate in combination with the receiver 710, the transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0170] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. The communication manager 720 may be configured to or otherwise support: a unit for identifying first control information, the first control information indicating a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein the first control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group. The communication manager 720 may be configured to or otherwise support: a unit for sending an access request in response to the first control information, the access request indicating a first service group in the set of multiple service groups and a corresponding network certificate for the first service group. The communication manager 720 may be configured to or otherwise support: a unit for receiving second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services of the first service group. The communication manager 720 may be configured to or otherwise support: a unit for transmitting a message with a core network service in a corresponding set of core network services of the first service group according to the service context.

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

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

[0173] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with service groups 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 collection of multiple antennas.

[0174] The transmitter 815 may provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with service groups 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 collection of multiple antennas.

[0175] The device 805 or its various components may be examples of means for performing various aspects of a service group in a service-based wireless system as described herein. For example, the communication manager 820 may include a service group manager 825, a service group access request manager 830, a service context manager 835, a core network service communication manager 840, or any combination thereof. The communication manager 820 may be an example of various aspects of the communication manager 720 as described herein. In some examples, the communication manager 820 or its various components may be configured to perform various operations (e.g., receive, monitor, send) using the receiver 810, the transmitter 815, or both or in other ways in cooperation with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 may receive information from the receiver 810, send information to the transmitter 815, or integrate with the receiver 810, the transmitter 815, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0176] According to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. The service group manager 825 may be configured to or otherwise support: a unit for identifying first control information, the first control information indicating a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein the first control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group. The service group access request manager 830 may be configured to or otherwise support: a unit for sending an access request in response to the first control information, the access request indicating a first service group in the set of multiple service groups and a corresponding network certificate for the first service group. The service context manager 830 may be configured to or otherwise support: a unit for receiving second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services of the first service group. The core network service communication manager 840 may be configured to or otherwise support: a unit for transmitting a message with a core network service in a corresponding set of core network services of the first service group according to the service context.

[0177] Fig. 9 A block diagram 900 of a communication manager 920 supporting a service group 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 means for performing various aspects of a service group in a service-based wireless system as described herein. For example, the communication manager 920 may include a service group manager 925, a service group access request manager 930, a service context manager 935, a core network service communication manager 940, a security context manager 945, a service group communication manager 950, a network subscription manager 955, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0178] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. The service group manager 925 may be configured to or otherwise support: a unit for identifying first control information, the first control information indicating a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein the first control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group. The service group access request manager 930 may be configured to or otherwise support: a unit for sending an access request in response to the first control information, the access request indicating a first service group in the set of multiple service groups and a corresponding network certificate for the first service group. The service context manager 935 may be configured to or otherwise support: a unit for receiving second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services of the first service group. The core network service communication manager 940 may be configured to or otherwise support: a unit for transmitting a message with a core network service in a corresponding set of core network services of the first service group according to the service context.

[0179] In some examples, the service context includes a primary security context associated with the first service group, and the security context manager 945 may be configured as or otherwise support a unit for performing the following operations: based on the primary security context, determining a corresponding security context for each core network service included in the first service group.

[0180] In some examples, to support transmitting messages according to a service context, the security context manager 945 may be configured or otherwise support means for transmitting the message according to a determined corresponding security context for a core network service.

[0181] In some examples, the primary security context includes authentication information, key agreement, or both.

[0182] In some examples, core network service communication manager 940 may be configured or otherwise support means for communicating a second message with a second core network service of the corresponding set of core network services according to the service context.

[0183] In some examples, the core network service is configured to: based on transmitting the message with the core network service, invoke a second core network service included in the first service group.

[0184] In some examples, the core network service includes a data service.In some examples, the second core network service includes a mobile service.

[0185] In some examples, the service group access request manager 930 may be configured as or otherwise support a unit for performing the following operations: in response to the first control information, sending a second access request, the second access request indicating a second service group in a set of multiple service groups and a corresponding network certificate for the second service group. In some examples, the service context manager 935 may be configured as or otherwise support a unit for performing the following operations: in response to the second access request, receiving third control information, the third control information indicating a second service context for communicating with a corresponding set of core network services of the second service group. In some examples, the core network service communication manager 940 may be configured as or otherwise support a unit for performing the following operations: based on the second service context, transmitting a second message to a second core network service of the corresponding set of core network services included in the second service group.

[0186] In some examples, the second core network service is configured to invoke a third core network service included in the first service group based on transmitting the second message with the second core network service.

[0187] In some examples, the second core network service includes a data service. In some examples, the third core network service includes a mobile service.

[0188] In some examples, to support identifying the first control information, the service group communication manager 950 may be configured as or otherwise support a unit for performing the following operations: identifying an indication that the first service group does not communicate with the second service group, wherein sending the second access request is based on identifying that the first service group does not communicate with the second service group.

[0189] In some examples, to support identifying the first control information, the service group communication manager 950 may be configured as or otherwise support a unit for performing the following operations: identifying whether each service group in the set of the multiple service groups is capable of communicating with one or more other service groups in the set of the multiple service groups.

[0190] In some examples, to support identifying the first control information, the network subscription manager 955 can be configured as or otherwise support a unit for performing the following operations: identifying an indication of a corresponding network subscription associated with each service group in a set of multiple service groups, wherein sending an access request is based on the corresponding network subscription associated with the first service group.

[0191] In some examples, the service context includes a radio access network configuration for communicating with the DU as part of using the core network service.

[0192] In some examples, the access request, the message, or both are sent to the DU for relaying to a network address associated with the core network service.

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

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

[0195] In some examples, to support identifying the first control information, the service group manager 925 may be configured or otherwise support means for performing the following operations: receiving the first control information via a wireless connection between the UE and the DU.

[0196] In some examples, to support identifying the first control information, the service group manager 925 may be configured as or otherwise support means for accessing the first control information from local storage at the UE.

[0197] Fig.10A diagram of a system 1000 including a device 1005 supporting a service group in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein or include components thereof. 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 electronically communicated or otherwise coupled (e.g., operably, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

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

[0199] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which may be able to send or receive multiple wireless transmissions simultaneously. The transceiver 1015 can communicate bidirectionally via one or more antennas 1025, wired or wireless links 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 for modulating packets, providing the modulated packets to one or more antennas 1025 for transmission, and demodulating packets received from one or more antennas 1025. The transceiver 715, or the transceiver 815 and the one or more antennas 1025 can be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or components thereof as described herein.

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

[0201] 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 separate gate or transistor logic component, a separate hardware component, or any combination thereof). In some examples, 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 processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to enable device 1005 to perform various functions (e.g., functions or tasks supporting a dynamic group common physical control channel). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform various functions described herein.

[0202] According to the examples disclosed herein, the communication manager 1020 can support wireless communication at the UE. For example, the communication manager 1020 can be configured to or otherwise support a unit for performing the following operations: identifying first control information, the first control information indicating a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with a DU, wherein the first control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group. The communication manager 1020 can be configured to or otherwise support a unit for performing the following operations: sending an access request in response to the first control information, the access request indicating a first service group in the set of multiple service groups and a corresponding network certificate for the first service group. The communication manager 1020 can be configured to or otherwise support a unit for performing the following operations: receiving second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services of the first service group. The communication manager 1020 may be configured or otherwise support means for communicating a message with a core network service in a corresponding set of core network services of the first service group according to the service context.

[0203] 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 related to reduced processing, reducing power consumption, more efficiently utilizing communication resources, improving coordination between devices, extending battery life, and improving utilization of processing power.

[0204] 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 the service group in the service-based wireless system as described herein, or the processor 1040 and the memory 1030 can be otherwise configured to perform or support such operations.

[0205] Fig.11A block diagram 1100 of a device 1105 supporting a service group 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).

[0206] The receiver 1110 may provide a unit for acquiring (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). 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) interfaces, wireless interfaces, or any combination thereof.

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

[0208] 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 a service group in a service-based wireless system. 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 of the functions described herein.

[0209] 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., with communication management circuitry). 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 of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0210] 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 using code executed by a processor (e.g., implemented as communication management software or firmware). If implemented using 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 units for performing the functions described in the present disclosure).

[0211] In some examples, communication manager 1120 can be configured to perform various operations (e.g., receive, acquire, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 can receive information from receiver 1110, send information to transmitter 1115, or integrate in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0212] According to an example as disclosed herein, the communication manager 1120 can support wireless communication at the DU. For example, the communication manager 1120 can be configured to or otherwise support a unit for performing the following operations: receiving an access request from a UE, the access request indicating a first service group in a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with a distributed unit, wherein each of the multiple service groups includes a corresponding core network service set, wherein each of the multiple service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request also indicates the corresponding network certificate for the first service group. The communication manager 1120 can be configured to or otherwise support a unit for performing the following operations: sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding core network service set of the first service group. The communication manager 1120 can be configured to or otherwise support a unit for performing the following operations: transmitting a message received from the UE according to the service context to a core network service in the corresponding core network service set of the first service group.

[0213] By including or configuring the communication manager 1120 according to examples as 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.

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

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

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

[0217] Device 1205 or its various components may be examples of units for performing various aspects of a service group in a service-based wireless system as described herein. For example, communication manager 1220 may include service group access request manager 1230, service context manager 1235, core network service communication manager 1240, 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 perform various operations (e.g., receive, monitor, send) using receiver 1210, transmitter 1215, or both or in other ways in collaboration with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 may receive information from receiver 1210, send information to transmitter 1215, or integrate with receiver 1210, transmitter 1215, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0218] According to examples as disclosed herein, the communication manager 1220 may support wireless communication at the DU. The service group access request manager 1230 may be configured to or otherwise support a unit for performing the following operations: receiving an access request from a UE, the access request indicating a first service group in a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with a distributed unit, wherein each of the multiple service groups includes a corresponding core network service set, wherein each of the multiple service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request also indicates the corresponding network certificate for the first service group. The service context manager 1235 may be configured to or otherwise support a unit for performing the following operations: sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding core network service set of the first service group. The core network service communication manager 1240 may be configured to or otherwise support a unit for performing the following operations: transmitting a message received from the UE according to the service context to a core network service in the corresponding core network service set of the first service group.

[0219] Fig.13 A block diagram 1300 of a communication manager 1320 supporting a service group in a service-based wireless system according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of 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 the service group in a service-based wireless system as described herein. For example, the communication manager 1320 may include a service group manager 1325, a service group access request manager 1330, a service context manager 1335, a core network service communication manager 1340, a service group communication manager 1345, a network subscription manager 1350, a security context manager 1355, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0220] According to examples disclosed herein, the communication manager 1320 may support wireless communication at the DU. The service group access request manager 1330 may be configured to or otherwise support a unit for performing the following operations: receiving an access request from a UE, the access request indicating a first service group in a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with a distributed unit, wherein each of the multiple service groups includes a corresponding core network service set, wherein each of the multiple service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request also indicates the corresponding network certificate for the first service group. The service context manager 1335 may be configured to or otherwise support a unit for performing the following operations: sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding core network service set of the first service group. The core network service communication manager 1340 may be configured to or otherwise support a unit for performing the following operations: transmitting a message received from the UE according to the service context to a core network service in the corresponding core network service set of the first service group.

[0221] In some examples, the service context includes a primary security context associated with the first service group. In some examples, a respective security context for each core network service included in the first service group is based on the primary security context.

[0222] In some examples, the primary security context includes authentication information, key agreement, or both.

[0223] In some examples, to support messaging in accordance with a service context, security context manager 1355 may be configured or otherwise support means for transmitting messages in accordance with a corresponding security context for a core network service.

[0224] In some examples, the core network service communication manager 1340 may be configured or otherwise support means for transmitting a second message received from the UE according to the service context to a second core network service in the corresponding set of core network services.

[0225] In some examples, the core network service is configured to invoke a second core network service included in the first service group based on a message transmitted to the core network service.

[0226] In some examples, the core network service includes a data service.In some examples, the second core network service includes a mobile service.

[0227] In some examples, the service group access request manager 1330 may be configured as or otherwise support a unit for performing the following operations: receiving a second access request from a UE, the second access request indicating a second service group in a set of multiple service groups and a corresponding network certificate for the second service group. In some examples, the service context manager 1335 may be configured as or otherwise support a unit for performing the following operations: sending second control information to the UE and in response to the second access request, the second control information indicating a second service context for communicating with a corresponding set of core network services of the second service group. In some examples, the core network service communication manager 1340 may be configured as or otherwise support a unit for performing the following operations: transmitting a second message received from the UE according to the second service context to a second core network service in a corresponding set of core network services included in the second service group.

[0228] In some examples, the second core network service is configured to invoke a third core network service included in the first service group based on a second message transmitted to the second core network service.

[0229] In some examples, the second core network service includes a data service and the third core network service includes a mobile service.

[0230] In some examples, the first service group does not communicate with the second service group.

[0231] In some examples, the service group manager 1325 can be configured as or otherwise support a unit for performing the following operations: sending second control information indicating a set of multiple service groups to the UE, wherein the second control information indicates, for each service group in the set of multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group.

[0232] In some examples, to support sending the second control information, the service group communication manager 1345 can be configured as or otherwise support a unit for performing the following operations: sending an indication of whether each service group in a set of multiple service groups is able to communicate with one or more other service groups in the set of multiple service groups.

[0233] In some examples, to support sending the second control information, the network subscription manager 1350 can be configured as or otherwise support a unit for performing the following operations: sending an indication of a corresponding network subscription associated with each service group in a set of multiple service groups, wherein receiving an access request is based on the corresponding network subscription associated with the first service group.

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

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

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

[0237] Fig.14 A diagram of a system 1400 including a device 1405 supporting a service group in a service-based wireless system according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of or include components of a device 1405, device 1405, or 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, 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., bus 1440).

[0238] 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. In addition, 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 (e.g., concurrently) send or receive wireless transmissions. The transceiver 1410 may also include a modem to modulate a signal to provide a modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter), 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 acquiring operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmitting or outputting 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, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 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) may 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 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, fronthaul communication link 168).

[0239] 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 (such as system memory or other types of memory). In some cases, code 1430 may not be directly executable by processor 1435, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition to this, memory 1425 may also include BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0240] 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 components, discrete hardware components, or any combination thereof). In some examples, 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) to enable device 1405 to perform various functions (e.g., functions or tasks supporting a dynamic group common physical control channel). 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, such as 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. Processor 1435 can be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (e.g., in memory 1425). In some implementations, processor 1435 can be a component of a processing system. A processing system can generally refer to a system or a series of machines or components that receive inputs and process inputs to generate an output set (which can be passed to, for example, other systems or components of device 1405). For example, the processing system of device 1405 can refer to a system including various other components or subcomponents of device 1405, such as a processor 1435, or a transceiver 1410, or a communication manager 1420, or a combination of other components or components of device 1405. The processing system of device 1405 can be docked with other components of device 1405, and can process information (such as input or signals) received from other components, and output information to other components. For example, a chip or modem of device 1405 may include a processing system and interface for outputting information, or obtaining 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 second 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 first interface may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1405 can receive information or signal input and can pass the information to the processing system.One of 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.

[0241] In some examples, bus 1440 may support communications within a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1440 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1405, or communications performed between different components of device 1405, which may be co-located or located in different locations (e.g., where device 1405 may refer to a system in which one or more communication managers 1420, transceivers 1410, memory 1425, code 1430, and processor 1435 may be located in one of different components or divided into different components).

[0242] In some examples, the communication manager 1420 can manage aspects of communicating with the service-based network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1420 can manage the delivery 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 cooperation of the UE 115 with 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.

[0243] According to an example as disclosed herein, the communication manager 1420 may support wireless communication at a DU. The communication manager 1420 may be configured to or otherwise support a unit for performing the following operations: receiving an access request from a UE, the access request indicating a first service group in a set of multiple service groups provided by a service-based network configured to connect to a RAN associated with a distributed unit, wherein each of the multiple service groups includes a corresponding core network service set, wherein each of the multiple service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request also indicates the corresponding network certificate for the first service group. The communication manager 1420 may be configured to or otherwise support a unit for performing the following operations: sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding core network service set of the first service group. The communication manager 1420 may be configured to or otherwise support a unit for performing the following operations: transmitting a message received from the UE according to the service context to a core network service in the corresponding core network service set of the first service group.

[0244] 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, extending battery life, and improving utilization of processing power.

[0245] In some examples, the communication manager 1420 may be configured to perform (where applicable) various operations (e.g., receive, acquire, monitor, output, transmit) using or otherwise in cooperation with the transceiver 1410, one or more antennas 1415, 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 may 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 a service group 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.

[0246] Fig.15A flowchart illustrating a method 1500 for supporting a service group in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described with reference to Figures 1 to 10 The UE 115 described herein performs. In some examples, the UE may execute an instruction set 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.

[0247] At 1505, the method may include identifying first control information indicating a plurality of service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein the first control information indicates, for each service group in the plurality of service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described with reference to Fig. 9 The described service group manager 925 is executed.

[0248] At 1510, the method may include sending an access request in response to the first control information, the access request indicating a first service group in a plurality of service groups and a corresponding network certificate for the first service group. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a service group access request manager 930 as described in reference 9.

[0249] At 1515, the method may include receiving second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services of the first service group. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Fig. 9 The service context manager 935 described above is executed.

[0250] At 1520, the method may include transmitting a message to a core network service in a corresponding set of core network services of the first service group according to the service context. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be described with reference to Fig. 9 The described core network services communication manager 940 is executed.

[0251] Fig.16A flowchart illustrating a method 1600 for supporting a service group in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described with reference to Figures 1 to 10 The UE 115 described herein performs. In some examples, the UE may execute an instruction set 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.

[0252] At 1605, the method may include identifying first control information indicating a plurality of service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein the first control information indicates, for each service group in the plurality of service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described with reference to Fig. 9 The described service group manager 925 is executed.

[0253] At 1610, the method may include sending an access request in response to the first control information, the access request indicating a first service group in a plurality of service groups and a corresponding network certificate for the first service group. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Fig. 9 The described service group access request manager 930 is executed.

[0254] At 1615, the method may include receiving second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services of the first service group. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described with reference to Fig. 9 The service context manager 935 described above is executed.

[0255] At 1620, the method may include transmitting a message to a core network service in a corresponding set of core network services of the first service group according to the service context. The operations of 1620 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1620 may be described by reference to Fig. 9 The described core network services communication manager 940 is executed.

[0256] At 1625, the method may include transmitting a second message to a second core network service of the corresponding set of core network services according to the service context. The operations of 1625 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1625 may be described by reference to Fig. 9 The described core network services communication manager 940 is executed.

[0257] Fig.17 A flow chart illustrating a method 1700 for supporting service groups in a service-based wireless system according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by the DU 165 or components thereof as described herein. For example, the operations of the method 1700 may be implemented by the DU 165 or components thereof as described herein. Figures 1 to 6 and Figures 11 to 14 The DU 165 described herein may perform the described functions. In some examples, the DU 165 may execute instruction sets to control functional units of the DU 165 to perform the described functions. Additionally or alternatively, the DU 165 may use dedicated hardware to perform aspects of the described functions.

[0258] At 1705, the method may include receiving an access request from a UE, the access request indicating a first service group of a plurality of service groups provided by a service-based network configured to connect to a RAN associated with a DU, wherein each of the plurality of service groups includes a corresponding set of core network services, wherein each of the plurality of service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request further indicates the corresponding network certificate for the first service group. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a service group access request manager 1330 as described in reference 13.

[0259] At 1710, the method may include sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and a corresponding set of core network services of the first service group. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described with reference to Fig.13 The service context manager 1335 described is executed.

[0260] At 1715, the method may include transmitting a message received from the UE according to the service context to a core network service in a corresponding set of core network services of the first service group. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be described with reference to Fig.13The core network services communication manager 1340 described above is executed.

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

[0262] At 1805, the method may include receiving an access request from a UE, the access request indicating a first service group of a plurality of service groups provided by a service-based network configured to connect to a RAN associated with a DU, wherein each service group of the plurality of service groups includes a corresponding set of core network services, wherein each service group of the plurality of service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request further indicates the corresponding network certificate for the first service group. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by referring to Fig.13 The described service group access request manager 1330 is executed.

[0263] At 1810, the method may include sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and a corresponding set of core network services of the first service group. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Fig.13 The service context manager 1335 described is executed.

[0264] At 1815, the method may include transmitting a message received from the UE according to the service context to a core network service in a corresponding set of core network services of the first service group. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be described with reference to Fig.13 The core network services communication manager 1340 described above is executed.

[0265] At 1820, the method may include transmitting a second message received from the UE according to the service context to a second core network service in the corresponding set of core network services. The operations of 1825 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1825 may be described with reference to Fig.13 The core network service communication manager 1340 described above is executed. The following provides an overview of various aspects of the present disclosure:

[0266] Aspect 1: A method for wireless communication at a UE, comprising: identifying first control information, the first control information indicating a plurality of service groups provided by a service-based network configured to connect to a RAN associated with a DU, wherein the first control information indicates, for each service group in the plurality of service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group; sending an access request in response to the first control information, the access request indicating a first service group in the plurality of service groups and a corresponding network certificate for the first service group; receiving second control information in response to the access request, the second control information indicating a service context for communicating with a corresponding set of core network services in the first service group; and transmitting a message to a core network service in a corresponding set of core network services in the first service group according to the service context.

[0267] Aspect 2: The method of Aspect 1, wherein the service context includes a primary security context associated with the first service group, and the method further comprises: determining a corresponding security context for each core network service included in the first service group based on the primary security context.

[0268] Aspect 3: The method of Aspect 2, wherein transmitting the message according to the service context comprises transmitting the message according to the corresponding security context determined for the core network service.

[0269] Aspect 4: The method of any one of Aspects 2 to 3, wherein the primary security context includes authentication information, key agreement, or both.

[0270] Aspect 5: The method in any one of Aspects 1 to 4 further includes: transmitting a second message to a second core network service in the corresponding core network service set based on the service context.

[0271] Aspect 6: The method of any one of Aspects 1 to 5, wherein, based at least in part on transmitting the message with a core network service, the core network service is configured to invoke a second core network service included in the first service group.

[0272] Aspect 7: The method of Aspect 6, wherein the core network service comprises a data service, and the second core network service comprises a mobile service.

[0273] Aspect 8: The method in any one of Aspects 1 to 7 further includes: sending a second access request in response to the first control information, the second access request indicating a second service group among multiple service groups and a corresponding network certificate for the second service group; receiving third control information in response to the second access request, the third control information indicating a second service context for communicating with a corresponding core network service set of the second service group; and transmitting a second message to a second core network service in a corresponding core network service set included in the second service group based on the second service context.

[0274] Aspect 9: The method of aspect 8, wherein the second core network service is configured to invoke a third core network service included in the first service group based at least in part on transmitting the second message with the second core network service.

[0275] Aspect 10: The method of aspect 9, wherein the second core network service includes a data service, and the third core network service includes a mobile service

[0276] Aspect 11: The method of any one of Aspects 8 to 10, wherein identifying the first control information comprises: determining that the first service group does not communicate with the second service group, wherein sending the second access request is based on determining that the first service group does not communicate with the second service group.

[0277] Aspect 12: The method of any one of Aspects 1 to 11, wherein identifying the first control information comprises: identifying whether each service group among the multiple service groups is capable of communicating with one or more other service groups among the multiple service groups.

[0278] Aspect 13: The method of any one of Aspects 1 to 12, wherein identifying the first control information comprises: identifying a corresponding network subscription associated with each of the multiple service groups, wherein sending the access request is based on the corresponding network subscription associated with the first service group.

[0279] Aspect 14: The method of any one of Aspects 1 to 13, wherein the service context includes a radio access network configuration for communicating with the DU as part of using the core network service.

[0280] Aspect 15: The method of any one of Aspects 1 to 14, wherein the access request, the message, or both are sent to the DU for relaying to a network address associated with the core network service

[0281] Aspect 16: The method of any one of Aspects 1 to 15, wherein each core network service in the corresponding set of core network services is associated with a corresponding application programming interface in the plurality of application programming interfaces.

[0282] Aspect 17: The method of any one of Aspects 1 to 16, wherein the corresponding core network service set includes mobile services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

[0283] Aspect 18: The method of any one of Aspects 1 to 17, wherein identifying the first control information comprises: receiving the first control information via a wireless connection between the UE and the DU.

[0284] Aspect 19: The method of any one of Aspects 1 to 17, wherein identifying the first control information comprises: accessing the first control information locally stored from the UE.

[0285] Aspect 20: A method for wireless communication at a DU, comprising: receiving an access request from a UE, the access request indicating a first service group among a plurality of service groups provided by a service-based network configured to connect to a RAN associated with the DU, wherein each of the plurality of service groups includes a corresponding core network service set, wherein each of the plurality of service groups is associated with a corresponding network certificate for accessing the service group, and wherein the access request also indicates the corresponding network certificate for the first service group; sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding core network service set of the first service group; and transmitting a message received from the UE according to the service context to a core network service in the corresponding core network service set of the first service group.

[0286] Aspect 21: The method of Aspect 20, wherein the service context includes a primary security context associated with the first service group, and the corresponding security context for each core network service included in the first service group is based on the primary security context.

[0287] Aspect 22: The method of Aspect 21, wherein the primary security context includes authentication information, key agreement, or both.

[0288] Aspect 23: The method of any one of Aspects 21 to 22, wherein transmitting the message according to the service context comprises: transmitting the message according to the corresponding security context for the core network service.

[0289] Aspect 24: The method in any one of Aspects 20 to 23 further includes: transmitting a second message received from the UE according to the service context to a second core network service in the corresponding core network service set.

[0290] Aspect 25: The method of any one of Aspects 20 to 24, wherein the core network service is configured to invoke a second core network service included in the first service group based at least in part on transmitting the message with the core network service.

[0291] Aspect 26: The method of Aspect 25, wherein the core network service comprises a data service, and the second core network service comprises a mobile service.

[0292] Aspect 27: The method in any one of Aspects 20 to 26 further includes: receiving a second access request from the UE, the second access request indicating a second service group among multiple service groups and a corresponding network certificate for the second service group; sending second control information to the UE and in response to the second access request, the second control information indicating a second service context for communicating with a corresponding core network service set of the second service group; and transmitting a second message received from the UE according to the second service context to a second core network service in the corresponding core network service set included in the second service group.

[0293] Aspect 28: The method of Aspect 27, wherein the second core network service is configured to invoke a third core network service included in the first service group based at least in part on transmitting the second message with the second core network service.

[0294] Aspect 29: The method of Aspect 28, wherein the second core network service includes a data service, and the third core network service includes a mobile service.

[0295] Aspect 30: The method of any one of Aspects 27 to 29, wherein the first service group does not communicate with the second service group.

[0296] Aspect 31: The method in any one of Aspects 20 to 30 further includes: sending second control information to the UE, the second control information indicating the multiple service groups, wherein the second control information indicates, for each service group in the multiple service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group.

[0297] Aspect 32: The method of Aspect 31, wherein sending the second control information comprises: sending an indication of whether each service group in the multiple service groups is able to communicate with one or more other service groups in the multiple service groups.

[0298] Aspect 33: The method of any one of Aspects 31 to 32, wherein sending the second control information comprises: sending an indication of a corresponding network subscription associated with each of the multiple service groups, wherein receiving the access request is based on the corresponding network subscription associated with the first service group.

[0299] Aspect 34: The method of any one of Aspects 20 to 33, wherein the service context includes a radio access network configuration for communicating with the UE as part of using the core network service.

[0300] Aspect 35: The method of any one of Aspects 20 to 34, wherein each core network service in the corresponding set of core network services is associated with a corresponding application programming interface in the plurality of application programming interfaces.

[0301] Aspect 36: The method of any one of Aspects 20 to 34, wherein the corresponding core network service set includes mobile services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

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

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

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

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

[0306] Aspect 41: An apparatus for wireless communication at a DU, comprising at least one unit for performing the method according to any one of aspects 20 to 36.

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for wireless communication at a user equipment (UE), comprising: identifying first control information indicating a plurality of service groups provided by a service-based network configured to connect a radio access network (RAN) associated with a distributed unit, wherein the first control information indicates, for each service group in the plurality of service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group; sending an access request in response to the first control information, the access request indicating a first service group of the plurality of service groups and the corresponding network certificate for the first service group; receiving, in response to the access request, second control information indicating a service context for communicating with the corresponding set of core network services of the first service group; and A message is transmitted with a core network service in the corresponding set of core network services of the first service group according to the service context.

2. The method according to claim 1, wherein: The service context includes a primary security context associated with the first service group, the method further comprising: Based on the master security context, a respective security context is determined for each core network service included in the first service group.

3. The method according to claim 1, further comprising: A second message is transmitted with a second core network service in the corresponding set of core network services according to the service context.

4. The method according to claim 1, wherein: The core network service is configured to invoke a second core network service included in the first service group based at least in part on communicating the message with the core network service.

5. The method according to claim 4, wherein: The core network services include data services, and The second core network service includes a mobile service.

6. The method according to claim 1, further comprising: sending, in response to the first control information, a second access request indicating a second service group among a plurality of service groups and a corresponding network certificate for the second service group; receiving, in response to the second access request, third control information indicating a second service context for communicating with the corresponding set of core network services of the second service group; as well as A second message is communicated with a second core network service in the corresponding set of core network services included in the second service group according to the second service context.

7. The method according to claim 6, wherein: The second core network service is configured to invoke a third core network service included in the first service group based at least in part on transmitting the second message with the second core network service.

8. The method according to claim 6, wherein: Identifying the first control information includes: A determination is made that the first service group is not in communication with the second service group, wherein sending the second access request is based on the determination that the first service group is not in communication with the second service group.

9. The method according to claim 1, wherein: The identifying the first control information comprises: A respective network subscription associated with each of the plurality of service groups is identified, wherein sending the access request is based on the respective network subscription associated with the first service group.

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

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

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

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

14. The method according to claim 1, wherein: Identifying the first control information includes: The first control information is received via a wireless connection between the UE and the distributed unit.

15. The method according to claim 1, wherein: Identifying the first control information includes: The first control information is accessed from local storage at the UE.

16. A method for wireless communication at a distributed unit, comprising: receiving an access request from a user equipment (UE), the access request indicating a first service group of a plurality of service groups provided by a service-based network configured to connect to a radio access network (RAN) associated with the distributed unit, wherein each service group of the plurality of service groups includes a respective set of core network services, wherein each service group of the plurality of service groups is associated with a respective network credential for accessing the service group, and wherein the access request further indicates the respective network credential for the first service group; sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding set of core network services of the first service group; and The message received from the UE according to the service context is delivered to a core network service in the corresponding core network service set of the first service group.

17. The method of claim 16, wherein: The service context includes a primary security context associated with the first service group, and A respective security context for each core network service included in the first service group is based on the primary security context.

18. The method according to claim 16, further comprising: The second message received from the UE according to the service context is transmitted to a second core network service in the corresponding core network service set.

19. The method according to claim 16, wherein: The core network service is configured to invoke a second core network service included in the first service group based at least in part on the message being transmitted to the core network service.

20. The method of claim 19, wherein: The core network services include data services, and The second core network service includes a mobile service.

21. The method of claim 16, further comprising: receiving a second access request from the UE, the second access request indicating a second service group of the plurality of service groups and the corresponding network certificate for the second service group; sending, to the UE and in response to the second access request, second control information indicating a second service context for communicating with the corresponding set of core network services of the second service group; as well as A second message received from the UE according to the second service context is delivered to a second core network service of the corresponding core network service set included in the second service group.

22. The method according to claim 21, wherein: The second core network service is configured to invoke a third core network service included in the first service group based at least in part on transmitting the second message to the second core network service.

23. The method of claim 16, further comprising: Sending second control information to the UE, the second control information indicating the multiple service groups, wherein the second control information indicates, for each service group in the multiple service groups, the corresponding core network service set included in the service group and the corresponding network certificate for accessing the service group.

24. The method according to claim 23, wherein: Sending the second control information includes: An indication of whether each service group in the plurality of service groups is able to communicate with one or more other service groups in the plurality of service groups is sent.

25. The method according to claim 23, wherein: Sending the second control information includes: An indication of a respective network subscription associated with each of the plurality of service groups is sent, wherein receiving the access request is based on the respective network subscription associated with the first service group.

26. The method of claim 16, wherein: The service context includes a radio access network configuration for communicating with the UE as part of utilizing the core network service.

27. The method of claim 16, wherein: Each core network service in the respective set of core network services is associated with a respective application programming interface in the plurality of application programming interfaces.

28. The method of claim 16, wherein: The corresponding set of core network services includes mobility services, connection state management services, security services, paging services, radio access services, data services, capability management services, location services, messaging services, or any combination thereof.

29. An apparatus for wireless communication of a user equipment (UE), comprising: Memory; as well as a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: identifying first control information indicating a plurality of service groups provided by a service-based network configured to connect a radio access network (RAN) associated with a distributed unit, wherein the first control information indicates, for each service group in the plurality of service groups, a corresponding set of core network services included in the service group and a corresponding network certificate for accessing the service group; sending an access request in response to the first control information, the access request indicating a first service group of the plurality of service groups and a corresponding network certificate for the first service group; receiving, in response to the access request, second control information indicating a service context for communicating with the corresponding set of core network services of the first service group; and A message is transmitted with a core network service in the corresponding set of core network services of the first service group according to the service context.

30. An apparatus for wireless communication at a distributed unit, comprising: Memory; as well as a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: receiving an access request from a user equipment (UE), the access request indicating a first service group of a plurality of service groups provided by a service-based network configured to connect to a radio access network (RAN) associated with a distributed unit, wherein each service group of the plurality of service groups includes a respective set of core network services, wherein each service group of the plurality of service groups is associated with a respective network credential for accessing the service group, and wherein the access request further indicates the respective network credential for the first service group; sending control information to the UE and in response to the access request, the control information indicating a service context for communication between the UE and the corresponding set of core network services of the first service group; and The message received from the UE according to the service context is delivered to a core network service in the corresponding core network service set of the first service group.

Images