Abstract: Systems, apparatuses, methods, and computer-readable media, are provided for offloading computationally intensive tasks from one computer device to another computer device taking into account, inter alia, energy consumption and latency budgets for both computation and communication. Embodiments may also exploit multiple radio access technologies (RATs) in order to find opportunities to offload computational tasks by taking into account, for example, network/RAT functionalities, processing, offloading coding/encoding mechanisms, and/or differentiating traffic between different RATs. Other embodiments may be described and/or claimed.

Abstract: Various approaches are provided for enabling Edge Dual Deployment (EDD). EDD includes Multi-access edge computing (MEC) Dual Deployments (MDD) initialization performed as a preliminary step before the actual registration, as a mechanism to allow the two platforms (EES and MEC platform) to communicate directly. MDD establishment is a dual registration mechanism of the edge application in the EDD environment. MDD update and closing are analogous registration update and de-registration processes, with both sub-cases.

Abstract: An example method includes, based on a request from the third-party entity to join the edge network, initiating a Zero-Knowledge Proof (ZKP) protocol by generating a common reference string (CRS) to establish public parameters within the edge network; transmitting the CRS to the third-party entity and an authorization server; obtaining an authorization of the third-party entity from the authorization server, the authorization server authenticating the third-party entity based on a ZKP proof constructed by the third-party entity using the CRS and a private credential of the third-party entity; authorizing the third-party entity to join the edge network based on the authorization; and deploying a smart contract on a distributed ledger, wherein the smart contract specifies conditions under which the third-party entity is granted access to the edge network, and wherein the distributed ledger records transactions related to access permissions of the third-party entity.

Abstract: Disclosed embodiments are related to techniques for implementing Vehicle-to-Everything (V2X) communications in Multi-access Edge Computing (MEC) systems and networks. V2X system scenarios characterized by high mobility and dynamic topologies, where the accuracy and timeliness of radio network information, location information may be hampered by environmental conditions and deployment density of network infrastructure. The disclosed embodiments provide a V2X Information Service (VIS) framework for cooperative acquisition, partitioning, and distribution of information for efficient, journey-specific quality-of-service (QoS) predictions. The VIS framework identifies space/time correlations between radio condition/quality data collected in V2X system(s) and a vehicle's planned journey for better prediction of the radio conditions/quality of the communication network along the designated route. As a consequence, the VIS may expose journey-specific information about the QoS prediction to authorized devices.

Abstract: A local server includes a controller configured to select a processing function for processing offload, and receive, from a traffic filter, target data that originates from a local network; and a processing platform comprising one or more processors and configured to apply the processing function to the target data to obtain processed data; and wherein the controller is further configured to send the processed data to a remote server for remote processing.

Abstract: Disclosed embodiments are related to techniques for implementing Multiple Access Management Services (MAMS), Multi-access Edge Computing (MEC), and 3GPP Fifth Generation (5G) technologies. Embodiments include enhanced application programming interfaces (APIs) that allow applications to influence multi-access (MA) traffic steering decisions, and also get informed of various MA traffic steering modes. Disclosed embodiments also include techniques to enable coexistence between MEC-based MAMS systems and 5G MA traffic steering mechanisms. Other embodiments may be described and/or claimed.

Abstract: A system configured to track network slicing operations within a 5G communication network includes processing circuitry configured to determine a network slice instance (NSI) associated with a QoS flow of a UE. The NSI communicates data for a network function virtualization (NFV) instance of a Multi-Access Edge Computing (MEC) system within the 5G communication network. Latency information for a plurality of communication links used by the NSI is retrieved. The plurality of communication links includes a first set of non-MEC communication links associated with a radio access network (RAN) of the 5G communication network and a second set of MEC communication links associated with the MEC system. A slice configuration policy is generated based on the retrieved latency information and slice-specific attributes of the NSI. Network resources of the 5G communication network used by the NSI are reconfigured based on the generated slice configuration policy.

Abstract: Methods, systems, and computer programs are presented for sharing information among multiple Mobility as a Service (MaaS) systems for presenting service information to users. One system includes means for receiving, by a multi-access edge computing (MEC) application, parameters of a global quality of service (QoS) prediction model, and means for sending, to a local prediction function (PF), an update of a local QoS prediction model. Further, the system includes means for detecting a journey of a vehicle requested by a user, and means for sending to the local PF, a request for a value of the QoS along the journey. The value of the QoS is a measure of quality of transportation services delivered during the journey. The system further includes means for receiving the predicted value of the QoS along the journey, and means for providing, by the MEC application, the predicted value of the QoS to the vehicle.

Abstract: Various approaches are provided for enabling Edge Dual Deployment (EDD). EDD includes Multi-access edge computing (MEC) Dual Deployments (MDD) initialization performed as a preliminary step before the actual registration, as a mechanism to allow the two platforms (EES and MEC platform) to communicate directly. MDD establishment is a dual registration mechanism of the edge application in the EDD environment. MDD update and closing are analogous registration update and de-registration processes, with both sub-cases.

Abstract: Various systems and methods are described implementing a multi-access edge computing (MEC) based system to realize MEC application registration and application data functions for MEC frameworks. In an example, operations are performed at a MEC orchestrator to maintain a registry of applications within a MEC system or among a federation of MEC systems, with the MEC orchestrator performing operations including: identifying, based on the communications with a plurality of MEC hosts, a plurality of applications provided by the MEC hosts in the MEC system (or, by applications provided by a plurality of MEC hosts in a federation); storing and synchronizing application information for the plurality of applications in a registry; and communicating the application information from the registry to an entity of the MEC system or to an entity federated with the MEC system.

