IP Library Granted Patent US 10,979,248
Granted Patent B1
US 10,979,248 · App. 16/727,871 · Granted Apr 13, 2021

Onboarding a VNF which includes a VNFC composed of manageable software elements

Inventor: Keith William Melkild (Allen, TX)
Assignee: OPEN INVENTION NETWORK LLC
H04L12/4641G06F9/45558G06F2009/45595
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 10,979,248
App. No.
16/727,871
Granted
Apr 13, 2021
Kind
B1
Abstract

The instant solution includes at least one element or action described or depicted herein.

Claims (62)

1. A method for on-boarding a Virtual Network Function (VNF) comprising a Virtual Network Function Component VNFC including a plurality of independently manageable Virtual Network Function Component VNFC software elements, the method comprising:

receiving, by a hardware-implemented server executing a Service Design and Creation (SDC) module, an archive, created by a VNF provider, the archive containing contents of a VNF package including a VNF Descriptor (VNFD) file containing a plurality of VNFC element descriptor files, each VNFC element descriptor file corresponding to one of the plurality of independently manageable VNFC software elements, and the archive containing VNFC software element artifacts;

identifying, by the SDC module, a manifest file in the archive, the manifest file listing an entire contents of the archive;

on-boarding, by the SDC module, the VNFD file;

on-boarding, by the SDC module and after the on-boarding of the VNFD file, the VNFC software element artifacts; and

enabling, by the SDC module, the VNF in a catalog of the SDC module.

2. The method of claim 1 , wherein the VNFC software element artifacts comprise:

a VNF specific lifecycle management (LCM) script file;

a VNFC element specific lifecycle script file;

a Virtualized Container (VC) upgrade scrip file;

a VC image binary file; and

a VNFC element software load.

3. The method of claim 1 , comprising: processing, by the SDC module, a signing certificate located in the archive based on the identifying a manifest file.

4. The method of claim 1 , further comprising:

storing, by the SDC module, the VNFD file and the VNFC software element artifacts in the catalog of the SDC module.

5. The method of claim 1 , further comprising:

storing, by the SDC module, the VNFD file and the VNFC software element artifacts in a remote database specified in a VC image descriptor file of the VNFD.

6. The method of claim 1 , wherein the enabling the VNF in a catalog of the SDC module further comprises:

automatically enabling the VNF in the catalog of the SDC module based on a completion of the on-boarding process.

7. The method of claim 1 , wherein a filesystem structure of the VNF Package conforms to a version of the Topology and Orchestration Specification for Cloud Application (TOSCA) standard.

8. An apparatus for on-boarding a Virtual Network Function (VNF) comprising a Virtual Network Function Component VNFC including a plurality of independently manageable Virtual Network Function Component VNFC software elements, the apparatus comprising:

a hardware-implemented server executing a Service Design and Creation (SDC) module configured to:

receive an archive, created by a VNF provider, containing contents of a VNF package including a VNF Descriptor (VNFD) file containing a plurality of VNFC element descriptor files, each VNFC element descriptor file corresponding to one of the plurality of independently manageable VNFC software elements, and the archive containing VNFC software element artifacts;

Identify a manifest file in the archive, the manifest file listing an entire contents of the archive;

on-board the VNFD file;

on-boarding the VNFC software element artifacts after the on-boarding of the VNFD file; and

enable the VNF in a catalog of the SDC module.

9. The system of claim 8 , wherein the VNFC software element artifacts comprise:

a VNF specific lifecycle management (LCM) script file;

a VNFC element specific lifecycle script file;

a Virtualized Container (VC) upgrade scrip file;

a VC image binary file; and

a VNFC element software load.

10. The system of claim 8 , wherein the SDC module is further configured to:

process a signing certificate located in the archive based on the identifying a manifest file.

11. The system of claim 8 , wherein the SDC module is further configured to:

store the VNFD file and the VNFC software element artifacts in the catalog of the SDC module.

12. The system of claim 8 , wherein the SDC module is further configured to:

store the VNFD file and the VNFC software element artifacts in a remote database specified in a VC image descriptor file of the VNFD.

13. The system of claim 8 , wherein, when the SDC module enables the VNF, the SDC module is further configured to:

automatically enable the VNF in the catalog of the SDC module based on a completion of the on-boarding process.

14. The system of claim 8 , wherein a filesystem structure of the VNF Package conforms to a version of the Topology and Orchestration Specification for Cloud Application (TOSCA) standard.

15. A non-transitory computer readable medium storing instructions for on-boarding Virtual Network Function (VNF) comprising a Virtual Network Function Component VNFC including a plurality of independently manageable Virtual Network Function Component VNFC software elements that when read by a processor of a hardware-implemented server executing a Service Design and Creation (SDC) module cause the processor to:

receive an archive, created by a VNF provider, containing contents of a VNF package including a VNF Descriptor (VNFD) file containing a plurality of VNFC element descriptor files, each VNFC element descriptor file corresponding to one of the plurality of independently manageable VNFC software elements, and the archive containing VNFC software element artifacts;

identify a manifest file in the archive, the manifest file listing an entire contents of the archive;

on-board the VNFD file;

on-boarding the VNFC software element artifacts after the on-boarding of the VNFD file; and

enable the VNF in a catalog of the SDC module.

16. The non-transitory computer readable medium of claim 15 , wherein the VNFC software element artifacts comprise:

a VNF specific lifecycle management (LCM) script file;

a VNFC element specific lifecycle script file;

a Virtualized Container (VC) upgrade scrip file;

a VC image binary file; and

a VNFC element software load.

17. The non-transitory computer readable medium of claim 15 , wherein the instruction further cause to processor to:

process a signing certificate located in the archive based on the identifying a manifest file.

18. The non-transitory computer readable medium of claim 15 , wherein the instruction further cause to processor to:

store the VNFD file and the VNFC software element artifacts in the catalog of the SDC module.

19. The non-transitory computer readable medium of claim 15 , wherein the instruction further cause to processor to:

store the VNFD file and the VNFC software element artifacts in a remote database specified in a VC image descriptor file of the VNFD.

20. The system of claim 15 , wherein, when the processor enables the VNF, the instructions further cause the processor to:

automatically enable the VNF in the catalog of the SDC module based on a completion of the on-boarding process.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 25, 2022
From: OPEN INVENTION NETWORK LLC
To: GOOGLE LLC
Reel/Frame 061766/0545 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2020
From: MELKILD, KEITH WILLIAM
To: OPEN INVENTION NETWORK LLC
Reel/Frame 052074/0762 →
Continuity (1)
Provisional Application 62784996 · Dec 26, 2018
Cited By (1)
US 12,219,025