Network planning methods, display methods, devices, storage media and software products

Abstract

This application provides a network planning method, display method, device, storage medium, and program product. The method involves a network planning server responding to a network planning request, determining at least one network type; identifying a target network configuration file matching any network type from multiple network configuration files; the target network configuration file including network device information and connection rules; generating first network planning information corresponding to the network type according to the network device information and the connection rules; determining the grid-connected portion corresponding to the multiple network types when at least one network type includes multiple network types, and determining second network planning information corresponding to the grid-connected portion according to the connection rules; and generating target network planning information based on the first and second network planning information corresponding to the multiple network types. The technical solution provided by this application improves the efficiency and accuracy of network planning.

Description

Technical Field

[0001] This application relates to the field of network planning, and more particularly to a network planning method, display method, device, storage medium, and program product. Background Technology

[0002] With the rapid development of emerging fields such as artificial intelligence model training and high-performance computing, modern data centers are facing severe network planning challenges.

[0003] In traditional solutions, network planning is typically done manually by personnel such as network planners, relying on their planning experience and on-site surveys. However, this approach is inefficient and fails to meet the demands of high-efficiency network planning, especially for complex planning requirements in scenarios involving multiple network types. Current manual planning methods struggle to handle these situations effectively. Summary of the Invention

[0004] This application provides a network planning method, display method, device, storage medium, and program product to solve the problem of low efficiency in traditional solutions where network planning and design are performed manually by relevant personnel, thereby improving network planning efficiency.

[0005] Firstly, this application provides a network planning method applied to a network planning server, the method comprising:

[0006] In response to a network planning request, determine at least one network type;

[0007] From multiple network configuration files, determine a target network configuration file that matches any network type; the target network configuration file includes network device information and connection rules.

[0008] Generate first network planning information corresponding to the network type based on the network device information and the connection rules;

[0009] When the at least one network type includes multiple network types, determine the grid connection portion corresponding to the multiple network types, and determine the second network planning information corresponding to the grid connection portion according to the connection rules;

[0010] Based on the first network planning information and the second network planning information corresponding to the multiple network types, target network planning information is generated.

[0011] Secondly, this application provides a display method applied to a network planning client, the method comprising:

[0012] Display the network planning page;

[0013] Planning prompts are displayed on the network planning page;

[0014] In response to a network planning operation triggered by the planning prompt information, a network planning request is generated. The network planning request is used to determine at least one network type and to determine a target network configuration file that matches any network type from multiple network configuration files. The target network configuration file includes network device information and connection rules. First network planning information corresponding to the network type is generated according to the network device information and the connection rules. In the case where the at least one network type includes multiple network types, the grid connection portion corresponding to the multiple network types is determined, and second network planning information corresponding to the grid connection portion is determined according to the connection rules. Target network planning information is generated based on the first network planning information and the second network planning information corresponding to the multiple network types respectively.

[0015] The target network planning information is displayed on the network planning page.

[0016] Thirdly, this application provides a computing device, including a processing component and a storage component; the storage component stores a computer program; the computer program is invoked and executed by the processing component to implement the network planning method as described in the first aspect, or the display method as described in the second aspect.

[0017] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processing component, implements the network planning method as described in the first aspect, or the display method as described in the second aspect.

[0018] Fifthly, this application provides a computer program product, including a computer program or instructions, which, when executed by a processing component, implement the network planning method as described in the first aspect, or the display method as described in the second aspect.

[0019] In this embodiment, in response to a network planning request, at least one network type can be determined, and a target network configuration file matching any network type can be determined from multiple network configuration files. The target network configuration file includes network device information and connection rules. Based on this network device information and connection rules, first network planning information corresponding to the network type can be automatically generated. Furthermore, when at least one network type includes multiple network types, the grid-connected portions corresponding to the multiple network types can be determined, and second network planning information corresponding to the grid-connected portions can be automatically determined according to the connection rules. Based on the first and second network planning information corresponding to the multiple network types respectively, target network planning information is automatically generated.

[0020] By automatically generating the first network planning information for each network type based on its corresponding network device information and connection rules, this significantly improves network planning efficiency compared to manual planning by personnel. It also reduces reliance on personnel's planning experience, lowers planning costs, and enhances accuracy. Furthermore, in planning scenarios involving multiple network types, the system automatically determines the interconnected portions of each network type according to their respective connection rules, and automatically confirms the second network planning information for those portions. Based on the first and second network planning information for each network type, it automatically generates the target network planning information. This solves the problem of traditional manual planning methods struggling to handle multi-network type deployments, meeting the needs of multi-network type deployments and further improving network planning efficiency and accuracy.

[0021] Furthermore, by using a configuration approach, network configuration files are used to store network device information and connection rules. When responding to network planning requests, these configuration data can be used to guide the automatic generation of network planning information. Compared to the hard-coded approach, this greatly improves the flexibility of network planning and provides technical support for the flexible and rapid updating of subsequent network configuration files.

[0022] These or other aspects of this application will become more apparent in the following description of the embodiments. Attached Figure Description

[0023] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0024] Figure 1 A flowchart of one embodiment of a network planning method provided in this application is shown;

[0025] Figure 2 This diagram illustrates a first constraint rule configuration system in a practical application.

[0026] Figure 3a A flowchart of one embodiment of a display method provided in this application is shown;

[0027] Figure 3b This shows a schematic diagram of a network planning page in a practical application;

[0028] Figure 4 This diagram illustrates the architecture of a system in a practical application.

[0029] Figure 5This invention provides a schematic diagram of the structure of one embodiment of a network planning device.

[0030] Figure 6 This application provides a schematic diagram illustrating the structure of one embodiment of a display device.

[0031] Figure 7 A schematic diagram of a computing device in a practical application is shown. Detailed Implementation

[0032] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0033] It should be noted that, in the cases involving user information in the embodiments of this application, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse. In addition, the various models involved in this application (including but not limited to language models or large models) comply with relevant laws and standards.

[0034] Additionally, it should be noted that when user interaction operations or triggering operations are involved in the embodiments of this application, these operations include, but are not limited to, various interaction methods such as touch operations, gesture operations, voice operations, head movement operations, and eye movement operations. Touch operations include, but are not limited to, click operations, double-click operations, long-press operations, swipe operations, pinch operations, or mouse hover operations. Swipe operations include, but are not limited to, straight-line swipes and curved-line swipes.

[0035] The technical solution of this application is applicable to network planning scenarios, especially heterogeneous network planning scenarios involving the deployment of multiple network types. The network planning results are used to guide network deployment in physical space, particularly in user-owned physical spaces. Physical space can refer to physical environmental resources, such as data centers. In a practical application, the technical solution of this application can be applied to cloud computing scenarios to perform network planning for the physical spaces of dedicated cloud customers, thereby enabling the construction of dedicated cloud networks.

[0036] Cloud computing is one of the fastest-growing trends in computer technology, involving the provision of hosted services over a network. A cloud computing environment provides computing and storage resources as a service to end users. End users can then request processing from the provided services. The processing capacity of these services is typically limited by the available resources.

[0037] It should be understood that although this disclosure includes a detailed description of cloud computing, the implementation of the teachings herein is not limited to a cloud computing environment. Rather, embodiments of the invention can be implemented in conjunction with any other type of computing environment now known or developed hereafter.

[0038] Cloud computing is a service delivery model designed to enable on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and deployed with minimal management effort or interaction with service providers.

[0039] Taking network planning in a private cloud scenario as an example, currently, it is usually done manually by relevant personnel, such as network planners, based on their own planning experience and on-site surveys, to design the network for private cloud customers and provide the network planning information to the private cloud customers so that they can deploy the network in the physical space.

[0040] Furthermore, with the rapid development of these emerging fields, traditional single-network types are no longer sufficient to meet complex task requirements, necessitating support for the collaborative planning of multiple network types, such as Data Center Networks (DCNs) and Cloud Performance Networks (CPNs). Traditional manual planning methods are ill-suited for effective planning.

[0041] To address the aforementioned technical problems, the inventors have proposed a technical solution for this application, comprising: responding to a network planning request, determining at least one network type; determining a target network configuration file matching any network type from multiple network configuration files; the target network configuration file including network device information and connection rules; generating first network planning information corresponding to the network type according to the network device information and the connection rules; when the at least one network type includes multiple network types, determining the grid-connected portion corresponding to the multiple network types, and determining second network planning information corresponding to the grid-connected portion according to the connection rules; and generating target network planning information based on the first network planning information and the second network planning information corresponding to the multiple network types respectively.

