Extending Routing Rules from External Services via SDN

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional networks are not programmable entities, making it impractical to configure them in real-time as they become more complex, especially when responding to external changes, as the intelligence lies within programming frameworks rather than network devices like switches or routers.

Innovation Solution

Implementing a software-defined networking (SDN) framework that allows for the extension of routing rules from external services through a computer-implemented method, using a network abstraction layer and service implementation layer to receive, interpret, and execute requests via a predefined API, enabling programmability at network elements like switches and routers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional networks are configured at individual devices, then network control is maintained at device level, but network complexity increases and real-time responsiveness becomes impractical

Engineering Contradiction:
Improvereal-time network configuration capabilityVSAvoidnetwork device complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the intelligence from individual network devices and concentrates it in a centralized controller. The controller receives flow requests, processes routing decisions, and pushes configured flows to network elements, thereby removing the complexity burden from individual devices while enabling real-time network configuration through centralized coordination.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments network control into distinct functional layers: a centralized controller that handles high-level routing decisions and flow configuration, and network elements that execute specific flow operations. This segmentation allows the controller to manage network complexity while network elements maintain simple, dedicated functions for packet forwarding and processing.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If intelligence is placed in programming frameworks rather than network devices, then framework control is centralized, but network adaptability to external changes decreases

Engineering Contradiction:
Improvenetwork adaptability to external changesVSAvoidnetwork configuration ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements dynamic network configuration where the centralized controller receives flow requests in real-time, processes routing decisions based on current network state, and pushes updated flow configurations to network elements. This dynamic approach enables the network to adapt to external changes while maintaining ease of operation through automated controller-mediated configuration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent establishes a feedback loop where network elements report flow status and network state information back to the centralized controller. The controller uses this feedback to make informed routing decisions and adjust flow configurations, enabling real-time network adaptability while simplifying operation through automated closed-loop control.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If routing rules are extended from external services, then network programmability is enabled, but system architecture complexity increases

Engineering Contradiction:
Improvenetwork programmabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a centralized controller as an intermediary between external services and network elements. The controller receives routing rules from external services, processes and validates them, then translates and pushes appropriate flow configurations to network elements. This intermediary approach enables network programmability while containing architecture complexity within the controller rather than distributing it throughout the network.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9509549B2Extending routing rules from external services
Publication Date: 2016.11.29 CISCO TECHNOLOGY INC
  • US9509549B2 patent drawing
  • US9509549B2 patent drawing
  • US9509549B2 patent drawing

AI summary

Techniques are disclosed to extend routing rules from external services. A request is received to modify a specified rule in a network element of a network. The specified rule governs disposition of a network flow specific to an application. The request is received via a communications channel configured to expose an application programming interface (API) to the application. The request is interpreted at a network abstraction layer of the network element. The request is converted into a command at a service implementation layer of the network element. The command is executed to modify the specified rule in the network element, responsive to the request.