Cloud network service configuration method, device and system, electronic equipment and storage medium

Abstract

The embodiment of the invention discloses a cloud network service configuration method, device and system, electronic equipment and a storage medium. A network model management server side predefines a plurality of standard network models, and the method applied to the network model management server side comprises the following steps: receiving an interface calling request from a cloud service controller, the interface calling request being initiated by the cloud service controller according to a network configuration request, the interface calling request carries associated interface type parameters and model identification parameters; performing corresponding processing on a network model corresponding to the model identification parameter according to a processing mode matched with the interface type parameter, and obtaining a service model matched with the network configuration request based on the processed network model; and converting the service model into a device model adaptive to the network device, and issuing the device model to the corresponding network device. The cloud network service configuration scheme provided by the embodiment of the invention has higher service expansion flexibility.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a cloud network service configuration method, device, system, electronic device, and computer-readable storage medium. Background Art

[0002] In the existing cloud network service configuration implementation, network devices need to send service configuration information through the cloud service controller before exchanging traffic. When the network devices complete the service network configuration according to the service configuration information sent by the cloud service controller, the service traffic can be transmitted between the network devices of both parties. However, in this implementation method, the cloud service controller needs to connect to different network devices, including the interfaces and configuration models of the network devices. When expanding new services, the new cloud service controller needs to adapt to the network devices of the existing network. When the network equipment changes, such as replacing the manufacturer, upgrading the software, etc., the cloud service controller that it depends on also needs to be adapted and upgraded. It can be seen that the existing cloud network service configuration method still has the problem of inflexible service expansion. Summary of the invention

[0003] The embodiments of the present application respectively provide a cloud network service configuration method, a cloud network service configuration device, a cloud network service configuration system, an electronic device, a computer-readable storage medium, and a computer program product.

[0004] In the first aspect, an embodiment of the present application provides a cloud network service configuration method, which is applied to a network model management server, and the network model management server predefines multiple standard network models. The method includes: receiving an interface call request from a cloud business controller, wherein the interface call request is initiated by the cloud business controller based on a network configuration request, and the interface call request carries associated interface type parameters and model identification parameters; performing corresponding processing on the network model corresponding to the model identification parameter in a processing method matching the interface type parameter, and obtaining a business model matching the network configuration request based on the processed network model; converting the business model into a device model adapted to the network device and then sending it to the corresponding network device.

[0005] In the second aspect, an embodiment of the present application provides a cloud network service configuration device, which is configured on a network model management server, and the network model management server predefines multiple standard network models. The device includes: a first receiving module, configured to receive an interface call request from a cloud business controller, wherein the interface call request is initiated by the cloud business controller based on a network configuration request, and the interface call request carries associated interface type parameters and model identification parameters; a processing module, configured to perform corresponding processing on the network model corresponding to the model identification parameter in a processing method matching the interface type parameter, and obtain a business model matching the network configuration request based on the processed network model; a conversion module, configured to convert the business model into a device model adapted to the network device and then send it to the corresponding network device.

[0006] In the third aspect, an embodiment of the present application provides another cloud network service configuration method, which is applied to a cloud business controller, and the method includes: receiving a network configuration request sent by a cloud console; generating an interface call request based on the network configuration request, wherein the interface call request carries associated interface type parameters and model identification parameters; sending the interface call request to a network model management server, so that the network model management server performs corresponding processing on the network model corresponding to the model identification parameter in a processing method matching the interface type parameter, and obtains a business model matching the network configuration request based on the processed network model, and converts the business model into a device model adapted to the network device and then sends it to the corresponding network device.

[0007] In the fourth aspect, an embodiment of the present application provides another cloud network service configuration device, which is configured on a cloud business controller, and the device includes: a second receiving module, configured to receive a network configuration request sent by a cloud console; a generating module, configured to generate an interface call request based on the network configuration request, wherein the interface call request carries associated interface type parameters and model identification parameters; a sending module, configured to send the interface call request to a network model management server, so that the network model management server performs corresponding processing on the network model corresponding to the model identification parameter in a processing method matching the interface type parameter, obtains a business model matching the network configuration request based on the processed network model, and converts the business model into a device model adapted to the network device and then sends it to the corresponding network device.

[0008] In the fifth aspect, an embodiment of the present application provides a cloud network service configuration system, including a cloud console, a cloud business controller, a network model management server and a network device, wherein: the cloud console generates a network configuration request based on customer input information, and sends the network configuration request to the cloud business controller; the cloud business controller generates an interface call request based on the network configuration request, and sends the interface call request to the network model management server, wherein the interface call request carries associated interface type parameters and model identification parameters; the network model management server processes the network model corresponding to the model identification parameter in a processing method matching the interface type parameter, obtains a business model matching the network configuration request based on the processed network model, and converts the business model into a device model adapted to the network device and sends it to the corresponding network device.

[0009] In a sixth aspect, an embodiment of the present application provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements the steps in the cloud network service configuration method as described above.

[0010] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium having computer-readable instructions stored thereon. When the computer-readable instructions are executed by a processor of a computer, the computer executes the steps in the cloud network service configuration method as described above.

[0011] In an eighth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the steps in the cloud network service configuration method as described above.

[0012] In the technical solution provided in the embodiment of the present application, by predefining multiple standard network models on the network model management server, a unified model form is presented to the upper-layer cloud business controller. The cloud business controller obtains the corresponding business model based on the standard network model by making an interface call to the network model management server. The business model is subsequently converted into a device model adapted to the network device through the network model management server and sent to the corresponding network device. When the device model takes effect in the network device, the configuration of the cloud network service is completed. It can be seen that in the cloud network service configuration scheme proposed in the present application, the cloud business controller directly connects with the standard network model without identifying the differences between various network devices. When expanding services on the cloud, the cloud business controller still does not need to identify the differences between the underlying network devices; and when the network device changes, it is only necessary to make corresponding changes to the model conversion method in the network model management server, and there is no need to change the cloud business controller. It can be seen that the cloud network service configuration scheme proposed in the embodiment of the present application has higher business expansion flexibility.

