METHOD FOR UPDATING NETWORK SERVICE DESCRIPTOR NSD AND APPARATUS

Abstract

The present invention relates to methods for updating an NSD and an apparatus. One method includes: receiving, by an NFVO, an NSD update request from a transmit end; and sending to an NSD coordinator an NSD update instruction carrying a to-be-updated NSD, so that the NSD coordinator updates the NSD, and the NSD coordinator updates the NSD according to the received NSD update instruction. The other method includes: when receiving a trigger message, obtaining, by an NFVO, an NSD in which a source VNF is located, the trigger message is used to indicate that a status of a VNF is changed to disabled, and the source VNF is a VNF whose status is changed to disabled; and sending to an NSD coordinator an NSD update instruction carrying the NSD, so that the NSD coordinator updates the NSD according to the received NSD update instruction.

Claims

1. A network functions virtualization orchestrator (NFVO), comprising: a receiver, configured to receive a network service descriptor (NSD) update request from a transmit end; and a transmitter, configured to send to a NSD coordinator an NSD update instruction carrying a to-be-updated NSD, so that the NSD coordinator updates the NSD.

2. The NFVO according to claim 1, wherein the NSD update request carries the NSD; or the NSD update request carries an NSD identifier corresponding to the NSD; and the NFVO further comprises a processor, configured to obtain the NSD according to the NSD identifier.

3. The NFVO according to claim 2, wherein the NSD update request further carries a source virtualized network function (VNF) identifier and a target VNF identifier; the obtaining unit is further configured to: obtain a target VNF package corresponding to the target VNF identifier; and wherein the NSD update instruction further carries the target VNF package and the source VNF identifier.

4. The NFVO according to claim 1, further comprising a processor configured to: determine that the transmit end is authorized to send the NSD update request.

5. The NFVO according to claim 2, wherein the transmitter is further configured to: send to a network service (NS) catalog functional entity a notification message carrying the NSD identifier, wherein the notification message is used to instruct the NS catalog functional entity to record a status of the NSD corresponding to the NSD identifier as disabled.

6. The NFVO according to claim 2, wherein the receiver is further configured to: receive an NSD update complete message from the NSD coordinator after updating the NSD is finished; and add the target VNF identifier to the NSD update complete message; and the transmitter is further configured to send to a VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, so that the VNF catalog functional entity updates a status of a target VNF corresponding to the target VNF identifier.

7. The NFVO according to claim 6, wherein the processor is configured to: operate the target VNF package, and instantiate the target VNF to run the target VNF; obtain a source VNF corresponding to the source VNF identifier; and switch data running on the source VNF corresponding to the source VNF identifier to the running target VNF to run.

8. The NFVO according to claim 6, wherein the receiver is further configured to: receive a status update complete message of the target VNF from the VNF catalog functional entity; and the transmitter is further configured to send the NSD update complete message to a transmit end after the status update complete message of the target VNF is received.

9. A network functions virtualization orchestrator (NFVO), comprising: a receiver, configured to receive a trigger message, wherein the trigger message is used to indicate that a status of a source virtualized network function (VNF) is changed to disabled; a processor, configured to obtain a network service descriptor (NSD) in which the source VNF is located; and a transmitter, configured to send to an NSD coordinator an NSD update instruction carrying the NSD, so that the NSD coordinator updates the NSD.

10. The NFVO according to claim 9, wherein the receiver is further configured to: receive an update confirm message from a VNF catalog functional entity, wherein the update confirm message is used to notify the NFVO that the NSD can be updated.

11. The NFVO according to claim 10, wherein the update confirm message carries NSD update policy information, and the NSD update policy information is used to indicate how the NSD is updated.

12. The NFVO according to claim 9, wherein the processor is further configured to: obtain a target VNF package and an identifier of the source VNF; wherein the NSD update instruction further carries the target VNF package and the identifier of the source VNF.

13. The NFVO according to claim 12, wherein the receiver is further configured to: receive an NSD update complete message from the NSD coordinator after updating the NSD is finished; and the processor is configured to obtain a target VNF identifier corresponding to the target VNF package, and add the target VNF identifier to the NSD update complete message; and the transmitter is further configured to send to a VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, so that the VNF catalog functional entity updates a status of a target VNF corresponding to the target VNF identifier.

14. The NFVO according to claim 13, wherein the processor is further configured to: operate the target VNF package, and instantiate the target VNF to run the target VNF; and switch data running on the source VNF corresponding to the identifier of the source VNF to the running target VNF to run.

