IP Library › Granted Patent US 12,393,436
Granted Patent B2
US 12,393,436 · App. 17/481,549 · Granted Aug 19, 2025

Method for deploying virtual machine and container, and related apparatus

Inventor: Xueliang Chen (Shenzhen, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
G06F9/45533G06F8/60H04W4/50
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,393,436
App. No.
17/481,549
Granted
Aug 19, 2025
Kind
B2
Abstract

Embodiments of this application disclose a method for deploying a virtual machine (VM) and a container to implement both container deployment and VM deployment in a multi-access edge computing (MEC) system. In the method, a unified orchestration function entity receives a deployment request, and determines that a deployment manner of an application is the container deployment or the VM deployment If the deployment manner of the application is the container deployment, a first resource allocation request is sent to an architecture manager, to request the architecture manager to deploy a container that can run an instance of the application. If the deployment manner of the application is the VM deployment, a resource allocation request is sent to a VIM, to request the VIM to deploy a VM that can run the instance of the application.

Claims (37)

1. A method for deploying an application, wherein the method comprises:

receiving a deployment request, wherein the deployment request is used to request to deploy an instance of an application, the deployment request comprises an identifier (ID) and orchestration information of the application, and the orchestration information is used to indicate resources required for running the instance of the application;

determining a deployment manner of the application based on the deployment request, wherein the deployment manner of the application comprises container deployment or virtual machine (VM) deployment;

sending a first resource allocation request to a container infrastructure manager (CIM) when the deployment manner of the application is the container deployment, wherein the first resource allocation request is used to request resources required for deploying a container capable of running the instance of the application; and

sending a second resource allocation request to a virtualized infrastructure manager (VIM) when the deployment manner of the application is the VM deployment, wherein the second resource allocation request is used to request resources required for deploying a VM capable of running the instance of the application.

2. The method according to claim 1 , wherein a correspondence exists between the ID of the application and the deployment manner of the application, and the determining a deployment manner of the application based on the deployment request comprises:

determining the deployment manner of the application based on the ID of the application and the correspondence.

3. The method according to claim 1 , wherein the deployment request further comprises a deployment type identifier, the deployment type identifier is used to identify the deployment manner of the application, and the determining a deployment manner of the application based on the deployment request comprises:

determining the deployment manner of the application based on the deployment type identifier.

4. The method according to claim 1 , wherein the method further comprises:

sending a configuration request to a mobile edge platform (MEP), wherein the configuration request is used to request the MEP to configure a traffic rule and a domain name system (DNS) rule for running the instance of the application.

5. The method according to claim 1 , wherein the method further comprises:

receiving a termination request, wherein the termination request comprises the ID of the application, and the termination request is used to terminate the instance of the application; and

sending a first resource deletion request to the architecture manager when the deployment manner of the application is the container deployment, wherein the first resource deletion request is used to request the architecture manager to delete resources occupied by the instance of the application; or

sending a second resource deletion request to the VIM when the deployment manner of the application is the VM deployment, wherein the second resource deletion request is used to request the VIM to delete resources occupied by the instance of the application.

6. The method according to claim 1 , wherein the method is performed by a unified orchestration function entity and the unified orchestration function entity is a mobile edge platform manager (MEPM) or a mobile edge orchestrator (MEO).

7. A unified orchestration function entity, wherein the unified orchestration function entity comprises a transceiver, a memory, and a processor, wherein

the transceiver is configured to perform communication;

the memory is configured to store a computer program; and

the processor is configured to invoke the computer program from the memory and run the computer program to:

receive a deployment request, and determine a deployment manner of an application based on the deployment request, wherein the deployment request is used to request to deploy an instance of the application, the deployment request comprises an identifier (ID) and orchestration information of the application, the orchestration information is used to indicate resources required for deploying the instance of the application, and the deployment manner of the application comprises container deployment or virtual machine (VM) deployment;

send a first resource allocation request to a container infrastructure manager (CIM) when the deployment manner of the application is the container deployment, wherein the first resource allocation request is used to request resources required for a container capable of running the instance of the application; and

send a second resource allocation request to a virtualized infrastructure manager (VIM) when the unified orchestration and scheduling management module determines that the deployment manner of the application is the VM deployment, wherein the second resource allocation request is used to request resources required for deploying a VM capable of running the instance of the application.

8. The unified orchestration function entity according to claim 7 , wherein a correspondence exists between the ID of the application and the deployment manner of the application, and the processor is further configured to invoke the computer program from the memory and run the computer program to:

determine the deployment manner of the application based on the ID of the application and the correspondence.

9. The unified orchestration function entity according to claim 7 , wherein the deployment request further comprises a deployment type identifier, the deployment type identifier is used to identify the deployment manner of the application, and the processor is further configured to invoke the computer program from the memory and run the computer program to determine the deployment manner of the application based on the deployment type identifier.

10. The unified orchestration function entity according to claim 7 , wherein the processor is further configured to invoke the computer program from the memory and run the computer program to send a configuration request to a mobile edge platform (MEP), wherein the configuration request is used to request the MEP to configure a traffic rule and a domain name system (DNS) rule that are followed for running the instance of the application.

11. The unified orchestration function entity according to claim 7 , wherein the processor is further configured to invoke the computer program from the memory and run the computer program to:

receive a termination request, wherein the termination request comprises the ID of the application, and the termination request is used to terminate the instance of the application;

send a first resource deletion request to the architecture manager when the deployment manner of the application is the container deployment, wherein the first resource deletion request is used to request the architecture manager to delete resources occupied by the instance of the application; and

send a second resource deletion request to the VIM when the deployment manner of the application is the VM deployment, wherein the second resource deletion request is used to request the VIM to delete the resources occupied by the instance of the application.

12. The unified orchestration function entity according to claim 7 , wherein the unified orchestration function entity is a mobile edge platform manager (MEPM) or a mobile edge orchestrator (MEO).

13. A multi-access edge computing (MEC) system, wherein the MEC system comprises a unified orchestration function entity and a container infrastructure manager (CIM);

the unified orchestration function entity comprises a transceiver, a memory, and a processor, wherein the transceiver is configured to perform communication; the memory is configured to store a computer program; and the processor is configured to invoke the computer program from the memory and run the computer program to: receive a deployment request, and determine a deployment manner of an application based on the deployment request, wherein the deployment request is used to request to deploy an instance of the application, the deployment request comprises an identifier (ID) and orchestration information of the application, the orchestration information indicates resources required for deploying the instance of the application, and the deployment manner of the application comprises a container deployment or a virtual machine (VM) deployment;

when the deployment manner of the application is the container deployment, the processor of the unified orchestration function entity is further configured to invoke the computer program from the memory and run the computer program to send a first resource allocation request to the CIM when the deployment manner of the application is the container deployment, wherein the first resource allocation request is used to request resources required for deploying a container capable of running the instance of the application, and to send a second resource allocation request to a virtualized infrastructure manager (VIM) if the deployment manner of the application is the VM deployment, wherein the second resource allocation request is used to request resources required for deploying a VM capable of running the instance of the application; and

the CIM comprises a transceiver, a memory, and a processor, wherein the transceiver is configured to perform communication; the memory is configured to store a computer program; and the processor is configured to invoke the computer program from the memory and run the computer program to: receive the first resource allocation request, and deploy, based on the first resource allocation request, the container capable of running the instance of the application.

14. The MEC system according to claim 13 , wherein the unified orchestration function entity is a mobile edge platform manager (MEPM) or a mobile edge orchestrator (MEO).

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 22, 2021
From: CHEN, XUELIANG
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 058463/0307 →
Priority Claims (1)
CN 201910224223.9 · Mar 22, 2019 · national
Continuity (2)
Continuation PCTCN2020080505 · Mar 20, 2020
Related Publication 20220004410A1 · Jan 6, 2022
References Cited (20)
US 20180025160A1 · Hwang et al. · 2018 [cited by applicant]
US 20180131557A1 · Chou · 2018 [cited by examiner]
US 20180365076A1 · Liu · 2018 [cited by examiner]
US 20190034244A1 · Yang · 2019 [cited by examiner]
US 20190042319A1 · Sood et al. · 2019 [cited by applicant]
US 20190138934A1 · Prakash · 2019 [cited by examiner]
US 20210117241A1 · Xia · 2021 [cited by examiner]
US 20220075666A1 · Xia · 2022 [cited by examiner]
CN 105975330A · 2016 [cited by applicant]
CN 107766050A · 2018 [cited by applicant]
CN 108205461A · 2018 [cited by applicant]
CN 108399094A · 2018 [cited by applicant]
CN 108418705A · 2018 [cited by applicant]
CN 109358967A · 2019 [cited by applicant]
CN 110569101 · 2019 [cited by examiner]
CN 107431696B · 2020 [cited by applicant]
WO 2018224243A1 · 2018 [cited by applicant]
ETSI GS MEC 003 V1.1.1 (Mar. 2016), Mobile Edge Computing (MEC); Framework and Reference Architecture, Total 18 Pages. [cited by applicant]
Huazhang Lv et al., “Deployment of Edge-Computing in 5G NFV Environment and Future Service-Based Architecture,” 2018 IEEE 4th International Conference on Computer and Communications (ICCC), Dec. 10, 2018; 6 total pages. [cited by applicant]
Giuseppe A. Carella et al., “Prototyping NFV-based Multi-access Edge Computing in 5G ready Networks with Open Baton,” 2017 IEEE Conference on Network Softwarization (NetSoft), Jul. 7, 2017; 4 total pages. [cited by applicant]