[0013] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 is a schematic diagram of an exemplary cloud network service configuration scenario;

[0015] Figure 2 is a schematic diagram of an exemplary network model management service architecture;

[0016] Figure 3 is a schematic diagram of an exemplary implementation environment proposed in the present application;

[0017] Figure 4 is a flow chart of a cloud network service configuration method shown in an exemplary embodiment of the present application;

[0018] Figure 5 is a schematic diagram of an exemplary definition of an operation type object;

[0019] Figure 6 is a schematic diagram of an exemplary IP address object definition;

[0020] Figure 7 is a schematic diagram of an exemplary definition of a routing table entry object;

[0021] Figure 8 is based on Figure 4 A flow chart of a cloud network service configuration method further proposed in the illustrated embodiment;

[0022] Fig. 9is a flow chart of a cloud network service configuration method shown in another exemplary embodiment of the present application;

[0023] Fig.10 is a block diagram of a cloud network service configuration device shown in an exemplary embodiment of the present application;

[0024] Fig.11 is a block diagram of a cloud network service configuration device shown in another exemplary embodiment of the present application;

[0025] Fig.12 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0026] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.

[0027] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0028] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0029] The term "multiple" as used in this application refers to two or more than two. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0030] The terms "first", "second", "third" and "fourth" etc. in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order. The terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

[0031] First of all, it should be noted that the technical solution provided in this application involves the field of cloud technology. It can be understood that the network that provides resources is called "cloud", and the resources in the "cloud" are infinitely expandable in the eyes of users, and can be obtained at any time, used on demand, expanded at any time, and paid for by use. Cloud technology refers to a hosting technology that unifies a series of resources such as hardware, software, and network in a wide area network or a local area network to realize the calculation, storage, processing, and sharing of data. Cloud technology is also called a general term for network technology, information technology, integration technology, management platform technology, application technology, etc. based on the application of cloud computing business model, which can form a resource pool, which is used on demand and is flexible and convenient. As an important support for cloud technology, cloud computing distributes computing tasks on a resource pool composed of a large number of computers, so that various application systems can obtain computing power, storage space, and information services as needed. The basic capability provider of cloud computing will establish a cloud computing resource pool platform, that is, a cloud platform, and deploy various types of virtual resources in the resource pool for external customers to choose to use.

[0032] As cloud computing develops today, cloud vendors provide users with a variety of services, among which network services are a very important part. The characteristic of cloud network services is that users' services need the cooperation of underlying network devices to be implemented. The specific implementation method is to send corresponding service configuration information, also called configuration instructions, to network devices through cloud service controllers. After network devices complete the configuration of their own service networks according to the service configuration information sent by cloud service controllers, they can start to execute network behaviors.

[0033] Figure 1 is a schematic diagram of an exemplary cloud network service configuration scenario, such as Figure 1As shown, in the existing cloud network service configuration scheme, the user selects the required cloud network product through the cloud console and fills in the configuration order. After the cloud console determines the cloud service controller corresponding to the cloud network product, it sends a service request to the cloud service controller. In response to the service request, the cloud service controller generates a business model for the user and stores it in the database, and then converts the generated business model into a configuration model of the corresponding network device, that is, the device model, and sends the configuration model to the network device through the network device interface. After the device takes effect, the creation of the business network is completed. It should be understood that the model mentioned in this application is the relevant business configuration information.

[0034] As cloud computing services expand, more and more network devices are deployed in business systems. The types of devices, manufacturers, and software and hardware versions vary. Services on the cloud are also expanding. In the existing cloud network service configuration solutions, for example Figure 1 In the architecture shown, an abstract model for business services needs to be designed, that is, a set of cloud business controllers needs to be developed. Each cloud business controller needs to be connected to different network devices, including device interfaces, configuration models, etc. When a new business is expanded, the new business controller needs to adapt to the existing network devices; when the network equipment changes, such as replacing the manufacturer or upgrading the software, all dependent business controllers also need to be adapted and upgraded, resulting in the problem of inflexible business expansion.

[0035] To solve the above problems, this application proposes to design a universal network model management service, define a set of standard network models within the service, and provide universal services to upper-layer businesses so that upper-layer businesses no longer need to perceive the differences in underlying devices.

[0036] Figure 2 is a schematic diagram of an exemplary network model management service architecture. Figure 2 As shown, in the general network model management service proposed in the present application, multiple standard network models are constructed, such as VRF (Virtual Routing Forwarding) model, NQA (Network Quality Analyzer) model, IPSEC (Internet Protocol Security) virtual tunnel interface model, ROUTE (routing), BGP (Border Gateway Protocol) peer group model, etc. These network models may have different implementation methods on different network devices, for example, different model combinations may correspond to different network devices, or different network devices may have different APIs (Application Programming Interface).

[0037] From the perspective of network protocols, a standard network model must be able to support various cloud network services and be compatible with various network devices. Therefore, after building a set of standard network models, you can ask the upper-level cloud business controller to use this set of network models as the standard when building business models. You can also use the network model directly, or a combination of multiple network models, or an expansion of the network model, etc. In short, the business model should be created based on the standard network model in the network model management service so that it can be easily converted when it is sent to network devices.

