Establishing connections to legacy first generation wireless networks via fully service-based networks

Abstract

Methods, systems, and devices for wireless communication are described. Techniques described herein provide for establishing a connection to a legacy generation wireless network via a fully service-based wireless network. The fully service-based wireless network may provide core network services associated with a central unit of the legacy generation wireless network. A distributed unit (DU) of the fully service-based wireless network may indicate the provided core network service to a user equipment (UE). The UE may receive a service context for communicating with the core network service, and the UE may send a service message to the core network service via the DU according to the service context, which may be forwarded to a legacy generation core network.

Description

[0001] Cross-reference

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 061,934, filed Dec. 5, 2022, by GRIOT et al., entitled “ESTABLISHING CONNECTIVITY TO LEGACY GENERATION WIRELESS NETWORK VIA A FULLY SERVICE BASED NETWORK,” which is assigned to the assignee of the present application and is hereby expressly incorporated by reference in its entirety. Technical Field

[0003] The following relates to wireless communication, including establishing connectivity to a legacy generation wireless network via a fully service based network. 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 the like. 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 interface with a service-based network that provides or supplies various core network services. Each respective core network service may be hosted or provided by a different operator or entity and may be associated with a different set of parameters for communicating with the respective core network service. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for enabling connections to legacy first-generation wireless networks via service-based networks. For example, the described technology provides a service-based network, such as a sixth-generation (6G) communication system, to provide core network services associated with a central unit (CU) of a legacy first-generation such as a fifth-generation (5G) radio access technology (RAT). The core network services associated with the 5G CU (5G CU services) may act as the 5G CU or may hand over with the 5G CU. The 6G radio access network (RAN) may provide a 6G enhanced distributed unit (eDU), which may indicate to a user equipment (UE) that the 6G RAN provides 5G CU services. The 5G CU services may indicate to the UE via the eDU a service context that the UE may use to communicate with the 5G core network via the 5G CU services. The UE may send a message to the 5G CU services via the eDU, and the message is forwarded to the 5G core network. The 5G CU services may forward a message from the 5G core network to the UE.

[0007] A method for wireless communication at a UE is described. The method may include: receiving, via a first RAT, control information from a distributed unit (DU), the control information indicating a core network service provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT; sending, via the first RAT and based on the control information, a service request to the DU indicating the core network service associated with the CU of the second RAT; receiving, based on the service request, via the first RAT from the DU a service context for communicating with the core network service according to the first RAT, the service context indicating a destination associated with the core network service; and sending, according to the service context, via the first RAT to the DU a service message, the service message including the destination and a payload in a format associated with the second RAT.

[0008] A device for wireless communication at a UE is described. The device may include a processor and a memory coupled to the processor, the memory storing instructions executable by the processor to cause the device to perform the following operations: receive control information from a DU via a first RAT, the control information indicating a core network service provided by a service-based network of the first RAT and configured to hand over to a core network service associated with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT; send, via the first RAT and based on the control information, a service request indicating the core network service associated with the CU of the second RAT to the DU; receive, based on the service request via the first RAT from the DU, a service context for communicating with the core network service according to the first RAT, the service context indicating a destination associated with the core network service; and send, according to the service context via the first RAT to the DU, a service message including the destination and a payload in a format associated with the second RAT.

[0009] Another device for wireless communication at a UE is described. The device may include: means for receiving control information from a DU via a first RAT, the control information indicating a core network service provided by a service-based network of the first RAT and configured to hand over to a core network service associated with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT; means for sending, via the first RAT and based on the control information, a service request indicating the core network service associated with the CU of the second RAT to the DU; means for receiving, based on the service request via the first RAT from the DU, a service context for communicating with the core network service according to the first RAT, the service context indicating a destination associated with the core network service; and means for sending, according to the service context via the first RAT to the DU, a service message including the destination and a payload in a format associated with the second RAT.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive control information from a DU via a first RAT, the control information indicating a core network service provided by a service-based network of the first RAT and configured to handover with a core network service associated with a RAN associated with the DU, wherein the DU is associated with the first RAT and wherein the core network service is associated with a CU of a second RAT; send, via the first RAT and based on the control information, a service request to the DU indicating the core network service associated with the CU of the second RAT; receive, based on the service request, via the first RAT from the DU a service context for communicating with the core network service according to the first RAT, the service context indicating a destination associated with the core network service; and send, according to the service context, via the first RAT to the DU a service message including the destination and a payload in a format associated with the second RAT.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for: receiving the control information via a system information block sent by the DU.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: sending a query for a service via the second RAT to the DU, wherein receiving the control information may be in response to the query.

[0013] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the service message may include operations, features, components, or instructions for: sending the service message including the payload, the payload including a non-access stratum (NAS) message associated with a core network destination of the second RAT.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the service message may include operations, features, components, or instructions for: sending the service message including the payload, the payload including a radio resource control message associated with the CU of the second RAT.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the service message may include operations, features, components, or instructions for: sending the service message including a packet data unit in a format associated with the second RAT.

[0016] 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 the DU according to the service context, a second service message that includes a second payload in a format associated with the second RAT.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for communicating with a network entity associated with the second RAT and the CU.

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

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the destination associated with the core network service may be a network address.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the service context indicates an identifier associated with the core network destination of the second RAT.

[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the core network service may be associated with an application programming interface.

[0022] A method for wireless communication at a DU is described. The method may include: conveying a service request received from a UE via a first RAT to a core network service provided by a service-based network of the first RAT and configured to interface with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT; conveying a service context received from the core network service to the UE via the first RAT, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service; and conveying a service message received from the UE via the first RAT to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0023] Describes an apparatus for wireless communication at a DU. The apparatus may include a processor and a memory coupled to the processor, the memory storing instructions executable by the processor to cause the apparatus to perform the following operations: convey a service request received from a UE via a first RAT to a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT; convey a service context received from the core network service to the UE via the first RAT, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service; and convey a service message received from the UE via the first RAT to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0024] Describes another apparatus for wireless communication at a DU. The apparatus may include: means for conveying a service request received from a UE via a first RAT to a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT; means for conveying a service context received from the core network service to the UE via the first RAT, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service; and means for conveying a service message received from the UE via the first RAT to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0025] A non-transitory computer-readable medium storing code for wireless communication at a DU is described. The code may include instructions executable by a processor to perform the following operations: convey a service request received from a UE via a first RAT to a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the DU is associated with the first RAT, and where the core network service is associated with a CU of a second RAT; convey a service context received from the core network service to the UE via the first RAT, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service; and convey a service message received from the UE via the first RAT to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: transmitting, via the first RAT, a system information block indicating that the core network service is available from a service-based network of the first RAT, where the service request may be a response to the transmission of the system information block.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving, via the first RAT, a query from the UE for a service via the second RAT; and in response to the query and via the first RAT, sending control information to the UE indicating that the core network service is available from a service-based network of the first RAT, where the service request may be in response to the transmission of the control information.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: conveying, according to the service context and via the first RAT, a second service message received from the core network service to the UE, the service message including a second payload in a format associated with the second RAT.

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

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the destination associated with the core network service may be a network address.

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the service context indicates an identifier associated with a core network destination of a second RAT.

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

[0033] A method for wireless communication at a core network service is described. The method may include: receiving, via a DU associated with a first RAT, a service request from a UE indicating the core network service, the core network service being provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, wherein the core network service is associated with a CU of a second RAT; sending, based on the service request according to the first RAT via the DU, a service context for communicating between the UE and the core network service to the UE, the service context indicating a destination associated with the core network service; and receiving, according to the service context via the DU, a service message from the UE, the service message including the destination and a payload in a format associated with the second RAT.

[0034] An apparatus for wireless communication at a core network service is described. The apparatus may include a processor and a memory coupled to the processor, the memory storing instructions executable by the processor to cause the apparatus to: receive, via a DU associated with a first RAT, a service request from a UE indicating the core network service, the core network service being provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, wherein the core network service is associated with a CU of a second RAT; send, based on the service request according to the first RAT via the DU, a service context for communicating between the UE and the core network service to the UE, the service context indicating a destination associated with the core network service; and receive, according to the service context via the DU, a service message from the UE, the service message including the destination and a payload in a format associated with the second RAT.

[0035] Describes another apparatus for wireless communication at a core network service. The apparatus may include: components for receiving, via a DU associated with a first RAT, a service request from a UE indicating the core network service, the core network service being provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, wherein the core network service is associated with a CU of a second RAT; components for sending, based on the service request, via the DU according to the first RAT, a service context for communicating between the UE and the core network service to the UE, the service context indicating a destination associated with the core network service; and components for receiving, according to the service context, via the DU, a service message from the UE, the service message including the destination and a payload in a format associated with the second RAT.

[0036] Describes a non-transitory computer-readable medium storing code for wireless communication at a core network service. The code may include instructions executable by a processor to perform the following operations: receive, via a DU associated with a first RAT, a service request from a UE indicating the core network service, the core network service being provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, wherein the core network service is associated with a CU of a second RAT; send, based on the service request, via the DU according to the first RAT, a service context for communicating between the UE and the core network service to the UE, the service context indicating a destination associated with the core network service; and receive, according to the service context, via the DU, a service message from the UE, the service message including the destination and a payload in a format associated with the second RAT.

[0037] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for: extracting a NAS message associated with the second RAT from the payload and sending the NAS message to a core network destination of the second RAT, wherein the payload indicates the core network destination.

[0038] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the NAS message may include operations, features, components, or instructions for sending the NAS message to an access and mobility management function via an N2 interface.

[0039] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the NAS message may include operations, features, components, or instructions for sending the NAS message to a user plane function via an N3 interface.

[0040] 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 core network entity of the second RAT, a second NAS message addressed to the UE and communicating, via the DU, a second service message to the UE according to the service context, the second service message including a second payload that includes the second NAS message.

[0041] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: extracting, from the payload, a radio resource control message associated with the second RAT and sending the radio resource control message to the CU.

[0042] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the service message may include operations, features, components, or instructions for: receiving the service message including the payload, the payload including a packet data unit in a format associated with the second RAT.

[0043] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the destination associated with the core network service may be a network address.

[0044] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the service context indicates an identifier associated with a core network destination of the second RAT.

[0045] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the core network service may be associated with an application programming interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 Examples of wireless communication systems that support establishing a connection to a legacy first-generation wireless network via a service-based network are illustrated in accordance with one or more aspects of the present disclosure.

[0047] Figure 2 Examples of wireless communication systems that support establishing a connection to a legacy first-generation wireless network via a service-based network are illustrated in accordance with one or more aspects of the present disclosure.

[0048] Figure 3 Examples of network architectures that support establishing a connection to a legacy first-generation wireless network via a service-based network are illustrated in accordance with one or more aspects of the present disclosure.

[0049] Figure 4Illustrates an example of a wireless communication system that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0050] Figure 5 Illustrates an example of a wireless communication system that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0051] Figure 6 Illustrates an example of a wireless communication system that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0052] Figure 7 Illustrates an example of a process flow that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0053] Figure 8 and Figure 9 Illustrates a block diagram of a device that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0054] Figure 10 Illustrates a block diagram of a communication manager that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0055] Figure 11 Illustrates a diagram of a system that includes a device that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0056] Figure 12 and Figure 13 Illustrates a block diagram of a device that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0057] Figure 14 Illustrates a block diagram of a communication manager that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0058] Figure 15 Illustrates a diagram of a system that includes a device that supports establishing a connection to a legacy first-generation wireless network via a service-only based network, according to one or more aspects of the present disclosure.