15. The NFVO according to claim 13, wherein the receiver is further configured to: receive a status update complete message of the target VNF from the VNF catalog functional entity; and the transmitter is further configured to send the NSD update complete message to a transmit end after the status update complete message of the target VNF is received.

16. A network service descriptor (NSD) coordinator, comprising: a receiver, configured to receive an NSD update instruction that carries an NSD from a network functions virtualization orchestrator (NFVO); and a processor, configured to update the NSD according to the NSD update instruction.

17. The NSD according to claim 16, wherein the NSD update instruction further carries a target virtualized network function (VNF) package and a source VNF identifier; and the processor is configured to: determine a configuration parameter that is corresponding to the source VNF identifier and in the NSD; obtain a parameter value that is corresponding to the configuration parameter and in the target VNF package; and replace an initial parameter value corresponding to the configuration parameter with the determined parameter value.

18. The NSD according to claim 16, wherein the NSD further comprises a transmitter and the transmitter is configured to: send an NSD update complete message to the NFVO; and send to a network service (NS) catalog functional entity a notification message carrying an updated NSD, wherein the notification message is used to notify the NS catalog functional entity that a status of the updated NSD is enabled.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0121] FIG. 1 is a flowchart for updating an NSD according to an embodiment of the present invention;

[0122] FIG. 2 is another flowchart for updating an NSD according to an embodiment of the present invention;

[0123] FIG. 3 is still another flowchart for updating an NSD according to an embodiment of the present invention;

[0124] FIG. 4 is a flowchart for updating an NSD according to an embodiment of the present invention;

[0125] FIG. 5A is a schematic functional structural diagram of an NFVO according to an embodiment of the present invention;

[0126] FIG. 5B is another schematic functional structural diagram of an NFVO according to an embodiment of the present invention;

[0127] FIG. 6A is still another schematic functional structural diagram of an NFVO according to an embodiment of the present invention;

[0128] FIG. 6B is yet another schematic functional structural diagram of an NFVO according to an embodiment of the present invention;

[0129] FIG. 7A is a schematic functional structural diagram of an NSD coordinator according to an embodiment of the present invention; and

[0130] FIG. 7B is another schematic functional structural diagram of an NSD coordinator according to an embodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

[0131] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the following clearly describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0132] The following explains some terms in this application, so as to facilitate understanding by a person skilled in the art.

[0133] Main function modules of an NFV E2E (End to End) are as follows:

[0134] OSS (Operations Support System)/BSS (Base Station Subsystem): used to initiate a service request to an NFVO and a request for a service-required resource, and responsible for troubleshooting.

[0135] NFVO: responsible for orchestrating and managing resources according to an OSS/BSS service request to implement an NFV service and monitor a VNF or NFVI (NFV infrastructure) resource and running status information thereof in real time.

[0136] VNFM (Virtualized Network Function Manager, VNF manager): responsible for managing a VNF life cycle, such as a start time, time to live, and VNF running status information.

[0137] VIM (virtualized infrastructure manager): responsible for managing and allocating an NFVI resource, and monitoring and collecting NFVI running status information.

[0138] EM (element manager): responsible for managing an element, including performance monitoring, service configuration, and the like of the element.

[0139] VNF catalog functional entity: used to store and manage VNF information.

[0140] NS catalog functional entity: used to store NS information and manage NS deployment template information.

[0141] NFV instance repository: used to store all VNF instances and information about the NS instances.

[0142] NFVI resource repository: used to store available/reserved/allocated resource information of an NFVI.

[0143] Related interfaces of the NFV E2E architecture are as follows:

[0144] Ve-Vnfm-em interface: used to exchange information between the EM and the VNFM, including information related to VNF instance query, VNF instance update, and the like.

[0145] Ve-Vnfm-em interface: used to exchange information between the VNF and the VNFM, including information related to VNF instance query, VNF instance update, and the like.

[0146] Os-Ma-nfvo interface: used to exchange information between the OSS/BSS and the NFVO, including information related to NSD and VNF package management, NS instance life time management, and the like.

[0147] Nf-Vi interface: used to exchange information between the VIM and the NFVI, including information related to VM resource allocation, VM migration, inter-VM link creation, and the like.

[0148] Or-Vnfm interface: used to exchange information between the NFVO and the VNFM, including information related to NFVI resource authorization and authentication, VNF instantiation, and the like.