[0038] Figure 3 is a schematic diagram of an exemplary implementation environment proposed in this application, which is a cloud network service configuration system, including a cloud console, a cloud service controller, a network model management server, and network devices. It can be seen that Figure 2 The network model management service of the example is deployed in Figure 3 The example network model management server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms, which are not limited here.

[0039] exist Figure 3 In the example implementation environment, the cloud business controller converts the business model into a standard network model and sends it down through the general API provided by the network model management server to the north. In the network model management server, the standard network model is converted into a differentiated device model through the device model conversion module.

[0040] Exemplarily, specifically, the cloud console generates a network configuration request according to the customer input information, and sends the network configuration request to the cloud service controller.

[0041] The cloud service controller generates an interface call request based on the network configuration request, and sends the interface call request to the network model management server, wherein the interface call request carries associated interface type parameters and model identification parameters.

[0042] The network model management server processes the network model corresponding to the model identification parameter in a processing method that matches the interface type parameter, obtains the business model that matches the network configuration request based on the processed network model, and converts the business model into a device model that is adapted to the network device and sends it to the corresponding network device. It can be seen that this implementation environment simplifies the development complexity of the upper-layer cloud business controller by centralizing the differences between device models in the network model management server for processing. Specifically, the cloud business controller directly connects to the standard network model without identifying the differences between the various underlying network devices. When the network device changes, only the device model conversion module in the network model management server needs to be changed accordingly, and there is no need to change the cloud business controller, thereby greatly improving the flexibility of cloud network service configuration.

[0043] It should also be understood that the network model, business model and device model mentioned in this embodiment can be understood as related business configuration information. For example, the VRF network model is the business configuration information related to virtual routing forwarding. The same is true for other network models. The business model is the business configuration information for connecting to the cloud business controller, and the device model is the business configuration information for connecting to the underlying network device.

[0044] The following is a detailed description of various embodiments of this application:

[0045] First see Figure 4 , Figure 4 is a flowchart of a cloud network service configuration method shown in an exemplary embodiment of the present application. The method can be applied to Figure 3 The implementation environment shown is, for example, Figure 3 The network model management server in the implementation environment shown is specifically executed. Of course, the method can also be applied in other implementation environments and executed by server devices in other implementation environments, and this embodiment does not limit this.

