CN115842721A

CN115842721A - Network deployment method, device and related equipment

Info

Publication number: CN115842721A
Application number: CN202111098446.9A
Authority: CN
Inventors: 何克光; 邓灵莉; 杨艳; 张佳辰; 王琛; 贾云飞
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2021-09-18
Filing date: 2021-09-18
Publication date: 2023-03-24

Abstract

The application provides a network deployment method, a network deployment device and related equipment, wherein the method comprises the steps of receiving first data, distributing the first data, and enabling a distribution object to perform network deployment according to the first data. In the embodiment of the application, after first data is received, the first data is distributed, so that a distribution object performs network deployment according to the first data, and the first data comprises an intention description file. Therefore, after the network service design and deployment are completed, intention description information corresponding to the network service does not need to be manually selected, the intention description file in the first data is directly distributed to a distribution object, the distribution object is enabled to carry out network deployment according to the intention description file, manual participation is not needed in the process, and therefore the efficiency of network deployment is improved.

Description

Network deployment method, device and related equipment

Technical Field

The present application relates to the field of computer network technologies, and in particular, to a network deployment method, apparatus, and related device.

Background

In the prior art, a design deployment system of a network service, a deployment system of an intention flow and a deployment system of a closed-loop flow for maintaining the intention are three separate systems. After the network service design and deployment are completed, intention description information corresponding to the network service is artificially selected and artificially imported into an intention knowledge base. If the disposition of the closed-loop process for maintaining the intention is included, after the disposition of the intention process, manually selecting closed-loop process description information corresponding to the intention description information, and disposing a closed-loop example according to the closed-loop process description information. This approach requires manual intervention, is relatively complex in flow, and is inefficient.

Disclosure of Invention

The embodiment of the application provides a network deployment method, a network deployment device and related equipment, and solves the problem of low network deployment efficiency.

In order to achieve the above object, in a first aspect, an embodiment of the present application provides a network deployment method, including:

receiving first data, wherein the first data includes an intention description file, the first data further includes at least one of a Virtual Network Function (VNF) packet, a Physical Network Function (PNF) packet, and a closed-loop flow file, the intention description file corresponds to at least one of the VNF packet and the PNF packet, and the closed-loop flow file corresponds to the intention description file;

and distributing the first data so that the distribution object performs network deployment according to the first data.

In a second aspect, an embodiment of the present application provides a network deployment method, including:

receiving files in a target directory, wherein the files in the target directory comprise intention description files;

and deploying the intentions according to the intention description file.

In a third aspect, an embodiment of the present application provides a network deployment method, including:

receiving files in a target directory, wherein the files in the target directory comprise closed-loop process files;

and carrying out closed-loop deployment according to the closed-loop flow file.

In a fourth aspect, an embodiment of the present application provides a network deployment apparatus, including a first transceiver,

the first transceiver is to:

receiving first data, wherein the first data comprises an intent description file, the first data further comprising at least one of a Virtual Network Function (VNF) package, a Physical Network Function (PNF) package, and a closed-loop flow file, the intent description file corresponding to at least one of the VNF package and the PNF package, the closed-loop flow file corresponding to the intent description file;

In a fifth aspect, an embodiment of the present application provides a network deployment apparatus, including a second transceiver and a second processor,

a second transceiver for;

the second processor is configured to:

and deploying the intentions according to the intention description file.

In a sixth aspect, an embodiment of the present application provides a network deployment apparatus, including a third transceiver and a third processor,

the third transceiver is to:

the third processor is configured to:

and carrying out closed-loop deployment according to the closed-loop flow file.

In a seventh aspect, an embodiment of the present application provides a network deployment device, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; the processor is configured to read a program in the memory to implement the steps in the network deployment method according to the first aspect; or, implementing the steps in the network deployment method according to the second aspect; or, implementing the steps in the network deployment method according to the third aspect.

In an eighth aspect, an embodiment of the present application provides a readable storage medium for storing a program, where the program when executed by a processor implements the steps in the network deployment method according to the first aspect; or, implementing the steps in the network deployment method according to the second aspect; or, implementing the steps in the network deployment method according to the third aspect.

In the embodiment of the application, after first data is received, the first data is distributed, so that a distribution object performs network deployment according to the first data, and the first data comprises an intention description file. Therefore, after the network service design and deployment are completed, intention description information corresponding to the network service does not need to be manually selected, the intention description file in the first data is directly distributed to a distribution object, the distribution object is enabled to carry out network deployment according to the intention description file, manual participation is not needed in the process, and therefore the efficiency of network deployment is improved.

Drawings

For a clear explanation of the technical solutions in the embodiments of the present application, the drawings of the specification are described below, it is obvious that the following drawings are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the listed drawings without any inventive effort.

Fig. 1 is a block diagram of a network system to which an embodiment of the present application is applicable;

fig. 2 is a flowchart of a network deployment method provided in an embodiment of the present application;

fig. 3 is a second flowchart of a network deployment method according to an embodiment of the present application;

fig. 4 is a third schematic flowchart of a network deployment method according to an embodiment of the present application;

fig. 5 is a fourth flowchart of a network deployment method provided in an embodiment of the present application;

fig. 6 is a fifth flowchart of a network deployment method provided in the embodiment of the present application;

fig. 7 is a sixth schematic flowchart of a network deployment method provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a network deployment apparatus provided in an embodiment of the present application;

fig. 9 is a second schematic structural diagram of a network deployment apparatus according to an embodiment of the present application;

fig. 10 is a third schematic structural diagram of a network deployment apparatus provided in the embodiment of the present application;

