Establishing connection to service-based core network via radio access network

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may be configured to receive control information from a distributed unit (DU) associated with a first radio access technology (RAT) of a radio access network (RAN), the control information indicating a core network service provided by a service-based network associated with a second RAT. The UE may send a service request via the first RAT, the service request indicating the core network service provided by the service-based network associated with the second RAT. The UE may receive control signaling from the DU indicating a service configuration for communicating with the core network service provided by the service-based network. The UE may then send a service message to the DU via the first RAT and according to the service configuration, the service message including a payload associated with the core network service, the payload being in a format associated with the second RAT.

Description

[0001] Cross-reference

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 061,952, filed on Dec. 5, 2022, by Griot et al., entitled "TECHNIQUES FOR ESTABLISHING CONNECTIVITY TO A SERVICE-BASED NETWORK VIA A RADIO ACCESS NETWORK", which is assigned to the assignee of the present application and is hereby incorporated by reference in its entirety. Technical Field

[0003] The following relates to wireless communication, including techniques for establishing connectivity to a service-based network via a radio access network (RAN). Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and so on. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems (such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multi-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE).

[0005] In the context of a service-based wireless system, a radio access network (RAN) may interact with a service-based network that provides or supplies various core network services. However, some network entities (e.g., a distributed unit (DU)) may not be able to perform wireless communication using a radio access technology (RAT) associated with the core network services of the service-based network. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for techniques that support establishing a connection to a service-based network via a radio access network (RAN). Generally, aspects of the present disclosure relate to enabling a distributed unit (DU) associated with a first radio access technology (RAT), such as a fifth-generation (5G) RAT, to utilize the signaling of the first RAT to facilitate the signaling and mechanisms for services provided via a second RAT, such as a sixth-generation (6G) RAT. In other words, aspects of the present disclosure relate to techniques that enable 6G communications to be performed over a 5G network to facilitate the migration to 6G services. For example, a 5G DU may include a 5G / 6G adapter component (which may include hardware and / or software) that interacts with 6G services, and converts 6G signaling to 5G signaling, and vice versa. For example, the 5G / 6G adapter may receive 6G communications from a 6G service and configure the DU (via the F1 interface) with 5G service configurations to relay 6G information to a user equipment (UE) via 5G signaling. Conversely, the 5G DU may receive 5G signaling from the UE that is intended for a 6G service and may convey the 5G signaling to the 5G / 6G adapter via the F1 service such that the 5G / 6G adapter may format the signaling into a 6G format to relay to the applicable 6G service.

[0007] A method is described. The method may include: receiving control information from a DU associated with a first RAT of a RAN, the control information indicating a core network service provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN; sending, via the first RAT and based on the control information, a service request indicating the core network service provided by the service-based network associated with the second RAT; receiving control signaling from the DU, the control signaling indicating a service configuration for communicating with the core network service provided by the service-based network based on the service request, the service configuration indicating a destination associated with the core network service; and sending, via the first RAT and according to the service configuration, a service message to the DU, the service message including a destination and a payload associated with the core network service, the payload being in a format associated with the second RAT.

[0008] Describes an apparatus. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive control information from a DU associated with a first RAT of a RAN, the control information indicating a core network service provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN; send a service request via the first RAT and based on the control information, the service request indicating a core network service provided by a service-based network associated with a second RAT; receive control signaling from the DU, the control signaling indicating a service configuration for communicating with the core network service provided by the service-based network based on the service request, the service configuration indicating a destination associated with the core network service; and send a service message via the first RAT and according to the service configuration to the DU, the service message including a destination associated with the core network service and a payload, the payload being in a format associated with the second RAT.

[0009] Describes another apparatus. The apparatus may include: means for receiving control information from a DU associated with a first RAT of a RAN, the control information indicating a core network service provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN; means for sending a service request via the first RAT and based on the control information, the service request indicating a core network service provided by a service-based network associated with a second RAT; means for receiving control signaling from the DU, the control signaling indicating a service configuration for communicating with the core network service provided by the service-based network based on the service request, the service configuration indicating a destination associated with the core network service; and means for sending a service message via the first RAT and according to the service configuration to the DU, the service message including a destination associated with the core network service and a payload, the payload being in a format associated with the second RAT.

[0010] A non-transitory computer-readable medium storing code is described. The code can include instructions executable by a processor to perform the following operations: receive control information from a DU associated with a first RAT of a RAN, the control information indicating a core network service provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN; send a service request via the first RAT and based on the control information, the service request indicating a core network service provided by a service-based network associated with a second RAT; receive control signaling from the DU, the control signaling indicating a service configuration for communicating with the core network service provided by the service-based network based on the service request, the service configuration indicating a destination associated with the core network service; and send a service message via the first RAT and according to the service configuration to the DU, the service message including a destination associated with the core network service and a payload, the payload being in a format associated with the second RAT.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein can also include operations, features, components, or instructions for: receiving a system information block (SIB) message including control information from a DU, where the SIB message can be received via the first RAT.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein can also include operations, features, components, or instructions for: sending capability signaling to a DU via the first RAT, the capability signaling indicating the ability of a user equipment (UE) to communicate with a core network service provided by a service-based network associated with a second RAT, where receiving the control information can be based on the capability signaling.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein can also include operations, features, components, or instructions for: establishing a wireless connection with a second DU associated with the second RAT based on operating in a dual-connectivity state, where the second DU can be communicatively coupled to at least a second core network service provided by the service-based network; and sending a second service message to the second DU via the second RAT, the second service message including a second destination associated with the second core network service, the service message further including additional service data associated with the second core network service, the additional service data including an additional payload in a format associated with the second RAT.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving second control signaling from a second DU, the second control signaling indicating a service context for communicating with a second core network service via a second RAT, wherein a second service message may be sent according to the service context.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a service request and a service message may be sent via one or more communication layers associated with a first RAT, the one or more communication layers including a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC) layer, or any combination thereof.

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

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first RAT includes 5G RAT, a new radio (NR) access technology, or both, and the second RAT includes 6G RAT.

[0018] A method is described. The method may include: receiving a service message from a core network service provided by a service-based network associated with a second RAT, wherein the service-based network is configured to interact with a RAN associated with a first RAT, the service message indicating a service context for communication between a UE and the core network service associated with the second RAT; determining a service configuration for communicating with the UE via the first RAT based on the service context associated with the second RAT; and sending a service message to the UE via the first RAT and according to the service configuration, the service message including a payload in a format associated with the second RAT.

[0019] An apparatus is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus: to receive a service message from a core network service provided by a service-based network associated with a second RAT, wherein the service-based network is configured to interact with a RAN associated with a first RAT, the service message indicating a service context for communication between a UE and the core network service associated with the second RAT; to determine a service configuration for communicating with the UE via the first RAT based on the service context associated with the second RAT; and to send a service message to the UE via the first RAT and according to the service configuration, the service message including a payload in a format associated with the second RAT.

[0020] Another apparatus is described. The apparatus may include: means for receiving a service message from a core network service provided by a service-based network associated with a second RAT, wherein the service-based network is configured to interact with a RAN associated with a first RAT, the service message indicating a service context for communication between a UE and the core network service associated with the second RAT; means for determining a service configuration for communicating with the UE via the first RAT based on the service context associated with the second RAT; and means for sending a service message to the UE via the first RAT and according to the service configuration, the service message including a payload in a format associated with the second RAT.

[0021] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to: receive a service message from a core network service provided by a service-based network associated with a second RAT, wherein the service-based network is configured to interact with a RAN associated with a first RAT, the service message indicating a service context for communication between a UE and the core network service associated with the second RAT; determine a service configuration for communicating with the UE via the first RAT based on the service context associated with the second RAT; and send a service message to the UE via the first RAT and according to the service configuration, the service message including a payload in a format associated with the second RAT.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for: receiving, via a service message, a service configuration request from a core network service for converting a service context associated with a second RAT into a service configuration associated with a first RAT, wherein determining the service configuration and sending the service message may be based on receiving the service configuration request.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for: sending, via the first RAT, a SIB message to the UE, the SIB message indicating a core network service provided by a service-based network; receiving, via the first RAT and based on the SIB message, a service request from the UE indicating the core network service; and sending, via the second RAT, the service request to a destination associated with the core network service, wherein receiving the service message may be based on sending the service request.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving, from a UE via a first RAT, capability signaling that indicates the UE's ability to communicate with a core network service provided by a service-based network associated with a second RAT, wherein transmitting the SIB message may be based on the capability signaling.

[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a service message may be received via an adapter component of a DU, the adapter component being configured to interact with a service-based network and translate communications between a first RAT and a second RAT, and the adapter component including a hardware component, a software component, or both.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending control signaling to a core network service, the control signaling indicating application programming interface information associated with a DU, wherein the service message may be received via the second RAT based on the application programming interface information.

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a service message may be transmitted via one or more communication layers associated with a first RAT, the one or more communication layers including a PHY layer, a MAC layer, an RLD layer, or any combination thereof.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first RAT includes a 5G RAT, an NR access technology, or both, and the second RAT includes a 6G RAT. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 Examples of wireless communication systems that illustrate techniques supporting establishing a connection to a service-based network via a radio access network (RAN) in accordance with one or more aspects of the present disclosure are shown.

[0030] Figure 2 Examples of wireless communication systems that illustrate techniques supporting establishing a connection to a service-based network via a radio access network (RAN) in accordance with one or more aspects of the present disclosure are shown.

[0031] Figure 3 Examples of network architectures that illustrate techniques supporting establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure are shown.

[0032] Figure 4An example of a wireless communication system is illustrated that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure.

[0033] Figure 5 An example of a process flow is illustrated that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure.

[0034] Figure 6 and Figure 7 A block diagram of an apparatus is illustrated that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure.

[0035] Figure 8 A block diagram of a communication manager is illustrated that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure.

[0036] Figure 9 A diagram of a system is illustrated that includes an apparatus that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure.

[0037] Figure 10 and Figure 11 A block diagram of an apparatus is illustrated that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure.

[0038] Figure 12 A block diagram of a communication manager is illustrated that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure.

[0039] Figure 13 A diagram of a system is illustrated that includes an apparatus that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure.

[0040] Figures 14 to 16 A flowchart is illustrated that depicts a method that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure. Detailed Description

[0041] Some wireless systems may exhibit a relatively vertical hierarchical 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 multiple backend (e.g., core network) devices associated with one or more functions of the system. Such a hierarchical structure can result in processing and other functions being performed at multiple devices (e.g., duplicate processing or capabilities across multiple backend devices), leading to wasted resources and excessive power consumption. Additionally, the backend architecture of some wireless systems may be owned and maintained by a small number of operators, which can make it difficult for other parties / entities to integrate with the system and can complicate the system's ability to provide customized services and functionality to wireless devices.

[0042] In contrast, some wireless systems (e.g., sixth-generation (6G) systems) may exhibit a flatter, service-based architecture in which a radio access network (RAN) (e.g., network entities) interacts with a service-based network to connect a UE to core network services maintained at various network addresses within the service-based network. In the context of a service-based system, operations and functions that might otherwise be performed by several centralized backend components (e.g., in some systems) can 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 may be able to establish and maintain connections (e.g., "subscribe") with different core network services or groups thereof on a per-point-of-choice basis, where each core network service provides or supplies a corresponding network functionality 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 personalized characteristics or needs of the respective UE.

[0043] Communication with core network services provided by a service-based network (e.g., 6G or cloud-based network) may require different protocols and communications that may not be supported by some network entities associated with other RATs, such as 5G RAN nodes including 5G DUs, 5G CUs, etc. Additionally, the development of RAN nodes (e.g., DUs, CUs) that support core network services of a service-based network may require significant time and investment, which can significantly slow down the migration from a current RAT to a service-based RAT (e.g., from 5G to 6G).

[0044] Accordingly, aspects of the present disclosure relate to enabling a DU associated with a first RAT (such as a 5G RAT) to utilize the signaling of the first RAT to facilitate the signaling and mechanisms for services provided via a second RAT (such as a 6G RAT). In other words, aspects of the present disclosure relate to techniques that enable 6G communication to be performed over a 5G network to facilitate the migration to 6G services. For example, a 5G DU may include a 5G / 6G adapter component (which may include hardware and / or software) that interacts with 6G services, and converts 6G signaling to 5G signaling, and vice versa. For example, the 5G / 6G adapter may receive 6G communication from a 6G service, and configure the DU using a 5G service configuration (via the F1 interface) to relay 6G information to the UE via 5G signaling. Conversely, the 5G DU may receive 5G signaling from the UE that is intended for a 6G service, and may convey the 5G signaling to the 5G / 6G adapter via the F1 service, such that the 5G / 6G adapter may format the signaling into a 6G format for relaying to the applicable 6G service.

[0045] Aspects of the present disclosure are first described in the context of a wireless communication system. Additional aspects of the present disclosure are described in the context of an example network architecture and an example process flow. Aspects of the present disclosure are further illustrated by means of apparatus diagrams, system diagrams, and flowcharts related to techniques for establishing a connection to a service-based network via a RAN, and aspects of the present disclosure are described with reference to these diagrams.

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

[0047] Network entity 105 can be dispersed throughout a geographical area to form a wireless communication system 100, and can include devices in different forms or with different capabilities. In various examples, network entity 105 can be referred to as a network element, a mobility element, a radio access network (RAN) node, an access point, or network equipment, among other designations. In some examples, network entity 105 and UE 115 can communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 can support a coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 can establish one or more communication links 125. Coverage area 110 can be an example of a geographical area within which network entity 105 and UE 115 can support signal communication according to one or more radio access technologies (RATs).

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

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

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

[0051] 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 a service-based network 130 using one or more 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, a network service API 180 at the service-based network 130 may interact with a corresponding DU service API 175 at the DU 165, which in turn interacts 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.

[0052] 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 NodeB, an eNodeB (eNB), a next-generation NodeB, or a giga NodeB (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home NodeB, a home eNodeB, a 6G NB, or other suitable terms). In some examples, the network entity 105 (e.g., the base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a service-based architecture and provide radio access within a single network entity 105 (e.g., a single RAN node, such as the base station 140, may include an RU 170, a DU 165, and a DU API 175 for the CN / RAN services 185). The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP).

[0053] Additionally, in some examples, one or more network entities 105 may be implemented in a split architecture (e.g., split base station architecture, split RAN architecture), which 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, network entity 105 may include one or more of the following: a central unit (CU), a DU 165, an RU 170, a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non RT RIC)), a service management and orchestration (SMO) system, or any combination thereof. One or more components of network entity 105 in a split RAN architecture may be collocated, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of a split RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0054] The functional division between components (e.g., CU, DU, and RU) is flexible and can support different functions, depending on which functions are performed at the components (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 the DU 165 such that the CU can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU can host higher 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 APIs 180 of the service-based network 130. The CU can be connected to one or more DUs 165 or RUs 170, and one or more DUs 165 or RUs 170 can host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and can each be at least partially controlled by the CU. Additionally or alternatively, a functional split of the protocol stack can be adopted between the DU 165 and the RU 170 such that the DU 165 can support one or more layers of the protocol stack and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU and the DU 165 or between the DU 165 and the RU 170 can be within a protocol layer (e.g., some functions of the protocol layer can 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 can 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 can be implemented according to the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0055] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement a wired backhaul connection and thereby provide 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 node 104) may be partially controlled by one another. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via the supported access and backhaul links (e.g., backhaul communication link 120). An IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with a UE 115 or may share the same antennas (e.g., of an RU 170 of the IAB node 104) used for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, an IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB nodes 104, UEs 115) within a relay chain or configuration (e.g., downstream) with an access network. In such cases, one or more components of a split RAN architecture (e.g., one or more IAB nodes 104 or components of an IAB node 104) may be configured to operate according to the techniques described herein.

