On-Demand API Provider Instantiation for MEC Resource Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile edge computing (MEC) systems waste resources of application programming interface (API) provider entities due to inefficient utilization, leading to suboptimal use of computing resources.

Innovation Solution

A communication method and apparatus that instantiates API provider entities on demand based on requirements, utilizing a common application programming interface framework core function (CCF) to query availability and request instantiation from a network management system, ensuring efficient resource allocation and utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If API provider entities are deployed as virtual server instances in MEC systems, then service capability and adaptability are improved, but resource waste occurs when entities are instantiated without demand

Engineering Contradiction:
Improveservice capabilityVSAvoidresource waste
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent implements dynamic instantiation of API provider entities based on real-time service requests. The network management system receives instantiation requests from CCF entities, queries availability of required APIs, and dynamically creates or activates API provider entities only when needed. This dynamic approach allows the system to adapt service capability to actual demand, avoiding static resource allocation that causes waste while maintaining the ability to provide diverse services when required.

Inventive Principle:
Principle #15Dynamics

2Reliability

If multiple API provider entities are pre-deployed to ensure service availability, then reliability is improved, but device complexity and resource consumption increase

Engineering Contradiction:
Improveservice availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a self-service mechanism where the network management system automatically manages the lifecycle of API provider entities. When the CCF entity requests an API, the network management system autonomously determines whether to instantiate a new API provider entity or activate an existing one, manages the instantiation process, and handles resource allocation. This self-service approach ensures service availability through automated response to requests while reducing system complexity by eliminating manual configuration and management overhead.

Inventive Principle:
Principle #25Self-service

3Productivity

If API provider entities are instantiated on-demand based on service requests, then resource utilization is improved, but response time may increase due to instantiation process

Engineering Contradiction:
Improveresource utilizationVSAvoidresponse time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-configuring API provider entity templates and metadata in the network management system. Before actual instantiation is needed, the system maintains readiness information including available APIs, entity templates, and deployment configurations. When a service request arrives, the system can rapidly instantiate entities using pre-prepared configurations rather than creating everything from scratch, thus improving resource utilization through on-demand instantiation while minimizing the time penalty of the instantiation process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250227442A1Communication method and apparatus
Publication Date: 2025.07.10 HUAWEI TECH CO LTD
  • US20250227442A1 patent drawing
  • US20250227442A1 patent drawing
  • US20250227442A1 patent drawing

AI summary

This application provides example communication methods and apparatuses. One example method includes receiving, by a first entity, a first request sent by a second entity, where the first request includes a first application programming interface (API) requested by the second entity. It is determined, from pre-stored first API information, that the first API is unavailable, where the first API information includes availability of multiple APIs, and the multiple APIs include the first API. A second request is sent to a network management system to request to instantiate an API provider entity corresponding to the first API. A first response is received from the network management system, where the first response comprises interface information of the first API.