FIG. 11 is a block diagram of a network deployment device in accordance with an embodiment of the present disclosure;

fig. 12 is a second schematic structural diagram of a network deployment device provided in the present application;

fig. 13 is a third schematic structural diagram of a network deployment device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. On the basis of the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without any creative effort belong to the protection scope of the present application.

The terms "first," "second," and the like in the embodiments of the present invention are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Further, as used herein, "and/or" means at least one of the connected objects, e.g., a and/or B and/or C, means 7 cases including a alone, B alone, C alone, and both a and B present, B and C present, a and C present, and a, B, and C present.

Referring to fig. 1, fig. 1 is a block diagram of a network system to which an embodiment of the present application is applicable, and as shown in fig. 1, includes a network service deployment system 11, an intention execution system 12, and a closed-loop execution system 13. Communication may be between the network service deployment system 11 and the intent execution system 12, and communication may also be between the network service deployment system 11 and the closed loop execution system 13.

The following describes a network deployment method provided in an embodiment of the present invention.

Referring to fig. 2, fig. 2 is a schematic flowchart of a network deployment method provided in an embodiment of the present application. The network deployment method shown in fig. 2 may be performed by the network service deployment system 11.

As shown in fig. 2, the network deployment method may include the following steps:

a step 201 of receiving first data, wherein the first data includes an intention description file, the first data further includes at least one of a virtual network function VNF package, a physical network function PNF package, and a closed-loop flow file, the intention description file corresponds to at least one of the VNF package and the PNF package, and the closed-loop flow file corresponds to the intention description file;

in particular implementations, the first data may be received by a designer in network service deployment system 11. The intention description file mainly describes intentions and corresponding workflows supported by a certain network service or a single virtual network function VNF or physical network function PNF in the network service according to a certain specification (including but not limited to the specification of TOSCA, JSON, YANG, RDFS, etc.), and puts description information related to the intentions into the same file or different files. The description information includes, but is not limited to, general expression description of the intent, parameter information corresponding to the intent, implementation workflow or policy information corresponding to the intent, closed-loop flow information for maintaining the intent, and the like. The corresponding workflow is a business process which is already supported by the system or can be supported by the network service after deployment.

The closed-loop flow file for maintaining the intention is mainly used for describing the corresponding closed-loop flow for maintaining the intention. And storing the closed-loop process information describing the closed-loop process into the same file or different files according to a certain specification (including but not limited to specifications of TOSCA/JSON/YANG/RDFS and the like) to obtain a closed-loop process file.

The above-mentioned corresponding closed-loop process information is divided into two cases. The first is to correspond to the existing closed-loop instance deployed in the system, and the closed-loop flow information here is mainly information without limitation to name, ID, flag, etc. for describing the existing closed-loop instance, so as to associate the intention with the existing closed-loop instance. The second is to describe a completely new closed-loop process, in which case the description information includes, but is not limited to, the closed-loop process, parameter information corresponding to the closed loop, corresponding workflow information, and the like. The corresponding workflow is a business process which is already supported by the system or can be supported by the network service after deployment.

The VNF package and the PNF package include network service component elements VNF and PNF, and network connections corresponding to the VNF and the PNF.

The intentions can be classified into the following two categories according to usage scenarios. The first category is network service specific intents, which depend on a particular network service, are that network service or an individual VNF/PNF support in the network service, so the lifecycle of the intents is strongly correlated to the lifecycle of the network service. The second category is a general purpose intent that is not dependent on any particular network service, and is a general purpose intent to support multiple network services, whose lifecycle is not related to a particular network service.

In a particular interest scenario of network services, the first data may include a VNF package and/or a PNF package, and an intent description file, or the first data may include a VNF package and/or a PNF package, an intent description file, and a closed-loop flow file. In the general intent scenario, the first data may include an intent description file and a closed-loop flow file.

Step 202, distributing the first data, so that the distributed object performs network deployment according to the first data.

In particular implementation, the action body performing the distribution work may be an orchestrator in a network service deployment system. The distribution object may be an intention execution system and a closed loop execution system. When the first data includes an intention description file, the distribution object includes an intention execution system, and the intention description file is distributed to the intention execution system. When the first data includes a closed-loop flow file, the distribution object includes a closed-loop execution system to which the closed-loop flow file is distributed.

The intention execution system can perform intention deployment according to the intention description file, the closed-loop execution system can perform closed-loop deployment according to the closed-loop flow file, and the network service deployment system can perform network service deployment according to the VNF package and the PNF package.

Before distributing the first data, the first data may be stored in the network service deployment system, or may not be stored.

Further, under the condition that the first data also comprises a closed-loop flow file, the closed-loop flow description information corresponding to the intention description information does not need to be manually selected after the intention flow is deployed, a closed-loop instance is deployed according to the closed-loop flow description information, and the closed-loop flow file in the first data is directly distributed to a distribution object to be subjected to network deployment according to the closed-loop flow file.

Optionally, after the receiving the first data and before the distributing the first data, the method further includes:

storing the first data into a target directory of a target file according to a preset rule;

wherein the preset rules comprise at least one of:

storing the intention description file to a first target directory in the target files, the target directory comprising the first target directory;

and storing the closed-loop process file to a second target directory in the target file, wherein the target directory comprises the second target directory.

In a specific implementation, before distributing the first data, the first data may be stored in a target directory of the target file according to a preset specification. The storage location of the target file may be a designer of the network service deployment system. The second target directory may be a next-level directory of the first target directory, or may be a peer-level directory of the first target directory.