[0042] By automatically generating the first network planning information for each network type based on its corresponding network device information and connection rules, this significantly improves network planning efficiency compared to manual planning by personnel. It also reduces reliance on personnel's planning experience, lowers planning costs, and enhances accuracy. Furthermore, in planning scenarios involving multiple network types, the system automatically determines the interconnected portions of each network type according to their respective connection rules, and automatically confirms the second network planning information for those portions. Based on the first and second network planning information for each network type, it automatically generates the target network planning information. This solves the problem of traditional manual planning methods struggling to handle multi-network type deployments, meeting the needs of multi-network type deployments and further improving network planning efficiency and accuracy.

[0043] Furthermore, by using a configuration approach, network configuration files are used to store network device information and connection rules. When responding to network planning requests, these configuration data can be used to guide the automatic generation of network planning information. Compared to the hard-coded approach, this greatly improves the flexibility of network planning and provides technical support for the flexible and rapid updating of subsequent network configuration files.

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] Figure 1 This is a flowchart of an embodiment of a network planning method provided in this application. The technical solution of this embodiment can be applied to a network planning server.

[0046] In a practical application, the system architecture to which the technical solution of this application applies may include a network planning server and a network planning client. The network planning client and the network planning server can establish a connection through a network, which may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0047] The network planning client can be targeted at personnel within the private cloud system, such as network architects, allowing them to trigger planning operations and view target network planning information. Optionally, the network planning client can also be targeted at private cloud customers, allowing them to trigger planning operations and view target network planning information. Alternatively, if a private cloud customer has login permissions for the network planning client, the client can be made available to them, allowing them to trigger planning operations and view target network planning information.

[0048] Optionally, the system architecture may also include a user client. The user client can establish connections with both the network planning client and the network planning server via the network. The user client can interact with the network planning server to provide server configuration information, user preference information, etc., or to obtain target network planning information sent by the network planning server. The user client may be geared towards private cloud customers.

[0049] Both the network planning client and user terminal can be browsers, apps, web applications such as H5 (HyperText Markup Language 5) applications, lightweight applications (also known as mini-programs), or cloud applications. Both can be deployed on electronic devices and rely on the device or certain apps on the device to run. Electronic devices can have displays and support information browsing, such as personal mobile terminals like smartphones, tablets, personal computers, desktop computers, smart speakers, smartwatches, etc.

[0050] Network planning servers can include servers that provide various services, such as servers that provide instant messaging or servers that provide network planning information generation services.

[0051] It should be noted that the server can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. The server can also be a server in a distributed system, or a server combined with blockchain. The server can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0052] It should be noted that, in the embodiments of this application, the user described generally refers to a "virtual user." Real users can register user accounts on the server to obtain user identity in the network environment. The interaction between the server and the user can be implemented based on the user account, and the corresponding data received or sent by the server to the user is also based on the user account. In fact, the user terminal corresponding to the user account receives or sends the corresponding data to the generating server.

[0053] Figure 1 The network planning method shown may include the following steps:

[0054] 101: In response to a network planning request, determine at least one network type.

[0055] In a practical application, at least one network type may include a Data Center Network (DCN) and a Cloud Performance Network (CPN). The CPN network may include multiple sub-network types such as a CPN computing network and a CPN storage network; in this embodiment, these multiple sub-network types are treated as a single network type.

[0056] Network planning requests can be generated by planning operations performed by users on the network planning page. Optionally, planning prompts can be sent to the network planning client beforehand and displayed on the network planning page to prompt the user to perform planning operations. In this embodiment, the user can refer to relevant network planning personnel or dedicated cloud customers. Network planning personnel can trigger network planning requests based on the needs of dedicated cloud customers.

[0057] Optionally, the network planning request may include at least one network type identifier provided by the user, thereby determining at least one network type corresponding to the at least one network type identifier.

[0058] Optionally, at least one network type can be automatically determined based on server configuration information. In some embodiments, determining at least one network type in response to a network planning request may include:

[0059] In response to a network planning request, obtain server configuration information; determine at least one network type that matches the server configuration information. Optionally, the server configuration information may be provided by the user.

[0060] Server configuration information may include the target task to be executed, initial scale information for multiple servers, and attribute information for any one server. The network planning server can determine at least one network type that matches the target task. For example, if the target task is artificial intelligence model training or high-performance computing, the at least one matching network type may include both DCN and CPN networks. Conversely, if the target task does not involve basic tasks such as artificial intelligence model training or high-performance computing, the at least one matching network type may only include DCN networks.

[0061] By obtaining server configuration information, at least one network type that matches the server configuration information is automatically determined, which improves the accuracy of network type determination and does not require user specification, thus enhancing the user experience.

[0062] 102: Determine the target network configuration file that matches any network type from multiple network configuration files; the target network configuration file includes network device information and connection rules.

[0063] Each network configuration file corresponds to a different network type. Different network types can have different configuration files, and the network device information and connection rules can also differ. A specific network configuration file can be pre-configured for each network type.

[0064] Network device information can include the device type, the quantity of each device type, and the device attributes. Device types can include switches, routers, optical splitters, and traffic splitters. Switches can be further divided into access switches and core switches (also known as distribution layer switches). Device attributes can include the manufacturer and model number.

[0065] For example, the equipment types included in a DCN network may include ASW (Access Switch) and DSW (Distribution Switch). The equipment types included in a CPN network may include RASW (Computer Network Access Switch) and RDSW (Computer Network Core Switch).

[0066] Connection rules can include connection requirements for any network device, network connection requirements, and network topology requirements. Connection requirements for any network device can include the port connection requirements for each of the device's multiple ports. Network connection requirements can refer to the connection requirements between two network devices belonging to different network types. Network topology requirements are used to ensure the rationality of the network topology. For example, network topology requirements can include that at least one port in any network device must establish a connection with ports in other network devices; that is, among the multiple network devices involved in the network topology, there cannot be any network device whose ports are all unconnected.

[0067] Optionally, one or more network configuration files can be pre-configured for each network type.

[0068] When a network type corresponds to a network configuration file, that network configuration file can be used as the target network configuration file for matching that network type.

[0069] When a network type corresponds to multiple network configuration files, as an optional approach, any one of the multiple network configuration files can be used as the target configuration file for matching that network type.

[0070] As another alternative approach, the above method may also include:

[0071] Obtain user preference information; user preference information may include network size information and / or device preference information corresponding to any network type;

[0072] Based on this, the target network configuration file that matches any network type can include:

[0073] Determine the target network profile that matches the network size information and / or device preference information for any given network type.

[0074] Network size can include thresholds for the number of network devices and servers that can be deployed. Any network type can offer multiple network sizes, with smaller network sizes allowing for lower thresholds for the number of network devices and / or servers compared to larger network sizes. Different network sizes can correspond to different network configuration files. For example, a user can specify a target network size for network planning, and this target network size can be included in the network size information.

[0075] Device preferences can include preferences for device attributes such as manufacturer and model. For example, a user can specify to deploy network devices manufactured by a target manufacturer and with a target model; the device preference information can include the target manufacturer and target model.

[0076] As one optional implementation, a target network configuration file matching the target network size can be determined for any network type. As another optional implementation, a target network configuration file matching device preference information can be determined for any network type. As yet another optional implementation, a target network configuration file matching both network size information and device preference information can be determined for any network type.

[0077] By acquiring user preference information, and given that multiple network configuration files correspond to any given network type, the system can determine the target network configuration file that matches the network size and / or device attributes specified by the user. This can meet diverse and personalized user planning needs and further enhance the user experience.

[0078] To improve the efficiency of configuration file generation and updates, multiple network configuration files can optionally be obtained using declarative logical expression configuration. This can be achieved using IaC (Infrastructure as Code) declarative modeling configuration, where declarative logical expression is a programming and expression paradigm whose core lies in describing the goal or desired state of computation, rather than specifying concrete execution steps. In a practical application, network configuration files can include YAML format configuration files (a format used to express data serialization).

[0079] Based on this, after determining the target network configuration file, the above method may further include:

[0080] The rule parsing engine is invoked to parse the target network configuration file and determine the network device information and connection rules.

[0081] Optionally, the above method may further include:

[0082] In response to a configuration file update request, retrieve the new network configuration file that uses declarative logic to express the configuration;

[0083] Based on the newly added network configuration file, multiple network configuration files are updated.

[0084] By using a declarative logic expression to generate network configuration files, compared to hard-coding, configuration and code are decoupled. Users do not need to manually write a lot of network configuration code, which greatly reduces the user operation process. When updating the network configuration file, there is no need to rewrite the code or perform a series of operations such as code testing and deployment, which further improves the generation and updating efficiency of network configuration files. At the same time, it supports the storage and reuse of multiple versions of configuration files.

[0085] 103: Generate the first network planning information corresponding to this network type based on network device information and connection rules.

[0086] In this embodiment, for each network type, the first network planning information corresponding to that network type can be generated according to the network device information and connection rules corresponding to that network type.

[0087] Optionally, the first network planning information may include a first network topology. Generating the first network planning information corresponding to this network type, based on network device information and connection rules, may include:

[0088] Calculate the first network topology corresponding to this network type based on network device information and connection rules.

[0089] Optionally, the virtual resources corresponding to the multiple network devices included in the network type can be determined, and the first network planning information can be generated based on the first network topology and the virtual resources corresponding to the multiple network devices.

[0090] Virtual resources can include IP addresses, BGP (Border Gateway Protocol), ASN (Autonomous System Number), etc., and can be provided by users.

[0091] 104: In cases where at least one network type includes multiple network types, determine the grid connection portion corresponding to the multiple network types, and determine the second network planning information corresponding to the grid connection portion according to the connection rules.

[0092] This involves determining the grid connection portion for each of the multiple network types based on connection rules corresponding to each network type, such as grid connection requirements. The grid connection portion can include multiple target network devices with grid connection requirements from the various network types. Furthermore, it involves generating second network planning information corresponding to the grid connection portion according to the connection rules for each of the multiple network types.

[0093] Optionally, the second network planning information may include a second network topology. According to the connection rules, the second network planning information corresponding to the grid-connected portion may include:

[0094] Calculate the second network topology corresponding to the grid-connected portion according to the connection rules.

[0095] Optionally, the virtual resources corresponding to the multiple target network devices included in the grid connection can be determined, and second network planning information can be generated based on the second network topology and the virtual resources corresponding to the multiple target network devices.

[0096] 105: Generate target network planning information based on the first network planning information and the second network planning information corresponding to multiple network types respectively.

[0097] Optionally, the target network planning information may include the target network topology. Based on first network planning information and second network planning information corresponding to multiple network types, the generated target network planning information may include:

[0098] The target network topology is generated based on the first and second network topologies corresponding to multiple network types.

[0099] Optionally, target planning information can also be generated based on the virtual resources corresponding to the multiple network devices included in the multiple network types, the virtual resources corresponding to the multiple target network devices included in the grid connection, and the target network topology.

[0100] Optionally, the above method may further include:

[0101] When at least one network type includes a network type, target network planning information is generated based on the first network planning information corresponding to that network type.

[0102] Optionally, generating target network planning information based on the first network planning information corresponding to this network type may include:

[0103] The first network topology corresponding to this network type is used as the target network topology.

[0104] Optionally, target planning information can also be generated based on the virtual resources corresponding to the multiple network devices included in the network type and the target network topology.

[0105] In a practical application, target network planning information may include a target device list, device connection information, and virtual resource information. The target device list may include multiple network devices, the device connection information may include the connection relationships between multiple network devices, and the virtual resource information may include the virtual resources corresponding to each of the multiple network devices.

[0106] Optionally, the above method may further include:

[0107] The target network planning information is provided to the user; the target network planning information can be used to instruct the determination of multiple network devices in the physical space according to the device list, the connection of the multiple network devices according to the device connection information, and the setting of corresponding virtual resources for the multiple network devices according to the virtual resource information.

[0108] Optionally, users can determine whether the physical space includes multiple network devices from the target device list, and whether several of these network devices need to be deployed in the physical space, based on the target device list. If multiple network devices corresponding to the target device list have already been deployed in the physical space, users can connect the multiple network devices according to the device connection information, and set corresponding virtual resources for each of the multiple network devices according to the virtual resource information.

[0109] These multiple network devices can be used to respond to task processing requests and utilize their respective virtual resources to transmit task data in order to execute the target task.

[0110] There are several ways to provide target network planning information to users. For example, the information can be sent to a network planning client for display, or a download link can be provided for users to download locally. Alternatively, the target network planning information can be sent to users via email, SMS, or instant messaging based on a communication account. The communication account could be, for example, the user's email address, mobile phone number, or instant messaging number. This application does not limit the specific method of provision.

[0111] In this embodiment, by automatically generating the first network planning information corresponding to any network type based on the network device information and connection rules, the efficiency of network planning is greatly improved compared to manual network planning by relevant personnel. This also reduces reliance on the planning experience of relevant personnel, lowers network planning costs, and improves the accuracy of network planning. Furthermore, in planning scenarios involving multiple network types, the connection rules corresponding to each network type are used to automatically determine the interconnected portions of multiple network types and automatically confirm the second network planning information corresponding to the interconnected portions. Based on the first and second network planning information corresponding to each of the multiple network types, target network planning information is automatically generated. This solves the problem of network planning in multi-network type deployment scenarios where manual planning is difficult to handle in traditional solutions, meeting the needs of multi-network type deployment and further improving network planning efficiency and accuracy.

[0112] Furthermore, by using a configuration approach, network configuration files are used to store network device information and connection rules. When responding to network planning requests, these configuration data can be used to guide the automatic generation of network planning information. Compared to the hard-coded approach, this greatly improves the flexibility of network planning and provides technical support for the flexible and rapid updating of subsequent network configuration files.

[0113] In some embodiments, network device information may include multiple device types and the number of devices corresponding to each device type, and connection rules may include the connection requirements of any network device. Based on this, generating first network planning information corresponding to the network type according to the network device information and connection rules may include:

[0114] Based on multiple device types and the number of devices corresponding to each device type, determine the multiple network devices corresponding to this network type;

[0115] Based on the connection requirements of each network device, determine the connection relationship between the multiple network devices.

[0116] Calculate the first network topology based on multiple network devices and their connections.

[0117] Based on the first network topology and the virtual resources corresponding to multiple network devices, first network planning information corresponding to the network type is generated.

[0118] Virtual resources may include one or more such as IP addresses, BGP protocols, and ASNs, and may be provided by users or determined based on target network configuration files.

[0119] In a practical application, virtual resources may include IP addresses. Optionally, the above method may also include:

[0120] Get the IP network segment corresponding to any network type;

[0121] Within this IP network segment, assign IP addresses to the various network devices included in this network type.

[0122] The IP network segment can be provided by the user, and different network types correspond to different IP network segments.

[0123] The first network planning information may include a list of first devices, first connection information, and first virtual resource information for that network type. The first device list may include the device ID, manufacturer, and model number of each network device included in that network type. The first connection information may include the connection information of each network device included in that network type, and may include port connection information for each port. The first virtual resource information may include the virtual resources allocated to each network device included in that network type.

[0124] Specifically, the connection requirements of any network device may include the port connection requirements corresponding to multiple ports involved in the network device.

[0125] Based on this, and considering the connection requirements of each network device, the connection relationships among the multiple network devices are determined as follows:

[0126] For any port in any network device, determine the connection relationship between that port and a port in a network device of another device type, according to the port connection requirements of that port.

[0127] For example, determining the connection relationship between a specific uplink interface in an access switch and a specific downlink interface in a core switch within a CPN network.

[0128] By determining the connection relationship between any port in any network device and a port in another network device of a different device type according to the port connection requirements, the connection relationship between network devices can be determined.

[0129] When at least one network type includes multiple network types, to improve network topology generation efficiency, a first network topology corresponding to each of the multiple network types can be generated first, followed by the generation of a second network topology corresponding to the interconnected portion. For example, a DCN network generates a corresponding Spine-Leaf topology, and a CPN network generates a corresponding Rail-Optimized topology. Therefore, in some embodiments, determining the interconnected portion corresponding to multiple network types may include:

[0130] Identify multiple target network devices with network connection requirements within multiple primary network topologies.

[0131] Optionally, multiple first network topologies can be generated independently in parallel. This parallel and independent generation can be achieved by calling different processes to execute simultaneously, thereby further improving generation efficiency.

[0132] Based on this, and according to the connection rules, the second network planning information corresponding to the grid-connected portion can include:

[0133] Determine the network connection relationship between the multiple target network devices according to their respective network connection requirements;

[0134] Calculate the second network topology based on multiple target network devices and their interconnection relationships;

[0135] Based on the second network topology and the target virtual resources corresponding to the multiple target network devices, second network planning information is generated.

[0136] The second network planning information may include a list of second devices, second connection information, and second virtual resource information for the network connection portion. The second device list may include the device ID, manufacturer, and model number of each of the multiple target network devices. The second connection information may include the connection information of the multiple target network devices, including port connection information for each port. The second virtual resource information may include the target virtual resources allocated to each of the multiple target network devices.

[0137] In multi-network type deployment scenarios, taking IP addresses as an example of virtual resources, consider two target network devices connected in a parallel network. Since they belong to different network types and correspond to different IP network segments, setting IP addresses in different IP network segments will prevent data transmission. Therefore, to avoid virtual resource allocation conflicts, in some embodiments, the above method may further include:

[0138] In cases where at least one network type includes multiple network types, obtain the IP network segments corresponding to each of the multiple network types, and determine the available target IP network segments other than the multiple IP network segments;

[0139] For any given network type, within the corresponding IP network segment, assign IP addresses to each of the network devices included in that network type, excluding the target network device.

[0140] For the network connection portion corresponding to multiple network types, IP addresses are set for multiple target network devices within the target IP network segment.

[0141] Furthermore, in scenarios involving multiple network types, including DCN and CPN networks, besides potential IP address allocation conflicts for target network devices in the connected portion, IP address allocation conflicts may also exist for certain specific network devices. For example, the IP address of the management port in a CPN network cannot use an IP address within the IP subnet corresponding to the CPN network type for data transmission. In this case, an IP address can be assigned to the management port within an available target IP subnet.

[0142] This embodiment decomposes network planning into three levels: "selecting network configuration files that match user preference information (including network scale information and / or device preference information)" + "generating network topology based on network configuration files" + "setting virtual resources for devices after network topology generation". In planning scenarios involving multiple network types, at each level, different network types use their own differentiated data models / algorithms to independently generate their own first network planning information, maintaining the independence and architectural characteristics of each network type and preventing mutual interference. For the network consolidation part, merging is performed after the first network planning information is generated. For example, the network topology of the consolidation part is generated after each first network topology is generated, and virtual resource conflict detection is performed on the target network devices of the consolidation part after the virtual resources of network devices of each network type are determined separately. For target network devices with resource conflicts, their corresponding virtual resources are re-determined, thereby ensuring that resource allocation is carried out without resource competition in the future. A phased collaborative algorithm is used to ensure the balance between optimization within a single network and cross-network coordination, while avoiding resource conflicts, solving configuration inconsistency problems, and simplifying the complexity of unified resource management.

[0143] Considering that users may encounter limitations in physical spaces, such as server room layout and rack space constraints, when deploying networks in a physical environment, the above method may further include the following in some embodiments to adapt to the actual physical space and ensure smooth network deployment:

[0144] Obtain the constraint rules configured for the physical space; network devices are deployed in the physical space, and the target network planning information can be used to indicate the construction of at least one network type corresponding to the physical space.

[0145] Based on this, the target network planning information can be generated using the first network planning information and the second network planning information corresponding to multiple network types, respectively.

[0146] Based on the first network planning information and the second network planning information corresponding to multiple network types, target network planning information is generated according to the constraint rules.

[0147] Optionally, when at least one network type includes a network type, generating target network planning information based on the first network planning information corresponding to that network type may include:

[0148] Based on the first network planning information corresponding to this network type, target network planning information is generated according to the constraint rules.

[0149] Constraint rules can be implemented in multiple ways.

[0150] As an optional implementation, the constraint rules may include the first constraint rule. The above method may also include:

[0151] In response to a tag setting request, set at least one tag attribute for network devices deployed in the physical space;

[0152] In response to a rule configuration request, configure a first constraint rule corresponding to the physical space based on at least one tag attribute corresponding to different network devices.

[0153] Tag attributes can identify the physical location where network devices are deployed.

[0154] Figure 2 A schematic diagram of a first constraint rule configuration system in a practical application is shown. Figure 2 As shown, the configuration system 20 may include a label attribute setting module 201 and a first constraint rule definition module 202.

[0155] The tag attribute setting module 201 can use a key-value pair format, such as tag attribute - attribute value, to set at least one tag attribute for network devices deployed in the physical space. For example, at least one tag attribute may include a data center tag "Data Center: Data Center Identifier", a cabinet tag "Cabinet: Cabinet Identifier", and a layer number tag "Layer Number: Layer Number Identifier", to identify a specific data center, a specific cabinet in that data center, and a specific layer within that cabinet in the physical space where the network device is deployed.

[0156] The first constraint rule definition module 202 can generate at least one constraint rule based on at least one tag attribute, and use the at least one constraint rule as the first constraint rule. For example, the at least one constraint rule may include "data center constraint", "rack constraint", and "number of layers constraint".

[0157] The first constraint rule can be used to constrain connection restrictions between a first network device with a first label attribute and a second network device with a second label attribute. Connection restrictions can include one or more of the following: prohibiting connection, allowing connection, and forcing connection. For example, connection restrictions could be: prohibiting network devices deployed in different data centers from establishing connections, allowing network devices deployed in the same data center or on the same rack, and so on.

[0158] Optionally, the first constraint rule can be expressed using declarative logic. In a practical application, a label selector can be used to configure the first constraint rule corresponding to the physical space based on at least one label attribute corresponding to different network devices. Based on this, a rule parsing engine can be invoked to parse the first constraint rule and obtain the connection restrictions between network devices.

[0159] By setting label attributes for network devices deployed in the physical space, and configuring the corresponding first constraint rules (i.e., connection restrictions between network devices) based on these label attributes, this embodiment creatively proposes a constraint modeling paradigm of "physical attribute labeling" + "connection restriction logic," which greatly improves the flexibility of the first constraint rules. Faced with new physical space constraint scenarios, label attributes and corresponding constraint rules can be set as needed without modifying the code, ensuring rapid adaptation to diverse physical space environments and meeting diverse and complex physical space deployment requirements.

[0160] As an alternative implementation, the constraint rules may include a second constraint rule. The above method may also include:

[0161] Obtain the port usage status of network devices deployed in the physical space; port usage status includes any of the following: idle, used, and pending; the port to be used can be a port with other connection requirements besides the target network plan, and can be provided by the user.

[0162] In response to the rule configuration request, the second constraint rule corresponding to the physical space is configured based on the port usage status of different network devices.

[0163] The second constraint rule can be used to constrain the generation of first network planning information and / or second network planning information based on the target port, where the target port can be a port whose port usage status is idle or waiting to be used.

[0164] Optionally, the second constraint rule can also be used to constrain connection restrictions corresponding to different port usage states. For example, allowing connections to ports in an idle state, and prohibiting connections to ports in a used or pending state, etc.

[0165] Optionally, the second constraint rule can be expressed using declarative logic. Based on this, the rule parsing engine can be invoked to parse the second constraint rule and obtain the connection restrictions corresponding to the port.

[0166] By obtaining the port usage status of network devices, fine-grained connection control at the port level is supported to meet users' connection needs for specific ports.

[0167] As another optional implementation, the constraint rules may include a first constraint rule and a second constraint rule. The configuration process of the first constraint rule and the second constraint rule is described above and will not be repeated here.

[0168] In a practical application, target network planning information is generated based on multiple first network planning information and second network planning information according to constraint rules. Specifically, the candidate network topology composed of multiple first network topologies and second network topologies is adjusted according to constraint rules to obtain the target network topology.

[0169] Based on this, the generation of target network planning information, according to the constraint rules, can include the following, based on the first network planning information and the second network planning information corresponding to multiple network types respectively:

[0170] The candidate network topology is composed of the first network topology and the second network topology corresponding to multiple network types, respectively.

