Edge Cloud Broker Resource Allocation for 5G Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud brokering solutions are inadequate for Edge Computing (EC) networks as they focus on centralized data centers and do not account for the distributed infrastructure of Edge Cloud, failing to efficiently manage and provide cloud services in 5G networks.

Innovation Solution

An Edge Cloud Broker (ECB) is introduced to select and manage edge cloud resources by obtaining UE location, requested application identifiers, and available resource locations, enabling the selection and deployment of edge cloud resources based on location and application requirements, and managing lifecycle operations such as deployment, scaling, and charging.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional centralized cloud brokering solutions are used, then cloud service management is simplified, but the distributed nature of Edge Computing infrastructure cannot be effectively managed

Engineering Contradiction:
Improvecloud service managementVSAvoidEdge Computing infrastructure management
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the centralized cloud broker functionality into distributed edge cloud brokers deployed at multiple edge locations. Each edge cloud broker independently manages local edge cloud resources, enabling the system to handle the distributed nature of Edge Computing infrastructure while maintaining simplified service management through standardized broker interfaces.

Inventive Principle:
Principle #1Segmentation

2Speed

If edge cloud resources are distributed across multiple locations, then service delivery efficiency is improved through reduced latency, but resource allocation complexity increases

Engineering Contradiction:
Improveservice delivery speedVSAvoidresource allocation complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent introduces edge cloud brokers as intermediary entities between users and distributed edge cloud resources. These brokers abstract the complexity of resource allocation across multiple locations by providing unified resource management interfaces, thereby maintaining fast service delivery through local resource placement while simplifying the complexity of distributed resource allocation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of time

If cloud services are brought closer to users at the network edge, then end-to-end latency is reduced, but the complexity of managing virtualized resources increases

Engineering Contradiction:
Improveend-to-end latencyVSAvoidvirtualized resource management
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent designs edge cloud brokers with multi-functional capabilities to handle various virtualized resource management tasks including deployment, scaling, monitoring, and allocation. This universal broker architecture reduces the complexity of managing diverse virtualized resources at the edge by consolidating multiple management functions into a single standardized interface and process framework.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP3632083B1Edge cloud broker and method therein for allocating edge cloud resources
Publication Date: 2024.05.15 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3632083B1 patent drawingFigure 1
  • EP3632083B1 patent drawingFigure 2
  • EP3632083B1 patent drawingFigure 3

AI summary

The present invention faces the issue of supporting edge cloud in an NG network. There is thus provided an edge cloud broker (ECB) and a method carried out by the ECB for selecting edge cloud resources of a mobile edge computing (MEC) network, the edge cloud resources usable by a UE accessing the NG network. This method comprises: obtaining, from a first network node of the NG network, a UE's location; obtaining, from a second network node of the NG network, an identifier of an edge cloud application that the UE requests; obtaining, from a third network node of the MEC network, a location of each one or more edge cloud resources available to execute the edge cloud application; and selecting, based on at least the UE's location and the location of each one or more edge cloud resources, an applicable edge cloud resource to execute the edge cloud application for the UE.