[0046] It should be noted that, regardless of the implementation environment, the execution body of the method predefines multiple standard network models to support the subsequent cloud network service configuration. The definition of the standard network model needs to be compatible with a variety of network devices and a variety of cloud business controllers as much as possible, so try to choose a general description language for definition, such as ProtoBuf (short for Protocol Buffers, an open source cross-platform serialized data structure protocol developed by Google), JSON (JavaScript Object Notation, JS object notation, a lightweight data exchange format), YAML (YAML Ain't Markup Language, a format used to express data serialization) and other types of description languages ​​for definition, which are not limited here.

[0047] Exemplarily, the definition of the standard network model may be implemented according to S310-S320 as shown below:

[0048] S310, generating a plurality of model protocol files, wherein different model protocol files are used to store model definition data of different network models;

[0049] S320, extracting model common definition data from the multiple model protocol files, and storing the model common definition data in a common protocol file, so that the multiple model protocol files and the common protocol file together form the pre-definition of the multiple standard network models in the network model management server.

[0050] In the above example, S310 is understood to define a model protocol file for each network model. If the ProtoBuf file is taken as an example, model protocol files such as Vrf.proto, nqa.proto, route.proto, etc. can be obtained. In addition, in order to reduce repeated definitions, S320 abstracts some common parts of the network model and stores them in public protocol files, such as common.proto files, so that multiple model protocol files and public protocol files together form multiple standard network models pre-defined in the network model management server.

[0051] Exemplarily, S320 extracts model common definition data from multiple model protocol files, and the process of storing the extracted model common definition data in the common protocol file specifically includes: extracting operation type definition data, IP address definition data and routing table item definition data from multiple model protocol files, and storing the extracted operation type definition data, IP address definition data and routing table item definition data in the common protocol file.

[0052] The operation types, IP addresses, and routing table entries mentioned above are all objects reused in the network model. However, it should be noted that the objects reused in the network model are not limited to only these three types. Different actual application scenarios may include different reused objects.

[0053] It can be understood that the operation type represents the operation action corresponding to each delivery of the network model to the network device, which usually includes three types: adding, deleting, and modifying. For example Figure 5 The following diagram shows the definition of an exemplary operation type object. It can be seen that the operation type object includes not only the three operation types of add, delete and modify, but also the invalid type that indicates that the operation is invalid. IP address is used to represent an IP address. This IP address can be an IPV4 (Internet Protocol Version 4) or IPV6 (Internet Protocol Version 6) address, which can be seen everywhere in the network model. Figure 6 This shows the definition of an exemplary IP address object, including the definition of the address version and the address itself. A routing table entry is used to represent a routing information, including the destination IP, the next hop address, etc. For example, Figure 7 The schematic routing table object shows that it uses Figure 6 The IP address object shown.

[0054] like Figure 4 As shown, in an exemplary embodiment, the cloud network service configuration method includes S410-S430, which are described in detail as follows:

[0055] S410, receiving an interface call request from a cloud service controller, wherein the interface call request is initiated by the cloud service controller according to a network configuration request, and the interface call request carries associated interface type parameters and model identification parameters.

[0056] The cloud business controller sends an interface call request to the network model management server, which is initiated by the cloud business server after receiving the network configuration request from the cloud console. It can be understood that the cloud console generates a corresponding network configuration request based on user input information, such as the selection information of the network product, and sends the network configuration request to the cloud business controller.

[0057] The network model management server provides services to the upper-layer cloud business controller through the northbound general API. The main function of the general API is to add, delete, and modify the specified network model, so the general API definition also has these three dimensions.

[0058] Based on these multiple API definition dimensions, the interface call request initiated by the cloud business controller carries associated interface type parameters and model identification parameters. That is, if an interface type parameter and a model identification parameter are regarded as a set of request parameters, the interface call request usually contains multiple sets of request parameters, and in each set of request parameters, the model identification parameter is used to identify the specified network model, and the corresponding interface type parameter is used to identify the processing operation of the specified dimension for the specified network model.

[0059] S420, performing corresponding processing on the network model corresponding to the model identification parameter in accordance with a processing method matching the interface type parameter, and obtaining a service model matching the network configuration request based on the processed network model.

[0060] The network model management server responds to the received interface call request and performs corresponding processing on the network model identified by the model identification parameter associated with the interface type parameter in a processing method that matches the interface type parameter. That is, the specified network model is operated according to the operation dimension specified by the cloud business controller, so as to obtain a business model that matches the network configuration request based on the processed network model.

[0061] Exemplarily, the interface type parameter carried by the interface call request includes at least one parameter of the creation type, deletion type, and update type, and usually includes these three parameters. It can also be understood that the network model management server provides three APIs to the north, namely, the creation type API, the deletion type API, and the update type API. The API definitions are shown in Table 1 below:

[0062] API Main parameters CTATE The network model to be created, including ID and creation parameters DELETE The network model to be deleted, including its ID UPDATE The network model to be updated, including ID and modified parameters

[0063] Table 1

[0064] If the interface type parameter includes a creation type, it means that a specified network model needs to be created. The specified network model is the network model identified by the model identification parameter associated with the interface type parameter of the creation type. Therefore, the specified network model is created on the network model management server. It should be understood that the creation of a network model on the network model management server mentioned in this embodiment refers to the creation of a network model as one of the network units that form a business model, that is, the created network model is included in the business model. It should also be understood that, as shown in Table 1, in addition to the need to pass in a network model identifier (such as the ID of the network model) for a call to a creation type API, it is usually necessary to pass in specific creation parameters so that the network model management server performs new processing of the specified network model according to the creation parameters.

[0065] If the interface type parameter includes a deletion type, it means that the specified network model needs to be deleted. Similarly, the specified network model is the network model identified by the model identification parameter associated with the interface type parameter of the deletion type. When the network model management server performs the corresponding processing operation, it can delete the specified network model. The deletion operation is understood as that the specified network model will not be included in the business model.

[0066] If the interface type parameter includes an update type, it indicates that the specified network model needs to be updated. Similarly, the specified network model is the network model identified by the model identification parameter associated with the interface type parameter of the update type. As shown in Table 1, in addition to the network model identification, the call to the update type API also needs to pass in specific update parameters so that the network model management server can perform model update processing on the specified network model according to the update parameters.

[0067] After executing all the related processing of the interface type parameters and the model identification parameters, the network models obtained in the network model management server are combined to form a business model. It can be seen that the business model obtained in this embodiment can be regarded as converted based on the standard network model, or it can be understood that the business model is constructed based on the standard network model. The conversion or construction method includes but is not limited to the direct use of the network model, the expansion of the network model, and the combination of multiple network models.

[0068] S430: Convert the service model into a device model adapted to the network device and send it to the corresponding network device.

[0069] In this embodiment, a device model conversion program is set up on the network model management server to convert the network model in the business model into a differential device model, so as to obtain a device model adapted to the network device, and then the differential device model is sent to the corresponding network device.

[0070] As can be seen from the above, this embodiment presents a unified model form to the upper-layer cloud business controller by pre-defining multiple standard network models on the network model management server. The cloud business controller directly connects to the standard network model without identifying the differences between various network devices, thereby simplifying the development complexity of the cloud business controller.

[0071] In the cloud network service configuration scheme proposed in this embodiment, when expanding services on the cloud, the new cloud business controller still only needs to connect to the standard network model in the network model management server, without identifying the differences between various network devices. When the network equipment changes, it is only necessary to make corresponding changes to the model conversion method in the network model management server, and there is no need to change the cloud business controller. As a result, the cloud network service configuration scheme proposed in this embodiment has higher business expansion flexibility.

[0072] Figure 8 is based on Figure 4 The embodiment shown is a flowchart of a cloud network service configuration method further proposed. Figure 8 As shown, the process of converting the service model mentioned in S430 into a device model adapted to the network device and then sending it to the corresponding network device includes S810-S820, which are described in detail as follows:

[0073] S810, converting each network model included in the business model into interface call data adapted to the network device, so as to use the obtained set of interface call data as a device model adapted to the corresponding network device.

[0074] In this embodiment, the conversion of the business model to the device model is understood as converting the network model contained in the business model into an API call to a specific network device, including finding the API to be called and generating parameters for the API call. Therefore, it is necessary to convert each network model contained in the business model into interface call data adapted to the network device, and use the obtained set of interface call data as the device model adapted to the corresponding network device.

[0075] As an exemplary implementation, the conversion of the business model to the device model can be directly implemented through code, and a set of conversion codes needs to be developed separately for each device type, where each device type is differentiated by multiple dimensions, such as manufacturer, software and hardware version, etc. This method can certainly achieve the function of model conversion, but it is not flexible enough. If a new device type is added or a network device is upgraded, the code needs to be redeveloped for software upgrade.

[0076] As another exemplary implementation, the conversion of the business model to the device model can be performed by mapping the configuration text. In this implementation, the conversion of each network model included in the business model into interface call data adapted to the network device includes the following process:

[0077] S811, obtaining a preset configuration text;

[0078] S812, based on the mapping rules between the network models and the network device interfaces recorded in the configuration text, map each network model included in the business model into interface call data adapted to the network device.

[0079] The configuration text records the mapping rules between the network model and the network device interface (i.e., the API of the network device). The mapping rules can be in JSON format, and the content consists of attributes and values, so that the network model management server can automatically map according to the JSON definition, which has the advantages of being easy to read and process. When adding or modifying the mapping rules, it is sufficient to modify the configuration text, without the need to repeatedly develop code and upgrade services for the network model management server.

[0080] S820: Call the corresponding network device interface based on the interface call data to send the device model to the corresponding network device.

[0081] As mentioned above, the conversion of the business model to the device model in this embodiment is understood as converting the network model contained in the business model into an API call to a specific network device, including finding the API to be called and generating parameters for the API call. Based on this, it can be seen that the interface call data adapted to the network device includes the network device interface to be called and the call parameters corresponding to the network device interface. Therefore, this embodiment can initiate a call to the corresponding interface of the network device based on the interface call data obtained by the conversion in S810, thereby sending the device model to the corresponding network device.

[0082] It can be seen that this embodiment stores the mapping rules between network models and network device interfaces in the configuration text, and automatically maps each network model contained in the business model to interface call data adapted to the network device based on the configuration text. This is equivalent to proposing an efficient device model conversion module in the network model management server, which can help improve the configuration efficiency of cloud network services.

[0083] In another exemplary embodiment, S812, based on the mapping rules between the network models and the network device interfaces recorded in the configuration text, the process of mapping each network model included in the business model to interface call data adapted to the network device includes the following steps:

[0084] S8121, determining the interface method of each network model included in the business model;

[0085] S8122, based on the corresponding mapping rules recorded in the configuration text, convert the interface methods of each network model into the corresponding network device interface, and obtain the calling parameters of each network device interface.

[0086] It can be understood that this embodiment determines the interface methods corresponding to each network model included in the business model by obtaining the cloud business controller's call to the general API provided by the network model management server to the north. In layman's terms, the cloud business controller's call to the general API provided by the network model management server to the north specifically includes performing three types of operations, namely, adding, deleting, and modifying, on the specified network model. Therefore, for each network model, its interface method includes operating it using one of the above operation types, specifically including interface methods related to the CREATE interface, UPDATE interface, or DELETE interface.

[0087] In this embodiment, based on the corresponding mapping rules recorded in the configuration text, the interface methods of each network model are converted into corresponding network device interfaces, and the process of obtaining the call parameters of each network device interface is called the model mapping process. Model mapping can be divided into at least three cases, in which the first case is that a network model directly corresponds to a set of API interfaces on network devices. In this case, model mapping is implemented as the following process:

[0088] S81221, locate the interface method converter and interface message converter corresponding to each network model in the configuration text, wherein the interface method converter defines the network device interface into which multiple request methods of the corresponding network model are converted, and the interface message converter defines the conversion method of the call message of multiple network device interfaces;

[0089] S81222, based on the interface method converter, convert the interface method of each network model into the corresponding network device interface, and based on the interface message converter, obtain the calling parameters of each network device interface.

[0090] It can be understood that when a network model directly corresponds to an API interface on a group of network devices, both the interface and field conversion are defined by a network model that directly corresponds to an API interface on a group of network devices. Therefore, the corresponding network device interface and the calling parameters of the network device interface are obtained directly through the interface method converter and interface message converter mapping set for the network model in the configuration text.

[0091] Assume that the Vrf model is defined as follows:

[0092]

[0093] Taking the Vrf model as an example, the corresponding relationship between several interface operation modes of the Vrf model and several interfaces of the network device is shown in Table 2 below:

[0094] How to operate the Vrf model Network device interface CREATE CreateVrf() UPDATE UpdateVrf() DELETE DeleteVrf()

[0095] Table 2

[0096] The JSON definition of the interface and field conversion between the Vrf model and the network device in the configuration text is as follows:

[0097]

[0098] Among them, model represents the name of the network model, apiTransformer represents the interface method converter, which internally defines the names of the network device interfaces and interface message converters converted from various request methods, and messageTransformer represents the interface message converter, which internally defines the conversion methods of various call messages of the network device interface.

[0099] In the above example, the message format of the CREATE method and UPDATE method of the Vrf model when calling the network device interface is VrfInfo. The name field in VrfInfo uses the id in the network model, and the description field in VrfInfo uses the description in the network model. The message format of the DELETE method of the Vrf model when calling the network device interface is deleteVrfInfo, which only contains the name field and uses the id in the network model.

[0100] The second case of model mapping is to decide whether to operate one more network device interface based on a specific field in the network model. In this case, model mapping includes the following processes based on the implementation process shown in the first case:

[0101] S81223, obtaining the specified field value contained in the interface method of each network model from the interface call request;

[0102] S81224, if the specified field value indicates that the specified field exists, then based on the corresponding mapping rules recorded in the configuration text, the corresponding interface method is converted to the corresponding network device interface, and the calling parameters of the corresponding network device interface are obtained; if the specified field value indicates that the specified field does not exist, the conversion processing of the corresponding interface method is not performed.

[0103] For example, assume that the VrfRate model is defined as follows:

[0104]

[0105] Taking the VrfRate model as an example, the rate field it contains is of optional type, which indicates that the cloud business controller can choose whether to fill in this field when calling the interface method, and the network model management server can identify whether the caller has filled in the field. If the optional type of modified field is not used, the rate field will be assigned a default value of 0 when it is not filled in. In this way, the network model management server cannot identify whether the business controller wants to set this field to 0 or not fill in this field to indicate that it is not set.

[0106] The conversion of the VrfRate model is first mapped to the Vrf-related methods of the device like the Vrf model, and then decides whether to call the rate-related methods based on whether the rate field is filled in. The JSON code of this mapping method in the configuration file is as follows:

[0107]

[0108]

[0109]

[0110] Compare the conversion JSON of the Vrf model, see the underlined content in the above code ， Converted JSON of VrfRate model exist There is an additional interface call mapping in the CREATE method and the UPDATE method, and it is conditional. It will only be called when the rate field specified in the contains field is included. In the DELETE method, there is also an additional interface call mapping, which is unconditional, because when deleting, VrfRate and the rate field associated with VrfRate will be deleted by default, and it can be executed even if there is no configuration.

[0111] The third case of model mapping is that an array type field is nested inside the network model. The network model allows different operations to be performed on each array element according to the definition of each element in the data. In this case, the model mapping also includes the following process based on the implementation process shown in the first case:

[0112] S81225, determine whether each network model contains an array type field;

[0113] S81226, if the determination is yes, then a predefined internal object is nested in the network device interface obtained by converting the interface method of each network model, wherein the array operation method used by the internal object when executing the call is the same as the model operation method used when the interface method is called.

[0114] It can be understood that in order to support different operations, the network model needs to define an operation type Operation to identify the internal element behavior, as shown in the following code:

[0115]

[0116] Assume that the AclTable model is defined as follows:

[0117]

[0118] It can be seen that the AclTable model contains repeated AclRule objects. AclRule is an internal object and does not exist as an independent network object. It contains Operation objects. When the AclTable model executes the CREATE method operation, the Operation of the internal AclRule can only be CREATE. After the network model management server creates the AclTable model, it will also call the API to create the AclRule object; when the AclTable model executes the DELETE method operation, the Operation of the internal AclRule can only be DELETE. When the network model management server deletes the AclTable model, it will first call the API to delete the AclRule object; when the AclTable model executes the UPDATE method operation, the Operation of the internal AclRule can be CREATE or DELETE. The network model management service creates or deletes the AclRule object according to the Operation object.

[0119] The following is an example of converting JSON to the UPDATE method of the AclTable model:

[0120]

[0121]

[0122]

[0123] It can be seen from the above that the method provided in this embodiment abstracts the conversion between the business model and the device model into three situations, and proposes corresponding JSON conversion codes based on these three situations, so that the model conversion is automatically mapped according to the model mapping rules contained in the JSON conversion code. When adding or modifying the mapping rules, it is only necessary to modify the JSON file in the network model management server, and there is no need to repeatedly develop code or upgrade services on the network model management server, thereby improving the flexibility of business expansion.

[0124] Fig. 91 is a flow chart of a cloud network service configuration method shown in another exemplary embodiment of the present application. The method is applied to a cloud service controller, that is, is specifically executed by the cloud service controller to achieve more flexible cloud network service configuration.

[0125] like Fig. 9 As shown, the method includes S910-S930 as shown below:

[0126] S910, receiving a network configuration request sent by a cloud console;

[0127] S920, generating an interface call request based on the network configuration request, wherein the interface call request carries an associated interface type parameter and a model identification parameter;

[0128] S930, sends the interface call request to the network model management server, so that the network model management server processes the network model corresponding to the model identification parameter in a processing method that matches the interface type parameter, obtains the business model that matches the network configuration request based on the processed network model, and converts the business model into a device model that is adapted to the network device and sends it to the corresponding network device.

[0129] The above process reveals that after receiving the network configuration request from the cloud console, the cloud service server sends an interface call request carrying the associated interface type parameters and model identification parameters to the network model management server. In response to the received interface call request, the network model management server performs operations on the specified network model according to the operation dimensions specified by the cloud service controller, thereby obtaining a business model that matches the network configuration request based on the processed network model, and finally completing the configuration of the cloud network service by converting the network model in the business model into a differentiated device model and sending it to the corresponding network device, and waiting for the device model to take effect in the network device.

[0130] It should be noted that the detailed details involved in the above process have been recorded in the aforementioned embodiments of the network model management server, and will not be repeated in this embodiment.

[0131] Fig.10 The block diagram of a cloud network service configuration device shown in an exemplary embodiment of the present application is configured on a network model management server, and the network model management server predefines a plurality of standard network models.

[0132] like Fig.10 As shown, in an exemplary embodiment, an exemplary cloud network service configuration device 1000 includes:

[0133] The first receiving module 1010 is configured to receive an interface call request from a cloud service controller, wherein the interface call request is initiated by the cloud service controller according to a network configuration request, and the interface call request carries an associated interface type parameter and a model identification parameter;

[0134] The processing module 1020 is configured to process the network model corresponding to the model identification parameter in a processing manner matching the interface type parameter, and obtain a service model matching the network configuration request based on the processed network model;

[0135] The conversion module 1030 is configured to convert the service model into a device model adapted to the network device and then send it to the corresponding network device.

[0136] In another exemplary embodiment, the processing module 1020 is configured to perform the following steps:

[0137] If the interface type parameter includes a creation type, a network model corresponding to the associated model identification parameter is created on the network model management server;

[0138] If the interface type parameter includes a deletion type, the network model corresponding to the associated model identifier is deleted from the network model management server;

[0139] If the interface type parameter includes an update type, the network model corresponding to the associated model identifier is updated;

[0140] The network models obtained from the network model management server are combined to form a business model that matches the network configuration request.

[0141] In another exemplary embodiment, the cloud network service configuration device 1000 further includes a predefined module, and the predefined module is configured to perform the following steps:

[0142] generating a plurality of model protocol files, wherein different model protocol files are used to store model definition data of different network models;

[0143] Model common definition data is extracted from multiple model protocol files, and the model common definition data is stored in the common protocol file, so that multiple standard network models are predefined in the network model management server end by the multiple model protocol files and the common protocol file.

[0144] In another exemplary embodiment, the predefined module is further configured to perform the following steps:

[0145] Extracting operation type definition data, IP address definition data and routing table entry definition data from a plurality of model protocol files;

[0146] The operation type definition data, IP address definition data and routing table entry definition data are stored in the public protocol file as model public definition data.

[0147] In another exemplary embodiment, the conversion module 1030 includes:

[0148] A conversion unit configured to convert each network model included in the business model into interface call data adapted to the network device, so as to use the obtained set of interface call data as a device model adapted to the corresponding network device;

[0149] The calling unit is configured to call the corresponding network device interface based on the interface calling data to send the device model to the corresponding network device.

[0150] In another exemplary embodiment, the conversion unit includes a mapping subunit, which is configured to obtain a preset configuration text and, based on a mapping rule between the network model and the network device interface recorded in the configuration text, map each network model included in the business model into interface call data adapted for the network device.

[0151] In another exemplary embodiment, the interface call data includes the network device interface to be called and the call parameters corresponding to the network device interface; the mapping subunit is further configured to perform the following steps:

[0152] Determine the interface methods of each network model included in the business model;

[0153] Based on the corresponding mapping rules recorded in the configuration text, the interface methods of each network model are converted into the corresponding network device interface, and the calling parameters of each network device interface are obtained.

[0154] In another exemplary embodiment, the mapping subunit is further configured to perform the following steps:

[0155] Locate the interface method converter and interface message converter corresponding to each network model in the configuration text, wherein the interface method converter defines the network device interface into which various request methods of the corresponding network model are converted, and the interface message converter defines the conversion method of the call messages of various network device interfaces;

[0156] The interface methods of each network model are converted into corresponding network device interfaces based on the interface method converter, and the calling parameters of each network device interface are obtained based on the interface message converter.

[0157] In another exemplary embodiment, the mapping subunit is further configured to perform the following steps:

[0158] Obtain the specified field values ​​contained in the interface methods of each network model from the interface call request;

[0159] If the specified field value indicates that the specified field exists, based on the corresponding mapping rule recorded in the configuration text, the corresponding interface method is converted into the corresponding network device interface, and the calling parameters of the corresponding network device interface are obtained;

[0160] If the specified field value indicates that the specified field does not exist, the conversion process of the corresponding interface method will not be performed.

[0161] In another exemplary embodiment, the mapping subunit is further configured to perform the following steps:

[0162] Determine whether each network model contains array type fields;

[0163] If the answer is yes, a predefined internal object is embedded in the network device interface obtained by converting the interface method of each network model, wherein the array operation mode used by the internal object when executing the call is the same as the model operation mode used by the interface method.

[0164] Fig.11 1 is a block diagram of a cloud network service configuration device according to another exemplary embodiment of the present application. The device is configured on a cloud service server to implement flexible configuration of cloud network services.

[0165] like Fig.11 As shown, in an exemplary embodiment, the cloud network service configuration device 1100 includes:

[0166] The second receiving module 1110 is configured to receive a network configuration request sent by the cloud console;

[0167] The generating module 1120 is configured to generate an interface calling request based on the network configuration request, wherein the interface calling request carries an associated interface type parameter and a model identification parameter;

[0168] The sending module 1130 is configured to send the interface call request to the network model management server, so that the network model management server processes the network model corresponding to the model identification parameter in a processing method that matches the interface type parameter, obtains the business model that matches the network configuration request based on the processed network model, and converts the business model into a device model that is adapted to the network device and then sends it to the corresponding network device.

[0169] It should be noted that the cloud network service configuration device provided in the above embodiment and the cloud network service configuration method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs the operation has been described in detail in the method embodiment, and will not be repeated here. In actual application, the cloud network service configuration device provided in the above embodiment can allocate the above functions to different functional modules as needed, that is, divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0170] An embodiment of the present application also provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements the cloud network service configuration method provided in the above-mentioned embodiments.

