Configuration processing method and device and storage medium

Abstract

The embodiment of the invention provides a configuration processing method and device and a storage medium, which can relate to the cloud technology, the method is applied to a control system, the control system comprises a core layer node and a plurality of access layer nodes, and the method comprises the following steps: the core layer node determines a target network device which takes effect for the creation of the configuration, determining a target access layer node corresponding to the target network equipment; the core layer node sends a creation configuration request to the target access layer node; the target access layer node analyzes the creation configuration request to obtain a target final state model, a creation operation type and information of target network equipment; analyzing the target final state model to obtain target final state configuration; based on the target final state configuration, the creation operation type and the information of the target network equipment, generating a creation configuration instruction; and the target access layer node issues a configuration creation instruction to the target network equipment, so that the target network equipment creates target final-state configuration.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of cloud technology, and in particular to a configuration processing method, device, and storage medium. Background Art

[0002] At present, the cloud control system is mainly used to manage a large number of network devices. For example, the control system sends a create configuration instruction to the network device so that the network device creates a configuration based on the create configuration instruction. For another example, the control system sends an update configuration instruction to the network device so that the network device updates the configuration based on the update configuration instruction. For another example, the control system sends a delete configuration instruction to the network device so that the network device deletes the configuration based on the delete configuration instruction.

[0003] At present, the control system may include a core layer node and multiple access layer nodes. The core layer node is oriented to multiple services. Each access layer node is located at the edge of the network and is oriented to one or a small number of services. Each access layer node can communicate with network devices within a certain area. How to configure and process based on the current control system architecture is a technical problem to be solved in this application. Summary of the invention

[0004] The embodiments of the present application provide a configuration processing method, device and storage medium to solve the technical problem of how to perform configuration processing based on the current control system architecture.

[0005] In a first aspect, an embodiment of the present application provides a configuration processing method, which is applied to a control system, the control system comprising: a core layer node and multiple access layer nodes, the method comprising: the core layer node determines the target network device for which the configuration creation is effective, and determines the target access layer node corresponding to the target network device; the core layer node sends a configuration creation request to the target access layer node; wherein the configuration creation request comprises: a target final state model, a creation operation type and information of the target network device; the target final state model is used to describe the target final state configuration; the target access layer node parses the configuration creation request to obtain the target final state model, the creation operation type and information of the target network device; and parses the target final state model to obtain the target final state configuration; and based on the target final state configuration, the creation operation type and information of the target network device, generates a configuration creation instruction; the target access layer node sends the configuration creation instruction to the target network device; wherein the configuration creation instruction is used for the target network device to create the target final state configuration.

[0006] In a second aspect, an embodiment of the present application provides a configuration processing method, which is applied to a control system, the control system comprising: a core layer node and multiple access layer nodes, the method comprising: the core layer node determines the target network device for which the updated configuration is effective, and determines the target access layer node corresponding to the target network device; the core layer node sends an update configuration request to the target access layer node; wherein the update configuration request comprises: a target update model, an update operation type and information of the target network device; the target update model is used to update the target final state configuration to be updated in the target final state configuration described by the target final state model; the target access layer node parses the update configuration request to obtain the target update model, the update operation type and information of the target network device; and parses the target update model to obtain content information carried by the target update model; and based on the content information, the update operation type and information of the target network device, generates an update configuration instruction; the target access layer node sends the update configuration instruction to the target network device; wherein the update configuration instruction is used for the target network device to update the final state configuration to be updated.

[0007] In a third aspect, an embodiment of the present application provides a configuration processing method, which is applied to a control system, the control system comprising: a core layer node and multiple access layer nodes, the method comprising: the core layer node determines the target network device for which the current deletion configuration is effective, and determines the target access layer node corresponding to the target network device; the core layer node sends a deletion configuration request to the target access layer node; wherein the deletion configuration request comprises: a target final state model, a deletion operation type and information about the target network device; the target final state model is used to describe the target final state configuration; the target access layer node parses the deletion configuration request to obtain the target final state model, the deletion operation type and information about the target network device; and parses the target final state model to obtain the target final state configuration; and based on the target final state configuration, the deletion operation type and information about the target network device, generates a deletion configuration instruction; the target access layer node sends the deletion configuration instruction to the target network device; wherein the deletion configuration instruction is used for the target network device to delete the target final state configuration.

[0008] In a fourth aspect, an embodiment of the present application provides a control system, which includes: a core layer node and multiple access layer nodes, wherein the core layer node is used to: determine the target network device for which the creation configuration is effective, and determine the target access layer node corresponding to the target network device; send a creation configuration request to the target access layer node; wherein the creation configuration request includes: a target final state model, a creation operation type, and information about the target network device; the target final state model is used to describe the target final state configuration; the target access layer node is used to: parse the creation configuration request to obtain the target final state model, the creation operation type, and information about the target network device; and parse the target final state model to obtain the target final state configuration; and based on the target final state configuration, the creation operation type, and information about the target network device, generate a creation configuration instruction; and issue the creation configuration instruction to the target network device; wherein the creation configuration instruction is used for the target network device to create the target final state configuration.

[0009] In a fifth aspect, an embodiment of the present application provides a control system, which includes: a core layer node and multiple access layer nodes, wherein the core layer node is used to: determine the target network device for which the current update configuration is effective, and determine the target access layer node corresponding to the target network device; send an update configuration request to the target access layer node; wherein the update configuration request includes: a target update model, an update operation type, and information about the target network device; the target update model is used to update the target final state configuration to be updated in the target final state configuration described by the target final state model; parse the update configuration request to obtain the target update model, the update operation type, and information about the target network device; and parse the target update model to obtain content information carried by the target update model; and generate an update configuration instruction based on the content information, the update operation type, and information about the target network device; the target access layer node is used to: send an update configuration instruction to the target network device; wherein the update configuration instruction is used for the target network device to update the final state configuration to be updated.

[0010] In a sixth aspect, an embodiment of the present application provides a control system, which includes: a core layer node and multiple access layer nodes, wherein the core layer node is used to: determine the target network device for which the current deletion configuration is effective, and determine the target access layer node corresponding to the target network device; send a deletion configuration request to the target access layer node; wherein the deletion configuration request includes: a target final state model, a deletion operation type, and information about the target network device; the target final state model is used to describe the target final state configuration; the target access layer node is used to: parse the deletion configuration request to obtain the target final state model, the deletion operation type, and information about the target network device; and parse the target final state model to obtain the target final state configuration; and based on the target final state configuration, the deletion operation type, and information about the target network device, generate a deletion configuration instruction; and send the deletion configuration instruction to the target network device; wherein the deletion configuration instruction is used for the target network device to delete the target final state configuration.

[0011] In the seventh aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, and executing a method as in any one of the first to third aspects or its various implementation methods.

[0012] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute a method as in any one of the first to third aspects or any of their implementations.

[0013] In a ninth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute a method as in any one of the first to third aspects or any of their implementations.

[0014] In a tenth aspect, an embodiment of the present application provides a computer program, which enables a computer to execute a method as in any one of the first to third aspects or any of their implementations.

[0015] Through the technical solution provided by this application, configuration creation, update and deletion can be performed based on the current control system architecture, thereby solving the technical problem of how to perform configuration processing based on the current control system architecture. In addition, core layer nodes are usually oriented to multiple businesses. Regardless of the business, the core layer nodes regard the target final state model and the target update model as black boxes, that is, the target final state model and the target update model are not parsed. Based on this, from the perspective of software development, the software code of the core layer nodes does not need to be changed for any business, thereby improving the reusability of the core layer nodes. Improving the reusability of the core layer nodes has important significance and value, such as improving development efficiency, reducing maintenance costs, improving software quality, promoting modularization and standardization, and improving resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 An application scenario diagram provided for an embodiment of the present application;

[0017] Figure 2 Another application scenario diagram provided for an embodiment of the present application;

[0018] Figure 3 An interactive flow chart of a configuration processing method provided in an embodiment of the present application;

[0019] Figure 4 An interactive flow chart of another configuration processing method provided in an embodiment of the present application;

[0020] Figure 5 An example schematic diagram of updating a final state model provided in an embodiment of the present application;

[0021] Figure 6 An interactive flow chart of another configuration processing method provided in an embodiment of the present application;

[0022] Figure 7 It is a schematic block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0024] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or server 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 that are not clearly listed or inherent to these processes, methods, products, or devices.

[0025] Embodiments of the present application may involve cloud technology.

[0026] Cloud technology refers to a hosting technology that unifies hardware, software, network and other resources within a wide area network or local area network to achieve data computing, storage, processing and sharing.

[0027] Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, application technology, etc. based on the cloud computing business model. It can form a resource pool, which can be used on demand and is flexible and convenient. Cloud computing technology will become an important support. The backend services of the technical network system require a large amount of computing and storage resources, such as video websites, picture websites and more portal websites. With the rapid development and application of the Internet industry, in the future, each item may have its own identification mark, which needs to be transmitted to the backend system for logical processing. Data of different levels will be processed separately. All kinds of industry data need strong system backing support, which can only be achieved through cloud computing.

