CN115804157A - Computation offload services in 6G systems - Google Patents

Abstract

Among other things, embodiments of the present disclosure relate to the following solutions: the 5GS is enhanced to support session establishment for enhanced computing and dynamic workload migration. In particular, some embodiments relate to supporting session establishment for computing offload services. Other embodiments may be described and/or claimed.

Description

Computation offload services in 6G systems

Cross Reference to Related Applications

This application claims priority from each of the following patent applications: U.S. provisional patent application No. 63/060,518, filed on 3/8/2020; U.S. provisional patent application No. 63/061,057, filed on 8/4 of 2020; and U.S. provisional patent application No. 63/060,911, filed on 8/4/2020.

Technical Field

Various embodiments may relate generally to the field of wireless communications. For example, some embodiments may involve the following solutions: the 5GS is enhanced to support session establishment for enhanced computing and dynamic workload migration. In particular, some embodiments relate to supporting session establishment for computing offload services. Other embodiments may be described and/or claimed.

Background

Modern cloud computing has become very popular for providing computing/storage capabilities to customers, which allows customers to focus more on Software (SW) development and data management without having to worry too much about the underlying infrastructure. Edge calculations are believed to extend this capability closer to the customer to optimize performance metrics such as latency. The 5G architecture design takes these scenarios into account and develops a multi-homed ULCL framework to offload computing tasks to different Data Networks (DNs), which may be located at the edge of the network. For UEs with limited computing power, applications may be presented in the cloud/edge for computing offload based on application level logic above the OS. For traffic transmitted through a cellular network, traffic routing may be inferred by an application to meet the QoS requirements of the application.

Drawings

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

Fig. 1 illustrates an example of a non-roaming 5G system architecture, denoted by reference point, in accordance with various embodiments.

Fig. 2 illustrates an example of an architecture to implement enhanced computations in a RAN, in accordance with various embodiments.

Fig. 3 illustrates an example of an RRC RAN computation offload (RCo) session establishment procedure, in accordance with various embodiments.

Fig. 4 illustrates an example of an N1PDU session establishment procedure for computing offload service enhancements, in accordance with various embodiments.

Fig. 5 illustrates an example of an N1RCo session establishment procedure in accordance with various embodiments.

Fig. 6 illustrates an example of using public and private keys to protect applications and data, in accordance with various embodiments.

Fig. 7 illustrates an example of the process associated with fig. 6, in accordance with various embodiments.

Fig. 8 illustrates an example of a process associated with an application layer using a trusted third party certification authority in accordance with various embodiments.

Fig. 9 illustrates an example of a non-roaming 5G system architecture, denoted by reference point, in accordance with various embodiments.

Fig. 10 illustrates an example of an initial registration process for a computing offload service, in accordance with various embodiments.

Fig. 11 illustrates an example of requesting computational offload (computeoffoad) subscription data for a UE, in accordance with various embodiments.

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

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

Fig. 14 is a block diagram illustrating the following components, according to some example embodiments: these components can 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.

Fig. 15 depicts an example of a process for practicing various embodiments discussed herein.

FIG. 16 depicts another example of a process for practicing various embodiments.

FIG. 17 depicts yet another example of a process for practicing 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 the 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 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 this document, the phrases "A or B" and "A/B" mean (A), (B), or (A and B).

With the trend of telecommunication network clouding, it is expected that a cellular network with flexibility and extensibility is constructed by a Virtualized Network Function (VNF) or a Containerized Network Function (CNF) running on general hardware. The heterogeneous computing power provided by hardware and software that naturally comes with this trend can be leveraged to provide enhanced computing for end devices across devices and networks. In general, these computing tasks have different requirements for resources and dependencies in different scenarios. For example, a computing task may be a standalone application instance, or an application instance serving one or more UEs. The computational task may also be a general function, such as AI training or reasoning using a particular accelerator or a microservice function. Further, the computing task may be initiated semi-statically or dynamically. To achieve these scenarios, the present disclosure proposes a solution that enables enhanced computing across devices and RANs to dynamically offload workloads and perform computing tasks at a network computing infrastructure with low latency and better computing scalability.

Session establishment for computing offload services in 6G systems

Among other things, embodiments of the present disclosure relate to the following solutions: the 5GS is enhanced to support session establishment for enhanced computing and dynamic workload migration. In particular, some embodiments relate to supporting session establishment for computing offload services. Other embodiments may be described and/or claimed.

Providing computing as a new service or as a network capability based on different scenarios has several advantages. First, the computation tasks can be done at the network edge to optimize latency. This latency includes communication latency as well as computation task start and execution latency. Second, the terminal device can enhance computing by providing requirements regarding the computing environment and computing tasks. Third, paradigms such as serverless computing can also be used to optimize resource efficiency and latency to handle more dynamic workloads. Embodiments of the present disclosure facilitate enabling a UE to establish a session for a computing offload service provided by a5 GS.

Fig. 1 illustrates an example of an architectural reference model of a 5G system architecture, which serves as a benchmark for the proposed enhancements. Fig. 2 illustrates the evolution of the 5GS architecture to support enhanced computing and dynamic workload migration.

Once the UE wants to offload a computing task to the network, it needs to establish a session for the computing offload service. The present disclosure continues by describing the following three embodiments for supporting session establishment for a computing offload service:

example 1: new RAN compute offload (RCo) session establishment procedure

A new RCo NAS protocol was introduced for exchanging RCo NAS messages between the UE and RAN computing CF.

The RCo NAS message is embedded in the RCo NAS container and transmitted using an RRC message (e.g., RRC setup complete (RRCSetupComplete) or a new RRC message). The RAN CU-CP computes a CF-forward RCo NAS container to the RAN.

For RAN calculation, a new RRC establishment cause value "mo-cmp" is introduced "

As part of an RRC setup request (RRCSetupRequest) message.

The UE initiates the RCo session setup procedure by sending an RCo session setup request. The RCo session parameters are:

-RAN calculation of Session IDFor identifying RAN computing sessions within a UE

-Computing offload network slice selection auxiliary information (C-NSSAI): for assisting the network in selecting a slice for computing offload services.

-Computing Data Network Name (CDNN): for identifying a data network for computing offload services.

-Computing Offload Capability (COC): the UE requests the computing offload capability during a registration procedure based on the allowed computing offload capability indicated by the network.

RAN CU-CP selects RAN calculation CF, e.g. based on C-NSSAI.

RAN computation CF creates SM association with PCF, e.g. for charging service.

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

RAN compute SF terminates user plane and provides compute offload service for UE.

Example 2: n1PDU session establishment procedure for computing offload service enhancements.

The UE initiates the N1PDU session setup procedure using the following new PDU session parameters:

-new request type- "RCo PDU session "

-RAN calculation of session IDFor identifying RAN computing sessions within the UE. Alternatively, the existing PDU session ID may be reused as the RAN computing session ID.

-Computing offload slice network selection auxiliary information (C-NSSAI): for assisting the network in selecting a slice for computing offload services.

-Computing Data Network Name (CDNN): identifying for computing offload servicesA data network.

-Computing Offload Capability (COC): the UE requests the computing offload capability during a registration procedure based on the allowed computing offload capability indicated by the network.

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

RAN CU-CP selecting RAN to compute CF, e.g. based on C-NSSAI

RAN computation CF selects RAN computation SF based on C-NSSAI, COC, CDNN and state of RAN computation SF.

SMF uses NGAP PDU session management procedure enhanced with new session parameters to assign resources for RCo PDU sessions over Uu and UP and set UP corresponding DRBs. The new session parameters are: the RAN computes session ID, C-NSSAI, CDNN, COC and endpoint information specific to the RAN computation SF.

RAN compute SF terminates user plane and provides compute offload service for UE.

Example 3: compared to embodiment 2, the main difference with the new N1RAN computation offload (RCo) session management procedure is that:

instead of enhancing the existing N1PDU session setup procedure, it is a new N1RCo session setup procedure.

Instead of enhancing the existing Nsmf _ PDU session (Nsmf _ pdusesation) service, a new SMF service Nsmf _ RCo session (Nsmf _ rcossesion) service.

New NGAP procedures for RCo session management, rather than enhancing existing NGAP PDU session management procedures

Example 1 New RRC RAN computation offload session establishment procedure

Fig. 3 illustrates a RAN computation offload (RCo) session establishment procedure proposed for a computation offload service.

The ue sends a RAN computation offload (RCo) session setup request embedded in an RCo container within an RRC message. The UE calculates a session ID for the session assignment RAN and includes it in the RCo session setup request. The UE also includes SUPI (Subscriber Permanent Identifier), COC (e.g., from an application manifest), and CDNN in the RCo session setup request. The UE includes the C-NSSAI in the RRC message.

RAN CU-CP selects RAN to compute CF, e.g. based on C-NSSAI.

RAN forwards RCo container with RCo session setup request to RAN computation CF.

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

Ran computation CF retrieves computation offload subscription information from UDM and verifies session parameters.

5. If needed, the RAN calculates that the CF initiates secondary authentication/authorization.

The 6a-6b.ran calculates that the CF requests to establish an SM policy association with the PCF to retrieve PCC rules (e.g., charging control information) for the session.

RAN calculation CF RAN calculation SF is selected (e.g., based on COC, CDNN, and C-NSSAI).

Ran calculation CF initiates SM policy association modification procedure with PCF initiated by SMF (e.g. satisfying policy control request trigger with respect to charging policy).

RAN calculation CF establishing RCo session with selected RAN calculation SF

RAN computation CF sends RCo session request to request RAN to assign resources for RCo session. The RAN computation CF also sends the RCo NAS container with RCo setup accept. The RAN computation CF includes the RAN computation session ID, C-NSSAI, CDNN and COC in the RCo setup accept.

Ran CU-CP forwards the RCo container with RCo setup accept to the UE and sets up the radio bearer.

Example 2N 1PDU session establishment procedure for computational offload service enhancement

