User interface for accessing multiple catalogs of items and indicating items added from catalogs
US-2024428304-A1 · Dec 26, 2024 · US
US9760923B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9760923-B1 |
| Application number | US-201514673587-A |
| Country | US |
| Kind code | B1 |
| Filing date | Mar 30, 2015 |
| Priority date | Jun 18, 2014 |
| Publication date | Sep 12, 2017 |
| Grant date | Sep 12, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system, method, and computer program product are provided for product/service design and creation. In use, at least one new resource is identified in a master catalog. The at least one resource is tested. Additionally, the at least one resource is released for service generation. Further, at least one service is generated utilizing the at least one resource. The at least one service is stored in the master catalog. In addition, the at least one service is released for product generation. Furthermore, at least one product is generated utilizing the at least one service. The at least one product is stored in the master catalog. Moreover, the at least one product is presented for sale.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: identifying a virtual network function (VNF) newly stored in a master catalog of a network function virtualization (NFV) management hardware system within a network function virtualization (NFV)-based network, the VNF being a software program implementation of a function within the NFV-based network; receiving, through tools of a product design and creation environment of the NFV management hardware system, details about the VNF, including: (a) processes to manage: start, update, scale and cease of the VNF, and (b) policies for: needed resources, when to scale, how to respond to errors, configurations, and dependencies on other resources; testing, through the tools of the product design and creation environment of the NFV management hardware system, the VNF; receiving, through the NFV management hardware system, a request that the VNF be approved for use in the NFV-based network; responsive to the request and upon ensuring that verification and validation tests have been completed for the VNF, releasing, through the tools of the product design and creation environment of the NFV management hardware system, the VNF for service generation; generating, through the tools of the product design and creation environment of the NFV management hardware system, a first service from the VNF; storing, by the product design and creation environment of the NFV management hardware system, the first service in the master catalog; making the first service accessible through the master catalog, by the product design and creation environment of the NFV management hardware system; combining, through the tools of the product design and creation environment of the NFV management hardware system, the first service with a second service existing in the master catalog to create a new third service in the master catalog with references being made to the first service and the second service; adding to the third service, through the tools of the product design and creation environment of the NFV management hardware system, processes and policies to address: an order in which the first service and the second service must be instantiated, service configuration, attributes required for instantiation, prerequisites, and compatibility with other services; validating, through the tools of the product design and creation environment of the NFV management hardware system, the compatibility of the first service with the second service to ensure there is interoperability and that no policies have been breached; responsive to the validation, making the third service available for instantiation in the NFV-based network; receiving, through the tools of the product design and creation environment of the NFV management hardware system, a new definition of a product that references the third service and that adds an additional set of processes and policies which address; price plans, order capture process, product eligibility for markets and customer types, and upgrades from previous product versions; automatically making the product available in a customer ordering system of the NFV management hardware system for selection, ordering, and provisioning of the product by customers of the NFV-based network. 2. The method of claim 1 , wherein separation between product, service, and resource layers is maintained in the master catalog. 3. A computer program product embodied on a non-transitory computer readable medium and including computer code executable by a processor to perform a method comprising: identifying a virtual network function (VNF) newly stored in a master catalog of a network function virtualization (NFV) management hardware system within a network function virtualization (NFV)-based network, the VNF being a software program implementation of a function within the NFV-based network; receiving, through tools of a product design and creation environment of the NFV management hardware system, details about the VNF, including: (a) processes to manage: start, update, scale and cease of the VNF, and (b) policies for: needed resources, when to scale, how to respond to errors, configurations, and dependencies on other resources; testing, through the tools of the product design and creation environment of the NFV management hardware system, the VNF; receiving, through the NFV management hardware system, a request that the VNF be approved for use in the NFV-based network; responsive to the request and upon ensuring that verification and validation tests have been completed for the VNF, releasing, through the tools of the product design and creation environment of the NFV management hardware system, the VNF for service generation; generating, through the tools of the product design and creation environment of the NFV management hardware system, a first service from the VNF; storing, by the product design and creation environment of the NFV management hardware system, the first service in the master catalog; making the first service accessible through the master catalog, by the product design and creation environment of the NFV management hardware system; combining, through the tools of the product design and creation environment of the NFV management hardware system, the first service with a second service existing in the master catalog to create a new third service in the master catalog with references being made to the first service and the second service; adding to the third service, through the tools of the product design and creation environment of the NFV management hardware system, processes and policies to address: an order in which the first service and the second service must be instantiated, service configuration, attributes required for instantiation, prerequisites, and compatibility with other services; validating, through the tools of the product design and creation environment of the NFV management hardware system, the compatibility of the first service with the second service to ensure there is interoperability and that no policies have been breached; responsive to the validation, making the third service available for instantiation in the NFV-based network; receiving, through the tools of the product design and creation environment of the NFV management hardware system, a new definition of a product that references the third service and that adds an additional set of processes and policies which address: price plans, order capture process, product eligibility for markets and customer types, and upgrades from previous product versions; automatically making the product available in a customer ordering system of the NFV management hardware system for selection, ordering, and provisioning of the product by customers of the NFV-based network. 4. The computer program product of claim 3 , wherein the computer program product is operable such that separation between product, service, and resource layers is maintained in the master catalog. 5. A system comprising: a memory system storing a master catalog; and one or more processing cores of a network function virtualization (NFV) management hardware system that are coupled to the memory system and that are each configured to: identify a virtual network function (VNF) newly stored in the master catalog of the NFV management hardware system within a network function virtualization (NFV)-based network, the VNF being a software program implementation of a function within the NFV-based network; receive, through tools of a product design and creation environment of the NFV management hardware system, details about the VNF, including: (a) processes to manage: start, update, scale and cease of the VNF, and (b) policies for: needed resources, when to scale, how to respond to errors, configurations, and dependencies
Catalogue creation or management · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.