[0028] Cloud computing refers to the delivery and use model of IT infrastructure, which means obtaining required resources through the network in an on-demand and easily scalable manner; in a broad sense, cloud computing refers to the delivery and use model of services, which means obtaining required services through the network in an on-demand and easily scalable manner. This service can be IT and software, Internet-related, or other services. Cloud computing is the product of the development and integration of traditional computer and network technologies such as grid computing, distributed computing, parallel computing, utility computing, network storage technologies, virtualization, and load balancing.

[0029] With the development of the Internet, real-time data streams, and the diversification of connected devices, as well as the demand for search services, social networks, mobile commerce, and open collaboration, cloud computing has developed rapidly. Different from the previous parallel distributed computing, the emergence of cloud computing will promote revolutionary changes in the entire Internet model and enterprise management model from a conceptual perspective.

[0030] In an embodiment of the present application, the control system can use cloud computing technology to create, update, delete, etc. the configuration of network devices.

[0031] The following is a description of the technical problems to be solved by the embodiments of the present application, the inventive concept and the network system architecture:

[0032] As described above, the current control system may include a core layer node and multiple access layer nodes. The core layer node is oriented to multiple services, and each access layer node is located at the edge of the network. It is oriented to one or a small number of services, and each access layer node can communicate with network devices within a certain area. How to perform configuration processing based on the current control system architecture is a technical problem to be solved in this application.

[0033] In order to solve the above technical problems, the embodiment of the present application proposes that when creating, updating or deleting a configuration, the core layer node mainly regards the final state model used to describe the final state configuration or the update model used to update the final state model as a black box, that is, the final state model or the update model is not parsed, but the intermediate final state model or the update model is sent to the access layer node, and the access layer node parses the intermediate final state model or the update model, and generates corresponding configuration instructions based on the parsing results, so as to send the configuration instructions to the corresponding network device, and finally realize the configuration creation, update or deletion of the network device.

[0034] For example, Figure 1An application scenario diagram provided for an embodiment of the present application.

[0035] like Figure 1 As shown, the control system 100 includes: a core layer node 110 and multiple access layer nodes 120, wherein the core layer node 110 and each access layer node 120 can be directly or indirectly connected via wired or wireless communication, which is not limited in this application. Each access layer node 120 can be directly or indirectly connected to at least one network device 130 via wired or wireless communication.

[0036] The core layer nodes 110 are usually deployed centrally, that is, deployed on the network center side, and are responsible for the management of the entire life cycle of the final state model, including: storage, deletion, migration, replay, etc. of the final state model. For example, after creating a configuration for the network device based on the final state model, the core layer node 110 can store the final state model; after the core layer node 110 obtains the updated final state model, it can store the updated final state model; after the final state configuration of the final state model is successfully deleted, the core layer node 110 can delete the final state model; after the main network device fails, the core layer node 110 can migrate the final state model corresponding to the main network device to the backup network device; when a certain network device fails but enters a normal state after restarting, the core layer node 110 can resend the final state model corresponding to the network device.

[0037] The core layer node 110 can also manage each access layer node 120, for example, detecting the heartbeat of each access layer node 120, adding, deleting or updating the access layer node, etc. The core layer node 110 can also manage each network device 130, for example, detecting the heartbeat of each access layer node 120, adding, deleting or updating the access layer node, etc.

[0038] It should be understood that the core layer node 110 can be connected to various types of services, for example, it can be connected to backbone network service types, access network service types, etc.

[0039] It is worth mentioning that in the embodiment of the present application, the core layer node 110 does not parse the final state configuration described by the final state model, but it can parse the model identification, type, version information, etc. carried by the final state model. The core layer node 110 also does not parse the content information carried by the update model, but it can parse the model identification, type, version information, etc. carried by the update model.

[0040] The access layer node 120 is usually deployed at the edge of the network, close to the network device side. The access layer node 120 can communicate with the core layer node 110 and the network device 130. It has the ability to parse the final state model and update the model, and generate corresponding configuration instructions based on the parsing results, such as creating configuration instructions, updating configuration instructions, and deleting configuration instructions. Among them, when generating configuration instructions, the access layer node 120 can adapt the device protocol, including: the communication protocol between it and the network device 130, the network configuration management protocol, etc. For example, the communication protocol can be a remote procedure call (RPC) protocol, a transmission control protocol / Internet protocol (TCP / IP), a hypertext transfer protocol (HTTP), a transport layer security protocol (TLS), etc. The network configuration management protocol can be a GRPC network management interface (GNMI), a network configuration (NETCONF) protocol, a simple network management protocol (SNMP), a REST configuration (RESTCONF) protocol, etc. In other words, the access layer node 120 can shield the protocol differences of the underlying network equipment end.

[0041] After generating the configuration instruction corresponding to the network device 130 , the access layer node 120 may send the configuration instruction to the corresponding network device 130 .

[0042] In short, if Figure 2 As shown, the core layer node may include, but is not limited to: a model management module, an access layer node management module, a network device management module, and a database, wherein the model management module is responsible for the management of the overall life cycle of the final state model, including: storage, deletion, migration, and replay of the final state model. The access layer node management module is responsible for managing the access layer nodes. The network device management module is responsible for managing network devices. The database is mainly used to store the final state model.

[0043] Each access layer node may include, but is not limited to: a model parsing module, a model update module, a configuration instruction delivery module, and a device protocol adaptation module. The model parsing module is used to parse the final state configuration described by the final state model. The model update module is used to update the final state model based on the updated model. The device protocol adaptation module is used to adapt to the device protocol when generating configuration instructions. The configuration instruction delivery module is used to deliver its corresponding configuration instructions to the network device.

[0044] In some implementations, for each network device, its device type corresponds to a device protocol, and the network device can receive a configuration instruction of an access layer node after the device protocol is adapted.

[0045] In the embodiment of the present application, the control system may also be referred to as a controller. Since it adopts cloud technology, the control system may also be referred to as a cloud control system or a cloud controller, etc. The embodiment of the present application does not impose any restrictions on this.

[0046] In the embodiment of the present application, the core layer node and the access layer node can be understood as software modules or functional modules, but is not limited to this.

[0047] It should be understood that Figure 1 and Figure 2 The application scenario shown takes two access layer nodes and four network devices as an example. In fact, other numbers of access layer nodes may be included, and each access layer node may be connected to at least one network device.

[0048] The technical solution of this application will be described in detail below:

[0049] Figure 3 An interactive flow chart of a configuration processing method provided in an embodiment of the present application, the method can be executed by a control system, the control system comprising: a core layer node and multiple access layer nodes, such as Figure 3 As shown, the method includes:

[0050] S310: The core layer node determines a target network device for which the configuration created this time is effective, and determines a target access layer node corresponding to the target network device;

[0051] It should be understood that Figure 3 The configuration processing method provided by the corresponding method embodiment is specifically a configuration creation method, which is used to create a configuration for a target network device. Based on this, the network device on which the created configuration takes effect is the target network device.

[0052] In some implementations, the number of the target network devices may be one or more.

[0053] In some implementations, the core layer node receives a create configuration request sent by a model orchestration trigger, and the create configuration request may include at least one of the following, but is not limited to: a target final state model, a create operation type, and an IDentity (ID) of a target network device. Further, the core layer node may determine the target network device based on the ID of the target network device.

[0054] It should be understood that the model arrangement trigger may be a software module for arranging the final state model, which may arrange the final state model into serialized binary information according to certain arrangement rules.

[0055] In some implementations, the core layer node may provide a Hypertext Transfer Protocol (HTTP) / Remote Procedure Call (RPC) interface to the outside, and the model orchestration trigger may call the interface to initiate the creation configuration request.

[0056] It should be understood that the target final state model is used to describe the target final state configuration, wherein the target final state configuration refers to the final state configuration to be created for the target network device, and the target final state model is the final state model used to describe the target final state configuration.

[0057] In some implementations, any final state model may include at least one of the following, but is not limited thereto:

[0058] (1) The unique identifier of the final state model;

[0059] From the code perspective, a final state model is a model instance, and the unique identifier is a globally unique identifier of the model instance, which is used to distinguish the model instance from other model instances.

[0060] In some implementations, a model instance corresponds to one or more configurations. For example, a configuration corresponding to a model instance may be a virtual routing forwarding (VRF) configuration. For example, a configuration corresponding to a model instance may include: a tunnel group configuration and a configuration of a tunnel in the tunnel group.

[0061] (2) Version information of the final state model;

[0062] The version information is used to distinguish different version information of the same type of final state models.

[0063] For example, the final state model A of version 1.0 and the final state model A of version 2.0, both have version information.

[0064] In some implementations, the version information of the final model may be used for model verification later.

[0065] For example, the access layer node may compare whether the version information of the final state model is consistent with the version information of the update model. If they are consistent, the final state model is allowed to be updated through the update model. If they are inconsistent, the final state model is not allowed to be updated through the update model.

[0066] For another example, the access layer node can compare the version information of the final state model it supports with the version information of the final state model received from the core layer node. If they are consistent, the access layer node can continue to parse the final state configuration described by the final state model. If they are inconsistent, the access layer node cannot continue to parse the final state configuration described by the final state model.

[0067] (3) Type information of the final state model;

[0068] The type information is used to distinguish different model types.

[0069] For example, the final state model used to describe the VRF configuration is a final state model of the VRF configuration type, and the final state model used to describe the routing configuration is a final state model of the routing configuration type.

[0070] (4) Content information of the final state model, that is, the final state configuration described by the final state model.