Fig. 4 illustrates an N1PDU session establishment procedure for computing offload service enhancements.

The ue sends a PDU session setup request embedded in a NAS container within an RRC message. The UE includes a request type for a computing offload session, a RAN computing session ID, a COC (e.g., from an application manifest), a CDNN, and a C-NSSAI.

AMF selects SMF via NRF based on C-NSSAI and ability to support a computing offload session.

Amf sends an Nsmf PDU session create SM context (Nsmf PDU session create SM context) request to SMF to create a session management context.

Smf retrieves COC subscription information from UDM and verifies session parameters.

SMF sends Nsmf _ PDU Session _ CreatesMeontext response to AMF

6. The AMF initiates secondary authentication/authorization if needed.

Smf requests to establish an SM policy association with PCF to retrieve PCC rules (e.g. charging control information) for the session.

8a.-8g.

The SMF sends a Namf _ comm _ N1N2 messaging (Namf _ Communication _ N1N2message transfer) including an N2RCo session setup request (new NGAP procedure). The SMF includes the RAN computing session ID, C-NSSAI, COC, and CDNN in the request.

The AMF forwards the N2RCo session setup request to the RAN CU-CP.

The RAN CU-CP selects the RAN computation CF, e.g. based on C-NSSAI, and forwards the RCo session setup request to the RAN computation CF.

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

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

RAN CU-CP Forwarding N2RCo Session setup response to AMF

The AMF sends a Namf _ Communication _ N2info notification (Namf _ Communication _ N2info notify) with RCo session setup response to the SMF.

SMF initiates SM policy association modification procedure with PCF initiated by SMF (e.g. satisfying policy control request trigger with respect to charging policy).

10a.-10b.

The SMF sends a Namf _ Communication _ N1N2MessageTransfer including a N2PDU session request. SMF includes C-NSSAI, CDNN and COC and endpoint information. SMF also includes N1 SM container with PDU session setup accept. The PDU session establishment accept includes C-NSSAI, CDNN, and COC.

RAN CU-CP establishes the required radio bearers based on the end point information and connects the user plane with RAN calculation SF. The RAN CU-CP forwards the NAS PDU session setup accept to the UE.

Example 3-New N1RAN computational offload (RCo) Session establishment procedure

Fig. 5 illustrates a new N1RCo session establishment procedure for a computing offload service.

Ue sends RCo session setup request (new N1 procedure) embedded in NAS container within RRC message. The UE includes the RAN computing session ID, COC (e.g., from an application manifest), CDNN, and C-NSSAI.

Amf retrieves COC subscription information from UDM and verifies RCo session parameters.

Amf creates UE context for RCo session.

4. The AMF initiates secondary authentication/authorization if needed.

Amf requests to establish an SM policy association with PCF to retrieve PCC rules (e.g., charging control information) for the session.

6a.-6e.

The AMF sends an N2RCo session setup request (new NGAP procedure) to the RAN CU-CP. The AMF includes the RAN computing session ID, C-NSSAI, COC, and CDNN in the request.

The RAN CU-CP selects the RAN computation CF, e.g. based on C-NSSAI, and forwards the RCo session setup request to the RAN computation CF.

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

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

The RAN CU-CP forwards the N2RCo session setup response to the AMF.

Amf initiates SM policy association modification procedure with PCF (e.g. satisfying policy control request trigger with respect to charging policy).

8.

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

RAN CU-CP establishes the required radio bearers based on the end point information and connects the user plane with RAN calculation SF. The RAN CU-CP forwards the NAS RCo session establishment acceptance to the UE.

End-to-end (E2E) application security for computing offload based on trusted third party

Enhanced computational or dynamic workload offloading across UEs and RANs allows computational tasks to be dynamically offloaded and executed over a network computing infrastructure with low latency and better computational scalability. With the trend of telecommunication network clouding, it is expected that a cellular network with flexibility and extensibility is constructed by a Virtualized Network Function (VNF) or a Containerized Network Function (CNF) running on general hardware. The heterogeneous computing power provided by hardware and software that naturally comes with this trend can be leveraged to provide enhanced computing for end devices across devices and networks. In general, these computing tasks have different requirements for resources and dependencies in different scenarios. For example, a computing task may be a standalone application instance, or an application instance serving one or more UEs. The computational task may also be a general function, such as AI training or reasoning using a particular accelerator or a microservice function. Further, the computing task may be semi-statically or dynamically initiated. To implement these scenarios, the device may need to negotiate with the network regarding resources and requirements. Further, the system may need to know more information about the computational tasks for routing, execution, billing, etc.

The current 5G architecture is designed for application-level data communication and does not have these considerations; therefore, the 6G evolution of current mobile networks cannot address these computing scenarios. Current edge offload models are based on the Communication Service Provider (CSP) infrastructure, where the CSP controls policy, charges from the user.

For enhanced computing services in 6G networks, mobile Network Operators (MNOs) need to have control over computing offload policies and charging from users. Embodiments described herein enable supporting Universal Integrated Circuit Card (UICC) based E2E application security with the following goals:

operator controlled application offload capability.

Operator control policy and charging for computational offload.

To achieve operator-controlled end-to-end E2E security for application-offload data between a UE and an application provider/server, the present disclosure proposes a solution in a trust domain that contains the following participants and entities:

operator (MNO): may be a calculated SF in the application provider domain.

UICC or Universal Subscriber Identity Module (USIM) manufacturer (SIM-based credential Generation)

Application provider (ASP + CSP + MNO or ASP integrated with MNO)

ME and operating System or application client

To the inventors' knowledge, there has been no previous solution to address application E2E security for UICC-based security anchors. There is no known method to dynamically subscribe and add UICC-based anchors to the application client and application server side.

To the best of the inventors' knowledge, there has been no previous solution to address enhanced computation and dynamic workload migration in cellular networks

The following options are presented in this disclosure to establish E2E application security using UICC or non-UICC based security.

A trusted third party, such as Google App Store (Google App Store) or Apple App Store (Apple App Store) or Enterprise App Store (Enterprise App Store), manages application subscription information.

1. UICC-based subscription information and personalization during manufacturing

Symmetric pre-shared keys stored on the SIM/UICC/USIM and encryption/decryption services provided by the mobile network operator or key management service provider.

The application provider has a business relationship with a KMS (key management service) provider, and provides a key service to the application provider.

2. An application layer of a trusted third party certification authority is used. In this case, a Key Management Server (KMS) provided by a third party key management service provider is a certificate authority.

The symmetric pre-shared key may be pre-provisioned into the application or dynamically provisioned.

For all options for 6G computing offload cases, the following deployment scenario is considered.

1. Scene 1: MNO provides connectivity, CSP provides computing infrastructure: similar to today's edge computation scenarios.

2. Scene 2: MNO possesses the communication + computing infrastructure and is responsible for communication + computing HW/SW development

3. Scene 3: MNO provides communication in cooperation with CSP + computing infrastructure MNO cooperates with CSP to perform computing SW development, e.g., computing HW/SW developed by CSP (e.g., CSP as provider of MNO).

1. Keying material information related to UICC-based application security and personalization during manufacturing.

Fig. 6 illustrates an example of such a scenario, where all applications and data are protected using a public and private key pair installed on the UICC during manufacture.

Scenes 1, 3: the MNO has an SLA with the CSP providing the infrastructure as a service. In this case, the application session will be protected using a public and private key pair.

Scene 2: in this case, the data pipe between the UE and the application offload will be protected using a public and private key pair.

In this solution, the trust domain comprises a third party providing key management services between the MNO and the application provider.

Provisioning of the group key and UICC identifier by the USIM provider to the application provider is done during manufacturing.

The 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 application service provider specific. The KDF is checked in step 4.

FIG. 7 illustrates a flow chart showing an example of the detailed process associated with the relationship in FIG. 6:

the application service provider has a business relationship with the mobile network operator MNO. The application service provider will also establish a business relationship with the security key management service provider.

As part of the manufacturing process of the UE vendor, the UE vendor purchases a batch of authenticated euiccs from a SIM provider (eUICC manufacturer), with MNOs indicated for computing offload connectivity.

The SIM provider provides the MNO operator with configuration files and compute offload security applets. The SIM provider generates a Key, the Group Key (Group Key). The provider then personalizes each eUICC using a UICC _ ANCHOR _ KEY (UICC _ ANCHOR _ KEY), which is derived from the group KEY using a KDF:

UICC _ ANCHOR _ KEY = KDF ("application provider ID or APP ID" | "group ID" | ICCID |, group KEY.)

The SIM provider securely sends the group key and the list of sent ICCIDs to the application service provider.

The application service provider shares this information with the MNO running the computing offload security service, or shares a separate computing offload security service that is trusted by the application service provider. The compute offload security service sets up a key management service.

When the UE is first turned on, it connects to the MNO network.

The UE authenticates to the MNO network.

The UE establishes an IP connection to a service platform of an application service provider and initiates a TLS connection

The client sends the following "PSK identity": "application ID or ASP ID" | "group ID" | | ICCID

The KMS verifies the identity of the connected UE and calculates a symmetric KEY UICC _ ANCHOR _ KEY, wherein the symmetric KEY is used for completing TLS handshake with PSK authentication.

The UE is now connected to the service platform and can securely send application data to the application service provider. The KMS may refresh the key on behalf of the application service provider for the lifetime of the applicable subscription.

2. An application layer of a trusted third party certification authority is used. In this case, a Key Management Server (KMS) provided by a third party key management service provider is a certificate authority.

In this solution, it is proposed that: for application layer authentication, the application client uses a certificate installed in the eUICC provided by the UICC manufacturer. The application provider uses a Certificate Authority (CA) to sign both the application client device certificate and the application server certificate.

The solution supports dynamic application certificate generation.

The preconditions are as follows:

-the application provider is provided with a server certificate.

The UE performs a registration procedure and establishes a computing session associated with a CRB (computed radio bearer).