[0056] In the context where the techniques described herein are applied to a split RAN architecture, one or more components of the split RAN architecture may be configured to support techniques for capability indication of multiple services 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., base station 140) may additionally or alternatively be performed by one or more components of a split RAN architecture (e.g., IAB nodes 104, DUs 165, CUs, RUs 170, RICs, SMOs).

[0057] The 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 suitable term, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. The 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, the UE 115 may include or may 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, etc., which may be implemented in various objects such as appliances, vehicles, meters, etc.

[0058] The UE 115 described herein may be capable of communicating with various types of devices, such as other UE 115s that may sometimes act as relays, and network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc., as Figure 1 shown.

[0059] The UE 115 and the network entity 105 may 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" may refer to a set of RF spectral resources having a defined physical (PHY) layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion (e.g., a bandwidth part (BWP)) of an RF spectral band that operates according to one or more PHY layer channels for a given radio access technology (e.g., 4G, 5G, 6G radio access technology). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating the operation of 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 a carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "transmit", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the communication of the network entity 105 of the RAN (e.g., base station 140, CU, DU 165, RU 170) with another device (e.g., directly or via one or more other network entities 105).

[0060] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of 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 according to a channel raster used for discovery by UE 115. A carrier may operate in a stand-alone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-stand-alone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0061] The communication link 125 shown in the wireless communication system 100 may include other transmission configurations such as a downlink transmission (e.g., a forward link transmission) from the network entity 105 to the UE 115, an uplink transmission (e.g., a reverse link transmission) from the UE 115 to the network entity 105, or both. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink communication and uplink communication (e.g., in TDD mode).

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

[0063] The signal waveform transmitted via a carrier may include 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 employing MCM techniques, a resource element may refer to the resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing may be inversely 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 decoding rate of the modulation scheme, or both), such that a relatively large number of resource elements (e.g., during 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 or beams), and the use of multiple spatial resources may increase the data rate or data integrity for communication with UE 115.

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

[0065] The time intervals for network entity 105 or UE 115 can be expressed as multiples of a basic time unit, and the basic time unit may refer to, for example, the sampling period T s = 1 / (Δf max ·N f ) seconds, where Δf max may represent the supported subcarrier spacing, and N f may represent the supported discrete Fourier transform (DFT) size. The time intervals of communication resources may be organized according to radio frames, and each radio frame has 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).

[0066] 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 also be divided into a certain 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 certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-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 f

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

[0068] According to various techniques, carriers may be used to multiplex physical channels for communication. For example, one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques may be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region of a physical control channel (e.g., a control resource set (CORESET)) may be defined by a set of symbol periods and may extend across the system bandwidth of a carrier or a subset of the system bandwidth. 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 in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. A search space set may include a common search space set configured to transmit control information to a plurality of UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115.

[0069] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier), and may be associated with an identifier for distinguishing adjacent cells (e.g., physical cell identifier (PCID), virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of the coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the scope of such cells can 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 may include a building, a subset of a building, or an external space between or overlapping with the coverage area 110, etc.

[0070] Macro cells generally cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unrestricted access to UEs 115 having a service subscription with the network provider supporting the macro cell. Compared with macro cells, small cells may be associated with a lower power network entity 105 (e.g., a lower power base station 140), and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 having a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

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

[0072] In some examples, network entity 105 (e.g., base station 140, RU 170) can be movable and thus provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

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

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

[0075] In some examples, UE 115 may be configured to communicate directly 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 performing D2D communication in a group may be within the coverage area 110 of a network entity 105 (e.g., base station 140, RU 170), and this network entity may support aspects of such D2D communication configured (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, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE among the other UEs 115 in the group. In some examples, the network entity 105 may facilitate the scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without involving the network entity 105.

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

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

[0078] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band because, in terms of length, the wavelength range is from approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clutter), but these waves may be sufficient to penetrate structures so that a macro cell can serve a UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).

[0079] The wireless communication system 100 may also operate using the super high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or using the extremely high frequency (EHF) region of the spectrum (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between the UE 115 and the network entity 105 (e.g., the base station 140, the RU 170), and the EHF antennas of the corresponding devices may be smaller and closer spaced than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater attenuation and shorter ranges than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the use of frequency bands designated across these frequency regions may vary by country or regulatory body.

[0080] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology that uses unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating using an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using an unlicensed band may be based on a carrier aggregation configuration in combination with a component carrier operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, or device-to-device (D2D) transmissions, etc.

[0081] The network entity 105 (e.g., the base station 140, the RU 170) or the UE 115 may be equipped with multiple antennas that may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or the UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, the 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 antenna ports in multiple rows and columns that the network entity 105 may use to support beamforming for communication 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, an antenna panel may support RF beamforming for signals transmitted via the antenna ports.

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

[0083] 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., the network entity 105, the UE 115) to shape or steer 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 the signals conveyed via the antenna elements of an antenna array such that some signals propagating along a particular direction relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals conveyed via the antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

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

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

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

[0087] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) 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). For example, the receiving device may perform receiving according to multiple receiving directions by: receiving via different antenna sub-arrays, processing the received signals according to different antenna sub-arrays, receiving according to different sets of receiving beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of an antenna array. Any of these operations may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receiving configuration may be aligned along a beam direction determined based on listening according to different receiving configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

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

[0089] In some embodiments, the wireless communication system 100 may support enabling a DU associated with a first RAT (e.g., a 5G DU) to utilize the signaling of the first RAT to facilitate the signaling and mechanisms for services provided via a service-based network 130 associated with a second RAT (e.g., 6G). In other words, aspects of the present disclosure relate to techniques that enable 6G communication to be performed over a 5G network to facilitate the migration to 6G services. For example, the 5G DU 165 of the wireless communication system 100 may include a 5G / 6G adapter component (which may include hardware and / or software) that interacts with the CN / RAN services 185 of the service-based network 130 associated with the second RAT and transforms the signaling of the second RAT into the signaling of the first RAT and vice versa. For example, the 5G / 6G adapter may receive 6G communication from the CN / RAN services 185 of the service-based network 130 and configure the DU 165 using a 5G service configuration (via the F1 interface) to relay 6G information to the UE 115 via 5G signaling. Conversely, the 5G DU 165 may receive 5G signaling from the UE 115 that is intended for the CN / RAN services 185 and may deliver the 5G signaling to the 5G / 6G adapter via the F1 service such that the 5G / 6G adapter may format the signaling into a 6G format for relay to the applicable CN / RAN services 185.

[0090] The techniques described herein may enable a DU 165 associated with a first RAT (e.g., 4G, 5G) to facilitate communication between a UE 115 and a CN / RAN service 185 associated with a second RAT (e.g., 6G) of a service-based network 130. Stated another way, aspects of the present disclosure may enable a 5G DU 165 to use 5G signaling to provide a UE 115 with access to a service-based network 130 of 6G services. Accordingly, aspects described herein may reduce the cost associated with building a service-based network 130 and may increase the speed at which a wireless network can migrate to a service-based network. Additionally, by enabling a DU 165 associated with a first RAT to facilitate communication with a service-based network 130 associated with a second RAT, aspects of the present disclosure may facilitate broader access to a service-based network 130 when building the infrastructure of a service-based network 130.

[0091] Figure 2 An example of a wireless communication system 200 supporting techniques for service establishment in a service-based wireless system in accordance with one or more aspects of the present disclosure is illustrated. Aspects of the wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. In some particular implementations, the wireless communication system 200 illustrates an example architecture of a service-based wireless communication system such as a 6G network as described in reference to Figure 1 the example architecture.

[0092] 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 interact with a RAN 210 of the wireless communication system 200, where the RAN 210 includes the one or more network entities (e.g., network entity 105-a). The service-based network 205 may support or provide a set of core network services 215 (e.g., core network services 215-a, 215-b, 215-c, 215-d, 215-d, 215-e). In some particular implementations, the service-based network 205 may include, or be associated with, a cloud platform where the respective core network services 215 are hosted at respective network addresses in the cloud platform.

[0093] UE 115-a can communicate with network entity 105-a using one or more communication links 220, which can include examples of access links (e.g., Uu links). Communication link 220 can include a bi-directional link, which can include both uplink communication and downlink communication. Similarly, network entity 105-a of RAN 210 can be configured to communicate with (e.g., interact with) service-based network 205 via one or more communication links (e.g., communication link 225), where communication link 215 can be configured to facilitate bi-directional communication between network entity 105-a and each of the corresponding core network services 215 of service-based network 205.

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

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

[0096] The different services, functionalities, and core network functions that may be supported or provided by the corresponding core network service 215 may 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 hosting information and providing signaling that facilitates the geographical movement 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 the subscribed UE 115 within the wireless communication system 200.

[0097] In some aspects, each core network service 215 may include corresponding APIs configured to facilitate wireless communication with the network entity 105-a and the UE 115-a, such as Figure 1 the network service API 180 illustrated in. The APIs 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.

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

[0099] Figure 2The service-based wireless communication system 200 (e.g., 6G network) illustrated in [document] may exhibit several differences and advantages compared to some other types of wireless systems (such as networks that alternatively exhibit a relatively more vertical hierarchical architecture, which includes many “layers” of different devices that perform the functions of the network). A more hierarchical structure may result in processing and other functions being performed at multiple devices (e.g., network entity 105 and one or more backend devices), leading to inefficient use of resources and high power consumption. Additionally, the backend architecture of a network with a more vertical hierarchical architecture may be owned and maintained by a small number of operators, which may make it difficult for other parties / entities to integrate with such systems, and the services provided to UE 115 and other devices may be difficult to customize within such systems.

