Information collection method and device, edge cluster and readable storage medium

Abstract

The embodiment of the invention provides an information collection method and device, an edge cluster and a readable storage medium, and the method comprises the steps: the edge cluster is not deployed with an IMS instance, the edge cluster and a central cloud share the IMS instance in the central cloud, and the method comprises the steps: when a network between the central cloud and the edge cluster is interrupted, the edge cluster is not deployed with the IMS instance in the central cloud; establishing a backup IMS instance according to the resource for deploying the IMS instance mirror image and the IMS instance initial mirror image; and obtaining resource information reported by the internal nodes of the edge cluster through the backup IMS instance.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communication technologies, and in particular, to an information collection method, apparatus, edge cluster, and readable storage medium. Background Art

[0002] In the prior art, edge clusters and central clouds are deployed in different geographical locations. Each Open Cloud (O-Cloud) cluster deploys an IMS (Infrastructure Management Service) instance to manage the resources in the cloud platform and report them to Service Management and Orchestration (SMO). If the edge cluster and the central cloud are disconnected due to special circumstances, how to obtain the resource information of each node in the edge cluster during the disconnection period is an urgent problem to be solved. Summary of the Invention

[0003] Embodiments of the present application aim to provide an information collection method, apparatus, edge cluster, and readable storage medium to solve the problem of how to obtain the resource information of each node in the edge cluster during the disconnection period.

[0004] In a first aspect, an information collection method is provided, which is applied to an edge cluster. The edge cluster does not deploy an IMS (Infrastructure Management Service) instance, and the edge cluster shares the IMS instance in the central cloud. The method includes:

[0005] In the case of a network interruption between the central cloud and the edge cluster, a backup IMS instance is established according to the resources for deploying the IMS instance image and the initial image of the IMS instance;

[0006] Resource information reported by internal nodes of the edge cluster is obtained through the backup IMS instance.

[0007] Optionally, before the network interruption between the central cloud and the edge cluster, the method further includes:

[0008] Obtaining a threshold value for the priority of a container or virtual machine;

[0009] Determining a first container or virtual machine that can be scheduled to run to the edge cluster according to the threshold value, where the priority of the first container or virtual machine is less than or equal to the threshold value.

[0010] Optionally, before establishing a backup IMS instance according to the resources for deploying the IMS instance image and the initial image of the IMS instance, the method further includes:

[0011] Obtaining the remaining resources of the edge cluster;

[0012] Determine whether the remaining resources are less than the resources required to deploy the IMS instance image;

[0013] If the remaining resources are less than the resources required to deploy the IMS instance image, terminate the container or virtual machine with the lowest priority in the edge cluster, and recycle the resources occupied by the terminated container or virtual machine. Then, determine whether the remaining resources of the edge cluster after recycling the resources are less than the resources required to deploy the IMS instance image, until the remaining resources of the edge cluster after recycling the resources are greater than or equal to the resources required to deploy the IMS instance image.

[0014] Optionally, when the network between the central cloud and the edge cluster is restored, the method further includes:

[0015] Send the resource information to the IMS instance of the central cloud through the backup IMS instance.

[0016] Optionally, when the network between the central cloud and the edge cluster is restored, the method further includes at least one of the following:

[0017] Terminate the backup IMS instance;

[0018] Restart the second container or virtual machine, where the second container or virtual machine includes the container or virtual machine terminated when the network between the central cloud and the edge cluster is interrupted, and send the first information to the central cloud, where the first information is used to indicate that the state of the second container or virtual machine has been terminated.

[0019] In a second aspect, an information collection device is provided, which is applied to an edge cluster that does not deploy an IMS instance. The edge cluster shares the IMS instance in the central cloud with the central cloud, and includes:

[0020] A first processing module, configured to establish a backup IMS instance according to the resources required to deploy the IMS instance image and the initial image of the IMS instance when the network between the central cloud and the edge cluster is interrupted;

[0021] A second processing module, configured to obtain the resource information reported by the internal nodes of the edge cluster through the backup IMS instance.

[0022] Optionally, the device further includes:

[0023] A first obtaining module, configured to obtain the threshold value of the priority of the container or virtual machine;

