Network deployment method, apparatus and related device

Abstract

The application provides a network deployment method, device and related equipment, wherein the method comprises receiving first data, wherein the first data comprises an intent description file, distributing the first data, so that a distribution object performs network deployment according to the first data. In the embodiment of the application, after receiving the first data, the first data is distributed, so that the distribution object performs network deployment according to the first data. The first data comprises an intent description file. In this way, it is not necessary to manually select the intent description information corresponding to the network service after the network service design deployment is completed. The intent description file in the first data is directly distributed to the distribution object, so that the distribution object performs network deployment according to the intent description file. The process does not need manual participation, thereby improving the efficiency of network deployment.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer networks, and in particular to a network deployment method and device and related equipment. BACKGROUND

[0002] In the prior art, a network service design and deployment system, an intent process deployment system, and a closed-loop process deployment system for maintaining intent are three separate systems. After the network service design and deployment are completed, the intent description information corresponding to the network service is manually selected and the intent knowledge base is manually imported. If the closed-loop process for maintaining intent is also deployed, after the intent process is deployed, the closed-loop process description information corresponding to the intent description information is manually selected and the closed-loop instance is deployed according to the closed-loop process description information. This method requires manual intervention, the process is complex, and the efficiency is low. SUMMARY

[0003] Embodiments of the present application provide a network deployment method, device and related equipment, which solve the problem of low network deployment efficiency.

[0004] To achieve the above-mentioned purpose, in a first aspect, embodiments of the present application provide a network deployment method, comprising:

[0005] receiving first data, wherein the first data includes an intent description file, and the first data further includes at least one of a virtual network feature (VNF) package, a physical network feature (PNF) package, and a closed-loop process file, the intent description file corresponds to at least one of the VNF package and the PNF package, and the closed-loop process file corresponds to the intent description file;

[0006] distributing the first data to enable a distribution object to perform network deployment according to the first data.

[0007] In a second aspect, embodiments of the present application provide a network deployment method, comprising:

[0008] receiving files in a target directory, wherein the files in the target directory include an intent description file;

[0009] deploying intent according to the intent description file.

[0010] In a third aspect, embodiments of the present application provide a network deployment method, comprising:

[0011] receiving files in a target directory, wherein the files in the target directory include a closed-loop process file;

[0012] Deploy the closed-loop process according to the aforementioned closed-loop procedure document.

[0013] Fourthly, embodiments of this application provide a network deployment apparatus, including a first transceiver.

[0014] The first transceiver is used for:

[0015] Receive first data, wherein the first data includes an intent description file, and 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 process file, wherein the intent description file corresponds to at least one of the VNF packet and the PNF packet, and the closed-loop process file corresponds to the intent description file;

[0016] The first data is distributed so that the distribution object can deploy the network based on the first data.

[0017] Fifthly, embodiments of this application provide a network deployment apparatus, including a second transceiver and a second processor.

[0018] The second transceiver is used for;

[0019] Receive files in a target directory, including intent description files;

[0020] The second processor is used for:

[0021] Deploy the intent according to the intent description file.

[0022] Sixthly, embodiments of this application provide a network deployment apparatus, including a third transceiver and a third processor.

[0023] The third transceiver is used for:

[0024] Receive files in the target directory, including closed-loop process files;

[0025] The third processor is used for:

[0026] Deploy the closed-loop process according to the aforementioned closed-loop procedure document.

[0027] In a seventh aspect, embodiments of this application provide a network deployment device, including: a transceiver, a memory, a processor, and a program stored in the memory and executable on the processor; the processor is configured to read the program in the memory to implement the steps of the network deployment method as described in the first aspect; or, to implement the steps of the network deployment method as described in the second aspect; or, to implement the steps of the network deployment method as described in the third aspect.

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

[0029] In the embodiment of the present application, the first data is distributed after being received, so that the distribution object performs network deployment according to the first data, and the first data includes an intent description file. In this way, the intent description information corresponding to the network service does not need to be manually selected after the network service design deployment is completed, and the intent description file in the first data is directly distributed to the distribution object, so that the distribution object can perform network deployment according to the intent description file. The process does not need human intervention, thereby improving the efficiency of network deployment. BRIEF DESCRIPTION OF DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings of the specification are described as follows. Obviously, the following drawings are only embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0031] Figure 1 is a structural diagram of a network system to which the embodiments of the present application can be applied;

[0032] Figure 2 is one of the flowcharts of the network deployment method provided by the embodiments of the present application;

[0033] Figure 3 is another flowchart of the network deployment method provided by the embodiments of the present application;

[0034] Figure 4 is a third flowchart of the network deployment method provided by the embodiments of the present application;

[0035] Figure 5 is a fourth flowchart of the network deployment method provided by the embodiments of the present application;

[0036] Figure 6 is a fifth flowchart of the network deployment method provided by the embodiments of the present application;

[0037] Figure 7 is a sixth flowchart of the network deployment method provided by the embodiments of the present application;

[0038] Figure 8 is one of the structural diagrams of the network deployment apparatus provided by the embodiments of the present application;

[0039] Figure 9This is a second schematic diagram of the network deployment device provided in the embodiments of this application;

[0040] Figure 10 This is the third structural schematic diagram of the network deployment device provided in the embodiments of this application;

[0041] Figure 11 This is one of the structural diagrams of the network deployment equipment provided in this application;

[0042] Figure 12 This is the second structural diagram of the network deployment equipment provided in this application;

[0043] Figure 13 This is the third structural diagram of the network deployment equipment provided in this application. Detailed Implementation

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

[0045] In the embodiments of this invention, the terms "first," "second," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or devices. Additionally, the use of "and / or" in this application indicates at least one of the connected objects, such as A and / or B and / or C, representing seven possibilities: including A alone, B alone, C alone, both A and B present, both B and C present, both A and C present, and A, B, and C present.

[0046] Please see Figure 1 , Figure 1 This is a structural diagram of a network system to which the embodiments of this application can be applied, such as... Figure 1 As shown, it includes a network service deployment system 11, an intent execution system 12, and a closed-loop execution system 13. The network service deployment system 11 and the intent execution system 12 can communicate with each other, and the network service deployment system 11 and the closed-loop execution system 13 can also communicate with each other.

[0047] The following describes the network deployment method provided in the embodiments of the present invention.

[0048] Referring to Figure 2 , Figure 2 is one of flow diagrams of a network deployment method provided by embodiments of the present application. Figure 2 The network deployment method shown can be performed by a network service deployment system 11.