For example, the Intent description file may be uniformly archived under the Intent directory of the NSD, where a next level directory, such as Intent/VNF1/, may be added if it contains an Intent for a single VNF/PNF support. The closed-loop flow file may be placed in an Intent/control-loop directory, which is a subordinate directory of the Intent. If the closed loop is for a particular VNF, a next level directory may be added here, such as may be placed at Intent/VNF1/control-loop. The file directory is only an example, and any directory organization form implemented by the method of the embodiment of the present application is within the scope of the patent.

According to the implementation mode, the first data are stored in the target directory of the target file according to the preset rule, so that the distribution object can conveniently search the target file according to the preset rule.

Optionally, the distributing the first data so that a distribution object performs network deployment according to the first data includes:

sending the intention description file in the first target directory to a loader of an intention execution system so that the intention execution system performs intention deployment according to the intention description file;

or when the first data comprises the closed-loop process file, sending the closed-loop process file in the second target directory to a loader of a closed-loop execution system, so that the closed-loop execution system performs closed-loop deployment according to the closed-loop process file.

In specific implementation, after the existing orchestrator service deployment workflow is completed, a process can be added for processing the distribution of the intention description file and the closed-loop process file. Distributing first data to a distribution object in the case that a target directory exists in a target file; in the case where the target directory does not exist in the target file, the first data does not need to be distributed to the distribution object. Further, in a case where the first target directory exists in the target file, the file stored in the first target directory is distributed to the intention execution system, and the distribution object includes the intention execution system. And distributing the closed-loop flow file to the closed-loop execution system under the condition that the second target directory exists in the target file, wherein the distribution object comprises the closed-loop execution system.

As an example, if the first data is stored according to the storage method of the first example, the orchestrator may analyze whether the target file includes an Intent directory or a control-loop directory under the Intent, where the control-loop is a lower directory of the Intent. . And if the corresponding directory exists, starting the distribution work of the corresponding description file. If the target file contains an Intent directory and the Intent directory contains an archived file, the archived file in the Intent directory, namely an Intent description file, can be distributed to a loader of an Intent execution system; if the target file contains a control-loop directory under Intent and the control-loop directory contains an archive file, the archive file in the control-loop directory, that is, the closed-loop flow file, can be distributed to the closed-loop execution system. If no corresponding directory exists, the distribution of the intention description file and/or the closed-loop flow file is not required, and the workflow is ended.

Optionally, after receiving the first data, the method further includes:

performing network service deployment according to the VNF package or the PNF package when the first data comprises the VNF package or the PNF package;

and sending a notification message to the distribution object when the network service deployment is completed, wherein the notification message is used for notifying the distribution object that the distribution object is about to send the file in the target directory.

In a specific implementation, the network service deployment system may perform network service deployment according to the VNF package and/or the PNF package. In the event that the network service deployment is complete, a notification message may be sent by the orchestrator of the network service deployment system to the distribution object. The orchestrator of the network service deployment system may respond to the subscription request at an appropriate time after receiving the subscription request of the distribution object for the notification message, and send the notification message; notification messages may also be sent to the distribution object directly at the appropriate time. And the distribution object prepares for receiving the files in the target directory after receiving the notification message.

For example, in case the network service deployment is completed, a first notification message is sent to the loader of the intended execution system for notifying the loader of the intended execution system that the intention description file under the first target directory is about to be sent thereto. And sending a second notification message to the loader of the closed-loop execution system when the deployment is finished, wherein the second notification message is used for notifying the loader of the closed-loop execution system that the closed-loop flow files under the second target directory are about to be sent to the loader of the closed-loop execution system.

In this embodiment, after the network service deployment is completed, a notification message is sent to the distribution object, which may facilitate the distribution object to be ready to receive the target file.

Optionally, before sending the notification message to the distribution object, the method further includes:

receiving at least one of a first subscription request for subscribing to a first notification message and a second subscription request for subscribing to a second notification message.

In particular implementations, the first subscription request and the second subscription request may be received by an orchestrator in a network service deployment system. The first notification message is used to notify the first distribution object that an intention description file in the first target directory is about to be sent. The first dispatch object may now be the loader of the intended execution system. The second notification message is used to notify the second distribution object that the closed-loop flow file in the second target directory is about to be sent. When the intention deployment is needed, an orchestrator in the network service deployment system needs to receive a first subscription request; when closed-loop deployment is needed, the orchestrator in the network service deployment system needs to receive a second subscription request.

According to the network deployment method in the embodiment of the application, after first data is received, the first data is distributed, so that a distribution object performs network deployment according to the first data, and the first data comprises an intention description file. Therefore, after the network service design and deployment are completed, intention description information corresponding to the network service does not need to be manually selected, the intention description file in the first data is directly distributed to a distribution object, the distribution object is enabled to carry out network deployment according to the intention description file, manual participation is not needed in the process, and therefore the efficiency of network deployment is improved.

Referring to fig. 3, fig. 3 is a schematic flowchart of a network deployment method provided in an embodiment of the present application. The network deployment method shown in fig. 3 may be performed by the intent execution system 12.

As shown in fig. 3, the network deployment method may include the steps of:

step 301, receiving files in a target directory, wherein the files in the target directory comprise intention description files;

in particular implementations, the files in the target directory may be received by a loader of the intent execution system. The files in the target directory may or may not be stored locally after being received.

And 302, deploying the intention according to the intention description file.

In a specific implementation, if the first data is archived in the manner of the above example one, the loader of the intention execution system may extract an archived file in the Intent directory, mainly an intention description file, including an intention related to the network service and an intention related to the VNF/PNF in the network service.