FIG. 8 illustrates an example of message flow associated with an application layer using a trusted third party certificate authority solution:

an application client on the ue requests onboard key generation for a new public/private key pair within the eUICC/UICC security applet. The application client generates a certificate signing request for a public key and requests the eUICC/UICC security applet to sign a portion of the request using a private key. The client application sends a CSR (certificate signing request) to the application server.

2. The application server forwards the CSR to its authentication authority. The CA signs the client public key with its own private key.

Ca returns signed client certificate.

4. The application server sends the new client certificate, its server certificate and the CA's self-signed certificate to the application client. The application client stores these credentials in the UICC/eUICC security applet.

5. The application client and the application server can now perform mutual authentication using the application credentials 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 solving the following pending problems: how to enhance 5GS to support registration for enhanced computation and dynamic workload migration because the current 5GS registration process does not support enhanced computation and dynamic workload migration. In particular, some embodiments of the present disclosure relate to enhancing the 5GS registration process to support authorization of computing offload services.

Providing computing as a new service or network capability has several advantages based on different scenarios. First, the computation tasks can be done at the network edge to optimize latency. This latency includes communication latency as well as computation task start and execution latency. Second, the terminal device can enhance computing by providing requirements regarding the computing environment and computing tasks. Third, paradigms such as serverless computing can also be used to optimize resource efficiency and latency to handle more dynamic workloads. Embodiments of the present disclosure may help enable a UE to register with a 5GS for services that support the above-described computational scenario.

The present disclosure continues by providing details for supporting service authentication and authorization for computing offload services. For example, fig. 9 again illustrates an example of an architectural reference model of a 5G system architecture (as introduced above for fig. 1) that serves as a benchmark for the proposed enhancements.

The following is a requirement to support 5GS registration for compute offload services:

reuse of the initial registration procedure by primary authentication using SUPI

New service subscription for compute offload services

New USIM service indicator for compute offload services

Support for different computing offload capability hierarchies

The UE provides general computing offload capability to the network. The network verifies the requested computing offload capability based on the subscription data and provides a list of supported and allowed computing offload capabilities to the UE.

Note: the detailed definition of computing offload capability is not constrained by this document.

Registration procedure enhancement

Fig. 10 illustrates a simplified version example of the initial registration process (taken from TS 23.502, version 16.5.0, 2020-07-09, clause 4.2.2.2.2) that incorporates enhancements for supporting computing offload services.

UE sends registration request andincluding the requested general purpose computing offload capability to indicate to the network that it wants to receive Which computing offload services。

Ran selects AMF, e.g., based on the requested NSSAI.The requested NSSAI may include off-load clothing for the computation One or more standardized slice/service types (SSTs) of a service.

The ran forwards the registration request to the selected AMF.

Amf initiates primary authentication.

5a-5b. AMF registers for this visitAnd retrieving subscription data, including the number of computing offload subscriptions from the UDM According to。

Amf creates UE context including calculating relevant UE context information.

7. The AMF performs AM policy association establishment/modification, if necessary.

Amf sends registration accept.AMF will allow in case of UE subscription to requested generic computation offload capability The generic computing offload capability is included in the registration acceptance.

The ran creates UE context, including calculating relevant UE context information.

10. If one or more requested S-NSSAIs are subject to network slice specific authentication and authorization, the AMF initiates NSSAA (network slice specific authentication and authorization).

UDM enhancements to support computing offload of subscription data

It is proposed to enhance a Nudm _ subscription data management (Nudm _ SubscriptionDataManagement) service. New get service operations and data types are added for computation offload in TS 29.503:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -first alteration to TS 29.503

Computing offload subscription data retrieval

Fig. 11 shows an example of a scenario in which a NF service consumer (e.g., AMF) sends a request to a UDM to receive computing offload subscription (computoffroadsubscription) data for a UE. The request contains the identity of the UE (/ { subji }) and the type of information requested (/ computeoffroadsubscription-data).

The nf service consumer (e.g., AMF) sends a GET (GET) request to a resource that represents the UE's computing offload subscription data.

Udm responds with "200OK" with message body containing UE's computational offload subscription data.

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

A second modification to TS 29.503

Modifications to existing table 6.1.6.1-1, indicated in bold:

TABLE 6.1.6.1-1: nudm _ SDM specific data type

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -third modification to TS 29.503

Type 6.1.6.2. Xx: computeoOffloadSubscriptionData

Table 6.1.6.2.XX-1: definition of type computeoOffloadSubscriptionData

-ending the altering of TS 29.503

System and implementation mode

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

Fig. 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 respect, and the described embodiments may be applicable to other networks that benefit from the principles described herein, such as future 3GPP systems and the like.

Network 1200 may include a UE1202, which may include any mobile or non-mobile computing device designed to communicate with RAN1204 via an over-the-air connection. The UE1202 may be communicatively coupled with the RAN1204 over a Uu interface. The UE1202 may be, but is not limited to, a smartphone, tablet, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment device, in-vehicle entertainment device, instrument cluster, heads-up display device, in-vehicle diagnostic device, dashboard mobile device, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, ioT device, or the like.

In some embodiments, the network 1200 may include multiple UEs directly coupled to each other via a sidelink interface. The UE may be an M2M/D2D device that communicates using a physical sidelink channel (e.g., without limitation, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.).

In some embodiments, the UE1202 may also communicate with the AP 1206 via an over-the-air connection. AP 1206 may manage a WLAN connection that may be used to offload some/all network traffic from RAN 1204. The connection between the UE1202 and the AP 1206 may conform to any IEEE 802.11 protocol, where AP1206 may be wireless fidelity

A router. In some embodiments, UE1202, RAN1204, and AP 1206 may utilize cellular WLAN aggregation (e.g., LWA/LWIP). Cellular WLAN aggregation may involve the RAN1204 configuring the UE1202 to utilize both cellular radio resources and WLAN resources.

RAN1204 may include one or more access nodes, such as AN 1208. The AN 1208 may terminate the air interface protocols of the UE1202 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 1208 may enable data/voice connectivity between CN1220 and UE 1202. In some embodiments, AN 1208 may be implemented in a separate device or as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN or pool of virtual baseband units, for example. AN 1208 is called BS, gNB, RAN node, eNB, ng-eNB, nodeB, RSU, TRxP, TRP, etc. The AN 1208 may be a macro cell base station or a low power base station for providing femto cells, pico cells, or other similar cells with smaller coverage areas, smaller user capacities, or higher bandwidths than macro cells.

In embodiments where the RAN1204 includes multiple ANs, they may be coupled to each other via AN X2 interface (in the case where the RAN1204 is AN LTE RAN) or AN Xn interface (in the case where the RAN1204 is a 5G RAN). The X2/Xn interface, which in some embodiments may be separated into a control/user plane interface, may allow the AN to communicate information related to handover, data/context transfer, mobility, load management, interference coordination, etc.

The ANs of RAN1204 may each manage one or more cells, groups of cells, component carriers, etc., to provide UE1202 with AN air interface for network access. The UE1202 may be simultaneously connected with multiple cells provided by the same or different ANs of the RAN 1204. For example, the UE1202 and the RAN1204 may use carrier aggregation to allow the UE1202 to connect with multiple component carriers, each corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN may be a primary node providing AN MCG and the second AN may be a secondary node providing AN SCG. The first/second AN can be any combination of eNB, gNB, ng-eNB, etc.

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

In a V2X scenario, the UE1202 or the AN 1208 may be or act as AN RSU, which may refer to any transport infrastructure entity for V2X communication. The RSU may be implemented in or by a suitable AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU"; RSUs implemented in or by a gNB may be referred to as "gNB-type RSUs"; and so on. In one example, the RSU is a computing device coupled with radio frequency circuitry located at the curb (which may provide connectivity support for passing vehicle UEs). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications/software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may provide very low latency communications required for high speed events (e.g., collision avoidance, traffic warnings, etc.). Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be enclosed 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 backhaul network.

In some embodiments, RAN1204 may be an LTE RAN 1210, including an eNB (e.g., eNB 1212). The LTE RAN 1210 may provide an LTE air interface with the following characteristics: SCS at 15 kHz; a CP-OFDM waveform for DL and an SC-FDMA waveform for UL; a Turbo code for data and a TBCC for control; and so on. The LTE air interface can rely on the CSI-RS to carry out CSI acquisition and beam management; rely on PDSCH/PDCCH DMRS to demodulate PDSCH/PDCCH; and CRS-dependent cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operate on a band below 6 GHz.

In some embodiments, the RAN1204 may be a NG-RAN 1214 including a gNB (e.g., gNB 1216) or a NG-eNB (e.g., NG-eNB 1218). The gNB1216 may connect with the 5G-enabled UE using a 5G NR interface. The gNB1216 may be connected to the 5G core through an NG interface, which may include an N2 interface or an N3 interface. The NG-eNB 1218 may also be connected with the 5G core over the NG interface, but may be connected with the UE via the LTE air interface. The gNB1216 and the ng-eNB 1218 may be connected to each other over an Xn interface.

