Packet Virtual Network Modeling for Service Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for configuring and managing packet technology services are labor-intensive, time-consuming, and expensive, lacking a technology-independent 'click-and-go' approach for service design and packet connectivity, especially for complex multipoint-to-multipoint services across major packet-based domains.
Innovation Solution
The implementation of packet virtual networks (PVNs) that provide technology-independent models for packet flow inspection, shaping, and configuration, using flow interface objects and connectivity objects to visually model Ethernet and non-Ethernet services, enabling rapid service design and deployment across various packet-based domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual software design and labor intensive coding are used for service configuration, then custom designed solutions can be provided, but deployment time and costs increase significantly
Solution Approach 1:
The patent uses template-based service models that can be copied and instantiated multiple times. Pre-defined service templates capture standard service configurations, allowing rapid deployment by copying templates rather than manually designing each service from scratch. This reduces deployment time while maintaining the ability to customize services by modifying template parameters.
Solution Approach 2:
The patent implements pre-configured service templates and models that contain standard service configurations prepared in advance. These templates include pre-defined parameters, policies, and configurations that can be directly applied to new services, eliminating the need for manual software design and coding for each service deployment.
2Manufacturing precision
If technology specific modeling is used for service configuration, then accurate service models can be created, but the process becomes slow and expensive
Solution Approach 1:
The patent implements a universal service modeling framework that can handle multiple service types and technologies through a common template structure. The service models are designed to be technology-agnostic, allowing the same modeling approach to be applied across different service domains while maintaining accuracy through parameter-specific configurations.
Solution Approach 2:
The patent divides service models into modular components and parameters that can be independently configured. Service templates are segmented into reusable building blocks, allowing accurate service modeling through combination of standardized modules rather than creating complete service models from scratch for each deployment.
3Adaptability or versatility
If extensive manual software design is performed, then complex multipoint-to-multipoint services can be modeled, but labor costs and deployment time increase
Solution Approach 1:
The patent introduces an intermediary service modeling layer that sits between the physical network infrastructure and the service configuration interface. This intermediary layer provides automated service model generation and validation, reducing the complexity of configuring complex multipoint-to-multipoint services by handling the intricate details through automated processes rather than manual design.
4Adaptability or versatility
If technology independent models are implemented, then agnostic service design is achieved, but support for specific packet flow inspection and shaping may be limited
Solution Approach 1:
The patent implements a hierarchical modeling approach where general technology-independent service templates provide the overall service framework, while technology-specific parameters and policies can be applied at the local level for specific packet flow inspection and shaping requirements. This allows the system to maintain technology independence at the service design level while providing precise control for specific packet handling needs.
Data Source
AI summary
Methods, systems, and computer readable media for modeling packet technology services using a packet virtual network (PVN) are provided. In some aspects, and at a computing platform, a method includes providing a plurality of flow interface objects. Each flow interface object can be associated with a physical device. The method further includes configuring the flow interface objects into a PVN, wherein the flow interface objects represent network devices or device sub-interfaces. The method further includes displaying the PVN for visually modeling an Ethernet and/or a non-Ethernet packet technology service. An exemplary system includes a computing platform having at least one processor and a memory, the computing platform being configured to access a plurality of flow interface objects stored in the memory and a PVN)-modeling module (PVN-MM) for grouping the flow interface objects into a PVN for modeling a service.