SDN (Software Defined Network) service configuration method and device, electronic equipment, storage medium and program product
By building an intent repository and using target intent information to find matching SDN service configuration solutions, the accuracy risks brought about by machine learning in SDN service configuration are resolved, and an efficient and reliable configuration process is achieved.
Patent Information
- Application Number
- CN202511774582.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-28
- Publication Date
- 2026-02-13
AI Technical Summary
In existing SDN service configurations, relying on machine learning to generate network and resource configuration schemes poses an accuracy risk, leading to problems such as configuration errors and security attacks, and also incurring high operation and maintenance costs.
By pre-building an intent repository to store intents and their matching business configuration schemes, and using the target intent information to find matching configuration schemes from the repository, the biases introduced by machine learning are avoided, thus achieving accurate SDN business configuration.
It reduces the risk of configuration errors and security attacks, lowers operation and maintenance costs, and improves the success rate and accuracy of configuration distribution.
Smart Images
Figure CN121530853A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present disclosure relates to the technical field of network, and particularly relates to an SDN service configuration method and device, electronic equipment, storage medium and program product. BACKGROUND
[0002] In the prior art, in order to reduce the difficulty of North Bound Interface (NBI) configuration operation in Software Defined Network (SDN) service configuration, the concept of Intent-Based Networking (IBN) is combined with SDN, and only the input of service intent can realize NBI configuration, that is, the association between service intent and NBI configuration needs to be established. The existing association between service intent and NBI configuration is mostly realized by machine learning.
[0003] However, the accuracy of machine learning needs to be considered. Even the current GPT and other AI large models sometimes produce different results that are contradictory. SDN service configuration should be rigorous and reliable, and completely relying on machine learning to generate network and resource configuration scheme has certain application risks. SUMMARY
[0004] In view of the above technical problems, the present disclosure provides an SDN service configuration method, device, electronic equipment, storage medium and program product.
[0005] In a first aspect, the present disclosure provides an SDN service configuration method, comprising: receiving target intent information; based on the target intent information, obtaining a target SDN service configuration scheme matched with the target intent information from a pre-constructed intent repository; sending the target SDN service configuration scheme to an Application Program Interface (API) server, so that the API server completes the target SDN service configuration based on the target SDN service configuration scheme.
[0006] In addition, according to the method of the first aspect of the present disclosure, based on the target intent information, the target SDN service configuration scheme matched with the target intent information is obtained from the pre-constructed intent repository, comprising: based on the target intent information, obtaining an intent coordinate related to the target intent information from the pre-constructed intent repository, the intent coordinate and the SDN service configuration scheme in the intent repository have a one-to-one mapping relationship; based on the target intent information and the intent coordinate related to the target intent information, obtaining a target intent coordinate corresponding to the target SDN service; Based on the target intention coordinate, the target SDN service configuration scheme matching the target intention information is obtained from the intention warehouse.
[0007] In addition, according to the method of the first aspect of the present disclosure, the intention warehouse is constructed by the SDN user equipment in the following way: Based on the intention of the plurality of SDN services, a plurality of NBI call requests matching the intention of each SDN service are obtained; Based on the plurality of NBI call requests corresponding to each SDN service, an SDN service configuration scheme corresponding to each SDN service is obtained; Based on each SDN service configuration scheme, an intention coordinate matching the same is constructed; The intention coordinate of each SDN service is bound with the SDN service configuration scheme to obtain an intention item corresponding to each SDN service; Based on the intention item corresponding to each SDN service, the construction of the intention warehouse is completed.
[0008] In addition, according to the method of the first aspect of the present disclosure, the intention warehouse is constructed by the following way: The log data of the NBI call request is obtained; Based on the log data, a plurality of NBI call requests corresponding to each SDN service are obtained; Based on the plurality of NBI call requests corresponding to each SDN service, an SDN service configuration scheme corresponding to each SDN service is obtained; Based on each SDN service configuration scheme, an intention coordinate matching the same is constructed; The intention coordinate of each SDN service is bound with the SDN service configuration scheme to obtain an intention item corresponding to each SDN service; Based on the intention item corresponding to each SDN service, the construction of the intention warehouse is completed.
[0009] In addition, according to the method of the first aspect of the present disclosure, based on the intention item corresponding to each SDN service, the construction of the intention warehouse is completed, which includes: The legality of each NBI call request in the intention item corresponding to each SDN service is verified; After the legality of all NBI call requests is verified and the SDN service is successfully constructed, the intention item corresponding to the SDN service that passes the verification is integrated and included in the intention warehouse.
[0010] In addition, according to the method of the first aspect of the present disclosure, the intention coordinate is constructed based on the SDN service type, the SDN service resource operation behavior and the SDN service configuration parameter.
[0011] The second aspect, the present disclosure provides an SDN service configuration device, comprising: The receiving module is configured to receive target intent information of a target SDN service. The obtaining module is configured to obtain, based on the target intent information, a target SDN service configuration scheme matched with the target intent information from a pre-constructed intent repository. The configuration module is configured to send the target SDN service configuration scheme to an application program interface (API) server, so that the API server completes target SDN service configuration based on the target SDN service configuration scheme.
[0012] In a third aspect, the present disclosure provides an electronic device, comprising a memory configured to store computer readable instructions, and a processor configured to execute the computer readable instructions, so that the electronic device performs the method according to any one of the embodiments of the first aspect.
[0013] In a fourth aspect, the present disclosure provides a non-transitory computer readable storage medium configured to store computer readable instructions, which, when executed by a processor, cause the processor to perform the method according to any one of the embodiments of the first aspect.
[0014] In a fifth aspect, the present disclosure provides a computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of the embodiments of the first aspect.
[0015] The present disclosure provides an SDN service configuration method, device, electronic device, storage medium and program product. The present disclosure pre-constructs an intent repository, which stores a plurality of intents and their matched service configuration schemes. The target intent information is used to find a target SDN service configuration scheme matched with the target SDN service from the intent repository, so as to realize target SDN service configuration. Compared with relying on a machine learning model to generate a configuration scheme, the present disclosure can avoid the deviation caused by machine learning, avoid configuration errors and security attacks caused by misuse of intent input, reduce the error correction and operation and maintenance costs of the system, and improve the success rate of configuration delivery.
[0016] It is to be understood that both the foregoing general description and the following detailed description are exemplary, and are intended to provide further explanation of the subject technology. BRIEF DESCRIPTION OF DRAWINGS
[0017] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which like reference characters refer to like elements in the several views. The accompanying drawings are used to provide further understanding of the present disclosure, and constitute a part of the specification, together with the present disclosure, serve to explain the present disclosure, and do not constitute a limitation on the present disclosure. In the drawings, the same reference numerals generally refer to the same parts or steps.
[0018] Figure 1 An architecture diagram of an SDN service configuration system provided by an embodiment of the present disclosure is shown in FIG. 1. Figure 2 A flowchart of an SDN service configuration method provided by an embodiment of the present disclosure is shown in FIG. 2. Figure 3 A flowchart of another SDN service configuration method provided by an embodiment of the present disclosure is shown in FIG. 3. Figure 4 A flowchart of another SDN service configuration method provided by an embodiment of the present disclosure is shown in FIG. 4. Figure 5 A flowchart of another SDN service configuration method provided by an embodiment of the present disclosure is shown in FIG. 5. Figure 6 A flowchart of an intent repository construction method provided by an embodiment of the present disclosure is shown in FIG. 6.
[0019] Figure 7 A flowchart of another intent repository construction method provided by an embodiment of the present disclosure is shown in FIG. 7.
[0020] Figure 8 A flowchart of another SDN service configuration method provided by an embodiment of the present disclosure is shown in FIG. 8.
[0021] Figure 9 A structural block diagram of an SDN service configuration apparatus provided by an embodiment of the present disclosure is shown in FIG. 9. Figure 10 A hardware block diagram of an electronic device provided by an embodiment of the present disclosure is shown in FIG. 10. Figure 11 A schematic diagram of a computer readable storage medium provided by an embodiment of the present disclosure is shown in FIG. 11. DETAILED DESCRIPTION
[0022] In order to make the objectives, technical solutions and advantages of the present disclosure more apparent, the following will describe the example embodiments according to the present disclosure in detail with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all the embodiments of the present disclosure, and it should be understood that the present disclosure is not limited by the example embodiments described herein.
[0023] Figure 1 An architecture diagram of an SDN service configuration system provided by an embodiment of the present disclosure is shown in FIG. 1. Figure 1 As shown in FIG. 1, the SDN service configuration system at least includes an intent repository module 101, an SDN control module 102, an API service module 103 and a log module 104.
[0024] An intent repository module 101 is configured to manage and store all verified published intents, each of which is composed of intent coordinates (IC) and a specific SDN service configuration scheme pointed to. The intent repository (IR) module 101 can provide the SDN user with an intent scheme selection of the SDN service configuration, and the SDN user can also contribute a customized intent solution to the intent repository module 101.
[0025] An SDN control module 102 is configured to receive and process an intent request of the SDN user. The SDN user submits the selected IC matching the intent request to the SDN control module 102, and the SDN control module 102 can obtain the corresponding SDN service configuration scheme from the intent repository module 101 according to the IC, and call the NBI provided by the API service module 103 according to the details of the SDN service configuration scheme, so as to complete the SDN service configuration. The SDN control module 102 can be an SDN controller.
[0026] An API service module 103 is configured to provide a northbound interface (NBI) capability. The API service module 103 can receive a NBI request called by the SDN user or the SDN controller, and complete the SDN resource configuration and network configuration delivery. The API service module 103 can be an application interface (API) server.
[0027] A log module 104 is configured to record log data of all NBI calling requests of the API service module 103. The log data can be collected and calculated by the SDN control module 102, and then can be integrated and extracted as a standardized intent, which is published to the intent repository module 101 by the SDN control module 102 for selection by the SDN user.
[0028] Further, the SDN service configuration system further includes an intent repository maintenance module 105, a user module 106 and an SDN management module 107.
[0029] The intent repository maintenance module 105 is configured to verify the legality of the intent, and only the intent verified as legal can be managed and stored by the intent repository module 101.
[0030] The user module 106 is configured to receive an intent request input by the SDN user, and send the intent request to the SDN control module 102.
[0031] The SDN management module 107 is configured to manage and display the SDN service configuration.
[0032] Figure 1 The various modules of the SDN service configuration system are only exemplary, and the specific configuration of the modules included in the SDN service configuration system can be adjusted according to the actual needs of the SDN service configuration, which is not limited in the present disclosure.
[0033] Figure 2 A flowchart of an SDN service configuration method provided by an embodiment of the present disclosure.
[0034] As shown in Figure 2 , the SDN service configuration method can be executed by an SDN controller, and specifically includes the following steps. Step 201, receiving target intent information.
[0035] In an embodiment of the present disclosure, the target intent information is a "result-oriented service requirement" corresponding to a target SDN service that needs to be configured with network resources. After the target intent information is input by an SDN user through a human-computer interface (such as a user module 106 as shown in Figure 1 , the SDN controller receives and subsequently converts it into specific network configuration.
[0036] Step 202, based on the target intent information, obtaining a target SDN service configuration scheme matching the target intent information from a pre-constructed intent repository.
[0037] In an embodiment of the present disclosure, the intent repository refers to a pre-constructed SDN service configuration scheme corresponding to the intent requirements of a variety of SDN services. The target SDN service configuration scheme is a set of directly executable SDN network configuration details that can meet the target intent information. After receiving the target intent information, the SDN controller obtains the target SDN service configuration scheme matching the target intent information from the pre-constructed intent repository according to the target intent information.
[0038] Step 203, sending the target SDN service configuration scheme to an application program interface (API) server, so that the API server completes the target SDN service configuration based on the target SDN service configuration scheme.
[0039] In an embodiment of the present disclosure, after obtaining the target SDN service configuration scheme matching the target intent information, the SDN controller sends the target SDN service configuration scheme to the API server. The API server generates network configuration corresponding to the target SDN service according to the received target SDN service configuration scheme, and completes the target SDN service configuration.
[0040] To sum up, according to the technical scheme provided by the embodiment of the present disclosure, the present disclosure pre-constructs an intent warehouse, the intent warehouse stores a plurality of intents and matching business configuration schemes, and a target SDN business configuration scheme matching a target SDN business is found from the intent warehouse through target intent information, so as to realize target SDN business configuration. Compared with relying on a machine learning model to generate a configuration scheme, the present disclosure can avoid the deviation caused by machine learning, avoid configuration errors and security attacks caused by misuse of intent input, reduce the error correction and operation and maintenance cost of the system, and improve the success rate of configuration delivery.
[0041] Figure 3 A flowchart of another SDN business configuration method provided by an embodiment of the present disclosure is shown.
[0042] As shown in Figure 3 , based on the target intent information, a target SDN business configuration scheme matching the target intent information is obtained from the pre-constructed intent warehouse, which specifically includes the following steps: Step 301, based on the target intent information, an intent coordinate related to the target intent information is obtained from the pre-constructed intent warehouse, and the intent coordinate and the SDN business configuration scheme in the intent warehouse have a one-to-one mapping relationship.
[0043] In an embodiment of the present disclosure, the intent coordinate is constructed based on the SDN business type, the SDN business resource operation behavior, and the SDN business configuration parameter. It is used to represent the specific implementation of the SDN business intent. Among them, the SDN business type refers to the essential classification of the business, such as VPC creation, creation of peer connection interworking, creation of public network, bandwidth adjustment, security isolation, or cross-domain interconnection, etc. The SDN business resource operation behavior refers to the specific operation action of the user on the SDN business resource, such as “create”, “modify”, “delete”, “expand”, “shrink”, etc. The SDN business configuration parameter refers to the specific technical index of the SDN business, such as the network segment of VPC, the bandwidth size, etc.
[0044] Specifically, the SDN business type, the SDN business resource operation behavior, and the SDN business configuration parameter are combined to generate the intent coordinate. The intent warehouse stores various common “intent coordinates” in advance, each intent coordinate is bound to a fixed set of SDN configuration schemes (such as configuration of bandwidth adjustment, route optimization, etc.), forming a one-to-one mapping relationship between the intent coordinate and the SDN business configuration scheme in the intent warehouse. After receiving the target intent information, the SDN controller finds a series of intent coordinates related to the target intent information from the pre-constructed intent warehouse according to the target intent information.
[0045] Exemplarily, for the SDN business such as creating VPC, according to the intent of “creating VPC”, the intent coordinate thereof is constructed as follows:
[0046] Wherein: is a fixed prefix identifier, represents a VPC service, representing an SDN service type, represents a service resource creation behavior (i.e. the aforementioned SDN service resource operation behavior), is a reserved default network segment and the information of the available zone to which it belongs, i.e. the aforementioned "SDN service configuration parameter". The following is a specific IC example:
[0047] By analyzing the aforementioned intent coordinates, it can be identified that a VPC service is created, which contains a Subnet with cidr of 192.168.1.0 / 24 and az of AZ_TC.
[0048] In actual application, after the SDN controller receives the target intent information, it pulls a series of intent coordinates related to the target intent information from the intent repository according to the target intent information. Specifically, it can support pulling intent coordinates IC under certain conditions, for example, if the target intent information involves VPC operation related, then according to the SDN service type (such as ) in the intent coordinates, it pulls related IC. The following is an example of IC pulling:
[0049] Wherein, IC_1, IC_2 and IC_3 represent the serial numbers of the intent coordinates under the relative specific conditions, and the serial numbers The corresponding IC represents creating service, The corresponding IC represents deleting service, The corresponding IC represents displaying service detail information, including all resource information in it. There are generally more than one intent related to "VPC" in the intent repository, which contains three intent coordinates of creating, deleting and querying. If there are 4, 5, etc., there will also be IC_4, IC_5, etc., which only represent a certain intent coordinate (i.e. a certain IC).
[0050] Step 302, based on the target intent information and the intent coordinates related to the target intent information, the target intent coordinates corresponding to the target SDN service are obtained.
[0051] In one embodiment of the present disclosure, after the SDN controller pulls a series of intent coordinates related to the target intent information from the intent warehouse and presents them to the SDN user, the SDN user, in combination with the specific needs of the target intent information, filters the target intent coordinates corresponding to the target SDN service from the series of intent coordinates, and then feeds the target intent coordinates back to the SDN controller, so that the SDN controller obtains the target intent coordinates corresponding to the target SDN service.
[0052] Illustratively, a series of intent coordinates have been pulled in step 301 above, based on which the user only needs to select an IC consistent with the service configuration requirements from the series of intent coordinates. For example, an IC for deleting a service intent is selected, and an example is as follows:
[0053] Step 303: Based on the target intent coordinates, obtain the target SDN service configuration scheme matching the target intent information from the intent warehouse.
[0054] In one embodiment of the present disclosure, after the target intent coordinates are determined, the target SDN service configuration scheme matching the target intent information is pulled from the intent warehouse according to the target intent coordinates.
[0055] Illustratively, the SDN controller is the core that receives and processes the intent information. Since each intent coordinate can uniquely point to the SDN service configuration scheme in the intent warehouse, after the target intent coordinates are obtained, the SDN controller can pull the corresponding SDN service configuration scheme from the intent warehouse according to the target intent coordinates. For example, the target intent coordinates pointed to by the example in step 302 are for deleting a service, and the corresponding service configuration scheme is as follows:
[0056] Delete as above Operation, in order, includes deleting , unbinding , deleting , deleting , deleting , deleting , and a series of NBI operations.
[0057] In summary, according to the technical scheme provided by the embodiment of the present disclosure, the present disclosure proposes and constructs an intent warehouse (for storing a one-to-one mapping relationship between intent coordinates and SDN service configuration schemes), pulls relevant intent coordinates through target intent information, determines a target intent coordinate from the pulled relevant intent coordinates in combination with specific requirements of the target intent information, and calls a matching configuration scheme from the intent warehouse through the target intent coordinate, so that the user can automatically and accurately obtain a required SDN service configuration scheme by only inputting intent information, without manually editing or writing a bottom configuration, and the efficiency, accuracy and intelligent level of the SDN service configuration are greatly improved.
[0058] Optionally, when there is no intent meeting the user service configuration requirement in the pulled IC, the intent can also be customized.
[0059] Figure 4 A flowchart of another SDN service configuration method provided by the embodiment of the present disclosure.
[0060] As shown in Figure 4 , the intent warehouse is constructed by the SDN user equipment in the following manner: Step 401, based on the intents of multiple SDN services, obtaining multiple NBI call requests matching the intent of each SDN service.
[0061] In an embodiment of the present disclosure, the NBI call request is an "instruction" triggering the northbound interface of the SDN controller to perform an operation. The SDN user collects the intents of multiple SDN services (such as "creating a VPC", "adjusting bandwidth", "deleting a subnet") through the SDN user equipment, obtains the corresponding NBI call request according to the intent requirements of each intent, and finally obtains multiple NBI requests matching the intents of respective services.
[0062] Specifically, the specific requirements of each SDN service intent usually need a series of NBI call requests to be combined to be implemented. For example: creating a VPC contains a series of NBI call requests related to SDN resources, such as creating a VPC , creating a subnet , creating a route table , creating a route , binding a security group , and the specific configuration order is as follows:
[0063] Step 402, based on the multiple NBI call requests corresponding to each SDN service, obtaining an SDN service configuration scheme corresponding to each SDN service.
[0064] In one embodiment of the present disclosure, the multiple NBI call requests corresponding to each SDN service are integrated, and a complete SDN service configuration scheme that can realize the intention requirement of the SDN service is finally generated.
[0065] Specifically, the multiple NBI call requests in step 402 are combined as a whole transaction, which can be regarded as a complete intention scheme (i.e., the SDN service configuration scheme).
[0066] In step 403, an intention coordinate matched with each SDN service configuration scheme is constructed.
[0067] In one embodiment of the present disclosure, for each complete SDN service configuration scheme, a dedicated "intention coordinate" is created, which is the unique identifier of the SDN service intention corresponding to the SDN service configuration scheme, and the corresponding configuration scheme can be quickly associated through the intention coordinate in the future.
[0068] Specifically, the construction method of the intention coordinate can refer to step 301.
[0069] In step 404, the intention coordinate of each SDN service is bound with the SDN service configuration scheme, and the intention item corresponding to each SDN service is obtained.
[0070] In one embodiment of the present disclosure, the "intention coordinate" of each SDN service and the corresponding "SDN service configuration scheme" are associated and bound to form a complete unit (i.e., "intention item") containing "identifier + implementation scheme", so as to quickly locate and call the configuration scheme through the intention coordinate in the future.
[0071] In step 405, the construction of the intention warehouse is completed based on the intention item corresponding to each SDN service.
[0072] In one embodiment of the present disclosure, the intention items of multiple SDN services (each intention item contains the bound intention coordinate and configuration scheme) are integrated and stored, and a complete and queryable "intention warehouse" is finally formed, which serves as the basic database for subsequent intention-driven configuration.
[0073] In actual application, if the SDN service configuration scheme is not familiar, various intentions in the IR and the corresponding SDN service configuration scheme implementation can be accessed for reference or direct secondary configuration based thereon to generate own intention.
[0074] Specifically, the A user is familiar with the SDN service, and completes the service intention construction of "creating a VPC" according to the steps (step 1-step 5) listed in step 401, and submits the constructed intention item to the intention repository IR, which is collected by the IR. The B user also has the service intention demand of "creating a VPC", but the B user is not familiar with how to arrange the service, so the B user can search the intention of "creating a VPC" from the intention repository IR, and after searching, the B user can directly obtain the existing intention of "creating a VPC" from the IR, because the intention matches the service demand of the B user, so the B user can directly use the intention. That is, even if the B user is not familiar with the service arrangement of "creating a VPC", as long as the intention repository IR collects the intention of "creating a VPC", the B user can use it directly to complete the service configuration, and reduces the use threshold of the service call.
[0075] In summary, according to the technical scheme provided by the embodiment of the present disclosure, the present disclosure collects the intentions of multiple SDN services, obtains multiple NBI call requests matched with each SDN service intention through the multiple SDN service intentions, integrates the multiple NBI call requests matched with each SDN service intention into one SDN service configuration scheme, constructs an intention coordinate for each SDN service configuration scheme, and binds the intention coordinate and the SDN service configuration scheme into an intention item, thereby integrating into an intention repository, forming a complete intention repository construction method. The above intention repository construction method integrates scattered NBI call requests into a structured configuration scheme, and binds a unique intention coordinate, so as to convert a complex service configuration into a simple mode of "coordinate identifier + scheme call", reduces the manual operation cost, and by means of the sharing mechanism of the intention repository, a user who is not familiar with the underlying configuration can directly reuse the existing intention item in the repository without needing to master specific arrangement logic, and realizes the mode of taking it directly. The intention repository centrally manages the mapping of intention demands and schemes of various services, avoids repeated design of configuration schemes, simultaneously ensures the consistency of configuration logic through standardized coordinates, and reduces human errors.
[0076] Figure 5 A flowchart of another SDN service configuration method provided by an embodiment of the present disclosure.
[0077] As shown in Figure 5 The intention repository is constructed in the following manner: Step 501, obtaining log data of NBI call requests.
[0078] In an embodiment of the present disclosure, log data related to NBI call requests in an SDN system is collected or extracted, and the log data records the key information of the whole flow of the NBI call.
[0079] For example, log data records information describing SDN business behavior, such as the type of resource request operation and configuration parameters. For instance:
[0080] Step 502: Based on log data, obtain multiple NBI call requests corresponding to each SDN service.
[0081] In one embodiment of this disclosure, log data is filtered and categorized according to the SDN service dimension to extract all relevant NBI call requests corresponding to each SDN service and establish a correspondence between "service" and "call request".
[0082] For example, NBI call requests can be marked and collected by recording the number of requests and setting a request count threshold, and then selected as the intent for orchestration of a specific SDN service. Specifically, NBI call requests that have reached the request count threshold are marked and collected, and temporarily stored in a set of NBI call requests for a specific SDN service. For example, an NBI call request set can be created, which gathers all the NBI call requests required for creation.
[0083] Step 503: Based on multiple NBI call requests corresponding to each SDN service, obtain the SDN service configuration scheme corresponding to each SDN service.
[0084] In one embodiment of this disclosure, when multiple NBI call requests required by a certain SDN service have been collected, the multiple NBI call requests can be sequentially integrated according to the configuration order of the SDN service corresponding to the multiple NBI call requests. The content formed after integration is the SDN service configuration scheme corresponding to the SDN service.
[0085] For example, based on the set of business NBI call requests in step 502, such as creating an NBI call request set, when the set contains all the NBI call requests required by the business, these NBI call requests are integrated according to the SDN business configuration order indicated by the set, and the integration result is regarded as a whole transaction and extracted into a complete and standardized intent scheme (i.e., SDN business configuration scheme).
[0086] Step 504: Based on each SDN service configuration scheme, construct the intent coordinates that match it.
[0087] In one embodiment of this disclosure, a unique "intent coordinate" is created for each complete SDN service configuration scheme. This intent coordinate is a unique identifier of the SDN service intent corresponding to the SDN service configuration scheme, and the corresponding configuration scheme can be quickly associated with the intent coordinate in the future.
[0088] Specifically, the method for constructing the intent coordinates can be referred to in step 301.
[0089] Step 505: Bind the intent coordinates of each SDN service to the SDN service configuration scheme to obtain the intent item corresponding to each SDN service.
[0090] In one embodiment of this disclosure, the "intent coordinates" of each SDN service are associated and bound with the corresponding "SDN service configuration scheme" to form a complete unit (i.e., "intent item") containing "identifier + implementation scheme", so that the configuration scheme can be quickly located and invoked through the intent coordinates in the future.
[0091] Step 506: Based on the intent items corresponding to each SDN service, complete the construction of the intent repository.
[0092] In one embodiment of this disclosure, intent items from multiple SDN services (each intent item contains bound intent coordinates and configuration schemes) are integrated and stored to form a complete, queryable "intent repository" as the base database for subsequent intent-driven configuration.
[0093] In summary, according to the technical solution provided in the embodiments of this disclosure, this disclosure achieves intent warehouse construction through log data mining, eliminating the need for manual orchestration of NBI call requests and configuration schemes. By mining existing NBI call request logs, it automatically categorizes businesses, integrates configuration logic, and generates intent items, significantly reducing the manual cost and threshold of warehouse construction. Furthermore, by extracting configuration schemes based on real business logs, it ensures that the intent items in the intent warehouse are highly consistent with actual business scenarios, while continuously incorporating new business types and gradually enriching the coverage of the warehouse. In addition, by using rules such as "request count threshold filtering" and "integration by configuration order," high-frequency and complete business configuration logic is selected, avoiding invalid or fragmented schemes from being included in the warehouse. At the same time, the standardized integration process reduces errors from manual orchestration, and the constructed intent warehouse can be directly reused by subsequent users. Users unfamiliar with the underlying configuration do not need to design from scratch and can directly call the configuration schemes extracted from real logs in the warehouse, improving business configuration efficiency.
[0094] Furthermore, based on the intent items corresponding to each SDN service, the intent repository is constructed, including: Perform legality verification on each NBI call request in the intent item corresponding to each SDN service. Once all NBI call requests have passed the validity verification and the SDN service has been successfully built, the intent items corresponding to the verified SDN services will be integrated and included in the intent repository.
[0095] Specifically, the SDN controller or SDN user equipment submits the intent items corresponding to each SDN service to the intent repository. The intent repository maintenance module (which can consist of the intent repository's technical team or an automation platform, and is not disclosed here) verifies the legitimacy of each NBI call request in the intent item corresponding to each SDN service. Once all NBI call requests pass legitimacy verification and the SDN service is successfully constructed through the API interface server, the intent items corresponding to the verified SDN service are integrated and included in the intent repository. For example, successfully creating... If the submission is successful, it indicates that the intent submission is valid and can be adopted by the intent repository. Otherwise, the intent submission is discarded, and the issue is reported to the submitter (i.e., the SDN controller or SDN user equipment).
[0096] Specifically, during the verification process, the intent item is decomposed, and the SDN service configuration parameters in the intent coordinates are read. These SDN service configuration parameters are then integrated with the various NBI call requests in the configuration scheme. These NBI call requests are then sent to the API interface server in the order they appear. The API interface server verifies the validity of the NBI call requests' parameters and integrates the intent items corresponding to the verified SDN services to form an intent repository. This API interface server's verification of the validity of NBI call requests is a fundamental capability of each northbound interface, and the verification method for NBI call requests is merely exemplary and not limited herein.
[0097] Furthermore, the creation of the intent repository also includes: after an intent submission is verified as valid, it can be pre-published to the intent repository. Pre-published intents can also be selected by SDN users; only when the number of intent selections for an intent item reaches a certain scale can it be officially published to IR. Conversely, if there is no response for a long period of time, the pre-published intent item can be considered for removal.
[0098] In summary, according to the technical solution provided in the embodiments of this disclosure, by verifying each NBI call request in the intent item, invalid intent items can be filtered out, avoiding the failure of subsequent SDN service configuration after incorrect configuration schemes are entered into the database; after verification, the SDN service must be successfully built as the final verification to ensure that the intent items entered into the database are all effective schemes that can be implemented and have no execution risk, thereby reducing the probability of SDN service configuration failure from the source.
[0099] To describe the technical solution of this disclosure in detail, the following references are made to the appendix. Figure 6 - Appendix Figure 8 This document describes in detail the SDN service configuration methods provided in this disclosure.
[0100] Figure 6This is a flowchart illustrating an intent repository construction method provided in an embodiment of the present disclosure.
[0101] Figure 7 This is a flowchart illustrating another intention repository construction method provided in an embodiment of the present disclosure.
[0102] Figure 8 This is a flowchart illustrating another SDN service configuration method provided in an embodiment of this disclosure.
[0103] like Figure 6 As shown, the intent repository construction method specifically includes the following steps: Step 601: Understand the intent of SDN services and configure the NBI call chain.
[0104] Specifically, each SDN service intent typically requires a series of NBI call requests to be implemented. SDN users, through their SDN user module (i.e., the aforementioned SDN user equipment), organize the series of NBI call requests corresponding to each SDN service intent, and then sequentially arrange and combine these NBI call requests according to the SDN service configuration order into a single entity, forming the SDN service configuration scheme corresponding to that SDN service intent. Alternatively, if unfamiliar with SDN service configuration schemes, users can access various intents and their corresponding configuration implementations in the IR (Information Reliability) for reference or directly perform secondary configurations to generate the intents they (i.e., the SDN user) require.
[0105] Step 602: Customize a unique IC.
[0106] Specifically, the definition of each intent requires a unique intent coordinate (IC) that is strictly mapped to a specific SDN service configuration scheme to avoid ambiguity and inconsistencies in the configuration of the same IC. The intent coordinate is constructed based on the SDN service type, SDN service resource operation behavior, and SDN service configuration parameters. The specific construction process can be found in step 301 and will not be elaborated here.
[0107] Step 603: Submit to IR.
[0108] Specifically, the configuration scheme generated in step 601 and the IC corresponding to step 2 are submitted to the intent repository as a complete intent item. All intent submitters will become contributing members of IR.
[0109] Step 604: The IR maintainer verifies the submission.
[0110] Specifically, the IR maintainer (i.e., the aforementioned intent repository maintenance module) is generally composed of the system's technical team or automation platform, without limitation here. The verification process only requires breaking down the submitted intent item, reading the reserved information in the IC (i.e., the aforementioned SDN service configuration parameters), integrating the NBI call requests of the configuration scheme, and sending each NBI call request sequentially to the API server. Of course, the API server itself will perform parameter validity verification on each NBI request. When all NBI call requests have been verified for validity, if the service can be successfully constructed, for example, successfully created, it indicates that the intent submission is valid and can be adopted and applied by the IR. Otherwise, the intent submission is discarded, and the process proceeds to step 606, where the issue is reported back to the submitter (i.e., the aforementioned SDN user module).
[0111] Step 605: Publish to IR for user selection.
[0112] Specifically, once an intent submission is verified as valid, it can typically be pre-published to IR. Pre-published intents can also be selected by users; only when a certain number of intents are selected can it be officially published to IR. Conversely, if there is no response for an extended period, the pre-published intent may be considered for removal.
[0113] Step 606: Provide feedback to the submitter.
[0114] like Figure 7 As shown, the intent repository construction method specifically includes the following steps: Step 701: The SDN controller collects NBI log data.
[0115] Specifically, the SDN controller collects NBI call request log data through the log data module. The log data records information describing SDN service behavior, such as the requested resource operation type and parameters. NBI call requests are marked and collected by recording the number of requests and setting request count thresholds.
[0116] Step 702: Calculate the number of requests for NBI in different business chains.
[0117] Specifically, according to the collection strategy in step 701, the SDN controller records the number of requests for each NBI call. A request count threshold is set, and NBI call requests that reach the threshold are marked and collected, temporarily stored in a specific business NBI set. For example, an NBI call request set is created. When this set gathers all the NBI call requests required for creation, an intent item construction task can be initiated.
[0118] Step 703: Integrate and extract into standardized intent.
[0119] Specifically, based on the business NBI set in step 702, for example, an NBI call request set is created. When the set contains all the NBI call requests required by the business, these NBI call requests are integrated according to the SDN business configuration order indicated by the set. The integration result is then regarded as a whole transaction and extracted into a complete and standardized intent scheme (i.e. intent item).
[0120] Step 704: Generate a unique IC and submit it to the IR.
[0121] Specifically, this step is related to Figure 6 Steps 602 and 603 are similar and will not be described again here.
[0122] Step 705: The IR maintenance party performs verification.
[0123] Specifically, this step is related to Figure 6 Step 604 is similar and will not be repeated here.
[0124] Step 706: Publish to IR for users to choose from.
[0125] Specifically, this step is related to Figure 6 Step 605 is similar and will not be repeated here.
[0126] Step 707: Feedback to the SDN controller.
[0127] The two intent collection schemes described above, namely "SDN user-defined intent" and "SDN controller intent collection", have intents derived from user-defined and real request data, respectively. They have also passed standard NBI verification, and the obtained intent results have high accuracy, reliability and universality, which are not available from other methods such as machine learning.
[0128] like Figure 8 As shown, the SDN service configuration method includes the following steps: Combination Figure 1 The system and Figures 6-7 The flowchart shown below details the complete implementation process of the SDN service configuration method provided in this disclosure: Step 801: Batch pull ICs from IR.
[0129] Specifically, to configure SDN services based on intents, the first task is to obtain the intents. The IR described in this disclosure is the central hub that manages massive intent solutions. When an intent is needed, candidate ICs (i.e., the aforementioned series of intent coordinates related to the intent) are simply retrieved from the IR based on the specific requirements of the intent. In particular, it is possible to retrieve ICs based on specific conditions. For example, if the intent is fuzzy, only ICs related to the specific SDN service type can be retrieved.
[0130] Step 802: Select an IC that matches the SDN service.
[0131] Specifically, intent-based SDN service configuration is typically done at the intent level. That is, each time only one intent matching the SDN service needs to be selected for input. In step 801, a series of candidate ICs have been retrieved from the IR. Based on this, the user only needs to select a target IC from the candidate ICs that matches the SDN service configuration requirements.
[0132] Step 803: Send IC to SDN controller.
[0133] Specifically, the target IC selected in step 802 is sent to the SDN controller for processing, and then the SDN service configuration is automatically completed. SDN service configuration can be completed simply by selecting and sending the IC. Compared to other methods such as natural language intent editing, the intent selection mode described in this proposal is simpler and more feasible.
[0134] Step 804: The SDN controller obtains the service plan from the IR based on the IC.
[0135] In this proposal, the SDN controller is the core of receiving and processing intents. Since each IC can uniquely point to a specific SDN service configuration scheme in the IR, after the SDN controller listens to the target IC submitted in step 803, it can retrieve the corresponding SDN service configuration scheme from the IR based on the target IC.
[0136] Step 805: The SDN controller sends the solution NBI to the API server.
[0137] Specifically, the configuration scheme described in step 804 corresponds to a series of sequentially invoked NBI sets. The SDN controller is responsible for sending NBI requests one by one to the API server according to the existing configuration order.
[0138] Step 806: The API server completes the configuration and distribution of business resources.
[0139] Specifically, the API server provides NBI capabilities, and all SDN services need to be configured through the API server. The API server executes NBI call requests sequentially, generates corresponding SDN network resources and basic network configurations, and further distributes the configurations to the underlying SDN layer, thus completing the SDN service configuration. Notably, all NBI call requests required for the above services and the fixed configuration order have been verified during the intent collection phase, ensuring extremely high accuracy in service configuration.
[0140] SDN network resources and basic network configuration refer to the underlying network configuration of specific SDN services, such as SDN network topology, network VNI, routing tables, sub-routes, local routes, etc. The specific configuration depends on the specific service. For each specific SDN service deployment, the SDN controller generates a corresponding network configuration and distributes it to the forwarding plane network devices, allowing the network service to take effect.
[0141] This disclosure also provides an SDN service configuration device. Figure 9 This is a structural block diagram of an SDN service configuration device provided in an embodiment of the present disclosure, such as... Figure 9 As shown, the SDN service configuration device 900 includes: a receiving module 901, an acquisition module 902, and a configuration module 903.
[0142] Specifically, the receiving module 901 is used to receive the target intent information of the target SDN service; Specifically, the acquisition module 902 is used to acquire a target SDN service configuration scheme that matches the target intent information from a pre-built intent repository based on the target intent information. Specifically, the configuration module 903 is used to send the target service configuration scheme to the application programming interface (API) server, so that the API server can complete the target SDN service configuration based on the target SDN service configuration scheme.
[0143] Figure 10 This is a hardware block diagram of an electronic device provided according to an embodiment of the present disclosure. The electronic device 1000 according to an embodiment of the present disclosure includes at least a processor and a memory for storing computer-readable instructions. When the computer-readable instructions are loaded and executed by the processor, the processor performs the SDN service configuration method described in any of the preceding embodiments of the present disclosure.
[0144] Figure 10The illustrated electronic device 1000 specifically includes a central processing unit (CPU) 1001, a graphics processing unit (GPU) 1002, and a memory 1003. These units are interconnected via a bus 1004. The CPU 1001 and / or GPU 1002 can function as the aforementioned processor, and the memory 1003 can function as the aforementioned memory storing computer-readable instructions. Furthermore, the electronic device 1000 may also include a communication unit 1005, a storage unit 1006, an output unit 1007, an input unit 1008, and an external device 1009, all of which are also connected to the bus 1004.
[0145] Figure 11 This is a schematic diagram of a computer-readable storage medium provided according to an embodiment of this disclosure. (As shown) Figure 11 As shown, a computer-readable storage medium 1100 according to an embodiment of this disclosure stores computer-readable instructions 1101 thereon. When the computer-readable instructions 1101 are executed by a processor, the SDN service configuration method described above with reference to any embodiment of this disclosure is performed. The computer-readable storage medium includes, but is not limited to, volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, optical disk, magnetic disk, etc.
[0146] This disclosure further provides a computer program product, including a computer program that, when executed by a processor, implements the SDN service configuration method described in any of the preceding embodiments of this disclosure.
[0147] The above is subject to the attached document. Figure 1 - Appendix Figure 11 This disclosure provides a detailed description of the SDN service configuration method, apparatus, electronic device, storage medium, and program product provided in the embodiments of this disclosure. The technical solutions of this disclosure have the following technical effects: 1. The concept of an Intent Repository (IR) was introduced for the first time to manage all valid intents and their matching SDN service configuration schemes. Each intent is assigned a unique Intent Coordinate (IC). All conventional SDN service configuration operations are simplified to: retrieving the IC, selecting the IC, sending the IC, and then the SDN controller reads and parses the IC, completing the configuration according to the NBI scheme pointed to by the IC. This significantly reduces the difficulty of inputting intents and the security issues associated with inputting intents, while improving the success rate of configuration distribution.
[0148] 2. To enrich the coverage scenarios of intents and build a more diverse intent repository (IR), two intent collection schemes are proposed: "SDN User-Defined Intents" and "SDN Controller-Collected Intents." "SDN User-Defined Intents" aims to build open and customizable IR intents, where all intents originate from user needs, and every user can be a participant and contributor to IR intents. "SDN Controller-Collected Intents" emphasizes basing its collection on real data; all intents originate from actual user requests, and each user's request record will influence intent generation. Both intent collection schemes revolve around the user, truly reflecting what users "want," while also reducing the uncertainty issues brought about by machine learning-based intent generation.
[0149] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.
[0150] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.
[0151] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.
[0152] Additionally, as used herein, the "or" used in a list of items beginning with "at least one" indicates a separate list, such that a list of, for example, "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not imply that the described example is preferred or better than other examples.
[0153] It should also be noted that in the systems and methods of this disclosure, the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered as equivalent solutions to this disclosure.
[0154] Various changes, substitutions, and modifications can be made to the technology described herein without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of this disclosure is not limited to the specific aspects of the processes, machines, manufactures, events, means, methods, and actions described above. Currently existing or later-developed processes, machines, manufactures, events, means, methods, or actions that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein can be utilized. Therefore, the appended claims include such processes, machines, manufactures, events, means, methods, or actions within their scope.
[0155] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.
[0156] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.
Claims
1. An SDN service configuration method, characterized in that, include: Receive target intent information; Based on the target intent information, obtain the target SDN service configuration scheme that matches the target intent information from the pre-built intent repository; The target SDN service configuration scheme is sent to the application programming interface (API) server, enabling the API server to complete the target SDN service configuration based on the target SDN service configuration scheme.
2. The SDN service configuration method according to claim 1, characterized in that, The step of obtaining a target SDN service configuration scheme that matches the target intent information from a pre-built intent repository based on the target intent information includes: Based on the target intent information, intent coordinates related to the target intent information are obtained from the pre-built intent repository, and the intent coordinates have a one-to-one mapping relationship with the SDN service configuration scheme in the intent repository; Based on the target intent information and the intent coordinates related to the target intent information, obtain the target intent coordinates corresponding to the target SDN service; Based on the target intent coordinates, a target SDN service configuration scheme that matches the target intent information is obtained from the intent repository.
3. The SDN service configuration method according to claim 1, characterized in that, The intent repository is constructed by the SDN user equipment in the following way: Based on the intents of multiple SDN services, obtain multiple NBI call requests that match the intent of each SDN service; Based on the multiple NBI call requests corresponding to each SDN service, obtain the SDN service configuration scheme corresponding to each SDN service; Based on each of the aforementioned SDN service configuration schemes, construct intent coordinates that match it; The intent coordinates of each SDN service are bound to the SDN service configuration scheme to obtain the intent item corresponding to each SDN service; Based on the intent item corresponding to each SDN service, the intent repository is constructed.
4. The SDN service configuration method according to claim 1, characterized in that, The intent repository is constructed in the following way: Obtain log data of NBI call requests; Based on the log data, obtain multiple NBI call requests corresponding to each SDN service; Based on the multiple NBI call requests corresponding to each SDN service, obtain the SDN service configuration scheme corresponding to each SDN service; Based on each of the aforementioned SDN service configuration schemes, construct intent coordinates that match it; The intent coordinates of each SDN service are bound to the SDN service configuration scheme to obtain the intent item corresponding to each SDN service; Based on the intent item corresponding to each SDN service, the intent repository is constructed.
5. The SDN service configuration method according to claim 3 or 4, characterized in that, The construction of the intent repository based on the intent item corresponding to each SDN service includes: Perform a legality check on each NBI call request in the intent item corresponding to each of the SDN services; After all NBI call requests pass the validity verification and the SDN service is successfully constructed, the intent items corresponding to the verified SDN service are integrated and included in the intent repository.
6. The SDN service configuration method according to claim 2, characterized in that, The intent coordinates are constructed based on SDN service type, SDN service resource operation behavior, and SDN service configuration parameters.
7. An SDN service configuration device, characterized in that, include: The receiving module is used to receive the target intent information of the target SDN service; The acquisition module is used to acquire a target SDN service configuration scheme that matches the target intent information from a pre-built intent repository based on the target intent information. The configuration module is used to send the target SDN service configuration scheme to the application programming interface (API) server, so that the API server can complete the target SDN service configuration based on the target SDN service configuration scheme.
8. An electronic device, characterized in that, include: Memory, used to store computer-readable instructions; as well as A processor for executing the computer-readable instructions, causing the electronic device to perform the SDN service configuration method as described in any one of claims 1 to 6.
9. A non-transitory computer-readable storage medium for storing computer-readable instructions, characterized in that, When the computer-readable instructions are executed by a processor, the processor performs the SDN service configuration method as described in any one of claims 1 to 6.
10. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the SDN service configuration method as described in any one of claims 1 to 6.