In some embodiments, the NG interface can be divided into two parts, a NG user plane (NG-U) interface, which carries traffic data between nodes of the NG-RAN 1214 and the UPF1248 (e.g., an N3 interface), and a NG control plane (NG-C) interface, which is a signaling interface between nodes of the NG-RAN 1214 and the AMF 1244 (e.g., an 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 for UL, and DFT-s-OFDM; polarity, repetition, simplex, and Reed-Muller (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 CRS, but may use PBCH DMRS for PBCH demodulation; performing PDSCH phase tracking using PTRS; and time tracking using the tracking reference signal. The 5G-NR air interface may operate over the FR1 band, which includes the sub-6 Ghz band, or the FR2 band, which includes the 24.25Ghz to 52.6Ghz band. The 5G-NR air interface may include SSBs, which are regions of a downlink resource grid including PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may use BWP for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, the UE1202 may be configured with multiple BWPs, where each BWP configuration has a different SCS. When the change of BWP is indicated to the UE1202, the SCS of the transmission also changes. Another example use case for BWP relates to power saving. In particular, the UE1202 may be configured with multiple BWPs with different numbers of frequency resources (e.g., PRBs) to support data transmission in different traffic load scenarios. BWPs containing a smaller number of PRBs may be used for data transmission with smaller traffic load while allowing power savings at the UE1202 and, in some cases, the gNB 1216. BWPs containing a large number of PRBs may be used for scenarios with higher traffic loads.

The RAN1204 is communicatively coupled to a CN1220, which includes network elements, to provide various functions to support data and telecommunications services to customers/subscribers (e.g., users of the UE 1202). The components of CN1220 may be implemented in one entity node or in different entity nodes. In some embodiments, NFV may be used to virtualize any or all of the functions provided by the network elements of CN1220 onto physical computing/storage resources in servers, switches, etc. The logical instances of CN1220 may be referred to as network slices, and the logical instances of a portion of CN1220 may be referred to as network subslices.

In some embodiments, the CN1220 may be an LTE CN 1222, which may also be referred to as an EPC. As shown, LTE CN 1222 may include MME1224, SGW 1226, SGSN 1228, HSS 1230, PGW 1232, and PCRF1234 coupled to each other by an interface (or "reference point"). The functions of the elements of LTE CN 1222 can be briefly introduced as follows.

The MME1224 may implement mobility management functions to track the current location of the UE1202 to facilitate paging, bearer activation/deactivation, handover, gateway selection, authentication, and so forth.

SGW 1226 may terminate the S1 interface to the RAN and route data packets between the RAN and LTE CN 1222. SGW 1226 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful interception, billing, and some policy enforcement.

The SGSN 1228 may track the location of the UE1202 and perform security functions and access control. In addition, the SGSN 1228 may perform EPC inter-node signaling for mobility between different RAT networks; perform PDN and S-GW selection as specified by MME 1224; performing MME selection for handover; and so on. The S3 reference point between the MME1224 and the SGSN 1228 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active state.

HSS 1230 may include a database for network subscribers that includes subscription related information to support the handling of communication sessions by network entities. HSS 1230 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependency, etc. The S6a reference point between HSS 1230 and MME1224 may enable the transmission of subscription and authentication data for authenticating/authorizing a user to access LTE CN 1220.

PGW 1232 may terminate the SGi interface to a Data Network (DN) 1236, which may include an application/content server 1238. The PGW 1232 may route data packets between the LTE CN 1222 and the data network 1236. PGW 1232 may be coupled with SGW 1226 through an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 1232 may also include nodes (e.g., PCEFs) for policy enforcement and charging data collection. Further, the SGi reference point between PGW 1232 and data network 1236 may be, for example, an operator external public, private PDN or an operator internal packet data network for provisioning IMS services. PGW 1232 may be coupled with PCRF1234 via the Gx reference point.

PCRF1234 is the policy and charging control element of LTE CN 1222. The PCRF1234 may be communicatively coupled to the application/content server 1238 to determine appropriate QoS and charging parameters for the service flow. The PCRF 1232 may provision (via the Gx reference point) the associated rules to the PCEF with the appropriate TFTs and QCIs.

In some embodiments, CN1220 may be 5GC 1240. As shown, the 5GC 1240 may include AUSF 1242, AMF 1244, SMF 1246, UPF1248, NSSF1250, NEF1252, NRF 1254, PCF 1256, UDM 1258, and AF1260 coupled to each other by an interface (or "reference point"). The function of the elements of the 5GC 1240 can be briefly described as follows.

The AUSF 1242 may store data for authentication of the UE1202 and handle functions related to authentication. AUSF 1242 may facilitate a common authentication framework for various access types. AUSF 1242 may also exhibit a Nausf service based interface in addition to communicating with other elements of the 5GC 1240 through reference points as shown.

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

SMF 1246 may be responsible for: SM (e.g., session establishment, tunnel management between UPF1248 and AN 1208); UE IP address assignment and management (including optional authorization); selection and control of the UP function; configuring traffic handling at UPF1248 to route traffic to the correct destination; terminating the interface to the policy control function; controlling a portion of policy enforcement, charging, and QoS; lawful interception (for SM events and interface to the LI system); terminate the SM portion of the NAS message; a downlink data notification; initiating AN-specific SM message, sent by AMF 1244 to AN 1208 via N2; and determines the SSC pattern for the session. SM may refer to the management of PDU sessions, or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE1202 and the data network 1236.

UPF1248 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point to interconnect with data network 1236, and a branch point to support multi-homed PDU sessions. UPF1248 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawful intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the 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 uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF1248 may include an uplink classifier to support routing of traffic flows to the data network.

NSSF1250 may select a set of network slice instances that serve UE 1202. NSSF1250 may also determine allowed NSSAIs and mappings to subscribed S-NSSAIs, if desired. The NSSF1250 may also determine a set of AMFs to be used to serve the UE1202, or determine a list of candidate AMFs, based on a suitable configuration and possibly by querying the NRFs 1254. Selection of a set of network slice instances for the UE1202 may be triggered by the AMF 1244 (with which the UE1202 registers by interacting with the NSSF 1250), which may result in a change in the AMF. NSSF1250 may interact with AMF 1244 via the N22 reference point; and may communicate with another NSSF in the visited network via an N31 reference point (not shown). Further, NSSF1250 may expose an interface based on the NSSF service.

NEF1252 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure/re-exposure, AF (e.g., AF 1260), edge computing or fog computing systems, and the like. In such embodiments, NEF1252 may authenticate, authorize, or throttle AF. NEF1252 may also translate information exchanged with AF1260 and information exchanged with internal network functions. For example, the NEF1252 may translate between the AF service identifier and the internal 5GC information. NEF1252 may also receive information from other NFs based on their exposure capabilities. This information may be stored as structured data in NEF1252 or in the data storage NF using a standardized interface. NEF1252 may then re-expose the stored information to other NFs and AFs, or for other purposes such as analysis. Further, NEF1252 may expose an interface based on the Nnef service.

The NRF 1254 may support a service discovery function, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 1254 also maintains information on available NF instances and the services these instances support. As used herein, the terms "instantiate … …", "instantiation", and the like may refer to the creation of an instance, while "instance" may refer to the specific occurrence of an object, e.g., an object may occur during execution of program code. Further, NRF 1254 may expose an interface based on the Nnrf service.

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

The UDM 1258 may process subscription-related information to support processing of communication sessions by network entities and may store subscription data for the UE 1202. For example, subscription data may be transferred via an N8 reference point between UDM 1258 and AMF 1244. The UDM 1258 may comprise two parts: front end and UDR are applied. The UDR may store subscription data and policy data for UDM 1258 and PCF 1256, and/or structured data and application data for exposure (including PFD for application detection, application request information for multiple UEs 1202) for NEF 1252. UDR221 may expose an interface based on the nurr service to allow UDM 1258, PCF 1256, and NEF1252 to access a particular collection of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM may include a UDM-FE that is responsible for handling credentials, location management, subscription management, and the like. 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 processing, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, UDM 1258 may also expose a numm service based interface.

The AF1260 may provide application impact on traffic routing, provide access to NEFs, and interact with the policy framework for policy control.

In some embodiments, the 5GC 1240 may implement the edge calculation by selecting an operator/third party service that is geographically close to the point where the UE1202 attaches to the network. This may reduce latency and load on the network. To provide an edge calculation implementation, the 5GC 1240 may select a UPF1248 near the UE1202 and perform traffic steering from the UPF1248 to the data network 1236 via the N6 interface. This may be based on UE subscription data, UE location and information provided by AF 1260. In this way, the AF1260 may affect UPF (re) selection and traffic routing. Based on operator deployment, the network operator may permit AF1260 to interact directly with the relevant NFs when AF1260 is considered a trusted entity. Further, the AF1260 may expose a Naf service-based interface.

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.

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

The UE1302 can be communicatively coupled with AN 1304 via a connection 1306. Connection 1306 is shown as an air interface to enable communicative coupling, and may conform to a cellular communication protocol operating at millimeter-wave or sub-6 GHz frequencies, such as the LTE protocol or the 5G NR protocol.

UE1302 may include a host platform 1308 coupled to a modem platform 1310. Host platform 1308 may include application processing circuitry 1312, which may be coupled with protocol processing circuitry 1314 of modem platform 1310. The application processing circuitry 1312 may run various applications that source/converge application data for the UE 1302. The application processing circuitry 1312 may also implement one or more layers of operations to send/receive application data to/from the data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

Protocol processing circuitry 1314 may implement one or more layers of operations to facilitate the transmission or reception of data over connection 1306. Layer operations implemented by the protocol processing circuit 1314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

The modem platform 1310 may also include digital baseband circuitry 1316, which may implement one or more layer operations "below" the layer operations performed by the protocol processing circuitry 1314 in the 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/demapping, 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.

Modem platform 1310 may also include transmit circuitry 1318, receive circuitry 1320, RF circuitry 1322, and an RF front end (RFFE) 1324, which may include or be connected to one or more antenna panels 1326. Briefly, the transmit circuit 1318 may include digital-to-analog converters, mixers, intermediate Frequency (IF) components, and so forth; the receive circuitry 1320 may include analog-to-digital converters, mixers, IF components, and the like; RF circuitry 1322 may include low noise amplifiers, power tracking components, and the like; RFFE 1324 may include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beam forming components (e.g., phased array antenna components), and so on. The selection and arrangement of components of transmit circuitry 1318, receive circuitry 1320, RF circuitry 1322, RFFE 1324 and antenna panel 1326 (collectively, "transmit/receive components") may be specific to details of a particular implementation, such as whether the communication is TDM or FDM, at millimeter wave or sub-6 GHz frequencies, and so forth. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be arranged in the same or different chips/modules, and so on.

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

UE reception may be established by and via antenna panel 1326, RFFE 1324, RF circuitry 1322, receive circuitry 1320, digital baseband circuitry 1316, and protocol processing circuitry 1314. In some embodiments, the antenna panel 1326 may receive transmissions from the AN 1304 by receiving beamformed signals received by multiple antennas/antenna elements of one or more antenna panels 1326.

UE transmission may be established through and via protocol processing circuitry 1314, digital baseband circuitry 1316, transmit circuitry 1318, RF circuitry 1322, RFFE 1324, and antenna panel 1326. In some embodiments, the transmit components of UE 1304 may apply spatial filters to the data to be transmitted to form transmit beams that are transmitted by the antenna elements of antenna panel 1326.

Similar to the UE1302, an 1304 may include a host platform 1328 coupled with a modem platform 1330. Host platform 1328 may include application processing circuitry 1332 coupled with protocol processing circuitry 1334 of modem platform 1330. The modem platform may also include digital baseband circuitry 1336, transmit circuitry 1338, receive circuitry 1340, RF circuitry 1342, RFFE circuitry 1344, and antenna panel 1346. The components of the AN 1304 can be similar to and substantially interchangeable with the synonymous components of the UE 1302. In addition to performing data transmission/reception as described above, the components of AN 1308 may perform various logical functions including, for example, RNC functions (e.g., radio bearer management), uplink and downlink dynamic radio resource management, and data packet scheduling.

Fig. 14 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing the instructions of any one or more of the methodologies discussed herein, according to some example embodiments. In particular, fig. 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 utilizing node virtualization (e.g., NFV), hypervisor 1402 may be executed to provide an execution environment utilizing hardware resources 1400 to one or more network slices/subslices.

Processor 1410 may include, for example, processor 1412 and processor 1414. Processor 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.

Memory/storage 1420 may include main memory, disk storage, or any suitable combination thereof. Memory/storage 1420 may include, but is 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, and the like.

The communication resources 1430 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripherals 1404 or one or more databases 1406 or other network elements via a network 1408. For example, the communication resources 1430 can include wired communication components (e.g., for coupling via USB, ethernet, etc.), cellular communication components, NFC components, bluetooth

Component (or Bluetooth)

Low power consumption),

Components, and other communication components。

The instructions 1450 may include software, programs, applications, applets, apps, or other executable code for causing at least any of the processors 1410 to perform any one or more of the methods discussed herein. The instructions 1450 may reside, completely or partially, within at least one of: the processor 1410 (e.g., within a cache memory of the processor), the memory/storage 1420, or any suitable combination thereof. Further, any portion of instructions 1450 may be communicated to hardware resource 1400 from any combination of peripherals 1404 or database 1406. Thus, the memory of processor 1410, memory/storage 1420, peripherals 1404, and database 1406 are examples of computer-readable and machine-readable media.

Example procedure

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portion(s) or implementation thereof, of fig. 12-14 or some other diagram herein, may be configured to perform one or more processes, techniques, or methods, or portion(s) thereof, as described herein. One such process is depicted in fig. 15. For example, process 1500 may include: at 1505, offload subscription management information is retrieved based on a Radio Access Network (RAN) computing session identifier included in a RAN computing offload (RCo) session setup request. The process further comprises: at 1510, a request is made for a Policy Control Function (PCF) to establish a Session Management (SM) policy association with the PCF to retrieve Policy and Charging Control (PCC) rules.

Another such process is depicted in fig. 16. In this example, process 1600 includes: at 1605, a key is selected from a plurality of keys stored by a Subscriber Identity Module (SIM) based on information associated with the application. The process further comprises: at 1610, based on the selected key, communication is made with an application server associated with the application.

Yet another such process is depicted in fig. 17. In this example, process 1700 includes: at 1705, a registration request is received that includes an indication of a computing offload service for a User Equipment (UE). The process further comprises: at 1710, subscription data, including computing offload subscription data, is retrieved from a Unified Data Management (UDM) function. The process further comprises: at 1715, a UE context is generated based on the computing offload subscription data, the UE context including UE context information related to the computing.

For one or more embodiments, at least one component recited in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as recited in the example section below. For example, 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 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, can be configured to operate in accordance with one or more examples set forth in the examples section below.

Examples of the invention

Example 1 may include a method to support session establishment for a computing offload service.

Example 2 may include the method of example 1 or some other example herein, whereby a new network node "RAN computing CF" is introduced as an endpoint of the control plane of the computing offload session.

Example 3 may include the method of example 1 or some other example herein, wherein the new network node "RAN computing SF" is thereby introduced as an endpoint of a user plane computing offload session.

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

Example 5 may include the method of examples 1-3 or some other example herein, whereby the UE is enhanced to send computing offload slice selection assistance information (C-NSSAI) during a session establishment procedure.

Example 5B may include the method of examples 1-3 or some other example herein, whereby the UE is enhanced to send the S-NSSAI with a particular slice/service type (SST) value standardized for computing offload services during a session establishment procedure. This is an alternative to example 5.

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

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

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

Example 9 may include the method of examples 1-8 or some other example herein, whereby the PCF is enhanced to support PCC rules for a session that supports computing offload services.

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

Example specific to example 1:

example 11 may include the method of examples 1-10 or some other example herein, whereby a new NAS protocol for supporting RCo session management is introduced between the UE and the RAN computing CF.

Example 12 may include the method of example 5 or some other example herein, whereby the RAN selects "RAN compute CF" based on C-NSSAI.

Example 13 may include the method of examples 1 to 12 or some other example herein, whereby the computing CF verifies the session parameters with computing offload subscription information.

Example 14 may include the method of examples 1-7 or some other example herein, whereby the computing CF selects the computing SF based on C-NSSAI, CDNN, and COC.

Examples common to embodiments 2 and 3

Example 15 may include the method of examples 1-3 or some other example herein, whereby the RAN is enhanced to support a new NGAP procedure for managing RAN computation offload services provided by the RAN computation CF/SF.

Example specific to example 2:

example 16 may include the method of example 15 or some other example herein, whereby the SMF is enhanced to manage RAN computation offload services provided by the RAN computation CF/SF using a new NGAP procedure.

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

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

Example 19 may include the method of examples 1 to 10 and 15 to 18 or some other example herein, whereby an existing N1PDU session establishment procedure is enhanced to support computing offload services.

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

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

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

Example 23 may include the method of example 21 or some other example herein, whereby the URSP is enhanced to support a new request type for computing offload information as part of the routing descriptor.

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

Example specific to example 3:

example 25 may include the method of examples 1 to 10 and 15 or some other example herein, whereby a new N1 NAS procedure "RAN computing offload (RCo) session establishment" is introduced to support computing offload services.

Example 26 may include the method of example 15 or some other example herein, whereby the AMF uses a new NGAP procedure for managing RAN computing offload services.

Example 27 may include the method of example 15 or some other example herein, whereby a new NF is introduced to use a new NGAP procedure for managing RAN computation offload services provided by the RAN computation 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, the request including an indication of a RAN compute session identifier; and is

The offload subscription management information is retrieved based on the RAN computing the session identifier.

Example 29 includes the method of example 28 or some other example herein, wherein the RCo setup request further includes an indication of computing 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 comprises verifying the session parameters.

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

Example 32 includes the method of example 28 or some other example herein, wherein the method further comprises requesting that a Policy Control Function (PCF) establish a Session Management (SM) policy association with the PCF to retrieve the Policy and Charging Control (PCC) rule.

Example 33 includes the method of example 28 or some other example herein, wherein the method further comprises selecting a RAN computing Service Function (SF) based on the RCo session setup request.

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

Example 35 includes the method of any one of examples 28-34 or some other example herein, wherein the method is performed by a RAN computation Control Function (CF).

Example 36 includes a method comprising:

receiving a Protocol Data Unit (PDU) session establishment request including an indication of a Compute Offload Capability (COC); and is

Retrieving COC subscription information from a Unified Data Management (UDM) function; and is

And establishing the 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 setup request further includes an indication of: compute offload slice network selection assistance information (C-NSSAI), RAN compute session identifier, or Compute Data Network Name (CDNN).

Example 38 includes the method of example 36 or some other example herein, wherein the method further includes requesting the PCF to establish an SM policy association with the PCF to retrieve the PCC rule.

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

Example 40 includes the method of any one 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, the request including Computation Offload Capability (COC) information;

retrieving COC subscription information from the UDM based on the COC information; and is

A UE context is created for the RCo session based on the RCo setup request and the COC subscription information.

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

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

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

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

Example A1 may include a method of supporting a third-party trusted service to facilitate securely transferring a security anchor between an application client and a server.

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

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

Example A4 may include the method of example 2 or some other example herein, wherein the application service provider provisions the group key and the ICCID to the MNO or a key management server.

Example A5 may include the method of example 2 or some other example herein, wherein the SIM provider securely sends the group key and the list of sent ICCIDs to an application service provider.

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

Example A7 may include a method comprising: for application layer authentication, the application client uses the certificate installed in the eUICC by the UICC manufacturer. The application provider uses a certificate authority to sign both the application client device certificate and the application server certificate.

Example A8 may include a method comprising:

selecting a key from a plurality of keys stored by the SIM based on application information associated with the application; and is

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 examples 8-9 or some other example herein, wherein the key is a group key.

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

Example a12 may include the method of examples 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 to communicate with the server.

Example a13 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 a14 may include the method of examples 8-13 or some other example herein, wherein the method is performed by the UE or a portion thereof.

Example B1 may include a method for registering with a 5G system to obtain authorization and receive computing offload services.

Example B2 may include the method of example 1 or some other example herein, whereby the registration process is enhanced to support exchange of computing offload capability.

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 computing offload capability to the network during registration.

Example B4 may include the method of examples 1-3 or some other example herein, whereby the AMF is enhanced to verify the requested computing offloading capability against the UE subscription.

Example B5 may include the method of examples 1-4 or some other example herein, whereby the AMF is enhanced to provide the UE with allowed computing offload capability during registration.

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

Example B7 may include the method of example 3 or the method of some other example herein, whereby the USIM is enhanced to support the computing offload services indicator.

Example B8 includes a method comprising:

receiving a registration request including an indication of a computing offload service for a User Equipment (UE);

retrieving subscription data including computing offload subscription data from a Unified Data Management (UDM) function; and is

Generating a UE context based on the computing offload subscription data, the UE context including UE context information related to the computing.

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 B10 includes the method of example 9 or some other example herein, wherein the NSSAI includes an indication of one or more standardized slices/service types (SSTs) of the computer offload services.

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

Example B12 includes the method of example 8 or some other example herein, wherein the method further comprises performing 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 comprises encoding the registration accept message for transmission to the UE.

Example B14 includes the method of example 13 or some other example herein, wherein the registration acceptance message includes an indication of allowed general purpose computing offload capability.

Example B15 includes the method of any one 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, the registration request including an indication of the requested general purpose computing offload capability; and is provided with

A registration acceptance message is received that includes an indication of the allowed general computing 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 NSSAI includes an indication of one or more standardized slices/service types (SSTs) of the computer offload services.

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

Example X1 includes an apparatus of a Radio Access Network (RAN) computation Control Function (CF), the apparatus comprising:

a memory to store a RAN compute offload (RCo) session establishment request, the request including an indication of a RAN compute session identifier; and

processing circuitry coupled with the memory to:

retrieving offload subscription management information based on the RAN computing a session identifier; and is

The request causes a Policy Control Function (PCF) to 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 X1 or some other example herein, wherein the processing circuitry is further to verify the session parameters.

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

Example X4 includes the apparatus of example X1 or some other example herein, wherein the processing circuitry is further to select a RAN computing Service Function (SF) based on the RCo session setup request.

Example X5 includes the apparatus of example X1 or some other example herein, wherein the processing circuitry is further to establish the RCo session with the selected RAN computing SF.

Example X6 includes the apparatus of any one of examples X1-X5 or some other example herein, wherein the computing 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:

selecting a key from a plurality of keys stored by a Subscriber Identity Module (SIM) based on information associated with an application; and is

Based on the selected key, communicating with an application server associated with the application.

Example X8 includes the one or more computer-readable media of example X7 or some other example herein, wherein the application information comprises 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 X10 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 the additional key.

Example X11 includes the one or more computer-readable media of example X10 or some other example herein, wherein the additional key comprises a UICC-specific key, an application-specific 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:

receiving a registration request including an indication of a computing offload service for a User Equipment (UE);

retrieving subscription data including computing offload subscription data from a Unified Data Management (UDM) function; and is

Based on the computing offload subscription data, a UE context is generated that includes UE context information related to the computing.

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 slices/service types (SSTs) for computer offload services.

Example X15 includes 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 the initial authentication.

Example X16 includes 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 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 the registration accept message for transmission to the UE.

Example X18 includes the one or more computer-readable media of example X17 or some other example herein, wherein the registration acceptance message includes an indication of the general computing offload capability allowed.

Z01 may comprise an apparatus comprising means for performing one or more elements of a method described in or relating 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 that, when executed by one or more processors of an electronic device, cause 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 comprise an apparatus comprising logic, modules or circuitry to perform one or more elements of a method described in or relating 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 in connection with any of examples 1-X18 or portions thereof.

Z05 may comprise an apparatus comprising: one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process as described in or in connection with any of examples 1-X18 or portions thereof.

Z06 may comprise a signal as described in or in connection with any one of examples 1-X18 or portions thereof.

Z07 may include a datagram, packet, frame, fragment, protocol Data Unit (PDU), or message as described in or in relation to any of examples 1-X18, or portions thereof, or otherwise described in this disclosure.

Z08 may comprise a signal encoded with data as described in or in connection with any of examples 1-X18 or portions thereof or otherwise described in this disclosure.

Z09 can include a signal encoded with a datagram, packet, frame, fragment, protocol Data Unit (PDU), or message as described in or in relation to any of examples 1-X18 or portions or parts thereof or otherwise described in this disclosure.

Z10 may comprise an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process as described in or in connection with any of examples 1-X18 or portions thereof.

Z11 may comprise a computer program comprising instructions, wherein the program is executable by a processing element to cause the processing element to perform a method, technique or process as described in or in connection with any of examples 1-X18 or portions thereof.

Z12 may comprise 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 comprise a system for providing wireless communication as shown and described herein.

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

Any of the above examples can be combined with any other example (or combination of examples) unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the 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 otherwise used herein, the terms, definitions, and abbreviations may be consistent with the terms, definitions, and abbreviations defined in 3gpp TR 21.905 v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein.

The 3GPP third generation partnership BFD beam failure detection CID cell ID (e.g.,

partner plan BLER block error rate positioning method

4G fourth generation BPSK binary phase shift key CIM public information model

5G fifth generation 35 controlled CIR carrier-to-interference ratio

BRAS broadband remote access CK encryption key of 5GC 5G core network

ACK acknowledgement server CM connection management

Optional selection when AF application function BSS business support system is in condition

AM acknowledged mode BS base station CMAS commercial mobility

AMBR aggregate maximum BSR buffer status report alert service

Bit rate notification CMD command

CMS cloud management system for AMF access and mobility BW bandwidth

The bandwidth part CO of the management function BWP is optional when the part CO is in accordance with the condition

AN access network C-RNTI cell wireless CoMP coordinated multipoint

ANR automatic neighbor relation electric network temporary identity CORESET control resource

AP application protocol, heaven CA carrier aggregation, acknowledgement

COTS commercial spot goods for cable port and access point certificate center

API application programming interface CAPEX capital expenditure CP control plane, cycle

APN access point name CBRA based on competition ring prefix and connection point

ARP distribution and retention preferred random access CPD connection point descriptor

First-level CC component carrier, national CPE customer terminal equipment

ARQ automatic repeat request home code, password verification and CPICH common pilot

Assessment channel of CCA clear channel of AS access layer

ASN.1 abstract syntax CCE control channel element CQI channel quality indication

Marking a CCCH common control channel symbol

AUSF authentication server power CE coverage enhancement CPU CSI processing unit,

CDM content distribution network central processing unit

AWGN additive Gaussian white CDMA C/R Command/response field

Noise CFRA contention-free random access CRAN cloud radio access

BAP backhaul adaptation protocol access network, cloud RAN

CRB (common resource Block) of BCH (broadcast channel) CG cell group

BER bit error rate CI cell identification CRC cyclic redundancy check

CRI channel state information DMTF distributed administrative EGPRS enhanced GPRS

Resource indicator, CSI-RS service set EIR equipment identity register

eLAA enhanced authorization secondary for resource indicator DPDK data plane development

C-RNTI cell RNTI suite assisted access and enhancement mode

CS circuit switching DM-RS and DMRS LAA solution

CSAR cloud service archiving and adjusting reference signal EM (effective memory) network element manager

CSI channel state information DN data network eMBB enhanced mobile bandwidth

Radio bearer for CSI-IM CSI interference measurement DRB data

CSI-RS CSI reference signal EMS-loaded network element management system

CSI-RSRP CSI reference DRS discovery reference signals eNB evolved node B,

signal reception power DRX discontinuous reception E-UTRAN node B

CSI-RSRQ CSI reference DSL Domain specific language, EN-DC E-UTRA-

Signal reception quality digital subscriber line NR dual connectivity

CSI-SINR CSI signal interference DSLAM DSL receiving EPC evolution type packet core

Noise ratio input multiplexer core

Enhanced CSMA carrier sense DwPTS downlink pilot EPDCCH

Multiple access frequency slot PDCCH, enhanced object

CSMA/CA Ethernet Local Area Network (LAN) Ethernet downlink control channel with collision avoidance

Exempt CSMA network EPRE per resource element

CSS common search space, E2E end-to-end energy

eCCA extended idle channel EPS evolution type grouping system for cell dedicated search space

CTS clear to send evaluation, extended CCA system

CW code ECCE enhanced control signal EREG enhanced REG,

CWS contention window size channel element, enhanced resource element group

D2D device-to-device CCE ETSI European Telecommunications Standard

DC double connectivity, straight ED energy detection association

Stream EDGE GSM evolution ETWS earthquake and tsunami prediction

DCI downlink control (GSM evolution) alarm enhancement system

An information-intensive data rate eUICC embedded UICC,

DF deploys embedded general integrated circuit of preferred EGMF exposure management

DL downlink function card

E-UTRA evolved FFT electrical services

GSM global system for mobile communications with further enhanced UTRA feLAA

E-UTRAN evolved authorization assisted access, access system, mobile expert group

UTRAN step enhanced LAA (group Spial Special)

EV2X enhanced V2X FN frame number Mobile)

F1AP F1 application protocol FPGA field programmable gate GTP GPRS tunnel protocol

F1-C F1 control plane array-interfacing device

fFR frequency range GTP-U user plane

GPRS tunneling protocol for F1-U F1 user plane to G-RNTI GERAN

The GTS dormant signal (and) is a temporary identity of the oral radio network

FACCH FAST CHANNEL GERAN GSM WUS RELATED)