[0059] Figures 16 to 18A flowchart is illustrated that shows a method for supporting the establishment of a connection to a legacy first-generation wireless network via a service-based network only, in accordance with one or more aspects of the present disclosure. Detailed Description

[0060] 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), a base station / network entity, 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.

[0061] 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 entity) interfaces 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") to different core network services or groups thereof on an as-needed 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 corresponding UE.

[0062] In some wireless systems, the RAN may interface with a service-based network that provides various core network services and may relay communications between the UE and the corresponding core network services. Specifically, the UE may subscribe to various core network services provided by the service-based network. However, each corresponding core network service may be hosted or provided by a different operator or entity and may be associated with a different set of parameters for communicating with the corresponding core network service. In other words, the communication parameters used to communicate with one core network service may not be used to communicate with another core network service.

[0063] Service-based wireless communication systems (e.g., service-based radio access technology (RAT)) may have higher throughput and increased spectrum compared to legacy wireless communication systems (e.g., legacy RAT). As operators transition to service-based systems, some operators may not offer a full set of services (e.g., 6G services), but may offer a 6G RAN to take advantage of the higher throughput and increased spectrum provided by 6G. Thus, an operator may desire to provide access to a 5G core network via the 6G RAN.

[0064] A service-based communication system may provide a central unit (CU) service that acts as or hands over with a legacy CU (e.g., a 5G CU). A UE may communicate with a legacy core network (e.g., a 5G core network) via a service-based RAN (e.g., a 6G RAN), such as via a 6G enhanced distributed unit (eDU). The 6G eDU may indicate to the UE that the 6G RAN provides a legacy (e.g., 5G) CU service. For example, the eDU may broadcast a system information block (SIB) indicating the availability of the 5G CU service, or the UE may query the eDU regarding whether the RAN associated with the relevant service provides a legacy CU service. The legacy CU service may then indicate to the UE, via the eDU, a service context that the UE can use to communicate with the legacy core network (e.g., a 5G core network) via the legacy CU service. For example, the service context may indicate the network address of the legacy CU service and the message format for legacy messages (e.g., 5G messages) sent via a service-based protocol (e.g., a 6G protocol). Thus, the UE may send a message to the legacy CU service in a service-based protocol format, where the message includes the legacy CU service as the destination and a payload of the message including the legacy message format. The legacy CU service may accordingly extract the legacy message from the service-based message payload and forward the legacy message to a target legacy core network entity / function, such as an access and mobility management function (AMF) or a user plane function (UPF). The legacy CU service may similarly forward messages from a legacy core network function / entity to the UE.

[0065] 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, an example wireless communication system, and an example process flow. Aspects of the present disclosure are further illustrated with reference to apparatus diagrams, system diagrams, and flowcharts related to techniques for service establishment in a service-based wireless system and are described with reference to these diagrams.

[0066] Figure 1An example of a wireless communication system 100 is illustrated that supports establishing a connection to a legacy first-generation wireless network via a service-based network, 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).

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

[0068] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or stationary and mobile at different times. The UEs 115 may be devices in different forms or having 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 entities 105 as shown.

[0069] 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 the UE 115, the network entity 105, the device, the equipment, the computing system, etc. can include the disclosure of the UE 115, the network entity 105, the device, the equipment, the computing system, etc. as nodes. For example, the disclosure that the UE 115 is configured to receive information from the network entity 105 also discloses that the first node is configured to receive information from the second node.

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

[0071] In some examples, network entity 105 may communicate with a service platform 150 (e.g., a cloud platform) that provides one or more core network services (CN services), one or more RAN services, or any combination thereof (CN / RAN services 185). The CN / RAN services may be provided via 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 UE 115. The services at UE 115 may correspond to one or more CN / RAN services 185 at service platform 150. For example, a network service API 180 at service-based network 130 may interface with a corresponding DU service API 175 at DU 165, which interfaces with a corresponding API at UE 115 to provide a service connection between the one or more UE 115 services and the corresponding CN / RAN services 185.

[0072] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base station transceiver, a radio base station, an access point, a radio transceiver, a 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, network entity 105 (e.g., 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 base station 140, may include an RU 170, a DU 165, and a DU API 175 for CN / RAN services 185). RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP).

[0073] Additionally, in some examples, one or more network entities 105 may be implemented in a 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 between two or more network entities 105 (such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN))). For example, network entity 105 may include one or more of the following: a 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 co-located, 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)).

[0074] 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)) functions 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, media access control (MAC) layer) functions 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 a protocol layer can be performed by one of the CU, DU 165, or RU 170, while other functions of that 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.

[0075] 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 wired backhaul connections, thereby providing an IAB network architecture (e.g., to a service-based network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) 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). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communications with the UE 115, or may share the same antennas (e.g., of the RU 170) of the IAB node 104 for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB nodes 104, UEs 115) within a relay chain or configuration (e.g., downstream) with the access network. In such cases, one or more components of the split RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0076] 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 the UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the split RAN architecture (e.g., IAB nodes 104, DUs 165, CUs, RUs 170, RICs, SMOs).

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

[0078] 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, as well as network entity 105 and network equipment including macro eNB or gNB, small cell eNB or gNB, or relay base stations, etc., as Figure 1 shown.

[0079] The UE 115 and network entity 105 may wirelessly communicate with each other 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 spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, the carrier for the communication link 125 may include a portion (e.g., bandwidth part (BWP)) of the RF spectrum band operating according to one or more physical layer channels for a given RAT (e.g., 4G, 5G, 6G RAT). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. According to the carrier aggregation configuration, the UE 115 may be configured 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).

[0080] 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 Radio Frequency Channel Number (EARFCN)) and may be identified according to a channel raster used for discovery by UE 115. A carrier may operate in stand-alone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or the carrier may operate in non-stand-alone mode, in which case a different carrier (e.g., of the same or a different RAT) is used to anchor the connection.

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

[0082] 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 for carriers of a particular RAT (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 capable of being configured 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.

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

[0084] One or more parameter sets may be supported for a carrier, and the parameter set may include subcarrier spacing (∆f) and cyclic prefix. The 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.

[0085] The time intervals for network entity 105 or UE 115 may be expressed as multiples of a basic time unit, which may refer to a sampling period, for example. seconds, for which may represent the supported subcarrier spacing, while may represent the supported discrete Fourier transform (DFT) size. The time intervals of communication resources may be organized according to radio frames, each radio frame having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0086] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may 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 fassociated with a sampling period. The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

[0088] 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. The search space set may include a common search space set configured to transmit control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115.

[0089] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity for communicating with the 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 the network entity 105, the scope of such cells can range from a relatively small area (e.g., a structure, a subset of a structure) to a relatively large 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.

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

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

[0092] In some examples, the 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.

[0093] 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. Examples of applications of MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0094] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). 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.

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

[0096] 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 a roadside unit), or communicate with the network via vehicle-to-network (V2N) communication through one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

[0097] 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 network 190. The 5G core network 190 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The 5G core network 190 may be an evolved packet core (EPC), which may include at least one control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an AMF) and at least one user plane entity for routing packets or interconnecting to external networks (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 the mobility, authentication, and bearer management of the UE 115 served by a network entity 105 (e.g., a base station 140) associated with the 5G core network 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.

[0098] 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 in order for macrocells to provide service to UEs 115 located indoors. Compared to communications using smaller frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).

[0099] 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 a device. However, the propagation of EHF transmissions may be affected by greater attenuation and shorter range 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.

[0100] 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) RAT, or NR technologies that use 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, the operation using an unlicensed band may be based on a carrier aggregation configuration combined with a component carrier operating using a licensed band (e.g., LAA). The operation using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, D2D transmissions, and the like.

[0101] 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, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0102] 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 a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports 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.

[0103] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., the network entity 105, the UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining 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).

[0104] The network entity 105 or the UE 115 may use beam scanning techniques as part of beamforming operations. 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 sets of beamforming weights 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 later transmission or reception by the network entity 105.

[0105] Some signals (such as data signals associated with a particular 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 the signals transmitted along one or more beam directions. For example, the UE 115 may receive one or more of the signals transmitted 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.

[0106] 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 type codebook, linear combination type codebook, port selection type 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 transmissions or receptions), or for transmitting signals in a single direction (e.g., for transmitting data to a receiving device).

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

[0108] 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., message brokers decouple radio network processes from network delivery mechanisms) 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 can be independently scaled by independently increasing or decreasing the resources allocated across the various functions). Additionally, efficiency can 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.

[0109] In some implementations, the wireless communication system 100 supports signaling and other mechanisms that enable the UE 115 to establish a wireless connection with a service-based network 130 (e.g., a 6G network). Specifically, aspects of the present disclosure relate to signaling between the UE 115, a network entity 105 (e.g., DU 165), and core network services (e.g., CN / RAN services 185) in a service-based network architecture that enables the UE 115 to establish and maintain connections with different core network services (e.g., CN / RAN services 185) provided by the network. Thus, the techniques described herein may enable the UE 115 to obtain a service context for each respective core network service subscribed to by the UE 115, where the service context includes core network service-specific communication parameters for communicating with the respective core network service.

[0110] For example, the UE 115 of the wireless communication system 100 may establish a connection with the DU 165 of the network entity 105 and may receive control signaling indicating core network services provided by the network (e.g., the CN / RAN service 185), as well as the network addresses of each of the provided core network services. The UE 115 may then send (via the relay of the DU 165) a service request to the network address of the provided core network service and may receive (via the relay of the DU 165) a service context for communicating with the core network service. The UE 115 may then communicate with the core network service according to the service context (via the DU 165).

[0111] In some aspects, the UE 115 may be able to request core network services provided by the network. For example, the UE 115 may be able to query a discovery service (e.g., a core network discovery service) that is configured to provide a list of the provided core network services that can be accessed by the respective querying UE 115. The core network services indicated as available to the UE 115 may be based on the capabilities of each respective UE 115. Some core network services may include or depend on other network function services. For example, in order for the UE 115 to subscribe to / communicate with a first core network service, the UE 115 may also be required to subscribe to / communicate with a second core network service associated with the first core network service.

[0112] The techniques described herein may enable the UE 115 to establish and maintain a connection (e.g., a subscription) with core network services provided by a service-based network (e.g., within a 6G system). Specifically, the techniques described herein may enable the UE 115 to obtain a service context for each respective core network service to which the UE 115 subscribes, where the service context includes core network service-specific parameters for communicating with the respective core network service. By enabling the UE 115 to subscribe to multiple different core network services, aspects of the present disclosure may enable the UE 115 to establish connections with a variety of core network services that may be provided by different operators or entities. Thus, the techniques described herein may enable the UE 115 to subscribe to different core network services on an as-needed or as-required basis according to the respective UE 115, thereby improving customization and the overall user experience at the UE 115. Additionally, by enabling the UE 115 to subscribe to specific core network services, the techniques described herein may enable the UE 115 to avoid communicating with unwanted or unneeded core network services, thereby reducing control signaling within the network, improving resource utilization, and reducing power consumption at the UE 115.

[0113] Service-based wireless communication systems (e.g., service-based radio access technology (RAT)) may have higher throughput and increased spectrum compared to legacy wireless communication systems (e.g., legacy RAT). As operators transition to service-based systems, some operators may not offer a full set of services (e.g., 6G services), but may offer a 6G RAN to take advantage of the higher throughput and increased spectrum provided by 6G. Thus, an operator may desire to provide access to a 5G core network via the 6G RAN.