[0171] The candidate network topology is updated according to the constraint rules to obtain the updated candidate network topology;

[0172] If the multiple network devices involved in the updated candidate network topology meet their respective connection requirements, the updated candidate network topology will be used as the target network topology.

[0173] Optionally, the above method may further include:

[0174] If multiple network devices involved in the updated candidate network topology do not meet their respective connection requirements, constraint warning information will be output.

[0175] For example, if a pair of network devices in a candidate network topology establishes a connection but does not meet the first constraint rule for allowing a connection based on their respective label attributes, the connection between the two devices can be canceled, and new connections between the two network devices and other network devices can be established. As another example, if a port of a network device in a candidate network topology establishes a connection but meets the second constraint rule for allowing a connection based on its port usage status, the connection to that port can be canceled, leaving the port unconnected, and so on.

[0176] After updating the candidate network topology using constraint rules, the updated candidate network topology can be checked according to the connection requirements of each of the multiple network devices involved in the topology to ensure the rationality of the architecture.

[0177] If the test fails, a constraint notification message can be used to inform the user of the test result. Optionally, the constraint notification message can also prompt the user to update the constraint rules.

[0178] Optionally, when at least one network type includes a network type, target network planning information is generated based on the first network planning information corresponding to that network type according to constraint rules. Specifically, the candidate network topology formed by the first network topology can be adjusted according to the constraint rules to obtain the target network topology.

[0179] Based on this, and according to the constraint rules, generating target network planning information based on the first network planning information corresponding to this network type can include:

[0180] The first network topology corresponding to this network type is selected as the candidate network topology;

[0181] The candidate network topology is updated according to the constraint rules to obtain the updated candidate network topology;

[0182] If the multiple network devices involved in the updated candidate network topology meet their respective connection requirements, the updated candidate network topology will be used as the target network topology.

[0183] Optionally, the above method may further include:

[0184] If multiple network devices involved in the updated candidate network topology do not meet their respective connection requirements, constraint warning information will be output.

[0185] This solution innovatively introduces the concept of "code as configuration" into network planning. It proposes a three-stage automatic iterative network planning scheme: "building network topologies based on declarative logical expression configuration files," "constraint-based network topology correction," and "automatic network topology rationality detection after correction." Compared to traditional hard-coding methods, this approach significantly improves network planning efficiency, accuracy, flexibility, and adaptability. When at least one network type includes a single network type, it automatically generates a first network topology based on the network configuration file, using it as the minimum candidate network topology under ideal conditions. This approach reduces network deployment costs while ensuring the architecture meets server configuration requirements. Physical constraints and / or port constraints are used as correction conditions for candidate network topologies to meet deployment needs under physical space constraints and / or port usage constraints. Furthermore, it adjusts candidate network topologies while maintaining architectural rationality, and performs real-time architectural rationality checks after adjustments to ensure that architectural specifications are not violated.

[0186] In some embodiments, the above method may further include:

[0187] In response to a server configuration update request, the server configuration information is updated to obtain the updated server configuration information; the updated server configuration information includes secondary scale information for multiple servers.

[0188] Based on the updated server configuration information, and according to the network device information and connection rules corresponding to at least one network type, while keeping the target network planning information unchanged, determine at least one new network device and the third network planning information corresponding to at least one new network device.

[0189] In this embodiment, the second scale information includes more servers than the first scale information, meaning that server capacity has been expanded.

[0190] Based on the updated server configuration information, the step of determining at least one network type matching the server configuration information can be re-executed. If the network device information corresponding to any network type is updated, at least one new network device is identified. Based on this at least one new network device and at least one new server, third network planning information is determined according to the connection rules corresponding to the at least one new network device.

[0191] Optionally, new connection relationships can be determined between any newly added network device and at least one newly added server, at least one network device involved in the target network topology, and / or at least one server, as well as new connection relationships between any newly added server and at least one newly added network device, and / or at least one network device involved in the target network topology.

[0192] Identify the virtual resources corresponding to at least one newly added network device;

[0193] Based on the newly added connection relationships and the virtual resources corresponding to at least one newly added network device, the third network planning information is determined.

[0194] The third network planning information may include a list of newly added devices, new connection information, and new virtual resource information. The list of newly added devices may include the device ID, manufacturer, and model number of each of the at least one newly added network device. The new connection information may include the connection information of the at least one newly added network device, including port connection information for each port. The new virtual resource information may include the virtual resources allocated to each of the at least one newly added network device.

[0195] By responding to server configuration update requests and updating server configuration information, in the event of server expansion, based on the updated server configuration information, and according to the network device information and connection rules corresponding to at least one network type, at least one new network device and the third network planning information corresponding to at least one new network device are determined while keeping the target network planning information unchanged. This improves the scalability of network planning and further enhances network planning efficiency compared to the hard-coding method used in traditional solutions.

[0196] Figure 3a This is a flowchart of an embodiment of a display method provided in this application. The technical solution of this embodiment can be applied to a network planning client.

[0197] 301: Displays the network planning page.

[0198] 302: Display planning prompts on the network planning page.

[0199] 303: In response to a network planning operation triggered by a planning prompt message, a network planning request is generated.

[0200] Network planning operations can be triggered by users. Taking network planning in a private cloud scenario as an example, optionally, the user can be a relevant network planning personnel or a private cloud customer.

[0201] In a practical application, a network planning request can be generated in response to a network planning operation triggered by a dedicated cloud customer who has login permissions to the network planning client. Conversely, if the dedicated cloud customer does not have login permissions to the network planning client, a network planning request can be generated in response to a network planning operation triggered by a network planner. The network planner can trigger network planning operations on behalf of the dedicated cloud customer according to their needs.

[0202] The network planning request is used to determine at least one network type and to determine a target network configuration file that matches any network type from multiple network configuration files. The target network configuration file includes network device information and connection rules. Based on the network device information and connection rules, first network planning information corresponding to the network type is generated. In the case where at least one network type includes multiple network types, the grid connection part corresponding to multiple network types is determined, and second network planning information corresponding to the grid connection part is determined according to the connection rules. Based on the first network planning information and second network planning information corresponding to multiple network types respectively, target network planning information is generated.

[0203] 304: Displays the target network planning information on the network planning page.

[0204] By responding to network planning operations on the network planning page, a network planning request is generated. Based on the network device information and connection rules corresponding to any network type, the first network planning information for that network type is automatically generated. Compared to manual network planning by personnel, this significantly improves network planning efficiency, reduces reliance on personnel's planning experience, lowers network planning costs, and increases accuracy. Furthermore, in planning scenarios involving multiple network types, the system automatically determines the interconnected portions of each network type according to their respective connection rules, and automatically confirms the second network planning information corresponding to those portions. Based on the first and second network planning information for each network type, target network planning information is automatically generated. This solves the network planning problem in multi-network type deployment scenarios where traditional manual planning methods struggle, meeting the needs of multi-network type deployments and further improving network planning efficiency and accuracy.

[0205] Furthermore, by using a configuration approach, network configuration files are used to store network device information and connection rules. When responding to network planning requests, these configuration data can be used to guide the automatic generation of network planning information. Compared to the hard-coded approach, this greatly improves the flexibility of network planning and provides technical support for the flexible and rapid updating of subsequent network configuration files.

[0206] Figure 3b This illustrates a schematic diagram of a network planning page in a practical application. For example... Figure 3b As shown, the network planning page 31 displays planning prompt information 311, which includes the text prompt "Please select network size" and a trigger control (shown as a drop-down menu button). In response to a network planning operation triggered by the planning prompt information, such as the user clicking the drop-down menu button, a selection list 312 containing multiple candidate network sizes is displayed on the network planning page 31. In response to the user's selection of any candidate network size, the network size is determined.

[0207] The network planning operations involving network configuration files, device preference information, etc., are the same as those described above and will not be explained in detail here.

[0208] It should be noted that some processes described in the above embodiments and accompanying drawings include multiple operations appearing in a specific order. However, it should be clearly understood that these operations may not be executed in the order they appear in this document, or they may be executed in parallel. The operation numbers, such as 101, 102, etc., are merely used to distinguish different operations and do not represent any execution order. Furthermore, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel. It should also be noted that the descriptions such as "first" and "second" in this document are used to distinguish different messages, devices, modules, etc., and do not represent a sequential order, nor do they limit "first" and "second" to different types.

