Network Service Descriptor Abstract Entities for Instance Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Network Service Descriptors (NSDs) lack the ability to specify different roles and connectivity for each instance of a given type within Virtual Network Function Forwarding Graphs (VNFFGs) and Network Forwarding Paths (NFPs, leading to ambiguity in traffic forwarding patterns and interconnections.
Innovation Solution
Introduce abstract entities in the NSD to allow indirect referencing of entity types, enabling multiple abstract entities for each entity type, which can be defined in the NSD and used in VNFFGs and NFPDs, allowing different interconnections and forwarding rules for each instance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If direct references to entity types are used in NSD, then the specification is simple and straightforward, but different roles and connectivity for each instance of a given type cannot be specified, leading to ambiguity in traffic forwarding patterns
Solution Approach 1:
The patent introduces abstract entities as intermediary elements between entity types and instances. These abstract entities serve as mediators that enable the specification of different roles and connectivity for each instance while maintaining a structured specification approach. The abstract entities act as a layer that translates the need for instance-specific customization into the existing descriptor reference framework.
2Manufacturing precision
If abstract entities are introduced to enable different interconnections for each instance, then precise definition of forwarding paths and rules is achieved, but the NSD specification structure becomes more complex
Solution Approach 1:
The patent segments the specification structure by introducing abstract entities as distinct intermediate elements. This segmentation allows the specification to be divided into entity type definitions, abstract entity definitions, and instance references, enabling precise control over forwarding paths while organizing the complexity into manageable segments rather than a monolithic structure.
3Reliability
If multiple abstract entities are allowed for each entity type, then ambiguity in traffic forwarding patterns is eliminated, but the number of elements to manage increases
Solution Approach 1:
The patent creates universal abstract entity templates that can be reused across multiple instances. Each abstract entity definition serves as a multi-functional template that can be referenced by multiple instances, reducing the need to define each instance separately. This universality maintains clarity in forwarding specifications while reducing the total number of unique elements that need to be managed.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
There are provided methods for defining a Network Service Descriptor (NSD) for a Network Service (NS), and Network Functions Virtualization (NFV) Orchestrator (NFVO) using said NSD. The NSD comprises zero, one or more of each of: a Virtualized Network Function (VNF) Descriptor (VNFD), a Physical Network Function (PNF) Descriptor (PNFD), a Network Service Descriptor (NSD), a Virtual Link (VL) Descriptor (VLD), and a VNF Forwarding Graph Descriptor (VNFFGD). One method comprising the step of defining at least one Connection Points (CP) Profile, wherein the CP Profile is referenced through a cpProfileId in a Network Forwarding Path Descriptor (NFPD) attribute of the VNFFGD, the CP Profile specifying a Connection Point Descriptor (CPD) or Service Access Point Descriptor (SAPD) for a given VnfProfile, PnfProfile or NsProfile.