System and method of managing PNF connectivity in a network slice instance
Systems and methods of managing PNF connectivity are provided. A NM determines to add to or remove external connectivity from a PNF and transmits a NS update request to a NFVO that contains an identifier of the NS instance to be updated, an indication of a type of update operation requested, and information of the PNF connectivity to be changed. A NS update response contains a lifecycle operation occurrence identifier identifying a NS lifecycle operation occurrence. Separate NS lifecycle change notification from the NFVO indicate that a NS update to change the connectivity of the PNF has started and a result of the change. The notifications include the lifecycle operation occurrence identifier.
1. An apparatus, comprising:
at least one processor configured to cause a network manager (NM) to:
generate a network slice (NS) update request for transmission to a Network Function Virtualization Orchestrator (NFVO) through an Os-Ma-nfvo reference point to add connectivity of an existing physical network function (PNF) in a NS instance;
obtain, from the NFVO in response to transmission of the NS update request, a NS update response that includes a lifecycle operation occurrence identifier, the lifecycle operation occurrence identifier identifying a NS lifecycle operation occurrence; and
after reception of the lifecycle operation occurrence identifier:
determine that a NS update to add connectivity to the existing PNF has started based on a first NS lifecycle change notification from the NFVO, the first NS lifecycle change comprising the lifecycle operation occurrence identifier; and
after a determination that the NS update has started, determine a result of the NS update based on a second NS lifecycle change notification from the NFVO, the second NS lifecycle change notification comprising the lifecycle operation occurrence identifier.
2. The apparatus according to claim 1 ,
wherein the NS update request comprises:
an identifier of the NS instance to be updated;
an indication of a type of update operation requested by the NS update request; and
information of the PNF connectivity to be changed.
3. The apparatus according to claim 2 ,
wherein the information of the PNF connectivity to be changed comprises:
an identifier of the PNF,
information of an external connection point of the PNF, and
externally provided link ports to be used to connect external connection points to an external virtual link (VL).
4. The apparatus according to claim 3 ,
wherein at least one processor is further arranged to:
assign the identifier of the PNF.
5. The apparatus according to claim 2 ,
wherein the information of the PNF connectivity to be changed comprises:
an AddExtPnfConnectivityData information element that is present if the indication of the type of update operation indicates addition of PNF connectivity and is not present if the indication of the type of update operation indicates removal of PNF connectivity.
6. The apparatus according to claim 2 ,
wherein the information of the PNF connectivity to be changed comprises:
a RemoveExtPnfConnectivityData information element that is present if the indication of the type of update operation indicates removal of PNF connectivity and is not present if the indication of the type of update operation indicates of addition PNF connectivity.
7. The apparatus according to claim 2 ,
wherein the information of the PNF connectivity to be changed comprises a greater number of attributes if the type of update operation indicates of addition PNF connectivity than if the indication of the type of update operation indicates removal of PNF connectivity.
8. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of a network manager (NM) service provider to:
generate a network slice (NS) update request to a Network Function Virtualization Orchestrator (NFVO) to add external connectivity to or remove external connectivity from an existing physical network function (PNF) in a NS instance; receive, from the NFVO in response to transmission of the NS update request, a NS update response that contains a lifecycle operation occurrence identifier, the lifecycle operation occurrence identifier identifying a NS lifecycle operation occurrence; and
after reception of the lifecycle operation occurrence identifier:
receive a first NS lifecycle change notification from the NFVO that a NS update to change connectivity of the existing PNF has started, the first NS lifecycle change comprising the lifecycle operation occurrence identifier; and
after a determination that the NS update has started, receive a second NS lifecycle change notification from the NFVO that indicates a result of the NS update, the second NS lifecycle change notification comprising a result of NS update, and the lifecycle operation occurrence identifier.
9. The medium according to claim 8 ,
wherein information of the PNF connectivity to be changed comprises:
an identifier of the PNF,
information of an external connection point of the PNF, and
externally provided link ports to be used to connect external connection points to an external virtual link (VL).
10. The medium according to claim 8 ,
wherein information of the PNF connectivity to be changed comprises:
an AddExtPnfConnectivityData information element that is present if an indication of an type of update operation indicates addition of PNF connectivity and is not present if the indication of the type of update operation indicates removal of PNF connectivity.
11. The medium according to claim 8 ,
wherein information of the PNF connectivity to be changed comprises:
a RemoveExtPnfConnectivityData information element that is present if an indication of an type of update operation indicates removal of PNF connectivity and is not present if the indication of the type of update operation indicates of addition PNF connectivity.
12. The medium according to claim 8 ,
wherein information of the PNF connectivity to be changed comprises a greater number of attributes if a type of update operation indicates of addition PNF connectivity than if an indication of the type of update operation indicates removal of PNF connectivity.
13. A method, comprising:
a network manager (NM),
generating a network slice (NS) update request for transmission to a Network Function Virtualization Orchestrator (NFVO) through an Os-Ma-nfvo reference point to add connectivity of an existing physical network function (PNF) in a NS instance;
obtaining, from the NFVO in response to transmission of the NS update request, a NS update response that includes a lifecycle operation occurrence identifier, the lifecycle operation occurrence identifier identifying a NS lifecycle operation occurrence; and
after reception of the lifecycle operation occurrence identifier:
determining that a NS update to add connectivity to the existing PNF has started based on a first NS lifecycle change notification from the NFVO, the first NS lifecycle change comprising the lifecycle operation occurrence identifier; and
after a determination that the NS update has started, determining a result of the NS update based on a second NS lifecycle change notification from the NFVO, the second NS lifecycle change notification comprising the lifecycle operation occurrence identifier.
14. The method according to claim 13 ,
wherein the NS update request comprises:
an identifier of the NS instance to be updated;
an indication of a type of update operation requested by the NS update request; and
information of the PNF connectivity to be changed.
15. The method according to claim 14 ,
wherein the information of the PNF connectivity to be changed comprises:
an identifier of the PNF,
information of an external connection point of the PNF, and
externally provided link ports to be used to connect external connection points to an external virtual link (VL).
16. The method according to claim 15 , further comprising:
assigning the identifier of the PNF.
17. The method according to claim 14 ,
wherein the information of the PNF connectivity to be changed comprises:
an AddExtPnfConnectivityData information element that is present if the indication of the type of update operation indicates addition of PNF connectivity and is not present if the indication of the type of update operation indicates removal of PNF connectivity.
18. The method according to claim 14 ,
wherein the information of the PNF connectivity to be changed comprises:
a RemoveExtPnfConnectivityData information element that is present if the indication of the type of update operation indicates removal of PNF connectivity and is not present if the indication of the type of update operation indicates of addition PNF connectivity.
19. The method according to claim 14 ,
wherein the information of the PNF connectivity to be changed comprises a greater number of attributes if the type of update operation indicates of addition PNF connectivity than if the indication of the type of update operation indicates removal of PNF connectivity.
20. The apparatus of claim 1 ,
wherein the PNF was previously added or instantiated in the NS instance without external connectivity.