Global unique control channel EDGE RAN and GSM GUMMEI

FACCH/F fast associated EDGE radio access network MME identifier

Control channel/full rate network GUTI globally unique temporary

FACCH/H fast associated GGSN gateway GPRS support UE identity

HARQ hybrid ARQ for control channel/half rate node,

GLONASS HARQ

FAUSCH fast uplink (English: global HANDO handoff)

Signaling channel 50Navigation Satellite HFN hyper frame number

FB function Block System (Global navigation satellite HHO hard Handover)

FBI feedback information satellite system)) HLR home location registration

FCC U.S. federal communication gNB next generation node B device

HN home network in committee gNB-CU gNB

FCCH frequency correction channel central unit, next generation node HO handover

FDD B Central Unit HPLMN local public

FDM frequency division multiplexing gNB-DU gNB (gigabit-capable radio network-to-radio network) land mobile network

FDMA (frequency division multiple Access) distributed unit and next generation HSDPA (high speed Downlink packet Access) high-speed downlink

FE front-end point B distributed unit link packet access

FEC forward error correction GNSS global navigation satellite HSN frequency hopping sequence number

FFS (fringe field switching) high-speed packet access of HSPA (high speed packet Access) system to be further researched

GPRS general packet radio HSS home subscriber server

ISO international standardization group for HSUPA high-speed uplink IMC IMS certificate

