Cloud network topology and orchestration methods, devices, computer equipment, and readable storage media

Abstract

The application relates to a cloud network networking arrangement method and device, computer equipment and a computer readable storage medium. The method comprises the following steps: acquiring node information of each network node in a cloud network, and detecting association relationship information between the network nodes; generating a target graph network according to the node information of each network node and the association relationship information between the network nodes, wherein an entity in the target graph network represents a network node in the cloud network, and an edge connecting the entities in the target graph network represents an association relationship between the network nodes in the cloud network; and in response to a networking arrangement request, performing cloud network networking arrangement according to the target graph network. The method can improve the efficiency of cloud network networking arrangement.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a cloud network networking method, apparatus, computer equipment, and computer-readable storage medium. Background Technology

[0002] With the development of Internet technology, cloud network technology has emerged, which can be used to achieve more efficient network interconnection.

[0003] In traditional technologies, cloud platforms typically use relational databases for network orchestration, that is, they use multiple data tables in relational databases for network orchestration.

[0004] However, because multiple tables in a relational database cannot efficiently and clearly express the relationships between network nodes in a cloud network, multiple cross-table queries are often required when using multiple tables in a relational database for network orchestration, resulting in low efficiency in cloud network orchestration. Summary of the Invention

[0005] Therefore, it is necessary to provide a cloud network orchestration method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the efficiency of cloud network orchestration in order to address the above-mentioned technical problems.

[0006] Firstly, this application provides a cloud network networking and orchestration method, including:

[0007] Obtain node information of each network node in the cloud network, and detect the association information between the network nodes;

[0008] A target graph network is generated based on the node information of each network node and the association information between each network node. The entities in the target graph network represent the network nodes in the cloud network, and the edges connecting the entities in the target graph network represent the association relationships between the network nodes in the cloud network.

[0009] In response to the network orchestration request, cloud network orchestration is performed according to the target graph network.

[0010] In one embodiment, the network orchestration request includes a route synchronization request; the step of performing cloud network orchestration according to the target graph network in response to the network orchestration request includes:

[0011] If a route synchronization request is detected, locate the first target entity corresponding to the route synchronization request in the target graph network;

[0012] Detect the network instance type corresponding to the first target entity, and based on the network instance type, detect at least one target routing table entity corresponding to the first target entity in the target graph network;

[0013] Obtain the route information to be synchronized corresponding to the route synchronization request, and synchronize the route information to be synchronized to the network node corresponding to the at least one target routing table entity in the cloud network according to the route information to be synchronized.

[0014] In one embodiment, detecting at least one target routing table entity corresponding to the first target entity in the target graph network according to the network instance type includes:

[0015] If the network instance type is a single-channel network instance, then in the target graph network, find the local gateway instance entity that has a loading relationship with the first target entity, and determine the routing table entity that has an inclusion relationship with the local gateway instance entity as the target routing table entity;

[0016] If the network instance type is a multi-channel network instance, then in the target graph network, find multiple local gateway instance entities that have a loading relationship with the first target entity, and determine multiple routing table entities that have an inclusion relationship with the multiple local gateway instance entities as target routing table entities.

[0017] If the network instance type is a cross-cloud network instance, then in the target graph network, find the local gateway instance entity and the external gateway instance that have a loading relationship with the first target entity, and determine the routing table entity that has an inclusion relationship with the local gateway instance entity as the target routing table entity, and determine the routing table entity that has an inclusion relationship with the external gateway instance as the target routing table entity.

[0018] In one embodiment, the network orchestration request includes a node deletion request; the step of performing cloud network orchestration according to the target graph network in response to the network orchestration request includes:

[0019] If a node deletion request is detected, locate the second target entity corresponding to the node deletion request in the target graph network;

[0020] Based on the entity information and connection edge information of the second target entity in the target graph network, the network nodes corresponding to the second target entity are networked and arranged in the cloud network.

[0021] In one embodiment, the step of orchestrating the network nodes corresponding to the second target entity in the cloud network based on the entity information and connection edge information of the second target entity in the target graph network includes:

[0022] Based on the entity information and connection edge information of the second target entity in the target graph network, the importance of the network node corresponding to the second target entity in the cloud network is scored to obtain an importance score;

[0023] If the importance score is greater than a preset score threshold, then the network node corresponding to the second target entity is retained in the cloud network;

[0024] If the importance score is not greater than a preset score threshold, then the network node corresponding to the second target entity is deleted from the cloud network.

[0025] In one embodiment, the network orchestration request includes a node addition request, and the step of responding to the network orchestration request by performing cloud network orchestration according to the target graph network includes:

[0026] If a node addition request is detected, then based on the new node information corresponding to the node addition request, at least one first associated entity of the node to be added corresponding to the node addition request is located in the target graph network.

[0027] Perform conflict verification between the network node information corresponding to each of the first associated entities and the newly added node information;

[0028] If the conflict verification passes, the node to be added corresponding to the node addition request will be added to the cloud network.

[0029] If the conflict check fails, return the failure information for the new request corresponding to the node.

[0030] In one embodiment, the network orchestration request includes a node update request, and the step of performing cloud network orchestration according to the target graph network in response to the network orchestration request includes:

[0031] If a node update request is detected, the third target entity corresponding to the node update request is located in the target graph network, and at least one second associated entity corresponding to the third target entity is detected.

[0032] Obtain the node update information corresponding to the node update request, and perform conflict verification between the network node information corresponding to each second associated entity and the node update information;

[0033] If the conflict verification passes, then in the cloud network, the node information of the node to be updated corresponding to the node update request is updated.

[0034] If the conflict check fails, return the update failure information corresponding to the node update request.

[0035] Secondly, this application also provides a cloud network networking and orchestration device, comprising:

[0036] The information extraction module is used to obtain node information of each network node in the cloud network and detect the association information between each network node;