[0171] Fig.12 The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Fig.12 The computer system 1200 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0172] like Fig.12 As shown, the computer system 1200 includes a central processing unit (CPU) 1201, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1202 or the program loaded from the storage part 1208 to the random access memory (RAM) 1203, such as executing the method described in the above embodiment. In the RAM 1203, various programs and data required for system operation are also stored. The CPU 1201, the ROM 1202 and the RAM 1203 are connected to each other through the bus 1204. The input / output (I / O) interface 1205 is also connected to the bus 1204.

[0173] The following components are connected to the I / O interface 1205: an input section 1206 including a keyboard, a mouse, etc.; an output section 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as needed so that a computer program read therefrom is installed into the storage section 1208 as needed.

[0174] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1209, and / or installed from a removable medium 1211. When the computer program is executed by a central processing unit (CPU) 1201, various functions defined in the system of the present application are executed.

[0175] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. The computer program contained in the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0176] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0177] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not constitute limitations on the units themselves in some cases.

[0178] Another aspect of the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the cloud network service configuration method as described above when the computer program is executed by a processor. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.

[0179] Another aspect of the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the cloud network service configuration method provided in each of the above embodiments.

[0180] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. A person skilled in the art can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.

[0181] It should also be noted that in the specific implementation of this application, data related to interface calls, network configurations, model conversions, etc. are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