[0024] A first determining module, configured to determine the first container or virtual machine that can be scheduled to run to the edge cluster according to the threshold value, where the priority of the first container or virtual machine is less than or equal to the threshold value.

[0025] Optionally, the device further includes:

[0026] A second acquisition module, configured to acquire the remaining resources of the edge cluster;

[0027] A judgment module, configured to judge whether the remaining resources are less than the resources for deploying the IMS instance image;

[0028] A third processing module, configured to, if the remaining resources are less than the resources for deploying the IMS instance image, terminate the container or virtual machine with the lowest priority in the edge cluster, recycle the resources occupied by the terminated container or virtual machine, and then judge whether the remaining resources of the edge cluster after resource recycling are less than the resources for deploying the IMS instance image, until the remaining resources of the edge cluster after resource recycling are greater than or equal to the resources for deploying the IMS instance image.

[0029] Optionally, the device further includes:

[0030] A fourth processing module, configured to send the resource information to the IMS instance of the central cloud through the backup IMS instance.

[0031] Optionally, the device further includes a fifth processing module, configured to perform at least one of the following: terminate the backup IMS instance; restart the second container or virtual machine, where the second container or virtual machine includes the container or virtual machine terminated when the network between the central cloud and the edge cluster is interrupted, and send first information to the central cloud, where the first information is used to indicate that the state of the second container or virtual machine has been terminated.

[0032] In a third aspect, an edge cluster is provided, including a processor, a memory, and a program or instruction stored on the memory and executable on the processor, where when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0033] In a fourth aspect, a readable storage medium is provided, where a program or instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0034] In this application, the edge cluster does not deploy an Infrastructure Management Service (IMS) instance. The edge cluster shares the IMS instance in the central cloud. In the case of a network interruption between the central cloud and the edge cluster, a backup IMS instance is established based on the resources for deploying the IMS instance image and the initial IMS instance image. Resource information reported by the internal nodes of the edge cluster is obtained through the backup IMS instance, that is, a backup IMS instance can be established during the disconnection of the edge cluster, and resource information of each node in the edge cluster can be collected through this backup IMS instance. Description of the Drawings

[0035] By reading the following detailed description of the preferred embodiments, various other advantages and benefits will become clear to those of ordinary skill in the art. The drawings are only for the purpose of showing the preferred embodiments and are not considered to be a limitation of this application. Moreover, throughout the drawings, the same reference numerals are used to represent the same components. In the drawings:

[0036] Figure 1 is a schematic diagram of O-Cloud in the related art;

[0037] Figure 2 is a schematic diagram of the high-level architecture of O-RAN in the related art;

[0038] Figure 3 is a schematic diagram of the interaction between SMO and O-Cloud in the related art;

[0039] Figure 4 is one of the information collection method flows provided by the embodiments of this application;

[0040] Figure 5 is another information collection method flow provided by the embodiments of this application;

[0041] Figure 6 is a schematic diagram of the information collection device provided by the embodiments of this application. Detailed Embodiments

[0042] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the drawings in the embodiments of this application. Obviously, the described embodiments are some, but not all, of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this application without creative efforts shall fall within the protection scope of this application.

[0043] The term "including" and any variations thereof in the description and claims of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products, or devices. In addition, the use of "and / or" in the description and claims indicates at least one of the connected objects. For example, A and / or B means including three cases: A alone, B alone, and both A and B exist.

[0044] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0045] In the Open Radio Access Network (O-RAN) architecture, the SMO is responsible for the management of the RAN domain, as Figure 1 shown.

[0046] O1 interface: The interface between the SMO framework and the Open-cloud (O-Cloud) that supports O-RAN virtual network functions.

[0047] The O2 interface is the interface between the SMO and the O-cloud under the O-RAN architecture, and is used to provide the management of the O-cloud infrastructure platform resources and workloads. The functions performed by the O2 interface for resource management in the current O-RAN architecture description are as follows:

[0048] (1) O-Cloud infrastructure discovery and management;

[0049] (2) O-Cloud infrastructure inwards expansion and outwards expansion;

[0050] (3) Creation, deletion, and allocation of O-Cloud infrastructure resources.

[0051] (4) Scaling up and scaling down the allocated O-Cloud infrastructure resources.