[0037] The graph network generation module is used to generate a target graph network based on the node information of each network node and the association information between each network node. The entities in the target graph network represent the network nodes in the cloud network, and the edges connecting the entities in the target graph network represent the association relationships between the network nodes in the cloud network.

[0038] The network orchestration module is used to respond to network orchestration requests and perform cloud network orchestration based on the target graph network.

[0039] In one embodiment, the network orchestration request includes a route synchronization request; the network orchestration module is further configured to:

[0040] If a route synchronization request is detected, locate the first target entity corresponding to the route synchronization request in the target graph network;

[0041] Detect the network instance type corresponding to the first target entity, and based on the network instance type, detect at least one target routing table entity corresponding to the first target entity in the target graph network;

[0042] Obtain the route information to be synchronized corresponding to the route synchronization request, and synchronize the route information to be synchronized to the network node corresponding to the at least one target routing table entity in the cloud network according to the route information to be synchronized.

[0043] In one embodiment, the network orchestration module is further configured to:

[0044] If the network instance type is a single-channel network instance, then in the target graph network, find the local gateway instance entity that has a loading relationship with the first target entity, and determine the routing table entity that has an inclusion relationship with the local gateway instance entity as the target routing table entity;

[0045] If the network instance type is a multi-channel network instance, then in the target graph network, find multiple local gateway instance entities that have a loading relationship with the first target entity, and determine multiple routing table entities that have an inclusion relationship with the multiple local gateway instance entities as target routing table entities.

[0046] If the network instance type is a cross-cloud network instance, then in the target graph network, find the local gateway instance entity and the external gateway instance that have a loading relationship with the first target entity, and determine the routing table entity that has an inclusion relationship with the local gateway instance entity as the target routing table entity, and determine the routing table entity that has an inclusion relationship with the external gateway instance as the target routing table entity.

[0047] In one embodiment, the network orchestration request includes a node deletion request; the network orchestration module is further configured to:

[0048] If a node deletion request is detected, locate the second target entity corresponding to the node deletion request in the target graph network;

[0049] Based on the entity information and connection edge information of the second target entity in the target graph network, the network nodes corresponding to the second target entity are networked and arranged in the cloud network.

[0050] In one embodiment, the network orchestration module is further configured to:

[0051] Based on the entity information and connection edge information of the second target entity in the target graph network, the importance of the network node corresponding to the second target entity in the cloud network is scored to obtain an importance score;

[0052] If the importance score is greater than a preset score threshold, then the network node corresponding to the second target entity is retained in the cloud network;

[0053] If the importance score is not greater than a preset score threshold, then the network node corresponding to the second target entity is deleted from the cloud network.

[0054] In one embodiment, the network orchestration request includes a node addition request; the network orchestration module is further configured to:

[0055] If a node addition request is detected, then based on the new node information corresponding to the node addition request, at least one first associated entity of the node to be added corresponding to the node addition request is located in the target graph network.

[0056] Perform conflict verification between the network node information corresponding to each of the first associated entities and the newly added node information;

[0057] If the conflict verification passes, the node to be added corresponding to the node addition request will be added to the cloud network.

[0058] If the conflict check fails, return the failure information for the new request corresponding to the node.

[0059] In one embodiment, the network orchestration request includes a node update request; the network orchestration module is further configured to:

[0060] If a node update request is detected, the third target entity corresponding to the node update request is located in the target graph network, and at least one second associated entity corresponding to the third target entity is detected.

[0061] Obtain the node update information corresponding to the node update request, and perform conflict verification between the network node information corresponding to each second associated entity and the node update information;

[0062] If the conflict verification passes, then in the cloud network, the node information of the node to be updated corresponding to the node update request is updated.

[0063] If the conflict check fails, return the update failure information corresponding to the node update request.

[0064] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0065] Obtain node information of each network node in the cloud network and detect the association information between each network node; generate a target graph network based on the node information of each network node and the association information between each network node, wherein entities in the target graph network represent network nodes in the cloud network, and edges connecting entities in the target graph network represent the association relationships between network nodes in the cloud network; and perform cloud network orchestration based on the target graph network in response to a network orchestration request.

[0066] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0067] Obtain node information of each network node in the cloud network and detect the association information between each network node; generate a target graph network based on the node information of each network node and the association information between each network node, wherein entities in the target graph network represent network nodes in the cloud network, and edges connecting entities in the target graph network represent the association relationships between network nodes in the cloud network; and perform cloud network orchestration based on the target graph network in response to a network orchestration request.

[0068] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0069] Obtain node information of each network node in the cloud network and detect the association information between each network node; generate a target graph network based on the node information of each network node and the association information between each network node, wherein entities in the target graph network represent network nodes in the cloud network, and edges connecting entities in the target graph network represent the association relationships between network nodes in the cloud network; and perform cloud network orchestration based on the target graph network in response to a network orchestration request.

[0070] The aforementioned cloud network orchestration method, apparatus, computer equipment, and computer-readable storage medium first acquire the node information of each network node in the cloud network and detect the association information between each network node. Then, based on the node information of each network node and the association information between each network node, a target graph network is generated. In the target graph network, entities represent network nodes in the cloud network, and edges connecting entities represent the associations between network nodes in the cloud network. In this way, the target graph network can efficiently and clearly show the associations between network nodes and the node information of the network nodes themselves. Therefore, the target graph network can be used for network orchestration, avoiding the need for multiple cross-table queries during cloud network orchestration, thus improving the efficiency of cloud network orchestration. Attached Figure Description

[0071] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0072] Figure 1 This is a flowchart illustrating a cloud network orchestration method in one embodiment of this application;

[0073] Figure 2 This is a schematic diagram of the graph network structure of the target graph network in one embodiment of this application;

[0074] Figure 3 This is a schematic diagram illustrating the process of cloud network orchestration based on a target graph network in one embodiment of this application;

[0075] Figure 4 This is a schematic diagram illustrating the process of cloud network orchestration based on a target graph network in another embodiment of this application;

