Edge Cloud Resource Allocation Platform for Mobile Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile network edge computing systems face challenges with high latency and resource inefficiency due to the need for multiple cloud deployments as user equipment (UE) moves across different coverage areas, consuming significant processing and memory resources.
Innovation Solution
An allocation platform that enables low-latency allocation of cloud computing resources to UE by receiving requests for computing resources and executing remote execution file packages, allowing applications to access cloud resources without prior deployment, thereby conserving resources and reducing latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If cloud deployment is performed at each MEC system as UE moves across coverage areas, then application accessibility is improved, but processing resources and memory resources are consumed significantly
Solution Approach 1:
The patent merges multiple cloud deployment instances into a single shared deployment that can be accessed by multiple MEC systems. Instead of deploying the application separately at each MEC system, a unified deployment architecture is implemented where the application is deployed once and made accessible across different coverage areas through the shared deployment, reducing redundant resource consumption while maintaining application accessibility.
Solution Approach 2:
The patent implements a universal cloud deployment that serves multiple MEC systems simultaneously. The deployment architecture is designed to be multi-functional, allowing a single deployment to support applications across different coverage areas and MEC systems, thereby eliminating the need for separate deployments at each location and reducing overall processing resource requirements.
2Adaptability or versatility
If cloud deployment is performed at each MEC system as UE moves across coverage areas, then application accessibility is improved, but memory resources are consumed significantly
Solution Approach 1:
The patent merges multiple cloud deployment instances into a single shared deployment that can be accessed by multiple MEC systems. Instead of deploying the application separately at each MEC system, a unified deployment architecture is implemented where the application is deployed once and made accessible across different coverage areas through the shared deployment, reducing redundant resource consumption while maintaining application accessibility.
Solution Approach 2:
The patent uses copying mechanisms to allow multiple MEC systems to access the same deployment without requiring full copies at each location. The deployment information and executable code are replicated or referenced across systems, enabling universal access while consuming minimal memory resources at each MEC system compared to storing complete deployment copies.
3Reliability
If orchestration tasks are performed to configure cloud computing resources, then application functionality is improved, but time is consumed significantly
Solution Approach 1:
The patent implements preliminary configuration of cloud computing resources through template-based deployment architectures. Common orchestration tasks and configuration parameters are pre-configured in deployment templates, allowing rapid instantiation of applications without performing time-consuming orchestration tasks from scratch. This preliminary action maintains application functionality while significantly reducing deployment time.
Solution Approach 2:
The patent uses parameter-based configuration where deployment templates contain configurable parameters that can be adjusted to meet specific application requirements. Instead of performing comprehensive orchestration tasks for each deployment, the system changes key parameters in pre-configured templates to adapt to different applications, maintaining functionality while reducing configuration time.
Data Source
AI summary
A device may receive, from a user equipment (UE), a request to allocate one or more computing resources for an application executing on the UE. The device may be associated with an edge node of a mobile network and the UE may be within a coverage area associated with the edge node. The device may receive a remote execution file package that is associated with code to be executed using the one or more computing resources. The device may assign the one or more computing resources for the application. The device may cause at least one of installation of the code for execution by the one or more computing resources, or execution of the code using the one or more computing resources. The device may transmit a response that provides an indication that the one or more computing resources have been allocated for the application.