OpenFlow Controller Inter-Domain Packet Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no known technique for establishing communication between hosts/networking elements in one OpenFlow domain to communicate with those in other OpenFlow domains, which are often geographically separated.
Innovation Solution
A method where a first controller device in one OpenFlow domain receives a packet destined for a destination endpoint in another domain, outputs a broadcast message to associate controller devices, receives a response, updates its flow table, and transmits the packet, using edge devices for encryption and decryption as needed, to enable inter-domain packet transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If OpenFlow domains are kept separate for security and management reasons, then domain isolation and security are maintained, but communication between domains cannot be established
Solution Approach 1:
The patent introduces an intermediary mechanism where the first controller device acts as a mediator between OpenFlow domains. It receives packets destined for external domains, outputs broadcast messages to discover routing information, and establishes flow tables to enable communication while maintaining domain separation. This intermediary approach allows inter-domain communication without merging the domains themselves.
2Adaptability or versatility
If broadcast messages are sent to discover routing information across domains, then inter-domain communication is enabled, but network traffic and controller overhead increase
Solution Approach 1:
The patent applies preliminary action by having the first controller device pre-establish flow tables with routing information from other domains before actual data transmission occurs. The broadcast message mechanism is used proactively to discover and store routing information, so that subsequent packet forwarding can occur efficiently without repeated broadcast operations.
3Adaptability or versatility
If flow tables are synchronized between controllers, then routing information is shared across domains, but information security and domain autonomy are compromised
Solution Approach 1:
The patent applies local quality by allowing each controller device to maintain its own local flow table with domain-specific routing information while selectively sharing only necessary routing data with external controllers. The first controller device updates its local flow table based on broadcast responses but keeps the detailed flow information localized, enabling secure inter-domain communication without full flow table synchronization.
Data Source
AI summary
A computer-implemented method comprising: receiving, by a first controller device in a first OpenFlow domain, a packet from an originating endpoint in the first OpenFlow domain destined for a destination endpoint in a second OpenFlow domain that is separate from the first OpenFlow domain; outputting, by the first controller device, a broadcast message identifying the destination endpoint to a plurality of respective controller devices associated with separate OpenFlow domains; receiving, by the first controller device, a response to the broadcast message from the destination endpoint via a second controller device associated with the second OpenFlow domain; updating, by the first controller device, a local flow table identifying a flow for transmitting the packet to the destination endpoint based on information included in the response; and transmitting, by the first controller device, the packet towards the destination endpoint based on updating the local flow table.