[0209] Figure 4 This diagram illustrates a system architecture used in a practical application. The following section will combine... Figure 4 The schematic diagram shown illustrates the technical solution of this application.

[0210] like Figure 4 As shown, the system architecture may include a network planning server 401 and a network planning client 402.

[0211] The network planning server 401 can send planning prompts to the network planning client 402 and respond to the network planning request sent by the network planning client 402, determining at least one network type, a target network configuration file matching any network type, and user preference information (step 401). The network configuration file is generated using a declarative logical expression. Based on the network device information and connection rules corresponding to any network type, a first network topology corresponding to that network type is generated to obtain at least one first network topology (step 402). If at least one network type includes multiple network types, the interconnected portion corresponding to the multiple network types is determined, and a second network topology corresponding to the interconnected portion is generated according to the connection rules (step 403). Based on the multiple first and second network topologies, a candidate network topology is generated (step 404). If at least one network type includes a single network type, the first network topology corresponding to that network type is directly used as the candidate network topology (not shown in the figure). The candidate network topology undergoes a compliance check according to the connection requirements of each of the multiple network devices involved in the candidate network topology (step 405). If the check fails, the process returns to step 405 and is re-executed.

[0212] If the test passes, obtain the constraint rules (step 406). The constraint rules may include physical space constraints configured based on label attributes and connection limitations, and port status constraints configured based on port usage status. Update the candidate network topology using the constraint rules (step 407). Perform a conformity check on the updated candidate network topology according to the connection requirements of each network device involved. If the check passes, use the updated candidate network topology as the target network topology (step 408); if the check fails, output constraint warning information (step 409).

[0213] Optionally, the network planning server 401 can also determine the virtual resources corresponding to multiple network devices involved in any first network topology, and the target virtual resources corresponding to multiple target network devices involved in the second network topology, and generate target planning information based on the target network topology and the virtual resources corresponding to multiple network devices involved in the target network topology.

[0214] The target network planning information may include a target device list, device connection information, and virtual resource information. The target device list may include multiple network devices, the device connection information may include the connection relationships between these devices, and the virtual resource information may include the virtual resources corresponding to each of the network devices. The network planning server 401 can provide the target planning information to the user. The user can determine, based on the target device list, whether the physical space includes the multiple network devices listed, and whether certain network devices need to be deployed in the physical space. If the multiple network devices corresponding to the target device list are already deployed in the physical space, the user can connect these devices according to the device connection information and configure their respective virtual resources according to the virtual resource information. These multiple network devices can be used to respond to task processing requests, utilizing their respective virtual resources to transmit task data and execute the target task.

[0215] By automatically generating the first network planning information for each network type based on its corresponding network device information and connection rules, this significantly improves network planning efficiency compared to manual planning by personnel. It also reduces reliance on personnel's planning experience, lowers planning costs, and enhances accuracy. Furthermore, in planning scenarios involving multiple network types, the system automatically determines the interconnected portions of each network type according to their respective connection rules, and automatically confirms the second network planning information for those portions. Based on the first and second network planning information for each network type, it automatically generates the target network planning information. This solves the problem of traditional manual planning methods struggling to handle multi-network type deployments, meeting the needs of multi-network type deployments and further improving network planning efficiency and accuracy.

[0216] Furthermore, by using a configuration approach, network configuration files are used to store network device information and connection rules. When responding to network planning requests, these configuration data can be used to guide the automatic generation of network planning information. Compared to the hard-coded approach, this greatly improves the flexibility of network planning and provides technical support for the flexible and rapid updating of subsequent network configuration files.

[0217] Furthermore, by setting label attributes for network devices deployed in the physical space, and configuring the corresponding first constraint rules (i.e., connection restrictions between network devices) based on these label attributes, this embodiment creatively proposes a constraint modeling paradigm of "physical attribute labeling" + "connection restriction condition logicization." This greatly improves the flexibility of the first constraint rules. Faced with new physical space constraint scenarios, label attributes and corresponding constraint rules can be set as needed without modifying the code, ensuring rapid adaptation to diverse physical space environments and meeting diverse and complex physical space deployment requirements. By obtaining the port usage status of network devices, fine-grained connection control at the port level is supported, meeting users' connection needs for specific ports.

[0218] Furthermore, by automatically generating multiple first and second network topologies based on network configuration files, and then automatically generating the minimum candidate network topology under ideal conditions based on these multiple first and second network topologies, the network deployment cost is reduced while ensuring that the architecture meets server configuration requirements. Physical constraints and / or port constraints are used as correction conditions for candidate network topologies to meet deployment requirements under physical space constraints and / or port usage constraints. The candidate network topologies are adjusted while maintaining architectural rationality, and real-time architectural rationality checks are performed after adjustments to ensure that architectural specifications are not violated. This solution innovatively introduces the concept of "code as configuration" into network planning, proposing a three-stage automatic iterative calculation network planning scheme: "building network topologies based on declarative logical expression configuration files" + "constraint-corrected network topologies" + "automatic network topology rationality checks after correction." Compared to the hard-coding method used in traditional solutions, this comprehensively improves the efficiency, accuracy, flexibility, and adaptability of network planning.

[0219] Figure 5 A schematic diagram of one embodiment of a network planning device provided in this application is shown. The device may include the following units:

[0220] The first determining unit 501 is configured to determine at least one network type in response to a network planning request;

[0221] The second determining unit 502 is used to determine a target network configuration file that matches any network type from multiple network configuration files; the target network configuration file includes network device information and connection rules;

[0222] The first generation unit 503 is used to generate first network planning information corresponding to the network type according to network device information and connection rules;

[0223] The third determining unit 504 is used to determine the grid connection part corresponding to the multiple network types when at least one network type includes multiple network types, and to determine the second network planning information corresponding to the grid connection part according to the connection rules.

[0224] The second generation unit 505 is used to generate target network planning information based on the first network planning information and the second network planning information corresponding to multiple network types respectively.

[0225] In some embodiments, the apparatus may further include: a first acquisition unit, configured to acquire constraint rules configured for a physical space; network devices are deployed in the physical space; target network planning information is used to indicate the construction of a network corresponding to at least one network type in the physical space;

[0226] The second generation unit 505 can be specifically used to generate target network planning information based on at least one first network planning information and a second network planning information corresponding to at least one network type, according to constraint rules.

[0227] In some embodiments, the constraint rules include a first constraint rule, and the apparatus may further include: a first setting unit, configured to set at least one label attribute for network devices deployed in the physical space in response to a label setting request;

[0228] The first configuration unit is used to configure the first constraint rule corresponding to the physical space based on at least one tag attribute corresponding to different network devices in response to a rule configuration request.

[0229] In some embodiments, the constraint rules include a second constraint rule, and the apparatus may further include: a second acquisition unit, configured to acquire the port usage status of network devices deployed in the physical space; the port usage status includes any one of idle, used, and unused;

[0230] The second configuration unit is used to respond to a rule configuration request and configure a second constraint rule corresponding to the physical space based on the port usage status of different network devices. The second constraint rule is used to constrain the generation of the first network planning information and / or the second network planning information based on the target port, wherein the target port is a port whose port usage status is idle or waiting to be used.

[0231] In some embodiments, the connection rules include the connection requirements of any network device; the first network planning information includes a first network topology, the second network planning information includes a second network topology, the target network planning information includes a target network topology, and the first generation unit 503 can be specifically used to calculate the first network topology corresponding to the network type according to the network device information and the connection rules.

[0232] The third determining unit 504 can be specifically used to calculate the second network topology corresponding to the grid-connected part according to the connection rules;

[0233] The second generation unit 505 can be specifically used to form a candidate network topology by at least one first network topology and a second network topology corresponding to at least one network type; update the candidate network topology according to constraint rules to obtain the updated candidate network topology; and, if the multiple network devices involved in the updated candidate network topology meet their respective connection requirements, use the updated candidate network topology as the target network topology.

[0234] In some embodiments, multiple network profiles are obtained using declarative logical expression configuration; the apparatus may further include: a third acquisition unit, configured to acquire a new network profile configured using declarative logical expression configuration in response to a profile update request;

[0235] The first update unit is used to update multiple network configuration files based on the newly added network configuration file;