[0149] Or-Vi interface: used to exchange information between the NFVO and the VIM, including information related to NFVI resource reservation, NFVI resource allocation, and the like.

[0150] Vi-Vnfm interface: used to exchange information between the VIM and the VNFM, including information related to NFVI resource reservation information query, NFVI resource allocation and resource release, and the like.

[0151] “Multiple” refers to two or more. The term “and/or” describes an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. The character “/” generally indicates an “or” relationship between the associated objects.

[0152] In the following, preferred embodiments of the present invention are described in detail with reference to the accompanying drawings of the specification. It should be understood that the preferred embodiments described herein are merely used to illustrate and explain the present invention, but are not intended to limit the present invention. In addition, the embodiments of the present application and features in the embodiments may be mutually combined in a case in which they do not conflict with each other.

[0153] Referring to FIG. 1, in an embodiment of the present invention, a process for updating an NSD is as follows:

[0154] Step 100: An NFVO receives an NSD update request sent by a transmit end.

[0155] Step 110: The NFVO sends to an NSD coordinator an NSD update instruction carrying a to-be-updated NSD, so that the NSD coordinator updates the NSD.

[0156] In this embodiment of the present invention, the transmit end may be an OSS or a BSS, or may be another functional entity, and details are not described herein.

[0157] In this embodiment of the present invention, optionally, the NSD update request may directly carry the NSD, or may be in the following manner:

[0158] The NSD update request carries an NSD identifier corresponding to the NSD; and

[0159] after the NFVO receives the NSD update request and before the NFVO sends the NSD update instruction, the process further includes:

[0160] The NFVO obtains the NSD according to the NSD identifier.

[0161] That is, the NSD may be directly sent to the NFVO by the transmit end, or the NSD identifier may be sent to the NFVO by the transmit end, and the NFVO obtains the NSD according to the NSD identifier.

[0162] Updating the NSD may be updating a configuration parameter of a VNF in the NSD, that is, relates to a configuration parameter of a source VNF and a configuration parameter of a target VNF. Therefore, in this embodiment of the present invention, the NSD update request further carries a source virtualized network function VNF identifier and a target VNF identifier. Only in this way, the NSD coordinator can know a configuration parameter of a VNF is to be used to replace a configuration parameter of another VNF.

[0163] Further, in this embodiment of the present invention, before the NFVO sends to the NSD coordinator the NSD update instruction, the process further includes the following operation:

[0164] The NFVO obtains a target VNF package corresponding to the target VNF identifier.

[0165] When the NFVO sends to the NSD coordinator the NSD update instruction, optionally, the following manner may be used:

[0166] The NFVO sends to the NSD coordinator the NSD update instruction, wherein the NSD update instruction further carries the target VNF package and the source VNF identifier.

[0167] In this embodiment of the present invention, to improve security, further, before the NFVO sends to the NSD coordinator the NSD update instruction, the process further includes the following operation:

[0168] The NFVO determines that the transmit end is authorized to send the NSD update request. That is, the transmit end is authorized and authenticated.

[0169] Certainly, integrity of the request sent by the transmit end further needs to be authenticated. These are all relatively well-known technologies. Therefore, details are not described herein.

[0170] The configuration parameter of the source VNF in the to-be-updated NSD may be tampered with due to viruses or attacks. In this case, if a status of an NSD that is recorded in an NS catalog functional entity is still enabled, a potential risk exists. Therefore, in this embodiment of the present invention, further, after the NFVO receives the NSD update request sent by the transmit end, the process further includes the following operation:

[0171] sending the NS catalog functional entity a notification message carrying the NSD identifier, where the notification message is used to instruct the NS catalog functional entity to record a status of the NSD corresponding to the NSD identifier as disabled. In this way, an NSD that is not updated is not to be used.

[0172] Current usage status information of the VNF package is recorded in a VNF catalog, and if the status of the NSD changes, the VNF catalog needs to be instructed to update a status of the VNF package. Therefore, in this embodiment of the present invention, further, after the NFVO sends to the NSD coordinator the NSD update instruction, the process further includes the following operations:

[0173] receiving an NSD update complete message that is sent by the NSD coordinator after finishing updating the NSD;

[0174] adding the target VNF identifier to the NSD update complete message; and

[0175] sending to a VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, so that the VNF catalog functional entity updates a status of a target VNF corresponding to the target VNF identifier.

[0176] In this embodiment of the present invention, an NS may be instantiated and is running. In this case, the NSD and some NS elements need to be updated. Therefore, after the NFVO receives the NSD update complete message, the process further includes the following operations:

