WO2022031555A1

WO2022031555A1 - Compute offload services in 6g systems

Info

Publication number: WO2022031555A1
Application number: PCT/US2021/044041
Authority: WO
Inventors: Puneet Jain; Abhijeet Kolekar; Ching-Yu Liao; Thomas Luetzenkirchen; Zongrui DING; Qian Li
Original assignee: Intel Corporation
Priority date: 2020-08-03
Filing date: 2021-07-30
Publication date: 2022-02-10
Also published as: CN115804157A

Abstract

Among other things, embodiments of the present disclosure are directed to solutions to enhance the 5GS for supporting session establishment for augmented computing and dynamic workload migration. In particular, some embodiments are directed to supporting session establishment for compute offload services. Other embodiments may be described and/or claimed.

Description

COMPUTE OFFLOAD SERVICES IN 6G SYSTEMS

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 63/060,518, which was filed 03 August 2020; U.S. Provisional Patent Application No. 63/061,057, which was filed 04 August 2020; and U.S. Provisional Patent Application No. 63/060,911, which was filed 04 August 2020.

FIELD

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to solutions to enhance the 5GS for supporting session establishment for augmented computing and dynamic workload migration. In particular, some embodiments are directed to supporting session establishment for compute offload services. Other embodiments may be described and/or claimed.

BACKGROUND

Modem cloud computing has become extremely popular to provide computing/storage capability to customers who can focus more on the SW development and data management without worrying too much about the underlying infrastructure. Edge computing is believed to extend this capability close to the customers to optimize performance metrics such as latency. The 5G architecture design take these scenarios into considerations and developed multi-homing, ULCL framework to offload compute tasks to different data networks (DNs), which may be at the network edge. For the UE with limited computing capabilities, the application can be rendered at the cloud/edge for computing offloading based on application level logic above OS. The traffic routing may be inference by the application for the traffic transported over the cellular networks to fulfill the QoS requirements of the application.

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 a non-roaming 5G system architecture in reference point representation 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 an RRC RAN Compute offload (RCo) session establishment procedure in accordance with various embodiments. Figure 4 illustrates an example of an N1 PDU session establishment procedure enhanced for compute offloading services in accordance with various embodiments.

Figure 5 illustrates an example of an N1 RCo session establishment procedure in accordance with various embodiments.

Figure 6 illustrates an example of applications and data being secured using public and private keys in accordance with various embodiments.

Figure 7 illustrates an example of a process associated with Figure 6 in accordance with various embodiments.

Figure 8 illustrates an example of a process associated with an application-level using trusted third-party certificate authority in accordance with various embodiments.

Figure 9 illustrates an example of a non-roaming 5G system architecture in reference point representation in accordance with various embodiments.

Figure 10 illustrates an example of an initial registration procedure for compute offload services in accordance with various embodiments.

Figure 11 illustrates an example of a requesting UE's ComputeOffload subscription data in accordance with various embodiments.

Figure 12 schematically illustrates a wireless network in accordance with various embodiments.

Figure 13 schematically illustrates components of a wireless network in accordance with various embodiments.

Figure 14 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.

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

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

Figure 17 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).

With the trend of Telco network cloudification, the cellular network is foreseen to be built with flexibility and scalability by virtualized network functions (VNFs) or containerized network functions (CNFs) running on general purpose hardware. Heterogenous computing capabilities provided by hardware and software, naturally coming with this trend, can be leveraged to provide augmented computing to end devices across device and network. These computing tasks generally have different requirements in resource and dependencies in different scenarios. For example, it can be an application instance either standalone or serving one or more UEs. It can also be a generic function like Al training or inference or a micro-service function using specific accelerators. In addition, the computing task can be semi-static or dynamically launched. To enable these scenarios, this disclosure proposes solutions to enable augmented computing across the device and RAN in order to dynamically offload workload and execute compute tasks at the network computing infrastructure with low latency and better computing scaling.

SESSION ESTABLISHMENT FOR COMPUTE OFFLOAD SERVICES IN 6G SYSTEMS

There are a variety of 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. Embodiments of the present disclosure help enable the UE to establish a session for Compute offload services provided by the 5GS.

Figure 1 illustrates an example of an architecture reference model of the 5G System Architecture which is used as a baseline for the proposed enhancements. Figure 2 illustrates an evolution of the 5GS architecture towards support for augmented computing and dynamic workload migration. Once the UE wants to offload a computing task to the network it needs to establish a session for compute offload services. This disclosure proceeds by describing the following three embodiments for supporting session establishment for compute offload services:

- Embodiment 1: New RAN Compute offload (RCo) session establishment procedure

• New RCo NAS protocol is introduced for exchanging RCo NAS messages between UE and RAN Compute CF.

• RCo NAS messages are embedded in RCo NAS containers and transferred using RRC messages (e.g. RRCSetupComplete or new RRC message). RAN CU-CP forwards the RCo NAS containers to RAN Compute CF.

• A new RRC establishment cause value of “mo-cmp” for RAN Compute is introduced as part of the RRCSetupRequest message.

• UE initiates RCo session establishment procedure by sending RCo session establishment request. The RCo session parameters are:

- RAN compute session ID used to identify a RAN compute session within a UE