[0100] In contrast, Figure 2 The service-based wireless communication system 200 illustrated in [document] exhibits a more flattened horizontal architecture, which enables the corresponding functions of the wireless communication system to be distributed across different components of the system (e.g., core network services 215). For example, such functions and protocols can be partitioned and distributed across the set of core network services 215 such that each core network service 215 can support or enable a small portion of the capabilities and functionality of a conventional wireless communication system. In other words, compared to components that provide all included network functions and protocols (e.g., modularization of network services / functions across multiple core network services 215), a service-based architecture can enable functions and protocols to be divided into self-contained services (e.g., core network services 215).

[0101] In this regard, the wireless communication system 200 can illustrate an example of a cloud-native platform configured to host a merger of CORE and RAN services, which can simplify protocols and reduce duplication of processing operations across CORE and RAN (e.g., redistribution of CORE and RAN 210 services). In other words, the convergence of RAN 210 and CN functions can reduce duplicate operations and functions for serving a UE at different layers.

[0102] 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 benefits of increased scalability, resiliency, elasticity, agility, reuse, visibility, automation, and failover. Additionally, the service-based architecture can enable each core network service 215 across the RAN 210 and CORE to scale independently by independently increasing or decreasing the resources allocated across the corresponding core network service 215.

[0103] In some specific implementations, as will be described in further detail herein, the wireless communication system 200 may support signaling and mechanisms that enable a network entity 105-a associated with a first RAT (e.g., 4G, 5G) to facilitate communication between a UE 115-a and a core network service 215 of a service-based network 205 (such as a 6G network) associated with a second RAT.

[0104] Figure 3 An example of a network architecture 300 (e.g., a decomposed base station architecture, a decomposed RAN architecture) that illustrates techniques for supporting service establishment in a service-based wireless system in accordance with one or more aspects of the present disclosure is shown. The network architecture 300 may illustrate examples 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 a 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 a 5G core 190-a via a fronthaul 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 an SMO 335 (e.g., an SMO framework), or both). The CU 310 may communicate with one or more DUs 165-a via a respective midhaul communication link 315 (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via a respective fronthaul communication link 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with a UE 115-b via one or more communication links 125-a. In some specific implementations, the UE 115-b may be served simultaneously by multiple RUs 170-a.

[0105] Each network entity 105 in the network entity 105 of the network architecture 300 (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) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) providing instructions to the interfaces of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, these network entities 105 may include a wired interface configured to receive signals on a wired transmission medium or transmit signals to one or more of the other network entities 105 on the 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 signals on a wireless transmission medium, transmit signals to one or more of the other network entities 105 on the wireless transmission medium, or both.

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

[0107] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, when interacting with the service-based network 305, DU 165-a may host one or more services for the service-based network 305 and one or more corresponding services at one or more UEs 115-b, as well as one or more APIs. In some examples, when interacting 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., high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation, and demodulation, etc.), at least partially depending on the functional split, such as those 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 that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 310.

[0108] In some examples, lower layer functions may be implemented by one or more RUs 170-a. For example, an RU 170-a controlled by 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, at least partially based on a functional split (such as a lower layer functional split). In such an architecture, RU 170-a may be implemented to handle over-the-air (OTA) communication with one or more UEs 115-b. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication 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).

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

[0110] The non-RT RIC 330-b can be configured to include logical 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 steering 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 the A1 interface). The near RT RIC 330-a can be configured to include logical functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via the E2 interface) that connects one or more CUs 310, one or more DUs 165-a, or both, and the O-eNB 325 to the near RT RIC 330-a.

[0111] In some examples, to generate an AI / ML model to be deployed in the near RT RIC 330-b, the non-RT RIC 330-b can receive parameters or external enrichment information from an external server. Such information can be utilized by the near RT RIC 330-a and can be received at the SMO 335 or the non-RT RIC 330-b from non-network data sources or from network functions. In some examples, the non-RT RIC 330-b or the near RT RIC 330-a can be configured to regulate RAN behavior or performance. For example, the non-RT RIC 330-b can monitor long-term trends and patterns in performance and employ an AI model or an ML model to perform corrective actions via the SMO 335 (e.g., reconfiguration via O1) or via the generation of RAN management policies such as A1 policies.

[0112] In some implementations, as will be described in further detail herein, the network architecture 300 can support signaling and mechanisms that enable a network entity 105-a associated with a first RAT (e.g., 4G, 5G) to facilitate communication between a UE 115-a and core network services 215 of a service-based network 205 associated with a second RAT (such as a 6G network).

[0113] Figure 4 An example of a wireless communication system 400 that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the wireless communication system 400 can implement or be implemented through aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, or any combination thereof. Specifically, the wireless communication system 400 can support signaling that enables a network entity 105 associated with a first RAT to facilitate communication between a UE 115 and core network services of a service-based network (such as a 6G network) associated with a second RAT, as described with respect to Figure 1 as described.

[0114] The wireless communication system 400 can include a UE 115-b, a first network entity 410-a (e.g., a first DU), a first core network service 405-a, a second network entity 410-b (e.g., a second DU), and a second core network service 405-b. In some implementations, the network entities 410-a, 410-b can include examples of O-RAN entities that include multiple components, such as one or more DUs, as Figure 3 shown and described. In this regard, Figure 4 the network entities 410-a, 410-b illustrated can additionally or alternatively be referred to as DUs or eDUs, as will be further shown and described herein.

[0115] For example, the core network services 405-a, 405-b can be associated with a service-based network, such as Figure 2 the service-based network 205 illustrated. In some aspects, the service-based network including the core network services 405 can be configured to communicate or interact with the RAN of the wireless communication system 400, where the RAN includes the one or more network entities (e.g., network entity 410). In some specific implementations, the core network services 405 can be associated with or hosted by a cloud platform, where the corresponding core network services 405 are hosted at corresponding network addresses or destinations in the cloud platform. In this regard, the communication (e.g., service message) can include a network address, a service ID, or other information indicating the corresponding destination of the corresponding core network service 405 as a communication within the service-based network.

[0116] In some aspects, the first network entity 410-a can be associated with a first RAT, such as LTE, 4G, or 5G RAT, and the second network entity 410-b can be associated with a second RAT, such as 6G or other service-based RAT. In this regard, the UE 115-b can communicate with the first network entity 410-a using the communication link 435-a, which can be an example of an NR or LTE link between the UE 115-b and the first network entity 410-a. Similarly, the UE 115-b can communicate with the second network entity 410-b using the communication link 435-b, which can be an example of a 6G link between the UE 115-b and the second network entity 410-b. In some cases, the communication links 435-a, 435-b can include examples of access links (e.g., Uu links), which can include a bidirectional link that enables both uplink and downlink communication between the UE 115-b and the corresponding network entity 410.

[0117] The corresponding network entity 410 can be configured to access or communicate (e.g., interact) with the core network services 405 of the service-based network via the communication links 440-a and 440-b, where the communication link 440 can be configured to facilitate two-way communication between the network entity 410 and the corresponding core network service 405. In some aspects, each core network service 405 can include a corresponding API configured to facilitate wireless communication with the corresponding network entity 410 and the UE 115-b, such as Figure 1 the network service API 180 illustrated. Although the core network services 405-a, 405-b are in Figure 4are illustrated as separate entities, but this is for illustrative purposes only. For example, in some cases, the first core network service 405-a and the second core network service 405-b may include the same core network service 405. In this regard, in some cases, the first network entity 410-a and the second network entity 410-b may be communicatively coupled to the same and / or different core network services 405.

[0118] In some aspects, the network entity 410 may facilitate traffic routing (e.g., service data unit routing) from the UE 115-b to the core network service 405, and vice versa. In other words, the network entity 410 may be configured to relay communications (e.g., service messages) from the UE 115-b to the core network service 405, and vice versa. The network entity 410 may facilitate traffic routing between the corresponding devices directly, via other network entities 410, via a proxy, or any combination thereof.

[0119] In some aspects, the wireless communication system 400 may support multiple deployment scenarios, including 5G and 6G stand-alone radio options (where 5GC or 6GC acts as the core network) and dual-connectivity operations. Additionally, as will be described in further detail herein, the wireless communication system 400 may support additional deployment scenarios in which various operations and functions are partitioned between RATs. For example, according to a first specific implementation, the UE 115-b may be configured to communicate with the first network entity 410-a using NG-RAN (e.g., 5G DU / RU 415) and a 6GC core network, where the 5G RAN (e.g., DU / RU 451) interacts with the cloud-native 6GC core network via a 6GC proxy service. According to a second specific implementation, the UE 115-b may be configured to communicate with a network entity 410 (not shown) using 6G-RAN (e.g., 6G DU / RU) and a 5G-CU' (e.g., an upgraded CU).

[0120] As previously noted herein, communication with core network services 405 provided by a service-based network (e.g., 6G or cloud-based network) may require more diverse protocols and communications that may not be supported by some network entities 410 associated with other RATs (such as 5G DU). For example, in some cases, a first network entity 410-a associated with a first RAT (e.g., 5G network entity 410-a) may not be able to perform 6G communication on its own (e.g., without dedicated 6G hardware / software). Thus, even in cases where UE 115-b is otherwise able to communicate with core network services 405, UE 115-b may still be unable to communicate with core network services 405 in cases where UE 115-b cannot access a network entity 410 configured to interact with the service-based network. Such drawbacks may slow down the migration from current RATs to service-based RATs. Additionally, the manufacturing and deployment of network entities 410 (e.g., eDU) that support core network services 405 of service-based networks may require significant time and investment, which may significantly slow down the migration from current RATs to service-based RATs (e.g., migration from 5G to 6G).

[0121] Accordingly, wireless communication system 400 may support signaling and mechanisms that enable a network entity 410 (e.g., first network entity 410-a, DU) associated with a first RAT (such as 5G RAT) to utilize signaling of the first RAT to facilitate communication with core network services 405 provided via a second RAT (such as 6G RAT). In other words, aspects of the present disclosure relate to techniques that enable 6G communication to be performed over a 5G network to facilitate migration to 6G services.

[0122] In this regard, aspects of the present disclosure may support independent 6G operation and 5G / 6G non-independent operation based on dual connectivity and network evolution. Additionally, aspects of the present disclosure may support infrastructure migration to service-based networks by enabling the use (e.g., reuse) of cloud platforms and fronthaul interfaces to enable co-located 5G and 6G operation. Additionally, aspects of the present disclosure may support spectrum migration by leveraging 5G spectrum bands to facilitate 6G communication on bands of existing deployments.

[0123] Specifically, in some embodiments, the first network entity 410-a (e.g., 5G DU) may include an adapter component 420, which may sometimes be referred to as a "5G / 6G adapter". The adapter component 420 may be configured to interact with a service-based network including core network services 405 and to translate communications between a first RAT (e.g., 5G, NR) and a second RAT (e.g., 6G). In this regard, the adapter component 420 may be configured to act as or serve as a DU (e.g., eDU 430) for the service-based network and may thus be configured to utilize 6G service contexts and routing APIs associated with the second RAT (e.g., 6G). Additionally, the adapter component 420 may be configured to act as or serve as a CU 425 for a DU / RU 415 associated with the first RAT (e.g., 5G, NR) via an F1 interface (e.g., F1-U / C). In some cases, the capability open API of the adapter component 420 may be configured to exchange capability information with the DU / RU 415.

[0124] The adapter component 420 may include hardware components, software components, or both, and may be added to the first network entity 410-a to enable the first network entity 410-a to facilitate communication between the UE 115-b and the service-based network. For example, the adapter component of the first network entity 410-a may relay or forward a service request to a destination (e.g., network address) associated with a first core network service 405-a via the second RAT (e.g., 6G). In this regard, the adapter component 420 may be configured to expose RAN services to the rest of the service-based network and vice versa.

[0125] In some aspects, the UE 115-b may send capability signaling to the first network entity 410-a, the second network entity 410-b, or both, where the capability signaling indicates the UE 115-b's ability to communicate with core network services 405 provided by a service-based network associated with a second RAT such as a 6G RAT.

[0126] In some aspects, the first network entity 410-a (e.g., 5G DU), the second network entity 410-b (e.g., 6G DU), or both may send control information indicating one or more core network services 405 provided by the service-based network that are accessible by the respective network entity 410. In this regard, the network (e.g., the RAN including network entities 410-a, 410-b) may be configured to broadcast the availability of the 6G network and associated core network services 405.

[0127] In some cases, control information may be indicated via System Information Block (SIB) messages. In other words, network entity 410 may utilize SIB messages to indicate or broadcast discovery information associated with 6G core network service 405. Network entity 410 may send control information (e.g., SIB) indicating the supported core network service 405 based on the received capability information indicating that UE 115-b is capable of communicating with core network service 405. Additionally, in some cases, UE 115-b may be able to query or request information associated with the available core network service 405.

