Managing virtual links in a network service instance

1. An apparatus of a Network Manager (NM), comprising:

one or more processors to send a Network Service (NS) update request to a Network Function Virtualization Orchestrator (NFVO) to add external connectivity to a Physical Network Function (PNF) instance or a Virtual Network Function (VNF) instance in an NS instance, wherein the NS update request comprises an attribute identifying an external connection point or an external link port for the PNF instance or the VNF instance, the one or more processors to receive an operation result containing a lifecycle operation occurrence identifier from the NFVO, to receive a lifecycle change notification from the NFVO indicating a start of an NS update, and to receive an NS Lifecycle Change notification from the NFVO indicating a result of the NS update; and

a memory to store the result of the NS update.

2. The apparatus of claim 1 , wherein the one or more processors are to send an NS update request to the NFVO to add a virtual link to the NS instance, to receive from the NFVO an operation result containing a lifecycle operation occurrence identifier, to receive from NFVO an NS Lifecycle Change notification indicating a start of NS update, and to receive from the NFVO an NS Lifecycle Change notification indicating a result of the NS update.

3. The apparatus of claim 1 , wherein the one or more processors are to send an NS update request to the NFVO to remove a virtual link from the NS instance, to receive from NFVO an operation result containing a lifecycle operation occurrence identifier, to receive from the NFVO an NS Lifecycle Change notification indicating the start of NS update, and to receive from the NFVO a NS Lifecycle Change notification indicating a result of the NS update.

4. The apparatus of claim 1 , wherein the one or more processors are to send an NS update request to the NFVO to change the external connectivity to the PNF instance, the NS update request containing the following attributes:

nsInstanceId: the identifier of the NS instance being updated;

updateType=“ChangeExtPnfConnectivity” to indicate the type of update operation; and

changeExtPnfConnectivityData: new external connectivity data of the PNF to be changed;

wherein changeExtPnfConnectivityData contains the following attributes

pnfId: the identifier of the PNF; and

pnfConnectivityData: Information about the PNF connectivity; and

wherein pnfConnectivityData contains the following attributes

extVirtualLinkId: Identifier of an external VL instance;

extCp: External CPs of the VNF to be connected to the external VL instance; and

extLinkPorts: link ports to be used to connect external connection points to the external VL instance.

5. The apparatus of claim 2 , wherein the NS update request to add the virtual link to the NS instance contains the following attributes:

nsInstanceId: the identifier of the NS instance being updated;

updateType=“AddVirtualLink” to indicate the type of update operation; and

add VirtualLinkData: the information of the virtual link to be added to a NS instance;

wherein add VirtualLinkData contains virtualLinkProfileId that is the identifier of VirtualLinkProfile.

6. The apparatus of claim 1 , wherein the NS update request to add the external connectivity to the PNF instance or the VNF instance contains the following attributes:

nsInstanceId: the identifier of the NS instance being updated;

updateType=“AddExtConnectivity” to indicate the type of update operation; and

addExtConnectivityData: the information of the external connectivity;

wherein addExtConnectivityData contains the following attributes:

vnfInstanceId: the identifier of the existing VNF instance;

extVirtualLinkData: information about the external VL to be added to the VNF instance;

pnfId: the identifier of the PNF; and

pnfConnectivityData: Information about the PNF connectivity;

wherein pnfConnectivityData contains the following attributes:

extVirtualLinkId: Identifier of an external VL instance;

extCp: External CPs of the VNF to be connected to the external VL instance; and

extLinkPorts: link ports to be used to connect external connection points to the external VL instance.

7. The apparatus of claim 1 , wherein the one or more processors are to send an NS update request to add a VNF instance with external connectivity to the NS instance, the NS update request containing the following attributes:

nsInstanceId: the identifier of the NS instance being updated;

updateType=“AddVnf” to indicate the type of update operation; and

VnfInstanceData: the information of the VNF instance to be added to the NS;

wherein VnfInstanceData contains the following attributes:

vnfInstanceId: the identifier of the existing VNF instance;

vnfProfileId: the identifier of the vnfProfile defined in the NSD for an existing VNF instance; and

extVirtualLinkData: information about the external VL to be added to the VNF instance.

8. An apparatus of a Network Function Virtualization Orchestrator (NFVO), comprising:

one or more processors to receive a request from a Network Manager (NM) to update a Network Service (NS) to add external connectivity to a physical network function (PNF) instance or a virtual network function (VNF) instance, wherein the request comprises an attribute identifying an external connection point or an external link port for the PNF instance or the VNF instance, the one or more processors to send to the NM an NS update operation result containing a lifecycle operation occurrence identifier, to send to the NM an NS Lifecycle Change notification indicating a start of the NS update, to connect the PNF instance or the VNF instance to an NS virtual link per the request, and to send to the NM a NS Lifecycle Change notification indicating a result of the NS update; and

a memory to store the request from the NM.

9. The apparatus of claim 8 , wherein the one or more processors are to receive a request from the NM to update the NS to add a virtual link to an NS instance, to send to the NM an NS update operation result containing a lifecycle operation occurrence identifier, to send to the NM an NS Lifecycle Change notification indicating the start of an NS update, to add the virtual link to the NS instance as per the request, and to send to the NM an NS Lifecycle Change notification indicating a result of the NS update.

10. The apparatus of claim 8 , wherein the one or more processors are to receive a request from the NM to update the NS to remove a virtual link from an NS instance, to send to the NM an NS update operation result containing a lifecycle operation occurrence identifier, to send to the NM an NS Lifecycle Change notification indicating the start of an NS update, to remove the virtual link from the NS instance per the request, and to send to the NM an NS Lifecycle Change notification indicating the result of the NS update.

11. One or more non-transitory storage media having instructions stored thereon that, when executed by a Network Manger (NM), result in:

sending a Network Service (NS) update request to a Network Function Virtualization Orchestrator (NFVO) to initiate an NS update operation, wherein the NS update request comprises an attribute identifying an external connection point or an external link port for a PNF instance or a VNF instance, the one or more processors;

receiving from the NFVO an operation result containing a lifecycle operation occurrence identifier;

receiving from the NFVO an NS Lifecycle Change notification indicating a start of an NS update; and

receiving from the NFVO an NS Lifecycle Change notification to indicating a result of the NS update.

12. The one or more non-transitory storage media of claim 11 , wherein the NS update operation is to add a Virtual Network Function Forwarding Graph (VNFFG) instance containing one or more Network Forwarding Paths (NFPs) to an NS instance with the following attributes:

nsInstanceId: the identifier of the NS instance being updated;

updateType=”AddVnffg” to indicate the type of update operation; and

addVnffgData: the information of the VNFFG to be added.

13. The one or more non-transitory storage media of claim 12 , wherein the NS update operation is to add one or more NFPs to the VNFFG instance in an NS instance via an VNFFG update action.

14. The one or more non-transitory storage media of claim 12 , wherein the NS update operation is to delete one or more NFPs from the VNFFG instance in an NS instance via an VNFFG update action.

15. The one or more non-transitory storage media of claim 12 , wherein the NS update operation is to delete the NFPs from the VNFFG instance in an NS instance with the following attributes:

nsInstanceId: the identifier of the NS instance being updated;

updateType=“UpdateVnffg” to indicate the type of update operation; and

updateVnffgData: the information of VNFFG to be updated.

16. The one or more non-transitory storage media of claim 15 , wherein the updateVnffgData contains the following attributes:

vnffgId: Identifier of the VNFFG instance to be updated; and

nfpId: identifier of the NFP instances to be deleted.

17. The one or more non-transitory storage media of claim 12 , wherein the NS update operation is to modify one or more NFPs in the VNFFG instance in a NS instance via an VNFFG update action.

18. The one or more non-transitory storage media of claim 12 , wherein the NS update operation is to modify the NFPs in the VNFFG instance in an NS instance with the following attributes:

nsInstanceId: the identifier of the NS instance being updated;

updateType=“UpdateVnffg” to indicate the type of update operation; and

updateVnffgData: the information of VNFFG to be updated.

19. The one or more non-transitory storage media of claim 18 , wherein the updateVnffgData contains the following attributes:

vnffgId: Identifier of the VNFFG instance to be updated;

nfp: Indicate the desired new NFP(s) for a given VNFFG, and may contain one or more of the following attributes; and

nfpId: Indicate the identifier of the NFP to be modified.