[0049] As shown in Figure 2 , the network deployment method can include the following steps:

[0050] Step 201, receiving first data, wherein the first data includes an intent description file, and 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 process file, the intent description file corresponds to at least one of the VNF package and the PNF package, and the closed loop process file corresponds to the intent description file;

[0051] In a specific implementation, the first data can be received by a designer in the network service deployment system 11. The intent description file mainly describes the intent and corresponding workflow supported by a certain network service or a certain individual virtual network function (VNF) or physical network function (PNF) in the network service according to a certain specification (including but not limited to TOSCA, JSON, YANG, RDFS, etc.), and places the description information related to the intent 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 process information for maintaining the intent, etc. The corresponding workflow is a business process that is already supported by the system or can be supported after the network service is deployed.

[0052] The closed loop process file for maintaining the intent mainly describes the corresponding closed loop process for maintaining the intent. The closed loop process information describing the closed loop process is stored in the same file or different files according to a certain specification (including but not limited to TOSCA / JSON / YANG / RDFS, etc.) to obtain the closed loop process file.

[0053] The above corresponding closed loop process information is divided into two cases. The first case is corresponding to an existing closed loop instance that has been deployed in the system. The closed loop process information here is mainly used to describe information such as name, ID, flag, etc. of the existing closed loop instance, so as to associate the intent with the existing closed loop instance. The second case is to describe a brand new closed loop process. At this time, the description information includes but is not limited to the closed loop process, parameter information corresponding to the closed loop, and corresponding workflow information, etc. The corresponding workflow is a business process that is already supported by the system or can be supported after the network service is deployed.

[0054] The VNF package and the PNF package include network service composition elements VNF and PNF, and network connections corresponding to the VNF and the PNF.

[0055] The intent can be divided into two categories according to the use scenario. The first category is a network service-specific intent. This type of intent depends on a specific network service and is supported by the network service or a single VNF / PNF in the network service. Therefore, the life cycle of the intent is strongly related to the life cycle of the network service. The second category is a general intent. This type of intent does not depend on any specific network service and is supported by multiple network services. The life cycle of the intent is not related to a specific network service.

[0056] In the scenario of the network service-specific intent, the first data can include a VNF package and / or a PNF package and an intent description file, or the first data can include a VNF package and / or a PNF package, an intent description file, and a closed-loop process file. In the scenario of the general intent, the first data can include an intent description file and a closed-loop process file.

[0057] In step 202, the first data is distributed, so that a distribution object performs network deployment according to the first data.

[0058] In a specific implementation, an action subject that performs the distribution can be an orchestrator in a network service deployment system. The distribution object can include an intent execution system and a closed-loop execution system. When the first data includes an intent description file, the distribution object includes the intent execution system, and the intent description file is distributed to the intent execution system. When the first data includes a closed-loop process file, the distribution object includes the closed-loop execution system, and the closed-loop process file is distributed to the closed-loop execution system.

[0059] The intent execution system can perform deployment of the intent according to the intent description file, the closed-loop execution system can perform deployment of the closed loop according to the closed-loop process file, and the network service deployment system can perform deployment of the network service according to the VNF package and the PNF package.

[0060] Before the first data is distributed, the first data can be stored in the network service deployment system or can not be stored.

[0061] In the embodiment of the present application, after the first data is received, the first data is distributed, so that a distribution object performs network deployment according to the first data. The first data includes an intent description file. In this way, it is not necessary to manually select the intent description information corresponding to the network service after the network service design and deployment are completed. The intent description file in the first data is directly distributed to the distribution object, so that the distribution object performs network deployment according to the intent description file. This process does not require manual participation, thereby improving the efficiency of network deployment.

[0062] Further, in the case that the first data further comprises a closed loop process file, without manually selecting the closed loop process description information corresponding to the intent description information after the deployment of the intent process, and deploying the closed loop instance according to the closed loop process description information, the closed loop process file in the first data is directly distributed to the distribution object, so that the network deployment is performed according to the closed loop process file, thereby the method provided by the embodiment of the present application can realize the automatic association of the network service deployment system, the intent execution system and the closed loop execution system, reduce the human intervention and the manual error, simplify the steps of the network service deployment, the intent deployment and the closed loop deployment of the intent, and better serve the automatic design, deployment and intent process support of the future network service.

[0063] Optionally, after receiving the first data, and before distributing the first data, the method further comprises:

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

[0065] wherein the preset rule comprises at least one of the following:

[0066] storing the intent description file into a first target directory of the target file, and the target directories comprise the first target directory;

[0067] storing the closed loop process file into a second target directory of the target file, and the target directories comprise the second target directory.

[0068] In the implementation, the first data can be stored into a target directory of a target file according to a preset rule before the first data is distributed. The storage location of the target file can be a designer of the network service deployment system. The second target directory can be a next-level directory of the first target directory, or a same-level directory of the first target directory.

[0069] In example one, the intent description file can be uniformly archived into an Intent directory of the NSD, and if the intent supports a single VNF / PNF, a next-level directory can be added, for example, Intent / vnf1 / . The closed loop process file can be placed in an Intent / control-loop directory, and the control-loop is a next-level directory of the intent. If the closed loop is for a specific VNF, a next-level directory can be added, for example, placed in Intent / vnf1 / control-loop. The file directory herein is only an example, and any directory organization form realized by using the method of the embodiment of the present application is within the protection scope of the patent.

[0070] The embodiment can facilitate the distribution object to search the target file according to the preset rule by storing the first data into the target directory of the target file according to the preset rule.

[0071] Optionally, the distributing the first data to enable the distribution object to perform network deployment according to the first data comprises:

[0072] sending the intent description file in the first target directory to a loader of an intent execution system to enable the intent execution system to perform deployment of the intent according to the intent description file;

[0073] 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 to enable the closed loop execution system to perform deployment of the closed loop according to the closed loop process file.

[0074] In a specific implementation, a process for distributing the intent description file and the closed loop process file can be added after the existing orchestrator service deployment workflow is completed. When the target file comprises the target directory, the first data is distributed to the distribution object; when the target file does not comprise the target directory, the first data is not distributed to the distribution object. Further, when the target file comprises the first target directory, the file stored in the first target directory is distributed to the intent execution system, and the distribution object comprises the intent execution system. When the target file comprises the second target directory, the closed loop process file is distributed to the closed loop execution system, and the distribution object comprises the closed loop execution system.