[0071] It should be understood that the final state configuration refers to the configuration of the final state, that is, for a certain configuration, there is only one configuration of the final state, and there is no configuration generated by any intermediate process. For example, in some cases, the control system can save each configuration created for the first time, and when the configuration is updated, it can also save the updated configuration, etc., but in the embodiment of the present application, the control system only saves the configuration of the final state, for example, in this example, the control system can only save the updated configuration.

[0072] In some implementations, the final configuration may be any of the following, but is not limited thereto: VRF configuration, routing configuration, IP configuration, and interface configuration.

[0073] In some implementations, the final configuration may include at least one item of content information, wherein each item of content information may include: a content ID and specific content.

[0074] For example, for a certain routing configuration, it includes:

[0075] Content 1: Source IP address;

[0076] Content 2: destination IP address;

[0077] Content 3: Next hop IP address.

[0078] The routing configuration includes three items of content information. The identifiers of the three items of content information are: 1, 2 and 3. The specific contents of the three items of content information are: source IP address, destination IP address, and next hop IP address.

[0079] It should be understood that for final state models with the same type and different identifiers, they can be used to describe the same or different final state configurations. For example, the final state models used to describe two routing configurations are of the same type but different identifiers, and the two routing configurations are different. For another example, the final state models used to describe two routing configurations are of the same type but different identifiers, but the two routing configurations are the same, and the two routing configurations will be configured to the master network device and the network device.

[0080] (5) Extended content of the final state model.

[0081] For example, the extended content may be the device type associated with the final state model.

[0082] In some implementations, the core layer node may maintain a correspondence between a target network device and a target access layer node, and determine the target access layer node based on the correspondence and the target network device.

[0083] In some possible implementations, other electronic devices besides the control system may maintain a correspondence between a target network device and a target access layer node, determine the target access layer node based on the correspondence and the target network device, and indicate to the core layer node that the access layer node corresponding to the target network device is the target access layer node.

[0084] It should be understood that the target access layer node refers to the access layer node to which the target network device is connected, and the embodiment of the present application does not limit how to determine the target access layer node.

[0085] S320: The core layer node sends a create configuration request to the target access layer node;

[0086] The creation configuration request includes: target final state model, creation operation type and target network device information.

[0087] It should be understood that the create configuration request may be the same as or different from the create configuration request received by the core layer node from the model orchestration trigger. For example, when the information of the target network device carried by the create configuration request in S320 is the ID of the target network device, the create configuration request in S320 is the same as the create configuration request received by the core layer node from the model orchestration trigger. When the information of the target network device carried by the create configuration request in S320 includes more than just the ID of the target network device, the create configuration request in S320 is different from the create configuration request received by the core layer node from the model orchestration trigger.

[0088] In some implementations, the information of the target network device includes at least one of the following, but is not limited thereto: an ID, an IP address, a port number, and a communication address of the target network device.

[0089] In some implementations, the core layer node can maintain a correspondence between the ID of the target network device and at least one of the IP, port number, and communication address of the target network device, and determine at least one of the IP, port number, and communication address of the target network device based on the correspondence and the ID of the target network device.

[0090] It should be understood that after the core layer node obtains the target final state model from the model orchestration trigger, it does not parse the target final state model, but transparently transmits it to the target access layer node.

[0091] S330: The target access layer node parses the create configuration request to obtain the target final state model, the create operation type and the information of the target network device; and parses the target final state model to obtain the target final state configuration; and generates a create configuration instruction based on the target final state configuration, the create operation type and the information of the target network device;

[0092] It should be understood that if the model orchestration trigger orchestrates the target final state model into serialized binary information according to certain orchestration rules, the target access layer node can deserialize and parse the obtained target final state model to obtain the target final state configuration.

[0093] In some possible implementations, the information of the target network device includes: the type of the target network device; accordingly, the target access layer node can determine the device protocol adopted by the target network device based on the type of the target network device; the target access layer node generates a creation configuration instruction based on the target final state configuration, the creation operation type and the device protocol adopted by the target network device.

[0094] In other possible implementations, the information of the target network device includes: the type of the target network device and at least one of the following information of the target network device: communication address, IP, port number; accordingly, the target access layer node can determine the device protocol adopted by the target network device based on the type of the target network device and at least one of the above information; the target access layer node generates a creation configuration instruction based on the target final state configuration, the creation operation type and the device protocol adopted by the target network device.

[0095] It should be understood that the difference between these two possible implementations is that: in the first possible implementation, the type of the target network device has a corresponding relationship with the device protocol adopted by the target network device, and the target access layer node determines the device protocol adopted by the target network device based on the corresponding relationship and the type of the target network device. In the second possible implementation, the type of the target network device and the at least one item of information mentioned above are combined to have a corresponding relationship with the device protocol adopted by the target network device, and the target access layer node determines the device protocol adopted by the target network device based on the corresponding relationship, the type of the target network device and the at least one item of information mentioned above.

[0096] In the embodiment of the present application, the target access layer node may generate a creation configuration instruction in any of the following achievable ways, but is not limited thereto:

[0097] In some possible implementations, the target access layer node generates an instruction template corresponding to the creation configuration instruction based on the creation operation type and the device protocol adopted by the target network device; writes various information of the target final state configuration into the corresponding position of the instruction template to obtain the creation configuration instruction.

[0098] Among them, the target access layer node determines that the first field of the instruction template corresponding to the creation configuration instruction is creat based on the creation operation type, and based on the device protocol adopted by the target network device, it can be determined what contents need to be written in other fields except the first field in the instruction template, and the length of each field can be determined. Based on this, the various information of the target final state configuration is written into the corresponding position of the instruction template to obtain the creation configuration instruction.

[0099] For example, if you want to create a routing configuration, the first field can be written as creat, which is 1 bit long, the second field can be written as the source IP address, which is 8 bits long, the third field can be written as the destination IP address, which is 8 bits long, and the fourth field can be written as the next hop IP address, which is 8 bits long.

[0100] In some other possible implementations, the target access layer node searches for a creation configuration instruction corresponding to the target final configuration, the creation operation type, and the information of the target network device.

[0101] In other words, in this implementable manner, there is a correspondence between the combined information of the target final state configuration, the creation operation type and the target network device information and the creation configuration instruction, and the target access layer node can determine the creation configuration instruction based on the correspondence.

[0102] It should be understood that the number of target final state configurations is one or more, and each target final state configuration may correspond to a create configuration instruction. For example, if the target final state configuration is a VRF configuration, then it corresponds to a create configuration instruction for instructing the creation of the VRF configuration, wherein the instruction may carry the VRF configuration. If the target final state configuration includes: a tunnel group configuration and a tunnel configuration in the tunnel group configuration, then it corresponds to two create configuration instructions, respectively for instructing the creation of a tunnel group configuration and the creation of a tunnel configuration, wherein the two instructions may carry the tunnel group configuration and the tunnel configuration, respectively.

[0103] S340: The target access layer node sends a creation configuration instruction to the target network device;

[0104] The creation configuration instruction is used for the target network device to create a target final configuration. The creation of the target final configuration by the target network device can also be referred to as the validation of the target final configuration by the target network device.

[0105] In some implementations, after the target network device determines that the target final configuration is successfully effective, it may send a effectiveness success response to the target access layer node.

[0106] It should be understood that if there are multiple target final state configurations mentioned above, the target access layer node can issue corresponding creation configuration instructions for each target final state configuration. Correspondingly, for each target final state configuration, when the target network device determines that the target final state configuration has successfully taken effect, it can send a successful effectiveness response to the target access layer node.

[0107] For example, when the target final state configuration includes: a tunnel group configuration and a tunnel configuration in the tunnel group configuration, then for each of the two target final state configurations, after the target network device determines that the target final state configuration has successfully taken effect, it can send a successful effectivity response to the target access layer node.

[0108] In some possible implementations, if all target final state configurations are created successfully, the target access layer node indicates to the core layer node that all target final state configurations are created successfully; if part or all of the target final state configurations fail to be created, the target access layer node indicates to the core layer node that part or all of the target final state configurations fail to be created.

[0109] In some implementations, if part or all of the target final state configuration fails to be created, the target access layer node reports the target final state configuration that failed to be created to the core layer node.

[0110] For example, when the target final state configuration includes: a tunnel group configuration and a configuration of a tunnel 11 in the tunnel group configuration, assuming that a creation failure occurs when creating the configuration of the tunnel 11, based on this, the target access layer node can report the failure of tunnel 11 creation to the core layer node.

[0111] In some implementations, if all target final state configurations are created successfully, the core layer node stores the target final state model. In other words, if all target final state configurations are created successfully, the core layer node can persistently store the target final state model.

[0112] In some possible implementations, if all target final state configurations are created successfully, the core layer node indicates to the model orchestration trigger that all target final state configurations are created successfully; if part or all of the target final state configurations fail to be created, the core layer node indicates to the model orchestration trigger that part or all of the target final state configurations fail to be created.

[0113] In some possible implementations, if part or all of the target final state configuration fails to be created, the core layer node reports the target final state configuration that failed to be created to the model orchestration trigger.

