IP Library Granted Patent US 11,327,787
Granted Patent B2
US 11,327,787 · App. 16/319,886 · Granted May 10, 2022

Using a managed object operation to control a lifecycle management operation

Inventor: Joey Chou (Scottsdale, AZ)
Assignee: Apple Inc.
G06F9/485G06F9/455G06F9/5077H04L41/0806
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,327,787
App. No.
16/319,886
Granted
May 10, 2022
Kind
B2
Abstract

Techniques for linking managed object (MO) operations and lifecycle operations associated with VNFs (Virtual Network Functions) are discussed. In various actions, MO operations can trigger associated lifecycle operations, or lifecycle operations can trigger associated MO operations. In some aspects, MO instance creation by an EM (Element Manager) can trigger associated VNF instantiation by a VNFM (VNF Manager), or vice versa. In the same or other aspects, MO instance deletion by an EM can trigger termination of an associated VNF by a VNFM, or vice versa.

Claims (62)

1. An apparatus configured to be employed within an EM (Element Manager), comprising:

a memory; and

one or more processors configured to:

receive a first request to create a MO (Managed Object) from a NM (Network Manager), wherein the first request indicates triggering of an instantiation of a VNF (Virtual Network Function) and comprises a VNFD (VNF Descriptor) ID (identifier) of the VNF and a DF (Deployment Flavor) ID of the VNF;

trigger the instantiation of the VNF based on the first request;

receive a first Notify operation from a VNFM (VNF Manager) indicating a result of the instantiation of the VNF, wherein the first Notify operation comprises a notification of a change in a lifecycle of the VNF, an instance ID of the VNF, and one or more resources affected by the VNF;

create a MOI (MO instance) comprising one or more attributes referring to the VNF, wherein the one or more attributes comprise the instance ID; and

send a notification to the NM indicating that the MO has been created.

2. The apparatus of claim 1 , wherein the one or more processors being configured to trigger instantiation of the VNF comprises the one or more processors being configured to:

send a second request to the VNFM to create a VNF identifier associated with the VNF;

receive a second response from the VNFM indicating the creation of a new instance of a VNF IE (information element) associated with the VNF;

send a third request to the VNFM to instantiate the VNF; and

receive a third response from the VNFM that identifies a lifecycle operation occurrence associated with the VNF.

3. The apparatus of claim 1 , wherein the one or more processors are further configured to receive a second Notify operation from the VNFM indicating a start of the instantiation of the VNF.

4. The apparatus of claim 1 , wherein the one or more processors are further configured to configure one or more attributes of the MOI.

5. The apparatus of claim 1 , wherein the one or more resources affected by the VNF comprise one or more of at least one VNFC (VNF Component) instance, at least one VL (Virtual Link) instance, or at least one virtualized storage instance.

6. The apparatus of claim 1 , wherein the one or more processors are further configured to:

send a fourth request to the VNFM to terminate the VNF, wherein the fourth request indicates the instance ID of the VNF;

receive a fourth response from the VNFM indicating a termination of the VNF, wherein the fourth response indicates a lifecycle operation occurrence ID of the termination;

receive a third Notify operation from the VNFM, wherein the third Notify operation comprises a first notification of a lifecycle change of the VNF, the instance ID of the VNF, a status indicating a start of the lifecycle change, and an operation indicating the lifecycle change is the termination of the VNF; and

receive a fourth Notify operation from the VNFM, wherein the fourth Notify operation comprises a second notification of the lifecycle change of the VNF, the one or more resources affected by the VNF, a status indicating a result of the lifecycle change, and an operation indicating the lifecycle change is the termination of the VNF.

7. The apparatus of claim 6 , wherein the one or more processors are further configured to:

send a fifth request to the VNFM to delete a VNF identifier that indicates the VNF instance ID; and

receive a fifth Notify operation from the VNFM, wherein the fifth Notify operation comprises a notification of a deletion of the VNF identifier that indicates the VNF instance ID.

8. The apparatus of claim 6 , wherein the one or more processors are further configured to:

receive an operation from the NM to delete the MO, wherein the operation to delete the MO indicates the termination of the VNF;