[0075] As an example, when the first data is stored in the storage mode of the above example one, the orchestrator can analyze whether the target file comprises the Intent directory or the control-loop directory under the Intent, and the control-loop is a subdirectory of the intent. If the corresponding directory exists, the distribution work of the corresponding description file is started. When the target file comprises the Intent directory and the Intent directory comprises the archive file, the archive file in the Intent directory, i.e., the intent description file, can be distributed to the loader of the intent execution system; when the target file comprises the control-loop directory under the Intent and the control-loop directory comprises the archive file, the archive file in the control-loop directory, i.e., the closed loop process file, can be distributed to the closed loop execution system. If the corresponding directory does not exist, the distribution of the intent description file and / or the closed loop process file is not needed, and the workflow ends.

[0076] Optionally, after the first data is received, the method further comprises:

[0077] in a case that the first data comprises the VNF package or the PNF package, performing network service deployment according to the VNF package or the PNF package;

[0078] in a case that the network service deployment is completed, sending a notification message to the distribution object, the notification message being used to notify the distribution object that a file in a target directory is about to be sent.

[0079] In specific implementation, the network service deployment system can perform network service deployment according to the VNF package and / or the PNF package. In a case that the network service deployment is completed, the orchestrator of the network service deployment system can send a notification message to the distribution object. The orchestrator of the network service deployment system can send the notification message in response to a subscription request of the distribution object for the notification message at a proper time, or directly send the notification message to the distribution object at a proper time. After receiving the notification message, the distribution object can prepare to receive the file in the target directory.

[0080] For example, in a case that the network service deployment is completed, a first notification message is sent to the loader of the intent execution system, which is used to notify the loader of the intent execution system that an intent description file under a first target directory is about to be sent to the loader. In a case that the intent deployment is completed, a second notification message is sent to the loader of the closed-loop execution system, which is used to notify the loader of the closed-loop execution system that a closed-loop process file under a second target directory is about to be sent to the loader.

[0081] In this embodiment, the notification message is sent to the distribution object after the network service deployment is completed, which can facilitate the distribution object to prepare to receive the target file.

[0082] Optionally, before the notification message is sent to the distribution object, the method further comprises:

[0083] receiving at least one of a first subscription request and a second subscription request, the first subscription request being used to subscribe to the first notification message, and the second subscription request being used to subscribe to the second notification message.

[0084] In specific implementation, the first subscription request and the second subscription request can be received by the orchestrator in the network service deployment system. The first notification message is used to notify a first distribution object that an intent description file in a first target directory is about to be sent. The first distribution object can be the loader of the intent execution system. The second notification message is used to notify a second distribution object that a closed-loop process file in a second target directory is about to be sent. The orchestrator in the network service deployment system needs to receive the first subscription request when the deployment of the intent is needed, and needs to receive the second subscription request when the deployment of the closed loop is needed.

[0085] The network deployment method in the embodiments of the present application receives first data and distributes the first data, so that a distribution object performs network deployment according to the first data, and the first data includes an intent description file. In this way, after the network service design deployment is completed, manual selection of the intent description information corresponding to the network service is not required, and the intent description file in the first data is directly distributed to the distribution object, so that the distribution object can perform network deployment according to the intent description file. The process does not require manual participation, thereby improving the efficiency of network deployment.

[0086] Referring to Figure 3 , Figure 3 is one of the flowcharts of the network deployment method provided in the embodiments of the present application. Figure 3 The network deployment method shown in the figure can be performed by the intent execution system 12.

[0087] As shown in the figure, Figure 3 The network deployment method can include the following steps:

[0088] Step 301, receiving a file in a target directory, wherein the file in the target directory includes an intent description file;

[0089] In specific implementation, the loader of the intent execution system can receive the file in the target directory. After receiving the file in the target directory, the file can be locally stored or not.

[0090] Step 302, deploying an intent according to the intent description file.

[0091] In specific implementation, if the first data is archived in the manner of Example 1, the loader of the intent execution system can extract the archive file under the Intent directory, mainly the intent description file, including the intent related to the network service and the intent related to the VNF / PNF in the network service.

[0092] Deploying the intent according to the intent description file, first, all the intent description files need to be parsed. After parsing, it is needed to determine whether the intent knowledge point corresponding to the intent description information already exists in the intent knowledge base. If it exists, it is considered that the intent knowledge point needs to be updated, and the information parsed from the new intent description file needs to be updated and reloaded. If it does not exist, it is considered that it is a brand-new intent knowledge point, and the parsed information needs to be imported into the intent knowledge base to form a new intent knowledge point.

[0093] The parsing of the above-mentioned intent file, the import of the intent information, and the generation of the intent knowledge belong to the existing functions of the intent execution system, and will not be described here.

[0094] Optionally, before the receiving of the file in the target directory, the method further includes:

[0095] sending a first subscription request, the first subscription request being used for subscribing to a first notification message, the first notification message being used for notifying a first distribution object that a file in a target directory is about to be sent, the file in the target directory including an intent description file.

[0096] The network deployment method in the embodiment of the present application receives first data and distributes the first data, so that a distribution object performs network deployment according to the first data, and the first data includes an intent description file. In this way, it is not necessary to manually select the intent description information corresponding to the network service after the network service design deployment is completed, and the intent description file in the first data is directly distributed to the distribution object, so that the distribution object performs network deployment according to the intent description file. The process does not need manual participation, thereby improving the efficiency of network deployment.

[0097] It should be noted that the embodiment is used as a device in an intent execution system corresponding to the method embodiment, and therefore, the related description of the method embodiment can be referred to, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be described here. Figure 2 The device in the intent execution system corresponding to the method embodiment, and therefore, the related description of the method embodiment can be referred to, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be described here. Figure 2 The device in the intent execution system corresponding to the method embodiment, and therefore, the related description of the method embodiment can be referred to, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be described here.

[0098] The device in the intent execution system corresponding to the method embodiment, and therefore, the related description of the method embodiment can be referred to, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be described here. Figure 4 Figure 4 is one of the flowcharts of the network deployment method provided by the embodiment of the present application. Figure 4 The network deployment method shown in the figure can be executed by the closed-loop execution system 13.

[0099] As shown in the figure, the network deployment method can include the following steps: Figure 4

[0100] Step 401, receiving a file in a target directory, the file in the target directory including a closed-loop process file;