[0128] For example, the first network entity 410-a may send a first SIB (e.g., via a first RAT) indicating that the first network entity 410-a is capable of facilitating communication with the first core network service 405-a, and the second network entity 410-b may send a second SIB (e.g., via a second RAT) indicating that the second network entity 410-b is capable of facilitating communication with the second core network service 405-b. As previously noted herein, the core network service 405 may be provided by a service-based network (e.g., a cloud-based network) associated with a second RAT (e.g., 6G), which is configured to interact with a RAN including the respective network entity 410 / DU.

[0129] In some cases, the respective network entity 410 and / or core network service 405 (via an API) may be able to determine the capabilities of UE 115-c and / or the network to support the respective core network service 405, and may thus be able to determine which capabilities are available. Accordingly, in some cases, network entity 410 and / or core network service 405 may be configured to enable / disable certain functions and / or core network service 405 associated with the second RAT based on the determined capabilities. For example, the first network entity 410-a and / or the first core network service 405-a may determine that certain 6G functions are not available to UE 115-b due to the capabilities of UE 115-b, the capabilities of the first network entity 410-a, or both. Thus, the control information indicating the available services and / or available functions of the first core network service 405-a may be customized based on the services / functions determined to be supported by the respective devices. As previously noted herein, the first core network service 405-a and the second core network service 405-b may be the same or different core network services 405.

[0130] In some aspects, UE 115-b may send a service request to a first network entity 410-a via a first RAT (e.g., 5G), where the service request indicates a first core network service 405-a provided (e.g., accessible) by the first network entity 410-a. For example, UE 115-b may use 5G signaling to request that the first network entity 410-a facilitate communication between UE 115-b and the first core network service 405-a associated with the 6G network. In this regard, UE 115-b may determine to connect to a service-based network (e.g., 6G network) via a legacy (e.g., 5G) RAN node (DU 415) based on discovering that the core network service 405 is available via the first network entity 410-a / DU 415 (e.g., based on the core network service 405 broadcast as available by DU 415 via SIB).

[0131] In some aspects, UE 115-b may send a service request (e.g., a connection request message) to the DU / RU 415 of the first network entity 410-a via one or more communication layers associated with the first RAT (e.g., 5G RAT), such as the PHY layer, MAC layer, RLC layer, or any combination thereof. In this regard, the service request may be conveyed via the 5G link layer (e.g., PHY, MAC, RLC), where the service request indicates a connection request for a 6G service. Additionally, when sending a message (e.g., a service request) intended for the core network service 405, UE 115-b may utilize a communication protocol associated with a second RAT (e.g., 6G protocol) above the PHY / MAC / RLC layers. In this regard, in some cases, UE 115-b may be configured to communicate with the first network entity 410-a in the stand-alone NR state using layer 1 (L1) and layer 2 (L2) signaling of the 6GC core network. Based on the UE115-b indicating that the signaling (e.g., service request) is intended for the core network service 405-a and based on the configuration, the network entity 410-a may be configured to select the CU 425 associated with the adapter component 420 during CU selection.

[0132] In some aspects, the service request may include a network address or other destination identifier associated with the first core network service 405-a, such that the first network entity 410-a (e.g., the adapter component 420, eDU 430) can forward or otherwise route the service request to the first core network service 405-a. In some aspects, the communication (e.g., service request) exchanged between the first network entity 410-a and the first core network service 405-a may be conveyed according to API information exchanged between the corresponding devices.

[0133] In some aspects, the first network entity 410-a may receive a service configuration request from the first core network service 405-a. In some aspects, the service configuration request may include a request for the first network entity 410-a to convert a service context associated with a second RAT (e.g., 6G service context) to a service configuration associated with a first RAT (e.g., 5G service configuration). In some cases, the service request message may indicate the service context associated with the communication between the first network entity 410-a and the first core network service 405-a. In this regard, the first core network service 405-a may take into account that UE 115-b is camped on a 5G cell (e.g., the first network entity 410-a) for service configuration, and may send a service configuration request based on determining that UE 115-b is communicating via the first network entity 410-a associated with the first RAT.

[0134] In other words, the first core network service 405-a may request the first network entity 410-a to convert the signaling from the first core network service 405-a intended for UE 115-a and the RAN configuration affecting the first network entity 410-a to a 5G service configuration and F1 signaling, such that 6G communication from the first core network service 405-a can be relayed to UE 115-b via 5G signaling. In other words, the first core network service 405-a may request the first network entity 410-a to forward 6G signaling from the first core network service 405-a to UE 115-b via the F1 interface, and based on the signaling provided by UE 115-b and intended for the service-based network, forward the signaling from UE 115-b intended for the 6G core network service 405-a (received from the DU via the F1 interface) to the first core network service 405-a

[0135] The first network entity 410-a may determine a service configuration for communicating with UE 115-b via the first RAT (e.g., 5G). In some aspects, the first network entity 410-a may determine the service configuration based on the service context associated with the second RAT (e.g., 6G) of the first core network service 405-a. In other words, the first network entity 410-a may determine a 5G service configuration for facilitating communication between UE 115-b and a 6G service-based network using 5G signaling with UE 115-b. In this regard, the first network entity 410-a may determine the service configuration based on receiving the service configuration request from the first core network service 405-a.

[0136] In some aspects, UE 115-b may receive control signaling from a first network entity 410-a, which indicates a service configuration for communicating with a first core network service 405-a via the first network entity 410-a. In other words, the first network entity 410-a may configure the UE 115-b with a 5G service configuration for communicating with the 6G core network service 405-a using 5G signaling.

[0137] Subsequently, the first network entity 410-a may relay one or more service messages between the UE 115-b and the first core network service 405-a. In other words, the first network entity 410-a may receive a service message from the UE 115-b and relay the service message to the first core network service 405-a, or vice versa. Additionally, the UE 115-b may use the 5G link layer protocol stack to continue all signaling and data transmission / reception associated with the second RAT (e.g., 6G signaling, including 6G service discovery, configuration, service activation / deactivation, data transmission / reception, etc.) towards the adapter component 420 via the DU / RU 415.

[0138] For example, the UE 115-b may send a first service message to the first network entity 410-a via a first RAT (e.g., 5G) and according to the service configuration, where the service message includes a destination (e.g., network address) and a payload of the first core network service 405-a. The UE 115-b may send the first service message via one or more communication layers (such as the PHY layer, MAC layer, RLC layer, or any combination thereof) associated with the first RAT (e.g., 5G RAT). In this example, the payload of the first service message may be in a format associated with the second RAT (e.g., 6G), such that the first network entity 410-a (e.g., the adapter component 420) may use the second RAT and relay or forward the first service message to the destination of the first core network service 405-a according to the service context for communication between the first network entity 410-a and the first core network service 405-a. In this regard, the first network entity 410-a may receive a 6G service message from the UE 115-a via 5G signaling and relay the 6G service message to the core network service 405-a via 6G signaling.

[0139] As another example, the first core network service 405-a may send a second service message to the first network entity 410-a via a second RAT (e.g., 6G) and according to a service context associated with the second RAT. In this example, the payload of the second service message may be in a format associated with the second RAT (e.g., 6G) such that the first network entity 410-a (e.g., the adapter component 420) may use the first RAT and according to a service configuration associated with the first RAT to relay or forward the second service message to the UE 115-b (e.g., convert 6G signaling to 5G signaling on the F1 interface). In this regard, the first network entity 410-a may relay the 6G service message received from the first core network service 405-a via 5G signaling relay.

[0140] In some cases, the UE 115-b may be configured to operate in a dual-connectivity or non-standalone operation mode or state, including connections associated with both a first RAT (e.g., 5G, NR) and a second RAT (e.g., 6G). In some aspects, the dual connectivity at the UE 115-b may be handled or managed by the dual-connectivity core network service 405. For example, the dual-connectivity service (e.g., the core network service 405) may control and manage the configuration for the dual connectivity at the UE 115-b, where the same data service may be configured to transmit and receive data to / from the UE 115-b using both RATs (e.g., both the first RAT and the second RAT).

[0141] For example, in some cases, the UE 115-b may establish a wireless connection with a second network entity 410-b (e.g., a second DU) associated with the second RAT. The UE 115-b may establish a connection with the second network entity 410-b based on operating in a dual-connectivity state. As previously noted herein, the second network entity 410-b may be capable of communicatively coupling to at least a second core network service 405-b provided by the service-based network. Thus, the UE 115-b may establish a connection with the second network entity 410-b based on receiving control information indicating the core network service 405 supported by the second network entity 410-b. The UE 115-b may be configured to establish a dual connection with the second network entity 410-b by sending a service request for the service of the second core network service 405-b, as described herein.

[0142] In some aspects, UE 115-b may receive control signaling from a second network entity 410-b, where the control signaling indicates a service context that can be used to communicate with a second core network service 405-b via a second RAT. In this regard, compared to the service configuration associated with the first RAT (e.g., 5G, NR) and the first network entity 410-a, the second network entity 410-b may indicate a service context associated with the second RAT (e.g., 6G), such that UE 115-b can utilize signaling (e.g., 6G signaling and protocols) associated with the second RAT to communicate with the second network entity 410-b and the second core network service 405-b.

[0143] Subsequently, the second network entity 410-b may relay one or more service messages between UE 115-b and the second core network service 405-b. In other words, the second network entity 410-b may receive a service message from UE 115-b and relay the service message to the second core network service 405-b, or vice versa.

[0144] For example, UE 115-b may send a third service message to the second network entity 410-b via a second RAT (e.g., 6G) and according to the service context, where the third service message includes a destination (e.g., network address) and a payload of the second core network service 405-b. In this example, the payload of the third service message may be in a format associated with the second RAT (e.g., 6G), such that the second network entity 410-b can use the second RAT and relay or forward the third service message to the destination of the second core network service 405-b according to the service context.

[0145] As another example, the second core network service 405-b may send a fourth service message to the second network entity 410-b via a second RAT (e.g., 6G) and according to the service context associated with the second RAT. In this example, the payload of the second service message may be in a format associated with the second RAT (e.g., 6G), such that the second network entity 410-b can use the second RAT and relay or forward the fourth service message to UE 115-b according to the service context.

[0146] The techniques described herein enable a DU associated with a first RAT (e.g., 4G, 5G), such as a first network entity 410-a, to facilitate communication between a UE 115-b and a core network service 405 associated with a second RAT (e.g., 6G) of a service-based network. In other words, aspects of the present disclosure enable a 5G DU (e.g., a first network entity 410-a) to use 5G signaling to provide a UE 115 with access to a service-based network based on 6G services. Accordingly, the aspects described herein can reduce the costs associated with building a service-based network and can increase the speed at which a wireless network can migrate to a service-based network. Additionally, by enabling a DU associated with a first RAT to facilitate communication with a service-based network associated with a second RAT, aspects of the present disclosure can facilitate broader access to a service-based network when building the infrastructure of a service-based network.

[0147] Figure 5 An example of a process flow 500 that illustrates techniques in support of establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure is shown. In some examples, aspects of the process flow 500 may implement aspects of or be implemented by aspects of a wireless communication system 100, a wireless communication system 200, a network architecture 300, a wireless communication system 400, or any combination thereof. Specifically, the process flow 500 illustrates signaling that enables a network entity associated with a first RAT (e.g., a DU 510) to facilitate communication between a UE 115 and a core network service 505 of a service-based network (such as a 6G network) associated with a second RAT, as referenced Figure 1 – Figure 4 as described.

[0148] The process flow 500 may include a UE 115-c, a first DU 510-a (e.g., a first network entity), a first core network service 505-a, a second DU 510-b (e.g., a second network entity), and a second core network service 505-b, which may be examples of the UE 115, network entity 105, core network services, and other wireless devices referenced Figure 1 – Figure 4 as described. For example, Figure 5 the first DU 510-a and the second DU 510-b illustrated may include examples of the first network entity 410-a and the second network entity 410-b illustrated as Figure 4 such. In this regard, the first DU 510-a may be associated with a first RAT (e.g., 5G, NR), and the second DU 510-b may be associated with a second RAT (e.g., 6G).

[0149] In some aspects, the core network services 505-a, 505-b may be included within a set of services provided or offered by a service-based network, such as the service-based network 205 exemplified by Figure 2 In such cases, the service-based network including the core network services 505 may be configured to interact (e.g., communicate) with the RAN including the respective DUs 510 in order to facilitate communication between the service-based network and the UE 115-c.

[0150] In some examples, the operations exemplified in the process flow 500 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software), or any combination thereof. Alternative examples may be implemented, where some steps are performed in an order different from the described order or not at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added.

[0151] At 515, the UE 115-c may send capability signaling to the first DU 510-a, the second DU 510-b, or both, where the capability signaling indicates the ability of the UE 115-c to communicate with the core network service 505 provided by a service-based network associated with a second RAT (such as a 6G RAT).