delete the MOI; and

send a notification of the deletion of the MOI to the NM.

9. The apparatus of claim 1 , wherein the one or more processors are further configured to:

receive a sixth Notify operation from the VNFM, wherein the sixth Notify operation comprises a notification of a lifecycle change of the VNF, a status indicating a result of the lifecycle change, and an operation indicating the lifecycle change is the termination of the VNF; and

detect that the VNF has been terminated based on checking the status and the operation of the sixth Notify operation.

10. The apparatus of claim 9 , wherein the one or more processors are further configured to:

determine to modify an attribute of the MOI to remove an association with the VNF instance ID; and

send a notification to the NM that indicates that the attribute of the MOI has been changed.

11. The apparatus of claim 9 , wherein the one or more processors are further configured to:

determine to delete the MOI;

identify the MOI based on the VNF instance ID;

delete the MOI; and

send a notification to the NM that indicates that the MOI has been deleted.

12. An apparatus configured to be employed within a VNFM (VNF (Virtual Network Function) Manager), comprising:

a memory; and

one or more processors configured to:

allocate virtualized resources to an instance of a VNF;

configure the instance of the VNF with one or more input parameters; and

send a first Notify operation to an EM (Element Manager) indicating a result of the instantiation of the VNF, wherein the first Notify operation comprises a notification of a change in a lifecycle of the VNF, an instance ID of the VNF, and one or more resources affected by the VNF.

13. The apparatus of claim 12 , wherein the one or more processors are further configured to:

receive a first request from the EM to create a VNF identifier associated with the VNF;

send a first response to the EM indicating the creation of a new instance of a VNF IE (information element) associated with the VNF;

receive a second request from the EM to instantiate the VNF; and

send a second response to the EM that identifies a lifecycle operation occurrence associated with the VNF.

14. The apparatus of claim 12 , wherein the one or more processors are further configured to send a second Notify operation to the EM indicating a start of the instantiation of the VNF.

15. The apparatus of claim 12 , wherein the one or more resources affected by the VNF comprise one or more of at least one VNFC (VNF Component) instance, at least one VL (Virtual Link) instance, or at least one virtualized storage instance.

16. The apparatus of claim 12 , wherein the one or more processors are further configured to:

receive a third request from the EM to terminate the VNF, wherein the third request indicates the instance ID of the VNF;

send a third response to the EM indicating a termination of the VNF, wherein the third response indicates a lifecycle operation occurrence ID of the termination;

send a third Notify operation to the EM, wherein the third Notify operation comprises a first notification of a lifecycle change of the VNF, the instance ID of the VNF, a status indicating a start of the lifecycle change, and an operation indicating the lifecycle change is the termination of the VNF; and

send a fourth Notify operation to the EM, wherein the fourth Notify operation comprises a second notification of the lifecycle change of the VNF, the one or more resources affected by the VNF, a status indicating a result of the lifecycle change, and an operation indicating the lifecycle change is the termination of the VNF.

17. The apparatus of claim 16 , wherein the one or more processors are further configured to:

receive a fourth request from the EM to delete a VNF identifier that indicates the VNF instance ID; and

send a fifth Notify operation to the EM, wherein the fifth Notify operation comprises a notification of a deletion of the VNF identifier that indicates the VNF instance ID.

18. The apparatus of claim 12 , wherein the one or more processors are further configured to:

send a sixth Notify operation to the EM, wherein the sixth Notify operation comprises a notification of a lifecycle change of the VNF, a status indicating a result of the lifecycle change, and an operation indicating the lifecycle change is the termination of the VNF.

Assignments (2)
CONFIRMATORY ASSIGNMENT Recorded Aug 11, 2020
From: INTEL IP CORPORATION
To: INTEL CORPORATION
Reel/Frame 053455/0489 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 25, 2020
From: INTEL CORPORATION
To: APPLE INC.
Reel/Frame 053065/0627 →
Continuity (2)
Provisional Application 62376126 · Aug 17, 2016
Related Publication 20190266012A1 · Aug 29, 2019