The deployment of intentions is performed according to the intention description file, all the intention description files need to be analyzed firstly, and after the analysis, whether intention knowledge points corresponding to the intention description information exist in an intention knowledge base needs to be judged. If the intention knowledge point exists, the intention knowledge point is considered to need to be updated, and updating and reloading are needed according to the analyzed information of the new intention description file. If the target information does not exist, the target information is considered as a brand new intention knowledge point, and analyzed information needs to be imported into an intention knowledge base to form a new intention knowledge point.

The analysis of the intention file, the introduction of the intention information, and the generation of the intention knowledge belong to the existing functions of the intention execution system, and are not described herein again.

Optionally, before receiving the file in the target directory, the method further includes:

and sending a first subscription request, wherein the first subscription request is used for subscribing a first notification message, the first notification message is used for notifying a first distribution object of about to send the files in the target directory, and the files in the target directory comprise the intention description file.

According to the network deployment method in the embodiment of the application, after first data is received, the first data is distributed, so that a distribution object carries out network deployment according to the first data, and the first data comprises an intention description file. Therefore, after the network service design and deployment are completed, intention description information corresponding to the network service does not need to be manually selected, the intention description file in the first data is directly distributed to a distribution object, the distribution object is enabled to carry out network deployment according to the intention description file, manual participation is not needed in the process, and therefore the efficiency of network deployment is improved.

It should be noted that, this embodiment is implemented as an implementation of the device in the intention execution system corresponding to the embodiment of the method in fig. 2, so that reference may be made to the relevant description in the embodiment of the method in fig. 2, and the same beneficial effects may be achieved. To avoid repetition of the description, the description is omitted.

Referring to fig. 4, fig. 4 is a schematic flowchart of a network deployment method provided in an embodiment of the present application. The network deployment method shown in fig. 4 may be performed by the closed loop execution system 13.

As shown in fig. 4, the network deployment method may include the steps of:

step 401, receiving files in a target directory, wherein the files in the target directory comprise closed-loop process files;

in particular implementations, the files in the target directory may be received by a loader of the closed-loop execution system. The files in the target directory may or may not be stored locally after being received.

And 402, deploying closed loops according to the closed loop flow files.

In a specific implementation, if the first data is archived in the manner of the example one, the loader of the closed-loop execution system may extract archived files under each control-loop directory under the Intent directory, which are mainly closed-loop process description files, including a closed-loop process description file for maintaining an intention related to the network service and a closed-loop process description file for maintaining an intention of a specific VNF/PNF in the network service.

All the closed-loop process description files are analyzed, and whether corresponding closed-loop instances exist can be judged according to information such as closed-loop names and IDs. And if the closed-loop instance exists, directly multiplexing the closed-loop instance, and configuring the closed-loop instance according to the related information of the network service. If the closed-loop flow information does not exist, the closed-loop flow information is considered to be brand-new closed-loop flow information, and the analyzed information needs to be deployed in a closed-loop execution system to form a new closed-loop example.

And deploying the analyzed closed-loop information in a closed-loop execution system to generate a corresponding closed-loop instance. This is the existing function of the closed loop execution system and will not be described here.

In a scenario where the network service is particularly interested, in addition to the aforementioned intent deployment procedure and closed-loop deployment procedure, deletion procedures are also included in the intent deployment and closed-loop deployment, and the deletion procedures are also strongly related to the particular network service.

When a network service is deleted, the intention corresponding to the network service or to a certain VNF/PNF under the network service is also deleted synchronously. For a closed-loop instance that maintains the intent, it is determined whether the closed-loop instance is also specific to the intent. If it is a closed-loop instance specific to maintaining the intent and no other intent is using the closed-loop instance, then the closed-loop instance is also deleted synchronously.

In the general intent scenario, the delete flow is also independent of the specific network service, in addition to the intent deployment flow and closed-loop deployment flow described previously. When the general intent is no longer to use the closed-loop instance that needs to be deleted, it is necessary to determine whether the closed-loop instance is also specific to the intent for maintaining the intent. If it is a closed-loop instance specific to maintaining the intent and no other intent is using the closed-loop instance, then the closed-loop instance is also deleted synchronously.

It should be noted that, the present embodiment is implemented as an apparatus in a closed-loop execution system corresponding to the embodiment of the method in fig. 2, and therefore, reference may be made to the relevant description in the embodiment of the method in fig. 2, and the same beneficial effects may be achieved. To avoid repetition of the description, the description is omitted.

The various optional implementations described in the embodiments of the present invention may be implemented in combination with each other or implemented separately without conflict, and the embodiments of the present invention are not limited thereto.

For ease of understanding, the examples are illustrated below:

as an example, referring to fig. 5, in a specific interesting scene of a network service, it is necessary to add a function 1, that is, func1, an orchestrator addition function 2, that is, func2, an intended execution system addition function 3, that is, func3, and a closed-loop execution system addition function 4, that is, func4, to a designer of a network service deployment system. The details are as follows.

The functional points of func1 added to the designer of the network service deployment system are as follows:

1) Designer input:

in the scheme, the designer input mainly comprises the following three parts:

a. a network service component element VNF/PNF and a corresponding network connection;