[0114] A service-based communication system may provide a CU service that acts as a legacy CU or interfaces with a legacy CU (e.g., a 5G CU). The UE 115 may communicate with a legacy core network (e.g., the 5G core network 190) via a service-based RAN (e.g., a 6G RAN), such as via a 6G eDU. The 6G eDU may indicate to the UE 115 that the 6G RAN provides a legacy CU (e.g., a 5G CU) service. For example, the eDU may broadcast an SIB indicating the availability of the legacy CU service, or the UE 115 may query the eDU regarding whether the RAN based on the associated service provides a legacy CU service. The legacy CU service may then indicate to the UE 115, via the eDU, a service context that the UE 115 may use to communicate with the legacy core network (e.g., the 5G core network) via the legacy CU service. For example, the service context may indicate a network address of the legacy CU service and a message format for legacy messages (e.g., 5G messages) sent via a service-based protocol (e.g., a 6G protocol). Thus, the UE 115 may send a message to the legacy CU service in a service-based protocol format via the eDU, where the message includes the legacy CU service as a destination and a payload of the message that includes the legacy message format. The legacy CU service may accordingly extract the legacy message from the service-based message payload and forward the legacy message to a target legacy core network entity / function, such as an AMF or a UPF. The legacy CU service may similarly forward a message from a legacy core network function / entity to the UE 115.

[0115] Figure 2 An example of a wireless communication system 200 that supports establishing a connection to a legacy generation wireless network via a fully service-based network is illustrated, in accordance with one or more aspects of the present disclosure. 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 with reference to Figure 1 the example architecture.

[0116] The wireless communication system 200 may include one or more UEs 115 (e.g., UE 115-a), one or more network entities (e.g., network entity 105-a), and a service-based network 205. In some aspects, the service-based network 205 may be configured to communicate with or handover to the 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 specific implementations, the service-based network 205 may include or be associated with a cloud platform, where the corresponding core network services 215 are hosted at corresponding network addresses in the cloud platform.

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

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

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

[0120] The different services, functionality, 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.

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

[0122] In some aspects, a network entity 105-a (e.g., eDU) may facilitate traffic routing (e.g., service data unit routing) from UE 115-a to core network services 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, 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 to 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 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).

[0123] Figure 2 The service-based wireless communication system 200 (e.g., 6G network) illustrated in FIG. 1 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 that includes many “layers” of different devices that perform functions of the network). The more hierarchical structure may result in processing and other functions being performed at multiple devices (e.g., network entities 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 services provided to UE 115 and other devices may be difficult to customize within such systems.

[0124] In contrast, Figure 2The service-based wireless communication system 200 illustrated herein exhibits a more flattened horizontal architecture that enables the corresponding functions of the wireless communication system to be distributed across different components of the system (e.g., core network services 215). For example, such functions and protocols 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 subset of the capabilities and functionality of a conventional wireless communication system. In other words, compared to a component that provides all the included network functions and protocols (e.g., modularization of network services / functions across multiple core network services 215), a service-based architecture can enable the functions and protocols to be divided into self-contained services (e.g., core network services 215).

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

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

[0127] In some embodiments, as will be described in further detail herein, the wireless communication system 200 can support signaling that enables a UE 115-a to establish and maintain communication with a core network service 215 of a service-based network 205 (such as a 6G network). Specifically, aspects of the present disclosure relate to signaling that enables a UE 115-a to subscribe to a core network service 215 on an as-needed or as-required basis of the UE 115-a. For example, as described herein, one of the core network services 215 can be a legacy CU service (e.g., a 5G CU service) through which the UE can communicate with a legacy core network (e.g., a 5G core network) via the RAN 210 and the service-based network 205.

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

[0129] Each network entity (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)) in the network entity 105 of the network architecture 300 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 the associated processor (e.g., controller) that provides instructions to the interfaces of the network entity 105 may be configured to communicate with one or more of the other network entities 105 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 that may include a receiver, a transmitter, or a transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or transmit signals to one or more of the other network entities 105 on the wireless transmission medium, or both.

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

[0131] 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 handing over to a 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 for these services. In some examples, when handing over to 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 3rd 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.

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

[0133] 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, the DU 165-a, the 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 directly communicate 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.

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

[0135] 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 at 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 of performance and employ an AI model or an ML model to perform corrective actions through the generation of reconfigurations at the SMO 335 (e.g., via O1) or via RAN management policies such as A1 policies.

[0136] In some implementations, as will be described in further detail herein, the network architecture 300 can support signaling that enables the UE 115 to establish and maintain communication with core network services of a service-based network such as a 6G network. Specifically, aspects of the present disclosure relate to signaling between the UE 115, the DU 165, and the core network services that enables the UE 115 to subscribe to core network services on an as-needed or requested basis for each respective UE 115 on a per-point-of-choice basis.

[0137] Figure 4 An example of a wireless communication system 400 that supports establishing a connection to a legacy first-generation wireless network via a fully service-based network is illustrated in accordance with one or more aspects of the present disclosure. 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.

[0138] The wireless communication system 400 can include a UE 115-c, a network entity 105-b, and a 5G core network 190-b. In some examples, the UE 115-c can be an example of the UE 115 as described herein, the network entity 105-b can be an example of the network entity 105 as described herein, and the 5G core network 190-b can be an example of the 5G core network 190 as described herein. In some examples, the network entity 105-b can include an example of an O-RAN entity that includes multiple components such as one or more DUs, as Figure 3 shown and described. In this regard, Figure 4The network entity 105-b illustrated in [document] may additionally or alternatively be referred to as a DU or eDU 105-b. The eDU 105-b may be associated with a first RAT (e.g., sending and receiving messages according to the first RAT) (e.g., 6G protocol). The 5G core network 190-b is associated with a second RAT (e.g., 5G RAT).

[0139] The wireless communication system 400 may include a 5G CU service 405 as a core network service. The 5G CU service 405 may be provided by a service-based network of a first RAT (e.g., 6G RAT), such as Figure 2 the service-based network 205 illustrated in [document]. The service-based network including the 5G CU service 405 may communicate or handover with the 6G RAN 410 of the wireless communication system 400, where the 6G RAN 410 includes one or more network entities (e.g., eDU 105-b). In some examples, the 5G CU service 405 may be one of several core network services associated with or hosted by a cloud platform, where the 5G CU service 405 may be hosted at a destination in the cloud platform. In some examples, the destination associated with the 5G CU service 405 may be a network address in the cloud platform.

[0140] The UE 115-c may communicate with the eDU 105-b using the communication link 220-a, which may be an example of the communication link 220 described herein. The eDU 105-b of the 6G RAN 410 may be configured to communicate (e.g., handover with) the 5G CU service 405 of the 6G service-based network via the communication link 225-a, which may be an example of the communication link 225 described herein. In some examples, the 5G CU service 405 may include 5G CU service APIs configured to facilitate wireless communication with the eDU 105-b and the UE 115-c, such as Figure 1 the network service API 180 illustrated in [document].

[0141] In some examples, the eDU 105-b may facilitate traffic routing (e.g., service data unit routing) from the UE 115-c to the 5G CU service 405, and vice versa. In other words, the eDU 105-b may be configured to relay communications from the UE 115-c to the 5G CU service 405, such as control information and service messages, and vice versa. The eDU 105-b may facilitate traffic routing between the corresponding devices directly, via other network entities 105, via a proxy, or any combination thereof.

[0142] As operators transition from 5G to 6G, some operators may not offer a complete set of 6G services but may offer 6G RAN 410 to take advantage of the higher throughput and increased spectrum provided by the 6G RAT. Thus, an operator may wish to provide access to the 5G core network 190-b via 6G RAN 410. The 6G communication system may provide 5G CU services 405 that act as a 5G CU, such that the UE 115-c can communicate with the 5G core network 190-b via the eDU 105-b over the 6G RAN 410. The control plane procedures for the 5G CU services 405 may include a 5G CU service discovery procedure, a 5G CU service configuration procedure, an RRC procedure on the 5G CU services 405, and a NAS procedure on the 5G CU services 405.

[0143] In an example 5G CU service discovery procedure, the eDU 105-b may indicate to the UE 115-c that the 6G RAN 410 provides 5G CU services 405. For example, the eDU 105-b may broadcast an SIB indicating the availability of the 5G CU services 405, and the UE 115-c may discover the 5G CU services 405. In some examples, the UE 115-c may ask an eDU 105-b or a discovery service not in the eDU 105-b about whether the associated 6G RAN 410 provides 5G CU services 405, and the eDU 105-b or the discovery service may respond to the UE 115-c, indicating that the 6G RAN 410 provides 5G CU services 405.

[0144] In some examples, after UE 115-c discovers 5G CU service 405, UE 115-c may choose to use 5G CU service 405 and may complete the 5G CU service configuration process. For example, UE 115-c may send a service request for 5G CU service 405 to eDU 105-b via communication link 220-a to establish a connection with eDU 105-b. After receiving the service request from UE 115-c, eDU 105-b may convey the service request to 5G CU service 405 via communication link 225-a. In response to the service request, a service configuration for communication involving 5G CU service 405 and UE 115-c may be established. For example, 5G CU service 405 may convey a service context for communication between UE 115-c and 5G CU service 405 to eDU 105-b via communication link 225-a. eDU 105-b may convey the service context to UE 115-c via communication link 220-a. For example, the service context may indicate a destination associated with 5G CU service 405 and a message format for 5G messages to be sent via a 6G protocol. The service context may indicate a RAN configuration for communication with eDU 105-b. In another example, the service context may indicate information or an ID for eDU 105-b to route to 5G CU service 405. In some examples, the service context may indicate identifiers of 5G core network functions (such as AMF 440 and UPF 445) that UE 115-c may use and that 5G CU service 405 may use to route to 5G core network 190-b.

[0145] In some examples, UE 115-c may send a service message to 5G CU service 405 in a 6G protocol format via eDU 105-b. The service message may include a destination or network address of 5G CU service 405 and a payload of a 5G message including a 5G message format. 5G CU service 405 may extract the 5G message from the payload of the service message and may forward the 5G message to one of the functions / entities in 5G core network 190-b, such as AMF 440 or UPF 445, via communication link 120-d.

[0146] Transmissions between the UE 115-c and the 5G core network 190-b may involve NAS procedures. For example, the UE 115-c may send a service message, where the NAS message of the 5G RAT is the payload of the service message. Additionally, the payload of the service message may indicate the 5G core network 190-b destination of the NAS message, such as the AMF 440 and the UPF 445. The 5G CU service 405 may extract the NAS message from the payload, and the 5G CU service 405 may send the NAS message to the 5G core network 190-b via the communication link 120-d. For example, the 5G CU service 405 may perform 5G CU operations for the N2 procedure as an operation towards the AMF 440 (e.g., terminating the N2 interface 430), and / or the 5G CU service 405 may perform 5G CU operations for the N3 procedure as an operation towards the UPF 445 (e.g., terminating the N3 interface 435). In some examples, the UE 115-c may also communicate with the 5G CU in the 5G network via the 5G CU service 405. In this example, the UE 115-c may use the 5G CU service 405 to communicate with the 5G core network 190-b and to communicate with the 5G gNB-CU or 5G CU. The communication from the UE 115-c via the 5G CU service 405 to the 5G core network 190-b may use NAS messages, and the communication from the UE 115-c via the 5G CU service 405 to the 5G CU may use RRC messages.