[0101] When implemented, the loader of the closed-loop execution system can receive the file in the target directory. After receiving the file in the target directory, it can be locally stored, or it can not be locally stored.

[0102] Step 402, performing closed-loop deployment according to the closed-loop process file.

[0103] When implemented, if the first data is archived in the manner of Example 1, the loader of the closed-loop execution system can extract the archived files under each control-loop directory belonging to the Intent directory, mainly the closed-loop process description file, including the closed-loop process description file for maintaining the intent of the network service and the closed-loop process description file for maintaining the specific VNF / PNF intent in the network service. ​​

[0104] Parsing all the closed loop process description files described above, it can be judged according to the closed loop name, ID and other information whether the corresponding closed loop instance already exists. If it exists, the closed loop instance is directly reused, and the closed loop instance is configured according to the related information of the network service. If it does not exist, it is considered that it is a brand new closed loop process information, and the parsed information needs to be deployed in the closed loop execution system to form a new closed loop instance.

[0105] The parsed closed loop information is deployed in the closed loop execution system to generate the corresponding closed loop instance. This belongs to the existing function of the closed loop execution system, which will not be described here.

[0106] In the scenario of network service specific intent, in addition to the intent deployment process and closed loop deployment process described above, the deletion process is also included in the intent deployment and closed loop deployment, and the deletion process is also strongly related to the specific network service.

[0107] When the network service is deleted, the intent corresponding to the network service or corresponding to a certain VNF / PNF under the network service is also deleted synchronously. For the closed loop instance maintaining the intent, it needs to be judged whether the closed loop instance is also specific to the intent. If it is specific to the closed loop instance maintaining the intent and no other intent uses the closed loop instance, the closed loop instance is also deleted synchronously.

[0108] In the scenario of general intent, in addition to the intent deployment process and closed loop deployment process described above, the deletion process is not related to the specific network service. When the general intent needs to be deleted, for the closed loop instance maintaining the intent, it needs to be judged whether the closed loop instance is also specific to the intent. If it is specific to the closed loop instance maintaining the intent and no other intent uses the closed loop instance, the closed loop instance is also deleted synchronously.

[0109] The network deployment method in the embodiment of the application receives first data and distributes the first data, so that a distribution object performs network deployment according to the first data, and the first data includes an intent description file. In this way, it is not necessary to manually select the intent description information corresponding to the network service after the network service design deployment is completed, and the intent description file in the first data is directly distributed to the distribution object, so that the network deployment is performed according to the intent description file. The process does not need human participation, thereby improving the efficiency of network deployment.

[0110] It should be noted that the embodiment is the implementation of the device in the closed loop execution system corresponding to the method embodiment, and therefore, the related description of the method embodiment can be referred to, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be described here. Figure 2 The method embodiment corresponds to the implementation of the device in the closed loop execution system, and therefore, the related description of the method embodiment can be referred to, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be described here. Figure 2 The method embodiment corresponds to the implementation of the device in the closed loop execution system, and therefore, the related description of the method embodiment can be referred to, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be described here.

[0111] The various optional embodiments introduced in the embodiments of the present application can be combined with each other to be implemented, or can be implemented alone, and the embodiments of the present application do not limit this.

[0112] For the convenience of understanding, the following is illustrated as an example:

[0113] As an example, refer to Figure 5 In the scenario of network service specific intent, it is necessary to add function 1, i.e. func1, to the designer of the network service deployment system, add function 2, i.e. func2, to the orchestrator, add function 3, i.e. func3, to the intent execution system, and add function 4, i.e. func4, to the closed-loop execution system. The following is described in detail.

[0114] Among them, the func1 added to the designer of the network service deployment system mainly adds the following functional points:

[0115] 1) Designer input:

[0116] In this scheme, the designer input mainly includes the following three parts:

[0117] a. Network service component elements VNF / PNF and corresponding network connections;

[0118] b. Network service corresponding intent description file: mainly describe the intent supported by a certain network service or a single VNF / PNF in the network service and the corresponding workflow according to a certain specification (including but not limited to TOSCA / JSON / YANG / RDFS, etc.), and put the description information related to these intents into the same file or different files. The description information includes but is not limited to general expression description of intent, parameter information corresponding to the intent, implementation workflow or policy information corresponding to the intent, closed-loop process information for maintaining the intent, etc. The corresponding workflow is a business process that the system already supports or can support after the network service is deployed.

[0119] c. Closed-loop process file for maintaining intent: mainly used to describe the corresponding closed-loop process for maintaining the intent, and describe the closed-loop process according to a certain specification (including but not limited to TOSCA / JSON / YANG / RDFS, etc.), and put it into the same file or different files.

[0120] The corresponding closed loop process information is divided into two cases. The first is corresponding to the existing closed loop instance deployed in the system, at this time the closed loop process information here is mainly used to describe the existing closed loop instance, not limited to name, ID, logo and other information, so that the intention is associated with the existing closed loop instance. The second is to describe a new closed loop process, at this time these description information includes not limited to closed loop process, closed loop corresponding parameter information, corresponding workflow information, etc. Among them, the corresponding workflow is the business process supported by the system or supported after the network service is deployed.

[0121] 2) Designer output:

[0122] The main output of the designer is the network service deployment file, which includes VNF / PNF package, intention description file and closed loop process file.

[0123] 3) Designer workflow:

[0124] The design function of the network service is unchanged, and func1 is added to increase the import function of the network service corresponding intention description file and the closed loop process description file of maintaining intention. Among them, the intention information file is uniformly archived to the Intent directory of NSD, if it contains the intention supported by a single VNF / PNF, this place can increase the next level directory, such as Intent / vnf1 / . And the information related to the closed loop of maintaining intention can be placed in Intent / control-loop directory, if the closed loop is for a specific VNF, this place can increase the next level directory, for example, it can be placed in Intent / vnf1 / control-loop. The file directory here is only an example of implementing this scheme, and any directory organization form using the idea of this application is within the protection scope of this patent.

[0125] The Tosca network service file directory exported by the designer is as follows (it is assumed here that the intention description file and the closed loop description file are saved in yaml format):

[0126] The func2 added in the orchestrator of the network service deployment system mainly has the following new functions:

[0127] 1) Enhancement of orchestrator function:

[0128] The orchestrator of the service deployment system needs to adapt and adjust the existing workflow, and after the existing orchestrator service deployment workflow is completed, a process is added to process the distribution of intention description file and closed loop process description file.