[0114] The embodiment of the present application provides a configuration processing method, including: the core layer node determines the target network device for which the configuration creation is effective, and determines the target access layer node corresponding to the target network device; the core layer node sends a creation configuration request to the target access layer node; the target access layer node parses the creation configuration request to obtain the target final state model, the creation operation type and the information of the target network device; and parses the target final state model to obtain the target final state configuration; and based on the target final state configuration, the creation operation type and the information of the target network device, generates a creation configuration instruction; the target access layer node issues a creation configuration instruction to the target network device so that the target network device creates the target final state configuration. Among them, the core layer node is usually oriented to multiple businesses. Regardless of the business, the core layer node regards the target final state model as a black box, that is, the target final state model is not parsed. Based on this, from the perspective of software development, for any business, the software code of the core layer node does not need to be changed, thereby improving the reusability of the core layer node, and improving the reusability of the software product (i.e., the core layer node in the embodiment of the present application) has important significance and value, which is mainly reflected in the following aspects:

[0115] (1) Improve development efficiency: By reusing existing software products, the workload of repetitive development can be reduced and the productivity of developers can be improved.

[0116] (2) Reduce maintenance costs: Software products with high reusability require fewer parts to be modified during maintenance, thereby reducing maintenance costs. At the same time, software products with high reusability are often more stable and reliable after repeated use and verification, thereby reducing potential failures and problems.

[0117] (3) Improve software quality: Software products with high reusability have often undergone rigorous testing and verification and have higher stability and reliability.

[0118] (4) Promote modularity and standardization: Modular and standardized components help improve the flexibility and scalability of software.

[0119] (5) Improve resource utilization: By reusing existing software products, you can avoid duplicate development and waste of resources, and improve overall resource utilization.

[0120] Since the target access layer node needs to parse the target final state model, from the perspective of software development, it is only necessary to add a new access layer node (that is, the target access layer node here) to the control system, or update the access layer node and use the updated access layer node as the target access layer node. The access layer node is usually oriented to one or a small number of businesses, and the software development difficulty of adding or updating the access layer node is relatively small.

[0121] Figure 4 The interactive flow chart of another configuration processing method provided in an embodiment of the present application, the method can be executed by a control system, the control system includes: a core layer node and multiple access layer nodes, such as Figure 4 As shown, the method includes:

[0122] S410: The core layer node determines a target network device for which the updated configuration is effective, and determines a target access layer node corresponding to the target network device;

[0123] It should be understood that Figure 4 The configuration processing method provided by the corresponding method embodiment is specifically a configuration update method, which is used to update the final configuration of the target network device, and specifically can update at least one content in the final configuration. Based on this, the network device on which this updated configuration takes effect is the target network device.

[0124] In some implementations, the number of the target network devices may be one or more.

[0125] In some implementations, the core layer node receives an update configuration request sent by the model orchestration trigger, and the update configuration request may include at least one of the following, but is not limited to: a target update model, an update operation type, and an ID of a target network device. Further, the core layer node may determine the target network device based on the ID of the target network device.

[0126] It should be understood that the explanation of model arrangement triggers can be found in Figure 3 The corresponding embodiments are not described in detail in this embodiment.

[0127] In some implementations, the core layer node may provide an HTTP / RPC interface to the outside, and the model orchestration trigger may call the interface to initiate the configuration update request.

[0128] It should be understood that the target update model is used to update the target final state configuration to be updated in the target final state configuration described by the target final state model; specifically, at least one item in the final state configuration to be updated can be updated. For example, assuming that the final state configuration to be updated is a routing configuration, then based on the target update model, at least one of the source IP address, destination IP address and next-hop IP address in the routing configuration can be updated.

[0129] It should be understood that the explanation of the target end state model and the target end state configuration can be referred to Figure 3 The corresponding embodiments are not described in detail in this embodiment.

[0130] In some implementations, for any update model, it may include at least one of the following, but is not limited to:

[0131] (1) A unique identifier for the updated model;

[0132] From a code perspective, an update model is a model instance, and the unique identifier is a globally unique identifier of the model instance, which is used to distinguish the model instance from other model instances.

[0133] (2) The unique identifier of the associated final state model;

[0134] It should be understood that the so-called associated final state model refers to the final state model to be updated by the update model. For example, the target update model mentioned above is the update model associated with the target final state model.

[0135] It should be understood that the explanation of the unique identifier of the final state model can be referred to Figure 3 The corresponding embodiments are not described in detail in this embodiment.

[0136] (3) Version information of the updated model;

[0137] The version information is used to distinguish different version information of the same type of update model.

[0138] For example, the update model A of version 1.0 and the update model A of version 2.0, both have version information.

[0139] In some implementations, the version information of the updated model may be subsequently used for model verification.

[0140] For example, the access layer node may compare whether the version information of the final state model is consistent with the version information of the update model. If they are consistent, the final state model is allowed to be updated through the update model. If they are inconsistent, the final state model is not allowed to be updated through the update model.

[0141] For another example, the access layer node can compare the version information of the update model it supports with the version information of the update model received from the core layer node. If they are consistent, the access layer node can continue to parse the update model. If they are inconsistent, the access layer node cannot continue to parse the update model.

[0142] (4) Type information of the update model;

[0143] The type information is used to distinguish different model types.

[0144] (5) Type information of the associated final state model;

[0145] It should be understood that the explanation of the type information of the final state model can be referred to Figure 3 The corresponding embodiments are not described in detail in this embodiment.

[0146] (6) content information of the updated model;

[0147] The content information of the update model is used to describe the operation of the update model on the specific content in the final configuration to be updated, as well as the content before and / or after the operation, and specifically consists of three parts:

[0148] 1. Operations on specific contents in the configuration to be updated: add, delete or modify;

[0149] 2. The ID of the specific content in the configuration to be updated;

[0150] 3. Content before and / or after the operation;

[0151] The ID of the specific content and the content before and / or after the operation may be collectively referred to as updated content.

[0152] For example, if a destination IP address needs to be added to a routing configuration, the updated content is content ID_1 and the newly added destination IP address.

[0153] For another example, assuming that for a routing configuration, the original destination IP address needs to be updated, then the update content includes: content ID_1, the original destination IP address, and the updated destination IP address.

[0154] For another example, assuming that for a routing configuration, the destination IP address needs to be deleted, then the update content may be content ID_2.

[0155] (7) Extended content of the updated model.

[0156] For example, the extension content may be to update the device type associated with the model.

[0157] It should be understood that the version information of the update model should be consistent with the version information of the associated final state model, and the type information of the update model should be consistent with the type information of the associated final state model.

[0158] It should be understood that the type information of the associated final state model and the unique identifier of the associated final state model can uniquely determine the final state model to be updated by the update model. The content information of the update model is used to describe the operation of the update model on the specific content in the final state configuration to be updated, as well as the content before and / or after the operation. After the access layer node obtains the content information, it can update the associated final state model.

[0159] It should be understood that the final state model defined in the embodiments of the present application is used to describe the final state configuration. The final state model has a complete life cycle, including: creation, update and deletion. It should be understood that the so-called creation of the final state model refers to the creation of the final state configuration described by the final state model, the so-called updating of the final state model refers to updating the final state configuration described by the final state model, and the so-called deletion of the final state model refers to deleting the final state configuration described by the final state model. Among them, the final state model is persisted by the core layer nodes and is used for configuration management, migration, query, replay, etc. The update model is used to update the final state model, and it will not be persisted by the core layer nodes, but it still has a complete life cycle, namely, including: creation, update and deletion.

[0160] Combine the following Figure 5 An example of updating the final state model based on the updated model is given below:

[0161] Figure 5 An example schematic diagram of an updated final state model provided in an embodiment of the present application is as follows: Figure 5 As shown, for the final state model 1 before updating, its unique identifier is identifier 1, the version information is version 1, the type information is type 1, the content information includes: content ID_1: content 1 and content ID_2: content 2, and the final state model 1 has no extended content.

[0162] For update model 2, its unique identifier is 2, the unique identifier of the associated final state model is identifier 1, the version information is version 1, the type information of update model 2 is type 1, the type information of the associated final state model is type 1, and the content information of the update model includes: <Modification, content ID_1, content 11>, <Delete, content ID_2>, <Add, content ID_3, content 3>, and the update model 2 has no extended content.

[0163] The final state model 1 is updated based on the update model 2 to obtain an updated final state model 1, whose unique identifier is identifier 1, version information is version 1, type information is type 1, content information includes: content ID_1: content 11 and content ID_3: content 3, and the updated final state model 1 has no extended content.

[0164] It should be understood that how to determine the target access layer node can refer to Figure 3 The corresponding embodiments are not described in detail in this embodiment.

[0165] S420: The core layer node sends a configuration update request to the target access layer node;

[0166] The update configuration request includes: target update model, update operation type and target network device information.

[0167] It should be understood that the update configuration request may be the same as or different from the update configuration request received by the core layer node from the model orchestration trigger. For example, when the information of the target network device carried by the update configuration request in S420 is the ID of the target network device, the update configuration request in S420 is the same as the update configuration request received by the core layer node from the model orchestration trigger. When the information of the target network device carried by the update configuration request in S420 includes more than just the ID of the target network device, the update configuration request in S420 is different from the update configuration request received by the core layer node from the model orchestration trigger.

[0168] It should be understood that the explanation of the information about the target network device can refer to Figure 3 The corresponding embodiments are not described in detail in this embodiment.