[0147] In some examples, such as Figure 5 shown, the 5G CU service may communicate with a 5G CU, and the 5G CU may communicate with the 5G core network. For the 5G CU service 405 acting as a 5G CU, such as Figure 4 shown, the 5G RRC may not be used, and the service protocol between the 5G CU service 405, the eDU 105-b, and the UE 115-c may be a 6G protocol that replaces the 5G RRC. In some examples, the transmission of the NAS message between the UE 115-c and the 5G core network 190-b may involve reconfiguration of the 5G CU service 405 of the UE 115-c for the transmission used for NAS, local configuration between the UE 115-c and the eDU 105-b, and / or configuration between the eDU 105-b and the 5G CU service 405. In some examples, the 5G CU service 405 may be connected to a 5G CU in the 5G network, and the UE 115-c may send an RRC message to the 5G CU via the 5G CU service 405. This may be considered an example of a dual connection with the UE 115-c using the 5G CU as the primary CU and the 5G CU service 405 acting as the secondary CU.

[0148] The 5G CU service 405 may receive a 5G message from a 5G core network function / entity (such as AMF 440 or UPF 445) of the 5G core network 190-b, may prepare another service message having the 5G message as a payload, and may send the service message to the UE 115-c via the eDU 105-b. The UE 115-c may receive the service message and may extract the 5G message from the payload of the service message. In some examples, the 5G CU service 405 may receive a NAS message addressed to the UE 115-c from the 5G core network 190-b. The 5G CU service 405-c may communicate the NAS message in the payload of the service message to the UE 115-c via the eDU 105-b according to the service context. The UE 115-c may receive the service message and may extract the NAS message from the payload.

[0149] In some examples, once the UE 115-c establishes a service context with the 5G CU service 405, the UE 115-c may perform 5G control plane procedures (such as registration) and packet data unit (PDU) session establishment using 6G transport and service signaling provided with the 5G CU service 405 toward the 5G core network 190-b. The UE 115-c may also send data toward the 5G CU service 405 with the intent that the data may be received by the UPF 445 (e.g., a 5G PDU session user plane anchor).

[0150] In some examples, the 5G CU service 405 may convert signaling from the 5G core network 190-b intended for RAN configuration and affecting the eDU 105-b into a request for the eDU 105-b configuration API. The 5G CU service 405 may forward 5G signaling received from the 5G core network 190-b destined for the UE 115-c to the eDU 105-b for the eDU 105-b to forward to the UE 115-c. The 5GCU service 405 may forward the signaling received from the UE 115-c to the AMF 440 based on the payload type, such as a NAS message.

[0151] Figure 5An example of a wireless communication system 500 that supports establishing a connection to a legacy generation wireless network via a fully service-based network in accordance with one or more aspects of the present disclosure is illustrated. In some examples, aspects of the wireless communication system 500 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, or any combination thereof. The wireless communication system 500 may include a UE 115-d, a network entity 105-c, a 5G core network 190-c, and a 5G CU service 405-a, which may be examples of the UE 115, the network entity 105, the 5G core network 190, and the 5G CU service 405 described herein. In some examples, the network entity 105-c may include an example of an O-RAN entity that includes multiple components, such as one or more DUs, such as Figure 3 As shown and described. In this regard, Figure 5 The network entity 105-c illustrated in the example may additionally or alternatively be referred to as a DU or eDU 105-c. The wireless communication system 500 may include a 5G CU 310-a. In some examples, the 5G CU 310-a may be an example of a 5G CU 310 as described herein. The eDU 105-b may be associated with a first RAT (e.g., a 6G protocol) (e.g., sending and receiving messages according to the first RAT). The 5G core network 190-b is associated with a second RAT (e.g., a 5G RAT).

[0152] 5G CU service 405-a may be provided by a 6G service-based network (such as Figure 2 405-a). The 6G service-based network including the 5G CU service 405-a may communicate or be interfacing with the 6G RAN 410-a of the wireless communication system 500, wherein the 6G RAN 410-a includes one or more network entities (e.g., eDU 105-c). In some examples, the 5G CU service 405-a may be one of several core network services associated with or hosted by a cloud platform, wherein the 5G CU service 405-a may be hosted at a network address in the cloud platform. In some examples, the 5G CU service 405-a may be co-located with the eDU 105-c or may be co-located with the 5G CU 310-a.

[0153] The UE 115-d may communicate with the eDU 105-c using a communication link 220-b, which may be an example of a communication link 220 as described herein. The eDU 105-c of the 6G RAN 410-a may be configured to communicate with (e.g., interface with) a 5G CU service 405-a of a 6G service-based network via a communication link 225-b, which may be an example of a communication link 225 as described herein. In some examples, the 5G CU service 405-a may include a 5G CU service API configured to facilitate wireless communications with the eDU 105-c and the UE 115-d, such as Figure 1 The web service API 180 is illustrated in FIG.

[0154] In some examples, the eDU 105-c may facilitate traffic routing (e.g., service data unit routing) from the UE 115-d to the 5G CU service 405-a, and vice versa. In other words, the eDU 105-c may be configured to relay communications, such as control information and service messages, from the UE 115-d to the 5G CU service 405-a, and vice versa. The eDU 105-c may facilitate traffic routing between the respective devices directly, via other network entities 105, via a proxy, or any combination thereof.

[0155] As operators transition from 5G to 6G, some operators may not provide a full set of 6G services, but may provide 6G RAN 410-a to take advantage of the higher throughput and increased spectrum provided by 6G. Therefore, operators may wish to provide access to the 5G core network 190-c via 6G RAN410-a. The 6G communication system may provide a 5G CU service 405-a that is interfacing with the 5G CU 310-a, so that the UE 115-d can communicate with the 5G core network 190-c via the 6G RAN 410-a via the eDU 105-c. The control plane process for the 5G CU service 405-a may include a 5G CU service discovery process, a 5G CU service configuration process, and an RRC process on the 5G CU service 405-a.

[0156] During the example 5G CU service discovery process, eDU 105-c may indicate to UE 115-d that 6G RAN 410-a provides 5G CU service 405-a. For example, eDU 105-c may broadcast an SIB indicating the availability of 5G CU service 405-a, and UE 115-d may discover 5G CU service 405-a. In some examples, UE 115-d may ask an eDU 105-c or a discovery service not in eDU 105-c about whether the associated 6G RAN 410-a provides 5G CU service 405-a, and eDU 105-c or the discovery service may respond to UE 115-d, indicating that 6G RAN 410 provides 5G CU service 405.

[0157] In some examples, after UE 115-d discovers 5G CU service 405-a, UE 115-d may choose to use 5G CU service 405-a and may complete the 5G CU service configuration process. For example, UE 115-d may send a service request for 5G CU service 405-a to eDU105-c via communication link 220-b to establish a connection with eDU 105-c. After receiving the service request from UE 115-d, eDU 105-c may convey the service request to 5G CU service 405-a via communication link 225-b. In response to the service request, a service configuration for communication involving 5G CU service 405-a and UE 115-d may be established. For example, 5G CU service 405-a may convey a service context for communication between UE 115-d and 5G CU service 405-a to eDU 105-c via communication link 225-b. eDU 105-c may convey the service context to UE 115-d via communication link 220-b. For example, the service context may indicate a destination associated with 5G CU service 405-a and a message format for 5G messages to be sent via the 6G protocol. In another example, the service context may indicate information or an ID for eDU 105-c to route to 5G CU service 405-a. In some examples, the service context may indicate identifiers of 5G core network functions (such as AMF 440-a and UPF 445-b) that UE 115-d may use and 5G CU service 405-a may use to route to the 5G core network 190-c. In some examples, the service context may indicate an identifier that UE 115-d may use and 5G CU service 405-a may use to route to 5G CU310-a.

[0158] In some examples, UE 115-d may send a service message to 5G CU service 405-a in a 6G protocol format via eDU 105-c. The service message may include the destination or network address of 5G CU service 405-a and the payload of a 5G message including a 5G message format. 5G CU service 405-a may extract the 5G message from the payload of the service message, and 5G CU service 405-a may forward the 5G message to 5G CU 310-a via communication link 315-a (e.g., F1 interface). 5G CU 310-a may forward the 5G message to one of the functions / entities in 5G core network 190-c (such as AMF 440-a or UPF 445-a) via communication link 120-f (such as via N2 interface 430-a and N3 interface 435-a). Thus, 5G CU service 405-a may route the communication between 5G CU 310-a and UE 115-d.

[0159] The transmission between UE 115-d and 5G CU 310-a may involve an RRC procedure. For example, UE 115-d may send a service message, where an RRC message of 5G RAT is the payload of the service message. 5G CU service 405-a may extract the RRC message from the payload, and 5G CU service 405-a may send the RRC message for an F1 procedure to 5G CU 310-a via the F1-U / C interface. Additionally, 5G CU service 405-a may receive an RRC message from 5C CU 310-a, and 5C CU service 405-a may send a service message with the payload of the RRC message to UE 115-d. In some examples, the transmission of the RRC message between UE 115-d and 5G CU 310-a may involve the reconfiguration of 5G CU service 405-a for UE 115-d for the transmission of RRC, the local configuration between UE 115-d and eDU 105-c, and / or the configuration between eDU 105-c and 5G CU service 405-a. In some examples, UE 115-d may also communicate with 5G core network 190-c via 5G CU service 405-a. In this example, UE 115-d may use 5G CU service 405-a to communicate with 5G CU 310-a and to communicate with 5G core network 190-c. The communication from UE 115-c via 5G CU service 405-a to 5G core network 190-c may use NAS messages, and the communication to 5G CU 310-a via 5G CU service 405-a may use RRC messages.

[0160] The 5G CU service 405-a may receive 5G messages from 5G core network functions / entities (such as the AMF 440-a or the UPF 445-a) of the 5G core network 190-b via the 5G CU 310-a. The 5G CU service 405-a may prepare another service message having the 5G message as a payload and may send the service message to the UE 115-d via the eDU 105-c. The UE 115-d may receive the service message and may extract the 5G message from the payload of the service message. The 5G CU service 405-a may forward signaling received from the UE 115-d to the CU 310-a according to the payload type, such as an RRC message. In some examples, the payload of the service message may be a PDU in 5G format.

[0161] Figure 6 An example of a wireless communication system 600 that supports establishing a connection to a legacy first-generation wireless network via a service-based network only is illustrated in accordance with one or more aspects of the present disclosure. In some examples, aspects of the wireless communication system 600 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, the wireless communication system 500, or any combination thereof. The wireless communication system 600 may include a UE 115-e, a network entity 105-d, a network entity 105-e, a 5G core network 190-d, a 5G CU service 405-b, and a 5G CU 310-b, which may be examples of the UE 115, the network entity 105, the 5G core network 190, the 5G CU service 405, and the 5G CU 310 described herein. In some examples, the network entity 105-d may include an example of an O-RAN entity that includes multiple components, such as one or more DUs, as Figure 3 shown and described. In this regard, Figure 6 the network entity 105-d illustrated in

[0162] The wireless communication system 600 may include a 6G RAN 410-b and a 5G RAN 610. In some examples, the UE 115-e may use the 5G RAN 610 as the primary network, and the UE 115-e may use the 6G RAN 410-b as an auxiliary or backup network. For example, the UE 115-e may communicate with the network entity 105-e using the communication link 125-b, which may be an example of the communication link 125 described. The network entity 105-e of the 5G RAN 610 may be configured to communicate with (e.g., handover with) the 5G CU 310-b of the 5G RAN 610 via the communication link 120-c, which may be an example of the communication link 120 described herein. For example, the communication link 120-c may be configured to facilitate two-way communication between the network entity 105-e and the 5G CU 310-b. The 5G CU 310-b may communicate with the 5G core network 190-d via the communication link 120-d. The UE 115-e may convey 5G format messages to the network entity 105-e of the 5G RAN 610.