[0129] The service deployment file distribution is parsed to determine whether it contains an Intent directory and a control-loop directory under the Intent. If the corresponding directories exist, the distribution of the corresponding description files is started. If the corresponding directories do not exist, the intent and closed-loop file distribution is not required, and the workflow ends, and the default service does not support the intent-related functions.

[0130] 2) Description file distribution:

[0131] After the network service deployment system completes the service deployment, the intent description file and the closed-loop process description file for maintaining the intent of the network service are distributed. In this application, the distribution objects include the loader of the intent execution system and the loader of the closed-loop execution system. The distribution of the intent description file to the loader of the intent execution system is only performed under the premise that the network deployment file after deployment completion contains the Intent directory and the archive file under the Intent directory (which can effectively reduce the workload of the loader of the intent execution system). The distribution of the closed-loop process description file to the loader of the closed-loop execution system is only performed under the premise that the network deployment file after deployment completion contains the Intent directory and the control-loop directory under the Intent directory and the archive file under the control-loop directory (which can effectively reduce the workload of the loader of the closed-loop execution system).

[0132] In this application, the intent execution system needs to add func3, which adds the following functional characteristics:

[0133] 1) Add network service subscription function:

[0134] The service subscriber needs to be the service deployment system orchestrator.

[0135] 2) Add subscription notification processing logic:

[0136] a. Once the network service deployment file distributed after the service orchestrator completes the deployment is received, local storage is performed.

[0137] b. The loader of the intent execution system extracts the archive file under the Intent directory of the network service deployment file, which is mainly the intent description file, including the intent related to the network service and the intent related to the VNF / PNF in the network service.

[0138] c. After parsing all the above intent description files, it is necessary to determine whether the intent knowledge corresponding to the intent description information already exists in the intent knowledge base. If it exists, it is considered that the intent knowledge needs to be updated, and needs to be updated and reloaded according to the information parsed after the new intent description file. If it does not exist, it is considered to be a new intent knowledge, and the parsed information needs to be imported into the intent knowledge base to form a new intent knowledge.

[0139] d. The parsing of the above intent file, the import of the intent information and the generation of the intent knowledge belong to the existing functions of the intent execution system, which will not be described here.

[0140] In this application, func4 needs to be added to the closed loop execution system, and the following new function features are added:

[0141] 1) Add network service subscription function:

[0142] Need to be a network service deployment system orchestrator service subscriber.

[0143] 2) Add subscription notification processing logic:

[0144] a. Once the network service deployment file distributed by the orchestrator after completing the deployment is received, it will be stored locally.

[0145] b. The loader of the closed loop execution system extracts the archive files under each control-loop directory under the Intent directory of the network service deployment file, mainly the closed loop process description file, including the closed loop process description file for maintaining the intent of the network service and the closed loop process description file for maintaining the specific VNF / PNF intent in the network service.

[0146] c. After parsing all the above closed loop process description files, it can be determined whether the corresponding closed loop instance already exists according to the closed loop name, ID, etc. If it exists, the closed loop instance is directly reused, and the closed loop instance is configured according to the related information of the network service. If it does not exist, it is considered to be a new closed loop process information, and the parsed information needs to be deployed in the closed loop execution system to form a new closed loop instance.

[0147] d. The parsed closed loop information is deployed in the closed loop execution system to generate the corresponding closed loop instance. These belong to the existing functions of the closed loop execution system, which will not be described here.

[0148] 5. Network service, intent knowledge point, closed loop instance deletion process:

[0149] For network service specific intents, in addition to the above deployment process, its deletion process is also strongly related to the specific network service.

[0150] When a network service is deleted, the intent corresponding to the network service or corresponding to a certain VNF / PNF under the network service is also deleted synchronously. For the closed loop instance maintaining the intent, it is needed to judge whether the closed loop instance is also specific to the intent. If it is specific to the closed loop instance maintaining the intent and no other intent is using the closed loop instance, the closed loop instance is also deleted synchronously.

[0151] As an example, see Figure 6 In the scenario of general intent, it is also needed to add func1 in the designer of the network service deployment system, add func2 in the orchestrator, add func3 in the intent execution system, and add func4 in the closed loop execution system, respectively. In this scenario, the intent is not related to a specific network service, so the deployment of the network service is not involved here. The scheme in this scenario focuses on associating the deployment of the intent flow and the deployment of the corresponding closed loop flow maintaining the intent together, and completes the deployment of the corresponding closed loop flow at the same time when the deployment of the intent flow is completed. The following is described in detail.

[0152] 1. func1:

[0153] The func1 added in the designer of the network service deployment system mainly adds the following functional points:

[0154] 1) Designer input:

[0155] In this scheme, the designer input mainly includes the following two parts:

[0156] a. General intent description file: mainly describe the general intent and the corresponding workflow according to a certain specification (including but not limited to TOSCA / JSON / YANG / RDFS, etc.), and put the description information related to the intent into the same file or different files. The description information includes but is not limited to the general expression description of the intent, the parameter information corresponding to the intent, the implementation workflow or policy information corresponding to the intent, the closed loop flow information for maintaining the intent, etc. The corresponding workflow is a business flow that the system has supported or can support after the deployment of the network service.

[0157] b. Closed loop flow description file for maintaining the intent, which is the same as the closed loop flow description file content in the scenario of network service specific intent, and is not described again.

[0158] 2) Designer output:

[0159] The main output of the designer is the intent knowledge and the corresponding closed loop flow deployment file.

[0160] 3) Designer workflow:

[0161] Add func1, add import function of general intent description file and maintenance intent closed loop process description file. Among them, the intent information file is uniformly archived in the Intent directory. And the information related to the closed loop of maintaining the intent can be placed in the Intent / control-loop directory. The file directory here is only an example of implementing this scheme, and any directory organization form that implements the idea of this application is within the protection scope of this patent.

[0162] The Tosca network service file directory exported by the designer is as follows (it is assumed here that the intent description file and the closed loop description file are saved in yaml format):

[0163] 2. func2:

[0164] The func2 added in the orchestrator of the network service deployment system mainly adds the following function points:

[0165] 1) Enhance the function of the orchestrator:

[0166] Here, the scheme is similar to the network service specific intent scenario, except that this place does not need the network deployment process.

[0167] Parse whether the distributed service deployment file contains the Intent directory and the control-loop directory under Intent. If the corresponding directory exists, start the distribution work of the corresponding description file.