[0076] Figure 5 This is a structural block diagram of a cloud network orchestration device in one embodiment;

[0077] Figure 6 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0078] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0079] Currently, cloud platforms typically perform network orchestration based on relational databases, utilizing multiple tables within the relational database. This means that when information about a network segment changes, multiple cross-table queries are required across these relational databases to identify the network nodes associated with the changed segment. Then, these associated network nodes are orchestrated for maintenance. Therefore, the network maintenance efficiency in this application is relatively low when network segment information changes.

[0080] In one exemplary embodiment, such as Figure 1 As shown, a cloud network topology and orchestration method is provided, including the following steps 202 to 206. Wherein:

[0081] Step 202: Obtain node information of each network node in the cloud network and detect the association information between each network node.

[0082] Among them, network nodes can be actual or virtual network nodes such as network instances, cloud network entities, cloud gateways, or routing tables in the cloud network; node information can be the node identifier and node network segment information of the network node; the relationship information can represent the logical relationship and hierarchical relationship between network nodes. The hierarchical relationship can be the inclusion relationship and the composition relationship, and the logical relationship can be the loading relationship and the routing relationship, etc.

[0083] As an example, step 202 includes: obtaining the node network segment information and node identifier of each network node in the cloud network; and detecting the hierarchical and logical relationships between each network node based on the node network segment information and node identifier of each network node to obtain the association relationship information between each network node.

[0084] Step 204: Generate a target graph network based on the node information of each network node and the association information between each network node. In the target graph network, the entities represent the network nodes in the cloud network, and the edges connecting the entities in the target graph network represent the association relationships between the network nodes in the cloud network.

[0085] As an example, step 204 includes: generating graph network entities corresponding to each network node based on the node information of each network node; generating entity connection edges between each graph network entity based on the association information between each network node; and using these entity connection edges to connect each graph network entity to obtain the target graph network.

[0086] Step 206: In response to the network orchestration request, perform cloud network orchestration based on the target network diagram.

[0087] As an example, step 206 includes: triggering the generation of a network orchestration request when the network segment information in the cloud network changes; in response to the network orchestration request, using the target graph network to query at least one network node to be orchestrated corresponding to the network orchestration request, and performing network orchestration on the node network segment information of at least one network node to be orchestrated.

[0088] Reference Figure 2 , Figure 2 A schematic diagram of the graph network structure of the target graph network in one embodiment is shown, consisting of... Figure 2 It can be seen that, Figure 2 The graph shows the graph network entities corresponding to different network nodes and the entity connection edges between graph network entities. The different network nodes include cloud network entities, cloud network instances, cloud gateways, and routing tables. Cloud network instances can be cloud leased line network entities, SD-WAN (Software Defined Wide Area Network) network instances, and VPC (Virtual Private Cloud) network instances, etc. Entity connection edges can represent inclusion relationships, composition relationships, loading relationships, and routing relationships, etc. The ID is the node identifier of the network node.

[0089] In the aforementioned cloud network orchestration method, the node information of each network node in the cloud network is first obtained, and the association information between each network node is detected. Then, based on the node information of each network node and the association information between each network node, a target graph network is generated. In the target graph network, entities represent network nodes in the cloud network, and edges connecting entities represent the associations between network nodes in the cloud network. In this way, the target graph network can efficiently and clearly show the associations between network nodes and the node information of the network nodes themselves. Therefore, the target graph network can be used for network orchestration, avoiding the need for multiple cross-table queries during cloud network orchestration, thus improving the efficiency of cloud network orchestration.

[0090] In one exemplary embodiment, such as Figure 3As shown, the network orchestration request includes a route synchronization request; in response to the network orchestration request, cloud network orchestration is performed according to the target network graph, including:

[0091] Step 302: If a route synchronization request is detected, locate the first target entity corresponding to the route synchronization request in the target graph network.

[0092] In the cloud network, if the routing information of a network node changes, the changed routing information is usually synchronized within the cloud network.

[0093] As an example, step 302 includes: if a route synchronization request is detected, then according to the node identifier in the route synchronization request, locate the first target entity corresponding to the route synchronization request in the target graph network, wherein the first target entity is the graph network entity corresponding to the network node whose routing information has changed.

[0094] Step 304: Detect the network instance type corresponding to the first target entity, and based on the network instance type, detect at least one target routing table entity corresponding to the first target entity in the target graph network.

[0095] In this embodiment, the network node corresponding to the first target entity can be a cloud network instance, and the type of cloud network instance can be a single-channel network instance, a multi-channel network instance, or a cross-cloud network instance, etc. The routing table entities associated with different types of cloud network instances are different.

[0096] As an example, step 304 includes: detecting the network instance type corresponding to the first target entity, and searching for at least one target routing entity corresponding to the first target entity in the target graph network according to the associated entity query method determined by the network instance type.

[0097] As an example, based on the associated entity query method determined by the network instance type, at least one target routing entity corresponding to the first target entity is located in the target graph network, including:

[0098] If the network instance type is a single-channel network instance or a multi-channel network instance, then at least one target routing entity corresponding to the first target entity is searched within the local cloud network where the first target entity is located; if the network instance type is a cross-cloud network instance, then at least one target routing entity corresponding to the first target entity is searched within the multiple cloud networks associated with the first target entity.

[0099] As an example, based on the network instance type, detecting at least one target routing table entity corresponding to a first target entity in the target graph network includes:

[0100] If the network instance type is a single-channel network instance, then in the target graph network, find the local gateway instance entity that has a loading relationship with the first target entity, and determine the routing table entity that has an inclusion relationship with the local gateway instance entity as the target routing table entity; if the network instance type is a multi-channel network instance, then in the target graph network, find multiple local gateway instance entities that have a loading relationship with the first target entity, and determine multiple routing table entities that have an inclusion relationship with multiple local gateway instance entities as the target routing table entity; if the network instance type is a cross-cloud network instance, then in the target graph network, find the local gateway instance entity and the external gateway instance that have a loading relationship with the first target entity, and determine the routing table entity that has an inclusion relationship with the local gateway instance entity as the target routing table entity, and determine the routing table entity that has an inclusion relationship with the external gateway instance as the target routing table entity.