[0052] See Figure 2, the SMO includes Federation O-Cloud Orchestration and Management (FOCOM), Network Function Orchestration (NFO), and Operations Administration and Maintenance (OAM) functions.

[0053] O-Cloud includes: Infrastructure Managed Services (IMS) and Deployment Management Services (DMS).

[0054] Federation O-Cloud Orchestration and Management (FOCOM): FOCOM is responsible for statistics and asset management of resources in the cloud. FOCOM is the main consumer of the services provided by IMS. FOCOM has information about O-Cloud resource management. Specifically, FOCOM needs to know whether the service is within the operator domain or outside.

[0055] Network Function Orchestration (NFO): NFO is responsible for assembling and orchestrating network functions as components of network function (NF) deployments in O-Cloud. It can also utilize the OAM function to access the O1 interface of the NF after deployment. NFO is the main consumer of DMS.

[0056] OAM function: The OAM function is responsible for Fault Configuration Accounting Performance Security (FCAPS) management of the O-RAN management entity. In the context of O2, they can be one of the functional blocks that provide callbacks to receive fault and / or performance data from subscriptions to O2ims or O2dms processes.

[0057] Infrastructure Managed Services (IMS): IMS is responsible for managing O-Cloud resources and the software used to manage these resources. IMS typically provides services for FOCOM to consume.

[0058] Deployment Management Services (DMS): DMS is responsible for managing NF deployments in O-Cloud. It provides the ability to instantiate, monitor, and terminate NF deployments. DMS typically provides services for NFO to consume.

[0059] See Figure 3, in the related art, the edge cluster and the central cloud are deployed in different geographical locations, i.e., different computer rooms. One IMS instance is deployed for each O-Cloud cluster to manage the resources in the cloud platform and report them to the SMO. When the scale of the edge cluster is small, no IMS instance is deployed, and it will be connected to the central cloud as a node and share the IMS instance with the central cloud. If the edge cluster and the central cloud are disconnected due to special circumstances and there is no IMS instance running in the edge cluster, the edge cluster will not report resource data to the IMS instance during the disconnection period. Until the disconnection ends and it reconnects to the IMS instance, the IMS instance continues to collect the reported data after reconnection. The data during the disconnection period will not be reported.

[0060] See Figure 4 , an information collection method provided by an embodiment of the present application is applied to an edge cluster. The edge cluster does not deploy an IMS instance and shares the IMS instance in the central cloud with the central cloud. The specific steps include: step 401 and step 402.

[0061] Step 401: In the case of a network interruption between the central cloud and the edge cluster, establish a backup IMS instance according to the resources for deploying the IMS instance image and the initial image of the IMS instance.

[0062] Optionally, the central cloud can send the resources for deploying the IMS instance image and the relevant information of the initial image of the IMS instance to the edge cluster.

[0063] Step 402: Obtain the resource information reported by the internal nodes of the edge cluster through the backup IMS instance.

[0064] Optionally, the internal nodes of the edge cluster may include, but are not limited to, at least one of the following: servers, storage devices, etc.

[0065] In an implementation manner of the present application, before the network interruption between the central cloud and the edge cluster, the method further includes:

[0066] Obtain the threshold value of the priority of the container or virtual machine;

[0067] Determine the first container or virtual machine that can be scheduled to run to the edge cluster according to the threshold value, and the priority of the first container or virtual machine is less than or equal to the threshold value.

[0068] For example, in an edge cluster, when all other resources except the reserved resources are occupied, only the first container or virtual machine with a priority less than or equal to the threshold value can be scheduled to run to the current edge cluster. If the priority of the container or virtual machine to be deployed is greater than the threshold value, it cannot be scheduled.

[0069] It should be noted that the higher the priority, the more important the virtual machine or container is, and the lower the priority, the less important the virtual machine or container is.

[0070] In an implementation manner of the present application, before establishing a backup IMS instance according to the resources for deploying the IMS instance image and the initial image of the IMS instance, the method further includes:

[0071] Obtain the remaining resources of the edge cluster;

[0072] Determine whether the remaining resources are less than the resources for deploying the IMS instance image;