[0177] operating the target VNF package, and instantiating the target VNF to run the target VNF;

[0178] obtaining a source VNF corresponding to the source VNF identifier; and

[0179] switching data running on the source VNF corresponding to the source VNF identifier to the running target VNF to run.

[0180] In this embodiment of the present invention, after the NFVO sends to the VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, the process further includes the following operations:

[0181] receiving a status update complete message of the target VNF that is returned by the VNF catalog functional entity; and

[0182] sending the NSD update complete message to a transmit end after the status update complete message of the target VNF is received.

[0183] The status of the NSD mentioned above is enabled and disabled. Certainly, the status of the NSD is not limited to the foregoing two states. In this case, there may be another state, such as delete pending.

[0184] The NSD includes various types of content, and the foregoing description uses VNF replacement as an example. Certainly, in actual application, updating the NSD may be replacing a VL (virtual link) or another component in the NSD. An update process is similar to a VNF replacement process, and details are not described herein.

[0185] The foregoing description indicates that the NFVO sends the NSD update instruction to the NSD coordinator after the transmit end sends the NSD update request to the NFVO. Certainly, in actual application, another trigger condition may be used. Therefore, another method for updating an NSD is provided. As shown in FIG. 2, a specific process is as follows:

[0186] Step 200: When receiving a trigger message, an NFVO obtains an NSD in which a source VNF is located, where the trigger message is used to indicate that a status of a VNF is changed to disabled, and the source VNF is a VNF whose status is changed to disabled.

[0187] Step 210: The NFVO sends to an NSD coordinator an NSD update instruction carrying the NSD, so that the NSD coordinator updates the NSD.

[0188] In this embodiment of the present invention, the trigger message may come from a VNFM, a VIM, or another functional entity.

[0189] In this embodiment of the present invention, there are multiple reasons that the status of the VNF is changed to disabled. For example, the VNF is damaged.

[0190] In this embodiment of the present invention, to improve security, after receiving the trigger message, the NFVO does not instantly send the NSD update instruction to the NSD coordinator, but before the NFVO sends the NSD update instruction to the NSD coordinator, the process further includes the following operation:

[0191] The NFVO receives an update confirm message returned by a VNF catalog functional entity, where the update confirm message is used to notify the NFVO that the NSD can be updated.

[0192] That is, after receiving the trigger message and further receiving the update confirm message, the NFVO sends the NSD update instruction to the NSD coordinator.

[0193] In this embodiment of the present invention, the NFVO may determine an NSD update policy by itself, or the NSD update policy may come from the update confirm message. That is, the update confirm message carries NSD update policy information, and the NSD update policy information is used to indicate how the NSD is updated.

[0194] After the update confirm message is received, if there is no NSD update policy information in the update confirm message, and the NFVO cannot formulate the NSD update policy, the NFVO does not send the NSD update instruction to the NSD coordinator.

[0195] Certainly, in actual application, the NFVO may receive an update deny message, and the update deny message is used to notify the NFVO that the NSD cannot be updated.

[0196] If the NSD is not to be updated, the NFVO notifies an NS catalog and identifies the NSD as disabled.

[0197] In this embodiment of the present invention, before the NFVO sends to the NSD coordinator the NSD update instruction carrying the NSD, the process further includes the following operation:

[0198] obtaining a target VNF package and an identifier of the source VNF; where

[0199] the NSD update instruction further carries the target VNF package and the identifier of the source VNF.

[0200] A configuration parameter of the source VNF in a to-be-updated NSD may be tampered with due to viruses or attacks. In this case, if a status of the NSD recorded in an NS catalog functional entity is still enabled, a potential risk exists. Therefore, in this embodiment of the present invention, after the NFVO sends to the NSD coordinator the NSD update instruction, the process further includes the following operations:

[0201] receiving an NSD update complete message that is sent by the NSD coordinator after finishing updating the NSD;

[0202] obtaining a target VNF identifier corresponding to the target VNF package, and adding the target VNF identifier to the NSD update complete message; and

[0203] sending to the VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, so that the VNF catalog functional entity updates a status of a target VNF corresponding to the target VNF identifier.

[0204] In this embodiment of the present invention, after the receiving, by the NFVO, an NSD update complete message that is sent by the NSD coordinator after finishing completing the NSD, the process further includes the following operations:

[0205] operating the target VNF package, and instantiating the target VNF to run the target VNF; and