[0169] It should be understood that after the core layer node obtains the target update model from the model orchestration trigger, it does not parse the target update model, but transparently transmits it to the target access layer node.

[0170] In some implementations, the core layer node can search the target final state model from the database according to the unique identifier of the target final state model carried by the target update model. Based on this, the core layer node can carry the searched target final state model in the update configuration request so that the subsequent target access layer node can detect whether the target update model is legal for the target final state model.

[0171] S430: The target access layer node parses the update configuration request to obtain the target update model, the update operation type and the target network device information; and parses the target update model to obtain the content information carried by the target update model; and generates an update configuration instruction based on the content information, the update operation type and the target network device information;

[0172] It should be understood that if the model orchestration trigger orchestrates the target update model into serialized binary information according to certain orchestration rules, the target access layer node can deserialize and parse the obtained target update model to obtain the content information carried by the target update model.

[0173] In some implementable embodiments, the update configuration request also includes: a target final state model; based on this, the configuration processing method also includes: the target access layer node parses the update configuration request to obtain the target final state model; the target access layer node parses the target final state model to obtain the type of the target final state model; and parses the target update model to obtain the type of the target update model; the target access layer node detects whether the target update model is legal for the target final state model based on the type of the target final state model, the type of the target update model, the operations included in the content information, and the operation restrictions corresponding to the content information; if the target update model is legal for the target final state model, then based on the content information, the update operation type and the information of the target network device, an update configuration instruction is generated.

[0174] It should be understood that if the model orchestration trigger orchestrates the target final state model into serialized binary information according to certain orchestration rules, the target access layer node can deserialize and parse the obtained target final state model to obtain the type of the target final state model.

[0175] It should be understood that the operations included in the content information may be addition, deletion or modification. The operation restriction conditions corresponding to the content information are, for example, that content 1 can only be modified but not deleted, and content 2 can only be added and deleted but not modified.

[0176] In some possible implementations, if the type of the target final state model is consistent with the type of the target update model, and the operation corresponding to the content information satisfies the operation restriction conditions, the target access layer node determines that the target update model is legal for the target final state model; if the type of the target final state model is inconsistent with the type of the target update model, or the operation included in the content information does not satisfy the operation restriction conditions, the target access layer node determines that the target update model is illegal for the target final state model.

[0177] For example, assuming that the type of the target final state model is type 1 and the type of the target update model is type 2, since the two are inconsistent, the target access layer node determines that the target update model is illegal for the target final state model.

[0178] For another example, assume that the content information carried in the target update model includes: <modification, content ID_1, content 11>, but content ID_1 is only allowed to be added or deleted, not modified. Based on this, the target access layer node determines that the target update model is illegal for the target final state model.

[0179] For another example, assume that the types of the target final state model and the target update model are both type 1, and the content information carried in the target update model includes: <modification, content ID_1, content 11>, content ID_1 is allowed to be modified, based on this, the target access layer node determines that the target update model is legal for the target final state model.

[0180] In some implementable embodiments, the target access layer node detects whether the target update model is legal for the target final state model based on the type and version information of the target final state model, the type and version information of the target update model, the operations included in the content information, and the operation restrictions corresponding to the content information; if the target update model is legal for the target final state model, an update configuration instruction is generated based on the content information, the update operation type, and the information of the target network device.

[0181] In some implementable embodiments, if the type of the target final state model is consistent with the type of the target update model, and the version information of the target final state model is consistent with the version information of the target update model, and the operation corresponding to the content information satisfies the operation restriction conditions, then the target access layer node determines that the target update model is legal for the target final state model; if the type of the target final state model is inconsistent with the type of the target update model, or the version information of the target final state model is inconsistent with the version information of the target update model, or the operation included in the content information does not satisfy the operation restriction conditions, then the target access layer node determines that the target update model is illegal for the target final state model.

[0182] For example, assuming that the version information of the target final state model is version 1 and the version of the target update model is version information 2, since the two are inconsistent, the target access layer node determines that the target update model is illegal for the target final state model.

[0183] For another example, assume that the types of the target final state model and the target update model are both type 1, and the version information of the target final state model and the target update model are both version 1, and the content information carried in the target update model includes: <Modification, content ID_1, content 11>, content ID_1 is allowed to be modified, based on this, the target access layer node determines that the target update model is legal for the target final state model.

[0184] In some possible implementations, the information of the target network device includes: the type of the target network device; accordingly, the target access layer node determines the device protocol adopted by the target network device based on the type of the target network device; the target access layer node generates an update configuration instruction based on the content information of the update model, the update operation type and the device protocol adopted by the target network device.

[0185] In other possible implementations, the information of the target network device includes: the type of the target network device and at least one of the following information of the target network device: communication address, IP, port number; accordingly, the target access layer node can determine the device protocol adopted by the target network device based on the type of the target network device and at least one of the above information; the target access layer node generates an update configuration instruction based on the content information of the update model, the update operation type and the device protocol adopted by the target network device.

[0186] It should be understood that the difference between these two possible implementations is that: in the first possible implementation, the type of the target network device has a corresponding relationship with the device protocol adopted by the target network device, and the target access layer node determines the device protocol adopted by the target network device based on the corresponding relationship and the type of the target network device. In the second possible implementation, the type of the target network device and the at least one item of information mentioned above are combined to have a corresponding relationship with the device protocol adopted by the target network device, and the target access layer node determines the device protocol adopted by the target network device based on the corresponding relationship, the type of the target network device and the at least one item of information mentioned above.

[0187] In the embodiment of the present application, the target access layer node may generate an update configuration instruction in any of the following achievable ways, but is not limited thereto:

[0188] In some possible implementations, the target access layer node generates an instruction template corresponding to the update configuration instruction based on the update operation type, the device protocol adopted by the target network device, and the operation included in the content information; writes the update content included in the content information into the corresponding position of the instruction template to obtain the update configuration instruction.

[0189] Among them, the target access layer node determines the operation field of the instruction template corresponding to the update configuration instruction based on the update operation type and the operation included in the content information, such as add, delete or amend. Based on the device protocol adopted by the target network device, it can be determined what contents need to be written into other fields in the instruction template except the operation field, and the length of each field can be determined. Based on this, the update content included in the content information is written into the corresponding position of the instruction template to obtain the update configuration instruction.

[0190] For example, if you want to add a routing configuration, the operation field can be add, which is 1 bit long. After the operation field, the source IP address, destination IP address, and next hop IP address can be written in sequence. The length of these three fields is 8 bits respectively.

[0191] For another example, if a routing configuration is to be modified, the operation field may be amend, which is 1 bit long. After the operation field, the source IP address before modification and the source IP address after modification may be written in sequence. The lengths of these two fields are 8 bits respectively.

[0192] For another example, if you want to delete a routing configuration, the operation field can be delete, which is 1 bit long. After the operation field, you can write content ID_1 corresponding to the source IP address, content ID_2 corresponding to the destination IP address, and content ID_3 corresponding to the next hop IP address. The length of these three fields is 2 bits respectively.

[0193] It should be understood that, since the content information may include multiple update contents, such as: content corresponding to the add operation, content corresponding to the modify operation, in this case, the target access layer node may generate an update configuration instruction. In which, each operation field in the instruction is followed by the update content corresponding to the operation field, for example, the source IP address, the destination IP address and the next hop IP address may be followed after the operation field add, and the source IP address before modification and the source IP address after modification may be followed after the operation field amend.

[0194] In other possible implementations, the target access layer node searches for content information of the update model, the update operation type, and the device protocol used by the target network device in conjunction with the corresponding update configuration instructions.

[0195] In other words, in this implementable manner, there is a correspondence between the content information of the update model, the update operation type, the joint information of the device protocol adopted by the target network device and the update configuration instruction, and the target access layer node can determine the update configuration instruction based on the correspondence.

[0196] It should be understood that the number of final state configurations to be updated is one or more; wherein each final state configuration to be updated corresponds to an update configuration instruction. For example, if the final state configuration to be updated is a VRF configuration, then it corresponds to an update configuration instruction for indicating the update of the VRF configuration, wherein the instruction may carry the updated VRF configuration. If the final state configuration to be updated includes: a tunnel group configuration and a tunnel configuration in the tunnel group configuration, then it corresponds to two update configuration instructions, respectively used to indicate the update of the tunnel group configuration and the update of the tunnel configuration, wherein the two instructions may carry the updated tunnel group configuration and the updated tunnel configuration, respectively.

[0197] S440: The target access layer node sends an update configuration instruction to the target network device;

[0198] The update configuration instruction is used by the target network device to update the final state configuration to be updated. The target network device updating the final state configuration to be updated can also be referred to as the target network device updating the final state configuration to be updated to take effect.

[0199] In some implementations, after the target network device has updated the final configuration to be updated, it may send an update success response to the target access layer node.

[0200] It should be understood that if there are multiple final state configurations to be updated, the target access layer node can issue corresponding update configuration instructions for each final state configuration to be updated. Correspondingly, for each final state configuration to be updated, when the target network device determines that the final state configuration to be updated has been updated, it can send an update success response to the target access layer node.

[0201] For example, when the final state configuration to be updated includes: a tunnel group configuration and a tunnel configuration in the tunnel group configuration, then for each of the two final state configurations to be updated, when the target network device determines that the final state configuration to be updated is updated successfully, it can send an update success response to the target access layer node.

