Dynamic Network Routing Using Bypass Configuration Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional static routing rules in network systems require extensive development, testing, and deployment for updates, leading to downtime and inflexibility in handling evolving market needs and regulatory restrictions.
Innovation Solution
Implementing dynamic routing tags in routing table entries that allow switch devices to bypass conventional static rules by accessing separate configuration files for dynamic routing criteria, based on additional message data, enhancing flexibility and reducing the need for frequent table updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Stability of the object's composition
If static routing rules are used in routing tables, then routing stability is maintained, but flexibility to adapt to market and regulatory changes deteriorates
Solution Approach 1:
The patent segments the routing system into two distinct components: static routing rules stored in routing tables and dynamic routing criteria stored in configuration files. This segmentation allows the static rules to maintain routing stability while the dynamic configuration files provide flexibility for market and regulatory changes, resolving the contradiction between stability and adaptability.
Solution Approach 2:
The patent introduces dynamic routing criteria that can be updated in configuration files without modifying the static routing tables. This dynamic component allows the system to adapt to changing market conditions and regulatory requirements while maintaining the stability of the core routing infrastructure, effectively resolving the contradiction between stability and flexibility.
2Adaptability or versatility
If routing table updates are performed to accommodate market and regulatory changes, then adaptability improves, but system downtime and complexity increase
Solution Approach 1:
By separating dynamic routing criteria from static routing rules into different files, the patent enables updates to be performed on configuration files without affecting the core routing table. This segmentation eliminates the need for system downtime during routing updates, as changes can be applied to configuration files while the system continues to operate with existing routing tables.
Solution Approach 2:
The patent allows routing criteria to be pre-configured in configuration files before they are needed. When market or regulatory changes occur, the pre-configured criteria can be quickly activated by updating configuration files rather than developing and testing new routing logic, significantly reducing update time and eliminating downtime.
3Adaptability or versatility
If static routing rules are updated frequently, then adaptability improves, but development and testing complexity increase
Solution Approach 1:
The patent segments routing logic into static rules that require minimal changes and dynamic criteria that can be frequently updated in configuration files. This segmentation reduces development and testing complexity because configuration file updates do not require the extensive validation that modifying routing table logic would require, enabling frequent adaptations to regulatory changes.
Solution Approach 2:
The patent introduces configuration files as an intermediary layer between market requirements and the core routing system. This intermediary allows adaptive changes to be made without directly modifying the routing logic, reducing development and testing complexity while maintaining the ability to respond to regulatory restrictions.
4Adaptability or versatility
If dynamic routing criteria are implemented, then flexibility improves, but system complexity increases
Solution Approach 1:
The patent segments the system into well-defined components: static routing tables and dynamic configuration files. This clear segmentation provides a simple interface between static and dynamic components, reducing the perceived complexity despite the enhanced flexibility. The separation of concerns makes the system architecture more manageable and easier to understand.
Data Source
AI summary
Systems and methods are provided for use in dynamically routing messages. One example method includes receiving, by a switch device of a network, a message including an account number indicative of a recipient institution and, in response, identifying a routing table entry for the message based on the account number. The method also includes identifying, by the switch device, a dynamic routing tag in the routing table entry and then, based on the dynamic routing tag, accessing a configuration file including bypass routing instructions for message. The configuration file is separate from the routing table entry. The method then includes routing, by the switch device, the message to the recipient institution consistent with the bypass routing instructions, instead of using routing instructions included in the identified routing table entry.