[0168] 2) Description file distribution:

[0169] In this application, the objects of distribution include the loader of the intent execution system and the loader of the closed loop execution system. Among them, the distribution of the intent execution system loader will only be carried out under the premise that the file contains the Intent directory and the Intent directory contains the archived file. And the distribution of the closed loop execution system loader will only be carried out under the premise that the file contains the Intent directory and the subordinate directory has the control-loop directory and the control-loop directory contains the archived file.

[0170] 3. func3:

[0171] In this application, the intent execution system needs to add func3, which adds the following function characteristics:

[0172] 1) Add network service subscription function:

[0173] Need to be a service subscriber of the network service deployment system orchestrator.

[0174] 2) Add subscription notification processing logic:

[0175] The solution in the scenario of the network service specific intent is the same as above, and will not be described again.

[0176] 4. func4:

[0177] In this application, func4 needs to be added in the closed loop execution system, and the following new function features are added:

[0178] 1) Add network service subscription function:

[0179] The service subscriber needs to be the network service deployment system orchestrator.

[0180] 2) Add subscription notification processing logic:

[0181] The solution in the scenario of the network service specific intent is the same as above, and will not be described again.

[0182] 5. Deletion process of network service, intent knowledge point, and closed loop instance:

[0183] For a general intent, in addition to the deployment process described above, its deletion process is also irrelevant to a specific network service.

[0184] When the general intent needs to be deleted because it is no longer used, for the 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 the intent and no other intent uses the closed loop instance, the closed loop instance is also deleted synchronously.

[0185] As an example, we take creating an end-to-end slice business and creating a corresponding SLA guarantee intent as an example (it should be noted that this application scenario is only for example, and the embodiments of the present application are not limited to this) to introduce the specific implementation process of the embodiments of the present application, see Figure 7 , Figure 7 is a flowchart of the embodiments of the present application.

[0186] After receiving the slice business requirement, the VNF / PNF and corresponding network connection design, SLA guarantee intent design, and closed loop process design of the maintenance intent are obtained. According to the above files, the end-to-end slice network service deployment file is first determined, and the end-to-end slice network service deployment is performed according to the end-to-end slice network service deployment file. After the network service deployment is completed, the intent description file and the closed loop process file can be distributed, and the intent description file is parsed by the intent execution system to generate the intent knowledge point for the deployment of the intent; the closed loop process file is parsed by the closed loop execution system to generate the closed loop instance for the deployment of the closed loop.

[0187] After the above steps, the deployment of the end-to-end slice network service, the deployment of the corresponding intent knowledge of the end-to-end slice network service, and the deployment of the closed-loop process instance of maintaining the intent are completed. When the user inputs the SLA guarantee intent of the natural language description related to the end-to-end slice network service, the specific execution process is as follows:

[0188] 1. The parser of the intent execution system parses the natural language description of the intent input by the user, and obtains the corresponding intent knowledge in the intent knowledge base according to the parsed information.

[0189] 2. The intent execution system generates a corresponding intent instance according to the intent knowledge obtained in the above step and the parameter information provided in the input intent.

[0190] 3. The intent instance executes the corresponding workflow to realize the intent of the user.

[0191] 4. The guarantee workflow of the intent instance will call the deployed closed-loop instance to continuously monitor the intent of the user and verify whether the intent meets the expectation in real time, and take appropriate corrective measures when the expected intent is not reached.

[0192] Reference Figure 8 , Figure 8 is one of the structural diagrams of the network deployment apparatus provided by the embodiments of the present application. As shown in Figure 8 , the network deployment apparatus 500 includes a first transceiver 501 and a first processor 502, wherein

[0193] The first transceiver 501 is configured to receive first data, wherein the first data includes an intent description file, and 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 process file, the intent description file corresponds to at least one of the VNF package and the PNF package, and the closed-loop process file corresponds to the intent description file.

[0194] The first data is distributed so that a distribution object performs network deployment according to the first data.

[0195] Optionally, the first processor 502 is configured to store the first data into a target directory of a target file according to a preset rule.

[0196] The preset rule includes at least one of the following:

[0197] The intent description file is stored into a first target directory in the target file, and the target directory includes the first target directory.

[0198] The closed-loop process file is stored into a second target directory in the target file, and the target directory includes the second target directory.

[0199] Optionally, the first transceiver 501 is further configured to send the intent description file in the first target directory to a loader of an intent execution system, so that the intent execution system deploys an intent according to the intent description file.

[0200] Alternatively, when the first data comprises 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 deploys a closed loop according to the closed loop process file.

[0201] Optionally, the first processor 502 is further configured to, when the first data comprises the VNF package or the PNF package, deploy a network service according to the VNF package or the PNF package.

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

[0203] Optionally, the first transceiver 501 is further configured to receive at least one of a first subscription request and a second subscription request, the first subscription request being used to subscribe to a first notification message, and the second subscription request being used to subscribe to a second notification message.

[0204] The network deployment apparatus 500 can realize various processes of the method embodiments of the present application Figure 2 and achieve the same beneficial effects. To avoid repetition, details are not described here.

[0205] Referring to Figure 9 , Figure 9 is one of the structural diagrams of the network deployment apparatus provided by the embodiments of the present application. As shown in Figure 9 , the network deployment apparatus 600 comprises a second transceiver 601 and a second processor 602, wherein

[0206] The second transceiver 601 is configured to receive a file in a target directory, the file in the target directory comprising an intent description file.

[0207] The second processor 602 is configured to deploy an intent according to the intent description file.

[0208] Optionally, the second transceiver 601 is further configured to send a first subscription request, the first subscription request being used to subscribe to a first notification message, the first notification message being used to notify a first distribution object that a file in the target directory is about to be sent, the file in the target directory comprising an intent description file.

[0209] The network deployment apparatus 600 can implement the embodiments of the present application Figure 3 The various processes of the method embodiments, and achieve the same beneficial effects, in order to avoid repetition, will not be repeated here.

[0210] Referring to Figure 10 , Figure 10 is one of the structural diagrams of the network deployment apparatus provided by the embodiments of the present application. As shown in Figure 10 , the network deployment apparatus 700 includes a third transceiver 701 and a third processor 702, wherein

[0211] The third transceiver 701 is configured to receive files in a target directory, wherein the files in the target directory include a closed-loop process file.

[0212] The third processor 702 is configured to perform closed-loop deployment according to the closed-loop process file.