Claims

1. A cloud network service configuration method, characterized in that: Applied to a network model management server, the network model management server pre-defines a plurality of standard network models; the method comprises: Receiving an interface call request from a cloud service controller, wherein the interface call request is initiated by the cloud service controller according to a network configuration request, and the interface call request carries an associated interface type parameter and a model identification parameter; Processing the network model corresponding to the model identification parameter in a processing manner matching the interface type parameter, and obtaining a service model matching the network configuration request based on the processed network model; The business model is converted into a device model adapted to the network device and then sent to the corresponding network device.

2. The method according to claim 1, characterized in that: The processing of the network model corresponding to the model identification parameter in a processing manner matching the interface type parameter, and obtaining a service model matching the network configuration request based on the processed network model, includes: If the interface type parameter includes a creation type, creating a network model corresponding to the associated model identification parameter on the network model management server; If the interface type parameter includes a deletion type, the network model corresponding to the associated model identifier is deleted from the network model management server; If the interface type parameter includes an update type, the network model corresponding to the associated model identifier is updated; The network models obtained from the network model management server are combined to form a business model that matches the network configuration request.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: generating a plurality of model protocol files, wherein different model protocol files are used to store model definition data of different network models; Model common definition data is extracted from the multiple model protocol files, and the model common definition data is stored in the common protocol file, so that the multiple model protocol files and the common protocol file together form the pre-definition of the multiple standard network models in the network model management server.