[0152] At 520, the first DU 510-a (e.g., 5G DU 510-a), the second DU 510-b (e.g., 6G DU 510-b), or both may send control information indicating one or more core network services 505 provided by the service-based network that are accessible by the respective DU 510. In this regard, the network (e.g., the RAN including DUs 510-a, 510-b) may be configured to broadcast the availability of the 6G network and the associated core network services 505. In some cases, the control information may be indicated via an SIB message sent over a first RAT (e.g., 5G). The DU 510 may send control information (e.g., SIB) indicating the supported core network services 505 based on the capability information received at 515 indicating that the UE 115-c is capable of communicating with the core network service 505.

[0153] For example, the first DU 510-a may send a first SIB indicating that the first DU 510-a is capable of facilitating communication with the first core network service 505-a, and the second DU 510-b may send a second SIB indicating that the second DU 510-b is capable of facilitating communication with the second core network service 505-b. As previously noted herein, the core network service 505 may be provided by a service-based network (e.g., a cloud-based network) associated with a second RAT (e.g., 6G), which is configured to interact with the RAN including the respective DUs 510.

[0154] At 525, the UE 115-c may send a service request to the first DU 510-a via a first RAT (e.g., 5G), the service request indicating a first core network service 505-a provided (e.g., accessible) by the first DU 510-a. For example, the UE 115-c may use 5G signaling to request that the first DU 510-a facilitate communication between the UE 115-c and the first core network service 505-a associated with the 6G network. The UE 115-c may send the service request via one or more communication layers (such as the PHY layer, MAC layer, RLC layer, or any combination thereof) associated with the first RAT (e.g., 5G RAT). The UE 115-c may send the service request at 525 based on sending capability signaling at 515, receiving a control message at 520, or both.

[0155] In some aspects, the service request may include a network address or other destination identifier associated with the first core network service 505-a such that the first DU 510-a can forward or otherwise route the service request to the first core network service 505-a. In some aspects, the communication (e.g., service request) exchanged between the first DU 510-a and the first core network service 505-a may be conveyed according to API information exchanged between the respective devices.

[0156] As previously noted herein, in some embodiments, the first DU 510-a (e.g., 5G DU 510-a) may include an adapter component (e.g., 5G / 6G adapter), such as Figure 4The illustrated adapter component 420. The adapter component can be configured to interact with a service-based network including a core network service 505 and to translate communications between a first RAT (e.g., 5G, NR) and a second RAT (e.g., 6G). The adapter component can include hardware components, software components, or both, and can be added to a first DU 510-a to enable the first DU 510-a to facilitate communications between a UE 115-c and the service-based network. For example, the adapter component of the first DU 510-a can relay or forward a service request to a destination (e.g., a network address) associated with a first core network service 505-a via a second RAT (e.g., 6G).

[0157] At 530, the first DU 510-a can receive a service configuration request from a first core network service 505-a. In some aspects, the service configuration request can include a request for the first DU 510-a to translate a service context associated with a second RAT (e.g., 6G service context) into a service configuration associated with a first RAT (e.g., 5G service configuration). In some cases, the request or message at 530 can indicate a service context associated with communications between the first DU 510-a and the first core network service 505-a.

[0158] In other words, the first core network service 505-a can request the first DU 510-a to translate signaling from the first core network service 505-a intended for a UE 115-a and RAN configurations affecting the first DU 510-a into a 5G service configuration and F1 signaling such that 6G communications from the first core network service 505-a can be relayed to the UE 115-c via 5G signaling. In other words, the first core network service 505-a can request the first DU 510-a to forward 6G signaling from the first core network service 505-a to the UE 115-c via the F1 interface and, based on signaling provided by the UE 115-c and intended for the service-based network, forward signaling from the UE 115-c intended for the 6G core network service 505-a (received from the DU via the F1 interface) to the first core network service 505-a

[0159] At 535, the first DU 510-a may determine a service configuration for communicating with the UE 115-c via a first RAT (e.g., 5G). In some aspects, the first DU 510-a may determine the service configuration at 535 based on a service context associated with a second RAT (e.g., 6G) of the first core network service 505-a. In other words, the first DU 510-a may determine a 5G service configuration for using 5G signaling with the UE 115-c to facilitate communication between the UE 115-c and a network based on a 6G service. In this regard, the first DU 510-a may determine the service configuration at 535 based on receiving a service configuration request at 530.

[0160] At 540, the UE 115-c may receive control signaling from the first DU 510-a that indicates a service configuration for communicating with the first core network service 505-a via the first DU 510-a. In other words, the first DU 510-a may configure the UE 115-c with a 5G service configuration for communicating with the 6G core network service 505-a using 5G signaling. The UE 115-c may receive the control signaling at 540 based on sending capability signaling at 515, receiving control information at 510, sending a service request at 525, or any combination thereof.

[0161] At 545, the first DU 510-a may relay one or more service messages between the UE 115-c and the first core network service 505-a. In other words, the first DU 510-a may receive a service message from the UE 115-c and relay the service message to the first core network service 505-a, or vice versa.

[0162] For example, UE 115-c may send a first service message to the first DU 510-a via a first RAT (e.g., 5G) and according to a service configuration, where the service message includes a destination (e.g., network address) of the first core network service 505-a and a payload. UE 115-c may send the first service message via one or more communication layers associated with the first RAT (e.g., 5G RAT), such as the PHY layer, MAC layer, RLC layer, or any combination thereof. In this example, the payload of the first service message may be in a format associated with a second RAT (e.g., 6G), such that the first DU 510-a (e.g., an adapter component) may use the second RAT and relay or forward the first service message to the destination of the first core network service 505-a according to a service context for communication between the DU 510-a and the first core network service 505-a. In this regard, the first DU 510-a may receive a 6G service message from the UE 115-a via 5G signaling and relay the 6G service message to the core network service 505-a via 6G signaling.

[0163] As another example, the first core network service 505-a may send a second service message to the first DU 510-a via a second RAT (e.g., 6G) and according to a service context associated with the second RAT. In this example, the payload of the second service message may be in a format associated with the second RAT (e.g., 6G), such that the first DU 510-a (e.g., an adapter component) may use the first RAT and relay or forward the second service message to the UE 115-c (e.g., convert 6G signaling to 5G signaling on the F1 interface) according to a service configuration associated with the first RAT. In this regard, the first DU 510-a may relay a 6G service message received from the first core network service 505-a via 5G signaling.

[0164] In some cases, UE 115-c may be configured to operate in a dual-connectivity or non-standalone operation mode or state, including connections associated with both a first RAT (e.g., 5G, NR) and a second RAT (e.g., 6G). In such cases, the process flow 500 may proceed to 550.

[0165] At 550, UE 115-c may establish a wireless connection with a second DU 510-b associated with a second RAT. UE 115-c may establish a connection with the second DU 510-b based on operating in a dual-connectivity state. As previously noted herein, the second DU 510-b may be communicatively coupled to at least a second core network service 505-b provided by a service-based network. Thus, UE 115-c may establish a connection with the second DU 510-b based on control information received from the second DU 510-b at 520. UE 115-c may be configured to establish a dual-connection with the second DU 510-b by sending a service request for a service of the second core network service 505-b, as described herein.

[0166] At 555, UE 115-c may receive control signaling that indicates a service context available for communicating with the second core network service 505-b via the second RAT. In this regard, compared to the service configuration associated with the first RAT (e.g., 5G, NR) at 540, the second DU 510-b may indicate a service context associated with the second RAT (e.g., 6G) such that UE 115-c may communicate with the second DU 510-b and the second core network service 505-b using signaling associated with the second RAT.

[0167] At 560, the second DU 510-b may relay one or more service messages between UE 115-c and the second core network service 505-b. In other words, the second DU 510-b may receive a service message from UE 115-c and relay the service message to the second core network service 505-b, or vice versa.

[0168] For example, UE 115-c may send a third service message to the second DU 510-b via the second RAT (e.g., 6G) and according to the service context, where the third service message includes a destination (e.g., network address) and a payload of the second core network service 505-a. In this example, the payload of the third service message may be in a format associated with the second RAT (e.g., 6G) such that the second DU 510-b may relay or forward the third service message to the destination of the second core network service 505-b using the second RAT and according to the service context.

[0169] As another example, the second core network service 505-b may send a fourth service message to the second DU 510-b via a second RAT (e.g., 6G) and according to a service context associated with the second RAT. In this example, the payload of the second service message may be in a format associated with the second RAT (e.g., 6G), such that the second DU 510-b may use the second RAT and relay or forward the fourth service message to the UE 115-c according to the service context.

[0170] The techniques described herein may enable a DU associated with a first RAT (e.g., 4G, 5G) (e.g., the first DU 510-a) to facilitate communication between the UE 115-c and a core network service 505 associated with a second RAT (e.g., 6G) of a service-based network. Stated another way, aspects of the present disclosure may enable a 5G DU 510 to use 5G signaling to provide the UE 115 access to a service-based network based on 6G services. Accordingly, the aspects described herein may reduce the cost associated with building a service-based network and may increase the speed at which a wireless network can migrate to a service-based network. Additionally, by enabling a DU 510 associated with a first RAT to facilitate communication with a service-based network associated with a second RAT, aspects of the present disclosure may facilitate broader access to a service-based network when building the infrastructure of a service-based network.

[0171] Figure 6 Block diagram 600 illustrates a device 605 supporting techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of the UE 115 described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0172] The receiver 610 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 related to techniques for establishing a connection to a service-based network via a RAN). The information may be delivered to other components of the device 605. The receiver 610 may utilize a single antenna or a group of multiple antennas.

[0173] The transmitter 615 can provide components for transmitting signals generated by other components of the device 605. For example, the transmitter 615 can transmit information associated with various information channels (e.g., control channels, data channels, information channels related to the technology for establishing a connection to a service-based network via the RAN), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 615 can be co-located with the receiver 610 in a transceiver module. The transmitter 615 can utilize a single antenna or a set of multiple antennas.

[0174] The communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can be examples of components for performing aspects of the techniques for establishing a connection to a service-based network via the RAN as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can support methods for performing one or more of the functions described herein.

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

[0176] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can 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 configured to or otherwise supporting components for performing the functions described in this disclosure.

[0177] In some examples, the communication manager 620 may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 620 may receive information from the receiver 610, convey information to the transmitter 615, or integrate in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0178] For example, the communication manager 620 may be configured to or otherwise support components for the following operations: receive control information from a DU associated with a first RAT of a RAN, the control information indicating a core network service provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN. The communication manager 620 may be configured to or otherwise support components for the following operations: send a service request via the first RAT and based on the control information, the service request indicating a core network service provided by a service-based network associated with a second RAT. The communication manager 620 may be configured to or otherwise support components for the following operations: receive control signaling from the DU, the control signaling indicating a service configuration for communicating with a core network service provided by the service-based network based on the service request, the service configuration indicating a destination associated with the core network service. The communication manager 620 may be configured to or otherwise support components for the following operations: send a service message to the DU via the first RAT and according to the service configuration, the service message including a destination associated with the core network service and a payload, the payload being in a format associated with a second RAT.

[0179] By including or configuring a communication manager 620 according to examples as described herein, a device 605 (e.g., a processor that controls or otherwise is coupled to the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) may support techniques that enable a DU associated with a first RAT (e.g., 4G, 5G) to facilitate communication between a UE 115 and a core network service associated with a second RAT (e.g., 6G) of a service-based network. Stated another way, aspects of the present disclosure may enable a 5G DU to use 5G signaling to provide a UE 115 with access to a service-based network based on 6G services. Accordingly, the aspects described herein may reduce the costs associated with building a service-based network and may increase the speed at which a wireless network can migrate to a service-based network. Additionally, by enabling a DU associated with a first RAT to facilitate communication with a service-based network associated with a second RAT, aspects of the present disclosure may facilitate broader access to service-based networks when building the infrastructure of a service-based network.

[0180] Figure 7 FIG. 700 is a block diagram illustrating a device 705 that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure. The device 705 may be an example of aspects of the device 605 or UE 115 described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0181] 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 related to techniques for establishing a connection to a service-based network via a RAN). The information may be delivered to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.

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

[0183] The device 705 or its various components may be examples of means for performing various aspects of the techniques for establishing a connection to a service-based network via a RAN described herein. For example, the communication manager 720 may include a control signaling reception manager 725, a service request transmission manager 730, a service message transmission manager 735, or any combination thereof. The communication manager 720 may be an example of aspects of the communication manager 620 described herein. In some examples, the communication manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 may receive information from the receiver 710, convey information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations described herein.

[0184] The control signaling reception manager 725 may be configured to or otherwise support components for the following operations: receive control information from a DU associated with a first RAT of the RAN, the control information indicating core network services provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN. The service request transmission manager 730 may be configured to or otherwise support components for the following operations: transmit a service request via the first RAT and based on the control information, the service request indicating core network services provided by a service-based network associated with a second RAT. The control signaling reception manager 725 may be configured to or otherwise support components for the following operations: receive control signaling from the DU, the control signaling indicating a service configuration for communicating with the core network services provided by the service-based network based on the service request, the service configuration indicating a destination associated with the core network services. The service message transmission manager 735 may be configured to or otherwise support components for the following operations: transmit a service message to the DU via the first RAT and according to the service configuration, the service message including a destination associated with the core network services and a payload, the payload being in a format associated with the second RAT.