[0206] switching data running on the source VNF corresponding to the identifier of the source VNF to the running target VNF to run.

[0207] In this embodiment of the present invention, after the sending, by the NFVO, the VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, the process further includes:

[0208] receiving a status update complete message of the target VNF that is returned by the VNF catalog functional entity; and

[0209] sending the NSD update complete message to a transmit end after the status update complete message of the target VNF is received.

[0210] The status of the NSD mentioned above is enabled and disabled. Certainly, the status of the NSD is not limited to the foregoing two states. In this case, there may be another state, such as delete pending.

[0211] The NSD includes various types of content, and the foregoing description uses VNF replacement as an example. Certainly, in actual application, updating the NSD may be replacing a VL or another component in the NSD. An update process is similar to a VNF replacement process, and details are not described herein.

[0212] In an embodiment of the present invention, as shown in FIG. 3, a method for updating an NSD is further provided:

[0213] Step 300: An NSD coordinator receives an NSD update instruction that carries an NSD and is sent by an NFVO.

[0214] Step 310: The NSD coordinator updates the NSD according to the NSD update instruction.

[0215] In this embodiment of the present invention, the NSD update instruction further carries a target VNF package and a source VNF identifier.

[0216] When the NSD coordinator updates the NSD according to the NSD update instruction, optionally, the following manners may be used:

[0217] The NSD coordinator determines a configuration parameter that is corresponding to the source VNF identifier and in the NSD;

[0218] the NSD coordinator obtains a parameter value that is corresponding to the configuration parameter and in the target VNF package; and

[0219] the NSD coordinator replaces an initial parameter value corresponding to the configuration parameter with the determined parameter value.

[0220] A configuration parameter of a source VNF in a to-be-updated NSD may be tampered with due to viruses or attacks. In this case, if a status of an NSD that is recorded in an NS catalog functional entity is still enabled, a potential risk exists. Therefore, in this embodiment of the present invention, after the NSD coordinator updates the NSD according to the NSD update instruction, the method further includes the following operations:

[0221] sending an NSD update complete message to the NFVO; and

[0222] sending the NS catalog functional entity a notification message carrying an updated NSD, where the notification message is used to notify the NS catalog functional entity that a status of the updated NSD is enabled.

[0223] Referring to FIG. 4, to better understand an embodiment of the present invention, the following provides a specific application scenario to further describe a process for updating an NSD in detail:

[0224] Step 400: A transmit end sends an NSD update request to an NFVO, where the NSD update request carries an NSD identifier, a source VNF identifier, and a target VNF identifier.

[0225] Step 410: The NFVO obtains an NSD according to the NSD identifier and obtains a target VNF package according to the target VNF identifier.

[0226] Step 420: The NFVO sends an NSD update instruction to an NSD coordinator.

[0227] In this step, the NSD update instruction carries the NSD, the target VNF package, and the source VNF identifier.

[0228] Step 430: The NFVO sends to an NS catalog functional entity a notification message carrying the NSD identifier.

[0229] In this step, the notification message is used to instruct the NS catalog functional entity to record a status of the NSD corresponding to the NSD identifier as disabled.

[0230] Step 440: The NSD coordinator updates the NSD according to the NSD update instruction.

[0231] Step 450: The NSD coordinator sends an NSD update complete message to the NFVO.

[0232] Step 460: The NFVO sends the NSD update complete message to a VNF catalog functional entity.

[0233] Step 470: The NSD coordinator sends to the NS catalog functional entity a notification message carrying an updated NSD.

[0234] Step 480: The VNF catalog functional entity sends a status update complete message of a target VNF to the NFVO after updating a status of the VNF.

[0235] Step 490: The NFVO sends the NSD update complete message to a transmit end.

[0236] Based on the foregoing technical solutions corresponding to the methods, referring to FIG. 5A, an embodiment of the present invention provides an NFVO, and the NFVO includes a receiving unit 50 and a sending unit 51.

[0237] The receiving unit 50 is configured to receive an NSD update request sent by a transmit end; and

[0238] the sending unit 51 is configured to send to an NSD coordinator an NSD update instruction carrying a to-be-updated NSD, so that the NSD coordinator updates the NSD.

[0239] In this embodiment of the present invention, optionally, the NSD update request carries the NSD; or

[0240] the NSD update request carries an NSD identifier corresponding to the NSD.

[0241] Further, the NFVO further includes an obtaining unit, configured to obtain the NSD according to the NSD identifier.