Route packet access IMEI international mobile equipment organization

HTTP hypertext transfer protocol ISP internet service provider

International Mobile group supplier for the International Mobile Gateway Initiative (IMGI)

HTTPS secure hypertext transfer protocol (IWF) interworking function

Transmission protocol (https is a basic IMPI IP multimedia private I-WLAN interworking WLAN

Http/1.1 over SSL, constraint of identity convolutional code

I.e., port 443) IMPUIP multimedia public length, USIM

I-Block information Block identity body key

ICCID IC card label IMS IP multimedia subsystem kB kilobyte (1000)

Byte identification system)

IAB Integrated Access and Return IMSI International Mobile subscriber Kbps kilobits per second

Encryption key for transmitting identity Kc

inter-ICIC inter-cell interference coordination IoT Internet of things Ki individual subscriber authentication

Adjusting IP internet protocol key

ID identity, identifier Ipsec IP security, mutual KPI Key Performance indicators

KQI key quality index of security of IDFT (inverse discrete Fourier transform) networking protocol

Transforming IP-CAN IP connectivity KSI key set identifiers

Ie information element access network ksps kilo symbols per second

IBE in-band transmission IP-M IP multicast KVM kernel virtual machine

IEEE electric and electronic IPv4 Internet protocol version L1 layer 1 (physical)