[0185] Figure 8 Block diagram 800 illustrates a communication manager 820 that supports techniques for establishing a connection to a service-based network via a RAN, in accordance with one or more aspects of the present disclosure. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of the techniques for establishing a connection to a service-based network via a RAN as described herein. For example, the communication manager 820 may include a control signaling reception manager 825, a service request transmission manager 830, a service message transmission manager 835, an SIB message reception manager 840, a capability signaling transmission manager 845, a dual connectivity manager 850, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0186] The control signaling reception manager 825 may be configured to or otherwise support components for the following operations: receive control information from a DU associated with a first RAT of a RAN, the control information indicating a core network service provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN. The service request transmission manager 830 may be configured to or otherwise support components for the following operations: transmit a service request via the first RAT and based on the control information, the service request indicating a core network service provided by a service-based network associated with a second RAT. In some examples, the control signaling reception manager 825 may be configured to or otherwise support components for the following operations: receive control signaling from the DU, the control signaling indicating a service configuration for communicating with a core network service provided by the service-based network based on the service request, the service configuration indicating a destination associated with the core network service. The service message transmission manager 835 may be configured to or otherwise support components for the following operations: transmit a service message to the DU via the first RAT and according to the service configuration, the service message including a destination and a payload associated with the core network service, the payload being in a format associated with the second RAT.

[0187] In some examples, the SIB message reception manager 840 may be configured to or otherwise support components for the following operations: receive an SIB message including control information from the DU, wherein the SIB message is received via the first RAT.

[0188] In some examples, the capability signaling transmission manager 845 may be configured to or otherwise support components for the following operations: transmit capability signaling to the DU via the first RAT, the capability signaling indicating the UE's capability to communicate with a core network service provided by a service-based network associated with a second RAT, wherein the reception of the control information is based on the capability signaling.

[0189] In some examples, the dual connection manager 850 may be configured to or otherwise support components for the following operations: establish a wireless connection with a second DU associated with a second RAT based on operating in a dual connection state, wherein the second DU is communicatively coupled to at least a second core network service provided by the service-based network. In some examples, the service message transmission manager 835 may be configured to or otherwise support components for the following operations: transmit a second service message to the second DU via the second RAT, the second service message including a second destination associated with the second core network service, the service message further including additional service data associated with the second core network service, the additional service data including an additional payload in a format associated with the second RAT.

[0190] In some examples, the control signaling reception manager 825 may be configured to or otherwise support components for the following operations: receiving second control signaling from a second DU, the second control signaling indicating a service context for communicating with a second core network service via a second RAT, wherein a second service message is sent according to the service context.

[0191] In some examples, the service request and the service message are sent via one or more communication layers associated with a first RAT, the one or more communication layers including a PHY layer, a MAC layer, an RLC layer, or any combination thereof.

[0192] In some examples, the service request, the service message, or both are sent to a DU for relaying to a destination associated with a core network service. In some examples, the first RAT includes a 5G RAT, an NR access technology, or both. In some examples, the second RAT includes a 6G RAT.

[0193] Figure 9 FIG. illustrates a diagram of a system 900 including a device 905 that supports techniques for establishing a connection to a service-based network via a RAN according to one or more aspects of the present disclosure. The device 905 may be an example of the device 605, the device 705, or the UE 115 described herein, or include components thereof. The device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). The device 905 may include components for two-way voice and data communication, the components including components for sending and receiving communication, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may communicate electronically via one or more buses (e.g., bus 945) or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) coupled.

[0194] The I / O controller 910 may manage input signals and output signals of the device 905. The I / O controller 910 may also manage peripheral devices not integrated into the device 905. In some cases, the I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 910 may utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 910 may represent, or interact with, a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor (such as processor 940). In some cases, a user may interact with device 905 via I / O controller 910 or via a hardware component controlled by I / O controller 910.

[0195] In some cases, device 905 may include a single antenna 925. However, in some other cases, device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925, wired or wireless links, as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem that is configured to: modulate packets; provide the modulated packets to one or more antennas 925 for transmission; and demodulate packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be examples of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof, or components thereof, as described herein.

[0196] Memory 930 may include random access memory (RAM) and read only memory (ROM). Memory 930 may store computer-readable, computer-executable code 935 that includes instructions that, when executed by processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored on a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, code 935 may not be directly executable by processor 940 but may, for example, cause a computer to perform the functions described herein when compiled and executed. In some cases, memory 930 may contain a basic input / output system (BIOS), etc., that may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0197] The processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting techniques for establishing a connection to a service-based network via a RAN). For example, the device 905 or components of the device 905 may include the processor 940 and a memory 930 coupled to or coupled with the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0198] For example, the communication manager 920 may be configured to or otherwise support components for: receiving control information from a DU associated with a first RAT of a RAN, the control information indicating core network services provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN. The communication manager 920 may be configured to or otherwise support components for: sending a service request via the first RAT and based on the control information, the service request indicating core network services provided by a service-based network associated with a second RAT. The communication manager 920 may be configured to or otherwise support components for: receiving control signaling from the DU, the control signaling indicating a service configuration for communicating with the core network services provided by the service-based network based on the service request, the service configuration indicating a destination associated with the core network services. The communication manager 920 may be configured to or otherwise support components for: sending a service message to the DU via the first RAT and according to the service configuration, the service message including a destination associated with the core network services and a payload, the payload being in a format associated with a second RAT.

[0199] By including or configuring a communication manager 920 according to examples as described herein, a device 905 may support techniques that enable a DU associated with a first RAT (e.g., 4G, 5G) to facilitate communication between a UE 115 and a core network service associated with a second RAT (e.g., 6G) of a service-based network. Stated another way, aspects of the present disclosure may enable a 5G DU to utilize 5G signaling to provide a UE 115 access to a service-based network over 6G. Accordingly, aspects described herein may reduce costs associated with building a service-based network and may increase the speed at which a wireless network can migrate to a service-based network. Additionally, by enabling a DU associated with a first RAT to facilitate communication with a service-based network associated with a second RAT, aspects of the present disclosure may facilitate broader access to service-based networks when building the infrastructure of a service-based network.

[0200] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise in conjunction with transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by processor 940, memory 930, code 935, or any combination thereof. For example, code 935 may include instructions executable by processor 940 to cause the device 905 to perform aspects of the techniques described herein for establishing a connection to a service-based network via a RAN, or processor 940 and memory 930 may otherwise be configured to perform or support such operations.

[0201] Figure 10 Block diagram 1000 illustrates a device 1005 that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

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

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

[0204] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or their various components may be examples of components for performing aspects of the techniques described herein for establishing a connection to a service-based network via a RAN. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

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

[0206] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices that is configured to or otherwise supports components for performing the functions described in this disclosure.

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

[0208] For example, the communication manager 1020 may be configured to or otherwise support components for the following operations: receiving a service message from a core network service provided by a service-based network associated with a second RAT, wherein the service-based network is configured to interact with a RAN associated with a first RAT, and the service message indicates a service context for communication between the UE and the core network service associated with the second RAT. The communication manager 1020 may be configured to or otherwise support components for the following operations: determining a service configuration for communicating with the UE via the first RAT based on the service context associated with the second RAT. The communication manager 1020 may be configured to or otherwise support components for the following operations: sending a service message to the UE via the first RAT and according to the service configuration, the service message including a payload in a format associated with the second RAT.

[0209] By including or configuring a communication manager 1020 according to the examples described herein, a device 1005 (e.g., a processor that controls or otherwise is coupled to a receiver 1010, a transmitter 1015, the communication manager 1020, or a combination thereof) may support techniques that enable a DU associated with a first RAT (e.g., 4G, 5G) to facilitate communication between a UE 115 and a core network service associated with a second RAT (e.g., 6G) of a service-based network. Stated another way, aspects of the present disclosure may enable a 5G DU to use 5G signaling to provide a UE 115 access to a 6G service-based network. Accordingly, the aspects described herein may reduce costs associated with building a service-based network and may increase the speed at which a wireless network can migrate to a service-based network. Additionally, by enabling a DU associated with a first RAT to facilitate communication with a service-based network associated with a second RAT, aspects of the present disclosure may facilitate broader access to service-based networks when building the infrastructure of a service-based network.

[0210] Figure 11 Block diagram 1100 illustrates a device 1105 that supports techniques for establishing a connection to a service-based network via a RAN according to one or more aspects of the present disclosure. The device 1105 may be an example of aspects of the device 1005 or the network entity 105 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 one another (e.g., via one or more buses).

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

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

[0213] The device 1105 or its various components may be examples of components for performing aspects of techniques for establishing a connection to a service-based network via a RAN as described herein. For example, the communication manager 1120 may include a service message receiving manager 1125, a service configuration manager 1130, a service message transmitting manager 1135, or any combination thereof. The communication manager 1120 may be an example of aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communication manager 1120 may receive information from the receiver 1110, convey information to the transmitter 1115, or integrate in combination with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0214] The service message receiving manager 1125 may be configured to or otherwise support components for the following operations: receiving a service message from a core network service provided by a service-based network associated with a second RAT, where the service-based network is configured to interact with a RAN associated with a first RAT, the service message indicating a service context for communication between the UE and the core network service associated with the second RAT. The service configuration manager 1130 may be configured to or otherwise support components for the following operations: determining a service configuration for communicating with the UE via the first RAT based on the service context associated with the second RAT. The service message sending manager 1135 may be configured to or otherwise support components for the following operations: sending a service message to the UE via the first RAT and according to the service configuration, the service message including a payload in a format associated with the second RAT.

[0215] Figure 12 Block diagram 1200 illustrates a communication manager 1220 that supports techniques for establishing a connection to a service-based network via a RAN, in accordance with one or more aspects of the present disclosure. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both, as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of the techniques for establishing a connection to a service-based network via a RAN, as described herein. For example, the communication manager 1220 may include a service message receiving manager 1225, a service configuration manager 1230, a service message sending manager 1235, a service configuration request receiving manager 1240, an SIB message sending manager 1245, a service request receiving manager 1250, a service request sending manager 1255, a control signaling sending manager 1260, a capability signaling receiving manager 1265, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0216] The service message receiving manager 1225 may be configured to or otherwise support components for the following operations: receiving service messages from a core network service provided by a service-based network associated with a second RAT, where the service-based network is configured to interact with a RAN associated with a first RAT, and the service messages indicate a service context for communication between the UE and the core network service associated with the second RAT. The service configuration manager 1230 may be configured to or otherwise support components for the following operations: determining a service configuration for communicating with the UE via the first RAT based on the service context associated with the second RAT. The service message sending manager 1235 may be configured to or otherwise support components for the following operations: sending a service message to the UE via the first RAT and according to the service configuration, where the service message includes a payload in a format associated with the second RAT.

[0217] In some examples, the service configuration request receiving manager 1240 may be configured to or otherwise support components for the following operations: receiving a service configuration request from the core network service via a service message, where the service configuration request is for converting the service context associated with the second RAT into a service configuration associated with the first RAT, and where determining the service configuration and sending the service message are based on receiving the service configuration request.

[0218] In some examples, the SIB message sending manager 1245 may be configured to or otherwise support components for the following operations: sending a SIB message to the UE via the first RAT, where the SIB message indicates a core network service provided by the service-based network. In some examples, the service request receiving manager 1250 may be configured to or otherwise support components for the following operations: receiving a service request indicating the core network service from the UE via the first RAT and based on the SIB message. In some examples, the service request sending manager 1255 may be configured to or otherwise support components for the following operations: and sending the service request to a destination associated with the core network service via the second RAT, where receiving the service message is based on sending the service request.

[0219] In some examples, the capability signaling receiving manager 1265 may be configured to or otherwise support components for the following operations: receiving capability signaling from the UE via the first RAT, where the capability signaling indicates the UE's ability to communicate with a core network service provided by a service-based network associated with the second RAT, and where sending the SIB message is based on the capability signaling.

[0220] In some examples, the service message is received via an adapter component of the DU. In some examples, the adapter component is configured to interact with a service-based network and to translate communications between a first RAT and a second RAT. In some examples, the adapter component includes a hardware component, a software component, or both.

[0221] In some examples, the control signaling sending manager 1260 may be configured to or otherwise support components for: sending control signaling to a core network service, the control signaling indicating application programming interface information associated with the DU, wherein the service message is received via the second RAT based on the application programming interface information.