[0101] Among them, a single-channel network entity can be a cloud private line network instance, a multi-channel network instance can be an SD-WAN network instance, and a cross-cloud network instance can be a VPC network instance.

[0102] Specifically, if the network instance type is a single-channel network instance, it means that the first target entity is associated with only one routing table entity, and the routing table lookup scope is the local cloud network. Therefore, in the local cloud network of the first target entity in the target graph network, the local gateway instance entity that has a loading relationship with the first target entity is searched. Where the network nodes corresponding to the local gateway instance entity and the first target entity are within the same cloud network, the routing table entity that has an inclusion relationship with the local gateway instance entity is used as the target routing table entity. If the network instance type is a multi-channel network instance, it means that the first target entity is associated with multiple routing table entities, and the routing table lookup scope is the local local cloud network. Therefore, in the local cloud network of the first target entity in the target graph network, the local gateway instance entity is searched. In the cloud network, multiple local gateway instance entities that have a loading relationship with the first target entity are searched, and multiple routing table entities that have an inclusion relationship with the multiple local gateway instance entities are identified as target routing table entities. If the network instance type is a cross-cloud network instance, it means that the first target entity is associated with routing table entities of multiple different cloud networks. The routing table search scope is the global cloud network. Therefore, in the entire target graph network, local gateway instance entities and external gateway instances that have a loading relationship with the first target entity are searched, and routing table entities that have an inclusion relationship with local gateway instance entities are identified as target routing table entities, and routing table entities that have an inclusion relationship with external gateway instances are identified as target routing table entities.

[0103] In this embodiment, the search range of the routing table entity corresponding to the first target entity in the target graph network can be located based on the network instance type of the first target entity. Therefore, it is possible to query the routing table entity from the target graph network more efficiently, thereby improving the search efficiency of the routing table.

[0104] Step 306: Obtain the route information to be synchronized corresponding to the route synchronization request, and synchronize the route information to be synchronized to at least one network node corresponding to the target routing table entity in the cloud network.

[0105] As an example, step 306 includes: obtaining the route information to be synchronized corresponding to the route synchronization request, and synchronizing the route information to be synchronized to the network nodes corresponding to all target route entities in the cloud network.

[0106] It should be noted that after the route synchronization is completed, the target graph network is updated based on the results of the route synchronization.

[0107] In the above embodiments, the search range of the routing table entity corresponding to the first target entity in the target graph network can be located based on the network instance type of the first target entity. Therefore, it is possible to query the routing table entity from the target graph network more efficiently, thereby enabling more efficient route synchronization and improving the efficiency of route synchronization.

[0108] In one exemplary embodiment, such as Figure 4 As shown, the network orchestration request includes a node deletion request; in response to the network orchestration request, cloud network orchestration is performed according to the target graph network, including:

[0109] Step 402: If a node deletion request is detected, locate the second target entity corresponding to the node deletion request in the target graph network.

[0110] When a network node in the cloud network needs to be deleted, a node deletion request will be triggered.

[0111] As an example, step 402 includes: if a node deletion request is detected, obtaining a node identifier from the node deletion request, and locating a second target entity corresponding to the node deletion request in the target graph network based on the node identifier, wherein the second target entity can be a graph network entity corresponding to the network node to be deleted in the cloud network.

[0112] Step 404: Based on the entity information and connection edge information of the second target entity in the target graph network, perform network arrangement of the network nodes corresponding to the second target entity in the cloud network.

[0113] Among them, entity information can be the node type information of network nodes, and connection edge information can be the number of connection edges.

[0114] As an example, step 404 includes: based on the node type information stored in the target graph network of the second target entity, detecting whether the network node corresponding to the second target entity is a key network node in the cloud network; if the network node corresponding to the second target entity is a key network node in the cloud network, retaining the network node corresponding to the second target entity in the cloud network and returning a deletion failure message; if the network node corresponding to the second target entity is not a key network node in the cloud network, and the number of connection edges corresponding to the second target entity is greater than a preset threshold, retaining the network node corresponding to the second target entity in the cloud network and returning a deletion failure message; and deleting the network node corresponding to the second target entity in the cloud network if the number of connection edges corresponding to the second target entity is not greater than the preset threshold.

[0115] It should be noted that critical network nodes can be cloud network entities. When the number of connection edges between a network node that is a critical network node or the second target entity exceeds a preset threshold, it indicates that the network node corresponding to the second target entity is important in the cloud network. If the network node is deleted directly, it may easily lead to network collapse in the cloud network.

[0116] As an example, based on the entity information and connection edge information of the second target entity in the target graph network, the network nodes corresponding to the second target entity are arranged in the cloud network, including:

[0117] Based on the entity information and connection edge information of the second target entity in the target graph network, the importance of the network node corresponding to the second target entity in the cloud network is scored to obtain an importance score; if the importance score is greater than a preset score threshold, the network node corresponding to the second target entity is retained in the cloud network; if the importance score is not greater than the preset score threshold, the network node corresponding to the second target entity is deleted from the cloud network.

[0118] Specifically, feature extraction is performed on the entity information of the second target entity in the target graph network to obtain entity information features, and feature extraction is performed on the connection edge information of the second target entity in the target graph network to obtain connection edge information features. The entity information features and connection edge information features are fused to obtain target fusion features. Based on the target fusion features, the importance of the network node corresponding to the second target entity in the cloud network is evaluated to obtain an importance score. If the importance score is greater than a preset score threshold, it indicates that the network node corresponding to the second target entity is highly important in the cloud network, and therefore the network node corresponding to the second target entity is retained in the cloud network. If the importance score is not greater than the preset score threshold, it indicates that the network node corresponding to the second target entity is low in importance in the cloud network, and therefore the network node corresponding to the second target entity is deleted from the cloud network.