Institute of engineers this 4-layer)

IEI information element identification IPv6 Internet protocol version L1-RSRP layer 1 parameter

Symbol 6 test signal received power

The IEIDL information element identifies IR Infrared L2 layer 2 (data)

Symbol data length IS synchronous link layer)

IETF Internet engineering task IRP integration reference point L3 layer 3 (network)

Service group ISDN integrated services digital layer)

LAA authorization-assisted access of IF infrastructure network

IM interference measurement and mutual ISIM IM service identity mode LAN

Modulation, IP multimedia block LBT listen before talk

LCM lifecycle management MANO management and orchestration of MO measurement objects, moves

LCR low chip rate MBMS multimedia broadcast mobile station calling-out

LCS location service and multicast service MPBCH MTC object

LCID logical channel ID MBSFN multimedia broadcast physical broadcast channel

LI layer index multicast service single frequency network MPDCCH MTC article

LLC logical link control, MCC Mobile Country code physical Downlink control channel

Low-layer compatibility MCG master cell group MPDSCH MTC

LPLMN local PLMN MCOT maximum channel occupation physical downlink shared channel

LPP LTE positioning protocol time MPRACH MTC thing

LSB least significant bit MCS modulation and coding strategy random access channel

LTE long term evolution MPUSCH MTC (human resource control channel) substance

LWA LTE-WLAN aggregation MDAF management data analysis physical uplink shared channel

Multi-protocol label switching (MPLS) with combined functions

LWIP adopts IPSec tunnel MDAS management data analysis and conversion

LTE/WLAN non-service MS mobile station

Line level integrated MDT MSB most significant bit

LTE long term evolution ME mobile equipment MSC mobile switching center

M2M machine to machine MeNB master eNB MSI minimum system information,

MAC medium access control MER message error rate MCH scheduling information

(protocol layer context) MGL measurement gap length MSID mobile station identifier

MAC message authentication code MGRP measurement gap repetition MSIN mobile station identification number

(Security/encryption Up-Down cycle MSISDN Mobile subscriber

Text) MIB Master information Block, pipe ISDN number

MAC-A for authentication and management information base MT mobile station called,

MAC MIMO multi-input multi-output mobile terminal for key agreement

(TSG T WG3 upper and lower MLC mobile location center MTC machine type communication)

Text) MM mobility management mMTC mass MTC,

MAC-I for signaling mobility management of MME (mobility management entity) in mass machine communication

60-body MU-MIMO multiuser for data integrity of information

MAC (TSG T WG3 MN master node MIMO)

Context) MnS management service MWUS MTC wakeup letter

Number, MTC WUS NPBCH narrowband physical NWUS narrowband wakeup signal

NACK negative acknowledgement broadcast channel number, narrowband WUS

NAI network access identifier NPDCCH narrowband physical NZP non-zero power

NAS non-access stratum, non-downlink control channel O & M operation and maintenance

Access layer NPDSCH narrowband physical ODU2 optical channel data sheet

NCT network connectivity extension downlink shared channel element-type 2

Plop NPRACH narrowband physical OFDM orthogonal frequency division multiplexing

OFDMA orthogonal frequency division multiple of NC-JT noncoherent joint transmission random access channel

Input NPUSCH narrowband physical address

NEC network capability exposing uplink shared channel OOB out-of-band

NE-DC NR-E-NPSS narrow-band master synchronization OOS out-of-sync

UTRA Dual connectivity number OPEX operational cost

NEF network exposure function NSSS narrowband auxiliary synchronization information OSI other system information

NF network function number OSS operation support system

NFP network forwarding path NR new air interface, adjacent area OTA air

PAPR (peak-to-average power ratio) of forwarding path relation of NFPD (network File packet data protocol) network

Descriptor NRF NF repository function PAR peak-to-average ratio

NFV network function virtual NRS narrowband reference signal PBCH physical broadcast channel

Method for realizing NS network service PC power control

Non-independent networking operator computer of NFVI NFV infrastructure NSA

NFVO NFV orchestrator as a mode PCC primary component carrier,

NG next generation, sub-generation NSD network service description main CC

Surrogate Pcell primary cell

NGEN-DC NG-RAN NSR network service record PCI physical cell ID,

E-UTRA-NR dual connectivity NSSAI network slicing selection of physical cell identities

Sexual assistance information PCEF policy and charging enforcement

NM network manager S-NNSAI Single line function

NSSAI PCF policy control function of NMS network management system

N-PoP point-of-presence NSSF network slice selection PCRF policy control and counting

NMIB, N-MIB narrowband function fee rule function

MIB NW network PDCP packet data convergence

Protocol, packet data convergence PP, PTP point-to-point link shared channel

Protocol layer PPP point-to-point protocol QAM Quadrature amplitude modulation

QoS of PDCCH physical downlink PRACH physical RACH QCI identifier

Physical resource block class of path control channel PRB

QCL quasi co-location of PDCP packet data convergence PRG physical resource block group

ProSe proximity services, base QFI QoS flow ID,

PDN packet data network, qoS flow identifier for neighbor service

Public data network PRS positioning reference signal QoS quality of service

PDSCH physical downlink PRR packet reception wireless QPSK quadrature (quadriphase)

Circuit shared channel electrical phase shift keying

PDU protocol data unit PS packet service QZSS quasi-zenith satellite system

PEI permanent equipment identification PSBCH physical side chain system

Random access of symbol broadcast channel RA-RNTI

PFD packet flow description PSDCH physical side chain RNTI

P-GW PDN gateway downlink channel RAB radio access bearer

PHICH physical hybrid PSCCH physical side bearer, random access burst

ARQ indicator channel control channel RACH random access channel

PHY physical layer PSFCH physical side chain RADIUS remote authentication dial

PLMN public land mobile feedback channel number user service

Network PSSCH physical side-chain RAN radio Access network

PIN shared channel network

PM Performance measurement PSCell Primary SCell RAND random number (for

PMI precoding matrix refers to PSS primary synchronization signal authentication)

RAR random access response of standard PSTN public switched telephone

PNF physical network function network RAT radio access technology

PNFD physical network function PT-RS phase tracking reference technique

Descriptor signal RAU routing area update

PNFR physical network function PTT one-key RB resource block, wireless

Recording PUCCH physical uplink electrical bearers

POC cellular-based link control channel RBG resource block group

PTT PUSCH physical uplink REG resource element group

Rel release edition, radio resource control SAP service access point

REQ request layer SAPD service access point delineation

RF radio frequency RRM radio resource management descriptor

RI rank indicator mechanism SAPI service access point mark

RIV resource indicator value RS reference signal identifier

RL radio link RSRP reference Signal reception SCC Secondary component Carrier,

RLC radio link control power auxiliary CC

Scell secondary cell for receiving reference signal RSRQ (radio reference quality) of system and radio link control

Layer quality SC-FDMA single carrier frequency

RLC AM RLC RSSI received signal strength division multiple access

SCG secondary cell group

RLC UM RLC uncertain RSU roadside units SCM security context

Acknowledged mode RSTD reference signal time management

RLF radio link error SCS subcarrier spacing

Barrier RTP real time protocol SCTP stream control transmission protocol

RLM radio Link supervision (RLM) Ready to Send protocol

SDAP service data adaptation for controlling RTT round trip time

RLM-RS for RLM Rx receive, protocol, service data adaptation

Reference signal receiver protocol layer of

RM registration management S1AP S1 application protocol SDL supplemental downlink

RMC reference measurement channel S1-MME for controlling SDNF structured data storage

RMSI MSI-remaining, plane-remaining S1 storage network function

Use of residual minimum system information S1-U for user plane SDP session description protocol

S1 SDSF structured data storage of RN relay node

RNC radio network control S-GW service gateway storage function

System S-RNTI SRNC wireless SDU service data unit

RNL radio network layer network temporary identity SEAF security anchoring work

RNTI radio network temporary S-TMSI SAE mobility