[0163] The 6G RAN 410-b may have a similar architecture and operation to Figure 5 the 6G RAN 410-a. For example, the 5G CU service 405-b may be provided by a 6G service-based network (e.g., Figure 2 the service-based network 205 illustrated in). The 6G service-based network including the 5G CU service 405-c may communicate with or handover to the 6G RAN 410-b of the wireless communication system 600, where the 6G RAN 410-b includes one or more network entities (e.g., eDU 105-d). In some examples, the 5G CU service 405-b may be one of several core network services associated with or hosted by a cloud platform, where the 5G CU service 405-b may be hosted at a network address in the cloud platform. In some examples, the 5G CU service 405-b may be collocated with the eDU 105-d or may be collocated with the 5G CU 310-b.

[0164] The UE 115-e may communicate with the eDU 105-d using the communication link 220-c, which may be an example of the communication link 220 described herein. The eDU 105-d of the 6G RAN may be configured to communicate with (e.g., handover with) the 5G CU service 405-b of the 6G service-based network via the communication link 225-c, which may be an example of the communication link 225 described herein. In some examples, the 5G CU service 405-b may include 5G CU service APIs configured to facilitate wireless communication with the eDU 105-d and the UE 115-e, such asFigure 1 The network service API 180 illustrated in

[0165] In some examples, the eDU 105-d may facilitate traffic routing (e.g., service data unit routing) from the UE 115-e to the 5G CU service 405-b, and vice versa. In other words, the eDU 105-d may be configured to relay communications such as control information and service messages from the UE 115-e to the 5G CU service 405-c, and vice versa. The eDU 105-d may facilitate traffic routing between the corresponding devices directly, via other network entities 105, via a proxy, or any combination thereof.

[0166] The 5G CU service 405-b may interface with the 5G CU 310-b such that the UE 115-e may communicate with the 5G core network 190-d via the 6G RAN 410-b via the 6G eDU 105-d. In some examples, the UE 115-e may send a service message to the 5G CU service 405-b in a 6G protocol format via the eDU 105-d. The service message may include the destination or network address of the 5G CU service 405-b and the payload of a 5G message including a 5G message format. The 5G CU service 405-b may extract the 5G message from the payload of the service message and may forward the 5G message to the 5G CU 310-b via a communication link 315-b (e.g., F1 interface). The 5G CU 310-b may forward the 5G message to one of the functions / entities of the 5G core network 190-d (such as the AMF 440-b or the UPF 445-b) via a communication link 120-d (such as via the N2 interface 430-b and the N3 interface 435-b). With the 5G CU service 405-b of the 6G RAN 410-b, the UE 115-e may operate in a dual-connectivity mode. The UE 115-e may communicate with the 5G core network 190-d using the 5G CU service 405-b of the 6G RAN 410-b, and the UE 115-e may communicate with the 5G core network 190-d using the 5G RAN 610.

[0167] Figure 7 An example of a process flow 700 is illustrated that supports establishing a connection to a legacy generation wireless network via a service-based network only, in accordance with one or more aspects of the present disclosure. In some examples, aspects of the process flow 700 may implement aspects of or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the network architecture 300, the wireless communication system 400, the wireless communication system 500, or the wireless communication system 600, or any combination thereof.

[0168] The procedure flow 700 may include the UE 115-f, an eDU 105-f associated with a first RAT (e.g., 6G RAT), a 5GCU service 405-c, a 5G CU 310-c associated with a second RAT (e.g., 5G RAT), and a 5G core network 190-e, which may be examples of the UE 115, eDU 105, 5G CU service 405, 5G CU 310, and 5G core network 190 described herein. In the following description of the procedure flow 700, the operations between the UE 115-f, eDU 105-f, 5G CU service 405-c, 5G CU 310-c, and 5G core network 190-d may be sent in an order different from the illustrated example order, or the operations performed by the UE 115-f, eDU 105-f, 5G CU service 405-c, 5G CU 310-c, and 5G core network 190-d may be performed in a different order or at different times. Some operations may also be omitted from the procedure flow 700, and other operations may be added to the procedure flow 700.

[0169] At 710, the UE 115-f may receive, via the first RAT, control information from the eDU 105-f indicating that the 5G CU service 405-c is provided by a 6G service-based network of the first RAT. The 5G CU service 405-c may be configured to handover with a 6G RAN associated with the eDU 105-f. The eDU 105-f may be associated with the first RAT, and in some examples, the 5G CU service is associated with a 5G CU 310-c of the second RAT.

[0170] At 715, the UE 115-f may send, via the first RAT, a service request indicating the 5G CU service 405-c to the eDU 105-f, and the eDU 105-f may convey the service request received from the UE 115-f to the 5G CU service 405-c.

[0171] At 720, the 5G CU service 405-c may send, according to the first RAT via the eDU 105-f, a service context for communicating between the UE 115-f and the 5G CU service 405-c to the UE 115-f. The service context may indicate a destination associated with the 5G CU service 405-c.

[0172] At 725, the UE 115-f may send a service message to the eDU 105-f according to the service context via the first RAT. The eDU 105-f conveys the service message to the 5G CU service 405-c. The service message may include the destination and a payload in a format associated with the second RAT.

[0173] At 730, the 5G CU service 405-c may extract the payload of the service message. In some examples, the payload of the service message may include a NAS message associated with a second RAT. Additionally, the payload of the service message may indicate the 5G core network 190-e destination of the NAS message, such as the AMF and the UPF. At 735, the 5G CU service 405-c may send the NAS message to the 5G core network 190-e. In some examples, the 5G CU service 405-c may send the NAS message to the AMF via the N2 interface. In some examples, the 5G CU service 405-c may send the NAS message to the UPF via the N3 interface.

[0174] In some examples, at 740, the 5G CU service 405-c may receive a second NAS message addressed to the UE 115-f from the 5G core network 190-e. At 745, the 5G CU service 405-c may convey the second NAS message in the payload of the second service message to the UE 115-f via the eDU 105-f according to the service context. The UE 115-f may receive the second service message and may extract the second NAS message from the payload.

[0175] In some examples, the payload of the service message may include an RRC message associated with a second RAT. As discussed above at 730, the 5G CU service 405-c may extract the RRC message from the payload of the service message. At 750, the 5G CU service 405-c may send the RRC message to the 5G CU 310-c. In some examples, the payload of the service message may include PDUs in a format associated with a second RAT.

[0176] In some examples, the UE 115-f may receive control information via a system information block sent by the eDU 105-f. In some examples, the UE 115-f may send a query for a service via a second RAT to the eDU 105-f, and the received control information may be responsive to the query.

[0177] In some examples, the UE 115-f may communicate with a network entity associated with a second RAT and the 5G CU 310-c (e.g., the UE 115-f may operate in a dual-connectivity mode). In some examples, the service context may include a RAN configuration for communicating with the eDU 105-f as part of the 5G CU service 405-c. In some examples, the service context may indicate an identifier associated with the 5G core network 190-e destination of the second RAT. The destination of the service context may be a network address. The 5G CU service 405-c may be associated with an application programming interface.

[0178] Figure 8 FIG. 800 is a block diagram of a device 805 that illustrates support for establishing a connection to a legacy first-generation wireless network via a service-based network, in accordance with one or more aspects of the present disclosure. The device 805 may be an example of aspects of a UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0179] The receiver 810 may provide components for receiving information associated with various information channels (e.g., control channels, data channels, information channels associated with establishing a connection to a legacy first-generation wireless network via a service-based network) such as packets, user data, control information, or any combination thereof. The information may be delivered to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.

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

[0181] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or their various components may be examples of components for performing various aspects of establishing a connection to a legacy first-generation wireless network via a service-based network as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or components may support methods for performing one or more of the functions described herein.

[0182] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof 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 may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0183] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor, DSP, CPU, ASIC, FPGA, 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.

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

[0185] According to an example as disclosed herein, a communication manager 820 may support wireless communication at a UE. For example, the communication manager 820 may be configured to or otherwise support components for receiving control information from a DU via a first RAT, the control information indicating a core network service provided by a service-based network of the first RAT and configured to hand over to a core network service associated with a RAN associated with the DU, where the DU is associated with the first RAT, and where the core network service is associated with a CU of a second RAT. The communication manager 820 may be configured to or otherwise support components for sending, via the first RAT and based on the control information, a service request indicating the core network service associated with the CU of the second RAT to the DU. The communication manager 820 may be configured to or otherwise support components for receiving, based on the service request, via the first RAT from the DU a service context for communicating with the core network service according to the first RAT, the service context indicating a destination associated with the core network service. The communication manager 820 may be configured to or otherwise support components for sending, according to the service context, via the first RAT to the DU a service message including the destination and a payload in a format associated with the second RAT.

[0186] By including or configuring a communication manager 820 according to an example as described herein, a device 805 (e.g., a processor controlling or otherwise coupled to a receiver 810, a transmitter 815, a communication manager 820, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0187] Figure 9 Block diagram 900 illustrates a device 905 supporting establishing a connection to a legacy first-generation wireless network via a service-based network only, according to one or more aspects of the present disclosure. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0188] The receiver 910 may provide components for receiving information associated with various information channels (e.g., control channels, data channels, information channels associated with establishing a connection to a legacy first-generation wireless network via a service-based network only) such as packets, user data, control information, or any combination thereof. The information may be delivered to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.

[0189] The transmitter 915 can provide components for transmitting signals generated by other components of the device 905. For example, the transmitter 915 can 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 establishing a connection to a legacy first-generation wireless network via a service-based network). In some examples, the transmitter 915 can be co-located with the receiver 910 in a transceiver module. The transmitter 915 can utilize a single antenna or a set of multiple antennas.

[0190] The device 905 or its various components can be examples of components for performing various aspects of establishing a connection to a legacy first-generation wireless network via a service-based network as described herein. For example, the communication manager 920 can include a control information reception manager 925, a service request manager 930, a service context manager 935, a service message manager 940, or any combination thereof. The communication manager 920 can be an example of aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communication manager 920 can receive information from the receiver 910, convey information to the transmitter 915, or integrate in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0191] According to an example as disclosed herein, a communication manager 920 may support wireless communication at a UE. A control information receiving manager 925 may be configured to or otherwise support components for receiving control information from a DU via a first RAT, the control information indicating core network services provided by a service-based network of the first RAT and configured to hand over to a core network service associated with a RAN associated with the DU, where the DU is associated with the first RAT, and where the core network service is associated with a CU of a second RAT. A service request manager 930 may be configured to or otherwise support components for sending, via the first RAT and based on the control information, a service request indicating a core network service associated with the CU of the second RAT to the DU. A service context manager 935 may be configured to or otherwise support components for receiving, based on the service request, via the first RAT from the DU a service context for communicating with the core network service according to the first RAT, the service context indicating a destination associated with the core network service. A service message manager 940 may be configured to or otherwise support components for sending, according to the service context, via the first RAT to the DU a service message, the service message including the destination and a payload in a format associated with the second RAT.

