Wide area network configuration method and device and readable storage medium
By using a visual topology system and a cross-vendor configuration translation engine, the problems of insufficient compatibility and low flexibility in wide area network configuration methods have been solved, making it easier and more flexible for network personnel in small and medium-sized enterprises.
Patent Information
- Application Number
- CN202511139065.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-14
- Publication Date
- 2025-11-18
AI Technical Summary
Existing wide area network configuration methods suffer from insufficient compatibility, low configuration flexibility, and difficulty in adapting to the skill level of network personnel in small and medium-sized enterprises.
The system allows users to drag and drop to build network topology structures, receive basic configuration information, and generate target configuration information using a cross-vendor configuration translation engine, supporting compatible configurations for devices from multiple vendors.
It enables network personnel in small and medium-sized enterprises to easily complete the construction and basic configuration of wide area network topology, improving compatibility and flexibility, and reducing the difficulty of operation.
Smart Images

Figure CN120979945A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of network technology, and in particular to a wide area network configuration method, apparatus, and readable storage medium. Background Technology
[0002] Modern enterprises rely heavily on networks for production and office work. The increasing complexity of networks, particularly with cloud applications and branch office networking, is a significant challenge. However, network administrators in small and medium-sized enterprises (SMEs) often lack sufficient network expertise and in-depth understanding of network functionality. This leads to numerous difficulties when building new networks or adding nodes and functionalities to existing ones. They are unfamiliar with commands, and the fragmented logic of the original manufacturer's web-based user interface (Web-based User Interface) makes it difficult to integrate with specific needs for appropriate configuration. Furthermore, existing wide area network (WAN) configuration methods have significant drawbacks: for example, controllers based on Zero-Touch Provisioning (ZTP) only support devices from a single manufacturer, resulting in severe incompatibility; simultaneously, SME networks cannot achieve functionality through scenario-based configuration, requiring network personnel to have a deep understanding of various device functions to complete configurations, leading to extremely low configuration flexibility. Summary of the Invention
[0003] The technical problem to be solved by the present invention is to address the above-mentioned shortcomings of the prior art by providing a wide area network configuration method, apparatus and readable storage medium, so as to solve the problems of insufficient compatibility, low configuration flexibility and difficulty in adapting to the level of network personnel in small and medium-sized enterprises in the existing wide area network configuration methods.
[0004] In a first aspect, the present invention provides a wide area network configuration method, the method comprising:
[0005] Receive wide area network topology structures constructed by users through a visual topology system using drag-and-drop functionality;
[0006] Receive basic configuration information filled in by the user for the network devices in the topology;
[0007] Based on the basic configuration information filled in, the simulation data is configured according to the preset operating system command format of the manufacturer, and the simulation network effect is simulated.
[0008] In response to the user's confirmation that the simulated network effect is consistent with expectations, the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology are obtained.
[0009] If the access network element device involves multiple manufacturers or models, based on the manufacturer and model of each access network element device, the basic configuration information of each access network element device is translated using a cross-manufacturer configuration translation engine to generate the corresponding target configuration information;
[0010] The target configuration information is then sent to the corresponding access network element devices.
[0011] Furthermore, the visual topology system has pre-defined typical network architecture and topology configuration sub-modules. The process of receiving the wide area network topology structure constructed by the user through drag-and-drop via the visual topology system specifically includes:
[0012] Receive wide area network topology structures constructed by users through dragging and dropping typical network architectures in the visual topology system; or,
[0013] It receives WAN topologies that users can customize and build by dragging and dropping the topology configuration submodule in the visual topology system.
[0014] Furthermore, the method also includes:
[0015] In response to the user's confirmation that the simulated network effect is inconsistent with expectations, a correction operation is performed on the topology and / or basic configuration information based on the feedback discrepancy information.
[0016] Furthermore, before translating the basic configuration information of each access network element device based on its manufacturer brand and model, and generating the corresponding target configuration information using a cross-manufacturer configuration translation engine, the method further includes:
[0017] Define command-line interface (CLI) configuration templates for different network equipment manufacturers using YAML, the next-generation data modeling language YANG, or JavaScript object representation JSON;
[0018] A cross-vendor configuration translation engine is built based on CLI configuration templates from different network equipment manufacturers.
[0019] Furthermore, the method also includes:
[0020] Abstract the network devices in the topology or actual network topology as graph nodes, and abstract the logical or physical connections between network devices as edge nodes. Attach attributes to each graph node and edge node to obtain the corresponding graph model.
[0021] Conflict detection is performed based on the graph model, and the conflict detection includes at least one of the following: detecting whether the Virtual Local Area Network Identifier (VLAN ID) is duplicated, and detecting whether the Internet Protocol (IP) addresses overlap.
[0022] Furthermore, the method also includes:
[0023] Receive the business objectives declared by the user through the Network Intent Description Language (NIDL);
[0024] The business objectives are translated using a translation engine configured by a different vendor, generating corresponding business objective translation instructions;
[0025] The translated instructions for the business objectives are then sent to the corresponding network devices in the actual network topology.
[0026] Furthermore, the basic configuration information includes Quality of Service (QoS) policy information, and after sending the target configuration information to the corresponding access network element device, the method further includes:
[0027] Collect network metric data from actual network topologies;
[0028] TS2Vec uses time-series vectorization to extract, encode, and label features from collected network metric data;
[0029] The labeled network metric data is used as sample data, and a prototype vector is constructed using a small number of samples less than a preset threshold.
[0030] Based on the similarity inference between the real-time data vector and the prototype vector, dynamic adjustments to the QoS policy are generated and executed.
[0031] In a second aspect, the present invention provides a wide area network configuration device, the device comprising:
[0032] The topology acquisition module is used to receive the wide area network topology structure that the user constructs by dragging and dropping through the visual topology system;
[0033] The basic configuration acquisition module is connected to the topology acquisition module and is used to receive basic configuration information filled in by the user for the network devices in the topology.
[0034] The simulation configuration module is connected to the basic configuration acquisition module. It is used to configure simulation data according to the basic configuration information filled in, according to the preset manufacturer's operating system command format, and to simulate network effects.
[0035] The brand and model acquisition module is connected to the simulation configuration module and is used to acquire the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology in response to the user's confirmation operation that the simulation network effect is consistent with expectations.
[0036] A cross-manufacturer configuration translation module is connected to the brand and model acquisition module. If the access network element device involves multiple manufacturers' brands or models, the cross-manufacturer configuration translation engine is used to translate the basic configuration information of each access network element device based on the manufacturer's brand and model of each access network element device, and generate the corresponding target configuration information.
[0037] The configuration information distribution module is connected to the cross-vendor configuration translation module and is used to distribute the target configuration information to the corresponding access network element device.
[0038] Thirdly, the present invention provides a wide area network configuration apparatus, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the wide area network configuration method described in the first aspect above.
[0039] Fourthly, the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the wide area network configuration method described in the first aspect.
[0040] This invention provides a wide area network (WAN) configuration method, apparatus, and readable storage medium. First, it receives a WAN topology structure constructed by a user through a drag-and-drop visual topology system; then, it receives basic configuration information filled in by the user for the network devices in the topology structure; next, based on the filled-in basic configuration information, it performs simulation data configuration according to a preset manufacturer's operating system command format and simulates the network effect; then, in response to the user's confirmation that the simulated network effect is consistent with expectations, it obtains the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology structure; if the access network element devices involve multiple manufacturer brands or models, based on the manufacturer brand and model of each access network element device, it uses a cross-manufacturer configuration translation engine to translate the basic configuration information of each access network element device to generate corresponding target configuration information. This invention enables network administrators in small and medium-sized enterprises (SMEs) to easily construct and configure wide area network (WAN) topologies through drag-and-drop operations and basic configuration information input in a visual topology system, significantly reducing operational difficulty. Simultaneously, it allows for configuration of simulated data and network effects according to preset vendor operating system command formats, validating the configuration's rationality before actual deployment. Furthermore, by utilizing a cross-vendor configuration translation engine, it translates the basic configuration information of access network elements from multiple vendors and models, generating target configuration information. This achieves seamless adaptation between devices from different vendors and supports flexible switching from single-vendor networking to multi-vendor expansion scenarios, comprehensively improving the compatibility, flexibility, and ease of use of WAN configuration. It solves the problems of insufficient compatibility, low configuration flexibility, and difficulty in adapting to the skill levels of network administrators in SMEs found in existing WAN configuration methods. Attached Figure Description
[0041] Figure 1 This is a flowchart of a wide area network configuration method according to Embodiment 1 of the present invention;
[0042] Figure 2 This is an architecture diagram of the wide area network configuration method according to an embodiment of the present invention;
[0043] Figure 3 This is a network architecture diagram of a two-layer circuit wide-area headquarters-branch office network according to an embodiment of the present invention;
[0044] Figure 4 This is a network architecture diagram of a three-layer MPLS VPN FULL Mesh network according to an embodiment of the present invention;
[0045] Figure 5 This is a network architecture diagram of a three-layer MPLS VPN Hub & Spokes networking according to an embodiment of the present invention;
[0046] Figure 6 This is a schematic diagram illustrating the automated implementation path for wide area network configuration in an embodiment of the present invention.
[0047] Figure 7 This is a schematic diagram of network device connections and attributes based on a graph model, according to an embodiment of the present invention.
[0048] Figure 8 This is a system architecture diagram of QoS dynamic optimization based on few-shot learning according to an embodiment of the present invention;
[0049] Figure 9 This is a schematic diagram of a wide area network configuration device according to Embodiment 2 of the present invention;
[0050] Figure 10 This is a schematic diagram of a wide area network configuration device according to Embodiment 3 of the present invention. Detailed Implementation
[0051] To enable those skilled in the art to better understand the technical solution of the present invention, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.
[0052] It is understood that the specific embodiments and accompanying drawings described herein are merely for explaining the invention and are not intended to limit the invention.
[0053] It is understood that, without conflict, the various embodiments and features in the embodiments of the present invention can be combined with each other.
[0054] It is understood that, for ease of description, only the parts related to the present invention are shown in the accompanying drawings, while the parts unrelated to the present invention are not shown in the drawings.
[0055] It is understood that each unit or module involved in the embodiments of the present invention may correspond to only one entity structure, or may be composed of multiple entity structures, or multiple units or modules may be integrated into one entity structure.
[0056] It is understood that the terms "first," "second," etc., in the embodiments of the present invention are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.
[0057] It is understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of this invention may occur in a different order than that marked in the accompanying drawings.
[0058] It is understood that the flowcharts and block diagrams of this invention illustrate the possible architecture, functions, and operations of systems, apparatuses, devices, and methods according to various embodiments of this invention. Each block in the flowchart or block diagram may represent a unit, module, program segment, or code, containing executable instructions for implementing the specified function. Furthermore, each block or combination of blocks in the block diagram and flowchart can be implemented using a hardware-based system to achieve the specified function, or using a combination of hardware and computer instructions.
[0059] It is understood that the units and modules involved in the embodiments of the present invention can be implemented by software or by hardware. For example, the units and modules can be located in a processor.
[0060] Example 1:
[0061] This embodiment provides a wide area network configuration method, such as... Figure 1 As shown, the method includes:
[0062] Step S101: Receive the wide area network topology structure constructed by the user through the visual topology system by dragging and dropping.
[0063] In this embodiment, the visual topology system uses React+Ant Design or Vue.js+Element UI to build an enterprise-grade lightweight visual interface, supporting component-based development and enabling rapid iteration. Tools such as React DnD / Vue Draggable are used to implement drag-and-drop network topology modules and canvas layout, allowing users to build wide area network topologies simply by dragging and dropping.
[0064] Optionally, the visual topology system has a pre-defined typical network architecture and topology configuration sub-module. The process of receiving the wide area network topology structure constructed by the user through drag-and-drop via the visual topology system specifically includes:
[0065] Receive wide area network topology structures constructed by users through dragging and dropping typical network architectures in the visual topology system; or,
[0066] It receives WAN topologies that users can customize and build by dragging and dropping the topology configuration submodule in the visual topology system.
[0067] In this embodiment, the visual topology system was designed and developed with typical network architectures and topology configuration sub-modules pre-built in. Users do not need to build from scratch and can directly use or make secondary adjustments based on these pre-set contents. Typical network architectures include Layer 2 circuit-switched WAN and Layer 3 MPLS VPN (Multi-Protocol Label Switching Virtual Private Network) networking. The topology configuration sub-modules include network basic modules, security policy modules, and service deployment modules. Users can customize the WAN topology by dragging and dropping the corresponding modules onto the canvas.
[0068] Step S102: Receive basic configuration information filled in by the user for the network devices in the topology.
[0069] In this embodiment, the basic configuration information filled in by the user is usually required, including the selection of access port type for each device line, allocation of VLAN (Virtual Local Area Network) information, configuration of interconnection IP (Internet Protocol) addresses (or automatically planned by the system), routing protocol, business IP address ranges of headquarters and branches, etc. If there are advanced requirements such as QoS (Quality of Service), they can be planned and filled in in the extended requirements attribute.
[0070] Step S103: Based on the basic configuration information filled in, configure the simulation data according to the preset manufacturer's operating system command format, and simulate the network effect.
[0071] In this embodiment, based on the basic configuration information filled in, the simulation data is configured according to the preset operating system command format of the manufacturer (such as Huawei), and the network effect is simulated. The simulation terminal can be used to check whether it matches the expectation (i.e., the ideal networking effect of the customer).
[0072] Step S104: In response to the user's confirmation that the simulated network effect is consistent with expectations, obtain the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology structure.
[0073] In this embodiment, the access network element devices are CE (Customer Edge) devices. Upon initial power-on, each access network element device completes two-way authentication with the cloud control center using a pre-installed device fingerprint certificate (e.g., a key in the TPM chip). After successful authentication, the cloud control center collects the manufacturer brand and model of each access network element device in the actual network topology. If it receives confirmation from the user that the simulated network effect is consistent with expectations, it obtains the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology.
[0074] Optionally, the method further includes:
[0075] In response to the user's confirmation that the simulated network effect is inconsistent with expectations, a correction operation is performed on the topology and / or basic configuration information based on the feedback discrepancy information.
[0076] In this embodiment, if the simulated network effect is inconsistent with expectations, the user provides feedback on the discrepancy, and the system makes corrections.
[0077] Step S105: If the access network element device involves multiple manufacturers or models, based on the manufacturer and model of each access network element device, the basic configuration information of each access network element device is translated using a cross-manufacturer configuration translation engine to generate the corresponding target configuration information.
[0078] In this embodiment, the network devices may come from a single manufacturer or multiple manufacturers. If the access network elements involve different manufacturers' brands or models, a cross-manufacturer configuration translation engine is used to convert the commands. This cross-manufacturer configuration translation engine is used to convert basic configuration information for a preset manufacturer into a command format (dedicated configuration commands) that can be recognized by the target manufacturer's devices, thereby achieving cross-manufacturer compatible configuration.
[0079] Step S106: Send the target configuration information to the corresponding access network element device.
[0080] In this embodiment, the target configuration information is sent to the corresponding access network element device so that it takes effect on the device side.
[0081] Optionally, before translating the basic configuration information of each access network element device based on its manufacturer brand and model, and generating the corresponding target configuration information using a cross-manufacturer configuration translation engine, the method further includes:
[0082] Define CLI (Command Line Interface) configuration templates for different network equipment vendors using YAML (YAML Ain't Markup Language), YANG (Yet Another Next Generation), or JSON (JavaScript Object Notation).
[0083] A cross-vendor configuration translation engine is built based on CLI configuration templates from different network equipment manufacturers.
[0084] In this embodiment, vendor CLI templates are defined using YAML / YANG / JSON, configurations are dynamically rendered, and multi-vendor instruction conversion logic is handled.
[0085] Optionally, the method further includes:
[0086] Abstract the network devices in the topology or actual network topology as graph nodes, and abstract the logical or physical connections between network devices as edge nodes. Attach attributes to each graph node and edge node to obtain the corresponding graph model.
[0087] Conflict detection is performed based on the graph model, and the conflict detection includes at least one of the following: detecting whether VLAN IDs (Virtual Local Area Network Identifiers) are duplicated, and detecting whether Internet Protocol (IP) addresses overlap.
[0088] In this embodiment, the steps for detecting duplicate VLAN IDs include: 1) Constructing a VLAN propagation graph: Traversing the port configurations of all network devices and recording the allowed VLAN IDs for each port. If two device ports are connected via a trunk and allow the same VLAN, a VLAN propagation path is established. 2) Performing conflict detection: Using DFS (Depth-First Search) or BFS (Breadth-First Search), traversing the propagation paths of the same VLAN ID. If the same VLAN ID is found to exist in two broadcast domains that are not directly connected, it is determined to be a VLAN ID conflict.
[0089] In this embodiment, the steps for detecting IP address overlap include: 1) Subnet intervalization: Converting each subnet (Classless Inter-Domain Routing, CIDR) into an integer interval. Example: 10.10.10.0 / 24 → interval [16777216, 16777471] (calculated by converting IP to integer). 2) Interval conflict detection: Using an interval tree or sorting scan method to check if there is any intersection among all subnet intervals. If there is an intersection, it is determined that the IP addresses overlap.
[0090] Optionally, the method further includes:
[0091] Receive the business objectives declared by the user through NIDL (Network Intent Description Language);
[0092] The business objectives are translated using a translation engine configured by a different vendor, generating corresponding business objective translation instructions;
[0093] The translated instructions for the business objectives are then sent to the corresponding network devices in the actual network topology.
[0094] In this embodiment, a unified network intent description language (NIDL) is defined. Users only need to declare their business objectives (such as "guarantee video conferencing bandwidth"), and the system will automatically translate them into multi-vendor instructions.
[0095] Optionally, the basic configuration information includes Quality of Service (QoS) policy information, and after sending the target configuration information to the corresponding access network element device, the method further includes:
[0096] Collect network metric data from actual network topologies;
[0097] The collected network metric data is used to perform feature extraction, encoding, and labeling using TS2Vec (Time Series to Vector).
[0098] The labeled network metric data is used as sample data, and a prototype vector is constructed using a small number of samples less than a preset threshold.
[0099] Based on the similarity inference between the real-time data vector and the prototype vector, dynamic adjustments to the QoS policy are generated and executed.
[0100] In this embodiment, the network indicator data includes, but is not limited to, traffic characteristics, network status, and service priorities (key services manually labeled by the user). Traffic characteristics include application type (video / file transfer), bandwidth utilization, burst traffic frequency, etc., while network status includes end-to-end latency (RTT), jitter, packet loss, etc. By collecting network indicator data from the actual network topology, the original data is compressed into a low-dimensional vector using methods such as time series embedding (TS2Vec), and then encoded and labeled. A prototype vector is constructed using a small number of samples (e.g., 5 traffic scenarios). The similarity between new samples and the prototype is calculated. Based on the similarity inference results, QoS optimization strategy information is generated, optimization instructions are generated, and the dynamic adjustment of the QoS strategy is executed.
[0101] It should be noted that the wide area network configuration method provided by this invention is a lightweight solution for rapid network deployment for small and medium-sized enterprises (SMEs). By generating network topology and device configurations through a drag-and-drop interface, it eliminates the reliance of SMEs on professional network engineers, lowering the technical barrier. Simultaneously, it constructs an intelligent translation mechanism for multi-vendor device commands and a cross-vendor command mapping library, dynamically converting common configuration logic into CLI commands for devices such as Cisco, Huawei, and H3C, automatically adapting to differences in proprietary protocols among different vendors. Furthermore, leveraging few-shot learning, optimization strategies can be generated with only a small amount of enterprise network data (such as topology and service type), directly mapping business intent to device configuration, further reducing the technical barrier.
[0102] In one specific embodiment, a wide area network (WAN) configuration method is provided. Based on the user's topology and requirements, a simulation model is established. After the user confirms the simulation results, the service configuration engine distributes data configurations to the network devices, quickly completing the project design, planning, and commissioning. The architecture diagram corresponding to this WAN configuration method is shown below. Figure 2 As shown, the entire architecture is divided into a visual topology system, an intelligent analysis and business translation system, a cloud control center, a cross-vendor configuration translation engine, and a remote secure access gateway, among other components.
[0103] 1) Visual Topology System: Used to provide users with initial network planning and design. Through the topology structure built by this system, information such as user interfaces, IP addresses, and routing protocol planning can be obtained.
[0104] 2) Intelligent Analysis and Business Translation System: Used to convert topological information into structured data.
[0105] 3) Cloud Control Center: Used for remote control and deployment of the results of the intelligent analysis and business transformation system, monitoring and updating network data.
[0106] 4) Cross-vendor configuration translation engine: Used to convert standard data for equipment from different manufacturers to adapt to equipment from other manufacturers.
[0107] The overall process of this wide area network configuration method includes: user design topology → generating configuration requirements → translation engine generating multi-vendor instructions → security gateway issuing → device execution → status transmission back to the cloud.
[0108] The anomaly handling process of this wide area network configuration method includes: device alarm → cloud analysis → triggering automatic repair (such as port isolation) → notifying the user.
[0109] Specifically, the wide area network configuration method may include the following steps:
[0110] S1. Construct the target network topology. Customers construct the network topology according to their actual situation. The visual topology system provides customers with typical topology structures and customization options through drag-and-drop functionality, allowing for quick and intuitive access.
[0111] The visual topology system provides network topology planning, allowing users to construct target network topologies based on models such as headquarters and branch offices, and enabling convenient operation through drag-and-drop functionality. Typical topologies include Layer 2 circuit-switched WAN and Layer 3 MPLS VPN, and user-defined architectures such as dual-center and hybrid networks are also possible.
[0112] Typical network architectures include:
[0113] (1) Two-layer circuit wide area headquarters-branch office networking
[0114] A two-layer circuit wide area network architecture for headquarters-branch office networking is as follows: Figure 3 As shown, point-to-point circuits are opened between headquarters and branch offices to achieve interconnection.
[0115] (2) Layer 3 MPLS VPN Full Mesh Network
[0116] A three-layer MPLS VPN full mesh network architecture is as follows: Figure 4 As shown, the headquarters and branch offices are connected in a flat, interconnected network.
[0117] (3) Three-layer MPLS VPN Hub & Spoke (Center & Branch) Network
[0118] A three-layer MPLS VPN hub & spoke network architecture is as follows: Figure 5 As shown, branch offices can communicate with headquarters, but branch offices cannot communicate directly with each other. If communication is required, it must go through headquarters CE.
[0119] Custom network topologies are built by dragging and dropping network devices, interconnection bandwidth, WAN line types, and the number of lines according to the customer's network plan. For example, a customer has a data center with three branch offices nationwide. One branch uses a carrier's circuit, while the other two use the internet and build their own IPsec VPN tunnels. This would require a custom network topology.
[0120] S2. AI (Artificial Intelligence) Intelligent Analysis. Based on the customer's topology, interconnection IPs, routing protocols, service IP addresses, etc., the system performs intelligent analysis of the network services. The customer confirms whether the results match their expectations. If not, the system makes minor adjustments after receiving feedback.
[0121] (1) Based on the network topology defined in S1, fill in the required fields in the intelligent analysis and service translation system, such as the selection of access port types for each device line, allocation of VLAN information, configuration of interconnection IP addresses (or automatically planned by the system), routing protocols, and business IP address ranges for headquarters and branches. If there are advanced requirements such as QoS, plan and fill them in the extended requirements attribute. The routing protocols support mainstream routing protocols such as static, BGP (Border Gateway Protocol), IS-IS (Intermediate System to Intermediate System), and OSPF (Open Shortest Path First). The system uses the operating system command format of a specific vendor (such as Huawei) to perform simulation data configuration according to the filled-in planning information (i.e., basic configuration information) and simulates the network effect. You can check whether it matches the design plan (i.e., the ideal network effect of the customer) through the simulation terminal. If there is a discrepancy, feedback information will be provided and the system will make corrections. For example, the original plan was a hybrid architecture between the data center and various branch offices, allowing all offices to access the data center, but some offices could access each other, without distinguishing between those that could not. However, the simulation results showed that all branch offices could not access each other. In that case, feedback should be provided on which nodes were planned to be able to access each other, but in reality they could not, and corrections should be made.
[0122] (2) The system generates network topology and IP address allocation table.
[0123] It should be noted that, to improve efficiency, the system defaults to selecting equipment from a single manufacturer. If equipment or models from different manufacturers are involved, a cross-manufacturer configuration translation engine is used for command conversion. For typical enterprise networking, single-manufacturer networking is more common, while multi-manufacturer equipment is generally used when expanding capacity or adding nodes.
[0124] S3. Go-live Preparation. Based on the generated network topology and basic configuration, fill in the manufacturer's brand and model of each access network element device. If multiple manufacturers' platforms are involved, compile according to the IOS (Internetwork Operating System) of different manufacturers' devices, configure accordingly, and distribute to the devices. Go-live preparation requires that the network element devices at each access point can access the cloud system via the Internet through IPsec (Internet Protocol Security).
[0125] Among them, the access network element equipment only includes CE equipment, while PE (Provider Edge) equipment is equipment of service providers such as operators and is not within the scope of enterprise maintenance and management.
[0126] In this process, network node devices register with the cloud control center via 4G / 5G wireless access boxes, configure the interconnection IP access between the local devices and the wireless boxes, and collect the brand and model of each access point device. It should be noted that if the access network element device (such as a CE device) supports ZTP, access can be completed automatically through device discovery. If the device does not support automatic online access, or cannot access the network due to network environment or other conditions, manual entry of device information (such as brand and model) is required.
[0127] S4. Automated Configuration. The cloud control center translates the configuration of each access point according to the topology plan and requirements, and completes the download and application of the configuration. If the customer manually goes online, the configuration file is exported according to the network element, and the customer manually configures it according to the network element.
[0128] The final configuration output configuration document can be copied and pasted by personnel of small and medium-sized enterprises after logging into the network element device, or the network element can access the one-click configuration system through a wireless device to send data.
[0129] Specifically, the schematic diagram of the implementation path for automating wide area network configuration is as follows: Figure 6 As shown. The front-end uses React to implement a drag-and-drop interface and real-time preview functionality; the back-end relies on FastAPI to process logic through a rule engine and generate CLI (command line interface) configuration commands; the vendor template library is based on the YANG model and adapts to the configuration specifications of multiple vendors such as Cisco, Huawei, and H3C; the simulation verification layer uses Netmiko / Paramiko (a tool library for device interaction) combined with EVE-NG (a network simulation platform) to simulate and verify the generated configuration.
[0130] Optionally, a lightweight development and deployment environment is provided, using React+Ant Design or Vue.js+Element UI to build an enterprise-grade lightweight visual interface that supports component-based development and rapid iteration. Tools such as React DnD / Vue Draggable are used to implement drag-and-drop network topology modules and canvas layout, while JointJS / GoJS and other libraries are used to implement professional flowchart / topology diagram drawing libraries, completing the visual deployment of network strategies. WebSocket / Socket.IO and other tools are used to build real-time communication between the system and network elements, dynamically displaying the generated CLI commands.
[0131] The backend development utilizes object-oriented languages such as Phyton, a customized network rules engine, and defines vendor CLI templates using YAML / YANG / JSON to dynamically render configurations and handle multi-vendor command conversion logic. It provides a RESTful API (Application Programming Interface) to receive frontend configuration data and return CLI commands.
[0132] The graphical module design of the topology graph includes:
[0133] (1) Module classification:
[0134] Network basics: VLANs, IP address allocation, routing tables.
[0135] Security policies: Firewall rules, ACL (Access Control List), and VPN (Virtual Private Network) configurations.
[0136] Service deployment: load balancing, QoS policies.
[0137] (2) Interaction logic:
[0138] Users drag and drop modules onto the canvas in the application's UI → fill in the parameter form (such as interface, VLAN ID, IP segment, routing protocol, etc.) → automatically generate a topology diagram.
[0139] The backend design includes:
[0140] (1) Multiple vendor CLI libraries:
[0141] The network of devices may be from a single manufacturer or multiple manufacturers, and different manufacturers' CLI class library engines may be built.
[0142] (a)cisco:
[0143] vlan:
[0144] create:"vlan{vlan_id}\n name{vlan_name}"
[0145] delete:"no vlan{vlan_id}"
[0146] (b)huawei:
[0147] vlan:
[0148] create:"vlan{vlan_id}\n description{vlan_name}"
[0149] (2) Yang API Interface:
[0150] For example: Adding VLANs to the Yang API interface
[0151]
[0152]
[0153] (3) Multi-vendor instruction conversion engine
[0154] A unified network intent description language (NIDL) is defined. Users only need to declare their business objectives (such as "guarantee video conferencing bandwidth"), and the system automatically translates them into multi-vendor commands. It should be noted that the multi-vendor command conversion engine here only applies to networks using equipment from multiple vendors, and is programmed according to the APIs of different vendors and different devices.
[0155] By setting up templates for different types of services from multiple vendors, the system can automatically match them based on network conditions.
[0156] ① Users select target vendors (such as Cisco and Huawei).
[0157] ② Load the corresponding vendor's YAML template based on the module type (such as VLAN).
[0158] ③ Replace the placeholders in the template (such as {vlan_id}) with user input values.
[0159] def generate_cli(module_type,vendor,params):
[0160] with open(f"templates / {vendor}.yaml")as f:
[0161] templates = yaml.safe_load(f)
[0162] command_template=templates[module_type]["create"]
[0163] return command_template.format(**params)
[0164] It should be noted that in the visual topology system, devices exist only as models and are distinguished solely by type. The cloud control center performs single-vendor data adaptation based on device type. Only some devices using multiple vendors require switching to a multi-vendor command conversion engine for command conversion before configuration is distributed.
[0165] (4) AI-based configuration conflict pre-detection
[0166] In a network architecture on the same wide area network, the interconnection IP addresses, user addresses, VLAN IDs, and loopback addresses of various sites, such as headquarters and branch offices, must not overlap or conflict. Otherwise, the network will generate alarms and become chaotic. During the network automation planning and configuration process, it is necessary to detect conflicts and provide automatic repair suggestions (such as reallocating IP segments and adjusting rule priorities).
[0167] The overall approach abstracts network devices (switches, routers) as graph nodes, and the physical or logical connections between devices as edge nodes. Each node and edge has attached attributes:
[0168] Node attributes: device type, management IP, and configured VLAN list.
[0169] Side attributes: port number, connected VLAN (Trunk / Access / Hybrid mode), IP subnet information.
[0170] Among them, the diagram of network device connections and attributes based on the graph model can be as follows: Figure 7 As shown.
[0171] ① Detect duplicate VLAN IDs
[0172] Constructing a VLAN propagation graph:
[0173] Iterate through the port configurations of all devices and record the allowed VLAN IDs for each port.
[0174] If the ports of two devices are connected via a trunk and the same VLAN is allowed, then a VLAN propagation path is established.
[0175] Conflict detection:
[0176] Use either Depth-First Search (DFS) or Breadth-First Search (BFS) to traverse the propagation path of the same VLAN ID.
[0177] If the same VLAN ID is found to exist in two broadcast domains that are not directly connected, it is considered a conflict.
[0178] ② Detecting overlapping IP addresses
[0179] Subnetting:
[0180] Convert each subnet (CIDR) to an integer range.
[0181] Example: 10.10.10.0 / 24 → range [16777216, 16777471] (calculated by converting IP to integer).
[0182] Interval collision detection:
[0183] Use an interval tree or sorting scan method to check if there is an intersection among all subnet intervals.
[0184] If there is an overlap, it is determined that the IP addresses are overlapping.
[0185] ③ Collision Detection Performance Improvement Solution
[0186] Incremental detection: When a user modifies the configuration through the graphical interface, only the affected subgraphs are recalculated.
[0187] Parallel processing: For large-scale network topologies, VLAN and IP detection tasks are split into multi-threaded / distributed computing.
[0188] ④ Visual feedback
[0189] Conflict highlighting: Mark conflicting VLANs or IP subnets in red in the graphical interface.
[0190] Recommended solutions: Based on graph connectivity analysis, we recommend configuration or subnet adjustment solutions.
[0191] It's important to note that configuration conflict pre-checking detects potential network conflicts within a wide area network (WAN) during deployment. For example, interfaces or VLANs cannot be defined with the same IP address in the same routing table, but the same address can exist in different VPN instances. Additionally, rules are needed to detect Layer 3 loops. For instance, in a U-shaped network with two interconnected devices and links, two-point, two-way loop prevention is required during the introduction of OSPF and BGP (Border Gateway Protocol).
[0192] (5) Dynamic QoS Optimization Based on Few-Shot Learning
[0193] By collecting or inputting network metric data that needs optimization, including traffic characteristics, network characteristics, and service priorities, the original data is compressed into low-dimensional vectors using methods such as Time Series Embedding (TS2Vec), and then encoded and labeled. A prototype vector is constructed using a small number of samples (e.g., 5 traffic scenarios), and the similarity between new samples and the prototype is calculated.
[0194] Traffic characteristics: application type (video / file transfer), bandwidth utilization, and frequency of burst traffic.
[0195] Network status: End-to-end latency (RTT), jitter, and packet loss.
[0196] Business priority: Key business functions manually marked by the user (e.g., VoIP is high priority).
[0197] For example, the architecture diagram of a QoS dynamic optimization system based on few-shot learning is as follows: Figure 8 As shown, the complete process from data acquisition to policy execution is presented: The system starts with network data acquisition, and the acquisition layer relies on Prometheus / SNMP to obtain real-time telemetry data such as traffic, latency, and packet loss; the few-shot learning engine serves as the core, first extracting features, encoding and labeling the raw data through methods such as TS2Vec, and then using meta-learning models such as MAML / ProtoNet to construct prototype vectors and calculate the similarity of new samples to complete model inference based on a small number of samples (such as 5 traffic scenarios); finally, the QoS dynamic adjustment execution layer links with the vendor's device adapter (to realize CLI / API translation) to complete policy distribution and verification.
[0198] It's important to note that both dynamic QoS optimization and user-declared service objectives are user requirements. However, QoS here refers more to metrics such as network latency, reliability, and priority, while user-declared service objectives focus more on the overall network architecture, routing, and the routing protocols used. For example, dynamic QoS optimization can include the following steps:
[0199] ① First, collect network traffic data and analyze the network quality, such as latency and packet loss, bandwidth utilization, the proportion of various applications, and traffic during peak and off-peak hours to determine peak network usage periods, when sudden traffic spikes typically occur, and when they will have a substantial impact on the network. Continuously collect real traffic data from the production network, and newly collected real traffic data needs to be tagged with scenario labels.
[0200] ② Traffic patterns artificially generated to simulate specific network conditions are created using traffic generation tools (such as iPerf, Ixia, Spirent TestCenter), network simulators (such as NS-3, OMNeT++), or mathematical models. When training the embedded model (such as TS2Vec), incorporating simulated multiple samples (including extreme and abnormal scenarios) can help the model learn more robust feature representations and improve its generalization ability to unknown real-world scenarios. Combining the traffic characteristics in the existing network with the user's SLA (Service Level Agreement) requirements, possible scenarios are simulated and inferences are performed. The goal is to enable the system to accurately identify and handle various real-world traffic scenarios.
[0201] ③ Through scenario reasoning, determine the QoS policy that suits the user requirements and the current network conditions, inform the customer of the optimization effect after dynamically adjusting the QoS, and implement it after the customer confirms.
[0202] It should be noted that QoS policy distribution is end-to-end, and generally includes the interconnected devices and the originating and destination device ports of the source and destination IP addresses.
[0203] (6) Equipment deployment
[0204] Manual deployment and access:
[0205] After completing the overall system analysis (i.e., simulation), the configuration format of network devices can be output on a per-network-element basis:
[0206] ①CLI command text: Copy directly to the device terminal.
[0207] ②Ansible Playbook: Automated batch deployment.
[0208] ③ PDF report: Includes topology diagram and configuration details.
[0209] It should be noted that many manufacturers' devices do not meet the requirement of zero-contact automatic startup. In this case, the configuration can be flashed manually.
[0210] Access to automated deployment:
[0211] ① Zero-contact safety authentication and automatic registration
[0212] ② When the network device is powered on for the first time, it completes two-way authentication with the cloud control center through the pre-set device fingerprint certificate (such as the key in the TPM chip).
[0213] ③ Automatically download initial configuration (such as management IP and VPN tunnel parameters).
[0214] It should be noted that when the end-point CE device has the conditions for network access and automatic online registration and management, it can be automatically managed and configuration data can be distributed through the cloud.
[0215] It should be noted that this invention utilizes the target network topology, interconnection bandwidth and line type, combined with network functional requirements, to collect network device brand and model information. It automatically configures each node device according to the requirements and obtains the target network result through simulation. After confirming that the result matches the target, the configuration of each node is completed. This invention solves the problems of syntax differences and proprietary protocol compatibility between devices from different manufacturers, enabling network administrators to quickly complete service deployment and network setup in a network scenario without needing in-depth knowledge of device commands. Furthermore, this invention eliminates the need to deploy large controllers, reducing the skill requirements for network administrators in small and medium-sized enterprises and improving network management efficiency.
[0216] The wide area network configuration method provided in this embodiment of the invention first receives a wide area network topology structure constructed by a user through a visual topology system using a drag-and-drop method; then receives basic configuration information filled in by the user for the network devices in the topology structure; next, based on the filled-in basic configuration information, performs simulation data configuration according to a preset manufacturer's operating system command format, and simulates the network effect; then, in response to the user's confirmation operation that the simulated network effect is consistent with expectations, obtains the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology structure; if the access network element device involves multiple manufacturer brands or models, based on the manufacturer brand and model of each access network element device, uses a cross-manufacturer configuration translation engine to translate the basic configuration information of each access network element device, generating corresponding target configuration information. This invention enables network administrators in small and medium-sized enterprises (SMEs) to easily construct and configure wide area network (WAN) topologies through drag-and-drop operations and basic configuration information input in a visual topology system, significantly reducing operational difficulty. Simultaneously, it allows for configuration of simulated data and network effects according to preset vendor operating system command formats, validating the configuration's rationality before actual deployment. Furthermore, by utilizing a cross-vendor configuration translation engine, it translates the basic configuration information of access network elements from multiple vendors and models, generating target configuration information. This achieves seamless adaptation between devices from different vendors and supports flexible switching from single-vendor networking to multi-vendor expansion scenarios, comprehensively improving the compatibility, flexibility, and ease of use of WAN configuration. It solves the problems of insufficient compatibility, low configuration flexibility, and difficulty in adapting to the skill levels of network administrators in SMEs found in existing WAN configuration methods.
[0217] Example 2:
[0218] like Figure 9 As shown, this embodiment provides a wide area network (WAN) configuration apparatus for executing the above-described WAN configuration method, including:
[0219] The topology acquisition module 11 is used to receive the wide area network topology structure constructed by the user through a visual topology system by dragging and dropping.
[0220] The basic configuration acquisition module 12 is connected to the topology acquisition module 11 and is used to receive basic configuration information filled in by the user for the network devices in the topology.
[0221] The simulation configuration simulation module 13 is connected to the basic configuration acquisition module 12 and is used to configure simulation data according to the basic configuration information filled in, according to the preset manufacturer's operating system command format, and to simulate network effects.
[0222] The brand and model acquisition module 14 is connected to the simulation configuration module 13 and is used to acquire the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology in response to the user's confirmation operation that the simulation network effect is consistent with the expectation.
[0223] The cross-manufacturer configuration translation module 15 is connected to the brand and model acquisition module 14. It is used to translate the basic configuration information of each access network element device based on the manufacturer brand and model of each access network element device and generate the corresponding target configuration information.
[0224] The configuration information distribution module 16 is connected to the cross-vendor configuration translation module 15 and is used to distribute the target configuration information to the corresponding access network element device.
[0225] Optionally, the visualization topology system has a pre-defined typical network architecture and topology configuration sub-module, and the topology structure acquisition module 11 is specifically used for:
[0226] Receive wide area network topology structures constructed by users through dragging and dropping typical network architectures in the visual topology system; or,
[0227] It receives WAN topologies that users can customize and build by dragging and dropping the topology configuration submodule in the visual topology system.
[0228] Optionally, the device further includes:
[0229] The correction module is used to respond to the user's confirmation that the simulated network effect is inconsistent with expectations, and to perform correction operations on the topology and / or basic configuration information based on the feedback difference information.
[0230] Optionally, the device further includes:
[0231] The configuration template definition module is used to define command-line interface (CLI) configuration templates for different network equipment manufacturers using YAML, the next-generation data modeling language YANG, or JavaScript object notation JSON.
[0232] The translation engine building module is used to build cross-vendor configuration translation engines based on CLI configuration templates from different network equipment manufacturers.
[0233] Optionally, the device further includes:
[0234] The graph model construction module is used to abstract network devices in the topology or actual network topology as graph nodes, abstract logical or physical connections between network devices as edge nodes, and attach attributes to each graph node and edge node to obtain the corresponding graph model.
[0235] A conflict detection module is used to perform conflict detection based on the graph model. The conflict detection includes at least one of the following: detecting whether the Virtual Local Area Network Identifier (VLANID) is duplicated, and detecting whether the Internet Protocol (IP) addresses overlap.
[0236] Optionally, the device further includes:
[0237] The business objective receiving module is used to receive business objectives declared by users through the Network Intent Description Language (NIDL).
[0238] The business target translation module is used to translate the business target using a translation engine configured by a different vendor and generate corresponding business target translation instructions;
[0239] The translation instruction distribution module is used to distribute the translated instructions for the business objectives to the corresponding network devices in the actual network topology.
[0240] Optionally, the basic configuration information includes Quality of Service (QoS) policy information, and the device further includes:
[0241] The network metrics collection module is used to collect network metrics data from the actual network topology;
[0242] The feature extraction and labeling module is used to extract, encode, and label features from the collected network indicator data using the time series vectorization representation TS2Vec.
[0243] The prototype vector construction module is used to construct prototype vectors from a small number of samples, less than a preset threshold, using labeled network metric data as sample data.
[0244] The QoS dynamic adjustment module is used to generate and execute dynamic adjustments of the QoS policy based on the similarity reasoning between the real-time data vector and the prototype vector.
[0245] Example 3:
[0246] refer to Figure 10 This embodiment provides a wide area network configuration device, including a memory 21 and a processor 22. The memory 21 stores a computer program, and the processor 22 is configured to run the computer program to execute the wide area network configuration method in Embodiment 1.
[0247] The memory 21 is connected to the processor 22. The memory 21 can be a flash memory, a read-only memory or other memory, and the processor 22 can be a central processing unit or a microcontroller.
[0248] Example 4:
[0249] This embodiment provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the wide area network configuration method in Embodiment 1 above.
[0250] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), DVD or other optical disc storage, cartridges, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer.
[0251] In summary, the wide area network configuration method, apparatus, and readable storage medium provided in this embodiment of the invention first receive a wide area network topology structure constructed by a user through a visual topology system using a drag-and-drop method; receive basic configuration information filled in by the user for the network devices in the topology structure; then, based on the filled-in basic configuration information, perform simulation data configuration according to a preset manufacturer's operating system command format, and simulate the network effect; then, in response to the user's confirmation that the simulated network effect is consistent with expectations, obtain the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology structure; if the access network element device involves multiple manufacturer brands or models, based on the manufacturer brand and model of each access network element device, use a cross-manufacturer configuration translation engine to translate the basic configuration information of each access network element device to generate corresponding target configuration information. This invention enables network administrators in small and medium-sized enterprises (SMEs) to easily construct and configure wide area network (WAN) topologies through drag-and-drop operations and basic configuration information input in a visual topology system, significantly reducing operational difficulty. Simultaneously, it allows for configuration of simulated data and network effects according to preset vendor operating system command formats, validating the configuration's rationality before actual deployment. Furthermore, by utilizing a cross-vendor configuration translation engine, it translates the basic configuration information of access network elements from multiple vendors and models, generating target configuration information. This achieves seamless adaptation between devices from different vendors and supports flexible switching from single-vendor networking to multi-vendor expansion scenarios, comprehensively improving the compatibility, flexibility, and ease of use of WAN configuration. It solves the problems of insufficient compatibility, low configuration flexibility, and difficulty in adapting to the skill levels of network administrators in SMEs found in existing WAN configuration methods.
[0252] It is understood that the above embodiments are merely exemplary implementations used to illustrate the principles of the present invention, and the present invention is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and essence of the present invention, and these modifications and improvements are also considered to be within the scope of protection of the present invention.
Claims
1. A wide area network configuration method, characterized in that, The method includes: Receive wide area network topology structures constructed by users through a visual topology system using drag-and-drop functionality; Receive basic configuration information filled in by the user for the network devices in the topology; Based on the basic configuration information filled in, the simulation data is configured according to the preset operating system command format of the manufacturer, and the simulation network effect is simulated. In response to the user's confirmation that the simulated network effect is consistent with expectations, the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology are obtained. If the access network element device involves multiple manufacturers or models, based on the manufacturer and model of each access network element device, the basic configuration information of each access network element device is translated using a cross-manufacturer configuration translation engine to generate the corresponding target configuration information; The target configuration information is then sent to the corresponding access network element devices.
2. The method according to claim 1, characterized in that, The visual topology system has pre-defined typical network architectures and topology configuration sub-modules. The process of receiving wide area network topology structures constructed by users through drag-and-drop functionality via the visual topology system specifically includes: Receive wide area network topology structures constructed by users through dragging and dropping typical network architectures in the visual topology system; or, It receives WAN topologies that users can customize and build by dragging and dropping the topology configuration submodule in the visual topology system.
3. The method according to claim 1, characterized in that, The method further includes: In response to the user's confirmation that the simulated network effect is inconsistent with expectations, a correction operation is performed on the topology and / or basic configuration information based on the feedback discrepancy information.
4. The method according to claim 1, characterized in that, Before generating the corresponding target configuration information by translating the basic configuration information of each access network element device based on the manufacturer's brand and model using a cross-manufacturer configuration translation engine, the method further includes: Define command-line interface (CLI) configuration templates for different network equipment manufacturers using YAML, the next-generation data modeling language YANG, or JavaScript object representation JSON; A cross-vendor configuration translation engine is built based on CLI configuration templates from different network equipment manufacturers.
5. The method according to claim 1, characterized in that, The method further includes: Abstract the network devices in the topology or actual network topology as graph nodes, and abstract the logical or physical connections between network devices as edge nodes. Attach attributes to each graph node and edge node to obtain the corresponding graph model. Conflict detection is performed based on the graph model, and the conflict detection includes at least one of the following: detecting whether the Virtual Local Area Network Identifier (VLAN ID) is duplicated, and detecting whether the Internet Protocol (IP) addresses overlap.
6. The method according to claim 1, characterized in that, The method further includes: Receive the business objectives declared by the user through the Network Intent Description Language (NIDL); The business objectives are translated using a translation engine configured by a different vendor, generating corresponding business objective translation instructions; The translated instructions for the business objectives are then sent to the corresponding network devices in the actual network topology.
7. The method according to claim 6, characterized in that, The basic configuration information includes Quality of Service (QoS) policy information. After sending the target configuration information to the corresponding access network element devices, the method further includes: Collect network metric data from actual network topologies; TS2Vec uses time-series vectorization to extract, encode, and label features from collected network metric data; The labeled network metric data is used as sample data, and a prototype vector is constructed using a small number of samples less than a preset threshold. Based on the similarity inference between the real-time data vector and the prototype vector, dynamic adjustments to the QoS policy are generated and executed.
8. A wide area network configuration device, characterized in that, The device includes: The topology acquisition module is used to receive the wide area network topology structure that the user constructs by dragging and dropping through the visual topology system; The basic configuration acquisition module is connected to the topology acquisition module and is used to receive basic configuration information filled in by the user for the network devices in the topology. The simulation configuration module is connected to the basic configuration acquisition module. It is used to configure simulation data according to the basic configuration information filled in, according to the preset manufacturer's operating system command format, and to simulate network effects. The brand and model acquisition module is connected to the simulation configuration module and is used to acquire the manufacturer brand and model of each access network element device in the actual network topology corresponding to the topology in response to the user's confirmation operation that the simulation network effect is consistent with expectations. A cross-manufacturer configuration translation module is connected to the brand and model acquisition module. If the access network element device involves multiple manufacturers' brands or models, the cross-manufacturer configuration translation engine is used to translate the basic configuration information of each access network element device based on the manufacturer's brand and model of each access network element device, and generate the corresponding target configuration information. The configuration information distribution module is connected to the cross-vendor configuration translation module and is used to distribute the target configuration information to the corresponding access network element device.
9. A wide area network configuration device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to implement the wide area network configuration method as described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the wide area network configuration method as described in any one of claims 1-7.