[0202] In some possible implementations, if all final state configurations to be updated are updated successfully, the target access layer node indicates to the core layer node that all final state configurations to be updated are updated successfully; if some or all final state configurations to be updated fail to be updated, the target access layer node indicates to the core layer node that some or all final state configurations to be updated fail to be updated.

[0203] In some possible implementations, if part or all of the final-state configurations to be updated fail to be updated, the target access layer node reports the final-state configurations to be updated that failed to be updated to the core layer node.

[0204] For example, when the final configuration to be updated includes: a tunnel group configuration and a configuration of a tunnel 11 in the tunnel group configuration, assuming that an update failure occurs when updating the configuration of the tunnel 11, based on this, the target access layer node can report the tunnel 11 update failure to the core layer node.

[0205] In some achievable embodiments, if all the final state configurations to be updated are successfully updated, the target access layer node updates the final state configurations to be updated of the target final state model based on the target update model, and reports the updated target final state model to the core layer node; the core layer node updates the stored target final state model to the updated target final state model. In other words, if all the target final state configurations are successfully updated, the core layer node can persistently store the target final state model and delete the original target final state model.

[0206] In some possible implementations, if all final-state configurations to be updated are updated successfully, the core layer node indicates to the model orchestration trigger that all final-state configurations to be updated are updated successfully; if some or all final-state configurations to be updated fail to be updated, the core layer node indicates to the model orchestration trigger that some or all final-state configurations to be updated fail to be updated.

[0207] In some possible implementations, if part or all of the final-state configurations to be updated fail to be updated, the core layer node reports the final-state configurations to be updated that failed to be updated to the model orchestration trigger.

[0208] The embodiment of the present application provides a configuration processing method, including: the core layer node determines the target network device for which the updated configuration is effective, and determines the target access layer node corresponding to the target network device; the core layer node sends an update configuration request to the target access layer node; the target access layer node parses the update configuration request to obtain the target update model, the update operation type and the target network device information; and parses the target update model to obtain the content information carried by the target update model; and based on the content information, the update operation type and the information of the target network device, generates an update configuration instruction; the target access layer node sends the update configuration instruction to the target network device so that the target network device updates the final configuration to be updated. Among them, the core layer node is usually oriented to multiple businesses. Regardless of the business, the core layer node regards the target update model as a black box, that is, the target update model is not parsed. Based on this, from the perspective of software development, for any business, the software code of the core layer node does not need to be changed, thereby improving the reusability of the core layer node, and improving the reusability of the software product (i.e., the core layer node in the embodiment of the present application) has important significance and value. The explanation of this significance and value can be referred to Figure 3 The corresponding method embodiment will not be described in detail in this embodiment.

[0209] Since the target access layer node needs to parse the target update model, or parse the target update model and the target final state model, from the perspective of software development, it is only necessary to add a new access layer node (that is, the target access layer node here) to the control system, or update the access layer node and use the updated access layer node as the target access layer node. The access layer node is usually oriented to one or a small number of businesses, and the software development difficulty of adding or updating the access layer node is relatively small.

[0210] In addition, the embodiments of the present application can more clearly store and update the final state configuration in the control system by separating the target final state model and the target update model. Specifically, the core layer nodes can persistently store the target final state model, and the target final state model carries the target final state configuration. That is to say, the core layer nodes can persistently store the target final state configuration, and the access layer nodes can update the target final state model based on the target update model, thereby reducing the complexity of configuration management.

[0211] Figure 6 The interactive flow chart of another configuration processing method provided in the embodiment of the present application, the method can be executed by a control system, the control system includes: a core layer node and multiple access layer nodes, such as Figure 6 As shown, the method includes:

[0212] S610: The core layer node determines the target network device for which the deletion configuration is effective, and determines the target access layer node corresponding to the target network device;

[0213] It should be understood that Figure 6 The configuration processing method provided by the corresponding method embodiment is specifically a configuration deletion method, which is used to delete the configuration of the target network device. Based on this, the network device on which the configuration deletion takes effect is the target network device.

[0214] In some implementations, the number of the target network devices may be one or more.

[0215] In some implementations, the core layer node receives a deletion configuration request sent by the model orchestration trigger, and the deletion configuration request may include at least one of the following, but is not limited to: a unique identifier of the target end-state model, a deletion operation type, and an ID of the target network device. Further, the core layer node may determine the target network device based on the ID of the target network device, and search the target end-state model from a database based on the unique identifier of the target end-state model.

[0216] It should be understood that the explanation of model arrangement triggers can be found in Figure 3 The corresponding embodiments are not described in detail in this embodiment.

[0217] In some implementations, the core layer node may provide an HTTP / RPC interface to the outside, and the model orchestration trigger may call the interface to initiate the configuration deletion request.

[0218] It should be understood that the explanation of the target end state model and the target end state configuration can be referred to Figure 3 The corresponding embodiments are not described in detail in this embodiment.

[0219] It should be understood that the method for determining the target access layer node can refer to Figure 3 The corresponding embodiments are not described in detail in this embodiment.

[0220] S620: The core layer node sends a configuration deletion request to the target access layer node;

[0221] The configuration deletion request includes: target final state model, deletion operation type and target network device information.

[0222] It should be understood that the deletion configuration request may be the same as or different from the deletion configuration request received by the core layer node from the model orchestration trigger. For example, when the information of the target network device carried by the deletion configuration request in S620 is the ID of the target network device, the deletion configuration request in S620 is the same as the deletion configuration request received by the core layer node from the model orchestration trigger. When the information of the target network device carried by the deletion configuration request in S620 includes more than just the ID of the target network device, the deletion configuration request in S620 is different from the deletion configuration request received by the core layer node from the model orchestration trigger.

[0223] It should be understood that the explanation of the information about the target network device can refer to Figure 3 The corresponding method embodiments are not described in detail in this embodiment.

[0224] It should be understood that after the core layer node finds the target final state model, it does not parse the target final state model, but transparently transmits it to the target access layer node.

[0225] S630: The target access layer node parses the configuration deletion request to obtain the target final state model, the deletion operation type, and the information of the target network device; and parses the target final state model to obtain the target final state configuration; and generates a configuration deletion instruction based on the target final state configuration, the deletion operation type, and the information of the target network device;

[0226] It should be understood that if the model orchestration trigger orchestrates the target final state model into serialized binary information according to certain orchestration rules, the target access layer node can deserialize and parse the obtained target final state model to obtain the target final state configuration.

[0227] In some possible implementations, the information of the target network device includes: the type of the target network device; the target access layer node can determine the device protocol adopted by the target network device based on the type of the target network device; the target access layer node generates a deletion configuration instruction based on the target final state configuration, the deletion operation type and the device protocol adopted by the target network device.

[0228] In other possible implementations, the information of the target network device includes: the type of the target network device and at least one of the following information of the target network device: communication address, IP, port number; accordingly, the target access layer node can determine the device protocol adopted by the target network device based on the type of the target network device and at least one of the above information; the target access layer node generates a deletion configuration instruction based on the target final state configuration, the deletion operation type and the device protocol adopted by the target network device.

[0229] It should be understood that the difference between these two possible implementations is that: in the first possible implementation, the type of the target network device has a corresponding relationship with the device protocol adopted by the target network device, and the target access layer node determines the device protocol adopted by the target network device based on the corresponding relationship and the type of the target network device. In the second possible implementation, the type of the target network device and the at least one item of information mentioned above are combined to have a corresponding relationship with the device protocol adopted by the target network device, and the target access layer node determines the device protocol adopted by the target network device based on the corresponding relationship, the type of the target network device and the at least one item of information mentioned above.

[0230] In the embodiment of the present application, the target access layer node may generate a deletion configuration instruction in any of the following achievable ways, but is not limited thereto:

[0231] In some possible implementations, the target access layer node generates an instruction template corresponding to the deletion configuration instruction based on the deletion operation type and the device protocol adopted by the target network device; writes various information of the target final state configuration into the corresponding position of the instruction template to obtain the deletion configuration instruction.

[0232] Among them, the target access layer node determines that the first field of the instruction template corresponding to the deletion configuration instruction is delete based on the deletion operation type. Based on the device protocol adopted by the target network device, it can be determined what contents need to be written into other fields in the instruction template except the first field, and the length of each field can be determined. Based on this, the various information of the target final state configuration is written into the corresponding position of the instruction template to obtain the deletion configuration instruction.

[0233] For example, if you want to delete a routing configuration, the first field can be written as delete, which is 1 bit long, the second field can be written as the source IP address, which is 8 bits long, the third field can be written as the destination IP address, which is 8 bits long, and the fourth field can be written as the next hop IP address, which is 8 bits long.

[0234] In other possible implementations, the target access layer node searches for a deletion configuration instruction corresponding to the target final configuration, the deletion operation type, and the device protocol used by the target network device.

[0235] In other words, in this implementable manner, there is a correspondence between the target final state configuration, the deletion operation type, the joint information of the device protocol adopted by the target network device and the deletion configuration instruction, and the target access layer node can determine the deletion configuration instruction based on the correspondence.