4. The method according to claim 3, characterized in that: The extracting the model common definition data from the plurality of model protocol files and storing the model common definition data in the common protocol file comprises: extracting operation type definition data, IP address definition data, and routing table entry definition data from the plurality of model protocol files; The operation type definition data, the IP address definition data, and the routing table entry definition data are stored in the common protocol file as the model common definition data.

5. The method according to claim 1 or 2, characterized in that: The converting the service model into a device model adapted to the network device and then sending it to the corresponding network device includes: Converting each network model included in the business model into interface call data adapted to the network device, so as to use the obtained set of interface call data as a device model adapted to the corresponding network device; The corresponding network device interface is called based on the interface calling data to send the device model to the corresponding network device.

6. The method according to claim 5, characterized in that The converting each network model included in the business model into interface call data adapted to the network device includes: Get the preset configuration text; Based on the mapping rules between the network models and the network device interfaces recorded in the configuration text, each network model included in the business model is mapped into interface call data adapted to the network device.

7. The method according to claim 6, characterized in that The interface call data includes the network device interface to be called and the call parameters corresponding to the network device interface; the mapping rule between the network model and the network device interface recorded in the configuration text, mapping each network model included in the business model to the interface call data adapted to the network device, includes: Determine the interface method of each network model included in the business model; Based on the corresponding mapping rules recorded in the configuration text, the interface methods of each network model are converted into corresponding network device interfaces, and the calling parameters of each network device interface are obtained.

