Global Persistence Mechanism for Autonomous Exchange Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multiparty service architectures lack global routing intelligence, leading to inefficient service request routing across autonomous exchange platforms, resulting in error messages and increased complexity, especially when partner carriers daisy-chain their platforms to find the correct hosting exchange platform for service sessions.
Innovation Solution
A network device with load balancer and application delivery controller capabilities captures successful routing information to create a global persistence mechanism, allowing subsequent service requests to be routed directly to the correct autonomous device hosting the multiparty service session, thereby reducing errors and complexity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If autonomous exchange platforms are used to provide multiparty services, then service autonomy and distributed architecture are improved, but global routing intelligence is lost leading to inefficient service request routing
Solution Approach 1:
The patent introduces a global persistence mechanism as an intermediary layer between autonomous exchange platforms. This mechanism maintains routing information about which exchange platforms host specific service sessions, enabling intelligent routing without centralizing control. The global persistence acts as a mediator that provides routing intelligence while preserving the autonomy of individual exchange platforms.
Solution Approach 2:
The system performs preliminary action by establishing and maintaining a global persistence mechanism that pre-records routing information about service session locations. Before service requests need to be routed, the system has already captured and stored the necessary routing intelligence, enabling direct and efficient routing decisions without requiring complex real-time discovery or daisy-chaining of platforms.
2Reliability
If daisy-chaining of exchange platforms is implemented to locate hosting platforms, then service request delivery is achieved, but error messages increase and routing efficiency decreases
Solution Approach 1:
The global persistence mechanism implements feedback by continuously capturing and updating routing information about where service sessions are hosted. This feedback loop ensures that the system always has current knowledge of service locations, enabling direct routing to the correct exchange platform without requiring time-consuming daisy-chaining or generating error messages during service request delivery.
3Productivity
If global routing intelligence is implemented, then service request routing efficiency is improved, but infrastructure cost and system complexity increase
Solution Approach 1:
The system implements self-service by enabling exchange platforms to autonomously provide routing information about their hosted service sessions. The global persistence mechanism captures this self-provided information without requiring complex external management infrastructure. Each exchange platform essentially serves itself by contributing routing data, which the global persistence then utilizes for efficient routing decisions.
Data Source
AI summary
Methods, devices, and storage media provide for receiving a request to use a multiparty service offered by autonomous devices; determining whether persistence information exists that indicates one of the autonomous devices to which the request is to be routed; selecting one of the autonomous devices to transmit the request in response to determining that persistence information does not exist, and wherein the device has no knowledge which of the autonomous devices is to accept the request; transmitting the request; receiving a response; recognizing whether the request is accepted based on the response; storing persistence information indicating the one of the autonomous devices is servicing the request; and using the persistence information to transmit a subsequent request to use the multiparty service to the one of the autonomous devices, wherein the subsequent request pertains to a same session of the multiparty service as the request.