[0073] If the remaining resources are less than the resources for deploying the IMS instance image, terminate the container or virtual machine with the lowest priority in the edge cluster, and recycle the resources occupied by the terminated container or virtual machine, and then determine whether the remaining resources of the edge cluster after resource recycling are less than the resources for deploying the IMS instance image until the remaining resources of the edge cluster after resource recycling are greater than or equal to the resources for deploying the IMS instance image.

[0074] In an implementation manner of the present application, when the network between the central cloud and the edge cluster is restored, the method further includes:

[0075] Send the resource information to the IMS instance of the central cloud through the backup IMS instance.

[0076] In an implementation manner of the present application, when the network between the central cloud and the edge cluster is restored, the method further includes at least one of the following:

[0077] Terminate the backup IMS instance;

[0078] Restart the second container or virtual machine, where the second container or virtual machine includes the container or virtual machine terminated when the network between the central cloud and the edge cluster is interrupted, and send the first information to the central cloud, where the first information is used to indicate that the state of the second container or virtual machine has been terminated.

[0079] When the network between the central cloud and the edge cluster is interrupted, that is, the edge cluster is out of contact, a backup IMS instance is established in the edge cluster, and the resource information reported by the internal nodes of the edge cluster during the period when the edge cluster is out of contact is obtained through this backup IMS instance. In this way, after reconnection, the resource information collected during the period when the edge cluster is out of contact can be transmitted to the central cloud through this backup IMS instance, ensuring the integrity of the resource information in the central cloud.

[0080] In this application, the infrastructure management service IMS instance is not deployed in the edge cluster, and the edge cluster shares the IMS instance in the central cloud. In the case of a network interruption between the central cloud and the edge cluster, a backup IMS instance is established according to the resources for deploying the IMS instance image and the initial IMS instance image; the resource information reported by the internal nodes of the edge cluster is obtained through the backup IMS instance, that is, a backup IMS instance can be established during the disconnection of the edge cluster, and the resource information of each node in the edge cluster can be collected through the backup IMS instance.

[0081] An optional implementation manner of this application is introduced below in conjunction with Embodiment 1.

[0082] Embodiment 1: Refer to Figure 5 , and the specific steps include:

[0083] Step 501: The central cloud reports the information of the edge clusters affiliated to it to the SMO, reporting which edge clusters do not have IMS instance deployment.

[0084] Step 502: The SMO instructs the central cloud to send the initial IMS instance image to the clusters without IMS instance deployment.

[0085] Step 503: Reserve resources for deploying the IMS instance image in each edge cluster. For example, the resources may include at least one of the following: Central Processing Unit (CPU), hard disk, memory, etc.

[0086] Step 504: Set the threshold value M for the priority of the container or virtual machine. If in an edge cluster, when all other resources except the reserved resources are occupied, only the virtual machines or containers with a priority less than or equal to M can be scheduled to run in the current edge cluster. If the priority of the virtual machine or container to be deployed is greater than M, it will not be scheduled and cannot be deployed.

[0087] In this embodiment, the higher the priority, the more important the virtual machine or container, and the lower the priority, the less important the virtual machine or container.

[0088] There is a network interruption between the central cloud and the edge cluster.

[0089] Step 505: The central cloud reports to the SMO that the disconnected edge cluster cannot report information to the IMS instance in the central cloud. In the information reported by the IMS instance in the central cloud to the SMO, the information of the disconnected edge cluster is missing.

[0090] Step 506: Since the IMS instance requires certain operating resources, there may be a situation where the remaining resources are insufficient to start (launch or restart) the IMS instance. In this case, the K virtual machines or containers with the lowest priority (K >= 1) are terminated in sequence, and the operating resources of the terminated virtual machines or containers are recovered until the remaining resources after recovery meet the requirements for establishing and deploying the IMS instance, and then a backup IMS instance is established. If the remaining resources meet the requirements for deploying the IMS instance, the IMS instance is directly established. The newly established backup IMS instance only receives the resource information reported by the internal nodes of the disconnected cluster.

[0091] Step 507: All nodes in the edge cloud cluster re-register with the backup IMS and send the resource information after the network interruption.

[0092] The network between the central cloud and the edge cluster is restored.

[0093] Step 508: The IMS instance in the edge cluster uploads the stored resource information to the IMS instance in the central cloud, restores the connection state before the network disconnection, and reports that the states of the K virtual machines or containers have been terminated.