[0222] In some examples, the service message is sent via one or more communication layers associated with the first RAT, the one or more communication layers including a PHY layer, a MAC layer, an RLC layer, or any combination thereof. In some examples, the first RAT includes a 5G RAT, an NR access technology, or both. In some examples, the second RAT includes a 6G RAT.

[0223] Figure 13 FIG. 1300 illustrates a system 1300 including an apparatus 1305 that supports techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure. The apparatus 1305 may be an example of the apparatus 1005, the apparatus 1105, or the network entity 105 as described herein, or may include components thereof. The apparatus 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and the communication may include communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. The apparatus 1305 may include components that support output and acquisition of communication, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, code 1330, and a processor 1335. These components may communicate electronically via one or more buses (e.g., bus 1340) or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) coupled.

[0224] The transceiver 1310 may support two-way communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. The transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some embodiments, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmitting or output operations, or a combination thereof. In some embodiments, the transceiver 1310 may include one or more processors or memory components or be configured to be coupled to the one or more processors or memory components, and the one or more processors or memory components are capable of operating to perform or support operations based on received or obtained information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip assembly installed in the device 1305. In some examples, the transceiver may be capable of operating to support communication via one or more communication links (e.g., communication link 125, fronthaul communication link 120, midhaul communication link, fronthaul communication link 168).

[0225] The memory 1325 may include RAM and ROM. The memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by the processor 1335, cause the device 1305 to perform the various functions described herein. The code 1330 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 1330 may not be directly executable by the processor 1335, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1325 may also contain a BIOS and the like, which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0226] The processor 1335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting techniques for establishing a connection to a service-based network via the RAN). For example, the device 1305 or components of the device 1305 may include the processor 1335 and the memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform the various functions described herein. The processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that may host functions for performing the functions of the device 1305 (e.g., by executing the code 1330). The processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as within the memory 1325). In some specific implementations, the processor 1335 may be a component of a processing system. A processing system generally may refer to a system or series of machines or components that receive inputs and process those inputs to produce a set of outputs (which may be delivered to other systems or components of, for example, the device 1305). For example, the processing system of the device 1305 may refer to a system including various other components or sub-components of the device 1305 (such as the processor 1335, or the transceiver 1310, or the communication manager 1320, or a combination of other components or components of the device 1305). The processing system of the device 1305 may interact with other components of the device 1305 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of the device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, and so on. In some specific implementations, one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter such that the device 1305 may transmit information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver such that the device 1305 may obtain information or signal inputs, and the information may be delivered to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0227] In some examples, bus 1340 may support communication within a protocol layer of a protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communication performed within components of device 1305, or communication performed between different components that may be co-located or located at different positions within device 1305 (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one component or divided among different components).

[0228] In some examples, communication manager 1320 may manage (e.g., via one or more wired or wireless backhaul links) aspects of communication with a core network. For example, communication manager 1320 may manage the delivery of data communication for client devices such as one or more UEs 115. In some examples, communication manager 1320 may manage communication with other network entities 105 and may include a controller or scheduler for coordinating with other network entities 105 to control communication with UEs 115. In some examples, communication manager 1320 may support the X2 interface within LTE / LTE-A radio communication network technologies to provide communication between network entities 105.

[0229] For example, communication manager 1320 may be configured to or otherwise support components for: receiving a service message from a core network service provided by a service-based network associated with a second RAT, where the service-based network is configured to interact with a RAN associated with a first RAT, the service message indicating a service context for communication between the UE and the core network service associated with the second RAT. Communication manager 1320 may be configured to or otherwise support components for: determining a service configuration for communicating with the UE via the first RAT based on the service context associated with the second RAT. Communication manager 1320 may be configured to or otherwise support components for: sending a service message to the UE via the first RAT and according to the service configuration, the service message including a payload in a format associated with the second RAT.

[0230] By including or configuring a communication manager 1320 according to examples as described herein, device 1305 may support techniques that enable a DU associated with a first RAT (e.g., 4G, 5G) to facilitate communication between UE 115 and a core network service associated with a second RAT (e.g., 6G) of a service-based network. In other words, aspects of the present disclosure may enable a 5G DU to use 5G signaling to provide UE 115 with access to a service-based network over 6G. Accordingly, the aspects described herein may reduce the costs associated with building a service-based network and may increase the speed at which a wireless network can migrate to a service-based network. Additionally, by enabling a DU associated with a first RAT to facilitate communication with a service-based network associated with a second RAT, aspects of the present disclosure may facilitate broader access to service-based networks when building the infrastructure of a service-based network.

[0231] In some examples, communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in concert with transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although communication manager 1320 is illustrated as a separate component, in some examples, one or more of the functions described with reference to communication manager 1320 may be supported or performed by transceiver 1310, processor 1335, memory 1325, code 1330, or any combination thereof. For example, code 1330 may include instructions that can be executed by processor 1335 to cause device 1305 to perform aspects of the techniques described herein for establishing a connection to a service-based network via a RAN, or processor 1335 and memory 1325 may otherwise be configured to perform or support such operations.

[0232] Figure 14 A flowchart is illustrated that depicts a method 1400 for supporting techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure. The operations of method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of method 1400 may be performed by UE 115 as described with reference to Figures 1 to 9 In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0233] At 1405, the method may include: receiving control information from a DU associated with a first RAT of a RAN, the control information indicating a core network service provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN. The operations at 1405 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1405 may be performed by a control signaling reception manager 825 as described with reference to Figure 8 The control signaling reception manager 825 described.

[0234] At 1410, the method may include: sending a service request via the first RAT and at least partially based on the control information, the service request indicating a core network service provided by a service-based network associated with a second RAT. The operations at 1410 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1410 may be performed by a service request sending manager 830 as described with reference to Figure 8 The service request sending manager 830 described.

[0235] At 1415, the method may include: receiving control signaling from the DU, the control signaling indicating a service configuration for communicating with a core network service provided at least partially based on the service request by the service-based network, the service configuration indicating a destination associated with the core network service. The operations at 1415 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1415 may be performed by a control signaling reception manager 825 as described with reference to Figure 8 The control signaling reception manager 825 described.

[0236] At 1420, the method may include: sending a service message to the DU via the first RAT and in accordance with the service configuration, the service message including a destination associated with the core network service and a payload, the payload being in a format associated with the second RAT. The operations at 1420 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1420 may be performed by a service message sending manager 835 as described with reference to Figure 8 The service message sending manager 835 described.

[0237] Figure 15 Illustrates a flowchart that depicts a method 1500 for supporting techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure. The operations of method 1500 may be implemented by a network entity or its components as described herein. For example, the operations of method 1500 may be performed by a network entity as described with reference to Figures 1 to 6 And Figures 10 to 13 The network entity described. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0238] At 1505, the method may include: receiving a service message from a core network service provided by a service-based network associated with a second RAT, wherein the service-based network is configured to interact with a RAN associated with a first RAT, the service message indicating a service context for communication between the UE and the core network service associated with the second RAT. Operations at 1505 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1505 may be performed by a service message reception manager 1225 as described in reference to Figure 12 described.

[0239] At 1510, the method may include: determining a service configuration for communicating with the UE via the first RAT based at least in part on the service context associated with the second RAT. Operations at 1510 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1510 may be performed by a service configuration manager 1230 as described in reference to Figure 12 described.

[0240] At 1515, the method may include: sending a service message to the UE via the first RAT and in accordance with the service configuration, the service message including a payload in a format associated with the second RAT. Operations at 1515 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1515 may be performed by a service message transmission manager 1235 as described in reference to Figure 12 described.

[0241] Figure 16 Illustrates a flowchart that depicts a method 1600 for supporting techniques for establishing a connection to a service-based network via a RAN in accordance with one or more aspects of the present disclosure. Operations of method 1600 may be implemented by a network entity or components thereof as described herein. For example, operations of method 1600 may be performed by a network entity as described in reference to Figures 1 to 6 and Figures 10 to 13 described. In some examples, the network entity may execute an instruction set to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0242] At 1605, the method may include: receiving a service message from a core network service provided by a service-based network associated with a second RAT, wherein the service-based network is configured to interact with a RAN associated with a first RAT, the service message indicating a service context for communication between the UE and the core network service associated with the second RAT. The operations at 1605 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1605 may be performed by a service message receiving manager 1225 as described with reference to Figure 12 described.

[0243] At 1610, the method may include: receiving, via the service message, a service configuration request from the core network service, the service configuration request for converting a service context associated with the second RAT into a service configuration associated with the first RAT. The operations at 1610 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1610 may be performed by a service configuration request receiving manager 1240 as described with reference to Figure 12 described.

[0244] At 1615, the method may include: determining a service configuration for communicating with the UE via the first RAT based on a service context associated with the second RAT, wherein determining the service configuration is at least partially based on receiving the service configuration request. The operations at 1615 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1615 may be performed by a service configuration manager 1230 as described with reference to Figure 12 described.

[0245] At 1620, the method may include: sending, via the first RAT and in accordance with the service configuration, a service message to the UE, the service message including a payload in a format associated with the second RAT, wherein sending the service message is at least partially based on receiving the service configuration request. The operations at 1620 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations at 1620 may be performed by a service message sending manager 1235 as described with reference to Figure 12 described.

[0246] An overview of aspects of the present disclosure is provided below:

[0247] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving control information from a DU associated with a first RAT of a RAN, the control information indicating a core network service provided by a service-based network associated with a second RAT, the service-based network being configured to interact with the RAN; transmitting, via the first RAT and at least in part based on the control information, a service request indicating the core network service provided by the service-based network associated with the second RAT; receiving control signaling from the DU, the control signaling indicating a service configuration for communicating with the core network service provided at least in part by the service-based network based on the service request, the service configuration indicating a destination associated with the core network service; and transmitting, via the first RAT and according to the service configuration, a service message to the DU, the service message including the destination associated with the core network service and a payload in a format associated with the second RAT.

[0248] Aspect 2: The method according to aspect 1, the method further comprising: receiving, from the DU, a SIB message including the control information, wherein the SIB message is received via the first RAT.

[0249] Aspect 3: The method according to any one of aspects 1 to 2, the method further comprising: transmitting, via the first RAT, capability signaling to the DU, the capability signaling indicating the UE's ability to communicate with a core network service provided by the service-based network associated with the second RAT, wherein receiving the control information is at least in part based on the capability signaling.

[0250] Aspect 4: The method according to any one of aspects 1 to 3, the method further comprising: establishing a wireless connection with a second DU associated with the second RAT, at least in part based on operating in a dual-connectivity state, wherein the second DU is communicatively coupled to at least a second core network service provided by the service-based network; and transmitting, via the second RAT, a second service message to the second DU, the second service message including a second destination associated with the second core network service, the service message further including additional service data associated with the second core network service, the additional service data including an additional payload in a format associated with the second RAT.

[0251] Aspect 5: The method according to aspect 4, the method further comprising: receiving, from the second DU, second control signaling indicating a service context for communicating with the second core network service via the second RAT, wherein the second service message is sent according to the service context.

[0252] Aspect 6: The method according to any one of aspects 1 to 5, wherein the service request and the service message are sent via one or more communication layers associated with the first RAT, the one or more communication layers including a PHY layer, a MAC layer, an RLD layer, or any combination thereof.

[0253] Aspect 7: The method according to any one of aspects 1 to 6, wherein the service request, the service message, or both are sent to the DU for relaying to the destination associated with the core network service.

[0254] Aspect 8: The method according to any one of aspects 1 to 7, wherein the first RAT includes a 5G RAT, an NR access technology, or both, and the second RAT includes a 6G RAT.

[0255] Aspect 9: A method for wireless communication at a DU, the DU being configured to communicate with a UE via a first RAT, the method comprising: receiving, from a core network service provided by a service-based network associated with a second RAT, a service message, wherein the service-based network is configured to interact with a RAN associated with the first RAT, the service message indicating a service context for communication between the UE and the core network service associated with the second RAT; determining, at least in part based on the service context associated with the second RAT, a service configuration for communicating with the UE via the first RAT; and sending, via the first RAT and according to the service configuration, the service message to the UE, the service message including a payload in a format associated with the second RAT.

[0256] Aspect 10: The method according to aspect 9, the method further comprising: receiving, via the service message, a service configuration request from the core network service, the service configuration request for converting the service context associated with the second RAT into the service configuration associated with the first RAT, wherein determining the service configuration and sending the service message are at least in part based on receiving the service configuration request.

[0257] Aspect 11: The method according to any one of aspects 9 to 10, the method further comprising: sending a System Information Block (SIB) message to the UE via the first Radio Access Technology (RAT), the SIB message indicating the core network services provided by the service-based network; receiving, via the first RAT and at least partially based on the SIB message, a service request from the UE indicating the core network services; and sending the service request to a destination associated with the core network services via the second RAT, wherein receiving the service message is at least partially based on sending the service request.

