Catalog File Variable Path for Virtualized Network Function Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing system faces challenges in efficiently creating a network service providing environment due to the large size and varied configuration of catalogs, which necessitates storing them in large-scale facilities, leading to prolonged transmission times from Central Data Centers to small-scale facilities, thereby increasing the time required to set up the environment.
Innovation Solution
A deployment control server is introduced that supplies a catalog file with a variable path to the deployment destination node, allowing it to download image files from designated image file storage nodes, reducing the need for pre-storing catalogs at each facility and shortening the setup time by selecting a nearby Regional Data Center as the download source.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If catalogs are stored in large-scale facilities (CDCs), then the storage capacity is sufficient, but the transmission time to small-scale facilities (GCs) becomes long
Solution Approach 1:
The catalog is divided into two parts: a small catalog file (metadata/configuration) that is transmitted to the GC, and a large image file that is downloaded directly from the CDC by the GC. This segmentation allows the critical path to be reduced to only the small catalog file transmission, while the large image file is fetched independently from the original storage location.
Solution Approach 2:
The catalog file acts as an intermediary that contains references (paths) to the actual image files. Instead of transmitting the entire catalog including large image files, the system transmits only the catalog file with paths, and the GC uses these paths to download image files directly from the CDC, eliminating the need for pre-uploading images to intermediate locations.
2Device complexity
If catalogs are transmitted from distant CDCs to GCs, then centralized storage is maintained, but the setup time for network service environment increases
Solution Approach 1:
The catalog file is prepared in advance at the CDC with embedded paths to image files, and this small catalog file is transmitted to the GC before the actual deployment. This preliminary action allows the GC to have all the information needed to quickly download and deploy image files without waiting for lengthy transmissions from the CDC.
Solution Approach 2:
The system transitions from a static model where all catalog data must be pre-transmitted to a dynamic model where the catalog file provides dynamic references that allow the GC to fetch image files on-demand from the CDC, optimizing the balance between centralized control and deployment speed.
3Quantity of substance
If all catalog files are stored centrally at CDCs, then storage resources are efficiently utilized, but the load on communication networks increases during deployment
Solution Approach 1:
The large image files are extracted from the catalog concept and stored separately at the CDC, while only the small catalog file with path references is transmitted to the GC. This extraction reduces the network load during catalog transmission to minimal levels, while the actual large file transfers occur directly between CDC and GC without involving intermediate network paths.
Data Source
AI summary
A deployment control server includes one or more processors. At least one of the one or more processors executes: supplying, to a deployment destination node in which a network service providing environment is to be created, a catalog file for referring a path to which the deployment destination node refers in order to download an image file for creating the network service providing environment, the path being written using a variable; supplying, to one or more image file storage nodes that are different from the deployment destination node, the image file for creating the network service providing environment; and providing, to the deployment destination node, a creation instruction to download the image file from the path written in the catalog file and thereby execute creation of the network service providing environment, and the path for downloading the image file from one of the one or more image file storage nodes as an argument with respect to the variable.