[0213] Optionally, the third transceiver 701 is further configured to send a second subscription request, wherein 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 the files in the target directory, including the closed-loop process file, are about to be sent.

[0214] The network deployment apparatus 700 can implement the embodiments of the present application Figure 4 The various processes of the method embodiments, and achieve the same beneficial effects, in order to avoid repetition, will not be repeated here.

[0215] The embodiments of the present application also provide a network deployment device. Since the principle of the network deployment device solving the problem is similar to the method in the embodiments of the present application Figure 2 , the implementation of the network deployment device can be referred to the implementation of the method, and the repeated parts will not be repeated. As shown in Figure 11 , the network deployment device of the embodiments of the present application includes:

[0216] The fourth processor 800 is configured to read the program in the memory 820 and execute the following processes:

[0217] Distribute the first data through the first transceiver 810, so that the distribution object performs network deployment according to the first data, or receive the first data, wherein the first data includes an intent description file, and 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 process file, the intent description file corresponds to at least one of the VNF package and the PNF package, and the closed-loop process file corresponds to the intent description file;

[0218] The first transceiver 810 is configured to receive and send data under the control of the fourth processor 800.

[0219] wherein, in Figure 8 The bus architecture can include any number of interconnected buses and bridges, specifically the various circuitry of the one or more fourth processors 800 and memory 820 represented by the fourth processor 800. The bus architecture can also link various other circuitry, such as peripheral devices, voltage regulators, and power management circuitry, which are well known in the art and thus, not further described herein. The bus interface provides an interface. The first transceiver 810 can 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 can store data used by the fourth processor 800 in executing operations.

[0220] Optionally, the fourth processor 800 is further configured to read a program in the memory 820 and perform the following steps:

[0221] store the first data into a target directory of a target file according to a preset rule;

[0222] wherein, the preset rule comprises at least one of the following:

[0223] store the intent description file into a first target directory of the target file, the target directory comprising the first target directory;

[0224] store the closed loop process file into a second target directory of the target file, the target directory comprising the second target directory.

[0225] Optionally, the fourth processor 800 is further configured to send the intent description file in the first target directory to a loader of an intent execution system, so that the intent execution system deploys an intent according to the intent description file;

[0226] Or, when the first data comprises the closed loop process file, 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 deploys a closed loop according to the closed loop process file.

[0227] Optionally, the fourth processor 800 is further configured to, in a case where the first data comprises the VNF package or the PNF package, deploy a network service according to the VNF package or the PNF package;

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

[0229] Optionally, the first transceiver 810 is further configured to receive at least one of a first subscription request and a second subscription request, the first subscription request being used to subscribe to the first notification message, and the second subscription request being used to subscribe to the second notification message.

[0230] The network deployment device provided by the embodiments of the present application can execute the method embodiments, and the implementation principles and technical effects are similar, and thus the embodiments will not be described here.

[0231] The embodiments of the present application further provide a network deployment device. Since the principle of solving problems by the network deployment device is similar to the method in the embodiments of the present application, Figure 3 the implementation of the network deployment device can be referred to the implementation of the method, and the repeated parts will not be described here. As shown in the figure, the network deployment device of the embodiments of the present application comprises: Figure 12

[0232] The fifth processor 900 is configured to read programs in the memory 920 and execute the following processes:

[0233] The second transceiver 910 is configured to receive files in a target directory under the control of the fifth processor 900, and the files in the target directory comprise an intent description file.

[0234] Deploying the intent according to the intent description file.

[0235] The second transceiver 910 is configured to receive and send data under the control of the fifth processor 900.

[0236] In the figure, Figure 12 The bus architecture can comprise any number of interconnecting buses and bridges, and the various circuitry represented by the fifth processor 900 and the memory 920 is linked by the bus architecture, which is well known in the art, and thus will not be further described here. The bus interface provides an interface. The second transceiver 910 can be a plurality of elements, that is, it comprises a transmitter and a second transceiver, which provides a unit for communicating with various other devices on a transmission medium. The fifth processor 900 is responsible for managing the bus architecture and general processing, and the memory 920 can store data used by the fifth processor 900 when performing operations.

[0237] Optionally, the fifth processor 900 is further configured to read programs in the memory 920 and execute the following steps:

[0238] ​The first subscription request is sent, and the first subscription request is used to subscribe to a first notification message, the first notification message is used to notify a first distribution object that a file in the target directory is about to be sent, and the file in the target directory includes an intent description file.

[0239] The network deployment device provided by the embodiments of the present application can perform Figure 3 The embodiments of the method have similar implementation principles and technical effects, and thus the embodiments of the network deployment device will not be described here.

[0240] The embodiments of the present application also provide a network deployment device. Since the principle of solving the problem by the network deployment device is similar to the method in the embodiments of the present application Figure 4 , the implementation of the network deployment device can be referred to the implementation of the method, and the repeated parts will not be described here. As shown in the figure, Figure 13 the network deployment device of the embodiments of the present application comprises:

[0241] The sixth processor 1000 is configured to read a program in the memory 1020 and perform the following processes:

[0242] The file in the target directory is received through the third transceiver 1010, and the file in the target directory includes the intent description file.

[0243] The deployment of the intent is performed according to the intent description file.

[0244] The third transceiver 1010 is configured to receive and send data under the control of the sixth processor 1000.

[0245] In the figure, Figure 12 , the bus architecture can include any number of interconnected buses and bridges, and various circuit links of one or more sixth processors represented by the sixth processor 1000 and the memory represented by the memory 1020 are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage stabilizers, and power management circuits, which are well known in the art, and thus they will not be further described herein. The bus interface provides an interface. The third transceiver 1010 can be multiple elements, that is, it includes a transmitter and a third transceiver, and provides a unit for communicating with various other devices on a transmission medium. The sixth processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 can store data used by the sixth processor 1000 when performing operations.

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

[0247] Send a first subscription request, which is used to subscribe to a first notification message. The first notification message is used to notify a first distribution object that a file in the target directory is about to be sent, and the file in the target directory includes an intent description file.

[0248] The network deployment device provided in this application embodiment can perform... Figure 4 The implementation principles and technical effects of the corresponding embodiments of the method are similar, and will not be described again here.

[0249] Furthermore, the computer-readable storage medium of this application embodiment is used to store a computer program, which can be executed by a processor to implement as follows: Figure 2 The various steps in the method embodiments shown, or implementations such as Figure 3 The various steps in the method embodiments shown, or implementations such as Figure 4 Each step in the method embodiment shown.