[0258] Aspect 12: The method according to aspect 11, the method further comprising: receiving, via the first RAT, capability signaling from the UE, the capability signaling indicating the UE's capability to communicate with core network services provided by the service-based network associated with the second RAT, wherein sending the SIB message is at least partially based on the capability signaling.

[0259] Aspect 13: The method according to any one of aspects 9 to 12, wherein the service message is received via an adapter component of the DU, the adapter component being configured to interact with the service-based network and to transform the communication between the first RAT and the second RAT, the adapter component comprising a hardware component, a software component, or both.

[0260] Aspect 14: The method according to any one of aspects 9 to 13, the method further comprising: sending control signaling to the core network services, the control signaling indicating application programming interface information associated with the DU, wherein the service message is received via the second RAT according to the application programming interface information.

[0261] Aspect 15: The method according to any one of aspects 9 to 14, wherein the service message is sent via one or more communication layers associated with the first RAT, the one or more communication layers comprising a Physical (PHY) layer, a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, or any combination thereof.

[0262] Aspect 16: The method according to any one of aspects 9 to 15, wherein the first RAT comprises a 5G RAT, a New Radio (NR) access technology, or both, and the second RAT comprises a 6G RAT.

[0263] Aspect 17: An apparatus, the apparatus 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 the method according to any one of aspects 1 to 8.

[0264] Aspect 18: An apparatus, the apparatus including at least one component for performing the method according to any one of Aspects 1 to 8.

[0265] Aspect 19: A non-transitory computer-readable medium storing code including instructions executable by a processor to perform the method according to any one of Aspects 1 to 8.

[0266] Aspect 20: An apparatus, the apparatus including: 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 the method according to any one of Aspects 9 to 16.

[0267] Aspect 21: An apparatus, the apparatus including at least one component for performing the method according to any one of Aspects 9 to 16.

[0268] Aspect 22: A non-transitory computer-readable medium storing code including instructions executable by a processor to perform the method according to any one of Aspects 9 to 16.

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

[0270] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than 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.

[0271] The information and signals described herein may be represented using any of a variety of different technologies 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 magnetic particles, optical fields or optical particles, or any combination thereof.

[0272] The various illustrative blocks and components described in connection with the disclosure herein can be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor may be a microprocessor, but in the 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0273] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific 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 can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located in different places, including being distributed such that portions of the functions are implemented at different physical locations.

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

[0275] As used herein (including in the claims), the "or" used in a list of items (e.g., a list of items that is accompanied by a phrase such as "at least one of" or "one or more of") indicates an inclusive listing, such that for example, the listing 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). Additionally, as used herein, the phrase "based on" should not be construed 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 disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0276] The term "determine" encompasses a variety of actions, and thus, "determine" can include operations such as computing, calculating, processing, deriving, investigating, looking up (such as looking up in a table, database, or other data structure), and ascertaining. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determine" can include parsing, obtaining, selecting, choosing, establishing, and other such like actions.

[0277] In the drawings, like components or features may have the same reference numerals. Additionally, various components of the same type may be distinguished by adding a dash and a second numeral used to differentiate between like components after the reference numeral. If only the first reference numeral is used in the specification, the description may apply to any one of the like components having the same first reference numeral, regardless of the second reference numeral or any other subsequent reference numerals.

[0278] The description set forth herein in connection with the drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples". The detailed description includes specific details for providing an understanding of the described techniques. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a processor; a memory coupled to the processor, the memory storing instructions that can be executed by the processor to cause the apparatus to: receive control information from a distributed unit associated with a first radio access technology of a radio access network (RAN), the control information indicating a core network service provided by a service-based network associated with a second radio access technology, the service-based network being configured to interact with the RAN; send a service request via the first radio access technology and at least partially based on the control information, the service request indicating the core network service provided by the service-based network associated with the second radio access technology; receive control signaling from the distributed unit, the control signaling indicating a service configuration for communicating with the core network service provided at least partially based on the service request by the service-based network, the service configuration indicating a destination associated with the core network service; and send a service message to the distributed unit via the first radio access technology and according to the service configuration, the service message including the destination and a payload associated with the core network service, the payload being in a format associated with the second radio access technology.

2. The apparatus according to claim 1, wherein the instructions can be further executed by the processor to cause the apparatus to: receive a system information block message including the control information from the distributed unit, wherein the system information block message is received via the first radio access technology.

3. The apparatus according to claim 1, wherein the instructions can be further executed by the processor to cause the apparatus to: send capability signaling to the distributed unit via the first radio access technology, the capability signaling indicating the UE's ability to communicate with the core network service provided by the service-based network associated with the second radio access technology, wherein receiving the control information is at least partially based on the capability signaling.

4. The apparatus according to claim 1, wherein the instructions can be further executed by the processor to cause the apparatus to: establish a wireless connection with a second distributed unit associated with the second radio access technology at least partially based on operating in a dual-connectivity state, wherein the second distributed unit can be communicatively coupled to at least a second core network service provided by the service-based network; and send a second service message to the second distributed unit via the second radio access technology, the second service message including a second destination associated with the second core network service, the service message further including additional service data associated with the second core network service, the additional service data including an additional payload in the format associated with the second radio access technology.

5. The apparatus according to claim 4, wherein the instructions are further executable by the processor to cause the apparatus to: Receive second control signaling from the second distributed unit, the second control signaling indicating a service context for communicating with the second core network service via the second radio access technology, wherein the second service message is sent according to the service context.

6. The apparatus according to claim 1, wherein the service request and the service message are sent via one or more communication layers associated with the first radio access technology, the one or more communication layers including a physical layer, a media access control layer, a radio link control layer, or any combination thereof.

7. The apparatus according to claim 1, wherein the service request, the service message, or both are sent to the distributed unit for relaying to the destination associated with the core network service.

8. The apparatus according to claim 1, wherein the first radio access technology includes a fifth-generation (5G) radio access technology, a new radio (NR) access technology, or both, and wherein the second radio access technology includes a sixth-generation (6G) radio access technology.

9. An apparatus for wireless communication at a distributed unit, the distributed unit being configured to communicate with a user equipment (UE) via a first radio access technology, the apparatus comprising: A processor; A memory coupled to the processor, the memory storing instructions that are executable by the processor to cause the apparatus to: Receive a service message from a core network service provided by a service-based network associated with a second radio access technology, wherein the service-based network is configured to interact with a radio access network (RAN) associated with the first radio access technology, the service message indicating a service context for communication between the UE and the core network service associated with the second radio access technology; Determine a service configuration for communicating with the UE via the first radio access technology at least in part based on the service context associated with the second radio access technology; And Send the service message to the UE via the first radio access technology and according to the service configuration, the service message including a payload in a format associated with the second radio access technology.

10. The apparatus according to claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: Receive a service configuration request from the core network service via the service message, the service configuration request for converting the service context associated with the second radio access technology into the service configuration associated with the first radio access technology, wherein determining the service configuration and sending the service message are at least in part based on receiving the service configuration request.

11. The apparatus according to claim 9, wherein the instructions are further executable by the processor to cause the apparatus to: Transmit a system information block message to the UE via the first radio access technology, the system information block message indicating the core network service provided by the service-based network; Receive, via the first radio access technology and at least in part based on the system information block message, a service request indicating the core network service from the UE; And Transmit the service request to a destination associated with the core network service via the second radio access technology, wherein receiving the service message is at least in part based on transmitting the service request.

12. The apparatus according to claim 11, wherein the instructions can be further executed by the processor to cause the apparatus to: Receive, via the first radio access technology, capability signaling from the UE, the capability signaling indicating the UE's ability to communicate with a core network service provided by a service-based network associated with the second radio access technology, wherein transmitting the system information block message is at least in part based on the capability signaling.

13. The apparatus according to claim 9, wherein the service message is received via an adapter component of the distributed unit, the adapter component being configured to interact with the service-based network and to translate communication between the first radio access technology and the second radio access technology, wherein the adapter component comprises a hardware component, a software component, or both.

14. The apparatus according to claim 9, wherein the instructions can be further executed by the processor to cause the apparatus to: Send control signaling to the core network service, the control signaling indicating application programming interface information associated with the distributed unit, wherein the service message is received via the second radio access technology according to the application programming interface information.

15. The apparatus according to claim 9, wherein the service message is transmitted via one or more communication layers associated with the first radio access technology, the one or more communication layers including a physical layer, a media access control layer, a radio link control layer, or any combination thereof.

16. The apparatus according to claim 9, wherein the first radio access technology comprises a fifth generation (5G) radio access technology, a new radio (NR) access technology, or both, and wherein the second radio access technology comprises a sixth generation (6G) radio access technology.

17. A method for wireless communication at a user equipment (UE), the method comprising: Receive control information from a distributed unit associated with a first radio access technology of a radio access network (RAN), the control information indicating a core network service provided by a service-based network associated with a second radio access technology, the service-based network being configured to interact with the RAN; Transmit, via the first radio access technology and at least in part based on the control information, a service request indicating the core network service provided by the service-based network associated with the second radio access technology; Receiving control signaling from the distributed unit, the control signaling indicating a service configuration for communicating with a core network service provided by the service-based network at least partially based on the service request, the service configuration indicating a destination associated with the core network service; And Sending a service message to the distributed unit via the first radio access technology and according to the service configuration, the service message including the destination and a payload associated with the core network service, the payload being in a format associated with the second radio access technology.

18. The method according to claim 17, the method further comprising: Receiving a system information block message including the control information from the distributed unit, wherein the system information block message is received via the first radio access technology.

19. The method according to claim 17, the method further comprising: Sending capability signaling to the distributed unit via the first radio access technology, the capability signaling indicating the UE's ability to communicate with a core network service provided by the service-based network associated with the second radio access technology, wherein receiving the control information is at least partially based on the capability signaling.

20. The method according to claim 17, the method further comprising: Establishing a wireless connection with a second distributed unit associated with the second radio access technology at least partially based on operating in a dual-connectivity state, wherein the second distributed unit is communicatively coupled to at least a second core network service provided by the service-based network; And Sending a second service message to the second distributed unit via the second radio access technology, the second service message including a second destination associated with the second core network service, the service message further including additional service data associated with the second core network service, the additional service data including an additional payload in the format associated with the second radio access technology.

21. The method according to claim 20, the method further comprising: Receiving second control signaling from the second distributed unit, the second control signaling indicating a service context for communicating with the second core network service via the second radio access technology, wherein the second service message is sent according to the service context.

22. The method according to claim 17, wherein the service request and the service message are sent via one or more communication layers associated with the first radio access technology, the one or more communication layers including a physical layer, a media access control layer, a radio link control layer, or any combination thereof.

23. The method according to claim 17, wherein the service request, the service message, or both are sent to the distributed unit for relaying to the destination associated with the core network service.

24. The method according to claim 17, wherein the first radio access technology includes fifth-generation (5G) radio access technology, new radio (NR) access technology, or both, and wherein the second radio access technology includes sixth-generation (6G) radio access technology.

25. A method for wireless communication at a distributed unit configured to communicate with a user equipment (UE) via a first radio access technology, the method comprising: Receiving a service message from a core network service provided by a service-based network associated with a second radio access technology, wherein the service-based network is configured to interact with a radio access network (RAN) associated with the first radio access technology, the service message indicating a service context for communication between the UE and the core network service associated with the second radio access technology; Determining a service configuration for communicating with the UE via the first radio access technology at least in part based on the service context associated with the second radio access technology; And Sending the service message to the UE via the first radio access technology and according to the service configuration, the service message including a payload in a format associated with the second radio access technology.

26. The method according to claim 25, the method further comprising: Receiving, via the service message, a service configuration request from the core network service for converting the service context associated with the second radio access technology into the service configuration associated with the first radio access technology, wherein determining the service configuration and sending the service message are at least in part based on receiving the service configuration request.

27. The method according to claim 25, the method further comprising: Sending a system information block message to the UE via the first radio access technology, the system information block message indicating the core network service provided by the service-based network; Receiving, via the first radio access technology and at least in part based on the system information block message, a service request from the UE indicating the core network service; And Sending the service request to a destination associated with the core network service via the second radio access technology, wherein receiving the service message is at least in part based on sending the service request.

28. The method according to claim 27, the method further comprising: Receiving, via the first radio access technology, capability signaling from the UE, the capability signaling indicating the UE's ability to communicate with a core network service provided by a service-based network associated with the second radio access technology, wherein sending the system information block message is at least in part based on the capability signaling.

29. The method according to claim 25, wherein the service message is received via an adapter component of the distributed unit, wherein the adapter component is configured to interact with the service-based network and to transform the communication between the first radio access technology and the second radio access technology, and wherein the adapter component comprises a hardware component, a software component, or both.

30. The method according to claim 25, the method further comprising: sending control signaling to the core network service, the control signaling indicating application programming interface information associated with the distributed unit, wherein the service message is received via the second radio access technology according to the application programming interface information.

Images