WO2022115364A1

WO2022115364A1 - Remote direct memory access (rdma) in next generation cellular networks

Info

Publication number: WO2022115364A1
Application number: PCT/US2021/060297
Authority: WO
Inventors: Zongrui DING; Qian Li; Sangeetha L. Bangolae; Abhijeet Kolekar; Thomas Luetzenkirchen; Puneet Jain; Ching-Yu Liao; Alexandre Saso STOJANOVSKI; Sudeep Palat; Youn Hyoung Heo; Xiaopeng Tong
Original assignee: Intel Corporation
Priority date: 2020-11-25
Filing date: 2021-11-22
Publication date: 2022-06-02

Abstract

Various embodiments herein are directed to enabling remote direct memory access (RDMA) between a user equipment (UE) and a cellular network. Some embodiments may set up QPs and keys to enable data exchange through RDMA for computing scaling solutions through the control plane or user plane. The existing identifiers inside of the cellular network may also be used as the keys to facilitate identifying services such as a network slice or a compute task.

Description

REMOTE DIRECT MEMORY ACCESS (RDMA) IN NEXT GENERATION

CELLULAR NETWORKS

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No.

63/118,476, which was filed November 25, 2020.

FIELD

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to enabling remote direct memory access (RDMA) between a user equipment (UE) and a cellular network.

BACKGROUND

Remote direct memory access (RDMA) is a host-offload, operating system (OS) by-pass technology to enable a secure direct memory-to-memory data communication between two applications on different hosts at network. Different from traditional network interfaces, RDMA bypasses the OS and allows programs to have low latency, high throughput, and a small CPU footprint. Among other things, embodiments of the present disclosure are directed to enabling RDMA between a UE and a cellular network.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

Figure 1 illustrates an example of RDMA protocol stack options in accordance with various embodiments.

Figure 2 illustrates an example of an architecture to enable augmented computing in RAN in accordance with various embodiments.

Figure 3 illustrates an example of a computing (Comp) control function (CF)/service function (SF) based solution to provide computing as a service in accordance with various embodiments.

Figure 4 illustrates an example of a Comp RF based solution to provide computing as resource in accordance with various embodiments.

Figure 5 illustrates an example of a RDMA over cellular network protocol stack in accordance with various embodiments.

Figures 6A and 6B illustrate an example of a Comp RF based solution to provide computing as resource in accordance with various embodiments. Figure 7 illustrates an example of a process to set up RDMA queue pair (QP) and keys through a control plane for embodiment 1 initiated by a UE in accordance with various embodiments.

Figure 8 illustrates an example of a process to set up RDMA QP and keys through a control plane for embodiment 1 initiated by computing functions in accordance with various embodiments.

Figures 9A and 9B illustrate an example of a process to set up RDMA QP and keys through a user plane for embodiment 1 initiated by a UE in accordance with various embodiments.

Figure 10 illustrates an example of a process to set up RDMA QP and keys through a user plane for embodiment 1 initiated by computing functions in accordance with various embodiments.

Figure 11 illustrates an example of a process to set up RDMA QP and keys through a control plane for embodiment 2 initiated by a UE in accordance with various embodiments.

Figure 12 illustrates an example of a process to set up RDMA QP and keys through a control plane for embodiment 2 initiated by DU/CU in accordance with various embodiments.

Figure 13 illustrates an example of a process to set up RDMA QP and keys through a user plane for embodiment 2 initiated by UE in accordance with various embodiments.

Figure 14 illustrates an example of a process to set up RDMA QP and keys through a user plane for embodiment 2 initiated by distributed unit (Decentralized unit (CU) in accordance with various embodiments.

Figure 15 illustrates an example of a network architecture according to various embodiments.

Figure 16 illustrates an example of a wireless network in accordance with various embodiments.

Figure 17 is a block diagram illustrating components, according to some embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., anon- transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

Figure 18 depicts an example of a procedure for practicing the various embodiments discussed herein.

Figure 19 depicts another example of a procedure for practicing the various embodiments.

Figure 20 depicts another example of a procedure for practicing the various embodiments.

DETAILED DESCRIPTION The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

In some embodiments, there may be different RDMA protocol stacks defined based on different media and transport protocols as shown, for example, in Figure 1. There are are a number of studies in both academia and industry about the benchmark for RDMA of RoCE/iWARP based solution performance compared to TCP/IP based solution. Some such studies show that generally a lOx performance gain can be achieved for RoCEv2 compared to TCP/IP in terms of throughput and latency.

The next generation cellular network air interface throughput is expected to be lOx from the 5G network, which would be comparable for the current ethemet throughput. Currently, there are no existing solutions to address the interactions among computing functions as well as computing functions and other functions.

The present disclosure provides embodiments that incorporate RDMA-like protocol(s) for computing offloading, wherein RDMA is used for data exchange between two hosts, one at a UE (e.g., UE 1502 of Figure 15) and one at the network function in the cellular network. In this disclosure, the RDMA data exchange may include, but is not limited to:

• data exchange between application instances at different hosts (e.g., between UE and a Comp SF);

• computational (resource, tasks, etc.) offloading between host and computing platform/devices (e.g., between UE and computing devices in the cellular network); and/or

• For remote data access such as read/wirte data from a host to a data storage (e.g., between UE and a Data Storage Function (DSF)).

In RDMA, Queue Pairs (QPs) are defined end to end to exchange data within allocated local and remote memories with keys such as local, remote keys to indicate the right to access corresponding memories. For cellular networks, the network memory either serving as computing resource or data storage resource need to be controlled by the cellular network. Thus, the memory and key allocation/exchange can be managed by the cellular network.

To enable computing offloading between two hosts over an air interface (e.g., Uu in 5G networks), this disclosure includes the following embodiments:

• Description/requirements of RDMA related information to be used for data change between UE and the network functions of the cellular network to enable interoperability.

• Mechanisms to exchange RDMA capabilities between two hosts (e.g., UE and the network functions in cellular network).

• Mechanisms to enable security protection and logical service partition for two hosts (e.g., using QPs and related keys for UE to access network resource/service).

• Mechanisms to map the keys to the cellular network identifiers, if applicable.

The embodiments herein enable interoperability of RDMA between UE and the cellular network, RDMA related information is specified and RDMA capability exchange is proposed. Some embodiments may set up QPs and keys to enable data exchange through RDMA for computing scaling solutions through the control plane or user plane. The existing identifiers inside of the cellular network may also be used as the keys to facilitate identifying services such as a network slice or a compute task.

There are several advantages of providing computing either as a new service or as a network capability based on different scenarios. First, the computing tasks can be completed at the network edge to optimize latency. This latency includes communication latency as well as the compute task launch and execution latency. Second, the end device can augment the computing by providing requirements about the computing environment and the compute task. Third, the resource efficiency and latency can also be optimized using paradigms like serverless computing to handle more dynamic workload.

RAN Architecture with Computing Functions

Figure 2 shows an example of a RAN architecture according to various embodiments. In this example, the RAN includes a communication plane, a computing plane, and a data plane. The functions to enable network computing include a RAN computing control client (Comp CC) at the UE, as well as a RAN computing control function (Comp CF) and the RAN computing service function (Comp SF) at the network side.

EMBODIMENTS 1 AND 2 Some embodiments may provide computing scaling between a UE and the cellular network with dynamic resource availability, including computing as a service (embodiment 1 as shown by Figure 3) and computing as resource (embodiment 2 as shown by Figure 4).

In embodiment 1, a function called Comp CSF interfaces applications and virtualizes/orchestrates local/remote resources dynamically for computing offloading. In embodiment 2, a function called Comp RF-C interfaces the network Comp RF-S for computing resource discovery and offloading.

RDMA can be applied as a transport protocol stack for computing offloading for both solutions, as shown by Figure 5. According to various embodiments, existing protocols (e.g., RoCEvl, RoCEv2, iWARP, etc.) that are used in different network communication medias and network protocols are migrated to the cellular network environment for allowing computing offloading between two hosts to exchange data over air interface, e.g., Uu in 5G network, but the solutions are not limited to these existing protocols. In the example of Figure 5, the protocol stacks, corresponding to RoCEvl, RoCEv2, and iWARP for cellular, are named RDMA over Cellular Network (RoCN) vl, RoCNv2, and iWARP for Cellular Network (iWARP-CN).

Modifications to IB transport protocol or iWARP protocol may be needed when adapting to the cellular network, which is out of this disclosure's scope. These protocol stacks are examples, and the new RDMA protocol stack for cellular can be standardized. The mechanisms discussed herein can also apply but are not limited to existing RDMA protocols.

EMBODIMENT 3

In an alternative embodiment, a particular method for mandating RDMA only is not standardized, but rather a framework and available IEs to allow multiple methods of RDMA like technologies to work are provided. An example of this embodiment is shown by Figures 6A and 6B. Among other things, this embodiment allows any direct memory transfer method, standardized or proprietary, to be quickly deployed without the need for standardization work in 3GPP.

Solution Define Common Sublayer PDU Type, and Common sublayer will provide common hooks to Cellular system for fine QoS, Congestion control, or any other by IE. Security establishment and keys that the application can manage, which can be used at the cellular level.

The present disclosure provides details using RDMA as an example protocol as described in embodiments 1 and 2. Embodiment 3 can be considered as a superset of embodiments 1 and 2. In some implementations, the terminology and/or details in embodiments 1 and 2 can be replaced by generic IE and messages. For example, RDMA requirements: Generic Protocol-related information, capability exchange, an indicator to denote the type of protocol, and a container to carry QP and keys information.

RDMA RELATED INFORMATION

RDMA requirements provide the information needed between two hosts (e.g., UE and RAN/network functions) to enable interoperability for computing and data access. This information may include, but is not limited to the following:

• RDMA protocol type (e.g., RoCNvl, RoCNv2, iWARP-CN, etc.) and version.

• RDMA configurations (e.g., packet interval, initial data rate, etc.).

• RDMA device type and/or manufacturers (e.g., the RDMA network interface card (RNIC) type and manufacturer).

• Number of QPs and type.

• Number of keys and type.

• Requirements on memory (e.g., size, type, maximum occupancy, etc.).

• RDMA indicator which indicates that the RDMA is the chosen transport for computing or data service.

RDMA CAPABILITY EXCHANGE

For embodiment 1, the UE can exchange RDMA capability between Comp CSF and Comp CF over reference point 1. The RDMA capability information can indicate whether RDMA is supported and a subset of RDMA related information as discussed previously.

For embodiment 2, the UE can exchange RDMA capability between Comp RF-C and Comp RF-S, and similar information can be exchanged as embodiment 1. The manner in which Comp RFs can get RDMA related information is up to the implementation.

In combination, the RDMA capability can be exchanged through RRC device capability inquiry request/response or the on-demand SIB to indicate the network's capability regardless of embodiment 1 or embodiment 2.

For embodiment 3, the RDMA capability can be exchanged by the defined IEs in the common sublayer.

RDMA RELATED INFORMATION EXCHANGE BETWEEN UE AND RAN/NETWORK FUNCTION

As discussed in more detail in the sections infra, the RDMA related information can be carried through one or more of the following mechanisms:

• Inside a new L3 container for Non-Access Stratum (NAS) eschange between the UE and CN node. • Inside a new container for Comp CF or the NAS container. In this case, it is transparently passed by the xNB (e.g., a 6G nodeB (NB), gNB, ng-eNB, or other RAN node) to Comp CF. This new container or NAS constainer can be piggybacked in an RRC message.

• Inside an RRC message. In this case, xNB may need to relay this to Comp CF.

In some embodiments, the RDMA related information may be an indicator or may include more detailed information as described in the previous sections. The existing RRC/NAS messages can be extended by adding new IEs/containers for RDMA, or alternatively new RRC/NAS messages dedicated for RDMA transfer can be defined. For a new container for Comp CF, a new L3 message can be defined, which represents the logical connection between UE and Comp CF for compute transport.

In some embodiments, the RDMA related information is exemplified between UE and the Comp CF/SF for computing offloading purposes using L3 messages. However, the RDMA related information may also be exchanged with other functions, such as data functions or other network functions in the core network for data exchange. In that case, the message flows procedures discussed in the following sections can apply with replacing Comp CF/SF with the corresponding functions and appropriate message container.

RDMA QP AND KEYS SET UP PROCEDURES FOR EMBODIMENT 1

In various embodiments, the RDMA QPs and keys can be set up through control plane (CP) or user plane (UP) between UE and the computing functions initiated by the UE or the computing functions. In some embodiments, the QP setup request may be initiated by the UE for both CP and UP approaches. In other embodiments, the QP setup request may be initiated by the Comp CF or the Comp SF.

Figure 7 shows an example of a procedure for setting up QP and keys through control plane initiated by UE, which may operate as follows:

1) UE sends a RRC RAN compute setup request to xNB to set up compute transport with an indication for RDMA and RDMA related information described above.