b. the intention description file corresponding to the network service: the method mainly describes intentions and corresponding workflows supported by a certain network service or a single VNF/PNF in the network service according to a certain specification (including but not limited to specifications such as TOSCA/JSON/YANG/RDFS), and puts description information related to the intentions into the same file or different files. The description information includes, but is not limited to, general expression description of the intent, parameter information corresponding to the intent, implementation workflow or policy information corresponding to the intent, closed-loop flow information for maintaining the intent, and the like. The corresponding workflow is a business process which is already supported by the system or can be supported by the network service after deployment.

c. Maintaining an intended closed-loop flow document: the method is mainly used for describing a corresponding closed-loop process for maintaining the intention, and the closed-loop process is described according to a certain specification (including but not limited to the specification of TOSCA/JSON/YANG/RDFS) and put into the same file or different files.

The above-mentioned corresponding closed-loop process information is divided into two cases. The first is to correspond to an existing closed-loop instance already deployed in the system, and here, the closed-loop flow information is mainly information, not limited to name, ID, flag, etc., for describing the existing closed-loop instance, so as to associate the intention with the existing closed-loop instance. The second is to describe a completely new closed-loop process, in which case the description information includes, but is not limited to, the closed-loop process, parameter information corresponding to the closed loop, corresponding workflow information, and the like. The corresponding workflow is a business process which is already supported by the system or can be supported by the network service after deployment.

2) The designer outputs:

the designer outputs mainly web service deployment files including VNF/PNF packages, intent description files, and closed-loop flow files.

3) Designer workflow:

the design function of the network service is unchanged, func1 is added, and the import function of the network service corresponding intention description file and the closed-loop flow description file for maintaining the intention is added. Wherein the intention information file is uniformly filed under the Intent directory of the NSD, if the intention supported by a single VNF/PNF is contained, a next-level directory, such as Intent/VNF1/, can be added. While information related to maintaining the intended closed loop may be placed in the Intent/control-loop directory, where a next level directory may be added if the closed loop is for a particular VNF, such as may be placed in Intent/VNF1/control-loop. The file directory here is only an example for implementing the scheme, and any directory organization form implemented by using the application idea is within the protection scope of the patent.

The designer-exported Tosca web services file directory is as follows (assuming here that both the intent description file and the closed loop description file are stored in yaml format):

func2 added to the orchestrator of the network service deployment system mainly adds the following functional points:

1) Function enhancement of the orchestrator:

the orchestrator of the service deployment system needs to adapt to the existing workflow, and after the existing orchestrator service deployment workflow is completed, a process is added for processing the distribution of the intention description file and the closed-loop process description file.

And analyzing whether the distributed service deployment file contains an Intent directory and a control-loop directory under the Intent. And if the corresponding directory exists, starting the distribution work of the corresponding description file. If the corresponding directory does not exist, the intention and closed-loop file distribution is not needed, the workflow is ended, and the default service does not support the function related to the intention.

2) Description file distribution:

after the network service deployment system finishes service deployment, the network service pair intention description file and the closed-loop flow description file for maintaining the intention are distributed. In the present application, the distributed objects include a loader of an intent execution system and a loader of a closed-loop execution system. For the distribution of the loader of the Intent execution system, the distribution of the Intent description file is performed only on the premise that the network deployment file after the deployment is judged to contain the Intent directory and the archive file is contained in the Intent directory (the workload of the loader of the Intent execution system can be effectively reduced). And the closed-loop execution system loader is distributed, the closed-loop flow description file is distributed only on the premise that the network deployment file which is completely deployed is judged to contain an Intent directory, a control-loop directory exists in a subordinate directory, and the archive file is contained in the control-loop directory (the workload of the closed-loop execution system loader can be effectively reduced).

In this application, it is desirable that the intent execution system add func3, with the following added functional features:

1) The newly-added network service subscription function comprises the following steps:

a service subscriber is required as a orchestrator of a network service deployment system.

2) Newly adding a subscription notification processing logic:

a. and once the network service deployment file distributed after the service orchestrator finishes deployment is received, the network service deployment file is locally stored.

b. The loader of the intention execution system extracts archive files under the network service deployment file Intent directory, mainly intention description files, including network service-related intents and VNF/PNF-related intents in the network service.

c. After analyzing all the above-mentioned intention description files, it is necessary to determine whether intention knowledge corresponding to the intention description information already exists in the intention knowledge base. If the intention knowledge exists, the intention knowledge is considered to be required to be updated, and the intention knowledge is required to be updated and reloaded according to the analyzed information of the new intention description file. If the intention knowledge does not exist, the intention knowledge is considered to be brand new intention knowledge, and the analyzed information needs to be imported into an intention knowledge base to form a new intention knowledge.

d. The analysis of the intention file, the introduction of the intention information, and the generation of the intention knowledge belong to the existing functions of the intention execution system, and are not described herein again.

In the application, func4 needs to be added to the closed-loop execution system, and the following functional characteristics are added:

2) Newly adding a subscription notification processing logic:

a. and once the network service deployment file distributed after the orchestrator finishes deployment is received, the network service deployment file is locally stored.

b. A loader of the closed-loop execution system extracts archive files under each control-loop catalog of a network service deployment file, wherein the archive files are mainly closed-loop process description files and comprise closed-loop process description files for maintaining network service related intents and closed-loop process description files for maintaining specific VNF/PNF intents in the network service.

c. All the closed-loop process description files are analyzed, and whether corresponding closed-loop instances exist can be judged according to information such as closed-loop names and IDs. And if the closed-loop instance exists, directly multiplexing the closed-loop instance, and configuring the closed-loop instance according to the related information of the network service. If the closed-loop flow information does not exist, the closed-loop flow information is considered to be brand-new closed-loop flow information, and the analyzed information needs to be deployed in a closed-loop execution system to form a new closed-loop example.