- Compute offload Network Slice Selection Assistance Information (C-NSSAD: used to assist the network to select a slice for compute offload service.

- Compute Data Network Name (CDNN): used to identify Data network for compute offload services.

- Compute Offload Capability (COC): The Compute offload capabilities requested by the UE based on allowed compute offload capabilities indicated by the network during registration procedure.

• RAN CU-CP selects a RAN Compute CF e.g. based on C-NSSAI.

• RAN Compute CF creates SM association with PCF e.g. for charging services.

• RAN Compute CF selects RAN Compute SF e.g. based on COC, CDNN and C-NSSAI.

• RAN Compute SF terminates the user-plane and provides compute offload services to the UE.

- Embodiment 2: N1 PDU Session establishment procedure enhanced for compute offload services.

UE initiates N1 PDU session establishment procedure with the following new PDU session parameters: - New Request Type - “RCo PDU session”

- RAN compute session ID used to identify a RAN compute session within a UE. As an alternative the existing PDU session ID could be reused as RAN compute session ID.

- Compute offload Slice Network Selection Assistance Information (C-NSSAD: used to assist the network to select a slice for compute offload service.

• SMF uses new NGAP procedures to manage RCo services provided by the RAN Compute CF/SF (no PDU session is established at UPF).

• RAN CU-CP selects a RAN Compute CF e.g. based on C-NSSAI

• RAN Compute CF selects RAN Compute SF based on C-NSSAI, COC, CDNN and the status of the RAN Compute SF.

• SMF uses NGAP PDU session management procedures enhanced with new session parameters to assign resources on Uu and UP for the RCo PDU session, and to setup corresponding DRBs. New session parameters are: RAN compute session ID, C-NSSAI, CDNN, COC and endpoint information specific to the RAN Compute SF.

- Embodiment: Using a new N1 RAN compute offload (RCo) session management procedure

The main differences compared to Embodiment 2 are:

• New N1 RCo session establishment procedure instead of enhancing the existing N1 PDU session establishment procedure.

• New SMF service NsmfyRCoSession service instead of enhancing the existing NsmfyPDUSession service.

• New NGAP procedures for RCo Session management instead of enhancing the existing NGAP PDU session management procedures Embodiment 1 - New RRC RAN compute offload session establishment procedure

Figure 3 illustrates the proposed RAN Compute offload (RCo) session establishment procedure for compute offload services.

1. The UE sends RAN Compute offload (RCo) session establishment request embedded in an RCo container inside an RRC message. The UE allocates the RAN Compute Session ID for the session and includes it in the RCo session establishment request. The UE also includes the SUPI, COC (e.g. from application manifest) and CDNN in the RCo session establishment request. The UE includes C-NSSAI in the RRC message.

2. The RAN CU-CP selects a RAN Compute CF e.g. based on C-NSSAI.

3. The RAN forwards the RCo container with the RCo session establishment request to the RAN Compute CF.

Note: The RAN CU-CP forwards subsequent RCo session management information based on the RAN compute session ID.

4. The RAN Compute CF retrieves compute offload subscription information from the UDM and validates the session parameters.

5. If required the RAN Compute CF initiates Secondary authentication/authorization.

6a-b. The RAN Compute CF requests to establish an SM Policy Association with the PCF to retrieve the PCC rules for the session (e.g. charging control information).

7. The RAN Compute CF selects a RAN Compute SF (e.g. based on COC, CDNN and C-NSSAI).

8. The RAN Compute CF initiates the SMF initiated SM Policy Association Modification procedure with the PCF (e.g. a Policy control request trigger is met related to charging policy).

9. The RAN Compute CF establishes a RCo session with the selected RAN Compute SF

10. The RAN Compute CF sends RCo session request to request the RAN to assign resources to the RCo session. The RAN Compute CF also sends an RCo NAS container with the RCo establishment accept. The RAN Compute CF includes the RAN Compute Session ID, C- NSSAI, CDNN and COC in the RCo establishment accept.

11. The RAN CU-CP forwards the RCo container with the RCo establishment accept to the UE and sets up the radio bearers. Embodiment 2 - N1 PDU Session establishment procedure enhanced for compute offload services

Figure 4 illustrates the N1 PDU session establishment procedure enhanced for compute offload services.

1. The UE sends PDU session establishment request embedded in a NAS container inside an RRC message. The UE includes the Request Type for compute offload sessions, RAN Compute Session ID, COC (e.g. from application manifest), CDNN and C-NSSAI.

2. The AMF selects the SMF via NRF based on C-NSSAI and the ability to support compute offload sessions.

3. The AMF sends Nsmf_PDUSession_CreateSMContext Request to the SMF to create a Session management context.

4. The SMF retrieves COC subscription information from the UDM and validates the session parameters.

5. The SMF sends Nsmf_PDUSession_CreateSMContext Response to the AMF

6. If required the AMF initiates Secondary authentication/authorization.

7a-b. The SMF requests to establish an SM Policy Association with the PCF to retrieve the PCC rules for the session (e.g. charging control information).

8a. -g.

The SMF sends Namf_Communication_N !N2MessageTransfer including a N2 RCo session establishment request (new NGAP procedure). The SMF includes RAN Compute Session ID, C-NSSAI, COC and CDNN in the request.

The AMF forwards the N2 RCo session establishment request to the RAN CU-CP.

The RAN CU-CP selects a RAN Compute CF e.g. based on C-NSSAI and forwards the RCo session establishment request to the RAN Compute CF.

The RAN Compute CF selects a RAN Compute SF e.g. based on COC and CDNN. The RAN Compute CF establishes an RCo session with the RAN Compute SF and sends RCo session establishment response to the RAN CU-CP. The RAN Compute CF includes the endpoint information (e.g. RAN Compute SF identifier) in the response.

The RAN CU-CP forwards N2 RCo session establishment response to the AMF

The AMF sends Namf_Communication_N2InfoNotify with the RCo session establishment response to the SMF.

9. The SMF initiates the SMF initiated SM Policy Association Modification procedure with the PCF (e.g. a Policy control request trigger is met related to charging policy). The SMF sends Namf_Communication_NlN2MessageTransfer including a N2 PDU session request. The SMF includes the C-NSSAI, CDNN and COC and endpoint information. The SMF also includes the N1 SM container with the PDU session establishment accept. The PDU Session Establishment Accept includes the C-NSSAI, CDNN and COC.

11. The RAN CU-CP establishes the required radio bearers and connects the user plane with the RAN Compute SF based on the endpoint information. The RAN CU-CP forwards NAS PDU session establishment accept to the UE.

Embodiment 3 - New N1 RAN Compute offload (RCo) session establishment procedure

Figure 5 illustrates the new N1 RCo session establishment procedure for compute offload services.

1. The UE sends RCo session establishment request (new N1 procedure) embedded in a NAS container inside an RRC message. The UE includes RAN Compute Session ID, COC (e.g. from application manifest), CDNN and C-NSSAI.

2. The AMF retrieves COC subscription information from the UDM and validates the RCo session parameters.

3. The AMF creates a UE context for an RCo session.

4. If required the AMF initiates Secondary authentication/authorization.

5a-b. The AMF requests to establish an SM Policy Association with the PCF to retrieve the PCC rules for the session (e.g. charging control information).

6a. -e.

The AMF sends N2 RCo session establishment request (new NGAP procedure) to the RAN CU-CP. The AMF includes RAN Compute Session ID, C-NSSAI, COC and CDNN in the request.

Note: The RAN CU-CP forwards subsequent RCo session management information to the RAN Compute CF based on the RAN Compute Session ID.

The RAN CU-CP forwards N2 RCo session establishment response to the AMF. 7. The AMF initiates the SM Policy Association Modification procedure with the PCF (e.g. a Policy control request trigger is met related to charging policy).

8.

The AMF sends N2 RCo session request (new NGAP procedure) to the RAN CU- CP. The AMF includes the C-NSSAI, CDNN and COC and endpoint information. The AMF also includes the N1 SM container with the RCo session establishment accept. The RCo Session Establishment Accept includes the C-NSSAI, CDNN and COC.

9. The RAN CU-CP establishes the required radio bearers and connects the user plane with the RAN Compute SF based on the endpoint information. The RAN CU-CP forwards NAS RCo session establishment accept to the UE.

TRUSTED THIRD PARTY BASED END-TO-END (E2E) APPLICATION SECURITY FOR COMPUTE OFFLOAD

Augmented computing across UE and RAN or dynamic workload offloading allows a compute task to be dynamically offloaded and executed on the network computing infrastructure with low latency and better computing scaling. With the trend of Telco network cloudification, the cellular network is foreseen to be built with flexibility and scalability by virtualized network functions (VNFs) or containerized network functions (CNFs) running on general-purpose hardware. Heterogenous computing capabilities provided by hardware and software, naturally coming with this trend, can be leveraged to provide augmented computing to end devices across devices and networks. These computing tasks generally have different requirements in resources and dependencies in different scenarios. For example, it can be an application instance either standalone or serving one or more UEs. It can also be a generic function like Al training or inference or a micro-service function using specific accelerators. Besides, the computing task can be semi-static or dynamically launched. To enable these scenarios, the device may need to negotiate with the network about resources and requirements. Besides, the system may need to know more information about the compute task for routing, execution, and charging, etc.

The current 5G architecture is designed for data communication at the application level without these considerations; therefore, not able to address these computing scenarios with the 6G evolution of the current mobile network. The current offloading model at the edge is based on communication service provider (CSP) infrastructure, where CSP controls policy, charging from the User.

With augmented compute service in 6G network, mobile network operator (MNO) needs to have control over the compute offload policy and charging from the User. Embodiments described herein enable support of universal integrated circuit card (UICC) based E2E application security with the following objectives:

• Operator Control of the Application Offload Capability.

• Operator Control for Policy and Charging for Compute Offload.

In order to achieve Operator Controlled end-to-end E2E Security for Application offload data between UE and Application Provider/Server, this disclosure proposes solutions in the Trust Domain which contains the following Actors and Entities:

• Operator (MNO): It can be COMPUTE SF in the Application Provider Domain.

• UICC or universal subscriber identity module (USIM) Manufacturer (SIM Based Credential Generation)

• Application Provider (ASP + CSP + MNO or Integrated ASP with MNO)

• ME and Operating System or Application Client

To the best knowledge of the inventors, there are no previous solutions to address Application E2E security with UICC based security anchor points. There are no known methods to dynamically subscribe and add UICC based anchors for application client and application serverside.

To the best knowledge of the inventors, there are no previous solutions to address augmented computing and dynamic workload migration in the cellular network

The following options are proposed in this disclosure, which uses UICC or non UICC based security for establishing the E2E application security.

Trusted third party (Example. Google App Store or Apple App Store or Enterprise App Store) manages the Application Subscription Information.

1. UICC based subscription information and Personalization during the Manufacturing Time o A symmetrical preshared key stored on the SIM/UICC/USIM and encryption/ decry ption service provided by a mobile network operator or Key Management Service provider. o The application vendor has a business relationship with KMS (key management service) provider and provides the key services to the application vendor.

2. Application-level using trusted third-party certificate authority. In this case, Key management server (KMS) provided by a third-party key management service provider is a Certificate Authority. o Symmetrical preshared Key can be pre-provisioned into the application or dynamically provisioned. Following deployment scenarios are considered for all the options for 6G compute offload cases.

1. Scenario 1: MNO provides connectivity, CSP provides computing infrastructure: Similar to today’s edge computing scenario.

2. Scenario 2: MNO owns communication +compute infrastructure and responsible for communication +compute HW/SW developments

3. Scenario 3: MNO provides communication +compute infrastructure in collaboration with the CSP

MNO collaborates with CSP on comp SW development, e.g., Comp HW/SW is developed by CSP (e.g., CSP as a vendor to MNO).

1. UICC based Application Security Related key material information and Personalization during the Manufacturing Time.

• Figure 6 illustrates an example of this scenario, where all the Applications and Data are secured using public and private key pair that is installed on the UICC during the manufacturing time.

• Scenario 1, 3: MNO has an SLA with CSP who is providing infrastructure as a service. In this case, the Application Session will be secured using public and private key pairs.

• Scenario 2: In this case, Data pipe between UE and Application Offload will be secured using public and private key pair.

In this solution, the trust domain includes a third party providing key management services between MNO and Application Provider.

The provisioning of Group key and UICC identifier from USIM provider to Application provider is done during manufacturing time.

Group Key is used to derive further keys. One option is to use UICC specific, e.g., ICCID; another option is to use Application-specific; the third option is to use per application service provider. Check the KDF in step 4.

Figure 7 illustrates a process flow showing an example of a detailed procedure associated with the relationships in Figure 6:

Application Service Provider has a commercial relationship with MNO, a mobile network operator. Application Service Provider will also establish a business relationship with a Security Key Management service provider.

UE vendor, as part of their manufacturing process, procures a batch of certified eUICC’s from SIM Provider (eUICC manufacturer), with the indication of MNO for the Compute Offload connectivity. SIM Provider provides a profile for the MNO operator and a Compute Offload security applet. SIM Provider generates a secret key Group Key. It then personalizes each eUICC with a UICC ANCHOR KEYs, where UICC KEY is derived from the Group Key using KDF:

UICC ANCHOR KEY = KDF ( “Application Provider ID or APP ID” || “Group ID” || ICCID || .. , GROUP KEY)

SIM Provider securely sends the GROUP KEY, and the list of ICCIDs sent in the to Application Service Provider.

Application Service Provider shares this information with MNO running a Compute Offload security service, or to a separate Compute Offload security service trusted by Application Service Provider. The Compute Offload security service sets up a Key Management Service.

When a UE is switched on for the first time, it connects to the MNO network.

UE Authenticates with MNO Network.

UE establishes an IP connection to the Application Service Provider’s service platform and initiates a TLS connection

The client sends the following “PSK identity”: “Application ID or ASP ID” || “group-id” || ICCID

KMS validates the identity of the connecting UE and calculates the symmetric key UICC ANCHOR KEY, that is used to complete the TLS handshake with PSK authentication.

The UE is now connected to the service platform and can send application data to the Application Service Provider securely. During the lifetime of the applicable subscription, the KMS, acting on behalf of the Application Service Provider, can refresh the Key.

2. Application-level using trusted third-party certificate authority. In this case, Key management server (KMS) provided by a third-party key management service provider is Certificate Authority.

In this solution, it is proposed that for Application-level Authentication, the Application client uses a certificate installed in the eUICC provided by the UICC Manufacturer. Application Provider uses certificate authority (CA) to sign both Application Client Device and Application Server certificates.

This solution supports dynamic application certification generation.

Pre-condition:

The application provider is provisioned with a server certificate.

UE performs a registration procedure and establishes a compute session, which is associated with a CRB (compute radio bearer).

Figure 8 illustrates an example of a message flow associated with the application-level using trusted third-party certificate authority solution: 1. Application Client on UE requests onboard key generation of a new public/private key pair within the eUICC/UICC security applet. It generates a certificate signing request for the Public Key, and it requests the eUICC/UICC security applet to sign a portion of that request using the private Key. The client application sends the CSR (Certificate Signing Request)to the Application server.

2. The Application server forwards the CSR to their certificate authority. CA signs the client public key using its own Private Key.

3. The CA returns the signed client certificate.

4. Application Server sends the new client certificate, its server certificate, and CA’s selfsigned certificate to the Application Client. The Application client stores these certificates to the UICC/eUICC security applet.

5. The Application Client and Application Server are now able to perform mutual authentication using the application certificates stored in the security applet.

REGISTRATION FOR COMPUTING OFFLOAD SERVICES IN 6G SYSTEMS

Among other things, embodiments of the present disclosure may be directed to resolving the open issue of how to enhance the 5GS for supporting registration for augmented computing and dynamic workload migration, since the current 5GS registration procedure does not support augmented computing and dynamic workload migration. In particular, some embodiments of the present disclosure are directed to enhancements to the 5GS registration procedure to support authorization for Compute offload services.

There are various 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 computing task. Third, resource efficiency and latency can also be optimized using paradigms like server-less computing to handle more dynamic workload. Embodiments of the present disclosure may help enable the UE to register with the 5GS for services supporting the above computing scenarios.

This disclosure proceeds by providing details for supporting service Authentication and Authorization for Compute offload services. For example, Figure 9 illustrates again (as introduced above for Figure 1) an example of the architecture reference model of the 5G System Architecture which is used as a baseline for the proposed enhancements.

Below are requirements for supporting 5GS Registration for Compute offload services:

• Reuse of the initial Registration procedure with Primary Authentication using SUPI • New Service subscription for Compute Offload Services

• New USIM Service Indicator for Compute Offload Services

• Support for different tiers of compute offload capabilities

• UE provides generic compute offload capabilities to the network. Network validates requested compute offload capabilities based on subscription data and provides list of supported and allowed compute offload capabilities to the UE.

Note: The detailed definition of compute offload capabilities is not subject to this IDF.

Registration procedure enhancement

Figure 10 illustrates an example of a simplified version of the initial registration procedure (extracted from TS 23.502, v. 16.5.0, 2020-07-09, clause 4.2.2.2.2) with the enhancements for supporting Compute offload services.

1. The UE sends a Registration request and includes the Requested Generic compute offload capability to indicate to the network which Compute offload services it wants to receive.

2. RAN selects an AMF e.g. based on Requested NS SAI, Requested NS SAI may include one or more standardised Slice/Service types (SST) s for Compute offload services.

3. RAN forwards the Registration request to the selected AMF.

4. AMF initiates Primary authentication.

5a-b. The AMF registers the access and retrieves the Subscription data including Compute offload subscription data from the UDM.

6. The AMF creates the UE context including Compute related UE context information.

7. If needed the AMF performs an AM Policy Association

Establishment/Modification.

8. The AMF sends Registration accept. If the UE is subscribed for the Requested

Generic compute offload

the AMF includes the Allowed Generic offload

9. The RAN create the UE context including Compute related UE context information.

10. If one or more requested S-NSSAI are subject to Network Slice Specific Authentication and Authorization the AMF initiates NSSAA (network slice specific authentication and authorization).

UDM enhancements to support Compute offload subscription data

It is proposed to enhance the Nudm_SubscriptionDataManagement Service. A new Get Service operation and Data Types are added for Compute offload in TS 29.503: - first change to TS 29.503 -

ComputeOffload Subscription Data Retrieval

Figure 11 shows an example of a scenario where the NF service consumer (e.g. AMF) sends a request to the UDM to receive the UE's ComputeOffloadSubscription Data. The request contains the UE's identity (/{supi}) and the type of the requested information (/ComputeOffioadSubscription-data).

1. The NF Service Consumer (e.g. AMF) sends a GET request to the resource representing the UE's Compute offload Subscription Data.

2. The UDM responds with "200 OK" with the message body containing the UE's Compute offload Subscription Data.

On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the GET response body.

- second change to TS 29.503 -

The changes to the existing Table 6.1.6.1-1: marked in bold:

Table 6.1.6.1-1: Nudm SDM specific Data Types

- third change to TS 29.503 - 6.1.6.2.XX Type: ComputeOffloadSubscriptionData

Table 6.1.6.2.XX-1: Definition of type ComputeOffloadSubscriptionData

- _end change to TS 29.503 -

SYSTEMS AND IMPLEMENTATIONS

Figures 12-14 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 12 illustrates a network 1200 in accordance with various embodiments. The network 1200 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/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 1200 may include a UE 1202, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1204 via an over-the-air connection. The UE 1202 may be communicatively coupled with the RAN 1204 by a Uu interface. The UE 1202 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electron! c/engine control unit, electron! c/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

In some embodiments, the network 1200 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 1202 may additionally communicate with an AP 1206 via an over-the-air connection. The AP 1206 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 1204. The connection between the UE 1202 and the AP 1206 may be consistent with any IEEE 802.11 protocol, wherein the AP 1206 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 1202, RAN 1204, and AP 1206 may utilize cellular- WLAN aggregation (for example, LWA/LWIP). Cellular- WLAN aggregation may involve the UE 1202 being configured by the RAN 1204 to utilize both cellular radio resources and WLAN resources.

The RAN 1204 may include one or more access nodes, for example, AN 1208. AN 1208 may terminate air-interface protocols for the UE 1202 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 1208 may enable data/voice connectivity between CN 1220 and the UE 1202. In some embodiments, the AN 1208 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, which may be referred to as a CRAN or virtual baseband unit pool. The AN 1208 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 1208 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.

In embodiments in which the RAN 1204 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 1204 is an LTE RAN) or an Xn interface (if the RAN 1204 is a 5G RAN). 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 1204 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1202 with an air interface for network access. The UE 1202 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 1204. For example, the UE 1202 and RAN 1204 may use carrier aggregation to allow the UE 1202 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 1204 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 1202 or AN 1208 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. 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 1204 may be an LTE RAN 1210 with eNBs, for example, eNB 1212. The LTE RAN 1210 may provide an LTE air interface 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 1204 may be an NG-RAN 1214 with gNBs, for example, gNB 1216, or ng-eNBs, for example, ng-eNB 1218. The gNB 1216 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 1216 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 1218 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 1216 and the ng-eNB 1218 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 1214 and a UPF 1248 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN1214 and an AMF 1244 (e.g., N2 interface). The NG-RAN 1214 may provide a 5G-NR air 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.

In some embodiments, 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 1202 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1202, 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 1202 with different amount of frequency resources (for example, 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 1202 and in some cases at the gNB 1216. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 1204 is communicatively coupled to CN 1220 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 1202). The components of the CN 1220 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 1220 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 1220 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1220 may be referred to as a network sub-slice.

In some embodiments, the CN 1220 may be an LTE CN 1222, which may also be referred to as an EPC. The LTE CN 1222 may include MME 1224, SGW 1226, SGSN 1228, HSS 1230, PGW 1232, and PCRF 1234 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 1222 may be briefly introduced as follows.

The MME 1224 may implement mobility management functions to track a current location of the UE 1202 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 1226 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 1222. The SGW 1226 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 1228 may track a location of the UE 1202 and perform security functions and access control. In addition, the SGSN 1228 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 1224; MME selection for handovers; etc. The S3 reference point between the MME 1224 and the SGSN 1228 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

The HSS 1230 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 1230 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1230 and the MME 1224 may enable transfer of subscription and authentication data for authenticating/ authorizing user access to the LTE CN 1220.

The PGW 1232 may terminate an SGi interface toward a data network (DN) 1236 that may include an application/content server 1238. The PGW 1232 may route data packets between the LTE CN 1222 and the data network 1236. The PGW 1232 may be coupled with the SGW 1226 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1232 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 1232 and the data network 12 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 1232 may be coupled with a PCRF 1234 via a Gx reference point.

The PCRF 1234 is the policy and charging control element of the LTE CN 1222. The PCRF 1234 may be communicatively coupled to the app/content server 1238 to determine appropriate QoS and charging parameters for service flows. The PCRF 1232 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 1220 may be a 5GC 1240. The 5GC 1240 may include an AUSF 1242, AMF 1244, SMF 1246, UPF 1248, NSSF 1250, NEF 1252, NRF 1254, PCF 1256, UDM 1258, and AF 1260 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 1240 may be briefly introduced as follows.

The AUSF 1242 may store data for authentication of UE 1202 and handle authentication- related functionality. The AUSF 1242 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 1240 over reference points as shown, the AUSF 1242 may exhibit an Nausf service-based interface.

The AMF 1244 may allow other functions of the 5GC 1240 to communicate with the UE 1202 and the RAN 1204 and to subscribe to notifications about mobility events with respect to the UE 1202. The AMF 1244 may be responsible for registration management (for example, for registering UE 1202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 1244 may provide transport for SM messages between the UE 1202 and the SMF 1246, and act as a transparent proxy for routing SM messages. AMF 1244 may also provide transport for SMS messages between UE 1202 and an SMSF. AMF 1244 may interact with the AUSF 1242 and the UE 1202 to perform various security anchor and context management functions. Furthermore, AMF 1244 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 1204 and the AMF 1244; and the AMF 1244 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 1244 may also support NAS signaling with the UE 1202 over an N3 IWF interface.

The SMF 1246 may be responsible for SM (for example, session establishment, tunnel management between UPF 1248 and AN 1208); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 1248 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 1244 over N2 to AN 1208; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 1202 and the data network 1236.

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

The NSSF 1250 may select a set of network slice instances serving the UE 1202. The NSSF 1250 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 1250 may also determine the AMF set to be used to serve the UE 1202, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 1254. The selection of a set of network slice instances for the UE 1202 may be triggered by the AMF 1244 with which the UE 1202 is registered by interacting with the NSSF 1250, which may lead to a change of AMF. The NSSF 1250 may interact with the AMF 1244 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 1250 may exhibit an Nnssf service-based interface.

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

The NRF 1254 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 1254 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 1254 may exhibit the Nnrf service-based interface.

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

The UDM 1258 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 1202. For example, subscription data may be communicated via an N8 reference point between the UDM 1258 and the AMF 1244. The UDM 1258 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 1258 and the PCF 1256, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1202) for the NEF 1252. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 1258, PCF 1256, and NEF 1252 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 1258 may exhibit the Nudm service-based interface.

The AF 1260 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 1240 may enable edge computing by selecting operator/3^rd party services to be geographically close to a point that the UE 1202 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 1240 may select a UPF 1248 close to the UE 1202 and execute traffic steering from the UPF 1248 to data network 1236 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1260. In this way, the AF 1260 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1260 is considered to be a trusted entity, the network operator may permit AF 1260 to interact directly with relevant NFs. Additionally, the AF 1260 may exhibit an Naf service-based interface.

The data network 1236 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/content server 1238.

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

The UE 1302 may be communicatively coupled with the AN 1304 via connection 1306.

The connection 1306 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 5GNR protocol operating at mmWave or sub-6GHz frequencies.

The UE 1302 may include a host platform 1308 coupled with a modem platform 1310.

The host platform 1308 may include application processing circuitry 1312, which may be coupled with protocol processing circuitry 1314 of the modem platform 1310. The application processing circuitry 1312 may run various applications for the UE 1302 that source/sink application data. The application processing circuitry 1312 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 1314 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1306. The layer operations implemented by the protocol processing circuitry 1314 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 1310 may further include digital baseband circuitry 1316 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1314 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 1310 may further include transmit circuitry 1318, receive circuitry 1320, RF circuitry 1322, and RF front end (RFFE) 1324, which may include or connect to one or more antenna panels 1326. Briefly, the transmit circuitry 1318 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 1320 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 1322 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 1324 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 1318, receive circuitry 1320, RF circuitry 1322, RFFE 1324, and antenna panels 1326 (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 1314 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 1326, RFFE 1324, RF circuitry 1322, receive circuitry 1320, digital baseband circuitry 1316, and protocol processing circuitry 1314. In some embodiments, the antenna panels 1326 may receive a transmission from the AN 1304 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1326.

A UE transmission may be established by and via the protocol processing circuitry 1314, digital baseband circuitry 1316, transmit circuitry 1318, RF circuitry 1322, RFFE 1324, and antenna panels 1326. In some embodiments, the transmit components of the UE 1304 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 1326.

Similar to the UE 1302, the AN 1304 may include a host platform 1328 coupled with a modem platform 1330. The host platform 1328 may include application processing circuitry 1332 coupled with protocol processing circuitry 1334 of the modem platform 1330. The modem platform may further include digital baseband circuitry 1336, transmit circuitry 1338, receive circuitry 1340, RF circuitry 1342, RFFE circuitry 1344, and antenna panels 1346. The components of the AN 1304 may be similar to and substantially interchangeable with like-named components of the UE 1302. In addition to performing data transmission/reception as described above, the components of the AN 1308 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 14 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 14 shows a diagrammatic representation of hardware resources 1400 including one or more processors (or processor cores) 1410, one or more memory /storage devices 1420, and one or more communication resources 1430, each of which may be communicatively coupled via a bus 1440 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1402 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1400.

The processors 1410 may include, for example, a processor 1412 and a processor 1414. The processors 1410 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 1420 may include main memory, disk storage, or any suitable combination thereof. The memory /storage devices 1420 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 1430 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1404 or one or more databases 1406 or other network elements via a network 1408. For example, the communication resources 1430 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 1450 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1410 to perform any one or more of the methodologies discussed herein. The instructions 1450 may reside, completely or partially, within at least one of the processors 1410 (e.g., within the processor’s cache memory), the memory /storage devices 1420, or any suitable combination thereof. Furthermore, any portion of the instructions 1450 may be transferred to the hardware resources 1400 from any combination of the peripheral devices 1404 or the databases 1406. Accordingly, the memory of processors 1410, the memory /storage devices 1420, the peripheral devices 1404, and the databases 1406 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 12-14, 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 15. For example, the process 1500 may include, at 1505, retrieving offload subscription management information based on a radio access network (RAN) compute session identifier included in a RAN compute offload (RCo) session establishment request. The process further includes, at 1510, requesting that a policy control function (PCF) establish a session management (SM) policy association with the PCF to retrieve policy and charging control (PCC) rules. Another such process is illustrated in Figure 16. In this example, process 1600 includes, at 1605, selecting, based on information associated with an application, a key from a plurality of keys stored by a subscriber identity module (SIM). The process further includes, at 1610, communicating with an application server associated with the application based on the selected key.

Another such process is illustrated in Figure 17. In this example, process 1700 includes, at 1705, receiving a registration request that includes an indication of a compute offload service for a user equipment (UE). The process further includes, at 1710, retrieving, from a unified data management (UDM) function, subscription data that includes compute offload subscription data. The process further includes, at 1715, generating a UE context based on the compute offload subscription data, the UE context including compute-related UE context information.

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 1 may include a method to support session establishment for compute offload services.

Example 2 may include the method of example 1 or some other example herein, whereby a new network node “RAN Compute CF” is introduced as the endpoint for the control plane of the compute offload session.

Example 3 may include the method of example 1 or some other example herein, wherein whereby a new network node “RAN Compute SF” is introduced as the endpoint for the user plane of the compute offload session.

Example 4 may include the method of examples 1 to 3 or some other example herein, whereby the UE is enhanced to send a RAN Compute Session ID during the session establishment procedure to identify the RAN compute session within the UE.

Example 5 may include the method of examples 1 to 3 or some other example herein, whereby the UE is enhanced to send Compute offload Slice Selection Assistance Information (C- NSSAI) during the session establishment procedure. Example 5B may include the method of examples 1 to 3 or some other example herein, whereby the UE is enhanced to send an S-NSSAI with a specific Slice/Service type (SST) value standardised for compute offload services during the session establishment procedure. This is an alternative to example 5.

Example 6 may include the method of examples 1 to 3 or some other example herein, whereby the UE is enhanced to send a Compute Data Network Name (CDNN) during the session establishment procedure.

Example 7 may include the method of examples 1 to 3 or some other example herein, whereby the UE is enhanced to send compute offload capability (COC) during the session establishment procedure.

Example 8 may include the method of examples 1 to 7 or some other example herein, whereby the UDM is enhanced to support compute offload subscription information.

Example 9 may include the method of examples 1 to 8 or some other example herein, whereby the PCF is enhanced to support PCC rules for sessions supporting compute offload services.

Example 10 may include the method of examples 1 to 3 or some other example herein, whereby the UE is enhanced to send a new RRC establishment cause value of “mo-cmp” for RAN Compute as part of the RRCSetupRequest message.

Examples specific to embodiment 1 :

Example 11 may include the method of s 1 to 10 or some other herein, whereby a new NAS protocol for supporting RCo session management is introduced between the UE and the RAN Compute CF.

Example 12 may include the method of 5 or some other herein, whereby the RAN selects a “RAN Compute CF” based on C-NSSAI.

Example 13 may include the method of s 1 to 12 or some other herein, whereby the Compute CF validates the session parameters with the compute offload subscription information.

Example 14 may include the method of s 1 to 7 or some other herein, whereby the Compute CF selects a Compute SF based on C-NSSAI, CDNN and COC.

Examples common to Embodiments 2 and 3

Example 15 may include the method of s 1 to 3 or some other herein, whereby the RAN is enhanced to support new NGAP procedures for the management of RAN compute offload services provided by the RAN Compute CF/SF.

Examples specific to Embodiment 2: Example 16 may include the method of 15 or some other herein, whereby the SMF is enhanced to use the new NGAP procedures for the management RAN compute offload services provided by the RAN Compute CF/SF.

Example 17 may include the method of s 1 to 7 or some other herein, whereby the NGAP procedures for PDU Session management are enhanced to support RAN compute Session ID, C- NSSAI, CDNN, COC and endpoint information specific to the selected RAN Compute SF.

Example 18 may include the method of 5 or some other herein, whereby the AMF is enhanced to select the SMF viaNRF based on C-NSSAI.

Example 19 may include the method of s 1 to 10 and 15 to 18 or some other herein, whereby the existing N1 PDU session establishment procedure is enhanced to support compute offload services.

Example 20 may include the method of 19 or some other herein, whereby the UE is enhanced to send a PDU Session ID during the session establishment procedure to identify the RAN compute session within the UE. This is an alternative to example 4.

Example 21 may include the method of 19 or some other herein, whereby the UE is enhanced to send a new Request type for compute offload.

Example 22 may include the method of 21 or some other herein, whereby the AMF is enhanced to select the SMF based on the ability to support the new Request type for compute offload.

Example 23 may include the method of 21 or some other herein, whereby the URSP is enhanced to support the new Request type for compute offload information as part of the route selection descriptor.

Example 24 may include the method of 5 or some other herein, whereby the URSP is enhanced to support C-NSSAI as part of route selection descriptor.

Examples specific to Embodiment 3:

Example 25 may include the method of s 1 to 10 and 15 or some other herein, whereby a new N1 NAS procedure “RAN Compute offload (RCo) Session establishment” is introduced to support compute offload services.

Example 26 may include the method of 15 or some other herein, whereby the AMF uses the new NGAP procedures for management RAN compute offload services.

Example 27 may include the method of 15 or some other herein, whereby a new NF is introduced to use the new NGAP procedures for management RAN compute offload services provided by the RAN Compute CF/SF. This is an alternative to example 26.

Example 28 includes a method comprising: receiving a radio access network (RAN) compute offload (RCo) session establishment request that includes an indication of a RAN compute session identifier; and retrieving offload subscription management information based on the RAN compute session identifier.

Example 29 includes the method of example 28 or some other example herein, wherein the RCo establishment request further includes an indication of compute offload slice network selection assistance information (C-NSSAI).

Example 30 includes the method of example 28 or some other example herein, wherein the method further includes validating session parameters.

Example 31 includes the method of example 28 or some other example herein, wherein the method further includes initiating a secondary authentication or authorization.

Example 32 includes the method of example 28 or some other example herein, wherein the method further includes requesting a policy control function (PCF) establish a session management (SM) policy association with the PCF to retrieve policy and charging control (PCC) rules.

Example 33 includes the method of example 28 or some other example herein, wherein the method further includes selecting a RAN compute service function (SF) based on the RCo session establishment request.

Example 34 includes the method of example 28 or some other example herein, wherein the method further includes establishing an RCo session with the selected RAN compute SF.

Example 35 includes the method of any of examples 28-34 or some other example herein, wherein the method is performed by RAN compute control function (CF).

Example 36 includes a method comprising: receiving, a protocol data unit (PDU) session establishment request that includes an indication of a compute offload capability (COC); and retrieving COC subscription information from a unified data management (UDM) function; and establishing a PDU session based on the PDU session establishment request and the COC subscription information.

Example 37 includes the method of example 36 or some other example herein, wherein the PDU session establishment request further includes an indication of: compute offload slice network selection assistance information (C-NSSAI), a RAN compute session identifier, or a compute data network name (CDNN). Example 38 includes the method of example 36 or some other example herein, wherein the method further includes requesting a PCF establish an SM policy association with the PCF to retrieve PCC rules.

Example 39 includes the method of example 38 or some other example herein, wherein the method further includes initiating an SM policy association modification procedure with the PCF.

Example 40 includes the method of any of examples 36-39 or some other example herein, wherein the method is performed by a session management function (SMF).

Example 41 includes a method comprising: receiving an RCo session establishment request that includes compute offload capability (COC) information; retrieving COC subscription information from a UDM based on the COC information; and creating a UE context for an RCo session based on the RCo establishment request and the COC subscription information.

Example 42 includes the method of example 41 or some other example herein, wherein the method further includes requesting a PCF establish an SM policy association with the PCF to retrieve PCC rules.

Example 43 includes the method of example 41 or some other example herein, wherein the method further includes providing an N2 RCo session establishment request to a RAN centralized unit-control plane (CU-CP) that includes information from the RCo session establishment request.

Example 44 includes the method of example 43 or some other example herein, wherein the information from the RCo session establishment request includes an indication of: compute offload slice network selection assistance information (C-NSSAI), a RAN compute session identifier, or a compute data network name (CDNN).

Example 45 includes the method of any of examples 41-44 or some other example herein, wherein the method is performed by an access and mobility management function (AMF).

Example Al may include the method to support a third-party trusted service for facilitating the secure transfer of security anchor between application client and server.

Example A2 may include the method of example 1 or some other example herein, in which SIM manufactures provisions a group anchor key for each application type or application provider.

Example A3 may include the method of example 2 or some other example herein, in which SIM manufacturer provisions a UICC key for each application id.

Example A4 may include the method of example 2 or some other example herein, in which application service provider supplies the MNO or Key Management Server the group key and ICCIDs. Example A5 may include the method of example 2 or some other example herein, in which SIM Provider securely sends the GROUP KEY, and the list of ICCIDs sent in the to Application Service Provider.

Example A6 may include the method of example 5 or some other example herein, where group key is used to derive further keys. One option is to use UICC specific, e.g., ICCID; another option is to use Application-specific; a third option is to use per application service provider.

Example A7 may include a method comprising: for Application-level Authentication, Application client uses a certificate installed in the eUICC by the UICC Manufacturer. Application Provider uses certificate authority to sign both Application Client Device and Application Server certificates.

Example A8 may include a method comprising: selecting a key, from a plurality of keys stored by a SIM, based on an application information associated with an application; and communicating with a server associated with the application based on the selected key.

Example A9 may include the method of example 8 or some other example herein, wherein the application information includes an application type, an application provider, and/or an application ID.

Example A10 may include the method of example 8-9 or some other example herein, wherein the key is a group key.

Example Al 1 may include the method of example 8-9 or some other example herein, wherein the key is a UICC key.

Example Al 2 may include the method of example 8-11 or some other example herein, wherein the selected key is a first key, and wherein the method further comprises generating a second key based on the first key for communicating with the server.

Example Al 3 may include the method of example 12 or some other example herein, wherein the second key is generated based on the first key and one or more of: UICC-specific information, application-specific information, and/or application service provider-specific information.

Example Al 4 may include the method of example 8-13 or some other example herein, wherein the method is performed by a UE or a portion thereof.

Example Bl may include a method for registering with a 5G System to get authorized and to receive Compute offload services.

Example B2 may include the method of example 1 or some other example herein, whereby the registration procedure is enhanced to support the exchange of Compute offload capabilities. Example B3 may include the method of examples 1 and 2 or some other example herein, whereby the UE is enhanced to provide the requested Compute offload capabilities to the network during Registration.

Example B4 may include the method of examples 1 to 3 or some other example herein, whereby the AMF is enhanced validate the requested Compute offload capabilities against the UE subscription.

Example B5 may include the method of examples 1 to 4 or some other example herein, whereby the AMF is enhanced to provide the allowed Compute offload capabilities to the UE during Registration.

Example B6 may include the method of examples 1 to 5 or some other example herein, whereby the UDM is enhanced to support Compute offload subscription data.

Example B7 may include the method of example 3 or some other example herein, whereby the USIM is enhanced too support a Compute offload service indicator.

Example B8 includes a method comprising: receiving a registration request that includes an indication of a compute offload service for a user equipment (UE); retrieving, from a unified data management (UDM) function, subscription data that includes compute offload subscription data; and generating a UE context based on the compute offload subscription data, the UE context including compute-related UO context information.

Example B9 includes the method of example 8 or some other example herein, wherein the registration request includes an indication of network slice selection assistance information (NSSAI).

Example BIO includes the method of example 9 or some other example herein, wherein the NSSAI includes an indication of one or more standardized slice/service types (SSTs) for computer offload services.

Example Bll includes the method of example 8 or some other example herein, wherein the method further includes initiating a primary authentication.

Example B12 includes the method of example 8 or some other example herein, wherein the method further includes performing an access and mobility (AM) policy association establishment or modification.

Example B13 includes the method of example 8 or some other example herein, wherein the method further includes encoding a registration accept message for transmission to the UE. Example B14 includes the method of example 13 or some other example herein, wherein the registration accept message includes an indication of an allowed generic compute offload capability.

Example B15 includes the method of any of examples 8-14 or some other example herein, wherein the method is performed by an access and mobility management function (AMF).

Example B16 includes a method comprising: sending a registration request that includes an indication of a requested generic compute offload capability; and receiving a registration accept message that includes an indication of an allowed generic compute offload capability.

Example B17 includes the method of example 16 or some other example herein, wherein the registration request includes an indication of network slice selection assistance information (NSSAI).

Example B18 includes the method of example 17 or some other example herein, wherein the NSSAI includes an indication of one or more standardized slice/service types (SSTs) for computer offload services.

Example B19 includes the method of any of examples 16-18 or some other example herein, wherein the method is performed by user equipment (UE) or portion thereof.

Example XI includes an apparatus of a radio access network (RAN) compute control function (CF) comprising: memory to store a RAN compute offload (RCo) session establishment request that includes an indication of a RAN compute session identifier; and processing circuitry, coupled with the memory, to: retrieve offload subscription management information based on the RAN compute session identifier; and request that a policy control function (PCF) establish a session management (SM) policy association with the PCF to retrieve policy and charging control (PCC) rules.

Example X2 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to validate session parameters.

Example X3 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to initiate a secondary authentication or authorization.

Example X4 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to select a RAN compute service function (SF) based on the RCo session establishment request. Example X5 includes the apparatus of example XI or some other example herein, wherein the processing circuitry is further to establish an RCo session with the selected RAN compute SF.

Example X6 includes the apparatus of any of examples XI -X5 or some other example herein, wherein the compute offload subscription information is retrieved from a unified data management function (UDM).

Example X7 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: select, based on information associated with an application, a key from a plurality of keys stored by a subscriber identity module (SIM); and communicate with an application server associated with the application based on the selected key.

Example X8 includes the one or more computer-readable media of example X7 or some other example herein, wherein the application information includes an application type, an application provider, or an application identifier.

Example X9 includes the one or more computer-readable media of example X7 or some other example herein, wherein the key is a universal integrated circuit card (UICC) key.

Example XI 0 includes the one or more computer-readable media of example X7 or some other example herein, wherein the selected key is a group key used to derive further keys.

Example XI 1 includes the one or more computer-readable media of example XI 0 or some other example herein, wherein the further keys include a UICC-specific key, an applicationspecific key, or a key associated with an application service provider.

Example X12 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause an access and mobility management function (AMF) to: receive a registration request that includes an indication of a compute offload service for a user equipment (UE); retrieve, from a unified data management (UDM) function, subscription data that includes compute offload subscription data; and generate a UE context based on the compute offload subscription data, the UE context including compute-related UE context information.

Example X13 includes the one or more computer-readable media of example X12 or some other example herein, wherein the registration request includes an indication of network slice selection assistance information (NSSAI). Example X14 includes the one or more computer-readable media of example X13 or some other example herein, wherein the NSSAI includes an indication of one or more standardized slice/service types (SSTs) for computer offload services.

Example X15 includes the one or more computer-readable media of example X12 or some other example herein, wherein the media further stores instructions for causing the AMF to initiate a primary authentication.

Example X16 includes the one or more computer-readable media of example X12 or some other example herein, wherein the media further stores instructions for causing the AMF to perform an access and mobility (AM) policy association establishment or modification.

Example X17 includes the one or more computer-readable media of example X12 or some other example herein, wherein the media further stores instructions for causing the AMF to encode a registration accept message for transmission to the UE.

Example XI 8 includes the one or more computer-readable media of example XI 7 or some other example herein, wherein the registration accept message includes an indication of an allowed generic compute offload capability.

Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-X18, or any other method or process described herein.

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 1-X18, or any other method or process described herein.

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 1-X18, or any other method or process described herein.

Z04 may include a method, technique, or process as described in or related to any of examples 1-X18, or portions or parts thereof.

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 1-X18, or portions thereof.

Z06 may include a signal as described in or related to any of examples 1-X18, or portions or parts thereof. Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-X18, or portions or parts thereof, or otherwise described in the present disclosure.

Z08 may include a signal encoded with data as described in or related to any of examples 1-X18, or portions or parts thereof, or otherwise described in the present disclosure.

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 1-X18, or portions or parts thereof, or otherwise described in the present disclosure.

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 1-X18, or portions thereof.

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 1-X18, or portions thereof.

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

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

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

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

Any of the above-described s may be combined with any other (or combination of s), 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.

Abbreviations

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 V16.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the s and embodiments discussed herein. 3GPP Third Generation 35 AWGN Additive 70 CCA Clear Channel

Partnership Project White Gaussian Assessment

4G Fourth Generation Noise CCE Control Channel

5G Fifth Generation BAP Backhaul Element

5GC 5G Core network Adaptation Protocol CCCH Common Control

ACK Acknowledgement 40 BCH Broadcast Channel 75 Channel

AF Application BER Bit Error Ratio CE Coverage

Function BFD Beam Failure Enhancement

AM Acknowledged Detection CDM Content Delivery

Mode BLER Block Error Rate Network

AMBRAggregate 45 BPSK Binary Phase Shift 80 CDMA Code-

Maximum Bit Rate Keying Division Multiple

AMF Access and BRAS Broadband Remote Access

Mobility Access Server CFRA Contention Free

Management BSS Business Support Random Access

Function 50 System 85 CG Cell Group

AN Access Network BS Base Station CI Cell Identity

ANR Automatic BSR Buffer Status CID Cell-ID (e g.,

Neighbour Relation Report positioning method)

AP Application BW Bandwidth CIM Common

Protocol, Antenna 55 BWP Bandwidth Part 90 Information Model

Port, Access Point C-RNTI Cell Radio CIR Carrier to

API Application Network Temporary Interference Ratio

Programming Interface Identity CK Cipher Key

APN Access Point Name CA Carrier CM Connection

ARP Allocation and 60 Aggregation, Certification 95 Management, Conditional

Retention Priority Authority Mandatory

ARQ Automatic Repeat CAPEX CAPital CMAS Commercial Mobile

Request Expenditure Alert Service

AS Access Stratum CBRA Contention Based CMD Command

ASN.1 Abstract Syntax 65 Random Access 100 CMS Cloud Management

Notation One CC Component Carrier, System

AUSF Authentication Country Code, CO Conditional

Server Function Cryptographic Optional

Checksum CoMP Coordinated MultiCS Circuit Switched DF Deployment Point CSAR Cloud Service Flavour

CORESET Control Archive DL Downlink

Resource Set CSI Channel-State DMTF Distributed

COTS Commercial Off- 40 Information 75 Management Task Force

The-Shelf CSI-IM CSI DPDK Data Plane

CP Control Plane, Interference Development Kit Cyclic Prefix, Connection Measurement DM-RS, DMRS Point CSI-RS CSI Demodulation

CPD Connection Point 45 Reference Signal 80 Reference Signal

Descriptor CSI-RSRP CSI DN Data network

CPE Customer Premise reference signal DRB Data Radio Bearer Equipment received power DRS Discovery

CPICHCommon Pilot CSI-RSRQ CSI Reference Signal

Channel 50 reference signal 85 DRX Discontinuous

CQI Channel Quality received quality Reception Indicator CSI-SINR CSI signal- DSL Domain Specific

CPU CSI processing to-noise and interference Language. Digital unit, Central Processing ratio Subscriber Line Unit 55 CSMA Carrier Sense 90 DSLAM DSL Access

C/R Multiple Access Multiplexer

Command/Respons CSMA/CA CSMA with DwPTS Downlink e field bit collision avoidance Pilot Time Slot

CRAN Cloud Radio CSS Common Search E-LAN Ethernet

Access Network, 60 Space, Cell- specific 95 Local Area Network

Cloud RAN Search Space E2E End-to-End

CRB Common Resource CTS Clear-to-Send ECCA extended clear

Block CW Codeword channel assessment,

CRC Cyclic Redundancy CWS Contention extended CCA Check 65 Window Size 100 ECCE Enhanced Control

CRI Channel-State D2D Device-to-Device Channel Element,

Information Resource DC Dual Connectivity, Enhanced CCE

Indicator, CSI-RS Direct Current ED Energy Detection

Resource Indicator DCI Downlink Control

C-RNTI Cell RNTI 70 Information EDGE Enhanced Datarates 35 EREG enhanced REG, FAUSCH Fast Uplink for GSM Evolution enhanced resource 70 Signalling Channel (GSM Evolution) element groups FB Functional Block EGMF Exposure ETSI European FBI Feedback Governance Telecommunication Information

Management 40 s Standards Institute FCC Federal Function ETWS Earthquake and 75 Communications

EGPRS Enhanced Tsunami Warning Commission GPRS System FC CH Frequency

EIR Equipment Identity eUICC embedded UICC, Correction CHannel Register 45 embedded Universal FDD Frequency Division eLAA enhanced Licensed Integrated Circuit Card 80 Duplex

Assisted Access, E-UTRA Evolved FDM Frequency Division enhanced LAA UTRA Multiplex

EM Element Manager E-UTRAN Evolved FDMAFrequency Division eMBB Enhanced Mobile 50 UTRAN Multiple Access

Broadband EV2X Enhanced V2X 85 FE Front End

EMS Element F1AP Fl Application FEC Forward Error

Management System Protocol Correction eNB evolved NodeB, E- Fl-C Fl Control plane FFS For Further Study UTRAN Node B 55 interface FFT Fast Fourier

EN-DC E-UTRA- Fl-U Fl User plane 90 Transformation

NR Dual interface feLAA further enhanced

Connectivity FACCH Fast Licensed Assisted

EPC Evolved Packet Associated Control Access, further Core 60 CHannel enhanced LAA

EPDCCH enhanced FACCH/F Fast 95 FN Frame Number PDCCH, enhanced Associated Control FPGA Field-

Physical Downlink Channel/Full rate Programmable Gate Control Cannel FACCH/H Fast Array EPRE Energy per resource 65 Associated Control FR Frequency Range element Channel/Half rate 100 G-RNTI GERAN

EPS Evolved Packet FACH Forward Access Radio Network System Channel Temporary Identity GERAN GSM EDGE 35 GTP-UGPRS Tunnelling HTTP Hyper Text

RAN, GSM EDGE Protocol for User 70 Transfer Protocol

Radio Access Plane HTTPS Hyper Text Network GTS Go To Sleep Signal Transfer Protocol

GGSN Gateway GPRS (related to WUS) Secure (https is Support Node 40 GUMMEI Globally http/1.1 over SSL, GLONASS Unique MME Identifier 75 i.e. port 443)

GLObal'naya GUTI Globally Unique I-Block Information

NAvigatsionnaya Temporary UE Identity Block

Sputnikovaya HARQ Hybrid ARQ, ICCID Integrated Circuit

Sistema (Engl.: 45 Hybrid Automatic Card Identification

Global Navigation Repeat Request 80 IAB Integrated Access

Satellite System) HANDO Handover and Backhaul gNB Next Generation HFN HyperFrame ICIC Inter-Cell NodeB Number Interference gNB-CU gNB- 50 HHO Hard Handover Coordination centralized unit, Next HLR Home Location 85 ID Identity, identifier

Generation NodeB Register IDFT Inverse Discrete centralized unit HN Home Network Fourier Transform gNB-DU gNB- HO Handover IE Information distributed unit, Next 55 HPLMN Home element

Generation NodeB Public Land Mobile 90 IBE In-Band Emission distributed unit Network GNSS Global Navigation HSDPA High Speed IEEE Institute of

Satellite System Downlink Packet Electrical and Electronics

GPRS General Packet 60 Access Engineers

Radio Service HSN Hopping Sequence 95 IEI Information

GSM Global System for Number Element Identifier Mobile HSPA High Speed Packet IEIDL Information

Communications, Access Element Identifier Groupe Special 65 HSS Home Subscriber Data Length Mobile Server 100 IETF Internet

GTP GPRS Tunneling HSUPA High Speed Engineering Task Protocol Uplink Packet Access Force

IF Infrastructure IM Interference ISDN Integrated Services Ll-RSRP Layer 1

Measurement, Digital Network reference signal Intermodulation, IP ISIM IM Services received power Multimedia Identity Module L2 Layer 2 (data link

IMC IMS Credentials 40 ISO International 75 layer)

IMEI International Organisation for L3 Layer 3 (network

Mobile Equipment Standardisation layer)

Identity ISP Internet Service LAA Licensed Assisted

IMGI International mobile Provider Access group identity 45 IWF Interworking- 80 LAN Local Area

IMPI IP Multimedia Function Network

Private Identity I-WLAN LBT Listen Before Talk

IMPU IP Multimedia Interworking LCM LifeCycle

PUblic identity WLAN Management

IMS IP Multimedia

Constraint length of 85 LCR Low Chip Rate

Subsystem the convolutional code, LCS Location Services

IMSI International USIM Individual key LCID Logical

Mobile Subscriber kB Kilobyte (1000 Channel ID

Identity bytes) LI Layer Indicator loT Internet of Things

kbps kilo-bits per second 90 LLC Logical Link

IP Internet Protocol Kc Ciphering key Control, Low Layer

Ipsec IP Security, Internet Ki Individual Compatibility Protocol Security subscriber LPLMN Local

IP-CAN IP- authentication key PLMN

Connectivity Access

KPI Key Performance 95 LPP LTE Positioning Network Indicator Protocol

IP-M IP Multicast KQI Key Quality LSB Least Significant

IPv4 Internet Protocol Indicator Bit

Version 4 KSI Key Set Identifier LTE Long Term

IPv6 Internet Protocol 65 ksps kilo-symbols per 100 Evolution

Version 6 second LWA LTE-WLAN

IR Infrared KVM Kernel Virtual aggregation

IS In Sync Machine LWIP LTE/WLAN Radio

IRP Integration LI Layer 1 (physical Level Integration with

Reference Point 70 layer) 105 IPsec Tunnel LTE Long Term

MCS Modulation and MPBCH MTC Evolution coding scheme Physical Broadcast

M2M Machine-to- MDAF Management Data 70 CHannel Machine Analytics Function MPDCCH MTC

MAC Medium Access MDAS Management Data Physical Downlink Control (protocol

Analytics Service Control CHannel layering context) MDT Minimization of MPDSCH MTC MAC Message Drive Tests 75 Physical Downlink authentication code ME Mobile Equipment Shared CHannel (security/encry ption MeNB master eNB MPRACH MTC context) 45 MER Message Error Physical Random

MAC-A MAC used Ratio Access CHannel for authentication and MGL Measurement Gap 80 MPUSCH MTC key agreement (TSG T Length Physical Uplink Shared

WG3 context) MGRP Measurement Gap Channel MAC-IMAC used for data

Repetition Period MPLS MultiProtocol integrity of signalling MIB Master Information Label Switching messages (TSG T Block, Management 85 MS Mobile Station WG3 context) Information Base MSB Most Significant MANO MIMO Multiple Input Bit

Management and

Multiple Output MSC Mobile Switching Orchestration MLC Mobile Location Centre

MBMS Multimedia Centre 90 MSI Minimum System Broadcast and Multicast MM Mobility Information, MCH Service Management Scheduling

MBSFN Multimedia

MME Mobility Information

Broadcast multicast Management Entity MSID Mobile Station service Single Frequency MN Master Node 95 Identifier Network MnS Management MSIN Mobile Station

MCC Mobile Country Service Identification Code

MO Measurement Number

MCG Master Cell Group Object, Mobile MSISDN Mobile MCOT Maximum Channel Originated 100 Subscriber ISDN

Occupancy Time Number MT Mobile Terminated, 35 NFPD Network NPSS Narrowband Mobile Termination Forwarding Path 70 Primary MTC Machine-Type Descriptor Synchronization Communications NFV Network Functions Signal mMTCmassive MTC, Virtualization NSSS Narrowband massive Machine- 40 NFVI NFV Infrastructure Secondary Type Communications NFVO NFV Orchestrator 75 Synchronization MU-MIMO Multi User NG Next Generation, Signal MIMO Next Gen NR New Radio, MWUS MTC wakeNGEN-DC NG-RAN E- Neighbour Relation up signal, MTC 45 UTRA-NR Dual NRF NF Repository

WUS Connectivity 80 Function NACKNegative NM Network Manager NRS Narrowband Acknowl edgement NMS Network Reference Signal NAI Network Access Management System NS Network Service Identifier 50 N-PoP Network Point of NSA Non-Standalone

NAS Non-Access Presence 85 operation mode Stratum, Non- Access NMIB, N-MIB NSD Network Service Stratum layer Narrowband MIB Descriptor NCT Network NPBCH Narrowband NSR Network Service Connectivity Topology 55 Physical Broadcast Record NC-JT NonCHannel 90 NSSAINetwork Slice coherent Joint NPDCCH Narrowband Selection Assistance Transmission Physical Downlink Information

NEC Network Capability Control CHannel S-NNSAI Single-

Exposure 60 NPDSCH Narrowband NSSAI

NE-DC NR-E- Physical Downlink 95 NSSF Network Slice UTRA Dual Shared CHannel Selection Function Connectivity NPRACH Narrowband NW Network NEF Network Exposure Physical Random NWUSNarrowband wake¬

Function 65 Access CHannel up signal, Narrowband

NF Network Function NPUSCH Narrowband 100 WUS NFP Network Physical Uplink NZP Non-Zero Power Forwarding Path Shared CHannel O&M Operation and

Maintenance ODU2 Optical channel

PCF Policy Control 70 PM Performance Data Unit - type 2 Function Measurement OFDM Orthogonal PCRF Policy Control and PMI Precoding Matrix Frequency Division Charging Rules Indicator Multiplexing Function PNF Physical Network

OFDMA Orthogonal 40 PDCP Packet Data 75 Function

Frequency Division Convergence Protocol, PNFD Physical Network

Multiple Access Packet Data Function Descriptor

OOB Out-of-band Convergence PNFR Physical Network

OOS Out of Sync Protocol layer Function Record

OPEX OPerating EXpense

PDCCH Physical 80 POC PTT over Cellular OSI Other System Downlink Control PP, PTP Point-to- Information Channel Point

OSS Operations Support PDCP Packet Data PPP Point-to-Point System Convergence Protocol Protocol

OTA over-the-air 50 PDN Packet Data 85 PRACH Physical

PAPR Peak-to-Average Network, Public Data RACH Power Ratio Network PRB Physical resource

PAR Peak to Average PDSCH Physical block Ratio Downlink Shared PRG Physical resource

PBCH Physical Broadcast 55 Channel 90 block group Channel PDU Protocol Data Unit ProSe Proximity Services,

PC Power Control, PEI Permanent Proximity-Based Personal Computer Equipment Identifiers Service PCC Primary PFD Packet Flow PRS Positioning Component Carrier, 60 Description 95 Reference Signal Primary CC P-GW PDN Gateway PRR Packet Reception

PCell Primary Cell PHICH Physical Radio PCI Physical Cell ID, hybrid-ARQ indicator PS Packet Services Physical Cell Identity channel PSBCH Physical PCEF Policy and

PHY Physical layer 100 Sidelink Broadcast Charging PLMN Public Land Mobile Channel

Enforcement Network PSDCH Physical Function PIN Personal Sidelink Downlink

Identification Number Channel PSCCH Physical QZSS Quasi-Zenith RL Radio Link

Sidelink Control Satellite System RLC Radio Link Control,

Channel RA-RNTI Random Radio Link Control layer

PSFCH Physical Access RNTI RLC AM RLC

Sidelink Feedback 40 RAB Radio Access 75 Acknowledged Mode

Channel Bearer, Random RLC UM RLC

PSSCH Physical Access Burst Unacknowledged Mode

Sidelink Shared RACH Random Access RLF Radio Link Failure

Channel Channel RLM Radio Link

PSCell Primary SCell 45 RADIUS Remote 80 Monitoring

PSS Primary Authentication Dial In RLM-RS Reference

Synchronization User Service Signal for RLM

Signal RAN Radio Access RM Registration

PSTN Public Switched Network Management

Telephone Network 50 RAND RANDom number 85 RMC Reference

PT-RS Phase-tracking (used for Measurement Channel reference signal authentication) RMSI Remaining MSI,

PTT Push-to-Talk RAR Random Access Remaining Minimum

PUCCH Physical Response System Information

Uplink Control 55 RAT Radio Access 90 RN Relay Node

Channel Technology RNC Radio Network

PUSCH Physical RAU Routing Area Controller

Uplink Shared Update RNL Radio Network

Channel RB Resource block, Layer

QAM Quadrature 60 Radio Bearer 95 RNTI Radio Network

Amplitude Modulation RBG Resource block Temporary Identifier

QCI QoS class of group ROHC RObust Header identifier REG Resource Element Compression

QCL Quasi co-location Group RRC Radio Resource

QFI QoS Flow ID, QoS 65 Rel Release 100 Control, Radio

Flow Identifier REQ REQuest Resource Control layer

QoS Quality of Service RF Radio Frequency RRM Radio Resource

QPSK Quadrature RI Rank Indicator Management

(Quaternary) Phase Shift RIV Resource indicator RS Reference Signal

Keying 70 value RSRP Reference Signal SAPI Service Access SEPP Security Edge Received Power Point Identifier Protection Proxy RSRQ Reference Signal SCC Secondary SFI Slot format Received Quality Component Carrier, indication

RS SI Received Signal 40 Secondary CC 75 SFTD Space-Frequency Strength Indicator SCell Secondary Cell Time Diversity, SFN and

RSU Road Side Unit SC-FDMA Single frame timing difference RSTD Reference Signal Carrier Frequency SFN System Frame Time difference Division Multiple Number or RTP Real Time Protocol 45 Access 80 Single Frequency

RTS Ready-To-Send SCG Secondary Cell Network RTT Round Trip Time Group SgNB Secondary gNB Rx Reception, SCM Security Context SGSN Serving GPRS Receiving, Receiver Management Support Node S1AP SI Application 50 SCS Subcarrier Spacing 85 S-GW Serving Gateway Protocol SCTP Stream Control SI System Information

SI -MME SI for the Transmission SI-RNTI System control plane Protocol Information RNTI

Sl-U SI for the user SDAP Service Data SIB System Information plane 55 Adaptation Protocol, 90 Block

S-GW Serving Gateway Service Data Adaptation SIM Subscriber Identity

S-RNTI SRNC Protocol layer Module

Radio Network SDL Supplementary SIP Session Initiated

Temporary Identity Downlink Protocol S-TMSI SAE 60 SDNF Structured Data 95 SiP System in Package Temporary Mobile Storage Network SL Sidelink Station Identifier Function SLA Service Level SA Standalone SDP Session Description Agreement operation mode Protocol SM Session SAE System 65 SDSF Structured Data 100 Management Architecture Evolution Storage Function SMF Session SAP Service Access SDU Service Data Unit Management Function Point SEAF Security Anchor SMS Short Message SAPD Service Access Function Service Point Descriptor 70 SeNB secondary eNB 105 SMSF SMS Function SMTC SSB-based 35 Signal Received TCP Transmission

Measurement Timing Quality Communication

Configuration SS-SINR 70 Protocol

SN Secondary Node, Synchronization TDD Time Division

Sequence Number Signal based Signal to Duplex

SoC System on Chip 40 Noise and Interference TDM Time Division

SON Self-Organizing Ratio Multiplexing

Network SSS Secondary 75 TDMATime Division

SpCell Special Cell Synchronization Multiple Access

SP-CSI-RNTISemi- Signal TE Terminal

Persistent CSI RNTI 45 SSSG Search Space Set Equipment

SPS Semi-Persistent Group TEID Tunnel End Point

Scheduling SSSIF Search Space Set 80 Identifier

SQN Sequence number Indicator TFT Traffic Flow

SR Scheduling Request SST Slice/Service Types Template

SRB Signalling Radio 50 SU-MIMO Single User TMSI Temporary Mobile

Bearer MIMO Subscriber Identity

SRS Sounding Reference SUL Supplementary 85 TNL Transport Network

Signal Uplink Layer

SS Synchronization TA Timing Advance, TPC Transmit Power

Signal 55 Tracking Area Control

SSB SS Block TAC Tracking Area TPMI Transmitted

SSBRI SSB Resource Code 90 Precoding Matrix

Indicator TAG Timing Advance Indicator

SSC Session and Service Group TR Technical Report

Continuity 60 TAU Tracking Area TRP, TRxP

SS-RSRP Update Transmission

Synchronization TB Transport Block 95 Reception Point

Signal based Reference TBS Transport Block TRS Tracking Reference

Signal Received Size Signal

Power 65 TBD To Be Defined TRx Transceiver

SS-RSRQ TCI Transmission TS Technical

Synchronization Configuration Indicator 100 Specifications,

Signal based Reference Technical Standard TTI Transmission Time UPF User Plane VM Virtual Machine

Interval Function VNF Virtualized

Tx Transmission, URI Uniform Resource Network Function

Transmitting, Identifier VNFFG VNF

Transmitter 40 URL Uniform Resource 75 Forwarding Graph

U-RNTI UTRAN Locator VNFFGD VNF

Radio Network URLLC UltraForwarding Graph

Temporary Identity Reliable and Low Descriptor

UART Universal Latency VNFMVNF Manager

Asynchronous 45 USB Universal Serial 80 VoIP Voice-over-IP,

Receiver and Bus Voice-over- Internet

Transmitter USIM Universal Protocol

UCI Uplink Control Subscriber Identity Module VPLMN Visited

Information USS UE-specific search Public Land Mobile

UE User Equipment

space 85 Network

UDM Unified Data UTRA UMTS Terrestrial VPN Virtual Private

Management Radio Access Network

UDP User Datagram UTRAN Universal VRB Virtual Resource

Protocol Terrestrial Radio Block

UDR Unified Data

Access Network 90 WiMAX Worldwide

Repository UwPTS Uplink Pilot Interoperability for

UDSF Unstructured Data Time Slot Microwave Access

Storage Network V2I Vehicle-to- WLANWireless Local

Function Infrastruction Area Network

UICC Universal

V2P Vehicle-to- 95 WMAN Wireless

Integrated Circuit Card Pedestrian Metropolitan Area

UL Uplink V2V Vehicle-to-Vehicle Network

UM Unacknowledged V2X Vehicle-to- WPANWireless Personal

Mode every thing Area Network

UML Unified Modelling 65 VIM Virtualized 100 X2-C X2-Control plane

Language Infrastructure Manager X2-U X2-User plane

UMTS Universal Mobile VL Virtual Link, XML extensible Markup

Telecommunication VLAN Virtual LAN, Language s System Virtual Local Area XRES EXpected user

UP User Plane 70 Network 105 RESponse XOR exclusive OR

ZC Zadoff-Chu

ZP Zero Power

Terminology

For the purposes of the present document, the following terms and definitions are applicable to the s and embodiments discussed herein.

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 , 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 “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 , 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 “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, 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/systems 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.

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.

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 , during execution of program code.

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 link, and/or the like.

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.

The term “SMTC” refers to an S SB-based measurement timing configuration configured by SSB- MeasurementTimingConflguration.

The term “SSB” refers to an SS/PBCH block.

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.

Claims

CLAIMS What is claimed is:

1. An apparatus of a radio access network (RAN) compute control function (CF) comprising: memory to store a RAN compute offload (RCo) session establishment request that includes an indication of a RAN compute session identifier; and processing circuitry, coupled with the memory, to: retrieve offload subscription management information based on the RAN compute session identifier; and request that a policy control function (PCF) establish a session management (SM) policy association with the PCF to retrieve policy and charging control (PCC) rules.

2. The apparatus of claim 1, wherein the processing circuitry is further to validate session parameters.

3. The apparatus of claim 1, wherein the processing circuitry is further to initiate a secondary authentication or authorization.

4. The apparatus of claim 1, wherein the processing circuitry is further to select a RAN compute service function (SF) based on the RCo session establishment request.

5. The apparatus of claim 1, wherein the processing circuitry is further to establish an RCo session with the selected RAN compute SF.

6. The apparatus of any of claims 1-5, wherein the compute offload subscription information is retrieved from a unified data management function (UDM).

7. One or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: select, based on information associated with an application, a key from a plurality of keys stored by a subscriber identity module (SIM); and communicate with an application server associated with the application based on the selected key.

55

8. The one or more computer-readable media of claim 7, wherein the application information includes an application type, an application provider, or an application identifier.

9. The one or more computer-readable media of claim 7, wherein the key is a universal integrated circuit card (UICC) key.

10. The one or more computer-readable media of claim 7, wherein the selected key is a group key used to derive further keys.

11. The one or more computer-readable media of claim 10, wherein the further keys include a UICC-specific key, an application-specific key, or a key associated with an application service provider.

12. One or more computer-readable media storing instructions that, when executed by one or more processors, cause an access and mobility management function (AMF) to: receive a registration request that includes an indication of a compute offload service for a user equipment (UE); retrieve, from a unified data management (UDM) function, subscription data that includes compute offload subscription data; and generate a UE context based on the compute offload subscription data, the UE context including compute-related UE context information.

13. The one or more computer-readable media of claim 12, wherein the registration request includes an indication of network slice selection assistance information (NSSAI).

14. The one or more computer-readable media of claim 13, wherein the NSSAI includes an indication of one or more standardized slice/service types (SSTs) for computer offload services.

15. The one or more computer-readable media of claim 12, wherein the media further stores instructions for causing the AMF to initiate a primary authentication.

16. The one or more computer-readable media of claim 12, wherein the media further stores instructions for causing the AMF to perform an access and mobility (AM) policy association establishment or modification.

56

17. The one or more computer-readable media of claim 12, wherein the media further stores instructions for causing the AMF to encode a registration accept message for transmission to the UE.

18. The one or more computer-readable media of claim 17, wherein the registration accept message includes an indication of an allowed generic compute offload capability.

57