2) The xNB sends out a RAN compute session establishment request to Comp CF with a special IE to include RDMA requirements received from Step 1).

3) If Comp CF accepts the compute task, a Comp SF with required RDMA support is selected.

4) Comp CF set up the compute task and also request to create required QPs with the RDMA related information received in Step 1). This message can be a request/response for setting up compute tasks with the requirements in RDMA information elements (IEs). The QP IDs and keys information is sent back to the Comp CF. Multiple QPs and multiple keys can be created at the Comp SF.

5) Comp CF sends a RAN compute session establishment response to the xNB to accept the compute task with RDMA support, with the RDMA QP IDs and keys.

6) The xNB sends the RDMA QP IDs and keys using RRC reconfiguration message to the UE.

Figure 8 shows an example of a procedure for setting up RDMA QP and keys through control plane initiated by Computing functions, which may operate as follows:

1) The Comp CF decides to set up RDMA with UE. This can be triggered by different reasons such as that the Comp SF is requesting for RDMA with UE to improve performance, mobility, change of Comp SF or a previous trigger event/conditions are met. If there is no assigned Comp SF or Comp SF change required, Comp CF may select anew Comp SF for the UE.

2) Comp CF request to set up QPs and generate keys with the assigned Comp SF similar to Figure 7 Step 4).

3) The Comp CF sends the RAN Compute session modification request message with the RDMA requirements and the generated QP ID and keys to the xNB. If the UE is not in RRC-CONNECTED state, the UE can be paged with the IEs for RDMA requirements and QP, key information or an indicator for RDMA Once UE is in RRC-CONNECTED mode, the procedures in Figure 10 can be applied as described below.

4) The xNB sends the RRC Reconfiguration message to the UE with the RDMA requirements, QP IDs and keys.

5) The UE sends the RRC Reconfiguration complete once the RDMA QP and keys are properly created and stored on UE.

Figures 9A and 9B show an example of a procedure for setting up QP and keys through user plane initiated by UE (Figure 9B is a continuation of the procedure beginning in Figure 9A), which may operate as follows:

1) UE sends a RRC RAN compute setup request to request compute transport setup with an indication for RDMA and optionally including the RDMA related information discussed previously.

2) xNB sends a RAN compute session establishment request with the RDMA indicator to the Comp CF. 3) If Comp CF accepts the compute task, a Comp SF with the required RDMA support is selected.

4) The Comp CF sets up the compute task with the selected Comp SF. An RDMA profile can be generated for the compute task based on the RDMA related information or the compute task's information. An identifier such as a task ID can be used to identify the RDMA profile about QPs and keys. The QPs and keys are not created during this step.

5) The Comp CF sends a RAN compute session establishment response message to the xNB with the RDMA profile's identifier such as the task ID.

6) The xNB sends a RRC Reconfiguration message to UE to set up radio bearer for computing. This message shall include the necessary bearer configuration information for RDMA connection management (CM) traffic such as QoS, priority, protocol, etc.

7) The UE sends a RRC Reconfiguration complete message to xNB. Then the radio bearer for computing is ready.

8) The compute transport is ready for the RDMA CM traffic. Then UE sends a request for QPs and keys described by the RDMA related information. The RDMA CM traffic can be RDMA traffic. For example, a special QP can be used to accept RDMA CM traffic. In this case, the QP ID may be pre-configured or sent from Comp CF in Step 4). The RDMA CM(Connection Management) traffic can also use other protocols such as HTTP/TCP to set up the QPs and keys.

9) The Comp SF can verify the task ID and create the required QPs and keys for the UE based on the RDMA profile set up at Step 3).

10) The Comp SF sends out the QP IDs and keys to the UE via the user plane.

Note: the RDMA CM (Connection Management) traffic is the user plane traffic for the purpose of connection management. In some embodiments, different protocols can be used to carry the RDMA CM information. For example, a special QP can be used and RDMA CM information is in the form of a RDMA packet. The RDMA CM information can also be exchanged by HTTP, etc.

Figure 10 shows an example of a procedure for setting up QP and keys through user plane initiated by the computing functions, which may operate as follows:

1) The Comp CF decides to set up RDMA between a Comp SF and the UE, which is similar to Figure 8 Step 1).

2) Comp CF sends RAN compute session modification request message to the xNB with an indicator for RDMA similar to Figure 8 Step 3).

3) The xNB sends the RRC reconfiguration message with RDMA indicator for CM traffic 4) The UE responds with a RRC reconfiguration complete message to the xNB to accept the request.

5) The compute transport between the UE and the Comp SF is ready to send RDMA CM traffic. Then the information about the RDMA requirements, QP and keys are sent to the UE via user plane.

RDMA QP AND KEYS SET UP PROCEDURES FOR EMBODIMENT 2

For embodiment 2, the RDMA QPs and keys are created between UE and RAN DU/CU and handled by the Comp RF-C in UE and Comp RF-S in RAN CU or DU through a control plane message initiated by the UE or RAN DU/CU as shown in Figures 11 and 12, respectively. The L2/L3 message referred to here can be MAC-based CE or RRC-based message. These can utilize existing messages similar to those used/discussed in above sections as part of embodiment 1 or newly defined compute/RDMA-specific messages.

Figure 11 shows an example of a procedure for setting up QP and keys through user plane initiated by the UE, which may operate as follows:

1) UE requests RDMA access through Comp RF-C and sends the L2/L3 message for computing with the RDMA related information described above to the Comp RF-S in RAN DU or CU.

2) The RAN DU/CU accepts the compute task and create related QP and keys. 3) The RAN DU/CU (Comp RF-S) sends the QP IDs and keys to the UE (Comp RF-C) to accept the compute task. If the compute task is not accepted, the QPs and keys shall not be created, and a reason may be included in the compute response.

Figure 12 shows an example of a procedure for setting up QP and keys through control plane initiated by the DU/CU, which may operate as follows:

1) The Comp RF-S in RAN DU or CU decides about setting up RDMA with the UE, then generating the related QP and key information based on the information such as UE's capability exchanged before the decision.

2) RAN DU/CU sends a L2/L3 message with the RDMA requirements, RDMA QP and key information to the UE for setting up RDMA with the UE.

3) UE confirms the RDMA setup by sending a L2/L3 message with RDMA information accepted. Figure 13 shows an example of a procedure for setting up RDMA between the Comp RF- C in UE and Comp RF-S in RAN CU or DU through user plane initiated by the UE, which may operate as follows:

1) UE requests RDMA access through Comp RF-C and sends the L2/L3 message for computing with an RDMA indicator to the Comp RF-S in RAN DU or CU, optionally including the RDMA requirements described above.

2) RAN DU/CU sends a L2/L3 message to indicate the compute task is accepted.

3) The UE is ready to send RDMA CM traffic, which can use any available protocol such as HTTP, special RDMA QPs similar to Figure 9B Step 8). A special QP ID can be preconfigured or sent via Step 2). UE sends RDMA related information for creating QP and keys to RAN DU/CU, which may include a task ID to indicate the associated compute task and the related RDMA profile. If a L3 message is used, then radio bearer can be established between UE and RAN CU or a DU with a collocated CU-UP. If a L2 message is used, the RDMA CM traffic can be sent in any suitable manner, such as via small data transfer. In this case, Step 3) may be combined with Step 1) and Step 2).

4) The RAN DU/CU verifies the compute task and create the required QPs and keys based on the RDMA related information received in Step 3).

5) The RAN DU/CU sends back the RDMA QP IDs and keys to UE via user plane.

Figure 14 shows an example of a procedure for setting up RDMA between the Comp RF- C in UE and Comp RF-S in RAN CU or DU through user plane initiated by the RAN DU/CU, which may operate as follows:

1) The Comp RF-S in RAN DU or CU decides setting up RDMA with the UE due to the reasons mentioned in Figure 8, Step 1).

2) RAN DU/CU sends a L2/L3 message with an indicator to setup RDMA with the UE.

3) The UE sends a L2/L3 message to indicate RDMA request is accepted.

4) The UE is ready to send RDMA CM traffic between RAN DU/CU and the UE similar to Figure 13 Step 3). Then the RDMA requirements and QP, key info can be sent via user plane.

RDMA QP ID AND KEYS

Some examples of possible identifier mappings between RDMA QP ID, keys, and the cellular network identifiers are as follows. • QP ID: The identifier for a logic connection with certain QoS. One compute task can include multiple QPs. The task ID can be mapped to a RDMA profile for creating the required QPs and keys.

• L key: Local key is to access local memory.

• R key: Remote key to access the remote memory.

• P key: Partition key to define the virtual partition between computation contexts. The S- NSSAI can be used as P_key to identify different network slice

• Q key: Queue key to define QP based domain, how unreliable datagram QP can talk to each other for multi-cast or broadcast.

A queue key can be allocated for parallel computing. For example, a RDMA write packet with a Q key can be sent to access different QPs on different memory space with the same computing commands to realize parallel computing. For example, the kernel program for runtimes like OpenCL and CUDA can be sent by a UE using a unreliable QP to multiple computing devices holding the UD QPs identified by the same Q key. For OpenCL and CUDA, the same kernel programs needed to be sent to different command queues associated with different devices. The Q key enables that the kernel program can be sent once to multiple devices.

SYSTEMS AND IMPLEMENTATIONS

Figures 15-16 illustrate exampels of various systems, devices, and components that may implement aspects of disclosed embodiments. For example, Figure 15 illustrates an example network architecture 1500 according to various embodiments. The network 1500 may operate in a manner consistent with 3GPP technical specifications for Long Term Evolution (LTE) or Fifth Generation (5G)/New Radio (NR) systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.

The network 1500 includes a UE 1502, which is any mobile or non-mobile computing device designed to communicate with a RAN 1504 via an over-the-air connection. The UE 1502 is communicatively coupled with the RAN 1504 by a Uu interface, which may be applicable to both LTE and NR systems. Examples of the UE 1502 include, but are not limited to, a smartphone, tablet computer, wearable computer, desktop computer, laptop computer, in-vehicle infotainment system, in-car entertainment system, instrument cluster, head-up display (HUD) device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, machine-to-machine (M2M), device-to-device (D2D), machine-type communication (MTC) device, Internet of Things (IoT) device, and/or the like. The network 1500 may include a plurality of UEs 1502 coupled directly with one another via a D2D, ProSe, PC5, and/or sidelink interface. These UEs 1502 may be M2M/D2D/MTC/IoT devices and/or vehicular systems that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. The UE 1502 may be the same or similar as the UEs shown and described with respect to Figures 1-6.

In some embodiments, the UE 1502 may additionally communicate with an AP 1506 via an over-the-air (OTA) connection. The AP 1506 manages a WLAN connection, which may serve to offload some/all network traffic from the RAN 1504. The connection between the UE 1502 and the AP 1506 may be consistent with any IEEE 802.11 protocol. Additionally, the UE 1502, RAN 1504, and AP 1506 may utilize cellular-WLAN aggregation/integration (e.g., LWA/LWIP). Cellular-WLAN aggregation may involve the UE 1502 being configured by the RAN 1504 to utilize both cellular radio resources and WLAN resources.

The RAN 1504 includes one or more access network nodes (ANs) 1508. The ANs 1508 terminate air-interface(s) for the UE 1502 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and PHY/Ll protocols. In this manner, the AN 1508 enables data/voice connectivity between CN 1520 and the UE 1502. The ANs 1508 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells; or some combination thereof. In these implementations, an AN 1508 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, etc. The ANs 1508 may be the same or similar as the xNBs and/or RAN nodes shown and described with respect to Figures 1-6.