[0192] Figure 10 Block diagram 1000 illustrates a communication manager 1020 that supports establishing a connection to a legacy first-generation wireless network via a fully service-based network, according to one or more aspects of the present disclosure. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both, as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of establishing a connection to a legacy first-generation wireless network via a fully service-based network, as described herein. For example, the communication manager 1020 may include a control information receiving manager 1025, a service request manager 1030, a service context manager 1035, a service message manager 1040, an inquiry sending manager 1045, a second RAT communication manager 1050, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0193] According to an example disclosed herein, the communication manager 1020 may support wireless communication at a UE. The control information receiving manager 1025 may be configured to or otherwise support components for receiving control information from a DU via a first RAT, the control information indicating a core network service provided by a service-based network of the first RAT and configured to hand over to a core network service associated with a RAN associated with the DU, where the DU is associated with the first RAT, and where the core network service is associated with a CU of a second RAT. The service request manager 1030 may be configured to or otherwise support components for sending, via the first RAT and based on the control information, a service request indicating the core network service associated with the CU of the second RAT to the DU. The service context manager 1035 may be configured to or otherwise support components for receiving, based on the service request, via the first RAT from the DU a service context for communicating with the core network service according to the first RAT, the service context indicating a destination associated with the core network service. The service message manager 1040 may be configured to or otherwise support components for sending, according to the service context, via the first RAT to the DU a service message that includes the destination and a payload in a format associated with the second RAT.

[0194] In some examples, to support receiving control information, the control information receiving manager 1025 may be configured to or otherwise support components for receiving control information via a system information block sent by the DU.

[0195] In some examples, the query sending manager 1045 may be configured to or otherwise support components for sending a query for a service via a second RAT to the DU, where the control information is received in response to the query.

[0196] In some examples, to support sending a service message, the service message manager 1040 may be configured to or otherwise support components for sending a service message that includes a payload, the payload including a NAS message associated with a core network destination of a second RAT.

[0197] In some examples, to support sending a service message, the service message manager 1040 may be configured to or otherwise support components for sending a service message that includes a payload, the payload including an RRC message associated with a CU of a second RAT.

[0198] In some examples, to support sending a service message, the service message manager 1040 may be configured to or otherwise support components for sending a service message that includes a PDU in a format associated with a second RAT.

[0199] In some examples, the service message manager 1040 may be configured to or otherwise support components for receiving a second service message from the DU according to the service context, the second service message including a second payload in a format associated with the second RAT.

[0200] In some examples, the second RAT communication manager 1050 may be configured to or otherwise support components for communicating with a network entity associated with the second RAT and the CU.

[0201] In some examples, the service context includes a RAN configuration for communicating with the DU as part of the core network service.

[0202] In some examples, the destination associated with the core network service is a network address.

[0203] In some examples, the service context indicates an identifier associated with the core network destination of the second RAT.

[0204] In some examples, the core network service is associated with an application programming interface.

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

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

[0207] In some cases, the device 1105 may include a single antenna 1125. However, in some other cases, the device 1105 may have more than one antenna 1125, and the more than one antenna may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1115 may communicate bidirectionally via one or more antennas 1125, wired or wireless links as described herein. For example, the transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1115 may also include a modem that is configured to: modulate a packet; provide the modulated packet to one or more antennas 1125 for transmission; and demodulate a packet received from one or more antennas 1125. The transceiver 1115, or the transceiver 1115 and one or more antennas 1125, may be examples of the transmitter 815, transmitter 915, receiver 810, receiver 910, or any combination thereof or components thereof as described herein.

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

[0209] Processor 1140 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, processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting the establishment of a connection to a legacy first-generation wireless network via a service-based network only). For example, device 1105 or components of device 1105 may include processor 1140 and memory 1130 coupled to or coupled with processor 1140, and processor 1140 and memory 1130 are configured to perform the various functions described herein.

[0210] According to an example as disclosed herein, communication manager 1120 may support wireless communication at a UE. For example, communication manager 1120 may be configured to or otherwise support components for receiving control information from a DU via a first RAT, the control information indicating a core network service provided by a service-based network of the first RAT and configured to hand over to a core network service associated with a RAN associated with the DU, where the DU is associated with the first RAT, and where the core network service is associated with a CU of a second RAT. Communication manager 1120 may be configured to or otherwise support components for sending, via the first RAT and based on the control information, a service request indicating the core network service associated with the CU of the second RAT to the DU. Communication manager 1120 may be configured to or otherwise support components for receiving, based on the service request, via the first RAT from the DU a service context for communicating with the core network service according to the first RAT, the service context indicating a destination associated with the core network service. Communication manager 1120 may be configured to or otherwise support components for sending, according to the service context, via the first RAT to the DU a service message including the destination and a payload in a format associated with the second RAT.

[0211] By including or configuring communication manager 1120 according to an example as described herein, device 1105 may support techniques for improving communication reliability, reducing latency, more efficiently utilizing communication resources, and improving coordination between devices.

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

[0213] Figure 12 Block diagram 1200 illustrates a device 1205 that supports establishing a connection to a legacy first-generation wireless network via a service-based network, in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of aspects of the network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0214] The receiver 1210 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 1205. In some examples, the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

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

[0216] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof or various components thereof may be examples of means for performing various aspects of establishing a connection to a legacy generation wireless network via a fully service-based network as described herein. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

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

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

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

[0220] According to examples disclosed herein, the communication manager 1220 may support wireless communication at the DU. For example, the communication manager 1220 may be configured or otherwise support components for conveying a service request received from a UE via a first RAT to a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT. The communication manager 1220 may be configured or otherwise support components for conveying a service context received from the core network service to the UE via the first RAT, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service. The communication manager 1220 may be configured or otherwise support components for conveying a service message received from the UE via the first RAT to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0221] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communication at a core network service. For example, the communication manager 1220 may be configured to or otherwise support components for receiving, from a UE via a DU associated with a first RAT, a service request indicating a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the core network service is associated with a CU of a second RAT. The communication manager 1220 may be configured to or otherwise support components for sending, based on the service request, via the DU according to the first RAT to the UE a service context for communicating between the UE and the core network service, the service context indicating a destination associated with the core network service. The communication manager 1220 may be configured to or otherwise support components for receiving, via the DU according to the service context, from the UE a service message including the destination and a payload in a format associated with the second RAT.

[0222] By including or configuring a communication manager 1220 according to examples as described herein, a device 1205 (e.g., a processor controlling or otherwise coupled to a receiver 1210, a transmitter 1215, a communication manager 1220, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0223] Figure 13 Block diagram 1300 illustrates a device 1305 supporting establishing a connection to a legacy first-generation wireless network via a service-based network only, according to one or more aspects of the present disclosure. The device 1305 may be an example of aspects of a device 1205 or a network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0224] The receiver 1310 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 1305. In some examples, the receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0225] Transmitter 1315 may provide a component for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of device 1305. For example, transmitter 1315 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, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0226] Device 1305 or its various components may be examples of components for performing various aspects of establishing a connection to a legacy first-generation wireless network via a service-based network as described herein. For example, communication manager 1320 may include a service request manager 1325, a service context manager 1330, a service message manager 1335, or any combination thereof. Communication manager 1320 may be an example of aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 may receive information from receiver 1310, convey information to transmitter 1315, or integrate in combination with receiver 1310, transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0227] According to an example as disclosed herein, the communication manager 1320 may support wireless communication at the DU. The service request manager 1325 may be configured to or otherwise support components for communicating a service request received from a UE via a first RAT to a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the DU is associated with the first RAT, and where the core network service is associated with a CU of a second RAT. The service context manager 1330 may be configured to or otherwise support components for communicating a service context received from the core network service to the UE via the first RAT, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service. The service message manager 1335 may be configured to or otherwise support components for communicating a service message received from the UE via the first RAT to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0228] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1320 may support wireless communication at the core network service. The service request manager 1325 may be configured to or otherwise support components for receiving, from a UE via a DU associated with a first RAT, a service request indicating a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the core network service is associated with a CU of a second RAT. The service context manager 1330 may be configured to or otherwise support components for sending, based on the service request and according to the first RAT via the DU, a service context for communicating between the UE and the core network service to the UE, the service context indicating a destination associated with the core network service. The service message manager 1335 may be configured to or otherwise support components for receiving a service message from the UE via the DU according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0229] Figure 14FIG. 1400 is a block diagram of a communication manager 1420 that illustrates support for establishing a connection to a legacy first-generation wireless network via a service-based network in accordance with one or more aspects of the present disclosure. The communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of components for performing various aspects of establishing a connection to a legacy first-generation wireless network via a service-based network as described herein. For example, the communication manager 1420 may include a service request manager 1425, a service context manager 1430, a service message manager 1435, a system information block manager 1440, a query reception manager 1445, a control information transmission manager 1450, a payload extraction manager 1455, a NAS message manager 1460, a radio resource control message manager 1465, or any combination thereof. Each of these components may communicate directly or indirectly with one another (e.g., via one or more buses), which communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualized components associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0230] In accordance with an example as disclosed herein, the communication manager 1420 may support wireless communication at a DU. The service request manager 1425 may be configured to or otherwise support components for communicating a service request received from a UE via a first RAT to a core network service provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, where the DU is associated with the first RAT, and where the core network service is associated with a CU of a second RAT. The service context manager 1430 may be configured to or otherwise support components for communicating a service context received from the core network service to the UE via the first RAT, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service. The service message manager 1435 may be configured to or otherwise support components for communicating a service message received from the UE via the first RAT to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0231] In some examples, the system information block manager 1440 may be configured to or otherwise support components for sending, via the first RAT, a system information block indicating that the core network service is provided by a service-based network of the first RAT, where the service request is a response to the sending of the system information block.

[0232] In some examples, the query reception manager 1445 may be configured to or otherwise support components for receiving, from a UE via a first RAT, a query for a service via a second RAT. In some examples, the control information sending manager 1450 may be configured to or otherwise support components for sending, in response to the query and via the first RAT, control information indicating that the core network service is provided by a service-based network of the first RAT to the UE, where the service request is in response to the sending of the control information.

[0233] In some examples, the service message manager 1435 may be configured to or otherwise support components for communicating, via the first RAT and according to the service context, a second service message received from the core network service to the UE, the service message including a second payload in a format associated with the second RAT.

[0234] In some examples, the service context includes a RAN configuration for communicating with the DU as part of the core network service.

[0235] In some examples, the destination associated with the core network service is a network address.

[0236] In some examples, the service context indicates an identifier associated with the core network destination of the second RAT.

[0237] In some examples, the core network service is associated with an application programming interface.

[0238] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1420 may support wireless communication at a core network service. In some examples, the service request manager 1425 may be configured to or otherwise support components for receiving, from a UE via a DU associated with a first RAT, a service request indicating a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the core network service is associated with a CU of a second RAT. In some examples, the service context manager 1430 may be configured to or otherwise support components for sending, based on the service request, via the DU to the UE, a service context for communicating between the UE and the core network service, the service context indicating a destination associated with the core network service. In some examples, the service message manager 1435 may be configured to or otherwise support components for receiving, according to the service context, via the DU from the UE, a service message that includes the destination and a payload in a format associated with the second RAT.

[0239] In some examples, the payload extraction manager 1455 may be configured to or otherwise support components for extracting, from the payload, a NAS message associated with a second RAT. In some examples, the NAS message manager 1460 may be configured to or otherwise support components for sending the NAS message to a core network destination of the second RAT, where the payload indicates the core network destination.

[0240] In some examples, to support sending the NAS message, the NAS message manager 1460 may be configured to or otherwise support components for sending the NAS via an N2 interface to an AMF.

[0241] In some examples, to support sending the NAS message, the NAS message manager 1460 may be configured to or otherwise support components for sending the NAS message via an N3 interface to a UPF.

[0242] In some examples, the NAS message manager 1460 may be configured to or otherwise support components for receiving, from a core network entity of the second RAT, a second NAS message addressed to the UE. In some examples, the service message manager 1435 may be configured to or otherwise support components for communicating, according to the service context, via the DU to the UE, a second service message that includes a second payload that includes the second NAS message.