d. And deploying the analyzed closed-loop information in a closed-loop execution system to generate a corresponding closed-loop instance. These are functions of the closed loop execution system and will not be described in detail here.

5. Deletion process of network service, intention knowledge point, closed loop instance, etc.:

for the specific intents of the network service, in addition to the aforementioned deployment procedure, its deletion procedure is also strongly related to the specific network service.

As an example, referring to fig. 6, in the general purpose scenario, it is also necessary to add func1, increase func2 by the orchestrator, increase func3 by the intention execution system, and increase func4 by the closed loop execution system in the designer of the network service deployment system, respectively. In this scenario, the intent is independent of the particular network service, so deployment of the network service may not be involved here. In the scheme under the scene, the key point is to associate the deployment of the intention flow with the deployment of the closed-loop flow which correspondingly maintains the intention, and the deployment of the corresponding closed-loop flow is completed while the deployment of the intention flow is completed. The details are as follows.

1.func1：

Func1 added to a designer of a network service deployment system mainly adds the following functional points:

1) Designer input:

in this scenario, the designer input mainly includes the following two parts:

a. general purpose description file: the general intentions and corresponding workflows are mainly described according to a certain specification (including but not limited to the specification of TOSCA/JSON/YANG/RDFS), and description information related to the intentions is put into the same file or different files. The description information includes, but is not limited to, general expression description of the intent, parameter information corresponding to the intent, implementation workflow or policy information corresponding to the intent, closed-loop flow information for maintaining the intent, and the like. The corresponding workflow is a business process which is already supported by the system or can be supported by the network service after deployment.

b. The content of the closed-loop flow description file for maintaining the intention is the same as that of the closed-loop flow description file in the scene of the specific intention of the network service, and is not repeated.

2) The designer outputs:

the designer outputs mainly intention knowledge and corresponding closed-loop flow deployment files.

3) Designer workflow:

adding func1, and adding the functions of importing a general purpose description file and a closed-loop process description file for maintaining the purpose. Wherein the intention information file is uniformly filed under the Intent directory. While information related to maintaining the intended closed loop may be placed in the Intent/control-loop directory. The file directory is only an example for implementing the scheme, and any directory organization form implemented by using the application idea is within the protection scope of the patent.

The designer exported Tosca web services file directory is as follows (assuming here that both the intent description file and the closed loop description file are stored in yaml format):

2.func2：

1) Function enhancement of the orchestrator:

here, similar to the scenario in the network service specific intent scenario, except that the flow of network deployment is not required here.

And analyzing whether the distributed service deployment file contains an Intent directory and a control-loop directory under the Intent. And if the corresponding directory exists, starting the distribution work of the corresponding description file.

2) Description file distribution:

in the present application, the distributed objects include a loader of an intent execution system and a loader of a closed-loop execution system. The distribution of the intention description file is performed only under the premise that the file contains an Intent directory and the archive file is contained under the Intent directory aiming at the distribution of the intention execution system loader. And the distribution of the closed-loop execution system loader is realized only on the premise that the file contains an Intent directory, the subordinate directory contains a control-loop directory, and the control-loop directory contains an archive file.

3.func3：

2) Newly added subscription notification processing logic:

here, the scheme is the same as that in the scenario where the network service is especially interesting, and is not described again.

4.func4：

2) Newly adding a subscription notification processing logic:

for general purposes, its deletion process is independent of the specific network service, in addition to the deployment process described previously.

When the general intent is no longer to be used and needs to be deleted, for a closed-loop instance that maintains the intent, it needs to be determined whether the closed-loop instance is also specific to the intent. If it is a closed-loop instance specific to maintaining the intent and no other intent is using the closed-loop instance, then the closed-loop instance is also deleted synchronously.

As an example, we take creating an end-to-end slicing service and creating a corresponding SLA guarantee intention as an example (it should be noted that this application scenario is only an example, and the embodiment of the present application is not limited thereto), and introduce a specific implementation process of the embodiment of the present application, refer to fig. 7, and fig. 7 is a flowchart of the embodiment of the present application.

After receiving slicing service requirements, obtaining VNF/PNF and closed-loop flow design corresponding to network connection design, SLA guarantee intention design and maintenance intention, firstly determining an end-to-end slicing network service deployment file according to the files, and carrying out end-to-end slicing network service deployment according to the end-to-end slicing network service deployment file. After the network service deployment is completed, the intention description file and the closed-loop flow file can be distributed, and the intention execution system analyzes the intention description file respectively to generate intention knowledge points for intention deployment; and analyzing the closed-loop flow file by the closed-loop execution system to generate a closed-loop instance, and deploying the closed loop.

After the steps, the deployment of the end-to-end slicing network service, the deployment of the intention knowledge corresponding to the end-to-end slicing network service and the deployment of the closed-loop flow example for maintaining the intention are completed. After the user inputs the SLA guarantee intention described in the natural language related to the end-to-end slicing network service, the specific execution flow is as follows:

1. the analyzer of the intention execution system analyzes the intention described by the natural language input by the user and acquires corresponding intention knowledge in the intention knowledge base according to the analyzed information.

2. And the intention execution system generates a corresponding intention example according to the intention knowledge acquired in the last step and the parameter information provided in the user input intention.

3. The intention instance executes the corresponding workflow to achieve the user's intention.

4. And executing a corresponding guarantee workflow by the intention example, calling the deployed closed-loop example, continuously monitoring the intention of the user, verifying whether the intention is met in real time, and taking corresponding corrective measures when the intention is not met.