One example implementation is a “CU/DU split” architecture where the ANs 1508 are embodied as a gNB-Central Unit (CU) that is communicatively coupled with one or more gNB- Distributed Units (DUs), where each DU may be communicatively coupled with one or more Radio Units (RUs) (also referred to as RRHs, RRUs, or the like) (see e.g., 3GPP TS 38.401 vl6.1.0 (2020-03)). In some implementations, the one or more RUs may be individual RSUs. In some implementations, the CU/DU split may include an ng-eNB-CU and one or more ng-eNB-DUs instead of, or in addition to, the gNB-CU and gNB-DUs, respectively. The ANs 1508 employed as the CU may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network including a virtual Base Band Unit (BBU) or BBU pool, cloud RAN (CRAN), Radio Equipment Controller (REC), Radio Cloud Center (RCC), centralized RAN (C-RAN), virtualized RAN (vRAN), and/or the like (although these terms may refer to different implementation concepts). Any other type of architectures, arrangements, and/or configurations can be used. The plurality of ANs may be coupled with one another via an X2 interface (if the RAN 1504 is an LTE RAN or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 1510) or an Xn interface (if the RAN 1504 is aNG-RAN 1514). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

The ANs of the RAN 1504 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1502 with an air interface for network access. The UE 1502 may be simultaneously connected with a plurality of cells provided by the same or different ANs 1508 of the RAN 1504. For example, the UE 1502 and RAN 1504 may use carrier aggregation to allow the UE 1502 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN 1508 may be a master node that provides an MCG and a second AN 1508 may be secondary node that provides an SCG. The first/second ANs 1508 may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 1504 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 1502 or AN 1508 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

In some embodiments, the RAN 1504 may be an E-UTRAN 1510 with one or more eNBs 1512. The an E-UTRAN 1510 provides an LTE air interface (Uu) with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 1504 may be a next generation (NG)-RAN 1514 with one or more gNB 1516 and/or on or more ng-eNB 1518. The gNB 1516 connects with 5G-enabled UEs 1502 using a 5G NR interface. The gNB 1516 connects with a 5GC 1540 through an NG interface, which includes an N2 interface or an N3 interface. The ng-eNB 1518 also connects with the 5GC 1540 through an NG interface, but may connect with a UE 1502 via the Uu interface. The gNB 1516 and the ng-eNB 1518 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 1514 and a UPF 1548 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 1514 and an AMF 1544 (e.g., N2 interface).

The NG-RAN 1514 may provide a 5G-NR air interface (which may also be referred to as a Uu interface) with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

The 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 1502 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1502, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 1502 with different amount of frequency resources (e.g., PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 1502 and in some cases at the gNB 1516. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 1504 is communicatively coupled to CN 1520 that includes network elements and/or network functions (NFs) to provide various functions to support data and telecommunications services to customers/subscribers (e.g., UE 1502). The components of the CN 1520 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 1520 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 1520 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1520 may be referred to as a network sub-slice.

The CN 1520 may be an LTE CN 1522 (also referred to as an Evolved Packet Core (EPC) 1522). The EPC 1522 may include MME 1524, SGW 1526, SGSN 1528, HSS 1530, PGW 1532, and PCRF 1534 coupled with one another over interfaces (or “reference points”) as shown. The NFs in the EPC 1522 are briefly introduced as follows.

The MME 1524 implements mobility management functions to track a current location of the UE 1502 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 1526 terminates an SI interface toward the RAN 1510 and routes data packets between the RAN 1510 and the EPC 1522. The SGW 1526 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The SGSN 1528 tracks a location of the UE 1502 and performs security functions and access control. The SGSN 1528 also performs inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 1524; MME 1524 selection for handovers; etc. The S3 reference point between the MME 1524 and the SGSN 1528 enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

The HSS 1530 includes a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 1530 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1530 and the MME 1524 may enable transfer of subscription and authentication data for authenti eating/ authorizing user access to the EPC 1520.

The PGW 1532 may terminate an SGi interface toward a data network (DN) 1536 that may include an application (app)/content server 1538. The PGW 1532 routes data packets between the EPC 1522 and the data network 1536. The PGW 1532 is communicatively coupled with the SGW 1526 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1532 may further include a node for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point may communicatively couple the PGW 1532 with the same or different data network 1536. The PGW 1532 may be communicatively coupled with a PCRF 1534 via a Gx reference point.

The PCRF 1534 is the policy and charging control element of the EPC 1522. The PCRF 1534 is communicatively coupled to the app/content server 1538 to determine appropriate QoS and charging parameters for service flows. The PCRF 1532 also provisions associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

The CN 1520 may be a 5GC 1540 including an AUSF 1542, AMF 1544, SMF 1546, UPF 1548, NSSF 1550, NEF 1552, NRF 1554, PCF 1556, UDM 1558, and AF 1560 coupled with one another over various interfaces as shown. The NFs in the 5GC 1540 are briefly introduced as follows.

The AUSF 1542 stores data for authentication of UE 1502 and handle authentication- related functionality. The AUSF 1542 may facilitate a common authentication framework for various access types.

The AMF 1544 allows other functions of the 5GC 1540 to communicate with the UE 1502 and the RAN 1504 and to subscribe to notifications about mobility events with respect to the UE 1502. The AMF 1544 is also responsible for registration management (e.g., for registering UE 1502), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 1544 provides transport for SM messages between the UE 1502 and the SMF 1546, and acts as a transparent proxy for routing SM messages. AMF 1544 also provides transport for SMS messages between UE 1502 and an SMSF. AMF 1544 interacts with the AUSF 1542 and the UE 1502 to perform various security anchor and context management functions. Furthermore, AMF 1544 is a termination point of a RAN-CP interface, which includes the N2 reference point between the RAN 1504 and the AMF 1544. The AMF 1544 is also a termination point of NAS (Nl) signaling, and performs NAS ciphering and integrity protection.

AMF 1544 also supports NAS signaling with the UE 1502 over an N3IWF interface. The N3IWF provides access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN 1504 and the AMF 1544 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 1514 and the 1548 for the user plane. As such, the AMF 1544 handles N2 signalling from the SMF 1546 and the AMF 1544 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, marks N3 user-plane packets in the uplink, and enforces QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. N3IWF may also relay UL and DL control-plane NAS signalling between the UE 1502 and AMF 1544 via an Nl reference point between the UE 1502and the AMF 1544, and relay uplink and downlink user- plane packets between the UE 1502 and UPF 1548. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 1502. The AMF 1544 may exhibit an Namf service-based interface, and may be a termination point for an N 14 reference point between two AMF s 1544 and an N17 reference point between the AMF 1544 and a 5G-EIR (not shown by Figurel5).

The SMF 1546 is responsible for SM (e.g., session establishment, tunnel management between UPF 1548 and AN 1508); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 1548 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 1544 over N2 to AN 1508; and determining SSC mode of a session. SM refers to management of a PDU session, and a PDU session or “session” refers to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 1502 and the DN 1536.

The UPF 1548 acts as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1536, and a branching point to support multi homed PDU session. The UPF 1548 also performs packet routing and forwarding, packet inspection, enforces user plane part of policy rules, lawfully intercept packets (UP collection), performs traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and performs downlink packet buffering and downlink data notification triggering. UPF 1548 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 1550 selects a set of network slice instances serving the UE 1502. The NSSF 1550 also determines allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 1550 also determines an AMF set to be used to serve the UE 1502, or a list of candidate AMFs 1544 based on a suitable configuration and possibly by querying the NRF 1554. The selection of a set of network slice instances for the UE 1502 may be triggered by the AMF 1544 with which the UE 1502 is registered by interacting with the NSSF 1550; this may lead to a change of AMF 1544. The NSSF 1550 interacts with the AMF 1544 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown).

The NEF 1552 securely exposes services and capabilities provided by 3GPP NFs for third party, internal exposure/re-exposure, AFs 1560, edge computing or fog computing systems (e.g., edge compute node 1536x, etc. In such embodiments, the NEF 1552 may authenticate, authorize, or throttle the AFs. NEF 1552 may also translate information exchanged with the AF 1560 and information exchanged with internal network functions. For example, the NEF 1552 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 1552 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 1552 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1552 to other NFs and AFs, or used for other purposes such as analytics.

TheNRF 1554 supports service discovery functions, receives NF discovery requests from NF instances, and provides information of the discovered NF instances to the requesting NF instances. NRF 1554 also maintains information of available NF instances and their supported services. TheNRF 1554 also supports service discovery functions, wherein the NRF 1554 receives NF Discovery Request fromNF instance or an SCP (not shown), and provides information of the discovered NF instances to the NF instance or SCP.

The PCF 1556 provides policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 1556 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 1558. In addition to communicating with functions over reference points as shown, the PCF 1556 exhibit an Npcf service-based interface.

The UDM 1558 handles subscription-related information to support the network entities’ handling of communication sessions, and stores subscription data of UE 1502. For example, subscription data may be communicated via an N8 reference point between the UDM 1558 and the AMF 1544. The UDM 1558 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 1558 and the PCF 1556, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1502) for the NEF 1552. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 1558, PCF 1556, and NEF 1552 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 1558 may exhibit the Nudm service-based interface.

AF 1560 provides application influence on traffic routing, provide access to NEF 1552, and interact with the policy framework for policy control. The AF 1560 may influence UPF 1548 (re)selection and traffic routing. Based on operator deployment, when AF 1560 is considered to be a trusted entity, the network operator may permit AF 1560 to interact directly with relevant NFs. Additionally, the AF 1560 may be used for edge computing implementations,

The 5GC 1540 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 1502 is attached to the network. This may reduce latency and load on the network. In edge computing implementations, the 5GC 1540 may select a UPF 1548 close to the UE 1502 and execute traffic steering from the UPF 1548 to DN 1536 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1560, which allows the AF 1560 to influence UPF (re)selection and traffic routing.

The data network (DN) 1536 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application (app)/content server 1538. The DN 1536 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. In this embodiment, the server 1538 can be coupled to an IMS via an S-CSCF or the I-CSCF. In some implementations, the DN 1536 may represent one or more local area DNs (LADNs), which are DNs 1536 (or DN names (DNNs)) that is/are accessible by a UE 1502 in one or more specific areas. Outside of these specific areas, the UE 1502 is not able to access the LADN/DN 1536.

Additionally or alternatively, the DN 1536 may be an Edge DN 1536, which is a (local) Data Network that supports the architecture for enabling edge applications. In these embodiments, the app server 1538 may represent the physical hardware systems/devices providing app server functionality and/or the application software resident in the cloud or at an edge compute node that performs server function(s). In some embodiments, the app/ content server 1538 provides an edge hosting environment that provides support required for Edge Application Server's execution. In some implementations, the DN 1536 may be, or include, one or more edge compute nodes, which may be the same or similar to the edge compute nodes such as those discussed herein.

In some embodiments, the 5GS can use one or more edge compute nodes to provide an interface and offload processing of wireless communication traffic. In these embodiments, the edge compute nodes may be included in, or co-located with one or more RAN 1510, 1514. For example, the edge compute nodes can provide a connection between the RAN 1514 and UPF 1548 in the 5GC 1540. The edge compute nodes can use one or more NFV instances instantiated on virtualization infrastructure within the edge compute nodes to process wireless connections to and from the RAN 1514 and UPF 1548.

These embodiments may be implemented using a variety of edge computing/networking technologies in various combinations and layouts of devices located at the edge of a network. Examples of such edge computing/networking technologies that may implement the embodiments herein include Multi-Access Edge Computing (MEC); Content Delivery Networks (CDNs) (also referred to as “Content Distribution Networks” or the like); Mobility Service Provider (MSP) edge computing and/or Mobility as a Service (MaaS) provider systems (e.g., used in AECC architectures); Nebula edge-cloud systems; Fog computing systems; Cloudlet edge-cloud systems; Mobile Cloud Computing (MCC) systems; Central Office Re-architected as a Datacenter (CORD), mobile CORD (M-CORD) and/or Converged Multi-Access and Core (COMAC) systems; and/or the like. Further, the techniques disclosed herein may relate to other IoT edge network systems and configurations, and other intermediate processing entities and architectures may also be used to practice the embodiments herein.