[0242] In this embodiment of the present invention, optionally, the NSD update request further carries a source virtualized network function VNF identifier and a target VNF identifier; and

[0243] the obtaining unit is further configured to:

[0244] obtain a target VNF package corresponding to the target VNF identifier.

[0245] In this case, optionally, that the sending unit 51 sends to the NSD coordinator the NSD update instruction is specifically:

[0246] sending the NSD coordinator the NSD update instruction, wherein the NSD update instruction further carries the target VNF package and the source VNF identifier.

[0247] In this embodiment of the present invention, further, the receiving unit 50 is further configured to:

[0248] determine that the transmit end is authorized to send the NSD update request.

[0249] In this embodiment of the present invention, further, the sending unit 51 is further configured to:

[0250] send an NS catalog functional entity a notification message carrying the NSD identifier, where the notification message is used to instruct the NS catalog functional entity to record a status of the NSD corresponding to the NSD identifier as disabled.

[0251] In this embodiment of the present invention, further, the receiving unit 50 is further configured to:

[0252] receive an NSD update complete message that is sent by the NSD coordinator after finishing updating the NSD; and

[0253] add the target VNF identifier to the NSD update complete message; and

[0254] the sending unit 51 is further configured to send to a VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, so that the VNF catalog functional entity updates a status of a target VNF corresponding to the target VNF identifier.

[0255] In this embodiment of the present invention, further, the NFVO further includes an instantiation unit and the instantiation unit is configured to:

[0256] operate the target VNF package, and instantiate the target VNF to run the target VNF;

[0257] obtain a source VNF corresponding to the source VNF identifier; and

[0258] switch data running on the source VNF corresponding to the source VNF identifier to the running target VNF to run.

[0259] In this embodiment of the present invention, further, the receiving unit 50 is further configured to:

[0260] receive a status update complete message of the target VNF that is returned by the VNF catalog functional entity; and

[0261] the sending unit 51 is further configured to send the NSD update complete message to a transmit end after the status update complete message of the target VNF is received.

[0262] Based on the foregoing technical solutions corresponding to the methods, referring to FIG. 5B, an embodiment of the present invention further provides an NFVO, and the NFVO includes a receiver 500 and a transmitter 510.

[0263] The receiver 500 is configured to receive an NSD update request sent by a transmit end; and

[0264] the transmitter 510 is configured to send to an NSD coordinator an NSD update instruction carrying a to-be-updated NSD, so that the NSD coordinator updates the NSD.

[0265] In this embodiment of the present invention, optionally, the NSD update request carries the NSD; or

[0266] the NSD update request carries an NSD identifier corresponding to the NSD.

[0267] Further, the NFVO further includes a processor, configured to obtain the NSD according to the NSD identifier.

[0268] In this embodiment of the present invention, optionally, the NSD update request further carries a source virtualized network function VNF identifier and a target VNF identifier; and

[0269] the processor is further configured to:

[0270] obtain a target VNF package corresponding to the target VNF identifier.

[0271] In this case, optionally, that the transmitter 510 sends to the NSD coordinator the NSD update instruction is specifically:

[0272] sending the NSD coordinator the NSD update instruction, wherein the NSD update instruction further carries the target VNF package and the source VNF identifier.

[0273] In this embodiment of the present invention, further, the receiver 500 is further configured to:

[0274] determine that the transmit end is authorized to send the NSD update request.

[0275] In this embodiment of the present invention, further, the transmitter 510 is further configured to:

[0276] send an NS catalog functional entity a notification message carrying the NSD identifier, where the notification message is used to instruct the NS catalog functional entity to record a status of the NSD corresponding to the NSD identifier as disabled.

[0277] In this embodiment of the present invention, further, the receiver 500 is further configured to:

[0278] receive an NSD update complete message that is sent by the NSD coordinator after finishing updating the NSD; and

[0279] add the target VNF identifier to the NSD update complete message; and

[0280] the transmitter 510 is further configured to send to a VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, so that the VNF catalog functional entity updates a status of a target VNF corresponding to the target VNF identifier.

[0281] In this embodiment of the present invention, further, the processor is further configured to:

[0282] operate the target VNF package, and instantiate the target VNF to run the target VNF;

[0283] obtain a source VNF corresponding to the source VNF identifier; and

[0284] switch data running on the source VNF corresponding to the source VNF identifier to the running target VNF to run.

[0285] In this embodiment of the present invention, further, the receiver 500 is further configured to:

[0286] receive a status update complete message of the target VNF that is returned by the VNF catalog functional entity; and

[0287] the transmitter 510 is further configured to send the NSD update complete message to a transmit end after the status update complete message of the target VNF is received.

[0288] Based on the foregoing technical solutions corresponding to the methods, referring to FIG. 6A, an embodiment of the present invention further provides an NFVO, and the NFVO includes a receiving unit 60 and a sending unit 61.

[0289] The receiving unit 60 is configured to: when receiving a trigger message, obtain a network service descriptor NSD in which a source VNF is located, where the trigger message is used to indicate that a status of a virtualized network function VNF is changed to disabled, and the source VNF is a VNF whose status is changed to disabled; and

[0290] the sending unit 61 is configured to send to an NSD coordinator an NSD update instruction carrying an NSD, so that the NSD coordinator updates the NSD.

[0291] In this embodiment of the present invention, further, the receiving unit 60 is further configured to:

[0292] receive an update confirm message returned by a VNF catalog functional entity, where the update confirm message is used to notify the NFVO that the NSD can be updated.

[0293] In this embodiment of the present invention, optionally, the update confirm message carries NSD update policy information, and the NSD update policy information is used to indicate how the NSD is updated.

[0294] In this embodiment of the present invention, further, the NFVO further includes an obtaining unit and the obtaining unit is configured to:

[0295] obtain a target VNF package and an identifier of the source VNF; where

[0296] the NSD update instruction further carries the target VNF package and the identifier of the source VNF.

[0297] In this embodiment of the present invention, further, the receiving unit 60 is further configured to:

[0298] receive an NSD update complete message that is sent by the NSD coordinator after finishing updating the NSD; and

[0299] obtain a target VNF identifier corresponding to the target VNF package, and add the target VNF identifier to the NSD update complete message; and

[0300] the sending unit 61 is further configured to send to the VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, so that the VNF catalog functional entity updates a status of a target VNF corresponding to the target VNF identifier.

[0301] In this embodiment of the present invention, further, the NFVO further includes an instantiation unit and the instantiation unit is further configured to:

[0302] operate the target VNF package, and instantiate the target VNF to run the target VNF; and

[0303] switch data running on the source VNF corresponding to the identifier of the source VNF to the running target VNF to run.

[0304] In this embodiment of the present invention, further, the receiving unit 60 is further configured to:

[0305] receive a status update complete message of the target VNF that is returned by the VNF catalog functional entity; and

[0306] the sending unit 61 is further configured to send the NSD update complete message to a transmit end after the status update complete message of the target VNF is received.

[0307] Based on the foregoing technical solutions corresponding to the methods, referring to FIG. 6B, an embodiment of the present invention further provides an NFVO, and the NFVO includes a receiver 600 and a transmitter 610.

[0308] The receiver 600 is configured to: when receiving a trigger message, obtain a network service descriptor NSD in which a source VNF is located, where the trigger message is used to indicate that a status of a virtualized network function VNF is changed to disabled, and the source VNF is a VNF whose status is changed to disabled; and

[0309] the transmitter 610 is configured to send to an NSD coordinator an NSD update instruction carrying an NSD, so that the NSD coordinator updates the NSD.

[0310] In this embodiment of the present invention, further, the receiver 600 is further configured to:

[0311] receive an update confirm message returned by a VNF catalog functional entity, where the update confirm message is used to notify the NFVO that the NSD can be updated.

[0312] In this embodiment of the present invention, optionally, the update confirm message carries NSD update policy information, and the NSD update policy information is used to indicate how the NSD is updated.

[0313] In this embodiment of the present invention, further, the NFVO further includes a processor, and the processor is configured to:

[0314] obtain a target VNF package and an identifier of the source VNF; where

[0315] the NSD update instruction further carries the target VNF package and the identifier of the source VNF.

[0316] In this embodiment of the present invention, further, the receiver 600 is further configured to:

[0317] receive an NSD update complete message that is sent by the NSD coordinator after finishing updating the NSD; and

[0318] obtain a target VNF identifier corresponding to the target VNF package, and add the target VNF identifier to the NSD update complete message; and

[0319] the transmitter 610 is further configured to send to the VNF catalog functional entity the NSD update complete message to which the target VNF identifier is added, so that the VNF catalog functional entity updates a status of a target VNF corresponding to the target VNF identifier.

[0320] In this embodiment of the present invention, further, the processor is further configured to:

[0321] operate the target VNF package, and instantiate the target VNF to run the target VNF; and