Referring to fig. 8, fig. 8 is a block diagram of a network deployment device according to an embodiment of the present invention. As shown in fig. 8, the network deploying apparatus 500 comprises a first transceiver 501 and a first processor 502, wherein,

a first transceiver 501 configured to receive first data, wherein the first data comprises an intention profile, the first data further comprises at least one of a virtual network function, VNF, package, a physical network function, PNF, package, and a closed-loop flow profile, the intention profile corresponding to at least one of the VNF package and the PNF package, the closed-loop flow profile corresponding to the intention profile;

Optionally, the first processor 502 is configured to store the first data in a target directory of a target file according to a preset rule;

wherein the preset rules comprise at least one of:

storing the closed-loop flow file to a second target directory in the target file, wherein the target directory comprises the second target directory.

Optionally, the first transceiver 501 is further configured to send the intention description file in the first target directory to a loader of an intention execution system, so that the intention execution system performs intention deployment according to the intention description file;

or, when the first data includes the closed-loop process file, the first transceiver 501 is further configured to send the closed-loop process file in the second target directory to a loader of a closed-loop execution system, so that the closed-loop execution system performs closed-loop deployment according to the closed-loop process file.

Optionally, the first processor 502 is further configured to perform network service deployment according to the VNF package or the PNF package if the first data includes the VNF package or the PNF package;

the first transceiver 501 is further configured to send a notification message to the distribution object when the network service deployment is completed, where the notification message is used to notify the distribution object that a file in a target directory is about to be sent.

Optionally, the first transceiver 501 is further configured to receive at least one of a first subscription request for subscribing to the first notification message and a second subscription request for subscribing to the second notification message.

The network deployment apparatus 500 can implement each process of the method embodiment in fig. 2 in the embodiment of the present invention, and achieve the same beneficial effects, and for avoiding repetition, details are not described here.

Referring to fig. 9, fig. 9 is a block diagram of a network deployment device according to an embodiment of the present invention. As shown in fig. 9, the network deploying apparatus 600 comprises a second transceiver 601 and a second processor 602, wherein,

a second transceiver 601, configured to receive files in a target directory, where the files in the target directory include an intention description file;

a second processor 602 for performing the deployment of the intent according to the intent description file.

Optionally, the second transceiver 601 is further configured to send a first subscription request, where the first subscription request is used to subscribe to a first notification message, where the first notification message is used to notify that a first distribution object is about to send a file in the target directory, where the file in the target directory includes an intention description file.

The network deployment apparatus 600 can implement each process of the method embodiment of fig. 3 in the embodiment of the present invention, and achieve the same beneficial effects, and is not described herein again to avoid repetition.

Referring to fig. 10, fig. 10 is a block diagram of a network deployment apparatus according to an embodiment of the present invention. As shown in fig. 10, the network deployment apparatus 700 comprises a third transceiver 701 and a third processor 702, wherein,

a third transceiver 701, configured to receive a file in a target directory, where the file in the target directory includes a closed-loop process file;

a third processor 702, configured to perform closed-loop deployment according to the closed-loop flow file.

Optionally, the third transceiver 701 is further configured to send a second subscription request, where the second subscription request is used to subscribe to a second notification message, and the second notification message is used to notify a second distribution object that a file in the target directory is about to be sent, where the file in the target directory is a closed-loop process file.

The network deployment apparatus 700 can implement each process of the method embodiment in fig. 4 in the embodiment of the present invention, and achieve the same beneficial effects, and is not described herein again to avoid repetition.

The embodiment of the invention also provides network deployment equipment. As the principle of the network deployment device to solve the problem is similar to the method in fig. 2 in the embodiment of the present application, the implementation of the network deployment device may refer to the implementation of the method, and repeated details are not repeated. As shown in fig. 11, the network deployment device according to the embodiment of the present application includes:

the fourth processor 800, configured to read the program in the memory 820, performs the following processes:

distributing the first data through a first transceiver 810 to enable a distribution object to perform network deployment according to the first data, or to receive and receive first data, wherein the first data comprises an intention description file, the first data further comprises at least one of a Virtual Network Function (VNF) package, a Physical Network Function (PNF) package and a closed-loop flow file, the intention description file corresponds to at least one of the VNF package and the PNF package, and the closed-loop flow file corresponds to the intention description file;

a first transceiver 810 for receiving and transmitting data under the control of the fourth processor 800.

Wherein in fig. 8, the bus architecture may include any number of interconnected buses and bridges, with one or more fourth processors, represented by the fourth processor 800, and various circuits of the memory, represented by the memory 820, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The first transceiver 810 may be a plurality of elements, i.e., including a transmitter and a first transceiver, providing a means for communicating with various other apparatus over a transmission medium. The fourth processor 800 is responsible for managing the bus architecture and general processing, and the memory 820 may store data used by the fourth processor 800 in performing operations.

Optionally, the fourth processor 800 is further configured to read the program in the memory 820, and execute the following steps:

wherein the preset rules comprise at least one of:

Optionally, the fourth processor 800 is further configured to send the intention description file in the first target directory to a loader of an intention execution system, so that the intention execution system performs intention deployment according to the intention description file;

Optionally, the fourth processor 800 is further configured to perform network service deployment according to the VNF package or the PNF package if the first data includes the VNF package or the PNF package;

the first transceiver 810 is further configured to send a notification message to the distribution object when the network service deployment is completed, where the notification message is used to notify the distribution object that a file in a target directory is about to be sent.