[0119] In the above embodiments, when a node deletion request is detected, the second target entity corresponding to the node deletion request is first located based on the target graph network. Then, based on the entity information and connection edge information of the second target entity in the target graph network, the importance of the network node corresponding to the second target entity to the cloud network is evaluated. Based on the evaluated importance, it can intelligently choose whether to delete the network node corresponding to the second target entity, making the maintenance of the cloud network more intelligent and convenient.

[0120] In one exemplary embodiment, the network orchestration request includes a node addition request. In response to the network orchestration request, cloud network orchestration is performed according to the target graph network, including:

[0121] If a node addition request is detected, based on the new node information corresponding to the node addition request, at least one first associated entity of the node to be added corresponding to the node addition request is located in the target graph network; conflict verification is performed between the network node information corresponding to each first associated entity and the new node information; if the conflict verification passes, the node to be added corresponding to the node addition request is added in the cloud network; if the conflict verification fails, the addition failure information corresponding to the node addition request is returned.

[0122] Specifically, if a node addition request is detected, the type of the node to be added is determined based on the node addition information corresponding to the node addition request; at least one first associated entity that matches the node addition type is located in the target graph network; it is checked whether the node addition information and the network node information of each first associated entity are the same. If they are the same, it is determined that the network node information corresponding to the first associated entity conflicts with the node addition information, and the addition failure information corresponding to the node addition request is returned; if they are not the same, it is determined that the network node information corresponding to the first associated entity does not conflict with the node addition information, and the node to be added corresponding to the node addition request is added in the cloud network.

[0123] Among them, the information of newly added nodes can be unique information such as the node identifier or routing address of the node to be added, and the information of network nodes corresponding to the first associated entity can be unique information such as the node identifier or routing address of the network node corresponding to the first associated entity.

[0124] In the above embodiments, when a node addition request is detected, at least one first associated entity corresponding to the node to be added can be automatically located using the target graph network. This allows for automatic conflict verification between the information of the new node and the network node information of the first associated entity, thereby determining whether to add the node to be added to the cloud network. This achieves automatic network maintenance for the node addition process of the cloud network, which helps to improve the network maintenance efficiency of the cloud network.

[0125] In one exemplary embodiment, the network orchestration request includes a node update request. In response to the network orchestration request, cloud network orchestration is performed according to the target graph network, including:

[0126] If a node update request is detected, the third target entity corresponding to the node update request is located in the target graph network, and at least one second associated entity corresponding to the third target entity is detected; the node update information corresponding to the node update request is obtained, and a conflict check is performed between the network node information corresponding to each second associated entity and the node update information; if the conflict check passes, the node information of the node to be updated corresponding to the node update request is updated in the cloud network; if the conflict check fails, the update failure information corresponding to the node update request is returned.

[0127] Specifically, if a node update request is detected, the node identifier is obtained from the node update request, and the node identifier is used to locate the third target entity corresponding to the node update request in the target graph network. At least one second associated entity with a connection edge to the third target entity is detected, where the third target entity is the graph network entity corresponding to the network node to be updated in the cloud network in the target graph network. The node update information corresponding to the node update request is obtained. The node update information is checked to see if it is the same as the network node information of each second associated entity. If they are the same, it is determined that the network node information corresponding to the second associated entity conflicts with the node update information, and the update failure information corresponding to the node update request is returned. If they are not the same, it is determined that the network node information corresponding to the second associated entity does not conflict with the node update information, and the node information of the node to be updated corresponding to the node update request is updated in the cloud network.

[0128] Among them, the node update information can be unique information such as the node identifier or routing address of the node to be updated after the update, and the network node information corresponding to the second associated entity can be unique information such as the node identifier or routing address of the network node corresponding to the second associated entity.

[0129] In the above embodiments, when a node update request is detected, the target graph network can be used to automatically locate the third target entity corresponding to the node to be updated, and detect at least one second associated entity corresponding to the third target entity. This allows for automatic conflict verification between the node update information and the network node information of the second associated entity, thereby determining whether to add the node information of the node to be updated in the cloud network for updating. This achieves automatic network maintenance of the node update process in the cloud network, which helps to improve the network maintenance efficiency of the cloud network.

[0130] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0131] Based on the same inventive concept, this application also provides a cloud network orchestration device for implementing the cloud network orchestration method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more cloud network orchestration device embodiments provided below can be found in the limitations of the cloud network orchestration method described above, and will not be repeated here.

[0132] In one exemplary embodiment, such as Figure 5 As shown, a cloud network orchestration device is provided, including: an information extraction module 502, a graph network generation module 504, and a network orchestration module 506, wherein:

[0133] The information extraction module 502 is used to obtain node information of each network node in the cloud network and detect the association information between each network node.

[0134] The graph network generation module 504 is used to generate a target graph network based on the node information of each network node and the association information between each network node. The entities in the target graph network represent the network nodes in the cloud network, and the edges connecting the entities in the target graph network represent the association relationships between the network nodes in the cloud network.

[0135] The network orchestration module 506 is used to respond to the network orchestration request and perform cloud network orchestration according to the target graph network.

[0136] In one embodiment, the network orchestration request includes a route synchronization request; the network orchestration module is further configured to:

[0137] If a route synchronization request is detected, locate the first target entity corresponding to the route synchronization request in the target graph network;

[0138] Detect the network instance type corresponding to the first target entity, and based on the network instance type, detect at least one target routing table entity corresponding to the first target entity in the target graph network;

[0139] Obtain the route information to be synchronized corresponding to the route synchronization request, and synchronize the route information to be synchronized to the network node corresponding to the at least one target routing table entity in the cloud network according to the route information to be synchronized.

[0140] In one embodiment, the network orchestration module is further configured to:

[0141] If the network instance type is a single-channel network instance, then in the target graph network, find the local gateway instance entity that has a loading relationship with the first target entity, and determine the routing table entity that has an inclusion relationship with the local gateway instance entity as the target routing table entity;

[0142] If the network instance type is a multi-channel network instance, then in the target graph network, find multiple local gateway instance entities that have a loading relationship with the first target entity, and determine multiple routing table entities that have an inclusion relationship with the multiple local gateway instance entities as target routing table entities.

[0143] If the network instance type is a cross-cloud network instance, then in the target graph network, find the local gateway instance entity and the external gateway instance that have a loading relationship with the first target entity, and determine the routing table entity that has an inclusion relationship with the local gateway instance entity as the target routing table entity, and determine the routing table entity that has an inclusion relationship with the external gateway instance as the target routing table entity.

[0144] In one embodiment, the network orchestration request includes a node deletion request; the network orchestration module is further configured to:

[0145] If a node deletion request is detected, locate the second target entity corresponding to the node deletion request in the target graph network;

[0146] Based on the entity information and connection edge information of the second target entity in the target graph network, the network nodes corresponding to the second target entity are networked and arranged in the cloud network.

[0147] In one embodiment, the network orchestration module is further configured to:

[0148] Based on the entity information and connection edge information of the second target entity in the target graph network, the importance of the network node corresponding to the second target entity in the cloud network is scored to obtain an importance score;

[0149] If the importance score is greater than a preset score threshold, then the network node corresponding to the second target entity is retained in the cloud network;

[0150] If the importance score is not greater than a preset score threshold, then the network node corresponding to the second target entity is deleted from the cloud network.

[0151] In one embodiment, the network orchestration request includes a node addition request; the network orchestration module is further configured to:

[0152] If a node addition request is detected, then based on the new node information corresponding to the node addition request, at least one first associated entity of the node to be added corresponding to the node addition request is located in the target graph network.

[0153] Perform conflict verification between the network node information corresponding to each of the first associated entities and the newly added node information;

[0154] If the conflict verification passes, the node to be added corresponding to the node addition request will be added to the cloud network.

[0155] If the conflict check fails, return the failure information for the new request corresponding to the node.

[0156] In one embodiment, the network orchestration request includes a node update request; the network orchestration module is further configured to:

[0157] If a node update request is detected, the third target entity corresponding to the node update request is located in the target graph network, and at least one second associated entity corresponding to the third target entity is detected.

[0158] Obtain the node update information corresponding to the node update request, and perform conflict verification between the network node information corresponding to each second associated entity and the node update information;

[0159] If the conflict verification passes, then in the cloud network, the node information of the node to be updated corresponding to the node update request is updated.

[0160] If the conflict check fails, return the update failure information corresponding to the node update request.

[0161] Each module in the aforementioned cloud network orchestration device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0162] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 6 As shown. The computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a cloud network networking and orchestration method. Those skilled in the art will understand that... Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0163] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0164] Obtain node information of each network node in the cloud network and detect the association information between each network node; generate a target graph network based on the node information of each network node and the association information between each network node, wherein entities in the target graph network represent network nodes in the cloud network, and edges connecting entities in the target graph network represent the association relationships between network nodes in the cloud network; and perform cloud network orchestration based on the target graph network in response to a network orchestration request.

[0165] In one embodiment, the network orchestration request includes a routing synchronization request; the processor, when executing the computer program, also performs the following steps:

[0166] If a route synchronization request is detected, locate the first target entity corresponding to the route synchronization request in the target graph network; detect the network instance type corresponding to the first target entity, and based on the network instance type, detect at least one target routing table entity corresponding to the first target entity in the target graph network; obtain the route information to be synchronized corresponding to the route synchronization request, and based on the route information to be synchronized, synchronize the route information to be synchronized to the network node corresponding to the at least one target routing table entity in the cloud network.

[0167] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0168] If the network instance type is a single-channel network instance, then in the target graph network, a local gateway instance entity that has a loading relationship with the first target entity is searched, and a routing table entity that has an inclusion relationship with the local gateway instance entity is determined as the target routing table entity; if the network instance type is a multi-channel network instance, then in the target graph network, multiple local gateway instance entities that have a loading relationship with the first target entity are searched, and multiple routing table entities that have an inclusion relationship with the multiple local gateway instance entities are determined as the target routing table entity; if the network instance type is a cross-cloud network instance, then in the target graph network, a local gateway instance entity and an external gateway instance that have a loading relationship with the first target entity are searched, and a routing table entity that has an inclusion relationship with the local gateway instance entity and a routing table entity that has an inclusion relationship with the external gateway instance are determined as the target routing table entity.

[0169] In one embodiment, the network orchestration request includes a node deletion request; the processor, when executing the computer program, also performs the following steps:

[0170] If a node deletion request is detected, the second target entity corresponding to the node deletion request is located in the target graph network; based on the entity information and connection edge information of the second target entity in the target graph network, the network nodes corresponding to the second target entity are arranged in the cloud network.

[0171] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0172] Based on the entity information and connection edge information of the second target entity in the target graph network, the importance of the network node corresponding to the second target entity in the cloud network is scored to obtain an importance score; if the importance score is greater than a preset scoring threshold, the network node corresponding to the second target entity is retained in the cloud network; if the importance score is not greater than the preset scoring threshold, the network node corresponding to the second target entity is deleted from the cloud network.

[0173] In one embodiment, the network orchestration request includes a node addition request; the processor, when executing the computer program, also performs the following steps:

[0174] If a node addition request is detected, at least one first associated entity of the node to be added corresponding to the node addition request is located in the target graph network according to the new node information corresponding to the node addition request; a conflict check is performed between the network node information corresponding to each first associated entity and the new node information; if the conflict check passes, the node to be added corresponding to the node addition request is added in the cloud network; if the conflict check fails, the addition failure information corresponding to the node addition request is returned.

[0175] In one embodiment, the network orchestration request includes a node update request; the processor, when executing the computer program, also performs the following steps:

[0176] If a node update request is detected, the third target entity corresponding to the node update request is located in the target graph network, and at least one second associated entity corresponding to the third target entity is detected; the node update information corresponding to the node update request is obtained, and a conflict check is performed between the network node information corresponding to each second associated entity and the node update information; if the conflict check passes, the node information of the node to be updated corresponding to the node update request is updated in the cloud network; if the conflict check fails, the update failure information corresponding to the node update request is returned.

[0177] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0178] Obtain node information of each network node in the cloud network and detect the association information between each network node; generate a target graph network based on the node information of each network node and the association information between each network node, wherein entities in the target graph network represent network nodes in the cloud network, and edges connecting entities in the target graph network represent the association relationships between network nodes in the cloud network; and perform cloud network orchestration based on the target graph network in response to a network orchestration request.

[0179] In one embodiment, the network orchestration request includes a routing synchronization request; the computer program, when executed by a processor, also performs the following steps:

[0180] If a route synchronization request is detected, locate the first target entity corresponding to the route synchronization request in the target graph network; detect the network instance type corresponding to the first target entity, and based on the network instance type, detect at least one target routing table entity corresponding to the first target entity in the target graph network; obtain the route information to be synchronized corresponding to the route synchronization request, and based on the route information to be synchronized, synchronize the route information to be synchronized to the network node corresponding to the at least one target routing table entity in the cloud network.

[0181] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0182] If the network instance type is a single-channel network instance, then in the target graph network, a local gateway instance entity that has a loading relationship with the first target entity is searched, and a routing table entity that has an inclusion relationship with the local gateway instance entity is determined as the target routing table entity; if the network instance type is a multi-channel network instance, then in the target graph network, multiple local gateway instance entities that have a loading relationship with the first target entity are searched, and multiple routing table entities that have an inclusion relationship with the multiple local gateway instance entities are determined as the target routing table entity; if the network instance type is a cross-cloud network instance, then in the target graph network, a local gateway instance entity and an external gateway instance that have a loading relationship with the first target entity are searched, and a routing table entity that has an inclusion relationship with the local gateway instance entity and a routing table entity that has an inclusion relationship with the external gateway instance are determined as the target routing table entity.

[0183] In one embodiment, the network orchestration request includes a node deletion request; when the computer program is executed by the processor, it further performs the following steps:

[0184] If a node deletion request is detected, the second target entity corresponding to the node deletion request is located in the target graph network; based on the entity information and connection edge information of the second target entity in the target graph network, the network nodes corresponding to the second target entity are arranged in the cloud network.

[0185] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0186] Based on the entity information and connection edge information of the second target entity in the target graph network, the importance of the network node corresponding to the second target entity in the cloud network is scored to obtain an importance score; if the importance score is greater than a preset scoring threshold, the network node corresponding to the second target entity is retained in the cloud network; if the importance score is not greater than the preset scoring threshold, the network node corresponding to the second target entity is deleted from the cloud network.

[0187] In one embodiment, the network orchestration request includes a node addition request; when the computer program is executed by the processor, it also performs the following steps:

[0188] If a node addition request is detected, at least one first associated entity of the node to be added corresponding to the node addition request is located in the target graph network according to the new node information corresponding to the node addition request; a conflict check is performed between the network node information corresponding to each first associated entity and the new node information; if the conflict check passes, the node to be added corresponding to the node addition request is added in the cloud network; if the conflict check fails, the addition failure information corresponding to the node addition request is returned.

[0189] In one embodiment, the network orchestration request includes a node update request; when the computer program is executed by the processor, it further performs the following steps:

[0190] If a node update request is detected, the third target entity corresponding to the node update request is located in the target graph network, and at least one second associated entity corresponding to the third target entity is detected; the node update information corresponding to the node update request is obtained, and a conflict check is performed between the network node information corresponding to each second associated entity and the node update information; if the conflict check passes, the node information of the node to be updated corresponding to the node update request is updated in the cloud network; if the conflict check fails, the update failure information corresponding to the node update request is returned.

[0191] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0192] Obtain node information of each network node in the cloud network and detect the association information between each network node; generate a target graph network based on the node information of each network node and the association information between each network node, wherein entities in the target graph network represent network nodes in the cloud network, and edges connecting entities in the target graph network represent the association relationships between network nodes in the cloud network; and perform cloud network orchestration based on the target graph network in response to a network orchestration request.

[0193] In one embodiment, the network orchestration request includes a routing synchronization request; the computer program, when executed by a processor, also performs the following steps:

[0194] If a route synchronization request is detected, locate the first target entity corresponding to the route synchronization request in the target graph network; detect the network instance type corresponding to the first target entity, and based on the network instance type, detect at least one target routing table entity corresponding to the first target entity in the target graph network; obtain the route information to be synchronized corresponding to the route synchronization request, and based on the route information to be synchronized, synchronize the route information to be synchronized to the network node corresponding to the at least one target routing table entity in the cloud network.

[0195] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0196] If the network instance type is a single-channel network instance, then in the target graph network, a local gateway instance entity that has a loading relationship with the first target entity is searched, and a routing table entity that has an inclusion relationship with the local gateway instance entity is determined as the target routing table entity; if the network instance type is a multi-channel network instance, then in the target graph network, multiple local gateway instance entities that have a loading relationship with the first target entity are searched, and multiple routing table entities that have an inclusion relationship with the multiple local gateway instance entities are determined as the target routing table entity; if the network instance type is a cross-cloud network instance, then in the target graph network, a local gateway instance entity and an external gateway instance that have a loading relationship with the first target entity are searched, and a routing table entity that has an inclusion relationship with the local gateway instance entity and a routing table entity that has an inclusion relationship with the external gateway instance are determined as the target routing table entity.

[0197] In one embodiment, the network orchestration request includes a node deletion request; when the computer program is executed by the processor, it further performs the following steps:

[0198] If a node deletion request is detected, the second target entity corresponding to the node deletion request is located in the target graph network; based on the entity information and connection edge information of the second target entity in the target graph network, the network nodes corresponding to the second target entity are arranged in the cloud network.

[0199] In one embodiment, when the computer program is executed by a processor, it also performs the following steps:

[0200] Based on the entity information and connection edge information of the second target entity in the target graph network, the importance of the network node corresponding to the second target entity in the cloud network is scored to obtain an importance score; if the importance score is greater than a preset scoring threshold, the network node corresponding to the second target entity is retained in the cloud network; if the importance score is not greater than the preset scoring threshold, the network node corresponding to the second target entity is deleted from the cloud network.

[0201] In one embodiment, the network orchestration request includes a node addition request; when the computer program is executed by the processor, it also performs the following steps:

[0202] If a node addition request is detected, at least one first associated entity of the node to be added corresponding to the node addition request is located in the target graph network according to the new node information corresponding to the node addition request; a conflict check is performed between the network node information corresponding to each first associated entity and the new node information; if the conflict check passes, the node to be added corresponding to the node addition request is added in the cloud network; if the conflict check fails, the addition failure information corresponding to the node addition request is returned.

[0203] In one embodiment, the network orchestration request includes a node update request; when the computer program is executed by the processor, it further performs the following steps:

[0204] If a node update request is detected, the third target entity corresponding to the node update request is located in the target graph network, and at least one second associated entity corresponding to the third target entity is detected; the node update information corresponding to the node update request is obtained, and a conflict check is performed between the network node information corresponding to each second associated entity and the node update information; if the conflict check passes, the node information of the node to be updated corresponding to the node update request is updated in the cloud network; if the conflict check fails, the update failure information corresponding to the node update request is returned.

[0205] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0206] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0207] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A cloud network configuration and arrangement method, characterized in that, The method comprises: obtaining node information of each network node in a cloud network, and detecting association relationship information between each network node; generating a target graph network according to the node information of each network node and the association relationship information between each network node, wherein an entity in the target graph network represents a network node in the cloud network, and an edge connecting entities in the target graph network represents an association relationship between network nodes in the cloud network; performing cloud network networking arrangement according to the target graph network in response to a networking arrangement request.

2. The method of claim 1, wherein, The networking arrangement request comprises a route synchronization request; The cloud network networking arrangement according to the target graph network in response to the networking arrangement request comprises: if a route synchronization request is detected, locating a first target entity corresponding to the route synchronization request in the target graph network; detecting a network instance type corresponding to the first target entity, and detecting at least one target route table entity corresponding to the first target entity in the target graph network according to the network instance type; obtaining to-be-synchronized route information corresponding to the route synchronization request, and synchronizing the to-be-synchronized route information to network nodes corresponding to the at least one target route table entity in the cloud network according to the to-be-synchronized route information.

3. The method of claim 2, wherein, The detecting at least one target route table entity corresponding to the first target entity in the target graph network according to the network instance type comprises: if the network instance type is a single-channel network instance, searching for a local gateway instance entity having a loading relationship with the first target entity in the target graph network, and determining a route table entity having an inclusion relationship with the local gateway instance entity as a target route table entity; if the network instance type is a multi-channel network instance, searching for a plurality of local gateway instance entities having a loading relationship with the first target entity in the target graph network respectively, and determining a plurality of route table entities having an inclusion relationship with the plurality of local gateway instance entities as target route table entities; if the network instance type is a cross-cloud network instance, searching for a local gateway instance entity and an external network gateway instance having a loading relationship with the first target entity in the target graph network, determining a route table entity having an inclusion relationship with the local gateway instance entity as a target route table entity, and determining a route table entity having an inclusion relationship with the external network gateway instance as a target route table entity.

4. The method of claim 1, wherein, The networking arrangement request comprises a node deletion request; and the cloud network networking arrangement according to the target graph network in response to the networking arrangement request comprises: if a node deletion request is detected, locating a second target entity corresponding to the node deletion request in the target graph network; performing networking arrangement on a network node corresponding to the second target entity in the cloud network according to entity information and connection edge information of the second target entity in the target graph network.

5. The method of claim 4, wherein, The network arrangement request comprises a node addition request. The cloud network arrangement comprises: if the node addition request is detected, at least one first associated entity of a node to be added corresponding to the node addition request is located in the target graph network according to the node addition request corresponding node information; the network node information corresponding to each first associated entity and the node addition information are conflict checked; 6. The method of claim 1, wherein, if the conflict checking is passed, the node corresponding to the node addition request is added in the cloud network; if the conflict checking is not passed, the addition failure information corresponding to the node addition request is returned. The network arrangement request comprises a node update request; the cloud network arrangement comprises: if the node update request is detected, a third target entity corresponding to the node update request is located in the target graph network, and at least one second associated entity corresponding to the third target entity is detected; the node update information corresponding to the node update request is obtained, and the network node information corresponding to each second associated entity and the node update information are conflict checked; if the conflict checking is passed, the node information of the node corresponding to the node update request is updated in the cloud network; 7. The method of claim 1, wherein, if the conflict checking is not passed, the update failure information corresponding to the node update request is returned. The device comprises: an information extraction module configured to obtain node information of each network node in a cloud network and detect association relationship information between the network nodes; a graph network generation module configured to generate a target graph network according to the node information of each network node and the association relationship information between the network nodes, wherein an entity in the target graph network represents a network node in the cloud network, and an edge connecting the entities in the target graph network represents an association relationship between the network nodes in the cloud network; a network arrangement module configured to perform cloud network arrangement according to the target graph network in response to a network arrangement request.

8. A cloud network networking and orchestration apparatus, characterized by comprising: The processor executes the computer program to implement the steps of the method in any one of claims 1 to 7. The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 7. ​ ​ 9.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-8 when the computer program is executed by the processor. ​ 10. A computer-readable storage medium having stored thereon a computer program, characterized in that, ​

Images