[0250] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by hardware related to program instructions, and the program can be stored in a readable medium. The present invention also provides a readable storage medium storing a computer program, which, when executed by a processor, can implement the above-described methods. Figure 2 ,or Figure 3 ,or Figure 4 Any step in the corresponding method embodiment can achieve the same technical effect, and will not be repeated here to avoid repetition.

[0251] The storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0252] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A network deployment method, characterized by, The method comprises the following steps: receiving first data, wherein the first data comprises an intent description file, the first data further comprises a virtual network function (VNF) package or a physical network function (PNF) package, and a closed-loop process file, the intent description file corresponds to the VNF package or the PNF package, and the closed-loop process file corresponds to the intent description file; storing the first data in a target directory of a target file according to a preset rule, wherein the preset rule comprises at least one of the following: storing the intent description file in a first target directory in the target file, the target directory comprising the first target directory; and storing the closed-loop process file in a second target directory in the target file, the target directory comprising the second target directory; distributing the first data to enable a distribution object to perform network deployment according to the first data, comprising: sending the intent description file in the first target directory to a loader of an intent execution system to enable the intent execution system to perform deployment of an intent according to the intent 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 to enable the closed-loop execution system to perform deployment of a closed loop according to the closed-loop process file.

2. The method of claim 1, wherein, After the receiving first data, the method further comprises: when the first data comprises the VNF package or the PNF package, performing network service deployment according to the VNF package or the PNF package; when the network service deployment is completed, sending a notification message to the distribution object, the notification message being used to notify the distribution object that a file in a target directory is about to be sent.

3. The method of claim 2, wherein, Before the sending a notification message to the distribution object, the method further comprises: receiving at least one of a first subscription request and a second subscription request, the first subscription request being used to subscribe to a first notification message, and the second subscription request being used to subscribe to a second notification message.

4. A network deployment method characterized by, The method comprises the following steps: receiving a file in a target directory, the file in the target directory comprising an intent description file, the intent description file corresponding to a VNF package or a PNF package, and a closed-loop process file corresponding to the intent description file; performing deployment of an intent according to the intent description file; wherein the intent description file is a file stored in the target directory according to a preset rule, the preset rule comprising at least one of the following: storing the intent description file in a first target directory in a target file, the target directory comprising the first target directory; and storing the closed-loop process file in a second target directory in the target file, the target directory comprising the second target directory. Before the receiving a file in a target directory, the method further comprises:

5. The network deployment method of claim 4, wherein, sending a first subscription request, the first subscription request being used to subscribe to a first notification message, the first notification message being used to notify a first distribution object that a file in the target directory is about to be sent, the file in the target directory comprising an intent description file. The method comprises the following steps:

6. A network deployment method characterized by, ​ receive files in a target directory, the files in the target directory including a closed loop procedure file, the closed loop procedure file corresponding to an intent description file, the intent description file corresponding to a VNF package or a PNF package; perform closed loop deployment according to the closed loop procedure file; wherein the closed loop procedure file is stored in the files in the target directory according to a preset rule, the preset rule including at least one of the following: storing the intent description file in a first target directory in the target file, the target directory including the first target directory; storing the closed loop procedure file in a second target directory in the target file, the target directory including the second target directory.

7. The network deployment method of claim 6, wherein, Before the receiving the files in the target directory, the method further includes: sending a second subscription request, the second subscription request being used for subscribing to a second notification message, the second notification message being used for notifying a second distribution object that the files in the target directory, the files in the target directory being closed loop procedure files, are about to be sent.

8. A network deployment apparatus, characterized by comprise a first transceiver, the first transceiver is configured to: receive first data, wherein the first data includes an intent description file, the first data further includes a virtual network function (VNF) package or a physical network function (PNF) package, and a closed loop procedure file, the intent description file corresponding to the VNF package or the PNF package, and the closed loop procedure file corresponding to the intent description file; store the first data in a target directory of a target file according to a preset rule, wherein the preset rule includes at least one of the following: storing the intent description file in a first target directory in the target file, the target directory including the first target directory; and storing the closed loop procedure file in a second target directory in the target file, the target directory including the second target directory; distribute the first data to enable a distribution object to perform network deployment according to the first data, including: sending the intent description file in the first target directory to a loader of an intent execution system to enable the intent execution system to perform intent deployment according to the intent description file; or, when the first data includes the closed loop procedure file, sending the closed loop procedure file in the second target directory to a loader of a closed loop execution system to enable the closed loop execution system to perform closed loop deployment according to the closed loop procedure file.

9. A network deployment apparatus, characterized by comprise a second transceiver and a second processor, the second transceiver is configured to: receive files in a target directory, the files in the target directory including an intent description file, the intent description file corresponding to a VNF package or a PNF package, and a closed loop procedure file corresponding to the intent description file; the second processor is configured to: perform intent deployment according to the intent description file; perform closed loop deployment according to the closed loop procedure file. The intent description file is a file stored in the target directory according to a preset rule, and the preset rule includes at least one of the following: storing the intent description file in a first target directory in the target file, and the target directory includes the first target directory; and storing the closed loop process file in a second target directory in the target file, and the target directory includes the second target directory.

10. A network deployment apparatus, characterized by The third transceiver and the third processor are included, The third transceiver is configured to: receive a file in a target directory, the file in the target directory including a closed loop process file corresponding to an intent description file corresponding to a VNF package or a PNF package; The third processor is configured to: perform closed loop deployment according to the closed loop process file. The closed loop process file is a file stored in the target directory according to a preset rule, and the preset rule includes at least one of the following: storing the intent description file in a first target directory in the target file, and the target directory includes the first target directory; and storing the closed loop process file in a second target directory in the target file, and the target directory includes the second target directory.

11. A network deployment device comprising: The transceiver, the memory, the processor, and the program stored in the memory and executable on the processor; characterized in that the processor is configured to read the program in the memory to implement the steps in the network deployment method according to any one of claims 1 to 3; or implement the steps in the network deployment method according to any one of claims 4 to 5; or implement the steps in the network deployment method according to any one of claims 6 to 7.

12. A readable storage medium for storing a program, characterized in that, The program is executed by the processor to implement the steps in the network deployment method according to any one of claims 1 to 3; or implement the steps in the network deployment method according to any one of claims 4 to 5; or implement the steps in the network deployment method according to any one of claims 6 to 7.

Images