Time identifier mobile station identifier SeNB secondary eNB

ROHC robust header compression SA independent operation mode SEPP security edge protection

RRC radio resource control SAE system architecture evolution proxy

SQN sequence number TAG timing advance group for SFI slot format indication

SFTD space frequency time diversity, SR scheduling request TAU tracking area update

SFN and frame time difference SRB signaling radio bearer TB transport blocks

SFN system frame number or single carrier TBS transport block size

Frequency network SRS sounding reference signal TBD to be defined

SgNB auxiliary gNB SS synchronization signal TCI transmission configuration indication

SGSN serving GPRS-to-SSB SS block symbol

Support node SSBRI SSB resource indication TCP transport communication protocol

S-GW service gateway symbol TDD time division duplex

SI system information SSC session and service connection TDM time division multiplexing

SI-RNTI SYSTEM INFORMATION CONTINUOUS TDMA-TDMA

RNTI SS-RSRP synchronous TE-based terminal equipment

Reference signal reception (TEID) tunnel endpoint identification for SIB system information block signals

SIM subscriber identity module power symbol

SIP session initiation protocol SS-RSRQ based on synchronous TFT traffic flow template

Reference signal reception (TMSI) temporary mobile subscriber for SiP system-in-package (SIP) signals

SL side chain mass identity

SLA service level agreement SS-SINR based on synchronous TNL transport network layer

sM session management signal-to-interference-and-noise ratio (TPC) transmission power control

SMF session management function SSS auxiliary synchronization signal TPMI (precoding matrix sending) for sending precoding matrix

SMS short message service SSSG search space cluster array indicator

SMSF SMS functional group TR technical report

SMTC SSSIF search space TRP and TRxP transmission interface based on SSB

Measurement timing configuration set indicator setpoint

SN auxiliary node, serial number SST slice/service type TRS tracking reference signal

SoC system-on-chip SU-MIMO single-user TRx transceiver

SON self-organizing network MIMO TS technical specification and technology

SpCell Special cell SUL supplement uplink technology standard

SP-CSI-RNTI semi-permanent TA timing advance and TTI transmission time interval

Sexual CSI RNTI tracking area Tx transmission, transmission,

SPS semi-permanent scheduling TAC tracking area code transmitter

U-RNTI UTRAN MODULE-LESS VRB VIRTUAL RESOURCE BLOCKS

Air WiMAX global microwave access for private search of radio network temporary identity USS UE

UART universal asynchronous receive inter-entry interoperability

UTRA UMTS terrestrial WLAN-less wireless local area network

UCI uplink control line electric access WMAN wireless metropolitan area network

Information UTRAN universal terrestrial WPAN-free wireless personal area

UE user equipment line access network domain network

UDM unified data management UwPTS uplink pilot X2-C X-control plane

UDP user datagram co-frequency time slot X2-U X-user plane

Meeting V2I vehicle to infrastructure XML extensible markup language

UDR unified data store declaration

Library V2P vehicle-to-pedestrian XRES expected user response

UDSF unstructured data V2V vehicle-to-vehicle XOR

Storage network function V2X vehicle-to-everything ZC Zadoff-Chu

ZP zero power of VIM virtual basic frame of UICC universal integrated circuit

Card structure manager

UL uplink VL virtual links

UM unacknowledged mode VLAN virtual LAN,

UML unified modeling language virtual local area network

UMTS universal mobile telecommunications VM virtual machine

System VNF virtualization of network power

UP user plane capability

UPF user plane function VNFFG VNF forwarding graph

URI URL VNFFGD VNF forwarding

Symbolic map descriptor

URL uniform resource location VNFM VNF manager

VoIP-compliant IP voice-over-IP interconnection

URLLC high-reliability low-time network protocol voice

Extended VPLMN visited public land

USB universal serial bus mobile network

USIM universal subscriber identity VPN virtual private network

Term(s)

For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein.

The term "circuitry" as used herein refers to, a portion of, or includes hardware components configured to provide the described functionality, such as: electronic circuits, logic circuits, processors (shared, dedicated, or group) and/or memories (shared, dedicated, or group), application Specific Integrated Circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable Logic Devices (PLDs), complex PLDs (complex PLDs, CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable socs), digital Signal Processors (DSPs), and the like. 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) and program code for performing the functions of the 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 circuit" as used herein refers to, is part of, or includes the following circuitry: the circuit is capable of sequentially and automatically performing a sequence of operational or logical operations or recording, storing and/or transmitting digital data. The processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuit" 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 tri-core processor, a quad-core processor, and/or any other device capable of executing or otherwise manipulating computer-executable instructions, such as program code, software modules, and/or functional processes. The processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. The one or more hardware accelerators may include, for example, computer Vision (CV) and/or Deep Learning (DL) accelerators. The terms "application circuitry" and/or "baseband circuitry" may be considered synonymous with "processor circuitry" and may be referred to as "processor circuitry".

The term "interface circuit" as used herein refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I/O interface, a peripheral component interface, a network interface card, and the like.

The term "user equipment" or "UE" as used herein refers to a device having radio communication capabilities and may describe a remote user of network resources in a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as: a client, a mobile phone, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio device, a reconfigurable mobile device, etc. Further, the terms "user equipment" or "UE" may include any type of wireless/wired device or any computing device that includes a wireless communication interface.

The term "network element" as used herein refers to an entity or virtualized device and/or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with and/or referred to as: networked computers, networking hardware, network devices, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, and the like.

The term "computer system" as used herein refers to any type of interconnected electronic devices, computer devices, or components thereof. Furthermore, the terms "computer system" and/or "system" may refer to components of computers that are communicatively coupled to each other. Moreover, the terms "computer system" and/or "system" may refer to multiple computing devices and/or multiple computing systems communicatively coupled with one another and configured to share computing and/or networking resources.

The terms "appliance" (application), "computer appliance," and the like, as used herein, refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or simulates or is otherwise dedicated to providing specific computing resources.

The term "resource" as used herein refers to an entity or virtual device, an entity or virtual component within a computing environment, and/or an entity or virtual component within a particular device, e.g., a computer device, a mechanical device, memory space, processor/CPU time, processor/CPU usage, processor and accelerator load, hardware time or usage, power, input/output operations, ports or network sockets, channel/link allocations, throughput, memory usage, storage, networks, databases and applications, workload units, etc. "hardware resources" may refer to computing, storage, and/or network resources provided by the physical hardware element(s). "virtualized resources" may refer to computing, storage, and/or network resources provided by a virtualization infrastructure to applications, devices, systems, etc. The term "network resource" or "communication resource" may refer to a resource accessible by a computer device/system via a communication network. The term "system resource" may refer to any kind of shared entity for providing a service, and may include computing and/or network resources. A system resource can be thought of as a collection 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, whether tangible or intangible, for communicating data or a stream of data. The term "channel" may be synonymous and/or equivalent to the following term: "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and/or any other similar term denoting a channel or medium through which data is communicated. Further, the term "link" as used herein refers to a connection that occurs between two devices over a RAT for the purpose of transmitting and receiving information.

The terms "instantiating" … …, "instantiation," and the like, as used herein, refer to the creation of an instance. An "instance" also refers to a specific occurrence of an object, e.g., an object may occur during execution of program code.

The terms "couple," "communicatively couple," and derivatives thereof are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but yet 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 coupled with each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements are in contact with each other via a communication means, including by a wire or other interconnection, by a wireless communication channel or link, or the like.

The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to an individual content of an information element, or a data element containing content.

The term "SMTC" refers to an SSB-based measurement timing configuration configured by an SSB-measurementtimingtconfiguration.

The term "SSB" refers to the SS/PBCH block.

The term "primary cell" refers to an MCG cell operating on a primary frequency, which is the cell when a UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

For DC operation, the term "primary SCG cell" refers to an SCG cell where the UE performs random access when performing reconfiguration with a synchronization procedure.

For CA-configured UEs, the term "secondary cell" refers to a cell that provides additional radio resources outside of a particular cell.

For a UE configured with DC, the term "secondary cell group" refers to a subset of serving cells that includes the PSCell and zero or more secondary cells.

For a UE under RRC _ CONNECTED that is not configured with CA/DC, the term "serving cell" refers to the primary cell, and there is only one serving cell consisting of the primary cell.

For a UE configured with CA/DC under RRC _ CONNECTED, the term serving cell(s) refers to the set of cells that includes the special cell(s) and all secondary cells.

For DC operation, the term "special cell" refers to the PCell of the MCG or the PSCell of the SCG; in other cases, the term "special cell" refers to Pcell.

Claims (18)

1. An apparatus of a Radio Access Network (RAN) computation Control Function (CF), comprising:

a memory to store a RAN compute offload (RCo) session setup request, the RCo session setup request including an indication of a RAN compute session identifier; and

processing circuitry coupled with the memory to:

retrieving offload subscription management information based on the RAN computing a session identifier; and is

The request causes a Policy Control Function (PCF) to 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 circuit is further to verify session parameters.

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

4. The apparatus of claim 1, wherein the processing circuitry is further to select a RAN computing Service Function (SF) based on the RCo session setup request.

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

6. The apparatus of any of claims 1-5, wherein the computing 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:

selecting a key from a plurality of keys stored by a Subscriber Identity Module (SIM) based on information associated with an application; and is

Communicating with an application server associated with the application based on the selected key.

8. The one or more computer-readable media of claim 7, wherein the application information comprises 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 additional key comprises 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:

receiving a registration request including an indication of a computing offload service for a User Equipment (UE);

retrieving subscription data including computing offload subscription data from a Unified Data Management (UDM) function; and is

Generating a UE context based on the computing offload subscription data, the UE context comprising UE context information related to the computing.

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 comprises 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 as claimed in claim 12, wherein the media further stores instructions for causing the AMF to perform Access and Mobility (AM) policy association establishment or modification.

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 allowed general purpose computing offload capability.

Images