[0322] switch data running on the source VNF corresponding to the identifier of the source VNF to the running target VNF to run.

[0323] In this embodiment of the present invention, further, the receiver 600 is further configured to:

[0324] receive a status update complete message of the target VNF that is returned by the VNF catalog functional entity; and

[0325] the transmitter 610 is further configured to send the NSD update complete message to a transmit end after the status update complete message of the target VNF is received.

[0326] Based on the foregoing technical solutions corresponding to the methods, referring to FIG. 7A, an embodiment of the present invention further provides an NSD coordinator, and the NSD coordinator includes a receiving unit 70 and an update unit 71.

[0327] The receiving unit 70 is configured to receive an NSD update instruction that carries an NSD and is sent by a network functions virtualization orchestrator NFVO; and

[0328] the update unit 71 is configured to update the NSD according to the NSD update instruction.

[0329] In this embodiment of the present invention, optionally, the NSD update instruction further carries a target VNF package and a source virtualized network function VNF identifier.

[0330] In this embodiment of the present invention, optionally, the update unit is specifically configured to:

[0331] determine a configuration parameter that is corresponding to the source VNF identifier and in the NSD;

[0332] obtain a parameter value that is corresponding to the configuration parameter and in the target VNF package; and

[0333] replace an initial parameter value corresponding to the configuration parameter with the determined parameter value.

[0334] In this embodiment of the present invention, further, a sending unit is configured to:

[0335] send an NSD update complete message to the NFVO; and

[0336] send an NS catalog functional entity a notification message carrying an updated NSD, where the notification message is used to notify the NS catalog functional entity that a status of the updated NSD is enabled.

[0337] Based on the foregoing technical solutions corresponding to the methods, referring to FIG. 7B, an embodiment of the present invention further provides an NSD coordinator, and the NSD coordinator includes a receiver 700 and a processor 710.

[0338] The receiver 700 is configured to receive an NSD update instruction that carries an NSD and is sent by a network functions virtualization orchestrator NFVO; and

[0339] the processor 710 is configured to update the NSD according to the NSD update instruction.

[0340] In this embodiment of the present invention, optionally, the NSD update instruction further carries a target VNF package and a source virtualized network function VNF identifier.

[0341] In this embodiment of the present invention, optionally, the processor 710 is specifically configured to:

[0342] determine a configuration parameter that is corresponding to the source VNF identifier and in the NSD;

[0343] obtain a parameter value that is corresponding to the configuration parameter and in the target VNF package; and

[0344] replace an initial parameter value corresponding to the configuration parameter with the determined parameter value.

[0345] In this embodiment of the present invention, further, the NSD coordinator further includes a transmitter, and the transmitter is configured to:

[0346] send an NSD update complete message to the NFVO; and

[0347] send an NS catalog functional entity a notification message carrying an updated NSD, where the notification message is used to notify the NS catalog functional entity that a status of the updated NSD is enabled.

[0348] The present invention is described with reference to the flowcharts and/or block diagrams of the method, the device (system), and the computer program product according to the embodiments of the present invention. It should be understood that computer program instructions may be used to implement each process and/or each block in the flowcharts and/or the block diagrams and a combination of a process and/or a block in the flowcharts and/or the block diagrams. These computer program instructions may be provided for a general-purpose computer, a dedicated computer, an embedded processor, or a processor of any other programmable data processing device to generate a machine, so that the instructions executed by a computer or a processor of any other programmable data processing device generate an apparatus for implementing a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.

[0349] These computer program instructions may also be stored in a computer readable memory that can instruct the computer or any other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory generate an artifact that includes an instruction apparatus. The instruction apparatus implements a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.

[0350] These computer program instructions may also be loaded onto a computer or another programmable data processing device, so that a series of operations and steps are performed on the computer or the another programmable device, thereby generating computer-implemented processing. Therefore, the instructions executed on the computer or the another programmable device provide steps for implementing a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.

[0351] Although some preferred embodiments of the present invention have been described, a person skilled in the art can make changes and modifications to these embodiments once they learn the basic inventive concept. Therefore, the following claims are intended to be construed as to cover the preferred embodiments and all changes and modifications falling within the scope of the present invention.

[0352] Obviously, a person skilled in the art can make various modifications and variations to the embodiments of the present invention without departing from the spirit and scope of the embodiments of the present invention. The present invention is intended to cover these modifications and variations provided that they fall within the scope of protection defined by the following claims and their equivalent technologies.