Lightweight edge distributed MEC device
By using the micro-container management, container management, and virtualization application management modules of lightweight edge distributed MEC devices, the problems of high deployment difficulty and high cost of existing MEC devices are solved, enabling flexible configuration of production needs and low-cost shop floor deployment.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA UNITED NETWORK COMM GRP CO LTD
- Filing Date
- 2023-06-30
- Publication Date
- 2026-06-09
Smart Images
Figure CN116846895B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of Internet technology, and in particular to a lightweight edge-distributed MEC device. Background Technology
[0002] 5G fully connected factories represent a significant direction for 5G applications. Unlike the standardized hardware architecture of 5G, 5G fully connected factories exhibit substantial differences in communication and digital signal processing. 5G Mobile Edge Computing (MEC), built upon 5G network capabilities and edge computing capabilities, is an edge cloud platform constructed on top of mobile network edge infrastructure and is a crucial unit in 5G fully connected factories. MEC devices are applied in scenarios such as industry, industrial parks, transportation, ports, healthcare, and new media, providing integrated ICT converged services and enabling user services to be deployed to the operator's edge or user side, effectively reducing computing latency and costs.
[0003] The MEC in the existing 5G standard is built on virtualization technology and contains complex hardware and control software. It is a powerful but costly and closed "heavy" network unit.
[0004] Existing MECs are suitable for deployment in operator equipment nodes such as aggregation nodes and base stations in 5G networks. However, fully connected 5G factories require the deployment of a large number of simple, low-cost, and lightweight MECs in specific indoor or outdoor areas of the production workshop. This allows enterprises to flexibly customize workshop-level edge distributed MEC devices to meet various latency, application deployment methods, and computing capabilities according to production needs. Therefore, existing MEC devices present technical challenges due to their high deployment difficulty and cost. Summary of the Invention
[0005] This application provides a lightweight edge-distributed MEC device to solve the technical problems of high deployment difficulty and high cost.
[0006] This application provides a lightweight edge-distributed MEC device, comprising:
[0007] The microcontainer management module is used to receive microcontainer orchestration instructions and generate microcontainer nodes based on the microcontainer orchestration instructions to manage the microcontainer applications corresponding to edge distributed MEC devices.
[0008] The container management module is used to generate container orchestration instructions and manage container applications corresponding to edge distributed MEC devices based on these instructions.
[0009] The virtualization application management module is used to offload the virtualization tasks of the edge distributed MEC device to the virtual machine corresponding to the upper-level MEC device of the edge distributed MEC device for execution, so as to realize the virtualization application corresponding to the virtualization task;
[0010] The computing resource management module is used to allocate computing resources to the micro-container management module, container management module, and virtualization application management module.
[0011] Optionally, the microcontainer management module includes:
[0012] The microcontainer orchestration agent unit is used to receive microcontainer orchestration instructions and generate orchestration instructions for creation, node management and node services based on the microcontainer orchestration instructions;
[0013] Microcontainer node units are used to generate, run, shut down, and delete microcontainer nodes based on orchestration instructions;
[0014] The micro-container node management unit is used to configure the environment of micro-container nodes based on the computing resource management module, and to maintain and manage the cluster corresponding to multiple micro-container nodes.
[0015] Optionally, the microcontainer orchestration agent unit includes:
[0016] The rules subunit is used to determine the orchestration method corresponding to the microcontainer node based on the operating system and implementation method of the microcontainer node, and to generate deployment rules for the microcontainer node based on the orchestration method.
[0017] Optionally, the microcontainer orchestration agent unit includes:
[0018] The indicator maintenance subunit is used to determine the microcontainer deployment scheme based on the application scenarios and deployment rules of the microcontainer nodes. The microcontainer deployment scheme includes the input, modification and maintenance operations of the number of microcontainer nodes, resource allocation and collaboration methods.
[0019] Optionally, the microcontainer orchestration agent unit includes:
[0020] The operation and maintenance subunit is used to monitor and report the operation and real-time status of microcontainer nodes.
[0021] Optionally, the microcontainer node management unit includes:
[0022] The environment management subunit is used to receive environment configuration instructions from the computing resource management module and manage the hardware environment of the micro-container node based on the environment configuration instructions; wherein, the hardware environment includes the deployment rules and deployment schemes corresponding to the micro-container node;
[0023] The computing power management subunit is used to receive computing power scheduling instructions from the computing power resource management module, and manage the computing power resources corresponding to the micro-container nodes based on the computing power scheduling instructions to meet the deployment plan.
[0024] Optionally, the container management module includes:
[0025] The container management unit is used to receive container orchestration instructions, determine container deployment scripts based on the container orchestration instructions, build and run container applications based on the container deployment scripts, and manage container applications.
[0026] Optionally, the computing resource management module includes:
[0027] The environment configuration management unit is used to generate environment configuration instructions for the hardware environment corresponding to the micro-container management module, container management module, and virtualization application management module.
[0028] The computing resource scheduling unit is used to generate computing resource scheduling instructions for the micro-container management module, container management module, and virtualization application management module.
[0029] Optionally, the computing resources include at least one of the following:
[0030] Local computing resources deployed in edge distributed MEC devices;
[0031] The computing power resources of the computing power pool are deployed in the first computing power expansion device connected to the edge distributed MEC device via a high-speed bus.
[0032] Enterprise computing resources deployed in a second computing power extension device connected to edge distributed MEC devices via a computing power resource interface.
[0033] Optionally, the deployment modes of the edge distributed MEC devices provided in this application include:
[0034] Distributed Unit (DU) Deployment Mode; In this mode, the edge distributed MEC device and the distributed unit (DU) are deployed in the same location. The edge distributed MEC device is connected to the centralized unit (CU) via a link, and the edge distributed MEC device communicates through the F1 interface of the 5G wireless network.
[0035] Base station deployment mode; where the base station deployment mode is a deployment mode in which the edge distributed MEC device and the base station are deployed in the same location.
[0036] The lightweight edge distributed MEC device provided in this application includes: a micro-container management module for receiving micro-container orchestration instructions and generating micro-container nodes for managing micro-container applications corresponding to the edge distributed MEC device based on the micro-container orchestration instructions; a container management module for generating container orchestration instructions and managing container applications corresponding to the edge distributed MEC device based on the container orchestration instructions; a virtualization application management module for offloading virtualization tasks of the edge distributed MEC device to the virtual machine corresponding to the parent MEC device of the edge distributed MEC device for execution; and a computing resource management module for allocating computing resources to the micro-container management module, the container management module, and the virtualization application management module. The lightweight edge distributed MEC device provided in this application can be flexibly configured and deployed to meet various workshop-level edge distributed MEC devices with different latency, application deployment methods, and computing capabilities according to enterprise production needs. It has a simple structure and function, low deployment difficulty, and low cost, thus achieving the technical effect of reducing the deployment difficulty and cost of MEC devices. Attached Figure Description
[0037] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0038] Figure 1 A schematic diagram of the structure of the lightweight edge-distributed MEC device provided in the embodiments of this application. Figure 1 ;
[0039] Figure 2 A schematic diagram of the structure of the lightweight edge-distributed MEC device provided in the embodiments of this application. Figure 2 ;
[0040] Figure 3 A schematic diagram of the structure of the lightweight edge-distributed MEC device provided in the embodiments of this application. Figure 3 ;
[0041] Figure 4 A schematic diagram of the structure of the lightweight edge-distributed MEC device provided in the embodiments of this application. Figure 4 .
[0042] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0043] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of devices consistent with some aspects of this application as detailed in the appended claims.
[0044] In existing technologies, 5G fully connected factories differ from the standardized hardware structure of 5G, exhibiting significant differences in communication and digital signal processing. 5G Mobile Edge Computing (MEC), built upon 5G network capabilities and edge computing capabilities, is an edge cloud platform constructed on top of mobile network edge infrastructure and is a crucial unit of 5G fully connected factories. MEC devices are applied in scenarios such as industry, parks, transportation, ports, healthcare, and new media, providing integrated ICT converged services and enabling user services to be deployed to the operator's edge or user side, effectively reducing computing latency and costs.
[0045] The MEC in the existing 5G standard is built on virtualization technology and contains complex hardware and control software. It is a powerful but costly and closed "heavy" network unit.
[0046] Existing MECs are suitable for deployment in operator equipment nodes such as aggregation nodes and base stations in 5G networks. However, fully connected 5G factories require the deployment of a large number of simple, low-cost, and lightweight MECs in specific indoor or outdoor areas of the production workshop. This allows enterprises to flexibly customize workshop-level edge distributed MEC devices to meet various latency, application deployment methods, and computing capabilities according to production needs. Therefore, existing MEC devices present technical challenges due to their high deployment difficulty and cost.
[0047] The lightweight edge distributed MEC device provided in this application includes: a micro-container management module for receiving micro-container orchestration instructions and generating micro-container nodes for managing micro-container applications corresponding to the edge distributed MEC device based on the micro-container orchestration instructions; a container management module for generating container orchestration instructions and managing container applications corresponding to the edge distributed MEC device based on the container orchestration instructions; a virtualization application management module for offloading virtualization tasks of the edge distributed MEC device to the virtual machine corresponding to the parent MEC device of the edge distributed MEC device for execution; and a computing resource management module for allocating computing resources to the micro-container management module, the container management module, and the virtualization application management module. The lightweight edge distributed MEC device provided in this application can be flexibly configured and deployed to meet various workshop-level edge distributed MEC devices with different latency, application deployment methods, and computing capabilities according to enterprise production needs. It has a simple structure and function, low deployment difficulty, and low cost, thus achieving the technical effect of reducing the deployment difficulty and cost of MEC devices.
[0048] The technical solution of this application and how it solves the above-mentioned technical problems will be described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.
[0049] Figure 1 A schematic diagram of the structure of the lightweight edge-distributed MEC device provided in the embodiments of this application. Figure 1 .like Figure 1 As shown, this application provides a lightweight edge-distributed MEC device 100, comprising:
[0050] The microcontainer management module 101 is used to receive microcontainer orchestration instructions and generate microcontainer nodes for managing microcontainer applications corresponding to edge distributed MEC devices based on the microcontainer orchestration instructions.
[0051] The container management module 102 is used to generate container orchestration instructions and manage container applications corresponding to edge distributed MEC devices based on the container orchestration instructions.
[0052] The virtualization application management module 103 is used to offload the virtualization tasks of the edge distributed MEC device to the virtual machine corresponding to the upper-level MEC device of the edge distributed MEC device for execution, so as to realize the virtualization application corresponding to the virtualization task.
[0053] In this embodiment, for virtualized applications that cannot be deployed using containers or require an independent operating system environment, a virtual environment offloading method is adopted. The virtual environment offloading corresponding to the upper-level MEC of the edge distributed MEC device is deployed in the edge distributed MEC device. The tasks in the virtualization unit of the edge distributed MEC device are offloaded to the virtual machine in the upper-level MEC for execution, thereby realizing the virtualized application in the edge distributed MEC device.
[0054] The computing resource management module 104 is used to allocate computing resources to the micro-container management module, the container management module, and the virtualization application management module.
[0055] In this embodiment, the deployment methods of edge distributed MEC devices include distributed unit (DU) deployment mode and base station deployment mode. In the distributed unit (DU) deployment mode, the edge distributed MEC devices and distributed unit (DU) are deployed in the same location. The edge distributed MEC devices are connected to the centralized unit (CU) via links, and the edge distributed MEC devices communicate through the F1 interface of the 5G wireless network. In the base station deployment mode, the edge distributed MEC devices and base stations are deployed in the same location. The base station achieves software and hardware integration of multiple edge distributed MEC devices through a unified interface by decoupling software and hardware and white-boxing hardware.
[0056] In this embodiment, the edge distributed MEC device separates application and computing power, providing a lightweight deployment environment that integrates micro-containers, containers, and virtualization. Lightweight orchestration is achieved by proxying upper-level MEC orchestration instructions. The edge distributed MEC device offers a wide range of application and computing power variations, providing high flexibility and meeting the requirements of diverse production sites for deploying and operating complex application types within the edge cloud environment.
[0057] The lightweight edge distributed MEC device provided in this application includes: a micro-container management module for receiving micro-container orchestration instructions and generating micro-container nodes for managing micro-container applications corresponding to the edge distributed MEC device based on the micro-container orchestration instructions; a container management module for generating container orchestration instructions and managing container applications corresponding to the edge distributed MEC device based on the container orchestration instructions; a virtualization application management module for offloading virtualization tasks of the edge distributed MEC device to the virtual machine corresponding to the parent MEC device of the edge distributed MEC device for execution; and a computing resource management module for allocating computing resources to the micro-container management module, the container management module, and the virtualization application management module. The lightweight edge distributed MEC device provided in this application can be flexibly configured and deployed to meet various workshop-level edge distributed MEC devices with different latency, application deployment methods, and computing capabilities according to enterprise production needs. It has a simple structure and function, low deployment difficulty, and low cost, thus achieving the technical effect of reducing the deployment difficulty and cost of MEC devices.
[0058] Figure 2 A schematic diagram of the structure of the lightweight edge-distributed MEC device provided in the embodiments of this application. Figure 2 .like Figure 2 As shown, in one possible implementation, the microcontainer management module 101 includes:
[0059] The microcontainer orchestration agent unit 201 is used to receive microcontainer orchestration instructions and generate orchestration instructions for creation, node management and node services based on the microcontainer orchestration instructions;
[0060] In this embodiment, the microcontainer orchestration agent unit is orchestrated uniformly by the global management center (MEC applicationorchestrator, MEAO) and the mobile edge platform manager (MEPM) in the MEC. After the orchestration instructions are issued to the MEC, the microcontainer orchestration agent unit translates and implements the received orchestration scheme into microcontainer orchestration, converting the MEPM orchestration instructions into orchestration instructions for microcontainer node establishment, node management, and node services. In addition, the microcontainer orchestration agent unit also has management functions such as authentication, access control, and metering.
[0061] Microcontainer node unit 202 is used to generate, run, shut down, and delete microcontainer nodes based on orchestration instructions;
[0062] In this embodiment, the microcontainer node unit implements full lifecycle management of microcontainer node generation, operation, shutdown and deletion based on orchestration instructions; after the orchestration instructions are translated by the microcontainer orchestration agent unit, images and container node maintenance are generated, and the download, storage and scheduling of images of the corresponding deployment entities of microcontainers are completed, as well as the creation, operation, stopping and deletion operations of microcontainer nodes are completed.
[0063] The micro-container node management unit 203 is used to configure the environment of micro-container nodes based on the computing resource management module, and to maintain and manage the cluster corresponding to multiple micro-container nodes.
[0064] In this embodiment, the micro-container node management unit includes an environment management subunit and a computing power management subunit. The environment management subunit receives environment configuration instructions from the computing power resource management module and manages the hardware environment of the micro-container node based on the environment configuration instructions. The hardware environment includes the deployment rules and deployment schemes corresponding to the micro-container node. The computing power management subunit receives computing power scheduling instructions from the computing power resource management module and manages the computing power resources corresponding to the micro-container node based on the computing power scheduling instructions to meet the deployment scheme.
[0065] In one possible implementation, the micro-container orchestration agent unit 201 includes:
[0066] The rules subunit is used to determine the orchestration method corresponding to the microcontainer node based on the operating system and implementation method of the microcontainer node, and to generate deployment rules for the microcontainer node based on the orchestration method.
[0067] In this embodiment, the rule subunit is used to maintain rules that meet the deployment requirements of different types of microservices. Since microcontainers have multiple basic operating systems (OS) and implementation methods, and each OS and implementation method has a different orchestration method, the orchestration method of each microcontainer is mapped to a rule. By adding and modifying the rules, the needs of actual applications in lightweight MEC for different microcontainers can be met.
[0068] In one possible implementation, the micro-container orchestration agent unit 201 includes:
[0069] The indicator maintenance subunit is used to determine the microcontainer deployment scheme based on the application scenarios and deployment rules of the microcontainer nodes. The microcontainer deployment scheme includes the input, modification and maintenance operations of the number of microcontainer nodes, resource allocation and collaboration methods.
[0070] In this embodiment, the indicator maintenance subunit has different requirements for latency, processing capacity, and reliability in different production application scenarios. The corresponding indicators are required to have a significant impact on the number of micro-container nodes, resource allocation, and collaboration methods. Based on the indicators and in accordance with the rules base specifications, the micro-container orchestration agent unit generates different microservice entity schemes.
[0071] In one possible implementation, the micro-container orchestration agent unit 201 includes:
[0072] The operation and maintenance subunit is used to monitor and report the operation and real-time status of microcontainer nodes.
[0073] Figure 3 A schematic diagram of the structure of the lightweight edge-distributed MEC device provided in the embodiments of this application. Figure 3 .like Figure 3 As shown, in one possible implementation, the micro-container node management unit 203 includes:
[0074] The environment management subunit 301 is used to receive environment configuration instructions from the computing resource management module and manage the hardware environment of the micro-container node based on the environment configuration instructions; wherein, the hardware environment includes the deployment rules and deployment schemes corresponding to the micro-container node;
[0075] In this embodiment, the environment management subunit completes the configuration and scheduling of the lowest-level hardware infrastructure of the micro-container and provides the hardware environment required by various micro-containers, such as memory and network capabilities. The environment management subunit creates the micro-container hardware environment using rules and indicators, and forms a fixed configuration strategy for repeated infrastructure creation. The configuration strategy includes configuration parameters and configuration data. The configuration parameters are fixed general parameters for configuring the environment and are used to configure a standard basic hardware environment. The configuration data are specific configuration parameters required by different indicators and are used to configure the standard basic hardware into a basic hardware environment that meets the indicator requirements.
[0076] The computing power management subunit 302 is used to receive computing power scheduling instructions from the computing power resource management module, and manage the computing power resources corresponding to the micro-container nodes based on the computing power scheduling instructions to meet the deployment plan.
[0077] In one possible implementation, the container management module 102 includes:
[0078] The container management unit is used to receive container orchestration instructions, determine container deployment scripts based on the container orchestration instructions, build and run container applications based on the container deployment scripts, and manage container applications.
[0079] In this embodiment, Docker is a widely used container engine, and the Kubernetes (k8s) tool can orchestrate and manage Docker containers. For example, the k8s orchestration function can build application services with a large number of containers, schedule across clusters, expand containers, continuously manage containers, and manage their health status.
[0080] In this embodiment, the Kubernetes-based Docker orchestration system is heavyweight and not suitable for deployment on lightweight edge distributed MEC devices. Therefore, it is deployed in the upper-level MEC of the lightweight edge distributed MEC device. The lightweight edge distributed MEC device uses a container orchestration agent to translate the orchestration scheme into a local lightweight container deployment script. The container is built and run through the execution of the local script. For example, the Kubernetes orchestration scheme is translated into a specific Docker-compose build script, and Docker image download, container building and running are completed through tools such as Compose.
[0081] In this embodiment, the container management unit is used to implement unified management and scheduling of containers distributed across different hardware nodes, including the scheduling and allocation of computing resources for distributed containers, load balancing, and management of container sets; for example, the smallest scheduling unit of Kubernetes, Pod, contains one or more related containers.
[0082] In this embodiment, the container management unit provides unified management of the underlying operating system, including installation, configuration, security management, component installation, updates and upgrades, and reset, providing a secure and reliable underlying operating system for containers.
[0083] Figure 4 A schematic diagram of the structure of the lightweight edge-distributed MEC device provided in the embodiments of this application. Figure 4 .like Figure 4 As shown, in one possible implementation, the computing resource management module 104 includes:
[0084] The environment configuration management unit 401 is used to generate environment configuration instructions for the hardware environment corresponding to the micro-container management module, container management module and virtualization application management module.
[0085] The computing resource scheduling unit 402 is used to generate computing resource scheduling instructions for the micro-container management module, container management module and virtualization application management module.
[0086] In this embodiment, the computing resource scheduling unit dynamically integrates multiple processors using a shared memory processor (SMP) approach, enabling the combination of different processors (such as CPU and GPU). The computing resource scheduling unit schedules multiple processors by sharing a physical address space, equipping each processor with a dedicated memory to form a processing unit, and each processing unit constitutes an independent computing node. The multiple processing units corresponding to the computing resource scheduling unit share a common memory, and each processing node can read and write programs and data in the shared memory. Communication between processing nodes is also conducted through the communication area of this memory using a communication protocol, thereby completing the scheduling of distributed computing resources.
[0087] In one possible implementation, the computing resources include at least one of the following:
[0088] Local computing resources deployed in edge distributed MEC devices;
[0089] In this embodiment, local computing resources are computing resources deployed in edge distributed MEC devices. They have the advantage of fast read speed. However, the computing power of local computing resources is deployed synchronously with the edge distributed MEC devices. Due to the size limitation of the edge distributed MEC devices, the computing power is limited and generally constitutes basic computing services.
[0090] The computing power resources of the computing power pool are deployed in the first computing power expansion device connected to the edge distributed MEC device via a high-speed bus.
[0091] In this embodiment, the computing power pool is an extension of the local computing power resources. It is generally deployed outside the edge distributed MEC device and connected to the edge distributed MEC device through a high-speed bus to extend the computing power resources in the edge distributed MEC device. The computing power pool can be deployed around the edge distributed MEC device, or it can serve multiple edge distributed MEC devices at the same time to realize the sharing of computing power resources.
[0092] Enterprise computing resources deployed in a second computing power extension device connected to edge distributed MEC devices via a computing power resource interface.
[0093] In one possible implementation, the deployment mode of the edge distributed MEC device provided in this application includes:
[0094] Distributed Unit (DU) Deployment Mode; In this mode, the edge distributed MEC device and the distributed unit (DU) are deployed in the same location. The edge distributed MEC device is connected to the centralized unit (CU) via a link, and the edge distributed MEC device communicates through the F1 interface of the 5G wireless network.
[0095] Base station deployment mode; where the base station deployment mode is a deployment mode in which the edge distributed MEC device and the base station are deployed in the same location.
[0096] The lightweight edge distributed MEC device provided in this application includes: a micro-container management module for receiving micro-container orchestration instructions and generating micro-container nodes for managing micro-container applications corresponding to the edge distributed MEC device based on the micro-container orchestration instructions; a container management module for generating container orchestration instructions and managing container applications corresponding to the edge distributed MEC device based on the container orchestration instructions; a virtualization application management module for offloading virtualization tasks of the edge distributed MEC device to the virtual machine corresponding to the parent MEC device of the edge distributed MEC device for execution; and a computing resource management module for allocating computing resources to the micro-container management module, the container management module, and the virtualization application management module. The lightweight edge distributed MEC device provided in this application can be flexibly configured and deployed to meet various workshop-level edge distributed MEC devices with different latency, application deployment methods, and computing capabilities according to enterprise production needs. It has a simple structure and function, low deployment difficulty, and low cost, thus achieving the technical effect of reducing the deployment difficulty and cost of MEC devices.
[0097] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.
[0098] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.
Claims
1. A lightweight edge-distributed MEC device, characterized in that, include: The microcontainer management module is used to receive microcontainer orchestration instructions and generate microcontainer nodes for managing the microcontainer applications corresponding to the edge distributed MEC devices based on the microcontainer orchestration instructions. The microcontainer management module includes a microcontainer orchestration agent unit, a microcontainer node unit, and a microcontainer node management unit. A container management module is used to generate container orchestration instructions and manage container applications corresponding to the edge distributed MEC device based on the container orchestration instructions. The container management module includes a container management unit. The virtualization application management module is used to offload the virtualization tasks of the edge distributed MEC device to the virtual machine corresponding to the upper-level MEC device of the edge distributed MEC device for execution, so as to realize the virtualization application corresponding to the virtualization task; The computing resource management module is used to allocate computing resources to the micro-container management module, the container management module, and the virtualization application management module. The microcontainer orchestration agent unit is used to receive the microcontainer orchestration instructions and generate orchestration instructions for creation, node management and node services based on the microcontainer orchestration instructions. The microcontainer node unit is used to generate, run, shut down, and delete the microcontainer node based on the orchestration instructions; The micro-container node management unit is used to configure the environment of the micro-container node based on the computing power resource management module, and to maintain and manage the clusters corresponding to multiple micro-container nodes. The container management unit is used to receive container orchestration instructions, determine container deployment scripts based on the container orchestration instructions, build and run the container application based on the container deployment scripts, and manage the container application.
2. The device according to claim 1, characterized in that, The microcontainer orchestration agent unit includes: The rule subunit is used to determine the orchestration method corresponding to the microcontainer node based on the operating system and implementation method of the microcontainer node, and to generate the deployment rules of the microcontainer node based on the orchestration method.
3. The device according to claim 2, characterized in that, The microcontainer orchestration agent unit includes: The indicator maintenance subunit is used to determine the microcontainer deployment scheme based on the application scenario of the microcontainer node and the deployment rules; wherein, the microcontainer deployment scheme includes input, modification and maintenance operations for the number of microcontainer nodes, resource allocation and collaboration methods.
4. The device according to claim 3, characterized in that, The microcontainer orchestration agent unit includes: The operation and maintenance subunit is used to monitor and report the operation and real-time status of microcontainer nodes.
5. The device according to claim 4, characterized in that, The microcontainer node management unit includes: An environment management subunit is used to receive environment configuration instructions from the computing resource management module and manage the hardware environment of the micro-container node based on the environment configuration instructions; wherein, the hardware environment includes the deployment rules and deployment scheme corresponding to the micro-container node; The computing power management subunit is used to receive computing power scheduling instructions from the computing power resource management module, and manage the computing power resources corresponding to the micro-container node based on the computing power scheduling instructions to meet the deployment scheme.
6. The device according to claim 1, characterized in that, The computing resource management module includes: The environment configuration management unit is used to generate environment configuration instructions for managing the hardware environment corresponding to the microcontainer management module, the container management module, and the virtualization application management module. The computing resource scheduling unit is used to generate computing resource scheduling instructions for managing the computing resources corresponding to the micro-container management module, the container management module, and the virtualization application management module.
7. The device according to claim 6, characterized in that, The computing resources include at least one of the following: Local computing resources deployed in the edge distributed MEC device; The computing power resources of the computing power pool are deployed in the first computing power expansion device connected to the edge distributed MEC device via a high-speed bus. Enterprise computing resources deployed in a second computing power extension device connected to the edge distributed MEC device via a computing power resource interface.
8. The device according to claim 1, characterized in that, The deployment modes of the edge distributed MEC devices include: Distributed Unit (DU) deployment mode; wherein, the distributed unit (DU) deployment mode is a deployment mode in which the edge distributed MEC device and the distributed unit (DU) are deployed in the same location, the edge distributed MEC device is connected to the centralized unit (CU) via a link, and the edge distributed MEC device communicates through the F1 interface of the 5G wireless network; Base station deployment mode; wherein, the base station deployment mode is a deployment mode in which the edge distributed MEC device and the base station are deployed in the same location.