The interfaces of the 5GC 1540 include reference points and service-based itnterfaces. The reference points include: N1 (between the UE 1502 and the AMF 1544), N2 (between RAN 1514 and AMF 1544), N3 (between RAN 1514 and UPF 1548), N4 (between the SMF 1546 and UPF 1548), N5 (between PCF 1556 and AF 1560), N6 (between UPF 1548 and DN 1536), N7 (between SMF 1546 and PCF 1556), N8 (between UDM 1558 and AMF 1544), N9 (between two UPFs 1548), N10 (between the UDM 1558 and the SMF 1546), Nil (between the AMF 1544 and the SMF 1546), N12 (between AUSF 1542 and AMF 1544), N13 (between AUSF 1542 and UDM 1558), N14 (between two AMFs 1544; not shown), N15 (between PCF 1556 and AMF 1544 in case of a non-roaming scenario, or between the PCF 1556 in a visited network and AMF 1544 in case of a roaming scenario), N16 (between two SMFs 1546; not shown), and N22 (between AMF 1544 and NSSF 1550). Other reference point representations not shown in Figure 15can also be used. The service-based representation of Figure 15represents NFs within the control plane that enable other authorized NFs to access their services. The service-based interfaces (SBIs) include: Narnf (SBI exhibited by AMF 1544), Nsrnf (SBI exhibited by SMF 1546), Nnef (SBI exhibited by NEF 1552), Npcf (SBI exhibited by PCF 1556), Nudm (SBI exhibited by the UDM 1558), Naf (SBI exhibited by AF 1560), Nnrf (SBI exhibited by NRF 1554), Nnssf (SBI exhibited by NSSF 1550), Nausf (SBI exhibited by AUSF 1542). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsl) not shown in Figure 15 can also be used. In some embodiments, the NEF 1552 can provide an interface to edge compute nodes 1536x, which can be used to process wireless connections with the RAN 1514.

As discussed previously, the system 1500 may include an SMSF, which is responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 1502 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 1542 and UDM 1558 for a notification procedure that the UE 1502 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 1558 when UE 1502 is available for SMS).

The 5GS may also include an SCP (or individual instances of the SCP) that supports indirect communication (see e.g., 3GPP TS 23.501 section 7.1.1); delegated discovery (see e.g., 3GPP TS 23.501 section 7.1.1); message forwarding and routing to destination NF/NF service(s), communication security (e.g., authorization of the NF Service Consumer to access the NF Service Producer API) (see e.g., 3GPP TS 33.501), load balancing, monitoring, overload control, etc.; and discovery and selection functionality for UDM(s), AUSF(s), UDR(s), PCF(s) with access to subscription data stored in the UDR based on UE's SUPI, SUCI or GPSI (see e.g., 3GPPTS 23.501 section 6.3). Load balancing, monitoring, overload control functionality provided by the SCP may be implementation specific. The SCP may be deployed in a distributed manner. More than one SCP can be present in the communication path between various NF Services. The SCP, although not an NF instance, can also be deployed distributed, redundant, and scalable.

Figure 16 schematically illustrates a wireless network 1600 in accordance with various embodiments. The wireless network 1600 may include a UE 1602 in wireless communication with an AN 1604. The UE 1602 and AN 1604 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 1602 may be communicatively coupled with the AN 1604 via connection 1606. The connection 1606 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 1602 may include a host platform 1608 coupled with a modem platform 1610. The host platform 1608 may include application processing circuitry 1612, which may be coupled with protocol processing circuitry 1614 of the modem platform 1610. The application processing circuitry 1612 may run various applications for the UE 1602 that source/sink application data. The application processing circuitry 1612 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

The protocol processing circuitry 1614 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1606. The layer operations implemented by the protocol processing circuitry 1614 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 1610 may further include digital baseband circuitry 1616 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1614 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 1610 may further include transmit circuitry 1618, receive circuitry 1620, RF circuitry 1622, and RF front end (RFFE) 1624, which may include or connect to one or more antenna panels 1626. Briefly, the transmit circuitry 1618 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 1620 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 1622 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 1624 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 1618, receive circuitry 1620, RF circuitry 1622, RFFE 1624, and antenna panels 1626 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 1614 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 1626, RFFE 1624, RF circuitry 1622, receive circuitry 1620, digital baseband circuitry 1616, and protocol processing circuitry 1614. In some embodiments, the antenna panels 1626 may receive a transmission from the AN 1604 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1626.

A UE transmission may be established by and via the protocol processing circuitry 1614, digital baseband circuitry 1616, transmit circuitry 1618, RF circuitry 1622, RFFE 1624, and antenna panels 1626. In some embodiments, the transmit components of the UE 1604 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 1626.

Similar to the UE 1602, the AN 1604 may include a host platform 1628 coupled with a modem platform 1630. The host platform 1628 may include application processing circuitry 1632 coupled with protocol processing circuitry 1634 of the modem platform 1630. The modem platform may further include digital baseband circuitry 1636, transmit circuitry 1638, receive circuitry 1640, RF circuitry 1642, RFFE circuitry 1644, and antenna panels 1646. The components of the AN 1604 may be similar to and substantially interchangeable with like-named components of the UE 1602. In addition to performing data transmission/reception as described above, the components of the AN 1608 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Figure 17 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 17 shows a diagrammatic representation of hardware resources 1700 including one or more processors (or processor cores) 1710, one or more memory /storage devices 1720, and one or more communication resources 1730, each of which may be communicatively coupled via a bus 1740 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1702 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1700.

The processors 1710 may include, for example, a processor 1712 and a processor 1714. The processors 1710 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio- frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory /storage devices 1720 may include main memory, disk storage, or any suitable combination thereof. The memory /storage devices 1720 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 1730 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1704 or one or more databases 1706 or other network elements via a network 1708. For example, the communication resources 1730 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 1750 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1710 to perform any one or more of the methodologies discussed herein. The instructions 1750 may reside, completely or partially, within at least one of the processors 1710 (e.g., within the processor’s cache memory), the memory /storage devices 1720, or any suitable combination thereof. Furthermore, any portion of the instructions 1750 may be transferred to the hardware resources 1700 from any combination of the peripheral devices 1704 or the databases 1706. Accordingly, the memory of processors 1710, the memory/storage devices 1720, the peripheral devices 1704, and the databases 1706 are examples of computer-readable and machine-readable media.

EXAMPLE PROCEDURES

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 15-17, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.

One such process is depicted in Figure 18. For example, the process 1800 may include, at 1805, sending a radio access network (RAN) compute session establishment request to a computing control function (Comp CF), the RAN compute session establishment request including an indication of remote direct memory access (RDMA) requirements. The process further includes, at 1810, receiving from the Comp CF, a RAN compute session establishment response that is to accept a compute session with RDMA support, wherein the RAN compute session establishment response includes an indication of a queue pair (QP) identifier and a QP key.

Figure 19 illustrates another process in accordance with various embodiments. In this example, the process 1900 includes, at 1905, receiving, from a computing control function (Comp CF), a RAN compute session modification request that includes an indication of: remote direct memory access (RDMA) requirements, a queue pair (QP) identifier, and a QP key. The process further includes, at 1910, in response to receiving the RAN compute session modification request, encoding a radio resource control (RRC) reconfiguration message for transmission to a user equipment (UE), the RRC reconfiguration message including an indication of the RDMA requirements, the QP identifier, and the QP key.

Figure 20 illustrates another process in accordance with various embodiments. In this example, the process 2000 includes, at 2005, encoding a radio resource control (RRC) radio access network (RAN) compute setup request for transmission to a next-generation NodeB (gNB), the RRC RAN compute setup request including an RDMA indicator or RDMA requirements. The process further includes, at 1210, receiving, from the gNB, an RRC reconfiguration message that includes: an indication to set up a radio bearer for computing, or an indication of a queue pair (QP) identifier and a QP key.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

EXAMPLES

Example A01 includes RDMA related information including: RDMA protocol type such as RoCNvl, RoCNv2, iWARP-CN, version; RDMA configurations such as packet interval, initial data rate, etc.; RDMA device type, manufacturer, such as the RDMA network interface card (RNIC) type and manufacturer; Number of QPs and type; Number of keys and type; and/or Requirements on memory such as size, type, maximum occupancy.

Example A02 includes a method of RDMA capability exchange between Comp CSF and Comp CF and/or between Comp RF-C and Comp RF-S. Example A02 may be combined with example A01.

Example A03 includes a method of exchanging RDMA related information between a UE and RAN/network functions. Example A03 may be combined with examples A01-A02.

Example A04 includes the method of example A03 and/or some other example(s) herein, wherein the RDMA related information is carried inside a new container for Comp CF or the NAS container; in this case, it is transparently passed by the xNB to Comp CF or other network functions. This new container or NAS constainer can be piggyback in RRC message.

Example A05 includes the method of example A03 and/or some other example(s) herein, wherein the RDMA related information is carried inside RRC message; in this case, xNB needs to relay this to Comp CF.

Example A06 includes the method of example A03 and/or some other example(s) herein, wherein the RDMA related information is carried inside a new L3 container for Non-Access Stratum (NAS) eschange between the UE and CN node.

Example A07 includes a method of QP and key information exchange for embodiment 1 via control plane initiated by UE or Comp CF to include the RDMA requirements, QP, key info in the RAN compute set up request/response. Example A07 may be combined with examples A01- A06.

Example A08 includes a method of QP and key information exchange for embodiment 1 via user plane initiated by UE or Comp CF to include the RDMA requirements, QP, key info in the RDMA CM traffic using the compute transport. Example A08 may be combined with examples A01-A07.

Example A09 includes a method of QP and key information exchange for embodiment 2 via control plane initiated by UE or RAN DU/CU to include the RDMA requirements, QP, key info in L2/L3 message between UE and RAN DU/CU. Example A09 may be combined with examples A01-A08.

Example A10 includes a method of QP and key information exchange for embodiment 2 via user plane initiated by UE or initiated by RAN DU/CU to include the RDMA requirements, QP, key info via radio bearer or other messages as detailed in Figure 12 and/or Figure 13. Example A10 may be combined with examples A01-A09.

Example A11 includes a method of mapping between QP ID and key information and existing cellular network identifiers/services, wherein: a Task ID can be used to identify a RDMA profile which includes the RDMA requirements and information; S-NSSAI can be used as P key; and/or a Q key can be used to enable parallel computing for applications such as OpenCL, OpenGL, CUD A, etc.

Example A12 includes a method to provide a framework and available IEs to allow multiple methods of RDMA like technologies to work.

Example A13 includes the method of example A12 and/or some other example(s) herein, wherein a generic framework providers compute and memory transfer protocol.

Example A14 includes the method of example A13 and/or some other example(s) herein, wherein Information elements can be used to define the type of protocol, type of direct memory transfer methods

Example A15 includes the method of example A13 and/or some other example(s) herein, wherein a common sublayer PDU type is defined.

Example A16 may include the method of example A14 and/or some other example(s) herein, wherein extensions to provide QoS information, congestion control information can be incorporated and transferred to another entity.

Example B01 includes a Remote Direct Memory Access (RDMA) method for compute scaling between a user equipment (UE) and a cellular network, the method comprising: performing a RDMA capability exchange; and setting up Queue Pairs (QPs) and keys to enable data exchange through RDM A for the compute scaling.

Example B02 includes the method of example B01 and/or some other example(s) herein, wherein performing the RDMA capability exchange comprises indicating whether RDMA is supported and/or providing a set of RDMA related information.

Example B03 includes the method of example B02 and/or some other example(s) herein, wherein the indication of RDMA support and/or the set of RDMA related information is carried inside a computing control function (Comp CF) container, a Non-Access Stratum (NAS) container, or in a Radio Resource Control (RRC) information element (IE)/message.

Example B04 includes the method of examples B01-B03 and/or some other example(s) herein, further comprising: sending, to a RAN node, an RRC Radio Access Network (RAN) compute setup request with an RDMA indication and/or the RDMA related information; sending, to a Comp CF, a RAN compute session establishment request including the RDMA indication and/or the RDMA related information, wherein if the Comp CF accepts the compute task, a Comp SF with required RDMA support is selected, the Comp CF sets up the compute task and also requests to create required QPs with the RDMA related information received, and the QP IDs and keys information is sent back to the Comp CF; and receiving the RDMA QP IDs and keys using RRC reconfiguration message.

Example B05 includes the method of examples B01-B03 and/or some other example(s) herein, further comprising: determining to set up RDMA with the UE; requesting to set up QPs and generate keys with an assigned Comp SF; sending a RAN Compute session modification request message with the RDMA requirements and the generated QP ID and keys to a RAN node, wherein an RRC Reconfiguration message is sent to the UE with the RDMA requirements, QP IDs, and keys, and the UE sends the RRC Reconfiguration complete once the RDMA QP and keys are properly created and stored on UE.