[0236] The second determining unit 502 can be used to call the rule parsing engine to parse the target network configuration file and determine the network device information and connection rules.

[0237] In some embodiments, the first determining unit 501 may be specifically used to obtain server configuration information in response to a network planning request; the server configuration information includes first scale information of a plurality of servers; and determine at least one network type that matches the server configuration information.

[0238] The device may further include: a second updating unit, configured to update server configuration information in response to a server configuration update request, and obtain updated server configuration information; the updated server configuration information includes second scale information of multiple servers;

[0239] The third update unit is used to determine at least one new network device and the third network planning information corresponding to at least one new network device, based on the updated server configuration information, according to the network device information and connection rules corresponding to at least one network type, while keeping the target network planning information unchanged.

[0240] In some embodiments, network device information includes multiple device types and the number of devices corresponding to each device type, and connection rules include the connection requirements of any network device; the first generation unit 503 can be specifically used to determine multiple network devices corresponding to a network type based on multiple device types and the number of devices corresponding to each device type; determine the connection relationship of multiple network devices based on the connection requirements corresponding to each of the multiple network devices; calculate a first network topology based on the multiple network devices and the connection relationship; and generate first network planning information corresponding to the network type based on the first network topology and the virtual resources corresponding to each of the multiple network devices.

[0241] In some embodiments, the third determining unit 504 may be specifically used to determine multiple target network devices with network connection requirements in multiple first network topologies; determine the network connection relationship between multiple target network devices according to the network connection requirements corresponding to each of the multiple target network devices; calculate a second network topology based on the multiple target network devices and the network connection relationship; and generate second network planning information based on the second network topology and the target virtual resources corresponding to each of the multiple target network devices.

[0242] In some embodiments, the virtual resource includes an IP address, and the apparatus may further include: a fourth acquisition unit, configured to acquire an IP network segment of a network type when at least one network type includes one network type; and to acquire IP network segments corresponding to each of the multiple network types when at least one network type includes multiple network types.

[0243] The fourth determining unit, in the case where at least one network type includes multiple network types, is used to determine the available target IP network segment in addition to multiple IP network segments;

[0244] The second setting unit, when at least one network type includes a network type, is used to set IP addresses for multiple network devices included in the network type within an IP network segment;

[0245] The third setting unit, when at least one network type includes multiple network types, is used to set IP addresses for each network device (excluding the target network device) within the corresponding IP network segment for any network type; and to set IP addresses for each target network device within the target IP network segment for the network-connected portion corresponding to multiple network types.

[0246] In some embodiments, the connection requirements include port connection requirements corresponding to multiple ports involved in the network device;

[0247] The first generation unit 503 can be used to determine the connection relationship between any port in any network device and a port in a network device of another device type, according to the port connection requirements of that port.

[0248] In some embodiments, the target network planning information includes a device list, device connection information, and virtual resource information; the device list includes multiple network devices, the device connection information includes the connection relationships between the multiple network devices, and the virtual resource information includes the virtual resources corresponding to each of the multiple network devices.

[0249] The device may further include: a providing unit for providing target network planning information to a user so that the user can deploy multiple network devices in the physical space according to the device list, connect the multiple network devices according to the device connection information, and set up corresponding virtual resources for the multiple network devices according to the virtual resource information; the multiple network devices are used to transmit task data using their respective corresponding virtual resources in response to task processing requests.

[0250] In some embodiments, the apparatus may further include: a fifth acquisition unit, configured to acquire user preference information; the user preference information includes network scale information and / or device preference information corresponding to any network type;

[0251] The second determining unit 502 can be specifically used to determine a target network configuration file that matches network size information and / or device preference information for any network type.

[0252] In some embodiments, the apparatus may further include: a fifth determining unit, configured to generate target network planning information based on first network planning information corresponding to the network type when at least one network type includes a network type.

[0253] Figure 5 The network planning device can perform Figure 1 The implementation principle and technical effects of the network planning method described in the illustrated embodiments will not be repeated here. The specific methods by which each unit of the network planning apparatus in the above embodiments performs its operations have been described in detail in the embodiments related to this method, and will not be elaborated upon here.

[0254] Figure 6 This application provides a schematic diagram of the structure of a display device according to one embodiment. The device may include the following units:

[0255] The first display unit 601 is used to display the network planning page;

[0256] The second display unit 602 is used to display planning prompts on the network planning page;

[0257] The third generation unit 603 is used to generate a network planning request in response to a network planning operation triggered by a planning prompt message. The network planning request is used to determine at least one network type and to determine a target network configuration file that matches any network type from multiple network configuration files. The target network configuration file includes network device information and connection rules. Based on the network device information and connection rules, first network planning information corresponding to the network type is generated. In the case where at least one network type includes multiple network types, the grid connection part corresponding to multiple network types is determined, and second network planning information corresponding to the grid connection part is determined according to the connection rules. Based on the first network planning information and second network planning information corresponding to multiple network types respectively, target network planning information is generated.

[0258] The third display unit 604 is used to display target network planning information on the network planning page.

[0259] Figure 6 The display device can perform Figure 6The implementation principle and technical effects of the display method described in the illustrated embodiments will not be repeated here. The specific methods by which each unit in the display device of the above embodiments performs its operations have been described in detail in the embodiments related to this method, and will not be elaborated upon here.

[0260] Figure 7 This is a schematic diagram of the structure of one embodiment of a computing device provided in this application. Figure 7 As shown, in practical applications, the computing device may include a storage component 701 and a processing component 702.

[0261] Storage component 701 is used to store computer programs and can be configured to store various other data to support operation on a computing device. Examples of this data include instructions for any application or method operating on the computing device, data structures, contact data, phone book data, messages, pictures, videos, etc.

[0262] Processing component 702, coupled to storage component 701, is used to execute computer programs in storage component 701 for implementing, etc. Figure 1 The network planning method shown or Figure 2 The display method shown.

[0263] Furthermore, such as Figure 7 As shown, the computing device may also include other components such as a communication component 703, a display component 704, a power supply component 705, and an audio component 706. Figure 7 The diagram only shows some components and does not mean that the computing device includes only these components. Figure 7 The components shown. Additionally... Figure 7 The components within the dashed box are optional, not mandatory, and their specific requirements depend on the product form of the computing device. The computing device in this embodiment can be a desktop computer, laptop computer, smartphone, or IoT (Internet of Things) device, or a server-side device such as a conventional server, cloud server, or server array. If the computing device in this embodiment is implemented as a desktop computer, laptop computer, or smartphone, it may include... Figure 7 The components within the dashed box; if the computing device in this embodiment is implemented as a conventional server, cloud server, or server array, etc., then it may not include... Figure 7 The component within the dashed box.

[0264] The aforementioned processing component includes one or more processors to execute computer instructions to complete all or part of the steps in the above method. Alternatively, the processing component may be implemented as one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the above method.

[0265] The aforementioned storage components can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0266] The aforementioned communication component is configured to facilitate wired or wireless communication between the device housing the communication component and other devices. The device housing the communication component can access wireless networks based on communication standards, such as mobile communication networks, or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel.

[0267] The aforementioned display components may include a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation.

[0268] The aforementioned power supply components provide power to various components within the device in which they reside. These power supply components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device in which they reside.

[0269] The aforementioned audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC) configured to receive external audio signals when the device containing the audio component is in an operating mode, such as call mode, recording mode, or voice recognition mode. The received audio signals can be further stored in memory or transmitted via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals.

[0270] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement the steps in the above-described method embodiments. The computer-readable storage medium includes volatile or non-volatile components, or a combination thereof, and can be removable or non-removable. Examples of computer-readable storage media include, but are not limited to, phase-change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), flash memory or other memory technologies, CD-ROM, Digital Video Disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium.

[0271] Accordingly, this application also provides a computer program product, which includes a computer program or instructions that, when executed by a processor, cause the processor to implement the steps in the above method embodiments. It should be understood that each step or combination of steps in the above method flow can be implemented by the computer program or instructions. Furthermore, these computer programs or instructions can be applied to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device, enabling the processor of the general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to function as an apparatus for implementing the corresponding functions in the above method embodiments.