Optionally, the first transceiver 810 is further configured to receive at least one of a first subscription request for subscribing to the first notification message and a second subscription request for subscribing to the second notification message.

The network deployment device provided in the embodiment of the present application may execute the method embodiment described above, and the implementation principle and the technical effect are similar, which are not described herein again.

The embodiment of the invention also provides network deployment equipment. As the principle of the network deployment device to solve the problem is similar to the method in fig. 3 in the embodiment of the present application, the implementation of the network deployment device may refer to the implementation of the method, and repeated details are not repeated. As shown in fig. 12, the network deployment device according to the embodiment of the present application includes:

a fifth processor 900, configured to read the program in the memory 920, and perform the following processes:

files in a target directory, including the intent description file, are received by the second transceiver 910.

And deploying the intentions according to the intention description file.

A second transceiver 910 for receiving and transmitting data under the control of the fifth processor 900.

Wherein in fig. 12 the bus architecture may comprise any number of interconnected buses and bridges, in particular one or more fifth processors represented by the fifth processor 900, linked together with various circuits of the memory represented by the memory 920. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The second transceiver 910 may be a plurality of elements, including a transmitter and a second transceiver, providing a means for communicating with various other apparatus over a transmission medium. The fifth processor 900 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the fifth processor 900 when performing operations.

Optionally, the fifth processor 900 is further configured to read the program in the memory 920, and perform the following steps:

The network deployment device provided in the embodiment of the present application may execute the embodiment corresponding to the method in fig. 3, and the implementation principle and the technical effect are similar, which are not described herein again.

The embodiment of the invention also provides network deployment equipment. As the principle of the network deployment device to solve the problem is similar to the method shown in fig. 4 in the embodiment of the present application, the implementation of the network deployment device may refer to the implementation of the method, and repeated details are not repeated. As shown in fig. 13, the network deployment device according to the embodiment of the present application includes:

the sixth processor 1000, configured to read the program in the memory 1020, performs the following processes:

files in the target directory, including the intent description file, are received by the third transceiver 1010.

And deploying the intentions according to the intention description file.

A third transceiver 1010 for receiving and transmitting data under the control of the sixth processor 1000.

Wherein in fig. 12, the bus architecture may include any number of interconnected buses and bridges, with one or more sixth processors, represented by sixth processor 1000, and various circuits of memory, represented by memory 1020, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The third transceiver 1010 may be a plurality of elements, including a transmitter and a third transceiver, providing a means for communicating with various other apparatus over a transmission medium. The sixth processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 may store data used by the sixth processor 1000 when performing operations.

Optionally, the sixth processor 1000 is further configured to read a program in the memory 1020, and perform the following steps:

The network deployment device provided in the embodiment of the present application may execute the embodiment corresponding to the method in fig. 4, and the implementation principle and the technical effect are similar, which are not described herein again.

Furthermore, the computer-readable storage medium of the embodiments of the present application is used for storing a computer program, which can be executed by a processor to implement the steps in the method embodiment shown in fig. 2, or to implement the steps in the method embodiment shown in fig. 3, or to implement the steps in the method embodiment shown in fig. 4.

Those skilled in the art will appreciate that all or part of the steps of the method according to the above embodiments may be implemented by hardware associated with program instructions, and the program may be stored in a readable medium. An embodiment of the present invention further provides a readable storage medium, where a computer program is stored on the readable storage medium, and when the computer program is executed by a processor, any step in the method embodiments corresponding to fig. 2, or fig. 3, or fig. 4 may be implemented, and the same technical effect may be achieved, and in order to avoid repetition, details are not repeated here.

The storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method of network deployment, comprising:

2. The method of claim 1, wherein after the receiving the first data and before the distributing the first data, the method further comprises:

wherein the preset rules comprise at least one of:

3. The method of claim 2, wherein said distributing the first data to enable a distribution object to perform network deployment according to the first data comprises:

4. The method of claim 1, wherein after receiving the first data, the method further comprises:

5. The method of claim 4, wherein prior to sending the notification message to the distribution object, the method further comprises:

6. A method of network deployment, comprising:

and deploying the intentions according to the intention description file.

7. The network deployment method of claim 6, wherein prior to receiving the file in the target directory, the method further comprises:

8. A method of network deployment, comprising:

and carrying out closed-loop deployment according to the closed-loop flow file.

9. The network deployment method of claim 8, wherein prior to receiving the file in the target directory, the method further comprises:

and sending a second subscription request, wherein the second subscription request is used for subscribing a second notification message, and the second notification message is used for notifying a second distribution object of about to send the file in the target directory, and the file in the target directory is a closed-loop process file.

10. A network deployment device comprising a first transceiver,

the first transceiver is to:

11. A network deployment apparatus comprising a second transceiver and a second processor,

the second transceiver is to:

the second processor is configured to:

and deploying the intentions according to the intention description file.

12. A network deployment apparatus comprising a third transceiver and a third processor,

the third transceiver is to:

the third processor is configured to:

and carrying out closed-loop deployment according to the closed-loop flow file.

13. A network deployment device comprising: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor; the processor is configured to read a program in the memory to implement the steps in the network deployment method according to any one of claims 1 to 5; or, implementing the steps in the network deployment method of any of claims 6 to 7; or implementing the steps in the network deployment method of any of claims 8 to 9.

14. A readable storage medium storing a program, wherein the program, when executed by a processor, implements the steps in the network deployment method of any one of claims 1 to 5; or, as implementing the steps in the network deployment method of any of claims 6 to 7; or implementing the steps in the network deployment method of any of claims 8 to 9.