Example B06 includes the method of examples B01-B03 and/or some other example(s) herein, further comprising: sending, to the Comp RF-S in RAN DU or CU, a request for RDMA access through a Comp RF-C, the request including the RDMA related information; and receiving, from the RAN DU/CU, an accept message indicating acceptance of a compute task and including related QPs and keys.

Example B07 includes the method of examples B01-B03 and/or some other example(s) herein, further comprising: determining, by a Comp RF-S in a RAN DU or CU, to set up RDMA with the UE; generating QP and key information based on UE capabilities; sending, to the UE, a message with RDMA requirements, the QP and key information for setting up RDMA; and receiving, from the UE, a confirmation message confirming that the RDMA information is accepted. Example B08 includes the method of examples B01-B07 and/or some other example(s) herein, wherein the RDMA related information includes onr or more of RDMA protocol type, RDMA version, RDMA configuration information, RDMA device type, RDMA device manufacturer, a number of QPs, supported QP types, a number of keys, supported key types, memory requirements, memory capabilities, and/or an RDMA indicator indicating that the RDMA is a chosen transport for computing and/or data service.

Example B09 includes the method of examples B01-B08 and/or some other example(s) herein, wherein the method is combined with any one of examples A01-A16.

Example XI includes an apparatus of a next-generation NodeB (gNB) comprising: memory to store remote direct memory access (RDMA) requirements received from a user equipment (UE); and processing circuitry, coupled with the memory, to: send a radio access network (RAN) compute session establishment request to a computing control function (Comp CF), the RAN compute session establishment request including an indication of the RDMA requirements; and receive, from the Comp CF, a RAN compute session establishment response that is to accept a compute session with RDMA support, wherein the RAN compute session establishment response includes an indication of a queue pair (QP) identifier and a QP key.

Example X2 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to encode a radio resource control (RRC) reconfiguration message for transmission to the UE, the RRC reconfiguration message including an indication of the QP identifier and the QP key.

Example X3 includes the apparatus of example XI or some other example herein, wherein the RDMA requirements include an RDMA protocol type, an RDMA configuration, an RDMA device type, a memory requirement, or an RDMA indicator that is to indicate RDMA is a chosen transport for a computing or data service.

Example X4 includes the apparatus of example XI or some other example herein, wherein RAN compute session establishment response includes an indication of a plurality of QP identifiers and a plurality of QP keys.

Example X5 includes the apparatus of example X4 or some other example herein, wherein the RDMA requirements include a number of QPs and QP types, and a number of QP keys and QP key types. Example X6 includes the apparatus of any of examples X1-X5 or some other example herein, wherein the RDMA requirements are received from the UE via an RRC RAN compute setup request.

Example X7 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a next-generation NodeB (gNB) to: receive, from a computing control function (Comp CF), a RAN compute session modification request that includes an indication of: remote direct memory access (RDMA) requirements, a queue pair (QP) identifier, and a QP key; and in response to receiving the RAN compute session modification request, encode a radio resource control (RRC) reconfiguration message for transmission to a user equipment (UE), the RRC reconfiguration message including an indication of the RDMA requirements, the QP identifier, and the QP key.

Example X8 includes the one or more computer-readable media of example X7 or some other example herein, wherein the media further stores instructions to cause the gNB to receive, from the UE, an RRC reconfiguration complete message that is to indicate the QP is created and stored on the UE.

Example X9 includes the one or more computer-readable media of example X7 or some other example herein, wherein the RDMA requirements include an RDMA protocol type, an RDMA configuration, an RDMA device type, a memory requirement, or an RDMA indicator that is to indicate RDMA is a chosen transport for a computing or data service.

Example XI 0 includes the one or more computer-readable media of example X7 or some other example herein, wherein RAN compute session establishment response includes an indication of a plurality of QP identifiers and a plurality of QP keys.

Example XI 1 includes the one or more computer-readable media of example XI 0 or some other example herein, wherein the RDMA requirements include a number of QPs and QP types, and a number of QP keys and QP key types.

Example XI 2 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: encode a radio resource control (RRC) radio access network (RAN) compute setup request for transmission to a next-generation NodeB (gNB), the RRC RAN compute setup request including an RDMA indicator or RDMA requirements; and receive, from the gNB, an RRC reconfiguration message that includes: an indication to set up a radio bearer for computing, or an indication of a queue pair (QP) identifier and a QP key. Example XI 3 includes the one or more computer-readable media of example XI 2 or some other example herein, wherein the media further stores instructions to cause the UE to create a QP based on the RRC reconfiguration message.

Example XI 4 includes the one or more computer-readable media of example XI 3 or some other example herein, wherein the media further stores instructions to cause the UE to encode an RRC reconfiguration complete message for transmission to the gNB to indicate the QP has been created.

Example XI 5 includes the one or more computer-readable media of example XI 2 or some other example herein, wherein the RRC reconfiguration message includes an indication to set up a radio bearer for computing, and wherein the media further stores instructions to cause the UE to configure a radio bearer based on the RRC reconfiguration message.

Example XI 6 includes the one or more computer-readable media of example XI 5 or some other example herein, wherein the RRC reconfiguration message comprises radio bearer configuration information for RDMA connection management (CM) traffic.

Example XI 7 includes the one or more computer-readable media of example XI 5 or some other example herein, wherein the media further stores instructions to cause the UE to encode an RRC reconfiguration complete message for transmission to the gNB to indicate the radio bearer is ready.

Example XI 8 includes the one or more computer-readable media of example XI 2 or some other example herein, wherein the media further stores instructions to cause the UE to send a request for QPs and QP keys to a computing service function (Comp SF).

Example XI 9 includes the one or more computer-readable media of example XI 8 or some other example herein, wherein the media further stores instructions to cause the UE to receive the QPs and QP keys from the Comp SF via a user plane communication.

Example X20 includes the one or more computer-readable media of example XI 2 or some other example herein, wherein the RDMA requirements include an RDMA protocol type, an RDMA configuration, an RDMA device type, a memory requirement, or an RDMA indicator that is to indicate RDMA is a chosen transport for a computing or data service.

Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples A01-A16, B01-B09, X1-X20, or any other method or process described herein.

Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples A01-A16, B01-B09, Xl-X20,or any other method or process described herein.

Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples AO 1 -A 16, B01-B09, Xl-X20,or any other method or process described herein.

Example Z04 may include a method, technique, or process as described in or related to any of examples A01-A16, B01-B09, Xl-X20,or portions or parts thereof.

Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples A01-A16, B01-B09, Xl-X20,or portions thereof.

Example Z06 may include a signal as described in or related to any of examples A01-A16, B01-B09, Xl-X20,or portions or parts thereof.

Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A01-A16, B01-B09, Xl-X20,or portions or parts thereof, or otherwise described in the present disclosure.

Example Z08 may include a signal encoded with data as described in or related to any of examples A01-A16, B01-B09, Xl-X20,or portions or parts thereof, or otherwise described in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A01-A16, B01- B09, Xl-X20,or portions or parts thereof, or otherwise described in the present disclosure.

Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples A01-A16, B01-B09, Xl-X20,or portions thereof.

Example Zll may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples A01-A16, B01- B09, Xl-X20,or portions thereof.

Example Z12 may include a signal in a wireless network as shown and described herein.

Example Z13 may include a method of communicating in a wireless network as shown and described herein.

Example Z14 may include a system for providing wireless communication as shown and described herein. Example Z15 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

TERMINOLOGY

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a,” “an” and “the” are intended to include plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specific the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operation, elements, components, and/or groups thereof.

For the purposes of the present disclosure, the phrase “A and/or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C). The description may use the phrases “in an embodiment,” or “In some embodiments,” which may each refer to one or more of the same or different embodiments. Furthermore, the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or ink, and/or the like.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field- programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “memory” and/or “memory circuitry” as used herein refers to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM, and/or SDRAM, core memory, ROM, magnetic disk storage mediums, optical storage mediums, flash memory devices or other machine readable mediums for storing data. The term “computer-readable medium” may include, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instructions or data.

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource. The term “element” refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary, wherein an element may be any type of entity including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof. The term “device” refers to a physical entity embedded inside, or attached to, another physical entity in its vicinity, with capabilities to convey digital information from or to that physical entity. The term “entity” refers to a distinct component of an architecture or device, or information transferred as a payload. The term “controller” refers to an element or entity that has the capability to affect a physical entity, such as by changing its state or causing the physical entity to move.

The term “cloud computing” or “cloud” refers to a paradigm for enabling network access to a scalable and elastic pool of shareable computing resources with self-service provisioning and administration on-demand and without active management by users. Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities offered via cloud computing that are invoked using a defined interface (e.g., an API or the like). The term “computing resource” or simply “resource” refers to any physical or virtual component, or usage of such components, of limited availability within a computer system or network. Examples of computing resources include usage/access to, for a period of time, servers, processor(s), storage equipment, memory devices, memory areas, networks, electrical power, input/output (peripheral) devices, mechanical devices, network connections (e.g., channels/links, ports, network sockets, etc.), operating systems, virtual machines (VMs), software/applications, computer files, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/sy stems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable. As used herein, the term “cloud service provider” (or CSP) indicates an organization which operates typically large-scale “cloud” resources comprised of centralized, regional, and edge data centers (e.g., as used in the context of the public cloud). In other examples, a CSP may also be referred to as a Cloud Service Operator (CSO). References to “cloud computing” generally refer to computing resources and services offered by a CSP or a CSO, at remote locations with at least some increased latency, distance, or constraints relative to edge computing.

As used herein, the term “data center” refers to a purpose-designed structure that is intended to house multiple high-performance compute and data storage nodes such that a large amount of compute, data storage and network resources are present at a single location. This often entails specialized rack and enclosure systems, suitable heating, cooling, ventilation, security, fire suppression, and power delivery systems. The term may also refer to a compute and data storage node in some contexts. A data center may vary in scale between a centralized or cloud data center (e.g., largest), regional data center, and edge data center (e.g., smallest).

As used herein, the term “edge computing” refers to the implementation, coordination, and use of computing and resources at locations closer to the “edge” or collection of “edges” of a network. Deploying computing resources at the network’s edge may reduce application and network latency, reduce network backhaul traffic and associated energy consumption, improve service capabilities, improve compliance with security or data privacy requirements (especially as compared to conventional cloud computing), and improve total cost of ownership). As used herein, the term “edge compute node” refers to a real-world, logical, or virtualized implementation of a compute-capable element in the form of a device, gateway, bridge, system or subsystem, component, whether operating in a server, client, endpoint, or peer mode, and whether located at an “edge” of an network or at a connected location further within the network. References to a “node” used herein are generally interchangeable with a “device”, “component”, and “sub system”; however, references to an “edge computing system” or “edge computing network” generally refer to a distributed architecture, organization, or collection of multiple nodes and devices, and which is organized to accomplish or offer some aspect of services or resources in an edge computing setting.

Additionally or alternatively, the term “Edge Computing” refers to a concept, as described in [6], that enables operator and 3rd party services to be hosted close to the UE's access point of attachment, to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. As used herein, the term “Edge Computing Service Provider” refers to a mobile network operator or a 3rd party service provider offering Edge Computing service. As used herein, the term “Edge Data Network” refers to a local Data Network (DN) that supports the architecture for enabling edge applications. As used herein, the term “Edge Hosting Environment” refers to an environment providing support required for Edge Application Server's execution. As used herein, the term “Application Server” refers to application software resident in the cloud performing the server function.

The term “Internet of Things” or “IoT” refers to a system of interrelated computing devices, mechanical and digital machines capable of transferring data with little or no human interaction, and may involve technologies such as real-time analytics, machine learning and/or AI, embedded systems, wireless sensor networks, control systems, automation (e.g., smarthome, smart building and/or smart city technologies), and the like. IoT devices are usually low-power devices without heavy compute or storage capabilities. “Edge IoT devices” may be any kind of IoT devices deployed at a network’s edge.