[0243] In some examples, the payload extraction manager 1455 may be configured to or otherwise support components for extracting RRC messages associated with a second RAT from a payload. In some examples, the radio resource control message manager 1465 may be configured to or otherwise support components for sending RRC messages to the CU.

[0244] In some examples, to support receiving service messages, the service message manager 1435 may be configured to or otherwise support components for receiving service messages, the service messages including a payload that includes PDUs in a format associated with a second RAT.

[0245] In some examples, the destination associated with the core network service is a network address.

[0246] In some examples, the service context indicates an identifier associated with a core network destination of a second RAT.

[0247] In some examples, the core network service is associated with an application programming interface.

[0248] Figure 15 Illustrated is a diagram of a system 1500 including a device 1505 that supports establishing a connection to a legacy first-generation wireless network via a service-based network only, in accordance with one or more aspects of the present disclosure. The device 1505 may be an example of the device 1205, the device 1305, or the network entity 105 as described herein, or include components thereof. The device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, the communication including communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. The device 1505 may include components that support outputting and obtaining communication, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, code 1530, and a processor 1535. These components may be electronically communicatively coupled via one or more buses (e.g., bus 1540) or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically).

[0249] The transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1510 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1515, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1515, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1510 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and one or more antennas 1515, or the transceiver 1510 and one or more antennas 1515 and one or more processors or memory components (e.g., processor 1535 or memory 1525 or both) may be included in a chip or chip assembly installed in the device 1505. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 315 , fronthaul communication link 168 ).

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

[0251] The processor 1535 may include intelligent hardware devices (such as 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 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1535. The processor 1535 may be configured to execute computer-readable instructions stored in a memory (such as the memory 1525) so that the device 1505 performs various functions (such as functions or tasks that support establishing a connection to a legacy first-generation wireless network via a service-based network). For example, the device 1505 or components of the device 1505 may include the processor 1535 and a memory 1525 coupled to the processor 1535, and the processor 1535 and the memory 1525 are configured to perform the various functions described herein. The processor 1535 may be an example of a cloud computing platform (such as one or more physical nodes and supporting software (such as an operating system, a virtual machine, or a container instance)), and the cloud computing platform may host functions for executing the functions of the device 1505 (such as by executing the code 1530). The processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1505 (such as within the memory 1525). In some specific implementations, the processor 1535 may be a component of a processing system. A processing system generally may refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be delivered to other systems or components of, for example, the device 1505). For example, the processing system of the device 1505 may refer to a system that includes various other components or sub-components of the device 1505 (such as the processor 1535, or the transceiver 1510, or the communication manager 1520, or a combination of other components or components of the device 1505). The processing system of the device 1505 may interface with other components of the device 1505 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or a modem of the device 1505 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 a chip or a modem and a transmitter so that the device 1505 may transmit information output from the chip or the modem.Additionally or alternatively, in some embodiments, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver such that the device 1505 may obtain information or signal input and the information may be delivered to the processing system. Those 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.

[0252] In some examples, the bus 1540 may support communication within a protocol layer of a protocol stack (e.g., within the protocol layer). In some examples, the bus 1540 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of the device 1505 or between different components of the device 1505 that may be co-located or located at different locations (e.g., where the device 1505 may refer to a system in which one or more of the communication manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 may be located in one component or divided between different components).

[0253] In some examples, the communication manager 1520 may manage (e.g., via one or more wired or wireless backhaul links) aspects of communication with a core network. For example, the communication manager 1520 may manage the delivery of data communication for client devices such as one or more UEs 115. In some examples, the communication manager 1520 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 the UEs 115. In some examples, the communication manager 1520 may support the X2 interface within an LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0254] According to an example as disclosed herein, the communication manager 1520 may support wireless communication at the DU. For example, the communication manager 1520 may be configured to or otherwise support components for communicating a service request received from a UE via a first RAT to a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the DU is associated with the first RAT, and where the core network service is associated with a CU of a second RAT. The communication manager 1520 may be configured to or otherwise support components for communicating a service context received from the core network service to the UE via the first RAT, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service. The communication manager 1520 may be configured to or otherwise support components for communicating a service message received from the UE via the first RAT to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0255] Additionally or alternatively, according to an example as disclosed herein, the communication manager 1520 may support wireless communication at the core network service. For example, the communication manager 1520 may be configured to or otherwise support components for receiving from a UE via a DU associated with a first RAT a service request indicating a core network service provided by a service-based network of the first RAT and configured to handover with a RAN associated with the DU, where the core network service is associated with a CU of a second RAT. The communication manager 1520 may be configured to or otherwise support components for sending via the DU to the UE a service context for communicating between the UE and the core network service according to the first RAT based on the service request, the service context indicating a destination associated with the core network service. The communication manager 1520 may be configured to or otherwise support components for receiving from the UE via the DU a service message according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0256] By including or configuring a communication manager 1520 according to an example as described herein, the device 1505 may support techniques for improving communication reliability, more efficiently utilizing communication resources, and improving coordination between devices.

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

[0258] Figure 16 A flowchart illustrating a method 1600 for supporting establishing a connection to a legacy first-generation wireless network via a service-based network in accordance with one or more aspects of the present disclosure is shown. Operations of method 1600 may be implemented by a UE or its components as described herein. For example, operations of method 1600 may be performed by a UE 115 as described with reference to Figures 1 to 11 herein. In some examples, the UE may execute an instruction set 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.

[0259] At 1605, the method may include receiving control information from a DU via a first RAT, the control information indicating a core network service provided by a service-based network of the first RAT and configured to hand over to a core network associated with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT. The operation of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1605 may be performed by a control information reception manager 1025 as described with reference to Figure 10 herein.

[0260] At 1610, the method may include sending, via the first RAT and based on the control information, a service request to the DU indicating the core network service associated with the CU of the second RAT. The operation of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operation of 1610 may be performed by a service request manager 1030 as described with reference to Figure 10 herein.

[0261] At 1615, the method may include receiving, via the first RAT based on the service request, a service context for communicating with the core network service according to the first RAT from the DU, the service context indicating a destination associated with the core network service. The operation at 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operation at 1615 may be performed by a service context manager 1035 as described with reference to Figure 10 and described in

[0262] At 1620, the method may include sending, via the first RAT according to the service context, a service message to the DU, the service message including the destination and a payload in a format associated with the second RAT. The operation at 1620 may be performed according to examples disclosed herein. In some examples, aspects of the operation at 1620 may be performed by a service message manager 1040 as described with reference to Figure 10 and described in

[0263] Figure 17 FIG. illustrates a flowchart of a method 1700 that shows support for establishing a connection to a legacy generation wireless network via a service-based network according to one or more aspects of the present disclosure. The operations of method 1700 may be implemented by a network entity or its components as described herein. For example, the operations of method 1700 may be performed by a network entity as described with reference to Figures 1 to 7 and Figures 12 to 15 and described in

[0264] At 1705, the method may include communicating a service request received from a UE via a first RAT to a core network service provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT. The operation at 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operation at 1705 may be performed by a service request manager 1425 as described with reference to Figure 14 and described in

[0265] At 1710, the method may include communicating, via the first RAT, a service context received from the core network service to the UE, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service. The operation at 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operation at 1710 may be performed by a service context manager as described with reference to Figure 14The described service context manager 1430 executes.

[0266] At 1715, the method may include communicating a service message received from the UE via the first RAT to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second RAT. The operation at 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1715 may be performed by the service message manager 1435 as described with reference to Figure 14 the described service message manager 1435.

[0267] Figure 18 Illustrates a flowchart of a method 1800 showing support for establishing a connection to a legacy first-generation wireless network via a service-based network according to one or more aspects of the present disclosure. The operations of method 1800 may be implemented by a network entity or its components as described herein. For example, the operations of method 1800 may be performed by a network entity as described with reference to Figures 1 to 7 and Figures 12 to 15 the described network entity. 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.

[0268] At 1805, the method may include receiving, from the UE via a DU associated with a first RAT, a service request indicating a core network service provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, wherein the core network service is associated with a CU of a second RAT. The operation at 1805 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1805 may be performed by the service request manager 1425 as described with reference to Figure 14 the described service request manager 1425.

[0269] At 1810, the method may include sending, via the DU according to the first RAT based on the service request, a service context for communicating between the UE and the core network service to the UE, the service context indicating a destination associated with the core network service. The operation at 1810 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1810 may be performed by the service context manager 1430 as described with reference to Figure 14 the described service context manager 1430.

[0270] At 1815, the method may include receiving, from the UE via the DU, a service message according to the service context, the service message including the destination and a payload in a format associated with the second RAT. Operations at 1815 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1815 may be performed by a service message manager 1435 as described with reference to Figure 14 and described in the service message manager 1435.

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

[0272] Aspect 1: A method for wireless communication at a UE, the method including: receiving, via a first RAT from a DU, control information indicating a core network service provided by a service-based network of the first RAT and configured to handover with a core network associated with a RAN associated with the DU, where the DU is associated with the first RAT and where the core network service is associated with a CU of a second RAT; sending, via the first RAT and at least partially based on the control information, a service request indicating the core network service associated with the CU of the second RAT to the DU; receiving, at least partially based on the service request, via the first RAT from the DU a service context for communicating with the core network service according to the first RAT, the service context indicating a destination associated with the core network service; and sending, according to the service context via the first RAT to the DU, a service message including the destination and a payload in a format associated with the second RAT.

[0273] Aspect 2: The method according to aspect 1, wherein receiving the control information includes: receiving the control information via a system information block sent by the DU.

[0274] Aspect 3: The method according to any one of aspects 1 to 2, the method further including: sending a query for a service via the second RAT to the DU, wherein receiving the control information is responsive to the query.

[0275] Aspect 4: The method according to any one of aspects 1 to 3, wherein sending the service message includes: sending the service message including the payload, the payload including a NAS message associated with a core network destination of the second RAT.

[0276] Aspect 5: The method according to any one of aspects 1 to 4, wherein sending the service message includes: sending the service message including the payload, the payload including an RRC message associated with the CU of the second RAT.

[0277] Aspect 6: The method according to any one of Aspects 1 to 5, wherein transmitting the service message includes: transmitting the service message including the PDU of the format associated with the second RAT.

[0278] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: receiving, from the DU according to the service context, a second service message, the second service message including a second payload of the format associated with the second RAT.

[0279] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: communicating with a network entity associated with the second RAT and the CU.

[0280] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the service context includes a RAN configuration for communicating with the DU as part of the core network service.

[0281] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the destination associated with the core network service is a network address.

[0282] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the service context indicates an identifier associated with the core network destination of the second RAT.

[0283] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the core network service is associated with an application programming interface.

[0284] Aspect 13: A method for wireless communication at a DU, the method comprising: conveying a service request received from a UE via a first RAT to a core network service, the core network service provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, wherein the DU is associated with the first RAT, and wherein the core network service is associated with a CU of a second RAT; conveying, via the first RAT, a service context received from the core network service to the UE, the service context for communicating between the UE and the core network service according to the first RAT and indicating a destination associated with the core network service; and conveying, according to the service context, a service message received from the UE via the first RAT to the core network service, the service message including the destination and a payload of a format associated with the second RAT.

[0285] Aspect 14: The method according to aspect 13, the method further comprising: transmitting, via the first RAT, a system information block indicating that the core network service is provided by the service-based network of the first RAT, wherein the service request is a response to the transmission of the system information block.

[0286] Aspect 15: The method according to any one of aspects 13 to 14, the method further comprising: receiving, via the first RAT, from the UE a query for a service via the second RAT; and in response to the query and via the first RAT, sending to the UE control information indicating that the core network service is provided by the service-based network of the first RAT, wherein the service request is in response to the transmission of the control information.

