Flow Interface Configuration for Automated Packet Service Deployment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current technologies for managing packet services require extensive manual software design, labor-intensive coding, and technology-specific modeling, making them expensive, time-consuming, and slow to deploy, with no technology-independent solutions for packet network configurations or multipoint-to-multipoint service modeling.

Innovation Solution

The method involves configuring flow interfaces on network routing elements using a virtual construct that supports technology-independent models for packet-based management tasks, enabling automated delivery of enterprise services by establishing flow interfaces with specified parameters and implementing them on media interfaces of network routing elements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual software design and labor-intensive coding are used for service configuration, then customization and control are improved, but deployment time and cost increase

Engineering Contradiction:

Improveservice configuration controlVSAvoiddeployment time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The patent uses templates to store predefined service configurations and network connectivity models. These templates act as reusable copies that can be instantiated multiple times without manual redesign, enabling rapid deployment while maintaining customization through template selection and parameter adjustment.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by pre-defining service configurations, network models, and connectivity templates before actual service deployment. This allows the system to automatically generate service-specific configurations from generic templates, eliminating the need for manual software design during deployment.

Inventive Principle:

Principle #10Preliminary action

2Manufacturing precision

If technology-specific modeling is used for packet network configuration, then precision and control are improved, but adaptability to different packet domains decreases

Engineering Contradiction:

Improveconfiguration precisionVSAvoidpacket domain adaptability

Core Design Contradiction:

Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The patent implements technology-independent models that can represent multiple packet-based domains (Ethernet, MPLS, ATM, Frame Relay, X.25) using a unified framework. The service configuration templates and network connectivity models are domain-agnostic, allowing the same modeling approach to be applied across different packet technologies while maintaining configuration precision through domain-specific parameter instantiation.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If extensive manual design and coding are required for enterprise service deployment, then service customization is improved, but productivity and automation level decrease

Engineering Contradiction:

Improveservice customizationVSAvoidservice deployment productivity

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system stores service configurations and network connectivity models as reusable templates that can be copied and instantiated for multiple services. This eliminates the need for extensive manual design and coding for each new service deployment, significantly improving productivity while maintaining customization through template selection and parameter configuration.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system enables self-service automation by automatically generating service-specific configurations from generic templates, performing self-testing of network connectivity, and automating the provisioning process. This reduces reliance on manual intervention while maintaining service customization through automated template instantiation and configuration generation.

Inventive Principle:

Principle #25Self-service

4Ease of manufacture

If technology-independent models are not used, then implementation simplicity is improved, but system versatility and reusability across packet domains decrease

Engineering Contradiction:

Improveimplementation simplicityVSAvoidpacket domain versatility

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements technology-independent models that provide a universal framework for representing multiple packet-based domains. The service configuration templates and network connectivity models are designed to be domain-agnostic, allowing the same modeling approach to be applied across different packet technologies while maintaining implementation simplicity through a unified template-based approach.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9866408B2Methods, systems, and computer readable media for configuring a flow interface on a network routing element

Publication Date: 2018.01.09 ORACLE INT CORP

AI summary

According to one aspect, the disclosed subject matter describes herein a method that includes establishing a plurality of flow interfaces associated with an enterprise service in response to receiving an order request for the enterprise service and sending, for each of the plurality of flow interfaces, flow interface information that specifies parameters associated with the flow interface to a network routing element designated to transport the enterprise service. The method further includes configuring the flow interface on a media interface of the network routing element as specified by the parameters included in the flow interface information and implementing the enterprise service via the configured flow interface.