As used herein, the term “cluster” refers to a set or grouping of entities as part of an edge computing system (or systems), in the form of physical entities (e.g., different computing systems, networks or network groups), logical entities (e.g., applications, functions, security constructs, containers), and the like. In some locations, a “cluster” is also referred to as a “group” or a “domain”. The membership of cluster may be modified or affected based on conditions or functions, including from dynamic or property-based membership, from network or system management scenarios, or from various example techniques discussed below which may add, modify, or remove an entity in a cluster. Clusters may also include or be associated with multiple layers, levels, or properties, including variations in security features and results based on such layers, levels, or properties.

The term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment. The term “AI/ML application” or the like may be an application that contains some AI/ML models and application-level descriptions. The term “machine learning” or “ML” refers to the use of computer systems implementing algorithms and/or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences. ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets. Although the term “ML algorithm” refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.

The term “machine learning model,” “ML model,” or the like may also refer to ML methods and concepts used by an ML-assisted solution. An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-leaming, multi-armed bandit learning, deep RL, etc.), neural networks, and the like. Depending on the implementation a specific ML model could have many sub-models as components and the ML model may train all sub-models together. Separately trained ML models can also be chained together in an ML pipeline during inference. An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. The “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference). The term “ML training host” refers to an entity, such as a network function, that hosts the training of the model. The term “ML inference host” refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable). The ML-host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution). The term “model inference information” refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code. The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. As used herein, a “database object”, “data structure”, or the like may refer to any representation of information that is in the form of an object, attribute-value pair (AVP), key-value pair (KVP), tuple, etc., and may include variables, data structures, functions, methods, classes, database records, database fields, database entities, associations between data and/or database entities (also referred to as a “relation”), blocks and links between blocks in block chain implementations, and/or the like.

An “information object,” as used herein, refers to a collection of structured data and/or any representation of information, and may include, for example electronic documents (or “documents”), database objects, data structures, files, audio data, video data, raw data, archive files, application packages, and/or any other like representation of information. The terms “electronic document” or “document,” may refer to a data structure, computer file, or resource used to record data, and includes various file types and/or data formats such as word processing documents, spreadsheets, slide presentations, multimedia items, webpage and/or source code documents, and/or the like. As examples, the information objects may include markup and/or source code documents such as HTML, XML, JSON, Apex®, CSS, JSP, MessagePack™, Apache® Thrift™, ASN.l, Google® Protocol Buffers (protobuf), or some other document(s)/format(s) such as those discussed herein. An information object may have both a logical and a physical structure. Physically, an information object comprises one or more units called entities. An entity is a unit of storage that contains content and is identified by a name. An entity may refer to other entities to cause their inclusion in the information object. An information object begins in a document entity, which is also referred to as a root element (or "root"). Logically, an information object comprises one or more declarations, elements, comments, character references, and processing instructions, all of which are indicated in the information object (e.g., using markup).

The term “data item” as used herein refers to an atomic state of a particular object with at least one specific property at a certain point in time. Such an object is usually identified by an object name or object identifier, and properties of such an object are usually defined as database objects (e.g., fields, records, etc.), object instances, or data elements (e.g., mark-up language elements/tags, etc.). Additionally or alternatively, the term “data item” as used herein may refer to data elements and/or content items, although these terms may refer to difference concepts. The term “data element” or “element” as used herein refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary. A data element is a logical component of an information object (e.g., electronic document) that may begin with a start tag (e.g., “<element>”) and end with a matching end tag (e.g., “</element>”), or only has an empty element tag (e.g., “<element />”). Any characters between the start tag and end tag, if any, are the element’s content (referred to herein as “content items” or the like).

The content of an entity may include one or more content items, each of which has an associated datatype representation. A content item may include, for example, attribute values, character values, URIs, qualified names (qnames), parameters, and the like. A qname is a fully qualified name of an element, attribute, or identifier in an information object. A qname associates a URI of a namespace with a local name of an element, attribute, or identifier in that namespace. To make this association, the qname assigns a prefix to the local name that corresponds to its namespace. The qname comprises a URI of the namespace, the prefix, and the local name. Namespaces are used to provide uniquely named elements and attributes in information objects. Content items may include text content (e.g., “<element>content item</element>”), attributes (e.g., “<element attribute-' attributeValue">”), and other elements referred to as “child elements” (e.g., “<elementl><element2>content item</element2></elementl>”). An “attribute” may refer to a markup construct including a name-value pair that exists within a start tag or empty element tag. Attributes contain data related to its element and/or control the element’s behavior.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information. As used herein, the term “radio technology” refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer. The term “radio access technology” or “RAT” refers to the technology used for the underlying physical connection to a radio based communication network. As used herein, the term “communication protocol” (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.

As used herein, the term “radio technology” refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer. The term “radio access technology” or “RAT” refers to the technology used for the underlying physical connection to a radio based communication network. As used herein, the term “communication protocol” (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like. Examples of wireless communications protocols may be used in various embodiments include a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology including, for example, 3GPP Fifth Generation (5G) or New Radio (NR), Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), Long Term Evolution (LTE), LTE- Advanced (LTE Advanced), LTE Extra, LTE-A Pro, cdmaOne (2G), Code Division Multiple Access 2000 (CDMA 2000), Cellular Digital Packet Data (CDPD), Mobitex, Circuit Switched Data (CSD), High-Speed CSD (HSCSD), Universal Mobile Telecommunications System (UMTS), Wideband Code Division Multiple Access (W-CDM), High Speed Packet Access (HSPA), HSPA Plus (HSPA+), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Synchronous Code Division Multiple Access (TD- SCDMA), LTE LAA, MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UTRA (E- UTRA), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (AMPS), Digital AMPS (D-AMPS), Total Access Communication System/Extended Total Access Communication System (TACS/ETACS), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), Cellular Digital Packet Data (CDPD), DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Personal Handy-phone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3GPP Generic Access Network, or GAN standard), Bluetooth®, Bluetooth Low Energy (BLE), IEEE 802.15.4 based protocols (e.g., IPv6 over Low power Wireless Personal Area Networks (6L0WPAN), WirelessHART, MiWi, Thread, 802.11a, etc.) WiFi-direct, ANT/ANT+, ZigBee, Z-Wave, 3GPP device-to-device (D2D) or Proximity Services (ProSe), Universal Plug and Play (UPnP), Low-Power Wide- Area-Network (LPWAN), Long Range Wide Area Network (LoRA) or LoRaWAN™ developed by Semtech and the LoRa Alliance, Sigfox, Wireless Gigabit Alliance (WiGig) standard, Worldwide Interoperability for Microwave Access (WiMAX), mmWave standards in general (e.g., wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. llad, IEEE 802.1 lay, etc.), V2X communication technologies (including 3GPP C-V2X), Dedicated Short Range Communications (DSRC) communication systems such as Intelligent-Transport-Systems (ITS) including the European ITS-G5, ITS-G5B, ITS-G5C, etc. In addition to the standards listed above, any number of satellite uplink technologies may be used for purposes of the present disclosure including, for example, radios compliant with standards issued by the International Telecommunication Union (ITU), or the European Telecommunications Standards Institute (ETSI), among others. The examples provided herein are thus understood as being applicable to various other communication technologies, both existing and not yet formulated.

The term “access network” refers to any network, using any combination of radio technologies, RATs, and/or communication protocols, used to connect user devices and service providers. In the context of WLANs, an “access network” is an IEEE 802 local area network (LAN) or metropolitan area network (MAN) between terminals and access routers connecting to provider services. The term “access router” refers to router that terminates a medium access control (MAC) service from terminals and forwards user traffic to information servers according to Internet Protocol (IP) addresses.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term “SSB” refers to a synchronization signal/Physical Broadcast Channel (SS/PBCH) block, which includes a Primary Syncrhonization Signal (PSS), a Secondary Syncrhonization Signal (SSS), and a PBCH. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation. The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA. The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC. The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA. The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell. Furthermore, any of the disclosed embodiments and example implementations can be embodied in the form of various types of hardware, software, firmware, middleware, or combinations thereof, including in the form of control logic, and using such hardware or software in a modular or integrated manner. Additionally, any of the software components or functions described herein can be implemented as software, program code, script, instructions, etc., operable to be executed by processor circuitry. These components, functions, programs, etc., can be developed using any suitable computer language such as, for example, Python, PyTorch, NumPy, Ruby, Ruby on Rails, Scala, Smalltalk, Java™, C++, C#, “C”, Kotlin, Swift, Rust, Go (or “Golang”), EMCAScript, JavaScript, TypeScript, Jscript, ActionScript, Server-Side JavaScript (SSJS), PHP, Pearl, Lua, Torch/Lua with Just-In Time compiler (LuaJIT), Accelerated Mobile Pages Script (AMPscript), VBScript, JavaServer Pages (JSP), Active Server Pages (ASP), Node.js, ASP.NET, JAMscript, Hypertext Markup Language (HTML), extensible HTML (XHTML), Extensible Markup Language (XML), XML User Interface Language (XUL), Scalable Vector Graphics (SVG), RESTful API Modeling Language (RAML), wiki markup or Wikitext, Wireless Markup Language (WML), Java Script Object Notion (JSON), Apache® MessagePack™, Cascading Stylesheets (CSS), extensible stylesheet language (XSL), Mustache template language, Handlebars template language, Guide Template Language (GTL), Apache® Thrift, Abstract Syntax Notation One (ASN.l), Google® Protocol Buffers (protobuf), Bitcoin Script, EVM® bytecode, Solidity™, Vyper (Python derived), Bamboo, Lisp Like Language (LLL), Simplicity provided by Blockstream™, Rholang, Michelson, Counterfactual, Plasma, Plutus, Sophia, Salesforce® Apex®, and/or any other programming language or development tools including proprietary programming languages and/or development tools. The software code can be stored as a computer- or processor-executable instructions or commands on a physical non- transitory computer-readable medium. Examples of suitable media include RAM, ROM, magnetic media such as a hard-drive or a floppy disk, or an optical medium such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like, or any combination of such storage or transmission devices.

ABBREVIATIONS

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein. 3GPP Third Generation ASN.1 Abstract Syntax CAPEX CAPital Partnership Notation One Expenditure

Project AUSF Authentication CBRA Contention Based 4G Fourth Server Function Random Access Generation 40 AWGN Additive 75 CC Component

5G Fifth Generation White Gaussian Carrier, Country 5GC 5G Core network Noise Code, Cryptographic ACK BAP Backhaul Checksum

Acknowledgeme Adaptation Protocol CCA Clear Channel nt 45 BCH Broadcast 80 Assessment

AF Application Channel CCE Control Channel Function BER Bit Error Ratio Element

AM Acknowledged BFD Beam Failure CCCH Common Control Mode Detection Channel

AMBRAggregate 50 BLER Block Error Rate 85 CE Coverage Maximum Bit Rate BPSK Binary Phase Enhancement AMF Access and Shift Keying CDM Content Delivery Mobility BRAS Broadband Network

Management Remote Access CDMA Code-

Function 55 Server 90 Division Multiple

AN Access Network BSS Business Support Access ANR Automatic System CFRA Contention Free Neighbour Relation BS Base Station Random Access AP Application BSR Buffer Status CG Cell Group Protocol, Antenna 60 Report 95 Cl Cell Identity

Port, Access Point BW Bandwidth CID Cell-ID (e g., API Application BWP Bandwidth Part positioning method) Programming Interface C-RNTI Cell CIM Common APN Access Point Radio Network Information Model Name 65 Temporary 100 CIR Carrier to

ARP Allocation and Identity Interference Ratio Retention Priority CA Carrier CK Cipher Key

ARQ Automatic Repeat Aggregation, CM Connection Request Certification Management,

AS Access Stratum 70 Authority Conditional CRAN Cloud Radio CS A/CA CSMA Mandatory 35 Access Network, with collision avoidance CM AS Commercial Cloud RAN 70 CSS Common Search Mobile Alert Service CRB Common Space, Cell- specific CMD Command Resource Block Search Space CMS Cloud CRC Cyclic CTS Clear-to-Send Management System 40 Redundancy Check CW Codeword CO Conditional CRI Channel-State 75 CWS Contention Optional Information Resource Window Size CoMP Coordinated Indicator, CSI-RS D2D Device-to-Device Multi-Point Resource DC Dual CORESET Control 45 Indicator Connectivity, Direct Resource Set C-RNTI Cell RNTI 80 Current COTS Commercial Off- CS Circuit Switched DCI Downlink The- Shelf CSAR Cloud Service Control