[0236] It should be understood that the number of target final state configurations is one or more, and each target final state configuration may correspond to a delete configuration instruction. For example, if the target final state configuration is a VRF configuration, then it corresponds to a delete configuration instruction for instructing to delete the VRF configuration, wherein the instruction may carry the VRF configuration. If the target final state configuration includes: a tunnel group configuration and a tunnel configuration in the tunnel group configuration, then it corresponds to two delete configuration instructions, respectively for instructing to delete the tunnel group configuration and to delete the tunnel configuration, wherein the two instructions may carry the tunnel group configuration and the tunnel configuration, respectively.

[0237] S640: The target access layer node sends a deletion configuration instruction to the target network device;

[0238] The configuration deletion instruction is used by the target network device to delete the target final configuration.

[0239] The target network device deleting the target final-state configuration may also be referred to as the target network device taking effect of the deletion of the target final-state configuration.

[0240] In some implementations, after the target network device determines that the target final configuration is deleted successfully, it may send a deletion success response to the target access layer node.

[0241] It should be understood that if there are multiple target final state configurations mentioned above, the target access layer node can issue a corresponding deletion configuration instruction for each target final state configuration. Correspondingly, for each target final state configuration, when the target network device determines that the target final state configuration is deleted successfully, it can send a deletion success response to the target access layer node.

[0242] For example, when the target final state configuration includes: a tunnel group configuration and a tunnel configuration in the tunnel group configuration, then for each of the two target final state configurations, when the target network device determines that the target final state configuration is successfully deleted, it can send a deletion success response to the target access layer node.

[0243] In some possible implementations, if all target final state configurations are deleted successfully, the target access layer node indicates to the core layer node that all target final state configurations are deleted successfully; if part or all of the target final state configurations fail to be deleted, the target access layer node indicates to the core layer node that part or all of the target final state configurations fail to be deleted.

[0244] In some implementations, if part or all of the target final state configuration fails to be deleted, the target access layer node reports the failed deletion of the target final state configuration to the core layer node, or generates an alarm message, which is used to indicate the failed deletion of the target final state configuration.

[0245] In some possible implementations, if all target final state configurations are deleted successfully, the core layer node deletes the target final state model.

[0246] In some possible implementations, if all target final state configurations are deleted successfully, the core layer node indicates to the model orchestration trigger that all target final state configurations are deleted successfully; if some or all target final state configurations fail to be deleted, the core layer node indicates to the model orchestration trigger that some or all target final state configurations fail to be deleted.

[0247] In some possible implementations, if part or all of the target final state configuration fails to be deleted, the core layer node reports the target final state configuration that failed to be deleted to the model orchestration trigger.

[0248] The embodiment of the present application provides a configuration processing method, including: the core layer node determines the target network device for which the current deletion configuration is effective, and determines the target access layer node corresponding to the target network device; the core layer node sends a deletion configuration request to the target access layer node; the target access layer node parses the deletion configuration request to obtain the target final state model, the deletion operation type and the information of the target network device; and parses the target final state model to obtain the target final state configuration; and based on the target final state configuration, the deletion operation type and the information of the target network device, generates a deletion configuration instruction; the target access layer node sends a deletion configuration instruction to the target network device so that the target network device deletes the target final state configuration. Among them, the core layer node is usually oriented to multiple businesses. Regardless of the business, the core layer node regards the target final state model as a black box, that is, the target final state model is not parsed. Based on this, from the perspective of software development, for any business, the software code of the core layer node does not need to be changed, thereby improving the reusability of the core layer node, and improving the reusability of the software product (i.e., the core layer node in the embodiment of the present application) has important significance and value. The explanation of this significance and value can be referred to Figure 3 The corresponding method embodiment will not be described in detail in this embodiment.

[0249] Since the target access layer node needs to parse the target final state model, from the perspective of software development, it is only necessary to add a new access layer node (that is, the target access layer node here) to the control system, or update the access layer node and use the updated access layer node as the target access layer node. The access layer node is usually oriented to one or a small number of businesses, and the software development difficulty of adding or updating the access layer node is relatively small.

[0250] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all belong to the protection scope of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the ideas of the present application, they should also be regarded as the contents disclosed in the present application.

[0251] It should also be understood that in the various method embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0252] The method provided in the embodiment of the present application is described above, and the control system provided in the embodiment of the present application is described below.

[0253] An embodiment of the present application provides a control system, which includes: a core layer node and multiple access layer nodes, wherein the core layer node is used to: determine the target network device for which the creation configuration is effective, and determine the target access layer node corresponding to the target network device; send a creation configuration request to the target access layer node; wherein the creation configuration request includes: a target final state model, a creation operation type and information about the target network device; the target final state model is used to describe the target final state configuration; the target access layer node is used to: parse the creation configuration request to obtain the target final state model, the creation operation type and information about the target network device; and parse the target final state model to obtain the target final state configuration; and based on the target final state configuration, the creation operation type and information about the target network device, generate a creation configuration instruction; and issue the creation configuration instruction to the target network device; wherein the creation configuration instruction is used for the target network device to create the target final state configuration.

[0254] In some possible implementations, the information of the target network device includes: the type of the target network device; the target access layer node is specifically used to: determine the device protocol adopted by the target network device based on the type of the target network device; generate a creation configuration instruction based on the target final state configuration, the creation operation type and the device protocol adopted by the target network device.

[0255] In some possible implementations, the target access layer node is specifically used to: generate an instruction template corresponding to a creation configuration instruction based on the creation operation type and the device protocol adopted by the target network device; write various information of the target final state configuration into the corresponding position of the instruction template to obtain a creation configuration instruction.

[0256] In some possible implementations, the number of target final state configurations is one or more; the target access layer node is also used to: if all target final state configurations are successfully created, indicate to the core layer node that all target final state configurations are successfully created; if some or all of the target final state configurations fail to be created, indicate to the core layer node that some or all of the target final state configurations fail to be created; and report the failed target final state configurations to the core layer node.

[0257] In some implementations, the core layer node is further configured to: if all target final state configurations are created successfully, store the target final state model.

[0258] An embodiment of the present application also provides another control system, which includes: a core layer node and multiple access layer nodes, wherein the core layer node is used to: determine the target network device for which the current update configuration is effective, and determine the target access layer node corresponding to the target network device; send an update configuration request to the target access layer node; wherein the update configuration request includes: a target update model, an update operation type and information about the target network device; the target update model is used to update the target final state configuration to be updated in the target final state configuration described by the target final state model; parse the update configuration request to obtain the target update model, the update operation type and information about the target network device; and parse the target update model to obtain content information carried by the target update model; and generate an update configuration instruction based on the content information, the update operation type and information about the target network device; the target access layer node is used to: send an update configuration instruction to the target network device; wherein the update configuration instruction is used for the target network device to update the final state configuration to be updated.

[0259] In some implementable embodiments, the update configuration request also includes: a target final state model; the target access layer node is also used to: parse the update configuration request to obtain the target final state model; parse the target final state model to obtain the type of the target final state model; and parse the target update model to obtain the type of the target update model; based on the type of the target final state model, the type of the target update model, the operations included in the content information, and the operation restrictions corresponding to the content information, detect whether the target update model is legal for the target final state model; accordingly, the target access layer node is specifically used to: if the target update model is legal for the target final state model, then based on the content information, the update operation type and the information of the target network device, generate an update configuration instruction.

[0260] In some implementable embodiments, the target access layer node is specifically used to: if the type of the target final state model is consistent with the type of the target update model, and the operation corresponding to the content information satisfies the operation restriction conditions, then determine that the target update model is legal for the target final state model; if the type of the target final state model is inconsistent with the type of the target update model, or the operation included in the content information does not satisfy the operation restriction conditions, then determine that the target update model is illegal for the target final state model.

[0261] In some possible implementations, the information of the target network device includes: the type of the target network device; the target access layer node is specifically used to: determine the device protocol adopted by the target network device based on the type of the target network device; and generate an update configuration instruction based on the content information, the update operation type and the device protocol adopted by the target network device.

[0262] In some possible implementations, the target access layer node is specifically used to: generate an instruction template corresponding to the update configuration instruction based on the update operation type, the device protocol adopted by the target network device, and the operation included in the content information; write the update content included in the content information into the corresponding position of the instruction template to obtain the update configuration instruction.

[0263] In some possible implementations, the number of final-state configurations to be updated is one or more; the target access layer node is also used to: if all the final-state configurations to be updated are updated successfully, indicate to the core layer node that all the final-state configurations to be updated are updated successfully; if some or all of the final-state configurations to be updated fail to be updated, indicate to the core layer node that some or all of the final-state configurations to be updated fail to be updated; and report the final-state configurations to be updated that have failed to be updated to the core layer node.

[0264] In some possible implementations, the target access layer node is also used to: if all the final state configurations to be updated are successfully updated, then update the final state configurations to be updated of the target final state model based on the target update model, and report the updated target final state model to the core layer node; the core layer node is also used to: update the target final state model stored therein to the updated target final state model.

[0265] An embodiment of the present application also provides another control system, which includes: a core layer node and multiple access layer nodes, wherein the core layer node is used to: determine the target network device for which the current deletion configuration is effective, and determine the target access layer node corresponding to the target network device; send a deletion configuration request to the target access layer node; wherein the deletion configuration request includes: a target final state model, a deletion operation type and information about the target network device; the target final state model is used to describe the target final state configuration; the target access layer node is used to: parse the deletion configuration request to obtain the target final state model, the deletion operation type and information about the target network device; and parse the target final state model to obtain the target final state configuration; and based on the target final state configuration, the deletion operation type and information about the target network device, generate a deletion configuration instruction; and issue the deletion configuration instruction to the target network device; wherein the deletion configuration instruction is used for the target network device to delete the target final state configuration.