Abstract: Embodiments herein may include systems, apparatuses, methods, and computer-readable media, for a multi-access edge computing (MEC) system. An apparatus for MEC may include a communication interface, a local cost measurements module, and a service allocation module. The communication interface may receive, from a UE, a request for a service to be provided to the UE. The local cost measurements module may collect a set of local cost measurements for the service. The service allocation module may determine to allocate the service to a MEC host based on an allocation policy related to a cost for the MEC host to provide the service or a cost for a service provider to provide the service in view of the one or more local cost measurements. Other embodiments may be described and/or claimed.

Abstract: Various aspects of methods, systems, and use cases for verification and attestation of operations in an edge computing environment are described, based on use of a trust calculus and established definitions of trustworthiness properties. In an example, an edge computing verification node is configured to: obtain a trust representation, corresponding to an edge computing feature, that is defined with a trust calculus and provided in a data definition language; receive, from an edge computing node, compute results and attestation evidence from the edge computing feature; attempt validation of the attestation evidence based on attestation properties defined by the trust representation; and communicate an indication of trustworthiness for the compute results, based on the validation of the attestation evidence. In further examples, the trust representation and validation is used in a named function network (NFN), for dynamic composition and execution of a function.

Abstract: Systems, apparatuses, methods, and computer-readable media, are provided for offloading computationally intensive tasks from one computer device to another computer device taking into account, inter alia, energy consumption and latency budgets for both computation and communication. Embodiments may also exploit multiple radio access technologies (RATs) in order to find opportunities to offload computational tasks by taking into account, for example, network/RAT functionalities, processing, offloading coding/encoding mechanisms, and/or differentiating traffic between different RATs. Other embodiments may be described and/or claimed.

Abstract: A named function network (NFN) system includes a routing node, a function generation node, and a server node. The routing node receives requests for new functions, the requests including data values for generating the new functions. The function generation node receives the data values from the routing node and generates a new function for the NFN using the data values. The server node receives a request from the routing node to execute the new function, executes the new function, and transmits results of the execution to the routing node.

Abstract: A system configured to track network slicing operations within a 5G communication network includes processing circuitry configured to determine a network slice instance (NSI) associated with a QoS flow of a UE. The NSI communicates data for a network function virtualization (NFV) instance of a Multi-Access Edge Computing (MEC) system within the 5G communication network. Latency information for a plurality of communication links used by the NSI is retrieved. The plurality of communication links includes a first set of non-MEC communication links associated with a radio access network (RAN) of the 5G communication network and a second set of MEC communication links associated with the MEC system. A slice configuration policy is generated based on the retrieved latency information and slice-specific attributes of the NSI. Network resources of the 5G communication network used by the NSI are reconfigured based on the generated slice configuration policy.

Abstract: An architecture to allow Multi-Access Edge Computing (MEC) billing and charge tracking, is disclosed. In an example, a tracking process, such as is performed by an edge computing apparatus, includes: receiving a computational processing request for a service operated with computing resources of the edge computing apparatus from a connected edge device within the first access network, wherein the computational processing request includes an identification of the connected edge device; identifying a processing device, within the first access network, for performing the computational processing request; and storing the identification of the connected edge device, a processing device identification, and data describing the computational processes completed by the processing device in association with the computational processing request.

Abstract: Techniques for maintaining service continuity in a 5G NR network in communication with a MEC system and an edge application (EDGEAPP) system are disclosed. A notification message originating from a service management function (SMF) of a core network (CN) is decoded at a network exposure function (NEF) of the CN. The notification message includes a UE IP address change of a UE. A private IP address of the UE is determined based on the UE IP address change. A query with the private IP address is encoded for transmission to a NAT server. A response from the NAT server is decoded. The response includes a public IP address and a UE ID of the UE. The public IP address corresponds to the private IP address. A tuple including the UE ID, the public IP address, and the private IP address is generated at the NEF.

Abstract: Various approaches for Multi-Access Edge Computing (MEC) and Operator Platform (OP) systems, and management of applications and services in such systems, are discussed herein. An example system is configured to coordinate operations of a MEC system and an EDGEAPP system. The system performs lifecycle management (LCM) operations of MEC and EDGEAPP applications in an Operator Platform instance in an Operator Platform domain, enabling coordination of the MEC and EDGEAPP applications in their respective systems. The system receives application data from an application client of a user equipment (UE) associated with either the MEC system or the EDGEAPP system and transmits the application data to an application host associated with (e.g., executed on) the other system. The system thus enables LCM of respective apps and communications among MEC and EDGEAPP systems, enhancing the overall performance of an Operator Platform.

Abstract: Systems and methods for a secure application computing environment in a federated Edge Cloud are disclosed herein. Application information corresponding to an application from an application provider may be received in a secure environment of a device such as an edge computing node. A trust level for execution of the application may be associated based at least in part on the application information, and based on the associated trust level, a trusted platform may be selected to deploy or launch the application.

Abstract: A central trajectory controller including a cell interface configured to establish signaling connections with one or more backhaul moving cells and to establish signaling connections with one or more outer moving cells, an input data repository configured to obtain input data related to a radio environment of the one or more outer moving cells and the one or more backhaul moving cells, and a trajectory processor configured to determine, based on the input data, first coarse trajectories for the one or more backhaul moving cells and second coarse trajectories for the one or more outer moving cells, the cell interface further configured to send the first coarse trajectories to the one or more backhaul moving cells and to send the second coarse trajectories to the one or more outer moving cells.