CP Control Plane, Archive Information Cyclic Prefix, 50 CSI Channel-State DF Deployment

Connection Point Information 85 Flavour CPD Connection Point CSI-IM CSI DL Downlink Descriptor Interference DMTF Distributed

CPE Customer Measurement Management Task Premise 55 CSI-RS CSI Force

Equipment Reference Signal 90 DPDK Data Plane

CPICHCommon Pilot CSI-RS RP CSI Development Kit Channel reference signal DM-RS, DMRS

CQI Channel Quality received power Demodulation Indicator 60 CSI-RSRQ CSI Reference Signal

CPU CSI processing reference signal 95 DN Data network unit, Central received quality DRB Data Radio Processing Unit CSI-SINR CSI Bearer

C/R signal-to-noise and DRS Discovery

Command/Respo 65 interference ratio Reference Signal nse field bit CSMA Carrier Sense 100 DRX Discontinuous Multiple Access Reception DSL Domain Specific eMBB Enhanced Mobile 70 E-UTRA Evolved Language. Digital Broadband UTRA

Subscriber Line EMS Element E-UTRAN Evolved DSLAM DSL Management System UTRAN

Access Multiplexer 40 eNB evolved NodeB, EV2X Enhanced V2X DwPTS Downlink E-UTRAN Node B 75 F1AP FI Application

Pilot Time Slot EN-DC E-UTRA- Protocol E-LAN Ethernet NR Dual Fl-C FI Control plane

Local Area Network Connectivity interface

E2E End-to-End 45 EPC Evolved Packet Fl-U FI User plane ECCA extended clear Core 80 interface channel EPDCCH enhanced FACCH Fast assessment, PDCCH, enhanced Associated Control extended CCA Physical CHannel ECCE Enhanced Control 50 Downlink Control FACCH/F Fast Channel Element, Cannel 85 Associated Control

Enhanced CCE EPRE Energy per Channel/Full rate ED Energy Detection resource element FACCH/H Fast EDGE Enhanced EPS Evolved Packet Associated Control Datarates for GSM 55 System Channel/Half rate

Evolution (GSM EREG enhanced REG, 90 FACH Forward Access Evolution) enhanced resource Channel

EGMF Exposure element groups FAUSCH Fast Governance ETSI European Uplink Signalling

Management 60 Telecommunicati Channel

Function ons Standards 95 FB Functional Block

EGPRS Enhanced Institute FBI Feedback

GPRS ETWS Earthquake and Information

EIR Equipment Tsunami Warning FCC Federal Identity Register 65 System Communications eLAA enhanced eUICC embedded UICC, 100 Commission Licensed Assisted embedded Universal FCCH Frequency

Access, enhanced Integrated Circuit Correction CHannel

LAA Card FDD Frequency

EM Element Manager Division Duplex FDM Frequency Sistema (Engl.: GUTI Globally Unique Division Multiplex Global Navigation Temporary UE

FDM A F requency Satellite System) Identity Division Multiple gNB Next Generation HARQ Hybrid ARQ,

Access 40 NodeB 75 Hybrid Automatic

FE Front End gNB-CU gNB- Repeat Request FEC Forward Error centrabzed unit, Next HANDO Handover Correction Generation HFN HyperFrame

FFS For Further Study NodeB Number FFT Fast Fourier 45 centralized unit 80 HHO Hard Handover

Transformation gNB -DU gNB- HLR Home Location feLAA further enhanced distributed unit, Next Register Licensed Assisted Generation HN Home Network

Access, further NodeB HO Handover enhanced LAA 50 distributed unit 85 HPLMN Home FN Frame Number GNSS Global Public Land Mobile FPGA Field- Navigation Satellite Network Programmable Gate System HSDPA High Array GPRS General Packet Speed Downlink

FR Frequency Range 55 Radio Service 90 Packet Access G-RNTI GERAN GSM Global System HSN Hopping

Radio Network for Mobile Sequence Number

Temporary Communications, HSPA High Speed

Identity Groupe Special Packet Access

GERAN 60 Mobile 95 HSS Home Subscriber

GSM EDGE GTP GPRS Tunneling Server RAN, GSM EDGE Protocol HSUPA High Radio Access GTP -U GPRS Tunnelling Speed Uplink Packet Network Protocol for User Access

GGSN Gateway GPRS 65 Plane 100 HTTP Hyper Text Support Node GTS Go To Sleep Transfer Protocol