[0094] Step 509: Terminate the IMS instance in the edge cluster, restart the K containers of the previous virtual machines or containers in the edge cluster, report the information that the states of the K virtual machines or containers have been terminated to the central cloud and report it to the SMO through the central cloud, and restore to the state before the network interruption.

[0095] See Figure 6 , an information collection device is provided in an embodiment of the present application, which is applied to an edge cluster. The edge cluster does not deploy an IMS instance, and the edge cluster shares the IMS instance in the central cloud with the central cloud. The device 600 includes:

[0096] A first processing module 601, configured to establish a backup IMS instance according to the resources for deploying the IMS instance image and the initial image of the IMS instance when the network between the central cloud and the edge cluster is interrupted;

[0097] A second processing module 602, configured to obtain the resource information reported by the internal nodes of the edge cluster through the backup IMS instance.

[0098] In an implementation manner of the present application, the device further includes:

[0099] A first obtaining module, configured to obtain the threshold value of the priority of the container or virtual machine;

[0100] A first determining module, configured to determine the first container or virtual machine that can be scheduled to run to the edge cluster according to the threshold value, and the priority of the first container or virtual machine is less than or equal to the threshold value.

[0101] In an implementation manner of the present application, the device further includes:

[0102] A second acquisition module, configured to acquire the remaining resources of the edge cluster;

[0103] A judgment module, configured to judge whether the remaining resources are less than the resources for deploying the IMS instance image;

[0104] A third processing module, configured to, if the remaining resources are less than the resources for deploying the IMS instance image, terminate the container or virtual machine with the lowest priority in the edge cluster, recycle the resources occupied by the terminated container or virtual machine, and then judge whether the remaining resources of the edge cluster after resource recycling are less than the resources for deploying the IMS instance image, until the remaining resources of the edge cluster after resource recycling are greater than or equal to the resources for deploying the IMS instance image.

[0105] In an implementation manner of the present application, the device further includes:

[0106] A fourth processing module, configured to send the resource information to the IMS instance of the central cloud through the backup IMS instance.

[0107] In an implementation manner of the present application, the device further includes a fifth processing module, configured to perform at least one of the following: terminate the backup IMS instance; restart the second container or virtual machine, where the second container or virtual machine includes the container or virtual machine terminated when the network between the central cloud and the edge cluster is interrupted, and send first information to the central cloud, where the first information is used to indicate that the state of the second container or virtual machine has been terminated.

[0108] The device provided by the embodiments of the present application can implement Figure 4 each process implemented by the method embodiments shown, and achieve the same technical effects. To avoid repetition, details are not described here again.

[0109] The embodiments of the present application further provide a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the method embodiments shown above is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described here again. Figure 4 The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disc, etc.

[0110] ​

[0111] The steps of the methods or algorithms described in connection with the disclosure of this application may be implemented in hardware or by a processor executing software instructions. The software instructions may consist of corresponding software modules, and the software modules may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may be carried in an ASIC. Additionally, the ASIC may be carried in a core network interface device. Of course, the processor and the storage medium may also exist as discrete components in the core network interface device.

[0112] Those skilled in the art should be able to realize that in one or more of the above examples, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, where communication media includes any medium that facilitates the transfer of a computer program from one place to another. The storage medium can be any available medium accessible by a general-purpose or special-purpose computer.

[0113] The specific embodiments described above further elaborate on the purpose, technical solutions, and beneficial effects of this application. It should be understood that the above description is only for the specific embodiments of this application and is not used to limit the protection scope of this application. Any modifications, equivalent replacements, improvements, etc. made based on the technical solutions of this application should be included within the protection scope of this application.

[0114] Those skilled in the art should understand that the embodiments of this application may be provided as a method, system, or computer program product. Therefore, the embodiments of this application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of this application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0115] Embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing device generate means for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or means for implementing the functions specified in multiple blocks.

[0116] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or means for implementing the functions specified in multiple blocks.

[0117] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or means for implementing the functions specified in multiple blocks.

[0118] Obviously, those skilled in the art can make various modifications and variations to the embodiments of the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims

1. An information collection method is applied to an edge cluster. Characterized in that, The edge cluster does not deploy an Infrastructure Management Service (IMS) instance, and the edge cluster shares the IMS instance in the central cloud with the central cloud. The method includes: In the case of a network interruption between the central cloud and the edge cluster, establish a backup IMS instance according to the resources for deploying the IMS instance image and the initial IMS instance image; Obtain the resource information reported by the internal nodes of the edge cluster through the backup IMS instance.

2. The method according to claim 1, Characterized in that, Before the network interruption between the central cloud and the edge cluster, the method further includes: Obtain the threshold value of the priority of the container or virtual machine; Determine the first container or virtual machine that can be scheduled to run on the edge cluster according to the threshold value, and the priority of the first container or virtual machine is less than or equal to the threshold value.

3. The method according to claim 1, Characterized in that, Before establishing a backup IMS instance according to the resources for deploying the IMS instance image and the initial IMS instance image, the method further includes: Obtain the remaining resources of the edge cluster; Judge whether the remaining resources are less than the resources for deploying the IMS instance image; If the remaining resources are less than the resources for deploying the IMS instance image, terminate the container or virtual machine with the lowest priority in the edge cluster, recycle the resources occupied by the terminated container or virtual machine, and then judge whether the remaining resources of the edge cluster after resource recycling are less than the resources for deploying the IMS instance image until the remaining resources of the edge cluster after resource recycling are greater than or equal to the resources for deploying the IMS instance image.

4. The method according to claim 1, Characterized in that, In the case of network recovery between the central cloud and the edge cluster, the method further includes: Send the resource information to the IMS instance of the central cloud through the backup IMS instance.

5. The method according to claim 1, Characterized in that, In the case of network recovery between the central cloud and the edge cluster, the method further includes at least one of the following: Terminate the backup IMS instance; Restart the second container or virtual machine. The second container or virtual machine includes the container or virtual machine terminated during the network interruption between the central cloud and the edge cluster, and send the first information to the central cloud. The first information is used to indicate that the status of the second container or virtual machine has been terminated.

6. An information collection device is applied to an edge cluster. Characterized in that, The edge cluster does not deploy an IMS instance, and the edge cluster shares the IMS instance in the central cloud with the central cloud. The device includes: A first processing module, configured to establish a backup IMS instance according to the resources for deploying the IMS instance image and the initial IMS instance image in the case of a network interruption between the central cloud and the edge cluster; A second processing module, configured to obtain the resource information reported by the internal nodes of the edge cluster through the backup IMS instance.

7. The device according to claim 6, It is characterized in that the device further comprises: a first acquisition module, configured to acquire a threshold value of the priority of a container or a virtual machine; a first determination module, configured to determine, according to the threshold value, a first container or virtual machine that can be scheduled to run on the edge cluster, where the priority of the first container or virtual machine is less than or equal to the threshold value.

8. The device according to claim 6, It is characterized in that the device further comprises: a second acquisition module, configured to acquire the remaining resources of the edge cluster; a judgment module, configured to judge whether the remaining resources are less than the resources for deploying the IMS instance image; a third processing module, configured to, if the remaining resources are less than the resources for deploying the IMS instance image, terminate the container or virtual machine with the lowest priority in the edge cluster, recycle the resources occupied by the terminated container or virtual machine, and then judge whether the remaining resources of the edge cluster after resource recycling are less than the resources for deploying the IMS instance image, until the remaining resources of the edge cluster after resource recycling are greater than or equal to the resources for deploying the IMS instance image.

9. The device according to claim 6, It is characterized in that the device further comprises: a fourth processing module, configured to send the resource information to the IMS instance of the central cloud through the backup IMS instance.

10. The device according to claim 6, It is characterized in that the device further comprises a fifth processing module, configured to perform at least one of the following: terminate the backup IMS instance; restart a second container or virtual machine, where the second container or virtual machine includes a container or virtual machine terminated during a network interruption between the central cloud and the edge cluster, and send first information to the central cloud, where the first information is used to indicate that the state of the second container or virtual machine has been terminated.

11. An edge cluster, It is characterized in that it includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, where when the program or instruction is executed by the processor, the steps of the method according to any one of claims 1 to 5 are implemented.

12. A readable storage medium, It is characterized in that a program or instruction is stored on the readable storage medium, where when the program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images