[0266] In some possible implementations, the information of the target network device includes: the type of the target network device; the target access layer node is specifically used to: the target access layer node determines the device protocol adopted by the target network device based on the type of the target network device; the target access layer node generates a deletion configuration instruction based on the target final state configuration, the deletion operation type and the device protocol adopted by the target network device.

[0267] In some possible implementations, the target access layer node is specifically used to: generate an instruction template corresponding to the deletion configuration instruction based on the deletion operation type and the device protocol adopted by the target network device; write various information of the target final state configuration into the corresponding position of the instruction template to obtain the deletion configuration instruction.

[0268] In some possible implementations, the number of target final state configurations is one or more; the target access layer node is also used to: if all target final state configurations are deleted successfully, indicate to the core layer node that all target final state configurations are deleted successfully; if some or all of the target final state configurations fail to be deleted, indicate to the core layer node that some or all of the target final state configurations fail to be deleted; and report the target final state configurations that failed to be deleted to the core layer node.

[0269] In some possible implementations, the core layer node is further configured to: if all final state configurations to be updated are deleted successfully, the core layer node deletes the target final state model.

[0270] It should be understood that the system embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, no further description is given here. Specifically, the control system provided in the embodiment of the present application can execute the above method embodiment, and the aforementioned and other operations and / or functions of each module in the control system are respectively for implementing the corresponding processes in the above methods, and for the sake of brevity, no further description is given here.

[0271] The control system of the embodiment of the present application is described above from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or a combination of hardware and software modules in the decoding processor to perform. Optionally, the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps in the above method embodiment in conjunction with its hardware.

[0272] Figure 7 It is a schematic block diagram of an electronic device provided in an embodiment of the present application.

[0273] like Figure 7 As shown, the electronic device may include:

[0274] The memory 710 and the processor 720, the memory 710 is used to store the computer program and transmit the program code to the processor 720. In other words, the processor 720 can call and run the computer program from the memory 710 to implement the method in the embodiment of the present application.

[0275] For example, the processor 720 may be configured to execute the above method embodiments according to instructions in the computer program.

[0276] In some embodiments of the present application, the processor 720 may include but is not limited to:

[0277] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

[0278] In some embodiments of the present application, the memory 710 includes but is not limited to:

[0279] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0280] In some embodiments of the present application, the computer program may be divided into one or more modules, which are stored in the memory 710 and executed by the processor 720 to complete the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0281] like Figure 7 As shown, the electronic device may also include:

[0282] The transceiver 730 may be connected to the processor 720 or the memory 710 .

[0283] The processor 720 may control the transceiver 730 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 730 may include a transmitter and a receiver. The transceiver 730 may further include an antenna, and the number of antennas may be one or more.

[0284] It should be understood that the various components in the electronic device are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0285] The present application also provides a computer storage medium on which a computer program is stored, and when the computer program is executed by a computer, the computer can perform the method of the above method embodiment. In other words, the present application embodiment also provides a computer program product containing instructions, and when the instructions are executed by a computer, the computer can perform the method of the above method embodiment.

[0286] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integration. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid state drive (solid state disk, SSD)), etc.

[0287] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0288] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the module is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0289] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. For example, each functional module in each embodiment of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0290] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A configuration processing method, characterized in that: The method is applied to a control system, the control system comprising: a core layer node and a plurality of access layer nodes, the method comprising: The core layer node determines the target network device for which the configuration created this time is effective, and determines the target access layer node corresponding to the target network device; The core layer node sends a create configuration request to the target access layer node; wherein the create configuration request includes: a target final state model, a create operation type and information of the target network device; the target final state model is used to describe the target final state configuration; The target access layer node parses the create configuration request to obtain the target final state model, the create operation type and the information of the target network device; and parses the target final state model to obtain the target final state configuration; and generates a create configuration instruction based on the target final state configuration, the create operation type and the information of the target network device; The target access layer node sends the creation configuration instruction to the target network device; wherein the creation configuration instruction is used by the target network device to create the target final state configuration.

2. The method according to claim 1, characterized in that: The information of the target network device includes: the type of the target network device; and the generating of the creation configuration instruction based on the target final configuration, the creation operation type and the information of the target network device includes: The target access layer node determines the device protocol adopted by the target network device based on the type of the target network device; The target access layer node generates the creation configuration instruction based on the target final state configuration, the creation operation type, and the device protocol adopted by the target network device.

3. The method according to claim 2, characterized in that The target access layer node generates the creation configuration instruction based on the target final state configuration, the creation operation type, and the device protocol adopted by the target network device, including: The target access layer node generates an instruction template corresponding to the creation configuration instruction based on the creation operation type and the device protocol adopted by the target network device; The target access layer node writes various information of the target final state configuration into the corresponding position of the instruction template to obtain the creation configuration instruction.

4. The method according to any one of claims 1 to 3, characterized in that: The number of the target final state configurations is one or more; and the method further comprises: If all the target final state configurations are created successfully, the target access layer node indicates to the core layer node that all the target final state configurations are created successfully; If part or all of the target final state configuration fails to be created, the target access layer node indicates to the core layer node that part or all of the target final state configuration fails to be created; and reports the failed creation of the target final state configuration to the core layer node.

5. The method according to claim 4, characterized in that Also includes: If all the target final state configurations are created successfully, the core layer node stores the target final state model.

6. A configuration processing method, characterized in that: The method is applied to a control system, the control system comprising: a core layer node and a plurality of access layer nodes, the method comprising: The core layer node determines the target network device for which the updated configuration is effective, and determines the target access layer node corresponding to the target network device; The core layer node sends a configuration update request to the target access layer node; wherein the configuration update request includes: a target update model, an update operation type, and information of the target network device; the target update model is used to update the target final state configuration to be updated in the target final state configuration described by the target final state model; The target access layer node parses the update configuration request to obtain the target update model, the update operation type and the target network device information; and parses the target update model to obtain the content information carried by the target update model; and generates an update configuration instruction based on the content information, the update operation type and the target network device information; The target access layer node sends the update configuration instruction to the target network device; wherein the update configuration instruction is used by the target network device to update the final configuration to be updated.

7. The method according to claim 6, characterized in that The update configuration request further includes: the target final state model; the method further includes: The target access layer node parses the configuration update request to obtain the target final state model; The target access layer node parses the target final state model to obtain the type of the target final state model; and parses the target update model to obtain the type of the target update model; The target access layer node detects whether the target update model is legal for the target final state model based on the type of the target final state model, the type of the target update model, the operations included in the content information, and the operation restriction conditions corresponding to the content information; The generating an update configuration instruction based on the content information, the update operation type and the information of the target network device includes: If the target update model is legal for the target final state model, an update configuration instruction is generated based on the content information, the update operation type and the information of the target network device.

8. The method according to claim 7, characterized in that The target access layer node detects whether the target update model is legal for the target final state model based on the type of the target final state model, the type of the target update model, the operations included in the content information, and the operation restriction conditions corresponding to the content information, including: If the type of the target final state model is consistent with the type of the target update model, and the operation corresponding to the content information satisfies the operation restriction condition, the target access layer node determines that the target update model is legal for the target final state model; If the type of the target final state model is inconsistent with the type of the target update model, or the operation included in the content information does not satisfy the operation restriction condition, the target access layer node determines that the target update model is illegal for the target final state model.

9. The method according to any one of claims 6 to 8, characterized in that: The information of the target network device includes: the type of the target network device; and the generating of the update configuration instruction based on the content information, the update operation type and the information of the target network device includes: The target access layer node determines the device protocol adopted by the target network device based on the type of the target network device; The target access layer node generates the update configuration instruction based on the content information, the update operation type and the device protocol adopted by the target network device.

10. The method according to claim 9, characterized in that The target access layer node generates the update configuration instruction based on the content information, the update operation type, and the device protocol adopted by the target network device, including: The target access layer node generates an instruction template corresponding to the update configuration instruction based on the update operation type, the device protocol adopted by the target network device, and the operation included in the content information; The target access layer node writes the updated content included in the content information into the corresponding position of the instruction template to obtain the updated configuration instruction.

11. The method according to any one of claims 6 to 8, characterized in that: The number of the final state configurations to be updated is one or more; and the method further includes: If all the final configurations to be updated are updated successfully, the target access layer node indicates to the core layer node that all the final configurations to be updated are updated successfully; If part or all of the final state configurations to be updated fail to be updated, the target access layer node indicates to the core layer node that part or all of the final state configurations to be updated fail to be updated; and reports the final state configurations to be updated that failed to be updated to the core layer node.

12. The method according to claim 11, characterized in that Also includes: If all the final state configurations to be updated are updated successfully, the target access layer node updates the final state configurations to be updated of the target final state model based on the target update model, and reports the updated target final state model to the core layer node; The core layer node updates the stored target final state model to the updated target final state model.

13. An electronic device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 12.

14. A computer-readable storage medium, characterized in that: Used to store a computer program, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 12.

Images