GLONASS Signal (related to HTTPS Hyper

GLObal'naya WUS) Text Transfer Protocol

NAvigatsionnaya GUMMEI Globally Secure (https is

Sputnikovaya 70 Unique MME Identifier http/ 1.1 over Intermodulation, 70 IRP Integration SSL, i.e. port 443) IP Multimedia Reference Point I-Block IMC IMS Credentials ISDN Integrated

Information IMEI International Services Digital

Block 40 Mobile Network

ICCID Integrated Circuit Equipment 75 ISIM IM Services Card Identification Identity Identity Module IAB Integrated Access IMGI International ISO International and Backhaul mobile group identity Organisation for ICIC Inter-Cell 45 IMPI IP Multimedia Standardisation Interference Private Identity 80 ISP Internet Service

Coordination IMPU IP Multimedia Provider ID Identity, PUblic identity IWF Interworking- identifier IMS IP Multimedia Function

IDFT Inverse Discrete 50 Subsystem I-WLAN Fourier Transform IMSI International 85 Interworking

IE Information Mobile WLAN element Subscriber Constraint length

IBE In-Band Emission Identity of the convolutional

55 IoT Internet of Things code, USIM Individual

IEEE Institute of IP Internet Protocol 90 key Electrical and Ipsec IP Security, kB Kilobyte (1000

Electronics Internet Protocol bytes) Engineers Security kbps kilo-bits per IEI Information 60 IP-CAN IP- second Element Identifier Connectivity Access 95 Kc Ciphering key

IEIDL Information Network Ki Individual Element Identifier IP-M IP Multicast subscriber

Data Length IPv4 Internet Protocol authentication IETF Internet 65 Version 4 key Engineering Task IPv6 Internet Protocol 100 KPI Key Performance Force Version 6 Indicator

IF Infrastructure IR Infrared KQI Key Quality IM Interference IS In Sync Indicator Measurement, KSI Key Set Identifier ksps kilo-symbols per LTE Long Term MBSFN second Evolution Multimedia

KVM Kernel Virtual LWA LTE-WLAN Broadcast multicast Machine aggregation service Single Frequency

LI Layer 1 (physical 40 LWIP LTE/WLAN 75 Network layer) Radio Level MCC Mobile Country

Ll-RSRP Layer 1 Integration with Code reference signal IPsec Tunnel MCG Master Cell received power LTE Long Term Group L2 Layer 2 (data link 45 Evolution 80 MCOT Maximum layer) M2M Machine-to- Channel

L3 Layer 3 (network Machine Occupancy Time layer) MAC Medium Access MCS Modulation and

LAA Licensed Assisted Control (protocol coding scheme Access 50 layering context) 85 MDAF Management

LAN Local Area MAC Message Data Analytics Network authentication code Function

LBT Listen Before (security/encryption MDAS Management Talk context) Data Analytics

LCM LifeCycle 55 MAC-A MAC 90 Service Management used for MDT Minimization of LCR Low Chip Rate authentication Drive Tests LCS Location Services and key agreement ME Mobile LCID Logical (TSG T WG3 context) Equipment Channel ID 60 MAC-IMAC used for 95 MeNB master eNB

LI Layer Indicator data integrity of MER Message Error LLC Logical Link signalling messages Ratio Control, Low Layer (TSG T WG3 context) MGL Measurement Compatibility MANO Gap Length LPLMN Local 65 Management and 100 MGRP Measurement PLMN Orchestration Gap Repetition Period

LPP LTE Positioning MBMS MIB Master Protocol Multimedia Information Block,

LSB Least Significant Broadcast and Multicast Management Bit 70 Service 105 Information Base MIMO Multiple Input 35 MSC Mobile Switching NCT Network Multiple Output Centre 70 Connectivity Topology

MLC Mobile Location MSI Minimum System NC-JT Non Centre Information, coherent Joint MM Mobility MCH Scheduling Transmission Management 40 Information NEC Network MME Mobility MSID Mobile Station 75 Capability Exposure Management Entity Identifier NE-DC NR-E- MN Master Node MSIN Mobile Station UTRA Dual MnS Management Identification Connectivity Service 45 Number NEF Network

MO Measurement MSISDN Mobile 80 Exposure Function Object, Mobile Subscriber ISDN NF Network

Originated Number Function MPBCH MTC MT Mobile NFP Network Physical Broadcast 50 Terminated, Mobile Forwarding Path CHannel Termination 85 NFPD Network

MPDCCH MTC MTC Machine-Type Forwarding Path

Physical Downlink Communications Descriptor Control CHannel mMTCmassive MTC, NFV Network

MPDSCH MTC 55 massive Machine- Functions

Physical Downlink Type Communications 90 Virtualization

Shared CHannel MU-MIMO Multi NFVI NFV MPRACH MTC User MIMO Infrastructure Physical Random MWUS MTC NFVO NFV Orchestrator

Access CHannel 60 wake-up signal, MTC NG Next Generation, MPUSCH MTC wus 95 Next Gen

Physical Uplink Shared NACKNegative NGEN-DC NG-RAN Channel Acknowledgement E-UTRA-NR Dual MPLS Multiprotocol NAI Network Access Connectivity Label Switching 65 Identifier NM Network MS Mobile Station NAS Non-Access 100 Manager MSB Most Significant Stratum, Non- Access NMS Network Bit Stratum layer Management System N-PoP Network Point of 35 NRF NF Repository 70 OOB Out-of-band Presence Function OOS Out of Sync NMIB, N-MIB NRS Narrowband OPEX OPerating Narrowband MIB Reference Signal EXpense NPBCH NS Network Service OSI Other System

Narrowband 40 NSA Non-Standalone 75 Information Physical Broadcast operation mode OSS Operations

CHannel NSD Network Service Support System NPDCCH Descriptor OTA over-the-air Narrowband NSR Network Service PAPR Peak-to-Average

Physical Downlink 45 Record 80 Power Ratio

Control CHannel NSSAINetwork Slice PAR Peak to Average NPDSCH Selection Ratio

Narrowband Assistance PBCH Physical Physical Downlink Information Broadcast Channel

Shared CHannel 50 S-NNSAI Single- 85 PC Power Control, NPRACH NSSAI Personal Computer

Narrowband NSSF Network Slice PCC Primary Physical Random Selection Function Component Carrier, Access CHannel NW Network Primary CC NPUSCH 55 NWUS Narrowband 90 PCell Primary Cell

Narrowband wake-up signal, PCI Physical Cell ID, Physical Uplink Narrowband WUS Physical Cell

Shared CHannel NZP Non-Zero Power Identity NPSS Narrowband O&M Operation and PCEF Policy and Primary 60 Maintenance 95 Charging

Synchronization ODU2 Optical channel Enforcement

Signal Data Unit - type 2 Function

NSSS Narrowband OFDM Orthogonal PCF Policy Control Secondary Frequency Division Function

Synchronization 65 Multiplexing 100 PCRF Policy Control

Signal OFDMA and Charging Rules

NR New Radio, Orthogonal Function Neighbour Relation Frequency Division PDCP Packet Data Multiple Access Convergence Protocol, Packet Data PNFD Physical Network 70 PSFCH Physical

Convergence Function Descriptor Sidelink Feedback Protocol layer PNFR Physical Network Channel PDCCH Physical Function Record PSSCH Physical Downlink Control 40 POC PTT over Sidelink Shared Channel Cellular 75 Channel

PDCP Packet Data PP, PTP Point-to- PSCell Primary SCell Convergence Protocol Point PSS Primary PDN Packet Data PPP Point-to-Point Synchronization Network, Public 45 Protocol Signal Data Network PRACH Physical 80 PSTN Public Switched PDSCH Physical RACH Telephone Network Downlink Shared PRB Physical resource PT-RS Phase-tracking Channel block reference signal

PDU Protocol Data 50 PRG Physical resource PTT Push-to-Talk Unit block group 85 PUCCH Physical

PEI Permanent ProSe Proximity Uplink Control Equipment Identifiers Services, Channel PFD Packet Flow Proximity-Based PUSCH Physical Description 55 Service Uplink Shared P-GW PDN Gateway PRS Positioning 90 Channel PHICH Physical Reference Signal QAM Quadrature hybrid-ARQ indicator PRR Packet Reception Amplitude channel Radio Modulation

PHY Physical layer 60 PS Packet Services QCI QoS class of PLMN Public Land PSBCH Physical 95 identifier Mobile Network Sidelink Broadcast QCL Quasi co-location PIN Personal Channel QFI QoS Flow ID, Identification Number PSDCH Physical QoS Flow Identifier PM Performance 65 Sidelink Downlink QoS Quality of Measurement Channel too Service PMI Precoding Matrix PSCCH Physical QPSK Quadrature Indicator Sidelink Control (Quaternary) Phase

PNF Physical Network Channel Shift Keying Function QZSS Quasi-Zenith RL Radio Link 70 Resource Control Satellite System RLC Radio Link layer

RA-RNTI Random Control, Radio RRM Radio Resource

Access RNTI Link Control Management RAB Radio Access 40 layer RS Reference Signal Bearer, Random RLC AM RLC 75 RSRP Reference Signal

Access Burst Acknowledged Mode Received Power RACH Random Access RLC UM RLC RSRQ Reference Signal Channel Unacknowledged Mode Received Quality

RADIUS Remote 45 RLF Radio Link RSSI Received Signal

Authentication Dial In Failure 80 Strength Indicator User Service RLM Radio Link RSU Road Side Unit RAN Radio Access Monitoring RSTD Reference Signal Network RLM-RS Reference Time difference

RANDRANDom 50 Signal for RLM RTP Real Time number (used for RM Registration 85 Protocol authentication) Management RTS Ready-To-Send RAR Random Access RMC Reference RTT Round Trip Time Response Measurement Channel Rx Reception,

RAT Radio Access 55 RMSI Remaining MSI, Receiving, Receiver Technology Remaining Minimum 90 S1AP SI Application RAU Routing Area System Protocol Update Information Sl-MME SI for the

RB Resource block, RN Relay Node control plane Radio Bearer 60 RNC Radio Network Sl-U SI for the user RBG Resource block Controller 95 plane group RNL Radio Network S-GW Serving Gateway

REG Resource Layer S-RNTI SRNC Element Group RNTI Radio Network Radio Network Rel Release 65 Temporary Identifier Temporary REQ REQuest ROHC RObust Header 100 Identity RF Radio Frequency Compression S-TMSI SAE RI Rank Indicator RRC Radio Resource Temporary Mobile RIV Resource Control, Radio Station Identifier indicator value SA Standalone 35 SDNF Structured Data 70 SIP Session Initiated operation mode Storage Network Protocol SAE System Function SiP System in Architecture Evolution SDP Session Package SAP Service Access Description Protocol SL Sidebnk Point 40 SDSF Structured Data 75 SLA Service Level

SAPD Service Access Storage Function Agreement Point Descriptor SDU Service Data Unit SM Session SAPI Service Access SEAF Security Anchor Management Point Identifier Function SMF Session SCC Secondary 45 SeNB secondary eNB 80 Management Function Component Carrier, SEPP Security Edge SMS Short Message Secondary CC Protection Proxy Service SCell Secondary Cell SFI Slot format SMSF SMS Function SC-FDMA Single indication SMTC SSB-based Carrier Frequency 50 SFTD Space-Frequency 85 Measurement Timing

Division Multiple Time Diversity, SFN Configuration

Access and frame timing SN Secondary Node,

SCG Secondary Cell difference Sequence Number Group SFN System Frame SoC System on Chip

SCM Security Context 55 Number or 90 SON Self-Organizing Management Single Frequency Network SCS Subcarrier Network SpCell Special Cell Spacing SgNB Secondary gNB SP-CSI-RNTISemi- SCTP Stream Control SGSN Serving GPRS Persistent CSI RNTI Transmission 60 Support Node 95 SPS Semi-Persistent Protocol S-GW Serving Gateway Scheduling

SDAP Service Data SI System SQN Sequence number Adaptation Protocol, Information SR Scheduling Service Data SI-RNTI System Request

Adaptation 65 Information RNTI 100 SRB Signalling Radio Protocol layer SIB System Bearer SDL Supplementary Information Block SRS Sounding Downlink SIM Subscriber Reference Signal Identity Module SS Synchronization 35 SUL Supplementary 70 TNL Transport Signal Uplink Network Layer

SSB SS Block TA Timing Advance, TPC Transmit Power SSBRI SSB Resource Tracking Area Control Indicator TAC Tracking Area TPMI Transmitted

SSC Session and 40 Code 75 Precoding Matrix Service TAG Timing Advance Indicator

Continuity Group TR Technical Report

SS-RSRP TAU Tracking Area TRP, TRxP Synchronization Update Transmission

Signal based Reference 45 TB Transport Block 80 Reception Point Signal Received TBS Transport Block TRS Tracking Power Size Reference Signal SS-RSRQ TBD To Be Defined TRx Transceiver Synchronization TCI Transmission TS Technical

Signal based Reference 50 Configuration Indicator 85 Specifications, Signal Received TCP Transmission Technical Quality Communication Standard SS-SINR Protocol TTI Transmission Synchronization TDD Time Division Time Interval

Signal based Signal to 55 Duplex 90 Tx Transmission,

Noise and Interference TDM Time Division Transmitting, Ratio Multiplexing Transmitter

SSS Secondary TDMATime Division U-RNTI UTRAN Synchronization Multiple Access Radio Network Signal 60 TE Terminal 95 Temporary

SSSG Search Space Set Equipment Identity Group TEID Tunnel End Point UART Universal

SSSIF Search Space Set Identifier Asynchronous Indicator TFT Traffic Flow Receiver and

SST Slice/Service 65 Template 100 Transmitter

Types TMSI Temporary UCI Uplink Control

SU-MIMO Single Mobile Information User MIMO Subscriber UE User Equipment

Identity UDM Unified Data USS UE-specific VPLMN Visited

Management search space Public Land Mobile

UDP User Datagram UTRA UMTS Terrestrial Network

Protocol Radio Access VPN Virtual Private

UDR Unified Data 40 UTRAN Universal 75 Network Repository Terrestrial Radio VRB Virtual Resource UDSF Unstructured Access Network Block Data Storage Network UwPTS Uplink WiMAX Function Pilot Time Slot Worldwide UICC Universal 45 V2I Vehicle-to- 80 Interoperability for Integrated Circuit Infrastruction Microwave Access Card V2P Vehicle-to- WLANWireless Local

UL Uplink Pedestrian Area Network

UM Unacknowledged V2V Vehicle-to- WMAN Wireless

Mode 50 Vehicle 85 Metropolitan Area

UML Unified V2X Vehicle-to- Network Modelling Language every thing WPANWireless Personal UMTS Universal Mobile VIM Virtualized Area Network T elecommunicati Infrastructure Manager X2-C X2-Control plane ons System 55 VL Virtual Link, 90 X2-U X2-User plane UP User Plane VLAN Virtual LAN, XML extensible

UPF User Plane Virtual Local Area Markup Language Function Network XRES EXpected user URI Uniform VM Virtual Machine RESponse Resource Identifier 60 VNF Virtualized 95 XOR exclusive OR URL Uniform Network Function ZC Zadoff-Chu Resource Locator VNFFG VNF ZP Zero Power URLLC Ultra- Forwarding Graph Reliable and Low VNFFGD VNF Latency 65 Forwarding Graph

USB Universal Serial Descriptor Bus VNFMVNF Manager

USIM Universal VoIP Voice-over-IP, Subscriber Identity Voice-over- Internet Module 70 Protocol The foregoing description provides illustration and description of various example embodiments, but is not intended to be exhaustive or to limit the scope of embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments. Where specific details are set forth in order to describe example embodiments of the disclosure, it should be apparent to one skilled in the art that the disclosure can be practiced without, or with variation of, these specific details. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives consistent with the present disclosure.

Claims

CLAIMS What is claimed is:

1. An apparatus of a next-generation NodeB (gNB) comprising: memory to store remote direct memory access (RDMA) requirements received from a user equipment (UE); and processing circuitry, coupled with the memory, to: send a radio access network (RAN) compute session establishment request to a computing control function (Comp CF), the RAN compute session establishment request including an indication of the RDMA requirements; and receive, from the Comp CF, a RAN compute session establishment response that is to accept a compute session with RDMA support, wherein the RAN compute session establishment response includes an indication of a queue pair (QP) identifier and a QP key.

2. The apparatus of claim 1, wherein the processing circuitry is further to encode a radio resource control (RRC) reconfiguration message for transmission to the UE, the RRC reconfiguration message including an indication of the QP identifier and the QP key.

3. The apparatus of claim 1, wherein the RDMA requirements include an RDMA protocol type, an RDMA configuration, an RDMA device type, a memory requirement, or an RDMA indicator that is to indicate RDMA is a chosen transport for a computing or data service.

4. The apparatus of claim 1, wherein RAN compute session establishment response includes an indication of a plurality of QP identifiers and a plurality of QP keys.

5. The apparatus of claim 4, wherein the RDMA requirements include a number of QPs and QP types, and a number of QP keys and QP key types.

6. The apparatus of any of claims 1-5, wherein the RDMA requirements are received from the UE via an RRC RAN compute setup request.

7. One or more computer-readable media storing instructions that, when executed by one or more processors, cause a next-generation NodeB (gNB) to: receive, from a computing control function (Comp CF), a RAN compute session modification request that includes an indication of: remote direct memory access (RDMA) requirements, a queue pair (QP) identifier, and a QP key; and in response to receiving the RAN compute session modification request, encode a radio resource control (RRC) reconfiguration message for transmission to a user equipment (UE), the RRC reconfiguration message including an indication of the RDMA requirements, the QP identifier, and the QP key.

8. The one or more computer-readable media of claim 7, wherein the media further stores instructions to cause the gNB to receive, from the UE, an RRC reconfiguration complete message that is to indicate the QP is created and stored on the UE.

9. The one or more computer-readable media of claim 7, wherein the RDMA requirements include an RDMA protocol type, an RDMA configuration, an RDMA device type, a memory requirement, or an RDMA indicator that is to indicate RDMA is a chosen transport for a computing or data service.

10. The one or more computer-readable media of claim 7, wherein RAN compute session establishment response includes an indication of a plurality of QP identifiers and a plurality of QP keys.

11. The one or more computer-readable media of claim 10, wherein the RDMA requirements include a number of QPs and QP types, and a number of QP keys and QP key types.

12. One or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: encode a radio resource control (RRC) radio access network (RAN) compute setup request for transmission to a next-generation NodeB (gNB), the RRC RAN compute setup request including an RDMA indicator or RDMA requirements; and receive, from the gNB, an RRC reconfiguration message that includes: an indication to set up a radio bearer for computing, or an indication of a queue pair (QP) identifier and a QP key.

13. The one or more computer-readable media of claim 12, wherein the media further stores instructions to cause the UE to create a QP based on the RRC reconfiguration message.

14. The one or more computer-readable media of claim 13, wherein the media further stores instructions to cause the UE to encode an RRC reconfiguration complete message for transmission to the gNB to indicate the QP has been created.

15. The one or more computer-readable media of claim 12, wherein the RRC reconfiguration message includes an indication to set up a radio bearer for computing, and wherein the media further stores instructions to cause the UE to configure a radio bearer based on the RRC reconfiguration message.

16. The one or more computer-readable media of claim 15, wherein the RRC reconfiguration message comprises radio bearer configuration information for RDMA connection management (CM) traffic.

17. The one or more computer-readable media of claim 15, wherein the media further stores instructions to cause the UE to encode an RRC reconfiguration complete message for transmission to the gNB to indicate the radio bearer is ready.

18. The one or more computer-readable media of claim 12, wherein the media further stores instructions to cause the UE to send a request for QPs and QP keys to a computing service function (Comp SF).

19. The one or more computer-readable media of claim 18, wherein the media further stores instructions to cause the UE to receive the QPs and QP keys from the Comp SF via a user plane communication.

20. The one or more computer-readable media of claim 12, wherein the RDMA requirements include an RDMA protocol type, an RDMA configuration, an RDMA device type, a memory requirement, or an RDMA indicator that is to indicate RDMA is a chosen transport for a computing or data service.