[0287] Aspect 16: The method according to any one of aspects 13 to 15, the method further comprising: communicating, via the first RAT according to the service context, a second service message received from the core network service to the UE, the service message including a second payload in the format associated with the second RAT.

[0288] Aspect 17: The method according to any one of aspects 13 to 16, wherein the service context includes a RAN configuration for communicating with the DU as part of the core network service.

[0289] Aspect 18: The method according to any one of aspects 13 to 17, wherein the destination associated with the core network service is a network address.

[0290] Aspect 19: The method according to any one of aspects 13 to 18, wherein the service context indicates an identifier associated with the core network destination of the second RAT.

[0291] Aspect 20: The method according to any one of aspects 13 to 19, wherein the core network service is associated with an application programming interface.

[0292] Aspect 21: A method for wireless communication at a core network service, the method comprising: receiving, via a DU associated with a first RAT, a service request indicating the core network service from a UE, the core network service being provided by a service-based network of the first RAT and configured to hand over with a RAN associated with the DU, wherein the core network service is associated with a CU of a second RAT; sending, at least in part based on the service request, a service context for communicating between the UE and the core network service to the UE via the DU according to the first RAT, the service context indicating a destination associated with the core network service; and receiving a service message from the UE via the DU according to the service context, the service message including the destination and a payload in a format associated with the second RAT.

[0293] Aspect 22: The method according to aspect 21, the method further comprising: extracting a NAS message associated with the second RAT from the payload; and sending the NAS message to a core network destination of the second RAT, wherein the payload indicates the core network destination.

[0294] Aspect 23: The method according to aspect 22, wherein sending the NAS message comprises: sending the NAS message to an access and mobility management function via an N2 interface.

[0295] Aspect 24: The method according to any one of aspects 22 to 23, wherein sending the NAS message comprises: sending the NAS message to a user plane function via an N3 interface.

[0296] Aspect 25: The method according to any one of aspects 22 to 24, the method further comprising: receiving a second NAS message addressed to the UE from a core network entity of the second RAT; and conveying a second service message to the UE via the DU according to the service context, the second service message including a second payload, the second payload including the second NAS message.

[0297] Aspect 26: The method according to any one of aspects 21 to 25, the method further comprising: extracting an RRC message associated with the second RAT from the payload; and sending the RRC message to the CU.

[0298] Aspect 27: The method according to any one of aspects 21 to 26, wherein receiving the service message comprises: receiving the service message including the payload, the payload including a PDU in the format associated with the second RAT.

[0299] Aspect 28: The method according to any one of aspects 21 to 27, wherein the destination associated with the core network service is a network address.

[0300] Aspect 29: The method according to any one of aspects 21 to 28, wherein the service context indicates an identifier associated with the core network destination of the second RAT.

[0301] Aspect 30: The method according to any one of aspects 21 to 29, wherein the core network service is associated with an application programming interface.

[0302] Aspect 31: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the apparatus to perform the method according to any one of aspects 1 to 12.

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

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

[0305] Aspect 34: An apparatus for wireless communication at a DU, the apparatus comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the apparatus to perform the method according to any one of aspects 13 to 20.

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

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

[0308] Aspect 37: An apparatus for wireless communication at a core network service, the apparatus comprising: a processor; and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the apparatus to perform the method according to any one of aspects 21 to 30.

[0309] Aspect 38: An apparatus for wireless communication at a core network service, the apparatus including at least one component for performing the method according to any one of Aspects 21 to 30.

[0310] Aspect 39: A non-transitory computer-readable medium storing code for wireless communication at a core network service, the code including instructions executable by a processor to perform the method according to any one of Aspects 21 to 30.

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

[0312] 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 may also be 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.

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

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

[0315] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using 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 positions, including being distributed such that different portions of the functions are implemented at different physical locations.

[0316] Computer-readable media includes both non-transitory computer storage media and communication media, which includes any medium that facilitates transfer of a computer program from one location to another. Non-transitory storage media can be any available media 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 (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 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 from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, 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. Disk can magnetically reproduce data, and disc can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0317] As used herein (including in the claims), the "or" used in a list of items (e.g., a list of items 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 present 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".

[0318] The term "determine" encompasses a variety of actions and, thus, "determine" can include operations such as calculating, computing, 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.

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

[0320] The description set forth herein in connection with the figures describes example configurations and does not represent all examples that can be implemented or that are 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 can 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.

[0321] The description provided herein enables a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure are obvious to a person of ordinary skill in the art, and the general principles defined herein can 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, but should be accorded the broadest 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; and 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 via a first radio access technology, the control information indicating a core network service provided by a service-based network of the first radio access technology and configured to handover with a radio access network associated with the distributed unit, wherein the distributed unit is associated with the first radio access technology, and wherein the core network service is associated with a central unit of a second radio access technology; send a service request to the distributed unit via the first radio access technology and at least partially based on the control information, the service request indicating the core network service associated with the central unit of the second radio access technology; receive, at least partially based on the service request, a service context from the distributed unit via the first radio access technology for communicating with the core network service according to the first radio access technology, the service context indicating a destination associated with the core network service; and send a service message to the distributed unit via the first radio access technology according to the service context, the service message including the destination and a payload in a format associated with the second radio access technology.

2. The apparatus according to claim 1, wherein the instructions for receiving the control information can be executed by the processor to cause the apparatus to: receive the control information via a system information block sent by the distributed unit.

3. The apparatus according to claim 1, wherein the instructions can be further executed by the processor to cause the apparatus to: send a query for a service to the distributed unit via the second radio access technology, wherein the control information is received in response to the query.

4. The apparatus according to claim 1, wherein the instructions for sending the service message can be executed by the processor to cause the apparatus to: send the service message including the payload, the payload including a non-access stratum message associated with a core network destination of the second radio access technology.

5. The apparatus according to claim 1, wherein the instructions for sending the service message can be executed by the processor to cause the apparatus to: send the service message including the payload, the payload including a radio resource control message associated with the central unit of the second radio access technology.

6. The apparatus according to claim 1, wherein the instructions for sending the service message can be executed by the processor to cause the apparatus to: send the service message including a packet data unit in the format associated with the second radio access technology.

7. The apparatus according to claim 1, wherein the instructions can be further executed by the processor to cause the apparatus to: Receive a second service message from the distributed unit according to the service context, the second service message including a second payload in the format associated with the second radio access technology.

8. The apparatus according to claim 1, wherein the instructions can be further executed by the processor to cause the apparatus to: Communicate with a network entity associated with the second radio access technology and the central unit.

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

10. The apparatus according to claim 1, wherein the destination associated with the core network service is a network address.

11. The apparatus according to claim 1, wherein the service context indicates an identifier associated with the core network destination of the second radio access technology.

12. The apparatus according to claim 1, wherein the core network service is associated with an application programming interface.

13. An apparatus for wireless communication at a distributed unit, 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: Forward a service request received from a user equipment (UE) via a first radio access technology to a core network service provided by a service-based network of the first radio access technology and configured to hand over with a radio access network associated with the distributed unit, wherein the distributed unit is associated with the first radio access technology, and wherein the core network service is associated with a central unit of a second radio access technology; Forward a service context received from the core network service to the UE via the first radio access technology, the service context for communicating between the UE and the core network service according to the first radio access technology and indicating a destination associated with the core network service; And Forward a service message received from the UE via the first radio access technology to the core network service according to the service context, the service message including the destination and a payload in a format associated with the second radio access technology.

14. The apparatus according to claim 13, wherein the instructions can be further executed by the processor to cause the apparatus to: Transmit, via the first radio access technology, a system information block indicating that the core network service is provided by the service-based network of the first radio access technology, wherein the service request is a response to the transmission of the system information block.

15. The apparatus according to claim 13, wherein the instructions can be further executed by the processor to cause the apparatus to: Receive, via the first radio access technology, a query for a service via the second radio access technology; and In response to the query and via the first radio access technology, send control information to the UE indicating that the core network service is provided by the service-based network of the first radio access technology, wherein the service request is in response to the sending of the control information.

16. The apparatus according to claim 13, wherein the instructions can be further executed by the processor to cause the apparatus to: Transmit, via the first radio access technology according to the service context, a second service message received from the core network service to the UE, the service message including a second payload in the format associated with the second radio access technology.

17. The apparatus according to claim 13, wherein the service context includes a radio access network configuration for communicating with the distributed unit as part of the core network service.

18. The apparatus according to claim 13, wherein the destination associated with the core network service is a network address.

19. The apparatus according to claim 13, wherein the service context indicates an identifier associated with the core network destination of the second radio access technology.

20. The apparatus according to claim 13, wherein the core network service is associated with an application programming interface.

21. An apparatus for wireless communication at a core network service, 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, via a distributed unit associated with a first radio access technology, a service request from a user equipment (UE) indicating a core network service provided by a service-based network of the first radio access technology and configured to handover with a radio access network associated with the distributed unit, wherein the core network service is associated with a central unit of a second radio access technology; At least partially based on the service request, send, via the distributed unit according to the first radio access technology, a service context for communicating between the UE and the core network service to the UE, the service context indicating a destination associated with the core network service; And Receive, via the distributed unit according to the service context, a service message from the UE, the service message including the destination and a payload in a format associated with the second radio access technology.

22. The apparatus according to claim 21, wherein the instructions can be further executed by the processor to cause the apparatus to: Extract a non-access stratum message associated with the second radio access technology from the payload; and Send the non-access stratum message to the core network destination of the second radio access technology, wherein the payload indicates the core network destination.

23. The apparatus according to claim 22, wherein the instructions for sending the non-access stratum message can be executed by the processor to cause the apparatus to: Send the non-access stratum message to the access and mobility management function via the N2 interface.

24. The apparatus according to claim 22, wherein the instruction for sending the non-access stratum message can be executed by the processor to cause the apparatus to: Send the non-access stratum message to the user plane function via the N3 interface.

25. The apparatus according to claim 22, wherein the instruction can be further executed by the processor to cause the apparatus to: Receive a second non-access stratum message addressed to the UE from a core network entity of the second radio access technology; and Transmit a second service message to the UE via the distributed unit according to the service context, the second service message including a second payload, the second payload including the second non-access stratum message.

26. The apparatus according to claim 21, wherein the instruction can be further executed by the processor to cause the apparatus to: Extract a radio resource control message associated with the second radio access technology from the payload; and Send the radio resource control message to the central unit.

27. The apparatus according to claim 21, wherein the instruction for receiving the service message can be executed by the processor to cause the apparatus to: Receive the service message including the payload, the payload including a packet data unit in the format associated with the second radio access technology.

28. The destination associated with the core network service is a network address according to claim 21.

29. The service context indicates an identifier associated with a core network destination of the second radio access technology according to claim 21.

30. A method for wireless communication at a user equipment (UE), the method comprising: Receiving, via a first radio access technology, control information from a distributed unit, the control information indicating a core network service provided by a service-based network of the first radio access technology and configured to handover with a radio access network associated with the distributed unit, wherein the distributed unit is associated with the first radio access technology, and wherein the core network service is associated with a central unit of a second radio access technology; Sending, via the first radio access technology and at least partially based on the control information, a service request to the distributed unit, the service request indicating the core network service associated with the central unit of the second radio access technology; Receiving, at least partially based on the service request, via the first radio access technology from the distributed unit a service context for communicating with the core network service according to the first radio access technology, the service context indicating a destination associated with the core network service; And Send a service message to the distributed unit via the first radio access technology according to the service context, where the service message includes the destination and a payload in a format associated with the second radio access technology.

Images