8. The method according to claim 7, characterized in that The method of converting the interface method of each network model into the corresponding network device interface based on the corresponding mapping rules recorded in the configuration text, and obtaining the calling parameters of each network device interface, includes: Locate the interface method converter and interface message converter corresponding to each network model in the configuration text, wherein the interface method converter defines the network device interface into which multiple request methods of the corresponding network model are converted, and the interface message converter defines the conversion method of the call message of multiple network device interfaces; Based on the interface method converter, the interface method of each network model is converted into a corresponding network device interface, and based on the interface message converter, the calling parameters of each network device interface are obtained.

9. The method according to claim 7, characterized in that: The method further comprises: Obtaining the specified field value contained in the interface method of each network model from the interface call request; If the specified field value indicates that the specified field exists, based on the corresponding mapping rule recorded in the configuration text, the corresponding interface method is converted into a corresponding network device interface, and the calling parameters of the corresponding network device interface are obtained; If the specified field value indicates that the specified field does not exist, the conversion process of the corresponding interface method is not performed.

10. The method according to claim 7, characterized in that The method further comprises: Determine whether each network model contains array type fields; If the answer is yes, a predefined internal object is embedded in the network device interface obtained by converting the interface method of each network model, wherein the array operation mode used by the internal object when executing the call is the same as the model operation mode used by the interface method.

11. A cloud network service configuration method, characterized in that: Applied to a cloud service controller, the method comprises: Receive network configuration requests sent by the cloud console; Generate an interface call request based on the network configuration request, wherein the interface call request carries an associated interface type parameter and a model identification parameter; The interface call request is sent to the network model management server, so that the network model management server processes the network model corresponding to the model identification parameter in a processing method that matches the interface type parameter, obtains a business model that matches the network configuration request based on the processed network model, and converts the business model into a device model that is adapted to the network device and then sends it to the corresponding network device.

12. A cloud network service configuration system, characterized in that: It includes cloud console, cloud business controller, network model management server and network equipment, including: The cloud console generates a network configuration request according to the customer input information, and sends the network configuration request to the cloud service controller; The cloud service controller generates an interface call request based on the network configuration request, and sends the interface call request to the network model management server, wherein the interface call request carries associated interface type parameters and model identification parameters; The network model management server processes the network model corresponding to the model identification parameter in a processing method that matches the interface type parameter, obtains a business model that matches the network configuration request based on the processed network model, and converts the business model into a device model that is adapted to the network device and then sends it to the corresponding network device.

13. A cloud network service configuration device, characterized in that: The device is configured on a network model management server, wherein the network model management server predefines a plurality of standard network models; the device comprises: A first receiving module is configured to receive an interface call request from a cloud service controller, wherein the interface call request is initiated by the cloud service controller according to a network configuration request, and the interface call request carries an associated interface type parameter and a model identification parameter; a processing module configured to process the network model corresponding to the model identification parameter in a processing manner matching the interface type parameter, and obtain a service model matching the network configuration request based on the processed network model; The conversion module is configured to convert the business model into a device model adapted to the network device and then send it to the corresponding network device.

14. An electronic device, characterized in that: include: one or more processors; A memory for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the cloud network service configuration method as described in any one of claims 1 to 11.

15. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the cloud network service configuration method described in any one of claims 1 to 11.

Images