[0272] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0273] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0274] Finally, it should be noted that the above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A network planning method, characterized in that, Applied to a network planning server, the method includes: In response to a network planning request, determine at least one network type; From multiple network configuration files, determine a target network configuration file that matches any network type; the target network configuration file includes network device information and connection rules. Generate first network planning information corresponding to the network type based on the network device information and the connection rules; When the at least one network type includes multiple network types, determine the grid connection portion corresponding to the multiple network types, and determine the second network planning information corresponding to the grid connection portion according to the connection rules; Based on the first network planning information and the second network planning information corresponding to the multiple network types, target network planning information is generated.

2. The method according to claim 1, characterized in that, Also includes: Obtain constraint rules configured for a physical space; the physical space is equipped with network devices; the target network planning information is used to indicate the construction of a network corresponding to the at least one network type in the physical space; The step of generating target network planning information based on the first network planning information and the second network planning information corresponding to the multiple network types includes: Based on the first network planning information and the second network planning information corresponding to the multiple network types respectively, target network planning information is generated according to the constraint rules.

3. The method according to claim 2, characterized in that, The constraint rule includes a first constraint rule, and the method further includes: In response to a tag setting request, at least one tag attribute is set for the network devices deployed in the physical space; In response to a rule configuration request, a first constraint rule corresponding to the physical space is configured based on at least one tag attribute corresponding to different network devices.

4. The method according to claim 2, characterized in that, The constraint rule includes a second constraint rule, and the method further includes: Obtain the port usage status of network devices deployed in the physical space; the port usage status includes any one of idle, used, and unused. In response to a rule configuration request, a second constraint rule is configured for the physical space based on the port usage status of different network devices. The second constraint rule is used to constrain the generation of the first network planning information and / or the second network planning information based on the target port, wherein the target port is a port whose port usage status is idle or waiting to be used.

5. The method according to claim 2, characterized in that, The connection rules include the connection requirements of any network device; The first network planning information includes a first network topology, and generating the first network planning information corresponding to the network type according to the network device information and the connection rules includes: Calculate the first network topology corresponding to the network type based on the network device information and the connection rules; The second network planning information includes a second network topology, and determining the second network planning information corresponding to the grid-connected portion according to the connection rules includes: Calculate the second network topology corresponding to the connected portion according to the connection rules; The target network planning information includes the target network topology. The generation of the target network planning information based on the first network planning information and the second network planning information corresponding to the multiple network types, according to the constraint rules, includes: The candidate network topology is composed of the first network topology and the second network topology corresponding to the multiple network types, respectively. The candidate network topology is updated according to the constraint rules to obtain the updated candidate network topology; If the multiple network devices involved in the updated candidate network topology meet their respective connection requirements, the updated candidate network topology shall be used as the target network topology.

6. The method according to any one of claims 1 to 5, characterized in that, The multiple network configuration files are obtained using declarative logical expression to define the configurations. The method further includes: In response to a configuration file update request, retrieve the new network configuration file that uses declarative logic to express the configuration; Based on the newly added network configuration file, the multiple network configuration files are updated.

7. The method according to any one of claims 1 to 5, characterized in that, The method further includes: The rule parsing engine is invoked to parse the target network configuration file and determine the network device information and the connection rules.

8. The method according to any one of claims 1 to 5, characterized in that, In response to a network planning request, determining at least one network type includes: In response to a network planning request, server configuration information is obtained; the server configuration information includes a first scale information of multiple servers; Determine at least one network type that matches the server configuration information; The method further includes: In response to a server configuration update request, the server configuration information is updated to obtain updated server configuration information; the updated server configuration information includes second-scale information of multiple servers; Based on the updated server configuration information, according to the network device information corresponding to the at least one network type and the connection rules, while keeping the target network planning information unchanged, at least one new network device and the third network planning information corresponding to the at least one new network device are determined.

9. The method according to claim 1, characterized in that, The network device information includes multiple device types and the number of devices corresponding to each of the multiple device types, and the connection rules include the connection requirements of any network device. The step of generating the first network planning information corresponding to the network type according to the network device information and the connection rules includes: Based on the multiple device types and the number of devices corresponding to each of the multiple device types, determine the multiple network devices corresponding to the network type; The connection relationship of the multiple network devices is determined based on the connection requirements corresponding to each of the multiple network devices; Based on the plurality of network devices and the connection relationships, calculate the first network topology; Based on the first network topology and the virtual resources corresponding to the plurality of network devices, first network planning information corresponding to the network type is generated.

10. The method according to claim 9, characterized in that, When the at least one network type includes multiple network types, determining the grid connection portion corresponding to the multiple network types includes: Identify multiple target network devices with network connection requirements within multiple primary network topologies; The step of determining the second network planning information corresponding to the grid-connected portion according to the connection rules includes: Determine the network connection relationship between the multiple target network devices according to their respective network connection requirements; Based on the multiple target network devices and the network connection relationship, calculate the second network topology; Based on the second network topology and the target virtual resources corresponding to the plurality of target network devices, second network planning information is generated.

11. The method according to claim 10, characterized in that, The virtual resources include Internet Protocol (IP) addresses; The method further includes: If the at least one network type includes a network type, obtain the IP network segment of the network type; Within the IP network segment, IP addresses are assigned to the various network devices included in the network type. When the at least one network type includes multiple network types, obtain the IP network segments corresponding to the multiple network types respectively, and determine the idle target IP network segments other than the multiple IP network segments; For any given network type, within the corresponding IP network segment, assign IP addresses to each of the network devices included in that network type, excluding the target network device. For the network connection portion corresponding to the multiple network types, IP addresses are respectively set for the multiple target network devices within the target IP network segment.

12. The method according to claim 9, characterized in that, The connection requirements include the port connection requirements corresponding to multiple ports involved in the network device; Determining the connection relationship of the multiple network devices based on their respective connection requirements includes: For any port in any network device, determine the connection relationship between the port and a port in a network device of another device type, according to the port connection requirements of the port.

13. The method according to claim 9, characterized in that, The target network planning information includes a device list, device connection information, and virtual resource information; the device list includes multiple network devices, the device connection information includes the connection relationships between the multiple network devices, and the virtual resource information includes the virtual resources corresponding to each of the multiple network devices. The method further includes: The target network planning information is provided to the user; the target network planning information is used to instruct the determination of multiple network devices in the physical space according to the device list, the connection of the multiple network devices according to the device connection information, and the setting of corresponding virtual resources for the multiple network devices according to the virtual resource information. The plurality of network devices are used to respond to task processing requests and transmit task data using their respective virtual resources.

14. The method according to any one of claims 1 to 5, characterized in that, Also includes: Obtain user preference information; The user preference information includes network size information and / or device preference information corresponding to any network type; The method for determining the target network configuration file that matches any network type includes: Determine the target network configuration file that matches the network size information and / or device preference information for any given network type.

15. The method according to any one of claims 1 to 5, characterized in that, Also includes: When the at least one network type includes a network type, target network planning information is generated based on the first network planning information corresponding to the network type.

16. The method according to any one of claims 1 to 5, characterized in that, The at least one network type includes data center networks and cloud performance networks.

17. A display method, characterized in that, The method, applied to a network planning client, includes: Display the network planning page; Planning prompts are displayed on the network planning page; In response to a network planning operation triggered by the planning prompt information, a network planning request is generated. The network planning request is used to determine at least one network type and to determine a target network configuration file that matches any network type from multiple network configuration files. The target network configuration file includes network device information and connection rules. First network planning information corresponding to the network type is generated according to the network device information and the connection rules. In the case where the at least one network type includes multiple network types, the grid connection portion corresponding to the multiple network types is determined, and second network planning information corresponding to the grid connection portion is determined according to the connection rules. Target network planning information is generated based on the first network planning information and the second network planning information corresponding to the multiple network types respectively. The target network planning information is displayed on the network planning page.

18. A computing device, characterized in that, This includes processing components and storage components; The storage component stores a computer program; the computer program is invoked and executed by the processing component to implement the network planning method as described in any one of claims 1 to 16, or the display method as described in claim 17.

19. A computer-readable storage medium, characterized in that, It stores a computer program, which, when executed by a processing component, implements the network planning method as described in any one of claims 1 to 16, or the display method as described in claim 17.

20. A computer program product, characterized in that, It includes a computer program or instructions that, when executed by a processing component, implement the network planning method as described in any one of claims 1 to 16, or the display method as described in claim 17.

Images